FOSS Wiki mediawiki https://foss.wiki/ MediaWiki 1.46.0 first-letter Media Special Talk User User talk FW FW talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk Guides Guides talk 10 494 1612 2020-03-17T22:04:25Z starcitizen>Alistar Bot 0 /* top */Hygiene, removed: {{Documentation}} wikitext text/x-wiki {{Documentation}} {{t|Cleanup}} should be placed on articles or section that you believe require a cleanup. This template adds pages to [[:Category:Pages needing cleanup]]. You should always specify the reason by including a parameter. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Should be rewritten as prose", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance templates]]</includeonly> a8a80c83c546e8cedf74e332782e1e4f2b22bd4b 10 487 1598 2020-03-19T00:32:09Z starcitizen>Alistair3149 0 wikitext text/x-wiki <includeonly>{{#invoke:Documentation|doc}}__NOEDITSECTION__{{#seo: |type = website |description = {{FULLPAGENAME}} is a template page used on the Star Citizen Wiki. Templates are pages that are embedded (transcluded) into other pages to allow for the repetition of information. |site_name = Star Citizen Wiki |locale = {{PAGELANGUAGE}} }}</includeonly><noinclude>{{/doc}}</noinclude> 2690a5347936db4ace54fe94a0b3092b6bb04a37 236 2022-03-29T02:14:34Z wikipedia>Bsherr 0 consistent with new substitution template format wikitext text/x-wiki {{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}<noinclude> <!-- Add categories to the /doc subpage --> </noinclude> 9e62b964e96c4e3d478edecbfcb3c0338ae8a276 237 236 2024-06-04T01:07:18Z Electron271 3 1 revision imported wikitext text/x-wiki {{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}<noinclude> <!-- Add categories to the /doc subpage --> </noinclude> 9e62b964e96c4e3d478edecbfcb3c0338ae8a276 828 359 1323 2020-04-01T06:12:40Z Wikipedia->MusikAnimal 0 1 revision imported Scribunto text/plain -- This module provides easy processing of arguments passed to Scribunto from -- #invoke. It is intended for use by other Lua modules, and should not be -- called from #invoke directly. local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local arguments = {} -- Generate four different tidyVal functions, so that we don't have to check the -- options every time we call it. local function tidyValDefault(key, val) if type(val) == 'string' then val = val:match('^%s*(.-)%s*$') if val == '' then return nil else return val end else return val end end local function tidyValTrimOnly(key, val) if type(val) == 'string' then return val:match('^%s*(.-)%s*$') else return val end end local function tidyValRemoveBlanksOnly(key, val) if type(val) == 'string' then if val:find('%S') then return val else return nil end else return val end end local function tidyValNoChange(key, val) return val end local function matchesTitle(given, title) local tp = type( given ) return (tp == 'string' or tp == 'number') and mw.title.new( given ).prefixedText == title end local translate_mt = { __index = function(t, k) return k end } function arguments.getArgs(frame, options) checkType('getArgs', 1, frame, 'table', true) checkType('getArgs', 2, options, 'table', true) frame = frame or {} options = options or {} --[[ -- Set up argument translation. --]] options.translate = options.translate or {} if getmetatable(options.translate) == nil then setmetatable(options.translate, translate_mt) end if options.backtranslate == nil then options.backtranslate = {} for k,v in pairs(options.translate) do options.backtranslate[v] = k end end if options.backtranslate and getmetatable(options.backtranslate) == nil then setmetatable(options.backtranslate, { __index = function(t, k) if options.translate[k] ~= k then return nil else return k end end }) end --[[ -- Get the argument tables. If we were passed a valid frame object, get the -- frame arguments (fargs) and the parent frame arguments (pargs), depending -- on the options set and on the parent frame's availability. If we weren't -- passed a valid frame object, we are being called from another Lua module -- or from the debug console, so assume that we were passed a table of args -- directly, and assign it to a new variable (luaArgs). --]] local fargs, pargs, luaArgs if type(frame.args) == 'table' and type(frame.getParent) == 'function' then if options.wrappers then --[[ -- The wrappers option makes Module:Arguments look up arguments in -- either the frame argument table or the parent argument table, but -- not both. This means that users can use either the #invoke syntax -- or a wrapper template without the loss of performance associated -- with looking arguments up in both the frame and the parent frame. -- Module:Arguments will look up arguments in the parent frame -- if it finds the parent frame's title in options.wrapper; -- otherwise it will look up arguments in the frame object passed -- to getArgs. --]] local parent = frame:getParent() if not parent then fargs = frame.args else local title = parent:getTitle():gsub('/sandbox$', '') local found = false if matchesTitle(options.wrappers, title) then found = true elseif type(options.wrappers) == 'table' then for _,v in pairs(options.wrappers) do if matchesTitle(v, title) then found = true break end end end -- We test for false specifically here so that nil (the default) acts like true. if found or options.frameOnly == false then pargs = parent.args end if not found or options.parentOnly == false then fargs = frame.args end end else -- options.wrapper isn't set, so check the other options. if not options.parentOnly then fargs = frame.args end if not options.frameOnly then local parent = frame:getParent() pargs = parent and parent.args or nil end end if options.parentFirst then fargs, pargs = pargs, fargs end else luaArgs = frame end -- Set the order of precedence of the argument tables. If the variables are -- nil, nothing will be added to the table, which is how we avoid clashes -- between the frame/parent args and the Lua args. local argTables = {fargs} argTables[#argTables + 1] = pargs argTables[#argTables + 1] = luaArgs --[[ -- Generate the tidyVal function. If it has been specified by the user, we -- use that; if not, we choose one of four functions depending on the -- options chosen. This is so that we don't have to call the options table -- every time the function is called. --]] local tidyVal = options.valueFunc if tidyVal then if type(tidyVal) ~= 'function' then error( "bad value assigned to option 'valueFunc'" .. '(function expected, got ' .. type(tidyVal) .. ')', 2 ) end elseif options.trim ~= false then if options.removeBlanks ~= false then tidyVal = tidyValDefault else tidyVal = tidyValTrimOnly end else if options.removeBlanks ~= false then tidyVal = tidyValRemoveBlanksOnly else tidyVal = tidyValNoChange end end --[[ -- Set up the args, metaArgs and nilArgs tables. args will be the one -- accessed from functions, and metaArgs will hold the actual arguments. Nil -- arguments are memoized in nilArgs, and the metatable connects all of them -- together. --]] local args, metaArgs, nilArgs, metatable = {}, {}, {}, {} setmetatable(args, metatable) local function mergeArgs(tables) --[[ -- Accepts multiple tables as input and merges their keys and values -- into one table. If a value is already present it is not overwritten; -- tables listed earlier have precedence. We are also memoizing nil -- values, which can be overwritten if they are 's' (soft). --]] for _, t in ipairs(tables) do for key, val in pairs(t) do if metaArgs[key] == nil and nilArgs[key] ~= 'h' then local tidiedVal = tidyVal(key, val) if tidiedVal == nil then nilArgs[key] = 's' else metaArgs[key] = tidiedVal end end end end end --[[ -- Define metatable behaviour. Arguments are memoized in the metaArgs table, -- and are only fetched from the argument tables once. Fetching arguments -- from the argument tables is the most resource-intensive step in this -- module, so we try and avoid it where possible. For this reason, nil -- arguments are also memoized, in the nilArgs table. Also, we keep a record -- in the metatable of when pairs and ipairs have been called, so we do not -- run pairs and ipairs on the argument tables more than once. We also do -- not run ipairs on fargs and pargs if pairs has already been run, as all -- the arguments will already have been copied over. --]] metatable.__index = function (t, key) --[[ -- Fetches an argument when the args table is indexed. First we check -- to see if the value is memoized, and if not we try and fetch it from -- the argument tables. When we check memoization, we need to check -- metaArgs before nilArgs, as both can be non-nil at the same time. -- If the argument is not present in metaArgs, we also check whether -- pairs has been run yet. If pairs has already been run, we return nil. -- This is because all the arguments will have already been copied into -- metaArgs by the mergeArgs function, meaning that any other arguments -- must be nil. --]] if type(key) == 'string' then key = options.translate[key] end local val = metaArgs[key] if val ~= nil then return val elseif metatable.donePairs or nilArgs[key] then return nil end for _, argTable in ipairs(argTables) do local argTableVal = tidyVal(key, argTable[key]) if argTableVal ~= nil then metaArgs[key] = argTableVal return argTableVal end end nilArgs[key] = 'h' return nil end metatable.__newindex = function (t, key, val) -- This function is called when a module tries to add a new value to the -- args table, or tries to change an existing value. if type(key) == 'string' then key = options.translate[key] end if options.readOnly then error( 'could not write to argument table key "' .. tostring(key) .. '"; the table is read-only', 2 ) elseif options.noOverwrite and args[key] ~= nil then error( 'could not write to argument table key "' .. tostring(key) .. '"; overwriting existing arguments is not permitted', 2 ) elseif val == nil then --[[ -- If the argument is to be overwritten with nil, we need to erase -- the value in metaArgs, so that __index, __pairs and __ipairs do -- not use a previous existing value, if present; and we also need -- to memoize the nil in nilArgs, so that the value isn't looked -- up in the argument tables if it is accessed again. --]] metaArgs[key] = nil nilArgs[key] = 'h' else metaArgs[key] = val end end local function translatenext(invariant) local k, v = next(invariant.t, invariant.k) invariant.k = k if k == nil then return nil elseif type(k) ~= 'string' or not options.backtranslate then return k, v else local backtranslate = options.backtranslate[k] if backtranslate == nil then -- Skip this one. This is a tail call, so this won't cause stack overflow return translatenext(invariant) else return backtranslate, v end end end metatable.__pairs = function () -- Called when pairs is run on the args table. if not metatable.donePairs then mergeArgs(argTables) metatable.donePairs = true end return translatenext, { t = metaArgs } end local function inext(t, i) -- This uses our __index metamethod local v = t[i + 1] if v ~= nil then return i + 1, v end end metatable.__ipairs = function (t) -- Called when ipairs is run on the args table. return inext, t, 0 end return args end return arguments 3134ecce8429b810d445e29eae115e2ae4c36c53 1590 1323 2023-01-24T03:54:04Z starcitizen>Alistair3149 0 Protected "[[Module:Arguments]]" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) Scribunto text/plain -- This module provides easy processing of arguments passed to Scribunto from -- #invoke. It is intended for use by other Lua modules, and should not be -- called from #invoke directly. local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local arguments = {} -- Generate four different tidyVal functions, so that we don't have to check the -- options every time we call it. local function tidyValDefault(key, val) if type(val) == 'string' then val = val:match('^%s*(.-)%s*$') if val == '' then return nil else return val end else return val end end local function tidyValTrimOnly(key, val) if type(val) == 'string' then return val:match('^%s*(.-)%s*$') else return val end end local function tidyValRemoveBlanksOnly(key, val) if type(val) == 'string' then if val:find('%S') then return val else return nil end else return val end end local function tidyValNoChange(key, val) return val end local function matchesTitle(given, title) local tp = type( given ) return (tp == 'string' or tp == 'number') and mw.title.new( given ).prefixedText == title end local translate_mt = { __index = function(t, k) return k end } function arguments.getArgs(frame, options) checkType('getArgs', 1, frame, 'table', true) checkType('getArgs', 2, options, 'table', true) frame = frame or {} options = options or {} --[[ -- Set up argument translation. --]] options.translate = options.translate or {} if getmetatable(options.translate) == nil then setmetatable(options.translate, translate_mt) end if options.backtranslate == nil then options.backtranslate = {} for k,v in pairs(options.translate) do options.backtranslate[v] = k end end if options.backtranslate and getmetatable(options.backtranslate) == nil then setmetatable(options.backtranslate, { __index = function(t, k) if options.translate[k] ~= k then return nil else return k end end }) end --[[ -- Get the argument tables. If we were passed a valid frame object, get the -- frame arguments (fargs) and the parent frame arguments (pargs), depending -- on the options set and on the parent frame's availability. If we weren't -- passed a valid frame object, we are being called from another Lua module -- or from the debug console, so assume that we were passed a table of args -- directly, and assign it to a new variable (luaArgs). --]] local fargs, pargs, luaArgs if type(frame.args) == 'table' and type(frame.getParent) == 'function' then if options.wrappers then --[[ -- The wrappers option makes Module:Arguments look up arguments in -- either the frame argument table or the parent argument table, but -- not both. This means that users can use either the #invoke syntax -- or a wrapper template without the loss of performance associated -- with looking arguments up in both the frame and the parent frame. -- Module:Arguments will look up arguments in the parent frame -- if it finds the parent frame's title in options.wrapper; -- otherwise it will look up arguments in the frame object passed -- to getArgs. --]] local parent = frame:getParent() if not parent then fargs = frame.args else local title = parent:getTitle():gsub('/sandbox$', '') local found = false if matchesTitle(options.wrappers, title) then found = true elseif type(options.wrappers) == 'table' then for _,v in pairs(options.wrappers) do if matchesTitle(v, title) then found = true break end end end -- We test for false specifically here so that nil (the default) acts like true. if found or options.frameOnly == false then pargs = parent.args end if not found or options.parentOnly == false then fargs = frame.args end end else -- options.wrapper isn't set, so check the other options. if not options.parentOnly then fargs = frame.args end if not options.frameOnly then local parent = frame:getParent() pargs = parent and parent.args or nil end end if options.parentFirst then fargs, pargs = pargs, fargs end else luaArgs = frame end -- Set the order of precedence of the argument tables. If the variables are -- nil, nothing will be added to the table, which is how we avoid clashes -- between the frame/parent args and the Lua args. local argTables = {fargs} argTables[#argTables + 1] = pargs argTables[#argTables + 1] = luaArgs --[[ -- Generate the tidyVal function. If it has been specified by the user, we -- use that; if not, we choose one of four functions depending on the -- options chosen. This is so that we don't have to call the options table -- every time the function is called. --]] local tidyVal = options.valueFunc if tidyVal then if type(tidyVal) ~= 'function' then error( "bad value assigned to option 'valueFunc'" .. '(function expected, got ' .. type(tidyVal) .. ')', 2 ) end elseif options.trim ~= false then if options.removeBlanks ~= false then tidyVal = tidyValDefault else tidyVal = tidyValTrimOnly end else if options.removeBlanks ~= false then tidyVal = tidyValRemoveBlanksOnly else tidyVal = tidyValNoChange end end --[[ -- Set up the args, metaArgs and nilArgs tables. args will be the one -- accessed from functions, and metaArgs will hold the actual arguments. Nil -- arguments are memoized in nilArgs, and the metatable connects all of them -- together. --]] local args, metaArgs, nilArgs, metatable = {}, {}, {}, {} setmetatable(args, metatable) local function mergeArgs(tables) --[[ -- Accepts multiple tables as input and merges their keys and values -- into one table. If a value is already present it is not overwritten; -- tables listed earlier have precedence. We are also memoizing nil -- values, which can be overwritten if they are 's' (soft). --]] for _, t in ipairs(tables) do for key, val in pairs(t) do if metaArgs[key] == nil and nilArgs[key] ~= 'h' then local tidiedVal = tidyVal(key, val) if tidiedVal == nil then nilArgs[key] = 's' else metaArgs[key] = tidiedVal end end end end end --[[ -- Define metatable behaviour. Arguments are memoized in the metaArgs table, -- and are only fetched from the argument tables once. Fetching arguments -- from the argument tables is the most resource-intensive step in this -- module, so we try and avoid it where possible. For this reason, nil -- arguments are also memoized, in the nilArgs table. Also, we keep a record -- in the metatable of when pairs and ipairs have been called, so we do not -- run pairs and ipairs on the argument tables more than once. We also do -- not run ipairs on fargs and pargs if pairs has already been run, as all -- the arguments will already have been copied over. --]] metatable.__index = function (t, key) --[[ -- Fetches an argument when the args table is indexed. First we check -- to see if the value is memoized, and if not we try and fetch it from -- the argument tables. When we check memoization, we need to check -- metaArgs before nilArgs, as both can be non-nil at the same time. -- If the argument is not present in metaArgs, we also check whether -- pairs has been run yet. If pairs has already been run, we return nil. -- This is because all the arguments will have already been copied into -- metaArgs by the mergeArgs function, meaning that any other arguments -- must be nil. --]] if type(key) == 'string' then key = options.translate[key] end local val = metaArgs[key] if val ~= nil then return val elseif metatable.donePairs or nilArgs[key] then return nil end for _, argTable in ipairs(argTables) do local argTableVal = tidyVal(key, argTable[key]) if argTableVal ~= nil then metaArgs[key] = argTableVal return argTableVal end end nilArgs[key] = 'h' return nil end metatable.__newindex = function (t, key, val) -- This function is called when a module tries to add a new value to the -- args table, or tries to change an existing value. if type(key) == 'string' then key = options.translate[key] end if options.readOnly then error( 'could not write to argument table key "' .. tostring(key) .. '"; the table is read-only', 2 ) elseif options.noOverwrite and args[key] ~= nil then error( 'could not write to argument table key "' .. tostring(key) .. '"; overwriting existing arguments is not permitted', 2 ) elseif val == nil then --[[ -- If the argument is to be overwritten with nil, we need to erase -- the value in metaArgs, so that __index, __pairs and __ipairs do -- not use a previous existing value, if present; and we also need -- to memoize the nil in nilArgs, so that the value isn't looked -- up in the argument tables if it is accessed again. --]] metaArgs[key] = nil nilArgs[key] = 'h' else metaArgs[key] = val end end local function translatenext(invariant) local k, v = next(invariant.t, invariant.k) invariant.k = k if k == nil then return nil elseif type(k) ~= 'string' or not options.backtranslate then return k, v else local backtranslate = options.backtranslate[k] if backtranslate == nil then -- Skip this one. This is a tail call, so this won't cause stack overflow return translatenext(invariant) else return backtranslate, v end end end metatable.__pairs = function () -- Called when pairs is run on the args table. if not metatable.donePairs then mergeArgs(argTables) metatable.donePairs = true end return translatenext, { t = metaArgs } end local function inext(t, i) -- This uses our __index metamethod local v = t[i + 1] if v ~= nil then return i + 1, v end end metatable.__ipairs = function (t) -- Called when ipairs is run on the args table. return inext, t, 0 end return args end return arguments 3134ecce8429b810d445e29eae115e2ae4c36c53 828 495 1614 2023-01-23T20:18:21Z starcitizen>Alistair3149 0 Created page with "-- This implements Template:Tlg local getArgs = require('Module:Arguments').getArgs local p = {} -- Is a string non-empty? local function _ne(s) return s ~= nil and s ~= "" end local nw = mw.text.nowiki local function addTemplate(s) local i, _ = s:find(':', 1, true) if i == nil then return 'Template:' .. s end local ns = s:sub(1, i - 1) if ns == '' or mw.site.namespaces[ns] then return s else return 'Template:' .. s end end local function trimTemplate(..." Scribunto text/plain -- This implements Template:Tlg local getArgs = require('Module:Arguments').getArgs local p = {} -- Is a string non-empty? local function _ne(s) return s ~= nil and s ~= "" end local nw = mw.text.nowiki local function addTemplate(s) local i, _ = s:find(':', 1, true) if i == nil then return 'Template:' .. s end local ns = s:sub(1, i - 1) if ns == '' or mw.site.namespaces[ns] then return s else return 'Template:' .. s end end local function trimTemplate(s) local needle = 'template:' if s:sub(1, needle:len()):lower() == needle then return s:sub(needle:len() + 1) else return s end end local function linkTitle(args) if _ne(args.nolink) then return args['1'] end local titleObj local titlePart = '[[' if args['1'] then -- This handles :Page and other NS titleObj = mw.title.new(args['1'], 'Template') else titleObj = mw.title.getCurrentTitle() end titlePart = titlePart .. (titleObj ~= nil and titleObj.fullText or addTemplate(args['1'])) local textPart = args.alttext if not _ne(textPart) then if titleObj ~= nil then textPart = titleObj:inNamespace("Template") and args['1'] or titleObj.fullText else -- redlink textPart = args['1'] end end if _ne(args.subst) then -- HACK: the ns thing above is probably broken textPart = 'subst:' .. textPart end if _ne(args.brace) then textPart = nw('{{') .. textPart .. nw('}}') elseif _ne(args.braceinside) then textPart = nw('{') .. textPart .. nw('}') end titlePart = titlePart .. '|' .. textPart .. ']]' if _ne(args.braceinside) then titlePart = nw('{') .. titlePart .. nw('}') end return titlePart end function p.main(frame) local args = getArgs(frame, { trim = true, removeBlanks = false }) return p._main(args) end function p._main(args) local bold = _ne(args.bold) or _ne(args.boldlink) or _ne(args.boldname) local italic = _ne(args.italic) or _ne(args.italics) local dontBrace = _ne(args.brace) or _ne(args.braceinside) local code = _ne(args.code) or _ne(args.tt) local show_result = _ne(args._show_result) local expand = _ne(args._expand) -- Build the link part local titlePart = linkTitle(args) if bold then titlePart = "'''" .. titlePart .. "'''" end if _ne(args.nowrapname) then titlePart = '<span class="nowrap">' .. titlePart .. '</span>' end -- Build the arguments local textPart = "" local textPartBuffer = "&#124;" local codeArguments = {} local codeArgumentsString = "" local i = 2 local j = 1 while args[i] do local val = args[i] if val ~= "" then if _ne(args.nowiki) then -- Unstrip nowiki tags first because calling nw on something that already contains nowiki tags will -- mangle the nowiki strip marker and result in literal UNIQ...QINU showing up val = nw(mw.text.unstripNoWiki(val)) end local k, v = string.match(val, "(.*)=(.*)") if not k then codeArguments[j] = val j = j + 1 else codeArguments[k] = v end codeArgumentsString = codeArgumentsString .. textPartBuffer .. val if italic then val = '<span style="font-style:italic;">' .. val .. '</span>' end textPart = textPart .. textPartBuffer .. val end i = i + 1 end -- final wrap local ret = titlePart .. textPart if not dontBrace then ret = nw('{{') .. ret .. nw('}}') end if _ne(args.a) then ret = nw('*') .. '&nbsp;' .. ret end if _ne(args.kbd) then ret = '<kbd>' .. ret .. '</kbd>' end if code then ret = '<code>' .. ret .. '</code>' elseif _ne(args.plaincode) then ret = '<code style="border:none;background:transparent;">' .. ret .. '</code>' end if _ne(args.nowrap) then ret = '<span class="nowrap">' .. ret .. '</span>' end --[[ Wrap as html?? local span = mw.html.create('span') span:wikitext(ret) --]] if _ne(args.debug) then ret = ret .. '\n<pre>' .. mw.text.encode(mw.dumpObject(args)) .. '</pre>' end if show_result then local result = mw.getCurrentFrame():expandTemplate{title = addTemplate(args[1]), args = codeArguments} ret = ret .. " → " .. result end if expand then local query = mw.text.encode('{{' .. addTemplate(args[1]) .. string.gsub(codeArgumentsString, textPartBuffer, "|") .. '}}') local url = mw.uri.fullUrl('special:ExpandTemplates', 'wpInput=' .. query) mw.log() ret = ret .. " [" .. tostring(url) .. "]" end return ret end return p c7307fa3959d308a2dd7fd2f5009c1ce6db3d122 10 493 1610 2023-01-24T21:22:52Z starcitizen>Alistair3149 0 Alistair3149 moved page [[Template:Tlx]] to [[Template:Template link expanded]] wikitext text/x-wiki #REDIRECT [[Template:Template link expanded]] 155e901040104f96908f1f4627c4eb3501301bf9 10 498 1620 2023-01-24T21:22:52Z starcitizen>Alistair3149 0 Alistair3149 moved page [[Template:Tlx]] to [[Template:Template link expanded]] wikitext text/x-wiki {{#Invoke:Template link general|main|code=on}}<noinclude> {{/doc}} <!-- Add categories to the /doc subpage, not here! --> </noinclude> f49d86d852e8c15c4ffa3f08e7f33ddfb0920b22 828 500 1624 2024-02-25T05:33:33Z starcitizen>Alistair3149 0 Scribunto text/plain local libraryUtil = require( 'libraryUtil' ) local checkType = libraryUtil.checkType local mArguments -- lazily initialise [[Module:Arguments]] local mError -- lazily initialise [[Module:Error]] local p = {} --- Helper function to throw error -- -- @param msg string - Error message -- -- @return string - Formatted error message in wikitext local function makeWikitextError( msg ) mError = require( 'Module:Error' ) return mError.error { message = 'Error: ' .. msg .. '.' } end function p.mbox( frame ) mArguments = require( 'Module:Arguments' ) local args = mArguments.getArgs( frame ) local title = args[ 1 ] or args[ 'title' ] local text = args[ 2 ] or args[ 'text' ] if not title or not text then return makeWikitextError( 'no title or text specified' ) end return p._mbox( title, text, { extraclasses = args.extraclasses, icon = args.icon } ) end function p._mbox( title, text, options ) checkType( '_mbox', 1, title, 'string' ) checkType( '_mbox', 2, text, 'string' ) checkType( '_mbox', 3, options, 'table', true ) options = options or {} local mbox = mw.html.create( 'div' ) local extraclasses if type( options.extraclasses ) == 'string' then extraclasses = options.extraclasses end mbox :attr( 'role', 'presentation' ) :addClass( 'mbox' ) :addClass( extraclasses ) local mboxTitle = mbox:tag( 'div' ):addClass( 'mbox-title' ) if options.icon and type( options.icon ) == 'string' then mboxTitle:tag( 'div' ) :addClass( 'mbox-icon metadata' ) :wikitext( '[[File:' .. options.icon .. '|14px|link=]]' ) :done() :tag( 'div' ) :wikitext( title ) else mboxTitle:wikitext( title ) end mbox:tag( 'div' ) :addClass( 'mbox-text' ) :wikitext( text ) return mw.getCurrentFrame():extensionTag { name = 'templatestyles', args = { src = 'Module:Mbox/styles.css' } } .. tostring( mbox ) end return p 5d52ff50f2eed059dbc7aa4785a15ffbb32347c1 0 1 1 2024-06-03T21:48:00Z Test 63 wikitext text/x-wiki <strong>MediaWiki has been installed.</strong> Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language] * [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki] 11cef88175cf81168a86e7c0327a5b2d7a1920f5 2 1 2024-06-03T22:24:32Z Electron271 3 remove the default stuff and add wiki info wikitext text/x-wiki ==== Welcome to the All Things Linux wiki! ==== The wiki is still being developed and setup, in the meantime chat about Linux at https://discord.gg/linux! 20d2c3446d2799861bc213ce63c27799939cce0b 3 2 2024-06-03T22:25:08Z Electron271 3 Protected "[[Main Page]]": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki ==== Welcome to the All Things Linux wiki! ==== The wiki is still being developed and setup, in the meantime chat about Linux at https://discord.gg/linux! 20d2c3446d2799861bc213ce63c27799939cce0b 7 3 2024-06-03T22:55:35Z Electron271 3 added directory wikitext text/x-wiki ==== Welcome to the All Things Linux wiki! ==== The wiki is still being developed and setup, in the meantime chat about Linux at https://discord.gg/linux! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Miscellaneous ==== * [[Main Page]] a22db45e517631d0eb112f0d8e1ed16a597b8b8c 17 7 2024-06-03T23:59:32Z Electron271 3 Chore: Update directory with new pages wikitext text/x-wiki ==== Welcome to the All Things Linux wiki! ==== The wiki is still being developed and setup, in the meantime chat about Linux at https://discord.gg/linux! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Guides ==== * [[Choosing A Linux Distribution]] ==== Miscellaneous ==== * [[Main Page]] 69b22397f256b8965076583bd06edb1fc755f811 21 17 2024-06-04T00:20:50Z Electron271 3 Chore: Update directory with new pages wikitext text/x-wiki ==== Welcome to the All Things Linux wiki! ==== The wiki is still being developed and setup, in the meantime chat about Linux at https://discord.gg/linux! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms]] ==== Miscellaneous ==== * [[Main Page]] 29ef458381ac82f370b118588000f4c8e2d7d717 337 21 2024-06-04T02:35:07Z Electron271 3 Chore: Update directory with new pages wikitext text/x-wiki ==== Welcome to the All Things Linux wiki! ==== The wiki is still being developed and setup, in the meantime chat about Linux at https://discord.gg/linux! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms]] ==== Terminology ==== * [[Command]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] c94611d9a5f01d5d2447bcc7036871a9b0b5adc7 340 337 2024-06-04T02:52:21Z Electron271 3 Chore: Update directory with new pages wikitext text/x-wiki ==== Welcome to the All Things Linux wiki! ==== The wiki is still being developed and setup, in the meantime chat about Linux at https://discord.gg/linux! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms]] ==== Terminology ==== * [[Command]] * [[Bloat]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] 7c2f9b5ab3dd6d8cedbf08835dc45e88ea9869d3 0 2 4 2024-06-03T22:47:36Z Electron271 3 Create a bare bones "Arch Linux", more to come very soon. wikitext text/x-wiki '''Arch Linux''' is a [[Linux]] distribution focused on the KISS (Keep It Simple, Stupid)<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. b0007fb537c2390c05ea73515ec4d0daaecc8b9a 5 4 2024-06-03T22:53:03Z Electron271 3 formatting changes wikitext text/x-wiki '''Arch Linux''' is a [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. 8bd49756f28d685cbf81a2e9e38f0ddb7c92f5db 331 5 2024-06-04T02:18:23Z Electron271 3 add infobox wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} '''Arch Linux''' is a [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. 815dde5157b28f0dfa53f698dc59fb859f775414 339 331 2024-06-04T02:46:37Z Electron271 3 added trivia category wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} '''Arch Linux''' is a [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> 4a085b6165b94664020f10ff4ca21ba2a1d0a528 342 339 2024-06-04T03:16:41Z Asiliria 7 brb!! wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} '''Arch Linux''' is a [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> b1ad457c45a52810166207626213ea0464ec7bf4 2 3 6 2024-06-03T22:55:32Z Amadaluzia 52 made a bio wikitext text/x-wiki Big Lain Fan e348cdaf7baa995109cd0d731358c740697d9f60 1 4 8 2024-06-03T23:18:59Z MediaBoomer 5 /* Suggested Pages */ new section wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; What is Linux anyways? -TLDR of what Linux is -Major differences between Linux and other OS -Key Terms (DE/WM, PM, GIT, Kernel, Distro, Etc.) Guide to Getting Started -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros Maintaining your system -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance Online and Linux Safety and Security -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations Cool sites that may be relevant for users to check out -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] Feel Free and Encouraged to contribute more ideas! [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) 819b330cbdbefce18c9005929993fe0159f352a6 9 8 2024-06-03T23:19:46Z MediaBoomer 5 /* Suggested Pages */ wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -Key Terms (DE/WM, PM, GIT, Kernel, Distro, Etc.) '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance ''' Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations ''' Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] Feel Free and Encouraged to contribute more ideas! [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) 9aab16ddf81037fa1cbcc4df78bca8c956006590 10 9 2024-06-03T23:20:18Z MediaBoomer 5 /* Suggested Pages */ wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -Key Terms (DE/WM, PM, GIT, Kernel, Distro, Etc.) '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) 65f974ebd594e0eec9b6a0de2c62ee41e25bb335 12 10 2024-06-03T23:38:09Z Electron271 3 /* organization idea */ new section wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -Key Terms (DE/WM, PM, GIT, Kernel, Distro, Etc.) '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) 0f659785292c15a2176c4e3532db17fbc8b93851 13 12 2024-06-03T23:40:58Z Asiliria 7 /* organization idea */ Reply wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -Key Terms (DE/WM, PM, GIT, Kernel, Distro, Etc.) '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) :I like the outline! I agree with Electron about organization and it applies to all of the categories - before writing these, we should have a general idea of ''all'' our subcategories [[User:Asiliria|Asiliria]] ([[User talk:Asiliria|talk]]) 23:40, 3 June 2024 (UTC) 1c345343d70c906558f477893853cd1fb0de4b9a 22 13 2024-06-04T00:20:50Z MediaBoomer 5 /* Suggested Pages */ wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -Key Terms (DE/WM, PM, GIT, Kernel, Distro, Etc.) '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Pros and Cons between package formats -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) :I like the outline! I agree with Electron about organization and it applies to all of the categories - before writing these, we should have a general idea of ''all'' our subcategories [[User:Asiliria|Asiliria]] ([[User talk:Asiliria|talk]]) 23:40, 3 June 2024 (UTC) ae1977c20248415013dfd2f08d9706d3f4ce61f9 318 22 2024-06-04T01:35:00Z MediaBoomer 5 wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -[[Key Terms]] '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Pros and Cons between package formats -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) :I like the outline! I agree with Electron about organization and it applies to all of the categories - before writing these, we should have a general idea of ''all'' our subcategories [[User:Asiliria|Asiliria]] ([[User talk:Asiliria|talk]]) 23:40, 3 June 2024 (UTC) eb6881d4949ad04fdd3b6438012add894cc043f9 2 5 11 2024-06-03T23:28:36Z MediaBoomer 5 Autobio added wikitext text/x-wiki MediaBoomer is a hobbyist sysadmin in their spare time who loves to excersize his passion for linux and the community around it. They've been a part of the community for a few years who can't get too excited to bring in new people into the wonderful world of open source. 18bdb5592963ca556296d733cb7cda9546154f7f 0 8 18 2024-06-04T00:12:57Z MediaBoomer 5 Created page with "When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of many of these terms and their TLDR; * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[QT]] * [[GTK]] * [[Package Manager]] * [[Git]] * [[GitHub]] * [[Repo / Repository]] * [[Kernel]] * [[Package]] * [[Program]] * [[App]] * [[Script]] * [[CLI]]..." wikitext text/x-wiki When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of many of these terms and their TLDR; * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[QT]] * [[GTK]] * [[Package Manager]] * [[Git]] * [[GitHub]] * [[Repo / Repository]] * [[Kernel]] * [[Package]] * [[Program]] * [[App]] * [[Script]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Drivers]] * [[Kernel Module]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[FOSS / FLOSS]] * [[Open Source]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] * [[ddos]] * [[phishing]] * [[Malware]] * [[Spyware]] * [[Virus]] * [[Privacy]] * [[Ownership]] * [[Security]] * __INDEX__ __NEWSECTIONLINK__ f49305f28bb3c6456f3f18bcd6982fbf092099f5 19 18 2024-06-04T00:14:16Z MediaBoomer 5 Intro revision wikitext text/x-wiki When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of some of the terms that a new user might actually want to know * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[QT]] * [[GTK]] * [[Package Manager]] * [[Git]] * [[GitHub]] * [[Repo / Repository]] * [[Kernel]] * [[Package]] * [[Program]] * [[App]] * [[Script]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Drivers]] * [[Kernel Module]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[FOSS / FLOSS]] * [[Open Source]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] * [[ddos]] * [[phishing]] * [[Malware]] * [[Spyware]] * [[Virus]] * [[Privacy]] * [[Ownership]] * [[Security]] * __INDEX__ __NEWSECTIONLINK__ 276d3807d93e489ef6e3387a22bd58e9c2ab5cc7 20 19 2024-06-04T00:17:34Z Electron271 3 /* unnecessary terms */ new section wikitext text/x-wiki When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of some of the terms that a new user might actually want to know * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[QT]] * [[GTK]] * [[Package Manager]] * [[Git]] * [[GitHub]] * [[Repo / Repository]] * [[Kernel]] * [[Package]] * [[Program]] * [[App]] * [[Script]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Drivers]] * [[Kernel Module]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[FOSS / FLOSS]] * [[Open Source]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] * [[ddos]] * [[phishing]] * [[Malware]] * [[Spyware]] * [[Virus]] * [[Privacy]] * [[Ownership]] * [[Security]] * __INDEX__ __NEWSECTIONLINK__ == unnecessary terms == hacking, ddos, phishing, malware, spyware, virus do not need to be on this list, and more likely all of these are dead links and i do not see every single one here getting one, a solution to that should idealy be found [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 00:17, 4 June 2024 (UTC) c37bf48cea7edaa0daecd335f36bcf98c2901bce 23 20 2024-06-04T00:24:02Z MediaBoomer 5 Seperating potentially confusing and very common key terms wikitext text/x-wiki When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of some of the terms that a new user might actually want to know * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[Package Manager]] * [[Repo / Repository]] * [[Script]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[FOSS / FLOSS]] * [[Open Source]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid overloading new users, We thought it best to seperate some of the more complicated topics that most new users wont need to learn about unless they are trying to do something specific. Here are some of those terms; * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ f86a66e92612e12a6bb9457baf3de407cf89bfe9 60 23 2024-06-04T00:58:32Z MediaBoomer 5 Added 'command' wikitext text/x-wiki When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of some of the terms that a new user might actually want to know * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[Package Manager]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[FOSS / FLOSS]] * [[Open Source]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid overloading new users, We thought it best to seperate some of the more complicated topics that most new users wont need to learn about unless they are trying to do something specific. Here are some of those terms; * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ ec474da33f5f164ad3ed3cb5595d5c0a36066065 325 60 2024-06-04T01:55:07Z MediaBoomer 5 bloat added wikitext text/x-wiki When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of some of the terms that a new user might actually want to know * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[Package Manager]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[bloat]] * [[FOSS / FLOSS]] * [[Open Source]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid overloading new users, We thought it best to seperate some of the more complicated topics that most new users wont need to learn about unless they are trying to do something specific. Here are some of those terms; * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ c5f0c4426a3053fec942ac522e9b8595612344fa 326 325 2024-06-04T01:56:22Z MediaBoomer 5 fixed caps wikitext text/x-wiki When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of some of the terms that a new user might actually want to know * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[Package Manager]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Bloat]] * [[FOSS / FLOSS]] * [[Open Source]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid overloading new users, We thought it best to seperate some of the more complicated topics that most new users wont need to learn about unless they are trying to do something specific. Here are some of those terms; * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ 371b27cb2cac3c8a0abbbf37b92548bbc14ec42c 327 326 2024-06-04T01:57:42Z Eternal 10 wikitext text/x-wiki When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of some of the terms that a new user might actually want to know * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[Package Manager]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Bloat]] * [[FOSS / FLOSS]] * [[Open Source]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid overloading new users, We thought it best to seperate some of the more complicated topics that most new users wont need to learn about unless they are trying to do something specific. Here are some of those terms; * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Ricing]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ e15ceeef4a4bc76e87d81a6c62e2843be9d134a6 328 327 2024-06-04T01:59:02Z Eternal 10 wikitext text/x-wiki When a new user starts diving into the world of Linux and open source as a whole, They will no doubt be bombarded with loads of Key Terms that sound foreign and confusing. Here is a quick compilation of some of the terms that a new user might actually want to know * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[Package Manager]] * [[Ricing]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Bloat]] * [[FOSS / FLOSS]] * [[Open Source]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid overloading new users, We thought it best to seperate some of the more complicated topics that most new users wont need to learn about unless they are trying to do something specific. Here are some of those terms; * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ acc4e03d78e808b92a974fb738694de362a56e5a 334 328 2024-06-04T02:25:41Z Asiliria 7 formality (please be more formal!) wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different categories that a new user should learn about upon interacting with Linux for the first time. * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[Package Manager]] * [[Ricing]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Bloat]] * [[FOSS / FLOSS]] * [[Open Source]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ 38cc4ad17ce584177c240c3f7d2c37d18b71a76e 6 9 24 2024-06-04T00:40:03Z Electron271 3 logo wikitext text/x-wiki == Summary == logo 556d0d26de95834fcb4079a22fddb56281d62907 0 158 317 2024-06-04T01:32:42Z MediaBoomer 5 Authored description wikitext text/x-wiki When using [[Linux]], sooner or later, there's a good chance you'll end finding yourself in front of a [[Terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a 'Command'. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include "[[fastfetch]]", "[[nano]]", "[[cat]]", etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with "sudo" followed with your original command. [[sudo]] Tells your computer to 'do' something as a 'super user' which will allow you to bypass restrictions. Furthermore, with commands you will likely need to include "options" that specify to the program how you want it to behave. One of the most common options is "--help", which will usually tell program to list all of its options. An example would be as follows cat --help In this case, the 'cat' utility would respond to this command with the following:<blockquote>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines............</blockquote>(Shortened to maintain focus on topic) These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, "--help" is always there and ready. If --help isnt enough, you can always run "[[man]]" before a program similarly to how you would run "[[sudo]]", and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a File to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory]] (Like shown) or you can provide a file from anywhere in the [[Filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt You will notice that I started describing the file location, I used the tilda sign "~". In linux and some other OS, The Tilda is a faster way to describe the users home folder. It is effectively the same thing as typing the full [[directory path]] except that it is much faster. Here is what it would look like to type the whole directory path nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ 84d760a1da54c692b40b3b9342e340e7814f6d98 10 162 329 2024-06-04T02:14:29Z Electron271 3 Created page with "<includeonly>{{#invoke:DistributionInfobox|main}}</includeonly>" wikitext text/x-wiki <includeonly>{{#invoke:DistributionInfobox|main}}</includeonly> c0062dc2777e2aa5baed0993cacecaae4b6c8e14 828 163 330 2024-06-04T02:14:30Z Electron271 3 Created page with "local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) :addImage( args.image, args.caption ) :addRow( 'Release Status', args.rele..." Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) :addImage( args.image, args.caption ) :addRow( 'Release Status', args.releasestatus ) :addRow( 'Update Method', args.updatemethod ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Website', args.website ) return retval end return p 3efd1984dd830a811c1119936e4746b3e2c7886a 0 164 332 2024-06-04T02:18:53Z MediaBoomer 5 Created page with "The Linux community is filled to the brim with awesome projects and various other guides worth checking out, Here's some great ones that we've found! * https://www.privacyguides.org/ * https://alternativeto.net * https://awesome-privacy.xyz * https://christitus.com/windows-tool/ * https://brainfucksec.github.io/firefox-hardening-guide" wikitext text/x-wiki The Linux community is filled to the brim with awesome projects and various other guides worth checking out, Here's some great ones that we've found! * https://www.privacyguides.org/ * https://alternativeto.net * https://awesome-privacy.xyz * https://christitus.com/windows-tool/ * https://brainfucksec.github.io/firefox-hardening-guide 0d69d75ba0a2b334cec5505d24ebdcb80470e3d1 0 166 336 2024-06-04T02:34:08Z Asiliria 7 Creation and basis wikitext text/x-wiki A term commonly used across any Linux community [SOURCE needed], "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life. <ref>[https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of Linux and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system. [SOURCE needed] fd2fd719175b50f63e7eb40cf1051731930f7401 338 336 2024-06-04T02:35:14Z Asiliria 7 citation title - whoops wikitext text/x-wiki A term commonly used across any Linux community [SOURCE needed], "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life. <ref>Merriam-Webster Dictionary. [https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of Linux and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system. [SOURCE needed] 0bb495663e7a3372acc5bddb03f11abad0e1b7ed 0 169 344 2024-06-04T03:29:31Z Asiliria 7 for later reference wikitext text/x-wiki Package managers refer to..... d2764ff79669606af87250545ee681db20b45bab 0 1 345 340 2024-06-04T03:29:59Z Electron271 3 update main page wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms]] ==== Terminology ==== * [[Command]] * [[Bloat]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' e88d87e5c2f1ae9d5980ab816b6bbcb23421d7f0 356 345 2024-06-04T04:00:12Z Electron271 3 Removed protection from "[[Main Page]]": unlock temporarily, change tmr wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms]] ==== Terminology ==== * [[Command]] * [[Bloat]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' e88d87e5c2f1ae9d5980ab816b6bbcb23421d7f0 359 356 2024-06-04T04:07:22Z Asiliria 7 Change to nomenclature... big brain time wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms|Nomenclature]] ==== Terminology ==== * [[Command]] * [[Bloat]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' c765ae01dbc12cabdb1a70c672ddb98c20dbc757 360 359 2024-06-04T04:07:57Z Asiliria 7 getting even larger brain wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms|Terminology and Nomenclature]] ==== Terminology ==== * [[Command]] * [[Bloat]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 057673af63461102550a026e4c3fb38cbda7724d 364 360 2024-06-04T04:23:37Z Asiliria 7 Adding a very important guide...! wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms|Terminology and Nomenclature]] * [[Common Issues and Troubleshooting]] ==== Terminology ==== * [[Command]] * [[Bloat]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' af64ca87d443234181a9f76730e4676c291b736b 367 364 2024-06-04T04:30:29Z Asiliria 7 Added NixOS! wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] * [[NixOS]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms|Terminology and Nomenclature]] * [[Common Issues and Troubleshooting]] ==== Terminology ==== * [[Command]] * [[Bloat]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 15112b814a401f2dc05745c25cfe712bd7118cdd 373 367 2024-06-04T13:39:26Z Add Debian to distro list wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] * [[NixOS]] * [[Debian]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms|Terminology and Nomenclature]] * [[Common Issues and Troubleshooting]] ==== Terminology ==== * [[Command]] * [[Bloat]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' fa5a24a3af9ccbdf5a3e81e7faa62a1f12cbc086 374 373 2024-06-04T13:39:58Z Respect alphabetical order - oops. wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == ==== Linux Distributions ==== * [[Arch Linux]] * [[Debian]] * [[NixOS]] ==== Guides ==== * [[Choosing A Linux Distribution]] * [[Key Terms|Terminology and Nomenclature]] * [[Common Issues and Troubleshooting]] ==== Terminology ==== * [[Command]] * [[Bloat]] ==== Miscellaneous ==== * [[Main Page]] * [[External Resources]] '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 3b346d9c729b465b4f28b0df72e0c5fd38bc55ec 403 374 2024-06-04T16:17:11Z Electron271 3 remove directory and add wikibot tags wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 82851938bf6ef93d5e50abe113d58feac6c18647 406 403 2024-06-04T16:52:34Z Tux 1 wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the All Things Linux Discord server! Check the server out if you need any support! == Directory == please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough 992b13fbd7a98507e72ae937084d541c670c1905 407 406 2024-06-04T16:53:03Z Electron271 3 Reverted edit by [[Special:Contributions/WikiBot|WikiBot]] ([[User talk:WikiBot|talk]]) to last revision by [[User:Electron271|Electron271]] wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 82851938bf6ef93d5e50abe113d58feac6c18647 408 407 2024-06-04T16:56:55Z Tux 1 wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough'''''==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> === Linux Distributions === * [[Arch Linux]] * [[Debian]] === Misc === * [[Bloat]] * [[Choosing A Linux Distribution]] * [[Command]] * [[Common Issues and Troubleshooting]] * [[Display Manager]] * [[External Resources]] * [[FOSS / FLOSS]] * [[KDE]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' aec6db41e0eab4a30f58ab2c77934f8e9543eeb1 409 408 2024-06-04T16:57:28Z Electron271 3 Reverted edit by [[Special:Contributions/WikiBot|WikiBot]] ([[User talk:WikiBot|talk]]) to last revision by [[User:Electron271|Electron271]] wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 82851938bf6ef93d5e50abe113d58feac6c18647 410 409 2024-06-04T16:58:01Z Tux 1 wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> === Linux Distributions === * [[Arch Linux]] * [[Debian]] === Misc === * [[Bloat]] * [[Choosing A Linux Distribution]] * [[Command]] * [[Common Issues and Troubleshooting]] * [[Display Manager]] * [[External Resources]] * [[FOSS / FLOSS]] * [[KDE]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 1fc58e53d3ee73c295e73bedb1a735938f8c211f 411 410 2024-06-04T16:58:56Z Tux 1 wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 6c8098ac1fda9aa0210f27e00752063e23979346 412 411 2024-06-04T16:59:35Z Electron271 3 Reverted edits by [[Special:Contributions/WikiBot|WikiBot]] ([[User talk:WikiBot|talk]]) to last revision by [[User:Electron271|Electron271]] wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 82851938bf6ef93d5e50abe113d58feac6c18647 0 2 347 342 2024-06-04T03:40:14Z Asiliria 7 new sections, "functionality" details, word choice, extra revisions wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its package manager<ref>[[package manager]]</ref> called ''pacman.'' Its main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> When using pacman, there are several repositories (awk, rephrase): * [core], housing all of the packages necessary for a base Arch installation to function; * [extra], housing applications and tooling that is not necessary for the system to function but serves instead for user-defined needs; * [multilib], housing 32-bit architecture libraries centered around legacy or compatibility concerns; ** [-testing], housing versions of these repositories that are under active development and are often very unstable; * the '''AUR''' (''Arch User Repository''), housing community-maintained, unofficial builds of software aimed at either convenience or specific use-cases; ** custom user repositories, housing specific software outside of the AUR and official repositories. <ref>Arch Linux Wiki - Official Repositories[https://wiki.archlinux.org/title/Official_repositories]</ref><ref>Arch Linux Wiki - Unofficial User Repositories[https://wiki.archlinux.org/title/Unofficial_repositories]</ref> === Philosophy === ... === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> a74ee667a62cf14740421b40faf389fda6bcb599 355 347 2024-06-04T03:56:45Z Asiliria 7 did that work? - pacman link wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Its main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> Pacman uses different repositories to store its packages: * [core], housing all of the packages necessary for a base Arch installation to function; * [extra], housing applications and tooling that is not necessary for the system to function but serves instead for user-defined needs; * [multilib], housing 32-bit architecture libraries centered around legacy or compatibility concerns; ** [-testing], housing versions of these repositories that are under active development and are often very unstable; * the '''AUR''' (''Arch User Repository''), housing community-maintained, unofficial builds of software aimed at either convenience or specific use-cases; ** custom user repositories, housing specific software outside of the AUR and official repositories. <ref>Arch Linux Wiki - Official Repositories[https://wiki.archlinux.org/title/Official_repositories]</ref><ref>Arch Linux Wiki - Unofficial User Repositories[https://wiki.archlinux.org/title/Unofficial_repositories]</ref> === Philosophy === ... === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> c186572a43e67e00f5fb92b1e9a6c59f8215fa83 393 355 2024-06-04T14:55:08Z Electron271 3 update testing repo section and add staging wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Its main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> Pacman uses different repositories to store its packages: * [core], housing all of the packages necessary for a base Arch installation to function; * [extra], housing applications and tooling that is not necessary for the system to function but serves instead for user-defined needs; * [multilib], housing 32-bit architecture libraries centered around legacy or compatibility concerns; ** [-testing], housing testing versions of the other repos that people from the Arch Testing Team<ref>https://wiki.archlinux.org/title/Arch_Testing_Team</ref> test before it gets into the main repos; ** [-staging], containing broken packages and is used solely by developers for rebuilding many packages at once; <ref>https://wiki.archlinux.org/title/official_repositories#Staging_repositories</ref> * the '''AUR''' (''Arch User Repository''), housing community-maintained, unofficial builds of software aimed at either convenience or specific use-cases; ** custom user repositories, housing specific software outside of the AUR and official repositories. <ref>Arch Linux Wiki - Official Repositories[https://wiki.archlinux.org/title/Official_repositories]</ref><ref>Arch Linux Wiki - Unofficial User Repositories[https://wiki.archlinux.org/title/Unofficial_repositories]</ref> === Philosophy === ... === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> 663fad4ff79a9142f4fde0c0a1bf82423a31e48f 399 393 2024-06-04T16:03:37Z Electron271 3 Chore: Update categories wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Its main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> Pacman uses different repositories to store its packages: * [core], housing all of the packages necessary for a base Arch installation to function; * [extra], housing applications and tooling that is not necessary for the system to function but serves instead for user-defined needs; * [multilib], housing 32-bit architecture libraries centered around legacy or compatibility concerns; ** [-testing], housing testing versions of the other repos that people from the Arch Testing Team<ref>https://wiki.archlinux.org/title/Arch_Testing_Team</ref> test before it gets into the main repos; ** [-staging], containing broken packages and is used solely by developers for rebuilding many packages at once; <ref>https://wiki.archlinux.org/title/official_repositories#Staging_repositories</ref> * the '''AUR''' (''Arch User Repository''), housing community-maintained, unofficial builds of software aimed at either convenience or specific use-cases; ** custom user repositories, housing specific software outside of the AUR and official repositories. <ref>Arch Linux Wiki - Official Repositories[https://wiki.archlinux.org/title/Official_repositories]</ref><ref>Arch Linux Wiki - Unofficial User Repositories[https://wiki.archlinux.org/title/Unofficial_repositories]</ref> === Philosophy === ... === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 948644f6c7e5c047110834adbed294f7c8f8cfbc 0 8 348 334 2024-06-04T03:41:28Z Asiliria 7 Added hyperlink to Package Managers that I created earlier wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different categories that a new user should learn about upon interacting with Linux for the first time. * [[Linux]] * [[Distro]] * [[DE / WM]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[Package manager|Package Manager]] * [[Ricing]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Bloat]] * [[FOSS / FLOSS]] * [[Open Source]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ 6df6fbc34de1225d82bf11987b2868837d8ef899 352 348 2024-06-04T03:52:07Z Asiliria 7 Added Display Managers wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different categories that a new user should learn about upon interacting with Linux for the first time. * [[Linux]] * [[Distro]] * [[DE / WM]] * [[Display Manager]] * [[KDE|KDE / Plasma]] * [[Gnome]] * [[Package manager|Package Manager]] * [[Ricing]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Bloat]] * [[FOSS / FLOSS]] * [[Open Source]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ 99b96754aaa79d8dadee438ec6bec29f30228220 357 352 2024-06-04T04:00:22Z Asiliria 7 Small de-abbreviations wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different categories that a new user should learn about upon interacting with Linux for the first time. * [[Linux]] * [[Distro]] * [[DE / WM|Desktop Environments and Window Managers]] * [[Display Manager]] * [[KDE|KDE / Plasma]] * [[Gnome|GNOME]] * [[Package manager|Package Manager]] * [[Ricing]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI]] * [[TUI]] * [[GUI]] * [[Drivers]] * [[Flatpak]] * [[Tar.xz / Tarball]] * [[AppImage]] * [[Snap]] * [[Bloat]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] * [[Compiling]] * [[Building]] * [[License]] * [[GPL / GPLv3]] * [[GNU]] * [[Hacking]] * [[apt]] * [[pacman]] * [[zypper]] * [[dnf]] * [[rpm]] __INDEX__ __NEWSECTIONLINK__ 4be5039d4be6c6f7e1f91913f8d3fb7057d155e8 362 357 2024-06-04T04:15:10Z Asiliria 7 lots of formatting, de-abbreviation, some potential ideas and notes for others wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Linux]] * [[Distro]] * [[DE / WM|Desktop Environments and Window Managers]] * [[Display Manager]] * [[KDE|KDE / Plasma]] * [[Gnome|GNOME]] * [[Package manager|Package Manager]] ** [[apt|''apt'']] ** [[pacman|''pacman'']] ** [[zypper|''zypper'']] ** [[dnf|''dnf'']] ** [[rpm|''rpm'']] ** [[Apk|''apk'']] ** [[Nixpkgs|''nixpkgs'']] * [[Ricing|Theming / "Ricing"]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI|Command-Line Interface (CLI)]] * [[TUI|Text-Based User Interface (TUI)]] * [[GUI|Graphical User Interface (GUI)]] * [[Drivers]] * [[Flatpak]] * [[tar.xz / Tarball]] - broaden to file compression? * [[AppImage]] * [[Snap]] * [[Bloat]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] - all three of the X's in one place? All in compositor, even? * [[Compiling]] * [[Building]] * [[License]] - put GPL in here? * [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[GNU]] - same place as GPL? * [[Hacking]] __INDEX__ __NEWSECTIONLINK__ 31196fedd79fdfa7b58fdbc48a756a651368c02a 371 362 2024-06-04T13:36:58Z Atmois 13 Indented KDE Plamsa & GNOME under DE & WM wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Linux]] * [[Distro]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[KDE|KDE Plasma]] ** [[Gnome|GNOME]] * [[Display Manager]] * [[Package manager|Package Manager]] ** [[apt|''apt'']] ** [[pacman|''pacman'']] ** [[zypper|''zypper'']] ** [[dnf|''dnf'']] ** [[rpm|''rpm'']] ** [[Apk|''apk'']] ** [[Nixpkgs|''nixpkgs'']] * [[Ricing|Theming / "Ricing"]] * [[Repo / Repository]] * [[Script]] * [[Command]] * [[Package]] * [[Program]] * [[CLI|Command-Line Interface (CLI)]] * [[TUI|Text-Based User Interface (TUI)]] * [[GUI|Graphical User Interface (GUI)]] * [[Drivers]] * [[Flatpak]] * [[tar.xz / Tarball]] - broaden to file compression? * [[AppImage]] * [[Snap]] * [[Bloat]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[Privacy]] * [[Ownership]] * [[Security]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Git]] * [[GitHub]] * [[Kernel]] * [[Bash]] * [[Shell]] * [[TTY]] * [[Kernel Module]] * [[Compositor]] * [[Wayland]] * [[XOrg|Xorg]] * [[X11]] * [[Xwayland]] - all three of the X's in one place? All in compositor, even? * [[Compiling]] * [[Building]] * [[License]] - put GPL in here? * [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[GNU]] - same place as GPL? * [[Hacking]] __INDEX__ __NEWSECTIONLINK__ 82bee5f452b9d8ef8286c3e196a3bf2351f6531f 386 371 2024-06-04T13:50:33Z Atmois 13 Alphabetise entries wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE|KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Nixpkgs|''nixpkgs'']] * [[Package]] * [[Package Manager]] ** [[apt|''apt'']] ** [[Apk|''apk'']] ** [[dnf|''dnf'']] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Program]] * [[Privacy]] * [[Repo / Repository]] * [[Ricing|Theming / "Ricing"]] * [[Script]] * [[Security]] * [[TUI|Text-Based User Interface (TUI)]] * [[tar.xz / Tarball]] - broaden to file compression? * [[Theming / "Ricing"|Ricing]] * [[Ownership]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Bash]] * [[Building]] * [[Compositor]] * [[Compiling]] * [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Git]] * [[GNU]] - same place as GPL? * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[License]] * [[Shell]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] - all three of the X's in one place? All in compositor, even? * [[GitHub]] __INDEX__ __NEWSECTIONLINK__ ec563daf83bf21f52342dc04fddd3f4824c59e8a 0 171 349 2024-06-04T03:46:53Z Eternal 10 Created page with "{{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration..." wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. b78dd927624884b4c148afb89868980db1037b87 389 349 2024-06-04T13:52:29Z Electron271 3 wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra.{{Citation needed}} === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. f69b8ab0255b05bf2213d9354e9156b332aea22c 2 172 350 2024-06-04T03:48:53Z Eternal 10 Created page with "== Hi i'm Eternal! == === Stuff about me === * Junior Web Dev / Hardware Tinkerer * Rust, Nix and Lua enjoyer * NixOS & Arch user * Wannabe Artist & Portal Test Subject" wikitext text/x-wiki == Hi i'm Eternal! == === Stuff about me === * Junior Web Dev / Hardware Tinkerer * Rust, Nix and Lua enjoyer * NixOS & Arch user * Wannabe Artist & Portal Test Subject 8e960de721445441ab7b338583edb38117a6c3fd 0 173 351 2024-06-04T03:50:05Z Asiliria 7 creating for reference, putting on terms wikitext text/x-wiki A Display Manager is... [created for linking and reference] 4125149f97e2185aa95ca837e5843a528cd043d6 0 174 353 2024-06-04T03:55:35Z Asiliria 7 Demoing the TUI page for later wikitext text/x-wiki A '''TUI''' (Text-based User Interface) generally refers to an application that solely exists within the terminal as a text-based application - this means that all of its content is rendered using letters and other unique characters to create a graphical interface. [REFERENCE POSSIBLE] Because of its independence from a ... , a8f748549d84ee0370e3a373e6d2bf4767197070 0 175 354 2024-06-04T03:56:05Z Asiliria 7 creating pacman page wikitext text/x-wiki In Arch Linux, Pacman is... c91601b251f68e61caac7e1087910dd756010819 0 176 358 2024-06-04T04:06:29Z Asiliria 7 Starting KDE page - potential room for an infobox wikitext text/x-wiki KDE is a popular [CITATION NEEDED, distrowatch?] Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> 78dd062816b02538af9bfc6932f6d00fcd2d2fc9 369 358 2024-06-04T13:06:17Z Electron271 3 add source for popular wikitext text/x-wiki KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> 88545d5328618077921211a9b9c7de7785c9dc86 0 177 361 2024-06-04T04:09:57Z Asiliria 7 Creating this so there's some sense of clarity/no confusion in terms to foss/floss wikitext text/x-wiki Free and Open Source Software, as well as its libre variants... 1d0fe0b4553c373239bcf842e53d3401bf9bfbe0 0 178 363 2024-06-04T04:19:03Z Asiliria 7 First citations and progress! wikitext text/x-wiki Linux in itself refers to two entities, the former being the kernel itself developed by Linus Torvalds and the latter being the families of Operating Systems that derive from it therein. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> (infobox potential) 9bf7ee41578d46a6052058bb9500891904611538 0 179 365 2024-06-04T04:27:25Z Asiliria 7 Added this page, as well as something very important - debugging and getting AI to work on Linux! wikitext text/x-wiki Not every install will be as flawless as a user will expect it to be, as they may encounter bugs for several potential reasons. There are numerous reasons why, ranging from simple hardware differences to past kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) * [[Artificial Intelligence on Linux]] ** [[w-okada]] (it's not very well documented and, while testing out of curiosity for Linux compatibility, I made some discoveries) c4178310d9f039bcdd74369e92b28ac87f315955 366 365 2024-06-04T04:28:13Z Asiliria 7 Revision for concision - awk wikitext text/x-wiki Not every install will be as flawless as a user will expect it to be, and they may encounter bugs for numerous reasons ranging from simple hardware differences to nuanced kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) * [[Artificial Intelligence on Linux]] ** [[w-okada]] (it's not very well documented and, while testing out of curiosity for Linux compatibility, I made some discoveries) eecf03a3094c72f6c74cebf9d41f2d7a224c6eab 0 182 372 2024-06-04T13:38:55Z Create a "Debian" page - more updates to come. wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Long-term support in Stable edition, rolling release in Testing (Trixie) and Unstable (Sid) editions | packagemanager = [[dpkg]] | usagetype = Desktop, server | website = [https://www.debian.org/ debian.org] }} '''Debian''' (/ˈdɛbiən/)<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref>, also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref>. a03c963f7270e4d41013f4649f62ac14a04d58ad 390 372 2024-06-04T13:56:48Z Add more information about Debian's relationship with the FSF and nonprofits. wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Long-term support in Stable edition, rolling release in Testing (Trixie) and Unstable (Sid) editions | packagemanager = [[dpkg]] | usagetype = Desktop, server | website = [https://www.debian.org/ debian.org] }} '''Debian''' (/ˈdɛbiən/)<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref>, also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref>. Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref>. However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref>. In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. c43b7e8b2db49fefb36fffafc560e8b687779621 391 390 2024-06-04T13:57:36Z Add Debian history and release freeze info. wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Long-term support in Stable edition, rolling release in Testing (Trixie) and Unstable (Sid) editions | packagemanager = [[dpkg]] | usagetype = Desktop, server | website = [https://www.debian.org/ debian.org] }} '''Debian''' (/ˈdɛbiən/)<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref>, also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref>. Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref>. However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref>. In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. 7c4dbc869dd0c67e72fa7dc135d8c3e13f0e3c27 392 391 2024-06-04T14:01:21Z Electron271 3 unify infobox wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[dpkg]] | usagetype = Desktop, Server | website = [https://www.debian.org/ debian.org] }} '''Debian''' (/ˈdɛbiən/)<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref>, also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref>. Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref>. However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref>. In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. 74a0de5a22d91612c9731ef88a538183c3f9cd78 402 392 2024-06-04T16:16:38Z Electron271 3 Chore: Update categories wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[dpkg]] | usagetype = Desktop, Server | website = [https://www.debian.org/ debian.org] }} '''Debian''' (/ˈdɛbiən/)<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref>, also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref>. Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref>. However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref>. In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. <references /> [[Category:Linux Distributions]] c8b5997e5c0e3710ad26d9432725c6b2e6ef4716 10 187 383 2024-06-04T13:44:48Z Electron271 3 citation needed wikitext text/x-wiki {{ {{{|safesubst:}}}#invoke:Unsubst||date=__DATE__ |$B= {{Fix |name={{{name|Citation needed}}} |link=Wikipedia:Citation needed |text=citation needed |class=Template-Fact |title={{{reason|This claim needs references to reliable sources.}}} |date={{{date|}}} |cat=[[Category:All articles with unsourced statements]] |cat-date=Category:Articles with unsourced statements }}{{#if:{{{1|}}}|[[Category:Pages containing citation needed template with deprecated parameters]]}} }}<noinclude> 7514cc5ddd756dc48d598a9b30b103677239bd40 384 383 2024-06-04T13:49:59Z Electron271 3 wikitext text/x-wiki <noinclude> ^{[citation needed]} </noinclude> 27096e4462b6ac7074965f020a3a1a806989e4a7 387 384 2024-06-04T13:50:37Z Electron271 3 wikitext text/x-wiki ^{[citation needed]} 9939198ca9bb948c334a4bcae50831352785f686 1 4 385 318 2024-06-04T13:50:21Z Kaizen 4 /* Suggested Pages */ Reply wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -[[Key Terms]] '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Pros and Cons between package formats -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) :Maybe most important commands to know "primer"? See for examples: :https://discord.com/channels/1172245377395728464/1172245377395728467/1237386711055601714 :https://discord.com/channels/1172245377395728464/1172245377395728467/1237388162440105984 [[User:Kaizen|Kaizen]] ([[User talk:Kaizen|talk]]) 13:50, 4 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) :I like the outline! I agree with Electron about organization and it applies to all of the categories - before writing these, we should have a general idea of ''all'' our subcategories [[User:Asiliria|Asiliria]] ([[User talk:Asiliria|talk]]) 23:40, 3 June 2024 (UTC) 6be19b3634f91e6515e2c2eda53cb0d324ef4727 0 166 388 338 2024-06-04T13:51:43Z Electron271 3 wikitext text/x-wiki A term commonly used across any Linux community{{Citation needed}}, "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life. <ref>Merriam-Webster Dictionary. [https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of Linux and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system.{{Citation needed}} b74684cfae4e52c34b42b81210a2277e959867ae 2 192 404 2024-06-04T16:32:36Z Atmois 13 Create page wikitext text/x-wiki Atmois 2be8128b39d57f4a350a0226d7469da6b1b11e79 405 404 2024-06-04T16:34:58Z Atmois 13 wikitext text/x-wiki Local tech nerd, who listens to ''a lot'' of music. cdb59352b10e4ab9a0185c2d80960c315f02aa1b 0 1 413 412 2024-06-04T16:59:46Z Tux 1 wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> === Linux Distributions === * [[Arch Linux]] * [[Debian]] === Misc === * [[Bloat]] * [[Choosing A Linux Distribution]] * [[Command]] * [[Common Issues and Troubleshooting]] * [[Display Manager]] * [[External Resources]] * [[FOSS / FLOSS]] * [[KDE]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' c12a20bdb6f6336925f41529149edc5214524dc1 414 413 2024-06-04T17:02:40Z Electron271 3 Protected "[[Main Page]]" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> === Linux Distributions === * [[Arch Linux]] * [[Debian]] === Misc === * [[Bloat]] * [[Choosing A Linux Distribution]] * [[Command]] * [[Common Issues and Troubleshooting]] * [[Display Manager]] * [[External Resources]] * [[FOSS / FLOSS]] * [[KDE]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' c12a20bdb6f6336925f41529149edc5214524dc1 418 414 2024-06-04T17:05:11Z Tux 1 WikiBot: update directory wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> === Guides === * [[Choosing A Linux Distribution]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] === Terminology === * [[Bloat]] * [[Command]] === Misc === * [[Common Issues and Troubleshooting]] * [[Display Manager]] * [[External Resources]] * [[FOSS / FLOSS]] * [[KDE]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 5244c1b348b72af7d8f222141eb3b57a10845f67 424 418 2024-06-04T17:06:53Z Tux 1 WikiBot: update directory wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] === Software === * [[KDE]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] === Misc === <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 4178a1583069e7bd518cdd7a497f5a3e8d1d2add 426 424 2024-06-04T17:09:16Z Tux 1 WikiBot: update directory wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! == Directory == <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] * [[NixOS]] === Software === * [[KDE]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] === Misc === * [[Key Terms]] * [[Linux]] * [[Main Page]] * [[Package manager]] * [[Pacman]] * [[TUI]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' ebdcf42f891a349a59a443d1b74bddbadaf58cd2 442 426 2024-06-04T18:26:03Z Electron271 3 wikitext text/x-wiki ==== Welcome to the All Things Linux Wiki! ==== This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] * [[NixOS]] === Software === * [[KDE]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] === Misc === * [[Key Terms]] * [[Linux]] * [[Main Page]] * [[Package manager]] * [[Pacman]] * [[TUI]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' d6c23fe7bd4104244bd2fe18f931b504ef1dc585 443 442 2024-06-04T18:28:16Z Electron271 3 wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] * [[NixOS]] === Software === * [[KDE]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] === Misc === * [[Key Terms]] * [[Linux]] * [[Main Page]] * [[Package manager]] * [[Pacman]] * [[TUI]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 8f621feb740c2f3afda4c8eb1a89f6c00e3b3618 445 443 2024-06-04T18:33:24Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] * [[NixOS]] === Package Managers === * [[Pacman]] === Software === * [[KDE]] * [[Pacman]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] === Misc === * [[Key Terms]] * [[Linux]] * [[Main Page]] * [[Package manager]] * [[TUI]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 9910368fd03a7bf36dfdf8a9acf66e10bc3cc843 451 445 2024-06-04T18:44:48Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] * [[NixOS]] === Package Managers === * [[Pacman]] === Software === * [[KDE]] * [[Pacman]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] === Misc === * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' cf0ded465b80897e9d6ac60e415a284d72a5d9a9 453 451 2024-06-04T18:51:27Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] * [[NixOS]] === Package Managers === * [[Pacman]] === Software === * [[KDE]] * [[Pacman]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] === Misc === * [[Common.js]] * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 77c865a3b9b217cb4f1486c6e7bc25d43af96586 455 453 2024-06-04T18:56:45Z Electron271 3 Chore: Update categories wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] * [[NixOS]] === Package Managers === * [[Pacman]] === Software === * [[KDE]] * [[Pacman]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] === Misc === * [[Common.js]] * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] c87e8cc18b8ff73372678d6a5cabd2e852ea0d09 462 455 2024-06-04T19:07:05Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] * [[NixOS]] === Meta === * [[Main Page]] === Package Managers === * [[Pacman]] === Software === * [[KDE]] * [[Pacman]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] === Misc === <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] d362b0544500b38dbc1a37ec59854ea93ef0d70c 0 166 415 388 2024-06-04T17:03:24Z Electron271 3 Chore: Update categories wikitext text/x-wiki A term commonly used across any Linux community{{Citation needed}}, "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life. <ref>Merriam-Webster Dictionary. [https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of Linux and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system.{{Citation needed}} <references /> [[Category:Terminology]] 2482981a28e56c73fa0a03f824376593255d3c89 0 158 417 317 2024-06-04T17:04:26Z Electron271 3 Chore: Update categories wikitext text/x-wiki When using [[Linux]], sooner or later, there's a good chance you'll end finding yourself in front of a [[Terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a 'Command'. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include "[[fastfetch]]", "[[nano]]", "[[cat]]", etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with "sudo" followed with your original command. [[sudo]] Tells your computer to 'do' something as a 'super user' which will allow you to bypass restrictions. Furthermore, with commands you will likely need to include "options" that specify to the program how you want it to behave. One of the most common options is "--help", which will usually tell program to list all of its options. An example would be as follows cat --help In this case, the 'cat' utility would respond to this command with the following:<blockquote>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines............</blockquote>(Shortened to maintain focus on topic) These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, "--help" is always there and ready. If --help isnt enough, you can always run "[[man]]" before a program similarly to how you would run "[[sudo]]", and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a File to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory]] (Like shown) or you can provide a file from anywhere in the [[Filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt You will notice that I started describing the file location, I used the tilda sign "~". In linux and some other OS, The Tilda is a faster way to describe the users home folder. It is effectively the same thing as typing the full [[directory path]] except that it is much faster. Here is what it would look like to type the whole directory path nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] a2c6e94d08fa95e4fcedf9de0f9838b1fb8bb0bf 0 179 419 366 2024-06-04T17:05:28Z Electron271 3 Chore: Update categories wikitext text/x-wiki Not every install will be as flawless as a user will expect it to be, and they may encounter bugs for numerous reasons ranging from simple hardware differences to nuanced kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) * [[Artificial Intelligence on Linux]] ** [[w-okada]] (it's not very well documented and, while testing out of curiosity for Linux compatibility, I made some discoveries) [[Category:Guides]] f36b962bf59ab980e865af09411d0601d3d8a4fb 427 419 2024-06-04T17:13:00Z Kaizen 4 wikitext text/x-wiki Not every install will be as flawless as a user will expect it to be, and they may encounter bugs for numerous reasons ranging from simple hardware differences to nuanced kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) * [[Artificial Intelligence on Linux]] ** [[w-okada]] (it's not very well documented and, while testing out of curiosity for Linux compatibility, I made some discoveries) Test edit for discord feed. [[Category:Guides]] 5a56d0c5fe481b218929b2db75c32122dd47ec68 0 173 420 351 2024-06-04T17:05:40Z Electron271 3 Chore: Update categories wikitext text/x-wiki A Display Manager is... [created for linking and reference] [[Category:Terminology]] 1dce4d00bba5b24ce43b92d07da486d6a34c4b0a 0 164 421 332 2024-06-04T17:05:57Z Electron271 3 Chore: Update categories wikitext text/x-wiki The Linux community is filled to the brim with awesome projects and various other guides worth checking out, Here's some great ones that we've found! * https://www.privacyguides.org/ * https://alternativeto.net * https://awesome-privacy.xyz * https://christitus.com/windows-tool/ * https://brainfucksec.github.io/firefox-hardening-guide [[Category:Guides]] 3bd16dc61e2fe8b34d8474d58b5f6306c705e90b 440 421 2024-06-04T18:16:59Z Add FMHY guides wikitext text/x-wiki The Linux community is filled to the brim with awesome projects and various other guides worth checking out, Here's some great ones that we've found! * https://www.privacyguides.org/ * https://alternativeto.net * https://awesome-privacy.xyz * https://christitus.com/windows-tool/ * https://brainfucksec.github.io/firefox-hardening-guide * https://rentry.co/fmhy-guides [[Category:Guides]] 15a3f077b28205a41f98d959c72af47ba27026e5 0 177 422 361 2024-06-04T17:06:12Z Electron271 3 Chore: Update categories wikitext text/x-wiki Free and Open Source Software, as well as its libre variants... [[Category:Terminology]] 206d485ca14b58caf4e1149e5bc882c3442452ee 434 422 2024-06-04T17:41:50Z Add actual content to page. wikitext text/x-wiki '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre and Open Source Software (FLOSS), is software that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111.</ref> FOSS is a neutral term that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> [[Category:Terminology]] 758f269e2492b5ac20048340ffc7019cf50a669c 436 434 2024-06-04T17:42:39Z Proper headers. wikitext text/x-wiki '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre and Open Source Software (FLOSS), is software that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111.</ref> FOSS is a neutral term that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> === References === [[Category:Terminology]] 7094c40c52105d6de872ec59694926b56150a852 0 176 423 369 2024-06-04T17:06:39Z Electron271 3 Chore: Update categories wikitext text/x-wiki KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> <references /> [[Category:Software]] [[Category:Desktop Environments]] dfc60c6ccfec39567f117984a03dad75a6f8943b 433 423 2024-06-04T17:29:04Z Add references header wikitext text/x-wiki KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> === References === <references /> [[Category:Software]] [[Category:Desktop Environments]] 82ccd73078ca29897f1395c0fe9b3b1ec254e4c7 457 433 2024-06-04T19:01:37Z wikitext text/x-wiki KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref><references /> [[Category:Software]] [[Category:Desktop Environments]] 37189713e2ec8d2d1308470d8980b3d81ea92a3d 463 457 2024-06-04T19:08:59Z Electron271 3 Chore: Update categories wikitext text/x-wiki KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref><references /> [[Category:Desktop Environments]] 7900f6a8b15243ed1424cdb8911795724370121a 0 171 425 389 2024-06-04T17:08:12Z Electron271 3 Chore: Update categories wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra.{{Citation needed}} === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 1815646701b1c612f3ed6e444d969a9f3b08d61a 432 425 2024-06-04T17:28:16Z Add references header wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra.{{Citation needed}} === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. === References === <references /> [[Category:Linux Distributions]] 124548f01a349768766336e0029def477ebf67cb 441 432 2024-06-04T18:21:27Z Astrid 8 I cited the phd thesis that lead to the creation of nix, and I changed the release model to "varied" wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Varied depending on user configuration | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. === References === <references /> [[Category:Linux Distributions]] 01c555d6c8e6d9ef46232a8918c10947dca80ff9 460 441 2024-06-04T19:02:43Z wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Varied depending on user configuration | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 6ece3c5704568ce35f1df714156b28d3f063c70b 0 8 428 386 2024-06-04T17:20:47Z Atmois 13 Fixed alphabetisation & organised it up wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE|KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[nixpkgs]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Ownership]] * [[Program]] * [[Privacy]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] - broaden to file compression? * [[Ricing|Theming / "Ricing"]] * [[TUI|Text-Based User Interface (TUI)]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] - same place as GPL? * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] - all three of the X's in one place? All in compositor, even? __INDEX__ __NEWSECTIONLINK__ cc29723aec8cd22b0e8a4f6992fd0d841f8dc99d 435 428 2024-06-04T17:42:16Z Atmois 13 Fix alphabetisation again (for the last time) wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE|KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[nixpkgs]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] - broaden to file compression? * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] - same place as GPL? * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] - all three of the X's in one place? All in compositor, even? __INDEX__ __NEWSECTIONLINK__ b940f1025f68b18a9f839ad04090c458ef0a7bc9 437 435 2024-06-04T17:52:10Z Keep questions like these in Discussion wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE|KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[nixpkgs]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] - broaden to file compression? * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] - all three of the X's in one place? All in compositor, even? __INDEX__ __NEWSECTIONLINK__ 08413f43df2162a0df53879da1842903ded70dc5 438 437 2024-06-04T17:54:03Z Missed some. wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE|KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[nixpkgs]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ faa805c9699578336b5f49df61c7be400e74ed24 449 438 2024-06-04T18:38:12Z Electron271 3 Chore: Update categories wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE|KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[nixpkgs]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 59715ff7a65e5b312ce48dc20c7c12e67112ac65 0 182 429 402 2024-06-04T17:23:28Z Add hardware req. - will add architectures soon. wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[dpkg]] | usagetype = Desktop, Server | website = [https://www.debian.org/ debian.org] }} '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool sets.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" |+ !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /> <references /> [[Category:Linux Distributions]] 12626dbb1fb3b1ec4548d995b49f3bf9a62816f5 430 429 2024-06-04T17:24:31Z Add references header wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[dpkg]] | usagetype = Desktop, Server | website = [https://www.debian.org/ debian.org] }} '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool sets.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" |+ !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /> === References === <references /> [[Category:Linux Distributions]] 17b4a55e228868e151eadde79f518262c1660b4b 459 430 2024-06-04T19:02:28Z wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[dpkg]] | usagetype = Desktop, Server | website = [https://www.debian.org/ debian.org] }} '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool sets.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" |+ !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] 5dd0246fb1159ad66fb979165fb120f43d6c9096 0 2 431 399 2024-06-04T17:27:57Z Add references header wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Its main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> Pacman uses different repositories to store its packages: * [core], housing all of the packages necessary for a base Arch installation to function; * [extra], housing applications and tooling that is not necessary for the system to function but serves instead for user-defined needs; * [multilib], housing 32-bit architecture libraries centered around legacy or compatibility concerns; ** [-testing], housing testing versions of the other repos that people from the Arch Testing Team<ref>https://wiki.archlinux.org/title/Arch_Testing_Team</ref> test before it gets into the main repos; ** [-staging], containing broken packages and is used solely by developers for rebuilding many packages at once; <ref>https://wiki.archlinux.org/title/official_repositories#Staging_repositories</ref> * the '''AUR''' (''Arch User Repository''), housing community-maintained, unofficial builds of software aimed at either convenience or specific use-cases; ** custom user repositories, housing specific software outside of the AUR and official repositories. <ref>Arch Linux Wiki - Official Repositories[https://wiki.archlinux.org/title/Official_repositories]</ref><ref>Arch Linux Wiki - Unofficial User Repositories[https://wiki.archlinux.org/title/Unofficial_repositories]</ref> === Philosophy === ... === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> === References === <references /> [[Category:Linux Distributions]] 52787c8c7febe3f1b5cfa2def9fd5f7c60361caa 458 431 2024-06-04T19:02:03Z wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Its main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> Pacman uses different repositories to store its packages: * [core], housing all of the packages necessary for a base Arch installation to function; * [extra], housing applications and tooling that is not necessary for the system to function but serves instead for user-defined needs; * [multilib], housing 32-bit architecture libraries centered around legacy or compatibility concerns; ** [-testing], housing testing versions of the other repos that people from the Arch Testing Team<ref>https://wiki.archlinux.org/title/Arch_Testing_Team</ref> test before it gets into the main repos; ** [-staging], containing broken packages and is used solely by developers for rebuilding many packages at once; <ref>https://wiki.archlinux.org/title/official_repositories#Staging_repositories</ref> * the '''AUR''' (''Arch User Repository''), housing community-maintained, unofficial builds of software aimed at either convenience or specific use-cases; ** custom user repositories, housing specific software outside of the AUR and official repositories. <ref>Arch Linux Wiki - Official Repositories[https://wiki.archlinux.org/title/Official_repositories]</ref><ref>Arch Linux Wiki - Unofficial User Repositories[https://wiki.archlinux.org/title/Unofficial_repositories]</ref> === Philosophy === ... === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 948644f6c7e5c047110834adbed294f7c8f8cfbc 0 175 444 354 2024-06-04T18:29:26Z Electron271 3 Chore: Update categories wikitext text/x-wiki In Arch Linux, Pacman is... [[Category:Software]] [[Category:Package Managers]] 029bff74e4982c402bc4b7d0c3dc6e61fd9f9295 464 444 2024-06-04T19:09:10Z Electron271 3 Chore: Update categories wikitext text/x-wiki In Arch Linux, Pacman is... [[Category:Package Managers]] b3e83ecbab9b1bf5d39aa207539f5ff4f6d061b7 1 194 446 2024-06-04T18:37:27Z Electron271 3 /* do not put stuff like (infobox potential) */ new section wikitext text/x-wiki == do not put stuff like (infobox potential) == if you must put it in a comment or somewhere hidden away from the user [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 18:37, 4 June 2024 (UTC) cc92b325670f1733eda8a24a0ff48119275f03f8 0 174 447 353 2024-06-04T18:37:54Z Electron271 3 Chore: Update categories wikitext text/x-wiki A '''TUI''' (Text-based User Interface) generally refers to an application that solely exists within the terminal as a text-based application - this means that all of its content is rendered using letters and other unique characters to create a graphical interface. [REFERENCE POSSIBLE] Because of its independence from a ... , [[Category:Terminology]] 6d072324f89a2926d287f54dc1b2a33fbecf9b43 0 169 448 344 2024-06-04T18:38:03Z Electron271 3 Chore: Update categories wikitext text/x-wiki Package managers refer to..... [[Category:Terminology]] 6ca37276eb03ef8dcd5cf7c3f62d9c4f9954121a 0 178 450 363 2024-06-04T18:38:22Z Electron271 3 Chore: Update categories wikitext text/x-wiki Linux in itself refers to two entities, the former being the kernel itself developed by Linus Torvalds and the latter being the families of Operating Systems that derive from it therein. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> (infobox potential) <references /> [[Category:Terminology]] 78ee8f613fb16c93f3f5e01dc9a2974c4035ec74 8 196 454 2024-06-04T18:56:03Z Add an automatic heading before the references list javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ $(document).ready(function(){ $('.mw-references-wrap').before('<h2>References</h2>'); }); 4526a214ca149b86a31f01350a234e4ad25c21d4 461 454 2024-06-04T19:06:52Z Protected "[[MediaWiki:Common.js]]": This is the JavaScript for ALL users. ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ $(document).ready(function(){ $('.mw-references-wrap').before('<h2>References</h2>'); }); 4526a214ca149b86a31f01350a234e4ad25c21d4 0 198 465 2024-06-04T19:11:34Z Atmois 13 Created page with "A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other progr..." wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == ==== Arch Based ==== [[Arch Linux|Arch]] is an independent [[Linux]] distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent [[Linux]] distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== Fedora is a community supported [[Linux]] distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== Gentoo is a [[Linux]] distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== Red Hat Enterprise Linux (RHEL) is a commercial [[Linux]] distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable [[Linux]] distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed [[Linux]] distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a [[Linux]] distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] | |} 24173bf2253d892a29374d865a04977c2b688c35 466 465 2024-06-04T19:18:11Z Atmois 13 Added info on NixOS wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == ==== Arch Based ==== [[Arch Linux|Arch]] is an independent [[Linux]] distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent [[Linux]] distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== Fedora is a community supported [[Linux]] distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== Gentoo is a [[Linux]] distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== Red Hat Enterprise Linux (RHEL) is a commercial [[Linux]] distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable [[Linux]] distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed [[Linux]] distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a [[Linux]] distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A [[Linux]] distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} 7006741fcad4b85e8dc43f366becbdc2e895bb60 0 182 467 459 2024-06-04T19:28:46Z Remove table caption and fix typo. wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[dpkg]] | usagetype = Desktop, Server | website = [https://www.debian.org/ debian.org] }} '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] 4abd9b7b9a553f5bf282c5c9b5be22341e732a70 520 467 2024-06-05T00:50:25Z Electron271 3 Add image to Debian wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[dpkg]] | usagetype = Desktop, Server | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE|KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] de239a3ee68f856d03e18441c8074186d75a46da 0 177 468 436 2024-06-04T19:51:40Z wikitext text/x-wiki '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre and Open Source Software (FLOSS), is software that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111.</ref> FOSS is a neutral term that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> [[Category:Terminology]] 758f269e2492b5ac20048340ffc7019cf50a669c 0 171 469 460 2024-06-04T20:07:01Z Amadaluzia 52 Added a paragraph about Home Manager. wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Varied depending on user configuration | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 6ed3fac80bbbda95d918d2ab772bb6f629e2b415 473 469 2024-06-04T20:37:02Z Astrid 8 I added a section about lix wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Varied depending on user configuration | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === Lix is a community fork of nix, and is located at https://lix.systems. It uses the meson build system. The Lix team also plans to gradually introduce rust to the source code<ref name=":0">https://lix.systems/about/#why-lix</ref>. There are also plans to improve the nix language and make it into the lix language, which is different but still generally syntactically compatible with the nix language<ref name=":0" />. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 0f568bdce4859c656a734b7d0a9b960f664de4db 475 473 2024-06-04T20:45:14Z Amadaluzia 52 /* Lix */ changed some small grammatical errors and reworded a sentence as to use the link tag. wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Varied depending on user configuration | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.</nowiki><ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language<ref name=":0" />. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] f2821007344c838a1b61fda24a0c6c409275ff89 476 475 2024-06-04T20:45:51Z Amadaluzia 52 /* Lix */ leftover from accidental visual mode edit wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Varied depending on user configuration | packagemanager = [[Nix]] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language<ref name=":0" />. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] cf4c830d26a4e35cc08069c2dde36c772e5869b3 484 476 2024-06-04T20:59:08Z Astrid 8 controversy section wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language<ref name=":0" />. === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra<ref>https://save-nix-together.org</ref>, he eventually resigned<ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref>. Following the resignation, the new board in charge decided to unban a fascist<ref name=":1" />. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 761328228bb51c22d766884402002555b9af8390 485 484 2024-06-04T21:00:29Z Astrid 8 fix repetition wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | updatemethod = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language<ref name=":0" />. === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra<ref>https://save-nix-together.org</ref>, he eventually resigned<ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref>. After the resignation, the new board in charge decided to unban a fascist<ref name=":1" />. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] b71d2af347f0a57fac1162667be2a7d5f55a99d1 0 1 470 462 2024-06-04T20:11:50Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[NixOS]] == Meta == * [[Main Page]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] c4d691916b31227800d72fe6efcdbae332880494 481 470 2024-06-04T20:54:57Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[NixOS]] == Mascots == * [[Larry the Cow]] == Meta == * [[Main Page]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Linux Distributions]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] d84f6453fa2c33c47323cb2bcdb9f3dae789fa9f 483 481 2024-06-04T20:55:50Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] == Meta == * [[Main Page]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] 203eb34a4d3b31bc351102afc78368b9a3fd0893 490 483 2024-06-04T21:21:27Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> === Desktop Environments === * [[KDE]] === Guides === * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] === Linux Distributions === * [[Arch Linux]] * [[Debian]] * [[Linux Distributions]] * [[NixOS]] === Mascots === * [[Larry the Cow]] === Meta === * [[Main Page]] === Package Managers === * [[Pacman]] === Terminology === * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] === Misc === * [[Gentoo Linux]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] 7cd1283f036169d64fbda08b25df6af75c4d8740 492 490 2024-06-04T21:24:08Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Gentoo Linux]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] == Meta == * [[Main Page]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] f5d495baa103720b8f986b694906e16eca0f2372 513 492 2024-06-04T23:08:11Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Gentoo Linux]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] == Meta == * [[Main Page]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] ebc5fc3b5ffca6ce9dcbe7475aec23166dc1db20 515 513 2024-06-04T23:29:41Z Electron271 3 Chore: Update categories wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Gentoo Linux]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] == Meta == * [[Main Page]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 10cb7936c035973662eac3219f296d021d3ea1fa 516 515 2024-06-04T23:34:58Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Gentoo Linux]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' e27c737c176c39004e962b91c6fde656beca548a 0 198 472 466 2024-06-04T20:31:10Z Electron271 3 Electron271 moved page [[Category:Linux Distributions]] to [[Linux Distributions]] without leaving a redirect: Wrong page wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == ==== Arch Based ==== [[Arch Linux|Arch]] is an independent [[Linux]] distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent [[Linux]] distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== Fedora is a community supported [[Linux]] distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== Gentoo is a [[Linux]] distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== Red Hat Enterprise Linux (RHEL) is a commercial [[Linux]] distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable [[Linux]] distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed [[Linux]] distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a [[Linux]] distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A [[Linux]] distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} 7006741fcad4b85e8dc43f366becbdc2e895bb60 482 472 2024-06-04T20:55:24Z Electron271 3 Chore: Update categories wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == ==== Arch Based ==== [[Arch Linux|Arch]] is an independent [[Linux]] distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent [[Linux]] distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== Fedora is a community supported [[Linux]] distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== Gentoo is a [[Linux]] distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== Red Hat Enterprise Linux (RHEL) is a commercial [[Linux]] distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable [[Linux]] distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed [[Linux]] distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a [[Linux]] distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A [[Linux]] distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] 127a4fce3cf6be3c71dd7721f05aa8f9e07d87bc 488 482 2024-06-04T21:19:07Z Atmois 13 Add extra info on the list wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux|Arch]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== Fedora is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== Gentoo is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== Red Hat Enterprise Linux (RHEL) is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] c2889c69030bcb620d7053b2c7ca4ccc1ad97f12 489 488 2024-06-04T21:21:15Z Amadaluzia 52 Linked the Gentoo wiki, changed Arch to Arch Linux wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== Fedora is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo Linux]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== Red Hat Enterprise Linux (RHEL) is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] aede9de7699f1e6230f4c085ce2dae112f265062 6 200 477 2024-06-04T20:48:14Z Electron271 3 "apt moo" command on Debian 12 through distrosea wikitext text/x-wiki == Summary == "apt moo" command on Debian 12 through distrosea e31638f3bb6b2b9ba63f3bc3b37f2e4ee0e3d6f3 6 201 478 2024-06-04T20:51:21Z Electron271 3 "emerge --moo" command on the Gentoo Live GUI through distrosea wikitext text/x-wiki == Summary == "emerge --moo" command on the Gentoo Live GUI through distrosea 767a2b7e65b7f7cb72148d549ec5c458bc42d531 0 202 479 2024-06-04T20:53:08Z Electron271 3 Add Larry the Cow wikitext text/x-wiki [[File:Larry the cow.png|frame|Larry the Cow]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". bacab07378683c2fcb5490aec0b445e013c7b998 480 479 2024-06-04T20:54:41Z Electron271 3 Chore: Update categories wikitext text/x-wiki [[File:Larry the cow.png|frame|Larry the Cow]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". <references /> [[Category:Mascots]] 29699a33a4fc621c9bb5e2c8f460cc02975fe721 494 480 2024-06-04T21:30:05Z Atmois 13 Update link to gentoo wikitext text/x-wiki [[File:Larry the cow.png|frame|Larry the Cow]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow</ref> of [[Gentoo Linux|Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". <references /> [[Category:Mascots]] f15da0187dec1b4a414d57c32bf9abf00df2f722 508 494 2024-06-04T22:29:50Z Electron271 3 larry the cow is now the most advanced page wikitext text/x-wiki {{LarryInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow</ref> of [[Gentoo Linux|Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". <references /> [[Category:Mascots]] 519f628585a109d484ddf6551d51b7e4d9e5d503 514 508 2024-06-04T23:19:02Z Electron271 3 more larry the cow facts wikitext text/x-wiki {{LarryInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow</ref> of [[Gentoo Linux|Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry</ref> <references /> [[Category:Mascots]] 035c4a1f2589d33b67db3cf2a8fc0431cb855835 0 203 487 2024-06-04T21:18:30Z Amadaluzia 52 Created Gentoo page wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[portage]] | usagetype = Desktop, Server | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around be how you want it to be. This distro aside having the systemd init system, also provides its own init system, known as OpenRC. Unlike other Linux distributions, everything you make is to be compiled. As such, users can compile their system as the way they want it to be.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> caf93bdcdac26feaea5dcf785bd860a5d2c83243 491 487 2024-06-04T21:23:25Z Amadaluzia 52 added link to Category:Linux Distributions wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[portage]] | usagetype = Desktop, Server | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around be how you want it to be. This distro aside having the systemd init system, also provides its own init system, known as OpenRC. Unlike other Linux distributions, everything you make is to be compiled. As such, users can compile their system as the way they want it to be.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 2e28227d7d5b86c73c4ab2f6df913c137ac87062 493 491 2024-06-04T21:27:22Z Amadaluzia 52 grammar fix wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[portage]] | usagetype = Desktop, Server | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around be how you want it to be. This distro aside having the systemd init system, also provides its own init system, known as OpenRC. Unlike other Linux distributions, everything you make is to be compiled. As such, users can compile their system in the way they want it to be.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 694a059fb686daf7f61843ea63a782b71a77c65d 521 493 2024-06-05T00:51:21Z Electron271 3 Add image to Gentoo wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[portage]] | usagetype = Desktop, Server | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE|KDE Plasma]]]] [https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around be how you want it to be. This distro aside having the systemd init system, also provides its own init system, known as OpenRC. Unlike other Linux distributions, everything you make is to be compiled. As such, users can compile their system in the way they want it to be.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] eef5b886d5da2680ea0b7c8658477ed205ed350c 523 521 2024-06-05T00:54:40Z Electron271 3 Electron271 moved page [[Gentoo Linux]] to [[Gentoo]]: the linux part is implied wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[portage]] | usagetype = Desktop, Server | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE|KDE Plasma]]]] [https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around be how you want it to be. This distro aside having the systemd init system, also provides its own init system, known as OpenRC. Unlike other Linux distributions, everything you make is to be compiled. As such, users can compile their system in the way they want it to be.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] eef5b886d5da2680ea0b7c8658477ed205ed350c 0 8 495 449 2024-06-04T21:33:08Z Amadaluzia 52 Changed `nixpkgs` to `Nix` with a link to the `NixOS` article wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE|KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] d7904ce115e3ebdc8f41c83b707b2a53b32581e2 828 204 496 2024-06-04T22:08:45Z Electron271 3 software infobox still heavy wip Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval.addImage( args.image, args.caption ) end retval.addRow( 'Release Status', args.releasestatus ) :addRow( 'Update Method', args.updatemethod ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Website', args.website ) return retval end return p 37e8df2d02f1cef0cb079b089817aa7e51b25d2f 499 496 2024-06-04T22:13:35Z Electron271 3 Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Update Method', args.updatemethod ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Website', args.website ) return retval end return p ad005314c8815feef866377b9171868b5cc41110 500 499 2024-06-04T22:17:20Z Electron271 3 Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Last Release', args.lastrelease ) :addRow( 'Language(s)', args.languages ) :addRow( 'Developer(s)', args.developers ) :addRow( 'Website', args.website ) return retval end return p 10e68839b660f1cac4400d90ee88f3367780e7be 10 205 497 2024-06-04T22:09:51Z Electron271 3 Created page with "<includeonly>{{#invoke:SoftwareInfobox|main}}</includeonly>" wikitext text/x-wiki <includeonly>{{#invoke:SoftwareInfobox|main}}</includeonly> 18a26db43b8047401f2133ffe702a70c137cb38f 0 169 498 448 2024-06-04T22:11:50Z Amadaluzia 52 added content to this page wikitext text/x-wiki A package manager, is a utility designed to manage your systems packages. The regular functions of a package manager are: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * And adding/removing/updating package repositories === List of known package managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (for example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [https://wiki.archlinux.org/title/Pacman pacman] is used in [[Arch Linux]] and maintained by the Arch Linux development team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [https://wiki.debian.org/Apt apt] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. [[Category:Terminology]] a4acbfb3313b3897a6253c93d128fbb5703fee47 509 498 2024-06-04T22:38:00Z Amadaluzia 52 added content to this page wikitext text/x-wiki [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager, is a utility designed to manage your systems packages. The regular functions of a package manager are: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * And adding/removing/updating package repositories === List of known package managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (for example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [https://wiki.archlinux.org/title/Pacman pacman] is used in [[Arch Linux]] and maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [https://wiki.debian.org/Apt apt] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://wiki.gentoo.org/wiki/Portage Portage] is developed and maintained the Gentoo Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. [[Category:Terminology]] 0c96d6c01635185887ca8d2d2e41e1e5f1b3ef68 0 175 501 464 2024-06-04T22:17:48Z Electron271 3 add pacman infobox wikitext text/x-wiki {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} In Arch Linux, Pacman is... [[Category:Package Managers]] 4c40fb159c157035cbc0b661be7fe43c8467f078 510 501 2024-06-04T22:38:58Z Aru 17 Initial commit, including an intro and basic pacman command usage wikitext text/x-wiki {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} == Intro == The Linux distribution Arch Linux and its derivatives usually use a [[package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Common Usages == Here are some common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy</code> |Update package listing- note that this does not update any packages |- |<code>pacman -Syu</code> |Update system's packages |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove package and its unneeded dependencies |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed- colloq. orphans |} == Safe Package Removal == When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> === TL;DR === Use <code>-R</code> to remove a package, <code>-Rs</code> to remove a package and its dependencies, and <code>pacman -R $(pacman -Qdtq)</code> to remove all orphans. [[Category:Package Managers]] beab17f82d0898e57385ef75e5d209885490972d 511 510 2024-06-04T22:49:13Z Electron271 3 remove dangerous partial upgrade command wikitext text/x-wiki {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} == Intro == The Linux distribution Arch Linux and its derivatives usually use a [[package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Common Usages == Here are some common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Syu</code> |Update system's packages |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove package and its unneeded dependencies |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed- colloq. orphans |} == Safe Package Removal == When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> === TL;DR === Use <code>-R</code> to remove a package, <code>-Rs</code> to remove a package and its dependencies, and <code>pacman -R $(pacman -Qdtq)</code> to remove all orphans. [[Category:Package Managers]] 8f45b20d709bd864a48c3e8fe68144cc1403dddb 517 511 2024-06-05T00:44:22Z Electron271 3 add image to pacman wikitext text/x-wiki {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Pacman 401.png|thumb|[[Pacman]]]] == Intro == The Linux distribution Arch Linux and its derivatives usually use a [[package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Common Usages == Here are some common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Syu</code> |Update system's packages |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove package and its unneeded dependencies |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed- colloq. orphans |} == Safe Package Removal == When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> === TL;DR === Use <code>-R</code> to remove a package, <code>-Rs</code> to remove a package and its dependencies, and <code>pacman -R $(pacman -Qdtq)</code> to remove all orphans. [[Category:Package Managers]] 424b03480d35c3254ff88352da9d6951b7a9604c 828 163 504 330 2024-06-04T22:22:42Z Electron271 3 Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Update Method', args.updatemethod ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Website', args.website ) return retval end return p ad005314c8815feef866377b9171868b5cc41110 0 2 505 458 2024-06-04T22:26:52Z Electron271 3 neofetch wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | updatemethod = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Its main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> Pacman uses different repositories to store its packages: * [core], housing all of the packages necessary for a base Arch installation to function; * [extra], housing applications and tooling that is not necessary for the system to function but serves instead for user-defined needs; * [multilib], housing 32-bit architecture libraries centered around legacy or compatibility concerns; ** [-testing], housing testing versions of the other repos that people from the Arch Testing Team<ref>https://wiki.archlinux.org/title/Arch_Testing_Team</ref> test before it gets into the main repos; ** [-staging], containing broken packages and is used solely by developers for rebuilding many packages at once; <ref>https://wiki.archlinux.org/title/official_repositories#Staging_repositories</ref> * the '''AUR''' (''Arch User Repository''), housing community-maintained, unofficial builds of software aimed at either convenience or specific use-cases; ** custom user repositories, housing specific software outside of the AUR and official repositories. <ref>Arch Linux Wiki - Official Repositories[https://wiki.archlinux.org/title/Official_repositories]</ref><ref>Arch Linux Wiki - Unofficial User Repositories[https://wiki.archlinux.org/title/Unofficial_repositories]</ref> === Philosophy === ... === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] e61a0be5e5c2ca13ce69eee5dd29d1c2415c06a6 828 207 506 2024-06-04T22:28:16Z Electron271 3 larryinfobox Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Larry', 'the Cow' ) return retval end return p f1b5f50a1f8afbb754d0fa2d4c15dfeee7987a2f 10 208 507 2024-06-04T22:28:33Z Electron271 3 Created page with "<includeonly>{{#invoke:LarryInfobox|main}}</includeonly>" wikitext text/x-wiki <includeonly>{{#invoke:LarryInfobox|main}}</includeonly> 2977b853b4d4d1dd4e3156eca3c05d347aeb67cc 0 209 512 2024-06-04T23:04:06Z Amadaluzia 52 Created a help landing spot for Mac users on Linux. wikitext text/x-wiki === Introduction === Linux is a good way to make-do with an old Mac you may have, especially with Apple discontinuing x86_64 CPU's in favor for their in-house M chips<ref>https://en.wikipedia.org/wiki/Mac_transition_to_Apple_silicon</ref>. Many issues exist due to hardware support, such as WiFi support, and keyboard + trackpad issues. In this article, you will see the troubles you may face when using Linux on your Mac. === MacBookPro11,x to MacBookPro12,1 === ==== WiFi doesn't work ==== This is a side-effect of [https://wiki.archlinux.org/title/broadcom_wireless#broadcom-wl Broadcom's driver support with Linux], read the page linked in order to get your fix. === Notes === ''' More issues will be added overtime. This list is far from done.''' <references /> [[Category:Guides]] 3ddb4119e3d6eaa12454d8c0a1e68cca88ab474c 0 176 519 463 2024-06-05T00:49:07Z Electron271 3 Add infobox and image to the KDE page wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref><references /> [[Category:Desktop Environments]] da237db6bd27560b58c2dc2ae6fc73ecc87f83de 0 178 525 450 2024-06-05T01:00:03Z Electron271 3 add infobox and image to tux wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux Kernel | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], Assembly, [[Rust]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] Linux in itself refers to two entities, the former being the kernel itself developed by Linus Torvalds and the latter being the families of Operating Systems that derive from it therein. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> <references /> [[Category:Terminology]] b94acf2c22298d4486a62ae8a1997bf7fc1b4da7 0 176 526 519 2024-06-05T01:00:40Z Electron271 3 Electron271 moved page [[KDE]] to [[KDE Plasma]] wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref><references /> [[Category:Desktop Environments]] da237db6bd27560b58c2dc2ae6fc73ecc87f83de 0 1 528 516 2024-06-05T01:52:05Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE]] * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Gentoo]] * [[Gentoo Linux]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 4623c1f03bc02ae4cf88f0e040ebb3df0ba1a9b1 532 528 2024-06-05T01:54:55Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Gentoo]] * [[Gentoo Linux]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 7461162d3cab3755a330d2a9b936e86f6fb766cf 535 532 2024-06-05T01:56:49Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 271cfbb181af32e5c37cefe925e363ce9fed2eb1 541 535 2024-06-05T02:51:31Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 85d55b9de7628e6122450f90a6f130778b860f56 543 541 2024-06-05T03:08:15Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Fedora Linux]] * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' f8fa5096c538b528345922d2f193c15ff4708959 546 543 2024-06-05T03:10:02Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora Linux]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 57c14e412f871e9d1ceecf7ee92ceedcd26a1b8d 580 546 2024-06-05T12:24:29Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Distrohopping]] * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' c1cbcd07a64546674843ca813d0ea461d6146dd2 0 182 529 520 2024-06-05T01:52:29Z Electron271 3 wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[dpkg]] | usagetype = Desktop, Server | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] b084ba9ec927303c23fee2099e710e1373f0874b 569 529 2024-06-05T12:16:42Z Atmois 13 Change updatemethod to releasemodel wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | usagetype = Desktop, Server | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] 7c0d105aaa80f78a927c865820008ddb2c7b3881 0 203 530 523 2024-06-05T01:52:50Z Electron271 3 wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | updatemethod = Rolling Release / Stable | packagemanager = [[portage]] | usagetype = Desktop, Server | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]] [https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around be how you want it to be. This distro aside having the systemd init system, also provides its own init system, known as OpenRC. Unlike other Linux distributions, everything you make is to be compiled. As such, users can compile their system in the way they want it to be.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 43e0c7cb021fb09d9d5a97c268f4a2799733f775 573 530 2024-06-05T12:22:15Z Atmois 13 Change updatemethod to releasemodel wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | usagetype = Desktop, Server | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]] [https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around be how you want it to be. This distro aside having the systemd init system, also provides its own init system, known as OpenRC. Unlike other Linux distributions, everything you make is to be compiled. As such, users can compile their system in the way they want it to be.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 44b98a4d82dbd3c96f707f54023c3f4072415610 0 8 531 495 2024-06-05T01:53:45Z Electron271 3 wikitext text/x-wiki The new user engaging with the modern world of Linux and the open-source ecosystem as a whole will likely be bombarded with loads of terminology that sounds foreign and often confusing. This is an index of different subjects that a new user should learn about upon interacting with Linux for the first time. * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 76f4f8e6fb175c6f670c2e2676aff89bfe35e804 554 531 2024-06-05T05:01:51Z Ari43 20 Made the introductory paragraph more friendly wikitext text/x-wiki == Introduction == New user engaging with the Linux and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is an list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] a582e18cc9e88832cf72501c9b94c0e8987f1cc3 555 554 2024-06-05T05:02:11Z Ari43 20 Fixed a minor grammatical error wikitext text/x-wiki == Introduction == New users engaging with the Linux and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is an list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 76dd0773052dc37d7926ccf5abdc70192261a45e 556 555 2024-06-05T05:02:53Z Ari43 20 Fixed another missed grammatical error :( wikitext text/x-wiki == Introduction == New users engaging with the Linux and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] f1f0dc5dc47b0b50c01efa620e0a7d158d3a2ae9 0 198 533 489 2024-06-05T01:55:46Z Electron271 3 wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== Fedora is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== Red Hat Enterprise Linux (RHEL) is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] a14b0f64bf22431d2be3126fc56a2554dbf4a1d3 544 533 2024-06-05T03:08:37Z Sodium 9 Added a link to Fedora Linux in the Linux Distributions section wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== [[Fedora Linux|Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== Red Hat Enterprise Linux (RHEL) is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] 24cdff33caa0d6e3e56e2a54d58a1b63a093a9f2 579 544 2024-06-05T12:23:44Z Electron271 3 wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== [[Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== Red Hat Enterprise Linux (RHEL) is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] 26968c500615cc0bc750a2291ad11a6a04e62609 0 202 534 514 2024-06-05T01:56:00Z Electron271 3 wikitext text/x-wiki {{LarryInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry</ref> <references /> [[Category:Mascots]] d296f06f4b943dcc347341cc67739ec4b264c015 0 214 536 2024-06-05T02:29:56Z Electron271 3 barebones tux page wikitext text/x-wiki {{LarryInfobox | title = Tux | image = [[File:Tux.svg|Tux|333px]] | caption = Tux! }} '''Tux''' is the official mascot of [[Linux]], designed by Larry Ewing<ref>https://web.archive.org/web/20040401161253/http://www.linux.org/info/logos.html</ref>. Tux was created for the Linux 2.0 logo competition<ref>https://web.archive.org/web/20040407092622/http://www.cs.earlham.edu/~jeremiah/linux-pix/linux-logo.html</ref>.<references /> [[Category:Mascots]] 4360187cc249054a30d328bc4c365df83cd95b31 2 216 539 2024-06-05T02:46:58Z Electron271 3 Created page with "This is the account which users which get deleted for whatever reasons are merged into then deleted. If you see a edit from this user it came from a deleted account." wikitext text/x-wiki This is the account which users which get deleted for whatever reasons are merged into then deleted. If you see a edit from this user it came from a deleted account. c20e2ba8118fd71eb715d125629d2db9d3d68073 540 539 2024-06-05T02:47:24Z Electron271 3 Protected "[[User:DeletedAccount]]": does not need any further edits ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki This is the account which users which get deleted for whatever reasons are merged into then deleted. If you see a edit from this user it came from a deleted account. c20e2ba8118fd71eb715d125629d2db9d3d68073 0 217 542 2024-06-05T03:05:29Z Sodium 9 Created Fedora Linux page wikitext text/x-wiki {{DistributionInfobox|title=Fedora Linux|image=[[File:Fedora logo.svg|Fedora_logo]]|caption=The Fedora Linux logo|releasestatus=Maintained|updatemethod=Cutting Edge Release|packagemanager=[[dnf]]|usagetype=Desktop, Server, Cloud|website=[https://fedoraproject.org/ fedoraproject.org]}}'''Fedora Linux''' is an independent [[Linux]] distribution<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called Red Hat Enterprise Linux (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> 3b2ecfa934a6d912e822dcd947864b8e5ff328ea 545 542 2024-06-05T03:09:17Z Electron271 3 Chore: Update categories wikitext text/x-wiki {{DistributionInfobox|title=Fedora Linux|image=[[File:Fedora logo.svg|Fedora_logo]]|caption=The Fedora Linux logo|releasestatus=Maintained|updatemethod=Cutting Edge Release|packagemanager=[[dnf]]|usagetype=Desktop, Server, Cloud|website=[https://fedoraproject.org/ fedoraproject.org]}}'''Fedora Linux''' is an independent [[Linux]] distribution<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called Red Hat Enterprise Linux (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] c7d151e373bea12de1726262c95ce795c315112e 570 545 2024-06-05T12:17:12Z Atmois 13 Change updatemethod to releasemodel wikitext text/x-wiki {{DistributionInfobox|title=Fedora Linux|image=[[File:Fedora logo.svg|Fedora_logo]]|caption=The Fedora Linux logo|releasestatus=Maintained|Change updatemethod to releasemodel=Cutting Edge Release|packagemanager=[[dnf]]|usagetype=Desktop, Server, Cloud|website=[https://fedoraproject.org/ fedoraproject.org]}}'''Fedora Linux''' is an independent [[Linux]] distribution<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called Red Hat Enterprise Linux (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] b11371409d445ba1fa2ba1495cd39a2bc3a2d247 572 570 2024-06-05T12:21:07Z Atmois 13 Change updatemethod to releasemodel wikitext text/x-wiki {{DistributionInfobox|title=Fedora Linux|image=[[File:Fedora logo.svg|Fedora_logo]]|caption=The Fedora Linux logo|releasestatus=Maintained|releasemodel=Cutting Edge Release|packagemanager=[[dnf]]|usagetype=Desktop, Server, Cloud|website=[https://fedoraproject.org/ fedoraproject.org]}}'''Fedora Linux''' is an independent [[Linux]] distribution<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called Red Hat Enterprise Linux (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] d2f748b587ceaa2c2fcc14968616a2078c5315e0 574 572 2024-06-05T12:22:24Z Electron271 3 fix infobox and weird release model wikitext text/x-wiki {{DistributionInfobox|title=Fedora Linux|image=[[File:Fedora logo.svg|Fedora_logo]]|caption=The Fedora Linux logo|releasestatus=Maintained|releasemodel=Semi-Rolling Release|packagemanager=[[dnf]]|usagetype=Desktop, Server, Cloud|website=[https://fedoraproject.org/ fedoraproject.org]}}'''Fedora Linux''' is an independent [[Linux]] distribution<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called Red Hat Enterprise Linux (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] d3e37d1426ceb9f0ac204e385d5a36615b87c361 575 574 2024-06-05T12:22:54Z Electron271 3 Electron271 moved page [[Fedora Linux]] to [[Fedora]] wikitext text/x-wiki {{DistributionInfobox|title=Fedora Linux|image=[[File:Fedora logo.svg|Fedora_logo]]|caption=The Fedora Linux logo|releasestatus=Maintained|releasemodel=Semi-Rolling Release|packagemanager=[[dnf]]|usagetype=Desktop, Server, Cloud|website=[https://fedoraproject.org/ fedoraproject.org]}}'''Fedora Linux''' is an independent [[Linux]] distribution<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called Red Hat Enterprise Linux (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] d3e37d1426ceb9f0ac204e385d5a36615b87c361 0 218 547 2024-06-05T04:04:26Z Ari43 20 Created the bones of a guide to installing Linux on older devices wikitext text/x-wiki == Introduction == Linux is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the desktop environment (or window manager) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like KDE or Gnome may be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |XFCE | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to keyboard focus * Requires significant text-based configuration to fit the preferences of the user |Not recommended for new users |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |Debian<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |Arch Linux<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * Arch Linux will not be covered in this article |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] 00ef4fd01c1ea124661556e44cc94cee5e820cdf 0 219 548 2024-06-05T04:05:32Z Ryna 21 Created page "Konqi" under mascots wikitext text/x-wiki {{LarryInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of KDE and [[KDE Plasma]], designed by Tyson Tan<ref>https://community.kde.org/Promo/Material/Mascots</ref>. Konqi's full name is "Konqi the Konqueror", being named after Konqueror, KDE's default web browser<ref>https://community.kde.org/Konqi</ref>.<references /> [[Category:Mascots]] 5c35a8450e6c0453f354c3925c572859f6d14516 0 209 549 512 2024-06-05T04:18:55Z Ari43 20 Added information on Asahi Linux, reformatted some section titles, reworded some sections wikitext text/x-wiki == Introduction == Linux is a good way to make-do with an old Intel Mac you may have. If you are attempting to install Linux on a device with an ARM (Apple Silicon) CPU, see the [[#Asahi Linux]] section. Many issues exist due to hardware support, such as WiFi support, and keyboard + trackpad issues on some devices. This page will list solutions to common issues as well as tips, tricks, and other information. On many Mac devices Linux works flawlessly after initial setup and troubleshooting is complete. == Asahi Linux == Asahi Linux as a work in progress port of many tools and drivers to Apple Silicon on Linux, and is currently under heavy development. More information can be found on the [https://asahilinux.org/ Asahi Linux website]. == Troubleshooting == === MacBookPro11,x to MacBookPro12,1 === ==== WiFi doesn't work ==== This is a side-effect of Broadcom's poor driver support on Linux, read [https://asahilinux.org/ this page] for information on how to install the proprietary '''broadcom-wl driver''' on Arch Linux. Other distributions should follow their respective guides if one exists. == Notes == '''> More issues will be added overtime. This list is far from done.''' <references /> [[Category:Guides]] ef1684b2b58169f3a6843c81946c3dc4e27b6048 550 549 2024-06-05T04:21:10Z Ari43 20 Ari43 moved page [[Macintosh to Linux]] to [[Linux on Apple Macintosh Devices]]: Title Clarity wikitext text/x-wiki == Introduction == Linux is a good way to make-do with an old Intel Mac you may have. If you are attempting to install Linux on a device with an ARM (Apple Silicon) CPU, see the [[#Asahi Linux]] section. Many issues exist due to hardware support, such as WiFi support, and keyboard + trackpad issues on some devices. This page will list solutions to common issues as well as tips, tricks, and other information. On many Mac devices Linux works flawlessly after initial setup and troubleshooting is complete. == Asahi Linux == Asahi Linux as a work in progress port of many tools and drivers to Apple Silicon on Linux, and is currently under heavy development. More information can be found on the [https://asahilinux.org/ Asahi Linux website]. == Troubleshooting == === MacBookPro11,x to MacBookPro12,1 === ==== WiFi doesn't work ==== This is a side-effect of Broadcom's poor driver support on Linux, read [https://asahilinux.org/ this page] for information on how to install the proprietary '''broadcom-wl driver''' on Arch Linux. Other distributions should follow their respective guides if one exists. == Notes == '''> More issues will be added overtime. This list is far from done.''' <references /> [[Category:Guides]] ef1684b2b58169f3a6843c81946c3dc4e27b6048 552 550 2024-06-05T04:24:28Z Ari43 20 Moved mention of Asahi Linux in introduction for clarity wikitext text/x-wiki == Introduction == Linux is a good way to make-do with an old Intel Mac you may have.Many issues exist due to hardware support, such as WiFi support, and keyboard + trackpad issues on some devices. This page will list solutions to common issues as well as tips, tricks, and other information. On many Mac devices Linux works flawlessly after initial setup and troubleshooting is complete. If you are attempting to install Linux on a device with an ARM (Apple Silicon) CPU, see the [[#Asahi Linux]] section. == Asahi Linux == Asahi Linux as a work in progress port of many tools and drivers to Apple Silicon on Linux, and is currently under heavy development. More information can be found on the [https://asahilinux.org/ Asahi Linux website]. == Troubleshooting == === MacBookPro11,x to MacBookPro12,1 === ==== WiFi doesn't work ==== This is a side-effect of Broadcom's poor driver support on Linux, read [https://asahilinux.org/ this page] for information on how to install the proprietary '''broadcom-wl driver''' on Arch Linux. Other distributions should follow their respective guides if one exists. == Notes == '''> More issues will be added overtime. This list is far from done.''' <references /> [[Category:Guides]] bebd3657cba174021255a7c8079812947bc48d3a 558 552 2024-06-05T07:56:30Z Amadaluzia 52 missing space added wikitext text/x-wiki == Introduction == Linux is a good way to make-do with an old Intel Mac you may have. Many issues exist due to hardware support, such as WiFi support, and keyboard + trackpad issues on some devices. This page will list solutions to common issues as well as tips, tricks, and other information. On many Mac devices Linux works flawlessly after initial setup and troubleshooting is complete. If you are attempting to install Linux on a device with an ARM (Apple Silicon) CPU, see the [[#Asahi Linux]] section. == Asahi Linux == Asahi Linux as a work in progress port of many tools and drivers to Apple Silicon on Linux, and is currently under heavy development. More information can be found on the [https://asahilinux.org/ Asahi Linux website]. == Troubleshooting == === MacBookPro11,x to MacBookPro12,1 === ==== WiFi doesn't work ==== This is a side-effect of Broadcom's poor driver support on Linux, read [https://asahilinux.org/ this page] for information on how to install the proprietary '''broadcom-wl driver''' on Arch Linux. Other distributions should follow their respective guides if one exists. == Notes == '''> More issues will be added overtime. This list is far from done.''' <references /> [[Category:Guides]] 5d49f9b16d5733cea05cc361a553af9360c178a6 0 220 551 2024-06-05T04:21:10Z Ari43 20 Ari43 moved page [[Macintosh to Linux]] to [[Linux on Apple Macintosh Devices]]: Title Clarity wikitext text/x-wiki #REDIRECT [[Linux on Apple Macintosh Devices]] 9cd4dfed0c705b6a35d0b0dc1efa8ae5f6c2db45 0 175 553 517 2024-06-05T04:57:01Z Ari43 20 Created content on safe usage, added command line flags and their use cases wikitext text/x-wiki {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Pacman 401.png|thumb|[[Pacman]]]] == Intro == The Linux distribution Arch Linux and its derivatives usually use a [[package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] [[Category:Package Managers]] 68ae709498ee962f739344ab37d6fc7994c3d7da 0 169 557 509 2024-06-05T05:13:18Z Ari43 20 Added rpm and some common package manager capabilities wikitext text/x-wiki == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (for example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [https://pacman.archlinux.page/ pacman] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [https://wiki.debian.org/Apt apt] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora Linux|Fedora]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [https://wiki.gentoo.org/wiki/Portage Portage] is developed and maintained the Gentoo Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. [[Category:Terminology]] 8aed70db8c6316d61d11863835b93b978837088e 577 557 2024-06-05T12:23:33Z Electron271 3 wikitext text/x-wiki == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (for example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [https://pacman.archlinux.page/ pacman] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [https://wiki.debian.org/Apt apt] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [https://wiki.gentoo.org/wiki/Portage Portage] is developed and maintained the Gentoo Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. [[Category:Terminology]] 0726718bf7055cd0880bd73c5386341483aee7c0 1 221 559 2024-06-05T08:01:36Z Amadaluzia 52 /* LarryInfobox causes Larry the Cow to infect this page */ new section wikitext text/x-wiki == LarryInfobox causes Larry the Cow to infect this page == What it reads on the tin, I thought it read Tux the Cow when I saw that bug. [[User:Balkenix|Balkenix]] ([[User talk:Balkenix|talk]]) 08:01, 5 June 2024 (UTC) 85fa03da0af8f2c4ff494397c4bacadf30871bcd 2 3 560 6 2024-06-05T08:02:16Z Amadaluzia 52 add discord wikitext text/x-wiki Big Lain Fan Discord: @balkenix c125ecfa377cf955f2e297cae2500836f8320cad 1 222 561 2024-06-05T08:04:49Z Amadaluzia 52 /* NixOS Linux */ new section wikitext text/x-wiki == NixOS Linux == I do not think its called that. It is called simply NixOS if memory serves. [[User:Balkenix|Balkenix]] ([[User talk:Balkenix|talk]]) 08:04, 5 June 2024 (UTC) 9df76e3aaa828afa9689b0d8d82b6e081dcea8cc 0 223 562 2024-06-05T08:36:32Z Uli 22 Information regarding the nature, patterns and motivation of distrohopping wikitext text/x-wiki == Distrohopping == Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new Linux distribution. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (eg. FSF approved distribution) * Ecosystem or Tooling (eg. libc, package manager, coreutils, init system) * Experimentation * Customization ... and many more. This behavior is increasingly common in Linux communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (eg. Debianisms, package managers, init systems) * Opinionated design philosophies (eg. Nix, Guix, Fedora Atomic) * Additional configuration needs (eg. minimalist distributions like Arch, Void, Crux and Gentoo) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (eg. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (eg. Liberapay, Github sponsors, FSF donations, Patreon) These techniques may help to enforce and individuals attachment to a particular distribution, allowing them to find distro to call ''home''. 0b55472c3f3eeac7e421370ad506cea222d53f1c 564 562 2024-06-05T08:51:13Z Uli 22 grammar wikitext text/x-wiki == Distrohopping == Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new Linux distribution. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (eg. FSF approved distribution) * Ecosystem or Tooling (eg. libc, package manager, coreutils, init system) * Experimentation * Customization ... and many more. This behavior is increasingly common in Linux communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (eg. Debianisms, package managers, init systems) * Opinionated design philosophies (eg. Nix, Guix, Fedora Atomic) * Additional configuration needs (eg. minimalist distributions like Arch, Void, Crux and Gentoo) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (eg. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (eg. Liberapay, Github sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. c6e7bac2121103feae87e1214ce88520e898641e 581 564 2024-06-05T12:27:16Z Electron271 3 Chore: Update categories wikitext text/x-wiki == Distrohopping == Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new Linux distribution. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (eg. FSF approved distribution) * Ecosystem or Tooling (eg. libc, package manager, coreutils, init system) * Experimentation * Customization ... and many more. This behavior is increasingly common in Linux communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (eg. Debianisms, package managers, init systems) * Opinionated design philosophies (eg. Nix, Guix, Fedora Atomic) * Additional configuration needs (eg. minimalist distributions like Arch, Void, Crux and Gentoo) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (eg. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (eg. Liberapay, Github sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] 5f73345010ed7f0029e1a90c8ae94ad80fb263dc 828 163 567 504 2024-06-05T12:14:30Z Atmois 13 Change updatemethod to releasemodel Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Website', args.website ) return retval end return p 436de9cdd260be60c0fa213ed7d4086e92007d66 571 567 2024-06-05T12:20:28Z Electron271 3 Protected "[[Module:DistributionInfobox]]": edits can break other pages easily ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Website', args.website ) return retval end return p 436de9cdd260be60c0fa213ed7d4086e92007d66 0 2 568 505 2024-06-05T12:15:50Z Atmois 13 Change updatemethod to releasemodel wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Its main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> Pacman uses different repositories to store its packages: * [core], housing all of the packages necessary for a base Arch installation to function; * [extra], housing applications and tooling that is not necessary for the system to function but serves instead for user-defined needs; * [multilib], housing 32-bit architecture libraries centered around legacy or compatibility concerns; ** [-testing], housing testing versions of the other repos that people from the Arch Testing Team<ref>https://wiki.archlinux.org/title/Arch_Testing_Team</ref> test before it gets into the main repos; ** [-staging], containing broken packages and is used solely by developers for rebuilding many packages at once; <ref>https://wiki.archlinux.org/title/official_repositories#Staging_repositories</ref> * the '''AUR''' (''Arch User Repository''), housing community-maintained, unofficial builds of software aimed at either convenience or specific use-cases; ** custom user repositories, housing specific software outside of the AUR and official repositories. <ref>Arch Linux Wiki - Official Repositories[https://wiki.archlinux.org/title/Official_repositories]</ref><ref>Arch Linux Wiki - Unofficial User Repositories[https://wiki.archlinux.org/title/Unofficial_repositories]</ref> === Philosophy === ... === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 41b6d174cae00187b44556b21e9dbd50cd40b9ba 0 171 578 485 2024-06-05T12:23:37Z Atmois 13 Change updatemethod to releasemodel wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | usagetype = Desktop, Server | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language<ref name=":0" />. === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra<ref>https://save-nix-together.org</ref>, he eventually resigned<ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref>. After the resignation, the new board in charge decided to unban a fascist<ref name=":1" />. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] ba7fa44a14c4a393ad7ad000e366acd4d46f6a1e 0 1 582 580 2024-06-05T12:40:04Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' f403cb87a7b5c5579b8e8d0feae2bcf99a04015c 590 582 2024-06-05T14:03:17Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] * [[Red Hat Enterprise Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 89565d3cd9c5d2be581b165f081006b97e3ced02 592 590 2024-06-05T14:06:02Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Older Devices]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 4d4e09ba42dd8544a1f4e67479f5399edd2f8b4d 594 592 2024-06-05T14:08:03Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Macintosh to Linux]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] * [[Red Hat Enterprise Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 89565d3cd9c5d2be581b165f081006b97e3ced02 596 594 2024-06-05T14:10:19Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 8892d1dc190c04c86086bb03eef61496f788ff71 610 596 2024-06-05T20:57:15Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[I3]] * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' c11bba196837f4d88f32b114f7165bc0c1c90921 618 610 2024-06-06T00:16:19Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[I3]] * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[AUR]] * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 1332d01a6bd99c2f36eca0b9f5f2d27ad67c035b 625 618 2024-06-06T03:23:41Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[I3]] * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[AUR]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 4d669de8569f5343ef6bab3abdebbf05bd67339b 0 175 583 553 2024-06-05T13:53:06Z Ari43 20 Added information about arguments, added repository details wikitext text/x-wiki {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Pacman 401.png|thumb|[[Pacman]]]] == Intro == The Linux distribution Arch Linux and its derivatives usually use a [[package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] [[Category:Package Managers]] 96aae306f8686373e32b436cf17013babf70f16f 0 2 584 568 2024-06-05T13:55:17Z Ari43 20 Removed redundant pacman details wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the AUR, Arch's well known user repository, possible. === Philosophy === ... === Trivia === * If you add "ILoveCandy" to /etc/pacman.conf instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] cc578adbee9a6db402cc716a41da2830e8fccdcc 603 584 2024-06-05T19:53:45Z PratyushKing 26 added a note for new users and a new trivia to speed up downloads wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the AUR, Arch's well known user repository, possible. Despite it being known as the hardest distributions to install and maintain (mainly because of its learning curve), it is now quite friendly for beginners. The install process is quite easy now where you connect network via the <code>iwctl</code> utility (for WiFi) and the <code>mmcli</code> utility (for mobile broadband modems) and just run the intuitive <code>archinstall</code> command. Once you do install, you can install a very easy to use AUR helper (recommended is <code>paru</code> but most users opt for <code>yay</code>), the commands are simplified too! A very important advise is to update your system per 2 weeks. You can install an AUR helper using any guide. You just run your AUR helper without any commands and it will update the full system and AUR packages, if you run the helper with just package name (for example, <code>yay firefox</code>), then it will show you a convenient list of package names (keep in mind, they can overlap due to the variety of packages). === Philosophy === ... === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> * If you wish to speed up your package downloads via the AUR or regular pacman, just edit your <code>/etc/pacman.conf</code>, uncomment the line where it says <code>ParallelDownloads</code>, you can keep it as default 5 but if you do have a good internet then a sweet spot is somewhere from 30-35 (for all the curious people, it just recurs a certain amount of bytes from each download instance on however much you want to recur over, that way if one download hangs, something is still downloading) [common issue: if your downloads say operation too slow just use the <code>-S</code> flag with package name and add the parameter <code>--disable-download-timeout</code>, this probably means you are overloading parallel downloads] <references /> [[Category:Linux Distributions]] 587e0ea9ec94dd74ebddce38f1f249e3693fb6dd 627 603 2024-06-06T07:12:24Z Removed opinionated section: specific Arch installation method without sources wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the AUR, Arch's well known user repository, possible. === Philosophy === ... === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> * If you wish to speed up your package downloads via the AUR or regular pacman, just edit your <code>/etc/pacman.conf</code>, uncomment the line where it says <code>ParallelDownloads</code>, you can keep it as default 5 but if you do have a good internet then a sweet spot is somewhere from 30-35 (for all the curious people, it just recurs a certain amount of bytes from each download instance on however much you want to recur over, that way if one download hangs, something is still downloading) [common issue: if your downloads say operation too slow just use the <code>-S</code> flag with package name and add the parameter <code>--disable-download-timeout</code>, this probably means you are overloading parallel downloads] <references /> [[Category:Linux Distributions]] 9420dc5df338b8826bd816af166c57b6e54354ed 628 627 2024-06-06T07:14:49Z Removed trivia section: information is wrong/misleading, please rewrite wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | usagetype = Desktop | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the AUR, Arch's well known user repository, possible. === Philosophy === ... === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 49eccb7610d88ba0e7fcce895fb491d99bf4e7cb 0 225 585 2024-06-05T13:55:47Z Atmois 13 Create RHEL page wikitext text/x-wiki {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | usagetype = Desktop, Server | website = [https://redhat.com/rhel/ redhat.com] }} Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial distribution developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat originally freely provided its source code but restricted free re-distributions of the officially supported versions of RHEL. Derivative distros such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023 Red Hat stopped publically providing the source code of RHEL however it is still avalible to customers and developers under the condition that they do not redistribute the source code.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> <references /> [[Category:Linux Distributions]] 344eae200d998101f43120d93ebc67c9c214a502 597 585 2024-06-05T14:13:42Z Ari43 20 Added controversy section, added information about business model wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | usagetype = Desktop, Server | website = [https://redhat.com/rhel/ redhat.com] }} Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial distribution developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL. However, it is still available to customers and developers under an Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] 8204a2740ca4b03edceb610bbc2c35aac940aaf6 598 597 2024-06-05T14:57:57Z Atmois 13 Readded refrenece to article on RHEL removing public avalibility of source code wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | usagetype = Desktop, Server | website = [https://redhat.com/rhel/ redhat.com] }} Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial distribution developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> However, it is still available to customers and developers under an Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] 3ba91c42c6db10c2488df9d7bd40414b2e9e43b5 599 598 2024-06-05T15:06:50Z Atmois 13 Put the right reference in wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | usagetype = Desktop, Server | website = [https://redhat.com/rhel/ redhat.com] }} Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial distribution developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under an Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] eb57cfd4459347e06d51a942520d4ef2147cad4f 600 599 2024-06-05T15:27:41Z Sodium 9 Fixed minor grammatical error wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | usagetype = Desktop, Server | website = [https://redhat.com/rhel/ redhat.com] }} Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial distribution developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] a7a3bebe1f6224beabf9dea339a4445599781f9c 0 198 586 579 2024-06-05T13:56:29Z Atmois 13 Add link to RHEL page wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== [[Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== [[RHEL|Red Hat Enterprise Linux (RHEL)]] is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] b9f6812bd04027b9448f67520c4ff49e883458e6 622 586 2024-06-06T02:31:45Z PratyushKing 26 added arch based and debian based distros wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- |EndeavourOS<ref>https://endeavouros.com/</ref> |Arch but simplified for new users providing an easy way to install and setup with a lot of friendly GUI tools to update/rank mirrors and easily update system without requiring any Arch Linux experience. |- |ArcoLinux<ref>https://arcolinux.com/</ref> |Basically simplified Arch Linux but with a lot of themes, customization and plenty of Desktop Environments, Window Managers and configurations. A good distribution for tinkerers. |- |Manjaro<ref>https://manjaro.org/</ref> |A once loved community project that had the best graphical AUR package management system that still is decent but causes a lot of package breakages<ref>https://forum.manjaro.org/t/something-is-just-breaking-my-installation/92088<nowiki/>https://forum.manjaro.org/t/update-breaks-the-manjaro-os/56107<nowiki/>https://www.reddit.com/r/ManjaroLinux/comments/gt89rj/manjaro_breaking_and_stability_issues/</ref> and somehow cyber attacks at the AUR repository (via pamac).<ref>https://www.reddit.com/r/archlinux/comments/mz3biz/is_the_aur_down_for_everyone/<nowiki/>https://www.linux.org/threads/manjaro-accidently-ddosed-the-aur.34248/</ref> |- |Artix Linux<ref>https://sourceforge.net/projects/artix-linux/</ref> |This is what people like to call a, "protest distro". It is basically Arch Linux but without <code>systemd</code>. Yeah, not much else. It's installer is quite confusing and causes a lot of new users to have issues. |- |Garuda Linux<ref>https://sourceforge.net/projects/garuda-linux/</ref> |One of the more fancy Arch Linux based distributions where you get a lot of cool themes with their desktop environments and certain window managers. You can however get all the themes that Garuda provides literally anywhere else on the internet but hey if you want to save time customizing, Garuda gives you a good out-of-the-box impression of Arch Linux with a very nice and simple installation process. It is Arch Linux but more easy to setup. |- |SteamOS<ref>https://store.steampowered.com/steamos</ref> |Not much important here but a notable distribution for those who use Steam handhelds, it is based on Arch Linux. |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- |Ubuntu<ref>https://ubuntu.com/</ref> |A very popular distribution that once was the best of them all but nowadays has been subtly ignored from the community due to the lack of Canonical's (parent company) decisions. You can still use it but it has a lot of things you would want to get rid of (snaps, telemetry, etc) |- |LMDE (Linux Mint)<ref>https://www.linuxmint.com/download_lmde.php</ref> |LMDE is Linux Mint Debian Edition, it is essentially Linux Mint but directly based on Debian rather than Ubuntu. A very nice pick for beginners. |- |Linux Mint<ref>https://www.linuxmint.com/download.php</ref> |The regular Linux Mint that features Ubuntu at it's core but stripped of all bad decisions of Canonical, it provides a lot of convenient features (printer support, etc) and is a quite stable distribution. |- |Pop!_OS<ref>https://pop.system76.com/</ref> |One of the most ease to use distribution for any MacOS user who switches to Linux. It is made by System76 and assures a cozy, nice-looking distribution. It has not been updated in a while but their COSMIC Desktop Environment is almost finished, as soon as it does it will take become the best again. It also has amazing NVIDIA support and has a very nice application installing software. |- |Rhino Linux<ref>https://rhinolinux.org/</ref> |One of the more recent ones, Rhino Linux (made by AJ) is a rolling release distribution that focuses on the ease of users, it has its own package manager (started as a wrapper) that installs and updates both from apt (which in this case is nala, a better frontend) and pacstall (their own in-house replacement to AUR). Overall, an awesome distribution for anyone looking for an arch-like alternative. It also features its own Unicorn Desktop Environment that is based of XFCE and looks quite nice. It's package manager is named <code>rpk</code> which is Rhino Packager. It will update your whole system with ease. It is very easy to install and a drop-in replacement to people coming from MacOS |- |Devuan<ref>https://www.devuan.org/</ref> |It is yet another "protest distribution". Similar to Artix except it is Debian or in other words it is Debian without <code>systemd</code>. Yeah, that's it! |- |PeppermintOS<ref>https://peppermintos.com/</ref> |A very easy to use Debian-based stable distribution allowing a very minimal setup, it also has ISOs with Devuan base. |} ==== Fedora Based ==== [[Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== [[RHEL|Red Hat Enterprise Linux (RHEL)]] is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] f84358df73429e42cff3bef57150a6b53817540f 626 622 2024-06-06T04:07:06Z PratyushKing 26 added Gentoo Based distros, added cite references to Fedora Based and Gentoo Based wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description !Beginner Friendly % |- |EndeavourOS<ref>https://endeavouros.com/</ref> |Arch but simplified for new users providing an easy way to install and setup with a lot of friendly GUI tools to update/rank mirrors and easily update system without requiring any Arch Linux experience. |80% |- |ArcoLinux<ref>https://arcolinux.com/</ref> |Basically simplified Arch Linux but with a lot of themes, customization and plenty of Desktop Environments, Window Managers and configurations. A good distribution for tinkerers. |55% |- |Manjaro<ref>https://manjaro.org/</ref> |A once loved community project that had the best graphical AUR package management system that still is decent but causes a lot of package breakages<ref>https://forum.manjaro.org/t/something-is-just-breaking-my-installation/92088<nowiki/>https://forum.manjaro.org/t/update-breaks-the-manjaro-os/56107<nowiki/>https://www.reddit.com/r/ManjaroLinux/comments/gt89rj/manjaro_breaking_and_stability_issues/</ref> and somehow cyber attacks at the AUR repository (via pamac).<ref>https://www.reddit.com/r/archlinux/comments/mz3biz/is_the_aur_down_for_everyone/<nowiki/>https://www.linux.org/threads/manjaro-accidently-ddosed-the-aur.34248/</ref> |25% |- |Artix Linux<ref>https://sourceforge.net/projects/artix-linux/</ref> |This is what people like to call a, "protest distro". It is basically Arch Linux but without <code>systemd</code>. Yeah, not much else. It's installer is quite confusing and causes a lot of new users to have issues. |30% |- |Garuda Linux<ref>https://sourceforge.net/projects/garuda-linux/</ref> |One of the more fancy Arch Linux based distributions where you get a lot of cool themes with their desktop environments and certain window managers. You can however get all the themes that Garuda provides literally anywhere else on the internet but hey if you want to save time customizing, Garuda gives you a good out-of-the-box impression of Arch Linux with a very nice and simple installation process. It is Arch Linux but more easy to setup. |60% |- |SteamOS<ref>https://store.steampowered.com/steamos</ref> |Not much important here but a notable distribution for those who use Steam handhelds, it is based on Arch Linux. |N/A (it is not a desktop OS) |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description !Beginner Friendly % |- |Ubuntu<ref>https://ubuntu.com/</ref> |A very popular distribution that once was the best of them all but nowadays has been subtly ignored from the community due to the lack of Canonical's (parent company) decisions. You can still use it but it has a lot of things you would want to get rid of (snaps, telemetry, etc) |85% |- |LMDE (Linux Mint)<ref>https://www.linuxmint.com/download_lmde.php</ref> |LMDE is Linux Mint Debian Edition, it is essentially Linux Mint but directly based on Debian rather than Ubuntu. A very nice pick for beginners. |90% |- |Linux Mint<ref>https://www.linuxmint.com/download.php</ref> |The regular Linux Mint that features Ubuntu at it's core but stripped of all bad decisions of Canonical, it provides a lot of convenient features (printer support, etc) and is a quite stable distribution. |95% |- |Pop!_OS<ref>https://pop.system76.com/</ref> |One of the most ease to use distribution for any MacOS user who switches to Linux. It is made by System76 and assures a cozy, nice-looking distribution. It has not been updated in a while but their COSMIC Desktop Environment is almost finished, as soon as it does it will take become the best again. It also has amazing NVIDIA support and has a very nice application installing software. |N/A (it is 2 years old right now and an update is yet to be pushed) |- |Rhino Linux<ref>https://rhinolinux.org/</ref> |One of the more recent ones, Rhino Linux (made by AJ) is a rolling release distribution that focuses on the ease of users, it has its own package manager (started as a wrapper) that installs and updates both from apt (which in this case is nala, a better frontend) and pacstall (their own in-house replacement to AUR). Overall, an awesome distribution for anyone looking for an arch-like alternative. It also features its own Unicorn Desktop Environment that is based of XFCE and looks quite nice. It's package manager is named <code>rpk</code> which is Rhino Packager. It will update your whole system with ease. It is very easy to install and a drop-in replacement to people coming from MacOS |80% |- |Devuan<ref>https://www.devuan.org/</ref> |It is yet another "protest distribution". Similar to Artix except it is Debian or in other words it is Debian without <code>systemd</code>. Yeah, that's it! |30% |- |PeppermintOS<ref>https://peppermintos.com/</ref> |A very easy to use Debian-based stable distribution allowing a very minimal setup, it also has ISOs with Devuan base. |60% |} ==== Fedora Based ==== [[Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description !Beginner Friendly % |- |Nobara Project<ref>https://nobaraproject.org/</ref> |"The Nobara Project, to put it simply, is a modified version of Fedora Linux with user-friendly fixes added to it." - Nobara Team |90% |- |QubesOS<ref>https://www.qubes-os.org/</ref> |A very sophisticated distribution that ensures each app being in it's own whole virtual system which gives you the most privacy out of any distribution. It is very resource-taking for that reason too but you do get the most security (or as it says on the website, "Reasonable security"). |15% |- |VanillaOS<ref>https://vanillaos.org/</ref> |An immutable distribution that prevents any user to cause package breakages, what it means is that the whole system after being setup in the regular form is locked permanently only allowing new virtual machines to take up disk space, it's primary source of applications is from the Fedora's immutable package manager or a better Distrobox GUI to allow you to use software from any distribution. |45% |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description !Beginner Friendly % |- |ChromiumOS<ref>https://www.chromium.org/chromium-os/</ref> |Yeah, all of you saw that coming, ChromiumOS despite using a heavily modified Gentoo base, it is still... a Gentoo base. |85% |- |ChromeOS Flex<ref>https://chromeos.google/products/chromeos-flex/</ref> |Same here, it is a very heavily modified Gentoo kernel for laptops or PCs that are not ChromeOS compatible hardware. |85% |- |Funtoo<ref>http://www.funtoo.org/Welcome</ref> |Funtoo is a community-developed Linux meta-distribution evolved from Gentoo, best optimized for performance on latest Intel or AMD hardware. |20% |- |Xenia Linux<ref>https://xenialinux.com/</ref> |An immutable modern distribution to get an up-to-date and stable desktop with pre-built ISOs including DEs. Really easy to install if you know some extent of Gentoo. |25% |} ==== Red Hat Enterprise Based ==== [[RHEL|Red Hat Enterprise Linux (RHEL)]] is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] e38dc4d694c2a4669a02a8f93a9416c6bf22070c 629 626 2024-06-06T07:19:47Z Reverted edits by [[Special:Contributions/PratyushKing|PratyushKing]] ([[User talk:PratyushKing|talk]]) to last revision by [[User:Atmois|Atmois]] wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== [[Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== [[RHEL|Red Hat Enterprise Linux (RHEL)]] is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== Slackware is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] b9f6812bd04027b9448f67520c4ff49e883458e6 0 164 587 440 2024-06-05T14:00:54Z Ari43 20 Organize page, add Wiki section wikitext text/x-wiki == Introduction == The Linux community is filled to the brim with awesome projects and various other guides worth checking out, Here's some great ones that we've found! == Guides == * https://www.privacyguides.org/ * https://awesome-privacy.xyz * https://brainfucksec.github.io/firefox-hardening-guide * https://rentry.co/fmhy-guides == Wikis == * https://wiki.archlinux.org/ * https://wiki.gentoo.org/ * https://wiki.debian.org/ == Tools == * https://christitus.com/windows-tool/ - Used for debloating and removing telemetry from Windows * https://alternativeto.net - A tool to find alternatives to popular software [[Category:Guides]] a40705e9b2d996b06c6d9bd23b130e2d028ab657 605 587 2024-06-05T20:35:43Z Asiliria 7 Formality, thorough extra details wikitext text/x-wiki == Introduction == The Linux community is abundant with awesome projects and various other guides worth checking out, Here's some great ones that we have found - keep in mind that, while these guides are very useful, they are not fully exhaustive. More than likely you discover new software every day! * Privacy is not an end goal, but a consistent journey that needs to be taken very seriously. ''Always'' seek help when in doubt and ensure you take everything with a grain of salt. ''Do not just blindly follow guides but use your own intuition!'' == Guides == * https://www.privacyguides.org/ - An essential guide to learning not just ''how'' to begin your privacy journey online but offers a comprehensive explanation of abstract privacy concepts that is simple to understand and by extension ''is assuredly not easy or quick -'' read with an open mind! ** https://awesome-privacy.xyz - More of a guide to tools you may find yourself wanting to use to enhance privacy, rather than an explanation. The next step from Privacy Guides, essentially. ** https://www.privacytools.io/ - Similar to Awesome Privacy, and offers a wide range of tools. This specific website is recommended very frequently. * https://brainfucksec.github.io/firefox-hardening-guide - A guide to "de-Mozilla" and security-harden Firefox. Assess whether or not this is a good option for you - ''similar to privacy, it is not an easy process.'' * https://rentry.co/fmhy-guides - General, yet extremely useful and even nuanced guides that you may find yourself needing for something very specific and hard to find on the internet. * https://github.com/luong-komorebi/Awesome-Linux-Software - Very extensive guide of not solely Linux software but mostly open-source software that has many use cases in mind. [[Choosing A Linux Distribution|May be helpful in picking a flavor of Linux for your specific use cases.]] == Wikis == * https://wiki.archlinux.org/ for Arch Linux; * https://wiki.gentoo.org/ for Gentoo; * https://wiki.debian.org/ for Debian. == Tools == * https://christitus.com/windows-tool/ - Used for debloating and removing telemetry from Windows. * https://alternativeto.net - A tool to find alternatives to popular software, both open-source and proprietary. [[Category:Guides]] 993c67c1852c0711e772d2c090e52fb3981ab289 0 203 593 573 2024-06-05T14:06:16Z Ari43 20 Changes for clarity wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | usagetype = Desktop, Server | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]] [https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around user customization. This distribution, in addition to having the systemd init system, also provides its own init system known as OpenRC. Unlike other Linux distributions, everything you install is compiled on the local system. As such, users can use compile flags, known as 'Use Flags,' to help them fit their system to their use case. .<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 0741318f01ff445a97019acf2461174586441519 0 217 595 575 2024-06-05T14:08:23Z Sodium 9 Added links to RHEL wikitext text/x-wiki {{DistributionInfobox|title=Fedora Linux|image=[[File:Fedora logo.svg|Fedora_logo]]|caption=The Fedora Linux logo|releasestatus=Maintained|releasemodel=Semi-Rolling Release|packagemanager=[[dnf]]|usagetype=Desktop, Server, Cloud|website=[https://fedoraproject.org/ fedoraproject.org]}}'''Fedora Linux''' is an independent [[Linux]] distribution<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being [[RHEL|Red Hat Enterprise Linux]] (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] f66c84237649a63a5ae920520692f7bbc2ebd45a 0 169 601 577 2024-06-05T18:05:36Z Atmois 13 Add links and remove wierd spacing wikitext text/x-wiki == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [https://pacman.archlinux.page/ pacman] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [https://wiki.debian.org/Apt apt] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and is maintained by [[RHEL|Red Hat]]. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [https://wiki.gentoo.org/wiki/Portage Portage] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. [[Category:Terminology]] d14839fc218dc2cdd5634d067cf7d2d7c11349a4 606 601 2024-06-05T20:37:30Z Change pacman link wikitext text/x-wiki == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [https://wiki.debian.org/Apt apt] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and is maintained by [[RHEL|Red Hat]]. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [https://wiki.gentoo.org/wiki/Portage Portage] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. [[Category:Terminology]] 7cff52c28f36a8a913d41b29533f86cec780d17c 0 223 602 581 2024-06-05T18:53:57Z Atmois 13 Add links wikitext text/x-wiki == Distrohopping == Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (eg. FSF approved distribution) * Ecosystem or Tooling (eg. libc, package manager, coreutils, init system) * Experimentation * Customization ... and many more. This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (eg. Debianisms, [[Package manager|package managers]], init systems) * Opinionated design philosophies (eg. Nix, Guix, Fedora Atomic) * Additional configuration needs (eg. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (eg. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (eg. Liberapay, Github sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] 140f3a7957425866348954c3241abf6a48df6f09 0 218 604 547 2024-06-05T20:32:40Z PratyushKing 26 add some notes for window managers and added fedora to distros wikitext text/x-wiki == Introduction == Linux is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the desktop environment (or window manager) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like KDE or Gnome may be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |XFCE | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to keyboard focus * Requires significant text-based configuration to fit the preferences of the user * Requires a lot of external packages for any popular program (example: keyrings, polkit, graphical toolkits, settings apps, etc) |Not recommended for new users and requires a lot of command line knowledge for any sort of troubleshooting. |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |Debian<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |Arch Linux<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * Arch Linux will not be covered in this article |- |Fedora<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considerably user-friendly with tons of guides. * A always supported backing from RedHat and being in general more stable than Arch Linux. | * Fedora (with the default GNOME) is very resource-taking. * Has a lot less documentation and has some level of learning curve. | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | * Please do note that the <code>rpm</code> package format is generally lot less used by package creators hence creating a lack of packages, please just use a converter like <code>alien</code> to convert rpm to deb.<ref>https://www.thegeekstuff.com/2010/11/alien-command-examples/</ref> * The installer is a bit more verbose for the beginners and requires a little bit more attention to not mess up. * If you have a more minimal system, please use a Fedora Spin, recommended is the XFCE spin. |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> 0e32708a8073ffeec3d68964d6f6ac7bae63716f 0 227 607 2024-06-05T20:50:13Z Create start of i3 page. wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/, i3wm.org]}}'''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layours, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref>Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> 0f8de6b0c005b18fad18841e41b997100cd1e474 609 607 2024-06-05T20:56:21Z Add DE category - might change to extra "window manager" category later. wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/, i3wm.org]}}'''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layours, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref>Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> [[Category:Desktop Environments]] 44b728c4555bc514f9ea5f5a47d301076306b625 611 609 2024-06-05T20:59:18Z Add a screenshot of a typical i3 session. wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/, i3wm.org]}} [[File:I3 window manager screenshot.png|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layours, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref>Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> [[Category:Desktop Environments]] 765900d75782d5f1a0a23d7ea510637d16d6cf83 612 611 2024-06-05T21:07:22Z Fix typo wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/, i3wm.org]}} [[File:I3 window manager screenshot.png|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref>Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> [[Category:Desktop Environments]] d1223a9ecee6a6cd1e13d8856d8f017a015d5b38 616 612 2024-06-05T23:17:28Z Ryna 21 Fixed a link directing to a 404 page wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:I3 window manager screenshot.png|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref>Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> [[Category:Desktop Environments]] fce1b0f0386d6c3bbcba3c2df056b0918ab65984 620 616 2024-06-06T01:54:39Z Asiliria 7 A silly naming scheme thing. I've seen this too often wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:I3 window manager screenshot.png|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> It is not to be confused with the Intel Core i3, which is a small mistake from beginners. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref>Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> [[Category:Desktop Environments]] a31f60eecdc7a20e731c7248c335ca55eed622e2 623 620 2024-06-06T03:11:07Z Ryna 21 Reworded wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:I3 window manager screenshot.png|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref>Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> [[Category:Desktop Environments]] 97e4c81f8ccca8aa094e21b84416e0a1743f6399 0 176 613 526 2024-06-05T21:33:23Z Asiliria 7 Major edits to description and details, features section wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak (is this true? - verify), and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. <references /> [[Category:Desktop Environments]] 3dcbf35995eb301065e640612ff256dfb651a848 0 228 614 2024-06-05T22:00:58Z PratyushKing 26 added the AUR page and a LOT of content in it wikitext text/x-wiki AUR which is also known as the '''A'''rch '''U'''ser '''R'''epository is a community-driven repository of PKGBUILDs, anyone can upload a package to the AUR (we will talk about how to do that in this article) and anyone can take down a package too from the AUR which just a simple letter to the mailing list (which stats say that at least 2-3 people are always active trying to look out for malicious PKGBUILD files). Basically, all the PKGBUILD is, it's a way to create an Arch Package, typically having an extension of <code>.pkg.tar.zst</code> (pkg meaning package, tar being a way to merge multiple files/folders into one, zst being a way to compress the file). Such a package with that extension can be installed via the command <code>sudo pacman -U <file>.pkg.tar.zst</code>. However, we would not be going in detail about that. AUR is also very much known to have broken packages (as later said in this article, you can easily add a package to AUR with 0 pushbacks 90% of the time), however if you read the PKGBUILDs (with an AUR helper that gives you the option to do so) then you can easily figure out if it will install or not. In a simple context, the average PKGBUILD will have two functions, it will be structured and functioned just like a regular bash script with metadata at top and two functions below, first function is the <code>prepare()</code> function and the other is <code>package()</code> function, to be short : the prepare function creates a directory for the package it is supposed to make and then adds all binaries, config files into how pacman will understand, the package function will just add final scripts, make the package (via <code>makepkg</code>) and then install it through pacman, however this is not always the case since all PKGBUILDs are just like regular bash scripts, you can just have a prepare function to check the files downloaded through source and the package function just putting the files in user directories, this way you won't need root permissions at all. We will see that in detail.<ref>https://wiki.archlinux.org/title/Arch_User_Repository</ref> === Significance === AUR being one of the biggest package sources in the Linux community, it has over 60,000 packages and active volunteers to quality check the unfiltered packages. AUR packages are very creative in their own regard also, from people using package converters to convert any deb or rpm package to an arch-compatible package to people using windows electron programs and modifying it to work on Linux, it is no surprise that you can find almost any package possible on the AUR. === Safety === With the great power of the AUR, you will be surprised by how secure it is, most people say it is very unsafe, however if you get the habit of reading the PKGBUILD files before installing them, you will never run into issues, but this is not even that severe of a security flaw due to how many people are always checking new packages submitted. The main issue starts with a famous term "dependency hell" which to be short means "installing separate packages that require a certain dependency of a specific version but they both have separate version requirements so you end up with a broken installation". Yeah, it sounds very complicated, because it is. Basically, if you have any 2 separate packages, one could be from your extra or core repositories (check the [[Pacman#Repositories|pacman]] page to learn about default repositories) and the other one could be from the AUR, well if the package maintainer of the AUR package and the package from the extra's repository, let's say depends on <code>ffmpeg</code> and it requires a very old version, well since the packages on the extra's repository are always kept up-to-date as soon as possible, you might end up having a "dependency hell" where pacman wants to use a newer version for the package in extra repository but the AUR package requires an older version and then you end up with a corrupted package and if the package is an important package for the system, you will end up with a full corrupted install. === Naming Scheme === This is a very strictly enforced naming scheme in the AUR and it is basically adding a suffix that determines the package type.. The main ones are: * <code>-git</code> : which means that the package will clone and build manually through a git repository. (Most likely GitHub or GitLab repository) * <code>-bin</code> : which means that the package will just fetch a pre-compiled binary and install the configuration files. (RECOMMENDED) * No Suffix : which means that the package is either proprietary or it is compiling or source-based package. Just see the PKGBUILD for this one. Now, ideally you would pick the <code>-bin</code> package or a proprietary package with no suffix meaning that it will just use binary anyways (because you cannot manually compile programs without source code), this is because it is much faster to use a pre-compiled binary as opposed to letting it manually clone, build and install. === Installing AUR packages === This might be a little complicated for those who aren't familiar with the way Arch Linux packages work but it is quite easy to grab. Basically, if you used <code>archinstall</code> for your system, you probably have this package called <code>base-devel</code>, it means base development and this is what allows us to install packages from the AUR repository, you must have <code>git</code> installed too since we need to clone packages. If you installed Arch Linux the manual way you have probably pacstrapped it because it is recommended in the ArchWiki, if you haven't then please install <code>base-devel</code> through pacman. To summarize, installing any package from AUR is basically getting a PKGBUILD that tells the system to create a package and install, it is kind of weird but essentially an AUR package is instructions to make an Arch Linux package. We will try to install the <code>waterfox-bin</code> package because it is not available in the extra or core repository. (To understand the <code>-bin</code> suffix, please check the naming scheme above). To install <code>waterfox-bin</code> via the AUR, you have to install <code>git</code> and <code>base-devel</code> via pacman as said earlier. Then you will use <code>git clone <nowiki>https://aur.archlinux.org/waterfox-bin.git</nowiki></code>, that will clone the PKGBUILD for Waterfox and put it in your current directory. Use <code>cd waterfox-bin</code> to go inside that directory and then run <code>makepkg -si</code> which will use <code>makepkg</code> to make the package and ask to install it. What we are doing here is using a single file to build an Arch Linux package for us and install that. This will successfully install the package. Yeah, it was that easy, to make it more easy however, we have AUR Helpers. === AUR Helpers === (WORK IN PROGRESS) 4309bfd166587114c2a2eb0ca8ab4dfdf551aa65 619 614 2024-06-06T01:16:49Z PratyushKing 26 added topic AUR Helpers wikitext text/x-wiki AUR which is also known as the '''A'''rch '''U'''ser '''R'''epository is a community-driven repository of PKGBUILDs, anyone can upload a package to the AUR (we will talk about how to do that in this article) and anyone can take down a package too from the AUR which just a simple letter to the mailing list (which stats say that at least 2-3 people are always active trying to look out for malicious PKGBUILD files). Basically, all the PKGBUILD is, it's a way to create an Arch Package, typically having an extension of <code>.pkg.tar.zst</code> (pkg meaning package, tar being a way to merge multiple files/folders into one, zst being a way to compress the file). Such a package with that extension can be installed via the command <code>sudo pacman -U <file>.pkg.tar.zst</code>. However, we would not be going in detail about that. AUR is also very much known to have broken packages (as later said in this article, you can easily add a package to AUR with 0 pushbacks 90% of the time), however if you read the PKGBUILDs (with an AUR helper that gives you the option to do so) then you can easily figure out if it will install or not. In a simple context, the average PKGBUILD will have two functions, it will be structured and functioned just like a regular bash script with metadata at top and two functions below, first function is the <code>prepare()</code> function and the other is <code>package()</code> function, to be short : the prepare function creates a directory for the package it is supposed to make and then adds all binaries, config files into how pacman will understand, the package function will just add final scripts, make the package (via <code>makepkg</code>) and then install it through pacman, however this is not always the case since all PKGBUILDs are just like regular bash scripts, you can just have a prepare function to check the files downloaded through source and the package function just putting the files in user directories, this way you won't need root permissions at all. We will see that in detail.<ref>https://wiki.archlinux.org/title/Arch_User_Repository</ref> === Significance === AUR being one of the biggest package sources in the Linux community, it has over 60,000 packages and active volunteers to quality check the unfiltered packages. AUR packages are very creative in their own regard also, from people managing to install packages from other formats (.deb) where it's not even made for Arch Linux<ref>https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=google-chrome</ref> to people using Windows Electron applications and modifying it to work on Linux<ref>https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=deezer</ref>, it is no surprise that you can find almost any package possible on the AUR. === Safety === With the great power of the AUR, you will be surprised by how secure it is, most people say it is very unsafe, however if you get the habit of reading the PKGBUILD files before installing them, you will never run into issues, but this is not even that severe of a security flaw due to how many people are always checking new packages submitted. The main issue starts with a famous term "dependency hell" which to be short means "installing separate packages that require a certain dependency of a specific version but they both have separate version requirements so you end up with a broken installation". Yeah, it sounds very complicated, because it is. Basically, if you have any 2 separate packages, one could be from your extra or core repositories (check the [[Pacman#Repositories|pacman]] page to learn about default repositories) and the other one could be from the AUR, well if the package maintainer of the AUR package and the package from the extra's repository, let's say depends on <code>ffmpeg</code> and it requires a very old version, well since the packages on the extra's repository are always kept up-to-date as soon as possible, you might end up having a "dependency hell" where pacman wants to use a newer version for the package in extra repository but the AUR package requires an older version and then you end up with a corrupted package and if the package is an important package for the system, you will end up with a full corrupted install. === Naming Scheme === This is a very strictly enforced naming scheme in the AUR and it is basically adding a suffix that determines the package type.. The main ones are: * <code>-git</code> : which means that the package will clone and build manually through a git repository. (Most likely GitHub or GitLab repository) * <code>-bin</code> : which means that the package will just fetch a pre-compiled binary and install the configuration files. (RECOMMENDED) * No Suffix : which means that the package is either proprietary or it is compiling or source-based package. Just see the PKGBUILD for this one. Now, ideally you would pick the <code>-bin</code> package or a proprietary package with no suffix meaning that it will just use binary anyways (because you cannot manually compile programs without source code), this is because it is much faster to use a pre-compiled binary as opposed to letting it manually clone, build and install. === Installing AUR packages === This might be a little complicated for those who aren't familiar with the way Arch Linux packages work but it is quite easy to grab. Basically, if you used <code>archinstall</code> for your system, you probably have this package called <code>base-devel</code>, it means base development and this is what allows us to install packages from the AUR repository, you must have <code>git</code> installed too since we need to clone packages. If you installed Arch Linux the manual way you have probably pacstrapped it because it is recommended in the ArchWiki, if you haven't then please install <code>base-devel</code> through pacman. To summarize, installing any package from AUR is basically getting a PKGBUILD that tells the system to create a package and install, it is kind of weird but essentially an AUR package is instructions to make an Arch Linux package. We will try to install the <code>waterfox-bin</code> package because it is not available in the extra or core repository. (To understand the <code>-bin</code> suffix, please check the naming scheme above). To install <code>waterfox-bin</code> via the AUR, you have to install <code>git</code> and <code>base-devel</code> via pacman as said earlier. Then you will use <code>git clone <nowiki>https://aur.archlinux.org/waterfox-bin.git</nowiki></code>, that will clone the PKGBUILD for Waterfox and put it in your current directory. Use <code>cd waterfox-bin</code> to go inside that directory and then run <code>makepkg -si</code> which will use <code>makepkg</code> to make the package and ask to install it. What we are doing here is using a single file to build an Arch Linux package for us and install that. This will successfully install the package. Yeah, it was that easy, to make it more easy however, we have AUR Helpers. === AUR Helpers === There are majorly 8 AUR helpers but only 3 most commonly used ones, namely: * <code>yay</code><ref>https://github.com/Jguer/yay</ref> (Yet another yogurt) : This is the most widely used AUR helper and is also surprisingly the most downloaded package on the AUR! It is written in go but it has a lot of propaganda behind it that it is dying and it is dead, one of the main developers from <code>yay</code> actually started <code>paru</code>, which is our next AUR helper. * <code>paru</code><ref>https://github.com/morganamilo/paru</ref> : This is by far the second most recognized AUR helper in the community and it is the most recent one, being made by one of the main developers of <code>yay</code>, it should be no surprise here that it is fully feature packed and offers a lot of features, we recommend this the most due to how it always forces you to review PKGBUILDs that you try to install, this always keeps you safe and forces you to be careful. It can get annoying sometimes but it is a very good habit to maintain especially if you like to scavenger hunt new packages every day. This AUR helper is written in Rust. * <code>pacaur</code><ref>https://github.com/rmarquis/pacaur</ref> : This is out of date nowadays and does not receive any support due to it lacking a lot of features, originally it was started as an AUR helper that minimizes user interaction but it is not being actively used right now and it is written in Bash. It is quite nostalgic to a lot of people so it is still fairly widely used. There are other AUR helpers but these 3 are the most common and easiest to use. We will focus with <code>paru</code> because of it being the most verbose AUR helper, it has some unsafe flags but you won't encounter it in most cases. To install an AUR helper, you do it just like a package except we will use the <code>-bin</code> versions of the package, see this is what most beginners in the community do wrong, they install the regular without <code>-bin</code> suffix AUR helper package build file. As we saw earlier at naming schemes, without that suffix, the package will be manually cloned and compiled then put into your system, but using the <code>-bin</code> packages just use a pre-compiled binary. This is a guide to install <code>paru</code> AUR helper but you can use the same with any AUR helper by just switching the names. # Run this command <code>sudo pacman -S base-devel git --needed --noconfirm</code> . This command looks very scary but it just installs git and the required package commands we want, it will not ask the user for any <code>(y/n)</code> but rather just do it and it will also prevent reinstalling so if you have both of these installed, it will just say that it is already installed and that it is skipping. # Then you run <code>git clone https://aur.archlinux.org/paru-bin.git --depth=1</code>, that will download our PKGBUILD from the AUR, this is one of the most common beginner mistake, they complain it takes too long but they never download the binary PKGBUILD script. The <code>--depth=1</code> flag is to just tell git to not get previous commit information and only get commit information from the last <n> number of commits, which here is 1 since we will just build and remove that directory. Once it is cloned, <code>cd</code> into that directory. # Once you are inside the directory, run <code>makepkg -si</code> and then wait, depending on your network you should take roughly 2-10 minutes to download and install. After it is done, just run <code>paru</code> and check. (if you do leave your devices and when you come back you see that it was waiting for root permission and that it had quit now saying timeout exceeded, you can just do a <code>ls</code> and check, there should be a package file [extension: <code>.pkg.tar.zst</code>], if it does then just do <code>sudo pacman -U <file>.pkg.tar.zst</code>) Done! Now you can enjoy installing packages. With paru you might want to change this one main thing, go into your <code>/etc/paru.conf</code> file with your favorite text editor. The most important thing you have to change is: Since paru by default when just ran with example: <code>paru brave</code>, it will by default print from first to last but there's a problem, now you cannot get the most relevant one to your search and end up with a lot of useless packages at the start, well you should un-comment the line where it says <code>BottomUp</code> in the configuration file, if it is not there just add a new line under the options category and write <code>BottomUp</code>. Other than that you can play around and add or remove flags however you like but don't forget to add/uncomment <code>Color</code> from the <code>/etc/pacman.conf</code> file because yes that effects to paru also. You can add <code>ILoveCandy</code> for quirky progress bars. === Further Dive into AUR Helpers === (WORK IN PROGRESS) e0ab41f6b197f1675e9fd1fc342b5d83e8adab6c 621 619 2024-06-06T01:55:39Z PratyushKing 26 general aur helper commands added wikitext text/x-wiki AUR which is also known as the '''A'''rch '''U'''ser '''R'''epository is a community-driven repository of PKGBUILDs, anyone can upload a package to the AUR (we will talk about how to do that in this article) and anyone can take down a package too from the AUR which just a simple letter to the mailing list (which stats say that at least 2-3 people are always active trying to look out for malicious PKGBUILD files). Basically, all the PKGBUILD is, it's a way to create an Arch Package, typically having an extension of <code>.pkg.tar.zst</code> (pkg meaning package, tar being a way to merge multiple files/folders into one, zst being a way to compress the file). Such a package with that extension can be installed via the command <code>sudo pacman -U <file>.pkg.tar.zst</code>. However, we would not be going in detail about that. AUR is also very much known to have broken packages (as later said in this article, you can easily add a package to AUR with 0 pushbacks 90% of the time), however if you read the PKGBUILDs (with an AUR helper that gives you the option to do so) then you can easily figure out if it will install or not. In a simple context, the average PKGBUILD will have two functions, it will be structured and functioned just like a regular bash script with metadata at top and two functions below, first function is the <code>prepare()</code> function and the other is <code>package()</code> function, to be short : the prepare function creates a directory for the package it is supposed to make and then adds all binaries, config files into how pacman will understand, the package function will just add final scripts, make the package (via <code>makepkg</code>) and then install it through pacman, however this is not always the case since all PKGBUILDs are just like regular bash scripts, you can just have a prepare function to check the files downloaded through source and the package function just putting the files in user directories, this way you won't need root permissions at all. We will see that in detail.<ref>https://wiki.archlinux.org/title/Arch_User_Repository</ref> === Significance === AUR being one of the biggest package sources in the Linux community, it has over 60,000 packages and active volunteers to quality check the unfiltered packages. AUR packages are very creative in their own regard also, from people managing to install packages from other formats (.deb) where it's not even made for Arch Linux<ref>https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=google-chrome</ref> to people using Windows Electron applications and modifying it to work on Linux<ref>https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=deezer</ref>, it is no surprise that you can find almost any package possible on the AUR. === Safety === With the great power of the AUR, you will be surprised by how secure it is, most people say it is very unsafe, however if you get the habit of reading the PKGBUILD files before installing them, you will never run into issues, but this is not even that severe of a security flaw due to how many people are always checking new packages submitted. The main issue starts with a famous term "dependency hell" which to be short means "installing separate packages that require a certain dependency of a specific version but they both have separate version requirements so you end up with a broken installation". Yeah, it sounds very complicated, because it is. Basically, if you have any 2 separate packages, one could be from your extra or core repositories (check the [[Pacman#Repositories|pacman]] page to learn about default repositories) and the other one could be from the AUR, well if the package maintainer of the AUR package and the package from the extra's repository, let's say depends on <code>ffmpeg</code> and it requires a very old version, well since the packages on the extra's repository are always kept up-to-date as soon as possible, you might end up having a "dependency hell" where pacman wants to use a newer version for the package in extra repository but the AUR package requires an older version and then you end up with a corrupted package and if the package is an important package for the system, you will end up with a full corrupted install. === Naming Scheme === This is a very strictly enforced naming scheme in the AUR and it is basically adding a suffix that determines the package type.. The main ones are: * <code>-git</code> : which means that the package will clone and build manually through a git repository. (Most likely GitHub or GitLab repository) * <code>-bin</code> : which means that the package will just fetch a pre-compiled binary and install the configuration files. (RECOMMENDED) * No Suffix : which means that the package is either proprietary or it is compiling or source-based package. Just see the PKGBUILD for this one. Now, ideally you would pick the <code>-bin</code> package or a proprietary package with no suffix meaning that it will just use binary anyways (because you cannot manually compile programs without source code), this is because it is much faster to use a pre-compiled binary as opposed to letting it manually clone, build and install. === Installing AUR packages === This might be a little complicated for those who aren't familiar with the way Arch Linux packages work but it is quite easy to grab. Basically, if you used <code>archinstall</code><ref>https://wiki.archlinux.org/title/Archinstall</ref> for your system, you probably have this package called <code>base-devel</code>, it means base development and this is what allows us to install packages from the AUR repository, you must have <code>git</code> installed too since we need to clone packages. If you installed Arch Linux the manual way you have probably pacstrapped it because it is recommended in the ArchWiki, if you haven't then please install <code>base-devel</code> through pacman. To summarize, installing any package from AUR is basically getting a PKGBUILD that tells the system to create a package and install, it is kind of weird but essentially an AUR package is instructions to make an Arch Linux package. We will try to install the <code>waterfox-bin</code><ref name=":0">https://aur.archlinux.org/packages/waterfox-bin</ref> package because it is not available in the extra or core repository. (To understand the <code>-bin</code> suffix, please check the naming scheme above). To install <code>waterfox-bin</code><ref name=":0" /> via the AUR, you have to install <code>git</code> and <code>base-devel</code> via pacman as said earlier. Then you will use <code>git clone <nowiki>https://aur.archlinux.org/waterfox-bin.git</nowiki></code>, that will clone the PKGBUILD for Waterfox and put it in your current directory. Use <code>cd waterfox-bin</code> to go inside that directory and then run <code>makepkg -si</code> which will use <code>makepkg</code> to make the package and ask to install it. What we are doing here is using a single file to build an Arch Linux package for us and install that. This will successfully install the package. Yeah, it was that easy, to make it more easy however, we have AUR Helpers. === AUR Helpers === There are majorly 8 AUR helpers but only 3 most commonly used ones, namely: * <code>yay</code><ref>https://github.com/Jguer/yay</ref> (Yet another yogurt) : This is the most widely used AUR helper and is also surprisingly the most downloaded package on the AUR! It is written in go but it has a lot of propaganda behind it that it is dying and it is dead, one of the main developers from <code>yay</code> actually started <code>paru</code>, which is our next AUR helper. * <code>paru</code><ref>https://github.com/morganamilo/paru</ref> : This is by far the second most recognized AUR helper in the community and it is the most recent one, being made by one of the main developers of <code>yay</code>, it should be no surprise here that it is fully feature packed and offers a lot of features, we recommend this the most due to how it always forces you to review PKGBUILDs that you try to install, this always keeps you safe and forces you to be careful. It can get annoying sometimes but it is a very good habit to maintain especially if you like to scavenger hunt new packages every day. This AUR helper is written in Rust. * <code>pacaur</code><ref>https://github.com/rmarquis/pacaur</ref> : This is out of date nowadays and does not receive any support due to it lacking a lot of features, originally it was started as an AUR helper that minimizes user interaction but it is not being actively used right now and it is written in Bash. It is quite nostalgic to a lot of people so it is still fairly widely used. There are other AUR helpers but these 3 are the most common and easiest to use. We will focus with <code>paru</code> because of it being the most verbose AUR helper, it has some unsafe flags but you won't encounter it in most cases. To install an AUR helper, you do it just like a package except we will use the <code>-bin</code> versions of the package, see this is what most beginners in the community do wrong, they install the regular without <code>-bin</code> suffix AUR helper package build file. As we saw earlier at naming schemes, without that suffix, the package will be manually cloned and compiled then put into your system, but using the <code>-bin</code> packages just use a pre-compiled binary. This is a guide to install <code>paru</code> AUR helper but you can use the same with any AUR helper by just switching the names. # Run this command <code>sudo pacman -S base-devel git --needed --noconfirm</code> . This command looks very scary but it just installs git and the required package commands we want, it will not ask the user for any <code>(y/n)</code> but rather just do it and it will also prevent reinstalling so if you have both of these installed, it will just say that it is already installed and that it is skipping. # Then you run <code>git clone https://aur.archlinux.org/paru-bin.git --depth=1</code>, that will download our PKGBUILD from the AUR, this is one of the most common beginner mistake, they complain it takes too long but they never download the binary PKGBUILD script. The <code>--depth=1</code> flag is to just tell git to not get previous commit information and only get commit information from the last <n> number of commits, which here is 1 since we will just build and remove that directory. Once it is cloned, <code>cd</code> into that directory. # Once you are inside the directory, run <code>makepkg -si</code> and then wait, depending on your network you should take roughly 2-10 minutes to download and install. After it is done, just run <code>paru</code> and check. (if you do leave your devices and when you come back you see that it was waiting for root permission and that it had quit now saying timeout exceeded, you can just do a <code>ls</code> and check, there should be a package file [extension: <code>.pkg.tar.zst</code>], if it does then just do <code>sudo pacman -U <file>.pkg.tar.zst</code>) Done! Now you can enjoy installing packages. With paru you might want to change this one main thing, go into your <code>/etc/paru.conf</code> file with your favorite text editor. The most important thing you have to change is: Since paru by default when just ran with example: <code>paru brave</code>, it will by default print from first to last but there's a problem, now you cannot get the most relevant one to your search and end up with a lot of useless packages at the start, well you should un-comment the line where it says <code>BottomUp</code> in the configuration file, if it is not there just add a new line under the options category and write <code>BottomUp</code>. Other than that you can play around and add or remove flags however you like but don't forget to add/uncomment <code>Color</code> from the <code>/etc/pacman.conf</code> file because yes that effects to paru also. You can add <code>ILoveCandy</code> for quirky progress bars. === General AUR Helper Commands === Spotlight to the paru AUR helper but all these commands should work with yay which is about 90% of users when paru + yay are combined. {| class="wikitable" |+Commands List !Command !Purpose !Is marked unsafe? |- |<code>paru</code> & <code>paru -Syu</code> |Both update all packages from pacman and the AUR |<code>paru -Sy</code> is marked unsafe. |- |<code>paru <package_name></code> |This command tells paru to search the AUR and allow you to select one or multiple packages to download and install from the AUR |No |- |<code>paru -S <package_name></code> |Unless the <code>AurOnly</code> flag is not enabled in the configuration file, this will install a package if that specific name is a packge from the AUR or from pacman |No |- |<code>paru -Ss <package_name></code> |Will act the same way as <code>paru <package_name></code> would except it will not allow you to select anything but rather just print a list in the same format |No |- |<code>paru -Sua</code> |Will only upgrade packages from the AUR |No |- |<code>paru -Rns</code> |This will remove an AUR package (or a regular system package without the <code>AurOnly</code> flag) and will remove any configuration files it had. |No |- |<code>paru -Rnsc</code> |This will remove an AUR package (or a regular system package without the <code>AurOnly</code> flag) and will remove any configuration files it had except it will also remove all cascading dependencies the program had installed. |No, but it can be dangerous if you don't check the packages |} === PKGBUILDs === (WORK IN PROGRESS) 0fe3815c658f4eeecb2646bd833996067f498fe0 624 621 2024-06-06T03:21:26Z Electron271 3 Chore: Update categories wikitext text/x-wiki AUR which is also known as the '''A'''rch '''U'''ser '''R'''epository is a community-driven repository of PKGBUILDs, anyone can upload a package to the AUR (we will talk about how to do that in this article) and anyone can take down a package too from the AUR which just a simple letter to the mailing list (which stats say that at least 2-3 people are always active trying to look out for malicious PKGBUILD files). Basically, all the PKGBUILD is, it's a way to create an Arch Package, typically having an extension of <code>.pkg.tar.zst</code> (pkg meaning package, tar being a way to merge multiple files/folders into one, zst being a way to compress the file). Such a package with that extension can be installed via the command <code>sudo pacman -U <file>.pkg.tar.zst</code>. However, we would not be going in detail about that. AUR is also very much known to have broken packages (as later said in this article, you can easily add a package to AUR with 0 pushbacks 90% of the time), however if you read the PKGBUILDs (with an AUR helper that gives you the option to do so) then you can easily figure out if it will install or not. In a simple context, the average PKGBUILD will have two functions, it will be structured and functioned just like a regular bash script with metadata at top and two functions below, first function is the <code>prepare()</code> function and the other is <code>package()</code> function, to be short : the prepare function creates a directory for the package it is supposed to make and then adds all binaries, config files into how pacman will understand, the package function will just add final scripts, make the package (via <code>makepkg</code>) and then install it through pacman, however this is not always the case since all PKGBUILDs are just like regular bash scripts, you can just have a prepare function to check the files downloaded through source and the package function just putting the files in user directories, this way you won't need root permissions at all. We will see that in detail.<ref>https://wiki.archlinux.org/title/Arch_User_Repository</ref> === Significance === AUR being one of the biggest package sources in the Linux community, it has over 60,000 packages and active volunteers to quality check the unfiltered packages. AUR packages are very creative in their own regard also, from people managing to install packages from other formats (.deb) where it's not even made for Arch Linux<ref>https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=google-chrome</ref> to people using Windows Electron applications and modifying it to work on Linux<ref>https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=deezer</ref>, it is no surprise that you can find almost any package possible on the AUR. === Safety === With the great power of the AUR, you will be surprised by how secure it is, most people say it is very unsafe, however if you get the habit of reading the PKGBUILD files before installing them, you will never run into issues, but this is not even that severe of a security flaw due to how many people are always checking new packages submitted. The main issue starts with a famous term "dependency hell" which to be short means "installing separate packages that require a certain dependency of a specific version but they both have separate version requirements so you end up with a broken installation". Yeah, it sounds very complicated, because it is. Basically, if you have any 2 separate packages, one could be from your extra or core repositories (check the [[Pacman#Repositories|pacman]] page to learn about default repositories) and the other one could be from the AUR, well if the package maintainer of the AUR package and the package from the extra's repository, let's say depends on <code>ffmpeg</code> and it requires a very old version, well since the packages on the extra's repository are always kept up-to-date as soon as possible, you might end up having a "dependency hell" where pacman wants to use a newer version for the package in extra repository but the AUR package requires an older version and then you end up with a corrupted package and if the package is an important package for the system, you will end up with a full corrupted install. === Naming Scheme === This is a very strictly enforced naming scheme in the AUR and it is basically adding a suffix that determines the package type.. The main ones are: * <code>-git</code> : which means that the package will clone and build manually through a git repository. (Most likely GitHub or GitLab repository) * <code>-bin</code> : which means that the package will just fetch a pre-compiled binary and install the configuration files. (RECOMMENDED) * No Suffix : which means that the package is either proprietary or it is compiling or source-based package. Just see the PKGBUILD for this one. Now, ideally you would pick the <code>-bin</code> package or a proprietary package with no suffix meaning that it will just use binary anyways (because you cannot manually compile programs without source code), this is because it is much faster to use a pre-compiled binary as opposed to letting it manually clone, build and install. === Installing AUR packages === This might be a little complicated for those who aren't familiar with the way Arch Linux packages work but it is quite easy to grab. Basically, if you used <code>archinstall</code><ref>https://wiki.archlinux.org/title/Archinstall</ref> for your system, you probably have this package called <code>base-devel</code>, it means base development and this is what allows us to install packages from the AUR repository, you must have <code>git</code> installed too since we need to clone packages. If you installed Arch Linux the manual way you have probably pacstrapped it because it is recommended in the ArchWiki, if you haven't then please install <code>base-devel</code> through pacman. To summarize, installing any package from AUR is basically getting a PKGBUILD that tells the system to create a package and install, it is kind of weird but essentially an AUR package is instructions to make an Arch Linux package. We will try to install the <code>waterfox-bin</code><ref name=":0">https://aur.archlinux.org/packages/waterfox-bin</ref> package because it is not available in the extra or core repository. (To understand the <code>-bin</code> suffix, please check the naming scheme above). To install <code>waterfox-bin</code><ref name=":0" /> via the AUR, you have to install <code>git</code> and <code>base-devel</code> via pacman as said earlier. Then you will use <code>git clone <nowiki>https://aur.archlinux.org/waterfox-bin.git</nowiki></code>, that will clone the PKGBUILD for Waterfox and put it in your current directory. Use <code>cd waterfox-bin</code> to go inside that directory and then run <code>makepkg -si</code> which will use <code>makepkg</code> to make the package and ask to install it. What we are doing here is using a single file to build an Arch Linux package for us and install that. This will successfully install the package. Yeah, it was that easy, to make it more easy however, we have AUR Helpers. === AUR Helpers === There are majorly 8 AUR helpers but only 3 most commonly used ones, namely: * <code>yay</code><ref>https://github.com/Jguer/yay</ref> (Yet another yogurt) : This is the most widely used AUR helper and is also surprisingly the most downloaded package on the AUR! It is written in go but it has a lot of propaganda behind it that it is dying and it is dead, one of the main developers from <code>yay</code> actually started <code>paru</code>, which is our next AUR helper. * <code>paru</code><ref>https://github.com/morganamilo/paru</ref> : This is by far the second most recognized AUR helper in the community and it is the most recent one, being made by one of the main developers of <code>yay</code>, it should be no surprise here that it is fully feature packed and offers a lot of features, we recommend this the most due to how it always forces you to review PKGBUILDs that you try to install, this always keeps you safe and forces you to be careful. It can get annoying sometimes but it is a very good habit to maintain especially if you like to scavenger hunt new packages every day. This AUR helper is written in Rust. * <code>pacaur</code><ref>https://github.com/rmarquis/pacaur</ref> : This is out of date nowadays and does not receive any support due to it lacking a lot of features, originally it was started as an AUR helper that minimizes user interaction but it is not being actively used right now and it is written in Bash. It is quite nostalgic to a lot of people so it is still fairly widely used. There are other AUR helpers but these 3 are the most common and easiest to use. We will focus with <code>paru</code> because of it being the most verbose AUR helper, it has some unsafe flags but you won't encounter it in most cases. To install an AUR helper, you do it just like a package except we will use the <code>-bin</code> versions of the package, see this is what most beginners in the community do wrong, they install the regular without <code>-bin</code> suffix AUR helper package build file. As we saw earlier at naming schemes, without that suffix, the package will be manually cloned and compiled then put into your system, but using the <code>-bin</code> packages just use a pre-compiled binary. This is a guide to install <code>paru</code> AUR helper but you can use the same with any AUR helper by just switching the names. # Run this command <code>sudo pacman -S base-devel git --needed --noconfirm</code> . This command looks very scary but it just installs git and the required package commands we want, it will not ask the user for any <code>(y/n)</code> but rather just do it and it will also prevent reinstalling so if you have both of these installed, it will just say that it is already installed and that it is skipping. # Then you run <code>git clone https://aur.archlinux.org/paru-bin.git --depth=1</code>, that will download our PKGBUILD from the AUR, this is one of the most common beginner mistake, they complain it takes too long but they never download the binary PKGBUILD script. The <code>--depth=1</code> flag is to just tell git to not get previous commit information and only get commit information from the last <n> number of commits, which here is 1 since we will just build and remove that directory. Once it is cloned, <code>cd</code> into that directory. # Once you are inside the directory, run <code>makepkg -si</code> and then wait, depending on your network you should take roughly 2-10 minutes to download and install. After it is done, just run <code>paru</code> and check. (if you do leave your devices and when you come back you see that it was waiting for root permission and that it had quit now saying timeout exceeded, you can just do a <code>ls</code> and check, there should be a package file [extension: <code>.pkg.tar.zst</code>], if it does then just do <code>sudo pacman -U <file>.pkg.tar.zst</code>) Done! Now you can enjoy installing packages. With paru you might want to change this one main thing, go into your <code>/etc/paru.conf</code> file with your favorite text editor. The most important thing you have to change is: Since paru by default when just ran with example: <code>paru brave</code>, it will by default print from first to last but there's a problem, now you cannot get the most relevant one to your search and end up with a lot of useless packages at the start, well you should un-comment the line where it says <code>BottomUp</code> in the configuration file, if it is not there just add a new line under the options category and write <code>BottomUp</code>. Other than that you can play around and add or remove flags however you like but don't forget to add/uncomment <code>Color</code> from the <code>/etc/pacman.conf</code> file because yes that effects to paru also. You can add <code>ILoveCandy</code> for quirky progress bars. === General AUR Helper Commands === Spotlight to the paru AUR helper but all these commands should work with yay which is about 90% of users when paru + yay are combined. {| class="wikitable" |+Commands List !Command !Purpose !Is marked unsafe? |- |<code>paru</code> & <code>paru -Syu</code> |Both update all packages from pacman and the AUR |<code>paru -Sy</code> is marked unsafe. |- |<code>paru <package_name></code> |This command tells paru to search the AUR and allow you to select one or multiple packages to download and install from the AUR |No |- |<code>paru -S <package_name></code> |Unless the <code>AurOnly</code> flag is not enabled in the configuration file, this will install a package if that specific name is a packge from the AUR or from pacman |No |- |<code>paru -Ss <package_name></code> |Will act the same way as <code>paru <package_name></code> would except it will not allow you to select anything but rather just print a list in the same format |No |- |<code>paru -Sua</code> |Will only upgrade packages from the AUR |No |- |<code>paru -Rns</code> |This will remove an AUR package (or a regular system package without the <code>AurOnly</code> flag) and will remove any configuration files it had. |No |- |<code>paru -Rnsc</code> |This will remove an AUR package (or a regular system package without the <code>AurOnly</code> flag) and will remove any configuration files it had except it will also remove all cascading dependencies the program had installed. |No, but it can be dangerous if you don't check the packages |} === PKGBUILDs === (WORK IN PROGRESS) <references /> [[Category:Terminology]] c248e73181d8d36bc8126c8b3b5f3d575c18c17f 630 624 2024-06-06T07:31:16Z Remove opinionated page lacking sources and focusing solely on AUR helpers, neglecting the official methods for installing from the AUR. wikitext text/x-wiki The '''A'''rch '''U'''ser '''R'''epository (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref>[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref><references /> [[Category:Terminology]] b754e33db0d191e7fbabfcb0c59d5e6fddeb3c98 632 630 2024-06-06T10:03:30Z Tess moved page [[AUR]] to [[Arch User Repository]]: Move AUR to Arch User Repository wikitext text/x-wiki The '''A'''rch '''U'''ser '''R'''epository (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref>[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref><references /> [[Category:Terminology]] b754e33db0d191e7fbabfcb0c59d5e6fddeb3c98 634 632 2024-06-06T10:05:39Z wikitext text/x-wiki The '''Arch''' '''User''' '''Repository''' (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref>[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref><references /> [[Category:Terminology]] 8b55acf27449effbb4937bd90b7028aa7f4f8852 0 219 615 548 2024-06-05T23:10:17Z Ryna 21 Added some sources and offsite links wikitext text/x-wiki {{LarryInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan<ref>https://community.kde.org/Promo/Material/Mascots</ref>. Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror], KDE's default web browser<ref>https://community.kde.org/Konqi</ref>.<references /> [[Category:Mascots]] 99213417bcff6079873f80cb34903250e63a16a3 0 231 633 2024-06-06T10:03:30Z Tess moved page [[AUR]] to [[Arch User Repository]]: Move AUR to Arch User Repository wikitext text/x-wiki #REDIRECT [[Arch User Repository]] fe8958248bedc8c5d9e62e119e91caf9eb0f61c2 0 233 637 2024-06-06T13:18:53Z Andre 27 Added small description, table of info and screenshot :3 wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = pkgtool, slackpkg | usagetype = Desktop, server | website = [https://slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent Linux distribution and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. 209152d5df27766021ecf74c9c77c1d94a0da4d2 638 637 2024-06-06T13:19:54Z Add to Linux Distributions category wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = pkgtool, slackpkg | usagetype = Desktop, server | website = [https://slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent Linux distribution and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. [[Category:Linux Distributions]] bf16c931d67a54beba7e2d9cbcbaf22ae7db2bc9 639 638 2024-06-06T13:21:05Z Change logo to use wiki commons wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = pkgtool, slackpkg | usagetype = Desktop, server | website = [https://slackware.com slackware.com] }} [[File:Slackware logo.svg|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent Linux distribution and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. [[Category:Linux Distributions]] d69cf398f8e68c526e5c50582c89191f467dd2f1 0 233 640 639 2024-06-06T13:21:39Z Undo revision, misread. Apologies. wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = pkgtool, slackpkg | usagetype = Desktop, server | website = [https://slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent Linux distribution and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. [[Category:Linux Distributions]] bf16c931d67a54beba7e2d9cbcbaf22ae7db2bc9 641 640 2024-06-06T13:24:46Z Andre 27 Fixed release model and website wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Release cycle | packagemanager = pkgtool, slackpkg | usagetype = Desktop, server | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent Linux distribution and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. [[Category:Linux Distributions]] ace7a7240c698aa9b11fc512919ec81b839d2ea8 643 641 2024-06-06T13:46:08Z Andre 27 Added History section :3 wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Release cycle | packagemanager = pkgtool, slackpkg | usagetype = Desktop, server | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent Linux distribution and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. [[Category:Linux Distributions]] 6bedf5639d936f3927c7a54a404e67797920954c 644 643 2024-06-06T13:47:53Z Small changes to the distro info box wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[pkgtool]], slackpkg | usagetype = Desktop, Server | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent Linux distribution and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. [[Category:Linux Distributions]] 523d1db6908f795dfb02f8dff0e476e52f77bb6a 670 644 2024-06-06T15:11:33Z Atmois 13 Update infoboxes wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = Blackbox, Fluxbox, FVWM, [[KDE Plamsa]], WMaker, Xfce | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent Linux distribution and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. [[Category:Linux Distributions]] 47fc0aea908bc26006066d31262435a9c7e77dab 0 218 642 604 2024-06-06T13:33:00Z Ari43 20 Removed general distribution advice, some other minor edits wikitext text/x-wiki == Introduction == Linux is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the desktop environment (or window manager) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like KDE or Gnome may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |XFCE | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |Debian<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |Arch Linux<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * Arch Linux will not be covered in this article |- |Fedora<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> 4af688126657f4644e0e684577d97a4d025c28d6 691 642 2024-06-06T19:02:07Z Andre 27 Added gentoo to lightweight distros :D wikitext text/x-wiki == Introduction == Linux is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the desktop environment (or window manager) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like KDE or Gnome may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support (see 4th column) * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 10 GB | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> 958c908dab7f85fc1ef2647878a1a107dee32764 0 1 645 625 2024-06-06T13:51:12Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[I3]] * [[KDE Plasma]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] * [[Slackware]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' f59b215f918f15e9d97970049d6eb3a5a0512220 0 198 647 629 2024-06-06T14:25:25Z Atmois 13 Add link to slackware page wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== [[Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== [[RHEL|Red Hat Enterprise Linux (RHEL)]] is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== [[Slackware]] is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== Ubuntu is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] d5796f168a02b9cc78d3af78709a79f9694f798d 0 203 648 593 2024-06-06T14:29:41Z Andre 27 Added info about emerge command wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | usagetype = Desktop, Server | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]][https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around user customization. This distribution, in addition to having the systemd init system, also provides its own init system known as OpenRC. Unlike other Linux distributions, everything you install is compiled on the local system. As such, users can use compile flags, known as 'Use Flags,' to help them fit their system to their use case. .<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. '''Emerge''' is a front-end for Portage and is used to manage the entire system. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 1acca589be8d6778f922a6279093fcc52f49e47e 666 648 2024-06-06T15:08:03Z Atmois 13 Update infoboxes wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = Budgie, Cinnamon, Deepin, Enlightenment, FVWM, GNOME, [[KDE Plasma]], LXDE, LXQt, Lumina, MATE, Pantheon, Xfce | usagetype = Desktop, Server | architectures = x86, alpha, amd64, arm, hppa, ia64, mips, ppc, ppc64, sparc | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]][https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around user customization. This distribution, in addition to having the systemd init system, also provides its own init system known as OpenRC. Unlike other Linux distributions, everything you install is compiled on the local system. As such, users can use compile flags, known as 'Use Flags,' to help them fit their system to their use case. .<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. '''Emerge''' is a front-end for Portage and is used to manage the entire system. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] c7153658007f0dcd7245b73facedf58a409afdfd 674 666 2024-06-06T16:44:59Z Andre 27 Gentoo only comes with kde live cd. Id put down tty too but that isnt a desktop :rolling_eyes: wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = x86, alpha, amd64, arm, hppa, ia64, mips, ppc, ppc64, sparc | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]][https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around user customization. This distribution, in addition to having the systemd init system, also provides its own init system known as OpenRC. Unlike other Linux distributions, everything you install is compiled on the local system. As such, users can use compile flags, known as 'Use Flags,' to help them fit their system to their use case. .<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. '''Emerge''' is a front-end for Portage and is used to manage the entire system. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 17e4f1405024459c50516e4527f75fefd79e33de 828 163 649 571 2024-06-06T14:37:23Z Removed protection from "[[Module:DistributionInfobox]]": temp Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Website', args.website ) return retval end return p 436de9cdd260be60c0fa213ed7d4086e92007d66 651 649 2024-06-06T14:42:30Z Atmois 13 Add desktops and architectures to infobox Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) ;addRow( 'Desktops', args.desktops ) :addRow( 'Usage Type', args.usagetype ) ;addRow( 'Architectures', args.architectures ) :addRow( 'Website', args.website ) return retval end return p 22d75acd7c751648edb0d537bc17ecd607dcdb85 654 651 2024-06-06T14:45:53Z Atmois 13 Rename desktops to defaultdesktops Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) ;addRow( 'Default Desktops', args.defaultdesktops ) :addRow( 'Usage Type', args.usagetype ) ;addRow( 'Architectures', args.architectures ) :addRow( 'Website', args.website ) return retval end return p fa7a3c2a7b36ff957aa66af15aa52264a602eb9f 655 654 2024-06-06T14:46:52Z Protected "[[Module:DistributionInfobox]]" ([Edit=Allow only administrators] (indefinite)) Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) ;addRow( 'Default Desktops', args.defaultdesktops ) :addRow( 'Usage Type', args.usagetype ) ;addRow( 'Architectures', args.architectures ) :addRow( 'Website', args.website ) return retval end return p fa7a3c2a7b36ff957aa66af15aa52264a602eb9f 656 655 2024-06-06T14:47:18Z Changed protection settings for "[[Module:DistributionInfobox]]" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) ;addRow( 'Default Desktops', args.defaultdesktops ) :addRow( 'Usage Type', args.usagetype ) ;addRow( 'Architectures', args.architectures ) :addRow( 'Website', args.website ) return retval end return p fa7a3c2a7b36ff957aa66af15aa52264a602eb9f 657 656 2024-06-06T14:49:25Z Removed protection from "[[Module:DistributionInfobox]]" Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) ;addRow( 'Default Desktops', args.defaultdesktops ) :addRow( 'Usage Type', args.usagetype ) ;addRow( 'Architectures', args.architectures ) :addRow( 'Website', args.website ) return retval end return p fa7a3c2a7b36ff957aa66af15aa52264a602eb9f 658 657 2024-06-06T14:49:47Z Atmois 13 Replace semicolon with colon Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Default Desktops', args.defaultdesktops ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Architectures', args.architectures ) :addRow( 'Website', args.website ) return retval end return p b660d45c0da77b4a0dd8716d3dabe7d016998a92 671 658 2024-06-06T15:14:50Z Protected "[[Module:DistributionInfobox]]" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Default Desktops', args.defaultdesktops ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Architectures', args.architectures ) :addRow( 'Website', args.website ) return retval end return p b660d45c0da77b4a0dd8716d3dabe7d016998a92 6 234 652 2024-06-06T14:42:50Z Andre 27 wikitext text/x-wiki A screenshot of the package 'git' being installed using portage 2e3952ce3614da4736100f84de47366bc5f8bd6f 0 2 659 628 2024-06-06T14:50:25Z Atmois 13 Update infoboxes wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, KDE, LXDE, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the AUR, Arch's well known user repository, possible. === Philosophy === ... === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 2759cd8aab1f67ace126a8ce79a16a18bc4de274 662 659 2024-06-06T15:02:00Z Link to KDE page wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the AUR, Arch's well known user repository, possible. === Philosophy === ... === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] d662ad668d76b5c57bc2629c77ec7f7c99d8a529 0 182 660 569 2024-06-06T14:55:21Z Atmois 13 Update infoboxes wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, Xfce, KDE Plasma, Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] f90784514df5c85874828185bba896783deb223f 664 660 2024-06-06T15:03:02Z Link to existing DE pages wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, Xfce, [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only Slackware. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] 9507a39ce709b899ae7bcaed3d262e6d42b32bec 690 664 2024-06-06T18:45:11Z Andre 27 added link wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, Xfce, [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a Linux distribution developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only [[Slackware]]. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] eb6d9cb7f986bb2dd86d45d7943353cbd1c6b285 0 217 661 595 2024-06-06T15:01:58Z Atmois 13 Update infoboxes wikitext text/x-wiki {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, i3, Sway, GNOME, KDE Plasma, LXDE, LXQt, MATE, Xfce |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}} '''Fedora Linux''' is an independent [[Linux]] distribution<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being [[RHEL|Red Hat Enterprise Linux]] (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] 68ca0463b417230c587edcaca1f6dcad2e0c1683 663 661 2024-06-06T15:02:36Z Link to existing DE pages wikitext text/x-wiki {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, Xfce |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}} '''Fedora Linux''' is an independent [[Linux]] distribution<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being [[RHEL|Red Hat Enterprise Linux]] (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] e2868b79056965066d8e7fdc524057f0e0f158d8 0 235 665 2024-06-06T15:03:48Z Andre 27 Wrote the first lines and added some info and a screenshot. I will continue later :3 wikitext text/x-wiki {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Portage.png|thumb|The package 'git' being installed via portage]] Portage is considered the heart of every Gentoo and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the package manager, although every package is managed by '''emerge'''. 3fe2d4f9931aaf0f7211cb7c8176f2a9a8de2161 672 665 2024-06-06T16:24:57Z Andre 27 fixed link wikitext text/x-wiki {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|The package 'git' being installed via portage]] Portage is considered the heart of every Gentoo and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the package manager, although every package is managed by '''emerge'''. fba4c4fccca17354795987b51da4fe9600290ecf 673 672 2024-06-06T16:32:07Z Andre 27 Added paragraph idk wikitext text/x-wiki {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|The package 'git' being installed via portage]] Portage is considered the heart of every Gentoo and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the package manager, although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. 32027d4f452b2ad0b834dd34a43bc8916faea09a 675 673 2024-06-06T16:47:46Z Andre 27 Pointed out that the package in the image is a binary wikitext text/x-wiki {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every Gentoo and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the package manager, although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. 302ea4ce8607911bd5433c5b5fe65bb9e2070f8a 0 171 667 578 2024-06-06T15:09:25Z Atmois 13 Update infoboxes wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], IceWM, [[KDE Plasma]], LXQt, Ratpoison, Xfce | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language<ref name=":0" />. === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra<ref>https://save-nix-together.org</ref>, he eventually resigned<ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref>. After the resignation, the new board in charge decided to unban a fascist<ref name=":1" />. === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] b195756e2e07c58ab4ed8a0f713071986bcb1f81 676 667 2024-06-06T17:26:30Z Atmois 13 Make statement less opinionated wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], IceWM, [[KDE Plasma]], LXQt, Ratpoison, Xfce | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language<ref name=":0" />. === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra<ref>https://save-nix-together.org</ref>, he eventually resigned<ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref>. After the resignation, the new board in charge decided to unban a user in support of extreme views.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] e7e5cfdcde8dbb718a79ab06b317e3202122a8e9 680 676 2024-06-06T17:43:45Z Amadaluzia 52 make it even less opinionated (and add more context) wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], IceWM, [[KDE Plasma]], LXQt, Ratpoison, Xfce | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref>. It was originally founded by Eelco Dolstra<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref>. === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language<ref name=":0" />. === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra<ref>https://save-nix-together.org</ref>, he eventually resigned<ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref>. After the resignation, the new board in charge decided to unban a controversial user from the Nixpkgs contributor Zulip chat.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] cb2ea6f0cccdea9b865f8c13bd0c36ea0bcd9e34 0 225 668 600 2024-06-06T15:10:28Z Atmois 13 Update infoboxes wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64, x86-64-v2 | website = [https://redhat.com/rhel/ redhat.com] }} Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial distribution developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] f4aa52f39db2104f0c932473658ede4608bf9a4f 0 8 669 556 2024-06-06T15:10:37Z Atmois 13 Add i3 wikitext text/x-wiki == Introduction == New users engaging with the Linux and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] ** [[i3]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 55ad04ce10e80c86b8175129bbfc9caa689be756 684 669 2024-06-06T18:17:03Z Andre 27 Added portage to package manager list wikitext text/x-wiki == Introduction == New users engaging with the Linux and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] ** [[i3]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[portage]] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] d123ad747ea8d3369ef65678b6175db29afe5881 685 684 2024-06-06T18:18:20Z Andre 27 Added another missing de lol wikitext text/x-wiki == Introduction == New users engaging with the Linux and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] ** [[i3]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[portage]] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] f7a1db5be21fb3a3ca78fe2368825f83ec3812b8 0 236 677 2024-06-06T17:26:55Z Andre 27 Added some things. Ill start writing paragraphs now lol :3 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.18, 2022-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:XFCE-4.10-Desktop.png|thumb|Screenshot of an older version of the XFCE desktop (4.10)]] a4c170bca439467c66aaea10b96c81a62d32eaa7 678 677 2024-06-06T17:36:18Z Andre 27 First paragraph, yay :3 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.18, 2022-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:XFCE-4.10-Desktop.png|thumb|Screenshot of an older version of the XFCE desktop (4.10)]]Xfce is a lightweight desktop environment. It aims to be fast and light for lower hardware, while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. 9a597bc3b9eb46fadfe0f6e094c5f8dfa0dfeedc 679 678 2024-06-06T17:42:54Z Andre 27 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.18, 2022-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:XFCE-4.10-Desktop.png|thumb|Screenshot of an older version of the XFCE desktop (4.10)]]Xfce is a lightweight desktop environment. It aims to be fast and light for lower hardware, while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [[Category:Desktop Environments]] 2b5411fd325a18719d5dc37fa291f0e046dc1a04 0 174 681 447 2024-06-06T18:03:01Z Andre 27 Added a picture of a TUI interface and fixed the abbreviation wikitext text/x-wiki [[File:MS-DOS install - keyboard.gif|alt=MS-DOS TUI installer|thumb|MS-DOS installation, which uses a TUI installer]] A '''TUI''' (Terminal User Interface) generally refers to an application that solely exists within the terminal as a text-based application - this means that all of its content is rendered using letters and other unique characters to create a graphical interface. [REFERENCE POSSIBLE] Because of its independence from a ... , [[Category:Terminology]] ffb354bc90862c3d45b1ad39374e9e3a63757399 0 178 682 525 2024-06-06T18:08:02Z Andre 27 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux Kernel | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], Assembly, [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] Linux in itself refers to two entities, the former being the kernel itself developed by Linus Torvalds and the latter being the families of Operating Systems that derive from it therein. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> <references /> [[Category:Terminology]] 8f2ac1117026c01087dae1783f62a9733da2ff1e 683 682 2024-06-06T18:11:05Z Andre 27 Ah yes, Arch linux is in charge of developing the kernel. And the official website is pacman.archlinux.org wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux Kernel | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], Assembly, [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] Linux in itself refers to two entities, the former being the kernel itself developed by Linus Torvalds and the latter being the families of Operating Systems that derive from it therein. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> <references /> [[Category:Terminology]] b0e84ca7fa4fb7cd52ddf35ad349c5abf22e0804 0 177 686 468 2024-06-06T18:23:11Z Andre 27 Added a translation to libre wikitext text/x-wiki '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the french word, libre)<ref>https://en.wiktionary.org/wiki/libre</ref> and Open Source Software (FLOSS), is software that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111.</ref> FOSS is a neutral term that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> [[Category:Terminology]] cec6fb4eceba0f513853e2b55eb203097c468d45 0 223 687 602 2024-06-06T18:25:31Z Andre 27 very very very very minor change, literally 2 clicks wikitext text/x-wiki == Distrohopping == Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (eg. FSF approved distribution) * Ecosystem or Tooling (eg. libc, [[package manager]], coreutils, init system) * Experimentation * Customization ... and many more. This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (eg. Debianisms, [[Package manager|package managers]], init systems) * Opinionated design philosophies (eg. Nix, Guix, Fedora Atomic) * Additional configuration needs (eg. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (eg. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (eg. Liberapay, Github sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] 0742875a5b3540bab2fadb5af5e052b42619166e 0 173 688 420 2024-06-06T18:31:19Z Andre 27 Wrote a basic definition and added 2 examples :D wikitext text/x-wiki [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager (GDM) being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|An screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a graphical user interface that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[desktop environment]] to use. [[Category:Terminology]] aae503ebbdda315c3e7124ce9ca1f3fea3e28e7c 0 158 689 417 2024-06-06T18:36:27Z Andre 27 Sudo is a seperate package btw, just pointing it out wikitext text/x-wiki When using [[Linux]], sooner or later, there's a good chance you'll end finding yourself in front of a [[Terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a 'Command'. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include "echo", "mv", "[[cat]]", etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with "sudo" followed with your original command. [[sudo]] Tells your computer to 'do' something as a 'super user' which will allow you to bypass restrictions. It should be important to note that '''sudo is a seperate package''' and won't come pre-installed with certain [[distributions]]. If this is the case, you need to use something like "su" to log in as root and then run your command as root or install sudo as root. Furthermore, with commands you will likely need to include "options" that specify to the program how you want it to behave. One of the most common options is "--help", which will usually tell program to list all of its options. An example would be as follows cat --help In this case, the 'cat' utility would respond to this command with the following:<blockquote>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines............</blockquote>(Shortened to maintain focus on topic) These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, "--help" is always there and ready. If --help isnt enough, you can always run "[[man]]" before a program similarly to how you would run "[[sudo]]", and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a File to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory]] (Like shown) or you can provide a file from anywhere in the [[Filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt You will notice that I started describing the file location, I used the tilda sign "~". In linux and some other OS, The Tilda is a faster way to describe the users home folder. It is effectively the same thing as typing the full [[directory path]] except that it is much faster. Here is what it would look like to type the whole directory path nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] e823e9add430f2a77bd492f2dbed8b4cd5451b96 0 227 692 623 2024-06-06T19:32:44Z Andre 27 Less scary picture lol. wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref>Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> [[Category:Desktop Environments]] a5e5710bb10ffb962b8ef064f56ffc0ff768ba43 0 233 693 670 2024-06-06T19:37:23Z Andre 27 Slackware only ships with KDE by default wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent Linux distribution and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. [[Category:Linux Distributions]] ddbd299c9a541aa8f175bf863e1006b656c806df 0 171 694 680 2024-06-06T19:43:11Z Re-order citations and slightly edit phrasing in the controversy section. wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], IceWM, [[KDE Plasma]], LXQt, Ratpoison, Xfce | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] e047b2d55fd672065c87718a2d135050cf7d3e22 703 694 2024-06-06T20:21:18Z Andre 27 Redirect to IceWM wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, Xfce | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux]] distribution built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 00883cae60dfeff4b534719dd0af05f74ad00755 0 236 695 679 2024-06-06T19:52:54Z Andre 27 Added features and stuff wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.18, 2022-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:XFCE-4.10-Desktop.png|thumb|Screenshot of an older version of the XFCE desktop (4.10)]]Xfce is a lightweight desktop environment. It aims to be fast and light for lower hardware, while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. === Features === Xfce has all the basic features of a desktop environment, while still remaining very light. The most basic components of Xfce are: * Window manager (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * Desktop Manager - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * File Manager (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a terminal emulator, text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> [[Category:Desktop Environments]] 40221a6e86d3987bc0a7e706d0f46411a25813db 697 695 2024-06-06T19:55:59Z Andre 27 Better screenshot wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.18, 2022-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight desktop environment. It aims to be fast and light for lower hardware, while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. === Features === Xfce has all the basic features of a desktop environment, while still remaining very light. The most basic components of Xfce are: * Window manager (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * Desktop Manager - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * File Manager (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a terminal emulator, text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> [[Category:Desktop Environments]] 2ef60570d840c868d443d69f96ef14f30d189edc 709 697 2024-06-07T02:48:24Z Asiliria 7 some grammatical tweaks that made me eeby jeeby wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.18, 2022-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * Window manager (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * Desktop Manager - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * File Manager (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a terminal emulator, text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> [[Category:Desktop Environments]] 652d657be3d22529915aa1ee6752bb756d80cc43 6 237 696 2024-06-06T19:54:53Z Andre 27 wikitext text/x-wiki Xfce 4.18 screenshot 371e53ace993367e3c3a9e3f0294764157fbdf31 0 235 698 675 2024-06-06T20:00:20Z Andre 27 Added category wikitext text/x-wiki {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every Gentoo and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the package manager, although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. [[Category:Package Managers]] cf9e59f36546836328c712bb2d812b707435885a 6 238 699 2024-06-06T20:10:06Z Andre 27 wikitext text/x-wiki Screenshot of icewm desktop a8270d1b4662de8990c3162122a8b3a4173e80ce 0 239 700 2024-06-06T20:11:31Z Andre 27 Idk what they are called. I added a thing on the side and a screenshot wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]] [[Category:Desktop Environments]] 78fc61ce4afcb5c99c3f33c068054b92652524de 702 700 2024-06-06T20:16:51Z Andre 27 Added a small description cus bored idk wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. [[Category:Desktop Environments]] da371fa23af9e8310783a4be5bcee27aea44a4a7 728 702 2024-06-07T09:03:28Z Andre 27 Install guide for IceWM cus yeah wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most package managers. On Debian and Debian-based distributions:<syntaxhighlight lang="bash"> $ apt install icewm </syntaxhighlight>On Arch and Arch-based distributions:<syntaxhighlight lang="bash"> $ pacman -S icewm </syntaxhighlight>On Gentoo and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ emerge -av x11-wm/icewm </syntaxhighlight>On RHEL, Fedora and Fedora-based distributions:<syntaxhighlight lang="bash"> dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Desktop Environments]] d81d673c1aa13ccb30096d34e10acd1b6a6def2f 729 728 2024-06-07T09:04:30Z Change installation commands to privileged user wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most package managers. On Debian and Debian-based distributions:<syntaxhighlight lang="bash"> # apt install icewm </syntaxhighlight>On Arch and Arch-based distributions:<syntaxhighlight lang="bash"> # pacman -S icewm </syntaxhighlight>On Gentoo and Gentoo-based distributions:<syntaxhighlight lang="bash"> # emerge -av x11-wm/icewm </syntaxhighlight>On RHEL, Fedora and Fedora-based distributions:<syntaxhighlight lang="bash"> # dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Desktop Environments]] f11d97984c2c05a73ba6bff96a2314f6bf013cb6 730 729 2024-06-07T09:05:44Z Change installation commands to sudo wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most package managers. On Debian and Debian-based distributions: # apt install icewm </syntaxhighlight>On Arch and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On Gentoo and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On RHEL, Fedora and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Desktop Environments]] bcb76043cbbd273a36809e3267c55b521a7281ea 731 730 2024-06-07T09:06:51Z Andre 27 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most package managers. On Debian and Debian-based distributions: <syntaxhighlight lang="bash">$ apt install icewm </syntaxhighlight>On Arch and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On Gentoo and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On RHEL, Fedora and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Desktop Environments]] f40e26ba156619d1a9149708dbcd18965f13d5fd 732 731 2024-06-07T09:07:28Z Andre 27 sudo deez nuts wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most package managers. On Debian and Debian-based distributions: <syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On Arch and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On Gentoo and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On RHEL, Fedora and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Desktop Environments]] 4d5fdd33b7e8fdad8e2bf38141f05de612dff297 0 228 701 634 2024-06-06T20:15:25Z PratyushKing 26 will add rest after thorough checks wikitext text/x-wiki The '''Arch''' '''User''' '''Repository''' (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref>[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The Arch User Repository also has it's own voting system where users can vote for packages and after reaching certain amount of popularity can enter the <code>extra</code> repository. However, the package must have a compatible license and good packaging technique, it should also be maintained actively. The packages that enter the <code>extra</code> repository can be directly installed by pacman.<references /> [[Category:Terminology]] f46d799bf04941df08259141cfba8aaf9d7308b0 725 701 2024-06-07T08:57:16Z Correct slightly wrong information and add source wikitext text/x-wiki The '''Arch''' '''User''' '''Repository''' (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /><references /> [[Category:Terminology]] 3c0c4dda55c75258e8dcaa1c9735b21de61b4641 726 725 2024-06-07T08:58:17Z Link to AUR wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /><references /> [[Category:Terminology]] 2a21345d3c0f8234f7ec5e0b5550497e4600912d 0 173 704 688 2024-06-06T20:50:15Z Asiliria 7 extra details wikitext text/x-wiki [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager (GDM) being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|An screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a graphical user interface that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[desktop environment]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself [referencing ly and cdm here, links needed]. [[Category:Terminology]] 56aab0bb56b8326b459f77a354065eb9c1a9b9e9 739 704 2024-06-07T09:31:18Z wikitext text/x-wiki [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager (GDM) being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|An screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a graphical user interface that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[desktop environment]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.{{Citation needed}} [[Category:Terminology]] 712802e6cc6467d4ab56ba5a43eed4c2f1e433a7 0 240 705 2024-06-06T20:59:45Z Atmois 13 Publish the base of the migrating between OS's page, will be updated with information for each section soon wikitext text/x-wiki == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your disribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most deriative distrobutions. ===== Moving to Arch ===== ===== Moving to Debian ===== ===== Moving to Fedora ===== ===== Moving from Arch ===== ===== Moving from Debian ===== ===== Moving from Fedora ===== ===== Moving from MacOS ===== ===== Moving from Windows ===== === General <bdi>Information</bdi> === fd9b76848b31cecb576b99bf4814327e53f47bb5 706 705 2024-06-06T21:04:03Z Atmois 13 Add category tag wikitext text/x-wiki == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your disribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most deriative distrobutions. ===== Moving to Arch ===== ===== Moving to Debian ===== ===== Moving to Fedora ===== ===== Moving from Arch ===== ===== Moving from Debian ===== ===== Moving from Fedora ===== ===== Moving from MacOS ===== ===== Moving from Windows ===== === General Information === [[Category:Guides]] bb6ccfd4e9dbf2aa2221c0169ac3f0785abb4376 0 1 707 645 2024-06-06T21:32:32Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[I3]] * [[IceWM]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] * [[Slackware]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[Pacman]] * [[Portage]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' fbd04e8445020828b2a20bb8f79adec9ff52227f 0 176 708 613 2024-06-07T02:43:51Z Asiliria 7 Adding extra applications wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak (is this true? - verify), and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. <references /> [[Category:Desktop Environments]] dc677ce71bc159aeb7cd4020c428b8307c80daf0 710 708 2024-06-07T02:51:02Z Asiliria 7 looking for heading field... (removed Flatpak doubts for Discover) wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. <references /> [[Category:Desktop Environments]] 9d50ed764e9aeea985cefb0540f0f311397060ad 713 710 2024-06-07T03:33:18Z Asiliria 7 Saving major changes - Edit Mode section moving on to Desktop Effects wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. === Desktop Effects === <references /> [[Category:Desktop Environments]] aa75f06ac4257f5ec57fbe5d2cd178ae7b8bab29 6 241 711 2024-06-07T02:53:32Z Asiliria 7 wikitext text/x-wiki The Widgets in the "Add Widgets..." field e9d052798f8c4d473571202776261829e95b01da 6 242 712 2024-06-07T03:30:28Z Asiliria 7 wikitext text/x-wiki A customized panel for KDE 1f8968ef5fe3e3bc29d9272244304a8f280220b4 6 243 714 2024-06-07T03:49:27Z Asiliria 7 wikitext text/x-wiki From the Libreboot site itself, an image of a Librebooted HP Desktop 72a89a7b202bf2b89c2820d9e7784109a655a191 0 244 715 2024-06-07T03:50:19Z Asiliria 7 Initial revisions, and starting some work wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most Linux beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. [CITATION NEEDED - for school, I have written an article on Libreboot, if it is helpful. It is honestly terrible from my own standpoint but may be helpful.] === Specific Device Tips === ==== Dell OptiPlex 9020 SFF - Easier Method ==== In a talk with Leah Rowe herself, there is little to no need for the popular Pomona Flash Clip [NOTE TO SELF f0ac9b989b8e8df3ef31047f4969d8c92b0fab4c 717 715 2024-06-07T04:09:33Z Asiliria 7 Adding images and refinements, a guide for the 9020 (my personal server!) wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most Linux beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. [CITATION NEEDED - for school, I have written an article on Libreboot, if it is helpful. It is honestly terrible from my own standpoint.] === Specific Device Tips === ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) aae0f9fae404d26195c7c1ef4c125a6bde1e3938 718 717 2024-06-07T04:11:07Z Asiliria 7 Changed to a heading wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most Linux beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. [CITATION NEEDED - for school, I have written an article on Libreboot, if it is helpful. It is honestly terrible from my own standpoint.] == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) 74339af59e4e6c7fcbd2362de1ab85b15ffdb030 719 718 2024-06-07T04:14:49Z Asiliria 7 small extra details wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most Linux beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. [CITATION NEEDED - for school, I have written an article on Libreboot, if it is helpful. It is honestly terrible from my own standpoint.] == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. ===== Steps ===== * '''Install flashprog and the lbmk repository -''' ... * ... (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) 6e3dc9b36edf4f5bde612b755f4ba530f7e8e09c 720 719 2024-06-07T05:15:56Z Ryna 21 Move to Guides category wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most Linux beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. [CITATION NEEDED - for school, I have written an article on Libreboot, if it is helpful. It is honestly terrible from my own standpoint.] == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. ===== Steps ===== * '''Install flashprog and the lbmk repository -''' ... * ... (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] 29f5476bf48238c3f7ecc0b878f8c33f101e2490 6 245 716 2024-06-07T03:59:18Z Asiliria 7 wikitext text/x-wiki Image of my (Asiliria) Pomona Flash Clip I got in March! cc70a34d4e1c4474c1ecd4a60a79f0ce5bcccebf 0 227 721 692 2024-06-07T08:31:06Z Add configuration section wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[awesome]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Desktop Environments]] 78ae54491ad48dc7cb4832578ee85da19f6ead5d 740 721 2024-06-07T09:31:22Z Andre 27 Added install guides for i3 wikitext text/x-wiki {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On Debian and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On Arch and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On Gentoo and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On Fedora and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it --> ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[awesome]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Desktop Environments]] 86d067bed99330d98a3387c0789cd7c45dfe9329 0 246 722 2024-06-07T08:43:54Z Start of dpkg page - software box + short description wikitext text/x-wiki {{SoftwareInfobox|image=|caption=|title=dpkg|releasestatus=Maintained|lastrelease=1.21.22 / 24 May 2023|languages=C, C++, Perl|developers=The Debian Project|website=[https://www.dpkg.org/ dpkg.org]}} '''dpkg''' (Debian Package) is the core software of the package management system in the Debian operating system and its derivatives. It is used to install, remove, and provide information about <code>.deb</code> packages. dpkg is a low-level tool. APT (Advanced Package Tool) is more commonly used in practice as it is a high-level tool.<ref>Afia Zahin Oishi (December 6, 2023). [https://linuxsimply.com/linux-basics/package-management/package-manager-comparison/dpkg-vs-apt/ <nowiki>"Dpkg Vs Apt [What's the Difference Between Package Managers]"</nowiki>]. linuxsimply.com. LinuxSimply.</ref> f951d743b6343ad4a4f65a9d85b0549ed516f569 724 722 2024-06-07T08:51:17Z Add package managers category wikitext text/x-wiki {{SoftwareInfobox|image=|caption=|title=dpkg|releasestatus=Maintained|lastrelease=1.21.22 / 24 May 2023|languages=C, C++, Perl|developers=The Debian Project|website=[https://www.dpkg.org/ dpkg.org]}} '''dpkg''' (Debian Package) is the core software of the package management system in the Debian operating system and its derivatives. It is used to install, remove, and provide information about <code>.deb</code> packages. dpkg is a low-level tool. APT (Advanced Package Tool) is more commonly used in practice as it is a high-level tool.<ref>Afia Zahin Oishi (December 6, 2023). [https://linuxsimply.com/linux-basics/package-management/package-manager-comparison/dpkg-vs-apt/ <nowiki>"Dpkg Vs Apt [What's the Difference Between Package Managers]"</nowiki>]. linuxsimply.com. LinuxSimply.</ref> [[Category:Package Managers]] 94c8dffc2b367e771c0653821f9c110ac0e9f29f 0 2 727 662 2024-06-07T09:02:00Z /atl.wiki wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux]] distribution focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the AUR, Arch's well known user repository, possible. === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] f1e1cbaef66f4a5a6a84c6abb1e18f96081f794d 0 8 733 685 2024-06-07T09:15:51Z Add dpkg to package manager list wikitext text/x-wiki == Introduction == New users engaging with the Linux and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] ** [[i3]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[apt|''apt'']] ** [[dnf|''dnf'']] ** [[dpkg]] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[portage]] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 632ceadb3f703367af27947154d1d6a28c2b0386 737 733 2024-06-07T09:28:46Z Fix APT link in package manager section wikitext text/x-wiki == Introduction == New users engaging with the Linux and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] ** [[i3]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[APT]] ** [[dnf|''dnf'']] ** [[dpkg]] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[portage]] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 03fcdb007f480576ae3cf1741a66ddd6e80d6053 0 247 734 2024-06-07T09:26:30Z Create APT page wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on Ubuntu.]]|caption=Advanced package tool|title=APT|releasestatus=Maintained|lastrelease=2.9.4 / 25 May 2024 | languages=C++, shell script, EML, CMake, C, Perl | developers=The Debian Project | website=[packages.debian.org packages.debian.org]}} APT (Advanced Package Tool), is a free-software user interface that works with core libraries to handle the installation and removal of software on Debian and Debian-based distribution.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html "apt-get(8)"]. Debian Manpages.</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. 7ba083883c09bdf06588627b6e2b0684598fadb1 735 734 2024-06-07T09:26:59Z Fix typo wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on Ubuntu.]]|caption=Advanced package tool|title=APT|releasestatus=Maintained|lastrelease=2.9.4 / 25 May 2024 | languages=C++, shell script, EML, CMake, C, Perl | developers=The Debian Project | website=[packages.debian.org packages.debian.org]}} APT (Advanced Package Tool), is a free-software user interface that works with core libraries to handle the installation and removal of software on Debian and Debian-based distributions.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html "apt-get(8)"]. Debian Manpages.</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. 6b8912cd3a23027dd24c5d717d537051a966fc55 736 735 2024-06-07T09:28:04Z wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on Ubuntu.]]|caption=|title=APT|releasestatus=Maintained|lastrelease=2.9.4 / 25 May 2024 | languages=C++, shell script, EML, CMake, C, Perl | developers=The Debian Project | website=[packages.debian.org packages.debian.org]}} APT (Advanced Package Tool), is a free-software user interface that works with core libraries to handle the installation and removal of software on Debian and Debian-based distributions.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html "apt-get(8)"]. Debian Manpages.</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. bc10a89aed25f8e034a3714b582b661d467e6812 738 736 2024-06-07T09:29:04Z Add package managers category wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on Ubuntu.]]|caption=|title=APT|releasestatus=Maintained|lastrelease=2.9.4 / 25 May 2024 | languages=C++, shell script, EML, CMake, C, Perl | developers=The Debian Project | website=[packages.debian.org packages.debian.org]}} APT (Advanced Package Tool), is a free-software user interface that works with core libraries to handle the installation and removal of software on Debian and Debian-based distributions.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html "apt-get(8)"]. Debian Manpages.</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. [[Category:Package Managers]] d5cc7425de805a3fdcfcd39a9187ac1d5b65b3c6 0 203 742 674 2024-06-07T09:49:23Z Andre 27 Added a sentance and rewrote available architectures cus i felt like i couldnt trust the current ones lol wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]][https://www.gentoo.org/ Gentoo Linux] is a source-based Linux distribution, aimed around user customization. This distribution, in addition to having the systemd init system, also provides its own init system known as OpenRC. Unlike other Linux distributions, everything you install is compiled on the local system. As such, users can use compile flags, known as 'Use Flags,' to help them fit their system to their use case. .<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Gentoo has support for a large variety of hardware and has extremely minimal requirements, which makes it great for most devices. === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. '''Emerge''' is a front-end for Portage and is used to manage the entire system. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] e74ae30c1cb275c3882e2362e92a660ed6730c45 0 248 743 2024-06-07T10:53:34Z Atmois 13 Create ubuntu page wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Ubtuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|thumb]] | caption = Ubtuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dpkg]], [[snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubtunu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version of RHEL was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions recieve 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu recieve 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] 7a6e488f033f42a639cee5664583e32cbd22922b 744 743 2024-06-07T10:55:19Z Tess moved page [[Ubtuntu]] to [[Ubuntu]] without leaving a redirect: Typo wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Ubtuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|thumb]] | caption = Ubtuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dpkg]], [[snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubtunu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version of RHEL was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions recieve 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu recieve 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] 7a6e488f033f42a639cee5664583e32cbd22922b 0 248 745 744 2024-06-07T10:55:32Z typo wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Ubtuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|thumb]] | caption = Ubtuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dpkg]], [[snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version of RHEL was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions recieve 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu recieve 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] 5464c593929d89c358d8a844e032cee88e95aae2 749 745 2024-06-07T11:01:59Z Atmois 13 Fix spelling wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Ubtuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|thumb]] | caption = Ubtuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dpkg]], [[snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version of RHEL was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu receives 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] 5fc3fdac39399f40837fd54428ac0eaa0fdc7c40 0 198 747 647 2024-06-07T10:56:30Z Atmois 13 Add ubuntu link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') comprises of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abanonded. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== [[Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== [[RHEL|Red Hat Enterprise Linux (RHEL)]] is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== [[Slackware]] is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installs will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== [[Ubuntu]] is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] 8c50bcba27009eddd1d43eb49ddd4a3782072d72 748 747 2024-06-07T11:00:47Z Atmois 13 Fix grammer and spelling wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abandoned. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== [[Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== [[RHEL|Red Hat Enterprise Linux (RHEL)]] is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== [[Slackware]] is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== [[Ubuntu]] is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] ca8620f9c0115ed38370198bed851a32dbf4a40e 796 748 2024-06-07T23:02:14Z Atmois 13 Update links wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the more notable ones, for a more comprehensive list of distributions see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on. Distributions in ''italics'' are abandoned. ==== Arch Based ==== [[Arch Linux]] is an independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Debian Based ==== [[Debian]] is an independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Fedora Based ==== [[Fedora]] is a community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Gentoo Based ==== [[Gentoo]] is a highly flexible source-based distribution designed to have highly optimized and frequently updated software. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Red Hat Enterprise Based ==== [[RHEL|Red Hat Enterprise Linux (RHEL)]] is a commercial distribution developed by Red Hat for the enterprise market. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Slackware Based ==== [[Slackware]] is a highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== openSUSE Based ==== openSUSE is a community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Ubuntu Based ==== [[Ubuntu]] is a distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. {| class="wikitable" |- ! Distribution !! Description |- | | |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] cd95f1b6f85582ea0e32cca89d1054a76cddc58a 0 2 750 727 2024-06-07T11:04:42Z Atmois 13 Add link wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the AUR, Arch's well known user repository, possible. === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 8c55124ac14bf0eeb7fec2728a149b2f002a4839 781 750 2024-06-07T22:39:53Z Atmois 13 Add links wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the [[Arch User Repository|AUR]], Arch's well known user repository, possible. === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 7541eb1098555fd4aa7345a7ee3ab9b9c4d4e4e5 782 781 2024-06-07T22:40:43Z Atmois 13 Add XFCE link wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the [[Arch User Repository|AUR]], Arch's well known user repository, possible. === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 0c30c11ccde7b6fae7b0cd6630bde1c3a4128fa0 0 182 751 690 2024-06-07T11:05:08Z Atmois 13 Add link wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, Xfce, [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a [[Linux Distributions|Linux distribution]] developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only [[Slackware]]. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] f9e9d64b309c1a4feca260b83546a91ce82eb361 787 751 2024-06-07T22:49:59Z Atmois 13 Add XFCE link wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, [[Xfce]], [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a [[Linux Distributions|Linux distribution]] developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. === History === Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only [[Slackware]]. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] ee2fb6d3a944e437318733c1026cd037d1dce858 0 217 752 663 2024-06-07T11:05:39Z Atmois 13 Add link wikitext text/x-wiki {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, Xfce |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}} '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being [[RHEL|Red Hat Enterprise Linux]] (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] 71db0feb122fca2aad5e195075fa782f93f753c5 789 752 2024-06-07T22:53:49Z Atmois 13 Add XFCE link wikitext text/x-wiki {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]] |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}} '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being [[RHEL|Red Hat Enterprise Linux]] (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] 244afcb387c5439fad05ec3c1d70c6773c724efc 0 203 753 742 2024-06-07T11:05:59Z Atmois 13 Add link wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]][https://www.gentoo.org/ Gentoo Linux] is a source-based [[Linux Distributions|Linux distribution]], aimed around user customization. This distribution, in addition to having the systemd init system, also provides its own init system known as OpenRC. Unlike other Linux distributions, everything you install is compiled on the local system. As such, users can use compile flags, known as 'Use Flags,' to help them fit their system to their use case. .<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Gentoo has support for a large variety of hardware and has extremely minimal requirements, which makes it great for most devices. === Portage === Portage is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. '''Emerge''' is a front-end for Portage and is used to manage the entire system. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 284a723a0d6048005cf3fabbe49651ac5d64fbe9 790 753 2024-06-07T22:54:42Z Atmois 13 Add links wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]][https://www.gentoo.org/ Gentoo Linux] is a source-based [[Linux Distributions|Linux distribution]], aimed around user customization. This distribution, in addition to having the systemd init system, also provides its own init system known as OpenRC. Unlike other Linux distributions, everything you install is compiled on the local system. As such, users can use compile flags, known as 'Use Flags,' to help them fit their system to their use case. .<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Gentoo has support for a large variety of hardware and has extremely minimal requirements, which makes it great for most devices. === Portage === [[Portage]] is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. '''Emerge''' is a front-end for Portage and is used to manage the entire system. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 68350e0bc848fc705b71a797a30f550e45261444 0 171 754 703 2024-06-07T11:06:18Z Atmois 13 Add link wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, Xfce | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] aadecb5bea438d72159a4be19e99bdd407580836 0 225 755 668 2024-06-07T11:06:37Z Atmois 13 Add link wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64, x86-64-v2 | website = [https://redhat.com/rhel/ redhat.com] }} Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] e83c08c4d4e38567cb2fe0780edbe19fc88b2935 0 233 756 693 2024-06-07T11:06:56Z Atmois 13 Add link wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. [[Category:Linux Distributions]] 4091204ef97c41ea33417c76c2d23ddba90c22bb 0 218 757 691 2024-06-07T12:12:08Z Andre 27 fixed link wikitext text/x-wiki == Introduction == Linux is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the desktop environment (or window manager) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like KDE or Gnome may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support (see 4th column) * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> a5c858b77f6ff698e79b48fadf8123d59268627e 760 757 2024-06-07T13:00:45Z Andre 27 Added puppy lunixs wikitext text/x-wiki == Introduction == Linux is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the desktop environment (or window manager) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like KDE or Gnome may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |Puppy Linux | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> fa1259ca4e44cfd01e0e802d6d6ee5c9d48bd077 761 760 2024-06-07T13:02:30Z Andre 27 I forgot system requirements for puppy lol wikitext text/x-wiki == Introduction == Linux is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the desktop environment (or window manager) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like KDE or Gnome may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |Puppy Linux | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref>https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> 2478542a1eba7dc88dd26ee88a15445264bebe3b 762 761 2024-06-07T14:22:35Z Andre 27 fixed debian archs wikitext text/x-wiki == Introduction == Linux is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the desktop environment (or window manager) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like KDE or Gnome may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |Puppy Linux | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref>https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> 088d94b062f8a7191010f7f21a3d6f8f9fe523e9 0 176 758 713 2024-06-07T12:13:50Z Asiliria 7 Reposition, add image wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. === Desktop Effects === <references /> [[Category:Guides]] 5266abb2a0bc5b0981b85eb55abc738898b94ff6 759 758 2024-06-07T12:14:18Z Asiliria 7 oops wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from Linux to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. === Desktop Effects === <references /> [[Category:Desktop Environments]] dd5b7a54d09ee8488a66e174650b51ae0723e38e 792 759 2024-06-07T22:58:06Z Atmois 13 Add links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. === Desktop Effects === <references /> [[Category:Desktop Environments]] bd15e6c26dfdbc5e6617a4d92477b36150e7f488 0 250 763 2024-06-07T14:50:10Z Asiliria 7 Testing links wikitext text/x-wiki (I'm gonna test something out here...) == w-okada == 84c28f1391728eb3ab48b60eba0138591dfca5fd 766 763 2024-06-07T15:11:55Z Asiliria 7 Massive field edits, as well as major additions for w-okada - I have had contact with a developer on how to set this up. wikitext text/x-wiki Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on Linux for not only proprietary applications and usage, but also is heavily used for [[Free and Open Source]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. === RECOMMENDED - anaconda and conda for beginners === ... == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, for helping with gender dysphoria, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) === NVIDIA setup === ... === AMDGPU setup === ... b52e7d5a3e78448ebdad8f48898aacca54c057de 768 766 2024-06-07T15:15:16Z Ryna 21 Edited a link to include Foss/Floss instead of 'Free and Open Source' wikitext text/x-wiki Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on Linux for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. === RECOMMENDED - anaconda and conda for beginners === ... == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, for helping with gender dysphoria, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) === NVIDIA setup === ... === AMDGPU setup === ... 66bb747815e0cdeb92d01c2c400f4e66f1e41426 769 768 2024-06-07T15:23:19Z Asiliria 7 Field entries wikitext text/x-wiki Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on Linux for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == RECOMMENDED - anaconda and conda for beginners == ... == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, for helping with gender dysphoria, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) ==== NVIDIA setup ==== ... === AMDGPU setup === ... == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> == Large Language Models - oLLaMa, Mistral, etc. == (Someone more experienced can help) 49369696d0297565314e1d533ca0cf72ac5fda08 771 769 2024-06-07T15:34:28Z Asiliria 7 Adding an image! wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on Linux for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == RECOMMENDED - anaconda and conda for beginners == ... == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, for helping with gender dysphoria, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) ==== NVIDIA setup ==== ... === AMDGPU setup === ... == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> == Large Language Models - oLLaMa, Mistral, etc. == (Someone more experienced can help) 1c1f70d5fbd70f781d53441ef396a53feacee795 772 771 2024-06-07T15:34:56Z Asiliria 7 image addition wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on Linux for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == RECOMMENDED - anaconda and conda for beginners == ... == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, for helping with gender dysphoria, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) ==== NVIDIA setup ==== ... === AMDGPU setup === ... == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> == Large Language Models - oLLaMa, Mistral, etc. == (Someone more experienced can help) 36fd3444ea18e4647907205c01e6aa568b9cd8f1 773 772 2024-06-07T15:55:19Z Asiliria 7 Making a table... wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on Linux for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == RECOMMENDED - anaconda and conda for beginners == ... == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, for helping with gender dysphoria, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output. * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a [[Secondary GPU|Secondary/Dual GPU]] (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- |... |... |- | | |} === AMDGPU setup === ... == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> == Large Language Models - oLLaMa, Mistral, etc. == (Someone more experienced can help) 387a20a3b1b207d801e79900862c99c83a8d8b7a 774 773 2024-06-07T15:55:58Z Asiliria 7 boldened and italicized. wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on Linux for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == RECOMMENDED - anaconda and conda for beginners == ... == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, for helping with gender dysphoria, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a [[Secondary GPU|Secondary/Dual GPU]] (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- |... |... |- | | |} === AMDGPU setup === ... == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> == Large Language Models - oLLaMa, Mistral, etc. == (Someone more experienced can help) 919bfe9bffbb5eaae9cef2d1e68cfba8f3bf9bc3 777 774 2024-06-07T17:17:14Z Asiliria 7 Removal of content - see wiki pub discord wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on Linux for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == RECOMMENDED - anaconda and conda for beginners == ... == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a [[Secondary GPU|Secondary/Dual GPU]] (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- |... |... |- | | |} === AMDGPU setup === ... == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> == Large Language Models - oLLaMa, Mistral, etc. == (Someone more experienced can help) 12193d3b07ff5710dbe3940d6304a54daca5e992 783 777 2024-06-07T22:43:01Z Atmois 13 Add links wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == RECOMMENDED - anaconda and conda for beginners == ... == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a [[Secondary GPU|Secondary/Dual GPU]] (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- |... |... |- | | |} === AMDGPU setup === ... == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> == Large Language Models - oLLaMa, Mistral, etc. == (Someone more experienced can help) 0a62d6cfd57402094455882d0e1d7a9752dc7f8f 0 179 764 427 2024-06-07T14:52:59Z Asiliria 7 Instead of links, make an index, remove test wikitext text/x-wiki Not every install will be as flawless as a user will expect it to be, and they may encounter bugs for numerous reasons ranging from simple hardware differences to nuanced kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) * [[Artificial Intelligence on Linux]] ** Covers w-okada, Stable Diffusion, ROCm/CUDA with proper driver setup, anaconda/conda... [[Category:Guides]] 8b269ad7d5ceef21aaaaca01ec0b95848c53f9ae 767 764 2024-06-07T15:13:14Z Asiliria 7 Format change - do people like this? wikitext text/x-wiki Not every install will be as flawless as a user will expect it to be, and they may encounter bugs for numerous reasons ranging from simple hardware differences to nuanced kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) === [[Artificial Intelligence on Linux]] === '''Covers w-okada, Stable Diffusion, Large Language Models, ROCm/CUDA with proper driver setup, anaconda/conda...''' [[Category:Guides]] a7850757ecc92d68dad759486b00f8030d0e87b5 6 251 765 2024-06-07T15:08:25Z Asiliria 7 wikitext text/x-wiki A diagram of how w-okada functions at the high-level. (TRANSLATION NEEDED) 7fefd3498275831665956b6e486e6cb4448f65d9 6 252 770 2024-06-07T15:34:03Z Asiliria 7 wikitext text/x-wiki The internals of an NVIDIA H100 Unit de78b9ea682aa3ad799a115f1d0f3bcaa825ffe7 0 254 776 2024-06-07T16:44:07Z Andre 27 Added that thing on the side + a screenshot. I will now start writing wikitext text/x-wiki {{SoftwareInfobox | image = [[File:DynamicWindowManager.png|DWM logo]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot of somebody's desktop running DWM]] e39695027cd6be817866710c25ffd77e02ac4f81 778 776 2024-06-07T17:19:40Z Andre 27 Saving this rn because hyprland fucking sucks and killed my cursor so i have to reboot wikitext text/x-wiki {{SoftwareInfobox | image = [[File:DynamicWindowManager.png|DWM logo]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot of somebody's desktop running DWM]]dwm (Dynamic Window Manager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. 0e088441c27cf217141b565293916404286d8184 0 247 780 738 2024-06-07T22:38:42Z Atmois 13 Add links wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on Ubuntu.]]|caption=|title=APT|releasestatus=Maintained|lastrelease=2.9.4 / 25 May 2024 | languages=C++, shell script, EML, CMake, C, Perl | developers=The Debian Project | website=[packages.debian.org packages.debian.org]}} APT (Advanced Package Tool), is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html "apt-get(8)"]. Debian Manpages.</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. [[Category:Package Managers]] 7eccdd3f25732796aec0a4d9e38042421273f9e4 0 166 784 415 2024-06-07T22:43:32Z Atmois 13 Add links wikitext text/x-wiki A term commonly used across any Linux community{{Citation needed}}, "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life. <ref>Merriam-Webster Dictionary. [https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of [[Linux]] and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system.{{Citation needed}} <references /> [[Category:Terminology]] f770b1a3f1e20e275c4bf2d5eb058ccfa5c68e29 0 158 785 689 2024-06-07T22:46:10Z Atmois 13 Add links wikitext text/x-wiki When using [[Linux]], sooner or later, there's a good chance you'll end finding yourself in front of a [[Terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a 'Command'. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include "echo", "mv", "[[cat]]", etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with "sudo" followed with your original command. [[sudo]] Tells your computer to 'do' something as a 'super user' which will allow you to bypass restrictions. It should be important to note that '''sudo is a seperate package''' and won't come pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you need to use something like "su" to log in as root and then run your command as root or install sudo as root. Furthermore, with commands you will likely need to include "options" that specify to the program how you want it to behave. One of the most common options is "--help", which will usually tell program to list all of its options. An example would be as follows cat --help In this case, the 'cat' utility would respond to this command with the following:<blockquote>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines............</blockquote>(Shortened to maintain focus on topic) These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, "--help" is always there and ready. If --help isnt enough, you can always run "[[man]]" before a program similarly to how you would run "[[sudo]]", and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a File to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory]] (Like shown) or you can provide a file from anywhere in the [[Filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt You will notice that I started describing the file location, I used the tilda sign "~". In linux and some other OS, The Tilda is a faster way to describe the users home folder. It is effectively the same thing as typing the full [[directory path]] except that it is much faster. Here is what it would look like to type the whole directory path nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 6f80f5c89e4e8cab7a9b9a131f70005258e634ea 0 246 786 724 2024-06-07T22:49:19Z Atmois 13 Add links wikitext text/x-wiki {{SoftwareInfobox|image=|caption=|title=dpkg|releasestatus=Maintained|lastrelease=1.21.22 / 24 May 2023|languages=C, C++, Perl|developers=The Debian Project|website=[https://www.dpkg.org/ dpkg.org]}} '''dpkg''' (Debian Package) is the core software of the package management system in the [[Debian]] operating system and its derivatives. It is used to install, remove, and provide information about <code>.deb</code> packages. dpkg is a low-level tool. [[APT|APT (Advanced Package Tool)]] is more commonly used in practice as it is a high-level tool.<ref>Afia Zahin Oishi (December 6, 2023). [https://linuxsimply.com/linux-basics/package-management/package-manager-comparison/dpkg-vs-apt/ <nowiki>"Dpkg Vs Apt [What's the Difference Between Package Managers]"</nowiki>]. linuxsimply.com. LinuxSimply.</ref> [[Category:Package Managers]] 3a4a714894fe53107701ffea101cca36bf2276c8 0 164 788 605 2024-06-07T22:52:43Z Atmois 13 Add links wikitext text/x-wiki == Introduction == The [[Linux]] community is abundant with awesome projects and various other guides worth checking out, Here's some great ones that we have found - keep in mind that, while these guides are very useful, they are not fully exhaustive. More than likely you discover new software every day! * Privacy is not an end goal, but a consistent journey that needs to be taken very seriously. ''Always'' seek help when in doubt and ensure you take everything with a grain of salt. ''Do not just blindly follow guides but use your own intuition!'' == Guides == * https://www.privacyguides.org/ - An essential guide to learning not just ''how'' to begin your privacy journey online but offers a comprehensive explanation of abstract privacy concepts that is simple to understand and by extension ''is assuredly not easy or quick -'' read with an open mind! ** https://awesome-privacy.xyz - More of a guide to tools you may find yourself wanting to use to enhance privacy, rather than an explanation. The next step from Privacy Guides, essentially. ** https://www.privacytools.io/ - Similar to Awesome Privacy, and offers a wide range of tools. This specific website is recommended very frequently. * https://brainfucksec.github.io/firefox-hardening-guide - A guide to "de-Mozilla" and security-harden Firefox. Assess whether or not this is a good option for you - ''similar to privacy, it is not an easy process.'' * https://rentry.co/fmhy-guides - General, yet extremely useful and even nuanced guides that you may find yourself needing for something very specific and hard to find on the internet. * https://github.com/luong-komorebi/Awesome-Linux-Software - Very extensive guide of not solely Linux software but mostly open-source software that has many use cases in mind. [[Choosing A Linux Distribution|May be helpful in picking a flavor of Linux for your specific use cases.]] == Wikis == * https://wiki.archlinux.org/ for Arch Linux * https://wiki.gentoo.org/ for Gentoo * https://wiki.debian.org/ for Debian * https://fedoraproject.org/wiki/Fedora_Project_Wiki for Fedora * https://wiki.ubuntu.com for Ubuntu == Tools == * https://christitus.com/windows-tool/ - Used for debloating and removing telemetry from Windows. * https://alternativeto.net - A tool to find alternatives to popular software, both open-source and proprietary. [[Category:Guides]] dde32525d4661af9e1e32d5ce1f00b30d2747c30 0 239 791 732 2024-06-07T22:56:27Z Atmois 13 Add links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most [[Package manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Desktop Environments]] 8b968df7ada16db2f1146d434a5e02003ca7ba81 0 8 793 737 2024-06-07T22:59:19Z Atmois 13 Add new entry + links wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[DE / WM|Desktop Environments and Window Managers]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] ** [[i3]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[Apk|''apk'']] ** [[APT]] ** [[dnf|''dnf'']] ** [[dpkg]] ** ''[[Flatpak]]'' ** [[NixOS|Nix]] ** [[pacman|''pacman'']] ** [[portage]] ** [[rpm|''rpm'']] ** [[Snap]] ** [[zypper|''zypper'']] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] ca18c41d5856bb61fa0a7c4f5d4e1f97da2b6a9f 0 244 794 720 2024-06-07T23:00:34Z Atmois 13 Add links wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. [CITATION NEEDED - for school, I have written an article on Libreboot, if it is helpful. It is honestly terrible from my own standpoint.] == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. ===== Steps ===== * '''Install flashprog and the lbmk repository -''' ... * ... (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] 964ecf61e8263a605729add509c675380fb8dbbd 0 178 795 683 2024-06-07T23:01:25Z Atmois 13 Update info to be clear + add links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux Kernel | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], Assembly, [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] Linux in itself refers to two entities, the former being the kernel itself developed by Linus Torvalds and the latter being the families of [[Linux Distributions|Operating Systems based off the Kernel]]. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> <references /> [[Category:Terminology]] a264ae38fe0472c65a7b6e75405bb78c5fdba76f 0 209 797 558 2024-06-07T23:02:39Z Atmois 13 Add links wikitext text/x-wiki == Introduction == [[Linux]] is a good way to make-do with an old Intel Mac you may have. Many issues exist due to hardware support, such as WiFi support, and keyboard + trackpad issues on some devices. This page will list solutions to common issues as well as tips, tricks, and other information. On many Mac devices Linux works flawlessly after initial setup and troubleshooting is complete. If you are attempting to install Linux on a device with an ARM (Apple Silicon) CPU, see the [[#Asahi Linux]] section. == Asahi Linux == Asahi Linux as a work in progress port of many tools and drivers to Apple Silicon on Linux, and is currently under heavy development. More information can be found on the [https://asahilinux.org/ Asahi Linux website]. == Troubleshooting == === MacBookPro11,x to MacBookPro12,1 === ==== WiFi doesn't work ==== This is a side-effect of Broadcom's poor driver support on Linux, read [https://asahilinux.org/ this page] for information on how to install the proprietary '''broadcom-wl driver''' on Arch Linux. Other distributions should follow their respective guides if one exists. == Notes == '''> More issues will be added overtime. This list is far from done.''' <references /> [[Category:Guides]] 14dfcffa29d96bf23b052f574f76f53f38c8b248 0 218 798 762 2024-06-07T23:03:42Z Atmois 13 Update info + links wikitext text/x-wiki == Introduction == [[Linux]] is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[desktop environment]] (or window manager) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or GNOMEmay still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |Puppy Linux | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref>https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> cf72ef4fc771561a3648379a0868b007660565ce 0 171 799 754 2024-06-07T23:04:33Z Atmois 13 Add links wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, Xfce | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] e2ae829b94c90406aefb54b440714f10ce36f867 821 799 2024-06-08T10:17:25Z Andre 27 added screenshot wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, Xfce | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 612aa5fa45b6b5d75634688f65fc3753ed20df5d 822 821 2024-06-08T10:18:56Z Andre 27 added link to xfce wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:NixOS-Logo.png|200px|The_NixOS_Logo]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 48f691ac1f9f307e7be880c02707259dc6684110 0 169 800 606 2024-06-07T23:05:36Z Atmois 13 Update info + links wikitext text/x-wiki == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. [[Category:Terminology]] 16012d694835ebb3d675aff9912a11bdc413b217 0 175 801 583 2024-06-07T23:06:24Z Atmois 13 Update links wikitext text/x-wiki {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Pacman 401.png|thumb|[[Pacman]]]] == Intro == The [[Linux Distributions|Linux distribution]] [[Arch Linux]] and its derivatives usually use a [[package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] [[Category:Package Managers]] 701d740ac85bd9c6f8d870e0f8a8b69472dfa3ee 0 235 802 698 2024-06-07T23:06:50Z Atmois 13 Add links wikitext text/x-wiki {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every [[Gentoo]] and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the [[package manager]], although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. [[Category:Package Managers]] 228af8b3a794652a2c8f67e4d693aaa3cce69804 0 255 803 2024-06-07T23:09:13Z Atmois 13 Add redirect wikitext text/x-wiki #REDIRECT [[Linux Distributions]] f6721c832bacd7daf16c3910dd1b30b95255d241 0 227 804 740 2024-06-07T23:10:33Z Atmois 13 Change display name to i3 wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On Debian and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On Arch and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On Gentoo and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On Fedora and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it --> ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[awesome]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Desktop Environments]] 0a768f9d68b1ebc1f23abfd836cfef5dab7c0b0b 830 804 2024-06-08T13:59:54Z Andre 27 debain wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On Arch and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On Gentoo and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On Fedora and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it --> ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[awesome]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Desktop Environments]] 797f74238a38ba5493c3c835dde2a07e0f88976d 831 830 2024-06-08T14:00:28Z Andre 27 arhc wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On Gentoo and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On Fedora and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it --> ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[awesome]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Desktop Environments]] 98e030695ecba75bd6c101c5811567346d1ae372 832 831 2024-06-08T14:00:52Z Andre 27 gentoo wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On Fedora and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it --> ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[awesome]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Desktop Environments]] e32f2e4b8f4f2b02a9d51ff0655eaf7d8dcda4f3 833 832 2024-06-08T14:01:09Z Andre 27 fedor wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[awesome]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Desktop Environments]] ed9c2250ed733235ee349b323b860f351294c8ec 0 225 805 755 2024-06-07T23:11:09Z Atmois 13 Change display name to Red Hat Enterprise Linux wikitext text/x-wiki {{DISPLAYTITLE:Red Hat Enterprise Linux}} == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64, x86-64-v2 | website = [https://redhat.com/rhel/ redhat.com] }} Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] d529908797d2309b2286e741194a85d50a3549fa 819 805 2024-06-08T10:12:41Z Andre 27 screenshot added wikitext text/x-wiki {{DISPLAYTITLE:Red Hat Enterprise Linux}} == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64, x86-64-v2 | website = [https://redhat.com/rhel/ redhat.com] }} [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] f0853ed799e6be09a0a3adce8be9b0d3c2575239 2 256 806 2024-06-08T00:59:33Z Ryna 21 Updated bio wikitext text/x-wiki Discord: rynathefox 8e21768cd92bb7f4ead73410ed0641c0d341e3ac 0 228 807 726 2024-06-08T06:52:51Z PratyushKing 26 added Creating AUR Package, Installing AUR packages, Safety wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === While there are simpler ways to do this, we will use the officially recommended method, which is manually installing it. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package because it is an AUR exclusive, you can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To make this process simpler and more intuitive, people have made AUR helpers, we are not going to go in depth with those but basically the most basic ones can search and download such packages, the more advanced ones can search and build and then the most commonly used ones are termed as pacman wrappers which means that they can search, build, update and can also deal with system packages so you can update your system entirely with such AUR helpers (you must not remove pacman however, these helpers just act as pacman and run pacman for you). You can take a look at this on the [[AUR helpers]] page. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are what you should install since they are pre-built binary packages and reduce effort in compiling programs by source. * <code>-git</code> : These packages are generally not recommended but they are more commonly found, these are compiled from source and they are downloaded via GitHub or GitLab. * No Suffix or other suffix : These packages are either proprietary or are compiled from other sources. Generally not recommended unless you know about that package. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add [https://wiki.archlinux.org/title/PKGBUILD required metadata] and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained [https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions here]. * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use [https://wiki.archlinux.org/title/Namcap namcap] to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === Like we saw just now, you can easily publish your package to the AUR with no checks other than the general SRCINFO file, while the AUR is actively moderated by volunteers, there are still a few malicious packages that are not caught because of which we suggest everyone to read the PKGBUILDs they use from the AUR ensuring that it is a safe one. We do also encourage people to actively go to the AUR mailing list and report malicious package that are not caught under the radar. The AUR has over 60,000 packages and we hope you actively report packages and do your best to keep the AUR clean. <references /> [[Category:Terminology]] 6ce5997153f241cd8817301711a8ded4ed5ac2fc 808 807 2024-06-08T07:00:43Z PratyushKing 26 most links changed to cite references wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === While there are simpler ways<ref>[[AUR Helpers]]</ref> to do this, we will use the officially recommended method, which is manually installing it. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code><ref>https://aur.archlinux.org/packages/visual-studio-code-bin</ref> package because it is an AUR exclusive, you can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To make this process simpler and more intuitive, people have made AUR helpers, we are not going to go in depth with those but basically the most basic ones can search and download such packages, the more advanced ones can search and build and then the most commonly used ones are termed as pacman wrappers which means that they can search, build, update and can also deal with system packages so you can update your system entirely with such AUR helpers (you must not remove pacman however, these helpers just act as pacman and run pacman for you). You can take a look at this on the [[AUR Helpers|AUR helpers]] page. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are what you should install since they are pre-built binary packages and reduce effort in compiling programs by source. * <code>-git</code> : These packages are generally not recommended but they are more commonly found, these are compiled from source and they are downloaded via GitHub or GitLab. * No Suffix or other suffix : These packages are either proprietary or are compiled from other sources. Generally not recommended unless you know about that package. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === Like we saw just now, you can easily publish your package to the AUR with no checks other than the general SRCINFO file, while the AUR is actively moderated by volunteers, there are still a few malicious packages that are not caught because of which we suggest everyone to read the PKGBUILDs they use from the AUR ensuring that it is a safe one. We do also encourage people to actively go to the AUR mailing list and report malicious package that are not caught under the radar. The AUR has over 60,000 packages and we hope you actively report packages and do your best to keep the AUR clean. <references /> [[Category:Terminology]] 5c7a39ada9e488e2521e83e81a14b7f3f3109660 838 808 2024-06-08T15:53:31Z Small corrections - more to review wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with [[AUR helpers]]. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully.<ref>[[AUR Helpers]]</ref> To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To make this process simpler and more intuitive, people have made AUR helpers, we are not going to go in depth with those but basically the most basic ones can search and download such packages, the more advanced ones can search and build and then the most commonly used ones are termed as pacman wrappers which means that they can search, build, update and can also deal with system packages so you can update your system entirely with such AUR helpers (you must not remove pacman however, these helpers just act as pacman and run pacman for you). You can take a look at this on the [[AUR Helpers|AUR helpers]] page. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are what you should install since they are pre-built binary packages and reduce effort in compiling programs by source. * <code>-git</code> : These packages are generally not recommended but they are more commonly found, these are compiled from source and they are downloaded via GitHub or GitLab. * No Suffix or other suffix : These packages are either proprietary or are compiled from other sources. Generally not recommended unless you know about that package. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === Like we saw just now, you can easily publish your package to the AUR with no checks other than the general SRCINFO file, while the AUR is actively moderated by volunteers, there are still a few malicious packages that are not caught because of which we suggest everyone to read the PKGBUILDs they use from the AUR ensuring that it is a safe one. We do also encourage people to actively go to the AUR mailing list and report malicious package that are not caught under the radar. The AUR has over 60,000 packages and we hope you actively report packages and do your best to keep the AUR clean. <references /> [[Category:Terminology]] 43898e7663b38c6248077a864047abfe21c5e887 840 838 2024-06-08T16:00:46Z wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with [[AUR helpers]]. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, [[AUR helpers]] have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, [[pacman]] is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are what you should install since they are pre-built binary packages and reduce effort in compiling programs by source. * <code>-git</code> : These packages are generally not recommended but they are more commonly found, these are compiled from source and they are downloaded via GitHub or GitLab. * No Suffix or other suffix : These packages are either proprietary or are compiled from other sources. Generally not recommended unless you know about that package. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === Like we saw just now, you can easily publish your package to the AUR with no checks other than the general SRCINFO file, while the AUR is actively moderated by volunteers, there are still a few malicious packages that are not caught because of which we suggest everyone to read the PKGBUILDs they use from the AUR ensuring that it is a safe one. We do also encourage people to actively go to the AUR mailing list and report malicious package that are not caught under the radar. The AUR has over 60,000 packages and we hope you actively report packages and do your best to keep the AUR clean. <references /> [[Category:Terminology]] f23d9bbce9563f08a28750f471f24abc0ac76a72 841 840 2024-06-08T16:08:12Z Rewrite safety section wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with [[AUR helpers]]. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, [[AUR helpers]] have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, [[pacman]] is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are what you should install since they are pre-built binary packages and reduce effort in compiling programs by source. * <code>-git</code> : These packages are generally not recommended but they are more commonly found, these are compiled from source and they are downloaded via GitHub or GitLab. * No Suffix or other suffix : These packages are either proprietary or are compiled from other sources. Generally not recommended unless you know about that package. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability.<references /> [[Category:Terminology]] 3fb730fb1e9d2b11f8e7acd7b6c3981178466e40 843 841 2024-06-08T16:14:30Z PratyushKing 26 minor edits to Package Naming wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILDs]]) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with [[AUR helpers]]. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, [[AUR helpers]] have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, [[pacman]] is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability.<references /> [[Category:Terminology]] 2380feb37abf1982af7ec26da1252f45b6dcdf91 0 257 809 2024-06-08T07:18:03Z PratyushKing 26 create Hyprland page wikitext text/x-wiki Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eyecandy. d9cd0e653f51d13ec58816ff178f750e34134ec5 810 809 2024-06-08T07:31:10Z PratyushKing 26 added Hyprland to wm category and added the infobox wikitext text/x-wiki Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eyecandy. {{SoftwareInfobox|caption=Hyprland logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|thumb|Hyprland logo]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} 418ff15167c7e3064b47c7aba4030d5036369346 811 810 2024-06-08T07:34:49Z PratyushKing 26 remove the unnecessary text wikitext text/x-wiki Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eyecandy. {{SoftwareInfobox|caption=|developers=The hyprwm team|image=[[File:Hyprland logo.png|thumb|Hyprland logo]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} aca3e77dd6842aedfc5969382dd1fa3951b790b8 812 811 2024-06-08T07:55:09Z PratyushKing 26 finally setting the infobox properly wikitext text/x-wiki Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eye candy. {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} 93caf354e85d1140699adf5951fb949c958fe2ce 813 812 2024-06-08T09:50:03Z Andre 27 Moved paragraph lower so it doesnt look so weird lol wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eye candy. 1e190e4d9af69744b090d292e649c07305e7da0e 816 813 2024-06-08T09:58:46Z Andre 27 added a screenshot of my desktop wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with neofetch and a browser with atl.wiki running along with it.]] Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eye candy. 9881dbad99e103f1ed04075687ffdfaa4eedc33f 817 816 2024-06-08T10:03:50Z Andre 27 [[Category:Desktop Environments]] wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with neofetch and a browser with atl.wiki running along with it.]] Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eye candy. [[Category:Desktop Environments]] b818911846fb45618b0e117b5a5172804d8ce617 824 817 2024-06-08T12:59:21Z Andre 27 linked neofetch for the future wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eye candy. [[Category:Desktop Environments]] 364e71cb2c93d90e3238b4927b0ae0e09112979f 835 824 2024-06-08T15:21:44Z PratyushKing 26 added Intro + Features (features may need a little review, i think i did a bit of bias) wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is quite optimized. === Features === There are tons of feature to this window manager like: * Smooth and animated graphics (such as moving windows, dragging them and in general opening and closing them) * Gradient customization for pretty much everything like window borders including gradient angles. * Nice integration with it's own apps (such as hyprpaper, hyprcursor and hypridle). * Compatibility with most wayland apps and support for <code>xorg-xwayland</code>. * Decent default configuration file auto-generated and has pretty much all important configurations setup for you (like touchpad tap to click, etc). === Installation === (WIP) [[Category:Desktop Environments]] adaca6c3c7d34928794045c3e80589d3facbfb8c 837 835 2024-06-08T15:48:12Z Remove empty section wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a tiling window manager that does not sacrifice on it's looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is quite optimized. === Features === There are tons of feature to this window manager like: * Smooth and animated graphics (such as moving windows, dragging them and in general opening and closing them) * Gradient customization for pretty much everything like window borders including gradient angles. * Nice integration with it's own apps (such as hyprpaper, hyprcursor and hypridle). * Compatibility with most wayland apps and support for <code>xorg-xwayland</code>. * Decent default configuration file auto-generated and has pretty much all important configurations setup for you (like touchpad tap to click, etc). [[Category:Desktop Environments]] 55e0b6fae9b523cce2c89cda0fa27b20b350266d 848 837 2024-06-08T17:09:16Z PratyushKing 26 added Installation properly wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling window manager that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is quite optimized. === Features === There are tons of feature to this window manager like: * Smooth and animated graphics (such as moving windows, dragging them and in general opening and closing them) * Gradient customization for pretty much everything like window borders including gradient angles. * Nice integration with it's own apps (such as hyprpaper, hyprcursor and hypridle). * Compatibility with most wayland apps and support for <code>xorg-xwayland</code>. * Decent default configuration file auto-generated and has pretty much all important configurations setup for you (like touchpad tap to click, etc). === Installation === To install Hyprland, it is recommended to use a rolling release or a semi-rolling release distributions. Most recommended ones include Arch Linux, Gentoo, NixOS, Fedora and openSUSE (Tumbleweed) due to them having the most recent packages and Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to try it on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package if you want to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : to add support for X11. * <code>legacy-renderer</code> : to enable the legacy renderer. * <code>systemd</code> : enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: NOT RECOMMENDED AND IS NOT SUPPORTED BY THE HYPRLAND DEVELOPERS. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the Ubuntu repo can be outdated. ==== Slackware ==== For Slackware, you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for Void Linux from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. [[Category:Desktop Environments]] 3637230c9993efa4d7e5d0fa68ff02389492c2ae 0 254 814 778 2024-06-08T09:51:33Z Andre 27 Added category wikitext text/x-wiki {{SoftwareInfobox | image = [[File:DynamicWindowManager.png|DWM logo]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot of somebody's desktop running DWM]]dwm (Dynamic Window Manager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. [[Category:Desktop Environments]] ba3091be8dabaa0de53a5237b856c992dd99a26f 836 814 2024-06-08T15:47:51Z Formatting wikitext text/x-wiki {{SoftwareInfobox | image = [[File:DynamicWindowManager.png|DWM logo]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot of somebody's desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. [[Category:Desktop Environments]] 7fe94cc83041c2bf12c898d3a830455648867aac 6 258 815 2024-06-08T09:56:55Z Andre 27 Screenshot of my hyprland desktop, showing the wiki and a neofetch wikitext text/x-wiki == Summary == Screenshot of my hyprland desktop, showing the wiki and a neofetch 1c3b5f0f587c76ff0d45d61999a85d4d124dc009 0 173 818 739 2024-06-08T10:06:13Z Andre 27 fixed typo wikitext text/x-wiki [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager (G'''DM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a graphical user interface that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[desktop environment]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.{{Citation needed}} [[Category:Terminology]] ec109666403942666e36f212d3f1ba2cc585c8e1 6 259 820 2024-06-08T10:16:19Z Andre 27 NixOS desktop running GNOME wikitext text/x-wiki == Summary == NixOS desktop running GNOME 1adefaca08785314274e8ed01210e0c93991f661 0 217 823 789 2024-06-08T10:22:22Z Andre 27 Added image wikitext text/x-wiki {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]] |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}} [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being [[RHEL|Red Hat Enterprise Linux]] (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] 211c7a5f94c9380c8d67c6cedc04ad75978e2025 6 260 825 2024-06-08T13:33:51Z Atmois 13 wikitext text/x-wiki Neofetch on NixOS 97302b54c9b418d5534811a9b0d3a63213cbc62a 0 261 826 2024-06-08T13:43:51Z Atmois 13 Create neofetch page wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2024-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch, github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]] (Neofetch-like utility written in [[C]]) and [[hyfetch]] (Fork of neofetch with pride flags). <references /> aaf8d66c1d20fefa6320f3704a78332b37ef0329 829 826 2024-06-08T13:58:22Z Andre 27 Fixed release date wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch, github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]] (Neofetch-like utility written in [[C]]) and [[hyfetch]] (Fork of neofetch with pride flags). <references /> ee9b6a029afe389bdf309deca4412cbab19e5c5c 6 262 827 2024-06-08T13:50:41Z Atmois 13 wikitext text/x-wiki Hyfetch on Arch cc4a589a14eb48f16e56bd1ec8ce036512faa221 828 827 2024-06-08T13:56:35Z Atmois 13 Atmois uploaded a new version of [[File:Hyfetch.png]] wikitext text/x-wiki Hyfetch on Arch cc4a589a14eb48f16e56bd1ec8ce036512faa221 0 263 834 2024-06-08T14:04:56Z Atmois 13 Create hyfetch page wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch, github.com/hykilpikonna/hyfetch] }} Hyfetch is an activly developed fork of [[Neofetch]] and is a command-line system information tool written in [[bash]] and [[python]] which displays information about your operating system, software and hardware with the option to colour the logos with pride flags. <references /> 616c61e8ec77348131de696d3a5432b073abc2d5 0 250 842 783 2024-06-08T16:09:51Z Remove empty sections wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (''AI'') is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (''LLMs''), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry [CITATION NEEDED] - but also on '''Advanced Micro Devices'''' (''AMD'') '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally [LINK NEEDED, perhaps GNU project] - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. * Do not use this to catfish. We trust you understand the basic moral complications of such activities, and if you choose to do so, ''beware''. (link to some article on the complications or what happens...) ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a [[Secondary GPU|Secondary/Dual GPU]] (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |} == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> f394ddb621386660548a4c53714bc72aed0def0e 845 842 2024-06-08T16:22:16Z Cleanup - more to review wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (''GPU''). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a [[Secondary GPU|Secondary/Dual GPU]] (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |} == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> 757c87829ac943a605e7dd6e76a5a4db4330d651 846 845 2024-06-08T16:22:28Z wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a [[Secondary GPU|Secondary/Dual GPU]] (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |} == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> de1a0aaeb2ebeb7110b1fd97f38dfd4d0ce2b587 0 1 844 707 2024-06-08T16:22:09Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[APT]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Pages with ignored display titles == * [[RHEL]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Artificial Intelligence on Linux]] * [[Hyfetch]] * [[Main Page]] * [[Neofetch]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' b92aed3283aae0ad99e55e4dfd55d70a72376b76 0 182 847 787 2024-06-08T16:28:48Z Move content from History to main description - didn't make sense to put it there. wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, [[Xfce]], [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a [[Linux Distributions|Linux distribution]] developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only [[Slackware]]. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[window managers]] instead of [[desktop environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] de60b98fdb70bcc1e2b2773aff3a3c570ff80a8a 0 254 849 836 2024-06-08T17:20:16Z Andre 27 rephrased a sentance wikitext text/x-wiki {{SoftwareInfobox | image = [[File:DynamicWindowManager.png|DWM logo]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. [[Category:Desktop Environments]] df442d0ecb5cfd778351c465cae2ff6d81b58412 850 849 2024-06-08T17:29:47Z Andre 27 added install guide. might add configuration guide too cus why the hell not wikitext text/x-wiki {{SoftwareInfobox | image = [[File:DynamicWindowManager.png|DWM logo]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can install the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight>dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. [[Category:Desktop Environments]] 87be3e96c45fb06c5a30567b62b8debbd6580709 852 850 2024-06-08T17:37:41Z Andre 27 im too lazy to summarize, figure it out wikitext text/x-wiki {{SoftwareInfobox | image = [[File:DynamicWindowManager.png|DWM logo]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can install the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight>dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:Desktop Environments]] 0417493441e96fa1820d3e00e7b08f5a67bac1c5 866 852 2024-06-08T19:28:01Z Andre 27 Added a few sentances and fixed one word wikitext text/x-wiki {{SoftwareInfobox | image = [[File:DynamicWindowManager.png|DWM logo]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:Desktop Environments]] f0e6b88a138b749a864e1cda6148262381182e95 898 866 2024-06-10T11:23:51Z Atmois 13 Change catagory wikitext text/x-wiki {{SoftwareInfobox | image = [[File:DynamicWindowManager.png|DWM logo]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:Window Manager]] 6a9f7cfafda6c0244d08b3c9f564200726fd542f 0 198 851 796 2024-06-08T17:32:34Z Asiliria 7 Repositioning as well as minor edits, moved Fedora down to RHEL based, openSUSE link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Ubuntu Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Ubuntu]] |A distribution based on [[Debian]] developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] 1f655a169ec70ca038010b116be4c0a158c0de93 856 851 2024-06-08T18:41:45Z Asiliria 7 Added Kali and moved Ubuntu - change Ubuntu later if poll finalizes <3 wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[./Https://www.kali.org/ Kali Linux] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" ISO with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] e4c93a9ee4673515f26a25a3f2896b279ca2f4ae 857 856 2024-06-08T18:42:03Z Asiliria 7 weird format bug wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" ISO with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |} [[Category:Linux Distributions]] 143e4592dbe53373f2762c34aae491c80ea0197f 858 857 2024-06-08T18:44:07Z Asiliria 7 All done adding :D wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an init system (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" ISO with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |} [[Category:Linux Distributions]] c6e4c1e4b3f63562831331e1ca81fc913865bf16 859 858 2024-06-08T18:59:54Z Andrew113 28 Added more distributions to the List of Linux Distributions. wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[init system]] (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro|Manjaro Linux]] |An arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" ISO with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A similar to [[Kali Linux]] distribution, designed for security, privacy, and development. ParrotOS has all the tools that are available in Kali Linux and also adds its own tools. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with [[RHEL]]. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 74ee6bade7f46765392ae9f42ab51982cc4ded6a 860 859 2024-06-08T19:11:00Z Asiliria 7 More distro additions wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[init system]] (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro|Manjaro Linux]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" ISO with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to [[Kali Linux]], Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with [[RHEL]]. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 4eab5f8304f32ff3fed2fb28d5cdc7e932255206 861 860 2024-06-08T19:18:24Z Andre 27 /* Gentoo Based */ Added funtoo to the gentoo list, but I'm not sure if the description is 100% correct. Please correct me if it isnt, i cant find a clear reason of existance for funtoo wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[init system]] (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro|Manjaro Linux]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" ISO with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to [[Kali Linux]], Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |Funtoo |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with [[RHEL]]. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 8302c08a6303e3cee30c4541039ae903bb55c76d 862 861 2024-06-08T19:21:56Z Andre 27 added artix and devuan because they are worth mentioning wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[init system]] (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro|Manjaro Linux]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |Artix |A fork of Arch Linux, which avoids the usage of systemd. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" ISO with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to [[Kali Linux]], Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |Devuan |A fork of [[Debian]], which avoids the usage of systemd. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |Funtoo |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with [[RHEL]]. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] b4fa5d2eb160f9b20273cc5fcee7e412509fa722 864 862 2024-06-08T19:26:02Z Asiliria 7 Extra details on Artix - please look into adding more depth for Dev wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[init system]] (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro|Manjaro Linux]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |Artix |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" ISO with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to [[Kali Linux]], Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of [[Debian]], which avoids the usage of systemd. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |Funtoo |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with [[RHEL]]. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 6c5f525995843e11c9a417760234005ef5e291e5 865 864 2024-06-08T19:26:45Z Asiliria 7 Linking up wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[init system]] (Such as systemd), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro|Manjaro Linux]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" ISO with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to [[Kali Linux]], Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of [[Debian]], which avoids the usage of systemd. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Enterprise Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary [citation] - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by RHEL. It aims to provide the latest software while maintaining a completely Free Software system. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with [[RHEL]]. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 1c06979446af3b155b0bdb8e78fa30d7678e519f 870 865 2024-06-08T19:52:01Z Atmois 13 Add reference for RHEL info, update info, add centOS stream, add puppy linux, add zorinOS, add pop!_OS, rename Manjarom, update links wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[init system]] (Such as [[systemd]]), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[Gnome|GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |} [[Category:Linux Distributions]] f7e75a15e9478db30997c006ec63423f1448a6ca 0 257 853 848 2024-06-08T17:44:12Z PratyushKing 26 minor caps change wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling window manager that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is quite optimized. === Features === There are tons of feature to this window manager like: * Smooth and animated graphics (such as moving windows, dragging them and in general opening and closing them) * Gradient customization for pretty much everything like window borders including gradient angles. * Nice integration with it's own apps (such as hyprpaper, hyprcursor and hypridle). * Compatibility with most wayland apps and support for <code>xorg-xwayland</code>. * Decent default configuration file auto-generated and has pretty much all important configurations setup for you (like touchpad tap to click, etc). === Installation === To install Hyprland, it is recommended to use a rolling release or a semi-rolling release distributions. Most recommended ones include Arch Linux, Gentoo, NixOS, Fedora and openSUSE (Tumbleweed) due to them having the most recent packages and Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to try it on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package if you want to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : to add support for X11. * <code>legacy-renderer</code> : to enable the legacy renderer. * <code>systemd</code> : enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended at all by the Hyprland developers and is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the Ubuntu repo can be outdated. ==== Slackware ==== For Slackware, you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for Void Linux from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. [[Category:Desktop Environments]] 3171600d92d9e6985f327696466f9ff1c7d2d583 854 853 2024-06-08T18:10:39Z PratyushKing 26 added Configuration & its first sub-topic Variables wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling window manager that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is quite optimized. === Features === There are tons of feature to this window manager like: * Smooth and animated graphics (such as moving windows, dragging them and in general opening and closing them) * Gradient customization for pretty much everything like window borders including gradient angles. * Nice integration with it's own apps (such as hyprpaper, hyprcursor and hypridle). * Compatibility with most wayland apps and support for <code>xorg-xwayland</code>. * Decent default configuration file auto-generated and has pretty much all important configurations setup for you (like touchpad tap to click, etc). === Installation === To install Hyprland, it is recommended to use a rolling release or a semi-rolling release distributions. Most recommended ones include Arch Linux, Gentoo, NixOS, Fedora and openSUSE (Tumbleweed) due to them having the most recent packages and Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to try it on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package if you want to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : to add support for X11. * <code>legacy-renderer</code> : to enable the legacy renderer. * <code>systemd</code> : enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended at all by the Hyprland developers and is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the Ubuntu repo can be outdated. ==== Slackware ==== For Slackware, you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for Void Linux from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables (This will have its own 7 sub-topics) * Binding Keys (bind and other variants) * Binding Special Keys (according to the XF86 specification) * Animations (quick overview) * Monitors (some references to <code>hyprctl</code>) ==== Variables ==== This is the most important part of your configuration file because it is pretty much your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Desktop Environments]] dfeb11456dc403ea8e73bdea358ee6a7578ba3a1 899 854 2024-06-10T11:24:20Z Atmois 13 Change catagory wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling window manager that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is quite optimized. === Features === There are tons of feature to this window manager like: * Smooth and animated graphics (such as moving windows, dragging them and in general opening and closing them) * Gradient customization for pretty much everything like window borders including gradient angles. * Nice integration with it's own apps (such as hyprpaper, hyprcursor and hypridle). * Compatibility with most wayland apps and support for <code>xorg-xwayland</code>. * Decent default configuration file auto-generated and has pretty much all important configurations setup for you (like touchpad tap to click, etc). === Installation === To install Hyprland, it is recommended to use a rolling release or a semi-rolling release distributions. Most recommended ones include Arch Linux, Gentoo, NixOS, Fedora and openSUSE (Tumbleweed) due to them having the most recent packages and Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to try it on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package if you want to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : to add support for X11. * <code>legacy-renderer</code> : to enable the legacy renderer. * <code>systemd</code> : enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended at all by the Hyprland developers and is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the Ubuntu repo can be outdated. ==== Slackware ==== For Slackware, you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for Void Linux from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables (This will have its own 7 sub-topics) * Binding Keys (bind and other variants) * Binding Special Keys (according to the XF86 specification) * Animations (quick overview) * Monitors (some references to <code>hyprctl</code>) ==== Variables ==== This is the most important part of your configuration file because it is pretty much your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Manager]] 8409af6cb60e44d34cd997aabadd575660b6d310 0 244 863 794 2024-06-08T19:22:37Z Asiliria 7 Added a silly article I wrote at HS for an engineering publication wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. ===== Steps ===== * '''Install flashprog and the lbmk repository -''' ... * ... (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] 091e2bbbe8f552d5306a5dc0760d86664730460d 867 863 2024-06-08T19:37:01Z Asiliria 7 Libreboot fill-ins wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. ===== Steps ===== * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. The Dell Optiplex 9020, after compiling your image should be named "dell9020mt_12mb." ** Flashprog, too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. * ... (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] 91eb88f72a716b61c73a516869cbc44893c0edd0 868 867 2024-06-08T19:38:42Z Asiliria 7 Rowe's own advice as well as warning wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. ===== Steps ===== As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your Dell OptiPlex machine. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. The Dell OptiPlex 9020, after compiling your image '''should be named''' "'''dell9020mt_12mb'''." ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. * ... (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] 3b1c95297366ac1352b555e727694d2bbd0eb9ff 871 868 2024-06-08T19:52:38Z Asiliria 7 The post-install Libreboot experience wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. ===== Steps ===== As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your Dell OptiPlex machine. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. The Dell OptiPlex 9020, after compiling your image '''should be named''' "'''dell9020mt_12mb'''." ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. * ... (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] 6145df0fd6ab292ef1e38a4316b22eb8b5bd1296 872 871 2024-06-08T19:53:52Z Asiliria 7 A small note on internal flashing as it appears in the Libreboot wiki wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. '''NOTE:''' After your first Libreboot, you are more than likely able to flash repeatedly afterwards without having to use a Pomona Flash Clip (below). Your device may vary. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. ===== Steps ===== As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your Dell OptiPlex machine. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. The Dell OptiPlex 9020, after compiling your image '''should be named''' "'''dell9020mt_12mb'''." ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. * ... (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] 28cf4f81988e708fc899d7673097f808793ce804 873 872 2024-06-08T19:55:55Z Asiliria 7 that should do it :D added details for device specificity wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. '''NOTE:''' After your first Libreboot, you are more than likely able to flash repeatedly afterwards without having to use a Pomona Flash Clip (below). Depending on your device, the flashing experience may and inevitably, at times, '''will''' vary. '''<u>Please check for your BIOS chip device on the Libreboot website.</u>''' == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. ===== Steps ===== As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your Dell OptiPlex machine. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. The Dell OptiPlex 9020, after compiling your image '''should be named''' "'''dell9020mt_12mb'''." ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. * ... (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] a505d2a380b9573b99be7480eef2ff8b6e0372e8 876 873 2024-06-08T19:58:43Z Asiliria 7 I think moving this to a dedicated Install section may be useful. wikitext text/x-wiki [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. '''NOTE:''' After your first Libreboot, you are more than likely able to flash repeatedly afterwards without having to use a Pomona Flash Clip (below). Depending on your device, the flashing experience may and inevitably, at times, '''will''' vary. '''<u>Please check for your BIOS chip device on the Libreboot website.</u>''' === Steps to Install === As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your machine using the Dell OptiPlex as an example. See below for an easier method for that specific device. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. For a Dell OptiPlex 9020, your image '''should be named''' "'''dell9020mt_12mb'''." after compilation. ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] 83c0ea56b054402007c699066394292f3dab5ab3 6 265 869 2024-06-08T19:51:17Z Asiliria 7 wikitext text/x-wiki Asiliria's OptiPlex running Libreboot 8771326d797e97320f5d3a7963abaf3ef8d4a185 0 261 874 829 2024-06-08T19:57:47Z Atmois 13 fix link wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]] (Neofetch-like utility written in [[C]]) and [[hyfetch]] (Fork of neofetch with pride flags). <references /> 05b9ee700ffd2099d3ac947492f033456c8b7f14 0 263 875 834 2024-06-08T19:58:09Z Atmois 13 fix link wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} Hyfetch is an activly developed fork of [[Neofetch]] and is a command-line system information tool written in [[bash]] and [[python]] which displays information about your operating system, software and hardware with the option to colour the logos with pride flags. <references /> f4362c3b54c8ab7bea175ef8553f03af5383c1d0 0 179 877 767 2024-06-08T20:01:35Z Asiliria 7 Adding Macintosh Devices to Common Issues - maybe consider repositioning as cleanup? wikitext text/x-wiki Not every install will be as flawless as a user will expect it to be, and they may encounter bugs for numerous reasons ranging from simple hardware differences to nuanced kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) === [[Linux on Apple Macintosh Devices|Linux on Apple Devices]] === If you use '''an Apple device,''' Linux may have a few issues running flawlessly on first install - '''this section details some steps you should consider taking if you have specific issues.''' === [[Artificial Intelligence on Linux]] === '''Covers w-okada, Stable Diffusion, Large Language Models, ROCm/CUDA with proper driver setup, anaconda/conda...''' [[Category:Guides]] 5482e971ad85b7af877b193215eaedea3849ce29 6 266 878 2024-06-09T09:28:03Z Atmois 13 Fastfetch on Fedora wikitext text/x-wiki == Summary == Fastfetch on Fedora 0fbfe34a14b6e81955f66319a2afccb184eba0e5 6 267 879 2024-06-09T09:28:22Z Andrew113 28 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 268 880 2024-06-09T09:28:38Z Atmois 13 Create page for fastfetch wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch github.com/fastfetch-cli/fastfetch] }} Fastfetch is a [[neofetch]]-like tool for fetching information about your operating system, software and hardware. It is written mainly in [[C]], with a focus on performance. bafcd9def244bd8a52fd205184f79e1cf88c1239 0 269 881 2024-06-09T10:29:17Z Andrew113 28 Made a new page about Budgie Desktop Environment. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Budgie logo.png]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern desktop designed to keep out the way of the user. Based on GNOME, budgie provides an easy to use interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] =Features= == • Budgie Desktop View== Budgie Desktop View is a software component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. == • Magpie== Magpie is a fork of the GNOME Project's Mutter window manager with Wayland support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. == • Budgie Control Center== Budgie Control Center is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. == • Budgie Screensaver== Budgie Screensaver is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. == • Budgie Backgrounds== Budgie Backgrounds is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. = Installation = Budgie is available on almost all linux distributions. === Arch-based systems === <syntaxhighlight lang="bash"> $ sudo pacman -S budgie </syntaxhighlight> In this case, budgie is a group of packages. If you wish to install only the desktop itself, install budgie-desktop. <syntaxhighlight lang="bash"> $ sudo pacman -S budgie-desktop </syntaxhighlight> It's also recommended to install nm-applet, the default GTK theme, and the default icon theme: <syntaxhighlight lang="bash"> sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet </syntaxhighlight> === Fedora Linux === Fedora has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. === Ubuntu === There is a [https://ubuntubudgie.org/ community ISO] that contains Ubuntu with Budgie Desktop instead of GNOME. === Void Linux === <syntaxhighlight lang="bash"> $ sudo xbps-install budgie-desktop </syntaxhighlight> === OpenSUSE === <syntaxhighlight lang="bash"> $ sudo zypper install budgie-desktop </syntaxhighlight> You can also choose Budgie as an option during the installation of OpenSUSE. 05e0e58c8ec8d6f385b7e71dab29d099489a1ad9 882 881 2024-06-09T20:38:19Z Atmois 13 Add DE catagory wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Budgie logo.png]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern desktop designed to keep out the way of the user. Based on GNOME, budgie provides an easy to use interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] =Features= == • Budgie Desktop View== Budgie Desktop View is a software component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. == • Magpie== Magpie is a fork of the GNOME Project's Mutter window manager with Wayland support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. == • Budgie Control Center== Budgie Control Center is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. == • Budgie Screensaver== Budgie Screensaver is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. == • Budgie Backgrounds== Budgie Backgrounds is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. = Installation = Budgie is available on almost all linux distributions. === Arch-based systems === <syntaxhighlight lang="bash"> $ sudo pacman -S budgie </syntaxhighlight> In this case, budgie is a group of packages. If you wish to install only the desktop itself, install budgie-desktop. <syntaxhighlight lang="bash"> $ sudo pacman -S budgie-desktop </syntaxhighlight> It's also recommended to install nm-applet, the default GTK theme, and the default icon theme: <syntaxhighlight lang="bash"> sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet </syntaxhighlight> === Fedora Linux === Fedora has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. === Ubuntu === There is a [https://ubuntubudgie.org/ community ISO] that contains Ubuntu with Budgie Desktop instead of GNOME. === Void Linux === <syntaxhighlight lang="bash"> $ sudo xbps-install budgie-desktop </syntaxhighlight> === OpenSUSE === <syntaxhighlight lang="bash"> $ sudo zypper install budgie-desktop </syntaxhighlight> You can also choose Budgie as an option during the installation of OpenSUSE. [[Category:Desktop Environments]] 62bc7255aa110f42ed97d024ef1cf7c9837320b2 0 1 883 844 2024-06-09T20:43:24Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[APT]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Pages with ignored display titles == * [[RHEL]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Misc == * [[Artificial Intelligence on Linux]] * [[Fastfetch]] * [[Hyfetch]] * [[Main Page]] * [[Neofetch]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' cfe910075a8477abc32a3d5f06e410f1d33a368e 6 270 884 2024-06-09T21:25:13Z Pseudify 33 wikitext text/x-wiki DNF 2767b03bfa1413dd8aa30d2d6c36a2ef688f71ac 0 272 886 2024-06-09T21:32:25Z Pseudify 33 Created page with "== Introduction: == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History: == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of t..." wikitext text/x-wiki == Introduction: == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History: == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features: == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage: == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility: == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development: == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion: == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. 2e92e79ccd5dbfe06246d1c93675d93357f1e3a0 887 886 2024-06-09T21:35:21Z Pseudify 33 /* Introduction: */ wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History: == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features: == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage: == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility: == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development: == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion: == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. 6790bc38abe317ad9b407b40954ed83aeb112f34 888 887 2024-06-09T21:35:31Z Pseudify 33 /* History: */ wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features: == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage: == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility: == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development: == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion: == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. ef53d05e75f5d1f788a1fcb6a49d92d70b289eda 889 888 2024-06-09T21:35:41Z Pseudify 33 /* Features: */ wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage: == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility: == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development: == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion: == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. 1cd4f8b5f43148beda1f715be33e10210cf32a6c 890 889 2024-06-09T21:35:51Z Pseudify 33 /* Usage: */ wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility: == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development: == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion: == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. a5c0874f9423510e5d7463afc00a1305636ceae3 891 890 2024-06-09T21:36:00Z Pseudify 33 /* Compatibility: */ wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development: == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion: == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. eafffa02e433778d67e530f1e4d5860eeabaa1cd 892 891 2024-06-09T21:36:08Z Pseudify 33 /* Community and Development: */ wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion: == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. 0727fa61643a2c82fc7f956c28ff25dfa89d2ae6 893 892 2024-06-09T21:36:15Z Pseudify 33 /* Conclusion: */ wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. 1c4d822954b4d5a8588fe9362a231e5768cc598c 2 273 894 2024-06-10T09:46:23Z Dainis 31 Created page with "I edit Latvian Wikipedia. Also known as Gatesby." wikitext text/x-wiki I edit Latvian Wikipedia. Also known as Gatesby. 756c0872f7152e1e72e369705aa70b5a6ce05e8a 0 274 895 2024-06-10T09:48:26Z Dainis 31 Created page with "'''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[bootloader]]s." wikitext text/x-wiki '''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[bootloader]]s. a8317263e59115ec2b8d219da2f075561570b1a0 897 895 2024-06-10T09:51:39Z Dainis 31 wikitext text/x-wiki '''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init system]]s. fa2bbe509fa84841b09fc5f05e4d4b3626b2eb03 0 275 896 2024-06-10T09:49:05Z Dainis 31 redir. wikitext text/x-wiki #REDIRECT [[Arch Linux]] 6940f5f1dee21428e534e6e7e2e1bb1fda6f0b73 0 227 900 833 2024-06-10T11:24:39Z Atmois 13 Change catagory wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic [[tiling window manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[awesome]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Window Manager]] 730e9ff6fa83a1c66419cec76293e5559f6f856a 0 239 901 791 2024-06-10T11:25:01Z Atmois 13 Change catagory wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most [[Package manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Window Manager]] bc038c902a39f533f04e3fb574ebd79fd3e8f407 932 901 2024-06-10T14:28:51Z Atmois 13 Update link wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most [[Package manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Window Managers]] 3036917d1654daa47ae0a6e665c4b9637a0b39f1 0 8 902 793 2024-06-10T11:35:27Z Atmois 13 Sepereated WM's and DE's and made the listed terms more consistant wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environments]] ** [[Gnome|GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[apk]] ** [[apt]] ** [[dnf]] ** [[dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager]] ** [[Dwm|DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] ae1092f5a3f3d531fd3d2ef9d258c28e601ffd47 909 902 2024-06-10T12:08:53Z Atmois 13 Update Links wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[apk]] ** [[apt]] ** [[dnf]] ** [[dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[Dwm|DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 35c16061476f5ebb838c08ec5516cc71fb518db4 921 909 2024-06-10T13:39:04Z Atmois 13 wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[apk]] ** [[apt]] ** [[dnf]] ** [[dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[Dwm|DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] fee39ff818ba75dc2da81f72d774c3ab17a640b1 0 269 903 882 2024-06-10T11:38:04Z use commons media instead wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern desktop designed to keep out the way of the user. Based on GNOME, budgie provides an easy to use interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] =Features= == • Budgie Desktop View== Budgie Desktop View is a software component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. == • Magpie== Magpie is a fork of the GNOME Project's Mutter window manager with Wayland support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. == • Budgie Control Center== Budgie Control Center is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. == • Budgie Screensaver== Budgie Screensaver is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. == • Budgie Backgrounds== Budgie Backgrounds is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. = Installation = Budgie is available on almost all linux distributions. === Arch-based systems === <syntaxhighlight lang="bash"> $ sudo pacman -S budgie </syntaxhighlight> In this case, budgie is a group of packages. If you wish to install only the desktop itself, install budgie-desktop. <syntaxhighlight lang="bash"> $ sudo pacman -S budgie-desktop </syntaxhighlight> It's also recommended to install nm-applet, the default GTK theme, and the default icon theme: <syntaxhighlight lang="bash"> sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet </syntaxhighlight> === Fedora Linux === Fedora has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. === Ubuntu === There is a [https://ubuntubudgie.org/ community ISO] that contains Ubuntu with Budgie Desktop instead of GNOME. === Void Linux === <syntaxhighlight lang="bash"> $ sudo xbps-install budgie-desktop </syntaxhighlight> === OpenSUSE === <syntaxhighlight lang="bash"> $ sudo zypper install budgie-desktop </syntaxhighlight> You can also choose Budgie as an option during the installation of OpenSUSE. [[Category:Desktop Environments]] f607742814c18b8cdff885f7d1fcdfe29a0459a1 947 903 2024-06-11T14:30:41Z Andrew113 28 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern desktop designed to keep out the way of the user. Based on GNOME, budgie provides an easy to use interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] =Features= == • Budgie Desktop View== Budgie Desktop View is a software component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. == • Magpie== Magpie is a fork of the GNOME Project's Mutter window manager with Wayland support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. == • Budgie Control Center== Budgie Control Center is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. == • Budgie Screensaver== Budgie Screensaver is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. == • Budgie Backgrounds== Budgie Backgrounds is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. = Installation = Budgie is available on almost all linux distributions. === Arch-based systems === <syntaxhighlight lang="bash"> $ sudo pacman -S budgie </syntaxhighlight> In this case, budgie is a group of packages. If you wish to install only the desktop itself, install budgie-desktop. <syntaxhighlight lang="bash"> $ sudo pacman -S budgie-desktop </syntaxhighlight> It's also recommended to install nm-applet, the default GTK theme, and the default icon theme: <syntaxhighlight lang="bash"> $ sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet </syntaxhighlight> === Fedora Linux === Fedora has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. === Ubuntu === There is a [https://ubuntubudgie.org/ community ISO] that contains Ubuntu with Budgie Desktop instead of GNOME. === Void Linux === <syntaxhighlight lang="bash"> $ sudo xbps-install budgie-desktop </syntaxhighlight> === OpenSUSE === <syntaxhighlight lang="bash"> $ sudo zypper install budgie-desktop </syntaxhighlight> You can also choose Budgie as an option during the installation of OpenSUSE. [[Category:Desktop Environments]] 29df10b5240b16d0ae39d539bc56e3bc379b3e0a 951 947 2024-06-11T18:27:18Z Atmois 13 Add links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], budgie provides an easy to use interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] =Features= == • Budgie Desktop View== Budgie Desktop View is a software component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. == • Magpie== Magpie is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. == • Budgie Control Center== Budgie Control Center is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. == • Budgie Screensaver== Budgie Screensaver is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. == • Budgie Backgrounds== Budgie Backgrounds is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. = Installation = Budgie is available on almost all [[Linux Distributions|linux distributions]]. === Arch-based systems === <syntaxhighlight lang="bash"> $ sudo pacman -S budgie </syntaxhighlight> In this case, budgie is a group of [[Package|packages]]. If you wish to install only the desktop itself, install budgie-desktop. <syntaxhighlight lang="bash"> $ sudo pacman -S budgie-desktop </syntaxhighlight> It's also recommended to install nm-applet, the default GTK theme, and the default icon theme: <syntaxhighlight lang="bash"> $ sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet </syntaxhighlight> === Fedora Linux === [[Fedora]] has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. === Ubuntu === There is a [https://ubuntubudgie.org/ community ISO] that contains [[Ubuntu]] with Budgie Desktop instead of GNOME. === Void Linux === <syntaxhighlight lang="bash"> $ sudo xbps-install budgie-desktop </syntaxhighlight> === OpenSUSE === <syntaxhighlight lang="bash"> $ sudo zypper install budgie-desktop </syntaxhighlight> You can also choose Budgie as an option during the installation of [[OpenSUSE]]. [[Category:Desktop Environments]] e0814676394bb24ace3e7bfd9e2555a151404988 0 171 905 822 2024-06-10T11:40:19Z use commons media instead wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] d94703b29559c6ae3d9a6711c23ad126db7ee06c 942 905 2024-06-11T03:30:23Z Arkannon 117 Added architecture along with a minor nit in Home Manager section wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options beyond the NixOS standard options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 00d20bd686b5192c0b3e165e9e80d3bf4d749d06 0 254 906 898 2024-06-10T11:41:35Z use commons media instead wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:Window Manager]] 6231ba5315a6cba77087459d98d9fc60eed8382e 933 906 2024-06-10T14:29:30Z Atmois 13 Fix catagory wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:Window Managers]] dfab0780d6801ef9f1e1ce3947c1d80674f4b793 0 182 907 847 2024-06-10T12:05:27Z Atmois 13 Fix links wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, [[Xfce]], [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a [[Linux Distributions|Linux distribution]] developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> Debian adheres to some of the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> In 1997, the Debian Project established the nonprofit organization Software in the Public Interest to sustain its financial support for development. Debian, one of the earliest operating systems built on the Linux kernel, remains active in development as of June 2024. It ranks as the second oldest Linux distribution, trailing only [[Slackware]]. The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. Regular updates are released, with each new candidate following a time-based freeze. === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[Window Manager|Window Managers]] instead of [[Desktop Environment|Desktop Environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /><references /> [[Category:Linux Distributions]] 852da4e58c0655f41fd63f054fb40b799166d278 0 198 908 870 2024-06-10T12:07:46Z Atmois 13 Update link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[init system]] (Such as [[systemd]]), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[DE / WM|Desktop Environments or Window Managers]] (Such as [[GNOME]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |} [[Category:Linux Distributions]] 8c4579596268810c55edc89d91d0659f6cd5b4db 914 908 2024-06-10T13:18:11Z Atmois 13 Update link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[init system]] (Such as [[systemd]]), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |} [[Category:Linux Distributions]] f2c04a35866bec42cac4f2c4bf23fc32c8a87dcb 915 914 2024-06-10T13:19:13Z Atmois 13 Update link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg|Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository (Repo)|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |} [[Category:Linux Distributions]] 10cba0d4ce00ea16edc1fc69f2a82afd388efd93 922 915 2024-06-10T13:43:44Z Atmois 13 Update link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |} [[Category:Linux Distributions]] 1ff83cbf76f4c7714456732ea6a38c5af6a58e6d 934 922 2024-06-10T15:24:14Z MymeType 35 Added entries for Slax wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), [[GNU]] tools and libraries, documentation, a [[Package manager|Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |} [[Category:Linux Distributions]] b0accea113b4ab18d37982b4ebc429df1db3a681 0 173 910 818 2024-06-10T12:09:23Z Atmois 13 Update link wikitext text/x-wiki [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager (G'''DM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a graphical user interface that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.{{Citation needed}} [[Category:Terminology]] 534075dd45c222c8691ec0ee45e30bdd1f3edcee 0 218 911 798 2024-06-10T12:10:15Z Atmois 13 Update links wikitext text/x-wiki == Introduction == [[Linux]] is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |Puppy Linux | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref>https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> 727eed6e49e1d3bd84e32346cdfa9ce67a289f6c 0 1 912 883 2024-06-10T13:09:42Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[APT]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Pages with ignored display titles == * [[RHEL]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Window Manager == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] == Misc == * [[Artificial Intelligence on Linux]] * [[Dnf]] * [[Fastfetch]] * [[Hyfetch]] * [[Main Page]] * [[Neofetch]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' f629cdff63d9f459b2e047d692560303dd0404ac 940 912 2024-06-10T18:45:01Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[APT]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Pages with ignored display titles == * [[RHEL]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] == Misc == * [[Artificial Intelligence on Linux]] * [[Dnf]] * [[Fastfetch]] * [[Hyfetch]] * [[Main Page]] * [[Neofetch]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' ce48b7208fbe47d6fc46a56d1dce384cd7a6a578 0 227 913 900 2024-06-10T13:16:08Z Atmois 13 Update link wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[awesome]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Window Manager]] 76cfc53205b587109c692c1eac95568a7b32f8dc 918 913 2024-06-10T13:36:44Z Atmois 13 Update link wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Window Manager]] cfbbd87e7726915bd0005b9786b60cd9a20fac75 931 918 2024-06-10T14:28:37Z Atmois 13 Fix catagory wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Window Managers]] 5c395a145d9f85b2260b8f3baba738dff41bcaf9 0 228 916 843 2024-06-10T13:20:10Z Atmois 13 Update link wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with [[AUR helpers]]. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, [[AUR helpers]] have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, [[pacman]] is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability.<references /> [[Category:Terminology]] bad31e9e1086ef4e1e28a2f3960a038ad3ecbaa6 920 916 2024-06-10T13:37:53Z Atmois 13 Remove link as its going under AUR page wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with AUR helpers. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, [[AUR helpers]] have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, [[pacman]] is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability.<references /> [[Category:Terminology]] b8b55c2e9b38348d7a84c87d2dc9e957cce6092c 923 920 2024-06-10T13:45:22Z Atmois 13 Remove link as its going under AUR page wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. Packages that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with AUR helpers. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, AUR helpers have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, [[pacman]] is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability.<references /> [[Category:Terminology]] f31a41de070a0126cb91f47f53d873bcb401eb65 950 923 2024-06-11T18:24:56Z Atmois 13 Add link wikitext text/x-wiki The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. [[Package|Packages]] that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with AUR helpers. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, AUR helpers have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, [[pacman]] is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability.<references /> [[Category:Terminology]] 8f94d35a56b7dc9123544f033708461a917a9e11 0 248 917 749 2024-06-10T13:34:26Z Andrew113 28 Minor changes wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|thumb]] | caption = Ubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[apt-get]], [[dpkg]], [[snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version of RHEL was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu receives 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] b97d7ba7e7124295b43aa0660a26c00ee397bbc6 925 917 2024-06-10T13:47:18Z Atmois 13 Update Links wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|thumb]] | caption = Ubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[apt]], [[dpkg]], [[snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version of RHEL was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu receives 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] 643e1369f9d413eb67b01956f2cb6981ab1a295e 6 276 919 2024-06-10T13:37:17Z Andrew113 28 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 274 924 897 2024-06-10T13:46:45Z Atmois 13 Update link wikitext text/x-wiki '''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[Init System]]s. fd2d04cb415f91939de819bffc9c8cfbb552ef04 0 272 926 893 2024-06-10T14:05:21Z Tux 1 wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. ca0600351ddb31e0bdbb7261192622d50714f862 0 277 927 2024-06-10T14:06:33Z Andrew113 28 Made a page about Rocky Linux wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_Logo.png|thumb]] | caption = Rocky Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] Rocky Linux is a Linux distribution developed by RSEF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit". It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. [[Category:Linux Distributions]] e4ef43957a44e2bf7be2fd56bc58f9be2bc424e8 928 927 2024-06-10T14:08:17Z Andrew113 28 i forgor the category tag wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_Logo.png|thumb]] | caption = Rocky Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] Rocky Linux is a Linux distribution developed by RSEF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit". It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. <references /> [[Category:Linux Distributions]] bcf61847f0f883d8537d24fb476f3e72d10a2d3f 936 928 2024-06-10T15:42:35Z Andrew113 28 wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_Logo.png|thumb]] | caption = Rocky Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] Rocky Linux is a Linux distribution developed by RSEF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit". It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. [[Category:Linux Distributions]] 9628f59fc56426bfa7f41140171d78ecaaed6a65 937 936 2024-06-10T15:45:28Z Andrew113 28 wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_Logo.png|thumb]] | caption = Rocky Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] Rocky Linux is a Linux distribution developed by RESF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit". It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. [[Category:Linux Distributions]] 24ba9aea57bd8c12734052f76eb45d7fa5683b62 0 240 929 706 2024-06-10T14:12:04Z Atmois 13 Restructured the page wikitext text/x-wiki == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your disribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most deriative distrobutions. ==== General Information ==== ===== Dual Booting ===== ===== Finding Alternatives for Apps ===== ==== Moving between specfic Operating Systems ==== ===== Moving to Linux from MacOS ===== ===== Moving to Linux from Windows ===== === General Information === [[Category:Guides]] be492a6b21c0701d62dd901a0c392c3290d6cc6c 0 257 930 899 2024-06-10T14:28:20Z Atmois 13 Fix catagory wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling window manager that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is quite optimized. === Features === There are tons of feature to this window manager like: * Smooth and animated graphics (such as moving windows, dragging them and in general opening and closing them) * Gradient customization for pretty much everything like window borders including gradient angles. * Nice integration with it's own apps (such as hyprpaper, hyprcursor and hypridle). * Compatibility with most wayland apps and support for <code>xorg-xwayland</code>. * Decent default configuration file auto-generated and has pretty much all important configurations setup for you (like touchpad tap to click, etc). === Installation === To install Hyprland, it is recommended to use a rolling release or a semi-rolling release distributions. Most recommended ones include Arch Linux, Gentoo, NixOS, Fedora and openSUSE (Tumbleweed) due to them having the most recent packages and Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to try it on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package if you want to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : to add support for X11. * <code>legacy-renderer</code> : to enable the legacy renderer. * <code>systemd</code> : enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended at all by the Hyprland developers and is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the Ubuntu repo can be outdated. ==== Slackware ==== For Slackware, you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for Void Linux from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables (This will have its own 7 sub-topics) * Binding Keys (bind and other variants) * Binding Special Keys (according to the XF86 specification) * Animations (quick overview) * Monitors (some references to <code>hyprctl</code>) ==== Variables ==== This is the most important part of your configuration file because it is pretty much your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Managers]] 1a4b09f5c1962ecadd5de96b5564868089015c00 6 278 935 2024-06-10T15:39:27Z MymeType 35 wikitext text/x-wiki Screenshot of the animation that plays when running Hyfetch in June. 1a8c82c39a6ef0120bc2ef0c3bab2fcb3b791f8a 0 2 938 782 2024-06-10T15:58:05Z Asiliria 7 Archinstall Addition wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the [[Arch User Repository|AUR]], Arch's well known user repository, possible. === Arch Installation Script === {| class="wikitable" |+ !Mirrors !Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales !Select your keyboard layout. |- !Disk Configuration and Partitioning !While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption !This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader !You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   !(Someone more experienced can fill) |- !Swap Memory !The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name !The name of your machine. |- !Root Password   !Set a password for the root account. |- !Profile and Drivers !Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager !Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio !It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels !There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages !Name any additional packages you may want (e.g. Firefox) |- !Network Configuration ! |} === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 03ffd253bcf8e3c7c48c1b70335fe14947181c98 0 263 939 875 2024-06-10T16:30:12Z MymeType 35 Added Features and Trivia section wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your operating system, software and hardware with the option to color the logos with pride flags. === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run <code>hyfetch</code> in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. <references /> 4babc2c6802ed17ddead48dcdae2711efb605fc0 0 235 941 802 2024-06-10T18:54:05Z MymeType 35 Added section detailing some of the important options of make.conf wikitext text/x-wiki {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every [[Gentoo]] and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the [[package manager]], although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. === Configuration === Configuration of Portage is done through various configuration files and folders found in /etc/portage, which allows configuration of features such as USE flags, default options, masked packages and more. ==== make.conf ==== make.conf is the main configuration file for Portage. It allows the configuration of system-wide USE flags, Portage features, accepted licenses and more. This file is regularly edited during the Gentoo installation process and during ordinary use of it, so it's very important to get the options right for it. Below are some of the most relevant ones. ===== COMMON_FLAGS, CFLAGS, CXXFLAGS, FCFFLAGS and FFLAGS ===== These variables determine the build and compile flags that will be used for all package compilations. The CFLAGS variable is for C applications, while the CXXFLAGS one is meant for C++ ones. Most users will keep these variables identical. A "safe" configuration to avoid compilation errors should look like this:<blockquote><code>COMMON_FLAGS="-march=native -O2 -pipe"</code> <code>CFLAGS="${COMMON_FLAGS}"</code> <code>CXXFLAGS="${COMMON_FLAGS}"</code> <code>FCFLAGS="${COMMON_FLAGS}"</code> <code>FFLAGS="${COMMON_FLAGS}"</code></blockquote> ===== MAKEOPTS ===== The MAKEOPTS variable is used to specify arguments that will be passed to [[Make]] during compilation. A good rule of thumb is to set the -j argument to about half your RAM size and the -l argument to the thread count of your CPU, which can be found by running <code>nproc</code>. For example, if you have 4 GB of RAM and a 6th generation Intel Core i3, your MAKEOPTS variable should look something like this:<blockquote><code>MAKEOPTS="-j2 -l4"</code></blockquote> ===== GENTOO_MIRRORS ===== The GENTOO_MIRRORS variable tells Portage what mirror(s) to download the packages from. It can be set manually by editing the variable with a link to the mirror(s) of your liking available [https://www.gentoo.org/downloads/mirrors/ here], or automatically via <code>mirrorselect</code>, which can select the fastest mirror(s) for you. It's highly recommended to set this variable to a mirror close to you, for example, if you want to use an Italian mirror you would have to edit the variable like this:<blockquote><code>GENTOO_MIRRORS="<nowiki>https://gentoo.mirror.garr.it/</nowiki>"</code></blockquote> ===== FEATURES ===== The FEATURES variable contains a list of features that you can enable which notably alters the behavior of Portage. For example, if you want to use binary packages and verify their signatures, you would have to set the variable like this:<blockquote><code>FEATURES="getbinpkg binpkg-request-signature"</code></blockquote> ===== EMERGE_DEFAULT_OPTS ===== The EMERGE_DEFAULT_OPTS variable contains the options that will be automatically set when running Portage every time. For example, if you want Portage to ask for confirmation and verbose output, you would set the variable to this:<blockquote><code>EMERGE_DEFAULT_OPTS="--ask --verbose"</code></blockquote> ===== USE ===== The USE variable allows the '''system-wide''' enabling or disabling of USE flags. An example of this variable may look like this:<blockquote><code>USE="pulseaudio X systemd dbus policykit udisks dist-kernel -alsa -wayland xwayland"</code></blockquote> ===== USE_EXPAND ===== USE_EXPAND is a set of variables that serve to extend the capabilities of USE flags. Below are the most relevant ones. ====== VIDEO_CARDS ====== VIDEO_CARDS is a variable that serves to specify the drivers you wish to install for your GPUs. For example, if you want to install the drivers for AMD and Intel graphics, you would set the variable to this:<blockquote><code>VIDEO_CARDS="amdgpu radeonsi intel"</code></blockquote> ====== CPU_FLAGS_* ====== The CPU_FLAGS_* variables specify the available features that your CPU has to optimize compiling packages. The currently available variables are CPU_FLAGS_X86 (for x86 and x86_64 architectures), CPU_FLAGS_ARM (for ARM and ARM64 architectures) and CPU_FLAGS_PPC (for PowerPC and PowerPC64 architectures). The <code>cpuid2cpuflags</code> utility can be used to find these flags. The output of this command may look something like this:<blockquote><code>CPU_FLAGS_X86: aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3</code></blockquote>The output can then be copied to make.conf. ===== ACCEPT_LICENSE ===== The ACCEPT_LICENSE variable can be used to tell Portage which type of licenses are allowed. Generally, it's preferred to not accept proprietary software licenses. To allow every license except proprietary ones, you can set the variable to this:<blockquote><code>ACCEPT_LICENSE="* -@EULA"</code></blockquote> [[Category:Package Managers]] c73bde8b7434e8ca997efd6dd55559fa72987967 0 279 943 2024-06-11T03:45:23Z Arkannon 117 Created page with "{{SoftwareInfobox | title = OpenSUSE | releasestatus = Maintained | lastrelease = 15.6 | developers = SUSE | website = [https://www.opensuse.org/] }}" wikitext text/x-wiki {{SoftwareInfobox | title = OpenSUSE | releasestatus = Maintained | lastrelease = 15.6 | developers = SUSE | website = [https://www.opensuse.org/] }} 48e339714beebd94d336ff5f44279f6e930431d9 944 943 2024-06-11T04:30:49Z Arkannon 117 wikitext text/x-wiki OpenSUSE is a linux distribution developed by the SUSE S.A., a software company that provides linux services to business and enterprise customers. particular feature that stands out is their in-house installer, YaST2, of the operating system that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with GUI and TUI options. This distribution stands out by having two variations of the distributions: OpenSUSE Tumbleweed is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. OpenSUSE Leap is the point release version, with a new release every year with older and more stable packages meant for business use. 2468d420cf9e6e4bfeac1d27cb40cd7c548f184f 6 280 945 2024-06-11T08:55:02Z MymeType 35 Logo of GNUstep and Window Maker wikitext text/x-wiki == Summary == Logo of GNUstep and Window Maker 17b05c3247bb385d4a3a0c36c5e2a655bf04c32d 0 281 946 2024-06-11T09:18:53Z MymeType 35 Created Window Maker page wikitext text/x-wiki Window Maker is a [[window manager]] for [[X11]] designed to emulate the look and feel of [[NeXTSTEP]] as an environment compatible with [[OpenStep]] libraries. It has been developed from scratch since 1997 by Alfredo Kojima in C. === Installation === Window Maker can be installed from most [[Package manager|package managers]]. On [[Debian]] and Debian-based distributions:<blockquote> # apt install wmaker </blockquote>On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]:<blockquote> $ yay -S windowmaker </blockquote>On [[Gentoo]] and Gentoo-based distributions:<blockquote> # emerge -av x11-wm/windowmaker </blockquote>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<blockquote> # dnf install WindowMaker </blockquote>If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running:<blockquote> $ wget <nowiki>https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz</nowiki> $ tar xvf WindowMaker-0.96.0.tar.gz $ cd WindowMaker-0.96.0.tar.gz $ ./configure --prefix=/usr $ make $ sudo make install </blockquote> fce403ecbd9a8b3d4b6e3a5a6fa1b3562649c3c1 948 946 2024-06-11T14:44:01Z Andrew113 28 changed blocks to syntax highlight wikitext text/x-wiki Window Maker is a [[window manager]] for [[X11]] designed to emulate the look and feel of [[NeXTSTEP]] as an environment compatible with [[OpenStep]] libraries. It has been developed from scratch since 1997 by Alfredo Kojima in C. === Installation === Window Maker can be installed from most [[Package manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang=""> # apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang=""> $ yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang=""> # emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang=""> # dnf install WindowMaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang=""> $ wget <nowiki>https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz</nowiki> </syntaxhighlight> <syntaxhighlight lang=""> $ tar xvf WindowMaker-0.96.0.tar.gz </syntaxhighlight> <syntaxhighlight lang=""> $ cd WindowMaker-0.96.0.tar.gz </syntaxhighlight> <syntaxhighlight lang=""> $ ./configure --prefix=/usr </syntaxhighlight> <syntaxhighlight lang=""> $ make </syntaxhighlight> <syntaxhighlight lang=""> # make install </syntaxhighlight> b7ead82b5f9fa66af0b09c41464950ec845266b6 949 948 2024-06-11T16:31:23Z Andrew113 28 added category + minor stuff wikitext text/x-wiki Window Maker is a [[window manager]] for [[X11]] designed to emulate the look and feel of [[NeXTSTEP]] as an environment compatible with [[OpenStep]] libraries. It has been developed from scratch since 1997 by Alfredo Kojima in C. === Installation === Window Maker can be installed from most [[Package manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang=""> # apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang=""> $ yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang=""> # emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang=""> # dnf install WindowMaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang=""> $ wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz </syntaxhighlight> <syntaxhighlight lang=""> $ tar xvf WindowMaker-0.96.0.tar.gz </syntaxhighlight> <syntaxhighlight lang=""> $ cd WindowMaker-0.96.0.tar.gz </syntaxhighlight> <syntaxhighlight lang=""> $ ./configure --prefix=/usr </syntaxhighlight> <syntaxhighlight lang=""> $ make </syntaxhighlight> <syntaxhighlight lang=""> # make install </syntaxhighlight> [[Category:Window Managers]] c01cdf7b20865bcef85a975f6719f2f66e951041 0 248 953 925 2024-06-12T11:45:36Z Dainis 31 removed thumbed image (don't thumb images in an infobox) wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[apt]], [[dpkg]], [[snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version of RHEL was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu receives 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] 2c38ab4a47677c424610fca4238d583a6633f24d 959 953 2024-06-12T13:45:55Z Atmois 13 Fix error wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[apt]], [[dpkg]], [[snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu receives 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] 347cdcecf101294709d9a39c8a9497ef440cda26 0 274 954 924 2024-06-12T11:52:34Z Dainis 31 wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = [[tty]], [[KDE]], [[Xfce]], [[Cinamon]] | usagetype = Desktop, Server | architectures = amd64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init System]]s. 773c821e4ee333ed88b5f633578f0b6d189a5658 955 954 2024-06-12T11:52:46Z Dainis 31 wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = [[tty]], [[KDE]], [[Xfce]], [[Cinamon]] | usagetype = Desktop, Server | architectures = amd64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init system]]s. a42546d401fd892dee2fbb41d4178e522362c281 957 955 2024-06-12T11:55:17Z Dainis 31 wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = [[tty]], [[KDE]], [[Xfce]], [[Cinamon]] | usagetype = Desktop, Server | architectures = amd64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init system]]s. d2f6b095c2dba77c8d1ed4163ae76319c64eef84 6 282 956 2024-06-12T11:54:40Z Dainis 31 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 2 958 938 2024-06-12T12:52:43Z Asiliria 7 Fixing all bold text wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the [[Arch User Repository|AUR]], Arch's well known user repository, possible. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration | |} === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 3201ea49bd79abfbb4577ff46e2bd5b6049394d9 977 958 2024-06-14T23:47:40Z Asiliria 7 Final touches (summer break - expect more coming!) wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the [[Arch User Repository|AUR]], Arch's well known user repository, possible. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] afe1fbe041c17ca9a42f4b452f555b80205ec3a9 984 977 2024-06-15T09:37:16Z Atmois 13 update links wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === One of the distinguishing traits of Arch Linux from other distributions is the presence of its [[Package Manager|package manager]] called ''[[pacman]].'' Pacman's main goal is to offer binary packages with an "intuitive build system" that is easy to maintain and manage.<ref>Arch Linux Wiki - About[https://archlinux.org/about/]</ref> This build system is what makes the [[Arch User Repository|AUR]], Arch's well known user repository, possible. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 3071235af227afb9b1cb22b6920c662685a44f13 2 283 960 2024-06-12T20:40:14Z Delta 39 Created page with "hi" wikitext text/x-wiki hi c22b5f9178342609428d6f51b2c5af4c0bde6a42 0 1 961 940 2024-06-13T02:54:15Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing A Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[RHEL]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[APT]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Pages with ignored display titles == * [[RHEL]] == Pages with syntax highlighting errors == * [[Window Maker]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Dnf]] * [[Fastfetch]] * [[Hyfetch]] * [[Main Page]] * [[Neofetch]] * [[OpenSUSE]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' d7daa5bf02c9a55e190ed6871f414dcb6b9258c7 994 961 2024-06-15T13:09:39Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Pages with syntax highlighting errors == * [[Window Maker]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Fastfetch]] * [[Hyfetch]] * [[Main Page]] * [[Neofetch]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 84c32106675bb6ae33dd0d47d1d040e162f706dc 0 240 962 929 2024-06-13T11:45:22Z Atmois 13 Add info on multi booting wikitext text/x-wiki == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your disribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most deriative distrobutions. ==== General Information ==== ===== Multi Booting ===== [[File:GRUB with ubuntu and windows vista.png|thumb|GRUB, with entries for Ubuntu and Windows Vista, an example of ''dual booting.'']] [[Multi-Booting|Multi Booting]] (Or often refered to as 'Dual Booting') is the process of installing multiple [[Operating Systems|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completly removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to parititon the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly reccomended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi-Booting|Multi Booting]] page. ===== Finding Alternatives for Apps ===== ==== Moving between specfic Operating Systems ==== ===== Moving to Linux from MacOS ===== ===== Moving to Linux from Windows ===== === General Information === [[Category:Guides]] c67ea958c9afb3c3fd4d6f1c4563c40e31fef2a4 963 962 2024-06-13T11:47:09Z Atmois 13 Fix link wikitext text/x-wiki == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your disribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most deriative distrobutions. ==== General Information ==== ===== Multi Booting ===== [[File:GRUB with ubuntu and windows vista.png|thumb|GRUB, with entries for Ubuntu and Windows Vista, an example of ''dual booting.'']] [[Multi Booting]] (Or often refered to as 'Dual Booting') is the process of installing multiple [[Operating Systems|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completly removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to parititon the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly reccomended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi Booting]] page. ===== Finding Alternatives for Apps ===== ==== Moving between specfic Operating Systems ==== ===== Moving to Linux from MacOS ===== ===== Moving to Linux from Windows ===== === General Information === [[Category:Guides]] d0b4e909d338177b398076f4a0a94079bb87276a 981 963 2024-06-15T09:35:16Z Atmois 13 Add info on workarounds and alternatives wikitext text/x-wiki == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your disribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most deriative distributions. ==== General Information ==== ===== Multi Booting ===== [[File:GRUB with ubuntu and windows vista.png|thumb|GRUB, with entries for [[Ubuntu]] and Windows Vista, an example of ''dual booting.'']] [[Multi Booting]] (Or often refered to as 'Dual Booting') is the process of installing multiple [[Operating Systems|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completly removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to parititon the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly reccomended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi Booting]] page. ===== Finding Alternatives or Workarounds for Apps ===== Often there is at least one [[application]] missing on Linux or an app that is missing some features or is buggy so you'll find yourself looking for alternative options. There also sometimes is the issue that your distribution doesn't have an app but another distribution does have it. A good place to start when looking for alternatives is [https://alternativeto.net AlternativeTo] which is a crowdsourced site useful to find alternatives for almost any app. Other useful sites include [https://www.privacytools.io Privacy Tools] and [https://awesome-privacy.xyz Awesome Privacy] with a privacy focused list of apps. When looking for workarounds for apps not supported for your distribution you should first check [https://flathub.org Flathub] and [https://snapcraft.io Snapcraft] (Note that [[Snap|Snaps]] are known to have performance issues) if your app is available there as they offer support for most distributions. If a steam game lacks native Linux support try checking [https://www.protondb.com ProtonDB] if Valve's proton tool supports your game. [https://www.winehq.org Wine] is also an option to run Windows apps on Linux. ==== Moving between specfic Operating Systems ==== ===== Moving to Linux from MacOS ===== ===== Moving to Linux from Windows ===== === General Information === [[Category:Guides]] a47adaa64b3d23a38da66b38b60de0ea3eeeefa5 0 225 968 819 2024-06-13T11:55:16Z Atmois 13 Try to fix display title? wikitext text/x-wiki {{DISPLAYTITLE:Red Hat Enterprise Linux (RHEL)}} {{DISPLAYTITLE:Red Hat Enterprise Linux}} == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64, x86-64-v2 | website = [https://redhat.com/rhel/ redhat.com] }} [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] Red Hat Enterprise Linux, commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] 983de79c0e2b4e2f2f86c2ea71fa8011a5a670f0 969 968 2024-06-13T12:28:12Z wikitext text/x-wiki {{DISPLAYTITLE:Red Hat Enterprise Linux (RHEL)}} {{DISPLAYTITLE:Red Hat Enterprise Linux}} == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64, x86-64-v2 | website = [https://redhat.com/rhel/ redhat.com] }} [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] d29a0bc198f489e5739196155e5452f7a20bd381 973 969 2024-06-13T18:37:00Z Atmois 13 Atmois moved page [[RHEL]] to [[Red Hat Enterprise Linux]]: rename to full name wikitext text/x-wiki {{DISPLAYTITLE:Red Hat Enterprise Linux (RHEL)}} {{DISPLAYTITLE:Red Hat Enterprise Linux}} == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64, x86-64-v2 | website = [https://redhat.com/rhel/ redhat.com] }} [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business costumers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] d29a0bc198f489e5739196155e5452f7a20bd381 975 973 2024-06-13T18:38:24Z Atmois 13 fix spelling + rename display title wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64, x86-64-v2 | website = [https://redhat.com/rhel/ redhat.com] }} [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business customers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] e1e967055cf122510616138305884d3face99bed 0 247 970 780 2024-06-13T12:32:48Z wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on Ubuntu.]]|caption=|title=APT|releasestatus=Maintained|lastrelease=2.9.4 / 25 May 2024 | languages=C++, shell script, EML, CMake, C, Perl | developers=The Debian Project | website=[packages.debian.org packages.debian.org]}} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html "apt-get(8)"]. Debian Manpages.</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. [[Category:Package Managers]] a066b8568c5637988f7ee70ee93147a80c192917 979 970 2024-06-15T09:20:43Z Atmois 13 update link wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]]|caption=|title=APT|releasestatus=Maintained|lastrelease=2.9.4 / 25 May 2024 | languages=C++, shell script, EML, CMake, C, Perl | developers=The Debian Project | website=[packages.debian.org packages.debian.org]}} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html "apt-get(8)"]. Debian Manpages.</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. [[Category:Package Managers]] df4564e53d0e04ca14bed487e97c3fe850a5b236 0 287 974 2024-06-13T18:37:00Z Atmois 13 Atmois moved page [[RHEL]] to [[Red Hat Enterprise Linux]]: rename to full name wikitext text/x-wiki #REDIRECT [[Red Hat Enterprise Linux]] 4d901a7028597d8e5e734c22ade8785943bef558 0 279 976 944 2024-06-13T19:53:18Z Atmois 13 add distro catagory wikitext text/x-wiki OpenSUSE is a linux distribution developed by the SUSE S.A., a software company that provides linux services to business and enterprise customers. particular feature that stands out is their in-house installer, YaST2, of the operating system that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with GUI and TUI options. This distribution stands out by having two variations of the distributions: OpenSUSE Tumbleweed is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. OpenSUSE Leap is the point release version, with a new release every year with older and more stable packages meant for business use. [[Category:Linux Distributions]] 72baa7a973d3416a6064c4ec6b429226d075f2ec 978 976 2024-06-15T09:00:46Z Atmois 13 add infobox, update links, fix grammer wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|thumb]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, ppc64, x86_64 | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. This distribution stands out by having two variations of the distributions: OpenSUSE Tumbleweed is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. OpenSUSE Leap is the point release version, with a new release every year with older and more stable packages meant for business use. [[Category:Linux Distributions]] ef51d02d7607996d8499fd444461217ec4afc1a0 0 272 980 926 2024-06-15T09:21:04Z Atmois 13 Add category tag wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. [[Category:Package Managers]] a308e483a3125fcdcbc3f0f8a6eeee6012392257 0 169 982 800 2024-06-15T09:36:40Z Atmois 13 Atmois moved page [[Package manager]] to [[Package Manager]]: Fix capatlisation on title wikitext text/x-wiki == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. [[Category:Terminology]] 16012d694835ebb3d675aff9912a11bdc413b217 0 288 983 2024-06-15T09:36:40Z Atmois 13 Atmois moved page [[Package manager]] to [[Package Manager]]: Fix capatlisation on title wikitext text/x-wiki #REDIRECT [[Package Manager]] adf819fee97ba35d21dcfe190e178867a7f3eeb9 0 171 986 942 2024-06-15T09:37:59Z Atmois 13 Update Links wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = The NixOS Logo | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options beyond the NixOS standard options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 7460c10ae5d62896e748b527daf1dce977423e41 0 175 987 801 2024-06-15T09:38:14Z Atmois 13 Update Links wikitext text/x-wiki {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Pacman 401.png|thumb|[[Pacman]]]] == Intro == The [[Linux Distributions|Linux distribution]] [[Arch Linux]] and its derivatives usually use a [[Package Manager|package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] [[Category:Package Managers]] e4cd2b83b35f1451f23b509ec7c2f73541fdd116 0 198 988 934 2024-06-15T09:38:57Z Atmois 13 Update link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |} [[Category:Linux Distributions]] 4ae457796867d8bc4b4273c466b0aa82a10329a6 0 223 989 687 2024-06-15T09:39:37Z Atmois 13 Update Links wikitext text/x-wiki == Distrohopping == Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (eg. FSF approved distribution) * Ecosystem or Tooling (eg. libc, [[Package Manager|package manager]], coreutils, [[Init System|init system]]) * Experimentation * Customization ... and many more. This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (eg. Debianisms, [[Package Manager|package managers]], init systems) * Opinionated design philosophies (eg. Nix, Guix, Fedora Atomic) * Additional configuration needs (eg. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (eg. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (eg. Liberapay, Github sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] 5cc97f107251e44072235282cfe495de67e053bf 0 235 990 941 2024-06-15T09:39:53Z Atmois 13 Update link wikitext text/x-wiki {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every [[Gentoo]] and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the [[Package Manager|package manager]], although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. === Configuration === Configuration of Portage is done through various configuration files and folders found in /etc/portage, which allows configuration of features such as USE flags, default options, masked packages and more. ==== make.conf ==== make.conf is the main configuration file for Portage. It allows the configuration of system-wide USE flags, Portage features, accepted licenses and more. This file is regularly edited during the Gentoo installation process and during ordinary use of it, so it's very important to get the options right for it. Below are some of the most relevant ones. ===== COMMON_FLAGS, CFLAGS, CXXFLAGS, FCFFLAGS and FFLAGS ===== These variables determine the build and compile flags that will be used for all package compilations. The CFLAGS variable is for C applications, while the CXXFLAGS one is meant for C++ ones. Most users will keep these variables identical. A "safe" configuration to avoid compilation errors should look like this:<blockquote><code>COMMON_FLAGS="-march=native -O2 -pipe"</code> <code>CFLAGS="${COMMON_FLAGS}"</code> <code>CXXFLAGS="${COMMON_FLAGS}"</code> <code>FCFLAGS="${COMMON_FLAGS}"</code> <code>FFLAGS="${COMMON_FLAGS}"</code></blockquote> ===== MAKEOPTS ===== The MAKEOPTS variable is used to specify arguments that will be passed to [[Make]] during compilation. A good rule of thumb is to set the -j argument to about half your RAM size and the -l argument to the thread count of your CPU, which can be found by running <code>nproc</code>. For example, if you have 4 GB of RAM and a 6th generation Intel Core i3, your MAKEOPTS variable should look something like this:<blockquote><code>MAKEOPTS="-j2 -l4"</code></blockquote> ===== GENTOO_MIRRORS ===== The GENTOO_MIRRORS variable tells Portage what mirror(s) to download the packages from. It can be set manually by editing the variable with a link to the mirror(s) of your liking available [https://www.gentoo.org/downloads/mirrors/ here], or automatically via <code>mirrorselect</code>, which can select the fastest mirror(s) for you. It's highly recommended to set this variable to a mirror close to you, for example, if you want to use an Italian mirror you would have to edit the variable like this:<blockquote><code>GENTOO_MIRRORS="<nowiki>https://gentoo.mirror.garr.it/</nowiki>"</code></blockquote> ===== FEATURES ===== The FEATURES variable contains a list of features that you can enable which notably alters the behavior of Portage. For example, if you want to use binary packages and verify their signatures, you would have to set the variable like this:<blockquote><code>FEATURES="getbinpkg binpkg-request-signature"</code></blockquote> ===== EMERGE_DEFAULT_OPTS ===== The EMERGE_DEFAULT_OPTS variable contains the options that will be automatically set when running Portage every time. For example, if you want Portage to ask for confirmation and verbose output, you would set the variable to this:<blockquote><code>EMERGE_DEFAULT_OPTS="--ask --verbose"</code></blockquote> ===== USE ===== The USE variable allows the '''system-wide''' enabling or disabling of USE flags. An example of this variable may look like this:<blockquote><code>USE="pulseaudio X systemd dbus policykit udisks dist-kernel -alsa -wayland xwayland"</code></blockquote> ===== USE_EXPAND ===== USE_EXPAND is a set of variables that serve to extend the capabilities of USE flags. Below are the most relevant ones. ====== VIDEO_CARDS ====== VIDEO_CARDS is a variable that serves to specify the drivers you wish to install for your GPUs. For example, if you want to install the drivers for AMD and Intel graphics, you would set the variable to this:<blockquote><code>VIDEO_CARDS="amdgpu radeonsi intel"</code></blockquote> ====== CPU_FLAGS_* ====== The CPU_FLAGS_* variables specify the available features that your CPU has to optimize compiling packages. The currently available variables are CPU_FLAGS_X86 (for x86 and x86_64 architectures), CPU_FLAGS_ARM (for ARM and ARM64 architectures) and CPU_FLAGS_PPC (for PowerPC and PowerPC64 architectures). The <code>cpuid2cpuflags</code> utility can be used to find these flags. The output of this command may look something like this:<blockquote><code>CPU_FLAGS_X86: aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3</code></blockquote>The output can then be copied to make.conf. ===== ACCEPT_LICENSE ===== The ACCEPT_LICENSE variable can be used to tell Portage which type of licenses are allowed. Generally, it's preferred to not accept proprietary software licenses. To allow every license except proprietary ones, you can set the variable to this:<blockquote><code>ACCEPT_LICENSE="* -@EULA"</code></blockquote> [[Category:Package Managers]] faa1bb07ebc329214008acbe6c328810238b9471 0 239 991 932 2024-06-15T09:40:04Z Atmois 13 Update link wikitext text/x-wiki {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Window Managers]] 751bf9c4a50e94912e464d3864c5fb44bd4b65dc 0 281 992 949 2024-06-15T09:40:27Z Atmois 13 Update Links wikitext text/x-wiki Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of [[NeXTSTEP]] as an environment compatible with [[OpenStep]] libraries. It has been developed from scratch since 1997 by Alfredo Kojima in C. === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang=""> # apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang=""> $ yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang=""> # emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang=""> # dnf install WindowMaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang=""> $ wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz </syntaxhighlight> <syntaxhighlight lang=""> $ tar xvf WindowMaker-0.96.0.tar.gz </syntaxhighlight> <syntaxhighlight lang=""> $ cd WindowMaker-0.96.0.tar.gz </syntaxhighlight> <syntaxhighlight lang=""> $ ./configure --prefix=/usr </syntaxhighlight> <syntaxhighlight lang=""> $ make </syntaxhighlight> <syntaxhighlight lang=""> # make install </syntaxhighlight> [[Category:Window Managers]] 9865eb132515377591f9d543425d7c4745b88e3f 995 992 2024-06-16T20:08:00Z MymeType 35 Fixed code formatting in the Installation section wikitext text/x-wiki Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of [[NeXTSTEP]] as an environment compatible with [[OpenStep]] libraries. It has been developed from scratch since 1997 by Alfredo Kojima in C. === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> [[Category:Window Managers]] 85c857a8ceb1c23b355cc6681ce01afdd7ae93a2 1007 995 2024-06-17T19:08:40Z MymeType 35 Added Design section, references and SoftwareInfobox template [PLEASE PROPERLY FORMAT SAID TEMPLATE] wikitext text/x-wiki {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home]</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home]</ref> === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> <references /> [[Category:Window Managers]] 4851973d2dabdd5b15c8b6057ac0f9ce96832262 1008 1007 2024-06-17T19:13:15Z MymeType 35 Added Configuration section [DISREGARD PREVIOUS FORMATTING REQUEST, SOFTWAREINFOBOX RENDERING IN VISUAL EDITOR IS BROKEN] wikitext text/x-wiki {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home]</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home]</ref> === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> === Configuration === Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more.<references /> [[Category:Window Managers]] 0f5cf9de644acd3e427d688f88b84249457cf7d1 1009 1008 2024-06-17T19:28:52Z MymeType 35 Added images of Window Maker and WPrefs wikitext text/x-wiki {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home]</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home]</ref> === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more.<references /> [[Category:Window Managers]] 5885518478f9588099de80017d8c54e63d5f392c 0 158 993 785 2024-06-15T09:43:16Z Atmois 13 Update link wikitext text/x-wiki When using [[Linux]], sooner or later, there's a good chance you'll end finding yourself in front of a [[Terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a 'Command'. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include "echo", "mv", "[[cat]]", etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with "sudo" followed with your original command. [[sudo]] Tells your computer to 'do' something as a 'super user' which will allow you to bypass restrictions. It should be important to note that '''sudo is a seperate package''' and won't come pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you need to use something like "su" to log in as root and then run your command as root or install sudo as root. Furthermore, with commands you will likely need to include "options" that specify to the program how you want it to behave. One of the most common options is "--help", which will usually tell program to list all of its options. An example would be as follows cat --help In this case, the 'cat' utility would respond to this command with the following:<blockquote>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines............</blockquote>(Shortened to maintain focus on topic) These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, "--help" is always there and ready. If --help isnt enough, you can always run "[[man]]" before a program similarly to how you would run "[[sudo]]", and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a File to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory]] (Like shown) or you can provide a file from anywhere in the [[Filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt You will notice that I started describing the file location, I used the tilda sign "~". In linux and some other OS, The Tilda is a faster way to describe the users home folder. It is effectively the same thing as typing the full [[Directory Path|directory path]] except that it is much faster. Here is what it would look like to type the whole directory path nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 38b0a94171c8a8b7619e4c063d0cf275c8c0b448 0 263 996 939 2024-06-16T20:13:45Z MymeType 35 Added screenshot of the Hyfetch Pride Month easter egg wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your operating system, software and hardware with the option to color the logos with pride flags. === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run <code>hyfetch</code> in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option.[[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|left|thumb|The Hyfetch Pride Month easter egg.]] <references /> 2e053daafadef226ae7d36ba78b66e5d9f220ea7 2 289 997 2024-06-16T20:41:49Z MymeType 35 Created user page wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os>NixOS</os> <extra>Axolotl Furry</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> <!-- ／l、 （ﾟ､ ｡ ７ ⠀l、ﾞ ~ヽ じしf_, )ノ --> </syntaxhighlight> 20dcdd34bac237308726d26c389494b34135ecca 998 997 2024-06-16T20:42:26Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os>NixOS</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> <!-- ／l、 （ﾟ､ ｡ ７ ⠀l、ﾞ ~ヽ じしf_, )ノ --> </syntaxhighlight> 271d9373af056bc25bf7bfd73aa7c80b3a5faa85 999 998 2024-06-16T20:43:49Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">NixOS</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> <!-- ／l、 （ﾟ､ ｡ ７ ⠀l、ﾞ ~ヽ じしf_, )ノ --> </syntaxhighlight> 7ae144a9794d464a4c7903adea587a2c8c4a2446 1000 999 2024-06-17T07:09:09Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">NixOS</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> <!-- ／l、 （ﾟ､ ｡ ７ ⠀l、ﾞ ~ヽ じしf_, )ノ --> </syntaxhighlight> 99c1aac60a45de2baaa6a39f174b94bd6d0536cc 1001 1000 2024-06-17T07:10:07Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">NixOS</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> <!-- ／l、 （ﾟ､ ｡ ７ ⠀l、ﾞ ~ヽ じしf_, )ノ --> </syntaxhighlight> fa8ac0517a701c8c25a136d684242370a0125055 1006 1001 2024-06-17T17:44:31Z MymeType 35 wikitext text/x-wiki ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">NixOS</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "Window Maker":"https://atl.wiki/index.php/Window_Maker" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ 9e2588f711c2b8c638508e93e41be4cc720ef9d5 0 257 1002 930 2024-06-17T15:45:16Z Amadaluzia 52 added a suggestion to users to follow the Hyprland installation guide wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling window manager that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is quite optimized. === Features === There are tons of feature to this window manager like: * Smooth and animated graphics (such as moving windows, dragging them and in general opening and closing them) * Gradient customization for pretty much everything like window borders including gradient angles. * Nice integration with it's own apps (such as hyprpaper, hyprcursor and hypridle). * Compatibility with most wayland apps and support for <code>xorg-xwayland</code>. * Decent default configuration file auto-generated and has pretty much all important configurations setup for you (like touchpad tap to click, etc). === Installation === This section is bound to change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. If you do need to follow the wiki however, you can continue reading. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release distributions. Most recommended ones include Arch Linux, Gentoo, NixOS, Fedora and openSUSE (Tumbleweed) due to them having the most recent packages and Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to try it on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package if you want to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : to add support for X11. * <code>legacy-renderer</code> : to enable the legacy renderer. * <code>systemd</code> : enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended at all by the Hyprland developers and is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the Ubuntu repo can be outdated. ==== Slackware ==== For Slackware, you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for Void Linux from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables (This will have its own 7 sub-topics) * Binding Keys (bind and other variants) * Binding Special Keys (according to the XF86 specification) * Animations (quick overview) * Monitors (some references to <code>hyprctl</code>) ==== Variables ==== This is the most important part of your configuration file because it is pretty much your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Managers]] 72afe922fd48cbb56d634fe166a55979484698b5 1004 1002 2024-06-17T16:55:02Z Atmois 13 Tidy up some grammer and add in links wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Good integration with it's own apps (Such as hyprpaper, hyprcursor and hypridle) * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) === Installation === This section will change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Managers]] 7de156967046542295c9af12dbc1d3b33611c4ce 1005 1004 2024-06-17T17:01:48Z Atmois 13 Remove uneccesary info wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) === Installation === This section will change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Managers]] fa41ed23a43f9a1f0c5f63ec790bd4e78409b57a 0 236 1003 709 2024-06-17T16:45:00Z Atmois 13 Add links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.18, 2022-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * Desktop Manager - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[Terminal Emulator|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> [[Category:Desktop Environments]] 24c0fb974ad8115bb13d0418bc5362f8a2de5b3e 6 290 1010 2024-06-17T20:10:28Z Amadaluzia 52 This is an example of GNOME 46, taken by UnusedEngine in All Things Linux. wikitext text/x-wiki == Summary == This is an example of GNOME 46, taken by UnusedEngine in All Things Linux. c5dec8a4f6c214296e7d51de72d2e67c6e560f84 0 291 1011 2024-06-17T20:53:42Z Amadaluzia 52 Create the GNOME article wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|200px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 46.2, 2024-05-30 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = The GNOME Project | website = [https://gnome.org/, gnome.org] }} [[File:GNOME 46.png|thumb|A desktop running GNOME 46 in Fedora Workstation 40]] [[GNOME]] is a desktop environment designed to be simple, beautiful, and elegant. It is the main desktop environment of [[Fedora]] and [[Ubuntu]] among others, and is a very popular desktop environment within [[Linux]]/BSD. GNOME began development in 1997 by Miguel de Icaza and Federico Mena, with GNOME 1, the first major release of GNOME, being released in 1999. == GTK == GTK (formerly, GIMP Toolkit) is a widget toolkit that was created for GIMP, but is known as the widget toolkit for GNOME. It uses the GLib data structure and GObject object and type system, to create the GUI behind GNOME and GTK apps such as Epiphany, GIMP and Transmission among others. GTK is one of the most commonly used GUI frameworks, alongside the Qt framework, Cocoa for macOS and Windows Forms for Windows among others. 59521f11e70e1aff553b9dd5f8c73daeb157b0b0 1012 1011 2024-06-17T20:57:24Z Amadaluzia 52 add GNOME to the Desktop Environments category wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|200px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 46.2, 2024-05-30 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = The GNOME Project | website = [https://gnome.org/, gnome.org] }} [[File:GNOME 46.png|thumb|A desktop running GNOME 46 in Fedora Workstation 40]] [[GNOME]] is a desktop environment designed to be simple, beautiful, and elegant. It is the main desktop environment of [[Fedora]] and [[Ubuntu]] among others, and is a very popular desktop environment within [[Linux]]/BSD. GNOME began development in 1997 by Miguel de Icaza and Federico Mena, with GNOME 1, the first major release of GNOME, being released in 1999. == GTK == GTK (formerly, GIMP Toolkit) is a widget toolkit that was created for GIMP, but is known as the widget toolkit for GNOME. It uses the GLib data structure and GObject object and type system, to create the GUI behind GNOME and GTK apps such as Epiphany, GIMP and Transmission among others. GTK is one of the most commonly used GUI frameworks, alongside the Qt framework, Cocoa for macOS and Windows Forms for Windows among others. [[Category:Desktop Environments]] fe3131c9c6e167daf13fa780212959bea6323142 2 289 1013 1006 2024-06-18T07:00:14Z MymeType 35 wikitext text/x-wiki ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">NixOS</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":[ null ], "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ 4f60c2ee1ae6b532ff048d7e0cdae35b15783e00 1024 1013 2024-06-21T08:02:26Z MymeType 35 wikitext text/x-wiki ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">NixOS</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "OpenBSD":"https://atl.wiki/index.php/OpenBSD", "SerenityOS":"https://atl.wiki/index.php/SerenityOS", "Haiku":"https://atl.wiki/index.php/Haiku", "Plan 9":"https://atl.wiki/index.php/Plan_9" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ b5d5af3cb7f03874ea1bc27da07ce1068f7b008b 1030 1024 2024-06-22T14:42:23Z MymeType 35 wikitext text/x-wiki ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">NixOS</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "Void Linux":"https://atl.wiki/index.php/Void_Linux", "SerenityOS":"https://atl.wiki/index.php/SerenityOS" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ b95b5217bb3e3d56a822d0cd3c4964c4729b8bbc 2 3 1014 560 2024-06-18T12:22:18Z Amadaluzia 52 changed to toml wikitext text/x-wiki <syntaxhighlight lang="toml"> [balkenix.about] name = "Åsmund Balkesen" bday = [ 6, 10, 2024 ] # dd/mm/yy os = [ "NixOS", "Windows" ] locales = [ "en_GB", "nb_NO" ] languages = [ "Nix", "Python", "C", "Rust" ] # Most knowledgable to least knowledgable extra = "I'm that \"no true scotsman\" everyone talks about." [balkenix.socials] discord = "@balkenix" youtube = "@balkenix" github = "@balkenix" </syntaxhighlight> 472d9dd14b7d98f871015af848361a3a4852a77d 0 1 1015 994 2024-06-18T19:52:41Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Fastfetch]] * [[Hyfetch]] * [[Main Page]] * [[Neofetch]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 55ede6b334dbad961fbcb528b80c5e3c55e3c6c1 1036 1015 2024-06-23T14:46:41Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == BSD Operating Systems == * [[OpenBSD]] == Desktop Environments == * [[Budgie]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Pages with syntax highlighting errors == * [[Artificial Intelligence on Linux]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package Manager]] * [[TUI]] == Unix Operating Systems == * [[OpenBSD]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Fastfetch]] * [[Hyfetch]] * [[Main Page]] * [[Multi-Booting]] * [[Neofetch]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' b7d99cad2b42fce10033f9414ce7c8018fddd2f6 1038 1036 2024-06-23T14:48:48Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Pages with syntax highlighting errors == * [[Artificial Intelligence on Linux]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Fastfetch]] * [[Hyfetch]] * [[Main Page]] * [[Multi-Booting]] * [[Neofetch]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' ed587f4e19d9569494fd6b5e13ace19f1480669c 1043 1038 2024-06-23T14:59:36Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Pages with syntax highlighting errors == * [[Artificial Intelligence on Linux]] == Programs == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-Booting]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Main Page]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' ab675c94de0ace20f68ed2c879ed74ef76a89b2f 14 292 1016 2024-06-18T21:46:15Z Atmois 13 Setup as redirect wikitext text/x-wiki #REDIRECT [[Desktop Environment]] 47a24ef8a53a0a96f30bd3f6ef3824b61a915e77 14 293 1017 2024-06-18T21:47:26Z Atmois 13 add redirect wikitext text/x-wiki #REDIRECT [[Package Manager]] adf819fee97ba35d21dcfe190e178867a7f3eeb9 14 294 1018 2024-06-18T21:48:15Z Atmois 13 Add redirect wikitext text/x-wiki #REDIRECT [[Key Terms]] 8bd6c2b36726c38e712a9c8dbf427c6543eb40d6 14 296 1020 2024-06-18T21:49:03Z Atmois 13 Add redirect wikitext text/x-wiki #REDIRECT [[Linux Distributions]] f6721c832bacd7daf16c3910dd1b30b95255d241 0 176 1021 792 2024-06-21T03:56:45Z Asiliria 7 Post-hospital comeback wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major differences functionally - most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. <references /> [[Category:Desktop Environments]] 21066173f51944a6c18716b0410790e2d08403f7 1022 1021 2024-06-21T04:06:31Z Asiliria 7 Desktop Effects addition wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major differences functionally - most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] f143cce2eac0a956831a68d78f8072f8d2d97555 1060 1022 2024-07-03T16:03:42Z Cpli 41 add "References" header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major differences functionally - most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> [[Category:Desktop Environments]] 5fa2db1ca7b9d8f8139849b01f83be831e476b0d 1062 1060 2024-07-03T16:06:27Z Cpli 41 revert previous change; duplicating references header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major differences functionally - most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 0de79b8f3fc62cceff31a3adcb9cc0912c979db9 0 250 1023 846 2024-06-21T05:03:39Z Asiliria 7 too eepy to continue wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == Ana/Miniconda Setup == ... (tomorrow's problem) == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a [[Secondary GPU|Secondary/Dual GPU]] (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards on more demanding games. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of Artificial Intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU -''' considering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight> https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): [VERIFY]<syntaxhighlight> conda create --name voicechanger --python=3.10.6 </syntaxhighlight> == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> f3b0c6f32242dab8d45f149de470afd62522ce45 0 297 1025 2024-06-21T21:05:53Z Matty 40 Created multi-booting page, added a short description and use cases, and defined some differences between multi-booting and virtual machines. Also included a section on common uses for multi-booting. wikitext text/x-wiki '''Multi-booting''' is the process of installing and using multiple operating systems on one machine. Multi-booting has many uses, including: * testing different operating systems, * utilizing software that may not work as expected on another OS, * deploying and testing software on different operating systems, and more. === Multi-booting vs. virtual machines === While virtual machines and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine. === '''Common uses for multi-booting''' === ===== Gaming ===== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is kernel-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. 8178eaf9803901a6541fa624fced5d1b3df09924 1026 1025 2024-06-21T21:18:08Z Matty 40 wikitext text/x-wiki '''Multi-booting''' is the process of installing and using multiple operating systems on one machine. Multi-booting has many uses, including: * testing different operating systems, * utilizing software that may not work as expected on another OS, * deploying and testing software on different operating systems, and more. === Multi-booting vs. virtual machines === While virtual machines and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine. === '''Common uses for multi-booting''' === ==== Gaming ==== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is kernel-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. 1a810a504d6871fb47e512e98bb26fadc1077ebb 1032 1026 2024-06-22T23:17:07Z Andre 27 "better known as dualbootering" wikitext text/x-wiki '''Multi-booting''' (better known as ''dual-booting'') is the process of installing and using multiple operating systems on one machine. Multi-booting has many uses, including: * testing different operating systems, * utilizing software that may not work as expected on another OS, * deploying and testing software on different operating systems, and more. === Multi-booting vs. virtual machines === While virtual machines and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine. === '''Common uses for multi-booting''' === ==== Gaming ==== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is kernel-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. 7c76af3acea379ba17f2615b0582fc2e2a8dd7b4 1033 1032 2024-06-23T01:55:11Z Matty 40 format wikitext text/x-wiki '''Multi-booting''' is the process of installing and using multiple operating systems on one machine. Multi-booting has many uses, including: * testing different operating systems, * utilizing software that may not work as expected on another OS, * deploying and testing software on different operating systems, and more. '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems. === Multi-booting vs. virtual machines === While virtual machines and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine. === Common uses for multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is kernel-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. 4cf31eaf679c8a15f03583db0abce3497b8d70a4 1041 1033 2024-06-23T14:55:15Z Electron271 3 wikitext text/x-wiki '''Multi-booting''' is the process of installing and using multiple operating systems on one machine. Multi-booting has many uses, including: * testing different operating systems, * utilizing software that may not work as expected on another OS, * deploying and testing software on different operating systems, and more. '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems. === Multi-booting vs. virtual machines === While virtual machines and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine. === Common uses for multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is kernel-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. [[Category:Terminology]] c616ef763f1fe5e8cefb0abc628136613540726e 1044 1041 2024-06-23T23:51:13Z Matty 40 Matty moved page [[Multi-Booting]] to [[Multi-booting]]: Misspelled title: Removing unnecessary capitalization for a cleaner appearance wikitext text/x-wiki '''Multi-booting''' is the process of installing and using multiple operating systems on one machine. Multi-booting has many uses, including: * testing different operating systems, * utilizing software that may not work as expected on another OS, * deploying and testing software on different operating systems, and more. '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems. === Multi-booting vs. virtual machines === While virtual machines and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine. === Common uses for multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is kernel-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. [[Category:Terminology]] c616ef763f1fe5e8cefb0abc628136613540726e 1046 1044 2024-06-23T23:57:40Z Matty 40 Linked to pages that need to be created and clarified some information about MB vs VM. wikitext text/x-wiki === Terminology === '''Multi-booting''' is the process of installing and using multiple [[Operating system|operating systems]] on one machine. Multi-booting has many uses, including: * testing different operating systems, * utilizing software that may not work as expected on another OS, * deploying and testing software on different operating systems, and more. '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. virtual machines === While virtual machines and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common uses for multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is kernel-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. [[Category:Terminology]] fe75a5b91422c32623caeaeb3974f5b07c813e83 1047 1046 2024-06-24T00:20:05Z Matty 40 Edited link wikitext text/x-wiki === Terminology === '''Multi-booting''' is the process of installing and using multiple [[Operating system|operating systems]] on one machine. Multi-booting has many uses, including: * testing different operating systems, * utilizing software that may not work as expected on another OS, * deploying and testing software on different operating systems, and more. '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. virtual machines === While [[Virtual machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common uses for multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is kernel-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. [[Category:Terminology]] c2cbbfed8f2ef6bf7e44b1df8464f5dfaa07c454 6 298 1027 2024-06-22T13:25:57Z MymeType 35 By The OpenBSD Project - http://www.openbsd.org/art4.html, BSD, https://commons.wikimedia.org/w/index.php?curid=134813056 wikitext text/x-wiki == Summary == By The OpenBSD Project - http://www.openbsd.org/art4.html, BSD, https://commons.wikimedia.org/w/index.php?curid=134813056 187a518b504c3cd11cccfa387e476dbef43862f4 0 299 1028 2024-06-22T14:35:33Z MymeType 35 Created OpenBSD page wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[Awesome]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix operating system, based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995.<ref name=":0">[[wikipedia:OpenBSD#|OpenBSD - Wikipedia]]</ref> The first version of OpenBSD (1.2) released on July 1996.<ref name=":0" /> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the SSH protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD DistroWatch.com: OpenBSD]</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref name=":0" /> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike Linux, which provides just the kernel and drivers. <references /> [[Category:Unix Operating Systems]] [[Category:BSD Operating Systems]] 0cbabf067246242466b245803fbef941f611ec1f 1029 1028 2024-06-22T14:36:49Z MymeType 35 wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[Awesome]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix operating system, based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995.<ref name=":0">[[wikipedia:OpenBSD#|OpenBSD - Wikipedia]]</ref> The first version of OpenBSD (1.2) released on July 1996.<ref name=":0" /> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the SSH protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD DistroWatch.com: OpenBSD]</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref name=":0" /> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Unix Operating Systems]] [[Category:BSD Operating Systems]] 530a0559bb3ff1d0efca8790a9ee2a15f122f0ad 1031 1029 2024-06-22T14:52:47Z Amadaluzia 52 made KDE link to something wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[Awesome]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix operating system, based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995.<ref name=":0">[[wikipedia:OpenBSD#|OpenBSD - Wikipedia]]</ref> The first version of OpenBSD (1.2) released on July 1996.<ref name=":0" /> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the SSH protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD DistroWatch.com: OpenBSD]</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref name=":0" /> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Unix Operating Systems]] [[Category:BSD Operating Systems]] 26fb097d4f0454ea71128a6890857b2f538ecc8d 1037 1031 2024-06-23T14:48:17Z Electron271 3 Chore: Update categories wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[Awesome]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix operating system, based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995.<ref name=":0">[[wikipedia:OpenBSD#|OpenBSD - Wikipedia]]</ref> The first version of OpenBSD (1.2) released on July 1996.<ref name=":0" /> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the SSH protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD DistroWatch.com: OpenBSD]</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref name=":0" /> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] a6de44bee15f5f772da1df83c80e888ec02146b1 0 269 1034 951 2024-06-23T02:19:06Z Matty 40 Hierarchical headings. Reformatted code blocks. Rephrased information and removed some duplication. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], budgie provides an easy to use interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] === Features === '''Budgie Desktop View''' is a software component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. === Installation === Budgie is available on almost all [[Linux Distributions|Linux distributions]]. ==== Arch-based systems ==== To install the '''budgie''' package group, which includes first-party applications such as a screensaver, execute <code>sudo pacman -S budgie</code>. Alternatively, <code>sudo pacman -S budgie-desktop</code> will install the standalone desktop. Recommended optional packages include the Arc GTK theme, the Papirus icon theme, and the Network Manager applet. Executing <code>sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet</code> will install them. ==== Fedora Linux ==== [[Fedora]] has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. ==== Ubuntu ==== There is a [https://ubuntubudgie.org/ community ISO] that contains [[Ubuntu]] with Budgie Desktop instead of GNOME. ==== Void Linux ==== <code>sudo xbps-install budgie-desktop</code> ==== OpenSUSE ==== Budgie can be selected during the OpenSUSE installation or installed afterward using <code>sudo zypper install budgie-desktop</code>. [[Category:Desktop Environments]] 4ed711cbdc5cc6d86230b27c4b5ebc0f8a1f9231 6 300 1035 2024-06-23T11:56:35Z Delta 39 Void Linux's logo. wikitext text/x-wiki == Summary == Void Linux's logo. 6cb28045394927ef477854714b1a9a2204c6c366 0 268 1039 880 2024-06-23T14:49:53Z Electron271 3 Chore: Update categories wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch github.com/fastfetch-cli/fastfetch] }} Fastfetch is a [[neofetch]]-like tool for fetching information about your operating system, software and hardware. It is written mainly in [[C]], with a focus on performance. [[Category:Programs]] 782245a76159fe6c00ce04221e5118d4fe47dea2 1053 1039 2024-06-24T21:44:10Z Atmois 13 add references wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch github.com/fastfetch-cli/fastfetch] }} Fastfetch is a [[neofetch]]-like tool for fetching information about your operating system, software and hardware. It is written mainly in [[C]], with a focus on performance.<ref>https://github.com/fastfetch-cli/fastfetch</ref> <references /> [[Category:Programs]] 7813eb132908489da8d2a7e6f112d7dcaaf3d919 0 263 1040 996 2024-06-23T14:51:14Z Electron271 3 Chore: Update categories wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your operating system, software and hardware with the option to color the logos with pride flags. === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option.[[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|left|thumb|The Hyfetch Pride Month easter egg.]] <references /> [[Category:Programs]] d5f2e275bfc1b59d82b38ca1d4b54434d8816926 1054 1040 2024-06-24T21:46:21Z Atmois 13 add references wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your operating system, software and hardware with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch</ref> === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|left|thumb|The Hyfetch Pride Month easter egg.]]If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. <references /> [[Category:Programs]] 84bec83acb46c88f5b4ab5d84c2cfbe88b24860c 0 261 1042 874 2024-06-23T14:59:00Z Electron271 3 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]] (Neofetch-like utility written in [[C]]) and [[hyfetch]] (Fork of neofetch with pride flags). <references /> [[Category:Programs]] 07a9a0207846545d588921842ee1039aefcac0ec 0 301 1045 2024-06-23T23:51:13Z Matty 40 Matty moved page [[Multi-Booting]] to [[Multi-booting]]: Misspelled title: Removing unnecessary capitalization for a cleaner appearance wikitext text/x-wiki #REDIRECT [[Multi-booting]] 863d11e9594a2c3b97086140e15812164f4855d4 6 302 1048 2024-06-24T09:57:05Z MymeType 35 By Katalin Kult - SerenityOS artwork repository, CC BY 4.0, https://commons.wikimedia.org/w/index.php?curid=116408796 wikitext text/x-wiki == Summary == By Katalin Kult - SerenityOS artwork repository, CC BY 4.0, https://commons.wikimedia.org/w/index.php?curid=116408796 6cd6188abcb2821c8f6c3185c6322e3d15849359 6 303 1049 2024-06-24T10:05:13Z MymeType 35 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 304 1050 2024-06-24T11:01:43Z MymeType 35 Created SerenityOS page wikitext text/x-wiki {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a Unix-like operating system completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS]</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive kernel, and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[Mac OS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to compile software from a ports collection for use with the operating system. [[Category:Misc Operating Systems]] b79c8b443ec6c6e65963cc3de7482fd5f72bb924 1051 1050 2024-06-24T11:07:26Z MymeType 35 wikitext text/x-wiki {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a Unix-like operating system completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS]</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive kernel, and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[Mac OS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to compile software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub]</ref> [[Category:Misc Operating Systems]] 60ccb6c56e643296e07736ba62b66303068b8d25 2 305 1052 2024-06-24T21:28:53Z Atmois 13 Create sandbox to test template wikitext text/x-wiki sandbox page c8b7fb5164d388b53173547efa3d5fe5d3374bd7 0 306 1055 2024-06-30T10:54:03Z Atmois 13 Create window manager page wikitext text/x-wiki A window manager is a piece of system software within [[Xorg]] which controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. They control serveral features of the GUI such as the borders, title bar, size and the ability to resize the windows. They can be provided as a part of [[Desktop Environment]] (Such as [[Kwin]] in [[KDE Plasma]]) with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]] or they can be standalone (Such as [[i3]]) to give the user the ability to create a more lightweight and customised environment at the cost of requiring the user to add the desired software. There are 3 main types of window managers, [[Window Manager#Stacking (Floating) Window Managers|#Stacking]] (Or floating) which provides the traditional desktop expereince such as [[Xfwm]] in [[Xfce]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[AwesomeWM]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[Dwm]]. Whilst on X the functionality of the window manager and [[Display Server]] are seperate on [[Wayland]] there are both combined into the [[Compositor|Wayland Compositor]]. ==== Stacking (Floating) Window Managers ==== ==== Tiling Window Managers ==== ==== Dynamic Window Managers ==== 07fe3f752c51fb336df97d0760d91ff7e36f1937 1056 1055 2024-06-30T19:55:06Z Atmois 13 Fix spelling and grammer wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. They control serveral features of the GUI, such as the borders, title bar, size and the ability to resize the windows. They can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Or they can be standalone (such as [[i3]]) to give the user the ability to create a more lightweight and customised environment at the cost of requiring the user to add the desired software. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[AwesomeWM]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[Dwm]].  ==== Stacking/Floating Window Managers ==== ==== Tiling Window Managers ==== ==== Dynamic Window Managers ==== dae500124136f9540dced3c5a5768aeb029749dd 1057 1056 2024-07-01T13:55:35Z Matty 40 Added information, edited grammar, etc. wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be standalone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[AwesomeWM]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[Dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some popular examples include: * [[awesome]] * [[bspwm]] * [[dwm]] * [[i3]] * [[qtile]] * [[xmonad]] ==== Dynamic Window Managers ==== 7b969a2169611d75d50351f4255f3f62a7cd77c8 2 307 1061 2024-07-03T16:04:46Z Cpli 41 elaborate on user's existence wikitext text/x-wiki ewwo there i exist<ref>https://chaos.social/@cpli</ref><ref>https://sr.ht/~cpli/</ref> == References == d1ef44bc0f54ed0f530f853481da5a375345b11d 0 299 1063 1037 2024-07-03T22:18:20Z Atmois 13 add links and update 'unix' to 'unix-like' wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[Awesome]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995.<ref name=":0">[[wikipedia:OpenBSD#|OpenBSD - Wikipedia]]</ref> The first version of OpenBSD (1.2) released on July 1996.<ref name=":0" /> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix-like operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD DistroWatch.com: OpenBSD]</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref name=":0" /> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] 4173eb947bf1ff61615a3d4d004986a254a217e7 1070 1063 2024-07-04T14:31:05Z MymeType 35 Reverted "Unix-like" back to "Unix" wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[Awesome]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995.<ref name=":0">[[wikipedia:OpenBSD#|OpenBSD - Wikipedia]]</ref> The first version of OpenBSD (1.2) released on July 1996.<ref name=":0" /> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD DistroWatch.com: OpenBSD]</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref name=":0" /> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] f6e8a2f38d0640ca7a63e6821103914aba9914c2 1073 1070 2024-07-04T18:12:05Z Atmois 13 Update link wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995.<ref name=":0">[[wikipedia:OpenBSD#|OpenBSD - Wikipedia]]</ref> The first version of OpenBSD (1.2) released on July 1996.<ref name=":0" /> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD DistroWatch.com: OpenBSD]</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref name=":0" /> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] 519b4db25e170998c74fdef938adfc53b48f48a9 0 2 1064 984 2024-07-04T05:11:37Z Cpli 41 mention minimal installation and rewrite pacman section into makepkg explainer wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from CRUX Linux being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4. 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>https://pacman.archlinux.page/makepkg.8.html</ref><ref>https://pacman.archlinux.page/PKGBUILD.5.html</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] 22f28645a9686a6b315be792933c5af7e00aba68 1067 1064 2024-07-04T05:52:29Z Cpli 41 link to crux wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4. 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>https://pacman.archlinux.page/makepkg.8.html</ref><ref>https://pacman.archlinux.page/PKGBUILD.5.html</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> [[Category:Linux Distributions]] dd5f9e2dfa9ddb2a4f750e1bef8f1729267904d6 0 203 1065 790 2024-07-04T05:21:19Z Cpli 41 remove trailing punctuation wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]][https://www.gentoo.org/ Gentoo Linux] is a source-based [[Linux Distributions|Linux distribution]], aimed around user customization. This distribution, in addition to having the systemd init system, also provides its own init system known as OpenRC. Unlike other Linux distributions, everything you install is compiled on the local system. As such, users can use compile flags, known as 'Use Flags,' to help them fit their system to their use case.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Gentoo has support for a large variety of hardware and has extremely minimal requirements, which makes it great for most devices. === Portage === [[Portage]] is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. '''Emerge''' is a front-end for Portage and is used to manage the entire system. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 3d158fdab4c9366e0ad3b4bcbc3a2d54b767ab1c 0 176 1066 1062 2024-07-04T05:38:40Z Cpli 41 adjective adjective wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 762d94175f8a4ea02a2f0dc784b2b0f6f883ad18 2 289 1068 1030 2024-07-04T14:27:09Z MymeType 35 Updated todo list wikitext text/x-wiki ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">NixOS</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "Void Linux":"https://atl.wiki/index.php/Void_Linux", "Fedora Atomic":"https://atl.wiki/index.php/Fedora_Atomic", "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ 0d8d4404797cc8e2b0388b321788b5fc00b6bdc5 1069 1068 2024-07-04T14:28:09Z MymeType 35 wikitext text/x-wiki ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">Fedora Silverblue, Bazzite</os> <extra>Furry (Axolotl)</extra> </about> <contact> <twitter>@MymeType</twitter> <discord>@mymetype</discord> <tumblr>@mymetype</tumblr> </contact> </profile> </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "Void Linux":"https://atl.wiki/index.php/Void_Linux", "Fedora Atomic":"https://atl.wiki/index.php/Fedora_Atomic", "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> ᓬ(ᵔ⤙ᵔ๑)ᕒ d848cdb137ed7ecde8ac89acc3e1b55d2672fc1d 1096 1069 2024-08-03T19:28:46Z MymeType 35 wikitext text/x-wiki ᓬ(ᵔ⤙ᵔ๑)ᕒ <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">Gentoo</os> <extra>Robot</extra> <socials>https://linktr.ee/mymetype</socials> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "Void Linux":"https://atl.wiki/index.php/Void_Linux", "Fedora Atomic":"https://atl.wiki/index.php/Fedora_Atomic", "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 5841f78751d0119e1120128193c1c6e5b2692118 1097 1096 2024-08-03T19:29:05Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Pansexual</sexuality> <os type="Linux">Gentoo</os> <extra>Robot</extra> <socials>https://linktr.ee/mymetype</socials> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "Void Linux":"https://atl.wiki/index.php/Void_Linux", "Fedora Atomic":"https://atl.wiki/index.php/Fedora_Atomic", "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 04ff303d6efa778868a800fcd2a7760d3db19c10 6 308 1071 2024-07-04T17:02:19Z Exhq 42 using sudo to sync the package databases in pacman wikitext text/x-wiki == Summary == using sudo to sync the package databases in pacman 28bc8fa07f477d27a0e1cf0bed35e57d15a44de9 0 306 1072 1057 2024-07-04T18:11:37Z Atmois 13 Update link wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be standalone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[AwesomeWM]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[Dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some popular examples include: * [[AwesomeWM|awesome]] * [[bspwm]] * [[dwm]] * [[i3]] * [[qtile]] * [[xmonad]] ==== Dynamic Window Managers ==== 3841073cf95a2eb35471646fd81784cb18d85370 1105 1072 2024-08-08T18:44:55Z Matty 40 moved category to Key Terms wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be standalone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[AwesomeWM]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[Dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some popular examples include: * [[AwesomeWM|awesome]] * [[bspwm]] * [[dwm]] * [[i3]] * [[qtile]] * [[xmonad]] ==== Dynamic Window Managers ==== [[Category:Key Terms]] 1e0ef3d4d438c032fa66e5dfbb1092e32cd06ee2 0 309 1074 2024-07-04T20:56:51Z Exhq 42 sudo - initial wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png|thumb]] | caption = Sudo used on [[pacman]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.15p5, 2023-12-30 | languages = [[c]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} sudo (substitute user do) is a [[cli]] tool used to run [[commands]] as other users (most likely [[root]]). the system administrator can further edit the permissions of which user/group can use sudo and what commands can they run it on through the <code>/etc/sudoers</code> file == Usage == The following are several common usecases for sudo. ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser'' {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} TODO: explain the usage of sudoedit and /etc/sudoers 19c369815a084129be90c44e728b6d420aaad0ac 1075 1074 2024-07-06T05:49:12Z Cpli 41 capitalization; some rewording wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png|thumb]] | caption = Sudo used on [[pacman]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.15p5, 2023-12-30 | languages = [[c]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} The cli tool <code>sudo</code> is a command line tool used to run commands as another user (most likely [[root]]). Its name is shorthand for "substitute user and do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file to specify which users or groups can execute specific commands. == Usage == The following are several common usecases for sudo. ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser'' {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} TODO: explain the usage of sudoedit and /etc/sudoers 5be7af229d8bd6e586e51afdc874330f11ffba11 1076 1075 2024-07-06T05:50:20Z Cpli 41 eliminate repetition wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png|thumb]] | caption = Sudo used on [[pacman]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.15p5, 2023-12-30 | languages = [[c]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]). Its name is shorthand for "substitute user and do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file to specify which users or groups can execute specific commands. == Usage == The following are several common usecases for sudo. ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser'' {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} TODO: explain the usage of sudoedit and /etc/sudoers 2d4b72d8b24694260eeccbd585c0c078d1ce3ef2 0 233 1077 756 2024-07-06T12:48:21Z MymeType 35 Added Xfce to Default Desktops section in Infobox wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. [[Category:Linux Distributions]] e28aeec0509abd6efdb39200be44b7f1d9a54c85 0 310 1078 2024-07-08T19:15:33Z Asiliria 7 Alpine Linux page creation - Category Insert wikitext text/x-wiki [[Category:Linux Distributions]] 07820c0c99d653d7e5bbe452f83fec927fb7f0dc 1080 1078 2024-07-08T19:35:00Z test wikitext text/x-wiki [[Category:Linux Distributions]] Test edit [remove this] c49830829d3e4379f11395589f9e278fddf01e5b 1081 1080 2024-07-08T19:36:46Z Asiliria 7 Alpine Linux please work wikitext text/x-wiki [[Category:Linux Distributions]] Alpine Linux, according to their main site, is a general purpose Linux distribution that aims to be "small," "simple," and "secure." It achieves this by using only the most basic and necessary binaries as well as tools to get started, as well as splitting binaries compiled as Position Independent Executables (PIEs) in order to ensure the installed system is centered around one or a few simple tasks without any unnecessary components. Instead of systemd, it uses OpenRC, and instead of glibc, it uses musl libc in pursuit of greater efficiency. 39125292c8835908081006116e4f378fb29585f5 1100 1081 2024-08-08T14:42:09Z Asiliria 7 Make more succinct wikitext text/x-wiki [[Category:Linux Distributions]] Alpine Linux, according to their main site, is a general purpose Linux distribution that aims to be "small," "simple," and "secure." It achieves this by using only the most basic and necessary binaries as well as tools to get started, compiled as Position Independent Executables (PIEs) in order to ensure the installed system is centered around one or a few simple tasks without any unnecessary components. Instead of systemd, it uses OpenRC, and instead of glibc, it uses musl libc in pursuit of greater efficiency. e3d9dca91cba91dc0f7130e6554e03933c656908 1110 1100 2024-10-03T14:47:57Z Seo 46 added some info on alpine's package manager, usage, and scripts to setup the system. wikitext text/x-wiki [[Category:Linux Distributions]] Alpine Linux, according to their main site, is a general purpose Linux distribution that aims to be "small," "simple," and "secure." It achieves this by using only the most basic and necessary binaries as well as tools to get started, compiled as Position Independent Executables (PIEs) in order to ensure the installed system is centered around one or a few simple tasks without any unnecessary components. Instead of systemd, it uses OpenRC, and instead of glibc, it uses musl libc in pursuit of greater efficiency. Alpine Linux is most commonly used in embedded systems and servers due to its ease of deployment and manageability. Its main package manager is 'apk', short for 'Alpine Package Keeper' (not to be confused with Android APKs.) Alpine's repositories are very small compared to most user-oriented distributions nowadays, hence it isn't used much on desktop machines. Alpine does not come with a graphical environment, editor or even a tool to execute as superuser out of the box, however it provides a number of scripts for setting up numerous things, among which are: 1) setup-desktop: Friendly TUI script to quickly set up a desktop environment and necessary tools to start working. 2) setup-xorg-base: Invokes 'apt' to download a number of Xorg-related packages. Note that it doesn't allow you to start working with Xorg right away, you still need to fetch other important packages and setup other things. 2d7180db0f2e821aacfc489f1dac7aebb48f9bdf 2 311 1082 2024-07-10T08:47:18Z Matty 40 migrated to-do from Discord to Wiki because I'm a copycat wikitext text/x-wiki Former nuclear submarine mechanic, life-long tech enthusiast. === To-Do: === * Virtual machine page f09e75f75791af551cbd3698d170b28aac8927eb 1083 1082 2024-07-10T08:48:05Z Matty 40 /* To-Do: */ wikitext text/x-wiki Former nuclear submarine mechanic, life-long tech enthusiast. === To-Do: === * Virtual machine page * Cinnamon desktop environment page 28c97b6f36375d9113dcd08721508e2f5880bc30 1102 1083 2024-08-08T18:32:20Z Matty 40 edited personal to-do wikitext text/x-wiki Former nuclear submarine mechanic, life-long tech enthusiast. === To-Do: === * Virtual machine page * <s>Cinnamon desktop environment page</s> 2d4c9645741b09c228314031de9a806c5e4b61a9 1 312 1084 2024-07-10T09:00:21Z Electron271 3 /* optional repos */ new section wikitext text/x-wiki == optional repos == include staging repos in the list (iirc there are more too) [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 09:00, 10 July 2024 (UTC) 389b57508702baa4456daec9b665a3ff883a0a8f 0 313 1085 2024-07-10T09:15:44Z Matty 40 Created Cinnamon page wikitext text/x-wiki Cinnamon is a desktop environment maintained by the Linux Mint team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets — can be organized freely. Additional applets can be downloaded from the internet. === Spices === Spices are cinnamon's names for add-on applets, desklets, themes, widgets, and more. They can be found at the Cinnamon Spices repository website. f86b03a40baa667497b02576c3d2022b93feaa8d 1087 1085 2024-07-10T09:24:06Z Matty 40 wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] Cinnamon is a desktop environment maintained by the Linux Mint team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet. === Spices === Spices are cinnamon's names for add-on applets, desklets, themes, widgets, and more. They can be found at the Cinnamon Spices repository website. 9a7058692e88e5c47749aaf35114cda66e0f490b 1093 1087 2024-08-01T23:47:01Z Matty 40 wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] == Overview == Cinnamon is a desktop environment maintained by the Linux Mint team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === Spices are cinnamon's names for add-on applets, desklets, themes, widgets, and more. They can be found at the Cinnamon Spices repository website. b1f70fb1b89fa485e647539d141c6d0419788e60 1094 1093 2024-08-01T23:55:03Z Matty 40 moved to Desktop Environments category wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] == Overview == Cinnamon is a desktop environment maintained by the Linux Mint team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === Spices are cinnamon's names for add-on applets, desklets, themes, widgets, and more. They can be found at the Cinnamon Spices repository website. [[Category:Desktop Environment]] 5e469983845c14766ecd152044a75df7773b9f6e 1095 1094 2024-08-02T00:02:23Z Matty 40 wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] == Overview == Cinnamon is a desktop environment maintained by the Linux Mint team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === A "Spice" is Cinnamon's name for an add-on applet, desklet, theme, widget, and more. They can be found at the Cinnamon Spices repository website. [[Category:Desktop Environment]] 1f8d1b550d3d1c2641d7bf764ddb63fcc673f787 1099 1095 2024-08-08T14:40:58Z Asiliria 7 wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] == Overview == Cinnamon is a desktop environment maintained by the Linux Mint team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === A "Spice" is Cinnamon's name for an add-on applet, desklet, theme, widget, and more. They can be found at the Cinnamon Spices repository website. [[Category:Desktop Environments]] 20237e3d5b746458efd9d397220dc8c81db48b5d 1104 1099 2024-08-08T18:42:03Z Matty 40 Added links to external sources wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] == Overview == [https://github.com/linuxmint/cinnamon Cinnamon] is a desktop environment maintained by the [https://www.linuxmint.com/ Linux Mint] team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === A "Spice" is Cinnamon's name for an add-on applet, desklet, theme, widget, and more. They can be found at the [https://cinnamon-spices.linuxmint.com/ Cinnamon Spices repository website]. [[Category:Desktop Environments]] f3fc0e248fcd10988ea8dbf5bca35bec4cb3ce2e 6 314 1086 2024-07-10T09:23:09Z Matty 40 wikitext text/x-wiki Cinnamon on Linux Mint 21.3 62e1259cfccf117da199011f77cf10240385569d 0 250 1088 1023 2024-07-17T04:10:05Z Asiliria 7 Syntax highlighting what? - Refined Setup details wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == Ana/Miniconda Setup == ... (tomorrow's problem) == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a [[Secondary GPU|Secondary/Dual GPU]] (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards on more demanding games. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of Artificial Intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU -''' considering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> 6b05255c844cf057b80787f353badb13ec1db45e 0 297 1089 1047 2024-07-22T10:52:29Z Atmois 13 add links and fix grammer wikitext text/x-wiki === Terminology === '''Multi-booting''' is the process of installing and using multiple [[Operating system|operating systems]] on one machine. Multi-booting has many uses, including: * Testing different operating systems * Utilizing software that may not work as expected on another OS * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. virtual machines === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common uses for multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on [[Linux]]. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. [[Category:Terminology]] 543274c8283441277a7333fdfb83a857e36641a0 1091 1089 2024-07-22T11:40:30Z Atmois 13 Write a generic guide on multibooting (Will clean up and make more readable with images) wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating system|operating systems (OS)]] on one machine. Multi-booting has many uses, including: * Testing different operating systems * Utilizing software that may not work as expected on another OS * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on Linux, some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on [[Linux]]. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == How to Multi-boot == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen distribution search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitons"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a Debian or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! [[Category:Terminology]] 71797a03375783169c3d364a54c46aedcd2390d8 1092 1091 2024-07-22T11:42:01Z Atmois 13 Update Links wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating system|operating systems (OS)]] on one machine. Multi-booting has many uses, including: * Testing different operating systems * Utilizing software that may not work as expected on another OS * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == How to Multi-boot == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen distribution search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitons"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! [[Category:Terminology]] 445b84d5ecfd0ce6524dddc79714e647eebd4e50 0 304 1090 1051 2024-07-22T10:54:11Z Atmois 13 add + update links wikitext text/x-wiki {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a [[Unix-like]] [[Operating System|operating system]] completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS]</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive [[kernel]], and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[Mac OS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[Virtual Machine|virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to [[Compiling|compile]] software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub]</ref> [[Category:Misc Operating Systems]] 141808f77610e14f64eedefb0ed39611af5ddfaf 0 1 1098 1043 2024-08-07T15:30:11Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environment == * [[Cinnamon]] == Desktop Environments == * [[Budgie]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Programs == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Sudo]] * [[Window Manager]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 496886a043bb1d55971fd774adbab72351adfe3d 1103 1098 2024-08-08T18:38:37Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Programs == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Sudo]] * [[Window Manager]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 1d7cb83bb141a35f1cc52937263e745480bcee35 1113 1103 2024-10-03T17:14:12Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Key Terms == * [[Window Manager]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Programs == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Sudo]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' eeaa2d1802b911765651ad78ac4ebe80e71d80d3 2 192 1101 405 2024-08-08T17:55:39Z Atmois 13 Add external link wikitext text/x-wiki Local tech nerd, who listens to ''a lot'' of music. https://atmois.com 3ccf5416c73d72e6c9ebcda5e00c324bf3096338 6 315 1107 2024-08-09T16:46:34Z Amadaluzia 52 made by @eepy-goddess on discord wikitext text/x-wiki == Summary == made by @eepy-goddess on discord 91af5dd80d0691f5c1248c28e25a9009ce7d9ccb 2 316 1109 2024-10-03T14:40:50Z Seo 46 added description wikitext text/x-wiki [https://fs2f.github.io] Personal page. ----Hi there! e6344337cccb80b86da255f305c47a6b40883192 0 317 1111 2024-10-03T15:31:17Z Seo 46 added a small overview + distribution info box. wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[xbps-*]] | defaultdesktops = [[Xfce]] (live image) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void GNU/Linux''' is a rolling-release Linux distribution built from source. Void Linux is most commonly used on desktop systems for its lightweight-ness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, amongst other things, It also allows you to choose between a glibc image and a musl image. Like most minimalistic distributions, Void does not come with a graphical environment out of the box. However, it can be installed by the user later on. d8fbeef097d660bce2dc82481423a298ff1b75b4 1112 1111 2024-10-03T16:06:55Z Seo 46 added a category tag wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[xbps-*]] | defaultdesktops = [[Xfce]] (live image) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void GNU/Linux''' is a rolling-release Linux distribution built from source. Void Linux is most commonly used on desktop systems for its lightweight-ness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, amongst other things, It also allows you to choose between a glibc image and a musl image. Like most minimalistic distributions, Void does not come with a graphical environment out of the box. However, it can be installed by the user later on. [[Category:Linux Distributions]] c67669ef9136b9b2bdb97dfa73eed8b70844d4f2 0 281 1114 1009 2024-10-04T10:35:12Z Seo 46 added command to install wmaker on void wikitext text/x-wiki {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home]</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home]</ref> === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight> On [[Void Linux]]: <syntaxhighlight lang="bash"> sudo xbps-install windowmaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more.<references /> [[Category:Window Managers]] 271637e39198e4693548fe23b8c7d8f0c9b78a0f 0 318 1115 2024-10-04T10:46:26Z Seo 46 added a small overview wikitext text/x-wiki The bootloader is a program that's responsible for booting the system. Most of the time, it will have a menu to choose an option from, making it a boot manager. A bootloader is installed onto the boot partition of the computer during a distribution's installation process. Most of the times, boot partitions may need from 200-600MB of space to work properly. Most bootloaders also have theming capabilities, take, for example, the previously mentioned GRUB. [[Category:Key Terms]] 7fc38e0e272d04660a27f9d08203b31092c0c104 2 289 1116 1097 2024-10-13T20:10:43Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>13/09/2008 (dd/mm/yyyy)</birthdate> <pronouns>he/him</pronouns> <sexuality>Bisexual</sexuality> <os type="Linux">Gentoo</os> <extra>Robot/Furry (Axolotl)</extra> <socials>https://linktr.ee/mymetype</socials> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "Fedora Atomic":"https://atl.wiki/index.php/Fedora_Atomic", "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> e4ca29e0c5cc7456fe205aee3bed7773a29b87a9 1117 1116 2024-10-13T20:11:36Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <sexuality>Bisexual</sexuality> <os type="Linux">Gentoo</os> <extra>Robot/Furry (Axolotl)</extra> <socials>https://linktr.ee/mymetype</socials> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "Fedora Atomic":"https://atl.wiki/index.php/Fedora_Atomic", "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 828b7b6fbaa91ce48a3d5f16de29e9cb11e90e73 1118 1117 2024-10-13T20:12:22Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <sexuality>Bisexual</sexuality> <os>Gentoo/Windows</os> <extra>Robot/Furry (Axolotl)</extra> <socials>https://linktr.ee/mymetype</socials> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "Fedora Atomic":"https://atl.wiki/index.php/Fedora_Atomic", "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 6fb20646874a9eb81c92adf6a90f5591cc51e61b 1119 1118 2024-10-13T20:16:24Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <sexuality>Bisexual</sexuality> <os>Gentoo/Windows</os> <extra>Robot/Furry (Axolotl)</extra> <socials>https://linktr.ee/mymetype</socials> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "FreeBSD":"https://atl.wiki/index.php/FreeBSD", "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 729afb972de6cb5d77fb29a1bb014c32ae67abaf 0 306 1120 1105 2024-10-24T16:05:37Z Imnotpolar 112 added info on Dynamic WMs, and organized a few of the others so they were in alphabetical order wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be standalone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some popular examples include: * [[bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[AwesomeWM|awesome]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Key Terms]] b9e584fe4233db71f27e8d70f76339c5fa99d0f8 1165 1120 2024-10-28T12:48:49Z Name correction wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be standalone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some popular examples include: * [[bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Key Terms]] 07cb0ec91c820a7a891510478ce44a7c97ec3623 0 319 1121 2024-10-24T19:08:56Z Imnotpolar 112 Created page with "'''Ricing''' is the process of customizing and fine-tuning your [[Desktop environment|desktop environment]] or [[Window Manager|window manager]] to achieve a highly personalized look and feel. The term originated from the concept of making aesthetic and functional improvements to a system's interface, similar to the act of modifying cars. Generally '''ricing''' focuses on visual customization, although, performance tweaks can be a part of the process." wikitext text/x-wiki '''Ricing''' is the process of customizing and fine-tuning your [[Desktop environment|desktop environment]] or [[Window Manager|window manager]] to achieve a highly personalized look and feel. The term originated from the concept of making aesthetic and functional improvements to a system's interface, similar to the act of modifying cars. Generally '''ricing''' focuses on visual customization, although, performance tweaks can be a part of the process. 93e3ef4b1aade44afc50a84cd2d409ad393d944c 2 3 1122 1014 2024-10-25T11:57:14Z Amadaluzia 52 identity change wikitext text/x-wiki <syntaxhighlight lang="toml"> [amadaluzia.about] name = "Artur Manuel" bday = [ 4, 9, 2007 ] # dd/mm/yy os = [ "NixOS", "Debian", "Windows" ] locales = [ "en_GB", "pt_PT" ] languages = [ "Nix", "Python", "Go", "C", "Rust" ] # Most knowledgable to least knowledgable extra = "Caught the portuguese virus on the first second of me being born :pensive:" [amadaluzia.socials] discord = "@amadaluzia" youtube = "@amadaluzia" github = "@amadalusia" </syntaxhighlight> 9e3e08a33335e9cc7c3def13e7ddab1fcda78c4a 1123 1122 2024-10-25T12:09:35Z Tess moved page [[User:Balkenix]] to [[User:Amadaluzia]]: Automatically moved page while merging the account "Balkenix" to "[[User:Amadaluzia|Amadaluzia]]" wikitext text/x-wiki <syntaxhighlight lang="toml"> [amadaluzia.about] name = "Artur Manuel" bday = [ 4, 9, 2007 ] # dd/mm/yy os = [ "NixOS", "Debian", "Windows" ] locales = [ "en_GB", "pt_PT" ] languages = [ "Nix", "Python", "Go", "C", "Rust" ] # Most knowledgable to least knowledgable extra = "Caught the portuguese virus on the first second of me being born :pensive:" [amadaluzia.socials] discord = "@amadaluzia" youtube = "@amadaluzia" github = "@amadalusia" </syntaxhighlight> 9e3e08a33335e9cc7c3def13e7ddab1fcda78c4a 3 321 1125 2024-10-25T12:12:41Z Amadaluzia 52 /* hey */ new section wikitext text/x-wiki == hey == hello [[User:Amadaluzia|Amadaluzia]] ([[User talk:Amadaluzia|talk]]) 12:12, 25 October 2024 (UTC) 94a9fa94387bc1c8528126c7b283bbb3697f0d99 0 322 1126 2024-10-25T23:31:38Z Xmm 51 Add a basic explanation of what musl libc is. wikitext text/x-wiki '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation e2c96b2e9e3ed4a4e77857b065b945faa43d659e 1127 1126 2024-10-25T23:37:10Z Xmm 51 Typography errors. wikitext text/x-wiki {{DISPLAYTITLE:musl}} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. __INDEX__ [[Category:Libc]] {{DEFAULTSORT:musl}} 62878c9a44d8207c972e47ed9d0e30a815540f16 1128 1127 2024-10-25T23:37:49Z Xmm 51 wikitext text/x-wiki {{DISPLAYTITLE:musl}} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. __INDEX__ [[Category:Libc]] {{DEFAULTSORT:musl}} {{DEFAULTSORT:musl}} 99b74c6456ccdcfaa088599d027631436cd55523 1130 1128 2024-10-25T23:53:46Z Xmm 51 Add a box with extra information and a screenshot showing musl ldd's output. wikitext text/x-wiki {{DISPLAYTITLE:musl}} {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. __INDEX__ [[Category:Libc]] {{DEFAULTSORT:musl}} {{DEFAULTSORT:musl}} 5cc9ce557aee9801f33286625b698f7d678050a6 1131 1130 2024-10-26T00:11:50Z Xmm 51 Add a comparison table along notes. wikitext text/x-wiki == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Comparisons between different C libraries implementations. === {| class="wikitable sortable" |+ !Bloat comparison !musl !uClibc !dietlibc !glibc |- !Complete .a set |426k |500k |120k |2.0M † |- !Complete .so set |527k |560k |185k |7.9M † |- !Smallest static C program |1.8k |5k |0.2k |662k |- !Static hello (using printf) |13k |70k |6k |662k |- !Dynamic overhead (min. dirty) |20k |40k |40k |48k |- !Static overhead (min. dirty) |8k |12k |8k |28k |- !Static stdio overhead (min. dirty) |8k |24k |16k |36k |- !Configurable featureset |no |yes |minimal |minimal |- !Behavior on resource exhaustion !musl !uClibc !dietlibc !glibc |- !Thread-local storage |reports failure |aborts |n/a |aborts |- !SIGEV_THREAD timers |no failure |n/a |n/a |lost overruns |- !pthread_cancel |no failure |aborts |n/a |aborts |- !regcomp and regexec |reports failure |crashes |reports failure |crashes |- !fnmatch |no failure |unknown |no failure |reports failure |- !printf family |no failure |no failure |no failure |reports failure |- !strtol family |no failure |no failure |no failure |no failure |- !Performance comparison !musl !uClibc !dietlibc !glibc |- !Tiny allocation & free |0.005 |0.004 |0.013 |0.002 |- !Big allocation & free |0.027 |0.018 |0.023 |0.016 |- !Allocation contention, local |0.048 |0.134 |0.393 |0.041 |- !Allocation contention, shared |0.050 |0.132 |0.394 |0.062 |- !Zero-fill (memset) |0.023 |0.048 |0.055 |0.012 |- !String length (strlen) |0.081 |0.098 |0.161 |0.048 |- !Byte search (strchr) |0.142 |0.243 |0.198 |0.028 |- !Substring (strstr) |0.057 |1.273 |1.030 |0.088 |- !Thread creation/joining |0.248 |0.126 |45.761 |0.142 |- !Mutex lock/unlock |0.042 |0.055 |0.785 |0.046 |- !UTF-8 decode buffered |0.073 |0.140 |0.257 |0.351 |- !UTF-8 decode byte-by-byte |0.153 |0.395 |0.236 |0.563 |- !Stdio putc/getc |0.270 |0.808 |7.791 |0.497 |- !Stdio putc/getc unlocked |0.200 |0.282 |0.269 |0.144 |- !Regex compile |0.058 |0.041 |0.014 |0.039 |- !Regex search (a{25}b) |0.188 |0.188 |0.967 |0.137 |- !Self-exec (static linked) |234µs |245µs |272µs |457µs |- !Self-exec (dynamic linked) |446µs |590µs |675µs |864µs |- !ABI and versioning comparison !musl !uClibc !dietlibc !glibc |- !Stable ABI |yes |no |unofficially |yes |- !LSB-compatible ABI |incomplete |no |no |yes |- !Backwards compatibility |yes |no |unofficially |yes |- !Forwards compatibility |yes |no |unofficially |no |- !Atomic upgrades |yes |no |no |no |- !Symbol versioning |no |no |no |yes |- !Algorithms comparison !musl !uClibc !dietlibc !glibc |- !Substring search (strstr) |twoway |naive |naive |twoway |- !Regular expressions |dfa |dfa |backtracking |dfa |- !Sorting (qsort) |smoothsort |shellsort |naive quicksort |introsort |- !Allocator (malloc) |musl-native |dlmalloc |diet-native |ptmalloc |- !Features comparison !musl !uClibc !dietlibc !glibc |- !Conformant printf |yes |yes |no |yes |- !Exact floating point printing |yes |no |no |yes |- !C99 math library |yes |partial |no |yes |- !C11 threads API |yes |no |no |no |- !C11 thread-local storage |yes |yes |no |yes |- !GCC libstdc++ compatibility |yes |yes |no |yes |- !POSIX threads |yes |yes, on most archs |broken |yes |- !POSIX process scheduling |stub |incorrect |no |incorrect |- !POSIX thread priority scheduling |yes |yes |no |yes |- !POSIX localedef |no |no |no |yes |- !Wide character interfaces |yes |yes |minimal |yes |- !Legacy 8-bit codepages |no |yes |minimal |slow, via gconv |- !Legacy CJK encodings |no |no |no |slow, via gconv |- !UTF-8 multibyte |native; 100% conformant |native; nonconformant |dangerously nonconformant |slow, via gconv; nonconformant |- !Iconv character conversions |most major encodings |mainly UTFs |no |the kitchen sink |- !Iconv transliteration extension |no |no |no |yes |- !Openwall-style TCB shadow |yes |no |no |no |- !Sun RPC, NIS |no |yes |yes |yes |- !Zoneinfo (advanced timezones) |yes |no |yes |yes |- !Gmon profiling |no |no |yes |yes |- !Debugging features |no |no |no |yes |- !Various Linux extensions |yes |yes |partial |yes |- !Target architectures comparison !musl !uClibc !dietlibc !glibc |- !i386 |yes |yes |yes |yes |- !x86_64 |yes |yes |yes |yes |- !x86_64 x32 ABI (ILP32) |experimental |no |no |non-conforming |- !ARM |yes |yes |yes |yes |- !Aarch64 (64-bit ARM) |yes |no |no |yes |- !MIPS |yes |yes |yes |yes |- !SuperH |yes |yes |no |yes |- !Microblaze |yes |partial |no |yes |- !PowerPC (32- and 64-bit) |yes |yes |yes |yes |- !Sparc |no |yes |yes |yes |- !Alpha |no |yes |yes |yes |- !S/390 (32-bit) |no |no |yes |yes |- !S/390x (64-bit) |yes |no |yes |yes |- !OpenRISC 1000 (or1k) |yes |no |no |not upstream |- !Motorola 680x0 (m68k) |yes |yes |no |yes |- !MMU-less microcontrollers |yes, elf/fdpic |yes, bflt |no |no |- !Build environment comparison !musl !uClibc !dietlibc !glibc |- !Legacy-code-friendly headers |partial |yes |no |yes |- !Lightweight headers |yes |no |yes |no |- !Usable without native toolchain |yes |no |yes |no |- !Respect for C namespace |yes |LFS64 problems |no |LFS64 problems |- !Respect for POSIX namespace |yes |LFS64 problems |no |LFS64 problems |- !Security/hardening comparison !musl !uClibc !dietlibc !glibc |- !Attention to corner cases |yes |yes |no |too much malloc |- !Safe UTF-8 decoder |yes |yes |no |yes |- !Avoids superlinear big-O's |yes |sometimes |no |yes |- !Stack smashing protection |yes |yes |no |yes |- !Heap corruption detection |yes |no |no |yes |- !Misc. comparisons !musl !uClibc !dietlibc !glibc |- !License |MIT |LGPL 2.1 |GPL 2 |LGPL 2.1+ w/exceptions |} Official benchmarks <ref>Etalabs [https://www.etalabs.net/compare_libcs.html]https://www.etalabs.net/compare_libcs.html</ref> ==Notes== <references /> c02dfdd7d457ada9a9f2ae70e4a2eaa95be2e3a6 1132 1131 2024-10-26T00:14:22Z Xmm 51 Add reference to "bloat" wikitext text/x-wiki == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Comparisons between different C libraries implementations. === {| class="wikitable sortable" |+ ![[Bloat]] comparison !musl !uClibc !dietlibc !glibc |- !Complete .a set |426k |500k |120k |2.0M † |- !Complete .so set |527k |560k |185k |7.9M † |- !Smallest static C program |1.8k |5k |0.2k |662k |- !Static hello (using printf) |13k |70k |6k |662k |- !Dynamic overhead (min. dirty) |20k |40k |40k |48k |- !Static overhead (min. dirty) |8k |12k |8k |28k |- !Static stdio overhead (min. dirty) |8k |24k |16k |36k |- !Configurable featureset |no |yes |minimal |minimal |- !Behavior on resource exhaustion !musl !uClibc !dietlibc !glibc |- !Thread-local storage |reports failure |aborts |n/a |aborts |- !SIGEV_THREAD timers |no failure |n/a |n/a |lost overruns |- !pthread_cancel |no failure |aborts |n/a |aborts |- !regcomp and regexec |reports failure |crashes |reports failure |crashes |- !fnmatch |no failure |unknown |no failure |reports failure |- !printf family |no failure |no failure |no failure |reports failure |- !strtol family |no failure |no failure |no failure |no failure |- !Performance comparison !musl !uClibc !dietlibc !glibc |- !Tiny allocation & free |0.005 |0.004 |0.013 |0.002 |- !Big allocation & free |0.027 |0.018 |0.023 |0.016 |- !Allocation contention, local |0.048 |0.134 |0.393 |0.041 |- !Allocation contention, shared |0.050 |0.132 |0.394 |0.062 |- !Zero-fill (memset) |0.023 |0.048 |0.055 |0.012 |- !String length (strlen) |0.081 |0.098 |0.161 |0.048 |- !Byte search (strchr) |0.142 |0.243 |0.198 |0.028 |- !Substring (strstr) |0.057 |1.273 |1.030 |0.088 |- !Thread creation/joining |0.248 |0.126 |45.761 |0.142 |- !Mutex lock/unlock |0.042 |0.055 |0.785 |0.046 |- !UTF-8 decode buffered |0.073 |0.140 |0.257 |0.351 |- !UTF-8 decode byte-by-byte |0.153 |0.395 |0.236 |0.563 |- !Stdio putc/getc |0.270 |0.808 |7.791 |0.497 |- !Stdio putc/getc unlocked |0.200 |0.282 |0.269 |0.144 |- !Regex compile |0.058 |0.041 |0.014 |0.039 |- !Regex search (a{25}b) |0.188 |0.188 |0.967 |0.137 |- !Self-exec (static linked) |234µs |245µs |272µs |457µs |- !Self-exec (dynamic linked) |446µs |590µs |675µs |864µs |- !ABI and versioning comparison !musl !uClibc !dietlibc !glibc |- !Stable ABI |yes |no |unofficially |yes |- !LSB-compatible ABI |incomplete |no |no |yes |- !Backwards compatibility |yes |no |unofficially |yes |- !Forwards compatibility |yes |no |unofficially |no |- !Atomic upgrades |yes |no |no |no |- !Symbol versioning |no |no |no |yes |- !Algorithms comparison !musl !uClibc !dietlibc !glibc |- !Substring search (strstr) |twoway |naive |naive |twoway |- !Regular expressions |dfa |dfa |backtracking |dfa |- !Sorting (qsort) |smoothsort |shellsort |naive quicksort |introsort |- !Allocator (malloc) |musl-native |dlmalloc |diet-native |ptmalloc |- !Features comparison !musl !uClibc !dietlibc !glibc |- !Conformant printf |yes |yes |no |yes |- !Exact floating point printing |yes |no |no |yes |- !C99 math library |yes |partial |no |yes |- !C11 threads API |yes |no |no |no |- !C11 thread-local storage |yes |yes |no |yes |- !GCC libstdc++ compatibility |yes |yes |no |yes |- !POSIX threads |yes |yes, on most archs |broken |yes |- !POSIX process scheduling |stub |incorrect |no |incorrect |- !POSIX thread priority scheduling |yes |yes |no |yes |- !POSIX localedef |no |no |no |yes |- !Wide character interfaces |yes |yes |minimal |yes |- !Legacy 8-bit codepages |no |yes |minimal |slow, via gconv |- !Legacy CJK encodings |no |no |no |slow, via gconv |- !UTF-8 multibyte |native; 100% conformant |native; nonconformant |dangerously nonconformant |slow, via gconv; nonconformant |- !Iconv character conversions |most major encodings |mainly UTFs |no |the kitchen sink |- !Iconv transliteration extension |no |no |no |yes |- !Openwall-style TCB shadow |yes |no |no |no |- !Sun RPC, NIS |no |yes |yes |yes |- !Zoneinfo (advanced timezones) |yes |no |yes |yes |- !Gmon profiling |no |no |yes |yes |- !Debugging features |no |no |no |yes |- !Various Linux extensions |yes |yes |partial |yes |- !Target architectures comparison !musl !uClibc !dietlibc !glibc |- !i386 |yes |yes |yes |yes |- !x86_64 |yes |yes |yes |yes |- !x86_64 x32 ABI (ILP32) |experimental |no |no |non-conforming |- !ARM |yes |yes |yes |yes |- !Aarch64 (64-bit ARM) |yes |no |no |yes |- !MIPS |yes |yes |yes |yes |- !SuperH |yes |yes |no |yes |- !Microblaze |yes |partial |no |yes |- !PowerPC (32- and 64-bit) |yes |yes |yes |yes |- !Sparc |no |yes |yes |yes |- !Alpha |no |yes |yes |yes |- !S/390 (32-bit) |no |no |yes |yes |- !S/390x (64-bit) |yes |no |yes |yes |- !OpenRISC 1000 (or1k) |yes |no |no |not upstream |- !Motorola 680x0 (m68k) |yes |yes |no |yes |- !MMU-less microcontrollers |yes, elf/fdpic |yes, bflt |no |no |- !Build environment comparison !musl !uClibc !dietlibc !glibc |- !Legacy-code-friendly headers |partial |yes |no |yes |- !Lightweight headers |yes |no |yes |no |- !Usable without native toolchain |yes |no |yes |no |- !Respect for C namespace |yes |LFS64 problems |no |LFS64 problems |- !Respect for POSIX namespace |yes |LFS64 problems |no |LFS64 problems |- !Security/hardening comparison !musl !uClibc !dietlibc !glibc |- !Attention to corner cases |yes |yes |no |too much malloc |- !Safe UTF-8 decoder |yes |yes |no |yes |- !Avoids superlinear big-O's |yes |sometimes |no |yes |- !Stack smashing protection |yes |yes |no |yes |- !Heap corruption detection |yes |no |no |yes |- !Misc. comparisons !musl !uClibc !dietlibc !glibc |- !License |MIT |LGPL 2.1 |GPL 2 |LGPL 2.1+ w/exceptions |} Official benchmarks <ref>Etalabs [https://www.etalabs.net/compare_libcs.html]https://www.etalabs.net/compare_libcs.html</ref> ==Notes== <references /> 78add1b4a0ef4146d8104d810f9332e8fa6898b0 1133 1132 2024-10-26T00:31:03Z Xmm 51 Usage on operating systems and another alternatives/implementations. wikitext text/x-wiki == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on Operating Systems === Linux distributions which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * Sabotage * Morpheus Linux * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against [[glibc]], [[gcompat]], glibmus-hq. can be used to execute them on musl-based distros. === Comparisons between different C library implementations. === {| class="wikitable sortable" |+ ![[Bloat]] comparison !musl !uClibc !dietlibc ![[glibc]] |- !Complete .a set |426k |500k |120k |2.0M † |- !Complete .so set |527k |560k |185k |7.9M † |- !Smallest static C program |1.8k |5k |0.2k |662k |- !Static hello (using printf) |13k |70k |6k |662k |- !Dynamic overhead (min. dirty) |20k |40k |40k |48k |- !Static overhead (min. dirty) |8k |12k |8k |28k |- !Static stdio overhead (min. dirty) |8k |24k |16k |36k |- !Configurable featureset |no |yes |minimal |minimal |- !Behavior on resource exhaustion !musl !uClibc !dietlibc ![[glibc]] |- !Thread-local storage |reports failure |aborts |n/a |aborts |- !SIGEV_THREAD timers |no failure |n/a |n/a |lost overruns |- !pthread_cancel |no failure |aborts |n/a |aborts |- !regcomp and regexec |reports failure |crashes |reports failure |crashes |- !fnmatch |no failure |unknown |no failure |reports failure |- !printf family |no failure |no failure |no failure |reports failure |- !strtol family |no failure |no failure |no failure |no failure |- !Performance comparison !musl !uClibc !dietlibc ![[glibc]] |- !Tiny allocation & free |0.005 |0.004 |0.013 |0.002 |- !Big allocation & free |0.027 |0.018 |0.023 |0.016 |- !Allocation contention, local |0.048 |0.134 |0.393 |0.041 |- !Allocation contention, shared |0.050 |0.132 |0.394 |0.062 |- !Zero-fill (memset) |0.023 |0.048 |0.055 |0.012 |- !String length (strlen) |0.081 |0.098 |0.161 |0.048 |- !Byte search (strchr) |0.142 |0.243 |0.198 |0.028 |- !Substring (strstr) |0.057 |1.273 |1.030 |0.088 |- !Thread creation/joining |0.248 |0.126 |45.761 |0.142 |- !Mutex lock/unlock |0.042 |0.055 |0.785 |0.046 |- !UTF-8 decode buffered |0.073 |0.140 |0.257 |0.351 |- !UTF-8 decode byte-by-byte |0.153 |0.395 |0.236 |0.563 |- !Stdio putc/getc |0.270 |0.808 |7.791 |0.497 |- !Stdio putc/getc unlocked |0.200 |0.282 |0.269 |0.144 |- !Regex compile |0.058 |0.041 |0.014 |0.039 |- !Regex search (a{25}b) |0.188 |0.188 |0.967 |0.137 |- !Self-exec (static linked) |234µs |245µs |272µs |457µs |- !Self-exec (dynamic linked) |446µs |590µs |675µs |864µs |- !ABI and versioning comparison !musl !uClibc !dietlibc ![[glibc]] |- !Stable ABI |yes |no |unofficially |yes |- !LSB-compatible ABI |incomplete |no |no |yes |- !Backwards compatibility |yes |no |unofficially |yes |- !Forwards compatibility |yes |no |unofficially |no |- !Atomic upgrades |yes |no |no |no |- !Symbol versioning |no |no |no |yes |- !Algorithms comparison !musl !uClibc !dietlibc ![[glibc]] |- !Substring search (strstr) |twoway |naive |naive |twoway |- !Regular expressions |dfa |dfa |backtracking |dfa |- !Sorting (qsort) |smoothsort |shellsort |naive quicksort |introsort |- !Allocator (malloc) |musl-native |dlmalloc |diet-native |ptmalloc |- !Features comparison !musl !uClibc !dietlibc ![[glibc]] |- !Conformant printf |yes |yes |no |yes |- !Exact floating point printing |yes |no |no |yes |- !C99 math library |yes |partial |no |yes |- !C11 threads API |yes |no |no |no |- !C11 thread-local storage |yes |yes |no |yes |- !GCC libstdc++ compatibility |yes |yes |no |yes |- !POSIX threads |yes |yes, on most archs |broken |yes |- !POSIX process scheduling |stub |incorrect |no |incorrect |- !POSIX thread priority scheduling |yes |yes |no |yes |- !POSIX localedef |no |no |no |yes |- !Wide character interfaces |yes |yes |minimal |yes |- !Legacy 8-bit codepages |no |yes |minimal |slow, via gconv |- !Legacy CJK encodings |no |no |no |slow, via gconv |- !UTF-8 multibyte |native; 100% conformant |native; nonconformant |dangerously nonconformant |slow, via gconv; nonconformant |- !Iconv character conversions |most major encodings |mainly UTFs |no |the kitchen sink |- !Iconv transliteration extension |no |no |no |yes |- !Openwall-style TCB shadow |yes |no |no |no |- !Sun RPC, NIS |no |yes |yes |yes |- !Zoneinfo (advanced timezones) |yes |no |yes |yes |- !Gmon profiling |no |no |yes |yes |- !Debugging features |no |no |no |yes |- !Various Linux extensions |yes |yes |partial |yes |- !Target architectures comparison !musl !uClibc !dietlibc ![[glibc]] |- !i386 |yes |yes |yes |yes |- !x86_64 |yes |yes |yes |yes |- !x86_64 x32 ABI (ILP32) |experimental |no |no |non-conforming |- !ARM |yes |yes |yes |yes |- !Aarch64 (64-bit ARM) |yes |no |no |yes |- !MIPS |yes |yes |yes |yes |- !SuperH |yes |yes |no |yes |- !Microblaze |yes |partial |no |yes |- !PowerPC (32- and 64-bit) |yes |yes |yes |yes |- !Sparc |no |yes |yes |yes |- !Alpha |no |yes |yes |yes |- !S/390 (32-bit) |no |no |yes |yes |- !S/390x (64-bit) |yes |no |yes |yes |- !OpenRISC 1000 (or1k) |yes |no |no |not upstream |- !Motorola 680x0 (m68k) |yes |yes |no |yes |- !MMU-less microcontrollers |yes, elf/fdpic |yes, bflt |no |no |- !Build environment comparison !musl !uClibc !dietlibc ![[glibc]] |- !Legacy-code-friendly headers |partial |yes |no |yes |- !Lightweight headers |yes |no |yes |no |- !Usable without native toolchain |yes |no |yes |no |- !Respect for C namespace |yes |LFS64 problems |no |LFS64 problems |- !Respect for POSIX namespace |yes |LFS64 problems |no |LFS64 problems |- !Security/hardening comparison !musl !uClibc !dietlibc ![[glibc]] |- !Attention to corner cases |yes |yes |no |too much malloc |- !Safe UTF-8 decoder |yes |yes |no |yes |- !Avoids superlinear big-O's |yes |sometimes |no |yes |- !Stack smashing protection |yes |yes |no |yes |- !Heap corruption detection |yes |no |no |yes |- !Misc. comparisons !musl !uClibc !dietlibc ![[glibc]] |- !License |MIT |LGPL 2.1 |GPL 2 |LGPL 2.1+ w/exceptions |} Official benchmarks <ref>Etalabs [https://www.etalabs.net/compare_libcs.html]https://www.etalabs.net/compare_libcs.html</ref> === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] ==Notes== <references /> ed747bc19d32bf618a774caad8b53d38d4e82214 1134 1133 2024-10-26T14:35:51Z Atmois 13 Atmois moved page [[Musl libc]] to [[Musl]]: Misspelled title: musl wikitext text/x-wiki == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on Operating Systems === Linux distributions which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * Sabotage * Morpheus Linux * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against [[glibc]], [[gcompat]], glibmus-hq. can be used to execute them on musl-based distros. === Comparisons between different C library implementations. === {| class="wikitable sortable" |+ ![[Bloat]] comparison !musl !uClibc !dietlibc ![[glibc]] |- !Complete .a set |426k |500k |120k |2.0M † |- !Complete .so set |527k |560k |185k |7.9M † |- !Smallest static C program |1.8k |5k |0.2k |662k |- !Static hello (using printf) |13k |70k |6k |662k |- !Dynamic overhead (min. dirty) |20k |40k |40k |48k |- !Static overhead (min. dirty) |8k |12k |8k |28k |- !Static stdio overhead (min. dirty) |8k |24k |16k |36k |- !Configurable featureset |no |yes |minimal |minimal |- !Behavior on resource exhaustion !musl !uClibc !dietlibc ![[glibc]] |- !Thread-local storage |reports failure |aborts |n/a |aborts |- !SIGEV_THREAD timers |no failure |n/a |n/a |lost overruns |- !pthread_cancel |no failure |aborts |n/a |aborts |- !regcomp and regexec |reports failure |crashes |reports failure |crashes |- !fnmatch |no failure |unknown |no failure |reports failure |- !printf family |no failure |no failure |no failure |reports failure |- !strtol family |no failure |no failure |no failure |no failure |- !Performance comparison !musl !uClibc !dietlibc ![[glibc]] |- !Tiny allocation & free |0.005 |0.004 |0.013 |0.002 |- !Big allocation & free |0.027 |0.018 |0.023 |0.016 |- !Allocation contention, local |0.048 |0.134 |0.393 |0.041 |- !Allocation contention, shared |0.050 |0.132 |0.394 |0.062 |- !Zero-fill (memset) |0.023 |0.048 |0.055 |0.012 |- !String length (strlen) |0.081 |0.098 |0.161 |0.048 |- !Byte search (strchr) |0.142 |0.243 |0.198 |0.028 |- !Substring (strstr) |0.057 |1.273 |1.030 |0.088 |- !Thread creation/joining |0.248 |0.126 |45.761 |0.142 |- !Mutex lock/unlock |0.042 |0.055 |0.785 |0.046 |- !UTF-8 decode buffered |0.073 |0.140 |0.257 |0.351 |- !UTF-8 decode byte-by-byte |0.153 |0.395 |0.236 |0.563 |- !Stdio putc/getc |0.270 |0.808 |7.791 |0.497 |- !Stdio putc/getc unlocked |0.200 |0.282 |0.269 |0.144 |- !Regex compile |0.058 |0.041 |0.014 |0.039 |- !Regex search (a{25}b) |0.188 |0.188 |0.967 |0.137 |- !Self-exec (static linked) |234µs |245µs |272µs |457µs |- !Self-exec (dynamic linked) |446µs |590µs |675µs |864µs |- !ABI and versioning comparison !musl !uClibc !dietlibc ![[glibc]] |- !Stable ABI |yes |no |unofficially |yes |- !LSB-compatible ABI |incomplete |no |no |yes |- !Backwards compatibility |yes |no |unofficially |yes |- !Forwards compatibility |yes |no |unofficially |no |- !Atomic upgrades |yes |no |no |no |- !Symbol versioning |no |no |no |yes |- !Algorithms comparison !musl !uClibc !dietlibc ![[glibc]] |- !Substring search (strstr) |twoway |naive |naive |twoway |- !Regular expressions |dfa |dfa |backtracking |dfa |- !Sorting (qsort) |smoothsort |shellsort |naive quicksort |introsort |- !Allocator (malloc) |musl-native |dlmalloc |diet-native |ptmalloc |- !Features comparison !musl !uClibc !dietlibc ![[glibc]] |- !Conformant printf |yes |yes |no |yes |- !Exact floating point printing |yes |no |no |yes |- !C99 math library |yes |partial |no |yes |- !C11 threads API |yes |no |no |no |- !C11 thread-local storage |yes |yes |no |yes |- !GCC libstdc++ compatibility |yes |yes |no |yes |- !POSIX threads |yes |yes, on most archs |broken |yes |- !POSIX process scheduling |stub |incorrect |no |incorrect |- !POSIX thread priority scheduling |yes |yes |no |yes |- !POSIX localedef |no |no |no |yes |- !Wide character interfaces |yes |yes |minimal |yes |- !Legacy 8-bit codepages |no |yes |minimal |slow, via gconv |- !Legacy CJK encodings |no |no |no |slow, via gconv |- !UTF-8 multibyte |native; 100% conformant |native; nonconformant |dangerously nonconformant |slow, via gconv; nonconformant |- !Iconv character conversions |most major encodings |mainly UTFs |no |the kitchen sink |- !Iconv transliteration extension |no |no |no |yes |- !Openwall-style TCB shadow |yes |no |no |no |- !Sun RPC, NIS |no |yes |yes |yes |- !Zoneinfo (advanced timezones) |yes |no |yes |yes |- !Gmon profiling |no |no |yes |yes |- !Debugging features |no |no |no |yes |- !Various Linux extensions |yes |yes |partial |yes |- !Target architectures comparison !musl !uClibc !dietlibc ![[glibc]] |- !i386 |yes |yes |yes |yes |- !x86_64 |yes |yes |yes |yes |- !x86_64 x32 ABI (ILP32) |experimental |no |no |non-conforming |- !ARM |yes |yes |yes |yes |- !Aarch64 (64-bit ARM) |yes |no |no |yes |- !MIPS |yes |yes |yes |yes |- !SuperH |yes |yes |no |yes |- !Microblaze |yes |partial |no |yes |- !PowerPC (32- and 64-bit) |yes |yes |yes |yes |- !Sparc |no |yes |yes |yes |- !Alpha |no |yes |yes |yes |- !S/390 (32-bit) |no |no |yes |yes |- !S/390x (64-bit) |yes |no |yes |yes |- !OpenRISC 1000 (or1k) |yes |no |no |not upstream |- !Motorola 680x0 (m68k) |yes |yes |no |yes |- !MMU-less microcontrollers |yes, elf/fdpic |yes, bflt |no |no |- !Build environment comparison !musl !uClibc !dietlibc ![[glibc]] |- !Legacy-code-friendly headers |partial |yes |no |yes |- !Lightweight headers |yes |no |yes |no |- !Usable without native toolchain |yes |no |yes |no |- !Respect for C namespace |yes |LFS64 problems |no |LFS64 problems |- !Respect for POSIX namespace |yes |LFS64 problems |no |LFS64 problems |- !Security/hardening comparison !musl !uClibc !dietlibc ![[glibc]] |- !Attention to corner cases |yes |yes |no |too much malloc |- !Safe UTF-8 decoder |yes |yes |no |yes |- !Avoids superlinear big-O's |yes |sometimes |no |yes |- !Stack smashing protection |yes |yes |no |yes |- !Heap corruption detection |yes |no |no |yes |- !Misc. comparisons !musl !uClibc !dietlibc ![[glibc]] |- !License |MIT |LGPL 2.1 |GPL 2 |LGPL 2.1+ w/exceptions |} Official benchmarks <ref>Etalabs [https://www.etalabs.net/compare_libcs.html]https://www.etalabs.net/compare_libcs.html</ref> === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] ==Notes== <references /> ed747bc19d32bf618a774caad8b53d38d4e82214 6 323 1129 2024-10-25T23:50:05Z Xmm 51 wikitext text/x-wiki musl ldd command output 4b50ee6daac9500fe6511a41da0a8459f6899170 0 324 1135 2024-10-26T14:35:51Z Atmois 13 Atmois moved page [[Musl libc]] to [[Musl]]: Misspelled title: musl wikitext text/x-wiki #REDIRECT [[Musl]] 3ac6a78efdafcbbd7db6071fcf69cdff3f0a71f2 2 325 1136 2024-10-27T17:39:18Z Katz 53 Created page with "A man, not a myth, and definitely not the legend" wikitext text/x-wiki A man, not a myth, and definitely not the legend 2e9cc513a23668512b76ed075e2dda0044490120 0 198 1137 988 2024-10-27T18:13:34Z Katz 53 added guix to independedt cdisbi Distributinos wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the package manager Guix and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] 8dcd8b7b28393a3000b804959b3552bb443a7019 1166 1137 2024-10-28T12:56:04Z Katz 53 switched a word around wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] f6603667eea7eac3dd1d34b3bf122c4f07477b0e 0 171 1138 986 2024-10-27T21:57:21Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module made to configure your user's <code>/home</code>, Home Manager can be installed in different ways but a common approach is using the NixOS module, as that rebuilds Home Manager along with NixOS. Home Manager also provides a wide variety of options beyond the NixOS standard options, which can be utilized to manage files, install and configure applications among other utilization options. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 9fc9a369ca239705980bdfd25b535682c98dcd54 1139 1138 2024-10-27T22:07:30Z Rustweld 50 home manager description wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in /home, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] d838fea58e2e7c950b9b3dfd8532ffd763f1811a 1140 1139 2024-10-27T22:08:11Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home<code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 0c5162786673ee8f79ec2b40579a222b0059da2b 1141 1140 2024-10-27T22:08:58Z Rustweld 50 /* Home Manager */ wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in /home, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 7aaa4c5921c4304cf7560f07186e5cd5cdc6137a 1142 1141 2024-10-27T22:14:58Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in `/home`, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 0e488c4679f30cff51885276ace2cde14b57d05c 1143 1142 2024-10-27T22:17:15Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> There are also plans to improve the Nix language and make it into the Lix language, which is different but still generally syntactically compatible with the Nix language.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] c9afd4cbf27305107bb03dd6da599bdd39488093 1144 1143 2024-10-27T22:26:08Z Rustweld 50 lix section improved wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community convention for nix, has received a sponsorship from Anduril, a military defense contractor based in the US. The event venue, TU Darmstadt, became aware of the sponsorship and asked for additional information from the Nix Foundation to determine if the sponsorship was in accordance with their policies. Following this, the Nix Foundation decided to rescind the Anduril sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 5b9a57c32a5f4d8e7b8dbf854cb4b44f10df546b 1145 1144 2024-10-27T22:30:44Z Rustweld 50 /* Anduril Sponsorship */ wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter of criticism to the Nix Foundation demanding the resignation of Eelco Dolstra, he eventually resigned.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After the resignation, a new board was formed. Their first action was to unban a controversial user from the Nixpkgs contributor Zulip chat, which sparked controversy.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 3b79ec7ab88c9bb771825ad97b98ecb07ccd7047 1146 1145 2024-10-27T22:33:08Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Awesome, Enlightenment, Fluxbox, GNOME, [[i3]], [[IceWM]], [[KDE Plasma]], LXQt, Ratpoison, [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] d4a296f527482662c73e65791d535c94eca725c4 1147 1146 2024-10-27T22:37:41Z Rustweld 50 fixed inaccuracies wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], which provides atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was originally founded by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 3dcc761b80072d3fd50cd15f1be2ffe07484aae6 1148 1147 2024-10-27T22:41:29Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS uses a purely functional package management approach, ensuring that package installations do not interfere with one another. * The Nix package manager allows for reproducible builds, making it ideal for development environments. <references /> [[Category:Linux Distributions]] 881de03451e694778c4c3253aa613700ffcd2f48 1149 1148 2024-10-27T22:42:57Z Rustweld 50 /* Trivia */ wikitext text/x-wiki {{DistributionInfobox | title = NixOS Linux | image = [[File:Nix snowflake.svg|thumb]] | caption = | releasestatus = Maintained | releasemodel = Varied depending on user configuration | packagemanager = [https://nixos.org Nix] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|NixOS desktop running GNOME 43.1 along with Neofetch.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. <references /> [[Category:Linux Distributions]] 3891ab9f51720d2685d8affbd4853af3193ff1bd 1150 1149 2024-10-27T22:44:37Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|thumb|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = Customizable based on user configuration | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. <references /> [[Category:Linux Distributions]] 935f07b3347bf4b9e1a6dcdff46fa5612befe678 1151 1150 2024-10-27T22:52:59Z Rustweld 50 added a whole section for flakes wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|thumb|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = Customizable based on user configuration | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''Nix Flakes''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments.<ref>https://wiki.nixos.org/wiki/Flakes</ref> * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment.<ref>https://www.tweag.io/blog/2020-05-25-flakes/</ref> [[Category:Package Management]] [[Category:Nix]] === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. <references /> [[Category:Linux Distributions]] 7b6391b6ad1291980c8fac073c3188c9145215cd 1152 1151 2024-10-27T22:54:24Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|thumb|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = Customizable based on user configuration | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments.<ref>https://wiki.nixos.org/wiki/Flakes</ref> * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment.<ref>https://www.tweag.io/blog/2020-05-25-flakes/</ref> [[Category:Package Management]] [[Category:Nix]] === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. <references /> [[Category:Linux Distributions]] 1b75f552914542fe15cee1edf9cdf8ef2806c506 1153 1152 2024-10-27T22:55:07Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|thumb|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = Customizable based on user configuration | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. [[Category:Package Management]] [[Category:Nix]] === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. <references /> [[Category:Linux Distributions]] 5dd41b67f098a50e5e3c8aecdec9db0519199a30 1154 1153 2024-10-27T22:58:30Z Rustweld 50 wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|thumb|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = Customizable based on user configuration | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. <references /> [[Category:Linux Distributions]] 99db93e37cd3bd882093b2dcaef0b0596c691ba8 0 317 1155 1112 2024-10-28T10:56:40Z Seo 46 added more info about XBPS, help needed wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[xbps-*]] | defaultdesktops = [[Xfce]] (live image) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] 96c556a69a98610a7a41dbfa46e73c52b5fc7f06 1156 1155 2024-10-28T11:00:56Z Seo 46 fixed some small stuff wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] 4bc4f22abfe592639e2e3f0e1df33ef8b10db4f5 1157 1156 2024-10-28T11:03:05Z Seo 46 hyperlink to the xbps page wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] 60bb664454b71dcda795b65d5cdf3a3e854c47ad 1158 1157 2024-10-28T11:31:05Z Seo 46 added an installation guide wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. ==Installation== Installation is done through the live ISO image, which is provided in both a graphical form and TUI form. This section will go over installing Void the second way, as it is much quicker. ===Prerequisites=== * Some time * At least 20Gb of disk space * A flash drive or SD card * Stable connection to the internet ===Installation=== '''Step 1''': Fetch the ISO image you want to download from [https://voidlinux.org/download/ the download page], then format the USB and burn the ISO onto it. Ideally, it should become bootable. If not, look up how to make a bootable flash drive with an ISO. '''Step 2''': Boot into the live enviroment. Ensure the BIOS/UEFI boot order is set up to boot from flash drives ''first'', otherwise it will boot from the disk. Once the system has finished booting, login as <code>root</code> and run <code>void-installer</code>. '''Step 3''': Go through the steps of the installation one by one. Make sure to change the mirror to a location close to you, otherwise installing packages will take longer than wanted. Format the target disk that Void will be installed on. Note that the data on the disk will be lost permanently after this, so if you have important data that you want to backup from the disk, do it now or it'll be lost to time! Partitions usually follow a scheme like this: {| class="wikitable" style="margin:auto" |- ! Partition !! Usage !! Size |- | Boot || Designated for the bootloader || 100MB-1GB |- | Swap || Self explanatory, partition for swap || Normally the size of RAM x 2 |- | Root || The main partition, most system files will be here || The rest of the disk size |} Additionally, you can make a <code>/home</code> partition, but I usually don't set up those so I won't be explaining them. Moving onto the mounting step, the boot partition should be mounted on <code>/boot/efi</code> on a UEFI system, otherwise <code>/boot</code>. Its file system should ideally be set to <code>vfat</code>. The swap partition doesn't need to be told to be mounted anywhere, you just choose the partition type <code>swap</code> and you're good to go. The root partition should just be mounted at <code>/</code>. You can use a couple of filesystems, though my favorites are <code>btrfs</code> and <code>xfs</code>. After that, you proceed with the installation, and if everything goes right, it should report that it has installed successfully. If not, check <code>/dev/tty8</code> by hitting '''Ctrl+Alt+F8'''. Congrats! Void Linux should now be installed on your machine. Make sure to check your network connection to be sure everything went smoothly. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] 6aa96ef9334d49338aa069bd3b19c758bd1d5bf8 1162 1158 2024-10-28T11:45:18Z Seo 46 proper capitalization wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. ==Installation== Installation is done through the live ISO image, which is provided in both a graphical form and TUI form. This section will go over installing Void the second way, as it is much quicker. ===Prerequisites=== * Some time * At least 20GB of disk space * A flash drive or SD card * Stable connection to the internet ===Installation=== '''Step 1''': Fetch the ISO image you want to download from [https://voidlinux.org/download/ the download page], then format the USB and burn the ISO onto it. Ideally, it should become bootable. If not, look up how to make a bootable flash drive with an ISO. '''Step 2''': Boot into the live enviroment. Ensure the BIOS/UEFI boot order is set up to boot from flash drives ''first'', otherwise it will boot from the disk. Once the system has finished booting, login as <code>root</code> and run <code>void-installer</code>. '''Step 3''': Go through the steps of the installation one by one. Make sure to change the mirror to a location close to you, otherwise installing packages will take longer than wanted. Format the target disk that Void will be installed on. Note that the data on the disk will be lost permanently after this, so if you have important data that you want to backup from the disk, do it now or it'll be lost to time! Partitions usually follow a scheme like this: {| class="wikitable" style="margin:auto" |- ! Partition !! Usage !! Size |- | Boot || Designated for the bootloader || 100MB-1GB |- | Swap || Self explanatory, partition for swap || Normally the size of RAM x 2 |- | Root || The main partition, most system files will be here || The rest of the disk size |} Additionally, you can make a <code>/home</code> partition, but I usually don't set up those so I won't be explaining them. Moving onto the mounting step, the boot partition should be mounted on <code>/boot/efi</code> on a UEFI system, otherwise <code>/boot</code>. Its file system should ideally be set to <code>vfat</code>. The swap partition doesn't need to be told to be mounted anywhere, you just choose the partition type <code>swap</code> and you're good to go. The root partition should just be mounted at <code>/</code>. You can use a couple of filesystems, though my favorites are <code>btrfs</code> and <code>xfs</code>. After that, you proceed with the installation, and if everything goes right, it should report that it has installed successfully. If not, check <code>/dev/tty8</code> by hitting '''Ctrl+Alt+F8'''. Congrats! Void Linux should now be installed on your machine. Make sure to check your network connection to be sure everything went smoothly. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] f20fc0906acb6c0b0eb29076fa8880decf54f9c5 1164 1162 2024-10-28T12:27:38Z Seo 46 added a screenshot preview wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} [[File:Voidlinux-by-dnv.png|alt=A screenshot of a Void Linux dark mode setup|thumb|Void Linux setup running DWM.]] '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. ==Installation== Installation is done through the live ISO image, which is provided in both a graphical form and TUI form. This section will go over installing Void the second way, as it is much quicker. ===Prerequisites=== * Some time * At least 20GB of disk space * A flash drive or SD card * Stable connection to the internet ===Installation=== '''Step 1''': Fetch the ISO image you want to download from [https://voidlinux.org/download/ the download page], then format the USB and burn the ISO onto it. Ideally, it should become bootable. If not, look up how to make a bootable flash drive with an ISO. '''Step 2''': Boot into the live enviroment. Ensure the BIOS/UEFI boot order is set up to boot from flash drives ''first'', otherwise it will boot from the disk. Once the system has finished booting, login as <code>root</code> and run <code>void-installer</code>. '''Step 3''': Go through the steps of the installation one by one. Make sure to change the mirror to a location close to you, otherwise installing packages will take longer than wanted. Format the target disk that Void will be installed on. Note that the data on the disk will be lost permanently after this, so if you have important data that you want to backup from the disk, do it now or it'll be lost to time! Partitions usually follow a scheme like this: {| class="wikitable" style="margin:auto" |- ! Partition !! Usage !! Size |- | Boot || Designated for the bootloader || 100MB-1GB |- | Swap || Self explanatory, partition for swap || Normally the size of RAM x 2 |- | Root || The main partition, most system files will be here || The rest of the disk size |} Additionally, you can make a <code>/home</code> partition, but I usually don't set up those so I won't be explaining them. Moving onto the mounting step, the boot partition should be mounted on <code>/boot/efi</code> on a UEFI system, otherwise <code>/boot</code>. Its file system should ideally be set to <code>vfat</code>. The swap partition doesn't need to be told to be mounted anywhere, you just choose the partition type <code>swap</code> and you're good to go. The root partition should just be mounted at <code>/</code>. You can use a couple of filesystems, though my favorites are <code>btrfs</code> and <code>xfs</code>. After that, you proceed with the installation, and if everything goes right, it should report that it has installed successfully. If not, check <code>/dev/tty8</code> by hitting '''Ctrl+Alt+F8'''. Congrats! Void Linux should now be installed on your machine. Make sure to check your network connection to be sure everything went smoothly. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] 55685e1dfad6d9fa444e2b5369a9746c7e489e4b 0 2 1159 1067 2024-10-28T11:33:26Z Seo 46 another small trivia fact wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4. 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>https://pacman.archlinux.page/makepkg.8.html</ref><ref>https://pacman.archlinux.page/PKGBUILD.5.html</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> <references /> * Arch is directly inspired by another DIY distribution named CRUX. [[Category:Linux Distributions]] 15841309c93f812a45e2805d91fd50e4aac46c9c 1160 1159 2024-10-28T11:34:48Z Seo 46 fixed the reference wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4. 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>https://pacman.archlinux.page/makepkg.8.html</ref><ref>https://pacman.archlinux.page/PKGBUILD.5.html</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> * Arch is directly inspired by another DIY distribution named CRUX. <references /> [[Category:Linux Distributions]] 00834872bd619f0f54583a9078bb25ca3353528c 2 316 1161 1109 2024-10-28T11:38:40Z Seo 46 small adjustment to my desc wikitext text/x-wiki ====Hi there!==== [https://fs2f.github.io Website] e4161c249603d3fe98af8ae3c80b957151c0b591 6 326 1163 2024-10-28T12:23:16Z Seo 46 small screenshot of a dwm setup on void linux, all done by dnv on deskto.ps wikitext text/x-wiki == Summary == small screenshot of a dwm setup on void linux, all done by dnv on deskto.ps 3b81e11cf060b4b9e49eb46a92620a2c7ecac5a6 0 306 1167 1165 2024-10-28T13:11:19Z Rewording wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be standalone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Key Terms]] 46d6a4c676735abb7d96b120da52d5d98d9f5fb4 1168 1167 2024-10-28T13:14:43Z Grammer fix wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Key Terms]] f0f244c3883a40ae31434dec32251a34cb1361fe 1182 1168 2024-10-29T08:55:15Z Atmois 13 wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Terminology]] 79f8a99fa1c584ca284fe22f7120a5b849ac7179 1209 1182 2024-10-30T10:17:40Z Atmois 13 Fix spelling of link wikitext text/x-wiki A window manager is a piece of system software for [[X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Terminology]] 97ae73662fff26b2c1a79f5ba47265137b14eb8d 1211 1209 2024-10-30T10:20:47Z Atmois 13 Fix spelling of link wikitext text/x-wiki A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[Xfwm]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Terminology]] 2149ff552e2580f4f7cc940073526ff548ea38ef 0 198 1169 1166 2024-10-28T13:24:59Z Atmois 13 Grammer wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers those that are most popular. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] 8576e9c48fa81a670b336091dd38b57115e7aec4 1170 1169 2024-10-28T13:27:15Z Grammer fix wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] 296ff9c18995b7946402472d35c12ffead2b821a 1216 1170 2024-10-30T10:23:52Z Atmois 13 Fix spelling of link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[Xorg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] 2833682e28f0867b1057d52f6a1f2c1ec1372c9b 0 1 1171 1113 2024-10-28T15:17:18Z Atmois 13 Removed info on contributing to be updated wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Key Terms == * [[Window Manager]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Programs == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Sudo]] <!-- endwikibot --> 7111b0667d12ac10268e7ce49bd4855c3e1fe176 1172 1171 2024-10-28T15:17:49Z Atmois 13 Reverted edit by [[Special:Contributions/Atmois|Atmois]] ([[User talk:Atmois|talk]]) to last revision by [[User:WikiBot|WikiBot]] wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Key Terms == * [[Window Manager]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Programs == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Compositor]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Sudo]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' eeaa2d1802b911765651ad78ac4ebe80e71d80d3 1179 1172 2024-10-28T15:42:51Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Key Terms == * [[Bootloader]] * [[Window Manager]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[Dnf]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Programs == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Musl]] * [[Ricing]] * [[Sudo]] * [[Test]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' b7087f4d662ec23dfb2a8c62c4e9037b765f135b 1195 1179 2024-10-29T16:14:56Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Programs == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Musl]] * [[Ricing]] * [[Sudo]] * [[Test]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' fd695accfff9fd4fd16a89bd906269a7384b1dfd 1200 1195 2024-10-29T16:32:02Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Xfce]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[Dpkg]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[Dwm]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Musl]] * [[Ricing]] * [[Sudo]] * [[Test]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' e84be6630c82c7a57550d7e2c00f46945b58fef8 0 8 1173 921 2024-10-28T15:32:04Z Atmois 13 Split section wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[apk]] ** [[apt]] ** [[dnf]] ** [[dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[Dwm|DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL / GPLv3|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 48384d68105a6142141f62f2c46116c3f8be5a15 1210 1173 2024-10-30T10:19:16Z Atmois 13 Fix spelling of links wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X|X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 46827cd2bc203bcea37b59cbb583816e51cb87c5 1212 1210 2024-10-30T10:20:53Z Atmois 13 Fix spelling of links wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] ** [[GPL|General Public License [vX] (GPL vX)]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] ae66031717ebc477bd9c5f2081d93874ba974eeb 1215 1212 2024-10-30T10:23:07Z Atmois 13 Remove GPL reference, will go under lisences page wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[Script]] * [[Security]] * [[tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 28dcc85abdce29927ee999622c11741cdb80f745 4 327 1174 2024-10-28T15:35:00Z Test wikitext text/x-wiki Page for testing 1e249df3a52d134afe70220190758d127445c3f7 1175 1174 2024-10-28T15:36:10Z wikitext text/x-wiki Page for testing 2 90993c12812f9e88dc70a6dda32c66530745228a 1176 1175 2024-10-28T15:39:40Z wikitext text/x-wiki Page for testing 2 3 efe3a7844a2903e7c620f50ac181d72cef614759 1177 1176 2024-10-28T15:40:47Z wikitext text/x-wiki Page for testing 2 3 4 c863147bcdc1a2680ff24919541b25eee8deac14 1178 1177 2024-10-28T15:41:25Z wikitext text/x-wiki Page for testing 2 3 4 5 7adba03887222bf6ff81620a07806acb4a9d7646 1193 1178 2024-10-29T09:19:40Z Atmois 13 Protected "[[Test]]": Page is for admin testing. ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki Page for testing 2 3 4 5 7adba03887222bf6ff81620a07806acb4a9d7646 1196 1193 2024-10-29T16:22:59Z Atmois 13 wikitext text/x-wiki Admin testing page. a76eea74da60fce4ed15067f9368bfab9ab97539 2 325 1180 1136 2024-10-28T15:43:14Z Katz 53 added gnu braile art for fun wikitext text/x-wiki not a myth, and definitely not the legend, but simply a man who tries to work hard. ⠀⠀⠀⠀⢠⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠀⡀⢀⠀⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠠⡀⠀⠀⠀ ⠀⠀⠀⠀⢆⢑⠅⢄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⢀⠠⡠⡐⠔⢌⢊⠪⠢⡑⢌⠢⡑⢌⢊⠢⠢⡠⠀⠀⠀⠀⠀⠀⠀⠀⢀⠄⢔⠠⡑⢅⠩⡊⡑⣉⠊⡜⢐⠂⢆⠄⢄⢀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡠⢊⠒⡄⠀⠀⠀ ⠀⠀⠀⠀⡕⡐⢕⠨⡂⠢⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡀⢠⢀⠢⠢⡑⢅⢊⠢⠢⡊⠜⢄⢅⠱⡁⢎⠰⡁⢎⠰⡁⢕⠡⡊⢜⠰⣀⠀⢀⢀⡐⢌⠢⡑⢌⠢⡑⢌⠢⡨⠢⡐⢅⠪⣈⢊⠔⡑⠔⡡⡉⡊⠢⠢⡐⢄⢀⠀⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠄⡣⢘⠄⡣⠂⠀⠀⠀ ⠀⠀⠀⠀⢎⠰⡁⢎⠨⡊⠔⡡⠢⡠⠠⢄⠔⡐⠔⡡⠣⡘⢄⢅⠕⡑⢌⠢⡡⡑⡑⢌⢊⠢⡑⢌⠪⡐⢅⠪⡐⢅⠪⡐⢅⢮⡺⣝⢮⣫⢏⡷⣹⢳⢧⠘⡄⢣⠨⡂⢕⠨⡂⢕⠨⡂⢆⠱⡨⡈⢎⠰⡨⡈⢕⠡⡊⠤⡡⢑⠌⡢⠒⢄⠢⡠⠠⡠⢐⠌⡢⢑⢌⠢⡑⢌⠅⠀⠀⠀ ⠀⠀⠀⠀⢅⠣⡘⢄⠣⡘⢌⠢⡑⢌⠢⡑⢌⢌⠪⡐⠕⡌⢢⠢⡑⢌⠢⡑⢔⢌⢊⠢⡑⢌⠢⡑⢌⠪⡐⢕⠨⡢⣑⣌⢢⡟⣮⡳⣝⢮⡳⣝⢷⣝⣽⡡⣊⡢⡑⢌⠢⡑⢌⠢⡑⢌⠢⡑⢔⠑⡌⢢⠊⡔⢡⠊⡔⡑⢌⠢⡑⢌⢊⠢⡑⢌⠢⡑⢌⠢⡑⢄⠕⡨⢢⢑⠄⠀⠀⠀ ⠀⠀⠀⠀⠐⠕⡌⡢⡑⢌⠢⡑⢌⠢⡑⢌⠢⡡⡑⢌⠪⡐⡅⡢⡑⢌⠆⡕⡰⡁⡕⡱⢨⢊⡪⣜⢦⡳⣹⡪⣫⢳⡕⣝⢮⡻⣜⡽⣪⢗⡽⣪⢷⡕⣷⢹⢎⢮⡝⣝⢕⢗⢵⢥⡱⣑⠜⡰⢡⢃⠪⡢⢑⢌⢢⢑⠌⡢⡑⢌⠢⡑⢌⠢⡑⢌⠢⡑⢌⠢⡑⢌⠢⡑⢔⠁⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠑⠨⡢⢑⢅⠱⡁⡣⢊⠜⡐⠕⠔⡜⡐⢕⢌⢢⢘⠔⡱⡨⠢⡪⡘⡔⡱⣱⢏⡞⣮⣪⡳⣕⢝⢮⡳⣝⢮⡳⣝⢮⡻⣮⡳⣝⢮⡳⣝⢮⡳⣝⢮⡺⣜⢧⡻⡪⣧⢫⡎⣷⡑⣕⢌⢎⠢⡣⢢⠱⡨⡊⢔⢅⠕⡱⠨⡢⡑⢌⠢⡑⢌⠢⡑⢌⢆⠕⡜⠈⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠈⠐⠡⠣⡪⡌⡪⣘⢌⢪⢊⠦⡱⢌⠦⠱⠅⠓⠘⠈⠁⠁⢈⣠⢤⣟⢼⡹⣖⢵⡝⣮⡫⣳⢝⢮⡳⣝⢮⡳⣝⢮⡻⣮⡳⣝⢾⡣⣟⢜⡧⡻⣜⢧⣛⢞⣜⢧⡻⣜⢧⣤⣀⠈⠁⠁⠑⠑⠊⠎⠦⢣⢪⡘⡜⢔⡱⡡⡣⡩⣊⢎⠪⠂⠃⠁⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠁⠀⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣰⡫⡺⣎⡷⣝⢮⡳⣕⢯⡺⣜⢧⣫⡳⣝⢮⢷⣝⢮⡳⣝⢾⣝⢯⡳⣝⢮⡳⣝⢮⡳⡵⣝⢵⡝⣮⢳⡝⣷⢪⢮⡣⡄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠀⠀⠈⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢠⢞⢵⣝⣝⢮⣻⢎⡷⣹⢎⡷⣹⢎⢷⢵⡝⣮⢳⢷⣹⡳⣝⡽⣣⢯⡳⣝⢮⡳⣝⢮⡳⣝⢞⢮⡳⣝⢮⡳⣝⡷⣹⢎⢷⡹⢦⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⡴⣫⡳⡳⢮⢮⡳⣝⢷⣝⢮⡳⣝⢮⡳⣝⢮⡺⣕⢯⡳⣝⢾⡵⣫⢞⡵⣫⢞⡵⣫⢞⡵⣫⢮⣫⡳⣝⢮⡳⣝⢮⡗⣽⢪⣗⢝⡮⡳⣄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⢞⢮⢮⣝⣝⡳⡳⣝⢾⣣⢟⡮⣳⠝⠊⠁⠀⠀⠈⠈⠓⠽⣪⢷⡝⣮⢳⡝⣮⠳⠙⠈⠀⠀⠀⠁⠑⠹⣎⢷⡹⣎⢿⡪⣗⢵⡝⣮⢳⡝⡮⣦⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡴⣣⢏⡗⡷⣪⢮⣝⢽⡪⡷⣝⢷⣝⠊⡀⠐⠀⢁⠀⠂⠀⠄⢀⠑⢷⡹⣎⢷⣹⠊⡁⢀⠁⡀⠁⠠⠀⠄⡀⠈⢳⣝⢮⣯⡻⣜⢧⡻⣜⢧⣛⢞⣜⢯⡄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⡾⡱⣯⣪⡻⣎⢷⢵⡝⡷⣝⢾⣝⢷⠅⡐⠄⡡⠈⣤⣤⣁⠌⡀⠢⢀⠪⣗⢽⡪⡗⠠⢂⠐⠄⢄⣬⣄⠂⡐⢀⢑⠀⣿⣪⢷⣝⢮⡳⣝⢮⡳⣝⢵⡝⣮⣛⢦⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⢟⣜⠷⡵⣕⢯⡺⣕⢷⣝⣮⡻⠓⠙⣿⡐⢅⢊⠰⡀⢷⣮⡿⢀⠌⠢⡡⢘⡧⣻⢜⣇⢘⢄⠑⢄⠻⣶⣻⠃⢄⠅⡢⢑⡼⡳⠙⠺⢷⡽⣮⡳⣝⢮⡳⣝⢮⢮⡳⣳⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣰⢏⢾⣪⡻⣺⣕⢯⣞⠝⠓⠁⠀⠀⠀⠀⢻⡮⡢⡱⡡⡊⢔⢄⢆⢪⢘⠔⣅⢿⡜⣧⢻⢮⡆⡕⡡⡃⢦⠨⡄⡣⢊⢆⢕⣱⣝⡇⠀⠀⠀⠈⠑⠛⢮⢷⣝⢮⡳⣳⢝⡮⡳⡄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢰⣝⣝⢷⡕⠿⠊⠃⠁⠀⠀⠀⠀⠀⠀⠀⠀⢸⡝⡷⣕⢎⢮⢪⡢⡣⣕⢕⡳⣮⢳⡝⣮⢳⡳⣝⢮⡪⡪⡲⡱⡪⡜⣥⢣⢷⢵⣽⠀⠀⠀⠀⠀⠀⠀⠀⠀⠉⠑⠫⠷⣝⢮⡻⣺⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀ ⠀⠀⠀⠀⠀⠀⠁⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠐⣯⢻⢮⣫⡳⣳⢝⡞⣮⡫⣗⢽⡣⣟⢼⡣⣟⢼⡣⣟⣝⢾⣕⢯⡺⣮⢳⢯⡺⣞⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠉⠈⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢿⡕⡷⡵⣝⢧⡻⣜⢧⡻⣜⢧⡻⣜⢧⡻⣜⢧⡻⣮⢺⡕⣯⢺⢵⣝⢗⡯⣺⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀ ⠀ ⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢹⡮⣻⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣎⢷⡹⣎⢗⢷⡭⡻⣮⣳⠅⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀ ⠀⠀ ⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠘⣯⢮⡻⣜⢧⡻⣜⢧⡻⣜⢧⡻⣜⢧⡻⣜⢧⡻⣜⢧⡻⣜⣝⢧⡫⣟⢼⡳⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀ ⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢟⡮⣳⢝⡮⣳⢝⡮⣳⢝⡮⣳⢝⡮⣳⢝⡮⣳⢝⡮⡳⡵⣝⢮⡻⣮⢳⡏⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀ ⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣏⢾⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⡵⣝⢽⡪⣗⢽⡪⣗⢽⠂⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⣷⢳⡝⣮⢳⡝⣮⢳⡝⣮⢳⡝⣮⢳⡝⣮⢻⣎⢷⡹⣎⢷⡹⣮⡳⣻⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢿⡱⣯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢷⡹⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⡗⣵⢫⡞⣵⢫⡞⣵⢫⡞⣵⢫⡞⣵⢫⡞⣵⢫⡞⣵⢫⡞⣵⣻⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣿⢪⣗⢽⡪⣗⢽⡪⣗⢽⡪⣗⢽⡪⣗⢽⡪⣗⢽⡪⣗⢽⡪⡞⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢽⡣⣯⢳⡝⣮⢳⡝⣮⢳⡝⣮⢳⡝⣮⢳⡝⣮⢳⡝⣮⢳⣝⠇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⡳⣝⢧⡻⣜⢧⡻⣜⢧⡻⣜⢧⡻⣜⢧⡻⣜⢧⡻⣜⢧⣻⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠐⣯⢺⡕⣯⢺⡕⣯⢺⡕⣯⢺⡕⣯⢺⡕⣯⢺⡕⣯⢺⡕⣯⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢺⣕⣯⣺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⢯⡺⣕⣯⡺⣮⠆⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀ ⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠚⠪⠷⢝⠯⡺⢗⠽⠮⠷⠽⠮⠷⠽⡮⡳⠻⠞⠊⠉⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ 055721f250b84753ecc03bbf419f4056d89ae96c 0 318 1181 1115 2024-10-29T08:54:58Z Atmois 13 Update Category wikitext text/x-wiki The bootloader is a program that's responsible for booting the system. Most of the time, it will have a menu to choose an option from, making it a boot manager. A bootloader is installed onto the boot partition of the computer during a distribution's installation process. Most of the times, boot partitions may need from 200-600MB of space to work properly. Most bootloaders also have theming capabilities, take, for example, the previously mentioned GRUB. [[Category:Terminology]] 4c097b6b55477b3d64db637a32506284e03714fb 0 328 1183 2024-10-29T09:01:19Z Atmois 13 Create Alpine redirect wikitext text/x-wiki #REDIRECT [[Alpine Linux]] 7e3d294d3e21b5efa6e6de82e19a4c593d1c497e 0 329 1184 2024-10-29T09:03:10Z Atmois 13 Create Display Manager Redirect wikitext text/x-wiki #REDIRECT [[Display Manager]] 0121c8d9988a547351a53848355208464de9e7c3 0 272 1185 980 2024-10-29T09:04:30Z Atmois 13 Atmois moved page [[Dnf]] to [[DNF]]: Misspelled title: Correct spelling of DNF wikitext text/x-wiki == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. [[Category:Package Managers]] a308e483a3125fcdcbc3f0f8a6eeee6012392257 0 330 1186 2024-10-29T09:04:30Z Atmois 13 Atmois moved page [[Dnf]] to [[DNF]]: Misspelled title: Correct spelling of DNF wikitext text/x-wiki #REDIRECT [[DNF]] e6efe667ff850f3aa4d7f81d5f2856a0f8bc5b7b 0 331 1187 2024-10-29T09:11:51Z Atmois 13 Create FOSS/FLOSS redirect wikitext text/x-wiki #REDIRECT [[FOSS / FLOSS]] d9cb876c0e70a08536f83d1256b1eb3cd5951ed0 0 176 1189 1066 2024-10-29T09:12:51Z Atmois 13 Atmois moved page [[KDE Plasma]] to [[Plasma]]: Changed to offical name wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 762d94175f8a4ea02a2f0dc784b2b0f6f883ad18 0 333 1190 2024-10-29T09:12:51Z Atmois 13 Atmois moved page [[KDE Plasma]] to [[Plasma]]: Changed to offical name wikitext text/x-wiki #REDIRECT [[Plasma]] 6b2b8946ff82ff10bd26ddb1fdc6929463f491ce 0 334 1191 2024-10-29T09:14:53Z Atmois 13 Redirect to Multi-Booting wikitext text/x-wiki #REDIRECT [[Multi-booting]] 863d11e9594a2c3b97086140e15812164f4855d4 0 335 1192 2024-10-29T09:18:57Z Atmois 13 Create redirect to Rocky Linux wikitext text/x-wiki #REDIRECT [[Rocky Linux]] ba9059f24f0add1a6904ba8eba236f356f1cc138 0 336 1194 2024-10-29T09:22:56Z Atmois 13 Create Void Linux redirect wikitext text/x-wiki #REDIRECT [[Void Linux]] 633bd409ffc97d980cfa31525656e1b91e450876 0 268 1197 1053 2024-10-29T16:23:59Z Atmois 13 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch github.com/fastfetch-cli/fastfetch] }} Fastfetch is a [[neofetch]]-like tool for fetching information about your operating system, software and hardware. It is written mainly in [[C]], with a focus on performance.<ref>https://github.com/fastfetch-cli/fastfetch</ref> <references /> [[Category:Software]] 326612a1f1d6387ccc8abacec39a2589aab62af5 0 263 1198 1054 2024-10-29T16:24:12Z Atmois 13 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your operating system, software and hardware with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch</ref> === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|left|thumb|The Hyfetch Pride Month easter egg.]]If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. <references /> [[Category:Software]] 806847c84b07c39609a0af7719293391df207d45 0 261 1199 1042 2024-10-29T16:24:23Z Atmois 13 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]] (Neofetch-like utility written in [[C]]) and [[hyfetch]] (Fork of neofetch with pride flags). <references /> [[Category:Software]] 6176501b10877b3edf30f23aa37e1d8d5d2cc561 0 309 1201 1076 2024-10-29T16:54:38Z Atmois 13 Add category software wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png|thumb]] | caption = Sudo used on [[pacman]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.15p5, 2023-12-30 | languages = [[c]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]). Its name is shorthand for "substitute user and do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file to specify which users or groups can execute specific commands. == Usage == The following are several common usecases for sudo. ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser'' {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} [[Category:Software]] 51789d97af1c8567c2d49b9422fd3c52841f2875 0 254 1202 933 2024-10-30T10:13:37Z Atmois 13 Atmois moved page [[Dwm]] to [[DWM]]: Rename for consistency wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:Window Managers]] dfab0780d6801ef9f1e1ce3947c1d80674f4b793 0 337 1203 2024-10-30T10:13:37Z Atmois 13 Atmois moved page [[Dwm]] to [[DWM]]: Rename for consistency wikitext text/x-wiki #REDIRECT [[DWM]] 2a0055b306484bbc04b0b583dffad55d0dd857a2 0 246 1204 786 2024-10-30T10:13:46Z Atmois 13 Atmois moved page [[Dpkg]] to [[DPKG]]: Rename for consistency wikitext text/x-wiki {{SoftwareInfobox|image=|caption=|title=dpkg|releasestatus=Maintained|lastrelease=1.21.22 / 24 May 2023|languages=C, C++, Perl|developers=The Debian Project|website=[https://www.dpkg.org/ dpkg.org]}} '''dpkg''' (Debian Package) is the core software of the package management system in the [[Debian]] operating system and its derivatives. It is used to install, remove, and provide information about <code>.deb</code> packages. dpkg is a low-level tool. [[APT|APT (Advanced Package Tool)]] is more commonly used in practice as it is a high-level tool.<ref>Afia Zahin Oishi (December 6, 2023). [https://linuxsimply.com/linux-basics/package-management/package-manager-comparison/dpkg-vs-apt/ <nowiki>"Dpkg Vs Apt [What's the Difference Between Package Managers]"</nowiki>]. linuxsimply.com. LinuxSimply.</ref> [[Category:Package Managers]] 3a4a714894fe53107701ffea101cca36bf2276c8 0 338 1205 2024-10-30T10:13:46Z Atmois 13 Atmois moved page [[Dpkg]] to [[DPKG]]: Rename for consistency wikitext text/x-wiki #REDIRECT [[DPKG]] 283009ead3bbe8f68bf3ea7bf769cf2c83303b89 0 236 1206 1003 2024-10-30T10:13:55Z Atmois 13 Atmois moved page [[Xfce]] to [[XFCE]]: Rename for consistency wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.18, 2022-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * Desktop Manager - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[Terminal Emulator|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> [[Category:Desktop Environments]] 24c0fb974ad8115bb13d0418bc5362f8a2de5b3e 0 339 1207 2024-10-30T10:13:55Z Atmois 13 Atmois moved page [[Xfce]] to [[XFCE]]: Rename for consistency wikitext text/x-wiki #REDIRECT [[XFCE]] 734e67e842805c722062eb3052283e5b39aab900 0 319 1208 1121 2024-10-30T10:15:42Z Atmois 13 Fix spelling of link wikitext text/x-wiki '''Ricing''' is the process of customizing and fine-tuning your [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to achieve a highly personalized look and feel. The term originated from the concept of making aesthetic and functional improvements to a system's interface, similar to the act of modifying cars. Generally '''ricing''' focuses on visual customization, although, performance tweaks can be a part of the process. dbc5fd29d0039bb1493bef5799f2c20797b0af71 0 248 1213 959 2024-10-30T10:21:39Z Atmois 13 Fix spelling of links wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu receives 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] cf7519ffa78a6402452767be7e91b8fb498839a4 0 304 1214 1090 2024-10-30T10:22:22Z Atmois 13 Fix spelling of link wikitext text/x-wiki {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a [[Unix-like]] [[Operating System|operating system]] completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS]</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive [[kernel]], and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[MacOS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[Virtual Machine|virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to [[Compiling|compile]] software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub]</ref> [[Category:Misc Operating Systems]] e38d6d5f43c6911a383ec509c87e9270008fd4a2 0 240 1217 981 2024-10-30T10:24:14Z Atmois 13 Fix spelling of link wikitext text/x-wiki == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your disribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most deriative distributions. ==== General Information ==== ===== Multi Booting ===== [[File:GRUB with ubuntu and windows vista.png|thumb|GRUB, with entries for [[Ubuntu]] and Windows Vista, an example of ''dual booting.'']] [[Multi Booting]] (Or often refered to as 'Dual Booting') is the process of installing multiple [[Operating System|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completly removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to parititon the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly reccomended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi Booting]] page. ===== Finding Alternatives or Workarounds for Apps ===== Often there is at least one [[application]] missing on Linux or an app that is missing some features or is buggy so you'll find yourself looking for alternative options. There also sometimes is the issue that your distribution doesn't have an app but another distribution does have it. A good place to start when looking for alternatives is [https://alternativeto.net AlternativeTo] which is a crowdsourced site useful to find alternatives for almost any app. Other useful sites include [https://www.privacytools.io Privacy Tools] and [https://awesome-privacy.xyz Awesome Privacy] with a privacy focused list of apps. When looking for workarounds for apps not supported for your distribution you should first check [https://flathub.org Flathub] and [https://snapcraft.io Snapcraft] (Note that [[Snap|Snaps]] are known to have performance issues) if your app is available there as they offer support for most distributions. If a steam game lacks native Linux support try checking [https://www.protondb.com ProtonDB] if Valve's proton tool supports your game. [https://www.winehq.org Wine] is also an option to run Windows apps on Linux. ==== Moving between specfic Operating Systems ==== ===== Moving to Linux from MacOS ===== ===== Moving to Linux from Windows ===== === General Information === [[Category:Guides]] c3f96fe3f65ad489afe4c6d4a468fa1c8aa4ce9d 0 297 1218 1092 2024-10-30T10:24:33Z Atmois 13 Fix spelling of link wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine. Multi-booting has many uses, including: * Testing different operating systems * Utilizing software that may not work as expected on another OS * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == How to Multi-boot == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen distribution search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitons"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! [[Category:Terminology]] eaad4f26ced239ac5ec37e807508f8444bb31fe4 1220 1218 2024-10-30T10:26:18Z Atmois 13 Fix spelling of link wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine. Multi-booting has many uses, including: * Testing different operating systems * Utilizing software that may not work as expected on another OS * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == How to Multi-boot == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen distribution search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitons"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-Boot|Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! [[Category:Terminology]] 5584c5f5c00a08f18a03bb8103d66738f30acdb9 0 250 1219 1088 2024-10-30T10:25:05Z Atmois 13 Remove link wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == Ana/Miniconda Setup == ... (tomorrow's problem) == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards on more demanding games. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of Artificial Intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU -''' considering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> 2f3fe4261d38471cb372b2361da8110b769ca9cd 0 8 1221 1215 2024-10-30T10:26:34Z Atmois 13 Fix spelling of link wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[XOrg|Xorg]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] d3878583686f960a5ed0ee80ad5532ae0f8829b7 0 274 1222 957 2024-10-30T10:27:05Z Atmois 13 Fix spelling of link wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = [[KDE]], [[Xfce]], [[Cinamon]] | usagetype = Desktop, Server | architectures = amd64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init system]]s. abf1672a0208023082b6520570cb28155bcc1627 0 158 1223 993 2024-10-30T10:27:47Z Atmois 13 Fix spelling of link wikitext text/x-wiki When using [[Linux]], sooner or later, there's a good chance you'll end finding yourself in front of a [[Terminal Emulator|Terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a 'Command'. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include "echo", "mv", "[[cat]]", etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with "sudo" followed with your original command. [[sudo]] Tells your computer to 'do' something as a 'super user' which will allow you to bypass restrictions. It should be important to note that '''sudo is a seperate package''' and won't come pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you need to use something like "su" to log in as root and then run your command as root or install sudo as root. Furthermore, with commands you will likely need to include "options" that specify to the program how you want it to behave. One of the most common options is "--help", which will usually tell program to list all of its options. An example would be as follows cat --help In this case, the 'cat' utility would respond to this command with the following:<blockquote>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines............</blockquote>(Shortened to maintain focus on topic) These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, "--help" is always there and ready. If --help isnt enough, you can always run "[[man]]" before a program similarly to how you would run "[[sudo]]", and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a File to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory]] (Like shown) or you can provide a file from anywhere in the [[Filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt You will notice that I started describing the file location, I used the tilda sign "~". In linux and some other OS, The Tilda is a faster way to describe the users home folder. It is effectively the same thing as typing the full [[Directory Path|directory path]] except that it is much faster. Here is what it would look like to type the whole directory path nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 4adc159cebe388d71599e7ecc4c68a7c4b687f4e 0 304 1224 1214 2024-10-30T10:28:15Z Atmois 13 Update links wikitext text/x-wiki {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a [[Unix]]-like [[Operating System|operating system]] completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS]</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive [[kernel]], and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[MacOS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[Virtual Machine|virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to [[Compiling|compile]] software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub]</ref> [[Category:Misc Operating Systems]] a8c2c988816cc84713ed02e9508b5f7b23bdb0ae 0 299 1225 1073 2024-10-30T10:28:50Z Atmois 13 Fix spelling of link wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995.<ref name=":0">[[wikipedia:OpenBSD#|OpenBSD - Wikipedia]]</ref> The first version of OpenBSD (1.2) released on July 1996.<ref name=":0" /> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD DistroWatch.com: OpenBSD]</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[XOrg]] build infrastructure.<ref name=":0" /> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] 75359fd7298747e8bfb835e5a753bf19d8e33f82 0 306 1226 1211 2024-10-30T10:29:13Z Atmois 13 Fix spelling of link wikitext text/x-wiki A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|#Stacking/Floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|#Tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|#Dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Terminology]] 59aaa44b8355be1618e255f68b4f4ba819d05528 0 198 1227 1216 2024-10-30T10:29:37Z Atmois 13 Fix spelling of link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] b5cfeacba35ae1f46c83ceca6cbea72a327c8993 4 340 1228 2024-10-30T10:32:52Z Atmois 13 Create contributing info page & meta category wikitext text/x-wiki Info for Contributors [[Category:Meta]] 5a3e47401d566d7e0405616587cb68defd2cab62 1229 1228 2024-10-30T10:33:09Z Atmois 13 Protected "[[Contributing]]": Meta Page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki Info for Contributors [[Category:Meta]] 5a3e47401d566d7e0405616587cb68defd2cab62 1243 1229 2024-11-03T15:57:30Z Atmois 13 Start contributing page draft wikitext text/x-wiki == This is a draft. == == <u>How Contributing Works</u> == Any user can register and submit changes to the wiki, however any changes from new users will require approval from a Wiki Admin [[Category:Meta]] 302749606651c791bd1f9fd03e959bf1754228d9 1249 1243 2024-11-08T11:19:59Z Atmois 13 Added contributing and reporting info wikitext text/x-wiki == This is a draft. == == <u>How Contributing Works</u> == Any user can register and submit changes to the wiki, however any changes from new users will require approval from a Wiki Admin or a Trusted User. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User, there are no formal requirements for becoming Trusted but we normally require some history of positive contributions to our or another wiki (E.g: You are an active contributor for the Arch Wiki) or a positive history within the Discord server or the FOSS community. If you do not have discord/wish to request the role another way you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]] however replies will typically be slower than via discord. == <u>Reporting</u> == If you see a malicious edit/vandalism you can contact us via the methods in the [[Contributing#Contacts|Contacts Section]] (Discord Preffered) with the link to the page/user/edit in question and we will tackle it as soon as possible! If you are a Trusted User you may set the "Authorised" revision to the previous one but do note other Trusted Users can override this. Always if possible avoid edit wars and contact an Admin who can mitigate the situatiom apropiately. == '''<u>Contacts</u>''' == '''Our Discord Server (Preffered) ~ In the Wiki-Public Channel:''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com [[Category:Meta]] 01b23e0ee68396bf5eaa42063b961fdda9dae62e 1250 1249 2024-11-08T14:39:26Z Atmois 13 Update contacts info wikitext text/x-wiki == This is a draft. == == <u>How Contributing Works</u> == Any user can register and submit changes to the wiki, however any changes from new users will require approval from a Wiki Admin or a Trusted User. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User, there are no formal requirements for becoming Trusted but we normally require some history of positive contributions to our or another wiki (E.g: You are an active contributor for the Arch Wiki) or a positive history within the Discord server or the FOSS community. If you do not have discord/wish to request the role another way you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]] however replies will typically be slower than via discord. == <u>Reporting</u> == If you see a malicious edit/vandalism you can contact us via the methods in the [[Contributing#Contacts|Contacts Section]] (Discord Preffered) with the link to the page/user/edit in question and we will tackle it as soon as possible! If you are a Trusted User you may set the "Authorised" revision to the previous one but do note other Trusted Users can override this. Always if possible avoid edit wars and contact an Admin who can mitigate the situation apropiately. == '''<u>Contacts</u>''' == You can contact the admins in several ways, the best is joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preffered):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] 000b933be14e29cc4cbea03a7ccd3e76839e7424 1251 1250 2024-11-08T15:15:42Z Atmois 13 Add standards section wikitext text/x-wiki == This is a draft. == == <u>How Contributing Works</u> == Any user can register and submit changes to the wiki, however any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User, there are no formal requirements for becoming Trusted but we normally require some history of positive contributions to our or another wiki (E.g: You are an active contributor for the Arch Wiki) or a positive history within the Discord server or the FOSS community. If you do not have discord/wish to request the role another way you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]] however replies will typically be slower than via discord. == <u>Reporting</u> == If you see a malicious edit/vandalism you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preffered) with the link to the page/user/edit in question and we will tackle it as soon as possible! If you are a Trusted User you may set the "Authorised" revision to the previous one but do note other Trusted Users can override this. Always if possible avoid edit wars and contact an Admin who can mitigate the situation apropiately. == <u>Standards</u> == We expect a high standard of our editors so we require the following for all pages unless exemption has been given by an Admin: * Always cite when required (E.g: Quotations, benchmarks, release dates), a good guide is the [[wikipedia:Wikipedia:Citing_sources|Wikipedia Citing Sources Guide]]. * Ensure information is accurate and up to date, this can be done by ensuring you are using the offical sources for information. * Pages should be unbiased, if there has been a controversy on a specific topic make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader only is given the facts. * Ensure that your page is consistant with others in both the formatting and the terminology, e.g. for the x86-64/AMD64/x64 architecture it should always be reffered to by AMD64 as it is its offical name. Further details on this can be seen in the [[Contributing#Formatting]] section. == '''<u>Contacts</u>''' == You can contact the admins in several ways, the best is joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preffered):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] 5f7e0d7a0630eccf14398c6df6b4ee7122c1403b 1255 1251 2024-11-09T10:31:24Z Atmois 13 Add extra info & move some to main page wikitext text/x-wiki == <u>Standards</u> == We expect a high standard of our editors so we require the following for all pages unless exemption has been given by an Admin: * '''Accuracy:''' Ensure information is accurate and up to date, this can be done by ensuring you are using the offical sources for information. Always cite when required (E.g: Quotations, benchmarks, release dates), a good guide is the [[wikipedia:Wikipedia:Citing_sources|Wikipedia Citing Sources Guide]]. * '''Impartiality:''' Pages should be unbiased, if there has been a controversy on a specific topic make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader only is given the facts. E.g: Instead of saying "xyz package is bad," say "xyz package has received criticism for...". * '''Consistancy:''' Ensure that your page is consistant with others in both the formatting and the terminology, e.g. for the x86-64/AMD64/x64 architecture it should always be reffered to by AMD64 as it is its offical name. Further details on this can be seen in the [[Contributing#Formatting]] section. * '''Courtesy:''' If you are doing any major changes to existing pages make sure to ask any active editors of the page or an admin to ensure that it meets our requirements and other editors are in agreement with the changes. Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when neccessary and you update list pages (E.g: [[Linux Distributions]]) when making a new entry. * Categorise page when needed, you can do this by selecting the hamburger menu then the categories button, please also avoid making new categories unless its required. * Don't make a new page unless you can add worthwile content to it. == <u>Formatting</u> == [[Category:Meta]] 0a8bc9cff155c52f159f8a979e2c0cb789292aef 1258 1255 2024-11-09T17:17:52Z Atmois 13 Update formatting wikitext text/x-wiki == Standards == We expect a high standard of our editors so we require the following for all pages unless exemption has been given by an Admin: * '''Accuracy:''' Ensure information is accurate and up to date, this can be done by ensuring you are using the offical sources for information. Always cite when required (E.g: Quotations, benchmarks, release dates), a good guide is the [[wikipedia:Wikipedia:Citing_sources|Wikipedia Citing Sources Guide]]. * '''Impartiality:''' Pages should be unbiased, if there has been a controversy on a specific topic make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader only is given the facts. E.g: Instead of saying "xyz package is bad," say "xyz package has received criticism for...". * '''Consistancy:''' Ensure that your page is consistant with others in both the formatting and the terminology, e.g. for the x86-64/AMD64/x64 architecture it should always be reffered to by AMD64 as it is its offical name. Further details on this can be seen in the [[Contributing#Formatting]] section. * '''Courtesy:''' If you are doing any major changes to existing pages make sure to ask any active editors of the page or an admin to ensure that it meets our requirements and other editors are in agreement with the changes. Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when neccessary and you update list pages (E.g: [[Linux Distributions]]) when making a new entry. * Categorise page when needed, you can do this by selecting the hamburger menu then the categories button, please also avoid making new categories unless its required. * Don't make a new page unless you can add worthwile content to it. == Formatting == [[Category:Meta]] 180e820f289713d579b38e3fcb9c61352f8c2395 10 483 1588 2024-10-30T23:43:08Z starcitizen>Alistair3149 0 Update templatestyles src wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:WikimediaUI-Alert.svg|14px|link=]]</span>This article or section may require a cleanup.</span> <div class="mbox-text">It might not meet the Star Citizen Wiki's [[Star Citizen:Style guide|quality standards]]. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Pages needing cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages needing cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> 532d1e265425e5ef6f23b1ecccd22e18c3464717 0 341 1230 2024-11-01T02:06:46Z Katz 53 Made a base for this page. Will work on throughout time. wikitext text/x-wiki Trinity Desktop Environment is an X11 desktop environment forked from KDE 3.5 in 2010. f002b41ee2c9c0f9c74556e52682659fd864de97 1232 1230 2024-11-01T02:30:59Z Katz 53 added an infobox wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tde-logo.png]] | caption = Trinity Desktop Environment logo | title = Trinity Desktop Environment | releasestatus = Maintained | lastrelease = R14.1.3, 2024-10-27 | languages = C | developers = Trinity Development Team | website = [https://www.trinitydesktop.org/ trinitydesktop.org] }} Trinity Desktop Environment is an X11 desktop environment forked from KDE 3 in 2010. 53d5c62fe387546288e01fc89fb653774c720d93 1234 1232 2024-11-03T12:30:49Z Atmois 13 Add category tag wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tde-logo.png]] | caption = Trinity Desktop Environment logo | title = Trinity Desktop Environment | releasestatus = Maintained | lastrelease = R14.1.3, 2024-10-27 | languages = C | developers = Trinity Development Team | website = [https://www.trinitydesktop.org/ trinitydesktop.org] }} Trinity Desktop Environment is an X11 desktop environment forked from KDE 3 in 2010. [[Category:Desktop Environment]] f8dc522b9f307e79cc91b4e615ea70d09b8f7274 1239 1234 2024-11-03T12:36:30Z Atmois 13 Fix catagory wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tde-logo.png]] | caption = Trinity Desktop Environment logo | title = Trinity Desktop Environment | releasestatus = Maintained | lastrelease = R14.1.3, 2024-10-27 | languages = C | developers = Trinity Development Team | website = [https://www.trinitydesktop.org/ trinitydesktop.org] }} Trinity Desktop Environment is an X11 desktop environment forked from KDE 3 in 2010. [[Category:Desktop Environments]] d0af843b3e18505074007a3ad420ebec302a1458 6 342 1231 2024-11-01T02:11:35Z Katz 53 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1 1233 1200 2024-11-03T12:26:43Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[XFCE]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Meta == * [[Contributing]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Neofetch]] * [[Sudo]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Musl]] * [[Ricing]] * [[Test]] * [[Trinity Desktop Environment]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' cb1403cc9976f5990ffd1621b291ec6e2a8bf744 1237 1233 2024-11-03T12:32:56Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environment == * [[Trinity Desktop Environment]] == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[XFCE]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Key Terms == * [[Ricing]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Meta == * [[Contributing]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Test]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' 01f74b9e76681e25ec1d5167693c50522710eda3 1242 1237 2024-11-03T14:43:12Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Meta == * [[Contributing]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Test]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' d36c0403c5a61d2f952fdbefac2b14dfc1376d6d 1246 1242 2024-11-03T18:00:07Z Atmois 13 Add category tag wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Meta == * [[Contributing]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Main Page]] * [[Test]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] 4d3f889134427421e25f9518ce34fe394b25aa75 1247 1246 2024-11-03T18:09:15Z Tux 1 WikiBot: update directory wikitext text/x-wiki '''''Welcome to the All Things Linux Wiki!''''' This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! Check the server out if you need any support! <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Meta == * [[Contributing]] * [[Main Page]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> '''''please note that there is no official process for contributing yet, only people with a history in the server can contribute, however a new system will be adopted soon enough''''' [[Category:Meta]] fc8b49dbd04c7a43dcc112325bfff950d3c67c62 1252 1247 2024-11-09T09:13:22Z Atmois 13 Update info wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == <u>How Contributing Works</u> == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User.  You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == <u>Reporting</u> == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Meta == * [[Contributing]] * [[Main Page]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''<u>Contacts</u>''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] 10c61658265271a1fcb57bea632bad09c16be925 1253 1252 2024-11-09T09:28:51Z Atmois 13 Add header wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == <u>How Contributing Works</u> == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User.  You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == <u>Reporting</u> == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == <u>Categories</u> == <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Meta == * [[Contributing]] * [[Main Page]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''<u>Contacts</u>''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] 4bdcc9b0ddbf999c64d53341a65976ae5b3779c2 1254 1253 2024-11-09T10:21:20Z Atmois 13 Add link wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == <u>How Contributing Works</u> == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == <u>Reporting</u> == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == <u>Categories</u> == <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Meta == * [[Contributing]] * [[Main Page]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''<u>Contacts</u>''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] 05a511dc8eb705a9f8d3934c420c4c481c42f581 1256 1254 2024-11-09T11:58:48Z Atmois 13 Update formatting wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> == Desktop Environments == * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] == Guides == * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] == Linux Distributions == * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] == Mascots == * [[Konqi]] * [[Larry the Cow]] * [[Tux]] == Meta == * [[Contributing]] * [[Main Page]] == Misc Operating Systems == * [[OpenBSD]] * [[SerenityOS]] == Package Managers == * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] == Software == * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] == Terminology == * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] == Window Managers == * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] == Misc == * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] bf58f34354c1f34599b4252d68f37cbca0728514 1257 1256 2024-11-09T17:16:51Z Tux 1 WikiBot: update directory wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] 230cba80f9189248e1697592ae47eea017b739c3 1266 1257 2024-11-09T20:00:14Z Tux 1 WikiBot: update directory wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Kernel]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] a68940144b9cacbbe114e57bc901f4092ec9c1a6 0 319 1235 1208 2024-11-03T12:31:15Z Atmois 13 Add category tag wikitext text/x-wiki '''Ricing''' is the process of customizing and fine-tuning your [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to achieve a highly personalized look and feel. The term originated from the concept of making aesthetic and functional improvements to a system's interface, similar to the act of modifying cars. Generally '''ricing''' focuses on visual customization, although, performance tweaks can be a part of the process. [[Category:Key Terms]] 0a7006d5118d5adcdc70596d5994db5c3f614e9a 1241 1235 2024-11-03T12:39:18Z Atmois 13 Fix catagory wikitext text/x-wiki '''Ricing''' is the process of customizing and fine-tuning your [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to achieve a highly personalized look and feel. The term originated from the concept of making aesthetic and functional improvements to a system's interface, similar to the act of modifying cars. Generally '''ricing''' focuses on visual customization, although, performance tweaks can be a part of the process. [[Category:Terminology]] 172dd3d76c233ac099d8ece03dd1258e1b5097c3 0 322 1236 1134 2024-11-03T12:31:49Z Atmois 13 Add category tag wikitext text/x-wiki == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on Operating Systems === Linux distributions which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * Sabotage * Morpheus Linux * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against [[glibc]], [[gcompat]], glibmus-hq. can be used to execute them on musl-based distros. === Comparisons between different C library implementations. === {| class="wikitable sortable" |+ ![[Bloat]] comparison !musl !uClibc !dietlibc ![[glibc]] |- !Complete .a set |426k |500k |120k |2.0M † |- !Complete .so set |527k |560k |185k |7.9M † |- !Smallest static C program |1.8k |5k |0.2k |662k |- !Static hello (using printf) |13k |70k |6k |662k |- !Dynamic overhead (min. dirty) |20k |40k |40k |48k |- !Static overhead (min. dirty) |8k |12k |8k |28k |- !Static stdio overhead (min. dirty) |8k |24k |16k |36k |- !Configurable featureset |no |yes |minimal |minimal |- !Behavior on resource exhaustion !musl !uClibc !dietlibc ![[glibc]] |- !Thread-local storage |reports failure |aborts |n/a |aborts |- !SIGEV_THREAD timers |no failure |n/a |n/a |lost overruns |- !pthread_cancel |no failure |aborts |n/a |aborts |- !regcomp and regexec |reports failure |crashes |reports failure |crashes |- !fnmatch |no failure |unknown |no failure |reports failure |- !printf family |no failure |no failure |no failure |reports failure |- !strtol family |no failure |no failure |no failure |no failure |- !Performance comparison !musl !uClibc !dietlibc ![[glibc]] |- !Tiny allocation & free |0.005 |0.004 |0.013 |0.002 |- !Big allocation & free |0.027 |0.018 |0.023 |0.016 |- !Allocation contention, local |0.048 |0.134 |0.393 |0.041 |- !Allocation contention, shared |0.050 |0.132 |0.394 |0.062 |- !Zero-fill (memset) |0.023 |0.048 |0.055 |0.012 |- !String length (strlen) |0.081 |0.098 |0.161 |0.048 |- !Byte search (strchr) |0.142 |0.243 |0.198 |0.028 |- !Substring (strstr) |0.057 |1.273 |1.030 |0.088 |- !Thread creation/joining |0.248 |0.126 |45.761 |0.142 |- !Mutex lock/unlock |0.042 |0.055 |0.785 |0.046 |- !UTF-8 decode buffered |0.073 |0.140 |0.257 |0.351 |- !UTF-8 decode byte-by-byte |0.153 |0.395 |0.236 |0.563 |- !Stdio putc/getc |0.270 |0.808 |7.791 |0.497 |- !Stdio putc/getc unlocked |0.200 |0.282 |0.269 |0.144 |- !Regex compile |0.058 |0.041 |0.014 |0.039 |- !Regex search (a{25}b) |0.188 |0.188 |0.967 |0.137 |- !Self-exec (static linked) |234µs |245µs |272µs |457µs |- !Self-exec (dynamic linked) |446µs |590µs |675µs |864µs |- !ABI and versioning comparison !musl !uClibc !dietlibc ![[glibc]] |- !Stable ABI |yes |no |unofficially |yes |- !LSB-compatible ABI |incomplete |no |no |yes |- !Backwards compatibility |yes |no |unofficially |yes |- !Forwards compatibility |yes |no |unofficially |no |- !Atomic upgrades |yes |no |no |no |- !Symbol versioning |no |no |no |yes |- !Algorithms comparison !musl !uClibc !dietlibc ![[glibc]] |- !Substring search (strstr) |twoway |naive |naive |twoway |- !Regular expressions |dfa |dfa |backtracking |dfa |- !Sorting (qsort) |smoothsort |shellsort |naive quicksort |introsort |- !Allocator (malloc) |musl-native |dlmalloc |diet-native |ptmalloc |- !Features comparison !musl !uClibc !dietlibc ![[glibc]] |- !Conformant printf |yes |yes |no |yes |- !Exact floating point printing |yes |no |no |yes |- !C99 math library |yes |partial |no |yes |- !C11 threads API |yes |no |no |no |- !C11 thread-local storage |yes |yes |no |yes |- !GCC libstdc++ compatibility |yes |yes |no |yes |- !POSIX threads |yes |yes, on most archs |broken |yes |- !POSIX process scheduling |stub |incorrect |no |incorrect |- !POSIX thread priority scheduling |yes |yes |no |yes |- !POSIX localedef |no |no |no |yes |- !Wide character interfaces |yes |yes |minimal |yes |- !Legacy 8-bit codepages |no |yes |minimal |slow, via gconv |- !Legacy CJK encodings |no |no |no |slow, via gconv |- !UTF-8 multibyte |native; 100% conformant |native; nonconformant |dangerously nonconformant |slow, via gconv; nonconformant |- !Iconv character conversions |most major encodings |mainly UTFs |no |the kitchen sink |- !Iconv transliteration extension |no |no |no |yes |- !Openwall-style TCB shadow |yes |no |no |no |- !Sun RPC, NIS |no |yes |yes |yes |- !Zoneinfo (advanced timezones) |yes |no |yes |yes |- !Gmon profiling |no |no |yes |yes |- !Debugging features |no |no |no |yes |- !Various Linux extensions |yes |yes |partial |yes |- !Target architectures comparison !musl !uClibc !dietlibc ![[glibc]] |- !i386 |yes |yes |yes |yes |- !x86_64 |yes |yes |yes |yes |- !x86_64 x32 ABI (ILP32) |experimental |no |no |non-conforming |- !ARM |yes |yes |yes |yes |- !Aarch64 (64-bit ARM) |yes |no |no |yes |- !MIPS |yes |yes |yes |yes |- !SuperH |yes |yes |no |yes |- !Microblaze |yes |partial |no |yes |- !PowerPC (32- and 64-bit) |yes |yes |yes |yes |- !Sparc |no |yes |yes |yes |- !Alpha |no |yes |yes |yes |- !S/390 (32-bit) |no |no |yes |yes |- !S/390x (64-bit) |yes |no |yes |yes |- !OpenRISC 1000 (or1k) |yes |no |no |not upstream |- !Motorola 680x0 (m68k) |yes |yes |no |yes |- !MMU-less microcontrollers |yes, elf/fdpic |yes, bflt |no |no |- !Build environment comparison !musl !uClibc !dietlibc ![[glibc]] |- !Legacy-code-friendly headers |partial |yes |no |yes |- !Lightweight headers |yes |no |yes |no |- !Usable without native toolchain |yes |no |yes |no |- !Respect for C namespace |yes |LFS64 problems |no |LFS64 problems |- !Respect for POSIX namespace |yes |LFS64 problems |no |LFS64 problems |- !Security/hardening comparison !musl !uClibc !dietlibc ![[glibc]] |- !Attention to corner cases |yes |yes |no |too much malloc |- !Safe UTF-8 decoder |yes |yes |no |yes |- !Avoids superlinear big-O's |yes |sometimes |no |yes |- !Stack smashing protection |yes |yes |no |yes |- !Heap corruption detection |yes |no |no |yes |- !Misc. comparisons !musl !uClibc !dietlibc ![[glibc]] |- !License |MIT |LGPL 2.1 |GPL 2 |LGPL 2.1+ w/exceptions |} Official benchmarks <ref>Etalabs [https://www.etalabs.net/compare_libcs.html]https://www.etalabs.net/compare_libcs.html</ref> === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] ==Notes== <references /> [[Category:Software]] 85f5e2c55bc2ed8f57b545f7b59eb28b32b6bf61 1248 1236 2024-11-03T19:31:46Z Xmm 51 Remove benchmarking tests as they aren't really useful to show wikitext text/x-wiki == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on Operating Systems === Linux distributions which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * Sabotage * Morpheus Linux * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against [[glibc]], [[gcompat]], glibmus-hq. can be used to execute them on musl-based distros. === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] [[Category:Software]] cc93abdd6f28dacd13f428cae289c4bc33131951 14 292 1238 1016 2024-11-03T12:36:07Z Atmois 13 Remove redirect wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 14 294 1240 1018 2024-11-03T12:38:59Z Atmois 13 Remove redirect wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 343 1244 2024-11-03T17:10:51Z Atmois 13 Create redirect wikitext text/x-wiki #REDIRECT [[Window Manager]] fb237677cbf09c3add44caece3d874ab59902125 4 327 1245 1196 2024-11-03T17:59:25Z Atmois 13 Remove indexing of testpage wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ 3a42ae0d04301b9cc99ec3cbd8ed215fcf1ba933 1259 1245 2024-11-09T18:17:45Z Atmois 13 Removed protection from "[[Test]]": no need to protect wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ 3a42ae0d04301b9cc99ec3cbd8ed215fcf1ba933 1260 1259 2024-11-09T18:19:09Z Beacrox 56 wikitext text/x-wiki Admin testing page. Bea was here __NOINDEX__ __NONEWSECTIONLINK__ 813694c006d18b1059d6dba9d8097bf38a345925 1261 1260 2024-11-09T18:23:02Z Khrozma 57 wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was here 33d6d99f6cc7db00314fff13cc10455322524da2 1262 1261 2024-11-09T18:24:05Z FarCotton 114 rofl wikitext text/x-wiki Admin testing page. FarCotton woz ‘ere __NOINDEX__ __NONEWSECTIONLINK__ 71bb79529ba0c68d405fc496f8ae8d7ae17a40f2 1263 1262 2024-11-09T18:25:20Z Atmois 13 Reverted edit by [[Special:Contributions/FarCotton|FarCotton]] ([[User talk:FarCotton|talk]]) to last revision by [[User:Khrozma|Khrozma]] wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was here 33d6d99f6cc7db00314fff13cc10455322524da2 0 344 1264 2024-11-09T19:47:48Z Khrozma 57 rough draft for Kernel wikitext text/x-wiki The Kernel is the core part of any operating system, including Linux. It's the fundamental layer between your hardware (like your CPU, memory, and GPU) and the software you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, Etc). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. cb233cfc23626ce24208ede84f0fe79fd721e1b0 1265 1264 2024-11-09T19:50:31Z Khrozma 57 wikitext text/x-wiki The Kernel is the core part of any operating system, including Linux. It's the fundamental layer between your hardware (like your CPU, memory, and GPU) and the software you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, Etc). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. 54b166ad3ad0c75b060243a8a107c6de998c3dfc 0 344 1267 1265 2024-11-09T20:03:16Z Khrozma 57 Added Terminology tag wikitext text/x-wiki The Kernel is the core part of any operating system, including Linux. It's the fundamental layer between your hardware (like your CPU, memory, and GPU) and the software you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, Etc). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. [[Category:Terminology]] fb99e5bc0855265793c3b052bf3534c602eee32a 0 1 1268 1266 2024-11-09T21:00:14Z Tux 1 WikiBot: update directory wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Kernel]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] ce8d3a1f592b02f148b381d1b6d4d4cf375e43c3 1271 1268 2024-11-10T00:00:22Z Tux 1 WikiBot: update directory wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Kernel]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Kernel Module]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] 2814597070fc5c3c3a6c14b06234818ce9e1d742 1278 1271 2024-11-14T14:00:16Z Tux 1 WikiBot: update directory wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Kernel]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Init System]] * [[Kernel Module]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] 8f386288fbb2c80a85e0c71c46e11a20d67ce02f 1281 1278 2024-11-14T19:00:14Z Tux 1 WikiBot: update directory wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] bc83d5e718bcd865bacb28ac5d7029b43207204e 1283 1281 2024-11-15T03:00:15Z Tux 1 WikiBot: update directory wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Init System]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] 90cbcbd79d3ef2834a2bc8a3d561e521a33aa2b8 1291 1283 2024-11-15T05:00:15Z Tux 1 WikiBot: update directory wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] bc83d5e718bcd865bacb28ac5d7029b43207204e 1301 1291 2024-11-15T06:00:16Z Tux 1 WikiBot: update directory wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Glibc]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] a929d8252de7b5fe2702b4ce504774ef2b64957f 1319 1301 2024-11-15T18:23:03Z Electron271 3 No TOC wikitext text/x-wiki == Welcome to the All Things Linux Wiki! == This is the official wiki for the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Glibc]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ f79d4005c5b88c9b393e70b41627ef4a58543032 0 345 1269 2024-11-09T23:32:21Z Khrozma 57 Created page with "Kernel Modules are pieces of code that can be loaded directly into the Kernel at runtime to extend functionality. The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your Distribution, As such, there are some distributions that only provide modules your system needs..." wikitext text/x-wiki Kernel Modules are pieces of code that can be loaded directly into the Kernel at runtime to extend functionality. The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your Distribution, As such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically Older ones benefit the most) at the cost of new devices potentially not working when added. b6a4ec5dfd6815bd79d5f47486a5058cf8195b2f 1270 1269 2024-11-09T23:35:38Z Khrozma 57 Added Kernel module rough draft. wikitext text/x-wiki Kernel Modules are pieces of code that can be loaded directly into the Kernel at runtime to extend functionality. The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your Distribution, As such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically Older ones benefit the most) at the cost of new devices potentially not working when added. It is also possible to compile a Linux kernel on a pre-existing system to only use needed Kernel modules. 29bb9fe3159c859c63efdfe783400dc885daf035 1280 1270 2024-11-14T18:39:47Z Imnotpolar 112 Added Kernel Modules to the Terminology category and linked some mentioned terms to their respective pages wikitext text/x-wiki Kernel Modules are pieces of code that can be loaded directly into the [[Kernel]] at runtime to extend functionality. The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your [[Linux Distributions|Distribution]], as such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically older ones benefit the most) at the cost of new devices potentially not working when added. It is also possible to compile a Linux kernel on a pre-existing system to only use needed Kernel modules. [[Category:Terminology]] 29402c85e728a831f0ed25d837f4180a19026a23 2 325 1275 1180 2024-11-14T00:06:23Z Katz 53 Replaced content with "not a myth, and definitely not the legend, but simply a man who tries to work hard. ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠠⢢⠳⠱⠙⠶⠒⠀⠀⠀⠀⠐⠶⠇⢶⣳⡀⠀ ⠀⢠⢐⣭⠀⠀⠠⣆⣵⣾⣴⢺⢷⣦⠀⠀⠈⢺⡋⠀ ⠀⠘⠻⣯⣄⡴⠛⢉⡭⢋⡠⡢⢩⡉⠛⣦⣼⣛⠍⠀ ⠀⠀⠈⠳⠋⠀⠀⢀⠀⠓⠣⠀⠐⢇⠀⠘⡐⠈⠀⠀ ⠀⠀⠀⠀⢌⠀⠤⠀⠀⡀⠐⢀⡂⠀⠘⠈⠈⠀⠀⠀ ⠀⠀⠀⠀..." wikitext text/x-wiki not a myth, and definitely not the legend, but simply a man who tries to work hard. ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠠⢢⠳⠱⠙⠶⠒⠀⠀⠀⠀⠐⠶⠇⢶⣳⡀⠀ ⠀⢠⢐⣭⠀⠀⠠⣆⣵⣾⣴⢺⢷⣦⠀⠀⠈⢺⡋⠀ ⠀⠘⠻⣯⣄⡴⠛⢉⡭⢋⡠⡢⢩⡉⠛⣦⣼⣛⠍⠀ ⠀⠀⠈⠳⠋⠀⠀⢀⠀⠓⠣⠀⠐⢇⠀⠘⡐⠈⠀⠀ ⠀⠀⠀⠀⢌⠀⠤⠀⠀⡀⠐⢀⡂⠀⠘⠈⠈⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠈⢂⡀⠀⠂⠀⠀⣐⡊⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠈⠀⠀⠀⠀⠀⠠⠤⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⡁⡢⢄⠁⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠁⠉⠀⠀⠀⠀⠀⠀⠀⠀ 18493d0eca787bbc643e15c86c8d4f3fbd2d75b9 1276 1275 2024-11-14T00:07:03Z Katz 53 wikitext text/x-wiki not a myth, and definitely not the legend, but simply a man who tries to work hard. ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⡠⡐⢦⣝⡲⣴⠢⣾⢥⡢⠄⠤⠀⠀⠀⠀⠀⠀⠀⠀⠠⠄⢠⣴⡦⢻⠴⣮⣧⣢⡀⠀⠀⠀ ⠀⠀⠀⠀⠠⢊⢐⣍⢎⠅⠂⠈⠉⠁⠀⠀⠉⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠀⠀⠈⠒⠁⡽⣸⣿⠜⡄⠀⠀ ⠀⠀⠀⢠⠁⡊⣜⢿⠀⠀⠀⠀⠀⠀⡠⠐⢈⣩⢫⡵⡦⣀⣴⣶⢴⣦⡄⡀⠀⠀⠀⠀⠀⢱⢓⣿⠷⢄⠀⠀ ⠀⠀⠀⠈⡐⠗⡷⡇⠀⠀⠀⠀⢀⣢⢜⣷⣿⣿⣿⣿⡿⡿⣝⣟⡿⣻⣿⣿⡢⡀⠀⠀⠀⢨⢚⣺⢿⡹⠀⠀ ⠀⠀⠀⠀⢲⢝⣫⡤⡀⠀⢀⣴⡻⡼⠿⠛⠉⠉⡉⠋⠉⠰⢵⡬⡟⠉⡚⠛⠷⣶⡄⣀⣀⣨⣽⣿⡃⡂⠀⠀ ⠀⠀⠀⠘⢕⠱⣾⡻⣾⣽⣾⠟⠁⠀⠀⢠⡊⠟⢁⠀⢀⠀⡄⠚⠁⡞⠈⡆⠀⠈⢾⣛⣿⡻⣫⠎⡚⠀⠀⠀ ⠀⠀⠀⠀⠈⠋⠮⣽⢑⡳⡜⠀⠀⠀⠀⠁⠃⠀⣶⢲⡶⠀⠀⠀⠀⢶⣲⠇⠀⠀⠈⢞⣻⠌⠌⠉⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠈⠒⠨⢥⠁⠀⠀⠀⠀⢐⠀⠀⠈⠁⠀⠈⠀⠀⠀⠀⠫⠣⡀⠀⠀⠈⢆⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠆⠁⠂⠀⠀⠀⠀⠠⡐⠀⢄⠀⠀⠹⣀⢁⠒⠐⠂⠃⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠠⢊⢠⠔⠔⠊⢡⠀⠀⠀⠀⠀⠀⠀⠛⠀⠶⣀⠈⠐⠀⠀⠀⡆⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠈⠀⠀⠨⠀⠀⠈⡄⠀⠀⠀⠀⠈⢄⠀⠀⠀⠁⠀⠀⣠⠴⠊⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡀⠀⠀⠈⠂⢀⠀⠀⠀⠀⠢⡀⠀⣀⢀⣀⣀⡈⠄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠡⠀⠀⠀⠸⠁⡀⠀⠀⠀⡀⠀⢁⡁⣀⠀⠀⠆⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠡⡀⠀⠀⠀⠜⠄⡄⠀⠀⠐⠋⡛⢙⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⡀⠆⠀⠈⠑⡁⠣⡀⠀⢀⢄⠃⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠀⠘⣅⢨⡐⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠐⠊⠨⠡⠠⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ 8b6ea9b6294c87be1fa89e7adccfca8db43dd10a 0 349 1277 2024-11-14T13:55:32Z Rayk4z1 62 Created page with "In Unix-based Operating systems, including [[Linux]], an '''Init''' system is required to enable optimal use of a OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from..." wikitext text/x-wiki In Unix-based Operating systems, including [[Linux]], an '''Init''' system is required to enable optimal use of a OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor''' <ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref>of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in a operating system is to maintain functionality throughout the system, in a Unix-based Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different groups of Inits, depending on the functionality of an Init determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS).''' Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware. <references /> e6b0e552add05b5ca1e992f832d0f15b44372528 1279 1277 2024-11-14T18:33:50Z Imnotpolar 112 Added Init System to the Terminology category wikitext text/x-wiki In Unix-based Operating systems, including [[Linux]], an '''Init''' system is required to enable optimal use of a OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor''' <ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref>of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in a operating system is to maintain functionality throughout the system, in a Unix-based Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different groups of Inits, depending on the functionality of an Init determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS).''' Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware. <references /> [[Category:Terminology]] f065efbf6d020adc1e258387ac195dd2b9b29755 1282 1279 2024-11-15T02:52:23Z Rayk4z1 62 Added information about the disadvantages of using traditional Init systems within newer operating systems with a rebate to other applications where a traditional init maybe necessary. Added A table showcasing 3 Operating systems that featured traditional inits. wikitext text/x-wiki In Unix-based Operating systems, including '''[[Linux]]''', an '''Init''' system is required to enable optimal use of a OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor''' <ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref>of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in a operating system is to maintain functionality throughout the system, in a Unix-based Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>:As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} <references /> 2a4b483ac2b1b468e767f14c6273f18c0de6913c 1290 1282 2024-11-15T04:12:59Z Imnotpolar 112 Re-add category and fix missing space wikitext text/x-wiki In Unix-based Operating systems, including '''[[Linux]]''', an '''Init''' system is required to enable optimal use of a OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor''' <ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref>of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in a operating system is to maintain functionality throughout the system, in a Unix-based Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} <references /> [[Category:Terminology]] a62f94a9d6a6068127edfd50df084db2a97d042c 1317 1290 2024-11-15T16:30:38Z Rayk4z1 62 Finished Non-table sections of MIS and began table for Init systems wikitext text/x-wiki In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is required to enable optimal use of a OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor''' <ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref>of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in a operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, ect. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS.<references /> [[Category:Terminology]] 6fb5233f3ec94b0b94067a7586c1dfac8fa48fa0 1 350 1284 2024-11-15T03:00:27Z Xmm 51 /* Unix-based should be Unix-like */ new section wikitext text/x-wiki == Unix-based should be Unix-like == This is because Unix-based would have implied that any future operating system after UNIX would be based on the original source code Unix-like operating systems are not based on it but rather take some principles. [[User:Xmm|~ xmm16 -- Privacy matters.]] ([[User talk:Xmm|talk]]) 03:00, 15 November 2024 (UTC) 6c3780bed32f8704c3ace76a8bbd3e545282d5fa 1 351 1285 2024-11-15T03:04:40Z Xmm 51 Amount of modules don't affect runtime performance wikitext text/x-wiki == Amount of modules don't affect runtime performance == The kernel runtime performance will ''always'' be the same, the only change is the availability of hardware and features. The only benefit of less kernel modules are smaller kernel images. [[User:Xmm|~ xmm16 -- Privacy matters.]] ([[User talk:Xmm|talk]]) 03:04, 15 November 2024 (UTC) e1fc171a34231fe1729a54fc9007a427deec8869 1286 1285 2024-11-15T03:05:26Z Xmm 51 Amount of modules don't affect runtime performance wikitext text/x-wiki == Amount of modules doesn't affect runtime performance == The kernel runtime performance will ''always'' be the same, the only change is the availability of hardware and features. The only benefit of less kernel modules are smaller kernel images. [[User:Xmm|~ xmm16 -- Privacy matters.]] ([[User talk:Xmm|talk]]) 03:04, 15 November 2024 (UTC) 737fde667351200684afe2858143bfe9e935a4f6 2 352 1287 2024-11-15T03:15:09Z Xmm 51 Biography wikitext text/x-wiki Security researcher from South America, I am 19 years old, I love anything related to UNIX and Unix-like operating systems, I advocate privacy and oh! I love cats. e009b5c15e92dc54b6cb58707249dcd77453a885 1289 1287 2024-11-15T04:08:14Z Xmm 51 wikitext text/x-wiki Security researcher from South America, I am 19 years old, I love anything related to UNIX and Unix-like operating systems, I advocate privacy and oh! I love cats. - Everything happens for a reason, sometimes the reason is that you're stupid and make bad decisions e40dc066d70f6ea447e8da7c18e3ab38431e596b 3 353 1288 2024-11-15T03:22:11Z Xmm 51 Public messages wikitext text/x-wiki == Public Messages for XMM16 == Feel free to leave any message in case you have questions or anything, you can also contact me at Discord! My user is @xmm16. c9cc55eec6f889ded762abb45d1e73e39a5e82f6 0 354 1292 2024-11-15T05:00:38Z Katz 53 base page created wikitext text/x-wiki '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. 88028135df53a3c646bf76cf664441a965eaeeee 1293 1292 2024-11-15T05:04:27Z Katz 53 wikitext text/x-wiki {{LarryInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. 6c7cef9d9c3ceb75f1a6f74a6ec872453db71cea 1294 1293 2024-11-15T05:08:08Z Katz 53 fixed huge puffy wikitext text/x-wiki {{LarryInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy|222px]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. ee977ed650a6ce8ff5b3024ff0626e74b0e3ba4b 1296 1294 2024-11-15T05:34:35Z Katz 53 wikitext text/x-wiki {{LarryInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy|222px]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. [[Category:Mascots]] 61445da947f5b99cac8c03f5be798c159b51bfb8 0 322 1295 1248 2024-11-15T05:30:35Z Xmm 51 Typography errors. wikitext text/x-wiki == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on Operating Systems === Linux distributions which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * Sabotage * Morpheus Linux * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against [[glibc]]. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] [[Category:Software]] 4c5af83e060dfca8f2e0bb6edcff41d6c296ddd7 0 355 1297 2024-11-15T05:35:14Z Xmm 51 Base wikitext text/x-wiki The '''GNU C Library''', commonly known as '''glibc''', is the GNU Project implementation of the C standard library. It provides a wrapper around the system calls of the Linux kernel and other kernels for application use. Despite its name, it now also directly supports C++ (and, indirectly, other programming languages). It was started in the 1980s by the Free Software Foundation (FSF) for the GNU operating system. e50bb469a2298e498c4e8c129aea28d64de40279 6 356 1298 2024-11-15T05:45:23Z Rayk4z1 62 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 828 207 1299 506 2024-11-15T05:45:31Z Xmm 51 Remove automatic adding of Larry the cow under the InfoBox, said thing should be manually done. Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end return retval end return p a765ed2f359127e25b0baa33db64c34ebd521c48 0 317 1300 1164 2024-11-15T05:46:27Z Seo 46 removed user-made install guide, linked to official source instead wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} [[File:Voidlinux-by-dnv.png|alt=A screenshot of a Void Linux dark mode setup|thumb|Void Linux setup running DWM.]] '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. ==Installation== A guide to installing Void Linux, among other useful information, is located on [https://docs.voidlinux.org/installation/index.html the documentation page]. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] 557020743ae2a9e7f157eaed3208e85f49546b99 1318 1300 2024-11-15T16:33:18Z Seo 46 fixed wording wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} [[File:Voidlinux-by-dnv.png|alt=A screenshot of a Void Linux dark mode setup|thumb|Void Linux setup running DWM.]] '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for numerous architectures and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. A guide to installing Void Linux, along with other useful information, is located on [https://docs.voidlinux.org/installation/index.html the documentation page]. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] 36684f7f0105f4168f90d1ff7ca3ac0f0c6754ca 8 357 1302 2024-11-15T06:20:26Z Tux 1 Created page with "/* All CSS here will be loaded for users of the Citizen skin */ :root { --color-surface-0: #11111B; }" css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root { --color-surface-0: #11111B; } ae1d6e509161a05e93959bcfd23ce63088e79aef 1303 1302 2024-11-15T06:34:43Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root { --color-surface-2: #11111B; } 89a1529fed51907db63816a33fb4ac35fa877a82 1304 1303 2024-11-15T06:35:18Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ e773629765c4869b54174dcdd1f09cf0ce7ab064 1305 1304 2024-11-15T07:50:19Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-dark { --color-surface-0: #1A1C28; } df88df399e65f548b92e1eff11124fcca23bdf57 1306 1305 2024-11-15T07:50:49Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-dark { --color-surface-0: #fff; } 5586f79ee5caa468b08f6310350c4b7a0ab136de 1307 1306 2024-11-15T07:52:02Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-auto { --color-surface-0: #fff; } 47dfc75e7da125f4f1d40a5c422b1373dca58f7c 1308 1307 2024-11-15T07:55:13Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-auto { --color-surface-0: #fff; } :root.skin-theme-clientpref-dark { --color-surface-0: #fff; } :root.skin-theme-clientpref-light { --color-surface-0: #fff; } 233d639d19fa35ecf435a9457df536923b87b36a 1309 1308 2024-11-15T07:58:31Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-os { --color-surface-0: #fff; } :root.skin-theme-clientpref-dark { --color-surface-0: #fff; } :root.skin-theme-clientpref-light { --color-surface-0: #fff; } e2a0849020cb04cfa3162facbfd2ec19e4d3ba3c 1310 1309 2024-11-15T07:59:41Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-os { --color-surface-0: #1A1B26; } :root.skin-theme-clientpref-dark { --color-surface-0: #1A1B26; } 20e2217aedd9c33cbad73a2052888de9c2ccce5d 1311 1310 2024-11-15T08:02:48Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-os:not(.citizen-feature-pure-black-clientpref-1), :root.skin-theme-clientpref-dark { --color-surface-0: #1A1B26; } f4ecc464e0e1aa05dae49586ab1010110a797f21 1312 1311 2024-11-15T08:03:57Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ /*:root.skin-theme-clientpref-os:not(.citizen-feature-pure-black-clientpref-1),*/ /*:root.skin-theme-clientpref-dark {*/ /* --color-surface-0: #1A1B26;*/ /*}*/ 62a8b886eaf1afd4cfbd85dd4be4d6e8cc9d68f1 1313 1312 2024-11-15T08:04:14Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-os:not(.citizen-feature-pure-black-clientpref-1), :root.skin-theme-clientpref-dark { --color-surface-0: #1A1B26; } f4ecc464e0e1aa05dae49586ab1010110a797f21 1314 1313 2024-11-15T08:08:59Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-dark:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } 9a2981309d9065406fbbe11a2cf5b68f0b7824b9 1315 1314 2024-11-15T08:13:32Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-dark:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } :root.skin-theme-clientpref-os:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } 96dbb3ec5b10be0721f71e3c77ef222852c7f6f5 1316 1315 2024-11-15T08:15:10Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } :root.skin-theme-clientpref-os:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } cdd2397e63b093855c12734f65952d071725d728 0 1 1321 1319 2024-11-15T18:24:48Z Electron271 3 add template wikitext text/x-wiki {{Main page/header}} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Glibc]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 50ae3750e379ad155197a227b92c7e0917eb00b1 1322 1321 2024-11-15T18:25:58Z Electron271 3 add improved header wikitext text/x-wiki {{Main Page/Header}} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Glibc]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 21161efca6fd939a045903ae96eed5497c79e954 1357 1322 2024-11-15T20:08:16Z Electron271 3 test wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Mediawiki |page2 = Is |page3 = So |page4 = Annoying |page5 = Test }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Glibc]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 956cc437295ad379c8d645dc397e3fffe8d7088a 1358 1357 2024-11-15T20:13:29Z Electron271 3 Add navpills wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Managers |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Misc |image11 = MiscATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Glibc]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 2e7191630d58df337dd3a184adc6decf0726796e 1368 1358 2024-11-15T22:00:15Z Tux 1 WikiBot: update directory wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Managers |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Misc |image11 = MiscATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Glibc]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 49fc27b26170afb0b1ecbcf2ebc1e18accd3e2c8 1369 1368 2024-11-15T22:06:36Z Electron271 3 quick test wikitext text/x-wiki {{Main Page/Header}} {{Navpills |text1 = Desktop Environments |page1 = "Category:Desktop_Environments" |image1 = Dewms.png |text2 = Window Managers |page2 = "Category:Window_Managers" |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Misc |image11 = MiscATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Glibc]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ a622687fb1f2cc4969d09971bc1f9b750c8ecb7c 1371 1369 2024-11-15T22:07:16Z Electron271 3 wikitext text/x-wiki {{Main Page/Header}} {{Navpills |text1 = Desktop Environments |page1 = Category:Desktop_Environments |image1 = Dewms.png |text2 = Window Managers |page2 = Category:Window_Managers |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Misc |image11 = MiscATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Glibc]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ cd2a2b41231c62a3041ea1fc00f5a0bb477befdd 1372 1371 2024-11-15T22:12:01Z Electron271 3 wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop_Environments |image1 = Dewms.png |page2 = Window_Managers |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Misc |image11 = MiscATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Glibc]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 18083743afc0134592dfc250cac7576ac52e9313 1373 1372 2024-11-15T22:12:17Z Electron271 3 wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Managers |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Misc |image11 = MiscATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Glibc]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 49fc27b26170afb0b1ecbcf2ebc1e18accd3e2c8 1388 1373 2024-11-15T22:18:55Z Electron271 3 wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Managers |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == Categories == <!-- beginwikibot --> === Desktop Environments === * [[Budgie]] * [[Cinnamon]] * [[GNOME]] * [[Plasma]] * [[Trinity Desktop Environment]] * [[XFCE]] === Guides === * [[Choosing a Linux Distribution]] * [[Common Issues and Troubleshooting]] * [[External Resources]] * [[Libreboot]] * [[Linux on Apple Macintosh Devices]] * [[Linux on Older Devices]] * [[Migrating between Operating Systems]] === Linux Distributions === * [[Alpine Linux]] * [[Arch Linux]] * [[Debian]] * [[Fedora]] * [[Gentoo]] * [[Linux Distributions]] * [[NixOS]] * [[OpenSUSE]] * [[Red Hat Enterprise Linux]] * [[Rocky Linux]] * [[Slackware]] * [[Ubuntu]] * [[Void Linux]] === Mascots === * [[Konqi]] * [[Larry the Cow]] * [[Puffy]] * [[Tux]] === Meta === * [[Contributing]] * [[Main Page]] === Misc Operating Systems === * [[OpenBSD]] * [[SerenityOS]] === Package Managers === * [[APT]] * [[DNF]] * [[DPKG]] * [[Pacman]] * [[Portage]] === Software === * [[Fastfetch]] * [[Glibc]] * [[Hyfetch]] * [[Musl]] * [[Neofetch]] * [[Sudo]] === Terminology === * [[Arch User Repository]] * [[Bloat]] * [[Bootloader]] * [[Command]] * [[Display Manager]] * [[Distrohopping]] * [[FOSS / FLOSS]] * [[Init System]] * [[Kernel]] * [[Kernel Module]] * [[Key Terms]] * [[Linux]] * [[Multi-booting]] * [[Package Manager]] * [[Ricing]] * [[TUI]] * [[Window Manager]] === Window Managers === * [[DWM]] * [[Hyprland]] * [[I3]] * [[IceWM]] * [[Window Maker]] === Misc === * [[Artificial Intelligence on Linux]] * [[Test]] <!-- endwikibot --> == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 1fc99f8e6c70571a92666129d51d84d6070d3f9a 1396 1388 2024-11-15T22:37:42Z Tux 1 Remove WikiBot wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Managers |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorised" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 65dd6dcca38b1d38696d940fe74403b109788085 828 359 1324 1323 2024-11-15T18:30:48Z Electron271 3 1 revision imported Scribunto text/plain -- This module provides easy processing of arguments passed to Scribunto from -- #invoke. It is intended for use by other Lua modules, and should not be -- called from #invoke directly. local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local arguments = {} -- Generate four different tidyVal functions, so that we don't have to check the -- options every time we call it. local function tidyValDefault(key, val) if type(val) == 'string' then val = val:match('^%s*(.-)%s*$') if val == '' then return nil else return val end else return val end end local function tidyValTrimOnly(key, val) if type(val) == 'string' then return val:match('^%s*(.-)%s*$') else return val end end local function tidyValRemoveBlanksOnly(key, val) if type(val) == 'string' then if val:find('%S') then return val else return nil end else return val end end local function tidyValNoChange(key, val) return val end local function matchesTitle(given, title) local tp = type( given ) return (tp == 'string' or tp == 'number') and mw.title.new( given ).prefixedText == title end local translate_mt = { __index = function(t, k) return k end } function arguments.getArgs(frame, options) checkType('getArgs', 1, frame, 'table', true) checkType('getArgs', 2, options, 'table', true) frame = frame or {} options = options or {} --[[ -- Set up argument translation. --]] options.translate = options.translate or {} if getmetatable(options.translate) == nil then setmetatable(options.translate, translate_mt) end if options.backtranslate == nil then options.backtranslate = {} for k,v in pairs(options.translate) do options.backtranslate[v] = k end end if options.backtranslate and getmetatable(options.backtranslate) == nil then setmetatable(options.backtranslate, { __index = function(t, k) if options.translate[k] ~= k then return nil else return k end end }) end --[[ -- Get the argument tables. If we were passed a valid frame object, get the -- frame arguments (fargs) and the parent frame arguments (pargs), depending -- on the options set and on the parent frame's availability. If we weren't -- passed a valid frame object, we are being called from another Lua module -- or from the debug console, so assume that we were passed a table of args -- directly, and assign it to a new variable (luaArgs). --]] local fargs, pargs, luaArgs if type(frame.args) == 'table' and type(frame.getParent) == 'function' then if options.wrappers then --[[ -- The wrappers option makes Module:Arguments look up arguments in -- either the frame argument table or the parent argument table, but -- not both. This means that users can use either the #invoke syntax -- or a wrapper template without the loss of performance associated -- with looking arguments up in both the frame and the parent frame. -- Module:Arguments will look up arguments in the parent frame -- if it finds the parent frame's title in options.wrapper; -- otherwise it will look up arguments in the frame object passed -- to getArgs. --]] local parent = frame:getParent() if not parent then fargs = frame.args else local title = parent:getTitle():gsub('/sandbox$', '') local found = false if matchesTitle(options.wrappers, title) then found = true elseif type(options.wrappers) == 'table' then for _,v in pairs(options.wrappers) do if matchesTitle(v, title) then found = true break end end end -- We test for false specifically here so that nil (the default) acts like true. if found or options.frameOnly == false then pargs = parent.args end if not found or options.parentOnly == false then fargs = frame.args end end else -- options.wrapper isn't set, so check the other options. if not options.parentOnly then fargs = frame.args end if not options.frameOnly then local parent = frame:getParent() pargs = parent and parent.args or nil end end if options.parentFirst then fargs, pargs = pargs, fargs end else luaArgs = frame end -- Set the order of precedence of the argument tables. If the variables are -- nil, nothing will be added to the table, which is how we avoid clashes -- between the frame/parent args and the Lua args. local argTables = {fargs} argTables[#argTables + 1] = pargs argTables[#argTables + 1] = luaArgs --[[ -- Generate the tidyVal function. If it has been specified by the user, we -- use that; if not, we choose one of four functions depending on the -- options chosen. This is so that we don't have to call the options table -- every time the function is called. --]] local tidyVal = options.valueFunc if tidyVal then if type(tidyVal) ~= 'function' then error( "bad value assigned to option 'valueFunc'" .. '(function expected, got ' .. type(tidyVal) .. ')', 2 ) end elseif options.trim ~= false then if options.removeBlanks ~= false then tidyVal = tidyValDefault else tidyVal = tidyValTrimOnly end else if options.removeBlanks ~= false then tidyVal = tidyValRemoveBlanksOnly else tidyVal = tidyValNoChange end end --[[ -- Set up the args, metaArgs and nilArgs tables. args will be the one -- accessed from functions, and metaArgs will hold the actual arguments. Nil -- arguments are memoized in nilArgs, and the metatable connects all of them -- together. --]] local args, metaArgs, nilArgs, metatable = {}, {}, {}, {} setmetatable(args, metatable) local function mergeArgs(tables) --[[ -- Accepts multiple tables as input and merges their keys and values -- into one table. If a value is already present it is not overwritten; -- tables listed earlier have precedence. We are also memoizing nil -- values, which can be overwritten if they are 's' (soft). --]] for _, t in ipairs(tables) do for key, val in pairs(t) do if metaArgs[key] == nil and nilArgs[key] ~= 'h' then local tidiedVal = tidyVal(key, val) if tidiedVal == nil then nilArgs[key] = 's' else metaArgs[key] = tidiedVal end end end end end --[[ -- Define metatable behaviour. Arguments are memoized in the metaArgs table, -- and are only fetched from the argument tables once. Fetching arguments -- from the argument tables is the most resource-intensive step in this -- module, so we try and avoid it where possible. For this reason, nil -- arguments are also memoized, in the nilArgs table. Also, we keep a record -- in the metatable of when pairs and ipairs have been called, so we do not -- run pairs and ipairs on the argument tables more than once. We also do -- not run ipairs on fargs and pargs if pairs has already been run, as all -- the arguments will already have been copied over. --]] metatable.__index = function (t, key) --[[ -- Fetches an argument when the args table is indexed. First we check -- to see if the value is memoized, and if not we try and fetch it from -- the argument tables. When we check memoization, we need to check -- metaArgs before nilArgs, as both can be non-nil at the same time. -- If the argument is not present in metaArgs, we also check whether -- pairs has been run yet. If pairs has already been run, we return nil. -- This is because all the arguments will have already been copied into -- metaArgs by the mergeArgs function, meaning that any other arguments -- must be nil. --]] if type(key) == 'string' then key = options.translate[key] end local val = metaArgs[key] if val ~= nil then return val elseif metatable.donePairs or nilArgs[key] then return nil end for _, argTable in ipairs(argTables) do local argTableVal = tidyVal(key, argTable[key]) if argTableVal ~= nil then metaArgs[key] = argTableVal return argTableVal end end nilArgs[key] = 'h' return nil end metatable.__newindex = function (t, key, val) -- This function is called when a module tries to add a new value to the -- args table, or tries to change an existing value. if type(key) == 'string' then key = options.translate[key] end if options.readOnly then error( 'could not write to argument table key "' .. tostring(key) .. '"; the table is read-only', 2 ) elseif options.noOverwrite and args[key] ~= nil then error( 'could not write to argument table key "' .. tostring(key) .. '"; overwriting existing arguments is not permitted', 2 ) elseif val == nil then --[[ -- If the argument is to be overwritten with nil, we need to erase -- the value in metaArgs, so that __index, __pairs and __ipairs do -- not use a previous existing value, if present; and we also need -- to memoize the nil in nilArgs, so that the value isn't looked -- up in the argument tables if it is accessed again. --]] metaArgs[key] = nil nilArgs[key] = 'h' else metaArgs[key] = val end end local function translatenext(invariant) local k, v = next(invariant.t, invariant.k) invariant.k = k if k == nil then return nil elseif type(k) ~= 'string' or not options.backtranslate then return k, v else local backtranslate = options.backtranslate[k] if backtranslate == nil then -- Skip this one. This is a tail call, so this won't cause stack overflow return translatenext(invariant) else return backtranslate, v end end end metatable.__pairs = function () -- Called when pairs is run on the args table. if not metatable.donePairs then mergeArgs(argTables) metatable.donePairs = true end return translatenext, { t = metaArgs } end local function inext(t, i) -- This uses our __index metamethod local v = t[i + 1] if v ~= nil then return i + 1, v end end metatable.__ipairs = function (t) -- Called when ipairs is run on the args table. return inext, t, 0 end return args end return arguments 3134ecce8429b810d445e29eae115e2ae4c36c53 1361 1324 2024-11-15T20:21:27Z Electron271 3 Protected "[[Module:Arguments]]": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) Scribunto text/plain -- This module provides easy processing of arguments passed to Scribunto from -- #invoke. It is intended for use by other Lua modules, and should not be -- called from #invoke directly. local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local arguments = {} -- Generate four different tidyVal functions, so that we don't have to check the -- options every time we call it. local function tidyValDefault(key, val) if type(val) == 'string' then val = val:match('^%s*(.-)%s*$') if val == '' then return nil else return val end else return val end end local function tidyValTrimOnly(key, val) if type(val) == 'string' then return val:match('^%s*(.-)%s*$') else return val end end local function tidyValRemoveBlanksOnly(key, val) if type(val) == 'string' then if val:find('%S') then return val else return nil end else return val end end local function tidyValNoChange(key, val) return val end local function matchesTitle(given, title) local tp = type( given ) return (tp == 'string' or tp == 'number') and mw.title.new( given ).prefixedText == title end local translate_mt = { __index = function(t, k) return k end } function arguments.getArgs(frame, options) checkType('getArgs', 1, frame, 'table', true) checkType('getArgs', 2, options, 'table', true) frame = frame or {} options = options or {} --[[ -- Set up argument translation. --]] options.translate = options.translate or {} if getmetatable(options.translate) == nil then setmetatable(options.translate, translate_mt) end if options.backtranslate == nil then options.backtranslate = {} for k,v in pairs(options.translate) do options.backtranslate[v] = k end end if options.backtranslate and getmetatable(options.backtranslate) == nil then setmetatable(options.backtranslate, { __index = function(t, k) if options.translate[k] ~= k then return nil else return k end end }) end --[[ -- Get the argument tables. If we were passed a valid frame object, get the -- frame arguments (fargs) and the parent frame arguments (pargs), depending -- on the options set and on the parent frame's availability. If we weren't -- passed a valid frame object, we are being called from another Lua module -- or from the debug console, so assume that we were passed a table of args -- directly, and assign it to a new variable (luaArgs). --]] local fargs, pargs, luaArgs if type(frame.args) == 'table' and type(frame.getParent) == 'function' then if options.wrappers then --[[ -- The wrappers option makes Module:Arguments look up arguments in -- either the frame argument table or the parent argument table, but -- not both. This means that users can use either the #invoke syntax -- or a wrapper template without the loss of performance associated -- with looking arguments up in both the frame and the parent frame. -- Module:Arguments will look up arguments in the parent frame -- if it finds the parent frame's title in options.wrapper; -- otherwise it will look up arguments in the frame object passed -- to getArgs. --]] local parent = frame:getParent() if not parent then fargs = frame.args else local title = parent:getTitle():gsub('/sandbox$', '') local found = false if matchesTitle(options.wrappers, title) then found = true elseif type(options.wrappers) == 'table' then for _,v in pairs(options.wrappers) do if matchesTitle(v, title) then found = true break end end end -- We test for false specifically here so that nil (the default) acts like true. if found or options.frameOnly == false then pargs = parent.args end if not found or options.parentOnly == false then fargs = frame.args end end else -- options.wrapper isn't set, so check the other options. if not options.parentOnly then fargs = frame.args end if not options.frameOnly then local parent = frame:getParent() pargs = parent and parent.args or nil end end if options.parentFirst then fargs, pargs = pargs, fargs end else luaArgs = frame end -- Set the order of precedence of the argument tables. If the variables are -- nil, nothing will be added to the table, which is how we avoid clashes -- between the frame/parent args and the Lua args. local argTables = {fargs} argTables[#argTables + 1] = pargs argTables[#argTables + 1] = luaArgs --[[ -- Generate the tidyVal function. If it has been specified by the user, we -- use that; if not, we choose one of four functions depending on the -- options chosen. This is so that we don't have to call the options table -- every time the function is called. --]] local tidyVal = options.valueFunc if tidyVal then if type(tidyVal) ~= 'function' then error( "bad value assigned to option 'valueFunc'" .. '(function expected, got ' .. type(tidyVal) .. ')', 2 ) end elseif options.trim ~= false then if options.removeBlanks ~= false then tidyVal = tidyValDefault else tidyVal = tidyValTrimOnly end else if options.removeBlanks ~= false then tidyVal = tidyValRemoveBlanksOnly else tidyVal = tidyValNoChange end end --[[ -- Set up the args, metaArgs and nilArgs tables. args will be the one -- accessed from functions, and metaArgs will hold the actual arguments. Nil -- arguments are memoized in nilArgs, and the metatable connects all of them -- together. --]] local args, metaArgs, nilArgs, metatable = {}, {}, {}, {} setmetatable(args, metatable) local function mergeArgs(tables) --[[ -- Accepts multiple tables as input and merges their keys and values -- into one table. If a value is already present it is not overwritten; -- tables listed earlier have precedence. We are also memoizing nil -- values, which can be overwritten if they are 's' (soft). --]] for _, t in ipairs(tables) do for key, val in pairs(t) do if metaArgs[key] == nil and nilArgs[key] ~= 'h' then local tidiedVal = tidyVal(key, val) if tidiedVal == nil then nilArgs[key] = 's' else metaArgs[key] = tidiedVal end end end end end --[[ -- Define metatable behaviour. Arguments are memoized in the metaArgs table, -- and are only fetched from the argument tables once. Fetching arguments -- from the argument tables is the most resource-intensive step in this -- module, so we try and avoid it where possible. For this reason, nil -- arguments are also memoized, in the nilArgs table. Also, we keep a record -- in the metatable of when pairs and ipairs have been called, so we do not -- run pairs and ipairs on the argument tables more than once. We also do -- not run ipairs on fargs and pargs if pairs has already been run, as all -- the arguments will already have been copied over. --]] metatable.__index = function (t, key) --[[ -- Fetches an argument when the args table is indexed. First we check -- to see if the value is memoized, and if not we try and fetch it from -- the argument tables. When we check memoization, we need to check -- metaArgs before nilArgs, as both can be non-nil at the same time. -- If the argument is not present in metaArgs, we also check whether -- pairs has been run yet. If pairs has already been run, we return nil. -- This is because all the arguments will have already been copied into -- metaArgs by the mergeArgs function, meaning that any other arguments -- must be nil. --]] if type(key) == 'string' then key = options.translate[key] end local val = metaArgs[key] if val ~= nil then return val elseif metatable.donePairs or nilArgs[key] then return nil end for _, argTable in ipairs(argTables) do local argTableVal = tidyVal(key, argTable[key]) if argTableVal ~= nil then metaArgs[key] = argTableVal return argTableVal end end nilArgs[key] = 'h' return nil end metatable.__newindex = function (t, key, val) -- This function is called when a module tries to add a new value to the -- args table, or tries to change an existing value. if type(key) == 'string' then key = options.translate[key] end if options.readOnly then error( 'could not write to argument table key "' .. tostring(key) .. '"; the table is read-only', 2 ) elseif options.noOverwrite and args[key] ~= nil then error( 'could not write to argument table key "' .. tostring(key) .. '"; overwriting existing arguments is not permitted', 2 ) elseif val == nil then --[[ -- If the argument is to be overwritten with nil, we need to erase -- the value in metaArgs, so that __index, __pairs and __ipairs do -- not use a previous existing value, if present; and we also need -- to memoize the nil in nilArgs, so that the value isn't looked -- up in the argument tables if it is accessed again. --]] metaArgs[key] = nil nilArgs[key] = 'h' else metaArgs[key] = val end end local function translatenext(invariant) local k, v = next(invariant.t, invariant.k) invariant.k = k if k == nil then return nil elseif type(k) ~= 'string' or not options.backtranslate then return k, v else local backtranslate = options.backtranslate[k] if backtranslate == nil then -- Skip this one. This is a tail call, so this won't cause stack overflow return translatenext(invariant) else return backtranslate, v end end end metatable.__pairs = function () -- Called when pairs is run on the args table. if not metatable.donePairs then mergeArgs(argTables) metatable.donePairs = true end return translatenext, { t = metaArgs } end local function inext(t, i) -- This uses our __index metamethod local v = t[i + 1] if v ~= nil then return i + 1, v end end metatable.__ipairs = function (t) -- Called when ipairs is run on the args table. return inext, t, 0 end return args end return arguments 3134ecce8429b810d445e29eae115e2ae4c36c53 828 360 1325 2024-11-15T18:35:42Z Electron271 3 Created page with "Imported from Wikipedia Module licensed under Creative Commons Attribution-ShareAlike 4.0 License" wikitext text/x-wiki Imported from Wikipedia Module licensed under Creative Commons Attribution-ShareAlike 4.0 License 8df8220ece690303ded89a76f48402ba27114c77 6 376 1349 2024-11-15T19:57:01Z Electron271 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 377 1350 2024-11-15T19:57:10Z Electron271 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 378 1351 2024-11-15T19:57:17Z Electron271 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 379 1352 2024-11-15T19:57:24Z Electron271 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 380 1353 2024-11-15T19:58:28Z Electron271 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 381 1354 2024-11-15T19:58:41Z Electron271 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 382 1355 2024-11-15T19:58:52Z Electron271 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 383 1356 2024-11-15T19:59:16Z Electron271 3 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 198 1365 1227 2024-11-15T20:35:41Z Wirable 58 /* Arch Based */ wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization And stability, it ships with its own Cachy Kernel and uses a Calamares installer. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now proprietary<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] 7e6d5fbb79de2674c426d665f8db9efc32cce603 1391 1365 2024-11-15T22:22:58Z Atmois 13 Update info on rhel wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization And stability, it ships with its own Cachy Kernel and uses a Calamares installer. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] bd7c4d08541eb229ccb9f8fda88f53ec194255c1 1 384 1366 2024-11-15T20:45:05Z Electron271 3 /* This page desperately needs citations */ new section wikitext text/x-wiki == This page desperately needs citations == Please add citations and continue to add them in the future [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 20:45, 15 November 2024 (UTC) e3462d9ea541e466cbd2a9ec433e14bd82a03170 0 355 1367 1297 2024-11-15T21:36:10Z Katz 53 added category wikitext text/x-wiki The '''GNU C Library''', commonly known as '''glibc''', is the GNU Project implementation of the C standard library. It provides a wrapper around the system calls of the Linux kernel and other kernels for application use. Despite its name, it now also directly supports C++ (and, indirectly, other programming languages). It was started in the 1980s by the Free Software Foundation (FSF) for the GNU operating system. [[Category:Software]] ae2e6621188fa847a872252f838f165f3395b6ee 14 385 1370 2024-11-15T22:06:36Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Meta" as well as all subcategories of category "Meta" if any exist. 13478b03d426f7a6ed6df32f4ffb2cca9de47deb 0 387 1375 2024-11-15T22:13:35Z Electron271 3 Redirected page to [[Category:Window Managers]] wikitext text/x-wiki #REDIRECT [[Category:Window_Managers]] 6455e268afb34e95082df1cdabbd02b55bf5820c 0 388 1376 2024-11-15T22:14:36Z Electron271 3 Redirected page to [[Category:Guides]] wikitext text/x-wiki #REDIRECT [[Category:Guides]] d410ab4344f17321ec8db76138389deac68d446a 14 389 1377 2024-11-15T22:14:57Z Electron271 3 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 14 390 1378 2024-11-15T22:15:22Z Electron271 3 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 391 1379 2024-11-15T22:15:27Z Electron271 3 Redirected page to [[Category:Mascots]] wikitext text/x-wiki #REDIRECT [[Category:Mascots]] e546235015ac54bd0517b17777eb86b9e7c228bd 0 392 1380 2024-11-15T22:15:39Z Electron271 3 Redirected page to [[Category:Meta]] wikitext text/x-wiki #REDIRECT [[Category:Meta]] be1fb64d7655ef23d875401a2de013b46fbd33de 14 393 1381 2024-11-15T22:16:08Z Electron271 3 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 394 1382 2024-11-15T22:16:12Z Electron271 3 Redirected page to [[Category:Misc Operating Systems]] wikitext text/x-wiki #REDIRECT [[Category:Misc_Operating_Systems]] d95918be2ca9afdf5af54349928b496de2479b58 0 395 1383 2024-11-15T22:16:30Z Electron271 3 Redirected page to [[Category:Package Managers]] wikitext text/x-wiki #REDIRECT [[Category:Package_Managers]] 0624013a3527e747af2c378839d7e1d7b49449bb 0 396 1384 2024-11-15T22:16:44Z Electron271 3 Redirected page to [[Category:Software]] wikitext text/x-wiki #REDIRECT [[Category:Software]] 274869cfa6043c734d970e7edad86805b36e6918 14 397 1385 2024-11-15T22:16:47Z Electron271 3 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 398 1386 2024-11-15T22:17:06Z Electron271 3 Redirected page to [[Category:Terminology]] wikitext text/x-wiki #REDIRECT [[Category:Terminology]] c30cb87e5ef5e6ab1e995ac327302c6758ec95ec 8 400 1389 2024-11-15T22:21:25Z Electron271 3 Created page with "This is the official wiki by the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]!" wikitext text/x-wiki This is the official wiki by the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! 76733b900da5d79ae02d112b1575318af23e4c6b 1390 1389 2024-11-15T22:21:35Z Electron271 3 Protected "[[MediaWiki:Citizen-footer-desc]]": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki This is the official wiki by the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Contributing#Contacts|Contacts Section]]! 76733b900da5d79ae02d112b1575318af23e4c6b 2 401 1392 2024-11-15T22:27:53Z Tux 1 Redirected page to [[Tux]] wikitext text/x-wiki #REDIRECT [[Tux]] e1325b0372fe45591c793f079cb82470ee616274 2 402 1393 2024-11-15T22:29:57Z Tux 1 Created page with "https://www.mediawiki.org/wiki/Extension:AbuseFilter" wikitext text/x-wiki https://www.mediawiki.org/wiki/Extension:AbuseFilter 094ce23f5dfe0c8b725a36d560451f6c21ea4161 2 403 1394 2024-11-15T22:30:25Z Tux 1 Created page with "https://www.mediawiki.org/wiki/Extension:Auto_Create_Category_Pages" wikitext text/x-wiki https://www.mediawiki.org/wiki/Extension:Auto_Create_Category_Pages ce249751a68a287f99d52aa7e49dd3218988fc77 8 404 1397 2024-11-15T22:42:10Z Tux 1 Created page with "🐧" wikitext text/x-wiki 🐧 6762c1dbc8f60755cd5171058fe78416ebf9a7ee 0 176 1398 1189 2024-11-15T23:39:17Z Electron271 3 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.0.5, 2024-05-21 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] b240c3b895c326c93da7c92b88fb797ba7d20a50 0 333 1399 1190 2024-11-15T23:40:08Z Electron271 3 wikitext text/x-wiki #REDIRECT [[Plasma]] [[Category:Desktop Environments]] a8eae6207fe17a9a0db0b6638006cf75d64adb09 0 405 1400 2024-11-15T23:48:03Z Sun 66 Definition of proprietary software. wikitext text/x-wiki Proprietary software is software owned by a company or an organization, which the public can’t view, edit, or redistribute. Examples of proprietary software are Microsoft Windows and Adobe Photoshop. 7c85d00c95e2e71bef5e20b6bfa2c166d408b984 1401 1400 2024-11-16T00:00:12Z Electron271 3 Set Category wikitext text/x-wiki Proprietary software is software owned by a company or an organization, which the public can’t view, edit, or redistribute. Examples of proprietary software are Microsoft Windows and Adobe Photoshop. [[Category:Terminology]] 1f9bbd5ccff9f56a7871ec742112f6158fc506f2 8 357 1402 1316 2024-11-16T02:51:03Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ /*:root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) {*/ /* --color-surface-0: #E1E2E7;*/ /*}*/ /*:root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) {*/ /* --color-surface-0: #11111b;*/ /*}*/ /*:root.skin-theme-clientpref-os:not(.citizen-feature-pure-black-clientpref-1) {*/ /* --color-surface-0: #11111b;*/ /*}*/ 6076186d90b9434fd926d2d929820a99dcf7aa25 8 357 1403 1402 2024-11-16T02:52:33Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } 10c6cb0eee25148523fd4a8beaf18494a2717e32 1404 1403 2024-11-16T03:09:19Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42; --color-primary__l: 76; } d04d10afc501625dce7b4cfd3a7db70e03d965fe 1405 1404 2024-11-16T03:10:41Z Tux 1 css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } 83a9ceb9df7515cf02c3dff4044bf5a19b2b8ef8 0 349 1406 1317 2024-11-16T06:36:42Z Katz 53 fixed the most minor spelling mistake wikitext text/x-wiki In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is required to enable optimal use of a OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor''' <ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref>of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in a operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, etc. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS.<references /> [[Category:Terminology]] ae08df7f4debcf78bc4f1235bd660b774670efbe 1417 1406 2024-11-18T18:22:19Z MymeType 35 Added runit to table of MIS wikitext text/x-wiki In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is required to enable optimal use of a OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor''' <ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref>of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in a operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, etc. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |runit |February 10, 2004 |September 29, 2024 |↓ |Gerrit Pape |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS.<references /> [[Category:Terminology]] 16f101cfcda0925702b19bd6f7a1c138a4d4bece 6 406 1407 2024-11-16T07:12:53Z Wirable 58 wikitext text/x-wiki CachyOS logo used for the duration of 2024+ (January 2024 First Release to 2024 December And after) 0061be0cf7e1ba0603554eac0587f9c1538ec90e 1 407 1408 2024-11-16T12:54:54Z Electron271 3 /* features category */ new section wikitext text/x-wiki == features category == rewrite to talk about plasmas actual features not kde projects other apps [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 12:54, 16 November 2024 (UTC) 7708bb0a1a3723448fef1cf71c46633a2d3c3ac2 1412 1408 2024-11-18T05:25:39Z Electron271 3 /* Citations Needed */ new section wikitext text/x-wiki == features category == rewrite to talk about plasmas actual features not kde projects other apps [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 12:54, 16 November 2024 (UTC) == Citations Needed == citations needed for some of the new categories [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 05:25, 18 November 2024 (UTC) 982df568e3c1ec7aa9b7e6251d2da0f9211f3ef4 0 1 1409 1396 2024-11-16T14:42:26Z Electron271 3 Spelling Error wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Managers |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorized" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 5fbe2cce92d91de7a69fee4355f95596e29eeabd 1433 1409 2024-11-22T21:47:15Z Atmois 13 Fix link wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Contributing#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorized" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 3d5420b9854bced084768b992f9f4ed7da20950d 1450 1433 2024-11-27T16:51:35Z Atmois 13 Fix link wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorized" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.com * tess(at)allthingslinux.com [[Category:Meta]] __NOTOC__ 5e4de350d28956d0899809aa29e5a1d0e7231b43 8 408 1410 2024-11-17T10:25:37Z Atmois 13 Create page for menu editor wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 8 409 1411 2024-11-17T10:48:29Z Atmois 13 Created page with " * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki * SEARCH * TOOLBOX * LANGUAGES" wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki * SEARCH * TOOLBOX * LANGUAGES df7c604d036435a413d00baa4fd183f6a56b1543 1 410 1413 2024-11-18T06:48:40Z Electron271 3 /* Citations Invalid */ new section wikitext text/x-wiki == Citations Invalid == please use direct citations not to wikipedia [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 06:48, 18 November 2024 (UTC) e6ce5e76de44a9e2572e75b37541015676bfbd0a 1415 1413 2024-11-18T18:17:10Z MymeType 35 /* Citations Invalid */ Reply wikitext text/x-wiki == Citations Invalid == please use direct citations not to wikipedia [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 06:48, 18 November 2024 (UTC) :fixed [[User:MymeType|MymeType]] ([[User talk:MymeType|talk]]) 18:17, 18 November 2024 (UTC) 19321799e702955ce4cdb70cf570703b7e71b9b8 1416 1415 2024-11-18T18:19:23Z Electron271 3 fixed wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 299 1414 1225 2024-11-18T16:43:23Z MymeType 35 Updated citations wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released on July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[XOrg]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] bfd83edad5e25f8e50592cb72afb27a073fcbc22 1445 1414 2024-11-26T21:46:00Z MymeType 35 Added OpenBSD under the BSD category wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released on July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[XOrg]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 7044c1bda71d968c104f1ea97ff96cb8064d8d15 6 411 1418 2024-11-19T14:13:39Z Minimum1674 68 wikitext text/x-wiki minimum's terminal, cowsay program, "i love ATL!" 2630b76895d5b2573db89e1a6798fc2689e7a1e4 0 412 1419 2024-11-19T15:56:12Z Minimum1674 68 uhh cowsay creation ig wikitext text/x-wiki {{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-com | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }} '''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. === Available Parameters === {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default || [given parameter] |} === Trivia === * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ 1] d4784a27bbde32857a266ca816c812d1841af0c6 1420 1419 2024-11-19T15:57:56Z Minimum1674 68 quick lil change wikitext text/x-wiki {{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-com | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }} '''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. === Available Parameters === {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default || [given parameter] |} === Trivia === * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ <nowiki>[static archive link here]</nowiki>] 77a26d7fdb0887f93d12ea90489e731897e52be8 1421 1420 2024-11-19T16:04:20Z Minimum1674 68 OH JEEZ THAT WAS A HORRIBLE MISTAKE (changed it btw) wikitext text/x-wiki {{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-org | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }} '''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. === Available Parameters === {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default || [given parameter] |} === Trivia === * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ <nowiki>[static archive link here]</nowiki>] bbfb7a6cd7790a4472c400d74490ecf853c918ed 1428 1421 2024-11-20T13:05:05Z Minimum1674 68 uh yeah more minor edits wikitext text/x-wiki {{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-org | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }} '''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. === Available Parameters === {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default (none unless specified) || [given parameter] |} === Trivia === * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ ^{<nowiki>[1]</nowiki>}] * [[Larry the Cow]] (<code>emerge --moo</code>) and Cowsay share the same ASCII art, [[Debian]]'s Larry ASCII arts don't. fa5b6bf01084111b6798c74c45f7b09846d80def 1429 1428 2024-11-20T14:04:48Z MymeType 35 /* Trivia */ Added xcowsay in trivia section wikitext text/x-wiki {{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-org | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }} '''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. === Available Parameters === {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default (none unless specified) || [given parameter] |} === Trivia === * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ ^{<nowiki>[1]</nowiki>}] * [[Larry the Cow]] (<code>emerge --moo</code>) and Cowsay share the same ASCII art, [[Debian]]'s Larry ASCII arts don't. * There is a graphical version of this program called [https://www.doof.me.uk/xcowsay/ xcowsay]. 8f5cb17c20fb4e1734d58b06bc0c950740b16b4c 4 327 1422 1263 2024-11-19T17:55:43Z Atmois 13 test wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ atmois was here 78d57d78f73e21e8458c0ad32271f057f4829683 1423 1422 2024-11-19T17:58:16Z Atmois 13 Merge edit by [[Special:Contributions/Test|Test]] wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here 6ef8b6c39850299cc1851fc665307e09a51fe96e 1424 1423 2024-11-19T18:22:33Z Test 63 wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here dcb2410517b2a6c524f1b9ec34eafa1ca33ccf50 1425 1424 2024-11-19T18:35:14Z Test 63 wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here testing testing 1 2 3 ae2a47b9cb818dcd6afb479f2e6bd7d61b06151b 1426 1425 2024-11-19T18:37:54Z Test 63 wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here testing testing 1 2 3 4 edc59a2b634fc1739fcb947a7c92c532031ac40d 1435 1426 2024-11-22T22:55:42Z Tux 1 wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen testing testing 1 2 3 4 782a5444ed6dd3eb5d3312b7de46e9fc92cfbb94 1451 1435 2024-11-27T21:52:28Z Atmois 13 test wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen testing testing 1 2 3 4<ref>hi</ref> 2d30c9a23336ff06271ca55439eab240733bcff4 0 415 1438 2024-11-24T01:37:55Z Rayk4z1 62 Began the POSIX Section. wikitext text/x-wiki POSIX, a rewritten name that stands for "Portable Operating System Interface" in replacement for IEEE-IX for the IEEE Computer Society, is a set of standards for upkeeping compatibility across different operating systems as it defines system & user-levels APIs in the addition of utility interfaces and command line shells for portability with Unix, Unix-Based/Like operating systems, and more.<ref>The Linux Code, November 1, 2023, ''POSIX: A Thorough Overview for Linux Developers — https://thelinuxcode.com/posix-standard/''</ref> === Modern Day POSIX Standards === There are many modern-day standards for POSIX, in order for a Unix-Based/Like operating system to POSIX-Compliant, it must provide implementations of the many POSIX APIs. These standards include the ability to use core services and/or processes properly: Core API Services and its processes, threads, signals, basic file I/O, as well as using Shell utilities such as bash and following commands like <code>grep</code> , <code>sort</code>, <code>find</code>, and plenty more. <references /> c0a393cec678b76b189ddbac544a612ee80870dd 2 316 1436 1161 2024-11-24T08:11:05Z Seo 46 edited link to my page wikitext text/x-wiki ====Hi there!==== [https://vnxcn.github.io Website] 60025552ab3b4cae0055b98ac41cb566877488e9 0 414 1437 2024-11-24T08:32:30Z Uli 22 Created page with "C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970's, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at [[Bell Labs]], and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a com..." wikitext text/x-wiki C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970's, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at [[Bell Labs]], and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and preprocessors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include [[GNU GCC]], [[Clang]], TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the [[Clang|Clang compiler toolchain]], however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, musl, GNU libc, mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as [[GNU Autotools]], [[CMake]], [[Meson Build|Meson]], [[Zig|Zig's build toolchain]] among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF), which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FOSS / FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, metaprogramming and structural components of a C codebase; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS / FLOSS|open source]] codebases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995-2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref>, many attribute issues regarding C to fragmentation and portability issues<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref>, lack of type safety and primitive resource access checks<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref>, poor administration on part of the C Language Working Group<ref>https://cor3ntin.github.io/posts/c/</ref>, and overall worsening over time<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref>. efb85a358878b408714f6518bb0fa0f3dd25e6f2 1439 1437 2024-11-24T08:36:44Z Uli 22 incomplete sentence (typo) wikitext text/x-wiki C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970's, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at [[Bell Labs]], and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and preprocessors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include [[GNU GCC]], [[Clang]], TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the [[Clang|Clang compiler toolchain]], however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, musl, GNU libc, mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as [[GNU Autotools]], [[CMake]], [[Meson Build|Meson]], [[Zig|Zig's build toolchain]] among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FOSS / FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, metaprogramming and structural components of a C codebase; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS / FLOSS|open source]] codebases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995-2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref>, many attribute issues regarding C to fragmentation and portability issues<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref>, lack of type safety and primitive resource access checks<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref>, poor administration on part of the C Language Working Group<ref>https://cor3ntin.github.io/posts/c/</ref>, and overall worsening over time<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref>. d5ef52f218e94c3d015aedf538d71446ffda2634 1440 1439 2024-11-24T08:39:43Z Uli 22 add links to existing pages wikitext text/x-wiki C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970's, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at [[Bell Labs]], and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and preprocessors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include [[GNU GCC]], [[Clang]], TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the [[Clang|Clang compiler toolchain]], however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as [[GNU Autotools]], [[CMake]], [[Meson Build|Meson]], [[Zig|Zig's build toolchain]] among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FOSS / FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, metaprogramming and structural components of a C codebase; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS / FLOSS|open source]] codebases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995-2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref>, many attribute issues regarding C to fragmentation and portability issues<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref>, lack of type safety and primitive resource access checks<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref>, poor administration on part of the C Language Working Group<ref>https://cor3ntin.github.io/posts/c/</ref>, and overall worsening over time<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref>. 93e2a2a03fed9b08362708452ae30b167645c68a 6 417 1442 2024-11-26T21:35:12Z MymeType 35 http://www.freebsd.org/ wikitext text/x-wiki == Summary == http://www.freebsd.org/ 241fe969fe6dd5ddd7e152dad90c61bbfa841ce7 0 418 1443 2024-11-26T21:45:02Z MymeType 35 Created FreeBSD page wikitext text/x-wiki {{DistributionInfobox|architectures=arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox|caption=The FreeBSD logo|defaultdesktops=[[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]]|image=[[File:FreeBSD logo.png|200px|FreeBSD_logo]]|packagemanager=pkg|releasemodel=Stable|releasestatus=Maintained|title=FreeBSD|usagetype=Desktop, Firewall, Raspberry Pi, Server|website=[https://freebsd.org freebsd.org]}} FreeBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released on November 1993<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"]. [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref>. [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[device drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a kernel and drivers, and relying on third-parties such as [[GNU]] for system software<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref>. The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref>. The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']}<references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 8622cc9b1fa2478914b3abf40bf04320679311b6 14 419 1444 2024-11-26T21:45:03Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "BSD" as well as all subcategories of category "BSD" if any exist. 2bdafead879b3da59306aac8512de90a8f8c5d05 2 289 1446 1119 2024-11-26T21:47:10Z MymeType 35 Edited todo list wikitext text/x-wiki <syntaxhighlight lang="xml"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <sexuality>Bisexual</sexuality> <os>Gentoo/Windows</os> <extra>Robot/Furry (Axolotl)</extra> <socials>https://linktr.ee/mymetype</socials> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json"> { "atl.wiki":{ "todo":{ "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 625925ee576786e2b3463da1433b260c920095aa 1448 1446 2024-11-26T21:48:35Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml" line="1"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <sexuality>Bisexual</sexuality> <os>Gentoo/Windows</os> <extra>Robot/Furry (Axolotl)</extra> <socials>https://linktr.ee/mymetype</socials> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json" line="1"> { "atl.wiki":{ "todo":{ "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 8a928b47677563b9c7f0ae5a728e7858044ab682 14 420 1447 2024-11-26T21:47:11Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Pages with syntax highlighting errors" as well as all subcategories of category "Pages with syntax highlighting errors" if any exist. 76f57da657baee01a414ff4c0530ae7fb5d8c1d7 8 421 1449 2024-11-27T16:19:50Z Atmois 13 Update footer text wikitext text/x-wiki Content on this site is licensed under $1 unless otherwise specified. 8d4baf6a182eb554fa569592214c7976d11bdd85 4 340 1452 1258 2024-11-27T22:17:21Z Atmois 13 Add info on citations wikitext text/x-wiki == Standards == We expect a high standard of our editors so we require the following for all pages unless exemption has been given by an Admin: * '''Accuracy:''' Ensure information is accurate and up to date, this can be done by ensuring you are using the offical sources for information. * '''Impartiality:''' Pages should be unbiased, if there has been a controversy on a specific topic make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader only is given the facts. E.g: Instead of saying "xyz package is bad," say "xyz package has received criticism for...". * '''Consistancy:''' Ensure that your page is consistant with others in both the formatting and the terminology, e.g. for the x86-64/AMD64/x64 architecture it should always be reffered to by AMD64 as it is its offical name. Further details on this can be seen in the [[Contributing#Formatting]] section. * '''Courtesy:''' If you are doing any major changes to existing pages make sure to ask any active editors of the page or an admin to ensure that it meets our requirements and other editors are in agreement with the changes. Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when neccessary and you update list pages (E.g: [[Linux Distributions]]) when making a new entry. * Categorise pages when needed, you can do this by selecting the hamburger menu then the categories button, avoid making new categories unless its required. * Don't make a new page unless you can add worthwile content to it. == Citations == Always cite the sources of content when it required, this can be because you are referencing other's statements, the release date of a piece of software or for any material that is challanged or is likely to be challenged in particular. If you ever obtain content from another source (Such as taking info from a wiki with a compatible liscense) or quote other locations online ensure you link to it appropiatly. A citation is composed of two components, a inline superscript next to the releavant section of text <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page, this is autogenerated once the page is saved. For the inline citation there is no specific style required as long you state the author, year of publication, the date of retrival & if possible a link to the original source. We reccommend the following structure which is adapted from the Harvard Referencing Style: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g: [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). == Formatting == <references /> [[Category:Meta]] b1fd03198eb9c38f2bb0991de72accbf511f214c 1453 1452 2024-11-28T20:25:37Z Atmois 13 Finish the base of the guidelines wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date, this can be done by ensuring you are using the offical sources or other high quality and reputable sources for information. Please ensure you appropiatly cite your sources following our [[Contributing#Citations]] guidelines. ===== <u>Impartiality</u> ===== Pages should be unbiased, if there has been a controversy on a specific topic make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader only is given the facts. E.g: Instead of saying "xyz package is bad," say "xyz package has received criticism for...". ===== <u>Consistancy</u> ===== Ensure that your page is consistant with others in both the formatting and the terminology, e.g. for the x86-64/AMD64/x64 architecture it should always be reffered to by AMD64 as it is its offical name. Further details on this can be seen in the [[Contributing#Formatting]] section. ===== '''<u>Courtesy</u>''' ===== If you are doing any major changes to existing pages make sure to ask any active editors of the page or an admin to ensure that it meets our requirements and other editors are in agreement with the changes. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when neccessary and you update list pages (E.g: [[Linux Distributions]]) when making a new entry. * Categorise pages when needed, you can do this by selecting the hamburger menu then the categories button, avoid making new categories unless its required. * Don't make a new page unless you can add worthwile content to it. == Citations == Always cite the sources of content when it required, this can be because you are referencing other's statements, the release date of a piece of software or for any material that is challanged or is likely to be challenged in particular. If you ever obtain content from another source (Such as taking info from a wiki with a compatible liscense) or quote other locations online ensure you link to it appropiatly. A citation is composed of two components, a inline superscript next to the releavant section of text <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page, this is autogenerated once the page is saved. For the inline citation there is no specific style required as long you state the author, year of publication, the date of retrival & if possible a link to the original source. We reccommend the following structure which is adapted from the Harvard Referencing Style: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g: [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Sources should be published & reliable and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' depends on context; common sense and editorial judgment are an indispensable part of the process. In general newer sources are better however if an older source is considered more reliable it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. == Formatting == All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistant, e.g. if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required when the name of a company or piece of software uses a specific spelling, e.g. "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]].<references /> [[Category:Meta]] 6ea652a3bc202416d371d6425af1f1b0c3d87bb5 0 274 1454 1222 2024-11-29T19:13:27Z Dainis 31 wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init system]]s. Possible init systems include: * [[dinit]] * [[OpenRC]] * [[runit]] * [[s6]] 05c72e13090099bc8aec9a2b36d4d1caf9d379dd 1455 1454 2024-11-29T19:13:49Z Dainis 31 Dainis moved page [[User:Dainis/Sandbox/Artix Linux]] to [[Artix Linux]] wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init system]]s. Possible init systems include: * [[dinit]] * [[OpenRC]] * [[runit]] * [[s6]] 05c72e13090099bc8aec9a2b36d4d1caf9d379dd 1457 1455 2024-11-29T19:14:13Z Dainis 31 wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''', also known simply as '''Artix''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init system]]s. Possible init systems include: * [[dinit]] * [[OpenRC]] * [[runit]] * [[s6]] c91cd5f80719712dc34f979b72b5216a7a3cdce6 2 422 1456 2024-11-29T19:13:49Z Dainis 31 Dainis moved page [[User:Dainis/Sandbox/Artix Linux]] to [[Artix Linux]] wikitext text/x-wiki #REDIRECT [[Artix Linux]] eb7020c7aceb66cced52640baa3660090fb5022c 0 423 1458 2024-11-29T19:14:50Z Dainis 31 Redirected page to [[Artix Linux]] wikitext text/x-wiki #REDIRECT [[Artix Linux]] eb7020c7aceb66cced52640baa3660090fb5022c 0 198 1459 1391 2024-11-29T19:15:25Z Dainis 31 /* Gentoo Based */ wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization And stability, it ships with its own Cachy Kernel and uses a Calamares installer. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] f6fa7b6e98ae26a80c7b60ff21cee07d2a5be037 1468 1459 2024-12-03T23:18:22Z Katz 53 wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a Calamares installer. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |} [[Category:Linux Distributions]] 6048ae3526e085ad6b2f111a5a99e9f10f052751 1479 1468 2024-12-25T03:58:07Z RealMrCactus 96 Alphabetized the tables. Added a few distributions. wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a Calamares installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 87fd5bac82d8a98c6e28934063bd397043469006 1481 1479 2024-12-28T21:59:41Z Stewarpt 100 Added Linux Mint to Debian Based distros list wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a Calamares installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 662d72abd83ee63ae3a654df4d5e2dde4fc59055 1483 1481 2024-12-29T15:56:14Z Stewarpt 100 Changed desktop environments so it redirects correctly and mentioned chromeos flex in chromeos description wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[XOrg]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments||Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a Calamares installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 8f5247f1dd91721173556dc34211d5442526a29f 0 203 1460 1065 2024-11-29T19:16:09Z Dainis 31 wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [[File:Gentoo Live GUI USB running KDE.png|thumb|Gentoo Live GUI USB running [[KDE Plasma]]]][https://www.gentoo.org/ Gentoo Linux] is a source-based [[Linux Distributions|Linux distribution]], aimed around user customization. This distribution, in addition to having the systemd init system, also provides its own init system known as OpenRC. Unlike other Linux distributions, everything you install is compiled on the local system. As such, users can use compile flags, known as 'USE Flags,' to help them fit their system to their use case.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Their unofficial mascot is [[Larry the Cow]], a cow who was once frustrated at the state of Linux distributions until he found Gentoo Linux.<ref name="about">https://www.gentoo.org/get-started/about/</ref> Gentoo has support for a large variety of hardware and has extremely minimal requirements, which makes it great for most devices. === Portage === [[Portage]] is the package manager for Gentoo Linux, it provides many configuration options based off of Bash, an example <code>make.conf</code> can be found [https://github.com/gentoo/portage/blob/master/cnf/make.conf.example here]. '''Emerge''' is a front-end for Portage and is used to manage the entire system. === Trivia === * You can find Larry the Cow by running <code>emerge --moo</code> on the command line. === Notes === <references /> [[Category:Linux Distributions]] 1cfc96182e6540bdcd8815a97a1ad3a24def114f 0 274 1461 1457 2024-11-29T21:13:33Z Katz 53 added category wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''', also known simply as '''Artix''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init system]]s. Possible init systems include: * [[dinit]] * [[OpenRC]] * [[runit]] * [[s6]] [[Category:Linux Distributions]] 8b808b8d0eedf883fbfd3649d62b21867d5016aa 0 424 1462 2024-11-29T23:32:14Z Aru 17 Created the AWK page stub wikitext text/x-wiki = AWK = AWK is a programming language focused primarily on textual data processing<ref>[https://www.gnu.org/software/gawk/manual/html_node/] Top (The GNU Awk User's Guide)</ref>, though it can be used for other general-purpose tasks. This page will focus primarily on GNU Awk, or GAWK/<code>gawk</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/], Although the language name is officially stylized AWK, GNU officially uses the stylization Awk. They also acknowledge that the language itself is spelled AWK.</ref>. == Basic Usage == One of the most basic ways to use AWK is in a pipe to filter columnar data. For example, <code>cat file.txt | awk '{ print $1 }'</code> will print the first (space-delimited) column of a given file. This can be generalized to the second, third, etc. columns using <code>$2</code>, <code>$3</code>, etc. respectively. AWK can also be ran with <code>awk 'program-here' input-file1 input-file2 ...</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/One_002dshot.html] One-shot (The GNU Awk User's Guide)</ref>, so the above example with <code>cat</code> could also be written as: <pre> awk '{ print $1 }' file.txt </pre>More usage examples can be found on the [https://www.gnu.org/software/gawk/manual/html_node/Command-Line.html GAWK manual page], as well as AWK's [https://www.gnu.org/software/gawk/manual/html_node/Options.html many command-line options]. == AWK as a Language == AWK can also be used as a programming language. AWK programs consist of a list of patterns followed by actions to perform for each of those patterns<ref>[https://www.gnu.org/software/gawk/manual/html_node/Getting-Started.html] Getting Started (The GNU Awk User's Guide)</ref>: <pre> pattern { action } pattern { action } ... </pre> === BEGIN and END === Two common patterns are <code>BEGIN</code> and <code>END</code>, which run the given action before and after any text is processed respectively. These are called the "startup" and "cleanup" actions<ref>[https://www.gnu.org/software/gawk/manual/html_node/Using-BEGIN_002fEND.html] Using BEGIN/END (The GNU Awk User's Guide)</ref>. For example, the following code will print "Hello, World!": <pre> awk 'BEGIN { print "Hello, World!" }' </pre> The following will accept input until an EOF (inputtable in many shells as Ctrl+D), then print "Hello, World!": <pre> awk 'END { print "Hello, World!" }' </pre> === Regex Pattern === AWK can also be used to run a command for every line that matches a given regular expression. The following example prints every line that contains "regex" (equivalent to <code>grep 'regex'</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Regexp-Usage.html] Regexp Usage (The GNU Awk User's Guide)</ref>:<syntaxhighlight lang="awk"> /regex/ { print } </syntaxhighlight>The <code>{ print }</code> is actually implicit, meaning it can also be written:<syntaxhighlight lang="awk"> /regex/ </syntaxhighlight>One can combine this with <code>$1</code>, <code>$2</code>, etc. to print the second column of every row containing a given string, for example:<syntaxhighlight lang="awk"> /regex/ { print $2 } </syntaxhighlight> === Operations === AWK can be used to perform operations seen in many other programming languages, such as addition (<code>+</code>), subtraction (<code>-</code>), multiplication (<code>*</code>), division (<code>/</code>), modulus (<code>%</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Arithmetic-Ops.html] Arithmetic Ops (The GNU Awk User's Guide)</ref>, variable assignment (<code>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Assignment-Ops.html] Assignment Ops (The GNU Awk User's Guide)</ref>, equality (<code>==</code>) and inequality checks (<code>!=</code>), and comparisons (<code><</code>, <code><=</code>, <code>></code>, <code>>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Comparison-Operators.html] Comparison Operators (The GNU Awk User's Guide)</ref>. === ARGC and ARGV === Like many other programming languages, AWK programs can parse command-line arguments. The <code>ARGC</code> and <code>ARGV</code> variables (among [https://www.gnu.org/software/gawk/manual/html_node/Built_002din-Variables.html many others]) store the count of the arguments and an array of the arguments respectively<ref>[https://www.gnu.org/software/gawk/manual/html_node/Auto_002dset.html#index-ARGC_002fARGV-variables] ARGC, ARGV - Auto-set (The GNU Awk User’s Guide)</ref>. ef03831f7d71a758a1b9af2779d769d8d5fecad2 1465 1462 2024-11-30T15:13:05Z Aru 17 Added to Programming Languages and Software categories wikitext text/x-wiki = AWK = AWK is a programming language focused primarily on textual data processing<ref>[https://www.gnu.org/software/gawk/manual/html_node/] Top (The GNU Awk User's Guide)</ref>, though it can be used for other general-purpose tasks. This page will focus primarily on GNU Awk, or GAWK/<code>gawk</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/], Although the language name is officially stylized AWK, GNU officially uses the stylization Awk. They also acknowledge that the language itself is spelled AWK.</ref>. == Basic Usage == One of the most basic ways to use AWK is in a pipe to filter columnar data. For example, <code>cat file.txt | awk '{ print $1 }'</code> will print the first (space-delimited) column of a given file. This can be generalized to the second, third, etc. columns using <code>$2</code>, <code>$3</code>, etc. respectively. AWK can also be ran with <code>awk 'program-here' input-file1 input-file2 ...</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/One_002dshot.html] One-shot (The GNU Awk User's Guide)</ref>, so the above example with <code>cat</code> could also be written as: <pre> awk '{ print $1 }' file.txt </pre>More usage examples can be found on the [https://www.gnu.org/software/gawk/manual/html_node/Command-Line.html GAWK manual page], as well as AWK's [https://www.gnu.org/software/gawk/manual/html_node/Options.html many command-line options]. == AWK as a Language == AWK can also be used as a programming language. AWK programs consist of a list of patterns followed by actions to perform for each of those patterns<ref>[https://www.gnu.org/software/gawk/manual/html_node/Getting-Started.html] Getting Started (The GNU Awk User's Guide)</ref>: <pre> pattern { action } pattern { action } ... </pre> === BEGIN and END === Two common patterns are <code>BEGIN</code> and <code>END</code>, which run the given action before and after any text is processed respectively. These are called the "startup" and "cleanup" actions<ref>[https://www.gnu.org/software/gawk/manual/html_node/Using-BEGIN_002fEND.html] Using BEGIN/END (The GNU Awk User's Guide)</ref>. For example, the following code will print "Hello, World!": <pre> awk 'BEGIN { print "Hello, World!" }' </pre> The following will accept input until an EOF (inputtable in many shells as Ctrl+D), then print "Hello, World!": <pre> awk 'END { print "Hello, World!" }' </pre> === Regex Pattern === AWK can also be used to run a command for every line that matches a given regular expression. The following example prints every line that contains "regex" (equivalent to <code>grep 'regex'</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Regexp-Usage.html] Regexp Usage (The GNU Awk User's Guide)</ref>:<syntaxhighlight lang="awk"> /regex/ { print } </syntaxhighlight>The <code>{ print }</code> is actually implicit, meaning it can also be written:<syntaxhighlight lang="awk"> /regex/ </syntaxhighlight>One can combine this with <code>$1</code>, <code>$2</code>, etc. to print the second column of every row containing a given string, for example:<syntaxhighlight lang="awk"> /regex/ { print $2 } </syntaxhighlight> === Operations === AWK can be used to perform operations seen in many other programming languages, such as addition (<code>+</code>), subtraction (<code>-</code>), multiplication (<code>*</code>), division (<code>/</code>), modulus (<code>%</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Arithmetic-Ops.html] Arithmetic Ops (The GNU Awk User's Guide)</ref>, variable assignment (<code>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Assignment-Ops.html] Assignment Ops (The GNU Awk User's Guide)</ref>, equality (<code>==</code>) and inequality checks (<code>!=</code>), and comparisons (<code><</code>, <code><=</code>, <code>></code>, <code>>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Comparison-Operators.html] Comparison Operators (The GNU Awk User's Guide)</ref>. === ARGC and ARGV === Like many other programming languages, AWK programs can parse command-line arguments. The <code>ARGC</code> and <code>ARGV</code> variables (among [https://www.gnu.org/software/gawk/manual/html_node/Built_002din-Variables.html many others]) store the count of the arguments and an array of the arguments respectively<ref>[https://www.gnu.org/software/gawk/manual/html_node/Auto_002dset.html#index-ARGC_002fARGV-variables] ARGC, ARGV - Auto-set (The GNU Awk User’s Guide)</ref>. <references /> [[Category:Software]] [[Category:Programming Languages]] f1287c90efb6f01c7c68d455877f13eeff220ec9 1 425 1463 2024-11-29T23:33:42Z Aru 17 /* TODO */ new section wikitext text/x-wiki == TODO == This is a general todo thread for future contributors. To start: Categorize the page, add sections on control flow, arrays, and functions, and provide more "basic usage" examples. [[User:Aru|Aru]] ([[User talk:Aru|talk]]) 23:33, 29 November 2024 (UTC) 5df080317093621f78448a6afbf48cf4042bdc50 1464 1463 2024-11-29T23:37:44Z Aru 17 Reword wikitext text/x-wiki == TODO == This is a general todo thread for future contributors. * Categorize the page * Control flow * Arrays * Functions * Basic usage examples * Diversify sources if deemed preferable fa0d99d9aa897c868cb74cd0d740175c64b3c23d 14 426 1467 2024-11-30T15:13:05Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Programming Languages" as well as all subcategories of category "Programming Languages" if any exist. 1064a65e9c6e89ff8188e9463f4d738d7b09d6af 0 349 1469 1417 2024-12-05T21:29:47Z Ow0cast 249 cleanup | move a space around a ref wikitext text/x-wiki In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is required to enable optimal use of a OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor'''<ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref> of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in a operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, etc. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |runit |February 10, 2004 |September 29, 2024 |↓ |Gerrit Pape |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS.<references /> [[Category:Terminology]] df53098b819c6329bed6a00f01ad9c8187b7923b 0 306 1470 1226 2024-12-05T21:38:41Z Ow0cast 249 cleanup | change how some links appear and rm some caps wikitext text/x-wiki A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environment|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Terminology]] 60eadb76770fb4c80c2baba3fdd535c0aa8ceb79 1482 1470 2024-12-29T15:50:32Z Stewarpt 100 Edited desktop environments so I brought you to the desktop environments page wikitext text/x-wiki A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[UI|User Interface (UI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Terminology]] 250f3dc91907472e025535c720bfc56dbbc1d61d 2 427 1471 2024-12-06T18:20:32Z Ow0cast 249 Created page with "==<nowiki>:</nowiki>3==" wikitext text/x-wiki ==<nowiki>:</nowiki>3== 5f4923d721516f0900606626c78716b3f51c2b5e 0 428 1472 2024-12-09T02:10:48Z RealMrCactus 96 Created page with "Man or Man pages is a [[command-line]] utility available on [[Unix]] and [[Unix-like]] [[operating systems]] that provides [[documentation]] for [[Program|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format]] and [[games]]. The Man pages are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a Man page the user can en..." wikitext text/x-wiki Man or Man pages is a [[command-line]] utility available on [[Unix]] and [[Unix-like]] [[operating systems]] that provides [[documentation]] for [[Program|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format]] and [[games]]. The Man pages are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a Man page the user can enter the following into their [[terminal]]: man <command_name> <ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> For example to read the Man page on [[pacman]] you would enter the following: man pacman == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardize layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> <references /> 0b81a457f04a7a49aa038610e70ee2ffbdef39f2 0 412 1473 1429 2024-12-12T06:16:35Z Minimum1674 68 added software tag wikitext text/x-wiki {{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-org | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }} '''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. === Available Parameters === {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default (none unless specified) || [given parameter] |} === Trivia === * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ ^{<nowiki>[1]</nowiki>}] * [[Larry the Cow]] (<code>emerge --moo</code>) and Cowsay share the same ASCII art, [[Debian]]'s Larry ASCII arts don't. * There is a graphical version of this program called [https://www.doof.me.uk/xcowsay/ xcowsay]. [[Category:Software]] 72e7deeb5ada3d1b9530d0a5db7b5b26fb927083 0 1 1474 1450 2024-12-12T13:33:25Z Atmois 13 Emails update wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorized" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * tess(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 2c432020dc27b4439aeda3e29a41dcd37bc7c6ad 1475 1474 2024-12-13T18:18:24Z Electron271 3 Add new contact email wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a Wiki Admin or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorized" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == '''Contacts''' == You can contact the wiki admins in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the Wiki Admins via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * tess(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 69589939370a4893e91fbafd8f5fa0b1df1dcb5e 2 289 1476 1448 2024-12-18T20:15:29Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml" line="1"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <os>Gentoo/Windows</os> <extra>Robot/Furry (Axolotl)</extra> <socials>https://linktr.ee/mymetype</socials> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json" line="1"> { "atl.wiki":{ "todo":{ "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> ce078ece2ee376aa2279034935a67bedce44e4b8 0 236 1477 1206 2024-12-23T17:28:31Z MymeType 35 Updated last release wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.20, 2024-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * Desktop Manager - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[Terminal Emulator|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> [[Category:Desktop Environments]] 201671c652e68c6c9ed32f7a17d0b90f7e3eabd0 0 429 1478 2024-12-25T04:18:57Z RealMrCactus 96 Made a page for CRUX Linux. wikitext text/x-wiki CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "[[Portfiles]]," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> e25f6483c1ceb8870664354d69c9421ab414a009 1480 1478 2024-12-27T03:08:51Z Katz 53 added category wikitext text/x-wiki CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "[[Portfiles]]," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> [[Category:Linux Distributions]] b0d7909fb81f6b407333b79c4d73ba1f00eaf128 0 430 1484 2025-01-01T08:39:19Z Rayk4z1 62 Begun the daemon processes page. added systemctl wikitext text/x-wiki Computers with the ability to multitask different processes at once contain a type of process labelled '''daemon''' process. These types of computer programs run in the background, which isn't controlled by a graphical interface or any user input, but rather, by the [[Init System|init system]], which also serves as the parent process<ref>Sep 2nd, 2020, ''Understanding daemons Unix'' by Aryaman Sharda: https://digitalbunker.dev/understanding-daemons-unix/</ref> of <u>most</u> daemons. For easier identification, processes' names end with the letter ''d'' to indicate the the subjected process is a daemon. There are a few ways a daemon process can be made, all with different use cases: calling a <code>fork</code>and having the parent exit <ref>Chapter 13. Daemon Processes by Shichao's Notes: https://notes.shichao.io/apue/ch13/</ref> creates a daemon process by tricking the shell to thinking the command is finished, the child process obtains a new GID (Group Identifier) but is assigned a different PID (Process Identifier), another method calls a <code>umask</code> to set the file mode creation mask to a known value, this method is typically preferred when the process makes necessary files. There are more uncommon methods to achieve a daemon process, but are typically too complicated. === Controlling a Daemon Process === ==== Using <code>systemctl</code>: ==== A user is able to adjust whether a daemon process is enabled or not using the <code>systemctl</code> command in their preferred shell, if the user wishes to start a daemon, they are able to use the <code>start</code> function, next to the service name in order to start it up. <syntaxhighlight lang="shell"> $ sudo systemctl start application.service # There is no output if a application begins succsesfully # If there is an error: Failed to start application.service: Unit application.service not found. # or Failed to start application.service: Access denied </syntaxhighlight>The user isn't required to add <code>*.service</code>, the system will automatically look for services that match. This command also works with <code>stop</code>, prompting the said service to terminate.<syntaxhighlight lang="shell"> $ sudo systemctl stop application.service # No Output if successful # Output on Error(s): Failed to stop application.service: Unit application.service not loaded. # or Failed to stop application.service: Access denied. </syntaxhighlight>If this is a process that is started by the init system at boot, it will begin again on a full reboot if it is enabled or when it is started manually. <references /> 072d0da38000e2e81d507bd6c3520ebbe31a6a96 1505 1484 2025-01-02T07:57:36Z Rayk4z1 62 Added Terminology and a bit of Use-Cases. wikitext text/x-wiki [[File:Daemon.png|thumb|Daemon Flowchart]] Computers with the ability to multitask different processes at once contain a type of process labelled '''daemon''' process. These types of computer programs run in the background, which isn't controlled by a graphical interface or any user input, but rather, by the [[Init System|init system]], which also serves as the parent process<ref>Sep 2nd, 2020, ''Understanding daemons Unix'' by Aryaman Sharda: https://digitalbunker.dev/understanding-daemons-unix/</ref> of <u>most</u> daemons. For easier identification, processes' names end with the letter ''d'' to indicate the the subjected process is a daemon. There are a few ways a daemon process can be made, all with different use cases: calling a <code>fork</code>and having the parent exit <ref>Chapter 13. Daemon Processes by Shichao's Notes: https://notes.shichao.io/apue/ch13/</ref> creates a daemon process by tricking the shell to thinking the command is finished, the child process obtains a new GID (Group Identifier) but is assigned a different PID (Process Identifier), another method calls a <code>umask</code> to set the file mode creation mask to a known value, this method is typically preferred when the process makes necessary files. There are more uncommon methods to achieve a daemon process, but are typically too complicated. === Terminology === The term "'''daemon'''" comes from MIT's Project MAC<ref>Take Our Word For It, Issue 129, Page 2: http://www.takeourword.com/TOW129/page2.html</ref> on the IBM 7094, labelled after scientist James Maxwell who imagined an interesting physics problem: He Imagined a container divided by a gate which separates the container into 2 equal parts, within the gate exists a hole big enough for one gas molecule, this gate was controlled by a ''daemon.'' Maxwell labelled it a "daemon" based off Greek Mythology where a daemon was a supernatural force that would work in the background. === Use-case(s) === ==== Unix-based/like Operating Systems ==== In such operating systems, daemons serve many functions for every part of the system and are very common. Although not required, many daemons have their parent be the init system, which possesses the PID of 1. Typically speaking, processes become daemons by being started by either the init system or a start up script. === Controlling a Daemon Process === ==== Using <code>systemctl</code>: ==== A user is able to adjust whether a daemon process is enabled or not using the <code>systemctl</code> command in their preferred shell, if the user wishes to start a daemon, they are able to use the <code>start</code> function, next to the service name in order to start it up. <syntaxhighlight lang="shell"> $ sudo systemctl start application.service # There is no output if a application begins succsesfully # If there is an error: Failed to start application.service: Unit application.service not found. # or Failed to start application.service: Access denied </syntaxhighlight>The user isn't required to add <code>*.service</code>, the system will automatically look for services that match. This command also works with <code>stop</code>, prompting the said service to terminate.<syntaxhighlight lang="shell"> $ sudo systemctl stop application.service # No Output if successful # Output on Error(s): Failed to stop application.service: Unit application.service not loaded. # or Failed to stop application.service: Access denied. </syntaxhighlight>If this is a process that is started by the init system at boot, it will begin again on a full reboot if it is enabled or when it is started manually. <references /> 5b5b21d1ef13a9fe39b9ad783b7179ba204bb821 0 395 1485 1383 2025-01-01T08:53:02Z Atmois 13 fix double redirect wikitext text/x-wiki #REDIRECT [[Package_Manager]] 090cbc1b1fd5d71e212e042015c295c66934c457 0 387 1486 1375 2025-01-01T08:53:04Z Atmois 13 fix double redirect wikitext text/x-wiki #REDIRECT [[Window_Manager]] f30c6998b29455871d47b5b5119e0b47257fe8e3 0 176 1487 1398 2025-01-01T22:16:10Z Gurov 103 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.2.4, 2024-11-26 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 90e7f7162cd0338aa0a6490d3574ae78d8e7d77e 0 291 1489 1012 2025-01-01T22:20:07Z Gurov 103 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|200px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 47, 2024-09-18 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = The GNOME Project | website = [https://gnome.org/, gnome.org] }} [[File:GNOME 46.png|thumb|A desktop running GNOME 46 in Fedora Workstation 40]] [[GNOME]] is a desktop environment designed to be simple, beautiful, and elegant. It is the main desktop environment of [[Fedora]] and [[Ubuntu]] among others, and is a very popular desktop environment within [[Linux]]/BSD. GNOME began development in 1997 by Miguel de Icaza and Federico Mena, with GNOME 1, the first major release of GNOME, being released in 1999. == GTK == GTK (formerly, GIMP Toolkit) is a widget toolkit that was created for GIMP, but is known as the widget toolkit for GNOME. It uses the GLib data structure and GObject object and type system, to create the GUI behind GNOME and GTK apps such as Epiphany, GIMP and Transmission among others. GTK is one of the most commonly used GUI frameworks, alongside the Qt framework, Cocoa for macOS and Windows Forms for Windows among others. [[Category:Desktop Environments]] 3b916a3184f4d3e48ef2812c4e9784a81d43e0f5 0 317 1488 1318 2025-01-01T22:20:18Z Kapija 105 added the architectures wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop | architectures = amd64, aarch64, i686 | website = [https://voidlinux.org/ voidlinux.org] }} [[File:Voidlinux-by-dnv.png|alt=A screenshot of a Void Linux dark mode setup|thumb|Void Linux setup running DWM.]] '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for x86_64, i686, aarch64, armv6l and armv7l, and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. A guide to installing Void Linux, along with other useful information, is located on [https://docs.voidlinux.org/installation/index.html the documentation page]. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] 86725e97560a508b30e610fb5b93573ad64e291e 1490 1488 2025-01-01T22:21:14Z Kapija 105 added the architectures wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} [[File:Voidlinux-by-dnv.png|alt=A screenshot of a Void Linux dark mode setup|thumb|Void Linux setup running DWM.]] '''Void GNU/Linux''' is a rolling-release Linux distribution built from source (not based on anything). Void Linux is most commonly used on desktop systems for its lightness, minimalism and ease of setup. It is distributed for x86_64, i686, aarch64, armv6l and armv7l, and also provides a rootfs tarball, and amongst other things, it also allows you to choose between a glibc and musl image. Like most minimalistic distributions, Void does not come with a graphical environment or any user utilities out of the box. However, they can be installed by the user later on. A guide to installing Void Linux, along with other useful information, is located on [https://docs.voidlinux.org/installation/index.html the documentation page]. ==XBPS== The '''X Binary Package System''', commonly abbreviated as XBPS, is a package manager maintained and developed by the Void Linux team. It features, on top of the normal package management utilities, tools to help port packages (from .deb to .xbps, for example), to make your own package and others. A list of general-use XBPS commands can be found below. {| class="wikitable" style="margin:auto" |- ! Utility !! Usage |- | xbps-install || Fetches a package and its dependencies from the repo and installs it |- | xbps-remove || Removes a package from the system |- | xbps-query || Used to do many things, like getting the total number of packages installed or searching for them in the repo |- | xbps-reconfigure || Reconfigures a specific package, allowing for additional customization or bugfixing |} [[Category:Linux Distributions]] 97ec4ec887a13a9e03493fa4c795e24d1459c2fd 6 431 1491 2025-01-01T22:40:27Z Gurov 103 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 432 1492 2025-01-01T22:48:30Z Ktmfn 104 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 433 1493 2025-01-01T22:49:02Z Gurov 103 Created page with "A '''CLI''' (Command-Line Interface) is a text-based interaction model in which users typewrite commands as text strings to interact with an operating system or a program through a computer. Unlike a [[TUI]], which relies upon a pseudo-graphical form made of characters, an interface that is purely a command-driven one usually would issue output in the form of lines of text upon receiving user instructions. File:Windows_Command_Prompt_Program.png|thumb|The Windows Comm..." wikitext text/x-wiki A '''CLI''' (Command-Line Interface) is a text-based interaction model in which users typewrite commands as text strings to interact with an operating system or a program through a computer. Unlike a [[TUI]], which relies upon a pseudo-graphical form made of characters, an interface that is purely a command-driven one usually would issue output in the form of lines of text upon receiving user instructions. [[File:Windows_Command_Prompt_Program.png|thumb|The Windows Command Prompt, an example of a CLI]] CLIs are often preferred by power users, system administrators, and developers for their efficiency, scriptability, and precise control over system operations. Common examples include: * Unix/Linux shells (bash, zsh, fish) * Windows Command Prompt * PowerShell * Python's REPL (Read-Eval-Print Loop) The main advantages of CLIs include: * Resource efficiency (minimal system requirements) * Automation capability through scripting * Remote system administration * Precise control over system operations * Speed of execution for experienced users While CLIs can have a steeper learning curve compared to GUIs (Graphical User Interfaces) or [[TUI]]s, they remain fundamental to modern computing, particularly in server administration, software development, and system maintenance. == History == Command-line interfaces emerged in the 1960s with computer terminals like the Teletype Model 33 ASR, which replaced punch cards as the primary means of computer interaction. Early operating systems like Unix and MS-DOS were primarily accessed through CLIs, establishing conventions that persist in modern computing. == Common Usage == CLI environments typically follow a standard pattern where: * The system displays a prompt (e.g., "$" for Unix-like systems) * Users type commands followed by arguments or options * The system executes the command and displays the output * The process repeats with a new prompt [[Category:Terminology]] [[Category:User interfaces]] 81bea521c8d95000af6bc48314e5b4ca23a3a2a9 14 435 1495 2025-01-01T22:49:02Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "User interfaces" as well as all subcategories of category "User interfaces" if any exist. a0c61140e3f758ff4d22dad673ca777e8556f667 6 434 1494 2025-01-01T22:49:12Z Ktmfn 104 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 436 1496 2025-01-01T23:02:37Z Ktmfn 104 Created page with "{{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie_Linux_Logo|thumb|logo of Adelie Linux]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/]}} [[File:Adelie_neofetch|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is a Linux Di..." wikitext text/x-wiki {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie_Linux_Logo|thumb|logo of Adelie Linux]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/]}} [[File:Adelie_neofetch|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is a [[Linux Distributions|Linux distribution]], based on Alpine Linux. The distribution targets old and low end machines, like desktops and servers. === Functionality === The most main difference of this distribution from others is in [[Package Manager|package manager]] named ''[[apk]]''from Alpine Linux and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4. 2024 comprises only 28 packages such as ''[[musl]]'', and the only optional package ''linux'', comprising the [[Linux|kernel]]. 00d73c07623d6c051789b6dd3c7e07dec355f1df 1498 1496 2025-01-01T23:05:29Z Ktmfn 104 wikitext text/x-wiki {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb|logo of Adelie Linux]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is a [[Linux Distributions|Linux distribution]], based on Alpine Linux. The distribution targets old and low end machines, like desktops and servers. === Functionality === The most main difference of this distribution from others is in [[Package Manager|package manager]] named ''[[apk]]''from Alpine Linux and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4. 2024 comprises only 28 packages such as ''[[musl]]'', and the only optional package ''linux'', comprising the [[Linux|kernel]]. 8d53d3763287a6a9083d5de3b0dc4f1a627b4592 1499 1498 2025-01-01T23:09:22Z Ktmfn 104 /* Functionality */ wikitext text/x-wiki {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb|logo of Adelie Linux]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is a [[Linux Distributions|Linux distribution]], based on Alpine Linux. The distribution targets old and low end machines, like desktops and servers. === Base description === One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution uses the OpenRC init system for service management, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. 29f0fdbb3c4bd438fc1ce59fb72b56504da7ef10 14 437 1497 2025-01-01T23:02:37Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Pages with broken file links" as well as all subcategories of category "Pages with broken file links" if any exist. 741f01da22ff0fc0b6ec39c197279a7c54b2c168 6 438 1500 2025-01-01T23:18:59Z Ktmfn 104 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 439 1501 2025-01-01T23:32:46Z Ktmfn 104 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 440 1502 2025-01-01T23:36:23Z Ktmfn 104 create new page wikitext text/x-wiki {{DistributionInfobox | title = ROSA Linux | image = [[File:ROSA_Linux_Logo.png|150px|thumb|ROSA Linux Logo]] | caption = The ROSA Linux logo | releasestatus = Abandoned | releasemodel = Stable | packagemanager = [https://rpm-software-management.github.io/ DNF package manager] | defaultdesktops = GNOME, [[KDE Plasma]], LXQt, [[Xfce]] | usagetype = Desktop, Server | architectures = P5 (i586), x86_64 | website = [https://rosa.ru/rosa-fresh-12/ rosa.ru/rosa-fresh-12] }} [[File:Rosalinux_desktop_showcase.jpeg|thumb|ROSA Linux Fresh 12 running on KDE Plasma 5 and has open Dolphin, Gwenview and mpvplayer]] '''ROSA Linux''' is a [[Linux Distributions|Linux distribution]] built around the '''OpenMandriva''', offering closed-source software such as Adobe Flash Player, proprietary multimedia codecs. It was initially developed by AO NTC IT ROSA. (rus. - АО «НТЦ ИТ РОСА») === Focus on KDE Plasma as the desktop environment. === ROSA Linux is known for its focus on the KDE Plasma desktop environment, which offers a rich graphical interface and extensive customization options. This makes it an attractive choice for users who appreciate a modern and aesthetically pleasing desktop experience. === Applications === The distribution includes a wide range of pre-installed applications, covering essential tasks such as web browsing, multimedia playback, and office productivity, while also providing access to a comprehensive software repository for additional applications. === Ease of use === One of the key features of ROSA Linux is its commitment to user experience, with an emphasis on ease of use and accessibility. The distribution is designed to be intuitive, making it suitable for both newcomers to Linux and experienced users. It also supports multiple languages, catering to a diverse user base. === Multiple editions. === ROSA Linux is available in several editions, including ROSA Fresh, which is aimed at general users and features the latest software updates, and ROSA Enterprise, which is tailored for business environments and focuses on stability and long-term support. With a strong emphasis on community involvement and open-source principles, ROSA Linux encourages contributions from users and developers alike. It has gained popularity in various regions, particularly in Russia and Eastern Europe, and continues to be a viable option for those seeking a reliable and visually appealing Linux distribution. 65cf125a0f70b24a4a7ab4f1a6669635b3d02184 4 327 1504 1451 2025-01-02T01:58:11Z Electron271 3 wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen electron was here testing testing 1 2 3 4<ref>hi</ref> 110f9ccb5d5d77eb7b483e41ad62284535646e7e 6 442 1507 2025-01-02T07:51:24Z Rayk4z1 62 Daemon Flow Chart wikitext text/x-wiki == Summary == Daemon Flow Chart 6ea3bc26b67f264f14550bf2cd092a8487377a79 0 441 1506 2025-01-02T08:38:53Z Rayk4z1 62 Started GNU with Componets and 3 references wikitext text/x-wiki GNU, not to mixed with XNU nor the animal, is a collection of software which is labelled '''free''', which is defined as a piece of software that is free to all and open sourced. GNU can technically be used as a standalone operating system, but is typically mixed in with other essential tools to push it up to quality of life standards and overall be easy-to-use. GNU also helped form what [[Linux]] is today with its essential tools mixed in with Linux's Kernel making GNU/Linux. <ref>[https://www.debian.org/releases/stable/armel/ch01s02.en.htmlInstalling&#x20;Debian&#x20;GNU Installing Debian GNU/Linux for armel]. Chapter 1.2, ''What is GNU/Linux?''</ref> === GNU's Components === The basic components provided by GNU: The GNU Compiler Collection aka the GCC, GNU Core Utilities (Core Utils), the GNU C Library (glibc), GNU Debugger (GDB), GNU Binary Utilities (binutils), and GNU Bash.<ref>[https://www.gnu.org/software/software.html GNU Software], The GNU Project: Free Software. ''"Make Proprietary software a thing of the past."''</ref><ref>[[wikipedia:List_of_GNU_packages|List of GNU Packages]] - Wikipedia, ''The Free Encyclopedia''. </ref> <references /> c565a7e1b0f2821a900ea1a98e4a003482067cbe 6 443 1508 2025-01-02T14:00:44Z Exulan 107 Example of an enterpise grade homelab. wikitext text/x-wiki == Summary == Example of an enterpise grade homelab. f41de82ef03559f9000aa0eec70d2116f58a6041 6 444 1509 2025-01-02T14:05:57Z Exulan 107 Internet speed example wikitext text/x-wiki == Summary == Internet speed example d3a4cddcc787595379789dd95db2c4d336101c8b 6 445 1510 2025-01-02T14:12:00Z Exulan 107 An example of an uninterruptible power supply. wikitext text/x-wiki == Summary == An example of an uninterruptible power supply. e11202091dbc93695fcdfb920f8a98a18049765d 6 446 1511 2025-01-02T14:17:44Z Exulan 107 Example of a storage failure. wikitext text/x-wiki == Summary == Example of a storage failure. c837f19a02b26570e1f4e0d63929b6d6826d687f 0 447 1512 2025-01-02T14:20:16Z Exulan 107 Introduction to Self-Hosting wikitext text/x-wiki == Self-Hosting == === Introduction === Self-hosting is a rewarding practice that allows you to reduce reliance on cloud services, giving you much greater control and privacy over the data you own. By self-hosting, the services you use, and by extension anything you store with those services, reside on your own hardware rather than third-party servers. Essentially, the “cloud” is just someone else’s computer, often a large, multi-billion-dollar infrastructure. However, with self-hosting, you own the data on the devices you manage. === What is Self-Hosting? === Self-hosting often refers to the process of running and managing your own services on personal hardware such as a laptop, desktop, single-board computer, or even an enterprise-grade server. This means you can set up and operate services for yourself, your family, or others without depending on external cloud platforms. === What Can I Host? === There are numerous possibilities for self-hosting, depending on your needs. Some popular options include: * Email server * Password manager * Personal website * File hosting service * Media server * VPN (Virtual Private Network) === Do I Need Anything Special to Self-Host? === [[File:Homelab.jpg|thumb|Example of an enterpise grade homelab]] The requirements are minimal. You can self-host using almost any device, from an old, cheap laptop to a single-board computer like a Raspberry Pi. Some enthusiasts take this a step further and use second-hand enterprise equipment from real data center infrastructure to host their services. These setups are often referred to as “HomeLabs.” However, anything that can connect to the internet or your local area network can be sufficient. === The Challenges of Self-Hosting === Like everything in life, self-hosting has its challenges. When hosting services at home, you are responsible for maintaining and fixing any problems that arise. Unlike cloud services, which are typically plug-and-play, homelabs require regular maintenance to ensure stable operation. Below are some challenges many homelab users encounter. ==== Common Problems ==== * '''Electricity Usage''' - One of the main concerns with starting a homelab is power consumption. As your homelab grows, so will its electricity usage. Additionally, the services you run rely on your home's power grid, meaning power outages can affect your services. [[File:Speedtest.png|thumb|Example of a users internet speed.]] * '''Internet Speed''' - Not all internet connections are equal. When exposing services to the outside world, consider how much bandwidth they will consume. A slow connection or data caps can limit what you can host effectively. Residential internet plans might not support the load or violate fair use policies. Like the electricity usage, you are relying on the reliance your ISP provides. * '''Natural Disasters''' - Hosting services in areas prone to natural disasters poses risks. If a disaster damages your homelab, your data may be lost along with the equipment. * '''Vulnerabilities''' - Even with the latest software and hardware, vulnerabilities persist. Tools like Shodan.io scan for exposed services, potentially attracting malicious actors. Without sufficient protection, your services may be at risk. * '''Hardware Failures''' - Nothing lasts forever. Self-hosted services depend on your hardware, which will need maintenance and occasional replacement. Hard drives, in particular, are susceptible to failure over time. * '''Sound''' - Unlike a laptop or a single-board computer, enterprise equipment is not built to be quiet. It is designed to run cool and avoid failure, which often results in high-pitched fan noise due to large amounts of airflow. * '''Dust''' - Most homelabs are not housed in ventilated data centers, leading to dust accumulation, which can clog and damage equipment. * '''User Error''' - Mistakes happen. Deleting the wrong files, modifying incorrect configurations, or failing to double-check changes can lead to data loss or downtime. === Solutions === [[File:Ups uninterruptible power supply.jpg|thumb|An example of an (UPS) Uninterruptible Power Supply]] * '''Electricity Usage''' - Use an Uninterruptible Power Supply (UPS). A UPS acts as a battery backup and protects against power surges. If the power goes out, the UPS switches to battery mode to keep your equipment running. UPS devices can range from small 600W models to large 10kW units that can power enterprise equipment for hours. * '''Internet Speed''' - If your internet is slow or capped, consider upgrading to a better plan if available. Some ISPs offer small business plans for residential users, providing higher speeds, service agreements, and multiple external IP addresses. * '''Natural Disasters''' - Perform regular off-site backups. Store data in locations unaffected by the same natural disasters as your homelab to ensure redundancy. * '''Vulnerabilities''' - To mitigate vulnerabilities some examples include: ** Keep all software and hardware up to date. ** Change default ports for commonly scanned services. ** Install a firewall. ** Use a VPN to access services instead of exposing them directly to the internet. ** Use encrypted protocols and storage. [[File:raid failure.png|thumb|An example of a drive failing in a raid.]] *'''Hardware Failures''' - Practice the 3-2-1 backup strategy: ** Keep at least THREE copies of your data. ** Use at least TWO types of storage. ** Keep at least ONE copy off-site. * '''Sound''' - To mitigate noise, consider buying fanless equipment, as fans are the primary source of noise. Alternatively, place the equipment in a room that is not frequently used to minimize sound. Keep in mind that fanless equipment carries a risk of overheating. * '''Dust''' - Regularly clean your equipment and store it in well-ventilated areas. Use compressed air or vacuum cleaners to remove dust. * '''User Error''' - Double-check all changes, avoid running unfamiliar commands, and thoroughly understand what you are deploying. e042c756eb60fdf32c2859a26a3777b3e5911ebb 1513 1512 2025-01-02T14:25:54Z Atmois 13 Atmois moved page [[Self hosting]] to [[Self-Hosting]]: Misspelled title wikitext text/x-wiki == Self-Hosting == === Introduction === Self-hosting is a rewarding practice that allows you to reduce reliance on cloud services, giving you much greater control and privacy over the data you own. By self-hosting, the services you use, and by extension anything you store with those services, reside on your own hardware rather than third-party servers. Essentially, the “cloud” is just someone else’s computer, often a large, multi-billion-dollar infrastructure. However, with self-hosting, you own the data on the devices you manage. === What is Self-Hosting? === Self-hosting often refers to the process of running and managing your own services on personal hardware such as a laptop, desktop, single-board computer, or even an enterprise-grade server. This means you can set up and operate services for yourself, your family, or others without depending on external cloud platforms. === What Can I Host? === There are numerous possibilities for self-hosting, depending on your needs. Some popular options include: * Email server * Password manager * Personal website * File hosting service * Media server * VPN (Virtual Private Network) === Do I Need Anything Special to Self-Host? === [[File:Homelab.jpg|thumb|Example of an enterpise grade homelab]] The requirements are minimal. You can self-host using almost any device, from an old, cheap laptop to a single-board computer like a Raspberry Pi. Some enthusiasts take this a step further and use second-hand enterprise equipment from real data center infrastructure to host their services. These setups are often referred to as “HomeLabs.” However, anything that can connect to the internet or your local area network can be sufficient. === The Challenges of Self-Hosting === Like everything in life, self-hosting has its challenges. When hosting services at home, you are responsible for maintaining and fixing any problems that arise. Unlike cloud services, which are typically plug-and-play, homelabs require regular maintenance to ensure stable operation. Below are some challenges many homelab users encounter. ==== Common Problems ==== * '''Electricity Usage''' - One of the main concerns with starting a homelab is power consumption. As your homelab grows, so will its electricity usage. Additionally, the services you run rely on your home's power grid, meaning power outages can affect your services. [[File:Speedtest.png|thumb|Example of a users internet speed.]] * '''Internet Speed''' - Not all internet connections are equal. When exposing services to the outside world, consider how much bandwidth they will consume. A slow connection or data caps can limit what you can host effectively. Residential internet plans might not support the load or violate fair use policies. Like the electricity usage, you are relying on the reliance your ISP provides. * '''Natural Disasters''' - Hosting services in areas prone to natural disasters poses risks. If a disaster damages your homelab, your data may be lost along with the equipment. * '''Vulnerabilities''' - Even with the latest software and hardware, vulnerabilities persist. Tools like Shodan.io scan for exposed services, potentially attracting malicious actors. Without sufficient protection, your services may be at risk. * '''Hardware Failures''' - Nothing lasts forever. Self-hosted services depend on your hardware, which will need maintenance and occasional replacement. Hard drives, in particular, are susceptible to failure over time. * '''Sound''' - Unlike a laptop or a single-board computer, enterprise equipment is not built to be quiet. It is designed to run cool and avoid failure, which often results in high-pitched fan noise due to large amounts of airflow. * '''Dust''' - Most homelabs are not housed in ventilated data centers, leading to dust accumulation, which can clog and damage equipment. * '''User Error''' - Mistakes happen. Deleting the wrong files, modifying incorrect configurations, or failing to double-check changes can lead to data loss or downtime. === Solutions === [[File:Ups uninterruptible power supply.jpg|thumb|An example of an (UPS) Uninterruptible Power Supply]] * '''Electricity Usage''' - Use an Uninterruptible Power Supply (UPS). A UPS acts as a battery backup and protects against power surges. If the power goes out, the UPS switches to battery mode to keep your equipment running. UPS devices can range from small 600W models to large 10kW units that can power enterprise equipment for hours. * '''Internet Speed''' - If your internet is slow or capped, consider upgrading to a better plan if available. Some ISPs offer small business plans for residential users, providing higher speeds, service agreements, and multiple external IP addresses. * '''Natural Disasters''' - Perform regular off-site backups. Store data in locations unaffected by the same natural disasters as your homelab to ensure redundancy. * '''Vulnerabilities''' - To mitigate vulnerabilities some examples include: ** Keep all software and hardware up to date. ** Change default ports for commonly scanned services. ** Install a firewall. ** Use a VPN to access services instead of exposing them directly to the internet. ** Use encrypted protocols and storage. [[File:raid failure.png|thumb|An example of a drive failing in a raid.]] *'''Hardware Failures''' - Practice the 3-2-1 backup strategy: ** Keep at least THREE copies of your data. ** Use at least TWO types of storage. ** Keep at least ONE copy off-site. * '''Sound''' - To mitigate noise, consider buying fanless equipment, as fans are the primary source of noise. Alternatively, place the equipment in a room that is not frequently used to minimize sound. Keep in mind that fanless equipment carries a risk of overheating. * '''Dust''' - Regularly clean your equipment and store it in well-ventilated areas. Use compressed air or vacuum cleaners to remove dust. * '''User Error''' - Double-check all changes, avoid running unfamiliar commands, and thoroughly understand what you are deploying. e042c756eb60fdf32c2859a26a3777b3e5911ebb 0 448 1514 2025-01-02T14:25:54Z Atmois 13 Atmois moved page [[Self hosting]] to [[Self-Hosting]]: Misspelled title wikitext text/x-wiki #REDIRECT [[Self-Hosting]] 1f8bdc453b2e397881971d35cbdea7d022385edf 2 289 1515 1476 2025-01-02T14:58:10Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml" line="1"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <distro>Gentoo Linux</distro> <extra>Furry (Axolotl)/Robot</extra> <website>https://mymetype.neocities.org</website> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json" line="1"> { "atl.wiki":{ "todo":{ "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 7d8a66d28456574d3b887338d9e10b988f158292 0 319 1516 1241 2025-01-02T15:25:35Z Gurov 103 Expanded the article with more technical details, examples of ricing tools, and better categorization. wikitext text/x-wiki '''Ricing''' refers to extensively customizing a [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to create a unique, personalized computing experience. The term originated from the automotive modification scene ("ricer" cars) and has been adopted by the Linux/Unix community. While primarily focused on aesthetic customization through themes, colors, widgets, and interface layouts, ricing often includes functionality improvements and performance optimization. Common ricing elements include: * Custom window borders, titlebars, and decorations * Carefully selected color schemes and typography * Specialized status bars and system monitors * Custom application launchers and menus * Personalized desktop widgets and notifications * Modified system icons and cursors Popular tools for ricing include window managers like i3, bspwm, and dwm, along with customization frameworks such as polybar and picom. The ricing community actively shares configurations ("dotfiles") and screenshots on platforms like Reddit's r/unixporn. [[Category:Terminology]] cc0b5911a0bbd0e04c58e3a182311dbcf499a29f 0 203 1517 1460 2025-01-02T15:38:44Z Gurov 103 Expanded the article significantly with new sections on installation, system optimization, security, community and development model, updated the Portage section with a cleaner table format for common commands, and improved the overall wiki structure with proper categories and external resources. wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by Daniel Robbins. Known for its emphasis on customization and performance optimization, Gentoo allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == Gentoo stands out for its unique approach to package management and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === * Complete system customization through source compilation * Choice between OpenRC and systemd init systems * Extensive hardware architecture support * Rolling release model with stable branch option * Minimal base system requirements * Advanced package management through Portage == Installation == Installing Gentoo requires manual configuration and compilation of the system components. The process involves: * Preparing the installation environment * Partitioning and formatting storage * Configuring and compiling the kernel * Setting up the bootloader * Installing and configuring base system packages For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is Gentoo's package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge -a package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |} == System Optimization == === Compilation Flags === Gentoo users can optimize their system through: * CPU-specific optimizations * Custom compile flags * USE flag combinations * Kernel configuration * Package-specific settings === Binary Packages === For users seeking faster installation times, Gentoo offers: * Pre-compiled package options * Binary package creation * Distribution of binary packages * Mixed source/binary environments == Security == Gentoo implements several security measures: * SELinux support * Hardened profiles * Regular security updates * Signed package verification * Kernel hardening options == Community and Development == === Community Resources === * [https://forums.gentoo.org/ Official Forums] * IRC channels * Mailing lists * Wiki documentation * Bug tracking system === Development Model === * Open source development * Community-driven package maintenance * Regular security updates * Active development team * Public Git repositories == Comparison with Other Distributions == === Advantages === * Maximum customization potential * Optimal performance through compilation * Complete control over features * Extensive documentation * Active community support === Considerations === * Longer installation time * Higher learning curve * Requires technical knowledge * Resource-intensive compilation * Regular maintenance needed == Trivia == * Larry the Cow is Gentoo's unofficial mascot * The name "Gentoo" comes from the fast-swimming Gentoo penguin * View Larry by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 38bca764c1eea6362cb7bbcd1fef6862fb664b32 1519 1517 2025-01-03T10:44:38Z MymeType 35 Removed -a flag as it just asks for confirmation and has no impact on the purpose of the command wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by Daniel Robbins. Known for its emphasis on customization and performance optimization, Gentoo allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == Gentoo stands out for its unique approach to package management and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === * Complete system customization through source compilation * Choice between OpenRC and systemd init systems * Extensive hardware architecture support * Rolling release model with stable branch option * Minimal base system requirements * Advanced package management through Portage == Installation == Installing Gentoo requires manual configuration and compilation of the system components. The process involves: * Preparing the installation environment * Partitioning and formatting storage * Configuring and compiling the kernel * Setting up the bootloader * Installing and configuring base system packages For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is Gentoo's package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |} == System Optimization == === Compilation Flags === Gentoo users can optimize their system through: * CPU-specific optimizations * Custom compile flags * USE flag combinations * Kernel configuration * Package-specific settings === Binary Packages === For users seeking faster installation times, Gentoo offers: * Pre-compiled package options * Binary package creation * Distribution of binary packages * Mixed source/binary environments == Security == Gentoo implements several security measures: * SELinux support * Hardened profiles * Regular security updates * Signed package verification * Kernel hardening options == Community and Development == === Community Resources === * [https://forums.gentoo.org/ Official Forums] * IRC channels * Mailing lists * Wiki documentation * Bug tracking system === Development Model === * Open source development * Community-driven package maintenance * Regular security updates * Active development team * Public Git repositories == Comparison with Other Distributions == === Advantages === * Maximum customization potential * Optimal performance through compilation * Complete control over features * Extensive documentation * Active community support === Considerations === * Longer installation time * Higher learning curve * Requires technical knowledge * Resource-intensive compilation * Regular maintenance needed == Trivia == * Larry the Cow is Gentoo's unofficial mascot * The name "Gentoo" comes from the fast-swimming Gentoo penguin * View Larry by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 533ea450ebf46f1d35fe402d7d11b4d9905dd23b 6 449 1518 2025-01-02T22:08:51Z Rayk4z1 62 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 450 1521 2025-01-02T23:22:31Z Rayk4z1 62 wikitext text/x-wiki Richard Stallman Portrait 4acd88ac76d9c71080b78b1b84a2d2e014d46f23 6 451 1522 2025-01-02T23:57:58Z Rayk4z1 62 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 441 1520 1506 2025-01-03T02:51:39Z Rayk4z1 62 Rewritten the whole thing, I added the uhmmmmm uhhhh uhmmmm.. the over view of it, then I added the GNU's Name section, and written about its origins kind of maybe and what it means,,, uhhhhhhhh then I did the Included SOftware, which I might add wit wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,") <ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU] , The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref>is a dedicated organization for [[free software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone operating system because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or proprietary: A few are GNU/[[Linux]], MacOS, Unix-based/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the [[proprietary software]] of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe. </ref> == Included Software / Components == As of June 2024, the GNU project currently holds 394 active packages, but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. == History of GNU == Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref>[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible architecture because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs. <ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> <references /> cef8a5d7ba1d2f116ddc38f838ce2bf8487b0c9d 1555 1520 2025-01-04T02:05:53Z Rayk4z1 62 Added 2 pictures: GCC logo and Richard Stallman, Creator of the GNU Project, added more info under included software wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,") <ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU] , The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref>is a dedicated organization for [[free software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone operating system because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or proprietary: A few are GNU/[[Linux]], MacOS, Unix-based/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the [[proprietary software]] of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe. </ref> == Included Software / Components == [[File:Gnu compiler collection-logo-1.png|alt=This logo depicts a Bull shaped animal jumping out of an egg, in black text that displays the letters G, C, C|left|thumb|224x224px|A logo of the GCC.]] As of June 2024, the GNU project currently holds 394 active packages, but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. Overall, these components are in many operating systems, mainly because of how easy GCC is to access for any developer. Because of Richard Stallman, he was able to open source the variety of tools and software developed for the GNU project and in turn, pushed forward for the movement of open and free software for all.<ref name=":0" /> == History of GNU == [[File:RichardStallman.jpg|alt=A Picture of Richard Matthew Stallman in 2024|thumb|341x341px|A Picture of Richard Matthew Stallman in 2024]] Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref name=":0">[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible architecture because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs. <ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> <references /> 5ec3dc64dbdd60124db8514de747e5dc1cbe93b2 8 456 1527 2025-01-03T18:15:34Z Atmois 13 Created page with "Autoconfirmed Users" wikitext text/x-wiki Autoconfirmed Users 377e649acadd50ac9fbbcf55d5fa6f6f4f08dcee 1549 1527 2025-01-03T20:46:38Z Atmois 13 wikitext text/x-wiki old - Autoconfirmed Users a74bebfde2a1f60f4a1f905dcf05a8eb0971acdb 8 457 1528 2025-01-03T18:15:48Z Atmois 13 Created page with "{{GENDER:$1|Autoconfirmed User}}" wikitext text/x-wiki {{GENDER:$1|Autoconfirmed User}} bd63162c7bbc263e6c84ce08b6371deec76d3071 1548 1528 2025-01-03T20:46:30Z Atmois 13 wikitext text/x-wiki {{GENDER:$1|old - Autoconfirmed User}} 2584633b168a90fecd6dbacfc4a134e17857ca6f 8 458 1530 2025-01-03T18:16:25Z Atmois 13 Created page with "{{GENDER:$1|Bot}}" wikitext text/x-wiki {{GENDER:$1|Bot}} dbab0cfe8909be6fccf6afd31fbfdb494d699cc0 8 462 1534 2025-01-03T18:17:57Z Atmois 13 Created page with "Interface Administrators" wikitext text/x-wiki Interface Administrators 618228bfd5906bc2850fd06deaf36c8fec70c3ff 8 463 1535 2025-01-03T18:18:07Z Atmois 13 Created page with "{{GENDER:$1|Interface Administrator}}" wikitext text/x-wiki {{GENDER:$1|Interface Administrator}} 0a9e3c43b06c36e4a58d9e5c05f401bf5ce5d1e2 8 464 1536 2025-01-03T18:58:16Z Atmois 13 Created page with "{{GENDER:$1|Administrator}}" wikitext text/x-wiki {{GENDER:$1|Administrator}} c484aba17651e1244cc14591e8057168f14faaea 0 317 1552 1490 2025-01-04T00:50:42Z Gurov 103 Extended the article with detailed sections on runit init system, package management with expanded command tables, added architecture and variant comparisons (glibc vs musl), and improved overall structure with proper categorization and external resources, while maintaining Void's focus on minimalism and independence. wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built entirely from scratch. Created in 2008 by Juan Romero Pardines, Void distinguishes itself through unique design choices including the runit init system, home-grown XBPS package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * runit init system instead of systemd * Choice between glibc and musl libc implementations * Rolling release model with stable package testing * Minimal base system with high customizability * Native support for both x86 and ARM architectures === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == Package Management == === XBPS (X Binary Package System) === XBPS is Void's native package manager, offering: * Fast dependency resolution * Binary and source package support * Package signing and verification * Repository management tools * Local package building {| class="wikitable" style="margin:auto" ! Command !! Description !! Common Usage |- | xbps-install || Package installation and system updates || <code>xbps-install -S</code> (sync)<br><code>xbps-install -u</code> (update) |- | xbps-remove || Package removal and cleanup || <code>xbps-remove -R pkg</code> (remove with deps)<br><code>xbps-remove -O</code> (clean orphans) |- | xbps-query || System and repository queries || <code>xbps-query -Rs pkg</code> (search)<br><code>xbps-query -l</code> (list installed) |- | xbps-reconfigure || Package reconfiguration || <code>xbps-reconfigure -f pkg</code> (force reconfigure) |- | xbps-alternatives || Alternative management || <code>xbps-alternatives -l</code> (list alternatives) |} == System Management == === Init System === Void uses runit as its init system, offering: * Simple service management * Clean daemon supervision * Fast boot times * Reliable service logging {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] [[Category:Linux Distributions]] 01d818e13f63b4fb722298ac6c725b27c19ea320 1553 1552 2025-01-04T01:02:46Z Gurov 103 Got yelled by people for the sentence "built entirely from scratch", forced to remove the word "entirely" lol. wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, Void distinguishes itself through unique design choices including the runit init system, home-grown XBPS package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * runit init system instead of systemd * Choice between glibc and musl libc implementations * Rolling release model with stable package testing * Minimal base system with high customizability * Native support for both x86 and ARM architectures === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == Package Management == === XBPS (X Binary Package System) === XBPS is Void's native package manager, offering: * Fast dependency resolution * Binary and source package support * Package signing and verification * Repository management tools * Local package building {| class="wikitable" style="margin:auto" ! Command !! Description !! Common Usage |- | xbps-install || Package installation and system updates || <code>xbps-install -S</code> (sync)<br><code>xbps-install -u</code> (update) |- | xbps-remove || Package removal and cleanup || <code>xbps-remove -R pkg</code> (remove with deps)<br><code>xbps-remove -O</code> (clean orphans) |- | xbps-query || System and repository queries || <code>xbps-query -Rs pkg</code> (search)<br><code>xbps-query -l</code> (list installed) |- | xbps-reconfigure || Package reconfiguration || <code>xbps-reconfigure -f pkg</code> (force reconfigure) |- | xbps-alternatives || Alternative management || <code>xbps-alternatives -l</code> (list alternatives) |} == System Management == === Init System === Void uses runit as its init system, offering: * Simple service management * Clean daemon supervision * Fast boot times * Reliable service logging {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] [[Category:Linux Distributions]] aac270ce287793de9ee499afbfbfd6e104e57f4d 1554 1553 2025-01-04T01:05:03Z Gurov 103 Better wording wikitext text/x-wiki {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution made from scratch. Created in 2008 by Juan Romero Pardines, Void distinguishes itself through unique design choices including the runit init system, home-grown XBPS package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * runit init system instead of systemd * Choice between glibc and musl libc implementations * Rolling release model with stable package testing * Minimal base system with high customizability * Native support for both x86 and ARM architectures === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == Package Management == === XBPS (X Binary Package System) === XBPS is Void's native package manager, offering: * Fast dependency resolution * Binary and source package support * Package signing and verification * Repository management tools * Local package building {| class="wikitable" style="margin:auto" ! Command !! Description !! Common Usage |- | xbps-install || Package installation and system updates || <code>xbps-install -S</code> (sync)<br><code>xbps-install -u</code> (update) |- | xbps-remove || Package removal and cleanup || <code>xbps-remove -R pkg</code> (remove with deps)<br><code>xbps-remove -O</code> (clean orphans) |- | xbps-query || System and repository queries || <code>xbps-query -Rs pkg</code> (search)<br><code>xbps-query -l</code> (list installed) |- | xbps-reconfigure || Package reconfiguration || <code>xbps-reconfigure -f pkg</code> (force reconfigure) |- | xbps-alternatives || Alternative management || <code>xbps-alternatives -l</code> (list alternatives) |} == System Management == === Init System === Void uses runit as its init system, offering: * Simple service management * Clean daemon supervision * Fast boot times * Reliable service logging {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] [[Category:Linux Distributions]] b7bda0fb0599caf5f3531d4e5345361fe3102c5b 0 322 1556 1295 2025-01-04T18:07:09Z Atmois 13 fix link wikitext text/x-wiki == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on Operating Systems === Linux distributions which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * Sabotage * Morpheus Linux * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against [[glibc]]. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] [[Category:Software]] f08a8dcedf608363b3b2f7b4c486963aa8be4cf6 0 274 1557 1461 2025-01-04T18:07:32Z Atmois 13 fix link wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''', also known simply as '''Artix''' is an [[Arch]]-based distribution being nearly identical to Arch besides using alternative [[init System]]s. Possible init systems include: * [[dinit]] * [[OpenRC]] * [[runit]] * [[s6]] [[Category:Linux Distributions]] 3c381a99905eb4db2ff1a0923bc960d0fa6b0c9b 1574 1557 2025-01-05T16:42:09Z Gurov 103 Added sections on Artix's history, package management, installation options, philosophy, and technical requirements. wikitext text/x-wiki {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''', also known simply as '''Artix''', is a Linux distribution based on [[Arch]] that focuses on providing alternative init systems to systemd . It maintains high compatibility with Arch Linux while offering users the freedom to choose their preferred init system. == History == Artix Linux emerged from the Arch-OpenRC and Manjaro-OpenRC projects, officially launching in 2017 as a response to Arch Linux's adoption of systemd as its only init system. The distribution aims to provide a systemd-free experience while maintaining the principles of simplicity and user-centricity that Arch Linux is known for. == Features == === Init System Options === Artix supports multiple init systems: * OpenRC - A dependency-based init system from Gentoo * runit - A cross-platform Unix init scheme with service supervision * s6 - A suite of programs for process supervision * dinit - A service manager and init system designed to be simple and portable === Package Management === Artix uses [[Pacman]] as its package manager and maintains its own repositories alongside converted Arch Linux packages. The distribution provides several package repositories: * System repositories (specific to each init system) * Universe repository (containing converted Arch packages) * Galaxy repository (Artix-specific packages) === Installation === The distribution offers several installation methods: * Live ISOs with various desktop environments * Base ISOs for minimal installations * OpenRC, runit, and s6 variants of each ISO == Philosophy == Artix adheres to the KISS principle (Keep It Simple, Stupid) inherited from Arch Linux while emphasizing: * Init system freedom * System transparency * User control * Minimal [[bloat]] * Rolling release model == Package Compatibility == While maintaining high compatibility with Arch Linux packages, some modifications are necessary for systemd-dependent packages. The Artix team maintains: * Native packages built specifically for Artix * Converted Arch packages modified to work without systemd * Scripts and tools to help users convert systemd-dependent packages == Community == Artix Linux maintains its own: * Forums for user support and discussion * Wiki documentation * Package repositories * Development team == System Requirements == * x86_64 architecture * Minimum 512 MB RAM (2 GB recommended) * Minimum 2 GB storage (20 GB recommended) * Basic knowledge of command line operations * Understanding of Linux system administration [[Category:Linux Distributions]] c4960db9d8371b0bd6dcfdfff2a7eaaac9cdcd87 3000 471 1558 2025-01-04T18:35:09Z Exulan 107 Created page with "== Best SSH Security Practices == The best SSH practices can be summarized into two main principles: # Keeping unauthorized users out of your system. # Making sure potential attackers don't even know your system exists. This guide will teach you the best SSH security practices. ==== SSH Programs: Dropbear vs OpenSSH ==== There are two primary SSH programs used on Linux/Unix-based systems: '''Dropbear''' and '''OpenSSH'''. In this guide, we will focus on '''OpenSSH'''..." wikitext text/x-wiki == Best SSH Security Practices == The best SSH practices can be summarized into two main principles: # Keeping unauthorized users out of your system. # Making sure potential attackers don't even know your system exists. This guide will teach you the best SSH security practices. ==== SSH Programs: Dropbear vs OpenSSH ==== There are two primary SSH programs used on Linux/Unix-based systems: '''Dropbear''' and '''OpenSSH'''. In this guide, we will focus on '''OpenSSH'''. ==== Installing SSH ==== Installing SSH varies by system. Below are common package managers where you can download SSH: '''Debian/Ubuntu-based systems:'''<syntaxhighlight lang="bash"> sudo apt install openssh-server </syntaxhighlight> Red Hat/CentOS/Fedora-based systems: <syntaxhighlight>sudo dnf install openssh-server</syntaxhighlight> Arch Linux-based systems: <syntaxhighlight>sudo pacman -S openssh</syntaxhighlight> OpenSUSE-based systems: <syntaxhighlight>sudo zypper install openssh</syntaxhighlight> macOS (via Homebrew): <syntaxhighlight>brew install openssh</syntaxhighlight> === Securing the OpenSSH Server === ==== Changing the Port ==== By default, SSH runs on '''port 22'''. While leaving it on port 22 is acceptable, your system will be easily detected by port scanners as running SSH. To mitigate this, you can change the port. The SSH configuration file is typically located at '''/etc/ssh/sshd_config''' and is usually owned by the root user. To edit it, you must open it as root, using either '''sudo''' or '''doas'''. Once you open the '''sshd_config''' file, you should see the following line: <syntaxhighlight>#Port 22</syntaxhighlight> To modify the port, uncomment the line by removing the `#` at the beginning and then change the '''22''' to any number between '''100''' and '''65534'''. You will need to uncomment any line you change for it to come into effect. For example: <syntaxhighlight>Port 2345</syntaxhighlight> Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> Once the change is made, you have successfully modified the port. To log in using the new port, use the following command: <syntaxhighlight><username>@<address> -p 2345</syntaxhighlight> ==== Key Authentication ==== Key-based authentication is a much safer alternative to using a password. Instead of entering a password to log in, you'll use a key pair: a '''private key''' that stays on your system and a '''public key''' that you store on the server. ===== How Key Authentication Works ===== Imagine you have a door with a lock. The private key is like your physical key, while the public key is the lock on the door. When the correct key is inserted, the door unlocks. This is essentially how key authentication works. * Prevents brute-force attacks. * Allows passwordless login (like Single Sign-On). * Requires each user to have a unique key pair. ==== Setting up Key Authentication ==== ===== Generating the Key Files ===== 1. On any Unix/Linux system, type the following command: <syntaxhighlight>ssh-keygen</syntaxhighlight> 2. You will be prompted to specify where to save the key files: <syntaxhighlight> Generating public/private ed25519 key pair. Enter file in which to save the key (/home/name/.ssh/id_ed25519): </syntaxhighlight> '''Example:''' <syntaxhighlight> Enter file in which to save the key (/home/name/.ssh/id_ed25519): /home/name/Desktop/key </syntaxhighlight> This will save both the public and private key files on your desktop under the name '''key'''. 3. You will be asked to set a passphrase for the key. If you trust the environment where the key is stored, you can leave it empty by pressing '''Enter'''. Alternatively, you can set a passphrase to add an extra layer of security. <syntaxhighlight> Enter passphrase for "/home/name/Desktop/key" (empty for no passphrase): </syntaxhighlight> 4. Once complete, the keys will be saved in the specified location: <syntaxhighlight> Your identification has been saved in /home/name/Desktop/key Your public key has been saved in /home/name/Desktop/key.pub The key fingerprint is: SHA256:I60X50p2/VwZ6MHhEqx8rWNse0pC5/vewW1i4tLufQ8 name@pc The key's randomart image is: +--[ED25519 256]--+ | | | . | | o . | | .. . = o | | . S+.+ * . | | o.==.+ o +| | . +.oXo.E++| | + o*.=B.=o| | . BOo+oo| +----[SHA256]-----+ </syntaxhighlight> Do not worry about the '''randomart''' as it has no functional purpose. 5. You now have two files: * key – This is your '''private key''' (keep this secure and never share it). * key.pub – This is your '''public key''' (place this on the server). The private key should stay on the machine you will use to access the server. ===== Securing the Server with Key Authentication ===== 1. Log in to the server you want to protect with key authentication. 2. Open the SSH configuration file: <syntaxhighlight> sudo nano /etc/ssh/sshd_config </syntaxhighlight> 3. Modify the following lines: <syntaxhighlight> #PermitRootLogin prohibit-password #PasswordAuthentication yes </syntaxhighlight> to: <syntaxhighlight> PermitRootLogin no PasswordAuthentication no </syntaxhighlight> This prevents root login over SSH, disables password login and forces key-based authentication. 4. Save and exit the file. 5. Go to the home directory of the user you wish to secure with key authentication. Create the '''.ssh''' directory (if it doesn't exist), then create the '''authorized_keys''' file inside it: <syntaxhighlight> mkdir -p ~/.ssh nano ~/.ssh/authorized_keys </syntaxhighlight> Paste the entire contents of the `.pub` file into this document and save it. 6. Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> '''DO NOT LOG OUT UNTIL YOU CONFRIM THE CONFIGURATION IS CORRECT TO AVOID BEING LOCKED OUT.''' 7. Open another terminal window on the machine you will use to SSH into the server and test the connection: <syntaxhighlight> ssh <user>@<address> -i /location/to/private/key/file </syntaxhighlight> If you can log in without a password, the key authentication system is correctly configured! 9d2a175dca6791be8946380b832412a8cac1cf9c 4 327 1559 1504 2025-01-05T13:30:09Z Test 63 wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen electron was here potato testing testing 1 2 3 4<ref>hi</ref> 1461fab984fe028a44b9e2fa857152a607ec3623 5 472 1560 2025-01-05T13:31:04Z Test 63 /* test */ new section wikitext text/x-wiki == test == test [[User:Test|Test]] ([[User talk:Test|talk]]) 13:31, 5 January 2025 (UTC) 38079a2ee99feb818f91387ee87a6f76fda4133e 0 1 1561 1475 2025-01-05T13:33:35Z Atmois 13 wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from new/untrusted users will require approval from a administrator or a Trusted User. You can find more information on our standards at [[Contributing]]. You can become a trusted user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to a Trusted User. There are no formal requirements for becoming trusted, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are a trusted user, you may set the "authorized" revision to the previous one, but do note other trusted users can override this. Always, if possible, avoid edit wars and contact an admin who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * tess(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 81940f1afec52b6682367f9294241df5898147f6 0 474 1564 2025-01-05T14:23:39Z Imnotpolar 112 Redirect to [Multi-Booting](https://atl.wiki/Multi-booting) wikitext text/x-wiki #REDIRECT [[Multi Booting]] cf81ca64bbf4d487f6b5f5c5dd2aebbe203352ba 0 475 1565 2025-01-05T14:24:57Z Imnotpolar 112 Redirect to [Multi-Booting](https://atl.wiki/Multi-booting) wikitext text/x-wiki #REDIRECT [[Multi-Booting]] 00fda6d12664ea1d75bbceb068bc74264a2e56d6 1566 1565 2025-01-05T14:26:08Z Imnotpolar 112 Fixed redirect to correct page wikitext text/x-wiki #REDIRECT [[Multi-booting]] 863d11e9594a2c3b97086140e15812164f4855d4 1572 1566 2025-01-05T14:56:23Z Atmois 13 Changed redirect target from [[Multi-booting]] to [[Multi Booting]] wikitext text/x-wiki #REDIRECT [[Multi Booting]] cf81ca64bbf4d487f6b5f5c5dd2aebbe203352ba 0 297 1567 1220 2025-01-05T14:54:17Z Atmois 13 Merge pages wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref>. The core concept of multi-booting revolves around partitioning a computer’s storage device, whether it be a HDD, SSD (sda/nvme), or eMMC.<ref name=":03" /> Each operating system requires its own partition, effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with UEFI (Unified Extensible Firmware Interface), an additional EFI System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref>, including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing software that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == How to Multi-boot == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen distribution search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitons"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-Boot|Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! <references /> [[Category:Terminology]] b43a98614e06d6ba162c3a4bcd74a8436b250297 1569 1567 2025-01-05T14:55:21Z Atmois 13 Atmois moved page [[Multi-booting]] to [[Multi Booting]]: Misspelled title wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref>. The core concept of multi-booting revolves around partitioning a computer’s storage device, whether it be a HDD, SSD (sda/nvme), or eMMC.<ref name=":03" /> Each operating system requires its own partition, effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with UEFI (Unified Extensible Firmware Interface), an additional EFI System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref>, including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing software that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == How to Multi-boot == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen distribution search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitons"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-Boot|Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! <references /> [[Category:Terminology]] b43a98614e06d6ba162c3a4bcd74a8436b250297 1576 1569 2025-01-05T20:04:31Z Atmois 13 wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref>. The core concept of multi-booting revolves around partitioning a computer’s storage device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own partition, effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with UEFI (Unified Extensible Firmware Interface), an additional EFI System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref>, including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing software that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == How to Multi-boot == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen distribution search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitons"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-Boot|Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! <references /> [[Category:Terminology]] ee008e1194fb4611eeb9edbf1b9bb5b268b09e50 14 476 1568 2025-01-05T14:54:17Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Pages with reference errors" as well as all subcategories of category "Pages with reference errors" if any exist. d0aae94a335d0eda6604510304e4796f8e801f0b 0 477 1570 2025-01-05T14:55:21Z Atmois 13 Atmois moved page [[Multi-booting]] to [[Multi Booting]]: Misspelled title wikitext text/x-wiki #REDIRECT [[Multi Booting]] cf81ca64bbf4d487f6b5f5c5dd2aebbe203352ba 0 301 1571 1045 2025-01-05T14:56:14Z Atmois 13 Changed redirect target from [[Multi-booting]] to [[Multi Booting]] wikitext text/x-wiki #REDIRECT [[Multi Booting]] cf81ca64bbf4d487f6b5f5c5dd2aebbe203352ba 0 334 1573 1191 2025-01-05T14:56:29Z Atmois 13 Changed redirect target from [[Multi-booting]] to [[Multi Booting]] wikitext text/x-wiki #REDIRECT [[Multi Booting]] cf81ca64bbf4d487f6b5f5c5dd2aebbe203352ba 0 182 1575 907 2025-01-05T16:47:47Z Gurov 103 Reorganized, new sections about features, release cycles and installation methods. wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, [[Xfce]], [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a [[Linux Distributions|Linux distribution]] developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> == History == Debian adheres to the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> In 1997, the Debian Project established Software in the Public Interest as a nonprofit organization to provide ongoing financial support. However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> == Features == === Release Cycle === Debian maintains three primary development branches: * Stable - The current official release, recommended for production systems * Testing - The next planned stable release, featuring newer software versions * Unstable (Sid) - The rolling development branch where new packages are initially introduced === Package Management System === Debian uses the [[APT]] (Advanced Package Tool) built on top of [[dpkg]], featuring: * Over 59,000 ready-to-install software packages * Multiple repository sections (main, contrib, non-free) * Secure package verification through signed repositories * Sophisticated dependency resolution === Project Management === The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as: * The Debian Social Contract * The Debian Constitution * The Debian Free Software Guidelines === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[Window Manager|Window Managers]] instead of [[Desktop Environment|Desktop Environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /> == Installation == Debian provides multiple installation methods: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Live images for testing before installation * Architecture-specific installers * Cloud images for virtual deployment <references /> [[Category:Linux Distributions]] b7dea4263d55215ac7882c914998cc0248ef196e 6 479 1578 2025-01-05T22:33:53Z 2elevation 115 wikitext text/x-wiki The Oreon Logo 6c210cc666c689159c5f3d13994ff83ba85fa390 1580 1578 2025-01-05T23:08:58Z Atmois 13 Atmois moved page [[File:Oreonlogo1.png]] to [[File:Oreonlogo.png]]: typo wikitext text/x-wiki The Oreon Logo 6c210cc666c689159c5f3d13994ff83ba85fa390 6 478 1577 2025-01-05T22:42:19Z 2elevation 115 wikitext text/x-wiki Oreon 10 8455109b512cc1429037a23255674864081c10aa 0 480 1579 2025-01-05T23:01:09Z 2elevation 115 Oreon Linux wikitext text/x-wiki {{DistributionInfobox |title=Oreon Linux |image=[[File:OreonLogo.png|Oreon_logo]] |caption=Oreon logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}} [[File:oreon10.png|thumb|Oreon 10 Core running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>https://oreonproject.org/</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>https://git.oreonproject.org/rpms</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>https://boostyconnect.com/oreon-lime-r1-lifecycle/</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>https://oreonproject.org/oreon-lime-r2-support-timeline/</ref><ref>https://oreonproject.org/oreon-lime-r2/</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/</ref> and other well-known sources. In October 2024, Oreon celebrated it's 1st anniversary on November 16, 2024 and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69</ref> Oreon 10 released to the public on December 12, 2024 shipping with KDE Plasma 6 and Linux 6.11<ref>https://forums.oreonproject.org/t/oreon-10-officially-released/98</ref> but was upgraded to 6.12 a few days later. On December 20, 2024, Oreon annouced that they will be going fully independent for it's next major release<ref>https://forums.oreonproject.org/t/oreon-is-going-fully-independent/118</ref> and will be built entirely from scratch. 4406bd13b9aace2ba3ca3d299cdaab1171039a11 1582 1579 2025-01-05T23:09:46Z Atmois 13 fix image wikitext text/x-wiki {{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|Oreon_logo]] |caption=Oreon logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}} [[File:oreon10.png|thumb|Oreon 10 Core running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>https://oreonproject.org/</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>https://git.oreonproject.org/rpms</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>https://boostyconnect.com/oreon-lime-r1-lifecycle/</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>https://oreonproject.org/oreon-lime-r2-support-timeline/</ref><ref>https://oreonproject.org/oreon-lime-r2/</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/</ref> and other well-known sources. In October 2024, Oreon celebrated it's 1st anniversary on November 16, 2024 and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69</ref> Oreon 10 released to the public on December 12, 2024 shipping with KDE Plasma 6 and Linux 6.11<ref>https://forums.oreonproject.org/t/oreon-10-officially-released/98</ref> but was upgraded to 6.12 a few days later. On December 20, 2024, Oreon annouced that they will be going fully independent for it's next major release<ref>https://forums.oreonproject.org/t/oreon-is-going-fully-independent/118</ref> and will be built entirely from scratch. f437b053c0c3fa6c03103bc94a6fd5d73b2dbb71 1583 1582 2025-01-05T23:10:40Z Atmois 13 fix formatting wikitext text/x-wiki {{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|thumb|Oreon_logo]] |caption=Oreon logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}} [[File:oreon10.png|thumb|Oreon 10 Core running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>https://oreonproject.org/</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>https://git.oreonproject.org/rpms</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>https://boostyconnect.com/oreon-lime-r1-lifecycle/</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>https://oreonproject.org/oreon-lime-r2-support-timeline/</ref><ref>https://oreonproject.org/oreon-lime-r2/</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/</ref> and other well-known sources. In October 2024, Oreon celebrated it's 1st anniversary on November 16, 2024 and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69</ref> Oreon 10 released to the public on December 12, 2024 shipping with KDE Plasma 6 and Linux 6.11<ref>https://forums.oreonproject.org/t/oreon-10-officially-released/98</ref> but was upgraded to 6.12 a few days later. On December 20, 2024, Oreon annouced that they will be going fully independent for it's next major release<ref>https://forums.oreonproject.org/t/oreon-is-going-fully-independent/118</ref> and will be built entirely from scratch. e92af92dc271d5fc0ff32cd63e5ac9abc86ca522 1584 1583 2025-01-05T23:11:43Z Atmois 13 add category and fix typo wikitext text/x-wiki {{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}} [[File:oreon10.png|thumb|Oreon 10 Core running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>https://oreonproject.org/</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>https://git.oreonproject.org/rpms</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>https://boostyconnect.com/oreon-lime-r1-lifecycle/</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>https://oreonproject.org/oreon-lime-r2-support-timeline/</ref><ref>https://oreonproject.org/oreon-lime-r2/</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/</ref> and other well-known sources. In October 2024, Oreon celebrated it's 1st anniversary on November 16, 2024 and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69</ref> Oreon 10 released to the public on December 12, 2024 shipping with KDE Plasma 6 and Linux 6.11<ref>https://forums.oreonproject.org/t/oreon-10-officially-released/98</ref> but was upgraded to 6.12 a few days later. On December 20, 2024, Oreon annouced that they will be going fully independent for it's next major release<ref>https://forums.oreonproject.org/t/oreon-is-going-fully-independent/118</ref> and will be built entirely from scratch. <references /> [[Category:Linux Distributions]] 28bc38fcac2713e419bddcf3c8d1c50cb74bebcc 828 501 1626 2025-01-06T01:13:43Z starcitizen>Alistar Bot 0 /* top */ clean up, replaced: --border-radius--medium → --border-radius-medium (2), --box-shadow-dialog → --box-shadow-drop-xx-large (2) sanitized-css text/css .mbox { position: relative; display: flex; flex-direction: column; margin-block: var( --space-md ); background-color: var( --color-surface-2 ); border: 1px solid var( --border-color-base ); border-radius: var( --border-radius-medium ); font-size: var( --font-size-small ); line-height: var( --line-height-xx-small ); } .mbox.mbox-high { background-color: var( --background-color-destructive-subtle ); } .mbox.mbox-med { background-color: var( --background-color-warning-subtle ); } .mbox-title { display: flex; align-items: center; padding: var( --space-sm ) var( --space-md ); } .mbox-icon img { display: block; width: var( --font-size-small ); height: auto; margin-right: var( --space-xs ); opacity: var( --opacity-icon-base ); filter: var( --filter-invert ); } .mbox-text { position: absolute; top: 100%; z-index: 10; padding: var( --space-md ); width: 100%; box-sizing: border-box; background-color: var( --color-surface-1 ); border-bottom-left-radius: var( --border-radius-medium ); border-bottom-right-radius: var( --border-radius-medium ); box-shadow: var( --box-shadow-drop-xx-large ); opacity: 0; visibility: hidden; } .mbox:hover { /* Merge with popup */ border-bottom-left-radius: 0; border-bottom-right-radius: 0; box-shadow: var( --box-shadow-drop-xx-large ); } .mbox:hover .mbox-text { opacity: 1; visibility: visible; } 923ac6043b5bf4cc551e119cfe089ba65b17b1ec 1627 1626 2025-01-08T11:01:47Z Atmois 13 1 revision imported sanitized-css text/css .mbox { position: relative; display: flex; flex-direction: column; margin-block: var( --space-md ); background-color: var( --color-surface-2 ); border: 1px solid var( --border-color-base ); border-radius: var( --border-radius-medium ); font-size: var( --font-size-small ); line-height: var( --line-height-xx-small ); } .mbox.mbox-high { background-color: var( --background-color-destructive-subtle ); } .mbox.mbox-med { background-color: var( --background-color-warning-subtle ); } .mbox-title { display: flex; align-items: center; padding: var( --space-sm ) var( --space-md ); } .mbox-icon img { display: block; width: var( --font-size-small ); height: auto; margin-right: var( --space-xs ); opacity: var( --opacity-icon-base ); filter: var( --filter-invert ); } .mbox-text { position: absolute; top: 100%; z-index: 10; padding: var( --space-md ); width: 100%; box-sizing: border-box; background-color: var( --color-surface-1 ); border-bottom-left-radius: var( --border-radius-medium ); border-bottom-right-radius: var( --border-radius-medium ); box-shadow: var( --box-shadow-drop-xx-large ); opacity: 0; visibility: hidden; } .mbox:hover { /* Merge with popup */ border-bottom-left-radius: 0; border-bottom-right-radius: 0; box-shadow: var( --box-shadow-drop-xx-large ); } .mbox:hover .mbox-text { opacity: 1; visibility: visible; } 923ac6043b5bf4cc551e119cfe089ba65b17b1ec 0 1 1585 1561 2025-01-06T20:52:46Z Atmois 13 update info wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from newer users will require approval from a administrator or a Moderator. You can find more information on our standards at [[Contributing]]. You can become an Auto-Moderated User in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to an Auto-Moderated User. There are no formal requirements for becoming an Auto-Moderated User, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the Discord server or the FOSS community.  If you do not have Discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an Auto-Moderated User, you may set the "authorized" revision to the previous one, but do note other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * tess(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ f541a5f3f75c7f15cffda9e63f8bdc85fe0e888c 1586 1585 2025-01-06T21:10:44Z Atmois 13 Fix capatalisation wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from newer users will require approval from a administrator or a moderator. You can find more information on our standards at [[Contributing]]. You can become an auto-moderated user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to an auto-moderated user. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community.  If you do not have discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an auto-moderated user, you may set the "authorised" revision to the previous one, but do note other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-pub channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * tess(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 59bcd976ab207764992c32bd02a950d2c1de3a8e 10 482 1587 2025-01-08T10:47:56Z Atmois 13 Create template wikitext text/x-wiki <templatedata> { "params": {}, "description": "Place on articles which references or lists commands the user can use on their system.\n\n", "format": "inline" } </templatedata> ca2b116d1288ae781e2dc775c80f0dc5d20ef793 10 483 1589 1588 2025-01-08T11:01:45Z Atmois 13 1 revision imported wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:WikimediaUI-Alert.svg|14px|link=]]</span>This article or section may require a cleanup.</span> <div class="mbox-text">It might not meet the Star Citizen Wiki's [[Star Citizen:Style guide|quality standards]]. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Pages needing cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages needing cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> 532d1e265425e5ef6f23b1ecccd22e18c3464717 1644 1589 2025-01-08T21:54:57Z Atmois 13 Add template wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup.</span> <div class="mbox-text">It might not meet the wiki's [[Contributing#Standards|quality standards]]. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Pages needing cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages needing cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> 8a3f33a631eb9438b5d0733761d867c1a89746fe 1649 1644 2025-01-10T11:05:59Z Atmois 13 Tidy up wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified.}}</span> <div class="mbox-text">It might not meet the wiki's [[Contributing#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Pages needing cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages needing cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> a9a88e65aabae3e6489f022675097aeb58c051c0 828 359 1591 1361 2025-01-08T11:01:45Z Atmois 13 1 revision imported Scribunto text/plain -- This module provides easy processing of arguments passed to Scribunto from -- #invoke. It is intended for use by other Lua modules, and should not be -- called from #invoke directly. local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local arguments = {} -- Generate four different tidyVal functions, so that we don't have to check the -- options every time we call it. local function tidyValDefault(key, val) if type(val) == 'string' then val = val:match('^%s*(.-)%s*$') if val == '' then return nil else return val end else return val end end local function tidyValTrimOnly(key, val) if type(val) == 'string' then return val:match('^%s*(.-)%s*$') else return val end end local function tidyValRemoveBlanksOnly(key, val) if type(val) == 'string' then if val:find('%S') then return val else return nil end else return val end end local function tidyValNoChange(key, val) return val end local function matchesTitle(given, title) local tp = type( given ) return (tp == 'string' or tp == 'number') and mw.title.new( given ).prefixedText == title end local translate_mt = { __index = function(t, k) return k end } function arguments.getArgs(frame, options) checkType('getArgs', 1, frame, 'table', true) checkType('getArgs', 2, options, 'table', true) frame = frame or {} options = options or {} --[[ -- Set up argument translation. --]] options.translate = options.translate or {} if getmetatable(options.translate) == nil then setmetatable(options.translate, translate_mt) end if options.backtranslate == nil then options.backtranslate = {} for k,v in pairs(options.translate) do options.backtranslate[v] = k end end if options.backtranslate and getmetatable(options.backtranslate) == nil then setmetatable(options.backtranslate, { __index = function(t, k) if options.translate[k] ~= k then return nil else return k end end }) end --[[ -- Get the argument tables. If we were passed a valid frame object, get the -- frame arguments (fargs) and the parent frame arguments (pargs), depending -- on the options set and on the parent frame's availability. If we weren't -- passed a valid frame object, we are being called from another Lua module -- or from the debug console, so assume that we were passed a table of args -- directly, and assign it to a new variable (luaArgs). --]] local fargs, pargs, luaArgs if type(frame.args) == 'table' and type(frame.getParent) == 'function' then if options.wrappers then --[[ -- The wrappers option makes Module:Arguments look up arguments in -- either the frame argument table or the parent argument table, but -- not both. This means that users can use either the #invoke syntax -- or a wrapper template without the loss of performance associated -- with looking arguments up in both the frame and the parent frame. -- Module:Arguments will look up arguments in the parent frame -- if it finds the parent frame's title in options.wrapper; -- otherwise it will look up arguments in the frame object passed -- to getArgs. --]] local parent = frame:getParent() if not parent then fargs = frame.args else local title = parent:getTitle():gsub('/sandbox$', '') local found = false if matchesTitle(options.wrappers, title) then found = true elseif type(options.wrappers) == 'table' then for _,v in pairs(options.wrappers) do if matchesTitle(v, title) then found = true break end end end -- We test for false specifically here so that nil (the default) acts like true. if found or options.frameOnly == false then pargs = parent.args end if not found or options.parentOnly == false then fargs = frame.args end end else -- options.wrapper isn't set, so check the other options. if not options.parentOnly then fargs = frame.args end if not options.frameOnly then local parent = frame:getParent() pargs = parent and parent.args or nil end end if options.parentFirst then fargs, pargs = pargs, fargs end else luaArgs = frame end -- Set the order of precedence of the argument tables. If the variables are -- nil, nothing will be added to the table, which is how we avoid clashes -- between the frame/parent args and the Lua args. local argTables = {fargs} argTables[#argTables + 1] = pargs argTables[#argTables + 1] = luaArgs --[[ -- Generate the tidyVal function. If it has been specified by the user, we -- use that; if not, we choose one of four functions depending on the -- options chosen. This is so that we don't have to call the options table -- every time the function is called. --]] local tidyVal = options.valueFunc if tidyVal then if type(tidyVal) ~= 'function' then error( "bad value assigned to option 'valueFunc'" .. '(function expected, got ' .. type(tidyVal) .. ')', 2 ) end elseif options.trim ~= false then if options.removeBlanks ~= false then tidyVal = tidyValDefault else tidyVal = tidyValTrimOnly end else if options.removeBlanks ~= false then tidyVal = tidyValRemoveBlanksOnly else tidyVal = tidyValNoChange end end --[[ -- Set up the args, metaArgs and nilArgs tables. args will be the one -- accessed from functions, and metaArgs will hold the actual arguments. Nil -- arguments are memoized in nilArgs, and the metatable connects all of them -- together. --]] local args, metaArgs, nilArgs, metatable = {}, {}, {}, {} setmetatable(args, metatable) local function mergeArgs(tables) --[[ -- Accepts multiple tables as input and merges their keys and values -- into one table. If a value is already present it is not overwritten; -- tables listed earlier have precedence. We are also memoizing nil -- values, which can be overwritten if they are 's' (soft). --]] for _, t in ipairs(tables) do for key, val in pairs(t) do if metaArgs[key] == nil and nilArgs[key] ~= 'h' then local tidiedVal = tidyVal(key, val) if tidiedVal == nil then nilArgs[key] = 's' else metaArgs[key] = tidiedVal end end end end end --[[ -- Define metatable behaviour. Arguments are memoized in the metaArgs table, -- and are only fetched from the argument tables once. Fetching arguments -- from the argument tables is the most resource-intensive step in this -- module, so we try and avoid it where possible. For this reason, nil -- arguments are also memoized, in the nilArgs table. Also, we keep a record -- in the metatable of when pairs and ipairs have been called, so we do not -- run pairs and ipairs on the argument tables more than once. We also do -- not run ipairs on fargs and pargs if pairs has already been run, as all -- the arguments will already have been copied over. --]] metatable.__index = function (t, key) --[[ -- Fetches an argument when the args table is indexed. First we check -- to see if the value is memoized, and if not we try and fetch it from -- the argument tables. When we check memoization, we need to check -- metaArgs before nilArgs, as both can be non-nil at the same time. -- If the argument is not present in metaArgs, we also check whether -- pairs has been run yet. If pairs has already been run, we return nil. -- This is because all the arguments will have already been copied into -- metaArgs by the mergeArgs function, meaning that any other arguments -- must be nil. --]] if type(key) == 'string' then key = options.translate[key] end local val = metaArgs[key] if val ~= nil then return val elseif metatable.donePairs or nilArgs[key] then return nil end for _, argTable in ipairs(argTables) do local argTableVal = tidyVal(key, argTable[key]) if argTableVal ~= nil then metaArgs[key] = argTableVal return argTableVal end end nilArgs[key] = 'h' return nil end metatable.__newindex = function (t, key, val) -- This function is called when a module tries to add a new value to the -- args table, or tries to change an existing value. if type(key) == 'string' then key = options.translate[key] end if options.readOnly then error( 'could not write to argument table key "' .. tostring(key) .. '"; the table is read-only', 2 ) elseif options.noOverwrite and args[key] ~= nil then error( 'could not write to argument table key "' .. tostring(key) .. '"; overwriting existing arguments is not permitted', 2 ) elseif val == nil then --[[ -- If the argument is to be overwritten with nil, we need to erase -- the value in metaArgs, so that __index, __pairs and __ipairs do -- not use a previous existing value, if present; and we also need -- to memoize the nil in nilArgs, so that the value isn't looked -- up in the argument tables if it is accessed again. --]] metaArgs[key] = nil nilArgs[key] = 'h' else metaArgs[key] = val end end local function translatenext(invariant) local k, v = next(invariant.t, invariant.k) invariant.k = k if k == nil then return nil elseif type(k) ~= 'string' or not options.backtranslate then return k, v else local backtranslate = options.backtranslate[k] if backtranslate == nil then -- Skip this one. This is a tail call, so this won't cause stack overflow return translatenext(invariant) else return backtranslate, v end end end metatable.__pairs = function () -- Called when pairs is run on the args table. if not metatable.donePairs then mergeArgs(argTables) metatable.donePairs = true end return translatenext, { t = metaArgs } end local function inext(t, i) -- This uses our __index metamethod local v = t[i + 1] if v ~= nil then return i + 1, v end end metatable.__ipairs = function (t) -- Called when ipairs is run on the args table. return inext, t, 0 end return args end return arguments 3134ecce8429b810d445e29eae115e2ae4c36c53 10 487 1599 1598 2025-01-08T11:01:45Z Atmois 13 1 revision imported wikitext text/x-wiki <includeonly>{{#invoke:Documentation|doc}}__NOEDITSECTION__{{#seo: |type = website |description = {{FULLPAGENAME}} is a template page used on the Star Citizen Wiki. Templates are pages that are embedded (transcluded) into other pages to allow for the repetition of information. |site_name = Star Citizen Wiki |locale = {{PAGELANGUAGE}} }}</includeonly><noinclude>{{/doc}}</noinclude> 2690a5347936db4ace54fe94a0b3092b6bb04a37 1650 1599 2025-01-10T11:09:42Z Atmois 13 update wikitext text/x-wiki <includeonly>{{#invoke:Documentation|doc}}__NOEDITSECTION__{{ |type = website |description = {{FULLPAGENAME}} is a template page used on the ATL Wiki. Templates are pages that are embedded into other articles as reuseable elements. |site_name = ATL Wiki |locale = {{PAGELANGUAGE}} }}</includeonly><noinclude>{{/doc}}</noinclude> 04f832677890e699d88890f9cbc8494ea4a74e48 10 493 1611 1610 2025-01-08T11:01:46Z Atmois 13 1 revision imported wikitext text/x-wiki #REDIRECT [[Template:Template link expanded]] 155e901040104f96908f1f4627c4eb3501301bf9 10 494 1613 1612 2025-01-08T11:01:46Z Atmois 13 1 revision imported wikitext text/x-wiki {{Documentation}} {{t|Cleanup}} should be placed on articles or section that you believe require a cleanup. This template adds pages to [[:Category:Pages needing cleanup]]. You should always specify the reason by including a parameter. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Should be rewritten as prose", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance templates]]</includeonly> a8a80c83c546e8cedf74e332782e1e4f2b22bd4b 1651 1613 2025-01-10T11:11:27Z Atmois 13 Fix wikitext text/x-wiki {{t|Cleanup}} should be placed on articles or section that you believe require a cleanup. This template adds pages to [[:Category:Pages needing cleanup]]. You should always specify the reason by including a parameter. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Requires citation", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance templates]]</includeonly> 9fbca24ba93ce8389d8d4bb8c19830069fb1783e 1679 1651 2025-01-12T12:05:00Z Atmois 13 fix wikitext text/x-wiki This template should be placed on articles or section that you believe require a cleanup. This template adds pages to [[:Category:Pages needing cleanup]]. You should always specify the reason by including a parameter. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Requires citation", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance templates]]</includeonly> 1e179cb497a4756e035afaf6b83675abc7ee5ff2 828 495 1615 1614 2025-01-08T11:01:46Z Atmois 13 1 revision imported Scribunto text/plain -- This implements Template:Tlg local getArgs = require('Module:Arguments').getArgs local p = {} -- Is a string non-empty? local function _ne(s) return s ~= nil and s ~= "" end local nw = mw.text.nowiki local function addTemplate(s) local i, _ = s:find(':', 1, true) if i == nil then return 'Template:' .. s end local ns = s:sub(1, i - 1) if ns == '' or mw.site.namespaces[ns] then return s else return 'Template:' .. s end end local function trimTemplate(s) local needle = 'template:' if s:sub(1, needle:len()):lower() == needle then return s:sub(needle:len() + 1) else return s end end local function linkTitle(args) if _ne(args.nolink) then return args['1'] end local titleObj local titlePart = '[[' if args['1'] then -- This handles :Page and other NS titleObj = mw.title.new(args['1'], 'Template') else titleObj = mw.title.getCurrentTitle() end titlePart = titlePart .. (titleObj ~= nil and titleObj.fullText or addTemplate(args['1'])) local textPart = args.alttext if not _ne(textPart) then if titleObj ~= nil then textPart = titleObj:inNamespace("Template") and args['1'] or titleObj.fullText else -- redlink textPart = args['1'] end end if _ne(args.subst) then -- HACK: the ns thing above is probably broken textPart = 'subst:' .. textPart end if _ne(args.brace) then textPart = nw('{{') .. textPart .. nw('}}') elseif _ne(args.braceinside) then textPart = nw('{') .. textPart .. nw('}') end titlePart = titlePart .. '|' .. textPart .. ']]' if _ne(args.braceinside) then titlePart = nw('{') .. titlePart .. nw('}') end return titlePart end function p.main(frame) local args = getArgs(frame, { trim = true, removeBlanks = false }) return p._main(args) end function p._main(args) local bold = _ne(args.bold) or _ne(args.boldlink) or _ne(args.boldname) local italic = _ne(args.italic) or _ne(args.italics) local dontBrace = _ne(args.brace) or _ne(args.braceinside) local code = _ne(args.code) or _ne(args.tt) local show_result = _ne(args._show_result) local expand = _ne(args._expand) -- Build the link part local titlePart = linkTitle(args) if bold then titlePart = "'''" .. titlePart .. "'''" end if _ne(args.nowrapname) then titlePart = '<span class="nowrap">' .. titlePart .. '</span>' end -- Build the arguments local textPart = "" local textPartBuffer = "&#124;" local codeArguments = {} local codeArgumentsString = "" local i = 2 local j = 1 while args[i] do local val = args[i] if val ~= "" then if _ne(args.nowiki) then -- Unstrip nowiki tags first because calling nw on something that already contains nowiki tags will -- mangle the nowiki strip marker and result in literal UNIQ...QINU showing up val = nw(mw.text.unstripNoWiki(val)) end local k, v = string.match(val, "(.*)=(.*)") if not k then codeArguments[j] = val j = j + 1 else codeArguments[k] = v end codeArgumentsString = codeArgumentsString .. textPartBuffer .. val if italic then val = '<span style="font-style:italic;">' .. val .. '</span>' end textPart = textPart .. textPartBuffer .. val end i = i + 1 end -- final wrap local ret = titlePart .. textPart if not dontBrace then ret = nw('{{') .. ret .. nw('}}') end if _ne(args.a) then ret = nw('*') .. '&nbsp;' .. ret end if _ne(args.kbd) then ret = '<kbd>' .. ret .. '</kbd>' end if code then ret = '<code>' .. ret .. '</code>' elseif _ne(args.plaincode) then ret = '<code style="border:none;background:transparent;">' .. ret .. '</code>' end if _ne(args.nowrap) then ret = '<span class="nowrap">' .. ret .. '</span>' end --[[ Wrap as html?? local span = mw.html.create('span') span:wikitext(ret) --]] if _ne(args.debug) then ret = ret .. '\n<pre>' .. mw.text.encode(mw.dumpObject(args)) .. '</pre>' end if show_result then local result = mw.getCurrentFrame():expandTemplate{title = addTemplate(args[1]), args = codeArguments} ret = ret .. " → " .. result end if expand then local query = mw.text.encode('{{' .. addTemplate(args[1]) .. string.gsub(codeArgumentsString, textPartBuffer, "|") .. '}}') local url = mw.uri.fullUrl('special:ExpandTemplates', 'wpInput=' .. query) mw.log() ret = ret .. " [" .. tostring(url) .. "]" end return ret end return p c7307fa3959d308a2dd7fd2f5009c1ce6db3d122 10 498 1621 1620 2025-01-08T11:01:46Z Atmois 13 1 revision imported wikitext text/x-wiki {{#Invoke:Template link general|main|code=on}}<noinclude> {{/doc}} <!-- Add categories to the /doc subpage, not here! --> </noinclude> f49d86d852e8c15c4ffa3f08e7f33ddfb0920b22 828 500 1625 1624 2025-01-08T11:01:47Z Atmois 13 1 revision imported Scribunto text/plain local libraryUtil = require( 'libraryUtil' ) local checkType = libraryUtil.checkType local mArguments -- lazily initialise [[Module:Arguments]] local mError -- lazily initialise [[Module:Error]] local p = {} --- Helper function to throw error -- -- @param msg string - Error message -- -- @return string - Formatted error message in wikitext local function makeWikitextError( msg ) mError = require( 'Module:Error' ) return mError.error { message = 'Error: ' .. msg .. '.' } end function p.mbox( frame ) mArguments = require( 'Module:Arguments' ) local args = mArguments.getArgs( frame ) local title = args[ 1 ] or args[ 'title' ] local text = args[ 2 ] or args[ 'text' ] if not title or not text then return makeWikitextError( 'no title or text specified' ) end return p._mbox( title, text, { extraclasses = args.extraclasses, icon = args.icon } ) end function p._mbox( title, text, options ) checkType( '_mbox', 1, title, 'string' ) checkType( '_mbox', 2, text, 'string' ) checkType( '_mbox', 3, options, 'table', true ) options = options or {} local mbox = mw.html.create( 'div' ) local extraclasses if type( options.extraclasses ) == 'string' then extraclasses = options.extraclasses end mbox :attr( 'role', 'presentation' ) :addClass( 'mbox' ) :addClass( extraclasses ) local mboxTitle = mbox:tag( 'div' ):addClass( 'mbox-title' ) if options.icon and type( options.icon ) == 'string' then mboxTitle:tag( 'div' ) :addClass( 'mbox-icon metadata' ) :wikitext( '[[File:' .. options.icon .. '|14px|link=]]' ) :done() :tag( 'div' ) :wikitext( title ) else mboxTitle:wikitext( title ) end mbox:tag( 'div' ) :addClass( 'mbox-text' ) :wikitext( text ) return mw.getCurrentFrame():extensionTag { name = 'templatestyles', args = { src = 'Module:Mbox/styles.css' } } .. tostring( mbox ) end return p 5d52ff50f2eed059dbc7aa4785a15ffbb32347c1 6 510 1642 2025-01-08T14:43:46Z Atmois 13 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 511 1643 2025-01-08T21:03:30Z Atmois 13 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 10 513 1646 2025-01-08T22:53:21Z Electron271 3 Created page with "<div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations. (hover for more information)</span> <div class="mbox-text">This article was most likely made before strict rules for citations were implemented [[Contributing#Citations|(Read here)]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{P..." wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations. (hover for more information)</span> <div class="mbox-text">This article was most likely made before strict rules for citations were implemented [[Contributing#Citations|(Read here)]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:No Citations]] for other pages that still need to be edited.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:No Citations]]</includeonly><noinclude> {{/doc}}</noinclude> 343ab1c174dba5aa33943a8de5b1182bbf105cd7 10 514 1647 2025-01-08T22:55:22Z Electron271 3 Created page with "{{Documentation}} {{t|No Citations}} should be placed on articles or section with little to no citations. This template adds pages to [[:Category:No Citations]]. == Usage == <code>{{tlx|No Citations}}</code> <includeonly>[[Category:Maintenance templates]]</includeonly>" wikitext text/x-wiki {{Documentation}} {{t|No Citations}} should be placed on articles or section with little to no citations. This template adds pages to [[:Category:No Citations]]. == Usage == <code>{{tlx|No Citations}}</code> <includeonly>[[Category:Maintenance templates]]</includeonly> 9da2b595b68a00ecf146890f33cbaf435eaac6c2 1661 1647 2025-01-11T18:25:52Z Atmois 13 remove old template wikitext text/x-wiki {{t|No Citations}} should be placed on articles or section with little to no citations. This template adds pages to [[:Category:No Citations]]. == Usage == <code>{{tlx|No Citations}}</code> <includeonly>[[Category:Maintenance templates]]</includeonly> 58749199642dceafd05828b1d80748ceccc7baa9 1680 1661 2025-01-12T12:05:12Z Atmois 13 fix wikitext text/x-wiki This template should be placed on articles or section with little to no citations. This template adds pages to [[:Category:No Citations]]. == Usage == <code>{{tlx|No Citations}}</code> <includeonly>[[Category:Maintenance templates]]</includeonly> bced771258819a195ddefe8317731c0e98a1eebe 14 515 1648 2025-01-08T22:55:22Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Category template documentation" as well as all subcategories of category "Category template documentation" if any exist. 94b447bfcbbc1f79230f325e4be9a4269dec355c 0 516 1652 2025-01-11T02:11:46Z Scottc96 18 Added systemd page wikitext text/x-wiki <nowiki>#</nowiki> Understanding Systemd Systemd is an init system and service manager used by many modern Linux distributions. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are **units**, which represent resources or services that systemd manages. Each unit is defined by a **unit file**, which specifies its behavior, configuration, and how it interacts with other units. --- <nowiki>##</nowiki> Why Systemd? Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here’s how Systemd differs: - **Parallel Startup**: Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. - **Centralized Management**: Systemd provides a unified system for managing services, devices, logs, and even network interfaces. - **Dependency Management**: Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. - **Logging**: Systemd integrates a powerful logging system, the **journal**, which makes it easier to manage and analyze logs. --- <nowiki>##</nowiki> Key Concepts in Systemd Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: - **Unit**: A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a **unit file**, which defines how it should behave and interact with other components. - **Unit File**: Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit’s dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. - **Service**: A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. - **Target**: Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. - **Systemd Init**: The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. - **Systemd Daemon**: The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. - **Systemd Journal**: A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. --- <nowiki>#</nowiki> Essential Systemd Commands Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands: - **systemctl**: This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. - **journalctl**: Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. - **timedatectl**: This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. - **hostnamectl**: With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. - **networkctl**: This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. --- <nowiki>##</nowiki> Getting Started with Systemd Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: <nowiki>###</nowiki> Managing Services - **Starting a Service**: To start a service, use the following command:   ```bash   systemctl start service-name   ```   *Example*: To start the Apache web server, you would run:   ```bash   systemctl start apache2   ``` - **Stopping a Service**: To stop a running service, use:   ```bash   systemctl stop service-name   ```   *Example*: To stop the Apache web server, you would run:   ```bash   systemctl stop apache2   ``` - **Restarting a Service**: To restart a service, use:   ```bash   systemctl restart service-name   ```   *Example*: To restart the Apache web server, you would run:   ```bash   systemctl restart apache2   ``` - **Enabling a Service**: To ensure a service starts automatically at boot, use:   ```bash   systemctl enable service-name   ```   *Example*: To enable the Apache web server to start at boot, you would run:   ```bash   systemctl enable apache2   ``` - **Disabling a Service**: To prevent a service from starting at boot, use:   ```bash   systemctl disable service-name   ```   *Example*: To disable the Apache web server from starting at boot, you would run:   ```bash   systemctl disable apache2   ``` --- <nowiki>##</nowiki> What Are Units?   Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. <nowiki>###</nowiki> Where Are Unit Files Stored? 1. **System Directory**     The primary location for system-wide unit files is the `/lib/systemd/system/` directory.     - This is where unit files are automatically installed when software packages are added to the system.     - **Important**: Do not modify files in this directory, as they may be replaced during software updates. 2. **Custom Directory**     To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there.     - Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. **Runtime Directory**     The `/run/systemd/system/` directory is used for temporary unit file changes during system operation.     - Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session.     - **Note**: Any changes made here are not saved and will be lost after a system reboot. <nowiki>###</nowiki> Types of Units   The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: | **Suffix**      | **Function**                                                                                                  | |------------------|--------------------------------------------------------------------------------------------------------------| | `.automount`     | Automatically mounts a specified file system when accessed, requiring a corresponding `.mount` unit.         | | `.device`        | Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs.     | | `.mount`         | Defines a specific mount point for file systems, with units named according to the mount path.               | | `.path`          | Specifies a file system path that triggers activation of other units when changes are detected.               | | `.scope`         | Created by systemd to manage groups of processes based on information from system bus interfaces.              | | `.service`       | Controls the execution of system services or applications, handling their lifecycle and dependencies.         | | `.slice`         | Organizes and manages resource allocation for processes using Linux Control Groups (cgroups).                 | | `.socket`        | Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation.| | `.snapshot`      | Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run.| | `.swap`          | Describes the swap space used by the system for memory management, allowing for temporary data storage.       | | `.target`        | Groups other units to synchronize their startup or shutdown during system boot or state transitions.          | | `.timer`         | Manages scheduled tasks and events, allowing for periodic execution of services or actions.                   | --- <nowiki>##</nowiki> Systemd Timers: A Replacement for Cron Jobs Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File `sudo nano /etc/systemd/system/daily-script.service` Contents: ``` [Unit] Description=Run daily script [Service] ExecStart=/path/to/your/script.sh ``` 2. Create a Timer File `sudo nano /etc/systemd/system/daily-script.timer` Contents: ``` [Unit] Description=Daily Timer for Script [Timer] OnCalendar=daily [Install] WantedBy=timers.target Enable and Start the Timer sudo systemctl enable daily-script.timer sudo systemctl start daily-script.timer ``` 3. Verify the Timer `systemctl list-timers` With OnCalendar, you can specify other schedules like weekly, hourly, or custom times (e.g., Mon \*-\*-\* 10:00:00). --- <nowiki>##</nowiki> How to Modify a Unit File?   - **Full Customization**     Copy the desired unit file to `/etc/systemd/system/` and modify it as needed.   - **Partial Changes**     If you only need to change a specific directive without copying the entire file:     1. Create a folder named after the unit file, ending with `.d`.       - Example: To modify `dummy.service`, create a folder named `dummy.service.d`.     2. Inside this folder, create a file ending with `.conf` to specify the changes.       - Example: `/etc/systemd/system/dummy.service.d/custom.conf`. --- <nowiki>##</nowiki> Precedence of Directories   When systemd processes unit files, it prioritizes directories in the following order:   1. `/etc/systemd/system` (highest priority for customizations)   2. `/run/systemd/system` (temporary, session-specific changes)   3. `/lib/systemd/system` (default system unit files)   --- <nowiki>##</nowiki> Troubleshooting Systemd Systemd provides several ways to troubleshoot and diagnose problems, including: - **systemctl status service-name**: Displays the status of a specific service, including whether it's running and any error messages. - **journalctl -u service-name**: Displays the logs for a specific service, making it easy to spot issues that may have occurred. - **systemctl list-units --failed**: Lists all failed units, providing a quick way to identify and address issues. - **systemctl daemon-reload**: Reloads the systemd manager configuration, useful after editing or adding unit files. 2f2ade1f337c54f2db03f279c6190d7811b2eccf 1653 1652 2025-01-11T02:37:51Z Scottc96 18 reformatted page wikitext text/x-wiki = Understanding Systemd = Systemd is an init system and service manager used by many modern Linux distributions. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here’s how Systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': Systemd provides a unified system for managing services, devices, logs, and even network interfaces. * '''Dependency Management''': Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': Systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in Systemd == Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit’s dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''Systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''Systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''Systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential Systemd Commands == Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash">systemctl start service-name</syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash">systemctl stop service-name</syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash">systemctl restart service-name</syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash">systemctl enable service-name</syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash">systemctl disable service-name</syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the `/lib/systemd/system/` directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there. * Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. '''Runtime Directory''' The `/run/systemd/system/` directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File '''sudo nano /etc/systemd/system/daily-script.service''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File '''sudo nano /etc/systemd/system/daily-script.timer''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer '''sudo systemctl enable daily-script.timer''' '''sudo systemctl start daily-script.timer''' === 3. Verify the Timer === To verify that your timer is active and running as scheduled, use the following command: '''systemctl list-timers''' This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With OnCalendar, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from `/lib/systemd/system/` to `/etc/systemd/system/` and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with `.d`. Example: To modify `dummy.service`, create a folder named `dummy.service.d` in `/etc/systemd/system/`. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a `.conf` file to specify your changes. Example: `/etc/systemd/system/dummy.service.d/custom.conf`. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. /etc/systemd/system/ (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. /run/systemd/system/ (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. /lib/systemd/system/ (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. '''systemctl status service-name''' Displays the status of a specific service, including whether it's running and any associated error messages. 2. '''journalctl -u service-name''' * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. '''systemctl list-units --failed''' * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. '''systemctl daemon-reload''' * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. 8b81b7cea0f6e1d1a7ece722b0219a2aa57e8122 1654 1653 2025-01-11T02:39:29Z Scottc96 18 fixed verify timer format wikitext text/x-wiki = Understanding Systemd = Systemd is an init system and service manager used by many modern Linux distributions. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here’s how Systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': Systemd provides a unified system for managing services, devices, logs, and even network interfaces. * '''Dependency Management''': Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': Systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in Systemd == Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit’s dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''Systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''Systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''Systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential Systemd Commands == Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash">systemctl start service-name</syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash">systemctl stop service-name</syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash">systemctl restart service-name</syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash">systemctl enable service-name</syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash">systemctl disable service-name</syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the `/lib/systemd/system/` directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there. * Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. '''Runtime Directory''' The `/run/systemd/system/` directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File '''sudo nano /etc/systemd/system/daily-script.service''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File '''sudo nano /etc/systemd/system/daily-script.timer''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer '''sudo systemctl enable daily-script.timer''' '''sudo systemctl start daily-script.timer''' 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: '''systemctl list-timers''' This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With OnCalendar, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from `/lib/systemd/system/` to `/etc/systemd/system/` and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with `.d`. Example: To modify `dummy.service`, create a folder named `dummy.service.d` in `/etc/systemd/system/`. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a `.conf` file to specify your changes. Example: `/etc/systemd/system/dummy.service.d/custom.conf`. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. /etc/systemd/system/ (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. /run/systemd/system/ (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. /lib/systemd/system/ (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. '''systemctl status service-name''' Displays the status of a specific service, including whether it's running and any associated error messages. 2. '''journalctl -u service-name''' * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. '''systemctl list-units --failed''' * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. '''systemctl daemon-reload''' * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. 2b0bdfdc194a3765b22b3d21eb1e19e8a572cee3 1655 1654 2025-01-11T02:41:53Z Scottc96 18 format fix wikitext text/x-wiki = Understanding Systemd = Systemd is an init system and service manager used by many modern Linux distributions. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here’s how Systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': Systemd provides a unified system for managing services, devices, logs, and even network interfaces. * '''Dependency Management''': Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': Systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in Systemd == Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit’s dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''Systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''Systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''Systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential Systemd Commands == Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash">systemctl start service-name</syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash">systemctl stop service-name</syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash">systemctl restart service-name</syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash">systemctl enable service-name</syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash">systemctl disable service-name</syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the `/lib/systemd/system/` directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there. * Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. '''Runtime Directory''' The `/run/systemd/system/` directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File '''sudo nano /etc/systemd/system/daily-script.service''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File '''sudo nano /etc/systemd/system/daily-script.timer''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer '''sudo systemctl enable daily-script.timer''' '''sudo systemctl start daily-script.timer''' 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: '''systemctl list-timers''' This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With OnCalendar, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from `/lib/systemd/system/` to `/etc/systemd/system/` and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with `.d`. Example: To modify `dummy.service`, create a folder named `dummy.service.d` in `/etc/systemd/system/`. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a `.conf` file to specify your changes. Example: `/etc/systemd/system/dummy.service.d/custom.conf`. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. /etc/systemd/system/ (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. /run/systemd/system/ (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. /lib/systemd/system/ (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. '''systemctl status service-name''' * Displays the status of a specific service, including whether it's running and any associated error messages. 2. '''journalctl -u service-name''' * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. '''systemctl list-units --failed''' * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. '''systemctl daemon-reload''' * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. c926f3de17331213eabb7f74022af29f2f56bf8d 0 517 1656 2025-01-11T05:46:58Z Scottc96 18 Created syscall entry for the wiki wikitext text/x-wiki = What is a System Call? = A system call (syscall) is a mechanism that allows a program to interact with the operating system. It acts as a bridge between the user space (where applications run) and the kernel space (where the operating system manages hardware and system resources). Programs use system calls to request services from the OS, such as managing files, processes, or hardware devices. For example, when you open a file, your application cannot directly access the hardware. Instead, it makes a system call (e.g., open()), which the OS handles to perform the requested task. Note that this is not a guide for ALL syscalls, but it is a guide to get you familiar enough with syscalls and strace. == Why Should You Learn About System Calls? == 1. Understanding How Programs Work: - System calls reveal how applications interact with the operating system to perform tasks like file handling, memory management, and networking. 2. Efficient Troubleshooting: - Knowing system calls can help diagnose performance issues or bugs by identifying which calls a program relies on. 3. Optimizing Software: - When developing programs, understanding system calls allows you to write efficient code by leveraging the right OS-level functions. 4. Security Awareness: - Many exploits and vulnerabilities target how system calls are used (or misused). Understanding them helps in writing secure code. 5. Kernel-Level Development: - If you're interested in low-level programming, such as operating system development or driver creation, system calls are fundamental. Basically, system calls are the foundation of how software and operating systems interact, making them essential knowledge for both beginner and advanced developers. == Categories of System Calls == System calls are grouped into five main categories: '''Process Control''' – Manage processes (create, terminate, etc.). '''File Management''' – Handle file operations (open, read, write, close). '''Device Management''' – Interact with hardware devices. '''Information Maintenance''' – Exchange information between the OS and programs. '''Communication''' – Enable processes to communicate. 1. '''Process Control''' * fork(): Creates a new process (child) that runs the same program as the parent. * exit(): Terminates the process and frees resources. * exec(): Replaces the current program in a process with a new one. 2. '''File Management''' * open(): Opens a file for reading or writing. * read(): Reads data from a file (multiple processes can read simultaneously). * write(): Writes data to a file (only one process can write at a time). * close(): Closes an open file. 3. '''Device Management''' * ioctl(): Performs device-specific operations not covered by standard calls (e.g., configuring hardware). 4. '''Information Maintenance''' * getpid(): Returns the process ID of the current process. * alarm(): Sets a timer to deliver a signal after a specified time. * sleep(): Pauses the process for a given time. 5. '''Communication''' * pipe(): Enables communication between processes via file descriptors. * shmget(): Allocates shared memory for process communication. * mmap(): Maps files or devices into a process’s memory. == Using strace to Look at System Calls == strace is a command-line tool that lets you see the system calls a program makes while it runs. It’s great for debugging, understanding program behavior, or learning how system calls work. === How to use strace === Steps to Use strace: 1. '''Run a Command with strace''': <syntaxhighlight lang="bash">strace <command></syntaxhighlight> This will show all the system calls made by the command. 2. '''Attach to a Running Process''': If a program is already running, use its process ID (PID): <syntaxhighlight lang="bash">strace -p <PID></syntaxhighlight> 3. '''Filter Specific System Calls''': To narrow down the output, trace specific system calls using the -e option: <syntaxhighlight lang="bash">strace -e <syscall> <command></syntaxhighlight> 4. '''Save Output to a File''': Use -o to redirect the output to a file for easier analysis: <syntaxhighlight lang="bash">strace -o trace_output.txt <command></syntaxhighlight> 5. '''Trace Execution Times''': To see how long each system call takes, use: <syntaxhighlight lang="bash">strace -T <command></syntaxhighlight> === Why Use strace? === * Debug program behavior (e.g., "Why is this program failing?"). * Identify which files, devices, or network resources a program accesses. * Learn what system calls a program makes for educational purposes. d6109e4f1737d2e60d8621b382ee4332e45f0342 3000 518 1657 2025-01-11T06:35:09Z Scottc96 18 Created permissions page wikitext text/x-wiki = Linux Permissions Guide = == Linux File Ownership == In Linux, there are three types of ownership classes: user, group, and others. === User === A user is the default owner and creator of a file. This user is often referred to as the owner. === Group === A group is a collection of users. All users belonging to a group share the same permissions to access a file or directory. Groups are useful for assigning permissions to multiple users at once. A user can belong to more than one group. === Others === Any users that are not part of the owner or group classes are categorized as "others." == Linux File Permissions == File permissions determine what actions users can perform on files or directories. There are three types of permissions: === Read Permission (r) === * For files: Allows users to open and view the contents of the file but not modify it. * For directories: Allows users to list the contents of the directory. === Write Permission (w) === * For files: Allows users to modify the contents of the file (edit, delete, save). * For directories: Allows users to modify directory contents (create, delete, and rename files inside the directory). === Execute Permission (x) === * For files: Allows users to execute or run the file, such as scripts or binaries. * For directories: Allows users to access files in the directory and obtain details about them. You can check permissions of files and directories using the `ls -l` command on a Linux terminal. == How to Change Permissions in Linux == Permissions can be modified using the `chmod` command. There are two methods to use `chmod`: symbolic mode and absolute mode. === Syntax === <code> chmod permissions filename</code> * '''permissions''': Specifies the read (r), write (w), and execute (x) permissions to be modified. * '''filename''': The name of the file or directory whose permissions need to be changed. === Symbolic Mode === In symbolic mode, you use symbols to specify permissions and users. Below are the representations: {| class="wikitable" |+Symbolic Representations !Symbol !Description |- |'''u''' |User/owner |- |'''g''' |Group |- |'''o''' |Others |} You can use the following operators to modify permissions: {| class="wikitable" |+Mathematical Operators !Operator !Description |- |'''+''' |Adds a permission |- |'''-''' |Removes a permission |- |'''=''' |Sets permissions (overwrites existing permissions) |} ==== Examples ==== * Add execution (x) permission for the owner:<code> chmod u+x script.sh</code> * Remove read and write (r, w) permissions for group and others:<code> chmod go-rw file.txt</code> * Set write (w) permission for group and overwrite existing permissions:<code> chmod g=w file.txt </code> === Absolute Mode === Absolute mode uses numeric values to represent permissions. Each permission is assigned a value as shown below: {| class="wikitable" |+Numeric Representation of Permissions !Permission !Numeric Value |- |Read (r) |4 |- |Write (w) |2 |- |Execute (x) |1 |} The total value for a permission set is calculated by adding the numeric values for the desired permissions. For example: * Read (4) + Write (2) = 6 * Read (4) + Execute (1) = 5 ==== Example ==== To set permissions as: * User: Read (4), Write (2) and Execute (1) * Group: Read (4) and Execute (1) * Others: Execute (1) Use the following command:<code> chmod 751 file.txt </code> This results in `rwxr-x--x`. == How to Change Ownership in Linux == File and directory ownership can be changed using the `chown` command. Ownership can be assigned to users, groups, or both. === Syntax === <code> chown [user][:group] filename</code> * '''user''': Specifies the new owner. * '''group''': Specifies the new group owner. === Examples === * Change ownership to user "jdoe":<code> chown jdoe file.txt</code> * Change ownership to user "jdoe" and group "devteam":<code>chown jdoe:devteam file.txt</code> * Change ownership recursively for a directory and its contents:<code> chown -R admin /opt/scripts</code> * Change only the group ownership:<code> chown :admins /opt/scripts </code> 3df01507fbfa4ce944957dda80b4ff8069a1aaa8 4 327 1658 1559 2025-01-11T13:06:07Z Atmois 13 idk wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen electron was here idk potato testing testing 1 2 3 4<ref>hi</ref> 159c42e98aad33352f54370bc21552948514bf50 0 418 1663 1443 2025-01-11T18:27:39Z Atmois 13 wikitext text/x-wiki {{DistributionInfobox|architectures=arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox|caption=The FreeBSD logo|defaultdesktops=[[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]]|image=[[File:FreeBSD logo.png|200px|FreeBSD_logo]]|packagemanager=pkg|releasemodel=Stable|releasestatus=Maintained|title=FreeBSD|usagetype=Desktop, Firewall, Raspberry Pi, Server|website=[https://freebsd.org freebsd.org]}} FreeBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released on November 1993<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"]. [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref>. [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[Drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a kernel and drivers, and relying on third-parties such as [[GNU]] for system software<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref>. The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref>. The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']}<references /> [[Category:Misc Operating Systems]] [[Category:BSD]] eee26bd2e1018a2450af3a900559142b8b1635dd 0 8 1664 1221 2025-01-11T18:32:20Z Atmois 13 fix link wikitext text/x-wiki == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 470487dc60c46cb96fe10102d76ba4c914dc43fd 0 198 1665 1483 2025-01-11T18:32:35Z Atmois 13 fix link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments||Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a Calamares installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 58b15c9c6a1530c890fd88fc9f5b73b97b0fcc75 0 299 1666 1445 2025-01-11T18:32:42Z Atmois 13 wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released on July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 7d4b75aea88029e27ead15ff63cb3a8383991d88 1671 1666 2025-01-11T18:35:29Z Atmois 13 Reverted edit by [[Special:Contributions/Atmois|Atmois]] ([[User talk:Atmois|talk]]) to last revision by [[User:MymeType|MymeType]] wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released on July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[XOrg]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 7044c1bda71d968c104f1ea97ff96cb8064d8d15 1673 1671 2025-01-11T18:37:47Z Atmois 13 fix wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released on July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 7d4b75aea88029e27ead15ff63cb3a8383991d88 0 176 1667 1487 2025-01-11T18:32:56Z Atmois 13 Fix link wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.2.4, 2024-11-26 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X.Org]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] f51a15d886beadfda5f5b4901423ed1fd19c229a 1670 1667 2025-01-11T18:35:23Z Atmois 13 Reverted edit by [[Special:Contributions/Atmois|Atmois]] ([[User talk:Atmois|talk]]) to last revision by [[User:Gurov|Gurov]] wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.2.4, 2024-11-26 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 90e7f7162cd0338aa0a6490d3574ae78d8e7d77e 0 227 1668 931 2025-01-11T18:33:02Z Atmois 13 wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X.Org]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Window Managers]] 3b5fcb5b88f45e7be134f4b0f1a221535a5fe3e8 1674 1668 2025-01-11T18:38:09Z Atmois 13 fix wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Window Managers]] 5c395a145d9f85b2260b8f3baba738dff41bcaf9 0 257 1669 1005 2025-01-11T18:33:42Z Atmois 13 Fix link wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) === Installation === This section will change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X.Org]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Managers]] ab6e4d1ed53f50e8ff4c1665d1d445970c5114a7 1672 1669 2025-01-11T18:37:02Z Atmois 13 fix wikitext text/x-wiki {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) === Installation === This section will change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Managers]] fa41ed23a43f9a1f0c5f63ec790bd4e78409b57a 0 306 1675 1482 2025-01-11T18:40:37Z Atmois 13 link fix wikitext text/x-wiki A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[GUI|Graphical User Interface (GUI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[qtile]] * [[i3]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[Hyprland]] * [[xmonad]] [[Category:Terminology]] e88072ef35cf72df325fb3c1e383bddc0f5382e6 0 428 1676 1472 2025-01-11T18:40:52Z Atmois 13 fix link wikitext text/x-wiki Man or Man pages is a [[command-line]] utility available on [[UNIX]] and [[UNIX-like]] [[operating systems]] that provides [[documentation]] for [[Program|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format]] and [[games]]. The Man pages are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a Man page the user can enter the following into their [[terminal]]: man <command_name> <ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> For example to read the Man page on [[pacman]] you would enter the following: man pacman == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardize layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> <references /> b24190d6b6098b5f21a675aea52371e08e90c272 0 304 1677 1224 2025-01-11T18:41:40Z Atmois 13 fix link wikitext text/x-wiki {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a [[UNIX-like]] [[Operating System|operating system]] completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS]</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive [[kernel]], and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[MacOS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[Virtual Machine|virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to [[Compiling|compile]] software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub]</ref> [[Category:Misc Operating Systems]] 5430afab6f67c7fac825d624042af2736d5fb272 0 405 1681 1401 2025-01-16T20:46:49Z Imnotgoodatnames 121 wikitext text/x-wiki Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Examples of proprietary software are Microsoft Windows and Adobe Photoshop. [[Category:Terminology]] 919dbf14cf131a327c061f312a1b871f7039ec46 0 177 1682 686 2025-01-16T20:53:18Z Imnotgoodatnames 121 FLOSS should also be mentioned here as the FSF claims it's a better neutral option than FOSS wikitext text/x-wiki '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the french word, libre)<ref>https://en.wiktionary.org/wiki/libre</ref> and Open Source Software (FLOSS), is software that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> [[Category:Terminology]] a73fcca0bc4d8cebee256d311baade2d969e3edf 0 174 1683 681 2025-01-16T22:19:13Z Imnotgoodatnames 121 replaced the MS-DOS setup image with a more Linux related one wikitext text/x-wiki [[File:Debian-Installer 10 Tasksel.svg|alt=Debian TUI installer|thumb|Debian 10 installation, which uses a TUI installer]] A '''TUI''' (Terminal User Interface) generally refers to an application that solely exists within the terminal as a text-based application - this means that all of its content is rendered using letters and other unique characters to create a graphical interface. [REFERENCE POSSIBLE] Because of its independence from a ... , [[Category:Terminology]] 590250da722957cad516c9b9c2bab2bd1e9a924b 0 198 1684 1665 2025-01-18T22:28:30Z Atmois 13 Add oreon entry wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments||Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a Calamares installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 87b1313614de6ac8b14a56b7c1725e1833a17ce2 0 1 1685 1586 2025-01-19T10:31:20Z Atmois 13 update contact info wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from newer users will require approval from a administrator or a moderator. You can find more information on our standards at [[Contributing]]. You can become an auto-moderated user in a few ways. You can join our discord at https://discord.gg/linux and request in the Wiki-Public channel to be promoted to an auto-moderated user. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community.  If you do not have discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an auto-moderated user, you may set the "authorised" revision to the previous one, but do note other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * tess(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 6d757301a150db695e9ae8b86dab9a824e8ee9af 1726 1685 2025-01-21T19:09:22Z Atmois 13 fix channel name wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from newer users will require approval from a administrator or a moderator. You can find more information on our standards at [[Contributing]]. You can become an auto-moderated user in a few ways. You can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community.  If you do not have discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an auto-moderated user, you may set the "authorised" revision to the previous one, but do note other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * tess(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 6b967feecb01d21493f3696056d88fe3630c4372 10 513 1686 1646 2025-01-19T10:47:19Z Atmois 13 Atmois moved page [[Template:No Citations]] to [[Template:Needs Citations]] without leaving a redirect wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations. (hover for more information)</span> <div class="mbox-text">This article was most likely made before strict rules for citations were implemented [[Contributing#Citations|(Read here)]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:No Citations]] for other pages that still need to be edited.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:No Citations]]</includeonly><noinclude> {{/doc}}</noinclude> 343ab1c174dba5aa33943a8de5b1182bbf105cd7 1689 1686 2025-01-19T10:49:11Z Atmois 13 updates name wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to needs citations. (hover for more information)</span> <div class="mbox-text">This article was most likely made before strict rules for citations were implemented [[Contributing#Citations|(Read here)]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that still need to be edited.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Needs Citations]]</includeonly><noinclude> {{/doc}}</noinclude> 5809b4437a824c3dbc4db054c4b6295777141b15 1696 1689 2025-01-19T11:16:28Z Atmois 13 Protected "[[Template:Needs Citations]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to needs citations. (hover for more information)</span> <div class="mbox-text">This article was most likely made before strict rules for citations were implemented [[Contributing#Citations|(Read here)]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that still need to be edited.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Needs Citations]]</includeonly><noinclude> {{/doc}}</noinclude> 5809b4437a824c3dbc4db054c4b6295777141b15 1712 1696 2025-01-19T12:52:24Z Atmois 13 update wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to needs citations.</span> <div class="mbox-text">This article was most likely made before strict rules for citations were implemented [[Contributing#Citations|(Read here)]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that still need to be edited.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Needs Citations]]</includeonly><noinclude> {{/doc}}</noinclude> 2947378f6eebd7128cec577b2eae5e8f8c5d2865 10 514 1687 1680 2025-01-19T10:47:19Z Atmois 13 Atmois moved page [[Template:No Citations/doc]] to [[Template:Needs Citations/doc]] without leaving a redirect wikitext text/x-wiki This template should be placed on articles or section with little to no citations. This template adds pages to [[:Category:No Citations]]. == Usage == <code>{{tlx|No Citations}}</code> <includeonly>[[Category:Maintenance templates]]</includeonly> bced771258819a195ddefe8317731c0e98a1eebe 1688 1687 2025-01-19T10:48:19Z Atmois 13 update name wikitext text/x-wiki This template should be placed on articles or section with little to no citations. This template adds pages to [[:Category:Needs Citations]]. == Usage == <code>{{tlx|Needs Citations}}</code> <includeonly>[[Category:Maintenance templates]]</includeonly> 2ab12c4ac5d85b9c1c0d0cd0308d3188832073b8 1697 1688 2025-01-19T11:16:56Z Atmois 13 Protected "[[Template:Needs Citations/doc]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki This template should be placed on articles or section with little to no citations. This template adds pages to [[:Category:Needs Citations]]. == Usage == <code>{{tlx|Needs Citations}}</code> <includeonly>[[Category:Maintenance templates]]</includeonly> 2ab12c4ac5d85b9c1c0d0cd0308d3188832073b8 1698 1697 2025-01-19T12:15:18Z Atmois 13 wikitext text/x-wiki This template should be placed on articles or section with little to no citations. This template adds pages to [[:Category:Needs Citations]]. == Usage == <code>{{tlx|Needs Citations}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 7e1b6fa975b19bb9afd7e6fa87a0a634a403017b 10 494 1690 1679 2025-01-19T11:04:06Z Atmois 13 update wikitext text/x-wiki This template should be placed on articles or section that you believe require a cleanup. This template adds pages to [[:Category:Pages Needing Cleanup]]. You should always specify the reason by including a parameter. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Biased Tone", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance Templates]]</includeonly> f9faec595b98b1170185cae49177344ba46d581b 1695 1690 2025-01-19T11:15:17Z Atmois 13 Protected "[[Template:Cleanup/doc]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki This template should be placed on articles or section that you believe require a cleanup. This template adds pages to [[:Category:Pages Needing Cleanup]]. You should always specify the reason by including a parameter. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Biased Tone", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance Templates]]</includeonly> f9faec595b98b1170185cae49177344ba46d581b 10 483 1691 1649 2025-01-19T11:07:47Z Atmois 13 update wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified.}}</span> <div class="mbox-text">It might not meet the wiki's [[Contributing#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> df6958dc76e8288fdffd4a6f7eef7b735c06b1e1 1694 1691 2025-01-19T11:13:15Z Atmois 13 Protected "[[Template:Cleanup]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified.}}</span> <div class="mbox-text">It might not meet the wiki's [[Contributing#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> df6958dc76e8288fdffd4a6f7eef7b735c06b1e1 14 519 1692 2025-01-19T11:07:48Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Maintenance Templates" as well as all subcategories of category "Maintenance Templates" if any exist. 7f3762a1e6879ccb40e2f2ccb90907863f47e1c8 4 340 1693 1453 2025-01-19T11:09:23Z Atmois 13 add info on new templates wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date, this can be done by ensuring you are using the offical sources or other high quality and reputable sources for information. Please ensure you appropiatly cite your sources following our [[Contributing#Citations]] guidelines. ===== <u>Impartiality</u> ===== Pages should be unbiased, if there has been a controversy on a specific topic make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader only is given the facts. E.g: Instead of saying "xyz package is bad," say "xyz package has received criticism for...". ===== <u>Consistancy</u> ===== Ensure that your page is consistant with others in both the formatting and the terminology, e.g. for the x86-64/AMD64/x64 architecture it should always be reffered to by AMD64 as it is its offical name. Further details on this can be seen in the [[Contributing#Formatting]] section. ===== '''<u>Courtesy</u>''' ===== If you are doing any major changes to existing pages make sure to ask any active editors of the page or an admin to ensure that it meets our requirements and other editors are in agreement with the changes. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when neccessary and you update list pages (E.g: [[Linux Distributions]]) when making a new entry. * Categorise pages when needed, you can do this by selecting the hamburger menu then the categories button, avoid making new categories unless its required. * Don't make a new page unless you can add worthwile content to it. If a page does not meet the standards of the wiki you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it required, this can be because you are referencing other's statements, the release date of a piece of software or for any material that is challanged or is likely to be challenged in particular. If you ever obtain content from another source (Such as taking info from a wiki with a compatible liscense) or quote other locations online ensure you link to it appropiatly. A citation is composed of two components, a inline superscript next to the releavant section of text <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page, this is autogenerated once the page is saved. For the inline citation there is no specific style required as long you state the author, year of publication, the date of retrival & if possible a link to the original source. We reccommend the following structure which is adapted from the Harvard Referencing Style: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g: [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Sources should be published & reliable and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' depends on context; common sense and editorial judgment are an indispensable part of the process. In general newer sources are better however if an older source is considered more reliable it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistant, e.g. if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required when the name of a company or piece of software uses a specific spelling, e.g. "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]].<references /> [[Category:Meta]] fa3be3180ecef6a0458eb334c81484c999126377 10 520 1699 2025-01-19T12:17:52Z Atmois 13 add info wikitext text/x-wiki A template used to document a subpage. 385aff1b35454723846533045b9ce9b36f676f26 1701 1699 2025-01-19T12:20:13Z Atmois 13 Protected "[[Template:Documentation/doc]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki A template used to document a subpage. 385aff1b35454723846533045b9ce9b36f676f26 10 487 1700 1650 2025-01-19T12:18:22Z Atmois 13 Protected "[[Template:Documentation]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki <includeonly>{{#invoke:Documentation|doc}}__NOEDITSECTION__{{ |type = website |description = {{FULLPAGENAME}} is a template page used on the ATL Wiki. Templates are pages that are embedded into other articles as reuseable elements. |site_name = ATL Wiki |locale = {{PAGELANGUAGE}} }}</includeonly><noinclude>{{/doc}}</noinclude> 04f832677890e699d88890f9cbc8494ea4a74e48 10 482 1702 1587 2025-01-19T12:26:53Z Atmois 13 update wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands which could potentially damage your system. Please ensure you understand the commands you are running before you run them. If you see a dangerous command please report it to an administrator.</span> <div class="mbox-text">This warning is placed on any page that lists a command, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be report to an [[Main Page#Contacts|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 0fcbed7c7e8b03959990fc1a4705fe417a731a29 1703 1702 2025-01-19T12:27:04Z Atmois 13 Protected "[[Template:CommandWarning]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands which could potentially damage your system. Please ensure you understand the commands you are running before you run them. If you see a dangerous command please report it to an administrator.</span> <div class="mbox-text">This warning is placed on any page that lists a command, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be report to an [[Main Page#Contacts|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 0fcbed7c7e8b03959990fc1a4705fe417a731a29 1706 1703 2025-01-19T12:28:26Z Atmois 13 typo wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands which could potentially damage your system. Please ensure you understand the commands you are running before you run them. If you see a dangerous command please report it to an administrator.</span> <div class="mbox-text">This warning is placed on any page that lists a command, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be reported to an [[Main Page#Contacts|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 0e90795966cac7dfb1aba26f091a880ae2bb03f8 1708 1706 2025-01-19T12:29:01Z Atmois 13 Atmois moved page [[Template:CommandWarning]] to [[Template:Command Warning]] without leaving a redirect: Misspelled title: Typo wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands which could potentially damage your system. Please ensure you understand the commands you are running before you run them. If you see a dangerous command please report it to an administrator.</span> <div class="mbox-text">This warning is placed on any page that lists a command, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be reported to an [[Main Page#Contacts|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 0e90795966cac7dfb1aba26f091a880ae2bb03f8 10 521 1704 2025-01-19T12:27:54Z Atmois 13 add doc wikitext text/x-wiki This warning must placed on any page that lists a command, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be report to an [[Main Page#Contacts|administrator]] immediately. b2bc60c013536cec0bb0891e92f845e5eaaa6a48 1705 1704 2025-01-19T12:28:05Z Atmois 13 Protected "[[Template:CommandWarning/doc]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki This warning must placed on any page that lists a command, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be report to an [[Main Page#Contacts|administrator]] immediately. b2bc60c013536cec0bb0891e92f845e5eaaa6a48 1707 1705 2025-01-19T12:28:40Z Atmois 13 typo wikitext text/x-wiki This warning must placed on any page that lists a command, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be reported to an [[Main Page#Contacts|administrator]] immediately. 448dcd963b9b2e6d5687e63a2177de8afac01f87 1709 1707 2025-01-19T12:29:01Z Atmois 13 Atmois moved page [[Template:CommandWarning/doc]] to [[Template:Command Warning/doc]] without leaving a redirect: Misspelled title: Typo wikitext text/x-wiki This warning must placed on any page that lists a command, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be reported to an [[Main Page#Contacts|administrator]] immediately. 448dcd963b9b2e6d5687e63a2177de8afac01f87 1710 1709 2025-01-19T12:32:37Z Atmois 13 fix wikitext text/x-wiki This warning must placed on any page that lists a command that a user can run on their system, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be reported to an [[Main Page#Contacts|administrator]] immediately. == Usage == <code>{{tlx|Command_Warning}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> d0f78515902b4d3ac95946fad618d6cdbcac87ba 10 523 1713 2025-01-19T13:32:20Z Atmois 13 create template wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please ensure you check with the main editor before making any content changes.</span> <div class="mbox-text">.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> de35b20585e329666286b80f287470c3d67e3fe8 1714 1713 2025-01-19T13:34:13Z Atmois 13 fix wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 0a1b5112969a4d5ac2b116314aa30e7f2c3ef253 1716 1714 2025-01-19T13:35:39Z Atmois 13 Protected "[[Template:Work In Progress]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) [cascading] wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 0a1b5112969a4d5ac2b116314aa30e7f2c3ef253 1717 1716 2025-01-19T13:36:11Z Atmois 13 Changed protection settings for "[[Template:Work In Progress]]": remove cascading ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 0a1b5112969a4d5ac2b116314aa30e7f2c3ef253 10 524 1715 2025-01-19T13:35:07Z Atmois 13 create doc wikitext text/x-wiki This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes. == Usage == <code>{{tlx|Work_In_Progress}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 8b81e59cedd498a6ba30babad72ad1f349eb9888 1718 1715 2025-01-19T13:36:24Z Atmois 13 Protected "[[Template:Work In Progress/doc]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes. == Usage == <code>{{tlx|Work_In_Progress}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 8b81e59cedd498a6ba30babad72ad1f349eb9888 828 525 1719 2025-01-19T14:32:38Z Atmois 13 add docs wikitext text/x-wiki == Distribution Infoboxes == In order to embed a infobox for distributions, you can put this at the very top of your article <pre> {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, KDE, LXDE, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} </pre> 9e2138446123fa04b68abec075a1ebd98b8af36d 1720 1719 2025-01-19T14:34:50Z Atmois 13 title wikitext text/x-wiki == Usage == In order to embed a infobox for distributions, you can put this at the very top of your article <pre> {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, KDE, LXDE, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} </pre> 396630062f9135a503c62b55397ec552894960f7 1721 1720 2025-01-19T14:35:03Z Atmois 13 Protected "[[Module:DistributionInfobox/doc]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki == Usage == In order to embed a infobox for distributions, you can put this at the very top of your article <pre> {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, KDE, LXDE, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} </pre> 396630062f9135a503c62b55397ec552894960f7 10 526 1722 2025-01-19T14:36:43Z Atmois 13 Redirected page to [[Module:DistributionInfobox/doc]] wikitext text/x-wiki #REDIRECT [[Module:DistributionInfobox/doc]] 77558eaa1d5751a016993d5e5c76f98d5ec9a18b 1733 1722 2025-01-21T19:34:50Z Atmois 13 Protected "[[Template:DistributionInfobox/doc]]": Template Redirect ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki #REDIRECT [[Module:DistributionInfobox/doc]] 77558eaa1d5751a016993d5e5c76f98d5ec9a18b 10 162 1723 329 2025-01-19T14:37:39Z Atmois 13 add meta stuff wikitext text/x-wiki <includeonly>{{#invoke:DistributionInfobox|main}}</includeonly> <includeonly>[[Category:Infoboxes]]</includeonly> <noinclude>{{/doc}}</noinclude> 07e4b6ccd54e7bc7213a3d9c3ee6eb5e92dfecc0 10 205 1727 497 2025-01-21T19:24:44Z Atmois 13 Protected "[[Template:SoftwareInfobox]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki <includeonly>{{#invoke:SoftwareInfobox|main}}</includeonly> 18a26db43b8047401f2133ffe702a70c137cb38f 1731 1727 2025-01-21T19:33:43Z Atmois 13 add docs and category wikitext text/x-wiki <includeonly>{{#invoke:Software|main}}</includeonly> <includeonly>[[Category:Infoboxes]]</includeonly> <noinclude>{{/doc}}</noinclude> 98efd28ca67acfe812c1cb12999d39e6e01012e7 828 204 1728 500 2025-01-21T19:25:19Z Atmois 13 Protected "[[Module:SoftwareInfobox]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Last Release', args.lastrelease ) :addRow( 'Language(s)', args.languages ) :addRow( 'Developer(s)', args.developers ) :addRow( 'Website', args.website ) return retval end return p 10e68839b660f1cac4400d90ee88f3367780e7be 828 528 1729 2025-01-21T19:31:53Z Atmois 13 add docs wikitext text/x-wiki == Usage == In order to embed a infobox for software, you can put this at the very top of your article <pre> {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} </pre> 35e59b25b2c96536ff7ddd2d7061eced75465fa7 1730 1729 2025-01-21T19:32:05Z Atmois 13 Protected "[[Module:SoftwareInfobox/doc]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki == Usage == In order to embed a infobox for software, you can put this at the very top of your article <pre> {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} </pre> 35e59b25b2c96536ff7ddd2d7061eced75465fa7 10 529 1732 2025-01-21T19:34:30Z Atmois 13 add redirect wikitext text/x-wiki #REDIRECT [[Module:SoftwareInfobox/doc]] 86ef231b2f98916b329c4dc0ed1341b2a9fcda99 1734 1732 2025-01-21T19:35:49Z Atmois 13 Protected "[[Template:SoftwareInfobox/doc]]": High traffic page: Template Redirect ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki #REDIRECT [[Module:SoftwareInfobox/doc]] 86ef231b2f98916b329c4dc0ed1341b2a9fcda99 10 208 1735 507 2025-01-21T19:37:13Z Atmois 13 Protected "[[Template:LarryInfobox]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki <includeonly>{{#invoke:LarryInfobox|main}}</includeonly> 2977b853b4d4d1dd4e3156eca3c05d347aeb67cc 828 207 1736 1299 2025-01-21T19:37:37Z Atmois 13 Protected "[[Module:LarryInfobox]]": Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end return retval end return p a765ed2f359127e25b0baa33db64c34ebd521c48 828 528 1737 1730 2025-01-21T19:38:50Z Atmois 13 add docs wikitext text/x-wiki == Usage == In order to embed a infobox for software, you can put this at the very top of your article <pre> {{LarryInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} </pre> db33a75a091b9ee9872ac411e23897e0b3cb5af7 1738 1737 2025-01-21T19:39:14Z Atmois 13 changed wrong page wikitext text/x-wiki == Usage == In order to embed a infobox for software, you can put this at the very top of your article <pre> {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} </pre> 35e59b25b2c96536ff7ddd2d7061eced75465fa7 828 530 1739 2025-01-21T19:39:46Z Atmois 13 add docs wikitext text/x-wiki == Usage == In order to embed a infobox for mascots, you can put this at the very top of your article <pre> {{LarryInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} </pre> 854b3e5ec877f88796580eb57f5205bbe9100123 1742 1739 2025-01-21T19:42:11Z Atmois 13 Protected "[[Module:LarryInfobox/doc]]": High traffic page: Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki == Usage == In order to embed a infobox for mascots, you can put this at the very top of your article <pre> {{LarryInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} </pre> 854b3e5ec877f88796580eb57f5205bbe9100123 1744 1742 2025-01-21T19:42:47Z Atmois 13 Atmois moved page [[Module:LarryInfobox/doc]] to [[Module:MascotInfobox/doc]] without leaving a redirect: Rename wikitext text/x-wiki == Usage == In order to embed a infobox for mascots, you can put this at the very top of your article <pre> {{LarryInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} </pre> 854b3e5ec877f88796580eb57f5205bbe9100123 1745 1744 2025-01-21T19:43:05Z Atmois 13 fix template wikitext text/x-wiki == Usage == In order to embed a infobox for mascots, you can put this at the very top of your article <pre> {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} </pre> ecdc93523f9ddd05084135ea5e220060255e11e3 10 531 1740 2025-01-21T19:41:13Z Atmois 13 add redirect wikitext text/x-wiki #REDIRECT [[Module:MascotInfobox/doc]] ff907f5cfbbe057f8bed0c2a318268c54f8e906f 1741 1740 2025-01-21T19:42:01Z Atmois 13 Protected "[[Template:LarryInfobox/doc]]": High traffic page: Template Redirect ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki #REDIRECT [[Module:MascotInfobox/doc]] ff907f5cfbbe057f8bed0c2a318268c54f8e906f 1749 1741 2025-01-21T19:44:41Z Atmois 13 Atmois moved page [[Template:LarryInfobox/doc]] to [[Template:MascotInfobox/doc]] without leaving a redirect: Rename wikitext text/x-wiki #REDIRECT [[Module:MascotInfobox/doc]] ff907f5cfbbe057f8bed0c2a318268c54f8e906f 828 207 1743 1736 2025-01-21T19:42:47Z Atmois 13 Atmois moved page [[Module:LarryInfobox]] to [[Module:MascotInfobox]] without leaving a redirect: Rename Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end return retval end return p a765ed2f359127e25b0baa33db64c34ebd521c48 10 205 1746 1731 2025-01-21T19:44:20Z Atmois 13 typo fix wikitext text/x-wiki <includeonly>{{#invoke:SoftwareInfobox|main}}</includeonly> <includeonly>[[Category:Infoboxes]]</includeonly> <noinclude>{{/doc}}</noinclude> 37be68093aba1a28b357de22e689330943fd71c5 10 208 1747 1735 2025-01-21T19:44:29Z Atmois 13 add docs wikitext text/x-wiki <includeonly>{{#invoke:MascotInfobox|main}}</includeonly> <includeonly>[[Category:Infoboxes]]</includeonly> <noinclude>{{/doc}}</noinclude> 09bc0a18f1db7e9bc2610deb8da388faaf1c5b3d 1748 1747 2025-01-21T19:44:41Z Atmois 13 Atmois moved page [[Template:LarryInfobox]] to [[Template:MascotInfobox]] without leaving a redirect: Rename wikitext text/x-wiki <includeonly>{{#invoke:MascotInfobox|main}}</includeonly> <includeonly>[[Category:Infoboxes]]</includeonly> <noinclude>{{/doc}}</noinclude> 09bc0a18f1db7e9bc2610deb8da388faaf1c5b3d 0 354 1750 1296 2025-01-21T19:45:24Z Atmois 13 Update template name wikitext text/x-wiki {{MascotInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy|222px]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. [[Category:Mascots]] 4a9b0a539e05a1b29bc5075c6feed57e9aa3d128 14 532 1751 2025-01-21T19:45:24Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Infoboxes" as well as all subcategories of category "Infoboxes" if any exist. 3b02eaea6608fc9c7f7549a56a557e48087315f8 0 219 1752 615 2025-01-21T19:45:28Z Atmois 13 Update template name wikitext text/x-wiki {{MascotInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan<ref>https://community.kde.org/Promo/Material/Mascots</ref>. Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror], KDE's default web browser<ref>https://community.kde.org/Konqi</ref>.<references /> [[Category:Mascots]] fda6ce1d330e3ba8068c1364e05b1e508aea9c63 0 214 1753 536 2025-01-21T19:45:31Z Atmois 13 Update template name wikitext text/x-wiki {{MascotInfobox | title = Tux | image = [[File:Tux.svg|Tux|333px]] | caption = Tux! }} '''Tux''' is the official mascot of [[Linux]], designed by Larry Ewing<ref>https://web.archive.org/web/20040401161253/http://www.linux.org/info/logos.html</ref>. Tux was created for the Linux 2.0 logo competition<ref>https://web.archive.org/web/20040407092622/http://www.cs.earlham.edu/~jeremiah/linux-pix/linux-logo.html</ref>.<references /> [[Category:Mascots]] 9d33ddbbe7690e744652f4637cdb1feb88a2b41e 0 202 1754 534 2025-01-21T19:45:34Z Atmois 13 Update template name wikitext text/x-wiki {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry</ref> <references /> [[Category:Mascots]] b1eecd5928554290984cd9ee4038831ab156acaa 0 1 1755 1726 2025-01-21T23:54:06Z Atmois 13 Remove email wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from newer users will require approval from a administrator or a moderator. You can find more information on our standards at [[Contributing]]. You can become an auto-moderated user in a few ways. You can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community.  If you do not have discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an auto-moderated user, you may set the "authorised" revision to the previous one, but do note other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ c3afdc8335b86a447167d4880ea610a8b646657b 1767 1755 2025-01-24T20:50:21Z Atmois 13 update links wikitext text/x-wiki {{Main Page/Header}} {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from newer users will require approval from a administrator or a moderator. You can find more information on our policies and standards on the [[Policies]] page. You can become an auto-moderated user in a few ways. You can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community.  If you do not have discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an auto-moderated user, you may set the "authorised" revision to the previous one, but do note other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 4d25b0e3eca154b12792d5c90d22ccc0bb6f3f9e 1770 1767 2025-01-25T12:33:48Z Atmois 13 Add header into main page wikitext text/x-wiki <div style='text-align: center;'> <h1>Welcome to the All Things Linux Wiki!</h1> <p> This is the official wiki by the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Main_Page#Contacts|Contacts Section]]!</p> </div> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from newer users will require approval from a administrator or a moderator. You can find more information on our policies and standards on the [[Policies]] page. You can become an auto-moderated user in a few ways. You can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community.  If you do not have discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an auto-moderated user, you may set the "authorised" revision to the previous one, but do note other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 526b8d7fdb391726eb0531f70eb93f5168cc7f95 1771 1770 2025-01-25T12:36:10Z Atmois 13 update info wikitext text/x-wiki <div style='text-align: center;'> <h1>Welcome to the All Things Linux Wiki!</h1> This is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Main_Page#Contacts|Contacts Section]]!</p> </div> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How Contributing Works == Any user can register and submit changes to the wiki. However, any changes from newer users will require approval from a administrator or a moderator. You can find more information on our policies and standards on the [[Policies]] page. You can become an auto-moderated user in a few ways. You can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community.  If you do not have discord or wish to request the role another way, you may contact us via the methods listed in the [[Main Page#Contacts|Contacts Section]]. However, replies will typically be slower than via discord.  == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an auto-moderated user, you may set the "authorised" revision to the previous one, but do note other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 746d5db983a815c9637895a599b3ccb9cf82cc0e 1774 1771 2025-02-02T11:09:06Z Atmois 13 Improve contributing section wikitext text/x-wiki <div style='text-align: center;'> <h1>Welcome to the All Things Linux Wiki!</h1> This is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Main_Page#Contacts|Contacts Section]]!</p> </div> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How you can contribute == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! All changes go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, don't worry about this as it only exists to stop spam and malicious actors. Most changes will be approved within 6 hours, and we rarely reject changes for reasons beyond large violations of our Code of Conduct. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user, or you may contact an admin via the methods listed in the [[Main Page#Contacts|Contacts Section]]. == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an auto-moderated user, you may set the "authorised" revision to the previous one, but do note that other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == '''Contacts''' == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. Email replies will typically be slower than via Discord. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 7fd51763454f40dcf4fadb7c39140f0e2c625765 1775 1774 2025-02-02T11:15:06Z Atmois 13 Fix formatting wikitext text/x-wiki <div style='text-align: center;'> <h1>Welcome to the All Things Linux Wiki!</h1> This is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Main_Page#Contacts|Contacts Section]]!</p> </div> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == How you can contribute == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! All changes go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, don't worry about this as it only exists to stop spam and malicious actors. Most changes will be approved within 6 hours, and we rarely reject changes for reasons beyond large violations of our Code of Conduct. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user, or you may contact an admin via the methods listed in the [[Main Page#Contacts|Contacts Section]]. == Reporting == If you see a malicious edit/vandalism, you can contact us via the methods in the [[Main Page#Contacts|Contacts Section]] (Discord Preferred) with the link to the page/user/edit in question, and we will tackle it as soon as possible! If you are an auto-moderated user, you may set the "authorised" revision to the previous one, but do note that other Auto-Moderated Users can override this. Always, if possible, avoid edit wars and contact an administrator who can mitigate the situation appropriately. == Contacts == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. Email replies will typically be slower than via Discord. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 25f9be79eda5350ff8ab3c70852bbd449b17a254 1776 1775 2025-02-02T12:23:17Z Atmois 13 Change focus to getting started on contributing and improving the writing. wikitext text/x-wiki <div style='text-align: center;'> <h1>Welcome to the All Things Linux Wiki!</h1> This is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Main_Page#Contacts|Contacts Section]]!</p> </div> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! Make sure to check out the [[policies]] page, which outlines guidelines and expectations for editors and if you need a place to start check out [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. For general MediaWiki editing support, check out [[metawikimedia:Help:Contents|Mediawiki's Editing Guide]]! ====== Moderation ====== All changes go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, don't worry about this as it only exists to stop spam and malicious actors. Most changes will be approved within 6 hours, and we rarely reject changes for reasons beyond large violations of our Code of Conduct. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user, or you may contact an admin via the methods listed in the [[Main Page#Contacts|Contacts Section]]. == Contacts == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. Email replies will typically be slower than via Discord. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 4975c5023375adb466f3b4f3d3d406feaeb19b48 1777 1776 2025-02-02T13:36:23Z Atmois 13 Improvements wikitext text/x-wiki <div style='text-align: center;'> <h1>Welcome to the All Things Linux Wiki!</h1> This is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Main_Page#Contacts|Contacts Section]]!</p> </div> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out [[metawikimedia:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. ====== Moderation ====== All changes go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, don't worry about this as it only exists to stop spam and malicious actors. Most changes will be approved within 6 hours, and we rarely reject changes for reasons beyond large violations of our Code of Conduct. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user, or you may contact an admin via the methods listed in the [[Main Page#Contacts|Contacts Section]]. == Contacts == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. Email replies will typically be slower than via Discord. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ b5b2a44409a6fac7b60241544b1002c4ba532cba 2 533 1756 2025-01-22T17:24:45Z Created page with "I am Vestik." wikitext text/x-wiki I am Vestik. c69faa3ba3b87905b8008e7903ddda5e84a66f1b 0 306 1757 1675 2025-01-23T17:44:38Z Glocean 124 /* Types of Window Manager */ wikitext text/x-wiki A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[GUI|Graphical User Interface (GUI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm * [[Wayfire]] ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[i3]] * [[Sway]] * [[SwayFx]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[dwl]] * [[qtile]] * [[Hyprland]] * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] ==== Scrollable Window Managers ==== Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[niri]] * [[PaperWM]] * [[karousel]] * [[papersway]] * [[hyprscroller]] * [[hyprslidr]] * [[PaperWM.spoon]] [[Category:Terminology]] 8f5254561fae510cd6a89b4b7063494f2d3991f7 0 534 1758 2025-01-23T19:21:30Z Glocean 124 Added an brief summary, installation instruction, and an "important software" section. Still a WIP wikitext text/x-wiki Niri is a scrollable-tiling wayland compositor. It was heavily inspired by [[PaperWM]], an extension for [[GNOME]]. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through the collumns. Opening a new window never causes existing windows to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor. == Features == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth touchpad and mouse gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config == Installation == Below you will find installation instruction for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Arch Linux === To download the latest stable release, run the following command:<syntaxhighlight lang="bash"> sudo pacman -S niri </syntaxhighlight>If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru:<syntaxhighlight lang="bash"> yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix'''<syntaxhighlight lang="nix"> environment.systemPackages = [ pkgs.niri ]; </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below:<syntaxhighlight lang="bash"> pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install.<syntaxhighlight> sudo zypper in niri </syntaxhighlight>Alternatively, you can install it with '''opi''' as well.<syntaxhighlight> opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''.<syntaxhighlight lang="bash"> sudo xbps-install -S niri </syntaxhighlight> == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file. While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages bellow to ensure app functionality.<syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> 7ac1a49278b4cc19e0ae24be750e1281cd8566c8 1760 1758 2025-01-24T18:40:07Z Glocean 124 Added sections to help with setting up niri and fixed some mistakes/typos wikitext text/x-wiki Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]]. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor. == Features == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Arch Linux === To download the latest stable release, run the following command:<syntaxhighlight lang="bash"> sudo pacman -S niri </syntaxhighlight>If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru:<syntaxhighlight lang="bash"> yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix'''<syntaxhighlight lang="nix"> environment.systemPackages = [ pkgs.niri ]; </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below:<syntaxhighlight lang="bash"> pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install.<syntaxhighlight> sudo zypper in niri </syntaxhighlight>Alternatively, you can install it with '''opi''' as well.<syntaxhighlight> opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''.<syntaxhighlight lang="bash"> sudo xbps-install -S niri </syntaxhighlight> == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file. While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages bellow to ensure app functionality.<syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session).<syntaxhighlight lang="bash"> mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight>'''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder.<syntaxhighlight lang="bash"> ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight>'''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight>After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''.<syntaxhighlight lang="bash"> ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight>Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''.<syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight>Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before.<syntaxhighlight lang="bash"> ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight>That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so. Let's set up '''xwayland-satellite''' like this. Open the config file located in '''~/.config/niri/config.kdl''' with your favorite text editor.<syntaxhighlight lang="bash"> nano ~/.config/niri/config.kdl </syntaxhighlight>add the line below to the config. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight>Let's set up '''swaybg''' like this instead of systemd. Add the following to your config file.<syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight>That's it! Some may find this approach a lot easier than the systemd one, however you won't be able to easily monitor their status and output, or restart and reload them. == Configuration == Niri is extremely customizable thanks to it's powerful config file. YaLTeR has done an incredible job of writing [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview official documentation] for niri, so please refer to it for configuration instructions. 519b0bda1f67db9698c9c5689094d50694345b22 1763 1760 2025-01-24T19:09:22Z Glocean 124 wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]]. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor. == Features == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Arch Linux === To download the latest stable release, run the following command:<syntaxhighlight lang="bash"> sudo pacman -S niri </syntaxhighlight>If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru:<syntaxhighlight lang="bash"> yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix'''<syntaxhighlight lang="nix"> environment.systemPackages = [ pkgs.niri ]; </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below:<syntaxhighlight lang="bash"> pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install.<syntaxhighlight> sudo zypper in niri </syntaxhighlight>Alternatively, you can install it with '''opi''' as well.<syntaxhighlight> opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''.<syntaxhighlight lang="bash"> sudo xbps-install -S niri </syntaxhighlight> == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file. While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages bellow to ensure app functionality.<syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session).<syntaxhighlight lang="bash"> mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight>'''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder.<syntaxhighlight lang="bash"> ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight>'''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight>After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''.<syntaxhighlight lang="bash"> ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight>Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''.<syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight>Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before.<syntaxhighlight lang="bash"> ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight>That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so. Let's set up '''xwayland-satellite''' like this. Open the config file located in '''~/.config/niri/config.kdl''' with your favorite text editor.<syntaxhighlight lang="bash"> nano ~/.config/niri/config.kdl </syntaxhighlight>add the line below to the config. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight>Let's set up '''swaybg''' like this instead of systemd. Add the following to your config file.<syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight>That's it! Some may find this approach a lot easier than the systemd one, however you won't be able to easily monitor their status and output, or restart and reload them. == Configuration == Niri is extremely customizable thanks to it's powerful config file. YaLTeR has done an incredible job of writing [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview official documentation] for niri, so please refer to it for configuration instructions. 9b1158eb1eb6e1ce404f96cea17e36ee497e20fa 1764 1763 2025-01-24T19:39:11Z Glocean 124 Added citations wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref>The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor. == Features == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config<ref>https://github.com/YaLTeR/niri?tab=readme-ov-file#features</ref> == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Arch Linux === To download the latest stable release, run the following command:<syntaxhighlight lang="bash"> sudo pacman -S niri </syntaxhighlight>If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru:<syntaxhighlight lang="bash"> yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix'''<syntaxhighlight lang="nix"> environment.systemPackages = [ pkgs.niri ]; </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below:<syntaxhighlight lang="bash"> pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install.<syntaxhighlight> sudo zypper in niri </syntaxhighlight>Alternatively, you can install it with '''opi''' as well.<syntaxhighlight> opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''.<syntaxhighlight lang="bash"> sudo xbps-install -S niri </syntaxhighlight> == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file. While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref>https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages bellow to ensure app functionality.<syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref>https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session).<syntaxhighlight lang="bash"> mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight>'''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder.<syntaxhighlight lang="bash"> ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight>'''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight>After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''.<syntaxhighlight lang="bash"> ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight>Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''.<syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight>Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before.<syntaxhighlight lang="bash"> ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight>That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so. Let's set up '''xwayland-satellite''' like this. Open the config file located in '''~/.config/niri/config.kdl''' with your favorite text editor.<syntaxhighlight lang="bash"> nano ~/.config/niri/config.kdl </syntaxhighlight>add the line below to the config. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight>Let's set up '''swaybg''' like this instead of systemd. Add the following to your config file.<syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight>That's it! Some may find this approach a lot easier than the systemd one, however you won't be able to easily monitor their status and output, or restart and reload them. == Configuration == Niri is extremely customizable thanks to it's powerful config file. YaLTeR has done an incredible job of writing [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview official documentation] for niri, so please refer to it for configuration instructions. <references /> d5266c77be4fc1b234730c90b793c64892b7a791 1780 1764 2025-02-02T15:27:05Z Amadaluzia 52 Strong cleanup wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref>The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor. == Features == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config<ref>https://github.com/YaLTeR/niri?tab=readme-ov-file#features</ref> == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. <syntaxhighlight> # dnf copr enable yalter/niri # dnf install niri </syntaxhighlight> === Arch Linux === To download the latest stable release, run the following command: <syntaxhighlight> # pacman -S niri </syntaxhighlight> If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: <syntaxhighlight> $ yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix''' <syntaxhighlight lang="nix"> {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; # In case you want to override niri. }; } </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: <syntaxhighlight> # pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. <syntaxhighlight> # zypper in niri </syntaxhighlight> Alternatively, you can install it with '''opi''' as well. <syntaxhighlight> # opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''. <syntaxhighlight> # xbps-install -S niri </syntaxhighlight> === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file. While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref>https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages bellow to ensure app functionality. Do note that the list of packages below doesn't apply to all distributions. <syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref>https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session). <syntaxhighlight> $ mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight> '''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder. <syntaxhighlight> $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> '''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight> After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight> Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so. In this case, if you desire XWayland, you may add the following to your configuration. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight> You may also automatically start <code>swaybg</code> in a similar manner. <syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight> For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. <references /> c8fc9a126c4e31b2ade6c29b7a63c3581f56205c 4 340 1759 1693 2025-01-23T21:29:08Z Atmois 13 Fix SPAG and improve readability wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Contributing#Citations]] guideline ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. E.g., instead of saying, "XYZ package is bad," say, "XYZ package has received criticism for...". ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details on this can be seen in the [[Contributing#Formatting]] section. If there is any doubt, consult an admin. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible license) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We recommend the following structure, which is adapted from the Harvard Referencing Style: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]].<references /> [[Category:Meta]] bfcb4a164a933cf99f12efbedbe17a8422c2b85a 1765 1759 2025-01-24T20:48:21Z Atmois 13 fix formatting wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Contributing#Citations]] guideline ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. E.g., instead of saying, "XYZ package is bad," say, "XYZ package has received criticism for...". ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details on this can be seen in the [[Contributing#Formatting]] section. If there is any doubt, consult an admin. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible license) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We recommend the following structure, which is adapted from the Harvard Referencing Style: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]].<references /> [[Category:Meta]] 0eebc1c448ba09243d3b3b6b86c2304b46a9be9c 1766 1765 2025-01-24T20:49:20Z Atmois 13 Atmois moved page [[Contributing]] to [[Policies]] without leaving a redirect: Restructing the meta pages wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Contributing#Citations]] guideline ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. E.g., instead of saying, "XYZ package is bad," say, "XYZ package has received criticism for...". ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details on this can be seen in the [[Contributing#Formatting]] section. If there is any doubt, consult an admin. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible license) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We recommend the following structure, which is adapted from the Harvard Referencing Style: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]].<references /> [[Category:Meta]] 0eebc1c448ba09243d3b3b6b86c2304b46a9be9c 1768 1766 2025-01-24T20:52:17Z Atmois 13 fix links wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Policies#Citations]] guideline ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. E.g., instead of saying, "XYZ package is bad," say, "XYZ package has received criticism for...". ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details on this can be seen in the [[Policies#Formatting]] section. If there is any doubt, consult an admin. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible license) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We recommend the following structure, which is adapted from the Harvard Referencing Style: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]].<references /> [[Category:Meta]] 81233a32b10f8af227a133ea071b0c1d3aa946fb 1769 1768 2025-01-24T21:51:56Z Atmois 13 Improvements wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Policies#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Policies#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible license) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We recommend the following structure, which is adapted from the Harvard Referencing Style: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]].<references /> [[Category:Meta]] 1c654d3270d284168d5f166a1b5f41b755adb109 10 513 1761 1712 2025-01-24T18:43:38Z Electron271 3 wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This article was most likely made before strict rules for citations were implemented [[Contributing#Citations|(Read here)]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that still need to be edited.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Needs Citations]]</includeonly><noinclude> {{/doc}}</noinclude> 854079b42229282d561b7bd41eb59a46aa6d5331 6 535 1762 2025-01-24T18:56:16Z Glocean 124 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 10 483 1772 1694 2025-02-01T19:37:17Z Atmois 13 Removed protection from "[[Template:Cleanup]]": test wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified.}}</span> <div class="mbox-text">It might not meet the wiki's [[Contributing#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> df6958dc76e8288fdffd4a6f7eef7b735c06b1e1 1773 1772 2025-02-01T19:37:54Z Atmois 13 Protected "[[Template:Cleanup]]": Test ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified.}}</span> <div class="mbox-text">It might not meet the wiki's [[Contributing#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> df6958dc76e8288fdffd4a6f7eef7b735c06b1e1 4 536 1778 2025-02-02T14:44:48Z Atmois 13 Create draft CoC wikitext text/x-wiki === 1. Safe for Work (SFW) Policy === All Things Linux Wiki is a '''Safe for Work (SFW)''' environment. '''NSFW (Not Safe for Work) content and discussions are strictly prohibited'''. While NSFW typically refers to sexually explicit material, the definition may evolve to include other forms of sensitive content. This applies to all content on the wiki, including but not limited to text, images & media. ==== Prohibited Content: ==== * '''Sexually explicit material''' in any form. * '''Violence, gore, or depictions of animal abuse'''. * '''Glorification of self-harm or suicide'''. == 2. Mutual Respect == All Things Linux Wiki is a '''respectful''' and '''inclusive''' community. ==== Expected Behaviour: ==== * Treat others '''with humility and respect'''. * Keep interactions '''constructive and considerate'''. * '''No harassment''': Bullying, doxxing, or coordinated attacks are '''strictly prohibited'''. * '''No hate speech''': Discriminatory remarks on any personal characteristics will not be tolerated. * '''No threats''': Direct or indirect threats against individuals or groups will result in '''immediate action'''. == 3. Responsible Expression & Discussions == The wiki welcomes '''diverse perspectives''' and encourages constructive discussions, but it is not a '''free-for-all debate forum'''. Please ensure all discussions are kept to talk pages and not done on articles unless it has been designated as a discussion page. ==== Guidelines for Expression: ==== * '''Stay on topic''': Discussions should focus on '''Linux, open-source software, and related technologies'''. * '''No disruptive debates''': Heated, repetitive, or toxic arguments will be moderated. * '''Avoid professional advice''': The wiki does not provide '''medical, legal, financial, or religious advice'''. == 4. Avoidance of Elitism == Linux and technology is for '''everyone''', from beginners to experts. ==== Expected Behaviour: ==== * '''Respect different choices''': Users may prefer different '''distros, desktop environments, package managers, or workflows'''. * '''No gatekeeping''': Beginners should feel welcome, not discouraged. We want to foster a growing Linux and FOSS community. == 5. Respecting Moderators & Rules == Moderators help maintain order. If a moderator asks you to '''modify behaviour, please cooperate'''. * '''Disagreements should be handled via the wiki staff''', not public disputes. * '''Do not backseat moderate''': If someone breaks a rule, report it instead of escalating the situation. == 6. Language Requirement: English Only == * The wiki uses '''English as the primary language'''. == 7. Content Guidelines == All contributions must align with the wiki’s '''goal of providing high-quality Linux documentation'''. ==== Prohibited Content: ==== * '''Low-effort, spam, or non-constructive edits'''. * '''Off-topic material''' unrelated to Linux, open-source software or general technology. * '''Unverified or misleading technical information.''' * '''Spam or self-promoting content''' not relevant to the article. == 8. Privacy & Security == * '''Do not dox or share personal information''' of other users. * '''Be cautious about sharing your own information.''' == 9. Enforcement & Punishments == Moderators '''reserve the right''' to take appropriate action depending on the severity of violations. If you believe a '''member of the team has abused their powers''', it should be '''reported to the administrators''' through a method listed [[Main Page#Contacts|here]]. ==== Possible Actions: ==== * '''Warnings''': Used for minor infractions. * '''Blocks''': Temporary restrictions from editing or participating. * '''IP Blocks''': Restricting editing access entirely. == 10. Punishment Evasion & Appeals == * '''Using alt accounts, VPN's or proxies to evade punishments will result in further punishment for yourself'''. * If you believe a punishment was unfair, you may '''appeal by contacting an administrator''' through a method listed [[Main Page#Contacts|here]]. == 11. Final Note: Exercise Common Sense == Not every situation can be predicted. Use '''good judgment, respect others, and contribute positively''' to the Linux community. If in doubt, '''ask for clarification rather than assuming'''. Thank you for being part of the '''All Things Linux Wiki'''! <blockquote>''<small>The Code of Conduct (CoC) for the wiki is adapted from the [https://allthingslinux.org/code-of-conduct All Things Linux CoC].</small>'' </blockquote> [[Category:Meta]] 45656c904f92ca48f602d653f97ba4c5c856c95f 1779 1778 2025-02-02T14:45:01Z Atmois 13 Protected "[[Code of Conduct]]": High traffic page: Meta ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki === 1. Safe for Work (SFW) Policy === All Things Linux Wiki is a '''Safe for Work (SFW)''' environment. '''NSFW (Not Safe for Work) content and discussions are strictly prohibited'''. While NSFW typically refers to sexually explicit material, the definition may evolve to include other forms of sensitive content. This applies to all content on the wiki, including but not limited to text, images & media. ==== Prohibited Content: ==== * '''Sexually explicit material''' in any form. * '''Violence, gore, or depictions of animal abuse'''. * '''Glorification of self-harm or suicide'''. == 2. Mutual Respect == All Things Linux Wiki is a '''respectful''' and '''inclusive''' community. ==== Expected Behaviour: ==== * Treat others '''with humility and respect'''. * Keep interactions '''constructive and considerate'''. * '''No harassment''': Bullying, doxxing, or coordinated attacks are '''strictly prohibited'''. * '''No hate speech''': Discriminatory remarks on any personal characteristics will not be tolerated. * '''No threats''': Direct or indirect threats against individuals or groups will result in '''immediate action'''. == 3. Responsible Expression & Discussions == The wiki welcomes '''diverse perspectives''' and encourages constructive discussions, but it is not a '''free-for-all debate forum'''. Please ensure all discussions are kept to talk pages and not done on articles unless it has been designated as a discussion page. ==== Guidelines for Expression: ==== * '''Stay on topic''': Discussions should focus on '''Linux, open-source software, and related technologies'''. * '''No disruptive debates''': Heated, repetitive, or toxic arguments will be moderated. * '''Avoid professional advice''': The wiki does not provide '''medical, legal, financial, or religious advice'''. == 4. Avoidance of Elitism == Linux and technology is for '''everyone''', from beginners to experts. ==== Expected Behaviour: ==== * '''Respect different choices''': Users may prefer different '''distros, desktop environments, package managers, or workflows'''. * '''No gatekeeping''': Beginners should feel welcome, not discouraged. We want to foster a growing Linux and FOSS community. == 5. Respecting Moderators & Rules == Moderators help maintain order. If a moderator asks you to '''modify behaviour, please cooperate'''. * '''Disagreements should be handled via the wiki staff''', not public disputes. * '''Do not backseat moderate''': If someone breaks a rule, report it instead of escalating the situation. == 6. Language Requirement: English Only == * The wiki uses '''English as the primary language'''. == 7. Content Guidelines == All contributions must align with the wiki’s '''goal of providing high-quality Linux documentation'''. ==== Prohibited Content: ==== * '''Low-effort, spam, or non-constructive edits'''. * '''Off-topic material''' unrelated to Linux, open-source software or general technology. * '''Unverified or misleading technical information.''' * '''Spam or self-promoting content''' not relevant to the article. == 8. Privacy & Security == * '''Do not dox or share personal information''' of other users. * '''Be cautious about sharing your own information.''' == 9. Enforcement & Punishments == Moderators '''reserve the right''' to take appropriate action depending on the severity of violations. If you believe a '''member of the team has abused their powers''', it should be '''reported to the administrators''' through a method listed [[Main Page#Contacts|here]]. ==== Possible Actions: ==== * '''Warnings''': Used for minor infractions. * '''Blocks''': Temporary restrictions from editing or participating. * '''IP Blocks''': Restricting editing access entirely. == 10. Punishment Evasion & Appeals == * '''Using alt accounts, VPN's or proxies to evade punishments will result in further punishment for yourself'''. * If you believe a punishment was unfair, you may '''appeal by contacting an administrator''' through a method listed [[Main Page#Contacts|here]]. == 11. Final Note: Exercise Common Sense == Not every situation can be predicted. Use '''good judgment, respect others, and contribute positively''' to the Linux community. If in doubt, '''ask for clarification rather than assuming'''. Thank you for being part of the '''All Things Linux Wiki'''! <blockquote>''<small>The Code of Conduct (CoC) for the wiki is adapted from the [https://allthingslinux.org/code-of-conduct All Things Linux CoC].</small>'' </blockquote> [[Category:Meta]] 45656c904f92ca48f602d653f97ba4c5c856c95f 2 3 1781 1123 2025-02-02T15:39:55Z Amadaluzia 52 Change TOML to Zig wikitext text/x-wiki <syntaxhighlight lang="zig"> const AboutMe = struct { name: []u8, bday: [][]u8, os: [][]u8, locales: [][]u8, programmingLanguages: [][]u8, extra: []u8 } const Socials = struct { discord: []u8, matrix: []u8, xmpp: []u8, libera: []u8, github: []u8, codeberg: []u8, youtube: []u8, } pub fn main() void { _ = AboutMe{ .name: "Artur Manuel", .bday: []u8{"4", "September", "2007"}, .os: []u8{"NixOS", "Gentoo"} .locales: []u8{"en_GB", "pt_PT"}, // learning de_DE .programmingLanguages: []u8{"Nix", "Python", "Go", "Haskell", "Rust", "C", "Zig"}, .extra: "Opps caught me being Portuguese at birth." } _ = Socials{ .discord: "@amadaluzia", .matrix: "@amadaluzia:tchncs.de", .xmpp: "@amadaluzia@paranoid.network", .libera: "amadaluzia", .github: "amadaluzia", .codeberg: "amadaluzia", .youtube: "@amadaluzia", } } </syntaxhighlight> 5cdb463fd783e1435d08523122e1f4e89b90abeb 0 250 1782 1219 2025-02-02T17:38:59Z Asiliria 7 Moving Page wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == Ana/Miniconda Setup == ... (tomorrow's problem) == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards on more demanding games. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of Artificial Intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU -''' considering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> [[Category:Guides]] 3f6852210adfa022d9646483275bc155be9618e4 1783 1782 2025-02-02T17:41:10Z Asiliria 7 Phrasing was bad! wikitext text/x-wiki [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == Ana/Miniconda Setup == ... (tomorrow's problem) == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU -''' considering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> [[Category:Guides]] bf95b0ccfe80f63d5ae4bb45356d7c8240643375 0 319 1784 1516 2025-02-02T17:44:11Z Asiliria 7 be clearer - accuracy of information wikitext text/x-wiki '''Ricing''' (''slang'') refers to extensively customizing a [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to create a unique, personalized computing experience. The term originated from the automotive modification scene ("ricer" cars) and has been adopted by the Linux/Unix community. While primarily focused on aesthetic customization through themes, colors, widgets, and interface layouts, ricing can improve functionality and performance. Common ricing elements include: * Custom window borders, titlebars, decorations; * Color schemes and typography; * Specialized status bars and system monitors; * Custom application launchers and menus * Personalized desktop widgets and notifications * Modified system icons and cursors Popular tools for ricing include customization frameworks such as polybar and picom for window managers like i3, bspwm, and dwm. The ricing community actively shares configurations ("dotfiles") and screenshots on platforms like Reddit's r/unixporn. [[Category:Terminology]] 1ce24c42ba97dfbdabe6cb9a816bafa5efb90c04 1785 1784 2025-02-02T17:54:04Z Asiliria 7 more phrasing wikitext text/x-wiki '''Ricing''' (''slang'') refers to extensively customizing a [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to create a unique, personalized computing experience. The term originated from the automotive modification scene ("ricer" cars) and has been adopted by the Linux/Unix community. While primarily focused on aesthetic customization through themes, colors, widgets, and interface layouts, ricing can improve functionality and performance. Common ricing elements include: * Custom window borders, titlebars, decorations; * Color schemes and typography; * Specialized status bars and system monitors; * Custom application launchers and menus * Personalized desktop widgets and notifications * Modified system icons and cursors Popular tools for ricing include customization frameworks such as polybar and picom for window managers like i3, bspwm, and dwm. People frequently share configuration files, or "dotfiles," and screenshots - [https://www.reddit.com/r/unixporn/ r/unixporn] is one of the most popular. [[Category:Terminology]] f7c8ed5c77a9149daa61d2f1572611ad48d01665 2 289 1786 1515 2025-02-02T17:55:31Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml" line="1"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <distro>Gentoo Linux</distro> <extra>Furry (Axolotl)</extra> <website>https://mymetype.neocities.org</website> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json" line="1"> { "atl.wiki":{ "todo":{ "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> db01dbaa37a6ac239093a3400b7b2709371f37f2 2 289 1787 1786 2025-02-02T17:57:45Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml" line="1"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <os> <linux>Gentoo<linux> <windows>Windows 10 Pro N</windows> <macos>macOS 12 (Monterrey)<macos> </os> <extra>Furry (Axolotl)</extra> <website>https://mymetype.neocities.org</website> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json" line="1"> { "atl.wiki":{ "todo":{ "Linux From Scratch":"https://atl.wiki/index.php/Linux_From_Scratch" }, "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 37b786b2e2c34d8ebd98e69871942a52863f4045 1789 1787 2025-02-02T19:42:29Z MymeType 35 wikitext text/x-wiki <syntaxhighlight lang="xml" line="1"> <?xml version="1.0" encoding="UTF-8"?> <profile> <about> <name>MymeType</name> <birthdate>2008-09-13</birthdate> <pronouns>he/him</pronouns> <os> <linux>Gentoo<linux> <windows>Windows 10 Pro N</windows> <macos>macOS 12 (Monterrey)<macos> </os> <extra>Furry (Axolotl)</extra> <website>https://mymetype.neocities.org</website> </about> </profile> </syntaxhighlight> <syntaxhighlight lang="json" line="1"> { "atl.wiki":{ "todo":{ null } "misc":{ "sandbox":"https://atl.wiki/index.php/User:MymeType/Sandbox", "talkpage":"https://atl.wiki/index.php/User_talk:MymeType" } } } </syntaxhighlight> 19832f8d223eb1b3bfe76d6de75dda29d86dbe66 0 537 1788 2025-02-02T19:40:24Z MymeType 35 Created Linux From Scratch page wikitext text/x-wiki {{DistributionInfobox|title=Linux From Scratch|image=[[File:Linux-From-Scratch logo.png|Linux-From-Scratch_logo]]|caption=Linux From Scratch logo|releasestatus=Maintained|packagemanager=None|releasemodel=Stable|usagetype=Source-based, Education|defaultdesktops=[[Fluxbox]], [[IceWM]], [[KDE Plasma]], [[LXQt]], [[Openbox]], [[Xfce]], [[GNOME]] (BLFS)|website=[https://www.linuxfromscratch.org/index.html www.linuxfromscratch.org]|architectures=i386, x86_64}} Linux From Scratch is the name of a type of [[Linux]] install and the name of a book written by Gerard Beekmans, which gives detailed instructions on how to achieve a fully functional Linux operating system entirely by compiling source packages. The book is available for free on the official website and major releases are usually published twice a year<ref>[https://www.linuxfromscratch.org/lfs/news.html "LFS News"]. ''www.linuxfromscratch.org''.</ref>. [[File:Linux From Scratch desktop.jpg|alt=Screenshot of a Linux From Scratch install with a modified Xfce desktop.|thumb|Screenshot of a Linux From Scratch install with a modified Xfce desktop.]] == Projects under LFS == The following projects are part of the Linux From Scratch umbrella and are accessible on the official website, and are as follows: * '''Linux From Scratch (LFS)''': The original book itself, which gives detailed instructions on how to create a bootable and fully functional Linux system by compiling source packages<ref>[https://www.linuxfromscratch.org/lfs/ "LFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. * '''Beyond Linux From Scratch (BLFS)''': An extension of the original LFS book to extend the functionality of a LFS system by providing instruction on how to compile a wide variety of additional packages, such as desktop environments and networking tools<ref>[https://www.linuxfromscratch.org/blfs/ "BLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. * '''Automated Linux From Scratch (ALFS)''': A project meant to automate the compilation of the various packages needed for a LFS system via the use of scripts<ref name=":0">[https://www.linuxfromscratch.org/alfs/ "MLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. The current official implementation of ALFS is ''jhalfs''<ref name=":0" />. * '''Multilib-LFS (MLFS)''': A variant of the original LFS book to build a system that's able to execute 32-bit binaries<ref>[https://www.linuxfromscratch.org/mlfs/ "MLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. It is cited as a strongly recommended requirement for GLFS<ref name=":1">[https://www.linuxfromscratch.org/glfs/ "GLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. * '''Gaming Linux From Scratch (GLFS)''': A guide based off the BLFS book that provides instructions for installing gaming software such as [[Steam]] and [[Wine]], software libraries such as [[OpenGL]] and [[Vulkan]] and proprietary graphics drivers for [[Nvidia]] and [[AMD]] GPUs<ref name=":1" />. * '''Hints''': Large library of user-submitted documents which provide tips on various things related to maintaining LFS systems<ref>[https://www.linuxfromscratch.org/hints/ "LFS Hints Project Home"]. ''www.linuxfromscratch.org''.</ref>. * '''Patches''': Central repository of user-submitted patch files to add LFS-specific functionality to various packages and also serves as a testing ground for patches that may be added to new LFS and BLFS versions<ref>[https://www.linuxfromscratch.org/patches/ "LFS Patches Project Home"]. ''www.linuxfromscratch.org''.</ref>. * '''LFS Editor's Guide''': Small document that describes the LFS development process<ref>[https://www.linuxfromscratch.org/lfs/LFS-EDITORS-GUIDE.html "Linux From Scratch Editor's Manual"]. ''www.linuxfromscratch.org''.</ref>. * '''Museum''': Archive of old LFS versions<ref>[https://www.linuxfromscratch.org/museum/ "Index of /museum"]. ''www.linuxfromscratch.org''.</ref>. == Standard build unit (SBU) == A peculiar feature of LFS is its usage of special measurement units to calculate the approximate time that a package takes to fully compile called standard build units (SBUs)<ref>[https://www.linuxfromscratch.org/lfs/view/stable/chapter04/aboutsbus.html "4.5 About SBUs"]. ''www.linuxfromscratch.org''</ref>, and 1 SBU is roughly equal to the time it takes to compile the first package in the LFS book, [[binutils]]<ref>[https://www.linuxfromscratch.org/lfs/view/stable/chapter05/binutils-pass1.html "5.2. Binutils-2.43.1 - Pass 1"]. ''www.linuxfromscratch.org.'' Retrieved 2 February 2025.</ref>. For example, if it took about 10 minutes to compile binutils, and the [[GRUB]] page says that it takes approximately 0.3 SBUs to build<ref>[https://www.linuxfromscratch.org/lfs/view/stable/chapter08/grub.html "8.64. GRUB-2.12"]. ''www.linuxfromscratch.org''. Retrieved 2 February 2025.</ref>, you would multiply the amount of time for how many SBUs the page says it would take, resulting in about 3 minutes of compile time. 5be679f59521f04ad3bee659f8eb55e70987b8fe 4 536 1790 1779 2025-02-02T23:12:00Z Atmois 13 Add AI image rule wikitext text/x-wiki === 1. Safe for Work (SFW) Policy === All Things Linux Wiki is a '''Safe for Work (SFW)''' environment. '''NSFW (Not Safe for Work) content and discussions are strictly prohibited'''. While NSFW typically refers to sexually explicit material, the definition may evolve to include other forms of sensitive content. This applies to all content on the wiki, including but not limited to text, images & media. ==== Prohibited Content: ==== * '''Sexually explicit material''' in any form. * '''Violence, gore, or depictions of animal abuse'''. * '''Glorification of self-harm or suicide'''. == 2. Mutual Respect == All Things Linux Wiki is a '''respectful''' and '''inclusive''' community. ==== Expected Behaviour: ==== * Treat others '''with humility and respect'''. * Keep interactions '''constructive and considerate'''. * '''No harassment''': Bullying, doxxing, or coordinated attacks are '''strictly prohibited'''. * '''No hate speech''': Discriminatory remarks on any personal characteristics will not be tolerated. * '''No threats''': Direct or indirect threats against individuals or groups will result in '''immediate action'''. == 3. Responsible Expression & Discussions == The wiki welcomes '''diverse perspectives''' and encourages constructive discussions, but it is not a '''free-for-all debate forum'''. Please ensure all discussions are kept to talk pages and not done on articles unless it has been designated as a discussion page. ==== Guidelines for Expression: ==== * '''Stay on topic''': Discussions should focus on '''Linux, open-source software, and related technologies'''. * '''No disruptive debates''': Heated, repetitive, or toxic arguments will be moderated. * '''Avoid professional advice''': The wiki does not provide '''medical, legal, financial, or religious advice'''. == 4. Avoidance of Elitism == Linux and technology is for '''everyone''', from beginners to experts. ==== Expected Behaviour: ==== * '''Respect different choices''': Users may prefer different '''distros, desktop environments, package managers, or workflows'''. * '''No gatekeeping''': Beginners should feel welcome, not discouraged. We want to foster a growing Linux and FOSS community. == 5. Respecting Moderators & Rules == Moderators help maintain order. If a moderator asks you to '''modify behaviour, please cooperate'''. * '''Disagreements should be handled via the wiki staff''', not public disputes. * '''Do not backseat moderate''': If someone breaks a rule, report it instead of escalating the situation. == 6. Language Requirement: English Only == * The wiki uses '''English as the primary language'''. == 7. Content Guidelines == All contributions must align with the wiki’s '''goal of providing high-quality Linux documentation'''. ==== Prohibited Content: ==== * '''Low-effort, spam, or non-constructive edits'''. * '''Off-topic material''' unrelated to Linux, open-source software or general technology. * '''Unverified or misleading technical information.''' * '''Spam or self-promoting content''' not relevant to the article. * AI Generated images are prohibited unless it is relevant to an article and clearly disclosed as being AI generated. == 8. Privacy & Security == * '''Do not dox or share personal information''' of other users. * '''Be cautious about sharing your own information.''' == 9. Enforcement & Punishments == Moderators '''reserve the right''' to take appropriate action depending on the severity of violations. If you believe a '''member of the team has abused their powers''', it should be '''reported to the administrators''' through a method listed [[Main Page#Contacts|here]]. ==== Possible Actions: ==== * '''Warnings''': Used for minor infractions. * '''Blocks''': Temporary restrictions from editing or participating. * '''IP Blocks''': Restricting editing access entirely. == 10. Punishment Evasion & Appeals == * '''Using alt accounts, VPN's or proxies to evade punishments will result in further punishment for yourself'''. * If you believe a punishment was unfair, you may '''appeal by contacting an administrator''' through a method listed [[Main Page#Contacts|here]]. == 11. Final Note: Exercise Common Sense == Not every situation can be predicted. Use '''good judgment, respect others, and contribute positively''' to the Linux community. If in doubt, '''ask for clarification rather than assuming'''. Thank you for being part of the '''All Things Linux Wiki'''! <blockquote>''<small>The Code of Conduct (CoC) for the wiki is adapted from the [https://allthingslinux.org/code-of-conduct All Things Linux CoC].</small>'' </blockquote> [[Category:Meta]] 4191b64a1297aa81768c492287c328d22e0e148a 1794 1790 2025-02-07T18:56:31Z Atmois 13 Update naming of atl.wiki wikitext text/x-wiki === 1. Safe for Work (SFW) Policy === atl.wiki is a '''Safe for Work (SFW)''' environment. '''NSFW (Not Safe for Work) content and discussions are strictly prohibited'''. While NSFW typically refers to sexually explicit material, the definition may evolve to include other forms of sensitive content. This applies to all content on the wiki, including but not limited to text, images & media. ==== Prohibited Content: ==== * '''Sexually explicit material''' in any form. * '''Violence, gore, or depictions of animal abuse'''. * '''Glorification of self-harm or suicide'''. == 2. Mutual Respect == atl.wiki is a '''respectful''' and '''inclusive''' community. ==== Expected Behaviour: ==== * Treat others '''with humility and respect'''. * Keep interactions '''constructive and considerate'''. * '''No harassment''': Bullying, doxxing, or coordinated attacks are '''strictly prohibited'''. * '''No hate speech''': Discriminatory remarks on any personal characteristics will not be tolerated. * '''No threats''': Direct or indirect threats against individuals or groups will result in '''immediate action'''. == 3. Responsible Expression & Discussions == The wiki welcomes '''diverse perspectives''' and encourages constructive discussions, but it is not a '''free-for-all debate forum'''. Please ensure all discussions are kept to talk pages and not done on articles unless it has been designated as a discussion page. ==== Guidelines for Expression: ==== * '''Stay on topic''': Discussions should focus on '''Linux, open-source software, and related technologies'''. * '''No disruptive debates''': Heated, repetitive, or toxic arguments will be moderated. * '''Avoid professional advice''': The wiki does not provide '''medical, legal, financial, or religious advice'''. == 4. Avoidance of Elitism == Linux and technology is for '''everyone''', from beginners to experts. ==== Expected Behaviour: ==== * '''Respect different choices''': Users may prefer different '''distros, desktop environments, package managers, or workflows'''. * '''No gatekeeping''': Beginners should feel welcome, not discouraged. We want to foster a growing Linux and FOSS community. == 5. Respecting Moderators & Rules == Moderators help maintain order. If a moderator asks you to '''modify behaviour, please cooperate'''. * '''Disagreements should be handled via the wiki staff''', not public disputes. * '''Do not backseat moderate''': If someone breaks a rule, report it instead of escalating the situation. == 6. Language Requirement: English Only == * The wiki uses '''English as the primary language'''. == 7. Content Guidelines == All contributions must align with the wiki’s '''goal of providing high-quality Linux documentation'''. ==== Prohibited Content: ==== * '''Low-effort, spam, or non-constructive edits'''. * '''Off-topic material''' unrelated to Linux, open-source software or general technology. * '''Unverified or misleading technical information.''' * '''Spam or self-promoting content''' not relevant to the article. * AI Generated images are prohibited unless it is relevant to an article and clearly disclosed as being AI generated. == 8. Privacy & Security == * '''Do not dox or share personal information''' of other users. * '''Be cautious about sharing your own information.''' == 9. Enforcement & Punishments == Moderators '''reserve the right''' to take appropriate action depending on the severity of violations. If you believe a '''member of the team has abused their powers''', it should be '''reported to the administrators''' through a method listed [[Main Page#Contacts|here]]. ==== Possible Actions: ==== * '''Warnings''': Used for minor infractions. * '''Blocks''': Temporary restrictions from editing or participating. * '''IP Blocks''': Restricting editing access entirely. == 10. Punishment Evasion & Appeals == * '''Using alt accounts, VPN's or proxies to evade punishments will result in further punishment for yourself'''. * If you believe a punishment was unfair, you may '''appeal by contacting an administrator''' through a method listed [[Main Page#Contacts|here]]. == 11. Final Note: Exercise Common Sense == Not every situation can be predicted. Use '''good judgment, respect others, and contribute positively''' to the Linux community. If in doubt, '''ask for clarification rather than assuming'''. Thank you for being part of the '''atl.wiki'''! <blockquote>''<small>The Code of Conduct (CoC) for the wiki is adapted from the [https://allthingslinux.org/code-of-conduct All Things Linux CoC].</small>'' </blockquote> [[Category:Meta]] 181dc0122dac9b353deda581c689b4fd40a2489b 1799 1794 2025-02-09T19:23:06Z Atmois 13 Atmois moved page [[Code of Conduct]] to [[Atl.wiki:Code of Conduct]]: Move to meta namespace wikitext text/x-wiki === 1. Safe for Work (SFW) Policy === atl.wiki is a '''Safe for Work (SFW)''' environment. '''NSFW (Not Safe for Work) content and discussions are strictly prohibited'''. While NSFW typically refers to sexually explicit material, the definition may evolve to include other forms of sensitive content. This applies to all content on the wiki, including but not limited to text, images & media. ==== Prohibited Content: ==== * '''Sexually explicit material''' in any form. * '''Violence, gore, or depictions of animal abuse'''. * '''Glorification of self-harm or suicide'''. == 2. Mutual Respect == atl.wiki is a '''respectful''' and '''inclusive''' community. ==== Expected Behaviour: ==== * Treat others '''with humility and respect'''. * Keep interactions '''constructive and considerate'''. * '''No harassment''': Bullying, doxxing, or coordinated attacks are '''strictly prohibited'''. * '''No hate speech''': Discriminatory remarks on any personal characteristics will not be tolerated. * '''No threats''': Direct or indirect threats against individuals or groups will result in '''immediate action'''. == 3. Responsible Expression & Discussions == The wiki welcomes '''diverse perspectives''' and encourages constructive discussions, but it is not a '''free-for-all debate forum'''. Please ensure all discussions are kept to talk pages and not done on articles unless it has been designated as a discussion page. ==== Guidelines for Expression: ==== * '''Stay on topic''': Discussions should focus on '''Linux, open-source software, and related technologies'''. * '''No disruptive debates''': Heated, repetitive, or toxic arguments will be moderated. * '''Avoid professional advice''': The wiki does not provide '''medical, legal, financial, or religious advice'''. == 4. Avoidance of Elitism == Linux and technology is for '''everyone''', from beginners to experts. ==== Expected Behaviour: ==== * '''Respect different choices''': Users may prefer different '''distros, desktop environments, package managers, or workflows'''. * '''No gatekeeping''': Beginners should feel welcome, not discouraged. We want to foster a growing Linux and FOSS community. == 5. Respecting Moderators & Rules == Moderators help maintain order. If a moderator asks you to '''modify behaviour, please cooperate'''. * '''Disagreements should be handled via the wiki staff''', not public disputes. * '''Do not backseat moderate''': If someone breaks a rule, report it instead of escalating the situation. == 6. Language Requirement: English Only == * The wiki uses '''English as the primary language'''. == 7. Content Guidelines == All contributions must align with the wiki’s '''goal of providing high-quality Linux documentation'''. ==== Prohibited Content: ==== * '''Low-effort, spam, or non-constructive edits'''. * '''Off-topic material''' unrelated to Linux, open-source software or general technology. * '''Unverified or misleading technical information.''' * '''Spam or self-promoting content''' not relevant to the article. * AI Generated images are prohibited unless it is relevant to an article and clearly disclosed as being AI generated. == 8. Privacy & Security == * '''Do not dox or share personal information''' of other users. * '''Be cautious about sharing your own information.''' == 9. Enforcement & Punishments == Moderators '''reserve the right''' to take appropriate action depending on the severity of violations. If you believe a '''member of the team has abused their powers''', it should be '''reported to the administrators''' through a method listed [[Main Page#Contacts|here]]. ==== Possible Actions: ==== * '''Warnings''': Used for minor infractions. * '''Blocks''': Temporary restrictions from editing or participating. * '''IP Blocks''': Restricting editing access entirely. == 10. Punishment Evasion & Appeals == * '''Using alt accounts, VPN's or proxies to evade punishments will result in further punishment for yourself'''. * If you believe a punishment was unfair, you may '''appeal by contacting an administrator''' through a method listed [[Main Page#Contacts|here]]. == 11. Final Note: Exercise Common Sense == Not every situation can be predicted. Use '''good judgment, respect others, and contribute positively''' to the Linux community. If in doubt, '''ask for clarification rather than assuming'''. Thank you for being part of the '''atl.wiki'''! <blockquote>''<small>The Code of Conduct (CoC) for the wiki is adapted from the [https://allthingslinux.org/code-of-conduct All Things Linux CoC].</small>'' </blockquote> [[Category:Meta]] 181dc0122dac9b353deda581c689b4fd40a2489b 8 538 1791 2025-02-05T14:08:44Z Atmois 13 Add Notice for relicensing wikitext text/x-wiki Please note that all new edits to atl.wiki will be now licensed as [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0]. Existing content is under the process of being re-licensed. The wiki footer and copyright notice will be updated accordingly once this process has finished. 2f8e121bddff7ccfb32bbd4561d4a0ad73623c80 1792 1791 2025-02-05T14:09:18Z Atmois 13 Protected "[[MediaWiki:Sitenotice]]": High traffic page: Wiki interface ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki Please note that all new edits to atl.wiki will be now licensed as [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0]. Existing content is under the process of being re-licensed. The wiki footer and copyright notice will be updated accordingly once this process has finished. 2f8e121bddff7ccfb32bbd4561d4a0ad73623c80 0 539 1793 2025-02-06T03:35:20Z Rayk4z1 62 Began the Kernel Commands Page: Added Basic Information header, SysReq Information and a table on possible Kernel Command Combinations to serve as a guide wikitext text/x-wiki '''Kernel commands''' are special key combinations that allow direct communication with the operating system's '''[[kernel]]''', the core part of the system that manages hardware and software interactions. These commands let users perform important tasks like '''forcing reboots, ending unresponsive processes, and running memory diagnostics'''. They are mostly used for system recovery and debugging when the operating system becomes unresponsive. However, because they operate at such a low level, improper use can result in '''data loss or system damage''' and should be used with caution. === The SysReq (System Request) Key<ref>[https://www.delorie.com/djgpp/doc/rbinter/id/30/15.html Ralf Brown's Interrupt List] - Callout or Callback (usually hooked rather than called)</ref> === The '''SysReq key''' was first introduced by IBM with the '''PC/AT''' and was originally meant to handle low-level operating system functions. In computing, "low-level" refers to processes that interact more directly with hardware.<ref>[https://web.archive.org/web/20060814072427/http://www-03.ibm.com/ibm/history/exhibits/pc25/pc25_fact.html The IBM Archives: Product Fact Sheet] - Wayback Machine: IBM</ref> For example, the programming language '''C''' is commonly used to develop operating systems because it allows efficient communication with hardware components. At first, the SysRq key was designed to '''prevent software conflicts''' by allowing system-level commands to run without interference from active applications. However, as operating systems advanced, its role changed across different platforms.<ref>[[wikipedia:System_request#cite_ref-mskb43648_6-0|System request]] - Wikipedia: The Free Encyclopedia</ref> ==== Use of the SysRq Key in Different Operating Systems ==== * '''Linux:''' The kernel can use the '''SysReq key''' to execute important commands, often for system recovery and debugging. The '''Magic SysRq key''' combinations allow users to restart the system, kill unresponsive processes, or recover from crashes without using the standard user interface.<ref>[https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html Linux Magic System Request Key Hacks] - What is the magic SysRq key?</ref> * '''Windows:''' In modern versions of '''Windows''', the SysReq key is mostly unused. However, it was once used for system debugging and, in some cases, has been repurposed by software like '''remote desktop tools''' or '''virtualization platforms''' to send special key commands.<ref>[https://web.archive.org/web/20081108021540/http://support.microsoft.com/kb/43648 Returning Control to Codeview] - Microsoft @2008</ref> While the '''SysRq key''' is no longer widely used in mainstream computing, it remains relevant for '''system administrators, developers, and users of certain non-mainstream operating systems''' who need a way to interact with the system at a low level. == Linux SysReq Information Table == To begin a kernel command, press & hold the <code>ALT</code>, then '''press''' <code>PrtSc</code> (You are not required to hold the key down). Then press on of the keys below:<ref>[https://www.kernel.org/doc/html/v4.14/admin-guide/sysrq.html?highlight=sysrq Linux Magic System Request Key Hacks] — What are the 'command' Keys, ''Documentation for sysrq.c''</ref> {| class="wikitable" |+ !''Letter'' !Use: |- |<code>b</code> |Will immediately begin rebooting the system without attempting to unmount any drives [This may corrupt data during a write operation; it is best to mount all drivers as '''R''' only (Read-only) after any writing operation using <code>u</code> then to reboot. |- | ====== '''<code>c</code>''' ====== |Crashes the system using a NULL pointer dereference -> can return a crash dump to file if configured to send/touch a file. |- |<code>'''d'''</code> |Shows all locks that are held. |- |<code>'''e'''</code> |Kernel sends a '''SIGTERM''' signal to all active processes, terminating them. This does not apply to the '''init''' process. |- |<code>'''f'''</code> |Calls an OOM (Out-of-memory) killer to attempt to kill any processes taking too much memory, but does not panic if nothing can be killed. |- |<code>'''g'''</code> |Used for the Kernel-Debugger (kgdb). |- |<code>'''h'''</code> |Kernel outputs possible commands; if you don't press a key with a corresponding command, it'll just output this instead, just in case!! |- |<code>'''i'''</code> |Kernel sends a '''SIGKILL''' signal to all active processes, killing them. This does not apply to the '''init''' process. |- |<code>'''j'''</code> |Kernel forcibly "thaws" any filesystem frozen by the FIFREEZE ioctl. (A system call to freeze a file system.) |- |<code>k</code> |Kills all programs on a current virtual console. Secure Access Key (SAK). |- |... |This table is a work in progress. |} == Reference List: == <references /> f1094fe0d221e0990f860f153a5cefdea81750f6 0 540 1795 2025-02-08T10:15:47Z Atmois 13 Add redirect wikitext text/x-wiki #REDIRECT [[Policies]] 3bc7a417571ec44b3abecef20d556b7ea97ec70b 4 541 1796 2025-02-09T19:17:54Z Atmois 13 Add disclaimer wikitext text/x-wiki All content unless specified otherwise is available under [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en Creative Commons Attribution-ShareAlike 4.0 International]. '''atl.wiki''' is an online collaborative source of information which is contributed to by individuals to provide a common resource of knowledge on Linux and FOSS related topics. The project is structured, so almost anyone can contribute and alter the content. Please note that any content found on '''atl.wiki''' has been verified by an expert in the relevant field. This does not mean you will not find valuable and accurate information on '''atl.wiki'''. However, '''atl.wiki''' cannot guarantee the validity of the information found here. The content of any given article may recently have been altered by someone whose personal beliefs may not align with established knowledge in the relevant fields. When you use '''atl.wiki''' you acknowledge the following: * <big>'''Review of Information'''</big><br>Whilst editors and '''atl.wiki''' team members attempt to review changes as much and often as we can, we cannot guarantee all pages are reviewed at the same frequency or rigour and that even a small change to a once reviewed page can invalidate the review. * <big>'''No Contract'''</big><br>All information on the wiki is provided freely with no contractual obligation between you, '''atl.wiki''' and its team, anyone who provides service to '''atl.wiki''' or any of the contributors. We are not responsible for information modified or removed on '''atl.wiki''' and the only agreement between you and '''atl.wiki''' is [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en Creative Commons Attribution-ShareAlike 4.0 International]. * <big>'''Trademarks'''</big><br>Any of the trademarks, service marks, collective marks, design rights, or similar rights that are mentioned, used, or cited on '''atl.wiki''' are the property of their respective owners. Their use here does not imply that you may use them for any purpose other than for the same or a similar informational use as contemplated by the original authors of these '''atl.wiki'''. Unless otherwise stated, '''atl.wiki''' is not endorsed by, nor affiliated with, any of the holders of any such rights, and as such, '''atl.wiki''' cannot grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk. * <big>'''Jurisdiction'''</big><br>'''atl.wiki''' content is stored on servers in Germany, and is maintained in reference to the protections afforded under German federal and EU law. Laws in your country or jurisdiction may not protect or permit the same kinds of speech or distribution. '''atl.wiki''' does not advocate for the violation of any laws and cannot be held responsible for any violations of such laws. * <big>'''Professional Advice'''</big><br>'''atl.wiki''' is not a source of professional advice, if you require professional advice please consult a professional who is licensed or knowledgeable in that area. 2e36be4418b62e9fd0639439d119ffc176a47e58 1797 1796 2025-02-09T19:22:34Z Atmois 13 Atmois moved page [[Atl.wiki:General disclaimer]] to [[Atl.wiki:Disclaimer]]: Cleaner Title wikitext text/x-wiki All content unless specified otherwise is available under [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en Creative Commons Attribution-ShareAlike 4.0 International]. '''atl.wiki''' is an online collaborative source of information which is contributed to by individuals to provide a common resource of knowledge on Linux and FOSS related topics. The project is structured, so almost anyone can contribute and alter the content. Please note that any content found on '''atl.wiki''' has been verified by an expert in the relevant field. This does not mean you will not find valuable and accurate information on '''atl.wiki'''. However, '''atl.wiki''' cannot guarantee the validity of the information found here. The content of any given article may recently have been altered by someone whose personal beliefs may not align with established knowledge in the relevant fields. When you use '''atl.wiki''' you acknowledge the following: * <big>'''Review of Information'''</big><br>Whilst editors and '''atl.wiki''' team members attempt to review changes as much and often as we can, we cannot guarantee all pages are reviewed at the same frequency or rigour and that even a small change to a once reviewed page can invalidate the review. * <big>'''No Contract'''</big><br>All information on the wiki is provided freely with no contractual obligation between you, '''atl.wiki''' and its team, anyone who provides service to '''atl.wiki''' or any of the contributors. We are not responsible for information modified or removed on '''atl.wiki''' and the only agreement between you and '''atl.wiki''' is [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en Creative Commons Attribution-ShareAlike 4.0 International]. * <big>'''Trademarks'''</big><br>Any of the trademarks, service marks, collective marks, design rights, or similar rights that are mentioned, used, or cited on '''atl.wiki''' are the property of their respective owners. Their use here does not imply that you may use them for any purpose other than for the same or a similar informational use as contemplated by the original authors of these '''atl.wiki'''. Unless otherwise stated, '''atl.wiki''' is not endorsed by, nor affiliated with, any of the holders of any such rights, and as such, '''atl.wiki''' cannot grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk. * <big>'''Jurisdiction'''</big><br>'''atl.wiki''' content is stored on servers in Germany, and is maintained in reference to the protections afforded under German federal and EU law. Laws in your country or jurisdiction may not protect or permit the same kinds of speech or distribution. '''atl.wiki''' does not advocate for the violation of any laws and cannot be held responsible for any violations of such laws. * <big>'''Professional Advice'''</big><br>'''atl.wiki''' is not a source of professional advice, if you require professional advice please consult a professional who is licensed or knowledgeable in that area. 2e36be4418b62e9fd0639439d119ffc176a47e58 4 542 1798 2025-02-09T19:22:34Z Atmois 13 Atmois moved page [[Atl.wiki:General disclaimer]] to [[Atl.wiki:Disclaimer]]: Cleaner Title wikitext text/x-wiki #REDIRECT [[Atl.wiki:Disclaimer]] 830e6d9ad18cfa7c8deba61a75caefe75e4d5e00 0 543 1800 2025-02-09T19:23:06Z Atmois 13 Atmois moved page [[Code of Conduct]] to [[Atl.wiki:Code of Conduct]]: Move to meta namespace wikitext text/x-wiki #REDIRECT [[Atl.wiki:Code of Conduct]] 5297fcbc5281cc5404dc5a511e409d1c2b4e2f66 0 1 1801 1777 2025-02-09T19:23:25Z Atmois 13 Update link wikitext text/x-wiki <div style='text-align: center;'> <h1>Welcome to the All Things Linux Wiki!</h1> This is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Main_Page#Contacts|Contacts Section]]!</p> </div> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png }} == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out [[metawikimedia:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. ====== Moderation ====== All changes go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, don't worry about this as it only exists to stop spam and malicious actors. Most changes will be approved within 6 hours, and we rarely reject changes for reasons beyond large violations of our Code of Conduct. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user, or you may contact an admin via the methods listed in the [[Main Page#Contacts|Contacts Section]]. == Contacts == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. Email replies will typically be slower than via Discord. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 508b2aee6e8c9628018aee6f6558c8baf25b82ad 1826 1801 2025-02-13T22:04:09Z Electron271 3 add new header, add more navpills wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == This is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Main_Page#Contacts|Contacts Section]]! == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out [[metawikimedia:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. ====== Moderation ====== All changes go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, don't worry about this as it only exists to stop spam and malicious actors. Most changes will be approved within 6 hours, and we rarely reject changes for reasons beyond large violations of our Code of Conduct. There are no formal requirements for becoming an auto-moderated user, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can join our discord at https://discord.gg/linux and request in the #wiki-chat channel to be promoted to an auto-moderated user, or you may contact an admin via the methods listed in the [[Main Page#Contacts|Contacts Section]]. == Contacts == You can contact the administrators in several ways. The best method is by joining our [https://discord.gg/linux discord] and asking in the #wiki-chat channel, or if it is of a sensitive nature, opening a ticket and asking to speak to the administrators via the <code>/ticket</code> command. Email replies will typically be slower than via Discord. '''Our Discord Server (Preferred):''' * https://discord.gg/linux ====== Email: ====== * atmois(at)allthingslinux.org * electron271(at)allthingslinux.org [[Category:Meta]] __NOTOC__ 510bbb41736daf7a5dd7be33dc13ef2e46b2877f 0 354 1802 1750 2025-02-12T22:31:37Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{MascotInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy|222px]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. [[Category:Mascots]] 60017039bd88e428894998237dfc8a5b95ecd2d7 14 544 1803 2025-02-12T22:31:37Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Needs Citations" as well as all subcategories of category "Needs Citations" if any exist. ab35d7913fc984d2f70911aa572673bcb8b651a1 1816 1803 2025-02-13T05:19:32Z Electron271 3 Update Category:Needs Citations wikitext text/x-wiki This lists pages that have the template below in them: {{Needs Citations}} 56806395035a8f7519657c3a5e679e75d3213c50 0 299 1804 1673 2025-02-12T22:32:28Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released on July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] fce91c8ed1d52bca3d20f94c2a2b41167fef371c 0 254 1805 1202 2025-02-12T22:33:23Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:Window Managers]] a8150d76beb0a0e81a0ef70f87178c4caf96c8e6 0 257 1806 1672 2025-02-12T22:33:34Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) === Installation === This section will change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Managers]] d5ee5039a2b28cc8a69e5c29e7a36f8b21530bf4 0 534 1807 1780 2025-02-12T22:33:44Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref>The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor. == Features == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config<ref>https://github.com/YaLTeR/niri?tab=readme-ov-file#features</ref> == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. <syntaxhighlight> # dnf copr enable yalter/niri # dnf install niri </syntaxhighlight> === Arch Linux === To download the latest stable release, run the following command: <syntaxhighlight> # pacman -S niri </syntaxhighlight> If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: <syntaxhighlight> $ yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix''' <syntaxhighlight lang="nix"> {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; # In case you want to override niri. }; } </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: <syntaxhighlight> # pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. <syntaxhighlight> # zypper in niri </syntaxhighlight> Alternatively, you can install it with '''opi''' as well. <syntaxhighlight> # opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''. <syntaxhighlight> # xbps-install -S niri </syntaxhighlight> === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file. While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref>https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages bellow to ensure app functionality. Do note that the list of packages below doesn't apply to all distributions. <syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref>https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session). <syntaxhighlight> $ mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight> '''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder. <syntaxhighlight> $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> '''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight> After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight> Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so. In this case, if you desire XWayland, you may add the following to your configuration. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight> You may also automatically start <code>swaybg</code> in a similar manner. <syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight> For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. <references /> 5e489593f9c49525f226393864db8595e1e0599a 0 175 1808 987 2025-02-12T22:34:09Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Pacman 401.png|thumb|[[Pacman]]]] == Intro == The [[Linux Distributions|Linux distribution]] [[Arch Linux]] and its derivatives usually use a [[Package Manager|package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] [[Category:Package Managers]] 2d8bf7781eb52b520be390a99bae6cab3f91dbee 0 235 1809 990 2025-02-12T22:34:42Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every [[Gentoo]] and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the [[Package Manager|package manager]], although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. === Configuration === Configuration of Portage is done through various configuration files and folders found in /etc/portage, which allows configuration of features such as USE flags, default options, masked packages and more. ==== make.conf ==== make.conf is the main configuration file for Portage. It allows the configuration of system-wide USE flags, Portage features, accepted licenses and more. This file is regularly edited during the Gentoo installation process and during ordinary use of it, so it's very important to get the options right for it. Below are some of the most relevant ones. ===== COMMON_FLAGS, CFLAGS, CXXFLAGS, FCFFLAGS and FFLAGS ===== These variables determine the build and compile flags that will be used for all package compilations. The CFLAGS variable is for C applications, while the CXXFLAGS one is meant for C++ ones. Most users will keep these variables identical. A "safe" configuration to avoid compilation errors should look like this:<blockquote><code>COMMON_FLAGS="-march=native -O2 -pipe"</code> <code>CFLAGS="${COMMON_FLAGS}"</code> <code>CXXFLAGS="${COMMON_FLAGS}"</code> <code>FCFLAGS="${COMMON_FLAGS}"</code> <code>FFLAGS="${COMMON_FLAGS}"</code></blockquote> ===== MAKEOPTS ===== The MAKEOPTS variable is used to specify arguments that will be passed to [[Make]] during compilation. A good rule of thumb is to set the -j argument to about half your RAM size and the -l argument to the thread count of your CPU, which can be found by running <code>nproc</code>. For example, if you have 4 GB of RAM and a 6th generation Intel Core i3, your MAKEOPTS variable should look something like this:<blockquote><code>MAKEOPTS="-j2 -l4"</code></blockquote> ===== GENTOO_MIRRORS ===== The GENTOO_MIRRORS variable tells Portage what mirror(s) to download the packages from. It can be set manually by editing the variable with a link to the mirror(s) of your liking available [https://www.gentoo.org/downloads/mirrors/ here], or automatically via <code>mirrorselect</code>, which can select the fastest mirror(s) for you. It's highly recommended to set this variable to a mirror close to you, for example, if you want to use an Italian mirror you would have to edit the variable like this:<blockquote><code>GENTOO_MIRRORS="<nowiki>https://gentoo.mirror.garr.it/</nowiki>"</code></blockquote> ===== FEATURES ===== The FEATURES variable contains a list of features that you can enable which notably alters the behavior of Portage. For example, if you want to use binary packages and verify their signatures, you would have to set the variable like this:<blockquote><code>FEATURES="getbinpkg binpkg-request-signature"</code></blockquote> ===== EMERGE_DEFAULT_OPTS ===== The EMERGE_DEFAULT_OPTS variable contains the options that will be automatically set when running Portage every time. For example, if you want Portage to ask for confirmation and verbose output, you would set the variable to this:<blockquote><code>EMERGE_DEFAULT_OPTS="--ask --verbose"</code></blockquote> ===== USE ===== The USE variable allows the '''system-wide''' enabling or disabling of USE flags. An example of this variable may look like this:<blockquote><code>USE="pulseaudio X systemd dbus policykit udisks dist-kernel -alsa -wayland xwayland"</code></blockquote> ===== USE_EXPAND ===== USE_EXPAND is a set of variables that serve to extend the capabilities of USE flags. Below are the most relevant ones. ====== VIDEO_CARDS ====== VIDEO_CARDS is a variable that serves to specify the drivers you wish to install for your GPUs. For example, if you want to install the drivers for AMD and Intel graphics, you would set the variable to this:<blockquote><code>VIDEO_CARDS="amdgpu radeonsi intel"</code></blockquote> ====== CPU_FLAGS_* ====== The CPU_FLAGS_* variables specify the available features that your CPU has to optimize compiling packages. The currently available variables are CPU_FLAGS_X86 (for x86 and x86_64 architectures), CPU_FLAGS_ARM (for ARM and ARM64 architectures) and CPU_FLAGS_PPC (for PowerPC and PowerPC64 architectures). The <code>cpuid2cpuflags</code> utility can be used to find these flags. The output of this command may look something like this:<blockquote><code>CPU_FLAGS_X86: aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3</code></blockquote>The output can then be copied to make.conf. ===== ACCEPT_LICENSE ===== The ACCEPT_LICENSE variable can be used to tell Portage which type of licenses are allowed. Generally, it's preferred to not accept proprietary software licenses. To allow every license except proprietary ones, you can set the variable to this:<blockquote><code>ACCEPT_LICENSE="* -@EULA"</code></blockquote> [[Category:Package Managers]] 0c0aaaf1138dd43490c029ef847ee98c14b46359 0 412 1810 1473 2025-02-12T22:35:08Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-org | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }} '''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. === Available Parameters === {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default (none unless specified) || [given parameter] |} === Trivia === * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ ^{<nowiki>[1]</nowiki>}] * [[Larry the Cow]] (<code>emerge --moo</code>) and Cowsay share the same ASCII art, [[Debian]]'s Larry ASCII arts don't. * There is a graphical version of this program called [https://www.doof.me.uk/xcowsay/ xcowsay]. [[Category:Software]] 8fb62654eb989677f98834e5e45c61e20336b4b6 0 355 1811 1367 2025-02-12T22:35:16Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} The '''GNU C Library''', commonly known as '''glibc''', is the GNU Project implementation of the C standard library. It provides a wrapper around the system calls of the Linux kernel and other kernels for application use. Despite its name, it now also directly supports C++ (and, indirectly, other programming languages). It was started in the 1980s by the Free Software Foundation (FSF) for the GNU operating system. [[Category:Software]] 6b6e204c6394103624ded328dd52ec975221e659 0 263 1812 1198 2025-02-12T22:35:24Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your operating system, software and hardware with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch</ref> === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|left|thumb|The Hyfetch Pride Month easter egg.]]If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. <references /> [[Category:Software]] f3bdd96dce12645ab26f48ccb2e91e3be8f2113f 1820 1812 2025-02-13T06:04:12Z Electron271 3 Fix image wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.4.11, 2024-1-02 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|thumb|The Hyfetch Pride Month easter egg.]] Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your operating system, software and hardware with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch</ref> === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. <references /> [[Category:Software]] d91c00f44e4baceda7f13108041b4f053426924e 0 322 1813 1556 2025-02-12T22:35:32Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the Linux kernel, released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on Operating Systems === Linux distributions which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * Sabotage * Morpheus Linux * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against [[glibc]]. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] [[Category:Software]] 3845ba2462f820453b6969b660da9481952f469b 0 309 1814 1201 2025-02-12T22:35:43Z Electron271 3 wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Sudo.png|thumb]] | caption = Sudo used on [[pacman]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.15p5, 2023-12-30 | languages = [[c]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]). Its name is shorthand for "substitute user and do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file to specify which users or groups can execute specific commands. == Usage == The following are several common usecases for sudo. ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser'' {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} [[Category:Software]] 826e73f577773775ff1061b8c97e2c9fb2fbf7b9 1817 1814 2025-02-13T05:48:42Z Electron271 3 Add citations, Add trivia section, Fix inaccuracy wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png|thumb]] | caption = Sudo used on [[pacman]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.15p5, 2023-12-30 | languages = [[c]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} [[File:Sudo logo.png|thumb|335x335px|Sudo's logo of a sandwich]] The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]).<ref name=":0">[https://man7.org/linux/man-pages/man8/sudo.8.html sudo(8)], Linux Manpages</ref> Its name is shorthand for "su 'do'"<ref>[https://www.sudo.ws/ sudo.ws], Sudo Developers</ref>, however as <code>su</code> stands for "substitute user"<ref>[https://man7.org/linux/man-pages/man1/su.1.html su(1)], Linux Manpages</ref> this would stand for "substitute user, do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file<ref name=":0" /> to specify which users or groups can execute specific commands. == Usage == {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |Run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser''<ref name=":0" /> == Trivia == * Sudo's logo is a sandwich in reference to [https://xkcd.com/149/ xkcd 149]<ref>[https://www.sudo.ws/about/logo/ sudo.ws/about/logo], Sudo Developers</ref> * If you add the line <code>Default insults</code> to the Defaults section of <code>/etc/sudoers</code>, you will be insulted whenever you type the wrong password.<ref>[https://www.geeksforgeeks.org/when-sudo-insults-you/ When sudo insults you!!], GeeksforGeeks, September 13, 2023 (February 12, 2025)</ref> [[Category:Software]] 69b1a38c017a0bb623ecae931e29b6f1654d820c 1819 1817 2025-02-13T05:57:29Z Electron271 3 Update version in infobox and add screenshot for sudo insults wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png|thumb]] | caption = Sudo used on [[pacman]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.16p2, 2024-11-25 | languages = [[C]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} [[File:Sudo logo.png|thumb|335x335px|Sudo's logo of a sandwich]] [[File:Sudo Insults.png|thumb|335x335px|Output from sudo when <code>Defaults insults</code> is added]] The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]).<ref name=":0">[https://man7.org/linux/man-pages/man8/sudo.8.html sudo(8)], Linux Manpages</ref> Its name is shorthand for "su 'do'"<ref>[https://www.sudo.ws/ sudo.ws], Sudo Developers</ref>, however as <code>su</code> stands for "substitute user"<ref>[https://man7.org/linux/man-pages/man1/su.1.html su(1)], Linux Manpages</ref> this would stand for "substitute user, do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file<ref name=":0" /> to specify which users or groups can execute specific commands. == Usage == {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |Run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser''<ref name=":0" /> == Trivia == * Sudo's logo is a sandwich in reference to [https://xkcd.com/149/ xkcd 149]<ref>[https://www.sudo.ws/about/logo/ sudo.ws/about/logo], Sudo Developers</ref> * If you add the line <code>Defaults insults</code> to the Defaults section of <code>/etc/sudoers</code>, you will be insulted whenever you type the wrong password.<ref>[https://www.geeksforgeeks.org/when-sudo-insults-you/ When sudo insults you!!], GeeksforGeeks, September 13, 2023 (February 12, 2025)</ref> [[Category:Software]] 53f4a01d1d40c4424b8355795142d83d68bc6bfb 4 327 1815 1658 2025-02-13T01:13:52Z Electron271 3 wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen electron was here idk potato testing testing 1 2 3 4<ref>hi</ref> {{MascotInfobox | title = Test | image = [[File:Larry the cow.png|Larry the Cow]] | caption = Test }} 2ff03f9d5f64a2f1237620e667b1c7a5a64694d8 6 545 1818 2025-02-13T05:56:55Z Electron271 3 Output from sudo when <code>Defaults insults</code> is added wikitext text/x-wiki == Summary == Output from sudo when <code>Defaults insults</code> is added c4abafe2a81352f6db71a3cc38d4dd8fc745212a 10 546 1821 2025-02-13T21:44:19Z Electron271 3 Created page with ".home-header { position: relative; padding-top: var( --space-xxl ); padding-bottom: var( --space-xxl ); line-height: var( --line-height-xx-small ); text-align: center; } .home-header__pretitle { margin-bottom: var( --space-xxs ); color: var( --color-subtle ); font-size: var( --font-size-small ); letter-spacing: 0.05em; } .home-header__title { margin: 0; font-size: 3rem; text-transform: uppercase; letter-spacing: 0.025em; line-height: 1; } .home-header..." sanitized-css text/css .home-header { position: relative; padding-top: var( --space-xxl ); padding-bottom: var( --space-xxl ); line-height: var( --line-height-xx-small ); text-align: center; } .home-header__pretitle { margin-bottom: var( --space-xxs ); color: var( --color-subtle ); font-size: var( --font-size-small ); letter-spacing: 0.05em; } .home-header__title { margin: 0; font-size: 3rem; text-transform: uppercase; letter-spacing: 0.025em; line-height: 1; } .home-header__subtitle { margin-top: var( --space-xxs ); font-size: var( --font-size-small ); } .home-header__search { padding: var( --space-md ); margin-top: var( --space-lg ); margin-bottom: var( --space-md ); margin-left: auto; margin-right: auto; max-width: 600px; background-color: var( --color-surface-2 ); border-radius: var( --border-radius-pill ); cursor: pointer; font-size: var( --font-size-small ); font-weight: var( --font-weight-medium ); text-align: center; } .home-header__search .desktoponly { margin-left: var( --space-xs ); } .home-header__search:hover { background-color: var( --background-color-button-quiet--hover ); } .home-header__searchIcon img { margin-right: var( --space-md ); opacity: var( --opacity-icon-base ); } /* Fix vertical alignment problem */ .home-header__search .keyboard-key { display: inline; padding-top: 0.1em; padding-bottom: 0.1em; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert( 1 ); } @media ( hover: none ) { .home-header__search .desktoponly { display: none; } } e99cc265f909634327a1ff4bfedbf6f333b8805f 1822 1821 2025-02-13T21:46:36Z Electron271 3 sanitized-css text/css .home-header { position: relative; padding-top: var( --space-xxl ); padding-bottom: var( --space-xxl ); line-height: var( --line-height-xx-small ); text-align: center; } .home-header__pretitle { margin-bottom: var( --space-xxs ); color: var( --color-subtle ); font-size: var( --font-size-small ); letter-spacing: 0.05em; } .home-header__title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } .home-header__subtitle { margin-top: var( --space-xxs ); font-size: var( --font-size-small ); } .home-header__search { padding: var( --space-md ); margin-top: var( --space-lg ); margin-bottom: var( --space-md ); margin-left: auto; margin-right: auto; max-width: 600px; background-color: var( --color-surface-2 ); border-radius: var( --border-radius-pill ); cursor: pointer; font-size: var( --font-size-small ); font-weight: var( --font-weight-medium ); text-align: center; } .home-header__search .desktoponly { margin-left: var( --space-xs ); } .home-header__search:hover { background-color: var( --background-color-button-quiet--hover ); } .home-header__searchIcon img { margin-right: var( --space-md ); opacity: var( --opacity-icon-base ); } /* Fix vertical alignment problem */ .home-header__search .keyboard-key { display: inline; padding-top: 0.1em; padding-bottom: 0.1em; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert( 1 ); } @media ( hover: none ) { .home-header__search .desktoponly { display: none; } } b2d12c92c6044d654d99afa7e9ac620ae8715713 10 548 1824 2025-02-13T21:51:48Z Electron271 3 Created page with "Modified from the starcitizen.tools wiki" wikitext text/x-wiki Modified from the starcitizen.tools wiki c92aa6a40f689e09902df2134234e8a148af8351 0 549 1827 2025-02-13T22:09:29Z Electron271 3 Redirected page to [[Category:Pages Needing Cleanup]] wikitext text/x-wiki #REDIRECT [[Category:Pages Needing Cleanup]] a96394bb6f07f8dbf56d29334bdf8d97f334c33d 14 550 1828 2025-02-13T22:10:27Z Electron271 3 Created page with "Category page for pages with the following template: {{Cleanup|Example}}" wikitext text/x-wiki Category page for pages with the following template: {{Cleanup|Example}} b2a02aac0f8cfb0afab569eb1a80a8687347c035 0 551 1829 2025-02-13T22:10:49Z Electron271 3 Redirected page to [[Category:Needs Citations]] wikitext text/x-wiki #REDIRECT [[Category:Needs Citations]] e025033023227465fbd17bb215e62117e1f68b98 0 272 1832 1185 2025-02-13T22:27:03Z Electron271 3 wikitext text/x-wiki {{Cleanup|Needs infobox}}{{Needs Citations}} == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. [[File:DNF Command Line Interface.png|thumb|left]] == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: - Installing Packages: `dnf install <package_name>` - Updating Packages `dnf update` - Removing Packages `dnf remove <package_name>` - Listing Installed Packages: `dnf list installed` - Searching for Packages: `dnf search <keyword>` - Managing Repositories `dnf repolist`, `dnf config-manager` - Viewing Transaction History: `dnf history` == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. [[Category:Package Managers]] 7605be281c1866cd41ed06fe35fae44b7c49969d 10 483 1833 1773 2025-02-13T22:36:10Z Electron271 3 wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified.}} (hover for more info)</span> <div class="mbox-text">It might not meet the wiki's [[Contributing#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> 2aabc6516e6a2efc9dd3d4df2ff33d3e17570e9e 10 513 1834 1761 2025-02-13T22:36:49Z Electron271 3 wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations. (hover for more info)</span> <div class="mbox-text">This article was most likely made before strict rules for citations were implemented [[Contributing#Citations|(Read here)]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that still need to be edited.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Needs Citations]]</includeonly><noinclude> {{/doc}}</noinclude> 5b4e7b3943f03257ad2154d4f3bd8c87540b48fe 10 523 1835 1717 2025-02-13T22:37:01Z Electron271 3 wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes. (hover for more info)</span> <div class="mbox-text">This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> a1d18dc50a5551aae7bc029e974d680f65c9cbc5 10 482 1836 1708 2025-02-13T22:37:18Z Electron271 3 wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands which could potentially damage your system. Please ensure you understand the commands you are running before you run them. If you see a dangerous command please report it to an administrator. (hover for more info)</span> <div class="mbox-text">This warning is placed on any page that lists a command, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be reported to an [[Main Page#Contacts|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> e4ca14fd6c7a8832e408562c9d32cadc2182fa7e 10 187 1837 387 2025-02-13T22:37:44Z Electron271 3 wikitext text/x-wiki ^{[citation needed]}<includeonly>[[Category:Needs Citations]]</includeonly> 333485d7d1179bbf7741bc94aa65e67d6644e8b3 2 553 1839 2025-02-13T23:22:07Z Electron271 3 Created page with "{{UserboxWarn|This user probably exists}} Wiki Administrator and team member of [https://allthingslinux.com allthingslinux.com] Contact at electron271(at)allthingslinux.org" wikitext text/x-wiki {{UserboxWarn|This user probably exists}} Wiki Administrator and team member of [https://allthingslinux.com allthingslinux.com] Contact at electron271(at)allthingslinux.org 64a95055d433a7a75cd5f91703351818a418b0eb 0 233 1840 1077 2025-02-13T23:40:38Z Katz 53 Added rolling release in specific mention to Slackware -Current wikitext text/x-wiki {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. [[Category:Linux Distributions]] daacebbf0965ab0eb75143ac0803a00507907271 0 310 1841 1110 2025-02-14T14:17:21Z Katz 53 Added info box, will have to add and change details later though I think it's mostly correct? wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Alpine Linux | image = | caption = | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[apk]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[Mate]], [[LXQt]] | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, ppc64le, s390x, loongarch64 | website = [https://www.alpinelinux.org/ alpinelinux.org] }} Alpine Linux, according to their main site, is a general purpose Linux distribution that aims to be "small," "simple," and "secure." It achieves this by using only the most basic and necessary binaries as well as tools to get started, compiled as Position Independent Executables (PIEs) in order to ensure the installed system is centered around one or a few simple tasks without any unnecessary components. Instead of systemd, it uses OpenRC, and instead of glibc, it uses musl libc in pursuit of greater efficiency. Alpine Linux is most commonly used in embedded systems and servers due to its ease of deployment and manageability. Its main package manager is 'apk', short for 'Alpine Package Keeper' (not to be confused with Android APKs.) Alpine's repositories are very small compared to most user-oriented distributions nowadays, hence it isn't used much on desktop machines. Alpine does not come with a graphical environment, editor or even a tool to execute as superuser out of the box, however it provides a number of scripts for setting up numerous things, among which are: 1) setup-desktop: Friendly TUI script to quickly set up a desktop environment and necessary tools to start working. 2) setup-xorg-base: Invokes 'apt' to download a number of Xorg-related packages. Note that it doesn't allow you to start working with Xorg right away, you still need to fetch other important packages and setup other things. 693cd04c8bfde6ee4093b4e692d505a68de8feb7 6 554 1843 2025-02-14T15:36:59Z Katz 53 alpine linux logo omgg wikitext text/x-wiki == Summary == alpine linux logo omgg ffc44080ab540b5e59bc3663126f3b8df4103eef 0 310 1844 1841 2025-02-14T15:37:32Z Katz 53 Added logo to info box wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Alpine Linux | image = [[File:alpinelinux-logo.svg|thumb]] | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[apk]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[Mate]], [[LXQt]] | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, ppc64le, s390x, loongarch64 | website = [https://www.alpinelinux.org/ alpinelinux.org] }} Alpine Linux, according to their main site, is a general purpose Linux distribution that aims to be "small," "simple," and "secure." It achieves this by using only the most basic and necessary binaries as well as tools to get started, compiled as Position Independent Executables (PIEs) in order to ensure the installed system is centered around one or a few simple tasks without any unnecessary components. Instead of systemd, it uses OpenRC, and instead of glibc, it uses musl libc in pursuit of greater efficiency. Alpine Linux is most commonly used in embedded systems and servers due to its ease of deployment and manageability. Its main package manager is 'apk', short for 'Alpine Package Keeper' (not to be confused with Android APKs.) Alpine's repositories are very small compared to most user-oriented distributions nowadays, hence it isn't used much on desktop machines. Alpine does not come with a graphical environment, editor or even a tool to execute as superuser out of the box, however it provides a number of scripts for setting up numerous things, among which are: 1) setup-desktop: Friendly TUI script to quickly set up a desktop environment and necessary tools to start working. 2) setup-xorg-base: Invokes 'apt' to download a number of Xorg-related packages. Note that it doesn't allow you to start working with Xorg right away, you still need to fetch other important packages and setup other things. 23cfcec3f544da06da37d21aaf372db17461da1a 6 555 1845 2025-02-15T05:33:10Z Rayk4z1 62 The Rust Logo wikitext text/x-wiki == Summary == The Rust Logo fd3d758fb8182b0885fb392032561335777dd309 4 327 1846 1815 2025-02-15T10:59:03Z Test 63 test wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen electron was here test n 1203 idk potato testing testing 1 2 3 4<ref>hi</ref> {{MascotInfobox | title = Test | image = [[File:Larry the cow.png|Larry the Cow]] | caption = Test }} 17ed222cc0596f8f1318f98c04e82618ea317889 1888 1846 2025-03-12T17:17:10Z Atmois 13 more testing wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen electron was here more testing???? test n 1203 idk potato testing testing 1 2 3 4<ref>hi</ref> {{MascotInfobox | title = Test | image = [[File:Larry the cow.png|Larry the Cow]] | caption = Test }} 46cc22b2079f47b6091d2d01f05536c53f261a35 4 556 1847 2025-02-15T18:00:08Z Atmois 13 Add about wikitext text/x-wiki This is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server or check the [[Main_Page#Contacts|Contacts Section]]! 29cf0f0411aa077a0d16c917d776304c62eec29a 1854 1847 2025-02-16T17:36:24Z Atmois 13 Add info wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out #wiki-chat on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator. == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Staff == To email all sysadmins at once please email: ''wiki(at)allthingslinux.org'' * [[User:Atmois|Atmois]] - Lead Sysadmin ** ''atmois(at)allthingslinux.org'' * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner ** ''kaizen(at)allthingslinux.org'' * [[User:Electron271|Electron271]] - Sysadmin ** ''electron271(at)allthingslinux.org'' * [[User:Scottc96|Scott96]] - Sysadmin ** ''scott(at)allthingslinux.org'' 6ea761681780186422e7cbecab30742b53221022 0 436 1848 1499 2025-02-15T18:17:11Z Ktmfn 104 wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb|logo of Adelie Linux]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is a [[Linux Distributions|Linux distribution]], based on Alpine Linux. The distribution targets old and low end machines, like desktops and servers. === Base description === One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution uses the OpenRC init system for service management, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. 46d5b5d91a877e5d3af82acb2c469db406a5fabc 2 325 1849 1276 2025-02-15T19:26:18Z Katz 53 wikitext text/x-wiki yolooooooooooooooooooooooooooooo ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⡠⡐⢦⣝⡲⣴⠢⣾⢥⡢⠄⠤⠀⠀⠀⠀⠀⠀⠀⠀⠠⠄⢠⣴⡦⢻⠴⣮⣧⣢⡀⠀⠀⠀ ⠀⠀⠀⠀⠠⢊⢐⣍⢎⠅⠂⠈⠉⠁⠀⠀⠉⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠀⠀⠈⠒⠁⡽⣸⣿⠜⡄⠀⠀ ⠀⠀⠀⢠⠁⡊⣜⢿⠀⠀⠀⠀⠀⠀⡠⠐⢈⣩⢫⡵⡦⣀⣴⣶⢴⣦⡄⡀⠀⠀⠀⠀⠀⢱⢓⣿⠷⢄⠀⠀ ⠀⠀⠀⠈⡐⠗⡷⡇⠀⠀⠀⠀⢀⣢⢜⣷⣿⣿⣿⣿⡿⡿⣝⣟⡿⣻⣿⣿⡢⡀⠀⠀⠀⢨⢚⣺⢿⡹⠀⠀ ⠀⠀⠀⠀⢲⢝⣫⡤⡀⠀⢀⣴⡻⡼⠿⠛⠉⠉⡉⠋⠉⠰⢵⡬⡟⠉⡚⠛⠷⣶⡄⣀⣀⣨⣽⣿⡃⡂⠀⠀ ⠀⠀⠀⠘⢕⠱⣾⡻⣾⣽⣾⠟⠁⠀⠀⢠⡊⠟⢁⠀⢀⠀⡄⠚⠁⡞⠈⡆⠀⠈⢾⣛⣿⡻⣫⠎⡚⠀⠀⠀ ⠀⠀⠀⠀⠈⠋⠮⣽⢑⡳⡜⠀⠀⠀⠀⠁⠃⠀⣶⢲⡶⠀⠀⠀⠀⢶⣲⠇⠀⠀⠈⢞⣻⠌⠌⠉⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠈⠒⠨⢥⠁⠀⠀⠀⠀⢐⠀⠀⠈⠁⠀⠈⠀⠀⠀⠀⠫⠣⡀⠀⠀⠈⢆⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠆⠁⠂⠀⠀⠀⠀⠠⡐⠀⢄⠀⠀⠹⣀⢁⠒⠐⠂⠃⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠠⢊⢠⠔⠔⠊⢡⠀⠀⠀⠀⠀⠀⠀⠛⠀⠶⣀⠈⠐⠀⠀⠀⡆⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠈⠀⠀⠨⠀⠀⠈⡄⠀⠀⠀⠀⠈⢄⠀⠀⠀⠁⠀⠀⣠⠴⠊⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡀⠀⠀⠈⠂⢀⠀⠀⠀⠀⠢⡀⠀⣀⢀⣀⣀⡈⠄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠡⠀⠀⠀⠸⠁⡀⠀⠀⠀⡀⠀⢁⡁⣀⠀⠀⠆⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠡⡀⠀⠀⠀⠜⠄⡄⠀⠀⠐⠋⡛⢙⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⡀⠆⠀⠈⠑⡁⠣⡀⠀⢀⢄⠃⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠀⠘⣅⢨⡐⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠐⠊⠨⠡⠠⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ba0676fe22e15f7a88c9a205e3fba138fb5e2f61 1889 1849 2025-03-15T23:34:37Z Katz 53 Replaced content with "subscribe to my patreon" wikitext text/x-wiki subscribe to my patreon da4ba1c444753c0d1eb92778fea170bc47cd52d0 6 557 1850 2025-02-16T02:43:59Z Rayk4z1 62 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 558 1851 2025-02-16T02:49:15Z Rayk4z1 62 Rust page: Basic Info, Syntax, OOP, Memory safety, 17 Citations + shared wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[C]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }}Rust, the programming language, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called "garbage collecting," where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety|# Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[Rust#Object-Orientated Programming in Rust|# Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December of 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├─src ; Contain all code for project | ├──main.rs ; Code is executed here ├─Cargo.toml ; Dependencies file ├─git.ignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!") } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { let var_name: i32 = 64; let mut another_var: i32 = 86; another_var = 128; // let declares a new variable, i32 is the type of the variable // but is not requred, then the value is given. // All variables end with a ";" } </syntaxhighlight>Using <code>let</code> defines a new variable. You are able to label the variable however you like; but, it is a good idea to give them simple and easy names for sake of other programmers and yourself. If you need to specify the type of value a variable is, you can write out <code>[var_name]: [type]</code> to declare a type, to see all types, see [[Rust#Variable Types|# Variable Types]]. By default, any variable defined is an '''immutable''' but using the <code>mut</code> term enables the variable to mutable, influenced by '''functional programming'''. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" line="1"> struct Values { Value1: bool, Value2: i32, Value3: String, // Value 4..., Value 5... } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: Values = Values { Value1: true, Value2: 64, Value3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { Length: i32, Width: i32, Height: i32 } // vvvvvv Cube implemented here vvvvvv impl Cube { fn Area(&self) -> i32 { self.Length * self.Width * self.Height // This returns the Cube's Volume } } fn main() { let RubiksCube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's Volume: {}", RubiksCube.Area()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an Area finder function within the <code>impl Cube</code> scope. We are able to use the <code>Area()</code> function on any Variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has an unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses "borrowing"; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing], Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> [[Category:Programming Languages]] 51b6b8ebec8911106f1f26f2b5ed4b54437be5d0 6 559 1852 2025-02-16T08:01:47Z 2elevation 115 wikitext text/x-wiki Plasma 6.3 3250a296f59e55fd75537350b0d8cf60d3ba58a7 0 480 1853 1584 2025-02-16T08:07:30Z 2elevation 115 Fixed some no longer valid statements including the independent base, which was cancelled along with additions about the newest Oreon 10 feature update build. wikitext text/x-wiki {{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}} [[File:Oreon10-2502.png|thumb|Oreon 10 Core (Build 2502) running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>https://oreonproject.org/</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>https://git.oreonproject.org/rpms</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>https://boostyconnect.com/oreon-lime-r1-lifecycle/</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>https://oreonproject.org/oreon-lime-r2-support-timeline/</ref><ref>https://oreonproject.org/oreon-lime-r2/</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/</ref> and other well-known sources. In October 2024, Oreon celebrated it's 1st anniversary on November 16, 2024 and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69</ref> Oreon 10 released to the public on December 12, 2024 shipping with KDE Plasma 6 and Linux 6.11<ref>https://forums.oreonproject.org/t/oreon-10-officially-released/98</ref> but was upgraded to 6.12 a few days later. A new update to Oreon 10 has been released on February 12, 2025 under the name "Build 2502." This update brought a few bug fixes along with some planned features for later such as Apple M-series Mac support.<ref>https://forums.oreonproject.org/t/oreon-10-build-2502-has-officially-released/150</ref> <references /> [[Category:Linux Distributions]] 2913df9f91c7e6b79fb04a292abecbaeedd6182b 0 1 1855 1826 2025-02-16T17:46:41Z Atmois 13 Update info wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out #wiki-chat on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:About#Staff|about#staff]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out [[metawikimedia:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact an administrator via the methods listed on [[Main_Page#About|about#staff]]. __NOTOC__ 56f203f969868f20b242697915fce6b98d6f6ccc 1885 1855 2025-03-04T21:15:04Z Atmois 13 Update link wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out #wiki-chat on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:About#Staff|about#staff]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [https://www.mediawiki.org/wiki/Help:Contents|Mediawiki's Editing Guide] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact an administrator via the methods listed on [[Main_Page#About|about#staff]]. __NOTOC__ 9512f3c7edf25f4863f13b8055e140f1fdd3fa4b 4 560 1856 2025-02-16T17:52:16Z Atmois 13 Add copyright page wikitext text/x-wiki All content unless specified otherwise is available under [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en Creative Commons Attribution-ShareAlike 4.0 International]. <syntaxhighlight> Attribution-ShareAlike 4.0 International ======================================================================= Creative Commons Corporation ("Creative Commons") is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an "as-is" basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible. Using Creative Commons Public Licenses Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses. Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC- licensed material, or material used under an exception or limitation to copyright. More considerations for licensors: wiki.creativecommons.org/Considerations_for_licensors Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor's permission is not necessary for any reason--for example, because of any applicable exception or limitation to copyright--then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public: wiki.creativecommons.org/Considerations_for_licensees ======================================================================= Creative Commons Attribution-ShareAlike 4.0 International Public License By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions. Section 1 -- Definitions. a. Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image. b. Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License. c. BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by Creative Commons as essentially the equivalent of this Public License. d. Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights. e. Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements. f. Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material. g. License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike. h. Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License. i. Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license. j. Licensor means the individual(s) or entity(ies) granting rights under this Public License. k. Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them. l. Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world. m. You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning. Section 2 -- Scope. a. License grant. 1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to: a. reproduce and Share the Licensed Material, in whole or in part; and b. produce, reproduce, and Share Adapted Material. 2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions. 3. Term. The term of this Public License is specified in Section 6(a). 4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a) (4) never produces Adapted Material. 5. Downstream recipients. a. Offer from the Licensor -- Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License. b. Additional offer from the Licensor -- Adapted Material. Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter's License You apply. c. No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material. 6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i). b. Other rights. 1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise. 2. Patent and trademark rights are not licensed under this Public License. 3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties. Section 3 -- License Conditions. Your exercise of the Licensed Rights is expressly made subject to the following conditions. a. Attribution. 1. If You Share the Licensed Material (including in modified form), You must: a. retain the following if it is supplied by the Licensor with the Licensed Material: i. identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated); ii. a copyright notice; iii. a notice that refers to this Public License; iv. a notice that refers to the disclaimer of warranties; v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable; b. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and c. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License. 2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information. 3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable. b. ShareAlike. In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply. 1. The Adapter's License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License. 2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material. 3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply. Section 4 -- Sui Generis Database Rights. Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material: a. for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database; b. if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and c. You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database. For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights. Section 5 -- Disclaimer of Warranties and Limitation of Liability. a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability. Section 6 -- Term and Termination. a. This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically. b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates: 1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or 2. upon express reinstatement by the Licensor. For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License. c. For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License. d. Sections 1, 5, 6, 7, and 8 survive termination of this Public License. Section 7 -- Other Terms and Conditions. a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed. b. Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License. Section 8 -- Interpretation. a. For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License. b. To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions. c. No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor. d. Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority. ======================================================================= Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” The text of the Creative Commons public licenses is dedicated to the public domain under the CC0 Public Domain Dedication. Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark "Creative Commons" or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses. Creative Commons may be contacted at creativecommons.org. </syntaxhighlight> 98ba0bec402e0c2e9e1e00259ae732a1b64f0664 0 534 1857 1807 2025-02-18T06:16:53Z Glocean 124 Reverted edit by [[Special:Contributions/Electron271|Electron271]] ([[User talk:Electron271|talk]]) to last revision by [[User:Amadaluzia|Amadaluzia]] wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref>The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor. == Features == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config<ref>https://github.com/YaLTeR/niri?tab=readme-ov-file#features</ref> == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. <syntaxhighlight> # dnf copr enable yalter/niri # dnf install niri </syntaxhighlight> === Arch Linux === To download the latest stable release, run the following command: <syntaxhighlight> # pacman -S niri </syntaxhighlight> If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: <syntaxhighlight> $ yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix''' <syntaxhighlight lang="nix"> {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; # In case you want to override niri. }; } </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: <syntaxhighlight> # pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. <syntaxhighlight> # zypper in niri </syntaxhighlight> Alternatively, you can install it with '''opi''' as well. <syntaxhighlight> # opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''. <syntaxhighlight> # xbps-install -S niri </syntaxhighlight> === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file. While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref>https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages bellow to ensure app functionality. Do note that the list of packages below doesn't apply to all distributions. <syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref>https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session). <syntaxhighlight> $ mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight> '''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder. <syntaxhighlight> $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> '''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight> After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight> Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so. In this case, if you desire XWayland, you may add the following to your configuration. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight> You may also automatically start <code>swaybg</code> in a similar manner. <syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight> For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. <references /> c8fc9a126c4e31b2ade6c29b7a63c3581f56205c 1858 1857 2025-02-18T08:12:58Z Glocean 124 test wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a silly scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref>The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor. == Features == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config<ref>https://github.com/YaLTeR/niri?tab=readme-ov-file#features</ref> == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. <syntaxhighlight> # dnf copr enable yalter/niri # dnf install niri </syntaxhighlight> === Arch Linux === To download the latest stable release, run the following command: <syntaxhighlight> # pacman -S niri </syntaxhighlight> If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: <syntaxhighlight> $ yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix''' <syntaxhighlight lang="nix"> {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; # In case you want to override niri. }; } </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: <syntaxhighlight> # pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. <syntaxhighlight> # zypper in niri </syntaxhighlight> Alternatively, you can install it with '''opi''' as well. <syntaxhighlight> # opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''. <syntaxhighlight> # xbps-install -S niri </syntaxhighlight> === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file. While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref>https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages bellow to ensure app functionality. Do note that the list of packages below doesn't apply to all distributions. <syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref>https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session). <syntaxhighlight> $ mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight> '''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder. <syntaxhighlight> $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> '''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight> After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight> Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so. In this case, if you desire XWayland, you may add the following to your configuration. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight> You may also automatically start <code>swaybg</code> in a similar manner. <syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight> For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. <references /> c4bc696010c40a8b1ee0ec8ee741abd8acf34d30 1859 1858 2025-02-18T08:25:10Z Glocean 124 Added citations wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1" /> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. <syntaxhighlight> # dnf copr enable yalter/niri # dnf install niri </syntaxhighlight> === Arch Linux === To download the latest stable release, run the following command: <syntaxhighlight> # pacman -S niri </syntaxhighlight> If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: <syntaxhighlight> $ yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix''' <syntaxhighlight lang="nix"> {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; # In case you want to override niri. }; } </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: <syntaxhighlight> # pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. <syntaxhighlight> # zypper in niri </syntaxhighlight> Alternatively, you can install it with '''opi''' as well. <syntaxhighlight> # opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''. <syntaxhighlight> # xbps-install -S niri </syntaxhighlight> === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file.<ref name=":1" /> While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref name=":1">https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages bellow to ensure app functionality<ref name=":1" />. Do note that the list of packages below doesn't apply to all distributions. <syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref name=":2">https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session). <syntaxhighlight> $ mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight> '''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder.<ref name=":2" /> <syntaxhighlight> $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> '''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder.<ref name=":2" /> <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight> After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight> Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so<ref>https://github.com/YaLTeR/niri/wiki/Configuration:-Miscellaneous</ref>. In this case, if you desire XWayland, you may add the following to your configuration. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight> You may also automatically start <code>swaybg</code> in a similar manner. <syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight> For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. <references /> 40c100b7296286584a48626503ecba9823ef2386 1860 1859 2025-02-18T18:06:18Z Katz 53 fixed a typo, one singular typo, a SINGULAR typo wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1" /> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. <syntaxhighlight> # dnf copr enable yalter/niri # dnf install niri </syntaxhighlight> === Arch Linux === To download the latest stable release, run the following command: <syntaxhighlight> # pacman -S niri </syntaxhighlight> If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: <syntaxhighlight> $ yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix''' <syntaxhighlight lang="nix"> {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; # In case you want to override niri. }; } </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: <syntaxhighlight> # pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. <syntaxhighlight> # zypper in niri </syntaxhighlight> Alternatively, you can install it with '''opi''' as well. <syntaxhighlight> # opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''. <syntaxhighlight> # xbps-install -S niri </syntaxhighlight> === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file.<ref name=":1" /> While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref name=":1">https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages below to ensure app functionality<ref name=":1" />. Do note that the list of packages below doesn't apply to all distributions. <syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref name=":2">https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session). <syntaxhighlight> $ mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight> '''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder.<ref name=":2" /> <syntaxhighlight> $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> '''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder.<ref name=":2" /> <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight> After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight> Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so<ref>https://github.com/YaLTeR/niri/wiki/Configuration:-Miscellaneous</ref>. In this case, if you desire XWayland, you may add the following to your configuration. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight> You may also automatically start <code>swaybg</code> in a similar manner. <syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight> For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. <references /> 2d8efd7276b131fe9377ad94655ef7ae0e9d2a59 6 561 1861 2025-02-19T02:50:48Z Katz 53 Running on Debian 13 (Trixie) wikitext text/x-wiki == Summary == Running on Debian 13 (Trixie) f2f92446a180421d7b8fc6f326f874dc25addc2b 0 341 1862 1239 2025-02-19T02:51:19Z Katz 53 added screenshot of TDE wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tde-logo.png]] | caption = Trinity Desktop Environment logo | title = Trinity Desktop Environment | releasestatus = Maintained | lastrelease = R14.1.3, 2024-10-27 | languages = C | developers = Trinity Development Team | website = [https://www.trinitydesktop.org/ trinitydesktop.org] }} [[File:Trinity R.14.1.3 screenshot.png|thumb|Screenshot of Trinity Desktop R14.1.3]] Trinity Desktop Environment is an X11 desktop environment forked from KDE 3 in 2010. [[Category:Desktop Environments]] 1d8d4e8cb007c900b39e13ef12469b7e37ac3cf6 0 562 1863 2025-02-19T18:01:50Z Katz 53 Created page with "OpenIndiana is a Unix [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel. Announced September 14, 2010 at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]]." wikitext text/x-wiki OpenIndiana is a Unix [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel. Announced September 14, 2010 at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]]. abed2ec3b714f9ca5e481e33407ab5b7bf060dc4 1864 1863 2025-02-19T18:14:40Z Katz 53 Added infobox and sources wikitext text/x-wiki {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel. Announced September 14, 2010 at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>https://web.archive.org/web/20100913030810/https://www.openindiana.org/</ref> 04ff1c707b630965abb61f404d8ff678fde59e02 1865 1864 2025-02-19T18:22:28Z Katz 53 categpory wikitext text/x-wiki {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel. Announced September 14, 2010 at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>https://web.archive.org/web/20100913030810/https://www.openindiana.org/</ref> [[Category:Misc Operating Systems]] [[Category:Illumos]] 0056c7cedc2c6c0b4700f3f76aa56b77db3f45f4 1867 1865 2025-02-20T18:31:16Z Katz 53 wikitext text/x-wiki {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel. Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>https://web.archive.org/web/20100913030810/https://www.openindiana.org/</ref> It was proved timely as Oracle shut down development of OpenSolaris. [[Category:Misc Operating Systems]] [[Category:Illumos]] 8493b365d20b49e3a54fab406dd32f02fdec0928 14 563 1866 2025-02-19T18:22:28Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Illumos" as well as all subcategories of category "Illumos" if any exist. bd3406f32ca137e660261154177b45b55056cd88 6 9 1868 24 2025-03-01T14:52:10Z Atmois 13 Atmois moved page [[File:Atlwikilogo.png]] to [[File:Logo.png]] without leaving a redirect: rename wikitext text/x-wiki == Summary == logo 556d0d26de95834fcb4079a22fddb56281d62907 1869 1868 2025-03-01T14:52:38Z Atmois 13 Protected "[[File:Logo.png]]": High traffic page: Logo ([Edit=Allow only administrators] (indefinite)) wikitext text/x-wiki == Summary == logo 556d0d26de95834fcb4079a22fddb56281d62907 6 564 1870 2025-03-01T14:53:45Z Atmois 13 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 1871 1870 2025-03-01T15:01:06Z Atmois 13 Protected "[[File:Logo.svg]]": High traffic page: Logo ([Edit=Allow only administrators] (indefinite)) wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 8 357 1872 1405 2025-03-01T15:13:19Z Atmois 13 temp disable css text/css /* All CSS here will be loaded for users of the Citizen skin */ /* :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } */ 607fa953f832ceb2604787a48beb9fcaecfdc4f0 1873 1872 2025-03-01T15:13:59Z Atmois 13 disable actually css text/css da39a3ee5e6b4b0d3255bfef95601890afd80709 1874 1873 2025-03-01T15:15:51Z Atmois 13 Undo change css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } 83a9ceb9df7515cf02c3dff4044bf5a19b2b8ef8 6 565 1875 2025-03-02T11:21:06Z Atmois 13 Sourced from: https://starcitizen.tools/resources/assets/badge-mediawiki.svg wikitext text/x-wiki == Summary == Sourced from: https://starcitizen.tools/resources/assets/badge-mediawiki.svg 151946ed5ece0513ec992dab78fd6cf3a4e2f5f3 1878 1875 2025-03-02T11:21:52Z Atmois 13 Protected "[[File:Badge-mediawiki.svg]]": High traffic page: Footer Icon ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [Upload=Allow only administrators] (indefinite)) wikitext text/x-wiki == Summary == Sourced from: https://starcitizen.tools/resources/assets/badge-mediawiki.svg 151946ed5ece0513ec992dab78fd6cf3a4e2f5f3 6 566 1876 2025-03-02T11:21:24Z Atmois 13 Sourced from: https://starcitizen.tools/resources/assets/badge-ccbysa.svg wikitext text/x-wiki == Summary == Sourced from: https://starcitizen.tools/resources/assets/badge-ccbysa.svg 30321a631720cd455c62539e6028737b79866af4 1877 1876 2025-03-02T11:21:38Z Atmois 13 Protected "[[File:Badge-ccbysa.svg]]": Footer Icon ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [Upload=Allow only administrators] (indefinite)) wikitext text/x-wiki == Summary == Sourced from: https://starcitizen.tools/resources/assets/badge-ccbysa.svg 30321a631720cd455c62539e6028737b79866af4 8 400 1879 1390 2025-03-04T19:17:27Z Atmois 13 Update contact info wikitext text/x-wiki This is the official wiki by the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server ! fd190c8a617d119cff3426c36475485c68ad5af5 1887 1879 2025-03-10T17:43:20Z Atmois 13 Fix grammer wikitext text/x-wiki This is the official wiki by the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server! fbca210f223ec142ba414d3ef05dcc3af7f30c57 8 538 1880 1792 2025-03-04T19:21:23Z Atmois 13 remove notice wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 567 1881 2025-03-04T19:24:40Z Bont 128 xfce mascot wikitext text/x-wiki == Summary == xfce mascot 02b7c869b4b1a567a63c07c63489fb9df476d4e4 0 568 1882 2025-03-04T19:29:00Z Bont 128 add xue wikitext text/x-wiki {{MascotInfobox | title = Xue | image = [[File:Xfce-xue.jpg]] | caption = Xue the XFCE mascot }} Xue is the mascot of [https://xfce.org/ XFCE] Xue is described as a black female mouse in [https://supertuxkart.net/Main_Page SuperTuxKart] [[Category:Mascots]] 03fc0e99d23846f8ca6587f86157c4aabc43e8de 0 569 1883 2025-03-04T19:37:20Z Bont 128 Add beastie page wikitext text/x-wiki {{MascotInfobox | title = Beastie (BSD Daemon) | image = [[File:Daemon-phk.svg]] | caption = Beastie, the BSD mascot }} Beastie is the mascot of [https://freebsd.org/ FreeBSD and BSD] Beastie is a red devil (daemon) who wears green sneakers and holds a yellow trident. [[Category:Mascots]] f28087e2f36b39398b1f25c0272e4b77222323d4 0 570 1884 2025-03-04T19:44:50Z Bont 128 add gnu wikitext text/x-wiki {{MascotInfobox | title = GNU | image = [[File:Heckert_GNU_white.svg]] | caption = GNU, the mascot of the GNU Project }} GNU is the mascot of the GNU Project [https://gnu.org/ gnu.org] GNU is a black and white sketch of a wildebeest (also known as a gnu or gnou) [[Category:Mascots]] 4f2a17b8d5fc5e323a303fd87e58ebbb87fc429b 0 176 1886 1670 2025-03-10T00:42:28Z Uncognic 129 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.3.2, 2025-02-25 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 68c00834a6a63291db702bb9576be71f6d388639 4 571 1890 2025-03-16T16:41:09Z Atmois 13 Create privacy policy wikitext text/x-wiki == atl.wiki Privacy Policy == Last Updated: 16th March 2025 Welcome to '''atl.wiki'''<nowiki/>'s Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''atl.wiki'''. By accessing or contributing to '''atl.wiki''', you agree to the terms outlined in this Privacy Policy. === <u>Information we Collect</u> === When editing '''atl.wiki''' you are creating a permanent, public record of every piece of content added, removed, or altered by you. Public historical logs will show the time of contribution and your username along with a log of edited content which will be publically available. When editing, your IP address will also be logged for anti-vandalism efforts, however it will only be available to administrators. ''To contribute to '''atl.wiki''', you are required to create an account. When registering, we collect:'' * A Username * Your Email Address (For account verification, password resets and communication purposes) ''When interacting with atl.wiki we collect the following information:'' * Edited Content * Comments Written * Pages Visited ''We may also collect the following information automatically:'' * IP Address * Browser Type * Device Information === <u>How we use your Information</u> === We do not sell, trade, or otherwise transfer your personal information to third parties. We will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where we are present. We will never provide your information to third parties without your explicit consent. ''We use your data to do the following:'' * To send administrative information to you. * For password resets via email. * To moderate and combat vandalism & spam. * To correctly attribute contributions to users. * To monitor and analyse the usage of our services. We use a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so we can’t guarantee that our security will not be breached. In the event of a data breach, we will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities. === <u>Your Rights</u> === Under the General Data Protections Act (GDPR) you are afforded the following rights: # The right to access, update or to delete the information we have on you. You can view and edit all of your data via your account settings. # The right to request that we correct any information about you that you believe is inaccurate or incomplete. # The right to object or request the restriction of our processing of your personal information. # The right to request a copy of the information we have on you in a structured and commonly used format. # The right to withdraw your consent at any time when '''atl.wiki''' relied on your consent to process your personal information. In order to comply with GDPR erasure requests and the licensing of '''atl.wiki''', we have implemented a process to remove all your data from '''atl.wiki'''. We will anonymise your account name and reattribute your edits to the anonymised username, as well as ask you to remove your email via your user preferences. Once this process has been completed we will "vanish" your account, which removes it from public logs, then we will block your account to prevent future logins. Please note that this process is irreversible once completed. This will also not remove anywhere that your username was edited into a page, and we will not remove reference to your name throughout the talk pages. To request this, please contact us using the information at the bottom of the page. == <u>Changes to the Privacy Policy</u> == We may change the Privacy Policy as needed to represent changes in our practises or legal requirements. We will notify users of updates that impact them, and all revisions will be available on this page. == <u>Third-party Links</u> == '''atl.wiki''' may contain links to third-party websites. We are not responsible for the privacy practices or content of these sites. We encourage users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>wiki@allthingslinux.org</code>. e342a291c4a40cb7d5cc381a5aca49f57eaa0653 1891 1890 2025-03-16T16:44:50Z Atmois 13 Update formatting wikitext text/x-wiki == atl.wiki Privacy Policy == Last Updated: 16th March 2025 Welcome to '''atl.wiki'''<nowiki/>'s Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''atl.wiki'''. By accessing or contributing to '''atl.wiki''', you agree to the terms outlined in this Privacy Policy. === <u>Information we Collect</u> === When editing '''atl.wiki''' you are creating a permanent, public record of every piece of content added, removed, or altered by you. Public historical logs will show the time of contribution and your username along with a log of edited content which will be publically available. When editing, your IP address will also be logged for anti-vandalism efforts, however it will only be available to administrators. ''To contribute to '''atl.wiki''', you are required to create an account. When registering, we collect:'' * A Username * Your Email Address (For account verification, password resets and communication purposes) ''When interacting with atl.wiki we collect the following information:'' * Edited Content * Comments Written * Pages Visited ''We may also collect the following information automatically:'' * IP Address * Browser Type * Device Information === <u>How we use your Information</u> === We do not sell, trade, or otherwise transfer your personal information to third parties. We will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where we are present. We will never provide your information to third parties without your explicit consent. ''We use your data to do the following:'' * To send administrative information to you. * For password resets via email. * To moderate and combat vandalism & spam. * To correctly attribute contributions to users. * To monitor and analyse the usage of our services. We use a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so we can’t guarantee that our security will not be breached. In the event of a data breach, we will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities. === <u>Your Rights</u> === ''Under the General Data Protections Act (GDPR) you are afforded the following rights:'' # The right to access, update or to delete the information we have on you. You can view and edit all of your data via your account settings. # The right to request that we correct any information about you that you believe is inaccurate or incomplete. # The right to object or request the restriction of our processing of your personal information. # The right to request a copy of the information we have on you in a structured and commonly used format. # The right to withdraw your consent at any time when '''atl.wiki''' relied on your consent to process your personal information. In order to comply with GDPR erasure requests and the licensing of '''atl.wiki''', we have implemented a process to remove all your data from '''atl.wiki'''. We will anonymise your account name and reattribute your edits to the anonymised username, as well as ask you to remove your email via your user preferences. Once this process has been completed we will "vanish" your account, which removes it from public logs, then we will block your account to prevent future logins. Please note that this process is irreversible once completed. This will also not remove anywhere that your username was edited into a page, and we will not remove reference to your name throughout the talk pages. To request this, please contact us using the information at the bottom of the page. == <u>Changes to the Privacy Policy</u> == We may change the Privacy Policy as needed to represent changes in our practises or legal requirements. We will notify users of updates that impact them, and all revisions will be available on this page. == <u>Third-party Links</u> == '''atl.wiki''' may contain links to third-party websites. We are not responsible for the privacy practices or content of these sites. We encourage users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>wiki@allthingslinux.org</code>. dd73080f97fa9e9e9f0e398bd139205495f5b099 1 221 1892 559 2025-03-17T14:35:49Z Atmois 13 Remove deadlink wikitext text/x-wiki == LarryInfobox causes Larry the Cow to infect this page == What it reads on the tin, I thought it read Tux the Cow when I saw that bug. Balkenix ([[User talk:Balkenix|talk]]) 08:01, 5 June 2024 (UTC) 323cd5b7a03fb0b4990322b0619986bfdb6e49fe 1 222 1893 561 2025-03-17T14:36:22Z Atmois 13 Remove deadlink wikitext text/x-wiki == NixOS Linux == I do not think its called that. It is called simply NixOS if memory serves. Balkenix 08:04, 5 June 2024 (UTC) e8ebcf9bb740aa0b6fa47d4cdc1cc5cad27c3204 1 221 1894 1892 2025-03-17T14:36:34Z Atmois 13 Remove deadlink wikitext text/x-wiki == LarryInfobox causes Larry the Cow to infect this page == What it reads on the tin, I thought it read Tux the Cow when I saw that bug. Balkenix 08:01, 5 June 2024 (UTC) 991eba9ce4a3d67703e549995c536f8bfd03c0b8 0 1 1895 1885 2025-03-19T16:30:37Z Atmois 13 Fix link wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out #wiki-chat on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:About#Staff|about#staff]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact an administrator via the methods listed on [[Main_Page#About|about#staff]]. __NOTOC__ 0b172db18ad6fd6c618c7656840954af97f445d8 1896 1895 2025-03-20T23:00:15Z Atmois 13 add info wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out #wiki-chat on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:About#Staff|about#staff]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * For users interested in creating guides for atl.wiki, ensure to check out [[Guides:Contributing]]! ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact an administrator via the methods listed on [[Main_Page#About|about#staff]]. __NOTOC__ e249ba8bccd43179bd704873042d6d646f01f3df 3000 572 1897 2025-03-20T23:18:13Z Atmois 13 Create guides contributing guideliens wikitext text/x-wiki TLDR: Ensure you have the <code><nowiki>{{CommandWarning}}</nowiki></code> template on the page, and all changes must be approved by staff for public viewing via ApprovedRevs. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. Guides are anything that explain to a user ''how'' to do something. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide how to harden Firefox with more privacy focused options, we expect and will maintain a higher standard of quality and safety than standard articles. This is because you are providing information to users to do things on their own hardware, which could potentially damage the systems or cause data loss. All main wiki policies apply, including but not limited to the [[Atl.wiki:Code of Conduct|Code of Conduct]] and the wiki [[policies]]. However, a special set of criteria are required, as outlined below: * All pages MUST contain the CommandWarning template at the beginning of the page. There are no exceptions to this rule, and violations of it will have the edits rejected until it has been added. You can add it using <code><nowiki>{{CommandWarning}}</nowiki></code> at the beginning of the page. {{Command Warning}} * To prevent malicious information being distributed on atl.wiki, all changes to guides from non-moderators/ATL staff must be approved by a moderator. When you make an edit it is submitted for review automatically and will normally be reviewed within 24 hours, but if it is still pending after 48 hours feel free to contact an admin. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this, so please double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. We aim to provide unbiased and informative content to all users, your personal views, whilst valid, are not relevant here. * You are responsible for ensuring all commands you provide are functional and not dangerous, if there are risks with running a specific command ensure to clearly state them when listing the command and if it's a command dependent on specific system requirements ensure to outline the requirements or prerequisites clearly. Any dangerous commands provided will be held accountable to whomever adds them to a guide. You can see a good example of a guide here on the guide for <MAKE DEMO GUIDE> which is maintained and has been made in accordance with our guidelines and standards, ff932b5e258801b2d0ffe2a0fa85516d4f5aeb8f 1898 1897 2025-03-20T23:18:33Z Atmois 13 Protected "[[Guides:Contributing]]": Meta page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki TLDR: Ensure you have the <code><nowiki>{{CommandWarning}}</nowiki></code> template on the page, and all changes must be approved by staff for public viewing via ApprovedRevs. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. Guides are anything that explain to a user ''how'' to do something. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide how to harden Firefox with more privacy focused options, we expect and will maintain a higher standard of quality and safety than standard articles. This is because you are providing information to users to do things on their own hardware, which could potentially damage the systems or cause data loss. All main wiki policies apply, including but not limited to the [[Atl.wiki:Code of Conduct|Code of Conduct]] and the wiki [[policies]]. However, a special set of criteria are required, as outlined below: * All pages MUST contain the CommandWarning template at the beginning of the page. There are no exceptions to this rule, and violations of it will have the edits rejected until it has been added. You can add it using <code><nowiki>{{CommandWarning}}</nowiki></code> at the beginning of the page. {{Command Warning}} * To prevent malicious information being distributed on atl.wiki, all changes to guides from non-moderators/ATL staff must be approved by a moderator. When you make an edit it is submitted for review automatically and will normally be reviewed within 24 hours, but if it is still pending after 48 hours feel free to contact an admin. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this, so please double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. We aim to provide unbiased and informative content to all users, your personal views, whilst valid, are not relevant here. * You are responsible for ensuring all commands you provide are functional and not dangerous, if there are risks with running a specific command ensure to clearly state them when listing the command and if it's a command dependent on specific system requirements ensure to outline the requirements or prerequisites clearly. Any dangerous commands provided will be held accountable to whomever adds them to a guide. You can see a good example of a guide here on the guide for <MAKE DEMO GUIDE> which is maintained and has been made in accordance with our guidelines and standards, ff932b5e258801b2d0ffe2a0fa85516d4f5aeb8f 1913 1898 2025-03-22T16:35:37Z Atmois 13 Update template wikitext text/x-wiki TLDR: Ensure you have the <code><nowiki>{{CommandWarning}}</nowiki></code> template on the page, and all changes must be approved by staff for public viewing via ApprovedRevs. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. Guides are anything that explain to a user ''how'' to do something. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide how to harden Firefox with more privacy focused options, we expect and will maintain a higher standard of quality and safety than standard articles. This is because you are providing information to users to do things on their own hardware, which could potentially damage the systems or cause data loss. All main wiki policies apply, including but not limited to the [[Atl.wiki:Code of Conduct|Code of Conduct]] and the wiki [[policies]]. However, a special set of criteria are required, as outlined below: * All pages MUST contain the CommandWarning template at the beginning of the page. There are no exceptions to this rule, and violations of it will have the edits rejected until it has been added. You can add it using <code><nowiki>{{GuideWarning}}</nowiki></code> at the beginning of the page. {{Guide Warning}} * To prevent malicious information being distributed on atl.wiki, all changes to guides from non-moderators/ATL staff must be approved by a moderator. When you make an edit it is submitted for review automatically and will normally be reviewed within 24 hours, but if it is still pending after 48 hours feel free to contact an admin. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this, so please double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. We aim to provide unbiased and informative content to all users, your personal views, whilst valid, are not relevant here. * You are responsible for ensuring all commands you provide are functional and not dangerous, if there are risks with running a specific command ensure to clearly state them when listing the command and if it's a command dependent on specific system requirements ensure to outline the requirements or prerequisites clearly. Any dangerous commands provided will be held accountable to whomever adds them to a guide. You can see a good example of a guide here on the guide for <MAKE DEMO GUIDE> which is maintained and has been made in accordance with our guidelines and standards, 28829893ae114466f5f5d2f1c472885276e5c6fa 1919 1913 2025-03-22T18:34:50Z Atmois 13 Add link to exemplar guide wikitext text/x-wiki TLDR: Ensure you have the <code><nowiki>{{CommandWarning}}</nowiki></code> template on the page, and all changes must be approved by staff for public viewing via ApprovedRevs. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. Guides are anything that explain to a user ''how'' to do something. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide how to harden Firefox with more privacy focused options, we expect and will maintain a higher standard of quality and safety than standard articles. This is because you are providing information to users to do things on their own hardware, which could potentially damage the systems or cause data loss. All main wiki policies apply, including but not limited to the [[Atl.wiki:Code of Conduct|Code of Conduct]] and the wiki [[policies]]. However, a special set of criteria are required, as outlined below: * All pages MUST contain the CommandWarning template at the beginning of the page. There are no exceptions to this rule, and violations of it will have the edits rejected until it has been added. You can add it using <code><nowiki>{{GuideWarning}}</nowiki></code> at the beginning of the page. {{Guide Warning}} * To prevent malicious information being distributed on atl.wiki, all changes to guides from non-moderators/ATL staff must be approved by a moderator. When you make an edit it is submitted for review automatically and will normally be reviewed within 24 hours, but if it is still pending after 48 hours feel free to contact an admin. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this, so please double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. We aim to provide unbiased and informative content to all users, your personal views, whilst valid, are not relevant here. * You are responsible for ensuring all commands you provide are functional and not dangerous, if there are risks with running a specific command ensure to clearly state them when listing the command and if it's a command dependent on specific system requirements ensure to outline the requirements or prerequisites clearly. Any dangerous commands provided will be held accountable to whomever adds them to a guide. You can see a good example of a guide here on the guide for '''[[Guides:Setting up Flathub on Fedora|Setting up Flathub on Fedora]]''' which is maintained and has been made in accordance with our guidelines and standards, a0377c0dd91cbd1ce96eefd4b766846d1c1a981e 10 482 1899 1836 2025-03-22T12:01:16Z Atmois 13 Update template wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands or instructions which could potentially damage your system. Please ensure you understand the commands or instructions you are running or following before you run or follow them. If you see a dangerous instruction, please report it to an administrator.</span> <div class="mbox-text">This warning is placed on any page that lists a command and gives users instructions to follow, it exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands should be reported to an [[Atl.wiki:About#Staff|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> a187ee0619a8641c569af8e7090881136c6ab735 1900 1899 2025-03-22T12:01:42Z Atmois 13 Atmois moved page [[Template:Command Warning]] to [[Template:Guide Warning]] without leaving a redirect: Rename with a better name wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands or instructions which could potentially damage your system. Please ensure you understand the commands or instructions you are running or following before you run or follow them. If you see a dangerous instruction, please report it to an administrator.</span> <div class="mbox-text">This warning is placed on any page that lists a command and gives users instructions to follow, it exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands should be reported to an [[Atl.wiki:About#Staff|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> a187ee0619a8641c569af8e7090881136c6ab735 1903 1900 2025-03-22T12:03:31Z Atmois 13 Update wording wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands or instructions which could potentially damage your system. Please ensure you understand the commands or instructions you are running or following before you run or follow them. If you see a dangerous instruction, please report it to an administrator.</span> <div class="mbox-text">This warning is placed on any page that lists a command and gives users instructions to follow, it exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[Atl.wiki:About#Staff|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 897139303f81124a317380e557c52dec69b5bc4b 1907 1903 2025-03-22T12:09:04Z Atmois 13 Update formatting wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands or instructions which could potentially damage your system. Please ensure you understand the commands or instructions you are running or following before you run or follow them. If you see a dangerous instruction, please report it to an administrator.</span> <div class="mbox-text">{{/doc}}</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 1f4842aeabdd6f95e7e74bac2350c0d3c066f5fc 1916 1907 2025-03-22T16:49:21Z Atmois 13 Update template wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article lists commands or instructions which could potentially damage your system. Please ensure you understand the commands or instructions you are running or following before you run or follow them. If you see a dangerous instruction, please report it to an administrator.</span> <div class="mbox-text">This warning exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[Atl.wiki:About#Staff|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> de257e8bfc900dc7a2832aed6f3f68858a339654 10 521 1901 1710 2025-03-22T12:01:42Z Atmois 13 Atmois moved page [[Template:Command Warning/doc]] to [[Template:Guide Warning/doc]] without leaving a redirect: Rename with a better name wikitext text/x-wiki This warning must placed on any page that lists a command that a user can run on their system, it exists to make users wary of running random commands they see on the internet and that they understand what they are doing to their system. Dangerous commands should be reported to an [[Main Page#Contacts|administrator]] immediately. == Usage == <code>{{tlx|Command_Warning}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> d0f78515902b4d3ac95946fad618d6cdbcac87ba 1902 1901 2025-03-22T12:03:03Z Atmois 13 Update info wikitext text/x-wiki This warning is placed on any page that lists a command and gives users instructions to follow, it exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[Atl.wiki:About#Staff|administrator]] immediately. == Usage == <code>{{tlx|Guide_Warning}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> c2e45f0daf8e9c210a056793c5624154a3195e17 10 523 1904 1835 2025-03-22T12:06:06Z Atmois 13 Update wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes and to notify the staff that it may not meet the [[Policies|contributing standards]] yet.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 6b686588a1e2fec80874976cfcc523892c183505 1906 1904 2025-03-22T12:08:28Z Atmois 13 Update formatting wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">{{/doc}}</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> c8cdc21c3547c368962f78fce4bfa557f6b476ce 1915 1906 2025-03-22T16:48:34Z Atmois 13 Update template wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This template means the author of a page is still actively working on the page, and this serves to notify other editors to check with them before potentially creating conflicting changes and to notify the staff that it may not meet the [[Policies|contributing standards]] yet.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 7e52ee8c825a7b23b148c71dda6bb3602dc1a3e7 10 524 1905 1718 2025-03-22T12:06:17Z Atmois 13 Update wikitext text/x-wiki This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes and to notify the staff that it may not meet the [[Policies|contributing standards]] yet. == Usage == <code>{{tlx|Work_In_Progress}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 2989c57d30a01aca5462474c7422a84c3b97157e 10 483 1908 1833 2025-03-22T12:10:30Z Atmois 13 Update formatting wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified.}}</span> <div class="mbox-text">{{/doc}}</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> bce81fd8a746545cc4c0da628cf108650e5d375d 1914 1908 2025-03-22T16:43:38Z Atmois 13 Fix formatting wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified.}}</span> <div class="mbox-text">This template means a page might not meet the wiki's [[Policies#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> c94d2efdf4686fab0f812bb2cc87b763eb25497d 10 494 1909 1695 2025-03-22T12:10:59Z Atmois 13 Update formatting wikitext text/x-wiki This template should be placed on pages which might not meet the wiki's [[Policies#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Biased Tone", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance Templates]]</includeonly> d5be538242d574ffcc0344aefef5e66efacceb42 10 513 1910 1834 2025-03-22T12:12:57Z Atmois 13 Update formatting wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">{{/doc}}</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Needs Citations]]</includeonly><noinclude> {{/doc}}</noinclude> fec68c6e41aafd8bbdb327ab897be5cc2868d327 1917 1910 2025-03-22T16:51:47Z Atmois 13 Update template wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This template is to be used on pages which may lack credible citations, as per our [[Policies#Citations|citations policy]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Needs Citations]]</includeonly><noinclude> {{/doc}}</noinclude> 1394cb98568d449129a8c67c60d50b00f20d6441 10 514 1911 1698 2025-03-22T12:13:44Z Atmois 13 Update wikitext text/x-wiki This template should be placed on pages which lack credible citations, as per our [[Policies#Citations|citations policy]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require moer citations. == Usage == <code>{{tlx|Needs Citations}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 5b3b2c7aa91a8898ff09218f0426b16b897349b7 1912 1911 2025-03-22T12:15:15Z Atmois 13 fix grammer and typo wikitext text/x-wiki This template should be placed on pages which may lack credible citations, as per our [[Policies#Citations|citations policy]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations. == Usage == <code>{{tlx|Needs Citations}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 7f8550e19abb7a6c606ed873794aa85fbc943339 3000 573 1918 2025-03-22T18:34:00Z Atmois 13 Create Guide for Flathub on Fedora wikitext text/x-wiki {{Guide Warning}} [[Flathub]] is a third party [[repository]] of applications that are packaged in the [[Flatpak]] format. By default, [[Fedora]] does not include the Flathub repository<ref>[https://developer.fedoraproject.org/deployment/flatpak/flatpak-usage.html Flatpak Usage On Fedora], Felipe Borges, Jarek Prokop, John Atti, Nick Dirschel, Pavel Valena, 2018 (Retrieved 22nd March 2025)</ref>. Some Flathub apps are also in the main Fedora repositories, but in some cases it ships newer versions or applications that aren’t available in the Fedora repositories<ref>[https://fedoramagazine.org/install-flathub-apps-fedora/ Installing Flathub Apps on Fedora], Ryan Lerch, 2018 (Retrieved 22nd March 2025)</ref>. You can set up Flathub graphically or via the command line, the recommended method is via the Flathub repository file or the terminal: ====== Installing Flathub via the Flathub Repository File (Recommended) ====== # Visit [https://flathub.org/setup/Fedora flathub.org/setup/Fedora] and select the text saying <code>Flathub Repository File</code> to download <code>flathub.flatpakrepo</code>. # Open your file manager and double-click the <code>flathub.flatpakrepo</code> file. It will open KDE Discover or GNOME software. # Select the <code>Install</code> button, you may need to log out and log back in to Fedora for Flathub apps to appear. ====== Installing Flathub via GNOME Software ====== # Open GNOME software and select the hamburger menu on the top right of the application and select <code>Software Respositories</code>. # Scroll down and enable the toggle for <code>Flathub</code> and the toggle for <code>Enable New Repositories</code>. # You may need to log out and log back into Fedora or run <code>gnome-software --quit</code> in your terminal for Flathub apps to appear in GNOME software. ====== Installing Flathub via the Command Line ====== # Open your terminal of choice. # Run the command <code>flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki></code>. # You may need to log out and log back into Fedora for Flathub apps to appear in GNOME software or KDE Discover. <references /> dbd62c73c6b292866a1362a51797cef8ecd7fed6 0 176 1920 1886 2025-03-23T00:07:26Z Uncognic 129 Added Plasma 6.3.3 release wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.3.3, 2025-03-11 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], an application store for Flatpak, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 417d095b7cdd9c9abc401e318fc13dfa576a0bbe 1921 1920 2025-03-23T00:08:52Z Uncognic 129 /* Features */ Discover supports updating and installing packages from the system package manager too wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.3.3, 2025-03-11 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's graphical package manager, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] b64ee6df3a374daa4eb9fdeb153174e310e30563 0 574 1922 2025-03-28T05:27:07Z Supus 132 Created a desultory wiki for sway, with definition, features and some warning before installation wikitext text/x-wiki Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes great inspiration from [[I3]] in its design and configuration, and, consequently, it is very compatible with [[I3]]. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[Swayfx]] is a fork of Sway that adds cool effects, animations, and visuals to it, something you may want to look into. === Notable Features: === According to Sway's official website: * Sway allows you to arrange your application windows ''logically'', rather than ''spatially''. * Windows are arranged into a grid by default which maximizes the efficiency of your screen and can be quickly manipulated using only the keyboard. * It works with your existing i3 configuration and supports most of i3's features, plus a few extras. * Extensive documentation in the form of man pages. == Pre-Installation: == All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. Not all login managers support Wayland. If you have issues starting sway and you use a login manager, your first step should be disabling the login manager and running sway as described by <code>man 1 sway.</code> 28ae8bcf0f86770fb42013d729e07e2e5a081ac3 1923 1922 2025-03-28T14:23:03Z Supus 132 rephrasing to avoid license related issues. wikitext text/x-wiki Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes great inspiration from [[I3]] in its design and configuration, and, consequently, it is very compatible with [[I3]]. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[Swayfx]] is a fork of Sway that adds cool effects, animations, and visuals to it, something you may want to look into. === Notable Features: === According to Sway's official website: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. == Pre-Installation: == * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> 05861ab2d64a4dfaeb1b722d92b004b1e69f4bf6 1924 1923 2025-03-29T10:21:36Z Supus 132 /* Pre-Installation: */ Added Installation section. May need a review by someone. wikitext text/x-wiki Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes great inspiration from [[I3]] in its design and configuration, and, consequently, it is very compatible with [[I3]]. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[Swayfx]] is a fork of Sway that adds cool effects, animations, and visuals to it, something you may want to look into. === Notable Features: === According to Sway's official website: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. == Pre-Installation: == * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] == Installation: == ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For Arch: ==== Using pacman: sudo pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For Debian: ==== Using apt package manager: apt install sway 0b96c960102d9f978e64c44d2b06ed225711824d 0 575 1925 2025-03-29T20:00:01Z Amadaluzia 52 Initialise page wikitext text/x-wiki GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref>. == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 27, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs notates their keybindings with the following table: (WIP) == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move `~/.emacs` to `~/.emacs.d/init.el` (create the directory if it is missing) to avoid any future confusion. In this `init.el`, add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After restarting Emacs, or running `elisp-re == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. 0fdd31c1e08cdc5ceaadeb4a63015646387b3a85 1928 1925 2025-03-29T20:12:29Z Lactose 130 Add SoftwareInfobox wikitext text/x-wiki {{SoftwareInfobox|image=[[File:EmacsIcon.svg|thumb]]|caption=GNU Emacs logo|title=GNU Emacs|releasestatus=Maintained|lastrelease=30.1, Feb 23, 2025|languages=[[C]], [[Emacs Lisp]]|developers=[[GNU]]|website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org]}} GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 27, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs notates their keybindings with the following table: (WIP) == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move `~/.emacs` to `~/.emacs.d/init.el` (create the directory if it is missing) to avoid any future confusion. In this `init.el`, add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After restarting Emacs, or running `elisp-re == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. 8bb35f68e119cc7f0b1ca592c852926ed8cd9b2d 1930 1928 2025-03-29T20:23:25Z Amadaluzia 52 Adds an image under the SoftwareInfobox. wikitext text/x-wiki {{SoftwareInfobox|image=[[File:EmacsIcon.svg|thumb]]|caption=GNU Emacs logo|title=GNU Emacs|releasestatus=Maintained|lastrelease=30.1, Feb 23, 2025|languages=[[C]], [[Emacs Lisp]]|developers=[[GNU]]|website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org]}} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 27, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs notates their keybindings with the following table: (WIP) == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move `~/.emacs` to `~/.emacs.d/init.el` (create the directory if it is missing) to avoid any future confusion. In this `init.el`, add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After restarting Emacs, or running `elisp-re == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. 26eaf3ed3b74314bd2e56f1bf1340b936ee9d668 1931 1930 2025-03-29T21:41:11Z Lactose 130 Added key modifiers in keybindings wikitext text/x-wiki {{SoftwareInfobox|image=[[File:EmacsIcon.svg|thumb]]|caption=GNU Emacs logo|title=GNU Emacs|releasestatus=Maintained|lastrelease=30.1, Feb 23, 2025|languages=[[C]], [[Emacs Lisp]]|developers=[[GNU]]|website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org]}} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 27, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several prefix keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- !C- !Control ! |- |M- |Meta |This is the Alt or Option key |- |S- |Shift | |- |s- |Super |This is the Windows or Command key |- |H- |Hyper |This key is supported, but no default bindings use it |- |A- |Alt* |*This is most certainly NOT the same key as Alt. This is a hold over back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move `~/.emacs` to `~/.emacs.d/init.el` (create the directory if it is missing) to avoid any future confusion. In this `init.el`, add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After restarting Emacs, or running `elisp-re == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. 58677b8f0a13a452556c6c2ca540eec5dbc913e2 1932 1931 2025-03-29T21:43:26Z Amadaluzia 52 Completes some more stuff wikitext text/x-wiki {{SoftwareInfobox|image=[[File:EmacsIcon.svg|thumb]]|caption=GNU Emacs logo|title=GNU Emacs|releasestatus=Maintained|lastrelease=30.1, Feb 23, 2025|languages=[[C]], [[Emacs Lisp]]|developers=[[GNU]]|website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org]}} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 27, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several prefix keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- !C- !Control ! |- |M- |Meta |This is the Alt or Option key |- |S- |Shift | |- |s- |Super |This is the Windows or Command key |- |H- |Hyper |This key is supported, but no default bindings use it |- |A- |Alt* |*This is most certainly NOT the same key as Alt. This is a hold over back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. 6482df2173fcbbcf0c388b7a526dd5442e899794 1935 1932 2025-03-29T22:02:32Z Lactose 130 Fix SoftwareInfobox wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 27, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several prefix keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- !C- !Control ! |- |M- |Meta |This is the Alt or Option key |- |S- |Shift | |- |s- |Super |This is the Windows or Command key |- |H- |Hyper |This key is supported, but no default bindings use it |- |A- |Alt* |*This is most certainly NOT the same key as Alt. This is a hold over back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. c7e833cb48370f5772d43ab99e9dcad0f8c59a49 1936 1935 2025-03-29T22:06:42Z Lactose 130 Fix typo wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 27, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several prefix keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- !C- !Control ! |- |M- |Meta |This is the Alt or Option key |- |S- |Shift | |- |s- |Super |This is the Windows or Command key |- |H- |Hyper |This key is supported, but no default bindings use it |- |A- |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. c9e98e05b0d654c5dddaf58f7b0fb97dd2ddd43f 1937 1936 2025-03-29T22:17:17Z Lactose 130 Expand on Keybindings wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 27, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |C- |Control | |- |M- |Meta |This is the Alt or Option key |- |S- |Shift | |- |s- |Super |This is the Windows or Command key |- |H- |Hyper |This key is supported, but no default bindings use it |- |A- |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. 64724a65af2c6c5f2492e8bc576a9cea25aeb275 1938 1937 2025-03-29T22:20:20Z Lactose 130 /* Keybindings */ wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 27, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. 3b24e0806b31ff049b662ce4d43e20be8c06a70f 1940 1938 2025-03-30T00:11:49Z Amadaluzia 52 Bump reccomended version to 28 wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 28, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. fe68ee5ee48fa52b81b9ab685402105cf8780640 1941 1940 2025-03-30T00:20:35Z Amadaluzia 52 Write an initial paragraph on Documentation wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 28, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by pressing <code>C-h ?</code> and pressing the key corresponding to the section you are looking for. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. 6172353c35fbb8d401ee3d87a89ecd3b2700eed2 1942 1941 2025-03-30T00:34:03Z Katz 53 /* Keybindings */ added Return key wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 28, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by pressing <code>C-h ?</code> and pressing the key corresponding to the section you are looking for. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. 44ff789721cbd1c6276d062042c86f7c6cd1e3c9 2 325 1926 1889 2025-03-29T20:01:01Z Katz 53 what wikitext text/x-wiki hi did you know i use emacs of the gnu variety wow that's crazy i know subscribe to my gnutreon 3a82f56586ca99abda1a988c54bbea1db8e0c85c 0 173 1927 910 2025-03-29T20:07:51Z Katz 53 Added citation of a tty dm wikitext text/x-wiki [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager (G'''DM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a graphical user interface that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.<ref>https://github.com/tvrzna/emptty</ref> [[Category:Terminology]] 4e4f8aa712e970a7e6bed333528b23dfebd5951a 6 576 1929 2025-03-29T20:22:10Z Amadaluzia 52 wikitext text/x-wiki A screenshot of a fresh Emacs 30.1 installation. 67ed71247e54ae6ec6085b7d35c934acac632a4a 828 204 1933 1728 2025-03-29T21:43:56Z Atmois 13 Add first release field Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Last Release', args.lastrelease ) :addRow( 'First Release', args.firstrelease ) :addRow( 'Language(s)', args.languages ) :addRow( 'Developer(s)', args.developers ) :addRow( 'Website', args.website ) return retval end return p f140ef2be48a0605732739bf634c04aa4c2eb1f6 828 528 1934 1738 2025-03-29T21:45:59Z Atmois 13 Add new field wikitext text/x-wiki == Usage == In order to embed a infobox for software, you can put this at the very top of your article <pre> {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.99.0, 2024-10-23 | firstrelease = 1.0.1, 2022-08-01 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} </pre> 38e7017ba79462008a68c617f4267fa0b4860f5c 2 3 1939 1781 2025-03-30T00:04:30Z Amadaluzia 52 Zig -> Rust, additional hints wikitext text/x-wiki <syntaxhighlight lang="rust"> use std::collections::HashMap; struct AboutMe<'a> { name: &'a str, socials: HashMap<&'a str, &'a str>, } fn main() { let amadaluzia = AboutMe { name: "Artur Manuel", socials: HashMap::from([ ("github", "amadaluzia"), ("codeberg", "amadaluzia"), ("matrix", "@amadaluzia:tchncs.de"), ("discord", "amadaluzia"), ("xmpp", "amadaluzia@xmpp.jp"), ("libera.chat", "amadaluzia"), ("signal", "amadaluzia.711") ]), }; println!("Hello! I am {}! You may find me on the following platforms:", amadaluzia.name); for i in amadaluzia.socials.iter() { println!("{}: {}", i.0, i.1) } } </syntaxhighlight>You may also be looking for: [[User:Amadaluzia/GNU Emacs]] a168f5dcabd4824b96d84123f4f028dbac1a3d25 0 575 1943 1942 2025-03-30T01:11:11Z Amadaluzia 52 Adds more info to "Setting up LSP support" wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 28, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) ; WIP HERE! </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. e23ff4222bb0b3275b224a97f09816721ef31973 1944 1943 2025-03-30T01:38:54Z Amadaluzia 52 add `local-set-key`s wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Your distribution may provide an Emacs package you can install with your package manager. Arch Linux provides binaries for the Emacs package for example.<ref>https://archlinux.org/packages/extra/x86_64/emacs/</ref> However, if it is not provided or if your distro provides a version older than Emacs 28, then you can build Emacs yourself.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. 5f46f98ca3b0e081ba05314391687378e4712752 1945 1944 2025-03-30T03:28:01Z Lactose 130 Extend install section wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Most distributions provide an Emacs package, installable via package manager.<ref>https://repology.org/project/emacs/versions</ref> There are multiple variants, each using a different graphical toolkit (or none in the case of <code>emacs-nox</code>). It is recommended to <code>emacs-gtk</code> or <code>emacs-pgtk</code> depending on your display server. The rest of the guide will assume you have a relatively recent release, at least version 28.1. === emacs-gtk (for X11) === <syntaxhighlight lang="shell-session"> # For Debian/Ubuntu based distros sudo apt-get install emacs-gtk # For Arch based distros sudo pacman -S emacs # For Fedora based distros sudo dnf install emacs-gtk+x11 </syntaxhighlight> === emacs-pgtk (for Wayland) === <syntaxhighlight lang="shell-session"> # For Debian/Ubuntu based distros sudo apt-get install emacs-pgtk # For Arch based distros sudo pacman -S emacs-wayland # For Fedora based distros sudo dnf install emacs </syntaxhighlight> === Gentoo Linux === Instead of having separate packages, Gentoo Linux utilizes USE flags to determine which toolkit to build Emacs with.<ref>https://wiki.gentoo.org/wiki/GNU_Emacs</ref> Add one of the following lines in <code>/etc/portage/package.use</code>.<syntaxhighlight lang="shell"># For gtk/X11 app-editors/emacs gtk X # For pgtk/Wayland app-editors/emacs gtk -X</syntaxhighlight>Emacs can now be installed by running <code>sudo emerge --ask app-editors/emacs</code>. == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. f809aa1ba80e4119ae6c6b3c2abc3670aadc2dc3 1946 1945 2025-03-30T03:31:39Z Amadaluzia 52 Remove mysterious new line at the top of the page wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Most distributions provide an Emacs package, installable via package manager.<ref>https://repology.org/project/emacs/versions</ref> There are multiple variants, each using a different graphical toolkit (or none in the case of <code>emacs-nox</code>). It is recommended to <code>emacs-gtk</code> or <code>emacs-pgtk</code> depending on your display server. The rest of the guide will assume you have a relatively recent release, at least version 28.1. === emacs-gtk (for X11) === <syntaxhighlight lang="shell-session"> # For Debian/Ubuntu based distros sudo apt-get install emacs-gtk # For Arch based distros sudo pacman -S emacs # For Fedora based distros sudo dnf install emacs-gtk+x11 </syntaxhighlight> === emacs-pgtk (for Wayland) === <syntaxhighlight lang="shell-session"> # For Debian/Ubuntu based distros sudo apt-get install emacs-pgtk # For Arch based distros sudo pacman -S emacs-wayland # For Fedora based distros sudo dnf install emacs </syntaxhighlight> === Gentoo Linux === Instead of having separate packages, Gentoo Linux utilizes USE flags to determine which toolkit to build Emacs with.<ref>https://wiki.gentoo.org/wiki/GNU_Emacs</ref> Add one of the following lines in <code>/etc/portage/package.use</code>.<syntaxhighlight lang="shell"># For gtk/X11 app-editors/emacs gtk X # For pgtk/Wayland app-editors/emacs gtk -X</syntaxhighlight>Emacs can now be installed by running <code>sudo emerge --ask app-editors/emacs</code>. == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple prefixes can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. 84461b11a080707baba4014e5e64bf9b9ebcdfbf 1947 1946 2025-03-30T03:31:45Z Lactose 130 /* Keybindings */ wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Installing Emacs == Most distributions provide an Emacs package, installable via package manager.<ref>https://repology.org/project/emacs/versions</ref> There are multiple variants, each using a different graphical toolkit (or none in the case of <code>emacs-nox</code>). It is recommended to <code>emacs-gtk</code> or <code>emacs-pgtk</code> depending on your display server. The rest of the guide will assume you have a relatively recent release, at least version 28.1. === emacs-gtk (for X11) === <syntaxhighlight lang="shell-session"> # For Debian/Ubuntu based distros sudo apt-get install emacs-gtk # For Arch based distros sudo pacman -S emacs # For Fedora based distros sudo dnf install emacs-gtk+x11 </syntaxhighlight> === emacs-pgtk (for Wayland) === <syntaxhighlight lang="shell-session"> # For Debian/Ubuntu based distros sudo apt-get install emacs-pgtk # For Arch based distros sudo pacman -S emacs-wayland # For Fedora based distros sudo dnf install emacs </syntaxhighlight> === Gentoo Linux === Instead of having separate packages, Gentoo Linux utilizes USE flags to determine which toolkit to build Emacs with.<ref>https://wiki.gentoo.org/wiki/GNU_Emacs</ref> Add one of the following lines in <code>/etc/portage/package.use</code>.<syntaxhighlight lang="shell"># For gtk/X11 app-editors/emacs gtk X # For pgtk/Wayland app-editors/emacs gtk -X</syntaxhighlight>Emacs can now be installed by running <code>sudo emerge --ask app-editors/emacs</code>. == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. 23e2ef5f3df5b806b18f1b98acb1f9e21bdc7b19 1948 1947 2025-03-30T17:18:17Z Amadaluzia 52 Remove installation guide wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. a6b3fa225bd8cccd7e79d4e98b64ef26fce27a0c 1952 1948 2025-03-30T18:18:03Z Amadaluzia 52 Add a link to the installation guide wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[User:Amadaluzia/GNU Emacs/Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with '''package-install'''. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. 718c814726dba913f832cec43cbb16d312fdb953 1955 1952 2025-03-30T18:43:08Z Amadaluzia 52 Added section about Evil. wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[User:Amadaluzia/GNU Emacs/Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>https://github.com/emacs-evil/evil</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features</ref> and Spacemacs<ref>https://www.spacemacs.org/</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook (prog-mode text-mode)) ; This will start Evil mode opening a text or programming buffer. ;; Option 2 (require 'evil) (add-hook #'prog-mode-hook #'evil-mode) (add-hook #'text-mode-hook #'evil-mode) </syntaxhighlight>You should now have Evil set up to your liking. 01ac09cc8f58dd7a1557c8f563e6f4c04e896269 1957 1955 2025-03-30T19:07:25Z Amadaluzia 52 Respect documentation better wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[User:Amadaluzia/GNU Emacs/Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>https://github.com/emacs-evil/evil</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features</ref> and Spacemacs<ref>https://www.spacemacs.org/</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ; This will start Evil mode opening a text or programming buffer. ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to your liking. f70ab4d4588a5515f857488bb1a3d37c750e1f08 1964 1957 2025-03-30T21:39:18Z Amadaluzia 52 Cleared up some things wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[User:Amadaluzia/GNU Emacs/Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>https://github.com/emacs-evil/evil</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features</ref> and Spacemacs<ref>https://www.spacemacs.org/</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. cb7c17c13e6a7ebab58a43c5212d870b97d78f44 1965 1964 2025-03-31T15:29:37Z Atmois 13 Atmois moved page [[User:Amadaluzia/GNU Emacs]] to [[GNU Emacs]] without leaving a redirect: Previously in sandbox wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[User:Amadaluzia/GNU Emacs/Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>https://github.com/emacs-evil/evil</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features</ref> and Spacemacs<ref>https://www.spacemacs.org/</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. cb7c17c13e6a7ebab58a43c5212d870b97d78f44 1968 1965 2025-03-31T17:32:39Z Amadaluzia 52 Fix redirect wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref>https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>https://github.com/emacs-evil/evil</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features</ref> and Spacemacs<ref>https://www.spacemacs.org/</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. e121787bea972482c8a5ad1481e0717d8c8800dc 1977 1968 2025-04-04T19:19:48Z Lactose 130 Add history section wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>https://github.com/emacs-evil/evil</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features</ref> and Spacemacs<ref>https://www.spacemacs.org/</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. 319531aaf2e174d0e16c736a4c3fce4fb28c5c79 1988 1977 2025-04-05T08:54:44Z Katz 53 Adeede a Categroroyory wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>https://github.com/emacs-evil/evil</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features</ref> and Spacemacs<ref>https://www.spacemacs.org/</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. [[Category:Software]] b5a8ff8982beb66aa59ef780b98f87cccab01776 3000 577 1949 2025-03-30T17:19:22Z Amadaluzia 52 Init page wikitext text/x-wiki Work In Progress 25b4dd6278802d62de32d2537064bfe03b3c2300 1950 1949 2025-03-30T17:22:17Z Amadaluzia 52 Add headers wikitext text/x-wiki WIP === Foreword === WIP === Installing on Gentoo Linux === WIP === Installing GNU Emacs from source === WIP aad58f8e0f01bee2208724e9588f7b9860558c38 1951 1950 2025-03-30T18:16:48Z Amadaluzia 52 Add content wikitext text/x-wiki [[User:Amadaluzia/GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>https://repology.org/project/emacs/versions</ref> and can be installed from Canonical's Snap<ref>https://snapcraft.io/emacs</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. === Foreword === This guide is subject to change. You should not expect the guides below to stay constant. === Installing === ==== Debian/Ubuntu-based distros ==== <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> ==== Fedora-based distros ==== <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> ==== openSUSE Tumbleweed ==== <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> ==== Arch Linux ==== <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> ==== Gentoo Linux ==== The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. 7db5341c8e9b2ea8e9460ae899e94388fd06cd22 1953 1951 2025-03-30T18:19:18Z Amadaluzia 52 Add note about versions wikitext text/x-wiki [[User:Amadaluzia/GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>https://repology.org/project/emacs/versions</ref> and can be installed from Canonical's Snap<ref>https://snapcraft.io/emacs</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. === Foreword === This guide is subject to change. You should not expect the guides below to stay constant. === Installing === ==== Debian/Ubuntu-based distros ==== <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> ==== Fedora-based distros ==== <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> ==== openSUSE Tumbleweed ==== <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> ==== Arch Linux ==== <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> ==== Gentoo Linux ==== The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. e876d2d23d2944f688597be49af5a3111f7e814a 1954 1953 2025-03-30T18:21:21Z Amadaluzia 52 Use headings and better subheadings wikitext text/x-wiki [[User:Amadaluzia/GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>https://repology.org/project/emacs/versions</ref> and can be installed from Canonical's Snap<ref>https://snapcraft.io/emacs</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Foreword == This guide is subject to change. You should not expect the guides below to stay constant. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight lang="shell-session"> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. ffa3997244d7ab80751ff0734eaac99d593b96ec 1956 1954 2025-03-30T19:06:11Z Amadaluzia 52 Remove unnecessary syntax-highlighting wikitext text/x-wiki [[User:Amadaluzia/GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>https://repology.org/project/emacs/versions</ref> and can be installed from Canonical's Snap<ref>https://snapcraft.io/emacs</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Foreword == This guide is subject to change. You should not expect the guides below to stay constant. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. 5381270a7b646327d2c36761d9c1e142983259fd 1960 1956 2025-03-30T19:17:48Z Amadaluzia 52 Adds GuideWarning wikitext text/x-wiki {{GuideWarning}} [[User:Amadaluzia/GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>https://repology.org/project/emacs/versions</ref> and can be installed from Canonical's Snap<ref>https://snapcraft.io/emacs</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Foreword == This guide is subject to change. You should not expect the guides below to stay constant. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. 0b56b92b0b90da3d28b3aa9142146660cc8901cc 1963 1960 2025-03-30T19:26:28Z Amadaluzia 52 Remove foreword wikitext text/x-wiki {{GuideWarning}} [[User:Amadaluzia/GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>https://repology.org/project/emacs/versions</ref> and can be installed from Canonical's Snap<ref>https://snapcraft.io/emacs</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. 55b0d83c5a62a457d00478a526838cd70d3f92fc 1966 1963 2025-03-31T15:30:15Z Atmois 13 Atmois moved page [[User:Amadaluzia/GNU Emacs/Installation Guide]] to [[Guides:Emacs Installation Guide]] without leaving a redirect: Previously in sandbox wikitext text/x-wiki {{GuideWarning}} [[User:Amadaluzia/GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>https://repology.org/project/emacs/versions</ref> and can be installed from Canonical's Snap<ref>https://snapcraft.io/emacs</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. 55b0d83c5a62a457d00478a526838cd70d3f92fc 1967 1966 2025-03-31T15:30:54Z Atmois 13 Update link wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>https://repology.org/project/emacs/versions</ref> and can be installed from Canonical's Snap<ref>https://snapcraft.io/emacs</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. 7f4545a7fe28e5f3635ccfed76ed0315373f049f 3000 572 1958 1919 2025-03-30T19:17:20Z Atmois 13 Update template name reference wikitext text/x-wiki TLDR: Ensure you have the <code><nowiki>{{CommandWarning}}</nowiki></code> template on the page, and all changes must be approved by staff for public viewing via ApprovedRevs. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. Guides are anything that explain to a user ''how'' to do something. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide how to harden Firefox with more privacy focused options, we expect and will maintain a higher standard of quality and safety than standard articles. This is because you are providing information to users to do things on their own hardware, which could potentially damage the systems or cause data loss. All main wiki policies apply, including but not limited to the [[Atl.wiki:Code of Conduct|Code of Conduct]] and the wiki [[policies]]. However, a special set of criteria are required, as outlined below: * All pages MUST contain the GuideWarning template at the beginning of the page. There are no exceptions to this rule, and violations of it will have the edits rejected until it has been added. You can add it using <code><nowiki>{{GuideWarning}}</nowiki></code> at the beginning of the page. {{Guide Warning}} * To prevent malicious information being distributed on atl.wiki, all changes to guides from non-moderators/ATL staff must be approved by a moderator. When you make an edit it is submitted for review automatically and will normally be reviewed within 24 hours, but if it is still pending after 48 hours feel free to contact an admin. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this, so please double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. We aim to provide unbiased and informative content to all users, your personal views, whilst valid, are not relevant here. * You are responsible for ensuring all commands you provide are functional and not dangerous, if there are risks with running a specific command ensure to clearly state them when listing the command and if it's a command dependent on specific system requirements ensure to outline the requirements or prerequisites clearly. Any dangerous commands provided will be held accountable to whomever adds them to a guide. You can see a good example of a guide here on the guide for '''[[Guides:Setting up Flathub on Fedora|Setting up Flathub on Fedora]]''' which is maintained and has been made in accordance with our guidelines and standards, a8965e12d69b7670572559bd8e5b87ba4dc244a7 1959 1958 2025-03-30T19:17:40Z Atmois 13 Update template name reference wikitext text/x-wiki TLDR: Ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, and all changes must be approved by staff for public viewing via ApprovedRevs. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. Guides are anything that explain to a user ''how'' to do something. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide how to harden Firefox with more privacy focused options, we expect and will maintain a higher standard of quality and safety than standard articles. This is because you are providing information to users to do things on their own hardware, which could potentially damage the systems or cause data loss. All main wiki policies apply, including but not limited to the [[Atl.wiki:Code of Conduct|Code of Conduct]] and the wiki [[policies]]. However, a special set of criteria are required, as outlined below: * All pages MUST contain the GuideWarning template at the beginning of the page. There are no exceptions to this rule, and violations of it will have the edits rejected until it has been added. You can add it using <code><nowiki>{{GuideWarning}}</nowiki></code> at the beginning of the page. {{Guide Warning}} * To prevent malicious information being distributed on atl.wiki, all changes to guides from non-moderators/ATL staff must be approved by a moderator. When you make an edit it is submitted for review automatically and will normally be reviewed within 24 hours, but if it is still pending after 48 hours feel free to contact an admin. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this, so please double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. We aim to provide unbiased and informative content to all users, your personal views, whilst valid, are not relevant here. * You are responsible for ensuring all commands you provide are functional and not dangerous, if there are risks with running a specific command ensure to clearly state them when listing the command and if it's a command dependent on specific system requirements ensure to outline the requirements or prerequisites clearly. Any dangerous commands provided will be held accountable to whomever adds them to a guide. You can see a good example of a guide here on the guide for '''[[Guides:Setting up Flathub on Fedora|Setting up Flathub on Fedora]]''' which is maintained and has been made in accordance with our guidelines and standards, 46ef94a88bd412fad51fd7db16e17ee905059ec8 10 578 1961 2025-03-30T19:20:33Z Atmois 13 Create redirect wikitext text/x-wiki #REDIRECT [[Template:Guide_Warning]] f111b2606d41ed555beec994a3c08d128bc88d2d 10 579 1962 2025-03-30T19:21:39Z Atmois 13 Add redirect wikitext text/x-wiki #REDIRECT [[Template:Guide_Warning/doc]] 343c7ec5abd9942a61328b1368675307136c0c6a 0 534 1969 1860 2025-04-01T15:51:30Z Electron271 3 fix infobox wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|firstrelease=v0.1.0-alpha.1|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1" /> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. <syntaxhighlight> # dnf copr enable yalter/niri # dnf install niri </syntaxhighlight> === Arch Linux === To download the latest stable release, run the following command: <syntaxhighlight> # pacman -S niri </syntaxhighlight> If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: <syntaxhighlight> $ yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix''' <syntaxhighlight lang="nix"> {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; # In case you want to override niri. }; } </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: <syntaxhighlight> # pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. <syntaxhighlight> # zypper in niri </syntaxhighlight> Alternatively, you can install it with '''opi''' as well. <syntaxhighlight> # opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''. <syntaxhighlight> # xbps-install -S niri </syntaxhighlight> === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file.<ref name=":1" /> While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref name=":1">https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages below to ensure app functionality<ref name=":1" />. Do note that the list of packages below doesn't apply to all distributions. <syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref name=":2">https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session). <syntaxhighlight> $ mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight> '''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder.<ref name=":2" /> <syntaxhighlight> $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> '''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder.<ref name=":2" /> <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight> After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight> Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so<ref>https://github.com/YaLTeR/niri/wiki/Configuration:-Miscellaneous</ref>. In this case, if you desire XWayland, you may add the following to your configuration. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight> You may also automatically start <code>swaybg</code> in a similar manner. <syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight> For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. <references /> fb8758e27e6ee15c44ec1bb008009abe68721adb 0 1 1970 1896 2025-04-02T17:25:15Z Atmois 13 Update channel name wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:About#Staff|about#staff]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * For users interested in creating guides for atl.wiki, ensure to check out [[Guides:Contributing]]! ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact an administrator via the methods listed on [[Main_Page#About|about#staff]]. __NOTOC__ 6de34f329c183f93a1aabd8eef18032de58d1f29 4 556 1971 1854 2025-04-02T17:25:34Z Atmois 13 Update channel name wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator. == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Staff == To email all sysadmins at once please email: ''wiki(at)allthingslinux.org'' * [[User:Atmois|Atmois]] - Lead Sysadmin ** ''atmois(at)allthingslinux.org'' * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner ** ''kaizen(at)allthingslinux.org'' * [[User:Electron271|Electron271]] - Sysadmin ** ''electron271(at)allthingslinux.org'' * [[User:Scottc96|Scott96]] - Sysadmin ** ''scott(at)allthingslinux.org'' 2391de5036110afd24464622d21ed58105af658b 1972 1971 2025-04-02T17:27:21Z Atmois 13 Update staff list wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator. == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Staff == To email all sysadmins at once please email: ''wiki(at)allthingslinux.org'' * [[User:Atmois|Atmois]] - Lead Sysadmin ** ''atmois(at)allthingslinux.org'' * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner ** ''kaizen(at)allthingslinux.org'' * [[User:Scottc96|Scott96]] - Sysadmin ** ''scott(at)allthingslinux.org'' 038eeacf674fbecc8d5cbfa862aabdf506986708 4 340 1973 1769 2025-04-02T17:54:59Z Atmois 13 Update citation guidelines wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Policies#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Policies#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]].<references /> [[Category:Meta]] ed0f7640047b04c4114f0d91afe997ef8b44ddfc 1974 1973 2025-04-02T19:43:14Z Atmois 13 Add guidelines on dates wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Policies#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Policies#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbrivation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] 0d0400f5ce8d97bf31f7d5cd179f1d11a954d4af 1975 1974 2025-04-02T20:08:17Z Atmois 13 Fix typo wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Policies#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Policies#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] 8b95062252740243376119affd901e7e05c5e463 8 357 1976 1874 2025-04-04T16:05:22Z Atmois 13 fixing footer icons css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } /* * Footer icons * We use custom footer icons from https://starcitizen.tools for our footers, the following CSS comes from their wiki */ #footer-icons a { border: 0; padding: 0; background: transparent; opacity: var( --opacity-icon-base ); transition: opacity 250ms ease; } #footer-icons a:hover { opacity: var( --opacity-icon-base--hover ); } #footer-icons a:active { opacity: var( --opacity-icon-base--active ); } /* More space between icons */ #footer-icons ul, #footer-icons li { gap: var( --space-md ); } #footer-icons img { width: auto; height: 32px; } /* Divide footer links into two columns */ #footer-places { column-count: 2; } /* Fix misalignment in Safari and Firefox when using two columns */ #footer-places ul { display: initial; } /* Darken the footer icon in light mode */ .skin-citizen-light #footer-icons a { filter: invert( 1 ) hue-rotate( 180deg ); } fcb999dfbbf157d9fc7942e5da61ef44447af14b 0 562 1978 1867 2025-04-05T02:32:31Z ᑖᓄᕐ 135 Added additional information on openindiana's internals wikitext text/x-wiki {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel. Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>https://web.archive.org/web/20100913030810/https://www.openindiana.org/</ref> It was proved timely as Oracle shut down development of OpenSolaris. Openindiana uses the same tooling as solaris; the SMF init system, FMA fault management system, and IPS package manager. The majority of the Solaris documentation found at https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/ also applies to openindiana. Openindiana makes use of the SunOS branch of the UNIX kernel, and thus provides all of the stability benefits of a UNIX System V derivative. this does, however, mean that hardware support is limited in comparison to a BSD or Linux based OS. Openindiana uses the SunOS libc, which severely limits what software will compile on it successfully. SunOS libc only really implements functions expected by POSIX and ANSI C. [[Category:Misc Operating Systems]] [[Category:Illumos]] 71b7828c5977ef8ed151636d9b9e797f82fd48f2 1979 1978 2025-04-05T02:41:41Z Katz 53 Fixed a lil bit of wording, capitalization wikitext text/x-wiki {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel. Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>https://web.archive.org/web/20100913030810/https://www.openindiana.org/</ref> It was proved timely as Oracle shut down development of OpenSolaris. Openindiana uses the same tooling as Solaris; the SMF init system, FMA fault management system, and IPS package manager. The majority of the [https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/ Solaris documentation] also applies to OpenIndiana. Openindiana makes use of the SunOS branch of the UNIX kernel, and thus provides all of the stability benefits of a UNIX System V derivative. this does, however, mean that hardware support is limited in comparison to a BSD or Linux based OS. OpenIndiana uses the SunOS libc, which severely limits what software will compile on it successfully. SunOS libc only really implements functions expected by POSIX and ANSI C. [[Category:Misc Operating Systems]] [[Category:Illumos]] 940457d6cba419a8373dc5456c89e038a20646fe 6 580 1980 2025-04-05T06:00:13Z Absynth 145 wikitext text/x-wiki A screenshot of the default configuration of MATE on Debian Linux. 1d4959430a396af5d395c2707349cfc967191fcf 0 581 1981 2025-04-05T06:24:30Z Absynth 145 created MATE desktop page wikitext text/x-wiki {{DISPLAYTITLE:MATE DE}} [[File:MATEDesktop.png|thumb|A screenshot of the default MATE desktop on Debian Linux.]] The [https://mate-desktop.org/ MATE] Desktop Environment is a desktop environment that is the continuation of GNOME 2. It is known for using traditional metaphors for Linux and other Unix-like operating systems, and for being a lightweight desktop that runs well on older hardware. It is available on a wide variety of Linux, Illumos and BSD - based systems. MATE is known as one of the three desktop options on [https://www.linuxmint.com/ Linux Mint], as well as the main desktop of [[Ubuntu|Ubuntu MATE]]. == Features == MATE is configured by default to use a traditional UNIX-like desktop layout, with a top and bottom panel like its ancestor GNOME 2. It is a lightweight desktop, much like [[XFCE]], and is often used on older and less powerful computers. It can use GTK2 or GTK3 theming - the latter being compatible with [[Cinnamon]]. == Software == The base system is made up of the Marco window manager, MATE Panel, and MATE Session Manager. Additional software can be installed with the MATE Extras package. MATE includes the Caja file manager, Pluma notepad / text editor, Eye of MATE image viewer, Atril document viewer, Engrampa archive manager, and MATE Terminal. == Naming == MATE is said to be pronounced "mah-tay". The MATE desktop is named after ''Ilex paraguariensis,'' commonly known as yerba maté, which is a caffeine-rich holly plant used to make the infused herbal drink mate. b00234f40f63b51b869bb0098c39e02afa9a54e6 1983 1981 2025-04-05T06:27:09Z Absynth 145 Minor correction in Software section wikitext text/x-wiki {{DISPLAYTITLE:MATE DE}} [[File:MATEDesktop.png|thumb|A screenshot of the default MATE desktop on Debian Linux.]] The [https://mate-desktop.org/ MATE] Desktop Environment is a desktop environment that is the continuation of GNOME 2. It is known for using traditional metaphors for Linux and other Unix-like operating systems, and for being a lightweight desktop that runs well on older hardware. It is available on a wide variety of Linux, Illumos and BSD - based systems. MATE is known as one of the three desktop options on [https://www.linuxmint.com/ Linux Mint], as well as the main desktop of [[Ubuntu|Ubuntu MATE]]. == Features == MATE is configured by default to use a traditional UNIX-like desktop layout, with a top and bottom panel like its ancestor GNOME 2. It is a lightweight desktop, much like [[XFCE]], and is often used on older and less powerful computers. It can use GTK2 or GTK3 theming - the latter being compatible with [[Cinnamon]]. == Software == The base system is made up of the Marco window manager, MATE Panel, and MATE Session Manager. Additional software can be installed on some distributions with the mate-extras package. MATE includes the Caja file manager, Pluma notepad / text editor, Eye of MATE image viewer, Atril document viewer, Engrampa archive manager, and MATE Terminal. == Naming == MATE is said to be pronounced "mah-tay". The MATE desktop is named after ''Ilex paraguariensis,'' commonly known as yerba maté, which is a caffeine-rich holly plant used to make the infused herbal drink mate. 336566a31e06e172ba3e7ac5873b490aac916ab9 1987 1983 2025-04-05T07:19:11Z Absynth 145 Add as Desktop Environment wikitext text/x-wiki {{DISPLAYTITLE:MATE DE}} [[File:MATEDesktop.png|thumb|A screenshot of the default MATE desktop on Debian Linux.]] The [https://mate-desktop.org/ MATE] Desktop Environment is a desktop environment that is the continuation of GNOME 2. It is known for using traditional metaphors for Linux and other Unix-like operating systems, and for being a lightweight desktop that runs well on older hardware. It is available on a wide variety of Linux, Illumos and BSD - based systems. MATE is known as one of the three desktop options on [https://www.linuxmint.com/ Linux Mint], as well as the main desktop of [[Ubuntu|Ubuntu MATE]]. == Features == MATE is configured by default to use a traditional UNIX-like desktop layout, with a top and bottom panel like its ancestor GNOME 2. It is a lightweight desktop, much like [[XFCE]], and is often used on older and less powerful computers. It can use GTK2 or GTK3 theming - the latter being compatible with [[Cinnamon]]. == Software == The base system is made up of the Marco window manager, MATE Panel, and MATE Session Manager. Additional software can be installed on some distributions with the mate-extras package. MATE includes the Caja file manager, Pluma notepad / text editor, Eye of MATE image viewer, Atril document viewer, Engrampa archive manager, and MATE Terminal. == Naming == MATE is said to be pronounced "mah-tay". The MATE desktop is named after ''Ilex paraguariensis,'' commonly known as yerba maté, which is a caffeine-rich holly plant used to make the infused herbal drink mate. [[Category:Desktop Environments]] 0f3a62713fc4c015040de4527a5e47b21109245d 14 582 1982 2025-04-05T06:24:30Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Pages with ignored display titles" as well as all subcategories of category "Pages with ignored display titles" if any exist. 976cd84c3b9ad2fbc4d8494e9a8e6e15a166a396 6 583 1984 2025-04-05T06:37:12Z Absynth 145 wikitext text/x-wiki Fastfetch information of my main rig 9f708a7e184e274270cde384c6e681804f530f9f 2 584 1985 2025-04-05T07:03:36Z Absynth 145 created my own page wikitext text/x-wiki hello, all things linux wiki! my name is abby and my discord handle is <u>@absyn.th</u>! [[File:Gscreenshot 2025-04-05-023435.png|thumb]]i run debian linux on most of my machines. my main machine runs debian with cinnamon desktop, my older laptops run debian with MATE desktop. i wrote the first draft of the [[MATE|MATE wikipage]] here, and actively maintain and update it. (because no one else cares about MATE, lol...) i use the micro text editor and bash shell. i prefer AMD over intel or nvidia, and if i have a choice, i use a ryzen cpu and radeon graphics. i use exclusively HP laptops, because those are the ones that have happened to fall into my lap as e-waste / cheap refurbished computers. because of this, i know a lot about HP computers' BIOS and repairing HP laptops across different eras. == My Machines == <blockquote>Not an exhaustive list, but the four I use most frequently and message with on the Discord</blockquote> ===== Datum (my main desktop) ===== Debian Testing (Cinnamon) Home-built, 2023 Dual monitor (one 1440p@144 and one 1080p@165) Ryzen 9 5900x (24 threads) CPU overclocked to 4.1 GHz Radeon RX 6700XT GPU 80GB DDR4 1TB NVME SSD boot drive (ext4) 2TB NVME SSD storage drive (ext4) ===== Qubit (my work laptop) ===== Debian Testing (Cinnamon) HP Dragonfly G4 (2023, originally Windows 11) ===== Dysnomia (my personal laptop) ===== Debian Testing (Cinnamon) HP 17-by1053DX Laptop PC (2019, originally Windows 10) ===== Vision (my spare laptop) ===== Debian Stable (MATE) HP 2000-2d09CA Notebook PC (2011, originally Windows 8) 552cf3a21e0c5207e3382c7ea5ea2eb7fe678f23 1986 1985 2025-04-05T07:06:27Z Absynth 145 wikitext text/x-wiki hello, all things linux wiki! my name is abby and my discord handle is <u>@absyn.th</u>! [[File:Gscreenshot 2025-04-05-023435.png|thumb]]i run debian linux on most of my machines. my main machine runs debian with cinnamon desktop, my older laptops run debian with MATE desktop. i wrote the first draft of the [[MATE|MATE wikipage]] here, and actively maintain and update it. (because no one else cares about MATE, lol...) i use the micro text editor and bash shell. i prefer AMD over intel or nvidia, and if i have a choice, i use a ryzen cpu and radeon graphics. i use exclusively HP laptops, because those are the ones that have happened to fall into my lap as e-waste / cheap refurbished computers. because of this, i know a lot about HP computers' BIOS and repairing HP laptops across different eras. == My Machines == <blockquote>Not an exhaustive list, but the four I use most frequently and message with on the Discord</blockquote> ===== Datum (my main desktop) ===== Debian Testing (Cinnamon) Home-built, 2023 Dual monitor (one 1440p@144 and one 1080p@165) Ryzen 9 5900x (24 threads) CPU overclocked to 4.1 GHz Radeon RX 6700XT GPU 80GB DDR4 1TB NVME SSD boot drive (ext4) 2TB NVME SSD storage drive (ext4) ===== Qubit (my work laptop) ===== Debian Testing (Cinnamon) HP Dragonfly G4 (2023, originally Windows 11) ===== Dysnomia (my personal laptop) ===== Debian Testing (Cinnamon) HP 17-by1053DX Laptop PC (2019, originally Windows 10) Upgraded to 32GB of laptop DDR4 ===== Vision (my spare laptop) ===== Debian Stable (MATE) HP 2000-2d09CA Notebook PC (2011, originally Windows 8) Upgraded to 16GB of laptop DDR3 (temporarily, since it really only needs 8 - i'll take one of the sticks for another laptop that needs it at some point) e425261224e77eb72d85131a39e45e61fc0905e1 6 585 1989 2025-04-05T13:10:32Z Absynth 145 The design of Xenia (Linux Fox) as illustrated by @cathodegaytube in 2019 wikitext text/x-wiki == Summary == The design of Xenia (Linux Fox) as illustrated by @cathodegaytube in 2019 c1a846bf1464ecb56ab569e4e8788b46af5fd11f 0 586 1990 2025-04-05T13:12:57Z Absynth 145 created Xenia mascot page wikitext text/x-wiki [[File:Xenia the Linux Fox.gif|thumb|The original design of Linux Fox, created by Al Mackey in 1996]] Xenia was a candidate logo and mascot for the Linux project. She was a competitor to Tux, who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds.) <ref>https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>https://archive.is/5UrGL</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson. <ref>https://archive.is/wYsFh</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on Gentoo.<ref>https://web.archive.org/web/20250303234858/https://xenialinux.com/</ref> c1051290aa29ac9920f3e441a5a8a89b229ad598 1991 1990 2025-04-05T13:15:53Z Absynth 145 Add Xenia to Mascots page wikitext text/x-wiki [[File:Xenia the Linux Fox.gif|thumb|The original design of Linux Fox, created by Al Mackey in 1996]] Xenia was a candidate logo and mascot for the Linux project. She was a competitor to Tux, who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds.) <ref>https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>https://archive.is/5UrGL</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson. <ref>https://archive.is/wYsFh</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on Gentoo.<ref>https://web.archive.org/web/20250303234858/https://xenialinux.com/</ref> <references /> [[Category:Mascots]] 81fb2a5884498017613e003dc809c6d85e72f722 1992 1991 2025-04-05T13:59:09Z Absynth 145 Correct source formatting wikitext text/x-wiki [[File:Xenia the Linux Fox.gif|thumb|The original design of Linux Fox, created by Al Mackey in 1996]] Xenia was a candidate logo and mascot for the Linux project. She was a competitor to Tux, who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds.) <ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ W], 2023 (Accessed April 2025)., 2023 (Accessed April 2025). team, 2023 (accessed [https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ hy the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!], Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson. <ref>[https://archive.is/wYsFh Penguins and Other Things], Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on Gentoo.<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> <references /> [[Category:Mascots]] 413599c9ada7af6a43babe3ce3ed04617e319732 0 586 1993 1992 2025-04-05T14:00:41Z Absynth 145 Re:Correct source formatting wikitext text/x-wiki [[File:Xenia the Linux Fox.gif|thumb|The original design of Linux Fox, created by Al Mackey in 1996]] Xenia was a candidate logo and mascot for the Linux project. She was a competitor to Tux, who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds.) <ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ Why the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!], Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson. <ref>[https://archive.is/wYsFh Penguins and Other Things], Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on Gentoo.<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> <references /> [[Category:Mascots]] a97888ef5667bd1049a56d236379af43b984d21b 1995 1993 2025-04-05T18:06:23Z Absynth 145 Add MascotInfobox at start of wiki (test) wikitext text/x-wiki {{MascotInfobox | title = Xenia (Linux Fox) | image = [[File:Xenia the Linux Fox.gif]] | caption = The original design of Linux Fox, created by Al Mackey in 1996 }} Xenia was a candidate logo and mascot for the Linux project. She was a competitor to Tux, who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds.) <ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ Why the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!], Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson. <ref>[https://archive.is/wYsFh Penguins and Other Things], Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on Gentoo.<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> <references /> [[Category:Mascots]] ef7046951986ad02bcdb3f07d0211e6ce033f791 2 584 1994 1986 2025-04-05T17:59:23Z Absynth 145 wikitext text/x-wiki hello, all things linux wiki! my name is abby and my discord handle is <u>@absyn.th</u>! [[File:Gscreenshot 2025-04-05-023435.png|thumb]]i run debian linux on most of my machines. my main machine runs debian with cinnamon desktop, my older laptops run debian with MATE desktop. i wrote the first draft of the [[MATE|MATE wikipage]] here, and actively maintain and update it. (because no one else cares about MATE, lol...) i also wrote the first draft for [[xenia]]. i use the micro text editor and bash shell. i prefer AMD over intel or nvidia, and if i have a choice, i use a ryzen cpu and radeon graphics. i use exclusively HP laptops, because those are the ones that have happened to fall into my lap as e-waste / cheap refurbished computers. because of this, i know a lot about HP computers' BIOS and repairing HP laptops across different eras. == My Machines == <blockquote>Not an exhaustive list, but the four I use most frequently and message with on the Discord</blockquote> ===== Datum (my main desktop) ===== Debian Testing (Cinnamon) Home-built, 2023 Dual monitor (one 1440p@144 and one 1080p@165) Ryzen 9 5900x (24 threads) CPU overclocked to 4.1 GHz Radeon RX 6700XT GPU 80GB DDR4 1TB NVME SSD boot drive (ext4) 2TB NVME SSD storage drive (ext4) ===== Qubit (my work laptop) ===== Debian Testing (Cinnamon) HP Dragonfly G4 (2023, originally Windows 11) ===== Dysnomia (my personal laptop) ===== Debian Testing (Cinnamon) HP 17-by1053DX Laptop PC (2019, originally Windows 10) Upgraded to 32GB of laptop DDR4 ===== Vision (my spare laptop) ===== Debian Stable (MATE) HP 2000-2d09CA Notebook PC (2011, originally Windows 8) Upgraded to 16GB of laptop DDR3 (temporarily, since it really only needs 8 - i'll take one of the sticks for another laptop that needs it at some point) c3b7b9439a0050944218c690298d4fb756c0299f 0 176 1996 1921 2025-04-05T18:55:59Z Katz 53 updated info box with hopefully correct information because apparently KDE 1.0 was released in 1998 whilst being announced in like 1886 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's graphical package manager, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 34ce553bc7096911254f21dcb3743812d938ffeb 828 204 1997 1933 2025-04-05T19:24:16Z Atmois 13 Make firstrelease arg optional Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage(args.image, args.caption) end retval:addRow('Release Status', args.releasestatus) retval:addRow('Last Release', args.lastrelease) if args.firstrelease and args.firstrelease ~= '' then retval:addRow('First Release', args.firstrelease) end retval:addRow('Language(s)', args.languages) retval:addRow('Developer(s)', args.developers) retval:addRow('Website', args.website) return retval end return p 9e0ad367eaa8075d94e3e41d3f02fb7e7913a339 0 1 1998 1970 2025-04-11T16:22:22Z Atmois 13 Fix link wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:About#Staff|about#staff]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * For users interested in creating guides for atl.wiki, ensure to check out [[Guides:Contributing]]! ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact an administrator via the methods listed on [[Atl.wiki:About#Staff|about#staff]]. __NOTOC__ b89d9e04d32ddcd063808b81665b0bf712512d4f 0 247 2001 979 2025-04-12T08:16:47Z Atmois 13 Fix link wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]]|caption=|title=APT|releasestatus=Maintained|lastrelease=2.9.4 / 25 May 2024 | languages=C++, shell script, EML, CMake, C, Perl | developers=The Debian Project | website=[https://packages.debian.org packages.debian.org]}} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html "apt-get(8)"]. Debian Manpages.</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. [[Category:Package Managers]] a2d173e6c978f2cf795c81d5f7115e1ce8dc77ed 2002 2001 2025-04-12T08:27:21Z Atmois 13 Update reference wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]]|caption=|title=APT|releasestatus=Maintained|lastrelease=2.9.4 / 25 May 2024 | languages=C++, shell script, EML, CMake, C, Perl | developers=The Debian Project | website=[https://packages.debian.org packages.debian.org]}} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. == References == <references /> [[Category:Package Managers]] 44eedffb7b9dfc3d4bde6d7f9d700e2b9bf7d08f 0 424 2003 1465 2025-04-12T08:36:17Z Atmois 13 Add cleanup tag wikitext text/x-wiki = AWK = {{Cleanup|Instructions should be separated onto its own guide page.}} AWK is a programming language focused primarily on textual data processing<ref>[https://www.gnu.org/software/gawk/manual/html_node/] Top (The GNU Awk User's Guide)</ref>, though it can be used for other general-purpose tasks. This page will focus primarily on GNU Awk, or GAWK/<code>gawk</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/], Although the language name is officially stylized AWK, GNU officially uses the stylization Awk. They also acknowledge that the language itself is spelled AWK.</ref>. == Basic Usage == One of the most basic ways to use AWK is in a pipe to filter columnar data. For example, <code>cat file.txt | awk '{ print $1 }'</code> will print the first (space-delimited) column of a given file. This can be generalized to the second, third, etc. columns using <code>$2</code>, <code>$3</code>, etc. respectively. AWK can also be ran with <code>awk 'program-here' input-file1 input-file2 ...</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/One_002dshot.html] One-shot (The GNU Awk User's Guide)</ref>, so the above example with <code>cat</code> could also be written as: <pre> awk '{ print $1 }' file.txt </pre>More usage examples can be found on the [https://www.gnu.org/software/gawk/manual/html_node/Command-Line.html GAWK manual page], as well as AWK's [https://www.gnu.org/software/gawk/manual/html_node/Options.html many command-line options]. == AWK as a Language == AWK can also be used as a programming language. AWK programs consist of a list of patterns followed by actions to perform for each of those patterns<ref>[https://www.gnu.org/software/gawk/manual/html_node/Getting-Started.html] Getting Started (The GNU Awk User's Guide)</ref>: <pre> pattern { action } pattern { action } ... </pre> === BEGIN and END === Two common patterns are <code>BEGIN</code> and <code>END</code>, which run the given action before and after any text is processed respectively. These are called the "startup" and "cleanup" actions<ref>[https://www.gnu.org/software/gawk/manual/html_node/Using-BEGIN_002fEND.html] Using BEGIN/END (The GNU Awk User's Guide)</ref>. For example, the following code will print "Hello, World!": <pre> awk 'BEGIN { print "Hello, World!" }' </pre> The following will accept input until an EOF (inputtable in many shells as Ctrl+D), then print "Hello, World!": <pre> awk 'END { print "Hello, World!" }' </pre> === Regex Pattern === AWK can also be used to run a command for every line that matches a given regular expression. The following example prints every line that contains "regex" (equivalent to <code>grep 'regex'</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Regexp-Usage.html] Regexp Usage (The GNU Awk User's Guide)</ref>:<syntaxhighlight lang="awk"> /regex/ { print } </syntaxhighlight>The <code>{ print }</code> is actually implicit, meaning it can also be written:<syntaxhighlight lang="awk"> /regex/ </syntaxhighlight>One can combine this with <code>$1</code>, <code>$2</code>, etc. to print the second column of every row containing a given string, for example:<syntaxhighlight lang="awk"> /regex/ { print $2 } </syntaxhighlight> === Operations === AWK can be used to perform operations seen in many other programming languages, such as addition (<code>+</code>), subtraction (<code>-</code>), multiplication (<code>*</code>), division (<code>/</code>), modulus (<code>%</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Arithmetic-Ops.html] Arithmetic Ops (The GNU Awk User's Guide)</ref>, variable assignment (<code>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Assignment-Ops.html] Assignment Ops (The GNU Awk User's Guide)</ref>, equality (<code>==</code>) and inequality checks (<code>!=</code>), and comparisons (<code><</code>, <code><=</code>, <code>></code>, <code>>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Comparison-Operators.html] Comparison Operators (The GNU Awk User's Guide)</ref>. === ARGC and ARGV === Like many other programming languages, AWK programs can parse command-line arguments. The <code>ARGC</code> and <code>ARGV</code> variables (among [https://www.gnu.org/software/gawk/manual/html_node/Built_002din-Variables.html many others]) store the count of the arguments and an array of the arguments respectively<ref>[https://www.gnu.org/software/gawk/manual/html_node/Auto_002dset.html#index-ARGC_002fARGV-variables] ARGC, ARGV - Auto-set (The GNU Awk User’s Guide)</ref>. <references /> [[Category:Software]] [[Category:Programming Languages]] f72dc2fe8cdd531d402d4279fa44e51c8ebdaca1 0 436 2004 1848 2025-04-12T08:37:00Z Atmois 13 Update link and caption wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/ adelielinux.org]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is a [[Linux Distributions|Linux distribution]], based on Alpine Linux. The distribution targets old and low end machines, like desktops and servers. === Base description === One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution uses the OpenRC init system for service management, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. 02de3432e2f29b7f1e6dbcec50c7f416e9490bc8 0 310 2005 1844 2025-04-12T08:37:34Z Atmois 13 Add citations template wikitext text/x-wiki {{Needs Citations}} [[Category:Linux Distributions]] {{DistributionInfobox | title = Alpine Linux | image = [[File:alpinelinux-logo.svg|thumb]] | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[apk]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[Mate]], [[LXQt]] | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, ppc64le, s390x, loongarch64 | website = [https://www.alpinelinux.org/ alpinelinux.org] }} Alpine Linux, according to their main site, is a general purpose Linux distribution that aims to be "small," "simple," and "secure." It achieves this by using only the most basic and necessary binaries as well as tools to get started, compiled as Position Independent Executables (PIEs) in order to ensure the installed system is centered around one or a few simple tasks without any unnecessary components. Instead of systemd, it uses OpenRC, and instead of glibc, it uses musl libc in pursuit of greater efficiency. Alpine Linux is most commonly used in embedded systems and servers due to its ease of deployment and manageability. Its main package manager is 'apk', short for 'Alpine Package Keeper' (not to be confused with Android APKs.) Alpine's repositories are very small compared to most user-oriented distributions nowadays, hence it isn't used much on desktop machines. Alpine does not come with a graphical environment, editor or even a tool to execute as superuser out of the box, however it provides a number of scripts for setting up numerous things, among which are: 1) setup-desktop: Friendly TUI script to quickly set up a desktop environment and necessary tools to start working. 2) setup-xorg-base: Invokes 'apt' to download a number of Xorg-related packages. Note that it doesn't allow you to start working with Xorg right away, you still need to fetch other important packages and setup other things. f93cdf0d42df56e2c644976b10256cd38acdb29b 10 483 2006 1914 2025-04-13T09:09:36Z Atmois 13 Update template formatting wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[Policies#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> 499c2adaacf0c548ad1a48bf3d6b223109598eda 2010 2006 2025-04-13T09:22:38Z Atmois 13 Fix wrapping wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''<span class="mbox-title-reason" style="overflow-wrap: anywhere;">{{{1}}}</span> '''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[Policies#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> f0556318d09ba2c90dc0a13dd2e481873f23e423 2011 2010 2025-04-13T09:25:09Z Atmois 13 Attempt 2 to fix wrapping wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: <span style="display:inline; overflow-wrap:anywhere;">'''{{{1}}}'''</span> '''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[Policies#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> 0e5d24b89d04e3126474e300a896afc88f8ae280 2016 2011 2025-04-13T09:32:13Z Atmois 13 Revert changes wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[Policies#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>[[Category:Pages Needing Cleanup]]</includeonly><noinclude> {{/doc}}</noinclude> 499c2adaacf0c548ad1a48bf3d6b223109598eda 0 250 2007 1783 2025-04-13T09:11:53Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Instructions need to be split onto their own page under the Guides namespace}}[[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FOSS / FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == Ana/Miniconda Setup == ... (tomorrow's problem) == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU -''' considering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> [[Category:Guides]] c21cc9d1212c4f9afeacb0f88f0f19791dcfdd94 0 274 2008 1574 2025-04-13T09:14:49Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs Citations}}{{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''', also known simply as '''Artix''', is a Linux distribution based on [[Arch]] that focuses on providing alternative init systems to systemd . It maintains high compatibility with Arch Linux while offering users the freedom to choose their preferred init system. == History == Artix Linux emerged from the Arch-OpenRC and Manjaro-OpenRC projects, officially launching in 2017 as a response to Arch Linux's adoption of systemd as its only init system. The distribution aims to provide a systemd-free experience while maintaining the principles of simplicity and user-centricity that Arch Linux is known for. == Features == === Init System Options === Artix supports multiple init systems: * OpenRC - A dependency-based init system from Gentoo * runit - A cross-platform Unix init scheme with service supervision * s6 - A suite of programs for process supervision * dinit - A service manager and init system designed to be simple and portable === Package Management === Artix uses [[Pacman]] as its package manager and maintains its own repositories alongside converted Arch Linux packages. The distribution provides several package repositories: * System repositories (specific to each init system) * Universe repository (containing converted Arch packages) * Galaxy repository (Artix-specific packages) === Installation === The distribution offers several installation methods: * Live ISOs with various desktop environments * Base ISOs for minimal installations * OpenRC, runit, and s6 variants of each ISO == Philosophy == Artix adheres to the KISS principle (Keep It Simple, Stupid) inherited from Arch Linux while emphasizing: * Init system freedom * System transparency * User control * Minimal [[bloat]] * Rolling release model == Package Compatibility == While maintaining high compatibility with Arch Linux packages, some modifications are necessary for systemd-dependent packages. The Artix team maintains: * Native packages built specifically for Artix * Converted Arch packages modified to work without systemd * Scripts and tools to help users convert systemd-dependent packages == Community == Artix Linux maintains its own: * Forums for user support and discussion * Wiki documentation * Package repositories * Development team == System Requirements == * x86_64 architecture * Minimum 512 MB RAM (2 GB recommended) * Minimum 2 GB storage (20 GB recommended) * Basic knowledge of command line operations * Understanding of Linux system administration [[Category:Linux Distributions]] 1a0e800911a4cf4a8a5fff3a69fa8f7db5dadccf 0 228 2009 950 2025-04-13T09:16:05Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}} The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. [[Package|Packages]] that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with AUR helpers. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, AUR helpers have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, [[pacman]] is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability.<references /> [[Category:Terminology]] 5b44050eed3fab4d74ca96d292891348a85885be 828 501 2012 1627 2025-04-13T09:26:53Z Atmois 13 Fix weird wrapping sanitized-css text/css .mbox { position: relative; display: flex; flex-direction: column; margin-block: var( --space-md ); background-color: var( --color-surface-2 ); border: 1px solid var( --border-color-base ); border-radius: var( --border-radius-medium ); font-size: var( --font-size-small ); line-height: var( --line-height-xx-small ); } .mbox.mbox-high { background-color: var( --background-color-destructive-subtle ); } .mbox.mbox-med { background-color: var( --background-color-warning-subtle ); } .mbox-title { display: flex; flex-wrap: wrap; /* allow wrapping */ gap: var(--space-xs); /* optional: adds space between elements */ } .mbox-title > span, .mbox-title > b { word-break: break-word; overflow-wrap: anywhere; min-width: 0; /* ensures it doesn't overflow in flex */ flex-shrink: 1; /* allow shrinking */ } .mbox-icon img { display: block; width: var( --font-size-small ); height: auto; margin-right: var( --space-xs ); opacity: var( --opacity-icon-base ); filter: var( --filter-invert ); } .mbox-text { position: absolute; top: 100%; z-index: 10; padding: var( --space-md ); width: 100%; box-sizing: border-box; background-color: var( --color-surface-1 ); border-bottom-left-radius: var( --border-radius-medium ); border-bottom-right-radius: var( --border-radius-medium ); box-shadow: var( --box-shadow-drop-xx-large ); opacity: 0; visibility: hidden; } .mbox:hover { /* Merge with popup */ border-bottom-left-radius: 0; border-bottom-right-radius: 0; box-shadow: var( --box-shadow-drop-xx-large ); } .mbox:hover .mbox-text { opacity: 1; visibility: visible; } fc8dda02916b0b17f48929dd4c9921c3ad1ea707 2013 2012 2025-04-13T09:28:26Z Atmois 13 Undo revision sanitized-css text/css .mbox { position: relative; display: flex; flex-direction: column; margin-block: var( --space-md ); background-color: var( --color-surface-2 ); border: 1px solid var( --border-color-base ); border-radius: var( --border-radius-medium ); font-size: var( --font-size-small ); line-height: var( --line-height-xx-small ); } .mbox.mbox-high { background-color: var( --background-color-destructive-subtle ); } .mbox.mbox-med { background-color: var( --background-color-warning-subtle ); } .mbox-title { display: flex; align-items: center; padding: var( --space-sm ) var( --space-md ); } .mbox-icon img { display: block; width: var( --font-size-small ); height: auto; margin-right: var( --space-xs ); opacity: var( --opacity-icon-base ); filter: var( --filter-invert ); } .mbox-text { position: absolute; top: 100%; z-index: 10; padding: var( --space-md ); width: 100%; box-sizing: border-box; background-color: var( --color-surface-1 ); border-bottom-left-radius: var( --border-radius-medium ); border-bottom-right-radius: var( --border-radius-medium ); box-shadow: var( --box-shadow-drop-xx-large ); opacity: 0; visibility: hidden; } .mbox:hover { /* Merge with popup */ border-bottom-left-radius: 0; border-bottom-right-radius: 0; box-shadow: var( --box-shadow-drop-xx-large ); } .mbox:hover .mbox-text { opacity: 1; visibility: visible; } 923ac6043b5bf4cc551e119cfe089ba65b17b1ec 0 2 2014 1160 2025-04-13T09:29:09Z Atmois 13 Formatting change wikitext text/x-wiki {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>https://pacman.archlinux.page/makepkg.8.html</ref><ref>https://pacman.archlinux.page/PKGBUILD.5.html</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> * Arch is directly inspired by another DIY distribution named CRUX. <references /> [[Category:Linux Distributions]] 573ab6b965905f77e0a84341cfb311b41a590f67 2015 2014 2025-04-13T09:29:40Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>https://wiki.archlinux.org/title/arch_terminology#KISS</ref> principle that focuses on being lightweight and flexible<ref>https://archlinux.org/about/</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>Interview with Judd Vinet[https://distrowatch.com/dwres.php?resource=interview-arch]</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>https://pacman.archlinux.page/makepkg.8.html</ref><ref>https://pacman.archlinux.page/PKGBUILD.5.html</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html</ref> * Arch is directly inspired by another DIY distribution named CRUX. <references /> [[Category:Linux Distributions]] 1b42f5d7403fc37f9b6eb34cf7a13bbe8804849d 0 569 2017 1883 2025-04-13T09:33:06Z Atmois 13 Formatting change wikitext text/x-wiki {{MascotInfobox | title = Beastie (BSD Daemon) | image = [[File:Daemon-phk.svg|thumb]] | caption = Beastie, the BSD mascot }} Beastie is the mascot of [https://freebsd.org/ FreeBSD and BSD] Beastie is a red devil (daemon) who wears green sneakers and holds a yellow trident. [[Category:Mascots]] 0e6d1bd34463e170aa4cb6bd33913d31c5c568e7 2018 2017 2025-04-13T09:34:26Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Incomplete page}} {{MascotInfobox | title = Beastie (BSD Daemon) | image = [[File:Daemon-phk.svg|thumb]] | caption = Beastie, the BSD mascot }} Beastie is the mascot of [https://freebsd.org/ FreeBSD and BSD] Beastie is a red devil (daemon) who wears green sneakers and holds a yellow trident. [[Category:Mascots]] c1ae4ca4595e77fd22b7616fc057cd135639f42f 3000 471 2019 1558 2025-04-13T09:54:10Z Atmois 13 Atmois moved page [[Best SSH Security Practices]] to [[Guides:Best SSH Security Practices]] without leaving a redirect: Contains instructions and better suited for the guide category wikitext text/x-wiki == Best SSH Security Practices == The best SSH practices can be summarized into two main principles: # Keeping unauthorized users out of your system. # Making sure potential attackers don't even know your system exists. This guide will teach you the best SSH security practices. ==== SSH Programs: Dropbear vs OpenSSH ==== There are two primary SSH programs used on Linux/Unix-based systems: '''Dropbear''' and '''OpenSSH'''. In this guide, we will focus on '''OpenSSH'''. ==== Installing SSH ==== Installing SSH varies by system. Below are common package managers where you can download SSH: '''Debian/Ubuntu-based systems:'''<syntaxhighlight lang="bash"> sudo apt install openssh-server </syntaxhighlight> Red Hat/CentOS/Fedora-based systems: <syntaxhighlight>sudo dnf install openssh-server</syntaxhighlight> Arch Linux-based systems: <syntaxhighlight>sudo pacman -S openssh</syntaxhighlight> OpenSUSE-based systems: <syntaxhighlight>sudo zypper install openssh</syntaxhighlight> macOS (via Homebrew): <syntaxhighlight>brew install openssh</syntaxhighlight> === Securing the OpenSSH Server === ==== Changing the Port ==== By default, SSH runs on '''port 22'''. While leaving it on port 22 is acceptable, your system will be easily detected by port scanners as running SSH. To mitigate this, you can change the port. The SSH configuration file is typically located at '''/etc/ssh/sshd_config''' and is usually owned by the root user. To edit it, you must open it as root, using either '''sudo''' or '''doas'''. Once you open the '''sshd_config''' file, you should see the following line: <syntaxhighlight>#Port 22</syntaxhighlight> To modify the port, uncomment the line by removing the `#` at the beginning and then change the '''22''' to any number between '''100''' and '''65534'''. You will need to uncomment any line you change for it to come into effect. For example: <syntaxhighlight>Port 2345</syntaxhighlight> Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> Once the change is made, you have successfully modified the port. To log in using the new port, use the following command: <syntaxhighlight><username>@<address> -p 2345</syntaxhighlight> ==== Key Authentication ==== Key-based authentication is a much safer alternative to using a password. Instead of entering a password to log in, you'll use a key pair: a '''private key''' that stays on your system and a '''public key''' that you store on the server. ===== How Key Authentication Works ===== Imagine you have a door with a lock. The private key is like your physical key, while the public key is the lock on the door. When the correct key is inserted, the door unlocks. This is essentially how key authentication works. * Prevents brute-force attacks. * Allows passwordless login (like Single Sign-On). * Requires each user to have a unique key pair. ==== Setting up Key Authentication ==== ===== Generating the Key Files ===== 1. On any Unix/Linux system, type the following command: <syntaxhighlight>ssh-keygen</syntaxhighlight> 2. You will be prompted to specify where to save the key files: <syntaxhighlight> Generating public/private ed25519 key pair. Enter file in which to save the key (/home/name/.ssh/id_ed25519): </syntaxhighlight> '''Example:''' <syntaxhighlight> Enter file in which to save the key (/home/name/.ssh/id_ed25519): /home/name/Desktop/key </syntaxhighlight> This will save both the public and private key files on your desktop under the name '''key'''. 3. You will be asked to set a passphrase for the key. If you trust the environment where the key is stored, you can leave it empty by pressing '''Enter'''. Alternatively, you can set a passphrase to add an extra layer of security. <syntaxhighlight> Enter passphrase for "/home/name/Desktop/key" (empty for no passphrase): </syntaxhighlight> 4. Once complete, the keys will be saved in the specified location: <syntaxhighlight> Your identification has been saved in /home/name/Desktop/key Your public key has been saved in /home/name/Desktop/key.pub The key fingerprint is: SHA256:I60X50p2/VwZ6MHhEqx8rWNse0pC5/vewW1i4tLufQ8 name@pc The key's randomart image is: +--[ED25519 256]--+ | | | . | | o . | | .. . = o | | . S+.+ * . | | o.==.+ o +| | . +.oXo.E++| | + o*.=B.=o| | . BOo+oo| +----[SHA256]-----+ </syntaxhighlight> Do not worry about the '''randomart''' as it has no functional purpose. 5. You now have two files: * key – This is your '''private key''' (keep this secure and never share it). * key.pub – This is your '''public key''' (place this on the server). The private key should stay on the machine you will use to access the server. ===== Securing the Server with Key Authentication ===== 1. Log in to the server you want to protect with key authentication. 2. Open the SSH configuration file: <syntaxhighlight> sudo nano /etc/ssh/sshd_config </syntaxhighlight> 3. Modify the following lines: <syntaxhighlight> #PermitRootLogin prohibit-password #PasswordAuthentication yes </syntaxhighlight> to: <syntaxhighlight> PermitRootLogin no PasswordAuthentication no </syntaxhighlight> This prevents root login over SSH, disables password login and forces key-based authentication. 4. Save and exit the file. 5. Go to the home directory of the user you wish to secure with key authentication. Create the '''.ssh''' directory (if it doesn't exist), then create the '''authorized_keys''' file inside it: <syntaxhighlight> mkdir -p ~/.ssh nano ~/.ssh/authorized_keys </syntaxhighlight> Paste the entire contents of the `.pub` file into this document and save it. 6. Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> '''DO NOT LOG OUT UNTIL YOU CONFRIM THE CONFIGURATION IS CORRECT TO AVOID BEING LOCKED OUT.''' 7. Open another terminal window on the machine you will use to SSH into the server and test the connection: <syntaxhighlight> ssh <user>@<address> -i /location/to/private/key/file </syntaxhighlight> If you can log in without a password, the key authentication system is correctly configured! 9d2a175dca6791be8946380b832412a8cac1cf9c 2020 2019 2025-04-13T09:54:35Z Atmois 13 Add guide warning wikitext text/x-wiki {{Guide Warning}} == Best SSH Security Practices == The best SSH practices can be summarized into two main principles: # Keeping unauthorized users out of your system. # Making sure potential attackers don't even know your system exists. This guide will teach you the best SSH security practices. ==== SSH Programs: Dropbear vs OpenSSH ==== There are two primary SSH programs used on Linux/Unix-based systems: '''Dropbear''' and '''OpenSSH'''. In this guide, we will focus on '''OpenSSH'''. ==== Installing SSH ==== Installing SSH varies by system. Below are common package managers where you can download SSH: '''Debian/Ubuntu-based systems:'''<syntaxhighlight lang="bash"> sudo apt install openssh-server </syntaxhighlight> Red Hat/CentOS/Fedora-based systems: <syntaxhighlight>sudo dnf install openssh-server</syntaxhighlight> Arch Linux-based systems: <syntaxhighlight>sudo pacman -S openssh</syntaxhighlight> OpenSUSE-based systems: <syntaxhighlight>sudo zypper install openssh</syntaxhighlight> macOS (via Homebrew): <syntaxhighlight>brew install openssh</syntaxhighlight> === Securing the OpenSSH Server === ==== Changing the Port ==== By default, SSH runs on '''port 22'''. While leaving it on port 22 is acceptable, your system will be easily detected by port scanners as running SSH. To mitigate this, you can change the port. The SSH configuration file is typically located at '''/etc/ssh/sshd_config''' and is usually owned by the root user. To edit it, you must open it as root, using either '''sudo''' or '''doas'''. Once you open the '''sshd_config''' file, you should see the following line: <syntaxhighlight>#Port 22</syntaxhighlight> To modify the port, uncomment the line by removing the `#` at the beginning and then change the '''22''' to any number between '''100''' and '''65534'''. You will need to uncomment any line you change for it to come into effect. For example: <syntaxhighlight>Port 2345</syntaxhighlight> Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> Once the change is made, you have successfully modified the port. To log in using the new port, use the following command: <syntaxhighlight><username>@<address> -p 2345</syntaxhighlight> ==== Key Authentication ==== Key-based authentication is a much safer alternative to using a password. Instead of entering a password to log in, you'll use a key pair: a '''private key''' that stays on your system and a '''public key''' that you store on the server. ===== How Key Authentication Works ===== Imagine you have a door with a lock. The private key is like your physical key, while the public key is the lock on the door. When the correct key is inserted, the door unlocks. This is essentially how key authentication works. * Prevents brute-force attacks. * Allows passwordless login (like Single Sign-On). * Requires each user to have a unique key pair. ==== Setting up Key Authentication ==== ===== Generating the Key Files ===== 1. On any Unix/Linux system, type the following command: <syntaxhighlight>ssh-keygen</syntaxhighlight> 2. You will be prompted to specify where to save the key files: <syntaxhighlight> Generating public/private ed25519 key pair. Enter file in which to save the key (/home/name/.ssh/id_ed25519): </syntaxhighlight> '''Example:''' <syntaxhighlight> Enter file in which to save the key (/home/name/.ssh/id_ed25519): /home/name/Desktop/key </syntaxhighlight> This will save both the public and private key files on your desktop under the name '''key'''. 3. You will be asked to set a passphrase for the key. If you trust the environment where the key is stored, you can leave it empty by pressing '''Enter'''. Alternatively, you can set a passphrase to add an extra layer of security. <syntaxhighlight> Enter passphrase for "/home/name/Desktop/key" (empty for no passphrase): </syntaxhighlight> 4. Once complete, the keys will be saved in the specified location: <syntaxhighlight> Your identification has been saved in /home/name/Desktop/key Your public key has been saved in /home/name/Desktop/key.pub The key fingerprint is: SHA256:I60X50p2/VwZ6MHhEqx8rWNse0pC5/vewW1i4tLufQ8 name@pc The key's randomart image is: +--[ED25519 256]--+ | | | . | | o . | | .. . = o | | . S+.+ * . | | o.==.+ o +| | . +.oXo.E++| | + o*.=B.=o| | . BOo+oo| +----[SHA256]-----+ </syntaxhighlight> Do not worry about the '''randomart''' as it has no functional purpose. 5. You now have two files: * key – This is your '''private key''' (keep this secure and never share it). * key.pub – This is your '''public key''' (place this on the server). The private key should stay on the machine you will use to access the server. ===== Securing the Server with Key Authentication ===== 1. Log in to the server you want to protect with key authentication. 2. Open the SSH configuration file: <syntaxhighlight> sudo nano /etc/ssh/sshd_config </syntaxhighlight> 3. Modify the following lines: <syntaxhighlight> #PermitRootLogin prohibit-password #PasswordAuthentication yes </syntaxhighlight> to: <syntaxhighlight> PermitRootLogin no PasswordAuthentication no </syntaxhighlight> This prevents root login over SSH, disables password login and forces key-based authentication. 4. Save and exit the file. 5. Go to the home directory of the user you wish to secure with key authentication. Create the '''.ssh''' directory (if it doesn't exist), then create the '''authorized_keys''' file inside it: <syntaxhighlight> mkdir -p ~/.ssh nano ~/.ssh/authorized_keys </syntaxhighlight> Paste the entire contents of the `.pub` file into this document and save it. 6. Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> '''DO NOT LOG OUT UNTIL YOU CONFRIM THE CONFIGURATION IS CORRECT TO AVOID BEING LOCKED OUT.''' 7. Open another terminal window on the machine you will use to SSH into the server and test the connection: <syntaxhighlight> ssh <user>@<address> -i /location/to/private/key/file </syntaxhighlight> If you can log in without a password, the key authentication system is correctly configured! 3cd6cce7a2ae16a5ffcdc586253b7627239f82c9 0 166 2021 784 2025-04-13T10:08:50Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} A term commonly used across any Linux community{{Citation needed}}, "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life. <ref>Merriam-Webster Dictionary. [https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of [[Linux]] and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system.{{Citation needed}} <references /> [[Category:Terminology]] 77c3da08106adf55544ff17c28b55f467e4528b8 0 318 2022 1181 2025-04-13T10:09:10Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs Citations}} The bootloader is a program that's responsible for booting the system. Most of the time, it will have a menu to choose an option from, making it a boot manager. A bootloader is installed onto the boot partition of the computer during a distribution's installation process. Most of the times, boot partitions may need from 200-600MB of space to work properly. Most bootloaders also have theming capabilities, take, for example, the previously mentioned GRUB. [[Category:Terminology]] 5c273d6d3aa836e9b1a9316da16c8959d1415289 0 269 2023 1034 2025-04-13T10:10:40Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Instructions should be separated onto their own page under the Guides namespace}} {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], budgie provides an easy to use interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] === Features === '''Budgie Desktop View''' is a software component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. === Installation === Budgie is available on almost all [[Linux Distributions|Linux distributions]]. ==== Arch-based systems ==== To install the '''budgie''' package group, which includes first-party applications such as a screensaver, execute <code>sudo pacman -S budgie</code>. Alternatively, <code>sudo pacman -S budgie-desktop</code> will install the standalone desktop. Recommended optional packages include the Arc GTK theme, the Papirus icon theme, and the Network Manager applet. Executing <code>sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet</code> will install them. ==== Fedora Linux ==== [[Fedora]] has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. ==== Ubuntu ==== There is a [https://ubuntubudgie.org/ community ISO] that contains [[Ubuntu]] with Budgie Desktop instead of GNOME. ==== Void Linux ==== <code>sudo xbps-install budgie-desktop</code> ==== OpenSUSE ==== Budgie can be selected during the OpenSUSE installation or installed afterward using <code>sudo zypper install budgie-desktop</code>. [[Category:Desktop Environments]] f1e83208e976684972fce82cd6c1de31ccffc3f5 0 414 2024 1440 2025-04-13T10:12:13Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970's, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at [[Bell Labs]], and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and preprocessors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include [[GNU GCC]], [[Clang]], TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the [[Clang|Clang compiler toolchain]], however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as [[GNU Autotools]], [[CMake]], [[Meson Build|Meson]], [[Zig|Zig's build toolchain]] among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FOSS / FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, metaprogramming and structural components of a C codebase; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS / FLOSS|open source]] codebases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995-2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref>, many attribute issues regarding C to fragmentation and portability issues<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref>, lack of type safety and primitive resource access checks<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref>, poor administration on part of the C Language Working Group<ref>https://cor3ntin.github.io/posts/c/</ref>, and overall worsening over time<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref>. 5670202b994ed9685434c1e9871a2a54aba2b453 0 433 2025 1493 2025-04-13T10:12:53Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs Citations}} A '''CLI''' (Command-Line Interface) is a text-based interaction model in which users typewrite commands as text strings to interact with an operating system or a program through a computer. Unlike a [[TUI]], which relies upon a pseudo-graphical form made of characters, an interface that is purely a command-driven one usually would issue output in the form of lines of text upon receiving user instructions. [[File:Windows_Command_Prompt_Program.png|thumb|The Windows Command Prompt, an example of a CLI]] CLIs are often preferred by power users, system administrators, and developers for their efficiency, scriptability, and precise control over system operations. Common examples include: * Unix/Linux shells (bash, zsh, fish) * Windows Command Prompt * PowerShell * Python's REPL (Read-Eval-Print Loop) The main advantages of CLIs include: * Resource efficiency (minimal system requirements) * Automation capability through scripting * Remote system administration * Precise control over system operations * Speed of execution for experienced users While CLIs can have a steeper learning curve compared to GUIs (Graphical User Interfaces) or [[TUI]]s, they remain fundamental to modern computing, particularly in server administration, software development, and system maintenance. == History == Command-line interfaces emerged in the 1960s with computer terminals like the Teletype Model 33 ASR, which replaced punch cards as the primary means of computer interaction. Early operating systems like Unix and MS-DOS were primarily accessed through CLIs, establishing conventions that persist in modern computing. == Common Usage == CLI environments typically follow a standard pattern where: * The system displays a prompt (e.g., "$" for Unix-like systems) * Users type commands followed by arguments or options * The system executes the command and displays the output * The process repeats with a new prompt [[Category:Terminology]] [[Category:User interfaces]] cefcb71618944f4a5b246e49d9272d26d686d077 0 429 2026 1480 2025-04-13T10:13:12Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "[[Portfiles]]," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> [[Category:Linux Distributions]] fd4158d9c956f23d4c5e272dd4140a120234875a 0 313 2028 1104 2025-04-13T10:16:45Z Atmois 13 Add citations tag wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] {{Needs Citations}} == Overview == [https://github.com/linuxmint/cinnamon Cinnamon] is a desktop environment maintained by the [https://www.linuxmint.com/ Linux Mint] team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === A "Spice" is Cinnamon's name for an add-on applet, desklet, theme, widget, and more. They can be found at the [https://cinnamon-spices.linuxmint.com/ Cinnamon Spices repository website]. [[Category:Desktop Environments]] 35e897ff7ccdc33eb317f7f77d98218d5848496e 0 179 2029 877 2025-04-13T11:12:41Z Atmois 13 Add work in progress tag, should be reworked to a category page wikitext text/x-wiki {{Work In Progress}} Not every install will be as flawless as a user will expect it to be, and they may encounter bugs for numerous reasons ranging from simple hardware differences to nuanced kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) === [[Linux on Apple Macintosh Devices|Linux on Apple Devices]] === If you use '''an Apple device,''' Linux may have a few issues running flawlessly on first install - '''this section details some steps you should consider taking if you have specific issues.''' === [[Artificial Intelligence on Linux]] === '''Covers w-okada, Stable Diffusion, Large Language Models, ROCm/CUDA with proper driver setup, anaconda/conda...''' [[Category:Guides]] 8a4f9f10b99e3fcab946c9fc94f99ef4f7d80919 0 173 2030 1927 2025-04-13T11:22:31Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Incomplete page & Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager (G'''DM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a graphical user interface that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.<ref>https://github.com/tvrzna/emptty</ref> [[Category:Terminology]] 5e40bda2a5be21403cd167c44243e9aa619ee8a5 0 223 2031 989 2025-04-13T11:22:56Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs Citations}} == Distrohopping == Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (eg. FSF approved distribution) * Ecosystem or Tooling (eg. libc, [[Package Manager|package manager]], coreutils, [[Init System|init system]]) * Experimentation * Customization ... and many more. This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (eg. Debianisms, [[Package Manager|package managers]], init systems) * Opinionated design philosophies (eg. Nix, Guix, Fedora Atomic) * Additional configuration needs (eg. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (eg. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (eg. Liberapay, Github sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] f832093d75ab1ba693739e1898a94fad9b3959fb 0 177 2032 1682 2025-04-13T11:23:30Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the french word, libre)<ref>https://en.wiktionary.org/wiki/libre</ref> and Open Source Software (FLOSS), is software that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> [[Category:Terminology]] 49199ff0ce85ccf113be2c08dc513b1dd0d9b61e 0 268 2033 1197 2025-04-13T11:26:29Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch github.com/fastfetch-cli/fastfetch] }} Fastfetch is a [[neofetch]]-like tool for fetching information about your operating system, software and hardware. It is written mainly in [[C]], with a focus on performance.<ref>https://github.com/fastfetch-cli/fastfetch</ref> <references /> [[Category:Software]] 1338ca3da177c7ccc4c50503bef24e50ea4cbfc5 0 217 2034 823 2025-04-13T11:27:02Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]] |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}} [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being [[RHEL|Red Hat Enterprise Linux]] (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] 59b9553cb0a86b3b160806502a795565baf9ad8c 0 164 2035 788 2025-04-13T11:28:00Z Atmois 13 Add WIP tag, pending major rework wikitext text/x-wiki {{Work In Progress}} == Introduction == The [[Linux]] community is abundant with awesome projects and various other guides worth checking out, Here's some great ones that we have found - keep in mind that, while these guides are very useful, they are not fully exhaustive. More than likely you discover new software every day! * Privacy is not an end goal, but a consistent journey that needs to be taken very seriously. ''Always'' seek help when in doubt and ensure you take everything with a grain of salt. ''Do not just blindly follow guides but use your own intuition!'' == Guides == * https://www.privacyguides.org/ - An essential guide to learning not just ''how'' to begin your privacy journey online but offers a comprehensive explanation of abstract privacy concepts that is simple to understand and by extension ''is assuredly not easy or quick -'' read with an open mind! ** https://awesome-privacy.xyz - More of a guide to tools you may find yourself wanting to use to enhance privacy, rather than an explanation. The next step from Privacy Guides, essentially. ** https://www.privacytools.io/ - Similar to Awesome Privacy, and offers a wide range of tools. This specific website is recommended very frequently. * https://brainfucksec.github.io/firefox-hardening-guide - A guide to "de-Mozilla" and security-harden Firefox. Assess whether or not this is a good option for you - ''similar to privacy, it is not an easy process.'' * https://rentry.co/fmhy-guides - General, yet extremely useful and even nuanced guides that you may find yourself needing for something very specific and hard to find on the internet. * https://github.com/luong-komorebi/Awesome-Linux-Software - Very extensive guide of not solely Linux software but mostly open-source software that has many use cases in mind. [[Choosing A Linux Distribution|May be helpful in picking a flavor of Linux for your specific use cases.]] == Wikis == * https://wiki.archlinux.org/ for Arch Linux * https://wiki.gentoo.org/ for Gentoo * https://wiki.debian.org/ for Debian * https://fedoraproject.org/wiki/Fedora_Project_Wiki for Fedora * https://wiki.ubuntu.com for Ubuntu == Tools == * https://christitus.com/windows-tool/ - Used for debloating and removing telemetry from Windows. * https://alternativeto.net - A tool to find alternatives to popular software, both open-source and proprietary. [[Category:Guides]] 212f089c2f7d01383341100f7408db1e1906612d 0 291 2036 1489 2025-04-13T11:28:42Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:GNOME logo.svg|200px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 47, 2024-09-18 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = The GNOME Project | website = [https://gnome.org/, gnome.org] }} [[File:GNOME 46.png|thumb|A desktop running GNOME 46 in Fedora Workstation 40]] [[GNOME]] is a desktop environment designed to be simple, beautiful, and elegant. It is the main desktop environment of [[Fedora]] and [[Ubuntu]] among others, and is a very popular desktop environment within [[Linux]]/BSD. GNOME began development in 1997 by Miguel de Icaza and Federico Mena, with GNOME 1, the first major release of GNOME, being released in 1999. == GTK == GTK (formerly, GIMP Toolkit) is a widget toolkit that was created for GIMP, but is known as the widget toolkit for GNOME. It uses the GLib data structure and GObject object and type system, to create the GUI behind GNOME and GTK apps such as Epiphany, GIMP and Transmission among others. GTK is one of the most commonly used GUI frameworks, alongside the Qt framework, Cocoa for macOS and Windows Forms for Windows among others. [[Category:Desktop Environments]] efae9558ebe15983203182c8a3feb9ff42a387ef 0 203 2037 1519 2025-04-13T11:30:02Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by Daniel Robbins. Known for its emphasis on customization and performance optimization, Gentoo allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == Gentoo stands out for its unique approach to package management and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === * Complete system customization through source compilation * Choice between OpenRC and systemd init systems * Extensive hardware architecture support * Rolling release model with stable branch option * Minimal base system requirements * Advanced package management through Portage == Installation == Installing Gentoo requires manual configuration and compilation of the system components. The process involves: * Preparing the installation environment * Partitioning and formatting storage * Configuring and compiling the kernel * Setting up the bootloader * Installing and configuring base system packages For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is Gentoo's package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |} == System Optimization == === Compilation Flags === Gentoo users can optimize their system through: * CPU-specific optimizations * Custom compile flags * USE flag combinations * Kernel configuration * Package-specific settings === Binary Packages === For users seeking faster installation times, Gentoo offers: * Pre-compiled package options * Binary package creation * Distribution of binary packages * Mixed source/binary environments == Security == Gentoo implements several security measures: * SELinux support * Hardened profiles * Regular security updates * Signed package verification * Kernel hardening options == Community and Development == === Community Resources === * [https://forums.gentoo.org/ Official Forums] * IRC channels * Mailing lists * Wiki documentation * Bug tracking system === Development Model === * Open source development * Community-driven package maintenance * Regular security updates * Active development team * Public Git repositories == Comparison with Other Distributions == === Advantages === * Maximum customization potential * Optimal performance through compilation * Complete control over features * Extensive documentation * Active community support === Considerations === * Longer installation time * Higher learning curve * Requires technical knowledge * Resource-intensive compilation * Regular maintenance needed == Trivia == * Larry the Cow is Gentoo's unofficial mascot * The name "Gentoo" comes from the fast-swimming Gentoo penguin * View Larry by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 28a3e3fb60310bc925e957f96cc2622e8b14bfeb 0 570 2038 1884 2025-04-13T11:30:26Z Atmois 13 Update formatting wikitext text/x-wiki {{MascotInfobox | title = GNU | image = [[File:Heckert_GNU_white.svg|thumb]] | caption = GNU, the mascot of the GNU Project }} GNU is the mascot of the GNU Project [https://gnu.org/ gnu.org] GNU is a black and white sketch of a wildebeest (also known as a gnu or gnou) [[Category:Mascots]] c8b3bffc5dd642d7553d6ae2cdf0badb1bea14de 2039 2038 2025-04-13T11:30:58Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs_Citations}} {{MascotInfobox | title = GNU | image = [[File:Heckert_GNU_white.svg|thumb]] | caption = GNU, the mascot of the GNU Project }} GNU is the mascot of the GNU Project [https://gnu.org/ gnu.org] GNU is a black and white sketch of a wildebeest (also known as a gnu or gnou) [[Category:Mascots]] 497c3ce607ec5d0bb45ed75dec8cf4a78a2b2ca0 0 257 2040 1806 2025-04-13T11:32:04Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Needs Citations}} {{Cleanup|Installation instructions should be separated onto its own page in the Guides namespace}} {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) === Installation === This section will change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Managers]] 0600ac542e53df637423d449a37b4f0ba2483858 0 239 2041 991 2025-04-13T11:33:24Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} {{Needs_Citations}} {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Window Managers]] f8c6e99b170721da788155a8f3d63a35df0e5472 0 8 2044 1664 2025-04-13T16:54:28Z Atmois 13 Added WIP tag, page pending rework wikitext text/x-wiki {{Work In Progress}} == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FOSS / FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] d659ceb3a6f9c657399d1868a5383254b752a2a2 0 344 2045 1267 2025-04-13T17:00:33Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Cleanup|Short article, requires more information}}{{Needs Citations}} The Kernel is the core part of any operating system, including Linux. It's the fundamental layer between your hardware (like your CPU, memory, and GPU) and the software you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, Etc). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. [[Category:Terminology]] 17fbc7c5f85471f4ec05e0da595be6e4fd1bb42c 0 539 2046 1793 2025-04-13T17:17:04Z Atmois 13 Update formatting wikitext text/x-wiki '''Kernel commands''' are special key combinations that allow direct communication with the operating system's '''[[kernel]]''', the core part of the system that manages hardware and software interactions. These commands let users perform important tasks like '''forcing reboots, ending unresponsive processes, and running memory diagnostics'''. They are mostly used for system recovery and debugging when the operating system becomes unresponsive. However, because they operate at such a low level, improper use can result in '''data loss or system damage''' and should be used with caution. === The SysReq (System Request) Key<ref>[https://www.delorie.com/djgpp/doc/rbinter/id/30/15.html Ralf Brown's Interrupt List] - Callout or Callback (usually hooked rather than called)</ref> === The '''SysReq key''' was first introduced by IBM with the '''PC/AT''' and was originally meant to handle low-level operating system functions. In computing, "low-level" refers to processes that interact more directly with hardware.<ref>[https://web.archive.org/web/20060814072427/http://www-03.ibm.com/ibm/history/exhibits/pc25/pc25_fact.html The IBM Archives: Product Fact Sheet] - Wayback Machine: IBM</ref> For example, the programming language '''C''' is commonly used to develop operating systems because it allows efficient communication with hardware components. At first, the SysRq key was designed to '''prevent software conflicts''' by allowing system-level commands to run without interference from active applications. However, as operating systems advanced, its role changed across different platforms.<ref>[[wikipedia:System_request#cite_ref-mskb43648_6-0|System request]] - Wikipedia: The Free Encyclopedia</ref> ==== Use of the SysRq Key in Different Operating Systems ==== * '''Linux:''' The kernel can use the '''SysReq key''' to execute important commands, often for system recovery and debugging. The '''Magic SysRq key''' combinations allow users to restart the system, kill unresponsive processes, or recover from crashes without using the standard user interface.<ref>[https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html Linux Magic System Request Key Hacks] - What is the magic SysRq key?</ref> * '''Windows:''' In modern versions of '''Windows''', the SysReq key is mostly unused. However, it was once used for system debugging and, in some cases, has been repurposed by software like '''remote desktop tools''' or '''virtualization platforms''' to send special key commands.<ref>[https://web.archive.org/web/20081108021540/http://support.microsoft.com/kb/43648 Returning Control to Codeview] - Microsoft @2008</ref> While the '''SysRq key''' is no longer widely used in mainstream computing, it remains relevant for '''system administrators, developers, and users of certain non-mainstream operating systems''' who need a way to interact with the system at a low level. == Linux SysReq Information Table == To begin a kernel command, press & hold the <code>ALT</code>, then '''press''' <code>PrtSc</code> (You are not required to hold the key down). Then press on of the keys below:<ref>[https://www.kernel.org/doc/html/v4.14/admin-guide/sysrq.html?highlight=sysrq Linux Magic System Request Key Hacks] — What are the 'command' Keys, ''Documentation for sysrq.c''</ref> {| class="wikitable" |+ !''Letter'' !Use: |- |<code>b</code> |Will immediately begin rebooting the system without attempting to unmount any drives [This may corrupt data during a write operation; it is best to mount all drivers as '''R''' only (Read-only) after any writing operation using <code>u</code> then to reboot. |- | ====== '''<code>c</code>''' ====== |Crashes the system using a NULL pointer dereference -> can return a crash dump to file if configured to send/touch a file. |- |<code>'''d'''</code> |Shows all locks that are held. |- |<code>'''e'''</code> |Kernel sends a '''SIGTERM''' signal to all active processes, terminating them. This does not apply to the '''init''' process. |- |<code>'''f'''</code> |Calls an OOM (Out-of-memory) killer to attempt to kill any processes taking too much memory, but does not panic if nothing can be killed. |- |<code>'''g'''</code> |Used for the Kernel-Debugger (kgdb). |- |<code>'''h'''</code> |Kernel outputs possible commands; if you don't press a key with a corresponding command, it'll just output this instead, just in case!! |- |<code>'''i'''</code> |Kernel sends a '''SIGKILL''' signal to all active processes, killing them. This does not apply to the '''init''' process. |- |<code>'''j'''</code> |Kernel forcibly "thaws" any filesystem frozen by the FIFREEZE ioctl. (A system call to freeze a file system.) |- |<code>k</code> |Kills all programs on a current virtual console. Secure Access Key (SAK). |- |... |This table is a work in progress. |}<references /> 4e6915a9257530707e5472fab9f90c35bd40d02d 2047 2046 2025-04-13T17:17:23Z Atmois 13 Update formatting wikitext text/x-wiki '''Kernel commands''' are special key combinations that allow direct communication with the operating system's '''[[kernel]]''', the core part of the system that manages hardware and software interactions. These commands let users perform important tasks like '''forcing reboots, ending unresponsive processes, and running memory diagnostics'''. They are mostly used for system recovery and debugging when the operating system becomes unresponsive. However, because they operate at such a low level, improper use can result in '''data loss or system damage''' and should be used with caution. === The SysReq (System Request) Key<ref>[https://www.delorie.com/djgpp/doc/rbinter/id/30/15.html Ralf Brown's Interrupt List] - Callout or Callback (usually hooked rather than called)</ref> === The '''SysReq key''' was first introduced by IBM with the '''PC/AT''' and was originally meant to handle low-level operating system functions. In computing, "low-level" refers to processes that interact more directly with hardware.<ref>[https://web.archive.org/web/20060814072427/http://www-03.ibm.com/ibm/history/exhibits/pc25/pc25_fact.html The IBM Archives: Product Fact Sheet] - Wayback Machine: IBM</ref> For example, the programming language '''C''' is commonly used to develop operating systems because it allows efficient communication with hardware components. At first, the SysRq key was designed to '''prevent software conflicts''' by allowing system-level commands to run without interference from active applications. However, as operating systems advanced, its role changed across different platforms.<ref>[[wikipedia:System_request#cite_ref-mskb43648_6-0|System request]] - Wikipedia: The Free Encyclopedia</ref> ==== Use of the SysRq Key in Different Operating Systems ==== * '''Linux:''' The kernel can use the '''SysReq key''' to execute important commands, often for system recovery and debugging. The '''Magic SysRq key''' combinations allow users to restart the system, kill unresponsive processes, or recover from crashes without using the standard user interface.<ref>[https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html Linux Magic System Request Key Hacks] - What is the magic SysRq key?</ref> * '''Windows:''' In modern versions of '''Windows''', the SysReq key is mostly unused. However, it was once used for system debugging and, in some cases, has been repurposed by software like '''remote desktop tools''' or '''virtualization platforms''' to send special key commands.<ref>[https://web.archive.org/web/20081108021540/http://support.microsoft.com/kb/43648 Returning Control to Codeview] - Microsoft @2008</ref> While the '''SysRq key''' is no longer widely used in mainstream computing, it remains relevant for '''system administrators, developers, and users of certain non-mainstream operating systems''' who need a way to interact with the system at a low level. == Linux SysReq Information Table == To begin a kernel command, press & hold the <code>ALT</code>, then '''press''' <code>PrtSc</code> (You are not required to hold the key down). Then press on of the keys below:<ref>[https://www.kernel.org/doc/html/v4.14/admin-guide/sysrq.html?highlight=sysrq Linux Magic System Request Key Hacks] — What are the 'command' Keys, ''Documentation for sysrq.c''</ref> {| class="wikitable" |+ !''Letter'' !Use: |- |<code>b</code> |Will immediately begin rebooting the system without attempting to unmount any drives [This may corrupt data during a write operation; it is best to mount all drivers as '''R''' only (Read-only) after any writing operation using <code>u</code> then to reboot. |- | ====== '''<code>c</code>''' ====== |Crashes the system using a NULL pointer dereference -> can return a crash dump to file if configured to send/touch a file. |- |<code>'''d'''</code> |Shows all locks that are held. |- |<code>'''e'''</code> |Kernel sends a '''SIGTERM''' signal to all active processes, terminating them. This does not apply to the '''init''' process. |- |<code>'''f'''</code> |Calls an OOM (Out-of-memory) killer to attempt to kill any processes taking too much memory, but does not panic if nothing can be killed. |- |<code>'''g'''</code> |Used for the Kernel-Debugger (kgdb). |- |<code>'''h'''</code> |Kernel outputs possible commands; if you don't press a key with a corresponding command, it'll just output this instead, just in case!! |- |<code>'''i'''</code> |Kernel sends a '''SIGKILL''' signal to all active processes, killing them. This does not apply to the '''init''' process. |- |<code>'''j'''</code> |Kernel forcibly "thaws" any filesystem frozen by the FIFREEZE ioctl. (A system call to freeze a file system.) |- |<code>k</code> |Kills all programs on a current virtual console. Secure Access Key (SAK). |- |... |This table is a work in progress. |} == References == <references /> 958dedc3bb0f0f11605190948cbb595542baba95 0 345 2048 1280 2025-04-13T17:24:01Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Cleanup|Short article}}{{Needs Citations}} Kernel Modules are pieces of code that can be loaded directly into the [[Kernel]] at runtime to extend functionality. The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your [[Linux Distributions|Distribution]], as such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically older ones benefit the most) at the cost of new devices potentially not working when added. It is also possible to compile a Linux kernel on a pre-existing system to only use needed Kernel modules. [[Category:Terminology]] de2bcae860524e3bd3bb5f7a14722127e9fb512b 0 219 2049 1752 2025-04-13T17:24:46Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the guidelines}} {{MascotInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan<ref>https://community.kde.org/Promo/Material/Mascots</ref>. Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror], KDE's default web browser<ref>https://community.kde.org/Konqi</ref>.<references /> [[Category:Mascots]] cb3ba5d52ee81ca453de48f93256d58d9cea0d76 2053 2049 2025-04-13T17:30:36Z Atmois 13 Update cleanup reason wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan<ref>https://community.kde.org/Promo/Material/Mascots</ref>. Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror], KDE's default web browser<ref>https://community.kde.org/Konqi</ref>.<references /> [[Category:Mascots]] d4807942d88125eb1c07a5370b4bb3c03c204bf5 0 202 2050 1754 2025-04-13T17:26:44Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the guidelines}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry</ref> <references /> [[Category:Mascots]] 78e2ff735f5d0c592c39ef283eafe127992ec402 2054 2050 2025-04-13T17:30:50Z Atmois 13 Update cleanup reason wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry</ref> <references /> [[Category:Mascots]] c156504960d9e9118724966dcbdc752ab7361d95 0 244 2051 876 2025-04-13T17:27:05Z Atmois 13 Add cleanup wikitext text/x-wiki {{Cleanup|Citations lack information required in the guidelines}} [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. '''NOTE:''' After your first Libreboot, you are more than likely able to flash repeatedly afterwards without having to use a Pomona Flash Clip (below). Depending on your device, the flashing experience may and inevitably, at times, '''will''' vary. '''<u>Please check for your BIOS chip device on the Libreboot website.</u>''' === Steps to Install === As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your machine using the Dell OptiPlex as an example. See below for an easier method for that specific device. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. For a Dell OptiPlex 9020, your image '''should be named''' "'''dell9020mt_12mb'''." after compilation. ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] b3467f134689651d250257f89f4b428730f60157 2052 2051 2025-04-13T17:29:15Z Atmois 13 Update reason for cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]. Installation instructions should be on its own Guides page.}} [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. '''NOTE:''' After your first Libreboot, you are more than likely able to flash repeatedly afterwards without having to use a Pomona Flash Clip (below). Depending on your device, the flashing experience may and inevitably, at times, '''will''' vary. '''<u>Please check for your BIOS chip device on the Libreboot website.</u>''' === Steps to Install === As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your machine using the Dell OptiPlex as an example. See below for an easier method for that specific device. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. For a Dell OptiPlex 9020, your image '''should be named''' "'''dell9020mt_12mb'''." after compilation. ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) [[Category:Guides]] 3cefee6ee4c56b6d5d22ffae538b52f3d1ae185b 0 178 2055 795 2025-04-13T17:31:34Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux Kernel | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], Assembly, [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] Linux in itself refers to two entities, the former being the kernel itself developed by Linus Torvalds and the latter being the families of [[Linux Distributions|Operating Systems based off the Kernel]]. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> <references /> [[Category:Terminology]] 760cf1037f2346a9196fbc79f512606bd36c7922 0 209 2056 797 2025-04-13T17:37:51Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Cleanup|Incomplete page, guides should be on their own page in the Guides namespace}} {{Needs_Citations}} == Introduction == [[Linux]] is a good way to make-do with an old Intel Mac you may have. Many issues exist due to hardware support, such as WiFi support, and keyboard + trackpad issues on some devices. This page will list solutions to common issues as well as tips, tricks, and other information. On many Mac devices Linux works flawlessly after initial setup and troubleshooting is complete. If you are attempting to install Linux on a device with an ARM (Apple Silicon) CPU, see the [[#Asahi Linux]] section. == Asahi Linux == Asahi Linux as a work in progress port of many tools and drivers to Apple Silicon on Linux, and is currently under heavy development. More information can be found on the [https://asahilinux.org/ Asahi Linux website]. == Troubleshooting == === MacBookPro11,x to MacBookPro12,1 === ==== WiFi doesn't work ==== This is a side-effect of Broadcom's poor driver support on Linux, read [https://asahilinux.org/ this page] for information on how to install the proprietary '''broadcom-wl driver''' on Arch Linux. Other distributions should follow their respective guides if one exists. == Notes == '''> More issues will be added overtime. This list is far from done.''' <references /> [[Category:Guides]] 5d391ed181485bbce4fa120e347ff327c1af34c5 0 218 2057 911 2025-04-13T17:38:14Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} == Introduction == [[Linux]] is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |Puppy Linux | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref>https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> 0c97eb1c89c1bb2368640a222442942f515b538a 0 581 2058 1987 2025-04-13T17:45:48Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs Citations}} {{DISPLAYTITLE:MATE DE}} [[File:MATEDesktop.png|thumb|A screenshot of the default MATE desktop on Debian Linux.]] The [https://mate-desktop.org/ MATE] Desktop Environment is a desktop environment that is the continuation of GNOME 2. It is known for using traditional metaphors for Linux and other Unix-like operating systems, and for being a lightweight desktop that runs well on older hardware. It is available on a wide variety of Linux, Illumos and BSD - based systems. MATE is known as one of the three desktop options on [https://www.linuxmint.com/ Linux Mint], as well as the main desktop of [[Ubuntu|Ubuntu MATE]]. == Features == MATE is configured by default to use a traditional UNIX-like desktop layout, with a top and bottom panel like its ancestor GNOME 2. It is a lightweight desktop, much like [[XFCE]], and is often used on older and less powerful computers. It can use GTK2 or GTK3 theming - the latter being compatible with [[Cinnamon]]. == Software == The base system is made up of the Marco window manager, MATE Panel, and MATE Session Manager. Additional software can be installed on some distributions with the mate-extras package. MATE includes the Caja file manager, Pluma notepad / text editor, Eye of MATE image viewer, Atril document viewer, Engrampa archive manager, and MATE Terminal. == Naming == MATE is said to be pronounced "mah-tay". The MATE desktop is named after ''Ilex paraguariensis,'' commonly known as yerba maté, which is a caffeine-rich holly plant used to make the infused herbal drink mate. [[Category:Desktop Environments]] 32e5cd1aff77ffd2cc43504e1b1374f13cab51fb 0 428 2059 1676 2025-04-13T17:46:32Z Atmois 13 Add citations tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} Man or Man pages is a [[command-line]] utility available on [[UNIX]] and [[UNIX-like]] [[operating systems]] that provides [[documentation]] for [[Program|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format]] and [[games]]. The Man pages are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a Man page the user can enter the following into their [[terminal]]: man <command_name> <ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> For example to read the Man page on [[pacman]] you would enter the following: man pacman == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardize layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> <references /> 8b330f61bb9e98dfa3d508343f5f91e290984659 0 240 2060 1217 2025-04-13T17:46:54Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs Citations}} == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your disribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most deriative distributions. ==== General Information ==== ===== Multi Booting ===== [[File:GRUB with ubuntu and windows vista.png|thumb|GRUB, with entries for [[Ubuntu]] and Windows Vista, an example of ''dual booting.'']] [[Multi Booting]] (Or often refered to as 'Dual Booting') is the process of installing multiple [[Operating System|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completly removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to parititon the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly reccomended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi Booting]] page. ===== Finding Alternatives or Workarounds for Apps ===== Often there is at least one [[application]] missing on Linux or an app that is missing some features or is buggy so you'll find yourself looking for alternative options. There also sometimes is the issue that your distribution doesn't have an app but another distribution does have it. A good place to start when looking for alternatives is [https://alternativeto.net AlternativeTo] which is a crowdsourced site useful to find alternatives for almost any app. Other useful sites include [https://www.privacytools.io Privacy Tools] and [https://awesome-privacy.xyz Awesome Privacy] with a privacy focused list of apps. When looking for workarounds for apps not supported for your distribution you should first check [https://flathub.org Flathub] and [https://snapcraft.io Snapcraft] (Note that [[Snap|Snaps]] are known to have performance issues) if your app is available there as they offer support for most distributions. If a steam game lacks native Linux support try checking [https://www.protondb.com ProtonDB] if Valve's proton tool supports your game. [https://www.winehq.org Wine] is also an option to run Windows apps on Linux. ==== Moving between specfic Operating Systems ==== ===== Moving to Linux from MacOS ===== ===== Moving to Linux from Windows ===== === General Information === [[Category:Guides]] 8009339c272b23b7f9edf8309bc22208529ea6b7 0 297 2061 1576 2025-04-13T17:49:36Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Instructions need to be separated onto their own page under the Guides namespace}} == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref>. The core concept of multi-booting revolves around partitioning a computer’s storage device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own partition, effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with UEFI (Unified Extensible Firmware Interface), an additional EFI System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref>, including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing software that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == How to Multi-boot == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen distribution search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitons"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-Boot|Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! <references /> [[Category:Terminology]] ed8038b3ed568e1e45ea8fb4fcb4b20b86c1118f 0 534 2062 1969 2025-04-13T17:50:27Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]. Installation instructions should be on their own page.}} {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|firstrelease=v0.1.0-alpha.1|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1" /> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config == Installation == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. <syntaxhighlight> # dnf copr enable yalter/niri # dnf install niri </syntaxhighlight> === Arch Linux === To download the latest stable release, run the following command: <syntaxhighlight> # pacman -S niri </syntaxhighlight> If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: <syntaxhighlight> $ yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix''' <syntaxhighlight lang="nix"> {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; # In case you want to override niri. }; } </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: <syntaxhighlight> # pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. <syntaxhighlight> # zypper in niri </syntaxhighlight> Alternatively, you can install it with '''opi''' as well. <syntaxhighlight> # opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''. <syntaxhighlight> # xbps-install -S niri </syntaxhighlight> === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file.<ref name=":1" /> While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref name=":1">https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages below to ensure app functionality<ref name=":1" />. Do note that the list of packages below doesn't apply to all distributions. <syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref name=":2">https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session). <syntaxhighlight> $ mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight> '''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder.<ref name=":2" /> <syntaxhighlight> $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> '''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder.<ref name=":2" /> <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight> After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight> Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so<ref>https://github.com/YaLTeR/niri/wiki/Configuration:-Miscellaneous</ref>. In this case, if you desire XWayland, you may add the following to your configuration. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight> You may also automatically start <code>swaybg</code> in a similar manner. <syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight> For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. <references /> ec7b065ba2c3a0e2c0204de8bdf60173637e1474 0 171 2063 1154 2025-04-13T17:51:19Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|thumb|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = Customizable based on user configuration | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. <references /> [[Category:Linux Distributions]] 83dae5e06d94d5be9ce6f740ac0abbf2cb465120 0 299 2064 1804 2025-04-13T17:51:36Z Atmois 13 Remove needs citations tag wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a Unix [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released on July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 7d4b75aea88029e27ead15ff63cb3a8383991d88 0 562 2065 1979 2025-04-13T17:52:00Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel. Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>https://web.archive.org/web/20100913030810/https://www.openindiana.org/</ref> It was proved timely as Oracle shut down development of OpenSolaris. Openindiana uses the same tooling as Solaris; the SMF init system, FMA fault management system, and IPS package manager. The majority of the [https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/ Solaris documentation] also applies to OpenIndiana. Openindiana makes use of the SunOS branch of the UNIX kernel, and thus provides all of the stability benefits of a UNIX System V derivative. this does, however, mean that hardware support is limited in comparison to a BSD or Linux based OS. OpenIndiana uses the SunOS libc, which severely limits what software will compile on it successfully. SunOS libc only really implements functions expected by POSIX and ANSI C. [[Category:Misc Operating Systems]] [[Category:Illumos]] 2847082b3353d0ea64b38077d5555330c59f5e72 0 279 2066 978 2025-04-13T17:52:19Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs_Citations}} == Introduction == {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|thumb]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, ppc64, x86_64 | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. This distribution stands out by having two variations of the distributions: OpenSUSE Tumbleweed is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. OpenSUSE Leap is the point release version, with a new release every year with older and more stable packages meant for business use. [[Category:Linux Distributions]] 9ff51c9b79119a402db8e839e7b34fc44079ed72 0 480 2067 1853 2025-04-13T17:52:42Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}} [[File:Oreon10-2502.png|thumb|Oreon 10 Core (Build 2502) running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>https://oreonproject.org/</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>https://git.oreonproject.org/rpms</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>https://boostyconnect.com/oreon-lime-r1-lifecycle/</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>https://oreonproject.org/oreon-lime-r2-support-timeline/</ref><ref>https://oreonproject.org/oreon-lime-r2/</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/</ref> and other well-known sources. In October 2024, Oreon celebrated it's 1st anniversary on November 16, 2024 and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69</ref> Oreon 10 released to the public on December 12, 2024 shipping with KDE Plasma 6 and Linux 6.11<ref>https://forums.oreonproject.org/t/oreon-10-officially-released/98</ref> but was upgraded to 6.12 a few days later. A new update to Oreon 10 has been released on February 12, 2025 under the name "Build 2502." This update brought a few bug fixes along with some planned features for later such as Apple M-series Mac support.<ref>https://forums.oreonproject.org/t/oreon-10-build-2502-has-officially-released/150</ref> <references /> [[Category:Linux Distributions]] fc12b765c366d189699bc6d0a6fbff916b5c0db3 0 169 2068 982 2025-04-13T17:53:27Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. [[Category:Terminology]] f1b2400ff8107c5405bbb4f1906313b8dd3bfa2e 3000 518 2069 1657 2025-04-13T17:54:01Z Atmois 13 Remove empty header wikitext text/x-wiki == Linux File Ownership == In Linux, there are three types of ownership classes: user, group, and others. === User === A user is the default owner and creator of a file. This user is often referred to as the owner. === Group === A group is a collection of users. All users belonging to a group share the same permissions to access a file or directory. Groups are useful for assigning permissions to multiple users at once. A user can belong to more than one group. === Others === Any users that are not part of the owner or group classes are categorized as "others." == Linux File Permissions == File permissions determine what actions users can perform on files or directories. There are three types of permissions: === Read Permission (r) === * For files: Allows users to open and view the contents of the file but not modify it. * For directories: Allows users to list the contents of the directory. === Write Permission (w) === * For files: Allows users to modify the contents of the file (edit, delete, save). * For directories: Allows users to modify directory contents (create, delete, and rename files inside the directory). === Execute Permission (x) === * For files: Allows users to execute or run the file, such as scripts or binaries. * For directories: Allows users to access files in the directory and obtain details about them. You can check permissions of files and directories using the `ls -l` command on a Linux terminal. == How to Change Permissions in Linux == Permissions can be modified using the `chmod` command. There are two methods to use `chmod`: symbolic mode and absolute mode. === Syntax === <code> chmod permissions filename</code> * '''permissions''': Specifies the read (r), write (w), and execute (x) permissions to be modified. * '''filename''': The name of the file or directory whose permissions need to be changed. === Symbolic Mode === In symbolic mode, you use symbols to specify permissions and users. Below are the representations: {| class="wikitable" |+Symbolic Representations !Symbol !Description |- |'''u''' |User/owner |- |'''g''' |Group |- |'''o''' |Others |} You can use the following operators to modify permissions: {| class="wikitable" |+Mathematical Operators !Operator !Description |- |'''+''' |Adds a permission |- |'''-''' |Removes a permission |- |'''=''' |Sets permissions (overwrites existing permissions) |} ==== Examples ==== * Add execution (x) permission for the owner:<code> chmod u+x script.sh</code> * Remove read and write (r, w) permissions for group and others:<code> chmod go-rw file.txt</code> * Set write (w) permission for group and overwrite existing permissions:<code> chmod g=w file.txt </code> === Absolute Mode === Absolute mode uses numeric values to represent permissions. Each permission is assigned a value as shown below: {| class="wikitable" |+Numeric Representation of Permissions !Permission !Numeric Value |- |Read (r) |4 |- |Write (w) |2 |- |Execute (x) |1 |} The total value for a permission set is calculated by adding the numeric values for the desired permissions. For example: * Read (4) + Write (2) = 6 * Read (4) + Execute (1) = 5 ==== Example ==== To set permissions as: * User: Read (4), Write (2) and Execute (1) * Group: Read (4) and Execute (1) * Others: Execute (1) Use the following command:<code> chmod 751 file.txt </code> This results in `rwxr-x--x`. == How to Change Ownership in Linux == File and directory ownership can be changed using the `chown` command. Ownership can be assigned to users, groups, or both. === Syntax === <code> chown [user][:group] filename</code> * '''user''': Specifies the new owner. * '''group''': Specifies the new group owner. === Examples === * Change ownership to user "jdoe":<code> chown jdoe file.txt</code> * Change ownership to user "jdoe" and group "devteam":<code>chown jdoe:devteam file.txt</code> * Change ownership recursively for a directory and its contents:<code> chown -R admin /opt/scripts</code> * Change only the group ownership:<code> chown :admins /opt/scripts </code> 82eb3eb422d6b706175d58b19b37b320ff01fba0 2070 2069 2025-04-13T17:54:27Z Atmois 13 Atmois moved page [[Permissions]] to [[Guides:Permissions]] without leaving a redirect: Move to guides wikitext text/x-wiki == Linux File Ownership == In Linux, there are three types of ownership classes: user, group, and others. === User === A user is the default owner and creator of a file. This user is often referred to as the owner. === Group === A group is a collection of users. All users belonging to a group share the same permissions to access a file or directory. Groups are useful for assigning permissions to multiple users at once. A user can belong to more than one group. === Others === Any users that are not part of the owner or group classes are categorized as "others." == Linux File Permissions == File permissions determine what actions users can perform on files or directories. There are three types of permissions: === Read Permission (r) === * For files: Allows users to open and view the contents of the file but not modify it. * For directories: Allows users to list the contents of the directory. === Write Permission (w) === * For files: Allows users to modify the contents of the file (edit, delete, save). * For directories: Allows users to modify directory contents (create, delete, and rename files inside the directory). === Execute Permission (x) === * For files: Allows users to execute or run the file, such as scripts or binaries. * For directories: Allows users to access files in the directory and obtain details about them. You can check permissions of files and directories using the `ls -l` command on a Linux terminal. == How to Change Permissions in Linux == Permissions can be modified using the `chmod` command. There are two methods to use `chmod`: symbolic mode and absolute mode. === Syntax === <code> chmod permissions filename</code> * '''permissions''': Specifies the read (r), write (w), and execute (x) permissions to be modified. * '''filename''': The name of the file or directory whose permissions need to be changed. === Symbolic Mode === In symbolic mode, you use symbols to specify permissions and users. Below are the representations: {| class="wikitable" |+Symbolic Representations !Symbol !Description |- |'''u''' |User/owner |- |'''g''' |Group |- |'''o''' |Others |} You can use the following operators to modify permissions: {| class="wikitable" |+Mathematical Operators !Operator !Description |- |'''+''' |Adds a permission |- |'''-''' |Removes a permission |- |'''=''' |Sets permissions (overwrites existing permissions) |} ==== Examples ==== * Add execution (x) permission for the owner:<code> chmod u+x script.sh</code> * Remove read and write (r, w) permissions for group and others:<code> chmod go-rw file.txt</code> * Set write (w) permission for group and overwrite existing permissions:<code> chmod g=w file.txt </code> === Absolute Mode === Absolute mode uses numeric values to represent permissions. Each permission is assigned a value as shown below: {| class="wikitable" |+Numeric Representation of Permissions !Permission !Numeric Value |- |Read (r) |4 |- |Write (w) |2 |- |Execute (x) |1 |} The total value for a permission set is calculated by adding the numeric values for the desired permissions. For example: * Read (4) + Write (2) = 6 * Read (4) + Execute (1) = 5 ==== Example ==== To set permissions as: * User: Read (4), Write (2) and Execute (1) * Group: Read (4) and Execute (1) * Others: Execute (1) Use the following command:<code> chmod 751 file.txt </code> This results in `rwxr-x--x`. == How to Change Ownership in Linux == File and directory ownership can be changed using the `chown` command. Ownership can be assigned to users, groups, or both. === Syntax === <code> chown [user][:group] filename</code> * '''user''': Specifies the new owner. * '''group''': Specifies the new group owner. === Examples === * Change ownership to user "jdoe":<code> chown jdoe file.txt</code> * Change ownership to user "jdoe" and group "devteam":<code>chown jdoe:devteam file.txt</code> * Change ownership recursively for a directory and its contents:<code> chown -R admin /opt/scripts</code> * Change only the group ownership:<code> chown :admins /opt/scripts </code> 82eb3eb422d6b706175d58b19b37b320ff01fba0 0 405 2071 1681 2025-04-13T17:55:45Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Short page}} Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Examples of proprietary software are Microsoft Windows and Adobe Photoshop. [[Category:Terminology]] 030f3f836f4b08d1d78a2b131d86c6591102b03d 0 440 2072 1502 2025-04-13T17:56:36Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = ROSA Linux | image = [[File:ROSA_Linux_Logo.png|thumb]] | caption = The ROSA Linux logo | releasestatus = Abandoned | releasemodel = Stable | packagemanager = [https://rpm-software-management.github.io/ DNF package manager] | defaultdesktops = GNOME, [[KDE Plasma]], LXQt, [[Xfce]] | usagetype = Desktop, Server | architectures = P5 (i586), x86_64 | website = [https://rosa.ru/rosa-fresh-12/ rosa.ru/rosa-fresh-12] }} [[File:Rosalinux_desktop_showcase.jpeg|thumb|ROSA Linux Fresh 12 running on KDE Plasma 5 and has open Dolphin, Gwenview and mpvplayer]] '''ROSA Linux''' is a [[Linux Distributions|Linux distribution]] built around the '''OpenMandriva''', offering closed-source software such as Adobe Flash Player, proprietary multimedia codecs. It was initially developed by AO NTC IT ROSA. (rus. - АО «НТЦ ИТ РОСА») === Focus on KDE Plasma as the desktop environment. === ROSA Linux is known for its focus on the KDE Plasma desktop environment, which offers a rich graphical interface and extensive customization options. This makes it an attractive choice for users who appreciate a modern and aesthetically pleasing desktop experience. === Applications === The distribution includes a wide range of pre-installed applications, covering essential tasks such as web browsing, multimedia playback, and office productivity, while also providing access to a comprehensive software repository for additional applications. === Ease of use === One of the key features of ROSA Linux is its commitment to user experience, with an emphasis on ease of use and accessibility. The distribution is designed to be intuitive, making it suitable for both newcomers to Linux and experienced users. It also supports multiple languages, catering to a diverse user base. === Multiple editions. === ROSA Linux is available in several editions, including ROSA Fresh, which is aimed at general users and features the latest software updates, and ROSA Enterprise, which is tailored for business environments and focuses on stability and long-term support. With a strong emphasis on community involvement and open-source principles, ROSA Linux encourages contributions from users and developers alike. It has gained popularity in various regions, particularly in Russia and Eastern Europe, and continues to be a viable option for those seeking a reliable and visually appealing Linux distribution. fa66cc6a61a8d3f9b88d3b0fc820c3d1a724b5cf 0 277 2073 937 2025-04-13T17:59:21Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs_Citations}} == Introduction == {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_Logo.png|thumb]] | caption = Rocky Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] Rocky Linux is a Linux distribution developed by RESF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit". It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. [[Category:Linux Distributions]] 5197affac4871b7e7213288effc5f70a9056b125 0 319 2074 1785 2025-04-13T18:02:06Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs Citations}} '''Ricing''' (''slang'') refers to extensively customizing a [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to create a unique, personalized computing experience. The term originated from the automotive modification scene ("ricer" cars) and has been adopted by the Linux/Unix community. While primarily focused on aesthetic customization through themes, colors, widgets, and interface layouts, ricing can improve functionality and performance. Common ricing elements include: * Custom window borders, titlebars, decorations; * Color schemes and typography; * Specialized status bars and system monitors; * Custom application launchers and menus * Personalized desktop widgets and notifications * Modified system icons and cursors Popular tools for ricing include customization frameworks such as polybar and picom for window managers like i3, bspwm, and dwm. People frequently share configuration files, or "dotfiles," and screenshots - [https://www.reddit.com/r/unixporn/ r/unixporn] is one of the most popular. [[Category:Terminology]] 03e929fabd4570be101fba1bc7af25a569a862d7 0 447 2075 1513 2025-04-13T18:03:57Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs Citations}} === Introduction === Self-hosting is a rewarding practice that allows you to reduce reliance on cloud services, giving you much greater control and privacy over the data you own. By self-hosting, the services you use, and by extension anything you store with those services, reside on your own hardware rather than third-party servers. Essentially, the “cloud” is just someone else’s computer, often a large, multi-billion-dollar infrastructure. However, with self-hosting, you own the data on the devices you manage. === What is Self-Hosting? === Self-hosting often refers to the process of running and managing your own services on personal hardware such as a laptop, desktop, single-board computer, or even an enterprise-grade server. This means you can set up and operate services for yourself, your family, or others without depending on external cloud platforms. === What Can I Host? === There are numerous possibilities for self-hosting, depending on your needs. Some popular options include: * Email server * Password manager * Personal website * File hosting service * Media server * VPN (Virtual Private Network) === Do I Need Anything Special to Self-Host? === [[File:Homelab.jpg|thumb|Example of an enterpise grade homelab]] The requirements are minimal. You can self-host using almost any device, from an old, cheap laptop to a single-board computer like a Raspberry Pi. Some enthusiasts take this a step further and use second-hand enterprise equipment from real data center infrastructure to host their services. These setups are often referred to as “HomeLabs.” However, anything that can connect to the internet or your local area network can be sufficient. === The Challenges of Self-Hosting === Like everything in life, self-hosting has its challenges. When hosting services at home, you are responsible for maintaining and fixing any problems that arise. Unlike cloud services, which are typically plug-and-play, homelabs require regular maintenance to ensure stable operation. Below are some challenges many homelab users encounter. ==== Common Problems ==== * '''Electricity Usage''' - One of the main concerns with starting a homelab is power consumption. As your homelab grows, so will its electricity usage. Additionally, the services you run rely on your home's power grid, meaning power outages can affect your services. [[File:Speedtest.png|thumb|Example of a users internet speed.]] * '''Internet Speed''' - Not all internet connections are equal. When exposing services to the outside world, consider how much bandwidth they will consume. A slow connection or data caps can limit what you can host effectively. Residential internet plans might not support the load or violate fair use policies. Like the electricity usage, you are relying on the reliance your ISP provides. * '''Natural Disasters''' - Hosting services in areas prone to natural disasters poses risks. If a disaster damages your homelab, your data may be lost along with the equipment. * '''Vulnerabilities''' - Even with the latest software and hardware, vulnerabilities persist. Tools like Shodan.io scan for exposed services, potentially attracting malicious actors. Without sufficient protection, your services may be at risk. * '''Hardware Failures''' - Nothing lasts forever. Self-hosted services depend on your hardware, which will need maintenance and occasional replacement. Hard drives, in particular, are susceptible to failure over time. * '''Sound''' - Unlike a laptop or a single-board computer, enterprise equipment is not built to be quiet. It is designed to run cool and avoid failure, which often results in high-pitched fan noise due to large amounts of airflow. * '''Dust''' - Most homelabs are not housed in ventilated data centers, leading to dust accumulation, which can clog and damage equipment. * '''User Error''' - Mistakes happen. Deleting the wrong files, modifying incorrect configurations, or failing to double-check changes can lead to data loss or downtime. === Solutions === [[File:Ups uninterruptible power supply.jpg|thumb|An example of an (UPS) Uninterruptible Power Supply]] * '''Electricity Usage''' - Use an Uninterruptible Power Supply (UPS). A UPS acts as a battery backup and protects against power surges. If the power goes out, the UPS switches to battery mode to keep your equipment running. UPS devices can range from small 600W models to large 10kW units that can power enterprise equipment for hours. * '''Internet Speed''' - If your internet is slow or capped, consider upgrading to a better plan if available. Some ISPs offer small business plans for residential users, providing higher speeds, service agreements, and multiple external IP addresses. * '''Natural Disasters''' - Perform regular off-site backups. Store data in locations unaffected by the same natural disasters as your homelab to ensure redundancy. * '''Vulnerabilities''' - To mitigate vulnerabilities some examples include: ** Keep all software and hardware up to date. ** Change default ports for commonly scanned services. ** Install a firewall. ** Use a VPN to access services instead of exposing them directly to the internet. ** Use encrypted protocols and storage. [[File:raid failure.png|thumb|An example of a drive failing in a raid.]] *'''Hardware Failures''' - Practice the 3-2-1 backup strategy: ** Keep at least THREE copies of your data. ** Use at least TWO types of storage. ** Keep at least ONE copy off-site. * '''Sound''' - To mitigate noise, consider buying fanless equipment, as fans are the primary source of noise. Alternatively, place the equipment in a room that is not frequently used to minimize sound. Keep in mind that fanless equipment carries a risk of overheating. * '''Dust''' - Regularly clean your equipment and store it in well-ventilated areas. Use compressed air or vacuum cleaners to remove dust. * '''User Error''' - Double-check all changes, avoid running unfamiliar commands, and thoroughly understand what you are deploying. fde152101e0ce5186c27bae37ab07981c03414cf 2 3 2076 1939 2025-04-13T18:04:06Z Amadaluzia 52 Add more content wikitext text/x-wiki <syntaxhighlight lang="rust"> use std::collections::HashMap; struct AboutMe<'a> { name: &'a str, desc: &'a str, socials: HashMap<&'a str, &'a str>, } fn main() { let amadaluzia = AboutMe { name: "Artur Manuel", desc: r#" I live in the UK and the internet as a background character in many free software communities (for example: you may find me on some mailing list) but I also contribute, most notably in nixpkgs. I do have other interests, such as gym, walking and photography, as well as speedrunning, filming and revising for english/maths among other things. "#, socials: HashMap::from([ ("matrix", "@amadaluzia:tchncs.de"), ("email", "amad@atl.tools"), ("signal", "amadaluzia.711"), ("libera.chat", "amadaluzia"), ("xmpp", "amadaluzia@xmpp.jp"), ("github", "amadaluzia"), ("codeberg", "amadaluzia"), ("sourcehut", "amadaluzia"), ("discord", "amadaluzia"), ]), }; println!( "Hello! I am {}! You may find me on the following platforms:", amadaluzia.name ); for i in amadaluzia.socials.iter() { println!("{} on {}", i.1, i.0) } println!( "{}", amadaluzia .desc .split_terminator('\n') .map(|s| s.trim()) .collect::<Vec<&str>>() .join("\n") ); } </syntaxhighlight> 9dc049b8c65873c423ce199b7277b1a6b9d6312c 0 304 2077 1677 2025-04-13T18:05:12Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a [[UNIX-like]] [[Operating System|operating system]] completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS]</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive [[kernel]], and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[MacOS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[Virtual Machine|virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to [[Compiling|compile]] software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub]</ref> [[Category:Misc Operating Systems]] c4ded684cf6ade2c22198c32f620a8db1f7aae2b 0 233 2078 1840 2025-04-13T18:05:33Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. [[Category:Linux Distributions]] 763b96e25b5d6b0b541fe0d4fe87e39d55c0de2c 0 574 2079 1924 2025-04-13T18:07:34Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes great inspiration from [[I3]] in its design and configuration, and, consequently, it is very compatible with [[I3]]. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[Swayfx]] is a fork of Sway that adds cool effects, animations, and visuals to it, something you may want to look into. === Notable Features: === According to Sway's official website: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. == Pre-Installation: == * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] == Installation: == ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For Arch: ==== Using pacman: sudo pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For Debian: ==== Using apt package manager: apt install sway 4e488ceb3c90c04b556e5072db694c3539203326 0 517 2080 1656 2025-04-13T18:11:17Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Cleanup|Installation instructions should be separated onto their own Guides page.}} {{Needs_Citations}} = What is a System Call? = A system call (syscall) is a mechanism that allows a program to interact with the operating system. It acts as a bridge between the user space (where applications run) and the kernel space (where the operating system manages hardware and system resources). Programs use system calls to request services from the OS, such as managing files, processes, or hardware devices. For example, when you open a file, your application cannot directly access the hardware. Instead, it makes a system call (e.g., open()), which the OS handles to perform the requested task. Note that this is not a guide for ALL syscalls, but it is a guide to get you familiar enough with syscalls and strace. == Why Should You Learn About System Calls? == 1. Understanding How Programs Work: - System calls reveal how applications interact with the operating system to perform tasks like file handling, memory management, and networking. 2. Efficient Troubleshooting: - Knowing system calls can help diagnose performance issues or bugs by identifying which calls a program relies on. 3. Optimizing Software: - When developing programs, understanding system calls allows you to write efficient code by leveraging the right OS-level functions. 4. Security Awareness: - Many exploits and vulnerabilities target how system calls are used (or misused). Understanding them helps in writing secure code. 5. Kernel-Level Development: - If you're interested in low-level programming, such as operating system development or driver creation, system calls are fundamental. Basically, system calls are the foundation of how software and operating systems interact, making them essential knowledge for both beginner and advanced developers. == Categories of System Calls == System calls are grouped into five main categories: '''Process Control''' – Manage processes (create, terminate, etc.). '''File Management''' – Handle file operations (open, read, write, close). '''Device Management''' – Interact with hardware devices. '''Information Maintenance''' – Exchange information between the OS and programs. '''Communication''' – Enable processes to communicate. 1. '''Process Control''' * fork(): Creates a new process (child) that runs the same program as the parent. * exit(): Terminates the process and frees resources. * exec(): Replaces the current program in a process with a new one. 2. '''File Management''' * open(): Opens a file for reading or writing. * read(): Reads data from a file (multiple processes can read simultaneously). * write(): Writes data to a file (only one process can write at a time). * close(): Closes an open file. 3. '''Device Management''' * ioctl(): Performs device-specific operations not covered by standard calls (e.g., configuring hardware). 4. '''Information Maintenance''' * getpid(): Returns the process ID of the current process. * alarm(): Sets a timer to deliver a signal after a specified time. * sleep(): Pauses the process for a given time. 5. '''Communication''' * pipe(): Enables communication between processes via file descriptors. * shmget(): Allocates shared memory for process communication. * mmap(): Maps files or devices into a process’s memory. == Using strace to Look at System Calls == strace is a command-line tool that lets you see the system calls a program makes while it runs. It’s great for debugging, understanding program behavior, or learning how system calls work. === How to use strace === Steps to Use strace: 1. '''Run a Command with strace''': <syntaxhighlight lang="bash">strace <command></syntaxhighlight> This will show all the system calls made by the command. 2. '''Attach to a Running Process''': If a program is already running, use its process ID (PID): <syntaxhighlight lang="bash">strace -p <PID></syntaxhighlight> 3. '''Filter Specific System Calls''': To narrow down the output, trace specific system calls using the -e option: <syntaxhighlight lang="bash">strace -e <syscall> <command></syntaxhighlight> 4. '''Save Output to a File''': Use -o to redirect the output to a file for easier analysis: <syntaxhighlight lang="bash">strace -o trace_output.txt <command></syntaxhighlight> 5. '''Trace Execution Times''': To see how long each system call takes, use: <syntaxhighlight lang="bash">strace -T <command></syntaxhighlight> === Why Use strace? === * Debug program behavior (e.g., "Why is this program failing?"). * Identify which files, devices, or network resources a program accesses. * Learn what system calls a program makes for educational purposes. cd8946c6c4c1bb18857a316780a98c5e91406c77 0 516 2081 1655 2025-04-13T18:13:50Z Atmois 13 Add cleanup and citations tags wikitext text/x-wiki {{Cleanup|Instructions should be seperated into its own Guide page}} {{Needs_Citations}} == Understanding Systemd == Systemd is an init system and service manager used by many modern Linux distributions. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here’s how Systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': Systemd provides a unified system for managing services, devices, logs, and even network interfaces. * '''Dependency Management''': Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': Systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in Systemd == Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit’s dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''Systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''Systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''Systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential Systemd Commands == Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash">systemctl start service-name</syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash">systemctl stop service-name</syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash">systemctl restart service-name</syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash">systemctl enable service-name</syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash">systemctl disable service-name</syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the `/lib/systemd/system/` directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there. * Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. '''Runtime Directory''' The `/run/systemd/system/` directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File '''sudo nano /etc/systemd/system/daily-script.service''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File '''sudo nano /etc/systemd/system/daily-script.timer''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer '''sudo systemctl enable daily-script.timer''' '''sudo systemctl start daily-script.timer''' 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: '''systemctl list-timers''' This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With OnCalendar, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from `/lib/systemd/system/` to `/etc/systemd/system/` and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with `.d`. Example: To modify `dummy.service`, create a folder named `dummy.service.d` in `/etc/systemd/system/`. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a `.conf` file to specify your changes. Example: `/etc/systemd/system/dummy.service.d/custom.conf`. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. /etc/systemd/system/ (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. /run/systemd/system/ (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. /lib/systemd/system/ (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. '''systemctl status service-name''' * Displays the status of a specific service, including whether it's running and any associated error messages. 2. '''journalctl -u service-name''' * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. '''systemctl list-units --failed''' * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. '''systemctl daemon-reload''' * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. 673a9ee596e6780a56ea1f85a365d76af0ebd783 0 174 2082 1683 2025-04-13T18:15:00Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Incomplete page}}[[File:Debian-Installer 10 Tasksel.svg|alt=Debian TUI installer|thumb|Debian 10 installation, which uses a TUI installer]] A '''TUI''' (Terminal User Interface) generally refers to an application that solely exists within the terminal as a text-based application - this means that all of its content is rendered using letters and other unique characters to create a graphical interface. [REFERENCE POSSIBLE] Because of its independence from a ... , [[Category:Terminology]] 27a21fdac7bc2e74fb7a04a9834fcb75ece64291 0 341 2083 1862 2025-04-13T18:16:38Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Cleanup|Incomplete page}} {{Needs_Citations}} {{SoftwareInfobox | image = [[File:Tde-logo.png]] | caption = Trinity Desktop Environment logo | title = Trinity Desktop Environment | releasestatus = Maintained | lastrelease = R14.1.3, 2024-10-27 | languages = C | developers = Trinity Development Team | website = [https://www.trinitydesktop.org/ trinitydesktop.org] }} [[File:Trinity R.14.1.3 screenshot.png|thumb|Screenshot of Trinity Desktop R14.1.3]] Trinity Desktop Environment is an X11 desktop environment forked from KDE 3 in 2010. [[Category:Desktop Environments]] 4612ba2a5da12ad25aa0b6b94833955dd31fb64e 0 214 2084 1753 2025-04-13T18:17:04Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Tux | image = [[File:Tux.svg|Tux|thumb]] | caption = Tux! }} '''Tux''' is the official mascot of [[Linux]], designed by Larry Ewing<ref>https://web.archive.org/web/20040401161253/http://www.linux.org/info/logos.html</ref>. Tux was created for the Linux 2.0 logo competition<ref>https://web.archive.org/web/20040407092622/http://www.cs.earlham.edu/~jeremiah/linux-pix/linux-logo.html</ref>.<references /> [[Category:Mascots]] ad4889aa9a9c912019d25c8464027966aeed9b93 0 568 2085 1882 2025-04-13T21:01:43Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs_Citations}} {{MascotInfobox | title = Xue | image = [[File:Xfce-xue.jpg|thumb]] | caption = Xue the XFCE mascot }} Xue is the mascot of [https://xfce.org/ XFCE] Xue is described as a black female mouse in [https://supertuxkart.net/Main_Page SuperTuxKart] [[Category:Mascots]] 0f51954089ba25ac2631a91b427e2f53990f59a3 0 236 2086 1477 2025-04-13T21:03:00Z Atmois 13 Add citations tag wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.20, 2024-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * Desktop Manager - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[Terminal Emulator|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> [[Category:Desktop Environments]] 1d892f2c3f5fb939d02458908b385a5bbac703bb 0 317 2087 1554 2025-04-13T21:05:08Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [https://docs.voidlinux.org/xbps/index.html XBPS] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution made from scratch. Created in 2008 by Juan Romero Pardines, Void distinguishes itself through unique design choices including the runit init system, home-grown XBPS package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * runit init system instead of systemd * Choice between glibc and musl libc implementations * Rolling release model with stable package testing * Minimal base system with high customizability * Native support for both x86 and ARM architectures === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == Package Management == === XBPS (X Binary Package System) === XBPS is Void's native package manager, offering: * Fast dependency resolution * Binary and source package support * Package signing and verification * Repository management tools * Local package building {| class="wikitable" style="margin:auto" ! Command !! Description !! Common Usage |- | xbps-install || Package installation and system updates || <code>xbps-install -S</code> (sync)<br><code>xbps-install -u</code> (update) |- | xbps-remove || Package removal and cleanup || <code>xbps-remove -R pkg</code> (remove with deps)<br><code>xbps-remove -O</code> (clean orphans) |- | xbps-query || System and repository queries || <code>xbps-query -Rs pkg</code> (search)<br><code>xbps-query -l</code> (list installed) |- | xbps-reconfigure || Package reconfiguration || <code>xbps-reconfigure -f pkg</code> (force reconfigure) |- | xbps-alternatives || Alternative management || <code>xbps-alternatives -l</code> (list alternatives) |} == System Management == === Init System === Void uses runit as its init system, offering: * Simple service management * Clean daemon supervision * Fast boot times * Reliable service logging {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] [[Category:Linux Distributions]] fd8046a62eb01497f990cacb4eaa373a54ec7da8 0 281 2088 1114 2025-04-13T21:08:27Z Atmois 13 Add cleanup tag wikitext text/x-wiki {{Cleanup|Installation instructions need to be separated onto its own page in the Guides namespace & citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home]</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home]</ref> === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight> On [[Void Linux]]: <syntaxhighlight lang="bash"> sudo xbps-install windowmaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more.<references /> [[Category:Window Managers]] 0f640c25d1043333dd8a542732a632926d75de4f 0 248 2089 1213 2025-04-13T21:10:00Z Atmois 13 Add cleanup and citations tag wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} == Introduction == {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = GNOME, Unity | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu, is a [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubtuntu receives 9 months of support.<ref>https://ubuntu.com/about/release-cycle</ref> <references /> [[Category:Linux Distributions]] fb9c2c160f6a420a8605bd4073370e398f025a2f 0 306 2090 1757 2025-04-13T21:10:55Z Atmois 13 Page pending rework to separate into WM and compositors wikitext text/x-wiki {{Work_In_Progress}} A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[GUI|Graphical User Interface (GUI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm * [[Wayfire]] ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[i3]] * [[Sway]] * [[SwayFx]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[dwl]] * [[qtile]] * [[Hyprland]] * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] ==== Scrollable Window Managers ==== Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[niri]] * [[PaperWM]] * [[karousel]] * [[papersway]] * [[hyprscroller]] * [[hyprslidr]] * [[PaperWM.spoon]] [[Category:Terminology]] 0c9abbc3335ff7eaa2d2e6a9741ef8682136459b 4 327 2091 1888 2025-04-14T09:48:09Z Atmois 13 Transclusion test wikitext text/x-wiki Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen electron was here {{Special:Contribute}} more testing???? test n 1203 idk potato testing testing 1 2 3 4<ref>hi</ref> {{MascotInfobox | title = Test | image = [[File:Larry the cow.png|Larry the Cow]] | caption = Test }} 6d413c437d3034ef1ae625c96fb6c7d60cb625b4 10 205 2092 1746 2025-04-14T13:31:03Z Atmois 13 Remove category tag wikitext text/x-wiki <includeonly>{{#invoke:SoftwareInfobox|main}}</includeonly> <noinclude>{{/doc}}</noinclude> d849369e71311b7efdd1adbff1de016be089e1df 10 162 2093 1723 2025-04-14T13:31:09Z Atmois 13 Remove category tag wikitext text/x-wiki <includeonly>{{#invoke:DistributionInfobox|main}}</includeonly> <noinclude>{{/doc}}</noinclude> 2142a38a1ae68da00c2a87ce1ef76c0923fae7a3 10 208 2094 1748 2025-04-14T13:31:15Z Atmois 13 Remove category tag wikitext text/x-wiki <includeonly>{{#invoke:MascotInfobox|main}}</includeonly> <noinclude>{{/doc}}</noinclude> c36d7ff1b6cb50d7f0ba5e04a0773be754b0f03c 6 590 2095 2025-04-15T16:09:55Z Atmois 13 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1 2096 1998 2025-04-15T16:11:24Z Atmois 13 Add CTA image wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:About#Staff|about#staff]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[policies]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * For users interested in creating guides for atl.wiki, ensure to check out [[Guides:Contributing]]! ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact an administrator via the methods listed on [[Atl.wiki:About#Staff|about#staff]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ c12afc7fa29be5312a990c0979921cfdb92a8f63 0 198 2097 1684 2025-04-18T13:03:18Z Atmois 13 Move openSUSE under other distros wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments||Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a Calamares installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from FOSS solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 25500b1dfc0dea0eec91905a3c5f194826824d81 0 540 2098 1795 2025-04-18T13:05:17Z Atmois 13 Change redirect wikitext text/x-wiki #REDIRECT [[Atl.wiki:Contributing]] ea1ae6152681dc1f296b81069c9c2fd6ca648c13 2 591 2099 2025-04-18T13:46:23Z Katz 53 bringing over Slackware page to here to prepare the overhaul wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=Slackware Linux|image=[[File:Slackware logo.svg|Slackware_logo]]|caption=Slackware Linux logo|releasestatus=Maintained|releasemodel=Stable, Rolling Release (Slackware -Current)|packagemanager=[[pkgtool]], slackpkg|defaultdesktops=[[KDE Plasma]], [[Xfce]]|usagetype=Desktop, Server|architectures=arm, i586, s390, x86_64|website=[http://www.slackware.com slackware.com]}} [[File:Slackware_15.0_screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. 0824408bffb8e87ced84f85ee3bbd49972ffb962 14 294 2100 1240 2025-04-18T14:51:10Z Atmois 13 Add redirect wikitext text/x-wiki #REDIRECT [[Key Terms]] 8bd6c2b36726c38e712a9c8dbf427c6543eb40d6 10 483 2101 2016 2025-04-18T17:10:39Z Atmois 13 Fix weird category thing wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[Policies#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /> <includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]] }} </includeonly> 420cd94897e9b8b9f9625b17d102c924860bdbfc 2102 2101 2025-04-18T17:11:42Z Atmois 13 Fix missing docs wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[Policies#Standards|quality standards]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /> <includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]] }} </includeonly> <noinclude> {{/doc}}</noinclude> f1a2a31bed28ce561a0a65d729978e4ac624fd04 2115 2102 2025-04-19T20:48:24Z Atmois 13 Update link wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /> <includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]] }} </includeonly> <noinclude> {{/doc}}</noinclude> 47aa4eadce2fd56fd53e1220b1ebb7bbd3ce4057 10 513 2103 1917 2025-04-18T17:12:18Z Atmois 13 Fix category thing wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This template is to be used on pages which may lack credible citations, as per our [[Policies#Citations|citations policy]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]] }} </includeonly> <noinclude> {{/doc}}</noinclude> 54c205e12abcaf36c69cb2d007d747e1d0aff992 2104 2103 2025-04-18T17:13:39Z Atmois 13 Fix link wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This template is to be used on pages which may lack credible citations, as per our [[Policies#Citations|citations policy]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Needs_Citations|| [[Category:Needs_Citations]] }} </includeonly> <noinclude> {{/doc}}</noinclude> 7b0f866705e57366414d25ebb25b72e9be214cad 2114 2104 2025-04-19T20:47:56Z Atmois 13 Update link wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This template is to be used on pages which may lack credible citations, as per our [[Guidelines#Citations|citations guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Needs_Citations|| [[Category:Needs_Citations]] }} </includeonly> <noinclude> {{/doc}}</noinclude> cbadad9ee69bbf2cc5011543774fc0ca7ee5b48c 8 592 2105 2025-04-19T10:13:07Z Atmois 13 Add licenses for images wikitext text/x-wiki * Unknown_copyright|I don't know exactly * Free licenses: ** PD|PD: public domain ** CC0|Creative Commons Zero ** CC-BY-4.0|Creative Commons Attribution 4.0 ** CC-BY-SA-4.0|Creative Commons Attribution Sharealike 4.0 ** GPL|GPL: GNU General Public License ** LGPL|LGPL: GNU Lesser General Public License 5b8003db3f1c30a000ede68b272674b86a22a065 2106 2105 2025-04-19T10:13:40Z Atmois 13 Update names wikitext text/x-wiki * Unknown_copyright|I don't know exactly * Free licenses: ** PD|PD: public domain ** CC0|Creative Commons Zero ** CC-BY-4.0|Creative Commons Attribution 4.0 ** CC-BY-SA-4.0|Creative Commons Attribution Sharealike 4.0 ** GPL|GNU General Public License ** LGPL|GNU Lesser General Public License a36a906dfd4bbbff1490dbf7eeddc75df211ec12 2107 2106 2025-04-19T10:13:59Z Atmois 13 Update names p2 wikitext text/x-wiki * Unknown_copyright|I don't know exactly * Free licenses: ** PD|Public Domain ** CC0|Creative Commons Zero ** CC-BY-4.0|Creative Commons Attribution 4.0 ** CC-BY-SA-4.0|Creative Commons Attribution Sharealike 4.0 ** GPL|GNU General Public License ** LGPL|GNU Lesser General Public License 3ca66abc8b387d084a3ab16709fc2df255d69020 4 593 2108 2025-04-19T10:39:05Z Atmois 13 Start contributing guide wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. === Using Images === There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. 9c4edc6b1bf9351059a36bc45b88df8a19db5683 2117 2108 2025-04-19T20:53:41Z Atmois 13 Add more info wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. === Using Images === There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki, these due to the nature of running code or acting as a reusable component cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. 6c996c498ee348dac836f802510be38a002952ff 4 340 2109 1975 2025-04-19T20:41:43Z Atmois 13 Atmois moved page [[Policies]] to [[Guidelines]] over redirect: better title name wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Policies#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Policies#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] 8b95062252740243376119affd901e7e05c5e463 2111 2109 2025-04-19T20:43:10Z Atmois 13 Update link wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Guidelines#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] 67f57c68b82e378e0724ae857575c75d17a8c577 0 594 2110 2025-04-19T20:41:43Z Atmois 13 Atmois moved page [[Policies]] to [[Guidelines]] over redirect: better title name wikitext text/x-wiki #REDIRECT [[Guidelines]] bb3d014a214db62e3828d9a8805dc1427011f38d 0 1 2112 2096 2025-04-19T20:46:56Z Atmois 13 Update links wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:About#Staff|about#staff]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make ATL Wiki a better source of information! ====== Where to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * For users interested in creating guides for atl.wiki, ensure to check out [[Guides:Contributing]]! ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact an administrator via the methods listed on [[Atl.wiki:About#Staff|about#staff]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ 9557853dc453fad1e3bb506547fea9292242166f 2118 2112 2025-04-21T09:30:27Z Atmois 13 Update where to start info wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:About#Staff|about#staff]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! ====== Where to Start ====== The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide, if you are interested in writing guides you may also want to check out [[Guides:Contributing]]. These pages will give you everything you need to start editing, if you are still unsure [[Atl.wiki:Contact|contact us]]! * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact an administrator via the methods listed on [[Atl.wiki:About#Staff|about#staff]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ 642fd2ef232587bf3e9998baa9e75d4dde0c1154 10 523 2113 1915 2025-04-19T20:47:28Z Atmois 13 Update link wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This template means the author of a page is still actively working on the page, and this serves to notify other editors to check with them before potentially creating conflicting changes and to notify the staff that it may not meet the [[Guidelines|wiki guidelines]] yet.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> e6587ab065cb1f913b3dca63262fd97014642cb8 2116 2113 2025-04-19T20:48:48Z Atmois 13 fix text wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This template means the author of a page is still actively working on the page, and this serves to notify other editors to check with them before potentially creating conflicting changes and to notify the staff that it may not meet the wiki's [[Guidelines|guidelines]] yet.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 143d45ab2abe61ea7d1e8917b5bd1edde0dbf04e 4 595 2119 2025-04-21T10:04:38Z Atmois 13 Create contact page wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.gg/linux Discord Server] and asking for help in the <code>#atl-wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for a Wiki Administrator. You may also direct message <code>@atmois</code> (Head of Wiki Operations) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''wiki(at)allthingslinux.org,'' please '''<u>DO NOT</u>''' send sensitive information to this email, if you wish to disclose vulnerabilities or wish for more secure communications please contact a sysadmin directly using their PGP key. * [[User:Atmois|Atmois]] - Head of Wiki Operations ** ''atmois(at)allthingslinux.org'' ** PGP: https://atl.wiki/atmois@allthingslinux.org-pubkey.asc * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner ** ''kaizen(at)allthingslinux.org'' * [[User:Scottc96|Scott96]] - Sysadmin ** ''scott(at)allthingslinux.org'' 565cdfd537f2c3ceabe2489a35a71d1898ba7d63 4 556 2120 1972 2025-04-21T10:04:48Z Atmois 13 Move contacts to its own page wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[Atl.wiki:Contact|contact page]]! == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin f7b38c41abb8abf19fdaf22a0e3062aeaa8947fb 8 409 2121 1411 2025-04-21T10:19:44Z Atmois 13 Add link for IA wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki * SEARCH * TOOLBOX * LANGUAGES * misc **{{fullurl:{{FULLPAGENAMEE}}|action=raw}}|View raw wikitext 9e2ab8cbbc9aa61f0a5d4c97446e00ed0f1213b6 2122 2121 2025-04-21T10:20:46Z Atmois 13 Update format wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki * SEARCH * TOOLBOX * LANGUAGES *{{fullurl:{{FULLPAGENAMEE}}|action=raw}}|Raw wikitext 36b9b285c89b684684e30324e4569a1aa5991c53 2123 2122 2025-04-21T10:21:33Z Atmois 13 Change order wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki *{{fullurl:{{FULLPAGENAMEE}}|action=raw}}|Raw wikitext * SEARCH * TOOLBOX * LANGUAGES 8264be978b3effa7e3a75a151aedc918d7cec80d 2124 2123 2025-04-21T10:21:44Z Atmois 13 Fix order wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki **{{fullurl:{{FULLPAGENAMEE}}|action=raw}}|Raw wikitext * SEARCH * TOOLBOX * LANGUAGES bde5d16a1a180bb4913c131acdfa079055ec76b4 2125 2124 2025-04-21T10:25:59Z Atmois 13 Attempt to fix? wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki ** [{{fullurl:{{PAGENAME}}|action=raw}} Raw wikitext] * SEARCH * TOOLBOX * LANGUAGES d5b427678171122d15e514a5d83adeace4f0318e 2126 2125 2025-04-21T10:27:04Z Atmois 13 Revert wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki ** {{fullurl:{{FULLPAGENAMEE}}|action=raw}}|View raw wikitext * SEARCH * TOOLBOX * LANGUAGES 643250d9d756203656e811e688223a1a0966a992 2127 2126 2025-04-21T10:27:51Z Atmois 13 revert wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help-mediawiki * SEARCH * TOOLBOX * LANGUAGES df7c604d036435a413d00baa4fd183f6a56b1543 8 400 2128 1887 2025-04-21T10:36:41Z Atmois 13 Add raw link for IA wikitext text/x-wiki This is the official wiki by the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server! You can see the raw content for the page you are on [{{fullurl:{{PAGENAME}}|action=raw}} here]! 379c139d31f70d752dfc2f7ed92d2944f600b3cd 0 227 2131 1674 2025-04-21T13:06:08Z Atmois 13 Change category wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:Window Management Systems/X_Window_Manager]] f4cb94c5f01dfe07c00a4c7ba592d31687d69b09 2146 2131 2025-04-21T13:39:31Z Atmois 13 Update category wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:X_Window_Manager]] ffc556be66916e90a5937185b5dfcd777f66901d 14 597 2132 2025-04-21T13:06:09Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Window Management Systems/X Window Manager" as well as all subcategories of category "Window Management Systems/X Window Manager" if any exist. 128a44f3418360a72b21361ab7abc4715f5e37b4 2143 2132 2025-04-21T13:38:16Z Atmois 13 Atmois moved page [[Category:Window Management Systems/X Window Manager]] to [[Category:X Window Manager]] without leaving a redirect: Shorter wikitext text/x-wiki This is a category page. It lists all of the pages in category "Window Management Systems/X Window Manager" as well as all subcategories of category "Window Management Systems/X Window Manager" if any exist. 128a44f3418360a72b21361ab7abc4715f5e37b4 2149 2143 2025-04-21T13:40:40Z Atmois 13 Make subcategory wikitext text/x-wiki This is a category page. It lists all of the pages in category "Window Management Systems/X Window Manager" as well as all subcategories of category "Window Management Systems/X Window Manager" if any exist. [[Category:Window Management Systems]] 5291aad6bb689a1cc47d4e70c40a669e388e5acf 0 257 2134 2040 2025-04-21T13:15:46Z Atmois 13 Update category wikitext text/x-wiki {{Needs Citations}} {{Cleanup|Installation instructions should be separated onto its own page in the Guides namespace}} {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) === Installation === This section will change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Window Management Systems/Wayland_Compositors]] 0a5805852bf09a00def8c257e087b13581ffaabc 2144 2134 2025-04-21T13:38:56Z Atmois 13 Update category wikitext text/x-wiki {{Needs Citations}} {{Cleanup|Installation instructions should be separated onto its own page in the Guides namespace}} {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window manager that aim for pure eye candy with nice animations, smooth looks and it's own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) === Installation === This section will change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Wayland_Compositors]] be4f2bf6b770943873ce297a9dc79f8f8c6659bd 14 598 2135 2025-04-21T13:15:46Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Window Management Systems/Wayland Compositors" as well as all subcategories of category "Window Management Systems/Wayland Compositors" if any exist. fef503a8dfdb4a23b0e469a0887aa69229a26dc5 2141 2135 2025-04-21T13:37:01Z Atmois 13 Add category wikitext text/x-wiki This is a category page. It lists all of the pages in category "Window Management Systems/Wayland Compositors" as well as all subcategories of category "Window Management Systems/Wayland Compositors" if any exist. [[Category:Window Management Systems]] 9c13a7f096420dcc1f84da6522243c235f122bf2 2142 2141 2025-04-21T13:37:42Z Atmois 13 Atmois moved page [[Category:Window Management Systems/Wayland Compositors]] to [[Category:Wayland Compositors]] without leaving a redirect: Shorter wikitext text/x-wiki This is a category page. It lists all of the pages in category "Window Management Systems/Wayland Compositors" as well as all subcategories of category "Window Management Systems/Wayland Compositors" if any exist. [[Category:Window Management Systems]] 9c13a7f096420dcc1f84da6522243c235f122bf2 0 239 2136 2041 2025-04-21T13:16:35Z Atmois 13 Update category wikitext text/x-wiki {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} {{Needs_Citations}} {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:Window Management Systems/X_Window_Manager]] 038674c9c9a9937ef33a4e3dc5e43e70945b08b0 2147 2136 2025-04-21T13:39:45Z Atmois 13 Update category wikitext text/x-wiki {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} {{Needs_Citations}} {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:X_Window_Manager]] 6cc775d731e7ea7951a2d4fe802c2fefb86770fb 0 281 2137 2088 2025-04-21T13:16:51Z Atmois 13 Update category wikitext text/x-wiki {{Cleanup|Installation instructions need to be separated onto its own page in the Guides namespace & citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home]</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home]</ref> === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight> On [[Void Linux]]: <syntaxhighlight lang="bash"> sudo xbps-install windowmaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more.<references /> [[Category:Window Management Systems/X_Window_Manager]] 07db6755595dc126a91b192a548a2c30792e2abb 2148 2137 2025-04-21T13:39:58Z Atmois 13 Update category wikitext text/x-wiki {{Cleanup|Installation instructions need to be separated onto its own page in the Guides namespace & citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home]</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home]</ref> === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight> On [[Void Linux]]: <syntaxhighlight lang="bash"> sudo xbps-install windowmaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more.<references /> [[Category:X_Window_Manager]] 9c4adbd4d65ae63fc51f1a82edf3dfa8497b5243 0 254 2138 1805 2025-04-21T13:18:01Z Atmois 13 Update category wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:Window Management Systems/X_Window_Manager]] c5e62ec5799c0bec33db88c1adb241a842795f41 2145 2138 2025-04-21T13:39:18Z Atmois 13 Update category wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Manager]] b590dbda471a7774432aca709b603c276357025c 2150 2145 2025-04-21T13:41:35Z Atmois 13 Typo fix wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] 0de8abfc7d0e5cae9f70fe4167a6da96f387f8e6 0 306 2139 2090 2025-04-21T13:20:39Z Atmois 13 Add category wikitext text/x-wiki {{Work_In_Progress}} A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[GUI|Graphical User Interface (GUI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm * [[Wayfire]] ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[i3]] * [[Sway]] * [[SwayFx]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[dwl]] * [[qtile]] * [[Hyprland]] * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] ==== Scrollable Window Managers ==== Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[niri]] * [[PaperWM]] * [[karousel]] * [[papersway]] * [[hyprscroller]] * [[hyprslidr]] * [[PaperWM.spoon]] [[Category:Terminology]] [[Category:Window Management Systems]] 6f44cc47a809bfcf3f15dc4eab874bf6a9aedd87 14 599 2140 2025-04-21T13:20:39Z Automatic category creator 64 Created automatically by the AutoCreateCategoryPages extension. wikitext text/x-wiki This is a category page. It lists all of the pages in category "Window Management Systems" as well as all subcategories of category "Window Management Systems" if any exist. df90b2c18f828eab18a243e8cdfd415e56938570 0 227 2152 2146 2025-04-21T13:41:42Z Atmois 13 Typo fix wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Installation === i3 can be installed on most package managers. ==== On [[Debian]] and Debian-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions:<!-- idk if this is right lol, if you use fedora please fix it -->==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:X_Window_Managers]] dc03c933dc59c81b4787c829ec59c16d86cf238e 0 239 2153 2147 2025-04-21T13:41:51Z Atmois 13 Typo fix wikitext text/x-wiki {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} {{Needs_Citations}} {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], C | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 window manager. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. === Installation === IceWM can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref> <syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> [[Category:X_Window_Managers]] a8af4e350218b5f472691db8e0959d1cb78701d1 0 281 2154 2148 2025-04-21T13:42:01Z Atmois 13 Typo fix wikitext text/x-wiki {{Cleanup|Installation instructions need to be separated onto its own page in the Guides namespace & citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home]</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home]</ref> === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions: <syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight> On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]: <syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight> On [[Gentoo]] and Gentoo-based distributions: <syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight> On [[RHEL]], [[Fedora]] and Fedora-based distributions: <syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight> On [[Void Linux]]: <syntaxhighlight lang="bash"> sudo xbps-install windowmaker </syntaxhighlight> If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running: <syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more.<references /> [[Category:X_Window_Managers]] 6f66a4d6ac215c35bba3a2e4184d7d05def8e8e7 14 597 2155 2149 2025-04-21T13:42:22Z Atmois 13 Atmois moved page [[Category:X Window Manager]] to [[Category:X Window Managers]] without leaving a redirect: Typo fix wikitext text/x-wiki This is a category page. It lists all of the pages in category "Window Management Systems/X Window Manager" as well as all subcategories of category "Window Management Systems/X Window Manager" if any exist. [[Category:Window Management Systems]] 5291aad6bb689a1cc47d4e70c40a669e388e5acf 0 306 2156 2139 2025-04-21T13:42:56Z Atmois 13 Atmois moved page [[Window Manager]] to [[X Window Manager]]: More appropiate title wikitext text/x-wiki {{Work_In_Progress}} A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent [[GUI|Graphical User Interface (GUI)]]. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as [[dwm]].  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm * [[Wayfire]] ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[i3]] * [[Sway]] * [[SwayFx]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[dwl]] * [[qtile]] * [[Hyprland]] * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] ==== Scrollable Window Managers ==== Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[niri]] * [[PaperWM]] * [[karousel]] * [[papersway]] * [[hyprscroller]] * [[hyprslidr]] * [[PaperWM.spoon]] [[Category:Terminology]] [[Category:Window Management Systems]] 6f44cc47a809bfcf3f15dc4eab874bf6a9aedd87 0 601 2157 2025-04-21T13:42:56Z Atmois 13 Atmois moved page [[Window Manager]] to [[X Window Manager]]: More appropiate title wikitext text/x-wiki #REDIRECT [[X Window Manager]] cacf475517e62f2a60dc72522001ea1821a13e10 2158 2157 2025-04-21T13:44:03Z Atmois 13 Change redirect wikitext text/x-wiki #REDIRECT [[Window Management System]] daa1f2c89177e4a5b11bdee2be6246557141d249 0 602 2159 2025-04-21T13:46:32Z Atmois 13 Create base of disambiguation page wikitext text/x-wiki {{Work In Progress}} == Disambiguation Page == This page will serve as a disambiguation page between [[Wayland Compositor|Wayland Compositor's]] ([[:Category:Wayland Compositors|Category]]) and [[X Window Manager|X Window Manager's]] ([[:Category:X Window Managers|Category]]). 4c46908c55bc5bfd4f6e6ad43f9a2227bc8cd7e7 2160 2159 2025-04-21T13:47:52Z Atmois 13 Add category wikitext text/x-wiki {{Work In Progress}} == Disambiguation Page == This page will serve as a disambiguation page between [[Wayland Compositor|Wayland Compositor's]] ([[:Category:Wayland Compositors|Category]]) and [[X Window Manager|X Window Manager's]] ([[:Category:X Window Managers|Category]]). [[Category:Window Management Systems]] fbd8759d29383ba77b6cf48562d0eb2aa5490c48 4 556 2161 2120 2025-04-21T16:47:42Z Atmois 13 Add subheader wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[Atl.wiki:Contact|contact page]]! == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin 820baa549129d4f77dbcc8b496dd605716d490e8 2214 2161 2025-04-30T16:19:14Z Atmois 13 Use stats module wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[Atl.wiki:Contact|contact page]]! == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin 63bdd6c475e8d85e9a38d03eb4f1d0080932fe67 8 400 2162 2128 2025-04-21T16:50:37Z Atmois 13 Fix link wikitext text/x-wiki This is the official wiki by the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server! You can see the raw content for the page you are on [{{fullurl:{{FULLPAGENAME}}|action=raw}} here]! 5f40dfd76a83ec9e703a71644337e72227214c90 0 1 2163 2118 2025-04-21T16:52:37Z Atmois 13 Update links wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! ====== Where to Start ====== The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide, if you are interested in writing guides you may also want to check out [[Guides:Contributing]]. These pages will give you everything you need to start editing, if you are still unsure [[Atl.wiki:Contact|contact us]]! * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ 35a5475ce0187bc6121cc49c8a8b0c3af4a7e171 2174 2163 2025-04-25T14:40:02Z Atmois 13 Update info wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! Please avoid putting instructions/commands on an article unless it is for informational purposes, if it is not please see [[Guides:Contributing]]. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ da81ea09bd56e4ac8e9a18959739168ca2463d48 2176 2174 2025-04-25T15:20:04Z Atmois 13 Update getting started on guides info wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Manager |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ f62f1039b71cd67427ce0c3362211482c723a0e1 2177 2176 2025-04-27T17:18:31Z Atmois 13 Update buttons wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |page3 = Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ ef131277a932474b947929f9d1d261905604fd7f 2180 2177 2025-04-27T17:34:57Z Atmois 13 Update guides link wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ 5f9026b1750dcef1241c286e79d4d34e9bd468e8 2184 2180 2025-04-28T12:47:13Z Atmois 13 Add key values wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! atl.wiki has [{{fullurl:Special:AllPages|hideredirects=1}} {{NUMBEROFARTICLES}} pages] consisting of [{{fullurl:Special:RecentChanges}} {{NUMBEROFEDITS}} edits] from [{{fullurl:Special:UserList}} {{NUMBEROFUSERS}} users]! Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Our Key Values ====== We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ 049f67a7a6a8303ece7d3a4d395d7689502106e4 2213 2184 2025-04-30T16:18:57Z Atmois 13 Use module for stats wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Our Key Values ====== We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ 2480f5f3b35eebcc6ca61d5f9aaa21de0bf74e8c 4 593 2164 2117 2025-04-21T17:24:50Z Atmois 13 Add more sections wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. === Using Images === There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. 835d61a585cbf14ad9c9889e0920930e24b0f5e8 2165 2164 2025-04-21T20:00:05Z Atmois 13 Add more info on editing existing pages wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. 9bc9d27c1f44afb49b7ddad5c8c6cd1ddf06ed10 2173 2165 2025-04-23T18:49:46Z Atmois 13 Add image wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. c0d37433d84ace46b51e545bc348ca7d8bf19b56 2181 2173 2025-04-27T17:51:24Z Atmois 13 Add new link wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. e8db833ddc88d6596184c7000d0c2d265e9f2d2a 2183 2181 2025-04-28T12:46:23Z Atmois 13 Add standards overview wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Standards === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. 5dc6917a02fc8d5661caefc5bfa324eaa9456235 2185 2183 2025-04-28T13:13:01Z Atmois 13 Update contributing wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. c628e714e067abc7ff8920888de09c98bb1a1d83 2188 2185 2025-04-28T21:21:03Z Atmois 13 Add how you can help section wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[Guidelines#Standards|standards]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[Atl.wiki:Contact|Contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. 839ddaf2941a66361ce88422336e010e47de77a8 6 603 2166 2025-04-22T16:15:28Z Zak 137 wikitext text/x-wiki Arch Linux ISO and person using the IWCTL to connect to a wifi named "My Wifi SSID" 202c6ac86096fe1b021625ec976c0fd7c2deb936 0 177 2167 2032 2025-04-23T13:59:26Z Atmois 13 Atmois moved page [[FOSS / FLOSS]] to [[FLOSS]] over a redirect without leaving a redirect wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the french word, libre)<ref>https://en.wiktionary.org/wiki/libre</ref> and Open Source Software (FLOSS), is software that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> [[Category:Terminology]] 49199ff0ce85ccf113be2c08dc513b1dd0d9b61e 0 331 2168 1187 2025-04-23T13:59:57Z Atmois 13 Fix redirect wikitext text/x-wiki #REDIRECT [[FLOSS]] 562b80127361500ea0f6e2dae53427f39a54a72b 0 8 2169 2044 2025-04-23T14:00:43Z Atmois 13 Fix link wikitext text/x-wiki {{Work In Progress}} == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] e81a459efd9141c9716896958b18326114248c07 0 414 2170 2024 2025-04-23T14:01:08Z Atmois 13 Fix link wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970's, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at [[Bell Labs]], and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and preprocessors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include [[GNU GCC]], [[Clang]], TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the [[Clang|Clang compiler toolchain]], however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as [[GNU Autotools]], [[CMake]], [[Meson Build|Meson]], [[Zig|Zig's build toolchain]] among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, metaprogramming and structural components of a C codebase; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS / FLOSS|open source]] codebases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995-2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref>, many attribute issues regarding C to fragmentation and portability issues<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref>, lack of type safety and primitive resource access checks<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref>, poor administration on part of the C Language Working Group<ref>https://cor3ntin.github.io/posts/c/</ref>, and overall worsening over time<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref>. a6aacf96e0f4647ec76676533991455c06170b46 0 250 2171 2007 2025-04-23T14:01:23Z Atmois 13 Fix link wikitext text/x-wiki {{Cleanup|Instructions need to be split onto their own page under the Guides namespace}}[[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == Ana/Miniconda Setup == ... (tomorrow's problem) == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU -''' considering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> [[Category:Guides]] 6ce95be383177d1ab77b9f8e03ac3b978111da88 6 604 2172 2025-04-23T18:15:01Z Atmois 13 wikitext text/x-wiki Image demonstrating how to upload file using sidebar 013525404a56a09973dc19858c133398c572b068 3000 605 2178 2025-04-27T17:33:34Z Atmois 13 Create index of guides wikitext text/x-wiki {{Special:AllPages/Guides:}} f871d3923c23b3fb871d2ae2d2d0c87908d41fa3 2179 2178 2025-04-27T17:33:48Z Atmois 13 Protected "[[Guides:Guides]]": High traffic page: Index page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki {{Special:AllPages/Guides:}} f871d3923c23b3fb871d2ae2d2d0c87908d41fa3 4 340 2182 2111 2025-04-28T12:35:48Z Atmois 13 Add accessibility header wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Guidelines#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. ====== <u>Accessibility</u> ====== We aim to make the wiki accessible to users of all ability levels, be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] 35c77c6ae07bfb84e26211ad1167db9b6c0ae7ad 8 606 2186 2025-04-28T20:59:52Z Atmois 13 Update block reasons wikitext text/x-wiki *Common block reasons ** Inserting false information ** Persistent vandalism ** Spamming links to external sites ** Intimidating behaviour or harassment ** Abusing alternate accounts ** Unacceptable username ** Anonymisation 79db2e37b3b6d07537bd8347715c459f3ba80a94 8 607 2187 2025-04-28T21:15:39Z Atmois 13 Update reasons wikitext text/x-wiki *Common suppress reasons ** Anonymisation ** Removing PII c448858ca65616ee20f68e19118af8ff1d50092b 0 263 2200 1820 2025-04-30T07:41:27Z Sudarshanrobot 139 Updated latest release info wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.99.0, 2024-10-24 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|thumb|The Hyfetch Pride Month easter egg.]] Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your operating system, software and hardware with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch</ref> === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. <references /> [[Category:Software]] c02950915871367c41c9c2db62d6a353873fb9d4 3000 608 2201 2025-04-30T10:52:20Z Madonuko 140 New Input method page! wikitext text/x-wiki Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims</ref> Users can use the IMF to switch between different IMEs.<ref>https://wiki.archlinux.org/title/Input_method</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>https://en.wikipedia.org/wiki/Intelligent_Input_Bus</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>https://en.wikipedia.org/wiki/Fcitx</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitxz * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == Unless otherwise specified, on most distributions, the package name will be <code>''<imf>''-''<ime>''</code> (e.g. <code>fcitx5-rime</code>) Note that due to a packaging issue, on Fedora, when you install <code>fcitx5-table-extra</code>, you also need to manually install <code>fcitx5-chinese-addons</code>. This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. === Legend === * '''F5!''': Built into Fcitx5 * '''F_!''': Built into Fcitx * ''F'': Available for Fcitx5/Fcitx under <code>fcitx5-<ime></code> * ''I'': Available for IBus under <code>ibus-<ime></code> * ''F??'': Available for Fcitx, but not Fcitx5. * ''F?'': Available for Fcitx5, but not Fcitx. === Chinese === * [[Rime]]: ''F I'' '''Nimf!''' :* [https://github.com/rime/home/wiki/GettingStarted Official (Traditional) Chinese guide] :* [https://wiki.archlinux.org/title/Rime#Configuration Arch Wiki] * Pinyin: <code>fcitx5-chinese-addons</code> ''I Scim'' '''Nimf!''' * [https://github.com/libpinyin/libpinyin libpinyin]: ''F?? I'' * [https://github.com/sunpinyin/sunpinyin SunPinyin]: ''F?? I'' * Chewing (i.e. Zhuyin): ''F I Scim'' '''Nimf!''' * Haifeng Wubi: <code>ibus-table-chinese-wubi-jidian</code> '''F!''' <code>scim-tables</code> '''uim!''' * Jidian Wubi: <code>ibus-table-chinese-wubi-jidian</code> '''F!''' <code>scim-tables</code> '''uim!''' * Cangjie: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-cangjie</code> <code>scim-tables</code> * Sucheng: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-quick</code> <code>scim-tables</code> * SmartCangjie: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-scj</code> <code>scim-tables</code> * Others: Try <code>fcitx5-table-extra</code> and <code>ibus-table-chinese</code> === Japanese === For configurations, see the [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Japanese#Input_tools Gentoo Wiki]. * Mozc: ''I'' ''Emacs'' :* Arch Linux: you can install the [https://wiki.archlinux.org/title/Mozc#The_UT_Dictionary UT flavors] instead: <code>fcitx5-mozc-ut</code> <code>fcitx-mozc-ut</code>. Otherwise: <code>fcitx5-mozc</code> :* Fedora: <code>fcitx5-mozc</code> * Anthy: ''F I'' '''uim! Scim! Hime! Gcin! Nimf!''' * SKK: ''F I'' '''uim!''' * KKC: ''F I'' === Korean === * Hangul (i.e. libhangul): ''F I Scim'' '''uim!''' === Vietnamese === * Unikey: ''F I'' * ViQR: <code>fcitx5-m17n</code> <code>ibus-table-tv</code> * [https://github.com/BambooEngine/ibus-bamboo Bamboo]: ''F? I'' === Other languages === The situation is a bit more complicated, for now you can see them on the [https://wiki.ultramarine-linux.org/en/usage/l10n/#list-of-imes-and-ims UM Wiki] and the [https://wiki.archlinux.org/title/Input_method#List_of_available_input_method_editors ArchWiki]. e991a784d83578a58c43302152d926aa86a72d24 2215 2201 2025-04-30T16:56:43Z Madonuko 140 /* List of IMs to IMEs */ Temporary commit, add table wikitext text/x-wiki Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. ArchWiki, Ultramarine Wiki. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref /> Users can use the IMF to switch between different IMEs.<ref /> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref /> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref /> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.'''↵While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitxz * The Gentoo Wiki suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {{Work In Progress}} {| class="wikitable" !IMF IME ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code>* |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Japanese |- |[[Mozc]] |{{AUR|fcitx5-mozc-ut}} |{{AUR|fcitx-mozc-ut}} |{{AUR|ibus-mozc}} |<nowiki>-</nowiki> |{{AUR|emacs-mozc}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |{{Pkg|fcitx5-anthy}} |{{Pkg|fcitx-anthy}} |{{Pkg|ibus-anthy}} |''built-in'' |<nowiki>-</nowiki> |{{AUR|scim-anthy}} |''built-in'' |''built-in'' |''built-in'' |- |SKK |{{Pkg|fcitx5-skk}} |{{Pkg|fcitx-skk}} |{{Pkg|ibus-skk}} |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |{{Pkg|fcitx5-kkc}} |{{Pkg|fcitx-kkc}} |{{Pkg|ibus-kkc}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |{{Pkg|fcitx5-hangul}} |{{Pkg|fcitx-hangul}} |{{Pkg|ibus-hangul}} |''built-in'' |<nowiki>-</nowiki> |{{AUR|scim-hangul}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |{{Pkg|fcitx5-unikey}} |{{Pkg|fcitx-unikey}} |{{Pkg|ibus-unikey}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Bamboo |{{Pkg|fcitx5-bamboo}} |<nowiki>-</nowiki> |{{AUR|ibus-bamboo}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |{{AUR|ibus-avro-git}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |{{AUR|ibus-helakuru}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |{{Pkg|fcitx5-m17n}} |{{Pkg|fcitx-m17n}} |{{AUR|ibus-m17n}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |{{AUR|scim-m17n}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |{{AUR|fcitx5-openbangla-git}} |<nowiki>-</nowiki> |{{AUR|openbangla-keyboard}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |{{Pkg|fcitx5-sayura}} |{{Pkg|fcitx-sayura}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<nowiki>-</nowiki> |<nowiki>-</nowiki> |{{AUR|govarnam-ibus-git}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |} Unless otherwise specified, on most distributions, the package name will be <code>''<imf>''-''<ime>''</code> (e.g. <code>fcitx5-rime</code>) Note that due to a packaging issue, on Fedora, when you install <code>fcitx5-table-extra</code>, you also need to manually install <code>fcitx5-chinese-addons</code>. This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. === Legend === * '''F5!''': Built into Fcitx5 * '''F_!''': Built into Fcitx * ''F'': Available for Fcitx5/Fcitx under <code>fcitx5-<ime></code> * ''I'': Available for IBus under <code>ibus-<ime></code> * ''F??'': Available for Fcitx, but not Fcitx5. * ''F?'': Available for Fcitx5, but not Fcitx. === Chinese === * [[Rime]]: ''F I'' '''Nimf!''' :* Official (Traditional) Chinese guide :* Arch Wiki * Pinyin: <code>fcitx5-chinese-addons</code> ''I Scim'' '''Nimf!''' * libpinyin: ''F?? I'' * SunPinyin: ''F?? I'' * Chewing (i.e. Zhuyin): ''F I Scim'' '''Nimf!''' * Haifeng Wubi: <code>ibus-table-chinese-wubi-jidian</code> '''F!''' <code>scim-tables</code> '''uim!''' * Jidian Wubi: <code>ibus-table-chinese-wubi-jidian</code> '''F!''' <code>scim-tables</code> '''uim!''' * Cangjie: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-cangjie</code> <code>scim-tables</code> * Sucheng: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-quick</code> <code>scim-tables</code> * SmartCangjie: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-scj</code> <code>scim-tables</code> * Others: Try <code>fcitx5-table-extra</code> and <code>ibus-table-chinese</code> === Japanese === For configurations, see the Gentoo Wiki. * Mozc: ''I'' ''Emacs'' :* Arch Linux: you can install the UT flavors instead: <code>fcitx5-mozc-ut</code> <code>fcitx-mozc-ut</code>. Otherwise: <code>fcitx5-mozc</code> :* Fedora: <code>fcitx5-mozc</code> * Anthy: ''F I'' '''uim! Scim! Hime! Gcin! Nimf!''' * SKK: ''F I'' '''uim!''' * KKC: ''F I'' === Korean === * Hangul (i.e. libhangul): ''F I Scim'' '''uim!''' === Vietnamese === * Unikey: ''F I'' * ViQR: <code>fcitx5-m17n</code> <code>ibus-table-tv</code> * Bamboo: ''F? I'' === Other languages === The situation is a bit more complicated, for now you can see them on the UM Wiki and the ArchWiki. <references /> c4e57921ac0f3ba1b0f7861cc4116020cb1cc56a 2216 2215 2025-04-30T17:01:58Z Madonuko 140 Get my table back wikitext text/x-wiki Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims</ref> Users can use the IMF to switch between different IMEs.<ref>https://wiki.archlinux.org/title/Input_method</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>https://en.wikipedia.org/wiki/Intelligent_Input_Bus</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>https://en.wikipedia.org/wiki/Fcitx</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitxz * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {{Work In Progress}} {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code>* |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Japanese |- |[[Mozc]] |{{AUR|fcitx5-mozc-ut}} |{{AUR|fcitx-mozc-ut}} |{{AUR|ibus-mozc}} |<nowiki>-</nowiki> |{{AUR|emacs-mozc}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |{{Pkg|fcitx5-anthy}} |{{Pkg|fcitx-anthy}} |{{Pkg|ibus-anthy}} |''built-in'' |<nowiki>-</nowiki> |{{AUR|scim-anthy}} |''built-in'' |''built-in'' |''built-in'' |- |SKK |{{Pkg|fcitx5-skk}} |{{Pkg|fcitx-skk}} |{{Pkg|ibus-skk}} |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |{{Pkg|fcitx5-kkc}} |{{Pkg|fcitx-kkc}} |{{Pkg|ibus-kkc}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |{{Pkg|fcitx5-hangul}} |{{Pkg|fcitx-hangul}} |{{Pkg|ibus-hangul}} |''built-in'' |<nowiki>-</nowiki> |{{AUR|scim-hangul}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |{{Pkg|fcitx5-unikey}} |{{Pkg|fcitx-unikey}} |{{Pkg|ibus-unikey}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Bamboo |{{Pkg|fcitx5-bamboo}} |<nowiki>-</nowiki> |{{AUR|ibus-bamboo}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |{{AUR|ibus-avro-git}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |{{AUR|ibus-helakuru}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |{{Pkg|fcitx5-m17n}} |{{Pkg|fcitx-m17n}} |{{AUR|ibus-m17n}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |{{AUR|scim-m17n}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |{{AUR|fcitx5-openbangla-git}} |<nowiki>-</nowiki> |{{AUR|openbangla-keyboard}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |{{Pkg|fcitx5-sayura}} |{{Pkg|fcitx-sayura}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<nowiki>-</nowiki> |<nowiki>-</nowiki> |{{AUR|govarnam-ibus-git}} |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |} Unless otherwise specified, on most distributions, the package name will be <code>''<imf>''-''<ime>''</code> (e.g. <code>fcitx5-rime</code>) Note that due to a packaging issue, on Fedora, when you install <code>fcitx5-table-extra</code>, you also need to manually install <code>fcitx5-chinese-addons</code>. This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. === Legend === * '''F5!''': Built into Fcitx5 * '''F_!''': Built into Fcitx * ''F'': Available for Fcitx5/Fcitx under <code>fcitx5-<ime></code> * ''I'': Available for IBus under <code>ibus-<ime></code> * ''F??'': Available for Fcitx, but not Fcitx5. * ''F?'': Available for Fcitx5, but not Fcitx. === Chinese === * [[Rime]]: ''F I'' '''Nimf!''' :* [https://github.com/rime/home/wiki/GettingStarted Official (Traditional) Chinese guide] :* [https://wiki.archlinux.org/title/Rime#Configuration Arch Wiki] * Pinyin: <code>fcitx5-chinese-addons</code> ''I Scim'' '''Nimf!''' * [https://github.com/libpinyin/libpinyin libpinyin]: ''F?? I'' * [https://github.com/sunpinyin/sunpinyin SunPinyin]: ''F?? I'' * Chewing (i.e. Zhuyin): ''F I Scim'' '''Nimf!''' * Haifeng Wubi: <code>ibus-table-chinese-wubi-jidian</code> '''F!''' <code>scim-tables</code> '''uim!''' * Jidian Wubi: <code>ibus-table-chinese-wubi-jidian</code> '''F!''' <code>scim-tables</code> '''uim!''' * Cangjie: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-cangjie</code> <code>scim-tables</code> * Sucheng: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-quick</code> <code>scim-tables</code> * SmartCangjie: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-scj</code> <code>scim-tables</code> * Others: Try <code>fcitx5-table-extra</code> and <code>ibus-table-chinese</code> === Japanese === For configurations, see the [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Japanese#Input_tools Gentoo Wiki]. * Mozc: ''I'' ''Emacs'' :* Arch Linux: you can install the [https://wiki.archlinux.org/title/Mozc#The_UT_Dictionary UT flavors] instead: <code>fcitx5-mozc-ut</code> <code>fcitx-mozc-ut</code>. Otherwise: <code>fcitx5-mozc</code> :* Fedora: <code>fcitx5-mozc</code> * Anthy: ''F I'' '''uim! Scim! Hime! Gcin! Nimf!''' * SKK: ''F I'' '''uim!''' * KKC: ''F I'' === Korean === * Hangul (i.e. libhangul): ''F I Scim'' '''uim!''' === Vietnamese === * Unikey: ''F I'' * ViQR: <code>fcitx5-m17n</code> <code>ibus-table-tv</code> * [https://github.com/BambooEngine/ibus-bamboo Bamboo]: ''F? I'' === Other languages === The situation is a bit more complicated, for now you can see them on the [https://wiki.ultramarine-linux.org/en/usage/l10n/#list-of-imes-and-ims UM Wiki] and the [https://wiki.archlinux.org/title/Input_method#List_of_available_input_method_editors ArchWiki]. d8c2a2437beaf5d0e16f3e7f27e43644c4b9a196 0 176 2202 1996 2025-04-30T12:56:20Z Jpetso 141 /* Features */ Discover is an app store more than a graphical package manager. Also makes the text more accessible. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it has been criticized for being either lackluster, difficult to use, and failing to work with some GPUs, it is still an effective option for many beginners [CITATION NEEDED]. Kdenlive, as a sample, was used explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] b5ba97537dc9cefc78caee4665410764d44351d9 2203 2202 2025-04-30T13:08:42Z Jpetso 141 /* Features */ Replace Kdenlive's [CITATION NEEDED] paragraph with a more general statement, hopefully also more useful. Also, phrasing tweaks wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE desktop. After the Plasma 5 update, many widgets and other features were soon deprecated or removed altogether, yet there is still a sizable enough amount of extra effects to use. * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 78de9910c92329539885e99384cefc2cee43f27f 2204 2203 2025-04-30T13:23:42Z Jpetso 141 /* Desktop Effects */ There aren't many KDE 4 users around anymore that would be disappointed by Plasma 5 or 6 not shipping a few plugins by default anymore. Instead, mention that the remaining "sizeable" number is part of a standard Plasma install wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for UNIX-Based Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] 70d9544de7ee8f0a412c634080102faaccb79e68 828 609 2205 2025-04-30T15:34:43Z Atmois 13 Create statsline module Scribunto text/plain local p = {} function p.stats() local siteStats = mw.site.stats local totalEdits = siteStats.edits local totalUsers = siteStats.users local function countPages(ns) return siteStats.pagesInNamespace(ns) or 0 end local pageCount = countPages(0) + countPages(3000) return string.format("atl.wiki has %d pages consisting of %d edits from %d users!", pageCount, totalEdits, totalUsers) end return p e693c884dbee68c07b9472a04bb2f380924e1f0e 2206 2205 2025-04-30T15:44:19Z Atmois 13 Improve Scribunto text/plain local p = {} function p.stats() local siteStats = mw.site.stats local totalEdits = siteStats.edits local totalUsers = siteStats.users local function countPages(ns) return siteStats.pagesInNamespace(ns) or 0 end local pageCount = countPages(0) + countPages(3000) return string.format( "atl.wiki has [https://atl.wiki/Atl.wiki:AllPages %d pages] consisting of [https://atl.wiki/Special:RecentChanges %d edits] from [https://atl.wiki/Special:ListUsers %d users]!", pageCount, totalEdits, totalUsers ) end return p 2ebef772b8e1a93dd01bd1f3d740554d0f456334 4 327 2207 2091 2025-04-30T15:44:34Z Atmois 13 test module wikitext text/x-wiki {{#invoke:StatsLine|stats}} Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen electron was here {{Special:Contribute}} more testing???? test n 1203 idk potato testing testing 1 2 3 4<ref>hi</ref> {{MascotInfobox | title = Test | image = [[File:Larry the cow.png|Larry the Cow]] | caption = Test }} e1f2148cbcae434fb001e434ec716e3af8d59fb6 10 610 2208 2025-04-30T16:00:12Z Atmois 13 Create for DPL wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 828 612 2212 2025-04-30T16:18:25Z Atmois 13 Add doc wikitext text/x-wiki ==== Usage: ==== <code><nowiki>{{#invoke:StatsLine|stats}}</nowiki></code> ==== Output: ==== {{#invoke:StatsLine|stats}} c6593216041dc3d25110f6009403864a924b5fb6 8 196 2217 461 2025-04-30T17:26:13Z Atmois 13 Rebind shortcut javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ $(document).ready(function(){ $('.mw-references-wrap').before('<h2>References</h2>'); }); mw.loader.using(['mediawiki.util'], function() { $(document).keydown(function(e) { // Check if Ctrl + Shift + 6 is pressed if (e.ctrlKey && e.shiftKey && e.key === '6') { // Prevent the default action (if any) e.preventDefault(); // Trigger the same action as Ctrl + Shift + B var event = new KeyboardEvent('keydown', { bubbles: true, cancelable: true, key: 'b', shiftKey: true, ctrlKey: true, metaKey: false }); document.dispatchEvent(event); } }); }); 58d0101c1d3e0a2d969c0983a900019df12f47db 2218 2217 2025-04-30T17:26:43Z Atmois 13 revert, it doesnt work javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ $(document).ready(function(){ $('.mw-references-wrap').before('<h2>References</h2>'); }); 4526a214ca149b86a31f01350a234e4ad25c21d4 3000 608 2219 2216 2025-04-30T17:28:42Z Madonuko 140 add notes wikitext text/x-wiki Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims</ref> Users can use the IMF to switch between different IMEs.<ref>https://wiki.archlinux.org/title/Input_method</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>https://en.wikipedia.org/wiki/Intelligent_Input_Bus</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>https://en.wikipedia.org/wiki/Fcitx</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitxz * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {{Work In Progress}} {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code>? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code> |<code>fcitx-mozc</code> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |} === Notes === <references group=Note/> Unless otherwise specified, on most distributions, the package name will be <code>''<imf>''-''<ime>''</code> (e.g. <code>fcitx5-rime</code>) Note that due to a packaging issue, on Fedora, when you install <code>fcitx5-table-extra</code>, you also need to manually install <code>fcitx5-chinese-addons</code>. This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. === Legend === * '''F5!''': Built into Fcitx5 * '''F_!''': Built into Fcitx * ''F'': Available for Fcitx5/Fcitx under <code>fcitx5-<ime></code> * ''I'': Available for IBus under <code>ibus-<ime></code> * ''F??'': Available for Fcitx, but not Fcitx5. * ''F?'': Available for Fcitx5, but not Fcitx. === Chinese === * [[Rime]]: ''F I'' '''Nimf!''' :* [https://github.com/rime/home/wiki/GettingStarted Official (Traditional) Chinese guide] :* [https://wiki.archlinux.org/title/Rime#Configuration Arch Wiki] * Pinyin: <code>fcitx5-chinese-addons</code> ''I Scim'' '''Nimf!''' * [https://github.com/libpinyin/libpinyin libpinyin]: ''F?? I'' * [https://github.com/sunpinyin/sunpinyin SunPinyin]: ''F?? I'' * Chewing (i.e. Zhuyin): ''F I Scim'' '''Nimf!''' * Haifeng Wubi: <code>ibus-table-chinese-wubi-jidian</code> '''F!''' <code>scim-tables</code> '''uim!''' * Jidian Wubi: <code>ibus-table-chinese-wubi-jidian</code> '''F!''' <code>scim-tables</code> '''uim!''' * Cangjie: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-cangjie</code> <code>scim-tables</code> * Sucheng: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-quick</code> <code>scim-tables</code> * SmartCangjie: <code>fcitx5-table-extra</code> <code>ibus-table-chinese-scj</code> <code>scim-tables</code> * Others: Try <code>fcitx5-table-extra</code> and <code>ibus-table-chinese</code> === Japanese === For configurations, see the [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Japanese#Input_tools Gentoo Wiki]. * Mozc: ''I'' ''Emacs'' :* Arch Linux: you can install the [https://wiki.archlinux.org/title/Mozc#The_UT_Dictionary UT flavors] instead: <code>fcitx5-mozc-ut</code> <code>fcitx-mozc-ut</code>. Otherwise: <code>fcitx5-mozc</code> :* Fedora: <code>fcitx5-mozc</code> * Anthy: ''F I'' '''uim! Scim! Hime! Gcin! Nimf!''' * SKK: ''F I'' '''uim!''' * KKC: ''F I'' === Korean === * Hangul (i.e. libhangul): ''F I Scim'' '''uim!''' === Vietnamese === * Unikey: ''F I'' * ViQR: <code>fcitx5-m17n</code> <code>ibus-table-tv</code> * [https://github.com/BambooEngine/ibus-bamboo Bamboo]: ''F? I'' === Other languages === The situation is a bit more complicated, for now you can see them on the [https://wiki.ultramarine-linux.org/en/usage/l10n/#list-of-imes-and-ims UM Wiki] and the [https://wiki.archlinux.org/title/Input_method#List_of_available_input_method_editors ArchWiki]. aaac335aba8497999ed277e8cd7e3921e9de98d6 2228 2219 2025-05-01T09:25:38Z Madonuko 140 /* Notes */ Fix the tables, add opinionated stuff wikitext text/x-wiki Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims</ref> Users can use the IMF to switch between different IMEs.<ref>https://wiki.archlinux.org/title/Input_method</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>https://en.wikipedia.org/wiki/Intelligent_Input_Bus</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>https://en.wikipedia.org/wiki/Fcitx</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitxz * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code><ref name=":0" group="Note">Additionally requires <code>fcitx5-chinese-addon</code> on Fedora due to packaging issues.</ref> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code><ref name=":0" group="Note" />? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code><ref group="Note"><code>fcitx5-mozc-ut</code>^AUR is instead recommended on Arch Linux.</ref> |<code>fcitx-mozc</code><ref group="Note"><code>fcitx-mozc-ut</code>^AUR is instead recommended on Arch.</ref> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |ViQR |<code>fcitx5-m17n</code><ref name=":1" group="Note">This is <code>fcitx5-table-viqr</code>, <code>fcitx-table-viqr</code>, <code>ibus-table-viqr</code> on Debian.</ref> |<code>fcitx-m17n</code><ref name=":1" group="Note" /> |<code>ibus-table-tv</code><ref name=":1" group="Note" /> |<code>uim-viqr</code> | - | - | - | - | - |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<code>uim-m17n</code><ref name=":2" group="Note">On some distros, this is <code>uim-m17nlib</code>.</ref> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code><ref group="Note">Requires the [[Terra]] repository on Fedora.</ref> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code><ref group="Note"><code>ibus-openbangla</code> on Fedora with the [[Terra]] repository.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<code>fcitx5-varnam</code> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Others |- |Thai |<code>fcitx5-libthai</code> | - |<code>ibus-table-tv</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> | - |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Math Symbols |[[Compose Key]]? |[[Compose Key]]? |<code>ibus-table-mathwriter</code> | - | - | - | - | - | - |- |Completion |''built-in'' | - |<code>ibus-typing-booster</code> | - | - | - | - | - | - |- |''"Everything Else"'' |<code>fcitx5-m17n</code>? |<code>fcitx-m17n</code>? |<code>ibus-m17n</code>? |<code>uim-m17n</code><ref name=":2" group="Note" />? | - |<code>scim-m17n</code>? | - | - | - |} === Notes === <references group=Note/> This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. == How to choose your IME == This section represents the general case and the authors' opinions. It is not necessary to follow them. {| class="wikitable" |+Chinese !Situation !IME !Rime IME !Notes |- |Already using [[Rime]] | rowspan="3" |Rime | - | rowspan="3" |Rime is very powerful, but it comes with the cost of writing your own configuration files and [https://github.com/rime/home/wiki reading Chinese documentations], and thus is not recommended to beginners. |- |Prefer a highly customizable experience | - |- |Good at writing configuration files | - |- |Know Pinyin |Pinyin |''built-in'' | |- |Know Zhuyin |Chewing |℞ bopomofo |<code>libzhuyin</code> is not recommended (very unpopular), avoid <code>fcitx5-zhuyin</code> & <code>ibus-libzhuyin</code>. |- |Know Cangjie 3 / Quick 3 | rowspan="2" |Cangjie/Quick | rowspan="2" |℞ cangjie |Rime with [https://github.com/kennethso168/rime-cangjie3-extension rime-cangjie3-extension] |- |Know Cangjie 5 / Quick 5 | |- |Know SmartCangjie 6 |SCJ |℞ scj | |- |Know Jyutping |Rime |℞ cantonese |Jyutping from table-extras is barely usable |- |Know Wubi |Haifeng Wubi | |https://www.zhukun.net/archives/4856 |} {| class="wikitable" |+Japanese !Situation !IME !Notes |- |You hate Qt |Anthy |Anthy is unmaintained but it's written in GTK, so if you want your IME to fit into your GTK theme, use Anthy. |- |Otherwise |Mozc |Mozc is maintained by Google and has better suggestions, but you should also consider using the UT dictionaries. |} e7e9bfda05a0454f18776183f45b70d534a6f301 2229 2228 2025-05-01T09:26:57Z Madonuko 140 /* Fcitx5 */ Fix typo in envs wikitext text/x-wiki Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims</ref> Users can use the IMF to switch between different IMEs.<ref>https://wiki.archlinux.org/title/Input_method</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>https://en.wikipedia.org/wiki/Intelligent_Input_Bus</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>https://en.wikipedia.org/wiki/Fcitx</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code><ref name=":0" group="Note">Additionally requires <code>fcitx5-chinese-addon</code> on Fedora due to packaging issues.</ref> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code><ref name=":0" group="Note" />? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code><ref group="Note"><code>fcitx5-mozc-ut</code>^AUR is instead recommended on Arch Linux.</ref> |<code>fcitx-mozc</code><ref group="Note"><code>fcitx-mozc-ut</code>^AUR is instead recommended on Arch.</ref> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |ViQR |<code>fcitx5-m17n</code><ref name=":1" group="Note">This is <code>fcitx5-table-viqr</code>, <code>fcitx-table-viqr</code>, <code>ibus-table-viqr</code> on Debian.</ref> |<code>fcitx-m17n</code><ref name=":1" group="Note" /> |<code>ibus-table-tv</code><ref name=":1" group="Note" /> |<code>uim-viqr</code> | - | - | - | - | - |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<code>uim-m17n</code><ref name=":2" group="Note">On some distros, this is <code>uim-m17nlib</code>.</ref> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code><ref group="Note">Requires the [[Terra]] repository on Fedora.</ref> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code><ref group="Note"><code>ibus-openbangla</code> on Fedora with the [[Terra]] repository.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<code>fcitx5-varnam</code> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Others |- |Thai |<code>fcitx5-libthai</code> | - |<code>ibus-table-tv</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> | - |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Math Symbols |[[Compose Key]]? |[[Compose Key]]? |<code>ibus-table-mathwriter</code> | - | - | - | - | - | - |- |Completion |''built-in'' | - |<code>ibus-typing-booster</code> | - | - | - | - | - | - |- |''"Everything Else"'' |<code>fcitx5-m17n</code>? |<code>fcitx-m17n</code>? |<code>ibus-m17n</code>? |<code>uim-m17n</code><ref name=":2" group="Note" />? | - |<code>scim-m17n</code>? | - | - | - |} === Notes === <references group=Note/> This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. == How to choose your IME == This section represents the general case and the authors' opinions. It is not necessary to follow them. {| class="wikitable" |+Chinese !Situation !IME !Rime IME !Notes |- |Already using [[Rime]] | rowspan="3" |Rime | - | rowspan="3" |Rime is very powerful, but it comes with the cost of writing your own configuration files and [https://github.com/rime/home/wiki reading Chinese documentations], and thus is not recommended to beginners. |- |Prefer a highly customizable experience | - |- |Good at writing configuration files | - |- |Know Pinyin |Pinyin |''built-in'' | |- |Know Zhuyin |Chewing |℞ bopomofo |<code>libzhuyin</code> is not recommended (very unpopular), avoid <code>fcitx5-zhuyin</code> & <code>ibus-libzhuyin</code>. |- |Know Cangjie 3 / Quick 3 | rowspan="2" |Cangjie/Quick | rowspan="2" |℞ cangjie |Rime with [https://github.com/kennethso168/rime-cangjie3-extension rime-cangjie3-extension] |- |Know Cangjie 5 / Quick 5 | |- |Know SmartCangjie 6 |SCJ |℞ scj | |- |Know Jyutping |Rime |℞ cantonese |Jyutping from table-extras is barely usable |- |Know Wubi |Haifeng Wubi | |https://www.zhukun.net/archives/4856 |} {| class="wikitable" |+Japanese !Situation !IME !Notes |- |You hate Qt |Anthy |Anthy is unmaintained but it's written in GTK, so if you want your IME to fit into your GTK theme, use Anthy. |- |Otherwise |Mozc |Mozc is maintained by Google and has better suggestions, but you should also consider using the UT dictionaries. |} bc8a3f3d45c16e43cc5131a8b7e68786a7299998 2265 2229 2025-05-03T06:59:28Z Madonuko 140 fix references to comply with guidelines wikitext text/x-wiki Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">[https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims Localization, Internationalization and Multilingualization], Ultramarine Linux, 2024 (Accessed: 2025-05-03)</ref> Users can use the IMF to switch between different IMEs.<ref>[https://wiki.archlinux.org/title/Input_method Input method], ArchWiki, 2020 (Accessed: 2025-05-03)</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>[[wikipedia:Intelligent_Input_Bus|Intelligent_Input_Bus]], Wikipedia, 2009 (Accessed: 2025-05-03)</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>[[wikipedia:Fcitx|Fcitx]], Wikipedia, 2010 (Accessed: 2025-05-03)</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code><ref name=":0" group="Note">Additionally requires <code>fcitx5-chinese-addon</code> on Fedora due to packaging issues.</ref> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code><ref name=":0" group="Note" />? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code><ref group="Note"><code>fcitx5-mozc-ut</code>^AUR is instead recommended on Arch Linux.</ref> |<code>fcitx-mozc</code><ref group="Note"><code>fcitx-mozc-ut</code>^AUR is instead recommended on Arch.</ref> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |ViQR |<code>fcitx5-m17n</code><ref name=":1" group="Note">This is <code>fcitx5-table-viqr</code>, <code>fcitx-table-viqr</code>, <code>ibus-table-viqr</code> on Debian.</ref> |<code>fcitx-m17n</code><ref name=":1" group="Note" /> |<code>ibus-table-tv</code><ref name=":1" group="Note" /> |<code>uim-viqr</code> | - | - | - | - | - |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<code>uim-m17n</code><ref name=":2" group="Note">On some distros, this is <code>uim-m17nlib</code>.</ref> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code><ref group="Note">Requires the [[Terra]] repository on Fedora.</ref> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code><ref group="Note"><code>ibus-openbangla</code> on Fedora with the [[Terra]] repository.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<code>fcitx5-varnam</code> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Others |- |Thai |<code>fcitx5-libthai</code> | - |<code>ibus-table-tv</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> | - |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Math Symbols |[[Compose Key]]? |[[Compose Key]]? |<code>ibus-table-mathwriter</code> | - | - | - | - | - | - |- |Completion |''built-in'' | - |<code>ibus-typing-booster</code> | - | - | - | - | - | - |- |''"Everything Else"'' |<code>fcitx5-m17n</code>? |<code>fcitx-m17n</code>? |<code>ibus-m17n</code>? |<code>uim-m17n</code><ref name=":2" group="Note" />? | - |<code>scim-m17n</code>? | - | - | - |} === Notes === <references group=Note/> This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. == How to choose your IME == This section represents the general case and the authors' opinions. It is not necessary to follow them. {| class="wikitable" |+Chinese !Situation !IME !Rime IME !Notes |- |Already using [[Rime]] | rowspan="3" |Rime | - | rowspan="3" |Rime is very powerful, but it comes with the cost of writing your own configuration files and [https://github.com/rime/home/wiki reading Chinese documentations], and thus is not recommended to beginners. |- |Prefer a highly customizable experience | - |- |Good at writing configuration files | - |- |Know Pinyin |Pinyin |''built-in'' | |- |Know Zhuyin |Chewing |℞ bopomofo |<code>libzhuyin</code> is not recommended (very unpopular), avoid <code>fcitx5-zhuyin</code> & <code>ibus-libzhuyin</code>. |- |Know Cangjie 3 / Quick 3 | rowspan="2" |Cangjie/Quick | rowspan="2" |℞ cangjie |Rime with [https://github.com/kennethso168/rime-cangjie3-extension rime-cangjie3-extension] |- |Know Cangjie 5 / Quick 5 | |- |Know SmartCangjie 6 |SCJ |℞ scj | |- |Know Jyutping |Rime |℞ cantonese |Jyutping from table-extras is barely usable |- |Know Wubi |Haifeng Wubi | |https://www.zhukun.net/archives/4856 |} {| class="wikitable" |+Japanese !Situation !IME !Notes |- |You hate Qt |Anthy |Anthy is unmaintained but it's written in GTK, so if you want your IME to fit into your GTK theme, use Anthy. |- |Otherwise |Mozc |Mozc is maintained by Google and has better suggestions, but you should also consider using the UT dictionaries. |} fb59544291924ecd7c9e055fe692613d747d5c5c 2274 2265 2025-05-06T17:44:44Z Atmois 13 Add guide warning wikitext text/x-wiki {{GuideWarning}} Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">[https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims Localization, Internationalization and Multilingualization], Ultramarine Linux, 2024 (Accessed: 2025-05-03)</ref> Users can use the IMF to switch between different IMEs.<ref>[https://wiki.archlinux.org/title/Input_method Input method], ArchWiki, 2020 (Accessed: 2025-05-03)</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>[[wikipedia:Intelligent_Input_Bus|Intelligent_Input_Bus]], Wikipedia, 2009 (Accessed: 2025-05-03)</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>[[wikipedia:Fcitx|Fcitx]], Wikipedia, 2010 (Accessed: 2025-05-03)</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code><ref name=":0" group="Note">Additionally requires <code>fcitx5-chinese-addon</code> on Fedora due to packaging issues.</ref> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code><ref name=":0" group="Note" />? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code><ref group="Note"><code>fcitx5-mozc-ut</code>^AUR is instead recommended on Arch Linux.</ref> |<code>fcitx-mozc</code><ref group="Note"><code>fcitx-mozc-ut</code>^AUR is instead recommended on Arch.</ref> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |ViQR |<code>fcitx5-m17n</code><ref name=":1" group="Note">This is <code>fcitx5-table-viqr</code>, <code>fcitx-table-viqr</code>, <code>ibus-table-viqr</code> on Debian.</ref> |<code>fcitx-m17n</code><ref name=":1" group="Note" /> |<code>ibus-table-tv</code><ref name=":1" group="Note" /> |<code>uim-viqr</code> | - | - | - | - | - |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<code>uim-m17n</code><ref name=":2" group="Note">On some distros, this is <code>uim-m17nlib</code>.</ref> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code><ref group="Note">Requires the [[Terra]] repository on Fedora.</ref> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code><ref group="Note"><code>ibus-openbangla</code> on Fedora with the [[Terra]] repository.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<code>fcitx5-varnam</code> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Others |- |Thai |<code>fcitx5-libthai</code> | - |<code>ibus-table-tv</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> | - |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Math Symbols |[[Compose Key]]? |[[Compose Key]]? |<code>ibus-table-mathwriter</code> | - | - | - | - | - | - |- |Completion |''built-in'' | - |<code>ibus-typing-booster</code> | - | - | - | - | - | - |- |''"Everything Else"'' |<code>fcitx5-m17n</code>? |<code>fcitx-m17n</code>? |<code>ibus-m17n</code>? |<code>uim-m17n</code><ref name=":2" group="Note" />? | - |<code>scim-m17n</code>? | - | - | - |} === Notes === <references group=Note/> This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. == How to choose your IME == This section represents the general case and the authors' opinions. It is not necessary to follow them. {| class="wikitable" |+Chinese !Situation !IME !Rime IME !Notes |- |Already using [[Rime]] | rowspan="3" |Rime | - | rowspan="3" |Rime is very powerful, but it comes with the cost of writing your own configuration files and [https://github.com/rime/home/wiki reading Chinese documentations], and thus is not recommended to beginners. |- |Prefer a highly customizable experience | - |- |Good at writing configuration files | - |- |Know Pinyin |Pinyin |''built-in'' | |- |Know Zhuyin |Chewing |℞ bopomofo |<code>libzhuyin</code> is not recommended (very unpopular), avoid <code>fcitx5-zhuyin</code> & <code>ibus-libzhuyin</code>. |- |Know Cangjie 3 / Quick 3 | rowspan="2" |Cangjie/Quick | rowspan="2" |℞ cangjie |Rime with [https://github.com/kennethso168/rime-cangjie3-extension rime-cangjie3-extension] |- |Know Cangjie 5 / Quick 5 | |- |Know SmartCangjie 6 |SCJ |℞ scj | |- |Know Jyutping |Rime |℞ cantonese |Jyutping from table-extras is barely usable |- |Know Wubi |Haifeng Wubi | |https://www.zhukun.net/archives/4856 |} {| class="wikitable" |+Japanese !Situation !IME !Notes |- |You hate Qt |Anthy |Anthy is unmaintained but it's written in GTK, so if you want your IME to fit into your GTK theme, use Anthy. |- |Otherwise |Mozc |Mozc is maintained by Google and has better suggestions, but you should also consider using the UT dictionaries. |} 18d10d813b6edcd65f91413c1bc0f0bbff1f427f 4 593 2220 2188 2025-04-30T18:12:28Z Atmois 13 Add key pages list wikitext text/x-wiki = Preface = Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[Guidelines#Standards|standards]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[Atl.wiki:Contact|Contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === * The [[Window Management System]] definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. * The [[Linux Distributions|Linux Distribution]] article which lists distros is lacking a lot of major distros and each section should have a short blurb and information about key facts about what distros under that group typically are (e.g. release cycle, package manager, etc) * The [[Package Manager]] page, which lists package managers, needs to be rewritten to compare and delve more into each package manager. * The [[Key Terms]] page needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table potentially * The [[Desktop Environments]] page needs to be written, it needs to contain basics around DE's and what they are and a list of DE's with a short blurb to each one and potentially key distros that offer them, a table could be used to list them. * The [[X Window Manager]] page, which lists WM's depending on the type, needs to be cleaned up to remove Wayland Compositors and each WM should have a short blurb to it and potentially key distros that offer them, a table could be used to list them. 98a2aa8f793766b51f3d5867024b625f8c645ba1 2 616 2230 2025-05-01T09:53:15Z Wilbur 142 create basic user page wikitext text/x-wiki Part of the ATL Systems Team; I run [https://iso.atl.dev ISO Archives]. I doubt I'll edit much, but some might happen here-and-there. wilbur@allthingslinux.org f06ba67ab37ac96e21a35d0c183b2c3595961195 6 617 2231 2025-05-01T11:01:39Z Atmois 13 wikitext text/x-wiki Image of enabled flathub repos in GNOME Software ef583c98a2cfde4619b87165bae6ad69a3f37c69 6 618 2232 2025-05-01T11:04:10Z Atmois 13 wikitext text/x-wiki GNOME Software GUI when Flathub Repo File has been enabled dcf3488d4c585a990dcddad3b5206a3ad81bb429 6 619 2233 2025-05-01T11:13:42Z Atmois 13 wikitext text/x-wiki Image of Flathub being enabled as primary flatpak repository f7dc89f463ee2648543092056b3f2abe98ea9a4f 3000 573 2234 1918 2025-05-01T11:14:24Z Atmois 13 Add images and KDE Discover section wikitext text/x-wiki {{Guide Warning}} [[Flathub]] is a third party [[repository]] of applications that are packaged in the [[Flatpak]] format. By default, [[Fedora]] does not include the Flathub repository<ref>[https://developer.fedoraproject.org/deployment/flatpak/flatpak-usage.html Flatpak Usage On Fedora], Felipe Borges, Jarek Prokop, John Atti, Nick Dirschel, Pavel Valena, 2018 (Retrieved 22nd March 2025)</ref>. Some Flathub apps are also in the main Fedora repositories, but in some cases it ships newer versions or applications that aren’t available in the Fedora repositories<ref>[https://fedoramagazine.org/install-flathub-apps-fedora/ Installing Flathub Apps on Fedora], Ryan Lerch, 2018 (Retrieved 22nd March 2025)</ref>. You can set up Flathub graphically via the repository file, GNOME Software or KDE Discover. Alternately, you can set it up through the command line. The recommended method is via the Flathub repository file or the terminal: ====== Installing Flathub via the Flathub Repository File (Recommended) ====== [[File:GNOMESoftwareFlathubFile.png|thumb|GNOME Software GUI when Flathub Repo File has been opened via File Manager]] # Visit [https://flathub.org/setup/Fedora flathub.org/setup/Fedora] and select the text saying <code>Flathub Repository File</code> to download <code>flathub.flatpakrepo</code>. # Open your file manager and double-click the <code>flathub.flatpakrepo</code> file. It will open KDE Discover or GNOME software. # Select the <code>Install</code> button, you may need to log out and log back in to Fedora for Flathub apps to appear. ====== Installing Flathub via GNOME Software ====== [[File:SoftwareReposGNOMESoftware.png|thumb|Image of Flathub being enabled in GNOME Software.]] # Open GNOME software and select the hamburger menu on the top right of the application and select <code>Software Respositories</code>. You can also use the key bind <code>RightCtrl + .</code> to open the menu. # Scroll down and enable the toggle for <code>Flathub</code> and the toggle for <code>Enable New Repositories</code>. # You may need to log out and log back into Fedora or run <code>gnome-software --quit</code> in your terminal for Flathub apps to appear in GNOME software. ====== Installing Flathub via the KDE Discover ====== [[File:DiscoverKDEFlathubRepo.png|thumb|328x328px|How the Flatpak section should look after finishing on KDE Discover]] # Open KDE discover and open the settings menu on the left of your screen. # Select the <code>Flathub - ''dl.flathub.org''</code> option. # Click the up arrow until Flathub is at the top of the list to make it the primary source, then click apply changes at the top of KDE Discover. # You may need to log out and log back into Fedora for Flathub apps to appear in KDE Discover. ====== Installing Flathub via the Command Line ====== # Open your terminal of choice. # Run the command <code>flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki></code>. # You may need to log out and log back into Fedora for Flathub apps to appear in GNOME software or KDE Discover. <references /> 4262c1bbb85181c93a2d2821ec202cb0d17d706c 4 556 2236 2214 2025-05-01T11:51:05Z Atmois 13 Start history/roadmap section wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[Atl.wiki:Contact|contact page]]! == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin == History & Roadmap == ===== 9th May 2024 - 2nd June 2024 ===== The initial plans were made for starting the wiki in the Discord Server, Mediawiki was chosen as the software for being the most extensible and powerful of the choices available. ===== 3rd June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the All Things Linux discord. Electron271, Green and Scott96 were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. ===== 4th June 2024 ===== We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose Citizen as our default theme due to its modern feel compared to the default skins. ===== 9th June 2024 ===== After suffering some DDOS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== 14th October 2024 ===== After a few quiet months of slow growth, Atmois was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at Weird Gloop (The hosters of the Minecraft and Runescape wiki's) we planned the next steps for the wiki. 28th October 2024 We opened registration to anyone... dd90dc061e6cb739718362d647705e2898ca16cd 2249 2236 2025-05-01T20:24:40Z Atmois 13 Finish history wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[Atl.wiki:Contact|contact page]]! == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin == History == ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the [https://discord.gg/linux All Things Linux discord]. [[User:Electron271|Electron271]], Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, [[User:Kaizen|Kaizen]]. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spambots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also reimplemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[Special:Favoritelist|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to relicence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another relicencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[Atl.wiki:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== The Future ===== Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute. We are always happy to welcome new faces, to a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] 4d83ebf54898c78e03f91af5965e745b5c7a39ba 4 340 2237 2182 2025-05-01T18:55:13Z Atmois 13 Atmois moved page [[Guidelines]] to [[Atl.wiki:Guidelines]]: Move to meta namespace wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Guidelines#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. ====== <u>Accessibility</u> ====== We aim to make the wiki accessible to users of all ability levels, be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrival Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] 35c77c6ae07bfb84e26211ad1167db9b6c0ae7ad 0 621 2238 2025-05-01T18:55:13Z Atmois 13 Atmois moved page [[Guidelines]] to [[Atl.wiki:Guidelines]]: Move to meta namespace wikitext text/x-wiki #REDIRECT [[Atl.wiki:Guidelines]] 430478cf0eb19c0552b1ee3bdaf8a382b8d5f6a6 0 594 2239 2110 2025-05-01T18:56:11Z Atmois 13 Change redirect wikitext text/x-wiki #REDIRECT [[Atl.wiki:Guidelines]] 430478cf0eb19c0552b1ee3bdaf8a382b8d5f6a6 10 483 2240 2115 2025-05-01T18:57:20Z Atmois 13 Update link wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[Atl.wiki:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /> <includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]] }} </includeonly> <noinclude> {{/doc}}</noinclude> c340365288d01bb537b83ac6b3538f929795ddb9 10 494 2241 1909 2025-05-01T18:57:46Z Atmois 13 Update link wikitext text/x-wiki This template should be placed on pages which might not meet the wiki's [[Atl.wiki:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Biased Tone", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance Templates]]</includeonly> 320027f73a417db744d8a7a4d8b3ce33a57834f9 10 513 2242 2114 2025-05-01T18:58:00Z Atmois 13 Update link wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This template is to be used on pages which may lack credible citations, as per our [[Atl.wiki:Guidelines#Citations|citations guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Needs_Citations|| [[Category:Needs_Citations]] }} </includeonly> <noinclude> {{/doc}}</noinclude> c9c309ed6cee5bd8d91f90b8b6345c53d96187a8 10 514 2243 1912 2025-05-01T18:58:11Z Atmois 13 Update link wikitext text/x-wiki This template should be placed on pages which may lack credible citations, as per our [[Atl.wiki:Guidelines#Citations|citations policy]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations. == Usage == <code>{{tlx|Needs Citations}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 02812499e3901a7c6dc187f9ab8b0055fbc830ec 10 523 2244 2116 2025-05-01T18:58:24Z Atmois 13 Update link wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This template means the author of a page is still actively working on the page, and this serves to notify other editors to check with them before potentially creating conflicting changes and to notify the staff that it may not meet the wiki's [[Atl.wiki:Guidelines|guidelines]] yet.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> e9883c89731215347f43e52a46f471f90d7009e6 10 524 2245 1905 2025-05-01T18:58:35Z Atmois 13 Update link wikitext text/x-wiki This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes and to notify the staff that it may not meet the [[Atl.wiki:Guidelines|contributing standards]] yet. == Usage == <code>{{tlx|Work_In_Progress}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 95503df8ddc0e5794a752380c72d99223e71f577 3000 572 2246 1959 2025-05-01T18:59:04Z Atmois 13 update link wikitext text/x-wiki TLDR: Ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, and all changes must be approved by staff for public viewing via ApprovedRevs. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. Guides are anything that explain to a user ''how'' to do something. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide how to harden Firefox with more privacy focused options, we expect and will maintain a higher standard of quality and safety than standard articles. This is because you are providing information to users to do things on their own hardware, which could potentially damage the systems or cause data loss. All main wiki policies apply, including but not limited to the [[Atl.wiki:Code of Conduct|Code of Conduct]] and the wiki [[Atl.wiki:Guidelines|guidelines]]. However, a special set of criteria are required, as outlined below: * All pages MUST contain the GuideWarning template at the beginning of the page. There are no exceptions to this rule, and violations of it will have the edits rejected until it has been added. You can add it using <code><nowiki>{{GuideWarning}}</nowiki></code> at the beginning of the page. {{Guide Warning}} * To prevent malicious information being distributed on atl.wiki, all changes to guides from non-moderators/ATL staff must be approved by a moderator. When you make an edit it is submitted for review automatically and will normally be reviewed within 24 hours, but if it is still pending after 48 hours feel free to contact an admin. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this, so please double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. We aim to provide unbiased and informative content to all users, your personal views, whilst valid, are not relevant here. * You are responsible for ensuring all commands you provide are functional and not dangerous, if there are risks with running a specific command ensure to clearly state them when listing the command and if it's a command dependent on specific system requirements ensure to outline the requirements or prerequisites clearly. Any dangerous commands provided will be held accountable to whomever adds them to a guide. You can see a good example of a guide here on the guide for '''[[Guides:Setting up Flathub on Fedora|Setting up Flathub on Fedora]]''' which is maintained and has been made in accordance with our guidelines and standards, 8ec66c17a92cdbfe360b9c3f7b137740ce87d5c0 0 622 2247 2025-05-01T19:02:20Z Atmois 13 Create placeholder wikitext text/x-wiki This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} 12ee7ed1aa7e0f329b15a150a2ba082d2bedc0d2 0 623 2248 2025-05-01T19:44:20Z Wilbur 142 create basic endeavouros page, could do with some more citations but most things can be found on the already cited references wikitext text/x-wiki '''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">https://endeavouros.com/</ref> === Overview === * Developer: EndeavourOS Team * OS Family: [[Linux]] (Unix-like) * Source Model: [[Open-source]] * Update Method: [[Rolling release]] * Package Manager: [[pacman]] (via Arch's repositories and the [[Arch User Repository|AUR]]) * Default User Interface: [[Plasma|KDE Plasma]] (installer), however many others are available including [[XFCE|Xfce]], [[GNOME]], [[i3]], [[Cinnamon]], [[MATE]], [[LXQt]], and [[Budgie]].<ref name=":0" /> * Architecture: [[x86_64]], [[aarch64]] === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>https://endeavouros.com/about-us/</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning Arch Linux fundamentals. === Installation === EndeavourOS provides an ISO with the Calamares installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === EndeavourOS is fully compatible with Arch Linux, meaning it uses Arch's official repositories directly and adheres closely to Arch’s philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * AUR Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate AUR package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * Pacman Compatibility: Fully compatible with Arch’s pacman package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for Arch Linux are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla Arch, or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the AUR, as well as EndeavourOS-specific themes and utilities.<ref>https://repo.c48.uk/endeavouros/repo/endeavouros/</ref> This is simply a pacman repository that can simply be added to any Arch Linux system if desired. 2c6555d05194877a25ca124b4b57b5e1966a2940 8 357 2251 1976 2025-05-01T20:32:38Z Atmois 13 Font fix try css text/css /* All CSS here will be loaded for users of the Citizen skin */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: "Fira Mono"; } :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } /* * Footer icons * We use custom footer icons from https://starcitizen.tools for our footers, the following CSS comes from their wiki */ #footer-icons a { border: 0; padding: 0; background: transparent; opacity: var( --opacity-icon-base ); transition: opacity 250ms ease; } #footer-icons a:hover { opacity: var( --opacity-icon-base--hover ); } #footer-icons a:active { opacity: var( --opacity-icon-base--active ); } /* More space between icons */ #footer-icons ul, #footer-icons li { gap: var( --space-md ); } #footer-icons img { width: auto; height: 32px; } /* Divide footer links into two columns */ #footer-places { column-count: 2; } /* Fix misalignment in Safari and Firefox when using two columns */ #footer-places ul { display: initial; } /* Darken the footer icon in light mode */ .skin-citizen-light #footer-icons a { filter: invert( 1 ) hue-rotate( 180deg ); } e4479311d2427017343aa458030aae7bb793e8ac 2253 2251 2025-05-01T20:36:46Z Atmois 13 try again css text/css /* All CSS here will be loaded for users of the Citizen skin */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: "Fira Mono"; --font-family-monospace: "Fira Mono"; } :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } /* * Footer icons * We use custom footer icons from https://starcitizen.tools for our footers, the following CSS comes from their wiki */ #footer-icons a { border: 0; padding: 0; background: transparent; opacity: var( --opacity-icon-base ); transition: opacity 250ms ease; } #footer-icons a:hover { opacity: var( --opacity-icon-base--hover ); } #footer-icons a:active { opacity: var( --opacity-icon-base--active ); } /* More space between icons */ #footer-icons ul, #footer-icons li { gap: var( --space-md ); } #footer-icons img { width: auto; height: 32px; } /* Divide footer links into two columns */ #footer-places { column-count: 2; } /* Fix misalignment in Safari and Firefox when using two columns */ #footer-places ul { display: initial; } /* Darken the footer icon in light mode */ .skin-citizen-light #footer-icons a { filter: invert( 1 ) hue-rotate( 180deg ); } 6678c40b32463ba51ed200105bad918a93939dae 2254 2253 2025-05-01T20:39:22Z Atmois 13 try again css text/css /* All CSS here will be loaded for users of the Citizen skin */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; --font-family-monospace: var(--font-family-citizen-monospace), 'Menlo', 'Consolas', 'Liberation Mono', 'Courier New', monospace; } :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } /* * Footer icons * We use custom footer icons from https://starcitizen.tools for our footers, the following CSS comes from their wiki */ #footer-icons a { border: 0; padding: 0; background: transparent; opacity: var( --opacity-icon-base ); transition: opacity 250ms ease; } #footer-icons a:hover { opacity: var( --opacity-icon-base--hover ); } #footer-icons a:active { opacity: var( --opacity-icon-base--active ); } /* More space between icons */ #footer-icons ul, #footer-icons li { gap: var( --space-md ); } #footer-icons img { width: auto; height: 32px; } /* Divide footer links into two columns */ #footer-places { column-count: 2; } /* Fix misalignment in Safari and Firefox when using two columns */ #footer-places ul { display: initial; } /* Darken the footer icon in light mode */ .skin-citizen-light #footer-icons a { filter: invert( 1 ) hue-rotate( 180deg ); } bee3aa349fc0b6bea8d329e0b24d4ca30206d80d 2255 2254 2025-05-01T20:40:51Z Atmois 13 remove css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } /* * Footer icons * We use custom footer icons from https://starcitizen.tools for our footers, the following CSS comes from their wiki */ #footer-icons a { border: 0; padding: 0; background: transparent; opacity: var( --opacity-icon-base ); transition: opacity 250ms ease; } #footer-icons a:hover { opacity: var( --opacity-icon-base--hover ); } #footer-icons a:active { opacity: var( --opacity-icon-base--active ); } /* More space between icons */ #footer-icons ul, #footer-icons li { gap: var( --space-md ); } #footer-icons img { width: auto; height: 32px; } /* Divide footer links into two columns */ #footer-places { column-count: 2; } /* Fix misalignment in Safari and Firefox when using two columns */ #footer-places ul { display: initial; } /* Darken the footer icon in light mode */ .skin-citizen-light #footer-icons a { filter: invert( 1 ) hue-rotate( 180deg ); } 4b46ded53c921eb80864b67b8025488ab2208834 8 624 2257 2025-05-01T20:48:49Z Atmois 13 Recreate css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; --font-family-monospace: var(--font-family-citizen-monospace), 'Menlo', 'Consolas', 'Liberation Mono', 'Courier New', monospace; } 0e190f6a8281a49458fa42889136f63b6e221aa5 2262 2257 2025-05-02T15:01:44Z Atmois 13 Update css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } cb13506087856f3aca4dc8fad92cdb764b1dac5c 4 327 2258 2207 2025-05-01T20:53:09Z Atmois 13 test wikitext text/x-wiki boo {{#invoke:StatsLine|stats}} Admin testing page. __NOINDEX__ __NONEWSECTIONLINK__ khrozma was not here atmois was here test - kaizen electron was here {{Special:Contribute}} more testing???? test n 1203 idk potato testing testing 1 2 3 4<ref>hi</ref> {{MascotInfobox | title = Test | image = [[File:Larry the cow.png|Larry the Cow]] | caption = Test }} 706fd2a99a8f1ab3c383882a747c8b11b8ef7b9e 0 625 2259 2025-05-02T10:00:57Z Wilbur 142 create cachyos page, references are at the bottom but not throughout yet wikitext text/x-wiki '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance. It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch’s rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was developed by a team led by Peter "ptr1337" Jung to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2023. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites. == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the AUR while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom Proton (`proton-cachyos`) and Wine builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Default browser: Cachy Browser (hardened Firefox fork). * Support for Btrfs snapshots with Limine bootloader. * Optional Firejail, DNSCrypt, AppArmor hardening. == Desktop Environments == CachyOS provides several preconfigured desktop environments: * KDE Plasma (default) * GNOME * Xfce * LXQt * Cutefish * Wayfire * i3, bspwm, Openbox Users can select their preferred environment during installation. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Btrfs with snapshot support is the default filesystem. * Full UEFI, ZFS, and Secure Boot support. * Smooth installation experience designed for newcomers to Arch. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times. == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. * Limine bootloader for rollback support via Btrfs. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub]. * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references> <ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos CachyOS Kernel Repository on GitHub]</ref> <ref name="official-docs">[https://wiki.cachyos.org Official CachyOS Wiki]</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos CachyOS on DistroWatch]</ref> <ref name="phoronix">[https://www.phoronix.com/scan.php?page=news_topic&item=CachyOS Phoronix - CachyOS Articles]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ BetaNews on CachyOS Performance]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks]</ref> </references> 64ff7185e4a0a1510eaebb24b9bb61831811646b 2260 2259 2025-05-02T10:03:28Z Wilbur 142 fix references wikitext text/x-wiki '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch’s rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was developed by a team led by Peter "ptr1337" Jung to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2023. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the AUR while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom Proton (`proton-cachyos`) and Wine builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Default browser: Cachy Browser (hardened Firefox fork). * Support for Btrfs snapshots with Limine bootloader. * Optional Firejail, DNSCrypt, AppArmor hardening. == Desktop Environments == CachyOS provides several preconfigured desktop environments: * KDE Plasma (default) * GNOME * Xfce * LXQt * Cutefish * Wayfire * i3, bspwm, Openbox Users can select their preferred environment during installation. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Btrfs with snapshot support is the default filesystem. * Full UEFI, ZFS, and Secure Boot support. * Smooth installation experience designed for newcomers to Arch. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. * Limine bootloader for rollback support via Btrfs. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references> <ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos CachyOS Kernel Repository on GitHub]</ref> <ref name="official-docs">[https://wiki.cachyos.org Official CachyOS Wiki]</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos CachyOS on DistroWatch]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ BetaNews on CachyOS Performance]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks]</ref> </references> 43d0dae4532a856b5d5a2c7ca6079c399d8c982f 2261 2260 2025-05-02T10:21:18Z Wilbur 142 link to other wiki pages because i forgot to do this earlier wikitext text/x-wiki '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch’s rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was developed by a team led by Peter "ptr1337" Jung to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2023. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Default browser: Cachy Browser (hardened Firefox fork). * Support for Btrfs snapshots with Limine bootloader. * Optional Firejail, DNSCrypt, AppArmor hardening. == Desktop Environments == CachyOS provides several preconfigured desktop environments: * [[Plasma|KDE Plasma]] (default) * [[GNOME]] * [[XFCE|Xfce]] * [[LXQt]] * [[Cutefish]] * [[Wayfire]] * [[i3]], [[bspwm]], [[Openbox]] Users can select their preferred environment during installation. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * [[Btrfs]] with snapshot support is the default filesystem. * Full UEFI, ZFS, and Secure Boot support. * Smooth installation experience designed for newcomers to Arch. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. * Limine bootloader for rollback support via Btrfs. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references> <ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos CachyOS Kernel Repository on GitHub]</ref> <ref name="official-docs">[https://wiki.cachyos.org Official CachyOS Wiki]</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos CachyOS on DistroWatch]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ BetaNews on CachyOS Performance]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks]</ref> </references> 5dce165248de7b7e283b4d07a38da151b93f5473 0 1 2263 2213 2025-05-02T16:01:47Z Atmois 13 Fix link wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Our Key Values ====== We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed on our [[Atl.wiki:Contact|Contact]] page. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ 79c77f887857746b683f9f45a0daff856d534676 4 536 2264 1799 2025-05-02T20:03:39Z Atmois 13 Add section on generative AI wikitext text/x-wiki === 1. Safe for Work (SFW) Policy === atl.wiki is a '''Safe for Work (SFW)''' environment. '''NSFW (Not Safe for Work) content and discussions are strictly prohibited'''. While NSFW typically refers to sexually explicit material, the definition may evolve to include other forms of sensitive content. This applies to all content on the wiki, including but not limited to text, images & media. ==== Prohibited Content: ==== * '''Sexually explicit material''' in any form. * '''Violence, gore, or depictions of animal abuse'''. * '''Glorification of self-harm or suicide'''. == 2. Mutual Respect == atl.wiki is a '''respectful''' and '''inclusive''' community. ==== Expected Behaviour: ==== * Treat others '''with humility and respect'''. * Keep interactions '''constructive and considerate'''. * '''No harassment''': Bullying, doxxing, or coordinated attacks are '''strictly prohibited'''. * '''No hate speech''': Discriminatory remarks on any personal characteristics will not be tolerated. * '''No threats''': Direct or indirect threats against individuals or groups will result in '''immediate action'''. == 3. Responsible Expression & Discussions == The wiki welcomes '''diverse perspectives''' and encourages constructive discussions, but it is not a '''free-for-all debate forum'''. Please ensure all discussions are kept to talk pages and not done on articles unless it has been designated as a discussion page. ==== Guidelines for Expression: ==== * '''Stay on topic''': Discussions should focus on '''Linux, open-source software, and related technologies'''. * '''No disruptive debates''': Heated, repetitive, or toxic arguments will be moderated. * '''Avoid professional advice''': The wiki does not provide '''medical, legal, financial, or religious advice'''. == 4. Avoidance of Elitism == Linux and technology is for '''everyone''', from beginners to experts. ==== Expected Behaviour: ==== * '''Respect different choices''': Users may prefer different '''distros, desktop environments, package managers, or workflows'''. * '''No gatekeeping''': Beginners should feel welcome, not discouraged. We want to foster a growing Linux and FOSS community. == 5. Respecting Moderators & Rules == Moderators help maintain order. If a moderator asks you to '''modify behaviour, please cooperate'''. * '''Disagreements should be handled via the wiki staff''', not public disputes. * '''Do not backseat moderate''': If someone breaks a rule, report it instead of escalating the situation. == 6. Language Requirement: English Only == * The wiki uses '''English as the primary language'''. == 7. Content Guidelines == All contributions must align with the wiki’s '''goal of providing high-quality Linux documentation'''. ==== Prohibited Content: ==== * '''Low-effort, spam, or non-constructive edits'''. * '''Off-topic material''' unrelated to Linux, open-source software or general technology. * '''Unverified or misleading technical information.''' * '''Spam or self-promoting content''' not relevant to the article. * AI Generated images are prohibited unless it is relevant to an article and clearly disclosed as being AI generated. * Use of generative AI to write content which will be published on the wiki is prohibited. However, AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used is permitted. == 8. Privacy & Security == * '''Do not dox or share personal information''' of other users. * '''Be cautious about sharing your own information.''' == 9. Enforcement & Punishments == Moderators '''reserve the right''' to take appropriate action depending on the severity of violations. If you believe a '''member of the team has abused their powers''', it should be '''reported to the administrators''' through a method listed [[Main Page#Contacts|here]]. ==== Possible Actions: ==== * '''Warnings''': Used for minor infractions. * '''Blocks''': Temporary restrictions from editing or participating. * '''IP Blocks''': Restricting editing access entirely. == 10. Punishment Evasion & Appeals == * '''Using alt accounts, VPN's or proxies to evade punishments will result in further punishment for yourself'''. * If you believe a punishment was unfair, you may '''appeal by contacting an administrator''' through a method listed [[Main Page#Contacts|here]]. == 11. Final Note: Exercise Common Sense == Not every situation can be predicted. Use '''good judgment, respect others, and contribute positively''' to the Linux community. If in doubt, '''ask for clarification rather than assuming'''. Thank you for being part of the '''atl.wiki'''! <blockquote>''<small>The Code of Conduct (CoC) for the wiki is adapted from the [https://allthingslinux.org/code-of-conduct All Things Linux CoC].</small>'' </blockquote> [[Category:Meta]] 570175071ed259193b330bbb1610ae5398277f23 0 626 2266 2025-05-03T17:47:01Z Wilbur 142 create Manjaro page (this page contains many links to non-existent wiki articles, but that will become less of a problem as time goes on anyway) wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>https://manjaro.org/</ref>. It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release. It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]]. <ref name=":0">https://distrowatch.com/table.php?distribution=manjaro</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>https://wiki.manjaro.org/index.php/Pamac</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>https://en.wikipedia.org/wiki/Manjaro</ref><ref>https://www.ubuntumint.com/manjaro-linux-history/</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>https://www.geeksforgeeks.org/how-to-install-manjaro-linux/</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch’s base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch’s, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro’s custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro-specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it syncs with Arch’s upstream packages selectively, manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>https://itsfoss.com/manjaro-vs-arch-linux/</ref> This tiered approach helps prevent system breakage and supports a smoother user experience. Manjaro packages may differ slightly or carry additional patches or branding. 0ee58a4fbc8edfdb8cd35680a8b28e04b87b416c 2 584 2267 1994 2025-05-04T08:42:21Z Atmois 13 Atmois moved page [[User:Absynth]] to [[User:Absynth@allthingslinux.org]]: Automatically moved page while merging the account "Absynth" to "[[User:Absynth@allthingslinux.org|Absynth@allthingslinux.org]]" wikitext text/x-wiki hello, all things linux wiki! my name is abby and my discord handle is <u>@absyn.th</u>! [[File:Gscreenshot 2025-04-05-023435.png|thumb]]i run debian linux on most of my machines. my main machine runs debian with cinnamon desktop, my older laptops run debian with MATE desktop. i wrote the first draft of the [[MATE|MATE wikipage]] here, and actively maintain and update it. (because no one else cares about MATE, lol...) i also wrote the first draft for [[xenia]]. i use the micro text editor and bash shell. i prefer AMD over intel or nvidia, and if i have a choice, i use a ryzen cpu and radeon graphics. i use exclusively HP laptops, because those are the ones that have happened to fall into my lap as e-waste / cheap refurbished computers. because of this, i know a lot about HP computers' BIOS and repairing HP laptops across different eras. == My Machines == <blockquote>Not an exhaustive list, but the four I use most frequently and message with on the Discord</blockquote> ===== Datum (my main desktop) ===== Debian Testing (Cinnamon) Home-built, 2023 Dual monitor (one 1440p@144 and one 1080p@165) Ryzen 9 5900x (24 threads) CPU overclocked to 4.1 GHz Radeon RX 6700XT GPU 80GB DDR4 1TB NVME SSD boot drive (ext4) 2TB NVME SSD storage drive (ext4) ===== Qubit (my work laptop) ===== Debian Testing (Cinnamon) HP Dragonfly G4 (2023, originally Windows 11) ===== Dysnomia (my personal laptop) ===== Debian Testing (Cinnamon) HP 17-by1053DX Laptop PC (2019, originally Windows 10) Upgraded to 32GB of laptop DDR4 ===== Vision (my spare laptop) ===== Debian Stable (MATE) HP 2000-2d09CA Notebook PC (2011, originally Windows 8) Upgraded to 16GB of laptop DDR3 (temporarily, since it really only needs 8 - i'll take one of the sticks for another laptop that needs it at some point) c3b7b9439a0050944218c690298d4fb756c0299f 2269 2267 2025-05-04T08:43:33Z Atmois 13 Atmois moved page [[User:Absynth@allthingslinux.org]] to [[User:Absynth]] without leaving a redirect: Move after rename user wikitext text/x-wiki hello, all things linux wiki! my name is abby and my discord handle is <u>@absyn.th</u>! [[File:Gscreenshot 2025-04-05-023435.png|thumb]]i run debian linux on most of my machines. my main machine runs debian with cinnamon desktop, my older laptops run debian with MATE desktop. i wrote the first draft of the [[MATE|MATE wikipage]] here, and actively maintain and update it. (because no one else cares about MATE, lol...) i also wrote the first draft for [[xenia]]. i use the micro text editor and bash shell. i prefer AMD over intel or nvidia, and if i have a choice, i use a ryzen cpu and radeon graphics. i use exclusively HP laptops, because those are the ones that have happened to fall into my lap as e-waste / cheap refurbished computers. because of this, i know a lot about HP computers' BIOS and repairing HP laptops across different eras. == My Machines == <blockquote>Not an exhaustive list, but the four I use most frequently and message with on the Discord</blockquote> ===== Datum (my main desktop) ===== Debian Testing (Cinnamon) Home-built, 2023 Dual monitor (one 1440p@144 and one 1080p@165) Ryzen 9 5900x (24 threads) CPU overclocked to 4.1 GHz Radeon RX 6700XT GPU 80GB DDR4 1TB NVME SSD boot drive (ext4) 2TB NVME SSD storage drive (ext4) ===== Qubit (my work laptop) ===== Debian Testing (Cinnamon) HP Dragonfly G4 (2023, originally Windows 11) ===== Dysnomia (my personal laptop) ===== Debian Testing (Cinnamon) HP 17-by1053DX Laptop PC (2019, originally Windows 10) Upgraded to 32GB of laptop DDR4 ===== Vision (my spare laptop) ===== Debian Stable (MATE) HP 2000-2d09CA Notebook PC (2011, originally Windows 8) Upgraded to 16GB of laptop DDR3 (temporarily, since it really only needs 8 - i'll take one of the sticks for another laptop that needs it at some point) c3b7b9439a0050944218c690298d4fb756c0299f 0 628 2270 2025-05-05T16:45:40Z Wilbur 142 made linux mint page, and found out that the package search website seems not to work anymore so i had to cite my own mirror again lol wikitext text/x-wiki Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>https://linuxmint.com/</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>https://iso.atl.dev/l/linuxmint</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>https://distrowatch.com/table.php?distribution=mint</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the [[Plasma|KDE]] desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use [[Ubuntu]] as its base and featured the GNOME desktop environment.<ref>https://www.linuxmint.com/about.php</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. The latest release, Linux Mint 22.1 "Xia", was launched in January 2025 and is supported until 2029.<ref>https://www.linuxmint.com/download.php</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications. fe7ad27aca89817db3a632ea02b7e62024c42ab2 2271 2270 2025-05-05T16:46:37Z Wilbur 142 (and apparently i didnt save said reference) wikitext text/x-wiki Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>https://linuxmint.com/</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>https://iso.atl.dev/l/linuxmint</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>https://distrowatch.com/table.php?distribution=mint</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the [[Plasma|KDE]] desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use [[Ubuntu]] as its base and featured the GNOME desktop environment.<ref>https://www.linuxmint.com/about.php</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. The latest release, Linux Mint 22.1 "Xia", was launched in January 2025 and is supported until 2029.<ref>https://www.linuxmint.com/download.php</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>https://repo.c48.uk/mint/pkgs/pool/</ref> f330ccc83eb44c192b021898a138706aca02d35a 0 198 2272 2097 2025-05-06T10:56:53Z Wilbur 142 add some links to pages, even if they're not created yet wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments||Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init system|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 91d6b8138ce105f4c08d28e5b0db671652cd6343 2273 2272 2025-05-06T11:58:06Z Wilbur 142 Init System needed a capital S to link wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments||Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |A distribution that focuses on quickly installing, updating and removing software, the main feature being support for the musl and glibc implementations. |} [[Category:Linux Distributions]] 78661124ac90795c4697114eed6d32eab53e1315 0 629 2275 2025-05-07T00:42:11Z Imnotpolar 112 Redirect to Desktop Environments wikitext text/x-wiki #REDIRECT [[Desktop Environments]] 0d2b0e7b1c1075c81af12dd0cb327527cd4f5a52 0 291 2276 2036 2025-05-07T00:58:24Z Imnotpolar 112 Overhaul wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:GNOME logo.svg|200px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 48, 2025-03-19 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = [https://gnome.org/] }} [[File:GNOME 46.png|thumb|A desktop running GNOME 46 in Fedora Workstation 40]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>What is Free Software? https://www.gnu.org/philosophy/free-sw.en.html</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>https://en.wikipedia.org/wiki/GNOME#History</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>https://foundation.gnome.org/</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. [[Category:Desktop Environments]] 7f252933921ff54b1001709c5a94f37edd081b70 2277 2276 2025-05-07T00:59:57Z Imnotpolar 112 Removed citations tag due to the significant overhaul of the page wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|200px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 48, 2025-03-19 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = [https://gnome.org/] }} [[File:GNOME 46.png|thumb|A desktop running GNOME 46 in Fedora Workstation 40]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>What is Free Software? https://www.gnu.org/philosophy/free-sw.en.html</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>https://en.wikipedia.org/wiki/GNOME#History</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>https://foundation.gnome.org/</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. [[Category:Desktop Environments]] ee10151ba1312a1cc317e8c455ab471bfd951716 2278 2277 2025-05-07T01:07:07Z Imnotpolar 112 Added citation for Qt not being licensed under free software. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|200px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 48, 2025-03-19 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = [https://gnome.org/] }} [[File:GNOME 46.png|thumb|A desktop running GNOME 46 in Fedora Workstation 40]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>What is Free Software? https://www.gnu.org/philosophy/free-sw.en.html</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>https://en.wikipedia.org/wiki/Qt_(software)#Early_developments</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>https://en.wikipedia.org/wiki/GNOME#History</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>https://foundation.gnome.org/</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. [[Category:Desktop Environments]] c89e500a3254b05edaa23572ab737caafc872e73 0 291 2279 2278 2025-05-07T01:09:08Z Imnotpolar 112 fixed gnome.org link wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|200px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 48, 2025-03-19 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[File:GNOME 46.png|thumb|A desktop running GNOME 46 in Fedora Workstation 40]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>What is Free Software? https://www.gnu.org/philosophy/free-sw.en.html</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>https://en.wikipedia.org/wiki/Qt_(software)#Early_developments</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>https://en.wikipedia.org/wiki/GNOME#History</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>https://foundation.gnome.org/</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. [[Category:Desktop Environments]] a0a000619159ee808b3629345df168a8d56728c2 2298 2279 2025-05-10T11:24:27Z Imnotpolar 112 Gnome Logo Update to White (more readable on the wiki's default theme) and fixed citations to follow wiki guidelines wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|300px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 48, 2025-03-19 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[File:GNOME 46.png|thumb|A desktop running GNOME 46 in Fedora Workstation 40]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>[https://www.gnu.org/philosophy/free-sw.en.html What is Free Software?], GNU (Accessed: May 7, 2025)</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>[[wikipedia:Qt_(software)#Early_developments|Early Developments of QT]], Wikipedia (Accessed: May 7, 2025)</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>[[wikipedia:GNOME#History|History of GNOME]], Wikipedia (Accessed: May 7, 2025)</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>[https://foundation.gnome.org/ GNOME Foundation Website]</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. [[Category:Desktop Environments]] d3a68df89c3ad121948de81ef86f1ccd89cc8ba5 4 340 2280 2237 2025-05-07T09:54:49Z Atmois 13 typo wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Guidelines#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. ====== <u>Accessibility</u> ====== We aim to make the wiki accessible to users of all ability levels, be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] 1ce87bd7e4d53d0ca58404bd6dfd78e38cee050b 2296 2280 2025-05-07T10:30:13Z Atmois 13 Add citations template information wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Guidelines#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. ====== <u>Accessibility</u> ====== We aim to make the wiki accessible to users of all ability levels, be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=2021 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template <code>Cite</code> and then filling out the relevant information in the interface. Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] f3bf23bbbec780538cb11eef14db60a79b7667f9 10 631 2283 2025-05-07T10:06:22Z Atmois 13 Try cite template wikitext text/x-wiki <includeonly>{{#if: {{{url|}}} | [{{{url}}} {{{title}}}] | {{{title|Untitled}}} }},{{#if: {{{author|}}} | {{{author}}}, }}{{#if: {{{year|}}} | {{{year}}} }} ({{#time:Y-m-d}}).</includeonly><noinclude>{{documentation}}</noinclude> 91407dae8a9f223e6177fa096c04d3c12bd1a2ce 2284 2283 2025-05-07T10:06:38Z Atmois 13 remove issue wikitext text/x-wiki <includeonly>{{#if: {{{url|}}} | [{{{url}}} {{{title}}}] | {{{title|Untitled}}} }},{{#if: {{{author|}}} | {{{author}}}, }}{{#if: {{{year|}}} | {{{year}}} }} ({{#time:Y-m-d}}).</includeonly> 09c18171845d958165b059f31eec3d96e429c5da 2285 2284 2025-05-07T10:09:01Z Atmois 13 Tidy up wikitext text/x-wiki <includeonly> {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]' | ''{{{title|Untitled}}}'' }} , {{#if: {{{author|}}} | {{{author}}}, }} {{#if: {{{year|}}} | {{{year}}} }} (Accessed: {{#time:F j, Y}}) </includeonly> 80ef4159a9f9e8af98479fb1e3ef9d90fef765ab 2286 2285 2025-05-07T10:10:12Z Atmois 13 fix p2 wikitext text/x-wiki <includeonly> {{#if: {{{url|}}} |''[{{{url}}} {{{title}}}]'' |''{{{title|Untitled}}}'' }} , {{#if: {{{author|}}} |{{{author}}}, }} {{#if: {{{year|}}} |{{{year}}} }} (Accessed: {{#time:F j, Y}}) </includeonly> f1dcb852bdd42b9880280669c37e47541130b70a 2287 2286 2025-05-07T10:12:23Z Atmois 13 fix p4 wikitext text/x-wiki <includeonly>{{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled}}}'' }},{{#if: {{{author|}}} | {{{author}}}, }}{{#if: {{{year|}}} | {{{year}}} }} (Accessed: {{#time:F j, Y}}).</includeonly> e9fbb2779f186e326081fa59eb2ee69086a0f00d 2288 2287 2025-05-07T10:12:50Z Atmois 13 tidy format wikitext text/x-wiki <includeonly>{{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled}}}'' }},{{#if: {{{ author|}}} | {{{author}}}, }}{{#if: {{{ year|}}} | {{{year}}} }} (Accessed: {{#time:F j, Y}}).</includeonly> 43767c928892923265ad780212b3f51325de80f0 2289 2288 2025-05-07T10:13:51Z Atmois 13 try fix formatting again wikitext text/x-wiki <includeonly> {{#if: {{{url|}}} |''[{{{url}}} {{{title}}}]'' |''{{{title|Untitled}}}'' }} , {{#if: {{{author|}}} | {{!}} {{{author}}}, }} {{#if: {{{year|}}} | {{!}} {{{year}}} }} (Accessed: {{#time:F j, Y}}). </includeonly> 9b116303ced3b102b6d348984e9c04063328724a 2290 2289 2025-05-07T10:14:53Z Atmois 13 fix again, this is so annoying wikitext text/x-wiki <includeonly> {{#if: {{{url|}}} |''[{{{url}}} {{{title}}}]'' |''{{{title|Untitled}}}'' }} {{#if: {{{author|}}} | , {{{author}}} }} {{#if: {{{year|}}} | , {{{year}}} }} (Accessed: {{#time:F j, Y}}). </includeonly> d18b26ff536f897296cf44640ae6d641c2cb1409 2291 2290 2025-05-07T10:16:01Z Atmois 13 try add whitespace wikitext text/x-wiki <includeonly>{{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled}}}'' }},{{#if: {{{author|}}} | {{{ author}}}, }}{{#if: {{{year|}}} | {{{ year}}} }} (Accessed: {{#time:F j, Y}}).</includeonly> db3dba09a4453dbdd13e67c62f29a26dbaf8950a 2292 2291 2025-05-07T10:16:55Z Atmois 13 try again wikitext text/x-wiki <includeonly> {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled}}}'' }}, {{#if: {{{author|}}} | {{{author}}}, }} {{#if: {{{year|}}} | {{{year}}} }} (Accessed: {{#time:F j, Y}}). </includeonly> 678db9c24b64d781a3e93d539211529a809b56c3 2294 2292 2025-05-07T10:24:14Z Atmois 13 try ake it referce stuff now wikitext text/x-wiki <includeonly> <ref>{{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled}}}'' }}, {{#if: {{{author|}}} | {{{author}}}, }} {{#if: {{{year|}}} | {{{year}}} }} (Accessed: {{#time:F j, Y}}).</ref> </includeonly> 4a361b7b4b70311e1089244c62f663e0e12660c5 2318 2294 2025-05-11T11:02:53Z Atmois 13 Fix format wikitext text/x-wiki <includeonly> <ref> {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled}}}''}}, {{#if: {{{author|}}} | {{{author}}}{{#if: {{{year|}}} |, }}}} {{#if: {{{year|}}} | {{{year}}} }} (Accessed: {{#time:F j, Y}}). </ref> </includeonly> dd93342d3ab7e86901e1441779081f26542112f3 2321 2318 2025-05-11T11:06:25Z Atmois 13 Add templatedata wikitext text/x-wiki <includeonly> <ref> {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled}}}''}}, {{#if: {{{author|Unknown}}} | {{{author}}}{{#if: {{{year|}}} |, }}}} {{#if: {{{year|}}} | {{{year}}} }} (Accessed: {{#time:F j, Y}}). </ref> </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "default": "Untitled", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Unknown", "required": true }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "default": "2025" } }, "description": "Add a citation using our reccomeneded structure to a page", "format": "inline" } </templatedata> </noinclude> 94765988e578541a88eef40a5b9beaf2cc72c7cb 2322 2321 2025-05-11T11:09:56Z Atmois 13 Update wikitext text/x-wiki <includeonly> <ref> ''[{{{url}}} {{{title}}}]'', {{{author}}}{{#if: {{{year|}}} |, {{{year}}} }} (Accessed: {{#time:F j, Y}}). </ref> </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> a1dc9699942db08bd6938e58ea083dd9ddd307f6 2324 2322 2025-05-11T11:14:21Z Atmois 13 try fix again wikitext text/x-wiki <includeonly> <ref>{{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}'' }} {{#if: {{{year|}}} | {{{year}}} }} (Accessed: {{#time:F j, Y}}).</ref> </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 55e554daa394a2f8b2e55b4e85348b98ce43cdc4 2325 2324 2025-05-11T11:15:17Z Atmois 13 try fix again wikitext text/x-wiki <includeonly> <ref> {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}'' }} {{#if: {{{author|}}} | {{{author}}} }} {{#if: {{{year|}}} | ({{{year}}}) }} (Accessed: {{#time:F j, Y}}). </ref> </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> b2affe786d54cd1918e5fa69dbd1d86d0f30da22 2327 2325 2025-05-11T11:16:13Z Atmois 13 try again wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}'' }} {{#if: {{{author|}}} | {{{author}}} }} {{#if: {{{year|}}} | ({{{year}}}) }} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 9da8a037d31147975d884d513cbefac5a95bda6d 2328 2327 2025-05-11T11:17:09Z Atmois 13 Format wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}'' }} {{#if: {{{author|}}} | , {{{author}}} }} {{#if: {{{year|}}} | , {{{year}}} }} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 92b4da52e22c3a60e455e9fb7d82b953432a0cac 2329 2328 2025-05-11T11:17:23Z Atmois 13 Format wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}'' }} {{#if: {{{author|}}} |, {{{author}}} }} {{#if: {{{year|}}} |, {{{year}}} }} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 5fc95cb57173128d2b43eb270656f536b72e1a0a 2331 2329 2025-05-11T11:18:39Z Atmois 13 format fix? wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}'' }} {{#if: {{{author|}}} |, {{{author|Anon.}}} }} {{#if: {{{year|}}} |, {{{year}}} }} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 9ac14826e1abda442dae06d838976c60b4bd39e8 4 327 2293 2258 2025-05-07T10:17:36Z Atmois 13 wikitext text/x-wiki {{Cite |title=Example Page |url=https://example.com |author=John Doe |year=2021 }} 7eaa2e6d2b27caef826b1b14d93d42caef555f5d 2295 2293 2025-05-07T10:24:42Z Atmois 13 test wikitext text/x-wiki Claim A{{Cite |title=Example Page |url=https://example.com |author=John Doe |year=2021 }} <references /> b73f5e84000d4d0326f709e70b312647b4847e4e 2310 2295 2025-05-11T09:52:02Z Atmois 13 test transclusion wikitext text/x-wiki {{Atl.wiki:About}} Claim A{{Cite |title=Example Page |url=https://example.com |author=John Doe |year=2021 }} <references /> 0c1356fcf3421a36d08caea9218b513c4bff331b 2317 2310 2025-05-11T11:00:41Z Atmois 13 clear wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 632 2297 2025-05-10T11:03:31Z Imnotpolar 112 wikitext text/x-wiki == Licensing == {{Unknown_copyright}} 7b203fe194cc7883784f17c9e319306626ab2bfe 6 633 2299 2025-05-10T11:41:59Z Imnotpolar 112 wikitext text/x-wiki == Licensing == {{CC-BY-4.0}} bfaf7ac650a059f96b01d8c29482fd37825aaefc 4 593 2301 2220 2025-05-10T15:19:38Z Atmois 13 Expand key pages section wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[Guidelines#Standards|standards]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[Atl.wiki:Contact|Contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === * The [[Window Management System]] definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. * The [[Linux Distributions|Linux Distribution]] article which lists distros is lacking a lot of major distros and each section should have a short blurb and information about key facts about what distros under that group typically are (e.g. release cycle, package manager, etc) * The [[Package Manager]] page, which lists package managers, needs to be rewritten to compare and delve more into each package manager. * The [[Key Terms]] page needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table potentially * The [[Desktop Environments]] page needs to be written, it needs to contain basics around DE's and what they are and a list of DE's with a short blurb to each one and potentially key distros that offer them, a table could be used to list them. * The [[X Window Manager]] page, which lists WM's depending on the type, needs to be cleaned up to remove Wayland Compositors and each WM should have a short blurb to it and potentially key distros that offer them, a table could be used to list them. * [[External Resources]] requires a clean-up to be organised and categorised properly, could make use of wiki tables with a short blurb for all websites listed. * [[Choosing a Linux Distribution]] needs expansion for non beginner recommendations, under work from [[User:Absynth]]. * [[Common Issues and Troubleshooting]] needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. df20e2d48ea29f1c0ad43fa94f74a15312cdd312 3000 572 2302 2246 2025-05-10T15:23:53Z Atmois 13 Add link to main contributing apge wikitext text/x-wiki TLDR: Ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, and all changes must be approved by staff for public viewing via ApprovedRevs. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. Guides are anything that explain to a user ''how'' to do something. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide how to harden Firefox with more privacy focused options, we expect and will maintain a higher standard of quality and safety than standard articles. This is because you are providing information to users to do things on their own hardware, which could potentially damage the systems or cause data loss. All main wiki policies apply, including but not limited to the [[Atl.wiki:Code of Conduct|Code of Conduct]] and the wiki [[Atl.wiki:Guidelines|guidelines]]. We also recommend you check out our [[Atl.wiki:Contributing|Contributing]] as well as it has a lot of important and useful information for editors. However, a special set of criteria are required, as outlined below: * All pages MUST contain the GuideWarning template at the beginning of the page. There are no exceptions to this rule, and violations of it will have the edits rejected until it has been added. You can add it using <code><nowiki>{{GuideWarning}}</nowiki></code> at the beginning of the page. {{Guide Warning}} * To prevent malicious information being distributed on atl.wiki, all changes to guides from non-moderators/ATL staff must be approved by a moderator. When you make an edit it is submitted for review automatically and will normally be reviewed within 24 hours, but if it is still pending after 48 hours feel free to contact an admin. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this, so please double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. We aim to provide unbiased and informative content to all users, your personal views, whilst valid, are not relevant here. * You are responsible for ensuring all commands you provide are functional and not dangerous, if there are risks with running a specific command ensure to clearly state them when listing the command and if it's a command dependent on specific system requirements ensure to outline the requirements or prerequisites clearly. Any dangerous commands provided will be held accountable to whomever adds them to a guide. You can see a good example of a guide here on the guide for '''[[Guides:Setting up Flathub on Fedora|Setting up Flathub on Fedora]]''' which is maintained and has been made in accordance with our guidelines and standards, 903c9154e4a0f553593b59ffa39509ccddaf27cc 3000 634 2303 2025-05-10T17:04:29Z RatX2 149 This is an article explaining the process of creating a bootable USB drive using Ventoy wikitext text/x-wiki {{GuideWarning}} '''Setting up a bootable USB drive using Ventoy''' Ventoy is an open source tool commonly used to create bootable USB drives for various linux installations. The main benefits to this tool is that it allows you to store multiple bootable ISO files on one USB drive. '''Download and installation'''<br> 1. The Ventoy application can be found at https://www.ventoy.net/en/index.html<br> 2. Extract the downloaded zip file<br> 3. Insert your USB drive<br> 4. Inside the Ventoy folder, run the Ventoy2Disk.exe file<br> 5. Now inside the application, select your desired USB drive<br> 6. Press the Install button<br> '''Warning''': Creating a bootable USB drive will delete all data stored on said USB. Backup your data and use with caution. After installing Ventoy you can copy a linux ISO file onto the USB drive, thus creating a bootable USB drive. After installation you may need to disable secure boot, depending on your chosen Linux distribution. Once the USB drive is made bootable, you can proceed to the next step, which is booting from USB though the BIOS menu. '''Booting from USB though the BIOS menu''' 1. Restart your computer<br> 2. Access the BIOS menu, typically by pressing ESC, Delete, or one of the 12 function keys (F1, F2, F3...)<br> 3. Enter the boot menu (Usually the key to enter the boot menu will be specified near the bottom of the screen)<br> 4. From the boot menu, select the USB drive<br> 5. If you have multiple ISO files on the same USB device, you will need to select which one you would like to boot into<br> 6. Selecting "boot in normal mode" will boot into the live environment, allowing you to try out, or install your Linux distribution<br> If you wish to install Linux, most distributions, such as Linux Mint, will have an application with a graphical interface to assist you in this process. '''Alternatives to Ventoy''' If Ventoy fails to create a bootable USB drive, or for any other reason, there are other tools available, such as:<br> - Rufus<br> - Belina Ether<br> - Fedora Media Writer<br> 2142a0559bbb6951fd7554888accf2f44ffce5b9 2304 2303 2025-05-10T17:06:20Z RatX2 149 wikitext text/x-wiki {{GuideWarning}} '''Setting up a bootable USB drive using Ventoy'''<br> Ventoy is an open source tool commonly used to create bootable USB drives for various linux installations. The main benefits to this tool is that it allows you to store multiple bootable ISO files on one USB drive. '''Download and installation'''<br> 1. The Ventoy application can be found at https://www.ventoy.net/en/index.html<br> 2. Extract the downloaded zip file<br> 3. Insert your USB drive<br> 4. Inside the Ventoy folder, run the Ventoy2Disk.exe file<br> 5. Now inside the application, select your desired USB drive<br> 6. Press the Install button<br> '''Warning''': Creating a bootable USB drive will delete all data stored on said USB. Backup your data and use with caution. After installing Ventoy you can copy a linux ISO file onto the USB drive, thus creating a bootable USB drive. After installation you may need to disable secure boot, depending on your chosen Linux distribution. Once the USB drive is made bootable, you can proceed to the next step, which is booting from USB though the BIOS menu. '''Booting from USB though the BIOS menu'''<br> 1. Restart your computer<br> 2. Access the BIOS menu, typically by pressing ESC, Delete, or one of the 12 function keys (F1, F2, F3...)<br> 3. Enter the boot menu (Usually the key to enter the boot menu will be specified near the bottom of the screen)<br> 4. From the boot menu, select the USB drive<br> 5. If you have multiple ISO files on the same USB device, you will need to select which one you would like to boot into<br> 6. Selecting "boot in normal mode" will boot into the live environment, allowing you to try out, or install your Linux distribution<br> If you wish to install Linux, most distributions, such as Linux Mint, will have an application with a graphical interface to assist you in this process. '''Alternatives to Ventoy''' If Ventoy fails to create a bootable USB drive, or for any other reason, there are other tools available, such as:<br> - Rufus<br> - Belina Ether<br> - Fedora Media Writer<br> f75c7b096e96dfe9aa19a1a3bea7aafeb608bbf8 2305 2304 2025-05-10T17:12:03Z RatX2 149 wikitext text/x-wiki {{GuideWarning}} ======Setting up a bootable USB drive using Ventoy====== Ventoy is an open source tool commonly used to create bootable USB drives for various linux installations. The main benefits to this tool is that it allows you to store multiple bootable ISO files on one USB drive. ====== Download and installation ====== 1. The Ventoy application can be found at https://www.ventoy.net/en/index.html<br> 2. Extract the downloaded zip file<br> 3. Insert your USB drive<br> 4. Inside the Ventoy folder, run the Ventoy2Disk.exe file<br> 5. Now inside the application, select your desired USB drive<br> 6. Press the Install button<br> '''Warning''': Creating a bootable USB drive will delete all data stored on said USB. Backup your data and use with caution. After installing Ventoy you can copy a linux ISO file onto the USB drive, thus creating a bootable USB drive. After installation you may need to disable secure boot, depending on your chosen Linux distribution. Once the USB drive is made bootable, you can proceed to the next step, which is booting from USB though the BIOS menu. ====== Booting from USB though the BIOS menu ====== 1. Restart your computer<br> 2. Access the BIOS menu, typically by pressing ESC, Delete, or one of the 12 function keys (F1, F2, F3...)<br> 3. Enter the boot menu (Usually the key to enter the boot menu will be specified near the bottom of the screen)<br> 4. From the boot menu, select the USB drive<br> 5. If you have multiple ISO files on the same USB device, you will need to select which one you would like to boot into<br> 6. Selecting "boot in normal mode" will boot into the live environment, allowing you to try out, or install your Linux distribution<br> If you wish to install Linux, most distributions, such as Linux Mint, will have an application with a graphical interface to assist you in this process. ====== Alternatives to Ventoy ====== If Ventoy fails to create a bootable USB drive, or for any other reason, there are other tools available, such as:<br> - Rufus<br> - Belina Ether<br> - Fedora Media Writer<br> 97d54736eec85ae061c52bcda8cc31c11871bb5f 2309 2305 2025-05-11T09:16:07Z Imnotpolar 112 minor spelling edit wikitext text/x-wiki {{GuideWarning}} ======Setting up a bootable USB drive using Ventoy====== Ventoy is an open source tool commonly used to create bootable USB drives for various linux installations. The main benefits to this tool is that it allows you to store multiple bootable ISO files on one USB drive. ====== Download and installation ====== 1. The Ventoy application can be found at https://www.ventoy.net/en/index.html<br> 2. Extract the downloaded zip file<br> 3. Insert your USB drive<br> 4. Inside the Ventoy folder, run the Ventoy2Disk.exe file<br> 5. Now inside the application, select your desired USB drive<br> 6. Press the Install button<br> '''Warning''': Creating a bootable USB drive will delete all data stored on said USB. Backup your data and use with caution. After installing Ventoy you can copy a linux ISO file onto the USB drive, thus creating a bootable USB drive. After installation you may need to disable secure boot, depending on your chosen Linux distribution. Once the USB drive is made bootable, you can proceed to the next step, which is booting from USB though the BIOS menu. ====== Booting from USB though the BIOS menu ====== 1. Restart your computer<br> 2. Access the BIOS menu, typically by pressing ESC, Delete, or one of the 12 function keys (F1, F2, F3...)<br> 3. Enter the boot menu (Usually the key to enter the boot menu will be specified near the bottom of the screen)<br> 4. From the boot menu, select the USB drive<br> 5. If you have multiple ISO files on the same USB device, you will need to select which one you would like to boot into<br> 6. Selecting "boot in normal mode" will boot into the live environment, allowing you to try out, or install your Linux distribution<br> If you wish to install Linux, most distributions, such as Linux Mint, will have an application with a graphical interface to assist you in this process. ====== Alternatives to Ventoy ====== If Ventoy fails to create a bootable USB drive, or for any other reason, there are other tools available, such as:<br> - Rufus (Windows only)<br> - balenaEtcher<br> - Fedora Media Writer<br> c3ccf6658aef756475bc364e7bd096df40c2bb36 6 635 2306 2025-05-10T18:19:02Z RatX2 149 wikitext text/x-wiki Ventoy's ISO selection menu 54f82a1aeb911ed33653c07d8ee950c17d9b525c 6 636 2307 2025-05-10T18:25:07Z RatX2 149 wikitext text/x-wiki Ventoy's installer b6ca4752e0fc750a898e58c92a2c98697b7be3e1 6 637 2308 2025-05-10T18:29:31Z RatX2 149 wikitext text/x-wiki Ventoy's Installer f53424b7dd6e24b6cef95d15c361bf6c836f652d 0 638 2311 2025-05-11T10:12:56Z Hikari 14 Added a basic page on ext4. wikitext text/x-wiki == Ext4 == Ext4 is an advanced level of the ext3 filesystem which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular distributions, however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. to format a partition <code>/dev/sdX</code> using <code>mkfs</code> do: <pre> mkfs -t ext4 /dev/sdX # or colloquially mkfs.ext4 /dev/sdX </pre> === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). <pre> tune2fs -o noatime /dev/sdX </pre> The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e HDDs) To set the commit interval to 60 seconds (from the default of 5) do: <pre> tune2fs -o commit=60 /dev/sdX </pre> ==== Changing the data mode ==== Ext4 provides three data modes<ref>https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> To change the data mode you can do: <pre> tune2fs -o data=... /dev/sdX </pre> ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost and can be disabled by doing: <pre> tune2fs -o barrier=0 /dev/sdX </pre> Only use this option if you know what you're doing. === Async journal commits and external journaling device === Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. To use /dev/sdb2 as a journal for /dev/sda1, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> If you want to convert a pre-existing ext4 filesystem to use an external journal, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>https://libre-consulting.com/posts/fs_ext4_external_journal/</ref>. <pre> tune2fs -o journal_async_commit /dev/sdX </pre> === Enabling fscrypt === fscrypt<ref>https://github.com/google/fscrypt</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. <pre> tune2fs -O encrypt /dev/sdX </pre> === Enabling fast_commit === fast_commit<ref>https://lwn.net/Articles/842385/</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by doing: <pre> tune2fs -O fast_commit /dev/sdX </pre> = References = 3489c3cd32f84154aa35ea2c258f04985d2dce60 2312 2311 2025-05-11T10:13:16Z Hikari 14 remove Ext4 header wikitext text/x-wiki Ext4 is an advanced level of the ext3 filesystem which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular distributions, however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. to format a partition <code>/dev/sdX</code> using <code>mkfs</code> do: <pre> mkfs -t ext4 /dev/sdX # or colloquially mkfs.ext4 /dev/sdX </pre> === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). <pre> tune2fs -o noatime /dev/sdX </pre> The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e HDDs) To set the commit interval to 60 seconds (from the default of 5) do: <pre> tune2fs -o commit=60 /dev/sdX </pre> ==== Changing the data mode ==== Ext4 provides three data modes<ref>https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> To change the data mode you can do: <pre> tune2fs -o data=... /dev/sdX </pre> ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost and can be disabled by doing: <pre> tune2fs -o barrier=0 /dev/sdX </pre> Only use this option if you know what you're doing. === Async journal commits and external journaling device === Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. To use /dev/sdb2 as a journal for /dev/sda1, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> If you want to convert a pre-existing ext4 filesystem to use an external journal, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>https://libre-consulting.com/posts/fs_ext4_external_journal/</ref>. <pre> tune2fs -o journal_async_commit /dev/sdX </pre> === Enabling fscrypt === fscrypt<ref>https://github.com/google/fscrypt</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. <pre> tune2fs -O encrypt /dev/sdX </pre> === Enabling fast_commit === fast_commit<ref>https://lwn.net/Articles/842385/</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by doing: <pre> tune2fs -O fast_commit /dev/sdX </pre> = References = b499199abb4d3eca59a97acb5a6ca2807cd94c8b 2313 2312 2025-05-11T10:14:00Z Hikari 14 Remove unnecessary References header. wikitext text/x-wiki Ext4 is an advanced level of the ext3 filesystem which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular distributions, however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. to format a partition <code>/dev/sdX</code> using <code>mkfs</code> do: <pre> mkfs -t ext4 /dev/sdX # or colloquially mkfs.ext4 /dev/sdX </pre> === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). <pre> tune2fs -o noatime /dev/sdX </pre> The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e HDDs) To set the commit interval to 60 seconds (from the default of 5) do: <pre> tune2fs -o commit=60 /dev/sdX </pre> ==== Changing the data mode ==== Ext4 provides three data modes<ref>https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> To change the data mode you can do: <pre> tune2fs -o data=... /dev/sdX </pre> ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost and can be disabled by doing: <pre> tune2fs -o barrier=0 /dev/sdX </pre> Only use this option if you know what you're doing. === Async journal commits and external journaling device === Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. To use /dev/sdb2 as a journal for /dev/sda1, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> If you want to convert a pre-existing ext4 filesystem to use an external journal, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>https://libre-consulting.com/posts/fs_ext4_external_journal/</ref>. <pre> tune2fs -o journal_async_commit /dev/sdX </pre> === Enabling fscrypt === fscrypt<ref>https://github.com/google/fscrypt</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. <pre> tune2fs -O encrypt /dev/sdX </pre> === Enabling fast_commit === fast_commit<ref>https://lwn.net/Articles/842385/</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by doing: <pre> tune2fs -O fast_commit /dev/sdX </pre> 12271530dce011c2634c97c9748660035207f9b5 2314 2313 2025-05-11T10:15:20Z Hikari 14 Remove an extra space. wikitext text/x-wiki Ext4 is an advanced level of the ext3 filesystem which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular distributions, however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. to format a partition <code>/dev/sdX</code> using <code>mkfs</code> do: <pre> mkfs -t ext4 /dev/sdX # or colloquially mkfs.ext4 /dev/sdX </pre> === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). <pre> tune2fs -o noatime /dev/sdX </pre> The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e HDDs) To set the commit interval to 60 seconds (from the default of 5) do: <pre> tune2fs -o commit=60 /dev/sdX </pre> ==== Changing the data mode ==== Ext4 provides three data modes<ref>https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> To change the data mode you can do: <pre> tune2fs -o data=... /dev/sdX </pre> ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost and can be disabled by doing: <pre> tune2fs -o barrier=0 /dev/sdX </pre> Only use this option if you know what you're doing. === Async journal commits and external journaling device === Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. To use /dev/sdb2 as a journal for /dev/sda1, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> If you want to convert a pre-existing ext4 filesystem to use an external journal, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>https://libre-consulting.com/posts/fs_ext4_external_journal/</ref>. <pre> tune2fs -o journal_async_commit /dev/sdX </pre> === Enabling fscrypt === fscrypt<ref>https://github.com/google/fscrypt</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. <pre> tune2fs -O encrypt /dev/sdX </pre> === Enabling fast_commit === fast_commit<ref>https://lwn.net/Articles/842385/</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by doing: <pre> tune2fs -O fast_commit /dev/sdX </pre> d41d27c1505e36ef904fb2aaddc309f30615a7f4 2315 2314 2025-05-11T10:16:35Z Hikari 14 Change the positioning of headers. wikitext text/x-wiki Ext4 is an advanced level of the ext3 filesystem which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular distributions, however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. to format a partition <code>/dev/sdX</code> using <code>mkfs</code> do: <pre> mkfs -t ext4 /dev/sdX # or colloquially mkfs.ext4 /dev/sdX </pre> === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). <pre> tune2fs -o noatime /dev/sdX </pre> The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e HDDs) To set the commit interval to 60 seconds (from the default of 5) do: <pre> tune2fs -o commit=60 /dev/sdX </pre> ==== Changing the data mode ==== Ext4 provides three data modes<ref>https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> To change the data mode you can do: <pre> tune2fs -o data=... /dev/sdX </pre> ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost and can be disabled by doing: <pre> tune2fs -o barrier=0 /dev/sdX </pre> Only use this option if you know what you're doing. ==== Async journal commits and external journaling device ==== Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. To use /dev/sdb2 as a journal for /dev/sda1, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> If you want to convert a pre-existing ext4 filesystem to use an external journal, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>https://libre-consulting.com/posts/fs_ext4_external_journal/</ref>. <pre> tune2fs -o journal_async_commit /dev/sdX </pre> ==== Enabling fscrypt support ==== fscrypt<ref>https://github.com/google/fscrypt</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. <pre> tune2fs -O encrypt /dev/sdX </pre> ==== Enabling fast_commit support ==== fast_commit<ref>https://lwn.net/Articles/842385/</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by doing: <pre> tune2fs -O fast_commit /dev/sdX </pre> 3a5c1ff988487621831e55f1aacaf38e685adb26 2316 2315 2025-05-11T10:47:05Z Hikari 14 use proper citations. wikitext text/x-wiki Ext4 is an advanced level of the ext3 filesystem which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular distributions, however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. to format a partition <code>/dev/sdX</code> using <code>mkfs</code> do: <pre> mkfs -t ext4 /dev/sdX # or colloquially mkfs.ext4 /dev/sdX </pre> === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). <pre> tune2fs -o noatime /dev/sdX </pre> The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e HDDs) To set the commit interval to 60 seconds (from the default of 5) do: <pre> tune2fs -o commit=60 /dev/sdX </pre> ==== Changing the data mode ==== Ext4 provides three data modes{{Cite|title=Linux's ext4 documentation.|url=https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode|author=Linux Foundation.|year=2018}}. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> To change the data mode you can do: <pre> tune2fs -o data=... /dev/sdX </pre> ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost and can be disabled by doing: <pre> tune2fs -o barrier=0 /dev/sdX </pre> Only use this option if you know what you're doing. ==== Async journal commits and external journaling device ==== Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. To use /dev/sdb2 as a journal for /dev/sda1, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> If you want to convert a pre-existing ext4 filesystem to use an external journal, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup{{Cite|title=Ext4 external journal benchmarks.|url=https://libre-consulting.com/posts/fs_ext4_external_journal/|author=Libre Consulting|year=2019}} <pre> tune2fs -o journal_async_commit /dev/sdX </pre> ==== Enabling fscrypt support ==== fscrypt{{Cite|title=Fscrypt.|url=https://github.com/google/fscrypt|author=Google|year=2017}} is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. <pre> tune2fs -O encrypt /dev/sdX </pre> ==== Enabling fast_commit support ==== fast_commit{{Cite|title=LWN's article on fast_commit.|url=https://lwn.net/Articles/842385/|author=LWN|year=2021}} is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by doing: <pre> tune2fs -O fast_commit /dev/sdX </pre> <references /> a0dbce3b5872735438509386c5c9427e78c25aa9 2319 2316 2025-05-11T11:03:26Z Hikari 14 Separate out commands into a guide page. wikitext text/x-wiki Ext4 is an advanced level of the ext3 [[filesystems]] which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular [[Linux Distributions|distributions]], however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. Information on how to do it can be found in [[Guides:Ext4]]. === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e HDDs) ==== Changing the data mode ==== Ext4 provides three data modes<ref>[https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode Linux's ext4 documentation ]</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost. Only disable this option if you know what you're doing. ==== Async journal commits and external journaling device ==== Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>[https://libre-consulting.com/posts/fs_ext4_external_journal/ ext4 external journal benchmarks.]</ref> ==== Enabling fscrypt support ==== fscrypt<ref>[https://github.com/google/fscrypt FSCrypt]</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. ==== Enabling fast_commit support ==== fast_commit <ref>[https://lwn.net/Articles/842385/ LWN's article on fast_commit.]</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by doing: <references /> 36123bcfa0d0d5377528ed4a826b901b3869a725 2330 2319 2025-05-11T11:17:31Z Hikari 14 Clarify what options are supposed to be used. wikitext text/x-wiki Ext4 is an advanced level of the ext3 [[filesystems]] which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular [[Linux Distributions|distributions]], however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. Information on how to do it can be found in [[Guides:Ext4]]. === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e HDDs) ==== Changing the data mode ==== Ext4 provides three data modes<ref>[https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode Linux's ext4 documentation ]</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> You can change the data mode by setting the <code>data=...</code> mount option. ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost. The mount option <code>barrier=0</code> disables write barriers. Only disable this option if you know what you're doing. ==== Async journal commits and external journaling device ==== Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>[https://libre-consulting.com/posts/fs_ext4_external_journal/ ext4 external journal benchmarks.]</ref> ==== Enabling fscrypt support ==== fscrypt<ref>[https://github.com/google/fscrypt FSCrypt]</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. ==== Enabling fast_commit support ==== fast_commit <ref>[https://lwn.net/Articles/842385/ LWN's article on fast_commit.]</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by setting the <code>fast_commit</code> feature flag. <references /> e8d243b042e1d66e85a4a664d2fe5e05693df98f 0 169 2320 2068 2025-05-11T11:04:34Z Ivanovics 150 add zypper to the list of package managers wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] [[Category:Terminology]] 88f96a3617b8cc927423de1052c94117e536fecf 3000 639 2323 2025-05-11T11:11:20Z Hikari 14 Added a small guide page. wikitext text/x-wiki {{Guide Warning}} == Formatting a partition to ext4 == Assuming the partition you want to format is called /dev/sdX, do: <pre> mkfs -t ext4 /dev/sdX # or mkfs.ext4 /dev/sdX </pre> The e2fsprogs package must be installed. == Setting mount options == You can set mount options for ext4 either by modifying <code>/etc/fstab</code> or <code>tune2fs</code><ref>[https://linux.die.net/man/8/tune2fs tune2fs]</ref> For example, to enable <code>noatime</code> on your filesystem, do: <pre> tune2fs -o noatime /dev/sdX </pre> == Using an external journal == Ext4 allows you to use an external journaling device paired with a partition that actually stores your data. To create a **new** partition with an external journal at /dev/sdb2, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> To convert a pre-existing filesystem, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> == Feature flags == Ext4 has tons of feature flags that can be enabled using the <code>tune2fs</code> utility, a list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. To enable a feature flag, do: <pre> tune2fs -O flag /dev/sdX </pre> Some common feature flags used often are <code>encrypt</code> and <code>fast_commit</code> <references /> f33e6fcc3f99141fcf3571d8c7e65516d763d928 2326 2323 2025-05-11T11:15:19Z Hikari 14 Add a period wikitext text/x-wiki {{Guide Warning}} == Formatting a partition to ext4 == Assuming the partition you want to format is called /dev/sdX, do: <pre> mkfs -t ext4 /dev/sdX # or mkfs.ext4 /dev/sdX </pre> The e2fsprogs package must be installed. == Setting mount options == You can set mount options for ext4 either by modifying <code>/etc/fstab</code> or <code>tune2fs</code><ref>[https://linux.die.net/man/8/tune2fs tune2fs]</ref> For example, to enable <code>noatime</code> on your filesystem, do: <pre> tune2fs -o noatime /dev/sdX </pre> == Using an external journal == Ext4 allows you to use an external journaling device paired with a partition that actually stores your data. To create a **new** partition with an external journal at /dev/sdb2, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> To convert a pre-existing filesystem, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> == Feature flags == Ext4 has tons of feature flags that can be enabled using the <code>tune2fs</code> utility, a list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. To enable a feature flag, do: <pre> tune2fs -O flag /dev/sdX </pre> Some common feature flags used often are <code>encrypt</code> and <code>fast_commit</code>. <references /> 1177a51ad3e6cf9250f68a4850ae37907b33ec8c 10 631 2332 2331 2025-05-11T11:19:35Z Atmois 13 Format fix? wikitext text/x-wiki <includeonly> {{#tag:ref|{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}} (Accessed: {{#time:F j, Y}})}} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 4cb2cd61f3be07c7373a653e8cc1de7a39d3d54c 2333 2332 2025-05-11T11:20:24Z Atmois 13 format fix wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}} (Accessed: {{#time:F j, Y}})}} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 1b2371c66f8faf0b669b07ead202feb6b422a7c7 2334 2333 2025-05-11T11:21:27Z Atmois 13 fix? wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}} |, {{{author}}}}}{{#if: {{{year|}}} |, {{{year}}}} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> be8801abb76b82e000b2362373e4805107980b21 2335 2334 2025-05-11T11:23:11Z Atmois 13 revert wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}'' }} {{#if: {{{author|}}} |, {{{author|Anon.}}} }} {{#if: {{{year|}}} |, {{{year}}} }} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 20a99020832b55635d89a687063412f29db4edce 2336 2335 2025-05-11T11:24:33Z Atmois 13 try fix again wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}''}} {{#if: {{{author|}}} |, {{{author|Anon.}}}}} {{#if: {{{year|}}} |, {{{year}}} }} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> e9a93174b1cb1098b37a5a5edd632e941242282e 2337 2336 2025-05-11T11:27:19Z Atmois 13 format fixed finally? wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}} | ''[{{{url}}} {{{title}}}]'' | ''{{{title|Untitled Source}}}'' }} {{#if: {{{author|}}} |, {{{author|Anon.}}} }} {{#if: {{{year|}}} |, {{{year}}} }} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 71cafbd6e13f5e29826ba88fae0915d82b3d78c2 2338 2337 2025-05-11T11:27:54Z Atmois 13 now? wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}} |''[{{{url}}} {{{title}}}]'' |''{{{title|Untitled Source}}}'' }} {{#if: {{{author|}}} |, {{{author|Anon.}}} }} {{#if: {{{year|}}} |, {{{year}}} }} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> fd697cfe4ad85c1708016d7e74b288ee8c4da498 2339 2338 2025-05-11T11:28:47Z Atmois 13 Format? wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}} {{#if: {{{author|}}}|, {{{author|Anon.}}}}} {{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> a466051c2d884eb6066af205463e8121506ae5c2 2340 2339 2025-05-11T11:29:24Z Atmois 13 format? wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the material", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 311d36952accb2c3a27c1ba8e6a74e8dd074c358 2342 2340 2025-05-11T11:34:52Z Atmois 13 tidy up templatedata wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page", "format": "inline" } </templatedata> </noinclude> 5148be9e31290810bfac7f2050af4922a046cdfa 2343 2342 2025-05-11T11:36:13Z Atmois 13 fix alignement wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata> </noinclude> 04aa25daf3a35a27fb29a96af8b303dfca07d9a9 2344 2343 2025-05-11T11:38:13Z Atmois 13 test wikitext text/x-wiki <includeonly> {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata> </noinclude> db477d69cd7481c07b14fd370eebcc517a7cc722 2345 2344 2025-05-11T11:39:08Z Atmois 13 add ref tag wikitext text/x-wiki <includeonly><ref> {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) }} </ref></includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata> </noinclude> a8f4ee6cbb5071ca1f94fa4b8beb13b635ae9d05 2346 2345 2025-05-11T11:39:51Z Atmois 13 tidfy wikitext text/x-wiki <includeonly><ref> {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) </ref></includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata> </noinclude> fe8408e294bac74413c0131d74805a023bf87116 2347 2346 2025-05-11T11:40:40Z Atmois 13 revert wikitext text/x-wiki <includeonly><ref> {{#tag:ref| {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) }} </ref></includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata> </noinclude> 01e87e8e48cf4b2c12329b505525dfce38fdc0b9 2348 2347 2025-05-11T11:40:55Z Atmois 13 revert wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata> </noinclude> 04aa25daf3a35a27fb29a96af8b303dfca07d9a9 2349 2348 2025-05-11T11:41:49Z Atmois 13 fix? wikitext text/x-wiki <includeonly> {{#tag:ref| {{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata> </noinclude> 606d465cd8977a988c268eec4b4e9e2848840908 2350 2349 2025-05-11T11:44:57Z Atmois 13 fix wikitext text/x-wiki <includeonly> {{#tag:ref|{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}}) }} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata> </noinclude> 9615b021882fe1a4149d5dffaa0eb8a307d3022e 2351 2350 2025-05-11T11:45:45Z Atmois 13 fix? wikitext text/x-wiki <includeonly> {{#tag:ref|{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}})}} </includeonly> <noinclude> <templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata> </noinclude> f73866216e6f4a4db100cd9ba81e6d20119b6438 2352 2351 2025-05-11T11:46:21Z Atmois 13 fix? wikitext text/x-wiki <includeonly> {{#tag:ref|{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}})}} </includeonly><noinclude><templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata></noinclude> 41cb55617c57359b4e9c936e563a5d7d4faa5a77 2353 2352 2025-05-11T11:47:50Z Atmois 13 format wikitext text/x-wiki <includeonly> {{#tag:ref|{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}})}} </includeonly><noinclude><templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata></noinclude> 083c186387ff7d9428f7f10826f947a17773ba25 4 327 2341 2317 2025-05-11T11:29:36Z Atmois 13 test wikitext text/x-wiki Test{{Cite|url=https://google.com|title=Google's Amazing Wesbite|author=John Doe|year=2025}} <references /> 127d7a023e0283f03f76cc2967b3c69d72aafd5d 2355 2341 2025-05-11T11:52:28Z Atmois 13 test wikitext text/x-wiki Test{{Cite|url=https://google.com|title=Google's Amazing Wesbite|author=John Doe|year=2025}} {{Cite|url=g|title=g|author=g|year=g}}<references /> a5310fb12a783ac99a8df1cf307a07098241683e 2374 2355 2025-06-03T17:30:04Z Atmois 13 wikitext text/x-wiki <gallery mode="packed" widths="200" heights="200"> File:Budgie desktop raven panel.png|Budgie File:LinuxMint22-Wilma-English.png|Cinnamon File:GNOME 46.png|GNOME File:MATEDesktop.png|MATE File:Openbox 3.4.10 default.png|Openbox File:KDE Plasma 5.26 screenshot.png|KDE Plasma File:Trinity R.14.1.3 screenshot.png|Trinity File:XFCE-4.18-Desktop.png|XFCE </gallery> d2ae67d24d62cfed682ef2ffd2d0dd91652cf847 2375 2374 2025-06-03T17:33:02Z Atmois 13 wikitext text/x-wiki <gallery widths="200" heights="200"> File:Budgie desktop raven panel.png|link=Budgie|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 46.png|link=GNOME|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE </gallery> 374f0cf77d31023746efec74124bd41dbc059d9a 2376 2375 2025-06-03T17:33:36Z Atmois 13 wikitext text/x-wiki <gallery mode="packed" widths="200" heights="200"> File:Budgie desktop raven panel.png|link=Budgie|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 46.png|link=GNOME|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE </gallery> 71e40305418b91fd1cdc51d1c937b123732ff3fa 4 340 2354 2296 2025-05-11T11:52:23Z Atmois 13 Add info wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Guidelines#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. ====== <u>Accessibility</u> ====== We aim to make the wiki accessible to users of all ability levels, be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use. Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. A citation is composed of two components: an inline superscript next to the relevant section of text, <ref>Sample Reference</ref>, you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] cd105cd3bea03e388930fcb38c497b4045086e99 0 313 2356 2028 2025-05-13T18:08:55Z Ivanovics 150 Improve article, include X-apps and starting cinnamon wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] {{Needs Citations}} == Overview == [https://github.com/linuxmint/cinnamon Cinnamon] is a desktop environment maintained by the [https://www.linuxmint.com/ Linux Mint] team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === A "Spice" is Cinnamon's name for an add-on applet, desklet, theme, widget, and more. They can be found at the [https://cinnamon-spices.linuxmint.com/ Cinnamon Spices repository website]. == Cinnamon applications == Cinnamon uses the X-app suite, which are a set of apps forked from GNOME and changed to work across XFCE, Cinnamon and MATE. {| class="wikitable" |+The list of apps are the following: !Application !GNOME !X-apps equivalent |- |Text editor |Gedit |xed |- |Image viewer |Eye of GNOME (EoG) |xviewer |- |Image organizer |gthumb |pix |- |Media player |Totem |xplayer |- |Document editor |Atril |xreader |} == Starting Cinnamon == There are two main methods of starting Cinnamon: * Selecting "Cinnamon" from your preferred [[Display Manager]] ** If your session crashes or has graphical artifacts you should select "Cinnamon (software rendering) instead, which disables 3D acceleration * Modifying your [[Xinitrc]] to include <code>exec cinnamon-session</code> [[Category:Desktop Environments]] 2de86ef44ed4ac4c0f1a850a0cfe4a027a3d4225 2359 2356 2025-05-27T07:52:33Z Matty 40 /* Panel */ wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] {{Needs Citations}} == Overview == [https://github.com/linuxmint/cinnamon Cinnamon] is a desktop environment maintained by the [https://www.linuxmint.com/ Linux Mint] team. Forked from GNOME Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in JavaScript, with core libraries being written in C. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === A "Spice" is Cinnamon's name for an add-on applet, desklet, theme, widget, and more. They can be found at the [https://cinnamon-spices.linuxmint.com/ Cinnamon Spices repository website]. == Cinnamon applications == Cinnamon uses the X-app suite, which are a set of apps forked from GNOME and changed to work across XFCE, Cinnamon and MATE. {| class="wikitable" |+The list of apps are the following: !Application !GNOME !X-apps equivalent |- |Text editor |Gedit |xed |- |Image viewer |Eye of GNOME (EoG) |xviewer |- |Image organizer |gthumb |pix |- |Media player |Totem |xplayer |- |Document editor |Atril |xreader |} == Starting Cinnamon == There are two main methods of starting Cinnamon: * Selecting "Cinnamon" from your preferred [[Display Manager]] ** If your session crashes or has graphical artifacts you should select "Cinnamon (software rendering) instead, which disables 3D acceleration * Modifying your [[Xinitrc]] to include <code>exec cinnamon-session</code> [[Category:Desktop Environments]] 4ac1015df0974005a4a8f60f31a5c2c2dc6c2a66 0 257 2360 2144 2025-05-27T12:40:45Z Treemore 153 fixing grammatical errors wikitext text/x-wiki {{Needs Citations}} {{Cleanup|Installation instructions should be separated onto its own page in the Guides namespace}} {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window managers that aim for pure eye candy with nice animations, smooth looks and its own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) === Installation === This section will change overtime, as such, you should follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. [[Category:Wayland_Compositors]] 607dcb5c4b0272b7ff98dde9a8c5644b5545448d 0 169 2361 2320 2025-05-30T02:22:18Z Wreed 154 Added entry for XBPS from Void Linux wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. [[Category:Terminology]] e312ecb764c89d9fe991728bf1aef22f83f49d64 2 640 2362 2025-06-01T00:23:50Z Shokisenshi 156 Created page with "hello world" wikitext text/x-wiki hello world 2aae6c35c94fcfb415dbe95f408b9ce91ee846ed 0 428 2363 2059 2025-06-01T17:45:29Z Stefi 157 added the section about changing the pager wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} Man or Man pages is a [[command-line]] utility available on [[UNIX]] and [[UNIX-like]] [[operating systems]] that provides [[documentation]] for [[Program|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format]] and [[games]]. The Man pages are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a Man page the user can enter the following into their [[terminal]]: man <command_name> <ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> For example to read the Man page on [[pacman]] you would enter the following: man pacman == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardize layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == '''Changing the Pager''' == The program that displays the manpage is stored in the `MANPAGER` or `PAGER` environment variable. By default, it uses `less`. Alternatively, the `-P` or `--pager` option can be used. <ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using `export PAGER="program-to-use"` or added to the `.bashrc` or `.zshrc` file for persistence. For example, using Neovim as the pager would be `export PAGER="nvim +Man!"`, `export PAGER="nano -"` to use Nano, and `export PAGER="less"` to revert it to less. For Fish shell, use `set -x PAGER program-to-use` to set it for the current session, and `set -Ux PAGER program-to-use` to set it globally. <ref>https://fishshell.com/docs/current/faq.html</ref> <references /> a7b8c9bae9aba99f2f89ab8f8486c5071f3187cc 0 641 2364 2025-06-02T03:18:29Z 0Stormy 158 Created base page for Openbox wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Maintenance |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/, openbox.org] }} [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable window manager for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>https://openbox.org/</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>https://openbox.org/obconf</ref> === Usage === While Openbox is perfectly usable on it's own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>https://slitaz.org/en/about/</ref><ref>https://crunchbang.org/about/</ref><references /> [[Category:Desktop Environments]] 53444b6bc0edc71bda45e3b79988cfe93b1188b5 2370 2364 2025-06-03T01:36:28Z 0Stormy 158 /* Usage */ wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Maintenance |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/, openbox.org] }} [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable window manager for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>https://openbox.org/</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>https://openbox.org/obconf</ref> === Usage === While Openbox is perfectly usable on its own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>https://slitaz.org/en/about/</ref><ref>https://crunchbang.org/about/</ref><references /> [[Category:Desktop Environments]] 48527b61c6810bc29f9dd7ca969de2d9e623c921 1 642 2365 2025-06-02T03:20:28Z 0Stormy 158 /* Keeping in Desktop Environments category */ new section wikitext text/x-wiki == Keeping in Desktop Environments category == I put my page on Openbox under desktop environments for now, should I (or someone else) make a category for window managers? [[User:0Stormy|0Stormy]] ([[User talk:0Stormy|talk]]) 03:20, 2 June 2025 (UTC) d035dbf0b606d888eadf6c21352a46195e11984f 0 198 2366 2273 2025-06-02T14:34:18Z Wreed 154 Paraphrased from the official website to reflect their description wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments||Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|Repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] f4d39b767eae907ce7006e43c90332cefd326561 2379 2366 2025-06-05T10:09:55Z Madonuko 140 add ublue and um linux wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Universal Blue]] |A community managed set of immutable distributions based on Fedora, including [[Aurora]], [[Bazzite]], [[Bluefin]], etc. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] 36187c2087320e3e1b913e9d1e725f833152d958 2380 2379 2025-06-05T11:44:43Z Hog 161 /* Other Independent Distributions */ wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Universal Blue]] |A community managed set of immutable distributions based on Fedora, including [[Aurora]], [[Bazzite]], [[Bluefin]], etc. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] 686e1c74da75d755e8f4d96065fb5499dd72c272 2381 2380 2025-06-05T11:45:18Z Hog 161 /* Other Independent Distributions */ punctuation wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Universal Blue]] |A community managed set of immutable distributions based on Fedora, including [[Aurora]], [[Bazzite]], [[Bluefin]], etc. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] 50e9783a653e874d4b50d527f64ef1898a2f40ec 0 643 2367 2025-06-02T15:50:07Z Wreed 154 Initial creating of XBPS wiki page, providing general description, a listing of tools and usage examples for common operations wikitext text/x-wiki {{SoftwareInfobox |title = XBPS |releasestatus = Maintained |lastrelease = 0.59.2, 2023-08-18 |firstrelease = 0.1beta1, 2009-08-17 |languages = [[C]] |developers = [[Void Linux]] |website = [https://github.com/void-linux/xbps github.com/void-linux/xbps] }} == Intro == The ''X Binary Package System'' (XBPS) is developed by the maintainers of [[Void Linux]] and is the package manager for their distribution. It was built from scratch, with the goals of speed, ease of use while being feature rich and portable. It is fully compatible with POSIX, SUSv2 and C99 standards<ref>https://github.com/void-linux/xbps#xbps</ref>, and is released under the BSD 2-Clause (Simplified) license ([https://spdx.org/licenses/BSD-2-Clause.html SPDX: BSD-2-Clause]). == Tools == XBPS is comprised of a number of utilities that provide different functionality, the ''core'' utility programs are as follows (not a complete list): {| class="wikitable" !<u>Name</u> !<u>Function</u> |- |xbps-create |Creating binary packages |- |xbps-dgraph |Generating graphs for tools like [https://graphviz.org<nowiki> GraphViz]</nowiki> |- |xbps-install |Installing and updating packages |- |xbps-pkgdb |Reporting and fixing issues with the package database |- |xbps-query |Querying package and repository information |- |xbps-reconfigure |Configuration of installed package (e.g., the system C library or Linux kernel) |- |xbps-remove |Removing packages |- |xbps-rindex |Handling local package repositories |} == Usage<ref>https://github.com/void-linux/xbps?tab=readme-ov-file#examples</ref> == {| class="wikitable" !<u>Command</u> !<u>Description</u> |- |<code>xbps-install -Su</code> |Synchronize with repositories and apply all available updates |- |<code>xbps-query -Rs <name></code> |Search through repository packages using the given name |- |<code>xbps-install <package></code> |Install a package by name |- |<code>xbps-remove -R <package></code> |Remove a package by name; along with it's dependent packages which are no longer needed by the system |- |<code>xbps-query -Rf <package></code> |List files owned by a package |- |<code>xbps-query -Ro /usr/bin/ls</code> |Find the package(s) that own/provide a file path, (e.g., the 'ls' command) |- |<code>xbps-reconfigure -f glibc-locales</code> |Regenerate your locale(s) when using a GLIBC based system<ref>https://man.voidlinux.org/xbps-reconfigure</ref> |} a9a11ccbc409239556059203bfda9769beada432 2369 2367 2025-06-02T16:08:44Z Wreed 154 adjust graphviz link to not show brackets inline wikitext text/x-wiki {{SoftwareInfobox |title = XBPS |releasestatus = Maintained |lastrelease = 0.59.2, 2023-08-18 |firstrelease = 0.1beta1, 2009-08-17 |languages = [[C]] |developers = [[Void Linux]] |website = [https://github.com/void-linux/xbps github.com/void-linux/xbps] }} == Intro == The ''X Binary Package System'' (XBPS) is developed by the maintainers of [[Void Linux]] and is the package manager for their distribution. It was built from scratch, with the goals of speed, ease of use while being feature rich and portable. It is fully compatible with POSIX, SUSv2 and C99 standards<ref>https://github.com/void-linux/xbps#xbps</ref>, and is released under the BSD 2-Clause (Simplified) license ([https://spdx.org/licenses/BSD-2-Clause.html SPDX: BSD-2-Clause]). == Tools == XBPS is comprised of a number of utilities that provide different functionality, the ''core'' utility programs are as follows (not a complete list): {| class="wikitable" !<u>Name</u> !<u>Function</u> |- |xbps-create |Creating binary packages |- |xbps-dgraph |Generating graphs for tools like [https://graphviz.org GraphViz] |- |xbps-install |Installing and updating packages |- |xbps-pkgdb |Reporting and fixing issues with the package database |- |xbps-query |Querying package and repository information |- |xbps-reconfigure |Configuration of installed package (e.g., the system C library or Linux kernel) |- |xbps-remove |Removing packages |- |xbps-rindex |Handling local package repositories |} == Usage<ref>https://github.com/void-linux/xbps?tab=readme-ov-file#examples</ref> == {| class="wikitable" !<u>Command</u> !<u>Description</u> |- |<code>xbps-install -Su</code> |Synchronize with repositories and apply all available updates |- |<code>xbps-query -Rs <name></code> |Search through repository packages using the given name |- |<code>xbps-install <package></code> |Install a package by name |- |<code>xbps-remove -R <package></code> |Remove a package by name; along with it's dependent packages which are no longer needed by the system |- |<code>xbps-query -Rf <package></code> |List files owned by a package |- |<code>xbps-query -Ro /usr/bin/ls</code> |Find the package(s) that own/provide a file path, (e.g., the 'ls' command) |- |<code>xbps-reconfigure -f glibc-locales</code> |Regenerate your locale(s) when using a GLIBC based system<ref>https://man.voidlinux.org/xbps-reconfigure</ref> |} 2096bb33497463faba6ef4913d39d43d9a8d0218 0 317 2368 2087 2025-06-02T16:06:58Z Wreed 154 Adding internal wiki links for newly added XBPS page, minor rephrasing of key features and addition of internal wiki links to mentions of Glibc and musl wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution made from scratch. Created in 2008 by Juan Romero Pardines, Void distinguishes itself through unique design choices including the runit init system, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and [[Musl]] variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses runit as its init system, offering: * Simple service management * Clean daemon supervision * Fast boot times {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] [[Category:Linux Distributions]] 4069b160d87407267accda6c054b725f65be988c 0 622 2371 2247 2025-06-03T07:56:38Z Delta0 159 Added table of Screenshots wikitext text/x-wiki This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} {| class="wikitable" |+ |'''Desktop Environment''' |Description |ExampleExample |- |[[Budgie]] | |[[File:Budgie desktop raven panel.png|center|thumb|600x600px]] |- |[[Cinnamon]] | |[[File:LinuxMint22-Wilma-English.png|thumb|600x600px]] |- |[[GNOME]] | |[[File:GNOME 46.png|thumb|600x600px]] |- |[[MATE]] | |[[File:MATEDesktop.png|thumb|600x600px]] |- |[[Openbox]] | |[[File:Openbox 3.4.10 default.png|thumb|600x600px]] |- |[[Plasma]] | |[[File:KDE Plasma 5.26 screenshot.png|thumb|600x600px]] |- |[[Trinity Desktop Environment]] | |[[File:Trinity R.14.1.3 screenshot.png|thumb|600x600px]] |- ![[XFCE]] ! ![[File:XFCE-4.18-Desktop.png|thumb|600x600px]] |} e923a27c19200b1d0bb5be9c44f5bd2580e17550 2372 2371 2025-06-03T08:10:02Z Delta0 159 Added alternative large desktop listing wikitext text/x-wiki This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} [[File:Budgie desktop raven panel.png|center|thumb|1024x1024px|Budgie|link=Budgie]] [[File:LinuxMint22-Wilma-English.png|center|thumb|1024x1024px|Cinnamon|link=Cinnamon]] [[File:GNOME 46.png|center|thumb|1024x1024px|GNOME|link=GNOME]] [[File:MATEDesktop.png|center|thumb|1024x1024px|MATE|link=MATE]] [[File:Openbox 3.4.10 default.png|center|thumb|1024x1024px|Openbox|link=Openbox]] [[File:KDE Plasma 5.26 screenshot.png|center|thumb|1024x1024px|KDE Plasma|link=Plasma]] [[File:Trinity R.14.1.3 screenshot.png|center|thumb|1024x1024px|Trinity|link=Trinity_Desktop_Environment]] [[File:XFCE-4.18-Desktop.png|center|thumb|1024x1024px|XFCE|link=XFCE]] {| class="wikitable" |+ |'''Desktop Environment''' |Description |Example |- |[[Budgie]] | |[[File:Budgie desktop raven panel.png|center|thumb|600x600px]] |- |[[Cinnamon]] | |[[File:LinuxMint22-Wilma-English.png|thumb|600x600px]] |- |[[GNOME]] | |[[File:GNOME 46.png|thumb|600x600px]] |- |[[MATE]] | |[[File:MATEDesktop.png|thumb|600x600px]] |- |[[Openbox]] | |[[File:Openbox 3.4.10 default.png|thumb|600x600px]] |- |[[Plasma]] | |[[File:KDE Plasma 5.26 screenshot.png|thumb|600x600px]] |- |[[Trinity Desktop Environment]] | |[[File:Trinity R.14.1.3 screenshot.png|thumb|600x600px]] |- ![[XFCE]] ! ![[File:XFCE-4.18-Desktop.png|thumb|600x600px]] |} 594617a247167961d858248976989a524dd90dae 2377 2372 2025-06-03T17:34:16Z Atmois 13 Change to using a packed gallary for images wikitext text/x-wiki This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} <gallery mode="packed" widths="200" heights="200"> File:Budgie desktop raven panel.png|link=Budgie|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 46.png|link=GNOME|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE </gallery> {| class="wikitable" |+ |'''Desktop Environment''' |Description |Example |- |[[Budgie]] | |[[File:Budgie desktop raven panel.png|center|thumb|600x600px]] |- |[[Cinnamon]] | |[[File:LinuxMint22-Wilma-English.png|thumb|600x600px]] |- |[[GNOME]] | |[[File:GNOME 46.png|thumb|600x600px]] |- |[[MATE]] | |[[File:MATEDesktop.png|thumb|600x600px]] |- |[[Openbox]] | |[[File:Openbox 3.4.10 default.png|thumb|600x600px]] |- |[[Plasma]] | |[[File:KDE Plasma 5.26 screenshot.png|thumb|600x600px]] |- |[[Trinity Desktop Environment]] | |[[File:Trinity R.14.1.3 screenshot.png|thumb|600x600px]] |- ![[XFCE]] ! ![[File:XFCE-4.18-Desktop.png|thumb|600x600px]] |} 8efece4946468e0542280955ce0d70945bab1840 2378 2377 2025-06-03T17:38:50Z Delta0 159 Removed old table. Moved DPL to bottom. wikitext text/x-wiki <gallery mode="packed" widths="200" heights="200"> File:Budgie desktop raven panel.png|link=Budgie|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 46.png|link=GNOME|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE </gallery> This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} e89a9a6ea7fb307048af53e0fffb1ed0ed93cb7a 2 644 2373 2025-06-03T16:32:18Z Madonuko 140 Created page with "V.P. DevOps at [https://fyralabs.com Fyra Labs] and [[Ultramarine Linux]]. Lead maintainer of [[Terra]]. === Pages I maintain === - [[Guides:Input method]]" wikitext text/x-wiki V.P. DevOps at [https://fyralabs.com Fyra Labs] and [[Ultramarine Linux]]. Lead maintainer of [[Terra]]. === Pages I maintain === - [[Guides:Input method]] 514bcd2048841f3e9621465b2d49d9806486c782 0 164 2382 2035 2025-06-05T11:49:10Z Hog 161 /* Tools */ Added Balena-Etcher wikitext text/x-wiki {{Work In Progress}} == Introduction == The [[Linux]] community is abundant with awesome projects and various other guides worth checking out, Here's some great ones that we have found - keep in mind that, while these guides are very useful, they are not fully exhaustive. More than likely you discover new software every day! * Privacy is not an end goal, but a consistent journey that needs to be taken very seriously. ''Always'' seek help when in doubt and ensure you take everything with a grain of salt. ''Do not just blindly follow guides but use your own intuition!'' == Guides == * https://www.privacyguides.org/ - An essential guide to learning not just ''how'' to begin your privacy journey online but offers a comprehensive explanation of abstract privacy concepts that is simple to understand and by extension ''is assuredly not easy or quick -'' read with an open mind! ** https://awesome-privacy.xyz - More of a guide to tools you may find yourself wanting to use to enhance privacy, rather than an explanation. The next step from Privacy Guides, essentially. ** https://www.privacytools.io/ - Similar to Awesome Privacy, and offers a wide range of tools. This specific website is recommended very frequently. * https://brainfucksec.github.io/firefox-hardening-guide - A guide to "de-Mozilla" and security-harden Firefox. Assess whether or not this is a good option for you - ''similar to privacy, it is not an easy process.'' * https://rentry.co/fmhy-guides - General, yet extremely useful and even nuanced guides that you may find yourself needing for something very specific and hard to find on the internet. * https://github.com/luong-komorebi/Awesome-Linux-Software - Very extensive guide of not solely Linux software but mostly open-source software that has many use cases in mind. [[Choosing A Linux Distribution|May be helpful in picking a flavor of Linux for your specific use cases.]] == Wikis == * https://wiki.archlinux.org/ for Arch Linux * https://wiki.gentoo.org/ for Gentoo * https://wiki.debian.org/ for Debian * https://fedoraproject.org/wiki/Fedora_Project_Wiki for Fedora * https://wiki.ubuntu.com for Ubuntu == Tools == * https://christitus.com/windows-tool/ - Used for debloating and removing telemetry from Windows. * https://alternativeto.net - A tool to find alternatives to popular software, both open-source and proprietary. * https://etcher.balena.io/ - An open-source tool to flash operating systems to an USB drive. [[Category:Guides]] 5fc6a703374ab5ffb79174cb8b29ee07cadc1b75 0 645 2383 2025-06-05T11:53:53Z Hog 161 Made page and brief summary wikitext text/x-wiki A driver is a computer program that controls or operates a type of device connected to the computer. 735fea6fadc5e18a30c448d896a84a36ae8d8576 0 198 2384 2381 2025-06-05T15:56:22Z Madonuko 140 split fedora and ublue to different distributions correctly wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] 61fe1cd11d410b413dd1868d2203d70aadfd2d37 0 645 2385 2383 2025-06-06T10:43:21Z Hog 161 wikitext text/x-wiki A driver is a computer program that controls or operates a type of device connected to the computer. A driver provides a software interface to hardware devices, enabling operating systems and other computer programs to access functions without needing to know precise details about the hardware being used. A driver communicates with the device through the computer bus. Some Drivers are Open-Source. Some example of these are [[AMD]] Graphic Drivers. e7f9ad41d62c96d6fe5e2e886e0df90c7ce6d2fb 4 646 2386 2025-06-07T17:13:02Z Atmois 13 Create account linking instructions wikitext text/x-wiki == '''<u>DO NOT share the link provided with anyone, including any staff members.</u>''' == To link your Discord and '''atl.wiki''' accounts in our [https://discord.gg/linux discord server], type <code>/verify</code> using '''''@atl.wiki'''''. You will receive a private link in your DM's, Then click the link, press '''Allow''', and return to Discord, if your '''atl.wiki''' account is at least '''3 days old''', and has met the '''minimum edit threshold''', uou will automatically be given the '''''@Wiki Author''''' role, which comes with bonus perks in the Discord server such as boosted XP, extra permissions and exclusive chat access. You may need to wait up to an hour for the role to be given. If you do not receive it open a ticket with <code>/ticket</code> and ask for help. If you have met the requirements '''after''' initially verifying, run <code>/unverify</code> then go through the verification process again, this will refresh your role. To see if you meet the requirements, visit the [[Special:UserRights]] page, search your username, and see if you're an ''implicit member of "Autoconfirmed Users"''. This role is automatically given by the wiki to users who meet the criteria. 00e2371d530d90068ba6efb60f70280f435d3cd2 8 624 2387 2262 2025-06-07T20:44:36Z Atmois 13 try improve readability of URLs css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all types of links, cleaner version */ a, a:visited, .external, .external:visited, .mw-redirect, .new { text-decoration: underline; } 829bad963889c62d6ab79786e61e170aff8a124b 0 1 2388 2263 2025-06-08T11:21:09Z Atmois 13 Add some info on instructions wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. You may also link your '''atl.wiki''' account to your discord account, following [[Atl.wiki:Discord Linking|these instructions]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Our Key Values ====== We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed on our [[Atl.wiki:Contact|Contact]] page. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ 9eb284959eaac3eaa28891e211e8efef6a558e0f 6 647 2389 2025-06-08T18:20:04Z Amadaluzia 52 wikitext text/x-wiki This is a desktop setup for FreeBSD that is the current daily driver of Amadaluzia. (8th of June, 2025) The window manager being used in this image is sway. e7012376dc8d7e38cacf3f0e0443f3158fc299a9 2 648 2390 2025-06-08T19:44:21Z Amadaluzia 52 Create a FreeBSD desktop page wikitext text/x-wiki [[File:Amadaluzia's FreeBSD Desktop.png|alt=A sway desktop running on FreeBSD 14.2-RELEASE|thumb|An example of a FreeBSD desktop]] [[FreeBSD]] is an operating system made for used by servers, desktops and embedded systems due to it's stability, advanced features and community behind it.<ref>[https://www.freebsd.org/ The FreeBSD official website] </ref> Many desktop environments can be installed on FreeBSD such as GNOME, KDE and XFCE.<ref>[https://docs.freebsd.org/en/books/handbook/desktop/ FreeBSD Handbook - Chapter 8. Desktop Environments]</ref> You can also expect find many of the available generic Linux-based utilities with examples being D-Bus, PulseAudio and WINE. As such, you may use FreeBSD like any Linux desktop, with exceptions. == Understanding the FreeBSD desktop stack == Similar to Linux-based operating systems<ref>[[wikipedia:Linux_range_of_use#Desktop|Desktop Linux components]]</ref>, it uses the following model: * The core of the system is the hardware, this consists of your CPU and GPU, and any potential peripherals (mouse, keyboard, and any connected displays). * The kernel, which uses the hardware directly using drivers and loads kernel modules (for example, OSS for sound devices) * The libc, which implements C functions needed by dynamically linked software * The system daemons that is set to start (for example, any screen reader daemons for visually impaired users) * The display server used for displaying a desktop (for example, Wayland or X11) * Any graphical libraries used for your desktop (for example, Qt6 on KDE Plasma) * Any desktop shells needed so your desktop can provide widgets (for example, GNOME Shell for GNOME) <references /> e151297313a7bb690d7ae96ae2e537dc96e8e0f9 2391 2390 2025-06-08T19:52:49Z Amadaluzia 52 Correct misrepresentation and grammar wikitext text/x-wiki [[File:Amadaluzia's FreeBSD Desktop.png|alt=A sway desktop running on FreeBSD 14.2-RELEASE|thumb|An example of a FreeBSD desktop]] [[FreeBSD]] is an operating system made for used by servers, desktops and embedded systems due to it's stability, advanced features and community behind it.<ref>[https://www.freebsd.org/ The FreeBSD official website] </ref> Many desktop environments can be installed on FreeBSD such as GNOME, KDE and XFCE.<ref>[https://docs.freebsd.org/en/books/handbook/desktop/ FreeBSD Handbook - Chapter 8. Desktop Environments]</ref> You can also expect find many of the available generic Linux-based utilities with examples being D-Bus, PulseAudio and WINE. As such, you may use FreeBSD like any Linux desktop, with exceptions. == Understanding the FreeBSD desktop stack == Similar to Linux-based operating systems,<ref>[[wikipedia:Linux_range_of_use#Desktop|Wikipedia - Components of the Linux Desktop]]</ref> it uses the following model: * The core of the system is the hardware, this consists of your CPU and GPU, and any potential peripherals (mouse, keyboard, and any connected displays). * The kernel, which uses the hardware directly using drivers and loads kernel modules (for example, OSS for sound devices) * The libc, which implements C functions needed by dynamically linked software * The system daemons that is set to start (for example, any screen reader daemons for visually impaired users) * The display server used for displaying a desktop (for example, Wayland or X11) * Any graphical libraries used for your desktop (for example, Qt6 on KDE Plasma) * Any desktop shells needed so your desktop can provide widgets (for example, GNOME Shell for GNOME) Additionally, this model is closely followed by the Darwin kernel architecture.<ref>[[wikipedia:Architecture_of_Windows_NT|Wikipedia - Mac OS X Architecture]] </ref><references /> f37042ebc17cdd93069ed5b9c803462a97df4cc4 2392 2391 2025-06-08T19:55:54Z Amadaluzia 52 Fix missed grammar wikitext text/x-wiki [[File:Amadaluzia's FreeBSD Desktop.png|alt=A sway desktop running on FreeBSD 14.2-RELEASE|thumb|An example of a FreeBSD desktop]] [[FreeBSD]] is an operating system used by servers, desktops and embedded systems due to it's stability, advanced features and community behind it.<ref>[https://www.freebsd.org/ The FreeBSD official website] </ref> Many desktop environments can be installed on FreeBSD such as GNOME, KDE and XFCE.<ref>[https://docs.freebsd.org/en/books/handbook/desktop/ FreeBSD Handbook - Chapter 8. Desktop Environments]</ref> You can also expect find many of the available generic Linux-based utilities with examples being D-Bus, PulseAudio and WINE. As such, you may use FreeBSD like any Linux desktop, with exceptions. == Understanding the FreeBSD desktop stack == Similar to Linux-based operating systems,<ref>[[wikipedia:Linux_range_of_use#Desktop|Wikipedia - Components of the Linux Desktop]]</ref> it uses the following model: * The core of the system is the hardware, this consists of your CPU and GPU, and any potential peripherals (mouse, keyboard, and any connected displays). * The kernel, which uses the hardware directly using drivers and loads kernel modules (for example, OSS for sound devices) * The libc, which implements C functions needed by dynamically linked software * The system daemons that is set to start (for example, any screen reader daemons for visually impaired users) * The display server used for displaying a desktop (for example, Wayland or X11) * Any graphical libraries used for your desktop (for example, Qt6 on KDE Plasma) * Any desktop shells needed so your desktop can provide widgets (for example, GNOME Shell for GNOME) Additionally, this model is closely followed by the Darwin kernel architecture.<ref>[[wikipedia:Architecture_of_Windows_NT|Wikipedia - Mac OS X Architecture]] </ref><references /> ea4eba379a30e6938778f3a2c5b9035173f99d6d 2393 2392 2025-06-08T19:57:13Z Amadaluzia 52 Missed word wikitext text/x-wiki [[File:Amadaluzia's FreeBSD Desktop.png|alt=A sway desktop running on FreeBSD 14.2-RELEASE|thumb|An example of a FreeBSD desktop]] [[FreeBSD]] is an operating system used by servers, desktops and embedded systems due to it's stability, advanced features and community behind it.<ref>[https://www.freebsd.org/ The FreeBSD official website] </ref> Many desktop environments can be installed on FreeBSD such as GNOME, KDE and XFCE.<ref>[https://docs.freebsd.org/en/books/handbook/desktop/ FreeBSD Handbook - Chapter 8. Desktop Environments]</ref> You can also expect to find many of the available generic Linux-based utilities with examples being D-Bus, PulseAudio and WINE. As such, you may use FreeBSD like any Linux desktop, with exceptions. == Understanding the FreeBSD desktop stack == Similar to Linux-based operating systems,<ref>[[wikipedia:Linux_range_of_use#Desktop|Wikipedia - Components of the Linux Desktop]]</ref> it uses the following model: * The core of the system is the hardware, this consists of your CPU and GPU, and any potential peripherals (mouse, keyboard, and any connected displays). * The kernel, which uses the hardware directly using drivers and loads kernel modules (for example, OSS for sound devices) * The libc, which implements C functions needed by dynamically linked software * The system daemons that is set to start (for example, any screen reader daemons for visually impaired users) * The display server used for displaying a desktop (for example, Wayland or X11) * Any graphical libraries used for your desktop (for example, Qt6 on KDE Plasma) * Any desktop shells needed so your desktop can provide widgets (for example, GNOME Shell for GNOME) Additionally, this model is closely followed by the Darwin kernel architecture.<ref>[[wikipedia:Architecture_of_Windows_NT|Wikipedia - Mac OS X Architecture]] </ref><references /> 6c081c95779312728488a92c1b9fbea0724589cb 2396 2393 2025-06-08T20:34:24Z Amadaluzia 52 Add critiques section wikitext text/x-wiki [[File:Amadaluzia's FreeBSD Desktop.png|alt=A sway desktop running on FreeBSD 14.2-RELEASE|thumb|An example of a FreeBSD desktop]] [[FreeBSD]] is an operating system used by servers, desktops and embedded systems due to it's stability, advanced features and community behind it.<ref>[https://www.freebsd.org/ The FreeBSD official website] </ref> Many desktop environments can be installed on FreeBSD such as GNOME, KDE and XFCE.<ref>[https://docs.freebsd.org/en/books/handbook/desktop/ FreeBSD Handbook - Chapter 8. Desktop Environments]</ref> You can also expect to find many of the available generic Linux-based utilities with examples being D-Bus, PulseAudio and WINE. As such, you may use FreeBSD like any Linux desktop, with exceptions. == Understanding the FreeBSD desktop stack == Similar to Linux-based operating systems,<ref>[[wikipedia:Linux_range_of_use#Desktop|Wikipedia - Components of the Linux Desktop]]</ref> it uses the following model: * The core of the system is the hardware, this consists of your CPU and GPU, and any potential peripherals (mouse, keyboard, and any connected displays). * The kernel, which uses the hardware directly using drivers and loads kernel modules (for example, OSS for sound devices) * The libc, which implements C functions needed by dynamically linked software * The system daemons that are set to start by default, or enabled manually in <code>/etc/rc.conf</code> (for example, any screen reader daemons for visually impaired users) * The display server used for displaying a desktop (for example, Wayland or X11) * Any graphical libraries used for your desktop (for example, Qt6 on KDE Plasma) * Any desktop shells needed so your desktop can provide widgets (for example, GNOME Shell for GNOME) Additionally, this model is closely followed by the Darwin kernel architecture.<ref>[[wikipedia:Architecture_of_Windows_NT|Wikipedia - Mac OS X Architecture]]</ref> == Critiques == The critiques of FreeBSD for desktop usage is also carried over from the Linux desktop, as the flaws from there are present in FreeBSD too. There are also flaws from a lack of *native* FreeBSD support,{{Citation_needed|reason="I don't know of any way I can back up this claim, as Steam or other sources such as SteamDB doesn't actually disclose any useful information regarding use on FreeBSD"}} which is critical for users of Steam. However, this is remedied by setting up Linux emulation.<ref>[https://docs.freebsd.org/en/books/handbook/linuxemu/ FreeBSD Handbook - Chapter 12. Linux Binary Compatibility]</ref> <references /> 38665828f97f35f663b6ead1fe617d9135c5b0b1 2397 2396 2025-06-08T20:40:58Z Amadaluzia 52 Fix citations wikitext text/x-wiki [[File:Amadaluzia's FreeBSD Desktop.png|alt=A sway desktop running on FreeBSD 14.2-RELEASE|thumb|An example of a FreeBSD desktop]] [[FreeBSD]] is an operating system used by servers, desktops and embedded systems due to it's stability, advanced features and community behind it.<ref>[https://www.freebsd.org/ The FreeBSD official website] </ref> Many desktop environments can be installed on FreeBSD such as GNOME, KDE and XFCE.<ref>[https://docs.freebsd.org/en/books/handbook/desktop/ FreeBSD Handbook - Chapter 8. Desktop Environments]</ref> You can also expect to find many of the available generic Linux-based utilities with examples being D-Bus, PulseAudio and WINE. As such, you may use FreeBSD like any Linux desktop, with exceptions. == Understanding the FreeBSD desktop stack == Similar to Linux-based operating systems,<ref>[[wikipedia:Linux_range_of_use#Desktop|Wikipedia - Components of the Linux Desktop]]</ref> it uses the following model: * The core of the system is the hardware, this consists of your CPU and GPU, and any potential peripherals (mouse, keyboard, and any connected displays). * The kernel, which uses the hardware directly using drivers and loads kernel modules (for example, OSS for sound devices) * The libc, which implements C functions needed by dynamically linked software * The system daemons that are set to start by default, or enabled manually in <code>/etc/rc.conf</code><ref>[https://docs.freebsd.org/en/books/handbook/config/#_the_etc_directory FreeBSD Handbook - Chapter 14.2.1. the /etc/ directory]</ref> (for example, any screen reader daemons for visually impaired users) * The display server used for displaying a desktop (for example, Wayland or X11) * Any graphical libraries used for your desktop (for example, Qt6 on KDE Plasma) * Any desktop shells needed so your desktop can provide widgets (for example, GNOME Shell for GNOME) Additionally, this model is closely followed by the Darwin kernel architecture.<ref>[[wikipedia:Architecture_of_macOS#Mac_OS_X|Wikipedia - Mac OS X Architecture]]</ref> == Critiques == The critiques of FreeBSD for desktop usage is also carried over from the Linux desktop, as the flaws from there are present in FreeBSD too. There are also flaws from a lack of *native* FreeBSD support,{{Citation_needed|reason="I don't know of any way I can back up this claim, as Steam or other sources such as SteamDB doesn't actually disclose any useful information regarding use on FreeBSD"}} which is critical for users of Steam. However, this is remedied by setting up Linux emulation.<ref>[https://docs.freebsd.org/en/books/handbook/linuxemu/ FreeBSD Handbook - Chapter 12. Linux Binary Compatibility]</ref> <references /> 885afea7249732b5526de8f5035a13668ad1ebce 2398 2397 2025-06-08T20:48:43Z Amadaluzia 52 Fix citations to fit guidelines wikitext text/x-wiki [[File:Amadaluzia's FreeBSD Desktop.png|alt=A sway desktop running on FreeBSD 14.2-RELEASE|thumb|An example of a FreeBSD desktop]] [[FreeBSD]] is an operating system used by servers, desktops and embedded systems due to it's stability, advanced features and community behind it.<ref>[https://www.freebsd.org/ The FreeBSD official website, FreeBSD and contributors]</ref> Many desktop environments can be installed on FreeBSD such as GNOME, KDE and XFCE.<ref>[https://docs.freebsd.org/en/books/handbook/desktop/ FreeBSD Handbook - Chapter 8. Desktop Environments, FreeBSD and contributors]</ref> You can also expect to find many of the available generic Linux-based utilities with examples being D-Bus, PulseAudio and WINE. As such, you may use FreeBSD like any Linux desktop, with exceptions. == Understanding the FreeBSD desktop stack == Similar to Linux-based operating systems,<ref>[[wikipedia:Linux_range_of_use#Desktop|Components of the Linux Desktop, Wikipedia]]</ref> it uses the following model: * The core of the system is the hardware, this consists of your CPU and GPU, and any potential peripherals (mouse, keyboard, and any connected displays). * The kernel, which uses the hardware directly using drivers and loads kernel modules (for example, OSS for sound devices) * The libc, which implements C functions needed by dynamically linked software * The system daemons that are set to start by default, or enabled manually in <code>/etc/rc.conf</code><ref>[https://docs.freebsd.org/en/books/handbook/config/#_the_etc_directory FreeBSD Handbook - Chapter 14.2.1. the /etc/ directory, FreeBSD and contributors]</ref> (for example, any screen reader daemons for visually impaired users) * The display server used for displaying a desktop (for example, Wayland or X11) * Any graphical libraries used for your desktop (for example, Qt6 on KDE Plasma) * Any desktop shells needed so your desktop can provide widgets (for example, GNOME Shell for GNOME) Additionally, this model is closely followed by the Darwin kernel architecture.<ref>[[wikipedia:Architecture_of_macOS#Mac_OS_X|Mac OS X Architecture, Wikipedia]]</ref> == Critiques == The critiques of FreeBSD for desktop usage is also carried over from the Linux desktop, as the flaws from there are present in FreeBSD too. There are also flaws from a lack of *native* FreeBSD support,{{Citation_needed|reason="I don't know of any way I can back up this claim, as Steam or other sources such as SteamDB doesn't actually disclose any useful information regarding use on FreeBSD"}} which is critical for users of Steam. However, this is remedied by setting up Linux emulation.<ref>[https://docs.freebsd.org/en/books/handbook/linuxemu/ FreeBSD Handbook - Chapter 12. Linux Binary Compatibility, FreeBSD and contributors]</ref> <references /> 1a140a97d1463131ffeb637f42d02be13a58ff65 2399 2398 2025-06-08T20:51:01Z Amadaluzia 52 Move missing citation in a more logical location wikitext text/x-wiki [[File:Amadaluzia's FreeBSD Desktop.png|alt=A sway desktop running on FreeBSD 14.2-RELEASE|thumb|An example of a FreeBSD desktop]] [[FreeBSD]] is an operating system used by servers, desktops and embedded systems due to it's stability, advanced features and community behind it.<ref>[https://www.freebsd.org/ The FreeBSD official website, FreeBSD and contributors]</ref> Many desktop environments can be installed on FreeBSD such as GNOME, KDE and XFCE.<ref>[https://docs.freebsd.org/en/books/handbook/desktop/ FreeBSD Handbook - Chapter 8. Desktop Environments, FreeBSD and contributors]</ref> You can also expect to find many of the available generic Linux-based utilities with examples being D-Bus, PulseAudio and WINE. As such, you may use FreeBSD like any Linux desktop, with exceptions. == Understanding the FreeBSD desktop stack == Similar to Linux-based operating systems,<ref>[[wikipedia:Linux_range_of_use#Desktop|Components of the Linux Desktop, Wikipedia]]</ref> it uses the following model: * The core of the system is the hardware, this consists of your CPU and GPU, and any potential peripherals (mouse, keyboard, and any connected displays). * The kernel, which uses the hardware directly using drivers and loads kernel modules (for example, OSS for sound devices) * The libc, which implements C functions needed by dynamically linked software * The system daemons that are set to start by default, or enabled manually in <code>/etc/rc.conf</code><ref>[https://docs.freebsd.org/en/books/handbook/config/#_the_etc_directory FreeBSD Handbook - Chapter 14.2.1. the /etc/ directory, FreeBSD and contributors]</ref> (for example, any screen reader daemons for visually impaired users) * The display server used for displaying a desktop (for example, Wayland or X11) * Any graphical libraries used for your desktop (for example, Qt6 on KDE Plasma) * Any desktop shells needed so your desktop can provide widgets (for example, GNOME Shell for GNOME) Additionally, this model is closely followed by the Darwin kernel architecture.<ref>[[wikipedia:Architecture_of_macOS#Mac_OS_X|Mac OS X Architecture, Wikipedia]]</ref> == Critiques == The critiques of FreeBSD for desktop usage is also carried over from the Linux desktop, as the flaws from there are present in FreeBSD too. There are also flaws from a lack of native FreeBSD support which is critical for users of Steam.{{Citation_needed|I do not have any sources for this information, nor does anyone else really. Steam, nor SteamDB does not provide any information about usage of their services on FreeBSD.}} However, this is remedied by setting up Linux emulation.<ref>[https://docs.freebsd.org/en/books/handbook/linuxemu/ FreeBSD Handbook - Chapter 12. Linux Binary Compatibility, FreeBSD and contributors]</ref> <references /> 99a1e91768ff281d2847d5381241c06ff4316943 10 187 2394 1837 2025-06-08T20:26:12Z Atmois 13 wikitext text/x-wiki ^{[citation needed]}<includeonly>[[Category:Needs Citations]]</includeonly> aa1a503901b6da806b9e3bdad86f8bc1439e7f87 4 340 2395 2354 2025-06-08T20:32:13Z Atmois 13 Add Wikipedian Protester wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is accurate and up to date; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately cite your sources following our [[Guidelines#Citations]] guidelines. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that could be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, make a section on the page regarding it and ensure that you remain unbiased at all times to ensure the reader is only given the facts. We avoid advocacy and strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. There is no "best view." In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions do not belong here. ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and our standards in both the formatting, language, and terminology used. Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting]] section. If there is any doubt, consult an admin; otherwise, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. For the most part, as long as the language used is consistent with the rest of the page and the terminology is used correctly, you can use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, consult with the active editors or an admin to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, reach out to an admin for help in resolving conflicts. Be welcoming to new members, helping them to get started and teaching them the ropes. Always act in good faith while assuming the same of others. ====== <u>Accessibility</u> ====== We aim to make the wiki accessible to users of all ability levels, be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] 8d6218715c6ee3324bf6b743908e8708896c97d2 0 218 2400 2057 2025-06-13T08:36:37Z Hog 161 added Tiny Core Linux wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} == Introduction == [[Linux]] is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |LXQT | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |Linux Mint<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |Puppy Linux | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |- |Tiny Core Linux | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> c76b7e2d43565e25fbad413d0bbd44573983206d 0 354 2401 1802 2025-06-13T08:41:50Z Hog 161 added Puffy GIF :3 wikitext text/x-wiki {{Needs Citations}} {{MascotInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy|222px]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. [[File:Puffyanim.gif|thumb|3D-rendered, animated OpenBSD mascot Puffy]] [[Category:Mascots]] 03928d9f6a250eb3cf0f83567a4dc36aea718641 0 254 2402 2150 2025-06-13T08:54:32Z Hog 161 Made capitalisation consistant wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''DWM''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. DWM is designed to be small in source code, fast and light. The first version of DWM was released on July 14th, 2006. === Installation === DWM is meant to be built from source. You can download the latest version of DWM by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling DWM, make sure you have X11 installed. You most likely have it installed already, but it won't hurt if you check. DWM can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec DWM</code> in it. You can then start X (by running <code>startx</code>) and DWM should be running. It is also recommended that you install dmenu and st along with DWM, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] 98a8a407285d47df848b115840b1f99693b39788 2 3 2403 2076 2025-06-14T00:48:19Z Amadaluzia 52 rewrite program to c++ wikitext text/x-wiki <syntaxhighlight lang="c++"> #include <string> #include <unordered_map> #include <print> // Compile with C++23 or above. This will not work otherwise. struct AboutMe { std::string name, description; std::unordered_map<std::string, std::string> socials; }; int main(void) { struct AboutMe amadaluzia; amadaluzia.name = "Artur Manuel"; amadaluzia.description = R"""( I live in the UK and the internet as a background character in many free software communities (for example: you may find me on some mailing list) but I also contribute, most notably in nixpkgs. I do have other interests, such as gym, walking and photography, as well as speedrunning, filming and revising for english/maths among other things. )"""; amadaluzia.socials = { {"XMPP", "amadaluzia@xmpp.earth"}, {"Signal", "@amadaluzia.711"}, {"Email", "amad@atl.tools"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"libera.chat", "amadaluzia"}, {"discord", "amadaluzia"} }; std::println("Hello, I am {}.", amadaluzia.name); std::println(amadaluzia.description); std::println("You may find me on the following platforms:"); for (auto const &[k, v] : amadaluzia.socials) std::println("{} on {}", v, k); return 0; } </syntaxhighlight> af0e227703d787a34ff90dd94e473dbcbd52232d 2404 2403 2025-06-14T00:50:03Z Amadaluzia 52 Fix std::println error wikitext text/x-wiki <syntaxhighlight lang="c++"> #include <string> #include <unordered_map> #include <print> // Compile with C++23 or above. This will not work otherwise. struct AboutMe { std::string name, description; std::unordered_map<std::string, std::string> socials; }; int main(void) { struct AboutMe amadaluzia; amadaluzia.name = "Artur Manuel"; amadaluzia.description = R"""( I live in the UK and the internet as a background character in many free software communities (for example: you may find me on some mailing list) but I also contribute, most notably in nixpkgs. I do have other interests, such as gym, walking and photography, as well as speedrunning, filming and revising for english/maths among other things. )"""; amadaluzia.socials = { {"XMPP", "amadaluzia@xmpp.earth"}, {"Signal", "@amadaluzia.711"}, {"Email", "amad@atl.tools"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"libera.chat", "amadaluzia"}, {"discord", "amadaluzia"} }; std::println("Hello, I am {}.", amadaluzia.name); std::println("{}", amadaluzia.description); std::println("You may find me on the following platforms:"); for (auto const &[k, v] : amadaluzia.socials) std::println("{} on {}", v, k); return 0; } </syntaxhighlight> 1116cebdf20f12ebd9813594de5d32d692b5b57a 2405 2404 2025-06-14T00:55:47Z Amadaluzia 52 Fix some code errors wikitext text/x-wiki <syntaxhighlight lang="c++">#include <string> #include <unordered_map> #include <print> // Compile with C++23 or above. This will not work otherwise. struct AboutMe { std::string name, description; std::unordered_map<std::string, std::string> socials; }; int main(void) { struct AboutMe amadaluzia; amadaluzia.name = "Artur Manuel"; amadaluzia.description = R"""(I live in the UK and the internet as a background character in many free software communities (for example: you may find me on some mailing list) but I also contribute, most notably in nixpkgs. I do have other interests, such as gym, walking and photography, as well as speedrunning, filming and revising for english/maths among other things. )"""; // TODO: fix ordering amadaluzia.socials = { {"XMPP", "amadaluzia@xmpp.earth"}, {"Signal", "@amadaluzia.711"}, {"Email", "amad@atl.tools"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Libera.Chat", "amadaluzia"}, {"Discord", "amadaluzia"} }; std::println("Hello, I am {}.", amadaluzia.name); std::println("{}", amadaluzia.description); std::println("You may find me on the following platforms:"); for (auto const &[k, v] : amadaluzia.socials) std::println("{} on {}", v, k); return 0; } </syntaxhighlight> 7b4c1a54b16091a4af1bea4a1e1733de3a186759 0 291 2406 2298 2025-06-14T05:42:36Z 0Stormy 158 Change desktop photo to display default layout and theme. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|300px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 48, 2025-03-19 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[File:GNOME 43.png|thumb|A desktop running GNOME 43]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>[https://www.gnu.org/philosophy/free-sw.en.html What is Free Software?], GNU (Accessed: May 7, 2025)</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>[[wikipedia:Qt_(software)#Early_developments|Early Developments of QT]], Wikipedia (Accessed: May 7, 2025)</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>[[wikipedia:GNOME#History|History of GNOME]], Wikipedia (Accessed: May 7, 2025)</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>[https://foundation.gnome.org/ GNOME Foundation Website]</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. [[Category:Desktop Environments]] da64e64d65a9481b576925580b7c6b228d3f2454 0 622 2407 2378 2025-06-14T05:44:25Z 0Stormy 158 Change gallery photos to match pages wikitext text/x-wiki <gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE </gallery> This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} ac25416449baafb084a588dfdde51aea4c6b87ec 2410 2407 2025-06-14T19:31:10Z Cherry 131 Added enlightenment to the desktop environment page wikitext text/x-wiki <gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} 49fb9b6047f630edc2e6580f2ca77f13d388ec79 6 649 2408 2025-06-14T18:20:50Z Cherry 131 Enlightenment Logo wikitext text/x-wiki == Summary == Enlightenment Logo == Licensing == {{Unknown_copyright}} 6729102f9fc79bf697ecc85894e83a51fb1e5826 0 650 2409 2025-06-14T19:25:29Z Cherry 131 Added a page for Enlightenment wikitext text/x-wiki {{SoftwareInfobox | image=[[File:Enlightenment logo.svg|Enlightenment_logo]] | caption = Enlightenment logo | title=Enlightenment | releasestatus=Maintained | lastrelease=0.27.1, March 17, 2025 | firstrelease=0.13.2, January 18, 1998 | languages=[[C]], ELF | developers=Enlightenment foundation | website=[https://www.enlightenment.org/, enlightenment.org/] }} [https://www.enlightenment.org/ Enlightenment] is a Desktop Environment and Window Manager for Linux and other Unix-like operating systems, such as BSD derivatives.<ref name=":0">https://www.enlightenment.org/about Mentions support for Linux and other Unix-like systems and its use in Samsung devices</ref> Originally created by Carsten Haitzler in the late 90s with the philosophy "that users should be given as much control as possible."<ref>https://www.enlightenment.org/about-enlightenment contains about the Enlightenment philosophy </ref> === Features === Enlightenment has many key features as a graphical desktop including its own set of graphical and system libraries known as the "Enlightenment Foundation Libraries". Designed to be portable and efficient while also being easy to use on various devices including touch devices even being used in Samsung devices.<ref name=":0" /> Some of the features Enlightenment itself: * Support for both [https://www.x.org/wiki/ X11] and experimental [https://wayland.freedesktop.org/ Wayland] support. * A hand optimized software rendering compositor. * Very low memory requirements. * The ability to configure everything graphically. * Touch gestures * Window Management Features ** Virtual desktops. ** Optional window tiling. ** Customizable mouse and keyboard bindings. ** And many more modules. <references /> 23f6be8f2c2dfc75ee7b2e992f84ab22c36cee26 2411 2409 2025-06-14T19:33:39Z Cherry 131 Added it to the Desktop Environments Catagory wikitext text/x-wiki {{SoftwareInfobox | image=[[File:Enlightenment logo.svg|Enlightenment_logo]] | caption = Enlightenment logo | title=Enlightenment | releasestatus=Maintained | lastrelease=0.27.1, March 17, 2025 | firstrelease=0.13.2, January 18, 1998 | languages=[[C]], ELF | developers=Enlightenment foundation | website=[https://www.enlightenment.org/, enlightenment.org/] }} [https://www.enlightenment.org/ Enlightenment] is a Desktop Environment and Window Manager for Linux and other Unix-like operating systems, such as BSD derivatives.<ref name=":0">https://www.enlightenment.org/about Mentions support for Linux and other Unix-like systems and its use in Samsung devices</ref> Originally created by Carsten Haitzler in the late 90s with the philosophy "that users should be given as much control as possible."<ref>https://www.enlightenment.org/about-enlightenment contains about the Enlightenment philosophy </ref> === Features === Enlightenment has many key features as a graphical desktop including its own set of graphical and system libraries known as the "Enlightenment Foundation Libraries". Designed to be portable and efficient while also being easy to use on various devices including touch devices even being used in Samsung devices.<ref name=":0" /> Some of the features Enlightenment itself: * Support for both [https://www.x.org/wiki/ X11] and experimental [https://wayland.freedesktop.org/ Wayland] support. * A hand optimized software rendering compositor. * Very low memory requirements. * The ability to configure everything graphically. * Touch gestures * Window Management Features ** Virtual desktops. ** Optional window tiling. ** Customizable mouse and keyboard bindings. ** And many more modules. <references /> [[Category:Desktop Environments]] 539eab4d90d5f4772969d6d376d1c29ce4feda6b 2412 2411 2025-06-14T21:26:42Z Cherry 131 Corrected improper citation format wikitext text/x-wiki {{SoftwareInfobox | image=[[File:Enlightenment logo.svg|Enlightenment_logo]] | caption = Enlightenment logo | title=Enlightenment | releasestatus=Maintained | lastrelease=0.27.1, March 17, 2025 | firstrelease=0.13.2, January 18, 1998 | languages=[[C]], ELF | developers=Enlightenment foundation | website=[https://www.enlightenment.org/, enlightenment.org/] }} [https://www.enlightenment.org/ Enlightenment] is a Desktop Environment and Window Manager for Linux and other Unix-like operating systems, such as BSD derivatives.<ref name=":0">[https://www.enlightenment.org/about Enlightenment About Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref>. Originally created by Carsten Haitzler in the late 90s with the philosophy "that users should be given as much control as possible."<ref>[https://www.enlightenment.org/about-enlightenment| About Enlightenment Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref>. === Features === Enlightenment has many key features as a graphical desktop including its own set of graphical and system libraries known as the "Enlightenment Foundation Libraries". Designed to be portable and efficient while also being easy to use on various devices including touch devices even being used in Samsung devices.<ref name=":0" /> * Support for both [https://www.x.org/wiki/ X11] and experimental [https://wayland.freedesktop.org/ Wayland] support. * A hand optimized software rendering compositor. * Very low memory requirements. * The ability to configure everything graphically. * Touch gestures * Window Management Features ** Virtual desktops. ** Optional window tiling. ** Customizable mouse and keyboard bindings. ** And many more modules. <references /> [[Category:Desktop Environments]] 7a103e09d68ac95d2c7421d14115c12b1d2c98f9 0 651 2413 2025-06-16T08:52:37Z Hog 161 Added Operating System Page wikitext text/x-wiki An operating system (OS) is a collection of software that manages a computer’s hardware and applications by allocating resources, including memory, CPU, input/output devices and file storage.<ref>https://www.ibm.com/think/topics/operating-systems</ref> A user interacts with an operating system through a user interface (UI), which issues commands in a language the OS can understand. The UI can be either a graphical user interface (GUI) or a command-line interface (CLI). All computer systems need a OS to function. c5539eee7147f14ebdbceea136f915e4b31d1c84 2414 2413 2025-06-16T08:54:40Z Hog 161 Added Links wikitext text/x-wiki An operating system (OS) is a collection of [[software]] that manages a computer’s [[hardware]] and [[applications]] by allocating resources, including memory, CPU, input/output devices and file storage.<ref>https://www.ibm.com/think/topics/operating-systems</ref> A user interacts with an operating system through a [[user interface]] (UI), which issues commands in a language the OS can understand. The UI can be either a [[graphical user interface]] (GUI) or a [[command-line interface]] (CLI). All computer systems need a OS to function. 4e90610a28d6a4157e4ca48d308edf5671d24afb 0 517 2415 2080 2025-06-16T12:10:28Z Hog 161 Added Links wikitext text/x-wiki {{Cleanup|Installation instructions should be separated onto their own Guides page.}} {{Needs_Citations}} = What is a System Call? = A system call (syscall) is a mechanism that allows a program to interact with the [[Operating System|operating system]]. It acts as a bridge between the user space (where applications run) and the kernel space (where the operating system manages hardware and system resources). Programs use system calls to request services from the OS, such as managing files, processes, or hardware devices. For example, when you open a file, your application cannot directly access the hardware. Instead, it makes a system call (e.g., open()), which the OS handles to perform the requested task. Note that this is not a guide for ALL syscalls, but it is a guide to get you familiar enough with syscalls and strace. == Why Should You Learn About System Calls? == 1. Understanding How Programs Work: - System calls reveal how applications interact with the operating system to perform tasks like file handling, memory management, and networking. 2. Efficient Troubleshooting: - Knowing system calls can help diagnose performance issues or bugs by identifying which calls a program relies on. 3. Optimizing Software: - When developing programs, understanding system calls allows you to write efficient code by leveraging the right OS-level functions. 4. Security Awareness: - Many exploits and vulnerabilities target how system calls are used (or misused). Understanding them helps in writing secure code. 5. Kernel-Level Development: - If you're interested in low-level programming, such as operating system development or driver creation, system calls are fundamental. Basically, system calls are the foundation of how software and operating systems interact, making them essential knowledge for both beginner and advanced developers. == Categories of System Calls == System calls are grouped into five main categories: '''Process Control''' – Manage processes (create, terminate, etc.). '''File Management''' – Handle file operations (open, read, write, close). '''Device Management''' – Interact with hardware devices. '''Information Maintenance''' – Exchange information between the OS and programs. '''Communication''' – Enable processes to communicate. 1. '''Process Control''' * fork(): Creates a new process (child) that runs the same program as the parent. * exit(): Terminates the process and frees resources. * exec(): Replaces the current program in a process with a new one. 2. '''File Management''' * open(): Opens a file for reading or writing. * read(): Reads data from a file (multiple processes can read simultaneously). * write(): Writes data to a file (only one process can write at a time). * close(): Closes an open file. 3. '''Device Management''' * ioctl(): Performs device-specific operations not covered by standard calls (e.g., configuring hardware). 4. '''Information Maintenance''' * getpid(): Returns the process ID of the current process. * alarm(): Sets a timer to deliver a signal after a specified time. * sleep(): Pauses the process for a given time. 5. '''Communication''' * pipe(): Enables communication between processes via file descriptors. * shmget(): Allocates shared memory for process communication. * mmap(): Maps files or devices into a process’s memory. == Using strace to Look at System Calls == strace is a command-line tool that lets you see the system calls a program makes while it runs. It’s great for debugging, understanding program behavior, or learning how system calls work. === How to use strace === Steps to Use strace: 1. '''Run a Command with strace''': <syntaxhighlight lang="bash">strace <command></syntaxhighlight> This will show all the system calls made by the command. 2. '''Attach to a Running Process''': If a program is already running, use its process ID (PID): <syntaxhighlight lang="bash">strace -p <PID></syntaxhighlight> 3. '''Filter Specific System Calls''': To narrow down the output, trace specific system calls using the -e option: <syntaxhighlight lang="bash">strace -e <syscall> <command></syntaxhighlight> 4. '''Save Output to a File''': Use -o to redirect the output to a file for easier analysis: <syntaxhighlight lang="bash">strace -o trace_output.txt <command></syntaxhighlight> 5. '''Trace Execution Times''': To see how long each system call takes, use: <syntaxhighlight lang="bash">strace -T <command></syntaxhighlight> === Why Use strace? === * Debug program behavior (e.g., "Why is this program failing?"). * Identify which files, devices, or network resources a program accesses. * Learn what system calls a program makes for educational purposes. 7b1d8da1131ea9cad0d33128cdf6333bc9b9a234 0 415 2416 1438 2025-06-16T12:13:56Z Hog 161 Added Links wikitext text/x-wiki POSIX, a rewritten name that stands for "Portable Operating System Interface" in replacement for IEEE-IX for the IEEE Computer Society, is a set of standards for upkeeping compatibility across different [[Operating System|operating systems]] as it defines system & user-levels [[API|APIs]] in the addition of utility interfaces and command line shells for portability with [[Unix]], Unix-Based/Like operating systems, and more.<ref>The Linux Code, November 1, 2023, ''POSIX: A Thorough Overview for Linux Developers — https://thelinuxcode.com/posix-standard/''</ref> === Modern Day POSIX Standards === There are many modern-day standards for POSIX, in order for a Unix-Based/Like operating system to POSIX-Compliant, it must provide implementations of the many POSIX APIs. These standards include the ability to use core services and/or processes properly: Core API Services and its processes, threads, signals, basic file I/O, as well as using [[Shell]] utilities such as bash and following commands like <code>grep</code> , <code>sort</code>, <code>find</code>, and plenty more. <references /> 7df275ff89370057fef16fb68743d1b73b9dcc8b 0 203 2417 2037 2025-06-16T12:31:56Z Hog 161 Added Links wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by Daniel Robbins. Known for its emphasis on customization and performance optimization, Gentoo allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == Gentoo stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === * Complete system customization through source compilation * Choice between OpenRC and systemd init systems * Extensive hardware architecture support * Rolling release model with stable branch option * Minimal base system requirements * Advanced package management through Portage == Installation == Installing Gentoo requires manual configuration and compilation of the system components. The process involves: * Preparing the installation environment * Partitioning and formatting storage * Configuring and compiling the kernel * Setting up the bootloader * Installing and configuring base system packages For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is Gentoo's package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |} == System Optimization == === Compilation Flags === Gentoo users can optimize their system through: * CPU-specific optimizations * Custom compile flags * USE flag combinations * Kernel configuration * Package-specific settings === Binary Packages === For users seeking faster installation times, Gentoo offers: * Pre-compiled package options * Binary package creation * Distribution of binary packages * Mixed source/binary environments == Security == Gentoo implements several security measures: * SELinux support * Hardened profiles * Regular security updates * Signed package verification * Kernel hardening options == Community and Development == === Community Resources === * [https://forums.gentoo.org/ Official Forums] * IRC channels * Mailing lists * Wiki documentation * Bug tracking system === Development Model === * Open source development * Community-driven package maintenance * Regular security updates * Active development team * Public Git repositories == Comparison with Other Distributions == === Advantages === * Maximum customization potential * Optimal performance through compilation * Complete control over features * Extensive documentation * Active community support === Considerations === * Longer installation time * Higher learning curve * Requires technical knowledge * Resource-intensive compilation * Regular maintenance needed == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" comes from the fast-swimming Gentoo penguin * View Larry by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 25279ffeb0a71cccb6bcd5d18ac138b82efea2db 0 173 2418 2030 2025-06-16T12:34:16Z Hog 161 Added Links wikitext text/x-wiki {{Cleanup|Incomplete page & Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager (G'''DM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a [[graphical user interface]] that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.<ref>https://github.com/tvrzna/emptty</ref> [[Category:Terminology]] 3d70f9c62b19e85f66258ceaa03bf8b0551d7f89 0 322 2419 1813 2025-06-16T12:37:51Z Hog 161 Added Links wikitext text/x-wiki {{Needs Citations}} == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the [[Linux|Linux kernel]], released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on [[Operating System|Operating Systems]] === [[Linux Distributions|Linux distributions]] which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * [[Sabotage]] * [[Morpheus Linux]] * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against [[glibc]]. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] [[Category:Software]] e896d4863e68a751cb46bc64fab7e35cbef59672 0 269 2420 2023 2025-06-16T13:12:33Z Hog 161 Added Links wikitext text/x-wiki {{Cleanup|Instructions should be separated onto their own page under the Guides namespace}} {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], budgie provides an easy to use [[User Interface|interface]] for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] === Features === '''Budgie Desktop View''' is a [[:Category:Software|software]] component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. === Installation === Budgie is available on almost all [[Linux Distributions|Linux distributions]]. ==== Arch-based systems ==== To install the '''budgie''' package group, which includes first-party applications such as a screensaver, execute <code>sudo pacman -S budgie</code>. Alternatively, <code>sudo pacman -S budgie-desktop</code> will install the standalone desktop. Recommended optional packages include the Arc GTK theme, the Papirus icon theme, and the Network Manager applet. Executing <code>sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet</code> will install them. ==== Fedora Linux ==== [[Fedora]] has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. ==== Ubuntu ==== There is a [https://ubuntubudgie.org/ community ISO] that contains [[Ubuntu]] with Budgie Desktop instead of GNOME. ==== Void Linux ==== <code>sudo xbps-install budgie-desktop</code> ==== OpenSUSE ==== Budgie can be selected during the OpenSUSE installation or installed afterward using <code>sudo zypper install budgie-desktop</code>. [[Category:Desktop Environments]] 764187bcce105beba10b35aa77178d028f0e2f23 0 418 2421 1663 2025-06-16T13:14:13Z Hog 161 Added Links wikitext text/x-wiki {{DistributionInfobox|architectures=arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox|caption=The FreeBSD logo|defaultdesktops=[[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]]|image=[[File:FreeBSD logo.png|200px|FreeBSD_logo]]|packagemanager=pkg|releasemodel=Stable|releasestatus=Maintained|title=FreeBSD|usagetype=Desktop, Firewall, Raspberry Pi, Server|website=[https://freebsd.org freebsd.org]}} FreeBSD is a [[Unix]] [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released on November 1993<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"]. [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref>. [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[Drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a [[kernel]] and [[drivers]], and relying on third-parties such as [[GNU]] for system [[:Category:Software|software]]<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref>. The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref>. The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']}<references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 3e9232c15cd8a709b4687dabe0a5c116ad4c652e 0 297 2422 2061 2025-06-16T13:19:33Z Hog 161 Spelling mistakes and added links wikitext text/x-wiki {{Cleanup|Instructions need to be separated onto their own page under the Guides namespace}} == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref>. The core concept of multi-booting revolves around partitioning a computer’s [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref>, including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == How to Multi-boot == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen [[Linux Distributions|distribution]] search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitions"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-Boot|Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! <references /> [[Category:Terminology]] f5f4a1882c949b1f6dc6fc01dd3780d6fba5c354 2426 2422 2025-06-17T07:11:54Z Hog 161 Added link to a guide. will create guide now. unsure of how to add to guides subgroup wikitext text/x-wiki {{Cleanup|Instructions need to be separated onto their own page under the Guides namespace}} == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref>. The core concept of multi-booting revolves around partitioning a computer’s [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref>, including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == [[Guides:How to Multi-boot]] == These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen [[Linux Distributions|distribution]] search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitions"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-Boot|Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! <references /> [[Category:Terminology]] 54cc6716caba6b939ef32788c84883cc484da75c 2429 2426 2025-06-17T07:15:38Z Hog 161 Moved Guide to dedicated page wikitext text/x-wiki {{Cleanup|Instructions need to be separated onto their own page under the Guides namespace}} == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref>. The core concept of multi-booting revolves around partitioning a computer’s [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref>, including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats.<references /> [[Category:Terminology]] 8b35b44c6bce265eb6ef7dfc92ff7c83e424551b 2430 2429 2025-06-17T07:16:01Z Hog 161 Removed warning wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref>. The core concept of multi-booting revolves around partitioning a computer’s [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref>, including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats.<references /> [[Category:Terminology]] 5ab1f721db6a85ae4227c6247db9b6c47e7289ea 0 344 2423 2045 2025-06-16T13:34:51Z Hog 161 Updated, added references, added links wikitext text/x-wiki {{Cleanup|Short article, requires more information}}{{Needs Citations}} The Kernel is the core part of any [[Operating System|operating system]], including [[Linux]]. It's the fundamental layer between your [[hardware]] (like your CPU, memory, and GPU) and the [[:Category:Software|software]] you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, Etc). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. [[Category:Terminology]] d17c8993f761d0831e13fd83afd23e9db5c15e2a 2424 2423 2025-06-16T13:35:03Z Hog 161 wikitext text/x-wiki The Kernel is the core part of any [[Operating System|operating system]], including [[Linux]]. It's the fundamental layer between your [[hardware]] (like your CPU, memory, and GPU) and the [[:Category:Software|software]] you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, Etc). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. [[Category:Terminology]] 78916de9f6c579e414bc34ddb297bcfc2843a64d 2425 2424 2025-06-17T07:06:13Z Hog 161 Edited citations and added image wikitext text/x-wiki [[File:Kernel Layout.svg|thumb|How the Kernel interacts with the software and hardware]] The Kernel is the core part of any [[Operating System|operating system]], including [[Linux]]. It's the fundamental layer between your [[hardware]] (like your CPU, memory, and GPU) and the [[:Category:Software|software]] you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, Etc). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2 Linus Torvalds 1991 (Retrieved 16th March 2025)</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel Kicksecure, Madaiden, Adrelanos 2023 (Retrieved 16th March 2025)</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. [[Category:Terminology]] 714aeff38a65e98c208676b40822420ac19af1fc 3000 652 2427 2025-06-17T07:12:19Z Hog 161 Ported instructions over wikitext text/x-wiki These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen [[Linux Distributions|distribution]] search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficent backups of data on the deivce to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficent storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io/ Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitions"''' app then you want to find your primary Windows partition (Useually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficent amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' submenu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-Boot|Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! a78fba4871c4be9c80d73c97eda69d01b411ce52 2428 2427 2025-06-17T07:13:20Z Hog 161 Spelling mistakes wikitext text/x-wiki These are some generic instructions for Dual-booting that should apply to most Linux distributions when Dual-booting with Windows, for instructions specific for your chosen [[Linux Distributions|distribution]] search up the distribution's wiki or search for a tutorial on YouTube. No matter how you Multi-boot you want to ensure you make sufficient backups of data on the device to an external medium and ensure you have a method of recovering your original OS. You will require a USB drive with at minimum 4GB of storage and you should ensure you have sufficient storage on your computer before continuing. If you are Dual-booting Windows and a Linux distribution it is the best practise to install Windows first as it will likely override your Linux [[bootloader]] when it installs itself. Once you are ready you want to download the ISO from your distribution's website and then using a tool like [https://etcher.balena.io/ Balena Etcher] flash the ISO onto the USB. Once this is complete you might want to test the distribution first using its [[Live Environment]], if so skip the following step regarding partitions. If you wish to continue installing you should open the '''"Create and format hard drive partitions"''' app then you want to find your primary Windows partition (Usually denoted with '''"Windows (C:)")''' and then right click and select '''"Shrink volume"'''. Then shrink it by however much you want to assign to your distribution (See their download page or wiki for how much space is required by minimum). You will want to also leave a sufficient amount of space for Windows on your drive and then hit '''"Shrink"'''. Then you can reboot your computer, if you are installing a [[Debian]] or [[Fedora]] based distribution you can skip the following step regarding [[Secure Boot|secure boot]]. You will now need to disable secure boot, you can do so by when booting up hitting the key for your [[BIOS]] menu (Typically '''F2''' or '''Delete'''), please note this menu will vary depending on your motherboard and you can find where to find the secure boot option by searching Google for your motherboard model, however it is typically in the '''Boot''' sub-menu, you want to select it and disable it and then you can save and exit. Then you want to go into your boot menu by hitting the relevant key for it (Typically '''F12''') when rebooting, you then want to select the option for your USB and then select the top most option in the boot menu for the USB and wait. Once you enter the Live Environment you can test things without risk of breaking your current installation, if you are ready to install open the installer usually on the desktop and follow the steps on the installer and set it up as you wish. When prompted for partitions (We highly suggest you find distribution specific guides for this) you will want to select the option to override a specific partition and then select the empty space which you created by shrinking your existing partition. Then you can continue and complete the installation. Once it is complete you can reboot and you should be promoted by a [[GRUB]] or [[Systemd-Boot|Systemd-boot]] menu with the option for your installed distribution and Windows, you are now done and can enjoy having multiple OS's on your device! 7b90b14ef7dc5096cf226eed1aa43e556e3dba80 0 169 2431 2361 2025-06-17T07:27:59Z Digit 165 /* List of Package Managers */ add palusid/exherbo, cpt/carbs, guix/guixsd, apk/alpine, scratch/venom, pmm/bedrock wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) [[NixOS]]'s Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. [[Category:Terminology]] c785c90571f4ce8576866d5ae2b4910fd919c06e 0 313 2432 2359 2025-06-17T07:38:32Z Hog 161 Added Links wikitext text/x-wiki [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] {{Needs Citations}} == Overview == [https://github.com/linuxmint/cinnamon Cinnamon] is a desktop environment maintained by the [https://www.linuxmint.com/ Linux Mint] team. Forked from [[GNOME]] Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in [[JavaScript]], with core libraries being written in [[C]]. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === A "Spice" is Cinnamon's name for an add-on applet, desklet, theme, widget, and more. They can be found at the [https://cinnamon-spices.linuxmint.com/ Cinnamon Spices repository website]. == Cinnamon applications == Cinnamon uses the X-app suite, which are a set of apps forked from GNOME and changed to work across XFCE, Cinnamon and MATE. {| class="wikitable" |+The list of apps are the following: !Application !GNOME !X-apps equivalent |- |Text editor |Gedit |xed |- |Image viewer |Eye of GNOME (EoG) |xviewer |- |Image organizer |gthumb |pix |- |Media player |Totem |xplayer |- |Document editor |Atril |xreader |} == Starting Cinnamon == There are two main methods of starting Cinnamon: * Selecting "Cinnamon" from your preferred [[Display Manager]] ** If your session crashes or has graphical artifacts you should select "Cinnamon (software rendering) instead, which disables 3D acceleration * Modifying your [[Xinitrc]] to include <code>exec cinnamon-session</code> [[Category:Desktop Environments]] 1ec023f9559ad2f6926949fb0cd3358185413d25 0 653 2433 2025-06-17T08:30:20Z Hog 161 Created page with "{{DistributionInfobox|title=Pop!_OS|image=APT (command-line frontend), dpkg (backend), Pop!_Shop (GUI), Flatpak|caption=The Pop!_OS logo|releasestatus=Maintained|packagemanager=[[Pacman]]|defaultdesktops=COSMIC|usagetype=Desktop|architectures=x86_64|website=[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX]}}Pop!_OS is a free and open-sourced Linux distribution based on Ubuntu. Pop!_OS features a custom desktop environment, based..." wikitext text/x-wiki {{DistributionInfobox|title=Pop!_OS|image=APT (command-line frontend), dpkg (backend), Pop!_Shop (GUI), Flatpak|caption=The Pop!_OS logo|releasestatus=Maintained|packagemanager=[[Pacman]]|defaultdesktops=COSMIC|usagetype=Desktop|architectures=x86_64|website=[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX]}}Pop!_OS is a free and open-sourced Linux distribution based on Ubuntu. Pop!_OS features a custom desktop environment, based on GNOME, called COSMIC. Pop!OS is developed by American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. === <u>Features</u> === * Full support for Nvidia and AMD GPUs * Disk Encryption * Window and Workspace managment * Recover Partition tool * GUI toggle 56aab789c6e8c76fa9cb3b03dbd8229f06ccf5d5 0 653 2434 2433 2025-06-17T08:46:07Z Hog 161 Fixed info box partially still needs some help wikitext text/x-wiki {{DistributionInfobox|title=Pop!_OS|image=[[File:File:Pop! OS Icon.svg|Pop!_OS Logo]]|caption=The Pop!_OS logo|releasestatus=Maintained|packagemanager=[[Pacman]]|defaultdesktops=COSMIC|usagetype=Desktop|architectures=x86_64|website=Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX]|releasemodel=Rolling release}}Pop!_OS is a free and open-sourced Linux distribution based on Ubuntu. Pop!_OS features a custom desktop environment, based on GNOME, called COSMIC. Pop!OS is developed by American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. === <u>Features</u> === * Full support for Nvidia and AMD GPUs * Disk Encryption * Window and Workspace managment * Recover Partition tool * GUI toggle 9aafc80df663f721b54410208365eef812a70158 2438 2434 2025-06-17T09:20:25Z Hog 161 Fixed Image wikitext text/x-wiki {{DistributionInfobox|title=Pop!_OS|image=[[File:Pop! OS Icon.svg|Thumb]]|caption=The Pop!_OS logo|releasestatus=Maintained|packagemanager=[[Pacman]]|defaultdesktops=COSMIC|usagetype=Desktop|architectures=x86_64|website=Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX]|releasemodel=Rolling release}}Pop!_OS is a free and open-sourced Linux distribution based on Ubuntu. Pop!_OS features a custom desktop environment, based on GNOME, called COSMIC. Pop!OS is developed by American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. === <u>Features</u> === * Full support for Nvidia and AMD GPUs * Disk Encryption * Window and Workspace managment * Recover Partition tool * GUI toggle 91b1cd75d666adaa58a645a8fc48235a85a41126 2439 2438 2025-06-17T09:22:56Z Hog 161 Added Links wikitext text/x-wiki {{DistributionInfobox|title=Pop!_OS|image=[[File:Pop! OS Icon.svg|Thumb]]|caption=The Pop!_OS logo|releasestatus=Maintained|packagemanager=[[Pacman]]|defaultdesktops=COSMIC|usagetype=Desktop|architectures=x86_64|website=Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX]|releasemodel=Rolling release}}Pop!_OS is a free and open-sourced [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]], based on [[GNOME]], called [[COSMIC]]. Pop!OS is developed by American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. === <u>Features</u> === * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace managment * Recover Partition tool * GUI toggle 923834b734eac041883fe2e1bd95ba38ed7b84c0 2447 2439 2025-06-17T16:15:59Z Madonuko 140 Show title correctly wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{DistributionInfobox|title=Pop!_OS|image=[[File:Pop! OS Icon.svg|Thumb]]|caption=The Pop!_OS logo|releasestatus=Maintained|packagemanager=[[Pacman]]|defaultdesktops=COSMIC|usagetype=Desktop|architectures=x86_64|website=Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX]|releasemodel=Rolling release}}Pop!_OS is a free and open-sourced [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]], based on [[GNOME]], called [[COSMIC]]. Pop!OS is developed by American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. === <u>Features</u> === * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace managment * Recover Partition tool * GUI toggle 20fd2aa4c656b730a73c10c45c00c8290d13336f 2481 2447 2025-06-19T09:52:23Z Atmois 13 Make image frameless wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{DistributionInfobox|title=Pop!_OS|image=[[File:Pop! OS Icon.svg|frameless]]|caption=The Pop!_OS logo|releasestatus=Maintained|packagemanager=[[Pacman]]|defaultdesktops=COSMIC|usagetype=Desktop|architectures=x86_64|website=Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX]|releasemodel=Rolling release}}Pop!_OS is a free and open-sourced [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]], based on [[GNOME]], called [[COSMIC]]. Pop!OS is developed by American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. === <u>Features</u> === * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle a2e5b15317ade01380a0893de6bfac0f094baf65 2 654 2435 2025-06-17T09:14:02Z Digit 165 Created page with "Eager to contribute to All Things Linux. :) == Briefest Human History == Born artist... this FOSS geeking thing came later. == Distro History == * Linux user since late 2003. * Started with SuSe linux, and used it as a base for 4 years of distro surfing on the side, then * sabayon linux as homebase for another 4 years of even heavier distro surfing on the side, * then pure gentoo for a couple years, * and even had aspirations of making own distro(s and meta-distr..." wikitext text/x-wiki Eager to contribute to All Things Linux. :) == Briefest Human History == Born artist... this FOSS geeking thing came later. == Distro History == * Linux user since late 2003. * Started with SuSe linux, and used it as a base for 4 years of distro surfing on the side, then * sabayon linux as homebase for another 4 years of even heavier distro surfing on the side, * then pure gentoo for a couple years, * and even had aspirations of making own distro(s and meta-distro collaboration frameworks and other high aspirations), before finding * [[bedrocklinux]], and all the 100s & 1000s distro surfing all but stopped(~), since no longer sought the best compromise single distro, as features from multiple distros can be combined in bedrocklinux. Typical core 4 strata in Digit's bedrock installs are [[Devuan]], [[Void]], [[Gentoo]] (any of which been used as installer to hijack), and [[artix]], for the AUR access. Also often featuring [[exherbo]], [[kiss]], [[carbs]], [[joborun]], [[xerolinux]], [[pclinuxos]], [[crux]], [[decibellinux]], and others. * took a couple years out of bedrock with just Devuan, to keep things simple during especially stressful time. == Biggest claims to fame or contributions to FOSS == # General FOSS advocacy everywhere, "it's the freedom". # Junior cat herding around various FOSS projects and teams. # The witch project (to be revived | decade dormant; 'life) # Digits Big Tiny Font Collection [https://notabug.org/Digit/dbtfc dbtfc] (nztt is Digit's daily driver font, which when sharing screenshots always gets polarised remarks). # Made the ascii big b for the bedrock neofetch\fastfetch # Coined the term strata/stratum, used in bedrocklinux. # General spray of other FOSS geekings yet to be completed to any level of presentability beyond the VAST scatter of unfinished projects, such as: * tabular boonad (an xmonad configuration or two), * halberd (a fanciful programming language somewhere betwixt dreamberd, haskell, fish, and spoken language (lojbanglish)), * portance (a message importance filtration system) * dtcp (Digits's terminal(/theme) colour picker). * wminizer (Window Manager Interactive Non-Interrupting Zero-downtime Editing Rotator ~ lets you switch wm without losing the entire X11 session and all programs running in it) * mergence (suite of lazy gentoo management wrapper tools) * various logo & mascot ideas for FOSS projects, and other artworks, desktop background wallpapers and such. * and more. == Hardware (+) == * Mostly old wacom penabled tablet thinkpads. * Old original (newly USB) wacom tablet * Kinesis Advantage (last version before the extra proprietary stuff got added to the version 2). * ... an eye on RISCV's future... * ... an eye on an 8bit retro-future. ... humanable. == Repos & Links & Things == [https://notabug.org/Digit/dbtfc notabug] a4d520679995af974403613594a7daf2a487fefc 2436 2435 2025-06-17T09:17:00Z Digit 165 /* Distro History */ or respins thereof nuance correction wikitext text/x-wiki Eager to contribute to All Things Linux. :) == Briefest Human History == Born artist... this FOSS geeking thing came later. == Distro History == * Linux user since late 2003. * Started with SuSe linux, and used it as a base for 4 years of distro surfing on the side, then * sabayon linux as homebase for another 4 years of even heavier distro surfing on the side, * then pure gentoo for a couple years, * and even had aspirations of making own distro(s and meta-distro collaboration frameworks and other high aspirations), before finding * [[bedrocklinux]], and all the 100s & 1000s distro surfing all but stopped(~), since no longer sought the best compromise single distro, as features from multiple distros can be combined in bedrocklinux. Typical core 4 strata in Digit's bedrock installs are [[Devuan]], [[Void]], [[Gentoo]] (any of which (or respins thereof) been used as installer to hijack), and [[artix]], for the AUR access. Also often featuring [[exherbo]], [[kiss]], [[carbs]], [[joborun]], [[xerolinux]], [[pclinuxos]], [[crux]], [[decibellinux]], and others. * took a couple years out of bedrock with just Devuan, to keep things simple during especially stressful time. == Biggest claims to fame or contributions to FOSS == # General FOSS advocacy everywhere, "it's the freedom". # Junior cat herding around various FOSS projects and teams. # The witch project (to be revived | decade dormant; 'life) # Digits Big Tiny Font Collection [https://notabug.org/Digit/dbtfc dbtfc] (nztt is Digit's daily driver font, which when sharing screenshots always gets polarised remarks). # Made the ascii big b for the bedrock neofetch\fastfetch # Coined the term strata/stratum, used in bedrocklinux. # General spray of other FOSS geekings yet to be completed to any level of presentability beyond the VAST scatter of unfinished projects, such as: * tabular boonad (an xmonad configuration or two), * halberd (a fanciful programming language somewhere betwixt dreamberd, haskell, fish, and spoken language (lojbanglish)), * portance (a message importance filtration system) * dtcp (Digits's terminal(/theme) colour picker). * wminizer (Window Manager Interactive Non-Interrupting Zero-downtime Editing Rotator ~ lets you switch wm without losing the entire X11 session and all programs running in it) * mergence (suite of lazy gentoo management wrapper tools) * various logo & mascot ideas for FOSS projects, and other artworks, desktop background wallpapers and such. * and more. == Hardware (+) == * Mostly old wacom penabled tablet thinkpads. * Old original (newly USB) wacom tablet * Kinesis Advantage (last version before the extra proprietary stuff got added to the version 2). * ... an eye on RISCV's future... * ... an eye on an 8bit retro-future. ... humanable. == Repos & Links & Things == [https://notabug.org/Digit/dbtfc notabug] 61349b0ab038fd4e4fdd626b2ba115b7f0f99eff 2440 2436 2025-06-17T09:30:08Z Digit 165 /* Distro History */ egalitarian pedagogy philosophy, important to add, kin spirit to atl. wikitext text/x-wiki Eager to contribute to All Things Linux. :) == Briefest Human History == Born artist... this FOSS geeking thing came later. == Distro History == * Linux user since late 2003. * Started with SuSe linux, and used it as a base for 4 years of distro surfing on the side, then * sabayon linux as homebase for another 4 years of even heavier distro surfing on the side, * then pure gentoo for a couple years, * and even had aspirations of making own distro(s and meta-distro collaboration frameworks and other high egalitarian aspirations around pedagogy and every user being a developer/contributor), before finding * [[bedrocklinux]], and all the 100s & 1000s distro surfing all but stopped(~), since no longer sought the best compromise single distro, as features from multiple distros can be combined in bedrocklinux. Typical core 4 strata in Digit's bedrock installs are [[Devuan]], [[Void]], [[Gentoo]] (any of which (or respins thereof) been used as installer to hijack), and [[artix]], for the AUR access. Also often featuring [[exherbo]], [[kiss]], [[carbs]], [[joborun]], [[xerolinux]], [[pclinuxos]], [[crux]], [[decibellinux]], and others. * took a couple years out of bedrock with just Devuan, to keep things simple during especially stressful time. == Biggest claims to fame or contributions to FOSS == # General FOSS advocacy everywhere, "it's the freedom". # Junior cat herding around various FOSS projects and teams. # The witch project (to be revived | decade dormant; 'life) # Digits Big Tiny Font Collection [https://notabug.org/Digit/dbtfc dbtfc] (nztt is Digit's daily driver font, which when sharing screenshots always gets polarised remarks). # Made the ascii big b for the bedrock neofetch\fastfetch # Coined the term strata/stratum, used in bedrocklinux. # General spray of other FOSS geekings yet to be completed to any level of presentability beyond the VAST scatter of unfinished projects, such as: * tabular boonad (an xmonad configuration or two), * halberd (a fanciful programming language somewhere betwixt dreamberd, haskell, fish, and spoken language (lojbanglish)), * portance (a message importance filtration system) * dtcp (Digits's terminal(/theme) colour picker). * wminizer (Window Manager Interactive Non-Interrupting Zero-downtime Editing Rotator ~ lets you switch wm without losing the entire X11 session and all programs running in it) * mergence (suite of lazy gentoo management wrapper tools) * various logo & mascot ideas for FOSS projects, and other artworks, desktop background wallpapers and such. * and more. == Hardware (+) == * Mostly old wacom penabled tablet thinkpads. * Old original (newly USB) wacom tablet * Kinesis Advantage (last version before the extra proprietary stuff got added to the version 2). * ... an eye on RISCV's future... * ... an eye on an 8bit retro-future. ... humanable. == Repos & Links & Things == [https://notabug.org/Digit/dbtfc notabug] e8f96bdda00e7fd485f0d925889d2de80436e524 2446 2440 2025-06-17T15:17:22Z Digit 165 /* Biggest claims to fame or contributions to FOSS */ wikitext text/x-wiki Eager to contribute to All Things Linux. :) == Briefest Human History == Born artist... this FOSS geeking thing came later. == Distro History == * Linux user since late 2003. * Started with SuSe linux, and used it as a base for 4 years of distro surfing on the side, then * sabayon linux as homebase for another 4 years of even heavier distro surfing on the side, * then pure gentoo for a couple years, * and even had aspirations of making own distro(s and meta-distro collaboration frameworks and other high egalitarian aspirations around pedagogy and every user being a developer/contributor), before finding * [[bedrocklinux]], and all the 100s & 1000s distro surfing all but stopped(~), since no longer sought the best compromise single distro, as features from multiple distros can be combined in bedrocklinux. Typical core 4 strata in Digit's bedrock installs are [[Devuan]], [[Void]], [[Gentoo]] (any of which (or respins thereof) been used as installer to hijack), and [[artix]], for the AUR access. Also often featuring [[exherbo]], [[kiss]], [[carbs]], [[joborun]], [[xerolinux]], [[pclinuxos]], [[crux]], [[decibellinux]], and others. * took a couple years out of bedrock with just Devuan, to keep things simple during especially stressful time. == Biggest claims to fame or contributions to FOSS == # Staying out of the way. # General FOSS advocacy everywhere, "it's the freedom". # Junior cat herding around various FOSS projects and teams. # The witch project (to be revived | decade dormant; 'life) # Digits Big Tiny Font Collection [https://notabug.org/Digit/dbtfc dbtfc] (nztt is Digit's daily driver font, which when sharing screenshots always gets polarised remarks). # Made the ascii big b for the bedrock neofetch\fastfetch # Coined the term strata/stratum, used in bedrocklinux. # General spray of other FOSS geekings yet to be completed to any level of presentability beyond the VAST scatter of unfinished projects, such as: * tabular boonad (an xmonad configuration or two), * halberd (a fanciful programming language somewhere betwixt dreamberd, haskell, fish, and spoken language (lojbanglish)), * portance (a message importance filtration system) * dtcp (Digits's terminal(/theme) colour picker). * wminizer (Window Manager Interactive Non-Interrupting Zero-downtime Editing Rotator ~ lets you switch wm without losing the entire X11 session and all programs running in it) * mergence (suite of lazy gentoo management wrapper tools) * various logo & mascot ideas for FOSS projects, and other artworks, desktop background wallpapers and such. * and more. == Hardware (+) == * Mostly old wacom penabled tablet thinkpads. * Old original (newly USB) wacom tablet * Kinesis Advantage (last version before the extra proprietary stuff got added to the version 2). * ... an eye on RISCV's future... * ... an eye on an 8bit retro-future. ... humanable. == Repos & Links & Things == [https://notabug.org/Digit/dbtfc notabug] 5a907830611d3f2d7c2e52a52bc98aaa63810031 0 263 2437 2200 2025-06-17T09:19:21Z Hog 161 Added Links wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.99.0, 2024-10-24 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|thumb|The Hyfetch Pride Month easter egg.]] Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your [[Operating System|operating system]], [[:Category:Software|software]] and [[hardware]] with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch</ref> === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. <references /> [[Category:Software]] 02b4b049bed60a9a09b9ce92caa674e68dc9fa78 0 166 2441 2021 2025-06-17T10:32:54Z Hog 161 Added Citations wikitext text/x-wiki A term commonly used across any Linux community<ref>[https://www.youtube.com/watch?v=LxuYnFD7brY TechOverTea] imported on 17th June 2025</ref>, "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life. <ref>Merriam-Webster Dictionary. [https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of [[Linux]] and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system.<ref>[https://www.techtarget.com/searchsecurity/answer/How-can-we-detect-and-uninstall-bloatware "What is Bloatware?"] TechTarget.com ,Imported 17th June 2025</ref> <references /> [[Category:Terminology]] 6ea74343a7d84e36dd0d984cc906a7dfa7279594 0 441 2442 1555 2025-06-17T10:44:47Z Hog 161 Added Links wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,") <ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU] , The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref>is a dedicated organization for free [[:Category:Software|software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone [[Operating System|operating system]] because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or [[Proprietary software|proprietary]]: A few are GNU/[[Linux]], MacOS, [[Unix|Unix-based]]/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the [[proprietary software]] of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe. </ref> == Included Software / Components == [[File:Gnu compiler collection-logo-1.png|alt=This logo depicts a Bull shaped animal jumping out of an egg, in black text that displays the letters G, C, C|left|thumb|224x224px|A logo of the GCC.]] As of June 2024, the GNU project currently holds 394 active [[packages]], but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. Overall, these components are in many operating systems, mainly because of how easy GCC is to access for any developer. Because of Richard Stallman, he was able to open source the variety of tools and software developed for the GNU project and in turn, pushed forward for the movement of open and free software for all.<ref name=":0" /> == History of GNU == [[File:RichardStallman.jpg|alt=A Picture of Richard Matthew Stallman in 2024|thumb|341x341px|A Picture of Richard Matthew Stallman in 2024]] Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref name=":0">[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible [[architecture]] because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs. <ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> <references /> 4f8fdae7f54d17b00575f0dfe5eccdb7ffc8609d 0 645 2443 2385 2025-06-17T10:54:13Z Hog 161 Added Links and images wikitext text/x-wiki [[File:Operating system placement.svg|thumb|How Drivers allow different parts of the computer to interact]] A driver is a computer [[:Category:Software|program]] that controls or operates a type of device connected to the computer. A driver provides a software interface to [[hardware]] devices, enabling [[Operating System|operating systems]] and other computer programs to access functions without needing to know precise details about the hardware being used. A driver communicates with the device through the computer bus. Some Drivers are [[Open-Source]]. Some example of these are [[AMD]] Graphic Drivers. 35962d760bf0992d909b8da255ad2937d8d9a677 2 655 2444 2025-06-17T10:55:41Z Hog 161 Made me>:3 wikitext text/x-wiki [[File:Sus scrofa f domesticus - Réserve africaine de Sigean 01.jpg|thumb|Photo of a hog i like]] Oink Oink! I probably fixed your article bozo. cffdfb4f5f8f10575bdad29e40a86fbb5799353f 0 8 2445 2169 2025-06-17T11:00:09Z Hog 161 added RTFM wikitext text/x-wiki {{Work In Progress}} == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building]] * [[Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 8e8589bab0903467863a4ec30fb0a69759371e62 0 656 2448 2025-06-18T07:41:52Z Hog 161 To be fixed. wikitext text/x-wiki Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pi's and other micro computers {{DistributionInfobox|title=Batocera|image=[[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]]|caption=Batocera Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|usagetype=Desktop|architectures=x86_64, Rpi4, Rpi5, RK3326 Handhelds|website=[https://batocera.org/ batocera.org]}} 5eb485aae3449569ef92edc593455449d23d8e0a 2449 2448 2025-06-18T07:46:02Z Hog 161 someone please fix thiss wikitext text/x-wiki Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pi's and other micro computers {{DistributionInfobox|title=Batocera|image=[[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]]|caption=Batocera Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|architectures=x86_64, Rpi4, Rpi5|website=[https://batocera.org/ batocera.org]}} 427e9790eaf0fe6b747b442eb1e59963625475b0 2459 2449 2025-06-18T08:34:09Z Atmois 13 fix infobox variables wikitext text/x-wiki {{DistributionInfobox |title=Batocera |image=placeholder |caption=Batocera Logo |releasestatus=Maintained |releasemodel=Rolling Release |packagemanager=placeholder |defaultdesktops=placeholder |usagetype=placeholder |architectures=x86_64, Rpi4, Rpi5 |website=[https://batocera.org/ batocera.org] }} Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pi's and other micro computers c78e4ee4a61c39b895b6a1c03f370d9f178177ee 2460 2459 2025-06-18T08:36:49Z Hog 161 added logo wikitext text/x-wiki {{DistributionInfobox |title=Batocera |image=[[file:Batocera-logo-art.png]] |caption=Batocera Logo |releasestatus=Maintained |releasemodel=Rolling Release |packagemanager=placeholder |defaultdesktops=placeholder |usagetype=placeholder |architectures=x86_64, Rpi4, Rpi5 |website=[https://batocera.org/ batocera.org] }} Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pi's and other micro computers 74f6792889484ce1314d270493be31be252ac264 2461 2460 2025-06-18T08:38:06Z Hog 161 replaced placeholders to the best of my knowledge wikitext text/x-wiki {{DistributionInfobox |title=Batocera |image=[[file:Batocera-logo-art.png]] |caption=Batocera Logo |releasestatus=Maintained |releasemodel=Rolling Release |packagemanager=pacman |defaultdesktops=No Desktop |usagetype=placeholder |architectures=x86_64, Rpi4, Rpi5 |website=[https://batocera.org/ batocera.org] }} Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pi's and other micro computers 5cd16d85d7d213c8a5504abc88fbf738b3a0628b 0 534 2450 2062 2025-06-18T07:52:11Z Hog 161 ignore this im creating a guide wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]. Installation instructions should be on their own page.}} {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|firstrelease=v0.1.0-alpha.1|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1" /> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading config == [[Guide:Installating Niri|Guide:Installation]] == Below you will find installation instructions for some popular linux distributions. If your distribution is not listed below, have a look at niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. <syntaxhighlight> # dnf copr enable yalter/niri # dnf install niri </syntaxhighlight> === Arch Linux === To download the latest stable release, run the following command: <syntaxhighlight> # pacman -S niri </syntaxhighlight> If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: <syntaxhighlight> $ yay -S niri-git </syntaxhighlight> === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in '''/etc/nixos/configuration.nix''' <syntaxhighlight lang="nix"> {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; # In case you want to override niri. }; } </syntaxhighlight> === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: <syntaxhighlight> # pkg install niri </syntaxhighlight> === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. <syntaxhighlight> # zypper in niri </syntaxhighlight> Alternatively, you can install it with '''opi''' as well. <syntaxhighlight> # opi niri </syntaxhighlight> === Void Linux === You can install niri on Void with '''xbps'''. <syntaxhighlight> # xbps-install -S niri </syntaxhighlight> === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file.<ref name=":1" /> While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here<ref name=":1">https://github.com/YaLTeR/niri/wiki/Important-Software</ref>. * '''Terminal:''' alacritty * '''App Launcher:''' fuzzel * '''Bar:''' waybar * '''Lockscreen:''' swaylock * '''Notifications:''' mako * '''Wallpapers:''' swaybg In addition to these, please install the packages below to ensure app functionality<ref name=":1" />. Do note that the list of packages below doesn't apply to all distributions. <syntaxhighlight> swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite </syntaxhighlight> == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri<ref name=":2">https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup</ref>, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a '''niri.service.wants''' folder, which is a special systemd folder. Any services linked there will be started together with '''niri.service''' (which is a systemd unit used by niri when running as a session). <syntaxhighlight> $ mkdir -p ~/.config/systemd/user/niri.service.wants </syntaxhighlight> '''mako''' and '''waybar''' provide systemd units out of the box, so you can simply symlink them into the '''niri.service.wants''' folder.<ref name=":2" /> <syntaxhighlight> $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> '''swaybg''' and '''swayidle''' do not provide a service so we will make our own. Let's start with '''swaybg'''. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into '''~/.config/systemd/user/swaybg.service''', replacing LakeSide.png with your actual wallpaper. Note that '''%h''' means your home folder.<ref name=":2" /> <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure </syntaxhighlight> After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to '''niri.service.wants'''. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> Similarly for '''swayidle''', put the following into '''~/.config/systemd/user/swayidle.service'''. <syntaxhighlight lang="systemd"> [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure </syntaxhighlight> Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. <syntaxhighlight> $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ </syntaxhighlight> That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the '''spawn-at-startup''' config option to do so<ref>https://github.com/YaLTeR/niri/wiki/Configuration:-Miscellaneous</ref>. In this case, if you desire XWayland, you may add the following to your configuration. <syntaxhighlight> spawn-at-startup "xwayland-satellite" </syntaxhighlight> You may also automatically start <code>swaybg</code> in a similar manner. <syntaxhighlight> spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" </syntaxhighlight> For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. <references /> 68d60e194a82f17796bf89704d518817cf17e453 2452 2450 2025-06-18T07:57:56Z Hog 161 Guide can now be found elsewhere wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example niri rice|title=niri|releasestatus=Maintained|firstrelease=v0.1.0-alpha.1|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">https://github.com/YaLTeR/niri/wiki/Important-Software</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading <references /> 604dbe15a5d4382c77fafe3686e46dee4d672ea7 3000 658 2458 2025-06-18T08:09:55Z Hog 161 corrected name by creating new page(please purge old one) wikitext text/x-wiki If your distribution is not listed below, have a look at Niri's [https://repology.org/project/niri/versions Repology page] and the [https://github.com/YaLTeR/niri/wiki/Getting-Started Getting Started] page. If niri is not packaged for your distribution, please follow the [https://github.com/YaLTeR/niri/wiki/Getting-Started#building build instructions] on niri's github repository. === Fedora === Fedora users may install niri using the following method. # dnf copr enable yalter/niri # dnf install niri === Arch Linux === To download the latest stable release, run the following command: # pacman -S niri If you would like to install the unstable git release, you can install it with an AUR helper like yay or paru: $ yay -S niri-git === NixOS === To install niri on NixOS, add the following to you nix configuration file, which is usually located in /etc/nixos/configuration.nix {pkgs, ...}: { programs.niri = { enable = true; package = pkgs.niri; ''# In case you want to override niri.'' }; } === FreeBSD === Niri is available as a FreeBSD port. You can install it with the command below: # pkg install niri === OpenSUSE Tumbleweed and Slowroll === Run the command below to install niri on OpenSUSE Tumbleweed and Slowroll. The package is available for OpenSUSE Leap as well, but it is outdated and not recommended to install. # zypper in niri Alternatively, you can install it with opi as well. # opi niri === Void Linux === You can install niri on Void with xbps. # xbps-install -S niri === Configurability === Niri configration is done in <code>$XDG_CONFIG_HOME/niri/config.kdl</code>. It provides the ability to customise keybindings, shaders, window layout among other options. [https://github.com/YaLTeR/niri/wiki/Configuration:-Overview More information will be found in the official documentation for Niri.] == Important and recommended software == Niri uses alacritty as it's default terminal, swaylock as it's lock screen, and fuzzel as it's default app launcher. However, you can easily customize what default apps are used in the configuration file. While you can pick and choose what packages you use, the "Example Setup" section will we using the apps listed here. * Terminal: alacritty * App Launcher: fuzzel * Bar: waybar * Lockscreen: swaylock * Notifications: mako * Wallpapers: swaybg In addition to these, please install the packages below to ensure app functionality. Do note that the list of packages below doesn't apply to all distributions. swayidle xdg-desktop-portal-gtk xdg-desktop-portal-gnome gnome-keyring plasma-polkit-agent xwayland-satellite == Example Systemd Setup == To make Niri more like a usable desktop environment, we will need to make sure that all the programs listed in the previous section start alongside niri, which we will do with systemd. Here we will cover how to set up mako, waybar, swaybg, and swayidle. Start by creating a niri.service.wants folder, which is a special systemd folder. Any services linked there will be started together with niri.service (which is a systemd unit used by niri when running as a session). $ mkdir -p ~/.config/systemd/user/niri.service.wants mako and waybar provide systemd units out of the box, so you can simply symlink them into the niri.service.wants folder. $ ln -s /usr/lib/systemd/user/mako.service ~/.config/systemd/user/niri.service.wants/ $ ln -s /usr/lib/systemd/user/waybar.service ~/.config/systemd/user/niri.service.wants/ swaybg and swayidle do not provide a service so we will make our own. Let's start with swaybg. Since we need to pass the wallpaper as a command-line argument, we can use a custom systemd service that will do that for us. Put the following into ~/.config/systemd/user/swaybg.service, replacing LakeSide.png with your actual wallpaper. Note that %h means your home folder. [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png" Restart=on-failure After that, run <code>systemctl --user daemon-reload</code> so that systemd pick up the changes, and then symlink it to niri.service.wants. $ ln -s ~/.config/systemd/user/swaybg.service ~/.config/systemd/user/niri.service.wants/ Similarly for swayidle, put the following into ~/.config/systemd/user/swayidle.service. [Unit] PartOf=graphical-session.target After=graphical-session.target Requisite=graphical-session.target [Service] ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f' Restart=on-failure Now, run <code>systemctl --user daemon-reload</code> again, and then symlink it just like before. $ ln -s ~/.config/systemd/user/swayidle.service ~/.config/systemd/user/niri.service.wants/ That's it! now these programs will start and end alongside niri. If there are some more programs that don't come with systemd units out of the box, you now know how to create one yourself. == Setting up niri using the configuration file instead of systemd == If you prefer to use niri's config file instead of systemd, you can utilize the spawn-at-startup config option to do so. In this case, if you desire XWayland, you may add the following to your configuration. spawn-at-startup "xwayland-satellite" You may also automatically start <code>swaybg</code> in a similar manner. spawn-at-startup "swaybg" "-m" "fill" "-i" "/home/user/Pictures/LakeSide.png" For how simple this approach seems in comparison to setting up systemd services, it may be harder to monitor than systemd. e36be82e64705a053a49a50b1ffc7c034cd28914 0 174 2462 2082 2025-06-18T08:50:29Z Hog 161 updated a tiny bit, unsure if counts as complete wikitext text/x-wiki {{Cleanup|Incomplete page}}[[File:Debian-Installer 10 Tasksel.svg|alt=Debian TUI installer|thumb|Debian 10 installation, which uses a TUI installer]] A '''TUI''' (Terminal User Interface) generally refers to an application that solely exists within the terminal as a text-based application - this means that all of its content is rendered using letters and other unique characters to create a graphical interface. [REFERENCE POSSIBLE]. Most Unix-Based Operating systems support virtual consoles. [[Category:Terminology]] cd3817a5afcf8ac62f35a483c9a3bfc77440921c 2480 2462 2025-06-19T09:50:19Z Atmois 13 Add citaiton needed wikitext text/x-wiki {{Cleanup|Incomplete page}}[[File:Debian-Installer 10 Tasksel.svg|alt=Debian TUI installer|thumb|Debian 10 installation, which uses a TUI installer]] A '''TUI''' (Terminal User Interface) generally refers to an application that solely exists within the terminal as a text-based application - this means that all of its content is rendered using letters and other unique characters to create a graphical interface.{{Citation needed}} Most Unix-Based Operating systems support virtual consoles. [[Category:Terminology]] d3531b168b77c4f1b3bb2a70294e5549edee2a26 0 354 2463 2401 2025-06-18T08:56:23Z Hog 161 updated and added reference wikitext text/x-wiki {{MascotInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy|222px]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. Puffy resembles a puffer-fish and has been the mascot since June 15th, 2000.<ref>https://www.openbsd.org/27.html</ref> [[File:Puffyanim.gif|thumb|99x99px|Animated Puffy Render]] [[Category:Mascots]] 8bbedac0d4bf3f97bad9762c904436923a524779 0 659 2464 2025-06-18T09:16:06Z Hog 161 Created page with info box. will continue later wikitext text/x-wiki {{DistributionInfobox|title=ChromeOS|image=[[File:Chromium_Logo.svg]]|caption=ChromiumOs Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=APT|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website=[chromeos https://chromeos.google/]}} 56559370917b540880fe00dee70ebb7a544ccaf6 2465 2464 2025-06-18T10:31:15Z Hog 161 added a small amount of information wikitext text/x-wiki {{DistributionInfobox|title=ChromeOS|image=[[File:Chromium_Logo.svg]]|caption=ChromiumOs Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=APT|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website=[chromeos https://chromeos.google/]}}ChromeOS (ChromiumOS) is a Unix-Based Linux distribution designed and developed by Google in 2009. ChromeOS is completely open-source<ref>http://source.chromium.org/chromiumos</ref>. f1f9868f34b94f53b8a4d5c508518e6446a15c35 2477 2465 2025-06-19T09:47:02Z Atmois 13 Fix link syntax and make logo frameless wikitext text/x-wiki {{DistributionInfobox|title=ChromeOS|image=[[File:Chromium_Logo.svg|frameless]]|caption=ChromiumOs Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=APT|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website=[https://chromeos.google/ chromeos]}}ChromeOS (ChromiumOS) is a Unix-Based Linux distribution designed and developed by Google in 2009. ChromeOS is completely open-source<ref>http://source.chromium.org/chromiumos</ref>. 856eeecdd8bc1ef21f8a76d5d655eb1120d9e446 1 660 2466 2025-06-18T10:32:05Z Hog 161 /* Can someone Scale the logo down? */ new section wikitext text/x-wiki == Can someone Scale the logo down? == Unable to do it myself for some reason. [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 10:32, 18 June 2025 (UTC) db56f76693b743db1051d7d77f817149ccd8332c 2478 2466 2025-06-19T09:47:12Z Atmois 13 /* Can someone Scale the logo down? */ Reply wikitext text/x-wiki == Can someone Scale the logo down? == Unable to do it myself for some reason. [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 10:32, 18 June 2025 (UTC) :fixed. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 09:47, 19 June 2025 (UTC) 339fc54e9cdcbdb12068aa11759f4571b963f9f5 2479 2478 2025-06-19T09:47:45Z Atmois 13 edit comment wikitext text/x-wiki == Can someone Scale the logo down? == Unable to do it myself for some reason. [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 10:32, 18 June 2025 (UTC) :fixed. you can use the "frameless" format for it [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 09:47, 19 June 2025 (UTC) 2d895534f26286b426b712aa3cfa81a69a2e7d97 0 661 2467 2025-06-18T10:50:05Z Hog 161 Created page with "Kali Linux is a open-sourced [[Linux Distributions|distribution]] specially designed for hacking .{{DistributionInfobox|title=Kali Linux|image=[[File:Kali-dragon-icon.svg]]|caption=Kali Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Apt]]|defaultdesktops=[[Xfce]], [[GNOME]], [[KDE Plasma]]|usagetype=Desktop, Mobile, USB|architectures=x86_64, ARM, ARM64, Cloud|website=[https://www.kali.org/ Kali.org]}}" wikitext text/x-wiki Kali Linux is a open-sourced [[Linux Distributions|distribution]] specially designed for hacking .{{DistributionInfobox|title=Kali Linux|image=[[File:Kali-dragon-icon.svg]]|caption=Kali Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Apt]]|defaultdesktops=[[Xfce]], [[GNOME]], [[KDE Plasma]]|usagetype=Desktop, Mobile, USB|architectures=x86_64, ARM, ARM64, Cloud|website=[https://www.kali.org/ Kali.org]}} 5f45d1dc80dc7d85e143b9d3b3cf9e7eb1478634 2468 2467 2025-06-18T11:32:55Z Hog 161 added a bit more information wikitext text/x-wiki {{DistributionInfobox|title=Kali Linux|image=[[File:Kali-dragon-icon.svg]]|caption=Kali Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Apt]]|defaultdesktops=[[Xfce]], [[GNOME]], [[KDE Plasma]]|usagetype=Desktop, Mobile, USB|architectures=x86_64, x86, armel, armhf|website=[https://www.kali.org/ Kali.org]}}Kali Linux is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, Digital forensics, and penetration testing. fd7cc0b78c189e79492de14d89e64892bcf8e3e7 2476 2468 2025-06-19T09:46:14Z Atmois 13 Make logo frameless wikitext text/x-wiki {{DistributionInfobox|title=Kali Linux|image=[[File:Kali-dragon-icon.svg|frameless]]|caption=Kali Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Apt]]|defaultdesktops=[[Xfce]], [[GNOME]], [[KDE Plasma]]|usagetype=Desktop, Mobile, USB|architectures=x86_64, x86, armel, armhf|website=[https://www.kali.org/ Kali.org]}}Kali Linux is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, Digital forensics, and penetration testing. 6739dfe9dd888de875b14f680730814fc10d2621 0 586 2469 1995 2025-06-18T11:36:28Z Hog 161 Added Links wikitext text/x-wiki {{MascotInfobox | title = Xenia (Linux Fox) | image = [[File:Xenia the Linux Fox.gif]] | caption = The original design of Linux Fox, created by Al Mackey in 1996 }} Xenia was a candidate logo and [[:Category:Mascots|mascot]] for the [[Linux]] project. She was a competitor to [[Tux]], who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds.) <ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ Why the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!], Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson. <ref>[https://archive.is/wYsFh Penguins and Other Things], Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on [[Gentoo]].<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> <references /> [[Category:Mascots]] fe98d962946e5019d094b23f3f429b3eaea001cb 0 250 2470 2171 2025-06-18T11:53:29Z Hog 161 added clean up tag wikitext text/x-wiki {{Cleanup|Instructions need to be split onto their own page under the Guides namespace}}{{Cleanup|Incomplete page}}[[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry{{Citation needed}} - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. * Keep in mind the philosophy of true freedom on the internet and digitally{{Citation needed}} - exercise your freedoms as you see fit using this technology at your own whims, but practice good ethics. == Ana/Miniconda Setup == ... (tomorrow's problem) == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU -''' considering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> == Stable Diffusion Setup - WebUI == According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> [[Category:Guides]] 19cf5c45425cbdb0e8934fe809ae825b7ac8733c 0 428 2471 2363 2025-06-18T12:49:34Z Hog 161 Fixed Links wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} Man or Man pages is a [[TUI|command-line]] utility available on [[UNIX]] and [[UNIX-like]] [[Operating System|operating systems]] that provides [[documentation]] for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format]] and [[games]]. The Man pages are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a Man page the user can enter the following into their [[TUI|terminal]]: man <command_name> <ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> For example to read the Man page on [[Pacman]] you would enter the following: man pacman == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == '''Changing the Pager''' == The program that displays the manpage is stored in the `MANPAGER` or `PAGER` environment variable. By default, it uses `less`. Alternatively, the `-P` or `--pager` option can be used. <ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using `export PAGER="program-to-use"` or added to the `.bashrc` or `.zshrc` file for persistence. For example, using Neovim as the pager would be `export PAGER="nvim +Man!"`, `export PAGER="nano -"` to use Nano, and `export PAGER="less"` to revert it to less. For Fish shell, use `set -x PAGER program-to-use` to set it for the current session, and `set -Ux PAGER program-to-use` to set it globally. <ref>https://fishshell.com/docs/current/faq.html</ref> <references /> 098a9609d8618b6c0bc3493d96e3e7ed50fe4ee5 0 516 2472 2081 2025-06-19T08:38:27Z Hog 161 added a link. will move guide later wikitext text/x-wiki {{Cleanup|Instructions should be seperated into its own Guide page}} {{Needs_Citations}} == Understanding Systemd == Systemd is an init system and service manager used by many modern [[Linux Distributions|Linux distributions]]. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here’s how Systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': Systemd provides a unified system for managing services, devices, logs, and even network interfaces. * '''Dependency Management''': Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': Systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in Systemd == Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit’s dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''Systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''Systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''Systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential Systemd Commands == Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash">systemctl start service-name</syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash">systemctl stop service-name</syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash">systemctl restart service-name</syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash">systemctl enable service-name</syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash">systemctl disable service-name</syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the `/lib/systemd/system/` directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there. * Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. '''Runtime Directory''' The `/run/systemd/system/` directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File '''sudo nano /etc/systemd/system/daily-script.service''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File '''sudo nano /etc/systemd/system/daily-script.timer''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer '''sudo systemctl enable daily-script.timer''' '''sudo systemctl start daily-script.timer''' 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: '''systemctl list-timers''' This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With OnCalendar, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from `/lib/systemd/system/` to `/etc/systemd/system/` and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with `.d`. Example: To modify `dummy.service`, create a folder named `dummy.service.d` in `/etc/systemd/system/`. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a `.conf` file to specify your changes. Example: `/etc/systemd/system/dummy.service.d/custom.conf`. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. /etc/systemd/system/ (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. /run/systemd/system/ (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. /lib/systemd/system/ (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. '''systemctl status service-name''' * Displays the status of a specific service, including whether it's running and any associated error messages. 2. '''journalctl -u service-name''' * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. '''systemctl list-units --failed''' * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. '''systemctl daemon-reload''' * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. 01dfbaeaba186b3137e76bfb5fe54da83594a5fa 3000 471 2473 2020 2025-06-19T08:44:26Z Hog 161 Added Links wikitext text/x-wiki {{Guide Warning}} == Best SSH Security Practices == The best SSH practices can be summarized into two main principles: # Keeping unauthorized users out of your system. # Making sure potential attackers don't even know your system exists. This guide will teach you the best SSH security practices. ==== SSH Programs: Dropbear vs OpenSSH ==== There are two primary SSH programs used on [[Linux Distributions|Linux]]/[[Unix|Unix-based]] systems: '''Dropbear''' and '''OpenSSH'''. In this guide, we will focus on '''OpenSSH'''. ==== Installing SSH ==== Installing SSH varies by system. Below are common [[Package Manager|package managers]] where you can download SSH: '''[[Debian]]/[[Ubuntu]]-based systems:'''<syntaxhighlight lang="bash"> sudo apt install openssh-server </syntaxhighlight> [[Red Hat Enterprise Linux|Red Hat]]/[[CentOS]]/[[Fedora]]-based systems: <syntaxhighlight>sudo dnf install openssh-server</syntaxhighlight> [[Arch Linux]]-based systems: <syntaxhighlight>sudo pacman -S openssh</syntaxhighlight> [[OpenSUSE]]-based systems: <syntaxhighlight>sudo zypper install openssh</syntaxhighlight> [[macOS]] (via [[Homebrew]]): <syntaxhighlight>brew install openssh</syntaxhighlight> === Securing the OpenSSH Server === ==== Changing the Port ==== By default, SSH runs on '''port 22'''. While leaving it on port 22 is acceptable, your system will be easily detected by port scanners as running SSH. To mitigate this, you can change the port. The SSH configuration file is typically located at '''/etc/ssh/sshd_config''' and is usually owned by the root user. To edit it, you must open it as root, using either '''sudo''' or '''doas'''. Once you open the '''sshd_config''' file, you should see the following line: <syntaxhighlight>#Port 22</syntaxhighlight> To modify the port, uncomment the line by removing the `#` at the beginning and then change the '''22''' to any number between '''100''' and '''65534'''. You will need to uncomment any line you change for it to come into effect. For example: <syntaxhighlight>Port 2345</syntaxhighlight> Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> Once the change is made, you have successfully modified the port. To log in using the new port, use the following command: <syntaxhighlight><username>@<address> -p 2345</syntaxhighlight> ==== Key Authentication ==== Key-based authentication is a much safer alternative to using a password. Instead of entering a password to log in, you'll use a key pair: a '''private key''' that stays on your system and a '''public key''' that you store on the server. ===== How Key Authentication Works ===== Imagine you have a door with a lock. The private key is like your physical key, while the public key is the lock on the door. When the correct key is inserted, the door unlocks. This is essentially how key authentication works. * Prevents brute-force attacks. * Allows passwordless login (like Single Sign-On). * Requires each user to have a unique key pair. ==== Setting up Key Authentication ==== ===== Generating the Key Files ===== 1. On any Unix/Linux system, type the following command: <syntaxhighlight>ssh-keygen</syntaxhighlight> 2. You will be prompted to specify where to save the key files: <syntaxhighlight> Generating public/private ed25519 key pair. Enter file in which to save the key (/home/name/.ssh/id_ed25519): </syntaxhighlight> '''Example:''' <syntaxhighlight> Enter file in which to save the key (/home/name/.ssh/id_ed25519): /home/name/Desktop/key </syntaxhighlight> This will save both the public and private key files on your desktop under the name '''key'''. 3. You will be asked to set a passphrase for the key. If you trust the environment where the key is stored, you can leave it empty by pressing '''Enter'''. Alternatively, you can set a passphrase to add an extra layer of security. <syntaxhighlight> Enter passphrase for "/home/name/Desktop/key" (empty for no passphrase): </syntaxhighlight> 4. Once complete, the keys will be saved in the specified location: <syntaxhighlight> Your identification has been saved in /home/name/Desktop/key Your public key has been saved in /home/name/Desktop/key.pub The key fingerprint is: SHA256:I60X50p2/VwZ6MHhEqx8rWNse0pC5/vewW1i4tLufQ8 name@pc The key's randomart image is: +--[ED25519 256]--+ | | | . | | o . | | .. . = o | | . S+.+ * . | | o.==.+ o +| | . +.oXo.E++| | + o*.=B.=o| | . BOo+oo| +----[SHA256]-----+ </syntaxhighlight> Do not worry about the '''randomart''' as it has no functional purpose. 5. You now have two files: * key – This is your '''private key''' (keep this secure and never share it). * key.pub – This is your '''public key''' (place this on the server). The private key should stay on the machine you will use to access the server. ===== Securing the Server with Key Authentication ===== 1. Log in to the server you want to protect with key authentication. 2. Open the SSH configuration file: <syntaxhighlight> sudo nano /etc/ssh/sshd_config </syntaxhighlight> 3. Modify the following lines: <syntaxhighlight> #PermitRootLogin prohibit-password #PasswordAuthentication yes </syntaxhighlight> to: <syntaxhighlight> PermitRootLogin no PasswordAuthentication no </syntaxhighlight> This prevents root login over SSH, disables password login and forces key-based authentication. 4. Save and exit the file. 5. Go to the home directory of the user you wish to secure with key authentication. Create the '''.ssh''' directory (if it doesn't exist), then create the '''authorized_keys''' file inside it: <syntaxhighlight> mkdir -p ~/.ssh nano ~/.ssh/authorized_keys </syntaxhighlight> Paste the entire contents of the `.pub` file into this document and save it. 6. Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> '''DO NOT LOG OUT UNTIL YOU CONFRIM THE CONFIGURATION IS CORRECT TO AVOID BEING LOCKED OUT.''' 7. Open another [[TUI|terminal]] window on the machine you will use to SSH into the server and test the connection: <syntaxhighlight> ssh <user>@<address> -i /location/to/private/key/file </syntaxhighlight> If you can log in without a password, the key authentication system is correctly configured! 040e861ae6a3bd67cb2c842616b8e4a263dfa1d4 0 198 2474 2384 2025-06-19T08:46:26Z Hog 161 added CentOS wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[CentOS]] |CentOS is a discontinued Linux distribution that provided a free and open-source community-supported computing platform |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] a74ca31dcf82433fd31827b615f9fdc85dbe1f25 2482 2474 2025-06-19T10:53:26Z Hog 161 punctuation wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[CentOS]] |CentOS is a discontinued Linux distribution that provided a free and open-source community-supported computing platform. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] a65b752006d3b97c1a6fa568238e457bcc80f1c3 0 650 2475 2412 2025-06-19T09:14:24Z Hog 161 added links wikitext text/x-wiki {{SoftwareInfobox | image=[[File:Enlightenment logo.svg|Enlightenment_logo]] | caption = Enlightenment logo | title=Enlightenment | releasestatus=Maintained | lastrelease=0.27.1, March 17, 2025 | firstrelease=0.13.2, January 18, 1998 | languages=[[C]], [[ELF]] | developers=Enlightenment Foundation | website=[https://www.enlightenment.org/, enlightenment.org/] }} [https://www.enlightenment.org/ Enlightenment] is a [[Desktop Environments|Desktop Environment]] and [[Window Manager]] for [[Linux]] and other [[Unix|Unix-like]] [[Operating System|operating systems]], such as [[BSD]] derivatives.<ref name=":0">[https://www.enlightenment.org/about Enlightenment About Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref>. Originally created by Carsten Haitzler in the late 90s with the philosophy "that users should be given as much control as possible."<ref>[https://www.enlightenment.org/about-enlightenment| About Enlightenment Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref>. === Features === Enlightenment has many key features as a [[graphical desktop]] including its own set of graphical and system libraries known as the "Enlightenment Foundation Libraries". Designed to be portable and efficient while also being easy to use on various devices including touch devices even being used in Samsung devices.<ref name=":0" /> * Support for both [https://www.x.org/wiki/ X11] and experimental [https://wayland.freedesktop.org/ Wayland] support. * A hand optimized software rendering compositor. * Very low memory requirements. * The ability to configure everything graphically. * Touch gestures * Window Management Features ** Virtual desktops. ** Optional window tiling. ** Customizable mouse and keyboard bindings. ** And many more modules. <references /> [[Category:Desktop Environments]] 2797ffdceb8fa9b28f43863d6ef9fa44a5493c36 0 622 2483 2410 2025-06-19T12:06:02Z Hog 161 Created VERY rough edit for Desktop Environment. will appreciate some help but i will finish at a later date wikitext text/x-wiki This page is in urgent need of work, below is a list of pages in the category. A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a GUI or TUI. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets. {| class="wikitable" |+ !Desktop Environment !Description |- |[[File:Budgie-Screenshot-Raven-RU.png|thumb|399x399px|[[Budgie]]]] | |- |[[File:Cinnamon 5.2.png|thumb|399x399px|[[Cinnamon]]]] | |- |[[File:Enlightenment-screenshot-2021.png|thumb|392x392px|[[Enlightenment]]]] | |- |[[File:GNOME 43.png|thumb|400x400px|[[GNOME]]]] | |- |[[File:Ubuntu MATE 22.10.png|thumb|400x400px|[[MATE]]]] | |- |[[File:Openbox 3.4.10 default.png|thumb|400x400px|[[Openbox]]]] | |- |[[File:KDE Plasma 6.3 desktop screenshot.webp|thumb|400x400px|[[Plasma]]]] | |- |[[File:Trinity R.14.1.3 screenshot.png|thumb|400x400px|[[Trinity Desktop Environment]]]] | |- |[[File:Xfce 4-18.png|thumb|400x400px|[[XFCE]]]] | |} 713b39fd838427127567632118549a41e82f8538 2484 2483 2025-06-19T13:12:28Z Atmois 13 Reverted edit by [[Special:Contributions/Hog|Hog]] ([[User talk:Hog|talk]]) to last revision by [[User:Cherry|Cherry]] wikitext text/x-wiki <gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} 49fb9b6047f630edc2e6580f2ca77f13d388ec79 2485 2484 2025-06-19T13:14:49Z Atmois 13 add WIP tag and DE blurb from reverted edit wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a GUI or TUI. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} 91de645e18a8dd8b1434c2d733c0b51cc3eb117e 2486 2485 2025-06-19T13:34:53Z Hog 161 Did half of descriptions wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a GUI or TUI. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} {| class="wikitable" |+ !Desktop Environment !Description |- |Budgie |The Budgie Desktop is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in Vala. |- |Cinnamon |Cinnamon is a Desktop Environment based on GNOME and developed by the Linux Mint team and written in JavaScript |- |Enlightenment |Enlightenment is a desktop environment and window manager for Linux and other Unix-Based Operating Systems written in C and ELF |- |GNOME |GNOME is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |MATE | |- |Openbox | |- |Plasma | |- |Trinity Desktop Environment | |- |XFCE | |} 913bd012d074e2b3773eb790053f82d0a6f10aa5 2487 2486 2025-06-19T13:48:18Z Hog 161 Finished Descriptions wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a GUI or TUI. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} {| class="wikitable" |+ !Desktop Environment !Description |- |Budgie |The Budgie Desktop is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in Vala. |- |Cinnamon |Cinnamon is a Desktop Environment based on GNOME and developed by the Linux Mint team and written in JavaScript. |- |Enlightenment |Enlightenment is a desktop environment and window manager for Linux and other Unix-Based Operating Systems written in C and ELF. |- |GNOME |GNOME is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |MATE |MATE is a lightweight desktop environment continuation of GNOME 2 and is coded in Python and C++. |- |Openbox |Openbox is a highly configurable and minimal desktop environment coded in C. |- |Plasma |KDE Plasma is a highly customizable and popular and is coded in C++ and QML. |- |Trinity Desktop Environment |Trinity Desktop Environment is an desktop environment forked from KDE 3 coded in C. |- |XFCE |XFCE is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in C. |} 92b84d217bd43be4bed0a60c08919d6103d7b14b 6 662 2488 2025-06-19T14:41:29Z Madonuko 140 Terra logo Taken from https://github.com/terrapkg/website/blob/7a3a56a04e300e2c2c7760829a24df8522db6fe7/public/terra.svg wikitext text/x-wiki == Summary == Terra logo Taken from https://github.com/terrapkg/website/blob/7a3a56a04e300e2c2c7760829a24df8522db6fe7/public/terra.svg == Licensing == {{GPL}} 96f94b33e22374562c93eeda3cce657c9d919a4c 0 663 2489 2025-06-19T16:38:15Z Madonuko 140 init page, /* Installation */, /* Infrastructure */ summary, /* See Also */ wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|thumb]] | caption = Terra logo | title = Terra | releasestatus = Maintained | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terra.fyralabs.com terra.fyralabs.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora]] Linux and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terra.fyralabs.com/ Terra], Terra, 2024 (Accessed: 2025-06-19)</ref> Developed by Fyra Labs, it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra uses a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://developer.fyralabs.com/terra/infrastructure How Terra Works], Fyra Labs, 2025 (Accessed: 2025-06-19)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://developer.fyralabs.com/terra/installing. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable Terra Extras. The package also comes with other streams not enabled by default, including the Nvidia and Mesa stream. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji], RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. == See Also == * [https://terra.fyralabs.com Main Website] * [https://developer.fyralabs.com/terra Fyra Developer Documentations for Terra] * [https://github.com/terrapkg/packages Terra Sources] 7bdedf90a5203d47576cd8cd54a4c8e28ca43be1 0 663 2490 2489 2025-06-19T16:50:35Z Madonuko 140 make logo frameless instead of thumb wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terra.fyralabs.com terra.fyralabs.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora]] Linux and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terra.fyralabs.com/ Terra], Terra, 2024 (Accessed: 2025-06-19)</ref> Developed by Fyra Labs, it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra uses a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://developer.fyralabs.com/terra/infrastructure How Terra Works], Fyra Labs, 2025 (Accessed: 2025-06-19)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://developer.fyralabs.com/terra/installing. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable Terra Extras. The package also comes with other streams not enabled by default, including the Nvidia and Mesa stream. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji], RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. == See Also == * [https://terra.fyralabs.com Main Website] * [https://developer.fyralabs.com/terra Fyra Developer Documentations for Terra] * [https://github.com/terrapkg/packages Terra Sources] b64a10a4c189ff47aa804cf64a0b46a975562c80 0 272 2491 1832 2025-06-19T16:58:44Z Madonuko 140 add infobox, fix wiki syntax wikitext text/x-wiki {{Cleanup|The page describes dnf's importance in a pretty biased way, and it feels somewhat AI-generated.}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:DNF Command Line Interface.png|frameless]] | caption = Invoking <code>sudo dnf upgrade</code> on a terminal with <code>dnf4</code> | title = DNF | releasestatus = Maintained | lastrelease = <code>dnf5</code> 5.2.13.1 (2025-04-25) | languages = [[C++]] | developers = [[Fedora]] and Red Hat, et al. | website = [https://github.com/rpm-software-management/dnf5/ github.com/rpm-software-management/dnf5] }} == Introduction == DNF, short for Dandified YUM, is a software package manager for Linux distributions such as Fedora, CentOS, and RHEL (Red Hat Enterprise Linux). It was designed to be a better version of the traditional YUM (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other RPM-based distributions. == Features == ==== 1. Dependency Resolution: ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== 2. Transaction History: ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== 3. Modularity Dupport: ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== 4. Plugin System: ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== 5. Parallel Downloads: ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== 6. Package Groups: ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: * Installing Packages: <code>dnf install <package_name></code> * Updating Packages <code>dnf update</code> * Removing Packages <code>dnf remove <package_name></code> * Listing Installed Packages: <code>dnf list installed</code> * Searching for Packages: <code>dnf search <keyword></code> * Managing Repositories <code>dnf repolist</code>, <code>dnf config-manager</code> * Viewing Transaction History: <code>dnf history</code> == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. [[Category:Package Managers]] c2ac401e8d158ed493d2703f2f985858d0bd7b4c 2492 2491 2025-06-19T17:08:00Z Madonuko 140 tidy up links and wiki syntax wikitext text/x-wiki {{Cleanup|is that <code>dnf</code>'s importance is described in a pretty biased way, and some parts of this page feels somewhat AI-generated.}}{{Needs Citations}}{{SoftwareInfobox | image = [[File:DNF Command Line Interface.png|frameless]] | caption = Invoking <code>sudo dnf upgrade</code> on a terminal with <code>dnf4</code> | title = DNF | releasestatus = Maintained | lastrelease = <code>dnf5</code> 5.2.13.1 (2025-04-25) | languages = [[C++]] | developers = [[Fedora]] and Red Hat, et al. | website = [https://github.com/rpm-software-management/dnf5/ github.com/rpm-software-management/dnf5] }} '''DNF''', short for ''Dandified YUM'', is a software package manager for Linux distributions such as [[Fedora]], [[CentOS]], and [[RHEL]] (Red Hat Enterprise Linux). It was designed to be a better version of the traditional [[YUM]] (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other [[RPM]]-based distributions. == Features == ==== Dependency Resolution ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== Transaction History ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== Modularity Dupport ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== Plugin System ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== Parallel Downloads ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== Package Groups ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: * Installing Packages: <code>dnf install <package_name></code> * Updating Packages: <code>dnf update</code> * Removing Packages: <code>dnf remove <package_name></code> * Listing Installed Packages: <code>dnf list installed</code> * Searching for Packages: <code>dnf search <keyword></code> * Managing Repositories: <code>dnf repolist</code>, <code>dnf config-manager</code> * Viewing Transaction History: <code>dnf history</code> == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. [[Category:Package Managers]] a02cc7cb035d3cb8c2fdd68191c47d8ab53ad12b 2551 2492 2025-06-21T13:29:14Z Madonuko 140 /* Development of DNF5 */ wikitext text/x-wiki {{Cleanup|is that <code>dnf</code>'s importance is described in a pretty biased way, and some parts of this page feels somewhat AI-generated.}}{{Needs Citations}}{{SoftwareInfobox | image = [[File:DNF Command Line Interface.png|frameless]] | caption = Invoking <code>sudo dnf upgrade</code> on a terminal with <code>dnf4</code> | title = DNF | releasestatus = Maintained | lastrelease = <code>dnf5</code> 5.2.13.1 (2025-04-25) | languages = [[C++]] | developers = [[Fedora]] and Red Hat, et al. | website = [https://github.com/rpm-software-management/dnf5/ github.com/rpm-software-management/dnf5] }} '''DNF''', short for ''Dandified YUM'', is a software package manager for Linux distributions such as [[Fedora]], [[CentOS]], and [[RHEL]] (Red Hat Enterprise Linux). It was designed to be a better version of the traditional [[YUM]] (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other [[RPM]]-based distributions. === Development of DNF5 === The development of DNF5, the next-generation Fedora package manager, began in early 2020 as a complete rewrite of the existing DNF4 codebase to address architectural and performance limitations:<ref>[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NWSURJRGZAIIMNZJT244DHDPOG2PBQXZ/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> <blockquote> We've managed to drop a lot of redundant code across the whole DNF stack in the past years, but we have reached a point when it's nearly impossible to consolidate the code any further without breaking the API/ABI. Especially with PackageKit being dead<ref>[https://blogs.gnome.org/hughsie/2019/02/14/packagekit-is-dead-long-live-well-something-else/ PackageKit is dead, long live, well, something else], hughsie, 2019 (Accessed 2025-06-21)</ref>, we can't move with the old "libhif" API in libdnf, because making any bigger changes to PackageKit is clearly out of scope. </blockquote> The announcement of DNF5 development was made in March 2020, with a roadmap targeting major API changes and early development snapshots throughout 2020, aiming for inclusion in Fedora 34 and stable replacement of DNF4 by early 2021.<ref>[https://lwn.net/Articles/814066/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> Key motivations for DNF5's development included the need to modernize the codebase, which had become cluttered and difficult to maintain, and to move away from dependencies on Python and older APIs. The new design emphasized a fully featured package manager written primarily in C++ for improved performance, reduced resource usage, and a smaller install size compared to DNF4.<ref>[https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5#Benefit_to_Fedora Make DNF5 The Default], Jaroslav Mracek, 2022 (Accessed 2025-06-21)</ref> DNF5 also aimed to unify the software management tools in Fedora by replacing DNF and Microdnf, and providing a new daemon alternative to PackageKit.<ref name=":0">[https://ostechnix.com/dnf5-package-manager-introduction/ Introduction to DNF5: The Next-Generation Fedora Package Manager], Sk, 2025 (Accessed: 2025-06-21)</ref> DNF5 introduced a new core library (libdnf5), revamped plugin systems, enhanced modularity support, and a streamlined command-line interface with improved user experience. The development process was marked by an emphasis on openness, community involvement, and transparent upstream issue tracking to foster broader collaboration. By Fedora 38, DNF5 was available, and it became the default package manager in Fedora 41, fully replacing the older DNF.<ref name=":0" /> == Features == ==== Dependency Resolution ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== Transaction History ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== Modularity Dupport ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== Plugin System ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== Parallel Downloads ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== Package Groups ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: * Installing Packages: <code>dnf install <package_name></code> * Updating Packages: <code>dnf update</code> * Removing Packages: <code>dnf remove <package_name></code> * Listing Installed Packages: <code>dnf list installed</code> * Searching for Packages: <code>dnf search <keyword></code> * Managing Repositories: <code>dnf repolist</code>, <code>dnf config-manager</code> * Viewing Transaction History: <code>dnf history</code> == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. [[Category:Package Managers]] 1af3f9a7d209b1ef7425b2b7f543d4dcfd95c87a 2552 2551 2025-06-21T13:31:53Z Madonuko 140 add cleanup template wikitext text/x-wiki {{Cleanup|The article does not reflect the latest information on dnf5}}{{Cleanup|is that <code>dnf</code>'s importance is described in a pretty biased way, and some parts of this page feels somewhat AI-generated.}}{{Needs Citations}}{{SoftwareInfobox | image = [[File:DNF Command Line Interface.png|frameless]] | caption = Invoking <code>sudo dnf upgrade</code> on a terminal with <code>dnf4</code> | title = DNF | releasestatus = Maintained | lastrelease = <code>dnf5</code> 5.2.13.1 (2025-04-25) | languages = [[C++]] | developers = [[Fedora]] and Red Hat, et al. | website = [https://github.com/rpm-software-management/dnf5/ github.com/rpm-software-management/dnf5] }} '''DNF''', short for ''Dandified YUM'', is a software package manager for Linux distributions such as [[Fedora]], [[CentOS]], and [[RHEL]] (Red Hat Enterprise Linux). It was designed to be a better version of the traditional [[YUM]] (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other [[RPM]]-based distributions. === Development of DNF5 === The development of DNF5, the next-generation Fedora package manager, began in early 2020 as a complete rewrite of the existing DNF4 codebase to address architectural and performance limitations:<ref>[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NWSURJRGZAIIMNZJT244DHDPOG2PBQXZ/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> <blockquote> We've managed to drop a lot of redundant code across the whole DNF stack in the past years, but we have reached a point when it's nearly impossible to consolidate the code any further without breaking the API/ABI. Especially with PackageKit being dead<ref>[https://blogs.gnome.org/hughsie/2019/02/14/packagekit-is-dead-long-live-well-something-else/ PackageKit is dead, long live, well, something else], hughsie, 2019 (Accessed 2025-06-21)</ref>, we can't move with the old "libhif" API in libdnf, because making any bigger changes to PackageKit is clearly out of scope. </blockquote> The announcement of DNF5 development was made in March 2020, with a roadmap targeting major API changes and early development snapshots throughout 2020, aiming for inclusion in Fedora 34 and stable replacement of DNF4 by early 2021.<ref>[https://lwn.net/Articles/814066/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> Key motivations for DNF5's development included the need to modernize the codebase, which had become cluttered and difficult to maintain, and to move away from dependencies on Python and older APIs. The new design emphasized a fully featured package manager written primarily in C++ for improved performance, reduced resource usage, and a smaller install size compared to DNF4.<ref>[https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5#Benefit_to_Fedora Make DNF5 The Default], Jaroslav Mracek, 2022 (Accessed 2025-06-21)</ref> DNF5 also aimed to unify the software management tools in Fedora by replacing DNF and Microdnf, and providing a new daemon alternative to PackageKit.<ref name=":0">[https://ostechnix.com/dnf5-package-manager-introduction/ Introduction to DNF5: The Next-Generation Fedora Package Manager], Sk, 2025 (Accessed: 2025-06-21)</ref> DNF5 introduced a new core library (libdnf5), revamped plugin systems, enhanced modularity support, and a streamlined command-line interface with improved user experience. The development process was marked by an emphasis on openness, community involvement, and transparent upstream issue tracking to foster broader collaboration. By Fedora 38, DNF5 was available, and it became the default package manager in Fedora 41, fully replacing the older DNF.<ref name=":0" /> == Features == ==== Dependency Resolution ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== Transaction History ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== Modularity Dupport ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== Plugin System ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== Parallel Downloads ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== Package Groups ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: * Installing Packages: <code>dnf install <package_name></code> * Updating Packages: <code>dnf update</code> * Removing Packages: <code>dnf remove <package_name></code> * Listing Installed Packages: <code>dnf list installed</code> * Searching for Packages: <code>dnf search <keyword></code> * Managing Repositories: <code>dnf repolist</code>, <code>dnf config-manager</code> * Viewing Transaction History: <code>dnf history</code> == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. [[Category:Package Managers]] 93aabcb5d9b2cb67abf89c2aba449ec4b9b8504b 0 474 2493 1564 2025-06-19T17:30:38Z Madonuko 140 redirect to [[Multi_Booting]] wikitext text/x-wiki #REDIRECT [[Multi_Booting]] aa832a4e2e647b457eed93fef1f77c4f377ae1fe 0 664 2494 2025-06-19T17:31:39Z Madonuko 140 redirect to [[Multi_Booting]] wikitext text/x-wiki #REDIRECT [[Multi_Booting]] aa832a4e2e647b457eed93fef1f77c4f377ae1fe 0 217 2495 2034 2025-06-19T17:33:55Z Madonuko 140 change the display name to Fedora Linux… because it's Fedora Linux wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}} {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]] |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}} [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being [[RHEL|Red Hat Enterprise Linux]] (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> <references /> [[Category:Linux Distributions]] c926df9f6e80d1f02fba2acd15f01fdccfbe9648 0 428 2496 2471 2025-06-19T17:48:55Z Madonuko 140 fix wiki syntax wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' is a [[TUI|command-line]] utility available on [[UNIX]] and [[UNIX-like]] [[Operating System|operating systems]] that provides [[documentation]] for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a Man page the user can enter the following into their [[TUI|terminal]]:<ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> man ''<command_name>'' For example, to read the Man page on [[Pacman]] you would enter the following: man pacman == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER<code> environment variable. By default, it uses <code>less<code>. Alternatively, the </code>-P</code> or </code>--pager</code> option can be used. <ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally. <ref>https://fishshell.com/docs/current/faq.html</ref> <references /> ee7e65db537f83f782dabcf30a33d1436d244362 2498 2496 2025-06-19T18:47:06Z Madonuko 140 bye man pacman, hi man man wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' (short for ''manual'') is a [[TUI|command-line]] utility available on [[UNIX]] and [[UNIX-like]] [[Operating System|operating systems]] that provides [[documentation]] for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a man page the user can enter the following into their [[TUI|terminal]]:<ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> man ''<command_name>'' For example, to read the manual for <code>man</code> command itself: man man == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER<code> environment variable. By default, it uses <code>less<code>. Alternatively, the </code>-P</code> or </code>--pager</code> option can be used. <ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally. <ref>https://fishshell.com/docs/current/faq.html</ref> <references /> 5decda2b2f550ad34bd327176f465a63be6f2727 2510 2498 2025-06-20T08:37:01Z Hog 161 Corrected link wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' (short for ''manual'') is a [[TUI|command-line]] utility available on [[UNIX]] and UNIX-like [[Operating System|operating systems]] that provides [[documentation]] for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a man page the user can enter the following into their [[TUI|terminal]]:<ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> man ''<command_name>'' For example, to read the manual for <code>man</code> command itself: man man == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER<code> environment variable. By default, it uses <code>less<code>. Alternatively, the </code>-P</code> or </code>--pager</code> option can be used. <ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally. <ref>https://fishshell.com/docs/current/faq.html</ref> <references /> 7a35d08d41d76627203ec04073365dad6db1c148 0 158 2497 1223 2025-06-19T18:15:16Z Madonuko 140 tidy up wiki syntax wikitext text/x-wiki {{cleanup|The language lacks formality and everything is clumped up. Splitting things into sections may help.}}When using [[Linux]], sooner or later, there's a good chance you'll end finding yourself in front of a [[Terminal Emulator|terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a '''command'''. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include <code>echo</code>, <code>mv</code>, [[cat|<code>cat</code>]], etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with <code>sudo</code> followed with your original command. [[sudo]] tells your computer to ''do'' something as a ''super user'' which will allow you to bypass restrictions. It should be important to note that '''sudo is a seperate package''' and may not be pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you will need to use something like <code>su</code> to log in as root and then run your command as root or install sudo as root. Furthermore, with commands you will likely need to include ''options'' that specify to the program how you want it to behave. One of the most common options is <code>--help</code>, which will usually tell program to list all of its options. An example would be as follows: cat --help In this case, the 'cat' utility would respond to this command with the following:<syntaxhighlight>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines ...</syntaxhighlight>(Shortened to maintain focus on topic) These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, <code>--help</code> is always there and ready. If not, you can always run [[man|<code>man</code>]] before a program similarly to how you would run <code>sudo</code>, and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a file to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory|working directory]] (Like shown) or you can provide a file from anywhere in the [[filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt The tilda sign <code>~</code>, in Linux and some other [[Operating System|operating systems]], expands to the full [[Directory Path|directory path]] of the current user's home folder. Here is what it would look like to type out the whole path: nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 8ff11ec5e20158930f5279580c685cf0cd2f7223 0 198 2499 2482 2025-06-19T18:50:55Z Madonuko 140 move [[CentOS]] to RH based and make it in italics wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] 170b0df494162c82a6f73536a96f3355b8455cbc 0 225 2500 975 2025-06-20T07:10:10Z Madonuko 140 remove x86-64-v2 because dnf doesn't support microarches wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64 | website = [https://redhat.com/rhel/ redhat.com] }} [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business customers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. <references /> [[Category:Linux Distributions]] 474da49699f66268578b9d796db89d653278061c 6 666 2503 2025-06-20T07:44:24Z Madonuko 140 Running `seq 50 | sed -E '15~15{s@.+@FizzBuzz@; b}; 3~3{s@.+@Fizz@; b}; 5~5s@.+@Buzz@' | pr -5t` in konsole wikitext text/x-wiki == Summary == Running `seq 50 | sed -E '15~15{s@.+@FizzBuzz@; b}; 3~3{s@.+@Fizz@; b}; 5~5s@.+@Buzz@' | pr -5t` in konsole == Licensing == {{CC0}} c6bff7e122530e4dfd66e109829908a46ad1684b 0 622 2504 2487 2025-06-20T08:13:28Z Hog 161 Added Links wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a GUI or TUI. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> This page is in urgent need of work, below is a list of pages in the category. {{#dpl: |category = Desktop Environments |namespace = Main }} {| class="wikitable" |+ !Desktop Environment !Description |- |Budgie |The Budgie Desktop is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |Cinnamon |Cinnamon is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |Enlightenment |Enlightenment is a desktop environment and window manager for [[Linux]] and other [[Unix|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |GNOME |GNOME is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |MATE |MATE is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |Openbox |Openbox is a highly configurable and minimal desktop environment coded in C. |- |Plasma |KDE Plasma is a highly customizable and popular and is coded in C++ and [[QML]]. |- |Trinity Desktop Environment |Trinity Desktop Environment is an desktop environment forked from [[Plasma|KDE]] 3 coded in C. |- |XFCE |XFCE is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in C. |} 4f838290d80d85c75eaf33ac0f49cb548e0b18ae 0 344 2505 2425 2025-06-20T08:15:50Z Hog 161 punctuation wikitext text/x-wiki [[File:Kernel Layout.svg|thumb|How the Kernel interacts with the software and hardware.]] The Kernel is the core part of any [[Operating System|operating system]], including [[Linux]]. It's the fundamental layer between your [[hardware]] (like your CPU, memory, and GPU) and the [[:Category:Software|software]] you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, Etc). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2 Linus Torvalds 1991 (Retrieved 16th March 2025)</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel Kicksecure, Madaiden, Adrelanos 2023 (Retrieved 16th March 2025)</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. [[Category:Terminology]] 5bfbd00cdca5c4ce7f16f103be6f1afdb43129cb 0 667 2506 2025-06-20T08:31:03Z Hog 161 Did a small bit of unix will complete later wikitext text/x-wiki {{Cleanup|Incomplete page}}UNIX is...{{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}} 8ca00a1d6fe494452075e0863d4ddb0fe0274e51 0 441 2507 2442 2025-06-20T08:32:14Z Hog 161 Corrected link wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,") <ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU] , The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref>is a dedicated organization for free [[:Category:Software|software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone [[Operating System|operating system]] because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or [[Proprietary software|proprietary]]: A few are GNU/[[Linux]], MacOS, [[UNIX|Unix-based]]/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the [[proprietary software]] of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe. </ref> == Included Software / Components == [[File:Gnu compiler collection-logo-1.png|alt=This logo depicts a Bull shaped animal jumping out of an egg, in black text that displays the letters G, C, C|left|thumb|224x224px|A logo of the GCC.]] As of June 2024, the GNU project currently holds 394 active [[packages]], but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. Overall, these components are in many operating systems, mainly because of how easy GCC is to access for any developer. Because of Richard Stallman, he was able to open source the variety of tools and software developed for the GNU project and in turn, pushed forward for the movement of open and free software for all.<ref name=":0" /> == History of GNU == [[File:RichardStallman.jpg|alt=A Picture of Richard Matthew Stallman in 2024|thumb|341x341px|A Picture of Richard Matthew Stallman in 2024]] Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref name=":0">[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible [[architecture]] because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs. <ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> <references /> a2eb28810a65f30e09bc22b10da4abf43bf50095 0 176 2508 2204 2025-06-20T08:32:47Z Hog 161 Added Links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:KDE logo.svg|KDE_logo]] | caption = KDE Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[UNIX|UNIX-Based]] Operating Systems, ranging from [[Linux]] to various flavors of BSD.<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] e7d21c1bf38812bd7b1b240f9bdb9eb99f32c904 0 415 2509 2416 2025-06-20T08:36:40Z Hog 161 Corrected link wikitext text/x-wiki POSIX, a rewritten name that stands for "Portable Operating System Interface" in replacement for IEEE-IX for the IEEE Computer Society, is a set of standards for upkeeping compatibility across different [[Operating System|operating systems]] as it defines system & user-levels [[API|APIs]] in the addition of utility interfaces and command line shells for portability with [[UNIX|Unix]], Unix-Based/Like operating systems, and more.<ref>The Linux Code, November 1, 2023, ''POSIX: A Thorough Overview for Linux Developers — https://thelinuxcode.com/posix-standard/''</ref> === Modern Day POSIX Standards === There are many modern-day standards for POSIX, in order for a Unix-Based/Like operating system to POSIX-Compliant, it must provide implementations of the many POSIX APIs. These standards include the ability to use core services and/or processes properly: Core API Services and its processes, threads, signals, basic file I/O, as well as using [[Shell]] utilities such as bash and following commands like <code>grep</code> , <code>sort</code>, <code>find</code>, and plenty more. <references /> 737b1f09cd3940ab39c808e6e02391272dd41630 0 659 2511 2477 2025-06-20T08:41:19Z Hog 161 Added Links wikitext text/x-wiki {{DistributionInfobox|title=ChromeOS|image=[[File:Chromium_Logo.svg|frameless]]|caption=ChromiumOs Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[APT]]|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website=[https://chromeos.google/ chromeos]}}ChromeOS (ChromiumOS) is a [[UNIX|Unix-Based]] [[Linux Distributions|Linux distribution]] designed and developed by Google in 2009. ChromeOS is completely open-source<ref>http://source.chromium.org/chromiumos</ref>. d7fe10879a0db7143a548f466b6934098edc937f 0 668 2512 2025-06-20T08:43:39Z Madonuko 140 init sed page with /* History */ and /* See Also */ wikitext text/x-wiki [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with GNU <code>sed</code> | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = C | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in Unix-like [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == <code>sed</code> dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor <code>ed</code> (1971) and the even earlier <code>qed</code> (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. <code>sed</code> first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep|<code>grep</code>]] command. While <code>grep</code> was used for searching text with regular expressions, <code>sed</code> was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name <code>''sed''</code> reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. <code>sed</code> was one of the earliest tools to support regular expressions and influenced many later languages, including <code>[[AWK|awk]]</code> and [[Perl]]. <code>awk</code>, developed later, and <code>sed</code> together, functioned as complementary tools for text processing in Unix shell scripts. Both <code>sed</code> and <code>awk</code> inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of <code>sed</code> have emerged. GNU <code>sed</code> added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called <code>minised</code> was reverse-engineered from BSD <code>sed</code> and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] e78e176f3d3ab98f860613962f9ef84200a09309 2513 2512 2025-06-20T08:45:44Z Hog 161 Added Links wikitext text/x-wiki [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with GNU <code>sed</code> | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == <code>sed</code> dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor <code>ed</code> (1971) and the even earlier <code>qed</code> (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. <code>sed</code> first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep|<code>grep</code>]] command. While <code>grep</code> was used for searching text with regular expressions, <code>sed</code> was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name <code>''sed''</code> reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. <code>sed</code> was one of the earliest tools to support regular expressions and influenced many later languages, including <code>[[AWK|awk]]</code> and [[Perl]]. <code>awk</code>, developed later, and <code>sed</code> together, functioned as complementary tools for text processing in Unix shell scripts. Both <code>sed</code> and <code>awk</code> inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of <code>sed</code> have emerged. GNU <code>sed</code> added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called <code>minised</code> was reverse-engineered from BSD <code>sed</code> and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] a377be1cb072c13c1ba6d0a27550d2e97e4e90df 2517 2513 2025-06-20T11:36:48Z Madonuko 140 /* Examples */ init wikitext text/x-wiki [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with GNU <code>sed</code> | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == <code>sed</code> dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor <code>ed</code> (1971) and the even earlier <code>qed</code> (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. <code>sed</code> first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep|<code>grep</code>]] command. While <code>grep</code> was used for searching text with regular expressions, <code>sed</code> was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name <code>''sed''</code> reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. <code>sed</code> was one of the earliest tools to support regular expressions and influenced many later languages, including <code>[[AWK|awk]]</code> and [[Perl]]. <code>awk</code>, developed later, and <code>sed</code> together, functioned as complementary tools for text processing in Unix shell scripts. Both <code>sed</code> and <code>awk</code> inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of <code>sed</code> have emerged. GNU <code>sed</code> added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called <code>minised</code> was reverse-engineered from BSD <code>sed</code> and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working directory contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells <code>sed</code> to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 21bfa2035914b8b9858459e767d267508763814a 2518 2517 2025-06-20T13:13:42Z Hog 161 Added Links wikitext text/x-wiki [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] <code>sed</code> | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == <code>sed</code> dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor <code>ed</code> (1971) and the even earlier <code>qed</code> (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. <code>sed</code> first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep|<code>grep</code>]] command. While <code>grep</code> was used for searching text with regular expressions, <code>sed</code> was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name <code>''sed''</code> reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. <code>sed</code> was one of the earliest tools to support regular expressions and influenced many later languages, including <code>[[AWK|awk]]</code> and [[Perl]]. <code>awk</code>, developed later, and <code>sed</code> together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both <code>sed</code> and <code>awk</code> inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of <code>sed</code> have emerged. GNU <code>sed</code> added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called <code>minised</code> was reverse-engineered from BSD <code>sed</code> and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells <code>sed</code> to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 845dca0899775e8913d27bd2964de96a3efa74c9 2527 2518 2025-06-20T18:21:48Z Madonuko 140 lowercase title wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] <code>sed</code> | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == <code>sed</code> dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor <code>ed</code> (1971) and the even earlier <code>qed</code> (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. <code>sed</code> first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep|<code>grep</code>]] command. While <code>grep</code> was used for searching text with regular expressions, <code>sed</code> was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name <code>''sed''</code> reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. <code>sed</code> was one of the earliest tools to support regular expressions and influenced many later languages, including <code>[[AWK|awk]]</code> and [[Perl]]. <code>awk</code>, developed later, and <code>sed</code> together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both <code>sed</code> and <code>awk</code> inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of <code>sed</code> have emerged. GNU <code>sed</code> added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called <code>minised</code> was reverse-engineered from BSD <code>sed</code> and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells <code>sed</code> to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 445b32033170b0847b4d4cd2e360c73eedf815f9 2531 2527 2025-06-20T18:40:01Z Madonuko 140 unsurround code tags wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor ed (1971) and the even earlier qed (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] f9522e4a0b34e49f320a0e66d53c6eb9f11e8362 2549 2531 2025-06-21T08:28:35Z Madonuko 140 /* Replace `backticks` with Tags */ showcase the -i flag wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor ed (1971) and the even earlier qed (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 8bce72444df432a2ebf7e6e85f498a9fd26a83c5 2 644 2514 2373 2025-06-20T08:53:17Z Madonuko 140 /* Pages I maintain */ I meowed a few more pages! wikitext text/x-wiki V.P. DevOps at [https://fyralabs.com Fyra Labs] and [[Ultramarine Linux]]. Lead maintainer of [[Terra]]. == Pages I maintain == * [[Guides:Input method]] * [[Sed]] * [[Terra]] 4c3d91565afc22bec465fbf1ea75416dfecc1d7a 3001 669 2515 2025-06-20T09:11:12Z Madonuko 140 /* What Counts as a “Guide” */ init discussion wikitext text/x-wiki == What Counts as a “Guide” == I don’t agree with some of the [[Template:Cleanup]]s mentioning splitting pages into guides, e.g. the one in the [[AWK]] page. Personally I think a “guide” is a set of instructions guiding readers on how to perform specific tasks. That’s not what’s happening in the awk page. It’s just providing examples on how to use the program. It doesn’t really achieve anything. The main problem here is '''we need a definition on “guide”'''. That is, the '''criteria'''. I think the main deciding factor is that within a guide, you need to perform steps (e.g. [[Guides:Installing Niri]], [[Guides:Setting up Flathub on Fedora]]), as opposed to just discrete documentations ([[Guides:Input method]]). Or reversely, if the [[Template:Guide Warning]] just doesn’t make sense on the page (because… like, the input method page barely has any instructions other than just maybe… like, may~be “hey there’s this package and there’s that package that you could install”), then it really shouldn’t be in [[Guides]] I think. 5168b3bf439ab397ac796cb774464342176b394e 2516 2515 2025-06-20T09:11:56Z Madonuko 140 /* What Counts as a “Guide” */ sign wikitext text/x-wiki == What Counts as a “Guide” == I don’t agree with some of the [[Template:Cleanup]]s mentioning splitting pages into guides, e.g. the one in the [[AWK]] page. Personally I think a “guide” is a set of instructions guiding readers on how to perform specific tasks. That’s not what’s happening in the awk page. It’s just providing examples on how to use the program. It doesn’t really achieve anything. The main problem here is '''we need a definition on “guide”'''. That is, the '''criteria'''. I think the main deciding factor is that within a guide, you need to perform steps (e.g. [[Guides:Installing Niri]], [[Guides:Setting up Flathub on Fedora]]), as opposed to just discrete documentations ([[Guides:Input method]]). Or reversely, if the [[Template:Guide Warning]] just doesn’t make sense on the page (because… like, the input method page barely has any instructions other than just maybe… like, may~be “hey there’s this package and there’s that package that you could install”), then it really shouldn’t be in [[Guides]] I think. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 09:11, 20 June 2025 (UTC) 8cdc5474c02838ad8dc0b143ff35258ba8e1c30f 0 174 2519 2480 2025-06-20T13:18:21Z Hog 161 Added Links wikitext text/x-wiki {{Cleanup|Incomplete page}}[[File:Debian-Installer 10 Tasksel.svg|alt=Debian TUI installer|thumb|Debian 10 installation, which uses a TUI installer]] A '''TUI''' (Terminal User Interface) generally refers to an [[:Category:Software|application]] that solely exists within the terminal as a text-based application - this means that all of its content is rendered using letters and other unique characters to create a graphical interface.{{Citation needed}} Most [[UNIX|Unix-Based]] [[Operating System|Operating systems]] support virtual consoles. [[Category:Terminology]] 0edc5b018467b25960fc3c9db22586422a5e1682 0 202 2520 2054 2025-06-20T13:23:21Z Hog 161 cleaned up some citations wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow Gentoo Wiki, 2023 (Imported 4th June 2024)</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html Gentoo Forums, 2003 (imported 4th June 2024)</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727 Gentoo Bug Report, 2003 (imported 4th June 2024)</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry</ref> <references /> [[Category:Mascots]] 10b58d06ac7dd6e6abce5e4825340a1ecbecfc56 0 670 2521 2025-06-20T16:12:43Z Madonuko 140 init wikitext text/x-wiki '''Regular Expression''', also known as '''Regex''' or '''RegExp''', refers to a type of pattern “used to match character combinations in strings”<ref>[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript], MDN, 2025 (Accessed 2025-06-20)</ref>. It is a very powerful tool for searching, matching, replacing, and parsing target text based on specific patterns. In other words, a ''regex engine''<ref>[https://www.regular-expressions.info/engine.html How a Regex Engine Works Internally], Jan Goyvaerts, 2019 (Accessed: 2025-06-20)</ref> can find, extract and substitute target text under a format defined by a given regex. Regex is not universally the same. Different flavours of regex are supported by different regex engines provided by different libraries and programming languages. However, a portion of the syntax is generally the same across them.<ref>[https://regex101.com/ regex101: build, test, and debug regex], regex101.com, 2025 (Accessed: 2025-06-20)</ref> == Usage == Regex is used in many text processing tools. Graphical examples include the find and replace feature in [[LibreOffice]]<ref>[https://help.libreoffice.org/25.2/en-US/text/swriter/guide/search_regexp.html?&DbPAR=SHARED&System=UNIX Using Regular Expressions in Text Searches], LibreOffice, 2025 (Accessed: 2025-06-20)</ref>. [[CLI|Command line]] examples include [[AWK]], [[sed]], and [[grep]]. Many popular scripting and programming languages provide built-in support for regex, notably [[JavaScript]], [[Perl]], [[Java]], [[Ruby]], [[Python]], [[C++]], [[PHP]], each with slighting varying implementations and different sets of supported syntax.<ref>[https://www.regular-expressions.info/tools.html Popular Tools, Utilities and Programming Languages That Support Regular Expressions], Jan Goyvaerts, 2021 (Accessed: 2025-06-21)</ref> == See Also == * [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript | MDN] * [https://regex101.com/ regex101: build, test, and debug regex] [[Category:Terminology]] 5563e4bffae5877d79fd0adb81205e863b36e2fa 0 671 2522 2025-06-20T16:13:49Z Madonuko 140 redirect to [[Regular Expression]] wikitext text/x-wiki #REDIRECT [[Regular Expression]] c3bda233a3650acc744c9108e4ef3275f66b9ad1 0 672 2523 2025-06-20T16:43:39Z Madonuko 140 redirect to [[Regular Expression]] wikitext text/x-wiki #REDIRECT [[Regular Expression]] c3bda233a3650acc744c9108e4ef3275f66b9ad1 6 673 2524 2025-06-20T17:06:17Z Madonuko 140 In Konsole fish shell, running grep --help | grep -n 'PATTERNS\|regex' wikitext text/x-wiki == Summary == In Konsole fish shell, running grep --help | grep -n 'PATTERNS\|regex' == Licensing == {{CC0}} 5b102ffc4b2373d17f4c471e5d33daa7d6880ce5 0 674 2525 2025-06-20T18:04:31Z Madonuko 140 init wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Running <code><nowiki>grep --help | grep -n 'PATTERNS\|regex'</nowiki></code> in [[Fish]] in [[Konsole]] | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU <code>grep</code>: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref>[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, <code>grep</code>'s creation stemmed from Thompson's need to analyze text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed|<code>ed</code>]] text editor into a standalone tool. He named the tool <code>grep</code> because in <code>ed</code>, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>. == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into <code>grep</code>, which finds all lines with the text “error”. However, <code>grep</code> itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended [[regular expression]]s'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> b531754d7f6bc427e39a3f4980fe967994ba6eac 2526 2525 2025-06-20T18:20:35Z Madonuko 140 /* Alternatives */ and /* See Also */ wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Running <code><nowiki>grep --help | grep -n 'PATTERNS\|regex'</nowiki></code> in [[Fish]] in [[Konsole]] | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU <code>grep</code>: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, <code>grep</code>'s creation stemmed from Thompson's need to analyze text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed|<code>ed</code>]] text editor into a standalone tool. He named the tool <code>grep</code> because in <code>ed</code>, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into <code>grep</code>, which finds all lines with the text “error”. However, <code>grep</code> itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended [[regular expression]]s'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Alternatives == Faster implementations of <code>grep</code> such as [[ripgrep]] (<code>rg</code>) and [[hypergrep]] (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU <code>grep</code>. The <code>agrep</code> tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] f77ab86338f1930cff2c34f8124642734f7181ba 2530 2526 2025-06-20T18:35:48Z Madonuko 140 unsurround code tags wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Running <code><nowiki>grep --help | grep -n 'PATTERNS\|regex'</nowiki></code> in [[Fish]] in [[Konsole]] | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU grep: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, grep's creation stemmed from Thompson's need to analyze text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed]] text editor into a standalone tool. He named the tool ''grep''' because in ed, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into grep, which finds all lines with the text “error”. However, grep itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended [[regular expression]]s'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Alternatives == Faster implementations of grep such as '''[[ripgrep]]''' (<code>rg</code>) and '''[[hypergrep]]''' (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU grep. The '''<code>agrep</code>''' tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] fa94700aa376e3c391f9826e4f8b7df890766fce 2542 2530 2025-06-20T19:54:58Z Madonuko 140 /* Examples */ init wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Running <code><nowiki>grep --help | grep -n 'PATTERNS\|regex'</nowiki></code> in [[Fish]] in [[Konsole]] | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU grep: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, grep's creation stemmed from Thompson's need to analyze text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed]] text editor into a standalone tool. He named the tool ''grep''' because in ed, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into grep, which finds all lines with the text “error”. However, grep itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended [[regular expression]]s'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Examples == === Finding Python Function Calls === In a [[Python]] codebase, we can find all calls to functions under the <code>subprocess</code> module with <code>shell=True</code>: $ grep -r --include='*.py' -nHE 'subprocess\.\w+\([^)]*shell=True' ./driver.py:69: return subprocess.call("lspci | grep -q -i NVIDIA", shell=True) == 0 ./driver.py:202: return subprocess.call("lspci | grep -q -i Network | grep -q -i Broadcom", shell=True) == 0 ./driver.py:211: return subprocess.call("lspci | grep -q -i Bluetooth | grep -q -i Broadcom", shell=True) == 0 ./util.py:38: proc = subprocess.Popen(f"chroot {chroot} /tmp/stellar-payload.sh", shell=True) ./util.py:63: # proc = subprocess.Popen(payload, shell=True) ./util.py:66: proc = subprocess.Popen(f"pkexec {tmpfile}", shell=True) (This is run on the [https://github.com/Ultramarine-Linux/stellar/ Ultramarine stellar codebase]) We can breakdown the flags used in this example: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>--include='*.py'</code>: only examine Python files * <code>-n</code>: show line numbers * <code>-H</code>: show file name * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] We can divide the pattern <code>subprocess\.\w+\([^)]*shell=True</code> into many parts: # <code>subprocess</code> matches the string “subprocess” literally; # <code>\.</code> matches the full stop literally; # <code>\w+</code> matches word characters one or more times, where a word character (<code>\w</code>) is any letter, digit or underscore<ref>[https://www.regexroo.com/word-characters Understanding \w and Its Counterpart \W in Regex], RegexRoo.com, 2025 (Accessed: 2025-06-21)</ref>; # <code>\(</code> matches for an open parenthesis <code>(</code> literally; # <code>[^)]*</code> is an inverse character group and matches any characters that are not the closing parenthesis <code>)</code> zero or more times; and # <code>shell=True</code> matches the string “shell=True” literally. === Finding Code Files with TODOs and FIXMEs === We can list out code files that contains both the word “FIXME” and “TODO”. For a Rust project: $ grep -rlZ 'FIXME' --include='*.rs' . | xargs -0 grep -l 'TODO' ./src/pages/_15_installing.rs ./src/main.rs Flags: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>-l</code>: output matching files' names only * <code>-Z</code>: instead of a new line character, print out a null character after each filename * <code>--include='*.rs'</code>: only examine Rust files In this example, the first command outputs the filenames with null separates, then [[xargs]] is used to feed the filenames into the second grep command, which searches for “TODO”s in those files. === Extracting All Unique Public IPv4 Addresses from Log Files === We can extract all the unique IPv4 addresses from a directory of log files, but exclude any private IP addresses, such as <code>10.x.x.x</code> / <code>192.168.x.x</code>: <syntaxhighlight lang=sh> grep -rhoE '([0-9]{1,3}\.){3}[0-9]{1,3}' /path/to/logs | sort -u | grep -vE '^10\.|^192\.168\.' </syntaxhighlight> Flags: * <code>-r</code>: find files recursively * <code>-h</code>: suppress printing of filenames * <code>-o</code>: show only matching part of line * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] * <code>-v</code>: select non-matching lines For the first pattern: # <code>[0-9]</code> matches the digits (0 to 9 on the ASCII table includes all digits), and <code>{1,3}</code> specifies the length must be between 1 and 3; and # <code>([0-9]{1,3}\.){3}</code> matches exactly 3 times the above followed by a full stop. For the second pattern: # <code>^10\.</code> matches for lines starting with <code>10.</code>; # <code>^192\.168\.</code> matches for lines starting with <code>192.168.</code>; and # <code>|</code> (which indicates “or”) allow matching for the regex specified on the left or the right. Due to invert flag (<code>-v</code>), if a line matches the second pattern, it is excluded, and other lines are printed instead. == Alternatives == Faster implementations of grep such as '''[[ripgrep]]''' (<code>rg</code>) and '''[[hypergrep]]''' (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU grep. The '''<code>agrep</code>''' tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] 6628c811a625f7fb55bd705eee7daa5a33e4cfcd 2543 2542 2025-06-20T19:57:04Z Madonuko 140 fix my english at 4am wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Running <code><nowiki>grep --help | grep -n 'PATTERNS\|regex'</nowiki></code> in [[Fish]] in [[Konsole]] | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU grep: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, grep's creation stemmed from Thompson's need to analyze text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed]] text editor into a standalone tool. He named the tool ''grep''' because in ed, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into grep, which finds all lines with the text “error”. However, grep itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended [[regular expression]]s'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Examples == === Finding Python Function Calls === In a [[Python]] codebase, we can find all calls to functions under the <code>subprocess</code> module with <code>shell=True</code>: $ grep -r --include='*.py' -nHE 'subprocess\.\w+\([^)]*shell=True' ./driver.py:69: return subprocess.call("lspci | grep -q -i NVIDIA", shell=True) == 0 ./driver.py:202: return subprocess.call("lspci | grep -q -i Network | grep -q -i Broadcom", shell=True) == 0 ./driver.py:211: return subprocess.call("lspci | grep -q -i Bluetooth | grep -q -i Broadcom", shell=True) == 0 ./util.py:38: proc = subprocess.Popen(f"chroot {chroot} /tmp/stellar-payload.sh", shell=True) ./util.py:63: # proc = subprocess.Popen(payload, shell=True) ./util.py:66: proc = subprocess.Popen(f"pkexec {tmpfile}", shell=True) (This is run on the [https://github.com/Ultramarine-Linux/stellar/ Ultramarine stellar codebase]) We can breakdown the flags used in this example: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>--include='*.py'</code>: only examine Python files * <code>-n</code>: show line numbers * <code>-H</code>: show file name * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] We can divide the pattern <code>subprocess\.\w+\([^)]*shell=True</code> into many parts: # <code>subprocess</code> matches the string “subprocess” literally; # <code>\.</code> matches the full stop literally; # <code>\w+</code> matches word characters one or more times, where a word character (<code>\w</code>) is any letter, digit or underscore<ref>[https://www.regexroo.com/word-characters Understanding \w and Its Counterpart \W in Regex], RegexRoo.com, 2025 (Accessed: 2025-06-21)</ref>; # <code>\(</code> matches for an open parenthesis <code>(</code> literally; # <code>[^)]*</code> is an inverse character group and matches any characters that are not the closing parenthesis <code>)</code> zero or more times; and # <code>shell=True</code> matches the string “shell=True” literally. === Finding Code Files with TODOs and FIXMEs === We can list out code files that contains both the word “FIXME” and “TODO”. For a Rust project: $ grep -rlZ 'FIXME' --include='*.rs' . | xargs -0 grep -l 'TODO' ./src/pages/_15_installing.rs ./src/main.rs Flags: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>-l</code>: output matching files' names only * <code>-Z</code>: instead of a new line character, print out a null character after each filename * <code>--include='*.rs'</code>: only examine Rust files In this example, the first command outputs the filenames with null separates, then [[xargs]] is used to feed the filenames into the second grep command, which searches for “TODO”s in those files. === Extracting All Unique Public IPv4 Addresses from Log Files === We can extract all the unique IPv4 addresses from a directory of log files, but exclude any private IP addresses, such as <code>10.x.x.x</code> / <code>192.168.x.x</code>: <syntaxhighlight lang=sh> grep -rhoE '([0-9]{1,3}\.){3}[0-9]{1,3}' /path/to/logs | sort -u | grep -vE '^10\.|^192\.168\.' </syntaxhighlight> Flags: * <code>-r</code>: find files recursively * <code>-h</code>: suppress printing of filenames * <code>-o</code>: show only matching part of line * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] * <code>-v</code>: select non-matching lines For the first pattern: # <code>[0-9]</code> matches the digits (0 to 9 on the ASCII table includes all digits), and <code>{1,3}</code> specifies the length must be between 1 and 3; and # <code>([0-9]{1,3}\.){3}</code> matches exactly 3 times the above followed by a full stop. For the second pattern: # <code>^10\.</code> matches for lines starting with <code>10.</code>; # <code>^192\.168\.</code> matches for lines starting with <code>192.168.</code>; and # <code>|</code> (which indicates “or”) allows matching for the regex specified on the left or the right. Due to the invert flag (<code>-v</code>), if a line matches the second pattern, it is excluded, and other lines are printed instead. == Alternatives == Faster implementations of grep such as '''[[ripgrep]]''' (<code>rg</code>) and '''[[hypergrep]]''' (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU grep, and usually not pre-installed on most distributions. The '''<code>agrep</code>''' tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] 4357640001a57a2040f18309828d0158a4bdb592 2548 2543 2025-06-20T20:00:48Z Madonuko 140 fix this "alt text" lol wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Searching for “PATTERNS” or “regex” in <code>grep --help</code> | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU grep: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, grep's creation stemmed from Thompson's need to analyze text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed]] text editor into a standalone tool. He named the tool ''grep''' because in ed, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into grep, which finds all lines with the text “error”. However, grep itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended [[regular expression]]s'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Examples == === Finding Python Function Calls === In a [[Python]] codebase, we can find all calls to functions under the <code>subprocess</code> module with <code>shell=True</code>: $ grep -r --include='*.py' -nHE 'subprocess\.\w+\([^)]*shell=True' ./driver.py:69: return subprocess.call("lspci | grep -q -i NVIDIA", shell=True) == 0 ./driver.py:202: return subprocess.call("lspci | grep -q -i Network | grep -q -i Broadcom", shell=True) == 0 ./driver.py:211: return subprocess.call("lspci | grep -q -i Bluetooth | grep -q -i Broadcom", shell=True) == 0 ./util.py:38: proc = subprocess.Popen(f"chroot {chroot} /tmp/stellar-payload.sh", shell=True) ./util.py:63: # proc = subprocess.Popen(payload, shell=True) ./util.py:66: proc = subprocess.Popen(f"pkexec {tmpfile}", shell=True) (This is run on the [https://github.com/Ultramarine-Linux/stellar/ Ultramarine stellar codebase]) We can breakdown the flags used in this example: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>--include='*.py'</code>: only examine Python files * <code>-n</code>: show line numbers * <code>-H</code>: show file name * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] We can divide the pattern <code>subprocess\.\w+\([^)]*shell=True</code> into many parts: # <code>subprocess</code> matches the string “subprocess” literally; # <code>\.</code> matches the full stop literally; # <code>\w+</code> matches word characters one or more times, where a word character (<code>\w</code>) is any letter, digit or underscore<ref>[https://www.regexroo.com/word-characters Understanding \w and Its Counterpart \W in Regex], RegexRoo.com, 2025 (Accessed: 2025-06-21)</ref>; # <code>\(</code> matches for an open parenthesis <code>(</code> literally; # <code>[^)]*</code> is an inverse character group and matches any characters that are not the closing parenthesis <code>)</code> zero or more times; and # <code>shell=True</code> matches the string “shell=True” literally. === Finding Code Files with TODOs and FIXMEs === We can list out code files that contains both the word “FIXME” and “TODO”. For a Rust project: $ grep -rlZ 'FIXME' --include='*.rs' . | xargs -0 grep -l 'TODO' ./src/pages/_15_installing.rs ./src/main.rs Flags: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>-l</code>: output matching files' names only * <code>-Z</code>: instead of a new line character, print out a null character after each filename * <code>--include='*.rs'</code>: only examine Rust files In this example, the first command outputs the filenames with null separates, then [[xargs]] is used to feed the filenames into the second grep command, which searches for “TODO”s in those files. === Extracting All Unique Public IPv4 Addresses from Log Files === We can extract all the unique IPv4 addresses from a directory of log files, but exclude any private IP addresses, such as <code>10.x.x.x</code> / <code>192.168.x.x</code>: <syntaxhighlight lang=sh> grep -rhoE '([0-9]{1,3}\.){3}[0-9]{1,3}' /path/to/logs | sort -u | grep -vE '^10\.|^192\.168\.' </syntaxhighlight> Flags: * <code>-r</code>: find files recursively * <code>-h</code>: suppress printing of filenames * <code>-o</code>: show only matching part of line * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] * <code>-v</code>: select non-matching lines For the first pattern: # <code>[0-9]</code> matches the digits (0 to 9 on the ASCII table includes all digits), and <code>{1,3}</code> specifies the length must be between 1 and 3; and # <code>([0-9]{1,3}\.){3}</code> matches exactly 3 times the above followed by a full stop. For the second pattern: # <code>^10\.</code> matches for lines starting with <code>10.</code>; # <code>^192\.168\.</code> matches for lines starting with <code>192.168.</code>; and # <code>|</code> (which indicates “or”) allows matching for the regex specified on the left or the right. Due to the invert flag (<code>-v</code>), if a line matches the second pattern, it is excluded, and other lines are printed instead. == Alternatives == Faster implementations of grep such as '''[[ripgrep]]''' (<code>rg</code>) and '''[[hypergrep]]''' (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU grep, and usually not pre-installed on most distributions. The '''<code>agrep</code>''' tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] f5d05b9084251371f8950475303e907dc2d7935d 2550 2548 2025-06-21T08:37:35Z Madonuko 140 /* History */ fix quotes wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Searching for “PATTERNS” or “regex” in <code>grep --help</code> | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU grep: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, grep’s creation stemmed from Thompson’s need to analyse text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed]] text editor into a standalone tool. He named the tool ''grep'' because in ed, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into grep, which finds all lines with the text “error”. However, grep itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended [[regular expression]]s'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Examples == === Finding Python Function Calls === In a [[Python]] codebase, we can find all calls to functions under the <code>subprocess</code> module with <code>shell=True</code>: $ grep -r --include='*.py' -nHE 'subprocess\.\w+\([^)]*shell=True' ./driver.py:69: return subprocess.call("lspci | grep -q -i NVIDIA", shell=True) == 0 ./driver.py:202: return subprocess.call("lspci | grep -q -i Network | grep -q -i Broadcom", shell=True) == 0 ./driver.py:211: return subprocess.call("lspci | grep -q -i Bluetooth | grep -q -i Broadcom", shell=True) == 0 ./util.py:38: proc = subprocess.Popen(f"chroot {chroot} /tmp/stellar-payload.sh", shell=True) ./util.py:63: # proc = subprocess.Popen(payload, shell=True) ./util.py:66: proc = subprocess.Popen(f"pkexec {tmpfile}", shell=True) (This is run on the [https://github.com/Ultramarine-Linux/stellar/ Ultramarine stellar codebase]) We can breakdown the flags used in this example: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>--include='*.py'</code>: only examine Python files * <code>-n</code>: show line numbers * <code>-H</code>: show file name * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] We can divide the pattern <code>subprocess\.\w+\([^)]*shell=True</code> into many parts: # <code>subprocess</code> matches the string “subprocess” literally; # <code>\.</code> matches the full stop literally; # <code>\w+</code> matches word characters one or more times, where a word character (<code>\w</code>) is any letter, digit or underscore<ref>[https://www.regexroo.com/word-characters Understanding \w and Its Counterpart \W in Regex], RegexRoo.com, 2025 (Accessed: 2025-06-21)</ref>; # <code>\(</code> matches for an open parenthesis <code>(</code> literally; # <code>[^)]*</code> is an inverse character group and matches any characters that are not the closing parenthesis <code>)</code> zero or more times; and # <code>shell=True</code> matches the string “shell=True” literally. === Finding Code Files with TODOs and FIXMEs === We can list out code files that contains both the word “FIXME” and “TODO”. For a Rust project: $ grep -rlZ 'FIXME' --include='*.rs' . | xargs -0 grep -l 'TODO' ./src/pages/_15_installing.rs ./src/main.rs Flags: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>-l</code>: output matching files' names only * <code>-Z</code>: instead of a new line character, print out a null character after each filename * <code>--include='*.rs'</code>: only examine Rust files In this example, the first command outputs the filenames with null separates, then [[xargs]] is used to feed the filenames into the second grep command, which searches for “TODO”s in those files. === Extracting All Unique Public IPv4 Addresses from Log Files === We can extract all the unique IPv4 addresses from a directory of log files, but exclude any private IP addresses, such as <code>10.x.x.x</code> / <code>192.168.x.x</code>: <syntaxhighlight lang=sh> grep -rhoE '([0-9]{1,3}\.){3}[0-9]{1,3}' /path/to/logs | sort -u | grep -vE '^10\.|^192\.168\.' </syntaxhighlight> Flags: * <code>-r</code>: find files recursively * <code>-h</code>: suppress printing of filenames * <code>-o</code>: show only matching part of line * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] * <code>-v</code>: select non-matching lines For the first pattern: # <code>[0-9]</code> matches the digits (0 to 9 on the ASCII table includes all digits), and <code>{1,3}</code> specifies the length must be between 1 and 3; and # <code>([0-9]{1,3}\.){3}</code> matches exactly 3 times the above followed by a full stop. For the second pattern: # <code>^10\.</code> matches for lines starting with <code>10.</code>; # <code>^192\.168\.</code> matches for lines starting with <code>192.168.</code>; and # <code>|</code> (which indicates “or”) allows matching for the regex specified on the left or the right. Due to the invert flag (<code>-v</code>), if a line matches the second pattern, it is excluded, and other lines are printed instead. == Alternatives == Faster implementations of grep such as '''[[ripgrep]]''' (<code>rg</code>) and '''[[hypergrep]]''' (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU grep, and usually not pre-installed on most distributions. The '''<code>agrep</code>''' tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] 4effa18e7e4aba13ec039bd75c2f74d4c2c8d861 0 1 2528 2388 2025-06-20T18:33:36Z Atmois 13 Fix grammer wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. You may also link your '''atl.wiki''' account to your discord account, following [[Atl.wiki:Discord Linking|these instructions]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Our Key Values ====== We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed on our [[Atl.wiki:Contact|Contact]] page. [[File:Atl.wiki CTA.png|center|thumb|960x960px]] __NOTOC__ 1a7a0d54d2c05894ef00a8be5971cee35ec745dd 2529 2528 2025-06-20T18:34:03Z Atmois 13 change image style wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[Atl.wiki:About|about]] page! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[Atl.wiki:Contact|contact page]]. You may also link your '''atl.wiki''' account to your discord account, following [[Atl.wiki:Discord Linking|these instructions]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[Atl.wiki:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[Atl.wiki:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Our Key Values ====== We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed on our [[Atl.wiki:Contact|Contact]] page. [[File:Atl.wiki CTA.png|center|frameless|960x960px]] __NOTOC__ 2d83e38976aa5ef9c640ae86bf6e2485a5e72505 0 345 2532 2048 2025-06-20T18:40:03Z Ivanovics 150 extend article (short article may not be needed anymore, unsure) wikitext text/x-wiki {{Cleanup|Short article}}{{Needs Citations}} Kernel Modules are pieces of code that can be loaded directly into the [[Kernel]] at runtime to extend functionality.<ref>https://linux-kernel-labs.github.io/refs/heads/master/labs/kernel_modules.html</ref> The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your [[Linux Distributions|Distribution]], as such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically older ones benefit the most) at the cost of new devices potentially not working when added. It is also possible to compile a Linux kernel on a pre-existing system to only use needed Kernel modules. == Obtaining information == Modules depend on the kernel release and the kernels version, though usually they are stored in <code>/usr/lib/modules/''kernel_release_version''</code>''.'' To see which modules are loaded, <code>lsmod</code> can be used. Obtaining information is achievable with <code>modinfo <module_name></code> == Module loading == === Automatic loading === Usually most needed modules are handled [[udev]], so usually out of tree modules arent needed, though there are cases where loading or blacklisting a module is needed for your setup to function properly. Early module loading is generally handled by your [[initramfs]] generator of choice, usually dracut, booster or mkinitcpio. Alternatively, [[systemd]] will load modules explicitly listed in <code>/etc/modules-load.d/</code> ,with the naming scheme of <code>/etc/modules-load.d/program.conf</code>. Lines starting with ; or # are parsed as comments and ignored === Manual loading === Kernel modules can be manually loaded with <code>modprobe <module_name></code>, or loading a module that by file name (i.e. modules that are not installed in <code>/usr/lib/modules/<kernel_release_version></code>) can be achieved either of the following ways:<syntaxhighlight lang="sh"> insmod file_name module_options modprobe file_name </syntaxhighlight>Removing a module can be achieved by:<syntaxhighlight lang="sh"> rmmod module_name modprobe -r module_name modprobe --remove module_name </syntaxhighlight> [[Category:Terminology]] 76aa86d33c24e533dbca44566285f86fd3ccc04b 8 624 2535 2387 2025-06-20T19:42:03Z Atmois 13 add CSS for nav btns css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all types of links, */ a, a:visited, .external, .external:visited, .mw-redirect, .new { text-decoration: underline; } /* Home page button grid, adapted from https://consumerrights.wiki/MediaWiki:Common.css */ .nav-btn-grid a{ text-decoration: none; } .nav-btn:active{ border-color: var( --color-base--active, #404244 ) !important; } @media screen { html.skin-theme-clientpref-night .nav-btn:active{ border: 2px solid var( --color-base--hover, #404244 ) !important; } } @media screen and (prefers-color-scheme: dark) { /* automatic mode */ html.skin-theme-clientpref-os .nav-btn:active { border: 2px solid var( --color-base--hover, #404244 ) !important; } } @media (hover: hover) { .nav-btn:hover{ border-color: var( --color-base--hover, #404244 ) !important; transform: scale(1.03); } html.skin-theme-clientpref-night .nav-btn:hover{ border: 2px solid var( --color-base--hover, #404244 ) !important; } } @media (hover: hover) and (prefers-color-scheme: dark) { html.skin-theme-clientpref-os .nav-btn:hover{ border: 2px solid var( --color-base--hover, #404244 ) !important; } } 9d40792aba651379c97d03b34c35276db834bde8 2539 2535 2025-06-20T19:50:38Z Atmois 13 remove navbtn stff css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all types of links, */ a, a:visited, .external, .external:visited, .mw-redirect, .new { text-decoration: underline; } d87661027eaafdce0e51cefca6f33b691b5f3619 0 663 2553 2490 2025-06-21T17:02:30Z Madonuko 140 more about the /* Infrastructure */ wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terra.fyralabs.com terra.fyralabs.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora]] Linux and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terra.fyralabs.com/ Terra], Terra, 2024 (Accessed: 2025-06-19)</ref> Developed by Fyra Labs, it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://developer.fyralabs.com/terra/infrastructure How Terra Works], Fyra Labs, 2025 (Accessed: 2025-06-19)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://developer.fyralabs.com/terra/installing. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji], RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://developer.fyralabs.com/terra/autoupdate Automatic Updates - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases :: Fedora Docs], Fedora, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably [[Rust]], [[Go]], [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://developer.fyralabs.com/terra/policy Policy – Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> == See Also == * [https://terra.fyralabs.com Main Website] * [https://developer.fyralabs.com/terra Fyra Developer Documentations for Terra] * [https://github.com/terrapkg/packages Terra Sources] 52aad40c36ac58d038b169ce069f99fda3c4b1d2 0 668 2554 2549 2025-06-21T17:46:43Z Madonuko 140 /* Syntax */ wip wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor ed (1971) and the even earlier qed (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<filter#1>''{''<command#1>''; ''<command#2>''; …} While at least 1 command is needed, filtering is optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<filter#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === This list is currently not exhaustive and is a work in progress. * <code>s/''<target>''/''<replace>''/''<flags>''</code> performs '''substitution'''. If <code>g</code> (''global'') is specified in ''<flags'', all matches of the pattern ''<target>'' are replaced as specified by the ''<replace>'' pattern. Otherwise, only the first match in each line (if there is one) is substituted. :* e.g.: <code>sed 's@red@blue@g'</code> replaces all matches of “red” (including in the word “Fred”) with “blue” (⇒ “Fblue”). :* e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces all matches of the word “dog” with “cat” correctly, avoiding the above issue. * <code>d</code> '''deletes''' lines. Without a filter, this deletes all lines. :* e.g.: <code>sed '/secret/d'</code> deletes lines with the text “secret”. * <code>p</code> '''prints''' out lines. Since sed by default prints out the lines already, this prints out the lines again. However, with the <code>-n</code> command-line flag, sed does not print out processed lines without the use of the <code>p</code> command. :* e.g.: <code>sed -n '/^secret/p'</code> prints out only lines starting with “secret”. * <code>a</code> '''appends''' new lines. This command is ''greedy''. :* e.g.: <code>1a Hello</code> appends a new line “Hello” between line 1 and 2. * <code>i</code> '''inserts''' new lines. This command is ''greedy''. :* e.g.: <code>1i Hello</code> inserts a new line “Hello” before line 1. * <code>c</code> '''changes''' whole lines. This command is ''greedy''. :* e.g.: <code>1c Hello</code> changes line 1 to just “Hello”. === Filters === This list is currently not exhaustive and is a work in progress. * <code>/''<regex>''/</code> only performs the actions on lines that match the given regex. :* In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] eebe4ed9f8c4be9dd620a39f07a11bd832327e97 2580 2554 2025-06-24T11:59:32Z Madonuko 140 /* Commands */ document everything wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor ed (1971) and the even earlier qed (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<filter#1>''{''<command#1>''; ''<command#2>''; …} While at least 1 command is needed, filtering is optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<filter#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). :* e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). :* e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. :* e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. :* e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. :* e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. :* e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. :This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. :* e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. :* e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). :* e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. :* e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. :* e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. :* e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. :* e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. :* e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. :* e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. :* e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. :* e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. :* e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. :* e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). :* e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. :* e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. :* e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). :* e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). :* e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. :* e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. :* e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. :* e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept '''addresses''' (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy”—text arguments span lines until an unescaped newline. :* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing <code>Esc</code> and then <code>Enter</code> separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Filters === This list is currently not exhaustive and is a work in progress. * <code>/''<regex>''/</code> only performs the actions on lines that match the given regex. :* In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang=“sh” line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang=“sh” line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang=“sh” line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 91790083c72c569e878dfc352163a94e1df1d6f9 2581 2580 2025-06-24T13:33:48Z Madonuko 140 fix sh wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor ed (1971) and the even earlier qed (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[https://en.wikipedia.org/wiki/Sed sed - Wikipedia], Wikipedia, 2025 (Accessed 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<filter#1>''{''<command#1>''; ''<command#2>''; …} While at least 1 command is needed, filtering is optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<filter#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). :* e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). :* e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. :* e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. :* e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. :* e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. :* e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. :This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. :* e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. :* e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). :* e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. :* e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. :* e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. :* e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. :* e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. :* e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. :* e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. :* e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. :* e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. :* e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. :* e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). :* e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. :* e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. :* e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). :* e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). :* e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. :* e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. :* e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. :* e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept '''addresses''' (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy”—text arguments span lines until an unescaped newline. :* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing <code>Esc</code> and then <code>Enter</code> separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Filters === This list is currently not exhaustive and is a work in progress. * <code>/''<regex>''/</code> only performs the actions on lines that match the given regex. :* In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] be2abf85c968a835e5d46486a832d6bb46ad593b 2582 2581 2025-06-24T13:47:07Z Hog 161 Normalised Citations wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor ed (1971) and the even earlier qed (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<filter#1>''{''<command#1>''; ''<command#2>''; …} While at least 1 command is needed, filtering is optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<filter#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). :* e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). :* e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. :* e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. :* e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. :* e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. :* e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. :This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. :* e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. :* e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). :* e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. :* e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. :* e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. :* e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. :* e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. :* e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. :* e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. :* e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. :* e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. :* e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. :* e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). :* e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. :* e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. :* e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). :* e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). :* e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. :* e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. :* e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. :* e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept '''addresses''' (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy”—text arguments span lines until an unescaped newline. :* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing <code>Esc</code> and then <code>Enter</code> separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Filters === This list is currently not exhaustive and is a work in progress. * <code>/''<regex>''/</code> only performs the actions on lines that match the given regex. :* In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 74d5c744e2579d7393b3c0ccf8be805deec567b9 2599 2582 2025-06-25T10:55:51Z Madonuko 140 /* Addresses */ wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor ed (1971) and the even earlier qed (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; …} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[addresses|#addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy”—text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10—20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to [[EOF]]. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10-15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] e3982ef191ac66ec5439225a6afdbe19e54bad8b 2600 2599 2025-06-25T11:08:57Z Madonuko 140 add a summary table I guess wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2013-05-21)</ref> It was based on the scripting features of the earlier interactive editor ed (1971) and the even earlier qed (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; …} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to [[EOF]]. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10-15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 81f8179e9004c32929b82f3b695b02583249e314 0 677 2555 2025-06-22T00:10:38Z Tatiana 166 page created with key points wikitext text/x-wiki Flatpak is a universal packaging system and runtime for installing packages separate from the system packages. Mainly meant for desktop applications, Flatpak allows application developers to distribute packages without needing to worry about distro compatibility because Flatpak installs it's own runtime dependencies. It claims to improve security through sandboxing providing the user the ability to give or revoke permissions for a given application. Flatpak is installed by default on many distributions and it's main distribution platform is Flathub. == Installation == Flatpak comes preinstalled on many distributions such as Linux Mint and Fedora but can be installed through most distro's package repositories if not present. ==== KDE Discover ==== KDE Discover includes the ability to install Flatpak and enable Flathub through its graphical user interface. Go to the setting tab and install the Flatpak backend then restart Discover then go back to the settings and enable Flathub. ==== CLI Install on Ubuntu ==== To install Flatpak from the CLI run:<syntaxhighlight lang="bash"> sudo apt install flatpak </syntaxhighlight>To enable Flathub from the CLI run:<syntaxhighlight lang="bash"> flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo </syntaxhighlight>If you make use of GNOME Software you can install the integration plugin:<syntaxhighlight lang="bash"> sudo apt install gnome-software-plugin-flatpak </syntaxhighlight>For the KDE Discover plugin run:<syntaxhighlight lang="bash"> sudo apt install plasma-discover-backend-flatpak </syntaxhighlight>For other distros read the guides on [https://flathub.org/setup Flathub.org]. == Compatibility == Flatpak allows improved package compatibility through its use of it's own runtime dependencies. Packages can run through Flatpak where it might not be possible to run on natively such as: * Applications that require a newer version of glibc than whats available on an stable release distro such as Rocky Linux 8. * Applications that depend on glibc such as Steam running on a distro using musl like Alpine Linux. * Multilib packages such as Steam or Wine on distros without multilib support such as CentOS Stream 10. == Sandboxing == Package permissions can be managed by the user through a graphical user interface with Flatseal which can be installed as a Flatpak. == Flathub Package Verification == Flathub has a package verification system that allows packages maintained by the official developers to have a verification tick<ref>[https://docs.flathub.org/docs/for-app-authors/verification]</ref>. This has lead to some confusion where verification is mistaken for package safety. Linux Mint hides unverified Flatpaks from Software Manager by default Starting in version 22<ref>[https://www.omgubuntu.co.uk/2024/06/linux-mint-will-hide-unverified-flatpaks]</ref>. 4c789ef71cc7b974436527fe9a8c80d740cb74f4 2556 2555 2025-06-22T05:58:37Z Madonuko 140 fix references wikitext text/x-wiki Flatpak is a universal packaging system and runtime for installing packages separate from the system packages. Mainly meant for desktop applications, Flatpak allows application developers to distribute packages without needing to worry about distro compatibility because Flatpak installs it's own runtime dependencies. It claims to improve security through sandboxing providing the user the ability to give or revoke permissions for a given application. Flatpak is installed by default on many distributions and it's main distribution platform is Flathub. == Installation == Flatpak comes preinstalled on many distributions such as Linux Mint and Fedora but can be installed through most distro's package repositories if not present. ==== KDE Discover ==== KDE Discover includes the ability to install Flatpak and enable Flathub through its graphical user interface. Go to the setting tab and install the Flatpak backend then restart Discover then go back to the settings and enable Flathub. ==== CLI Install on Ubuntu ==== To install Flatpak from the CLI run:<syntaxhighlight lang="bash"> sudo apt install flatpak </syntaxhighlight>To enable Flathub from the CLI run:<syntaxhighlight lang="bash"> flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo </syntaxhighlight>If you make use of GNOME Software you can install the integration plugin:<syntaxhighlight lang="bash"> sudo apt install gnome-software-plugin-flatpak </syntaxhighlight>For the KDE Discover plugin run:<syntaxhighlight lang="bash"> sudo apt install plasma-discover-backend-flatpak </syntaxhighlight>For other distros read the guides on [https://flathub.org/setup Flathub.org]. == Compatibility == Flatpak allows improved package compatibility through its use of it's own runtime dependencies. Packages can run through Flatpak where it might not be possible to run on natively such as: * Applications that require a newer version of glibc than whats available on an stable release distro such as Rocky Linux 8. * Applications that depend on glibc such as Steam running on a distro using musl like Alpine Linux. * Multilib packages such as Steam or Wine on distros without multilib support such as CentOS Stream 10. == Sandboxing == Package permissions can be managed by the user through a graphical user interface with Flatseal which can be installed as a Flatpak. == Flathub Package Verification == Flathub has a package verification system that allows packages maintained by the official developers to have a verification tick<ref>[https://docs.flathub.org/docs/for-app-authors/verification Verification | Flathub Documentation], Flathub Team, 2025 (Accessed: 2025-06-22)</ref>. This has lead to some confusion where verification is mistaken for package safety. Linux Mint hides unverified Flatpaks from Software Manager by default Starting in version 22<ref>[https://www.omgubuntu.co.uk/2024/06/linux-mint-will-hide-unverified-flatpaks Linux Mint Will Hide Unverified Flatpaks in Software Manager - OMG! Ubuntu], Joey Sneddon, 2024 (Accessed: 2025-06-22)</ref>. b07ee250d9d107e840d67fa2e907293976f117fc 6 678 2557 2025-06-22T06:13:06Z Madonuko 140 CC-BY-3.0 https://git-scm.com/downloads/logos wikitext text/x-wiki == Summary == CC-BY-3.0 https://git-scm.com/downloads/logos a40a3fd2e0c142696aa272413e461fed56818cf6 0 679 2558 2025-06-22T06:54:42Z Madonuko 140 init wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = <code>git</code> | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git’s early design emphasized a distributed workflow similar to BitKeeper’s but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like GitHub, which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> 3afe2bd2ba4d66abe596fbcd0864167e77b39e93 2566 2558 2025-06-22T09:35:28Z Madonuko 140 /* Usage */ init wip wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = <code>git</code> | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git’s early design emphasized a distributed workflow similar to BitKeeper’s but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like GitHub, which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. For example, to switch to the master branch: git checkout master To create and switch to the develop branch: git checkout -b develop To create and switch to the feature branch based on the develop branch: git checkout -b feature develop To obtain files from the develop branch into the current working directory: git checkout develop -- file1 file2 To discard changes in the current working directory: git checkout -- file1 file2 9e78ec50fb19f012e18857c68da6295c52e887e4 2601 2566 2025-06-25T11:15:45Z Madonuko 140 /* Checkout */ make content into table wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = <code>git</code> | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git’s early design emphasized a distributed workflow similar to BitKeeper’s but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like GitHub, which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} f7d118144d114be2281c4887a59208aa30e0c69f 10 482 2559 1916 2025-06-22T08:05:59Z Atmois 13 Update text wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section lists commands or instructions which could potentially damage your system. Please ensure you understand the commands or instructions you are running or following before you run or follow them.</span> <div class="mbox-text">This warning exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[Atl.wiki:About#Staff|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> f41daea24997dc81f13cc9c3a45af0ac23970ca5 0 424 2560 2003 2025-06-22T08:17:06Z Atmois 13 remove cleanup template wikitext text/x-wiki = AWK = AWK is a programming language focused primarily on textual data processing<ref>[https://www.gnu.org/software/gawk/manual/html_node/] Top (The GNU Awk User's Guide)</ref>, though it can be used for other general-purpose tasks. This page will focus primarily on GNU Awk, or GAWK/<code>gawk</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/], Although the language name is officially stylized AWK, GNU officially uses the stylization Awk. They also acknowledge that the language itself is spelled AWK.</ref>. == Basic Usage == One of the most basic ways to use AWK is in a pipe to filter columnar data. For example, <code>cat file.txt | awk '{ print $1 }'</code> will print the first (space-delimited) column of a given file. This can be generalized to the second, third, etc. columns using <code>$2</code>, <code>$3</code>, etc. respectively. AWK can also be ran with <code>awk 'program-here' input-file1 input-file2 ...</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/One_002dshot.html] One-shot (The GNU Awk User's Guide)</ref>, so the above example with <code>cat</code> could also be written as: <pre> awk '{ print $1 }' file.txt </pre>More usage examples can be found on the [https://www.gnu.org/software/gawk/manual/html_node/Command-Line.html GAWK manual page], as well as AWK's [https://www.gnu.org/software/gawk/manual/html_node/Options.html many command-line options]. == AWK as a Language == AWK can also be used as a programming language. AWK programs consist of a list of patterns followed by actions to perform for each of those patterns<ref>[https://www.gnu.org/software/gawk/manual/html_node/Getting-Started.html] Getting Started (The GNU Awk User's Guide)</ref>: <pre> pattern { action } pattern { action } ... </pre> === BEGIN and END === Two common patterns are <code>BEGIN</code> and <code>END</code>, which run the given action before and after any text is processed respectively. These are called the "startup" and "cleanup" actions<ref>[https://www.gnu.org/software/gawk/manual/html_node/Using-BEGIN_002fEND.html] Using BEGIN/END (The GNU Awk User's Guide)</ref>. For example, the following code will print "Hello, World!": <pre> awk 'BEGIN { print "Hello, World!" }' </pre> The following will accept input until an EOF (inputtable in many shells as Ctrl+D), then print "Hello, World!": <pre> awk 'END { print "Hello, World!" }' </pre> === Regex Pattern === AWK can also be used to run a command for every line that matches a given regular expression. The following example prints every line that contains "regex" (equivalent to <code>grep 'regex'</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Regexp-Usage.html] Regexp Usage (The GNU Awk User's Guide)</ref>:<syntaxhighlight lang="awk"> /regex/ { print } </syntaxhighlight>The <code>{ print }</code> is actually implicit, meaning it can also be written:<syntaxhighlight lang="awk"> /regex/ </syntaxhighlight>One can combine this with <code>$1</code>, <code>$2</code>, etc. to print the second column of every row containing a given string, for example:<syntaxhighlight lang="awk"> /regex/ { print $2 } </syntaxhighlight> === Operations === AWK can be used to perform operations seen in many other programming languages, such as addition (<code>+</code>), subtraction (<code>-</code>), multiplication (<code>*</code>), division (<code>/</code>), modulus (<code>%</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Arithmetic-Ops.html] Arithmetic Ops (The GNU Awk User's Guide)</ref>, variable assignment (<code>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Assignment-Ops.html] Assignment Ops (The GNU Awk User's Guide)</ref>, equality (<code>==</code>) and inequality checks (<code>!=</code>), and comparisons (<code><</code>, <code><=</code>, <code>></code>, <code>>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Comparison-Operators.html] Comparison Operators (The GNU Awk User's Guide)</ref>. === ARGC and ARGV === Like many other programming languages, AWK programs can parse command-line arguments. The <code>ARGC</code> and <code>ARGV</code> variables (among [https://www.gnu.org/software/gawk/manual/html_node/Built_002din-Variables.html many others]) store the count of the arguments and an array of the arguments respectively<ref>[https://www.gnu.org/software/gawk/manual/html_node/Auto_002dset.html#index-ARGC_002fARGV-variables] ARGC, ARGV - Auto-set (The GNU Awk User’s Guide)</ref>. <references /> [[Category:Software]] [[Category:Programming Languages]] f1287c90efb6f01c7c68d455877f13eeff220ec9 3001 669 2561 2516 2025-06-22T08:34:48Z Atmois 13 /* What Counts as a “Guide” */ Reply wikitext text/x-wiki == What Counts as a “Guide” == I don’t agree with some of the [[Template:Cleanup]]s mentioning splitting pages into guides, e.g. the one in the [[AWK]] page. Personally I think a “guide” is a set of instructions guiding readers on how to perform specific tasks. That’s not what’s happening in the awk page. It’s just providing examples on how to use the program. It doesn’t really achieve anything. The main problem here is '''we need a definition on “guide”'''. That is, the '''criteria'''. I think the main deciding factor is that within a guide, you need to perform steps (e.g. [[Guides:Installing Niri]], [[Guides:Setting up Flathub on Fedora]]), as opposed to just discrete documentations ([[Guides:Input method]]). Or reversely, if the [[Template:Guide Warning]] just doesn’t make sense on the page (because… like, the input method page barely has any instructions other than just maybe… like, may~be “hey there’s this package and there’s that package that you could install”), then it really shouldn’t be in [[Guides]] I think. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 09:11, 20 June 2025 (UTC) :The original purpose of Guides was to clearly separate the moderation of commands and instructions to avoid potentially malicious commands being spread via the wiki, this was achieved by outright forbidding commands on non-guide pages (Which have more lax moderation, such as lacking approvals). However, it is clunky and can create a divide. :The issue is it's a hard line to put down, and what do we deem specifically needing a guide or being fine in an article with the small warning template. [[Guides:Input method]] for example doesn't list commands or is focused around a step-by-step guide to do something, but it still is a set of instructions/documentation of a sort. For the [[AWK]] page, I have removed the template, as I do agree that is fine on its informational article. :Following the hardline approach comes with the advantage, it's a very clear line and makes a clear divide but can be excessively strict and create guides which could literally be one-liners or are actually a replica of the man page. On the contrary, following the softer approach does slightly increase the risk of not being able to moderate it as effectively, but this will become a lesser issue as the wiki grows, and more eyes are on it. :I think what needs to be found is a good middle ground that can easily be defined and upheld of what constitutes its own page and what does not, I think one-liners such as on the [[Terra]] page with the template are fine as they are, but i'm not sure about the [[Guides:Input method]] page being an informational article or essentially creating a man page on the main article pages as their style is aiming to be similar as to what a Wikipedia article is. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 08:34, 22 June 2025 (UTC) a32ca43ce72446d2daffccd7cab105eb5f7863e3 2562 2561 2025-06-22T08:35:28Z Atmois 13 /* What Counts as a “Guide” */ format fix wikitext text/x-wiki == What Counts as a “Guide” == I don’t agree with some of the [[Template:Cleanup]]s mentioning splitting pages into guides, e.g. the one in the [[AWK]] page. Personally I think a “guide” is a set of instructions guiding readers on how to perform specific tasks. That’s not what’s happening in the awk page. It’s just providing examples on how to use the program. It doesn’t really achieve anything. The main problem here is '''we need a definition on “guide”'''. That is, the '''criteria'''. I think the main deciding factor is that within a guide, you need to perform steps (e.g. [[Guides:Installing Niri]], [[Guides:Setting up Flathub on Fedora]]), as opposed to just discrete documentations ([[Guides:Input method]]). Or reversely, if the [[Template:Guide Warning]] just doesn’t make sense on the page (because… like, the input method page barely has any instructions other than just maybe… like, may~be “hey there’s this package and there’s that package that you could install”), then it really shouldn’t be in [[Guides]] I think. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 09:11, 20 June 2025 (UTC) :The original purpose of Guides was to clearly separate the moderation of commands and instructions to avoid potentially malicious commands being spread via the wiki, this was achieved by outright forbidding commands on non-guide pages (Which have more lax moderation, such as lacking approvals). However, it is clunky and can create a divide. The issue is it's a hard line to put down, and what do we deem specifically needing a guide or being fine in an article with the small warning template. [[Guides:Input method]] for example doesn't list commands or is focused around a step-by-step guide to do something, but it still is a set of instructions/documentation of a sort. For the [[AWK]] page, I have removed the template, as I do agree that is fine on its informational article. Following the hardline approach comes with the advantage, it's a very clear line and makes a clear divide but can be excessively strict and create guides which could literally be one-liners or are actually a replica of the man page. On the contrary, following the softer approach does slightly increase the risk of not being able to moderate it as effectively, but this will become a lesser issue as the wiki grows, and more eyes are on it. I think what needs to be found is a good middle ground that can easily be defined and upheld of what constitutes its own page and what does not, I think one-liners such as on the [[Terra]] page with the template are fine as they are, but i'm not sure about the [[Guides:Input method]] page being an informational article or essentially creating a man page on the main article pages as their style is aiming to be similar as to what a Wikipedia article is. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 08:34, 22 June 2025 (UTC) f8afab2734ab72ce9a88ad7804563579e0214b2c 2563 2562 2025-06-22T08:35:54Z Atmois 13 format fix p2 wikitext text/x-wiki == What Counts as a “Guide” == I don’t agree with some of the [[Template:Cleanup]]s mentioning splitting pages into guides, e.g. the one in the [[AWK]] page. Personally I think a “guide” is a set of instructions guiding readers on how to perform specific tasks. That’s not what’s happening in the awk page. It’s just providing examples on how to use the program. It doesn’t really achieve anything. The main problem here is '''we need a definition on “guide”'''. That is, the '''criteria'''. I think the main deciding factor is that within a guide, you need to perform steps (e.g. [[Guides:Installing Niri]], [[Guides:Setting up Flathub on Fedora]]), as opposed to just discrete documentations ([[Guides:Input method]]). Or reversely, if the [[Template:Guide Warning]] just doesn’t make sense on the page (because… like, the input method page barely has any instructions other than just maybe… like, may~be “hey there’s this package and there’s that package that you could install”), then it really shouldn’t be in [[Guides]] I think. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 09:11, 20 June 2025 (UTC) :The original purpose of Guides was to clearly separate the moderation of commands and instructions to avoid potentially malicious commands being spread via the wiki, this was achieved by outright forbidding commands on non-guide pages (Which have more lax moderation, such as lacking approvals). However, it is clunky and can create a divide. :The issue is it's a hard line to put down, and what do we deem specifically needing a guide or being fine in an article with the small warning template. [[Guides:Input method]] for example doesn't list commands or is focused around a step-by-step guide to do something, but it still is a set of instructions/documentation of a sort. For the [[AWK]] page, I have removed the template, as I do agree that is fine on its informational article. :Following the hardline approach comes with the advantage, it's a very clear line and makes a clear divide but can be excessively strict and create guides which could literally be one-liners or are actually a replica of the man page. On the contrary, following the softer approach does slightly increase the risk of not being able to moderate it as effectively, but this will become a lesser issue as the wiki grows, and more eyes are on it. :I think what needs to be found is a good middle ground that can easily be defined and upheld of what constitutes its own page and what does not, I think one-liners such as on the [[Terra]] page with the template are fine as they are, but i'm not sure about the [[Guides:Input method]] page being an informational article or essentially creating a man page on the main article pages as their style is aiming to be similar as to what a Wikipedia article is. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 08:34, 22 June 2025 (UTC) f4ee1664d5b7ff77f55b45cac23356c9ae7e8d64 2567 2563 2025-06-22T09:48:28Z Madonuko 140 /* What Counts as a “Guide” */ Reply wikitext text/x-wiki == What Counts as a “Guide” == I don’t agree with some of the [[Template:Cleanup]]s mentioning splitting pages into guides, e.g. the one in the [[AWK]] page. Personally I think a “guide” is a set of instructions guiding readers on how to perform specific tasks. That’s not what’s happening in the awk page. It’s just providing examples on how to use the program. It doesn’t really achieve anything. The main problem here is '''we need a definition on “guide”'''. That is, the '''criteria'''. I think the main deciding factor is that within a guide, you need to perform steps (e.g. [[Guides:Installing Niri]], [[Guides:Setting up Flathub on Fedora]]), as opposed to just discrete documentations ([[Guides:Input method]]). Or reversely, if the [[Template:Guide Warning]] just doesn’t make sense on the page (because… like, the input method page barely has any instructions other than just maybe… like, may~be “hey there’s this package and there’s that package that you could install”), then it really shouldn’t be in [[Guides]] I think. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 09:11, 20 June 2025 (UTC) :The original purpose of Guides was to clearly separate the moderation of commands and instructions to avoid potentially malicious commands being spread via the wiki, this was achieved by outright forbidding commands on non-guide pages (Which have more lax moderation, such as lacking approvals). However, it is clunky and can create a divide. :The issue is it's a hard line to put down, and what do we deem specifically needing a guide or being fine in an article with the small warning template. [[Guides:Input method]] for example doesn't list commands or is focused around a step-by-step guide to do something, but it still is a set of instructions/documentation of a sort. For the [[AWK]] page, I have removed the template, as I do agree that is fine on its informational article. :Following the hardline approach comes with the advantage, it's a very clear line and makes a clear divide but can be excessively strict and create guides which could literally be one-liners or are actually a replica of the man page. On the contrary, following the softer approach does slightly increase the risk of not being able to moderate it as effectively, but this will become a lesser issue as the wiki grows, and more eyes are on it. :I think what needs to be found is a good middle ground that can easily be defined and upheld of what constitutes its own page and what does not, I think one-liners such as on the [[Terra]] page with the template are fine as they are, but i'm not sure about the [[Guides:Input method]] page being an informational article or essentially creating a man page on the main article pages as their style is aiming to be similar as to what a Wikipedia article is. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 08:34, 22 June 2025 (UTC) ::I think you've made me realise the current input method page is just a gigantic mess and really should be split apart, because it currently serves both as a guide and an informational article. ::But assuming my page is just an outlier, there's a bit of a contradiction on the moderation part: why not in the first place moderate and check all articles instead of just the ones in the guides category? Isn't that basically what you guys have been doing? ::I think the rule can be formalised as something like this: ::# if there's a set of instructions, you need the warning template; ::# if the instructions are more than 2000 bytes, separate it into a guide page; and ::# guide pages should not be informational. ::— [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 09:48, 22 June 2025 (UTC) 6da2c98c199510b3dfe915b40f98956d62fa7b7d 6 680 2564 2025-06-22T09:15:10Z Madonuko 140 wikitext text/x-wiki == Licensing == {{CC0}} 3f16ad18d78614720e9f206e6115a53bd34db67d 2565 2564 2025-06-22T09:18:48Z Madonuko 140 Madonuko uploaded a new version of [[File:Git merge rebase squash explained.png]] wikitext text/x-wiki == Licensing == {{CC0}} 3f16ad18d78614720e9f206e6115a53bd34db67d 2 681 2568 2025-06-23T00:02:04Z Gurov 103 Created page with "Hi" wikitext text/x-wiki Hi 94dd9e08c129c785f7f256e82fbe0a30e6d1ae40 0 682 2569 2025-06-23T11:40:48Z Hog 161 made a very small page for puppy linux wikitext text/x-wiki '''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003.{{DistributionInfobox|title=Puppy Linux|image=[[File:Puppy logo.svg|Puppy Linux Logo]]|caption=Puppy Linux Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=[[ICEWM]]|usagetype=Desktop|architectures=x86_64, x86, ARM|website=[https://puppylinux-woof-ce.github.io/ Link]}} d58a1d55be50ec8d76c2981956bae13157b6e5e4 2 683 2570 2025-06-23T11:49:20Z Hog 161 Added FarCotten :33333 wikitext text/x-wiki FarCotten (AKA: Nearcotten, Closecotten, MediumDistanceCotten, CottenEyeJoe, CottenCandy, Fartcotten, ShartCotten, FarFromGrass, FarFromWomen, FantaCotten, FastCotten, ETC) is an administrator for the ATL discord c3c6c5ecaed060d69c613781030c178d77512b4d 2572 2570 2025-06-23T12:26:09Z Atmois 13 Revert changes wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 2 655 2571 2444 2025-06-23T11:55:13Z Hog 161 wikitext text/x-wiki [[File:Sus scrofa f domesticus - Réserve africaine de Sigean 01.jpg|thumb|Photo of a hog i like]] I probably fixed your article bozo. 3c3b992dae117cdaa1a690c0156c1185d5d1dd24 0 257 2574 2360 2025-06-24T09:25:29Z Hog 161 Ported instructions over wikitext text/x-wiki {{Needs Citations}} {{Cleanup|Installation instructions should be separated onto its own page in the Guides namespace}} {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=C++|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window managers that aim for pure eye candy with nice animations, smooth looks and its own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) [[Category:Wayland_Compositors]] d9aed38fa5bb012384cd7264590f1abe9c3c02b2 3000 684 2575 2025-06-24T09:25:45Z Hog 161 Created page with "This section will change overtime, as such, you should probably follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a blee..." wikitext text/x-wiki This section will change overtime, as such, you should probably follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. ea14e8d7e07b2b2aa8d61aa56738891e3bcf2b7e 0 239 2576 2153 2025-06-24T09:42:40Z Hog 161 Ported instructions over and added links wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], [[C]] | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]]IceWM is a fast, simple and light X11 [[Window Management System|window manager]]. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. [[Category:X_Window_Managers]] <references /> 482da2e0800090823df76c2606a943b7d12c2265 3000 685 2577 2025-06-24T09:42:57Z Hog 161 instruction page created wikitext text/x-wiki IceWM can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions:<syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/</ref><syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> a9b53cda4dc1f3f224ea13735ad37acd95079bf1 2578 2577 2025-06-24T09:43:59Z Hog 161 cleaned up citations wikitext text/x-wiki IceWM can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions:<syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/ Official Website, 2025 (Fetched 24th June 2025)</ref><syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> a179d1862ba615272bdbf4557ac28cd9810431ba 0 263 2579 2437 2025-06-24T09:48:58Z Hog 161 cleaned up citations wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.99.0, 2024-10-24 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|thumb|The Hyfetch Pride Month easter egg.]] Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your [[Operating System|operating system]], [[:Category:Software|software]] and [[hardware]] with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch Hyfetch Github 2025 (fetched 24th June 2024)</ref> === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. <references /> [[Category:Software]] 4072802d52affc06ae00992b75f2fb87e71e40c0 1 686 2583 2025-06-24T13:47:53Z Hog 161 /* Citation 2. */ new section wikitext text/x-wiki == Citation 2. == Is the date accurate for the accessed? [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 13:47, 24 June 2025 (UTC) 9208fdab459efb16d50e1364ef79742cd31bd55e 10 687 2584 2025-06-24T13:48:13Z Atmois 13 Copy keypress template from wikipedia wikitext text/x-wiki <includeonly>{{{{{♥|safesubst:}}}#invoke:key|keypress}}</includeonly><noinclude> {{/doc}} </noinclude> 6a95ad64d3256bcc85a6235e5aa0e87e61330dbb 2591 2584 2025-06-24T14:01:55Z Atmois 13 Correct link wikitext text/x-wiki <includeonly>{{safesubst:#invoke:Key_Press|keypress}}</includeonly><noinclude> {{/doc}} </noinclude> a1e518549ebb40b4b5489c958f5a2f7ba9f5d947 10 688 2585 2025-06-24T13:50:30Z Atmois 13 Add source link wikitext text/x-wiki Adapted from https://en.wikipedia.org/wiki/Template:Key_press 66fb39e33a100ec30027c0eb6633775ec1362ce8 828 689 2586 2025-06-24T13:52:47Z Atmois 13 Import key press module from wikipedia Scribunto text/plain -- This module implements {{key press}}. local kbdPrefix = '<kbd class="keyboard-key nowrap">' local kbdSuffix = '</kbd>' local keyText = { ['caps lock'] = '⇪ Caps Lock', ['[[caps lock]]'] = '⇪ [[Caps Lock]]', ['shift'] = '⇧ Shift', ['[[shift key|shift]]'] = '⇧ [[Shift key|Shift]]', ['enter'] = '↵ Enter', ['[[enter key|enter]]'] = '↵ [[Enter key|Enter]]', ['cmd'] = '⌘ Cmd', ['[[command key|cmd]]'] = '⌘ [[Command key|Cmd]]', ['command'] = '⌘ Command', ['[[command key|command]]'] = '⌘ [[Command key|Command]]', ['opt'] = '⌥ Opt', ['[[option key|opt]]'] = '⌥ [[Option key|Opt]]', ['option'] = '⌥ Option', ['[[option key|option]]'] = '⌥ [[Option key|Option]]', ['tab'] = 'Tab ↹', ['[[tab key|tab]]'] = '[[Tab key|Tab]] ↹', ['backspace'] = '← Backspace', ['[[backspace]]'] = '← [[Backspace]]', ['win'] = '⊞ Win', ['[[windows key|win]]'] = '⊞ [[Windows key|Win]]', ['menu'] = '≣ Menu', ['[[menu key|menu]]'] = '≣ [[Menu key|Menu]]', ['up'] = '↑', ['[[arrow keys|up]]'] = '[[Arrow keys|↑]]', ['down'] = '↓', ['[[arrow keys|down]]'] = '[[Arrow keys|↓]]', ['left'] = '←', ['[[arrow keys|left]]'] = '[[Arrow keys|←]]', ['right'] = '→', ['[[arrow keys|right]]'] = '[[Arrow keys|→]]', ['asterisk'] = '*', ['hash'] = '#', ['[[#]]'] = '[[Number sign|#]]', ['colon'] = ':', ['[[:]]'] = '[[Colon (punctuation)|:]]', ['pipe'] = '&#124;', ['[[|]]'] = '[[Pipe symbol|&#124;]]', ['semicolon'] = ';', ['[[;]]'] = '[[Semi-colon|&#59;]]', ['equals'] = '&#61;', -- Left & right analog sticks. ['l up'] = 'L↑', ['l down'] = 'L↓', ['l left'] = 'L←', ['l right'] = 'L→', ['l ne'] = 'L↗', ['l se'] = 'L↘', ['l nw'] = 'L↖', ['l sw'] = 'L↙', ['r up'] = 'R↑', ['r down'] = 'R↓', ['r left'] = 'R←', ['r right'] = 'R→', ['r ne'] = 'R↗', ['r se'] = 'R↘', ['r nw'] = 'R↖', ['r sw'] = 'R↙', -- PlayStation. ['ex'] = '×', ['circle'] = '○', ['square'] = '□', ['triangle'] = '△', -- Nintendo 64 and GameCube. ['c up'] = 'C↑', ['c down'] = 'C↓', ['c left'] = 'C←', ['c right'] = 'C→', ['c ne'] = 'C↗', ['c se'] = 'C↘', ['c nw'] = 'C↖', ['c sw'] = 'C↙', } local keyAlias = { -- ['alternate name for key (alias)'] = 'name for key used in key table' ['[[cmd key|cmd]]'] = '[[command key|cmd]]', ['[[cmd key|command]]'] = '[[command key|command]]', ['[[opt key|opt]]'] = '[[option key|opt]]', ['[[option key]]'] = '[[option key|option]]', ['[[opt key|option]]'] = '[[option key|option]]', ['[[win key|win]]'] = '[[windows key|win]]', ['*'] = 'asterisk', ['#'] = 'hash', [':'] = 'colon', [';'] = 'semicolon', ['l-up'] = 'l up', ['l-down'] = 'l down', ['l-left'] = 'l left', ['l-right'] = 'l right', ['l-ne'] = 'l ne', ['l-se'] = 'l se', ['l-nw'] = 'l nw', ['l-sw'] = 'l sw', ['r-up'] = 'r up', ['r-down'] = 'r down', ['r-left'] = 'r left', ['r-right'] = 'r right', ['r-ne'] = 'r ne', ['r-se'] = 'r se', ['r-nw'] = 'r nw', ['r-sw'] = 'r sw', ['ps x'] = 'ex', ['ps c'] = 'circle', ['ps s'] = 'square', ['ps t'] = 'triangle', ['c-up'] = 'c up', ['c-down'] = 'c down', ['c-left'] = 'c left', ['c-right'] = 'c right', ['c-ne'] = 'c ne', ['c-se'] = 'c se', ['c-nw'] = 'c nw', ['c-sw'] = 'c sw', } local Collection = {} Collection.__index = Collection do function Collection:add(item) if item ~= nil then self.n = self.n + 1 self[self.n] = item end end function Collection:join(sep) return table.concat(self, sep) end function Collection:sort(comp) table.sort(self, comp) end function Collection.new() return setmetatable({n = 0}, Collection) end end local function keyPress(args) local chainNames = { 'chain first', 'chain second', 'chain third', 'chain fourth', 'chain fifth', 'chain sixth', 'chain seventh', 'chain eighth', 'chain ninth', } local result = Collection.new() local chainDefault = args.chain or '+' for i, id in ipairs(args) do if i > 1 then result:add(args[chainNames[i - 1]] or chainDefault) end local lc = id:lower() local text = keyText[lc] or keyText[keyAlias[lc]] local leftRight = lc:match("^left ") or lc:match("^right ") if not text and leftRight then local _lc = lc:gsub("^" .. leftRight, "") local suffix = keyText[_lc] or keyText[keyAlias[_lc]] if suffix then text = leftRight:gsub("^%l", string.upper) .. " " .. suffix end end result:add(kbdPrefix .. (text or id) .. kbdSuffix) end return mw.getCurrentFrame():extensionTag{ name = 'templatestyles', args = { src = 'Module:Key/styles.css'} } .. result:join() end local function keypress(frame) -- Called by "{{key press|...}}". -- Using the template doubles the post‐expand include size. return keyPress(frame:getParent().args) end local function press(frame) -- Called by "{{#invoke:key|press|...}}". return keyPress(frame.args) end return { keypress = keypress, press = press, } 5af1229b7a53f870f70730f7d782cc4f1d5c7bf3 2589 2586 2025-06-24T13:59:40Z Atmois 13 Update comments Scribunto text/plain -- This module implements {{Key Press}}. local kbdPrefix = '<kbd class="keyboard-key nowrap">' local kbdSuffix = '</kbd>' local keyText = { ['caps lock'] = '⇪ Caps Lock', ['[[caps lock]]'] = '⇪ [[Caps Lock]]', ['shift'] = '⇧ Shift', ['[[shift key|shift]]'] = '⇧ [[Shift key|Shift]]', ['enter'] = '↵ Enter', ['[[enter key|enter]]'] = '↵ [[Enter key|Enter]]', ['cmd'] = '⌘ Cmd', ['[[command key|cmd]]'] = '⌘ [[Command key|Cmd]]', ['command'] = '⌘ Command', ['[[command key|command]]'] = '⌘ [[Command key|Command]]', ['opt'] = '⌥ Opt', ['[[option key|opt]]'] = '⌥ [[Option key|Opt]]', ['option'] = '⌥ Option', ['[[option key|option]]'] = '⌥ [[Option key|Option]]', ['tab'] = 'Tab ↹', ['[[tab key|tab]]'] = '[[Tab key|Tab]] ↹', ['backspace'] = '← Backspace', ['[[backspace]]'] = '← [[Backspace]]', ['win'] = '⊞ Win', ['[[windows key|win]]'] = '⊞ [[Windows key|Win]]', ['menu'] = '≣ Menu', ['[[menu key|menu]]'] = '≣ [[Menu key|Menu]]', ['up'] = '↑', ['[[arrow keys|up]]'] = '[[Arrow keys|↑]]', ['down'] = '↓', ['[[arrow keys|down]]'] = '[[Arrow keys|↓]]', ['left'] = '←', ['[[arrow keys|left]]'] = '[[Arrow keys|←]]', ['right'] = '→', ['[[arrow keys|right]]'] = '[[Arrow keys|→]]', ['asterisk'] = '*', ['hash'] = '#', ['[[#]]'] = '[[Number sign|#]]', ['colon'] = ':', ['[[:]]'] = '[[Colon (punctuation)|:]]', ['pipe'] = '&#124;', ['[[|]]'] = '[[Pipe symbol|&#124;]]', ['semicolon'] = ';', ['[[;]]'] = '[[Semi-colon|&#59;]]', ['equals'] = '&#61;', -- Left & right analog sticks. ['l up'] = 'L↑', ['l down'] = 'L↓', ['l left'] = 'L←', ['l right'] = 'L→', ['l ne'] = 'L↗', ['l se'] = 'L↘', ['l nw'] = 'L↖', ['l sw'] = 'L↙', ['r up'] = 'R↑', ['r down'] = 'R↓', ['r left'] = 'R←', ['r right'] = 'R→', ['r ne'] = 'R↗', ['r se'] = 'R↘', ['r nw'] = 'R↖', ['r sw'] = 'R↙', -- PlayStation. ['ex'] = '×', ['circle'] = '○', ['square'] = '□', ['triangle'] = '△', -- Nintendo 64 and GameCube. ['c up'] = 'C↑', ['c down'] = 'C↓', ['c left'] = 'C←', ['c right'] = 'C→', ['c ne'] = 'C↗', ['c se'] = 'C↘', ['c nw'] = 'C↖', ['c sw'] = 'C↙', } local keyAlias = { -- ['alternate name for key (alias)'] = 'name for key used in key table' ['[[cmd key|cmd]]'] = '[[command key|cmd]]', ['[[cmd key|command]]'] = '[[command key|command]]', ['[[opt key|opt]]'] = '[[option key|opt]]', ['[[option key]]'] = '[[option key|option]]', ['[[opt key|option]]'] = '[[option key|option]]', ['[[win key|win]]'] = '[[windows key|win]]', ['*'] = 'asterisk', ['#'] = 'hash', [':'] = 'colon', [';'] = 'semicolon', ['l-up'] = 'l up', ['l-down'] = 'l down', ['l-left'] = 'l left', ['l-right'] = 'l right', ['l-ne'] = 'l ne', ['l-se'] = 'l se', ['l-nw'] = 'l nw', ['l-sw'] = 'l sw', ['r-up'] = 'r up', ['r-down'] = 'r down', ['r-left'] = 'r left', ['r-right'] = 'r right', ['r-ne'] = 'r ne', ['r-se'] = 'r se', ['r-nw'] = 'r nw', ['r-sw'] = 'r sw', ['ps x'] = 'ex', ['ps c'] = 'circle', ['ps s'] = 'square', ['ps t'] = 'triangle', ['c-up'] = 'c up', ['c-down'] = 'c down', ['c-left'] = 'c left', ['c-right'] = 'c right', ['c-ne'] = 'c ne', ['c-se'] = 'c se', ['c-nw'] = 'c nw', ['c-sw'] = 'c sw', } local Collection = {} Collection.__index = Collection do function Collection:add(item) if item ~= nil then self.n = self.n + 1 self[self.n] = item end end function Collection:join(sep) return table.concat(self, sep) end function Collection:sort(comp) table.sort(self, comp) end function Collection.new() return setmetatable({n = 0}, Collection) end end local function keyPress(args) local chainNames = { 'chain first', 'chain second', 'chain third', 'chain fourth', 'chain fifth', 'chain sixth', 'chain seventh', 'chain eighth', 'chain ninth', } local result = Collection.new() local chainDefault = args.chain or '+' for i, id in ipairs(args) do if i > 1 then result:add(args[chainNames[i - 1]] or chainDefault) end local lc = id:lower() local text = keyText[lc] or keyText[keyAlias[lc]] local leftRight = lc:match("^left ") or lc:match("^right ") if not text and leftRight then local _lc = lc:gsub("^" .. leftRight, "") local suffix = keyText[_lc] or keyText[keyAlias[_lc]] if suffix then text = leftRight:gsub("^%l", string.upper) .. " " .. suffix end end result:add(kbdPrefix .. (text or id) .. kbdSuffix) end return mw.getCurrentFrame():extensionTag{ name = 'templatestyles', args = { src = 'Module:Key/styles.css'} } .. result:join() end local function keypress(frame) -- Called by "{{Key Press|...}}". -- Using the template doubles the post‐expand include size. return keyPress(frame:getParent().args) end local function press(frame) -- Called by "{{#invoke:key|press|...}}". return keyPress(frame.args) end return { keypress = keypress, press = press, } c1052ef5e131636dfed3589e3b725859ffae804c 2596 2589 2025-06-24T14:15:03Z Atmois 13 Update css path Scribunto text/plain -- This module implements {{Key Press}}. local kbdPrefix = '<kbd class="keyboard-key nowrap">' local kbdSuffix = '</kbd>' local keyText = { ['caps lock'] = '⇪ Caps Lock', ['[[caps lock]]'] = '⇪ [[Caps Lock]]', ['shift'] = '⇧ Shift', ['[[shift key|shift]]'] = '⇧ [[Shift key|Shift]]', ['enter'] = '↵ Enter', ['[[enter key|enter]]'] = '↵ [[Enter key|Enter]]', ['cmd'] = '⌘ Cmd', ['[[command key|cmd]]'] = '⌘ [[Command key|Cmd]]', ['command'] = '⌘ Command', ['[[command key|command]]'] = '⌘ [[Command key|Command]]', ['opt'] = '⌥ Opt', ['[[option key|opt]]'] = '⌥ [[Option key|Opt]]', ['option'] = '⌥ Option', ['[[option key|option]]'] = '⌥ [[Option key|Option]]', ['tab'] = 'Tab ↹', ['[[tab key|tab]]'] = '[[Tab key|Tab]] ↹', ['backspace'] = '← Backspace', ['[[backspace]]'] = '← [[Backspace]]', ['win'] = '⊞ Win', ['[[windows key|win]]'] = '⊞ [[Windows key|Win]]', ['menu'] = '≣ Menu', ['[[menu key|menu]]'] = '≣ [[Menu key|Menu]]', ['up'] = '↑', ['[[arrow keys|up]]'] = '[[Arrow keys|↑]]', ['down'] = '↓', ['[[arrow keys|down]]'] = '[[Arrow keys|↓]]', ['left'] = '←', ['[[arrow keys|left]]'] = '[[Arrow keys|←]]', ['right'] = '→', ['[[arrow keys|right]]'] = '[[Arrow keys|→]]', ['asterisk'] = '*', ['hash'] = '#', ['[[#]]'] = '[[Number sign|#]]', ['colon'] = ':', ['[[:]]'] = '[[Colon (punctuation)|:]]', ['pipe'] = '&#124;', ['[[|]]'] = '[[Pipe symbol|&#124;]]', ['semicolon'] = ';', ['[[;]]'] = '[[Semi-colon|&#59;]]', ['equals'] = '&#61;', -- Left & right analog sticks. ['l up'] = 'L↑', ['l down'] = 'L↓', ['l left'] = 'L←', ['l right'] = 'L→', ['l ne'] = 'L↗', ['l se'] = 'L↘', ['l nw'] = 'L↖', ['l sw'] = 'L↙', ['r up'] = 'R↑', ['r down'] = 'R↓', ['r left'] = 'R←', ['r right'] = 'R→', ['r ne'] = 'R↗', ['r se'] = 'R↘', ['r nw'] = 'R↖', ['r sw'] = 'R↙', -- PlayStation. ['ex'] = '×', ['circle'] = '○', ['square'] = '□', ['triangle'] = '△', -- Nintendo 64 and GameCube. ['c up'] = 'C↑', ['c down'] = 'C↓', ['c left'] = 'C←', ['c right'] = 'C→', ['c ne'] = 'C↗', ['c se'] = 'C↘', ['c nw'] = 'C↖', ['c sw'] = 'C↙', } local keyAlias = { -- ['alternate name for key (alias)'] = 'name for key used in key table' ['[[cmd key|cmd]]'] = '[[command key|cmd]]', ['[[cmd key|command]]'] = '[[command key|command]]', ['[[opt key|opt]]'] = '[[option key|opt]]', ['[[option key]]'] = '[[option key|option]]', ['[[opt key|option]]'] = '[[option key|option]]', ['[[win key|win]]'] = '[[windows key|win]]', ['*'] = 'asterisk', ['#'] = 'hash', [':'] = 'colon', [';'] = 'semicolon', ['l-up'] = 'l up', ['l-down'] = 'l down', ['l-left'] = 'l left', ['l-right'] = 'l right', ['l-ne'] = 'l ne', ['l-se'] = 'l se', ['l-nw'] = 'l nw', ['l-sw'] = 'l sw', ['r-up'] = 'r up', ['r-down'] = 'r down', ['r-left'] = 'r left', ['r-right'] = 'r right', ['r-ne'] = 'r ne', ['r-se'] = 'r se', ['r-nw'] = 'r nw', ['r-sw'] = 'r sw', ['ps x'] = 'ex', ['ps c'] = 'circle', ['ps s'] = 'square', ['ps t'] = 'triangle', ['c-up'] = 'c up', ['c-down'] = 'c down', ['c-left'] = 'c left', ['c-right'] = 'c right', ['c-ne'] = 'c ne', ['c-se'] = 'c se', ['c-nw'] = 'c nw', ['c-sw'] = 'c sw', } local Collection = {} Collection.__index = Collection do function Collection:add(item) if item ~= nil then self.n = self.n + 1 self[self.n] = item end end function Collection:join(sep) return table.concat(self, sep) end function Collection:sort(comp) table.sort(self, comp) end function Collection.new() return setmetatable({n = 0}, Collection) end end local function keyPress(args) local chainNames = { 'chain first', 'chain second', 'chain third', 'chain fourth', 'chain fifth', 'chain sixth', 'chain seventh', 'chain eighth', 'chain ninth', } local result = Collection.new() local chainDefault = args.chain or '+' for i, id in ipairs(args) do if i > 1 then result:add(args[chainNames[i - 1]] or chainDefault) end local lc = id:lower() local text = keyText[lc] or keyText[keyAlias[lc]] local leftRight = lc:match("^left ") or lc:match("^right ") if not text and leftRight then local _lc = lc:gsub("^" .. leftRight, "") local suffix = keyText[_lc] or keyText[keyAlias[_lc]] if suffix then text = leftRight:gsub("^%l", string.upper) .. " " .. suffix end end result:add(kbdPrefix .. (text or id) .. kbdSuffix) end return mw.getCurrentFrame():extensionTag{ name = 'templatestyles', args = { src = 'Module:Key_Press/styles.css'} } .. result:join() end local function keypress(frame) -- Called by "{{Key Press|...}}". -- Using the template doubles the post‐expand include size. return keyPress(frame:getParent().args) end local function press(frame) -- Called by "{{#invoke:key|press|...}}". return keyPress(frame.args) end return { keypress = keypress, press = press, } 78110a8c91eb161364a3a51319abd3d68ded428e 828 690 2587 2025-06-24T13:53:17Z Atmois 13 Add source link wikitext text/x-wiki Adapted from https://en.wikipedia.org/wiki/Module:Key_press 8f9d9c05ae78415850975a1b37235280e46c3798 4 327 2588 2376 2025-06-24T13:56:10Z Atmois 13 Replaced content with "{{Key_Press}}" wikitext text/x-wiki {{Key_Press}} a46edf125178a7171c79642207c5d7e9a83d8cf1 10 691 2590 2025-06-24T14:00:37Z Atmois 13 Redirected page to [[Template:Key Press]] wikitext text/x-wiki #REDIRECT [[Template:Key_Press]] 2b0da6577828dec1de8f8e18229c5dbf155299c2 10 692 2592 2025-06-24T14:07:59Z Atmois 13 Redirected page to [[Template:Key Press]] wikitext text/x-wiki #REDIRECT [[Template:Key_Press]] 2b0da6577828dec1de8f8e18229c5dbf155299c2 10 693 2593 2025-06-24T14:08:35Z Atmois 13 Redirected page to [[Template:Key press]] wikitext text/x-wiki #REDIRECT [[Template:Key_press]] f4733c559a0e86f6016a46769233d3a22c3a7298 828 694 2594 2025-06-24T14:13:00Z Atmois 13 Improt styles from starcitizen wiki sanitized-css text/css .keyboard-key { padding: 0.25em 0.5em; display: inline-block; line-height: 1; font-weight: var( --font-weight-medium ); font-size: 0.875rem; border-radius: var( --border-radius-base ); border: 1px solid; border-color: var( --border-color-base ); background: var( --color-surface-3 ); color: var( --color-emphasized ); } 9151ad2e1dd1edd1f1d8c3e31c02341621601b79 2595 2594 2025-06-24T14:13:45Z Atmois 13 Add source comment sanitized-css text/css .keyboard-key { padding: 0.25em 0.5em; display: inline-block; line-height: 1; font-weight: var( --font-weight-medium ); font-size: 0.875rem; border-radius: var( --border-radius-base ); border: 1px solid; border-color: var( --border-color-base ); background: var( --color-surface-3 ); color: var( --color-emphasized ); } /* Imported from https://starcitizen.tools/Module:Key/styles.css */ 499bef99227c798b7932067eb4be2669fce39e0d 8 196 2597 2218 2025-06-24T17:34:55Z Atmois 13 Implement privacy respecting analytics javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ $(document).ready(function(){ $('.mw-references-wrap').before('<h2>References</h2>'); }); var s = document.createElement('script'); s.defer = true; s.src = 'https://umami.atl.wiki/script.js'; s.setAttribute('data-website-id', '21f384be-587d-4b00-8727-203d00c898d5'); document.head.appendChild(s); 30ece590ade72daf2b0cc976b4fda9315d51dc05 4 556 2598 2249 2025-06-24T21:45:00Z Atmois 13 Fix some grammer wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[Atl.wiki:Contact|contact page]]! == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin == History == ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. ===== June 2024 ===== W e obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the [https://discord.gg/linux All Things Linux discord]. [[User:Electron271|Electron271]], Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, [[User:Kaizen|Kaizen]]. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spambots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also reimplemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[Special:Favoritelist|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to relicence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another relicencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[Atl.wiki:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== The Future ===== Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] 26238f5e9a63e943fc8ef451d10c1b0817345342 0 227 2602 2152 2025-06-26T08:11:16Z Hog 161 Removed instructions wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== [[Category:X_Window_Managers]] 6dda7deb3b840252e52f10e175eb1f14a78b8e92 3000 695 2603 2025-06-26T08:11:26Z Hog 161 Ported instructions over wikitext text/x-wiki === Installation === ==== On [[Debian]] and Debian-based distributions: ==== You can sometimes install using a software manager.<syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> fb9b2ad8874bf01d48fe1f6f9f085db002223f81 3000 696 2604 2025-06-26T08:24:23Z Hog 161 Created Guide for problem i had to inform others wikitext text/x-wiki === Using Cinnamon === * Open Start Menu in bottom right corner * Log Out * Click on [[Cinnamon]] Logo next to log In details * Switch to desired [[Window Manager]] === Using i3 === <syntaxhighlight> Mod+shift+e </syntaxhighlight> * Confirm that you want to log out in pop-up * Click on [[i3]] logo next to Log In details * Switch to desired Window Manager === Using XFCE === * Open Start Menu in Top Left corner * Log Out * Click on [[XFCE]] Logo next to log In details * Switch to desired Window Manager === Using MATE === * Open Start Menu in bottom right corner * Log Out * Click on [[MATE]] Logo next to log In details * Switch to desired Window Manager d20cc5ffbe0f4ea031bee4d52757ed801f29e44c 0 248 2605 2089 2025-06-26T08:35:07Z Hog 161 added information and fixed citations wikitext text/x-wiki {{Needs_Citations}} == Introduction == {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu Logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[GNOME]], [[Unity]] | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu, is a Highly Popular [[Linux Distributions|Linux distribution]] derived from [[Debian]] and is developed by Canonical for the commercial market and the first version was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS versions receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubuntu receives 9 months of support.<ref>https://ubuntu.com/about/release-cycle Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> Ubuntu can be run locally, on a cloud, or in a [[Virtual Machine|VM]]. Ubuntu comes packaged with basic GNOME utilities as default and additionally from Ubuntu Software (formally Ubuntu Software Centre) and from APT, Ubuntu's default package manager. <references /> [[Category:Linux Distributions]] 2c676994a4aef4e84b59a7e1f0ffb1a88b6c8c0a 3000 697 2606 2025-06-26T08:39:20Z Hog 161 Ported instructions over wikitext text/x-wiki === Installation === Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions:<syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]:<syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight>On [[Void Linux]]:<syntaxhighlight lang="bash"> sudo xbps-install windowmaker </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running:<syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> e2c1df80e8232d14a55848a47e98d67292b4cd15 0 281 2607 2154 2025-06-26T08:40:28Z Hog 161 Cleaned up wikitext text/x-wiki {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home] official Window Maker Website, 2025 (Imported 16th June 2024)</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home] Dockapps Website, 2025 (Imported 16th June 2024)</ref> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more.<references /> [[Category:X_Window_Managers]] 82ad1f89f077127a0ca439422d72c2f5376cafad 0 667 2608 2506 2025-06-26T08:44:00Z Hog 161 added a bit more information wikitext text/x-wiki {{Cleanup|Incomplete page}}'''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system.{{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}} d1850a7e46002d99e0ed6974d413659cd4ad4b4c 0 171 2609 2063 2025-06-26T08:49:51Z Hog 161 cleaned up citations wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|thumb|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = Customizable based on user configuration | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. <references /> [[Category:Linux Distributions]] 0e986ea6ed7cf88e8500530a16f23ed884b6dfde 0 414 2610 2170 2025-06-26T09:06:09Z Hog 161 Made it a bit easier to read wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970's, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at Bell Labs, and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and pre-processors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include GNU GCC, Clang, TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the Clang compiler toolchain, however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as GNU Autotools, CMake, Meson, Zig's build toolchain among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, meta-programming and structural components of a C code base; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS|open source]] code bases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995-2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref>, many attribute issues regarding C to fragmentation and portability issues<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref>, lack of type safety and primitive resource access checks<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref>, poor administration on part of the C Language Working Group<ref>https://cor3ntin.github.io/posts/c/</ref>, and overall worsening over time<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref>. 9073b7286984ac72c92ce69fba6c0ea83f0f7bdb 0 257 2611 2574 2025-06-26T13:11:30Z Hog 161 Removed warning wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=[[C++]]|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window managers that aim for pure eye candy with nice animations, smooth looks and its own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has it's own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc) [[Category:Wayland_Compositors]] e0525df42ec2a05006ea35e069578334f67cedbd 0 219 2612 2053 2025-06-26T13:14:04Z Hog 161 fixed citations wikitext text/x-wiki {{MascotInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan<ref>https://community.kde.org/Promo/Material/Mascots Official KDE Wiki, 2025 (Imported 6th June 2024)</ref>. Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror], KDE's default web browser<ref>https://community.kde.org/Konqi Official KDE Wiki, 2025 (Imported 6th June 2024)</ref>.<references /> [[Category:Mascots]] 4ff08eded5a177397d1a54470e488ddcb1db85a0 0 345 2613 2532 2025-06-26T13:19:05Z Hog 161 fixed citations wikitext text/x-wiki {{Needs Citations}} Kernel Modules are pieces of code that can be loaded directly into the [[Kernel]] at runtime to extend functionality.<ref>https://linux-kernel-labs.github.io/refs/heads/master/labs/kernel_modules.html Kernel Labs Github, 2025 (imported 26th June 2025)</ref> The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your [[Linux Distributions|Distribution]], as such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically older ones benefit the most) at the cost of new devices potentially not working when added. It is also possible to compile a Linux kernel on a pre-existing system to only use needed Kernel modules. == Obtaining information == Modules depend on the kernel release and the kernels version, though usually they are stored in <code>/usr/lib/modules/''kernel_release_version''</code>''.'' To see which modules are loaded, <code>lsmod</code> can be used. Obtaining information is achievable with <code>modinfo <module_name></code> == Module loading == === Automatic loading === Usually most needed modules are handled [[udev]], so usually out of tree modules aren't needed, though there are cases where loading or blacklisting a module is needed for your setup to function properly. Early module loading is generally handled by your [[initramfs]] generator of choice, usually dracut, booster or mkinitcpio. Alternatively, [[systemd]] will load modules explicitly listed in <code>/etc/modules-load.d/</code> ,with the naming scheme of <code>/etc/modules-load.d/program.conf</code>. Lines starting with ; or # are parsed as comments and ignored === Manual loading === Kernel modules can be manually loaded with <code>modprobe <module_name></code>, or loading a module that by file name (i.e. modules that are not installed in <code>/usr/lib/modules/<kernel_release_version></code>) can be achieved either of the following ways:<syntaxhighlight lang="sh"> insmod file_name module_options modprobe file_name </syntaxhighlight>Removing a module can be achieved by:<syntaxhighlight lang="sh"> rmmod module_name modprobe -r module_name modprobe --remove module_name </syntaxhighlight> [[Category:Terminology]] 059132e5e4a80eeb52dcebabf7d3e85bb8d4e7c6 0 304 2614 2077 2025-06-26T13:20:23Z Hog 161 wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a [[UNIX|UNIX-like]] [[Operating System|operating system]] completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS]</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive [[kernel]], and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[MacOS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[Virtual Machine|virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to [[Compiling|compile]] software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub]</ref> [[Category:Misc Operating Systems]] 03236b1ea8dfc9cf1ee175120ad46fe0157da019 0 698 2615 2025-06-26T13:21:23Z Hog 161 Made redirect wikitext text/x-wiki #REDIRECT [[UNIX]] 0cf09966066b69f970594b9e99bc47ae3895f61c 0 268 2616 2033 2025-06-26T13:23:20Z Hog 161 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch github.com/fastfetch-cli/fastfetch] }} Fastfetch is a [[neofetch]]-like tool for fetching information about your [[Operating System|operating system]], [[software]] and hardware. It is written mainly in [[C]], with a focus on performance.<ref>https://github.com/fastfetch-cli/fastfetch Fastfetch Github, 2025 (Imported 26th, June 2025)</ref> <references /> [[Category:Software]] 586bbe2fc6a8db27d56425a2d98872d8daed66e2 0 240 2617 2060 2025-06-26T13:30:23Z Hog 161 added incomplete tag wikitext text/x-wiki {{Cleanup|Incomplete page}}{{Needs Citations}} == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your disribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most deriative distributions. ==== General Information ==== ===== Multi Booting ===== [[File:GRUB with ubuntu and windows vista.png|thumb|GRUB, with entries for [[Ubuntu]] and Windows Vista, an example of ''dual booting.'']] [[Multi Booting]] (Or often refered to as 'Dual Booting') is the process of installing multiple [[Operating System|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completly removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to parititon the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly reccomended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi Booting]] page. ===== Finding Alternatives or Workarounds for Apps ===== Often there is at least one [[application]] missing on Linux or an app that is missing some features or is buggy so you'll find yourself looking for alternative options. There also sometimes is the issue that your distribution doesn't have an app but another distribution does have it. A good place to start when looking for alternatives is [https://alternativeto.net AlternativeTo] which is a crowdsourced site useful to find alternatives for almost any app. Other useful sites include [https://www.privacytools.io Privacy Tools] and [https://awesome-privacy.xyz Awesome Privacy] with a privacy focused list of apps. When looking for workarounds for apps not supported for your distribution you should first check [https://flathub.org Flathub] and [https://snapcraft.io Snapcraft] (Note that [[Snap|Snaps]] are known to have performance issues) if your app is available there as they offer support for most distributions. If a steam game lacks native Linux support try checking [https://www.protondb.com ProtonDB] if Valve's proton tool supports your game. [https://www.winehq.org Wine] is also an option to run Windows apps on Linux. ==== Moving between specfic Operating Systems ==== ===== Moving to Linux from MacOS ===== ===== Moving to Linux from Windows ===== === General Information === [[Category:Guides]] e1849afc22904a29ea67262e963a7fe9d304da73 2 655 2618 2571 2025-06-26T13:33:36Z Hog 161 edited my page wikitext text/x-wiki [[File:Sus scrofa f domesticus - Réserve africaine de Sigean 01.jpg|thumb|Photo of a hog i like]] I probably fixed your article bozo. Im gonna put these tags here so i can copy and paste{{Work In Progress}}{{Needs Citations}}{{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{Cleanup|Incomplete page}} f616723f7e2f19222b7bf1847c8f07ade9a22e34 2 3 2619 2405 2025-06-27T02:28:19Z Amadaluzia 52 Maukkis gave me her version of the C++ so I added it and refactored it. wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <tuple> #include <vector> #include <print> // Compile with C++23 or above. This will not work otherwise. struct AboutMe { std::string name, description; std::vector<std::tuple<std::string, std::string>> socials; }; int main(void) { struct AboutMe amadaluzia { .name = "Artur Manuel", .description { "I live in the UK and the internet as a background character in many\n" "free software communities (for example: you may find me on some\n" "mailing list) but I also contribute, most notably in nixpkgs.\n" "I do have other interests, such as gym, walking and photography, as\n" "well as speedrunning, filming and revising for english/maths among\n" "other things.\n" }, .socials { {"Signal", "@amadaluzia.711"}, {"Email", "amad@atl.tools"}, {"XMPP", "amadaluzia@xmpp.earth"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Libera.Chat", "amadaluzia"}, {"Discord", "amadaluzia"}, }, }; std::println("Hello, I am {}.", amadaluzia.name); std::println("{}", amadaluzia.description); std::println("You may find me on the following platforms:"); for (auto const &[k, v] : amadaluzia.socials) std::println("{} on {}", v, k); return 0; }</syntaxhighlight> f84715370cea0b05b4ea76b84248402e72c551ad 0 405 2620 2071 2025-06-27T08:20:16Z Hog 161 added information and citations wikitext text/x-wiki {{Cleanup|Short page}} Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Linux and Other Unix-Like Operating systems will avoid or not support Proprietary software when possible. This is mainly due to incompatible licensing.<ref>https://solutionshub.epam.com/blog/post/proprietary-software-definition-examples Epam, 2025 (imported 27th June 2025)</ref> Some examples of proprietary software are Microsoft Windows and Adobe Photoshop. [[Category:Terminology]] de85c68ec5ed15ffaac8fe9eaae1ea3747e9f20b 0 663 2621 2553 2025-06-27T08:21:49Z Hog 161 Added warning wikitext text/x-wiki {{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}}{{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terra.fyralabs.com terra.fyralabs.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora]] Linux and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terra.fyralabs.com/ Terra], Terra, 2024 (Accessed: 2025-06-19)</ref> Developed by Fyra Labs, it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://developer.fyralabs.com/terra/infrastructure How Terra Works], Fyra Labs, 2025 (Accessed: 2025-06-19)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://developer.fyralabs.com/terra/installing. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji], RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://developer.fyralabs.com/terra/autoupdate Automatic Updates - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases :: Fedora Docs], Fedora, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably [[Rust]], [[Go]], [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://developer.fyralabs.com/terra/policy Policy – Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> == See Also == * [https://terra.fyralabs.com Main Website] * [https://developer.fyralabs.com/terra Fyra Developer Documentations for Terra] * [https://github.com/terrapkg/packages Terra Sources] d87913fa2c4b00ea0a2922d42aff4dee4cae694f 0 236 2622 2086 2025-06-27T08:22:33Z Hog 161 Added warning wikitext text/x-wiki {{Needs_Citations}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.20, 2024-12-15 | languages = C | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * Desktop Manager - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[Terminal Emulator|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> [[Category:Desktop Environments]] cfc15ae2b180e737a4be8abc059dde23d56b2aec 0 198 2623 2499 2025-06-27T08:47:48Z Hog 161 Added AIX wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is a Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AIX]] |A series of Unix-Based Operating systems for Power servers. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] cd9c7827534938e61756e0837428669d31eb611d 3001 699 2624 2025-06-27T08:50:55Z Hog 161 /* Should this be reformatted? */ new section wikitext text/x-wiki == Should this be reformatted? == Maybe group by installing an operating system, installing software? [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 08:50, 27 June 2025 (UTC) a76f3c2f4851a7a2de858acbadc87edf842cb40f 0 177 2625 2167 2025-06-27T08:53:53Z Hog 161 fixed citations wikitext text/x-wiki '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the french word, libre)<ref>https://en.wiktionary.org/wiki/libre Wikitionary. Wikimedia Foundation. Accessed June 4, 2024.</ref> and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> [[Category:Terminology]] ac8ecfb4d493b6fb32f2b569c9af3a3d2d38a52a 0 418 2626 2421 2025-06-27T10:26:31Z Hog 161 fixed citations wikitext text/x-wiki {{DistributionInfobox|architectures=arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox|caption=The FreeBSD logo|defaultdesktops=[[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]]|image=[[File:FreeBSD logo.png|200px|FreeBSD_logo]]|packagemanager=[[pkg]]|releasemodel=Stable|releasestatus=Maintained|title=FreeBSD|usagetype=Desktop, Firewall, Raspberry Pi, Server|website=[https://freebsd.org freebsd.org]}} FreeBSD is a [[UNIX|Unix]] [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released on November 1993<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"]. [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref>. [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[Drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a [[kernel]] and [[drivers]], and relying on third-parties such as [[GNU]] for system [[:Category:Software|software]]<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref>. The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref>. The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']}<references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 25cf6835479eff89f89ae922a8c2f160963743eb 0 700 2627 2025-06-27T10:39:58Z Hog 161 made a very small page for calamares wikitext text/x-wiki Calamares is a distribution-independent system installer, with an advanced partitioning feature for both manual and automated partitioning operations. Calamares is designed to be customizable by distribution maintainers without the need for cumbersome patching, thanks to third-party branding and external modules support.<ref>https://github.com/calamares/calamares Calamares Github, 2025 (27th June 2025)</ref>{{SoftwareInfobox|image=[[File:Calamares on Debian 10 screenshot.jpg|frameless]]|caption=Calamares Installer|title=Calamares|releasestatus=Maintained|lastrelease=3.3.14 (Feb 20, 2025)|languages=[[C++]], [[Python]]|developers=Adriaan de Groot|website=https://calamares.io/}} 82c940fa5a3419949073ada57e1f39b59ce7f7dc 2628 2627 2025-06-27T10:41:20Z Hog 161 corrected categorises wikitext text/x-wiki Calamares is a distribution-independent system installer, with an advanced partitioning feature for both manual and automated partitioning operations. Calamares is designed to be customizable by distribution maintainers without the need for cumbersome patching, thanks to third-party branding and external modules support.<ref>https://github.com/calamares/calamares Calamares Github, 2025 (27th June 2025)</ref>{{SoftwareInfobox|image=[[File:Calamares on Debian 10 screenshot.jpg|frameless]]|caption=Calamares Installer|title=Calamares|releasestatus=Maintained|lastrelease=3.3.14 (Feb 20, 2025)|languages=[[C++]], [[Python]]|developers=Adriaan de Groot|website=https://calamares.io/}} <references /> [[Category:Software]] 1da34cbd5cf40809edbf7164d2aaa053e20e07b0 14 397 2629 1385 2025-06-27T10:43:09Z Hog 161 added brief description wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer 6696ae40dcb1c26b6f8ad59d5d87ac73d59b5acf 0 659 2630 2511 2025-06-27T10:51:28Z Hog 161 fixed citations wikitext text/x-wiki {{DistributionInfobox|title=ChromeOS|image=[[File:Chromium_Logo.svg|frameless]]|caption=ChromiumOs Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[APT]]|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website=[https://chromeos.google/ chromeos]}}ChromeOS (ChromiumOS) is a [[UNIX|Unix-Based]] [[Linux Distributions|Linux distribution]] designed and developed by Google in 2009. ChromeOS is completely open-source<ref>http://source.chromium.org/chromiumos Official ChromeOS website, 2025 (imported 27th June 2025)</ref>. <references /> b1a53715580eabb1d89f5f4427d5323732c806c8 0 679 2631 2601 2025-06-28T09:50:40Z Madonuko 140 some more docs wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = <code>git</code> | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git’s early design emphasized a distributed workflow similar to BitKeeper’s but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like GitHub, which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. 5c0b7bbc780132f43f565e3679c4df22cd12209a 0 668 2632 2600 2025-06-28T14:24:33Z Madonuko 140 fix cite 2 access date wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor ed (1971) and the even earlier qed (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; …} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to [[EOF]]. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10-15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 4d2149a77e47ee138594ab638f55c886c9f30a95 1 686 2633 2583 2025-06-28T14:25:12Z Madonuko 140 /* Citation 2. */ Reply wikitext text/x-wiki == Citation 2. == Is the date accurate for the accessed? [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 13:47, 24 June 2025 (UTC) :No it wasn't. Fixed. Thanks! — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 14:25, 28 June 2025 (UTC) 1e35b864ae3170b0be49cc904b3b566d48c4c35c 2 644 2634 2514 2025-06-29T13:56:57Z Madonuko 140 wikitext text/x-wiki V.P. DevOps at [https://fyralabs.com Fyra Labs] and [[Ultramarine Linux]]. Lead maintainer of [[Terra]]. == Pages I maintain == * [[Guides:Input method]] * [[Sed]] * [[Terra]] * [[Grep]] * [[Git]] * [[Regular Expression]] ac1506442013ea87564ac3f48c15bb4e7a57e326 3000 701 2635 2025-06-29T18:35:05Z Tatiana 166 Created article for using ollama. wikitext text/x-wiki Ollama is a runtime for running AI models locally or on a personal server. == Installation == === Official Install Script === curl -fsSL <nowiki>https://ollama.com/install.sh</nowiki> | sh === Arch Linux === ==== No GPU ==== sudo pacman -S ollama ==== ROCm (AMD) ==== sudo pacman -S ollama-rocm ==== CUDA (Nvidia) ==== sudo pacman -S ollama-cuda == Using Models == When picking models, ensure there is enough memory to fit the model you are using. Models small enough to fit in the GPUs memory will only use the GPU while models too big to fit in the GPU will use a mix of GPU and CPU. To check GPU and CPU memory usage run: ollama ps === From Terminal === Gemma 3 will download if not already on the system and then run. ollama run gemma3 Gemma 3 by default uses the 4B version of the model but different versions can be specified. ollama run gemma3:12b Ollama uses q4_K_M quantisation by default but different quantisation level can be specified. ollama run gemma3:12b-it-q8_0 === From a Graphical User Interface === ==== Alpaca ==== Alpaca is officially distributed as a Flatpak. flatpak install flathub com.jeffser.Alpaca Alpaca can be configured to use Ollama externally including remote hosts but can also install Ollama internally as a Flatpak. flatpak install flathub com.jeffser.Alpaca.Plugins.Ollama The Flatpak Ollama plugin can support AMD GPUs using another plugin. flatpal install flathub com.jeffser.Alpaca.Plugins.AMD ==== Visual Studio Code ==== Ollama can be integrated into Visual Studio Code using [https://marketplace.visualstudio.com/items?itemName=Continue.continue Continue]. == Officially Supported GPUs == Consult this [https://github.com/ollama/ollama/blob/main/docs/gpu.md table] for official GPU support. == Use Unsupported AMD GPUs on ROCm == To use ROCm on GPUs not officially supported by Ollama we can extend the Systemd service file with the following command: sudo systemctl edit ollama.service This will open up a file in the systems text editor where you can extend the service. Below are examples of what to add to the file: === Example: Radeon RX 6000 series === <syntaxhighlight> [Service] Environment="HSA_OVERRIDE_GFX_VERSION=10.3.0" </syntaxhighlight> === Example: Radeon RX 5000 series === <syntaxhighlight> [Service] Environment="HSA_OVERRIDE_GFX_VERSION=10.1.0" </syntaxhighlight>The Ollama service will need to be restarted before the GPU can be used. sudo systemctl restart ollama.service 638a525db686d8800be6f87a4a885939a9284d68 0 2 2637 2015 2025-06-29T19:38:50Z Asiliria 7 citations fixed wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === {| class="wikitable" |+ !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. <references /> [[Category:Linux Distributions]] 4850915d73d317297066d8f9da3fe2debe137d68 2 702 2638 2025-06-29T19:42:28Z Asiliria 7 wow that's me wikitext text/x-wiki hey guys ae594fe690ed26c80808f0eb817cad9bcd53e729 6 703 2639 2025-06-29T19:59:30Z Asiliria 7 wikitext text/x-wiki A cat generated using FLUX.1 [schnell]. 657797e376dc6e97c1b4544e9252cd4fb571d2d5 6 704 2640 2025-06-29T20:37:43Z Asiliria 7 wikitext text/x-wiki Ollama says hi to ATL. c3c4290da2059da24a0790f1911c8f9e4f6fbc4a 0 250 2641 2470 2025-06-29T20:38:26Z Asiliria 7 extended stable diffusion page, added Ollama header wikitext text/x-wiki {{Cleanup|Instructions need to be split onto their own page under the Guides namespace}}{{Cleanup|Incomplete page}}[[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. == Ana/Miniconda Setup == While not required, it is heavily recommended to use ''conda'' to manage Python libraries required by various machine learning and artificial intelligence projects from places like Github and Hugging Face. Conda exists as a distinct virtual environment separate from the native distribution's Python packages. Users may specify version number and install additional plugins as well as packages within an environment utilizing conda. It is recommended to read the Linux setup for Miniconda on their [https://www.anaconda.com/docs/getting-started/miniconda/install#linux official website]. The install for Miniconda is very unorthodox compared to installing other packages on a Linux system - be mindful. == Stable Diffusion Setup - WebUI (Forge) == [[File:Cat.png|thumb|A cat generated using FLUX.1 [schnell].]] According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> Stable Diffusion WebUI Forge is a version of Stable Diffusion WebUI that offers additional support for FLUX.1 [dev] and FLUX.1 [schnell] models. For some users, using the Forge version may result in greater stability using FLUX as opposed to the vanilla version. Simply clone the Forge repository:<syntaxhighlight lang="bash"> git clone https://github.com/lllyasviel/stable-diffusion-webui-forge/issues </syntaxhighlight>...install required pip packages:<syntaxhighlight lang="bash"> pip3 install -r requirements.txt </syntaxhighlight>...and run the program:<syntaxhighlight lang="bash"> python3 launch.py </syntaxhighlight> ==== Extra notes ==== ===== Run options/flags ===== It is advisory to set additional launch parameters for better performance, e.g. using '''xformers''' for optimization or to specify a certain directory where models are stored. You can place these in a separate xxx.sh file to run instead of having to copy-and-paste large strings - here is an example:<syntaxhighlight lang="bash"> python3 launch.py --listen --xformers --enable-insecure-extension-access --cuda-malloc --port 7860 --vae-dir=/run/media/jennaannilyn/Pikmin3/models/vae --ckpt-dir=/run/media/jennaannilyn/Pikmin3/AI/ --lora-dir=/run/media/jennaannilyn/Pikmin3/AI/models/loras --no-half-vae </syntaxhighlight> === Installing and using Ollama on Linux === [[File:Ollama.png|thumb|Ollama says hi to ATL.]] According to Ollama's main page, Ollama is used to run open-source/open-weight, locally hosted Large Language Models. == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU, c'''onsidering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> ==== The Deiteris Fork ==== Some users may prefer Deiteris's version, which may offer extra precision and performance for more advanced users. The process is almost identical, except that you must clone his fork:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>...while consequently running a different Python command:<syntaxhighlight lang="bash"> python3 ./main.py </syntaxhighlight> [[Category:Guides]] 8cc6128d56418e784cfd70b00a51ae3f831a7e8f 4 593 2642 2301 2025-06-30T17:23:21Z Atmois 13 Remove link to the choosing a distro page wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[Atl.wiki:About|about]] page! Some important pages are also listed below: * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[Atl.wiki:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[Atl.wiki:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[Guidelines#Standards|standards]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[Atl.wiki:Contact|Contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === * The [[Window Management System]] definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. * The [[Linux Distributions|Linux Distribution]] article which lists distros is lacking a lot of major distros and each section should have a short blurb and information about key facts about what distros under that group typically are (e.g. release cycle, package manager, etc) * The [[Package Manager]] page, which lists package managers, needs to be rewritten to compare and delve more into each package manager. * The [[Key Terms]] page needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table potentially * The [[Desktop Environments]] page needs to be written, it needs to contain basics around DE's and what they are and a list of DE's with a short blurb to each one and potentially key distros that offer them, a table could be used to list them. * The [[X Window Manager]] page, which lists WM's depending on the type, needs to be cleaned up to remove Wayland Compositors and each WM should have a short blurb to it and potentially key distros that offer them, a table could be used to list them. * [[External Resources]] requires a clean-up to be organised and categorised properly, could make use of wiki tables with a short blurb for all websites listed. * [[Common Issues and Troubleshooting]] needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 03cae8648d9584f14920fa497d4f744adc0e3970 3000 705 2643 2025-07-01T08:12:00Z Hog 161 Ported instructions over wikitext text/x-wiki strace is a command-line tool that lets you see the system calls a program makes while it runs. It’s great for debugging, understanding program behavior, or learning how system calls work. === How to use strace === Steps to Use strace: 1. '''Run a Command with strace''':<syntaxhighlight lang="bash">strace <command></syntaxhighlight>This will show all the system calls made by the command. 2. '''Attach to a Running Process''': If a program is already running, use its process ID (PID):<syntaxhighlight lang="bash">strace -p <PID></syntaxhighlight>3. '''Filter Specific System Calls''': To narrow down the output, trace specific system calls using the -e option:<syntaxhighlight lang="bash">strace -e <syscall> <command></syntaxhighlight>4. '''Save Output to a File''': Use -o to redirect the output to a file for easier analysis:<syntaxhighlight lang="bash">strace -o trace_output.txt <command></syntaxhighlight>5. '''Trace Execution Times''': To see how long each system call takes, use:<syntaxhighlight lang="bash">strace -T <command></syntaxhighlight> 728317be621722d234abd9399a75f4b954762d50 0 517 2644 2415 2025-07-01T08:12:18Z Hog 161 cleaned up wikitext text/x-wiki {{Needs_Citations}} = What is a System Call? = A system call (syscall) is a mechanism that allows a program to interact with the [[Operating System|operating system]]. It acts as a bridge between the user space (where applications run) and the kernel space (where the operating system manages hardware and system resources). Programs use system calls to request services from the OS, such as managing files, processes, or hardware devices. For example, when you open a file, your application cannot directly access the hardware. Instead, it makes a system call (e.g., open()), which the OS handles to perform the requested task. Note that this is not a guide for ALL syscalls, but it is a guide to get you familiar enough with syscalls and strace. == Why Should You Learn About System Calls? == 1. Understanding How Programs Work: - System calls reveal how applications interact with the operating system to perform tasks like file handling, memory management, and networking. 2. Efficient Troubleshooting: - Knowing system calls can help diagnose performance issues or bugs by identifying which calls a program relies on. 3. Optimizing Software: - When developing programs, understanding system calls allows you to write efficient code by leveraging the right OS-level functions. 4. Security Awareness: - Many exploits and vulnerabilities target how system calls are used (or misused). Understanding them helps in writing secure code. 5. Kernel-Level Development: - If you're interested in low-level programming, such as operating system development or driver creation, system calls are fundamental. Basically, system calls are the foundation of how software and operating systems interact, making them essential knowledge for both beginner and advanced developers. == Categories of System Calls == System calls are grouped into five main categories: '''Process Control''' – Manage processes (create, terminate, etc.). '''File Management''' – Handle file operations (open, read, write, close). '''Device Management''' – Interact with hardware devices. '''Information Maintenance''' – Exchange information between the OS and programs. '''Communication''' – Enable processes to communicate. 1. '''Process Control''' * fork(): Creates a new process (child) that runs the same program as the parent. * exit(): Terminates the process and frees resources. * exec(): Replaces the current program in a process with a new one. 2. '''File Management''' * open(): Opens a file for reading or writing. * read(): Reads data from a file (multiple processes can read simultaneously). * write(): Writes data to a file (only one process can write at a time). * close(): Closes an open file. 3. '''Device Management''' * ioctl(): Performs device-specific operations not covered by standard calls (e.g., configuring hardware). 4. '''Information Maintenance''' * getpid(): Returns the process ID of the current process. * alarm(): Sets a timer to deliver a signal after a specified time. * sleep(): Pauses the process for a given time. 5. '''Communication''' * pipe(): Enables communication between processes via file descriptors. * shmget(): Allocates shared memory for process communication. * mmap(): Maps files or devices into a process’s memory. === Why Use strace? === * Debug program behavior (e.g., "Why is this program failing?"). * Identify which files, devices, or network resources a program accesses. * Learn what system calls a program makes for educational purposes. cd254cb7dc50efba7385d081871d70b2de7fcfe8 3000 706 2645 2025-07-01T08:29:01Z Hog 161 Ported instructions over wikitext text/x-wiki ==== Arch-based systems ==== To install the '''budgie''' package group, which includes first-party applications such as a screensaver, execute <code>sudo pacman -S budgie</code>. Alternatively, <code>sudo pacman -S budgie-desktop</code> will install the standalone desktop. Recommended optional packages include the Arc GTK theme, the Papirus icon theme, and the Network Manager applet. Executing <code>sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet</code> will install them. ==== Fedora Linux ==== [[Fedora]] has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. ==== Ubuntu ==== There is a [https://ubuntubudgie.org/ community ISO] that contains [[Ubuntu]] with Budgie Desktop instead of GNOME. ==== Void Linux ==== <code>sudo xbps-install budgie-desktop</code> ==== OpenSUSE ==== Budgie can be selected during the OpenSUSE installation or installed afterward using <code>sudo zypper install budgie-desktop</code>. 10231d499e3d34cb2c0e90a500b69b506f468e17 0 269 2646 2420 2025-07-01T08:29:03Z Hog 161 Ported instructions over wikitext text/x-wiki {{Cleanup|Instructions should be separated onto their own page under the Guides namespace}} {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], budgie provides an easy to use Interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] === Features === '''Budgie Desktop View''' is a [[:Category:Software|software]] component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. [[Category:Desktop Environments]] 5413ad7cf871d3eabdd3119746e52af9c563f7cc 2647 2646 2025-07-01T08:30:40Z Hog 161 Normalised capitalisation and edited infobox wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Budgie.svg|borderless]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], Budgie provides an easy to use Interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] === Features === '''Budgie Desktop View''' is a [[:Category:Software|software]] component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. [[Category:Desktop Environments]] 319369b9ed861587294651f7baeca917245a830c 0 158 2648 2497 2025-07-01T08:35:22Z Hog 161 Formatted wikitext text/x-wiki ==== <u>Introduction</u> ==== When using [[Linux]], sooner or later, there's a good chance you'll end finding yourself in front of a [[TUI|terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a '''command'''. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include <code>echo</code>, <code>mv</code>, [[cat|<code>cat</code>]], etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with <code>sudo</code> followed with your original command. [[sudo]] tells your computer to ''do'' something as a ''super user'' which will allow you to bypass restrictions. It should be important to note that '''sudo is a separate package''' and may not be pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you will need to use something like <code>su</code> to log in as root and then run your command as root or install sudo as root. ==== <u>Useful Commands</u> ==== Furthermore, with commands you will likely need to include ''options'' that specify to the program how you want it to behave. One of the most common options is <code>--help</code>, which will usually tell program to list all of its options. An example would be as follows: cat --help In this case, the 'cat' utility would respond to this command with the following:<syntaxhighlight>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines ...</syntaxhighlight>These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, <code>--help</code> is always there and ready. If not, you can always run [[man|<code>man</code>]] before a program similarly to how you would run <code>sudo</code>, and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a file to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory|working directory]] (Like shown) or you can provide a file from anywhere in the [[filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt The tilda sign <code>~</code>, in Linux and some other [[Operating System|operating systems]], expands to the full [[Directory Path|directory path]] of the current user's home folder. Here is what it would look like to type out the whole path: nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 38c2c2304f30a54d37a39cc003143d6b0fb5c825 0 707 2649 2025-07-01T08:43:33Z Hog 161 Made a short page for GRUB wikitext text/x-wiki '''GRUB''' (short for '''GNU GRand Unified Bootloader''') is a boot loader package developed by the GNU Project.{{SoftwareInfobox|image=[[File:Grub-knoppix.jpg|thumb]]|caption=Grub Boot Menu|title=GRUB|releasestatus=Maintained|lastrelease=2.12, 2023-12-20|languages=[[C]], [[Assembly]]|developers=GNU Project|website=[http://gnu.org/software/grub/ GNU Page]}} [[Category:Software]] 8c39b08e5d75ef7742afb1a4fe9f304c0d09c0f2 2650 2649 2025-07-01T09:12:54Z Hog 161 Added more Information wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Grub-knoppix.jpg|thumb]]|caption=Grub Boot Menu|title=GRUB|releasestatus=Maintained|lastrelease=2.12, 2023-12-20|languages=[[C]], [[Assembly]]|developers=GNU Project|website=[http://gnu.org/software/grub/ GNU Page]}}'''GRUB''' (short for '''GNU GRand Unified Bootloader''') is a boot loader package , For [[UNIX|UNIX-Like]] Systems developed by the GNU Project. It provides the user with the option to choose between different [[Operating System|operating systems]] or [[kernel]] versions without having to use the BIOS. GRUB has two versions, GRUB 0 (Also known as GRUB Legacy) and GRUB 2. [[Category:Software]] 85036a21139b02fe62d7480b75535016ab6b7b9c 2651 2650 2025-07-01T09:23:50Z Hog 161 punctuation wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Grub-knoppix.jpg|thumb]]|caption=Grub Boot Menu|title=GRUB|releasestatus=Maintained|lastrelease=2.12, 2023-12-20|languages=[[C]], [[Assembly]]|developers=GNU Project|website=[http://gnu.org/software/grub/ GNU Page]}}'''GRUB''' (short for '''GNU GRand Unified Bootloader''') is a boot loader package For [[UNIX|UNIX-Like]] Systems developed by the GNU Project. It provides the user with the option to choose between different [[Operating System|operating systems]] or [[kernel]] versions without having to use the BIOS. GRUB has two versions, GRUB 0 (Also known as GRUB Legacy) and GRUB 2. [[Category:Software]] 86b7d1ef90dad6db645ed376d3acd46b4bd27ce6 2654 2651 2025-07-01T13:47:05Z Madonuko 140 stub wikitext text/x-wiki [[Category:Software]]{{Cleanup|stub article}}{{SoftwareInfobox |image=[[File:Grub-knoppix.jpg|thumb]] |caption=Grub Boot Menu |title=GRUB |releasestatus=Maintained |lastrelease=2.12, 2023-12-20 |languages=[[C]], [[Assembly]] |developers=GNU Project |website=[http://gnu.org/software/grub/ GNU Page] }}'''GRUB''' (short for '''GRand Unified Bootloader''') is a [[bootloader]] designed for [[UNIX|UNIX-like]] systems developed by the GNU Project. It provides the user with the option to choose between different [[Operating System|operating systems]] or [[kernel]] versions without having to use the [[BIOS]]. Originally developed by Erich Boleyn<ref>[http://www.uruk.org/grub/ GRUB -- GRand Unified Bootloader], Erich Boleyn (Accessed: 2025-07-01)</ref>, GRUB is now a part of the GNU project and comes with two versions, GRUB 0 (Also known as GRUB Legacy) and GRUB 2. Since GRUB Legacy is obsoleted and should no longer be used, this article mainly describes GRUB 2. == See More == * [https://wiki.archlinux.org/title/Grub Grub on ArchWiki] d9e8a4332129410163dde8ac92ead5b6c47a5d6c 0 656 2652 2461 2025-07-01T10:41:08Z Hog 161 added a tiny bit more info wikitext text/x-wiki {{DistributionInfobox |title=Batocera |image=[[file:Batocera-logo-art.png]] |caption=Batocera Logo |releasestatus=Maintained |releasemodel=Rolling Release |packagemanager=pacman |defaultdesktops=No Desktop |usagetype=placeholder |architectures=x86_64, Rpi4, Rpi5 |website=[https://batocera.org/ batocera.org] }} Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pi's and other micro computers. Batocera offers emulation cores for retro consoles and retro home computers. bf1ff8982a65fbf8e34b51f8e148fdf497cd021d 0 708 2653 2025-07-01T13:32:12Z Madonuko 140 redirect to [[GRUB]] wikitext text/x-wiki #REDIRECT [[GRUB]] 3604dd76195752af8f019df46f2553084e566e3b 0 709 2655 2025-07-01T14:09:37Z Madonuko 140 init wikitext text/x-wiki This article describes the general boot process of most Linux distributions. While most Linux distributions integrates varying components, the basic steps remain the same. == BIOS == The BIOS (Basic Input/Output System) is the firmware that initializes hardware components and provides a basic set of services to the kernel. It is obtained from the ROM and is responsible for loading the bootloader. Once the correct boot device is selected, the BIOS loads the boot sector, which is the first sector (512 bytes) of the boot device. The boot sector contains the bootloader, which is responsible for loading the kernel. == Bootloader == The bootloader is responsible for loading the kernel into memory and starting the kernel. Common bootloaders include [[GRUB]], [[Syslinux]], [[Limine]], [[systemd-boot]], [[rEFInd]], etc. Usually, the bootloader is stored separately from the kernel, in different [[partition]]s or even on a different device. It displays an interface, such as a text-based menu to select the kernel to boot. == Initramfs == The initramfs is a compressed filesystem that is loaded into memory during boot. It contains essential files and utilities required to mount the actual root [[filesystem]] and start the init process. The initramfs is typically created using [[mkinitcpio]] or [[dracut]]. == Kernel == The kernel is the core of the operating system and is responsible for managing hardware resources and providing a platform for user-space applications. It is responsible for initializing hardware, managing memory, and providing a virtual filesystem. It is loaded by the bootloader and starts the init process. == Init == The init process, which must be stored under <code>/sbin/init</code>, is responsible for initializing the system and starting the user-space applications. It is responsible for mounting the root filesystem, starting the necessary system services, and starting the graphical user interface. On most modern systems, this is [[systemd]]. Some older systems use [[sysvinit]] or [[upstart]]. == TTY == The [[TTY]] (Teletype) is a text-based interface that allows users to interact with the operating system. It is responsible for displaying text and accepting user input. It is typically used for logging in and running commands. It is also used for debugging and troubleshooting. The TTY is available even on modern systems and can be accessed through the {{Key press|Ctrl|Alt|F1}} to {{Key press|Ctrl|Alt|F6}} keys. == Display Manager == The [[display manager]] is responsible for managing the [[GUI|graphical user interface]]. On most modern systems, this is [[lightdm]], [[gdm]], or [[sddm]]. Once the user logs in, the display manager executes the [[window manager]] or [[desktop environment]] chosen by the user. e439d7c6266e3c4ec7ce068f7f4689b6710387bd 2656 2655 2025-07-02T07:46:33Z Hog 161 Added some citations (TBC) and fixed links wikitext text/x-wiki This article describes the general boot process of most Linux distributions.<ref>https://medium.com/@gangulysutapa96/6-stages-of-linux-boot-process-5ee84265d8a0 Medium.com, 2023 (Imported 02.07.25)</ref> While most Linux distributions integrates varying components, the basic steps remain the same. == BIOS == The BIOS (Basic Input/Output System) is the firmware that initializes hardware components and provides a basic set of services to the kernel.<ref>https://www.lenovo.com/gb/en/glossary/what-is-a-bios?srsltid=AfmBOopXGO9x6E-4ZTe5WNDbGEMlTYXBLk1ivYj5LXSQC8OTUAjEAASC Lenovo.com, 2025 (Imported 02.07.2025)</ref> It is obtained from the ROM and is responsible for loading the bootloader. Once the correct boot device is selected, the BIOS loads the boot sector, which is the first sector (512 bytes) of the boot device.<ref>https://neosmart.net/wiki/mbr-boot-process/ Neosmart.net, 2025 (Imported 02,07,2025)</ref>The boot sector contains the bootloader, which is responsible for loading the kernel. == Bootloader == The bootloader is responsible for loading the kernel into memory and starting the kernel. Common bootloaders include [[GRUB]], [[Syslinux]], [[Limine]], [[Systemd|systemd-boot]], [[rEFInd]], etc. Usually, the bootloader is stored separately from the kernel, in different [[partition]]s or even on a different device. It displays an interface, such as a text-based menu to select the kernel to boot. == Initramfs == The initramfs is a compressed filesystem that is loaded into memory during boot. It contains essential files and utilities required to mount the actual root [[filesystem]] and start the init process. The initramfs is typically created using [[mkinitcpio]] or [[dracut]]. == Kernel == The kernel is the core of the operating system and is responsible for managing hardware resources and providing a platform for user-space applications. It is responsible for initializing hardware, managing memory, and providing a virtual filesystem. It is loaded by the bootloader and starts the init process. == Init == The init process, which must be stored under <code>/sbin/init</code>, is responsible for initializing the system and starting the user-space applications. It is responsible for mounting the root filesystem, starting the necessary system services, and starting the graphical user interface. On most modern systems, this is [[systemd]]. Some older systems use [[sysvinit]] or [[upstart]]. == TTY == The [[TTY]] (Teletype) is a text-based interface that allows users to interact with the operating system. It is responsible for displaying text and accepting user input. It is typically used for logging in and running commands. It is also used for debugging and troubleshooting. The TTY is available even on modern systems and can be accessed through the {{Key press|Ctrl|Alt|F1}} to {{Key press|Ctrl|Alt|F6}} keys. == Display Manager == The [[Display Manager|display manager]] is responsible for managing the [[GUI|graphical user interface]]. On most modern systems, this is [[lightdm]], [[gdm]], or [[sddm]]. Once the user logs in, the display manager executes the [[Window Manager|window manager]] or [[Desktop Environments|desktop environment]] chosen by the user. 3a9f47b98c47cd94ea1f789af55ca6770bb66f7f 2659 2656 2025-07-02T10:31:50Z Hog 161 yet another citation wikitext text/x-wiki This article describes the general boot process of most Linux distributions.<ref>https://medium.com/@gangulysutapa96/6-stages-of-linux-boot-process-5ee84265d8a0 Medium.com, 2023 (Imported 02.07.25)</ref> While most Linux distributions integrates varying components, the basic steps remain the same. === BIOS === The BIOS (Basic Input/Output System) is the firmware that initializes hardware components and provides a basic set of services to the kernel.<ref>https://www.lenovo.com/gb/en/glossary/what-is-a-bios?srsltid=AfmBOopXGO9x6E-4ZTe5WNDbGEMlTYXBLk1ivYj5LXSQC8OTUAjEAASC Lenovo.com, 2025 (Imported 02.07.2025)</ref> It is obtained from the ROM and is responsible for loading the bootloader. Once the correct boot device is selected, the BIOS loads the boot sector, which is the first sector (512 bytes) of the boot device.<ref>https://neosmart.net/wiki/mbr-boot-process/ Neosmart.net, 2025 (Imported 02,07,2025)</ref>The boot sector contains the bootloader, which is responsible for loading the kernel. === Bootloader === The bootloader is responsible for loading the kernel into memory and starting the kernel. Common bootloaders include [[GRUB]], [[Syslinux]], [[Limine]], [[Systemd|systemd-boot]], [[rEFInd]], etc. Usually, the bootloader is stored separately from the kernel, in different [[partition]]s or even on a different device. It displays an interface, such as a text-based menu to select the kernel to boot. === Initramfs === The initramfs is a compressed filesystem that is loaded into memory during boot. It contains essential files and utilities required to mount the actual root [[filesystem]] and start the init process. The initramfs is typically created using [[mkinitcpio]] or [[dracut]]. === Kernel === The kernel is the core of the operating system and is responsible for managing hardware resources and providing a platform for user-space applications. It is responsible for initializing hardware, managing memory, and providing a virtual filesystem. It is loaded by the bootloader and starts the init process. === Init === The init process, which must be stored under <code>/sbin/init</code>, is responsible for initializing the system and starting the user-space applications. It is responsible for mounting the root filesystem, starting the necessary system services, and starting the graphical user interface. On most modern systems, this is [[systemd]]. Some older systems use [[sysvinit]] or [[upstart]]. === TTY === The [[TTY]] (Teletype) is a text-based interface that allows users to interact with the operating system. It is responsible for displaying text and accepting user input. It is typically used for logging in and running commands. It is also used for debugging and troubleshooting. The TTY is available even on modern systems and can be accessed through the {{Key press|Ctrl|Alt|F1}} to {{Key press|Ctrl|Alt|F6}} keys. === Display Manager === The [[Display Manager|display manager]] is responsible for managing the [[GUI|graphical user interface]].<ref>https://wiki.archlinux.org/title/Display_manager Arch wiki, 2025 (Imported 02.07.2025)</ref>On most modern systems, this is [[lightdm]], [[gdm]], or [[sddm]]. Once the user logs in, the display manager executes the [[Window Manager|window manager]] or [[Desktop Environments|desktop environment]] chosen by the user. 3339df2eb92b34056947db8cea43df1c667e9b6f 2697 2659 2025-07-08T13:11:25Z Hog 161 wikitext text/x-wiki This article describes the general boot process of most Linux distributions.<ref>https://medium.com/@gangulysutapa96/6-stages-of-linux-boot-process-5ee84265d8a0 Medium.com, 2023 (Imported 02.07.25)</ref> While most Linux distributions integrates varying components, the basic steps remain the same. === BIOS === The BIOS (Basic Input/Output System) is the firmware that initializes hardware components and provides a basic set of services to the kernel.<ref>https://www.lenovo.com/gb/en/glossary/what-is-a-bios?srsltid=AfmBOopXGO9x6E-4ZTe5WNDbGEMlTYXBLk1ivYj5LXSQC8OTUAjEAASC Lenovo.com, 2025 (Imported 02.07.2025)</ref> It is obtained from the ROM and is responsible for loading the bootloader. Once the correct boot device is selected, the BIOS loads the boot sector, which is the first sector (512 bytes) of the boot device.<ref>https://neosmart.net/wiki/mbr-boot-process/ Neosmart.net, 2025 (Imported 02.07.2025)</ref>The boot sector contains the bootloader, which is responsible for loading the [[kernel]]. === Bootloader === The bootloader is responsible for loading the kernel into memory and starting the kernel. Common bootloaders include [[GRUB]], [[Syslinux]], [[Limine]], [[Systemd|systemd-boot]], [[rEFInd]], etc. Usually, the bootloader is stored separately from the kernel, in different [[partition]]s or even on a different device. It displays an interface, such as a text-based menu to select the kernel to boot. === Initramfs === The initramfs is a compressed filesystem that is loaded into memory during boot. It contains essential files and utilities required to mount the actual root [[filesystem]] and start the init process. The initramfs is typically created using [[mkinitcpio]] or [[dracut]]. === Kernel === The kernel is the core of the operating system and is responsible for managing hardware resources and providing a platform for user-space applications. It is responsible for initializing hardware, managing memory, and providing a virtual filesystem. It is loaded by the bootloader and starts the init process. === Init === The init process, which must be stored under <code>/sbin/init</code>, is responsible for initializing the system and starting the user-space applications. It is responsible for mounting the root filesystem, starting the necessary system services, and starting the graphical user interface. On most modern systems, this is [[systemd]]. Some older systems use [[sysvinit]] or [[upstart]]. === TTY === The [[TTY]] (Teletype) is a text-based interface that allows users to interact with the operating system. It is responsible for displaying text and accepting user input. It is typically used for logging in and running commands. It is also used for debugging and troubleshooting. The TTY is available even on modern systems and can be accessed through the {{Key press|Ctrl|Alt|F1}} to {{Key press|Ctrl|Alt|F6}} keys. === Display Manager === The [[Display Manager|display manager]] is responsible for managing the [[GUI|graphical user interface]].<ref>https://wiki.archlinux.org/title/Display_manager Arch wiki, 2025 (Imported 02.07.2025)</ref>On most modern systems, this is [[lightdm]], [[gdm]], or [[sddm]]. Once the user logs in, the display manager executes the [[Window Manager|window manager]] or [[Desktop Environments|desktop environment]] chosen by the user. 07d8384ee88ceb65817a109f08c8b4047f4bac34 0 707 2657 2654 2025-07-02T08:26:56Z Hog 161 added information wikitext text/x-wiki [[Category:Software]]{{Cleanup|stub article}}{{SoftwareInfobox |image=[[File:Grub-knoppix.jpg|thumb]] |caption=Grub Boot Menu |title=GRUB |releasestatus=Maintained |lastrelease=2.12, 2023-12-20 |languages=[[C]], [[Assembly]] |developers=GNU Project |website=[http://gnu.org/software/grub/ GNU Page] }}'''GRUB''' (short for '''GRand Unified Bootloader''') is a [[bootloader]] designed for [[UNIX|UNIX-like]] systems developed by the GNU Project. It provides the user with the option to choose between different [[Operating System|operating systems]] or [[kernel]] versions without having to use the [[BIOS]]. Originally developed by Erich Boleyn<ref>[http://www.uruk.org/grub/ GRUB -- GRand Unified Bootloader], Erich Boleyn (Accessed: 2025-07-01)</ref>, GRUB is now a part of the GNU project and comes with two versions, GRUB 0 (Also known as GRUB Legacy) and GRUB 2. Since GRUB Legacy is obsoleted and should no longer be used, this article mainly describes GRUB 2. GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU Hurd with the University of Utah’s Mach 4 microkernel (now known as GNU Mach). Erich and Brian Ford designed the Multiboot Specification, because they were determined not to add to the large number of mutually-incompatible PC boot methods.<ref name=":0">https://www.gnu.org/software/grub/manual/grub/grub.html#Overview GNU website, 2025 (Imported 02.07.2025)</ref> Around 2002, Yoshinori K. Okuji started work on PUPA (Preliminary Universal Programming Architecture for GNU GRUB), aiming to rewrite the core of GRUB to make it cleaner, safer, more robust, and more powerful. PUPA was eventually renamed to GRUB 2, and the original version of GRUB was renamed to GRUB Legacy. <ref name=":0" /> GRUB contains support for multiple file systems ( [[FAT32]], [[ext4]], [[Btrfs]] or [[XFS]].) Both GRUB 2 and GRUB 0 systems support [[UEFI]] and BIOS-based systems. == See More == * [https://wiki.archlinux.org/title/Grub Grub on ArchWiki] 309389fd1d5bac2b01d8314fe1021de19ee4c705 2684 2657 2025-07-03T17:37:01Z Atmois 13 Remove cleanup tag wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox |image=[[File:Grub-knoppix.jpg|thumb]] |caption=Grub Boot Menu |title=GRUB |releasestatus=Maintained |lastrelease=2.12, 2023-12-20 |languages=[[C]], [[Assembly]] |developers=GNU Project |website=[http://gnu.org/software/grub/ GNU Page] }}'''GRUB''' (short for '''GRand Unified Bootloader''') is a [[bootloader]] designed for [[UNIX|UNIX-like]] systems developed by the GNU Project. It provides the user with the option to choose between different [[Operating System|operating systems]] or [[kernel]] versions without having to use the [[BIOS]]. Originally developed by Erich Boleyn<ref>[http://www.uruk.org/grub/ GRUB -- GRand Unified Bootloader], Erich Boleyn (Accessed: 2025-07-01)</ref>, GRUB is now a part of the GNU project and comes with two versions, GRUB 0 (Also known as GRUB Legacy) and GRUB 2. Since GRUB Legacy is obsoleted and should no longer be used, this article mainly describes GRUB 2. GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU Hurd with the University of Utah’s Mach 4 microkernel (now known as GNU Mach). Erich and Brian Ford designed the Multiboot Specification, because they were determined not to add to the large number of mutually-incompatible PC boot methods.<ref name=":0">https://www.gnu.org/software/grub/manual/grub/grub.html#Overview GNU website, 2025 (Imported 02.07.2025)</ref> Around 2002, Yoshinori K. Okuji started work on PUPA (Preliminary Universal Programming Architecture for GNU GRUB), aiming to rewrite the core of GRUB to make it cleaner, safer, more robust, and more powerful. PUPA was eventually renamed to GRUB 2, and the original version of GRUB was renamed to GRUB Legacy. <ref name=":0" /> GRUB contains support for multiple file systems ( [[FAT32]], [[ext4]], [[Btrfs]] or [[XFS]].) Both GRUB 2 and GRUB 0 systems support [[UEFI]] and BIOS-based systems. == See More == * [https://wiki.archlinux.org/title/Grub Grub on ArchWiki] d8c4f65c3d69a3481645b6ff73af5368536ec7d6 0 173 2658 2418 2025-07-02T10:28:28Z Hog 161 fixed citations wikitext text/x-wiki {{Cleanup|Incomplete page}} [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager (G'''DM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a [[graphical user interface]] that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.<ref>https://github.com/tvrzna/emptty GitHub, 2025 (Imported 02.07.2025)</ref> [[Category:Terminology]] 5510fe97ac09ac4823f4f66f6598d1b252992e40 0 158 2660 2648 2025-07-02T10:33:07Z Hog 161 wikitext text/x-wiki {{Needs Citations}} ==== <u>Introduction</u> ==== When using [[Linux]], sooner or later, there's a good chance you'll end finding yourself in front of a [[TUI|terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a '''command'''. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include <code>echo</code>, <code>mv</code>, [[cat|<code>cat</code>]], etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with <code>sudo</code> followed with your original command. [[sudo]] tells your computer to ''do'' something as a ''super user'' which will allow you to bypass restrictions. It should be important to note that '''sudo is a separate package''' and may not be pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you will need to use something like <code>su</code> to log in as root and then run your command as root or install sudo as root. ==== <u>Useful Commands</u> ==== Furthermore, with commands you will likely need to include ''options'' that specify to the program how you want it to behave. One of the most common options is <code>--help</code>, which will usually tell program to list all of its options. An example would be as follows: cat --help In this case, the 'cat' utility would respond to this command with the following:<syntaxhighlight>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines ...</syntaxhighlight>These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, <code>--help</code> is always there and ready. If not, you can always run [[man|<code>man</code>]] before a program similarly to how you would run <code>sudo</code>, and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a file to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory|working directory]] (Like shown) or you can provide a file from anywhere in the [[filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt The tilda sign <code>~</code>, in Linux and some other [[Operating System|operating systems]], expands to the full [[Directory Path|directory path]] of the current user's home folder. Here is what it would look like to type out the whole path: nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 6515777894a704e1bee6234e3d3585cfbc20bb92 2 655 2661 2618 2025-07-02T10:34:30Z Hog 161 punctuation wikitext text/x-wiki [[File:Sus scrofa f domesticus - Réserve africaine de Sigean 01.jpg|thumb|Photo of a hog i like]] I probably fixed your article bozo. I'm gonna put these tags here so i can copy and paste{{Work In Progress}}{{Needs Citations}}{{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{Cleanup|Incomplete page}} 074d953c85eeff9db7ce4c3c78b75e2080b6b11b 2688 2661 2025-07-04T08:15:22Z Hog 161 Removed warnings wikitext text/x-wiki [[File:Sus scrofa f domesticus - Réserve africaine de Sigean 01.jpg|thumb|Photo of a hog i like]] I probably fixed your article bozo. 3c3b992dae117cdaa1a690c0156c1185d5d1dd24 0 668 2662 2632 2025-07-02T10:38:54Z Hog 161 Added Links wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref>. == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor [[ed]] (1971) and the even earlier [[qed]] (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref>. sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; …} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to [[EOF]]. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10-15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 0b9328a6a9601f1634cb711e5328823ea2db977c 1 4 2663 385 2025-07-02T10:40:06Z Hog 161 /* I believe we should add a languages catagorie */ new section wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -[[Key Terms]] '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Pros and Cons between package formats -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) :Maybe most important commands to know "primer"? See for examples: :https://discord.com/channels/1172245377395728464/1172245377395728467/1237386711055601714 :https://discord.com/channels/1172245377395728464/1172245377395728467/1237388162440105984 [[User:Kaizen|Kaizen]] ([[User talk:Kaizen|talk]]) 13:50, 4 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) :I like the outline! I agree with Electron about organization and it applies to all of the categories - before writing these, we should have a general idea of ''all'' our subcategories [[User:Asiliria|Asiliria]] ([[User talk:Asiliria|talk]]) 23:40, 3 June 2024 (UTC) == I believe we should add a languages catagorie == see above [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 10:40, 2 July 2025 (UTC) 6a9f568b0d56d52d20eb48288aea7f1820359d84 2666 2663 2025-07-03T05:12:26Z Madonuko 140 /* I believe we should add a languages catagorie */ Reply wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -[[Key Terms]] '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Pros and Cons between package formats -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) :Maybe most important commands to know "primer"? See for examples: :https://discord.com/channels/1172245377395728464/1172245377395728467/1237386711055601714 :https://discord.com/channels/1172245377395728464/1172245377395728467/1237388162440105984 [[User:Kaizen|Kaizen]] ([[User talk:Kaizen|talk]]) 13:50, 4 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) :I like the outline! I agree with Electron about organization and it applies to all of the categories - before writing these, we should have a general idea of ''all'' our subcategories [[User:Asiliria|Asiliria]] ([[User talk:Asiliria|talk]]) 23:40, 3 June 2024 (UTC) == I believe we should add a languages catagorie == see above [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 10:40, 2 July 2025 (UTC) :The wiki itself is English-only though? [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 05:12, 3 July 2025 (UTC) efa7d19d99cadad98dafadf3e72e58f9564fac38 2667 2666 2025-07-03T07:46:42Z Atmois 13 /* I believe we should add a languages catagorie */ Reply wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -[[Key Terms]] '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Pros and Cons between package formats -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) :Maybe most important commands to know "primer"? See for examples: :https://discord.com/channels/1172245377395728464/1172245377395728467/1237386711055601714 :https://discord.com/channels/1172245377395728464/1172245377395728467/1237388162440105984 [[User:Kaizen|Kaizen]] ([[User talk:Kaizen|talk]]) 13:50, 4 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) :I like the outline! I agree with Electron about organization and it applies to all of the categories - before writing these, we should have a general idea of ''all'' our subcategories [[User:Asiliria|Asiliria]] ([[User talk:Asiliria|talk]]) 23:40, 3 June 2024 (UTC) == I believe we should add a languages catagorie == see above [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 10:40, 2 July 2025 (UTC) :The wiki itself is English-only though? [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 05:12, 3 July 2025 (UTC) ::I believe its for programming languages, I can add a category but i wont add a button for now as the homepage structure is due to change. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 07:46, 3 July 2025 (UTC) df0fabfb5a0aa7562bc9aa0a1469087ea1141d66 2668 2667 2025-07-03T08:13:22Z Hog 161 /* I believe we should add a languages catagorie */ Reply wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -[[Key Terms]] '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Pros and Cons between package formats -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) :Maybe most important commands to know "primer"? See for examples: :https://discord.com/channels/1172245377395728464/1172245377395728467/1237386711055601714 :https://discord.com/channels/1172245377395728464/1172245377395728467/1237388162440105984 [[User:Kaizen|Kaizen]] ([[User talk:Kaizen|talk]]) 13:50, 4 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) :I like the outline! I agree with Electron about organization and it applies to all of the categories - before writing these, we should have a general idea of ''all'' our subcategories [[User:Asiliria|Asiliria]] ([[User talk:Asiliria|talk]]) 23:40, 3 June 2024 (UTC) == I believe we should add a languages catagorie == see above [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 10:40, 2 July 2025 (UTC) :The wiki itself is English-only though? [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 05:12, 3 July 2025 (UTC) ::I believe its for programming languages, I can add a category but i wont add a button for now as the homepage structure is due to change. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 07:46, 3 July 2025 (UTC) :::yeh i meant programming languages lol [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 08:13, 3 July 2025 (UTC) b6f26ff434b796bd09c8ba322099c75e5ccd8da9 0 261 2664 1199 2025-07-02T10:48:17Z Hog 161 added a tiny bit more info wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was created by Dylan Araps in 2017 and was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]] (Neofetch-like utility written in [[C]]) and [[hyfetch]] (Fork of neofetch with pride flags). <references /> [[Category:Software]] dc8595932d0e6751db25224c038bcf90e24798ac 2683 2664 2025-07-03T16:59:44Z Atmois 13 Clean up writing wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was created by Dylan Araps in 2017 and was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]], a neofetch-like utility written in [[C]], and [[hyfetch]], a fork of neofetch with pride flags. <references /> [[Category:Software]] e83224383c916ce6c71d63958c101794a3bcd023 0 236 2665 2622 2025-07-02T10:50:58Z Hog 161 Fixed Links wikitext text/x-wiki {{Needs_Citations}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.20, 2024-12-15 | languages = [[C]] | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight [[Desktop Environments|desktop environment]] aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * [[Desktop Manager]] - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[TUI|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> [[Category:Desktop Environments]] 44029ef8846167408850f4fcd05b78351aef6d03 0 269 2669 2647 2025-07-03T08:14:05Z Hog 161 changed Logo wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], Budgie provides an easy to use Interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] === Features === '''Budgie Desktop View''' is a [[:Category:Software|software]] component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. [[Category:Desktop Environments]] fd3fa5748bde375691a17bdfb34faaf543f7f1a4 2682 2669 2025-07-03T16:56:42Z Atmois 13 Add citations template wikitext text/x-wiki {{Needs Citations}}{{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], Budgie provides an easy to use Interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] === Features === '''Budgie Desktop View''' is a [[:Category:Software|software]] component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in [[C]], and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. [[Category:Desktop Environments]] 950dfe386fe9cbb9c808e890a0d9ff6a6134000c 0 341 2670 2083 2025-07-03T08:27:38Z Hog 161 added and corrected information wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:Tde-logo.png]] | caption = Trinity Desktop Environment logo | title = Trinity Desktop Environment | releasestatus = Maintained | lastrelease = R14.1.3, 2024-10-27 | languages = [[C++]] | developers = Trinity Development Team | website = [https://www.trinitydesktop.org/ trinitydesktop.org] }} [[File:Trinity R.14.1.3 screenshot.png|thumb|Screenshot of Trinity Desktop R14.1.3]] Trinity Desktop Environment (TDE) is an X11 [[Desktop Environments|desktop environment]] for [[Unix-Like]] [[Operating System|Operating systems]] forked from KDE 3.5 in 2010. Trinity is packaged for [[Arch Linux]], [[Debian]], [[Fedora]], [[Gentoo]], [[Mageia]], [[OpenSUSE]], [[Raspberry Pi OS]], [[Red Hat Enterprise Linux]], [[Slackware]], [[Ubuntu]] and various other [[Linux Distributions|distributions]] [[Category:Desktop Environments]] 802da03b44b1cf0da7d1620131e75de869a0d292 0 176 2671 2508 2025-07-03T08:38:30Z Hog 161 corrected logo wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[UNIX|UNIX-Based]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] a9a45a1886ecd181a935f8b866639ae7020a8ce8 0 623 2672 2248 2025-07-03T08:46:34Z Hog 161 reformatting wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}'''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">https://endeavouros.com/</ref> {{DistributionInfobox|title=EndeavourOS|image=[[File:EndeavourOS Logo.svg|Thumb]]|caption=The Endeavour OS logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, aArch64|website=[https://endeavouros.com endeavouros.org]}} === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>https://endeavouros.com/about-us/</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning Arch Linux fundamentals. === Installation === EndeavourOS provides an ISO with the Calamares installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === EndeavourOS is fully compatible with Arch Linux, meaning it uses Arch's official repositories directly and adheres closely to Arch’s philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * AUR Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate AUR package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * Pacman Compatibility: Fully compatible with Arch’s pacman package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for Arch Linux are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla Arch, or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the AUR, as well as EndeavourOS-specific themes and utilities.<ref>https://repo.c48.uk/endeavouros/repo/endeavouros/</ref> This is simply a pacman repository that can simply be added to any Arch Linux system if desired. 1154d56e317148e6a8cffa6ba1b8bc7a3a04fd7b 2680 2672 2025-07-03T16:48:08Z Atmois 13 Move infobox wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=EndeavourOS|image=[[File:EndeavourOS Logo.svg|Thumb]]|caption=The Endeavour OS logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, aArch64|website=[https://endeavouros.com endeavouros.org]}}'''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">https://endeavouros.com/</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>https://endeavouros.com/about-us/</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning Arch Linux fundamentals. === Installation === EndeavourOS provides an ISO with the Calamares installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === EndeavourOS is fully compatible with Arch Linux, meaning it uses Arch's official repositories directly and adheres closely to Arch’s philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * AUR Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate AUR package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * Pacman Compatibility: Fully compatible with Arch’s pacman package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for Arch Linux are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla Arch, or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the AUR, as well as EndeavourOS-specific themes and utilities.<ref>https://repo.c48.uk/endeavouros/repo/endeavouros/</ref> This is simply a pacman repository that can simply be added to any Arch Linux system if desired. e204919e365b05973a5e68fb3f3b7dd4a732fb9c 2693 2680 2025-07-07T11:43:51Z Hog 161 wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=EndeavourOS|image=[[File:EndeavourOS Logo.svg|Thumb]]|caption=The Endeavour OS logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, aArch64|website=[https://endeavouros.com endeavouros.org]}}'''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">https://endeavouros.com/</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>https://endeavouros.com/about-us/</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning Arch Linux fundamentals. === Installation === EndeavourOS provides an ISO with the Calamares installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with Arch Linux, meaning it uses Arch's official repositories directly and adheres closely to Arch’s philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * AUR Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate AUR package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * Pacman Compatibility: Fully compatible with Arch’s pacman package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for Arch Linux are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla Arch, or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the AUR, as well as EndeavourOS-specific themes and utilities.<ref>https://repo.c48.uk/endeavouros/repo/endeavouros/</ref> This is simply a pacman repository that can simply be added to any Arch Linux system if desired. 0a9b242dfdab09d2f68c8ead5c49f36cde595932 0 534 2673 2452 2025-07-03T08:57:02Z Hog 161 Made capitalisation consistant wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example Niri Rice|title=niri|releasestatus=Maintained|firstrelease=v0.1.0-alpha.1|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]], an extension for [[GNOME]] <ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">https://github.com/YaLTeR/niri/wiki/Important-Software</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading <references /> be74d2f5736ec2555e25987ffe00e571f492db65 2679 2673 2025-07-03T16:45:04Z Atmois 13 Reword reference to inspiration for niri wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example Niri Rice|title=niri|releasestatus=Maintained|firstrelease=v0.1.0-alpha.1|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">https://github.com/YaLTeR/niri/wiki/Important-Software</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading <references /> 5e38c463c5b10765fc7130184ee90a5e993efaf4 0 428 2674 2510 2025-07-03T09:23:06Z Hog 161 wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' (short for ''manual'') is a [[TUI|command-line]] utility available on [[UNIX]] and UNIX-like [[Operating System|operating systems]] that provides documentation for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a man page the user can enter the following into their [[TUI|terminal]]:<ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> man ''<command_name>'' For example, to read the manual for <code>man</code> command itself: man man == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER<code> environment variable. By default, it uses <code>less<code>. Alternatively, the </code>-P</code> or </code>--pager</code> option can be used. <ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally. <ref>https://fishshell.com/docs/current/faq.html</ref> <references /> 0ce92d33ee097c1a7c37ec943b5a2763d6037b5b 0 164 2675 2382 2025-07-03T11:51:08Z Hog 161 (I see the warning but i was removing the link to "Choosing your distribution") wikitext text/x-wiki {{Work In Progress}} == Introduction == The [[Linux]] community is abundant with awesome projects and various other guides worth checking out, Here's some great ones that we have found - keep in mind that, while these guides are very useful, they are not fully exhaustive. More than likely you discover new software every day! * Privacy is not an end goal, but a consistent journey that needs to be taken very seriously. ''Always'' seek help when in doubt and ensure you take everything with a grain of salt. ''Do not just blindly follow guides but use your own intuition!'' == Guides == * https://www.privacyguides.org/ - An essential guide to learning not just ''how'' to begin your privacy journey online but offers a comprehensive explanation of abstract privacy concepts that is simple to understand and by extension ''is assuredly not easy or quick -'' read with an open mind! ** https://awesome-privacy.xyz - More of a guide to tools you may find yourself wanting to use to enhance privacy, rather than an explanation. The next step from Privacy Guides, essentially. ** https://www.privacytools.io/ - Similar to Awesome Privacy, and offers a wide range of tools. This specific website is recommended very frequently. * https://brainfucksec.github.io/firefox-hardening-guide - A guide to "de-Mozilla" and security-harden Firefox. Assess whether or not this is a good option for you - ''similar to privacy, it is not an easy process.'' * https://rentry.co/fmhy-guides - General, yet extremely useful and even nuanced guides that you may find yourself needing for something very specific and hard to find on the internet. * https://github.com/luong-komorebi/Awesome-Linux-Software - Very extensive guide of not solely Linux software but mostly open-source software that has many use cases in mind. May be helpful in picking a flavor of Linux for your specific use cases. == Wikis == * https://wiki.archlinux.org/ for Arch Linux * https://wiki.gentoo.org/ for Gentoo * https://wiki.debian.org/ for Debian * https://fedoraproject.org/wiki/Fedora_Project_Wiki for Fedora * https://wiki.ubuntu.com for Ubuntu == Tools == * https://christitus.com/windows-tool/ - Used for debloating and removing telemetry from Windows. * https://alternativeto.net - A tool to find alternatives to popular software, both open-source and proprietary. * https://etcher.balena.io/ - An open-source tool to flash operating systems to an USB drive. [[Category:Guides]] e4359b54b3e854b9d0c2a307f18d3e798b2b4da6 0 700 2676 2628 2025-07-03T12:10:08Z Hog 161 added qml wikitext text/x-wiki Calamares is a distribution-independent system installer, with an advanced partitioning feature for both manual and automated partitioning operations. Calamares is designed to be customizable by distribution maintainers without the need for cumbersome patching, thanks to third-party branding and external modules support.<ref>https://github.com/calamares/calamares Calamares Github, 2025 (27th June 2025)</ref> {{SoftwareInfobox|image=[[File:Calamares on Debian 10 screenshot.jpg|frameless]]|caption=Calamares Installer|title=Calamares|releasestatus=Maintained|lastrelease=3.3.14 (Feb 20, 2025)|languages=[[C++]], [[Python]], [[QML]]|developers=Adriaan de Groot|website=https://calamares.io/}} <references /> [[Category:Software]] dbe212a7cc663990f03e21d9f62c6790996074e8 2677 2676 2025-07-03T16:34:14Z Atmois 13 Update URL wikitext text/x-wiki Calamares is a distribution-independent system installer, with an advanced partitioning feature for both manual and automated partitioning operations. Calamares is designed to be customizable by distribution maintainers without the need for cumbersome patching, thanks to third-party branding and external modules support.<ref>https://github.com/calamares/calamares Calamares Github, 2025 (27th June 2025)</ref> {{SoftwareInfobox|image=[[File:Calamares on Debian 10 screenshot.jpg|frameless]]|caption=Calamares Installer|title=Calamares|releasestatus=Maintained|lastrelease=3.3.14 (Feb 20, 2025)|languages=[[C++]], [[Python]], [[QML]]|developers=Adriaan de Groot|website=[https://calamares.io/ calamares.io]}} <references /> [[Category:Software]] cc2b1e4a9e248a03c312a69275c8e528ddd7754d 2678 2677 2025-07-03T16:40:13Z Atmois 13 Move infobox wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Calamares on Debian 10 screenshot.jpg|frameless]]|caption=Calamares Installer|title=Calamares|releasestatus=Maintained|lastrelease=3.3.14 (Feb 20, 2025)|languages=[[C++]], [[Python]], [[QML]]|developers=Adriaan de Groot|website=[https://calamares.io/ calamares.io]}}Calamares is a distribution-independent system installer, with an advanced partitioning feature for both manual and automated partitioning operations. Calamares is designed to be customizable by distribution maintainers without the need for cumbersome patching, thanks to third-party branding and external modules support.<ref>https://github.com/calamares/calamares Calamares Github, 2025 (27th June 2025)</ref><references /> [[Category:Software]] 11d405c26bc6678cc27846a784dd78b70574b2dd 0 667 2681 2608 2025-07-03T16:55:31Z Atmois 13 Move infobox wikitext text/x-wiki {{Cleanup|Incomplete page}}{{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}}'''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. a3b93216bce82a87539cc577d3152c095e49d848 3000 701 2685 2635 2025-07-03T17:40:18Z Atmois 13 Atmois moved page [[Ollama]] to [[Guides:Ollama Setup]] without leaving a redirect: Move to guides page wikitext text/x-wiki Ollama is a runtime for running AI models locally or on a personal server. == Installation == === Official Install Script === curl -fsSL <nowiki>https://ollama.com/install.sh</nowiki> | sh === Arch Linux === ==== No GPU ==== sudo pacman -S ollama ==== ROCm (AMD) ==== sudo pacman -S ollama-rocm ==== CUDA (Nvidia) ==== sudo pacman -S ollama-cuda == Using Models == When picking models, ensure there is enough memory to fit the model you are using. Models small enough to fit in the GPUs memory will only use the GPU while models too big to fit in the GPU will use a mix of GPU and CPU. To check GPU and CPU memory usage run: ollama ps === From Terminal === Gemma 3 will download if not already on the system and then run. ollama run gemma3 Gemma 3 by default uses the 4B version of the model but different versions can be specified. ollama run gemma3:12b Ollama uses q4_K_M quantisation by default but different quantisation level can be specified. ollama run gemma3:12b-it-q8_0 === From a Graphical User Interface === ==== Alpaca ==== Alpaca is officially distributed as a Flatpak. flatpak install flathub com.jeffser.Alpaca Alpaca can be configured to use Ollama externally including remote hosts but can also install Ollama internally as a Flatpak. flatpak install flathub com.jeffser.Alpaca.Plugins.Ollama The Flatpak Ollama plugin can support AMD GPUs using another plugin. flatpal install flathub com.jeffser.Alpaca.Plugins.AMD ==== Visual Studio Code ==== Ollama can be integrated into Visual Studio Code using [https://marketplace.visualstudio.com/items?itemName=Continue.continue Continue]. == Officially Supported GPUs == Consult this [https://github.com/ollama/ollama/blob/main/docs/gpu.md table] for official GPU support. == Use Unsupported AMD GPUs on ROCm == To use ROCm on GPUs not officially supported by Ollama we can extend the Systemd service file with the following command: sudo systemctl edit ollama.service This will open up a file in the systems text editor where you can extend the service. Below are examples of what to add to the file: === Example: Radeon RX 6000 series === <syntaxhighlight> [Service] Environment="HSA_OVERRIDE_GFX_VERSION=10.3.0" </syntaxhighlight> === Example: Radeon RX 5000 series === <syntaxhighlight> [Service] Environment="HSA_OVERRIDE_GFX_VERSION=10.1.0" </syntaxhighlight>The Ollama service will need to be restarted before the GPU can be used. sudo systemctl restart ollama.service 638a525db686d8800be6f87a4a885939a9284d68 0 663 2686 2621 2025-07-03T17:41:02Z Atmois 13 Remove cleanup tag wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terra.fyralabs.com terra.fyralabs.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora]] Linux and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terra.fyralabs.com/ Terra], Terra, 2024 (Accessed: 2025-06-19)</ref> Developed by Fyra Labs, it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://developer.fyralabs.com/terra/infrastructure How Terra Works], Fyra Labs, 2025 (Accessed: 2025-06-19)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://developer.fyralabs.com/terra/installing. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji], RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://developer.fyralabs.com/terra/autoupdate Automatic Updates - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases :: Fedora Docs], Fedora, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably [[Rust]], [[Go]], [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://developer.fyralabs.com/terra/policy Policy – Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> == See Also == * [https://terra.fyralabs.com Main Website] * [https://developer.fyralabs.com/terra Fyra Developer Documentations for Terra] * [https://github.com/terrapkg/packages Terra Sources] 52aad40c36ac58d038b169ce069f99fda3c4b1d2 0 218 2687 2400 2025-07-04T08:14:48Z Hog 161 Added Links wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} == Introduction == [[Linux]] is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most tiling Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> 67aeeb0cdf951bf9ec01427d47e5e0d0a77c9800 0 178 2689 2055 2025-07-04T08:18:17Z Hog 161 wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] Linux in itself refers to two entities, the former being the [[kernel]] itself developed by Linus Torvalds and the latter being the families of [[Linux Distributions|Operating Systems based off the Kernel]]. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. <references /> [[Category:Terminology]] fffa3c26ed17278a73dcfd387b03c36f5159c744 2 3 2690 2619 2025-07-04T17:02:30Z Amadaluzia 52 Reduce nested generic types wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <vector> #include <print> // Compile with C++23 or above. This will not work otherwise. struct SocialPair { std::string service, username; }; struct AboutMe { std::string name, description; std::vector<SocialPair> socials; }; int main(void) { struct AboutMe amadaluzia { .name = "Artur Manuel", .description { "I live in the UK and the internet as a background character in many\n" "free software communities (for example: you may find me on some\n" "mailing list) but I also contribute, most notably in nixpkgs.\n" "I do have other interests, such as gym, walking and photography, as\n" "well as speedrunning, filming and revising for english/maths among\n" "other things.\n" }, .socials { {"Signal", "@amadaluzia.711"}, {"Email", "amad@atl.tools"}, {"XMPP", "amadaluzia@xmpp.earth"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Libera.Chat", "amadaluzia"}, {"Discord", "amadaluzia"}, }, }; std::println("Hello, I am {}.", amadaluzia.name); std::println("{}", amadaluzia.description); std::println("You may find me on the following platforms:"); for (auto const &[service, username] : amadaluzia.socials) std::println("{} on {}", username, service); return 0; }</syntaxhighlight> 673e78b3f6b4f0fb8af44c76aa3ac01d6833b5c7 5 710 2691 2025-07-07T11:26:45Z Hog 161 /* Punctuation mistake at June 2024 */ new section wikitext text/x-wiki == Punctuation mistake at June 2024 == W e [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 11:26, 7 July 2025 (UTC) 84c9416420ac899d88a5079e59547447d711f313 2695 2691 2025-07-07T14:05:06Z Atmois 13 /* Punctuation mistake at June 2024 */ Reply wikitext text/x-wiki == Punctuation mistake at June 2024 == W e [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 11:26, 7 July 2025 (UTC) :Resolved. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 14:05, 7 July 2025 (UTC) 3df7c085d6c0a1caa1f069ef5002a986f54c683a 0 569 2692 2018 2025-07-07T11:38:00Z Hog 161 wikitext text/x-wiki {{Cleanup|Incomplete page}} {{MascotInfobox | title = Beastie (BSD Daemon) | image = [[File:Daemon-phk.svg|borderless]] | caption = Beastie, the BSD mascot }} Beastie is the mascot of [https://freebsd.org/ FreeBSD and BSD] Beastie is a red devil (daemon) who wears green sneakers and holds a yellow trident. [[Category:Mascots]] 9055a800b56b04aadd440cf568344016122e6eac 4 556 2694 2598 2025-07-07T14:04:57Z Atmois 13 Fix typo wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[Atl.wiki:Contact|contact page]]! == Important Links == * [[Atl.wiki:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[Atl.wiki:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[Atl.wiki:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin == History == ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the [https://discord.gg/linux All Things Linux discord]. [[User:Electron271|Electron271]], Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, [[User:Kaizen|Kaizen]]. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spambots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also reimplemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[Special:Favoritelist|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to relicence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another relicencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[Atl.wiki:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== The Future ===== Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] 6c1dbf2fa00faea91ebaeb05ca1cd6d9d54c3cd3 4 340 2696 2395 2025-07-07T20:49:30Z Atmois 13 Clean up writing wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update list pages (e.g., [[Linux Distributions]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the standards of the wiki and what can be improved upon. It will add said page to [[:Category:Pages Needing Cleanup]]. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>).</code> e.g., [https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy], Linux Foundation, 2015 (Accessed: November 27, 2024). Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between major citation and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible. If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. It will add said page to [[:Category:Needs Citations]]. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} <references /> [[Category:Meta]] 04fca42b8f3984fc43be5853e58523d980fa0ffe 2703 2696 2025-07-10T17:12:20Z Atmois 13 Cleanup the page wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Standards == Other things to keep in mind when making edits include: * Ensure that your page appropriately links to other pages by adding links when necessary, and you update category list pages (e.g., [[Linux Distributions]] or [[Desktop Environments]]) when making a new entry. * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer " uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] for our own needs and refined to what is seen to be fit by the team.'' [[Category:Meta]] 6cb6200e56f3161c657e786c9c19dc9897502f99 3000 695 2698 2603 2025-07-08T13:45:03Z Hog 161 wikitext text/x-wiki === Installation === ==== On [[Debian]] and Debian-based distributions: ==== You can sometimes install using a software manager, such as [[synaptic]].<syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> == <u>See Also</u> == [[I3]] 82124fe529987f7964e8241f6cfe7e9708c9c6b1 0 568 2699 2085 2025-07-09T08:30:25Z Hog 161 added alt text wikitext text/x-wiki {{Needs_Citations}} {{MascotInfobox | title = Xue | image = [[File:Xfce-xue.jpg|borderless]] | caption = Xue the XFCE mascot | alt =A small black illustrated mouse }} Xue is the mascot of [https://xfce.org/ XFCE] Xue is described as a black female mouse in [https://supertuxkart.net/Main_Page SuperTuxKart] [[Category:Mascots]] ec9f3f9e50746ef0dc0affd91d7fb0911d124ff6 2702 2699 2025-07-10T15:50:20Z Atmois 13 Fix alt text wikitext text/x-wiki {{Needs_Citations}} {{MascotInfobox | title = Xue | image = [[File:Xfce-xue.jpg |frameless |alt=A small black illustrated mouse]] | caption = Xue the XFCE mascot }} Xue is the mascot of [https://xfce.org/ XFCE] Xue is described as a black female mouse in [https://supertuxkart.net/Main_Page SuperTuxKart] [[Category:Mascots]] d908df32dcd7cb586a9b3a05deef79a19067e7bb 0 2 2700 2637 2025-07-10T13:25:43Z Hog 161 wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. <references /> [[Category:Linux Distributions]] 64a3dba8acbbc8280af7ef6bce568b89ec5e2865 4 327 2701 2588 2025-07-10T13:52:49Z Atmois 13 wikitext text/x-wiki test a94a8fe5ccb19ba61c4c0873d391e987982fbbd3 0 711 2704 2025-07-10T17:13:15Z Atmois 13 Create redirect wikitext text/x-wiki #REDIRECT [[Atl.wiki:Guidelines#Citations]] 669b9e2e1586efc6f6d294df76ea312d8a825eb2 0 240 2705 2617 2025-07-11T10:07:56Z Hog 161 added alt text wikitext text/x-wiki {{Cleanup|Incomplete page}}{{Needs Citations}} == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your distribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most derivative distributions. ==== General Information ==== ===== Multi Booting ===== [[File:GRUB with ubuntu and windows vista.png|alt=A black and white grub menu, it contains entries for Ubuntu Linux and Windows Vista|thumb|GRUB, with entries for [[Ubuntu]] and Windows Vista, an example of ''dual booting.'']] [[Multi Booting]] (Or often refered to as 'Dual Booting') is the process of installing multiple [[Operating System|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completely removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to partition the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly recommended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi Booting]] page. ===== Finding Alternatives or Workarounds for Apps ===== Often there is at least one [[application]] missing on Linux or an app that is missing some features or is buggy so you'll find yourself looking for alternative options. There also sometimes is the issue that your distribution doesn't have an app but another distribution does have it. A good place to start when looking for alternatives is [https://alternativeto.net AlternativeTo] which is a crowdsourced site useful to find alternatives for almost any app. Other useful sites include [https://www.privacytools.io Privacy Tools] and [https://awesome-privacy.xyz Awesome Privacy] with a privacy focused list of apps. When looking for workarounds for apps not supported for your distribution you should first check [https://flathub.org Flathub] and [https://snapcraft.io Snapcraft] (Note that [[Snap|Snaps]] are known to have performance issues) if your app is available there as they offer support for most distributions. If a steam game lacks native Linux support try checking [https://www.protondb.com ProtonDB] if Valve's proton tool supports your game. [https://www.winehq.org Wine] is also an option to run Windows apps on Linux. ==== Moving between specific Operating Systems ==== ===== Moving to Linux from MacOS ===== ===== Moving to Linux from Windows ===== === General Information === [[Category:Guides]] 6b34f68c2ed4806c5e83d3fc0bbac5bfcc058762 0 173 2706 2658 2025-07-11T10:13:27Z Hog 161 wikitext text/x-wiki {{Cleanup|Incomplete page}} [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager ('''GDM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a [[graphical user interface]] that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.<ref>https://github.com/tvrzna/emptty GitHub, 2025 (Imported 02.07.2025)</ref> [[Category:Terminology]] 1145b179089c7ea1d545a9e2a055f83c50adb16b 0 679 2707 2631 2025-07-11T11:58:16Z Hog 161 wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git’s early design emphasized a distributed workflow similar to BitKeeper’s but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like GitHub, which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. ce98ae86b2335e9fffa8c6fc525a5a58fe9637e4 2708 2707 2025-07-11T11:59:10Z Hog 161 wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = Git | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git’s early design emphasized a distributed workflow similar to BitKeeper’s but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like GitHub, which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>Git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>Git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>Git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>Git checkout -b new_branch_name</code> or <code>Git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>Git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>Git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>Git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>Git rm</code> to remove files. Alternatively, <code>Git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>Git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>Git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>Git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>Git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>Git stash</code> can be popped using <code>Git stash pop</code>. You can also list all stashes using <code>Git stash list</code>, drop a stash using <code>Git stash drop</code>, clear all stashes using <code>Git stash clear</code>, and apply a stash using <code>Git stash apply</code>. === Checkout === The <code>Git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>Git checkout</code> !Action !Command |- |Switch to master branch | <code>Git checkout master</code> |- |Create and switch to develop branch | <code>Git checkout -b develop</code> |- |Create and switch to feature branch, based on develop | <code>Git checkout -b feature develop</code> |- |Obtain files from develop into working directory | <code>Git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory | <code>Git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>Git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>Git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>Git push</code>. To pull changes from a remote repository, you can use <code>Git pull</code>. === Revert and Reset === <code>Git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>Git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>Git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>Git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>Git bisect start</code> starts the bisect process. Here the user should use <code>Git bisect good</code> and <code>Git bisect bad</code> to mark the known good and bad commits. After that, Git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>Git bisect good</code> or <code>Git bisect bad</code>. ca6ff394b2d01bf0e4e6eaf337155b97656e4d70 2714 2708 2025-07-11T19:42:25Z Madonuko 140 Undo revision [[Special:Diff/2708|2708]] by [[Special:Contributions/Hog|Hog]] ([[User talk:Hog|talk]]) wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git’s early design emphasized a distributed workflow similar to BitKeeper’s but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like GitHub, which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. ce98ae86b2335e9fffa8c6fc525a5a58fe9637e4 0 318 2709 2022 2025-07-11T12:31:32Z Hog 161 wikitext text/x-wiki {{Needs Citations}} The bootloader is a [[:Category:Software|program]] that's responsible for booting the system. Most of the time, it will have a menu to choose an option from, making it a boot manager. A bootloader is installed onto the boot partition of the computer during a [[Linux Distributions|distribution's]] installation process. Most of the times, boot partitions may need from 200 to 600MB of space to work properly. Most bootloaders also have theming capabilities, take, for example, [[GRUB]]. [[Category:Terminology]] 83a6a862597c4ec677e7a16854af9cd3f8552b80 0 279 2710 2066 2025-07-11T12:38:18Z Hog 161 wikitext text/x-wiki {{Needs_Citations}} == Introduction == {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, ppc64, x86_64 | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. This distribution stands out by having two variations of the distributions: OpenSUSE Tumbleweed is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. OpenSUSE Leap is the point release version, with a new release every year with older and more stable packages meant for business use. [[Category:Linux Distributions]] 679064d604ed3a48b199a42894367c0098c0e322 0 682 2711 2569 2025-07-11T12:39:01Z Hog 161 wikitext text/x-wiki '''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003.{{DistributionInfobox|title=Puppy Linux|image=[[File:Puppy logo.svg|frameless|Puppy Linux Logo]]|caption=Puppy Linux Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=[[ICEWM]]|usagetype=Desktop|architectures=x86_64, x86, ARM|website=[https://puppylinux-woof-ce.github.io/ Link]}} 74e636095e1e909b3244b4f47067bd941299d79b 0 171 2712 2609 2025-07-11T12:39:37Z Hog 161 wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = Customizable based on user configuration | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. <references /> [[Category:Linux Distributions]] 72f6665be5220e94afab7159849666849292ca02 0 656 2713 2652 2025-07-11T12:40:09Z Hog 161 wikitext text/x-wiki {{DistributionInfobox |title=Batocera |image=[[file:Batocera-logo-art.png|frameless]] |caption=Batocera Logo |releasestatus=Maintained |releasemodel=Rolling Release |packagemanager=pacman |defaultdesktops=No Desktop |usagetype=placeholder |architectures=x86_64, Rpi4, Rpi5 |website=[https://batocera.org/ batocera.org] }} Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pi's and other micro computers. Batocera offers emulation cores for retro consoles and retro home computers. 5e7b9cb24fa00bea866193462c4ca6e5ed81eefd 0 712 2715 2025-07-12T13:51:15Z Atmois 13 Create redirect wikitext text/x-wiki #REDIRECT [[Atl.wiki:About]] da276aa52103045fe77ceb411698a912e64a9348 2717 2715 2025-07-12T15:44:30Z Atmois 13 Update redirect wikitext text/x-wiki #REDIRECT [[ATL:About]] e2f313d8318943e7ed05627d2fe316b0cdff90a7 4 340 2716 2703 2025-07-12T14:14:43Z Atmois 13 Create links/redirect guidelines wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[Atl.wiki:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[Atl.wiki:About#Wiki Staff|admin]]. == Standards == Other things to keep in mind when making edits include: * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 |Use of comma within a year |} == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] for our own needs and refined to what is seen to be fit by the team.'' [[Category:Meta]] 1e0111a49677f1e2044db1ef160be9a28a48f108 2750 2716 2025-07-14T21:03:53Z Atmois 13 create protected pages section wikitext text/x-wiki == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[Atl.wiki:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[Atl.wiki:About#Wiki Staff|admin]]. == Standards == Other things to keep in mind when making edits include: * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == ... == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] for our own needs and refined to what is seen to be fit by the team.'' [[Category:Meta]] 6e257af211aa485a67e7521220fb5ae0dbfaa264 0 711 2718 2704 2025-07-12T15:44:48Z Atmois 13 Update redirect wikitext text/x-wiki #REDIRECT [[ATL:Guidelines#Citations]] d560f30b092feca28efa65787df6f17b44ea8014 0 543 2719 1800 2025-07-12T15:45:03Z Atmois 13 Update redirect wikitext text/x-wiki #REDIRECT [[ATL:Code of Conduct]] 0079bf599db4c1f18569780fabbf61d2bcda4637 0 540 2720 2098 2025-07-12T15:45:19Z Atmois 13 Update redirect wikitext text/x-wiki #REDIRECT [[ATL:Contributing]] 7990cc6638acd3cbaf63dcbbbd8913bad4f5785f 0 621 2721 2238 2025-07-12T15:45:33Z Atmois 13 Update redirect wikitext text/x-wiki #REDIRECT [[ATL:Guidelines]] 994392746895b76d9751899e3ca8673f9a148174 0 594 2723 2239 2025-07-12T15:45:59Z Atmois 13 Update redirect wikitext text/x-wiki #REDIRECT [[ATL:Guidelines]] 994392746895b76d9751899e3ca8673f9a148174 4 542 2724 1798 2025-07-12T15:46:19Z Atmois 13 Update redirect wikitext text/x-wiki #REDIRECT [[ATL:Disclaimer]] c2012baa108140f488865086442aa041511deaa0 10 483 2726 2240 2025-07-13T10:46:31Z Atmois 13 Change link wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[ATL:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /> <includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]] }} </includeonly> <noinclude> {{/doc}}</noinclude> 9a9db625187f2c98592fb92a406cafa9421bc52d 10 494 2727 2241 2025-07-13T10:46:54Z Atmois 13 Change link wikitext text/x-wiki This template should be placed on pages which might not meet the wiki's [[ATL:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Biased Tone", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance Templates]]</includeonly> 2cdd88619099b974f1bca951a6029334574ffad6 10 513 2728 2242 2025-07-13T10:47:26Z Atmois 13 Change link wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This template is to be used on pages which may lack credible citations, as per our [[ATL:Guidelines#Citations|citations guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Needs_Citations|| [[Category:Needs_Citations]] }} </includeonly> <noinclude> {{/doc}}</noinclude> d5e1de62687cd582b2d0b2d77cacf43d9c3fbd93 10 514 2729 2243 2025-07-13T10:47:41Z Atmois 13 Change link wikitext text/x-wiki This template should be placed on pages which may lack credible citations, as per our [[ATL:Guidelines#Citations|citations policy]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations. == Usage == <code>{{tlx|Needs Citations}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> e388826549d40e7af002744cad384106e739fd62 10 482 2730 2559 2025-07-13T10:48:02Z Atmois 13 Change link wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section lists commands or instructions which could potentially damage your system. Please ensure you understand the commands or instructions you are running or following before you run or follow them.</span> <div class="mbox-text">This warning exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[ATL:Contact|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 8d505407cdcb0e0220faa9f5022ebda8e816c71b 10 521 2731 1902 2025-07-13T10:48:16Z Atmois 13 Change link wikitext text/x-wiki This warning is placed on any page that lists a command and gives users instructions to follow, it exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[ATL:Contact|administrator]] immediately. == Usage == <code>{{tlx|Guide_Warning}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> e72c02efe78a8c2c8327363c060e2c0699ae66bb 10 523 2732 2244 2025-07-13T11:05:23Z Atmois 13 Fix link wikitext text/x-wiki <div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This template means the author of a page is still actively working on the page, and this serves to notify other editors to check with them before potentially creating conflicting changes and to notify the staff that it may not meet the wiki's [[ATL:Guidelines|guidelines]] yet.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 1273164a779234e4bc02d79d9bd326f68be7d086 10 524 2733 2245 2025-07-13T11:05:36Z Atmois 13 Fix link wikitext text/x-wiki This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes and to notify the staff that it may not meet the [[ATL:Guidelines|contributing standards]] yet. == Usage == <code>{{tlx|Work_In_Progress}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> ee585853065eba467dc49a8a24edb7a398d5d92b 2 3 2734 2690 2025-07-13T16:51:43Z Amadaluzia 52 Removed Signal, as I don't have multiple phones and am using it under something diff now wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <vector> #include <print> // Compile with C++23 or above. This will not work otherwise. struct SocialPair { std::string service, username; }; struct AboutMe { std::string name, description; std::vector<SocialPair> socials; }; int main(void) { struct AboutMe amadaluzia { .name = "Artur Manuel", .description { "I live in the UK and the internet as a background character in many\n" "free software communities (for example: you may find me on some\n" "mailing list) but I also contribute, most notably in nixpkgs.\n" "I do have other interests, such as gym, walking and photography, as\n" "well as speedrunning, filming and revising for english/maths among\n" "other things.\n" }, .socials { {"XMPP", "amadaluzia@xmpp.earth"}, {"Email", "amad@atl.tools"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Libera.Chat", "amadaluzia"}, {"Discord", "amadaluzia"}, }, }; std::println("Hello, I am {}.", amadaluzia.name); std::println("{}", amadaluzia.description); std::println("You may find me on the following platforms:"); for (auto const &[service, username] : amadaluzia.socials) std::println("{} on {}", username, service); return 0; }</syntaxhighlight> 179d0b2ed981ea3d9ef5eb5a1a9602d74072cde4 0 1 2735 2529 2025-07-13T18:38:51Z Atmois 13 Update links wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. You may also link your '''atl.wiki''' account to your discord account, following [[ATL:Discord Linking|these instructions]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[ATL:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Our Key Values ====== We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed on our [[ATL:Contact|Contact]] page. [[File:Atl.wiki CTA.png|center|frameless|960x960px]] __NOTOC__ 47d928c4767ecaa7eb164b3891bee06c71488d1a 4 556 2736 2694 2025-07-13T18:39:44Z Atmois 13 Update links wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[ATL:Contact|contact page]]! == Important Links == * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[ATL:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin == History == ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the [https://discord.gg/linux All Things Linux discord]. [[User:Electron271|Electron271]], Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, [[User:Kaizen|Kaizen]]. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spambots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also reimplemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[Special:Favoritelist|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to relicence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another relicencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[ATL:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== The Future ===== Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] e8145a9f7d77485a61971a6026d7418334e72564 4 593 2737 2642 2025-07-13T18:40:11Z Atmois 13 Update links wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[ATL:About|about]] page! Some important pages are also listed below: * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[ATL:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share or send you any kind of spam or promotional emails. Once you create an account, you can get started editing! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[ATL:Copyrights|CC-BY-SA]] to match our wiki content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. To contribute to them, either by submitting improvements or creating new ones, please contact an administrator for more details. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[ATL:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[Guidelines#Standards|standards]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[ATL:Contact|Contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === * The [[Window Management System]] definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. * The [[Linux Distributions|Linux Distribution]] article which lists distros is lacking a lot of major distros and each section should have a short blurb and information about key facts about what distros under that group typically are (e.g. release cycle, package manager, etc) * The [[Package Manager]] page, which lists package managers, needs to be rewritten to compare and delve more into each package manager. * The [[Key Terms]] page needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table potentially * The [[Desktop Environments]] page needs to be written, it needs to contain basics around DE's and what they are and a list of DE's with a short blurb to each one and potentially key distros that offer them, a table could be used to list them. * The [[X Window Manager]] page, which lists WM's depending on the type, needs to be cleaned up to remove Wayland Compositors and each WM should have a short blurb to it and potentially key distros that offer them, a table could be used to list them. * [[External Resources]] requires a clean-up to be organised and categorised properly, could make use of wiki tables with a short blurb for all websites listed. * [[Common Issues and Troubleshooting]] needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 06d1f074d61d5842a5b6b6df33de1e4742695f98 2747 2737 2025-07-14T20:44:16Z Atmois 13 Cleanup the page wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[ATL:About|about]] page! Some important pages are also listed below: * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[ATL:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[ATL:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[ATL:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[ATL:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[ATL:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distros, it lacks a lot of major distros and each section should have a short blurb and information about key facts about what distros under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists WM's depending on the type, needs to be cleaned up to remove Wayland Compositors and each WM should have a short blurb to it and potentially key distros that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 1f7dad61e217cb8cceafdb4fe5071b65e47a84f4 2748 2747 2025-07-14T20:46:02Z Atmois 13 Typo fix wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[ATL:About|about]] page! Some important pages are also listed below: * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[ATL:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[ATL:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[ATL:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[ATL:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[ATL:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distros, it lacks a lot of major distros and each section should have a short blurb and information about key facts about what distros under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distros that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 4b56179c5b1ca08fb6dbaa7bb3beea9df654c88f 2749 2748 2025-07-14T20:59:26Z Atmois 13 Restructure wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[ATL:About|about]] page! Some important pages are also listed below: * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[ATL:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[ATL:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[ATL:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it is notable enough to be included on the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[ATL:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[ATL:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distros, it lacks a lot of major distros and each section should have a short blurb and information about key facts about what distros under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distros that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 38861a00361e8c6405825073772828e17cb90832 3000 572 2738 2302 2025-07-13T18:40:46Z Atmois 13 Update links wikitext text/x-wiki TLDR: Ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, and all changes must be approved by staff for public viewing via ApprovedRevs. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. Guides are anything that explain to a user ''how'' to do something. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide how to harden Firefox with more privacy focused options, we expect and will maintain a higher standard of quality and safety than standard articles. This is because you are providing information to users to do things on their own hardware, which could potentially damage the systems or cause data loss. All main wiki policies apply, including but not limited to the [[ATL:Code of Conduct|Code of Conduct]] and the wiki [[ATL:Guidelines|guidelines]]. We also recommend you check out our [[ATL:Contributing|Contributing]] as well as it has a lot of important and useful information for editors. However, a special set of criteria are required, as outlined below: * All pages MUST contain the GuideWarning template at the beginning of the page. There are no exceptions to this rule, and violations of it will have the edits rejected until it has been added. You can add it using <code><nowiki>{{GuideWarning}}</nowiki></code> at the beginning of the page. {{Guide Warning}} * To prevent malicious information being distributed on atl.wiki, all changes to guides from non-moderators/ATL staff must be approved by a moderator. When you make an edit it is submitted for review automatically and will normally be reviewed within 24 hours, but if it is still pending after 48 hours feel free to contact an admin. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this, so please double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. We aim to provide unbiased and informative content to all users, your personal views, whilst valid, are not relevant here. * You are responsible for ensuring all commands you provide are functional and not dangerous, if there are risks with running a specific command ensure to clearly state them when listing the command and if it's a command dependent on specific system requirements ensure to outline the requirements or prerequisites clearly. Any dangerous commands provided will be held accountable to whomever adds them to a guide. You can see a good example of a guide here on the guide for '''[[Guides:Setting up Flathub on Fedora|Setting up Flathub on Fedora]]''' which is maintained and has been made in accordance with our guidelines and standards, dada65359fe5804a95cc71c64117b78c1793117f 0 562 2739 2065 2025-07-13T19:05:25Z Amadaluzia 52 Added more citations, and added more citations needed. Some typo fixes too. wikitext text/x-wiki {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel.<ref>[https://docs.openindiana.org/misc/openindiana/#what-is-the-openindiana-operating-system What is OpenIndiana Project?], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>https://web.archive.org/web/20100913030810/https://www.openindiana.org/</ref> It was proved timely as Oracle shut down development of OpenSolaris.<ref>[https://web.archive.org/web/20201109033546/http://sstallion.blogspot.com/2010/08/opensolaris-is-dead.html OpenSolaris is Dead.], Iconoclastic Tendencies, August 13, 2010 (Accessed: July 13, 2025)</ref> OpenIndiana uses the same tooling as Solaris; the SMF init system,<ref>[https://docs.openindiana.org/handbook/systems-administration/#service-management-facility Service Management Facility], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> FMA fault management system,<ref>[https://docs.openindiana.org/misc/openindiana/#what-features-does-openindiana-have What features does OpenIndiana have?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and IPS package manager,<ref>[https://docs.openindiana.org/handbook/systems-administration/#software-management Software management], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> The majority of the [https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/ Solaris documentation] also applies to OpenIndiana.{{Citation needed}} OpenIndiana makes use of the SunOS branch of the UNIX kernel,<ref>[https://docs.openindiana.org/misc/openindiana/#why-is-it-called-openindiana Why is it called OpenIndiana?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and thus provides all of the stability benefits of a UNIX System V derivative.{{Citation needed}} This does, however, mean that hardware support is limited in comparison to a BSD or Linux based OS.<ref>[https://docs.openindiana.org/community-hcl/getting-hardware-info/ Getting information about hardware] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> OpenIndiana uses the SunOS libc, which severely limits what software will compile on it successfully. SunOS libc only implements functions expected by POSIX and ANSI C.{{Citation needed}} [[Category:Misc Operating Systems]] [[Category:Illumos]] 048ed5664b96f959c03662bb70b17b83686c6f50 2 713 2740 2025-07-13T19:14:59Z Amadaluzia 52 Sandbox wikitext text/x-wiki = The Sandbox = You will expect to see pages that are being tampered with here. 47b4aaad545bbfbc71371f0867f344356b33ea04 6 714 2741 2025-07-13T19:18:10Z Amadaluzia 52 Drawing on a NetBSD laptop's touchscreen using a stylus, from oshimaya. https://twitter.com/oshimyja wikitext text/x-wiki == Summary == Drawing on a NetBSD laptop's touchscreen using a stylus, from oshimaya. https://twitter.com/oshimyja == Licensing == {{Unknown_copyright}} ad8e81b4feb941f47551bad37384fe9e6808eaf3 10 631 2743 2353 2025-07-14T08:46:36Z Atmois 13 Tidy up formatting wikitext text/x-wiki <includeonly>{{#tag:ref|{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}})}}</includeonly><noinclude><templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata></noinclude> 69eefeb4bcc7b79e56680513617e7bee78f33f95 4 327 2744 2701 2025-07-14T08:46:47Z Atmois 13 cite test wikitext text/x-wiki test statment{{Cite|url=https://atl.wiki|title=ATL Wiki|author=Editors|year=2025}} =References= <references /> 8c05a220b5fc758fb77212630dfaca92a1f98220 0 716 2751 2025-07-14T21:32:25Z Chiyo 177 A small history and summary about Hackintosh, aswell as pointers for starting your hackintosh journey! wikitext text/x-wiki = Hackintosh = == Definition == A '''Hackintosh''' is a non‑Apple computer configured to run Apple's '''macOS''', using unofficial methods to bypass hardware restrictions. Apple’s software license restricts macOS usage to Apple‑branded machines<ref>{{Cite|title=Hackintosh|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == History == === Origins === The concept surfaced as users attempted to run Mac OS on non‑Apple hardware. It gained real momentum after Apple transitioned to Intel CPUs, making macOS compatible with x86 architecture<ref>{{Cite|title=Intel Macs usher in Hackintosh era|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === PC Installations === Following the release of Intel-based Macs in 2006, community developers modified the macOS kernel to disable hardware checks and employed EFI emulation tools like FakeEFI to boot macOS on PCs<ref>{{Cite|title=Hackintosh bootloaders|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === Bootloader Evolution === Bootloaders such as Chameleon and Clover evolved to improve reliability. In 2019, '''OpenCore''' was introduced, offering advanced features like support for macOS security features including System Integrity Protection and FileVault<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === Legal Developments === In 2008, Apple sued Psystar for selling unauthorized macOS clones. The court ruled Psystar violated Apple copyright and the DMCA, underscoring Apple’s legal restrictions<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == Technical and Legal Status == Apple’s EULA prohibits running macOS on non‑Apple hardware<ref>{{Cite|title=Hackintosh licensing|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. The DMCA’s anti‑circumvention provisions create legal uncertainty in the U.S.<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. Apple’s transition to ARM-based silicon (beginning in 2020) reduces future feasibility for x86 Hackintoshes<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref>. == Hardware Compatibility == According to the '''Dortania OpenCore Install Guide''': CPUs: modern Intel (up to Comet Lake) and patched AMD Ryzen series GPUs: Intel integrated graphics (Ivy Bridge to Ice Lake), AMD GCN/Vega/Navi; NVIDIA support is limited Networking: Broadcom-based Wi‑Fi and Ethernet adapters are preferred<ref>{{Cite|title=OpenCore hardware limits|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref> == Installation Guide == This guide provides a high-level overview. For full instructions, consult the [[OpenCore Install Guide]]. === 1. Prepare hardware === Confirm that your CPU, GPU, and network adapters match published compatibility lists. === 2. Obtain macOS installer === On a real Mac, download the desired macOS version (such as Sonoma or Sequoia) from the App Store. === 3. Build a USB installer === Partition a USB drive as HFS+ or APFS and use '''OpenCore''' along with official tools to create a bootable installer<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 4. Configure BIOS/UEFI === Disable Secure Boot, VT-d, CSM, Fast Boot. Enable UEFI and XHCI handoff<ref>{{Cite|title=OpenCore BIOS settings|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 5. Boot and install macOS === Boot from the USB installer, format the target storage as APFS, then proceed with the installation. === 6. Post-install configuration === Migrate the USB EFI folder to the internal EFI partition. Install necessary kexts (for audio, network), configure USB mapping, and finalize settings such as NVRAM, FileVault, and Sleep/Wake. == Resources == [https://dortania.github.io/OpenCore-Install-Guide/ Dortania OpenCore Install Guide] – full tutorial [https://en.wikipedia.org/wiki/Hackintosh Hackintosh – Wikipedia] [https://tonymacx86.com/ tonymacx86 forums] – hardware build guides and buyer lists == See also == [[macOS]] [[Virtualization]] [[BIOS]] == References == <references/> 34550a6ea5a204eb719557336563b2a465bff7f7 6 717 2752 2025-07-14T21:49:36Z Chiyo 177 wikitext text/x-wiki apple logo 97601fdb867b6cc8b5409a27a2f34214fc1eacce 0 718 2753 2025-07-14T21:50:36Z Chiyo 177 MacOS history aswell as general information wikitext text/x-wiki = macOS = [[File:Apple-Logo-Transparent.png|thumb|right]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical operating systems developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a UNIX (Darwin/BSD) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> 1ca85b2e8385523e04887983a996f645176e3d75 6 719 2754 2025-07-14T23:50:12Z Chiyo 177 wikitext text/x-wiki A photo of Zen, modeled by Chiyo! e9dbec1c00965ec495a897f59a360a4e2554b66d 2 721 2756 2025-07-15T00:09:18Z Chiyo 177 made basic page wikitext text/x-wiki HI IM CHIYO LUL IM SUPER ACTIVE IN ATL PLS COME LOOK AT MY CONTRIBS <3 EXPECT MORE FROM HERE XOXO 21f6bec3b3a09de5b1d2138934e09bde7882945f 2 722 2757 2025-07-15T02:20:19Z Ow0cast 249 go away!!!!!!!!! css text/css #p-coll-print_export, #footer-info-copyright, #footer-places, #footer-icons, #pt-prefswitch-link-on, #pt-prefswitch-link-anon, #editpage-copywarn, #editpage-copywarn2, #mw-history-searchform, #siteSub, #t-print, #n-contents, #t-specialpages, #feedlinks, .editpage-head-copywarn { display: none } a { text-decoration: none; } 005de5c30ae285b96c67a05d01a458b16111153e 0 166 2758 2441 2025-07-15T02:35:49Z Ow0cast 249 cleanup | spaces around refs wikitext text/x-wiki A term commonly used across any Linux community,<ref>[https://www.youtube.com/watch?v=LxuYnFD7brY TechOverTea] imported on 17th June 2025</ref> "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life.<ref>Merriam-Webster Dictionary. [https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of [[Linux]] and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system.<ref>[https://www.techtarget.com/searchsecurity/answer/How-can-we-detect-and-uninstall-bloatware "What is Bloatware?"] TechTarget.com ,Imported 17th June 2025</ref> <references /> [[Category:Terminology]] 81224d2e1768ded47471e509b14b887391202f7c 0 418 2759 2626 2025-07-15T02:51:04Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki {{DistributionInfobox|architectures=arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox|caption=The FreeBSD logo|defaultdesktops=[[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]]|image=[[File:FreeBSD logo.png|200px|FreeBSD_logo]]|packagemanager=[[pkg]]|releasemodel=Stable|releasestatus=Maintained|title=FreeBSD|usagetype=Desktop, Firewall, Raspberry Pi, Server|website=[https://freebsd.org freebsd.org]}} FreeBSD is a [[UNIX|Unix]] [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released on November 1993.<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"] [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref> [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[Drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a [[kernel]] and [[drivers]], and relying on third-parties such as [[GNU]] for system [[:Category:Software|software]].<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref> The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports.<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref> The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']}<references /> [[Category:Misc Operating Systems]] [[Category:BSD]] a63d1b295116f10c7a548b2d25c2b1a7bc1ed391 0 586 2760 2469 2025-07-15T02:53:52Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki {{MascotInfobox | title = Xenia (Linux Fox) | image = [[File:Xenia the Linux Fox.gif]] | caption = The original design of Linux Fox, created by Al Mackey in 1996 }} Xenia was a candidate logo and [[:Category:Mascots|mascot]] for the [[Linux]] project. She was a competitor to [[Tux]], who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds)<ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ Why the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!], Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson.<ref>[https://archive.is/wYsFh Penguins and Other Things], Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on [[Gentoo]].<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> <references /> [[Category:Mascots]] ecc7c4a11fd6ff283aa3bd70859e4520ccde3748 0 650 2761 2475 2025-07-15T02:55:30Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki {{SoftwareInfobox | image=[[File:Enlightenment logo.svg|Enlightenment_logo]] | caption = Enlightenment logo | title=Enlightenment | releasestatus=Maintained | lastrelease=0.27.1, March 17, 2025 | firstrelease=0.13.2, January 18, 1998 | languages=[[C]], [[ELF]] | developers=Enlightenment Foundation | website=[https://www.enlightenment.org/, enlightenment.org/] }} [https://www.enlightenment.org/ Enlightenment] is a [[Desktop Environments|Desktop Environment]] and [[Window Manager]] for [[Linux]] and other [[Unix|Unix-like]] [[Operating System|operating systems]], such as [[BSD]] derivatives.<ref name=":0">[https://www.enlightenment.org/about Enlightenment About Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref>. Originally created by Carsten Haitzler in the late 90s with the philosophy "that users should be given as much control as possible."<ref>[https://www.enlightenment.org/about-enlightenment| About Enlightenment Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref> === Features === Enlightenment has many key features as a [[graphical desktop]] including its own set of graphical and system libraries known as the "Enlightenment Foundation Libraries". Designed to be portable and efficient while also being easy to use on various devices including touch devices even being used in Samsung devices.<ref name=":0" /> * Support for both [https://www.x.org/wiki/ X11] and experimental [https://wayland.freedesktop.org/ Wayland] support. * A hand optimized software rendering compositor. * Very low memory requirements. * The ability to configure everything graphically. * Touch gestures * Window Management Features ** Virtual desktops. ** Optional window tiling. ** Customizable mouse and keyboard bindings. ** And many more modules. <references /> [[Category:Desktop Environments]] 620ec691c6d645bb0ca982da87b65b36fedccfdc 0 668 2762 2662 2025-07-15T02:58:22Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''.’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref> == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor [[ed]] (1971) and the even earlier [[qed]] (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command.<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref> sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; …} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to [[EOF]]. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10-15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] ad1f3c6dd6fdd50ce907ecaf4db8c754e512d837 0 441 2763 2507 2025-07-15T03:03:02Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,")<ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU], The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> is a dedicated organization for free [[:Category:Software|software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone [[Operating System|operating system]] because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or [[Proprietary software|proprietary]]: A few are GNU/[[Linux]], [[MacOS]], [[UNIX|Unix-based]]/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the [[proprietary software]] of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe. </ref> == Included Software / Components == [[File:Gnu compiler collection-logo-1.png|alt=This logo depicts a Bull shaped animal jumping out of an egg, in black text that displays the letters G, C, C|left|thumb|224x224px|A logo of the GCC.]] As of June 2024, the GNU project currently holds 394 active [[packages]], but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. Overall, these components are in many operating systems, mainly because of how easy GCC is to access for any developer. Because of Richard Stallman, he was able to open source the variety of tools and software developed for the GNU project and in turn, pushed forward for the movement of open and free software for all.<ref name=":0" /> == History of GNU == [[File:RichardStallman.jpg|alt=A Picture of Richard Matthew Stallman in 2024|thumb|341x341px|A Picture of Richard Matthew Stallman in 2024]] Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref name=":0">[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible [[architecture]] because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs.<ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> <references /> 0cc2091e3cb160f8736e52e71e34cfb5005456fd 0 214 2764 2084 2025-07-15T03:05:30Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Tux | image = [[File:Tux.svg|Tux|thumb]] | caption = Tux! }} '''Tux''' is the official mascot of [[Linux]], designed by Larry Ewing.<ref>https://web.archive.org/web/20040401161253/http://www.linux.org/info/logos.html</ref> Tux was created for the Linux 2.0 logo competition.<ref>https://web.archive.org/web/20040407092622/http://www.cs.earlham.edu/~jeremiah/linux-pix/linux-logo.html</ref><references /> [[Category:Mascots]] b549d6a0f9b025e640f69c4a996389cfa691b145 6 723 2765 2025-07-15T04:55:57Z Chiyo 177 wikitext text/x-wiki uwuzen lmfao 044b3c31f6d1151215586d21dc62355c57daf1be 6 724 2766 2025-07-15T04:56:58Z Chiyo 177 wikitext text/x-wiki kaizen chan! 8fa36b23809bb0fe963d76ffd97a0f9976a8575e 828 609 2768 2206 2025-07-15T10:37:18Z Atmois 13 Change to use wikilinks Scribunto text/plain local p = {} function p.stats() local siteStats = mw.site.stats local totalEdits = siteStats.edits local totalUsers = siteStats.users local function countPages(ns) return siteStats.pagesInNamespace(ns) or 0 end local pageCount = countPages(0) + countPages(3000) return string.format( "atl.wiki has [ATL:AllPages %d pages] consisting of [Special:RecentChanges %d edits] from [Special:ListUsers %d users]!", pageCount, totalEdits, totalUsers ) end return p c90c6f99e7f6344cad81c4d277c28c990870add8 2769 2768 2025-07-15T10:37:49Z Atmois 13 Actually use wikilinks Scribunto text/plain local p = {} function p.stats() local siteStats = mw.site.stats local totalEdits = siteStats.edits local totalUsers = siteStats.users local function countPages(ns) return siteStats.pagesInNamespace(ns) or 0 end local pageCount = countPages(0) + countPages(3000) return string.format( "atl.wiki has [[ATL:AllPages %d pages]] consisting of [[Special:RecentChanges %d edits]] from [[Special:ListUsers %d users]]!", pageCount, totalEdits, totalUsers ) end return p 7209745ba6f3fd6e4a82cc4eeb2892a34c817983 2770 2769 2025-07-15T10:38:17Z Atmois 13 Fix formatting Scribunto text/plain local p = {} function p.stats() local siteStats = mw.site.stats local totalEdits = siteStats.edits local totalUsers = siteStats.users local function countPages(ns) return siteStats.pagesInNamespace(ns) or 0 end local pageCount = countPages(0) + countPages(3000) return string.format( "atl.wiki has [[ATL:AllPages| %d pages]] consisting of [[Special:RecentChanges| %d edits]] from [[Special:ListUsers| %d users]]!", pageCount, totalEdits, totalUsers ) end return p 5b7e95c92d49cf5173d867782da96c99762d50d5 2 722 2772 2757 2025-07-15T14:18:28Z Ow0cast 249 maybe css text/css #p-coll-print_export, #footer-info-copyright, #footer-places, #footer-icons, #pt-prefswitch-link-on, #pt-prefswitch-link-anon, #editpage-copywarn, #editpage-copywarn2, #mw-history-searchform, #siteSub, #t-print, #n-contents, #t-specialpages, #feedlinks, .editpage-head-copywarn { display: none } a span { text-decoration: none; } 7d4f7c1f4cf3a16ca62bd17bc4d80503bc5166e8 3000 573 2773 2234 2025-07-17T01:46:25Z Ow0cast 249 wikitext text/x-wiki {{Guide Warning}} [[Flathub]] is a third party [[repository]] of applications that are packaged in the [[Flatpak]] format. By default, [[Fedora]] does not include the Flathub repository<ref>[https://developer.fedoraproject.org/deployment/flatpak/flatpak-usage.html Flatpak Usage On Fedora], Felipe Borges, Jarek Prokop, John Atti, Nick Dirschel, Pavel Valena, 2018 (Retrieved 22nd March 2025)</ref>. Some Flathub apps are also in the main Fedora repositories, but in some cases it ships newer versions or applications that aren’t available in the Fedora repositories.<ref>[https://fedoramagazine.org/install-flathub-apps-fedora/ Installing Flathub Apps on Fedora], Ryan Lerch, 2018 (Retrieved 22nd March 2025)</ref> You can set up Flathub graphically via the repository file, GNOME Software or KDE Discover. Alternately, you can set it up through the command line. The recommended method is via the Flathub repository file or the terminal: ====== Installing Flathub via the Flathub Repository File (Recommended) ====== [[File:GNOMESoftwareFlathubFile.png|thumb|GNOME Software GUI when Flathub Repo File has been opened via File Manager]] # Visit [https://flathub.org/setup/Fedora flathub.org/setup/Fedora] and select the text saying <code>Flathub Repository File</code> to download <code>flathub.flatpakrepo</code>. # Open your file manager and double-click the <code>flathub.flatpakrepo</code> file. It will open KDE Discover or GNOME software. # Select the <code>Install</code> button, you may need to log out and log back in to Fedora for Flathub apps to appear. ====== Installing Flathub via GNOME Software ====== [[File:SoftwareReposGNOMESoftware.png|thumb|Image of Flathub being enabled in GNOME Software.]] # Open GNOME software and select the hamburger menu on the top right of the application and select <code>Software Respositories</code>. You can also use the key bind <code>RightCtrl + .</code> to open the menu. # Scroll down and enable the toggle for <code>Flathub</code> and the toggle for <code>Enable New Repositories</code>. # You may need to log out and log back into Fedora or run <code>gnome-software --quit</code> in your terminal for Flathub apps to appear in GNOME software. ====== Installing Flathub via the KDE Discover ====== [[File:DiscoverKDEFlathubRepo.png|thumb|328x328px|How the Flatpak section should look after finishing on KDE Discover]] # Open KDE discover and open the settings menu on the left of your screen. # Select the <code>Flathub - ''dl.flathub.org''</code> option. # Click the up arrow until Flathub is at the top of the list to make it the primary source, then click apply changes at the top of KDE Discover. # You may need to log out and log back into Fedora for Flathub apps to appear in KDE Discover. ====== Installing Flathub via the Command Line ====== # Open your terminal of choice. # Run the command <code>flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki></code>. # You may need to log out and log back into Fedora for Flathub apps to appear in GNOME software or KDE Discover. <references /> 0ee64d922f5f0d75764115175cf0c0afa6de7d3c 2774 2773 2025-07-17T01:47:23Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] (same with last revision) wikitext text/x-wiki {{Guide Warning}} [[Flathub]] is a third party [[repository]] of applications that are packaged in the [[Flatpak]] format. By default, [[Fedora]] does not include the Flathub repository.<ref>[https://developer.fedoraproject.org/deployment/flatpak/flatpak-usage.html Flatpak Usage On Fedora], Felipe Borges, Jarek Prokop, John Atti, Nick Dirschel, Pavel Valena, 2018 (Retrieved 22nd March 2025)</ref> Some Flathub apps are also in the main Fedora repositories, but in some cases it ships newer versions or applications that aren’t available in the Fedora repositories.<ref>[https://fedoramagazine.org/install-flathub-apps-fedora/ Installing Flathub Apps on Fedora], Ryan Lerch, 2018 (Retrieved 22nd March 2025)</ref> You can set up Flathub graphically via the repository file, GNOME Software or KDE Discover. Alternately, you can set it up through the command line. The recommended method is via the Flathub repository file or the terminal: ====== Installing Flathub via the Flathub Repository File (Recommended) ====== [[File:GNOMESoftwareFlathubFile.png|thumb|GNOME Software GUI when Flathub Repo File has been opened via File Manager]] # Visit [https://flathub.org/setup/Fedora flathub.org/setup/Fedora] and select the text saying <code>Flathub Repository File</code> to download <code>flathub.flatpakrepo</code>. # Open your file manager and double-click the <code>flathub.flatpakrepo</code> file. It will open KDE Discover or GNOME software. # Select the <code>Install</code> button, you may need to log out and log back in to Fedora for Flathub apps to appear. ====== Installing Flathub via GNOME Software ====== [[File:SoftwareReposGNOMESoftware.png|thumb|Image of Flathub being enabled in GNOME Software.]] # Open GNOME software and select the hamburger menu on the top right of the application and select <code>Software Respositories</code>. You can also use the key bind <code>RightCtrl + .</code> to open the menu. # Scroll down and enable the toggle for <code>Flathub</code> and the toggle for <code>Enable New Repositories</code>. # You may need to log out and log back into Fedora or run <code>gnome-software --quit</code> in your terminal for Flathub apps to appear in GNOME software. ====== Installing Flathub via the KDE Discover ====== [[File:DiscoverKDEFlathubRepo.png|thumb|328x328px|How the Flatpak section should look after finishing on KDE Discover]] # Open KDE discover and open the settings menu on the left of your screen. # Select the <code>Flathub - ''dl.flathub.org''</code> option. # Click the up arrow until Flathub is at the top of the list to make it the primary source, then click apply changes at the top of KDE Discover. # You may need to log out and log back into Fedora for Flathub apps to appear in KDE Discover. ====== Installing Flathub via the Command Line ====== # Open your terminal of choice. # Run the command <code>flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki></code>. # You may need to log out and log back into Fedora for Flathub apps to appear in GNOME software or KDE Discover. <references /> 2b4ea6b9bdd02ac895240da670932a2be13be6e4 2 427 2775 1471 2025-07-17T02:03:53Z Ow0cast 249 wikitext text/x-wiki ==<nowiki>:</nowiki>3== see [[wikipedia:User:Ow0cast|my wikipedia userpage]] 8758f23e525f3459a1a70f4dd42bc5715a686c65 0 219 2776 2612 2025-07-17T02:08:33Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki {{MascotInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan.<ref>https://community.kde.org/Promo/Material/Mascots Official KDE Wiki, 2025 (Imported 6th June 2024)</ref> Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror], KDE's default web browser.<ref>https://community.kde.org/Konqi Official KDE Wiki, 2025 (Imported 6th June 2024)</ref><references /> [[Category:Mascots]] 4cdc597e9d36c305c56921a866a725c6eafe1de3 0 428 2777 2674 2025-07-17T02:10:59Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] | this one did it right but put spaces before the cites so its wrong wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' (short for ''manual'') is a [[TUI|command-line]] utility available on [[UNIX]] and UNIX-like [[Operating System|operating systems]] that provides documentation for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a man page the user can enter the following into their [[TUI|terminal]]:<ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> man ''<command_name>'' For example, to read the manual for <code>man</code> command itself: man man == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER<code> environment variable. By default, it uses <code>less<code>. Alternatively, the </code>-P</code> or </code>--pager</code> option can be used.<ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally.<ref>https://fishshell.com/docs/current/faq.html</ref> <references /> 5e9a4acbf49d7828930300d41b1847671b572a5e 0 653 2778 2481 2025-07-17T02:13:08Z Ow0cast 249 tagging | needs cites wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox|title=Pop!_OS|image=[[File:Pop! OS Icon.svg|frameless]]|caption=The Pop!_OS logo|releasestatus=Maintained|packagemanager=[[Pacman]]|defaultdesktops=COSMIC|usagetype=Desktop|architectures=x86_64|website=Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX]|releasemodel=Rolling release}}Pop!_OS is a free and open-sourced [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]], based on [[GNOME]], called [[COSMIC]]. Pop!OS is developed by American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. === <u>Features</u> === * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle baa8d370386f5739ea2bac1caeb6dab5c14e76f5 0 709 2779 2697 2025-07-17T02:14:33Z Ow0cast 249 cleanup | spaces around refs wikitext text/x-wiki This article describes the general boot process of most Linux distributions.<ref>https://medium.com/@gangulysutapa96/6-stages-of-linux-boot-process-5ee84265d8a0 Medium.com, 2023 (Imported 02.07.25)</ref> While most Linux distributions integrates varying components, the basic steps remain the same. === BIOS === The BIOS (Basic Input/Output System) is the firmware that initializes hardware components and provides a basic set of services to the kernel.<ref>https://www.lenovo.com/gb/en/glossary/what-is-a-bios?srsltid=AfmBOopXGO9x6E-4ZTe5WNDbGEMlTYXBLk1ivYj5LXSQC8OTUAjEAASC Lenovo.com, 2025 (Imported 02.07.2025)</ref> It is obtained from the ROM and is responsible for loading the bootloader. Once the correct boot device is selected, the BIOS loads the boot sector, which is the first sector (512 bytes) of the boot device.<ref>https://neosmart.net/wiki/mbr-boot-process/ Neosmart.net, 2025 (Imported 02.07.2025)</ref> The boot sector contains the bootloader, which is responsible for loading the [[kernel]]. === Bootloader === The bootloader is responsible for loading the kernel into memory and starting the kernel. Common bootloaders include [[GRUB]], [[Syslinux]], [[Limine]], [[Systemd|systemd-boot]], [[rEFInd]], etc. Usually, the bootloader is stored separately from the kernel, in different [[partition]]s or even on a different device. It displays an interface, such as a text-based menu to select the kernel to boot. === Initramfs === The initramfs is a compressed filesystem that is loaded into memory during boot. It contains essential files and utilities required to mount the actual root [[filesystem]] and start the init process. The initramfs is typically created using [[mkinitcpio]] or [[dracut]]. === Kernel === The kernel is the core of the operating system and is responsible for managing hardware resources and providing a platform for user-space applications. It is responsible for initializing hardware, managing memory, and providing a virtual filesystem. It is loaded by the bootloader and starts the init process. === Init === The init process, which must be stored under <code>/sbin/init</code>, is responsible for initializing the system and starting the user-space applications. It is responsible for mounting the root filesystem, starting the necessary system services, and starting the graphical user interface. On most modern systems, this is [[systemd]]. Some older systems use [[sysvinit]] or [[upstart]]. === TTY === The [[TTY]] (Teletype) is a text-based interface that allows users to interact with the operating system. It is responsible for displaying text and accepting user input. It is typically used for logging in and running commands. It is also used for debugging and troubleshooting. The TTY is available even on modern systems and can be accessed through the {{Key press|Ctrl|Alt|F1}} to {{Key press|Ctrl|Alt|F6}} keys. === Display Manager === The [[Display Manager|display manager]] is responsible for managing the [[GUI|graphical user interface]].<ref>https://wiki.archlinux.org/title/Display_manager Arch wiki, 2025 (Imported 02.07.2025)</ref> On most modern systems, this is [[lightdm]], [[gdm]], or [[sddm]]. Once the user logs in, the display manager executes the [[Window Manager|window manager]] or [[Desktop Environments|desktop environment]] chosen by the user. da55b11478c336628fa18581c828b56546c34d68 0 297 2780 2430 2025-07-17T02:26:23Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref> The core concept of multi-booting revolves around partitioning a computer’s [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Valorant's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats.<references /> [[Category:Terminology]] 3c01bb5226c4acef6d44ae09493f69bbd62108f3 0 726 2781 2025-07-17T02:29:34Z Ow0cast 249 redir | man -> manpages wikitext text/x-wiki #REDIRECT [[manpages]] dbd941515ff1754794608ca23ce32cc0c6b22716 0 727 2782 2025-07-17T02:31:15Z Ow0cast 249 redir | system call -> syscalls wikitext text/x-wiki #REDIRECT [[Syscalls]] 8e129b41374ab6567708c2dac7915e0da94ccb98 0 1 2783 2735 2025-07-19T15:38:11Z Atmois 13 Update links wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. You may also link your '''atl.wiki''' account to your discord account, following [[ATL:Discord Linking|these instructions]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[ATL:Contributing|Contributing]] Guide. It's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[ATL:Guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Our Key Values ====== We have 5 key values for '''atl.wiki''', these summarise all of our [[ATL:Guidelines]] well: # Accuracy: Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed on our [[ATL:Contact|Contact]] page. [[File:Atl.wiki CTA.png|center|frameless|960x960px]] __NOTOC__ ecc5b853a4fd8a2ea6c88186813f120e0484c734 2788 2783 2025-07-19T19:03:46Z Atmois 13 Fix link masking wikitext text/x-wiki <center> {{Main Page/Header}} <hr> {{Navpills |page1 = Desktop Environments |image1 = Dewms.png |page2 = Window Management System |image2 = Dewms.png |text3 = Guides |page3 = Guides:Guides |image3 = Guides.png |page4 = Linux Distributions |image4 = Distributions.png |page5 = Mascots |image5 = Mascots.png |page6 = Meta |image6 = MetaATL.png |page7 = Misc Operating Systems |image7 = MiscATL.png |page8 = Package Managers |image8 = SoftwareATL.png |page9 = Software |image9 = SoftwareATL.png |page10 = Terminology |image10 = TerminologyATL.png |page11 = Pages Needing Cleanup |image11 = MetaATL.png |text12 = Pages Needing Citations |page12 = Needs Citations |image12 = MetaATL.png }} </center> == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. You may also link your '''atl.wiki''' account to your discord account, following [[ATL:Discord Linking|these instructions]]. == Getting Started on the Wiki == '''Don't be afraid to edit''' – ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content (Citing claims with references), uploading free use images, correct spelling and grammar mistakes or improve prose to make articles more readable! The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. You just need to use common sense as you edit, and if you accidentally make a mistake, another editor can always help to fix or improve it later. So go and edit an article and help make '''atl.wiki''' a better source of information! If you are interested in writing guides or instructional articles for the wiki, check out [[Guides:Contributing]]. We do this to allow us to easier manage content as well as have a higher standard of content to prevent damage to user devices through our [[Main Page#Moderation|moderation]] system. ====== Places to Start ====== * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]]. These pages contain many useful guidelines if you're unsure of something. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] which contain comprehensive information for editors. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * The [[Special:RecentChanges|recent changes]] page shows a feed of recent edits to the wiki. Use it to look for pages which may need improvement. * Check out [[Special:WantedPages]] for the most linked-to pages which do not exist. ====== Our Key Values ====== We have 5 key values for '''atl.wiki''', these summarise all of our [[ATL:Guidelines|guidelines]] well: # Accuracy: Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. ====== Moderation ====== Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed on our [[ATL:Contact|Contact]] page. [[File:Atl.wiki CTA.png|center|frameless|960x960px]] __NOTOC__ 3db97a3b6df5840b60483e865795e0ccf45ed4fa 5 728 2784 2025-07-19T15:54:00Z Atmois 13 /* Guidelines talk page */ new section wikitext text/x-wiki == Guidelines talk page == You can discuss or propose changes to the guidelines page below. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 15:54, 19 July 2025 (UTC) 823de3da90dc6f4b110c546ec1db6e22289b91c2 4 340 2785 2750 2025-07-19T15:54:19Z Atmois 13 Add explain point wikitext text/x-wiki These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. To contribute or propose changes, either make a post on the [[ATL talk:Guidelines|Talk Page]] detailing the changes, contact an admin or refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]]. == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Standards == Other things to keep in mind when making edits include: * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == ... == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] for our own needs and refined to what is seen to be fit by the team.'' [[Category:Meta]] 34e95d0eae18eb2a1e6cbc290a47112072c8bbdd 2786 2785 2025-07-19T17:32:07Z Atmois 13 Add protected page guidelines wikitext text/x-wiki These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. To contribute or propose changes, either make a post on the [[ATL talk:Guidelines|Talk Page]] detailing the changes, contact an admin or refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]]. == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Standards == Other things to keep in mind when making edits include: * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammer fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] for our own needs and refined to what is seen to be fit by the team.'' [[Category:Meta]] 3f147b05ec17ed2d830b62c1c7597ba2c1fd3be3 2787 2786 2025-07-19T17:35:25Z Atmois 13 Remove broken heading wikitext text/x-wiki These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. To contribute or propose changes, either make a post on the [[ATL talk:Guidelines|Talk Page]] detailing the changes, contact an admin or refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]]. == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will autogenerate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Standards == Other things to keep in mind when making edits include: * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammer fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote><references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] for our own needs and refined to what is seen to be fit by the team.'' [[Category:Meta]] 998fb1531d39bf7125ea67d7bec19dea915b3aca 2789 2787 2025-07-19T20:51:10Z Atmois 13 add a preamble wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will auto generate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is autogenerated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid == Edit Summary == ... == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Standards == Other things to keep in mind when making edits include: * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote><references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 975a9d894b0b68d077b7d861040ddc44be88b620 2790 2789 2025-07-20T07:56:00Z Atmois 13 Write guidelines on edit summaries wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will auto generate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Standards == Other things to keep in mind when making edits include: * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote><references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 61b97fe6c9748dbf3f731210ec07d94442bc003d 0 562 2791 2739 2025-07-20T10:19:45Z Imnotgoodatnames 121 "UNIX/Unix operating system" should only be used for UNIX certified operating systems, which OI, despite being based on an OS that was UNIX certified, is not. wikitext text/x-wiki {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix-like [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel.<ref>[https://docs.openindiana.org/misc/openindiana/#what-is-the-openindiana-operating-system What is OpenIndiana Project?], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>https://web.archive.org/web/20100913030810/https://www.openindiana.org/</ref> It was proved timely as Oracle shut down development of OpenSolaris.<ref>[https://web.archive.org/web/20201109033546/http://sstallion.blogspot.com/2010/08/opensolaris-is-dead.html OpenSolaris is Dead.], Iconoclastic Tendencies, August 13, 2010 (Accessed: July 13, 2025)</ref> OpenIndiana uses the same tooling as Solaris; the SMF init system,<ref>[https://docs.openindiana.org/handbook/systems-administration/#service-management-facility Service Management Facility], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> FMA fault management system,<ref>[https://docs.openindiana.org/misc/openindiana/#what-features-does-openindiana-have What features does OpenIndiana have?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and IPS package manager,<ref>[https://docs.openindiana.org/handbook/systems-administration/#software-management Software management], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> The majority of the [https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/ Solaris documentation] also applies to OpenIndiana.{{Citation needed}} OpenIndiana makes use of the SunOS branch of the UNIX kernel,<ref>[https://docs.openindiana.org/misc/openindiana/#why-is-it-called-openindiana Why is it called OpenIndiana?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and thus provides all of the stability benefits of a UNIX System V derivative.{{Citation needed}} This does, however, mean that hardware support is limited in comparison to a BSD or Linux based OS.<ref>[https://docs.openindiana.org/community-hcl/getting-hardware-info/ Getting information about hardware] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> OpenIndiana uses the SunOS libc, which severely limits what software will compile on it successfully. SunOS libc only implements functions expected by POSIX and ANSI C.{{Citation needed}} [[Category:Misc Operating Systems]] [[Category:Illumos]] 6b08f0989d9dd8650a029553cec42f572d2510f2 0 169 2792 2431 2025-07-20T10:21:33Z Beatrixzy 179 Added references to PKG (FreeBSD's package manager) wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) [[NixOS]]'s Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in [[Alpine Linux]] and [[Debian]]. It's github repository is available [https://github.com/freebsd/pkg here] [[Category:Terminology]] 0f5b1280d720bb57e34fe322c1c71602cb026571 0 418 2793 2759 2025-07-20T10:23:44Z Imnotgoodatnames 121 "UNIX/Unix operating system" should only be used for UNIX certified operating systems, which modern BSDs, including FreeBSD, are not. wikitext text/x-wiki {{DistributionInfobox|architectures=arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox|caption=The FreeBSD logo|defaultdesktops=[[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]]|image=[[File:FreeBSD logo.png|200px|FreeBSD_logo]]|packagemanager=[[pkg]]|releasemodel=Stable|releasestatus=Maintained|title=FreeBSD|usagetype=Desktop, Firewall, Raspberry Pi, Server|website=[https://freebsd.org freebsd.org]}} FreeBSD is a [[UNIX|Unix]]-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released on November 1993.<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"] [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref> [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[Drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a [[kernel]] and [[drivers]], and relying on third-parties such as [[GNU]] for system [[:Category:Software|software]].<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref> The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports.<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref> The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']}<references /> [[Category:Misc Operating Systems]] [[Category:BSD]] a437910fd6cdfecc46a0296101595a1748ce47ce 0 299 2794 2064 2025-07-20T10:26:04Z Imnotgoodatnames 121 "Unix operating system" should only be used for UNIX certified operating systems, which modern BSDs, including OpenBSD, are not. wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a [[UNIX|Unix]]-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released on July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely-used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] d84ecc88552469ef1c49ed22c5cb1b2d1460971a 6 729 2795 2025-07-20T12:39:29Z Imnotgoodatnames 121 Ed Unix line editor wikitext text/x-wiki == Summary == Ed Unix line editor == Licensing == {{PD}} 51710f553fbfe3e5caf87f335a3814e8f029d9f8 6 730 2796 2025-07-20T12:40:30Z Imnotgoodatnames 121 Unix CLI shell enviroment wikitext text/x-wiki == Summary == Unix CLI shell enviroment == Licensing == {{PD}} 06974b3ca3926fad3180679adf7f27656a3dbbda 6 731 2797 2025-07-20T12:42:36Z Imnotgoodatnames 121 MS-DOS COMMAND.COM environment wikitext text/x-wiki == Summary == MS-DOS COMMAND.COM environment == Licensing == {{PD}} 90682bc42bc6166eec37956c16a677591ea2d6fe 0 433 2798 2025 2025-07-20T12:55:29Z Imnotgoodatnames 121 Added images a CLI text editor, MS-DOS prompt, minor text edits, replaced image of a GUI environment with a CLI window with a full CLI environment. wikitext text/x-wiki {{Needs Citations}} A '''CLI''' (Command-Line Interface) is a text-based interaction model in which users type commands as text strings to interact with an operating system or a program through a computer. Unlike a [[TUI]], which relies upon a pseudo-graphical form made of characters, an interface that is purely a command-driven one usually would issue output in the form of lines of text upon receiving user instructions. [[File:Unix shell.png|thumb|A Unix shell command prompt, an example of a CLI]] CLIs are often preferred by power users, system administrators, and developers for their efficiency, scriptability, and precise control over system operations. Common examples include: * Unix/Linux shells (sh, bash, zsh, fish) * Windows Command Prompt * PowerShell * Python's REPL (Read-Eval-Print Loop) The main advantages of CLIs include: * Resource efficiency (minimal system requirements) * Automation capability through scripting * Remote system administration * Precise control over system operations * Speed of execution for experienced users While CLIs can have a steeper learning curve compared to GUIs (Graphical User Interfaces) or [[TUI]]s, they remain fundamental to modern computing, particularly in server administration, software development, and system maintenance. == History == [[File:Ed editor.png|thumb|Ed, a Unix CLI text editor]] Command-line interfaces emerged in the 1960s with teleprinters like the Teletype Model 33 ASR, which replaced punch cards as the primary means of computer interaction. Early operating systems like Unix and MS-DOS were primarily accessed through CLIs, establishing conventions that persist in modern computing. [[File:Command com.png|thumb|The MS-DOS command prompt]] == Common Usage == CLI environments typically follow a standard pattern where: * The system displays a prompt (e.g., "$" for Unix-like systems) * Users type commands followed by arguments or options * The system executes the command and displays the output * The process repeats with a new prompt [[Category:Terminology]] [[Category:User interfaces]] 4690f157db1f94d39590635bbc912964724f0215 2811 2798 2025-07-21T12:47:25Z Imnotgoodatnames 121 wikitext text/x-wiki {{Needs Citations}} A '''CLI''' (Command-Line Interface) is a text-based interaction model in which users type commands as text strings to interact with an operating system or a program through a computer. Unlike a [[TUI]], which relies upon a pseudo-graphical form made of characters, an interface that is purely a command-driven one usually would issue output in the form of lines of text upon receiving user instructions. [[File:Unix shell.png|thumb|A Unix shell command prompt, an example of a CLI]] CLIs are often preferred by power users, system administrators, and developers for their efficiency, scriptability, and precise control over system operations. Common examples include: * Unix/Linux shells (sh, bash, zsh, fish) * Windows Command Prompt * PowerShell * Python's REPL (Read-Eval-Print Loop) The main advantages of CLIs include: * Resource efficiency (minimal system requirements) * Automation capability through scripting * Remote system administration * Precise control over system operations * Speed of execution for experienced users While CLIs can have a steeper learning curve compared to GUIs (Graphical User Interfaces) or [[TUI]]s, they remain fundamental to modern computing, particularly in server administration, software development, and system maintenance. == History == [[File:Edwind.png|thumb|CLI text editor Ed in a GUI terminal emulator window]] Command-line interfaces emerged in the 1960s with teleprinters like the Teletype Model 33 ASR, which replaced punch cards as the primary means of computer interaction. Early operating systems like Unix and MS-DOS were primarily accessed through CLIs, establishing conventions that persist in modern computing. [[File:Command com.png|thumb|The MS-DOS command prompt]] == Common Usage == CLI environments typically follow a standard pattern where: * The system displays a prompt (e.g., "$" for Unix-like systems) * Users type commands followed by arguments or options * The system executes the command and displays the output * The process repeats with a new prompt [[Category:Terminology]] [[Category:User interfaces]] 8edfe46d3a00b1ba51c9f6a2c002a33e17f1aad0 0 667 2799 2681 2025-07-20T13:10:15Z Imnotgoodatnames 121 wikitext text/x-wiki {{Cleanup|Incomplete page}}{{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}}'''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. Examples of modern UNIX operating systems include Apple's MacOS and IBM AIX. d83a0fc26c50aac260ac5afca2bf6c437fda8697 2 732 2800 2025-07-20T16:00:21Z Beatrixzy 179 Added a brief summary to self wikitext text/x-wiki Beatrixzy (AKA Bea / Beatroot in ATL) is a user who owns obscure hardware and occasionally does obscure things to those machines. Usually found in Lounge ++ or vip-lounge 6295dd5192e1f9b338e2a75bc801a2dea633a692 0 733 2801 2025-07-20T20:28:22Z S1oplus 180 Added more info about the Apple M1 SoC, still have more stuff to add soon. wikitext text/x-wiki The Apple M1 is an SoC that was launched in 2020 following the company’s switch from x86-64 to ARM64e cpus, the M1 has 8 Cores (4 Firestorm and 4 Icestorm) taken from the A14 Bionic. [[File:M1 A13 comparison MacMini9 1 M1.jpg|alt=M1 and A13 Bionic|thumb|M1 and A13 Bionic]] The SoC has been present in the late 2020 MacBook Air, late 2020 13” MacBook Pro, 2020 Mac Mini, 2021 24” iMac, iPad Pro 2021 (both sizes) and the 5th generation iPad Air (2022) It features a 7 or 8 core GPU (8 core was optional in some models) which uses cores from the A14 Bionic. {{DEFAULTSORT:Apple M1}} d7c8a75d4699ab07a3df4a50a7d72c621ea52248 2802 2801 2025-07-20T20:37:01Z Ow0cast 249 tagging | needs cites wikitext text/x-wiki {{Needs Citations}} The Apple M1 is an SoC that was launched in 2020 following the company’s switch from x86-64 to ARM64e cpus, the M1 has 8 Cores (4 Firestorm and 4 Icestorm) taken from the A14 Bionic. [[File:M1 A13 comparison MacMini9 1 M1.jpg|alt=M1 and A13 Bionic|thumb|M1 and A13 Bionic]] The SoC has been present in the late 2020 MacBook Air, late 2020 13” MacBook Pro, 2020 Mac Mini, 2021 24” iMac, iPad Pro 2021 (both sizes) and the 5th generation iPad Air (2022) It features a 7 or 8 core GPU (8 core was optional in some models) which uses cores from the A14 Bionic. {{DEFAULTSORT:Apple M1}} b6f0c3b307ea156d160eb002b64be8e5cd38ac3c 2803 2802 2025-07-20T21:30:15Z S1oplus 180 reorganized some of the page and added more info on M1, variants and devices. wikitext text/x-wiki {{Needs Citations}} '''Apple M1''' is a series of ARM-based system-on-a-chip (SoC) designed by Apple Inc., launched 2020 to 2022. It is part of the Apple silicon series, as a central processing unit (CPU) and graphics processing unit (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon"[https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php] and the world's best CPU performance per watt.[https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php][https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwith. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion. [[File:Macbook Air 2020 (M1) - 1.jpg|thumb|M1 MacBook Air running [[macOS]] 11 "Big Sur"]] The M1 runs Apple's [[macOS]] and iPadOS, Initial support for the M1 SoC in the Linux kernel was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] === CPU === The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big.LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU. ==== M1 Pro and M1 Max ==== The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC). ==== M1 Ultra ==== The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC). === Other features === The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second. Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four). The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors) and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23). The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini. The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks. At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks. == Devices with M1 == as of July 20th 2025, device with M1 include: * Macbook Air 2020 (M1) * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) == M1 Pro: == * Macbook Pro 14 & 16 inch (2021) == M1 Max: == * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) == M1 Ultra: == * Mac Studio (2022) {{DEFAULTSORT:Apple M1}} 637b102e802c1056a4a815cc16011e6683986775 2804 2803 2025-07-20T21:33:16Z S1oplus 180 made "CPU" and "Other features" into headings wikitext text/x-wiki {{Needs Citations}} '''Apple M1''' is a series of ARM-based system-on-a-chip (SoC) designed by Apple Inc., launched 2020 to 2022. It is part of the Apple silicon series, as a central processing unit (CPU) and graphics processing unit (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon"[https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php] and the world's best CPU performance per watt.[https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php][https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwith. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion. [[File:Macbook Air 2020 (M1) - 1.jpg|thumb|M1 MacBook Air running [[macOS]] 11 "Big Sur"]] The M1 runs Apple's [[macOS]] and iPadOS, Initial support for the M1 SoC in the Linux kernel was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == CPU == The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big.LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU. == M1 Pro and M1 Max == The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC). == M1 Ultra == The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC). == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second. Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four). The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors) and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23). The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini. The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks. At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks. == Devices with M1 == as of July 20th 2025, device with M1 include: * Macbook Air 2020 (M1) * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) == M1 Pro: == * Macbook Pro 14 & 16 inch (2021) == M1 Max: == * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) == M1 Ultra: == * Mac Studio (2022) {{DEFAULTSORT:Apple M1}} 0cf272b1b8efb35232063a39f9515b0c77beb22b 2805 2804 2025-07-20T22:34:57Z S1oplus 180 wikitext text/x-wiki {{Needs Citations}} '''Apple M1''' is a series of ARM-based system-on-a-chip (SoC) designed by Apple Inc., launched 2020 to 2022. It is part of the Apple silicon series, as a central processing unit (CPU) and graphics processing unit (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon"[https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php] and the world's best CPU performance per watt.[https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php][https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwith. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion. [[File:Macbook Air 2020 (M1) - 1.jpg|thumb|M1 MacBook Air running [[macOS]] 11 "Big Sur"]] The M1 runs Apple's [[macOS]] and iPadOS, Initial support for the M1 SoC in the Linux kernel was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == CPU == The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big.LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU. == M1 Pro and M1 Max == The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC). == M1 Ultra == The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC). == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second. Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four). The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors) and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23). The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini. The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks. At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks. == Devices with M1 == as of July 20th 2025, device with M1 include: Macbook Air 2020 (M1) Mac Mini 2020 (M1) 13 inch Macbook Pro 2020 (M1) 24 inch iMac 2021 (M1) iPad Pro 11 inch (3rd Generation) iPad Pro 12 inch (5th Generation) iPad Air (5th Generation) Macbook Pro 14 & 16 inch (2021) Mac Studio (2022){{DEFAULTSORT:Apple M1}} 7156d2d36cad904cac2592b44fff34662107b84a 4 571 2806 1891 2025-07-21T11:50:24Z Atmois 13 Update privacy policy wikitext text/x-wiki = atl.wiki Privacy Policy = Last Updated: 21st July 2025 Welcome to '''atl.wiki'''<nowiki/>'s Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''atl.wiki'''. By accessing or contributing to '''atl.wiki''', you agree to the terms outlined in this Privacy Policy. == <u>Information atl.wiki Collects</u> == When you edit any article or page on '''atl.wiki''', you are creating a permanent, public record of any change, addition, removal made by you. Public records will show the time and username authoring the edits. ''To contribute to '''atl.wiki''', you are required to create an account. When registering, '''atl.wiki''' collects:'' * A Username * [Optionally] Your Email Address <blockquote>Other information such as your pronouns, Discord ID and full name may be optionally provided to us via your user preferences or our Discord linking service.</blockquote> When a user is logged in '''atl.wiki''' uses essential cookies to maintain your login session and preferences. These cookies are required for the site to function and not shared nor used across other sites. Upon visiting the wiki the web-server will automatically log your IP Address and your User Agent, this information helps identify technical issues and ensure compatibility across devices. The web-server logs are automatically cleared regularly. The IP address of an editor will also be logged by Mediawiki when an edit has been made for anti-vandalism efforts. The logged IP is only available to administrators and will only be used for the purpose of blocking or sanctioning malicious users. <blockquote>The logging is provided by the [[mediawikiwiki:Extension:CheckUser|Check User Extension]].</blockquote> ==== Services atl.wiki Uses ==== '''atl.wiki''' uses a self-hosted instance of Umami Analytics to collect anonymous data about how visitors interact with our website. Umami collects: Page views, referring website and user agents. Umami does not collect personal data or use cookies, this data allows us to improve our site’s performance and user experience. <blockquote>For more details, please see [https://umami.is/docs Umami's Documentation].</blockquote> '''atl.wiki''' also uses Cloudflare to enhance website security and performance. Cloudflare may process certain technical information, such as IP addresses and user agents, to provide services like content delivery, DDoS protection, and caching. Cloudflare also makes use of cookies of cookies to manage bot protection and verify access. These cookies are required for site security and functionality, these cookies are not shared nor used across other sites. <blockquote>For more details, please see [https://www.cloudflare.com/en-gb/privacypolicy/ Cloudflare’s Privacy Policy].</blockquote> === <u>How atl.wiki uses your Information</u> === '''atl.wiki''' does not sell, trade, or otherwise transfer your personal information to third parties. '''atl.wiki''' will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where '''atl.wiki''' is present. '''atl.wiki''' will never provide your information to third parties without your explicit consent. '''''atl.wiki''' use your data to do the following:'' * To send administrative notices via email. * For the ability to reset your account password via email. * To moderate and combat vandalism & spam on the wiki. * To correctly attribute contributions on the wiki to users. * To monitor and analyse the usage of our services and identify technical issues. '''atl.wiki''' uses a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so '''atl.wiki''' cannot guarantee that our security will not be breached. In the event of a data breach, '''atl.wiki''' will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities. == <u>Your Rights</u> == ''Under the General Data Protections Act you are afforded the following rights:'' ; Right to be informed: : The right to be informed about the collection and use of their personal data. ; Right to access: : The right to access and receive a copy of their personal data, and other supplementary information. ; Right to rectification: : The right to have inaccurate personal data rectified, or completed if it is incomplete. ; Right to erasure: : The right to have personal data erased (Also known as being "forgotten"). ; Right to restrict processing: : The right to request the restriction or suppression of their personal data. ; Right to data portability: : The right to obtain and reuse their personal data for their own purposes across different services. ; Right to object: : The right to object to the processing of their personal data in certain circumstances. ; Right to control automated decision making: : The right to be informed about automated decision systems and are allowed to request human review. == <u>Changes to the Privacy Policy</u> == '''atl.wiki''' may change the Privacy Policy as needed to represent changes in our practises or legal requirements. '''atl.wiki''' will notify users of updates that impact them, and all revisions will be available on this page. == <u>Third-party Links</u> == '''atl.wiki''' may contain links to third-party websites. '''atl.wiki''' is not responsible for the privacy practices or content of these sites. '''atl.wiki''' encourages users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>wiki@allthingslinux.org</code>. f6f4774e7d36c12972dbe49032176a5f2ef150cb 2807 2806 2025-07-21T11:54:19Z Atmois 13 Reinsert the erasure protocol wikitext text/x-wiki = atl.wiki Privacy Policy = Last Updated: 21st July 2025 Welcome to '''atl.wiki'''<nowiki/>'s Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''atl.wiki'''. By accessing or contributing to '''atl.wiki''', you agree to the terms outlined in this Privacy Policy. == <u>Information atl.wiki Collects</u> == When you edit any article or page on '''atl.wiki''', you are creating a permanent, public record of any change, addition, removal made by you. Public records will show the time and username authoring the edits. ''To contribute to '''atl.wiki''', you are required to create an account. When registering, '''atl.wiki''' collects:'' * A Username * [Optionally] Your Email Address <blockquote>Other information such as your pronouns, Discord ID and full name may be optionally provided to us via your user preferences or our Discord linking service.</blockquote> When a user is logged in '''atl.wiki''' uses essential cookies to maintain your login session and preferences. These cookies are required for the site to function and not shared nor used across other sites. Upon visiting the wiki the web-server will automatically log your IP Address and your User Agent, this information helps identify technical issues and ensure compatibility across devices. The web-server logs are automatically cleared regularly. The IP address of an editor will also be logged by Mediawiki when an edit has been made for anti-vandalism efforts. The logged IP is only available to administrators and will only be used for the purpose of blocking or sanctioning malicious users. <blockquote>The logging is provided by the [[mediawikiwiki:Extension:CheckUser|Check User Extension]].</blockquote> ==== Services atl.wiki Uses ==== '''atl.wiki''' uses a self-hosted instance of Umami Analytics to collect anonymous data about how visitors interact with our website. Umami collects: Page views, referring website and user agents. Umami does not collect personal data or use cookies, this data allows us to improve our site’s performance and user experience. <blockquote>For more details, please see [https://umami.is/docs Umami's Documentation].</blockquote> '''atl.wiki''' also uses Cloudflare to enhance website security and performance. Cloudflare may process certain technical information, such as IP addresses and user agents, to provide services like content delivery, DDoS protection, and caching. Cloudflare also makes use of cookies of cookies to manage bot protection and verify access. These cookies are required for site security and functionality, these cookies are not shared nor used across other sites. <blockquote>For more details, please see [https://www.cloudflare.com/en-gb/privacypolicy/ Cloudflare’s Privacy Policy].</blockquote> === <u>How atl.wiki uses your Information</u> === '''atl.wiki''' does not sell, trade, or otherwise transfer your personal information to third parties. '''atl.wiki''' will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where '''atl.wiki''' is present. '''atl.wiki''' will never provide your information to third parties without your explicit consent. '''''atl.wiki''' use your data to do the following:'' * To send administrative notices via email. * For the ability to reset your account password via email. * To moderate and combat vandalism & spam on the wiki. * To correctly attribute contributions on the wiki to users. * To monitor and analyse the usage of our services and identify technical issues. '''atl.wiki''' uses a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so '''atl.wiki''' cannot guarantee that our security will not be breached. In the event of a data breach, '''atl.wiki''' will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities. == <u>Your Rights</u> == ''Under the General Data Protections Act you are afforded the following rights:'' ; Right to be informed: : The right to be informed about the collection and use of their personal data. ; Right to access: : The right to access and receive a copy of their personal data, and other supplementary information. ; Right to rectification: : The right to have inaccurate personal data rectified, or completed if it is incomplete. ; Right to erasure: : The right to have personal data erased (Also known as being "forgotten"). ; Right to restrict processing: : The right to request the restriction or suppression of their personal data. ; Right to data portability: : The right to obtain and reuse their personal data for their own purposes across different services. ; Right to object: : The right to object to the processing of their personal data in certain circumstances. ; Right to control automated decision making: : The right to be informed about automated decision systems and are allowed to request human review. In order to comply with GDPR erasure requests and the licensing of content, '''atl.wiki''' has implemented a process to remove all your data from '''atl.wiki'''. Your account name will be anonymised and your edits will be reattributed to the anonymised username. You will be asked to remove your email and other personal information provided to us via your user preferences. Once this process has been completed your account will be "vanished", which removes it from public logs, then your account will be blocked to prevent future logins. == <u>Changes to the Privacy Policy</u> == '''atl.wiki''' may change the Privacy Policy as needed to represent changes in our practises or legal requirements. '''atl.wiki''' will notify users of updates that impact them, and all revisions will be available on this page. == <u>Third-party Links</u> == '''atl.wiki''' may contain links to third-party websites. '''atl.wiki''' is not responsible for the privacy practices or content of these sites. '''atl.wiki''' encourages users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>wiki@allthingslinux.org</code>. 415c5c965df921001445391a6ecacf41d921a79d 0 218 2808 2687 2025-07-21T12:22:40Z Imnotgoodatnames 121 Changed "Most tiling Window managers" to "Most Window managers". There's nothing specific about tiling WMs that makes them more lightweight than other kinds of WM, such as stacking WMs. wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} == Introduction == [[Linux]] is a great choice for reviving older and slower devices due to it's often significantly lower system requirements than Windows<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> and macOS, and complete lack of planned obsolescence. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> cd64320e003b58a2bc93ffb8ab4d4d5a11803b50 6 734 2809 2025-07-21T12:35:34Z Imnotgoodatnames 121 Ed in a graphical terminal emulator window. wikitext text/x-wiki == Summary == Ed in a graphical terminal emulator window. == Licensing == {{PD}} b4e14d62791b51ea24a143f6867d39d77e454dd5 6 735 2810 2025-07-21T12:36:33Z Imnotgoodatnames 121 Line editor Ed wikitext text/x-wiki == Summary == Line editor Ed == Licensing == {{PD}} 04cba9a47f8be3e24387fc951976f4d75f98229a 0 736 2812 2025-07-21T13:34:13Z Imnotgoodatnames 121 Created page. wikitext text/x-wiki [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like it's successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was a part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains a part of POSIX and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to it's reputation as a user-hostile environment ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tools <code>sed</code> and <code>grep</code> were directly inspired by ed commands <code>s/e/d</code> and <code>g/re/p</code> ed would serve as a major influence to the line editor ex, from which would later come the screen editor vi, whose variants remain some of the most popular TUI text editors. 4a900e1580574de133b729e4cb69d644df8c6fd4 0 736 2813 2812 2025-07-21T13:41:09Z Madonuko 140 links and format wikitext text/x-wiki [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains part of POSIX and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to it's reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tools [[sed|<code>sed</code>]] and [[grep|<code>grep</code>]] were directly inspired by ed commands <code>s/e/d</code> and <code>g/re/p</code> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor [[vi]], whose variants remain some of the most popular TUI text editors. 5da6982ab0445f4b184f6eeae0049a17eba0a0cb 2814 2813 2025-07-21T14:38:20Z Imnotgoodatnames 121 wikitext text/x-wiki [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to it's reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tools [[sed|<code>sed</code>]] and [[grep|<code>grep</code>]] were directly inspired by ed commands <code>s/e/d</code> and <code>g/re/p</code> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor [[vi]], whose variants remain some of the most popular TUI text editors. 92e9c60f80fe05f33cfb7094839692ff7bd168e7 2863 2814 2025-07-23T19:01:56Z Ow0cast 249 /* Legacy */ cleanup | semi-auto, typos fixed: it's → its wikitext text/x-wiki [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tools [[sed|<code>sed</code>]] and [[grep|<code>grep</code>]] were directly inspired by ed commands <code>s/e/d</code> and <code>g/re/p</code> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor [[vi]], whose variants remain some of the most popular TUI text editors. f1a4bc00c3505162275606f0aeb6f6bc9d1facad 0 626 2815 2266 2025-07-21T14:38:35Z Persimmon 181 Added information about partial upgrades wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>https://manjaro.org/</ref>. It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]]. <ref name=":0">https://distrowatch.com/table.php?distribution=manjaro</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>https://wiki.manjaro.org/index.php/Pamac</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>https://en.wikipedia.org/wiki/Manjaro</ref><ref>https://www.ubuntumint.com/manjaro-linux-history/</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>https://www.geeksforgeeks.org/how-to-install-manjaro-linux/</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch’s base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch’s, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro’s custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch’s upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>https://itsfoss.com/manjaro-vs-arch-linux/</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. Manjaro packages may also differ slightly in configuration or carry additional patches or branding. Furthermore, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported</ref> 95350dfba3f4bef087146315ad5f9b6f29dca400 2826 2815 2025-07-21T16:19:16Z Atmois 13 Change wording to remove bias wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>https://manjaro.org/</ref>. It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]]. <ref name=":0">https://distrowatch.com/table.php?distribution=manjaro</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>https://wiki.manjaro.org/index.php/Pamac</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>https://en.wikipedia.org/wiki/Manjaro</ref><ref>https://www.ubuntumint.com/manjaro-linux-history/</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>https://www.geeksforgeeks.org/how-to-install-manjaro-linux/</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch’s base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch’s, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro’s custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch’s upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>https://itsfoss.com/manjaro-vs-arch-linux/</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. Manjaro packages may also differ slightly in configuration or carry additional patches or branding. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported</ref> 963596fba73e0bda7ba080d3652f4f4c26495cc8 2832 2826 2025-07-21T18:39:38Z Persimmon 181 Move sentence down for continuity wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>https://manjaro.org/</ref>. It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]]. <ref name=":0">https://distrowatch.com/table.php?distribution=manjaro</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>https://wiki.manjaro.org/index.php/Pamac</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>https://en.wikipedia.org/wiki/Manjaro</ref><ref>https://www.ubuntumint.com/manjaro-linux-history/</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>https://www.geeksforgeeks.org/how-to-install-manjaro-linux/</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch’s base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch’s, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro’s custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch’s upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>https://itsfoss.com/manjaro-vs-arch-linux/</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. 1e43d0e3980e94b8117067199065aaf1c69fe64b 2834 2832 2025-07-22T00:04:11Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]], spaces around cites wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>https://manjaro.org/</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">https://distrowatch.com/table.php?distribution=manjaro</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>https://wiki.manjaro.org/index.php/Pamac</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>https://en.wikipedia.org/wiki/Manjaro</ref><ref>https://www.ubuntumint.com/manjaro-linux-history/</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>https://www.geeksforgeeks.org/how-to-install-manjaro-linux/</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch’s base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch’s, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro’s custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch’s upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>https://itsfoss.com/manjaro-vs-arch-linux/</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. aa00a155a609966981b8c9de50b6d0f8c6b60eaf 0 405 2816 2620 2025-07-21T14:43:28Z Imnotgoodatnames 121 Changed "Unix-like operating systems" to "open source operating systems". Proprietary Unix-like operating systems exist (eg. Oracle Solaris) wikitext text/x-wiki {{Cleanup|Short page}} Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Linux and other open source operating systems will avoid or not support proprietary software when possible. This is mainly due to incompatible licensing.<ref>https://solutionshub.epam.com/blog/post/proprietary-software-definition-examples Epam, 2025 (imported 27th June 2025)</ref> Some examples of proprietary software are Microsoft Windows and Adobe Photoshop. [[Category:Terminology]] ce42584f5c2cb05a12e4c55a64fba86393232d15 0 176 2817 2671 2025-07-21T14:44:54Z Imnotgoodatnames 121 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows.<references /> [[Category:Desktop Environments]] c5f35773b65741a1cc7dee07fc527c2fde7b3dea 0 641 2818 2370 2025-07-21T14:48:19Z Imnotgoodatnames 121 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Maintenance |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/, openbox.org] }} [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable [[X Window Manager|window manager]] for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>https://openbox.org/</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>https://openbox.org/obconf</ref> === Usage === While Openbox is perfectly usable on its own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>https://slitaz.org/en/about/</ref><ref>https://crunchbang.org/about/</ref><references /> [[Category:Desktop Environments]] 52e4b79e4475efc07e5edb97d2735b171a5c0ee8 0 570 2819 2039 2025-07-21T15:02:31Z Imnotgoodatnames 121 wikitext text/x-wiki {{Needs_Citations}} {{MascotInfobox | title = GNU | image = [[File:Heckert_GNU_white.svg|thumb]] | caption = GNU, the mascot of the GNU Project }} GNU is the mascot of the [[GNU]] Project GNU is a black and white sketch of a wildebeest (also known as a gnu or gnou) [[Category:Mascots]] 1778cf38eb17015f0bfea3eb9415a7a894b53065 0 733 2820 2805 2025-07-21T15:04:53Z S1oplus 180 Added most if not all missing citations, added "Variants" table. wikitext text/x-wiki '''Apple M1''' is a series of ARM-based system-on-a-chip (SoC) designed by Apple Inc., launched 2020 to 2022. It is part of the Apple silicon series, as a central processing unit (CPU) and graphics processing unit (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwith. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>[[wikipedia:Apple_M1#:~:text=The%20original%20M1,has%20114%20billion.|https://en.wikipedia.org/wiki/Apple_M1#:~:text=The%20original%20M1,has%20114%20billion.]]</ref> [[File:Macbook Air 2020 (M1) - 1.jpg|thumb|M1 MacBook Air running [[macOS]] 11 "Big Sur"]] The M1 runs Apple's [[macOS]] and iPadOS, Initial support for the M1 SoC in the Linux kernel was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == CPU == The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big.LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[[wikipedia:Apple_M1#CPU:~:text=The%20M1%20has,by%20the%20GPU.|https://en.wikipedia.org/wiki/Apple_M1#CPU:~:text=The%20M1%20has,by%20the%20GPU.]]</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>https://en.wikipedia.org/wiki/Apple_M1#CPU:~:text=M1%20Pro%20and%20M1%20Max%5B,level%20cache%20(SLC).%5B12%5D</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>[[wikipedia:Apple_M1#CPU:~:text=M1%20Ultra%5B,level%20cache%20(SLC).|https://en.wikipedia.org/wiki/Apple_M1#CPU:~:text=M1%20Ultra%5B,level%20cache%20(SLC).]]</ref> == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>https://www.apple.com/mac/m1/</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>https://support.apple.com/kb/SP858?locale=en_US</ref><ref>https://support.apple.com/kb/SP865?locale=en_US</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>https://borderpolar.com/tech/apple-m1-benchmarks/</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>https://www.nytimes.com/wirecutter/reviews/best-macbooks/</ref><ref>https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: Macbook Air 2020 (M1) - base model has binned, 7-Core GPU Mac Mini 2020 (M1) 13 inch Macbook Pro 2020 (M1) 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU iPad Pro 11 inch (3rd Generation) iPad Pro 12 inch (5th Generation) iPad Air (5th Generation) Macbook Pro 14 & 16 inch (2021) Mac Studio (2022) == Variants == The table below shows the various SoCs based on the "Firestorm" and "Icestorm" microarchitectures. {| class="wikitable" |+ !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} {{DEFAULTSORT:Apple M1}} 0a4feb6bae5792623e7e41bd4c101bb3ca9d1f46 2821 2820 2025-07-21T15:06:33Z S1oplus 180 Reorganized CPU tab (i fogor to do it in the last edit) wikitext text/x-wiki '''Apple M1''' is a series of ARM-based system-on-a-chip (SoC) designed by Apple Inc., launched 2020 to 2022. It is part of the Apple silicon series, as a central processing unit (CPU) and graphics processing unit (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwith. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>[[wikipedia:Apple_M1#:~:text=The%20original%20M1,has%20114%20billion.|https://en.wikipedia.org/wiki/Apple_M1#:~:text=The%20original%20M1,has%20114%20billion.]]</ref> [[File:Macbook Air 2020 (M1) - 1.jpg|thumb|M1 MacBook Air running [[macOS]] 11 "Big Sur"]] The M1 runs Apple's [[macOS]] and iPadOS, Initial support for the M1 SoC in the Linux kernel was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == CPU == === M1 === The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big.LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[[wikipedia:Apple_M1#CPU:~:text=The%20M1%20has,by%20the%20GPU.|https://en.wikipedia.org/wiki/Apple_M1#CPU:~:text=The%20M1%20has,by%20the%20GPU.]]</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>https://en.wikipedia.org/wiki/Apple_M1#CPU:~:text=M1%20Pro%20and%20M1%20Max%5B,level%20cache%20(SLC).%5B12%5D</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>[[wikipedia:Apple_M1#CPU:~:text=M1%20Ultra%5B,level%20cache%20(SLC).|https://en.wikipedia.org/wiki/Apple_M1#CPU:~:text=M1%20Ultra%5B,level%20cache%20(SLC).]]</ref> == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>https://www.apple.com/mac/m1/</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>https://support.apple.com/kb/SP858?locale=en_US</ref><ref>https://support.apple.com/kb/SP865?locale=en_US</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>https://borderpolar.com/tech/apple-m1-benchmarks/</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>https://www.nytimes.com/wirecutter/reviews/best-macbooks/</ref><ref>https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: Macbook Air 2020 (M1) - base model has binned, 7-Core GPU Mac Mini 2020 (M1) 13 inch Macbook Pro 2020 (M1) 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU iPad Pro 11 inch (3rd Generation) iPad Pro 12 inch (5th Generation) iPad Air (5th Generation) Macbook Pro 14 & 16 inch (2021) Mac Studio (2022) == Variants == The table below shows the various SoCs based on the "Firestorm" and "Icestorm" microarchitectures. {| class="wikitable" |+ !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} {{DEFAULTSORT:Apple M1}} ac71fa94fde8f201959b1bcf81b3d9f6ffbc95a6 2822 2821 2025-07-21T15:42:56Z Imnotgoodatnames 121 Replaced all Wikipedia sources. wikitext text/x-wiki '''Apple M1''' is a series of ARM-based system-on-a-chip (SoC) designed by Apple Inc., launched 2020 to 2022. It is part of the Apple silicon series, as a central processing unit (CPU) and graphics processing unit (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwith. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>https://www.apple.com/newsroom/2022/03/apple-unveils-m1-ultra-the-worlds-most-powerful-chip-for-a-personal-computer/</ref> [[File:Macbook Air 2020 (M1) - 1.jpg|thumb|M1 MacBook Air running [[macOS]] 11 "Big Sur"]] The M1 runs Apple's [[macOS]] and iPadOS, Initial support for the M1 SoC in the Linux kernel was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == CPU == === M1 === The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big.LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[https://www.youtube.com/watch?v=BCvL8O0-Qwo https://www.youtube.com/watch?v=BCvL8O0-Qwo&t=4m18s]</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>https://www.apple.com/mac/m1/</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>https://support.apple.com/kb/SP858?locale=en_US</ref><ref>https://support.apple.com/kb/SP865?locale=en_US</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>https://borderpolar.com/tech/apple-m1-benchmarks/</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>https://www.nytimes.com/wirecutter/reviews/best-macbooks/</ref><ref>https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: Macbook Air 2020 (M1) - base model has binned, 7-Core GPU Mac Mini 2020 (M1) 13 inch Macbook Pro 2020 (M1) 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU iPad Pro 11 inch (3rd Generation) iPad Pro 12 inch (5th Generation) iPad Air (5th Generation) Macbook Pro 14 & 16 inch (2021) Mac Studio (2022) == Variants == The table below shows the various SoCs based on the "Firestorm" and "Icestorm" microarchitectures. {| class="wikitable" |+ !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} {{DEFAULTSORT:Apple M1}} 9d3d2023c460d653f9782fa9743b91cd5690f78c 2827 2822 2025-07-21T16:24:49Z Atmois 13 Move table, add links and fix some grammar and spelling mistakes wikitext text/x-wiki '''Apple M1''' is a series of [[ARM|ARM-based]] system-on-a-chip (SoC) designed by [[Apple|Apple Inc]]., launched 2020 to 2022. It is part of the Apple silicon series, as a [[central processing unit]] (CPU) and [[graphics processing unit]] (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwidth. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>https://www.apple.com/newsroom/2022/03/apple-unveils-m1-ultra-the-worlds-most-powerful-chip-for-a-personal-computer/</ref> [[File:Macbook Air 2020 (M1) - 1.jpg|thumb|M1 MacBook Air running [[macOS]] 11 "Big Sur"]] The M1 runs Apple's [[macOS]] and iPadOS, Initial support for the M1 SoC in the Linux kernel was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == M1 Chip Variants == === M1 === The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big. LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[https://www.youtube.com/watch?v=BCvL8O0-Qwo https://www.youtube.com/watch?v=BCvL8O0-Qwo&t=4m18s]</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> {| class="wikitable" |+SoCs of the "Firestorm" and "Icestorm" microarchitectures. !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>https://www.apple.com/mac/m1/</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>https://support.apple.com/kb/SP858?locale=en_US</ref><ref>https://support.apple.com/kb/SP865?locale=en_US</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>https://borderpolar.com/tech/apple-m1-benchmarks/</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>https://www.nytimes.com/wirecutter/reviews/best-macbooks/</ref><ref>https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: * Macbook Air 2020 (M1) - base model has binned, 7-Core GPU * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) and all the devices respective varients. {{DEFAULTSORT:Apple M1}} cb99c5f669c8d33485246e51c24841effc8e76f3 2829 2827 2025-07-21T17:43:21Z S1oplus 180 Added the only missing M1 variant (A14), added devices that use it, fixed spelling mistakes and moved the MacBook image. wikitext text/x-wiki '''Apple M1''' is a series of [[ARM|ARM-based]] system-on-a-chip (SoC) designed by [[Apple|Apple Inc]]., launched 2020 to 2022. It is part of the Apple silicon series, as a [[central processing unit]] (CPU) and [[graphics processing unit]] (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwidth. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>https://www.apple.com/newsroom/2022/03/apple-unveils-m1-ultra-the-worlds-most-powerful-chip-for-a-personal-computer/</ref> The M1 runs Apple's [[macOS]] and [[iPadOS]], Initial support for the M1 SoC in the [[Linux|Linux kernel]] was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == M1 Chip Variants == === A14 === [[File:Apple A14.jpg|thumb|Apple A14 Bionic, the chip M1 is based on.]] The Apple A14 Bionic features an Apple-designed 64-bit, six-core CPU, implementing ARMv8 with two high-performance cores called '''Firestorm''' and four energy-efficient cores called '''Icestorm'''.<ref>[https://www.youtube.com/live/KR0g-1hnQPA?si=0l-0ixbkIdH8_pLf https://www.youtube.com/live/KR0g-1hnQPA]</ref> === M1 === The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big. LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[https://www.youtube.com/watch?v=BCvL8O0-Qwo https://www.youtube.com/watch?v=BCvL8O0-Qwo&t=4m18s]</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> {| class="wikitable" |+SoCs of the "Firestorm" and "Icestorm" microarchitectures. !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>https://www.apple.com/mac/m1/</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>https://support.apple.com/kb/SP858?locale=en_US</ref><ref>https://support.apple.com/kb/SP865?locale=en_US</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>https://borderpolar.com/tech/apple-m1-benchmarks/</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>https://www.nytimes.com/wirecutter/reviews/best-macbooks/</ref><ref>https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: * [[File:Macbook Pro 13" M1 2020.jpg|thumb|M1 Macbook Pro]]Macbook Air 2020 (M1) - base model has binned, 7-Core GPU * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) * iPhone 12 and 12 mini (A14) * iPhone 12 Pro and 12 Pro Max (A14) * iPad air 4(th generation) (A14) * iPad (10th generation) (A14) and all the devices respective variants. {{DEFAULTSORT:Apple M1}} faf9978a7952c213612b3a069bbd121e31ab54d8 2830 2829 2025-07-21T17:47:42Z S1oplus 180 Fixed more spelling mistakes wikitext text/x-wiki '''Apple M1''' is a series of [[ARM|ARM-based]] system-on-a-chip (SoC) designed by [[Apple|Apple Inc]]., launched 2020 to 2022. It is part of the Apple silicon series, as a [[central processing unit]] (CPU) and [[graphics processing unit]] (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwidth. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>https://www.apple.com/newsroom/2022/03/apple-unveils-m1-ultra-the-worlds-most-powerful-chip-for-a-personal-computer/</ref> The M1 runs Apple's [[macOS]] and [[iPadOS]], Initial support for the M1 SoC in the [[Linux|Linux kernel]] was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == M1 Chip Variants == === A14 === [[File:Apple A14.jpg|thumb|Apple A14 Bionic, the chip M1 is based on.]] The Apple A14 Bionic features an Apple-designed 64-bit, six-core CPU, implementing ARMv8 with two high-performance cores called “Firestorm” and four energy-efficient cores called “Icestorm”.<ref>[https://www.youtube.com/live/KR0g-1hnQPA?si=0l-0ixbkIdH8_pLf https://www.youtube.com/live/KR0g-1hnQPA]</ref> === M1 === The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big. LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[https://www.youtube.com/watch?v=BCvL8O0-Qwo https://www.youtube.com/watch?v=BCvL8O0-Qwo&t=4m18s]</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> {| class="wikitable" |+SoCs of the "Firestorm" and "Icestorm" microarchitectures. !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>https://www.apple.com/mac/m1/</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>https://support.apple.com/kb/SP858?locale=en_US</ref><ref>https://support.apple.com/kb/SP865?locale=en_US</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>https://borderpolar.com/tech/apple-m1-benchmarks/</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>https://www.nytimes.com/wirecutter/reviews/best-macbooks/</ref><ref>https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: * [[File:Macbook Pro 13" M1 2020.jpg|thumb|M1 Macbook Pro]]Macbook Air 2020 (M1) - base model has binned, 7-Core GPU * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) * iPhone 12 and 12 mini (A14) * iPhone 12 Pro and 12 Pro Max (A14) * iPad air 4(th generation) (A14) * iPad (10th generation) (A14) and all the devices respective variants. {{DEFAULTSORT:Apple M1}} 236f60c1474f4363d25112209732360763378489 2831 2830 2025-07-21T18:30:50Z S1oplus 180 fixed “devices with M1” wikitext text/x-wiki '''Apple M1''' is a series of [[ARM|ARM-based]] system-on-a-chip (SoC) designed by [[Apple|Apple Inc]]., launched 2020 to 2022. It is part of the Apple silicon series, as a [[central processing unit]] (CPU) and [[graphics processing unit]] (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwidth. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>https://www.apple.com/newsroom/2022/03/apple-unveils-m1-ultra-the-worlds-most-powerful-chip-for-a-personal-computer/</ref> The M1 runs Apple's [[macOS]] and [[iPadOS]], Initial support for the M1 SoC in the [[Linux|Linux kernel]] was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == M1 Chip Variants == === A14 === [[File:Apple A14.jpg|thumb|Apple A14 Bionic, the chip M1 is based on.]] The Apple A14 Bionic features an Apple-designed 64-bit, six-core CPU, implementing ARMv8 with two high-performance cores called “Firestorm” and four energy-efficient cores called “Icestorm”.<ref>[https://www.youtube.com/live/KR0g-1hnQPA?si=0l-0ixbkIdH8_pLf https://www.youtube.com/live/KR0g-1hnQPA]</ref> === M1 === The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big. LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[https://www.youtube.com/watch?v=BCvL8O0-Qwo https://www.youtube.com/watch?v=BCvL8O0-Qwo&t=4m18s]</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> {| class="wikitable" |+SoCs of the "Firestorm" and "Icestorm" microarchitectures. !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>https://www.apple.com/mac/m1/</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>https://support.apple.com/kb/SP858?locale=en_US</ref><ref>https://support.apple.com/kb/SP865?locale=en_US</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>https://borderpolar.com/tech/apple-m1-benchmarks/</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>https://www.nytimes.com/wirecutter/reviews/best-macbooks/</ref><ref>https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: * [[File:Macbook Pro 13" M1 2020.jpg|thumb|M1 Macbook Pro]] * Macbook Air 2020 (M1) - base model has binned, 7-Core GPU * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) * iPhone 12 and 12 mini (A14) * iPhone 12 Pro and 12 Pro Max (A14) * iPad air 4(th generation) (A14) * iPad (10th generation) (A14) and all the devices respective variants. {{DEFAULTSORT:Apple M1}} 3b87919baec5d68f37be3782762a4e993b620e14 4 340 2823 2790 2025-07-21T16:05:41Z Atmois 13 Finish citations section wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin'''; for any topics not outlined below, follow [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. As long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and lay out the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will auto generate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Standards == Other things to keep in mind when making edits include: * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote><references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 9fd885d224ea7218a39476ba5528e62ea72aaa49 2843 2823 2025-07-23T10:44:01Z Atmois 13 Grammer fix wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will auto generate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Standards == Other things to keep in mind when making edits include: * Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. * Don't make a new page unless you can add worthwhile content to it. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote><references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 5f4c9ca42efc29e9166161373f3123e20b0bcefa 2844 2843 2025-07-23T10:48:50Z Atmois 13 Create notability and categories headers for guidelines on the topic wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will auto generate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == Don't make a new page unless you can add worthwhile content to it. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote><references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] dddf4be2f92f5bd138c282e80b21d0dd33dac7f6 2846 2844 2025-07-23T14:03:05Z Atmois 13 Create an AI policy for the wiki wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will auto generate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == Don't make a new page unless you can add worthwhile content to it. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 0c503dda48ac89c2aa2a1e063a4852d707311072 2847 2846 2025-07-23T16:53:54Z Atmois 13 Add responsible disclosure section wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will auto generate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == Don't make a new page unless you can add worthwhile content to it. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits.<references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] bea14d5eb753d4cc1c70989e09e3d9df0285a6e7 0 218 2824 2808 2025-07-21T16:10:55Z Atmois 13 Reword the introduction to remove bias towards Linux wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} == Introduction == [[Linux]] due to its generally lower system requirements than [[Windows]]<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> or [[macOS]] and a general absence of vendor-imposed hardware restrictions is frequently chosen for reviving and reusing older devices. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (ie. keyrings, polkit, GTK, QT, etc) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> af0722add6c7fe2b1d3c1eb25163195e96baed0f 4 737 2825 2025-07-21T16:14:30Z Atmois 13 Create redirect wikitext text/x-wiki #REDIRECT [[wikipedia:Wikipedia:VisualEditor]] a56d10cd67826558bbb26be1ab27c7c48b44fd8c 0 310 2828 2005 2025-07-21T16:55:06Z Persimmon 181 Complete rewrite wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Alpine Linux | image = [[File:alpinelinux-logo.svg|thumb]] | releasestatus = Maintained | releasemodel = Point or Rolling | packagemanager = [[apk]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[MATE]], [[LXQt]] | usagetype = Container, Embedded, Server, Desktop | architectures = amd64, aarch64, armel, armhf, i686, ppc64le, s390x, loongarch64 | website = [https://www.alpinelinux.org/ alpinelinux.org] }} Alpine Linux is a lightweight Linux distribution that aims to "small", "simple" and "secure".<ref name=":0">https://alpinelinux.org/about/</ref> It is one of the few distributions that do not use the GNU C Library or GNU coreutils by default. Alpine by default follows a point release update model while its edge repositories follow a rolling release model. Twice a year, typically on November and May, a new stable version is branched from edge and released.<ref>https://alpinelinux.org/releases/</ref> == Features == Alpine's main feature is its small size. Its minimal system requirements and ease of deployability makes it suitable for use in containers, embedded systems and other systems with very limited resources. All user-space binaries in Alpine are compiled as position-independent executables with stack-smashing protection for security reasons.<ref name=":0" /> Alpine comes preinstalled configuration scripts which allows quick configuration and installation of the system.<ref>[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts]</ref> Alpine also offers a web-server based configuration tool named the Alpine Configuration Framework (ACF).<ref>https://wiki.alpinelinux.org/wiki/Alpine_Configuration_Framework_Design</ref> Alpine offers a "diskless installation"<ref>https://wiki.alpinelinux.org/wiki/Installation#Installation_Overview</ref>, which allows Alpine to be installed to and be used from RAM. == Differences from other Linux Distributions == * Alpine uses musl as its standard C library. This compromises its support for some programs such as Electron based applications<ref>https://wiki.alpinelinux.org/wiki/APKBUILD_examples:JavaScript</ref> and the NVIDIA drivers.<ref>https://wiki.alpinelinux.org/wiki/NVIDIA</ref> * Alpine by default lacks the standard base utilities that other distributions come with, such as GNU bash, coreutils, findutils, pciutils, usbutils, util-linux, udev. Instead of these, their busybox implementations are used. This is what allows Alpine to be so small, yet this also causes compatibility issues with many programs and scripts as their busybox implementations lack many features of their counterparts<ref>https://wiki.alpinelinux.org/wiki/How_to_get_regular_stuff_working</ref>. To solve these compatibility issues, the user can install the standard version of these programs as they wish. * Alpine does not use systemd. Instead, it uses busybox for its init process and OpenRC for service management.<ref>https://wiki.alpinelinux.org/wiki/OpenRC</ref> * Alpine uses its own package manager, the "Alpine Package Keeper" (apk).<ref>https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper</ref> * Alpine uses the LTS branch of the Linux kernel by default.<ref>https://github.com/alpinelinux/alpine-conf/blob/55ec2cf0504195ee60f68b21a29607302f8a15d0/setup-disk.in#L1489</ref> d6591e7701ccaa6d678f3f638d371aa5105af87b 2833 2828 2025-07-21T21:41:41Z Persimmon 181 grammar wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Alpine Linux | image = [[File:alpinelinux-logo.svg|thumb]] | releasestatus = Maintained | releasemodel = Point or Rolling | packagemanager = [[apk]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[MATE]], [[LXQt]] | usagetype = Container, Embedded, Server, Desktop | architectures = amd64, aarch64, armel, armhf, i686, ppc64le, s390x, loongarch64 | website = [https://www.alpinelinux.org/ alpinelinux.org] }} Alpine Linux is a lightweight Linux distribution that aims to "small", "simple" and "secure".<ref name=":0">https://alpinelinux.org/about/</ref> It is one of the few distributions that do not use the GNU C Library or GNU coreutils by default. Alpine, by default, follows a point release update model while its edge repositories follow a rolling release model. Twice a year, typically on November and May, a new stable version is branched from edge and released.<ref>https://alpinelinux.org/releases/</ref> == Features == Alpine's main feature is its small size. Its minimal system requirements and ease of deployability makes it suitable for use in containers, embedded systems and other systems with very limited resources. All user-space binaries in Alpine are compiled as position-independent executables with stack-smashing protection for security reasons.<ref name=":0" /> Alpine comes preinstalled with configuration scripts which allow quick configuration and installation of the system.<ref>[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts]</ref> Alpine also offers a web-server based configuration tool named the Alpine Configuration Framework (ACF).<ref>https://wiki.alpinelinux.org/wiki/Alpine_Configuration_Framework_Design</ref> Alpine offers a "diskless installation"<ref>https://wiki.alpinelinux.org/wiki/Installation#Installation_Overview</ref>, allowing it to be installed to and be used from RAM. == Differences from other Linux Distributions == * Alpine uses musl as its standard C library. This compromises its support for some programs such as Electron based applications<ref>https://wiki.alpinelinux.org/wiki/APKBUILD_examples:JavaScript</ref> and the NVIDIA drivers.<ref>https://wiki.alpinelinux.org/wiki/NVIDIA</ref> * Alpine by default lacks the standard base utilities that other distributions come with such as GNU bash, coreutils, findutils, pciutils, usbutils, util-linux, udev. Instead of these, their BusyBox implementations are used. This is what makes Alpine so small in size, yet this also causes compatibility issues with many programs and scripts as their BusyBox implementations lack many features of their counterparts<ref>https://wiki.alpinelinux.org/wiki/How_to_get_regular_stuff_working</ref>. To solve these compatibility issues, the user can install the standard version of these programs as they wish. * Alpine does not use systemd. Instead, it uses BusyBox for its init process and OpenRC for service management.<ref>https://wiki.alpinelinux.org/wiki/OpenRC</ref> * Alpine uses its own package manager, the "Alpine Package Keeper" (apk).<ref>https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper</ref> * Alpine uses the LTS branch of the Linux kernel by default.<ref>https://github.com/alpinelinux/alpine-conf/blob/55ec2cf0504195ee60f68b21a29607302f8a15d0/setup-disk.in#L1489</ref> e9c2143eb24553d688392f7774bd4f83e723fc91 0 677 2835 2556 2025-07-22T00:07:36Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki Flatpak is a universal packaging system and runtime for installing packages separate from the system packages. Mainly meant for desktop applications, Flatpak allows application developers to distribute packages without needing to worry about distro compatibility because Flatpak installs it's own runtime dependencies. It claims to improve security through sandboxing providing the user the ability to give or revoke permissions for a given application. Flatpak is installed by default on many distributions and it's main distribution platform is Flathub. == Installation == Flatpak comes preinstalled on many distributions such as Linux Mint and Fedora but can be installed through most distro's package repositories if not present. ==== KDE Discover ==== KDE Discover includes the ability to install Flatpak and enable Flathub through its graphical user interface. Go to the setting tab and install the Flatpak backend then restart Discover then go back to the settings and enable Flathub. ==== CLI Install on Ubuntu ==== To install Flatpak from the CLI run:<syntaxhighlight lang="bash"> sudo apt install flatpak </syntaxhighlight>To enable Flathub from the CLI run:<syntaxhighlight lang="bash"> flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo </syntaxhighlight>If you make use of GNOME Software you can install the integration plugin:<syntaxhighlight lang="bash"> sudo apt install gnome-software-plugin-flatpak </syntaxhighlight>For the KDE Discover plugin run:<syntaxhighlight lang="bash"> sudo apt install plasma-discover-backend-flatpak </syntaxhighlight>For other distros read the guides on [https://flathub.org/setup Flathub.org]. == Compatibility == Flatpak allows improved package compatibility through its use of it's own runtime dependencies. Packages can run through Flatpak where it might not be possible to run on natively such as: * Applications that require a newer version of glibc than whats available on an stable release distro such as Rocky Linux 8. * Applications that depend on glibc such as Steam running on a distro using musl like Alpine Linux. * Multilib packages such as Steam or Wine on distros without multilib support such as CentOS Stream 10. == Sandboxing == Package permissions can be managed by the user through a graphical user interface with Flatseal which can be installed as a Flatpak. == Flathub Package Verification == Flathub has a package verification system that allows packages maintained by the official developers to have a verification tick.<ref>[https://docs.flathub.org/docs/for-app-authors/verification Verification | Flathub Documentation], Flathub Team, 2025 (Accessed: 2025-06-22)</ref> This has lead to some confusion where verification is mistaken for package safety. Linux Mint hides unverified Flatpaks from Software Manager by default Starting in version 22.<ref>[https://www.omgubuntu.co.uk/2024/06/linux-mint-will-hide-unverified-flatpaks Linux Mint Will Hide Unverified Flatpaks in Software Manager - OMG! Ubuntu], Joey Sneddon, 2024 (Accessed: 2025-06-22)</ref> bbc0b7e741c1274eba51d2cd603afa9a79bbabac 0 659 2836 2630 2025-07-22T01:08:45Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki {{DistributionInfobox|title=ChromeOS|image=[[File:Chromium_Logo.svg|frameless]]|caption=ChromiumOs Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[APT]]|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website=[https://chromeos.google/ chromeos]}}ChromeOS (ChromiumOS) is a [[UNIX|Unix-Based]] [[Linux Distributions|Linux distribution]] designed and developed by Google in 2009. ChromeOS is completely open-source.<ref>http://source.chromium.org/chromiumos Official ChromeOS website, 2025 (imported 27th June 2025)</ref> <references /> 5fc8a9f3a47e4d36c0ac9ac0b4d4be7305558962 2848 2836 2025-07-23T18:26:09Z Ow0cast 249 factual | chromeos does NOT use apt wikitext text/x-wiki {{DistributionInfobox|title=ChromeOS|image=[[File:Chromium_Logo.svg|frameless]]|caption=ChromiumOs Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Portage]]|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website=[https://chromeos.google/ chromeos]}}ChromeOS (ChromiumOS) is a [[UNIX|Unix-Based]] [[Linux Distributions|Linux distribution]] designed and developed by Google in 2009. ChromeOS is completely open-source.<ref>http://source.chromium.org/chromiumos Official ChromeOS website, 2025 (imported 27th June 2025)</ref> <references /> b06f367261a315066bdde8352c3e9d51f1cc8acb 0 297 2837 2780 2025-07-22T01:12:07Z Ow0cast 249 ce | vanguard isnt just for valorant wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref> The core concept of multi-booting revolves around partitioning a computer’s [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system’s configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straight-forward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Riot's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats.<references /> [[Category:Terminology]] 3c410135bb6c2c5cbadf15b5f8587186b624dbd6 0 414 2838 2610 2025-07-22T01:21:36Z Ow0cast 249 cleanup | [[wikipedia:MOS:PF|period before citation]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970's, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at Bell Labs, and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and pre-processors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include GNU GCC, Clang, TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the Clang compiler toolchain, however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as GNU Autotools, CMake, Meson, Zig's build toolchain among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, meta-programming and structural components of a C code base; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS|open source]] code bases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995-2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial,<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref> many attribute issues regarding C to fragmentation and portability issues,<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref> lack of type safety and primitive resource access checks,<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref> poor administration on part of the C Language Working Group,<ref>https://cor3ntin.github.io/posts/c/</ref> and overall worsening over time.<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref> e59d8e574ea95b0a9818a39144cc5177d6e2e81a 2857 2838 2025-07-23T18:59:16Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: 1970's → 1970s, 1995-2024 → 1995–2024 wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970s, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at Bell Labs, and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and pre-processors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include GNU GCC, Clang, TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the Clang compiler toolchain, however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as GNU Autotools, CMake, Meson, Zig's build toolchain among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, meta-programming and structural components of a C code base; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS|open source]] code bases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995–2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial,<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref> many attribute issues regarding C to fragmentation and portability issues,<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref> lack of type safety and primitive resource access checks,<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref> poor administration on part of the C Language Working Group,<ref>https://cor3ntin.github.io/posts/c/</ref> and overall worsening over time.<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref> 64135f2989f4d0ff7f59ddfed0175b4b088b07a9 2 3 2839 2734 2025-07-22T09:26:53Z Amadaluzia 52 Add some more socials wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <vector> #include <print> // Compile with C++23 or above. This will not work otherwise. struct SocialPair { std::string service, username; }; struct AboutMe { std::string name, description; std::vector<SocialPair> socials; }; int main(void) { struct AboutMe amadaluzia { .name = "Artur Manuel", .description { "I live in the UK and the internet as a background character in many\n" "free software communities (for example: you may find me on some\n" "mailing list) but I also contribute, most notably in nixpkgs.\n" "I do have other interests, such as gym, walking and photography, as\n" "well as speedrunning, filming and revising for english/maths among\n" "other things.\n" }, .socials { {"XMPP", "amadaluzia@xmpp.earth"}, {"Email", "amad@atl.tools"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Libera.Chat", "amadaluzia"}, {"Discord", "amadaluzia"}, {"Revolt", "amadaluzia#3242"}, {"Matrix (alt)", "@amadaluzia:pub.solar"}, {"Email (alt)", "amadaluzia@tutanota.com"}, }, }; std::println("Hello, I am {}.", amadaluzia.name); std::println("{}", amadaluzia.description); std::println("You may find me on the following platforms:"); for (auto const &[service, username] : amadaluzia.socials) std::println("{} on {}", username, service); return 0; }</syntaxhighlight> ed8e085d9720afc07ad69d4322afa0ddbfb70a56 2840 2839 2025-07-22T09:27:30Z Amadaluzia 52 reordered socials wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <vector> #include <print> // Compile with C++23 or above. This will not work otherwise. struct SocialPair { std::string service, username; }; struct AboutMe { std::string name, description; std::vector<SocialPair> socials; }; int main(void) { struct AboutMe amadaluzia { .name = "Artur Manuel", .description { "I live in the UK and the internet as a background character in many\n" "free software communities (for example: you may find me on some\n" "mailing list) but I also contribute, most notably in nixpkgs.\n" "I do have other interests, such as gym, walking and photography, as\n" "well as speedrunning, filming and revising for english/maths among\n" "other things.\n" }, .socials { {"Email", "amad@atl.tools"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Libera.Chat", "amadaluzia"}, {"Discord", "amadaluzia"}, {"XMPP", "amadaluzia@xmpp.earth"}, {"Revolt", "amadaluzia#3242"}, {"Matrix (alt)", "@amadaluzia:pub.solar"}, {"Email (alt)", "amadaluzia@tutanota.com"}, }, }; std::println("Hello, I am {}.", amadaluzia.name); std::println("{}", amadaluzia.description); std::println("You may find me on the following platforms:"); for (auto const &[service, username] : amadaluzia.socials) std::println("{} on {}", username, service); return 0; }</syntaxhighlight> 0a5abdfb5a47742ca352649d38f74a5d7aa4b6e2 0 248 2841 2605 2025-07-22T16:58:38Z Imnotgoodatnames 121 Fixed grammar mistakes, slightly reformatted some sentences to sound better, removed the "Introduction" heading since it was kind of pointless. wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu Logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[GNOME]], [[Unity]] | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu is a highly popular [[Linux Distributions|Linux distribution]] derived from [[Debian]] and developed by Canonical for the commercial market. The first version of Ubuntu was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS version receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubuntu receive 9 months of support.<ref>https://ubuntu.com/about/release-cycle Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> Ubuntu can be run locally, on a cloud, or in a [[Virtual Machine|VM]]. Ubuntu comes packaged with basic GNOME utilities as default and additionally from Ubuntu Software (formally Ubuntu Software Centre) and from APT, Ubuntu's default package manager. <references /> [[Category:Linux Distributions]] e1218394df855728649c9c9aa11d0d8da40d190e 2842 2841 2025-07-23T09:05:14Z Madonuko 140 fix weird space at the start of the article wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu Logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[GNOME]], [[Unity]] | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu is a highly popular [[Linux Distributions|Linux distribution]] derived from [[Debian]] and developed by Canonical for the commercial market. The first version of Ubuntu was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS version receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubuntu receive 9 months of support.<ref>https://ubuntu.com/about/release-cycle Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> Ubuntu can be run locally, on a cloud, or in a [[Virtual Machine|VM]]. Ubuntu comes packaged with basic GNOME utilities as default and additionally from Ubuntu Software (formally Ubuntu Software Centre) and from APT, Ubuntu's default package manager. <references /> [[Category:Linux Distributions]] 052183e330de9b019a3075c1cf6247bf5eafbe0b 0 174 2845 2519 2025-07-23T11:35:17Z Imnotgoodatnames 121 Changed the definition slightly to be more specific, removed mostly unrelated sentence, added citation. wikitext text/x-wiki {{Cleanup|Incomplete page}}[[File:Debian-Installer 10 Tasksel.svg|alt=Debian TUI installer|thumb|Debian 10 installation, which uses a TUI installer]] A '''TUI''' (Terminal User Interface or Text User Interface) generally refers to a pseudo-graphical interface in a virtual terminal environment - this means that all of its content is rendered solely using text including letters and other unique characters to resemble a graphical interface. [[Category:Terminology]] 58b3f82e44a916ff7bb65c5094f31c8a277a24a7 0 317 2849 2368 2025-07-23T18:27:17Z Lost 176 Improved the summary. wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm]</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and [[Musl]] variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses runit as its init system, offering: * Simple service management * Clean daemon supervision * Fast boot times {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] [[Category:Linux Distributions]] 9cde967a6277e5299a8c08dc531b5a6fb5b19c27 0 214 2850 2764 2025-07-23T18:31:06Z Ow0cast 249 cleanup | frameless in infobox wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Tux | image = [[File:Tux.svg|frameless|size=200px]] | caption = Tux! }} '''Tux''' is the official mascot of [[Linux]], designed by Larry Ewing.<ref>https://web.archive.org/web/20040401161253/http://www.linux.org/info/logos.html</ref> Tux was created for the Linux 2.0 logo competition.<ref>https://web.archive.org/web/20040407092622/http://www.cs.earlham.edu/~jeremiah/linux-pix/linux-logo.html</ref><references /> [[Category:Mascots]] 900bac64d2a20ae1ee390750b92c9dd92d7887a4 0 257 2852 2611 2025-07-23T18:54:46Z Ow0cast 249 cleanup | semi-auto, typos fixed: etc) → etc.), it's own → its own wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=[[C++]]|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window managers that aim for pure eye candy with nice animations, smooth looks and its own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has its own wallpaper software called hyprpaper which is considered to be well optimized. === Features === There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc.) [[Category:Wayland_Compositors]] 355f5d1c0e5237979e10bdab208cc28a13e14fe0 0 480 2853 2067 2025-07-23T18:56:14Z Ow0cast 249 /* History */ cleanup | semi-auto, typos fixed: November 16, 2024 → November 16, 2024, (3), it's → its wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}} [[File:Oreon10-2502.png|thumb|Oreon 10 Core (Build 2502) running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>https://oreonproject.org/</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>https://git.oreonproject.org/rpms</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>https://boostyconnect.com/oreon-lime-r1-lifecycle/</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>https://oreonproject.org/oreon-lime-r2-support-timeline/</ref><ref>https://oreonproject.org/oreon-lime-r2/</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/</ref> and other well-known sources. In October 2024, Oreon celebrated its 1st anniversary on November 16, 2024, and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69</ref> Oreon 10 released to the public on December 12, 2024, shipping with KDE Plasma 6 and Linux 6.11<ref>https://forums.oreonproject.org/t/oreon-10-officially-released/98</ref> but was upgraded to 6.12 a few days later. A new update to Oreon 10 has been released on February 12, 2025, under the name "Build 2502." This update brought a few bug fixes along with some planned features for later such as Apple M-series Mac support.<ref>https://forums.oreonproject.org/t/oreon-10-build-2502-has-officially-released/150</ref> <references /> [[Category:Linux Distributions]] e724c0ebe025a57fb0f74877cb217950171344f3 0 643 2854 2369 2025-07-23T18:56:28Z Ow0cast 249 /* Usage<ref>https://github.com/void-linux/xbps?tab=readme-ov-file#examples</ref> */ cleanup | semi-auto, typos fixed: it's → its wikitext text/x-wiki {{SoftwareInfobox |title = XBPS |releasestatus = Maintained |lastrelease = 0.59.2, 2023-08-18 |firstrelease = 0.1beta1, 2009-08-17 |languages = [[C]] |developers = [[Void Linux]] |website = [https://github.com/void-linux/xbps github.com/void-linux/xbps] }} == Intro == The ''X Binary Package System'' (XBPS) is developed by the maintainers of [[Void Linux]] and is the package manager for their distribution. It was built from scratch, with the goals of speed, ease of use while being feature rich and portable. It is fully compatible with POSIX, SUSv2 and C99 standards<ref>https://github.com/void-linux/xbps#xbps</ref>, and is released under the BSD 2-Clause (Simplified) license ([https://spdx.org/licenses/BSD-2-Clause.html SPDX: BSD-2-Clause]). == Tools == XBPS is comprised of a number of utilities that provide different functionality, the ''core'' utility programs are as follows (not a complete list): {| class="wikitable" !<u>Name</u> !<u>Function</u> |- |xbps-create |Creating binary packages |- |xbps-dgraph |Generating graphs for tools like [https://graphviz.org GraphViz] |- |xbps-install |Installing and updating packages |- |xbps-pkgdb |Reporting and fixing issues with the package database |- |xbps-query |Querying package and repository information |- |xbps-reconfigure |Configuration of installed package (e.g., the system C library or Linux kernel) |- |xbps-remove |Removing packages |- |xbps-rindex |Handling local package repositories |} == Usage<ref>https://github.com/void-linux/xbps?tab=readme-ov-file#examples</ref> == {| class="wikitable" !<u>Command</u> !<u>Description</u> |- |<code>xbps-install -Su</code> |Synchronize with repositories and apply all available updates |- |<code>xbps-query -Rs <name></code> |Search through repository packages using the given name |- |<code>xbps-install <package></code> |Install a package by name |- |<code>xbps-remove -R <package></code> |Remove a package by name; along with its dependent packages which are no longer needed by the system |- |<code>xbps-query -Rf <package></code> |List files owned by a package |- |<code>xbps-query -Ro /usr/bin/ls</code> |Find the package(s) that own/provide a file path, (e.g., the 'ls' command) |- |<code>xbps-reconfigure -f glibc-locales</code> |Regenerate your locale(s) when using a GLIBC based system<ref>https://man.voidlinux.org/xbps-reconfigure</ref> |} 71dc1670811c9ac9fbde42aed9a3b05d491a88b3 0 250 2855 2641 2025-07-23T18:57:09Z Ow0cast 249 /* Ana/Miniconda Setup */ cleanup | semi-auto, typos fixed: Github → GitHub wikitext text/x-wiki {{Cleanup|Instructions need to be split onto their own page under the Guides namespace}}{{Cleanup|Incomplete page}}[[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. == Ana/Miniconda Setup == While not required, it is heavily recommended to use ''conda'' to manage Python libraries required by various machine learning and artificial intelligence projects from places like GitHub and Hugging Face. Conda exists as a distinct virtual environment separate from the native distribution's Python packages. Users may specify version number and install additional plugins as well as packages within an environment utilizing conda. It is recommended to read the Linux setup for Miniconda on their [https://www.anaconda.com/docs/getting-started/miniconda/install#linux official website]. The install for Miniconda is very unorthodox compared to installing other packages on a Linux system - be mindful. == Stable Diffusion Setup - WebUI (Forge) == [[File:Cat.png|thumb|A cat generated using FLUX.1 [schnell].]] According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> Stable Diffusion WebUI Forge is a version of Stable Diffusion WebUI that offers additional support for FLUX.1 [dev] and FLUX.1 [schnell] models. For some users, using the Forge version may result in greater stability using FLUX as opposed to the vanilla version. Simply clone the Forge repository:<syntaxhighlight lang="bash"> git clone https://github.com/lllyasviel/stable-diffusion-webui-forge/issues </syntaxhighlight>...install required pip packages:<syntaxhighlight lang="bash"> pip3 install -r requirements.txt </syntaxhighlight>...and run the program:<syntaxhighlight lang="bash"> python3 launch.py </syntaxhighlight> ==== Extra notes ==== ===== Run options/flags ===== It is advisory to set additional launch parameters for better performance, e.g. using '''xformers''' for optimization or to specify a certain directory where models are stored. You can place these in a separate xxx.sh file to run instead of having to copy-and-paste large strings - here is an example:<syntaxhighlight lang="bash"> python3 launch.py --listen --xformers --enable-insecure-extension-access --cuda-malloc --port 7860 --vae-dir=/run/media/jennaannilyn/Pikmin3/models/vae --ckpt-dir=/run/media/jennaannilyn/Pikmin3/AI/ --lora-dir=/run/media/jennaannilyn/Pikmin3/AI/models/loras --no-half-vae </syntaxhighlight> === Installing and using Ollama on Linux === [[File:Ollama.png|thumb|Ollama says hi to ATL.]] According to Ollama's main page, Ollama is used to run open-source/open-weight, locally hosted Large Language Models. == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU, c'''onsidering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> ==== The Deiteris Fork ==== Some users may prefer Deiteris's version, which may offer extra precision and performance for more advanced users. The process is almost identical, except that you must clone his fork:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>...while consequently running a different Python command:<syntaxhighlight lang="bash"> python3 ./main.py </syntaxhighlight> [[Category:Guides]] f1575251f8589e5c89b8fc9c7fb0508c8c81d2b0 0 516 2856 2472 2025-07-23T18:57:44Z Ow0cast 249 cleanup | semi-auto, typos fixed: Here’s → Here's, ’s → 's wikitext text/x-wiki {{Cleanup|Instructions should be seperated into its own Guide page}} {{Needs_Citations}} == Understanding Systemd == Systemd is an init system and service manager used by many modern [[Linux Distributions|Linux distributions]]. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here's how Systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': Systemd provides a unified system for managing services, devices, logs, and even network interfaces. * '''Dependency Management''': Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': Systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in Systemd == Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit's dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''Systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''Systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''Systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential Systemd Commands == Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash">systemctl start service-name</syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash">systemctl stop service-name</syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash">systemctl restart service-name</syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash">systemctl enable service-name</syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash">systemctl disable service-name</syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the `/lib/systemd/system/` directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there. * Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. '''Runtime Directory''' The `/run/systemd/system/` directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File '''sudo nano /etc/systemd/system/daily-script.service''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File '''sudo nano /etc/systemd/system/daily-script.timer''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer '''sudo systemctl enable daily-script.timer''' '''sudo systemctl start daily-script.timer''' 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: '''systemctl list-timers''' This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With OnCalendar, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from `/lib/systemd/system/` to `/etc/systemd/system/` and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with `.d`. Example: To modify `dummy.service`, create a folder named `dummy.service.d` in `/etc/systemd/system/`. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a `.conf` file to specify your changes. Example: `/etc/systemd/system/dummy.service.d/custom.conf`. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. /etc/systemd/system/ (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. /run/systemd/system/ (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. /lib/systemd/system/ (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. '''systemctl status service-name''' * Displays the status of a specific service, including whether it's running and any associated error messages. 2. '''journalctl -u service-name''' * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. '''systemctl list-units --failed''' * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. '''systemctl daemon-reload''' * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. ef2a80d07b1dd82e93eb6920b65c65a162109207 0 668 2858 2762 2025-07-23T18:59:58Z Ow0cast 249 cleanup | semi-auto, typos fixed: 10-15 → 10–15, … → ... wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''.’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref> == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor [[ed]] (1971) and the even earlier [[qed]] (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command.<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref> sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; ...} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to [[EOF]]. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10–15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] 78f6769aa23886b309dcdf32000a7d1d019437d5 0 198 2859 2623 2025-07-23T19:00:35Z Ow0cast 249 cleanup | semi-auto, typos fixed: Linux based → Linux-based, a Arch-Based → an Arch-Based wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AIX]] |A series of Unix-Based Operating systems for Power servers. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} [[Category:Linux Distributions]] b79dc6e265d3192909240e12d0786ebfc3901529 0 299 2860 2794 2025-07-23T19:00:48Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: on July 1996 → in July 1996, widely- → widely wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a [[UNIX|Unix]]-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released in July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 7d19727520c0a60e0bec619e4d9487b755a5ab9a 0 349 2861 1469 2025-07-23T19:01:08Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: a OS. → an OS. (2) wikitext text/x-wiki In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is required to enable optimal use of an OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor'''<ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref> of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in an operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, etc. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |runit |February 10, 2004 |September 29, 2024 |↓ |Gerrit Pape |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS.<references /> [[Category:Terminology]] 51540b70cc990c8aeb92f831116724e80ae8ee29 0 623 2862 2693 2025-07-23T19:01:16Z Ow0cast 249 cleanup | semi-auto, typos fixed: ’s → 's (2) wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=EndeavourOS|image=[[File:EndeavourOS Logo.svg|Thumb]]|caption=The Endeavour OS logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, aArch64|website=[https://endeavouros.com endeavouros.org]}}'''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">https://endeavouros.com/</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>https://endeavouros.com/about-us/</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning Arch Linux fundamentals. === Installation === EndeavourOS provides an ISO with the Calamares installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with Arch Linux, meaning it uses Arch's official repositories directly and adheres closely to Arch's philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * AUR Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate AUR package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * Pacman Compatibility: Fully compatible with Arch's pacman package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for Arch Linux are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla Arch, or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the AUR, as well as EndeavourOS-specific themes and utilities.<ref>https://repo.c48.uk/endeavouros/repo/endeavouros/</ref> This is simply a pacman repository that can simply be added to any Arch Linux system if desired. cddd74844d77ccbe7a5a68b9839b437094f0f082 0 677 2864 2835 2025-07-23T19:02:04Z Ow0cast 249 cleanup | semi-auto, typos fixed: it's → its, it's own → its own wikitext text/x-wiki Flatpak is a universal packaging system and runtime for installing packages separate from the system packages. Mainly meant for desktop applications, Flatpak allows application developers to distribute packages without needing to worry about distro compatibility because Flatpak installs its own runtime dependencies. It claims to improve security through sandboxing providing the user the ability to give or revoke permissions for a given application. Flatpak is installed by default on many distributions and it's main distribution platform is Flathub. == Installation == Flatpak comes preinstalled on many distributions such as Linux Mint and Fedora but can be installed through most distro's package repositories if not present. ==== KDE Discover ==== KDE Discover includes the ability to install Flatpak and enable Flathub through its graphical user interface. Go to the setting tab and install the Flatpak backend then restart Discover then go back to the settings and enable Flathub. ==== CLI Install on Ubuntu ==== To install Flatpak from the CLI run:<syntaxhighlight lang="bash"> sudo apt install flatpak </syntaxhighlight>To enable Flathub from the CLI run:<syntaxhighlight lang="bash"> flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo </syntaxhighlight>If you make use of GNOME Software you can install the integration plugin:<syntaxhighlight lang="bash"> sudo apt install gnome-software-plugin-flatpak </syntaxhighlight>For the KDE Discover plugin run:<syntaxhighlight lang="bash"> sudo apt install plasma-discover-backend-flatpak </syntaxhighlight>For other distros read the guides on [https://flathub.org/setup Flathub.org]. == Compatibility == Flatpak allows improved package compatibility through its use of its own runtime dependencies. Packages can run through Flatpak where it might not be possible to run on natively such as: * Applications that require a newer version of glibc than whats available on an stable release distro such as Rocky Linux 8. * Applications that depend on glibc such as Steam running on a distro using musl like Alpine Linux. * Multilib packages such as Steam or Wine on distros without multilib support such as CentOS Stream 10. == Sandboxing == Package permissions can be managed by the user through a graphical user interface with Flatseal which can be installed as a Flatpak. == Flathub Package Verification == Flathub has a package verification system that allows packages maintained by the official developers to have a verification tick.<ref>[https://docs.flathub.org/docs/for-app-authors/verification Verification | Flathub Documentation], Flathub Team, 2025 (Accessed: 2025-06-22)</ref> This has lead to some confusion where verification is mistaken for package safety. Linux Mint hides unverified Flatpaks from Software Manager by default Starting in version 22.<ref>[https://www.omgubuntu.co.uk/2024/06/linux-mint-will-hide-unverified-flatpaks Linux Mint Will Hide Unverified Flatpaks in Software Manager - OMG! Ubuntu], Joey Sneddon, 2024 (Accessed: 2025-06-22)</ref> d8784439143062298c8ccb30ab78e2bbd834bf1b 0 223 2865 2031 2025-07-23T19:02:39Z Ow0cast 249 /* Distrohopping */ cleanup | semi-auto, typos fixed: Github → GitHub, eg. → e.g. (7) wikitext text/x-wiki {{Needs Citations}} == Distrohopping == Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (e.g. FSF approved distribution) * Ecosystem or Tooling (e.g. libc, [[Package Manager|package manager]], coreutils, [[Init System|init system]]) * Experimentation * Customization ... and many more. This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (e.g. Debianisms, [[Package Manager|package managers]], init systems) * Opinionated design philosophies (e.g. Nix, Guix, Fedora Atomic) * Additional configuration needs (e.g. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (e.g. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (e.g. Liberapay, GitHub sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] dbafe9145b2552c36d6d45d9d9e4c25bc35622b3 0 558 2866 1851 2025-07-23T19:03:05Z Ow0cast 249 cleanup | semi-auto, typos fixed: December of 2022 → December 2022, an unique → a unique wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[C]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }}Rust, the programming language, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called "garbage collecting," where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety|# Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[Rust#Object-Orientated Programming in Rust|# Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├─src ; Contain all code for project | ├──main.rs ; Code is executed here ├─Cargo.toml ; Dependencies file ├─git.ignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!") } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { let var_name: i32 = 64; let mut another_var: i32 = 86; another_var = 128; // let declares a new variable, i32 is the type of the variable // but is not requred, then the value is given. // All variables end with a ";" } </syntaxhighlight>Using <code>let</code> defines a new variable. You are able to label the variable however you like; but, it is a good idea to give them simple and easy names for sake of other programmers and yourself. If you need to specify the type of value a variable is, you can write out <code>[var_name]: [type]</code> to declare a type, to see all types, see [[Rust#Variable Types|# Variable Types]]. By default, any variable defined is an '''immutable''' but using the <code>mut</code> term enables the variable to mutable, influenced by '''functional programming'''. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" line="1"> struct Values { Value1: bool, Value2: i32, Value3: String, // Value 4..., Value 5... } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: Values = Values { Value1: true, Value2: 64, Value3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { Length: i32, Width: i32, Height: i32 } // vvvvvv Cube implemented here vvvvvv impl Cube { fn Area(&self) -> i32 { self.Length * self.Width * self.Height // This returns the Cube's Volume } } fn main() { let RubiksCube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's Volume: {}", RubiksCube.Area()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an Area finder function within the <code>impl Cube</code> scope. We are able to use the <code>Area()</code> function on any Variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses "borrowing"; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing], Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> [[Category:Programming Languages]] 61ef61e91759277e19f2cd479edd285fe9a5959a 0 344 2867 2505 2025-07-23T19:03:40Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: Etc) → etc.) wikitext text/x-wiki [[File:Kernel Layout.svg|thumb|How the Kernel interacts with the software and hardware.]] The Kernel is the core part of any [[Operating System|operating system]], including [[Linux]]. It's the fundamental layer between your [[hardware]] (like your CPU, memory, and GPU) and the [[:Category:Software|software]] you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, etc.). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2 Linus Torvalds 1991 (Retrieved 16th March 2025)</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel Kicksecure, Madaiden, Adrelanos 2023 (Retrieved 16th March 2025)</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. [[Category:Terminology]] 46a59bf099bfc797fde53042418f80036e5c2407 0 169 2869 2792 2025-07-23T19:05:14Z Ow0cast 249 /* List of Package Managers */ cleanup | semi-auto, typos fixed: github → GitHub, It's → Its wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) [[NixOS]]'s Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in [[Alpine Linux]] and [[Debian]]. Its GitHub repository is available [https://github.com/freebsd/pkg here] [[Category:Terminology]] 50aa4814c3245c2a5e09f7ff701ac4fc8ca669c9 0 626 2870 2834 2025-07-23T19:05:29Z Ow0cast 249 cleanup | semi-auto, typos fixed: ’s → 's (4) wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>https://manjaro.org/</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">https://distrowatch.com/table.php?distribution=manjaro</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>https://wiki.manjaro.org/index.php/Pamac</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>https://en.wikipedia.org/wiki/Manjaro</ref><ref>https://www.ubuntumint.com/manjaro-linux-history/</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>https://www.geeksforgeeks.org/how-to-install-manjaro-linux/</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch's base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch's, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro's custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch's upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>https://itsfoss.com/manjaro-vs-arch-linux/</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. a304fa5910d28195e13de42630f8e2ada69e601f 0 651 2871 2414 2025-07-23T19:06:01Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: ’s → 's, a OS → an OS wikitext text/x-wiki An operating system (OS) is a collection of [[software]] that manages a computer's [[hardware]] and [[applications]] by allocating resources, including memory, CPU, input/output devices and file storage.<ref>https://www.ibm.com/think/topics/operating-systems</ref> A user interacts with an operating system through a [[user interface]] (UI), which issues commands in a language the OS can understand. The UI can be either a [[graphical user interface]] (GUI) or a [[command-line interface]] (CLI). All computer systems need an OS to function. ce338300c8f7ff1a4aac40732b982292d942e9a8 0 177 2872 2625 2025-07-23T19:06:21Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: french → French wikitext text/x-wiki '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word, libre)<ref>https://en.wiktionary.org/wiki/libre Wikitionary. Wikimedia Foundation. Accessed June 4, 2024.</ref> and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> [[Category:Terminology]] 8d227d8ff3c049ecebf6144894bad50ee8ca090b 0 297 2873 2837 2025-07-23T19:06:43Z Ow0cast 249 cleanup | semi-auto, typos fixed: straight-forward → straightforward, ’s → 's (2) wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref> The core concept of multi-booting revolves around partitioning a computer's [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system's configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straightforward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Riot's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats.<references /> [[Category:Terminology]] eea3efd48df728681ac5964778555735597a9795 0 679 2874 2714 2025-07-23T19:07:06Z Ow0cast 249 /* History */ cleanup | semi-auto, typos fixed: ’s → 's (2) wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git's early design emphasized a distributed workflow similar to BitKeeper's but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like GitHub, which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. b5982a5fb7f6cb7c1fc157adcaad568f40ada6cc 0 418 2875 2793 2025-07-23T19:07:16Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: on November 1993 → in November 1993 wikitext text/x-wiki {{DistributionInfobox|architectures=arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox|caption=The FreeBSD logo|defaultdesktops=[[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]]|image=[[File:FreeBSD logo.png|200px|FreeBSD_logo]]|packagemanager=[[pkg]]|releasemodel=Stable|releasestatus=Maintained|title=FreeBSD|usagetype=Desktop, Firewall, Raspberry Pi, Server|website=[https://freebsd.org freebsd.org]}} FreeBSD is a [[UNIX|Unix]]-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released in November 1993.<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"] [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref> [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[Drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a [[kernel]] and [[drivers]], and relying on third-parties such as [[GNU]] for system [[:Category:Software|software]].<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref> The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports.<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref> The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']}<references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 9f206f09c1e6962a5cd3a64b23b3872c8418764c 2921 2875 2025-07-25T19:48:09Z Ow0cast 249 cleanup | semi-auto, removing duplicate links wikitext text/x-wiki {{DistributionInfobox|architectures=arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox|caption=The FreeBSD logo|defaultdesktops=[[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]]|image=[[File:FreeBSD logo.png|200px|FreeBSD_logo]]|packagemanager=[[pkg]]|releasemodel=Stable|releasestatus=Maintained|title=FreeBSD|usagetype=Desktop, Firewall, Raspberry Pi, Server|website=[https://freebsd.org freebsd.org]}} FreeBSD is a [[UNIX|Unix]]-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released in November 1993.<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"] [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref> [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[Drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a kernel and drivers, and relying on third-parties such as [[GNU]] for system [[:Category:Software|software]].<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref> The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports.<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref> The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']}<references /> [[Category:Misc Operating Systems]] [[Category:BSD]] e17ebe38dc366732b3d7c2de3ec59bc6e59a502c 0 716 2876 2751 2025-07-23T19:07:38Z Ow0cast 249 cleanup | semi-auto, typos fixed: ’s → 's (5) wikitext text/x-wiki = Hackintosh = == Definition == A '''Hackintosh''' is a non‑Apple computer configured to run Apple's '''macOS''', using unofficial methods to bypass hardware restrictions. Apple's software license restricts macOS usage to Apple‑branded machines<ref>{{Cite|title=Hackintosh|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == History == === Origins === The concept surfaced as users attempted to run Mac OS on non‑Apple hardware. It gained real momentum after Apple transitioned to Intel CPUs, making macOS compatible with x86 architecture<ref>{{Cite|title=Intel Macs usher in Hackintosh era|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === PC Installations === Following the release of Intel-based Macs in 2006, community developers modified the macOS kernel to disable hardware checks and employed EFI emulation tools like FakeEFI to boot macOS on PCs<ref>{{Cite|title=Hackintosh bootloaders|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === Bootloader Evolution === Bootloaders such as Chameleon and Clover evolved to improve reliability. In 2019, '''OpenCore''' was introduced, offering advanced features like support for macOS security features including System Integrity Protection and FileVault<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === Legal Developments === In 2008, Apple sued Psystar for selling unauthorized macOS clones. The court ruled Psystar violated Apple copyright and the DMCA, underscoring Apple's legal restrictions<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == Technical and Legal Status == Apple's EULA prohibits running macOS on non‑Apple hardware<ref>{{Cite|title=Hackintosh licensing|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. The DMCA's anti‑circumvention provisions create legal uncertainty in the U.S.<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. Apple's transition to ARM-based silicon (beginning in 2020) reduces future feasibility for x86 Hackintoshes<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref>. == Hardware Compatibility == According to the '''Dortania OpenCore Install Guide''': CPUs: modern Intel (up to Comet Lake) and patched AMD Ryzen series GPUs: Intel integrated graphics (Ivy Bridge to Ice Lake), AMD GCN/Vega/Navi; NVIDIA support is limited Networking: Broadcom-based Wi‑Fi and Ethernet adapters are preferred<ref>{{Cite|title=OpenCore hardware limits|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref> == Installation Guide == This guide provides a high-level overview. For full instructions, consult the [[OpenCore Install Guide]]. === 1. Prepare hardware === Confirm that your CPU, GPU, and network adapters match published compatibility lists. === 2. Obtain macOS installer === On a real Mac, download the desired macOS version (such as Sonoma or Sequoia) from the App Store. === 3. Build a USB installer === Partition a USB drive as HFS+ or APFS and use '''OpenCore''' along with official tools to create a bootable installer<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 4. Configure BIOS/UEFI === Disable Secure Boot, VT-d, CSM, Fast Boot. Enable UEFI and XHCI handoff<ref>{{Cite|title=OpenCore BIOS settings|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 5. Boot and install macOS === Boot from the USB installer, format the target storage as APFS, then proceed with the installation. === 6. Post-install configuration === Migrate the USB EFI folder to the internal EFI partition. Install necessary kexts (for audio, network), configure USB mapping, and finalize settings such as NVRAM, FileVault, and Sleep/Wake. == Resources == [https://dortania.github.io/OpenCore-Install-Guide/ Dortania OpenCore Install Guide] – full tutorial [https://en.wikipedia.org/wiki/Hackintosh Hackintosh – Wikipedia] [https://tonymacx86.com/ tonymacx86 forums] – hardware build guides and buyer lists == See also == [[macOS]] [[Virtualization]] [[BIOS]] == References == <references/> 23dcb53242adeb58cb12cd4d14fb7659e4e10b66 0 517 2877 2644 2025-07-23T19:08:04Z Ow0cast 249 /* Categories of System Calls */ cleanup | semi-auto, typos fixed: ’s → 's wikitext text/x-wiki {{Needs_Citations}} = What is a System Call? = A system call (syscall) is a mechanism that allows a program to interact with the [[Operating System|operating system]]. It acts as a bridge between the user space (where applications run) and the kernel space (where the operating system manages hardware and system resources). Programs use system calls to request services from the OS, such as managing files, processes, or hardware devices. For example, when you open a file, your application cannot directly access the hardware. Instead, it makes a system call (e.g., open()), which the OS handles to perform the requested task. Note that this is not a guide for ALL syscalls, but it is a guide to get you familiar enough with syscalls and strace. == Why Should You Learn About System Calls? == 1. Understanding How Programs Work: - System calls reveal how applications interact with the operating system to perform tasks like file handling, memory management, and networking. 2. Efficient Troubleshooting: - Knowing system calls can help diagnose performance issues or bugs by identifying which calls a program relies on. 3. Optimizing Software: - When developing programs, understanding system calls allows you to write efficient code by leveraging the right OS-level functions. 4. Security Awareness: - Many exploits and vulnerabilities target how system calls are used (or misused). Understanding them helps in writing secure code. 5. Kernel-Level Development: - If you're interested in low-level programming, such as operating system development or driver creation, system calls are fundamental. Basically, system calls are the foundation of how software and operating systems interact, making them essential knowledge for both beginner and advanced developers. == Categories of System Calls == System calls are grouped into five main categories: '''Process Control''' – Manage processes (create, terminate, etc.). '''File Management''' – Handle file operations (open, read, write, close). '''Device Management''' – Interact with hardware devices. '''Information Maintenance''' – Exchange information between the OS and programs. '''Communication''' – Enable processes to communicate. 1. '''Process Control''' * fork(): Creates a new process (child) that runs the same program as the parent. * exit(): Terminates the process and frees resources. * exec(): Replaces the current program in a process with a new one. 2. '''File Management''' * open(): Opens a file for reading or writing. * read(): Reads data from a file (multiple processes can read simultaneously). * write(): Writes data to a file (only one process can write at a time). * close(): Closes an open file. 3. '''Device Management''' * ioctl(): Performs device-specific operations not covered by standard calls (e.g., configuring hardware). 4. '''Information Maintenance''' * getpid(): Returns the process ID of the current process. * alarm(): Sets a timer to deliver a signal after a specified time. * sleep(): Pauses the process for a given time. 5. '''Communication''' * pipe(): Enables communication between processes via file descriptors. * shmget(): Allocates shared memory for process communication. * mmap(): Maps files or devices into a process's memory. === Why Use strace? === * Debug program behavior (e.g., "Why is this program failing?"). * Identify which files, devices, or network resources a program accesses. * Learn what system calls a program makes for educational purposes. 686b1fca8c05af14cc48cfa49c669e5d27bb8101 0 625 2878 2261 2025-07-23T19:08:36Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: ’s → 's wikitext text/x-wiki '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was developed by a team led by Peter "ptr1337" Jung to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2023. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Default browser: Cachy Browser (hardened Firefox fork). * Support for Btrfs snapshots with Limine bootloader. * Optional Firejail, DNSCrypt, AppArmor hardening. == Desktop Environments == CachyOS provides several preconfigured desktop environments: * [[Plasma|KDE Plasma]] (default) * [[GNOME]] * [[XFCE|Xfce]] * [[LXQt]] * [[Cutefish]] * [[Wayfire]] * [[i3]], [[bspwm]], [[Openbox]] Users can select their preferred environment during installation. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * [[Btrfs]] with snapshot support is the default filesystem. * Full UEFI, ZFS, and Secure Boot support. * Smooth installation experience designed for newcomers to Arch. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. * Limine bootloader for rollback support via Btrfs. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references> <ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos CachyOS Kernel Repository on GitHub]</ref> <ref name="official-docs">[https://wiki.cachyos.org Official CachyOS Wiki]</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos CachyOS on DistroWatch]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ BetaNews on CachyOS Performance]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks]</ref> </references> 8ccfeb8f024fb86f041ea6202c7d8a73273ee78c 0 707 2879 2684 2025-07-23T19:08:44Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: ’s → 's wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox |image=[[File:Grub-knoppix.jpg|thumb]] |caption=Grub Boot Menu |title=GRUB |releasestatus=Maintained |lastrelease=2.12, 2023-12-20 |languages=[[C]], [[Assembly]] |developers=GNU Project |website=[http://gnu.org/software/grub/ GNU Page] }}'''GRUB''' (short for '''GRand Unified Bootloader''') is a [[bootloader]] designed for [[UNIX|UNIX-like]] systems developed by the GNU Project. It provides the user with the option to choose between different [[Operating System|operating systems]] or [[kernel]] versions without having to use the [[BIOS]]. Originally developed by Erich Boleyn<ref>[http://www.uruk.org/grub/ GRUB -- GRand Unified Bootloader], Erich Boleyn (Accessed: 2025-07-01)</ref>, GRUB is now a part of the GNU project and comes with two versions, GRUB 0 (Also known as GRUB Legacy) and GRUB 2. Since GRUB Legacy is obsoleted and should no longer be used, this article mainly describes GRUB 2. GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU Hurd with the University of Utah's Mach 4 microkernel (now known as GNU Mach). Erich and Brian Ford designed the Multiboot Specification, because they were determined not to add to the large number of mutually-incompatible PC boot methods.<ref name=":0">https://www.gnu.org/software/grub/manual/grub/grub.html#Overview GNU website, 2025 (Imported 02.07.2025)</ref> Around 2002, Yoshinori K. Okuji started work on PUPA (Preliminary Universal Programming Architecture for GNU GRUB), aiming to rewrite the core of GRUB to make it cleaner, safer, more robust, and more powerful. PUPA was eventually renamed to GRUB 2, and the original version of GRUB was renamed to GRUB Legacy. <ref name=":0" /> GRUB contains support for multiple file systems ( [[FAT32]], [[ext4]], [[Btrfs]] or [[XFS]].) Both GRUB 2 and GRUB 0 systems support [[UEFI]] and BIOS-based systems. == See More == * [https://wiki.archlinux.org/title/Grub Grub on ArchWiki] b4576177677aa4c88a65d6e667c500709b607ef6 0 674 2880 2550 2025-07-23T19:08:59Z Ow0cast 249 /* History */ cleanup | semi-auto, typos fixed: ’s → 's (2) wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Searching for “PATTERNS” or “regex” in <code>grep --help</code> | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU grep: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, grep's creation stemmed from Thompson's need to analyse text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed]] text editor into a standalone tool. He named the tool ''grep'' because in ed, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into grep, which finds all lines with the text “error”. However, grep itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended [[regular expression]]s'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Examples == === Finding Python Function Calls === In a [[Python]] codebase, we can find all calls to functions under the <code>subprocess</code> module with <code>shell=True</code>: $ grep -r --include='*.py' -nHE 'subprocess\.\w+\([^)]*shell=True' ./driver.py:69: return subprocess.call("lspci | grep -q -i NVIDIA", shell=True) == 0 ./driver.py:202: return subprocess.call("lspci | grep -q -i Network | grep -q -i Broadcom", shell=True) == 0 ./driver.py:211: return subprocess.call("lspci | grep -q -i Bluetooth | grep -q -i Broadcom", shell=True) == 0 ./util.py:38: proc = subprocess.Popen(f"chroot {chroot} /tmp/stellar-payload.sh", shell=True) ./util.py:63: # proc = subprocess.Popen(payload, shell=True) ./util.py:66: proc = subprocess.Popen(f"pkexec {tmpfile}", shell=True) (This is run on the [https://github.com/Ultramarine-Linux/stellar/ Ultramarine stellar codebase]) We can breakdown the flags used in this example: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>--include='*.py'</code>: only examine Python files * <code>-n</code>: show line numbers * <code>-H</code>: show file name * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] We can divide the pattern <code>subprocess\.\w+\([^)]*shell=True</code> into many parts: # <code>subprocess</code> matches the string “subprocess” literally; # <code>\.</code> matches the full stop literally; # <code>\w+</code> matches word characters one or more times, where a word character (<code>\w</code>) is any letter, digit or underscore<ref>[https://www.regexroo.com/word-characters Understanding \w and Its Counterpart \W in Regex], RegexRoo.com, 2025 (Accessed: 2025-06-21)</ref>; # <code>\(</code> matches for an open parenthesis <code>(</code> literally; # <code>[^)]*</code> is an inverse character group and matches any characters that are not the closing parenthesis <code>)</code> zero or more times; and # <code>shell=True</code> matches the string “shell=True” literally. === Finding Code Files with TODOs and FIXMEs === We can list out code files that contains both the word “FIXME” and “TODO”. For a Rust project: $ grep -rlZ 'FIXME' --include='*.rs' . | xargs -0 grep -l 'TODO' ./src/pages/_15_installing.rs ./src/main.rs Flags: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>-l</code>: output matching files' names only * <code>-Z</code>: instead of a new line character, print out a null character after each filename * <code>--include='*.rs'</code>: only examine Rust files In this example, the first command outputs the filenames with null separates, then [[xargs]] is used to feed the filenames into the second grep command, which searches for “TODO”s in those files. === Extracting All Unique Public IPv4 Addresses from Log Files === We can extract all the unique IPv4 addresses from a directory of log files, but exclude any private IP addresses, such as <code>10.x.x.x</code> / <code>192.168.x.x</code>: <syntaxhighlight lang=sh> grep -rhoE '([0-9]{1,3}\.){3}[0-9]{1,3}' /path/to/logs | sort -u | grep -vE '^10\.|^192\.168\.' </syntaxhighlight> Flags: * <code>-r</code>: find files recursively * <code>-h</code>: suppress printing of filenames * <code>-o</code>: show only matching part of line * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] * <code>-v</code>: select non-matching lines For the first pattern: # <code>[0-9]</code> matches the digits (0 to 9 on the ASCII table includes all digits), and <code>{1,3}</code> specifies the length must be between 1 and 3; and # <code>([0-9]{1,3}\.){3}</code> matches exactly 3 times the above followed by a full stop. For the second pattern: # <code>^10\.</code> matches for lines starting with <code>10.</code>; # <code>^192\.168\.</code> matches for lines starting with <code>192.168.</code>; and # <code>|</code> (which indicates “or”) allows matching for the regex specified on the left or the right. Due to the invert flag (<code>-v</code>), if a line matches the second pattern, it is excluded, and other lines are printed instead. == Alternatives == Faster implementations of grep such as '''[[ripgrep]]''' (<code>rg</code>) and '''[[hypergrep]]''' (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU grep, and usually not pre-installed on most distributions. The '''<code>agrep</code>''' tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] ed94ff209d9c41f6bb37e918b2a6c0757413cdd6 0 430 2881 1505 2025-07-23T19:09:20Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: the the → the wikitext text/x-wiki [[File:Daemon.png|thumb|Daemon Flowchart]] Computers with the ability to multitask different processes at once contain a type of process labelled '''daemon''' process. These types of computer programs run in the background, which isn't controlled by a graphical interface or any user input, but rather, by the [[Init System|init system]], which also serves as the parent process<ref>Sep 2nd, 2020, ''Understanding daemons Unix'' by Aryaman Sharda: https://digitalbunker.dev/understanding-daemons-unix/</ref> of <u>most</u> daemons. For easier identification, processes' names end with the letter ''d'' to indicate the subjected process is a daemon. There are a few ways a daemon process can be made, all with different use cases: calling a <code>fork</code>and having the parent exit <ref>Chapter 13. Daemon Processes by Shichao's Notes: https://notes.shichao.io/apue/ch13/</ref> creates a daemon process by tricking the shell to thinking the command is finished, the child process obtains a new GID (Group Identifier) but is assigned a different PID (Process Identifier), another method calls a <code>umask</code> to set the file mode creation mask to a known value, this method is typically preferred when the process makes necessary files. There are more uncommon methods to achieve a daemon process, but are typically too complicated. === Terminology === The term "'''daemon'''" comes from MIT's Project MAC<ref>Take Our Word For It, Issue 129, Page 2: http://www.takeourword.com/TOW129/page2.html</ref> on the IBM 7094, labelled after scientist James Maxwell who imagined an interesting physics problem: He Imagined a container divided by a gate which separates the container into 2 equal parts, within the gate exists a hole big enough for one gas molecule, this gate was controlled by a ''daemon.'' Maxwell labelled it a "daemon" based off Greek Mythology where a daemon was a supernatural force that would work in the background. === Use-case(s) === ==== Unix-based/like Operating Systems ==== In such operating systems, daemons serve many functions for every part of the system and are very common. Although not required, many daemons have their parent be the init system, which possesses the PID of 1. Typically speaking, processes become daemons by being started by either the init system or a start up script. === Controlling a Daemon Process === ==== Using <code>systemctl</code>: ==== A user is able to adjust whether a daemon process is enabled or not using the <code>systemctl</code> command in their preferred shell, if the user wishes to start a daemon, they are able to use the <code>start</code> function, next to the service name in order to start it up. <syntaxhighlight lang="shell"> $ sudo systemctl start application.service # There is no output if a application begins succsesfully # If there is an error: Failed to start application.service: Unit application.service not found. # or Failed to start application.service: Access denied </syntaxhighlight>The user isn't required to add <code>*.service</code>, the system will automatically look for services that match. This command also works with <code>stop</code>, prompting the said service to terminate.<syntaxhighlight lang="shell"> $ sudo systemctl stop application.service # No Output if successful # Output on Error(s): Failed to stop application.service: Unit application.service not loaded. # or Failed to stop application.service: Access denied. </syntaxhighlight>If this is a process that is started by the init system at boot, it will begin again on a full reboot if it is enabled or when it is started manually. <references /> d4b8b46d1fc33f9f12a994a264ad7d759456c0bd 0 218 2882 2824 2025-07-23T19:09:45Z Ow0cast 249 cleanup | semi-auto, typos fixed: time consuming → time-consuming, ie. → i.e. , etc) → etc.) wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} == Introduction == [[Linux]] due to its generally lower system requirements than [[Windows]]<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> or [[macOS]] and a general absence of vendor-imposed hardware restrictions is frequently chosen for reviving and reusing older devices. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (i.e. keyrings, polkit, GTK, QT, etc.) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time-consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' [[Category:Guides]] <references /> bc1ad056204b25004bc63d051773f325bb92e503 0 447 2883 2075 2025-07-23T19:10:05Z Ow0cast 249 cleanup | semi-auto, typos fixed: enterpise → enterprise, ’s → 's wikitext text/x-wiki {{Needs Citations}} === Introduction === Self-hosting is a rewarding practice that allows you to reduce reliance on cloud services, giving you much greater control and privacy over the data you own. By self-hosting, the services you use, and by extension anything you store with those services, reside on your own hardware rather than third-party servers. Essentially, the “cloud” is just someone else's computer, often a large, multi-billion-dollar infrastructure. However, with self-hosting, you own the data on the devices you manage. === What is Self-Hosting? === Self-hosting often refers to the process of running and managing your own services on personal hardware such as a laptop, desktop, single-board computer, or even an enterprise-grade server. This means you can set up and operate services for yourself, your family, or others without depending on external cloud platforms. === What Can I Host? === There are numerous possibilities for self-hosting, depending on your needs. Some popular options include: * Email server * Password manager * Personal website * File hosting service * Media server * VPN (Virtual Private Network) === Do I Need Anything Special to Self-Host? === [[File:Homelab.jpg|thumb|Example of an enterprise grade homelab]] The requirements are minimal. You can self-host using almost any device, from an old, cheap laptop to a single-board computer like a Raspberry Pi. Some enthusiasts take this a step further and use second-hand enterprise equipment from real data center infrastructure to host their services. These setups are often referred to as “HomeLabs.” However, anything that can connect to the internet or your local area network can be sufficient. === The Challenges of Self-Hosting === Like everything in life, self-hosting has its challenges. When hosting services at home, you are responsible for maintaining and fixing any problems that arise. Unlike cloud services, which are typically plug-and-play, homelabs require regular maintenance to ensure stable operation. Below are some challenges many homelab users encounter. ==== Common Problems ==== * '''Electricity Usage''' - One of the main concerns with starting a homelab is power consumption. As your homelab grows, so will its electricity usage. Additionally, the services you run rely on your home's power grid, meaning power outages can affect your services. [[File:Speedtest.png|thumb|Example of a users internet speed.]] * '''Internet Speed''' - Not all internet connections are equal. When exposing services to the outside world, consider how much bandwidth they will consume. A slow connection or data caps can limit what you can host effectively. Residential internet plans might not support the load or violate fair use policies. Like the electricity usage, you are relying on the reliance your ISP provides. * '''Natural Disasters''' - Hosting services in areas prone to natural disasters poses risks. If a disaster damages your homelab, your data may be lost along with the equipment. * '''Vulnerabilities''' - Even with the latest software and hardware, vulnerabilities persist. Tools like Shodan.io scan for exposed services, potentially attracting malicious actors. Without sufficient protection, your services may be at risk. * '''Hardware Failures''' - Nothing lasts forever. Self-hosted services depend on your hardware, which will need maintenance and occasional replacement. Hard drives, in particular, are susceptible to failure over time. * '''Sound''' - Unlike a laptop or a single-board computer, enterprise equipment is not built to be quiet. It is designed to run cool and avoid failure, which often results in high-pitched fan noise due to large amounts of airflow. * '''Dust''' - Most homelabs are not housed in ventilated data centers, leading to dust accumulation, which can clog and damage equipment. * '''User Error''' - Mistakes happen. Deleting the wrong files, modifying incorrect configurations, or failing to double-check changes can lead to data loss or downtime. === Solutions === [[File:Ups uninterruptible power supply.jpg|thumb|An example of an (UPS) Uninterruptible Power Supply]] * '''Electricity Usage''' - Use an Uninterruptible Power Supply (UPS). A UPS acts as a battery backup and protects against power surges. If the power goes out, the UPS switches to battery mode to keep your equipment running. UPS devices can range from small 600W models to large 10kW units that can power enterprise equipment for hours. * '''Internet Speed''' - If your internet is slow or capped, consider upgrading to a better plan if available. Some ISPs offer small business plans for residential users, providing higher speeds, service agreements, and multiple external IP addresses. * '''Natural Disasters''' - Perform regular off-site backups. Store data in locations unaffected by the same natural disasters as your homelab to ensure redundancy. * '''Vulnerabilities''' - To mitigate vulnerabilities some examples include: ** Keep all software and hardware up to date. ** Change default ports for commonly scanned services. ** Install a firewall. ** Use a VPN to access services instead of exposing them directly to the internet. ** Use encrypted protocols and storage. [[File:raid failure.png|thumb|An example of a drive failing in a raid.]] *'''Hardware Failures''' - Practice the 3-2-1 backup strategy: ** Keep at least THREE copies of your data. ** Use at least TWO types of storage. ** Keep at least ONE copy off-site. * '''Sound''' - To mitigate noise, consider buying fanless equipment, as fans are the primary source of noise. Alternatively, place the equipment in a room that is not frequently used to minimize sound. Keep in mind that fanless equipment carries a risk of overheating. * '''Dust''' - Regularly clean your equipment and store it in well-ventilated areas. Use compressed air or vacuum cleaners to remove dust. * '''User Error''' - Double-check all changes, avoid running unfamiliar commands, and thoroughly understand what you are deploying. b19b3dded44275781ea07676805556ba2cb472b1 0 638 2884 2330 2025-07-23T19:10:11Z Ow0cast 249 /* Performance */ cleanup | semi-auto, typos fixed: i.e → i.e. wikitext text/x-wiki Ext4 is an advanced level of the ext3 [[filesystems]] which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular [[Linux Distributions|distributions]], however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. Information on how to do it can be found in [[Guides:Ext4]]. === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e. HDDs) ==== Changing the data mode ==== Ext4 provides three data modes<ref>[https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode Linux's ext4 documentation ]</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> You can change the data mode by setting the <code>data=...</code> mount option. ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost. The mount option <code>barrier=0</code> disables write barriers. Only disable this option if you know what you're doing. ==== Async journal commits and external journaling device ==== Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>[https://libre-consulting.com/posts/fs_ext4_external_journal/ ext4 external journal benchmarks.]</ref> ==== Enabling fscrypt support ==== fscrypt<ref>[https://github.com/google/fscrypt FSCrypt]</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. ==== Enabling fast_commit support ==== fast_commit <ref>[https://lwn.net/Articles/842385/ LWN's article on fast_commit.]</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by setting the <code>fast_commit</code> feature flag. <references /> e5767ab7e522570694f13abd4982ac208f7a27a5 0 240 2885 2705 2025-07-23T19:10:30Z Ow0cast 249 /* Multi Booting */ cleanup | semi-auto, typos fixed: refered → referred wikitext text/x-wiki {{Cleanup|Incomplete page}}{{Needs Citations}} == Introduction == When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your distribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most derivative distributions. ==== General Information ==== ===== Multi Booting ===== [[File:GRUB with ubuntu and windows vista.png|alt=A black and white grub menu, it contains entries for Ubuntu Linux and Windows Vista|thumb|GRUB, with entries for [[Ubuntu]] and Windows Vista, an example of ''dual booting.'']] [[Multi Booting]] (Or often referred to as 'Dual Booting') is the process of installing multiple [[Operating System|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completely removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to partition the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly recommended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi Booting]] page. ===== Finding Alternatives or Workarounds for Apps ===== Often there is at least one [[application]] missing on Linux or an app that is missing some features or is buggy so you'll find yourself looking for alternative options. There also sometimes is the issue that your distribution doesn't have an app but another distribution does have it. A good place to start when looking for alternatives is [https://alternativeto.net AlternativeTo] which is a crowdsourced site useful to find alternatives for almost any app. Other useful sites include [https://www.privacytools.io Privacy Tools] and [https://awesome-privacy.xyz Awesome Privacy] with a privacy focused list of apps. When looking for workarounds for apps not supported for your distribution you should first check [https://flathub.org Flathub] and [https://snapcraft.io Snapcraft] (Note that [[Snap|Snaps]] are known to have performance issues) if your app is available there as they offer support for most distributions. If a steam game lacks native Linux support try checking [https://www.protondb.com ProtonDB] if Valve's proton tool supports your game. [https://www.winehq.org Wine] is also an option to run Windows apps on Linux. ==== Moving between specific Operating Systems ==== ===== Moving to Linux from MacOS ===== ===== Moving to Linux from Windows ===== === General Information === [[Category:Guides]] 42d8785a75c4ac8382e4094d83d55a6d704e32ba 6 738 2886 2025-07-23T19:17:20Z Lost 176 wikitext text/x-wiki hmm maybe this might be my profile picture. 0ebd81ed86048c92dadb70bee7285577694cb01d 4 327 2887 2744 2025-07-23T19:19:14Z Ow0cast 249 /* top */ cleanup | semi-auto, typos fixed: statment → statement (:trol:) wikitext text/x-wiki test statement{{Cite|url=https://atl.wiki|title=ATL Wiki|author=Editors|year=2025}} =References= <references /> b5db4419a460b5f1f7ec9549bbcae51aef8ff24f 2916 2887 2025-07-25T16:50:52Z Atmois 13 wikitext text/x-wiki linux is cool.<ref>{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributors|year=2025}}</ref> why? because i said so =References= <references /> 006bb07bc72c9f73258f3b1aafd3bfbf371e5e9c 2917 2916 2025-07-25T16:53:09Z Atmois 13 fix? wikitext text/x-wiki linux is cool.{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributors|year=2025}} why? because i said so =References= <references /> 8200015f488489d2c8d84037796eb2dbdfa791d5 2919 2917 2025-07-25T16:55:59Z Atmois 13 test fix to template wikitext text/x-wiki linux is cool.<ref>{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributiors|year=2025}}</ref> why? because i said so =References= <references /> ab50d3c2eadc8c5c86d64590ff02ac169026a717 3 739 2888 2025-07-23T19:43:28Z Lost 176 Making my page. wikitext text/x-wiki Hello, I am a fellow GNU/Linux user probably the same as you. Hopefully my contributions help some people out. [[File:avatar.png|thumb|pfp]] b5b8b557e1eca3ead7e64fbae8bb9cb404c0478e 2889 2888 2025-07-23T19:44:46Z Lost 176 wikitext text/x-wiki Hello, I am a fellow GNU/Linux user probably the same as you. Hopefully my contributions help some people out. [[File:Profile_Picture.png|thumb|Profile Picture]] 9948845220f6a67fc8c2f7f44d316783f43b16e3 2 740 2890 2025-07-23T19:46:26Z Lost 176 Profile wikitext text/x-wiki Hello, I am a fellow GNU/Linux user probably the same as you. Hopefully my contributions help some people out. [[File:Profile_Picture.png|thumb|Profile Picture]] 9948845220f6a67fc8c2f7f44d316783f43b16e3 4 340 2891 2847 2025-07-24T11:43:46Z Atmois 13 Create notability standards wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the template below! You just need to replace the information with what is relevant to your claim, and it will auto generate it. Then you just need to add <code><nowiki><references /></nowiki></code> to the end of the page to generate the full list of references. DO NOT leave a white space either side of the citation template, it will break. <code><nowiki>{{Cite|title=Example Page|url=https://example.com|author=John Doe|year=1970 }}</nowiki></code> You can also add this by using the Insert button on the Visual Editor and selecting the Template, <code>Cite</code> and then filling out the relevant information in the interface. ''If you use the Visual Editor, we recommend adding the template after you have written the content around it for ease of use.'' A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. ; Pages Correctly Located and Categorised : Pages align with the [[Guides:Contributing|guides policy]], must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its [[ATL:Guidelines]], particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits.<references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 1de27874a35c1e20e72ca056a2d77044d8a8c781 2915 2891 2025-07-25T16:42:22Z Atmois 13 Update information about citation template wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. ; Pages Correctly Located and Categorised : Pages align with the [[Guides:Contributing|guides policy]], must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its [[ATL:Guidelines]], particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits.<references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 507779f7a351cea182f1c227c53960f0fb964f23 2925 2915 2025-07-26T12:02:09Z Atmois 13 Remove broken link wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. ; Pages Correctly Located and Categorised : Pages align with the [[Guides:Contributing|guides policy]], must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits.<references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] ca005f41b4be7aa0dc3217db3f2cd231f42f3195 8 750 2911 2025-07-25T15:04:48Z Atmois 13 Create cite-tool-definition.json json application/json [ { "name": "cite", "icon": "ref-cite-web", "template": "Cite" } ] 07759276b6464544407be79d0600641c0c357da5 8 751 2912 2025-07-25T15:17:47Z Atmois 13 Created page with "{ "web": "Cite" }" json application/json { "web": "Cite" } da6be6f4de9e8946008a5a72b9d5eeed3f999432 8 752 2913 2025-07-25T15:18:04Z Atmois 13 Created page with "Cite" wikitext text/x-wiki Cite 17fafd9717f13e737baf7e30b97440c1a93d6dc4 2914 2913 2025-07-25T15:23:22Z Atmois 13 Change description wikitext text/x-wiki Citation Tempalte 188221a98825c1c1b62fdd569fbe4e8c087390ff 2920 2914 2025-07-25T17:28:22Z Atmois 13 fix typo wikitext text/x-wiki Citation Template 7b74a5144ac3e8e464942df0f062bd0f613df7e9 10 631 2918 2743 2025-07-25T16:55:09Z Atmois 13 Remove auto <ref></ref> adding as the button does this for the user wikitext text/x-wiki <includeonly>{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} (Accessed: {{#time:F j, Y}})</includeonly><noinclude><templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata></noinclude> 685a369b2f6d2a51cfbb204790465000e3d71fd4 0 306 2922 2156 2025-07-25T19:53:21Z Ow0cast 249 cleanup | semi-auto, removing duplicate links wikitext text/x-wiki {{Work_In_Progress}} A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent GUI. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as dwm.  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm * [[Wayfire]] ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * i3 * [[Sway]] * [[SwayFx]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[dwl]] * qtile * [[Hyprland]] * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] ==== Scrollable Window Managers ==== Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[niri]] * [[PaperWM]] * [[karousel]] * [[papersway]] * [[hyprscroller]] * [[hyprslidr]] * [[PaperWM.spoon]] [[Category:Terminology]] [[Category:Window Management Systems]] e1a9e554bd8fe927207ee368d65a37eeb49fe223 0 663 2923 2686 2025-07-25T19:54:42Z Ow0cast 249 cleanup | semi-auto, removing duplicate links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terra.fyralabs.com terra.fyralabs.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora]] Linux and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terra.fyralabs.com/ Terra], Terra, 2024 (Accessed: 2025-06-19)</ref> Developed by Fyra Labs, it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://developer.fyralabs.com/terra/infrastructure How Terra Works], Fyra Labs, 2025 (Accessed: 2025-06-19)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://developer.fyralabs.com/terra/installing. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji], RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://developer.fyralabs.com/terra/autoupdate Automatic Updates - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases :: Fedora Docs], Fedora, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably Rust, Go, [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://developer.fyralabs.com/terra/policy Policy – Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> == See Also == * [https://terra.fyralabs.com Main Website] * [https://developer.fyralabs.com/terra Fyra Developer Documentations for Terra] * [https://github.com/terrapkg/packages Terra Sources] a23f94c73785a10575b7a67d97e6d2eda3c11827 0 433 2924 2811 2025-07-25T19:55:13Z Ow0cast 249 cleanup | semi-auto wikitext text/x-wiki {{Needs Citations}} A '''CLI''' (Command-Line Interface) is a text-based interaction model in which users type commands as text strings to interact with an operating system or a program through a computer. Unlike a [[TUI]], which relies upon a pseudo-graphical form made of characters, an interface that is purely a command-driven one usually would issue output in the form of lines of text upon receiving user instructions. [[File:Unix shell.png|thumb|A Unix shell command prompt, an example of a CLI]] CLIs are often preferred by power users, system administrators, and developers for their efficiency, scriptability, and precise control over system operations. Common examples include: * Unix/Linux shells (sh, bash, zsh, fish) * Windows Command Prompt * PowerShell * Python's REPL (Read-Eval-Print Loop) The main advantages of CLIs include: * Resource efficiency (minimal system requirements) * Automation capability through scripting * Remote system administration * Precise control over system operations * Speed of execution for experienced users While CLIs can have a steeper learning curve compared to GUIs (Graphical User Interfaces) or TUIs, they remain fundamental to modern computing, particularly in server administration, software development, and system maintenance. == History == [[File:Edwind.png|thumb|CLI text editor Ed in a GUI terminal emulator window]] Command-line interfaces emerged in the 1960s with teleprinters like the Teletype Model 33 ASR, which replaced punch cards as the primary means of computer interaction. Early operating systems like Unix and MS-DOS were primarily accessed through CLIs, establishing conventions that persist in modern computing. [[File:Command com.png|thumb|The MS-DOS command prompt]] == Common Usage == CLI environments typically follow a standard pattern where: * The system displays a prompt (e.g., "$" for Unix-like systems) * Users type commands followed by arguments or options * The system executes the command and displays the output * The process repeats with a new prompt [[Category:Terminology]] [[Category:User interfaces]] afd0df1e267c780f8ceb5836b41ca1a71332db91 0 753 2926 2025-07-26T12:06:29Z Atmois 13 Create redirect wikitext text/x-wiki #REDIRECT [[ATL:Privacy policy]] 8daa90aa5ef7f584dde8d208b7952878db59ceb0 8 196 2927 2597 2025-07-26T12:10:28Z Atmois 13 Remove auto generated reference list header javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://atl.wiki/ATL:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://umami.atl.wiki/script.js'; s.setAttribute('data-website-id', '21f384be-587d-4b00-8727-203d00c898d5'); document.head.appendChild(s); df22fc0d55dafa3da87c38473b5c87c26b87f125 4 646 2928 2386 2025-07-26T14:24:08Z Atmois 13 Fix typo wikitext text/x-wiki == '''<u>DO NOT share the link provided with anyone, including any staff members.</u>''' == To link your Discord and '''atl.wiki''' accounts in our [https://discord.gg/linux discord server], type <code>/verify</code> using '''''@atl.wiki'''''. You will receive a private link in your DM's, Then click the link, press '''Allow''', and return to Discord, if your '''atl.wiki''' account is at least '''3 days old''', and has met the '''minimum edit threshold''', you will automatically be given the '''''@Wiki Author''''' role, which comes with bonus perks in the Discord server such as boosted XP, extra permissions and exclusive chat access. You may need to wait up to an hour for the role to be given. If you do not receive it open a ticket with <code>/ticket</code> and ask for help. If you have met the requirements '''after''' initially verifying, run <code>/unverify</code> then go through the verification process again, this will refresh your role. To see if you meet the requirements, visit the [[Special:UserRights]] page, search your username, and see if you're an ''implicit member of "Autoconfirmed Users"''. This role is automatically given by the wiki to users who meet the criteria. 3c2e72e7391442eae45f305a26892fa8ea4ad966 828 609 2929 2770 2025-07-26T15:11:23Z Atmois 13 Update page link Scribunto text/plain local p = {} function p.stats() local siteStats = mw.site.stats local totalEdits = siteStats.edits local totalUsers = siteStats.users local function countPages(ns) return siteStats.pagesInNamespace(ns) or 0 end local pageCount = countPages(0) + countPages(3000) return string.format( "atl.wiki has [[Special:AllPages| %d pages]] consisting of [[Special:RecentChanges| %d edits]] from [[Special:ListUsers| %d users]]!", pageCount, totalEdits, totalUsers ) end return p 11795b6337fb18fa01bf599fa4394cf283c11ec0 0 622 2930 2504 2025-07-26T15:13:44Z Atmois 13 Remove dynamic page list wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a GUI or TUI. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> {| class="wikitable" |+ !Desktop Environment !Description |- |Budgie |The Budgie Desktop is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |Cinnamon |Cinnamon is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |Enlightenment |Enlightenment is a desktop environment and window manager for [[Linux]] and other [[Unix|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |GNOME |GNOME is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |MATE |MATE is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |Openbox |Openbox is a highly configurable and minimal desktop environment coded in C. |- |Plasma |KDE Plasma is a highly customizable and popular and is coded in C++ and [[QML]]. |- |Trinity Desktop Environment |Trinity Desktop Environment is an desktop environment forked from [[Plasma|KDE]] 3 coded in C. |- |XFCE |XFCE is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in C. |} f7cbf2fc4308585ddb84320080e47925b207e5ca 0 424 2931 2560 2025-07-26T16:50:01Z Atmois 13 Add references header wikitext text/x-wiki = AWK = AWK is a programming language focused primarily on textual data processing<ref>[https://www.gnu.org/software/gawk/manual/html_node/] Top (The GNU Awk User's Guide)</ref>, though it can be used for other general-purpose tasks. This page will focus primarily on GNU Awk, or GAWK/<code>gawk</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/], Although the language name is officially stylized AWK, GNU officially uses the stylization Awk. They also acknowledge that the language itself is spelled AWK.</ref>. == Basic Usage == One of the most basic ways to use AWK is in a pipe to filter columnar data. For example, <code>cat file.txt | awk '{ print $1 }'</code> will print the first (space-delimited) column of a given file. This can be generalized to the second, third, etc. columns using <code>$2</code>, <code>$3</code>, etc. respectively. AWK can also be ran with <code>awk 'program-here' input-file1 input-file2 ...</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/One_002dshot.html] One-shot (The GNU Awk User's Guide)</ref>, so the above example with <code>cat</code> could also be written as: <pre> awk '{ print $1 }' file.txt </pre>More usage examples can be found on the [https://www.gnu.org/software/gawk/manual/html_node/Command-Line.html GAWK manual page], as well as AWK's [https://www.gnu.org/software/gawk/manual/html_node/Options.html many command-line options]. == AWK as a Language == AWK can also be used as a programming language. AWK programs consist of a list of patterns followed by actions to perform for each of those patterns<ref>[https://www.gnu.org/software/gawk/manual/html_node/Getting-Started.html] Getting Started (The GNU Awk User's Guide)</ref>: <pre> pattern { action } pattern { action } ... </pre> === BEGIN and END === Two common patterns are <code>BEGIN</code> and <code>END</code>, which run the given action before and after any text is processed respectively. These are called the "startup" and "cleanup" actions<ref>[https://www.gnu.org/software/gawk/manual/html_node/Using-BEGIN_002fEND.html] Using BEGIN/END (The GNU Awk User's Guide)</ref>. For example, the following code will print "Hello, World!": <pre> awk 'BEGIN { print "Hello, World!" }' </pre> The following will accept input until an EOF (inputtable in many shells as Ctrl+D), then print "Hello, World!": <pre> awk 'END { print "Hello, World!" }' </pre> === Regex Pattern === AWK can also be used to run a command for every line that matches a given regular expression. The following example prints every line that contains "regex" (equivalent to <code>grep 'regex'</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Regexp-Usage.html] Regexp Usage (The GNU Awk User's Guide)</ref>:<syntaxhighlight lang="awk"> /regex/ { print } </syntaxhighlight>The <code>{ print }</code> is actually implicit, meaning it can also be written:<syntaxhighlight lang="awk"> /regex/ </syntaxhighlight>One can combine this with <code>$1</code>, <code>$2</code>, etc. to print the second column of every row containing a given string, for example:<syntaxhighlight lang="awk"> /regex/ { print $2 } </syntaxhighlight> === Operations === AWK can be used to perform operations seen in many other programming languages, such as addition (<code>+</code>), subtraction (<code>-</code>), multiplication (<code>*</code>), division (<code>/</code>), modulus (<code>%</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Arithmetic-Ops.html] Arithmetic Ops (The GNU Awk User's Guide)</ref>, variable assignment (<code>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Assignment-Ops.html] Assignment Ops (The GNU Awk User's Guide)</ref>, equality (<code>==</code>) and inequality checks (<code>!=</code>), and comparisons (<code><</code>, <code><=</code>, <code>></code>, <code>>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Comparison-Operators.html] Comparison Operators (The GNU Awk User's Guide)</ref>. === ARGC and ARGV === Like many other programming languages, AWK programs can parse command-line arguments. The <code>ARGC</code> and <code>ARGV</code> variables (among [https://www.gnu.org/software/gawk/manual/html_node/Built_002din-Variables.html many others]) store the count of the arguments and an array of the arguments respectively<ref>[https://www.gnu.org/software/gawk/manual/html_node/Auto_002dset.html#index-ARGC_002fARGV-variables] ARGC, ARGV - Auto-set (The GNU Awk User’s Guide)</ref>. == References == <references /> [[Category:Software]] [[Category:Programming Languages]] ae405cde2105294770c0504bc5e8f601593860a4 0 310 2932 2833 2025-07-26T16:50:24Z Atmois 13 Add references header wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Alpine Linux | image = [[File:alpinelinux-logo.svg|thumb]] | releasestatus = Maintained | releasemodel = Point or Rolling | packagemanager = [[apk]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[MATE]], [[LXQt]] | usagetype = Container, Embedded, Server, Desktop | architectures = amd64, aarch64, armel, armhf, i686, ppc64le, s390x, loongarch64 | website = [https://www.alpinelinux.org/ alpinelinux.org] }} Alpine Linux is a lightweight Linux distribution that aims to "small", "simple" and "secure".<ref name=":0">https://alpinelinux.org/about/</ref> It is one of the few distributions that do not use the GNU C Library or GNU coreutils by default. Alpine, by default, follows a point release update model while its edge repositories follow a rolling release model. Twice a year, typically on November and May, a new stable version is branched from edge and released.<ref>https://alpinelinux.org/releases/</ref> == Features == Alpine's main feature is its small size. Its minimal system requirements and ease of deployability makes it suitable for use in containers, embedded systems and other systems with very limited resources. All user-space binaries in Alpine are compiled as position-independent executables with stack-smashing protection for security reasons.<ref name=":0" /> Alpine comes preinstalled with configuration scripts which allow quick configuration and installation of the system.<ref>[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts]</ref> Alpine also offers a web-server based configuration tool named the Alpine Configuration Framework (ACF).<ref>https://wiki.alpinelinux.org/wiki/Alpine_Configuration_Framework_Design</ref> Alpine offers a "diskless installation"<ref>https://wiki.alpinelinux.org/wiki/Installation#Installation_Overview</ref>, allowing it to be installed to and be used from RAM. == Differences from other Linux Distributions == * Alpine uses musl as its standard C library. This compromises its support for some programs such as Electron based applications<ref>https://wiki.alpinelinux.org/wiki/APKBUILD_examples:JavaScript</ref> and the NVIDIA drivers.<ref>https://wiki.alpinelinux.org/wiki/NVIDIA</ref> * Alpine by default lacks the standard base utilities that other distributions come with such as GNU bash, coreutils, findutils, pciutils, usbutils, util-linux, udev. Instead of these, their BusyBox implementations are used. This is what makes Alpine so small in size, yet this also causes compatibility issues with many programs and scripts as their BusyBox implementations lack many features of their counterparts<ref>https://wiki.alpinelinux.org/wiki/How_to_get_regular_stuff_working</ref>. To solve these compatibility issues, the user can install the standard version of these programs as they wish. * Alpine does not use systemd. Instead, it uses BusyBox for its init process and OpenRC for service management.<ref>https://wiki.alpinelinux.org/wiki/OpenRC</ref> * Alpine uses its own package manager, the "Alpine Package Keeper" (apk).<ref>https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper</ref> * Alpine uses the LTS branch of the Linux kernel by default.<ref>https://github.com/alpinelinux/alpine-conf/blob/55ec2cf0504195ee60f68b21a29607302f8a15d0/setup-disk.in#L1489</ref> == References == c501c5c144b50f24cbec2e1dd604f6fea09298d0 0 2 2933 2700 2025-07-26T16:50:44Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |(Someone more experienced can fill) |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick pipewire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four kernels, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] 42754ba963e490a9d6c03b9286fc451218d0e506 0 228 2934 2009 2025-07-26T16:50:58Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}} The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. [[Package|Packages]] that enter the extra repository can be directly installed with [[pacman]].<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with AUR helpers. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, AUR helpers have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, [[pacman]] is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability. == References == <references /> [[Category:Terminology]] 7d7f31109028dcc82915af00865cb13ed86623f3 0 250 2935 2855 2025-07-26T16:51:14Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Instructions need to be split onto their own page under the Guides namespace}}{{Cleanup|Incomplete page}}[[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. == Ana/Miniconda Setup == While not required, it is heavily recommended to use ''conda'' to manage Python libraries required by various machine learning and artificial intelligence projects from places like GitHub and Hugging Face. Conda exists as a distinct virtual environment separate from the native distribution's Python packages. Users may specify version number and install additional plugins as well as packages within an environment utilizing conda. It is recommended to read the Linux setup for Miniconda on their [https://www.anaconda.com/docs/getting-started/miniconda/install#linux official website]. The install for Miniconda is very unorthodox compared to installing other packages on a Linux system - be mindful. == Stable Diffusion Setup - WebUI (Forge) == [[File:Cat.png|thumb|A cat generated using FLUX.1 [schnell].]] According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> Stable Diffusion WebUI Forge is a version of Stable Diffusion WebUI that offers additional support for FLUX.1 [dev] and FLUX.1 [schnell] models. For some users, using the Forge version may result in greater stability using FLUX as opposed to the vanilla version. Simply clone the Forge repository:<syntaxhighlight lang="bash"> git clone https://github.com/lllyasviel/stable-diffusion-webui-forge/issues </syntaxhighlight>...install required pip packages:<syntaxhighlight lang="bash"> pip3 install -r requirements.txt </syntaxhighlight>...and run the program:<syntaxhighlight lang="bash"> python3 launch.py </syntaxhighlight> ==== Extra notes ==== ===== Run options/flags ===== It is advisory to set additional launch parameters for better performance, e.g. using '''xformers''' for optimization or to specify a certain directory where models are stored. You can place these in a separate xxx.sh file to run instead of having to copy-and-paste large strings - here is an example:<syntaxhighlight lang="bash"> python3 launch.py --listen --xformers --enable-insecure-extension-access --cuda-malloc --port 7860 --vae-dir=/run/media/jennaannilyn/Pikmin3/models/vae --ckpt-dir=/run/media/jennaannilyn/Pikmin3/AI/ --lora-dir=/run/media/jennaannilyn/Pikmin3/AI/models/loras --no-half-vae </syntaxhighlight> === Installing and using Ollama on Linux === [[File:Ollama.png|thumb|Ollama says hi to ATL.]] According to Ollama's main page, Ollama is used to run open-source/open-weight, locally hosted Large Language Models. == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU, c'''onsidering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> ==== The Deiteris Fork ==== Some users may prefer Deiteris's version, which may offer extra precision and performance for more advanced users. The process is almost identical, except that you must clone his fork:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>...while consequently running a different Python command:<syntaxhighlight lang="bash"> python3 ./main.py </syntaxhighlight> == References == [[Category:Guides]] b9918df1eb69490230679b96d5a0156c60565674 0 656 2936 2713 2025-07-26T16:58:21Z Atmois 13 Add references header wikitext text/x-wiki {{DistributionInfobox |title=Batocera |image=[[file:Batocera-logo-art.png|frameless]] |caption=Batocera Logo |releasestatus=Maintained |releasemodel=Rolling Release |packagemanager=pacman |defaultdesktops=No Desktop |usagetype=placeholder |architectures=x86_64, Rpi4, Rpi5 |website=[https://batocera.org/ batocera.org] }} Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pi's and other micro computers. Batocera offers emulation cores for retro consoles and retro home computers. == References == 78f8d7de2f278116f8644afbe8cc27d5ee09501c 0 166 2937 2758 2025-07-26T16:58:41Z Atmois 13 Add references header wikitext text/x-wiki A term commonly used across any Linux community,<ref>[https://www.youtube.com/watch?v=LxuYnFD7brY TechOverTea] imported on 17th June 2025</ref> "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life.<ref>Merriam-Webster Dictionary. [https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of [[Linux]] and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system.<ref>[https://www.techtarget.com/searchsecurity/answer/How-can-we-detect-and-uninstall-bloatware "What is Bloatware?"] TechTarget.com ,Imported 17th June 2025</ref> == References == <references /> [[Category:Terminology]] e934b9e9330629fb258a220cf9fca93982dbf223 0 709 2938 2779 2025-07-26T16:58:58Z Atmois 13 Add references header wikitext text/x-wiki This article describes the general boot process of most Linux distributions.<ref>https://medium.com/@gangulysutapa96/6-stages-of-linux-boot-process-5ee84265d8a0 Medium.com, 2023 (Imported 02.07.25)</ref> While most Linux distributions integrates varying components, the basic steps remain the same. === BIOS === The BIOS (Basic Input/Output System) is the firmware that initializes hardware components and provides a basic set of services to the kernel.<ref>https://www.lenovo.com/gb/en/glossary/what-is-a-bios?srsltid=AfmBOopXGO9x6E-4ZTe5WNDbGEMlTYXBLk1ivYj5LXSQC8OTUAjEAASC Lenovo.com, 2025 (Imported 02.07.2025)</ref> It is obtained from the ROM and is responsible for loading the bootloader. Once the correct boot device is selected, the BIOS loads the boot sector, which is the first sector (512 bytes) of the boot device.<ref>https://neosmart.net/wiki/mbr-boot-process/ Neosmart.net, 2025 (Imported 02.07.2025)</ref> The boot sector contains the bootloader, which is responsible for loading the [[kernel]]. === Bootloader === The bootloader is responsible for loading the kernel into memory and starting the kernel. Common bootloaders include [[GRUB]], [[Syslinux]], [[Limine]], [[Systemd|systemd-boot]], [[rEFInd]], etc. Usually, the bootloader is stored separately from the kernel, in different [[partition]]s or even on a different device. It displays an interface, such as a text-based menu to select the kernel to boot. === Initramfs === The initramfs is a compressed filesystem that is loaded into memory during boot. It contains essential files and utilities required to mount the actual root [[filesystem]] and start the init process. The initramfs is typically created using [[mkinitcpio]] or [[dracut]]. === Kernel === The kernel is the core of the operating system and is responsible for managing hardware resources and providing a platform for user-space applications. It is responsible for initializing hardware, managing memory, and providing a virtual filesystem. It is loaded by the bootloader and starts the init process. === Init === The init process, which must be stored under <code>/sbin/init</code>, is responsible for initializing the system and starting the user-space applications. It is responsible for mounting the root filesystem, starting the necessary system services, and starting the graphical user interface. On most modern systems, this is [[systemd]]. Some older systems use [[sysvinit]] or [[upstart]]. === TTY === The [[TTY]] (Teletype) is a text-based interface that allows users to interact with the operating system. It is responsible for displaying text and accepting user input. It is typically used for logging in and running commands. It is also used for debugging and troubleshooting. The TTY is available even on modern systems and can be accessed through the {{Key press|Ctrl|Alt|F1}} to {{Key press|Ctrl|Alt|F6}} keys. === Display Manager === The [[Display Manager|display manager]] is responsible for managing the [[GUI|graphical user interface]].<ref>https://wiki.archlinux.org/title/Display_manager Arch wiki, 2025 (Imported 02.07.2025)</ref> On most modern systems, this is [[lightdm]], [[gdm]], or [[sddm]]. Once the user logs in, the display manager executes the [[Window Manager|window manager]] or [[Desktop Environments|desktop environment]] chosen by the user. == References == 0c723dd984d981421d6c6526ea0c3db1cf9d11aa 0 414 2939 2857 2025-07-26T16:59:31Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970s, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at Bell Labs, and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and pre-processors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include GNU GCC, Clang, TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the Clang compiler toolchain, however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as GNU Autotools, CMake, Meson, Zig's build toolchain among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, meta-programming and structural components of a C code base; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS|open source]] code bases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995–2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial,<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref> many attribute issues regarding C to fragmentation and portability issues,<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref> lack of type safety and primitive resource access checks,<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref> poor administration on part of the C Language Working Group,<ref>https://cor3ntin.github.io/posts/c/</ref> and overall worsening over time.<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref> == References == 1cc15a9f774effaafbab43ef19aa7b54d36d5ffc 0 429 2940 2026 2025-07-26T16:59:49Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "[[Portfiles]]," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> == References == [[Category:Linux Distributions]] e7e053fc8b0b417f30a963d59b5f6183f475c1d9 0 700 2941 2678 2025-07-26T17:00:36Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox|image=[[File:Calamares on Debian 10 screenshot.jpg|frameless]]|caption=Calamares Installer|title=Calamares|releasestatus=Maintained|lastrelease=3.3.14 (Feb 20, 2025)|languages=[[C++]], [[Python]], [[QML]]|developers=Adriaan de Groot|website=[https://calamares.io/ calamares.io]}}Calamares is a distribution-independent system installer, with an advanced partitioning feature for both manual and automated partitioning operations. Calamares is designed to be customizable by distribution maintainers without the need for cumbersome patching, thanks to third-party branding and external modules support.<ref>https://github.com/calamares/calamares Calamares Github, 2025 (27th June 2025)</ref> == References == <references /> [[Category:Software]] 7ce8cacdc6da783e44ede4591c21992d9d0c9d26 0 659 2942 2848 2025-07-26T17:00:49Z Atmois 13 Add references header wikitext text/x-wiki {{DistributionInfobox|title=ChromeOS|image=[[File:Chromium_Logo.svg|frameless]]|caption=ChromiumOs Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Portage]]|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website=[https://chromeos.google/ chromeos]}}ChromeOS (ChromiumOS) is a [[UNIX|Unix-Based]] [[Linux Distributions|Linux distribution]] designed and developed by Google in 2009. ChromeOS is completely open-source.<ref>http://source.chromium.org/chromiumos Official ChromeOS website, 2025 (imported 27th June 2025)</ref> == References == <references /> f70f7c9674d15c2e9a532a19cb61f8b5ca596a28 0 272 2943 2552 2025-07-26T17:01:51Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|The article does not reflect the latest information on dnf5}}{{Cleanup|is that <code>dnf</code>'s importance is described in a pretty biased way, and some parts of this page feels somewhat AI-generated.}}{{Needs Citations}}{{SoftwareInfobox | image = [[File:DNF Command Line Interface.png|frameless]] | caption = Invoking <code>sudo dnf upgrade</code> on a terminal with <code>dnf4</code> | title = DNF | releasestatus = Maintained | lastrelease = <code>dnf5</code> 5.2.13.1 (2025-04-25) | languages = [[C++]] | developers = [[Fedora]] and Red Hat, et al. | website = [https://github.com/rpm-software-management/dnf5/ github.com/rpm-software-management/dnf5] }} '''DNF''', short for ''Dandified YUM'', is a software package manager for Linux distributions such as [[Fedora]], [[CentOS]], and [[RHEL]] (Red Hat Enterprise Linux). It was designed to be a better version of the traditional [[YUM]] (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other [[RPM]]-based distributions. === Development of DNF5 === The development of DNF5, the next-generation Fedora package manager, began in early 2020 as a complete rewrite of the existing DNF4 codebase to address architectural and performance limitations:<ref>[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NWSURJRGZAIIMNZJT244DHDPOG2PBQXZ/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> <blockquote> We've managed to drop a lot of redundant code across the whole DNF stack in the past years, but we have reached a point when it's nearly impossible to consolidate the code any further without breaking the API/ABI. Especially with PackageKit being dead<ref>[https://blogs.gnome.org/hughsie/2019/02/14/packagekit-is-dead-long-live-well-something-else/ PackageKit is dead, long live, well, something else], hughsie, 2019 (Accessed 2025-06-21)</ref>, we can't move with the old "libhif" API in libdnf, because making any bigger changes to PackageKit is clearly out of scope. </blockquote> The announcement of DNF5 development was made in March 2020, with a roadmap targeting major API changes and early development snapshots throughout 2020, aiming for inclusion in Fedora 34 and stable replacement of DNF4 by early 2021.<ref>[https://lwn.net/Articles/814066/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> Key motivations for DNF5's development included the need to modernize the codebase, which had become cluttered and difficult to maintain, and to move away from dependencies on Python and older APIs. The new design emphasized a fully featured package manager written primarily in C++ for improved performance, reduced resource usage, and a smaller install size compared to DNF4.<ref>[https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5#Benefit_to_Fedora Make DNF5 The Default], Jaroslav Mracek, 2022 (Accessed 2025-06-21)</ref> DNF5 also aimed to unify the software management tools in Fedora by replacing DNF and Microdnf, and providing a new daemon alternative to PackageKit.<ref name=":0">[https://ostechnix.com/dnf5-package-manager-introduction/ Introduction to DNF5: The Next-Generation Fedora Package Manager], Sk, 2025 (Accessed: 2025-06-21)</ref> DNF5 introduced a new core library (libdnf5), revamped plugin systems, enhanced modularity support, and a streamlined command-line interface with improved user experience. The development process was marked by an emphasis on openness, community involvement, and transparent upstream issue tracking to foster broader collaboration. By Fedora 38, DNF5 was available, and it became the default package manager in Fedora 41, fully replacing the older DNF.<ref name=":0" /> == Features == ==== Dependency Resolution ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== Transaction History ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== Modularity Dupport ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== Plugin System ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== Parallel Downloads ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== Package Groups ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: * Installing Packages: <code>dnf install <package_name></code> * Updating Packages: <code>dnf update</code> * Removing Packages: <code>dnf remove <package_name></code> * Listing Installed Packages: <code>dnf list installed</code> * Searching for Packages: <code>dnf search <keyword></code> * Managing Repositories: <code>dnf repolist</code>, <code>dnf config-manager</code> * Viewing Transaction History: <code>dnf history</code> == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. == References == [[Category:Package Managers]] 50c0a4d213b02a352618723182965ec366341978 0 246 2944 1204 2025-07-26T17:02:02Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox|image=|caption=|title=dpkg|releasestatus=Maintained|lastrelease=1.21.22 / 24 May 2023|languages=C, C++, Perl|developers=The Debian Project|website=[https://www.dpkg.org/ dpkg.org]}} '''dpkg''' (Debian Package) is the core software of the package management system in the [[Debian]] operating system and its derivatives. It is used to install, remove, and provide information about <code>.deb</code> packages. dpkg is a low-level tool. [[APT|APT (Advanced Package Tool)]] is more commonly used in practice as it is a high-level tool.<ref>Afia Zahin Oishi (December 6, 2023). [https://linuxsimply.com/linux-basics/package-management/package-manager-comparison/dpkg-vs-apt/ <nowiki>"Dpkg Vs Apt [What's the Difference Between Package Managers]"</nowiki>]. linuxsimply.com. LinuxSimply.</ref> == References == [[Category:Package Managers]] 5dfab86d6c02a7dccf1f02fea64c403fa3ce875d 0 430 2945 2881 2025-07-26T17:02:19Z Atmois 13 Add references header wikitext text/x-wiki [[File:Daemon.png|thumb|Daemon Flowchart]] Computers with the ability to multitask different processes at once contain a type of process labelled '''daemon''' process. These types of computer programs run in the background, which isn't controlled by a graphical interface or any user input, but rather, by the [[Init System|init system]], which also serves as the parent process<ref>Sep 2nd, 2020, ''Understanding daemons Unix'' by Aryaman Sharda: https://digitalbunker.dev/understanding-daemons-unix/</ref> of <u>most</u> daemons. For easier identification, processes' names end with the letter ''d'' to indicate the subjected process is a daemon. There are a few ways a daemon process can be made, all with different use cases: calling a <code>fork</code>and having the parent exit <ref>Chapter 13. Daemon Processes by Shichao's Notes: https://notes.shichao.io/apue/ch13/</ref> creates a daemon process by tricking the shell to thinking the command is finished, the child process obtains a new GID (Group Identifier) but is assigned a different PID (Process Identifier), another method calls a <code>umask</code> to set the file mode creation mask to a known value, this method is typically preferred when the process makes necessary files. There are more uncommon methods to achieve a daemon process, but are typically too complicated. === Terminology === The term "'''daemon'''" comes from MIT's Project MAC<ref>Take Our Word For It, Issue 129, Page 2: http://www.takeourword.com/TOW129/page2.html</ref> on the IBM 7094, labelled after scientist James Maxwell who imagined an interesting physics problem: He Imagined a container divided by a gate which separates the container into 2 equal parts, within the gate exists a hole big enough for one gas molecule, this gate was controlled by a ''daemon.'' Maxwell labelled it a "daemon" based off Greek Mythology where a daemon was a supernatural force that would work in the background. === Use-case(s) === ==== Unix-based/like Operating Systems ==== In such operating systems, daemons serve many functions for every part of the system and are very common. Although not required, many daemons have their parent be the init system, which possesses the PID of 1. Typically speaking, processes become daemons by being started by either the init system or a start up script. === Controlling a Daemon Process === ==== Using <code>systemctl</code>: ==== A user is able to adjust whether a daemon process is enabled or not using the <code>systemctl</code> command in their preferred shell, if the user wishes to start a daemon, they are able to use the <code>start</code> function, next to the service name in order to start it up. <syntaxhighlight lang="shell"> $ sudo systemctl start application.service # There is no output if a application begins succsesfully # If there is an error: Failed to start application.service: Unit application.service not found. # or Failed to start application.service: Access denied </syntaxhighlight>The user isn't required to add <code>*.service</code>, the system will automatically look for services that match. This command also works with <code>stop</code>, prompting the said service to terminate.<syntaxhighlight lang="shell"> $ sudo systemctl stop application.service # No Output if successful # Output on Error(s): Failed to stop application.service: Unit application.service not loaded. # or Failed to stop application.service: Access denied. </syntaxhighlight>If this is a process that is started by the init system at boot, it will begin again on a full reboot if it is enabled or when it is started manually. == References == <references /> 7b295baf733b90b0826ce3df54f7b5fb4e8cd94d 0 182 2946 1575 2025-07-26T17:02:32Z Atmois 13 Add references header wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, [[Xfce]], [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a [[Linux Distributions|Linux distribution]] developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> == History == Debian adheres to the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> In 1997, the Debian Project established Software in the Public Interest as a nonprofit organization to provide ongoing financial support. However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> == Features == === Release Cycle === Debian maintains three primary development branches: * Stable - The current official release, recommended for production systems * Testing - The next planned stable release, featuring newer software versions * Unstable (Sid) - The rolling development branch where new packages are initially introduced === Package Management System === Debian uses the [[APT]] (Advanced Package Tool) built on top of [[dpkg]], featuring: * Over 59,000 ready-to-install software packages * Multiple repository sections (main, contrib, non-free) * Secure package verification through signed repositories * Sophisticated dependency resolution === Project Management === The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as: * The Debian Social Contract * The Debian Constitution * The Debian Free Software Guidelines === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[Window Manager|Window Managers]] instead of [[Desktop Environment|Desktop Environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /> == Installation == Debian provides multiple installation methods: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Live images for testing before installation * Architecture-specific installers * Cloud images for virtual deployment == References == <references /> [[Category:Linux Distributions]] 73f96161ee886c6118e853c99e4fd5cceb9084e4 0 173 2947 2706 2025-07-26T17:02:46Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Incomplete page}} [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager ('''GDM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a [[graphical user interface]] that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.<ref>https://github.com/tvrzna/emptty GitHub, 2025 (Imported 02.07.2025)</ref> == References == [[Category:Terminology]] 6997cd26efc7a43571489966bd5e4a29957f1e3f 0 736 2948 2863 2025-07-26T17:03:22Z Atmois 13 Add references header wikitext text/x-wiki [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tools [[sed|<code>sed</code>]] and [[grep|<code>grep</code>]] were directly inspired by ed commands <code>s/e/d</code> and <code>g/re/p</code> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor [[vi]], whose variants remain some of the most popular TUI text editors. == References == 377bd0e8d701285d81af3c89d2cb93565eecd692 0 623 2949 2862 2025-07-26T17:04:24Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=EndeavourOS|image=[[File:EndeavourOS Logo.svg|Thumb]]|caption=The Endeavour OS logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, aArch64|website=[https://endeavouros.com endeavouros.org]}}'''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">https://endeavouros.com/</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>https://endeavouros.com/about-us/</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning Arch Linux fundamentals. === Installation === EndeavourOS provides an ISO with the Calamares installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with Arch Linux, meaning it uses Arch's official repositories directly and adheres closely to Arch's philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * AUR Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate AUR package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * Pacman Compatibility: Fully compatible with Arch's pacman package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for Arch Linux are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla Arch, or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the AUR, as well as EndeavourOS-specific themes and utilities.<ref>https://repo.c48.uk/endeavouros/repo/endeavouros/</ref> This is simply a pacman repository that can simply be added to any Arch Linux system if desired. == References == 0dcf931e8329202e8895cdd1c2edb4d851e90e68 0 650 2950 2761 2025-07-26T17:04:41Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox | image=[[File:Enlightenment logo.svg|Enlightenment_logo]] | caption = Enlightenment logo | title=Enlightenment | releasestatus=Maintained | lastrelease=0.27.1, March 17, 2025 | firstrelease=0.13.2, January 18, 1998 | languages=[[C]], [[ELF]] | developers=Enlightenment Foundation | website=[https://www.enlightenment.org/, enlightenment.org/] }} [https://www.enlightenment.org/ Enlightenment] is a [[Desktop Environments|Desktop Environment]] and [[Window Manager]] for [[Linux]] and other [[Unix|Unix-like]] [[Operating System|operating systems]], such as [[BSD]] derivatives.<ref name=":0">[https://www.enlightenment.org/about Enlightenment About Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref>. Originally created by Carsten Haitzler in the late 90s with the philosophy "that users should be given as much control as possible."<ref>[https://www.enlightenment.org/about-enlightenment| About Enlightenment Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref> === Features === Enlightenment has many key features as a [[graphical desktop]] including its own set of graphical and system libraries known as the "Enlightenment Foundation Libraries". Designed to be portable and efficient while also being easy to use on various devices including touch devices even being used in Samsung devices.<ref name=":0" /> * Support for both [https://www.x.org/wiki/ X11] and experimental [https://wayland.freedesktop.org/ Wayland] support. * A hand optimized software rendering compositor. * Very low memory requirements. * The ability to configure everything graphically. * Touch gestures * Window Management Features ** Virtual desktops. ** Optional window tiling. ** Customizable mouse and keyboard bindings. ** And many more modules. == References == <references /> [[Category:Desktop Environments]] 28f2bf600ee6c77ec94a6a288b56ff9bd4993117 0 638 2951 2884 2025-07-26T17:05:19Z Atmois 13 Add references header wikitext text/x-wiki Ext4 is an advanced level of the ext3 [[filesystems]] which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular [[Linux Distributions|distributions]], however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. Information on how to do it can be found in [[Guides:Ext4]]. === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e. HDDs) ==== Changing the data mode ==== Ext4 provides three data modes<ref>[https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode Linux's ext4 documentation ]</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> You can change the data mode by setting the <code>data=...</code> mount option. ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost. The mount option <code>barrier=0</code> disables write barriers. Only disable this option if you know what you're doing. ==== Async journal commits and external journaling device ==== Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>[https://libre-consulting.com/posts/fs_ext4_external_journal/ ext4 external journal benchmarks.]</ref> ==== Enabling fscrypt support ==== fscrypt<ref>[https://github.com/google/fscrypt FSCrypt]</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. ==== Enabling fast_commit support ==== fast_commit <ref>[https://lwn.net/Articles/842385/ LWN's article on fast_commit.]</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by setting the <code>fast_commit</code> feature flag. == References == <references /> 0b572f1083e48c7effc667695b2d6ec13678448e 0 177 2952 2872 2025-07-26T17:05:55Z Atmois 13 Add references header wikitext text/x-wiki '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word, libre)<ref>https://en.wiktionary.org/wiki/libre Wikitionary. Wikimedia Foundation. Accessed June 4, 2024.</ref> and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == [[Category:Terminology]] 8cc6ff9724e83f6298ee51301da76972902fb8e9 0 268 2953 2616 2025-07-26T17:06:04Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch github.com/fastfetch-cli/fastfetch] }} Fastfetch is a [[neofetch]]-like tool for fetching information about your [[Operating System|operating system]], [[software]] and hardware. It is written mainly in [[C]], with a focus on performance.<ref>https://github.com/fastfetch-cli/fastfetch Fastfetch Github, 2025 (Imported 26th, June 2025)</ref> == References == <references /> [[Category:Software]] 4bef65bd167ea03b5143b66824616bd06a1988fd 0 217 2954 2495 2025-07-26T17:06:20Z Atmois 13 Add references header wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}} {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]] |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}} [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being [[RHEL|Red Hat Enterprise Linux]] (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> == References == <references /> [[Category:Linux Distributions]] 1d9401a965cdf26a5ed06163907c51bb8a9a79f6 0 677 2955 2864 2025-07-26T17:06:36Z Atmois 13 Add references header wikitext text/x-wiki Flatpak is a universal packaging system and runtime for installing packages separate from the system packages. Mainly meant for desktop applications, Flatpak allows application developers to distribute packages without needing to worry about distro compatibility because Flatpak installs its own runtime dependencies. It claims to improve security through sandboxing providing the user the ability to give or revoke permissions for a given application. Flatpak is installed by default on many distributions and it's main distribution platform is Flathub. == Installation == Flatpak comes preinstalled on many distributions such as Linux Mint and Fedora but can be installed through most distro's package repositories if not present. ==== KDE Discover ==== KDE Discover includes the ability to install Flatpak and enable Flathub through its graphical user interface. Go to the setting tab and install the Flatpak backend then restart Discover then go back to the settings and enable Flathub. ==== CLI Install on Ubuntu ==== To install Flatpak from the CLI run:<syntaxhighlight lang="bash"> sudo apt install flatpak </syntaxhighlight>To enable Flathub from the CLI run:<syntaxhighlight lang="bash"> flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo </syntaxhighlight>If you make use of GNOME Software you can install the integration plugin:<syntaxhighlight lang="bash"> sudo apt install gnome-software-plugin-flatpak </syntaxhighlight>For the KDE Discover plugin run:<syntaxhighlight lang="bash"> sudo apt install plasma-discover-backend-flatpak </syntaxhighlight>For other distros read the guides on [https://flathub.org/setup Flathub.org]. == Compatibility == Flatpak allows improved package compatibility through its use of its own runtime dependencies. Packages can run through Flatpak where it might not be possible to run on natively such as: * Applications that require a newer version of glibc than whats available on an stable release distro such as Rocky Linux 8. * Applications that depend on glibc such as Steam running on a distro using musl like Alpine Linux. * Multilib packages such as Steam or Wine on distros without multilib support such as CentOS Stream 10. == Sandboxing == Package permissions can be managed by the user through a graphical user interface with Flatseal which can be installed as a Flatpak. == Flathub Package Verification == Flathub has a package verification system that allows packages maintained by the official developers to have a verification tick.<ref>[https://docs.flathub.org/docs/for-app-authors/verification Verification | Flathub Documentation], Flathub Team, 2025 (Accessed: 2025-06-22)</ref> This has lead to some confusion where verification is mistaken for package safety. Linux Mint hides unverified Flatpaks from Software Manager by default Starting in version 22.<ref>[https://www.omgubuntu.co.uk/2024/06/linux-mint-will-hide-unverified-flatpaks Linux Mint Will Hide Unverified Flatpaks in Software Manager - OMG! Ubuntu], Joey Sneddon, 2024 (Accessed: 2025-06-22)</ref> == References == bb7540c4f0d6299f8ce1916f29703d992180e96d 0 418 2956 2921 2025-07-26T17:06:54Z Atmois 13 Add references header wikitext text/x-wiki {{DistributionInfobox|architectures=arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox|caption=The FreeBSD logo|defaultdesktops=[[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]]|image=[[File:FreeBSD logo.png|200px|FreeBSD_logo]]|packagemanager=[[pkg]]|releasemodel=Stable|releasestatus=Maintained|title=FreeBSD|usagetype=Desktop, Firewall, Raspberry Pi, Server|website=[https://freebsd.org freebsd.org]}} FreeBSD is a [[UNIX|Unix]]-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released in November 1993.<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"] [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref> [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[Drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a kernel and drivers, and relying on third-parties such as [[GNU]] for system [[:Category:Software|software]].<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref> The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports.<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref> The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']} == References == <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] a63ca4d6c22ebab97464421d59e1dc3a6ee67e24 0 291 2957 2406 2025-07-26T17:07:17Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|300px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 48, 2025-03-19 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[File:GNOME 43.png|thumb|A desktop running GNOME 43]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>[https://www.gnu.org/philosophy/free-sw.en.html What is Free Software?], GNU (Accessed: May 7, 2025)</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>[[wikipedia:Qt_(software)#Early_developments|Early Developments of QT]], Wikipedia (Accessed: May 7, 2025)</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>[[wikipedia:GNOME#History|History of GNOME]], Wikipedia (Accessed: May 7, 2025)</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>[https://foundation.gnome.org/ GNOME Foundation Website]</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. == References == [[Category:Desktop Environments]] a422acfd4e54030beff334f5b0fb7f2c7734a2a3 0 441 2958 2763 2025-07-26T17:07:29Z Atmois 13 Add references header wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,")<ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU], The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> is a dedicated organization for free [[:Category:Software|software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone [[Operating System|operating system]] because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or [[Proprietary software|proprietary]]: A few are GNU/[[Linux]], [[MacOS]], [[UNIX|Unix-based]]/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the [[proprietary software]] of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe. </ref> == Included Software / Components == [[File:Gnu compiler collection-logo-1.png|alt=This logo depicts a Bull shaped animal jumping out of an egg, in black text that displays the letters G, C, C|left|thumb|224x224px|A logo of the GCC.]] As of June 2024, the GNU project currently holds 394 active [[packages]], but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. Overall, these components are in many operating systems, mainly because of how easy GCC is to access for any developer. Because of Richard Stallman, he was able to open source the variety of tools and software developed for the GNU project and in turn, pushed forward for the movement of open and free software for all.<ref name=":0" /> == History of GNU == [[File:RichardStallman.jpg|alt=A Picture of Richard Matthew Stallman in 2024|thumb|341x341px|A Picture of Richard Matthew Stallman in 2024]] Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref name=":0">[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible [[architecture]] because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs.<ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> == References == <references /> b53daa63f269b65136281fff9f71dce48271a77a 0 575 2959 1988 2025-07-26T17:07:48Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">https://www.gnu.org/software/emacs/emacs.html</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>https://melpa.org/#/getting-started</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>https://github.com/emacs-evil/evil</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features</ref> and Spacemacs<ref>https://www.spacemacs.org/</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == [[Category:Software]] 00321378a33c82cc24767c7beff656bcacbf71ba 0 707 2960 2879 2025-07-26T17:08:01Z Atmois 13 Add references header wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox |image=[[File:Grub-knoppix.jpg|thumb]] |caption=Grub Boot Menu |title=GRUB |releasestatus=Maintained |lastrelease=2.12, 2023-12-20 |languages=[[C]], [[Assembly]] |developers=GNU Project |website=[http://gnu.org/software/grub/ GNU Page] }}'''GRUB''' (short for '''GRand Unified Bootloader''') is a [[bootloader]] designed for [[UNIX|UNIX-like]] systems developed by the GNU Project. It provides the user with the option to choose between different [[Operating System|operating systems]] or [[kernel]] versions without having to use the [[BIOS]]. Originally developed by Erich Boleyn<ref>[http://www.uruk.org/grub/ GRUB -- GRand Unified Bootloader], Erich Boleyn (Accessed: 2025-07-01)</ref>, GRUB is now a part of the GNU project and comes with two versions, GRUB 0 (Also known as GRUB Legacy) and GRUB 2. Since GRUB Legacy is obsoleted and should no longer be used, this article mainly describes GRUB 2. GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU Hurd with the University of Utah's Mach 4 microkernel (now known as GNU Mach). Erich and Brian Ford designed the Multiboot Specification, because they were determined not to add to the large number of mutually-incompatible PC boot methods.<ref name=":0">https://www.gnu.org/software/grub/manual/grub/grub.html#Overview GNU website, 2025 (Imported 02.07.2025)</ref> Around 2002, Yoshinori K. Okuji started work on PUPA (Preliminary Universal Programming Architecture for GNU GRUB), aiming to rewrite the core of GRUB to make it cleaner, safer, more robust, and more powerful. PUPA was eventually renamed to GRUB 2, and the original version of GRUB was renamed to GRUB Legacy. <ref name=":0" /> GRUB contains support for multiple file systems ( [[FAT32]], [[ext4]], [[Btrfs]] or [[XFS]].) Both GRUB 2 and GRUB 0 systems support [[UEFI]] and BIOS-based systems. == See More == * [https://wiki.archlinux.org/title/Grub Grub on ArchWiki] == References == a92f4a6c237a0a5c64d7f32972d140f9484cdb8c 0 679 2961 2874 2025-07-26T17:08:43Z Atmois 13 Add references header wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git's early design emphasized a distributed workflow similar to BitKeeper's but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like GitHub, which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. == References == a91f18136e4acb7ed495e0885f6593ab9d2ce985 0 674 2962 2880 2025-07-26T17:09:00Z Atmois 13 Add references header wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Searching for “PATTERNS” or “regex” in <code>grep --help</code> | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU grep: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, grep's creation stemmed from Thompson's need to analyse text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed]] text editor into a standalone tool. He named the tool ''grep'' because in ed, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into grep, which finds all lines with the text “error”. However, grep itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended [[regular expression]]s'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Examples == === Finding Python Function Calls === In a [[Python]] codebase, we can find all calls to functions under the <code>subprocess</code> module with <code>shell=True</code>: $ grep -r --include='*.py' -nHE 'subprocess\.\w+\([^)]*shell=True' ./driver.py:69: return subprocess.call("lspci | grep -q -i NVIDIA", shell=True) == 0 ./driver.py:202: return subprocess.call("lspci | grep -q -i Network | grep -q -i Broadcom", shell=True) == 0 ./driver.py:211: return subprocess.call("lspci | grep -q -i Bluetooth | grep -q -i Broadcom", shell=True) == 0 ./util.py:38: proc = subprocess.Popen(f"chroot {chroot} /tmp/stellar-payload.sh", shell=True) ./util.py:63: # proc = subprocess.Popen(payload, shell=True) ./util.py:66: proc = subprocess.Popen(f"pkexec {tmpfile}", shell=True) (This is run on the [https://github.com/Ultramarine-Linux/stellar/ Ultramarine stellar codebase]) We can breakdown the flags used in this example: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>--include='*.py'</code>: only examine Python files * <code>-n</code>: show line numbers * <code>-H</code>: show file name * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] We can divide the pattern <code>subprocess\.\w+\([^)]*shell=True</code> into many parts: # <code>subprocess</code> matches the string “subprocess” literally; # <code>\.</code> matches the full stop literally; # <code>\w+</code> matches word characters one or more times, where a word character (<code>\w</code>) is any letter, digit or underscore<ref>[https://www.regexroo.com/word-characters Understanding \w and Its Counterpart \W in Regex], RegexRoo.com, 2025 (Accessed: 2025-06-21)</ref>; # <code>\(</code> matches for an open parenthesis <code>(</code> literally; # <code>[^)]*</code> is an inverse character group and matches any characters that are not the closing parenthesis <code>)</code> zero or more times; and # <code>shell=True</code> matches the string “shell=True” literally. === Finding Code Files with TODOs and FIXMEs === We can list out code files that contains both the word “FIXME” and “TODO”. For a Rust project: $ grep -rlZ 'FIXME' --include='*.rs' . | xargs -0 grep -l 'TODO' ./src/pages/_15_installing.rs ./src/main.rs Flags: * <code>-r</code>: find files recursively (by default in the current working [[directory]]) * <code>-l</code>: output matching files' names only * <code>-Z</code>: instead of a new line character, print out a null character after each filename * <code>--include='*.rs'</code>: only examine Rust files In this example, the first command outputs the filenames with null separates, then [[xargs]] is used to feed the filenames into the second grep command, which searches for “TODO”s in those files. === Extracting All Unique Public IPv4 Addresses from Log Files === We can extract all the unique IPv4 addresses from a directory of log files, but exclude any private IP addresses, such as <code>10.x.x.x</code> / <code>192.168.x.x</code>: <syntaxhighlight lang=sh> grep -rhoE '([0-9]{1,3}\.){3}[0-9]{1,3}' /path/to/logs | sort -u | grep -vE '^10\.|^192\.168\.' </syntaxhighlight> Flags: * <code>-r</code>: find files recursively * <code>-h</code>: suppress printing of filenames * <code>-o</code>: show only matching part of line * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] * <code>-v</code>: select non-matching lines For the first pattern: # <code>[0-9]</code> matches the digits (0 to 9 on the ASCII table includes all digits), and <code>{1,3}</code> specifies the length must be between 1 and 3; and # <code>([0-9]{1,3}\.){3}</code> matches exactly 3 times the above followed by a full stop. For the second pattern: # <code>^10\.</code> matches for lines starting with <code>10.</code>; # <code>^192\.168\.</code> matches for lines starting with <code>192.168.</code>; and # <code>|</code> (which indicates “or”) allows matching for the regex specified on the left or the right. Due to the invert flag (<code>-v</code>), if a line matches the second pattern, it is excluded, and other lines are printed instead. == Alternatives == Faster implementations of grep such as '''[[ripgrep]]''' (<code>rg</code>) and '''[[hypergrep]]''' (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU grep, and usually not pre-installed on most distributions. The '''<code>agrep</code>''' tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] == References == 170533339b215a6a1a839568875fc245418e5a51 0 263 2963 2579 2025-07-26T17:09:25Z Atmois 13 Add references header wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.99.0, 2024-10-24 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|thumb|The Hyfetch Pride Month easter egg.]] Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your [[Operating System|operating system]], [[:Category:Software|software]] and [[hardware]] with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch Hyfetch Github 2025 (fetched 24th June 2024)</ref> === Features === Due to Hyfetch being a direct fork of [[Neofetch]], many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of [[Neofetch]] bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. == References == <references /> [[Category:Software]] 6d3458f7c5f48bdb502322a0dbc8d5a0260f23e7 0 227 2964 2602 2025-07-26T17:09:55Z Atmois 13 Add references header wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager]</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== == References == [[Category:X_Window_Managers]] 9428b1e6ebdc0b7af67ef113d6816fbc44ecabad 0 349 2965 2861 2025-07-26T17:10:24Z Atmois 13 Add references header wikitext text/x-wiki In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is required to enable optimal use of an OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor'''<ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref> of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in an operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, etc. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |runit |February 10, 2004 |September 29, 2024 |↓ |Gerrit Pape |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS. == References == <references /> [[Category:Terminology]] d76564ed7764b66fcc57987e1ca6e79c8f5e7c91 0 661 2966 2476 2025-07-26T17:10:55Z Atmois 13 Add citations template wikitext text/x-wiki {{Needs Citations}}{{DistributionInfobox|title=Kali Linux|image=[[File:Kali-dragon-icon.svg|frameless]]|caption=Kali Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Apt]]|defaultdesktops=[[Xfce]], [[GNOME]], [[KDE Plasma]]|usagetype=Desktop, Mobile, USB|architectures=x86_64, x86, armel, armhf|website=[https://www.kali.org/ Kali.org]}}Kali Linux is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, Digital forensics, and penetration testing. 7b19a08d92902dcf781bb809dfcb577bded9af87 0 344 2967 2867 2025-07-26T17:11:07Z Atmois 13 Add references header wikitext text/x-wiki [[File:Kernel Layout.svg|thumb|How the Kernel interacts with the software and hardware.]] The Kernel is the core part of any [[Operating System|operating system]], including [[Linux]]. It's the fundamental layer between your [[hardware]] (like your CPU, memory, and GPU) and the [[:Category:Software|software]] you interact with (like programs and applications). When people refer to Linux, they usually refer to a combination of the Linux Kernel with other important Software (Like GNU Utilities) to make a fully functional Operating system to use. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, etc.). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2 Linus Torvalds 1991 (Retrieved 16th March 2025)</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel Kicksecure, Madaiden, Adrelanos 2023 (Retrieved 16th March 2025)</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. == References == [[Category:Terminology]] 151134401e2de9e2df4a66321392387619e301a3 0 345 2968 2613 2025-07-26T17:11:21Z Atmois 13 Add references header wikitext text/x-wiki {{Needs Citations}} Kernel Modules are pieces of code that can be loaded directly into the [[Kernel]] at runtime to extend functionality.<ref>https://linux-kernel-labs.github.io/refs/heads/master/labs/kernel_modules.html Kernel Labs Github, 2025 (imported 26th June 2025)</ref> The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your [[Linux Distributions|Distribution]], as such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically older ones benefit the most) at the cost of new devices potentially not working when added. It is also possible to compile a Linux kernel on a pre-existing system to only use needed Kernel modules. == Obtaining information == Modules depend on the kernel release and the kernels version, though usually they are stored in <code>/usr/lib/modules/''kernel_release_version''</code>''.'' To see which modules are loaded, <code>lsmod</code> can be used. Obtaining information is achievable with <code>modinfo <module_name></code> == Module loading == === Automatic loading === Usually most needed modules are handled [[udev]], so usually out of tree modules aren't needed, though there are cases where loading or blacklisting a module is needed for your setup to function properly. Early module loading is generally handled by your [[initramfs]] generator of choice, usually dracut, booster or mkinitcpio. Alternatively, [[systemd]] will load modules explicitly listed in <code>/etc/modules-load.d/</code> ,with the naming scheme of <code>/etc/modules-load.d/program.conf</code>. Lines starting with ; or # are parsed as comments and ignored === Manual loading === Kernel modules can be manually loaded with <code>modprobe <module_name></code>, or loading a module that by file name (i.e. modules that are not installed in <code>/usr/lib/modules/<kernel_release_version></code>) can be achieved either of the following ways:<syntaxhighlight lang="sh"> insmod file_name module_options modprobe file_name </syntaxhighlight>Removing a module can be achieved by:<syntaxhighlight lang="sh"> rmmod module_name modprobe -r module_name modprobe --remove module_name </syntaxhighlight> == References == [[Category:Terminology]] 8d938435beee5789051d0ce13c20fb8431aeb3b8 0 219 2969 2776 2025-07-26T17:11:34Z Atmois 13 Add references header wikitext text/x-wiki {{MascotInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan.<ref>https://community.kde.org/Promo/Material/Mascots Official KDE Wiki, 2025 (Imported 6th June 2024)</ref> Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror], KDE's default web browser.<ref>https://community.kde.org/Konqi Official KDE Wiki, 2025 (Imported 6th June 2024)</ref> == References == <references /> [[Category:Mascots]] 8b7986c8c54704292351c8d336a90506bdc2db12 0 202 2970 2520 2025-07-26T17:12:13Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow Gentoo Wiki, 2023 (Imported 4th June 2024)</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html Gentoo Forums, 2003 (imported 4th June 2024)</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727 Gentoo Bug Report, 2003 (imported 4th June 2024)</ref> * Larry can be found in [[emerge]] by running "emerge --moo", Larry can also be found in [[Dpkg|apt]] by running "apt moo". * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry</ref> == References == <references /> [[Category:Mascots]] 099b280795e9d97d1499b82f94b554e0af1f3e7c 0 244 2971 2052 2025-07-26T17:12:28Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]. Installation instructions should be on its own Guides page.}} [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. '''NOTE:''' After your first Libreboot, you are more than likely able to flash repeatedly afterwards without having to use a Pomona Flash Clip (below). Depending on your device, the flashing experience may and inevitably, at times, '''will''' vary. '''<u>Please check for your BIOS chip device on the Libreboot website.</u>''' === Steps to Install === As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your machine using the Dell OptiPlex as an example. See below for an easier method for that specific device. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. For a Dell OptiPlex 9020, your image '''should be named''' "'''dell9020mt_12mb'''." after compilation. ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) == References == [[Category:Guides]] 01de4e088641b39694a820a6c0a6a011f20ccd35 0 178 2972 2689 2025-07-26T17:12:40Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] Linux in itself refers to two entities, the former being the [[kernel]] itself developed by Linus Torvalds and the latter being the families of [[Linux Distributions|Operating Systems based off the Kernel]]. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. == References == <references /> [[Category:Terminology]] ab438e01acf0c71185c897b925b4c26849a71e9e 0 198 2973 2859 2025-07-26T17:12:54Z Atmois 13 Add references header wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of [[systemd]]. In its stead, it offers four alternative [[Init System|init systems]] in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of [[systemd]]. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AIX]] |A series of Unix-Based Operating systems for Power servers. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of [[GNU]] utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] fabcf7d4ca9f1439ae1fad300c45bb3ed7c019b4 0 537 2974 1788 2025-07-26T17:13:05Z Atmois 13 Add references header wikitext text/x-wiki {{DistributionInfobox|title=Linux From Scratch|image=[[File:Linux-From-Scratch logo.png|Linux-From-Scratch_logo]]|caption=Linux From Scratch logo|releasestatus=Maintained|packagemanager=None|releasemodel=Stable|usagetype=Source-based, Education|defaultdesktops=[[Fluxbox]], [[IceWM]], [[KDE Plasma]], [[LXQt]], [[Openbox]], [[Xfce]], [[GNOME]] (BLFS)|website=[https://www.linuxfromscratch.org/index.html www.linuxfromscratch.org]|architectures=i386, x86_64}} Linux From Scratch is the name of a type of [[Linux]] install and the name of a book written by Gerard Beekmans, which gives detailed instructions on how to achieve a fully functional Linux operating system entirely by compiling source packages. The book is available for free on the official website and major releases are usually published twice a year<ref>[https://www.linuxfromscratch.org/lfs/news.html "LFS News"]. ''www.linuxfromscratch.org''.</ref>. [[File:Linux From Scratch desktop.jpg|alt=Screenshot of a Linux From Scratch install with a modified Xfce desktop.|thumb|Screenshot of a Linux From Scratch install with a modified Xfce desktop.]] == Projects under LFS == The following projects are part of the Linux From Scratch umbrella and are accessible on the official website, and are as follows: * '''Linux From Scratch (LFS)''': The original book itself, which gives detailed instructions on how to create a bootable and fully functional Linux system by compiling source packages<ref>[https://www.linuxfromscratch.org/lfs/ "LFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. * '''Beyond Linux From Scratch (BLFS)''': An extension of the original LFS book to extend the functionality of a LFS system by providing instruction on how to compile a wide variety of additional packages, such as desktop environments and networking tools<ref>[https://www.linuxfromscratch.org/blfs/ "BLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. * '''Automated Linux From Scratch (ALFS)''': A project meant to automate the compilation of the various packages needed for a LFS system via the use of scripts<ref name=":0">[https://www.linuxfromscratch.org/alfs/ "MLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. The current official implementation of ALFS is ''jhalfs''<ref name=":0" />. * '''Multilib-LFS (MLFS)''': A variant of the original LFS book to build a system that's able to execute 32-bit binaries<ref>[https://www.linuxfromscratch.org/mlfs/ "MLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. It is cited as a strongly recommended requirement for GLFS<ref name=":1">[https://www.linuxfromscratch.org/glfs/ "GLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. * '''Gaming Linux From Scratch (GLFS)''': A guide based off the BLFS book that provides instructions for installing gaming software such as [[Steam]] and [[Wine]], software libraries such as [[OpenGL]] and [[Vulkan]] and proprietary graphics drivers for [[Nvidia]] and [[AMD]] GPUs<ref name=":1" />. * '''Hints''': Large library of user-submitted documents which provide tips on various things related to maintaining LFS systems<ref>[https://www.linuxfromscratch.org/hints/ "LFS Hints Project Home"]. ''www.linuxfromscratch.org''.</ref>. * '''Patches''': Central repository of user-submitted patch files to add LFS-specific functionality to various packages and also serves as a testing ground for patches that may be added to new LFS and BLFS versions<ref>[https://www.linuxfromscratch.org/patches/ "LFS Patches Project Home"]. ''www.linuxfromscratch.org''.</ref>. * '''LFS Editor's Guide''': Small document that describes the LFS development process<ref>[https://www.linuxfromscratch.org/lfs/LFS-EDITORS-GUIDE.html "Linux From Scratch Editor's Manual"]. ''www.linuxfromscratch.org''.</ref>. * '''Museum''': Archive of old LFS versions<ref>[https://www.linuxfromscratch.org/museum/ "Index of /museum"]. ''www.linuxfromscratch.org''.</ref>. == Standard build unit (SBU) == A peculiar feature of LFS is its usage of special measurement units to calculate the approximate time that a package takes to fully compile called standard build units (SBUs)<ref>[https://www.linuxfromscratch.org/lfs/view/stable/chapter04/aboutsbus.html "4.5 About SBUs"]. ''www.linuxfromscratch.org''</ref>, and 1 SBU is roughly equal to the time it takes to compile the first package in the LFS book, [[binutils]]<ref>[https://www.linuxfromscratch.org/lfs/view/stable/chapter05/binutils-pass1.html "5.2. Binutils-2.43.1 - Pass 1"]. ''www.linuxfromscratch.org.'' Retrieved 2 February 2025.</ref>. For example, if it took about 10 minutes to compile binutils, and the [[GRUB]] page says that it takes approximately 0.3 SBUs to build<ref>[https://www.linuxfromscratch.org/lfs/view/stable/chapter08/grub.html "8.64. GRUB-2.12"]. ''www.linuxfromscratch.org''. Retrieved 2 February 2025.</ref>, you would multiply the amount of time for how many SBUs the page says it would take, resulting in about 3 minutes of compile time. == References == 32129cae121b00aaf9df67993106177ac48eaabb 0 628 2975 2271 2025-07-26T17:13:19Z Atmois 13 Add references header wikitext text/x-wiki Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>https://linuxmint.com/</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>https://iso.atl.dev/l/linuxmint</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>https://distrowatch.com/table.php?distribution=mint</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the [[Plasma|KDE]] desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use [[Ubuntu]] as its base and featured the GNOME desktop environment.<ref>https://www.linuxmint.com/about.php</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. The latest release, Linux Mint 22.1 "Xia", was launched in January 2025 and is supported until 2029.<ref>https://www.linuxmint.com/download.php</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>https://repo.c48.uk/mint/pkgs/pool/</ref> == References == 0594bffac498981e4cf1e43a4ef93c7bf420b238 0 218 2976 2882 2025-07-26T17:13:36Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} == Introduction == [[Linux]] due to its generally lower system requirements than [[Windows]]<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> or [[macOS]] and a general absence of vendor-imposed hardware restrictions is frequently chosen for reviving and reusing older devices. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (i.e. keyrings, polkit, GTK, QT, etc.) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time-consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' == References == [[Category:Guides]] <references /> 434391c201f99db4ddb891349fa3becdf69a14d5 0 733 2977 2831 2025-07-26T17:14:06Z Atmois 13 Add references header wikitext text/x-wiki '''Apple M1''' is a series of [[ARM|ARM-based]] system-on-a-chip (SoC) designed by [[Apple|Apple Inc]]., launched 2020 to 2022. It is part of the Apple silicon series, as a [[central processing unit]] (CPU) and [[graphics processing unit]] (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwidth. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>https://www.apple.com/newsroom/2022/03/apple-unveils-m1-ultra-the-worlds-most-powerful-chip-for-a-personal-computer/</ref> The M1 runs Apple's [[macOS]] and [[iPadOS]], Initial support for the M1 SoC in the [[Linux|Linux kernel]] was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == M1 Chip Variants == === A14 === [[File:Apple A14.jpg|thumb|Apple A14 Bionic, the chip M1 is based on.]] The Apple A14 Bionic features an Apple-designed 64-bit, six-core CPU, implementing ARMv8 with two high-performance cores called “Firestorm” and four energy-efficient cores called “Icestorm”.<ref>[https://www.youtube.com/live/KR0g-1hnQPA?si=0l-0ixbkIdH8_pLf https://www.youtube.com/live/KR0g-1hnQPA]</ref> === M1 === The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big. LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[https://www.youtube.com/watch?v=BCvL8O0-Qwo https://www.youtube.com/watch?v=BCvL8O0-Qwo&t=4m18s]</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> {| class="wikitable" |+SoCs of the "Firestorm" and "Icestorm" microarchitectures. !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>https://www.apple.com/mac/m1/</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>https://support.apple.com/kb/SP858?locale=en_US</ref><ref>https://support.apple.com/kb/SP865?locale=en_US</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>https://borderpolar.com/tech/apple-m1-benchmarks/</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>https://www.nytimes.com/wirecutter/reviews/best-macbooks/</ref><ref>https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: * [[File:Macbook Pro 13" M1 2020.jpg|thumb|M1 Macbook Pro]] * Macbook Air 2020 (M1) - base model has binned, 7-Core GPU * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) * iPhone 12 and 12 mini (A14) * iPhone 12 Pro and 12 Pro Max (A14) * iPad air 4(th generation) (A14) * iPad (10th generation) (A14) and all the devices respective variants. == References == {{DEFAULTSORT:Apple M1}} d637c45ecbda3efd822fae933bb7972d3a77b26c 0 626 2978 2870 2025-07-26T17:14:32Z Atmois 13 Add references header wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>https://manjaro.org/</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">https://distrowatch.com/table.php?distribution=manjaro</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>https://wiki.manjaro.org/index.php/Pamac</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>https://en.wikipedia.org/wiki/Manjaro</ref><ref>https://www.ubuntumint.com/manjaro-linux-history/</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>https://www.geeksforgeeks.org/how-to-install-manjaro-linux/</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch's base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch's, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro's custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch's upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>https://itsfoss.com/manjaro-vs-arch-linux/</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. == References == d98375d9e61b0fe68a2d0cde3ca6884e7b714efe 0 428 2979 2777 2025-07-26T17:14:42Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' (short for ''manual'') is a [[TUI|command-line]] utility available on [[UNIX]] and UNIX-like [[Operating System|operating systems]] that provides documentation for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a man page the user can enter the following into their [[TUI|terminal]]:<ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> man ''<command_name>'' For example, to read the manual for <code>man</code> command itself: man man == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER<code> environment variable. By default, it uses <code>less<code>. Alternatively, the </code>-P</code> or </code>--pager</code> option can be used.<ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally.<ref>https://fishshell.com/docs/current/faq.html</ref> == References == <references /> 2273185910bf9d396e77a6ebebc2c9651c91426c 0 297 2980 2873 2025-07-26T17:14:59Z Atmois 13 Add references header wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref> The core concept of multi-booting revolves around partitioning a computer's [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system's configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. One trade-off for this is that multi-booting provides the booted OS with bare access to the machine's components, rather than needing to go through the same translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straightforward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Riot's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == References == <references /> [[Category:Terminology]] fc1dae4184d7c53ae5166812cb0978115920cdf9 0 261 2981 2683 2025-07-26T17:15:15Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was created by Dylan Araps in 2017 and was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]], a neofetch-like utility written in [[C]], and [[hyfetch]], a fork of neofetch with pride flags. == References == <references /> [[Category:Software]] 48201350523af70ac7884f13777a334308dd2049 0 534 2982 2679 2025-07-26T17:15:28Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example Niri Rice|title=niri|releasestatus=Maintained|firstrelease=v0.1.0-alpha.1|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">https://github.com/YaLTeR/niri/wiki/Important-Software</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading == References == <references /> 0c86848dd92899260a7db4e314483191e8953acf 0 171 2983 2712 2025-07-26T17:15:40Z Atmois 13 Add references header wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = Customizable based on user configuration | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] 6af0787d1b4d9b2d40891bd3559250a432ca99a1 0 299 2984 2860 2025-07-26T17:15:58Z Atmois 13 Add references header wikitext text/x-wiki {{DistributionInfobox|architectures=alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus|caption=The OpenBSD logo|defaultdesktops=[[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]]|image=[[File:OpenBSD logo.png|200px|OpenBSD_logo]]|packagemanager=pkg_*|releasemodel=Stable|releasestatus=Maintained|title=OpenBSD|usagetype=Security, Server|website=[https://openbsd.org openbsd.org]}} OpenBSD is a [[UNIX|Unix]]-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released in July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. == References == <references /> [[Category:Misc Operating Systems]] [[Category:BSD]] 0393e06001d427375957a61b9619be7a4c7d08cf 0 562 2985 2791 2025-07-26T17:16:08Z Atmois 13 Add references header wikitext text/x-wiki {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix-like [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel.<ref>[https://docs.openindiana.org/misc/openindiana/#what-is-the-openindiana-operating-system What is OpenIndiana Project?], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>https://web.archive.org/web/20100913030810/https://www.openindiana.org/</ref> It was proved timely as Oracle shut down development of OpenSolaris.<ref>[https://web.archive.org/web/20201109033546/http://sstallion.blogspot.com/2010/08/opensolaris-is-dead.html OpenSolaris is Dead.], Iconoclastic Tendencies, August 13, 2010 (Accessed: July 13, 2025)</ref> OpenIndiana uses the same tooling as Solaris; the SMF init system,<ref>[https://docs.openindiana.org/handbook/systems-administration/#service-management-facility Service Management Facility], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> FMA fault management system,<ref>[https://docs.openindiana.org/misc/openindiana/#what-features-does-openindiana-have What features does OpenIndiana have?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and IPS package manager,<ref>[https://docs.openindiana.org/handbook/systems-administration/#software-management Software management], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> The majority of the [https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/ Solaris documentation] also applies to OpenIndiana.{{Citation needed}} OpenIndiana makes use of the SunOS branch of the UNIX kernel,<ref>[https://docs.openindiana.org/misc/openindiana/#why-is-it-called-openindiana Why is it called OpenIndiana?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and thus provides all of the stability benefits of a UNIX System V derivative.{{Citation needed}} This does, however, mean that hardware support is limited in comparison to a BSD or Linux based OS.<ref>[https://docs.openindiana.org/community-hcl/getting-hardware-info/ Getting information about hardware] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> OpenIndiana uses the SunOS libc, which severely limits what software will compile on it successfully. SunOS libc only implements functions expected by POSIX and ANSI C.{{Citation needed}} == References == [[Category:Misc Operating Systems]] [[Category:Illumos]] e0097d2cae05c5937d837f64ef3cf58ef861bb8e 0 682 2986 2711 2025-07-26T17:20:11Z Atmois 13 Add citations template wikitext text/x-wiki {{Needs Citations}}{{DistributionInfobox|title=Puppy Linux|image=[[File:Puppy logo.svg|frameless|Puppy Linux Logo]]|caption=Puppy Linux Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=[[ICEWM]]|usagetype=Desktop|architectures=x86_64, x86, ARM|website=[https://puppylinux-woof-ce.github.io/ Link]}}'''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003. ac424f0d18a3f8fc43ce85a7c2490dc5e2f1395a 0 641 2987 2818 2025-07-26T17:20:25Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Maintenance |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/, openbox.org] }} [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable [[X Window Manager|window manager]] for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>https://openbox.org/</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>https://openbox.org/obconf</ref> === Usage === While Openbox is perfectly usable on its own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>https://slitaz.org/en/about/</ref><ref>https://crunchbang.org/about/</ref> == References == <references /> [[Category:Desktop Environments]] ed8318e29088d8847c66dc40af75653a76a2bae2 0 354 2988 2463 2025-07-26T17:20:34Z Atmois 13 Add references header wikitext text/x-wiki {{MascotInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy|222px]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. Puffy resembles a puffer-fish and has been the mascot since June 15th, 2000.<ref>https://www.openbsd.org/27.html</ref> [[File:Puffyanim.gif|thumb|99x99px|Animated Puffy Render]] == References == [[Category:Mascots]] 22fe88b730589ea0909d14a1eb010804cb604dcd 0 405 2989 2816 2025-07-26T17:20:43Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Short page}} Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Linux and other open source operating systems will avoid or not support proprietary software when possible. This is mainly due to incompatible licensing.<ref>https://solutionshub.epam.com/blog/post/proprietary-software-definition-examples Epam, 2025 (imported 27th June 2025)</ref> Some examples of proprietary software are Microsoft Windows and Adobe Photoshop. == References == [[Category:Terminology]] 07064c5c555f0f76a02a866f4e13f42f4b01e215 0 235 2990 1809 2025-07-26T17:20:52Z Atmois 13 References wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>https://github.com/gentoo/portage/blob/master/NEWS</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every [[Gentoo]] and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the [[Package Manager|package manager]], although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. === Configuration === Configuration of Portage is done through various configuration files and folders found in /etc/portage, which allows configuration of features such as USE flags, default options, masked packages and more. ==== make.conf ==== make.conf is the main configuration file for Portage. It allows the configuration of system-wide USE flags, Portage features, accepted licenses and more. This file is regularly edited during the Gentoo installation process and during ordinary use of it, so it's very important to get the options right for it. Below are some of the most relevant ones. ===== COMMON_FLAGS, CFLAGS, CXXFLAGS, FCFFLAGS and FFLAGS ===== These variables determine the build and compile flags that will be used for all package compilations. The CFLAGS variable is for C applications, while the CXXFLAGS one is meant for C++ ones. Most users will keep these variables identical. A "safe" configuration to avoid compilation errors should look like this:<blockquote><code>COMMON_FLAGS="-march=native -O2 -pipe"</code> <code>CFLAGS="${COMMON_FLAGS}"</code> <code>CXXFLAGS="${COMMON_FLAGS}"</code> <code>FCFLAGS="${COMMON_FLAGS}"</code> <code>FFLAGS="${COMMON_FLAGS}"</code></blockquote> ===== MAKEOPTS ===== The MAKEOPTS variable is used to specify arguments that will be passed to [[Make]] during compilation. A good rule of thumb is to set the -j argument to about half your RAM size and the -l argument to the thread count of your CPU, which can be found by running <code>nproc</code>. For example, if you have 4 GB of RAM and a 6th generation Intel Core i3, your MAKEOPTS variable should look something like this:<blockquote><code>MAKEOPTS="-j2 -l4"</code></blockquote> ===== GENTOO_MIRRORS ===== The GENTOO_MIRRORS variable tells Portage what mirror(s) to download the packages from. It can be set manually by editing the variable with a link to the mirror(s) of your liking available [https://www.gentoo.org/downloads/mirrors/ here], or automatically via <code>mirrorselect</code>, which can select the fastest mirror(s) for you. It's highly recommended to set this variable to a mirror close to you, for example, if you want to use an Italian mirror you would have to edit the variable like this:<blockquote><code>GENTOO_MIRRORS="<nowiki>https://gentoo.mirror.garr.it/</nowiki>"</code></blockquote> ===== FEATURES ===== The FEATURES variable contains a list of features that you can enable which notably alters the behavior of Portage. For example, if you want to use binary packages and verify their signatures, you would have to set the variable like this:<blockquote><code>FEATURES="getbinpkg binpkg-request-signature"</code></blockquote> ===== EMERGE_DEFAULT_OPTS ===== The EMERGE_DEFAULT_OPTS variable contains the options that will be automatically set when running Portage every time. For example, if you want Portage to ask for confirmation and verbose output, you would set the variable to this:<blockquote><code>EMERGE_DEFAULT_OPTS="--ask --verbose"</code></blockquote> ===== USE ===== The USE variable allows the '''system-wide''' enabling or disabling of USE flags. An example of this variable may look like this:<blockquote><code>USE="pulseaudio X systemd dbus policykit udisks dist-kernel -alsa -wayland xwayland"</code></blockquote> ===== USE_EXPAND ===== USE_EXPAND is a set of variables that serve to extend the capabilities of USE flags. Below are the most relevant ones. ====== VIDEO_CARDS ====== VIDEO_CARDS is a variable that serves to specify the drivers you wish to install for your GPUs. For example, if you want to install the drivers for AMD and Intel graphics, you would set the variable to this:<blockquote><code>VIDEO_CARDS="amdgpu radeonsi intel"</code></blockquote> ====== CPU_FLAGS_* ====== The CPU_FLAGS_* variables specify the available features that your CPU has to optimize compiling packages. The currently available variables are CPU_FLAGS_X86 (for x86 and x86_64 architectures), CPU_FLAGS_ARM (for ARM and ARM64 architectures) and CPU_FLAGS_PPC (for PowerPC and PowerPC64 architectures). The <code>cpuid2cpuflags</code> utility can be used to find these flags. The output of this command may look something like this:<blockquote><code>CPU_FLAGS_X86: aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3</code></blockquote>The output can then be copied to make.conf. ===== ACCEPT_LICENSE ===== The ACCEPT_LICENSE variable can be used to tell Portage which type of licenses are allowed. Generally, it's preferred to not accept proprietary software licenses. To allow every license except proprietary ones, you can set the variable to this:<blockquote><code>ACCEPT_LICENSE="* -@EULA"</code></blockquote> == References == [[Category:Package Managers]] 0d3ca52e218950a07e7397352758e73edb3be545 0 176 2991 2817 2025-07-26T17:21:07Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> [[Category:Desktop Environments]] 9f7ac26908dbea6cc6f9302ea74c6886619d0d1b 0 175 2992 1808 2025-07-26T17:21:18Z Atmois 13 Add references header wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Pacman 401.png|thumb|[[Pacman]]]] == Intro == The [[Linux Distributions|Linux distribution]] [[Arch Linux]] and its derivatives usually use a [[Package Manager|package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] == References == [[Category:Package Managers]] 528a19a139d9de7666147a10a0e57272382d7f2f 0 415 2993 2509 2025-07-26T17:21:44Z Atmois 13 Add references header wikitext text/x-wiki POSIX, a rewritten name that stands for "Portable Operating System Interface" in replacement for IEEE-IX for the IEEE Computer Society, is a set of standards for upkeeping compatibility across different [[Operating System|operating systems]] as it defines system & user-levels [[API|APIs]] in the addition of utility interfaces and command line shells for portability with [[UNIX|Unix]], Unix-Based/Like operating systems, and more.<ref>The Linux Code, November 1, 2023, ''POSIX: A Thorough Overview for Linux Developers — https://thelinuxcode.com/posix-standard/''</ref> === Modern Day POSIX Standards === There are many modern-day standards for POSIX, in order for a Unix-Based/Like operating system to POSIX-Compliant, it must provide implementations of the many POSIX APIs. These standards include the ability to use core services and/or processes properly: Core API Services and its processes, threads, signals, basic file I/O, as well as using [[Shell]] utilities such as bash and following commands like <code>grep</code> , <code>sort</code>, <code>find</code>, and plenty more. == References == <references /> 4d239c6034751a449119405ba08d55a42c122085 0 651 2994 2871 2025-07-26T17:22:00Z Atmois 13 Add references header wikitext text/x-wiki An operating system (OS) is a collection of [[software]] that manages a computer's [[hardware]] and [[applications]] by allocating resources, including memory, CPU, input/output devices and file storage.<ref>https://www.ibm.com/think/topics/operating-systems</ref> A user interacts with an operating system through a [[user interface]] (UI), which issues commands in a language the OS can understand. The UI can be either a [[graphical user interface]] (GUI) or a [[command-line interface]] (CLI). All computer systems need an OS to function. == References == 77c1d801af884578bd6ea1423f9bacb06a0c17e3 0 480 2995 2853 2025-07-26T17:22:12Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}} [[File:Oreon10-2502.png|thumb|Oreon 10 Core (Build 2502) running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>https://oreonproject.org/</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>https://git.oreonproject.org/rpms</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>https://boostyconnect.com/oreon-lime-r1-lifecycle/</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>https://oreonproject.org/oreon-lime-r2-support-timeline/</ref><ref>https://oreonproject.org/oreon-lime-r2/</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/</ref> and other well-known sources. In October 2024, Oreon celebrated its 1st anniversary on November 16, 2024, and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69</ref> Oreon 10 released to the public on December 12, 2024, shipping with KDE Plasma 6 and Linux 6.11<ref>https://forums.oreonproject.org/t/oreon-10-officially-released/98</ref> but was upgraded to 6.12 a few days later. A new update to Oreon 10 has been released on February 12, 2025, under the name "Build 2502." This update brought a few bug fixes along with some planned features for later such as Apple M-series Mac support.<ref>https://forums.oreonproject.org/t/oreon-10-build-2502-has-officially-released/150</ref> == References == <references /> [[Category:Linux Distributions]] cc5640800744e6066da1833da53c4259085e3d29 0 225 2996 2500 2025-07-26T17:22:32Z Atmois 13 Add references header wikitext text/x-wiki == Introduction == {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64 | website = [https://redhat.com/rhel/ redhat.com] }} [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business customers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. == References == <references /> [[Category:Linux Distributions]] 4be118877d01b6e2f512b9251a522a8b5c93a357 0 670 2997 2521 2025-07-26T17:22:48Z Atmois 13 Add references header wikitext text/x-wiki '''Regular Expression''', also known as '''Regex''' or '''RegExp''', refers to a type of pattern “used to match character combinations in strings”<ref>[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript], MDN, 2025 (Accessed 2025-06-20)</ref>. It is a very powerful tool for searching, matching, replacing, and parsing target text based on specific patterns. In other words, a ''regex engine''<ref>[https://www.regular-expressions.info/engine.html How a Regex Engine Works Internally], Jan Goyvaerts, 2019 (Accessed: 2025-06-20)</ref> can find, extract and substitute target text under a format defined by a given regex. Regex is not universally the same. Different flavours of regex are supported by different regex engines provided by different libraries and programming languages. However, a portion of the syntax is generally the same across them.<ref>[https://regex101.com/ regex101: build, test, and debug regex], regex101.com, 2025 (Accessed: 2025-06-20)</ref> == Usage == Regex is used in many text processing tools. Graphical examples include the find and replace feature in [[LibreOffice]]<ref>[https://help.libreoffice.org/25.2/en-US/text/swriter/guide/search_regexp.html?&DbPAR=SHARED&System=UNIX Using Regular Expressions in Text Searches], LibreOffice, 2025 (Accessed: 2025-06-20)</ref>. [[CLI|Command line]] examples include [[AWK]], [[sed]], and [[grep]]. Many popular scripting and programming languages provide built-in support for regex, notably [[JavaScript]], [[Perl]], [[Java]], [[Ruby]], [[Python]], [[C++]], [[PHP]], each with slighting varying implementations and different sets of supported syntax.<ref>[https://www.regular-expressions.info/tools.html Popular Tools, Utilities and Programming Languages That Support Regular Expressions], Jan Goyvaerts, 2021 (Accessed: 2025-06-21)</ref> == See Also == * [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript | MDN] * [https://regex101.com/ regex101: build, test, and debug regex] == References == [[Category:Terminology]] 6c5ae6302e8c3060d34a2af89025fe2877f35964 0 558 2998 2866 2025-07-26T17:23:07Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[C]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }}Rust, the programming language, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called "garbage collecting," where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety|# Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[Rust#Object-Orientated Programming in Rust|# Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├─src ; Contain all code for project | ├──main.rs ; Code is executed here ├─Cargo.toml ; Dependencies file ├─git.ignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!") } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { let var_name: i32 = 64; let mut another_var: i32 = 86; another_var = 128; // let declares a new variable, i32 is the type of the variable // but is not requred, then the value is given. // All variables end with a ";" } </syntaxhighlight>Using <code>let</code> defines a new variable. You are able to label the variable however you like; but, it is a good idea to give them simple and easy names for sake of other programmers and yourself. If you need to specify the type of value a variable is, you can write out <code>[var_name]: [type]</code> to declare a type, to see all types, see [[Rust#Variable Types|# Variable Types]]. By default, any variable defined is an '''immutable''' but using the <code>mut</code> term enables the variable to mutable, influenced by '''functional programming'''. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" line="1"> struct Values { Value1: bool, Value2: i32, Value3: String, // Value 4..., Value 5... } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: Values = Values { Value1: true, Value2: 64, Value3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { Length: i32, Width: i32, Height: i32 } // vvvvvv Cube implemented here vvvvvv impl Cube { fn Area(&self) -> i32 { self.Length * self.Width * self.Height // This returns the Cube's Volume } } fn main() { let RubiksCube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's Volume: {}", RubiksCube.Area()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an Area finder function within the <code>impl Cube</code> scope. We are able to use the <code>Area()</code> function on any Variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses "borrowing"; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing], Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == [[Category:Programming Languages]] 9e8a50c60b4ac1903cdba89bd9db9101d1278e58 0 668 2999 2858 2025-07-26T17:23:33Z Atmois 13 Add references header wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''.’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref> == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor [[ed]] (1971) and the even earlier [[qed]] (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command.<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref> sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; ...} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to [[EOF]]. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10–15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended [[regular expression]]s''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] == References == 7527f11e7f51301b4c2cbeaca9b5d012ead0e7cd 3032 2999 2025-07-29T18:20:46Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''.’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref> == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor [[ed]] (1971) and the even earlier [[qed]] (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command.<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref> sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; ...} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to EOF. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10–15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended regular expressions''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] == References == 1e127c27ef9e2fb5fe3e4c9c4ceea6060d15aeb4 0 304 3000 2614 2025-07-26T17:23:59Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a [[UNIX|UNIX-like]] [[Operating System|operating system]] completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS]</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive [[kernel]], and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[MacOS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[Virtual Machine|virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to [[Compiling|compile]] software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub]</ref> == References == [[Category:Misc Operating Systems]] 1eda030652aaa6ee1effe884402f1fd468d97a1f 0 233 3001 2078 2025-07-26T17:24:09Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with [[KDE Plasma|KDE]] * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. == References == [[Category:Linux Distributions]] 5a1596d068843511d0edf9575ffcb448e56827d2 0 309 3002 1819 2025-07-26T17:24:22Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png|thumb]] | caption = Sudo used on [[pacman]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.16p2, 2024-11-25 | languages = [[C]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} [[File:Sudo logo.png|thumb|335x335px|Sudo's logo of a sandwich]] [[File:Sudo Insults.png|thumb|335x335px|Output from sudo when <code>Defaults insults</code> is added]] The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]).<ref name=":0">[https://man7.org/linux/man-pages/man8/sudo.8.html sudo(8)], Linux Manpages</ref> Its name is shorthand for "su 'do'"<ref>[https://www.sudo.ws/ sudo.ws], Sudo Developers</ref>, however as <code>su</code> stands for "substitute user"<ref>[https://man7.org/linux/man-pages/man1/su.1.html su(1)], Linux Manpages</ref> this would stand for "substitute user, do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file<ref name=":0" /> to specify which users or groups can execute specific commands. == Usage == {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |Run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser''<ref name=":0" /> == Trivia == * Sudo's logo is a sandwich in reference to [https://xkcd.com/149/ xkcd 149]<ref>[https://www.sudo.ws/about/logo/ sudo.ws/about/logo], Sudo Developers</ref> * If you add the line <code>Defaults insults</code> to the Defaults section of <code>/etc/sudoers</code>, you will be insulted whenever you type the wrong password.<ref>[https://www.geeksforgeeks.org/when-sudo-insults-you/ When sudo insults you!!], GeeksforGeeks, September 13, 2023 (February 12, 2025)</ref> == References == [[Category:Software]] 96135e35701ab047a2dcc5d56cb2493d2a18ed3b 0 663 3003 2923 2025-07-26T17:25:33Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terra.fyralabs.com terra.fyralabs.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora]] Linux and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terra.fyralabs.com/ Terra], Terra, 2024 (Accessed: 2025-06-19)</ref> Developed by Fyra Labs, it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://developer.fyralabs.com/terra/infrastructure How Terra Works], Fyra Labs, 2025 (Accessed: 2025-06-19)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://developer.fyralabs.com/terra/installing. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji], RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://developer.fyralabs.com/terra/autoupdate Automatic Updates - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases :: Fedora Docs], Fedora, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably Rust, Go, [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://developer.fyralabs.com/terra/policy Policy – Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> == See Also == * [https://terra.fyralabs.com Main Website] * [https://developer.fyralabs.com/terra Fyra Developer Documentations for Terra] * [https://github.com/terrapkg/packages Terra Sources] == References == 403e999445a90542edb3239455919854d75e96b5 0 214 3004 2850 2025-07-26T17:25:46Z Atmois 13 Add references header wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Tux | image = [[File:Tux.svg|frameless|size=200px]] | caption = Tux! }} '''Tux''' is the official mascot of [[Linux]], designed by Larry Ewing.<ref>https://web.archive.org/web/20040401161253/http://www.linux.org/info/logos.html</ref> Tux was created for the Linux 2.0 logo competition.<ref>https://web.archive.org/web/20040407092622/http://www.cs.earlham.edu/~jeremiah/linux-pix/linux-logo.html</ref> == References == <references /> [[Category:Mascots]] f7e348edac5e18490308896811df07877489397f 0 248 3005 2842 2025-07-26T17:26:00Z Atmois 13 Add references header wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu Logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[GNOME]], [[Unity]] | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu is a highly popular [[Linux Distributions|Linux distribution]] derived from [[Debian]] and developed by Canonical for the commercial market. The first version of Ubuntu was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS version receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubuntu receive 9 months of support.<ref>https://ubuntu.com/about/release-cycle Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> Ubuntu can be run locally, on a cloud, or in a [[Virtual Machine|VM]]. Ubuntu comes packaged with basic GNOME utilities as default and additionally from Ubuntu Software (formally Ubuntu Software Centre) and from APT, Ubuntu's default package manager. == References == <references /> [[Category:Linux Distributions]] 80f26a5b41ebba41692ad680d0f2d283837bb571 0 317 3006 2849 2025-07-26T17:26:25Z Atmois 13 Add references header wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm]</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and [[Musl]] variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses runit as its init system, offering: * Simple service management * Clean daemon supervision * Fast boot times {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == [[Category:Linux Distributions]] 658e8d74cae3f1ad77bac09c1e71df7c5f22d150 3018 3006 2025-07-26T21:56:33Z Ow0cast 249 cleanup | semi-auto, removing duplicate links wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm]</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and Musl variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses runit as its init system, offering: * Simple service management * Clean daemon supervision * Fast boot times {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == [[Category:Linux Distributions]] 492bbca2967bc82c6447484eaea27c8971e13a36 0 281 3007 2607 2025-07-26T17:26:34Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox|caption=Window Maker and GNUstep logo|developers=Window Maker developers|image=[[File:GNUstep logo.png|200px|GNUstep_logo]]|languages=[[C]]|lastrelease=0.96.0, 2023-08-05|releasestatus=Maintained|title=Window Maker|website=[https://windowmaker.org/ windowmaker.org]}} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home] official Window Maker Website, 2025 (Imported 16th June 2024)</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home] Dockapps Website, 2025 (Imported 16th June 2024)</ref> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more. == References == <references /> [[Category:X_Window_Managers]] 55d4e224c6e2fe8a1b6851c9d318b43146c2bc86 0 643 3008 2854 2025-07-26T17:26:50Z Atmois 13 Add references header wikitext text/x-wiki {{SoftwareInfobox |title = XBPS |releasestatus = Maintained |lastrelease = 0.59.2, 2023-08-18 |firstrelease = 0.1beta1, 2009-08-17 |languages = [[C]] |developers = [[Void Linux]] |website = [https://github.com/void-linux/xbps github.com/void-linux/xbps] }} == Intro == The ''X Binary Package System'' (XBPS) is developed by the maintainers of [[Void Linux]] and is the package manager for their distribution. It was built from scratch, with the goals of speed, ease of use while being feature rich and portable. It is fully compatible with POSIX, SUSv2 and C99 standards<ref>https://github.com/void-linux/xbps#xbps</ref>, and is released under the BSD 2-Clause (Simplified) license ([https://spdx.org/licenses/BSD-2-Clause.html SPDX: BSD-2-Clause]). == Tools == XBPS is comprised of a number of utilities that provide different functionality, the ''core'' utility programs are as follows (not a complete list): {| class="wikitable" !<u>Name</u> !<u>Function</u> |- |xbps-create |Creating binary packages |- |xbps-dgraph |Generating graphs for tools like [https://graphviz.org GraphViz] |- |xbps-install |Installing and updating packages |- |xbps-pkgdb |Reporting and fixing issues with the package database |- |xbps-query |Querying package and repository information |- |xbps-reconfigure |Configuration of installed package (e.g., the system C library or Linux kernel) |- |xbps-remove |Removing packages |- |xbps-rindex |Handling local package repositories |} == Usage<ref>https://github.com/void-linux/xbps?tab=readme-ov-file#examples</ref> == {| class="wikitable" !<u>Command</u> !<u>Description</u> |- |<code>xbps-install -Su</code> |Synchronize with repositories and apply all available updates |- |<code>xbps-query -Rs <name></code> |Search through repository packages using the given name |- |<code>xbps-install <package></code> |Install a package by name |- |<code>xbps-remove -R <package></code> |Remove a package by name; along with its dependent packages which are no longer needed by the system |- |<code>xbps-query -Rf <package></code> |List files owned by a package |- |<code>xbps-query -Ro /usr/bin/ls</code> |Find the package(s) that own/provide a file path, (e.g., the 'ls' command) |- |<code>xbps-reconfigure -f glibc-locales</code> |Regenerate your locale(s) when using a GLIBC based system<ref>https://man.voidlinux.org/xbps-reconfigure</ref> |} == References == a560bfb5e4da72b42cf262eb808f2fdc4814bc53 0 236 3009 2665 2025-07-26T17:27:05Z Atmois 13 Add references header wikitext text/x-wiki {{Needs_Citations}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.20, 2024-12-15 | languages = [[C]] | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight [[Desktop Environments|desktop environment]] aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * [[Desktop Manager]] - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[TUI|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>https://xfce.org/about</ref> == References == [[Category:Desktop Environments]] a4fc112f93010ac705f0334fc53b6b3dd663f216 0 586 3010 2760 2025-07-26T17:27:22Z Atmois 13 Add references header wikitext text/x-wiki {{MascotInfobox | title = Xenia (Linux Fox) | image = [[File:Xenia the Linux Fox.gif]] | caption = The original design of Linux Fox, created by Al Mackey in 1996 }} Xenia was a candidate logo and [[:Category:Mascots|mascot]] for the [[Linux]] project. She was a competitor to [[Tux]], who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds)<ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ Why the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!], Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson.<ref>[https://archive.is/wYsFh Penguins and Other Things], Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on [[Gentoo]].<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> == References == <references /> [[Category:Mascots]] 4b746884eb82e798d36adb91692b2879f5ae205f 3000 577 3012 1967 2025-07-26T17:29:55Z Atmois 13 Add references header wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>https://repology.org/project/emacs/versions</ref> and can be installed from Canonical's Snap<ref>https://snapcraft.io/emacs</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. == References == aea3d58b922e3026c4e259c5af4e0fd987d7f2f5 3000 639 3013 2326 2025-07-26T17:30:05Z Atmois 13 Add references header wikitext text/x-wiki {{Guide Warning}} == Formatting a partition to ext4 == Assuming the partition you want to format is called /dev/sdX, do: <pre> mkfs -t ext4 /dev/sdX # or mkfs.ext4 /dev/sdX </pre> The e2fsprogs package must be installed. == Setting mount options == You can set mount options for ext4 either by modifying <code>/etc/fstab</code> or <code>tune2fs</code><ref>[https://linux.die.net/man/8/tune2fs tune2fs]</ref> For example, to enable <code>noatime</code> on your filesystem, do: <pre> tune2fs -o noatime /dev/sdX </pre> == Using an external journal == Ext4 allows you to use an external journaling device paired with a partition that actually stores your data. To create a **new** partition with an external journal at /dev/sdb2, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> To convert a pre-existing filesystem, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> == Feature flags == Ext4 has tons of feature flags that can be enabled using the <code>tune2fs</code> utility, a list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. To enable a feature flag, do: <pre> tune2fs -O flag /dev/sdX </pre> Some common feature flags used often are <code>encrypt</code> and <code>fast_commit</code>. == References == <references /> 181c8bb263976b6ac3bcd67baf57ef4eede3c348 3000 608 3014 2274 2025-07-26T17:30:46Z Atmois 13 Add references header wikitext text/x-wiki {{GuideWarning}} Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">[https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims Localization, Internationalization and Multilingualization], Ultramarine Linux, 2024 (Accessed: 2025-05-03)</ref> Users can use the IMF to switch between different IMEs.<ref>[https://wiki.archlinux.org/title/Input_method Input method], ArchWiki, 2020 (Accessed: 2025-05-03)</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>[[wikipedia:Intelligent_Input_Bus|Intelligent_Input_Bus]], Wikipedia, 2009 (Accessed: 2025-05-03)</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>[[wikipedia:Fcitx|Fcitx]], Wikipedia, 2010 (Accessed: 2025-05-03)</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code><ref name=":0" group="Note">Additionally requires <code>fcitx5-chinese-addon</code> on Fedora due to packaging issues.</ref> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code><ref name=":0" group="Note" />? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code><ref group="Note"><code>fcitx5-mozc-ut</code>^AUR is instead recommended on Arch Linux.</ref> |<code>fcitx-mozc</code><ref group="Note"><code>fcitx-mozc-ut</code>^AUR is instead recommended on Arch.</ref> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |ViQR |<code>fcitx5-m17n</code><ref name=":1" group="Note">This is <code>fcitx5-table-viqr</code>, <code>fcitx-table-viqr</code>, <code>ibus-table-viqr</code> on Debian.</ref> |<code>fcitx-m17n</code><ref name=":1" group="Note" /> |<code>ibus-table-tv</code><ref name=":1" group="Note" /> |<code>uim-viqr</code> | - | - | - | - | - |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<code>uim-m17n</code><ref name=":2" group="Note">On some distros, this is <code>uim-m17nlib</code>.</ref> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code><ref group="Note">Requires the [[Terra]] repository on Fedora.</ref> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code><ref group="Note"><code>ibus-openbangla</code> on Fedora with the [[Terra]] repository.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<code>fcitx5-varnam</code> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Others |- |Thai |<code>fcitx5-libthai</code> | - |<code>ibus-table-tv</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> | - |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Math Symbols |[[Compose Key]]? |[[Compose Key]]? |<code>ibus-table-mathwriter</code> | - | - | - | - | - | - |- |Completion |''built-in'' | - |<code>ibus-typing-booster</code> | - | - | - | - | - | - |- |''"Everything Else"'' |<code>fcitx5-m17n</code>? |<code>fcitx-m17n</code>? |<code>ibus-m17n</code>? |<code>uim-m17n</code><ref name=":2" group="Note" />? | - |<code>scim-m17n</code>? | - | - | - |} === Notes === <references group=Note/> This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. == How to choose your IME == This section represents the general case and the authors' opinions. It is not necessary to follow them. {| class="wikitable" |+Chinese !Situation !IME !Rime IME !Notes |- |Already using [[Rime]] | rowspan="3" |Rime | - | rowspan="3" |Rime is very powerful, but it comes with the cost of writing your own configuration files and [https://github.com/rime/home/wiki reading Chinese documentations], and thus is not recommended to beginners. |- |Prefer a highly customizable experience | - |- |Good at writing configuration files | - |- |Know Pinyin |Pinyin |''built-in'' | |- |Know Zhuyin |Chewing |℞ bopomofo |<code>libzhuyin</code> is not recommended (very unpopular), avoid <code>fcitx5-zhuyin</code> & <code>ibus-libzhuyin</code>. |- |Know Cangjie 3 / Quick 3 | rowspan="2" |Cangjie/Quick | rowspan="2" |℞ cangjie |Rime with [https://github.com/kennethso168/rime-cangjie3-extension rime-cangjie3-extension] |- |Know Cangjie 5 / Quick 5 | |- |Know SmartCangjie 6 |SCJ |℞ scj | |- |Know Jyutping |Rime |℞ cantonese |Jyutping from table-extras is barely usable |- |Know Wubi |Haifeng Wubi | |https://www.zhukun.net/archives/4856 |} {| class="wikitable" |+Japanese !Situation !IME !Notes |- |You hate Qt |Anthy |Anthy is unmaintained but it's written in GTK, so if you want your IME to fit into your GTK theme, use Anthy. |- |Otherwise |Mozc |Mozc is maintained by Google and has better suggestions, but you should also consider using the UT dictionaries. |} == References == 61631bcfcb2c37a1b6a169ca58bffb89358de8af 3000 684 3015 2575 2025-07-26T17:30:58Z Atmois 13 Add references header wikitext text/x-wiki This section will change overtime, as such, you should probably follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only</ref> and for a manual build install<ref>https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>https://wiki.hyprland.org/Configuring/Configuring-Hyprland/</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. == References == f1e6b7eadfc290d1689569d9b93de4cbd4d67a69 3000 685 3016 2578 2025-07-26T17:31:10Z Atmois 13 Add references header wikitext text/x-wiki IceWM can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions:<syntaxhighlight lang="bash">$ sudo apt install icewm </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions:<syntaxhighlight lang="bash"> $ sudo pacman -S icewm </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/icewm </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> $ sudo dnf install icewm </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (3.5.1) by running:<ref>https://ice-wm.org/ Official Website, 2025 (Fetched 24th June 2025)</ref><syntaxhighlight lang="bash"> $ wget https://github.com/ice-wm/icewm/releases/download/3.5.1/icewm-3.5.1.tar.lz $ tar -x --lzip -vpf icewm-3.5.1.tar.lz $ cd icewm-3.5.1 $ ./configure --prefix=/usr $ make $ sudo make install </syntaxhighlight> == References == 8801b34730832e6371771c992b203975734e73b1 3000 573 3017 2774 2025-07-26T17:32:14Z Atmois 13 Add references header wikitext text/x-wiki {{Guide Warning}} [[Flathub]] is a third party [[repository]] of applications that are packaged in the [[Flatpak]] format. By default, [[Fedora]] does not include the Flathub repository<ref>[https://developer.fedoraproject.org/deployment/flatpak/flatpak-usage.html Flatpak Usage On Fedora], Felipe Borges, Jarek Prokop, John Atti, Nick Dirschel, Pavel Valena, 2018 (Retrieved 22nd March 2025)</ref>. Some Flathub apps are also in the main Fedora repositories, but in some cases it ships newer versions or applications that aren’t available in the Fedora repositories<ref>[https://fedoramagazine.org/install-flathub-apps-fedora/ Installing Flathub Apps on Fedora], Ryan Lerch, 2018 (Retrieved 22nd March 2025)</ref>. You can set up Flathub graphically via the repository file, GNOME Software or KDE Discover. Alternately, you can set it up through the command line. The recommended method is via the Flathub repository file or the terminal: ====== Installing Flathub via the Flathub Repository File (Recommended) ====== [[File:GNOMESoftwareFlathubFile.png|thumb|GNOME Software GUI when Flathub Repo File has been opened via File Manager]] # Visit [https://flathub.org/setup/Fedora flathub.org/setup/Fedora] and select the text saying <code>Flathub Repository File</code> to download <code>flathub.flatpakrepo</code>. # Open your file manager and double-click the <code>flathub.flatpakrepo</code> file. It will open KDE Discover or GNOME software. # Select the <code>Install</code> button, you may need to log out and log back in to Fedora for Flathub apps to appear. ====== Installing Flathub via GNOME Software ====== [[File:SoftwareReposGNOMESoftware.png|thumb|Image of Flathub being enabled in GNOME Software.]] # Open GNOME software and select the hamburger menu on the top right of the application and select <code>Software Respositories</code>. You can also use the key bind <code>RightCtrl + .</code> to open the menu. # Scroll down and enable the toggle for <code>Flathub</code> and the toggle for <code>Enable New Repositories</code>. # You may need to log out and log back into Fedora or run <code>gnome-software --quit</code> in your terminal for Flathub apps to appear in GNOME software. ====== Installing Flathub via the KDE Discover ====== [[File:DiscoverKDEFlathubRepo.png|thumb|328x328px|How the Flatpak section should look after finishing on KDE Discover]] # Open KDE discover and open the settings menu on the left of your screen. # Select the <code>Flathub - ''dl.flathub.org''</code> option. # Click the up arrow until Flathub is at the top of the list to make it the primary source, then click apply changes at the top of KDE Discover. # You may need to log out and log back into Fedora for Flathub apps to appear in KDE Discover. ====== Installing Flathub via the Command Line ====== # Open your terminal of choice. # Run the command <code>flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki></code>. # You may need to log out and log back into Fedora for Flathub apps to appear in GNOME software or KDE Discover. == References == <references /> df46465e4aca59780dccd0b499e4d16523cdf95e 0 428 3019 2979 2025-07-26T21:58:15Z Ow0cast 249 cleanup | semi-auto, removing duplicate links wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' (short for ''manual'') is a [[TUI|command-line]] utility available on [[UNIX]] and UNIX-like [[Operating System|operating systems]] that provides documentation for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a man page the user can enter the following into their terminal:<ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> man ''<command_name>'' For example, to read the manual for <code>man</code> command itself: man man == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER<code> environment variable. By default, it uses <code>less<code>. Alternatively, the </code>-P</code> or </code>--pager</code> option can be used.<ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally.<ref>https://fishshell.com/docs/current/faq.html</ref> == References == <references /> 56a84e462c2d6f775262457841902ce58a33a035 0 269 3020 2682 2025-07-26T21:58:30Z Ow0cast 249 cleanup | semi-auto, removing duplicate links wikitext text/x-wiki {{Needs Citations}}{{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], Budgie provides an easy to use Interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] === Features === '''Budgie Desktop View''' is a [[:Category:Software|software]] component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in C, and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. [[Category:Desktop Environments]] 1b4015ccbb24c8871d73aab9775175f56dd31ba9 0 8 3021 2445 2025-07-27T09:09:58Z Kelsy 29 /* Advanced Terms */ wikitext text/x-wiki {{Work In Progress}} == Introduction == New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 31848fc5b334e1cfdf02a208a99b50e448601c89 4 340 3022 2925 2025-07-27T10:19:08Z Atmois 13 Add alt text formatting guidelines wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. ; Pages Correctly Located and Categorised : Pages align with the [[Guides:Contributing|guides policy]], must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] a2d7d12548f03703de21a7c70ee5422e39de7ca4 0 736 3023 2948 2025-07-28T07:04:12Z Imnotgoodatnames 121 Corrected info about sed wikitext text/x-wiki [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s s/regexp/replacement command was inherited from ed. ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor [[vi]], whose variants remain some of the most popular TUI text editors. == References == 681d44f5aa2e9bea09ebda66a6cbdf5f9de3ea38 3024 3023 2025-07-28T07:13:33Z Imnotgoodatnames 121 Added citations wikitext text/x-wiki [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s s/regexp/replacement command was inherited from ed.<ref>https://www.gnu.org/software/ed/manual/ed_manual.html</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor [[vi]], whose variants remain some of the most popular TUI text editors.<ref>https://ex-vi.sourceforge.net/ex.html</ref><ref>https://ex-vi.sourceforge.net/vi.html</ref> == References == f7430103c97b395c7f33e00e142f8badaf24e0a4 3029 3024 2025-07-29T18:09:53Z Imnotgoodatnames 121 Changed page title from "Ed" to "ed" wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s s/regexp/replacement command was inherited from ed.<ref>https://www.gnu.org/software/ed/manual/ed_manual.html</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor [[vi]], whose variants remain some of the most popular TUI text editors.<ref>https://ex-vi.sourceforge.net/ex.html</ref><ref>https://ex-vi.sourceforge.net/vi.html</ref> == References == 250a312ba811d9dc24a835b247e92bdf372af09b 3030 3029 2025-07-29T18:14:27Z Imnotgoodatnames 121 added to software category wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s s/regexp/replacement command was inherited from ed.<ref>https://www.gnu.org/software/ed/manual/ed_manual.html</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor [[vi]], whose variants remain some of the most popular TUI text editors.<ref>https://ex-vi.sourceforge.net/ex.html</ref><ref>https://ex-vi.sourceforge.net/vi.html</ref> == References == [[category:software]] 85d06a41d10673a0db961b2a032052fda8db7cd3 3034 3030 2025-07-29T18:27:59Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html</ref> ed was part of the original Unix operating system from 1969.<ref>https://man.cat-v.org/unix-1st/1/ed</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s s/regexp/replacement command was inherited from ed.<ref>https://www.gnu.org/software/ed/manual/ed_manual.html</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor vi, whose variants remain some of the most popular TUI text editors.<ref>https://ex-vi.sourceforge.net/ex.html</ref><ref>https://ex-vi.sourceforge.net/vi.html</ref> == References == [[category:software]] 66b74a85fb185aa740e4515a53e6e76f5bb26de9 8 456 3025 1549 2025-07-28T16:36:39Z Atmois 13 Change role title wikitext text/x-wiki Autoconfirmed Users 377e649acadd50ac9fbbcf55d5fa6f6f4f08dcee 8 457 3026 1548 2025-07-28T16:36:50Z Atmois 13 Change role title wikitext text/x-wiki {{GENDER:$1|Autoconfirmed User}} bd63162c7bbc263e6c84ce08b6371deec76d3071 0 178 3027 2972 2025-07-29T17:45:03Z Mawfyy 184 I added the linux main source code wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] Linux in itself refers to two entities, the former being the [[kernel]] itself developed by Linus Torvalds and the latter being the families of [[Linux Distributions|Operating Systems based off the Kernel]]. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look [https://www.kernel.org/<nowiki> here]. </nowiki> == References == <references /> [[Category:Terminology]] 8987ab028678102e5f6498b624eddfbe503472c1 3028 3027 2025-07-29T17:54:18Z Mawfyy 184 wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] Linux in itself refers to two entities, the former being the [[kernel]] itself developed by Linus Torvalds and the latter being the families of [[Linux Distributions|Operating Systems based off the Kernel]]. <ref>Edward, Jackson W. ''Linux+ Guide to Linux Certification,'' p. 33. [https://books.google.com/books?id=EHLH4S78LmsC&pg=PA33]</ref> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> [[Category:Terminology]] cfe255b2ba792dcba23445f262cedfa5a622905c 0 574 3031 2079 2025-07-29T18:20:14Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes great inspiration from i3 in its design and configuration, and, consequently, it is very compatible with i3. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[Swayfx]] is a fork of Sway that adds cool effects, animations, and visuals to it, something you may want to look into. === Notable Features: === According to Sway's official website: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. == Pre-Installation: == * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] == Installation: == ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For Arch: ==== Using pacman: sudo pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For Debian: ==== Using apt package manager: apt install sway b2bdd955ce6f6629a0010a0c51cf3bf5174360a8 0 198 3033 2973 2025-07-29T18:27:46Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AIX]] |A series of Unix-Based Operating systems for Power servers. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] 641f3f42b7c296a9a566a3a2987cb75f657edd9d 0 223 3035 2865 2025-07-29T18:28:22Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{Needs Citations}} == Distrohopping == Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (e.g. FSF approved distribution) * Ecosystem or Tooling (e.g. libc, [[Package Manager|package manager]], coreutils, [[Init System|init system]]) * Experimentation * Customization ... and many more. This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (e.g. Debianisms, package managers, init systems) * Opinionated design philosophies (e.g. Nix, Guix, Fedora Atomic) * Additional configuration needs (e.g. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (e.g. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (e.g. Liberapay, GitHub sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] c835eb40808ebc841115418a1ad4cf31709489df 0 628 3036 2975 2025-07-29T18:29:03Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>https://linuxmint.com/</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>https://iso.atl.dev/l/linuxmint</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>https://distrowatch.com/table.php?distribution=mint</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>https://www.linuxmint.com/about.php</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. The latest release, Linux Mint 22.1 "Xia", was launched in January 2025 and is supported until 2029.<ref>https://www.linuxmint.com/download.php</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>https://repo.c48.uk/mint/pkgs/pool/</ref> == References == 13a8d1ce5064a80a8c6f3bc1242a5afe69609a1c 3045 3036 2025-07-29T18:48:41Z Ow0cast 249 improvements | add infobox wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[apt]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>https://linuxmint.com/</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>https://iso.atl.dev/l/linuxmint</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>https://distrowatch.com/table.php?distribution=mint</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>https://www.linuxmint.com/about.php</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. The latest release, Linux Mint 22.1 "Xia", was launched in January 2025 and is supported until 2029.<ref>https://www.linuxmint.com/download.php</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>https://repo.c48.uk/mint/pkgs/pool/</ref> == References == 6884d6d0f14b2598cc7fda6e073bc6241b7ea9b8 0 169 3037 2869 2025-07-29T18:29:50Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [https://rpm.org/ rpm] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] [[Category:Terminology]] 9c8cc1a29ea67504943bd19e3a75566cd013bfad 0 228 3038 2934 2025-07-29T18:30:27Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}} The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. [[Package|Packages]] that enter the extra repository can be directly installed with pacman.<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with AUR helpers. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, AUR helpers have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, pacman is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability. == References == <references /> [[Category:Terminology]] aaf49a08e8b75428e6452d48cae4162ddb1c29d2 0 263 3039 2963 2025-07-29T18:31:25Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.99.0, 2024-10-24 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|thumb|The Hyfetch Pride Month easter egg.]] Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your [[Operating System|operating system]], [[:Category:Software|software]] and [[hardware]] with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch Hyfetch Github 2025 (fetched 24th June 2024)</ref> === Features === Due to Hyfetch being a direct fork of Neofetch, many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of Neofetch bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. == References == <references /> [[Category:Software]] f6df98179bba9989daa18080534179fb30ec564e 0 674 3040 2962 2025-07-29T18:32:51Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Searching for “PATTERNS” or “regex” in <code>grep --help</code> | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU grep: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, grep's creation stemmed from Thompson's need to analyse text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed]] text editor into a standalone tool. He named the tool ''grep'' because in ed, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into grep, which finds all lines with the text “error”. However, grep itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended regular expressions'' (ERE), while the lack of so only allows ''basic regular expressions'' (BRE), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=sh> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Examples == === Finding Python Function Calls === In a [[Python]] codebase, we can find all calls to functions under the <code>subprocess</code> module with <code>shell=True</code>: $ grep -r --include='*.py' -nHE 'subprocess\.\w+\([^)]*shell=True' ./driver.py:69: return subprocess.call("lspci | grep -q -i NVIDIA", shell=True) == 0 ./driver.py:202: return subprocess.call("lspci | grep -q -i Network | grep -q -i Broadcom", shell=True) == 0 ./driver.py:211: return subprocess.call("lspci | grep -q -i Bluetooth | grep -q -i Broadcom", shell=True) == 0 ./util.py:38: proc = subprocess.Popen(f"chroot {chroot} /tmp/stellar-payload.sh", shell=True) ./util.py:63: # proc = subprocess.Popen(payload, shell=True) ./util.py:66: proc = subprocess.Popen(f"pkexec {tmpfile}", shell=True) (This is run on the [https://github.com/Ultramarine-Linux/stellar/ Ultramarine stellar codebase]) We can breakdown the flags used in this example: * <code>-r</code>: find files recursively (by default in the current working directory) * <code>--include='*.py'</code>: only examine Python files * <code>-n</code>: show line numbers * <code>-H</code>: show file name * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] We can divide the pattern <code>subprocess\.\w+\([^)]*shell=True</code> into many parts: # <code>subprocess</code> matches the string “subprocess” literally; # <code>\.</code> matches the full stop literally; # <code>\w+</code> matches word characters one or more times, where a word character (<code>\w</code>) is any letter, digit or underscore<ref>[https://www.regexroo.com/word-characters Understanding \w and Its Counterpart \W in Regex], RegexRoo.com, 2025 (Accessed: 2025-06-21)</ref>; # <code>\(</code> matches for an open parenthesis <code>(</code> literally; # <code>[^)]*</code> is an inverse character group and matches any characters that are not the closing parenthesis <code>)</code> zero or more times; and # <code>shell=True</code> matches the string “shell=True” literally. === Finding Code Files with TODOs and FIXMEs === We can list out code files that contains both the word “FIXME” and “TODO”. For a Rust project: $ grep -rlZ 'FIXME' --include='*.rs' . | xargs -0 grep -l 'TODO' ./src/pages/_15_installing.rs ./src/main.rs Flags: * <code>-r</code>: find files recursively (by default in the current working directory) * <code>-l</code>: output matching files' names only * <code>-Z</code>: instead of a new line character, print out a null character after each filename * <code>--include='*.rs'</code>: only examine Rust files In this example, the first command outputs the filenames with null separates, then [[xargs]] is used to feed the filenames into the second grep command, which searches for “TODO”s in those files. === Extracting All Unique Public IPv4 Addresses from Log Files === We can extract all the unique IPv4 addresses from a directory of log files, but exclude any private IP addresses, such as <code>10.x.x.x</code> / <code>192.168.x.x</code>: <syntaxhighlight lang=sh> grep -rhoE '([0-9]{1,3}\.){3}[0-9]{1,3}' /path/to/logs | sort -u | grep -vE '^10\.|^192\.168\.' </syntaxhighlight> Flags: * <code>-r</code>: find files recursively * <code>-h</code>: suppress printing of filenames * <code>-o</code>: show only matching part of line * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] * <code>-v</code>: select non-matching lines For the first pattern: # <code>[0-9]</code> matches the digits (0 to 9 on the ASCII table includes all digits), and <code>{1,3}</code> specifies the length must be between 1 and 3; and # <code>([0-9]{1,3}\.){3}</code> matches exactly 3 times the above followed by a full stop. For the second pattern: # <code>^10\.</code> matches for lines starting with <code>10.</code>; # <code>^192\.168\.</code> matches for lines starting with <code>192.168.</code>; and # <code>|</code> (which indicates “or”) allows matching for the regex specified on the left or the right. Due to the invert flag (<code>-v</code>), if a line matches the second pattern, it is excluded, and other lines are printed instead. == Alternatives == Faster implementations of grep such as '''[[ripgrep]]''' (<code>rg</code>) and '''[[hypergrep]]''' (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU grep, and usually not pre-installed on most distributions. The '''<code>agrep</code>''' tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] == References == cd85f267e69f7935afe14074190d2bbbe8232c5a 0 322 3041 2419 2025-07-29T18:33:08Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{Needs Citations}} == musl == {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the [[Linux|Linux kernel]], released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on [[Operating System|Operating Systems]] === [[Linux Distributions|Linux distributions]] which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * [[Sabotage]] * [[Morpheus Linux]] * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against glibc. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] [[Category:Software]] 95177e812f063ef4239c414e39d9c54a34b17166 0 441 3042 2958 2025-07-29T18:33:30Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,")<ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU], The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> is a dedicated organization for free [[:Category:Software|software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone [[Operating System|operating system]] because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or [[Proprietary software|proprietary]]: A few are GNU/[[Linux]], [[MacOS]], [[UNIX|Unix-based]]/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the proprietary software of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe. </ref> == Included Software / Components == [[File:Gnu compiler collection-logo-1.png|alt=This logo depicts a Bull shaped animal jumping out of an egg, in black text that displays the letters G, C, C|left|thumb|224x224px|A logo of the GCC.]] As of June 2024, the GNU project currently holds 394 active [[packages]], but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. Overall, these components are in many operating systems, mainly because of how easy GCC is to access for any developer. Because of Richard Stallman, he was able to open source the variety of tools and software developed for the GNU project and in turn, pushed forward for the movement of open and free software for all.<ref name=":0" /> == History of GNU == [[File:RichardStallman.jpg|alt=A Picture of Richard Matthew Stallman in 2024|thumb|341x341px|A Picture of Richard Matthew Stallman in 2024]] Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref name=":0">[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible [[architecture]] because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs.<ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> == References == <references /> 9c2d3c3b30dae037b53e5972bf165388b3908ab4 0 233 3043 3001 2025-07-29T18:33:42Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with KDE * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. == References == [[Category:Linux Distributions]] c41497dbfb14a0637bcdd2ead98f0af127ed1700 6 754 3044 2025-07-29T18:47:12Z Ow0cast 249 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 755 3046 2025-07-30T15:08:20Z Imnotgoodatnames 121 nvi text editor in Ex mode. wikitext text/x-wiki == Summary == nvi text editor in Ex mode. == Licensing == {{PD}} a60198ec57eea0cb55d99184c05dca6b40dd294a 0 756 3047 2025-07-30T15:11:40Z Imnotgoodatnames 121 Created page. wikitext text/x-wiki {{DISPLAYTITLE:ex}} [[File:Exedit.png|thumb|nvi text editor in Ex mode]] Ex is a text editor developed for [[UNIX|Unix]] systems in 1976 as a modified version of em, which was an improved version of the original Unix text editor [[ed]].<ref>https://ex-vi.sourceforge.net/ex.html</ref> Like ed, ex is a line editor, meaning commands can only be executed on one line at a time. Ex was eventually modified into a screen editor and became [[vi]]. Modern versions of ex are rarely distributed on their own, but are rather line editor modes of vi text editors.<ref>https://man.netbsd.org/ex.1</ref> == References == [[category:software]] f705b4955e63fe008a32319a547a44650b9b7793 3048 3047 2025-07-30T16:07:09Z Imnotgoodatnames 121 Added citations, removed bad citation wikitext text/x-wiki {{DISPLAYTITLE:ex}} [[File:Exedit.png|thumb|nvi text editor in Ex mode]] Ex is a text editor developed for [[UNIX|Unix]] systems in 1977 as a modified version of em, which was an improved version of the original Unix text editor [[ed]].<ref>https://man.freebsd.org/cgi/man.cgi?query=vi&manpath=FreeBSD+14.3-RELEASE</ref><ref>https://web.archive.org/web/20240621040052/https://www.groklaw.net/article.php?story=20050422235450910</ref> Like ed, ex is a line editor, meaning commands can only be executed on one line at a time. Ex was eventually modified into a screen editor and became [[vi]]. Modern versions of ex are rarely distributed on their own, but are rather line editor modes of vi text editors.<ref>https://man.netbsd.org/ex.1</ref> == References == [[category:software]] 2cf8a09351b0640830a9b06e526045e9eaa26ec2 0 757 3049 2025-07-31T17:42:23Z Ow0cast 249 redir | syscall -> syscalls wikitext text/x-wiki #REDIRECT [[Syscalls]] 8e129b41374ab6567708c2dac7915e0da94ccb98 4 593 3050 2749 2025-07-31T20:51:02Z Atmois 13 Add mention of notability standards wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making atl.wiki an amazing resource for all users of Linux and FOSS related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''atl.wiki''' uses. For users interested in writing guides for '''atl.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''atl.wiki''' or All Things Linux you can visit our [https://allthingslinux.org website] or see the [[ATL:About|about]] page! Some important pages are also listed below: * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[ATL:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer If you ever have any questions or need help, you can join [https://discord.gg/linux All Things Linux's Discord Server] and check out #atl-wiki for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''atl.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''atl.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''atl.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[ATL:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''atl.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another compatible free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[ATL:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it meets the standards of the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * All changes must be approved by staff for public viewing via ApprovedRevs (More details in "Moderation" section) * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''atl.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[ATL:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. Please ensure when making new pages you follow the [[ATL:Guidelines#Notability Standards|Notability Standards]]! This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[ATL:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distros, it lacks a lot of major distros and each section should have a short blurb and information about key facts about what distros under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distros that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 17c901592012052b5f5c2de8a8dc9bc9ce2655dc 3000 572 3051 2738 2025-07-31T20:52:34Z Atmois 13 Update with Madonuka's changes from Guides:Contributing/Draft to make the page more readable wikitext text/x-wiki == TL;DR == Ensure you have the '''[[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]]''' template on the page, and all changes MUST be approved by staff for public viewing via <code>ApprovedRevs</code>. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Definition == Guides are '''''anything that explain to a user how to do something'''''. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide on hardening Firefox with more privacy focused options, a higher standard of quality and safety than standard articles SHOULD be maintained for guides. This is because unlike normal articles that only provide factual information, guides contain instructions for users to do things to their systems, which could potentially damage the systems or cause data loss. == Policies == All main wiki policies apply, including but not limited to the [[ATL:Code of Conduct|Code of Conduct]] and the wiki [[ATL:Guidelines|guidelines]]. We also recommend you check out our [[ATL:Contributing|Contributing page]] as well, which has a lot of important and useful information for editors. In addition, a special set of criteria are required, as outlined below: * All guides MUST ''start'' with [[Template:Guide Warning]]. ** There are no exceptions to this rule, and violations of the rule entail all edits to be rejected until the template's addition. ** Add it using <code><nowiki>{{GuideWarning}}</nowiki></code> or <code><nowiki>{{Guide Warning}}</nowiki></code> at the beginning of the page: ** {{Guide Warning}} * To prevent distribution of malicious information, all changes to guides, unless from moderators/ATL staff, MUST be approved by a moderator. ** All edits are automatically submitted for review, and will normally be reviewed within 24 hours; but if it is still pending after 48 hours feel free to contact a moderator. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this: ** Double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. ** Aim to provide unbiased and informative content to all users. Your personal views, regardless of validity, are irrelevant here. * You are responsible for ensuring all instructions you provide are safe and functional. ** In guides, any foreseeable risks with running a specific command MUST be clearly stated. ** Ensure to clearly outline, if any, the requirements and prerequisites of the commands. ** Any dangerous commands provided will be held accountable to whomever adds them to a guide. A good example guide would be '''[[Guides:Setting up Flathub on Fedora]]''', which is maintained and has been made in accordance with our guidelines and standards. f337dd282878def9c6e0b14bbb52a8d3c10303b1 3055 3051 2025-07-31T21:34:38Z Atmois 13 Update to loosen the circumstances where a guide is required. wikitext text/x-wiki == TL;DR == Ensure you have the '''[[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]]''' template on the page, and all changes MUST be approved by staff for public viewing via <code>ApprovedRevs</code>. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Definition == Guides are '''''anything that explain to a user how to do something beyond a link to another source or a brief instruction'''''. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide on hardening Firefox with more privacy focused options, a higher standard of quality and safety than standard articles SHOULD be maintained for guides. This is because unlike normal articles that only provide factual information, guides contain instructions for users to do things to their systems, which could potentially damage the systems or cause data loss. == Policies == All main wiki policies apply, including but not limited to the [[ATL:Code of Conduct|Code of Conduct]] and the wiki [[ATL:Guidelines|guidelines]]. We also recommend you check out our [[ATL:Contributing|Contributing page]] as well, which has a lot of important and useful information for editors. In addition, a special set of criteria are required, as outlined below: * All guides MUST ''start'' with [[Template:Guide Warning]]. ** There are no exceptions to this rule, and violations of the rule entail all edits to be rejected until the template's addition. ** Add it using <code><nowiki>{{GuideWarning}}</nowiki></code> or <code><nowiki>{{Guide Warning}}</nowiki></code> at the beginning of the page: ** {{Guide Warning}} * To prevent distribution of malicious information, all changes to guides, unless from moderators/ATL staff, MUST be approved by a moderator. ** All edits are automatically submitted for review, and will normally be reviewed within 24 hours; but if it is still pending after 48 hours feel free to contact a moderator. * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this: ** Double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. ** Aim to provide unbiased and informative content to all users. Your personal views, regardless of validity, are irrelevant here. * You are responsible for ensuring all instructions you provide are safe and functional. ** In guides, any foreseeable risks with running a specific command MUST be clearly stated. ** Ensure to clearly outline, if any, the requirements and prerequisites of the commands. ** Any dangerous commands provided will be held accountable to whomever adds them to a guide. A good example guide would be '''[[Guides:Setting up Flathub on Fedora]]''', which is maintained and has been made in accordance with our guidelines and standards. da6dcf537533180cf396f2f34c6069d90ff5ea15 4 340 3052 3022 2025-07-31T20:55:31Z Atmois 13 Add note on docs style content wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we do not permit extensive documentation of every feature or function of a piece of software or system due to the large amount of maintenance needed to support pages of that kind, that is more suitable for its docs. ; Pages Correctly Located and Categorised : Pages align with the [[Guides:Contributing|guides policy]], must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 74106153db3aff04f90c9879c7eb0d6138776cba 3054 3052 2025-07-31T21:33:20Z Atmois 13 Add commands policy wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we do not permit extensive documentation of every feature or function of a piece of software or system due to the large amount of maintenance needed to support pages of that kind, that is more suitable for its docs. ; Pages Correctly Located and Categorised : Pages align with the [[Guides:Contributing|guides policy]], must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 6f30e7984468f684cd35f2365a2027447ae50239 3058 3054 2025-08-01T17:38:10Z Atmois 13 Update topic relevancy to permit more extensive lists and examples under subpages wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages align with the [[Guides:Contributing|guides policy]], must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 775c55b862b8cdd33d0f51aed45e8cff372b6a56 3059 3058 2025-08-01T17:54:59Z Atmois 13 Add summary of guides policy wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page, and all changes MUST be approved by staff for public viewing via ApprovedRevs. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 22f4dc432bc87d6f4382674f3fa10c1706ead5bb 3060 3059 2025-08-01T17:56:16Z Atmois 13 Add subheading for guides warning template section wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page, and all changes MUST be approved by staff for public viewing via ApprovedRevs. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 116bd811e74e843ef9dcb9768fb1522380da2cdb 3068 3060 2025-08-02T17:57:24Z Atmois 13 Update alt text policy with feedback from User:Aaron wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ====== <u>Accessibility</u> ====== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page, and all changes MUST be approved by staff for public viewing via ApprovedRevs. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] f094bb163a2b01df10f76c8ffe01a6ff411ad611 2 192 3053 1101 2025-07-31T21:02:27Z Atmois 13 Add role onto userpage (1000 edits!) wikitext text/x-wiki Local tech nerd, who listens to ''a lot'' of music. '''atl.wiki'''<nowiki/>'s project lead, come join us and [[ATL:Contributing|contribute]]! https://atmois.com 9b945c48a85fa6b9dde06324224aa6953a1de64a 10 631 3056 2918 2025-08-01T11:17:06Z Atmois 13 Change accessed date to be an suggested field wikitext text/x-wiki <includeonly>{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}}{{#if: {{{accessdate|}}}| (Accessed: {{{accessdate}}})}}</includeonly><noinclude><templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited, this can be an archive.org link if the available source is offline.", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true }, "accessdate": { "label": "Access Date", "type": "date", "suggested": true, "description": "The date the source cited was accessed." } }, "description": "Add a citation using our recommended structure to a page" } </templatedata></noinclude> 0ddd212dc2eeda79cbf21072d90b60b750f729c5 0 667 3057 2799 2025-08-01T17:12:08Z Imnotgoodatnames 121 Added tiny bit of info about the current trademark holder, with a citation, added references header wikitext text/x-wiki {{Cleanup|Incomplete page}}{{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}}'''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. The owner of the UNIX® trademark has been The Open Group since 1994.<ref>[https://unix.org/what_is_unix.html What is UNIX ®?] unix.org</ref> Examples of modern UNIX operating systems include Apple's MacOS and IBM AIX. == References == a389269ce3a2fe997af73d44a0bcf857aefdbced 4 556 3061 2736 2025-08-01T18:50:38Z Atmois 13 Add august 2025 entry wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[ATL:Contact|contact page]]! == Important Links == * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[ATL:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin == History == ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the [https://discord.gg/linux All Things Linux discord]. [[User:Electron271|Electron271]], Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, [[User:Kaizen|Kaizen]]. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spambots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also reimplemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[Special:Favoritelist|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to relicence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another relicencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[ATL:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ====== August 2025 ====== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines and so much more that make every little bit of the wiki a better experience for both editors and users. With 1.0 we... ===== The Future ===== Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] d6fbadeb36033d999959efa5f32e4e6a9060e28d 3073 3061 2025-08-02T18:28:53Z Atmois 13 Add homepage redesign wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[ATL:Contact|contact page]]! == Important Links == * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[ATL:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Sysadmin == History == ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the [https://discord.gg/linux All Things Linux discord]. [[User:Electron271|Electron271]], Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, [[User:Kaizen|Kaizen]]. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spambots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also reimplemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[Special:Favoritelist|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to relicence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another relicencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[ATL:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ====== August 2025 ====== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. With 1.0 we... ===== The Future ===== Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] ef8e83a61161a4be1f731fb4d635309d95727f97 2 758 3062 2025-08-02T03:16:38Z Mawfyy 184 Created page with "Linux and web dev nerd since 2019." wikitext text/x-wiki Linux and web dev nerd since 2019. 58d299bbb5a9e4741fbd8db390e719469cd20dca 6 759 3063 2025-08-02T03:44:00Z Mawfyy 184 wikitext text/x-wiki Running nodeJS. 906635d0c967a1ea5445679ebbb3925d448497a9 3067 3063 2025-08-02T03:48:04Z Mawfyy 184 Adding tmux at the end wikitext text/x-wiki Running nodeJS in Tmux. 77547231cfc439547eac196520719afbb1d71c64 6 760 3064 2025-08-02T03:44:54Z Mawfyy 184 wikitext text/x-wiki Running Neovim. ea04b12fb1a2404c73c1ab4b402846c88bcc5876 3066 3064 2025-08-02T03:47:08Z Mawfyy 184 wikitext text/x-wiki Running Neovim in Tmux. 01c452dc03005d4bed833acd2eece7cc0d8362d0 0 761 3065 2025-08-02T03:46:04Z Mawfyy 184 Create Tmux page with examples wikitext text/x-wiki Tmux is a terminal multiplexer, you can switch between windows or tabs within in the same terminal. [[File:Image.png|thumb]] [[File:Neovim.png|thumb]] 81a71f600806092258fd991303e4ce2123deec78 0 1 3069 2788 2025-08-02T17:58:41Z Atmois 13 Update the wiki homepage using the redesigned page from the staging wiki wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">atl.wiki</h1> <div class="home-header-subtitle">A wiki for Linux and FOSS topics by the [https://allthingslinux.org All Things Linux] non-profit organization</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''atl.wiki''' is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out <code>#quick-support</code> and <code>#support-forum</code> in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#atl-wiki</code> channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content, uploading free use images, check pages meet the guidelines or improve prose to make articles more readable! ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-section"> <div class="content-header">Our Key Values</div> '''atl.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these 5 values when editing on the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> {{Special:RecentChanges|namespace=0|limit=5|hidebots}} </div> </div> [[File:Atl.wiki CTA.png|center|frameless|960x960px]] a3af5cbce0c7fcd5b159655f208e2d0c08bdb296 3071 3069 2025-08-02T18:22:34Z Atmois 13 Update the boxes layout wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">atl.wiki</h1> <div class="home-header-subtitle">A wiki for Linux and FOSS topics by the [https://allthingslinux.org All Things Linux] non-profit organization</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''atl.wiki''' is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out <code>#quick-support</code> and <code>#support-forum</code> in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#atl-wiki</code> channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content, uploading free use images, check pages meet the guidelines or improve prose to make articles more readable! ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''atl.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these 5 values when editing on the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> {{Special:RecentChanges|namespace=0|limit=5|hidebots}} </div> </div> [[File:Atl.wiki CTA.png|center|frameless|960x960px]] cf21c0133dbfd9938eb2b9741d4ff367560900de 3072 3071 2025-08-02T18:23:27Z Atmois 13 Add spacing p2 wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">atl.wiki</h1> <div class="home-header-subtitle">A wiki for Linux and FOSS topics by the [https://allthingslinux.org All Things Linux] non-profit organization</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''atl.wiki''' is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out <code>#quick-support</code> and <code>#support-forum</code> in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#atl-wiki</code> channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content, uploading free use images, check pages meet the guidelines or improve prose to make articles more readable! ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''atl.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these 5 values when editing on the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> {{Special:RecentChanges|namespace=0|limit=5|hidebots}} </div> </div> [[File:Atl.wiki CTA.png|center|frameless|960x960px]] 5ef200cd57d5a60a6b41d9693470756d497025e8 3074 3072 2025-08-02T18:44:43Z Atmois 13 Increase recent changes length wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">atl.wiki</h1> <div class="home-header-subtitle">A wiki for Linux and FOSS topics by the [https://allthingslinux.org All Things Linux] non-profit organization</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''atl.wiki''' is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out <code>#quick-support</code> and <code>#support-forum</code> in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#atl-wiki</code> channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''Anyone'' can edit almost every page; just find something that can be improved and make it better! You can add content, uploading free use images, check pages meet the guidelines or improve prose to make articles more readable! ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''atl.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these 5 values when editing on the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> {{Special:RecentChanges|namespace=0|limit=10|hidebots}} </div> </div> [[File:Atl.wiki CTA.png|center|frameless|960x960px]] c6a5250f20ebe67047b247cdb5cbc5dd72c178c7 8 624 3070 2539 2025-08-02T18:01:33Z Atmois 13 Update to include changes to the main page CSS and make the contrast on the links css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } 742a40215909d63131facfb0e8ba54832744d76c 0 171 3075 2983 2025-08-02T20:35:32Z Deviantsemicolon 174 Changed release cycle to be more accurate wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo, a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] fcba223301aed753c26a0919c16a5a98ebee81ba 3080 3075 2025-08-02T20:42:10Z Deviantsemicolon 174 Fixed punctuation wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = Enlightenment, GNOME, [[KDE Plasma]], LXQt, [[Xfce]], MATE, Pantheon, Cinnamon | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] f88bb3ecab3894e92d87b83c8b4a2a1ad72026b1 3082 3080 2025-08-02T20:46:15Z Deviantsemicolon 174 Removed most of the default desktops from the default desktop section, as NixOS doesn't really have default desktop environments, especially not those. wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = none(GNOME and [[KDE Plasma]] come with respective ISOs for easier installation, however this is not required) | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] 9ea8181865b668650ddd4ee7d35f681af0c8ccf7 0 306 3076 2922 2025-08-02T20:36:36Z RelativeAlbatros 187 hyprland, hyprslider and hyprscroller are Window Managers for Wayland not X wikitext text/x-wiki {{Work_In_Progress}} A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent GUI. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as dwm.  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm * [[Wayfire]] ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * i3 * [[Sway]] * [[SwayFx]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[dwl]] * qtile * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] ==== Scrollable Window Managers ==== Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[niri]] * [[PaperWM]] * [[karousel]] * [[papersway]] * [[PaperWM.spoon]] [[Category:Terminology]] [[Category:Window Management Systems]] 03b5bf043d744b37c46635e85c9b3f1f90f418a8 3078 3076 2025-08-02T20:40:48Z RelativeAlbatros 187 niri is a Window manager for wayland wikitext text/x-wiki {{Work_In_Progress}} A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent GUI. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as dwm.  === Types of Window Manager === ==== Stacking/Floating Window Managers ==== Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm * [[Wayfire]] ==== Tiling Window Managers ==== Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * i3 * [[Sway]] * [[SwayFx]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] ==== Dynamic Window Managers ==== Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[dwl]] * qtile * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] ==== Scrollable Window Managers ==== Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[PaperWM]] * [[karousel]] * [[papersway]] * [[PaperWM.spoon]] [[Category:Terminology]] [[Category:Window Management Systems]] f6ae9c80feaba38862745813e5d61e38ed149a9c 2 732 3077 2800 2025-08-02T20:39:20Z Beatrixzy 179 Updated biography, added additional info wikitext text/x-wiki Beatrixzy (AKA Bea / Beatroot in ATL) is a user who owns obscure hardware and occasionally does obscure things to those machines (this includes putting unsupported firmware on a computer / mobile phone). User is usually found messing about with either linux / phones, Modding consoles or playing certain games. ec38cecc49e973df37fe094ab1b04ba6c1f7479d 0 622 3079 2930 2025-08-02T20:41:52Z 0Stormy 158 Moving Openbox to to the X11 Window Manager page. wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a GUI or TUI. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> {| class="wikitable" |+ !Desktop Environment !Description |- |Budgie |The Budgie Desktop is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |Cinnamon |Cinnamon is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |Enlightenment |Enlightenment is a desktop environment and window manager for [[Linux]] and other [[Unix|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |GNOME |GNOME is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |MATE |MATE is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |Plasma |KDE Plasma is a highly customizable and popular and is coded in C++ and [[QML]]. |- |Trinity Desktop Environment |Trinity Desktop Environment is an desktop environment forked from [[Plasma|KDE]] 3 coded in C. |- |XFCE |XFCE is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in C. |} 6de3a8dfbe486bbbd5eabcea9a62442039ad725e 0 762 3081 2025-08-02T20:45:00Z Beatrixzy 179 Added brief information to Zypper, this needs urgent work though. wikitext text/x-wiki Zypper is OpenSUSE's package manager. Built on top of SAT Solver, Zypper is known to be blazing fast. Zypper includes shortened cmdlets to add on to how fast Zypper truly is. These include: in (install),rm (remove),dup (distribution upgrade). More information on Zypper can be found [https://en.opensuse.org/Portal:Libzypp here]. 60da71dd943d2a8d36c42d1426078be930b55f61 0 763 3083 2025-08-02T20:47:25Z 0Stormy 158 Start work on X Window Manager page wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display its [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often are paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |Openbox |A minimal and highly configurable stacking window manager written in C. |} b33bf729b64bc87c6d40346c9a78131d940913ee 0 764 3084 2025-08-02T20:47:38Z Dreamer120 188 create the Tilck page wikitext text/x-wiki Tilck is a tiny monolithic [[kernel]] designed to be compatible with [[Linux]] on the binary level. It currently runs on the i686 and RISCV64 architectures, with plans to port it to ARM. It is intended for embedded systems due to its very small size and low-latency abilities. While Linux-compatible, Tilck does not aim to replace the Linux kernel, nor to be an alternative to it for desktop users. In its current state, Tilck implements about ~100 Linux system calls, allowing many programs intended for Linux to work out of the box. While not currently implemented, the developers plan to implement Networking at some point, with the network cards of specific SoC being the initial targets. aa16b9f2718f4b6de478ccf4423feaef70594d8c 0 171 3085 3082 2025-08-02T20:48:03Z Deviantsemicolon 174 Made some clarifications for previous edit wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = None, however ISOs with GNOME and [[KDE Plasma]] are offered for easier installation | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] bb3e04884bd919da4ab8196e7abe2b2f907a0cfe 3089 3085 2025-08-02T20:51:51Z Deviantsemicolon 174 Removed extra info from InfoBox at Zoe's request wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} [[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup. === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] a793a4fe97a31304faca6464d0606fb1ca6e41be 3093 3089 2025-08-02T20:54:42Z Atmois 13 Change the layout to fix issues with rendering icons wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Nix Flakes]''' is an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] 777bd6ccdb4b3084f202199707c0e74ad003e4b3 3094 3093 2025-08-02T20:54:50Z Deviantsemicolon 174 /* Flakes */ wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] 220788a5958f2ebc2b7a36f61b34cb86b93a94b7 0 763 3086 3083 2025-08-02T20:48:35Z 0Stormy 158 Typo wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often are paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |Openbox |A minimal and highly configurable stacking window manager written in C. |} d9a846f938586ebed9e651b8a52d3655b72854d5 3087 3086 2025-08-02T20:49:37Z 0Stormy 158 Typo (again) wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |Openbox |A minimal and highly configurable stacking window manager written in C. |} 2ba25f791d0b257c300bf5e1d8ec635c42a432db 3131 3087 2025-08-02T21:33:40Z Imnotgoodatnames 121 Added more WMs - twm, IceWM, WMaker wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |Openbox |A minimal and highly configurable stacking window manager written in C. |- |twm |Tab Window Manager - standard X11 window manager since 1989. |- |IceWM |Lightweight window manager that includes a taskbar, start menu and other features. |- |Window Maker |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |} 6d4f5b66a58791350aff07b5974f2b66c274f874 0 765 3088 2025-08-02T20:50:08Z RelativeAlbatros 187 initial description wikitext text/x-wiki X11 is a version of the X [[display server]] released in 1987 for [[UNIX|Unix]] operating systems. X11 is currently maintained by the X.Org foundation with the free and open-source implementation, X.Org Server. 7023ae6976676b86f29154a07a3e17272dcd83a8 0 297 3090 2980 2025-08-02T20:52:48Z RelativeAlbatros 187 make sentence clearer wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)." (No Link.)</ref> The core concept of multi-booting revolves around partitioning a computer's [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system's configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. it provides however the booted OS with full access to the machine's components, rather than needing to go through translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straightforward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Riot's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == References == <references /> [[Category:Terminology]] 0455a2160257699780a3524870dbb42b1993d01c 3100 3090 2025-08-02T20:59:12Z Atmois 13 Clean up citation wikitext text/x-wiki == Overview == '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)."</ref> The core concept of multi-booting revolves around partitioning a computer's [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system's configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. it provides however the booted OS with full access to the machine's components, rather than needing to go through translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straightforward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Riot's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == References == <references /> [[Category:Terminology]] a34ff0d86e25aa660eea297fdc05eba7fb1b643f 0 764 3091 3084 2025-08-02T20:52:52Z Dreamer120 188 wikitext text/x-wiki Tilck is a tiny monolithic [[kernel]] designed to be compatible with [[Linux]] on the binary level. It currently runs on the i686 and RISCV64 architectures, with plans to port it to ARM. It is intended for embedded systems due to its very small size and low-latency abilities. While Linux-compatible, Tilck does not aim to replace the Linux kernel, nor to be an alternative to it for desktop users. In its current state, Tilck implements about ~100 Linux system calls, allowing many programs intended for Linux to work out of the box. While not currently implemented, the developers plan to implement Networking at some point, with the network cards of specific SoC being the initial targets.<ref>{{Cite|url=https://github.com/vvaltchev/tilck|title=Tilck: A Tiny Linux-Compatible Kernel|author=Vladislav K. Valtchev|year=Nov 22, 2024|accessdate=August 2, 2025}}</ref> == References == # https://github.com/vvaltchev/tilck 3ff01d265e999d06f1e2759e8260cb40374dfa8d 3092 3091 2025-08-02T20:53:10Z Dreamer120 188 wikitext text/x-wiki Tilck is a tiny monolithic [[kernel]] designed to be compatible with [[Linux]] on the binary level. It currently runs on the i686 and RISCV64 architectures, with plans to port it to ARM. It is intended for embedded systems due to its very small size and low-latency abilities. While Linux-compatible, Tilck does not aim to replace the Linux kernel, nor to be an alternative to it for desktop users. In its current state, Tilck implements about ~100 Linux system calls, allowing many programs intended for Linux to work out of the box. While not currently implemented, the developers plan to implement Networking at some point, with the network cards of specific SoC being the initial targets.<ref>{{Cite|url=https://github.com/vvaltchev/tilck|title=Tilck: A Tiny Linux-Compatible Kernel|author=Vladislav K. Valtchev|year=Nov 22, 2024|accessdate=August 2, 2025}}</ref> 962f089ecc20947fa5e0b897ea31e58b6f1e1224 3096 3092 2025-08-02T20:56:20Z Dreamer120 188 wikitext text/x-wiki Tilck is a tiny monolithic [[kernel]] designed to be compatible with [[Linux]] on the binary level. It currently runs on the i686 and RISCV64 architectures, with plans to port it to ARM. It is intended for embedded systems due to its very small size and low-latency abilities. While Linux-compatible, Tilck does not aim to replace the Linux kernel, nor to be an alternative to it for desktop users. In its current state, Tilck implements about ~100 Linux system calls, allowing many programs intended for Linux to work out of the box. While not currently implemented, the developers plan to implement Networking at some point, with the network cards of specific SoC being the initial targets.<ref>{{Cite|url=https://github.com/vvaltchev/tilck|title=Tilck: A Tiny Linux-Compatible Kernel|author=Vladislav K. Valtchev|year=Nov 22, 2024|accessdate=August 2, 2025}}</ref> <references /> [[Category:Misc Operating Systems]] 449ceb202287d4bc6523258616c6fb4a613a4e10 3099 3096 2025-08-02T20:57:40Z Dreamer120 188 wikitext text/x-wiki Tilck is a tiny monolithic [[kernel]] designed to be compatible with [[Linux]] on the binary level. It currently runs on the i686 and RISCV64 architectures, with plans to port it to ARM. It is intended for embedded systems due to its very small size and low-latency abilities. While Linux-compatible, Tilck does not aim to replace the Linux kernel, nor to be an alternative to it for desktop users. In its current state, Tilck implements about ~100 Linux system calls, allowing many programs intended for Linux to work out of the box. While not currently implemented, the developers plan to implement Networking at some point, with the network cards of specific SoC being the initial targets.<ref>{{Cite|url=https://github.com/vvaltchev/tilck|title=Tilck: A Tiny Linux-Compatible Kernel|author=Vladislav K. Valtchev|year=Nov 22, 2024|accessdate=August 2, 2025}}</ref> == References == <references /> [[Category:Misc Operating Systems]] 76f96cd92976685cb60b06d7a8041188dd04d415 0 254 3095 2402 2025-08-02T20:55:39Z RelativeAlbatros 187 remove redundant sentence as it depends on the user's environment. wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''DWM''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. DWM is designed to be small in source code, fast and light. The first version of DWM was released on July 14th, 2006. === Installation === DWM is meant to be built from source. You can download the latest version of DWM by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling DWM, make sure you have X11 installed. DWM can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec DWM</code> in it. You can then start X (by running <code>startx</code>) and DWM should be running. It is also recommended that you install dmenu and st along with DWM, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] 6ffc6fa6c7179594a58ac78589b2ec71e103a787 3097 3095 2025-08-02T20:56:32Z RelativeAlbatros 187 installation requires X11 libraries, one can have the xorg server binary but is unable to compile dwm wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''DWM''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. DWM is designed to be small in source code, fast and light. The first version of DWM was released on July 14th, 2006. === Installation === DWM is meant to be built from source. You can download the latest version of DWM by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling DWM, make sure you have X11 libraries installed. DWM can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make install clean </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec DWM</code> in it. You can then start X (by running <code>startx</code>) and DWM should be running. It is also recommended that you install dmenu and st along with DWM, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] 5290e4234019b2c812eebc66ac4474cdf3572fe2 3098 3097 2025-08-02T20:57:36Z RelativeAlbatros 187 command was in the wrong order, putting clean at the end will delete the generated binary. wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = DWM logo | title = DWM | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''DWM''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. DWM is designed to be small in source code, fast and light. The first version of DWM was released on July 14th, 2006. === Installation === DWM is meant to be built from source. You can download the latest version of DWM by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling DWM, make sure you have X11 libraries installed. DWM can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec DWM</code> in it. You can then start X (by running <code>startx</code>) and DWM should be running. It is also recommended that you install dmenu and st along with DWM, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] d1c867effdbc3fe09606a13db01c57f56885b575 3102 3098 2025-08-02T21:00:40Z RelativeAlbatros 187 dwm is always spelled in lower case even after a point. Binary generated is also in lower case in the makefile provided by suckless wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] c39f51038d5fa8af077e1cc4033184492a69b3d9 3105 3102 2025-08-02T21:05:37Z Imnotgoodatnames 121 dwm is always lowercase, changed the display title to reflect that wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] c76bdab1d92d979068689db41438e7d45d438d1a 3111 3105 2025-08-02T21:10:08Z Atmois 13 Attempt to fix page title wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] 8cee2716cba9ceb3f8174fda2561c12bf6a58860 3112 3111 2025-08-02T21:10:38Z Atmois 13 Remove duplicate display title module wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] c76bdab1d92d979068689db41438e7d45d438d1a 3114 3112 2025-08-02T21:14:24Z Atmois 13 Remove display title to readd after fix wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] c39f51038d5fa8af077e1cc4033184492a69b3d9 3115 3114 2025-08-02T21:14:51Z Atmois 13 Readd custom display title of "dwm" wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file and put <code>exec dwm</code> in it. You can then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. [[Category:X_Window_Managers]] c76bdab1d92d979068689db41438e7d45d438d1a 3132 3115 2025-08-02T21:33:57Z RelativeAlbatros 187 add See also section linking to dwm main page and improve sentence structure wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light. The first version of dwm was released on July 14th, 2006. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. === See Also === [https://dwm.suckless.org/ dwm suckless - main page] [[Category:X_Window_Managers]] [[Category:Window Management Systems]] 092d61e282a3d369f1085b40e0f7171245e9e2e3 3133 3132 2025-08-02T21:36:14Z RelativeAlbatros 187 add license and citation wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences https://dwm.suckless.org/]</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. === See Also === [https://dwm.suckless.org/ dwm suckless - main page] [[Category:X_Window_Managers]] [[Category:Window Management Systems]] 65c13a4ffa2577c90fcdbc17a548649e37e32cc9 3134 3133 2025-08-02T21:37:40Z RelativeAlbatros 187 add references section wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences https://dwm.suckless.org/]</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have X11 libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install dmenu and st along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. === See Also === [https://dwm.suckless.org/ dwm suckless - main page] === References === [[Category:X_Window_Managers]] [[Category:Window Management Systems]] 45d303747b21ef1557456b637bbc43864b8d85b6 10 631 3101 3056 2025-08-02T21:00:34Z Atmois 13 Fix formatting wikitext text/x-wiki <includeonly>{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} {{#if: {{{accessdate|}}}| (Accessed: {{{accessdate}}})}}</includeonly><noinclude><templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited, this can be an archive.org link if the available source is offline.", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true }, "accessdate": { "label": "Access Date", "type": "date", "suggested": true, "description": "The date the source cited was accessed." } }, "description": "Add a citation using our recommended structure to a page" } </templatedata></noinclude> 85861d369fb0c39e64c7811af947374ffbd05fd6 0 2 3103 2933 2025-08-02T21:04:21Z Landline 196 Updated details about the archinstall script wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations for more advanced control the manual installation should be used {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- !Kernels |There are four [[kernel]]<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] d17f7fa16baaa5910d23b8b9d98f30d9fad95adf 3104 3103 2025-08-02T21:05:29Z Landline 196 Changed kernel page link location wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations for more advanced control the manual installation should be used {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] 8afcba8db7bc80410ff0fbf50b95cf9046b8c1e7 3107 3104 2025-08-02T21:06:25Z Landline 196 Added punctuation wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] d924943e06b8a7484fab8d743d0736390ecdfff7 3121 3107 2025-08-02T21:17:39Z RelativeAlbatros 187 mention that arch is rolling release in the description wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent rolling release [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. Arch Linux is kept up-to-date by regularly updating the packages of the system. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Arch Installation Script === This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] 3e146d501273e1e6cfae9c55d19e08749d796e42 0 667 3106 3057 2025-08-02T21:05:58Z Dreamer120 188 wikitext text/x-wiki {{Cleanup|Incomplete page}}{{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}}'''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. The owner of the UNIX® trademark has been The Open Group since 1994.<ref>[https://unix.org/what_is_unix.html What is UNIX ®?] unix.org</ref> Examples of modern UNIX operating systems include Apple's MacOS and IBM AIX. Being genetic UNIX® is not required for UNIX® certification. Formerly, Inspur K-UX was certified UNIX®, specifically versions 2.0 and 3.0. Inspur K-UX's UNIX® certification expired in February of 2019 and has yet to be renewed.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Inspur_K-UX|title=Inspur K-UX|author=Huihermit|year=21 January 2025|accessdate=2 August 2025}}</ref> == References == 50f70af0041a34196dc61d14c9b5d828abff4938 0 429 3108 2940 2025-08-02T21:07:10Z Atmois 13 Atmois moved page [[CRUX Linux]] to [[CRUX]]: Misspelled title: Renamed to the official name wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "[[Portfiles]]," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> == References == [[Category:Linux Distributions]] e7e053fc8b0b417f30a963d59b5f6183f475c1d9 3120 3108 2025-08-02T21:17:33Z Rosurarosaura 197 Added summary of the ports system, and added information about releases wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] <ref>https://crux.nu/doc/prt-get%20-%20User%20Manual.html<ref> with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. CRUX has had 27 documented releases <ref>http://ftp.morpheus.net/pub/linux/crux/<ref>,from 0.9.7 to the current release, 3.8 ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "Pkgfiles," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> == Ports System == CRUX uses a BSD-style ports system, revolving around the packaging system pkgutils , each port contains a Pkgfile which tells pkgmk or prt-get what to do, it is a relatively simple process, that involves fetching the source declared in the Pkgfile (Or if the file is already present and matches the checksum, it extracts it.), Following the compilation steps declared in the Pkgfile while using the optimizations and arguments declared in ```/etc/pkgmk.conf```, this part is declared in the ```build()``` section of the Pkgfile, since a Pkgfile is essentially a BASH script, it can be edited by the end user to match their own needs. <ref>https://crux.nu/Main/Handbook3-8-Package<ref> == References == [[Category:Linux Distributions]] 540afcc52ba166076a63a5032e674df63af08258 3122 3120 2025-08-02T21:18:31Z Rosurarosaura 197 fixed citations wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] <ref>https://crux.nu/doc/prt-get%20-%20User%20Manual.html</ref> with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. CRUX has had 27 documented releases <ref>http://ftp.morpheus.net/pub/linux/crux/</ref>,from 0.9.7 to the current release, 3.8 ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "Pkgfiles," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> == Ports System == CRUX uses a BSD-style ports system, revolving around the packaging system pkgutils , each port contains a Pkgfile which tells pkgmk or prt-get what to do, it is a relatively simple process, that involves fetching the source declared in the Pkgfile (Or if the file is already present and matches the checksum, it extracts it.), Following the compilation steps declared in the Pkgfile while using the optimizations and arguments declared in ```/etc/pkgmk.conf```, this part is declared in the ```build()``` section of the Pkgfile, since a Pkgfile is essentially a BASH script, it can be edited by the end user to match their own needs. <ref>https://crux.nu/Main/Handbook3-8-Package</ref> == References == [[Category:Linux Distributions]] e9a33282b4425f8183857fc1c61fba8ef124726c 3123 3122 2025-08-02T21:18:52Z Rosurarosaura 197 /* Ports System */ wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] <ref>https://crux.nu/doc/prt-get%20-%20User%20Manual.html</ref> with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. CRUX has had 27 documented releases <ref>http://ftp.morpheus.net/pub/linux/crux/</ref>,from 0.9.7 to the current release, 3.8 ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "Pkgfiles," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> == Ports System == CRUX uses a BSD-style ports system, revolving around the packaging system pkgutils , each port contains a Pkgfile which tells pkgmk or prt-get what to do, it is a relatively simple process, that involves fetching the source declared in the Pkgfile (Or if the file is already present and matches the checksum, it extracts it.), Following the compilation steps declared in the Pkgfile while using the optimizations and arguments declared in ```/etc/pkgmk.conf```, this part is declared in the ```build()``` section of the Pkgfile, since a Pkgfile is essentially a BASH script, it can be edited by the end user to match their own needs. <ref>https://crux.nu/Main/Handbook3-8-Package</ref> == References == [[Category:Linux Distributions]] 1e4ebdfdadc7c862218dff13e3807b675fd0e42a 0 766 3109 2025-08-02T21:07:10Z Atmois 13 Atmois moved page [[CRUX Linux]] to [[CRUX]]: Misspelled title: Renamed to the official name wikitext text/x-wiki #REDIRECT [[CRUX]] cd720e5403ba754335971ea4021839c6fb3ae038 0 767 3110 2025-08-02T21:07:56Z RelativeAlbatros 187 initial description wikitext text/x-wiki RTFM is an acronym to "Read The Fucking Manual". f2d3369faa2258498946637b9456ca366275411a 3117 3110 2025-08-02T21:15:58Z Landline 196 Extended the content of the page and added a bit more explanation wikitext text/x-wiki RTFM is an acronym of "Read The Fucking Manual"<ref>{{Cite|url=http://www.catb.org/~esr/faqs/smart-questions.html#rtfm|title=How To Ask Questions The Smart Way|author=Eric Steven Raymond|year=21 May 2014|accessdate=02/08/2025}}</ref> or "Read The Friendly Manual". It's usually used when a user asks a question that could be easily answered by reading the manual 4b859cb014b86fd3854dcd963ce254140415f8e4 3118 3117 2025-08-02T21:17:10Z Atmois 13 Update accessed date to be inline with [[ATL:Guidelines#Citations]] wikitext text/x-wiki RTFM is an acronym of "Read The Fucking Manual"<ref>{{Cite|url=http://www.catb.org/~esr/faqs/smart-questions.html#rtfm|title=How To Ask Questions The Smart Way|author=Eric Steven Raymond|year=21 May 2014|accessdate=2 August 2025}}</ref> or "Read The Friendly Manual". It's usually used when a user asks a question that could be easily answered by reading the manual ab2a348a5d885c867da93e7b588852d9fd553125 0 768 3113 2025-08-02T21:10:57Z RelativeAlbatros 187 initial description wikitext text/x-wiki GUI or Graphical User Interface is a form of user interface where the user interacts with graphical elements such as icons and menus, in contrast to a CLI. 95630b5b23554eca8c026cd2b96c84aaf6310ce4 0 769 3116 2025-08-02T21:15:04Z DeltaNova 193 Creation of Wayland Compositiors Page wikitext text/x-wiki == Wayland Compositors == {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter''' || GNOME || C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin''' || KDE Plasma || C++ || KDE’s compositor and window manager, with full Wayland support since Plasma 5. |- | '''Sway''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''Hyprland''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |} efbcd6fefcb2248d25fdeb180d0da95049738206 3129 3116 2025-08-02T21:28:37Z Landline 196 Added links wikitext text/x-wiki == Wayland Compositors == {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''[[Weston]]''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin''' || [[KDE Plasma]]|| C++ || KDE’s compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |} 1a1538b71417454f61766058d848f9dbc00dd0ab 2 770 3119 2025-08-02T21:17:31Z Ow0cast 249 borrowing from wikipedia, see history on [[wikipedia:Module:Message box/ambox.css]] for attrib css text/css .ambox { border: 1px solid #a2a9b1; /* @noflip */ border-left: 10px solid #36c; /* Default "notice" blue */ background-color: #fbfbfb; box-sizing: border-box; } /* Single border between stacked boxes. Take into account base templatestyles, * user styles, and Template:Dated maintenance category. * remove link selector when T200206 is fixed */ .ambox + link + .ambox, .ambox + link + style + .ambox, .ambox + link + link + .ambox, /* TODO: raise these as "is this really that necessary???". the change was Dec 2021 */ .ambox + .mw-empty-elt + link + .ambox, .ambox + .mw-empty-elt + link + style + .ambox, .ambox + .mw-empty-elt + link + link + .ambox { margin-top: -1px; } /* For the "small=left" option. */ /* must override .ambox + .ambox styles above */ html body.mediawiki .ambox.mbox-small-left { /* @noflip */ margin: 4px 1em 4px 0; overflow: hidden; width: 238px; border-collapse: collapse; font-size: 88%; line-height: 1.25em; } .ambox-speedy { /* @noflip */ border-left: 10px solid #b32424; /* Red */ background-color: #fee7e6; /* Pink */ } .ambox-delete { /* @noflip */ border-left: 10px solid #b32424; /* Red */ } .ambox-content { /* @noflip */ border-left: 10px solid #f28500; /* Orange */ } .ambox-style { /* @noflip */ border-left: 10px solid #fc3; /* Yellow */ } .ambox-move { /* @noflip */ border-left: 10px solid #9932cc; /* Purple */ } .ambox-protection { /* @noflip */ border-left: 10px solid #a2a9b1; /* Gray-gold */ } .ambox .mbox-text { border: none; /* @noflip */ padding: 0.25em 0.5em; width: 100%; } .ambox .mbox-image { border: none; /* @noflip */ padding: 2px 0 2px 0.5em; text-align: center; } .ambox .mbox-imageright { border: none; /* @noflip */ padding: 2px 0.5em 2px 0; text-align: center; } /* An empty narrow cell */ .ambox .mbox-empty-cell { border: none; padding: 0; width: 1px; } .ambox .mbox-image-div { width: 52px; } @media (min-width: 720px) { .ambox { margin: 0 10%; /* 10% = Will not overlap with other elements */ } } @media print { body.ns-0 .ambox { display: none !important; } } 79b3da455473ad263f5d5f5d0e9f99c487935c52 1 312 3124 1084 2025-08-02T21:20:29Z RelativeAlbatros 187 /* Remove Default Desktop Section */ new section wikitext text/x-wiki == optional repos == include staging repos in the list (iirc there are more too) [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 09:00, 10 July 2024 (UTC) == Remove Default Desktop Section == Arch doesn't ship nor recommend a specific DE or WM, it merely provides them for the user. It is thus inaccurate to mention these desktops as "default". [[User:RelativeAlbatros|RelativeAlbatros]] ([[User talk:RelativeAlbatros|talk]]) 21:20, 2 August 2025 (UTC) ffb0ec6b51b975406360143feda71e9388969cdf 3126 3124 2025-08-02T21:22:07Z Atmois 13 /* Remove Default Desktop Section */ Reply wikitext text/x-wiki == optional repos == include staging repos in the list (iirc there are more too) [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 09:00, 10 July 2024 (UTC) == Remove Default Desktop Section == Arch doesn't ship nor recommend a specific DE or WM, it merely provides them for the user. It is thus inaccurate to mention these desktops as "default". [[User:RelativeAlbatros|RelativeAlbatros]] ([[User talk:RelativeAlbatros|talk]]) 21:20, 2 August 2025 (UTC) :The default desktop section is for desktops offered in the installer and to my knowledge those are the ones offered in archinstall? The title of "Default" does need to be changed which will be addressed on the template. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 21:22, 2 August 2025 (UTC) d269ef27d60555ac32a08289102727961bf47fdd 2 771 3125 2025-08-02T21:20:59Z RelativeAlbatros 187 Created page with "Github Page: github.com/RelativeAlbatros" wikitext text/x-wiki Github Page: github.com/RelativeAlbatros 037dd237acd78f2598492e03b798656022701526 0 622 3127 3079 2025-08-02T21:26:48Z RelativeAlbatros 187 add links wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a GUI or TUI. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> {| class="wikitable" |+ !Desktop Environment !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in C. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in C. |} 288b050d58ab56929b20240901755c54e8281085 3128 3127 2025-08-02T21:27:19Z RelativeAlbatros 187 add links wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> {| class="wikitable" |+ !Desktop Environment !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in C. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in C. |} ee0e0cfe4aa2013098ff0cfb34d6d19c6c486070 3130 3128 2025-08-02T21:29:12Z RelativeAlbatros 187 mention LXQt wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> {| class="wikitable" |+ !Desktop Environment !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from Razor-qt and LXDE components which were ported to [[Qt]]. |} 0a46a9694dff85313889f3171828a0b6ca1caae7 0 772 3135 2025-08-02T21:38:01Z Landline 196 Create the Python page wikitext text/x-wiki Python is a high-level programming language focused on ease of use ad668d950bed289458836ff1eea5e64af2eedbf3 3136 3135 2025-08-02T21:40:14Z Landline 196 Added cleanup notice wikitext text/x-wiki {{Cleanup|Stub}} Python is a high-level programming language focused on ease of use 1d4ff69df027f55bfa32aa88d1e75d85a23db5e9 3153 3136 2025-08-02T22:12:08Z RelativeAlbatros 187 add category wikitext text/x-wiki {{Cleanup|Stub}} Python is a high-level programming language focused on ease of use [[Category:Programming Languages]] 9613bc7fb9f67747cc33b2967ed3c5b934d6aeae 3155 3153 2025-08-02T22:14:07Z RelativeAlbatros 187 add category + expand on description wikitext text/x-wiki {{Cleanup|Stub}} Python is a high-level general-purpose interpreted programming language focused on ease of use and readability. Python is dynamically type checked and garbage-collected. [[Category:Programming Languages]] 8ab1fe25c38480648dac7c62dcee6abd2553a7e1 3161 3155 2025-08-02T22:25:55Z Landline 196 Added infobox wikitext text/x-wiki {{Cleanup |This page is a stub}} {{SoftwareInfobox | image = [[Python.png|thumb]] | caption = Python Logo | title = Python | releasestatus = Maintained | lastrelease = 3.13.5, 2025-06-11 | firstrelease = 1.0.1, 2022-08-01 | languages = [[python]] | developers = Python Software Foundation | website = [https://python.org] }} Python is a high-level programming language focused on ease of use 13548c63dd5d6f8b494285029bb97da0ddaa8c90 0 254 3137 3134 2025-08-02T21:43:26Z RelativeAlbatros 187 add configuration and patches section wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences https://dwm.suckless.org/]</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. === Installation === dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. === Configuration === Configuration is done through editing the config.h file which is written in C and recompiling dwm. === Patches === dwm has many patches provided in the suckless website to add and improve its features<ref>https://dwm.suckless.org/patches/</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff === See Also === [https://dwm.suckless.org/ dwm suckless - main page] === References === [[Category:X_Window_Managers]] [[Category:Window Management Systems]] 9264aa4f038fb93f80c0b4fb01d9627d4f0e3d3d 0 158 3138 2660 2025-08-02T21:45:28Z RelativeAlbatros 187 typo wikitext text/x-wiki {{Needs Citations}} ==== <u>Introduction</u> ==== When using [[Linux]], sooner or later, there's a good chance you'll end up finding yourself in front of a [[TUI|terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a '''command'''. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include <code>echo</code>, <code>mv</code>, [[cat|<code>cat</code>]], etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with <code>sudo</code> followed with your original command. [[sudo]] tells your computer to ''do'' something as a ''super user'' which will allow you to bypass restrictions. It should be important to note that '''sudo is a separate package''' and may not be pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you will need to use something like <code>su</code> to log in as root and then run your command as root or install sudo as root. ==== <u>Useful Commands</u> ==== Furthermore, with commands you will likely need to include ''options'' that specify to the program how you want it to behave. One of the most common options is <code>--help</code>, which will usually tell program to list all of its options. An example would be as follows: cat --help In this case, the 'cat' utility would respond to this command with the following:<syntaxhighlight>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines ...</syntaxhighlight>These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, <code>--help</code> is always there and ready. If not, you can always run [[man|<code>man</code>]] before a program similarly to how you would run <code>sudo</code>, and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a file to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory|working directory]] (Like shown) or you can provide a file from anywhere in the [[filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt The tilda sign <code>~</code>, in Linux and some other [[Operating System|operating systems]], expands to the full [[Directory Path|directory path]] of the current user's home folder. Here is what it would look like to type out the whole path: nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] a3ab6a340793d79ba0de98d927d72eb8c276d66a 2 773 3139 2025-08-02T21:47:38Z Ow0cast 249 tmpl | create template for testing wikitext text/x-wiki You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} {{#ifeq:{{{action-ing|}}}|yes|{{{action-ing}}|editing}}]</span> it. 76c5d13e30b324ccbf6c05743d6cea961afc8ee6 3141 3139 2025-08-02T21:49:55Z Ow0cast 249 tmpl | fix params wikitext text/x-wiki You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} {{{action|editing}}}]</span> it. 349988b07048fb28e93b08995d21281a4e96df42 1 312 3140 3126 2025-08-02T21:47:48Z RelativeAlbatros 187 /* Remove Default Desktop Section */ Reply wikitext text/x-wiki == optional repos == include staging repos in the list (iirc there are more too) [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 09:00, 10 July 2024 (UTC) == Remove Default Desktop Section == Arch doesn't ship nor recommend a specific DE or WM, it merely provides them for the user. It is thus inaccurate to mention these desktops as "default". [[User:RelativeAlbatros|RelativeAlbatros]] ([[User talk:RelativeAlbatros|talk]]) 21:20, 2 August 2025 (UTC) :The default desktop section is for desktops offered in the installer and to my knowledge those are the ones offered in archinstall? The title of "Default" does need to be changed which will be addressed on the template. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 21:22, 2 August 2025 (UTC) ::I agree with you, however I think that it shouldn't be mentioned in order not to lead new users to error that Arch doesn't support other DEs or WMs. [[User:RelativeAlbatros|RelativeAlbatros]] ([[User talk:RelativeAlbatros|talk]]) 21:47, 2 August 2025 (UTC) b949950768db27071edcedc2e92f48cd4adfd272 0 769 3142 3129 2025-08-02T21:54:08Z DeltaNova 193 References Added wikitext text/x-wiki == Wayland Compositors == {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''[[Weston]]''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>https://gitlab.gnome.org/GNOME/mutter</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>https://github.com/KDE/kwin</ref>''' || [[KDE Plasma]]|| C++ || KDE’s compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>https://github.com/riverwm/river</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>https://github.com/WayfireWM/wayfire</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>https://github.com/cage-kiosk/cage</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |} ==References== <references /> e7a0b2d7bf3369ec16b293c3394e25a26e47b851 3160 3142 2025-08-02T22:24:27Z DeltaNova 193 wikitext text/x-wiki == Wayland Compositors == {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>https://gitlab.freedesktop.org/wayland/weston</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>https://gitlab.gnome.org/GNOME/mutter</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>https://github.com/KDE/kwin</ref>''' || [[KDE Plasma]]|| C++ || KDE’s compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>https://github.com/riverwm/river</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>https://github.com/WayfireWM/wayfire</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>https://github.com/cage-kiosk/cage</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |} ==References== <references /> 9f3a849b62e0220089405bf58f5f121d0cb05d30 3183 3160 2025-08-03T01:06:34Z Deviantsemicolon 174 /* Wayland Compositors */ added niri wikitext text/x-wiki == Wayland Compositors == {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>https://gitlab.freedesktop.org/wayland/weston</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>https://gitlab.gnome.org/GNOME/mutter</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>https://github.com/KDE/kwin</ref>''' || [[KDE Plasma]]|| C++ || KDE’s compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>https://github.com/riverwm/river</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>https://github.com/WayfireWM/wayfire</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>https://github.com/cage-kiosk/cage</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''Niri<ref>https://github.com/YaLTeR/niri</ref>''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |} ==References== <references /> b69ffe659bc1fe5e526f264068b1137044c1a9cd 0 2 3143 3121 2025-08-02T21:55:06Z RelativeAlbatros 187 add installation section wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent rolling release [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. Arch Linux is kept up-to-date by regularly updating the packages of the system. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Installation === Arch Linux is generally installed through following the [https://wiki.archlinux.org/title/Installation_guide Installation Guide], and reading the [https://wiki.archlinux.org Arch Wiki]. The default Arch Linux ISO image is provided with archinstall, an installation script. ==== Arch Installation Script ==== This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] bbfee1a4cc2e8c00ef15b43e7c9788774256b0f7 2 774 3144 2025-08-02T21:56:01Z Ow0cast 249 tmpl | create template for testing wikitext text/x-wiki {{#invoke:mbox|mbox | icon = OOjs UI icon alert.svg | title = {{{title|}}} | text = {{{text|}}} | extraclasses = mbox-med }} 890f96c6ba914d9de960ec0904f26dc8757cb142 0 775 3145 2025-08-02T21:56:39Z Miyu 183 Initialize page for nix-shell. wikitext text/x-wiki Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software before discarding upon exiting the shell. Example usage:<pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre> == References == <references /><!-- document auto run --> <!-- environment.sessionVariables.NIX_AUTO_RUN = "1"; --> <!-- export NIX_AUTO_RUN="1" --> <!-- add the image --> 0d6ac371e3b714138921559228f5efec7add9842 3159 3145 2025-08-02T22:17:31Z Miyu 183 Add Image. wikitext text/x-wiki [[File:2025-08-02 16-38-21.png|thumb|440x440px|Example of environment variable NIX_AUTO_RUN="1"; powered by nix-shell. Missing commands will be downloaded automatically unless there are multiple sources.]] Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software before discarding upon exiting the shell. Example usage:<pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre> == References == <references /><!-- document auto run --> <!-- environment.sessionVariables.NIX_AUTO_RUN = "1"; --> <!-- export NIX_AUTO_RUN="1" --> <!-- add the image --> b02c304c89eb247dcef5260f7b7957c270c3ed48 3169 3159 2025-08-02T22:45:57Z Miyu 183 Extend documentation on Auto run wikitext text/x-wiki [[File:2025-08-02 16-38-21.png|thumb|440x440px|Example of environment variable NIX_AUTO_RUN="1"; powered by nix-shell. Missing commands will be downloaded automatically unless there are multiple sources.]] Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software before discarding upon exiting the shell. ==== Example usage: ==== <pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre>By default your shell will be set to bash, you can modify this with <code>--command zsh</code> The shorthand for <code>--packages</code> is <code>-p</code> ==== Full usage: ==== <pre> [user:~]$ nix-shell --packages cowsay --command bash --run 'cowsay Success' --pure _________ < Success > --------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || </pre> ==== Auto run: [as shown in the image] ==== Auto run allows you to automatically download any packages you're missing, although it only checks the first word of your command. Allowing your to use any command like <code>inxi</code> by just typing the command name and running it, this extends to parameters as well, ex: <code>inxi -Fxxx</code> This c be enabled with <code>export NIX_AUTO_RUN="1"</code> Or by setting <code>environment.sessionVariables.NIX_AUTO_RUN = "1";</code> in your config. == References == <references /><!-- document auto run --> <!-- environment.sessionVariables.NIX_AUTO_RUN = "1"; --> <!-- export NIX_AUTO_RUN="1" --> e05239c88b1d2dac472981dda59f8b74a9676346 3172 3169 2025-08-02T22:55:39Z Miyu 183 Fix typos and detail parameters. wikitext text/x-wiki [[File:2025-08-02 16-38-21.png|thumb|440x440px|Example of environment variable NIX_AUTO_RUN="1"; powered by nix-shell. Missing commands will be downloaded automatically unless there are multiple sources.]] Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software before discarding upon exiting the shell. ==== Example usage: ==== <pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre>By default your shell will be set to bash, you can modify this with <code>--command zsh</code> The shorthand for <code>--packages</code> is <code>-p</code> ==== Full usage: ==== <pre> [user:~]$ nix-shell --packages cowsay --command bash --run 'cowsay Success' --pure _________ < Success > --------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || </pre><code>--pure</code> removes all other packages from the shell environment, say if you want to use <code>appimage-run</code> but the version of qt on your host is out-of-date. This way you don't have to remove/update qt outside the command. <code>--run</code> allows you to write out the full intended command, without first entering the shell. ==== Auto run: [as shown in the image] ==== Auto run allows you to automatically download any packages you're missing, although it only checks the first word of your command. Allowing you to use any command like <code>inxi</code> by just typing out the command and running it, this extends to parameters as well, ex: <code>inxi -Fxxx</code> This can be enabled with <code>export NIX_AUTO_RUN="1"</code> Or by setting <code>environment.sessionVariables.NIX_AUTO_RUN = "1";</code> in your config. == References == <references /> 17296b76f0f6288b0d13575f19d1ca4b798235fb 3175 3172 2025-08-02T23:39:36Z Miyu 183 Extend documentation to shell.nix wikitext text/x-wiki [[File:2025-08-02 16-38-21.png|thumb|440x440px|Example of environment variable NIX_AUTO_RUN="1"; powered by nix-shell. Missing commands will be downloaded automatically unless there are multiple sources.]] Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software before discarding upon exiting the shell. ===== Example usage: ===== <pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre>By default your shell will be set to bash, you can modify this with <code>--command zsh</code> The shorthand for <code>--packages</code> is <code>-p</code> ===== Full usage: ===== <pre> [user:~]$ nix-shell --packages cowsay --command bash --run 'cowsay Success' --pure _________ < Success > --------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || </pre><code>--pure</code> removes all other packages from the shell environment, say if you want to use <code>appimage-run</code> but the version of qt on your host is out-of-date. This way you don't have to remove/update qt outside the command. <code>--run</code> allows you to write out the full intended command, without first entering the shell. ==== Auto run: [as shown in the image] ==== Auto run allows you to automatically download any packages you're missing, although it only checks the first word of your command. Allowing you to use any command like <code>inxi</code> by just typing out the command and running it, this extends to parameters as well, ex: <code>inxi -Fxxx</code> This can be enabled via: <code>export NIX_AUTO_RUN="1"</code> Or by adding <code>environment.sessionVariables.NIX_AUTO_RUN = "1";</code> to your config. ==== Shell.nix ==== A <code>shell.nix</code> file sets up a reproducible development environment. When you run <code>nix-shell</code> it opens a shell with all your project's dependencies, keeping them isolated from your system. It can also be version locked by specifying channels or commit hashes. Below is an example <code>shell.nix</code> for a Node.js project<ref>https://nix.dev/tutorials/first-steps/declarative-shell.html</ref><pre>with (import <nixpkgs> {}); mkShell { buildInputs = [ nodejs-12_x yarn ]; shellHook = '' mkdir -p .nix-node export NODE_PATH=$PWD/.nix-node export NPM_CONFIG_PREFIX=$PWD/.nix-node export PATH=$NODE_PATH/bin:$PATH ''; }</pre> == References == <references /> db4bcc6281486e8013ffb3f1a65bd565dba255c8 3177 3175 2025-08-02T23:49:32Z Miyu 183 Installation info wikitext text/x-wiki [[File:2025-08-02 16-38-21.png|thumb|440x440px|Example of environment variable NIX_AUTO_RUN="1"; powered by nix-shell. Missing commands will be downloaded automatically unless there are multiple sources.]] Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software before discarding upon exiting the shell. Nix-shell is preinstalled with [[NixOS]] & [https://nixos.org Nix]. ===== Example usage: ===== <pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre>By default your shell will be set to bash, you can modify this with <code>--command zsh</code> The shorthand for <code>--packages</code> is <code>-p</code> ===== Full usage: ===== <pre> [user:~]$ nix-shell --packages cowsay --command bash --run 'cowsay Success' --pure _________ < Success > --------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || </pre><code>--pure</code> removes all other packages from the shell environment, say if you want to use <code>appimage-run</code> but the version of qt on your host is out-of-date. This way you don't have to remove/update qt outside the command. <code>--run</code> allows you to write out the full intended command, without first entering the shell. ==== Auto run: [as shown in the image] ==== Auto run allows you to automatically download any packages you're missing, although it only checks the first word of your command. Allowing you to use any command like <code>inxi</code> by just typing out the command and running it, this extends to parameters as well, ex: <code>inxi -Fxxx</code> This can be enabled via: <code>export NIX_AUTO_RUN="1"</code> Or by adding <code>environment.sessionVariables.NIX_AUTO_RUN = "1";</code> to your config. ==== Shell.nix ==== A <code>shell.nix</code> file sets up a reproducible development environment. When you run <code>nix-shell</code> it opens a shell with all your project's dependencies, keeping them isolated from your system. It can also be version locked by specifying channels or commit hashes. Below is an example <code>shell.nix</code> for a Node.js project<ref>https://nix.dev/tutorials/first-steps/declarative-shell.html</ref><pre>with (import <nixpkgs> {}); mkShell { buildInputs = [ nodejs-12_x yarn ]; shellHook = '' mkdir -p .nix-node export NODE_PATH=$PWD/.nix-node export NPM_CONFIG_PREFIX=$PWD/.nix-node export PATH=$NODE_PATH/bin:$PATH ''; }</pre> == References == <references /> 4f62f5b181c190efc559e1bf736f38f7bab1bb14 3180 3177 2025-08-03T00:46:01Z Miyu 183 Refine and complete. wikitext text/x-wiki [[File:2025-08-02 16-38-21.png|thumb|440x440px|Example of <code>NIX_AUTO_RUN=1</code> powered by nix-shell. Missing commands will be downloaded unless there are multiple sources.]] Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software from a shell before discarding it upon exiting. Included with [[NixOS]] and [https://nixos.org Nix]. ===== Example usage: ===== <pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre>By default, <code>nix-shell</code> uses <code>bash</code> as the shell. You can change this using the <code>--command</code> flag, for example: <code>--command zsh</code>. The <code>-p</code> flag is shorthand for <code>--packages</code>. ===== Full usage: ===== <pre> [user:~]$ nix-shell --packages cowsay \ --command bash \ --run 'cowsay Success' \ --pure _________ < Success > --------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || </pre><code>--pure</code> removes all other packages from the shell environment, say; if you want to use <code>appimage-run</code> but the version of qt on your host is out-of-date. This way you don't have to remove/update qt outside the command. <code>--run</code> allows you to write out the full intended command, without first entering the shell. More parameters can be found in <code>man nix-shell</code>. ==== Auto run: [as shown in the image] ==== Auto run allows you to automatically download any packages you're missing, although it only checks the first word of your command. Allowing you to use any command like <code>inxi</code> by just typing out the command and running it, this extends to parameters as well, ex: <code>inxi -Fxxx</code>. This can be enabled via: <code>export NIX_AUTO_RUN="1"</code> Or by adding <code>environment.sessionVariables.NIX_AUTO_RUN = "1";</code> to your configuration. ==== Shell.nix ==== A <code>shell.nix</code> file sets up a reproducible development environment. When you run <code>nix-shell</code> it opens a shell with all your project's dependencies, keeping them isolated from your system. It can also be version locked by specifying channels or commit hashes. Below is an example <code>shell.nix</code> for a Node.js project.<ref>https://nix.dev/tutorials/first-steps/declarative-shell.html</ref><pre>with (import <nixpkgs> {}); mkShell { buildInputs = [ nodejs-12_x yarn ]; shellHook = '' mkdir -p .nix-node export NODE_PATH=$PWD/.nix-node export NPM_CONFIG_PREFIX=$PWD/.nix-node export PATH=$NODE_PATH/bin:$PATH ''; }</pre> == References == <references /> 631571e8427a1eb63f6ea85383b9378153c5cca7 2 776 3146 2025-08-02T21:58:04Z Ow0cast 249 tmpl | create template for testing wikitext text/x-wiki {{User:Ow0cast/TemplateAlertMedium | title = This page is a stub. {{User:Ow0cast/TemplateAssistByEditing|action=expanding}} | text = This message means that this page has been deemed not long enough to provide meaningful coverage of its topic. }} 9f8a7033b3582169ba0a4bc9614e6d98fc408b19 6 777 3147 2025-08-02T21:58:51Z Miyu 183 wikitext text/x-wiki Example of NIX_AUTO_RUN="1". A user is trying to use a command they don't have in their environment, and are prompted to select where to download it from, there are multiple options. 21e2b7501e2ec7dcc862f9001ac5db74a529aaf6 0 763 3148 3131 2025-08-02T22:03:26Z DeltaNova 193 Added awesome and Compiz wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |awesome |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |Compiz |Compiz is a compositing window manager for the X Window System. |- |Openbox |A minimal and highly configurable stacking window manager written in C. |- |twm |Tab Window Manager - standard X11 window manager since 1989. |- |IceWM |Lightweight window manager that includes a taskbar, start menu and other features. |- |Window Maker |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |} 68ab7b5ce108869ca7d5fe7886f921050c0b1a38 3152 3148 2025-08-02T22:11:34Z DeltaNova 193 References Added wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |awesome<ref>https://github.com/awesomeWM/awesome</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |Compiz |Compiz is a compositing window manager for the X Window System. |- |Openbox |A minimal and highly configurable stacking window manager written in C. |- |twm |Tab Window Manager - standard X11 window manager since 1989. |- |IceWM |Lightweight window manager that includes a taskbar, start menu and other features. |- |Window Maker |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |} ==References== <references /> 016dff6c38f57fdfe227ab23f3ee6ee33ef5988c 3156 3152 2025-08-02T22:15:04Z DeltaNova 193 References Added wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |awesome<ref>https://github.com/awesomeWM/awesome</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |Compiz |Compiz is a compositing window manager for the X Window System. |- |Openbox |A minimal and highly configurable stacking window manager written in C. |- |twm |Tab Window Manager - standard X11 window manager since 1989. |- |IceWM<ref>https://github.com/bbidulock/icewm</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |Window Maker<ref>https://github.com/window-maker/wmaker</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |} ==References== <references /> f12bf83701fdbe454bbbbde89bf6a80402606d86 8 592 3149 2107 2025-08-02T22:05:54Z Atmois 13 Add other license option wikitext text/x-wiki * Unknown_copyright|I don't know exactly * Other License * Free licenses: ** PD|Public Domain ** CC0|Creative Commons Zero ** CC-BY-4.0|Creative Commons Attribution 4.0 ** CC-BY-SA-4.0|Creative Commons Attribution Sharealike 4.0 ** GPL|GNU General Public License ** LGPL|GNU Lesser General Public License eb9f25ca82750fe504d596aa15b793ae8886f8ec 0 414 3150 2939 2025-08-02T22:10:11Z RelativeAlbatros 187 add category wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970s, adopted by the majority of UNIX systems.<ref>https://dl.acm.org/doi/10.1145/2509136.2509515</ref> The language was initially implemented by Dennis Ritchie whilst working at Bell Labs, and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and pre-processors for their respective machines and instruction sets.<ref>https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>https://en.cppreference.com/w/c/language/history</ref> Some popular compilers for the C programming language include GNU GCC, Clang, TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the Clang compiler toolchain, however, for example, [[Illumos]]<ref>https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/</ref> and [[Plan 9]]<ref>https://9p.io/sys/doc/compiler.html</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>https://smlfamily.github.io/Basis/</ref><ref>https://doc.rust-lang.org/beta/std/index.html</ref><ref>https://ziglang.org/documentation/master/std/</ref><ref>https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html</ref><ref>https://www.scala-lang.org/api/current/</ref><ref>https://ocaml.org/manual/5.2/api/index.html</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>https://www.musl-libc.org/faq.html</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>https://wiki.musl-libc.org/compatibility</ref><ref>https://www.fefe.de/dietlibc/FAQ.txt</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>https://wiki.osdev.org/C_Library</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>https://nullprogram.com/blog/2017/03/30/</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as GNU Autotools, CMake, Meson, Zig's build toolchain among a plethora others, however for ideological<ref>https://suckless.org/sucks/</ref><ref>https://www.interaction-design.org/literature/topics/keep-it-simple-stupid</ref><ref>http://harmful.cat-v.org/software/GNU/auto-hell</ref> and practical<ref>https://twdev.blog/2021/08/cmake/</ref><ref>https://silverhammermba.github.io/blog/2023/01/06/gradle</ref><ref>https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>https://github.com/Mercury-Language/mercury</ref><ref>https://github.com/NetBSD/src</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, meta-programming and structural components of a C code base; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>https://docs.kernel.org/process/5.Posting.html</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS|open source]] code bases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995–2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial,<ref>https://web.mit.edu/~simsong/www/ugh.pdf</ref> many attribute issues regarding C to fragmentation and portability issues,<ref>http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful</ref> lack of type safety and primitive resource access checks,<ref>https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review</ref> poor administration on part of the C Language Working Group,<ref>https://cor3ntin.github.io/posts/c/</ref> and overall worsening over time.<ref>https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html</ref><ref>https://wiki.theory.org/YourLanguageSucks</ref> == References == <references /> [[Category:Programming Languages]] 401f2c063fd0398d8a9a3d9622e68b848e5cae3c 0 778 3151 2025-08-02T22:11:11Z RelativeAlbatros 187 initial description wikitext text/x-wiki '''C++''' is a high-level, general-purpose programming language created by Danish computer scientist Bjarne Stroustrup. [[Category:Programming Languages]] 71767461d071439ea05b6f0d27ae0ca47babfda7 0 198 3154 3033 2025-08-02T22:13:34Z True1ann 202 Add OpenRC to "some" of the Init Systems, as it is a commonly used alternative for systemd wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AIX]] |A series of Unix-Based Operating systems for Power servers. |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] 96567998a21fa1ff1af4923552d52dbbde6ad887 3184 3154 2025-08-03T01:12:26Z Cherry 131 /* Other Independent Distributions */ Remove AIX as it is not a Linux Distribution wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: [[OpenRC]], [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] fa8a7c4a1780e7aa401ab1a0bee23f3cbcffe88f 0 779 3157 2025-08-02T22:15:50Z RelativeAlbatros 187 initial description wikitext text/x-wiki '''Haskell''' (/ˈhæskəl/) is a general-purpose, statically typed, purely functional programming language with type inference and lazy evaluation. [[Category:Programming Languages]] 4d4ccb2f970d9d15dde96a9de57ca80418ede19d 3158 3157 2025-08-02T22:16:16Z RelativeAlbatros 187 remove redundant pronunciation wikitext text/x-wiki '''Haskell''' is a general-purpose, statically typed, purely functional programming language with type inference and lazy evaluation. [[Category:Programming Languages]] 6b67d21b85d7ccc8bb90cf389fcbb1aff974034d 0 780 3162 2025-08-02T22:28:23Z RelativeAlbatros 187 Init wikitext text/x-wiki '''Cron''' is a job-scheduler in [[UNIX|Unix-like]] [[Operating System|Operating Systems]]. Users set-up cron jobs to run at periodically at fixed times, dates and intervals. === Crone implementations === * cronie * fcrone * dcrone * vixie-cron * scrone-git === Usage === edit your cron-jobs by running: crontab -e each line of crontab file represents a job and is formatted like this: * * * * * <command to execute> # | | | | | # | | | | day of the week (0–6) (Sunday to Saturday; # | | | month (1–12) 7 is also Sunday on some systems) # | | day of the month (1–31) # | hour (0–23) # minute (0–59) Crontab uses the following symbols {| class="wikitable" |+ !Symbol !Description |- |'''*''' |specifies every possible time interval |- |''',''' |List multiple values separated by a comma. |- |'''-''' |specify a range between two numbers |- |'''/''' |Specify a periodicity/frequency using a slash |} Crontab also has some special keywords: {| class="wikitable" |+ !Keyword !Description |- |'''@reboot''' |at startup |- |'''@yearly''' |once a year |- |'''@anually''' |identical to @yearly |- |'''@montly''' |once a month |- |'''@weekly''' |once a week |- |'''@daily''' |once a day |- |'''@midnight''' |identitcal to @daily |- |'''@hourly''' |once an hour |} 5e81bb614667da01ee1a1a69635f38a57aee8d86 3163 3162 2025-08-02T22:31:50Z RelativeAlbatros 187 add basic cron commands wikitext text/x-wiki '''Cron''' is a job-scheduler in [[UNIX|Unix-like]] [[Operating System|Operating Systems]]. Users set-up cron jobs to run at periodically at fixed times, dates and intervals. === Crone implementations === * cronie * fcrone * dcrone * vixie-cron * scrone-git === Usage === edit your cron-jobs by running: crontab -e each line of crontab file represents a job and is formatted like this: * * * * * <command to execute> # | | | | | # | | | | day of the week (0–6) (Sunday to Saturday; # | | | month (1–12) 7 is also Sunday on some systems) # | | day of the month (1–31) # | hour (0–23) # minute (0–59) Crontab uses the following symbols {| class="wikitable" |+ !Symbol !Description |- |'''*''' |specifies every possible time interval |- |''',''' |List multiple values separated by a comma. |- |'''-''' |specify a range between two numbers |- |'''/''' |Specify a periodicity/frequency using a slash |} Crontab also has some special keywords: {| class="wikitable" |+ !Keyword !Description |- |'''@reboot''' |at startup |- |'''@yearly''' |once a year |- |'''@anually''' |identical to @yearly |- |'''@montly''' |once a month |- |'''@weekly''' |once a week |- |'''@daily''' |once a day |- |'''@midnight''' |identitcal to @daily |- |'''@hourly''' |once an hour |} ==== Basic cron commands ==== {| class="wikitable" |+ !Command !Description |- |'''crontab -l''' |list your cronjobs |- |'''crontab -e''' |edit your cronjobs |- |'''crontab -r''' |remove all your cronjobs |} 67f0ca1c93e1d16191f022ec4d0cbafa000033b3 0 250 3164 2935 2025-08-02T22:32:12Z Landline 196 Fix url for the deiteris fork wikitext text/x-wiki {{Cleanup|Instructions need to be split onto their own page under the Guides namespace}}{{Cleanup|Incomplete page}}[[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. == Ana/Miniconda Setup == While not required, it is heavily recommended to use ''conda'' to manage Python libraries required by various machine learning and artificial intelligence projects from places like GitHub and Hugging Face. Conda exists as a distinct virtual environment separate from the native distribution's Python packages. Users may specify version number and install additional plugins as well as packages within an environment utilizing conda. It is recommended to read the Linux setup for Miniconda on their [https://www.anaconda.com/docs/getting-started/miniconda/install#linux official website]. The install for Miniconda is very unorthodox compared to installing other packages on a Linux system - be mindful. == Stable Diffusion Setup - WebUI (Forge) == [[File:Cat.png|thumb|A cat generated using FLUX.1 [schnell].]] According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> Stable Diffusion WebUI Forge is a version of Stable Diffusion WebUI that offers additional support for FLUX.1 [dev] and FLUX.1 [schnell] models. For some users, using the Forge version may result in greater stability using FLUX as opposed to the vanilla version. Simply clone the Forge repository:<syntaxhighlight lang="bash"> git clone https://github.com/lllyasviel/stable-diffusion-webui-forge/issues </syntaxhighlight>...install required pip packages:<syntaxhighlight lang="bash"> pip3 install -r requirements.txt </syntaxhighlight>...and run the program:<syntaxhighlight lang="bash"> python3 launch.py </syntaxhighlight> ==== Extra notes ==== ===== Run options/flags ===== It is advisory to set additional launch parameters for better performance, e.g. using '''xformers''' for optimization or to specify a certain directory where models are stored. You can place these in a separate xxx.sh file to run instead of having to copy-and-paste large strings - here is an example:<syntaxhighlight lang="bash"> python3 launch.py --listen --xformers --enable-insecure-extension-access --cuda-malloc --port 7860 --vae-dir=/run/media/jennaannilyn/Pikmin3/models/vae --ckpt-dir=/run/media/jennaannilyn/Pikmin3/AI/ --lora-dir=/run/media/jennaannilyn/Pikmin3/AI/models/loras --no-half-vae </syntaxhighlight> === Installing and using Ollama on Linux === [[File:Ollama.png|thumb|Ollama says hi to ATL.]] According to Ollama's main page, Ollama is used to run open-source/open-weight, locally hosted Large Language Models. == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>https://github.com/w-okada/voice-changer</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU, c'''onsidering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> ==== The Deiteris Fork ==== Some users may prefer Deiteris's version, which may offer extra precision and performance for more advanced users. The process is almost identical, except that you must clone his fork:<syntaxhighlight lang="bash"> git clone https://github.com/deiteris/voice-changer </syntaxhighlight>...while consequently running a different Python command:<syntaxhighlight lang="bash"> python3 ./main.py </syntaxhighlight> == References == [[Category:Guides]] 3979e4c67c0fdea4629c0a46bd413bb2770a4afe 0 781 3165 2025-08-02T22:34:46Z DeltaNova 193 Initial Page about RPM wikitext text/x-wiki = RPM Packages = '''RPM''' stands for '''Red Hat Package Manager'''. It is both a package format (`.rpm`) and the name of the package management system used primarily in Red Hat-based Linux distributions, including: * Red Hat Enterprise Linux (RHEL) * Fedora * CentOS * AlmaLinux * Rocky Linux * openSUSE (with some differences) == Overview == An RPM package is a file that contains: * Compiled software binaries * Configuration files * Metadata (name, version, dependencies, etc.) * Installation and removal scripts The standard file extension is `.rpm`. RPM packages are used to install, update, and remove software cleanly and consistently, while tracking file ownership and managing dependencies. == RPM vs DEB == RPM is used in Red Hat-based systems, while DEB is used in Debian-based systems (like Ubuntu). Both serve similar purposes but are not interchangeable. == Components of an RPM Package == * **Header**: Contains metadata (name, version, architecture, etc.) * **Payload**: The actual files to be installed * **Scripts**: Optional pre/post-install and removal scripts == Common Tools == * `rpm` — Low-level tool for querying, installing, and removing RPM packages * `dnf` or `yum` — High-level package managers that resolve dependencies and interact with repositories * `rpmbuild` — Tool for building RPM packages from SPEC files * `rpmlint` — Linter to check RPM quality and packaging errors == Basic Commands == === Installing an RPM file === <syntaxhighlight lang="bash"> sudo rpm -ivh package.rpm </syntaxhighlight> Or using DNF (which handles dependencies): <syntaxhighlight lang="bash"> sudo dnf install ./package.rpm </syntaxhighlight> === Query installed packages === <syntaxhighlight lang="bash"> rpm -q package-name </syntaxhighlight> === List all installed RPMs === <syntaxhighlight lang="bash"> rpm -qa </syntaxhighlight> === Remove a package === <syntaxhighlight lang="bash"> sudo rpm -e package-name </syntaxhighlight> === Verify a package === <syntaxhighlight lang="bash"> rpm -V package-name </syntaxhighlight> == Advantages == * Dependency tracking * Transaction-based installation/removal * Clean upgrade paths * Strong ecosystem support (DNF, YUM, repositories, etc.) == Limitations == * Requires careful dependency management * Not compatible with DEB systems * Binary format — not human-readable == External Resources == * [https://rpm.org/ Official RPM Site] * [https://fedoraproject.org/wiki/RPM Fedora RPM Guide] * [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Fedora Packaging Guidelines] == See Also == * [[YUM]] * [[DNF]] * [[rpmbuild]] 497c239f39bad93fa6a885333bb2d95cd19108a4 3167 3165 2025-08-02T22:42:38Z DeltaNova 193 Add Category:Package Managers wikitext text/x-wiki = RPM Packages = '''RPM''' stands for '''Red Hat Package Manager'''. It is both a package format (`.rpm`) and the name of the package management system used primarily in Red Hat-based Linux distributions, including: * Red Hat Enterprise Linux (RHEL) * Fedora * CentOS * AlmaLinux * Rocky Linux * openSUSE (with some differences) == Overview == An RPM package is a file that contains: * Compiled software binaries * Configuration files * Metadata (name, version, dependencies, etc.) * Installation and removal scripts The standard file extension is `.rpm`. RPM packages are used to install, update, and remove software cleanly and consistently, while tracking file ownership and managing dependencies. == RPM vs DEB == RPM is used in Red Hat-based systems, while DEB is used in Debian-based systems (like Ubuntu). Both serve similar purposes but are not interchangeable. == Components of an RPM Package == * **Header**: Contains metadata (name, version, architecture, etc.) * **Payload**: The actual files to be installed * **Scripts**: Optional pre/post-install and removal scripts == Common Tools == * `rpm` — Low-level tool for querying, installing, and removing RPM packages * `dnf` or `yum` — High-level package managers that resolve dependencies and interact with repositories * `rpmbuild` — Tool for building RPM packages from SPEC files * `rpmlint` — Linter to check RPM quality and packaging errors == Basic Commands == === Installing an RPM file === <syntaxhighlight lang="bash"> sudo rpm -ivh package.rpm </syntaxhighlight> Or using DNF (which handles dependencies): <syntaxhighlight lang="bash"> sudo dnf install ./package.rpm </syntaxhighlight> === Query installed packages === <syntaxhighlight lang="bash"> rpm -q package-name </syntaxhighlight> === List all installed RPMs === <syntaxhighlight lang="bash"> rpm -qa </syntaxhighlight> === Remove a package === <syntaxhighlight lang="bash"> sudo rpm -e package-name </syntaxhighlight> === Verify a package === <syntaxhighlight lang="bash"> rpm -V package-name </syntaxhighlight> == Advantages == * Dependency tracking * Transaction-based installation/removal * Clean upgrade paths * Strong ecosystem support (DNF, YUM, repositories, etc.) == Limitations == * Requires careful dependency management * Not compatible with DEB systems * Binary format — not human-readable == External Resources == * [https://rpm.org/ Official RPM Site] * [https://fedoraproject.org/wiki/RPM Fedora RPM Guide] * [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Fedora Packaging Guidelines] == See Also == * [[YUM]] * [[DNF]] * [[rpmbuild]] [[Category:Package Managers]] 91e0f3ce593808cbae51220cf9834c7ce887c73f 0 782 3166 2025-08-02T22:35:59Z RelativeAlbatros 187 initial description wikitext text/x-wiki Eww (Elkowars Wacky Widgets) is a standalone widget system made in Rust by Elkowar that allows to implement custom widgets in any window manager. Configuration is done through a yuck and a scss (or css) file.<ref>{{Cite|url=https://github.com/elkowar/eww|title=original repo|author=Elkowar}}</ref> [[Category:Widget system]] b525bbc7a9eda2b28062e50c0bce3a6c8b1c45ea 0 169 3168 3037 2025-08-02T22:45:24Z DeltaNova 193 Switch to local cite reference wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[Rpm]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] [[Category:Terminology]] 42c84b143a135ba4da3ad7b09955f4b13834a61b 3170 3168 2025-08-02T22:50:55Z DeltaNova 193 /* List of Package Managers */ Updated info about rpm and dnf wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] [[Category:Terminology]] 43fa14bdda857046151b5fa4fa33d3006be6dadd 2 783 3171 2025-08-02T22:53:36Z Ow0cast 249 tmpl | create template for missing infobox wikitext text/x-wiki {{User:Ow0cast/TemplateAlertMedium | title = This page is missing an infobox. {{User:Ow0cast/TemplateAssistByEditing|action=creating}} | text = This message means that this page does not have an infobox. An infobox is a panel in the top right corner of the article and contains key facts about a topic, such as the package manager for a distro or the language of a software TODO create index of infobox templates and link to it }} 9449e91e021d037a0872401172fcd308bacb0f9c 0 178 3173 3028 2025-08-02T23:11:30Z DeltaNova 193 Linux kernel page major overhaul wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] = Linux Kernel = The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and deallocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under the terms of the [[GNU General Public License]] version 2 (GPLv2), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] * [[Unix]] * [[Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> [[Category:Terminology]] d52a66ffb76a8fcefcad94d6048a5b27567cee21 0 784 3174 2025-08-02T23:34:42Z Average USA patriot 204 Created page with "Zorin OS" wikitext text/x-wiki Zorin OS 3765201511395b4aeedd9497d18b9691206c4789 3178 3174 2025-08-02T23:53:44Z Average USA patriot 204 wikitext text/x-wiki fdsfsfs {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[apt]] | defaultdesktops = GNOME | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }} Zorin OS is a ubuntu based linux distribution made for a better Work flow. with a modifyed version of the Gnome GUI, it also has paid model that comes with more desktop options and software. it was frist realsed on the frist of july, 2009, under the name Zorin OS 1.0 61a226e9b04e7e74f850a2bdf6fdc374b7816ad9 3179 3178 2025-08-02T23:55:08Z Average USA patriot 204 wikitext text/x-wiki {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[apt]] | defaultdesktops = GNOME | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }} Zorin OS is a ubuntu based linux distribution made for a better Work flow. with a modifyed version of the Gnome GUI, it also has paid model that comes with more desktop options and free software. it was frist realsed on the frist of july, 2009, under the name Zorin OS 1.0 22ba05170fa5112e436fc8bf069c7cd8971bea13 6 785 3176 2025-08-02T23:40:17Z Average USA patriot 204 wikitext text/x-wiki Official logo for Zorin and Zorin OS 63beb247c938054295f62cb42e5ebc5c47690ad1 6 786 3181 2025-08-03T00:53:00Z Miyu 183 wikitext text/x-wiki Floralheat Unicode 4b936cdba4f7665ca354c716b76a2c8d072cc813 2 787 3182 2025-08-03T00:54:23Z Miyu 183 Update my profile. wikitext text/x-wiki [[File:Floralheat.png|none|thumb|406x406px]] === Hi, I'm miyu. === I like All Things Linux, literally. Checkout my NixOS configuration here: https://github.com/fndov/NixPro/ Here's some of my bookmarks for Nix! https://github.com/search?q=+language%3ANix&type=code https://search.nixos.org/packages https://search.nixos.org/options https://home-manager-options.extranix.com/ https://nixos.wiki/wiki/Flakes b191a9894c667c72437c3e8875159bddb0fae445 0 171 3185 3094 2025-08-03T01:30:12Z Miyu 183 Detail differences and source, connecting nix-shell. wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such has nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] 8ad1825527a22f21d1153baa577f74764d40e03f 0 775 3186 3180 2025-08-03T01:48:12Z Miyu 183 Add to software category. wikitext text/x-wiki [[File:2025-08-02 16-38-21.png|thumb|440x440px|Example of <code>NIX_AUTO_RUN=1</code> powered by nix-shell. Missing commands will be downloaded unless there are multiple sources.]] Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software from a shell before discarding it upon exiting. Included with [[NixOS]] and [https://nixos.org Nix]. ===== Example usage: ===== <pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre>By default, <code>nix-shell</code> uses <code>bash</code> as the shell. You can change this using the <code>--command</code> flag, for example: <code>--command zsh</code>. The <code>-p</code> flag is shorthand for <code>--packages</code>. ===== Full usage: ===== <pre> [user:~]$ nix-shell --packages cowsay \ --command bash \ --run 'cowsay Success' \ --pure _________ < Success > --------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || </pre><code>--pure</code> removes all other packages from the shell environment, say; if you want to use <code>appimage-run</code> but the version of qt on your host is out-of-date. This way you don't have to remove/update qt outside the command. <code>--run</code> allows you to write out the full intended command, without first entering the shell. More parameters can be found in <code>man nix-shell</code>. ==== Auto run: [as shown in the image] ==== Auto run allows you to automatically download any packages you're missing, although it only checks the first word of your command. Allowing you to use any command like <code>inxi</code> by just typing out the command and running it, this extends to parameters as well, ex: <code>inxi -Fxxx</code>. This can be enabled via: <code>export NIX_AUTO_RUN="1"</code> Or by adding <code>environment.sessionVariables.NIX_AUTO_RUN = "1";</code> to your configuration. ==== Shell.nix ==== A <code>shell.nix</code> file sets up a reproducible development environment. When you run <code>nix-shell</code> it opens a shell with all your project's dependencies, keeping them isolated from your system. It can also be version locked by specifying channels or commit hashes. Below is an example <code>shell.nix</code> for a Node.js project.<ref>https://nix.dev/tutorials/first-steps/declarative-shell.html</ref><pre>with (import <nixpkgs> {}); mkShell { buildInputs = [ nodejs-12_x yarn ]; shellHook = '' mkdir -p .nix-node export NODE_PATH=$PWD/.nix-node export NPM_CONFIG_PREFIX=$PWD/.nix-node export PATH=$NODE_PATH/bin:$PATH ''; }</pre> == References == <references /> [[Category:Software]] ac23fe88756a08f5f3fad464ec2b8daab8573386 0 682 3187 2986 2025-08-03T01:54:31Z Cherry 131 Corrected Various Things on the Puppy Linux Card wikitext text/x-wiki {{Needs Citations}}{{DistributionInfobox|title=Puppy Linux|image=[[File:Puppy logo.svg|frameless|Puppy Linux Logo]]|caption=Puppy Linux Logo|releasestatus=Maintained|releasemodel=Rolling Release / Stable|packagemanager=[[dpkg]], [[XBPS]], PPM|defaultdesktops=JWM, [[Xfce]], LXDE|usagetype=Desktop|architectures=x86_64, x86, ARM|website=[https://puppylinux-woof-ce.github.io/ Link]}}'''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003. fb5252d477e863fdae83f85399383ca3bd84fbc9 6 788 3188 2025-08-03T01:55:37Z Lost 176 svg logo of templeos wikitext text/x-wiki == Summary == svg logo of templeos == Licensing == {{CC0}} 4a8b5e7228e41af0319ca73bac3be14305e1ea3d 0 784 3189 3179 2025-08-03T02:12:30Z Average USA patriot 204 wikitext text/x-wiki {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[apt]] | defaultdesktops = GNOME | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }} Zorin OS is a ubuntu based linux distribution made for newcomers to linux, with a modifyed version of the Gnome GUI and XFCE 4 that is familiar to windows users. it also has paid model that comes with more desktop options and free software. it was frist realsed on the frist of july, 2009, under the name Zorin OS 1.0 5ff671decb2bff55261b1adb5c652c9b0d235072 0 217 3190 2954 2025-08-03T02:56:58Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}} {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]] |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}} [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> == References == <references /> [[Category:Linux Distributions]] 4c416b9ffc4105d95c30625be5b5772110650ae6 0 667 3191 3106 2025-08-03T02:57:59Z Ow0cast 249 /* top */ semi automated clean up |, typos fixed: February of 2019 → February 2019 wikitext text/x-wiki {{Cleanup|Incomplete page}}{{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}}'''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. The owner of the UNIX® trademark has been The Open Group since 1994.<ref>[https://unix.org/what_is_unix.html What is UNIX ®?] unix.org</ref> Examples of modern UNIX operating systems include Apple's MacOS and IBM AIX. Being genetic UNIX® is not required for UNIX® certification. Formerly, Inspur K-UX was certified UNIX®, specifically versions 2.0 and 3.0. Inspur K-UX's UNIX® certification expired in February 2019 and has yet to be renewed.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Inspur_K-UX|title=Inspur K-UX|author=Huihermit|year=21 January 2025|accessdate=2 August 2025}}</ref> == References == f58e9159893e4480a30496c340cfc607221f35ad 0 198 3192 3184 2025-08-03T02:59:10Z Ow0cast 249 semi automated clean up | remove duplicate wikilinks wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] a42bd34598a5adb7953f75caa31cde99c8d09625 3203 3192 2025-08-03T05:40:41Z Average USA patriot 204 wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>https://en.wikipedia.org/wiki/Arch_Linux</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>https://en.wikipedia.org/wiki/Zenwalk</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>https://crux.nu/</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>https://slitaz.org/en/</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] 3685b962da0a576f308468e42134fc9c395c6f4e 0 429 3193 3123 2025-08-03T02:59:42Z Ow0cast 249 /* Ports System */ semi automated clean up |, typos fixed: , → , wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] <ref>https://crux.nu/doc/prt-get%20-%20User%20Manual.html</ref> with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. CRUX has had 27 documented releases <ref>http://ftp.morpheus.net/pub/linux/crux/</ref>,from 0.9.7 to the current release, 3.8 ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "Pkgfiles," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> == Ports System == CRUX uses a BSD-style ports system, revolving around the packaging system pkgutils, each port contains a Pkgfile which tells pkgmk or prt-get what to do, it is a relatively simple process, that involves fetching the source declared in the Pkgfile (Or if the file is already present and matches the checksum, it extracts it.), Following the compilation steps declared in the Pkgfile while using the optimizations and arguments declared in ```/etc/pkgmk.conf```, this part is declared in the ```build()``` section of the Pkgfile, since a Pkgfile is essentially a BASH script, it can be edited by the end user to match their own needs. <ref>https://crux.nu/Main/Handbook3-8-Package</ref> == References == [[Category:Linux Distributions]] aac0b9bc9156cead629f85c1c43bda11808d73e1 3240 3193 2025-08-04T10:35:51Z Ok 425 Insert distro info table alongside small additional info for the page. wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=CRUX|image=[[File: Crux.png]]|caption=The Official CRUX logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[pkgutils]]|defaultdesktops=[[KDE Plasma]]|usagetype=Desktop|architectures=x86_64|website=[https://crux.nu/ crux.nu]}}CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] <ref>https://crux.nu/doc/prt-get%20-%20User%20Manual.html</ref> with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>https://crux.nu/Main/About</ref> Unlike other distributions, the primary goal of CRUX is not to be the most popular or to put as many features as possible into the system. The idea is rather to build a streamlined distribution, targetted at a specific audience which in turn gets a system without compromises. Some of the characteristics of CRUX are: * KISS (Keep It Simple, Stupid) concept, applied to both the system and the development process * Source based package installation using a ports system * Simplicity over automation * Targetted at experienced users with compact, to the point documentation * Native configurations over configuration abstraction layers * Up to date features and packages, however no bleeding edge software in the main repositories * Easy way to extend the system by yourself * Active community of contributors outside the core development team ==History== CRUX was founded by Per Lidén.<ref>https://crux.nu/Profiles/PerLiden</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>https://crux.nu/Main/About</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. CRUX has had 27 documented releases <ref>http://ftp.morpheus.net/pub/linux/crux/</ref>,from 0.9.7 to the current release, 3.8 ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>https://crux.nu/Main/About</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "Pkgfiles," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>https://crux.nu/Main/About</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>https://crux.nu/Main/About</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>https://crux.nu/Main/About</ref> == Ports System == CRUX uses a BSD-style ports system, revolving around the packaging system pkgutils, each port contains a Pkgfile which tells pkgmk or prt-get what to do, it is a relatively simple process, that involves fetching the source declared in the Pkgfile (Or if the file is already present and matches the checksum, it extracts it.), Following the compilation steps declared in the Pkgfile while using the optimizations and arguments declared in ```/etc/pkgmk.conf```, this part is declared in the ```build()``` section of the Pkgfile, since a Pkgfile is essentially a BASH script, it can be edited by the end user to match their own needs. <ref>https://crux.nu/Main/Handbook3-8-Package</ref> == References == [[Category:Linux Distributions]] 2cd39b40e8b5f5d81ab7967b08ee2315c0bcc5de 0 769 3194 3183 2025-08-03T03:00:06Z Ow0cast 249 /* Wayland Compositors */ semi automated clean up |, typos fixed: ’s → 's wikitext text/x-wiki == Wayland Compositors == {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>https://gitlab.freedesktop.org/wayland/weston</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>https://gitlab.gnome.org/GNOME/mutter</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>https://github.com/KDE/kwin</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>https://github.com/riverwm/river</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>https://github.com/WayfireWM/wayfire</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>https://github.com/cage-kiosk/cage</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''Niri<ref>https://github.com/YaLTeR/niri</ref>''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |} ==References== <references /> a6cf69611688ff06017d259c94813d731ad24a88 0 778 3195 3151 2025-08-03T03:57:20Z Rayk4z1 62 Added a lot of info about C++, deleting the last's dude singular sentence and added actual information with good sources. Installation Guide, WIP Compatibility section. wikitext text/x-wiki '''C++''', not to be confused with the g++ compiler, is a high-level multi-use programming language built on top of the C programming Language to add Object-Oriented Programming features.<ref>Bjarne Stroustrup, The University of Edinburgh - The Essence of C++: https://www.youtube.com/watch?v=86xWVb4XIyE</ref> The C++ programming language was '''originally developed by Bjarne Stroustrup in 1985'''. From its inception, C++ was designed with key principles in mind: '''efficient resource usage, high performance, and exceptional flexibility'''.<ref>Bjarne Stroustrup - The C++ Programming Language:https://archive.org/details/cprogramminglang00stro_0</ref> By the release of '''C++98 in 1997''', the language had evolved significantly, incorporating advanced features like '''functional programming capabilities and enhanced low-level memory manipulation'''. These additions greatly expanded its utility, making it a foundational language for developing major operating systems like '''Linux and Windows''', as well as various microcomputer applications. <ref>Bjarne Stroustrup, C++ Applications: https://www.stroustrup.com/applications.html (Accessed 8/2/2025)</ref>Today, C++ is a wide-spread language, found in a vast array of applications. It powers everything from '''desktop applications and high-performance video games to robust server systems and precision-critical software'''. Its versatility has made it a common choice for demanding computing tasks. <ref>ISO/IEC 14882:2024: https://www.iso.org/standard/83626.html</ref> C++ is predominantly used as a '''compiled language''', meaning its source code is translated into machine-readable instructions before execution. Numerous companies and vendors offer C++ compilers. Notable examples include '''g++ from the GNU Software Foundation''', along with compilers distributed by major tech players like '''Microsoft, Intel, and IBM'''.<ref>Wikipedia, Category: C++ Compilers https://en.wikipedia.org/wiki/Category:C%2B%2B_compilers (Accessed 8/2/2025)</ref> Despite its widespread adoption, powerful functionality, and flexibility, C++ does face criticism within the programming community. Prominent figures, such as '''Linus Torvalds, the creator of the Linux Kernel'''<ref>Linus Torvalds, LWN.net, Re: [RFC] Convert builin-mailinfo.c to use The Better String Library.: https://lwn.net/Articles/249460/ (Accessed 8/2/2025)</ref>, have voiced concerns about certain aspects of the language, among '''other notable voices'''. Since 2012, C++ has followed a predictable '''three-year release schedule''' for new versions of its standard. Currently, the active standard is '''C++23''', and the next anticipated release, following this established pattern, will be '''C++26'''. This consistent release cycle allows developers and compiler implementers to plan for upcoming features and changes.<ref>Rohit Sharma, C++: Where It's Heading and It's New Features: https://dzone.com/articles/c-where-is-it-heading-and-what-are-the-new-feature (Accessed 8/2/2025)</ref> = Compatibility = With different vendors producing different compilers, there is bound to be some incompatibility. Yet C++ standards committee members have overall decided it was best that the implementation of fixes for a couple of common problems found in many compilers to be solved by the compiler without having a "standardized" way of doing so. It should also be noted that C++ is not just a version of C with more features. In other words, valid C code might not exactly be valid in C++. Many common examples include OOP features such as classes. The term <code>class</code> in C++ can be used as a variable name in a C program.<ref>Itanium C++ ABI: https://itanium-cxx-abi.github.io/cxx-abi/ (Accessed 8/2/2025)</ref> (WIP) = Installation = To install support for the C++ Language, ensure you have a viable compiler, it is likely you already have a compiler on a Linux System, to check, you can run:<syntaxhighlight lang="shell-session"> [user] $ g++ --version g++ (GCC) 15.1.1 20250425 Copyright (C) 2025 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [user] $ </syntaxhighlight>If you do not have a compiler, you can install one using your distributions package manager OR you can directly download it from source, these commands will download the GCC-Suite (aka, gcc, g++, etc).<syntaxhighlight lang="shell-session"> [user] $ sudo apt install build-essential # for apt (Ubuntu/Ubuntu-based) [user] $ sudo pacman -S base-devel # for pacman (Arch) [user] $ sudo dnf install gcc-c++ # for dnf (Red Hat/Fedora) [user] $ sudo xbps-install base-devel # for xbps (Void) ... [user] $ g++ --version # To verify the installation. </syntaxhighlight>You can now compile C++ code. <references /> [[Category:Programming Languages]] 1e919df58e41b853e37d093da9edc63163ce72b8 3197 3195 2025-08-03T04:35:58Z Madonuko 140 tidy up formats wikitext text/x-wiki [[Category:Programming Languages]] {{Work In Progress}} '''C++''' is a high-level multi-use programming language built on top of the C programming Language to add Object-Oriented Programming features.<ref>Bjarne Stroustrup, The University of Edinburgh - The Essence of C++: https://www.youtube.com/watch?v=86xWVb4XIyE</ref> Originally developed by Bjarne Stroustrup in 1985, from its inception, C++ was designed with key principles in mind: '''efficient resource usage, high performance, and exceptional flexibility'''.<ref>Bjarne Stroustrup - The C++ Programming Language:https://archive.org/details/cprogramminglang00stro_0</ref> By the release of C++98 in 1997, the language had evolved significantly, incorporating advanced features like '''functional programming capabilities and enhanced low-level memory manipulation'''. These additions greatly expanded its utility, making it a foundational language for developing major operating systems like '''Linux and Windows''', as well as various microcomputer applications.<ref>Bjarne Stroustrup, C++ Applications: https://www.stroustrup.com/applications.html (Accessed 8/2/2025)</ref> Today, C++ is a wide-spread language, found in a vast array of applications. It powers everything from desktop applications and high-performance video games to robust server systems and precision-critical software. Its versatility has made it a common choice for demanding computing tasks.<ref>ISO/IEC 14882:2024: https://www.iso.org/standard/83626.html</ref> C++ is predominantly used as a '''compiled language''', meaning its source code is translated into machine-readable instructions before execution. Numerous companies and vendors offer C++ compilers. Notable examples include <code>g++</code> from the [[wikipedia:GNU Compiler Collection|GNU Compiler Collection]] and <code>clang++</code> from [[LLVM]], along with compilers distributed by major tech players like '''Microsoft, Intel, and IBM'''.<ref>Wikipedia, Category: C++ Compilers https://en.wikipedia.org/wiki/Category:C%2B%2B_compilers (Accessed 8/2/2025)</ref> Despite its widespread adoption, powerful functionality, and flexibility, C++ does face criticism within the programming community. Prominent figures, such as [[Linus Torvalds]], the creator of the Linux Kernel<ref>Linus Torvalds, LWN.net, Re: [RFC] Convert builin-mailinfo.c to use The Better String Library.: https://lwn.net/Articles/249460/ (Accessed 8/2/2025)</ref>, have voiced concerns about certain aspects of the language, among other notable voices. Since 2012, C++ has followed a predictable '''three-year release schedule''' for new versions of its standard. Currently, the active standard is '''C++23''', and the next anticipated release, following this established pattern, will be '''C++26'''. This consistent release cycle allows developers and compiler implementers to plan for upcoming features and changes.<ref>Rohit Sharma, C++: Where It's Heading and It's New Features: https://dzone.com/articles/c-where-is-it-heading-and-what-are-the-new-feature (Accessed 8/2/2025)</ref> = Compatibility = With different vendors producing different compilers, there is bound to be some incompatibility. Yet C++ standards committee members have overall decided it was best that the implementation of fixes for a couple of common problems found in many compilers to be solved by the compiler without having a "standardized" way of doing so. It should also be noted that C++ is not just a version of C with more features. In other words, valid C code might not exactly be valid in C++. Many common examples include OOP features such as classes. The term <code>class</code> in C++ can be used as a variable name in a C program.<ref>Itanium C++ ABI: https://itanium-cxx-abi.github.io/cxx-abi/ (Accessed 8/2/2025)</ref> = Installation = {{Guide Warning}} To install support for the C++ Language, ensure you have a viable compiler, it is likely you already have a compiler on a Linux System, to check, you can run:<syntaxhighlight lang="shell-session"> [user] $ g++ --version g++ (GCC) 15.1.1 20250425 Copyright (C) 2025 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</syntaxhighlight> If you do not have a compiler, you can install one using your distributions package manager OR you can directly download it from source, these commands will download the GCC-Suite (aka, gcc, g++, etc).<syntaxhighlight lang="shell-session"> [user] $ sudo apt install build-essential # for apt (Ubuntu/Ubuntu-based) [user] $ sudo pacman -S base-devel # for pacman (Arch) [user] $ sudo dnf install gcc-c++ # for dnf (Red Hat/Fedora) [user] $ sudo xbps-install base-devel # for xbps (Void) ... [user] $ g++ --version # To verify the installation. </syntaxhighlight> f4e911801fdecfabd61359b71471740bd3a69f34 3199 3197 2025-08-03T05:01:23Z Madonuko 140 [[Template:SoftwareInfobox]] wikitext text/x-wiki [[Category:Programming Languages]] {{Work In Progress}} {{SoftwareInfobox | image = [[File:C++ Hello World.png|frameless]] | caption = The Hello World program in C++, compiled with [[clang++]] | title = C++ | releasestatus = Maintained | lastrelease = C++23 | languages = C++ | developers = Standard C++ Foundation | website = https://isocpp.org/ }} '''C++''' is a high-level multi-use programming language built on top of the C programming Language to add Object-Oriented Programming features.<ref>Bjarne Stroustrup, The University of Edinburgh - The Essence of C++: https://www.youtube.com/watch?v=86xWVb4XIyE</ref> Originally developed by Bjarne Stroustrup in 1985, from its inception, C++ was designed with key principles in mind: '''efficient resource usage, high performance, and exceptional flexibility'''.<ref>Bjarne Stroustrup - The C++ Programming Language:https://archive.org/details/cprogramminglang00stro_0</ref> By the release of C++98 in 1997, the language had evolved significantly, incorporating advanced features like '''functional programming capabilities and enhanced low-level memory manipulation'''. These additions greatly expanded its utility, making it a foundational language for developing major operating systems like '''Linux and Windows''', as well as various microcomputer applications.<ref>Bjarne Stroustrup, C++ Applications: https://www.stroustrup.com/applications.html (Accessed 8/2/2025)</ref> Today, C++ is a wide-spread language, found in a vast array of applications. It powers everything from desktop applications and high-performance video games to robust server systems and precision-critical software. Its versatility has made it a common choice for demanding computing tasks.<ref>ISO/IEC 14882:2024: https://www.iso.org/standard/83626.html</ref> C++ is predominantly used as a '''compiled language''', meaning its source code is translated into machine-readable instructions before execution. Numerous companies and vendors offer C++ compilers. Notable examples include <code>g++</code> from the [[wikipedia:GNU Compiler Collection|GNU Compiler Collection]] and <code>clang++</code> from [[LLVM]], along with compilers distributed by major tech players like '''Microsoft, Intel, and IBM'''.<ref>Wikipedia, Category: C++ Compilers https://en.wikipedia.org/wiki/Category:C%2B%2B_compilers (Accessed 8/2/2025)</ref> Despite its widespread adoption, powerful functionality, and flexibility, C++ does face criticism within the programming community. Prominent figures, such as [[Linus Torvalds]], the creator of the Linux Kernel<ref>Linus Torvalds, LWN.net, Re: [RFC] Convert builin-mailinfo.c to use The Better String Library.: https://lwn.net/Articles/249460/ (Accessed 8/2/2025)</ref>, have voiced concerns about certain aspects of the language, among other notable voices. Since 2012, C++ has followed a predictable '''three-year release schedule''' for new versions of its standard. Currently, the active standard is '''C++23''', and the next anticipated release, following this established pattern, will be '''C++26'''. This consistent release cycle allows developers and compiler implementers to plan for upcoming features and changes.<ref>Rohit Sharma, C++: Where It's Heading and It's New Features: https://dzone.com/articles/c-where-is-it-heading-and-what-are-the-new-feature (Accessed 8/2/2025)</ref> = Compatibility = With different vendors producing different compilers, there is bound to be some incompatibility. Yet C++ standards committee members have overall decided it was best that the implementation of fixes for a couple of common problems found in many compilers to be solved by the compiler without having a "standardized" way of doing so. It should also be noted that C++ is not just a version of C with more features. In other words, valid C code might not exactly be valid in C++. Many common examples include OOP features such as classes. The term <code>class</code> in C++ can be used as a variable name in a C program.<ref>Itanium C++ ABI: https://itanium-cxx-abi.github.io/cxx-abi/ (Accessed 8/2/2025)</ref> = Installation = {{Guide Warning}} To install support for the C++ Language, ensure you have a viable compiler, it is likely you already have a compiler on a Linux System, to check, you can run:<syntaxhighlight lang="shell-session"> [user] $ g++ --version g++ (GCC) 15.1.1 20250425 Copyright (C) 2025 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</syntaxhighlight> If you do not have a compiler, you can install one using your distributions package manager OR you can directly download it from source, these commands will download the GCC-Suite (aka, gcc, g++, etc).<syntaxhighlight lang="shell-session"> [user] $ sudo apt install build-essential # for apt (Ubuntu/Ubuntu-based) [user] $ sudo pacman -S base-devel # for pacman (Arch) [user] $ sudo dnf install gcc-c++ # for dnf (Red Hat/Fedora) [user] $ sudo xbps-install base-devel # for xbps (Void) ... [user] $ g++ --version # To verify the installation. </syntaxhighlight> 43c9337368925e94efe92a2732fda411b50a7afd 3205 3199 2025-08-03T06:21:10Z Madonuko 140 fix headings wikitext text/x-wiki [[Category:Programming Languages]] {{Work In Progress}} {{SoftwareInfobox | image = [[File:C++ Hello World.png|frameless]] | caption = The Hello World program in C++, compiled with [[clang++]] | title = C++ | releasestatus = Maintained | lastrelease = C++23 | languages = C++ | developers = Standard C++ Foundation | website = https://isocpp.org/ }} '''C++''' is a high-level multi-use programming language built on top of the C programming Language to add Object-Oriented Programming features.<ref>Bjarne Stroustrup, The University of Edinburgh - The Essence of C++: https://www.youtube.com/watch?v=86xWVb4XIyE</ref> Originally developed by Bjarne Stroustrup in 1985, from its inception, C++ was designed with key principles in mind: '''efficient resource usage, high performance, and exceptional flexibility'''.<ref>Bjarne Stroustrup - The C++ Programming Language:https://archive.org/details/cprogramminglang00stro_0</ref> By the release of C++98 in 1997, the language had evolved significantly, incorporating advanced features like '''functional programming capabilities and enhanced low-level memory manipulation'''. These additions greatly expanded its utility, making it a foundational language for developing major operating systems like '''Linux and Windows''', as well as various microcomputer applications.<ref>Bjarne Stroustrup, C++ Applications: https://www.stroustrup.com/applications.html (Accessed 8/2/2025)</ref> Today, C++ is a wide-spread language, found in a vast array of applications. It powers everything from desktop applications and high-performance video games to robust server systems and precision-critical software. Its versatility has made it a common choice for demanding computing tasks.<ref>ISO/IEC 14882:2024: https://www.iso.org/standard/83626.html</ref> C++ is predominantly used as a '''compiled language''', meaning its source code is translated into machine-readable instructions before execution. Numerous companies and vendors offer C++ compilers. Notable examples include <code>g++</code> from the [[wikipedia:GNU Compiler Collection|GNU Compiler Collection]] and <code>clang++</code> from [[LLVM]], along with compilers distributed by major tech players like '''Microsoft, Intel, and IBM'''.<ref>Wikipedia, Category: C++ Compilers https://en.wikipedia.org/wiki/Category:C%2B%2B_compilers (Accessed 8/2/2025)</ref> Despite its widespread adoption, powerful functionality, and flexibility, C++ does face criticism within the programming community. Prominent figures, such as [[Linus Torvalds]], the creator of the Linux Kernel<ref>Linus Torvalds, LWN.net, Re: [RFC] Convert builin-mailinfo.c to use The Better String Library.: https://lwn.net/Articles/249460/ (Accessed 8/2/2025)</ref>, have voiced concerns about certain aspects of the language, among other notable voices. Since 2012, C++ has followed a predictable '''three-year release schedule''' for new versions of its standard. Currently, the active standard is '''C++23''', and the next anticipated release, following this established pattern, will be '''C++26'''. This consistent release cycle allows developers and compiler implementers to plan for upcoming features and changes.<ref>Rohit Sharma, C++: Where It's Heading and It's New Features: https://dzone.com/articles/c-where-is-it-heading-and-what-are-the-new-feature (Accessed 8/2/2025)</ref> == Compatibility == With different vendors producing different compilers, there is bound to be some incompatibility. Yet C++ standards committee members have overall decided it was best that the implementation of fixes for a couple of common problems found in many compilers to be solved by the compiler without having a "standardized" way of doing so. It should also be noted that C++ is not just a version of C with more features. In other words, valid C code might not exactly be valid in C++. Many common examples include OOP features such as classes. The term <code>class</code> in C++ can be used as a variable name in a C program.<ref>Itanium C++ ABI: https://itanium-cxx-abi.github.io/cxx-abi/ (Accessed 8/2/2025)</ref> == Installation == {{Guide Warning}} To install support for the C++ Language, ensure you have a viable compiler, it is likely you already have a compiler on a Linux System, to check, you can run:<syntaxhighlight lang="shell-session"> [user] $ g++ --version g++ (GCC) 15.1.1 20250425 Copyright (C) 2025 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</syntaxhighlight> If you do not have a compiler, you can install one using your distributions package manager OR you can directly download it from source, these commands will download the GCC-Suite (aka, gcc, g++, etc).<syntaxhighlight lang="shell-session"> [user] $ sudo apt install build-essential # for apt (Ubuntu/Ubuntu-based) [user] $ sudo pacman -S base-devel # for pacman (Arch) [user] $ sudo dnf install gcc-c++ # for dnf (Red Hat/Fedora) [user] $ sudo xbps-install base-devel # for xbps (Void) ... [user] $ g++ --version # To verify the installation. </syntaxhighlight> == References == 6c2c6d1acc912edb6c696ea08ab68a46717e0a56 0 2 3196 3143 2025-08-03T04:06:17Z Zorzem 208 Fixed incorrect information about arch linux coming with desktop environments by default wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch Linux Base Neofetch output.png|thumb|[[neofetch]] on Arch Linux]] '''Arch Linux''' is an independent rolling release [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. Arch Linux is kept up-to-date by regularly updating the packages of the system. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Installation === Arch Linux is generally installed through following the [https://wiki.archlinux.org/title/Installation_guide Installation Guide], and reading the [https://wiki.archlinux.org Arch Wiki]. The default Arch Linux ISO image is provided with archinstall, an installation script. ==== Arch Installation Script ==== This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] 3d4684744482f7ca3908ebe2e36203a7f8289f06 3207 3196 2025-08-03T12:03:24Z Imnotgoodatnames 121 replaced Neofetch screenshot with poorly done censorship with another one wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch_Linux_Minimal_Neofetch_Output.png|thumb|[[Neofetch]] on Arch Linux]] '''Arch Linux''' is an independent rolling release [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. Arch Linux is kept up-to-date by regularly updating the packages of the system. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Installation === Arch Linux is generally installed through following the [https://wiki.archlinux.org/title/Installation_guide Installation Guide], and reading the [https://wiki.archlinux.org Arch Wiki]. The default Arch Linux ISO image is provided with archinstall, an installation script. ==== Arch Installation Script ==== This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] 333c05640454bb225827cec7f5441fb16a622c9f 6 789 3198 2025-08-03T04:42:56Z Madonuko 140 wikitext text/x-wiki == Licensing == {{CC0}} 3f16ad18d78614720e9f206e6115a53bd34db67d 0 790 3200 2025-08-03T05:18:59Z Average USA patriot 204 Created page with "'''Red Star OS''' is a Red Hat Enterprise Linux based Distro Developed by the Democratic People's Republic of Korea (DPRK), made as a replacment for Windows in North Korea. it was frist developed in 1998 by the Korea Computer Center." wikitext text/x-wiki '''Red Star OS''' is a Red Hat Enterprise Linux based Distro Developed by the Democratic People's Republic of Korea (DPRK), made as a replacment for Windows in North Korea. it was frist developed in 1998 by the Korea Computer Center. ef41b945c58a6a91940d342ee5b41e5c03f5eb60 3201 3200 2025-08-03T05:19:33Z Average USA patriot 204 wikitext text/x-wiki '''Red Star OS''' is a Red Hat Enterprise Linux based Distro Developed in the Democratic People's Republic of Korea (DPRK), made as a replacment for Windows in North Korea. it was frist developed in 1998 by the Korea Computer Center. 76b98da74e564eedd8e2e73c637e08475808e6bb 3202 3201 2025-08-03T05:35:28Z Average USA patriot 204 wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = Red Star OS | image = [[File:Red Star OS Logo 2020.svg|190px]] | caption = Red Star OS logo | releasestatus = Maintained | releasemodel = Unknown | packagemanager = [[RPM]] | defaultdesktops = Unknown | usagetype = Desktop | architectures = [[IA-32]], [[x86-64]], [[ARM]] | website = None }} '''Red Star OS''' is a Red Hat Enterprise Linux based Distro Developed in the Democratic People's Republic of Korea (DPRK), made as a replacment for Windows in North Korea. it was frist developed in 1998 by the Korea Computer Center. 60d38be90c8dd160589eb6629ef3720c5be4b82a 3206 3202 2025-08-03T08:58:41Z Average USA patriot 204 wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = Red Star OS | image = [[File:Red Star OS Logo 2020.svg|190px]] | caption = Red Star OS logo | releasestatus = Maintained | releasemodel = Unknown | packagemanager = [[rpm]] | defaultdesktops = Unknown | usagetype = Desktop | architectures = [[IA-32]], [[x86-64]], [[ARM]] | website = None }} '''Red Star OS''' is a Red Hat Enterprise Linux based Distro Developed in the Democratic People's Republic of Korea (DPRK), made as a replacment for Windows in North Korea. it was frist developed in 1998 by the Korea Computer Center. 0c77796d4e6becd6b63e4246a0e2721d22aa7c00 3230 3206 2025-08-04T07:54:41Z Average USA patriot 204 wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = Red Star OS | image = [[File:Red Star OS Logo 2020.svg|190px]] | caption = Red Star OS logo | releasestatus = Maintained | releasemodel = Unknown | packagemanager = [[rpm]] | defaultdesktops = Unknown | usagetype = Desktop | architectures = [[IA-32]], [[x86-64]], [[ARM]] | website = None }} '''Red Star OS''' is a Red Hat Linux based Distro Developed in the Democratic People's Republic of Korea (DPRK), made as a replacment for Windows in North Korea. it was frist developed in 1998 by the Korea Computer Center. c4125908d38aa1d0cc352545bd3da07f644d26ab 0 279 3204 2710 2025-08-03T05:47:22Z Hailey 209 Add information about openSUSE slowroll wikitext text/x-wiki {{Needs_Citations}} == Introduction == {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, ppc64, x86_64 | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. ==== Versions ==== This distribution stands out by having two primary variations of the distribution: OpenSUSE Tumbleweed is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. OpenSUSE Leap is the point release version, with a new release every year with older and more stable packages meant for business use. ===== openSUSE Slowroll ===== Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. [[Category:Linux Distributions]] b0c1097824647bc07fdeadb34e572aeb11aea608 0 602 3208 2160 2025-08-03T13:41:29Z Wilbur 142 fix link to wayland compositors and grammar wikitext text/x-wiki {{Work In Progress}} == Disambiguation Page == This page will serve as a disambiguation page between [[Wayland Compositors]] ([[:Category:Wayland Compositors|Category]]) and [[X Window Manager|X Window Manager's]] ([[:Category:X Window Managers|Category]]). [[Category:Window Management Systems]] 5da423f4e490a855af38f1eaade4a184423488d6 0 791 3209 2025-08-03T16:21:54Z Atmois 13 Add redirect to category page wikitext text/x-wiki #REDIRECT [[:Category:Programming Languages]] de594450526f31fcc297f1b3624007cd7cc6196e 0 772 3210 3161 2025-08-03T17:28:16Z Elia73333 213 added an actual description. wikitext text/x-wiki {{Python|Designed by=Guido van Rossum (31 January 1956 - 69 Years old)|Developers=Python Software Foundation|First Version=20 February 1991 - v0.9.0|Last Version=11 June 2025 - 3.13.5|Extensions=.py, .pyw, .pyz, .pyi, .pyc, .pyd|License=[https://docs.python.org/3/license.html](Python Software Foundation License)|website=[https://python.org/]}}Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s as a successor to the ABC programming language. He released the first version (0.9.0) in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020 and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python. Python is currently the most used programming language (according to https://www.tiobe.com/tiobe-index/). Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as Discord.py (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers Visual Studio Code because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. 0c96748f4789f7b5aa93369ca91edf7c72062e73 3211 3210 2025-08-03T18:06:25Z Elia73333 213 added installation guides wikitext text/x-wiki {{Python|Designed by=Guido van Rossum (31 January 1956 - 69 Years old)|Developers=Python Software Foundation|First Version=20 February 1991 - v0.9.0|Last Version=11 June 2025 - 3.13.5|Extensions=.py, .pyw, .pyz, .pyi, .pyc, .pyd|License=[https://docs.python.org/3/license.html](Python Software Foundation License)|website=[https://python.org/]}}Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s as a successor to the ABC programming language. He released the first version (0.9.0) in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020 and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python. Python is currently the most used programming language (according to https://www.tiobe.com/tiobe-index/). Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as Discord.py (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers Visual Studio Code because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> 76a5efdb2a1e4a27237b0ddaacbdbd23f61a685d 3212 3211 2025-08-03T18:09:57Z Elia73333 213 wikitext text/x-wiki Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s as a successor to the ABC programming language. He released the first version (0.9.0) in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020 and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python. Python is currently the most used programming language (according to https://www.tiobe.com/tiobe-index/). Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as Discord.py (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers Visual Studio Code because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> 935bc7be72fd5e0202c5c9bfc205b303bee65cd4 3213 3212 2025-08-03T18:14:38Z Elia73333 213 wikitext text/x-wiki Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s as a successor to the ABC programming language. He released the first version (0.9.0) in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020 and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python. Python is currently the most used programming language (according to https://www.tiobe.com/tiobe-index/). Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as Discord.py (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers Visual Studio Code because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> [[Category:Programming Languages]] 4f30ccf468a4e88651e77e04c2b1046bb1508142 3224 3213 2025-08-03T20:20:30Z Elia73333 213 Added softwareinfobox, citations wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Pythoon | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref>as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language<ref>https://www.tiobe.com/tiobe-index/</ref>. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as Discord.py<ref>https://discordpy.readthedocs.io/</ref> (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers Visual Studio Code<ref>https://code.visualstudio.com/</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> = References (To be finished) = <references /> [[Category:Programming Languages]] f17e2e74d50c060a9829bbad143167bffb7e7d79 3229 3224 2025-08-04T07:33:24Z Elia73333 213 Fixed hyperlinks and citations wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Pythoon | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref>as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language<ref>https://www.tiobe.com/tiobe-index/</ref>. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers[https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> = References (To be finished) = <references /> [[Category:Programming Languages]] 70b9001b0f3ba45f389218f86f7d0b1101b65471 3236 3229 2025-08-04T09:54:10Z Elia73333 213 Specified the "most used programming language" section wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Pythoon | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref>as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purposes softwares. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers[https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> = References (To be finished) = <references /> [[Category:Programming Languages]] 8daa4906ac7d256f23d64a0551af90b34e362eb2 3237 3236 2025-08-04T10:01:30Z Readyready15728 186 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref>as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purposes softwares. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers[https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> = References (To be finished) = <references /> [[Category:Programming Languages]] ba3680a93f8c3f6879a3937793b5fba39a574581 3239 3237 2025-08-04T10:23:34Z Elia73333 213 added pip infos wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref>as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purposes softwares. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = PIP (Package Manager) = [https://pypi.org/project/pip/ PIP] is Python's Package Manager, through PIP you can install all the libraries needed for your project to run. PIP stands for "''PIP Installed Packages"'' or "''PIP Installs Packages"''<ref>https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for</ref>. PIP connects to an online software repository (PyPI). PIP was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain PIP and VirtualEnv. = Installing packages with PIP = [user@hostname ~]$ <code>pip install package-name</code> = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y</syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight>[user@hostname ~]$ sudo yum install python3 python3-pip -y</syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> == Installation for PIP == Python 3.4+ included PIP by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash">[user@hostname ~]$ python -m ensurepip --upgrade</syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script, from <nowiki>https://bootstrap.pypa.io/get-pip.py</nowiki>. # Open a new terminal, cd to the folder containing containing the file # Run: <syntaxhighlight lang="bash"> [user@hostname ~]$ python get-pip.py </syntaxhighlight> = References = <references /> [[Category:Programming Languages]] 7076b148be467e1354dee4cb452883e2dee6d6a4 0 792 3214 2025-08-03T18:34:40Z Ok 425 Create initial article for Assembly Languages wikitext text/x-wiki An '''assembly''' language is a low-level machine language that uses symbolic instructions rather than raw binary coding to communicate directly with a computer's hardware, making it easier for humans to read. Unlike high-level programming languages that tend to restrict direct access to your system, an '''assembly''' language offers direct access to the system's architecture, allowing full control over the system, processor, memory and other hardware components inside the system. Each '''assembly''' language is specific to an architecture, those include but are not limited to: x86, ARM or RISC-V. The language uses something called '''"mnemonics",''' which are short textual codes that represent specific machine code instructions. For example, instead of using 10110000, a programmer might write MOV AL, 0 to perform the same operation. An '''assembly''' language is very fast, but won't get you anywhere due to it's complexity and lack of features. One might be more interested to look into something like [[C]] or [[C++]] for that kind of fast, optimized language. 4d4d05642d2336f1c592203656dbdb6e95af2484 3232 3214 2025-08-04T08:34:37Z Ok 425 Upload image for the assembly code used for the Motorola MC6800 wikitext text/x-wiki [[File:Motorola 6800 Assembly Language.png|thumb|Assembly code for the [[wikipedia:MC6800|Motorola MC6800]]]] An '''assembly''' language is a low-level machine language that uses symbolic instructions rather than raw binary coding to communicate directly with a computer's hardware, making it easier for humans to read. Unlike high-level programming languages that tend to restrict direct access to your system, an '''assembly''' language offers direct access to the system's architecture, allowing full control over the system, processor, memory and other hardware components inside the system. Each '''assembly''' language is specific to an architecture, those include but are not limited to: x86, ARM or RISC-V. The language uses something called '''"mnemonics",''' which are short textual codes that represent specific machine code instructions. For example, instead of using 10110000, a programmer might write MOV AL, 0 to perform the same operation. An '''assembly''' language is very fast, but won't get you anywhere due to it's complexity and lack of features. One might be more interested to look into something like [[C]] or [[C++]] for that kind of fast, optimized language. 9104b44085535d1f41905a41df55deb519c29c6b 3235 3232 2025-08-04T09:53:59Z Ok 425 Added category wikitext text/x-wiki [[File:Motorola 6800 Assembly Language.png|thumb|Assembly code for the [[wikipedia:MC6800|Motorola MC6800]]]] An '''assembly''' language is a low-level machine language that uses symbolic instructions rather than raw binary coding to communicate directly with a computer's hardware, making it easier for humans to read. Unlike high-level programming languages that tend to restrict direct access to your system, an '''assembly''' language offers direct access to the system's architecture, allowing full control over the system, processor, memory and other hardware components inside the system. Each '''assembly''' language is specific to an architecture, those include but are not limited to: x86, ARM or RISC-V. The language uses something called '''"mnemonics",''' which are short textual codes that represent specific machine code instructions. For example, instead of using 10110000, a programmer might write MOV AL, 0 to perform the same operation. An '''assembly''' language is very fast, but won't get you anywhere due to it's complexity and lack of features. One might be more interested to look into something like [[C]] or [[C++]] for that kind of fast, optimized language. [[Category:Programming Languages]] 05d933c4f3a8a2e88d2d698f8fbe6f1e27bfa44b 0 203 3216 2417 2025-08-03T18:45:00Z Ok 425 Bold Gentoo mentions, add hyperlink to Daniel Robbins, and include external source link. wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === * Complete system customization through source compilation * Choice between OpenRC and systemd init systems * Extensive hardware architecture support * Rolling release model with stable branch option * Minimal base system requirements * Advanced package management through Portage == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The process involves: * Preparing the installation environment * Partitioning and formatting storage * Configuring and compiling the kernel * Setting up the bootloader * Installing and configuring base system packages For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through: * CPU-specific optimizations * Custom compile flags * USE flag combinations * Kernel configuration * Package-specific settings === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers: * Pre-compiled package options * Binary package creation * Distribution of binary packages * Mixed source/binary environments == Security == '''Gentoo''' implements several security measures: * [https://wiki.gentoo.org/wiki/SELinux SELinux support] * [https://wiki.gentoo.org/wiki/Hardened_Gentoo Hardened profiles] * Regular security updates * Signed package verification * [https://wiki.gentoo.org/wiki/Kernel Kernel hardening options] == Community and Development == === Community Resources === * [https://forums.gentoo.org/ Official Forums] * IRC channels * Mailing lists * Wiki documentation * Bug tracking system === Development Model === * Open source development * Community-driven package maintenance * Regular security updates * Active development team * Public Git repositories == Comparison with Other Distributions == === Advantages === * Maximum customization potential * Optimal performance through compilation * Complete control over features * Extensive documentation * Active community support === Considerations === * Longer installation time * Higher learning curve * Requires technical knowledge * Resource-intensive compilation * Regular maintenance needed == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" comes from the fast-swimming Gentoo penguin * View Larry by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 793bb58fa57a8053eea719d2f8bcc3597d4688b0 3228 3216 2025-08-04T07:05:03Z Ok 425 wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === * Complete system customization through source compilation * Choice between OpenRC and Systemd init systems * Extensive hardware architecture support * Rolling release model with stable branch option * Minimal base system requirements * Advanced package management through Portage * Allows storing multiple versions of the same package on the system == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The process involves: * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Media Preparing the installation environment] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Networking Configuring the network] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks Partitioning and formatting storage] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Stage Installing the stage file] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base Installing the base system] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel Configuring the kernel] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/System Configuring the system] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Tools Installing system tools] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader Setting up the bootloader] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Finalizing Creating the user account] For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through: * CPU-specific optimizations * Custom compile flags * USE flag combinations * Kernel configuration * Package-specific settings === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers: * Pre-compiled package options * Binary package creation * Distribution of binary packages * Mixed source/binary environments == Security == '''Gentoo''' implements several security measures: * [https://wiki.gentoo.org/wiki/SELinux SELinux support] * [https://wiki.gentoo.org/wiki/Hardened_Gentoo Hardened profiles] * Regular security updates * Signed package verification * [https://wiki.gentoo.org/wiki/Kernel Kernel hardening options] == Community and Development == === Community Resources === * [https://forums.gentoo.org/ Official Forums] * IRC channels * Mailing lists * Wiki documentation * [https://bugs.gentoo.org/ Bug tracking system] === Development Model === * Open source development * Community-driven package maintenance * Regular security updates * Active development team * Public Git repositories == Comparison with Other Distributions == === Advantages === * Maximum customization potential * Optimal performance through compilation * Complete control over features * Extensive documentation * Active community support === Considerations === * Longer installation time * Higher learning curve * Requires technical knowledge * Resource-intensive compilation * Regular maintenance needed == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" comes from the fast-swimming Gentoo penguin * View Larry by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] bdd5cfb5d7a53359f77c6fe04c50618e9a52142e 3231 3228 2025-08-04T08:29:21Z Ok 425 Added more documentation in various places. wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === * Complete system customization through source compilation * Choice between OpenRC and Systemd init systems * Extensive hardware architecture support * Rolling release model with stable branch option * Minimal base system requirements * Advanced package management through Portage * Allows storing multiple versions of the same package on the system == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The process involves: * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Media Preparing the installation environment] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Networking Configuring the network] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks Partitioning and formatting storage] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Stage Installing the stage file] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base Installing the base system] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel Configuring the kernel] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/System Configuring the system] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Tools Installing system tools] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader Setting up the bootloader] * [https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Finalizing Creating the user account] For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |- |<code>emerge --unmerge package</code> |Remove a package and its dependencies |- |<code>emerge --depclean</code> |Remove unused dependencies |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through: * CPU-specific optimizations * Custom compile flags * USE flag combinations * Kernel configuration * Package-specific settings === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers: * Pre-compiled package options * Binary package creation * Distribution of binary packages * Mixed source/binary environments == Security == '''Gentoo''' implements several security measures: * [https://wiki.gentoo.org/wiki/SELinux SELinux support] * [https://wiki.gentoo.org/wiki/Hardened_Gentoo Hardened profiles] * Regular security updates * Signed package verification * [https://wiki.gentoo.org/wiki/Kernel Kernel hardening options] == Community and Development == === Community Resources === * [https://forums.gentoo.org/ Official Forums] * IRC channels * Mailing lists * Wiki documentation * [https://bugs.gentoo.org/ Bug tracking system] === Development Model === * Open source development * Community-driven package maintenance * Regular security updates * Active development team * Public Git repositories == Comparison with Other Distributions == === Advantages === * Maximum customization potential * Optimal performance through compilation * Complete control over features * Extensive documentation * Active community support * Ability to fetch binary packages in heavier packages === Considerations === * Longer installation time * Higher learning curve * Requires technical knowledge * Resource-intensive compilation * Regular maintenance needed == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 0617a4dc21962591999771070f932df16aec9863 6 797 3223 2025-08-03T20:15:19Z Elia73333 213 wikitext text/x-wiki == Licensing == {{GPL}} 6b26f5cce63faf4ce1130ffc4f5c42cf3e3a00ac 10 798 3226 2025-08-04T00:54:17Z Ow0cast 249 tmpl | call to action for issue templates wikitext text/x-wiki You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} {{{action|editing}}}]</span> it. <noinclude> <templatedata> { "params": { "action": { "label": "Link Text", "description": "Text to use for the edit link", "type": "string", "suggested": true, "default": "editing" } }, "description": "Provides a call to action to edit the page to solve an issue", "format": "inline" } </templatedata> </noinclude> d20e171ea54f90af3214c149a5e87763daab34b4 10 799 3227 2025-08-04T01:01:21Z Ow0cast 249 tmpl | create stub issue template wikitext text/x-wiki {{#invoke:mbox|mbox | icon = OOjs UI icon alert.svg | title = This page is a stub. {{AssistByEditing|action=expanding}} | text = This message means that this page has been deemed not long enough to provide meaningful coverage of its topic. | extraclasses = mbox-med notice-stub }} <includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]] }} </includeonly> <noinclude> <templatedata> { "params": {}, "description": "Adds a notice that the page may be too short with a call to action to expand it" } </templatedata> </noinclude> 72dd7f8dafa64b6c75ae3fd18abfbf064e3ed2ff 6 800 3233 2025-08-04T08:53:24Z Ok 425 wikitext text/x-wiki Larry after he grew his black and white patches feb9124bc94408ea6acd08db20f406fdb77dfd65 0 202 3234 2970 2025-08-04T08:58:06Z Ok 425 Fixed code blocks, added Larry image. wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow Gentoo Wiki, 2023 (Imported 4th June 2024)</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html Gentoo Forums, 2003 (imported 4th June 2024)</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727 Gentoo Bug Report, 2003 (imported 4th June 2024)</ref> * Larry can be found in [[emerge]] by running <code>emerge --moo</code> Larry can also be found in [[Dpkg|apt]] by running <code>apt moo</code> . * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry</ref> [[File:Larry The Cow with Gentoo Logo.png|thumb|Larry after he grew his black and white patches]] == References == <references /> [[Category:Mascots]] 97e0aeef73d02444b9ed13acf7d668511564e38d 6 801 3238 2025-08-04T10:07:13Z Ok 425 wikitext text/x-wiki CRUX b5c126ceb8a07eaab403876d39b6c0ea034a33c6 0 802 3241 2025-08-04T10:50:43Z Ok 425 Create initial article for pkgutils package manager wikitext text/x-wiki '''pkgutils''' is a set of utilities (pkgadd, pkgrm, pkginfo, pkgmk and rejmerge), which are used for managing software packages in Linux. It is developed for and used by the CRUX distribution <ref>http://crux.nu</ref> All the packages installed with '''pkgutils''' are plain <code>.tar.gz</code> files. == Usage == The following are several common usages of '''pkgutils'''. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pkgadd package1.pkg.tar.gz package2.pkg.tar.gz</code> {| class="wikitable" |+Common Pkgutils Commands !Command !Description |- |<code>pkgadd package.pkg.tar.gz</code> |Install a given package |- |<code>pkgrm package</code> |Remove a given package. |- |<code>ports -u</code> |Sync ports tree |- |<code>prt-get update</code> |Sync local index with the ports tree |- |<code>prt-get upgrade</code> |Rebuild and reinstalls newer versions of installed packages |- |<code>prt-get search package</code> |Search a given package |- |<code>pkginfo -i</code> |List all installed packages |- |<code>pkginfo package</code> |Display info about a given package |} == See Also == [https://crux.nu/Main/Handbook3-7-Package pkgutils - CRUX] [[Category:Package Manager]] 6dd7700666f4a4a65bf71ea669b772d85954d4eb 0 169 3242 3170 2025-08-04T10:56:39Z Ok 425 Added pkgutils inside the list of Package Managers. wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] [[Category:Terminology]] 95e75286c64c234e3c46f30d5c10ad10beb87b23 0 169 3243 3242 2025-08-04T10:58:38Z Ok 425 Fixed grammatical error found in the portage section wikitext text/x-wiki {{Needs_Citations}} == Introduction == [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained by the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] [[Category:Terminology]] 558e20707546a1f10370303a5ae9d4f5d734ffff 0 772 3244 3239 2025-08-04T11:15:30Z Ok 425 Added documentation for setting up venv in python. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref>as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purposes softwares. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = PIP (Package Manager) = [https://pypi.org/project/pip/ PIP] is Python's Package Manager, through PIP you can install all the libraries needed for your project to run. PIP stands for "''PIP Installed Packages"'' or "''PIP Installs Packages"''<ref>https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for</ref>. PIP connects to an online software repository (PyPI). PIP was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain PIP and VirtualEnv. = Installing packages with PIP = [user@hostname ~]$ <code>pip install package-name</code> = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y</syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight>[user@hostname ~]$ sudo yum install python3 python3-pip -y</syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> == Installation for PIP == Python 3.4+ included PIP by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash">[user@hostname ~]$ python -m ensurepip --upgrade</syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script, from <nowiki>https://bootstrap.pypa.io/get-pip.py</nowiki>. # Open a new terminal, cd to the folder containing containing the file # Run: <syntaxhighlight lang="bash">[user@hostname ~]$ python get-pip.py</syntaxhighlight> == '''Setup Python Venv''' == <syntaxhighlight lang="bash">[user@hostname ~]$ python -m venv path/to/venv/ [user@hostname ~]$ source path/to/venv/bin/activate</syntaxhighlight> = References = <references /> [[Category:Programming Languages]] 22bd1992be57361c004635565035532521efee47 3245 3244 2025-08-04T11:24:43Z Elia73333 213 venv descriptions wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref>as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purposes softwares. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = PIP (Package Manager) = [https://pypi.org/project/pip/ PIP] is Python's Package Manager, through PIP you can install all the libraries needed for your project to run. PIP stands for "''PIP Installed Packages"'' or "''PIP Installs Packages"''<ref>https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for</ref>. PIP connects to an online software repository (PyPI). PIP was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain PIP and VirtualEnv. = Virtual Environments (VENV) = The venv module allows users to create Virtual Environments each with their own independent modules and libraries, these may be useful if you want to isolate a certain project from the rest of your files, or for debugging. Venv got created by Ian Bicking (the same developer who created PIP) and is now maintained by the Python Package Authority (PyPA). = Installing packages with PIP = [user@hostname ~]$ <code>pip install package-name</code> = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y</syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight>[user@hostname ~]$ sudo yum install python3 python3-pip -y</syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> == Installation for PIP == Python 3.4+ included PIP by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash">[user@hostname ~]$ python -m ensurepip --upgrade</syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script, from <nowiki>https://bootstrap.pypa.io/get-pip.py</nowiki>. # Open a new terminal, cd to the folder containing containing the file # Run: <syntaxhighlight lang="bash">[user@hostname ~]$ python get-pip.py</syntaxhighlight> == '''Setup Python Venv''' == <syntaxhighlight lang="bash">[user@hostname ~]$ python -m venv path/to/venv/ [user@hostname ~]$ source path/to/venv/bin/activate</syntaxhighlight> = References = <references /> [[Category:Programming Languages]] 18233610eac5f663d6ef5db57dff83ad9eb816f0 3247 3245 2025-08-04T11:31:09Z Elia73333 213 fixes for: readability issues, sentence structuring, grammar errors, etc. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref> as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purpose software. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = pip (Package Manager) = [https://pypi.org/project/pip/ pip] is Python's Package Manager, through pip you can install all the libraries needed for your project to run. pip stands for "''pip Installs Packages"''<ref>https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for</ref>. pip connects to an online software repository (PyPI). pip was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain pip and VirtualEnv. = Virtual Environments (VENV) = The venv module allows users to create Virtual Environments each with their own independent modules and libraries, This is useful for isolating project dependencies or debugging.. Venv was created by Ian Bicking (the same developer who created pip) and is now maintained by the Python Package Authority (PyPA). = Installing packages with pip = [user@hostname ~]$ <code>pip install package-name</code> = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y</syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight>[user@hostname ~]$ sudo yum install python3 python3-pip -y</syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> == Installation for pip == Python 3.4+ included pip by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash">[user@hostname ~]$ python -m ensurepip --upgrade</syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script, from <nowiki>https://bootstrap.pypa.io/get-pip.py</nowiki>. # Open a new terminal, cd to the folder containing the file # Run: <syntaxhighlight lang="bash">[user@hostname ~]$ python get-pip.py</syntaxhighlight> == '''Setup Python Venv''' == <syntaxhighlight lang="bash">[user@hostname ~]$ python -m venv path/to/venv/ [user@hostname ~]$ source path/to/venv/bin/activate</syntaxhighlight> = References = <references /> [[Category:Programming Languages]] 083365c7848d8e0e82445352c55ccf4349487648 3248 3247 2025-08-04T11:47:15Z Readyready15728 186 /* Setup Python Venv */ wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref> as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purpose software. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = pip (Package Manager) = [https://pypi.org/project/pip/ pip] is Python's Package Manager, through pip you can install all the libraries needed for your project to run. pip stands for "''pip Installs Packages"''<ref>https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for</ref>. pip connects to an online software repository (PyPI). pip was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain pip and VirtualEnv. = Virtual Environments (VENV) = The venv module allows users to create Virtual Environments each with their own independent modules and libraries, This is useful for isolating project dependencies or debugging.. Venv was created by Ian Bicking (the same developer who created pip) and is now maintained by the Python Package Authority (PyPA). = Installing packages with pip = [user@hostname ~]$ <code>pip install package-name</code> = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y</syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight>[user@hostname ~]$ sudo yum install python3 python3-pip -y</syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> == Installation for pip == Python 3.4+ included pip by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash">[user@hostname ~]$ python -m ensurepip --upgrade</syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script, from <nowiki>https://bootstrap.pypa.io/get-pip.py</nowiki>. # Open a new terminal, cd to the folder containing the file # Run: <syntaxhighlight lang="bash">[user@hostname ~]$ python get-pip.py</syntaxhighlight> == '''Setup Python venv''' == When installing pip packages system-wide as root you will typically see a message like this one: <syntaxhighlight> ~ sudo pip install pyperclip Collecting pyperclip Downloading pyperclip-1.9.0.tar.gz (20 kB) Preparing metadata (setup.py) ... done Building wheels for collected packages: pyperclip Building wheel for pyperclip (setup.py) ... done Created wheel for pyperclip: filename=pyperclip-1.9.0-py3-none-any.whl size=11014 sha256=696d851be7b0d99fe8112ddf5c6ebc2b9444464b2a729911930d64bebc124c35 Stored in directory: /root/.cache/pip/wheels/cc/ae/36/ee17d1de094fcb61e24106cb329b5103861e819f94bef5e10a Successfully built pyperclip Installing collected packages: pyperclip Successfully installed pyperclip-1.9.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv </syntaxhighlight> Running pip as root can result in conflicted, broken packages and security risks.<ref>https://askubuntu.com/questions/802544/is-sudo-pip-install-still-a-broken-practice</ref> That is why the warning advises users to create venv environments for Python software projects. The invocation is simple. Here's what it should look like in bash: <syntaxhighlight lang="bash">[user@hostname ~]$ python -m venv path/to/venv/ [user@hostname ~]$ source path/to/venv/bin/activate</syntaxhighlight> If you are not using bash, things may change slightly. For example, a user of the fish shell would instead run <syntaxhighlight> source venv/bin/activate.fish </syntaxhighlight> You'll know that a venv is currently active from an altered prompt such as this one: <syntaxhighlight> (venv) user@hostname:~$ </syntaxhighlight> With a venv loaded, all pip commands such as "pip install" and "pip uninstall" will affect only that venv. All Python code run with the venv's installation of Python will prefer to import the venv's libraries over any system libraries. (The command "which python" can help ensure that it is truly the venv Python as opposed to, say, the system "/usr/bin/python" that is running.) Lastly, a user who wishes to turn off a venv for the time being will only need to give the command "deactivate" to the shell. = References = <references /> [[Category:Programming Languages]] 078c7bbaea32dfb960c81699c88aa2b627d9a43c 3249 3248 2025-08-04T11:49:06Z Readyready15728 186 /* Setup Python venv */ wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref> as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purpose software. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = pip (Package Manager) = [https://pypi.org/project/pip/ pip] is Python's Package Manager, through pip you can install all the libraries needed for your project to run. pip stands for "''pip Installs Packages"''<ref>https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for</ref>. pip connects to an online software repository (PyPI). pip was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain pip and VirtualEnv. = Virtual Environments (VENV) = The venv module allows users to create Virtual Environments each with their own independent modules and libraries, This is useful for isolating project dependencies or debugging.. Venv was created by Ian Bicking (the same developer who created pip) and is now maintained by the Python Package Authority (PyPA). = Installing packages with pip = [user@hostname ~]$ <code>pip install package-name</code> = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y</syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight>[user@hostname ~]$ sudo yum install python3 python3-pip -y</syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> == Installation for pip == Python 3.4+ included pip by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash">[user@hostname ~]$ python -m ensurepip --upgrade</syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script, from <nowiki>https://bootstrap.pypa.io/get-pip.py</nowiki>. # Open a new terminal, cd to the folder containing the file # Run: <syntaxhighlight lang="bash">[user@hostname ~]$ python get-pip.py</syntaxhighlight> == '''Setup Python venv''' == When installing pip packages system-wide as root you will typically see a message like this one: <syntaxhighlight> ~ sudo pip install pyperclip Collecting pyperclip Downloading pyperclip-1.9.0.tar.gz (20 kB) Preparing metadata (setup.py) ... done Building wheels for collected packages: pyperclip Building wheel for pyperclip (setup.py) ... done Created wheel for pyperclip: filename=pyperclip-1.9.0-py3-none-any.whl size=11014 sha256=696d851be7b0d99fe8112ddf5c6ebc2b9444464b2a729911930d64bebc124c35 Stored in directory: /root/.cache/pip/wheels/cc/ae/36/ee17d1de094fcb61e24106cb329b5103861e819f94bef5e10a Successfully built pyperclip Installing collected packages: pyperclip Successfully installed pyperclip-1.9.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv </syntaxhighlight> Running pip as root can result in conflicted, broken packages and security risks.<ref>https://askubuntu.com/questions/802544/is-sudo-pip-install-still-a-broken-practice</ref> That is why the warning advises users to create venv environments for Python software projects. The invocation is simple. Here's what it should look like in bash: <syntaxhighlight lang="bash">[user@hostname ~]$ python -m venv path/to/venv/ [user@hostname ~]$ source path/to/venv/bin/activate</syntaxhighlight> The first line creates the folder containing the venv and the second line activates it. If you are not using bash, things may change slightly. For example, a user of the fish shell would instead run <syntaxhighlight> source venv/bin/activate.fish </syntaxhighlight> You'll know that a venv is currently active from an altered prompt such as this one: <syntaxhighlight> (venv) user@hostname:~$ </syntaxhighlight> With a venv loaded, all pip commands such as "pip install" and "pip uninstall" will affect only that venv. All Python code run with the venv's installation of Python will prefer to import the venv's libraries over any system libraries. (The command "which python" can help ensure that it is truly the venv Python as opposed to, say, the system "/usr/bin/python" that is running.) Lastly, a user who wishes to turn off a venv for the time being will only need to give the command "deactivate" to the shell. = References = <references /> [[Category:Programming Languages]] c1ded90116de4232f8b42a414ab3efffcb6883d0 3250 3249 2025-08-04T13:18:35Z Readyready15728 186 /* Setup Python venv */ wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref> as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purpose software. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = pip (Package Manager) = [https://pypi.org/project/pip/ pip] is Python's Package Manager, through pip you can install all the libraries needed for your project to run. pip stands for "''pip Installs Packages"''<ref>https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for</ref>. pip connects to an online software repository (PyPI). pip was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain pip and VirtualEnv. = Virtual Environments (VENV) = The venv module allows users to create Virtual Environments each with their own independent modules and libraries, This is useful for isolating project dependencies or debugging.. Venv was created by Ian Bicking (the same developer who created pip) and is now maintained by the Python Package Authority (PyPA). = Installing packages with pip = [user@hostname ~]$ <code>pip install package-name</code> = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y</syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight>[user@hostname ~]$ sudo yum install python3 python3-pip -y</syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> == Installation for pip == Python 3.4+ included pip by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash">[user@hostname ~]$ python -m ensurepip --upgrade</syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script, from <nowiki>https://bootstrap.pypa.io/get-pip.py</nowiki>. # Open a new terminal, cd to the folder containing the file # Run: <syntaxhighlight lang="bash">[user@hostname ~]$ python get-pip.py</syntaxhighlight> == '''Setup Python venv''' == When installing pip packages system-wide as root you will typically see a message like this one: <syntaxhighlight> ~ sudo pip install pyperclip Collecting pyperclip Downloading pyperclip-1.9.0.tar.gz (20 kB) Preparing metadata (setup.py) ... done Building wheels for collected packages: pyperclip Building wheel for pyperclip (setup.py) ... done Created wheel for pyperclip: filename=pyperclip-1.9.0-py3-none-any.whl size=11014 sha256=696d851be7b0d99fe8112ddf5c6ebc2b9444464b2a729911930d64bebc124c35 Stored in directory: /root/.cache/pip/wheels/cc/ae/36/ee17d1de094fcb61e24106cb329b5103861e819f94bef5e10a Successfully built pyperclip Installing collected packages: pyperclip Successfully installed pyperclip-1.9.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv </syntaxhighlight> Running pip as root can result in conflicted, broken packages and security risks.<ref>https://askubuntu.com/questions/802544/is-sudo-pip-install-still-a-broken-practice</ref> There are two possible responses to this situation: * See whether your distribution offers a system package to suit your needs. Depending on the distribution, system packages may be outdated, but this option should be tried first unless you are actively developing software. For example, with the Python module pyperclip mentioned below, there was a system package available that could fill the need, python3-pyperclip. * Or, if you are writing your own software, you can heed the warning as written and use the following instructions: The invocation is simple. Here's what it should look like in bash: <syntaxhighlight lang="bash">[user@hostname ~]$ python -m venv path/to/venv/ [user@hostname ~]$ source path/to/venv/bin/activate</syntaxhighlight> The first line creates the folder containing the venv and the second line activates it. If you are not using bash, things may change slightly. For example, a user of the fish shell would instead run <syntaxhighlight> source venv/bin/activate.fish </syntaxhighlight> You'll know that a venv is currently active from an altered prompt such as this one: <syntaxhighlight> (venv) user@hostname:~$ </syntaxhighlight> With a venv loaded, all pip commands such as "pip install" and "pip uninstall" will affect only that venv. All Python code run with the venv's installation of Python will prefer to import the venv's libraries over any system libraries. (The command "which python" can help ensure that it is truly the venv Python as opposed to, say, the system "/usr/bin/python" that is running.) Lastly, a user who wishes to turn off a venv for the time being will only need to give the command "deactivate" to the shell. Further information about venv can be found in [https://docs.python.org/3/library/venv.html Python's official documentation]. = References = <references /> [[Category:Programming Languages]] 216c62ecc195702c0fa988ca5f8209f6f9f63ac2 3251 3250 2025-08-04T13:21:18Z Readyready15728 186 /* Setup Python venv */ wikitext text/x-wiki {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref> as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purpose software. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE. However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. = pip (Package Manager) = [https://pypi.org/project/pip/ pip] is Python's Package Manager, through pip you can install all the libraries needed for your project to run. pip stands for "''pip Installs Packages"''<ref>https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for</ref>. pip connects to an online software repository (PyPI). pip was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain pip and VirtualEnv. = Virtual Environments (VENV) = The venv module allows users to create Virtual Environments each with their own independent modules and libraries, This is useful for isolating project dependencies or debugging.. Venv was created by Ian Bicking (the same developer who created pip) and is now maintained by the Python Package Authority (PyPA). = Installing packages with pip = [user@hostname ~]$ <code>pip install package-name</code> = Installation = === Debian/Ubuntu Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo apt update [user@hostname ~]$ sudo apt install python3 python3-pip -y</syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash">[user@hostname ~]$ sudo pacman -Syu python python-pip</syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight>[user@hostname ~]$ sudo yum install python3 python3-pip -y</syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> [user@hostname ~]$ sudo yum install python3 python3-pip -y </syntaxhighlight> == Installation for pip == Python 3.4+ included pip by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash">[user@hostname ~]$ python -m ensurepip --upgrade</syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script, from <nowiki>https://bootstrap.pypa.io/get-pip.py</nowiki>. # Open a new terminal, cd to the folder containing the file # Run: <syntaxhighlight lang="bash">[user@hostname ~]$ python get-pip.py</syntaxhighlight> == '''Setup Python venv''' == When installing pip packages system-wide as root you will typically see a message like this one: <syntaxhighlight> ~ sudo pip install pyperclip Collecting pyperclip Downloading pyperclip-1.9.0.tar.gz (20 kB) Preparing metadata (setup.py) ... done Building wheels for collected packages: pyperclip Building wheel for pyperclip (setup.py) ... done Created wheel for pyperclip: filename=pyperclip-1.9.0-py3-none-any.whl size=11014 sha256=696d851be7b0d99fe8112ddf5c6ebc2b9444464b2a729911930d64bebc124c35 Stored in directory: /root/.cache/pip/wheels/cc/ae/36/ee17d1de094fcb61e24106cb329b5103861e819f94bef5e10a Successfully built pyperclip Installing collected packages: pyperclip Successfully installed pyperclip-1.9.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv </syntaxhighlight> Running pip as root can result in conflicted, broken packages and security risks.<ref>https://askubuntu.com/questions/802544/is-sudo-pip-install-still-a-broken-practice</ref> There are two possible responses to this situation: * See whether your distribution offers a system package to suit your needs. Depending on the distribution, system packages may be outdated, but this option should be tried first unless you are actively developing software. For example, with the Python module pyperclip mentioned above, there was a system package available that could fill the need, python3-pyperclip. * Or, if you are writing your own software, you can heed the warning as written and use the following instructions: The invocation is simple. Here's what it should look like in bash: <syntaxhighlight lang="bash">[user@hostname ~]$ python -m venv path/to/venv/ [user@hostname ~]$ source path/to/venv/bin/activate</syntaxhighlight> The first line creates the folder containing the venv and the second line activates it. If you are not using bash, things may change slightly. For example, a user of the fish shell would instead run <syntaxhighlight> source venv/bin/activate.fish </syntaxhighlight> You'll know that a venv is currently active from an altered prompt such as this one: <syntaxhighlight> (venv) user@hostname:~$ </syntaxhighlight> With a venv loaded, all pip commands such as "pip install" and "pip uninstall" will affect only that venv. All Python code run with the venv's installation of Python will prefer to import the venv's libraries over any system libraries. (The command "which python" can help ensure that it is truly the venv Python as opposed to, say, the system "/usr/bin/python" that is running.) Lastly, a user who wishes to turn off a venv for the time being will only need to give the command "deactivate" to the shell. Further information about venv can be found in [https://docs.python.org/3/library/venv.html Python's official documentation]. = References = <references /> [[Category:Programming Languages]] bd959985e63f6b075aabeacdaff6ca8a12dfb44c 0 790 3246 3230 2025-08-04T11:25:26Z Ok 425 Fixed grammatical errors found in the entire page, modified the distribution template to a more up-to-date and accurate version, added the "Browser" header for additional information. wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = Red Star OS | image = [[File:Red Star OS Logo 2020.svg|190px]] | caption = Red Star OS logo | releasestatus = Maintained | releasemodel = Unknown | packagemanager = [[rpm]] | defaultdesktops = [[KDE Plasma]], [[GNOME]] | usagetype = Desktop | architectures = [[IA-32]], [[x86-64]], [[ARM]] | website = None }} '''Red Star OS ('''Korean: 붉은별''')''' is a Red Hat Linux based distribution developed in the Democratic People's Republic of Korea (DPRK), made as a replacement for Windows in North Korea. It was first developed in 1998 by the Korea Computer Center. == Browser == '''Red Star OS''' relies on a heavily modified version of [[Firefox]] called ''[[Naenara]], which means "Our Country" in Korean.'' 5dca0d3d0e5b3702513934fe5d9f0159730bceba 0 203 3252 3231 2025-08-04T14:39:24Z Ok 425 Major page changes, removed majority of the bullet pointed lists with a more detailed documentation. wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish thru source compilation of the packages and the kernel itself. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements, the only downside of that being increase compilation time, however '''Gentoo''' is very minimal and it allows a lot of flexibility in that regard. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "slotting". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. To manage those multiple versions of the same packages ( slotting ), '''Gentoo''' provides a tool called '''eselect'''. It acts as a manager for setting system defaults, such as choosing which version of GCC, Python, or even your preferred text editor should be used globally. == Use cases of eselect == Changing the GCC version<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect gcc list [1] x86_64-pc-linux-gnu-13 * [2] x86_64-pc-linux-gnu-14 [user@hostname ~]$ eselect gcc set 2</syntaxhighlight>Changing the locale<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 * [3] en_US.utf8 [4] POSIX [ ] (free form) [user@hostname ~]$ eselect locale set 3 </syntaxhighlight> == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp) </syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |- |<code>emerge --unmerge package</code> |Remove a package and its dependencies |- |<code>emerge --depclean</code> |Remove unused dependencies |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through: * CPU-specific optimizations * Custom compile flags * USE flag combinations * Kernel configuration * Package-specific settings === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers: * Pre-compiled package options * Binary package creation * Distribution of binary packages * Mixed source/binary environments == Security == '''Gentoo''' implements several security measures: * [https://wiki.gentoo.org/wiki/SELinux SELinux support] * [https://wiki.gentoo.org/wiki/Hardened_Gentoo Hardened profiles] * Regular security updates * Signed package verification * [https://wiki.gentoo.org/wiki/Kernel Kernel hardening options] == Community and Development == === Community Resources === * [https://forums.gentoo.org/ Official Forums] * IRC channels * Mailing lists * Wiki documentation * [https://bugs.gentoo.org/ Bug tracking system] === Development Model === * Open source development * Community-driven package maintenance * Regular security updates * Active development team * Public Git repositories == Comparison with Other Distributions == '''Gentoo''' allows maximum customization potential, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to fetch binaries in heavier packages. However, '''Gentoo''' has it's own downsides; It will take longer to install packages as they compile from source, meaning it will take some time until finished and ready to use. If the system has a very weak CPU, the Operating System will take a while to fully install. The Operating System has a higher learning curve, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 0949a98e860d3248cf3285ed224c4e60414e2133 3261 3252 2025-08-05T03:28:46Z Ok 425 Replaced the bullet pointed Binary Packages section with actual text. wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish thru source compilation of the packages and the kernel itself. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements, the only downside of that being increase compilation time, however '''Gentoo''' is very minimal and it allows a lot of flexibility in that regard. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "slotting". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. To manage those multiple versions of the same packages ( slotting ), '''Gentoo''' provides a tool called '''eselect'''. It acts as a manager for setting system defaults, such as choosing which version of GCC, Python, or even your preferred text editor should be used globally. == Use cases of eselect == Changing the GCC version<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect gcc list [1] x86_64-pc-linux-gnu-13 * [2] x86_64-pc-linux-gnu-14 [user@hostname ~]$ eselect gcc set 2</syntaxhighlight>Changing the locale<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 * [3] en_US.utf8 [4] POSIX [ ] (free form) [user@hostname ~]$ eselect locale set 3 </syntaxhighlight> == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp) </syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |- |<code>emerge --unmerge package</code> |Remove a package and its dependencies |- |<code>emerge --depclean</code> |Remove unused dependencies |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. * CPU-specific optimizations * Custom compile flags * USE flag combinations * Kernel configuration * Package-specific settings === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers pre-compiled package options, which usually end in '''<code>-bin</code>''', by example one might want to install Firefox without the hassle of compiling, they can just download the binary version of it by doing <code>sudo emerge firefox-bin</code>. Obviously, not all binary packages will end in the <code>-bin</code> format, they can be named simply like normal packages, for that reason Portage highlights the binary and source packages differently in colors so the user knows which are binary and which are meant for compiling, additionally portage also informs the user of which packages are binaries or source. For additional packages, users might opt for the [https://wiki.gentoo.org/wiki/Project:GURU GURU] project repository, it aims to be a very large user repository, full of binaries and source packages that are not found inside the normal '''Gentoo''' repositories, meant to extend the experience that you can have in this Operating System. Users can create their own repository online as well, or how we call it, "overlays". The user can create an overlay with the desired package, make an ebuild for it and then publish it online for people to use. To get started with an overlay, one must first understand what are ebuilds and how they work, for this it's preferred to read the '''Gentoo Wiki''' on how to do it, it is possible to even add your custom package inside '''GURU''' later, and even the official '''Gentoo''' repository if it's seen as valuable. == Security == '''Gentoo''' implements several security measures: * [https://wiki.gentoo.org/wiki/SELinux SELinux support] * [https://wiki.gentoo.org/wiki/Hardened_Gentoo Hardened profiles] * Regular security updates * Signed package verification * [https://wiki.gentoo.org/wiki/Kernel Kernel hardening options] == Community and Development == === Community Resources === * [https://forums.gentoo.org/ Official Forums] * IRC channels * Mailing lists * Wiki documentation * [https://bugs.gentoo.org/ Bug tracking system] === Development Model === * Open source development * Community-driven package maintenance * Regular security updates * Active development team * Public Git repositories == Comparison with Other Distributions == '''Gentoo''' allows maximum customization potential, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to fetch binaries in heavier packages. However, '''Gentoo''' has it's own downsides; It will take longer to install packages as they compile from source, meaning it will take some time until finished and ready to use. If the system has a very weak CPU, the Operating System will take a while to fully install. The Operating System has a higher learning curve, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] f4301026dc7ad2fe8c42db1141d5b59adee448a5 3266 3261 2025-08-05T11:32:45Z Ok 425 Cleaned up the bullet pointed lists and remove the warning regarding too many bullet pointed lists. wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish thru source compilation of the packages and the kernel itself. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements, the only downside of that being increase compilation time, however '''Gentoo''' is very minimal and it allows a lot of flexibility in that regard. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "slotting". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. To manage those multiple versions of the same packages ( slotting ), '''Gentoo''' provides a tool called '''eselect'''. It acts as a manager for setting system defaults, such as choosing which version of GCC, Python, or even your preferred text editor should be used globally. == Use cases of eselect == Changing the GCC version<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect gcc list [1] x86_64-pc-linux-gnu-13 * [2] x86_64-pc-linux-gnu-14 [user@hostname ~]$ eselect gcc set 2</syntaxhighlight>Changing the locale<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 * [3] en_US.utf8 [4] POSIX [ ] (free form) [user@hostname ~]$ eselect locale set 3 </syntaxhighlight> == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp) </syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |- |<code>emerge --unmerge package</code> |Remove a package and its dependencies |- |<code>emerge --depclean</code> |Remove unused dependencies |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers pre-compiled package options, which usually end in '''<code>-bin</code>''', by example one might want to install Firefox without the hassle of compiling, they can just download the binary version of it by doing <code>sudo emerge firefox-bin</code>. Obviously, not all binary packages will end in the <code>-bin</code> format, they can be named simply like normal packages, for that reason Portage highlights the binary and source packages differently in colors so the user knows which are binary and which are meant for compiling, additionally portage also informs the user of which packages are binaries or source. For additional packages, users might opt for the [https://wiki.gentoo.org/wiki/Project:GURU GURU] project repository, it aims to be a very large user repository, full of binaries and source packages that are not found inside the normal '''Gentoo''' repositories, meant to extend the experience that you can have in this Operating System. Users can create their own repository online as well, or how we call it, "overlays". The user can create an overlay with the desired package, make an ebuild for it and then publish it online for people to use. To get started with an overlay, one must first understand what are ebuilds and how they work, for this it's preferred to read the '''Gentoo Wiki''' on how to do it, it is possible to even add your custom package inside '''GURU''' later, and even the official '''Gentoo''' repository if it's seen as valuable. == Security == '''Gentoo''' allows users to setup extensive [[SELinux]] support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === One might be interested in community resources for '''Gentoo.''' The official community forums can be found at [https://forums.gentoo.org/ forums.gentoo.org/]. Additionally, IRC ('''Internet Relay Chat''') channels has been setup as well. For those who are interested in the official IRC channels, they can be found on the '''Gentoo Wiki''' in the [https://wiki.gentoo.org/wiki/IRC IRC] article. It is possible to subscribe to the [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] or even send emails to them, the page lists the most important lists with the most traffic. There are other, more specialized lists that might be more appropriate depending on the topic. There is a [https://www.gentoo.org/support/documentation/ wiki documentation] available as well. Users can search up specific pages in the site directly, so that they don't waste time finding the right page. Ultimately, '''Gentoo''' offers a [https://bugs.gentoo.org/ bug tracking system] for those who are interested in being up to date with current bugs, or even attempt to solve them. === Development Model === '''Gentoo''' was developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the userbase through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == '''Gentoo''' allows maximum customization potential, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to fetch binaries in heavier packages. However, '''Gentoo''' has it's own downsides; It will take longer to install packages as they compile from source, meaning it will take some time until finished and ready to use. If the system has a very weak CPU, the Operating System will take a while to fully install. The Operating System has a higher learning curve, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] aac58fc83b372c8243a62f6f6a099f2b8dcffdd9 3276 3266 2025-08-05T17:48:20Z Ok 425 Added citiations, removed the no citations warning. wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]<ref>https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer)</ref>. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile<ref>https://en.wikipedia.org/wiki/Compilation</ref> their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish thru source compilation of the packages and the kernel itself. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements, the only downside of that being increase compilation time, however '''Gentoo''' is very minimal and it allows a lot of flexibility in that regard. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "slotting". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. To manage those multiple versions of the same packages ( slotting ), '''Gentoo''' provides a tool called '''eselect'''. It acts as a manager for setting system defaults, such as choosing which version of GCC, Python, or even your preferred text editor should be used globally. == Use cases of eselect == Changing the GCC version<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect gcc list [1] x86_64-pc-linux-gnu-13 * [2] x86_64-pc-linux-gnu-14 [user@hostname ~]$ eselect gcc set 2</syntaxhighlight>Changing the locale<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 * [3] en_US.utf8 [4] POSIX [ ] (free form) [user@hostname ~]$ eselect locale set 3 </syntaxhighlight> == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp) </syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |- |<code>emerge --unmerge package</code> |Remove a package and its dependencies |- |<code>emerge --depclean</code> |Remove unused dependencies |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers pre-compiled package options, which usually end in '''<code>-bin</code>''', by example one might want to install Firefox without the hassle of compiling, they can just download the binary version of it by doing <code>sudo emerge firefox-bin</code>. Obviously, not all binary packages will end in the <code>-bin</code> format, they can be named simply like normal packages, for that reason Portage highlights the binary and source packages differently in colors so the user knows which are binary and which are meant for compiling, additionally portage also informs the user of which packages are binaries or source. For additional packages, users might opt for the [https://wiki.gentoo.org/wiki/Project:GURU GURU] project repository, it aims to be a very large user repository, full of binaries and source packages that are not found inside the normal '''Gentoo''' repositories, meant to extend the experience that you can have in this Operating System. Users can create their own repository online as well, or how we call it, "overlays". The user can create an overlay with the desired package, make an ebuild for it and then publish it online for people to use. To get started with an overlay, one must first understand what are ebuilds and how they work, for this it's preferred to read the '''Gentoo Wiki''' on how to do it, it is possible to even add your custom package inside '''GURU''' later, and even the official '''Gentoo''' repository if it's seen as valuable. == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === One might be interested in community resources for '''Gentoo.''' The official community forums can be found at [https://forums.gentoo.org/ forums.gentoo.org/]. Additionally, IRC<ref>Internet Relay Chat</ref> channels has been setup as well. For those who are interested in the official IRC channels, they can be found on the '''Gentoo Wiki''' in the [https://wiki.gentoo.org/wiki/IRC IRC] article. It is possible to subscribe to the [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] or even send emails to them, the page lists the most important lists with the most traffic. There are other, more specialized lists that might be more appropriate depending on the topic. There is a [https://www.gentoo.org/support/documentation/ wiki documentation] available as well. Users can search up specific pages in the site directly, so that they don't waste time finding the right page. Ultimately, '''Gentoo''' offers a [https://bugs.gentoo.org/ bug tracking system] for those who are interested in being up to date with current bugs, or even attempt to solve them. === Development Model === '''Gentoo''' was developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the userbase through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == '''Gentoo''' allows maximum customization potential, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to fetch binaries in heavier packages. However, '''Gentoo''' has it's own downsides; It will take longer to install packages as they compile from source, meaning it will take some time until finished and ready to use. If the system has a very weak CPU, the Operating System will take a while to fully install. The Operating System has a higher learning curve, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 361409fb96d4ea9a39755cf2b78fa0391d9327dd 10 688 3253 2585 2025-08-04T18:24:21Z Ow0cast 249 tmpl docs | replace external link to wikipedia with interwiki link wikitext text/x-wiki Adapted from [[wikipedia:Template:Key Press|Template:Key Press]] on Wikipedia 39fffdbff1177dca53d55e7831bc0da5c7f779c9 10 687 3254 2591 2025-08-04T18:29:13Z Ow0cast 249 tmpl | add template data wikitext text/x-wiki <includeonly>{{safesubst:#invoke:Key_Press|keypress}}</includeonly><noinclude> {{/doc}} <templatedata> { "params": { "any": { "label": "Any positional argument", "description": "The key(s) to display", "type": "string" } }, "description": "Properly formats a keybind.", "paramOrder": [ "any" ] } </templatedata></noinclude> 0dcb0f1de73618efd1279996b9589b47d8d2b8dc 0 317 3255 3018 2025-08-04T19:45:06Z Satnus 215 Changed the section about the init system to use less bullet points. wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm]</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and Musl variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses the homegrown [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for run it. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == [[Category:Linux Distributions]] 1038119e8043f40058a779b9a837611e10f8dfb7 3256 3255 2025-08-04T19:46:19Z Satnus 215 Fixed a typo on the init section that happened because of my autocorrect. wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm]</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and Musl variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses the homegrown [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for runit. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == [[Category:Linux Distributions]] 11520b50d5ca82047130057b77203e7a81c9e235 0 171 3257 3185 2025-08-04T19:46:30Z Crdr 216 typo wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such as nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] 3bec55a482a6a1be01bf9b9387ab659a12e9ab52 2 803 3258 2025-08-05T00:32:51Z Host 218 Created page with "hello! i'm adi, part of the systems team at ATL. feel free to reach out :) [http://mailto:host@allthingslinux.org host@allthingslinux.org]" wikitext text/x-wiki hello! i'm adi, part of the systems team at ATL. feel free to reach out :) [http://mailto:host@allthingslinux.org host@allthingslinux.org] a99e404adddbc23845ffa25571c2d529b29a1c13 3259 3258 2025-08-05T00:33:31Z Host 218 wikitext text/x-wiki hello! i'm adi, part of the systems team at ATL. feel free to reach out :) [mailto:host@allthingslinux.org host@allthingslinux.org] 107b847d1138d539de6925156acd4b51657d9f86 2 804 3260 2025-08-05T01:43:54Z Ow0cast 249 trol wikitext text/x-wiki <templatestyles src="Module:Mbox/styles.css"></templatestyles> <div class="mbox mbox-med"><div class="mbox-title"><div class="mbox-icon metadata">[[File:OOjs UI icon alert.svg|14px|link=]]</div><big><big>Unauthorized editing of this page may result in in being [[wikipedia:WP:TROUT|slapped with a trout]]</big></big><br> </div></div> 9700d4d72ded82acbb923f09b6c3b214b4342af4 2 805 3262 2025-08-05T04:51:35Z Ow0cast 249 make sandbox and test a theory wikitext text/x-wiki {{padright:xyz|50}} 6d3d6e142e0ec6541cabf95919c507795c66d023 3263 3262 2025-08-05T04:52:17Z Ow0cast 249 wikitext text/x-wiki {{padright:xyz|75}} b5f9a6162c54227dbde9459f4404629559d5020f 3264 3263 2025-08-05T04:53:28Z Ow0cast 249 wikitext text/x-wiki {{padright:xyz|120}} d60f46c1e5fe40f1b0d94bddcb90ac271d429fbc 0 763 3265 3156 2025-08-05T10:53:38Z Satnus 215 Added i3, added reference for twm wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |awesome<ref>https://github.com/awesomeWM/awesome</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |Compiz |Compiz is a compositing window manager for the X Window System. |- |Openbox |A minimal and highly configurable stacking window manager written in C. |- |twm<ref>https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |IceWM<ref>https://github.com/bbidulock/icewm</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |i3<ref>https://i3wm.org</ref> |A tiling window manager for advanced users and developers. |- |Window Maker<ref>https://github.com/window-maker/wmaker</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |} ==References== <references /> 1ed8e3b875a7a30abdfd08d09e7385198a3c1f17 3279 3265 2025-08-06T00:54:31Z Hetman Foko 221 added XMonad to X WMs table wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |awesome<ref>https://github.com/awesomeWM/awesome</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |Compiz |Compiz is a compositing window manager for the X Window System. |- |Openbox |A minimal and highly configurable stacking window manager written in C. |- |twm<ref>https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |IceWM<ref>https://github.com/bbidulock/icewm</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |i3<ref>https://i3wm.org</ref> |A tiling window manager for advanced users and developers. |- |Window Maker<ref>https://github.com/window-maker/wmaker</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |XMonad<ref>https://xmonad.org/</ref> |Window Manager configurable via the Haskell functional programming language. |} ==References== <references /> 6f2a2561be8a0d6bfaa54613c9e94656aa2a172f 3287 3279 2025-08-07T09:45:06Z Satnus 215 Added internal links to all window managers. wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |[[awesome]]<ref>https://github.com/awesomeWM/awesome</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |[[Compiz]] |Compiz is a compositing window manager for the X Window System. |- |[[Openbox]] |A minimal and highly configurable stacking window manager written in C. |- |[[twm]]<ref>https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |[[IceWM]]<ref>https://github.com/bbidulock/icewm</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |[[i3]]<ref>https://i3wm.org</ref> |A tiling window manager for advanced users and developers. |- |[[Window Maker]]<ref>https://github.com/window-maker/wmaker</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |[[XMonad]]<ref>https://xmonad.org/</ref> |Window Manager configurable via the Haskell functional programming language. |} ==References== <references /> 9fa69db897a1e69578d52c65033769911e8ef14a 0 344 3267 2967 2025-08-05T13:55:31Z Atmois 13 Improve readability of the first paragraph and remove a spiel about gnu/linux wikitext text/x-wiki [[File:Kernel Layout.svg|thumb|How the Kernel interacts with the software and hardware.]] The Kernel is the core part of any [[Operating System|operating system]], such as the [[Linux|Linux Kernel]]. It's the fundamental layer between the computers [[hardware]] - including but not limited to the CPU, RAM, and GPU, and the [[:Category:Software|software]] you interact with. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, etc.). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2 Linus Torvalds 1991 (Retrieved 16th March 2025)</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel Kicksecure, Madaiden, Adrelanos 2023 (Retrieved 16th March 2025)</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. == References == [[Category:Terminology]] 8a965a1bc989bd784ba9db1f8b9797273d7cfc21 6 807 3269 2025-08-05T15:10:45Z Satnus 215 wikitext text/x-wiki Sudo used on whoami, demonstrating its capabilities to run a command as root (or another user). c3fe8e8acfd534388d748466d97d444b088dc8e3 0 309 3270 3002 2025-08-05T15:16:28Z Satnus 215 Changed thumbnail of sudo, updated Last Release wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png.png|thumb]] |thumb]] | caption = Sudo used on [[whoami]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.17p2 | languages = [[C]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} [[File:Sudo logo.png|thumb|335x335px|Sudo's logo of a sandwich]] [[File:Sudo Insults.png|thumb|335x335px|Output from sudo when <code>Defaults insults</code> is added]] The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]).<ref name=":0">[https://man7.org/linux/man-pages/man8/sudo.8.html sudo(8)], Linux Manpages</ref> Its name is shorthand for "su 'do'"<ref>[https://www.sudo.ws/ sudo.ws], Sudo Developers</ref>, however as <code>su</code> stands for "substitute user"<ref>[https://man7.org/linux/man-pages/man1/su.1.html su(1)], Linux Manpages</ref> this would stand for "substitute user, do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file<ref name=":0" /> to specify which users or groups can execute specific commands. == Usage == {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |Run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser''<ref name=":0" /> == Trivia == * Sudo's logo is a sandwich in reference to [https://xkcd.com/149/ xkcd 149]<ref>[https://www.sudo.ws/about/logo/ sudo.ws/about/logo], Sudo Developers</ref> * If you add the line <code>Defaults insults</code> to the Defaults section of <code>/etc/sudoers</code>, you will be insulted whenever you type the wrong password.<ref>[https://www.geeksforgeeks.org/when-sudo-insults-you/ When sudo insults you!!], GeeksforGeeks, September 13, 2023 (February 12, 2025)</ref> == References == [[Category:Software]] e106a91bed1a1351a546eeda25bfd38807d92493 0 2 3271 3207 2025-08-05T15:48:07Z Sol Wolf 219 /* Installation */ Refactored the installation section. wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch_Linux_Minimal_Neofetch_Output.png|thumb|[[Neofetch]] on Arch Linux]] '''Arch Linux''' is an independent rolling release [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. Arch Linux is kept up-to-date by regularly updating the packages of the system. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Installation === The Arch Linux website provides a downloadable ISO image that can be flashed onto a bootable drive. The operating system can be installed by following the [https://wiki.archlinux.org/title/Installation_guide Installation Guide] or by using the included installation script, archinstall. ==== Arch Installation Script ==== This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] 7dfc45e344e21d5e296e319a0b7a65e2dc65cb88 6 808 3272 2025-08-05T17:28:17Z Ok 425 Official logo for the Funtoo Linux Distribution wikitext text/x-wiki == Summary == Official logo for the Funtoo Linux Distribution 5c4f40cf8e00af588dc2c75b5365686d62b66bc7 0 809 3273 2025-08-05T17:33:00Z Ok 425 Create initial article for the Funtoo distribution with minimal info. wikitext text/x-wiki {{DistributionInfobox|title=Funtoo Linux|image=[[File:funtoo.png|300px|Gentoo Linux logo matte]]|caption=The official Funtoo Linux logo|releasestatus=Discontinued|releasemodel=Rolling Release / Stable|packagemanager=[[portage]]|defaultdesktops=[[GNOME]]|usagetype=Desktop, Server|architectures=amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86|website=[https://www.gentoo.org/ gentoo.org]}}[https://www.funtoo.org/Welcome Funtoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in early 2008 by Daniel Robbins. Known for its emphasis on customization and performance optimization, '''Funtoo''' allows users to compile their entire system from source code, providing granular control over system components and features. f72876afda4db67ef818bd5d0e8f851bde14cb5e 3274 3273 2025-08-05T17:33:38Z Ok 425 wikitext text/x-wiki {{DistributionInfobox|title=Funtoo Linux|image=[[File:funtoo.png|300px|Gentoo Linux logo matte]]|caption=The official Funtoo Linux logo|releasestatus=Discontinued|releasemodel=Rolling Release / Stable|packagemanager=[[portage]]|defaultdesktops=[[GNOME]]|usagetype=Desktop, Server|architectures=amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86|website=[https://www.funtoo.org/Welcome funtoo.org]}}[https://www.funtoo.org/Welcome Funtoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in early 2008 by Daniel Robbins. Known for its emphasis on customization and performance optimization, '''Funtoo''' allows users to compile their entire system from source code, providing granular control over system components and features. 5ff1e6df9dbd5516750f6a579118c5b60f210d58 3275 3274 2025-08-05T17:36:59Z Ok 425 Added the page to the Linux Distribution category wikitext text/x-wiki {{DistributionInfobox|title=Funtoo Linux|image=[[File:funtoo.png|300px|Gentoo Linux logo matte]]|caption=The official Funtoo Linux logo|releasestatus=Discontinued|releasemodel=Rolling Release / Stable|packagemanager=[[portage]]|defaultdesktops=[[GNOME]]|usagetype=Desktop, Server|architectures=amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86|website=[https://www.funtoo.org/Welcome funtoo.org]}}[https://www.funtoo.org/Welcome Funtoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in early 2008 by Daniel Robbins. Known for its emphasis on customization and performance optimization, '''Funtoo''' allows users to compile their entire system from source code, providing granular control over system components and features. [[Category:Linux Distributions]] 015866ac825cecd10801ea83e4429679b621d358 0 810 3277 2025-08-05T18:00:15Z Rayk4z1 62 Partially Create the OpenRC page but I got really lazy, So its just general info and one paragraphy on over view wikitext text/x-wiki '''OpenRC''' is a dependency-based [[Init System|init system]] made in [[C]] and [[Shell]] for Unix-like [[Operating System|Operating Systems]]. Created by [[NetBSD]] developer and ex-maintainer of the [[Gentoo]] Project.<ref>Wikipedia, The Free Encyclopedia: https://en.wikipedia.org/wiki/OpenRC (Accessed Aug 5th, 2025)</ref> Due to OpenRC being made from C and POSIX-Compliant Shell, it is portable between [[Linux]], [[FreeBSD]], and NetBSD. It can optionally be used as an init system or as a [[Process Supervisor|process supervisor]]. = Overview = OpenRC is a default init system and/or process supervisor on many [[Linux Distributions]] due to its lightweight and compatibility properties. The init system is made of several modular components allowing full-scale customization in terms of what the process actual does for being an init system or as a daemon supervisor. (W.I.P, I got lazy again) 048bc47c952024a572f9c0e4a3ebb56cd0c3637e 0 202 3278 3234 2025-08-05T18:05:23Z ArainVinn 220 Added citation details to follow guidelines, said 4th June 2024 for citations 4 and 5 assuming that the original author added them at the same time. Couldn't find the creation date for the myspace page. wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow Gentoo Wiki, 2023 (Imported 4th June 2024)</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html Gentoo Forums, 2003 (imported 4th June 2024)</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727 Gentoo Bug Report, 2003 (imported 4th June 2024)</ref> * Larry can be found in [[emerge]] by running <code>emerge --moo</code> Larry can also be found in [[Dpkg|apt]] by running <code>apt moo</code> . * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow MySpace, (imported 4th June 2024)</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry, Gentoo Wiki, 2000 (imported 4th June 2024)</ref> [[File:Larry The Cow with Gentoo Logo.png|thumb|Larry after he grew his black and white patches]] == References == <references /> [[Category:Mascots]] f06fc89ee3e9714a9338d41dee071b36de136b90 0 668 3280 3032 2025-08-06T10:43:33Z Madonuko 140 /* Installation */ and /* Flags and Options */ wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''.’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref> == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor [[ed]] (1971) and the even earlier [[qed]] (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command.<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref> sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Installation == sed is installed by default on most UNIX systems. If not, consult the distribution's [[package manager]]. For most cases the package name would be <code>sed</code> or <code>gsed</code>. Different flavours of sed are available, the most common ones being GNU sed and BSD sed. Developers who expect their sed scripts to be executed on different platforms should account for their significant differences.<ref>[https://www.baeldung.com/linux/gnu-bsd-stream-editor GNU sed vs. BSD sed], Haidar Ali, 2024 (Accessed: 2025-08-06)</ref> Run <code>sed --version</code> to check for the version and flavour of sed. == Flags and Options == For the full list, consult <code>[[man]] 'sed(1)'</code> or <code>sed --help</code>. {| class="wikitable" |+ Table of Common Command-line Flags & Options |- ! Flag !! Description |- | <code>-n</code> || Suppress printing |- | <code>-e</code> || Multiple commands (e.g., <code>sed -e 's/a/b/' -e 's/c/d/'</code>) |- | <code>-f</code> || Read commands from file |- | <code>-i[SUFFIX]</code> || Edit file in-place. A suffix for the backup file may be provided. |- | <code>-E</code>/<code>-r</code> || Use extended regex |- | <code>-z</code> || Null-terminated lines |} == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; ...} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to EOF. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10–15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended regular expressions''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] == Related Tools == * [[AWK]]: Process column-based data * [[grep]]: Search for lines in stream using regex * [[perl]]: Programming language for complex text processing == References == 01c2604c6c70b2cc3b09ecc0b09a5b2a6f7d1413 3286 3280 2025-08-07T09:28:51Z Imnotgoodatnames 121 Changed "UNIX" to "Unix-like" as it applies to other Unix-like systems such as Linux distros, the BSDs, etc. wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''.’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref> == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor [[ed]] (1971) and the even earlier [[qed]] (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command.<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref> sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Installation == sed is installed by default on most Unix-like systems. If not, consult the distribution's [[package manager]]. For most cases the package name would be <code>sed</code> or <code>gsed</code>. Different flavours of sed are available, the most common ones being GNU sed and BSD sed. Developers who expect their sed scripts to be executed on different platforms should account for their significant differences.<ref>[https://www.baeldung.com/linux/gnu-bsd-stream-editor GNU sed vs. BSD sed], Haidar Ali, 2024 (Accessed: 2025-08-06)</ref> Run <code>sed --version</code> to check for the version and flavour of sed. == Flags and Options == For the full list, consult <code>[[man]] 'sed(1)'</code> or <code>sed --help</code>. {| class="wikitable" |+ Table of Common Command-line Flags & Options |- ! Flag !! Description |- | <code>-n</code> || Suppress printing |- | <code>-e</code> || Multiple commands (e.g., <code>sed -e 's/a/b/' -e 's/c/d/'</code>) |- | <code>-f</code> || Read commands from file |- | <code>-i[SUFFIX]</code> || Edit file in-place. A suffix for the backup file may be provided. |- | <code>-E</code>/<code>-r</code> || Use extended regex |- | <code>-z</code> || Null-terminated lines |} == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; ...} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to EOF. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10–15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended regular expressions''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] == Related Tools == * [[AWK]]: Process column-based data * [[grep]]: Search for lines in stream using regex * [[perl]]: Programming language for complex text processing == References == 600c6701efa48296d0609af98259ef48a3323ced 3288 3286 2025-08-07T15:45:40Z Madonuko 140 /* Advanced Topics */ wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''.’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref> == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor [[ed]] (1971) and the even earlier [[qed]] (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command.<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref> sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Installation == sed is installed by default on most Unix-like systems. If not, consult the distribution's [[package manager]]. For most cases the package name would be <code>sed</code> or <code>gsed</code>. Different flavours of sed are available, the most common ones being GNU sed and BSD sed. Developers who expect their sed scripts to be executed on different platforms should account for their significant differences.<ref>[https://www.baeldung.com/linux/gnu-bsd-stream-editor GNU sed vs. BSD sed], Haidar Ali, 2024 (Accessed: 2025-08-06)</ref> Run <code>sed --version</code> to check for the version and flavour of sed. == Flags and Options == For the full list, consult <code>[[man]] 'sed(1)'</code> or <code>sed --help</code>. {| class="wikitable" |+ Table of Common Command-line Flags & Options |- ! Flag !! Description |- | <code>-n</code> || Suppress printing |- | <code>-e</code> || Multiple commands (e.g., <code>sed -e 's/a/b/' -e 's/c/d/'</code>) |- | <code>-f</code> || Read commands from file |- | <code>-i[SUFFIX]</code> || Edit file in-place. A suffix for the backup file may be provided. |- | <code>-E</code>/<code>-r</code> || Use extended regex |- | <code>-z</code> || Null-terminated lines |} == Syntax == The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; ...} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. === Commands === * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). === Addresses === * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to EOF. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10–15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} == Examples == === Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags === Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''extended regular expressions''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> === FizzBuzz === FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz === Renaming Files === Multiple files can be renamed if the new name can be easily systematically determined from the old name: <syntaxhighlight lang="sh"> ls *.txt | sed 's/\(.*\)\.txt/mv & \1_old.txt/' | sh </syntaxhighlight> The commands could also be executed within sed: <syntaxhighlight lang="sh"> ls *.txt | sed 's/\(.*\)\.txt/mv & \1_old.txt/e' </syntaxhighlight> == Advanced Topics == === Performance === Regex is frequently used in sed scripts. As with every other engines, avoid backtracking in regex by limiting matches, e.g., <code>.*</code> vs. <code>[^ ]*</code> when matching until a space potentially. See [[Regular Expression#Optimisation]] for further tips. Additionally, the use of regex greatly affects the performance of the sed script, as showcased by the following simple benchmark: {| class="wikitable" !Command !<code>seq</code> Time !<code>sed</code> Time |- | <syntaxhighlight lang="sh" line> time seq 999999999 | sed ' 15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' > /dev/null </syntaxhighlight> | <code>12.54s user 2.48s system 25% cpu 58.894 total</code> | <code>56.64s user 2.00s system 99% cpu 58.894 total</code> |- | <syntaxhighlight lang="sh" line> time seq 999999999 | sed ' 15~15{s@.\+@FizzBuzz@; b} 3~3{s@.\+@Fizz@; b} 5~5s@.+@Buzz@' > /dev/null </syntaxhighlight> | <code>13.25s user 2.65s system 11% cpu 2:20.58 total</code> | <code>138.01s user 2.15s system 99% cpu 2:20.58 total</code> |- | <syntaxhighlight lang="sh" line> time seq 999999999 | sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' > /dev/null </syntaxhighlight> | <code>14.08s user 2.83s system 9% cpu 2:49.54 total</code> | <code>166.93s user 2.07s system 99% cpu 2:49.54 total</code> |} As opposed to popular beliefs, adding an address filter before an <code>s</code> command does not improve performance: <syntaxhighlight lang="shell-session"> $ time seq 999999999 | sed 's@11@@' > /dev/null seq 999999999 13.87s user 2.87s system 22% cpu 1:15.94 total sed 's@11@@' > /dev/null 73.50s user 2.20s system 99% cpu 1:15.94 total $ time seq 999999999 | sed '/11/s@11@@' > /dev/null seq 999999999 13.89s user 2.79s system 20% cpu 1:21.60 total sed '/11/s@11@@' > /dev/null 79.13s user 2.20s system 99% cpu 1:21.61 total </syntaxhighlight> === Basic Regular Expression === Contrary to expectations, the original flavour of the built-in regular expression is not a subset of the extended flavour. Instead, some tokens (such as <code>\|</code>, <code>\(''group''\)</code>, etc.) require an extra prefixing backslash. Consult the following online documentations for the in-depth overview of the flavour: * https://www.gnu.org/software/sed/manual/html_node/Regular-Expressions.html * https://en.wikibooks.org/wiki/Regular_Expressions/POSIX_Basic_Regular_Expressions Even then, the use of extended regular expression could impact performance (as shown above), so it could be useful to use BRE instead. === Sandboxing === The <code>--sandbox</code> flag could be useful in cases where untrusted sed scripts need to be executed: --sandbox -- block commands that can affect the system (r/w/W/e) This mode prevents sed scripts from executing commands, read or writing files specified by the scripts. == Troubleshooting == === <code>unterminated `s' command</code> === As the error message suggests, <code>s</code> commands must be terminated with the given delimiter: <syntaxhighlight lang="shell-session"> $ echo 'a foo of chocolate' | sed 's/foo/bar' # Missing final delimiter sed: -e expression #1, char 9: unterminated `s' command $ echo 'a foo of chocolate' | sed 's/foo/bar/' a bar of chocolate $ echo 'a foo of chocolate' | sed 's@a@the' sed: -e expression #1, char 7: unterminated `s' command $ echo 'a foo of chocolate' | sed 's@a@the@' the foo of chocolate </syntaxhighlight> === Greedy Patterns === <syntaxhighlight lang="shell-session"> $ echo "foo bar baz" | sed 's/f.*b/x/' xaz </syntaxhighlight> Some times the unexpected output is obtained due to the pattern matching too greedily. Since both BRE and ERE do not support lazy patterns, a more limiting expression is needed compared to <code>.</code> which matches for all characters: <syntaxhighlight lang="shell-session"> $ echo "foo bar baz" | sed 's/f\w* b/x/' xar baz </syntaxhighlight> == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] == Related Tools == * [[AWK]]: Process column-based data * [[grep]]: Search for lines in stream using regex * [[perl]]: Programming language for complex text processing == References == 62ea3b6dae425ad4bc21905ffc8ef44cc543fed3 3290 3288 2025-08-07T16:15:42Z Madonuko 140 split page according to guidelines wikitext text/x-wiki {{DISPLAYTITLE:sed}} [[Category:Software]] [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Sed-fizzbuzz.png|frameless]] | caption = Solving the FizzBuzz problem with [[GNU]] sed | title = <code>sed</code> | releasestatus = Maintained | lastrelease = 4.9 (2022-11-07) | languages = [[C]] | developers = GNU <code>sed</code>: GNU Project, et al. | website = https://www.gnu.org/software/sed/ }} '''<code>sed</code>''' ('''S'''tream '''ED'''itor) is a powerful text processing tool available in [[UNIX|Unix-like]] [[Operating System|operating systems]], used for filtering and transforming text, especially when working with streams of text data. Most commonly, it is ‘''used for extracting part of a file using pattern matching or substituting multiple occurrences of a string within a file''.’<ref>[https://www.gnu.org/software/sed/ GNU sed - GNU Project - Free Software Foundation], Free Software Foundation, Inc., 2020 (Accessed: 2025-06-20)</ref> == History == sed dates back to the early 1970s at Bell Labs. It was developed from 1973 to 1974 by Lee E. McMahon as a Unix utility designed to parse and transform text using a simple programming language.<ref>[https://web.archive.org/web/20180627160704/http://sed.sourceforge.net/sedfaq2.html#s2.1 The sed FAQ, Section 2.1], Eric Pement, 2003 (Accessed: 2018-06-27)</ref> It was based on the scripting features of the earlier interactive editor [[ed]] (1971) and the even earlier [[qed]] (1965–66), inheriting their pattern matching and substitution syntax, notably the use of slashes for patterns and the <code>s///</code> substitution command.<ref name=":0">[[wikipedia:Sed|sed - Wikipedia]], Wikipedia, 2025 (Accessed: 2025-06-20)</ref> sed first appeared in Version 7 Unix and was created to serve as a general-purpose line-oriented stream editor, evolving naturally as a successor to the [[grep]] command. While grep was used for searching text with regular expressions, sed was designed to perform substitutions and other editing operations on streams of text, making it more versatile for text processing tasks.<ref>[https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed A Brief History of sed], Sourcerer Blog, 2018 (Accessed: 2025-06-20)</ref> The name ''sed'' reflects its function as a ''stream editor'', capable of performing global regular expression substitutions and deletions. sed was one of the earliest tools to support regular expressions and influenced many later languages, including [[AWK]] and [[Perl]]. AWK, developed later, and sed together, functioned as complementary tools for text processing in Unix [[TUI|shell]] scripts. Both sed and awk inspired Perl's design, especially in its pattern matching and substitution features.<ref name=":0" /> Over time, several variants of sed have emerged. GNU sed added features like in-place file editing, while other versions like <code>ssed</code> ('''super-sed''') extended regular expression compatibility to Perl-like syntax.<ref>[https://launchpad.net/ssed ssed], Launchpad, 2005 (Accessed: 2025-06-20)</ref> A minimal version called minised was reverse-engineered from BSD sed and used in embedded systems for its speed and low memory usage.<ref name=":0" /> == Installation == sed is installed by default on most Unix-like systems. If not, consult the distribution's [[package manager]]. For most cases the package name would be <code>sed</code> or <code>gsed</code>. Different flavours of sed are available, the most common ones being GNU sed and BSD sed. Developers who expect their sed scripts to be executed on different platforms should account for their significant differences.<ref>[https://www.baeldung.com/linux/gnu-bsd-stream-editor GNU sed vs. BSD sed], Haidar Ali, 2024 (Accessed: 2025-08-06)</ref> Run <code>sed --version</code> to check for the version and flavour of sed. == Flags and Options == For the full list, consult <code>[[man]] 'sed(1)'</code> or <code>sed --help</code>. {| class="wikitable" |+ Table of Common Command-line Flags & Options |- ! Flag !! Description |- | <code>-n</code> || Suppress printing |- | <code>-e</code> || Multiple commands (e.g., <code>sed -e 's/a/b/' -e 's/c/d/'</code>) |- | <code>-f</code> || Read commands from file |- | <code>-i[SUFFIX]</code> || Edit file in-place. A suffix for the backup file may be provided. |- | <code>-E</code>/<code>-r</code> || Use extended regex |- | <code>-z</code> || Null-terminated lines |} == Syntax == Visit [[Sed/Syntax]] for the in-depth documentation for sed's scripting language. == Examples == Visit [[Sed/Examples]] for different examples with varying complexity. == Advanced Topics == === Performance === Regex is frequently used in sed scripts. As with every other engines, avoid backtracking in regex by limiting matches, e.g., <code>.*</code> vs. <code>[^ ]*</code> when matching until a space potentially. See [[Regular Expression#Optimisation]] for further tips. Additionally, the use of regex greatly affects the performance of the sed script, as showcased by the following simple benchmark: {| class="wikitable" !Command !<code>seq</code> Time !<code>sed</code> Time |- | <syntaxhighlight lang="sh" line> time seq 999999999 | sed ' 15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' > /dev/null </syntaxhighlight> | <code>12.54s user 2.48s system 25% cpu 58.894 total</code> | <code>56.64s user 2.00s system 99% cpu 58.894 total</code> |- | <syntaxhighlight lang="sh" line> time seq 999999999 | sed ' 15~15{s@.\+@FizzBuzz@; b} 3~3{s@.\+@Fizz@; b} 5~5s@.+@Buzz@' > /dev/null </syntaxhighlight> | <code>13.25s user 2.65s system 11% cpu 2:20.58 total</code> | <code>138.01s user 2.15s system 99% cpu 2:20.58 total</code> |- | <syntaxhighlight lang="sh" line> time seq 999999999 | sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' > /dev/null </syntaxhighlight> | <code>14.08s user 2.83s system 9% cpu 2:49.54 total</code> | <code>166.93s user 2.07s system 99% cpu 2:49.54 total</code> |} As opposed to popular beliefs, adding an address filter before an <code>s</code> command does not improve performance: <syntaxhighlight lang="shell-session"> $ time seq 999999999 | sed 's@11@@' > /dev/null seq 999999999 13.87s user 2.87s system 22% cpu 1:15.94 total sed 's@11@@' > /dev/null 73.50s user 2.20s system 99% cpu 1:15.94 total $ time seq 999999999 | sed '/11/s@11@@' > /dev/null seq 999999999 13.89s user 2.79s system 20% cpu 1:21.60 total sed '/11/s@11@@' > /dev/null 79.13s user 2.20s system 99% cpu 1:21.61 total </syntaxhighlight> === Basic Regular Expression === Contrary to expectations, the original flavour of the built-in regular expression is not a subset of the extended flavour. Instead, some tokens (such as <code>\|</code>, <code>\(''group''\)</code>, etc.) require an extra prefixing backslash. Consult the following online documentations for the in-depth overview of the flavour: * https://www.gnu.org/software/sed/manual/html_node/Regular-Expressions.html * https://en.wikibooks.org/wiki/Regular_Expressions/POSIX_Basic_Regular_Expressions Even then, the use of extended regular expression could impact performance (as shown above), so it could be useful to use BRE instead. === Extended Regular Expression === Unlike BRE, ERE comes with syntax closer to conventional regexes. To enable ERE, add the <code>-E</code> flag. === Sandboxing === The <code>--sandbox</code> flag could be useful in cases where untrusted sed scripts need to be executed: --sandbox -- block commands that can affect the system (r/w/W/e) This mode prevents sed scripts from executing commands, read or writing files specified by the scripts. == Troubleshooting == === <code>unterminated `s' command</code> === As the error message suggests, <code>s</code> commands must be terminated with the given delimiter: <syntaxhighlight lang="shell-session"> $ echo 'a foo of chocolate' | sed 's/foo/bar' # Missing final delimiter sed: -e expression #1, char 9: unterminated `s' command $ echo 'a foo of chocolate' | sed 's/foo/bar/' a bar of chocolate $ echo 'a foo of chocolate' | sed 's@a@the' sed: -e expression #1, char 7: unterminated `s' command $ echo 'a foo of chocolate' | sed 's@a@the@' the foo of chocolate </syntaxhighlight> === Greedy Patterns === <syntaxhighlight lang="shell-session"> $ echo "foo bar baz" | sed 's/f.*b/x/' xaz </syntaxhighlight> Some times the unexpected output is obtained due to the pattern matching too greedily. Since both BRE and ERE do not support lazy patterns, a more limiting expression is needed compared to <code>.</code> which matches for all characters: <syntaxhighlight lang="shell-session"> $ echo "foo bar baz" | sed 's/f\w* b/x/' xar baz </syntaxhighlight> == See Also == * [https://learnbyexample.github.io/learn_gnused/ CLI text processing with GNU sed], by Sundeep Agarwal at [https://learnbyexample.github.io learnbyexample.github.io] * [https://en.wikibooks.org/wiki/Sed Sed - Wikibooks, open books for an open world] * [https://www.gnu.org/software/sed/manual/sed.html Official online GNU <code>sed</code> manual] == Related Tools == * [[AWK]]: Process column-based data * [[grep]]: Search for lines in stream using regex * [[perl]]: Programming language for complex text processing == References == e5fb146dca12e4b6c7a104d7746511d8ed4fe916 0 682 3281 3187 2025-08-06T13:27:41Z Satnus 215 Added a "Short Page" Template wikitext text/x-wiki {{Needs Citations}}{{Cleanup | Short page}}{{DistributionInfobox|title=Puppy Linux|image=[[File:Puppy logo.svg|frameless|Puppy Linux Logo]]|caption=Puppy Linux Logo|releasestatus=Maintained|releasemodel=Rolling Release / Stable|packagemanager=[[dpkg]], [[XBPS]], PPM|defaultdesktops=JWM, [[Xfce]], LXDE|usagetype=Desktop|architectures=x86_64, x86, ARM|website=[https://puppylinux-woof-ce.github.io/ Link]}}'''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003. 751d1e651ebe86f489518d7988f8c94cae7802ad 3282 3281 2025-08-06T17:04:29Z Ow0cast 249 tmpl | replace "cleanup|short page" with "stub" wikitext text/x-wiki {{Needs Citations}}{{stub}}{{DistributionInfobox|title=Puppy Linux|image=[[File:Puppy logo.svg|frameless|Puppy Linux Logo]]|caption=Puppy Linux Logo|releasestatus=Maintained|releasemodel=Rolling Release / Stable|packagemanager=[[dpkg]], [[XBPS]], PPM|defaultdesktops=JWM, [[Xfce]], LXDE|usagetype=Desktop|architectures=x86_64, x86, ARM|website=[https://puppylinux-woof-ce.github.io/ Link]}}'''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003. 86060e424c04ca7671f611f9e8ba20dfec168837 2 811 3283 2025-08-06T19:29:24Z Ow0cast 249 idea crafting wikitext text/x-wiki hi c22b5f9178342609428d6f51b2c5af4c0bde6a42 0 779 3284 3158 2025-08-06T19:53:59Z Hetman Foko 221 add SoftwareInfobox; add {history, philosophy, installation, links} sections wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Haskell-Logo.svg]] | title = Haskell | releasestatus = Maintained | lastrelease = GHC 9.12.2 - 22 July 2025 / Haskell2010 | firstrelease = 0.29 - 25 July 1996 / Haskell 1.0 | languages = Haskell | developers = The Haskell Foundation | designed by = ICFP | website = [https://haskell.org haskell.org] }} {{Needs Citations}} '''Haskell''' is a general-purpose, statically typed, purely functional programming language with type inference and lazy evaluation. = History = Functional Programming in the 80's already had its roots in programming - such as the Lisp language. The new idea that sparked creation of multiple functional languages (such as Miranda, SASL, KRC) was lazy evaluation - which later became one of core Haskell ideas. In order to centralize functional programming efforts, multiple conferences (later merged into International Conference on Functional Programming) were held in the 90's. They resulted in creation of '''Haskell'''. = Philosophy = Haskell as a functional language inherits its philosophy from math-oriented subjects such as Lambda Calculus or Category Theory. Despite it's reputation, Haskell doesn't require prior knowledge of those in order to write basic code. = Installation & Usage = Most common Haskell compiler is '''GHC''' - Glasgow Haskell Compiler. Installation process shouldn't be harder than installing `ghc` package with your favorite package manager. GHC provides essential tools, such as `ghc` and `ghci` - the compiler and interpreter. The latter can be used for simple inline operations, which is extremely useful when learning the language. = Useful Links = * [https://learnyouahaskell.github.io/ Learn You A Haskell] is a popular book (with a free online copy) which aims to explain Haskell without requiring prior knowledge in functional programming. * [https://hoogle.haskell.org/ Hoogle] is a Haskell API search engine, helpful in finding libraries etc. [[Category:Programming Languages]] d292c465e43b1752bd4cc095c8352d8c47233d4e 3285 3284 2025-08-06T20:09:24Z Hetman Foko 221 consistent version field wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Haskell-Logo.svg]] | title = Haskell | releasestatus = Maintained | lastrelease = GHC 9.12.2 - 22 July 2025 / Haskell2010 | firstrelease = GHC 0.29 - 25 July 1996 / Haskell 1.0 | languages = Haskell | developers = The Haskell Foundation | designed by = ICFP | website = [https://haskell.org haskell.org] }} {{Needs Citations}} '''Haskell''' is a general-purpose, statically typed, purely functional programming language with type inference and lazy evaluation. = History = Functional Programming in the 80's already had its roots in programming - such as the Lisp language. The new idea that sparked creation of multiple functional languages (such as Miranda, SASL, KRC) was lazy evaluation - which later became one of core Haskell ideas. In order to centralize functional programming efforts, multiple conferences (later merged into International Conference on Functional Programming) were held in the 90's. They resulted in creation of '''Haskell'''. = Philosophy = Haskell as a functional language inherits its philosophy from math-oriented subjects such as Lambda Calculus or Category Theory. Despite it's reputation, Haskell doesn't require prior knowledge of those in order to write basic code. = Installation & Usage = Most common Haskell compiler is '''GHC''' - Glasgow Haskell Compiler. Installation process shouldn't be harder than installing `ghc` package with your favorite package manager. GHC provides essential tools, such as `ghc` and `ghci` - the compiler and interpreter. The latter can be used for simple inline operations, which is extremely useful when learning the language. = Useful Links = * [https://learnyouahaskell.github.io/ Learn You A Haskell] is a popular book (with a free online copy) which aims to explain Haskell without requiring prior knowledge in functional programming. * [https://hoogle.haskell.org/ Hoogle] is a Haskell API search engine, helpful in finding libraries etc. [[Category:Programming Languages]] f4f2986995b495694a261239ce4cd2c944f43ad5 0 812 3289 2025-08-07T16:15:18Z Madonuko 140 init wikitext text/x-wiki For the main page, visit [[sed]]. The general syntax in sed is: ''<address#1>''{''<command#1>''; ''<command#2>''; ...} While at least 1 command is needed, addresses are optional; specifying no commands does not alter the text stream in most cases. If a filter corresponds to only 1 command, the braces can be omitted: ''<address#1><command#1>'' To specify multiple commands, separate them with new lines. Most commands also allow separation by semicolons (<code>;</code>), but ''greedy'' commands such as <code>c</code> and <code>i</code> take in the semicolons and the rest of the line, and thus cannot be separated with semicolons. == Commands == * <code>s/''<regex>''/''<replacement>''/''<flags>''</code> performs '''substitution'''. The <code>g</code> flag replaces all matches per line; without it, only the first match is replaced. Other flags: <code>\1,\2,...</code> (The ''n''-th regex group), <code>p</code> (print on replace), <code>i</code> (case-insensitive), <code>w ''<file>''</code> (write to file). ** e.g.: <code>sed 's/red/blue/g'</code> replaces all “red” with “blue” (including in “Fred” → “Fblue”). ** e.g.: <code>sed 's:\bdog\b:cat:g'</code> replaces whole words “dog” with “cat”. * <code>d</code> '''deletes''' the current pattern space. Often used with addresses. ** e.g.: <code>sed '/error/d'</code> deletes lines containing “error”. ** e.g.: <code>sed '3,7d'</code> deletes lines 3 to 7. * <code>p</code> '''prints''' the current pattern space. Usually combined with <code>-n</code> to suppress automatic printing. ** e.g.: <code>sed -n '/important/p'</code> prints only lines containing “important”. * <code>a ''<text>''</code> '''appends''' ''<text>'' after the current line. Text continues until a newline not escaped with <code>\</code>. ** e.g.: <code>sed '3a\New Line'</code> appends “New Line” after line 3. This is the same as <code>sed '3a New Line'</code> * <code>i ''<text>''</code> '''inserts''' ''<text>'' before the current line. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” before line 1. * <code>c ''<text>''</code> '''changes''' the current line to ''<text>''. ** e.g.: <code>sed '/old/c\new content'</code> replaces lines matching “old” with “new content”. * <code>y/''<src-chars>''/''<dest-chars>''/</code> '''transliterates''' characters one-to-one (like <code>tr</code>). ** e.g.: <code>sed 'y/abc/ABC/'</code> converts ‘a’→‘A’, ‘b’→‘B’, ‘c’→‘C’. * <code>q [''<exit-code>'']</code> '''quits''' processing immediately. With address, exits after processing that line. ** e.g.: <code>sed '5q'</code> processes only the first 5 lines. * <code>r ''<file>''</code> '''reads''' a file and appends its content after the current line. ** e.g.: <code>sed '/End/r data.txt'</code> inserts contents of “data.txt” after lines containing “End”. * <code>w ''<file>''</code> '''writes''' the current pattern space to ''<file>''. ** e.g.: <code>sed '/important/w log.txt'</code> saves lines with “important” to “log.txt”. * <code>=</code> prints the '''current line number''' to stdout. ** e.g.: <code>sed -n '/pattern/='</code> prints line numbers containing “pattern”. * <code>n</code> '''next''' line: replaces pattern space with next input line, skip remaining commands. ** e.g.: <code>sed 'n;d'</code> deletes every *even*-numbered line. * <code>N</code> '''appends next line''' to pattern space (with embedded newline). Useful for multiline processing. ** e.g.: <code>sed 'N;s/\n/ /'</code> joins every two consecutive lines. * <code>P</code> prints the first part (up to newline) of the pattern space. Used after <code>N</code>. ** e.g.: <code>sed -n 'N;P'</code> prints only the first line of each pair. * <code>D</code> deletes the first part (up to newline) of the pattern space. Restarts cycle if content remains. ** e.g.: <code>sed 'N;/error/D'</code> deletes leading lines in a pair if “error” is found. * <code>h</code> copies pattern space to '''hold space''' (overwriting). <code>H</code> appends with newline. * <code>g</code> copies hold space to pattern space (overwriting). <code>G</code> appends with newline. ** e.g.: <code>sed -n '/start/{h; /end/{g; p}}'</code> prints lines between “start” and “end” inclusively. * <code>x</code> '''exchanges''' hold space and pattern space. ** e.g.: <code>sed '/swap/{x;p;x}'</code> prints hold space when “swap” is matched. * <code>l</code> prints pattern space in '''unambiguous form''' (non-printable as hex, wraps long lines). ** e.g.: <code>sed -n l</code> shows hidden characters. * <code>: ''<label>''</code> defines a label for branching. Requires a single colon. * <code>b ''<label>''</code> branches to ''<label>'' (or end of script if no label). * <code>t ''<label>''</code> branches to ''<label>'' only if a substitution succeeded since last input line or <code>t</code>. ** e.g.: <code>sed ':a; s/foo/bar/; ta; s/baz/qux/'</code> repeatedly replaces “foo” until none remain, then replaces “baz”. * <code>e [''<command>'']</code> '''executes''' a command and sends output to output stream. Without argument, executes pattern space. ** e.g.: <code>sed 's/.*/date +%s/e'</code> replaces each line with the current Unix timestamp. * <code>F</code> prints the '''filename''' being processed (useful with multiple files). ** e.g.: <code>sed -n F *.log</code> prints all filenames in a directory. * <code>Q [''<exit-code>'']</code> quits without printing pattern space (like <code>q</code> but silent). ** e.g.: <code>sed '/match/Q42'</code> exits with code 42 upon first “match”. * <code>v ''<version>''</code> fails if <code>sed</code> version is less than ''<version>'' (e.g., <code>v 4.2</code>). * <code>z</code> '''zaps''' (empties) the pattern space. Useful for multiline processing. ** e.g.: <code>sed '/pattern/{z;d}'</code> deletes lines after “pattern” is found. * <code>#</code> denotes a '''comment''' until next newline. ** e.g.: <code>sed 's/A/B/ # Replace A'</code> ignores text after <code>#</code>. * <code>{ }</code> groups commands into a block. Must appear as separate commands. ** e.g.: <code>sed '/start/{s/A/B/; s/C/D/}'</code> applies substitutions only to lines containing “start”. * <code>T ''<label>''</code> branches to ''<label>'' only if ''no'' substitutions succeeded since last input line or <code>T</code> (opposite of <code>t</code>). ; Notes # Most commands accept [[Sed#Addresses|addresses]] (e.g., <code>''<start>'',''<end>''</code> or <code>/''<regex>''/</code>) to restrict operation. # <code>a</code>, <code>i</code>, and <code>c</code> are “greedy” — text arguments span lines until an unescaped newline. #* To use multiple commands, separate each command with a new line. Input a new line in a shell by pressing {{Key press|Esc}} and then {{Key press|Enter}} separately. # '''Hold space''' commands (<code>h</code>, <code>g</code>, etc.) enable advanced stateful operations. # Frequency ranking is estimated based on common use cases (e.g., <code>s</code> is most frequent). == Addresses == * <code>/''<regex>''/</code> selects lines matching a [[regular expression]] pattern. Used to filter lines for command application. ** e.g.: <code>sed -n '/error/p'</code> prints lines containing “error”. ** e.g.: <code>sed '/^#/d'</code> deletes comment lines starting with <code>#</code>. ** In case a different delimiter needs to be used, the starting character needs to be escaped by a backslash like so: <code>\!/usr/include/[^/]+\.h!</code> * <code>''<n>''</code> targets a '''specific line number'''. ** e.g.: <code>sed '42s/old/new/'</code> replaces “old” with “new” only on line 42. ** e.g.: <code>sed '1i\Header'</code> inserts “Header” ''before'' line 1. ** <code>0</code> and <code>$</code> refers to the start and the end of the file. * <code>''<start>'',''<end>''</code> operates on lines '''from <code>''start''</code> to <code>''end''</code>''' (inclusive). Numbers, [[regex]]es, or <code>$</code> ([[EOF]]) allowed. ** e.g.: <code>sed '10,20d'</code> deletes lines 10–20. ** e.g.: <code>sed '5,$s/foo/bar/'</code> substitutes “foo” → “bar” from line 5 to EOF. ** e.g.: <code>sed -n '/error/,$p'</code> prints from first “error” to EOF. * <code>!</code> applies commands to lines '''NOT''' matching the address. ** e.g.: <code>sed '/pattern/!d'</code> deletes lines ''not'' containing “pattern”. ** e.g.: <code>sed '3,5!s/foo/bar/'</code> substitutes “foo” → “bar” ''except'' on lines 3–5. * <code>''<address>'',+''<n>''</code> selects address plus <code>''n''</code> following lines (GNU Extension) ** e.g.: <code>sed '/START/,+3d'</code> deletes “START” line + next 3 lines ** e.g.: <code>sed '10,+5s/foo/bar/'</code> substitutes in lines 10–15 * <code>''<start>''~''<step>''</code> selects every <code>''step''</code> lines starting at <code>''start''</code> (GNU Extension) ** e.g.: <code>sed '1~2d'</code> deletes every odd line (1,3,5...) ** e.g.: <code>sed '2~5s/^/# /'</code> comments lines 2,7,12,17... {| class="wikitable" |+Summary Table of sed Address Types !Type !Syntax !Example !Explanation |- |Regex |<code>/pattern/</code> |<code>sed '/foo/d'</code> |Delete lines containing “error” |- |Single Line |<code>5</code> |<code>sed '5q'</code> |Quit after line 5 |- |Regex Range |<code>/a/,/b/</code> |<code>sed '/start/,/end/p'</code> |Print between markers |- |Line Range |<code>3,7</code> |<code>sed '3,7s/a/b/'</code> |Substitute in lines 3–7 |- |Step |<code>start~step</code> |<code>sed '1~3d'</code> |Delete every 3rd line starting at 1 |- |Offset |<code>addr,+n</code> |<code>sed '/err/,+2d'</code> |Delete error line + next 2 lines |- |Special |<code>0</code>, <code>$</code> |<code>sed '$s/old/new/'</code> |Substitute in last line |- |Combined |<code>5,/x/</code> |<code>sed '5,/end/d'</code> |Delete from line 5 to next “end” |- |Negation |<code>!</code> |<code>sed '/keep/!d'</code> |Delete lines not containing “keep” |} 249b5c577c4aadf9e7e81c6f3ccd281cce982b7a 0 813 3291 2025-08-07T16:15:49Z Madonuko 140 init wikitext text/x-wiki For the main page, visit [[sed]]. This page showcases different example usecases with sed, with varying complexity. == Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags == Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''[[sed#Extended Regular Expression|extended regular expression]]''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> == FizzBuzz == FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == Renaming Files == Multiple files can be renamed if the new name can be easily systematically determined from the old name: <syntaxhighlight lang="sh"> ls *.txt | sed 's/\(.*\)\.txt/mv & \1_old.txt/' | sh </syntaxhighlight> The commands could also be executed within sed: <syntaxhighlight lang="sh"> ls *.txt | sed 's/\(.*\)\.txt/mv & \1_old.txt/e' </syntaxhighlight> ef653a8b4a19f47be702df4e63b90267a03f3c62 3292 3291 2025-08-07T16:17:53Z Madonuko 140 /* References */ wikitext text/x-wiki For the main page, visit [[sed]]. This page showcases different example usecases with sed, with varying complexity. == Replace <code>`backticks`</code> with <code><nowiki><code></nowiki></code> Tags == Suppose the working [[directory]] contains the file <code>file.txt</code>: `sed` is a very powerful text processor. It is commonly used to perform text transformations. `sed` is inspired by `grep`. First, the texts wrapped around backticks can be obtained using the <code>-E</code> flag, which enables ''[[sed#Extended Regular Expression|extended regular expression]]''<ref>[https://www.man7.org/linux/man-pages/man1/sed.1.html sed(1) - Linux manual page], man7.org, 2022 (Accessed: 2025-06-20)</ref> (aka. ''regex''). $ sed -E 's/`.+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND. The <code>g</code> flag (''global'') performs the substitution infinitely many times instead of just once for each line. Notice the last line is not matched correctly since <code>.+</code> is ''greedily evaluated''<ref>[https://www.computerworld.com/article/1392270/regular-expression-tutorial-part-5-greedy-and-non-greedy-quantification.html Regular Expression Tutorial Part 5: Greedy and Non-Greedy Quantification], Andrew Johnson, 2001 (Accessed: 2025-06-20)</ref>. This can be resolved by using <code>[^`]</code>, which matches all characters except <code>`</code>, instead of <code>.</code> which matches all characters: $ sed -E 's/`[^`]+`/FOUND/g' file.txt FOUND is a very powerful text processor. It is commonly used to perform text transformations. FOUND is inspired by FOUND. Next, we add regex group 1 to the inner texts wrapped inside the backticks, and set the replacement text to <code><nowiki><code>\1</code></nowiki></code>. <code>\1</code> expands to the content of regex group 1. <nowiki> $ sed -E 's/`([^`]+)`/<code>\1</code>/g' file.txt</nowiki> sed: -e expression #1, char 23: unknown option to `s' The error occurs because the replacement text contains the character <code>/</code>, which is used as the separator for the <code>s</code> command. The desired result can be obtained by escaping it using a backslash: <nowiki> $ sed -E 's/`([^`]+)`/<code>\1<\/code>/g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Alternatively, we can change the separator to <code>@</code>: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' file.txt</nowiki> <nowiki><code>sed</code> is a very powerful text processor.</nowiki> <nowiki>It is commonly used to perform text transformations.</nowiki> <nowiki><code>sed</code> is inspired by <code>grep</code>.</nowiki> Finally, we can use the <code>-i</code> flag to edit the file directly: <nowiki> $ sed -E 's@`([^`]+)`@<code>\1</code>@g' -i file.txt</nowiki> == FizzBuzz == FizzBuzz is a famous problem that involves 4 rules: # if a number is divisible by 15, print <code>FizzBuzz</code>; # if a number is divisible by 3, print <code>Fizz</code>; # if a number is divisible by 5, print <code>Buzz</code>; # otherwise, print the number itself. In this example, FizzBuzz is performed on the first 50 positive integers, which are prepared with <code>seq 50</code>. The numbers can be further processed by checking whether the line number is a multiple of 15, 3, or 5: <syntaxhighlight lang="sh" line copy> sed -E ' 15~15{s@.+@FizzBuzz@; b} 3~3{s@.+@Fizz@; b} 5~5s@.+@Buzz@' </syntaxhighlight> <code>~15</code> performs the specified command following itself every 15 lines. The <code>15</code> before the <code>~</code> sign indicates which line to start counting. In this case, <code>s@.+@FizzBuzz@; b</code> is performed every 15 lines starting with the 15th line. <code>s@.+@FizzBuzz@</code> performs a substitution. With the <code>-E</code> flag, the regex <code>.+</code> can be used to match for the entire line. The entire line is then replaced with <code>FizzBuzz</code>. Finally, the <code>b</code> command (<code>b</code> stands for ''branch'') tells sed to skip the remaining commands and process the next line. The same is done for line numbers divisible by 3 and 5. Note that for <code>5~5s@.+@Buzz@</code>, <code>b</code> is no longer needed since all conditions have already been processed. The commands can be further improved by using <code>c</code> (which stands for ''change''): <syntaxhighlight lang="sh" line copy> sed '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' </syntaxhighlight> Note the lack of <code>-E</code> since regexes are no longer in use. And finally, <code>pr -5t</code> prints out the results in 5 columns. The full command is now: <syntaxhighlight lang="sh" line copy> seq 50 | sed -E '15~15c FizzBuzz 3~3c Fizz 5~5c Buzz' | pr -5t </syntaxhighlight> The output is: 1 11 Fizz 31 41 2 Fizz 22 32 Fizz Fizz 13 23 Fizz 43 4 14 Fizz 34 44 Buzz FizzBuzz Buzz Buzz FizzBuzz Fizz 16 26 Fizz 46 7 17 Fizz 37 47 8 Fizz 28 38 Fizz Fizz 19 29 Fizz 49 Buzz Buzz FizzBuzz Buzz Buzz == Renaming Files == Multiple files can be renamed if the new name can be easily systematically determined from the old name: <syntaxhighlight lang="sh"> ls *.txt | sed 's/\(.*\)\.txt/mv & \1_old.txt/' | sh </syntaxhighlight> The commands could also be executed within sed: <syntaxhighlight lang="sh"> ls *.txt | sed 's/\(.*\)\.txt/mv & \1_old.txt/e' </syntaxhighlight> == References == 28ca45389e85f29f2a3b035f718c5e9bf71b0c8c 0 670 3293 2997 2025-08-07T17:53:19Z Madonuko 140 /* Flavours */ & /* Optimisation */ wikitext text/x-wiki '''Regular Expression''', also known as '''Regex''' or '''RegExp''', refers to a type of pattern “used to match character combinations in strings”<ref>[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript], MDN, 2025 (Accessed 2025-06-20)</ref>. It is a very powerful tool for searching, matching, replacing, and parsing target text based on specific patterns. In other words, a ''regex engine''<ref>[https://www.regular-expressions.info/engine.html How a Regex Engine Works Internally], Jan Goyvaerts, 2019 (Accessed: 2025-06-20)</ref> can find, extract and substitute target text under a format defined by a given regex. Regex is not universally the same. Different flavours of regex are supported by different regex engines provided by different libraries and programming languages. However, a portion of the syntax is generally the same across them.<ref>[https://regex101.com/ regex101: build, test, and debug regex], regex101.com, 2025 (Accessed: 2025-06-20)</ref> == Usage == Regex is used in many text processing tools. Graphical examples include the find and replace feature in [[LibreOffice]]<ref>[https://help.libreoffice.org/25.2/en-US/text/swriter/guide/search_regexp.html?&DbPAR=SHARED&System=UNIX Using Regular Expressions in Text Searches], LibreOffice, 2025 (Accessed: 2025-06-20)</ref>. [[CLI|Command line]] examples include [[AWK]], [[sed]], and [[grep]]. Many popular scripting and programming languages provide built-in support for regex, notably [[JavaScript]], [[Perl]], [[Java]], [[Ruby]], [[Python]], [[C++]], [[PHP]], each with slighting varying implementations and different sets of supported syntax.<ref>[https://www.regular-expressions.info/tools.html Popular Tools, Utilities and Programming Languages That Support Regular Expressions], Jan Goyvaerts, 2021 (Accessed: 2025-06-21)</ref> == Flavours == === Basic Regular Expression === See [https://en.wikibooks.org/wiki/Regular_Expressions/POSIX_Basic_Regular_Expressions Regular Expressions/POSIX Basic Regular Expressions] from Wikibooks for more details. In short, '''Basic Regular Expression''' (BRE) is a notable variant of regex used across different [[POSIX]] utilities, notably in [[sed#Basic Regular Expression]] and [[grep#Basic Regular Expression]]. Unlike other mainstream flavours, BRE requires backslashes to escape many of the common regex symbols and patterns, such as <code>\(''capture groups''\)</code> and repeaters like <code>\{1, 2\}</code>. Implementations of BRE may also vary across different vendors. For example, GNU extensions like <code>\?</code> and <code>\+</code> are introduced into GNU sed.<ref>[https://www.gnu.org/software/sed/manual/html_node/Regular-Expressions.html Regular Expressions - sed, a stream editor], GNU (Accessed: 2025-08-08)</ref>. === Extended Regular Expression === See [https://en.wikibooks.org/wiki/Regular_Expressions/POSIX-Extended_Regular_Expressions Regular Expression/POSIX-Extended Regular Expressions] from Wikibooks for more details. As the name suggests, '''Extended Regular Expression''' (ERE) is a POSIX extension for POSIX-compliant software to process more sophisticated regular expressions. While programs like [[AWK]] support ERE by default, others like sed and grep require an extra <code>-E</code> command-line flag. ERE is closer to other mainstream flavours in the sense that the backslash prefixes to the aforementioned patterns are removed. In addition, crucial and common patterns like <code>+</code> are introduced into ERE. == Optimisation == === Prefer Lazy Quantifiers === Greedy quantifiers such as <code>.+</code> force engines to perform ''backtracking'', where it go back each character one by one to check whether the current largest string matches the regex. In comparison, lazy quantifier allow engines to immediately process the next pattern once a match is found, because it is not required to determine whether there is a larger match. Consider the test string <code>foo bar baz</code> and the regex <code>/f.*? bar/</code>. After finding <code>f</code>, the engine accept anything until it finds a <code> bar</code> suffix. This operation is ''O(n)'' because even if the suffix fails to match, it can just continue until the matching suffix arrives. It takes a PCRE2-flavoured engine 9 steps to correctly match the string.<ref>[https://regex101.com/r/GIFDjf/2/debugger regex101: lazy match for foo bar baz], regex101, 2025-08-08 (Accessed: 2025-08-08)</ref> In contrary, <code>/f.* bar/</code> takes the same engine 18 moves instead.<ref>[https://regex101.com/r/BY5U8b/1/debugger regex101: greedy match for foo bar baz], regex101, 2025-08-08 (Accessed: 2025-08-08)</ref> The engine is required to take all characters until the end, and then, in backwards, match each character to check whether there is a valid suffix. This is done to ensure <code>.*</code> matches the largest possible portion in the test string. This operation is thus ''O(n²)'' in the worst case scenario, and is how the phrase “''catastrophic backtracking''” is born.<ref>[https://www.regular-expressions.info/catastrophic.html Runaway Regular Expressions: Catastrophic Backtracking], Jan Goyvaerts, 2021 (Accessed: 2025-08-08)</ref><ref>[https://regex101.com/r/iXSKTs/1/debugger regex101: Catastrophic backtracking example], elm, 2018-05-16 (Accessed: 2025-08-08)</ref><ref>[https://www.w3docs.com/learn-javascript/catastrophic-backtracking.html Catastrophic Backtracking], W3docs (Accessed: 2025-08-08)</ref> === Limit Matches === Adding anchors to regexes may speed up the matching process so that the engine does not need to check for every character in the test string.<ref>[https://jsdev.space/howto/optimize-regex/ Optimizing Regex for Better Performance], JSDev Space, 2025-01-03 (Accessed: 2025-08-08)</ref> Common anchors include <code>^</code> (start of line) and <code>$</code> (end of line) in multi-line mode. Other checks like <code>\b</code> (word boundary) could serve similar purposes.<ref>[https://www.loggly.com/blog/five-invaluable-techniques-to-improve-regex-performance/ Five Invaluable Techniques to Improve Regex Performance], Liz Bennett, 2015-06-30 (Accessed: 2025-08-08)</ref> On the other hand, adding more complicated checks like lookahead checks could speed up or slow down<ref>[https://last9.io/blog/regex-optimization-techniques/#technique-10-use-lookaheadslookbehinds-judiciously Regex Optimization Techniques: 14 Methods for DevOps Performance | Last9], Anjali Udasi, 2025-04-10 (Accessed: 2025-08-08)</ref> the engine. === Approximate Optimisation === When processing large files, it could be beneficial to split a regex into 2 different regexes to improve the pipeline. This allows approximate optimisation, which is an advanced technique for reducing the time needed to find matches within large test strings: <syntaxhighlight lang="sh"> # Slow: Check 'cat' / 'dog' / 'bird' sed -nE 's/(cat|dog|bird)/animal/gp' large_file.txt # Faster: Check single characters first grep '[cdb][aoi][tgr]' large_file.txt | sed -nE 's/(cat|dog|bird)/animal/gp' </syntaxhighlight> This does not always create improvements, so make sure to perform benchmarks before implementing this optimisation. == See Also == * [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript | MDN] * [https://regex101.com/ regex101: build, test, and debug regex] == References == [[Category:Terminology]] 828cec9ca23e9d1d76ebe98c00e1fba2edc71618 0 558 3294 2998 2025-08-07T17:58:45Z Hetman Foko 221 conventional git ignore filename wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[C]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }}Rust, the programming language, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called "garbage collecting," where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety|# Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[Rust#Object-Orientated Programming in Rust|# Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├─src ; Contain all code for project | ├──main.rs ; Code is executed here ├─Cargo.toml ; Dependencies file ├─.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!") } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { let var_name: i32 = 64; let mut another_var: i32 = 86; another_var = 128; // let declares a new variable, i32 is the type of the variable // but is not requred, then the value is given. // All variables end with a ";" } </syntaxhighlight>Using <code>let</code> defines a new variable. You are able to label the variable however you like; but, it is a good idea to give them simple and easy names for sake of other programmers and yourself. If you need to specify the type of value a variable is, you can write out <code>[var_name]: [type]</code> to declare a type, to see all types, see [[Rust#Variable Types|# Variable Types]]. By default, any variable defined is an '''immutable''' but using the <code>mut</code> term enables the variable to mutable, influenced by '''functional programming'''. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" line="1"> struct Values { Value1: bool, Value2: i32, Value3: String, // Value 4..., Value 5... } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: Values = Values { Value1: true, Value2: 64, Value3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { Length: i32, Width: i32, Height: i32 } // vvvvvv Cube implemented here vvvvvv impl Cube { fn Area(&self) -> i32 { self.Length * self.Width * self.Height // This returns the Cube's Volume } } fn main() { let RubiksCube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's Volume: {}", RubiksCube.Area()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an Area finder function within the <code>impl Cube</code> scope. We are able to use the <code>Area()</code> function on any Variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses "borrowing"; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing], Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == [[Category:Programming Languages]] 25bd9e9eb2ae7923a8af7b030f0702c2b09108dd 3296 3294 2025-08-07T18:21:31Z Madonuko 140 /* Syntax, Features, and More */ fix fs tree wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[C]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }}Rust, the programming language, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called "garbage collecting," where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety|# Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[Rust#Object-Orientated Programming in Rust|# Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!") } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { let var_name: i32 = 64; let mut another_var: i32 = 86; another_var = 128; // let declares a new variable, i32 is the type of the variable // but is not requred, then the value is given. // All variables end with a ";" } </syntaxhighlight>Using <code>let</code> defines a new variable. You are able to label the variable however you like; but, it is a good idea to give them simple and easy names for sake of other programmers and yourself. If you need to specify the type of value a variable is, you can write out <code>[var_name]: [type]</code> to declare a type, to see all types, see [[Rust#Variable Types|# Variable Types]]. By default, any variable defined is an '''immutable''' but using the <code>mut</code> term enables the variable to mutable, influenced by '''functional programming'''. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" line="1"> struct Values { Value1: bool, Value2: i32, Value3: String, // Value 4..., Value 5... } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: Values = Values { Value1: true, Value2: 64, Value3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { Length: i32, Width: i32, Height: i32 } // vvvvvv Cube implemented here vvvvvv impl Cube { fn Area(&self) -> i32 { self.Length * self.Width * self.Height // This returns the Cube's Volume } } fn main() { let RubiksCube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's Volume: {}", RubiksCube.Area()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an Area finder function within the <code>impl Cube</code> scope. We are able to use the <code>Area()</code> function on any Variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses "borrowing"; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing], Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == [[Category:Programming Languages]] 7c62e3145cb880ca7efe4c1d8798d3b4503db15a 3297 3296 2025-08-07T18:33:30Z Madonuko 140 I thought I was looking at C# what the fuck is this monstrosity wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[C]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called “garbage collecting,” where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[#Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" lines> struct MyStruct { field1: bool, field2: i32, field3: String, } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: MyStruct = MyStruct { field1: true, field2: 64, field3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height // This returns the Cube's Volume } } fn main() { let rubiks_cube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's volume: {}", rubiks_cube.volume()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an area finder function within the <code>impl Cube</code> scope. We are able to use the <code>volume()</code> method on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing], Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == [[Category:Programming Languages]] 7e2b067301fe59a9ea0a2adabb376dc4f253d456 0 670 3295 3293 2025-08-07T18:17:00Z Madonuko 140 /* Atomic Grouping */ & /* Possessive Quantifiers */ wikitext text/x-wiki '''Regular Expression''', also known as '''Regex''' or '''RegExp''', refers to a type of pattern “used to match character combinations in strings”<ref>[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript], MDN, 2025 (Accessed 2025-06-20)</ref>. It is a very powerful tool for searching, matching, replacing, and parsing target text based on specific patterns. In other words, a ''regex engine''<ref>[https://www.regular-expressions.info/engine.html How a Regex Engine Works Internally], Jan Goyvaerts, 2019 (Accessed: 2025-06-20)</ref> can find, extract and substitute target text under a format defined by a given regex. Regex is not universally the same. Different flavours of regex are supported by different regex engines provided by different libraries and programming languages. However, a portion of the syntax is generally the same across them.<ref>[https://regex101.com/ regex101: build, test, and debug regex], regex101.com, 2025 (Accessed: 2025-06-20)</ref> == Usage == Regex is used in many text processing tools. Graphical examples include the find and replace feature in [[LibreOffice]]<ref>[https://help.libreoffice.org/25.2/en-US/text/swriter/guide/search_regexp.html?&DbPAR=SHARED&System=UNIX Using Regular Expressions in Text Searches], LibreOffice, 2025 (Accessed: 2025-06-20)</ref>. [[CLI|Command line]] examples include [[AWK]], [[sed]], and [[grep]]. Many popular scripting and programming languages provide built-in support for regex, notably [[JavaScript]], [[Perl]], [[Java]], [[Ruby]], [[Python]], [[C++]], [[PHP]], each with slighting varying implementations and different sets of supported syntax.<ref>[https://www.regular-expressions.info/tools.html Popular Tools, Utilities and Programming Languages That Support Regular Expressions], Jan Goyvaerts, 2021 (Accessed: 2025-06-21)</ref> == Flavours == === Basic Regular Expression === See [https://en.wikibooks.org/wiki/Regular_Expressions/POSIX_Basic_Regular_Expressions Regular Expressions/POSIX Basic Regular Expressions] from Wikibooks for more details. In short, '''Basic Regular Expression''' (BRE) is a notable variant of regex used across different [[POSIX]] utilities, notably in [[sed#Basic Regular Expression]] and [[grep#Basic Regular Expression]]. Unlike other mainstream flavours, BRE requires backslashes to escape many of the common regex symbols and patterns, such as <code>\(''capture groups''\)</code> and repeaters like <code>\{1, 2\}</code>. Implementations of BRE may also vary across different vendors. For example, GNU extensions like <code>\?</code> and <code>\+</code> are introduced into GNU sed.<ref>[https://www.gnu.org/software/sed/manual/html_node/Regular-Expressions.html Regular Expressions - sed, a stream editor], GNU (Accessed: 2025-08-08)</ref>. === Extended Regular Expression === See [https://en.wikibooks.org/wiki/Regular_Expressions/POSIX-Extended_Regular_Expressions Regular Expression/POSIX-Extended Regular Expressions] from Wikibooks for more details. As the name suggests, '''Extended Regular Expression''' (ERE) is a POSIX extension for POSIX-compliant software to process more sophisticated regular expressions. While programs like [[AWK]] support ERE by default, others like sed and grep require an extra <code>-E</code> command-line flag. ERE is closer to other mainstream flavours in the sense that the backslash prefixes to the aforementioned patterns are removed. In addition, crucial and common patterns like <code>+</code> are introduced into ERE. == Optimisation == === Prefer Lazy Quantifiers === Greedy quantifiers such as <code>.+</code> force engines to perform ''backtracking'', where it go back each character one by one to check whether the current largest string matches the regex. In comparison, lazy quantifier allow engines to immediately process the next pattern once a match is found, because it is not required to determine whether there is a larger match. Consider the test string <code>foo bar baz</code> and the regex <code>/f.*? bar/</code>. After finding <code>f</code>, the engine accept anything until it finds a <code> bar</code> suffix. This operation is ''O(n)'' because even if the suffix fails to match, it can just continue until the matching suffix arrives. It takes a PCRE2-flavoured engine 9 steps to correctly match the string.<ref>[https://regex101.com/r/GIFDjf/2/debugger regex101: lazy match for foo bar baz], regex101, 2025-08-08 (Accessed: 2025-08-08)</ref> In contrary, <code>/f.* bar/</code> takes the same engine 18 moves instead.<ref>[https://regex101.com/r/BY5U8b/1/debugger regex101: greedy match for foo bar baz], regex101, 2025-08-08 (Accessed: 2025-08-08)</ref> The engine is required to take all characters until the end, and then, in backwards, match each character to check whether there is a valid suffix. This is done to ensure <code>.*</code> matches the largest possible portion in the test string. This operation is thus ''O(n²)'' in the worst case scenario. An even worse example like <code>(x+x+)+y</code><ref>[https://regex101.com/r/iXSKTs/1/debugger regex101: Catastrophic backtracking example], elm, 2018-05-16 (Accessed: 2025-08-08)</ref> have an even worse exponential complexity of ''O(2ⁿ)''.<ref>[https://www.regular-expressions.info/catastrophic.html Runaway Regular Expressions: Catastrophic Backtracking], Jan Goyvaerts, 2021 (Accessed: 2025-08-08)</ref> These examples are how the phrase “''catastrophic backtracking''” was born.<ref>[https://www.w3docs.com/learn-javascript/catastrophic-backtracking.html Catastrophic Backtracking], W3docs (Accessed: 2025-08-08)</ref> === Limit Matches === Adding anchors to regexes may speed up the matching process so that the engine does not need to check for every character in the test string.<ref name=":0">[https://jsdev.space/howto/optimize-regex/ Optimizing Regex for Better Performance], JSDev Space, 2025-01-03 (Accessed: 2025-08-08)</ref> Common anchors include <code>^</code> (start of line) and <code>$</code> (end of line) in multi-line mode. Other checks like <code>\b</code> (word boundary) could serve similar purposes.<ref>[https://www.loggly.com/blog/five-invaluable-techniques-to-improve-regex-performance/ Five Invaluable Techniques to Improve Regex Performance], Liz Bennett, 2015-06-30 (Accessed: 2025-08-08)</ref> On the other hand, adding more complicated checks like lookahead checks could speed up<ref name=":0" /> or slow down<ref>[https://last9.io/blog/regex-optimization-techniques/#technique-10-use-lookaheadslookbehinds-judiciously Regex Optimization Techniques: 14 Methods for DevOps Performance | Last9], Anjali Udasi, 2025-04-10 (Accessed: 2025-08-08)</ref> the engine. === Atomic Grouping === The <code>(?>''atomic group'')</code> reduces backtracking by forcing the engine to discard all backtracking positions in the group after leaving the group.<ref>[https://www.regular-expressions.info/atomic.html Atomic Grouping], Jan Goyvaerts, 2022-11-21 (Accessed: 2025-08-08)</ref> === Possessive Quantifiers === Possessive quantifiers including <code>*+</code>,<code>++</code>, etc. are basically syntactic sugar for greedy quantifiers within an atomic group.<ref>[https://www.regular-expressions.info/possessive.html Possessive Quantifiers], Jan Goyvaerts, 2022-11-21 (Accessed: 2025-08-08)</ref> === Approximate Optimisation === When processing large files, it could be beneficial to split a regex into 2 different regexes to improve the pipeline. This allows approximate optimisation, which is an advanced technique for reducing the time needed to find matches within large test strings: <syntaxhighlight lang="sh"> # Slow: Check 'cat' / 'dog' / 'bird' sed -nE 's/(cat|dog|bird)/animal/gp' large_file.txt # Faster: Check single characters first grep '[cdb][aoi][tgr]' large_file.txt | sed -nE 's/(cat|dog|bird)/animal/gp' </syntaxhighlight> This does not always create improvements, so make sure to perform benchmarks before implementing this optimisation. == See Also == * [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript | MDN] * [https://regex101.com/ regex101: build, test, and debug regex] == References == [[Category:Terminology]] 1d5196474f46436718bfca343082970c29f67e4c 0 674 3298 3040 2025-08-07T18:49:07Z Madonuko 140 better syntaxhighlight wikitext text/x-wiki {{DISPLAYTITLE:grep}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Grep_help_grep.png|frameless]] | caption = Searching for “PATTERNS” or “regex” in <code>grep --help</code> | title = <code>grep</code> | releasestatus = Maintained | lastrelease = 3.12 (2025-04-10) | languages = [[C]] | developers = GNU grep: GNU Project, et al. | website = https://www.gnu.org/software/grep/ }} '''<code>grep</code>''' (''global regular expression print'') is a fundamental [[CLI|command-line]] utility in [[UNIX|Unix-like]] [[Operating System|operating systems]], designed to “[search] plain-text data sets for lines matching a [[regular expression]]”<ref>[https://knot.math.usf.edu/software/dnagrep/grep/wikipedia_snapshot_for_grep.html Wikipedia Snapshot for grep], knot.math.usf.edu, 2012 (Accessed 2025-06-21)</ref><ref name=":0">[https://en.wikipedia.org/wiki/Grep grep], Wikipedia, 2025 (Accessed 2025-06-21)</ref>. == History == Developed by Ken Thompson at Bell Labs in 1973 for Unix, grep's creation stemmed from Thompson's need to analyse text in ''The Federalist Papers'' for authorship attribution. To handle large files efficiently, he extracted the regex code from the [[ed]] text editor into a standalone tool. He named the tool ''grep'' because in ed, the command <code>g/re/p</code> prints out all lines that match the pattern <code>re</code>.<ref name=":0" /> == Usage == === Basic Search === From <code>grep --help</code>: Usage: grep [OPTION]... PATTERNS [FILE]... Search for PATTERNS in each FILE. Example: grep -i 'hello world' menu.h main.c PATTERNS can contain multiple patterns separated by newlines. The most basic usage is <syntaxhighlight lang="sh"> cat log.txt | grep "error" </syntaxhighlight> This feeds the content of the <code>log.txt</code> file into grep, which finds all lines with the text “error”. However, grep itself can read files directly, so it is better to just do: <syntaxhighlight lang="sh"> grep "error" log.txt </syntaxhighlight> The most common flags are: -i, --ignore-case ignore case distinctions in patterns and data -w, --word-regexp match only whole words -r, --recursive like --directories=recurse -n, --line-number print line number with output lines For example, * <code>grep -i warning log.txt</code> matches <code>warning</code>, <code>WARNING</code>, <code>Warning</code>, etc. * <code>grep -w berry</code> matches <code>berry</code> but not <code>strawberry</code> or <code>blueberry</code>. * <code>grep -r admin /etc/</code> searches for <code>admin</code> in all files inside the <code>/etc/</code> [[directory]]. === Extended Regular Expressions === The <code>-E</code> flag enables ''extended regular expressions'' ([[ERE]]), while the lack of so only allows ''basic regular expressions'' ([[BRE]]), a very small subset of what most modern regex implementations provide:<ref>[https://www.gnu.org/software/grep/manual/grep.html GNU Grep 3.12], gnu.org, 2025 (Accessed: 2025-06-21)</ref> <syntaxhighlight lang=shell-session> $ grep --help | grep -- '--' | head -n3 # `--` to tell grep to stop processing flags -E, --extended-regexp PATTERNS are extended regular expressions -F, --fixed-strings PATTERNS are strings -G, --basic-regexp PATTERNS are basic regular expressions $ grep --help | grep '^\s+--' $ grep --help | grep -E '^\s+--' | head -n3 --no-ignore-case do not ignore case distinctions (default) --help display this help text and exit --line-buffered flush output on every line </syntaxhighlight> == Examples == === Finding Python Function Calls === In a [[Python]] codebase, we can find all calls to functions under the <code>subprocess</code> module with <code>shell=True</code>: <syntaxhighlight lang=shell-session> $ grep -r --include='*.py' -nHE 'subprocess\.\w+\([^)]*shell=True' ./driver.py:69: return subprocess.call("lspci | grep -q -i NVIDIA", shell=True) == 0 ./driver.py:202: return subprocess.call("lspci | grep -q -i Network | grep -q -i Broadcom", shell=True) == 0 ./driver.py:211: return subprocess.call("lspci | grep -q -i Bluetooth | grep -q -i Broadcom", shell=True) == 0 ./util.py:38: proc = subprocess.Popen(f"chroot {chroot} /tmp/stellar-payload.sh", shell=True) ./util.py:63: # proc = subprocess.Popen(payload, shell=True) ./util.py:66: proc = subprocess.Popen(f"pkexec {tmpfile}", shell=True) </syntaxhighlight> (This is run on the [https://github.com/Ultramarine-Linux/stellar/ Ultramarine stellar codebase]) We can breakdown the flags used in this example: * <code>-r</code>: find files recursively (by default in the current working directory) * <code>--include='*.py'</code>: only examine Python files * <code>-n</code>: show line numbers * <code>-H</code>: show file name * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] We can divide the pattern <code>subprocess\.\w+\([^)]*shell=True</code> into many parts: # <code>subprocess</code> matches the string “subprocess” literally; # <code>\.</code> matches the full stop literally; # <code>\w+</code> matches word characters one or more times, where a word character (<code>\w</code>) is any letter, digit or underscore<ref>[https://www.regexroo.com/word-characters Understanding \w and Its Counterpart \W in Regex], RegexRoo.com, 2025 (Accessed: 2025-06-21)</ref>; # <code>\(</code> matches for an open parenthesis <code>(</code> literally; # <code>[^)]*</code> is an inverse character group and matches any characters that are not the closing parenthesis <code>)</code> zero or more times; and # <code>shell=True</code> matches the string “shell=True” literally. === Finding Code Files with TODOs and FIXMEs === We can list out code files that contains both the word “FIXME” and “TODO”. For a Rust project: <syntaxhighlight lang=shell-session> $ grep -rlZ 'FIXME' --include='*.rs' . | xargs -0 grep -l 'TODO' ./src/pages/_15_installing.rs ./src/main.rs </syntaxhighlight> Flags: * <code>-r</code>: find files recursively (by default in the current working directory) * <code>-l</code>: output matching files' names only * <code>-Z</code>: instead of a new line character, print out a null character after each filename * <code>--include='*.rs'</code>: only examine Rust files In this example, the first command outputs the filenames with null separates, then [[xargs]] is used to feed the filenames into the second grep command, which searches for “TODO”s in those files. === Extracting All Unique Public IPv4 Addresses from Log Files === We can extract all the unique IPv4 addresses from a directory of log files, but exclude any private IP addresses, such as <code>10.x.x.x</code> / <code>192.168.x.x</code>: <syntaxhighlight lang=sh> grep -rhoE '([0-9]{1,3}\.){3}[0-9]{1,3}' /path/to/logs | sort -u | grep -vE '^10\.|^192\.168\.' </syntaxhighlight> Flags: * <code>-r</code>: find files recursively * <code>-h</code>: suppress printing of filenames * <code>-o</code>: show only matching part of line * <code>-E</code>: enable [[#Extended Regular Expressions|ERE]] * <code>-v</code>: select non-matching lines For the first pattern: # <code>[0-9]</code> matches the digits (0 to 9 on the ASCII table includes all digits), and <code>{1,3}</code> specifies the length must be between 1 and 3; and # <code>([0-9]{1,3}\.){3}</code> matches exactly 3 times the above followed by a full stop. For the second pattern: # <code>^10\.</code> matches for lines starting with <code>10.</code>; # <code>^192\.168\.</code> matches for lines starting with <code>192.168.</code>; and # <code>|</code> (which indicates “or”) allows matching for the regex specified on the left or the right. Due to the invert flag (<code>-v</code>), if a line matches the second pattern, it is excluded, and other lines are printed instead. == Alternatives == Faster implementations of grep such as '''[[ripgrep]]''' (<code>rg</code>) and '''[[hypergrep]]''' (<code>hgrep</code>) are usually available in mainstream package repositories, but are not bug-for-bug compatible with GNU grep, and usually not pre-installed on most distributions. The '''<code>agrep</code>''' tool (''approximate grep'') can find matches even if the pattern is not matched exactly<ref>[[wikipedia:Agrep|agrep]], Wikipedia, 2025 (Accessed: 2025-06-21)</ref>. == See Also == * [[AWK|awk]] * [[sed]] * [[Regular Expression]] == References == 1fcce348d192a533dd6f740ef6975c87d02a7adc 0 814 3299 2025-08-07T18:50:01Z Madonuko 140 #REDIRECT [[Regular Expression#Basic Regular Expression]] wikitext text/x-wiki #REDIRECT [[Regular Expression#Basic Regular Expression]] 495479ca7d6a95efcfa62d908f67ccb4d7551b08 0 815 3300 2025-08-07T18:50:21Z Madonuko 140 #REDIRECT [[Regular Expression#Extended Regular Expression]] wikitext text/x-wiki #REDIRECT [[Regular Expression#Extended Regular Expression]] 21330eb3a515bff2528252a7ac726d3f70c573b1 0 816 3301 2025-08-07T19:42:37Z Satnus 215 Made a short page for runit. wikitext text/x-wiki {{Work In Progress}} Runit is a cross platform init & service management scheme used on Unix like systems such as Linux, *BSD, Mac OS X & Solaris.<ref>https://smarden.org/runit/ Runit's official website.</ref> It was made by Gerrit Pape to replace sysvinit and other init schemes in Unix systems. Runit can be used either as an init scheme or a service supervisor running under another, preexisting init scheme. === Design === In the role of an init scheme, runit performs booting, running, halting or resetting the system in three stages: * Stage 1: Runit starts /etc/runit/1 and waits for it to terminate. The system's one time initialization tasks are completed here. /etc/runit/1 is slimmed down as much as possible, and has full access to /dev/console in case something goes wrong. * Stage 2: Runit starts /etc/runit/2 which in turn runs runsvdir. Its task is to monitor services represented as directories defined by the distro.<ref>[https://smarden.org/runit/runsvdir.8]</ref> This part of Runit is the only one which can be used across different Unix like systems with little modification.<ref>[https://smarden.org/runit/benefits]</ref> Stage 2 is supposed to stay running till the system halts or reboots. * Stage 3: If runit is told to halt or reboot, it stops /etc/runit/2 and runs /etc/runit/3 to shutdown or reboot the system. === Distributions with runit === * antiX Linux (runit offered as official alternative) * Arch Linux (runit offered as unofficial alternative)<ref>https://wiki.archlinux.org/title/Runit</ref> * Artix Linux (runit offered as official alternative)<ref>https://wiki.artixlinux.org/Main/Runit</ref> * Debian (runit offered as unofficial alternative)<ref>https://tracker.debian.org/pkg/runit</ref> * Devuan (runit offered as official alternative)<ref>https://www.devuan.org/os/init-freedom</ref> * FreeBSD (runit offered as alternative)<ref>https://www.freshports.org/sysutils/runit/</ref> * Gentoo (runit offered as alternative)<ref>https://wiki.gentoo.org/wiki/Runit</ref> * Linux from Scratch (runit offered as unofficial alternative)<ref>https://code.google.com/archive/p/runit-for-lfs/</ref> * OpenBSD (runit offered as alternative)<ref>https://openports.eu/ports/sysutils/runit</ref> * Ubuntu (runit offered as unofficial alternative)<ref>https://packages.ubuntu.com/search?keywords=runit</ref> * Void Linux (runit is the default)<ref>https://docs.voidlinux.org/config/services/index.html</ref> == References == <references /> 47dc856a3472a827c855ce2723fb6b95b72c9d0b 0 428 3302 3019 2025-08-07T19:57:47Z Ow0cast 249 ce | fix code tags wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' (short for ''manual'') is a [[TUI|command-line]] utility available on [[UNIX]] and UNIX-like [[Operating System|operating systems]] that provides documentation for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a man page the user can enter the following into their terminal:<ref>https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage</ref> man ''<command_name>'' For example, to read the manual for <code>man</code> command itself: man man == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>https://en.wikipedia.org/wiki/Man_page#Manual_sections</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>https://en.wikipedia.org/wiki/Man_page#Layout</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER</code> environment variable. By default, it uses <code>less</code>. Alternatively, the <code>-P</code> or <code>--pager</code> option can be used.<ref>https://www.mankier.com/1/man.mandoc#Environment</ref><ref>https://www.man7.org/linux/man-pages/man1/man.1.html</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally.<ref>https://fishshell.com/docs/current/faq.html</ref> == References == <references /> 9ad15cccc53a939512ae83dee73e1d1532d1bbeb 2 817 3303 2025-08-08T06:00:31Z Madonuko 140 I wonder if WikiMonkey-ArchWiki works javascript text/javascript mw.loader.load('https://rawcdn.githack.com/kynikos/wiki-monkey/v5.5.3/dist/WikiMonkey-ArchWiki.min.js'); 0b9bb3326746bec17118c27447743e516d1e5d6c 3304 3303 2025-08-08T06:03:14Z Madonuko 140 what about WikiMonkey-Wikipedia javascript text/javascript mw.loader.load('https://rawcdn.githack.com/kynikos/wiki-monkey/v5.5.3/dist/WikiMonkey-Wikipedia.min.js'); 819ff18b6a8eed52c0337946d41384287b3995a5 2 818 3305 2025-08-08T07:09:43Z Hamachitan 222 Created page with "{{Cleanup|にゃんにゃんねこにゃんにゃん}} Lorem." wikitext text/x-wiki {{Cleanup|にゃんにゃんねこにゃんにゃん}} Lorem. 78f5248af4b93301a143de027bb2c348a3e1a7df 3306 3305 2025-08-08T07:53:48Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Cleanup|にゃんにゃんねこにゃんにゃん}}Lorem. dff8c45f79c4b807f305fd38c72d797a6536ab26 3307 3306 2025-08-08T08:05:12Z Hamachitan 222 Undo revision [[Special:Diff/3306|3306]] by [[Special:Contributions/Hamachitan|Hamachitan]] ([[User talk:Hamachitan|talk]]) wikitext text/x-wiki {{Cleanup|にゃんにゃんねこにゃんにゃん}} Lorem. 78f5248af4b93301a143de027bb2c348a3e1a7df 3308 3307 2025-08-08T08:05:32Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Cleanup|にゃんにゃんねこにゃんにゃん}}Lorem. dff8c45f79c4b807f305fd38c72d797a6536ab26 0 779 3309 3285 2025-08-08T08:16:33Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Haskell-Logo.svg]] | title = Haskell | releasestatus = Maintained | lastrelease = GHC 9.12.2 - 22 July 2025 / Haskell2010 | firstrelease = GHC 0.29 - 25 July 1996 / Haskell 1.0 | languages = Haskell | developers = The Haskell Foundation | designed by = ICFP | website = [https://haskell.org haskell.org] }}{{Needs Citations}}'''Haskell''' is a general-purpose, statically typed, purely functional programming language with type inference and lazy evaluation. = History = Functional Programming in the 80's already had its roots in programming - such as the Lisp language. The new idea that sparked creation of multiple functional languages (such as Miranda, SASL, KRC) was lazy evaluation - which later became one of core Haskell ideas. In order to centralize functional programming efforts, multiple conferences (later merged into International Conference on Functional Programming) were held in the 90's. They resulted in creation of '''Haskell'''. = Philosophy = Haskell as a functional language inherits its philosophy from math-oriented subjects such as Lambda Calculus or Category Theory. Despite it's reputation, Haskell doesn't require prior knowledge of those in order to write basic code. = Installation & Usage = Most common Haskell compiler is '''GHC''' - Glasgow Haskell Compiler. Installation process shouldn't be harder than installing `ghc` package with your favorite package manager. GHC provides essential tools, such as `ghc` and `ghci` - the compiler and interpreter. The latter can be used for simple inline operations, which is extremely useful when learning the language. = Useful Links = * [https://learnyouahaskell.github.io/ Learn You A Haskell] is a popular book (with a free online copy) which aims to explain Haskell without requiring prior knowledge in functional programming. * [https://hoogle.haskell.org/ Hoogle] is a Haskell API search engine, helpful in finding libraries etc. [[Category:Programming Languages]] 771748fda5f86a28b05a36fdf6a922e75e16f707 2 819 3310 2025-08-08T08:17:52Z Hamachitan 222 nuko supervision bot real wikitext text/x-wiki Experimental bot by [[User:Madonuko]]. This bot is always run with nuko supervision. b346ff5d845b55e2a16e1110f5375dc01e1ee7ea 0 412 3311 1810 2025-08-08T08:18:32Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Needs Citations}}{{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-org | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }}'''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. === Available Parameters === {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default (none unless specified) || [given parameter] |} === Trivia === * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ ^{<nowiki>[1]</nowiki>}] * [[Larry the Cow]] (<code>emerge --moo</code>) and Cowsay share the same ASCII art, [[Debian]]'s Larry ASCII arts don't. * There is a graphical version of this program called [https://www.doof.me.uk/xcowsay/ xcowsay]. [[Category:Software]] 8e58c0e9416f9074dbff3b2cdf27d5e57269d63a 3341 3311 2025-08-08T09:28:08Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{Needs Citations}}{{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-org | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }}'''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. == Available Parameters == {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default (none unless specified) || [given parameter] |} == Trivia == * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ ^{<nowiki>[1]</nowiki>}] * [[Larry the Cow]] (<code>emerge --moo</code>) and Cowsay share the same ASCII art, [[Debian]]'s Larry ASCII arts don't. * There is a graphical version of this program called [https://www.doof.me.uk/xcowsay/ xcowsay]. [[Category:Software]] 9906efc56c097bda6b3415b429df44a6c7ff5f55 0 268 3312 2953 2025-08-08T08:19:07Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch github.com/fastfetch-cli/fastfetch] }}Fastfetch is a [[neofetch]]-like tool for fetching information about your [[Operating System|operating system]], [[software]] and hardware. It is written mainly in [[C]], with a focus on performance.<ref>https://github.com/fastfetch-cli/fastfetch Fastfetch Github, 2025 (Imported 26th, June 2025)</ref> == References == <references /> [[Category:Software]] a5697ca9e7ed89b4b0c73f8bd43111d055ab7571 0 355 3313 1811 2025-08-08T08:19:18Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Needs Citations}}The '''GNU C Library''', commonly known as '''glibc''', is the GNU Project implementation of the C standard library. It provides a wrapper around the system calls of the Linux kernel and other kernels for application use. Despite its name, it now also directly supports C++ (and, indirectly, other programming languages). It was started in the 1980s by the Free Software Foundation (FSF) for the GNU operating system. [[Category:Software]] b53ee6ecff3d45cc74a0b5a11fe624b9cb9c433b 0 263 3314 3039 2025-08-08T08:19:45Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Needs Citations}}{{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.99.0, 2024-10-24 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }}[[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|thumb|The Hyfetch Pride Month easter egg.]] Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your [[Operating System|operating system]], [[:Category:Software|software]] and [[hardware]] with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch Hyfetch Github 2025 (fetched 24th June 2024)</ref> === Features === Due to Hyfetch being a direct fork of Neofetch, many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of Neofetch bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. == References == <references /> [[Category:Software]] 3659930fbca140007f3906f4d33348d1a89ad87f 0 322 3315 3041 2025-08-08T08:21:03Z Madonuko 140 Strip leading empty lines wikitext text/x-wiki {{Needs Citations}}{{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the [[Linux|Linux kernel]], released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. === Usage on [[Operating System|Operating Systems]] === [[Linux Distributions|Linux distributions]] which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * [[Sabotage]] * [[Morpheus Linux]] * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against glibc. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. === See also === * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] [[Category:Software]] 421533e6986c390faecb4aa4420c2b810ec0e280 0 261 3316 2981 2025-08-08T08:21:40Z Madonuko 140 Strip leading empty lines wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was created by Dylan Araps in 2017 and was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]], a neofetch-like utility written in [[C]], and [[hyfetch]], a fork of neofetch with pride flags. == References == <references /> [[Category:Software]] 78c1830d6ff8de309f4e43a7f002018f4ead7838 0 228 3317 3038 2025-08-08T08:24:21Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}}The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. [[Package|Packages]] that enter the extra repository can be directly installed with pacman.<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with AUR helpers. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, AUR helpers have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, pacman is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>https://wiki.archlinux.org/title/PKGBUILD</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>https://wiki.archlinux.org/title/Namcap</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability. == References == <references /> [[Category:Terminology]] 24cda555f6d89126d92cb954a45d42753f7b0ce6 0 318 3318 2709 2025-08-08T08:24:44Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Needs Citations}}The bootloader is a [[:Category:Software|program]] that's responsible for booting the system. Most of the time, it will have a menu to choose an option from, making it a boot manager. A bootloader is installed onto the boot partition of the computer during a [[Linux Distributions|distribution's]] installation process. Most of the times, boot partitions may need from 200 to 600MB of space to work properly. Most bootloaders also have theming capabilities, take, for example, [[GRUB]]. [[Category:Terminology]] 587d136a580eb0e11985336162be8b33ff46755b 0 433 3319 2924 2025-08-08T08:25:24Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Needs Citations}}A '''CLI''' (Command-Line Interface) is a text-based interaction model in which users type commands as text strings to interact with an operating system or a program through a computer. Unlike a [[TUI]], which relies upon a pseudo-graphical form made of characters, an interface that is purely a command-driven one usually would issue output in the form of lines of text upon receiving user instructions. [[File:Unix shell.png|thumb|A Unix shell command prompt, an example of a CLI]] CLIs are often preferred by power users, system administrators, and developers for their efficiency, scriptability, and precise control over system operations. Common examples include: * Unix/Linux shells (sh, bash, zsh, fish) * Windows Command Prompt * PowerShell * Python's REPL (Read-Eval-Print Loop) The main advantages of CLIs include: * Resource efficiency (minimal system requirements) * Automation capability through scripting * Remote system administration * Precise control over system operations * Speed of execution for experienced users While CLIs can have a steeper learning curve compared to GUIs (Graphical User Interfaces) or TUIs, they remain fundamental to modern computing, particularly in server administration, software development, and system maintenance. == History == [[File:Edwind.png|thumb|CLI text editor Ed in a GUI terminal emulator window]] Command-line interfaces emerged in the 1960s with teleprinters like the Teletype Model 33 ASR, which replaced punch cards as the primary means of computer interaction. Early operating systems like Unix and MS-DOS were primarily accessed through CLIs, establishing conventions that persist in modern computing. [[File:Command com.png|thumb|The MS-DOS command prompt]] == Common Usage == CLI environments typically follow a standard pattern where: * The system displays a prompt (e.g., "$" for Unix-like systems) * Users type commands followed by arguments or options * The system executes the command and displays the output * The process repeats with a new prompt [[Category:Terminology]] [[Category:User interfaces]] 0d79752d56172067f45945da7ec30def0e9d0ac2 0 158 3320 3138 2025-08-08T08:28:22Z Madonuko 140 Strip leading empty lines; create cleanup notice wikitext text/x-wiki {{Needs Citations}}{{Cleanup|Contrary to the page title, this page does not provide in-depth information for commands}}When using [[Linux]], sooner or later, there's a good chance you'll end up finding yourself in front of a [[TUI|terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a '''command'''. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include <code>echo</code>, <code>mv</code>, [[cat|<code>cat</code>]], etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with <code>sudo</code> followed with your original command. [[sudo]] tells your computer to ''do'' something as a ''super user'' which will allow you to bypass restrictions. It should be important to note that '''sudo is a separate package''' and may not be pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you will need to use something like <code>su</code> to log in as root and then run your command as root or install sudo as root. == Useful Commands == Furthermore, with commands you will likely need to include ''options'' that specify to the program how you want it to behave. One of the most common options is <code>--help</code>, which will usually tell program to list all of its options. An example would be as follows: cat --help In this case, the 'cat' utility would respond to this command with the following:<syntaxhighlight>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines ...</syntaxhighlight>These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, <code>--help</code> is always there and ready. If not, you can always run [[man|<code>man</code>]] before a program similarly to how you would run <code>sudo</code>, and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a file to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory|working directory]] (Like shown) or you can provide a file from anywhere in the [[filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt The tilda sign <code>~</code>, in Linux and some other [[Operating System|operating systems]], expands to the full [[Directory Path|directory path]] of the current user's home folder. Here is what it would look like to type out the whole path: nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] 7302c7e92b3c5600731b17bc040ff3c7c249ce37 0 223 3321 3035 2025-08-08T08:29:05Z Madonuko 140 Strip leading empty lines wikitext text/x-wiki {{Needs Citations}}{{Stub}}Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (e.g. FSF approved distribution) * Ecosystem or Tooling (e.g. libc, [[Package Manager|package manager]], coreutils, [[Init System|init system]]) * Experimentation * Customization ... and many more. This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (e.g. Debianisms, package managers, init systems) * Opinionated design philosophies (e.g. Nix, Guix, Fedora Atomic) * Additional configuration needs (e.g. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (e.g. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (e.g. Liberapay, GitHub sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] 4bd97cc6b74bc39b271d4ad1e810a797f5696cf7 0 345 3322 2968 2025-08-08T08:29:50Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Needs Citations}}Kernel Modules are pieces of code that can be loaded directly into the [[Kernel]] at runtime to extend functionality.<ref>https://linux-kernel-labs.github.io/refs/heads/master/labs/kernel_modules.html Kernel Labs Github, 2025 (imported 26th June 2025)</ref> The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your [[Linux Distributions|Distribution]], as such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically older ones benefit the most) at the cost of new devices potentially not working when added. It is also possible to compile a Linux kernel on a pre-existing system to only use needed Kernel modules. == Obtaining information == Modules depend on the kernel release and the kernels version, though usually they are stored in <code>/usr/lib/modules/''kernel_release_version''</code>''.'' To see which modules are loaded, <code>lsmod</code> can be used. Obtaining information is achievable with <code>modinfo <module_name></code> == Module loading == === Automatic loading === Usually most needed modules are handled [[udev]], so usually out of tree modules aren't needed, though there are cases where loading or blacklisting a module is needed for your setup to function properly. Early module loading is generally handled by your [[initramfs]] generator of choice, usually dracut, booster or mkinitcpio. Alternatively, [[systemd]] will load modules explicitly listed in <code>/etc/modules-load.d/</code> ,with the naming scheme of <code>/etc/modules-load.d/program.conf</code>. Lines starting with ; or # are parsed as comments and ignored === Manual loading === Kernel modules can be manually loaded with <code>modprobe <module_name></code>, or loading a module that by file name (i.e. modules that are not installed in <code>/usr/lib/modules/<kernel_release_version></code>) can be achieved either of the following ways:<syntaxhighlight lang="sh"> insmod file_name module_options modprobe file_name </syntaxhighlight>Removing a module can be achieved by:<syntaxhighlight lang="sh"> rmmod module_name modprobe -r module_name modprobe --remove module_name </syntaxhighlight> == References == [[Category:Terminology]] 695f99e21c4b0eebb07bb9c1f0f2e5e79f67c2fc 0 178 3323 3173 2025-08-08T08:31:30Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Cleanup|Short article}}{{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }}[[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] = Linux Kernel = The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and deallocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under the terms of the [[GNU General Public License]] version 2 (GPLv2), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] * [[Unix]] * [[Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> [[Category:Terminology]] 2a413879d866b9c78d404dfe335b0130c8f4724f 0 8 3324 3021 2025-08-08T08:31:50Z Madonuko 140 Strip leading empty lines wikitext text/x-wiki {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ [[Category:Terminology]] a17655046d5ee3ead2df0c41c451dd7467ba3a6c 0 405 3325 2989 2025-08-08T08:32:31Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Cleanup|Short page}}Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Linux and other open source operating systems will avoid or not support proprietary software when possible. This is mainly due to incompatible licensing.<ref>https://solutionshub.epam.com/blog/post/proprietary-software-definition-examples Epam, 2025 (imported 27th June 2025)</ref> Some examples of proprietary software are Microsoft Windows and Adobe Photoshop. == References == [[Category:Terminology]] 62c694e1996159888d5425df53450c0ef74a1c22 0 319 3326 2074 2025-08-08T08:32:41Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Needs Citations}}'''Ricing''' (''slang'') refers to extensively customizing a [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to create a unique, personalized computing experience. The term originated from the automotive modification scene ("ricer" cars) and has been adopted by the Linux/Unix community. While primarily focused on aesthetic customization through themes, colors, widgets, and interface layouts, ricing can improve functionality and performance. Common ricing elements include: * Custom window borders, titlebars, decorations; * Color schemes and typography; * Specialized status bars and system monitors; * Custom application launchers and menus * Personalized desktop widgets and notifications * Modified system icons and cursors Popular tools for ricing include customization frameworks such as polybar and picom for window managers like i3, bspwm, and dwm. People frequently share configuration files, or "dotfiles," and screenshots - [https://www.reddit.com/r/unixporn/ r/unixporn] is one of the most popular. [[Category:Terminology]] 2649c8be45127fd07bb90b25c82287f3328d54f7 0 169 3327 3243 2025-08-08T08:33:39Z Madonuko 140 Strip leading empty lines wikitext text/x-wiki {{Needs_Citations}}[[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories == List of Package Managers == All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained by the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] [[Category:Terminology]] b1e7c0e0614b2231c2cae2170ad6010f9a1c02a5 0 2 3328 3271 2025-08-08T08:35:56Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }}[[File:Arch_Linux_Minimal_Neofetch_Output.png|thumb|[[Neofetch]] on Arch Linux]] '''Arch Linux''' is an independent rolling release [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. Arch Linux is kept up-to-date by regularly updating the packages of the system. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Installation === The Arch Linux website provides a downloadable ISO image that can be flashed onto a bootable drive. The operating system can be installed by following the [https://wiki.archlinux.org/title/Installation_guide Installation Guide] or by using the included installation script, archinstall. ==== Arch Installation Script ==== This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> [[Category:Linux Distributions]] 70143a14ad57c19d819ac61e904022f5a8eae231 0 217 3329 3190 2025-08-08T08:36:32Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]] |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64 |website=[https://fedoraproject.org/ fedoraproject.org]}}[[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> == References == <references /> [[Category:Linux Distributions]] 6cf87cb6e2bb17a0a77a2f48be2c198e5f66564f 0 203 3330 3276 2025-08-08T08:36:42Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }}[https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]<ref>https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer)</ref>. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile<ref>https://en.wikipedia.org/wiki/Compilation</ref> their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish thru source compilation of the packages and the kernel itself. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements, the only downside of that being increase compilation time, however '''Gentoo''' is very minimal and it allows a lot of flexibility in that regard. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "slotting". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. To manage those multiple versions of the same packages ( slotting ), '''Gentoo''' provides a tool called '''eselect'''. It acts as a manager for setting system defaults, such as choosing which version of GCC, Python, or even your preferred text editor should be used globally. == Use cases of eselect == Changing the GCC version<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect gcc list [1] x86_64-pc-linux-gnu-13 * [2] x86_64-pc-linux-gnu-14 [user@hostname ~]$ eselect gcc set 2</syntaxhighlight>Changing the locale<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 * [3] en_US.utf8 [4] POSIX [ ] (free form) [user@hostname ~]$ eselect locale set 3 </syntaxhighlight> == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp) </syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |- |<code>emerge --unmerge package</code> |Remove a package and its dependencies |- |<code>emerge --depclean</code> |Remove unused dependencies |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers pre-compiled package options, which usually end in '''<code>-bin</code>''', by example one might want to install Firefox without the hassle of compiling, they can just download the binary version of it by doing <code>sudo emerge firefox-bin</code>. Obviously, not all binary packages will end in the <code>-bin</code> format, they can be named simply like normal packages, for that reason Portage highlights the binary and source packages differently in colors so the user knows which are binary and which are meant for compiling, additionally portage also informs the user of which packages are binaries or source. For additional packages, users might opt for the [https://wiki.gentoo.org/wiki/Project:GURU GURU] project repository, it aims to be a very large user repository, full of binaries and source packages that are not found inside the normal '''Gentoo''' repositories, meant to extend the experience that you can have in this Operating System. Users can create their own repository online as well, or how we call it, "overlays". The user can create an overlay with the desired package, make an ebuild for it and then publish it online for people to use. To get started with an overlay, one must first understand what are ebuilds and how they work, for this it's preferred to read the '''Gentoo Wiki''' on how to do it, it is possible to even add your custom package inside '''GURU''' later, and even the official '''Gentoo''' repository if it's seen as valuable. == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === One might be interested in community resources for '''Gentoo.''' The official community forums can be found at [https://forums.gentoo.org/ forums.gentoo.org/]. Additionally, IRC<ref>Internet Relay Chat</ref> channels has been setup as well. For those who are interested in the official IRC channels, they can be found on the '''Gentoo Wiki''' in the [https://wiki.gentoo.org/wiki/IRC IRC] article. It is possible to subscribe to the [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] or even send emails to them, the page lists the most important lists with the most traffic. There are other, more specialized lists that might be more appropriate depending on the topic. There is a [https://www.gentoo.org/support/documentation/ wiki documentation] available as well. Users can search up specific pages in the site directly, so that they don't waste time finding the right page. Ultimately, '''Gentoo''' offers a [https://bugs.gentoo.org/ bug tracking system] for those who are interested in being up to date with current bugs, or even attempt to solve them. === Development Model === '''Gentoo''' was developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the userbase through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == '''Gentoo''' allows maximum customization potential, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to fetch binaries in heavier packages. However, '''Gentoo''' has it's own downsides; It will take longer to install packages as they compile from source, meaning it will take some time until finished and ready to use. If the system has a very weak CPU, the Operating System will take a while to fully install. The Operating System has a higher learning curve, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 76680a18b8892a4c538f17064fbe4073a4a6262c 0 171 3331 3257 2025-08-08T08:36:52Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }}'''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such as nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] 5646c4a8f99b602bf93c7b73b4639dfc99d0014f 0 480 3332 2995 2025-08-08T08:38:00Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}}[[File:Oreon10-2502.png|thumb|Oreon 10 Core (Build 2502) running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>https://oreonproject.org/</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>https://git.oreonproject.org/rpms</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>https://boostyconnect.com/oreon-lime-r1-lifecycle/</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>https://oreonproject.org/oreon-lime-r2-support-timeline/</ref><ref>https://oreonproject.org/oreon-lime-r2/</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/</ref> and other well-known sources. In October 2024, Oreon celebrated its 1st anniversary on November 16, 2024, and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69</ref> Oreon 10 released to the public on December 12, 2024, shipping with KDE Plasma 6 and Linux 6.11<ref>https://forums.oreonproject.org/t/oreon-10-officially-released/98</ref> but was upgraded to 6.12 a few days later. A new update to Oreon 10 has been released on February 12, 2025, under the name "Build 2502." This update brought a few bug fixes along with some planned features for later such as Apple M-series Mac support.<ref>https://forums.oreonproject.org/t/oreon-10-build-2502-has-officially-released/150</ref> == References == <references /> [[Category:Linux Distributions]] c0350b0d960c8ad3f7cbf5f45d1dac4076d95c8f 0 233 3333 3043 2025-08-08T08:38:10Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }}[[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with KDE * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. == References == [[Category:Linux Distributions]] b823577cf6994e715100d2dd3819f1aaa1d0a6de 0 279 3334 3204 2025-08-08T08:38:15Z Madonuko 140 Strip leading empty lines wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, ppc64, x86_64 | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. ==== Versions ==== This distribution stands out by having two primary variations of the distribution: OpenSUSE Tumbleweed is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. OpenSUSE Leap is the point release version, with a new release every year with older and more stable packages meant for business use. ===== openSUSE Slowroll ===== Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. [[Category:Linux Distributions]] 2584dc238a92ddd20aa916942d2ab66e06d88676 0 317 3335 3256 2025-08-08T08:39:08Z Hamachitan 222 Strip leading empty lines wikitext text/x-wiki {{Needs_Citations}}{{Cleanup|Page relies too heavily on bullet pointed lists}}{{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }}'''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm]</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and Musl variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses the homegrown [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for runit. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == [[Category:Linux Distributions]] bae84470d6186b4ed0a6b7181347fa7821a3df84 0 277 3336 2073 2025-08-08T08:39:22Z Madonuko 140 Strip leading empty lines wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_Logo.png|thumb]] | caption = Rocky Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] Rocky Linux is a Linux distribution developed by RESF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit". It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. [[Category:Linux Distributions]] 76aa2bba5764004a417b2601744f204abfb1b8d1 6 820 3337 2025-08-08T08:51:47Z Imnotgoodatnames 121 Slackware Linux logo wikitext text/x-wiki == Summary == Slackware Linux logo 3ee5d5d8a2a9cd227b72dba5063f35f7badb7a28 0 424 3338 2931 2025-08-08T09:24:52Z Hamachitan 222 /* AWK */ Remove redundant first heading wikitext text/x-wiki AWK is a programming language focused primarily on textual data processing<ref>[https://www.gnu.org/software/gawk/manual/html_node/] Top (The GNU Awk User's Guide)</ref>, though it can be used for other general-purpose tasks. This page will focus primarily on GNU Awk, or GAWK/<code>gawk</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/], Although the language name is officially stylized AWK, GNU officially uses the stylization Awk. They also acknowledge that the language itself is spelled AWK.</ref>. == Basic Usage == One of the most basic ways to use AWK is in a pipe to filter columnar data. For example, <code>cat file.txt | awk '{ print $1 }'</code> will print the first (space-delimited) column of a given file. This can be generalized to the second, third, etc. columns using <code>$2</code>, <code>$3</code>, etc. respectively. AWK can also be ran with <code>awk 'program-here' input-file1 input-file2 ...</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/One_002dshot.html] One-shot (The GNU Awk User's Guide)</ref>, so the above example with <code>cat</code> could also be written as: <pre> awk '{ print $1 }' file.txt </pre>More usage examples can be found on the [https://www.gnu.org/software/gawk/manual/html_node/Command-Line.html GAWK manual page], as well as AWK's [https://www.gnu.org/software/gawk/manual/html_node/Options.html many command-line options]. == AWK as a Language == AWK can also be used as a programming language. AWK programs consist of a list of patterns followed by actions to perform for each of those patterns<ref>[https://www.gnu.org/software/gawk/manual/html_node/Getting-Started.html] Getting Started (The GNU Awk User's Guide)</ref>: <pre> pattern { action } pattern { action } ... </pre> === BEGIN and END === Two common patterns are <code>BEGIN</code> and <code>END</code>, which run the given action before and after any text is processed respectively. These are called the "startup" and "cleanup" actions<ref>[https://www.gnu.org/software/gawk/manual/html_node/Using-BEGIN_002fEND.html] Using BEGIN/END (The GNU Awk User's Guide)</ref>. For example, the following code will print "Hello, World!": <pre> awk 'BEGIN { print "Hello, World!" }' </pre> The following will accept input until an EOF (inputtable in many shells as Ctrl+D), then print "Hello, World!": <pre> awk 'END { print "Hello, World!" }' </pre> === Regex Pattern === AWK can also be used to run a command for every line that matches a given regular expression. The following example prints every line that contains "regex" (equivalent to <code>grep 'regex'</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Regexp-Usage.html] Regexp Usage (The GNU Awk User's Guide)</ref>:<syntaxhighlight lang="awk"> /regex/ { print } </syntaxhighlight>The <code>{ print }</code> is actually implicit, meaning it can also be written:<syntaxhighlight lang="awk"> /regex/ </syntaxhighlight>One can combine this with <code>$1</code>, <code>$2</code>, etc. to print the second column of every row containing a given string, for example:<syntaxhighlight lang="awk"> /regex/ { print $2 } </syntaxhighlight> === Operations === AWK can be used to perform operations seen in many other programming languages, such as addition (<code>+</code>), subtraction (<code>-</code>), multiplication (<code>*</code>), division (<code>/</code>), modulus (<code>%</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Arithmetic-Ops.html] Arithmetic Ops (The GNU Awk User's Guide)</ref>, variable assignment (<code>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Assignment-Ops.html] Assignment Ops (The GNU Awk User's Guide)</ref>, equality (<code>==</code>) and inequality checks (<code>!=</code>), and comparisons (<code><</code>, <code><=</code>, <code>></code>, <code>>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Comparison-Operators.html] Comparison Operators (The GNU Awk User's Guide)</ref>. === ARGC and ARGV === Like many other programming languages, AWK programs can parse command-line arguments. The <code>ARGC</code> and <code>ARGV</code> variables (among [https://www.gnu.org/software/gawk/manual/html_node/Built_002din-Variables.html many others]) store the count of the arguments and an array of the arguments respectively<ref>[https://www.gnu.org/software/gawk/manual/html_node/Auto_002dset.html#index-ARGC_002fARGV-variables] ARGC, ARGV - Auto-set (The GNU Awk User’s Guide)</ref>. == References == <references /> [[Category:Software]] [[Category:Programming Languages]] 582f080a26e649a5826f3b7e4606a480f623693b 0 436 3339 2004 2025-08-08T09:25:43Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/ adelielinux.org]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is a [[Linux Distributions|Linux distribution]], based on Alpine Linux. The distribution targets old and low end machines, like desktops and servers. == Base description == One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution uses the OpenRC init system for service management, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. 2c105faedde9e502284e8c8c942afb3133f9ce28 0 269 3340 3020 2025-08-08T09:27:17Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{Needs Citations}}{{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], Budgie provides an easy to use Interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] == Features == '''Budgie Desktop View''' is a [[:Category:Software|software]] component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in C, and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. [[Category:Desktop Environments]] dc7f73403e2f5f08462b01e3340b1488a96805aa 0 780 3342 3163 2025-08-08T09:28:18Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki '''Cron''' is a job-scheduler in [[UNIX|Unix-like]] [[Operating System|Operating Systems]]. Users set-up cron jobs to run at periodically at fixed times, dates and intervals. == Crone implementations == * cronie * fcrone * dcrone * vixie-cron * scrone-git == Usage == edit your cron-jobs by running: crontab -e each line of crontab file represents a job and is formatted like this: * * * * * <command to execute> # | | | | | # | | | | day of the week (0–6) (Sunday to Saturday; # | | | month (1–12) 7 is also Sunday on some systems) # | | day of the month (1–31) # | hour (0–23) # minute (0–59) Crontab uses the following symbols {| class="wikitable" |+ !Symbol !Description |- |'''*''' |specifies every possible time interval |- |''',''' |List multiple values separated by a comma. |- |'''-''' |specify a range between two numbers |- |'''/''' |Specify a periodicity/frequency using a slash |} Crontab also has some special keywords: {| class="wikitable" |+ !Keyword !Description |- |'''@reboot''' |at startup |- |'''@yearly''' |once a year |- |'''@anually''' |identical to @yearly |- |'''@montly''' |once a month |- |'''@weekly''' |once a week |- |'''@daily''' |once a day |- |'''@midnight''' |identitcal to @daily |- |'''@hourly''' |once an hour |} === Basic cron commands === {| class="wikitable" |+ !Command !Description |- |'''crontab -l''' |list your cronjobs |- |'''crontab -e''' |edit your cronjobs |- |'''crontab -r''' |remove all your cronjobs |} 77ad4e086d5dc0249c10ca1dd68aaa1a0f826b1c 0 254 3343 3137 2025-08-08T09:28:28Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences https://dwm.suckless.org/]</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm. == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>https://dwm.suckless.org/patches/</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == [[Category:X_Window_Managers]] [[Category:Window Management Systems]] ac2920f77f177de126f1fcc6ef7356fbe6318f1a 0 164 3344 2675 2025-08-08T09:28:40Z Hamachitan 222 /* Introduction */ Remove redundant first heading wikitext text/x-wiki {{Work In Progress}} The [[Linux]] community is abundant with awesome projects and various other guides worth checking out, Here's some great ones that we have found - keep in mind that, while these guides are very useful, they are not fully exhaustive. More than likely you discover new software every day! * Privacy is not an end goal, but a consistent journey that needs to be taken very seriously. ''Always'' seek help when in doubt and ensure you take everything with a grain of salt. ''Do not just blindly follow guides but use your own intuition!'' == Guides == * https://www.privacyguides.org/ - An essential guide to learning not just ''how'' to begin your privacy journey online but offers a comprehensive explanation of abstract privacy concepts that is simple to understand and by extension ''is assuredly not easy or quick -'' read with an open mind! ** https://awesome-privacy.xyz - More of a guide to tools you may find yourself wanting to use to enhance privacy, rather than an explanation. The next step from Privacy Guides, essentially. ** https://www.privacytools.io/ - Similar to Awesome Privacy, and offers a wide range of tools. This specific website is recommended very frequently. * https://brainfucksec.github.io/firefox-hardening-guide - A guide to "de-Mozilla" and security-harden Firefox. Assess whether or not this is a good option for you - ''similar to privacy, it is not an easy process.'' * https://rentry.co/fmhy-guides - General, yet extremely useful and even nuanced guides that you may find yourself needing for something very specific and hard to find on the internet. * https://github.com/luong-komorebi/Awesome-Linux-Software - Very extensive guide of not solely Linux software but mostly open-source software that has many use cases in mind. May be helpful in picking a flavor of Linux for your specific use cases. == Wikis == * https://wiki.archlinux.org/ for Arch Linux * https://wiki.gentoo.org/ for Gentoo * https://wiki.debian.org/ for Debian * https://fedoraproject.org/wiki/Fedora_Project_Wiki for Fedora * https://wiki.ubuntu.com for Ubuntu == Tools == * https://christitus.com/windows-tool/ - Used for debloating and removing telemetry from Windows. * https://alternativeto.net - A tool to find alternatives to popular software, both open-source and proprietary. * https://etcher.balena.io/ - An open-source tool to flash operating systems to an USB drive. [[Category:Guides]] 47d977cd4bcebd252688211f36bfac34a719b3cd 0 716 3345 2876 2025-08-08T09:29:10Z Hamachitan 222 /* Hackintosh */ Remove redundant first heading wikitext text/x-wiki == Definition == A '''Hackintosh''' is a non‑Apple computer configured to run Apple's '''macOS''', using unofficial methods to bypass hardware restrictions. Apple's software license restricts macOS usage to Apple‑branded machines<ref>{{Cite|title=Hackintosh|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == History == === Origins === The concept surfaced as users attempted to run Mac OS on non‑Apple hardware. It gained real momentum after Apple transitioned to Intel CPUs, making macOS compatible with x86 architecture<ref>{{Cite|title=Intel Macs usher in Hackintosh era|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === PC Installations === Following the release of Intel-based Macs in 2006, community developers modified the macOS kernel to disable hardware checks and employed EFI emulation tools like FakeEFI to boot macOS on PCs<ref>{{Cite|title=Hackintosh bootloaders|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === Bootloader Evolution === Bootloaders such as Chameleon and Clover evolved to improve reliability. In 2019, '''OpenCore''' was introduced, offering advanced features like support for macOS security features including System Integrity Protection and FileVault<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === Legal Developments === In 2008, Apple sued Psystar for selling unauthorized macOS clones. The court ruled Psystar violated Apple copyright and the DMCA, underscoring Apple's legal restrictions<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == Technical and Legal Status == Apple's EULA prohibits running macOS on non‑Apple hardware<ref>{{Cite|title=Hackintosh licensing|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. The DMCA's anti‑circumvention provisions create legal uncertainty in the U.S.<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. Apple's transition to ARM-based silicon (beginning in 2020) reduces future feasibility for x86 Hackintoshes<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref>. == Hardware Compatibility == According to the '''Dortania OpenCore Install Guide''': CPUs: modern Intel (up to Comet Lake) and patched AMD Ryzen series GPUs: Intel integrated graphics (Ivy Bridge to Ice Lake), AMD GCN/Vega/Navi; NVIDIA support is limited Networking: Broadcom-based Wi‑Fi and Ethernet adapters are preferred<ref>{{Cite|title=OpenCore hardware limits|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref> == Installation Guide == This guide provides a high-level overview. For full instructions, consult the [[OpenCore Install Guide]]. === 1. Prepare hardware === Confirm that your CPU, GPU, and network adapters match published compatibility lists. === 2. Obtain macOS installer === On a real Mac, download the desired macOS version (such as Sonoma or Sequoia) from the App Store. === 3. Build a USB installer === Partition a USB drive as HFS+ or APFS and use '''OpenCore''' along with official tools to create a bootable installer<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 4. Configure BIOS/UEFI === Disable Secure Boot, VT-d, CSM, Fast Boot. Enable UEFI and XHCI handoff<ref>{{Cite|title=OpenCore BIOS settings|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 5. Boot and install macOS === Boot from the USB installer, format the target storage as APFS, then proceed with the installation. === 6. Post-install configuration === Migrate the USB EFI folder to the internal EFI partition. Install necessary kexts (for audio, network), configure USB mapping, and finalize settings such as NVRAM, FileVault, and Sleep/Wake. == Resources == [https://dortania.github.io/OpenCore-Install-Guide/ Dortania OpenCore Install Guide] – full tutorial [https://en.wikipedia.org/wiki/Hackintosh Hackintosh – Wikipedia] [https://tonymacx86.com/ tonymacx86 forums] – hardware build guides and buyer lists == See also == [[macOS]] [[Virtualization]] [[BIOS]] == References == <references/> 065e424d6411a9e636c364538aac7b6db50089cd 0 257 3346 2852 2025-08-08T09:29:24Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox|caption=Hyprland Logo|developers=The hyprwm team|image=[[File:Hyprland logo.png|center|frame]]|languages=[[C++]]|lastrelease=v0.40.0, 2024-05-04|releasestatus=Maintained|title=Hyprland|website=[https://hyprland.org/ hyprland.org]}} [[File:Hyprland.png|thumb|A screenshot of a desktop running Hyprland, with [[neofetch]] and a browser with atl.wiki running along with it.]] Hyprland is a dynamic tiling [[Window Manager]] that does not sacrifice on its looks, it is a wl-roots based compositor that has a lot of eye candy. It was originally made by Vaxry. It is one of the few window managers that aim for pure eye candy with nice animations, smooth looks and its own somewhat of an ecosystem. It also has it's very own custom syntax for its configurations. It is somewhat similar to bash scripting and it is quite easy to use. The hyperwm team has also made nice utilities that go well with the tiling window manager. Some like hyprcursor are made to completely change and revolutionize the XCursor style we have been using for years, others like hypridle are made for Hyprland specifically and shares a lot of features with something like swayidle, except it is tightly integrated with Hyprland configuration folders. It also has its own wallpaper software called hyprpaper which is considered to be well optimized. == Features == There are a lot of features included in Hyprland including: * Smooth and animated graphics (Such as moving windows, dragging them and other general animations such as opening and closing them) * Gradient customization for most things such as window borders with the option for gradient angles * Compatibility with most [[wayland]] apps and support for <code>xorg-xwayland</code> * Default configuration file auto-generated with the most important configurations setup (Such as touchpad tap to click, etc.) [[Category:Wayland_Compositors]] 5090e91b0cb2a5b07d693aedcb60aa29c7e55771 0 209 3347 2056 2025-08-08T09:29:34Z Hamachitan 222 /* Introduction */ Remove redundant first heading wikitext text/x-wiki {{Cleanup|Incomplete page, guides should be on their own page in the Guides namespace}} {{Needs_Citations}} [[Linux]] is a good way to make-do with an old Intel Mac you may have. Many issues exist due to hardware support, such as WiFi support, and keyboard + trackpad issues on some devices. This page will list solutions to common issues as well as tips, tricks, and other information. On many Mac devices Linux works flawlessly after initial setup and troubleshooting is complete. If you are attempting to install Linux on a device with an ARM (Apple Silicon) CPU, see the [[#Asahi Linux]] section. == Asahi Linux == Asahi Linux as a work in progress port of many tools and drivers to Apple Silicon on Linux, and is currently under heavy development. More information can be found on the [https://asahilinux.org/ Asahi Linux website]. == Troubleshooting == === MacBookPro11,x to MacBookPro12,1 === ==== WiFi doesn't work ==== This is a side-effect of Broadcom's poor driver support on Linux, read [https://asahilinux.org/ this page] for information on how to install the proprietary '''broadcom-wl driver''' on Arch Linux. Other distributions should follow their respective guides if one exists. == Notes == '''> More issues will be added overtime. This list is far from done.''' <references /> [[Category:Guides]] 44e7ae4cb6e2331a1489c4cce997ef2a03d1aa96 0 218 3348 2976 2025-08-08T09:29:44Z Hamachitan 222 /* Introduction */ Remove redundant first heading wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} [[Linux]] due to its generally lower system requirements than [[Windows]]<ref>https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3</ref> or [[macOS]] and a general absence of vendor-imposed hardware restrictions is frequently chosen for reviving and reusing older devices. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (i.e. keyrings, polkit, GTK, QT, etc.) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>https://www.linuxmint.com/faq.php</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>https://wiki.archlinux.org/title/Frequently_asked_questions</ref><ref>https://wiki.archlinux.org/title/Arch_compared_to_other_distributions</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time-consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>https://fedoraproject.org/wiki/FAQ</ref><ref>https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' == References == [[Category:Guides]] <references /> fbbd592a9b199f05f7b171c34f1683d1ad1785e5 3393 3348 2025-08-09T13:05:33Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} [[Linux]] due to its generally lower system requirements than [[Windows]]<ref>[https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3 Revive Old Hardware with Linux], Aidan Palmer, 2023-03-05 (Accessed: 2025-08-09)</ref> or [[macOS]] and a general absence of vendor-imposed hardware restrictions is frequently chosen for reviving and reusing older devices. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (i.e. keyrings, polkit, GTK, QT, etc.) |Usually require command line knowledge to troubleshoot|} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>[https://www.linuxmint.com/faq.php Frequently Asked Questions - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>[https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <span style="color:#fc493b">https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <sup>🍣404]</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Frequently_asked_questions Frequently asked questions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://wiki.archlinux.org/title/Arch_compared_to_other_distributions Arch compared to other distributions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time-consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>[https://fedoraproject.org/wiki/FAQ FAQ], Fedora Project Wiki, 2025-07-24 (Accessed: 2025-08-09)</ref><ref>[https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs Hardware Overview], Fedora Docs, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">[https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html System requirements for Puppy Linux], THE.Hosting, 2023-04-23 (Accessed: 2025-08-09)</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> ||} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' == References == [[Category:Guides]] <references /> 45bcf062e7fc1ba7c7d19c349b8485b0451938d7 0 733 3349 2977 2025-08-08T09:30:14Z Hamachitan 222 /* M1 */ Remove redundant first heading wikitext text/x-wiki '''Apple M1''' is a series of [[ARM|ARM-based]] system-on-a-chip (SoC) designed by [[Apple|Apple Inc]]., launched 2020 to 2022. It is part of the Apple silicon series, as a [[central processing unit]] (CPU) and [[graphics processing unit]] (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwidth. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>https://www.apple.com/newsroom/2022/03/apple-unveils-m1-ultra-the-worlds-most-powerful-chip-for-a-personal-computer/</ref> The M1 runs Apple's [[macOS]] and [[iPadOS]], Initial support for the M1 SoC in the [[Linux|Linux kernel]] was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == M1 Chip Variants == === A14 === [[File:Apple A14.jpg|thumb|Apple A14 Bionic, the chip M1 is based on.]] The Apple A14 Bionic features an Apple-designed 64-bit, six-core CPU, implementing ARMv8 with two high-performance cores called “Firestorm” and four energy-efficient cores called “Icestorm”.<ref>[https://www.youtube.com/live/KR0g-1hnQPA?si=0l-0ixbkIdH8_pLf https://www.youtube.com/live/KR0g-1hnQPA]</ref> The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big. LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[https://www.youtube.com/watch?v=BCvL8O0-Qwo https://www.youtube.com/watch?v=BCvL8O0-Qwo&t=4m18s]</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>https://www.anandtech.com/show/17024/apple-m1-max-performance-review</ref> {| class="wikitable" |+SoCs of the "Firestorm" and "Icestorm" microarchitectures. !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>https://www.apple.com/mac/m1/</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>https://support.apple.com/kb/SP858?locale=en_US</ref><ref>https://support.apple.com/kb/SP865?locale=en_US</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>https://borderpolar.com/tech/apple-m1-benchmarks/</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>https://www.nytimes.com/wirecutter/reviews/best-macbooks/</ref><ref>https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: * [[File:Macbook Pro 13" M1 2020.jpg|thumb|M1 Macbook Pro]] * Macbook Air 2020 (M1) - base model has binned, 7-Core GPU * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) * iPhone 12 and 12 mini (A14) * iPhone 12 Pro and 12 Pro Max (A14) * iPad air 4(th generation) (A14) * iPad (10th generation) (A14) and all the devices respective variants. == References == {{DEFAULTSORT:Apple M1}} 70f3a38de861d01af83507ad07538114dc4b2df2 0 240 3350 2885 2025-08-08T09:30:28Z Hamachitan 222 /* Introduction */ Remove redundant first heading wikitext text/x-wiki {{Cleanup|Incomplete page}}{{Needs Citations}} When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your distribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most derivative distributions. === General Information === ==== Multi Booting ==== [[File:GRUB with ubuntu and windows vista.png|alt=A black and white grub menu, it contains entries for Ubuntu Linux and Windows Vista|thumb|GRUB, with entries for [[Ubuntu]] and Windows Vista, an example of ''dual booting.'']] [[Multi Booting]] (Or often referred to as 'Dual Booting') is the process of installing multiple [[Operating System|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completely removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to partition the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly recommended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi Booting]] page. ==== Finding Alternatives or Workarounds for Apps ==== Often there is at least one [[application]] missing on Linux or an app that is missing some features or is buggy so you'll find yourself looking for alternative options. There also sometimes is the issue that your distribution doesn't have an app but another distribution does have it. A good place to start when looking for alternatives is [https://alternativeto.net AlternativeTo] which is a crowdsourced site useful to find alternatives for almost any app. Other useful sites include [https://www.privacytools.io Privacy Tools] and [https://awesome-privacy.xyz Awesome Privacy] with a privacy focused list of apps. When looking for workarounds for apps not supported for your distribution you should first check [https://flathub.org Flathub] and [https://snapcraft.io Snapcraft] (Note that [[Snap|Snaps]] are known to have performance issues) if your app is available there as they offer support for most distributions. If a steam game lacks native Linux support try checking [https://www.protondb.com ProtonDB] if Valve's proton tool supports your game. [https://www.winehq.org Wine] is also an option to run Windows apps on Linux. === Moving between specific Operating Systems === ==== Moving to Linux from MacOS ==== ==== Moving to Linux from Windows ==== == General Information == [[Category:Guides]] 8fba964443b864b0bf7b7e0a479589b7cc09e39d 0 322 3351 3315 2025-08-08T09:30:38Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{Needs Citations}}{{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the [[Linux|Linux kernel]], released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. == Usage on [[Operating System|Operating Systems]] == [[Linux Distributions|Linux distributions]] which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * [[Sabotage]] * [[Morpheus Linux]] * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against glibc. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. == See also == * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] [[Category:Software]] 10c95c155e6f24f05f21298399903ce5731f943d 0 279 3352 3334 2025-08-08T09:30:48Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, ppc64, x86_64 | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == This distribution stands out by having two primary variations of the distribution: OpenSUSE Tumbleweed is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. OpenSUSE Leap is the point release version, with a new release every year with older and more stable packages meant for business use. === openSUSE Slowroll === Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. [[Category:Linux Distributions]] d279d3e4d3c728804e9c69a897a00d341ecf26e4 0 653 3353 2778 2025-08-08T09:31:18Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox|title=Pop!_OS|image=[[File:Pop! OS Icon.svg|frameless]]|caption=The Pop!_OS logo|releasestatus=Maintained|packagemanager=[[Pacman]]|defaultdesktops=COSMIC|usagetype=Desktop|architectures=x86_64|website=Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX]|releasemodel=Rolling release}}Pop!_OS is a free and open-sourced [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]], based on [[GNOME]], called [[COSMIC]]. Pop!OS is developed by American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. == <u>Features</u> == * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle e02051464688632811cf8c4735bab7e22395f0de 0 440 3354 2072 2025-08-08T09:31:44Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = ROSA Linux | image = [[File:ROSA_Linux_Logo.png|thumb]] | caption = The ROSA Linux logo | releasestatus = Abandoned | releasemodel = Stable | packagemanager = [https://rpm-software-management.github.io/ DNF package manager] | defaultdesktops = GNOME, [[KDE Plasma]], LXQt, [[Xfce]] | usagetype = Desktop, Server | architectures = P5 (i586), x86_64 | website = [https://rosa.ru/rosa-fresh-12/ rosa.ru/rosa-fresh-12] }} [[File:Rosalinux_desktop_showcase.jpeg|thumb|ROSA Linux Fresh 12 running on KDE Plasma 5 and has open Dolphin, Gwenview and mpvplayer]] '''ROSA Linux''' is a [[Linux Distributions|Linux distribution]] built around the '''OpenMandriva''', offering closed-source software such as Adobe Flash Player, proprietary multimedia codecs. It was initially developed by AO NTC IT ROSA. (rus. - АО «НТЦ ИТ РОСА») == Focus on KDE Plasma as the desktop environment. == ROSA Linux is known for its focus on the KDE Plasma desktop environment, which offers a rich graphical interface and extensive customization options. This makes it an attractive choice for users who appreciate a modern and aesthetically pleasing desktop experience. == Applications == The distribution includes a wide range of pre-installed applications, covering essential tasks such as web browsing, multimedia playback, and office productivity, while also providing access to a comprehensive software repository for additional applications. == Ease of use == One of the key features of ROSA Linux is its commitment to user experience, with an emphasis on ease of use and accessibility. The distribution is designed to be intuitive, making it suitable for both newcomers to Linux and experienced users. It also supports multiple languages, catering to a diverse user base. == Multiple editions. == ROSA Linux is available in several editions, including ROSA Fresh, which is aimed at general users and features the latest software updates, and ROSA Enterprise, which is tailored for business environments and focuses on stability and long-term support. With a strong emphasis on community involvement and open-source principles, ROSA Linux encourages contributions from users and developers alike. It has gained popularity in various regions, particularly in Russia and Eastern Europe, and continues to be a viable option for those seeking a reliable and visually appealing Linux distribution. 0b0cc9c430fc2f4b11386206eb0bcb56c3f7be9d 3359 3354 2025-08-08T09:33:52Z Madonuko 140 Strip leading empty lines; remove fullstops from headings wikitext text/x-wiki {{Needs_Citations}}{{DistributionInfobox | title = ROSA Linux | image = [[File:ROSA_Linux_Logo.png|thumb]] | caption = The ROSA Linux logo | releasestatus = Abandoned | releasemodel = Stable | packagemanager = [https://rpm-software-management.github.io/ DNF package manager] | defaultdesktops = GNOME, [[KDE Plasma]], LXQt, [[Xfce]] | usagetype = Desktop, Server | architectures = P5 (i586), x86_64 | website = [https://rosa.ru/rosa-fresh-12/ rosa.ru/rosa-fresh-12] }} [[File:Rosalinux_desktop_showcase.jpeg|thumb|ROSA Linux Fresh 12 running on KDE Plasma 5 and has open Dolphin, Gwenview and mpvplayer]] '''ROSA Linux''' is a [[Linux Distributions|Linux distribution]] built around the '''OpenMandriva''', offering closed-source software such as Adobe Flash Player, proprietary multimedia codecs. It was initially developed by AO NTC IT ROSA. (rus. - АО «НТЦ ИТ РОСА») == Focus on KDE Plasma as the desktop environment == ROSA Linux is known for its focus on the KDE Plasma desktop environment, which offers a rich graphical interface and extensive customization options. This makes it an attractive choice for users who appreciate a modern and aesthetically pleasing desktop experience. == Applications == The distribution includes a wide range of pre-installed applications, covering essential tasks such as web browsing, multimedia playback, and office productivity, while also providing access to a comprehensive software repository for additional applications. == Ease of use == One of the key features of ROSA Linux is its commitment to user experience, with an emphasis on ease of use and accessibility. The distribution is designed to be intuitive, making it suitable for both newcomers to Linux and experienced users. It also supports multiple languages, catering to a diverse user base. == Multiple editions == ROSA Linux is available in several editions, including ROSA Fresh, which is aimed at general users and features the latest software updates, and ROSA Enterprise, which is tailored for business environments and focuses on stability and long-term support. With a strong emphasis on community involvement and open-source principles, ROSA Linux encourages contributions from users and developers alike. It has gained popularity in various regions, particularly in Russia and Eastern Europe, and continues to be a viable option for those seeking a reliable and visually appealing Linux distribution. 30bb0a198d3efc86b8e9e2e18123285c559eb3a3 0 225 3355 2996 2025-08-08T09:32:01Z Hamachitan 222 /* Introduction */ Remove redundant first heading wikitext text/x-wiki {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64 | website = [https://redhat.com/rhel/ redhat.com] }} [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business customers.<ref>https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. == References == <references /> [[Category:Linux Distributions]] 1044036e058c49810694712a90534e4edb3d97c9 0 447 3356 2883 2025-08-08T09:32:11Z Hamachitan 222 /* Introduction */ Remove redundant first heading wikitext text/x-wiki {{Needs Citations}} Self-hosting is a rewarding practice that allows you to reduce reliance on cloud services, giving you much greater control and privacy over the data you own. By self-hosting, the services you use, and by extension anything you store with those services, reside on your own hardware rather than third-party servers. Essentially, the “cloud” is just someone else's computer, often a large, multi-billion-dollar infrastructure. However, with self-hosting, you own the data on the devices you manage. == What is Self-Hosting? == Self-hosting often refers to the process of running and managing your own services on personal hardware such as a laptop, desktop, single-board computer, or even an enterprise-grade server. This means you can set up and operate services for yourself, your family, or others without depending on external cloud platforms. == What Can I Host? == There are numerous possibilities for self-hosting, depending on your needs. Some popular options include: * Email server * Password manager * Personal website * File hosting service * Media server * VPN (Virtual Private Network) == Do I Need Anything Special to Self-Host? == [[File:Homelab.jpg|thumb|Example of an enterprise grade homelab]] The requirements are minimal. You can self-host using almost any device, from an old, cheap laptop to a single-board computer like a Raspberry Pi. Some enthusiasts take this a step further and use second-hand enterprise equipment from real data center infrastructure to host their services. These setups are often referred to as “HomeLabs.” However, anything that can connect to the internet or your local area network can be sufficient. == The Challenges of Self-Hosting == Like everything in life, self-hosting has its challenges. When hosting services at home, you are responsible for maintaining and fixing any problems that arise. Unlike cloud services, which are typically plug-and-play, homelabs require regular maintenance to ensure stable operation. Below are some challenges many homelab users encounter. === Common Problems === * '''Electricity Usage''' - One of the main concerns with starting a homelab is power consumption. As your homelab grows, so will its electricity usage. Additionally, the services you run rely on your home's power grid, meaning power outages can affect your services. [[File:Speedtest.png|thumb|Example of a users internet speed.]] * '''Internet Speed''' - Not all internet connections are equal. When exposing services to the outside world, consider how much bandwidth they will consume. A slow connection or data caps can limit what you can host effectively. Residential internet plans might not support the load or violate fair use policies. Like the electricity usage, you are relying on the reliance your ISP provides. * '''Natural Disasters''' - Hosting services in areas prone to natural disasters poses risks. If a disaster damages your homelab, your data may be lost along with the equipment. * '''Vulnerabilities''' - Even with the latest software and hardware, vulnerabilities persist. Tools like Shodan.io scan for exposed services, potentially attracting malicious actors. Without sufficient protection, your services may be at risk. * '''Hardware Failures''' - Nothing lasts forever. Self-hosted services depend on your hardware, which will need maintenance and occasional replacement. Hard drives, in particular, are susceptible to failure over time. * '''Sound''' - Unlike a laptop or a single-board computer, enterprise equipment is not built to be quiet. It is designed to run cool and avoid failure, which often results in high-pitched fan noise due to large amounts of airflow. * '''Dust''' - Most homelabs are not housed in ventilated data centers, leading to dust accumulation, which can clog and damage equipment. * '''User Error''' - Mistakes happen. Deleting the wrong files, modifying incorrect configurations, or failing to double-check changes can lead to data loss or downtime. == Solutions == [[File:Ups uninterruptible power supply.jpg|thumb|An example of an (UPS) Uninterruptible Power Supply]] * '''Electricity Usage''' - Use an Uninterruptible Power Supply (UPS). A UPS acts as a battery backup and protects against power surges. If the power goes out, the UPS switches to battery mode to keep your equipment running. UPS devices can range from small 600W models to large 10kW units that can power enterprise equipment for hours. * '''Internet Speed''' - If your internet is slow or capped, consider upgrading to a better plan if available. Some ISPs offer small business plans for residential users, providing higher speeds, service agreements, and multiple external IP addresses. * '''Natural Disasters''' - Perform regular off-site backups. Store data in locations unaffected by the same natural disasters as your homelab to ensure redundancy. * '''Vulnerabilities''' - To mitigate vulnerabilities some examples include: ** Keep all software and hardware up to date. ** Change default ports for commonly scanned services. ** Install a firewall. ** Use a VPN to access services instead of exposing them directly to the internet. ** Use encrypted protocols and storage. [[File:raid failure.png|thumb|An example of a drive failing in a raid.]] *'''Hardware Failures''' - Practice the 3-2-1 backup strategy: ** Keep at least THREE copies of your data. ** Use at least TWO types of storage. ** Keep at least ONE copy off-site. * '''Sound''' - To mitigate noise, consider buying fanless equipment, as fans are the primary source of noise. Alternatively, place the equipment in a room that is not frequently used to minimize sound. Keep in mind that fanless equipment carries a risk of overheating. * '''Dust''' - Regularly clean your equipment and store it in well-ventilated areas. Use compressed air or vacuum cleaners to remove dust. * '''User Error''' - Double-check all changes, avoid running unfamiliar commands, and thoroughly understand what you are deploying. a45f5ef423c4c9ac8818a11ab7a7bd68a0815c45 0 769 3357 3194 2025-08-08T09:32:21Z Hamachitan 222 /* Wayland Compositors */ Remove redundant first heading wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>https://gitlab.freedesktop.org/wayland/weston</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>https://gitlab.gnome.org/GNOME/mutter</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>https://github.com/KDE/kwin</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>https://github.com/riverwm/river</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>https://github.com/WayfireWM/wayfire</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>https://github.com/cage-kiosk/cage</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''Niri<ref>https://github.com/YaLTeR/niri</ref>''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |} ==References== <references /> a19f7cdfb1fe08864ce6e38d692e31366e7a6080 3365 3357 2025-08-08T19:32:30Z Lyon 224 Made Niri link to the Niri wiki page wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>https://gitlab.freedesktop.org/wayland/weston</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>https://gitlab.gnome.org/GNOME/mutter</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>https://github.com/KDE/kwin</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>https://github.com/riverwm/river</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>https://github.com/WayfireWM/wayfire</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>https://github.com/cage-kiosk/cage</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''[[Niri]]''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |} ==References== <references /> 6ac5d07ab41dcf78879384caa6bc651bf5827759 3378 3365 2025-08-09T12:14:18Z Solomoncyj 225 add cosmic-comp wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>https://gitlab.freedesktop.org/wayland/weston</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>https://gitlab.gnome.org/GNOME/mutter</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>https://github.com/KDE/kwin</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>https://github.com/riverwm/river</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>https://github.com/WayfireWM/wayfire</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>https://github.com/cage-kiosk/cage</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''[[Niri]]''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |Cosmic-comp<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |Cosmic |Rust |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |} ==References== <references /> e75e7523cb42a3a6a546b5bab5762e660e82eb37 0 306 3358 3078 2025-08-08T09:32:51Z Hamachitan 222 Tidy up heading levels wikitext text/x-wiki {{Work_In_Progress}} A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent GUI. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as dwm.  == Types of Window Manager == === Stacking/Floating Window Managers === Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm * [[Wayfire]] === Tiling Window Managers === Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * i3 * [[Sway]] * [[SwayFx]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] === Dynamic Window Managers === Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[dwl]] * qtile * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] === Scrollable Window Managers === Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[PaperWM]] * [[karousel]] * [[papersway]] * [[PaperWM.spoon]] [[Category:Terminology]] [[Category:Window Management Systems]] aa353c775f267f07ef300f856c4a4d4791ddd872 10 483 3360 2726 2025-08-08T12:56:59Z Atmois 13 Remove newline wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[ATL:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /> <includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]]}} </includeonly> <noinclude> {{/doc}}</noinclude> 10652b198b9e783d0e6919a74157eee7da57054a 10 523 3361 2732 2025-08-08T13:18:36Z Atmois 13 Edit from [[User:Madonuko]] to improve template wikitext text/x-wiki <includeonly><div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This template means the author of a page is still actively working on the page, and this serves to notify other editors to check with them before potentially creating conflicting changes and to notify the staff that it may not meet the wiki's [[ATL:Guidelines|guidelines]] yet.</div></div><templatestyles src="Module:Mbox/styles.css" /></includeonly><noinclude>{{/doc}}</noinclude> efce70105ae18cd4a3fffe04150752f317cca310 2 819 3362 3310 2025-08-08T16:19:08Z Madonuko 140 hamachi yum wikitext text/x-wiki {{DISPLAYTITLE:ハマチたん}} Romanised as ''Hamachi-tan''. Experimental bot by [[User:Madonuko]]. This bot is always run with nuko supervision. == Suggestions & Requests == Feel free to mention/ping Mado on Discord. == History == On 2025-08-08, Mado wanted a way to tidy up formats of wiki pages automatically. Realising there is no good client-side-only tool available on Linux, it was quickly decided that creating a wiki bot might be overpowered but is the simplest way. Thus, <ruby>'''ハマチたん'''<rt>hamachitan</rt></ruby> was born, whose name was decided by the fact Mado likes the Japanese fish [[wikipedia:ja:ハマチ|ハマチ]], young Japanese amberjack. d3486ee3c1e2095bb949f80c59fef70fb72bd1c8 0 772 3363 3251 2025-08-08T16:42:46Z Madonuko 140 tidy up format, add guide warnings, etc. wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>http://www.artima.com/intv/pythonP.html</ref> as a successor to the ABC programming language. He released the first version (0.9.0)<ref>https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>https://survey.stackoverflow.co/2022/</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>https://www.python.org/doc/av</ref> Python is currently the most used programming language among developers<ref>https://www.tiobe.com/tiobe-index/</ref>, used daily for lots of general-purpose software. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and also IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE.<!-- However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. --> == pip (Package Manager) == [https://pypi.org/project/pip/ pip] is Python's Package Manager, through pip you can install all the libraries needed for your project to run. pip stands for "''pip Installs Packages"''<ref>https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for</ref>. pip connects to an online software repository (PyPI). pip was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain pip and venv. === Installation for pip === Python 3.4+ included pip by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash"> python -m ensurepip --upgrade </syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script from https://bootstrap.pypa.io/get-pip.py. # Open a new [[terminal]] and [[cd]] to the folder containing the file # <code>python get-pip.py</code> === Installing packages with pip === {{Guide Warning}} pip install package-name == Virtual Environments (VENV) == The venv module allows users to create Virtual Environments each with their own independent modules and libraries, This is useful for isolating project dependencies or debugging. Created by Ian Bicking (the same developer who created pip), it is now maintained by the Python Package Authority (PyPA). == Installation == {{Guide Warning}} === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> sudo apt update sudo apt install python3 python3-pip </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash"> sudo pacman -Syu python python-pip </syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight lang="bash"> sudo yum install python3 python3-pip </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> sudo yum install python3 python3-pip </syntaxhighlight> == '''Setup Python venv''' == {{Guide Warning}} When installing pip packages system-wide as root you will typically see a message like this one: <syntaxhighlight lang="shell-session"> [user@hostname ~]$ sudo pip install pyperclip Collecting pyperclip Downloading pyperclip-1.9.0.tar.gz (20 kB) Preparing metadata (setup.py) ... done Building wheels for collected packages: pyperclip Building wheel for pyperclip (setup.py) ... done Created wheel for pyperclip: filename=pyperclip-1.9.0-py3-none-any.whl size=11014 sha256=696d851be7b0d99fe8112ddf5c6ebc2b9444464b2a729911930d64bebc124c35 Stored in directory: /root/.cache/pip/wheels/cc/ae/36/ee17d1de094fcb61e24106cb329b5103861e819f94bef5e10a Successfully built pyperclip Installing collected packages: pyperclip Successfully installed pyperclip-1.9.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv </syntaxhighlight> Running pip as root can result in conflicts, broken packages and security risks.<ref>https://askubuntu.com/questions/802544/is-sudo-pip-install-still-a-broken-practice</ref> There are two possible responses to this situation: * See whether your distribution offers a system package to suit your needs. Depending on the distribution, system packages may be outdated, but this option should be tried first unless you are actively developing software. For example, with the Python module pyperclip mentioned above, there was a system package available that could fill the need, python3-pyperclip. * Or, if you are writing your own software, you can heed the warning as written and use the following instructions: python -m venv path/to/venv/ source path/to/venv/bin/activate The first line creates the folder containing the venv and the second line activates it. If you are not using bash, things may change slightly. For example, a user of the [[fish]] shell would instead run source venv/bin/activate.fish You'll know that a venv is currently active from an altered prompt such as this one: <syntaxhighlight lang="shell-session"> (venv) [user@hostname ~]$ </syntaxhighlight> With a venv loaded, all pip commands such as "pip install" and "pip uninstall" will affect only that venv. All Python code run with the venv's installation of Python will prefer to import the venv's libraries over any system libraries. (The command "which python" can help ensure that it is truly the venv Python as opposed to, say, the system "/usr/bin/python" that is running.) Lastly, a user who wishes to turn off a venv for the time being will only need to give the command "deactivate" to the shell. Further information about venv can be found in [https://docs.python.org/3/library/venv.html Python's official documentation]. == References == 0cd10df37b8deae4492f6f6e041f6ec78342cd7a 3370 3363 2025-08-09T10:24:38Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.5 - 11 June 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>[http://www.artima.com/intv/pythonP.html The Making of Python], Bill Venners, 2003-01-13 (Accessed: 2025-08-09)</ref> as a successor to the ABC programming language. He released the first version (0.9.0)<ref>[https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html The History of Python: A Brief Timeline of Python], Guido van Rossum, 2009-01-20 (Accessed: 2025-08-09)</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>[https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html Python Insider: Python 2.7.18, the last release of Python 2], Benjamin Peterson, 2020-04-20 (Accessed: 2025-08-09)</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>[https://survey.stackoverflow.co/2022/ Stack Overflow Developer Survey 2022], Stack Overflow, 2022-08-09 (Accessed: 2025-08-09)</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>[https://www.python.org/doc/av Audio/Video Instructional Materials for Python], Python Software Foundation, 2025-08-09 (Accessed: 2025-08-09)</ref> Python is currently the most used programming language among developers<ref>[https://www.tiobe.com/tiobe-index/ TIOBE Index], Paul Jansen, 2025-08-09 (Accessed: 2025-08-09)</ref>, used daily for lots of general-purpose software. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and also IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE.<!-- However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. --> == pip (Package Manager) == [https://pypi.org/project/pip/ pip] is Python's Package Manager, through pip you can install all the libraries needed for your project to run. pip stands for "''pip Installs Packages"''<ref>[https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for python - What does PIP stand for? - Unix & Linux Stack Exchange], Unix & Linux Stack Exchange, 2014-11-24 (Accessed: 2025-08-09)</ref>. pip connects to an online software repository (PyPI). pip was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain pip and venv. === Installation for pip === Python 3.4+ included pip by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash"> python -m ensurepip --upgrade </syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script from https://bootstrap.pypa.io/get-pip.py. # Open a new [[terminal]] and [[cd]] to the folder containing the file # <code>python get-pip.py</code> === Installing packages with pip === {{Guide Warning}} pip install package-name == Virtual Environments (VENV) == The venv module allows users to create Virtual Environments each with their own independent modules and libraries, This is useful for isolating project dependencies or debugging. Created by Ian Bicking (the same developer who created pip), it is now maintained by the Python Package Authority (PyPA). == Installation == {{Guide Warning}} === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> sudo apt update sudo apt install python3 python3-pip </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash"> sudo pacman -Syu python python-pip </syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight lang="bash"> sudo yum install python3 python3-pip </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> sudo yum install python3 python3-pip </syntaxhighlight> == '''Setup Python venv''' == {{Guide Warning}} When installing pip packages system-wide as root you will typically see a message like this one: <syntaxhighlight lang="shell-session"> [user@hostname ~]$ sudo pip install pyperclip Collecting pyperclip Downloading pyperclip-1.9.0.tar.gz (20 kB) Preparing metadata (setup.py) ... done Building wheels for collected packages: pyperclip Building wheel for pyperclip (setup.py) ... done Created wheel for pyperclip: filename=pyperclip-1.9.0-py3-none-any.whl size=11014 sha256=696d851be7b0d99fe8112ddf5c6ebc2b9444464b2a729911930d64bebc124c35 Stored in directory: /root/.cache/pip/wheels/cc/ae/36/ee17d1de094fcb61e24106cb329b5103861e819f94bef5e10a Successfully built pyperclip Installing collected packages: pyperclip Successfully installed pyperclip-1.9.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv </syntaxhighlight> Running pip as root can result in conflicts, broken packages and security risks.<ref>[https://askubuntu.com/questions/802544/is-sudo-pip-install-still-a-broken-practice package management - Is `sudo pip install` still a broken practice? - Ask Ubuntu], Ask Ubuntu, 2016-07-25 (Accessed: 2025-08-09)</ref> There are two possible responses to this situation: * See whether your distribution offers a system package to suit your needs. Depending on the distribution, system packages may be outdated, but this option should be tried first unless you are actively developing software. For example, with the Python module pyperclip mentioned above, there was a system package available that could fill the need, python3-pyperclip. * Or, if you are writing your own software, you can heed the warning as written and use the following instructions: python -m venv path/to/venv/ source path/to/venv/bin/activate The first line creates the folder containing the venv and the second line activates it. If you are not using bash, things may change slightly. For example, a user of the [[fish]] shell would instead run source venv/bin/activate.fish You'll know that a venv is currently active from an altered prompt such as this one: <syntaxhighlight lang="shell-session"> (venv) [user@hostname ~]$ </syntaxhighlight> With a venv loaded, all pip commands such as "pip install" and "pip uninstall" will affect only that venv. All Python code run with the venv's installation of Python will prefer to import the venv's libraries over any system libraries. (The command "which python" can help ensure that it is truly the venv Python as opposed to, say, the system "/usr/bin/python" that is running.) Lastly, a user who wishes to turn off a venv for the time being will only need to give the command "deactivate" to the shell. Further information about venv can be found in [https://docs.python.org/3/library/venv.html Python's official documentation]. == References == b4453d313b7b7bc864e6ca123c924e12d823e7a1 0 171 3364 3331 2025-08-08T19:26:26Z Lyon 224 Added a small note about flakes being experimental BUT stable and trusted. wikitext text/x-wiki {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }}'''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such as nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental (But mostly stable and trusted) feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> [[Category:Linux Distributions]] 4da2a2d357cfc73d96e2dcd08b0e42dc1180defe 2 3 3366 2840 2025-08-08T20:06:42Z Amadaluzia 52 Refactor to make it all worse wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <functional> #include <print> using String = std::string; class Person { virtual String description() = 0; }; using SocialPair = struct { String service; String username; }; class Amadaluzia : Person { public: String name = "Artur Manuel"; int age = 17; std::vector<String> interests{ "Programming", "CLI development", "GUI development", "Web development", "Library development", "System administration", "Walking", "Climbing", "Math", "Learning", "Exercise", "Sports", "Socialising", "Writing", "Photography", "Video editing", "Movie production", "Techno music", "Shoegaze", "Alternative Rock", }; std::vector<SocialPair> socials = { {"Email", "amad@atl.tools"}, {"Email (tutanota.com alt)", "amadaluzia@tutanota.com"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Matrix (pub.solar alt)", "@amadaluzia:pub.solar"}, {"Matrix (envs.net alt)", "@amadaluzia:envs.net"}, {"libera.chat", "amadaluzia"}, {"oftc.net", "amadaluzia"}, {"Revolt", "amadaluzia#3242"}, {"Mastodon", "@amadaluzia@bsd.cafe"}, {"Discord", "amadaluzia"}, {"Discord (alt)", "balke.nix"}, }; String description() override; }; String Amadaluzia::description() { String result{}; result += std::format("Good day, my name is {}, commonly known online as \"amadaluzia\". I am a {}\n", name, age); result += "year old Portuguese-Italian resident of the UK. You may have seen me in many\n"; result += "programming spaces, however, I am keenly interested in many other topics. More\n"; result += "specifically, I am interested in:\n"; for (auto interest : interests) result += std::format("- {}\n", interest); result += "I am also present on many social media platforms, even multiple times! Moreover, I\n"; result += "have pretty much the same name everywhere, so you can reliably find me. But I will\n"; result += "share my social platforms here as I use many decentralised services. Here I am:\n"; for (auto const &[service, username] : socials) result += std::format("- {} on {}\n", username, service); result += "\nIf you can find any ways of optimising this program, let me know, as long as the\n"; result += "it's kept to Amadaluzia::description(). Thank you for reading!\n"; return result; } int main(void) { Amadaluzia amadaluzia; std::println("{}", amadaluzia.description()); }</syntaxhighlight> fd1d56976e3b1e472b0c4a19627d58105f8214be 0 217 3367 3329 2025-08-09T01:11:35Z Solomoncyj 225 feat: Release system, pkg mgmt system, added stuff to side template wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}}[[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> == Release system == Fedora current follows a system where a new version is released every 6 months<ref>https://docs.fedoraproject.org/en-US/releases/lifecycle/</ref>, which brings breaking changes, such as major library versions.<ref>https://docs.fedoraproject.org/en-US/releases/lifecycle/</ref> System upgrades are usually handled offline to prevent system breakage == The package management system == the Package manager [[dnf]] , is usually called with the following arguments * <code>sudo dnf up</code> --- updates syetem pacjages * <code>sudo dnf in <pkg names> <...></code> --- install new packages * <code>sudo dnf rm <pkg names> <...></code> --- remove packages * <code>sudo dnf system-upgrade --relesever=<rel></code> --- updates syetem version and packages<ref>https://dnf.readthedocs.io/</ref> == References == <references /> [[Category:Linux Distributions]] 5ff0fc468914151f3035a7fe23a35d5b754e69c3 3368 3367 2025-08-09T09:49:01Z Atmois 13 Change logo in infobox to frameless wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}}[[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>https://docs.fedoraproject.org/en-US/project/#_our_vision</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel</ref> == Release system == Fedora current follows a system where a new version is released every 6 months<ref>https://docs.fedoraproject.org/en-US/releases/lifecycle/</ref>, which brings breaking changes, such as major library versions.<ref>https://docs.fedoraproject.org/en-US/releases/lifecycle/</ref> System upgrades are usually handled offline to prevent system breakage == The package management system == the Package manager [[dnf]] , is usually called with the following arguments * <code>sudo dnf up</code> --- updates syetem pacjages * <code>sudo dnf in <pkg names> <...></code> --- install new packages * <code>sudo dnf rm <pkg names> <...></code> --- remove packages * <code>sudo dnf system-upgrade --relesever=<rel></code> --- updates syetem version and packages<ref>https://dnf.readthedocs.io/</ref> == References == <references /> [[Category:Linux Distributions]] 24a8498ca73c132a5ab8b7fc88dc051d36f78c7a 3369 3368 2025-08-09T10:24:37Z Solomoncyj 225 fix: set up referenses wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}}[[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>https://web.archive.org/web/20031001204515/http://www.fedora.us/</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[ https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref> == Release system == Fedora current follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], </nowiki>'''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</nowiki></ref> System upgrades are usually handled offline to prevent system breakage == The package management system == the Package manager [[dnf]] , is usually called with the following arguments * <code>sudo dnf up</code> --- updates system packages * <code>sudo dnf in <pkg names> <...></code> --- install new packages * <code>sudo dnf rm <pkg names> <...></code> --- remove packages * <code>sudo dnf system-upgrade --relesever=<rel></code> --- updates syetem version and packages<ref>[https://dnf.readthedocs.io/<nowiki> DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</nowiki></ref> == References == <references /> [[Category:Linux Distributions]] 523cf60e65f388844661fafa72f29d032249c4eb 3371 3369 2025-08-09T10:31:58Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}}[[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[ https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref> == Release system == Fedora current follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], </nowiki>'''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</nowiki></ref> System upgrades are usually handled offline to prevent system breakage == The package management system == the Package manager [[dnf]] , is usually called with the following arguments * <code>sudo dnf up</code> --- updates system packages * <code>sudo dnf in <pkg names> <...></code> --- install new packages * <code>sudo dnf rm <pkg names> <...></code> --- remove packages * <code>sudo dnf system-upgrade --relesever=<rel></code> --- updates syetem version and packages<ref>[https://dnf.readthedocs.io/<nowiki> DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</nowiki></ref> == References == <references /> [[Category:Linux Distributions]] f50f6db5b65e2a6490858e693649643687313349 0 310 3372 2932 2025-08-09T10:36:11Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Alpine Linux | image = [[File:alpinelinux-logo.svg|thumb]] | releasestatus = Maintained | releasemodel = Point or Rolling | packagemanager = [[apk]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[MATE]], [[LXQt]] | usagetype = Container, Embedded, Server, Desktop | architectures = amd64, aarch64, armel, armhf, i686, ppc64le, s390x, loongarch64 | website = [https://www.alpinelinux.org/ alpinelinux.org] }} Alpine Linux is a lightweight Linux distribution that aims to "small", "simple" and "secure".<ref name=":0">[https://alpinelinux.org/about/ about | Alpine Linux], Alpine Linux Development Team, 2025-02-14 (Accessed: 2025-08-09)</ref> It is one of the few distributions that do not use the GNU C Library or GNU coreutils by default. Alpine, by default, follows a point release update model while its edge repositories follow a rolling release model. Twice a year, typically on November and May, a new stable version is branched from edge and released.<ref>[https://alpinelinux.org/releases/ Alpine release branches | Alpine Linux], Alpine Linux Development Team, 2025-07-15 (Accessed: 2025-08-09)</ref> == Features == Alpine's main feature is its small size. Its minimal system requirements and ease of deployability makes it suitable for use in containers, embedded systems and other systems with very limited resources. All user-space binaries in Alpine are compiled as position-independent executables with stack-smashing protection for security reasons.<ref name=":0" /> Alpine comes preinstalled with configuration scripts which allow quick configuration and installation of the system.<ref>[[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts] <span style="color:#fc493b">[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts] <sup>🍣DEAD?]</ref> Alpine also offers a web-server based configuration tool named the Alpine Configuration Framework (ACF).<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Configuration_Framework_Design Alpine Configuration Framework Design - Alpine Linux], Alpine Linux Wiki, 2025-03-10 (Accessed: 2025-08-09)</ref> Alpine offers a "diskless installation"<ref>[https://wiki.alpinelinux.org/wiki/Installation#Installation_Overview Installation - Alpine Linux], Alpine Linux Wiki, 2025-07-30 (Accessed: 2025-08-09)</ref>, allowing it to be installed to and be used from RAM. == Differences from other Linux Distributions == * Alpine uses musl as its standard C library. This compromises its support for some programs such as Electron based applications<ref>[https://wiki.alpinelinux.org/wiki/APKBUILD_examples:JavaScript APKBUILD examples:JavaScript - Alpine Linux], Alpine Linux Wiki, 2023-05-13 (Accessed: 2025-08-09)</ref> and the NVIDIA drivers.<ref>[https://wiki.alpinelinux.org/wiki/NVIDIA NVIDIA - Alpine Linux], Alpine Linux Wiki, 2025-05-09 (Accessed: 2025-08-09)</ref> * Alpine by default lacks the standard base utilities that other distributions come with such as GNU bash, coreutils, findutils, pciutils, usbutils, util-linux, udev. Instead of these, their BusyBox implementations are used. This is what makes Alpine so small in size, yet this also causes compatibility issues with many programs and scripts as their BusyBox implementations lack many features of their counterparts<ref>[https://wiki.alpinelinux.org/wiki/How_to_get_regular_stuff_working How to get regular stuff working - Alpine Linux], Alpine Linux Wiki, 2025-07-20 (Accessed: 2025-08-09)</ref>. To solve these compatibility issues, the user can install the standard version of these programs as they wish. * Alpine does not use systemd. Instead, it uses BusyBox for its init process and OpenRC for service management.<ref>[https://wiki.alpinelinux.org/wiki/OpenRC OpenRC - Alpine Linux], Alpine Linux Wiki, 2025-08-08 (Accessed: 2025-08-09)</ref> * Alpine uses its own package manager, the "Alpine Package Keeper" (apk).<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper Alpine Package Keeper - Alpine Linux], Alpine Linux Wiki, 2025-05-25 (Accessed: 2025-08-09)</ref> * Alpine uses the LTS branch of the Linux kernel by default.<ref>[https://github.com/alpinelinux/alpine-conf/blob/55ec2cf0504195ee60f68b21a29607302f8a15d0/setup-disk.in#L1489 alpine-conf/setup-disk.in at 55ec2cf0504195ee60f68b21a29607302f8a15d0 · alpinelinux/alpine-conf · GitHub], ncopa, 2025-07-15 (Accessed: 2025-08-09)</ref> == References == c58e30eaa76c51a6e863e7f7e68338379713a19f 0 169 3373 3327 2025-08-09T10:40:48Z Solomoncyj 225 /* List of Package Managers */ add rpm to opensuse wikitext text/x-wiki {{Needs_Citations}}[[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories == List of Package Managers == All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained by the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper]/[[Rpm]], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] [[Category:Terminology]] 422235f3ce171244069ecb1124edea2f2a30a934 0 228 3374 3317 2025-08-09T11:53:57Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}}The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. [[Package|Packages]] that enter the extra repository can be directly installed with pacman.<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with AUR helpers. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, AUR helpers have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, pacman is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>[https://wiki.archlinux.org/title/PKGBUILD PKGBUILD], ArchWiki, 2025-06-12 (Accessed: 2025-08-09)</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>[https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions Creating packages], ArchWiki, 2025-06-13 (Accessed: 2025-08-09)</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>[https://wiki.archlinux.org/title/Namcap namcap], ArchWiki, 2025-06-16 (Accessed: 2025-08-09)</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability. == References == <references /> [[Category:Terminology]] c226e7d18133c8405cd62c97f6b08a304256d1cd 0 250 3375 3164 2025-08-09T11:55:08Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Instructions need to be split onto their own page under the Guides namespace}}{{Cleanup|Incomplete page}}[[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>[https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/ NVIDIA Hopper Architecture In-Depth | NVIDIA Technical Blog], Michael Andersch, Greg Palmer, Ronny Krashinsky, Nick Stam, Vishal Mehta, Gonzalo Brito and Sridhar Ramaswamy, 2022-03-22 (Accessed: 2025-08-09)</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. == Ana/Miniconda Setup == While not required, it is heavily recommended to use ''conda'' to manage Python libraries required by various machine learning and artificial intelligence projects from places like GitHub and Hugging Face. Conda exists as a distinct virtual environment separate from the native distribution's Python packages. Users may specify version number and install additional plugins as well as packages within an environment utilizing conda. It is recommended to read the Linux setup for Miniconda on their [https://www.anaconda.com/docs/getting-started/miniconda/install#linux official website]. The install for Miniconda is very unorthodox compared to installing other packages on a Linux system - be mindful. == Stable Diffusion Setup - WebUI (Forge) == [[File:Cat.png|thumb|A cat generated using FLUX.1 [schnell].]] According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> Stable Diffusion WebUI Forge is a version of Stable Diffusion WebUI that offers additional support for FLUX.1 [dev] and FLUX.1 [schnell] models. For some users, using the Forge version may result in greater stability using FLUX as opposed to the vanilla version. Simply clone the Forge repository:<syntaxhighlight lang="bash"> git clone https://github.com/lllyasviel/stable-diffusion-webui-forge/issues </syntaxhighlight>...install required pip packages:<syntaxhighlight lang="bash"> pip3 install -r requirements.txt </syntaxhighlight>...and run the program:<syntaxhighlight lang="bash"> python3 launch.py </syntaxhighlight> ==== Extra notes ==== ===== Run options/flags ===== It is advisory to set additional launch parameters for better performance, e.g. using '''xformers''' for optimization or to specify a certain directory where models are stored. You can place these in a separate xxx.sh file to run instead of having to copy-and-paste large strings - here is an example:<syntaxhighlight lang="bash"> python3 launch.py --listen --xformers --enable-insecure-extension-access --cuda-malloc --port 7860 --vae-dir=/run/media/jennaannilyn/Pikmin3/models/vae --ckpt-dir=/run/media/jennaannilyn/Pikmin3/AI/ --lora-dir=/run/media/jennaannilyn/Pikmin3/AI/models/loras --no-half-vae </syntaxhighlight> === Installing and using Ollama on Linux === [[File:Ollama.png|thumb|Ollama says hi to ATL.]] According to Ollama's main page, Ollama is used to run open-source/open-weight, locally hosted Large Language Models. == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>[https://github.com/w-okada/voice-changer GitHub - w-okada/voice-changer: リアルタイムボイスチェンジャー Realtime Voice Changer], w-okada, 2022-08-09 (Accessed: 2025-08-09)</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU, c'''onsidering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> ==== The Deiteris Fork ==== Some users may prefer Deiteris's version, which may offer extra precision and performance for more advanced users. The process is almost identical, except that you must clone his fork:<syntaxhighlight lang="bash"> git clone https://github.com/deiteris/voice-changer </syntaxhighlight>...while consequently running a different Python command:<syntaxhighlight lang="bash"> python3 ./main.py </syntaxhighlight> == References == [[Category:Guides]] d19cfed5f9bd5b6ea3b06e78326d0e03c27c2e86 0 414 3376 3150 2025-08-09T12:07:41Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970s, adopted by the majority of UNIX systems.<ref>[https://dl.acm.org/doi/10.1145/2509136.2509515 <span style="color:#fc493b">https://dl.acm.org/doi/10.1145/2509136.2509515 <sup>🍣403]</ref> The language was initially implemented by Dennis Ritchie whilst working at Bell Labs, and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and pre-processors for their respective machines and instruction sets.<ref>[https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance Freedom and Portability - by Babbage - The Chip Letter], Babbage, 2024-05-05 (Accessed: 2025-08-09)</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>[https://en.cppreference.com/w/c/language/history History of C], cppreference.com, 2025-05-27 (Accessed: 2025-08-09)</ref> Some popular compilers for the C programming language include GNU GCC, Clang, TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the Clang compiler toolchain, however, for example, [[Illumos]]<ref>[https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/ Illumos Gets A New C Compiler | Hackaday], Al Williams, 2023-07-16 (Accessed: 2025-08-09)</ref> and [[Plan 9]]<ref>[https://9p.io/sys/doc/compiler.html <span style="color:#fc493b">https://9p.io/sys/doc/compiler.html <sup>🍣DEAD?]</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>[https://smlfamily.github.io/Basis/ Standard ML Basis Library], AT&T and Lucent Technologies, 2004-04-12 (Accessed: 2025-08-09)</ref><ref>[https://doc.rust-lang.org/beta/std/index.html std - Rust], doc.rust-lang.org, 2025-08-05 (Accessed: 2025-08-09)</ref><ref>[https://ziglang.org/documentation/master/std/ Zig Documentation], ziglang.org, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html All Classes (Java Platform SE 8 )], docs.oracle.com, 2025-06-30 (Accessed: 2025-08-09)</ref><ref>[https://www.scala-lang.org/api/current/ Scala 3], , 2025-07-29 (Accessed: 2025-08-09)</ref><ref>[https://ocaml.org/manual/5.2/api/index.html The OCaml API], , (Accessed: 2025-08-09)</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>[https://www.musl-libc.org/faq.html musl FAQ], , 2018-02-21 (Accessed: 2025-08-09)</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>[https://wiki.musl-libc.org/compatibility musl libc - Compatibility], , 2025-04-26 (Accessed: 2025-08-09)</ref><ref>[https://www.fefe.de/dietlibc/FAQ.txt <span style="color:#fc493b">https://www.fefe.de/dietlibc/FAQ.txt <sup>🍣DEAD?]</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>[https://wiki.osdev.org/C_Library C Library], OSDev Wiki, 2024-06-24 (Accessed: 2025-08-09)</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>[https://nullprogram.com/blog/2017/03/30/ How to Write Portable C Without Complicating Your Build], Chris Wellons, 2017-03-30 (Accessed: 2025-08-09)</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as GNU Autotools, CMake, Meson, Zig's build toolchain among a plethora others, however for ideological<ref>[https://suckless.org/sucks/ software that sucks less | suckless.org software that sucks less], , 2025-05-29 (Accessed: 2025-08-09)</ref><ref>[https://www.interaction-design.org/literature/topics/keep-it-simple-stupid What is Keep It Simple, Stupid (KISS)?], Interaction Design Foundation - IxDF, 2016-06-05 (Accessed: 2025-08-09)</ref><ref>[http://harmful.cat-v.org/software/GNU/auto-hell GNU Auto*hell], , (Accessed: 2025-08-09)</ref> and practical<ref>[https://twdev.blog/2021/08/cmake/ Why CMake sucks? - twdev.blog], Tomasz Wisniewski, 2021-08-06 (Accessed: 2025-08-09)</ref><ref>[https://silverhammermba.github.io/blog/2023/01/06/gradle Gradle still sucks | Floating little leaves of code], Maxwell Anselm, 2023-01-06 (Accessed: 2025-08-09)</ref><ref>[https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system Stop the autoconf insanity! Why we need a new build system. – Freecode], Andrew McCall, 2003-06-21 (Accessed: 2018-11-18)</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>[https://github.com/Mercury-Language/mercury GitHub - Mercury-Language/mercury: The Mercury logic programming system.], Mercury-Language, 2013-08-09 (Accessed: 2025-08-09)</ref><ref>[https://github.com/NetBSD/src GitHub - NetBSD/src: Automatic conversion of the NetBSD src CVS module, use with care.], NetBSD, 2025-08-09 (Accessed: 2025-08-09)</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, meta-programming and structural components of a C code base; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>[https://docs.kernel.org/process/5.Posting.html 5. Posting patches — The Linux Kernel documentation], The kernel development community, 2025-07-27 (Accessed: 2025-08-09)</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS|open source]] code bases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995–2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial,<ref>[https://web.mit.edu/~simsong/www/ugh.pdf <span style="color:#fc493b">https://web.mit.edu/~simsong/www/ugh.pdf <sup>🍣DEAD?]</ref> many attribute issues regarding C to fragmentation and portability issues,<ref>[http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful #ifdef Considered Harmful, or Portability Experience With C News], Henry Spencer, (Accessed: 2025-08-09)</ref> lack of type safety and primitive resource access checks,<ref>[https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review <span style="color:#fc493b">https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review <sup>🍣403]</ref> poor administration on part of the C Language Working Group,<ref>[https://cor3ntin.github.io/posts/c/ The problem with C | cor3ntin], cor3ntin, 2025-05-10 (Accessed: 2025-08-09)</ref> and overall worsening over time.<ref>[https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html C23 - What We Have To Suffer], Harry Fairhead, (Accessed: 2025-08-09)</ref><ref>[https://wiki.theory.org/YourLanguageSucks YourLanguageSucks], TheoryOrg, 2022-09-29 (Accessed: 2025-08-09)</ref> == References == <references /> [[Category:Programming Languages]] 5d1ca212ba7e45e906873f1917bdbf2f71610101 3377 3376 2025-08-09T12:11:19Z Madonuko 140 /* References */ fix HMCT shenanigans wikitext text/x-wiki C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970s, adopted by the majority of UNIX systems.<ref>[https://dl.acm.org/doi/10.1145/2509136.2509515 <span style="color:#fc493b">https://dl.acm.org/doi/10.1145/2509136.2509515 <sup>🍣403]</ref> The language was initially implemented by Dennis Ritchie whilst working at Bell Labs, and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and pre-processors for their respective machines and instruction sets.<ref>[https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance Freedom and Portability - by Babbage - The Chip Letter], Babbage, 2024-05-05 (Accessed: 2025-08-09)</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>[https://en.cppreference.com/w/c/language/history History of C], cppreference.com, 2025-05-27 (Accessed: 2025-08-09)</ref> Some popular compilers for the C programming language include GNU GCC, Clang, TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the Clang compiler toolchain, however, for example, [[Illumos]]<ref>[https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/ Illumos Gets A New C Compiler | Hackaday], Al Williams, 2023-07-16 (Accessed: 2025-08-09)</ref> and [[Plan 9]]<ref>[https://9p.io/sys/doc/compiler.html <span style="color:#fc493b">https://9p.io/sys/doc/compiler.html <sup>🍣DEAD?]</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>[https://smlfamily.github.io/Basis/ Standard ML Basis Library], AT&T and Lucent Technologies, 2004-04-12 (Accessed: 2025-08-09)</ref><ref>[https://doc.rust-lang.org/beta/std/index.html std - Rust], doc.rust-lang.org, 2025-08-05 (Accessed: 2025-08-09)</ref><ref>[https://ziglang.org/documentation/master/std/ Zig Documentation], ziglang.org, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html All Classes (Java Platform SE 8 )], docs.oracle.com, 2025-06-30 (Accessed: 2025-08-09)</ref><ref>[https://www.scala-lang.org/api/current/ Scala 3], , 2025-07-29 (Accessed: 2025-08-09)</ref><ref>[https://ocaml.org/manual/5.2/api/index.html The OCaml API], , (Accessed: 2025-08-09)</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>[https://www.musl-libc.org/faq.html musl FAQ], , 2018-02-21 (Accessed: 2025-08-09)</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>[https://wiki.musl-libc.org/compatibility musl libc - Compatibility], , 2025-04-26 (Accessed: 2025-08-09)</ref><ref>[https://www.fefe.de/dietlibc/FAQ.txt <span style="color:#fc493b">https://www.fefe.de/dietlibc/FAQ.txt <sup>🍣DEAD?]</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>[https://wiki.osdev.org/C_Library C Library], OSDev Wiki, 2024-06-24 (Accessed: 2025-08-09)</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>[https://nullprogram.com/blog/2017/03/30/ How to Write Portable C Without Complicating Your Build], Chris Wellons, 2017-03-30 (Accessed: 2025-08-09)</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as GNU Autotools, CMake, Meson, Zig's build toolchain among a plethora others, however for ideological<ref>[https://suckless.org/sucks/ software that sucks less | suckless.org software that sucks less], , 2025-05-29 (Accessed: 2025-08-09)</ref><ref>[https://www.interaction-design.org/literature/topics/keep-it-simple-stupid What is Keep It Simple, Stupid (KISS)?], Interaction Design Foundation - IxDF, 2016-06-05 (Accessed: 2025-08-09)</ref><ref>[http://harmful.cat-v.org/software/GNU/auto-hell GNU Auto*hell], , (Accessed: 2025-08-09)</ref> and practical<ref>[https://twdev.blog/2021/08/cmake/ Why CMake sucks? - twdev.blog], Tomasz Wisniewski, 2021-08-06 (Accessed: 2025-08-09)</ref><ref>[https://silverhammermba.github.io/blog/2023/01/06/gradle Gradle still sucks | Floating little leaves of code], Maxwell Anselm, 2023-01-06 (Accessed: 2025-08-09)</ref><ref>[https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system Stop the autoconf insanity! Why we need a new build system. – Freecode], Andrew McCall, 2003-06-21 (Accessed: 2018-11-18)</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>[https://github.com/Mercury-Language/mercury GitHub - Mercury-Language/mercury: The Mercury logic programming system.], Mercury-Language, 2013-08-09 (Accessed: 2025-08-09)</ref><ref>[https://github.com/NetBSD/src GitHub - NetBSD/src: Automatic conversion of the NetBSD src CVS module, use with care.], NetBSD, 2025-08-09 (Accessed: 2025-08-09)</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, meta-programming and structural components of a C code base; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>[https://docs.kernel.org/process/5.Posting.html 5. Posting patches — The Linux Kernel documentation], The kernel development community, 2025-07-27 (Accessed: 2025-08-09)</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS|open source]] code bases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995–2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial,<ref>[https://web.mit.edu/~simsong/www/ugh.pdf The UNIX-HATERS Handbook], Simson Garfinkel, Daniel Weise, and Steven Strassmann, 1994 (Accessed: 2025-08-09)</ref> many attribute issues regarding C to fragmentation and portability issues,<ref>[http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful #ifdef Considered Harmful, or Portability Experience With C News], Henry Spencer, (Accessed: 2025-08-09)</ref> lack of type safety and primitive resource access checks,<ref>[https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review <span style="color:#fc493b">https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review <sup>🍣403]</ref> poor administration on part of the C Language Working Group,<ref>[https://cor3ntin.github.io/posts/c/ The problem with C], cor3ntin, 2020-08-30 (Accessed: 2025-08-09)</ref> and overall worsening over time.<ref>[https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html C23 - What We Have To Suffer], Harry Fairhead, 2023-04-05 (Accessed: 2025-08-09)</ref><ref>[https://wiki.theory.org/YourLanguageSucks YourLanguageSucks], TheoryOrg, 2022-09-29 (Accessed: 2025-08-09)</ref> == References == <references /> [[Category:Programming Languages]] 2e1d609ea7ef16c62d259f61622c1441fa8fe0a2 0 429 3379 3240 2025-08-09T12:18:45Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=CRUX|image=[[File: Crux.png]]|caption=The Official CRUX logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[pkgutils]]|defaultdesktops=[[KDE Plasma]]|usagetype=Desktop|architectures=x86_64|website=[https://crux.nu/ crux.nu]}}CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] <ref>[https://crux.nu/doc/prt-get%20-%20User%20Manual.html prt-get - User Manual], Johannes Winkelmann, 2003-08-09 (Accessed: 2025-08-09)</ref> with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> Unlike other distributions, the primary goal of CRUX is not to be the most popular or to put as many features as possible into the system. The idea is rather to build a streamlined distribution, targetted at a specific audience which in turn gets a system without compromises. Some of the characteristics of CRUX are: * KISS (Keep It Simple, Stupid) concept, applied to both the system and the development process * Source based package installation using a ports system * Simplicity over automation * Targetted at experienced users with compact, to the point documentation * Native configurations over configuration abstraction layers * Up to date features and packages, however no bleeding edge software in the main repositories * Easy way to extend the system by yourself * Active community of contributors outside the core development team ==History== CRUX was founded by Per Lidén.<ref>[https://crux.nu/Profiles/PerLiden CRUX | Profiles / PerLiden], CRUX, 2011-01-04 (Accessed: 2025-08-09)</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. CRUX has had 27 documented releases <ref>[http://ftp.morpheus.net/pub/linux/crux/ Index of /pub/linux/crux/], , (Accessed: 2025-08-09)</ref>,from 0.9.7 to the current release, 3.8 ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "Pkgfiles," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> == Ports System == CRUX uses a BSD-style ports system, revolving around the packaging system pkgutils, each port contains a Pkgfile which tells pkgmk or prt-get what to do, it is a relatively simple process, that involves fetching the source declared in the Pkgfile (Or if the file is already present and matches the checksum, it extracts it.), Following the compilation steps declared in the Pkgfile while using the optimizations and arguments declared in ```/etc/pkgmk.conf```, this part is declared in the ```build()``` section of the Pkgfile, since a Pkgfile is essentially a BASH script, it can be edited by the end user to match their own needs. <ref>[https://crux.nu/Main/Handbook3-8-Package CRUX | Main / Handbook3-8-Package], CRUX, 2025-05-10 (Accessed: 2025-08-09)</ref> == References == [[Category:Linux Distributions]] 4314a82592e8a4cf1336279a71fa9415a5601f03 0 625 3380 2878 2025-08-09T12:37:35Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was developed by a team led by Peter "ptr1337" Jung to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2023. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Default browser: Cachy Browser (hardened Firefox fork). * Support for Btrfs snapshots with Limine bootloader. * Optional Firejail, DNSCrypt, AppArmor hardening. == Desktop Environments == CachyOS provides several preconfigured desktop environments: * [[Plasma|KDE Plasma]] (default) * [[GNOME]] * [[XFCE|Xfce]] * [[LXQt]] * [[Cutefish]] * [[Wayfire]] * [[i3]], [[bspwm]], [[Openbox]] Users can select their preferred environment during installation. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * [[Btrfs]] with snapshot support is the default filesystem. * Full UEFI, ZFS, and Secure Boot support. * Smooth installation experience designed for newcomers to Arch. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. * Limine bootloader for rollback support via Btrfs. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ ] (Accessed: )</ref></references> 71ea0adc065e45997fcb1fb9980a59ade9b339bf 3381 3380 2025-08-09T12:38:24Z Madonuko 140 I'll just add back the title for the 404 page wikitext text/x-wiki '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was developed by a team led by Peter "ptr1337" Jung to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2023. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Default browser: Cachy Browser (hardened Firefox fork). * Support for Btrfs snapshots with Limine bootloader. * Optional Firejail, DNSCrypt, AppArmor hardening. == Desktop Environments == CachyOS provides several preconfigured desktop environments: * [[Plasma|KDE Plasma]] (default) * [[GNOME]] * [[XFCE|Xfce]] * [[LXQt]] * [[Cutefish]] * [[Wayfire]] * [[i3]], [[bspwm]], [[Openbox]] Users can select their preferred environment during installation. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * [[Btrfs]] with snapshot support is the default filesystem. * Full UEFI, ZFS, and Secure Boot support. * Smooth installation experience designed for newcomers to Arch. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. * Limine bootloader for rollback support via Btrfs. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 46210ab6569105d1ce3220523b273aad46640978 0 254 3382 3343 2025-08-09T12:39:24Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]]'''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm. == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == [[Category:X_Window_Managers]] [[Category:Window Management Systems]] aedd931484947d8387956a893fd2fe64115dac2a 0 736 3383 3034 2025-08-09T12:42:00Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html ed], The IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> ed was part of the original Unix operating system from 1969.<ref>[https://man.cat-v.org/unix-1st/1/ed ed(1)], Unix First Edition Manual Page, 1971-11-03 (Accessed: 2025-08-09)</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>[https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html Shell & Utilities: Detailed Toc], IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s s/regexp/replacement command was inherited from ed.<ref>[https://www.gnu.org/software/ed/manual/ed_manual.html GNU 'ed' Manual], GNU, 1993-08-09 (Accessed: 2025-08-09)</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor vi, whose variants remain some of the most popular TUI text editors.<ref>[https://ex-vi.sourceforge.net/ex.html ex.1], 2005-03-24 (Accessed: 2025-08-09)</ref><ref>[https://ex-vi.sourceforge.net/vi.html vi.1], 2005-03-24 (Accessed: 2025-08-09)</ref> == References == [[category:software]] 5f07f479ec4d49a528e9f0ccaf280f90da5b61b3 0 623 3384 2949 2025-08-09T12:42:46Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=EndeavourOS|image=[[File:EndeavourOS Logo.svg|Thumb]]|caption=The Endeavour OS logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=Cinnamon, Enlightenment, GNOME, [[KDE Plasma]], LXDE, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, aArch64|website=[https://endeavouros.com endeavouros.org]}}'''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">[https://endeavouros.com/ Home - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>[https://endeavouros.com/about-us/ About us - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning Arch Linux fundamentals. === Installation === EndeavourOS provides an ISO with the Calamares installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with Arch Linux, meaning it uses Arch's official repositories directly and adheres closely to Arch's philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * AUR Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate AUR package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * Pacman Compatibility: Fully compatible with Arch's pacman package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for Arch Linux are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla Arch, or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the AUR, as well as EndeavourOS-specific themes and utilities.<ref>[https://repo.c48.uk/endeavouros/repo/endeavouros/ Index of /endeavouros/repo/endeavouros/] (Accessed: 2025-08-09)</ref> This is simply a pacman repository that can simply be added to any Arch Linux system if desired. == References == 5d3b6ac462d107e8c390639ce40e27447afffc14 0 756 3385 3048 2025-08-09T12:44:44Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{DISPLAYTITLE:ex}} [[File:Exedit.png|thumb|nvi text editor in Ex mode]] Ex is a text editor developed for [[UNIX|Unix]] systems in 1977 as a modified version of em, which was an improved version of the original Unix text editor [[ed]].<ref>[https://man.freebsd.org/cgi/man.cgi?query=vi&manpath=FreeBSD+14.3-RELEASE vi], The FreeBSD Project, 2024-04-18 (Accessed: 2025-08-09)</ref><ref>[https://web.archive.org/web/20240621040052/https://www.groklaw.net/article.php?story=20050422235450910 Groklaw - The Daemon, the Gnu and the Penguin, Ch. 4 & 5 - by Peter H. Salus], Peter H. Salus, 2005-04-22 (Accessed: 2024-06-21)</ref> Like ed, ex is a line editor, meaning commands can only be executed on one line at a time. Ex was eventually modified into a screen editor and became [[vi]]. Modern versions of ex are rarely distributed on their own, but are rather line editor modes of vi text editors.<ref>[https://man.netbsd.org/ex.1 ex(1) - NetBSD Manual Pages], 3rd Berkeley Distribution, 2024-04-28 (Accessed: 2025-08-09)</ref> == References == [[category:software]] 007612b5dced34be26091ed18833ca0f60809e54 0 638 3386 2951 2025-08-09T12:46:10Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki Ext4 is an advanced level of the ext3 [[filesystems]] which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular [[Linux Distributions|distributions]], however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. Information on how to do it can be found in [[Guides:Ext4]]. === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. this time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e. HDDs) ==== Changing the data mode ==== Ext4 provides three data modes<ref>[https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode 1. General Information — The Linux Kernel documentation], The kernel development community, 2018-10-22 (Accessed: 2025-08-09)</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> You can change the data mode by setting the <code>data=...</code> mount option. ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost. The mount option <code>barrier=0</code> disables write barriers. Only disable this option if you know what you're doing. ==== Async journal commits and external journaling device ==== Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>[https://libre-consulting.com/posts/fs_ext4_external_journal/ ext4: using external journal to optimise performance], Libre Solutions Pty Ltd, 2019-01-24 (Accessed: 2025-08-09)</ref> ==== Enabling fscrypt support ==== fscrypt<ref>[https://github.com/google/fscrypt GitHub - google/fscrypt: Go tool for managing Linux filesystem encryption], Google, 2017-08-09 (Accessed: 2025-08-09)</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. ==== Enabling fast_commit support ==== fast_commit <ref>[https://lwn.net/Articles/842385/ <nowiki>Fast commits for ext4 [LWN.net]</nowiki>], Marta Rybczyńska, 2021-01-15 (Accessed: 2025-08-09)</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by setting the <code>fast_commit</code> feature flag. == References == <references /> 6cdce5731faef95c735999d8e64316e32bd2e3d8 0 291 3387 2957 2025-08-09T12:46:42Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|300px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 48, 2025-03-19 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[File:GNOME 43.png|thumb|A desktop running GNOME 43]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>[https://www.gnu.org/philosophy/free-sw.en.html What is Free Software?], GNU (Accessed: May 7, 2025)</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>[[wikipedia:Qt_(software)#Early_developments|Early Developments of QT]], Wikipedia (Accessed: May 7, 2025)</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>[[wikipedia:GNOME#History|History of GNOME]], Wikipedia (Accessed: May 7, 2025)</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>[https://foundation.gnome.org/ GNOME Foundation], GNOME Foundation, 2025-08-08 (Accessed: 2025-08-09)</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. == References == [[Category:Desktop Environments]] d3348ce6949aead3f4764a0835bf8cd50cc88d50 0 575 3388 2959 2025-08-09T12:52:47Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html <span style="color:#fc493b">https://www.gnu.org/software/emacs/emacs.html <sup>🍣DEAD?]</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <sup>🍣DEAD?]</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys|} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html <span style="color:#fc493b">https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html <sup>🍣DEAD?]</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == [[Category:Software]] 5988a8de7254155ff5e3039e7bdd4f1c033872d5 0 203 3389 3330 2025-08-09T12:54:22Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }}[https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]<ref>[https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer) Daniel Robbins (computer programmer)], Wikipedia contributors, 2024-01-10 (Accessed: 2025-08-09)</ref>. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile<ref>[https://en.wikipedia.org/wiki/Compilation Compilation], Wikipedia contributors, 2024-07-30 (Accessed: 2025-08-09)</ref> their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish thru source compilation of the packages and the kernel itself. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements, the only downside of that being increase compilation time, however '''Gentoo''' is very minimal and it allows a lot of flexibility in that regard. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "slotting". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. To manage those multiple versions of the same packages ( slotting ), '''Gentoo''' provides a tool called '''eselect'''. It acts as a manager for setting system defaults, such as choosing which version of GCC, Python, or even your preferred text editor should be used globally. == Use cases of eselect == Changing the GCC version<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect gcc list [1] x86_64-pc-linux-gnu-13 * [2] x86_64-pc-linux-gnu-14 [user@hostname ~]$ eselect gcc set 2</syntaxhighlight>Changing the locale<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 * [3] en_US.utf8 [4] POSIX [ ] (free form) [user@hostname ~]$ eselect locale set 3 </syntaxhighlight> == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp)</syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |- |<code>emerge --unmerge package</code> |Remove a package and its dependencies |- |<code>emerge --depclean</code> |Remove unused dependencies |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers pre-compiled package options, which usually end in '''<code>-bin</code>''', by example one might want to install Firefox without the hassle of compiling, they can just download the binary version of it by doing <code>sudo emerge firefox-bin</code>. Obviously, not all binary packages will end in the <code>-bin</code> format, they can be named simply like normal packages, for that reason Portage highlights the binary and source packages differently in colors so the user knows which are binary and which are meant for compiling, additionally portage also informs the user of which packages are binaries or source. For additional packages, users might opt for the [https://wiki.gentoo.org/wiki/Project:GURU GURU] project repository, it aims to be a very large user repository, full of binaries and source packages that are not found inside the normal '''Gentoo''' repositories, meant to extend the experience that you can have in this Operating System. Users can create their own repository online as well, or how we call it, "overlays". The user can create an overlay with the desired package, make an ebuild for it and then publish it online for people to use. To get started with an overlay, one must first understand what are ebuilds and how they work, for this it's preferred to read the '''Gentoo Wiki''' on how to do it, it is possible to even add your custom package inside '''GURU''' later, and even the official '''Gentoo''' repository if it's seen as valuable. == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === One might be interested in community resources for '''Gentoo.''' The official community forums can be found at [https://forums.gentoo.org/ forums.gentoo.org/]. Additionally, IRC<ref>Internet Relay Chat</ref> channels has been setup as well. For those who are interested in the official IRC channels, they can be found on the '''Gentoo Wiki''' in the [https://wiki.gentoo.org/wiki/IRC IRC] article. It is possible to subscribe to the [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] or even send emails to them, the page lists the most important lists with the most traffic. There are other, more specialized lists that might be more appropriate depending on the topic. There is a [https://www.gentoo.org/support/documentation/ wiki documentation] available as well. Users can search up specific pages in the site directly, so that they don't waste time finding the right page. Ultimately, '''Gentoo''' offers a [https://bugs.gentoo.org/ bug tracking system] for those who are interested in being up to date with current bugs, or even attempt to solve them. === Development Model === '''Gentoo''' was developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the userbase through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == '''Gentoo''' allows maximum customization potential, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to fetch binaries in heavier packages. However, '''Gentoo''' has it's own downsides; It will take longer to install packages as they compile from source, meaning it will take some time until finished and ready to use. If the system has a very weak CPU, the Operating System will take a while to fully install. The Operating System has a higher learning curve, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] [[Category:Linux Distributions]] 9341bf0ac6a09afdf5b22da86b7a658dcf951509 0 227 3390 2964 2025-08-09T12:55:21Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox|image=[[File:I3 window manager logo.svg|I3_window_manager_logo]]|caption=i3 logo|title=i3|releasestatus=Maintained|lastrelease=4.23, Oct 29, 2023|languages=[[C]]|developers=Michael Stapelberg|website=[https://i3wm.org/ i3wm.org]}} [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager - YouTube], Google TechTalks, 2012-06-18 (Accessed: 2025-08-09)</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== == References == [[Category:X_Window_Managers]] 7f7ed420d9ec26b0712aeeba6e67d95bb89ef08f 0 198 3391 3203 2025-08-09T12:57:42Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.|} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults.|} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref>|} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS).|} == References == [[Category:Linux Distributions]] c1e09a6d614ac6ea6e02e54edb22c9cb1cf86311 0 628 3392 3045 2025-08-09T13:01:47Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[apt]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>[https://iso.atl.dev/l/linuxmint linuxmint - ATL ISO Archives], All Things Linux (Accessed: 2025-08-09)</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. The latest release, Linux Mint 22.1 "Xia", was launched in January 2025 and is supported until 2029.<ref>[https://www.linuxmint.com/download.php Download Linux Mint 22.1 - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> == References == 1a26a9436b31fdd0797a70e50688bb2694bf3bf8 0 733 3394 3349 2025-08-09T13:09:19Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki '''Apple M1''' is a series of [[ARM|ARM-based]] system-on-a-chip (SoC) designed by [[Apple|Apple Inc]]., launched 2020 to 2022. It is part of the Apple silicon series, as a [[central processing unit]] (CPU) and [[graphics processing unit]] (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwidth. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>[https://www.apple.com/newsroom/2022/03/apple-unveils-m1-ultra-the-worlds-most-powerful-chip-for-a-personal-computer/ Apple unveils M1 Ultra, the world’s most powerful chip for a personal computer], Apple, 2022-03-08 (Accessed: 2025-08-09)</ref> The M1 runs Apple's [[macOS]] and [[iPadOS]], Initial support for the M1 SoC in the [[Linux|Linux kernel]] was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == M1 Chip Variants == === A14 === [[File:Apple A14.jpg|thumb|Apple A14 Bionic, the chip M1 is based on.]] The Apple A14 Bionic features an Apple-designed 64-bit, six-core CPU, implementing ARMv8 with two high-performance cores called “Firestorm” and four energy-efficient cores called “Icestorm”.<ref>[https://www.youtube.com/live/KR0g-1hnQPA?si=0l-0ixbkIdH8_pLf Apple Event — October 13 - YouTube], Apple, 2020-10-13 (Accessed: 2025-08-09)</ref> The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big. LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[https://www.youtube.com/watch?v=BCvL8O0-Qwo Apple Unveils M1 Ultra Chip (Full Reveal) - YouTube], CNET Highlights, 2022-03-08 (Accessed: 2025-08-09)</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>[https://www.anandtech.com/show/17024/apple-m1-max-performance-review Apple M1 Pro and M1 Max: Specs, Performance, Everything We Know], Tom's Hardware, 2021-10-25 (Accessed: 2025-08-09)</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>[https://www.anandtech.com/show/17024/apple-m1-max-performance-review Apple M1 Pro and M1 Max: Specs, Performance, Everything We Know], Tom's Hardware, 2021-10-25 (Accessed: 2025-08-09)</ref> {| class="wikitable" |+SoCs of the "Firestorm" and "Icestorm" microarchitectures. !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>[https://www.apple.com/mac/m1/ Mac], Apple, 2025-08-09 (Accessed: 2025-08-09)</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>[https://support.apple.com/kb/SP858?locale=en_US MacBook Pro (16-inch, 2021) - Technical Specifications], Apple Support, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://support.apple.com/kb/SP865?locale=en_US Mac Studio (2022) - Technical Specifications], Apple Support, 2025-08-09 (Accessed: 2025-08-09)</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>[https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/ Apple M1 Ultra Chip Is Nearly 3 Times Bigger Than AMD's Ryzen CPUs, Benchmarks Show Desktop Intel & AMD CPUs Still Ahead], Hassan Mujtaba, 2022-03-19 (Accessed: 2025-08-09)</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>[https://borderpolar.com/tech/apple-m1-benchmarks/ <span style="color:#fc493b">https://borderpolar.com/tech/apple-m1-benchmarks/ <sup>🍣522]</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>[https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/ M1 Mac mini power consumption and thermals vs Intel models - 9to5Mac], Ben Lovejoy, 2021-01-28 (Accessed: 2025-08-09)</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>[https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F Mac - Compare Models], Apple, 2025-08-09 (Accessed: 2025-08-09)</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>[https://www.nytimes.com/wirecutter/reviews/best-macbooks/ The 3 Best MacBooks of 2025 | Reviews by Wirecutter], Dave Gershgorn, 2025-07-22 (Accessed: 2025-08-09)</ref><ref>[https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw Yeah, Apple’s M1 MacBook Pro is powerful, but it’s the battery life that will blow you away | TechCrunch], Matthew Panzarino, 2020-11-17 (Accessed: 2025-08-09)</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: * [[File:Macbook Pro 13" M1 2020.jpg|thumb|M1 Macbook Pro]] * Macbook Air 2020 (M1) - base model has binned, 7-Core GPU * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) * iPhone 12 and 12 mini (A14) * iPhone 12 Pro and 12 Pro Max (A14) * iPad air 4(th generation) (A14) * iPad (10th generation) (A14) and all the devices respective variants. == References == {{DEFAULTSORT:Apple M1}} 4843599ba64caed2cf3afc816927c5c1f2964b33 0 626 3395 2978 2025-08-09T13:12:02Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>[https://manjaro.org/ Manjaro – The Linux for People and Organizations], Manjaro, 2025-08-09 (Accessed: 2025-08-09)</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">[https://distrowatch.com/table.php?distribution=manjaro DistroWatch.com: Manjaro Linux], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>[https://wiki.manjaro.org/index.php/Pamac Pamac - Manjaro], Manjaro, 2023-03-09 (Accessed: 2025-08-09)</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>[https://en.wikipedia.org/wiki/Manjaro Manjaro], Wikipedia contributors, 2025-07-01 (Accessed: 2025-08-09)</ref><ref>[https://www.ubuntumint.com/manjaro-linux-history/ The History of Manjaro Linux Distribution], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>[https://www.geeksforgeeks.org/how-to-install-manjaro-linux/ How to Install Manjaro Linux?], GeeksforGeeks, 2023-12-22 (Accessed: 2025-08-09)</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch's base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch's, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>[https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/ How to Enable Arch User Repository (AUR) in Manjaro Linux], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro's custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch's upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>[https://itsfoss.com/manjaro-vs-arch-linux/ Manjaro vs Arch: What's the Difference? Which one to Use?], Dimitrios, Abhishek Prakash, 2023-09-13 (Accessed: 2025-08-09)</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>[https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. == References == 053efd1dfc0b58e1ced4895cb4ea56944eafb5ca 0 428 3396 3302 2025-08-09T13:14:46Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' (short for ''manual'') is a [[TUI|command-line]] utility available on [[UNIX]] and UNIX-like [[Operating System|operating systems]] that provides documentation for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a man page the user can enter the following into their terminal:<ref>[https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage man page], Wikipedia contributors, 2025-07-14 (Accessed: 2025-08-09)</ref> man ''<command_name>'' For example, to read the manual for <code>man</code> command itself: man man == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>[https://en.wikipedia.org/wiki/Man_page#Manual_sections man page], Wikipedia contributors, 2025-07-14 (Accessed: 2025-08-09)</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>[https://en.wikipedia.org/wiki/Man_page#Manual_sections man page], Wikipedia contributors, 2025-07-14 (Accessed: 2025-08-09)</ref>|} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>[https://en.wikipedia.org/wiki/Man_page#Layout man page], Wikipedia contributors, 2025-07-14 (Accessed: 2025-08-09)</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER</code> environment variable. By default, it uses <code>less</code>. Alternatively, the <code>-P</code> or <code>--pager</code> option can be used.<ref>[https://www.mankier.com/1/man.mandoc#Environment man.mandoc: display manual pages | mandoc Commands | Man Pages], ManKier, 2020-07-20 (Accessed: 2025-08-09)</ref><ref>[https://www.man7.org/linux/man-pages/man1/man.1.html man(1) - Linux manual page], Michael Kerrisk, 2025-02-02 (Accessed: 2025-08-09)</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally.<ref>[https://fishshell.com/docs/current/faq.html Frequently asked questions — fish-shell 4.0.2 documentation], fish-shell developers, 2024-08-09 (Accessed: 2025-08-09)</ref> == References == <references /> 48313817e8cfd21e576499310e08dbca7920a885 0 534 3397 2982 2025-08-09T13:15:03Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox|image=[[File:Niri Rice.png|300px|example_niri_rice]]|caption=Example Niri Rice|title=niri|releasestatus=Maintained|firstrelease=v0.1.0-alpha.1|lastrelease=Version 25.01|languages=[[Rust]]|developers=Ivan Molodetskikh A.K.A. YaLTeR|website=[https://github.com/YaLTeR/niri Github Repository]}} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">[https://github.com/YaLTeR/niri/wiki/Important-Software Important Software · YaLTeR/niri Wiki · GitHub], YaLTeR, 2025-08-09 (Accessed: 2025-08-09)</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading == References == <references /> fb377e8edef180e9f74b7179a3a128255f0202e0 0 775 3398 3186 2025-08-09T13:18:05Z Madonuko 140 /* References */ [[ATL:Guidelines#Citations]] wikitext text/x-wiki [[File:2025-08-02 16-38-21.png|thumb|440x440px|Example of <code>NIX_AUTO_RUN=1</code> powered by nix-shell. Missing commands will be downloaded unless there are multiple sources.]] Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software from a shell before discarding it upon exiting. Included with [[NixOS]] and [https://nixos.org Nix]. ===== Example usage: ===== <pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre>By default, <code>nix-shell</code> uses <code>bash</code> as the shell. You can change this using the <code>--command</code> flag, for example: <code>--command zsh</code>. The <code>-p</code> flag is shorthand for <code>--packages</code>. ===== Full usage: ===== <pre> [user:~]$ nix-shell --packages cowsay \ --command bash \ --run 'cowsay Success' \ --pure _________ < Success > --------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || </pre><code>--pure</code> removes all other packages from the shell environment, say; if you want to use <code>appimage-run</code> but the version of qt on your host is out-of-date. This way you don't have to remove/update qt outside the command. <code>--run</code> allows you to write out the full intended command, without first entering the shell. More parameters can be found in <code>man nix-shell</code>. ==== Auto run: [as shown in the image] ==== Auto run allows you to automatically download any packages you're missing, although it only checks the first word of your command. Allowing you to use any command like <code>inxi</code> by just typing out the command and running it, this extends to parameters as well, ex: <code>inxi -Fxxx</code>. This can be enabled via: <code>export NIX_AUTO_RUN="1"</code> Or by adding <code>environment.sessionVariables.NIX_AUTO_RUN = "1";</code> to your configuration. ==== Shell.nix ==== A <code>shell.nix</code> file sets up a reproducible development environment. When you run <code>nix-shell</code> it opens a shell with all your project's dependencies, keeping them isolated from your system. It can also be version locked by specifying channels or commit hashes. Below is an example <code>shell.nix</code> for a Node.js project.<ref>[https://nix.dev/tutorials/first-steps/declarative-shell.html Declarative shell environments with shell.nix — nix.dev documentation], NixOS Foundati on, 2016-08-09 (Accessed: 2025-08-09)</ref><pre>with (import <nixpkgs> {}); mkShell { buildInputs = [ nodejs-12_x yarn ]; shellHook = '' mkdir -p .nix-node export NODE_PATH=$PWD/.nix-node export NPM_CONFIG_PREFIX=$PWD/.nix-node export PATH=$NODE_PATH/bin:$PATH ''; }</pre> == References == <references /> [[Category:Software]] a77f0f8c1c8b101383954a7d3189fdda455a4ad0 0 562 3399 2985 2025-08-09T13:19:31Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>[https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips Getting Started - OpenIndiana Docs], The OpenIndiana Project, 2025-08-06 (Accessed: 2025-08-09)</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix-like [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel.<ref>[https://docs.openindiana.org/misc/openindiana/#what-is-the-openindiana-operating-system What is OpenIndiana Project?], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>[https://web.archive.org/web/20100913030810/https://www.openindiana.org/ Project OpenIndiana], The OpenIndiana Project, 2010-08-09 (Accessed: 2010-09-13)</ref> It was proved timely as Oracle shut down development of OpenSolaris.<ref>[https://web.archive.org/web/20201109033546/http://sstallion.blogspot.com/2010/08/opensolaris-is-dead.html OpenSolaris is Dead.], Iconoclastic Tendencies, August 13, 2010 (Accessed: July 13, 2025)</ref> OpenIndiana uses the same tooling as Solaris; the SMF init system,<ref>[https://docs.openindiana.org/handbook/systems-administration/#service-management-facility Service Management Facility], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> FMA fault management system,<ref>[https://docs.openindiana.org/misc/openindiana/#what-features-does-openindiana-have What features does OpenIndiana have?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and IPS package manager,<ref>[https://docs.openindiana.org/handbook/systems-administration/#software-management Software management], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> The majority of the [https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/ Solaris documentation] also applies to OpenIndiana.{{Citation needed}} OpenIndiana makes use of the SunOS branch of the UNIX kernel,<ref>[https://docs.openindiana.org/misc/openindiana/#why-is-it-called-openindiana Why is it called OpenIndiana?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and thus provides all of the stability benefits of a UNIX System V derivative.{{Citation needed}} This does, however, mean that hardware support is limited in comparison to a BSD or Linux based OS.<ref>[https://docs.openindiana.org/community-hcl/getting-hardware-info/ Getting information about hardware] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> OpenIndiana uses the SunOS libc, which severely limits what software will compile on it successfully. SunOS libc only implements functions expected by POSIX and ANSI C.{{Citation needed}} == References == [[Category:Misc Operating Systems]] [[Category:Illumos]] 023e900d9242d38a05ed9b3c5c9ffe8c7ad1e8d5 0 641 3400 2987 2025-08-09T13:20:40Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Maintenance |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/, openbox.org] }} [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable [[X Window Manager|window manager]] for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>[https://openbox.org/ Home - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>[https://openbox.org/obconf ObConf - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> === Usage === While Openbox is perfectly usable on its own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], lxqt, 2025-08-09 (Accessed: 2025-08-09)</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>[https://slitaz.org/en/about/ SliTaz - About the project], SliTaz (Accessed: 2025-08-09)</ref><ref>[https://crunchbang.org/about/ About - CrunchBang], CrunchBang Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> == References == <references /> [[Category:Desktop Environments]] 815e19228eaa57154c12c89fcd7acc0ae56bdca2 0 651 3401 2994 2025-08-09T13:20:51Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki An operating system (OS) is a collection of [[software]] that manages a computer's [[hardware]] and [[applications]] by allocating resources, including memory, CPU, input/output devices and file storage.<ref>[https://www.ibm.com/think/topics/operating-systems What is an Operating System?], IBM, 2025-08-09 (Accessed: 2025-08-09)</ref> A user interacts with an operating system through a [[user interface]] (UI), which issues commands in a language the OS can understand. The UI can be either a [[graphical user interface]] (GUI) or a [[command-line interface]] (CLI). All computer systems need an OS to function. == References == 036a15ad39a22cf511c84c79ccea5fcca5fa48a7 3403 3401 2025-08-09T13:22:30Z Madonuko 140 /* References */ fix HMCT shenanigans wikitext text/x-wiki An operating system (OS) is a collection of [[software]] that manages a computer's [[hardware]] and [[applications]] by allocating resources, including memory, CPU, input/output devices and file storage.<ref>[https://www.ibm.com/think/topics/operating-systems What is an Operating System? | IBM], Stephanie Susnjara & Ian Smalley, 2025-03-05 (Accessed: 2025-08-09)</ref> A user interacts with an operating system through a [[user interface]] (UI), which issues commands in a language the OS can understand. The UI can be either a [[graphical user interface]] (GUI) or a [[command-line interface]] (CLI). All computer systems need an OS to function. == References == 59c48461eacf25964caa42c37d7f9e04e12326b1 0 821 3402 2025-08-09T13:21:36Z Madonuko 140 #REDIRECT [[Operating System]] wikitext text/x-wiki #REDIRECT [[Operating System]] 4d4dd358fc4cb31741d493c347ea9f96c2c6af75 0 480 3404 3332 2025-08-09T13:24:32Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}}[[File:Oreon10-2502.png|thumb|Oreon 10 Core (Build 2502) running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>[https://oreonproject.org/ Oreon Project - Where open source becomes something special], Oreon Project (Accessed: 2025-08-09)</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>[https://git.oreonproject.org/rpms <span style="color:#fc493b">https://git.oreonproject.org/rpms <sup>🍣502]</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>[https://boostyconnect.com/oreon-lime-r1-lifecycle/ Oreon Lime R1/R1.1 Lifecycle], BoostyConnect, 2025-08-09 (Accessed: 2025-08-09)</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>[https://oreonproject.org/oreon-lime-r2-support-timeline/ Oreon Lime (R2) Support Timeline], Oreon Project (Accessed: 2025-08-09)</ref><ref>[https://oreonproject.org/oreon-lime-r2/ Oreon Lime (R2)], Oreon Project (Accessed: 2025-08-09)</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>[https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/ Oreon Lime is AlmaLinux with a desktop twist • The Register], Liam Proven, 2024-08-20 (Accessed: 2025-08-09)</ref> and other well-known sources. In October 2024, Oreon celebrated its 1st anniversary on November 16, 2024, and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>[https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69 <span style="color:#fc493b">https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69 <sup>🍣404]</ref> Oreon 10 released to the public on December 12, 2024, shipping with KDE Plasma 6 and Linux 6.11<ref>[https://forums.oreonproject.org/t/oreon-10-officially-released/98 <span style="color:#fc493b">https://forums.oreonproject.org/t/oreon-10-officially-released/98 <sup>🍣404]</ref> but was upgraded to 6.12 a few days later. A new update to Oreon 10 has been released on February 12, 2025, under the name "Build 2502." This update brought a few bug fixes along with some planned features for later such as Apple M-series Mac support.<ref>[https://forums.oreonproject.org/t/oreon-10-build-2502-has-officially-released/150 <span style="color:#fc493b">https://forums.oreonproject.org/t/oreon-10-build-2502-has-officially-released/150 <sup>🍣404]</ref> == References == <references /> [[Category:Linux Distributions]] fdebb256283e29420241c55774170e5f62da6f89 0 175 3405 2992 2025-08-09T13:24:51Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[File:Pacman 401.png|thumb|[[Pacman]]]] == Intro == The [[Linux Distributions|Linux distribution]] [[Arch Linux]] and its derivatives usually use a [[Package Manager|package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>[https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] == References == [[Category:Package Managers]] 625dac01ab0706d1c3af5361f18564663abf80bc 0 802 3406 3241 2025-08-09T13:25:07Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki '''pkgutils''' is a set of utilities (pkgadd, pkgrm, pkginfo, pkgmk and rejmerge), which are used for managing software packages in Linux. It is developed for and used by the CRUX distribution <ref>[http://crux.nu CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> All the packages installed with '''pkgutils''' are plain <code>.tar.gz</code> files. == Usage == The following are several common usages of '''pkgutils'''. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pkgadd package1.pkg.tar.gz package2.pkg.tar.gz</code> {| class="wikitable" |+Common Pkgutils Commands !Command !Description |- |<code>pkgadd package.pkg.tar.gz</code> |Install a given package |- |<code>pkgrm package</code> |Remove a given package. |- |<code>ports -u</code> |Sync ports tree |- |<code>prt-get update</code> |Sync local index with the ports tree |- |<code>prt-get upgrade</code> |Rebuild and reinstalls newer versions of installed packages |- |<code>prt-get search package</code> |Search a given package |- |<code>pkginfo -i</code> |List all installed packages |- |<code>pkginfo package</code> |Display info about a given package |} == See Also == [https://crux.nu/Main/Handbook3-7-Package pkgutils - CRUX] [[Category:Package Manager]] 8cc0df8f0e81977b2434d26835b71fb3673865cd 0 235 3407 2990 2025-08-09T13:25:28Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>[https://github.com/gentoo/portage/blob/master/NEWS portage/NEWS at master · gentoo/portage · GitHub], Gentoo Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every [[Gentoo]] and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the [[Package Manager|package manager]], although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. === Configuration === Configuration of Portage is done through various configuration files and folders found in /etc/portage, which allows configuration of features such as USE flags, default options, masked packages and more. ==== make.conf ==== make.conf is the main configuration file for Portage. It allows the configuration of system-wide USE flags, Portage features, accepted licenses and more. This file is regularly edited during the Gentoo installation process and during ordinary use of it, so it's very important to get the options right for it. Below are some of the most relevant ones. ===== COMMON_FLAGS, CFLAGS, CXXFLAGS, FCFFLAGS and FFLAGS ===== These variables determine the build and compile flags that will be used for all package compilations. The CFLAGS variable is for C applications, while the CXXFLAGS one is meant for C++ ones. Most users will keep these variables identical. A "safe" configuration to avoid compilation errors should look like this:<blockquote><code>COMMON_FLAGS="-march=native -O2 -pipe"</code> <code>CFLAGS="${COMMON_FLAGS}"</code> <code>CXXFLAGS="${COMMON_FLAGS}"</code> <code>FCFLAGS="${COMMON_FLAGS}"</code> <code>FFLAGS="${COMMON_FLAGS}"</code></blockquote> ===== MAKEOPTS ===== The MAKEOPTS variable is used to specify arguments that will be passed to [[Make]] during compilation. A good rule of thumb is to set the -j argument to about half your RAM size and the -l argument to the thread count of your CPU, which can be found by running <code>nproc</code>. For example, if you have 4 GB of RAM and a 6th generation Intel Core i3, your MAKEOPTS variable should look something like this:<blockquote><code>MAKEOPTS="-j2 -l4"</code></blockquote> ===== GENTOO_MIRRORS ===== The GENTOO_MIRRORS variable tells Portage what mirror(s) to download the packages from. It can be set manually by editing the variable with a link to the mirror(s) of your liking available [https://www.gentoo.org/downloads/mirrors/ here], or automatically via <code>mirrorselect</code>, which can select the fastest mirror(s) for you. It's highly recommended to set this variable to a mirror close to you, for example, if you want to use an Italian mirror you would have to edit the variable like this:<blockquote><code>GENTOO_MIRRORS="<nowiki>https://gentoo.mirror.garr.it/</nowiki>"</code></blockquote> ===== FEATURES ===== The FEATURES variable contains a list of features that you can enable which notably alters the behavior of Portage. For example, if you want to use binary packages and verify their signatures, you would have to set the variable like this:<blockquote><code>FEATURES="getbinpkg binpkg-request-signature"</code></blockquote> ===== EMERGE_DEFAULT_OPTS ===== The EMERGE_DEFAULT_OPTS variable contains the options that will be automatically set when running Portage every time. For example, if you want Portage to ask for confirmation and verbose output, you would set the variable to this:<blockquote><code>EMERGE_DEFAULT_OPTS="--ask --verbose"</code></blockquote> ===== USE ===== The USE variable allows the '''system-wide''' enabling or disabling of USE flags. An example of this variable may look like this:<blockquote><code>USE="pulseaudio X systemd dbus policykit udisks dist-kernel -alsa -wayland xwayland"</code></blockquote> ===== USE_EXPAND ===== USE_EXPAND is a set of variables that serve to extend the capabilities of USE flags. Below are the most relevant ones. ====== VIDEO_CARDS ====== VIDEO_CARDS is a variable that serves to specify the drivers you wish to install for your GPUs. For example, if you want to install the drivers for AMD and Intel graphics, you would set the variable to this:<blockquote><code>VIDEO_CARDS="amdgpu radeonsi intel"</code></blockquote> ====== CPU_FLAGS_* ====== The CPU_FLAGS_* variables specify the available features that your CPU has to optimize compiling packages. The currently available variables are CPU_FLAGS_X86 (for x86 and x86_64 architectures), CPU_FLAGS_ARM (for ARM and ARM64 architectures) and CPU_FLAGS_PPC (for PowerPC and PowerPC64 architectures). The <code>cpuid2cpuflags</code> utility can be used to find these flags. The output of this command may look something like this:<blockquote><code>CPU_FLAGS_X86: aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3</code></blockquote>The output can then be copied to make.conf. ===== ACCEPT_LICENSE ===== The ACCEPT_LICENSE variable can be used to tell Portage which type of licenses are allowed. Generally, it's preferred to not accept proprietary software licenses. To allow every license except proprietary ones, you can set the variable to this:<blockquote><code>ACCEPT_LICENSE="* -@EULA"</code></blockquote> == References == [[Category:Package Managers]] a61bdf8b084dfbf3e1bb5dfb4132c541fb8e10a0 0 354 3408 2988 2025-08-09T13:26:03Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{MascotInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy|222px]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. Puffy resembles a puffer-fish and has been the mascot since June 15th, 2000.<ref>[https://www.openbsd.org/27.html OpenBSD 2.7], Theo de Raadt, 2000-06-15 (Accessed: 2025-08-09)</ref> [[File:Puffyanim.gif|thumb|99x99px|Animated Puffy Render]] == References == [[Category:Mascots]] 090bb1ddee1d64505f07eb93ee848803344956a0 0 225 3409 3355 2025-08-09T13:27:32Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64 | website = [https://redhat.com/rhel/ redhat.com] }} [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business customers.<ref>[https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux Red Hat Enterprise Linux], Red Hat, 2025-08-09 (Accessed: 2025-08-09)</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. == References == <references /> [[Category:Linux Distributions]] fa2a1d674cfde5d5afc740faecc839460f5c2c32 0 816 3410 3301 2025-08-09T13:32:50Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Work In Progress}} Runit is a cross platform init & service management scheme used on Unix like systems such as Linux, *BSD, Mac OS X & Solaris.<ref>https://smarden.org/runit/ Runit's official website.</ref> It was made by Gerrit Pape to replace sysvinit and other init schemes in Unix systems. Runit can be used either as an init scheme or a service supervisor running under another, preexisting init scheme. === Design === In the role of an init scheme, runit performs booting, running, halting or resetting the system in three stages: * Stage 1: Runit starts /etc/runit/1 and waits for it to terminate. The system's one time initialization tasks are completed here. /etc/runit/1 is slimmed down as much as possible, and has full access to /dev/console in case something goes wrong. * Stage 2: Runit starts /etc/runit/2 which in turn runs runsvdir. Its task is to monitor services represented as directories defined by the distro.<ref>[https://smarden.org/runit/runsvdir.8 runsvdir(8) manual page], Gerrit Pape (Accessed: 2025-08-09)</ref> This part of Runit is the only one which can be used across different Unix like systems with little modification.<ref>[https://smarden.org/runit/benefits runit - benefits], Gerrit Pape (Accessed: 2025-08-09)</ref> Stage 2 is supposed to stay running till the system halts or reboots. * Stage 3: If runit is told to halt or reboot, it stops /etc/runit/2 and runs /etc/runit/3 to shutdown or reboot the system. === Distributions with runit === * antiX Linux (runit offered as official alternative) * Arch Linux (runit offered as unofficial alternative)<ref>[https://wiki.archlinux.org/title/Runit Runit], ArchWiki (Accessed: 2025-08-09)</ref> * Artix Linux (runit offered as official alternative)<ref>[https://wiki.artixlinux.org/Main/Runit Wiki | Main / runit], Artix Wiki (Accessed: 2025-08-09)</ref> * Debian (runit offered as unofficial alternative)<ref>[https://tracker.debian.org/pkg/runit runit - Debian Package Tracker], Debian Package Tracker, 2023-08-09 (Accessed: 2025-08-09)</ref> * Devuan (runit offered as official alternative)<ref>[https://www.devuan.org/os/init-freedom Init Freedom], Devuan GNU+Linux Free Operating System, 2025-01-01 (Accessed: 2025-08-09)</ref> * FreeBSD (runit offered as alternative)<ref>[https://www.freshports.org/sysutils/runit/ FreshPorts -- sysutils/runit: Service supervision tools compatible with DJB daemontools], Dan Langille, 2025-07-31 (Accessed: 2025-08-09)</ref> * Gentoo (runit offered as alternative)<ref>[https://wiki.gentoo.org/wiki/Runit runit], Gentoo Wiki (Accessed: 2025-08-09)</ref> * Linux from Scratch (runit offered as unofficial alternative)<ref>[https://code.google.com/archive/p/runit-for-lfs/ runit-for-lfs.], Google Code Archive, 2014-07-25 (Accessed: 2025-08-09)</ref> * OpenBSD (runit offered as alternative)<ref>[https://openports.eu/ports/sysutils/runit runit | OpenBSD ports], OpenPorts (Accessed: 2025-08-09)</ref> * Ubuntu (runit offered as unofficial alternative)<ref>[https://packages.ubuntu.com/search?keywords=runit Ubuntu – Package Search Results -- runit], Ubuntu, 2025-08-09 (Accessed: 2025-08-09)</ref> * Void Linux (runit is the default)<ref>[https://docs.voidlinux.org/config/services/index.html Services and Daemons - runit], Void Linux Handbook (Accessed: 2025-08-09)</ref> == References == <references /> ab8680b5271c0cb8a27fc57e0ebc459d986318f4 0 304 3411 3000 2025-08-09T13:33:38Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox|architectures=x86-64|caption=The SerenityOS logo|releasestatus=Maintained|title=SerenityOS|usagetype=Desktop, Development|website=[https://serenityos.org serenityos.org]|image=[[File:SerenityOS logo.png|200px|SerenityOS_logo]]|releasemodel=In development|packagemanager=Ports|defaultdesktops=SerenityOS desktop}}SerenityOS is a [[UNIX|UNIX-like]] [[Operating System|operating system]] completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS], SerenityOS (Accessed: 2025-08-09)</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive [[kernel]], and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[MacOS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[Virtual Machine|virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to [[Compiling|compile]] software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub], SerenityOS, 2025-08-09 (Accessed: 2025-08-09)</ref> == References == [[Category:Misc Operating Systems]] 4bc07a9d0295715a9c333e8b0dfc423f1a51b7ba 0 233 3412 3333 2025-08-09T14:01:59Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware logo.svg|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }}[[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>[http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf A history of Slackware development], Eric Hameleers, 2009-10-09 (Accessed: 2025-08-09)</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with KDE * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. == References == [[Category:Linux Distributions]] c3f2a36987bd2451d36443444bf5a85c08628f5a 0 214 3413 3004 2025-08-09T14:09:10Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Tux | image = [[File:Tux.svg|frameless|size=200px]] | caption = Tux! }} '''Tux''' is the official mascot of [[Linux]], designed by Larry Ewing.<ref>[https://web.archive.org/web/20040401161253/http://www.linux.org/info/logos.html Linux Online - Linux Logos and Mascots], Linux Online Inc, 2004-08-09 (Accessed: 2004-04-01)</ref> Tux was created for the Linux 2.0 logo competition.<ref>[https://web.archive.org/web/20040407092622/http://www.cs.earlham.edu/~jeremiah/linux-pix/linux-logo.html Linux Logo Competition], Jeremiah E. Jahn, 2004-08-09 (Accessed: 2004-04-07)</ref> == References == <references /> [[Category:Mascots]] 8391da02ef989bfcb670c8818aad95bdff9ddb41 0 317 3414 3335 2025-08-09T14:11:06Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Needs_Citations}}{{Cleanup|Page relies too heavily on bullet pointed lists}}{{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }}'''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm Void Linux: Distribution mit XBPS-Paketverwaltung], Pro-Linux, 2015-06-12 (Accessed: 2025-08-09)</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and Musl variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses the homegrown [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for runit. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == [[Category:Linux Distributions]] e51b33edc88963fdeaf7315c874203424a8b77ef 0 769 3415 3378 2025-08-09T14:14:19Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''[[Niri]]''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |Cosmic-comp<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |Cosmic |Rust |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps|} ==References== <references /> 33a39d4503288ce93b7c27781b47302018447420 3423 3415 2025-08-09T19:00:57Z Acceus 231 Corrected minor editing mistake wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''[[Niri]]''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |Cosmic-comp<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |Cosmic |Rust |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |} ==References== <references /> b993b17048ca77747eb8413396221bf54ffcc469 0 643 3416 3008 2025-08-09T14:15:04Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{SoftwareInfobox |title = XBPS |releasestatus = Maintained |lastrelease = 0.59.2, 2023-08-18 |firstrelease = 0.1beta1, 2009-08-17 |languages = [[C]] |developers = [[Void Linux]] |website = [https://github.com/void-linux/xbps github.com/void-linux/xbps] }} == Intro == The ''X Binary Package System'' (XBPS) is developed by the maintainers of [[Void Linux]] and is the package manager for their distribution. It was built from scratch, with the goals of speed, ease of use while being feature rich and portable. It is fully compatible with POSIX, SUSv2 and C99 standards<ref>[https://github.com/void-linux/xbps#xbps GitHub - void-linux/xbps: The X Binary Package System (XBPS)], Void Linux, 2025-08-09 (Accessed: 2025-08-09)</ref>, and is released under the BSD 2-Clause (Simplified) license ([https://spdx.org/licenses/BSD-2-Clause.html SPDX: BSD-2-Clause]). == Tools == XBPS is comprised of a number of utilities that provide different functionality, the ''core'' utility programs are as follows (not a complete list): {| class="wikitable" !<u>Name</u> !<u>Function</u> |- |xbps-create |Creating binary packages |- |xbps-dgraph |Generating graphs for tools like [https://graphviz.org GraphViz] |- |xbps-install |Installing and updating packages |- |xbps-pkgdb |Reporting and fixing issues with the package database |- |xbps-query |Querying package and repository information |- |xbps-reconfigure |Configuration of installed package (e.g., the system C library or Linux kernel) |- |xbps-remove |Removing packages |- |xbps-rindex |Handling local package repositories |} == Usage<ref>[https://github.com/void-linux/xbps?tab=readme-ov-file#examples GitHub - void-linux/xbps: The X Binary Package System (XBPS)], Void Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> == {| class="wikitable" !<u>Command</u> !<u>Description</u> |- |<code>xbps-install -Su</code> |Synchronize with repositories and apply all available updates |- |<code>xbps-query -Rs <name></code> |Search through repository packages using the given name |- |<code>xbps-install <package></code> |Install a package by name |- |<code>xbps-remove -R <package></code> |Remove a package by name; along with its dependent packages which are no longer needed by the system |- |<code>xbps-query -Rf <package></code> |List files owned by a package |- |<code>xbps-query -Ro /usr/bin/ls</code> |Find the package(s) that own/provide a file path, (e.g., the 'ls' command) |- |<code>xbps-reconfigure -f glibc-locales</code> |Regenerate your locale(s) when using a GLIBC based system<ref>[https://man.voidlinux.org/xbps-reconfigure xbps-reconfigure(1) - Void Linux manpages], Void Linux, 2023-02-09 (Accessed: 2025-08-09)</ref>|} == References == cbeb778478609e16861d3f2e1fc7ab8772ea61b8 0 236 3417 3009 2025-08-09T14:17:57Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Needs_Citations}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.20, 2024-12-15 | languages = [[C]] | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]]Xfce is a lightweight [[Desktop Environments|desktop environment]] aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * [[Desktop Manager]] - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[TUI|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>[https://xfce.org/about About – Xfce], Xfce Development Team, 2021-11-10 (Accessed: 2025-08-09)</ref> == References == [[Category:Desktop Environments]] fa5acab4138816714cd25c8485e996992ab66a0e 0 763 3418 3287 2025-08-09T14:42:47Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |[[awesome]]<ref>[https://github.com/awesomeWM/awesome GitHub - awesomeWM/awesome: awesome window manager], awesomeWM, 2025-08-09 (Accessed: 2025-08-09)</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |[[Compiz]] |Compiz is a compositing window manager for the X Window System. |- |[[Openbox]] |A minimal and highly configurable stacking window manager written in C. |- |[[twm]]<ref>[https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml TWM], 2010-11-13 (Accessed: 2025-08-09)</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |[[IceWM]]<ref>[https://github.com/bbidulock/icewm GitHub - bbidulock/icewm: A window manager designed for speed, usability, and consistency], bbidulock, 2025-08-09 (Accessed: 2025-08-09)</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |[[i3]]<ref>[https://i3wm.org i3: improved tiling X11 window manager], Michael Stapelberg, 2025-06-12 (Accessed: 2025-08-09)</ref> |A tiling window manager for advanced users and developers. |- |[[Window Maker]]<ref>[https://github.com/window-maker/wmaker GitHub - window-maker/wmaker: Mirror of the official repository repo.or.cz/wmaker-crm.git. Do not send pull requests here, send your patches to wmaker-dev@googlegroups.com instead], window-maker, 2020-08-09 (Accessed: 2025-08-09)</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |[[XMonad]]<ref>[https://xmonad.org/ home | xmonad - the tiling window manager that rocks], xmonad, 2025-06-15 (Accessed: 2025-08-09)</ref> |Window Manager configurable via the Haskell functional programming language.|} ==References== <references /> e7f810786d29a3ec11ffd2cf45c3cb2bec42ba18 0 247 3419 2002 2025-08-09T16:29:23Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref>[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. == References == <references /> 60f345dce29ed0ae52280baed304175c398cdedf 0 424 3420 3338 2025-08-09T16:39:39Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Programming Languages]] AWK is a programming language focused primarily on textual data processing<ref>[https://www.gnu.org/software/gawk/manual/html_node/] Top (The GNU Awk User's Guide)</ref>, though it can be used for other general-purpose tasks. This page will focus primarily on GNU Awk, or GAWK/<code>gawk</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/], Although the language name is officially stylized AWK, GNU officially uses the stylization Awk. They also acknowledge that the language itself is spelled AWK.</ref>. == Basic Usage == One of the most basic ways to use AWK is in a pipe to filter columnar data. For example, <code>cat file.txt | awk '{ print $1 }'</code> will print the first (space-delimited) column of a given file. This can be generalized to the second, third, etc. columns using <code>$2</code>, <code>$3</code>, etc. respectively. AWK can also be ran with <code>awk 'program-here' input-file1 input-file2 ...</code><ref>[https://www.gnu.org/software/gawk/manual/html_node/One_002dshot.html] One-shot (The GNU Awk User's Guide)</ref>, so the above example with <code>cat</code> could also be written as: <pre> awk '{ print $1 }' file.txt </pre>More usage examples can be found on the [https://www.gnu.org/software/gawk/manual/html_node/Command-Line.html GAWK manual page], as well as AWK's [https://www.gnu.org/software/gawk/manual/html_node/Options.html many command-line options]. == AWK as a Language == AWK can also be used as a programming language. AWK programs consist of a list of patterns followed by actions to perform for each of those patterns<ref>[https://www.gnu.org/software/gawk/manual/html_node/Getting-Started.html] Getting Started (The GNU Awk User's Guide)</ref>: <pre> pattern { action } pattern { action } ... </pre> === BEGIN and END === Two common patterns are <code>BEGIN</code> and <code>END</code>, which run the given action before and after any text is processed respectively. These are called the "startup" and "cleanup" actions<ref>[https://www.gnu.org/software/gawk/manual/html_node/Using-BEGIN_002fEND.html] Using BEGIN/END (The GNU Awk User's Guide)</ref>. For example, the following code will print "Hello, World!": <pre> awk 'BEGIN { print "Hello, World!" }' </pre> The following will accept input until an EOF (inputtable in many shells as Ctrl+D), then print "Hello, World!": <pre> awk 'END { print "Hello, World!" }' </pre> === Regex Pattern === AWK can also be used to run a command for every line that matches a given regular expression. The following example prints every line that contains "regex" (equivalent to <code>grep 'regex'</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Regexp-Usage.html] Regexp Usage (The GNU Awk User's Guide)</ref>:<syntaxhighlight lang="awk"> /regex/ { print } </syntaxhighlight>The <code>{ print }</code> is actually implicit, meaning it can also be written:<syntaxhighlight lang="awk"> /regex/ </syntaxhighlight>One can combine this with <code>$1</code>, <code>$2</code>, etc. to print the second column of every row containing a given string, for example:<syntaxhighlight lang="awk"> /regex/ { print $2 } </syntaxhighlight> === Operations === AWK can be used to perform operations seen in many other programming languages, such as addition (<code>+</code>), subtraction (<code>-</code>), multiplication (<code>*</code>), division (<code>/</code>), modulus (<code>%</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Arithmetic-Ops.html] Arithmetic Ops (The GNU Awk User's Guide)</ref>, variable assignment (<code>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Assignment-Ops.html] Assignment Ops (The GNU Awk User's Guide)</ref>, equality (<code>==</code>) and inequality checks (<code>!=</code>), and comparisons (<code><</code>, <code><=</code>, <code>></code>, <code>>=</code>)<ref>[https://www.gnu.org/software/gawk/manual/html_node/Comparison-Operators.html] Comparison Operators (The GNU Awk User's Guide)</ref>. === ARGC and ARGV === Like many other programming languages, AWK programs can parse command-line arguments. The <code>ARGC</code> and <code>ARGV</code> variables (among [https://www.gnu.org/software/gawk/manual/html_node/Built_002din-Variables.html many others]) store the count of the arguments and an array of the arguments respectively<ref>[https://www.gnu.org/software/gawk/manual/html_node/Auto_002dset.html#index-ARGC_002fARGV-variables] ARGC, ARGV - Auto-set (The GNU Awk User’s Guide)</ref>. == References == <references /> b84edc1c839786474f2afef81f785d03160d4427 2 822 3421 2025-08-09T17:05:25Z Madonuko 140 why are there no emojis huh css text/css @import url('https://fonts.googleapis.com/css2?family=Noto+Color+Emoji&display=swap'); .comment, .autocomment { font-family: var(--font-family-base), 'Noto Color Emoji'; } 389edd8bc98725e794bc9a1bae7d15f6ffe300c9 0 823 3422 2025-08-09T18:57:58Z Peanut 229 I created the new page for the Geeko mascot of openSUSE. wikitext text/x-wiki [[File:OpenSUSE Button.svg|alt=Geeko is a chameleon drawing and is the mascot for openSUSE.|thumb]] '''Geeko''' is the official mascot of openSUSE. It is a chameleon and not a gecko.<ref>https://en.opensuse.org/openSUSE:Geeko, openSUSE, 2010-07-14 (Accessed: 9 August 2025). </ref> == References == <references /> [[Category:Mascots]] 7125b6610e0ddaf964e221d0c6386a24fb4e747a 3424 3422 2025-08-09T19:01:46Z Peanut 229 Link to openSUSE atl wiki page added. wikitext text/x-wiki [[File:OpenSUSE Button.svg|alt=Geeko is a chameleon drawing and is the mascot for openSUSE.|thumb]] '''Geeko''' is the official mascot of [[openSUSE]]. It is a chameleon and not a gecko.<ref>https://en.opensuse.org/openSUSE:Geeko, openSUSE, 2010-07-14 (Accessed: 9 August 2025). </ref> == References == <references /> [[Category:Mascots]] 287308791967a52261fb4dbf0092d5bc3e2f1cc6 0 198 3425 3391 2025-08-09T19:03:20Z Acceus 231 corrected formatting mistake wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] 053fff56b84d3f7dd6be935115694977b81d3ecc 3427 3425 2025-08-09T20:13:07Z Matvey 233 add Astra Linux wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] bfce38a1cc13d932e226161f4669378cb0ca4d52 0 169 3426 3373 2025-08-09T20:02:47Z Matvey 233 add homebrew to the list of package managers wikitext text/x-wiki {{Needs_Citations}}[[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories == List of Package Managers == All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained by the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper]/[[Rpm]], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] * [[Homebrew]] (or just brew) was originally created as a package manager for macOS, but it has Linux support too. You can install it on almost any distribution as an alternative package manager. You can find more information about it on [https://brew.sh/ the official website], the source is hosted [https://github.com/Homebrew/brew on GitHub] [[Category:Terminology]] 1f633ca5913eb5e90fc0f8bba1aa74daf941ed23 0 628 3428 3392 2025-08-09T20:17:06Z Matvey 233 Fix apt link wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[apt]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>[https://iso.atl.dev/l/linuxmint linuxmint - ATL ISO Archives], All Things Linux (Accessed: 2025-08-09)</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. The latest release, Linux Mint 22.1 "Xia", was launched in January 2025 and is supported until 2029.<ref>[https://www.linuxmint.com/download.php Download Linux Mint 22.1 - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> == References == b568b60bbfbf0b59f62bae855101bbfadfa0dff2 3431 3428 2025-08-09T20:19:06Z Matvey 233 fix broken apt link wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>[https://iso.atl.dev/l/linuxmint linuxmint - ATL ISO Archives], All Things Linux (Accessed: 2025-08-09)</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. The latest release, Linux Mint 22.1 "Xia", was launched in January 2025 and is supported until 2029.<ref>[https://www.linuxmint.com/download.php Download Linux Mint 22.1 - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> == References == 4b504319e900f8fb7b9057de16dab89e0a43f24e 0 661 3429 2966 2025-08-09T20:18:04Z Matvey 233 fix apt link wikitext text/x-wiki {{Needs Citations}}{{DistributionInfobox|title=Kali Linux|image=[[File:Kali-dragon-icon.svg|frameless]]|caption=Kali Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[APT]]|defaultdesktops=[[Xfce]], [[GNOME]], [[KDE Plasma]]|usagetype=Desktop, Mobile, USB|architectures=x86_64, x86, armel, armhf|website=[https://www.kali.org/ Kali.org]}}Kali Linux is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, Digital forensics, and penetration testing. e2b1450f7bee6b97f98fa272ea794da027077a71 0 784 3430 3189 2025-08-09T20:18:39Z Matvey 233 fix broken apt link wikitext text/x-wiki {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = GNOME | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }} Zorin OS is a ubuntu based linux distribution made for newcomers to linux, with a modifyed version of the Gnome GUI and XFCE 4 that is familiar to windows users. it also has paid model that comes with more desktop options and free software. it was frist realsed on the frist of july, 2009, under the name Zorin OS 1.0 95e8d529cfba61a7b7eceae507e33955a0d950f1 3000 824 3432 2025-08-09T21:18:03Z Maelstrom071 235 Created a basic guide on setting up and installing FL Studio 12 wikitext text/x-wiki FL Studio 12 has been tested to work very well under WINE. The recommended version to use is 12.5.1, as older versions have issues with loading WAV Vorbis files. Newer versions have not yet been tested. == Prerequisites == FL Studio is paid software. You will need to download your registry key file before starting this guide. You can still use the software in demo mode if you do not have a key. This guide requires [[Bottles]] to be installed. The recommended way of installing Bottles is via [[Flatpak]]. Using the caffe-9.7 runner is recommended as it fixes minor issues with cursor icons and windowing. Make sure it is installed by opening Bottles preferences via {{keypress|Ctrl|,}}. Then, select the "Runners" tab at the top, and expand the "Caffe" section. Find caffe-9.7 and click the download button next to it, if it is present. If you see a folder icon, then it is already installed. == Installation == === Preparing the bottle === Start by creating the bottle by clicking the "+" button in the top-left corner of the application Give the bottle a name, such as "FL Studio 12" (The name is not significant, this is only an example). Make sure "Application" is selected, then click "Runner" and choose "caffe-9.7". Finish by clicking create. Wait for the bottle to finish configuration, this may take up to 10 seconds. Once the bottle has been created, within its details menu, under the "Options" section, click the "Dependencies" button. Using the search button in the top-right corner, search for "allfonts" and then click the download button next to its result. Installation may take a while, so please be patient while it installs. Then, go back to the details page.<ref name=":0">{{Cite|url=https://github.com/Torbuntu/fl-studio-linux-setup|title=FL Studio Linux Setup|author=Torbuntu|year=2025|accessdate=2025-08-09}}</ref> In order for musical notation to be displayed correctly, the msgothic font must be installed manually. Download the file from https://github.com/FSKiller/Microsoft-Fonts/blob/main/msgothic.ttc, and save it to your downloads folder. Next, click the ellipses (three dots) on the top-right corner and select "Browse files...". This will open the bottle's C drive directory in your default file explorer. Navigate to "windows" then "Fonts" and copy the downloaded font file into this directory from your downloads.<ref name=":0" /> Back in the details page of the bottle, under the "Options" section, click the "Settings" button. Scroll down to the "Compatibility" section and change the Windows version to Windows 11.<ref name=":0" /> Finally, return back to the details page to prepare for installation. === Registering the software === Prior to installation, you must register the software (unless you intend to use it in demo mode). To do this, download your registry key from Image-Line's website and save it to your downloads. Copy it into your bottle by clicking the three dots on the top-right corner and selecting "Browse files...". Navigate to "users > steamuser > Documents", and copy your registry file into there. Now, back in Bottles, scroll down to the "Tools" section. From here, open the Registry editor. In the menu bar of the registry editor, click File > Import registry file... Within the browser, open "Documents" and then double click the registry file you copied into your bottle earlier. The registry editor will ask you to confirm, click yes, then once done, exit the registry editor. The software should now be registered === Installing FL Studio 12 === Scroll up in the details page, and click the "Run Executable..." button. Select the FL Studio 12.5.1 installer and click open. Proceed with setup as usual, select "All users" when prompted. De-select "ASIO4ALL" as it is known not to work very well under WINE. (Note, if you are '''not''' creating a new bottle and are upgrading an existing one, de-select "Clear" under the settings option, and select "Migrate previous version". If you '''are''' creating a new bottle, do '''not''' do this, or the installation will fail.). You can now launch the program from Bottles by clicking the run button next to "FL" (for the 32-bit version), and "FL 64" (for the 64-bit version). I recommend clicking the three dots next to each option, and selecting "Add desktop entry". This will add shortcuts to FL Studio within your desktop environment, so you can access it from your app launcher without needing to open Bottles every time. I also recommend you edit the desktop entry files using a tool such as [[KDE Menu Editor]] to give them more reasonable names. b71ca8a2e1ee50fa6b2706b6c7489b3df7a4cb4e 3435 3432 2025-08-09T21:31:11Z Maelstrom071 235 Added section for documents pass-through wikitext text/x-wiki FL Studio 12 has been tested to work very well under WINE. The recommended version to use is 12.5.1, as older versions have issues with loading WAV Vorbis files. Newer versions have not yet been tested. == Prerequisites == FL Studio is paid software. You will need to download your registry key file before starting this guide. You can still use the software in demo mode if you do not have a key. This guide requires [[Bottles]] to be installed. The recommended way of installing Bottles is via [[Flatpak]]. Using the caffe-9.7 runner is recommended as it fixes minor issues with cursor icons and windowing. Make sure it is installed by opening Bottles preferences via {{keypress|Ctrl|,}}. Then, select the "Runners" tab at the top, and expand the "Caffe" section. Find caffe-9.7 and click the download button next to it, if it is present. If you see a folder icon, then it is already installed. == Installation == === Preparing the bottle === Start by creating the bottle by clicking the "+" button in the top-left corner of the application Give the bottle a name, such as "FL Studio 12" (The name is not significant, this is only an example). Make sure "Application" is selected, then click "Runner" and choose "caffe-9.7". Finish by clicking create. Wait for the bottle to finish configuration, this may take up to 10 seconds. Once the bottle has been created, within its details menu, under the "Options" section, click the "Dependencies" button. Using the search button in the top-right corner, search for "allfonts" and then click the download button next to its result. Installation may take a while, so please be patient while it installs. Then, go back to the details page.<ref name=":0">{{Cite|url=https://github.com/Torbuntu/fl-studio-linux-setup|title=FL Studio Linux Setup|author=Torbuntu|year=2025|accessdate=2025-08-09}}</ref> In order for musical notation to be displayed correctly, the msgothic font must be installed manually. Download the file from https://github.com/FSKiller/Microsoft-Fonts/blob/main/msgothic.ttc, and save it to your downloads folder. Next, click the ellipses (three dots) on the top-right corner and select "Browse files...". This will open the bottle's C drive directory in your default file explorer. Navigate to "windows" then "Fonts" and copy the downloaded font file into this directory from your downloads.<ref name=":0" /> Back in the details page of the bottle, under the "Options" section, click the "Settings" button. Scroll down to the "Compatibility" section and change the Windows version to Windows 11.<ref name=":0" /> Finally, return back to the details page to prepare for installation. === Registering the software === Prior to installation, you must register the software (unless you intend to use it in demo mode). To do this, download your registry key from Image-Line's website and save it to your downloads. Copy it into your bottle by clicking the three dots on the top-right corner and selecting "Browse files...". Navigate to "users > steamuser > Documents", and copy your registry file into there. Now, back in Bottles, scroll down to the "Tools" section. From here, open the Registry editor. In the menu bar of the registry editor, click File > Import registry file... Within the browser, open "Documents" and then double click the registry file you copied into your bottle earlier. The registry editor will ask you to confirm, click yes, then once done, exit the registry editor. The software should now be registered === Installing FL Studio 12 === Scroll up in the details page, and click the "Run Executable..." button. Select the FL Studio 12.5.1 installer and click open. Proceed with setup as usual, select "All users" when prompted. De-select "ASIO4ALL" as it is known not to work very well under WINE. (Note, if you are '''not''' creating a new bottle and are upgrading an existing one, de-select "Clear" under the settings option, and select "Migrate previous version". If you '''are''' creating a new bottle, do '''not''' do this, or the installation will fail.). You can now launch the program from Bottles by clicking the run button next to "FL" (for the 32-bit version), and "FL 64" (for the 64-bit version). I recommend clicking the three dots next to each option, and selecting "Add desktop entry". This will add shortcuts to FL Studio within your desktop environment, so you can access it from your app launcher without needing to open Bottles every time. I also recommend you edit the desktop entry files using a tool such as [[KDE Menu Editor]] to give them more reasonable names. == Tweaks == === Documents folder pass-through === It is likely that you'll need to share files between FL Studio and your main system (Project files, samples, etc.). The simplest way to do this is by creating a dedicated folder in your Documents directory, and linking it somewhere within your bottle's C drive. You may also pass through your entire home directory or documents directory, however this is not typically recommended for security purposes, as it requires allowing all other bottles access too. First create the desired directory in your file explorer, and then create a symbolic link ('''NOT''' a shortcut). This can be done in Dolphin by dragging and dropping a directory, then selecting "Link Here". To open your bottle's documents folder, go to bottles, click on your bottle, click the three dots on the top-right, and select "Browse files..." Now navigate to "users > steamuser > Documents". Drag and drop your folder here, and select "Link Here". Now, we must authorize Bottles to access this directory. The easiest way to do this is via [[Flatseal]]. Within the application, in the list on the left hand side, search for "Bottles". Once selected, in the page on the right, scroll down to the "Filesystem" section. If you wish to expose your entire home directory (Not recommended), enable the "All user files" toggle. Otherwise, click the add button next to "Other files", add an entry, such as "~/Documents/<your folder here>". (~) replaces your own home directory, so change this as needed. If you want to use an absolute path instead; "/home/<username>/Documents/<your folder here>". Now, you should be able to access this directory within FL Studio == References == ec81646854b832b0c60ebec5cd085b3049ea6390 6 825 3433 2025-08-09T21:21:32Z Keiran 236 wikitext text/x-wiki Shows an example of Helix being used within a Rust codebase. 4b01fd8b9b9d7927726f2515473c476c2e644968 0 826 3434 2025-08-09T21:24:47Z Keiran 236 Write the introductory paragraph wikitext text/x-wiki [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]] and [[Kakoune]]. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Helix bundles and enables many features out of the box and does not yet have a plugin system. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. However, many users decide to fork Helix in order to add functionality that isn't included out of the box. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] 5e3caf581ae1663d6443a0fbfa43cd1c4caf47dd 0 827 3436 2025-08-09T21:52:05Z Keiran 236 :3 wikitext text/x-wiki '''Wayland''' is a communication protocol that specifies the communication between a display server and its clients, as well as a [[C (programming language)|C]] library implementation of that protocol. A display server using the Wayland protocol is called a ''[[Wayland#Wayland compositors|Wayland compositor]]'', because it additionally performs the task of a compositing window manager. Wayland is developed by a group of volunteers initially led by Kristian Høgsberg as a free and open-source community-driven project with the aim of replacing the X Window System with a secure and simpler windowing system for [[Linux]] and other [[Unix]]-like operating systems. The project's source code is published under the terms of the [[MIT License]], a permissive free software license. The Wayland project also develops an implementation of a Wayland compositor called ''[[Wayland#Weston|Weston]]''. == Overview == [[File:Wayland_display_server_protocol.svg|right|thumb]] The Wayland Display Server project was started by [[Red Hat]] developer Kristian Høgsberg in 2008. Beginning around 2010, Linux desktop graphics have moved from having "a pile of rendering interfaces... all talking to the X server, which is at the center of the universe" towards putting the Linux kernel and its components (i.e. Direct Rendering Infrastructure (DRI), Direct Rendering Manager (DRM)) "in the middle", with "window systems like X and Wayland ... off in the corner". This will be "a much-simplified graphics system offering more flexibility and better performance". Høgsberg could have added an [[Xdmx|extension to X]] as many recent projects have done, but preferred to "[push] X out of the hotpath between clients and the hardware" for reasons explained in the project's FAQ. Wayland consists of a protocol and a reference implementation named [[Wayland#Weston|Weston]]. The project is also developing versions of [[GTK]] and [[Qt (software)|Qt]] that render to Wayland instead of to X. Most applications are expected to gain support for Wayland through one of these libraries without modification to the application. Initial versions of Wayland have not provided network transparency, though Høgsberg noted in 2010 that network transparency is possible. It was attempted as a Google Summer of Code project in 2011, but was not successful. Adam Jackson has envisioned providing remote access to a Wayland application by either "pixel-scraping" (like [[Virtual Network Computing|VNC]]) or getting it to send a "rendering command stream" across the network (as in [[Remote Desktop Protocol|RDP]], [[SPICE (protocol)|SPICE]] or [[X Window System|X11]]). As of early 2013, Høgsberg was experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor. In August 2017, GNOME saw the first such pixel-scraping VNC server implementation under Wayland. In modern Wayland compositors, network transparency is handled in an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] that implements the RemoteDesktop portal. Many Wayland compositors also include an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] for common tasks such as a native file picker for native applications and sandboxes such as [[Flatpak]] ([https://github.com/flatpak/xdg-desktop-portal-gtk xdg-desktop-portal-gtk] is commonly used as a fallback filepicker), screen recording, network transparency, screenshots, color picking, and other tasks that could be seen as needing user intervention and being security risks otherwise. Note that xdg-desktop-portal is not Flatpak or Wayland-specific, and can be used with alternative packaging systems and windowing systems. == Wayland compositors == [[File:Window_(windowing_system).svg|right|thumb|Typical elements of a [[Window (computing)|window]]. The Wayland protocol does not specify what software is responsible for rendering the [[window decoration]].{{r|Graesslin 2013 decorations}}]] [[File:KDE_Plasma_5.24_on_Arch_Linux_screenshot.png|thumb|Plasma 5.24.0 (February 2022) on Wayland ({{code|kwin_wayland}} compositor) under [[Arch Linux]]]] [[Display server|Display servers]] that implement the Wayland display server protocol are also called ''Wayland compositors'' because they additionally perform the task of a [[compositing window manager]]. A library called '''wlroots''' is a modular Wayland implementation that functions as a base for several compositors Some notable Wayland compositors are: * [[Wayland#Weston|Weston]] implementation from the Wayland development team. For details about Weston see below. * [[Enlightenment (window manager)|Enlightenment]] had Wayland support since version 0.20 * [[KWin]], the default wayland compositor of KDE Plasma * [[Mutter (software)|Mutter]], the default wayland compositor of GNOME * [[Sway (window manager)|Sway]] – a tiling Wayland compositor, based on wlroots; it is a drop-in replacement for the i3 X11 window manager. * Hyprland tiling Wayland compositor written in C++. Noteworthy features of Hyprland include dynamic tiling, tabbed windows, and a custom renderer that provides window animations, rounded corners, and Dual-Kawase Blur on transparent windows. * Woodland-based window-stacking compositor for Wayland written in C, inspired by TinyWL and focused on simplicity and stability. * labwc wlroots-based window-stacking compositor for Wayland, inspired by [[Openbox]]. It follows a similar approach and coding style to Sway. === Weston === [[Weston (software)|Weston]] is a Wayland compositor previously developed as the [[reference implementation]] of the protocol by the Wayland project. It is written in [[C (programming language)|C]] and released under the [[MIT License]]. Weston officially supports only [[Linux]] due to dependencies on kernel-specific features such as kernel mode-setting (KMS), the Graphics Execution Manager (GEM), and [[udev]]. On Linux, it handles input via [[evdev]] and buffer management via Generic Buffer Management (GBM). A prototype port for [[FreeBSD]] was announced in 2013. The compositor supports High-bandwidth Digital Content Protection (HDCP) and uses GEM to share buffers between applications and the compositor. It features a plug-in architecture with "shells" that provide elements like docks and panels. Applications are responsible for rendering their own window decorations. Weston supports rendering via [[OpenGL ES]] or the [[pixman]] library for software rendering. The full OpenGL stack is avoided to prevent pulling in [[GLX]] and other [[X Window System]] dependencies. A remote desktop interface for Weston was proposed in 2013 by a developer from [[RealVNC]]. ==== Maynard ==== [[File:Maynard_desktop.png|thumb|Maynard (in January 2017)]] '''''Maynard''''' is a [[graphical shell]] and has been written as a plug-in for Weston, just as the [[GNOME Shell]] has been written as a plug-in to [[Mutter (software)|Mutter]]. The [[Raspberry Pi Holdings|Raspberry Pi]] in collaboration with [[Collabora]] released Maynard. === libinput === [[File:Libinput_for_Wayland_compositors.svg|thumb|libinput was created to consolidate the input stack across multiple Wayland compositors.]] The Weston code for handling input devices (keyboards, pointers, touch screens, etc.) was split into its own separate library, called ''libinput'', for which support was first merged in Weston 1.5. Libinput handles input devices for multiple Wayland compositors and also provides a generic [[X.Org Server]] input driver. It aims to provide one implementation for multiple Wayland compositors with a common way to handle input events while minimizing the amount of custom input code compositors need to include. libinput provides device detection (via [[udev]]), device handling, input device event processing and abstraction. Version 1.0 of libinput followed version 0.21, and included support for tablets, button sets and touchpad gestures. This version will maintain stable API/ABI. As GNOME/GTK and [[KDE Frameworks 5]] have mainlined the required changes, Fedora 22 will replace X.Org's evdev and Synaptics drivers with libinput. With version 1.16, the [[X.Org Server]] obtained support for the libinput library in form of a wrapper called [[Mono]]. === Wayland Security Module === Wayland Security Module is a proposition that resembles the [[Linux Security Module]] interface found in the [[Linux kernel]]. Some applications (especially the ones related to [[accessibility]]) require privileged capabilities that should work across different Wayland compositors. Currently, applications under Wayland are generally unable to perform any sensitive tasks such as taking screenshots or injecting input events without going through [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] or obtaining privileged access to the system. Wayland Security Module is a way to delegate security decisions within the compositor to a centralized security decision engine. == Adoption == The Wayland protocol is designed to be simple so that additional protocols and interfaces need to be defined and implemented to achieve a holistic windowing system. While many graphical toolkits already fully support Wayland, the developers of the [[Graphical shell|graphical shells]] are cooperating with the Wayland developers to create the necessary additional interfaces. === Desktop Linux distributions === Most major Linux distributions default to using Wayland. Some notable examples are: * [[Debian]] ships Wayland as the default session for GNOME since version [[Debian 10|10 (Buster)]], released 6 July 2019. * [[Fedora Linux|Fedora]] starting with version 25 (released 22 November 2016) uses Wayland for the default GNOME 3.22 desktop session, with [[X.Org Server|X.Org]] as a fallback if the graphics driver cannot support Wayland. Fedora uses Wayland as the default for KDE desktop session starting with version 34 (released 27 April 2021) * [[Manjaro]] ships Wayland as default in the Gnome edition of Manjaro 20.2 (Nibia) (released 22 November 2020). * [[Raspberry Pi OS]], a port of Debian, has offered the option to use Wayland since version [[Debian 11|11 (Bullseye)]], which was released on 3 December 2021. Wayland became the default in version [[Debian 12|12 (Bookworm)]], released on 10 October 2023. * [[Red Hat Enterprise Linux]] ships Wayland as the default session in version 8, released 7 May 2019. * [[Ubuntu (operating system)|Ubuntu]] shipped with Wayland by default in Ubuntu 17.10 (Artful Aardvark). However, Ubuntu 18.04 LTS reverted to X.Org by default due to several issues. Since Ubuntu 21.04, Wayland is the default again. * [[Slackware Linux]] included Wayland on 20 February 2020 for the development version, -current, which became version 15.0 in 2022. However, Wayland is still not the default. == History == Kristian Høgsberg, a [[Linux]] graphics and [[X.Org Server|X.Org]] developer who previously worked on [[AIGLX]] and [[Direct Rendering Infrastructure|DRI2]], started Wayland as a spare-time project in 2008 while working for [[Red Hat]]. His stated goal was a system in which "every frame is perfect, by which I mean that applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker." Høgsberg was driving through the town of Wayland, Massachusetts when the underlying concepts "crystallized", hence the name (Weston and Maynard are also nearby towns in the same area, continuing the reference). In October 2010, Wayland became a [[freedesktop.org]] project. As part of the migration, the prior Google Group was replaced by the ''wayland-devel'' mailing list as the project's central point of discussion and development. The Wayland client and server libraries were initially released under the [[MIT License]], while the reference compositor Weston and some example clients used the [[GNU General Public License version 2]]. Later, all the GPL code was relicensed under the MIT license "to make it easier to move code between the reference implementation and the actual libraries". In 2015 it was discovered that the license text used by Wayland was a slightly different and older version of the MIT license, and the license text was updated to the current version used by the [[X.Org Server|X.Org project]] (known as [[Expat License|MIT Expat License]]). {| class="wikitable sortable collapsible text-align:center" |} e8bd459ea8aad1de2159f3d190b99ccf22908d74 0 828 3437 2025-08-09T21:57:52Z Keiran 236 source: https://en.wikipedia.org/wiki/Udev wikitext text/x-wiki '''udev''' (userspace {{mono|[[devfs|/dev]]}}) is a device manager for the [[Linux kernel]]. As the successor of [[devfsd]] and hotplug, udev primarily manages device nodes in the {{mono|[[devfs|/dev]]}} directory. At the same time, udev also handles all [[user space]] events raised when hardware devices are added into the system or removed from it, including [[firmware]] loading as required by certain devices. == Rationale == It is an [[operating system]]'s [[Kernel (operating system)|kernel]] that is responsible for providing an abstract interface of the hardware to the rest of the software. Being a [[monolithic kernel]], the [[Linux kernel]] does exactly that: device drivers are part of the Linux kernel, and make up more than half of its source code. Hardware can be accessed through [[System call|system calls]] or over their device nodes. To be able to deal with peripheral devices that are [[hotplug]]-capable in a user-friendly way, a part of handling all of these hotplug-capable hardware devices was handed over from the kernel to a [[Daemon (computing)|daemon]] running in user-space. Running in user space serves security and stability purposes. == Design == Device drivers are part of the Linux kernel, in which their primary functions include device discovery, detecting device state changes, and similar low-level hardware functions. After loading a device driver into memory from the kernel, detected events are sent out to the userspace daemon udevd. It is the device manager, {{Mono|udevd}}, that catches all of these events and then decides what shall happen next. For this, {{Mono|udevd}} has a very comprehensive set of configuration files, which can all be adjusted by the computer administrator, according to their needs. * In case a new storage device is connected over USB, {{Mono|udevd}} is notified by the kernel and itself notifies the udisksd-daemon. That daemon could then mount the file systems. * In case a new Ethernet cable is plugged into the Ethernet NIC, {{Mono|udevd}} is notified by the kernel and itself notifies the NetworkManager-daemon. The NetworkManager-daemon could start dhclient for that NIC, or configure according to some manual configuration. The complexity of doing so forced application authors to re-implement hardware support logic. Some hardware devices also required privileged helper programs to prepare them for use. These often have to be invoked in ways that could be awkward to express with the Unix permissions model (for example, allowing users to join [[Wireless network|wireless networks]] only if they are logged into the video console). Application authors resorted to using [[setuid]] binaries or run service [[Daemon (computing)|daemons]] to provide their own access control and privilege separation, potentially introducing security holes each time. [[HAL (software)|HAL]] was created to deal with these challenges, but is now deprecated in most Linux distributions, its functionality being replaced by udevd. == Overview == Unlike traditional [[Unix]] systems, where the device nodes in the {{mono|/dev}} directory have been a static set of files, the Linux udev device manager dynamically provides only the nodes for the devices actually present on a system. Although [[devfs]] used to provide similar functionality, Greg Kroah-Hartman cited a number of reasons for preferring udev over devfs: * udev supports persistent device naming, which does not depend on, for example, the order in which the devices are plugged into the system. The default udev setup provides persistent names for storage devices. Any hard disk is recognized by its unique filesystem id, the name of the disk and the physical location on the hardware it is connected to. * udev executes entirely in [[user space]], as opposed to devfs's [[kernel space]]. One consequence is that udev moved the naming policy out of the kernel and can run arbitrary programs to compose a name for the device from the device's properties, before the node is created; there, the whole process is also interruptible and it runs with a lower priority. The udev, as a whole, is divided into three parts: * [[Library (computing)|Library]] ''libudev'' that allows access to device information; it was incorporated into the [[systemd]] 183 software bundle. * User space [[Daemon (computing)|daemon]] {{Mono|udevd}} that manages the virtual {{Mono|/dev}}. * Administrative [[command-line utility]] {{Mono|udevadm}} for diagnostics. The system gets calls from the kernel via [[netlink]] socket. Earlier versions used [[Hotplug (software)|hotplug]], adding a link to themselves in {{mono|/etc/hotplug.d/default}} with this purpose. == Operation == [[File:Free_and_open-source-software_display_servers_and_UI_toolkits.svg|thumb|350x350px|udev has been incorporated into [[systemd]] 183]] udev is a generic device manager running as a [[Daemon (computer software)|daemon]] on a Linux system and listening (via a [[netlink]] socket) to uevents the kernel sends out if a new device is initialized or a device is removed from the system. The udev package comes with an extensive set of rules that match against exported values of the event and properties of the discovered device. A matching rule will possibly name and create a device node and run configured programs to set up and configure the device. udev rules can match on properties like the kernel subsystem, the kernel device name, the physical location of the device, or properties like the device's serial number. Rules can also request information from external programs to name a device or specify a custom name that will always be the same, regardless of the order devices are discovered by the system. In the past a common way to use udev on Linux systems was to let it send events through a socket to [[HAL (software)|HAL]], which would perform further device-specific actions. For example, HAL would notify other software running on the system that the new hardware had arrived by issuing a broadcast message on the [[D-Bus]] [[Inter-process communication|IPC]] system to all interested [[Process (computing)|processes]]. In this way, desktops such as [[GNOME]] or [[K Desktop Environment 3]] could start the [[file browser]] to browse the file systems of newly attached [[USB flash drive|USB flash drives]] and [[Secure Digital|SD cards]]. By the middle of 2011 HAL had been deprecated by most Linux distributions as well as by the KDE, GNOME and [[Xfce]] desktop environments, among others. The functionality previously embodied in HAL has been integrated into udev itself, or moved to separate software such as udisks and [[upower]]. * udev provides low-level access to the linux device tree. Allows programs to enumerate devices and their properties and get notifications when devices come and go. * dbus is a framework to allow programs to communicate with each other, securely, reliably, and with a high-level object-oriented programming interface. * udisks (formerly known as DeviceKit-disks) is a daemon that sits on top of libudev and other kernel interfaces and provides a high-level interface to storage devices and is accessible via dbus to applications. * upower (formerly known as DeviceKit-power) is a daemon that sits on top of libudev and other kernel interfaces and provides a high-level interface to power management and is accessible via dbus to applications. * [[NetworkManager]] is a daemon that sits on top of libudev and other kernel interfaces (and a couple of other daemons) and provides a high-level interface to network configuration and setup and is accessible via dbus to apps. udev receives messages from the kernel, and passes them on to subsystem daemons such as Network Manager. Applications talk to Network Manager over D-Bus. : <chem>Kernel -> udev -> Network Manager <=> D-Bus <=> Firefox</chem> HAL is obsolete and only used by legacy code. Ubuntu 10.04 shipped without HAL. Initially a new daemon DeviceKit was planned to replace certain aspects of HAL, but in March 2009, DeviceKit was deprecated in favor of adding the same code to udev as a package: udev-extras, and some functions have now moved to udev proper. == History == udev was introduced in Linux 2.5. The Linux kernel version 2.6.13 introduced or updated a new version of the [[uevent]] interface. A system using a new version of udev will not boot with kernels older than 2.6.13 unless udev is disabled and a traditional {{mono|/dev}} directory is used for device access. In April 2012, udev's [[codebase]] was merged into the [[systemd]] source tree, making systemd 183 the first version to include udev. In October 2012, [[Linus Torvalds]] criticized Kay Sievers's approach to udev maintenance and bug fixing related to [[firmware]] loading, stating: {{quote|Yes, doing it in the kernel is "more robust". But don't play games, and stop the lying. It's more robust because we have maintainers that care, and because we know that regressions are not something we can play fast and loose with. If something breaks, and we don't know what the right fix for that breakage is, we ''revert'' the thing that broke. So yes, we're clearly better off doing it in the kernel. Not because firmware loading cannot be done in user space. But simply because udev maintenance since Greg gave it up has gone downhill.}} In 2012, the [[Gentoo Linux]] project created a [[Fork (software development)|fork]] of systemd's udev codebase in order to avoid dependency on the systemd architecture. The resulting fork is called ''[[eudev]]'' and it makes udev functionality available without systemd. A stated goal of the project is to keep eudev independent of any [[Linux distribution]] or [[init]] system. The Gentoo project describes eudev as follows: {{quote|eudev is a fork of systemd-udev with the goal of obtaining better compatibility with existing software such as [[OpenRC]] and [[Upstart (software)|Upstart]], older kernels, various toolchains and anything else required by users and various distributions.}} On May 29, 2014, support for firmware loading through udev was dropped from systemd, as it has been decided that it is the kernel's task to load firmware. Two days later, Lennart Poettering suggested this patch be postponed until [[kdbus]] starts to be utilized by udev; at that point, the plan was to switch udev to use kdbus as the underlying messaging system, and to get rid of the userspace-to-userspace netlink-based transport. cf6c4d49cb39a92f4f1df9c0dabecd627bf8718b 3439 3437 2025-08-09T22:02:08Z Keiran 236 fix some formatting issues wikitext text/x-wiki '''udev''' is a device manager for the [[Linux kernel]]. As the successor of [[devfsd]] and hotplug, udev primarily manages device nodes in the directory. At the same time, udev also handles all [[user space]] events raised when hardware devices are added into the system or removed from it, including [[firmware]] loading as required by certain devices. == Rationale == It is an [[operating system]]'s [[Kernel (operating system)|kernel]] that is responsible for providing an abstract interface of the hardware to the rest of the software. Being a [[monolithic kernel]], the [[Linux kernel]] does exactly that: device drivers are part of the Linux kernel, and make up more than half of its source code. Hardware can be accessed through [[System call|system calls]] or over their device nodes. To be able to deal with peripheral devices that are [[hotplug]]-capable in a user-friendly way, a part of handling all of these hotplug-capable hardware devices was handed over from the kernel to a [[Daemon (computing)|daemon]] running in user-space. Running in user space serves security and stability purposes. == Design == Device drivers are part of the Linux kernel, in which their primary functions include device discovery, detecting device state changes, and similar low-level hardware functions. After loading a device driver into memory from the kernel, detected events are sent out to the userspace daemon udevd. It is the device manager that catches all of these events and then decides what shall happen next. This has a very comprehensive set of configuration files, which can all be adjusted by the computer administrator, according to their needs. * In case a new storage device is connected over USB, udevd is notified by the kernel and itself notifies the udisksd-daemon. That daemon could then mount the file systems. * In case a new Ethernet cable is plugged into the Ethernet NIC, udevd is notified by the kernel and itself notifies the NetworkManager-daemon. The NetworkManager-daemon could start dhclient for that NIC, or configure according to some manual configuration. The complexity of doing so forced application authors to re-implement hardware support logic. Some hardware devices also required privileged helper programs to prepare them for use. These often have to be invoked in ways that could be awkward to express with the Unix permissions model (for example, allowing users to join [[Wireless network|wireless networks]] only if they are logged into the video console). Application authors resorted to using [[setuid]] binaries or run service [[Daemon (computing)|daemons]] to provide their own access control and privilege separation, potentially introducing security holes each time. [[HAL (software)|HAL]] was created to deal with these challenges, but is now deprecated in most Linux distributions, its functionality being replaced by udevd. == Overview == Unlike traditional [[Unix]] systems, where the device nodes in the /dev directory have been a static set of files, the Linux udev device manager dynamically provides only the nodes for the devices actually present on a system. Although [[devfs]] used to provide similar functionality, Greg Kroah-Hartman cited a number of reasons for preferring udev over devfs: * udev supports persistent device naming, which does not depend on, for example, the order in which the devices are plugged into the system. The default udev setup provides persistent names for storage devices. Any hard disk is recognized by its unique filesystem id, the name of the disk and the physical location on the hardware it is connected to. * udev executes entirely in [[user space]], as opposed to devfs's [[kernel space]]. One consequence is that udev moved the naming policy out of the kernel and can run arbitrary programs to compose a name for the device from the device's properties, before the node is created; there, the whole process is also interruptible and it runs with a lower priority. The udev, as a whole, is divided into three parts: * [[Library (computing)|Library]] ''libudev'' that allows access to device information; it was incorporated into the [[systemd]] 183 software bundle. * User space [[Daemon (computing)|daemon]] udevd that manages the virtual /dev. * Administrative [[command-line utility]] udevadm for diagnostics. The system gets calls from the kernel via [[netlink]] socket. Earlier versions used [[Hotplug (software)|hotplug]], adding a link to themselves in /etc/hotplug.d/default with this purpose. == Operation == [[File:Free_and_open-source-software_display_servers_and_UI_toolkits.svg|thumb|350x350px|udev has been incorporated into [[systemd]] 183]] udev is a generic device manager running as a [[Daemon (computer software)|daemon]] on a Linux system and listening (via a [[netlink]] socket) to uevents the kernel sends out if a new device is initialized or a device is removed from the system. The udev package comes with an extensive set of rules that match against exported values of the event and properties of the discovered device. A matching rule will possibly name and create a device node and run configured programs to set up and configure the device. udev rules can match on properties like the kernel subsystem, the kernel device name, the physical location of the device, or properties like the device's serial number. Rules can also request information from external programs to name a device or specify a custom name that will always be the same, regardless of the order devices are discovered by the system. In the past a common way to use udev on Linux systems was to let it send events through a socket to [[HAL (software)|HAL]], which would perform further device-specific actions. For example, HAL would notify other software running on the system that the new hardware had arrived by issuing a broadcast message on the [[D-Bus]] [[Inter-process communication|IPC]] system to all interested [[Process (computing)|processes]]. In this way, desktops such as [[GNOME]] or [[K Desktop Environment 3]] could start the [[file browser]] to browse the file systems of newly attached [[USB flash drive|USB flash drives]] and [[Secure Digital|SD cards]]. By the middle of 2011 HAL had been deprecated by most Linux distributions as well as by the KDE, GNOME and [[Xfce]] desktop environments, among others. The functionality previously embodied in HAL has been integrated into udev itself, or moved to separate software such as udisks and [[upower]]. * udev provides low-level access to the linux device tree. Allows programs to enumerate devices and their properties and get notifications when devices come and go. * dbus is a framework to allow programs to communicate with each other, securely, reliably, and with a high-level object-oriented programming interface. * udisks (formerly known as DeviceKit-disks) is a daemon that sits on top of libudev and other kernel interfaces and provides a high-level interface to storage devices and is accessible via dbus to applications. * upower (formerly known as DeviceKit-power) is a daemon that sits on top of libudev and other kernel interfaces and provides a high-level interface to power management and is accessible via dbus to applications. * [[NetworkManager]] is a daemon that sits on top of libudev and other kernel interfaces (and a couple of other daemons) and provides a high-level interface to network configuration and setup and is accessible via dbus to apps. udev receives messages from the kernel, and passes them on to subsystem daemons such as Network Manager. Applications talk to Network Manager over D-Bus. : <chem>Kernel -> udev -> Network Manager <=> D-Bus <=> Firefox</chem> HAL is obsolete and only used by legacy code. Ubuntu 10.04 shipped without HAL. Initially a new daemon DeviceKit was planned to replace certain aspects of HAL, but in March 2009, DeviceKit was deprecated in favor of adding the same code to udev as a package: udev-extras, and some functions have now moved to udev proper. == History == udev was introduced in Linux 2.5. The Linux kernel version 2.6.13 introduced or updated a new version of the [[uevent]] interface. A system using a new version of udev will not boot with kernels older than 2.6.13 unless udev is disabled and a traditional /dev directory is used for device access. In April 2012, udev's [[codebase]] was merged into the [[systemd]] source tree, making systemd 183 the first version to include udev. In October 2012, [[Linus Torvalds]] criticized Kay Sievers's approach to udev maintenance and bug fixing related to [[firmware]] loading. In 2012, the [[Gentoo Linux]] project created a [[Fork (software development)|fork]] of systemd's udev codebase in order to avoid dependency on the systemd architecture. The resulting fork is called ''[[eudev]]'' and it makes udev functionality available without systemd. A stated goal of the project is to keep eudev independent of any [[Linux distribution]] or [[init]] system. On May 29, 2014, support for firmware loading through udev was dropped from systemd, as it has been decided that it is the kernel's task to load firmware. Two days later, Lennart Poettering suggested this patch be postponed until [[kdbus]] starts to be utilized by udev; at that point, the plan was to switch udev to use kdbus as the underlying messaging system, and to get rid of the userspace-to-userspace netlink-based transport. f3732e0fdfd9784c62461fb8f887514030abad26 6 829 3438 2025-08-09T22:00:13Z Maelstrom071 235 wikitext text/x-wiki The runners screen in Bottles' settings dbf866ac037cfa35071d8585b4249867ec576237 6 830 3440 2025-08-09T22:05:10Z Maelstrom071 235 wikitext text/x-wiki Bottles details screen with the options, dependencies, registry editor, and meatballs menu highlighted 8b8ccd6ecd253806c32235fbafd4237b5021bd58 6 831 3441 2025-08-09T22:07:01Z Maelstrom071 235 wikitext text/x-wiki FL Studio 12 installer with annotations highlighting specific options 81bf398fb94c338edee8cadd564f3ba85ed908d2 2 832 3442 2025-08-09T22:07:24Z TheCommCraft 238 Created page with "[[File:Https://willroll.thecommcraft.de/img8151398|frame|My PFP]]" wikitext text/x-wiki [[File:Https://willroll.thecommcraft.de/img8151398|frame|My PFP]] 77b031c5409fe4e3d26bbd742d8cf00e73aed9f3 2 833 3443 2025-08-09T22:09:05Z Keiran 236 uwu wikitext text/x-wiki '''Keiran''' is a UK-based student and developer with a mild obsession for customising everything until it breaks, then fixing it "for the experience". A proud [[Arch Linux]] user, Keiran runs the [[Fish]] shell by default, edits code in the [[Helix]] text editor for terminal work, occasionally switching to [[Neovim]] when the lack of plugins is just too unbearable. 5a6ec988fb98df57e0c618d493d09ccfc82eeb7b 6 834 3444 2025-08-09T22:11:15Z Maelstrom071 235 wikitext text/x-wiki FL Studio 12 installer highlighted with relevant options f2935e91aebea3c2ff11e964b3482f7b05b719da 6 835 3445 2025-08-09T22:12:53Z Maelstrom071 235 wikitext text/x-wiki Flatseal app open with Bottles settings with Filesystem options highlighted c1f5157610d633914fa92dcbc6526f8632b4ad0a 0 268 3446 3312 2025-08-09T22:14:01Z Keiran 236 Make the intro more descriptive, link terms, mention cross-platform support, add categories wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch running on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C (programming language)|C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch GitHub repository] }} '''Fastfetch''' is a cross-platform command-line utility for displaying system information, similar in purpose to [[Neofetch]]. It is primarily written in [[C (programming language)|C]] and is designed with a strong focus on speed and low resource usage. Fastfetch can display details about the [[Operating system|operating system]], hardware components, and installed software in a highly configurable format. The tool supports a wide range of modules, allowing users to customise the output to include information such as CPU, GPU, memory, storage, display resolution, kernel version, package count, and more. It is actively maintained and available for Linux, macOS, and Windows. == See also == * [[Neofetch]] * [[Screenfetch]] == References == <references /> [[Category:Software]] [[Category:Command-line software]] [[Category:System information tools]] 433d6cb2a3666460c6ac5305af7b257d260ba792 3000 824 3447 3435 2025-08-09T22:14:36Z Maelstrom071 235 Added images and a warning and a few links wikitext text/x-wiki {{Guide_Warning}} [[FL Studio]] 12 has been tested to work very well under [[Wine|WINE]]. The recommended version to use is 12.5.1, as older versions have issues with loading WAV Vorbis files. Newer versions have not yet been tested. == Prerequisites == [[File:Bottles Runners screen.png|thumb|The runners page in Bottles, showing caffe-9.7 already installed]] FL Studio is paid software. You will need to download your registry key file before starting this guide. You can still use the software in demo mode if you do not have a key. This guide requires [[Bottles]] to be installed. The recommended way of installing Bottles is via [[Flatpak]]. Using the caffe-9.7 runner is recommended as it fixes minor issues with cursor icons and windowing. Make sure it is installed by opening Bottles preferences via {{keypress|Ctrl|,}}. Then, select the "Runners" tab at the top, and expand the "Caffe" section. Find caffe-9.7 and click the download button next to it, if it is present. If you see a folder icon, then it is already installed. == Installation == === Preparing the bottle === [[File:Bottles details screen (highlighted).png|thumb|The Bottles details screen with relevant menu options highlighted]] Start by creating the bottle by clicking the "+" button in the top-left corner of the application Give the bottle a name, such as "FL Studio 12" (The name is not significant, this is only an example). Make sure "Application" is selected, then click "Runner" and choose "caffe-9.7". Finish by clicking create. Wait for the bottle to finish configuration, this may take up to 10 seconds. Once the bottle has been created, within its details menu, under the "Options" section, click the "Dependencies" button. Using the search button in the top-right corner, search for "allfonts" and then click the download button next to its result. Installation may take a while, so please be patient while it installs. Then, go back to the details page.<ref name=":0">{{Cite|url=https://github.com/Torbuntu/fl-studio-linux-setup|title=FL Studio Linux Setup|author=Torbuntu|year=2025|accessdate=2025-08-09}}</ref> In order for musical notation to be displayed correctly, the msgothic font must be installed manually. Download the file from https://github.com/FSKiller/Microsoft-Fonts/blob/main/msgothic.ttc, and save it to your downloads folder. Next, click the ellipses (three dots) on the top-right corner and select "Browse files...". This will open the bottle's C drive directory in your default file explorer. Navigate to "windows" then "Fonts" and copy the downloaded font file into this directory from your downloads.<ref name=":0" /> Back in the details page of the bottle, under the "Options" section, click the "Settings" button. Scroll down to the "Compatibility" section and change the Windows version to Windows 11.<ref name=":0" /> Finally, return back to the details page to prepare for installation. === Registering the software === Prior to installation, you must register the software (unless you intend to use it in demo mode). To do this, download your registry key from Image-Line's website and save it to your downloads. Copy it into your bottle by clicking the three dots on the top-right corner and selecting "Browse files...". Navigate to "users > steamuser > Documents", and copy your registry file into there. Now, back in Bottles, scroll down to the "Tools" section. From here, open the Registry editor. In the menu bar of the registry editor, click File > Import registry file... Within the browser, open "Documents" and then double click the registry file you copied into your bottle earlier. The registry editor will ask you to confirm, click yes, then once done, exit the registry editor. The software should now be registered === Installing FL Studio 12 === [[File:FL Studio installer (highlighted).png|thumb|FL Studio 12 installer with relevant options highlighted]] Scroll up in the details page, and click the "Run Executable..." button. Select the FL Studio 12.5.1 installer and click open. Proceed with setup as usual, select "All users" when prompted. De-select "ASIO4ALL" as it is known not to work very well under WINE. (Note, if you are '''not''' creating a new bottle and are upgrading an existing one, de-select "Clear" under the settings option, and select "Migrate previous version". If you '''are''' creating a new bottle, do '''not''' do this, or the installation will fail.). You can now launch the program from Bottles by clicking the run button next to "FL" (for the 32-bit version), and "FL 64" (for the 64-bit version). I recommend clicking the three dots next to each option, and selecting "Add desktop entry". This will add shortcuts to FL Studio within your desktop environment, so you can access it from your app launcher without needing to open Bottles every time. I also recommend you edit the desktop entry files using a tool such as [[KDE Menu Editor]] to give them more reasonable names. == Tweaks == === Documents folder pass-through === [[File:Flatseal options for Bottles (highlighted).png|thumb|Flatseal with relevant options highlighted]] It is likely that you'll need to share files between FL Studio and your main system (Project files, samples, etc.). The simplest way to do this is by creating a dedicated folder in your Documents directory, and linking it somewhere within your bottle's C drive. You may also pass through your entire home directory or documents directory, however this is not typically recommended for security purposes, as it requires allowing all other bottles access too. First create the desired directory in your file explorer, and then create a symbolic link ('''NOT''' a shortcut). This can be done in [[Dolphin]] by dragging and dropping a directory, then selecting "Link Here". To open your bottle's documents folder, go to bottles, click on your bottle, click the three dots on the top-right, and select "Browse files..." Now navigate to "users > steamuser > Documents". Drag and drop your folder here, and select "Link Here". Now, we must authorize Bottles to access this directory. The easiest way to do this is via [[Flatseal]]. Within the application, in the list on the left hand side, search for "Bottles". Once selected, in the page on the right, scroll down to the "Filesystem" section. If you wish to expose your entire home directory (Not recommended), enable the "All user files" toggle. Otherwise, click the add button next to "Other files", add an entry, such as "~/Documents/<your folder here>". (~) replaces your own home directory, so change this as needed. If you want to use an absolute path instead; "/home/<username>/Documents/<your folder here>". Now, you should be able to access this directory within FL Studio == References == 2ef778c662c9b70ff7741918aaa8bb1bbd30462d 0 257 3448 3346 2025-08-09T22:20:42Z Keiran 236 Reduce repetition, improve structure, better linking, add categories wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.40.0, 2024-05-04 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor built on [[wlroots]]. It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Official Hyprland website]</ref> Hyprland uses its own configuration syntax, designed to be readable and easy to learn, with similarities to shell scripting. The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway (window manager)|Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] 8fcdcab60353b96e82a467abf058a91d4fa0101d 3481 3448 2025-08-10T04:09:34Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.40.0, 2024-05-04 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor built on [[wlroots]]. It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Hyprland], 2025-08-10 (Accessed: 2025-08-10)</ref> Hyprland uses its own configuration syntax, designed to be readable and easy to learn, with similarities to shell scripting. The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway (window manager)|Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] 58fbd9e8650378453b87d55f88a3da3c1f0959bd 14 390 3449 1378 2025-08-09T22:29:09Z Bont 128 Make the page more pleasant to view wikitext text/x-wiki == FOSS Mascots == <hr> ===== A ===== <hr> ===== B ===== * [[Beastie]] <hr> ===== C ===== <hr> ===== D ===== <hr> ===== E ===== <hr> ===== F ===== <hr> ===== G ===== * [[Geeko]] * [[Gnu]] <hr> ===== H ===== <hr> ===== I ===== <hr> ===== J ===== <hr> ===== K ===== * [[Konqi]] * [[Katie]] <hr> ===== L ===== * [[Larry the Cow|Larry The Cow]] <hr> ===== M ===== <hr> ===== N ===== <hr> ===== O ===== <hr> ===== P ===== * [[Puffy]] <hr> ===== Q ===== <hr> ===== R ===== <hr> ===== S ===== <hr> ===== T ===== * [[Tux]] <hr> ===== U ===== <hr> ===== V ===== <hr> ===== W ===== <hr> ===== X ===== * [[Xenia]] * [[Xue]] <hr> ===== Y ===== <hr> ===== Z ===== <hr> fbfe06d4e70d137e92903e4bc62484bd333a8564 3450 3449 2025-08-09T22:31:16Z Bont 128 add small bio wikitext text/x-wiki == FOSS Mascots == The pages listed below give information about characters that represent certain FOSS programs, utilities, or just represent anything that supports the community.<hr> ===== A ===== <hr> ===== B ===== * [[Beastie]] <hr> ===== C ===== <hr> ===== D ===== <hr> ===== E ===== <hr> ===== F ===== <hr> ===== G ===== * [[Geeko]] * [[Gnu]] <hr> ===== H ===== <hr> ===== I ===== <hr> ===== J ===== <hr> ===== K ===== * [[Konqi]] * [[Katie]] <hr> ===== L ===== * [[Larry the Cow|Larry The Cow]] <hr> ===== M ===== <hr> ===== N ===== <hr> ===== O ===== <hr> ===== P ===== * [[Puffy]] <hr> ===== Q ===== <hr> ===== R ===== <hr> ===== S ===== <hr> ===== T ===== * [[Tux]] <hr> ===== U ===== <hr> ===== V ===== <hr> ===== W ===== <hr> ===== X ===== * [[Xenia]] * [[Xue]] <hr> ===== Y ===== <hr> ===== Z ===== <hr> 6618527c4be0dfb623e2d7c758120ac7b6ca4151 3452 3450 2025-08-09T23:03:32Z Bont 128 remove everything i did because it doesnt align with the guidelines wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 3465 3452 2025-08-09T23:29:45Z Bont 128 update page to meet guideline requirements wikitext text/x-wiki ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[FreeBSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] |[[Linux]] |} c5bc22fcbf965748df757b7bd238c92d3bebaa81 3466 3465 2025-08-09T23:33:25Z Bont 128 add a small bio wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[FreeBSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] |[[Linux]] |} 5c881c9a9a2250aef69b43f0cc193f0e94cc0eb5 10 208 3451 2094 2025-08-09T23:03:16Z Atmois 13 Removed protection from "[[Template:MascotInfobox]]": Revert to namespace protections wikitext text/x-wiki <includeonly>{{#invoke:MascotInfobox|main}}</includeonly> <noinclude>{{/doc}}</noinclude> c36d7ff1b6cb50d7f0ba5e04a0773be754b0f03c 2 832 3453 3442 2025-08-09T23:10:02Z TheCommCraft 238 joke added wikitext text/x-wiki <nowiki>#</nowiki>"><nowiki><img src=/ onerror=alert(2)></nowiki> c3e80ad70fc3392411a4a086429a37257a69d367 828 163 3454 671 2025-08-09T23:21:13Z Atmois 13 Removed protection from "[[Module:DistributionInfobox]]": Revert to namespace protections Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Default Desktops', args.defaultdesktops ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Architectures', args.architectures ) :addRow( 'Website', args.website ) return retval end return p b660d45c0da77b4a0dd8716d3dabe7d016998a92 828 525 3455 1721 2025-08-09T23:21:21Z Atmois 13 Removed protection from "[[Module:DistributionInfobox/doc]]": Revert to namespace protections wikitext text/x-wiki == Usage == In order to embed a infobox for distributions, you can put this at the very top of your article <pre> {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Cinnamon, Enlightenment, GNOME, KDE, LXDE, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} </pre> 396630062f9135a503c62b55397ec552894960f7 828 530 3456 1745 2025-08-09T23:21:40Z Atmois 13 Removed protection from "[[Module:MascotInfobox/doc]]": Revert to namespace protections wikitext text/x-wiki == Usage == In order to embed a infobox for mascots, you can put this at the very top of your article <pre> {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} </pre> ecdc93523f9ddd05084135ea5e220060255e11e3 10 531 3457 1749 2025-08-09T23:21:50Z Atmois 13 Removed protection from "[[Template:MascotInfobox/doc]]": Revert to namespace protections wikitext text/x-wiki #REDIRECT [[Module:MascotInfobox/doc]] ff907f5cfbbe057f8bed0c2a318268c54f8e906f 828 207 3458 1743 2025-08-09T23:21:59Z Atmois 13 Removed protection from "[[Module:MascotInfobox]]": Revert to namespace protections Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end return retval end return p a765ed2f359127e25b0baa33db64c34ebd521c48 10 529 3459 1734 2025-08-09T23:22:06Z Atmois 13 Removed protection from "[[Template:SoftwareInfobox/doc]]": Revert to namespace protections wikitext text/x-wiki #REDIRECT [[Module:SoftwareInfobox/doc]] 86ef231b2f98916b329c4dc0ed1341b2a9fcda99 10 526 3460 1733 2025-08-09T23:22:14Z Atmois 13 Removed protection from "[[Template:DistributionInfobox/doc]]": Revert to namespace protections wikitext text/x-wiki #REDIRECT [[Module:DistributionInfobox/doc]] 77558eaa1d5751a016993d5e5c76f98d5ec9a18b 828 528 3461 1934 2025-08-09T23:22:23Z Atmois 13 Removed protection from "[[Module:SoftwareInfobox/doc]]": Revert to namespace protections wikitext text/x-wiki == Usage == In order to embed a infobox for software, you can put this at the very top of your article <pre> {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.99.0, 2024-10-23 | firstrelease = 1.0.1, 2022-08-01 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} </pre> 38e7017ba79462008a68c617f4267fa0b4860f5c 828 204 3462 1997 2025-08-09T23:22:31Z Atmois 13 Removed protection from "[[Module:SoftwareInfobox]]": Revert to namespace protections Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage(args.image, args.caption) end retval:addRow('Release Status', args.releasestatus) retval:addRow('Last Release', args.lastrelease) if args.firstrelease and args.firstrelease ~= '' then retval:addRow('First Release', args.firstrelease) end retval:addRow('Language(s)', args.languages) retval:addRow('Developer(s)', args.developers) retval:addRow('Website', args.website) return retval end return p 9e0ad367eaa8075d94e3e41d3f02fb7e7913a339 10 205 3463 2092 2025-08-09T23:22:39Z Atmois 13 Removed protection from "[[Template:SoftwareInfobox]]": Revert to namespace protections wikitext text/x-wiki <includeonly>{{#invoke:SoftwareInfobox|main}}</includeonly> <noinclude>{{/doc}}</noinclude> d849369e71311b7efdd1adbff1de016be089e1df 6 836 3467 2025-08-09T23:59:14Z Bont 128 wikitext text/x-wiki logo for fastfetch 1e0e767b11eff75a4d6301ef26f93b9e502331fe 6 837 3468 2025-08-10T00:09:29Z Bont 128 wikitext text/x-wiki a 86f7e437faa5a7fce15d1ddcb9eaeaea377667b8 14 397 3469 2629 2025-08-10T00:20:09Z Bont 128 update software page to match mascot style wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == ==== Text Editors ==== {| class="wikitable" !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} ==== System Utilities ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} ==== Ease of Use applications ==== {| !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} ==== Entertainment ==== {| !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} ==== Programming ==== {| !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} dfb2e4b3591f995af421a1e3dc49f3d31018ab93 3470 3469 2025-08-10T00:20:53Z Bont 128 fix last tables wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == ==== Text Editors ==== {| class="wikitable" !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} ==== System Utilities ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} ==== Ease of Use applications ==== {| class="wikitable" !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} ==== Entertainment ==== {| !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} ==== Programming ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} a20b28052b1c8c19f88e9e248c834e0b032218e6 3471 3470 2025-08-10T00:21:10Z Bont 128 fix entertainment wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == ==== Text Editors ==== {| class="wikitable" !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} ==== System Utilities ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} ==== Ease of Use applications ==== {| class="wikitable" !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} ==== Entertainment ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} ==== Programming ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} 570bad7f725daf9bba93864e6eb49fdb5b915e0e 0 769 3472 3423 2025-08-10T00:34:26Z Angelwood 239 add LabWC wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''[[Niri]]''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |Cosmic-comp<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |Cosmic |Rust |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |labwc<ref>https://labwc.github.io/</ref> |None |C |A Stacking/Floating Wayland compositor inspired by Openbox. |} ==References== <references /> 721468e22067daa28979d4345c97d93705c51d8e 3482 3472 2025-08-10T04:10:56Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''[[Niri]]''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |Cosmic-comp<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |Cosmic |Rust |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |labwc<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |C |A Stacking/Floating Wayland compositor inspired by Openbox. |} ==References== <references /> 6b5097ce912af91c798c599e3095d3cae665e9fa 0 827 3473 3436 2025-08-10T00:36:14Z Angelwood 239 Remove duplicated list of wayland compostors, link to its dedicated page wikitext text/x-wiki '''Wayland''' is a communication protocol that specifies the communication between a display server and its clients, as well as a [[C (programming language)|C]] library implementation of that protocol. A display server using the Wayland protocol is called a ''[[Wayland#Wayland compositors|Wayland compositor]]'', because it additionally performs the task of a compositing window manager. Wayland is developed by a group of volunteers initially led by Kristian Høgsberg as a free and open-source community-driven project with the aim of replacing the X Window System with a secure and simpler windowing system for [[Linux]] and other [[Unix]]-like operating systems. The project's source code is published under the terms of the [[MIT License]], a permissive free software license. The Wayland project also develops an implementation of a Wayland compositor called ''[[Wayland#Weston|Weston]]''. == Overview == [[File:Wayland_display_server_protocol.svg|right|thumb]] The Wayland Display Server project was started by [[Red Hat]] developer Kristian Høgsberg in 2008. Beginning around 2010, Linux desktop graphics have moved from having "a pile of rendering interfaces... all talking to the X server, which is at the center of the universe" towards putting the Linux kernel and its components (i.e. Direct Rendering Infrastructure (DRI), Direct Rendering Manager (DRM)) "in the middle", with "window systems like X and Wayland ... off in the corner". This will be "a much-simplified graphics system offering more flexibility and better performance". Høgsberg could have added an [[Xdmx|extension to X]] as many recent projects have done, but preferred to "[push] X out of the hotpath between clients and the hardware" for reasons explained in the project's FAQ. Wayland consists of a protocol and a reference implementation named [[Wayland#Weston|Weston]]. The project is also developing versions of [[GTK]] and [[Qt (software)|Qt]] that render to Wayland instead of to X. Most applications are expected to gain support for Wayland through one of these libraries without modification to the application. Initial versions of Wayland have not provided network transparency, though Høgsberg noted in 2010 that network transparency is possible. It was attempted as a Google Summer of Code project in 2011, but was not successful. Adam Jackson has envisioned providing remote access to a Wayland application by either "pixel-scraping" (like [[Virtual Network Computing|VNC]]) or getting it to send a "rendering command stream" across the network (as in [[Remote Desktop Protocol|RDP]], [[SPICE (protocol)|SPICE]] or [[X Window System|X11]]). As of early 2013, Høgsberg was experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor. In August 2017, GNOME saw the first such pixel-scraping VNC server implementation under Wayland. In modern Wayland compositors, network transparency is handled in an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] that implements the RemoteDesktop portal. Many Wayland compositors also include an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] for common tasks such as a native file picker for native applications and sandboxes such as [[Flatpak]] ([https://github.com/flatpak/xdg-desktop-portal-gtk xdg-desktop-portal-gtk] is commonly used as a fallback filepicker), screen recording, network transparency, screenshots, color picking, and other tasks that could be seen as needing user intervention and being security risks otherwise. Note that xdg-desktop-portal is not Flatpak or Wayland-specific, and can be used with alternative packaging systems and windowing systems. == Wayland compositors == [[File:Window_(windowing_system).svg|right|thumb|Typical elements of a [[Window (computing)|window]]. The Wayland protocol does not specify what software is responsible for rendering the [[window decoration]].{{r|Graesslin 2013 decorations}}]] [[File:KDE_Plasma_5.24_on_Arch_Linux_screenshot.png|thumb|Plasma 5.24.0 (February 2022) on Wayland ({{code|kwin_wayland}} compositor) under [[Arch Linux]]]] [[Display server|Display servers]] that implement the Wayland display server protocol are also called ''Wayland compositors'' because they additionally perform the task of a [[compositing window manager]]. A library called '''wlroots''' is a modular Wayland implementation that functions as a base for several compositors A list of compositors can be found [[Wayland Compositors|here]]. === Weston === [[Weston (software)|Weston]] is a Wayland compositor previously developed as the [[reference implementation]] of the protocol by the Wayland project. It is written in [[C (programming language)|C]] and released under the [[MIT License]]. Weston officially supports only [[Linux]] due to dependencies on kernel-specific features such as kernel mode-setting (KMS), the Graphics Execution Manager (GEM), and [[udev]]. On Linux, it handles input via [[evdev]] and buffer management via Generic Buffer Management (GBM). A prototype port for [[FreeBSD]] was announced in 2013. The compositor supports High-bandwidth Digital Content Protection (HDCP) and uses GEM to share buffers between applications and the compositor. It features a plug-in architecture with "shells" that provide elements like docks and panels. Applications are responsible for rendering their own window decorations. Weston supports rendering via [[OpenGL ES]] or the [[pixman]] library for software rendering. The full OpenGL stack is avoided to prevent pulling in [[GLX]] and other [[X Window System]] dependencies. A remote desktop interface for Weston was proposed in 2013 by a developer from [[RealVNC]]. ==== Maynard ==== [[File:Maynard_desktop.png|thumb|Maynard (in January 2017)]] '''''Maynard''''' is a [[graphical shell]] and has been written as a plug-in for Weston, just as the [[GNOME Shell]] has been written as a plug-in to [[Mutter (software)|Mutter]]. The [[Raspberry Pi Holdings|Raspberry Pi]] in collaboration with [[Collabora]] released Maynard. === libinput === [[File:Libinput_for_Wayland_compositors.svg|thumb|libinput was created to consolidate the input stack across multiple Wayland compositors.]] The Weston code for handling input devices (keyboards, pointers, touch screens, etc.) was split into its own separate library, called ''libinput'', for which support was first merged in Weston 1.5. Libinput handles input devices for multiple Wayland compositors and also provides a generic [[X.Org Server]] input driver. It aims to provide one implementation for multiple Wayland compositors with a common way to handle input events while minimizing the amount of custom input code compositors need to include. libinput provides device detection (via [[udev]]), device handling, input device event processing and abstraction. Version 1.0 of libinput followed version 0.21, and included support for tablets, button sets and touchpad gestures. This version will maintain stable API/ABI. As GNOME/GTK and [[KDE Frameworks 5]] have mainlined the required changes, Fedora 22 will replace X.Org's evdev and Synaptics drivers with libinput. With version 1.16, the [[X.Org Server]] obtained support for the libinput library in form of a wrapper called [[Mono]]. === Wayland Security Module === Wayland Security Module is a proposition that resembles the [[Linux Security Module]] interface found in the [[Linux kernel]]. Some applications (especially the ones related to [[accessibility]]) require privileged capabilities that should work across different Wayland compositors. Currently, applications under Wayland are generally unable to perform any sensitive tasks such as taking screenshots or injecting input events without going through [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] or obtaining privileged access to the system. Wayland Security Module is a way to delegate security decisions within the compositor to a centralized security decision engine. == Adoption == The Wayland protocol is designed to be simple so that additional protocols and interfaces need to be defined and implemented to achieve a holistic windowing system. While many graphical toolkits already fully support Wayland, the developers of the [[Graphical shell|graphical shells]] are cooperating with the Wayland developers to create the necessary additional interfaces. === Desktop Linux distributions === Most major Linux distributions default to using Wayland. Some notable examples are: * [[Debian]] ships Wayland as the default session for GNOME since version [[Debian 10|10 (Buster)]], released 6 July 2019. * [[Fedora Linux|Fedora]] starting with version 25 (released 22 November 2016) uses Wayland for the default GNOME 3.22 desktop session, with [[X.Org Server|X.Org]] as a fallback if the graphics driver cannot support Wayland. Fedora uses Wayland as the default for KDE desktop session starting with version 34 (released 27 April 2021) * [[Manjaro]] ships Wayland as default in the Gnome edition of Manjaro 20.2 (Nibia) (released 22 November 2020). * [[Raspberry Pi OS]], a port of Debian, has offered the option to use Wayland since version [[Debian 11|11 (Bullseye)]], which was released on 3 December 2021. Wayland became the default in version [[Debian 12|12 (Bookworm)]], released on 10 October 2023. * [[Red Hat Enterprise Linux]] ships Wayland as the default session in version 8, released 7 May 2019. * [[Ubuntu (operating system)|Ubuntu]] shipped with Wayland by default in Ubuntu 17.10 (Artful Aardvark). However, Ubuntu 18.04 LTS reverted to X.Org by default due to several issues. Since Ubuntu 21.04, Wayland is the default again. * [[Slackware Linux]] included Wayland on 20 February 2020 for the development version, -current, which became version 15.0 in 2022. However, Wayland is still not the default. == History == Kristian Høgsberg, a [[Linux]] graphics and [[X.Org Server|X.Org]] developer who previously worked on [[AIGLX]] and [[Direct Rendering Infrastructure|DRI2]], started Wayland as a spare-time project in 2008 while working for [[Red Hat]]. His stated goal was a system in which "every frame is perfect, by which I mean that applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker." Høgsberg was driving through the town of Wayland, Massachusetts when the underlying concepts "crystallized", hence the name (Weston and Maynard are also nearby towns in the same area, continuing the reference). In October 2010, Wayland became a [[freedesktop.org]] project. As part of the migration, the prior Google Group was replaced by the ''wayland-devel'' mailing list as the project's central point of discussion and development. The Wayland client and server libraries were initially released under the [[MIT License]], while the reference compositor Weston and some example clients used the [[GNU General Public License version 2]]. Later, all the GPL code was relicensed under the MIT license "to make it easier to move code between the reference implementation and the actual libraries". In 2015 it was discovered that the license text used by Wayland was a slightly different and older version of the MIT license, and the license text was updated to the current version used by the [[X.Org Server|X.Org project]] (known as [[Expat License|MIT Expat License]]). {| class="wikitable sortable collapsible text-align:center" |} f5b508934e447a96af2b6897ec9a5208d47a905a 0 309 3474 3270 2025-08-10T00:53:29Z Cherry 131 corrected the logo to the logo being described wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png.png|thumb]] |thumb]] | caption = Sudo used on [[whoami]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.17p2 | languages = [[C]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} [[File:Sudo_logo_(2019).png|thumb|335x335px|Sudo's logo of a sandwich]] [[File:Sudo Insults.png|thumb|335x335px|Output from sudo when <code>Defaults insults</code> is added]] The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]).<ref name=":0">[https://man7.org/linux/man-pages/man8/sudo.8.html sudo(8)], Linux Manpages</ref> Its name is shorthand for "su 'do'"<ref>[https://www.sudo.ws/ sudo.ws], Sudo Developers</ref>, however as <code>su</code> stands for "substitute user"<ref>[https://man7.org/linux/man-pages/man1/su.1.html su(1)], Linux Manpages</ref> this would stand for "substitute user, do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file<ref name=":0" /> to specify which users or groups can execute specific commands. == Usage == {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |Run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser''<ref name=":0" /> == Trivia == * Sudo's logo is a sandwich in reference to [https://xkcd.com/149/ xkcd 149]<ref>[https://www.sudo.ws/about/logo/ sudo.ws/about/logo], Sudo Developers</ref> * If you add the line <code>Defaults insults</code> to the Defaults section of <code>/etc/sudoers</code>, you will be insulted whenever you type the wrong password.<ref>[https://www.geeksforgeeks.org/when-sudo-insults-you/ When sudo insults you!!], GeeksforGeeks, September 13, 2023 (February 12, 2025)</ref> == References == [[Category:Software]] be3c23073330b90fd403afcbc065766bf0c65bdf 0 623 3475 3384 2025-08-10T01:08:47Z Cherry 131 Fixed some typos and added more links wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=EndeavourOS|image=[[File:EndeavourOS Logo.svg|Thumb]]|caption=The Endeavour OS logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=[[Cinnamon]], [[I3]], [[GNOME]], [[KDE Plasma]], [[LXDE]], [[LXQt]], [[MATE]], [[Xfce]], [[Budgie]]|usagetype=Desktop|architectures=x86_64, AArch64|website=[https://endeavouros.com endeavouros.org]}}'''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">[https://endeavouros.com/ Home - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>[https://endeavouros.com/about-us/ About us - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning [[Arch Linux]] fundamentals. === Installation === EndeavourOS provides an ISO with the [[Calamares]] installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with [[Arch Linux]], meaning it uses Arch's official repositories directly and adheres closely to Arch's philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * [[AUR]] Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate [[AUR]] package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * Pacman Compatibility: Fully compatible with Arch's pacman package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for Arch Linux are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla Arch, or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the AUR, as well as EndeavourOS-specific themes and utilities.<ref>[https://repo.c48.uk/endeavouros/repo/endeavouros/ Index of /endeavouros/repo/endeavouros/] (Accessed: 2025-08-09)</ref> This is simply a pacman repository that can simply be added to any Arch Linux system if desired. == References == 5a1ae45b155387a0c5bd3b5706e83f6edb906dd7 3476 3475 2025-08-10T01:10:26Z Cherry 131 missed some things that needed to be linked wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox|title=EndeavourOS|image=[[File:EndeavourOS Logo.svg|Thumb]]|caption=The Endeavour OS logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=[[Cinnamon]], [[I3]], [[GNOME]], [[KDE Plasma]], [[LXDE]], [[LXQt]], [[MATE]], [[Xfce]], [[Budgie]]|usagetype=Desktop|architectures=x86_64, AArch64|website=[https://endeavouros.com endeavouros.org]}}'''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">[https://endeavouros.com/ Home - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>[https://endeavouros.com/about-us/ About us - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning [[Arch Linux]] fundamentals. === Installation === EndeavourOS provides an ISO with the [[Calamares]] installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with [[Arch Linux]], meaning it uses Arch's official repositories directly and adheres closely to Arch's philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * [[AUR]] Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate [[AUR]] package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * [[Pacman]] Compatibility: Fully compatible with Arch's [[pacman]] package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for [[Arch Linux]] are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla [[Arch]], or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the [[AUR]], as well as EndeavourOS-specific themes and utilities.<ref>[https://repo.c48.uk/endeavouros/repo/endeavouros/ Index of /endeavouros/repo/endeavouros/] (Accessed: 2025-08-09)</ref> This is simply a [[pacman]] repository that can simply be added to any [[Arch Linux]] system if desired. == References == 7a86dc164a95ebc341602eacea6e7ddfb0405e55 0 223 3477 3321 2025-08-10T02:07:14Z Texandoomguy 240 Added a citation. Kinda hard to find good sources. wikitext text/x-wiki {{Needs Citations}}{{Stub}}Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (e.g. FSF approved distribution) * Ecosystem or Tooling (e.g. libc, [[Package Manager|package manager]], coreutils, [[Init System|init system]]) * Experimentation * Customization ... and many more. <ref name=":0">{{Cite|url=https://read.amazon.com/sample/B09781GYC5?clientId=share|title=Distro-Hopping, What, Why & How Explained! Ch 2.1|author=Steven Ovadia|year=2016|accessdate=November 17}}</ref> This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (e.g. Debianisms, package managers, init systems) * Opinionated design philosophies (e.g. Nix, Guix, Fedora Atomic) * Additional configuration needs (e.g. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. <ref name=":0" /> Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. {{Citation needed}} '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (e.g. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (e.g. Liberapay, GitHub sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] 1f53f7f11eb774713e33d9e8264d5c9f69769677 3478 3477 2025-08-10T02:08:16Z Texandoomguy 240 wrong date wikitext text/x-wiki {{Needs Citations}}{{Stub}}Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (e.g. FSF approved distribution) * Ecosystem or Tooling (e.g. libc, [[Package Manager|package manager]], coreutils, [[Init System|init system]]) * Experimentation * Customization ... and many more. <ref name=":0">{{Cite|url=https://read.amazon.com/sample/B09781GYC5?clientId=share|title=Distro-Hopping, What, Why & How Explained! Ch 2.1|author=Steven Ovadia|year=2016|accessdate=August 9}}</ref> This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (e.g. Debianisms, package managers, init systems) * Opinionated design philosophies (e.g. Nix, Guix, Fedora Atomic) * Additional configuration needs (e.g. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. <ref name=":0" /> Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. {{Citation needed}} '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (e.g. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (e.g. Liberapay, GitHub sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. [[Category:Terminology]] a0db6fd56c39b519d7822166a98884676f069fed 2 838 3479 2025-08-10T02:16:55Z Texandoomguy 240 Created page with "== The Texan DoomGuy == I'm Bill. I use NixOS. I've been interested in Linux since I was 11, which does not help me beat the autistic nerd allegations, of which are true. === Socials: === @TexanDoomGuy on really everything. Maybe @Texan_DoomGuy. Email: TexanDoomGuy@TexanDoomGuy.com Website: TexanDoomGuy.com" wikitext text/x-wiki == The Texan DoomGuy == I'm Bill. I use NixOS. I've been interested in Linux since I was 11, which does not help me beat the autistic nerd allegations, of which are true. === Socials: === @TexanDoomGuy on really everything. Maybe @Texan_DoomGuy. Email: TexanDoomGuy@TexanDoomGuy.com Website: TexanDoomGuy.com e0146eb7b3484c9e01ed7a8b09af4fb5918c1485 0 575 3480 3388 2025-08-10T04:09:08Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <sup>🍣DEAD?]</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys|} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == [[Category:Software]] 7b6cf8ef2274653742f7dc8f5496a1597733e64f 3000 577 3483 3012 2025-08-10T04:13:19Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. == References == e17cdde1a66a951989d7657c3242d3c3a8c454d8 3000 639 3484 3013 2025-08-10T04:13:29Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki {{Guide Warning}} == Formatting a partition to ext4 == Assuming the partition you want to format is called /dev/sdX, do: <pre> mkfs -t ext4 /dev/sdX # or mkfs.ext4 /dev/sdX </pre> The e2fsprogs package must be installed. == Setting mount options == You can set mount options for ext4 either by modifying <code>/etc/fstab</code> or <code>tune2fs</code><ref>[https://linux.die.net/man/8/tune2fs <span style="color:#fc493b">https://linux.die.net/man/8/tune2fs <sup>🍣403]</ref> For example, to enable <code>noatime</code> on your filesystem, do: <pre> tune2fs -o noatime /dev/sdX </pre> == Using an external journal == Ext4 allows you to use an external journaling device paired with a partition that actually stores your data. To create a **new** partition with an external journal at /dev/sdb2, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> To convert a pre-existing filesystem, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> == Feature flags == Ext4 has tons of feature flags that can be enabled using the <code>tune2fs</code> utility, a list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. To enable a feature flag, do: <pre> tune2fs -O flag /dev/sdX </pre> Some common feature flags used often are <code>encrypt</code> and <code>fast_commit</code>. == References == <references /> 3eef77f28d8f48fbd6065d3ecdc8117c7af2fc93 3000 684 3485 3015 2025-08-10T04:14:37Z Hamachitan 222 /* References */ 🍣 Tidy up format, see [[ATL:Guidelines#Citations]] wikitext text/x-wiki This section will change overtime, as such, you should probably follow the [https://wiki.hyprland.org/Getting-Started/Installation/ official installation guide] instead. To install Hyprland, it is recommended to use a rolling release or a semi-rolling release [[Linux Distributions|distributions]]. Most recommended ones include [[Arch Linux]], [[Gentoo]], [[NixOS]], [[Fedora]] and [[openSUSE]] (Tumbleweed) due to them having the most recent packages as Hyprland is a bleeding edge window manager. You must also install kitty if you do not have an existing configuration or existing dotfiles you want to try. ==== Arch Linux ==== By far the easiest one to install Hyprland on, you just run this command: <code>sudo pacman -S hyprland --needed</code> The <code>--needed</code> flag is to make sure that you do not reinstall Hyprland. ==== NixOS ==== Just enable Hyprland in your NixOS configuration by adding: <code>programs'''.'''hyprland'''.'''enable = '''true''';</code> ==== openSUSE (Tumbleweed) ==== It is quite simple here also, you can just simply run: <code>sudo zypper install hyprland</code> Alternatively, you can install it via YaST2 Software, you can also try manual building if you are not on Tumbleweed. It is not recommended to use Hyprland on other versions than Tumbleweed. ==== Fedora ==== You must have the latest version of Fedora installed, if so run the following: <code>sudo dnf install hyprland</code> You can also install the <code>hyprland-devel</code> package to build plugins. ==== Gentoo ==== You can edit some USE flags like: * <code>X</code> : To add support for [[X11]]. * <code>legacy-renderer</code> : to enable the Legacy renderer. * <code>systemd</code> : Enable use of specific [[systemd]] libraries like socket activation or session tracking. But, it is not necessary to edit any of these USE flags and should be able to manually build using: <code>emerge --ask gui-wm/hyprland # please run as root</code> ==== Ubuntu 23.04 ==== WARNING: Not recommended by the Hyprland developers as it is potentially unsafe for other packages on a system. This can lead to system breakages so we are not including it in this article but you can read [https://gist.github.com/Vertecedoc4545/3b077301299c20c5b9b4db00f4ca6000 this article]. Please do note that this is long and tedious and may require you to manually build extremely lengthy packages and/or dependency hell since most dependencies on the [[Ubuntu]] [[Repository|repositories]] can be outdated. ==== Slackware ==== For [[Slackware]], you might need to use the SlackBuilds repository which has the <code>hyprland-bin</code> package. ==== Void Linux ==== Hyprland is not available for [[Void Linux]] from the official repositories [https://github.com/void-linux/void-packages/issues/37544 as Hyprland doesn’t build against tagged wlroots], however template files are available [https://github.com/Makrennel/hyprland-void from a third party] which can build Hyprland using [https://github.com/void-linux/void-packages xbps-src]. The [https://github.com/Makrennel/hyprland-void/blob/master/README.md README] has a pretty good explanation on how to install and use it. For a manual releases install<ref>[https://wiki.hyprland.org/Getting-Started/Installation/#manual-releases-linux-only Installation], Hyprland Wiki, 2025-08-09 (Accessed: 2025-08-10)</ref> and for a manual build install<ref>[https://wiki.hyprland.org/Getting-Started/Installation/#manual-manual-build Installation], Hyprland Wiki, 2025-08-09 (Accessed: 2025-08-10)</ref> you can check the Hyprland wiki. === Configuration === This is a pretty verbose topic but is very simple for new users. Hyprland configuration files are generally suffixed with a <code>.conf</code> extension and are quite simple to read because almost everything is a variable. The Hyprland Wiki has a step above<ref>[https://wiki.hyprland.org/Configuring/Configuring-Hyprland/ <span style="color:#fc493b">https://wiki.hyprland.org/Configuring/Configuring-Hyprland/ <sup>🍣404]</ref> but this guide will teach you pretty much everything you need to know. Your configuration file is located at <code>~/.config/hypr/hyprland.conf</code> and can contain configurations of programs that are under the hypr-ecosystem. This topic is divided into 6 sub-sections: * Variables * Section-specific variables * Binding Keys * Binding Special Keys * Animations * Monitors ==== Variables ==== This is the most important part of your configuration file because it is most of your whole configuration file, the entire hyprland.conf is comprised of a syntax like: <code>variable = arg1, arg2, arg3, arg4</code> Each line is required to have 3 commas, however not 4 arguments, for example you can do: <code>monitor =,preferred,auto,1 # this is actually part of your auto-generated configuration file</code> There are some exceptional cases where all 3 commas are not necessary like the <code>exec-once</code> command but most of the time it does require 3 commas. == References == 2ba659a4baf0f5fe3c0ca8a124cedfd690f55358 0 839 3486 2025-08-10T04:26:16Z Madonuko 140 #REDIRECT [[AWK]] wikitext text/x-wiki #REDIRECT [[AWK]] 85dff44fcea9f4ccb45a423877aed39b875313c9 6 840 3487 2025-08-10T06:39:00Z Madonuko 140 https://github.com/Ultramarine-Linux/logos/blob/lapis/icons/hicolor/scalable/apps/fedora-logo-icon.svg wikitext text/x-wiki == Summary == https://github.com/Ultramarine-Linux/logos/blob/lapis/icons/hicolor/scalable/apps/fedora-logo-icon.svg 9f421f70fcee5846f0b11f837e8a5c55b3471d2c 0 841 3488 2025-08-10T07:01:39Z Madonuko 140 init wikitext text/x-wiki [[category:Linux Distributions]] {{DistributionInfobox | title = Ultramarine Linux | image = [[File:Ultramarine_Logo_Icon.svg|Ultramarine Logo|frameless]] | caption = Ultramarine Linux Logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[dnf]], [[rpm]] | defaultdesktops = [[Budgie]], [[GNOME]], [[Plasma]], [[XFCE]] | usagetype = Desktop | architectures = aarch64, x86_64 | website = https://ultramarine-linux.org | Current version = um42 }} '''Ultramarine Linux''' is a [[Fedora]]-based Linux distribution for any people with different technical backgrounds, by providing sane defaults and tweaks out of the box.<ref>[https://ultramarine-linxu.org Ultramarine Linux], Ultramarine Project, 2025 (Accessed: 2025-08-10)</ref> Started by Cappy Ishihara in 2021, the team ''Ultramarine Project'' later had a merger, and the [[distro]] is now a major successful product of [[Fyra Labs]].<ref>[https://wiki.fyralabs.com/Ultramarine_Linux Ultramarine Linux], Fyra Labs Wiki, 2023-10-01 (Accessed: 2025-08-10)</ref> Unlike Fedora, the Ultramarine team prioritises on being more ''pragmatical'' over being more ideological<ref>[https://wiki.ultramarine-linux.org/en/welcome/ Welcome], Ultramarine Wiki, 2025 (Accessed: 2025-08-10)</ref>, by for example installing non-free drivers and codecs automatically<ref>[https://www.zdnet.com/article/ultramarine-linux-40-continues-to-be-one-fine-unofficial-fedora-spin/ Ultramarine Linux 40 continues to be one fine unofficial Fedora Spin], Jack Wallen, 2024-12-23 (Accessed: 2025-08-10)</ref>, improving overall user experience. == History == Created in 2021, Ultramarine Linux was the spiritual successor to [[Korora Linux]], following the goal of creating a system that “just works”. It was created due to “frustration with the legal limits of Fedora”<ref>[https://github.com/Ultramarine-Linux/wiki/blob/ba740779d7fe037429c88adbe238039ea3c69991/src/content/docs/en/welcome.md wiki/src/content/docs/en/welcome.md at ba740779d7fe037429c88adbe238039ea3c69991 · Ultramarine-Linux/wiki], Ultramarine Linux, 2023 (Accessed: 2025-08-10)</ref>, and was shipped as a base-Fedora image with tweaks, codecs and drivers on top. The first release Ultramarine 35 (UM35) came with 4 editions: Budgie, [[Cutefish]], [[Pantheon]] and [[GNOME]]. Budgie was made as the ''flagship'' edition, because it was a rather popular [[DE]] that was not yet available on Fedora 35. 8d8fcd7f7ff1f861249546bb744eb283977dac7a 3492 3488 2025-08-10T09:09:18Z Madonuko 140 more wikitext text/x-wiki [[category:Linux Distributions]] {{DistributionInfobox | title = Ultramarine Linux | image = [[File:Ultramarine_Logo_Icon.svg|Ultramarine Logo|frameless]] | caption = Ultramarine Linux Logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[dnf]], [[rpm]] | defaultdesktops = [[Budgie]], [[GNOME]], [[Plasma]], [[XFCE]] | usagetype = Desktop | architectures = aarch64, x86_64 | website = https://ultramarine-linux.org | Current version = um42 }} '''Ultramarine Linux''' is a [[Fedora]]-based Linux distribution for any people with different technical backgrounds, by providing sane defaults and tweaks out of the box.<ref>[https://ultramarine-linxu.org Ultramarine Linux], Ultramarine Project, 2025 (Accessed: 2025-08-10)</ref> Started by Cappy Ishihara in 2021, the team ''Ultramarine Project'' later had a merger, and the [[distro]] is now a major successful product of [[Fyra Labs]].<ref>[https://wiki.fyralabs.com/Ultramarine_Linux Ultramarine Linux], Fyra Labs Wiki, 2023-10-01 (Accessed: 2025-08-10)</ref> Unlike Fedora, the Ultramarine team prioritises on being more ''pragmatical'' over being more ideological<ref name=":0">[https://wiki.ultramarine-linux.org/en/welcome/ Welcome], Ultramarine Wiki, 2025 (Accessed: 2025-08-10)</ref>, by for example installing non-free drivers and codecs automatically<ref>[https://www.zdnet.com/article/ultramarine-linux-40-continues-to-be-one-fine-unofficial-fedora-spin/ Ultramarine Linux 40 continues to be one fine unofficial Fedora Spin], Jack Wallen, 2024-12-23 (Accessed: 2025-08-10)</ref>, improving overall user experience. == History == Created in 2021, Ultramarine Linux was the spiritual successor to [[Korora Linux]], following the goal of creating a system that “just works”. It was created due to “frustration with the legal limits of Fedora”<ref>[https://github.com/Ultramarine-Linux/wiki/blob/ba740779d7fe037429c88adbe238039ea3c69991/src/content/docs/en/welcome.md wiki/src/content/docs/en/welcome.md at ba740779d7fe037429c88adbe238039ea3c69991 · Ultramarine-Linux/wiki], Ultramarine Linux, 2023 (Accessed: 2025-08-10)</ref>, and was shipped as a base-Fedora image with tweaks, codecs and drivers on top. The first release Ultramarine 35 (UM35) came with 4 editions: Budgie, [[Cutefish]], [[Pantheon]] and [[GNOME]]. Budgie was made as the ''flagship'' edition, because it was a rather popular [[DE]] that was not yet available on Fedora 35.<ref>[https://news.itsfoss.com/fedora-budgie-sway-official/ Official Fedora Budgie & Sway Spins to Arrive With Fedora 38 Release], Sourav Rudra, 2023-01-04 (Accessed: 2025-08-10)</ref> The merger with Fyra Labs later brought packaging toolchains like Andaman and Subatomic to life, which replaced Ultramarine's own packaging tool [http://github.com/Ultramarine-Linux/umpkg umpkg], and was followed by the creation of [[Terra]], which was intended to be a common software [[repository]] shared between Ultramarine and its sister project [[tauOS]]. Cutefish and Pantheon editions were removed in later editions due to lack of upstream maintenance, and were replaced by KDE Plasma and XFCE respectively.<ref name=":0"/> == Repositories == Apart from the Fedora stable and update repositories, Ultramarine also comes with all free and non-free [[RPM Fusion]] repositories, and Terra with extra streams enabled. Ultramarine Linux also comes with [[Flathub]] instead of [[Fedora Flatpaks]], making the experience free of hassles.<ref name=":0"/> == Ultramarine Anywhere == Originally named as ''Ultramarine Everywhere'', ''Ultramarine Anywhere'' is an initiative started from Ultramarine 38 that provides better hardware support for other platforms.<ref>[https://wiki.ultramarine-linux.org/en/anywhere/anywhere/ Ultramarine Anywhere], Ultramarine Wiki, 2025 (Accessed: 2025-08-10)</ref> Currently Ultramarine Linux has first-class support for various different kinds of [[Chromebook]], [[Raspberry Pi]], and [[Microsoft Surface]] models. Ultramarine also initiated earlier [[WSL]] support than Fedora and its derivatives. == References == 7447dd4f8a41aaaf066594a112c1d1d0601cf439 4 646 3489 2928 2025-08-10T08:21:32Z Atmois 13 Add minimum edit count wikitext text/x-wiki == '''<u>DO NOT share the link provided with anyone, including any staff members.</u>''' == To link your Discord and '''atl.wiki''' accounts in our [https://discord.gg/linux discord server], type <code>/verify</code> using '''''@atl.wiki'''''. You will receive a private link in your DM's, Then click the link, press '''Allow''', and return to Discord, if your '''atl.wiki''' account is at least '''3 days old''', and has met the '''minimum edit threshold of 15 edits''', you will automatically be given the '''''@Wiki Author''''' role, which comes with bonus perks in the Discord server such as boosted XP, extra permissions and exclusive chat access. You may need to wait up to an hour for the role to be given. If you do not receive it open a ticket with <code>/ticket</code> and ask for help. If you have met the requirements '''after''' initially verifying, run <code>/unverify</code> then go through the verification process again, this will refresh your role. To see if you meet the requirements, visit the [[Special:UserRights]] page, search your username, and see if you're an ''implicit member of "Autoconfirmed Users"''. This role is automatically given by the wiki to users who meet the criteria. 2e6f4106c409fc5142fc46a2171493abd60e9cb5 0 177 3490 2952 2025-08-10T08:33:28Z Soccera 243 Add synonym for proprietary wikitext text/x-wiki '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word, libre)<ref>https://en.wiktionary.org/wiki/libre Wikitionary. Wikimedia Foundation. Accessed June 4, 2024.</ref> and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary, or nonfree software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == [[Category:Terminology]] eb6c9488f646fe652d1567cd2b114b803e55c3ec 0 842 3491 2025-08-10T09:02:15Z Soccera 243 Create opendoas page wikitext text/x-wiki The command line tool <code>doas</code> is used to run commands as another user. The configuration file is located at <code>/etc/doas.conf</code>. == Usage == {| class="wikitable" |+Common opendoas Commands !Command !Description |- |<code>doas <command></code> |Run the given command as root |- |<code>doas -s</code> |Opens SHELL or the shell listed in /etc/passwd with root permissions |- |<code>doas -L</code> |Clear persisted authentication if present |- |<code>doas -C</code> |Check configuration file for errors. If run with another command, this will be performed. |- |<code>doas -n</code> |Runs in non-interactive mode. If <code>nopass</code> is not set for the given command, it will fail. |- |<code>doas -u <user></code> |Executes the shell as the given user |- |} 691136b1526209d9a437bd15312721f964315aa3 3493 3491 2025-08-10T09:11:40Z Madonuko 140 software category wikitext text/x-wiki [[Category:Software]] The command line tool <code>doas</code> is used to run commands as another user. The configuration file is located at <code>/etc/doas.conf</code>. == Usage == {| class="wikitable" |+Common opendoas Commands !Command !Description |- |<code>doas <command></code> |Run the given command as root |- |<code>doas -s</code> |Opens SHELL or the shell listed in /etc/passwd with root permissions |- |<code>doas -L</code> |Clear persisted authentication if present |- |<code>doas -C</code> |Check configuration file for errors. If run with another command, this will be performed. |- |<code>doas -n</code> |Runs in non-interactive mode. If <code>nopass</code> is not set for the given command, it will fail. |- |<code>doas -u <user></code> |Executes the shell as the given user |} 00876a939620e5982477acc13b6841390f743d41 0 441 3494 3042 2025-08-10T09:12:19Z Soccera 243 GNU actively campaigns against the use of "open source" https://www.gnu.org/philosophy/open-source-misses-the-point.html wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,")<ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU], The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> is a dedicated organization for free [[:Category:Software|software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone [[Operating System|operating system]] because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or [[Proprietary software|proprietary]]: A few are GNU/[[Linux]], [[MacOS]], [[UNIX|Unix-based]]/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the proprietary software of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe. </ref> == Included Software / Components == [[File:Gnu compiler collection-logo-1.png|alt=This logo depicts a Bull shaped animal jumping out of an egg, in black text that displays the letters G, C, C|left|thumb|224x224px|A logo of the GCC.]] As of June 2024, the GNU project currently holds 394 active [[packages]], but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. Overall, these components are in many operating systems, mainly because of how easy GCC is to access for any developer. Because of Richard Stallman, he was able to free the variety of tools and software developed for the GNU project and in turn, pushed forward for the movement of open and free software for all.<ref name=":0" /> == History of GNU == [[File:RichardStallman.jpg|alt=A Picture of Richard Matthew Stallman in 2024|thumb|341x341px|A Picture of Richard Matthew Stallman in 2024]] Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref name=":0">[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible [[architecture]] because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs.<ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> == References == <references /> 4261dfdeb788255084c61806f7e7f97655e1d8ce 14 397 3495 3471 2025-08-10T09:14:07Z Madonuko 140 /* System Utilities */ [[opendoas]] wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == ==== Text Editors ==== {| class="wikitable" !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} ==== System Utilities ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[opendoas|OpenDoas]] |Ted Unangst |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} ==== Ease of Use applications ==== {| class="wikitable" !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} ==== Entertainment ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} ==== Programming ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} cc6079b8d897d15cd4588e6812ebad853113d150 3532 3495 2025-08-10T21:04:43Z OgloTheNerd 248 Added a section for music-related software, fixed some grammar. wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == ==== Text Editors ==== {| class="wikitable" !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} ==== System Utilities ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[opendoas|OpenDoas]] |Ted Unangst |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} ==== Ease of Use Applications ==== {| class="wikitable" !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} ==== Entertainment ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} ==== Programming ==== {| class="wikitable" !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} ==== Open-Source Music Players ==== {| class="wikitable" !Application !Developer !Ecosystem (If Any) !UI Framework |- |[https://mierak.github.io/rmpc RMPC] |Mierak (And Others) |[https://www.musicpd.org/ MPD] |[https://crates.io/crates/ratatui Ratatui] ([[TUI]]) |- |[https://github.com/ncmpcpp/ncmpcpp NCMPCPP] |Andrzej Rybczak (And Others) |[https://www.musicpd.org/ MPD] |NCurses ([[TUI]]) |- |[https://musikcube.com/ Musikcube] |Casey Langen |Musikcube (Custom) |NCurses ([[TUI]]) |} d0e8dab010067dd026556475b34ec5dc474ee890 3535 3532 2025-08-10T21:38:18Z OgloTheNerd 248 Added table titles to the tables themselves. wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == {| class="wikitable" |+Text Editors !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} {| class="wikitable" |+System Utilities !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[opendoas|OpenDoas]] |Ted Unangst |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} {| class="wikitable" |+Installers !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} {| class="wikitable" |+Useless But Fun !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} {| class="wikitable" |+Programming !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} {| class="wikitable" |+Open-Source Music Players !Application !Developer !Ecosystem (If Any) !UI Framework |- |[https://mierak.github.io/rmpc RMPC] |Mierak (And Others) |[https://www.musicpd.org/ MPD] |[https://crates.io/crates/ratatui Ratatui] ([[TUI]]) |- |[https://github.com/ncmpcpp/ncmpcpp NCMPCPP] |Andrzej Rybczak (And Others) |[https://www.musicpd.org/ MPD] |NCurses ([[TUI]]) |- |[https://musikcube.com/ Musikcube] |Casey Langen |Musikcube (Custom) |NCurses ([[TUI]]) |} 1f2af97698a84d820619bdcf7d62ab95afccb91f 3536 3535 2025-08-10T21:52:01Z OgloTheNerd 248 Added shells. wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == {| class="wikitable" |+Text Editors !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} {| class="wikitable" |+System Utilities !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[opendoas|OpenDoas]] |Ted Unangst |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} {| class="wikitable" |+Installers !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} {| class="wikitable" |+Useless But Fun !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} {| class="wikitable" |+Programming !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} {| class="wikitable" |+Open-Source Music Players !Application !Developer !Ecosystem (If Any) !UI Framework |- |[https://mierak.github.io/rmpc RMPC] |Mierak (And Others) |[https://www.musicpd.org/ MPD] |[https://crates.io/crates/ratatui Ratatui] ([[TUI]]) |- |[https://github.com/ncmpcpp/ncmpcpp NCMPCPP] |Andrzej Rybczak (And Others) |[https://www.musicpd.org/ MPD] |NCurses ([[TUI]]) |- |[https://musikcube.com/ Musikcube] |Casey Langen |Musikcube (Custom) |NCurses ([[TUI]]) |} {| class="wikitable" |+Shells !Application !Developer |- |[https://www.gnu.org/software/bash/ Bash] |[[GNU]] |- |[https://fishshell.com/ Fish] |Axel Liljencrantz (And Others) |- |[https://www.zsh.org/ ZSH] |Peter Stephenson |} 0762d1cb866dbc287bb305b1d36cc081bdd169cc 0 842 3496 3493 2025-08-10T09:21:36Z Soccera 243 Add history section wikitext text/x-wiki [[Category:Software]] The command line tool <code>doas</code> is used to run commands as another user. The configuration file is located at <code>/etc/doas.conf</code>. == Usage == {| class="wikitable" |+Common opendoas Commands !Command !Description |- |<code>doas <command></code> |Run the given command as root |- |<code>doas -s</code> |Opens SHELL or the shell listed in /etc/passwd with root permissions |- |<code>doas -L</code> |Clear persisted authentication if present |- |<code>doas -C</code> |Check configuration file for errors. If run with another command, this will be performed. |- |<code>doas -n</code> |Runs in non-interactive mode. If <code>nopass</code> is not set for the given command, it will fail. |- |<code>doas -u <user></code> |Executes the shell as the given user |} == History == The <code>doas</code> command first appeared in OpenBSD 5.8. <code>doas</code> was forked into Opendoas in 2015 by Ted Unangst <tedu@openbsd.org>. 4b60059c1fee011c7822a1651a3f5b7d4704137f 0 841 3497 3492 2025-08-10T09:23:27Z Madonuko 140 improve infobox wikitext text/x-wiki [[category:Linux Distributions]] {{DistributionInfobox | title = Ultramarine Linux | image = [[File:Ultramarine_Logo_Icon.svg|Ultramarine Logo|frameless]] | caption = Ultramarine Linux Logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[dnf|dnf5]], [[rpm]], [[flatpak]] | defaultdesktops = [[Budgie]], [[GNOME]], [[Plasma]], [[XFCE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = https://ultramarine-linux.org | Current version = um42 }} '''Ultramarine Linux''' is a [[Fedora]]-based Linux distribution for any people with different technical backgrounds, by providing sane defaults and tweaks out of the box.<ref>[https://ultramarine-linxu.org Ultramarine Linux], Ultramarine Project, 2025 (Accessed: 2025-08-10)</ref> Started by Cappy Ishihara in 2021, the team ''Ultramarine Project'' later had a merger, and the [[distro]] is now a major successful product of [[Fyra Labs]].<ref>[https://wiki.fyralabs.com/Ultramarine_Linux Ultramarine Linux], Fyra Labs Wiki, 2023-10-01 (Accessed: 2025-08-10)</ref> Unlike Fedora, the Ultramarine team prioritises on being more ''pragmatical'' over being more ideological<ref name=":0">[https://wiki.ultramarine-linux.org/en/welcome/ Welcome], Ultramarine Wiki, 2025 (Accessed: 2025-08-10)</ref>, by for example installing non-free drivers and codecs automatically<ref>[https://www.zdnet.com/article/ultramarine-linux-40-continues-to-be-one-fine-unofficial-fedora-spin/ Ultramarine Linux 40 continues to be one fine unofficial Fedora Spin], Jack Wallen, 2024-12-23 (Accessed: 2025-08-10)</ref>, improving overall user experience. == History == Created in 2021, Ultramarine Linux was the spiritual successor to [[Korora Linux]], following the goal of creating a system that “just works”. It was created due to “frustration with the legal limits of Fedora”<ref>[https://github.com/Ultramarine-Linux/wiki/blob/ba740779d7fe037429c88adbe238039ea3c69991/src/content/docs/en/welcome.md wiki/src/content/docs/en/welcome.md at ba740779d7fe037429c88adbe238039ea3c69991 · Ultramarine-Linux/wiki], Ultramarine Linux, 2023 (Accessed: 2025-08-10)</ref>, and was shipped as a base-Fedora image with tweaks, codecs and drivers on top. The first release Ultramarine 35 (UM35) came with 4 editions: Budgie, [[Cutefish]], [[Pantheon]] and [[GNOME]]. Budgie was made as the ''flagship'' edition, because it was a rather popular [[DE]] that was not yet available on Fedora 35.<ref>[https://news.itsfoss.com/fedora-budgie-sway-official/ Official Fedora Budgie & Sway Spins to Arrive With Fedora 38 Release], Sourav Rudra, 2023-01-04 (Accessed: 2025-08-10)</ref> The merger with Fyra Labs later brought packaging toolchains like Andaman and Subatomic to life, which replaced Ultramarine's own packaging tool [http://github.com/Ultramarine-Linux/umpkg umpkg], and was followed by the creation of [[Terra]], which was intended to be a common software [[repository]] shared between Ultramarine and its sister project [[tauOS]]. Cutefish and Pantheon editions were removed in later editions due to lack of upstream maintenance, and were replaced by KDE Plasma and XFCE respectively.<ref name=":0"/> == Repositories == Apart from the Fedora stable and update repositories, Ultramarine also comes with all free and non-free [[RPM Fusion]] repositories, and Terra with extra streams enabled. Ultramarine Linux also comes with [[Flathub]] instead of [[Fedora Flatpaks]], making the experience free of hassles.<ref name=":0"/> == Ultramarine Anywhere == Originally named as ''Ultramarine Everywhere'', ''Ultramarine Anywhere'' is an initiative started from Ultramarine 38 that provides better hardware support for other platforms.<ref>[https://wiki.ultramarine-linux.org/en/anywhere/anywhere/ Ultramarine Anywhere], Ultramarine Wiki, 2025 (Accessed: 2025-08-10)</ref> Currently Ultramarine Linux has first-class support for various different kinds of [[Chromebook]], [[Raspberry Pi]], and [[Microsoft Surface]] models. Ultramarine also initiated earlier [[WSL]] support than Fedora and its derivatives. == References == aff7d3a74fa3cb5e948adc73b7b852e048bb95e8 3498 3497 2025-08-10T10:11:22Z Madonuko 140 /* Installation */ wikitext text/x-wiki [[category:Linux Distributions]] {{DistributionInfobox | title = Ultramarine Linux | image = [[File:Ultramarine_Logo_Icon.svg|Ultramarine Logo|frameless]] | caption = Ultramarine Linux Logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[dnf|dnf5]], [[rpm]], [[flatpak]] | defaultdesktops = [[Budgie]], [[GNOME]], [[Plasma]], [[XFCE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = https://ultramarine-linux.org | Current version = um42 }} '''Ultramarine Linux''' is a [[Fedora]]-based Linux distribution for people with varying technical backgrounds by providing sane defaults and tweaks out of the box.<ref>[https://ultramarine-linxu.org Ultramarine Linux], Ultramarine Project, 2025 (Accessed: 2025-08-10)</ref> Started by Cappy Ishihara in 2021, the team ''Ultramarine Project'' later had a merger, and the [[distro]] is now a major successful product by [[Fyra Labs]].<ref>[https://wiki.fyralabs.com/Ultramarine_Linux Ultramarine Linux], Fyra Labs Wiki, 2023-10-01 (Accessed: 2025-08-10)</ref> Unlike Fedora, the Ultramarine team prioritises on being more ''pragmatical'' over being more ideological<ref name=":0">[https://wiki.ultramarine-linux.org/en/welcome/ Welcome], Ultramarine Wiki, 2025 (Accessed: 2025-08-10)</ref>, by for example installing non-free drivers and codecs automatically<ref>[https://www.zdnet.com/article/ultramarine-linux-40-continues-to-be-one-fine-unofficial-fedora-spin/ Ultramarine Linux 40 continues to be one fine unofficial Fedora Spin], Jack Wallen, 2024-12-23 (Accessed: 2025-08-10)</ref>, improving overall user experience. == History == Created in 2021, Ultramarine Linux was the spiritual successor to [[Korora Linux]], following the goal of creating a system that “just works”. It was created due to “frustration with the legal limits of Fedora”<ref>[https://github.com/Ultramarine-Linux/wiki/blob/ba740779d7fe037429c88adbe238039ea3c69991/src/content/docs/en/welcome.md wiki/src/content/docs/en/welcome.md at ba740779d7fe037429c88adbe238039ea3c69991 · Ultramarine-Linux/wiki], Ultramarine Linux, 2023 (Accessed: 2025-08-10)</ref>, and was shipped as a base-Fedora image with tweaks, codecs and drivers on top. The first release Ultramarine 35 (UM35) came with 4 editions: Budgie, [[Cutefish]], [[Pantheon]] and [[GNOME]]. Budgie was made as the ''flagship'' edition, because it was a rather popular [[DE]] that was not yet available on Fedora 35.<ref>[https://news.itsfoss.com/fedora-budgie-sway-official/ Official Fedora Budgie & Sway Spins to Arrive With Fedora 38 Release], Sourav Rudra, 2023-01-04 (Accessed: 2025-08-10)</ref> The merger with Fyra Labs later brought packaging toolchains like Andaman and Subatomic to life, which replaced Ultramarine's own packaging tool [http://github.com/Ultramarine-Linux/umpkg umpkg], and was followed by the creation of [[Terra]], which was intended to be a common software [[repository]] shared between Ultramarine and its sister project [[tauOS]]. Cutefish and Pantheon editions were removed in later editions due to lack of upstream maintenance, and were replaced by KDE Plasma and XFCE respectively.<ref name=":0"/> == Installation == There are 3 main supported ways to install Ultramarine Linux: # Migration from Fedora ([https://ultramarine-linux.org/migrate.sh migrate.sh]) or [[risiOS]] ([https://ultramarine-linux.org/migrate-risi.sh migrate-risi.sh]) is supported. # ISO and raw images are provided for different corresponding platforms on the [https://ultramarine-linux.org/download/ download page]. # Ultramarine WSL is also available on the [https://apps.microsoft.com/detail/9pbpg2rdmzb9 Microsoft Store]. == Repositories == Apart from the Fedora stable and update repositories, Ultramarine also comes with all free and non-free [[RPM Fusion]] repositories, and Terra with extra streams enabled. Ultramarine Linux also comes with [[Flathub]] instead of [[Fedora Flatpaks]], making the experience free of hassles.<ref name=":0"/> == Ultramarine Anywhere == Originally named as ''Ultramarine Everywhere'', ''Ultramarine Anywhere'' is an initiative started from Ultramarine 38 that provides better hardware support for other platforms.<ref>[https://wiki.ultramarine-linux.org/en/anywhere/anywhere/ Ultramarine Anywhere], Ultramarine Wiki, 2025 (Accessed: 2025-08-10)</ref> Currently Ultramarine Linux has first-class support for various different kinds of [[Chromebook]], [[Raspberry Pi]], and [[Microsoft Surface]] models. Ultramarine also initiated earlier [[WSL]] support than Fedora and its derivatives. == References == 77e52c3f36ce5ea57d111c7652542866a58d0f3e 0 843 3499 2025-08-10T11:32:06Z Madonuko 140 init wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Gnu-nano.svg|frameless]] | caption = [[GNU]] nano logo | title = <code>nano</code> | releasestatus = Maintained | lastrelease = 8.5 | languages = [[C]] | developers = GNU <code>nano</code>: GNU Project, et al. | website = https://www.nano-editor.org/ }} The '''nano''' editor is a simple, user-friendly [[TUI]] text editor<ref>[https://www.nano-editor.org/dist/latest/nano.html The GNU nano text editor], GNU, 2025-06-12 (Accessed: 2025-08-10)</ref> commonly preinstalled on most [[UNIX]]-like [[OS|operating system]]s. While other UNIX TUI editors such as [[vim]] and [[emacs]] require the user to memorise keybinds and shortcuts, nano's interface comes with reminders on how to perform most common-day tasks, making it suitable even for users without technical backgrounds.<ref>[https://www.geeksforgeeks.org/linux-unix/nano-text-editor-in-linux/ Nano Text Editor in Linux], GeeksforGeeks, 2025-07-12 (Accessed: 2025-08-10)</ref> nano also supports some advanced features, such as syntax highlighting.<ref>[https://wiki.archlinux.org/title/Nano nano], ArchWiki (Accessed: 2025-08-10)</ref> == History == === Naming === According to the manual, the name ''nano'' stands for ''“Nano's ANOther text editor”''. Its original name ''TIP'' stood for ''“TIP Isn't Pico”'', where [[pico]] was another text editor that eventually inspired the creation of nano.<ref>[[wikipedia:GNU nano]], Wikipedia contributors, 2025 (Accessed: 2025-08-10)</ref> == Installation == nano is installed by default on most Unix-like systems. If not, consult the distribution's [[package manager]]. For most cases the package name would be <code>nano</code>. == Usage == See <code>[[man]] 'nano(1)'</code>. In short, run <code>nano filename.txt</code> to start editing a specific file, regardless of whether the file exists. == References == 55fe78453461fa2e7ca547a2a5f8afeafcfb175e 0 844 3500 2025-08-10T11:33:16Z Madonuko 140 #REDIRECT [[nano]] wikitext text/x-wiki #REDIRECT [[nano]] e1343ca8c2200e08740fb366b483db5a1d9e36df 0 274 3501 2008 2025-08-10T12:48:24Z Iguanacucumber 246 precise dinit is available in the ISO wikitext text/x-wiki {{Needs Citations}}{{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''', also known simply as '''Artix''', is a Linux distribution based on [[Arch]] that focuses on providing alternative init systems to systemd . It maintains high compatibility with Arch Linux while offering users the freedom to choose their preferred init system. == History == Artix Linux emerged from the Arch-OpenRC and Manjaro-OpenRC projects, officially launching in 2017 as a response to Arch Linux's adoption of systemd as its only init system. The distribution aims to provide a systemd-free experience while maintaining the principles of simplicity and user-centricity that Arch Linux is known for. == Features == === Init System Options === Artix supports multiple init systems: * OpenRC - A dependency-based init system from Gentoo * runit - A cross-platform Unix init scheme with service supervision * s6 - A suite of programs for process supervision * dinit - A service manager and init system designed to be simple and portable === Package Management === Artix uses [[Pacman]] as its package manager and maintains its own repositories alongside converted Arch Linux packages. The distribution provides several package repositories: * System repositories (specific to each init system) * Universe repository (containing converted Arch packages) * Galaxy repository (Artix-specific packages) === Installation === The distribution offers several installation methods: * Live ISOs with various desktop environments * Base ISOs for minimal installations * OpenRC, runit, dinit, and s6 variants of each ISO == Philosophy == Artix adheres to the KISS principle (Keep It Simple, Stupid) inherited from Arch Linux while emphasizing: * Init system freedom * System transparency * User control * Minimal [[bloat]] * Rolling release model == Package Compatibility == While maintaining high compatibility with Arch Linux packages, some modifications are necessary for systemd-dependent packages. The Artix team maintains: * Native packages built specifically for Artix * Converted Arch packages modified to work without systemd * Scripts and tools to help users convert systemd-dependent packages == Community == Artix Linux maintains its own: * Forums for user support and discussion * Wiki documentation * Package repositories * Development team == System Requirements == * x86_64 architecture * Minimum 512 MB RAM (2 GB recommended) * Minimum 2 GB storage (20 GB recommended) * Basic knowledge of command line operations * Understanding of Linux system administration [[Category:Linux Distributions]] 30481f156dfcce788f57eb2e365df03b2cb267f3 0 198 3502 3427 2025-08-10T12:50:43Z Solomoncyj 225 add steamOS to list of distributions wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos<nowiki> Steamos], Valve, 2025</nowiki></ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] e279b53f3fd03666dffb9be94168b749dd9641a3 3505 3502 2025-08-10T13:08:23Z Madonuko 140 /* References */ fix last edit wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-Based Distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] 69ef51011b1132535be66502dd3d716932e73f5e 3514 3505 2025-08-10T16:47:17Z Madonuko 140 /* Arch Based */ add CyberOS wikitext text/x-wiki A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == [[Category:Linux Distributions]] 123ff6bd2cef784e2456ca85ba0fa34e9a33f624 0 769 3503 3482 2025-08-10T13:01:18Z Iguanacucumber 246 add dwl compositor wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''[[Niri]]''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |Cosmic-comp<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |Cosmic |Rust |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |labwc<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |C |A Stacking/Floating Wayland compositor inspired by Openbox. |- | '''dwl<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref>''' || None || C || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> a2ac108d8f924b1d6d9657d89b20c6f82b5b35ab 3504 3503 2025-08-10T13:04:42Z Iguanacucumber 246 precise dwl is a manual tiller wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref>''' || None (Reference) || C || Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || [[KDE Plasma]]|| C++ || KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref>''' || None (tiling) || Zig || Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''[[Niri]]''' || None (scrolling/tiling) || Rust || A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |Cosmic-comp<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |Cosmic |Rust |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |labwc<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |C |A Stacking/Floating Wayland compositor inspired by Openbox. |- | '''dwl<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref>''' || None (tilling) || C || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 4b870fe6c56a01ac1f8280a8649e6de9e3dacf8f 0 763 3506 3418 2025-08-10T13:29:02Z Satnus 215 Fixed a small issue with the table. wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Openbox 3.4.10 default.png|link=Openbox|Openbox </gallery> {| class="wikitable" |+ !Window Manager !Description |- |[[awesome]]<ref>[https://github.com/awesomeWM/awesome GitHub - awesomeWM/awesome: awesome window manager], awesomeWM, 2025-08-09 (Accessed: 2025-08-09)</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |[[Compiz]] |Compiz is a compositing window manager for the X Window System. |- |[[Openbox]] |A minimal and highly configurable stacking window manager written in C. |- |[[twm]]<ref>[https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml TWM], 2010-11-13 (Accessed: 2025-08-09)</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |[[IceWM]]<ref>[https://github.com/bbidulock/icewm GitHub - bbidulock/icewm: A window manager designed for speed, usability, and consistency], bbidulock, 2025-08-09 (Accessed: 2025-08-09)</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |[[i3]]<ref>[https://i3wm.org i3: improved tiling X11 window manager], Michael Stapelberg, 2025-06-12 (Accessed: 2025-08-09)</ref> |A tiling window manager for advanced users and developers. |- |[[Window Maker]]<ref>[https://github.com/window-maker/wmaker GitHub - window-maker/wmaker: Mirror of the official repository repo.or.cz/wmaker-crm.git. Do not send pull requests here, send your patches to wmaker-dev@googlegroups.com instead], window-maker, 2020-08-09 (Accessed: 2025-08-09)</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |[[XMonad]]<ref>[https://xmonad.org/ home | xmonad - the tiling window manager that rocks], xmonad, 2025-06-15 (Accessed: 2025-08-09)</ref> |Window Manager configurable via the Haskell functional programming language. |} ==References== <references /> a9b2179fca85612fe845b6593c1ca085e8cba6f1 0 846 3508 2025-08-10T13:51:54Z Platzmacher 245 i added a redirect to the C programing page wikitext text/x-wiki #REDIRECT [[C]] cca4306dba82e7672800fd8eb9cfecf07152a86a 6 847 3509 2025-08-10T15:16:10Z Madonuko 140 from gh wikitext text/x-wiki == Summary == from gh ac8c2900b9701f75fe214c46dbe1ad5b349e6f32 10 799 3510 3227 2025-08-10T15:25:53Z Madonuko 140 fix empty lines wikitext text/x-wiki {{#invoke:mbox|mbox | icon = OOjs UI icon alert.svg | title = This page is a stub. {{AssistByEditing|action=expanding}} | text = This message means that this page has been deemed not long enough to provide meaningful coverage of its topic. | extraclasses = mbox-med notice-stub }}<includeonly>{{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup||[[Category:Pages Needing Cleanup]]}}</includeonly><noinclude> <templatedata> { "params": {}, "description": "Adds a notice that the page may be too short with a call to action to expand it" } </templatedata> </noinclude> 70f6b3bf87499f4e2e18913b05e3370a0c35419b 8 357 3511 2255 2025-08-10T16:13:36Z Atmois 13 Change default to full width css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.citizen-feature-custom-width-clientpref-full :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } /* * Footer icons * We use custom footer icons from https://starcitizen.tools for our footers, the following CSS comes from their wiki */ #footer-icons a { border: 0; padding: 0; background: transparent; opacity: var( --opacity-icon-base ); transition: opacity 250ms ease; } #footer-icons a:hover { opacity: var( --opacity-icon-base--hover ); } #footer-icons a:active { opacity: var( --opacity-icon-base--active ); } /* More space between icons */ #footer-icons ul, #footer-icons li { gap: var( --space-md ); } #footer-icons img { width: auto; height: 32px; } /* Divide footer links into two columns */ #footer-places { column-count: 2; } /* Fix misalignment in Safari and Firefox when using two columns */ #footer-places ul { display: initial; } /* Darken the footer icon in light mode */ .skin-citizen-light #footer-icons a { filter: invert( 1 ) hue-rotate( 180deg ); } 5d9ca1e98c18cd868d478cc8d4e51e127b2a18a4 0 848 3512 2025-08-10T16:42:20Z Madonuko 140 init wikitext text/x-wiki [[category:Linux Distributions]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued in around 2022 to 2023<ref>[https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2022 (Accessed: 2022-05-14)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the DE, and Arch Linux was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to Ubuntu. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were remove and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The CutefishOS team which was rebased to Sichuan also did not live long due to lack of Western support, and silently died out between mid-2021 and 2022. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives] == References == a7c7cd2f47a359ad82778a3d6b8328f7d1543409 3515 3512 2025-08-10T17:01:24Z Madonuko 140 /* History */ add revives wikitext text/x-wiki [[category:Linux Distributions]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued in around 2022 to 2023<ref>[https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2022 (Accessed: 2022-05-14)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the DE, and Arch Linux was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to Ubuntu. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were remove and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The new CutefishOS team which was rebased to Sichuan also did not live long due to lack of Western support, and silently died out between mid-2021 and 2022. === CutefishOS Reborn === CutefishOS Reborn was a Western community's attempt to revive CutefishOS's development. It gauged some interest but very quickly died off in mid-2022. === LingmoOS === [https://github.com/LingmoOS/LingmoOS LingmoOS] is an active revive<ref>[https://github.com/orgs/cutefishos/discussions/22 Is this project dead or still in development? · cutefishos · Discussion #22], GitHub, 2023 (Accessed: 2025-08-11)</ref> of CutefishOS, but it has not received major attention from the media. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives] == References == de72d0382672aec4d017dd964c86c8462ac78ed6 0 849 3513 2025-08-10T16:44:16Z Madonuko 140 #REDIRECT [[CyberOS]] wikitext text/x-wiki #REDIRECT [[CyberOS]] eef1770cba0ed0f80b05f152f846f333556536fc 0 233 3516 3412 2025-08-10T20:11:44Z Imnotgoodatnames 121 Replaced "Bluepill" logo with official logo from the website wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware_logo_from_the_official_Slackware_site.svg|frameless|upright=0.8|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }}[[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>[http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf A history of Slackware development], Eric Hameleers, 2009-10-09 (Accessed: 2025-08-09)</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with KDE * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. == References == [[Category:Linux Distributions]] b9592963b7c5536fec188cd43bdad7500736f095 3517 3516 2025-08-10T20:14:03Z Imnotgoodatnames 121 logo is now inverted in dark theme to improve visibility wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware_logo_from_the_official_Slackware_site.svg{{!}}class=skin-invert|frameless|upright=0.8|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }}[[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>[http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf A history of Slackware development], Eric Hameleers, 2009-10-09 (Accessed: 2025-08-09)</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with KDE * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. == References == [[Category:Linux Distributions]] 24a2af88d63e196af3bbfb5ab29f30ebf913c0f8 8 196 3518 2927 2025-08-10T20:25:29Z Atmois 13 Removed protection from "[[MediaWiki:Common.js]]": Revert to namespace protections javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://atl.wiki/ATL:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://umami.atl.wiki/script.js'; s.setAttribute('data-website-id', '21f384be-587d-4b00-8727-203d00c898d5'); document.head.appendChild(s); df22fc0d55dafa3da87c38473b5c87c26b87f125 828 359 3519 1591 2025-08-10T20:27:39Z Atmois 13 Removed protection from "[[Module:Arguments]]": Revert to namespace protections Scribunto text/plain -- This module provides easy processing of arguments passed to Scribunto from -- #invoke. It is intended for use by other Lua modules, and should not be -- called from #invoke directly. local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local arguments = {} -- Generate four different tidyVal functions, so that we don't have to check the -- options every time we call it. local function tidyValDefault(key, val) if type(val) == 'string' then val = val:match('^%s*(.-)%s*$') if val == '' then return nil else return val end else return val end end local function tidyValTrimOnly(key, val) if type(val) == 'string' then return val:match('^%s*(.-)%s*$') else return val end end local function tidyValRemoveBlanksOnly(key, val) if type(val) == 'string' then if val:find('%S') then return val else return nil end else return val end end local function tidyValNoChange(key, val) return val end local function matchesTitle(given, title) local tp = type( given ) return (tp == 'string' or tp == 'number') and mw.title.new( given ).prefixedText == title end local translate_mt = { __index = function(t, k) return k end } function arguments.getArgs(frame, options) checkType('getArgs', 1, frame, 'table', true) checkType('getArgs', 2, options, 'table', true) frame = frame or {} options = options or {} --[[ -- Set up argument translation. --]] options.translate = options.translate or {} if getmetatable(options.translate) == nil then setmetatable(options.translate, translate_mt) end if options.backtranslate == nil then options.backtranslate = {} for k,v in pairs(options.translate) do options.backtranslate[v] = k end end if options.backtranslate and getmetatable(options.backtranslate) == nil then setmetatable(options.backtranslate, { __index = function(t, k) if options.translate[k] ~= k then return nil else return k end end }) end --[[ -- Get the argument tables. If we were passed a valid frame object, get the -- frame arguments (fargs) and the parent frame arguments (pargs), depending -- on the options set and on the parent frame's availability. If we weren't -- passed a valid frame object, we are being called from another Lua module -- or from the debug console, so assume that we were passed a table of args -- directly, and assign it to a new variable (luaArgs). --]] local fargs, pargs, luaArgs if type(frame.args) == 'table' and type(frame.getParent) == 'function' then if options.wrappers then --[[ -- The wrappers option makes Module:Arguments look up arguments in -- either the frame argument table or the parent argument table, but -- not both. This means that users can use either the #invoke syntax -- or a wrapper template without the loss of performance associated -- with looking arguments up in both the frame and the parent frame. -- Module:Arguments will look up arguments in the parent frame -- if it finds the parent frame's title in options.wrapper; -- otherwise it will look up arguments in the frame object passed -- to getArgs. --]] local parent = frame:getParent() if not parent then fargs = frame.args else local title = parent:getTitle():gsub('/sandbox$', '') local found = false if matchesTitle(options.wrappers, title) then found = true elseif type(options.wrappers) == 'table' then for _,v in pairs(options.wrappers) do if matchesTitle(v, title) then found = true break end end end -- We test for false specifically here so that nil (the default) acts like true. if found or options.frameOnly == false then pargs = parent.args end if not found or options.parentOnly == false then fargs = frame.args end end else -- options.wrapper isn't set, so check the other options. if not options.parentOnly then fargs = frame.args end if not options.frameOnly then local parent = frame:getParent() pargs = parent and parent.args or nil end end if options.parentFirst then fargs, pargs = pargs, fargs end else luaArgs = frame end -- Set the order of precedence of the argument tables. If the variables are -- nil, nothing will be added to the table, which is how we avoid clashes -- between the frame/parent args and the Lua args. local argTables = {fargs} argTables[#argTables + 1] = pargs argTables[#argTables + 1] = luaArgs --[[ -- Generate the tidyVal function. If it has been specified by the user, we -- use that; if not, we choose one of four functions depending on the -- options chosen. This is so that we don't have to call the options table -- every time the function is called. --]] local tidyVal = options.valueFunc if tidyVal then if type(tidyVal) ~= 'function' then error( "bad value assigned to option 'valueFunc'" .. '(function expected, got ' .. type(tidyVal) .. ')', 2 ) end elseif options.trim ~= false then if options.removeBlanks ~= false then tidyVal = tidyValDefault else tidyVal = tidyValTrimOnly end else if options.removeBlanks ~= false then tidyVal = tidyValRemoveBlanksOnly else tidyVal = tidyValNoChange end end --[[ -- Set up the args, metaArgs and nilArgs tables. args will be the one -- accessed from functions, and metaArgs will hold the actual arguments. Nil -- arguments are memoized in nilArgs, and the metatable connects all of them -- together. --]] local args, metaArgs, nilArgs, metatable = {}, {}, {}, {} setmetatable(args, metatable) local function mergeArgs(tables) --[[ -- Accepts multiple tables as input and merges their keys and values -- into one table. If a value is already present it is not overwritten; -- tables listed earlier have precedence. We are also memoizing nil -- values, which can be overwritten if they are 's' (soft). --]] for _, t in ipairs(tables) do for key, val in pairs(t) do if metaArgs[key] == nil and nilArgs[key] ~= 'h' then local tidiedVal = tidyVal(key, val) if tidiedVal == nil then nilArgs[key] = 's' else metaArgs[key] = tidiedVal end end end end end --[[ -- Define metatable behaviour. Arguments are memoized in the metaArgs table, -- and are only fetched from the argument tables once. Fetching arguments -- from the argument tables is the most resource-intensive step in this -- module, so we try and avoid it where possible. For this reason, nil -- arguments are also memoized, in the nilArgs table. Also, we keep a record -- in the metatable of when pairs and ipairs have been called, so we do not -- run pairs and ipairs on the argument tables more than once. We also do -- not run ipairs on fargs and pargs if pairs has already been run, as all -- the arguments will already have been copied over. --]] metatable.__index = function (t, key) --[[ -- Fetches an argument when the args table is indexed. First we check -- to see if the value is memoized, and if not we try and fetch it from -- the argument tables. When we check memoization, we need to check -- metaArgs before nilArgs, as both can be non-nil at the same time. -- If the argument is not present in metaArgs, we also check whether -- pairs has been run yet. If pairs has already been run, we return nil. -- This is because all the arguments will have already been copied into -- metaArgs by the mergeArgs function, meaning that any other arguments -- must be nil. --]] if type(key) == 'string' then key = options.translate[key] end local val = metaArgs[key] if val ~= nil then return val elseif metatable.donePairs or nilArgs[key] then return nil end for _, argTable in ipairs(argTables) do local argTableVal = tidyVal(key, argTable[key]) if argTableVal ~= nil then metaArgs[key] = argTableVal return argTableVal end end nilArgs[key] = 'h' return nil end metatable.__newindex = function (t, key, val) -- This function is called when a module tries to add a new value to the -- args table, or tries to change an existing value. if type(key) == 'string' then key = options.translate[key] end if options.readOnly then error( 'could not write to argument table key "' .. tostring(key) .. '"; the table is read-only', 2 ) elseif options.noOverwrite and args[key] ~= nil then error( 'could not write to argument table key "' .. tostring(key) .. '"; overwriting existing arguments is not permitted', 2 ) elseif val == nil then --[[ -- If the argument is to be overwritten with nil, we need to erase -- the value in metaArgs, so that __index, __pairs and __ipairs do -- not use a previous existing value, if present; and we also need -- to memoize the nil in nilArgs, so that the value isn't looked -- up in the argument tables if it is accessed again. --]] metaArgs[key] = nil nilArgs[key] = 'h' else metaArgs[key] = val end end local function translatenext(invariant) local k, v = next(invariant.t, invariant.k) invariant.k = k if k == nil then return nil elseif type(k) ~= 'string' or not options.backtranslate then return k, v else local backtranslate = options.backtranslate[k] if backtranslate == nil then -- Skip this one. This is a tail call, so this won't cause stack overflow return translatenext(invariant) else return backtranslate, v end end end metatable.__pairs = function () -- Called when pairs is run on the args table. if not metatable.donePairs then mergeArgs(argTables) metatable.donePairs = true end return translatenext, { t = metaArgs } end local function inext(t, i) -- This uses our __index metamethod local v = t[i + 1] if v ~= nil then return i + 1, v end end metatable.__ipairs = function (t) -- Called when ipairs is run on the args table. return inext, t, 0 end return args end return arguments 3134ecce8429b810d445e29eae115e2ae4c36c53 8 400 3520 2162 2025-08-10T20:29:03Z Atmois 13 Removed protection from "[[MediaWiki:Citizen-footer-desc]]": Revert to namespace protections wikitext text/x-wiki This is the official wiki by the [https://discord.gg/linux All Things Linux Discord server]! The aim of this wiki is to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software! If you need support, ensure to check out our Discord server! You can see the raw content for the page you are on [{{fullurl:{{FULLPAGENAME}}|action=raw}} here]! 5f40dfd76a83ec9e703a71644337e72227214c90 10 494 3521 2727 2025-08-10T20:29:14Z Atmois 13 Removed protection from "[[Template:Cleanup/doc]]": Revert to namespace protections wikitext text/x-wiki This template should be placed on pages which might not meet the wiki's [[ATL:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Biased Tone", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance Templates]]</includeonly> 2cdd88619099b974f1bca951a6029334574ffad6 10 513 3522 2728 2025-08-10T20:29:23Z Atmois 13 Removed protection from "[[Template:Needs Citations]]": Revert to namespace protections wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This template is to be used on pages which may lack credible citations, as per our [[ATL:Guidelines#Citations|citations guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Needs_Citations|| [[Category:Needs_Citations]] }} </includeonly> <noinclude> {{/doc}}</noinclude> d5e1de62687cd582b2d0b2d77cacf43d9c3fbd93 10 514 3523 2729 2025-08-10T20:29:31Z Atmois 13 Removed protection from "[[Template:Needs Citations/doc]]": Revert to namespace protections wikitext text/x-wiki This template should be placed on pages which may lack credible citations, as per our [[ATL:Guidelines#Citations|citations policy]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations. == Usage == <code>{{tlx|Needs Citations}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> e388826549d40e7af002744cad384106e739fd62 10 487 3524 1700 2025-08-10T20:30:15Z Atmois 13 Removed protection from "[[Template:Documentation]]": Revert to namespace protections wikitext text/x-wiki <includeonly>{{#invoke:Documentation|doc}}__NOEDITSECTION__{{ |type = website |description = {{FULLPAGENAME}} is a template page used on the ATL Wiki. Templates are pages that are embedded into other articles as reuseable elements. |site_name = ATL Wiki |locale = {{PAGELANGUAGE}} }}</includeonly><noinclude>{{/doc}}</noinclude> 04f832677890e699d88890f9cbc8494ea4a74e48 10 520 3525 1701 2025-08-10T20:30:22Z Atmois 13 Removed protection from "[[Template:Documentation/doc]]": Revert to namespace protections wikitext text/x-wiki A template used to document a subpage. 385aff1b35454723846533045b9ce9b36f676f26 10 482 3526 2730 2025-08-10T20:30:33Z Atmois 13 Removed protection from "[[Template:Guide Warning]]": Revert to namespace protections wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section lists commands or instructions which could potentially damage your system. Please ensure you understand the commands or instructions you are running or following before you run or follow them.</span> <div class="mbox-text">This warning exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[ATL:Contact|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> 8d505407cdcb0e0220faa9f5022ebda8e816c71b 10 521 3527 2731 2025-08-10T20:30:42Z Atmois 13 Removed protection from "[[Template:Guide Warning/doc]]": Revert to namespace protections wikitext text/x-wiki This warning is placed on any page that lists a command and gives users instructions to follow, it exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[ATL:Contact|administrator]] immediately. == Usage == <code>{{tlx|Guide_Warning}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> e72c02efe78a8c2c8327363c060e2c0699ae66bb 10 523 3528 3361 2025-08-10T20:30:54Z Atmois 13 Removed protection from "[[Template:Work In Progress]]": Revert to namespace protections wikitext text/x-wiki <includeonly><div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This template means the author of a page is still actively working on the page, and this serves to notify other editors to check with them before potentially creating conflicting changes and to notify the staff that it may not meet the wiki's [[ATL:Guidelines|guidelines]] yet.</div></div><templatestyles src="Module:Mbox/styles.css" /></includeonly><noinclude>{{/doc}}</noinclude> efce70105ae18cd4a3fffe04150752f317cca310 10 524 3529 2733 2025-08-10T20:31:02Z Atmois 13 Removed protection from "[[Template:Work In Progress/doc]]": Revert to namespace protections wikitext text/x-wiki This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes and to notify the staff that it may not meet the [[ATL:Guidelines|contributing standards]] yet. == Usage == <code>{{tlx|Work_In_Progress}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> ee585853065eba467dc49a8a24edb7a398d5d92b 10 483 3530 3360 2025-08-10T20:31:11Z Atmois 13 Removed protection from "[[Template:Cleanup]]": Revert to namespace protections wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[ATL:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /> <includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]]}} </includeonly> <noinclude> {{/doc}}</noinclude> 10652b198b9e783d0e6919a74157eee7da57054a 8 538 3531 1880 2025-08-10T20:31:51Z Atmois 13 Removed protection from "[[MediaWiki:Sitenotice]]": Revert to namespace protections wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 850 3533 2025-08-10T21:33:06Z OgloTheNerd 248 wikitext text/x-wiki Btop is a terminal-based system monitoring tool. 8db3c001f021da262aecdd070185a352d4cd6f6e 0 174 3534 2845 2025-08-10T21:34:45Z OgloTheNerd 248 Rewrote the entire wiki page, made it much more informative. wikitext text/x-wiki {{Cleanup|Incomplete page}} [[File:Btop.png|alt=Btop System Monitor|thumb|Btop, a terminal-based system monitoring tool.]] A terminal user interface (TUI) is a form of user interface where a program prints special characters that are interpreted by the terminal renderer and are completely invisible, but manipulate the way the terminal renders stuff like for example changing the color of the following text, moving the cursor to an arbitrary place in the terminal, making text bold, making text italic, changing the color palette of the Linux TTY, and so much more. The program can also read in keyboard input by reading special character sequences in sent by the terminal driver. '''<u>FUN FACT</u>''': You may have tried using your arrow keys once or twice to move your cursor in a prompt from a program such as the [[Pacman]] package manager or something else that throws prompts for the user to answer. You may have noticed that instead of moving your cursor, the arrow keys send "garbage" text ("^[[D^[[C^[[A^[[B"). Programs such as Bash are able to move your cursor when you hit the arrow keys by actually reading and interpreting this "garbage" text in real-time using a terminal configuration mode called "raw mode" which is when the terminal disables a bunch of buffering settings that would normally require you to press ENTER before the terminal can see your user input. {| class="wikitable" |+Terminal Manipulation Libraries !Library !Language !Developer !Description |- |[https://gitlab.com/Oglo12/otmlib Oglo's Terminal Manipulation Library] |[[C (programming language)|C]] |Jackson Novak (OgloTheNerd) |A single-header C99 library for manipulating the terminal. |- |[https://invisible-island.net/ncurses/ NCurses] |[[C (programming language)|C]] |Thomas Dickey |A library installed on most Linux and BSD systems for creating terminal user interfaces. |- |[https://crates.io/crates/crossterm Crossterm] |[[Rust]] |Timon |A cross-platform terminal manipulation library written in Rust. |- |[https://github.com/termbox/termbox2 Termbox2] |[[C (programming language)|C]] |Adam |A suckless single-header C library for manipulating the terminal. |} [[Category:Terminology]] c32e80e981788956905c455d16de7206bb59fc7b 3537 3534 2025-08-10T21:54:19Z OgloTheNerd 248 Added link to Bash. wikitext text/x-wiki {{Cleanup|Incomplete page}} [[File:Btop.png|alt=Btop System Monitor|thumb|Btop, a terminal-based system monitoring tool.]] A terminal user interface (TUI) is a form of user interface where a program prints special characters that are interpreted by the terminal renderer and are completely invisible, but manipulate the way the terminal renders stuff like for example changing the color of the following text, moving the cursor to an arbitrary place in the terminal, making text bold, making text italic, changing the color palette of the Linux TTY, and so much more. The program can also read in keyboard input by reading special character sequences in sent by the terminal driver. '''<u>FUN FACT</u>''': You may have tried using your arrow keys once or twice to move your cursor in a prompt from a program such as the [[Pacman]] package manager or something else that throws prompts for the user to answer. You may have noticed that instead of moving your cursor, the arrow keys send "garbage" text ("^[[D^[[C^[[A^[[B"). Programs such as [https://www.gnu.org/software/bash/ Bash] are able to move your cursor when you hit the arrow keys by actually reading and interpreting this "garbage" text in real-time using a terminal configuration mode called "raw mode" which is when the terminal disables a bunch of buffering settings that would normally require you to press ENTER before the terminal can see your user input. {| class="wikitable" |+Terminal Manipulation Libraries !Library !Language !Developer !Description |- |[https://gitlab.com/Oglo12/otmlib Oglo's Terminal Manipulation Library] |[[C (programming language)|C]] |Jackson Novak (OgloTheNerd) |A single-header C99 library for manipulating the terminal. |- |[https://invisible-island.net/ncurses/ NCurses] |[[C (programming language)|C]] |Thomas Dickey |A library installed on most Linux and BSD systems for creating terminal user interfaces. |- |[https://crates.io/crates/crossterm Crossterm] |[[Rust]] |Timon |A cross-platform terminal manipulation library written in Rust. |- |[https://github.com/termbox/termbox2 Termbox2] |[[C (programming language)|C]] |Adam |A suckless single-header C library for manipulating the terminal. |} [[Category:Terminology]] 4d449e242b891ddad351ae4c7ae3219ab9b217e4 2 851 3538 2025-08-11T00:02:37Z Platzmacher 245 added my page wikitext text/x-wiki <syntaxhighlight lang="json" line="1"> { "user": { "name": "Eric", "age": 17, "gender": { "sex":"Agender", "pronouns": "any" }, "discord": { "username": "platzmacher", "link": "https://discord.com/users/749590720284852296" }, "OS": { "Linux": { "distro": "Manjaro", "WM": "Hyprland" }, "Windows": "Windows 11" }, "note": "just a random dude in the Internet that thinks he can do anything" } } </syntaxhighlight> i s̶t̶o̶l̶e̶ got inspired the idea from [[User:MymeType|MymeType]] 7c2cef704e09506e9e6817049564b72aa37341dc 2 3 3539 3366 2025-08-11T01:00:09Z Amadaluzia 52 Removed useless new line wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <functional> #include <print> using String = std::string; class Person { virtual String description() = 0; }; using SocialPair = struct { String service; String username; }; class Amadaluzia : Person { public: String name = "Artur Manuel"; int age = 17; std::vector<String> interests{ "Programming", "CLI development", "GUI development", "Web development", "Library development", "System administration", "Walking", "Climbing", "Math", "Learning", "Exercise", "Sports", "Socialising", "Writing", "Photography", "Video editing", "Movie production", "Techno music", "Shoegaze", "Alternative Rock", }; std::vector<SocialPair> socials = { {"Email", "amad@atl.tools"}, {"Email (tutanota.com alt)", "amadaluzia@tutanota.com"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Matrix (pub.solar alt)", "@amadaluzia:pub.solar"}, {"Matrix (envs.net alt)", "@amadaluzia:envs.net"}, {"libera.chat", "amadaluzia"}, {"oftc.net", "amadaluzia"}, {"Revolt", "amadaluzia#3242"}, {"Mastodon", "@amadaluzia@bsd.cafe"}, {"Discord", "amadaluzia"}, {"Discord (alt)", "balke.nix"}, }; String description() override; }; String Amadaluzia::description() { String result{}; result += std::format("Good day, my name is {}, commonly known online as \"amadaluzia\". I am a {}\n", name, age); result += "year old Portuguese-Italian resident of the UK. You may have seen me in many\n"; result += "programming spaces, however, I am keenly interested in many other topics. More\n"; result += "specifically, I am interested in:\n"; for (auto interest : interests) result += std::format("- {}\n", interest); result += "I am also present on many social media platforms, even multiple times! Moreover, I\n"; result += "have pretty much the same name everywhere, so you can reliably find me. But I will\n"; result += "share my social platforms here as I use many decentralised services. Here I am:\n"; for (auto const &[service, username] : socials) result += std::format("- {} on {}\n", username, service); result += "\nIf you can find any ways of optimising this program, let me know, as long as the\n"; result += "it's kept to Amadaluzia::description(). Thank you for reading!\n"; return result; } int main(void) { Amadaluzia amadaluzia; std::println("{}", amadaluzia.description()); }</syntaxhighlight> eb0b7b21231a3e72e5546df540623c4ea8c1be0e 2 852 3540 2025-08-11T01:09:35Z Joey 250 Created page with "some random newgen nerd love ricing, working with different wms n' configs and making things pretty but optimal occasionally ill contribute to the wiki on my free time because i love linux systems and i think all users old and new deserve a resource like this one have a joyous afternoon reader !" wikitext text/x-wiki some random newgen nerd love ricing, working with different wms n' configs and making things pretty but optimal occasionally ill contribute to the wiki on my free time because i love linux systems and i think all users old and new deserve a resource like this one have a joyous afternoon reader ! 3bd10d7ac102936d47110baf69394ce6cb0f808b 0 853 3541 2025-08-11T01:19:00Z Platzmacher 245 added the start of the GNU GPL page wikitext text/x-wiki {{Work_In_Progress}} The '''GNU General Public License''' (short '''GNU GPL''' or '''GPL''') is a copyleft license published by the Free Software Foundation (FSF) and written by Richard Stallman<ref>https://archive.ph/20120907170559/http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html</ref>. The newest Version is the GNU General Public License version 3 (GNU GPLv3) released in June 2007<ref>https://www.gnu.org/licenses/gpl-3.0.en.html#license-text </ref> and can be found [here](https://www.gnu.org/licenses/gpl-3.0.en.html#license-text) TODO: Add a short description of the 3 Versions 760ef7d28fdcee862d90944707ac58794970098e 3543 3541 2025-08-11T01:22:40Z Platzmacher 245 fixed a wrong link wikitext text/x-wiki {{Work_In_Progress}} The '''GNU General Public License''' (short '''GNU GPL''' or '''GPL''') is a copyleft license published by the Free Software Foundation (FSF) and written by Richard Stallman<ref>https://archive.ph/20120907170559/http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html</ref>. The newest Version is the GNU General Public License version 3 (GNU GPLv3) released in June 2007<ref>https://www.gnu.org/licenses/gpl-3.0.en.html#license-text </ref> and can be found here [https://www.gnu.org/licenses/gpl-3.0.en.html#license-text here] TODO: Add a short description of the 3 Versions b4f5ddd284cdfedb22b3a1d279860ef5dde45960 6 854 3542 2025-08-11T01:19:17Z Beacrox 56 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 855 3544 2025-08-11T01:59:57Z Beacrox 56 Created page with "{{Needs Citations}} [[File:Pulse Visualizer.png|thumb|alt=Pulse Visualizer in CRT mode|Pulse Visualizer in CRT mode|alt=Screenshot of Pulse Visualizer displaying CRT-style visual effects.]] '''Pulse Visualizer''' is a real-time audio visualizer inspired by [https://minimeters.app/ MiniMeters] and written in [[C++]] and [[GLSL]]. It captures system audio via [[PipeWire]] or [[PulseAudio]], processes the signal through digital signal processing (DSP) stages using fftw<ref..." wikitext text/x-wiki {{Needs Citations}} [[File:Pulse Visualizer.png|thumb|alt=Pulse Visualizer in CRT mode|Pulse Visualizer in CRT mode|alt=Screenshot of Pulse Visualizer displaying CRT-style visual effects.]] '''Pulse Visualizer''' is a real-time audio visualizer inspired by [https://minimeters.app/ MiniMeters] and written in [[C++]] and [[GLSL]]. It captures system audio via [[PipeWire]] or [[PulseAudio]], processes the signal through digital signal processing (DSP) stages using fftw<ref>https://fftw.org/<nowiki/>(Accessed: 2025-8-11)</ref>, libebur128<ref>https://github.com/jiixyj/libebur128<nowiki/>(Accessed: 2025-8-11)</ref> and other custom DSP methods, and renders visuals with hardware acceleration through [[OpenGL]] in an [[SDL2]] window.<ref>https://github.com/Beacroxx/pulse-visualizer Pulse Visualizer GitHub, 2025 (Accessed: 2025-08-11)</ref> === Features === Pulse Visualizer supports multiple real-time visualization modes, including stereometer, oscilloscope, spectrum analyzer, spectrogram, peak/LUFS meter, and VU meter. Users can customize the panels with features such as CRT screen emulation using GPU compute shaders, adjustable visual effects (blur, glow, chromatic aberration, vignette), and draggable, resizable panels. The application offers hot reloading of both configuration and theme files without restarting, and is compatible with Linux and BSD systems using PipeWire or PulseAudio for audio input. === References === <references /> [[Category:Software]] __INDEX__ 9afb71b9dd8fc1a893e67b09b7b08085e2a1a1c6 2 856 3545 2025-08-11T02:08:21Z Beacrox 56 Created page with "Hello, I'm Bea! I'm from Germany and I build random electronics and software projects. My interests are Linux, 3D printing, electronics and robotics." wikitext text/x-wiki Hello, I'm Bea! I'm from Germany and I build random electronics and software projects. My interests are Linux, 3D printing, electronics and robotics. 546c3dc29d01cde47e32d76deaaf12ccd587d90c 2 427 3546 2775 2025-08-11T03:23:16Z Atmois 13 Atmois moved page [[User:Ow0cast]] to [[User:Owuh]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" wikitext text/x-wiki ==<nowiki>:</nowiki>3== see [[wikipedia:User:Ow0cast|my wikipedia userpage]] 8758f23e525f3459a1a70f4dd42bc5715a686c65 3566 3546 2025-08-11T03:24:04Z Atmois 13 Atmois moved page [[User:Owuh]] to [[User:Ow0cast]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" wikitext text/x-wiki ==<nowiki>:</nowiki>3== see [[wikipedia:User:Ow0cast|my wikipedia userpage]] 8758f23e525f3459a1a70f4dd42bc5715a686c65 2 804 3548 3260 2025-08-11T03:23:16Z Atmois 13 Atmois moved page [[User:Ow0cast/Editnotice]] to [[User:Owuh/Editnotice]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" wikitext text/x-wiki <templatestyles src="Module:Mbox/styles.css"></templatestyles> <div class="mbox mbox-med"><div class="mbox-title"><div class="mbox-icon metadata">[[File:OOjs UI icon alert.svg|14px|link=]]</div><big><big>Unauthorized editing of this page may result in in being [[wikipedia:WP:TROUT|slapped with a trout]]</big></big><br> </div></div> 9700d4d72ded82acbb923f09b6c3b214b4342af4 3567 3548 2025-08-11T03:24:04Z Atmois 13 Atmois moved page [[User:Owuh/Editnotice]] to [[User:Ow0cast/Editnotice]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" wikitext text/x-wiki <templatestyles src="Module:Mbox/styles.css"></templatestyles> <div class="mbox mbox-med"><div class="mbox-title"><div class="mbox-icon metadata">[[File:OOjs UI icon alert.svg|14px|link=]]</div><big><big>Unauthorized editing of this page may result in in being [[wikipedia:WP:TROUT|slapped with a trout]]</big></big><br> </div></div> 9700d4d72ded82acbb923f09b6c3b214b4342af4 2 770 3550 3119 2025-08-11T03:23:16Z Atmois 13 Atmois moved page [[User:Ow0cast/Sandbox1.css]] to [[User:Owuh/Sandbox1.css]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" css text/css .ambox { border: 1px solid #a2a9b1; /* @noflip */ border-left: 10px solid #36c; /* Default "notice" blue */ background-color: #fbfbfb; box-sizing: border-box; } /* Single border between stacked boxes. Take into account base templatestyles, * user styles, and Template:Dated maintenance category. * remove link selector when T200206 is fixed */ .ambox + link + .ambox, .ambox + link + style + .ambox, .ambox + link + link + .ambox, /* TODO: raise these as "is this really that necessary???". the change was Dec 2021 */ .ambox + .mw-empty-elt + link + .ambox, .ambox + .mw-empty-elt + link + style + .ambox, .ambox + .mw-empty-elt + link + link + .ambox { margin-top: -1px; } /* For the "small=left" option. */ /* must override .ambox + .ambox styles above */ html body.mediawiki .ambox.mbox-small-left { /* @noflip */ margin: 4px 1em 4px 0; overflow: hidden; width: 238px; border-collapse: collapse; font-size: 88%; line-height: 1.25em; } .ambox-speedy { /* @noflip */ border-left: 10px solid #b32424; /* Red */ background-color: #fee7e6; /* Pink */ } .ambox-delete { /* @noflip */ border-left: 10px solid #b32424; /* Red */ } .ambox-content { /* @noflip */ border-left: 10px solid #f28500; /* Orange */ } .ambox-style { /* @noflip */ border-left: 10px solid #fc3; /* Yellow */ } .ambox-move { /* @noflip */ border-left: 10px solid #9932cc; /* Purple */ } .ambox-protection { /* @noflip */ border-left: 10px solid #a2a9b1; /* Gray-gold */ } .ambox .mbox-text { border: none; /* @noflip */ padding: 0.25em 0.5em; width: 100%; } .ambox .mbox-image { border: none; /* @noflip */ padding: 2px 0 2px 0.5em; text-align: center; } .ambox .mbox-imageright { border: none; /* @noflip */ padding: 2px 0.5em 2px 0; text-align: center; } /* An empty narrow cell */ .ambox .mbox-empty-cell { border: none; padding: 0; width: 1px; } .ambox .mbox-image-div { width: 52px; } @media (min-width: 720px) { .ambox { margin: 0 10%; /* 10% = Will not overlap with other elements */ } } @media print { body.ns-0 .ambox { display: none !important; } } 79b3da455473ad263f5d5f5d0e9f99c487935c52 3568 3550 2025-08-11T03:24:04Z Atmois 13 Atmois moved page [[User:Owuh/Sandbox1.css]] to [[User:Ow0cast/Sandbox1.css]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" css text/css .ambox { border: 1px solid #a2a9b1; /* @noflip */ border-left: 10px solid #36c; /* Default "notice" blue */ background-color: #fbfbfb; box-sizing: border-box; } /* Single border between stacked boxes. Take into account base templatestyles, * user styles, and Template:Dated maintenance category. * remove link selector when T200206 is fixed */ .ambox + link + .ambox, .ambox + link + style + .ambox, .ambox + link + link + .ambox, /* TODO: raise these as "is this really that necessary???". the change was Dec 2021 */ .ambox + .mw-empty-elt + link + .ambox, .ambox + .mw-empty-elt + link + style + .ambox, .ambox + .mw-empty-elt + link + link + .ambox { margin-top: -1px; } /* For the "small=left" option. */ /* must override .ambox + .ambox styles above */ html body.mediawiki .ambox.mbox-small-left { /* @noflip */ margin: 4px 1em 4px 0; overflow: hidden; width: 238px; border-collapse: collapse; font-size: 88%; line-height: 1.25em; } .ambox-speedy { /* @noflip */ border-left: 10px solid #b32424; /* Red */ background-color: #fee7e6; /* Pink */ } .ambox-delete { /* @noflip */ border-left: 10px solid #b32424; /* Red */ } .ambox-content { /* @noflip */ border-left: 10px solid #f28500; /* Orange */ } .ambox-style { /* @noflip */ border-left: 10px solid #fc3; /* Yellow */ } .ambox-move { /* @noflip */ border-left: 10px solid #9932cc; /* Purple */ } .ambox-protection { /* @noflip */ border-left: 10px solid #a2a9b1; /* Gray-gold */ } .ambox .mbox-text { border: none; /* @noflip */ padding: 0.25em 0.5em; width: 100%; } .ambox .mbox-image { border: none; /* @noflip */ padding: 2px 0 2px 0.5em; text-align: center; } .ambox .mbox-imageright { border: none; /* @noflip */ padding: 2px 0.5em 2px 0; text-align: center; } /* An empty narrow cell */ .ambox .mbox-empty-cell { border: none; padding: 0; width: 1px; } .ambox .mbox-image-div { width: 52px; } @media (min-width: 720px) { .ambox { margin: 0 10%; /* 10% = Will not overlap with other elements */ } } @media print { body.ns-0 .ambox { display: none !important; } } 79b3da455473ad263f5d5f5d0e9f99c487935c52 2 774 3552 3144 2025-08-11T03:23:16Z Atmois 13 Atmois moved page [[User:Ow0cast/TemplateAlertMedium]] to [[User:Owuh/TemplateAlertMedium]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" wikitext text/x-wiki {{#invoke:mbox|mbox | icon = OOjs UI icon alert.svg | title = {{{title|}}} | text = {{{text|}}} | extraclasses = mbox-med }} 890f96c6ba914d9de960ec0904f26dc8757cb142 3569 3552 2025-08-11T03:24:04Z Atmois 13 Atmois moved page [[User:Owuh/TemplateAlertMedium]] to [[User:Ow0cast/TemplateAlertMedium]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" wikitext text/x-wiki {{#invoke:mbox|mbox | icon = OOjs UI icon alert.svg | title = {{{title|}}} | text = {{{text|}}} | extraclasses = mbox-med }} 890f96c6ba914d9de960ec0904f26dc8757cb142 2 773 3554 3141 2025-08-11T03:23:16Z Atmois 13 Atmois moved page [[User:Ow0cast/TemplateAssistByEditing]] to [[User:Owuh/TemplateAssistByEditing]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" wikitext text/x-wiki You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} {{{action|editing}}}]</span> it. 349988b07048fb28e93b08995d21281a4e96df42 3570 3554 2025-08-11T03:24:04Z Atmois 13 Atmois moved page [[User:Owuh/TemplateAssistByEditing]] to [[User:Ow0cast/TemplateAssistByEditing]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" wikitext text/x-wiki You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} {{{action|editing}}}]</span> it. 349988b07048fb28e93b08995d21281a4e96df42 2 783 3556 3171 2025-08-11T03:23:17Z Atmois 13 Atmois moved page [[User:Ow0cast/TemplateIssueNoInfobox]] to [[User:Owuh/TemplateIssueNoInfobox]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" wikitext text/x-wiki {{User:Ow0cast/TemplateAlertMedium | title = This page is missing an infobox. {{User:Ow0cast/TemplateAssistByEditing|action=creating}} | text = This message means that this page does not have an infobox. An infobox is a panel in the top right corner of the article and contains key facts about a topic, such as the package manager for a distro or the language of a software TODO create index of infobox templates and link to it }} 9449e91e021d037a0872401172fcd308bacb0f9c 3571 3556 2025-08-11T03:24:05Z Atmois 13 Atmois moved page [[User:Owuh/TemplateIssueNoInfobox]] to [[User:Ow0cast/TemplateIssueNoInfobox]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" wikitext text/x-wiki {{User:Ow0cast/TemplateAlertMedium | title = This page is missing an infobox. {{User:Ow0cast/TemplateAssistByEditing|action=creating}} | text = This message means that this page does not have an infobox. An infobox is a panel in the top right corner of the article and contains key facts about a topic, such as the package manager for a distro or the language of a software TODO create index of infobox templates and link to it }} 9449e91e021d037a0872401172fcd308bacb0f9c 2 776 3558 3146 2025-08-11T03:23:17Z Atmois 13 Atmois moved page [[User:Ow0cast/TemplateIssueStub]] to [[User:Owuh/TemplateIssueStub]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" wikitext text/x-wiki {{User:Ow0cast/TemplateAlertMedium | title = This page is a stub. {{User:Ow0cast/TemplateAssistByEditing|action=expanding}} | text = This message means that this page has been deemed not long enough to provide meaningful coverage of its topic. }} 9f8a7033b3582169ba0a4bc9614e6d98fc408b19 3572 3558 2025-08-11T03:24:05Z Atmois 13 Atmois moved page [[User:Owuh/TemplateIssueStub]] to [[User:Ow0cast/TemplateIssueStub]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" wikitext text/x-wiki {{User:Ow0cast/TemplateAlertMedium | title = This page is a stub. {{User:Ow0cast/TemplateAssistByEditing|action=expanding}} | text = This message means that this page has been deemed not long enough to provide meaningful coverage of its topic. }} 9f8a7033b3582169ba0a4bc9614e6d98fc408b19 2 722 3560 2772 2025-08-11T03:23:17Z Atmois 13 Atmois moved page [[User:Ow0cast/common.css]] to [[User:Owuh/common.css]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" css text/css #p-coll-print_export, #footer-info-copyright, #footer-places, #footer-icons, #pt-prefswitch-link-on, #pt-prefswitch-link-anon, #editpage-copywarn, #editpage-copywarn2, #mw-history-searchform, #siteSub, #t-print, #n-contents, #t-specialpages, #feedlinks, .editpage-head-copywarn { display: none } a span { text-decoration: none; } 7d4f7c1f4cf3a16ca62bd17bc4d80503bc5166e8 3573 3560 2025-08-11T03:24:05Z Atmois 13 Atmois moved page [[User:Owuh/common.css]] to [[User:Ow0cast/common.css]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" css text/css #p-coll-print_export, #footer-info-copyright, #footer-places, #footer-icons, #pt-prefswitch-link-on, #pt-prefswitch-link-anon, #editpage-copywarn, #editpage-copywarn2, #mw-history-searchform, #siteSub, #t-print, #n-contents, #t-specialpages, #feedlinks, .editpage-head-copywarn { display: none } a span { text-decoration: none; } 7d4f7c1f4cf3a16ca62bd17bc4d80503bc5166e8 2 805 3562 3264 2025-08-11T03:23:17Z Atmois 13 Atmois moved page [[User:Ow0cast/sandbox]] to [[User:Owuh/sandbox]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" wikitext text/x-wiki {{padright:xyz|120}} d60f46c1e5fe40f1b0d94bddcb90ac271d429fbc 3574 3562 2025-08-11T03:24:05Z Atmois 13 Atmois moved page [[User:Owuh/sandbox]] to [[User:Ow0cast/sandbox]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" wikitext text/x-wiki {{padright:xyz|120}} d60f46c1e5fe40f1b0d94bddcb90ac271d429fbc 2 811 3564 3283 2025-08-11T03:23:17Z Atmois 13 Atmois moved page [[User:Ow0cast/sandbox2/]] to [[User:Owuh/sandbox2/]]: Automatically moved page while merging the account "Ow0cast" to "[[User:Owuh|Owuh]]" wikitext text/x-wiki hi c22b5f9178342609428d6f51b2c5af4c0bde6a42 3575 3564 2025-08-11T03:24:05Z Atmois 13 Atmois moved page [[User:Owuh/sandbox2/]] to [[User:Ow0cast/sandbox2/]] without leaving a redirect: Automatically moved page while renaming the user "[[User:Owuh|Owuh]]" to "[[User:Ow0cast|Ow0cast]]" wikitext text/x-wiki hi c22b5f9178342609428d6f51b2c5af4c0bde6a42 10 483 3576 3530 2025-08-11T04:08:31Z Madonuko 140 remove new lines wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[ATL:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>{{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]]}}</includeonly> <noinclude>{{/doc}}</noinclude> e2a066e266d5a6f1d767334db64b1817d4714c3f 0 436 3577 3339 2025-08-11T04:09:53Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/ adelielinux.org]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is a [[Linux Distributions|Linux distribution]], based on Alpine Linux. The distribution targets old and low end machines, like desktops and servers. == Base description == One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution uses the OpenRC init system for service management, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. d14c6b4ebc84cba2a680e9ec465af310ec799a97 0 2 3578 3328 2025-08-11T04:10:10Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[Category:Linux Distributions]] [[File:Arch_Linux_Minimal_Neofetch_Output.png|thumb|[[Neofetch]] on Arch Linux]] '''Arch Linux''' is an independent rolling release [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. Arch Linux is kept up-to-date by regularly updating the packages of the system. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages. <code>makepkg</code> is part of the ''pacman'' package. === Installation === The Arch Linux website provides a downloadable ISO image that can be flashed onto a bootable drive. The operating system can be installed by following the [https://wiki.archlinux.org/title/Installation_guide Installation Guide] or by using the included installation script, archinstall. ==== Arch Installation Script ==== This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots. * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX. == References == <references /> 66715f7ba48b8c480e680d648c56ce96df66b65e 0 228 3579 3374 2025-08-11T04:10:20Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] {{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}}The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. [[Package|Packages]] that enter the extra repository can be directly installed with pacman.<ref name=":0" /> === How does it work? === The Arch User Repository or the AUR, unlike your regular repository, '''does not host made packages''' but rather it hosts PKGBUILDs that can be used to make packages, these PKGBUILDs contain metadata at the top and mainly two functions/methods: * <code>prepare()</code> : This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code> : This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. The surprising part about the AUR is that most packages do not need to follow this style, the packages can just directly copy configuration and binary files directly to their respective places without requiring to make a package. In fact because of the flexibility of AUR packages, you can make your own package by just using a package converter and cloning some package not made for Arch Linux and just convert the package into an Arch-compatible one. It sure works! You can even package apps by manually editing the files of a package and just use that. Unlike any other packaging format, PKGBUILDs can be installed without root too because they are indeed just scripts. It is however suggested to properly read the PKGBUILDs you get from the AUR for your own safety. === Installation of packages === On this page, we use the officially recommended method, though you can also install packages from the Arch User Repository with AUR helpers. While these tools can simplify the process and save time, they may introduce security risks and potential system instability if not used carefully. To start, you must be on an Arch Linux system and install the following packages: * <code>git</code> : This will be used to clone a package from the AUR. * <code>base-devel</code> : This should be probably installed but if it isn't, you must do. This gives us the tools to make PKGBUILDs. You can [https://aur.archlinux.org/packages?O=0&K= search the AUR] and choose your package, we will take the <code>visual-studio-code-bin</code> package as an example. You can pick any package you like and just replace the name. To install, follow these steps: * <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code> : This will clone the package from the AUR and will be stored in your current directory. * <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. * <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, AUR helpers have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, pacman is still required as these helpers essentially use pacman to perform their tasks. === Package Naming === All packages have either one of three suffixes: * <code>-bin</code> : These packages are pre-compiled and are not built by source. * <code>-git</code> : These packages are generally not recommended as they are unstable packages and are not intended for regular use however they can have new features or bug fixes. * No Suffix or other suffix : These packages are stable packages where they have been tested and are proven stable. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>[https://wiki.archlinux.org/title/PKGBUILD PKGBUILD], ArchWiki, 2025-06-12 (Accessed: 2025-08-09)</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>[https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions Creating packages], ArchWiki, 2025-06-13 (Accessed: 2025-08-09)</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>[https://wiki.archlinux.org/title/Namcap namcap], ArchWiki, 2025-06-16 (Accessed: 2025-08-09)</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability. == References == <references /> 7f627473a7b0317655a875b176fcc28a5828ed76 0 250 3580 3375 2025-08-11T04:10:30Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Instructions need to be split onto their own page under the Guides namespace}}{{Cleanup|Incomplete page}}[[Category:Guides]] [[File:NVIDIA - Hopper Architectures, Internals.png|thumb|The internals of an NVIDIA H100 Unit<ref>[https://developer.nvidia.com/blog/nvidia-hopper-architecture-in-depth/ NVIDIA Hopper Architecture In-Depth | NVIDIA Technical Blog], Michael Andersch, Greg Palmer, Ronny Krashinsky, Nick Stam, Vishal Mehta, Gonzalo Brito and Sridhar Ramaswamy, 2022-03-22 (Accessed: 2025-08-09)</ref>]] Due to the fact that Linux runs 91.5% of supercomputers and is used frequently for professional tasks,<ref>Elad, Barry. ''Linux Statistics 2024 by Market Share, Usage Data, Number Of Users and Facts.[https://www.enterpriseappstoday.com/stats/linux-statistics.html]''</ref> '''Artificial Intelligence''' (AI) is used widely on [[Linux]] for not only proprietary applications and usage, but also is heavily used for [[FLOSS]] applications of such technologies. Such examples include voice changers, image generators, '''Large Language Models''' (LLMs), and much more. If you are feeling frustrated or confused, this is a guide on how to not only yield results on '''NVIDIA''' cards - commonly used in the AI industry - but also on '''Advanced Micro Devices'''' (AMD) '''[https://www.amd.com/en/products/software/rocm.html ROCm]-capable Graphics Processing Units''' (GPU). Both drivers have the capability to run AI applications, yet also depends on the developers' and project's support for such technologies. == Ana/Miniconda Setup == While not required, it is heavily recommended to use ''conda'' to manage Python libraries required by various machine learning and artificial intelligence projects from places like GitHub and Hugging Face. Conda exists as a distinct virtual environment separate from the native distribution's Python packages. Users may specify version number and install additional plugins as well as packages within an environment utilizing conda. It is recommended to read the Linux setup for Miniconda on their [https://www.anaconda.com/docs/getting-started/miniconda/install#linux official website]. The install for Miniconda is very unorthodox compared to installing other packages on a Linux system - be mindful. == Stable Diffusion Setup - WebUI (Forge) == [[File:Cat.png|thumb|A cat generated using FLUX.1 [schnell].]] According to the project's main page, the Stable Diffusion WebUI is a "web interface for Stable Diffusion" in order to generate images using prompts or image-to-image generation.<ref>AUTOMATIC1111, ''stable-diffusion-webui''. Main Page[https://github.com/AUTOMATIC1111/stable-diffusion-webui]</ref> Stable Diffusion WebUI Forge is a version of Stable Diffusion WebUI that offers additional support for FLUX.1 [dev] and FLUX.1 [schnell] models. For some users, using the Forge version may result in greater stability using FLUX as opposed to the vanilla version. Simply clone the Forge repository:<syntaxhighlight lang="bash"> git clone https://github.com/lllyasviel/stable-diffusion-webui-forge/issues </syntaxhighlight>...install required pip packages:<syntaxhighlight lang="bash"> pip3 install -r requirements.txt </syntaxhighlight>...and run the program:<syntaxhighlight lang="bash"> python3 launch.py </syntaxhighlight> ==== Extra notes ==== ===== Run options/flags ===== It is advisory to set additional launch parameters for better performance, e.g. using '''xformers''' for optimization or to specify a certain directory where models are stored. You can place these in a separate xxx.sh file to run instead of having to copy-and-paste large strings - here is an example:<syntaxhighlight lang="bash"> python3 launch.py --listen --xformers --enable-insecure-extension-access --cuda-malloc --port 7860 --vae-dir=/run/media/jennaannilyn/Pikmin3/models/vae --ckpt-dir=/run/media/jennaannilyn/Pikmin3/AI/ --lora-dir=/run/media/jennaannilyn/Pikmin3/AI/models/loras --no-half-vae </syntaxhighlight> === Installing and using Ollama on Linux === [[File:Ollama.png|thumb|Ollama says hi to ATL.]] According to Ollama's main page, Ollama is used to run open-source/open-weight, locally hosted Large Language Models. == w-okada's voice changer == [[File:W-okada voice-changer - Diagram.png|thumb|A diagram of how w-okada functions at the high-level. <ref>[https://github.com/w-okada/voice-changer GitHub - w-okada/voice-changer: リアルタイムボイスチェンジャー Realtime Voice Changer], w-okada, 2022-08-09 (Accessed: 2025-08-09)</ref>|left]] According to w-okada's documentation in English, and as implied by the name of the repository, it is an AI-powered "voice changer" tool.<ref>GitHub, ''voice-changer''[https://github.com/w-okada/voice-changer]</ref> There are numerous uses for this: for simple enjoyment, for music covers, and for anonymity, w-okada as a voice changer is an extremely useful utility. ==== NVIDIA setup ==== Setup for NVIDIA cards is particularly straightforward, especially on [[Arch Linux]] where drivers are equally as abundant as they are functionally sufficient for this application. If you are considering investing in or using an existing NVIDIA card: {| class="wikitable mw-collapsible" |+Functionality and Post Setup !4 GB VRAM cards or '''LESS''' !''<u>You will likely struggle with using w-okada at times below 4 GB (2 GB, 1 GB, etc.) in hearing glitches and a lot of slowness in transmission of your voice - input - and the new voice - output.</u>'' * 1 GB - Likely entirely unusable or extremely slow. Untested. * 2 GB - Slow and not useful for real-time computation, may have better usage as a Secondary/Dual GPU (potential guide here) for other applications or usage where such processing is not needed in a real-time scenario. Untested. * 4 GB - Very slow and buggy when used as your primary, sole Dedicated GPU. However, you '''will likely have an ideal experience''' when using '''Dual GPUs''' and can reach up to or around 64-48 Chunk Size. '''TESTED (Arch Linux, nvidia/nvidia-dkms on 32 GB RAM and an NVIDIA GTX 1050 Ti GPU with an AMD 5600X Processor - will verify).''' |- !'''8 GB VRAM EXACT''' !More than often, 8 GB as an '''extra or dual GPU''' is sufficient in order to get satisfactory results at reasonable speeds (100-250 ms, average). ('''SEMI-TESTED''') * '''DUAL -''' In this case, '''you must make sure that, for dual NVIDIA setups, you reinstall your drivers if you are using a brand-new card!''' This is to prevent extreme overheating and fan noise. Otherwise, there should be no further concerns. * '''SINGLE -''' On non-GPU intensive applications, response time should lean towards the latter half of usual speeds. However, it will have comparable experience to lower end cards running more demanding software. '''Partition your resources.''' |- !'''12 GB or MORE''' !Considering the general trend of artificial intelligence, '''12 GB of VRAM is ideal.''' ('''TESTED - GIGABYTE GeForce RTX 3060 12 GB''') '''12 GB''' of VRAM should handle heavier workloads and other programs simultaneously well, and beyond is sufficient for best performance. * It may be redundant to have such a large amount of VRAM for this task, however, if it is a '''dual GPU, c'''onsidering cost, it is likely better to stay with an 8 GB model. |} NVIDIA cards generally seem to get the same performance as they do on Windows for Linux voicechanger users. === Setup === Clone the voicechanger repository:<syntaxhighlight lang="bash"> git clone https://github.com/w-okada/voice-changer </syntaxhighlight>'''(Using Conda):''' Assuming you are in a blank ''base'' environment, create a new environment running Python 3.10.6, ideally ('''this is because of compatibility with w-okada'''): <syntaxhighlight lang="bash"> conda create --name voicechanger --python=3.10.6 </syntaxhighlight>'''Make sure you have installed NVIDIA drivers for your specific distribution. Consult their respective wiki pages for more info.''' At this point, you want to activate your voicechanger environment:<syntaxhighlight lang="bash"> conda activate voicechanger </syntaxhighlight>...and cd into the '''server''' directory, assuming you are in the directory of which you have cloned the repository into:<syntaxhighlight lang="bash"> cd voice-changer/server </syntaxhighlight>Your first run will require you to install the requirements file:<syntaxhighlight lang="bash"> pip install -r requirements.txt </syntaxhighlight>After installing, run MMVCServerSIO.py:<syntaxhighlight lang="bash"> python3 MMVCServerSIO.py </syntaxhighlight> ==== The Deiteris Fork ==== Some users may prefer Deiteris's version, which may offer extra precision and performance for more advanced users. The process is almost identical, except that you must clone his fork:<syntaxhighlight lang="bash"> git clone https://github.com/deiteris/voice-changer </syntaxhighlight>...while consequently running a different Python command:<syntaxhighlight lang="bash"> python3 ./main.py </syntaxhighlight> == References == b92ea5d9929eecb6e2c3191db9edbebbf933bc7e 0 274 3581 3501 2025-08-11T04:11:00Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs Citations}} {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''', also known simply as '''Artix''', is a Linux distribution based on [[Arch]] that focuses on providing alternative init systems to systemd . It maintains high compatibility with Arch Linux while offering users the freedom to choose their preferred init system. == History == Artix Linux emerged from the Arch-OpenRC and Manjaro-OpenRC projects, officially launching in 2017 as a response to Arch Linux's adoption of systemd as its only init system. The distribution aims to provide a systemd-free experience while maintaining the principles of simplicity and user-centricity that Arch Linux is known for. == Features == === Init System Options === Artix supports multiple init systems: * OpenRC - A dependency-based init system from Gentoo * runit - A cross-platform Unix init scheme with service supervision * s6 - A suite of programs for process supervision * dinit - A service manager and init system designed to be simple and portable === Package Management === Artix uses [[Pacman]] as its package manager and maintains its own repositories alongside converted Arch Linux packages. The distribution provides several package repositories: * System repositories (specific to each init system) * Universe repository (containing converted Arch packages) * Galaxy repository (Artix-specific packages) === Installation === The distribution offers several installation methods: * Live ISOs with various desktop environments * Base ISOs for minimal installations * OpenRC, runit, dinit, and s6 variants of each ISO == Philosophy == Artix adheres to the KISS principle (Keep It Simple, Stupid) inherited from Arch Linux while emphasizing: * Init system freedom * System transparency * User control * Minimal [[bloat]] * Rolling release model == Package Compatibility == While maintaining high compatibility with Arch Linux packages, some modifications are necessary for systemd-dependent packages. The Artix team maintains: * Native packages built specifically for Artix * Converted Arch packages modified to work without systemd * Scripts and tools to help users convert systemd-dependent packages == Community == Artix Linux maintains its own: * Forums for user support and discussion * Wiki documentation * Package repositories * Development team == System Requirements == * x86_64 architecture * Minimum 512 MB RAM (2 GB recommended) * Minimum 2 GB storage (20 GB recommended) * Basic knowledge of command line operations * Understanding of Linux system administration c8c5fff2d22e227d904e28a98eb0e42334a1c88a 0 792 3582 3235 2025-08-11T04:11:20Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Programming Languages]] [[File:Motorola 6800 Assembly Language.png|thumb|Assembly code for the [[wikipedia:MC6800|Motorola MC6800]]]] An '''assembly''' language is a low-level machine language that uses symbolic instructions rather than raw binary coding to communicate directly with a computer's hardware, making it easier for humans to read. Unlike high-level programming languages that tend to restrict direct access to your system, an '''assembly''' language offers direct access to the system's architecture, allowing full control over the system, processor, memory and other hardware components inside the system. Each '''assembly''' language is specific to an architecture, those include but are not limited to: x86, ARM or RISC-V. The language uses something called '''"mnemonics",''' which are short textual codes that represent specific machine code instructions. For example, instead of using 10110000, a programmer might write MOV AL, 0 to perform the same operation. An '''assembly''' language is very fast, but won't get you anywhere due to it's complexity and lack of features. One might be more interested to look into something like [[C]] or [[C++]] for that kind of fast, optimized language. 6c00212cb50e246e315292a846d77af06dab293c 0 569 3583 2692 2025-08-11T04:13:51Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Mascots]] {{Cleanup|Incomplete page}} {{MascotInfobox | title = Beastie (BSD Daemon) | image = [[File:Daemon-phk.svg|borderless]] | caption = Beastie, the BSD mascot }} Beastie is the mascot of [https://freebsd.org/ FreeBSD and BSD] Beastie is a red devil (daemon) who wears green sneakers and holds a yellow trident. b9f3aff3ccba7d57a7bb41071b78589b475403b6 0 166 3584 2937 2025-08-11T04:14:01Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] A term commonly used across any Linux community,<ref>[https://www.youtube.com/watch?v=LxuYnFD7brY TechOverTea] imported on 17th June 2025</ref> "bloat" is commonly used to describe "unwarranted or excessive growth or enlargement" in the most universal sense for day-to-day life.<ref>Merriam-Webster Dictionary. [https://www.merriam-webster.com/dictionary/bloat]</ref> Within the realm of [[Linux]] and programming, "bloat" often refers to unnecessary tooling, code, applications, algorithms, etc. that can severely or at least noticeably impact the performance of a system.<ref>[https://www.techtarget.com/searchsecurity/answer/How-can-we-detect-and-uninstall-bloatware "What is Bloatware?"] TechTarget.com ,Imported 17th June 2025</ref> == References == <references /> accfa4e2e3cb94a48a27f9e8929372ad8818aabd 0 318 3585 3318 2025-08-11T04:14:11Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] {{Needs Citations}}The bootloader is a [[:Category:Software|program]] that's responsible for booting the system. Most of the time, it will have a menu to choose an option from, making it a boot manager. A bootloader is installed onto the boot partition of the computer during a [[Linux Distributions|distribution's]] installation process. Most of the times, boot partitions may need from 200 to 600MB of space to work properly. Most bootloaders also have theming capabilities, take, for example, [[GRUB]]. ead11280418a8d4ac7ebedfbc3c579674d5d8b7d 0 269 3586 3340 2025-08-11T04:14:21Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Desktop Environments]] {{Needs Citations}} {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/, buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], Budgie provides an easy to use Interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] == Features == '''Budgie Desktop View''' is a [[:Category:Software|software]] component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in C, and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. cc3aa67b4cef25928f169d28b645a476f5c3728f 0 414 3587 3377 2025-08-11T04:14:51Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Programming Languages]] C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970s, adopted by the majority of UNIX systems.<ref>[https://dl.acm.org/doi/10.1145/2509136.2509515 <span style="color:#fc493b">https://dl.acm.org/doi/10.1145/2509136.2509515 <sup>🍣403]</ref> The language was initially implemented by Dennis Ritchie whilst working at Bell Labs, and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie himself had produced his own C compiler for the DEC PDP-11, however this lacked the portability, problematic for adoption by the dynamically evolving UNIX landscape; this issue would later be addressed by companies distributing UNIX and corresponding C compilers and pre-processors for their respective machines and instruction sets.<ref>[https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance Freedom and Portability - by Babbage - The Chip Letter], Babbage, 2024-05-05 (Accessed: 2025-08-09)</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>[https://en.cppreference.com/w/c/language/history History of C], cppreference.com, 2025-05-27 (Accessed: 2025-08-09)</ref> Some popular compilers for the C programming language include GNU GCC, Clang, TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the Clang compiler toolchain, however, for example, [[Illumos]]<ref>[https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/ Illumos Gets A New C Compiler | Hackaday], Al Williams, 2023-07-16 (Accessed: 2025-08-09)</ref> and [[Plan 9]]<ref>[https://9p.io/sys/doc/compiler.html <span style="color:#fc493b">https://9p.io/sys/doc/compiler.html <sup>🍣DEAD?]</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>[https://smlfamily.github.io/Basis/ Standard ML Basis Library], AT&T and Lucent Technologies, 2004-04-12 (Accessed: 2025-08-09)</ref><ref>[https://doc.rust-lang.org/beta/std/index.html std - Rust], doc.rust-lang.org, 2025-08-05 (Accessed: 2025-08-09)</ref><ref>[https://ziglang.org/documentation/master/std/ Zig Documentation], ziglang.org, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html All Classes (Java Platform SE 8 )], docs.oracle.com, 2025-06-30 (Accessed: 2025-08-09)</ref><ref>[https://www.scala-lang.org/api/current/ Scala 3], , 2025-07-29 (Accessed: 2025-08-09)</ref><ref>[https://ocaml.org/manual/5.2/api/index.html The OCaml API], , (Accessed: 2025-08-09)</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>[https://www.musl-libc.org/faq.html musl FAQ], , 2018-02-21 (Accessed: 2025-08-09)</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>[https://wiki.musl-libc.org/compatibility musl libc - Compatibility], , 2025-04-26 (Accessed: 2025-08-09)</ref><ref>[https://www.fefe.de/dietlibc/FAQ.txt <span style="color:#fc493b">https://www.fefe.de/dietlibc/FAQ.txt <sup>🍣DEAD?]</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>[https://wiki.osdev.org/C_Library C Library], OSDev Wiki, 2024-06-24 (Accessed: 2025-08-09)</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>[https://nullprogram.com/blog/2017/03/30/ How to Write Portable C Without Complicating Your Build], Chris Wellons, 2017-03-30 (Accessed: 2025-08-09)</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as GNU Autotools, CMake, Meson, Zig's build toolchain among a plethora others, however for ideological<ref>[https://suckless.org/sucks/ software that sucks less | suckless.org software that sucks less], , 2025-05-29 (Accessed: 2025-08-09)</ref><ref>[https://www.interaction-design.org/literature/topics/keep-it-simple-stupid What is Keep It Simple, Stupid (KISS)?], Interaction Design Foundation - IxDF, 2016-06-05 (Accessed: 2025-08-09)</ref><ref>[http://harmful.cat-v.org/software/GNU/auto-hell GNU Auto*hell], , (Accessed: 2025-08-09)</ref> and practical<ref>[https://twdev.blog/2021/08/cmake/ Why CMake sucks? - twdev.blog], Tomasz Wisniewski, 2021-08-06 (Accessed: 2025-08-09)</ref><ref>[https://silverhammermba.github.io/blog/2023/01/06/gradle Gradle still sucks | Floating little leaves of code], Maxwell Anselm, 2023-01-06 (Accessed: 2025-08-09)</ref><ref>[https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system Stop the autoconf insanity! Why we need a new build system. – Freecode], Andrew McCall, 2003-06-21 (Accessed: 2018-11-18)</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>[https://github.com/Mercury-Language/mercury GitHub - Mercury-Language/mercury: The Mercury logic programming system.], Mercury-Language, 2013-08-09 (Accessed: 2025-08-09)</ref><ref>[https://github.com/NetBSD/src GitHub - NetBSD/src: Automatic conversion of the NetBSD src CVS module, use with care.], NetBSD, 2025-08-09 (Accessed: 2025-08-09)</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, meta-programming and structural components of a C code base; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>[https://docs.kernel.org/process/5.Posting.html 5. Posting patches — The Linux Kernel documentation], The kernel development community, 2025-07-27 (Accessed: 2025-08-09)</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS|open source]] code bases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995–2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial,<ref>[https://web.mit.edu/~simsong/www/ugh.pdf The UNIX-HATERS Handbook], Simson Garfinkel, Daniel Weise, and Steven Strassmann, 1994 (Accessed: 2025-08-09)</ref> many attribute issues regarding C to fragmentation and portability issues,<ref>[http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful #ifdef Considered Harmful, or Portability Experience With C News], Henry Spencer, (Accessed: 2025-08-09)</ref> lack of type safety and primitive resource access checks,<ref>[https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review <span style="color:#fc493b">https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review <sup>🍣403]</ref> poor administration on part of the C Language Working Group,<ref>[https://cor3ntin.github.io/posts/c/ The problem with C], cor3ntin, 2020-08-30 (Accessed: 2025-08-09)</ref> and overall worsening over time.<ref>[https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html C23 - What We Have To Suffer], Harry Fairhead, 2023-04-05 (Accessed: 2025-08-09)</ref><ref>[https://wiki.theory.org/YourLanguageSucks YourLanguageSucks], TheoryOrg, 2022-09-29 (Accessed: 2025-08-09)</ref> == References == <references /> 3ed2d2d6b43f8b16bcdaa85b3914f0b06cb67c92 0 433 3588 3319 2025-08-11T04:15:01Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] [[Category:User interfaces]] {{Needs Citations}}A '''CLI''' (Command-Line Interface) is a text-based interaction model in which users type commands as text strings to interact with an operating system or a program through a computer. Unlike a [[TUI]], which relies upon a pseudo-graphical form made of characters, an interface that is purely a command-driven one usually would issue output in the form of lines of text upon receiving user instructions. [[File:Unix shell.png|thumb|A Unix shell command prompt, an example of a CLI]] CLIs are often preferred by power users, system administrators, and developers for their efficiency, scriptability, and precise control over system operations. Common examples include: * Unix/Linux shells (sh, bash, zsh, fish) * Windows Command Prompt * PowerShell * Python's REPL (Read-Eval-Print Loop) The main advantages of CLIs include: * Resource efficiency (minimal system requirements) * Automation capability through scripting * Remote system administration * Precise control over system operations * Speed of execution for experienced users While CLIs can have a steeper learning curve compared to GUIs (Graphical User Interfaces) or TUIs, they remain fundamental to modern computing, particularly in server administration, software development, and system maintenance. == History == [[File:Edwind.png|thumb|CLI text editor Ed in a GUI terminal emulator window]] Command-line interfaces emerged in the 1960s with teleprinters like the Teletype Model 33 ASR, which replaced punch cards as the primary means of computer interaction. Early operating systems like Unix and MS-DOS were primarily accessed through CLIs, establishing conventions that persist in modern computing. [[File:Command com.png|thumb|The MS-DOS command prompt]] == Common Usage == CLI environments typically follow a standard pattern where: * The system displays a prompt (e.g., "$" for Unix-like systems) * Users type commands followed by arguments or options * The system executes the command and displays the output * The process repeats with a new prompt 4d5200a133bb2e4003ab9a7360e59260383dd07e 0 429 3589 3379 2025-08-11T04:15:21Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = CRUX | image = [[File: Crux.png]] | caption = The Official CRUX logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[pkgutils]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64 | website = [https://crux.nu/ crux.nu] }} CRUX is a lightweight, [[x86-64]] Linux distribution targeted at experienced Linux users. It focuses on simplicity and adheres to the [[KISS]] principle (Keep It Simple, Stupid). CRUX uses a tar.gz-based [[Package Manager|package management]] system, allowing users to build packages from [[source code]] <ref>[https://crux.nu/doc/prt-get%20-%20User%20Manual.html prt-get - User Manual], Johannes Winkelmann, 2003-08-09 (Accessed: 2025-08-09)</ref> with fine-grained control over compilation options. It does not use [[systemd]] as its init system, opting for a simpler init system based on BSD-style init scripts.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> Unlike other distributions, the primary goal of CRUX is not to be the most popular or to put as many features as possible into the system. The idea is rather to build a streamlined distribution, targetted at a specific audience which in turn gets a system without compromises. Some of the characteristics of CRUX are: * KISS (Keep It Simple, Stupid) concept, applied to both the system and the development process * Source based package installation using a ports system * Simplicity over automation * Targetted at experienced users with compact, to the point documentation * Native configurations over configuration abstraction layers * Up to date features and packages, however no bleeding edge software in the main repositories * Easy way to extend the system by yourself * Active community of contributors outside the core development team ==History== CRUX was founded by Per Lidén.<ref>[https://crux.nu/Profiles/PerLiden CRUX | Profiles / PerLiden], CRUX, 2011-01-04 (Accessed: 2025-08-09)</ref> The initial goal was to create a minimalist Linux distribution that was easy to understand and maintain.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> The focus has consistently been on providing a stable and efficient base system that users can customize to their specific needs. CRUX has had 27 documented releases <ref>[http://ftp.morpheus.net/pub/linux/crux/ Index of /pub/linux/crux/], , (Accessed: 2025-08-09)</ref>,from 0.9.7 to the current release, 3.8 ==Features== * '''Init system:''' CRUX uses a [[BSD]]-style init system<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref>, consisting of simple shell scripts. This contrasts with more complex init systems like systemd. This design choice emphasizes simplicity and control for the user. * '''Package management:''' CRUX uses a [[ports]]-based package management system. This means that packages are defined by "Pkgfiles," which contain instructions for downloading, compiling, and installing software from source code. This approach allows users to customize compilation options and optimize software for their specific hardware.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> This is similar in concept to FreeBSD Ports or Gentoo's Portage. * '''KISS principle:''' CRUX strongly adheres to the KISS principle. This means that the distribution is designed to be as simple as possible, avoiding unnecessary complexity. This philosophy is reflected in the init system, package management, and overall design of the system.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> * '''No systemd:''' CRUX notably does not use systemd. This is a deliberate choice to maintain simplicity and avoid the complexity associated with system.<ref>[https://crux.nu/Main/About CRUX | Main / About], CRUX, 2024-02-18 (Accessed: 2025-08-09)</ref> == Ports System == CRUX uses a BSD-style ports system, revolving around the packaging system pkgutils, each port contains a Pkgfile which tells pkgmk or prt-get what to do, it is a relatively simple process, that involves fetching the source declared in the Pkgfile (Or if the file is already present and matches the checksum, it extracts it.), Following the compilation steps declared in the Pkgfile while using the optimizations and arguments declared in ```/etc/pkgmk.conf```, this part is declared in the ```build()``` section of the Pkgfile, since a Pkgfile is essentially a BASH script, it can be edited by the end user to match their own needs. <ref>[https://crux.nu/Main/Handbook3-8-Package CRUX | Main / Handbook3-8-Package], CRUX, 2025-05-10 (Accessed: 2025-08-09)</ref> == References == abd55394a10d8876caeb0f9e34a15e8bec4e6e0c 0 700 3590 2941 2025-08-11T04:15:31Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Calamares on Debian 10 screenshot.jpg|frameless]] | caption = Calamares Installer | title = Calamares | releasestatus = Maintained | lastrelease = 3.3.14 (Feb 20, 2025) | languages = [[C++]], [[Python]], [[QML]] | developers = Adriaan de Groot | website = [https://calamares.io/ calamares.io] }} Calamares is a distribution-independent system installer, with an advanced partitioning feature for both manual and automated partitioning operations. Calamares is designed to be customizable by distribution maintainers without the need for cumbersome patching, thanks to third-party branding and external modules support.<ref>https://github.com/calamares/calamares Calamares Github, 2025 (27th June 2025)</ref> == References == <references /> 7eefe83c3988c24313c408678dee395c60348f24 0 659 3591 2942 2025-08-11T04:16:01Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = ChromeOS | image = [[File:Chromium_Logo.svg|frameless]] | caption = ChromiumOs Logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Portage]] | defaultdesktops = Chromium, Aura Shell | usagetype = Desktop | architectures = x86_64, IA-32, ARM, ARM64 | website = [https://chromeos.google/ chromeos] }} ChromeOS (ChromiumOS) is a [[UNIX|Unix-Based]] [[Linux Distributions|Linux distribution]] designed and developed by Google in 2009. ChromeOS is completely open-source.<ref>http://source.chromium.org/chromiumos Official ChromeOS website, 2025 (imported 27th June 2025)</ref> == References == <references /> c12d48c05e68c2206f174c722c27f9f1d66c3d71 0 313 3592 2432 2025-08-11T04:17:26Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Desktop Environments]] [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] {{Needs Citations}} [https://github.com/linuxmint/cinnamon Cinnamon] is a desktop environment maintained by the [https://www.linuxmint.com/ Linux Mint] team. Forked from [[GNOME]] Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in [[JavaScript]], with core libraries being written in [[C]]. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === A "Spice" is Cinnamon's name for an add-on applet, desklet, theme, widget, and more. They can be found at the [https://cinnamon-spices.linuxmint.com/ Cinnamon Spices repository website]. == Cinnamon applications == Cinnamon uses the X-app suite, which are a set of apps forked from GNOME and changed to work across XFCE, Cinnamon and MATE. {| class="wikitable" |+The list of apps are the following: !Application !GNOME !X-apps equivalent |- |Text editor |Gedit |xed |- |Image viewer |Eye of GNOME (EoG) |xviewer |- |Image organizer |gthumb |pix |- |Media player |Totem |xplayer |- |Document editor |Atril |xreader |} == Starting Cinnamon == There are two main methods of starting Cinnamon: * Selecting "Cinnamon" from your preferred [[Display Manager]] ** If your session crashes or has graphical artifacts you should select "Cinnamon (software rendering) instead, which disables 3D acceleration * Modifying your [[Xinitrc]] to include <code>exec cinnamon-session</code> ca2787c67f09bd2b958598a01ab3dd8d2ed23e80 0 158 3593 3320 2025-08-11T04:17:36Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] {{Needs Citations}}{{Cleanup|Contrary to the page title, this page does not provide in-depth information for commands}}When using [[Linux]], sooner or later, there's a good chance you'll end up finding yourself in front of a [[TUI|terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a '''command'''. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include <code>echo</code>, <code>mv</code>, [[cat|<code>cat</code>]], etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with <code>sudo</code> followed with your original command. [[sudo]] tells your computer to ''do'' something as a ''super user'' which will allow you to bypass restrictions. It should be important to note that '''sudo is a separate package''' and may not be pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you will need to use something like <code>su</code> to log in as root and then run your command as root or install sudo as root. == Useful Commands == Furthermore, with commands you will likely need to include ''options'' that specify to the program how you want it to behave. One of the most common options is <code>--help</code>, which will usually tell program to list all of its options. An example would be as follows: cat --help In this case, the 'cat' utility would respond to this command with the following:<syntaxhighlight>Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines ...</syntaxhighlight>These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, <code>--help</code> is always there and ready. If not, you can always run [[man|<code>man</code>]] before a program similarly to how you would run <code>sudo</code>, and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a file to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory|working directory]] (Like shown) or you can provide a file from anywhere in the [[filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt The tilda sign <code>~</code>, in Linux and some other [[Operating System|operating systems]], expands to the full [[Directory Path|directory path]] of the current user's home folder. Here is what it would look like to type out the whole path: nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ e3bab91a5af585ac186bd14aee7212dd90c0ac21 0 179 3594 2029 2025-08-11T04:19:43Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Guides]] {{Work In Progress}} Not every install will be as flawless as a user will expect it to be, and they may encounter bugs for numerous reasons ranging from simple hardware differences to nuanced kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) === [[Linux on Apple Macintosh Devices|Linux on Apple Devices]] === If you use '''an Apple device,''' Linux may have a few issues running flawlessly on first install - '''this section details some steps you should consider taking if you have specific issues.''' === [[Artificial Intelligence on Linux]] === '''Covers w-okada, Stable Diffusion, Large Language Models, ROCm/CUDA with proper driver setup, anaconda/conda...''' 814bb2152b59a1f5ff0f9b9135251a8fbf2580b0 0 412 3595 3341 2025-08-11T04:20:05Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{Needs Citations}} {{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-org | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }} '''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. == Available Parameters == {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default (none unless specified) || [given parameter] |} == Trivia == * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ ^{<nowiki>[1]</nowiki>}] * [[Larry the Cow]] (<code>emerge --moo</code>) and Cowsay share the same ASCII art, [[Debian]]'s Larry ASCII arts don't. * There is a graphical version of this program called [https://www.doof.me.uk/xcowsay/ xcowsay]. f494b8e94942f4d50887e3b34a06dc0208bf5cad 0 272 3596 2943 2025-08-11T04:20:15Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Package Managers]] {{Cleanup|The article does not reflect the latest information on dnf5}}{{Cleanup|is that <code>dnf</code>'s importance is described in a pretty biased way, and some parts of this page feels somewhat AI-generated.}}{{Needs Citations}} {{SoftwareInfobox | image = [[File:DNF Command Line Interface.png|frameless]] | caption = Invoking <code>sudo dnf upgrade</code> on a terminal with <code>dnf4</code> | title = DNF | releasestatus = Maintained | lastrelease = <code>dnf5</code> 5.2.13.1 (2025-04-25) | languages = [[C++]] | developers = [[Fedora]] and Red Hat, et al. | website = [https://github.com/rpm-software-management/dnf5/ github.com/rpm-software-management/dnf5] }} '''DNF''', short for ''Dandified YUM'', is a software package manager for Linux distributions such as [[Fedora]], [[CentOS]], and [[RHEL]] (Red Hat Enterprise Linux). It was designed to be a better version of the traditional [[YUM]] (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other [[RPM]]-based distributions. === Development of DNF5 === The development of DNF5, the next-generation Fedora package manager, began in early 2020 as a complete rewrite of the existing DNF4 codebase to address architectural and performance limitations:<ref>[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NWSURJRGZAIIMNZJT244DHDPOG2PBQXZ/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> <blockquote> We've managed to drop a lot of redundant code across the whole DNF stack in the past years, but we have reached a point when it's nearly impossible to consolidate the code any further without breaking the API/ABI. Especially with PackageKit being dead<ref>[https://blogs.gnome.org/hughsie/2019/02/14/packagekit-is-dead-long-live-well-something-else/ PackageKit is dead, long live, well, something else], hughsie, 2019 (Accessed 2025-06-21)</ref>, we can't move with the old "libhif" API in libdnf, because making any bigger changes to PackageKit is clearly out of scope. </blockquote> The announcement of DNF5 development was made in March 2020, with a roadmap targeting major API changes and early development snapshots throughout 2020, aiming for inclusion in Fedora 34 and stable replacement of DNF4 by early 2021.<ref>[https://lwn.net/Articles/814066/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> Key motivations for DNF5's development included the need to modernize the codebase, which had become cluttered and difficult to maintain, and to move away from dependencies on Python and older APIs. The new design emphasized a fully featured package manager written primarily in C++ for improved performance, reduced resource usage, and a smaller install size compared to DNF4.<ref>[https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5#Benefit_to_Fedora Make DNF5 The Default], Jaroslav Mracek, 2022 (Accessed 2025-06-21)</ref> DNF5 also aimed to unify the software management tools in Fedora by replacing DNF and Microdnf, and providing a new daemon alternative to PackageKit.<ref name=":0">[https://ostechnix.com/dnf5-package-manager-introduction/ Introduction to DNF5: The Next-Generation Fedora Package Manager], Sk, 2025 (Accessed: 2025-06-21)</ref> DNF5 introduced a new core library (libdnf5), revamped plugin systems, enhanced modularity support, and a streamlined command-line interface with improved user experience. The development process was marked by an emphasis on openness, community involvement, and transparent upstream issue tracking to foster broader collaboration. By Fedora 38, DNF5 was available, and it became the default package manager in Fedora 41, fully replacing the older DNF.<ref name=":0" /> == Features == ==== Dependency Resolution ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== Transaction History ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== Modularity Dupport ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== Plugin System ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== Parallel Downloads ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== Package Groups ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: * Installing Packages: <code>dnf install <package_name></code> * Updating Packages: <code>dnf update</code> * Removing Packages: <code>dnf remove <package_name></code> * Listing Installed Packages: <code>dnf list installed</code> * Searching for Packages: <code>dnf search <keyword></code> * Managing Repositories: <code>dnf repolist</code>, <code>dnf config-manager</code> * Viewing Transaction History: <code>dnf history</code> == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. == References == a1f678e37781ae15483d525047378920623f4ac1 0 246 3597 2944 2025-08-11T04:20:25Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = | caption = | title = dpkg | releasestatus = Maintained | lastrelease = 1.21.22 / 24 May 2023 | languages = C, C++, Perl | developers = The Debian Project | website = [https://www.dpkg.org/ dpkg.org] }} '''dpkg''' (Debian Package) is the core software of the package management system in the [[Debian]] operating system and its derivatives. It is used to install, remove, and provide information about <code>.deb</code> packages. dpkg is a low-level tool. [[APT|APT (Advanced Package Tool)]] is more commonly used in practice as it is a high-level tool.<ref>Afia Zahin Oishi (December 6, 2023). [https://linuxsimply.com/linux-basics/package-management/package-manager-comparison/dpkg-vs-apt/ <nowiki>"Dpkg Vs Apt [What's the Difference Between Package Managers]"</nowiki>]. linuxsimply.com. LinuxSimply.</ref> == References == 361cb0ba9664a69c5cc6011c288dd4c9f27bef3a 0 254 3598 3382 2025-08-11T04:20:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm. == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == 9e3ec03c499d9270450c19d90fb3837815ea4164 0 182 3599 2946 2025-08-11T04:21:15Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, [[Xfce]], [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[Category:Linux Distributions]] [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a [[Linux Distributions|Linux distribution]] developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> == History == Debian adheres to the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> In 1997, the Debian Project established Software in the Public Interest as a nonprofit organization to provide ongoing financial support. However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> == Features == === Release Cycle === Debian maintains three primary development branches: * Stable - The current official release, recommended for production systems * Testing - The next planned stable release, featuring newer software versions * Unstable (Sid) - The rolling development branch where new packages are initially introduced === Package Management System === Debian uses the [[APT]] (Advanced Package Tool) built on top of [[dpkg]], featuring: * Over 59,000 ready-to-install software packages * Multiple repository sections (main, contrib, non-free) * Secure package verification through signed repositories * Sophisticated dependency resolution === Project Management === The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as: * The Debian Social Contract * The Debian Constitution * The Debian Free Software Guidelines === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[Window Manager|Window Managers]] instead of [[Desktop Environment|Desktop Environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /> == Installation == Debian provides multiple installation methods: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Live images for testing before installation * Architecture-specific installers * Cloud images for virtual deployment == References == <references /> 33ccb28553b2345bfba9d987988da91f0728332f 0 622 3600 3130 2025-08-11T04:21:25Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> {| class="wikitable" |+ !Desktop Environment !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from Razor-qt and LXDE components which were ported to [[Qt]]. |} df25c56833861a889b7f138e0d2bead4b2af6229 0 173 3601 2947 2025-08-11T04:21:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Incomplete page}} [[Category:Terminology]] [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager ('''GDM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a [[graphical user interface]] that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself.<ref>https://github.com/tvrzna/emptty GitHub, 2025 (Imported 02.07.2025)</ref> == References == dd31c0f521645d83b2ac807e84e1f302cee57c58 0 223 3602 3478 2025-08-11T04:22:25Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] {{Needs Citations}}{{Stub}}Distrohopping is the pattern of behavior whereby an individual may feel the desire to constantly seek for a new [[Linux Distributions|Linux distribution]]. This may be done for many reasons, including: * Productivity * Performance * Software Freedom (e.g. FSF approved distribution) * Ecosystem or Tooling (e.g. libc, [[Package Manager|package manager]], coreutils, [[Init System|init system]]) * Experimentation * Customization ... and many more. <ref name=":0">{{Cite|url=https://read.amazon.com/sample/B09781GYC5?clientId=share|title=Distro-Hopping, What, Why & How Explained! Ch 2.1|author=Steven Ovadia|year=2016|accessdate=August 9}}</ref> This behavior is increasingly common in [[Linux]] communities, notably seen in new-to-linux users who are motivated by curiosity, making ambitious decisions with little regard for the implications. This behavior can also be considered counter-intuitive for some, whereby a user is suffering reduced productivity and increased technological issues due to: * Discontinuity between Linux distributions (e.g. Debianisms, package managers, init systems) * Opinionated design philosophies (e.g. Nix, Guix, Fedora Atomic) * Additional configuration needs (e.g. minimalist distributions like [[Arch Linux|Arch]], Void, Crux and [[Gentoo]]) ... and many many more. <ref name=":0" /> Not all distrohopping is considered harmful however. There is a mountain of evidence to suggest that trying out new things can help engage and excite individuals, not to mention the educational and experiential growth it is capable of providing. {{Citation needed}} '''It is not okay to insult, belittle or demean others based on their tendencies to "hop" between Linux distributions'''. If one so wishes to do so, avoiding distrohopping is complex and multifaceted in nature, it will be different from person-to-person. Some may require self-disciplinary techniques in order to reduce motivation to distrohop, these may include: * "Distro Challenges", i.e. dedicating a given period to a '''singular''' distribution * Contributing to Linux distributions upstream * Familiarizing yourself with a distributions community (e.g. through IRC, Matrix, Discord, Mailing lists, Zulip) * Making personal commitments to a Linux distribution financially (e.g. Liberapay, GitHub sponsors, FSF donations, Patreon) These techniques may help to enforce and individual's attachment to a particular distribution, allowing them to find distro to call ''home''. c29a37cf5a0925fb7e70e26d36cd53c311f16a35 0 736 3603 3383 2025-08-11T04:22:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[category:software]] [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html ed], The IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> ed was part of the original Unix operating system from 1969.<ref>[https://man.cat-v.org/unix-1st/1/ed ed(1)], Unix First Edition Manual Page, 1971-11-03 (Accessed: 2025-08-09)</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>[https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html Shell & Utilities: Detailed Toc], IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s s/regexp/replacement command was inherited from ed.<ref>[https://www.gnu.org/software/ed/manual/ed_manual.html GNU 'ed' Manual], GNU, 1993-08-09 (Accessed: 2025-08-09)</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor vi, whose variants remain some of the most popular TUI text editors.<ref>[https://ex-vi.sourceforge.net/ex.html ex.1], 2005-03-24 (Accessed: 2025-08-09)</ref><ref>[https://ex-vi.sourceforge.net/vi.html vi.1], 2005-03-24 (Accessed: 2025-08-09)</ref> == References == 697ac1ad5bd225caaee47c826004645517d0ec08 0 623 3604 3476 2025-08-11T04:22:45Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = EndeavourOS | image = [[File:EndeavourOS Logo.svg|Thumb]] | caption = The Endeavour OS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[Cinnamon]], [[I3]], [[GNOME]], [[KDE Plasma]], [[LXDE]], [[LXQt]], [[MATE]], [[Xfce]], [[Budgie]] | usagetype = Desktop | architectures = x86_64, AArch64 | website = [https://endeavouros.com endeavouros.org] }} '''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">[https://endeavouros.com/ Home - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>[https://endeavouros.com/about-us/ About us - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning [[Arch Linux]] fundamentals. === Installation === EndeavourOS provides an ISO with the [[Calamares]] installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with [[Arch Linux]], meaning it uses Arch's official repositories directly and adheres closely to Arch's philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * [[AUR]] Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate [[AUR]] package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * [[Pacman]] Compatibility: Fully compatible with Arch's [[pacman]] package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for [[Arch Linux]] are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla [[Arch]], or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the [[AUR]], as well as EndeavourOS-specific themes and utilities.<ref>[https://repo.c48.uk/endeavouros/repo/endeavouros/ Index of /endeavouros/repo/endeavouros/] (Accessed: 2025-08-09)</ref> This is simply a [[pacman]] repository that can simply be added to any [[Arch Linux]] system if desired. == References == d786d7f0448f7d32de84fc5885cf61fd58dd3125 0 650 3605 2950 2025-08-11T04:23:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Desktop Environments]] {{SoftwareInfobox | image=[[File:Enlightenment logo.svg|Enlightenment_logo]] | caption = Enlightenment logo | title=Enlightenment | releasestatus=Maintained | lastrelease=0.27.1, March 17, 2025 | firstrelease=0.13.2, January 18, 1998 | languages=[[C]], [[ELF]] | developers=Enlightenment Foundation | website=[https://www.enlightenment.org/, enlightenment.org/] }} [https://www.enlightenment.org/ Enlightenment] is a [[Desktop Environments|Desktop Environment]] and [[Window Manager]] for [[Linux]] and other [[Unix|Unix-like]] [[Operating System|operating systems]], such as [[BSD]] derivatives.<ref name=":0">[https://www.enlightenment.org/about Enlightenment About Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref>. Originally created by Carsten Haitzler in the late 90s with the philosophy "that users should be given as much control as possible."<ref>[https://www.enlightenment.org/about-enlightenment| About Enlightenment Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref> === Features === Enlightenment has many key features as a [[graphical desktop]] including its own set of graphical and system libraries known as the "Enlightenment Foundation Libraries". Designed to be portable and efficient while also being easy to use on various devices including touch devices even being used in Samsung devices.<ref name=":0" /> * Support for both [https://www.x.org/wiki/ X11] and experimental [https://wayland.freedesktop.org/ Wayland] support. * A hand optimized software rendering compositor. * Very low memory requirements. * The ability to configure everything graphically. * Touch gestures * Window Management Features ** Virtual desktops. ** Optional window tiling. ** Customizable mouse and keyboard bindings. ** And many more modules. == References == <references /> 4ebe7665887485a73e3ecff67636657c6fad7cde 0 782 3606 3166 2025-08-11T04:23:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Widget system]] Eww (Elkowars Wacky Widgets) is a standalone widget system made in Rust by Elkowar that allows to implement custom widgets in any window manager. Configuration is done through a yuck and a scss (or css) file.<ref>{{Cite|url=https://github.com/elkowar/eww|title=original repo|author=Elkowar}}</ref> 8ba14e7c108b658b1639a3f432bab96038d095f3 0 756 3607 3385 2025-08-11T04:24:06Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DISPLAYTITLE:ex}} [[category:software]] [[File:Exedit.png|thumb|nvi text editor in Ex mode]] Ex is a text editor developed for [[UNIX|Unix]] systems in 1977 as a modified version of em, which was an improved version of the original Unix text editor [[ed]].<ref>[https://man.freebsd.org/cgi/man.cgi?query=vi&manpath=FreeBSD+14.3-RELEASE vi], The FreeBSD Project, 2024-04-18 (Accessed: 2025-08-09)</ref><ref>[https://web.archive.org/web/20240621040052/https://www.groklaw.net/article.php?story=20050422235450910 Groklaw - The Daemon, the Gnu and the Penguin, Ch. 4 & 5 - by Peter H. Salus], Peter H. Salus, 2005-04-22 (Accessed: 2024-06-21)</ref> Like ed, ex is a line editor, meaning commands can only be executed on one line at a time. Ex was eventually modified into a screen editor and became [[vi]]. Modern versions of ex are rarely distributed on their own, but are rather line editor modes of vi text editors.<ref>[https://man.netbsd.org/ex.1 ex(1) - NetBSD Manual Pages], 3rd Berkeley Distribution, 2024-04-28 (Accessed: 2025-08-09)</ref> == References == 09f471e4e943f520d7fd51cf6118213ec5b84830 0 164 3608 3344 2025-08-11T04:24:36Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Guides]] {{Work In Progress}} The [[Linux]] community is abundant with awesome projects and various other guides worth checking out, Here's some great ones that we have found - keep in mind that, while these guides are very useful, they are not fully exhaustive. More than likely you discover new software every day! * Privacy is not an end goal, but a consistent journey that needs to be taken very seriously. ''Always'' seek help when in doubt and ensure you take everything with a grain of salt. ''Do not just blindly follow guides but use your own intuition!'' == Guides == * https://www.privacyguides.org/ - An essential guide to learning not just ''how'' to begin your privacy journey online but offers a comprehensive explanation of abstract privacy concepts that is simple to understand and by extension ''is assuredly not easy or quick -'' read with an open mind! ** https://awesome-privacy.xyz - More of a guide to tools you may find yourself wanting to use to enhance privacy, rather than an explanation. The next step from Privacy Guides, essentially. ** https://www.privacytools.io/ - Similar to Awesome Privacy, and offers a wide range of tools. This specific website is recommended very frequently. * https://brainfucksec.github.io/firefox-hardening-guide - A guide to "de-Mozilla" and security-harden Firefox. Assess whether or not this is a good option for you - ''similar to privacy, it is not an easy process.'' * https://rentry.co/fmhy-guides - General, yet extremely useful and even nuanced guides that you may find yourself needing for something very specific and hard to find on the internet. * https://github.com/luong-komorebi/Awesome-Linux-Software - Very extensive guide of not solely Linux software but mostly open-source software that has many use cases in mind. May be helpful in picking a flavor of Linux for your specific use cases. == Wikis == * https://wiki.archlinux.org/ for Arch Linux * https://wiki.gentoo.org/ for Gentoo * https://wiki.debian.org/ for Debian * https://fedoraproject.org/wiki/Fedora_Project_Wiki for Fedora * https://wiki.ubuntu.com for Ubuntu == Tools == * https://christitus.com/windows-tool/ - Used for debloating and removing telemetry from Windows. * https://alternativeto.net - A tool to find alternatives to popular software, both open-source and proprietary. * https://etcher.balena.io/ - An open-source tool to flash operating systems to an USB drive. 8edf1e3e8dddd4e820689b592f03f9099aa4e291 0 177 3609 3490 2025-08-11T04:25:06Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word, libre)<ref>https://en.wiktionary.org/wiki/libre Wikitionary. Wikimedia Foundation. Accessed June 4, 2024.</ref> and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, and distribute the software, modified or not, to everyone free of charge. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary, or nonfree software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == 69c431d8e810c5269ddd7e0ae806187f2d491f76 0 268 3610 3446 2025-08-11T04:26:54Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Command-line software]] [[Category:System information tools]] {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch running on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C (programming language)|C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch GitHub repository] }} '''Fastfetch''' is a cross-platform command-line utility for displaying system information, similar in purpose to [[Neofetch]]. It is primarily written in [[C (programming language)|C]] and is designed with a strong focus on speed and low resource usage. Fastfetch can display details about the [[Operating system|operating system]], hardware components, and installed software in a highly configurable format. The tool supports a wide range of modules, allowing users to customise the output to include information such as CPU, GPU, memory, storage, display resolution, kernel version, package count, and more. It is actively maintained and available for Linux, macOS, and Windows. == See also == * [[Neofetch]] * [[Screenfetch]] == References == <references /> cc1ce1434f4aeed760dac62f02ed07713bf022e5 0 217 3611 3371 2025-08-11T04:27:04Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}} [[Category:Linux Distributions]] [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[ https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref> == Release system == Fedora current follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], </nowiki>'''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</nowiki></ref> System upgrades are usually handled offline to prevent system breakage == The package management system == the Package manager [[dnf]] , is usually called with the following arguments * <code>sudo dnf up</code> --- updates system packages * <code>sudo dnf in <pkg names> <...></code> --- install new packages * <code>sudo dnf rm <pkg names> <...></code> --- remove packages * <code>sudo dnf system-upgrade --relesever=<rel></code> --- updates syetem version and packages<ref>[https://dnf.readthedocs.io/<nowiki> DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</nowiki></ref> == References == <references /> ac290bb6e1b7ed9f2feb154437f169b44d5178ed 0 418 3612 2956 2025-08-11T04:27:14Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Misc Operating Systems]] [[Category:BSD]] {{DistributionInfobox | architectures = arm, aarch64, armel, i486, ia64, mips, mipsel, sparc64, pc98, powerpc, powerpc64, ps3, x86_64, xbox | caption = The FreeBSD logo | defaultdesktops = [[GNOME]], [[LXQt]], [[KDE Plasma]], [[MATE]], [[Cinnamon]], [[Xfce]] | image = [[File:FreeBSD logo.png|200px|FreeBSD_logo]] | packagemanager = [[pkg]] | releasemodel = Stable | releasestatus = Maintained | title = FreeBSD | usagetype = Desktop, Firewall, Raspberry Pi, Server | website = [https://freebsd.org freebsd.org] }} FreeBSD is a [[UNIX|Unix]]-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by The FreeBSD Project. The first version of FreeBSD released in November 1993.<ref>[https://www.oreilly.com/openbook/opensources/book/kirkmck.html "Open Sources: Voices from the Open Source Revolution"] [[wikipedia:O'Reilly_Media|O'Reilly Media]]. 29 March 1999. [https://web.archive.org/web/20141007064642/http://oreilly.com/catalog/opensources/book/kirkmck.html Archived] from the original on 7 October 2014. Retrieved 15 June 2022.</ref> [[File:FreeBSD 13.0 boot loader screenshot.png|alt=Screenshot of FreeBSD 13.0 boot loader|thumb|Screenshot of FreeBSD 13.0 boot loader]] FreeBSD maintains a complete system, delivering a [[kernel]], [[Drivers]], [[userland]] utilities, and documentation, as opposed to [[Linux]] only delivering a kernel and drivers, and relying on third-parties such as [[GNU]] for system [[:Category:Software|software]].<ref>Chisnall, David (20 January 2006). [http://www.informit.com/articles/article.aspx?p=439601 BSD: The Other Free UNIX Family]. informit.com. [https://web.archive.org/web/20140105042620/http://www.informit.com/articles/article.aspx?p=439601 Archived] from the original on 5 January 2014. Retrieved 13 December 2013.</ref> The FreeBSD source code is generally released under a permissive BSD license, as opposed to the copyleft GPL used by Linux. The project includes a security team overseeing all software shipped in the base distribution. Third-party applications may be installed using the pkg package management system or from source via FreeBSD Ports.<ref>[https://docs.freebsd.org/en/books/handbook/ports/ "Chapter 4. Installing Applications: Packages and Ports"]. FreeBSD Handbook. The FreeBSD Project. [https://web.archive.org/web/20210922103704/https://docs.freebsd.org/en/books/handbook/ports/ Archived] from the original on 22 September 2021. Retrieved 16 June 2021.</ref> The project is supported and promoted by the FreeBSD Foundation. Much of FreeBSD's codebase has become an integral part of other operating systems such as Darwin (the basis for macOS, iOS, iPadOS, watchOS, and tvOS), TrueNAS (an open-source NAS/SAN operating system), and the system software for the PlayStation 3<ref>[http://doc.dl.playstation.net/doc/ps3-oss "Licenses of software used on PlayStation®3 console"]. [https://web.archive.org/web/20160326150848/http://doc.dl.playstation.net/doc/ps3-oss/ Archived] from the original on 26 March 2016. Retrieved 11 August 2010.</ref><ref>Rosenberg, Alex (17 December 2013). [https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html "FreeBSD Handbook and PS3"]. freebsd-doc (Mailing list). [https://web.archive.org/web/20170202003719/https://lists.freebsd.org/pipermail/freebsd-doc/2013-December/022959.html Archived] from the original on 2 February 2017. Retrieved 22 January 2016.</ref> and PlayStation 4<ref>[https://doc.dl.playstation.net/doc/ps4-oss/ "Open Source Software used in PlayStation®4"]. Sony Interactive Entertainment. [https://web.archive.org/web/20171212193301/https://doc.dl.playstation.net/doc/ps4-oss/ Archived] from the original on 12 December 2017. Retrieved 4 January 2019.</ref> game consoles. The other current BSD systems (OpenBSD, NetBSD, and DragonFly BSD) also contain a large amount of FreeBSD code, and vice-versa.^{[''citation needed'']} == References == <references /> 683713941d6692ea1900424bb6a961c6288a79d4 0 809 3613 3275 2025-08-11T04:27:24Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Funtoo Linux | image = [[File:funtoo.png|300px|Gentoo Linux logo matte]] | caption = The official Funtoo Linux logo | releasestatus = Discontinued | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.funtoo.org/Welcome funtoo.org] }} [https://www.funtoo.org/Welcome Funtoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in early 2008 by Daniel Robbins. Known for its emphasis on customization and performance optimization, '''Funtoo''' allows users to compile their entire system from source code, providing granular control over system components and features. d3e44d31ceffa4367a0a05cb3b9566fd2932b415 0 291 3614 3387 2025-08-11T04:28:04Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|300px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 48, 2025-03-19 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[Category:Desktop Environments]] [[File:GNOME 43.png|thumb|A desktop running GNOME 43]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>[https://www.gnu.org/philosophy/free-sw.en.html What is Free Software?], GNU (Accessed: May 7, 2025)</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>[[wikipedia:Qt_(software)#Early_developments|Early Developments of QT]], Wikipedia (Accessed: May 7, 2025)</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>[[wikipedia:GNOME#History|History of GNOME]], Wikipedia (Accessed: May 7, 2025)</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>[https://foundation.gnome.org/ GNOME Foundation], GNOME Foundation, 2025-08-08 (Accessed: 2025-08-09)</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. == References == 20b3bb8e857f878674f4707cd609f1d928bc7a8d 0 441 3615 3494 2025-08-11T04:29:34Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,")<ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU], The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> is a dedicated organization for free [[:Category:Software|software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone [[Operating System|operating system]] because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or [[Proprietary software|proprietary]]: A few are GNU/[[Linux]], [[MacOS]], [[UNIX|Unix-based]]/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the proprietary software of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe. </ref> == Included Software / Components == [[File:Gnu compiler collection-logo-1.png|alt=This logo depicts a Bull shaped animal jumping out of an egg, in black text that displays the letters G, C, C|left|thumb|224x224px|A logo of the GCC.]] As of June 2024, the GNU project currently holds 394 active [[packages]], but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. Overall, these components are in many operating systems, mainly because of how easy GCC is to access for any developer. Because of Richard Stallman, he was able to free the variety of tools and software developed for the GNU project and in turn, pushed forward for the movement of open and free software for all.<ref name=":0" /> == History of GNU == [[File:RichardStallman.jpg|alt=A Picture of Richard Matthew Stallman in 2024|thumb|341x341px|A Picture of Richard Matthew Stallman in 2024]] Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref name=":0">[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible [[architecture]] because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs.<ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> == References == <references /> fbc7e446579607d41568391311b7e0a89e34679a 0 575 3616 3480 2025-08-11T04:29:44Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <sup>🍣DEAD?]</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys|} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == 78d5ef2d9fde1abfa5e79dd6c193867806159e5d 0 853 3617 3543 2025-08-11T04:29:54Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work_In_Progress}} The '''GNU General Public License''' (short '''GNU GPL''' or '''GPL''') is a copyleft license published by the Free Software Foundation (FSF) and written by Richard Stallman<ref>https://archive.ph/20120907170559/http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html</ref>. The newest Version is the GNU General Public License version 3 (GNU GPLv3) released in June 2007<ref>https://www.gnu.org/licenses/gpl-3.0.en.html#license-text </ref> and can be found here [https://www.gnu.org/licenses/gpl-3.0.en.html#license-text here] TODO: Add a short description of the 3 Versions c84908379ac1dd49dfbe09f2def60e47f302843d 0 823 3618 3424 2025-08-11T04:30:17Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Mascots]] [[File:OpenSUSE Button.svg|alt=Geeko is a chameleon drawing and is the mascot for openSUSE.|thumb]] '''Geeko''' is the official mascot of [[openSUSE]]. It is a chameleon and not a gecko.<ref>https://en.opensuse.org/openSUSE:Geeko, openSUSE, 2010-07-14 (Accessed: 9 August 2025). </ref> == References == <references /> 9f0bce4c11e1d4e37b082abcc36f188c77f255d6 0 203 3619 3389 2025-08-11T04:30:57Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]]<ref>[https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer) Daniel Robbins (computer programmer)], Wikipedia contributors, 2024-01-10 (Accessed: 2025-08-09)</ref>. Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile<ref>[https://en.wikipedia.org/wiki/Compilation Compilation], Wikipedia contributors, 2024-07-30 (Accessed: 2025-08-09)</ref> their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish thru source compilation of the packages and the kernel itself. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements, the only downside of that being increase compilation time, however '''Gentoo''' is very minimal and it allows a lot of flexibility in that regard. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "slotting". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. To manage those multiple versions of the same packages ( slotting ), '''Gentoo''' provides a tool called '''eselect'''. It acts as a manager for setting system defaults, such as choosing which version of GCC, Python, or even your preferred text editor should be used globally. == Use cases of eselect == Changing the GCC version<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect gcc list [1] x86_64-pc-linux-gnu-13 * [2] x86_64-pc-linux-gnu-14 [user@hostname ~]$ eselect gcc set 2</syntaxhighlight>Changing the locale<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 * [3] en_US.utf8 [4] POSIX [ ] (free form) [user@hostname ~]$ eselect locale set 3 </syntaxhighlight> == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp)</syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |- |<code>emerge --unmerge package</code> |Remove a package and its dependencies |- |<code>emerge --depclean</code> |Remove unused dependencies |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers pre-compiled package options, which usually end in '''<code>-bin</code>''', by example one might want to install Firefox without the hassle of compiling, they can just download the binary version of it by doing <code>sudo emerge firefox-bin</code>. Obviously, not all binary packages will end in the <code>-bin</code> format, they can be named simply like normal packages, for that reason Portage highlights the binary and source packages differently in colors so the user knows which are binary and which are meant for compiling, additionally portage also informs the user of which packages are binaries or source. For additional packages, users might opt for the [https://wiki.gentoo.org/wiki/Project:GURU GURU] project repository, it aims to be a very large user repository, full of binaries and source packages that are not found inside the normal '''Gentoo''' repositories, meant to extend the experience that you can have in this Operating System. Users can create their own repository online as well, or how we call it, "overlays". The user can create an overlay with the desired package, make an ebuild for it and then publish it online for people to use. To get started with an overlay, one must first understand what are ebuilds and how they work, for this it's preferred to read the '''Gentoo Wiki''' on how to do it, it is possible to even add your custom package inside '''GURU''' later, and even the official '''Gentoo''' repository if it's seen as valuable. == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === One might be interested in community resources for '''Gentoo.''' The official community forums can be found at [https://forums.gentoo.org/ forums.gentoo.org/]. Additionally, IRC<ref>Internet Relay Chat</ref> channels has been setup as well. For those who are interested in the official IRC channels, they can be found on the '''Gentoo Wiki''' in the [https://wiki.gentoo.org/wiki/IRC IRC] article. It is possible to subscribe to the [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] or even send emails to them, the page lists the most important lists with the most traffic. There are other, more specialized lists that might be more appropriate depending on the topic. There is a [https://www.gentoo.org/support/documentation/ wiki documentation] available as well. Users can search up specific pages in the site directly, so that they don't waste time finding the right page. Ultimately, '''Gentoo''' offers a [https://bugs.gentoo.org/ bug tracking system] for those who are interested in being up to date with current bugs, or even attempt to solve them. === Development Model === '''Gentoo''' was developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the userbase through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == '''Gentoo''' allows maximum customization potential, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to fetch binaries in heavier packages. However, '''Gentoo''' has it's own downsides; It will take longer to install packages as they compile from source, meaning it will take some time until finished and ready to use. If the system has a very weak CPU, the Operating System will take a while to fully install. The Operating System has a higher learning curve, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] 88a58d81fbcc32b3f211816e1f42e41c744a4d2f 0 355 3620 3313 2025-08-11T04:31:07Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{Needs Citations}}The '''GNU C Library''', commonly known as '''glibc''', is the GNU Project implementation of the C standard library. It provides a wrapper around the system calls of the Linux kernel and other kernels for application use. Despite its name, it now also directly supports C++ (and, indirectly, other programming languages). It was started in the 1980s by the Free Software Foundation (FSF) for the GNU operating system. 769048076239ed57f5e163a3fce0f2f294368320 0 570 3621 2819 2025-08-11T04:33:48Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Mascots]] {{Needs_Citations}} {{MascotInfobox | title = GNU | image = [[File:Heckert_GNU_white.svg|thumb]] | caption = GNU, the mascot of the GNU Project }} GNU is the mascot of the [[GNU]] Project GNU is a black and white sketch of a wildebeest (also known as a gnu or gnou) 52aa8873546ca16feaf14d868232a55a0f1a9ca9 0 716 3622 3345 2025-08-11T04:33:58Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki A '''Hackintosh''' is a non‑Apple computer configured to run Apple's '''macOS''', using unofficial methods to bypass hardware restrictions. Apple's software license restricts macOS usage to Apple‑branded machines<ref>{{Cite|title=Hackintosh|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == History == === Origins === The concept surfaced as users attempted to run Mac OS on non‑Apple hardware. It gained real momentum after Apple transitioned to Intel CPUs, making macOS compatible with x86 architecture<ref>{{Cite|title=Intel Macs usher in Hackintosh era|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === PC Installations === Following the release of Intel-based Macs in 2006, community developers modified the macOS kernel to disable hardware checks and employed EFI emulation tools like FakeEFI to boot macOS on PCs<ref>{{Cite|title=Hackintosh bootloaders|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === Bootloader Evolution === Bootloaders such as Chameleon and Clover evolved to improve reliability. In 2019, '''OpenCore''' was introduced, offering advanced features like support for macOS security features including System Integrity Protection and FileVault<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === Legal Developments === In 2008, Apple sued Psystar for selling unauthorized macOS clones. The court ruled Psystar violated Apple copyright and the DMCA, underscoring Apple's legal restrictions<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == Technical and Legal Status == Apple's EULA prohibits running macOS on non‑Apple hardware<ref>{{Cite|title=Hackintosh licensing|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. The DMCA's anti‑circumvention provisions create legal uncertainty in the U.S.<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. Apple's transition to ARM-based silicon (beginning in 2020) reduces future feasibility for x86 Hackintoshes<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref>. == Hardware Compatibility == According to the '''Dortania OpenCore Install Guide''': CPUs: modern Intel (up to Comet Lake) and patched AMD Ryzen series GPUs: Intel integrated graphics (Ivy Bridge to Ice Lake), AMD GCN/Vega/Navi; NVIDIA support is limited Networking: Broadcom-based Wi‑Fi and Ethernet adapters are preferred<ref>{{Cite|title=OpenCore hardware limits|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref> == Installation Guide == This guide provides a high-level overview. For full instructions, consult the [[OpenCore Install Guide]]. === 1. Prepare hardware === Confirm that your CPU, GPU, and network adapters match published compatibility lists. === 2. Obtain macOS installer === On a real Mac, download the desired macOS version (such as Sonoma or Sequoia) from the App Store. === 3. Build a USB installer === Partition a USB drive as HFS+ or APFS and use '''OpenCore''' along with official tools to create a bootable installer<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 4. Configure BIOS/UEFI === Disable Secure Boot, VT-d, CSM, Fast Boot. Enable UEFI and XHCI handoff<ref>{{Cite|title=OpenCore BIOS settings|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 5. Boot and install macOS === Boot from the USB installer, format the target storage as APFS, then proceed with the installation. === 6. Post-install configuration === Migrate the USB EFI folder to the internal EFI partition. Install necessary kexts (for audio, network), configure USB mapping, and finalize settings such as NVRAM, FileVault, and Sleep/Wake. == Resources == [https://dortania.github.io/OpenCore-Install-Guide/ Dortania OpenCore Install Guide] – full tutorial [https://en.wikipedia.org/wiki/Hackintosh Hackintosh – Wikipedia] [https://tonymacx86.com/ tonymacx86 forums] – hardware build guides and buyer lists == See also == [[macOS]] [[Virtualization]] [[BIOS]] == References == <references/> 20aa2e903efed2d5690a5874d6f5647360e00ded 0 779 3623 3309 2025-08-11T04:34:08Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Haskell-Logo.svg]] | title = Haskell | releasestatus = Maintained | lastrelease = GHC 9.12.2 - 22 July 2025 / Haskell2010 | firstrelease = GHC 0.29 - 25 July 1996 / Haskell 1.0 | languages = Haskell | developers = The Haskell Foundation | designed by = ICFP | website = [https://haskell.org haskell.org] }} {{Needs Citations}}'''Haskell''' is a general-purpose, statically typed, purely functional programming language with type inference and lazy evaluation. = History = Functional Programming in the 80's already had its roots in programming - such as the Lisp language. The new idea that sparked creation of multiple functional languages (such as Miranda, SASL, KRC) was lazy evaluation - which later became one of core Haskell ideas. In order to centralize functional programming efforts, multiple conferences (later merged into International Conference on Functional Programming) were held in the 90's. They resulted in creation of '''Haskell'''. = Philosophy = Haskell as a functional language inherits its philosophy from math-oriented subjects such as Lambda Calculus or Category Theory. Despite it's reputation, Haskell doesn't require prior knowledge of those in order to write basic code. = Installation & Usage = Most common Haskell compiler is '''GHC''' - Glasgow Haskell Compiler. Installation process shouldn't be harder than installing `ghc` package with your favorite package manager. GHC provides essential tools, such as `ghc` and `ghci` - the compiler and interpreter. The latter can be used for simple inline operations, which is extremely useful when learning the language. = Useful Links = * [https://learnyouahaskell.github.io/ Learn You A Haskell] is a popular book (with a free online copy) which aims to explain Haskell without requiring prior knowledge in functional programming. * [https://hoogle.haskell.org/ Hoogle] is a Haskell API search engine, helpful in finding libraries etc. a79253b0fd6c7e1bf127caa5754df182e3669196 0 263 3624 3314 2025-08-11T04:34:46Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | image = [[File:Hyfetch.png|thumb]] | caption = Hyfetch on Arch | title = Hyfetch | releasestatus = Maintained | lastrelease = 1.99.0, 2024-10-24 | languages = [[bash]], [[python]] | developers = hykilpikonna | website = [https://github.com/hykilpikonna/hyfetch github.com/hykilpikonna/hyfetch] }} [[Category:Software]] [[File:Hyfetch pride month.png|alt=The Hyfetch Pride Month easter egg.|thumb|The Hyfetch Pride Month easter egg.]] Hyfetch is an actively developed fork of [[Neofetch]] and is a command-line system information tool written in [[Bash]] and [[Python]] which displays information about your [[Operating System|operating system]], [[:Category:Software|software]] and [[hardware]] with the option to color the logos with pride flags.<ref>https://github.com/hykilpikonna/hyfetch Hyfetch Github 2025 (fetched 24th June 2024)</ref> === Features === Due to Hyfetch being a direct fork of Neofetch, many of the features from it are available on Hyfetch, with the addition of some other ones such as the aforementioned ability to color the distro logo with pride flags and the ability to use a different backend for Hyfetch, such as [[Fastfetch]]. If the pride flag feature is not desired, you can run the <code>neowofetch</code> command, which is an actively maintained fork of Neofetch used as the default backend for Hyfetch. ==== neowofetch ==== Neowofetch is an actively maintained fork of Neofetch bundled with Hyfetch as the default backend. It has all the features from the original, but it lacks the ability to color the logo with pride flags. Neowofetch was named this way to avoid naming conflicts with the original Neofetch. === Trivia === * If you run Hyfetch in the month of June, an animation will play of a bunch of pride flags scrolling in the background with an ASCII text box that says "Happy Pride Month!". This animation can be replayed with the <code>--june</code> option. == References == <references /> 6130d15fbaef299fa7cb30cb275c668ccee9f285 0 257 3625 3481 2025-08-11T04:34:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.40.0, 2024-05-04 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor built on [[wlroots]]. It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Hyprland], 2025-08-10 (Accessed: 2025-08-10)</ref> Hyprland uses its own configuration syntax, designed to be readable and easy to learn, with similarities to shell scripting. The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway (window manager)|Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> 3348a584dfaecb55c051f760d89255451f8a6ae6 0 227 3626 3390 2025-08-11T05:05:43Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox | image = [[File:I3 window manager logo.svg|I3_window_manager_logo]] | caption = i3 logo | title = i3 | releasestatus = Maintained | lastrelease = 4.23, Oct 29, 2023 | languages = [[C]] | developers = Michael Stapelberg | website = [https://i3wm.org/ i3wm.org] }} [[Category:X_Window_Managers]] [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager - YouTube], Google TechTalks, 2012-06-18 (Accessed: 2025-08-09)</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== == References == 5674487990455a3f9b3633134c8bbce769c752ce 0 239 3627 2576 2025-08-11T05:05:52Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], [[C]] | developers = Marko Maček, community contributors | website = [https://ice-wm.org/, ice-wm.org] }} [[Category:X_Window_Managers]] [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]] IceWM is a fast, simple and light X11 [[Window Management System|window manager]]. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. <references /> 4ecf95bfea475777e3dc64e909167bacc3372c1c 0 349 3628 2965 2025-08-11T05:06:02Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is required to enable optimal use of an OS. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor'''<ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref> of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in an operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, etc. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |runit |February 10, 2004 |September 29, 2024 |↓ |Gerrit Pape |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS. == References == <references /> dce049c46bded64e34af656148bcc15aa222f52e 0 661 3629 3429 2025-08-11T05:06:12Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox | title = Kali Linux | image = [[File:Kali-dragon-icon.svg|frameless]] | caption = Kali Logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APT]] | defaultdesktops = [[Xfce]], [[GNOME]], [[KDE Plasma]] | usagetype = Desktop, Mobile, USB | architectures = x86_64, x86, armel, armhf | website = [https://www.kali.org/ Kali.org] }} Kali Linux is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, Digital forensics, and penetration testing. 44af5b01866b34d3fed80b4fc2dda86af1e2feea 0 344 3630 3267 2025-08-11T05:06:52Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] [[File:Kernel Layout.svg|thumb|How the Kernel interacts with the software and hardware.]] The Kernel is the core part of any [[Operating System|operating system]], such as the [[Linux|Linux Kernel]]. It's the fundamental layer between the computers [[hardware]] - including but not limited to the CPU, RAM, and GPU, and the [[:Category:Software|software]] you interact with. The Linux Kernel itself is a Modular and Monolithic Kernel, meaning that it incorporates most of the Core functions within the Kernel itself (Like Process management, device drivers, Memory management, File systems, etc.). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2 Linus Torvalds 1991 (Retrieved 16th March 2025)</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel Kicksecure, Madaiden, Adrelanos 2023 (Retrieved 16th March 2025)</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. == References == 2ad095cc6a07c39b135ae6d92674d0988ff3fc96 0 345 3631 3322 2025-08-11T05:15:36Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] {{Needs Citations}}Kernel Modules are pieces of code that can be loaded directly into the [[Kernel]] at runtime to extend functionality.<ref>https://linux-kernel-labs.github.io/refs/heads/master/labs/kernel_modules.html Kernel Labs Github, 2025 (imported 26th June 2025)</ref> The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every modules built in by default, but this may vary depending on your [[Linux Distributions|Distribution]], as such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically older ones benefit the most) at the cost of new devices potentially not working when added. It is also possible to compile a Linux kernel on a pre-existing system to only use needed Kernel modules. == Obtaining information == Modules depend on the kernel release and the kernels version, though usually they are stored in <code>/usr/lib/modules/''kernel_release_version''</code>''.'' To see which modules are loaded, <code>lsmod</code> can be used. Obtaining information is achievable with <code>modinfo <module_name></code> == Module loading == === Automatic loading === Usually most needed modules are handled [[udev]], so usually out of tree modules aren't needed, though there are cases where loading or blacklisting a module is needed for your setup to function properly. Early module loading is generally handled by your [[initramfs]] generator of choice, usually dracut, booster or mkinitcpio. Alternatively, [[systemd]] will load modules explicitly listed in <code>/etc/modules-load.d/</code> ,with the naming scheme of <code>/etc/modules-load.d/program.conf</code>. Lines starting with ; or # are parsed as comments and ignored === Manual loading === Kernel modules can be manually loaded with <code>modprobe <module_name></code>, or loading a module that by file name (i.e. modules that are not installed in <code>/usr/lib/modules/<kernel_release_version></code>) can be achieved either of the following ways:<syntaxhighlight lang="sh"> insmod file_name module_options modprobe file_name </syntaxhighlight>Removing a module can be achieved by:<syntaxhighlight lang="sh"> rmmod module_name modprobe -r module_name modprobe --remove module_name </syntaxhighlight> == References == c0cca709dcfb526762f81b7e6d9e2b70b89a2c42 0 8 3632 3324 2025-08-11T05:15:44Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 01f4c62b4a34a9c6d440ca58207b240de22eca13 0 219 3633 2969 2025-08-11T05:15:54Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan.<ref>https://community.kde.org/Promo/Material/Mascots Official KDE Wiki, 2025 (Imported 6th June 2024)</ref> Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror], KDE's default web browser.<ref>https://community.kde.org/Konqi Official KDE Wiki, 2025 (Imported 6th June 2024)</ref> == References == <references /> 41b0466486f44a0b7bedc88466372cef3e3486b7 0 202 3634 3278 2025-08-11T05:16:04Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[Category:Mascots]] [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is the unofficial mascot<ref>https://wiki.gentoo.org/wiki/Larry_the_cow Gentoo Wiki, 2023 (Imported 4th June 2024)</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html Gentoo Forums, 2003 (imported 4th June 2024)</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727 Gentoo Bug Report, 2003 (imported 4th June 2024)</ref> * Larry can be found in [[emerge]] by running <code>emerge --moo</code> Larry can also be found in [[Dpkg|apt]] by running <code>apt moo</code> . * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow MySpace, (imported 4th June 2024)</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry, Gentoo Wiki, 2000 (imported 4th June 2024)</ref> [[File:Larry The Cow with Gentoo Logo.png|thumb|Larry after he grew his black and white patches]] == References == <references /> 2841eaa25f695437ea18bbbd7913fecc80850122 0 244 3635 2971 2025-08-11T05:16:44Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]. Installation instructions should be on its own Guides page.}} [[Category:Guides]] [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. '''NOTE:''' After your first Libreboot, you are more than likely able to flash repeatedly afterwards without having to use a Pomona Flash Clip (below). Depending on your device, the flashing experience may and inevitably, at times, '''will''' vary. '''<u>Please check for your BIOS chip device on the Libreboot website.</u>''' === Steps to Install === As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your machine using the Dell OptiPlex as an example. See below for an easier method for that specific device. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. For a Dell OptiPlex 9020, your image '''should be named''' "'''dell9020mt_12mb'''." after compilation. ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository] and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) == References == bfc5159ba6dce5e05ebb83c7bd9e860d224a34ba 0 178 3636 3323 2025-08-11T05:17:18Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[Category:Terminology]] [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and deallocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under the terms of the [[GNU General Public License]] version 2 (GPLv2), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] * [[Unix]] * [[Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> 606bee6cc6a51b535102fdd81cc1093f6e64bdde 0 198 3637 3514 2025-08-11T05:17:28Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software. <ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == 665990c5c867a4b31137fddbb1f91f9f1b31c0cd 0 537 3638 2974 2025-08-11T05:17:41Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = Linux From Scratch | image = [[File:Linux-From-Scratch logo.png|Linux-From-Scratch_logo]] | caption = Linux From Scratch logo | releasestatus = Maintained | packagemanager = None | releasemodel = Stable | usagetype = Source-based, Education | defaultdesktops = [[Fluxbox]], [[IceWM]], [[KDE Plasma]], [[LXQt]], [[Openbox]], [[Xfce]], [[GNOME]] (BLFS) | website = [https://www.linuxfromscratch.org/index.html www.linuxfromscratch.org] | architectures = i386, x86_64 }} Linux From Scratch is the name of a type of [[Linux]] install and the name of a book written by Gerard Beekmans, which gives detailed instructions on how to achieve a fully functional Linux operating system entirely by compiling source packages. The book is available for free on the official website and major releases are usually published twice a year<ref>[https://www.linuxfromscratch.org/lfs/news.html "LFS News"]. ''www.linuxfromscratch.org''.</ref>. [[File:Linux From Scratch desktop.jpg|alt=Screenshot of a Linux From Scratch install with a modified Xfce desktop.|thumb|Screenshot of a Linux From Scratch install with a modified Xfce desktop.]] == Projects under LFS == The following projects are part of the Linux From Scratch umbrella and are accessible on the official website, and are as follows: * '''Linux From Scratch (LFS)''': The original book itself, which gives detailed instructions on how to create a bootable and fully functional Linux system by compiling source packages<ref>[https://www.linuxfromscratch.org/lfs/ "LFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. * '''Beyond Linux From Scratch (BLFS)''': An extension of the original LFS book to extend the functionality of a LFS system by providing instruction on how to compile a wide variety of additional packages, such as desktop environments and networking tools<ref>[https://www.linuxfromscratch.org/blfs/ "BLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. * '''Automated Linux From Scratch (ALFS)''': A project meant to automate the compilation of the various packages needed for a LFS system via the use of scripts<ref name=":0">[https://www.linuxfromscratch.org/alfs/ "MLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. The current official implementation of ALFS is ''jhalfs''<ref name=":0" />. * '''Multilib-LFS (MLFS)''': A variant of the original LFS book to build a system that's able to execute 32-bit binaries<ref>[https://www.linuxfromscratch.org/mlfs/ "MLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. It is cited as a strongly recommended requirement for GLFS<ref name=":1">[https://www.linuxfromscratch.org/glfs/ "GLFS Project Homepage"]. ''www.linuxfromscratch.org''.</ref>. * '''Gaming Linux From Scratch (GLFS)''': A guide based off the BLFS book that provides instructions for installing gaming software such as [[Steam]] and [[Wine]], software libraries such as [[OpenGL]] and [[Vulkan]] and proprietary graphics drivers for [[Nvidia]] and [[AMD]] GPUs<ref name=":1" />. * '''Hints''': Large library of user-submitted documents which provide tips on various things related to maintaining LFS systems<ref>[https://www.linuxfromscratch.org/hints/ "LFS Hints Project Home"]. ''www.linuxfromscratch.org''.</ref>. * '''Patches''': Central repository of user-submitted patch files to add LFS-specific functionality to various packages and also serves as a testing ground for patches that may be added to new LFS and BLFS versions<ref>[https://www.linuxfromscratch.org/patches/ "LFS Patches Project Home"]. ''www.linuxfromscratch.org''.</ref>. * '''LFS Editor's Guide''': Small document that describes the LFS development process<ref>[https://www.linuxfromscratch.org/lfs/LFS-EDITORS-GUIDE.html "Linux From Scratch Editor's Manual"]. ''www.linuxfromscratch.org''.</ref>. * '''Museum''': Archive of old LFS versions<ref>[https://www.linuxfromscratch.org/museum/ "Index of /museum"]. ''www.linuxfromscratch.org''.</ref>. == Standard build unit (SBU) == A peculiar feature of LFS is its usage of special measurement units to calculate the approximate time that a package takes to fully compile called standard build units (SBUs)<ref>[https://www.linuxfromscratch.org/lfs/view/stable/chapter04/aboutsbus.html "4.5 About SBUs"]. ''www.linuxfromscratch.org''</ref>, and 1 SBU is roughly equal to the time it takes to compile the first package in the LFS book, [[binutils]]<ref>[https://www.linuxfromscratch.org/lfs/view/stable/chapter05/binutils-pass1.html "5.2. Binutils-2.43.1 - Pass 1"]. ''www.linuxfromscratch.org.'' Retrieved 2 February 2025.</ref>. For example, if it took about 10 minutes to compile binutils, and the [[GRUB]] page says that it takes approximately 0.3 SBUs to build<ref>[https://www.linuxfromscratch.org/lfs/view/stable/chapter08/grub.html "8.64. GRUB-2.12"]. ''www.linuxfromscratch.org''. Retrieved 2 February 2025.</ref>, you would multiply the amount of time for how many SBUs the page says it would take, resulting in about 3 minutes of compile time. == References == fac783c4c47ca3c4ac288f5ad605929e7382604d 0 209 3639 3347 2025-08-11T05:19:46Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Incomplete page, guides should be on their own page in the Guides namespace}} {{Needs_Citations}} [[Category:Guides]] [[Linux]] is a good way to make-do with an old Intel Mac you may have. Many issues exist due to hardware support, such as WiFi support, and keyboard + trackpad issues on some devices. This page will list solutions to common issues as well as tips, tricks, and other information. On many Mac devices Linux works flawlessly after initial setup and troubleshooting is complete. If you are attempting to install Linux on a device with an ARM (Apple Silicon) CPU, see the [[#Asahi Linux]] section. == Asahi Linux == Asahi Linux as a work in progress port of many tools and drivers to Apple Silicon on Linux, and is currently under heavy development. More information can be found on the [https://asahilinux.org/ Asahi Linux website]. == Troubleshooting == === MacBookPro11,x to MacBookPro12,1 === ==== WiFi doesn't work ==== This is a side-effect of Broadcom's poor driver support on Linux, read [https://asahilinux.org/ this page] for information on how to install the proprietary '''broadcom-wl driver''' on Arch Linux. Other distributions should follow their respective guides if one exists. == Notes == '''> More issues will be added overtime. This list is far from done.''' <references /> 202d7e06f44b4ebbb72ec3d8287c9656cb50d05d 0 218 3640 3393 2025-08-11T05:19:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} [[Category:Guides]] [[Linux]] due to its generally lower system requirements than [[Windows]]<ref>[https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3 Revive Old Hardware with Linux], Aidan Palmer, 2023-03-05 (Accessed: 2025-08-09)</ref> or [[macOS]] and a general absence of vendor-imposed hardware restrictions is frequently chosen for reviving and reusing older devices. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (i.e. keyrings, polkit, GTK, QT, etc.) |Usually require command line knowledge to troubleshoot|} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>[https://www.linuxmint.com/faq.php Frequently Asked Questions - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>[https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <span style="color:#fc493b">https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <sup>🍣404]</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Frequently_asked_questions Frequently asked questions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://wiki.archlinux.org/title/Arch_compared_to_other_distributions Arch compared to other distributions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time-consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>[https://fedoraproject.org/wiki/FAQ FAQ], Fedora Project Wiki, 2025-07-24 (Accessed: 2025-08-09)</ref><ref>[https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs Hardware Overview], Fedora Docs, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">[https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html System requirements for Puppy Linux], THE.Hosting, 2023-04-23 (Accessed: 2025-08-09)</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> ||} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' == References == <references /> 227b830843f23bd7e42ee08c33052a6e8a8fea07 0 581 3641 2058 2025-08-11T05:20:06Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} {{DISPLAYTITLE:MATE DE}} [[Category:Desktop Environments]] [[File:MATEDesktop.png|thumb|A screenshot of the default MATE desktop on Debian Linux.]] The [https://mate-desktop.org/ MATE] Desktop Environment is a desktop environment that is the continuation of GNOME 2. It is known for using traditional metaphors for Linux and other Unix-like operating systems, and for being a lightweight desktop that runs well on older hardware. It is available on a wide variety of Linux, Illumos and BSD - based systems. MATE is known as one of the three desktop options on [https://www.linuxmint.com/ Linux Mint], as well as the main desktop of [[Ubuntu|Ubuntu MATE]]. == Features == MATE is configured by default to use a traditional UNIX-like desktop layout, with a top and bottom panel like its ancestor GNOME 2. It is a lightweight desktop, much like [[XFCE]], and is often used on older and less powerful computers. It can use GTK2 or GTK3 theming - the latter being compatible with [[Cinnamon]]. == Software == The base system is made up of the Marco window manager, MATE Panel, and MATE Session Manager. Additional software can be installed on some distributions with the mate-extras package. MATE includes the Caja file manager, Pluma notepad / text editor, Eye of MATE image viewer, Atril document viewer, Engrampa archive manager, and MATE Terminal. == Naming == MATE is said to be pronounced "mah-tay". The MATE desktop is named after ''Ilex paraguariensis,'' commonly known as yerba maté, which is a caffeine-rich holly plant used to make the infused herbal drink mate. d1b1bdcfa832ea18cca3eff3a01285a18bc3e4ef 0 718 3642 2753 2025-08-11T05:20:16Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[File:Apple-Logo-Transparent.png|thumb|right]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical operating systems developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a UNIX (Darwin/BSD) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> 5334735f78443438f16eee3561821cd437951ab0 0 240 3643 3350 2025-08-11T05:21:38Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Guides]] {{Cleanup|Incomplete page}}{{Needs Citations}} When switching between [[Linux Distributions]], Windows or MacOS migrating your system to another can often be difficult, this guide aims to try tackle this problem when migrating to and from [[Arch Linux|Arch,]] [[Debian]], [[Fedora]], Windows and MacOS. More distributions may be added to this guide at some point and if your distribution isn't listed you can reference the general information section applies to switching to almost any distribution from any operating system and the information for Arch, Debian and Fedora should apply to most derivative distributions. === General Information === ==== Multi Booting ==== [[File:GRUB with ubuntu and windows vista.png|alt=A black and white grub menu, it contains entries for Ubuntu Linux and Windows Vista|thumb|GRUB, with entries for [[Ubuntu]] and Windows Vista, an example of ''dual booting.'']] [[Multi Booting]] (Or often referred to as 'Dual Booting') is the process of installing multiple [[Operating System|Operating Systems (OS)]] on your device. It is an especially useful tactic for [[Distrohopping|distrohoppers]], people new to [[Linux]] by allowing users to test or use an OS without completely removing their current one. Doing so requires a [[bootloader]] (Such as [[GRUB]]) setup and the user to partition the storage medium on their device and then install the operating systems with a CD or USB Flash Drive. When dualbooting Linux and Windows it is best to first install Windows as it will likely override the Linux bootloader when installing its own bootloader. It is also highly recommended to backup any files on the OS that is already on the device (If changing a single boot machine to a multi-boot machine). For a more comprehensive guide on how to dual boot see the [[Multi Booting]] page. ==== Finding Alternatives or Workarounds for Apps ==== Often there is at least one [[application]] missing on Linux or an app that is missing some features or is buggy so you'll find yourself looking for alternative options. There also sometimes is the issue that your distribution doesn't have an app but another distribution does have it. A good place to start when looking for alternatives is [https://alternativeto.net AlternativeTo] which is a crowdsourced site useful to find alternatives for almost any app. Other useful sites include [https://www.privacytools.io Privacy Tools] and [https://awesome-privacy.xyz Awesome Privacy] with a privacy focused list of apps. When looking for workarounds for apps not supported for your distribution you should first check [https://flathub.org Flathub] and [https://snapcraft.io Snapcraft] (Note that [[Snap|Snaps]] are known to have performance issues) if your app is available there as they offer support for most distributions. If a steam game lacks native Linux support try checking [https://www.protondb.com ProtonDB] if Valve's proton tool supports your game. [https://www.winehq.org Wine] is also an option to run Windows apps on Linux. === Moving between specific Operating Systems === ==== Moving to Linux from MacOS ==== ==== Moving to Linux from Windows ==== == General Information == b9a560638d0147cd0944e9f13b1e7ef27f9aebdd 0 297 3644 3100 2025-08-11T05:21:48Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)."</ref> The core concept of multi-booting revolves around partitioning a computer's [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system's configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. it provides however the booted OS with full access to the machine's components, rather than needing to go through translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straightforward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Riot's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == References == <references /> f31f35c5d3f993bd527c60bf8289a5373094eecb 3645 3644 2025-08-11T05:22:13Z Madonuko 140 fix HMCT wikitext text/x-wiki [[Category:Terminology]] '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)."</ref> The core concept of multi-booting revolves around partitioning a computer's [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system's configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. it provides however the booted OS with full access to the machine's components, rather than needing to go through translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straightforward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Riot's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == References == <references /> 67bc9488b992da7114dbd0debdc76ef39fa7e6aa 0 322 3646 3351 2025-08-11T05:22:18Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{Needs Citations}} {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the [[Linux|Linux kernel]], released under the MIT License. It was developed by Rich Felker to write a clean, efficient, and standards-conformant libc implementation. == Usage on [[Operating System|Operating Systems]] == [[Linux Distributions|Linux distributions]] which use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * [[Sabotage]] * [[Morpheus Linux]] * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against glibc. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. == See also == * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] 20ba825c8c90b2cab9a4842f25ca477b81262aac 0 261 3647 3316 2025-08-11T05:24:44Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] }} Neofetch is a command-line system information tool written in [[bash]] which displays information about your operating system, software and hardware. It was created by Dylan Araps in 2017 and was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]], a neofetch-like utility written in [[C]], and [[hyfetch]], a fork of neofetch with pride flags. == References == <references /> 285bf1af2f53d26309321aa89f77ce1a39262008 0 534 3648 3397 2025-08-11T05:24:54Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox | image = [[File:Niri Rice.png|300px|example_niri_rice]] | caption = Example Niri Rice | title = niri | releasestatus = Maintained | firstrelease = v0.1.0-alpha.1 | lastrelease = Version 25.01 | languages = [[Rust]] | developers = Ivan Molodetskikh A.K.A. YaLTeR | website = [https://github.com/YaLTeR/niri Github Repository] }} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">[https://github.com/YaLTeR/niri/wiki/Important-Software Important Software · YaLTeR/niri Wiki · GitHub], YaLTeR, 2025-08-09 (Accessed: 2025-08-09)</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse] gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations] * Live-reloading == References == <references /> 8b155902937e59295386a911884e5bd6b22bcb8b 0 775 3649 3398 2025-08-11T05:25:04Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[File:2025-08-02 16-38-21.png|thumb|440x440px|Example of <code>NIX_AUTO_RUN=1</code> powered by nix-shell. Missing commands will be downloaded unless there are multiple sources.]] Nix-shell is command line tool for managing environment packages, allowing you to temporarily install and use software from a shell before discarding it upon exiting. Included with [[NixOS]] and [https://nixos.org Nix]. ===== Example usage: ===== <pre> [user:~]$ hello bash: command not found: hello [user:~]$ nix-shell -p hello [nix-shell:~]$ hello Hello, world! </pre>By default, <code>nix-shell</code> uses <code>bash</code> as the shell. You can change this using the <code>--command</code> flag, for example: <code>--command zsh</code>. The <code>-p</code> flag is shorthand for <code>--packages</code>. ===== Full usage: ===== <pre> [user:~]$ nix-shell --packages cowsay \ --command bash \ --run 'cowsay Success' \ --pure _________ < Success > --------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || </pre><code>--pure</code> removes all other packages from the shell environment, say; if you want to use <code>appimage-run</code> but the version of qt on your host is out-of-date. This way you don't have to remove/update qt outside the command. <code>--run</code> allows you to write out the full intended command, without first entering the shell. More parameters can be found in <code>man nix-shell</code>. ==== Auto run: [as shown in the image] ==== Auto run allows you to automatically download any packages you're missing, although it only checks the first word of your command. Allowing you to use any command like <code>inxi</code> by just typing out the command and running it, this extends to parameters as well, ex: <code>inxi -Fxxx</code>. This can be enabled via: <code>export NIX_AUTO_RUN="1"</code> Or by adding <code>environment.sessionVariables.NIX_AUTO_RUN = "1";</code> to your configuration. ==== Shell.nix ==== A <code>shell.nix</code> file sets up a reproducible development environment. When you run <code>nix-shell</code> it opens a shell with all your project's dependencies, keeping them isolated from your system. It can also be version locked by specifying channels or commit hashes. Below is an example <code>shell.nix</code> for a Node.js project.<ref>[https://nix.dev/tutorials/first-steps/declarative-shell.html Declarative shell environments with shell.nix — nix.dev documentation], NixOS Foundati on, 2016-08-09 (Accessed: 2025-08-09)</ref><pre>with (import <nixpkgs> {}); mkShell { buildInputs = [ nodejs-12_x yarn ]; shellHook = '' mkdir -p .nix-node export NODE_PATH=$PWD/.nix-node export NPM_CONFIG_PREFIX=$PWD/.nix-node export PATH=$NODE_PATH/bin:$PATH ''; }</pre> == References == <references /> 406779afedb5594bfed9276db4f139bae4560df9 0 171 3650 3364 2025-08-11T05:25:14Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such as nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental (But mostly stable and trusted) feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> 8bb275968bdbf2ef8bad4ea82718897e4b489a11 0 299 3651 2984 2025-08-11T05:25:54Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Misc Operating Systems]] [[Category:BSD]] {{DistributionInfobox | architectures = alpha, armish, aviion, hppa, i386, landisk, loongson, luna88k, octeon, powerpc, powerpc64, risc64, sgi, socppc, sparc, sparc64, x86_64, zaurus | caption = The OpenBSD logo | defaultdesktops = [[FVWM]], [[AfterStep]], [[AwesomeWM]], [[Blackbox]], [[Enlightenment]], [[Fluxbox]], [[GNOME]], [[IceWM]], [[KDE Plasma]], [[Openbox]], [[Window Maker]], [[Xfce]] | image = [[File:OpenBSD logo.png|200px|OpenBSD_logo]] | packagemanager = pkg_* | releasemodel = Stable | releasestatus = Maintained | title = OpenBSD | usagetype = Security, Server | website = [https://openbsd.org openbsd.org] }} OpenBSD is a [[UNIX|Unix]]-like [[Operating System|operating system]], based on the [[BSD|BSD (Berkley Software Distribution)]], developed by Theo de Raadt since 1995. The first version of OpenBSD (1.2) released in July 1996.<ref name=":0">De Raadt, Theo (18 October 1996). [http://wolfram.schneider.org/bsd/ftp/releases/OpenBSD-2.0 "The OpenBSD 2.0 release"]. ''openbsd-announce'' (Mailing list).</ref> [[File:OpenBSD 7.0 fvwm screenshot.png|alt=OpenBSD 7.0 running on the default desktop (FVWM).|thumb|OpenBSD 7.0 running on the default desktop (FVWM).]] The OpenBSD project produces a free, multi-platform BSD 4.4-based Unix operating system. Its efforts emphasize portability, standardisation, correctness, proactive security and integrated cryptography. The project also develops the widely used and popular [[OpenSSH]] (OpenBSD Secure Shell) software, which provides encrypted communication sessions over a computer network using the [[SSH]] protocol.<ref>[https://distrowatch.com/table.php?distribution=OpenBSD "OpenBSD"]. DistroWatch.com.</ref> Many open source projects widely used in other operating systems started off as components of OpenBSD, such as [[doas]], a safer replacement of the popular [[sudo]], the aforementioned OpenSSH and [[Xenocara]], a customized [[X.Org]] build infrastructure.<ref>[https://xenocara.org/ "About Xenocara"]. ''Xenocara''.</ref> Like all BSD operating systems, OpenBSD provides a kernel, drivers, userland utilities and documentation unlike [[Linux]], which provides just the kernel and drivers, relying on third-parties such as [[GNU]]. == References == <references /> 84642fdb49058c003890f5583937acb25d352fbc 0 562 3652 3399 2025-08-11T05:26:04Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Misc Operating Systems]] [[Category:Illumos]] {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>[https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips Getting Started - OpenIndiana Docs], The OpenIndiana Project, 2025-08-06 (Accessed: 2025-08-09)</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix-like [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel.<ref>[https://docs.openindiana.org/misc/openindiana/#what-is-the-openindiana-operating-system What is OpenIndiana Project?], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>[https://web.archive.org/web/20100913030810/https://www.openindiana.org/ Project OpenIndiana], The OpenIndiana Project, 2010-08-09 (Accessed: 2010-09-13)</ref> It was proved timely as Oracle shut down development of OpenSolaris.<ref>[https://web.archive.org/web/20201109033546/http://sstallion.blogspot.com/2010/08/opensolaris-is-dead.html OpenSolaris is Dead.], Iconoclastic Tendencies, August 13, 2010 (Accessed: July 13, 2025)</ref> OpenIndiana uses the same tooling as Solaris; the SMF init system,<ref>[https://docs.openindiana.org/handbook/systems-administration/#service-management-facility Service Management Facility], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> FMA fault management system,<ref>[https://docs.openindiana.org/misc/openindiana/#what-features-does-openindiana-have What features does OpenIndiana have?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and IPS package manager,<ref>[https://docs.openindiana.org/handbook/systems-administration/#software-management Software management], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> The majority of the [https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/ Solaris documentation] also applies to OpenIndiana.{{Citation needed}} OpenIndiana makes use of the SunOS branch of the UNIX kernel,<ref>[https://docs.openindiana.org/misc/openindiana/#why-is-it-called-openindiana Why is it called OpenIndiana?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and thus provides all of the stability benefits of a UNIX System V derivative.{{Citation needed}} This does, however, mean that hardware support is limited in comparison to a BSD or Linux based OS.<ref>[https://docs.openindiana.org/community-hcl/getting-hardware-info/ Getting information about hardware] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> OpenIndiana uses the SunOS libc, which severely limits what software will compile on it successfully. SunOS libc only implements functions expected by POSIX and ANSI C.{{Citation needed}} == References == 868556b3238bfd9e9e9995af682174ea61bc8a62 0 279 3653 3352 2025-08-11T05:26:14Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, ppc64, x86_64 | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == This distribution stands out by having two primary variations of the distribution: OpenSUSE Tumbleweed is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. OpenSUSE Leap is the point release version, with a new release every year with older and more stable packages meant for business use. === openSUSE Slowroll === Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. 725f12f523345d722da6c0b4f469c9e60417446d 0 641 3654 3400 2025-08-11T05:26:24Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Maintenance |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/, openbox.org] }} [[Category:Desktop Environments]] [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable [[X Window Manager|window manager]] for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>[https://openbox.org/ Home - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>[https://openbox.org/obconf ObConf - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> === Usage === While Openbox is perfectly usable on its own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], lxqt, 2025-08-09 (Accessed: 2025-08-09)</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>[https://slitaz.org/en/about/ SliTaz - About the project], SliTaz (Accessed: 2025-08-09)</ref><ref>[https://crunchbang.org/about/ About - CrunchBang], CrunchBang Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> == References == <references /> 95d30b7ed794267485a6261124ab2061a9c1a9bb 0 480 3655 3404 2025-08-11T05:54:14Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Oreon Linux |image=[[File:Oreonlogo.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop |architectures = aarch64, x86_64 |website=[https://oreonproject.org/ oreonproject.org]}} [[Category:Linux Distributions]] [[File:Oreon10-2502.png|thumb|Oreon 10 Core (Build 2502) running KDE Plasma]] '''Oreon Linux''' is an Alma Linux-based [[Linux Distributions|Linux Distribution]], developed by The Oreon Foundation and it's team. The project's goals are to provide more packages than [[wikipedia:AlmaLinux|Alma Linux]]<ref>[https://oreonproject.org/ Oreon Project - Where open source becomes something special], Oreon Project (Accessed: 2025-08-09)</ref> by porting missing packages over from [[Fedora|Fedora Linux]].<ref>[https://git.oreonproject.org/rpms <span style="color:#fc493b">https://git.oreonproject.org/rpms <sup>🍣502]</ref> The first release, ''Oreon Lime (R1/R1.1)'' was released on January 1, 2024<ref>[https://boostyconnect.com/oreon-lime-r1-lifecycle/ Oreon Lime R1/R1.1 Lifecycle], BoostyConnect, 2025-08-09 (Accessed: 2025-08-09)</ref>, but was shortly replaced with Oreon Lime (R2) bringing the Alma Linux base on February 18, 2024<ref>[https://oreonproject.org/oreon-lime-r2-support-timeline/ Oreon Lime (R2) Support Timeline], Oreon Project (Accessed: 2025-08-09)</ref><ref>[https://oreonproject.org/oreon-lime-r2/ Oreon Lime (R2)], Oreon Project (Accessed: 2025-08-09)</ref>, followed by other new releases. === History === Oreon Lime (R2) was released on February 18, 2024, shipped with GNOME 40 and Linux 5.14. This release was mentioned by The Register<ref>[https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/ Oreon Lime is AlmaLinux with a desktop twist • The Register], Liam Proven, 2024-08-20 (Accessed: 2025-08-09)</ref> and other well-known sources. In October 2024, Oreon celebrated its 1st anniversary on November 16, 2024, and mentioned that they have reached a milestone of 10,000 downloads worldwide in October.<ref>[https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69 <span style="color:#fc493b">https://forums.oreonproject.org/t/one-year-strong-celebrating-oreons-journey-and-looking-ahead/69 <sup>🍣404]</ref> Oreon 10 released to the public on December 12, 2024, shipping with KDE Plasma 6 and Linux 6.11<ref>[https://forums.oreonproject.org/t/oreon-10-officially-released/98 <span style="color:#fc493b">https://forums.oreonproject.org/t/oreon-10-officially-released/98 <sup>🍣404]</ref> but was upgraded to 6.12 a few days later. A new update to Oreon 10 has been released on February 12, 2025, under the name "Build 2502." This update brought a few bug fixes along with some planned features for later such as Apple M-series Mac support.<ref>[https://forums.oreonproject.org/t/oreon-10-build-2502-has-officially-released/150 <span style="color:#fc493b">https://forums.oreonproject.org/t/oreon-10-build-2502-has-officially-released/150 ^{🍣404]</ref> == References == <references /> d3f214c79f05389c342a33274c8822b35bf20a80 0 169 3656 3426 2025-08-11T05:54:25Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories == List of Package Managers == All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained by the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper]/[[Rpm]], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[bedrock linux]]'s special use case. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] * [[Homebrew]] (or just brew) was originally created as a package manager for macOS, but it has Linux support too. You can install it on almost any distribution as an alternative package manager. You can find more information about it on [https://brew.sh/ the official website], the source is hosted [https://github.com/Homebrew/brew on GitHub] 5ccade9bc315e0628f2e0ad95b9ecbae2f4749ba 0 175 3657 3405 2025-08-11T05:54:39Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[Category:Package Managers]] [[File:Pacman 401.png|thumb|[[Pacman]]]] The [[Linux Distributions|Linux distribution]] [[Arch Linux]] and its derivatives usually use a [[Package Manager|package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, though some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>[https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] == References == 455c66ae6557c0cf70e2cd3ed385deb21720c658 0 802 3658 3406 2025-08-11T05:54:49Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Package Manager]] '''pkgutils''' is a set of utilities (pkgadd, pkgrm, pkginfo, pkgmk and rejmerge), which are used for managing software packages in Linux. It is developed for and used by the CRUX distribution <ref>[http://crux.nu CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> All the packages installed with '''pkgutils''' are plain <code>.tar.gz</code> files. == Usage == The following are several common usages of '''pkgutils'''. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pkgadd package1.pkg.tar.gz package2.pkg.tar.gz</code> {| class="wikitable" |+Common Pkgutils Commands !Command !Description |- |<code>pkgadd package.pkg.tar.gz</code> |Install a given package |- |<code>pkgrm package</code> |Remove a given package. |- |<code>ports -u</code> |Sync ports tree |- |<code>prt-get update</code> |Sync local index with the ports tree |- |<code>prt-get upgrade</code> |Rebuild and reinstalls newer versions of installed packages |- |<code>prt-get search package</code> |Search a given package |- |<code>pkginfo -i</code> |List all installed packages |- |<code>pkginfo package</code> |Display info about a given package |} == See Also == [https://crux.nu/Main/Handbook3-7-Package pkgutils - CRUX] cbc70f8e7bfcf7f77e4c834e4557608cf9d23508 0 176 3659 2991 2025-08-11T05:55:20Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video] to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> d95745bed5959e776fa5aa58c7008ae4af94a804 0 653 3660 3353 2025-08-11T05:55:30Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox | title = Pop!_OS | image = [[File:Pop! OS Icon.svg|frameless]] | caption = The Pop!_OS logo | releasestatus = Maintained | packagemanager = [[Pacman]] | defaultdesktops = COSMIC | usagetype = Desktop | architectures = x86_64 | website = Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX] | releasemodel = Rolling release }} Pop!_OS is a free and open-sourced [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]], based on [[GNOME]], called [[COSMIC]]. Pop!OS is developed by American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. == <u>Features</u> == * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle 314e1e916fc78f5f0db4acf57f004403ea9feaf0 0 235 3661 3407 2025-08-11T05:55:46Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>[https://github.com/gentoo/portage/blob/master/NEWS portage/NEWS at master · gentoo/portage · GitHub], Gentoo Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[Category:Package Managers]] [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every [[Gentoo]] and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the [[Package Manager|package manager]], although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. === Configuration === Configuration of Portage is done through various configuration files and folders found in /etc/portage, which allows configuration of features such as USE flags, default options, masked packages and more. ==== make.conf ==== make.conf is the main configuration file for Portage. It allows the configuration of system-wide USE flags, Portage features, accepted licenses and more. This file is regularly edited during the Gentoo installation process and during ordinary use of it, so it's very important to get the options right for it. Below are some of the most relevant ones. ===== COMMON_FLAGS, CFLAGS, CXXFLAGS, FCFFLAGS and FFLAGS ===== These variables determine the build and compile flags that will be used for all package compilations. The CFLAGS variable is for C applications, while the CXXFLAGS one is meant for C++ ones. Most users will keep these variables identical. A "safe" configuration to avoid compilation errors should look like this:<blockquote><code>COMMON_FLAGS="-march=native -O2 -pipe"</code> <code>CFLAGS="${COMMON_FLAGS}"</code> <code>CXXFLAGS="${COMMON_FLAGS}"</code> <code>FCFLAGS="${COMMON_FLAGS}"</code> <code>FFLAGS="${COMMON_FLAGS}"</code></blockquote> ===== MAKEOPTS ===== The MAKEOPTS variable is used to specify arguments that will be passed to [[Make]] during compilation. A good rule of thumb is to set the -j argument to about half your RAM size and the -l argument to the thread count of your CPU, which can be found by running <code>nproc</code>. For example, if you have 4 GB of RAM and a 6th generation Intel Core i3, your MAKEOPTS variable should look something like this:<blockquote><code>MAKEOPTS="-j2 -l4"</code></blockquote> ===== GENTOO_MIRRORS ===== The GENTOO_MIRRORS variable tells Portage what mirror(s) to download the packages from. It can be set manually by editing the variable with a link to the mirror(s) of your liking available [https://www.gentoo.org/downloads/mirrors/ here], or automatically via <code>mirrorselect</code>, which can select the fastest mirror(s) for you. It's highly recommended to set this variable to a mirror close to you, for example, if you want to use an Italian mirror you would have to edit the variable like this:<blockquote><code>GENTOO_MIRRORS="<nowiki>https://gentoo.mirror.garr.it/</nowiki>"</code></blockquote> ===== FEATURES ===== The FEATURES variable contains a list of features that you can enable which notably alters the behavior of Portage. For example, if you want to use binary packages and verify their signatures, you would have to set the variable like this:<blockquote><code>FEATURES="getbinpkg binpkg-request-signature"</code></blockquote> ===== EMERGE_DEFAULT_OPTS ===== The EMERGE_DEFAULT_OPTS variable contains the options that will be automatically set when running Portage every time. For example, if you want Portage to ask for confirmation and verbose output, you would set the variable to this:<blockquote><code>EMERGE_DEFAULT_OPTS="--ask --verbose"</code></blockquote> ===== USE ===== The USE variable allows the '''system-wide''' enabling or disabling of USE flags. An example of this variable may look like this:<blockquote><code>USE="pulseaudio X systemd dbus policykit udisks dist-kernel -alsa -wayland xwayland"</code></blockquote> ===== USE_EXPAND ===== USE_EXPAND is a set of variables that serve to extend the capabilities of USE flags. Below are the most relevant ones. ====== VIDEO_CARDS ====== VIDEO_CARDS is a variable that serves to specify the drivers you wish to install for your GPUs. For example, if you want to install the drivers for AMD and Intel graphics, you would set the variable to this:<blockquote><code>VIDEO_CARDS="amdgpu radeonsi intel"</code></blockquote> ====== CPU_FLAGS_* ====== The CPU_FLAGS_* variables specify the available features that your CPU has to optimize compiling packages. The currently available variables are CPU_FLAGS_X86 (for x86 and x86_64 architectures), CPU_FLAGS_ARM (for ARM and ARM64 architectures) and CPU_FLAGS_PPC (for PowerPC and PowerPC64 architectures). The <code>cpuid2cpuflags</code> utility can be used to find these flags. The output of this command may look something like this:<blockquote><code>CPU_FLAGS_X86: aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3</code></blockquote>The output can then be copied to make.conf. ===== ACCEPT_LICENSE ===== The ACCEPT_LICENSE variable can be used to tell Portage which type of licenses are allowed. Generally, it's preferred to not accept proprietary software licenses. To allow every license except proprietary ones, you can set the variable to this:<blockquote><code>ACCEPT_LICENSE="* -@EULA"</code></blockquote> == References == 8a34e5b3714d0740f3b205f1dd3132f781fef1f8 0 405 3662 3325 2025-08-11T05:55:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] {{Cleanup|Short page}}Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Linux and other open source operating systems will avoid or not support proprietary software when possible. This is mainly due to incompatible licensing.<ref>https://solutionshub.epam.com/blog/post/proprietary-software-definition-examples Epam, 2025 (imported 27th June 2025)</ref> Some examples of proprietary software are Microsoft Windows and Adobe Photoshop. == References == 0e39ce94e0341e85b2b7739ab05510bfa7d3c28d 0 354 3663 3408 2025-08-11T05:56:26Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox | title = Puffy | image = [[File:Puffy-openbsd.gif|Puffy|222px]] }} '''Puffy''' is the current mascot of [[OpenBSD]] created by Semaka Studios used as of version 2.7. Puffy resembles a puffer-fish and has been the mascot since June 15th, 2000.<ref>[https://www.openbsd.org/27.html OpenBSD 2.7], Theo de Raadt, 2000-06-15 (Accessed: 2025-08-09)</ref> [[File:Puffyanim.gif|thumb|99x99px|Animated Puffy Render]] == References == f0d0028894880fbfda62b7a2bea1db5682eb5683 0 855 3664 3544 2025-08-11T05:56:36Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} [[Category:Software]] [[File:Pulse Visualizer.png|thumb|alt=Pulse Visualizer in CRT mode|Pulse Visualizer in CRT mode|alt=Screenshot of Pulse Visualizer displaying CRT-style visual effects.]] '''Pulse Visualizer''' is a real-time audio visualizer inspired by [https://minimeters.app/ MiniMeters] and written in [[C++]] and [[GLSL]]. It captures system audio via [[PipeWire]] or [[PulseAudio]], processes the signal through digital signal processing (DSP) stages using fftw<ref>https://fftw.org/<nowiki/>(Accessed: 2025-8-11)</ref>, libebur128<ref>https://github.com/jiixyj/libebur128<nowiki/>(Accessed: 2025-8-11)</ref> and other custom DSP methods, and renders visuals with hardware acceleration through [[OpenGL]] in an [[SDL2]] window.<ref>https://github.com/Beacroxx/pulse-visualizer Pulse Visualizer GitHub, 2025 (Accessed: 2025-08-11)</ref> === Features === Pulse Visualizer supports multiple real-time visualization modes, including stereometer, oscilloscope, spectrum analyzer, spectrogram, peak/LUFS meter, and VU meter. Users can customize the panels with features such as CRT screen emulation using GPU compute shaders, adjustable visual effects (blur, glow, chromatic aberration, vignette), and draggable, resizable panels. The application offers hot reloading of both configuration and theme files without restarting, and is compatible with Linux and BSD systems using PipeWire or PulseAudio for audio input. === References === <references /> __INDEX__ e791c94bdf1069b6753aa1f015fd3810100b3de7 3697 3664 2025-08-11T06:23:43Z Beacrox 56 Cite configuration wikitext text/x-wiki {{Needs Citations}} [[Category:Software]] [[File:Pulse Visualizer.png|thumb|alt=Pulse Visualizer in CRT mode|Pulse Visualizer in CRT mode|alt=Screenshot of Pulse Visualizer displaying CRT-style visual effects.]] '''Pulse Visualizer''' is a real-time audio visualizer inspired by [https://minimeters.app/ MiniMeters] and written in [[C++]] and [[GLSL]]. It captures system audio via [[PipeWire]] or [[PulseAudio]], processes the signal through digital signal processing (DSP) stages using fftw<ref>https://fftw.org/<nowiki/>(Accessed: 2025-8-11)</ref>, libebur128<ref>https://github.com/jiixyj/libebur128<nowiki/>(Accessed: 2025-8-11)</ref> and other custom DSP methods, and renders visuals with hardware acceleration through [[OpenGL]] in an [[SDL2]] window.<ref>https://github.com/Beacroxx/pulse-visualizer Pulse Visualizer GitHub, 2025 (Accessed: 2025-08-11)</ref> === Features === Pulse Visualizer supports multiple real-time visualization modes, including stereometer, oscilloscope, spectrum analyzer, spectrogram, peak/LUFS meter, and VU meter. Users can customize the panels with features such as CRT screen emulation using GPU compute shaders, adjustable visual effects (blur, glow, chromatic aberration, vignette), and draggable, resizable panels. The application offers hot reloading of both configuration and theme files without restarting, and is compatible with Linux and BSD systems using PipeWire or PulseAudio for audio input.<ref>https://github.com/Beacroxx/pulse-visualizer/blob/main/CONFIGURATION.md<nowiki/>(Accessed: 2025-8-11)</ref> === References === <references /> __INDEX__ 1348abe9b3d657594592d9b81fd7c1a22b0ee295 3705 3697 2025-08-12T17:20:26Z Beacrox 56 Mention cross-platform/wasapi and change sdl2 to sdl3 wikitext text/x-wiki {{Needs Citations}} [[Category:Software]] [[File:Pulse Visualizer.png|thumb|alt=Pulse Visualizer in CRT mode|Pulse Visualizer in CRT mode|alt=Screenshot of Pulse Visualizer displaying CRT-style visual effects.]] '''Pulse Visualizer''' is a cross-platform real-time audio visualizer inspired by [https://minimeters.app/ MiniMeters] and written in [[C++]] and [[GLSL]]. It captures system audio via [[PipeWire]], [[PulseAudio]] or WASAPI, processes the signal through digital signal processing (DSP) stages using fftw<ref>https://fftw.org/<nowiki/>(Accessed: 2025-8-11)</ref>, libebur128<ref>https://github.com/jiixyj/libebur128<nowiki/>(Accessed: 2025-8-11)</ref> and other custom DSP methods, and renders visuals with hardware acceleration through [[OpenGL]] in an [[SDL3]] window.<ref>https://github.com/Beacroxx/pulse-visualizer Pulse Visualizer GitHub, 2025 (Accessed: 2025-08-11)</ref> === Features === Pulse Visualizer supports multiple real-time visualization modes, including stereometer, oscilloscope, spectrum analyzer, spectrogram, peak/LUFS meter, and VU meter. Users can customize the panels with features such as CRT screen emulation using GPU compute shaders, adjustable visual effects (blur, glow, chromatic aberration, vignette), and draggable, resizable panels. The application offers hot reloading of both configuration and theme files without restarting, and is compatible with Linux and BSD systems using PipeWire or PulseAudio for audio input.<ref>https://github.com/Beacroxx/pulse-visualizer/blob/main/CONFIGURATION.md<nowiki/>(Accessed: 2025-8-11)</ref> === References === <references /> __INDEX__ 2b41f45c8e52c386963956df54b2e8401f67c13e 0 682 3665 3282 2025-08-11T05:56:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}}{{stub}} {{DistributionInfobox | title = Puppy Linux | image = [[File:Puppy logo.svg|frameless|Puppy Linux Logo]] | caption = Puppy Linux Logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]], [[XBPS]], PPM | defaultdesktops = JWM, [[Xfce]], LXDE | usagetype = Desktop | architectures = x86_64, x86, ARM | website = [https://puppylinux-woof-ce.github.io/ Link] }} '''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003. c98c1f100d0297e72b9551183fc55a3b2e726588 0 440 3666 3359 2025-08-11T05:57:36Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = ROSA Linux | image = [[File:ROSA_Linux_Logo.png|thumb]] | caption = The ROSA Linux logo | releasestatus = Abandoned | releasemodel = Stable | packagemanager = [https://rpm-software-management.github.io/ DNF package manager] | defaultdesktops = GNOME, [[KDE Plasma]], LXQt, [[Xfce]] | usagetype = Desktop, Server | architectures = P5 (i586), x86_64 | website = [https://rosa.ru/rosa-fresh-12/ rosa.ru/rosa-fresh-12] }} [[File:Rosalinux_desktop_showcase.jpeg|thumb|ROSA Linux Fresh 12 running on KDE Plasma 5 and has open Dolphin, Gwenview and mpvplayer]] '''ROSA Linux''' is a [[Linux Distributions|Linux distribution]] built around the '''OpenMandriva''', offering closed-source software such as Adobe Flash Player, proprietary multimedia codecs. It was initially developed by AO NTC IT ROSA. (rus. - АО «НТЦ ИТ РОСА») == Focus on KDE Plasma as the desktop environment == ROSA Linux is known for its focus on the KDE Plasma desktop environment, which offers a rich graphical interface and extensive customization options. This makes it an attractive choice for users who appreciate a modern and aesthetically pleasing desktop experience. == Applications == The distribution includes a wide range of pre-installed applications, covering essential tasks such as web browsing, multimedia playback, and office productivity, while also providing access to a comprehensive software repository for additional applications. == Ease of use == One of the key features of ROSA Linux is its commitment to user experience, with an emphasis on ease of use and accessibility. The distribution is designed to be intuitive, making it suitable for both newcomers to Linux and experienced users. It also supports multiple languages, catering to a diverse user base. == Multiple editions == ROSA Linux is available in several editions, including ROSA Fresh, which is aimed at general users and features the latest software updates, and ROSA Enterprise, which is tailored for business environments and focuses on stability and long-term support. With a strong emphasis on community involvement and open-source principles, ROSA Linux encourages contributions from users and developers alike. It has gained popularity in various regions, particularly in Russia and Eastern Europe, and continues to be a viable option for those seeking a reliable and visually appealing Linux distribution. 9cd00b6e483b48b67ad6cf7c4b761113c43f86e8 0 225 3667 3409 2025-08-11T05:57:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64 | website = [https://redhat.com/rhel/ redhat.com] }} [[Category:Linux Distributions]] [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business customers.<ref>[https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux Red Hat Enterprise Linux], Red Hat, 2025-08-09 (Accessed: 2025-08-09)</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. == References == <references /> 6fdf100729a96f2f1b4959cb0ce555c66b9cd86d 0 790 3668 3246 2025-08-11T05:58:06Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = Red Star OS | image = [[File:Red Star OS Logo 2020.svg|190px]] | caption = Red Star OS logo | releasestatus = Maintained | releasemodel = Unknown | packagemanager = [[rpm]] | defaultdesktops = [[KDE Plasma]], [[GNOME]] | usagetype = Desktop | architectures = [[IA-32]], [[x86-64]], [[ARM]] | website = None }} '''Red Star OS ('''Korean: 붉은별''')''' is a Red Hat Linux based distribution developed in the Democratic People's Republic of Korea (DPRK), made as a replacement for Windows in North Korea. It was first developed in 1998 by the Korea Computer Center. == Browser == '''Red Star OS''' relies on a heavily modified version of [[Firefox]] called ''[[Naenara]], which means "Our Country" in Korean.'' 9eeec773c55e7ea7e19e3f000f81c4ef2a099ce6 0 670 3669 3295 2025-08-11T05:58:46Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] '''Regular Expression''', also known as '''Regex''' or '''RegExp''', refers to a type of pattern “used to match character combinations in strings”<ref>[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript], MDN, 2025 (Accessed 2025-06-20)</ref>. It is a very powerful tool for searching, matching, replacing, and parsing target text based on specific patterns. In other words, a ''regex engine''<ref>[https://www.regular-expressions.info/engine.html How a Regex Engine Works Internally], Jan Goyvaerts, 2019 (Accessed: 2025-06-20)</ref> can find, extract and substitute target text under a format defined by a given regex. Regex is not universally the same. Different flavours of regex are supported by different regex engines provided by different libraries and programming languages. However, a portion of the syntax is generally the same across them.<ref>[https://regex101.com/ regex101: build, test, and debug regex], regex101.com, 2025 (Accessed: 2025-06-20)</ref> == Usage == Regex is used in many text processing tools. Graphical examples include the find and replace feature in [[LibreOffice]]<ref>[https://help.libreoffice.org/25.2/en-US/text/swriter/guide/search_regexp.html?&DbPAR=SHARED&System=UNIX Using Regular Expressions in Text Searches], LibreOffice, 2025 (Accessed: 2025-06-20)</ref>. [[CLI|Command line]] examples include [[AWK]], [[sed]], and [[grep]]. Many popular scripting and programming languages provide built-in support for regex, notably [[JavaScript]], [[Perl]], [[Java]], [[Ruby]], [[Python]], [[C++]], [[PHP]], each with slighting varying implementations and different sets of supported syntax.<ref>[https://www.regular-expressions.info/tools.html Popular Tools, Utilities and Programming Languages That Support Regular Expressions], Jan Goyvaerts, 2021 (Accessed: 2025-06-21)</ref> == Flavours == === Basic Regular Expression === See [https://en.wikibooks.org/wiki/Regular_Expressions/POSIX_Basic_Regular_Expressions Regular Expressions/POSIX Basic Regular Expressions] from Wikibooks for more details. In short, '''Basic Regular Expression''' (BRE) is a notable variant of regex used across different [[POSIX]] utilities, notably in [[sed#Basic Regular Expression]] and [[grep#Basic Regular Expression]]. Unlike other mainstream flavours, BRE requires backslashes to escape many of the common regex symbols and patterns, such as <code>\(''capture groups''\)</code> and repeaters like <code>\{1, 2\}</code>. Implementations of BRE may also vary across different vendors. For example, GNU extensions like <code>\?</code> and <code>\+</code> are introduced into GNU sed.<ref>[https://www.gnu.org/software/sed/manual/html_node/Regular-Expressions.html Regular Expressions - sed, a stream editor], GNU (Accessed: 2025-08-08)</ref>. === Extended Regular Expression === See [https://en.wikibooks.org/wiki/Regular_Expressions/POSIX-Extended_Regular_Expressions Regular Expression/POSIX-Extended Regular Expressions] from Wikibooks for more details. As the name suggests, '''Extended Regular Expression''' (ERE) is a POSIX extension for POSIX-compliant software to process more sophisticated regular expressions. While programs like [[AWK]] support ERE by default, others like sed and grep require an extra <code>-E</code> command-line flag. ERE is closer to other mainstream flavours in the sense that the backslash prefixes to the aforementioned patterns are removed. In addition, crucial and common patterns like <code>+</code> are introduced into ERE. == Optimisation == === Prefer Lazy Quantifiers === Greedy quantifiers such as <code>.+</code> force engines to perform ''backtracking'', where it go back each character one by one to check whether the current largest string matches the regex. In comparison, lazy quantifier allow engines to immediately process the next pattern once a match is found, because it is not required to determine whether there is a larger match. Consider the test string <code>foo bar baz</code> and the regex <code>/f.*? bar/</code>. After finding <code>f</code>, the engine accept anything until it finds a <code> bar</code> suffix. This operation is ''O(n)'' because even if the suffix fails to match, it can just continue until the matching suffix arrives. It takes a PCRE2-flavoured engine 9 steps to correctly match the string.<ref>[https://regex101.com/r/GIFDjf/2/debugger regex101: lazy match for foo bar baz], regex101, 2025-08-08 (Accessed: 2025-08-08)</ref> In contrary, <code>/f.* bar/</code> takes the same engine 18 moves instead.<ref>[https://regex101.com/r/BY5U8b/1/debugger regex101: greedy match for foo bar baz], regex101, 2025-08-08 (Accessed: 2025-08-08)</ref> The engine is required to take all characters until the end, and then, in backwards, match each character to check whether there is a valid suffix. This is done to ensure <code>.*</code> matches the largest possible portion in the test string. This operation is thus ''O(n²)'' in the worst case scenario. An even worse example like <code>(x+x+)+y</code><ref>[https://regex101.com/r/iXSKTs/1/debugger regex101: Catastrophic backtracking example], elm, 2018-05-16 (Accessed: 2025-08-08)</ref> have an even worse exponential complexity of ''O(2ⁿ)''.<ref>[https://www.regular-expressions.info/catastrophic.html Runaway Regular Expressions: Catastrophic Backtracking], Jan Goyvaerts, 2021 (Accessed: 2025-08-08)</ref> These examples are how the phrase “''catastrophic backtracking''” was born.<ref>[https://www.w3docs.com/learn-javascript/catastrophic-backtracking.html Catastrophic Backtracking], W3docs (Accessed: 2025-08-08)</ref> === Limit Matches === Adding anchors to regexes may speed up the matching process so that the engine does not need to check for every character in the test string.<ref name=":0">[https://jsdev.space/howto/optimize-regex/ Optimizing Regex for Better Performance], JSDev Space, 2025-01-03 (Accessed: 2025-08-08)</ref> Common anchors include <code>^</code> (start of line) and <code>$</code> (end of line) in multi-line mode. Other checks like <code>\b</code> (word boundary) could serve similar purposes.<ref>[https://www.loggly.com/blog/five-invaluable-techniques-to-improve-regex-performance/ Five Invaluable Techniques to Improve Regex Performance], Liz Bennett, 2015-06-30 (Accessed: 2025-08-08)</ref> On the other hand, adding more complicated checks like lookahead checks could speed up<ref name=":0" /> or slow down<ref>[https://last9.io/blog/regex-optimization-techniques/#technique-10-use-lookaheadslookbehinds-judiciously Regex Optimization Techniques: 14 Methods for DevOps Performance | Last9], Anjali Udasi, 2025-04-10 (Accessed: 2025-08-08)</ref> the engine. === Atomic Grouping === The <code>(?>''atomic group'')</code> reduces backtracking by forcing the engine to discard all backtracking positions in the group after leaving the group.<ref>[https://www.regular-expressions.info/atomic.html Atomic Grouping], Jan Goyvaerts, 2022-11-21 (Accessed: 2025-08-08)</ref> === Possessive Quantifiers === Possessive quantifiers including <code>*+</code>,<code>++</code>, etc. are basically syntactic sugar for greedy quantifiers within an atomic group.<ref>[https://www.regular-expressions.info/possessive.html Possessive Quantifiers], Jan Goyvaerts, 2022-11-21 (Accessed: 2025-08-08)</ref> === Approximate Optimisation === When processing large files, it could be beneficial to split a regex into 2 different regexes to improve the pipeline. This allows approximate optimisation, which is an advanced technique for reducing the time needed to find matches within large test strings: <syntaxhighlight lang="sh"> # Slow: Check 'cat' / 'dog' / 'bird' sed -nE 's/(cat|dog|bird)/animal/gp' large_file.txt # Faster: Check single characters first grep '[cdb][aoi][tgr]' large_file.txt | sed -nE 's/(cat|dog|bird)/animal/gp' </syntaxhighlight> This does not always create improvements, so make sure to perform benchmarks before implementing this optimisation. == See Also == * [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions Regular expressions - JavaScript | MDN] * [https://regex101.com/ regex101: build, test, and debug regex] == References == 186a0fe1577178058a6818f7e9e32ed68c174655 0 319 3670 3326 2025-08-11T05:59:28Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] {{Needs Citations}}'''Ricing''' (''slang'') refers to extensively customizing a [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to create a unique, personalized computing experience. The term originated from the automotive modification scene ("ricer" cars) and has been adopted by the Linux/Unix community. While primarily focused on aesthetic customization through themes, colors, widgets, and interface layouts, ricing can improve functionality and performance. Common ricing elements include: * Custom window borders, titlebars, decorations; * Color schemes and typography; * Specialized status bars and system monitors; * Custom application launchers and menus * Personalized desktop widgets and notifications * Modified system icons and cursors Popular tools for ricing include customization frameworks such as polybar and picom for window managers like i3, bspwm, and dwm. People frequently share configuration files, or "dotfiles," and screenshots - [https://www.reddit.com/r/unixporn/ r/unixporn] is one of the most popular. b2a890d16772ace11f8b78d83d063f14c15f21c2 0 277 3671 3336 2025-08-11T05:59:38Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_Logo.png|thumb]] | caption = Rocky Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[Category:Linux Distributions]] [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] Rocky Linux is a Linux distribution developed by RESF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit". It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. 36d4e4f97ca6d6c6ab5fd9870a88f3acbc101ffb 0 781 3672 3167 2025-08-11T05:59:49Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Package Managers]] = RPM Packages = '''RPM''' stands for '''Red Hat Package Manager'''. It is both a package format (`.rpm`) and the name of the package management system used primarily in Red Hat-based Linux distributions, including: * Red Hat Enterprise Linux (RHEL) * Fedora * CentOS * AlmaLinux * Rocky Linux * openSUSE (with some differences) == Overview == An RPM package is a file that contains: * Compiled software binaries * Configuration files * Metadata (name, version, dependencies, etc.) * Installation and removal scripts The standard file extension is `.rpm`. RPM packages are used to install, update, and remove software cleanly and consistently, while tracking file ownership and managing dependencies. == RPM vs DEB == RPM is used in Red Hat-based systems, while DEB is used in Debian-based systems (like Ubuntu). Both serve similar purposes but are not interchangeable. == Components of an RPM Package == * **Header**: Contains metadata (name, version, architecture, etc.) * **Payload**: The actual files to be installed * **Scripts**: Optional pre/post-install and removal scripts == Common Tools == * `rpm` — Low-level tool for querying, installing, and removing RPM packages * `dnf` or `yum` — High-level package managers that resolve dependencies and interact with repositories * `rpmbuild` — Tool for building RPM packages from SPEC files * `rpmlint` — Linter to check RPM quality and packaging errors == Basic Commands == === Installing an RPM file === <syntaxhighlight lang="bash"> sudo rpm -ivh package.rpm </syntaxhighlight> Or using DNF (which handles dependencies): <syntaxhighlight lang="bash"> sudo dnf install ./package.rpm </syntaxhighlight> === Query installed packages === <syntaxhighlight lang="bash"> rpm -q package-name </syntaxhighlight> === List all installed RPMs === <syntaxhighlight lang="bash"> rpm -qa </syntaxhighlight> === Remove a package === <syntaxhighlight lang="bash"> sudo rpm -e package-name </syntaxhighlight> === Verify a package === <syntaxhighlight lang="bash"> rpm -V package-name </syntaxhighlight> == Advantages == * Dependency tracking * Transaction-based installation/removal * Clean upgrade paths * Strong ecosystem support (DNF, YUM, repositories, etc.) == Limitations == * Requires careful dependency management * Not compatible with DEB systems * Binary format — not human-readable == External Resources == * [https://rpm.org/ Official RPM Site] * [https://fedoraproject.org/wiki/RPM Fedora RPM Guide] * [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Fedora Packaging Guidelines] == See Also == * [[YUM]] * [[DNF]] * [[rpmbuild]] 6b49a17e68bd5b42272e947bcc1901eb69063fc3 0 558 3673 3297 2025-08-11T06:00:00Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[C]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called “garbage collecting,” where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[#Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" lines> struct MyStruct { field1: bool, field2: i32, field3: String, } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: MyStruct = MyStruct { field1: true, field2: 64, field3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height // This returns the Cube's Volume } } fn main() { let rubiks_cube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's volume: {}", rubiks_cube.volume()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an area finder function within the <code>impl Cube</code> scope. We are able to use the <code>volume()</code> method on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing], Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == 01a5d96fddf244a67db9759fb9042989f167cd3c 0 447 3674 3356 2025-08-11T06:00:31Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} Self-hosting is a rewarding practice that allows you to reduce reliance on cloud services, giving you much greater control and privacy over the data you own. By self-hosting, the services you use, and by extension anything you store with those services, reside on your own hardware rather than third-party servers. Essentially, the “cloud” is just someone else's computer, often a large, multi-billion-dollar infrastructure. However, with self-hosting, you own the data on the devices you manage. == What is Self-Hosting? == Self-hosting often refers to the process of running and managing your own services on personal hardware such as a laptop, desktop, single-board computer, or even an enterprise-grade server. This means you can set up and operate services for yourself, your family, or others without depending on external cloud platforms. == What Can I Host? == There are numerous possibilities for self-hosting, depending on your needs. Some popular options include: * Email server * Password manager * Personal website * File hosting service * Media server * VPN (Virtual Private Network) == Do I Need Anything Special to Self-Host? == [[File:Homelab.jpg|thumb|Example of an enterprise grade homelab]] The requirements are minimal. You can self-host using almost any device, from an old, cheap laptop to a single-board computer like a Raspberry Pi. Some enthusiasts take this a step further and use second-hand enterprise equipment from real data center infrastructure to host their services. These setups are often referred to as “HomeLabs.” However, anything that can connect to the internet or your local area network can be sufficient. == The Challenges of Self-Hosting == Like everything in life, self-hosting has its challenges. When hosting services at home, you are responsible for maintaining and fixing any problems that arise. Unlike cloud services, which are typically plug-and-play, homelabs require regular maintenance to ensure stable operation. Below are some challenges many homelab users encounter. === Common Problems === * '''Electricity Usage''' - One of the main concerns with starting a homelab is power consumption. As your homelab grows, so will its electricity usage. Additionally, the services you run rely on your home's power grid, meaning power outages can affect your services. [[File:Speedtest.png|thumb|Example of a users internet speed.]] * '''Internet Speed''' - Not all internet connections are equal. When exposing services to the outside world, consider how much bandwidth they will consume. A slow connection or data caps can limit what you can host effectively. Residential internet plans might not support the load or violate fair use policies. Like the electricity usage, you are relying on the reliance your ISP provides. * '''Natural Disasters''' - Hosting services in areas prone to natural disasters poses risks. If a disaster damages your homelab, your data may be lost along with the equipment. * '''Vulnerabilities''' - Even with the latest software and hardware, vulnerabilities persist. Tools like Shodan.io scan for exposed services, potentially attracting malicious actors. Without sufficient protection, your services may be at risk. * '''Hardware Failures''' - Nothing lasts forever. Self-hosted services depend on your hardware, which will need maintenance and occasional replacement. Hard drives, in particular, are susceptible to failure over time. * '''Sound''' - Unlike a laptop or a single-board computer, enterprise equipment is not built to be quiet. It is designed to run cool and avoid failure, which often results in high-pitched fan noise due to large amounts of airflow. * '''Dust''' - Most homelabs are not housed in ventilated data centers, leading to dust accumulation, which can clog and damage equipment. * '''User Error''' - Mistakes happen. Deleting the wrong files, modifying incorrect configurations, or failing to double-check changes can lead to data loss or downtime. == Solutions == [[File:Ups uninterruptible power supply.jpg|thumb|An example of an (UPS) Uninterruptible Power Supply]] * '''Electricity Usage''' - Use an Uninterruptible Power Supply (UPS). A UPS acts as a battery backup and protects against power surges. If the power goes out, the UPS switches to battery mode to keep your equipment running. UPS devices can range from small 600W models to large 10kW units that can power enterprise equipment for hours. * '''Internet Speed''' - If your internet is slow or capped, consider upgrading to a better plan if available. Some ISPs offer small business plans for residential users, providing higher speeds, service agreements, and multiple external IP addresses. * '''Natural Disasters''' - Perform regular off-site backups. Store data in locations unaffected by the same natural disasters as your homelab to ensure redundancy. * '''Vulnerabilities''' - To mitigate vulnerabilities some examples include: ** Keep all software and hardware up to date. ** Change default ports for commonly scanned services. ** Install a firewall. ** Use a VPN to access services instead of exposing them directly to the internet. ** Use encrypted protocols and storage. [[File:raid failure.png|thumb|An example of a drive failing in a raid.]] *'''Hardware Failures''' - Practice the 3-2-1 backup strategy: ** Keep at least THREE copies of your data. ** Use at least TWO types of storage. ** Keep at least ONE copy off-site. * '''Sound''' - To mitigate noise, consider buying fanless equipment, as fans are the primary source of noise. Alternatively, place the equipment in a room that is not frequently used to minimize sound. Keep in mind that fanless equipment carries a risk of overheating. * '''Dust''' - Regularly clean your equipment and store it in well-ventilated areas. Use compressed air or vacuum cleaners to remove dust. * '''User Error''' - Double-check all changes, avoid running unfamiliar commands, and thoroughly understand what you are deploying. dcd5282841d340bc6b77dec4b4338ece48c4c21d 0 304 3675 3411 2025-08-11T06:00:52Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Misc Operating Systems]] {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | architectures = x86-64 | caption = The SerenityOS logo | releasestatus = Maintained | title = SerenityOS | usagetype = Desktop, Development | website = [https://serenityos.org serenityos.org] | image = [[File:SerenityOS logo.png|200px|SerenityOS_logo]] | releasemodel = In development | packagemanager = Ports | defaultdesktops = SerenityOS desktop }} SerenityOS is a [[UNIX|UNIX-like]] [[Operating System|operating system]] completely written from scratch, which has been in continuous development since 2018, with its first version releasing on October 10, 2018. Originally, it was solely developed by Andreas Kling as a one-man project.<ref name=":0">[[wikipedia:SerenityOS|SerenityOS - Wikipedia]]</ref><ref name=":1">[https://serenityos.org/ SerenityOS], SerenityOS (Accessed: 2025-08-09)</ref> The system supports the x86-64 instruction set (though work is currently at the early stages to support AArch64 and RISC-V), features a preemptive [[kernel]], and hosts multiple complex applications including its own web browser, [[Ladybird]], and integrated development environment (IDE).<ref name=":0" /> SerenityOS aims to be a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems such as [[Microsoft Windows]] and [[MacOS]]. Incorporating third-party code into the system is discouraged. The Ladybird web browser, for instance, does not use a pre-existing web engine such as [[WebKit]], instead using its own known as LibWeb. There is a collection of ported software, such as [[GCC]], [[Git]] and [[Doom]], with varying levels of functionality.<ref name=":0" /><ref name=":1" /> [[File:SerenityOS screenshot.png|alt=Screenshot of SerenityOS displaying various applications.|thumb|Screenshot of SerenityOS displaying various applications.]] There are no available SerenityOS ISO images that can be downloaded to run the operating system directly, requiring users to compile the base system and build an image for use with a [[Virtual Machine|virtual machine]] like [[QEMU]]. The same can be said for any precompiled binary packages, requiring users to [[Compiling|compile]] software from a ports collection for use with the operating system.<ref name=":0" /><ref>[https://github.com/SerenityOS/serenity/blob/master/Documentation/FAQ.md serenity/Documentation/FAQ.md at master · SerenityOS/serenity · GitHub], SerenityOS, 2025-08-09 (Accessed: 2025-08-09)</ref> == References == 1845c9eae579c905499126a481c4f33e4f516538 0 233 3676 3517 2025-08-11T06:01:02Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware_logo_from_the_official_Slackware_site.svg{{!}}class=skin-invert|frameless|upright=0.8|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[Category:Linux Distributions]] [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17th 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16th, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>[http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf A history of Slackware development], Eric Hameleers, 2009-10-09 (Accessed: 2025-08-09)</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with KDE * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3rd, 2022 with the release of Slackware 15.0. == References == 1beb47dda59aef9dbd68a11b37d0241bd935cfa8 0 309 3677 3474 2025-08-11T06:01:37Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png.png|thumb]] |thumb]] | caption = Sudo used on [[whoami]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.17p2 | languages = [[C]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} [[Category:Software]] [[File:Sudo_logo_(2019).png|thumb|335x335px|Sudo's logo of a sandwich]] [[File:Sudo Insults.png|thumb|335x335px|Output from sudo when <code>Defaults insults</code> is added]] The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]).<ref name=":0">[https://man7.org/linux/man-pages/man8/sudo.8.html sudo(8)], Linux Manpages</ref> Its name is shorthand for "su 'do'"<ref>[https://www.sudo.ws/ sudo.ws], Sudo Developers</ref>, however as <code>su</code> stands for "substitute user"<ref>[https://man7.org/linux/man-pages/man1/su.1.html su(1)], Linux Manpages</ref> this would stand for "substitute user, do". System administrators may configure sudo by editing the <code>/etc/sudoers</code> file<ref name=":0" /> to specify which users or groups can execute specific commands. == Usage == {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |Run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser''<ref name=":0" /> == Trivia == * Sudo's logo is a sandwich in reference to [https://xkcd.com/149/ xkcd 149]<ref>[https://www.sudo.ws/about/logo/ sudo.ws/about/logo], Sudo Developers</ref> * If you add the line <code>Defaults insults</code> to the Defaults section of <code>/etc/sudoers</code>, you will be insulted whenever you type the wrong password.<ref>[https://www.geeksforgeeks.org/when-sudo-insults-you/ When sudo insults you!!], GeeksforGeeks, September 13, 2023 (February 12, 2025)</ref> == References == 7820473ac3cf69737b0ca20832743c4b70124fb7 0 517 3678 2877 2025-08-11T06:02:13Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}} A system call (syscall) is a mechanism that allows a program to interact with the [[Operating System|operating system]]. It acts as a bridge between the user space (where applications run) and the kernel space (where the operating system manages hardware and system resources). Programs use system calls to request services from the OS, such as managing files, processes, or hardware devices. For example, when you open a file, your application cannot directly access the hardware. Instead, it makes a system call (e.g., open()), which the OS handles to perform the requested task. Note that this is not a guide for ALL syscalls, but it is a guide to get you familiar enough with syscalls and strace. == Why Should You Learn About System Calls? == 1. Understanding How Programs Work: - System calls reveal how applications interact with the operating system to perform tasks like file handling, memory management, and networking. 2. Efficient Troubleshooting: - Knowing system calls can help diagnose performance issues or bugs by identifying which calls a program relies on. 3. Optimizing Software: - When developing programs, understanding system calls allows you to write efficient code by leveraging the right OS-level functions. 4. Security Awareness: - Many exploits and vulnerabilities target how system calls are used (or misused). Understanding them helps in writing secure code. 5. Kernel-Level Development: - If you're interested in low-level programming, such as operating system development or driver creation, system calls are fundamental. Basically, system calls are the foundation of how software and operating systems interact, making them essential knowledge for both beginner and advanced developers. == Categories of System Calls == System calls are grouped into five main categories: '''Process Control''' – Manage processes (create, terminate, etc.). '''File Management''' – Handle file operations (open, read, write, close). '''Device Management''' – Interact with hardware devices. '''Information Maintenance''' – Exchange information between the OS and programs. '''Communication''' – Enable processes to communicate. 1. '''Process Control''' * fork(): Creates a new process (child) that runs the same program as the parent. * exit(): Terminates the process and frees resources. * exec(): Replaces the current program in a process with a new one. 2. '''File Management''' * open(): Opens a file for reading or writing. * read(): Reads data from a file (multiple processes can read simultaneously). * write(): Writes data to a file (only one process can write at a time). * close(): Closes an open file. 3. '''Device Management''' * ioctl(): Performs device-specific operations not covered by standard calls (e.g., configuring hardware). 4. '''Information Maintenance''' * getpid(): Returns the process ID of the current process. * alarm(): Sets a timer to deliver a signal after a specified time. * sleep(): Pauses the process for a given time. 5. '''Communication''' * pipe(): Enables communication between processes via file descriptors. * shmget(): Allocates shared memory for process communication. * mmap(): Maps files or devices into a process's memory. === Why Use strace? === * Debug program behavior (e.g., "Why is this program failing?"). * Identify which files, devices, or network resources a program accesses. * Learn what system calls a program makes for educational purposes. ae5846365707f57ed2ab34c561f9d2935fab0321 0 516 3679 2856 2025-08-11T06:02:23Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Instructions should be seperated into its own Guide page}} {{Needs_Citations}} Systemd is an init system and service manager used by many modern [[Linux Distributions|Linux distributions]]. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here's how Systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': Systemd provides a unified system for managing services, devices, logs, and even network interfaces. * '''Dependency Management''': Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': Systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in Systemd == Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit's dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''Systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''Systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''Systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential Systemd Commands == Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash">systemctl start service-name</syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash">systemctl stop service-name</syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash">systemctl restart service-name</syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash">systemctl enable service-name</syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash">systemctl disable service-name</syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the `/lib/systemd/system/` directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there. * Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. '''Runtime Directory''' The `/run/systemd/system/` directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File '''sudo nano /etc/systemd/system/daily-script.service''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File '''sudo nano /etc/systemd/system/daily-script.timer''' Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer '''sudo systemctl enable daily-script.timer''' '''sudo systemctl start daily-script.timer''' 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: '''systemctl list-timers''' This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With OnCalendar, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from `/lib/systemd/system/` to `/etc/systemd/system/` and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with `.d`. Example: To modify `dummy.service`, create a folder named `dummy.service.d` in `/etc/systemd/system/`. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a `.conf` file to specify your changes. Example: `/etc/systemd/system/dummy.service.d/custom.conf`. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. /etc/systemd/system/ (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. /run/systemd/system/ (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. /lib/systemd/system/ (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. '''systemctl status service-name''' * Displays the status of a specific service, including whether it's running and any associated error messages. 2. '''journalctl -u service-name''' * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. '''systemctl list-units --failed''' * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. '''systemctl daemon-reload''' * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. 6df0c32486301135cfb3a74423dfec9569791bf2 0 174 3680 3537 2025-08-11T06:02:33Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Incomplete page}} [[Category:Terminology]] [[File:Btop.png|alt=Btop System Monitor|thumb|Btop, a terminal-based system monitoring tool.]] A terminal user interface (TUI) is a form of user interface where a program prints special characters that are interpreted by the terminal renderer and are completely invisible, but manipulate the way the terminal renders stuff like for example changing the color of the following text, moving the cursor to an arbitrary place in the terminal, making text bold, making text italic, changing the color palette of the Linux TTY, and so much more. The program can also read in keyboard input by reading special character sequences in sent by the terminal driver. '''<u>FUN FACT</u>''': You may have tried using your arrow keys once or twice to move your cursor in a prompt from a program such as the [[Pacman]] package manager or something else that throws prompts for the user to answer. You may have noticed that instead of moving your cursor, the arrow keys send "garbage" text ("^[[D^[[C^[[A^[[B"). Programs such as [https://www.gnu.org/software/bash/ Bash] are able to move your cursor when you hit the arrow keys by actually reading and interpreting this "garbage" text in real-time using a terminal configuration mode called "raw mode" which is when the terminal disables a bunch of buffering settings that would normally require you to press ENTER before the terminal can see your user input. {| class="wikitable" |+Terminal Manipulation Libraries !Library !Language !Developer !Description |- |[https://gitlab.com/Oglo12/otmlib Oglo's Terminal Manipulation Library] |[[C (programming language)|C]] |Jackson Novak (OgloTheNerd) |A single-header C99 library for manipulating the terminal. |- |[https://invisible-island.net/ncurses/ NCurses] |[[C (programming language)|C]] |Thomas Dickey |A library installed on most Linux and BSD systems for creating terminal user interfaces. |- |[https://crates.io/crates/crossterm Crossterm] |[[Rust]] |Timon |A cross-platform terminal manipulation library written in Rust. |- |[https://github.com/termbox/termbox2 Termbox2] |[[C (programming language)|C]] |Adam |A suckless single-header C library for manipulating the terminal. |} 866bacb8a4c999e8fd516fc738271de3d9709f6f 0 663 3681 3003 2025-08-11T06:02:48Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terra.fyralabs.com terra.fyralabs.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora]] Linux and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terra.fyralabs.com/ Terra], Terra, 2024 (Accessed: 2025-06-19)</ref> Developed by Fyra Labs, it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://developer.fyralabs.com/terra/infrastructure How Terra Works], Fyra Labs, 2025 (Accessed: 2025-06-19)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://developer.fyralabs.com/terra/installing. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji], RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://developer.fyralabs.com/terra/autoupdate Automatic Updates - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases :: Fedora Docs], Fedora, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably Rust, Go, [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://developer.fyralabs.com/terra/policy Policy – Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> == See Also == * [https://terra.fyralabs.com Main Website] * [https://developer.fyralabs.com/terra Fyra Developer Documentations for Terra] * [https://github.com/terrapkg/packages Terra Sources] == References == f3e19594c7dfc8ec80d26fde989d07415dd9a24a 0 764 3682 3099 2025-08-11T06:03:19Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Misc Operating Systems]] Tilck is a tiny monolithic [[kernel]] designed to be compatible with [[Linux]] on the binary level. It currently runs on the i686 and RISCV64 architectures, with plans to port it to ARM. It is intended for embedded systems due to its very small size and low-latency abilities. While Linux-compatible, Tilck does not aim to replace the Linux kernel, nor to be an alternative to it for desktop users. In its current state, Tilck implements about ~100 Linux system calls, allowing many programs intended for Linux to work out of the box. While not currently implemented, the developers plan to implement Networking at some point, with the network cards of specific SoC being the initial targets.<ref>{{Cite|url=https://github.com/vvaltchev/tilck|title=Tilck: A Tiny Linux-Compatible Kernel|author=Vladislav K. Valtchev|year=Nov 22, 2024|accessdate=August 2, 2025}}</ref> == References == <references /> 14029591e974d37007df0489c9b4f9547a8ceb53 0 341 3683 2670 2025-08-11T06:03:33Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:Tde-logo.png]] | caption = Trinity Desktop Environment logo | title = Trinity Desktop Environment | releasestatus = Maintained | lastrelease = R14.1.3, 2024-10-27 | languages = [[C++]] | developers = Trinity Development Team | website = [https://www.trinitydesktop.org/ trinitydesktop.org] }} [[Category:Desktop Environments]] [[File:Trinity R.14.1.3 screenshot.png|thumb|Screenshot of Trinity Desktop R14.1.3]] Trinity Desktop Environment (TDE) is an X11 [[Desktop Environments|desktop environment]] for [[Unix-Like]] [[Operating System|Operating systems]] forked from KDE 3.5 in 2010. Trinity is packaged for [[Arch Linux]], [[Debian]], [[Fedora]], [[Gentoo]], [[Mageia]], [[OpenSUSE]], [[Raspberry Pi OS]], [[Red Hat Enterprise Linux]], [[Slackware]], [[Ubuntu]] and various other [[Linux Distributions|distributions]] df5227db5eeb39a8a5a6d1b36fbe66ff1d33428c 0 214 3684 3413 2025-08-11T06:03:47Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Mascots]] {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Tux | image = [[File:Tux.svg|frameless|size=200px]] | caption = Tux! }} '''Tux''' is the official mascot of [[Linux]], designed by Larry Ewing.<ref>[https://web.archive.org/web/20040401161253/http://www.linux.org/info/logos.html Linux Online - Linux Logos and Mascots], Linux Online Inc, 2004-08-09 (Accessed: 2004-04-01)</ref> Tux was created for the Linux 2.0 logo competition.<ref>[https://web.archive.org/web/20040407092622/http://www.cs.earlham.edu/~jeremiah/linux-pix/linux-logo.html Linux Logo Competition], Jeremiah E. Jahn, 2004-08-09 (Accessed: 2004-04-07)</ref> == References == <references /> 99620944a58e0e63e8cf85fee49e0d303f246913 0 667 3685 3191 2025-08-11T06:04:09Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Incomplete page}} {{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}} '''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. The owner of the UNIX® trademark has been The Open Group since 1994.<ref>[https://unix.org/what_is_unix.html What is UNIX ®?] unix.org</ref> Examples of modern UNIX operating systems include Apple's MacOS and IBM AIX. Being genetic UNIX® is not required for UNIX® certification. Formerly, Inspur K-UX was certified UNIX®, specifically versions 2.0 and 3.0. Inspur K-UX's UNIX® certification expired in February 2019 and has yet to be renewed.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Inspur_K-UX|title=Inspur K-UX|author=Huihermit|year=21 January 2025|accessdate=2 August 2025}}</ref> == References == 1e22a994b63e678838ef75c1fe94d48bc597bc3b 0 248 3686 3005 2025-08-11T06:04:19Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu Logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[GNOME]], [[Unity]] | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu is a highly popular [[Linux Distributions|Linux distribution]] derived from [[Debian]] and developed by Canonical for the commercial market. The first version of Ubuntu was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS version receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubuntu receive 9 months of support.<ref>https://ubuntu.com/about/release-cycle Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> Ubuntu can be run locally, on a cloud, or in a [[Virtual Machine|VM]]. Ubuntu comes packaged with basic GNOME utilities as default and additionally from Ubuntu Software (formally Ubuntu Software Centre) and from APT, Ubuntu's default package manager. == References == <references /> c5abd02aec2866c84178f959005b931602ceb465 0 317 3687 3414 2025-08-11T06:04:41Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}}{{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm Void Linux: Distribution mit XBPS-Paketverwaltung], Pro-Linux, 2015-06-12 (Accessed: 2025-08-09)</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and Musl variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses the homegrown [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for runit. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == 078b19a65dc28b2dc9e4c49dd6c7cdab503bcb24 0 281 3688 3007 2025-08-11T06:04:55Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:X_Window_Managers]] {{SoftwareInfobox | caption = Window Maker and GNUstep logo | developers = Window Maker developers | image = [[File:GNUstep logo.png|200px|GNUstep_logo]] | languages = [[C]] | lastrelease = 0.96.0, 2023-08-05 | releasestatus = Maintained | title = Window Maker | website = [https://windowmaker.org/ windowmaker.org] }} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home] official Window Maker Website, 2025 (Imported 16th June 2024)</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home] Dockapps Website, 2025 (Imported 16th June 2024)</ref> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more. == References == <references /> 82544c7ab1bdf60e26ee1f7c3a257e7a9df6d000 0 602 3689 3208 2025-08-11T06:05:16Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Window Management Systems]] {{Work In Progress}} == Disambiguation Page == This page will serve as a disambiguation page between [[Wayland Compositors]] ([[:Category:Wayland Compositors|Category]]) and [[X Window Manager|X Window Manager's]] ([[:Category:X Window Managers|Category]]). cc3e9c8477e03b7d70e3255e06e80d053eaf4c62 0 643 3690 3416 2025-08-11T06:05:26Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox |title = XBPS |releasestatus = Maintained |lastrelease = 0.59.2, 2023-08-18 |firstrelease = 0.1beta1, 2009-08-17 |languages = [[C]] |developers = [[Void Linux]] |website = [https://github.com/void-linux/xbps github.com/void-linux/xbps] }} The ''X Binary Package System'' (XBPS) is developed by the maintainers of [[Void Linux]] and is the package manager for their distribution. It was built from scratch, with the goals of speed, ease of use while being feature rich and portable. It is fully compatible with POSIX, SUSv2 and C99 standards<ref>[https://github.com/void-linux/xbps#xbps GitHub - void-linux/xbps: The X Binary Package System (XBPS)], Void Linux, 2025-08-09 (Accessed: 2025-08-09)</ref>, and is released under the BSD 2-Clause (Simplified) license ([https://spdx.org/licenses/BSD-2-Clause.html SPDX: BSD-2-Clause]). == Tools == XBPS is comprised of a number of utilities that provide different functionality, the ''core'' utility programs are as follows (not a complete list): {| class="wikitable" !<u>Name</u> !<u>Function</u> |- |xbps-create |Creating binary packages |- |xbps-dgraph |Generating graphs for tools like [https://graphviz.org GraphViz] |- |xbps-install |Installing and updating packages |- |xbps-pkgdb |Reporting and fixing issues with the package database |- |xbps-query |Querying package and repository information |- |xbps-reconfigure |Configuration of installed package (e.g., the system C library or Linux kernel) |- |xbps-remove |Removing packages |- |xbps-rindex |Handling local package repositories |} == Usage<ref>[https://github.com/void-linux/xbps?tab=readme-ov-file#examples GitHub - void-linux/xbps: The X Binary Package System (XBPS)], Void Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> == {| class="wikitable" !<u>Command</u> !<u>Description</u> |- |<code>xbps-install -Su</code> |Synchronize with repositories and apply all available updates |- |<code>xbps-query -Rs <name></code> |Search through repository packages using the given name |- |<code>xbps-install <package></code> |Install a package by name |- |<code>xbps-remove -R <package></code> |Remove a package by name; along with its dependent packages which are no longer needed by the system |- |<code>xbps-query -Rf <package></code> |List files owned by a package |- |<code>xbps-query -Ro /usr/bin/ls</code> |Find the package(s) that own/provide a file path, (e.g., the 'ls' command) |- |<code>xbps-reconfigure -f glibc-locales</code> |Regenerate your locale(s) when using a GLIBC based system<ref>[https://man.voidlinux.org/xbps-reconfigure xbps-reconfigure(1) - Void Linux manpages], Void Linux, 2023-02-09 (Accessed: 2025-08-09)</ref>|} == References == 393bb29a1fb627008af011fdc1bec381141eb7a7 0 236 3691 3417 2025-08-11T06:05:46Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|XFCE logo]] | caption = XFCE logo | title = XFCE | releasestatus = Maintained | lastrelease = Xfce 4.20, 2024-12-15 | languages = [[C]] | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[Category:Desktop Environments]] [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]] Xfce is a lightweight [[Desktop Environments|desktop environment]] aiming to be fast for weaker hardware while still remaining user friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * [[Desktop Manager]] - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[TUI|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal based calendar and a CD and DVD burning application.<ref>[https://xfce.org/about About – Xfce], Xfce Development Team, 2021-11-10 (Accessed: 2025-08-09)</ref> == References == af4a67ec723bbb9f8295565112119bcb75c6cf71 0 306 3692 3358 2025-08-11T06:05:58Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] [[Category:Window Management Systems]] {{Work_In_Progress}} A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent GUI. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as dwm.  == Types of Window Manager == === Stacking/Floating Window Managers === Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm * [[Wayfire]] === Tiling Window Managers === Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * i3 * [[Sway]] * [[SwayFx]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] === Dynamic Window Managers === Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * [[dwl]] * qtile * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] === Scrollable Window Managers === Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[PaperWM]] * [[karousel]] * [[papersway]] * [[PaperWM.spoon]] aa4efec94e52e0403b73ef5a98fb6fe084b21c0f 0 586 3693 3010 2025-08-11T06:06:18Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox | title = Xenia (Linux Fox) | image = [[File:Xenia the Linux Fox.gif]] | caption = The original design of Linux Fox, created by Al Mackey in 1996 }} Xenia was a candidate logo and [[:Category:Mascots|mascot]] for the [[Linux]] project. She was a competitor to [[Tux]], who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds)<ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ Why the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!], Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson.<ref>[https://archive.is/wYsFh Penguins and Other Things], Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on [[Gentoo]].<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> == References == <references /> 2f7f7823c25a7642a23a8303c9656b8e76f1e195 0 568 3694 2702 2025-08-11T06:06:28Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Mascots]] {{Needs_Citations}} {{MascotInfobox | title = Xue | image = [[File:Xfce-xue.jpg |frameless |alt=A small black illustrated mouse]] | caption = Xue the XFCE mascot }} Xue is the mascot of [https://xfce.org/ XFCE] Xue is described as a black female mouse in [https://supertuxkart.net/Main_Page SuperTuxKart] f813303dc430fe7a7754a0cbc3e7d1e1d5225d17 0 784 3696 3430 2025-08-11T06:07:09Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = GNOME | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }} Zorin OS is a ubuntu based linux distribution made for newcomers to linux, with a modifyed version of the Gnome GUI and XFCE 4 that is familiar to windows users. it also has paid model that comes with more desktop options and free software. it was frist realsed on the frist of july, 2009, under the name Zorin OS 1.0 ef7607b71eb44afd621aa7a287c313086f56502c 3000 695 3698 2698 2025-08-11T07:27:07Z Peanut 229 Added entry for openSUSE. wikitext text/x-wiki === Installation === ==== On [[Debian]] and Debian-based distributions: ==== You can sometimes install using a software manager, such as [[synaptic]].<syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> ==== On [[OpenSUSE]] Tumbleweed or Leap: ==== <syntaxhighlight lang="bash"> sudo zypper in i3 </syntaxhighlight> == <u>See Also</u> == [[I3]] 0eb42f41d5987dc8330791d397a2291dc888a055 0 853 3699 3617 2025-08-11T15:11:38Z Platzmacher 245 Added the GPL and LGPL section and unfinished AGPL section wikitext text/x-wiki {{Work_In_Progress}} The '''GNU General Public License''' (short '''GNU GPL''' or '''GPL''') is a collection of copyleft license published by the Free Software Foundation (FSF) and written by Richard Stallman<ref>https://archive.ph/20120907170559/http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html</ref>. This License is also part of the [[GNU]] project === Copyleft === A copyleft license requires that any modifications or extensions to a program licensed under a copyleft license must also be licensed under the same (or a compatible) license. === "or-later" clause === All GNU GPL licenses may contain an optional clause, an “or-later” clause (sometimes referred to as a “lifeboat clause”). This clause allows all later versions to be used. Programs without this clause are referred to as “only.” for example * GNU GPLv2-or-later can also be licensed under GNU GPLv3-or-later without any problem * GNU GPLv2-only can only be licensed under the GNU GPLv2 The same applies to the GNU AGPL and LGPL licenses. The FSF recommends using the “or-later” clause, as it is compatible with future versions of the GNU GPL, since GNU GPLv2 and v3 are not compatible and therefore a program licensed only under GNU GPLv2 cannot be mixed with a GNU GPLv3 program. == Licenses == There are three versions of the GNU GPL, with version 3 being the most recent version for all of them. # GNU General Public License (GPL) – The standard strong copyleft license used for most programs. # GNU Lesser General Public License (LGPL) – A weak copyleft license mainly used for libraries. # GNU Affero General Public License (AGPL) – Similar to the GPL, but also covers use over a network. === GNU General Public License (GPL) === This license is used for regular programs such as the Linux kernel, which uses GNU GPLv2 only. The latest version is the GNU General Public License Version 3 (GNU GPLv3), which was released in June 2007<ref>https://www.gnu.org/licenses/gpl-3.0.en.html#license-text </ref> and can be found [https://www.gnu.org/licenses/gpl-3.0.en.html#license-text here]. If part of a program (e.g., a library) uses this license, the entire program must be licensed under the GNU GPL. If this is not desired, the GNU LGPL or another license should be used. === GNU Lesser General Public License (LGPL) === The GNU LGPL (formerly known as the Library General Public License) was created at the same time as the GNU GPLv2 and was also published in June 2007, but the first version was called GNU LGPLv2 to match the GNU GPLv2. This license was created because the GNU GPL was too restrictive, especially for libraries. If a program uses a library licensed under the GNU LGPL, only the modification of that library must be published. This allows a library to be used in [[Proprietary software]] The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/lgpl-3.0.html here] === GNU Affero General Public License (AGPL) === The GNU AGPL was created to close a loophole when modified software licensed under the GNU GPL was run on a server the source code dont need to be published because of that the AGPL was created to fix this loophole The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/agpl-3.0.html#license-text here] <references /> 64a5a46268577dab75d507861869e73d6495c50e 6 867 3700 2025-08-11T15:31:11Z Madonuko 140 https://www.cutefishos.com/ wikitext text/x-wiki == Summary == https://www.cutefishos.com/ 3e26ec79e63201b4178c1f4b209d85f872c348cb 0 848 3701 3515 2025-08-11T15:36:20Z Madonuko 140 /* CyberDE */ wikitext text/x-wiki [[category:Linux Distributions]] [[category:Desktop Environments]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued in around 2022 to 2023<ref>[https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2022 (Accessed: 2022-05-14)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the DE, and Arch Linux was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to Ubuntu. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were remove and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The new CutefishOS team which was rebased to Sichuan also did not live long due to lack of Western support, and silently died out between mid-2021 and 2022. === CutefishOS Reborn === CutefishOS Reborn was a Western community's attempt to revive CutefishOS's development. It gauged some interest but very quickly died off in mid-2022. === LingmoOS === [https://github.com/LingmoOS/LingmoOS LingmoOS] is an active revive<ref>[https://github.com/orgs/cutefishos/discussions/22 Is this project dead or still in development? · cutefishos · Discussion #22], GitHub, 2023 (Accessed: 2025-08-11)</ref> of CutefishOS, but it has not received major attention from the media. == CyberDE == [[File:VSCode In Cutefish.png|thumb|right|Visual Studio Code running on CutefishDE.<ref>[https://cutefishos.com CutefishOS], Cutefish Team, 2025 (Accessed: 2025-08-11)</ref>]] The desktop environment that came with CyberOS, usually referred to as ''Cyber'' or ''CyberDE'', was made using Qt5 and was commonly said to resemble the look and feel of Mac OS X.<ref>[https://wiki.archlinux.org/title/Cutefish Cutefish], ArchWiki (Accessed: 2025-08-11)</ref> <code>cyber-launcher</code> came with the dock at the bottom, which had a button that opens the launcher, and a status line bar with embedded global context menus at the top. Many parts of the interface were also partially transparent. Window controls were at the top right corner and resembles [[Microsoft Windows]], while titles were centred. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives] == References == ac254bc937e29c58eb28ad6cc3b84c3af9486b9d 6 868 3702 2025-08-11T17:36:22Z Platzmacher 245 Logo of the GNU GPLv3 License wikitext text/x-wiki == Summary == Logo of the GNU GPLv3 License == Licensing == {{PD}} 77741fcc394704df78831c7c4ecb3c27145299c2 14 397 3703 3536 2025-08-11T20:05:27Z OgloTheNerd 248 Added games section. wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == {| class="wikitable" |+Text Editors !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} {| class="wikitable" |+System Utilities !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[opendoas|OpenDoas]] |Ted Unangst |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} {| class="wikitable" |+Installers !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} {| class="wikitable" |+Useless But Fun !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} {| class="wikitable" |+Programming !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} {| class="wikitable" |+Open-Source Music Players !Application !Developer !Ecosystem (If Any) !UI Framework |- |[https://mierak.github.io/rmpc RMPC] |Mierak (And Others) |[https://www.musicpd.org/ MPD] |[https://crates.io/crates/ratatui Ratatui] ([[TUI]]) |- |[https://github.com/ncmpcpp/ncmpcpp NCMPCPP] |Andrzej Rybczak (And Others) |[https://www.musicpd.org/ MPD] |NCurses ([[TUI]]) |- |[https://musikcube.com/ Musikcube] |Casey Langen |Musikcube (Custom) |NCurses ([[TUI]]) |} {| class="wikitable" |+Shells !Application !Developer |- |[https://www.gnu.org/software/bash/ Bash] |[[GNU]] |- |[https://fishshell.com/ Fish] |Axel Liljencrantz (And Others) |- |[https://www.zsh.org/ ZSH] |Peter Stephenson |} {| class="wikitable" |+Open-Source Games !Game !Description !Genre |- |[https://www.supertux.org/ SuperTux] |A free and open-source platformer game inspired by Super Mario Bros. |Platformer |- |[https://supertuxkart.net SuperTuxKart] |A free and open-source racing game inspired by Super Mario Kart. |Racer |- |[https://xonotic.org Xonotic] |A free and open-source shooter game based on the Quake engine. |Shooter |- |[https://neverball.org/ Neverball] |Tilt the floor to roll a ball through an obstacle course before time runs out. Neverball is part puzzle game, part action game, and entirely a test of skill. |Puzzler |- |[https://github.com/jorio/Bugdom Bugdom (Ported For Modern Systems)] |Bugdom is a 1999 Macintosh game by Pangea Software. You play as Rollie McFly, a pill bug on a quest to save ladybugs from King Thorax’s iron grip on the Bugdom. |Quest Adventure |- |[https://www.classicube.net/ ClassiCube] |A free and open-source voxel game inspired by Minecraft Classic. |Sandbox |- |[https://tuxracer.sourceforge.net/ Extreme Tux Racer] |A free and open-source game where Tux tries to glide on his belly all the way down to the finish line before the time is up. |Racer |- |[https://www.teeworlds.com/ Teeworlds] |Teeworlds is a '''free online multiplayer game''', available for '''all major operating systems'''. Battle with up to '''16 players''' in a variety of game modes, including '''Team Deathmatch''' and '''Capture The Flag'''. You can even '''design your own maps!''' |Competitive |- |[https://www.luanti.org/ Luanti (Formerly Minetest)] |A free and open-source voxel game engine. |Sandbox |- |[https://veloren.net/ Veloren] |Veloren is an action-adventure role-playing game set in a vast fantasy world. |Action Adventure |- |[https://play0ad.com/ 0 A.D.] |'''0 A.D.''' (pronounced “zero-ey-dee”) is a free, open-source, historical Real Time Strategy (RTS) game currently under development by Wildfire Games, a global group of volunteer game developers. As the leader of an ancient civilization, you must gather the resources you need to raise a military force and dominate your enemies. |Real-Time Strategy |- |[https://github.com/seehuhn/moon-buggy Moon Buggy] |A free and open-source terminal-based game where you jump over craters. |Action |- |[https://www.victornils.net/tetris/ Vitetris] |A free and open-source recreation of Tetris that can be played in your terminal. |Real-Time Strategy |- |[https://crates.io/crates/tui48 Tui48] |An elegant and faithful 2048 clone in the terminal. (Written in Rust.) |Strategy |} 511059a9128240e5a2c1f9370a084e273cc27e1f 0 239 3704 3627 2025-08-12T10:58:23Z Smeech 252 Corrected Website URL wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 3.5.1, 2024-06-06 | languages = [[C++]], [[C]] | developers = Marko Maček, community contributors | website = [https://ice-wm.org/ ice-wm.org] }} [[Category:X_Window_Managers]] [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]] IceWM is a fast, simple and light X11 [[Window Management System|window manager]]. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. <references /> a1442dabd4dad8b1b8123fe89c754b4374670ab3 2 869 3706 2025-08-13T04:22:22Z Poseidon 255 Added basic page about myself. wikitext text/x-wiki <blockquote>The only true wisdom is in knowing you know nothing. — Socrates</blockquote> Hi, I'm Poseidon (you may know me as Coolio or Cool-Game-Dev). I'm an Arch turned NixOS user, avid FOSS supporter, and programmer. d4d40b67f6da9ec734d1337586673bf36771d9d1 0 268 3707 3610 2025-08-13T04:37:26Z Poseidon 255 Add citation to the FastFetch GitHub page. wikitext text/x-wiki [[Category:Software]] [[Category:Command-line software]] [[Category:System information tools]] {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch running on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.15.0, 2024-06-06 | languages = [[C (programming language)|C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch GitHub repository] }} '''Fastfetch''' is a cross-platform command-line utility for displaying system information, similar in purpose to [[Neofetch]]. It is primarily written in [[C (programming language)|C]] and is designed with a strong focus on speed and low resource usage. Fastfetch can display details about the [[Operating system|operating system]], hardware components, and installed software in a highly configurable format<ref name=":0">{{Cite|url=https://github.com/fastfetch-cli/fastfetch|title=Fastfetch GitHub page}}</ref>. The tool supports a wide range of modules, allowing users to customise the output to include information such as CPU, GPU, memory, storage, display resolution, kernel version, package count, and more. It is actively maintained and available for Linux, macOS, and Windows<ref name=":0" />. == See also == * [[Neofetch]] * [[Screenfetch]] == References == <references /> 6c889b1f5112ab93c5933c32b42c9a54c96d78ca 0 762 3708 3081 2025-08-13T04:43:47Z Poseidon 255 Add short page cleanup banner. wikitext text/x-wiki {{Cleanup|Short Page}} Zypper is OpenSUSE's package manager. Built on top of SAT Solver, Zypper is known to be blazing fast. Zypper includes shortened cmdlets to add on to how fast Zypper truly is. These include: in (install),rm (remove),dup (distribution upgrade). More information on Zypper can be found [https://en.opensuse.org/Portal:Libzypp here]. 3acd538040fc974a63ead94233e7e3d53f102a12 3713 3708 2025-08-13T05:19:04Z Madonuko 140 stub wikitext text/x-wiki {{stub}} Zypper is OpenSUSE's package manager. Built on top of SAT Solver, Zypper is known to be blazing fast. Zypper includes shortened cmdlets to add on to how fast Zypper truly is. These include: in (install),rm (remove),dup (distribution upgrade). More information on Zypper can be found [https://en.opensuse.org/Portal:Libzypp here]. 5723b7cf0cc7dd83e636bfc6d365f339969a35a6 3000 695 3709 3698 2025-08-13T04:53:16Z Poseidon 255 Add installation guide for NixOS. wikitext text/x-wiki === Installation === ==== On [[Debian]] and Debian-based distributions: ==== You can sometimes install using a software manager, such as [[synaptic]].<syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight>'''On [[NixOS]] and NixOS-based distributions, add the following to your configuration.nix:'''<syntaxhighlight lang="nixos"> services.xserver.windowManagers.i3.enable = true; </syntaxhighlight> == <u>See Also</u> == [[I3]] 94d23bbdeb6e4cf6c2bc83be5a507797902483a2 3710 3709 2025-08-13T04:56:04Z Madonuko 140 Undo revision [[Special:Diff/3709|3709]] by [[Special:Contributions/Poseidon|Poseidon]] ([[User talk:Poseidon|talk]]) wikitext text/x-wiki === Installation === ==== On [[Debian]] and Debian-based distributions: ==== You can sometimes install using a software manager, such as [[synaptic]].<syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> ==== On [[OpenSUSE]] Tumbleweed or Leap: ==== <syntaxhighlight lang="bash"> sudo zypper in i3 </syntaxhighlight> == <u>See Also</u> == [[I3]] 0eb42f41d5987dc8330791d397a2291dc888a055 3711 3710 2025-08-13T05:00:42Z Poseidon 255 Fix formatting error wikitext text/x-wiki === Installation === ==== On [[Debian]] and Debian-based distributions: ==== You can sometimes install using a software manager, such as [[synaptic]].<syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> ==== On [[OpenSUSE]] Tumbleweed or Leap: ==== <syntaxhighlight lang="bash"> sudo zypper in i3 </syntaxhighlight> ==== On [[NixOS]] and NixOS-based distributions ==== <syntaxhighlight lang="nixos"> services.xserver.windowManagers.i3.enable = true; </syntaxhighlight> == <u>See Also</u> == [[I3]] 9565cbde995c1aabee98331b41e19026a26ad735 3729 3711 2025-08-14T02:44:32Z Poseidon 255 /* On OpenSUSE Tumbleweed or Leap: */ Add missing $ from shell command wikitext text/x-wiki === Installation === ==== On [[Debian]] and Debian-based distributions: ==== You can sometimes install using a software manager, such as [[synaptic]].<syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> ==== On [[OpenSUSE]] Tumbleweed or Leap: ==== <syntaxhighlight lang="bash"> $ sudo zypper in i3 </syntaxhighlight> ==== On [[NixOS]] and NixOS-based distributions ==== <syntaxhighlight lang="nixos"> services.xserver.windowManagers.i3.enable = true; </syntaxhighlight> == <u>See Also</u> == [[I3]] 8bf988afed8cd155cef56206f55b239072f6805d 3 870 3712 2025-08-13T05:04:21Z Madonuko 140 /* Your Edit in Guides:Installing i3 */ new section wikitext text/x-wiki == Your Edit in [[Guides:Installing i3]] == Your [https://atl.wiki/index.php?title=Guides:Installing_i3&curid=695&diff=3709&oldid=3698 latest edit] that attempted to add the nix instructions removed the openSUSE instructions, which is why it's been reverted. If you would like to perform the edit again, make sure existing content is not removed without justification, and follow existing heading formats. Also what's your username on Discord? might want to add that to your wiki profile. ー [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 05:04, 13 August 2025 (UTC) 78e205f0d7534af016ff97472ec5ca7aa1ab4157 10 631 3714 3101 2025-08-13T06:05:45Z Madonuko 140 set accessdate to required in visual editor wikitext text/x-wiki <includeonly>{{#if: {{{url|}}}|''[{{{url}}} {{{title}}}]''|''{{{title|Untitled Source}}}''}}{{#if: {{{author|}}}|, {{{author|Anon.}}}}}{{#if: {{{year|}}}|, {{{year}}}}} {{#if: {{{accessdate|}}}| (Accessed: {{{accessdate}}})}}</includeonly><noinclude><templatedata> { "params": { "url": { "label": "URL", "description": "The URL to access the content cited, this can be an archive.org link if the available source is offline.", "type": "url", "required": true }, "title": { "label": "Title", "description": "The title of the works, the citation is from", "type": "content", "required": true, "default": "Untitled Source" }, "author": { "label": "Author", "description": "The author of the content cited", "type": "content", "suggested": true, "default": "Anon." }, "year": { "label": "Year", "description": "The year of publication of the content cited", "type": "number", "suggested": true }, "accessdate": { "label": "Access Date", "type": "date", "description": "The date the source cited was accessed.", "required": true } }, "description": "Add a citation using our recommended structure to a page" } </templatedata></noinclude> d03c5d2812d3aaacc8fc8f04af6cdaa2537cb703 2 3 3715 3539 2025-08-13T07:55:37Z Amadaluzia 52 Mention Keyoxide wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <functional> #include <print> using String = std::string; class Person { virtual String description() = 0; }; using SocialPair = struct { String service; String username; }; class Amadaluzia : Person { public: String name = "Artur Manuel"; int age = 17; std::vector<String> interests{ "Programming", "CLI development", "GUI development", "Web development", "Library development", "System administration", "Walking", "Climbing", "Math", "Learning", "Exercise", "Sports", "Socialising", "Writing", "Photography", "Video editing", "Movie production", "Techno music", "Shoegaze", "Alternative Rock", }; std::vector<SocialPair> socials = { {"Email", "amad@atl.tools"}, {"Email (tutanota.com alt)", "amadaluzia@tutanota.com"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Matrix (pub.solar alt)", "@amadaluzia:pub.solar"}, {"Matrix (envs.net alt)", "@amadaluzia:envs.net"}, {"libera.chat", "amadaluzia"}, {"oftc.net", "amadaluzia"}, {"Revolt", "amadaluzia#3242"}, {"Mastodon", "@amadaluzia@bsd.cafe"}, {"Discord", "amadaluzia"}, {"Discord (alt)", "balke.nix"}, {"Keyoxide": "aspe:keyoxide.org:ZV3A66CSCNOS7V4N5A4DOD57I4"}, }; String description() override; }; String Amadaluzia::description() { String result{}; result += std::format("Good day, my name is {}, commonly known online as \"amadaluzia\". I am a {}\n", name, age); result += "year old Portuguese-Italian resident of the UK. You may have seen me in many\n"; result += "programming spaces, however, I am keenly interested in many other topics. More\n"; result += "specifically, I am interested in:\n"; for (auto interest : interests) result += std::format("- {}\n", interest); result += "I am also present on many social media platforms, even multiple times! Moreover, I\n"; result += "have pretty much the same name everywhere, so you can reliably find me. But I will\n"; result += "share my social platforms here as I use many decentralised services. Here I am:\n"; for (auto const &[service, username] : socials) result += std::format("- {} on {}\n", username, service); result += "\nIf you can find any ways of optimising this program, let me know, as long as the\n"; result += "it's kept to Amadaluzia::description(). Thank you for reading!\n"; return result; } int main(void) { Amadaluzia amadaluzia; std::println("{}", amadaluzia.description()); }</syntaxhighlight> 2ff29d46d4f5c3571ebd192f7e18a41fa5dd2d54 14 390 3716 3466 2025-08-13T09:36:47Z UBU 256 /* Linux Kernel Mascots */ wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[FreeBSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Tuz.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tuz]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] |[[Linux]] |} 9b7b8bd7511f9d94f0773e5187f979e3d3b501fd 0 217 3717 3611 2025-08-13T10:03:29Z Wilbur 142 syetem -> system wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Semi-Rolling Release |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}} [[Category:Linux Distributions]] [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[ https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref> == Release system == Fedora current follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], </nowiki>'''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</nowiki></ref> System upgrades are usually handled offline to prevent system breakage == The package management system == the Package manager [[dnf]] , is usually called with the following arguments * <code>sudo dnf up</code> --- updates system packages * <code>sudo dnf in <pkg names> <...></code> --- install new packages * <code>sudo dnf rm <pkg names> <...></code> --- remove packages * <code>sudo dnf system-upgrade --relesever=<rel></code> --- updates system version and packages<ref>[https://dnf.readthedocs.io/<nowiki> DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</nowiki></ref> == References == <references /> dadcbe841f336bccb58633948f1c551f287adfda 6 871 3718 2025-08-13T10:19:42Z Satnus 215 Transparent Go logo. wikitext text/x-wiki == Summary == Transparent Go logo. 6f0e14643001e1c80682e5d165a695afff585bc5 3719 3718 2025-08-13T10:28:31Z Satnus 215 Satnus uploaded a new version of [[File:Golang-logo.png]] wikitext text/x-wiki == Summary == Transparent Go logo. 6f0e14643001e1c80682e5d165a695afff585bc5 6 872 3720 2025-08-13T10:33:55Z Satnus 215 Actual transparent & official Go logo. wikitext text/x-wiki == Summary == Actual transparent & official Go logo. 5be499e79b0606e59f7bce627cb5163b8be0a8fa 10 513 3721 3522 2025-08-13T14:05:22Z Madonuko 140 fix empty lines wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This template is to be used on pages which may lack credible citations, as per our [[ATL:Guidelines#Citations|citations guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Needs_Citations|| [[Category:Needs_Citations]] }}</includeonly> <noinclude> {{/doc}}</noinclude> 7737486c7483a16c251332812c832928cb21e7d3 0 269 3722 3586 2025-08-13T14:06:23Z Madonuko 140 fix bad website link wikitext text/x-wiki [[Category:Desktop Environments]] {{Needs Citations}} {{SoftwareInfobox | image = [[File:Budgie.svg|thumb]] | caption = Budgie Logo | title = Budgie | releasestatus = Maintained | lastrelease = 10.9.1 | languages = [[Vala]] | developers = Buddies of Budgie | website = [https://buddiesofbudgie.org/ buddiesofbudgie.org] }} The '''Budgie Desktop''' is a feature-rich, modern [[Desktop Environment|desktop environment]] designed to keep out the way of the user. Based on [[GNOME]], Budgie provides an easy to use Interface for everyone. Raven provides an all-in-one center for accessing your calendar, controlling sound output and input (including per-app volume control), media playback and more. [[File:BudgieScreenshot.jpg|thumb|Screenshot of Budgie DE with Raven]] == Features == '''Budgie Desktop View''' is a [[:Category:Software|software]] component meant to provide desktop icons within Budgie. Budgie Desktop View is implemented in Vala, and uses GTK 3 for widgets. '''Magpie''' is a fork of the GNOME Project's Mutter window manager with [[Wayland]] support removed, principally intended to reduce the maintenance burden of GNOME stack upgrades by stabilizing on a particular version of the Mutter API. '''Budgie Control Center''' is a fork of GNOME Control Center with Budgie-specific settings and features, and is the standard settings application for Budgie. Budgie Control Center is implemented in [[C]], and uses GTK 3 and libhandy for widgets. '''Budgie Screensaver''' is a fork of GNOME Screensaver with additional fixes and minor updates, and serves to provide an authentication prompt when the system is locked. Budgie Screensaver is implemented in C, and uses GTK 3 for widgets. '''Budgie Backgrounds''' is Budgie's default set of background images for use with Linux distributions that do not provide their own, and is entirely composed of public domain images. cd6aa01795b0b3efcc8ecdbf0e0e8faa5f121837 2 817 3723 3304 2025-08-13T16:33:24Z Madonuko 140 jwb? javascript text/javascript mw.loader.load('https://en.wikipedia.org/w/index.php?title=User:Joeytje50/JWB.js/load.js&action=raw&ctype=text/javascript'); 5f312793154a6efe61b31cdb2c72e8d90bd8c190 3724 3723 2025-08-13T16:35:47Z Madonuko 140 nah javascript text/javascript da39a3ee5e6b4b0d3255bfef95601890afd80709 3725 3724 2025-08-13T16:36:39Z Madonuko 140 wtf javascript text/javascript ; 2d14ab97cc3dc294c51c0d6814f4ea45f4b4e312 828 873 3726 2025-08-13T17:59:35Z Ow0cast 249 mod | stealing some modules from wikipedia Scribunto text/plain --[[ This module is intended to provide access to basic string functions. Most of the functions provided here can be invoked with named parameters, unnamed parameters, or a mixture. If named parameters are used, Mediawiki will automatically remove any leading or trailing whitespace from the parameter. Depending on the intended use, it may be advantageous to either preserve or remove such whitespace. Global options ignore_errors: If set to 'true' or 1, any error condition will result in an empty string being returned rather than an error message. error_category: If an error occurs, specifies the name of a category to include with the error message. The default category is [Category:Errors reported by Module String]. no_category: If set to 'true' or 1, no category will be added if an error is generated. Unit tests for this module are not available at Module:String/tests. ]] local str = {} --[[ len This function returns the length of the target string. Usage: {{#invoke:String|len|target_string|}} OR {{#invoke:String|len|s=target_string}} Parameters s: The string whose length to report If invoked using named parameters, Mediawiki will automatically remove any leading or trailing whitespace from the target string. ]] function str.len( frame ) local new_args = str._getParameters( frame.args, {'s'} ) local s = new_args['s'] or '' return mw.ustring.len( s ) end --[[ sub This function returns a substring of the target string at specified indices. Usage: {{#invoke:String|sub|target_string|start_index|end_index}} OR {{#invoke:String|sub|s=target_string|i=start_index|j=end_index}} Parameters s: The string to return a subset of i: The first index of the substring to return, defaults to 1. j: The last index of the string to return, defaults to the last character. The first character of the string is assigned an index of 1. If either i or j is a negative value, it is interpreted the same as selecting a character by counting from the end of the string. Hence, a value of -1 is the same as selecting the last character of the string. If the requested indices are out of range for the given string, an error is reported. ]] function str.sub( frame ) local new_args = str._getParameters( frame.args, { 's', 'i', 'j' } ) local s = new_args['s'] or '' local i = tonumber( new_args['i'] ) or 1 local j = tonumber( new_args['j'] ) or -1 local len = mw.ustring.len( s ) -- Convert negatives for range checking if i < 0 then i = len + i + 1 end if j < 0 then j = len + j + 1 end if i > len or j > len or i < 1 or j < 1 then return str._error( 'String subset index out of range' ) end if j < i then return str._error( 'String subset indices out of order' ) end return mw.ustring.sub( s, i, j ) end --[[ This function implements that features of {{str sub old}} and is kept in order to maintain these older templates. ]] function str.sublength( frame ) local i = tonumber( frame.args.i ) or 0 local len = tonumber( frame.args.len ) return mw.ustring.sub( frame.args.s, i + 1, len and ( i + len ) ) end --[[ _match This function returns a substring from the source string that matches a specified pattern. It is exported for use in other modules Usage: strmatch = require("Module:String")._match sresult = strmatch( s, pattern, start, match, plain, nomatch ) Parameters s: The string to search pattern: The pattern or string to find within the string start: The index within the source string to start the search. The first character of the string has index 1. Defaults to 1. match: In some cases it may be possible to make multiple matches on a single string. This specifies which match to return, where the first match is match= 1. If a negative number is specified then a match is returned counting from the last match. Hence match = -1 is the same as requesting the last match. Defaults to 1. plain: A flag indicating that the pattern should be understood as plain text. Defaults to false. nomatch: If no match is found, output the "nomatch" value rather than an error. For information on constructing Lua patterns, a form of [regular expression], see: * http://www.lua.org/manual/5.1/manual.html#5.4.1 * http://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Patterns * http://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Ustring_patterns ]] -- This sub-routine is exported for use in other modules function str._match( s, pattern, start, match_index, plain_flag, nomatch ) if s == '' then return str._error( 'Target string is empty' ) end if pattern == '' then return str._error( 'Pattern string is empty' ) end start = tonumber(start) or 1 if math.abs(start) < 1 or math.abs(start) > mw.ustring.len( s ) then return str._error( 'Requested start is out of range' ) end if match_index == 0 then return str._error( 'Match index is out of range' ) end if plain_flag then pattern = str._escapePattern( pattern ) end local result if match_index == 1 then -- Find first match is simple case result = mw.ustring.match( s, pattern, start ) else if start > 1 then s = mw.ustring.sub( s, start ) end local iterator = mw.ustring.gmatch(s, pattern) if match_index > 0 then -- Forward search for w in iterator do match_index = match_index - 1 if match_index == 0 then result = w break end end else -- Reverse search local result_table = {} local count = 1 for w in iterator do result_table[count] = w count = count + 1 end result = result_table[ count + match_index ] end end if result == nil then if nomatch == nil then return str._error( 'Match not found' ) else return nomatch end else return result end end --[[ match This function returns a substring from the source string that matches a specified pattern. Usage: {{#invoke:String|match|source_string|pattern_string|start_index|match_number|plain_flag|nomatch_output}} OR {{#invoke:String|match|s=source_string|pattern=pattern_string|start=start_index |match=match_number|plain=plain_flag|nomatch=nomatch_output}} Parameters s: The string to search pattern: The pattern or string to find within the string start: The index within the source string to start the search. The first character of the string has index 1. Defaults to 1. match: In some cases it may be possible to make multiple matches on a single string. This specifies which match to return, where the first match is match= 1. If a negative number is specified then a match is returned counting from the last match. Hence match = -1 is the same as requesting the last match. Defaults to 1. plain: A flag indicating that the pattern should be understood as plain text. Defaults to false. nomatch: If no match is found, output the "nomatch" value rather than an error. If invoked using named parameters, Mediawiki will automatically remove any leading or trailing whitespace from each string. In some circumstances this is desirable, in other cases one may want to preserve the whitespace. If the match_number or start_index are out of range for the string being queried, then this function generates an error. An error is also generated if no match is found. If one adds the parameter ignore_errors=true, then the error will be suppressed and an empty string will be returned on any failure. For information on constructing Lua patterns, a form of [regular expression], see: * http://www.lua.org/manual/5.1/manual.html#5.4.1 * http://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Patterns * http://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Ustring_patterns ]] -- This is the entry point for #invoke:String|match function str.match( frame ) local new_args = str._getParameters( frame.args, {'s', 'pattern', 'start', 'match', 'plain', 'nomatch'} ) local s = new_args['s'] or '' local start = tonumber( new_args['start'] ) or 1 local plain_flag = str._getBoolean( new_args['plain'] or false ) local pattern = new_args['pattern'] or '' local match_index = math.floor( tonumber(new_args['match']) or 1 ) local nomatch = new_args['nomatch'] return str._match( s, pattern, start, match_index, plain_flag, nomatch ) end --[[ pos This function returns a single character from the target string at position pos. Usage: {{#invoke:String|pos|target_string|index_value}} OR {{#invoke:String|pos|target=target_string|pos=index_value}} Parameters target: The string to search pos: The index for the character to return If invoked using named parameters, Mediawiki will automatically remove any leading or trailing whitespace from the target string. In some circumstances this is desirable, in other cases one may want to preserve the whitespace. The first character has an index value of 1. If one requests a negative value, this function will select a character by counting backwards from the end of the string. In other words pos = -1 is the same as asking for the last character. A requested value of zero, or a value greater than the length of the string returns an error. ]] function str.pos( frame ) local new_args = str._getParameters( frame.args, {'target', 'pos'} ) local target_str = new_args['target'] or '' local pos = tonumber( new_args['pos'] ) or 0 if pos == 0 or math.abs(pos) > mw.ustring.len( target_str ) then return str._error( 'String index out of range' ) end return mw.ustring.sub( target_str, pos, pos ) end --[[ str_find This function duplicates the behavior of {{str_find}}, including all of its quirks. This is provided in order to support existing templates, but is NOT RECOMMENDED for new code and templates. New code is recommended to use the "find" function instead. Returns the first index in "source" that is a match to "target". Indexing is 1-based, and the function returns -1 if the "target" string is not present in "source". Important Note: If the "target" string is empty / missing, this function returns a value of "1", which is generally unexpected behavior, and must be accounted for separatetly. ]] function str.str_find( frame ) local new_args = str._getParameters( frame.args, {'source', 'target'} ) local source_str = new_args['source'] or '' local target_str = new_args['target'] or '' if target_str == '' then return 1 end local start = mw.ustring.find( source_str, target_str, 1, true ) if start == nil then start = -1 end return start end --[[ find This function allows one to search for a target string or pattern within another string. Usage: {{#invoke:String|find|source_str|target_string|start_index|plain_flag}} OR {{#invoke:String|find|source=source_str|target=target_str|start=start_index|plain=plain_flag}} Parameters source: The string to search target: The string or pattern to find within source start: The index within the source string to start the search, defaults to 1 plain: Boolean flag indicating that target should be understood as plain text and not as a Lua style regular expression, defaults to true If invoked using named parameters, Mediawiki will automatically remove any leading or trailing whitespace from the parameter. In some circumstances this is desirable, in other cases one may want to preserve the whitespace. This function returns the first index >= "start" where "target" can be found within "source". Indices are 1-based. If "target" is not found, then this function returns 0. If either "source" or "target" are missing / empty, this function also returns 0. This function should be safe for UTF-8 strings. ]] function str.find( frame ) local new_args = str._getParameters( frame.args, {'source', 'target', 'start', 'plain' } ) local source_str = new_args['source'] or '' local pattern = new_args['target'] or '' local start_pos = tonumber(new_args['start']) or 1 local plain = new_args['plain'] or true if source_str == '' or pattern == '' then return 0 end plain = str._getBoolean( plain ) local start = mw.ustring.find( source_str, pattern, start_pos, plain ) if start == nil then start = 0 end return start end --[[ replace This function allows one to replace a target string or pattern within another string. Usage: {{#invoke:String|replace|source_str|pattern_string|replace_string|replacement_count|plain_flag}} OR {{#invoke:String|replace|source=source_string|pattern=pattern_string|replace=replace_string| count=replacement_count|plain=plain_flag}} Parameters source: The string to search pattern: The string or pattern to find within source replace: The replacement text count: The number of occurences to replace, defaults to all. plain: Boolean flag indicating that pattern should be understood as plain text and not as a Lua style regular expression, defaults to true ]] function str.replace( frame ) local new_args = str._getParameters( frame.args, {'source', 'pattern', 'replace', 'count', 'plain' } ) local source_str = new_args['source'] or '' local pattern = new_args['pattern'] or '' local replace = new_args['replace'] or '' local count = tonumber( new_args['count'] ) local plain = new_args['plain'] or true if source_str == '' or pattern == '' then return source_str end plain = str._getBoolean( plain ) if plain then pattern = str._escapePattern( pattern ) replace = string.gsub( replace, "%%", "%%%%" ) --Only need to escape replacement sequences. end local result if count ~= nil then result = mw.ustring.gsub( source_str, pattern, replace, count ) else result = mw.ustring.gsub( source_str, pattern, replace ) end return result end --[[ simple function to pipe string.rep to templates. ]] function str.rep( frame ) local repetitions = tonumber( frame.args[2] ) if not repetitions then return str._error( 'function rep expects a number as second parameter, received "' .. ( frame.args[2] or '' ) .. '"' ) end return string.rep( frame.args[1] or '', repetitions ) end --[[ escapePattern This function escapes special characters from a Lua string pattern. See [1] for details on how patterns work. [1] https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Patterns Usage: {{#invoke:String|escapePattern|pattern_string}} Parameters pattern_string: The pattern string to escape. ]] function str.escapePattern( frame ) local pattern_str = frame.args[1] if not pattern_str then return str._error( 'No pattern string specified' ) end local result = str._escapePattern( pattern_str ) return result end --[[ count This function counts the number of occurrences of one string in another. ]] function str.count(frame) local args = str._getParameters(frame.args, {'source', 'pattern', 'plain'}) local source = args.source or '' local pattern = args.pattern or '' local plain = str._getBoolean(args.plain or true) if plain then pattern = str._escapePattern(pattern) end local _, count = mw.ustring.gsub(source, pattern, '') return count end --[[ endswith This function determines whether a string ends with another string. ]] function str.endswith(frame) local args = str._getParameters(frame.args, {'source', 'pattern'}) local source = args.source or '' local pattern = args.pattern or '' if pattern == '' then -- All strings end with the empty string. return "yes" end if mw.ustring.sub(source, -mw.ustring.len(pattern), -1) == pattern then return "yes" else return "" end end --[[ join Join all non empty arguments together; the first argument is the separator. Usage: {{#invoke:String|join|sep|one|two|three}} ]] function str.join(frame) local args = {} local sep for _, v in ipairs( frame.args ) do if sep then if v ~= '' then table.insert(args, v) end else sep = v end end return table.concat( args, sep or '' ) end -- findpagetext returns the position of a piece of text in a page -- First positional parameter or |text is the search text -- Optional parameter |title is the page title, defaults to current page -- Optional parameter |plain is either true for plain search (default) or false for Lua pattern search -- Optional parameter |nomatch is the return value when no match is found; default is nil function str._findpagetext(args) -- process parameters local nomatch = args.nomatch or "" if nomatch == "" then nomatch = nil end -- local text = mw.text.trim(args[1] or args.text or "") if text == "" then return nil end -- local title = args.title or "" local titleobj if title == "" then titleobj = mw.title.getCurrentTitle() else titleobj = mw.title.new(title) end -- local plain = args.plain or "" if plain:sub(1, 1) == "f" then plain = false else plain = true end -- get the page content and look for 'text' - return position or nomatch local content = titleobj and titleobj:getContent() return content and mw.ustring.find(content, text, 1, plain) or nomatch end function str.findpagetext(frame) local args = frame.args local pargs = frame:getParent().args for k, v in pairs(pargs) do args[k] = v end if not (args[1] or args.text) then return nil end -- just the first value return (str._findpagetext(args)) end --[[ Helper function that populates the argument list given that user may need to use a mix of named and unnamed parameters. This is relevant because named parameters are not identical to unnamed parameters due to string trimming, and when dealing with strings we sometimes want to either preserve or remove that whitespace depending on the application. ]] function str._getParameters( frame_args, arg_list ) local new_args = {} local index = 1 local value for _, arg in ipairs( arg_list ) do value = frame_args[arg] if value == nil then value = frame_args[index] index = index + 1 end new_args[arg] = value end return new_args end --[[ Helper function to handle error messages. ]] function str._error( error_str ) local frame = mw.getCurrentFrame() local error_category = frame.args.error_category or 'Errors reported by Module String' local ignore_errors = frame.args.ignore_errors or false local no_category = frame.args.no_category or false if str._getBoolean(ignore_errors) then return '' end local error_str = '<strong class="error">String Module Error: ' .. error_str .. '</strong>' if error_category ~= '' and not str._getBoolean( no_category ) then error_str = '[[Category:' .. error_category .. ']]' .. error_str end return error_str end --[[ Helper Function to interpret boolean strings ]] function str._getBoolean( boolean_str ) local boolean_value if type( boolean_str ) == 'string' then boolean_str = boolean_str:lower() if boolean_str == 'false' or boolean_str == 'no' or boolean_str == '0' or boolean_str == '' then boolean_value = false else boolean_value = true end elseif type( boolean_str ) == 'boolean' then boolean_value = boolean_str else error( 'No boolean value found' ) end return boolean_value end --[[ Helper function that escapes all pattern characters so that they will be treated as plain text. ]] function str._escapePattern( pattern_str ) return ( string.gsub( pattern_str, "[%(%)%.%%%+%-%*%?%[%^%$%]]", "%%%0" ) ) end return str 459b1a3d0c703ac4e7d25c1edbeaad32a165dc7d 10 874 3727 2025-08-13T18:40:43Z Madonuko 140 init with only template data wikitext text/x-wiki <templatedata> { "params": { "1": { "label": "Since", "description": "The date (YYYY-MM-DD) the link was found dead", "example": "2025-08-08", "type": "date", "autovalue": "{{SUBST:CURRENTYEAR}}-{{SUBST:CURRENTMONTH}}-{{SUBST:CURRENTDAY}}", "required": true }, "2": { "label": "Reason", "description": "The status code or the error message when accessing the dead link", "example": "418", "type": "unknown", "required": true } }, "description": "Denote dead links, used by [[User:Hamachitan]].", "format": "inline" } </templatedata> 0b25b616e37c3c83d5260ab4f91fae1bd59ee6d2 10 875 3728 2025-08-13T18:41:08Z Madonuko 140 init wikitext text/x-wiki <includeonly><sup style="color:#fc493b" title="since {{{1}}}{{#ifeq:3|{{#invoke:String|len|{{{2}}}}}||<nowiki/>: {{{2}}}}}">🍣{{#ifeq:3|{{#invoke:String|len|{{{2}}}}}|{{{2}}}|DEAD}}}</includeonly><noinclude>{{/doc}}</noinclude> 4f48ae3b0fa1d8ec24160ed881de5ff4734c9d5f 0 254 3730 3598 2025-08-14T06:44:17Z Hamachitan 222 🍣 Detect and tag dead external links wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/, dwm.suckless.org]{{Dead Link|2025-08-14|404}} }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm. == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == 1bc0300c978ed4ce22fbb877cf8ecfebc9f3aab3 0 736 3731 3603 2025-08-14T06:45:44Z Hamachitan 222 🍣 Detect and tag dead external links wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[category:software]] [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html ed], The IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> ed was part of the original Unix operating system from 1969.<ref>[https://man.cat-v.org/unix-1st/1/ed ed(1)]{{Dead Link|2025-08-14|Cannot connect to host man.cat-v.org:443 ssl:default [None]}}, Unix First Edition Manual Page, 1971-11-03 (Accessed: 2025-08-09)</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>[https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html Shell & Utilities: Detailed Toc], IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s s/regexp/replacement command was inherited from ed.<ref>[https://www.gnu.org/software/ed/manual/ed_manual.html GNU 'ed' Manual], GNU, 1993-08-09 (Accessed: 2025-08-09)</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor vi, whose variants remain some of the most popular TUI text editors.<ref>[https://ex-vi.sourceforge.net/ex.html ex.1], 2005-03-24 (Accessed: 2025-08-09)</ref><ref>[https://ex-vi.sourceforge.net/vi.html vi.1], 2005-03-24 (Accessed: 2025-08-09)</ref> == References == 61fb07af76e0e1625122f79194ac50ab32cfa6ad 0 575 3732 3616 2025-08-14T07:05:31Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository]{{Dead Link|2025-08-14|timeout (8)}}, 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <sup>🍣DEAD?]{{Dead Link|2025-08-14|timeout (8)}}</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys|} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == b3ee259b6a214a0fb5497455fb3f24b295ca174b 0 853 3733 3699 2025-08-14T07:14:16Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{Work_In_Progress}} The '''GNU General Public License''' (short '''GNU GPL''' or '''GPL''') is a collection of copyleft license published by the Free Software Foundation (FSF) and written by Richard Stallman<ref>https://archive.ph/20120907170559/http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html{{Dead Link|2025-08-14|429}}</ref>. This License is also part of the [[GNU]] project === Copyleft === A copyleft license requires that any modifications or extensions to a program licensed under a copyleft license must also be licensed under the same (or a compatible) license. === "or-later" clause === All GNU GPL licenses may contain an optional clause, an “or-later” clause (sometimes referred to as a “lifeboat clause”). This clause allows all later versions to be used. Programs without this clause are referred to as “only.” for example * GNU GPLv2-or-later can also be licensed under GNU GPLv3-or-later without any problem * GNU GPLv2-only can only be licensed under the GNU GPLv2 The same applies to the GNU AGPL and LGPL licenses. The FSF recommends using the “or-later” clause, as it is compatible with future versions of the GNU GPL, since GNU GPLv2 and v3 are not compatible and therefore a program licensed only under GNU GPLv2 cannot be mixed with a GNU GPLv3 program. == Licenses == There are three versions of the GNU GPL, with version 3 being the most recent version for all of them. # GNU General Public License (GPL) – The standard strong copyleft license used for most programs. # GNU Lesser General Public License (LGPL) – A weak copyleft license mainly used for libraries. # GNU Affero General Public License (AGPL) – Similar to the GPL, but also covers use over a network. === GNU General Public License (GPL) === This license is used for regular programs such as the Linux kernel, which uses GNU GPLv2 only. The latest version is the GNU General Public License Version 3 (GNU GPLv3), which was released in June 2007<ref>[https://www.gnu.org/licenses/gpl-3.0.en.html#license-text The GNU General Public License v3.0], Free Software Foundation, 2007-08-14 (Accessed: 2025-08-14)</ref> and can be found [https://www.gnu.org/licenses/gpl-3.0.en.html#license-text here]. If part of a program (e.g., a library) uses this license, the entire program must be licensed under the GNU GPL. If this is not desired, the GNU LGPL or another license should be used. === GNU Lesser General Public License (LGPL) === The GNU LGPL (formerly known as the Library General Public License) was created at the same time as the GNU GPLv2 and was also published in June 2007, but the first version was called GNU LGPLv2 to match the GNU GPLv2. This license was created because the GNU GPL was too restrictive, especially for libraries. If a program uses a library licensed under the GNU LGPL, only the modification of that library must be published. This allows a library to be used in [[Proprietary software]] The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/lgpl-3.0.html here] === GNU Affero General Public License (AGPL) === The GNU AGPL was created to close a loophole when modified software licensed under the GNU GPL was run on a server the source code dont need to be published because of that the AGPL was created to fix this loophole The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/agpl-3.0.html#license-text here] <references /> aa171b7a23f630480836d116cbc315e5873b17e9 0 244 3734 3635 2025-08-14T07:36:43Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]. Installation instructions should be on its own Guides page.}} [[Category:Guides]] [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. '''NOTE:''' After your first Libreboot, you are more than likely able to flash repeatedly afterwards without having to use a Pomona Flash Clip (below). Depending on your device, the flashing experience may and inevitably, at times, '''will''' vary. '''<u>Please check for your BIOS chip device on the Libreboot website.</u>''' === Steps to Install === As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your machine using the Dell OptiPlex as an example. See below for an easier method for that specific device. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. For a Dell OptiPlex 9020, your image '''should be named''' "'''dell9020mt_12mb'''." after compilation. ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository]{{Dead Link|2025-08-14|404}} and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) == References == d256daf4a430438499c4d484f7c870408b68fc2e 0 718 3735 3642 2025-08-14T07:38:37Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[File:Apple-Logo-Transparent.png|thumb|right]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical operating systems developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a UNIX (Darwin/BSD) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> ff17618b5f4df3b7cd9f469601b4d7ae849316e4 0 626 3736 3395 2025-08-14T07:38:57Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>[https://manjaro.org/ Manjaro – The Linux for People and Organizations], Manjaro, 2025-08-09 (Accessed: 2025-08-09)</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">[https://distrowatch.com/table.php?distribution=manjaro DistroWatch.com: Manjaro Linux], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>[https://wiki.manjaro.org/index.php/Pamac Pamac - Manjaro]{{Dead Link|2025-08-14|500}}, Manjaro, 2023-03-09 (Accessed: 2025-08-09)</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>[https://en.wikipedia.org/wiki/Manjaro Manjaro], Wikipedia contributors, 2025-07-01 (Accessed: 2025-08-09)</ref><ref>[https://www.ubuntumint.com/manjaro-linux-history/ The History of Manjaro Linux Distribution], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>[https://www.geeksforgeeks.org/how-to-install-manjaro-linux/ How to Install Manjaro Linux?], GeeksforGeeks, 2023-12-22 (Accessed: 2025-08-09)</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch's base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch's, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>[https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/ How to Enable Arch User Repository (AUR) in Manjaro Linux], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro's custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch's upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>[https://itsfoss.com/manjaro-vs-arch-linux/ Manjaro vs Arch: What's the Difference? Which one to Use?], Dimitrios, Abhishek Prakash, 2023-09-13 (Accessed: 2025-08-09)</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>[https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. == References == 84042d575909457fa1b6b0b51d89ed522fe25612 0 534 3737 3648 2025-08-14T07:39:47Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox | image = [[File:Niri Rice.png|300px|example_niri_rice]] | caption = Example Niri Rice | title = niri | releasestatus = Maintained | firstrelease = v0.1.0-alpha.1 | lastrelease = Version 25.01 | languages = [[Rust]] | developers = Ivan Molodetskikh A.K.A. YaLTeR | website = [https://github.com/YaLTeR/niri Github Repository] }} Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">[https://github.com/YaLTeR/niri/wiki/Important-Software Important Software · YaLTeR/niri Wiki · GitHub], YaLTeR, 2025-08-09 (Accessed: 2025-08-09)</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad]{{Dead Link|2025-08-14|403}} and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse]{{Dead Link|2025-08-14|403}} gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations]{{Dead Link|2025-08-14|403}} * Live-reloading == References == <references /> fcd614e6c6e7818ef069756079115e42db3608bf 0 171 3738 3650 2025-08-14T07:40:04Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such as nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental (But mostly stable and trusted) feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org{{Dead Link|2025-08-14|Cannot connect to host save-nix-together.org:443 ssl:default [Connect call failed ('35.220.189.138', 443)]}} NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> 9a1836401a73240c6d9dddd3e8a741abb4bbe001 0 641 3739 3654 2025-08-14T07:41:03Z Madonuko 140 fix the goddamn link ??? wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Maintenance |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/ openbox.org] }} [[Category:Desktop Environments]] [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable [[X Window Manager|window manager]] for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>[https://openbox.org/ Home - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>[https://openbox.org/obconf ObConf - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> === Usage === While Openbox is perfectly usable on its own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], lxqt, 2025-08-09 (Accessed: 2025-08-09)</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>[https://slitaz.org/en/about/ SliTaz - About the project], SliTaz (Accessed: 2025-08-09)</ref><ref>[https://crunchbang.org/about/ About - CrunchBang], CrunchBang Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> == References == <references /> e11a51b73075843e5337999268c79028b66dde7f 0 176 3740 3659 2025-08-14T07:42:16Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop]{{Dead Link|2025-08-14|404}} }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2025-08-14|503}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2025-08-14|503}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> 18c02c81e9112c946b0806c7ef738ff13de1a941 0 767 3741 3118 2025-08-14T07:43:15Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki RTFM is an acronym of "Read The Fucking Manual"<ref>{{Cite|url=http://www.catb.org/~esr/faqs/smart-questions.html#rtfm{{Dead Link|2025-08-14|timeout (10)}}|title=How To Ask Questions The Smart Way|author=Eric Steven Raymond|year=21 May 2014|accessdate=2 August 2025}}</ref> or "Read The Friendly Manual". It's usually used when a user asks a question that could be easily answered by reading the manual d6d8bbe35f8ab3a1a7463b218e06f15a7fcd941c 0 558 3742 3673 2025-08-14T07:44:25Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[C]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called “garbage collecting,” where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[#Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" lines> struct MyStruct { field1: bool, field2: i32, field3: String, } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: MyStruct = MyStruct { field1: true, field2: 64, field3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height // This returns the Cube's Volume } } fn main() { let rubiks_cube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's volume: {}", rubiks_cube.volume()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an area finder function within the <code>impl Cube</code> scope. We are able to use the <code>volume()</code> method on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == 9ba020ce79f9a29839f4245cea2ce33a8fd8f2f3 0 663 3743 3681 2025-08-14T07:52:14Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terra.fyralabs.com terra.fyralabs.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora]] Linux and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terra.fyralabs.com/ Terra], Terra, 2024 (Accessed: 2025-06-19)</ref> Developed by Fyra Labs, it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://developer.fyralabs.com/terra/infrastructure How Terra Works], Fyra Labs, 2025 (Accessed: 2025-06-19)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://developer.fyralabs.com/terra/installing. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji]{{Dead Link|2025-08-14|401}}, RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://developer.fyralabs.com/terra/autoupdate Automatic Updates - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases :: Fedora Docs], Fedora, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably Rust, Go, [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://developer.fyralabs.com/terra/policy Policy – Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> == See Also == * [https://terra.fyralabs.com Main Website] * [https://developer.fyralabs.com/terra Fyra Developer Documentations for Terra] * [https://github.com/terrapkg/packages Terra Sources] == References == b35f29eaa4675a32038b22afb2bd80452a57591e 0 841 3744 3498 2025-08-14T07:53:30Z Madonuko 140 fix link wikitext text/x-wiki [[category:Linux Distributions]] {{DistributionInfobox | title = Ultramarine Linux | image = [[File:Ultramarine_Logo_Icon.svg|Ultramarine Logo|frameless]] | caption = Ultramarine Linux Logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[dnf|dnf5]], [[rpm]], [[flatpak]] | defaultdesktops = [[Budgie]], [[GNOME]], [[Plasma]], [[XFCE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = https://ultramarine-linux.org | Current version = um42 }} '''Ultramarine Linux''' is a [[Fedora]]-based Linux distribution for people with varying technical backgrounds by providing sane defaults and tweaks out of the box.<ref>[https://ultramarine-linux.org Ultramarine Linux], Ultramarine Project, 2025 (Accessed: 2025-08-10)</ref> Started by Cappy Ishihara in 2021, the team ''Ultramarine Project'' later had a merger, and the [[distro]] is now a major successful product by [[Fyra Labs]].<ref>[https://wiki.fyralabs.com/Ultramarine_Linux Ultramarine Linux], Fyra Labs Wiki, 2023-10-01 (Accessed: 2025-08-10)</ref> Unlike Fedora, the Ultramarine team prioritises on being more ''pragmatical'' over being more ideological<ref name=":0">[https://wiki.ultramarine-linux.org/en/welcome/ Welcome], Ultramarine Wiki, 2025 (Accessed: 2025-08-10)</ref>, by for example installing non-free drivers and codecs automatically<ref>[https://www.zdnet.com/article/ultramarine-linux-40-continues-to-be-one-fine-unofficial-fedora-spin/ Ultramarine Linux 40 continues to be one fine unofficial Fedora Spin], Jack Wallen, 2024-12-23 (Accessed: 2025-08-10)</ref>, improving overall user experience. == History == Created in 2021, Ultramarine Linux was the spiritual successor to [[Korora Linux]], following the goal of creating a system that “just works”. It was created due to “frustration with the legal limits of Fedora”<ref>[https://github.com/Ultramarine-Linux/wiki/blob/ba740779d7fe037429c88adbe238039ea3c69991/src/content/docs/en/welcome.md wiki/src/content/docs/en/welcome.md at ba740779d7fe037429c88adbe238039ea3c69991 · Ultramarine-Linux/wiki], Ultramarine Linux, 2023 (Accessed: 2025-08-10)</ref>, and was shipped as a base-Fedora image with tweaks, codecs and drivers on top. The first release Ultramarine 35 (UM35) came with 4 editions: Budgie, [[Cutefish]], [[Pantheon]] and [[GNOME]]. Budgie was made as the ''flagship'' edition, because it was a rather popular [[DE]] that was not yet available on Fedora 35.<ref>[https://news.itsfoss.com/fedora-budgie-sway-official/ Official Fedora Budgie & Sway Spins to Arrive With Fedora 38 Release], Sourav Rudra, 2023-01-04 (Accessed: 2025-08-10)</ref> The merger with Fyra Labs later brought packaging toolchains like Andaman and Subatomic to life, which replaced Ultramarine's own packaging tool [http://github.com/Ultramarine-Linux/umpkg umpkg], and was followed by the creation of [[Terra]], which was intended to be a common software [[repository]] shared between Ultramarine and its sister project [[tauOS]]. Cutefish and Pantheon editions were removed in later editions due to lack of upstream maintenance, and were replaced by KDE Plasma and XFCE respectively.<ref name=":0"/> == Installation == There are 3 main supported ways to install Ultramarine Linux: # Migration from Fedora ([https://ultramarine-linux.org/migrate.sh migrate.sh]) or [[risiOS]] ([https://ultramarine-linux.org/migrate-risi.sh migrate-risi.sh]) is supported. # ISO and raw images are provided for different corresponding platforms on the [https://ultramarine-linux.org/download/ download page]. # Ultramarine WSL is also available on the [https://apps.microsoft.com/detail/9pbpg2rdmzb9 Microsoft Store]. == Repositories == Apart from the Fedora stable and update repositories, Ultramarine also comes with all free and non-free [[RPM Fusion]] repositories, and Terra with extra streams enabled. Ultramarine Linux also comes with [[Flathub]] instead of [[Fedora Flatpaks]], making the experience free of hassles.<ref name=":0"/> == Ultramarine Anywhere == Originally named as ''Ultramarine Everywhere'', ''Ultramarine Anywhere'' is an initiative started from Ultramarine 38 that provides better hardware support for other platforms.<ref>[https://wiki.ultramarine-linux.org/en/anywhere/anywhere/ Ultramarine Anywhere], Ultramarine Wiki, 2025 (Accessed: 2025-08-10)</ref> Currently Ultramarine Linux has first-class support for various different kinds of [[Chromebook]], [[Raspberry Pi]], and [[Microsoft Surface]] models. Ultramarine also initiated earlier [[WSL]] support than Fedora and its derivatives. == References == 02a705f150bad1a9d882375c5cc795150f2af1cd 4 876 3745 2025-08-14T10:26:02Z Atmois 13 Create blank page to be filled out wikitext text/x-wiki . 3a52ce780950d4d969792a2559cd519d7ee8c727 0 218 3746 3640 2025-08-14T19:17:45Z Satnus 215 Fixed a messed up table & removed the "Citations Needed" template. wikitext text/x-wiki [[Category:Guides]] [[Linux]] due to its generally lower system requirements than [[Windows]]<ref>[https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3 Revive Old Hardware with Linux], Aidan Palmer, 2023-03-05 (Accessed: 2025-08-09)</ref> or [[macOS]] and a general absence of vendor-imposed hardware restrictions is frequently chosen for reviving and reusing older devices. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (i.e. keyrings, polkit, GTK, QT, etc.) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>[https://www.linuxmint.com/faq.php Frequently Asked Questions - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>[https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <span style="color:#fc493b">https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <sup>🍣404]</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Frequently_asked_questions Frequently asked questions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://wiki.archlinux.org/title/Arch_compared_to_other_distributions Arch compared to other distributions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time-consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>[https://fedoraproject.org/wiki/FAQ FAQ], Fedora Project Wiki, 2025-07-24 (Accessed: 2025-08-09)</ref><ref>[https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs Hardware Overview], Fedora Docs, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">[https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html System requirements for Puppy Linux], THE.Hosting, 2023-04-23 (Accessed: 2025-08-09)</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' == References == <references /> 2977376d1937d832f358b868d7a60f981551dfc7 3001 877 3747 2025-08-14T20:59:49Z Satnus 215 /* Revamping the page */ new section wikitext text/x-wiki == Revamping the page == This page should be changed to only show installing i3 & i3-wm with a placeholder package manager, a repology embed (though I'm not sure if those are possible, if not we'll just list the repos with i3) and maybe guides to build and/or install it manually when repos dont have it? I think listing every installation command for i3 when most are virtually identical is a bit unnecessary. [[User:Satnus|Satnus]] ([[User talk:Satnus|talk]]) 20:59, 14 August 2025 (UTC) 8749865aa6f385e7f547e9466a56497f2fd13f30 3000 878 3748 2025-08-15T15:47:01Z Ilija.culap 258 Created page with "{{Guide_Warning}} In this guide you will learn how to install PiHole on your openSUSE MicroOS. MicroOS is very lightweight operating system designed for containerized and virtualized workloads. It also supports automatic updates and self-maintenance. There is also a SELinux (Security Extension) enabled and configured by default. Our container is going to run as root user (rootfull). For deployment we are going to to use quadlet files. Those are special files that are go..." wikitext text/x-wiki {{Guide_Warning}} In this guide you will learn how to install PiHole on your openSUSE MicroOS. MicroOS is very lightweight operating system designed for containerized and virtualized workloads. It also supports automatic updates and self-maintenance. There is also a SELinux (Security Extension) enabled and configured by default. Our container is going to run as root user (rootfull). For deployment we are going to to use quadlet files. Those are special files that are going to be handled by systemd, so we can then use systemd commands to start, stop and restart our PiHole service. '''Requirements and prerequisites:''' * Installed openSUSE MicroOS with container support * Basic command-line knowledge Start with creating a folder to hold all your PiHole configuration and 2 subfolders as shown below. MicroOS is immutable and you can’t put files wherever you want. You should use /var or /root folders on your filesystem. I’m going to use /var directory. mkdir /var/pihole mkdir /var/pihole/etc-pihole mkdir /var/pihole/etc-dnsmasq.d Next step is to create .container file in /etc/containers/systemd/ (You can actually skip this step, because your text editor is going to create this file for you in the next step). touch /etc/containers/systemd/pihole.container and then edit it: vim /etc/containers/systemd/pihole.container I’m using vim text editor, but feel free to use whatever editor you like (for example nano). In this file put following content and change your time zone and password: [Unit] Description=PiHole Container StartLimitIntervalSec=0 [Container] Image=docker.io/pihole/pihole:latest Volume=/var/pihole/etc-pihole:/etc/pihole:Z Volume=/var/pihole/etc-dnsmasq.d:/etc/dnsmasq.d:Z AutoUpdate=registry Environment="TZ=Europe/Berlin" Environment="FTLCONF_webserver_api_password=changeme" PublishPort=53:53/tcp PublishPort=53:53/udp PublishPort=5555:80/tcp [Service] Restart=always RestartSec=1m [Install] WantedBy=default.target Next step is to reload systemd so it can load all new and changed files (your .container file): systemctl daemon-reload and start your pihole service (in this command pihole is the name of .container file. Adjust your command accordingly!): systemctl start pihole And that’s it. Your PiHole service is now running. You can check if everything is okay with: podman stats To exit press CTRL + C. To access your WEB Interface go to: http://<Server-IP>:5555/admin/ 5df05f2f1f064aa60283e33914da9012c5aadf89 0 622 3749 3600 2025-08-16T08:53:20Z OgloTheNerd 248 Improved table. wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:GNOME 43.png|GNOME File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from Razor-qt and LXDE components which were ported to [[Qt]]. |} d3b1c7f7094a0a3ce342d1263e86bf361d67e574 4 595 3750 2119 2025-08-16T10:16:57Z Atmois 13 Update security policy and add new team member wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.gg/linux Discord Server] and asking for help in the <code>#atl-wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for a Wiki Administrator. You may also direct message <code>@atmois</code> (Head of Wiki Operations) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''wiki(at)allthingslinux.org.'' To report security vulnerabilities please see our [https://allthingslinux.org/security ATL Security Policy]. * [[User:Atmois|Atmois]] - Head of Wiki Operations ** ''atmois(at)allthingslinux.org'' * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner ** ''kaizen(at)allthingslinux.org'' * [[User:Scottc96|Scott96]] - Sysadmin ** ''scott(at)allthingslinux.org'' *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''owuh(at)allthingslinux.org'' de04502b6d7cda60e06f5d33d5f275eba1b7eb1d 0 625 3751 3381 2025-08-16T14:47:07Z Satnus 215 Added an infobox and maybe too many default desktops? wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[i3]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[qtile]], [[sway]], [[ukui]], [[wayfire]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was developed by a team led by Peter "ptr1337" Jung to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2023. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Default browser: Cachy Browser (hardened Firefox fork). * Support for Btrfs snapshots with Limine bootloader. * Optional Firejail, DNSCrypt, AppArmor hardening. == Desktop Environments == CachyOS provides several preconfigured desktop environments: * [[Plasma|KDE Plasma]] (default) * [[GNOME]] * [[XFCE|Xfce]] * [[LXQt]] * [[Cutefish]] * [[Wayfire]] * [[i3]], [[bspwm]], [[Openbox]] Users can select their preferred environment during installation. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * [[Btrfs]] with snapshot support is the default filesystem. * Full UEFI, ZFS, and Secure Boot support. * Smooth installation experience designed for newcomers to Arch. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. * Limine bootloader for rollback support via Btrfs. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> d6aba6b71afa201ecf78fa79450b482b7d348a53 0 198 3752 3637 2025-08-16T15:27:07Z Ow0cast 249 cleanup | spaces around refs wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == 1bbff1f31e0a3d051d537b6cb75c0ae9c7727970 0 763 3753 3506 2025-08-16T15:41:39Z 0Stormy 158 Update X Window Manager gallery wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Screenshot of awesomewm4.png|link=awesomewm|awesome File:Compiz Shift Switcher.png|link=Compiz|Compiz File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:Twm.png|link=twm|twm File:Icewm-default.jpg|link=IceWM|IceWM File:I3-wm.png|link=i3|i3 File:Wmaker-0.80.2.png|link=Window_Maker|Window Maker File:Xmonad screenshot.png|link=Xmonad|XMonad </gallery> {| class="wikitable" |+ !Window Manager !Description |- |[[awesome]]<ref>[https://github.com/awesomeWM/awesome GitHub - awesomeWM/awesome: awesome window manager], awesomeWM, 2025-08-09 (Accessed: 2025-08-09)</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |[[Compiz]] |Compiz is a compositing window manager for the X Window System. |- |[[Openbox]] |A minimal and highly configurable stacking window manager written in C. |- |[[twm]]<ref>[https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml TWM], 2010-11-13 (Accessed: 2025-08-09)</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |[[IceWM]]<ref>[https://github.com/bbidulock/icewm GitHub - bbidulock/icewm: A window manager designed for speed, usability, and consistency], bbidulock, 2025-08-09 (Accessed: 2025-08-09)</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |[[i3]]<ref>[https://i3wm.org i3: improved tiling X11 window manager], Michael Stapelberg, 2025-06-12 (Accessed: 2025-08-09)</ref> |A tiling window manager for advanced users and developers. |- |[[Window Maker]]<ref>[https://github.com/window-maker/wmaker GitHub - window-maker/wmaker: Mirror of the official repository repo.or.cz/wmaker-crm.git. Do not send pull requests here, send your patches to wmaker-dev@googlegroups.com instead], window-maker, 2020-08-09 (Accessed: 2025-08-09)</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |[[XMonad]]<ref>[https://xmonad.org/ home | xmonad - the tiling window manager that rocks], xmonad, 2025-06-15 (Accessed: 2025-08-09)</ref> |Window Manager configurable via the Haskell functional programming language. |} ==References== <references /> ec8bc089f4d07178652bf4a58a3bf8668af2a04c 3000 824 3754 3447 2025-08-16T15:52:11Z 0Stormy 158 Update FL Studio guide to be more version independent wikitext text/x-wiki {{Guide_Warning}} [[FL Studio]] 24 has been tested to work very well under [[Wine|WINE]]. The recommended version to use is 12.5.1 or newer, as older versions have issues with loading WAV and Vorbis files. == Prerequisites == [[File:Bottles Runners screen.png|thumb|The runners page in Bottles, showing caffe-9.7 already installed]] FL Studio is paid software. You will need to download your registry key file before starting this guide. You can still use the software in demo mode if you do not have a key. This guide requires [[Bottles]] to be installed. The recommended way of installing Bottles is via [[Flatpak]]. Using the caffe-9.7 runner is recommended as it fixes minor issues with cursor icons and windowing. Make sure it is installed by opening Bottles preferences via {{keypress|Ctrl|,}}. Then, select the "Runners" tab at the top, and expand the "Caffe" section. Find caffe-9.7 and click the download button next to it, if it is present. If you see a folder icon, then it is already installed. == Installation == === Preparing the bottle === [[File:Bottles details screen (highlighted).png|thumb|The Bottles details screen with relevant menu options highlighted]] Start by creating the bottle by clicking the "+" button in the top-left corner of the application Give the bottle a name, such as "FL Studio 24" (The name is not significant, this is only an example). Make sure "Application" is selected, then click "Runner" and choose "caffe-9.7". Finish by clicking create. Wait for the bottle to finish configuration, this may take up to 10 seconds. Once the bottle has been created, within its details menu, under the "Options" section, click the "Dependencies" button. Using the search button in the top-right corner, search for "allfonts" and then click the download button next to its result. Installation may take a while, so please be patient while it installs. Then, go back to the details page.<ref name=":0">{{Cite|url=https://github.com/Torbuntu/fl-studio-linux-setup|title=FL Studio Linux Setup|author=Torbuntu|year=2025|accessdate=2025-08-09}}</ref> In order for musical notation to be displayed correctly, the msgothic font must be installed manually. Download the file from https://github.com/FSKiller/Microsoft-Fonts/blob/main/msgothic.ttc, and save it to your downloads folder. Next, click the ellipses (three dots) on the top-right corner and select "Browse files...". This will open the bottle's C drive directory in your default file explorer. Navigate to "windows" then "Fonts" and copy the downloaded font file into this directory from your downloads.<ref name=":0" /> Back in the details page of the bottle, under the "Options" section, click the "Settings" button. Scroll down to the "Compatibility" section and change the Windows version to Windows 11.<ref name=":0" /> Finally, return back to the details page to prepare for installation. === Registering the software === Prior to installation, you must register the software (unless you intend to use it in demo mode). To do this, download your registry key from Image-Line's website and save it to your downloads. Copy it into your bottle by clicking the three dots on the top-right corner and selecting "Browse files...". Navigate to "users > steamuser > Documents", and copy your registry file into there. Now, back in Bottles, scroll down to the "Tools" section. From here, open the Registry editor. In the menu bar of the registry editor, click File > Import registry file... Within the browser, open "Documents" and then double click the registry file you copied into your bottle earlier. The registry editor will ask you to confirm, click yes, then once done, exit the registry editor. The software should now be registered === Installing FL Studio === [[File:FL Studio installer (highlighted).png|thumb|FL Studio 12 installer with relevant options highlighted]] Scroll up in the details page, and click the "Run Executable..." button. Select the FL Studio installer and click open. Proceed with setup as usual, select "All users" when prompted. De-select "ASIO4ALL" as it is known not to work very well under WINE. (Note, if you are '''not''' creating a new bottle and are upgrading an existing one, de-select "Clear" under the settings option, and select "Migrate previous version". If you '''are''' creating a new bottle, do '''not''' do this, or the installation will fail.). You can now launch the program from Bottles by clicking the run button next to "FL" (for the 32-bit version), and "FL 64" (for the 64-bit version). I recommend clicking the three dots next to each option, and selecting "Add desktop entry". This will add shortcuts to FL Studio within your desktop environment, so you can access it from your app launcher without needing to open Bottles every time. I also recommend you edit the desktop entry files using a tool such as [[KDE Menu Editor]] to give them more reasonable names. == Tweaks == === Documents folder pass-through === [[File:Flatseal options for Bottles (highlighted).png|thumb|Flatseal with relevant options highlighted]] It is likely that you'll need to share files between FL Studio and your main system (Project files, samples, etc.). The simplest way to do this is by creating a dedicated folder in your Documents directory, and linking it somewhere within your bottle's C drive. You may also pass through your entire home directory or documents directory, however this is not typically recommended for security purposes, as it requires allowing all other bottles access too. First create the desired directory in your file explorer, and then create a symbolic link ('''NOT''' a shortcut). This can be done in [[Dolphin]] by dragging and dropping a directory, then selecting "Link Here". To open your bottle's documents folder, go to bottles, click on your bottle, click the three dots on the top-right, and select "Browse files..." Now navigate to "users > steamuser > Documents". Drag and drop your folder here, and select "Link Here". Now, we must authorize Bottles to access this directory. The easiest way to do this is via [[Flatseal]]. Within the application, in the list on the left hand side, search for "Bottles". Once selected, in the page on the right, scroll down to the "Filesystem" section. If you wish to expose your entire home directory (Not recommended), enable the "All user files" toggle. Otherwise, click the add button next to "Other files", add an entry, such as "~/Documents/<your folder here>". (~) replaces your own home directory, so change this as needed. If you want to use an absolute path instead; "/home/<username>/Documents/<your folder here>". Now, you should be able to access this directory within FL Studio == References == 16b4eb23f43d5c6813027c643797e0568bebb70d 3756 3754 2025-08-17T23:24:04Z Maelstrom071 235 Undo revision [[Special:Diff/3754|3754]] by [[Special:Contributions/0Stormy|0Stormy]] ([[User talk:0Stormy|talk]]) wikitext text/x-wiki {{Guide_Warning}} [[FL Studio]] 12 has been tested to work very well under [[Wine|WINE]]. The recommended version to use is 12.5.1, as older versions have issues with loading WAV Vorbis files. Newer versions have not yet been tested. == Prerequisites == [[File:Bottles Runners screen.png|thumb|The runners page in Bottles, showing caffe-9.7 already installed]] FL Studio is paid software. You will need to download your registry key file before starting this guide. You can still use the software in demo mode if you do not have a key. This guide requires [[Bottles]] to be installed. The recommended way of installing Bottles is via [[Flatpak]]. Using the caffe-9.7 runner is recommended as it fixes minor issues with cursor icons and windowing. Make sure it is installed by opening Bottles preferences via {{keypress|Ctrl|,}}. Then, select the "Runners" tab at the top, and expand the "Caffe" section. Find caffe-9.7 and click the download button next to it, if it is present. If you see a folder icon, then it is already installed. == Installation == === Preparing the bottle === [[File:Bottles details screen (highlighted).png|thumb|The Bottles details screen with relevant menu options highlighted]] Start by creating the bottle by clicking the "+" button in the top-left corner of the application Give the bottle a name, such as "FL Studio 12" (The name is not significant, this is only an example). Make sure "Application" is selected, then click "Runner" and choose "caffe-9.7". Finish by clicking create. Wait for the bottle to finish configuration, this may take up to 10 seconds. Once the bottle has been created, within its details menu, under the "Options" section, click the "Dependencies" button. Using the search button in the top-right corner, search for "allfonts" and then click the download button next to its result. Installation may take a while, so please be patient while it installs. Then, go back to the details page.<ref name=":0">{{Cite|url=https://github.com/Torbuntu/fl-studio-linux-setup|title=FL Studio Linux Setup|author=Torbuntu|year=2025|accessdate=2025-08-09}}</ref> In order for musical notation to be displayed correctly, the msgothic font must be installed manually. Download the file from https://github.com/FSKiller/Microsoft-Fonts/blob/main/msgothic.ttc, and save it to your downloads folder. Next, click the ellipses (three dots) on the top-right corner and select "Browse files...". This will open the bottle's C drive directory in your default file explorer. Navigate to "windows" then "Fonts" and copy the downloaded font file into this directory from your downloads.<ref name=":0" /> Back in the details page of the bottle, under the "Options" section, click the "Settings" button. Scroll down to the "Compatibility" section and change the Windows version to Windows 11.<ref name=":0" /> Finally, return back to the details page to prepare for installation. === Registering the software === Prior to installation, you must register the software (unless you intend to use it in demo mode). To do this, download your registry key from Image-Line's website and save it to your downloads. Copy it into your bottle by clicking the three dots on the top-right corner and selecting "Browse files...". Navigate to "users > steamuser > Documents", and copy your registry file into there. Now, back in Bottles, scroll down to the "Tools" section. From here, open the Registry editor. In the menu bar of the registry editor, click File > Import registry file... Within the browser, open "Documents" and then double click the registry file you copied into your bottle earlier. The registry editor will ask you to confirm, click yes, then once done, exit the registry editor. The software should now be registered === Installing FL Studio 12 === [[File:FL Studio installer (highlighted).png|thumb|FL Studio 12 installer with relevant options highlighted]] Scroll up in the details page, and click the "Run Executable..." button. Select the FL Studio 12.5.1 installer and click open. Proceed with setup as usual, select "All users" when prompted. De-select "ASIO4ALL" as it is known not to work very well under WINE. (Note, if you are '''not''' creating a new bottle and are upgrading an existing one, de-select "Clear" under the settings option, and select "Migrate previous version". If you '''are''' creating a new bottle, do '''not''' do this, or the installation will fail.). You can now launch the program from Bottles by clicking the run button next to "FL" (for the 32-bit version), and "FL 64" (for the 64-bit version). I recommend clicking the three dots next to each option, and selecting "Add desktop entry". This will add shortcuts to FL Studio within your desktop environment, so you can access it from your app launcher without needing to open Bottles every time. I also recommend you edit the desktop entry files using a tool such as [[KDE Menu Editor]] to give them more reasonable names. == Tweaks == === Documents folder pass-through === [[File:Flatseal options for Bottles (highlighted).png|thumb|Flatseal with relevant options highlighted]] It is likely that you'll need to share files between FL Studio and your main system (Project files, samples, etc.). The simplest way to do this is by creating a dedicated folder in your Documents directory, and linking it somewhere within your bottle's C drive. You may also pass through your entire home directory or documents directory, however this is not typically recommended for security purposes, as it requires allowing all other bottles access too. First create the desired directory in your file explorer, and then create a symbolic link ('''NOT''' a shortcut). This can be done in [[Dolphin]] by dragging and dropping a directory, then selecting "Link Here". To open your bottle's documents folder, go to bottles, click on your bottle, click the three dots on the top-right, and select "Browse files..." Now navigate to "users > steamuser > Documents". Drag and drop your folder here, and select "Link Here". Now, we must authorize Bottles to access this directory. The easiest way to do this is via [[Flatseal]]. Within the application, in the list on the left hand side, search for "Bottles". Once selected, in the page on the right, scroll down to the "Filesystem" section. If you wish to expose your entire home directory (Not recommended), enable the "All user files" toggle. Otherwise, click the add button next to "Other files", add an entry, such as "~/Documents/<your folder here>". (~) replaces your own home directory, so change this as needed. If you want to use an absolute path instead; "/home/<username>/Documents/<your folder here>". Now, you should be able to access this directory within FL Studio == References == 2ef778c662c9b70ff7741918aaa8bb1bbd30462d 4 327 3755 2919 2025-08-16T18:18:52Z Atmois 13 hi wikitext text/x-wiki linux is cool.<ref>{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributiors|year=2025}}</ref> why? because i said so. hi =References= <references /> 714b55c250750330737e5c3b0fc321a5b3296968 3000 824 3757 3756 2025-08-17T23:24:47Z Maelstrom071 235 Undo revision [[Special:Diff/3756|3756]] by [[Special:Contributions/Maelstrom071|Maelstrom071]] ([[User talk:Maelstrom071|talk]]) wikitext text/x-wiki {{Guide_Warning}} [[FL Studio]] 24 has been tested to work very well under [[Wine|WINE]]. The recommended version to use is 12.5.1 or newer, as older versions have issues with loading WAV and Vorbis files. == Prerequisites == [[File:Bottles Runners screen.png|thumb|The runners page in Bottles, showing caffe-9.7 already installed]] FL Studio is paid software. You will need to download your registry key file before starting this guide. You can still use the software in demo mode if you do not have a key. This guide requires [[Bottles]] to be installed. The recommended way of installing Bottles is via [[Flatpak]]. Using the caffe-9.7 runner is recommended as it fixes minor issues with cursor icons and windowing. Make sure it is installed by opening Bottles preferences via {{keypress|Ctrl|,}}. Then, select the "Runners" tab at the top, and expand the "Caffe" section. Find caffe-9.7 and click the download button next to it, if it is present. If you see a folder icon, then it is already installed. == Installation == === Preparing the bottle === [[File:Bottles details screen (highlighted).png|thumb|The Bottles details screen with relevant menu options highlighted]] Start by creating the bottle by clicking the "+" button in the top-left corner of the application Give the bottle a name, such as "FL Studio 24" (The name is not significant, this is only an example). Make sure "Application" is selected, then click "Runner" and choose "caffe-9.7". Finish by clicking create. Wait for the bottle to finish configuration, this may take up to 10 seconds. Once the bottle has been created, within its details menu, under the "Options" section, click the "Dependencies" button. Using the search button in the top-right corner, search for "allfonts" and then click the download button next to its result. Installation may take a while, so please be patient while it installs. Then, go back to the details page.<ref name=":0">{{Cite|url=https://github.com/Torbuntu/fl-studio-linux-setup|title=FL Studio Linux Setup|author=Torbuntu|year=2025|accessdate=2025-08-09}}</ref> In order for musical notation to be displayed correctly, the msgothic font must be installed manually. Download the file from https://github.com/FSKiller/Microsoft-Fonts/blob/main/msgothic.ttc, and save it to your downloads folder. Next, click the ellipses (three dots) on the top-right corner and select "Browse files...". This will open the bottle's C drive directory in your default file explorer. Navigate to "windows" then "Fonts" and copy the downloaded font file into this directory from your downloads.<ref name=":0" /> Back in the details page of the bottle, under the "Options" section, click the "Settings" button. Scroll down to the "Compatibility" section and change the Windows version to Windows 11.<ref name=":0" /> Finally, return back to the details page to prepare for installation. === Registering the software === Prior to installation, you must register the software (unless you intend to use it in demo mode). To do this, download your registry key from Image-Line's website and save it to your downloads. Copy it into your bottle by clicking the three dots on the top-right corner and selecting "Browse files...". Navigate to "users > steamuser > Documents", and copy your registry file into there. Now, back in Bottles, scroll down to the "Tools" section. From here, open the Registry editor. In the menu bar of the registry editor, click File > Import registry file... Within the browser, open "Documents" and then double click the registry file you copied into your bottle earlier. The registry editor will ask you to confirm, click yes, then once done, exit the registry editor. The software should now be registered === Installing FL Studio === [[File:FL Studio installer (highlighted).png|thumb|FL Studio 12 installer with relevant options highlighted]] Scroll up in the details page, and click the "Run Executable..." button. Select the FL Studio installer and click open. Proceed with setup as usual, select "All users" when prompted. De-select "ASIO4ALL" as it is known not to work very well under WINE. (Note, if you are '''not''' creating a new bottle and are upgrading an existing one, de-select "Clear" under the settings option, and select "Migrate previous version". If you '''are''' creating a new bottle, do '''not''' do this, or the installation will fail.). You can now launch the program from Bottles by clicking the run button next to "FL" (for the 32-bit version), and "FL 64" (for the 64-bit version). I recommend clicking the three dots next to each option, and selecting "Add desktop entry". This will add shortcuts to FL Studio within your desktop environment, so you can access it from your app launcher without needing to open Bottles every time. I also recommend you edit the desktop entry files using a tool such as [[KDE Menu Editor]] to give them more reasonable names. == Tweaks == === Documents folder pass-through === [[File:Flatseal options for Bottles (highlighted).png|thumb|Flatseal with relevant options highlighted]] It is likely that you'll need to share files between FL Studio and your main system (Project files, samples, etc.). The simplest way to do this is by creating a dedicated folder in your Documents directory, and linking it somewhere within your bottle's C drive. You may also pass through your entire home directory or documents directory, however this is not typically recommended for security purposes, as it requires allowing all other bottles access too. First create the desired directory in your file explorer, and then create a symbolic link ('''NOT''' a shortcut). This can be done in [[Dolphin]] by dragging and dropping a directory, then selecting "Link Here". To open your bottle's documents folder, go to bottles, click on your bottle, click the three dots on the top-right, and select "Browse files..." Now navigate to "users > steamuser > Documents". Drag and drop your folder here, and select "Link Here". Now, we must authorize Bottles to access this directory. The easiest way to do this is via [[Flatseal]]. Within the application, in the list on the left hand side, search for "Bottles". Once selected, in the page on the right, scroll down to the "Filesystem" section. If you wish to expose your entire home directory (Not recommended), enable the "All user files" toggle. Otherwise, click the add button next to "Other files", add an entry, such as "~/Documents/<your folder here>". (~) replaces your own home directory, so change this as needed. If you want to use an absolute path instead; "/home/<username>/Documents/<your folder here>". Now, you should be able to access this directory within FL Studio == References == 16b4eb23f43d5c6813027c643797e0568bebb70d 3758 3757 2025-08-18T00:32:02Z Maelstrom071 235 clarification on wav-vorbis wikitext text/x-wiki {{Guide_Warning}} [[FL Studio]] 24 has been tested to work very well under [[Wine|WINE]]. The recommended version to use is 12.5.1 or newer, as older versions have issues with loading Vorbis-encoded WAV files. == Prerequisites == [[File:Bottles Runners screen.png|thumb|The runners page in Bottles, showing caffe-9.7 already installed]] FL Studio is paid software. You will need to download your registry key file before starting this guide. You can still use the software in demo mode if you do not have a key. This guide requires [[Bottles]] to be installed. The recommended way of installing Bottles is via [[Flatpak]]. Using the caffe-9.7 runner is recommended as it fixes minor issues with cursor icons and windowing. Make sure it is installed by opening Bottles preferences via {{keypress|Ctrl|,}}. Then, select the "Runners" tab at the top, and expand the "Caffe" section. Find caffe-9.7 and click the download button next to it, if it is present. If you see a folder icon, then it is already installed. == Installation == === Preparing the bottle === [[File:Bottles details screen (highlighted).png|thumb|The Bottles details screen with relevant menu options highlighted]] Start by creating the bottle by clicking the "+" button in the top-left corner of the application Give the bottle a name, such as "FL Studio 24" (The name is not significant, this is only an example). Make sure "Application" is selected, then click "Runner" and choose "caffe-9.7". Finish by clicking create. Wait for the bottle to finish configuration, this may take up to 10 seconds. Once the bottle has been created, within its details menu, under the "Options" section, click the "Dependencies" button. Using the search button in the top-right corner, search for "allfonts" and then click the download button next to its result. Installation may take a while, so please be patient while it installs. Then, go back to the details page.<ref name=":0">{{Cite|url=https://github.com/Torbuntu/fl-studio-linux-setup|title=FL Studio Linux Setup|author=Torbuntu|year=2025|accessdate=2025-08-09}}</ref> In order for musical notation to be displayed correctly, the msgothic font must be installed manually. Download the file from https://github.com/FSKiller/Microsoft-Fonts/blob/main/msgothic.ttc, and save it to your downloads folder. Next, click the ellipses (three dots) on the top-right corner and select "Browse files...". This will open the bottle's C drive directory in your default file explorer. Navigate to "windows" then "Fonts" and copy the downloaded font file into this directory from your downloads.<ref name=":0" /> Back in the details page of the bottle, under the "Options" section, click the "Settings" button. Scroll down to the "Compatibility" section and change the Windows version to Windows 11.<ref name=":0" /> Finally, return back to the details page to prepare for installation. === Registering the software === Prior to installation, you must register the software (unless you intend to use it in demo mode). To do this, download your registry key from Image-Line's website and save it to your downloads. Copy it into your bottle by clicking the three dots on the top-right corner and selecting "Browse files...". Navigate to "users > steamuser > Documents", and copy your registry file into there. Now, back in Bottles, scroll down to the "Tools" section. From here, open the Registry editor. In the menu bar of the registry editor, click File > Import registry file... Within the browser, open "Documents" and then double click the registry file you copied into your bottle earlier. The registry editor will ask you to confirm, click yes, then once done, exit the registry editor. The software should now be registered === Installing FL Studio === [[File:FL Studio installer (highlighted).png|thumb|FL Studio 12 installer with relevant options highlighted]] Scroll up in the details page, and click the "Run Executable..." button. Select the FL Studio installer and click open. Proceed with setup as usual, select "All users" when prompted. De-select "ASIO4ALL" as it is known not to work very well under WINE. (Note, if you are '''not''' creating a new bottle and are upgrading an existing one, de-select "Clear" under the settings option, and select "Migrate previous version". If you '''are''' creating a new bottle, do '''not''' do this, or the installation will fail.). You can now launch the program from Bottles by clicking the run button next to "FL" (for the 32-bit version), and "FL 64" (for the 64-bit version). I recommend clicking the three dots next to each option, and selecting "Add desktop entry". This will add shortcuts to FL Studio within your desktop environment, so you can access it from your app launcher without needing to open Bottles every time. I also recommend you edit the desktop entry files using a tool such as [[KDE Menu Editor]] to give them more reasonable names. == Tweaks == === Documents folder pass-through === [[File:Flatseal options for Bottles (highlighted).png|thumb|Flatseal with relevant options highlighted]] It is likely that you'll need to share files between FL Studio and your main system (Project files, samples, etc.). The simplest way to do this is by creating a dedicated folder in your Documents directory, and linking it somewhere within your bottle's C drive. You may also pass through your entire home directory or documents directory, however this is not typically recommended for security purposes, as it requires allowing all other bottles access too. First create the desired directory in your file explorer, and then create a symbolic link ('''NOT''' a shortcut). This can be done in [[Dolphin]] by dragging and dropping a directory, then selecting "Link Here". To open your bottle's documents folder, go to bottles, click on your bottle, click the three dots on the top-right, and select "Browse files..." Now navigate to "users > steamuser > Documents". Drag and drop your folder here, and select "Link Here". Now, we must authorize Bottles to access this directory. The easiest way to do this is via [[Flatseal]]. Within the application, in the list on the left hand side, search for "Bottles". Once selected, in the page on the right, scroll down to the "Filesystem" section. If you wish to expose your entire home directory (Not recommended), enable the "All user files" toggle. Otherwise, click the add button next to "Other files", add an entry, such as "~/Documents/<your folder here>". (~) replaces your own home directory, so change this as needed. If you want to use an absolute path instead; "/home/<username>/Documents/<your folder here>". Now, you should be able to access this directory within FL Studio == References == 4066b9325c66f4895bc228d88b9ef7ae2832d8d4 3762 3758 2025-08-18T02:35:16Z 0Stormy 158 Rewrote FL Studio install guide wikitext text/x-wiki This guide will go through the steps of installing FL Studio on Linux via and app called Bottles. This guide targets FL Studio 25 but will likely also work on older versions, but usability on older versions cannot be guaranteed though. == Getting License Key == Since FL Studio is paid software, you will need to buy FL Studio and grab your registry key for it. You can find it under your owned products on the account page of Image-Line's website. Online registry may also work, but this functionality cannot be guaranteed, especially with older versions of FL Studio. This guide will NOT explain how to pirate FL Studio. You can still use FL Studio in demo mode if you do not have a license. == Installing Bottles == To start, you will need to install Bottles, which is a graphical software manager and runner for Windows software. You can get Bottles from the Flathub website, in your software manager by searching for Bottles, or by typing:<syntaxhighlight lang="bash"> flatpak install flathub com.usebottles.bottles </syntaxhighlight> === Update Flatpak Permissions === Bottles' flatpak package by default has quite limited file system access for security purposes, but you'll need to give it access to your home folder so you can install your registry key and save projects to a folder of your choosing. You can give Bottles access to your home folder with:<syntaxhighlight lang="bash"> flatpak override --user --filesystem-home com.usebottles.bottles </syntaxhighlight> == Setup == First, you'll want to open Bottles, on first launch it will give you a prompt to quickly set it up. Click continue and let Bottles set things up. [[File:Bottle Creation Screen.png|alt=Bottle Creation Screen|thumb|Bottle Creation Screen]] Once you're done letting Bottles set things up, create a new Bottle, call it something like "FL Studio" or similar, use Soda as your runner and make sure to set the Bottle type to "Gaming" as FL Studio and VST plugins use a lot of DirectX features that require DXVK to use. === Installing License Key === Once the Bottle is finished being created, click "Close" From there, click on the Bottle you just created and navigate down to the registry editor. Once you open the registry editor, in the the menubar navigate to Registry > Import Registry File... and install your .reg file from where ever you downloaded it to, Note that your host (system) storage devices will be binded to drive letters in Bottles automatically, such as Z:\ being equivelent to your root directory by default. === Installing FL Studio === [[File:FL Studio Installer.png|alt=FL Studio Installer|thumb|FL Studio Installer]] You will need to download the FL Studio installer from [https://www.image-line.com/fl-studio-download/ Image-Line's website]. From there in your Bottle, click "Run Executable..." and select the installer you downloaded. From there go through the installer, in older versions of FL Studio make sure to uncheck "AISO4ALL" as it has a lot of compatibility issues with Bottles. Once it's finished installing, click "Finish" to close the installer. You should now see an program listing in Bottles called "FL64", click the play button and FL Studio should launch either activated if you installed your license key or in trial mode if you didn't. Feel free to load up into demo project to test if things work properly, if everything works in the demo project, FL Studio is working and you have finished the install. [[File:FL Studio In Bottles.png|alt=FL Studio running in Bottles|thumb|FL Studio running in Bottles]] Adding a shortcut to FL Studio can be done by clicking the 3 dots in the program listing for FL Studio in your Bottle and clicking "Add Desktop Entry". Assuming everything works, you now have FL Studio running on your Linux machine. Enjoy! 3cca125b3a95631b396a28e02def11837bd47650 3765 3762 2025-08-18T14:55:26Z Platzmacher 245 Fixed a Typo wikitext text/x-wiki This guide will go through the steps of installing FL Studio on Linux via an app called Bottles. This guide targets FL Studio 25 but will likely also work on older versions, but usability on older versions cannot be guaranteed though. == Getting License Key == Since FL Studio is paid software, you will need to buy FL Studio and grab your registry key for it. You can find it under your owned products on the account page of Image-Line's website. Online registry may also work, but this functionality cannot be guaranteed, especially with older versions of FL Studio. This guide will NOT explain how to pirate FL Studio. You can still use FL Studio in demo mode if you do not have a license. == Installing Bottles == To start, you will need to install Bottles, which is a graphical software manager and runner for Windows software. You can get Bottles from the Flathub website, in your software manager by searching for Bottles, or by typing:<syntaxhighlight lang="bash"> flatpak install flathub com.usebottles.bottles </syntaxhighlight> === Update Flatpak Permissions === Bottles' flatpak package by default has quite limited file system access for security purposes, but you'll need to give it access to your home folder so you can install your registry key and save projects to a folder of your choosing. You can give Bottles access to your home folder with:<syntaxhighlight lang="bash"> flatpak override --user --filesystem-home com.usebottles.bottles </syntaxhighlight> == Setup == First, you'll want to open Bottles, on first launch it will give you a prompt to quickly set it up. Click continue and let Bottles set things up. [[File:Bottle Creation Screen.png|alt=Bottle Creation Screen|thumb|Bottle Creation Screen]] Once you're done letting Bottles set things up, create a new Bottle, call it something like "FL Studio" or similar, use Soda as your runner and make sure to set the Bottle type to "Gaming" as FL Studio and VST plugins use a lot of DirectX features that require DXVK to use. === Installing License Key === Once the Bottle is finished being created, click "Close" From there, click on the Bottle you just created and navigate down to the registry editor. Once you open the registry editor, in the the menubar navigate to Registry > Import Registry File... and install your .reg file from where ever you downloaded it to, Note that your host (system) storage devices will be binded to drive letters in Bottles automatically, such as Z:\ being equivelent to your root directory by default. === Installing FL Studio === [[File:FL Studio Installer.png|alt=FL Studio Installer|thumb|FL Studio Installer]] You will need to download the FL Studio installer from [https://www.image-line.com/fl-studio-download/ Image-Line's website]. From there in your Bottle, click "Run Executable..." and select the installer you downloaded. From there go through the installer, in older versions of FL Studio make sure to uncheck "AISO4ALL" as it has a lot of compatibility issues with Bottles. Once it's finished installing, click "Finish" to close the installer. You should now see an program listing in Bottles called "FL64", click the play button and FL Studio should launch either activated if you installed your license key or in trial mode if you didn't. Feel free to load up into demo project to test if things work properly, if everything works in the demo project, FL Studio is working and you have finished the install. [[File:FL Studio In Bottles.png|alt=FL Studio running in Bottles|thumb|FL Studio running in Bottles]] Adding a shortcut to FL Studio can be done by clicking the 3 dots in the program listing for FL Studio in your Bottle and clicking "Add Desktop Entry". Assuming everything works, you now have FL Studio running on your Linux machine. Enjoy! 91a08edd545b01b05e9c21443f706442153662d6 3767 3765 2025-08-18T18:15:26Z Ow0cast 249 restore guide warning template wikitext text/x-wiki {{Guide Warning}} This guide will go through the steps of installing FL Studio on Linux via an app called Bottles. This guide targets FL Studio 25 but will likely also work on older versions, but usability on older versions cannot be guaranteed though. == Getting License Key == Since FL Studio is paid software, you will need to buy FL Studio and grab your registry key for it. You can find it under your owned products on the account page of Image-Line's website. Online registry may also work, but this functionality cannot be guaranteed, especially with older versions of FL Studio. This guide will NOT explain how to pirate FL Studio. You can still use FL Studio in demo mode if you do not have a license. == Installing Bottles == To start, you will need to install Bottles, which is a graphical software manager and runner for Windows software. You can get Bottles from the Flathub website, in your software manager by searching for Bottles, or by typing:<syntaxhighlight lang="bash"> flatpak install flathub com.usebottles.bottles </syntaxhighlight> === Update Flatpak Permissions === Bottles' flatpak package by default has quite limited file system access for security purposes, but you'll need to give it access to your home folder so you can install your registry key and save projects to a folder of your choosing. You can give Bottles access to your home folder with:<syntaxhighlight lang="bash"> flatpak override --user --filesystem-home com.usebottles.bottles </syntaxhighlight> == Setup == First, you'll want to open Bottles, on first launch it will give you a prompt to quickly set it up. Click continue and let Bottles set things up. [[File:Bottle Creation Screen.png|alt=Bottle Creation Screen|thumb|Bottle Creation Screen]] Once you're done letting Bottles set things up, create a new Bottle, call it something like "FL Studio" or similar, use Soda as your runner and make sure to set the Bottle type to "Gaming" as FL Studio and VST plugins use a lot of DirectX features that require DXVK to use. === Installing License Key === Once the Bottle is finished being created, click "Close" From there, click on the Bottle you just created and navigate down to the registry editor. Once you open the registry editor, in the the menubar navigate to Registry > Import Registry File... and install your .reg file from where ever you downloaded it to, Note that your host (system) storage devices will be binded to drive letters in Bottles automatically, such as Z:\ being equivelent to your root directory by default. === Installing FL Studio === [[File:FL Studio Installer.png|alt=FL Studio Installer|thumb|FL Studio Installer]] You will need to download the FL Studio installer from [https://www.image-line.com/fl-studio-download/ Image-Line's website]. From there in your Bottle, click "Run Executable..." and select the installer you downloaded. From there go through the installer, in older versions of FL Studio make sure to uncheck "AISO4ALL" as it has a lot of compatibility issues with Bottles. Once it's finished installing, click "Finish" to close the installer. You should now see an program listing in Bottles called "FL64", click the play button and FL Studio should launch either activated if you installed your license key or in trial mode if you didn't. Feel free to load up into demo project to test if things work properly, if everything works in the demo project, FL Studio is working and you have finished the install. [[File:FL Studio In Bottles.png|alt=FL Studio running in Bottles|thumb|FL Studio running in Bottles]] Adding a shortcut to FL Studio can be done by clicking the 3 dots in the program listing for FL Studio in your Bottle and clicking "Add Desktop Entry". Assuming everything works, you now have FL Studio running on your Linux machine. Enjoy! 13ed500040f017f3afa21ff2c63162434cce0202 6 879 3759 2025-08-18T00:56:01Z 0Stormy 158 wikitext text/x-wiki The popup used by Bottles used to create a "Bottle", which is essentially a Wine prefix. 517ecc03dfc86658a3272c4c4d6fdff396701c69 6 880 3760 2025-08-18T02:20:14Z 0Stormy 158 wikitext text/x-wiki FL Studio installer program 792bfda0a77745b459a4a7cc0363c736b3664e1b 6 881 3761 2025-08-18T02:32:10Z 0Stormy 158 wikitext text/x-wiki FL Studio 25 running in Bottles. 4524e9c6f31ab215b37957ad3f2204f18530cb46 2 882 3763 2025-08-18T06:17:36Z Ow0cast 249 trout! wikitext text/x-wiki {| style="margin: 2em auto; text-align: center;" |- | [[File:Rainbow trout transparent.png|175px|link=Wikipedia:Trout]] | style="width: 280px; vertical-align: middle; padding-top: 0.5em;" | <p style="font-size: 225%; color: Red;">'''''Whack!'''''</p><p style="font-size: 115%;">''You've been [[Wikipedia:Whacking with a wet trout|whacked with a wet trout]].''</p><small>{{{1|Don't take this too seriously. Someone just wants to let you know that you did something silly.}}}</small> |} 23b45e12e4f691bd0548c30d8d12fedbc5fe7889 3 883 3764 2025-08-18T06:18:50Z Ow0cast 249 /* trout! */ new section wikitext text/x-wiki == trout! == {{User:ow0cast/trout}} <code>[[User:Ow0cast|/etc/owuh]] $ ([[User talk:Ow0cast|💬]] &#124; she/her)</code> 06:18, 18 August 2025 (UTC) e5e570cc8ab95039c4cbaffa0105d0c547742344 2 851 3766 3538 2025-08-18T18:12:41Z Platzmacher 245 updated my page wikitext text/x-wiki <syntaxhighlight lang="json" line="1"> { "user": { "name": "Eric", "age": 17, "gender": { "sex":"Agender", "pronouns": "any" }, "discord": { "username": "platzmacher", "link": "https://discord.com/users/749590720284852296" }, "OS": { "Linux": { "distro": "Linux Mint", "WM": "Cinnamon" }, "Windows": "Windows 11" }, "note": "just a random dude in the Internet that thinks he can do anything" } } </syntaxhighlight> i s̶t̶o̶l̶e̶ got inspired the idea from [[User:MymeType|MymeType]] 1f946f95cae4bda2d27e042b770dcf8bba6255d6 0 884 3768 2025-08-18T20:06:10Z Satnus 215 Created an okayish page for LXQT. wikitext text/x-wiki [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQT | image = [[File:Helix lxqt.svg|thumb]] | caption = LXQT Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]], [[QT]] | developers = The LXQT Team | website = [https://lxqt-project.org/ lxqt-project,org] }} LXQT (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQT is recommended for people who want a minimal system or have hardware constraints. === History === After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQT was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. === Installation === The most recommended method for installing LXQT is to either install a distribution which comes with LXQT by default, eg. [[Lubuntu]], or which offers it as a desktop environment option while installing the distribution, eg. [[debian]]. Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQT from their package manager. This will usually also pull all necessary dependencies for it. For most distributions, LXQt can be installed using the conventional package manager, for example: <syntaxhighlight lang="bash"> # apt install lxqt </syntaxhighlight> It is recommended to check your distribution's documentation if your distribution has a different method of packaging software. '''This is only for users whose systems have no desktop environment installed. It is not recommended to have two or more desktop environments on the same system''' It is also highly recommended to install a display manager, specifically [[SDDM]], though LXQT can also be started from the tty with the following command. <syntaxhighlight lang="bash"> # startlxqt </syntaxhighlight> It can also be started at boot by adding the following to .xinitrc: <syntaxhighlight> exec startlxqt </syntaxhighlight> <ref>https://wiki.archlinux.org/title/LXQt Archwiki Accessed: 2025-08-18 </ref> === References === eb36f030671112ff3fcaef6f9a91757d544101aa 3769 3768 2025-08-18T20:12:56Z Satnus 215 Fixed inconsistent capitalization for the LXQt abbreviation wikitext text/x-wiki [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|thumb]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]], [[QT]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project,org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. === History === After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. === Installation === The most recommended method for installing LXQt is to either install a distribution which comes with LXQt by default, eg. [[Lubuntu]], or which offers it as a desktop environment option while installing the distribution, eg. [[debian]]. Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This will usually also pull all necessary dependencies for it. For most distributions, LXQt can be installed using the conventional package manager, for example: <syntaxhighlight lang="bash"> # apt install lxqt </syntaxhighlight> It is recommended to check your distribution's documentation if your distribution has a different method of packaging software. '''This is only for users whose systems have no desktop environment installed. It is not recommended to have two or more desktop environments on the same system''' It is also highly recommended to install a display manager, specifically [[SDDM]], though LXQt can also be started from the tty with the following command. <syntaxhighlight lang="bash"> # startlxqt </syntaxhighlight> It can also be started at boot by adding the following to .xinitrc: <syntaxhighlight> exec startlxqt </syntaxhighlight> <ref>https://wiki.archlinux.org/title/LXQt Archwiki Accessed: 2025-08-18 </ref> === References === 2d316687add67e2a8efa14f0f48c664333a666cc 3770 3769 2025-08-19T13:10:59Z Madonuko 140 fix typos, tidy up wikitext text/x-wiki {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. === History === After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. === Installation === The most recommended method for installing LXQt is to either install a distribution which comes with LXQt by default, eg. [[Lubuntu]], or which offers it as a desktop environment option while installing the distribution, e.g. [[Debian]]. Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This will usually also pull all necessary dependencies for it. For most distributions, LXQt can be installed using the conventional package manager, for example: <syntaxhighlight lang="bash"> # apt install lxqt </syntaxhighlight> It is recommended to check your distribution's documentation if your distribution has a different method of packaging software. '''This is only for users whose systems have no desktop environment installed. It is not recommended to have two or more desktop environments on the same system''' It is also highly recommended to install a display manager, specifically [[SDDM]], though LXQt can also be started from the tty with the following command. <syntaxhighlight lang="bash"> # startlxqt </syntaxhighlight> It can also be started at boot by adding the following to .xinitrc:<ref>https://wiki.archlinux.org/title/LXQt Archwiki Accessed: 2025-08-18</ref> <syntaxhighlight> exec startlxqt </syntaxhighlight> === References === 860de9bc2b895f4064dc42169cdbfa0ff0576918 3771 3770 2025-08-19T16:43:21Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. === History === After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. === Installation === The most recommended method for installing LXQt is to either install a distribution which comes with LXQt by default, eg. [[Lubuntu]], or which offers it as a desktop environment option while installing the distribution, e.g. [[Debian]]. Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This will usually also pull all necessary dependencies for it. For most distributions, LXQt can be installed using the conventional package manager, for example: <syntaxhighlight lang="bash"> # apt install lxqt </syntaxhighlight> It is recommended to check your distribution's documentation if your distribution has a different method of packaging software. '''This is only for users whose systems have no desktop environment installed. It is not recommended to have two or more desktop environments on the same system''' It is also highly recommended to install a display manager, specifically [[SDDM]], though LXQt can also be started from the tty with the following command. <syntaxhighlight lang="bash"> # startlxqt </syntaxhighlight> It can also be started at boot by adding the following to .xinitrc:<ref>https://wiki.archlinux.org/title/LXQt Archwiki Accessed: 2025-08-18</ref> <syntaxhighlight> exec startlxqt </syntaxhighlight> === References === edbf4d0a85306d3c499ea3ce362780083ae81623 3772 3771 2025-08-19T16:48:53Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The most recommended method for installing LXQt is to either install a distribution which comes with LXQt by default, eg. [[Lubuntu]], or which offers it as a desktop environment option while installing the distribution, e.g. [[Debian]]. Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This will usually also pull all necessary dependencies for it. For most distributions, LXQt can be installed using the conventional package manager, for example: <syntaxhighlight lang="bash"> # apt install lxqt </syntaxhighlight> It is recommended to check your distribution's documentation if your distribution has a different method of packaging software. '''This is only for users whose systems have no desktop environment installed. It is not recommended to have two or more desktop environments on the same system''' It is also highly recommended to install a display manager, specifically [[SDDM]], though LXQt can also be started from the tty with the following command. <syntaxhighlight lang="bash"> # startlxqt </syntaxhighlight> It can also be started at boot by adding the following to .xinitrc:<ref>https://wiki.archlinux.org/title/LXQt Archwiki Accessed: 2025-08-18</ref> <syntaxhighlight> exec startlxqt </syntaxhighlight> == References == 97ea00b35c440a4081fbf8cbdc9849b5cb131a30 3798 3772 2025-08-21T14:48:13Z Satnus 215 Omitted some incorrect information. wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The most recommended method for installing LXQt is to either install a distribution which comes with LXQt by default, eg. [[Lubuntu]], or which offers it as a desktop environment option while installing the distribution, e.g. [[Debian]]. Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This will usually also pull all necessary dependencies for it. The way to install depends highly on the distribution. It is recommended to look at either distribution documentation or distribution specific guides to install LXQt. '''This is only for users whose systems have no desktop environment installed. It is not recommended to have two or more desktop environments on the same system''' After installation, it is highly recommended to also install [[SDDM]], LXQt's preferred display manager, to be able to start LXQt smoothly. == References == d84d45c7d6a1453163f68653f2506357c745b5bd 6 885 3773 2025-08-19T20:22:02Z Atmois 13 test wikitext text/x-wiki == Summary == test 88b31b8ee5348e290cd75f142d356df331cc5e21 0 842 3774 3496 2025-08-20T11:13:49Z NachoLord117 260 Made mention that "/etc/doas.conf" will probably need to be created manually. wikitext text/x-wiki [[Category:Software]] The command line tool <code>doas</code> is used to run commands as another user. The configuration file is located at <code>/etc/doas.conf</code>. Do note, however, you may need to manually create this file before using <code>doas</code>. To do so, see <code>man doas.conf</code> in man 5. == Usage == {| class="wikitable" |+Common opendoas Commands !Command !Description |- |<code>doas <command></code> |Run the given command as root |- |<code>doas -s</code> |Opens SHELL or the shell listed in /etc/passwd with root permissions |- |<code>doas -L</code> |Clear persisted authentication if present |- |<code>doas -C</code> |Check configuration file for errors. If run with another command, this will be performed. |- |<code>doas -n</code> |Runs in non-interactive mode. If <code>nopass</code> is not set for the given command, it will fail. |- |<code>doas -u <user></code> |Executes the shell as the given user |} == History == The <code>doas</code> command first appeared in OpenBSD 5.8. <code>doas</code> was forked into Opendoas in 2015 by Ted Unangst <tedu@openbsd.org>. d89bf707be30aba6ec31b253853678a4d97e1905 0 736 3775 3731 2025-08-20T11:19:19Z NachoLord117 260 Placed the sed example in <code> tags, and added a final "/". wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[category:software]] [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html ed], The IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> ed was part of the original Unix operating system from 1969.<ref>[https://man.cat-v.org/unix-1st/1/ed ed(1)]{{Dead Link|2025-08-14|Cannot connect to host man.cat-v.org:443 ssl:default [None]}}, Unix First Edition Manual Page, 1971-11-03 (Accessed: 2025-08-09)</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>[https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html Shell & Utilities: Detailed Toc], IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s <code>s/regexp/replacement/</code> command was inherited from ed.<ref>[https://www.gnu.org/software/ed/manual/ed_manual.html GNU 'ed' Manual], GNU, 1993-08-09 (Accessed: 2025-08-09)</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor vi, whose variants remain some of the most popular TUI text editors.<ref>[https://ex-vi.sourceforge.net/ex.html ex.1], 2005-03-24 (Accessed: 2025-08-09)</ref><ref>[https://ex-vi.sourceforge.net/vi.html vi.1], 2005-03-24 (Accessed: 2025-08-09)</ref> == References == 6f93eb7689868181339919f9aedb95084fd61786 3801 3775 2025-08-21T17:39:53Z Imnotgoodatnames 121 Removed dead link label from second citation because the site in question isn't dead and works fine for me and others wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[category:software]] [[File:Ed1.png|thumb|Text editor ed]] ed is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html ed], The IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> ed was part of the original Unix operating system from 1969.<ref>[https://man.cat-v.org/unix-1st/1/ed ed(1)], Unix First Edition Manual Page, 1971-11-03 (Accessed: 2025-08-09)</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>[https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html Shell & Utilities: Detailed Toc], IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s <code>s/regexp/replacement/</code> command was inherited from ed.<ref>[https://www.gnu.org/software/ed/manual/ed_manual.html GNU 'ed' Manual], GNU, 1993-08-09 (Accessed: 2025-08-09)</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor vi, whose variants remain some of the most popular TUI text editors.<ref>[https://ex-vi.sourceforge.net/ex.html ex.1], 2005-03-24 (Accessed: 2025-08-09)</ref><ref>[https://ex-vi.sourceforge.net/vi.html vi.1], 2005-03-24 (Accessed: 2025-08-09)</ref> == References == a874549f321f951635f20b15981a149b98b8aeea 0 886 3776 2025-08-20T12:13:54Z NachoLord117 260 This is the first version of this article. It documents a bit of history with vi, a barebones "how-to", and some implementations of vi. wikitext text/x-wiki {{Needs Citations|date=august 2025}} The vi program is a full-screen console-based text editor. It was originally written in the 1970s by Bill Joy, as an enhancement for [[ex]], which in tern was an enhanced version of [[ed]]. As such, vi still has many ex-like features today. To use vi, you can hit "i" to enter "insert mode". You then may type what you wish, and hit the <code>esc</code> key to exit "insert mode". When you're no longer in "insert mode", you can hit the ":" (colon) command to type in ex-like commands. The two most common commands are <code>w [filename]</code> to save the file, and <code>q</code>, which is used to quit the program. These commands can be combined to quit and save in one step, like so: <code>wq</code>. To quit without saving, enter <code>q!</code>. When not in insert mode, you may use the <code>h</code> key to move back one column, <code>j</code> to move the cursor down one line, <code>k</code> to move up a line, and the <code>l</code> to move forward one column. Please note that these letters are lowercase. As is often the case with Unix programs, capitalization matters. Also, when in insert mode, you <i>might</i> be able to use your arrow keys, although this seems to depend on which implementation of vi you are using. It is generally recommended to learn the above keys instead. Modern implementations of vi consist of vim, neovim, elvis, nvi, and the a version of vi built in to [[busybox]], the latter of which can be called via <code>busybox vi</code>. [[Category:Software]] 296395790982857ab07360e8a74abd19012cee7c 3777 3776 2025-08-20T12:20:50Z NachoLord117 260 Turned the implementations of vi into links. wikitext text/x-wiki {{Needs Citations|date=august 2025}} The vi program is a full-screen console-based text editor. It was originally written in the 1970s by Bill Joy, as an enhancement for [[ex]], which in tern was an enhanced version of [[ed]]. As such, vi still has many ex-like features today. To use vi, you can hit "i" to enter "insert mode". You then may type what you wish, and hit the <code>esc</code> key to exit "insert mode". When you're no longer in "insert mode", you can hit the ":" (colon) command to type in ex-like commands. The two most common commands are <code>w [filename]</code> to save the file, and <code>q</code>, which is used to quit the program. These commands can be combined to quit and save in one step, like so: <code>wq</code>. To quit without saving, enter <code>q!</code>. When not in insert mode, you may use the <code>h</code> key to move back one column, <code>j</code> to move the cursor down one line, <code>k</code> to move up a line, and the <code>l</code> to move forward one column. Please note that these letters are lowercase. As is often the case with Unix programs, capitalization matters. Also, when in insert mode, you <i>might</i> be able to use your arrow keys, although this seems to depend on which implementation of vi you are using. It is generally recommended to learn the above keys instead. Modern implementations of vi consist of [[vim]], [[neovim]], [[elvis]], [[nvi]], and the a version of vi built in to [[busybox]], the latter of which can be called via <code>busybox vi</code>. [[Category:Software]] 5f77fa6b263fbb21562a6ba2afbd354bc45c7dcd 3778 3777 2025-08-20T12:31:44Z NachoLord117 260 Added headers wikitext text/x-wiki {{Needs Citations|date=august 2025}} The vi program is a full-screen console-based text editor. It was originally written in the 1970s by Bill Joy, as an enhancement for [[ex]], which in tern was an enhanced version of [[ed]]. As such, vi still has many ex-like features today. ==Using vi== To use vi, you can hit "i" to enter "insert mode". You then may type what you wish, and hit the <code>esc</code> key to exit "insert mode". When you're no longer in "insert mode", you can hit the ":" (colon) command to type in ex-like commands. The two most common commands are <code>w [filename]</code> to save the file, and <code>q</code>, which is used to quit the program. These commands can be combined to quit and save in one step, like so: <code>wq</code>. To quit without saving, enter <code>q!</code>. When not in insert mode, you may use the <code>h</code> key to move back one column, <code>j</code> to move the cursor down one line, <code>k</code> to move up a line, and the <code>l</code> to move forward one column. Please note that these letters are lowercase. As is often the case with Unix programs, capitalization matters. Also, when in insert mode, you <i>might</i> be able to use your arrow keys, although this seems to depend on which implementation of vi you are using. It is generally recommended to learn the above keys instead. ==Implementations== Modern implementations of vi consist of [[vim]], [[neovim]], [[elvis]], [[nvi]], and the a version of vi built in to [[busybox]], the latter of which can be called via <code>busybox vi</code>. [[Category:Software]] 80cee5d55e4430e2a04c8b3221207dac9f5f9f35 3779 3778 2025-08-20T12:46:11Z NachoLord117 260 Added a stub template. wikitext text/x-wiki {{Needs Citations|date=august 2025}} {{stub|date=august 2025}} The vi program is a full-screen console-based text editor. It was originally written in the 1970s by Bill Joy, as an enhancement for [[ex]], which in tern was an enhanced version of [[ed]]. As such, vi still has many ex-like features today. ==Using vi== To use vi, you can hit "i" to enter "insert mode". You then may type what you wish, and hit the <code>esc</code> key to exit "insert mode". When you're no longer in "insert mode", you can hit the ":" (colon) command to type in ex-like commands. The two most common commands are <code>w [filename]</code> to save the file, and <code>q</code>, which is used to quit the program. These commands can be combined to quit and save in one step, like so: <code>wq</code>. To quit without saving, enter <code>q!</code>. When not in insert mode, you may use the <code>h</code> key to move back one column, <code>j</code> to move the cursor down one line, <code>k</code> to move up a line, and the <code>l</code> to move forward one column. Please note that these letters are lowercase. As is often the case with Unix programs, capitalization matters. Also, when in insert mode, you <i>might</i> be able to use your arrow keys, although this seems to depend on which implementation of vi you are using. It is generally recommended to learn the above keys instead. ==Implementations== Modern implementations of vi consist of [[vim]], [[neovim]], [[elvis]], [[nvi]], and the a version of vi built in to [[busybox]], the latter of which can be called via <code>busybox vi</code>. [[Category:Software]] 7d8b2f50193ec5fa09dd345c79c148a29602ec98 3799 3779 2025-08-21T17:22:08Z Imnotgoodatnames 121 added 'a' command and information about nvi wikitext text/x-wiki {{Needs Citations|date=august 2025}} {{stub|date=august 2025}} The vi program is a full-screen console-based text editor. It was originally written in the 1970s by Bill Joy, as an enhancement for [[ex]], which in tern was an enhanced version of [[ed]]. As such, vi still has many ex-like features today. ==Using vi== To use vi, you can hit <code>i</code> or <code>a</code> (append) to enter "insert mode". You then may type what you wish, and hit the <code>esc</code> key to exit "insert mode". When you're no longer in "insert mode", you can hit the ":" (colon) command to type in ex-like commands. The two most common commands are <code>w [filename]</code> to save the file, and <code>q</code>, which is used to quit the program. These commands can be combined to quit and save in one step, like so: <code>wq</code>. To quit without saving, enter <code>q!</code>. When not in insert mode, you may use the <code>h</code> key to move back one column, <code>j</code> to move the cursor down one line, <code>k</code> to move up a line, and the <code>l</code> to move forward one column. Please note that these letters are lowercase. As is often the case with Unix programs, capitalization matters. Also, when in insert mode, you <i>might</i> be able to use your arrow keys, although this seems to depend on which implementation of vi you are using. It is generally recommended to learn the above keys instead. ==Implementations== Modern implementations of vi consist of [[vim]], [[neovim]], [[elvis]], [[nvi]], and the a version of vi built in to [[busybox]], the latter of which can be called via <code>busybox vi</code>. nvi/nex is a replacement for vi/ex and was originally developed as part of 4BSD.<ref>https://man.openbsd.org/vi.1</ref> [[Category:Software]] 6d6d0f70545325913d3568c63a91b2b774026f42 0 887 3780 2025-08-20T13:08:55Z NachoLord117 260 Wrote a few paragraphs, describing what Pulseaudio is. wikitext text/x-wiki [[Category:Software]] {{Stub}} {{Needs Citations}} '''Pulseaudio''', sometimes known as simply '''pulse''', is a [[SoundSever|Sound Server]] intended for GNU/Linux systems. It can serve as an intermediate programs between a sound-generating program (such as a music player), and outputs such as [[Bluez]], [[ALSA]], and the [[oss|Open Sound System]] (OSS). Being a Sound Server, Pulseaudio is capable of mixing multiple audio streams together in real-time. It can also load various plugins, which can enhance it's capabilities. Pulseaudio has been criticized for it's high latency, and is being deprecated in favor of [[Pipewire]]. 47c582b4ff0398f781f022fef5bc9132c89acaae 14 397 3781 3703 2025-08-20T13:28:20Z NachoLord117 260 /* List of Software */ Added a new Category: MultiMedia. I added PulseAudio, PipeWire, mpv, and ffmpeg to it. wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == {| class="wikitable" |+Text Editors !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} {| class="wikitable" |+System Utilities !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[opendoas|OpenDoas]] |Ted Unangst |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} {| class="wikitable" |+Installers !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} {| class="wikitable" |+Useless But Fun !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} {| class="wikitable" |+Programming !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} {| class="wikitable" |+Open-Source Music Players !Application !Developer !Ecosystem (If Any) !UI Framework |- |[https://mierak.github.io/rmpc RMPC] |Mierak (And Others) |[https://www.musicpd.org/ MPD] |[https://crates.io/crates/ratatui Ratatui] ([[TUI]]) |- |[https://github.com/ncmpcpp/ncmpcpp NCMPCPP] |Andrzej Rybczak (And Others) |[https://www.musicpd.org/ MPD] |NCurses ([[TUI]]) |- |[https://musikcube.com/ Musikcube] |Casey Langen |Musikcube (Custom) |NCurses ([[TUI]]) |} {| class="wikitable" |+Shells !Application !Developer |- |[https://www.gnu.org/software/bash/ Bash] |[[GNU]] |- |[https://fishshell.com/ Fish] |Axel Liljencrantz (And Others) |- |[https://www.zsh.org/ ZSH] |Peter Stephenson |} {| class="wikitable" |+Open-Source Games !Game !Description !Genre |- |[https://www.supertux.org/ SuperTux] |A free and open-source platformer game inspired by Super Mario Bros. |Platformer |- |[https://supertuxkart.net SuperTuxKart] |A free and open-source racing game inspired by Super Mario Kart. |Racer |- |[https://xonotic.org Xonotic] |A free and open-source shooter game based on the Quake engine. |Shooter |- |[https://neverball.org/ Neverball] |Tilt the floor to roll a ball through an obstacle course before time runs out. Neverball is part puzzle game, part action game, and entirely a test of skill. |Puzzler |- |[https://github.com/jorio/Bugdom Bugdom (Ported For Modern Systems)] |Bugdom is a 1999 Macintosh game by Pangea Software. You play as Rollie McFly, a pill bug on a quest to save ladybugs from King Thorax’s iron grip on the Bugdom. |Quest Adventure |- |[https://www.classicube.net/ ClassiCube] |A free and open-source voxel game inspired by Minecraft Classic. |Sandbox |- |[https://tuxracer.sourceforge.net/ Extreme Tux Racer] |A free and open-source game where Tux tries to glide on his belly all the way down to the finish line before the time is up. |Racer |- |[https://www.teeworlds.com/ Teeworlds] |Teeworlds is a '''free online multiplayer game''', available for '''all major operating systems'''. Battle with up to '''16 players''' in a variety of game modes, including '''Team Deathmatch''' and '''Capture The Flag'''. You can even '''design your own maps!''' |Competitive |- |[https://www.luanti.org/ Luanti (Formerly Minetest)] |A free and open-source voxel game engine. |Sandbox |- |[https://veloren.net/ Veloren] |Veloren is an action-adventure role-playing game set in a vast fantasy world. |Action Adventure |- |[https://play0ad.com/ 0 A.D.] |'''0 A.D.''' (pronounced “zero-ey-dee”) is a free, open-source, historical Real Time Strategy (RTS) game currently under development by Wildfire Games, a global group of volunteer game developers. As the leader of an ancient civilization, you must gather the resources you need to raise a military force and dominate your enemies. |Real-Time Strategy |- |[https://github.com/seehuhn/moon-buggy Moon Buggy] |A free and open-source terminal-based game where you jump over craters. |Action |- |[https://www.victornils.net/tetris/ Vitetris] |A free and open-source recreation of Tetris that can be played in your terminal. |Real-Time Strategy |- |[https://crates.io/crates/tui48 Tui48] |An elegant and faithful 2048 clone in the terminal. (Written in Rust.) |Strategy |} {|class="wikitable" |+MultiMedia !Logo !Application !Developer !Purpose |- |None |[[PulseAudio]] |[[FreeDesktop]] |Sound Server |- |None |[[PipeWire]] |[[FreeDesktop]] |Sound Server |- |None |[[mpv]] |Many Contributors |Audio/Video player |- |None |[[ffmpeg]] |Many Contributors |Media Converter |} 821fd1c35b4df073851012cf72738181692bd343 3784 3781 2025-08-20T13:42:45Z NachoLord117 260 /* List of Software */ Added DeaDBeef as a music player. wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer == List of Software == {| class="wikitable" |+Text Editors !Logo !Application !Developer |- |[[File:Breezeicons-apps-48-emacs.svg|alt=A purple circle with the letter E on it|frameless|64x64px]] |[[GNU Emacs]] |[[GNU]] |- |None |[[Vi]] |Bill Joy |- |None |[[Ed]] |AT&T Bell Labs |- |None |[[Ex]] |Bill Joy |- |[[File:Vimlogo.svg|alt=a green diamond with "Vim" written on it|frameless|64x64px]] |[[Vim]] |Bram Moolenaar |- |[[File:Neovim-mark.svg|alt=A blue and green letter N|frameless|78x78px]] |[[Neovim|NeoVim]] |Many Contributors |- |[[File:Gnu-nano.svg|alt=ASCII text shape of the lowercase letter n|frameless|64x64px]] |[[Gnu nano|GNU Nano]] |[[GNU]] |} {| class="wikitable" |+System Utilities !Logo !Application !Developer |- |None |[[neofetch]] |Dylan Araps |- |[[File:Fastfetch logo.png|alt=a mockup of a terminal with a spaceship on the left and arrows on the right mimicking text|frameless|64x64px]] |[[fastfetch]] |Many Contributors |- |None |[[GRUB]] |[[GNU]] |- |None |[[grep]] |[[GNU]] |- |[[File:Sudo logo (2019).png|alt=A joyous sandwich with a face with the word sudo underneath|frameless|71x71px]] |[[sudo]] |Todd C. Miller |- |None |[[opendoas|OpenDoas]] |Ted Unangst |- |None |[[sed]] |[[GNU]] |- |None |[[Hyfetch]] |hykilpikonna |- |None |[[Nix-shell|Nix Shell]] |Nix |} {| class="wikitable" |+Installers !Logo !Application !Developer |- |[[File:Calamares Logo.png|alt=an orange box with a white arrow pointing down|frameless|64x64px]] |[[Calamares]] |Adriaan de Groot |} {| class="wikitable" |+Useless But Fun !Logo !Application !Developer |- |None |[[cowsay]] |cowsay-org |} {| class="wikitable" |+Programming !Logo !Application !Developer |- |None |[[AWK]] |[[GNU]] |- |[[File:Git-logo-orange.svg|alt=an orange diamond with branches coming out, and the word git next to that|frameless|64x64px]] |[[Git]] |Linus Torvalds |- |None |[[glibc]] |[[GNU]] |- |None |[[musl]] |Rich Felker |} {| class="wikitable" |+Open-Source Music Players !Application !Developer !Ecosystem (If Any) !UI Framework |- |[https://mierak.github.io/rmpc RMPC] |Mierak (And Others) |[https://www.musicpd.org/ MPD] |[https://crates.io/crates/ratatui Ratatui] ([[TUI]]) |- |[https://github.com/ncmpcpp/ncmpcpp NCMPCPP] |Andrzej Rybczak (And Others) |[https://www.musicpd.org/ MPD] |NCurses ([[TUI]]) |- |[https://musikcube.com/ Musikcube] |Casey Langen |Musikcube (Custom) |NCurses ([[TUI]]) |- |[[DeaDBeef]] |Oleksiy Yakovenko and other contributors |DeaDBeef (Custom) |[[GTK]] ([[GUI]]) |} {| class="wikitable" |+Shells !Application !Developer |- |[https://www.gnu.org/software/bash/ Bash] |[[GNU]] |- |[https://fishshell.com/ Fish] |Axel Liljencrantz (And Others) |- |[https://www.zsh.org/ ZSH] |Peter Stephenson |} {| class="wikitable" |+Open-Source Games !Game !Description !Genre |- |[https://www.supertux.org/ SuperTux] |A free and open-source platformer game inspired by Super Mario Bros. |Platformer |- |[https://supertuxkart.net SuperTuxKart] |A free and open-source racing game inspired by Super Mario Kart. |Racer |- |[https://xonotic.org Xonotic] |A free and open-source shooter game based on the Quake engine. |Shooter |- |[https://neverball.org/ Neverball] |Tilt the floor to roll a ball through an obstacle course before time runs out. Neverball is part puzzle game, part action game, and entirely a test of skill. |Puzzler |- |[https://github.com/jorio/Bugdom Bugdom (Ported For Modern Systems)] |Bugdom is a 1999 Macintosh game by Pangea Software. You play as Rollie McFly, a pill bug on a quest to save ladybugs from King Thorax’s iron grip on the Bugdom. |Quest Adventure |- |[https://www.classicube.net/ ClassiCube] |A free and open-source voxel game inspired by Minecraft Classic. |Sandbox |- |[https://tuxracer.sourceforge.net/ Extreme Tux Racer] |A free and open-source game where Tux tries to glide on his belly all the way down to the finish line before the time is up. |Racer |- |[https://www.teeworlds.com/ Teeworlds] |Teeworlds is a '''free online multiplayer game''', available for '''all major operating systems'''. Battle with up to '''16 players''' in a variety of game modes, including '''Team Deathmatch''' and '''Capture The Flag'''. You can even '''design your own maps!''' |Competitive |- |[https://www.luanti.org/ Luanti (Formerly Minetest)] |A free and open-source voxel game engine. |Sandbox |- |[https://veloren.net/ Veloren] |Veloren is an action-adventure role-playing game set in a vast fantasy world. |Action Adventure |- |[https://play0ad.com/ 0 A.D.] |'''0 A.D.''' (pronounced “zero-ey-dee”) is a free, open-source, historical Real Time Strategy (RTS) game currently under development by Wildfire Games, a global group of volunteer game developers. As the leader of an ancient civilization, you must gather the resources you need to raise a military force and dominate your enemies. |Real-Time Strategy |- |[https://github.com/seehuhn/moon-buggy Moon Buggy] |A free and open-source terminal-based game where you jump over craters. |Action |- |[https://www.victornils.net/tetris/ Vitetris] |A free and open-source recreation of Tetris that can be played in your terminal. |Real-Time Strategy |- |[https://crates.io/crates/tui48 Tui48] |An elegant and faithful 2048 clone in the terminal. (Written in Rust.) |Strategy |} {|class="wikitable" |+MultiMedia !Logo !Application !Developer !Purpose |- |None |[[PulseAudio]] |[[FreeDesktop]] |Sound Server |- |None |[[PipeWire]] |[[FreeDesktop]] |Sound Server |- |None |[[mpv]] |Many Contributors |Audio/Video player |- |None |[[ffmpeg]] |Many Contributors |Media Converter |} c65fc711d32ebbbe22dbd43e2339a1038c8d953d 3800 3784 2025-08-21T17:32:56Z Atmois 13 Removed the list of software because maintaining that would be impossible, the autogenerated category list is sufficient, the custom content should be explaining what software is, a history etc with some examples rather than trying to list every piece of software out there. wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer. 4200462ee38cd92ad564b0e8027935bc7fd70f11 0 638 3782 3386 2025-08-20T13:31:28Z NachoLord117 260 /* Performance */ Added information about reducing access times & preventing wear on physical media. Also merged two paragraphs and fixed a minor capitalization issue. wikitext text/x-wiki Ext4 is an advanced level of the ext3 [[filesystems]] which incorporates scalability and reliability enhancements for supporting large filesystems (64 bit) in keeping with increasing disk capacities and state-of-the-art feature requirements. It is currently the default filesystem for some popular [[Linux Distributions|distributions]], however it is being steadily replaced by the much newer [[BTRFS]]. ---- === Formatting a partition to ext4 === Formatting a disk partition to ext4 can be done using the <code>[https://linux.die.net/man/8/mkfs mkfs]</code> utility, which is a generic wrapper over individual binaries that create filesystems on provided partitions. Information on how to do it can be found in [[Guides:Ext4]]. === Filesystem options === Ext4 provides numerous options for tuning the filesystem to your workloads. A complete list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. ==== Performance ==== You can enable the <code>noatime</code> mount option, which disables atime (a feature that notes when a file was last accessed by a user). This can potentially speed up access times while reducing wear on flash-based media, such as memory cards, flash drives, and SSDs. The filesystem initially stores your data (to be written) in memory and then flushes it to the disk in the form of a "commit" once it reaches a certain threshold of time. This time is referred to as the "commit interval", increasing the value also increases the chance of data loss but can provide better performance on slower disks (i.e. HDDs) ==== Changing the data mode ==== Ext4 provides three data modes<ref>[https://www.kernel.org/doc/html/v4.19/filesystems/ext4/ext4.html#data-mode 1. General Information — The Linux Kernel documentation], The kernel development community, 2018-10-22 (Accessed: 2025-08-09)</ref>. <pre> writeback mode In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance. ordered mode In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it’s time to write the new metadata out to disk, the associated data blocks are written first. In general, this mode performs slightly slower than writeback but significantly faster than journal mode. journal mode data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location. In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Enabling this mode will disable delayed allocation and O_DIRECT support. </pre> You can change the data mode by setting the <code>data=...</code> mount option. ==== Disabling the write barrier ==== Warning: Disabling the write barrier when you do not have a battery backed cache is a bad idea. Write barriers enforce that metadata is properly written and ordered on the disk, increasing data safety. It does however come a performance cost. The mount option <code>barrier=0</code> disables write barriers. Only disable this option if you know what you're doing. ==== Async journal commits and external journaling device ==== Ext4 allows other partitions/disks to act as a journal, this can provide a significant speedup if, for example, an SSD is used as a journal for data stored in an HDD. It is also recommended to enable <code>journal_async_commit</code> which can provide a nice speedup<ref>[https://libre-consulting.com/posts/fs_ext4_external_journal/ ext4: using external journal to optimise performance], Libre Solutions Pty Ltd, 2019-01-24 (Accessed: 2025-08-09)</ref> ==== Enabling fscrypt support ==== fscrypt<ref>[https://github.com/google/fscrypt GitHub - google/fscrypt: Go tool for managing Linux filesystem encryption], Google, 2017-08-09 (Accessed: 2025-08-09)</ref> is a high-level tool for the management of Linux native filesystem encryption. fscrypt manages metadata, key generation, key wrapping, PAM integration, and provides a uniform interface for creating and modifying encrypted directories. To enable support for FSCrypt in ext4, enable the <code>encrypt</code> feature flag. ==== Enabling fast_commit support ==== fast_commit <ref>[https://lwn.net/Articles/842385/ <nowiki>Fast commits for ext4 [LWN.net]</nowiki>], Marta Rybczyńska, 2021-01-15 (Accessed: 2025-08-09)</ref> is an ext4 feature flag which introduces a newer, and lighter weight journaling method. It can be enabled by setting the <code>fast_commit</code> feature flag. == References == <references /> c82145fb52ed1f05f316063e3e22fb622674b051 15 888 3783 2025-08-20T13:37:18Z NachoLord117 260 /* Merge "Open-Source Music Players" with "MultiMedia"? */ new section wikitext text/x-wiki == Merge "Open-Source Music Players" with "MultiMedia"? == I've created a new category, "MultiMedia", as a catch-all for all things related to audio and video. Since I've done that, perhaps the "Open-Source Music Players" category should become a sub-category? Or, did I just make it obsolete? [[User:NachoLord117|NachoLord117]] ([[User talk:NachoLord117|talk]]) 13:37, 20 August 2025 (UTC) 5c444dcf24a8705aa6ea10505e1ab4c62aabeaf8 0 848 3785 3701 2025-08-20T14:10:26Z NachoLord117 260 Updated the information on the death of CyberOS, based on a reference via ArchiveOS.org. wikitext text/x-wiki [[category:Linux Distributions]] [[category:Desktop Environments]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued on 2021-06-23<ref>[https://archiveos.org/cyberos-linux/], CyberOS Team, 2022 (Accessed: 2025-08-20)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the DE, and Arch Linux was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to Ubuntu. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were remove and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The new CutefishOS team which was rebased to Sichuan also did not live long due to lack of Western support, and silently died out between mid-2021 and 2022. === CutefishOS Reborn === CutefishOS Reborn was a Western community's attempt to revive CutefishOS's development. It gauged some interest but very quickly died off in mid-2022. === LingmoOS === [https://github.com/LingmoOS/LingmoOS LingmoOS] is an active revive<ref>[https://github.com/orgs/cutefishos/discussions/22 Is this project dead or still in development? · cutefishos · Discussion #22], GitHub, 2023 (Accessed: 2025-08-11)</ref> of CutefishOS, but it has not received major attention from the media. == CyberDE == [[File:VSCode In Cutefish.png|thumb|right|Visual Studio Code running on CutefishDE.<ref>[https://cutefishos.com CutefishOS], Cutefish Team, 2025 (Accessed: 2025-08-11)</ref>]] The desktop environment that came with CyberOS, usually referred to as ''Cyber'' or ''CyberDE'', was made using Qt5 and was commonly said to resemble the look and feel of Mac OS X.<ref>[https://wiki.archlinux.org/title/Cutefish Cutefish], ArchWiki (Accessed: 2025-08-11)</ref> <code>cyber-launcher</code> came with the dock at the bottom, which had a button that opens the launcher, and a status line bar with embedded global context menus at the top. Many parts of the interface were also partially transparent. Window controls were at the top right corner and resembles [[Microsoft Windows]], while titles were centred. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives] == References == 3043d147c351806904ba478a442148a88d7305b7 3786 3785 2025-08-20T14:12:52Z NachoLord117 260 /* The Purge */ Fixed some typos. wikitext text/x-wiki [[category:Linux Distributions]] [[category:Desktop Environments]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued on 2021-06-23<ref>[https://archiveos.org/cyberos-linux/], CyberOS Team, 2022 (Accessed: 2025-08-20)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the DE, and Arch Linux was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to Ubuntu. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were removed and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The new CutefishOS team, which was rebased to Sichuan, also did not live long, due to lack of Western support, and silently died out between mid-2021 and 2022. === CutefishOS Reborn === CutefishOS Reborn was a Western community's attempt to revive CutefishOS's development. It gauged some interest but very quickly died off in mid-2022. === LingmoOS === [https://github.com/LingmoOS/LingmoOS LingmoOS] is an active revive<ref>[https://github.com/orgs/cutefishos/discussions/22 Is this project dead or still in development? · cutefishos · Discussion #22], GitHub, 2023 (Accessed: 2025-08-11)</ref> of CutefishOS, but it has not received major attention from the media. == CyberDE == [[File:VSCode In Cutefish.png|thumb|right|Visual Studio Code running on CutefishDE.<ref>[https://cutefishos.com CutefishOS], Cutefish Team, 2025 (Accessed: 2025-08-11)</ref>]] The desktop environment that came with CyberOS, usually referred to as ''Cyber'' or ''CyberDE'', was made using Qt5 and was commonly said to resemble the look and feel of Mac OS X.<ref>[https://wiki.archlinux.org/title/Cutefish Cutefish], ArchWiki (Accessed: 2025-08-11)</ref> <code>cyber-launcher</code> came with the dock at the bottom, which had a button that opens the launcher, and a status line bar with embedded global context menus at the top. Many parts of the interface were also partially transparent. Window controls were at the top right corner and resembles [[Microsoft Windows]], while titles were centred. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives] == References == 728c3e7552dd062aef40774f04a3eb78d3235bc4 3787 3786 2025-08-20T14:14:07Z NachoLord117 260 /* LingmoOS */ Fixed another typo. wikitext text/x-wiki [[category:Linux Distributions]] [[category:Desktop Environments]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued on 2021-06-23<ref>[https://archiveos.org/cyberos-linux/], CyberOS Team, 2022 (Accessed: 2025-08-20)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the DE, and Arch Linux was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to Ubuntu. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were removed and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The new CutefishOS team, which was rebased to Sichuan, also did not live long, due to lack of Western support, and silently died out between mid-2021 and 2022. === CutefishOS Reborn === CutefishOS Reborn was a Western community's attempt to revive CutefishOS's development. It gauged some interest but very quickly died off in mid-2022. === LingmoOS === [https://github.com/LingmoOS/LingmoOS LingmoOS] is an active revival<ref>[https://github.com/orgs/cutefishos/discussions/22 Is this project dead or still in development? · cutefishos · Discussion #22], GitHub, 2023 (Accessed: 2025-08-11)</ref> of CutefishOS, but it has not received major attention from the media. == CyberDE == [[File:VSCode In Cutefish.png|thumb|right|Visual Studio Code running on CutefishDE.<ref>[https://cutefishos.com CutefishOS], Cutefish Team, 2025 (Accessed: 2025-08-11)</ref>]] The desktop environment that came with CyberOS, usually referred to as ''Cyber'' or ''CyberDE'', was made using Qt5 and was commonly said to resemble the look and feel of Mac OS X.<ref>[https://wiki.archlinux.org/title/Cutefish Cutefish], ArchWiki (Accessed: 2025-08-11)</ref> <code>cyber-launcher</code> came with the dock at the bottom, which had a button that opens the launcher, and a status line bar with embedded global context menus at the top. Many parts of the interface were also partially transparent. Window controls were at the top right corner and resembles [[Microsoft Windows]], while titles were centred. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives] == References == fbfae8dfeb9a34760aed49cb836b0757efb59390 3802 3787 2025-08-21T18:07:40Z Madonuko 140 Undo revision [[Special:Diff/3785|3785]] by [[Special:Contributions/NachoLord117|NachoLord117]] ([[User talk:NachoLord117|talk]]) wikitext text/x-wiki [[category:Linux Distributions]] [[category:Desktop Environments]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued in around 2022 to 2023<ref>[https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2022 (Accessed: 2022-05-14)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the DE, and Arch Linux was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to Ubuntu. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were removed and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The new CutefishOS team, which was rebased to Sichuan, also did not live long, due to lack of Western support, and silently died out between mid-2021 and 2022. === CutefishOS Reborn === CutefishOS Reborn was a Western community's attempt to revive CutefishOS's development. It gauged some interest but very quickly died off in mid-2022. === LingmoOS === [https://github.com/LingmoOS/LingmoOS LingmoOS] is an active revival<ref>[https://github.com/orgs/cutefishos/discussions/22 Is this project dead or still in development? · cutefishos · Discussion #22], GitHub, 2023 (Accessed: 2025-08-11)</ref> of CutefishOS, but it has not received major attention from the media. == CyberDE == [[File:VSCode In Cutefish.png|thumb|right|Visual Studio Code running on CutefishDE.<ref>[https://cutefishos.com CutefishOS], Cutefish Team, 2025 (Accessed: 2025-08-11)</ref>]] The desktop environment that came with CyberOS, usually referred to as ''Cyber'' or ''CyberDE'', was made using Qt5 and was commonly said to resemble the look and feel of Mac OS X.<ref>[https://wiki.archlinux.org/title/Cutefish Cutefish], ArchWiki (Accessed: 2025-08-11)</ref> <code>cyber-launcher</code> came with the dock at the bottom, which had a button that opens the launcher, and a status line bar with embedded global context menus at the top. Many parts of the interface were also partially transparent. Window controls were at the top right corner and resembles [[Microsoft Windows]], while titles were centred. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives] == References == 6e0846453d973bcbc4e052f2ad27ef36f54fd9cb 3806 3802 2025-08-21T18:27:08Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[category:Linux Distributions]] [[category:Desktop Environments]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued in around 2022 to 2023<ref>[https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2022 (Accessed: 2022-05-14)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the DE, and Arch Linux was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to Ubuntu. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were removed and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The new CutefishOS team, which was rebased to Sichuan, also did not live long, due to lack of Western support, and silently died out between mid-2021 and 2022. === CutefishOS Reborn === CutefishOS Reborn was a Western community's attempt to revive CutefishOS's development. It gauged some interest but very quickly died off in mid-2022. === LingmoOS === [https://github.com/LingmoOS/LingmoOS LingmoOS] is an active revival<ref>[https://github.com/orgs/cutefishos/discussions/22 Is this project dead or still in development? · cutefishos · Discussion #22], GitHub, 2023 (Accessed: 2025-08-11)</ref> of CutefishOS, but it has not received major attention from the media. == CyberDE == [[File:VSCode In Cutefish.png|thumb|right|Visual Studio Code running on CutefishDE.<ref>[https://cutefishos.com CutefishOS], Cutefish Team, 2025 (Accessed: 2025-08-11)</ref>]] The desktop environment that came with CyberOS, usually referred to as ''Cyber'' or ''CyberDE'', was made using Qt5 and was commonly said to resemble the look and feel of Mac OS X.<ref>[https://wiki.archlinux.org/title/Cutefish Cutefish], ArchWiki (Accessed: 2025-08-11)</ref> <code>cyber-launcher</code> came with the dock at the bottom, which had a button that opens the launcher, and a status line bar with embedded global context menus at the top. Many parts of the interface were also partially transparent. Window controls were at the top right corner and resembles [[Microsoft Windows]], while titles were centred. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives] == References == 13b950747c50a3eb1aa28ded0da9f673e028cfd8 1 889 3788 2025-08-20T15:49:33Z Atmois 13 /* Test post */ new section wikitext text/x-wiki == Test post == https://iso.atl.dev/c/cyberos [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 15:49, 20 August 2025 (UTC) 1aaa79358f3ad05b89dedbaf21e0cba6e1905452 3789 3788 2025-08-20T15:50:29Z Test 63 /* Test post 2 */ new section wikitext text/x-wiki == Test post == https://iso.atl.dev/c/cyberos [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 15:49, 20 August 2025 (UTC) == Test post 2 == https://iso.atl.dev/c/cyberos [[User:Test|Test]] ([[User talk:Test|talk]]) 15:50, 20 August 2025 (UTC) 0b64b387939d3c66d8ecd6c80ed41c0fc4498d75 3790 3789 2025-08-20T15:51:42Z Test 63 /* Test post 3 */ new section wikitext text/x-wiki == Test post == https://iso.atl.dev/c/cyberos [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 15:49, 20 August 2025 (UTC) == Test post 2 == https://iso.atl.dev/c/cyberos [[User:Test|Test]] ([[User talk:Test|talk]]) 15:50, 20 August 2025 (UTC) == Test post 3 == The recent [https://atl.wiki/index.php?title=CyberOS&diff=prev&oldid=3785 edit] by [[User:NachoLord117]] was incorrect. It claimed that the distro was discontinued on 2021-06-23, but I'm quite literally holding the ISO image for 2021-08-06. All ''known'' versions of CyberOS has been uploaded by me to [https://iso.atl.dev/c/cyberos ATL ISO Archives], ''known'' as in known by me (former translator), and another person who was involved in hosting the ISOs. Also the edit broke the citation (see guidelines). [[User:Test|Test]] ([[User talk:Test|talk]]) 15:51, 20 August 2025 (UTC) b2bb8b2870817a908ce95625ee8fd618a7692401 3791 3790 2025-08-20T15:52:10Z Madonuko 140 /* Discontinue Date */ new section wikitext text/x-wiki == Test post == https://iso.atl.dev/c/cyberos [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 15:49, 20 August 2025 (UTC) == Test post 2 == https://iso.atl.dev/c/cyberos [[User:Test|Test]] ([[User talk:Test|talk]]) 15:50, 20 August 2025 (UTC) == Test post 3 == The recent [https://atl.wiki/index.php?title=CyberOS&diff=prev&oldid=3785 edit] by [[User:NachoLord117]] was incorrect. It claimed that the distro was discontinued on 2021-06-23, but I'm quite literally holding the ISO image for 2021-08-06. All ''known'' versions of CyberOS has been uploaded by me to [https://iso.atl.dev/c/cyberos ATL ISO Archives], ''known'' as in known by me (former translator), and another person who was involved in hosting the ISOs. Also the edit broke the citation (see guidelines). [[User:Test|Test]] ([[User talk:Test|talk]]) 15:51, 20 August 2025 (UTC) == Discontinue Date == The recent [https://atl.wiki/index.php?title=CyberOS&diff=prev&oldid=3785 edit] by [[User:NachoLord117]] was incorrect. It claimed that the distro was discontinued on 2021-06-23, but I'm quite literally holding the ISO image for 2021-08-06. All ''known'' versions of CyberOS has been uploaded by me to [https://iso.atl.dev/c/cyberos ATL ISO Archives], ''known'' as in known by me (former translator), and another person who was involved in hosting the ISOs. Also the edit broke the citation (see guidelines). — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 15:52, 20 August 2025 (UTC) 10d162d1ed3ec6110acd2f07a235403c44a77fce 3792 3791 2025-08-20T15:52:34Z Atmois 13 Remove test posts wikitext text/x-wiki == Discontinue Date == The recent [https://atl.wiki/index.php?title=CyberOS&diff=prev&oldid=3785 edit] by [[User:NachoLord117]] was incorrect. It claimed that the distro was discontinued on 2021-06-23, but I'm quite literally holding the ISO image for 2021-08-06. All ''known'' versions of CyberOS has been uploaded by me to [https://iso.atl.dev/c/cyberos ATL ISO Archives], ''known'' as in known by me (former translator), and another person who was involved in hosting the ISOs. Also the edit broke the citation (see guidelines). — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 15:52, 20 August 2025 (UTC) 364908c777d7d12dfbe0e72e7937d12c7cb655b4 6 890 3793 2025-08-20T19:09:54Z Satnus 215 A screenshot of lxqt I took from within a qemu VM. Its cropped so its not the best quality, but its good enough wikitext text/x-wiki == Summary == A screenshot of lxqt I took from within a qemu VM. Its cropped so its not the best quality, but its good enough == Licensing == {{PD}} 0d1919bfd125a776b97bd00bb61ab25eacab4588 0 622 3794 3749 2025-08-20T19:14:55Z Satnus 215 Added LXQt screenshot, reordered the table and screenshots to alphabetical order, added internal links for LXDE & Razor-qt in the LXQt description. wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment File:GNOME 43.png|GNOME File:lxqt-screenshot-about.png|link=LXQt|LXQt File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |- |} f0329102c986e92a3fe2fd63a6e7e4d329bf55f8 0 891 3795 2025-08-21T04:16:50Z Katamine 263 main desc. for steamOS wikitext text/x-wiki SteamOS is an Arch-based Linux Distribution produced by Valve for it's use on proprietary hardware such as the Steam Deck. SteamOS focuses mainly on the user gaming experience by offering easy-access to Steam services such as the game library and more. 8c9ac168fc498aea764763d1fb50ef7b29680c38 3796 3795 2025-08-21T04:25:05Z Katamine 263 Hyperlinks wikitext text/x-wiki SteamOS is an Immutable [[Arch Linux|Arch]]-based Linux Distribution produced by [[wikipedia:Valve_Corporation|Valve]] for it's use on proprietary hardware such as the [[wikipedia:Steam_Deck|Steam Deck.]] SteamOS focuses mainly on the user gaming experience by offering easy-access to Steam services such as the game library, Steam store and more. 587900f1d3a9b015413c36997f843a44dcabe605 6 892 3797 2025-08-21T09:17:32Z NoTag 251 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 893 3803 2025-08-21T18:11:16Z Madonuko 140 #REDIRECT [[APT]] wikitext text/x-wiki #REDIRECT [[APT]] 39727d1c16607535c5c5e4bcb8169f5490bf7012 0 894 3804 2025-08-21T18:11:35Z Madonuko 140 #REDIRECT [[Rpm]] wikitext text/x-wiki #REDIRECT [[Rpm]] 19ccc05d4274c55cbd9cb3a7296a84ef6aa31a7b 0 179 3805 3594 2025-08-21T18:26:29Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Guides]] {{Work In Progress}} Not every install will be as flawless as a user will expect it to be, and they may encounter bugs for numerous reasons ranging from simple hardware differences to nuanced kernel bugs. Here is a comprehensive list of some issues that commonly occur! * (Naming things from support channel!) == [[Linux on Apple Macintosh Devices|Linux on Apple Devices]] == If you use '''an Apple device,''' Linux may have a few issues running flawlessly on first install - '''this section details some steps you should consider taking if you have specific issues.''' == [[Artificial Intelligence on Linux]] == '''Covers w-okada, Stable Diffusion, Large Language Models, ROCm/CUDA with proper driver setup, anaconda/conda...''' dbaca275c0dd5d4f04237a321ec5afcb187da647 0 716 3807 3622 2025-08-21T18:27:42Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki A '''Hackintosh''' is a non‑Apple computer configured to run Apple's '''macOS''', using unofficial methods to bypass hardware restrictions. Apple's software license restricts macOS usage to Apple‑branded machines<ref>{{Cite|title=Hackintosh|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == History == === Origins === The concept surfaced as users attempted to run Mac OS on non‑Apple hardware. It gained real momentum after Apple transitioned to Intel CPUs, making macOS compatible with x86 architecture<ref>{{Cite|title=Intel Macs usher in Hackintosh era|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === PC Installations === Following the release of Intel-based Macs in 2006, community developers modified the macOS kernel to disable hardware checks and employed EFI emulation tools like FakeEFI to boot macOS on PCs<ref>{{Cite|title=Hackintosh bootloaders|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. === Bootloader Evolution === Bootloaders such as Chameleon and Clover evolved to improve reliability. In 2019, '''OpenCore''' was introduced, offering advanced features like support for macOS security features including System Integrity Protection and FileVault<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === Legal Developments === In 2008, Apple sued Psystar for selling unauthorized macOS clones. The court ruled Psystar violated Apple copyright and the DMCA, underscoring Apple's legal restrictions<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. == Technical and Legal Status == Apple's EULA prohibits running macOS on non‑Apple hardware<ref>{{Cite|title=Hackintosh licensing|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. The DMCA's anti‑circumvention provisions create legal uncertainty in the U.S.<ref>{{Cite|title=Psystar Lawsuit|url=https://en.wikipedia.org/wiki/Hackintosh|author=Wikipedia contributors|year=2025}}</ref>. Apple's transition to ARM-based silicon (beginning in 2020) reduces future feasibility for x86 Hackintoshes<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref>. == Hardware Compatibility == According to the '''Dortania OpenCore Install Guide''': CPUs: modern Intel (up to Comet Lake) and patched AMD Ryzen series GPUs: Intel integrated graphics (Ivy Bridge to Ice Lake), AMD GCN/Vega/Navi; NVIDIA support is limited Networking: Broadcom-based Wi‑Fi and Ethernet adapters are preferred<ref>{{Cite|title=OpenCore hardware limits|url=https://dortania.github.io/OpenCore-Install-Guide/macos-limits.html|author=Dortania contributors|year=2024}}</ref> == Installation Guide == This guide provides a high-level overview. For full instructions, consult the [[OpenCore Install Guide]]. === 1. Prepare hardware === Confirm that your CPU, GPU, and network adapters match published compatibility lists. === 2. Obtain macOS installer === On a real Mac, download the desired macOS version (such as Sonoma or Sequoia) from the App Store. === 3. Build a USB installer === Partition a USB drive as HFS+ or APFS and use '''OpenCore''' along with official tools to create a bootable installer<ref>{{Cite|title=OpenCore Install Guide|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 4. Configure BIOS/UEFI === Disable Secure Boot, VT-d, CSM, Fast Boot. Enable UEFI and XHCI handoff<ref>{{Cite|title=OpenCore BIOS settings|url=https://dortania.github.io/OpenCore-Install-Guide/|author=Dortania contributors|year=2024}}</ref>. === 5. Boot and install macOS === Boot from the USB installer, format the target storage as APFS, then proceed with the installation. === 6. Post-install configuration === Migrate the USB EFI folder to the internal EFI partition. Install necessary kexts (for audio, network), configure USB mapping, and finalize settings such as NVRAM, FileVault, and Sleep/Wake. == Resources == [https://dortania.github.io/OpenCore-Install-Guide/ Dortania OpenCore Install Guide] – full tutorial [https://en.wikipedia.org/wiki/Hackintosh Hackintosh – Wikipedia] [https://tonymacx86.com/ tonymacx86 forums] – hardware build guides and buyer lists == See also == [[macOS]] [[Virtualization]] [[BIOS]] == References == <references/> 87f491250929e8c0e5c3362421bd1330f0848693 0 718 3808 3735 2025-08-21T18:27:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[File:Apple-Logo-Transparent.png|thumb|right]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical operating systems developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a UNIX (Darwin/BSD) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> 8f6e4a74dcd15d05c4db75ecce3477101fcd6c0d 3847 3808 2025-08-24T09:51:17Z Imnotgoodatnames 121 changed displaytitle to "macOS" wikitext text/x-wiki {{DISPLAYTITLE:macOS}} [[File:Apple-Logo-Transparent.png|thumb|right]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical operating systems developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a UNIX (Darwin/BSD) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> fc93a0c6f2adfbf1b061cbf66181fcf4874823ce 0 855 3809 3705 2025-08-21T18:28:13Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} [[Category:Software]] [[File:Pulse Visualizer.png|thumb|alt=Pulse Visualizer in CRT mode|Pulse Visualizer in CRT mode|alt=Screenshot of Pulse Visualizer displaying CRT-style visual effects.]] '''Pulse Visualizer''' is a cross-platform real-time audio visualizer inspired by [https://minimeters.app/ MiniMeters] and written in [[C++]] and [[GLSL]]. It captures system audio via [[PipeWire]], [[PulseAudio]] or WASAPI, processes the signal through digital signal processing (DSP) stages using fftw<ref>https://fftw.org/<nowiki/>(Accessed: 2025-8-11)</ref>, libebur128<ref>https://github.com/jiixyj/libebur128<nowiki/>(Accessed: 2025-8-11)</ref> and other custom DSP methods, and renders visuals with hardware acceleration through [[OpenGL]] in an [[SDL3]] window.<ref>https://github.com/Beacroxx/pulse-visualizer Pulse Visualizer GitHub, 2025 (Accessed: 2025-08-11)</ref> == Features == Pulse Visualizer supports multiple real-time visualization modes, including stereometer, oscilloscope, spectrum analyzer, spectrogram, peak/LUFS meter, and VU meter. Users can customize the panels with features such as CRT screen emulation using GPU compute shaders, adjustable visual effects (blur, glow, chromatic aberration, vignette), and draggable, resizable panels. The application offers hot reloading of both configuration and theme files without restarting, and is compatible with Linux and BSD systems using PipeWire or PulseAudio for audio input.<ref>https://github.com/Beacroxx/pulse-visualizer/blob/main/CONFIGURATION.md<nowiki/>(Accessed: 2025-8-11)</ref> == References == <references /> __INDEX__ 8a85780f568703c7501e7f84b9546fd8dedad1af 0 887 3810 3780 2025-08-21T18:28:30Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{Stub}} {{Needs Citations}} '''Pulseaudio''', sometimes known as simply '''pulse''', is a [[SoundSever|Sound Server]] intended for GNU/Linux systems. It can serve as an intermediate programs between a sound-generating program (such as a music player), and outputs such as [[Bluez]], [[ALSA]], and the [[oss|Open Sound System]] (OSS). Being a Sound Server, Pulseaudio is capable of mixing multiple audio streams together in real-time. It can also load various plugins, which can enhance it's capabilities. Pulseaudio has been criticized for it's high latency, and is being deprecated in favor of [[Pipewire]]. ce189445b7946a1e6fb4a7f1aa13b9dde24e95f9 0 781 3811 3672 2025-08-21T18:29:01Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Package Managers]] '''RPM''' stands for '''Red Hat Package Manager'''. It is both a package format (`.rpm`) and the name of the package management system used primarily in Red Hat-based Linux distributions, including: * Red Hat Enterprise Linux (RHEL) * Fedora * CentOS * AlmaLinux * Rocky Linux * openSUSE (with some differences) == Overview == An RPM package is a file that contains: * Compiled software binaries * Configuration files * Metadata (name, version, dependencies, etc.) * Installation and removal scripts The standard file extension is `.rpm`. RPM packages are used to install, update, and remove software cleanly and consistently, while tracking file ownership and managing dependencies. == RPM vs DEB == RPM is used in Red Hat-based systems, while DEB is used in Debian-based systems (like Ubuntu). Both serve similar purposes but are not interchangeable. == Components of an RPM Package == * **Header**: Contains metadata (name, version, architecture, etc.) * **Payload**: The actual files to be installed * **Scripts**: Optional pre/post-install and removal scripts == Common Tools == * `rpm` — Low-level tool for querying, installing, and removing RPM packages * `dnf` or `yum` — High-level package managers that resolve dependencies and interact with repositories * `rpmbuild` — Tool for building RPM packages from SPEC files * `rpmlint` — Linter to check RPM quality and packaging errors == Basic Commands == === Installing an RPM file === <syntaxhighlight lang="bash"> sudo rpm -ivh package.rpm </syntaxhighlight> Or using DNF (which handles dependencies): <syntaxhighlight lang="bash"> sudo dnf install ./package.rpm </syntaxhighlight> === Query installed packages === <syntaxhighlight lang="bash"> rpm -q package-name </syntaxhighlight> === List all installed RPMs === <syntaxhighlight lang="bash"> rpm -qa </syntaxhighlight> === Remove a package === <syntaxhighlight lang="bash"> sudo rpm -e package-name </syntaxhighlight> === Verify a package === <syntaxhighlight lang="bash"> rpm -V package-name </syntaxhighlight> == Advantages == * Dependency tracking * Transaction-based installation/removal * Clean upgrade paths * Strong ecosystem support (DNF, YUM, repositories, etc.) == Limitations == * Requires careful dependency management * Not compatible with DEB systems * Binary format — not human-readable == External Resources == * [https://rpm.org/ Official RPM Site] * [https://fedoraproject.org/wiki/RPM Fedora RPM Guide] * [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Fedora Packaging Guidelines] == See Also == * [[YUM]] * [[DNF]] * [[rpmbuild]] 23ce990b0bfcb6522e15bb712ab999bb09904083 0 886 3812 3799 2025-08-21T18:29:17Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{Needs Citations|date=august 2025}} {{stub|date=august 2025}} The vi program is a full-screen console-based text editor. It was originally written in the 1970s by Bill Joy, as an enhancement for [[ex]], which in tern was an enhanced version of [[ed]]. As such, vi still has many ex-like features today. ==Using vi== To use vi, you can hit <code>i</code> or <code>a</code> (append) to enter "insert mode". You then may type what you wish, and hit the <code>esc</code> key to exit "insert mode". When you're no longer in "insert mode", you can hit the ":" (colon) command to type in ex-like commands. The two most common commands are <code>w [filename]</code> to save the file, and <code>q</code>, which is used to quit the program. These commands can be combined to quit and save in one step, like so: <code>wq</code>. To quit without saving, enter <code>q!</code>. When not in insert mode, you may use the <code>h</code> key to move back one column, <code>j</code> to move the cursor down one line, <code>k</code> to move up a line, and the <code>l</code> to move forward one column. Please note that these letters are lowercase. As is often the case with Unix programs, capitalization matters. Also, when in insert mode, you <i>might</i> be able to use your arrow keys, although this seems to depend on which implementation of vi you are using. It is generally recommended to learn the above keys instead. ==Implementations== Modern implementations of vi consist of [[vim]], [[neovim]], [[elvis]], [[nvi]], and the a version of vi built in to [[busybox]], the latter of which can be called via <code>busybox vi</code>. nvi/nex is a replacement for vi/ex and was originally developed as part of 4BSD.<ref>https://man.openbsd.org/vi.1</ref> 266c3acb45e68fc5deba2d8c8ddb268879c03dfc 0 279 3813 3653 2025-08-21T18:42:11Z Ilija.culap 258 wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, ppc64, x86_64 | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == This distribution stands out by having two primary variations of the distribution: * '''OpenSUSE Tumbleweed''' is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. * '''OpenSUSE Leap''' is the point release version, with a new release every year with older and more stable packages meant for business use. === openSUSE Slowroll === Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === openSUSE MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. 952cfdac73ffd8a58809435eac6ff4ae9ca432a5 3000 878 3814 3748 2025-08-21T18:48:05Z Ilija.culap 258 Added link to openSUSE Wiki page, removed one empty line wikitext text/x-wiki {{Guide_Warning}} In this guide you will learn how to install PiHole on your [[OpenSUSE|openSUSE MicroOS]]. MicroOS is very lightweight operating system designed for containerized and virtualized workloads. It also supports automatic updates and self-maintenance. There is also a SELinux (Security Extension) enabled and configured by default. Our container is going to run as root user (rootfull). For deployment we are going to to use quadlet files. Those are special files that are going to be handled by systemd, so we can then use systemd commands to start, stop and restart our PiHole service. '''Requirements and prerequisites:''' * Installed openSUSE MicroOS with container support * Basic command-line knowledge Start with creating a folder to hold all your PiHole configuration and 2 subfolders as shown below. MicroOS is immutable and you can’t put files wherever you want. You should use /var or /root folders on your filesystem. I’m going to use /var directory. mkdir /var/pihole mkdir /var/pihole/etc-pihole mkdir /var/pihole/etc-dnsmasq.d Next step is to create .container file in /etc/containers/systemd/ (You can actually skip this step, because your text editor is going to create this file for you in the next step). touch /etc/containers/systemd/pihole.container and then edit it: vim /etc/containers/systemd/pihole.container I’m using vim text editor, but feel free to use whatever editor you like (for example nano). In this file put following content and change your time zone and password: [Unit] Description=PiHole Container StartLimitIntervalSec=0 [Container] Image=docker.io/pihole/pihole:latest Volume=/var/pihole/etc-pihole:/etc/pihole:Z Volume=/var/pihole/etc-dnsmasq.d:/etc/dnsmasq.d:Z AutoUpdate=registry Environment="TZ=Europe/Berlin" Environment="FTLCONF_webserver_api_password=changeme" PublishPort=53:53/tcp PublishPort=53:53/udp PublishPort=5555:80/tcp [Service] Restart=always RestartSec=1m [Install] WantedBy=default.target Next step is to reload systemd so it can load all new and changed files (your .container file): systemctl daemon-reload and start your pihole service (in this command pihole is the name of .container file. Adjust your command accordingly!): systemctl start pihole And that’s it. Your PiHole service is now running. You can check if everything is okay with: podman stats To exit press CTRL + C. To access your WEB Interface go to: http://<Server-IP>:5555/admin/ 1c7991b8da9b01d101580d1124054864d0767eac 0 219 3815 3633 2025-08-21T18:49:23Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan.<ref>https://community.kde.org/Promo/Material/Mascots Official KDE Wiki, 2025 (Imported 6th June 2024)</ref> Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror]{{Dead Link|2025-08-22|timeout (10)}}, KDE's default web browser.<ref>https://community.kde.org/Konqi Official KDE Wiki, 2025 (Imported 6th June 2024)</ref> == References == <references /> 008838944704f3229bdc1ae84cf749b3d75969b8 0 626 3816 3736 2025-08-21T18:50:55Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>[https://manjaro.org/ Manjaro – The Linux for People and Organizations], Manjaro, 2025-08-09 (Accessed: 2025-08-09)</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">[https://distrowatch.com/table.php?distribution=manjaro DistroWatch.com: Manjaro Linux], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" [[Rolling Release]] * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>[https://wiki.manjaro.org/index.php/Pamac Pamac - Manjaro], Manjaro, 2023-03-09 (Accessed: 2025-08-09)</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>[https://en.wikipedia.org/wiki/Manjaro Manjaro], Wikipedia contributors, 2025-07-01 (Accessed: 2025-08-09)</ref><ref>[https://www.ubuntumint.com/manjaro-linux-history/ The History of Manjaro Linux Distribution], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>[https://www.geeksforgeeks.org/how-to-install-manjaro-linux/ How to Install Manjaro Linux?], GeeksforGeeks, 2023-12-22 (Accessed: 2025-08-09)</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch's base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch's, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>[https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/ How to Enable Arch User Repository (AUR) in Manjaro Linux], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro's custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch's upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>[https://itsfoss.com/manjaro-vs-arch-linux/ Manjaro vs Arch: What's the Difference? Which one to Use?], Dimitrios, Abhishek Prakash, 2023-09-13 (Accessed: 2025-08-09)</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>[https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. == References == 053efd1dfc0b58e1ced4895cb4ea56944eafb5ca 0 297 3817 3645 2025-08-21T18:52:58Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Terminology]] '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)."</ref> The core concept of multi-booting revolves around partitioning a computer's [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system's configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader]{{Dead Link|2025-08-22|timeout (10)}}, Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. it provides however the booted OS with full access to the machine's components, rather than needing to go through translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straightforward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Riot's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == References == <references /> 804b8e7bc3935867e24ea4536f86deb0bed6bef0 0 176 3818 3740 2025-08-21T18:55:21Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop]{{Dead Link|2025-08-14|404}} }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover]{{Dead Link|2025-08-22|timeout (10)}}, Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2025-08-14|503}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2025-08-14|503}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate]{{Dead Link|2025-08-22|timeout (10)}} - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> 07b9918daa21f972c516b112e59290e5c33a0809 0 895 3819 2025-08-21T19:00:14Z Ilija.culap 258 Started new page for pihole wikitext text/x-wiki Pi-hole is network-wide ad-blocking software, that you can run on your own device. Project website: https://github.com/pi-hole 83e94c8396869f8d40a5dbaf36ed323637a780cf 0 586 3820 3693 2025-08-21T19:00:56Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox | title = Xenia (Linux Fox) | image = [[File:Xenia the Linux Fox.gif]] | caption = The original design of Linux Fox, created by Al Mackey in 1996 }} Xenia was a candidate logo and [[:Category:Mascots|mascot]] for the [[Linux]] project. She was a competitor to [[Tux]], who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds)<ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ Why the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!]{{Dead Link|2025-08-22|429}}, Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson.<ref>[https://archive.is/wYsFh Penguins and Other Things]{{Dead Link|2025-08-22|429}}, Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurned many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on [[Gentoo]].<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> == References == <references /> f86a2e8648bd3f2093cfc662a7933cc54e461801 3000 577 3821 3483 2025-08-21T19:05:38Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL]{{Dead Link|2025-08-22|timeout (10)}} its Savannah repository. == References == d58f6043d153f71e9c17110fef67e0d57257b06f 3823 3821 2025-08-21T19:08:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL]{{Dead Link|2025-08-22|timeout (10)}} its Savannah repository. == References == 99b4aea18060640cb66b678932331f74fd448dba 3000 471 3822 2473 2025-08-21T19:08:42Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Guide Warning}} The best SSH practices can be summarized into two main principles: # Keeping unauthorized users out of your system. # Making sure potential attackers don't even know your system exists. This guide will teach you the best SSH security practices. === SSH Programs: Dropbear vs OpenSSH === There are two primary SSH programs used on [[Linux Distributions|Linux]]/[[Unix|Unix-based]] systems: '''Dropbear''' and '''OpenSSH'''. In this guide, we will focus on '''OpenSSH'''. === Installing SSH === Installing SSH varies by system. Below are common [[Package Manager|package managers]] where you can download SSH: '''[[Debian]]/[[Ubuntu]]-based systems:'''<syntaxhighlight lang="bash"> sudo apt install openssh-server </syntaxhighlight> [[Red Hat Enterprise Linux|Red Hat]]/[[CentOS]]/[[Fedora]]-based systems: <syntaxhighlight>sudo dnf install openssh-server</syntaxhighlight> [[Arch Linux]]-based systems: <syntaxhighlight>sudo pacman -S openssh</syntaxhighlight> [[OpenSUSE]]-based systems: <syntaxhighlight>sudo zypper install openssh</syntaxhighlight> [[macOS]] (via [[Homebrew]]): <syntaxhighlight>brew install openssh</syntaxhighlight> == Securing the OpenSSH Server == === Changing the Port === By default, SSH runs on '''port 22'''. While leaving it on port 22 is acceptable, your system will be easily detected by port scanners as running SSH. To mitigate this, you can change the port. The SSH configuration file is typically located at '''/etc/ssh/sshd_config''' and is usually owned by the root user. To edit it, you must open it as root, using either '''sudo''' or '''doas'''. Once you open the '''sshd_config''' file, you should see the following line: <syntaxhighlight>#Port 22</syntaxhighlight> To modify the port, uncomment the line by removing the `#` at the beginning and then change the '''22''' to any number between '''100''' and '''65534'''. You will need to uncomment any line you change for it to come into effect. For example: <syntaxhighlight>Port 2345</syntaxhighlight> Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> Once the change is made, you have successfully modified the port. To log in using the new port, use the following command: <syntaxhighlight><username>@<address> -p 2345</syntaxhighlight> === Key Authentication === Key-based authentication is a much safer alternative to using a password. Instead of entering a password to log in, you'll use a key pair: a '''private key''' that stays on your system and a '''public key''' that you store on the server. ==== How Key Authentication Works ==== Imagine you have a door with a lock. The private key is like your physical key, while the public key is the lock on the door. When the correct key is inserted, the door unlocks. This is essentially how key authentication works. * Prevents brute-force attacks. * Allows passwordless login (like Single Sign-On). * Requires each user to have a unique key pair. === Setting up Key Authentication === ==== Generating the Key Files ==== 1. On any Unix/Linux system, type the following command: <syntaxhighlight>ssh-keygen</syntaxhighlight> 2. You will be prompted to specify where to save the key files: <syntaxhighlight> Generating public/private ed25519 key pair. Enter file in which to save the key (/home/name/.ssh/id_ed25519): </syntaxhighlight> '''Example:''' <syntaxhighlight> Enter file in which to save the key (/home/name/.ssh/id_ed25519): /home/name/Desktop/key </syntaxhighlight> This will save both the public and private key files on your desktop under the name '''key'''. 3. You will be asked to set a passphrase for the key. If you trust the environment where the key is stored, you can leave it empty by pressing '''Enter'''. Alternatively, you can set a passphrase to add an extra layer of security. <syntaxhighlight> Enter passphrase for "/home/name/Desktop/key" (empty for no passphrase): </syntaxhighlight> 4. Once complete, the keys will be saved in the specified location: <syntaxhighlight> Your identification has been saved in /home/name/Desktop/key Your public key has been saved in /home/name/Desktop/key.pub The key fingerprint is: SHA256:I60X50p2/VwZ6MHhEqx8rWNse0pC5/vewW1i4tLufQ8 name@pc The key's randomart image is: +--[ED25519 256]--+ | | | . | | o . | | .. . = o | | . S+.+ * . | | o.==.+ o +| | . +.oXo.E++| | + o*.=B.=o| | . BOo+oo| +----[SHA256]-----+ </syntaxhighlight> Do not worry about the '''randomart''' as it has no functional purpose. 5. You now have two files: * key – This is your '''private key''' (keep this secure and never share it). * key.pub – This is your '''public key''' (place this on the server). The private key should stay on the machine you will use to access the server. ==== Securing the Server with Key Authentication ==== 1. Log in to the server you want to protect with key authentication. 2. Open the SSH configuration file: <syntaxhighlight> sudo nano /etc/ssh/sshd_config </syntaxhighlight> 3. Modify the following lines: <syntaxhighlight> #PermitRootLogin prohibit-password #PasswordAuthentication yes </syntaxhighlight> to: <syntaxhighlight> PermitRootLogin no PasswordAuthentication no </syntaxhighlight> This prevents root login over SSH, disables password login and forces key-based authentication. 4. Save and exit the file. 5. Go to the home directory of the user you wish to secure with key authentication. Create the '''.ssh''' directory (if it doesn't exist), then create the '''authorized_keys''' file inside it: <syntaxhighlight> mkdir -p ~/.ssh nano ~/.ssh/authorized_keys </syntaxhighlight> Paste the entire contents of the `.pub` file into this document and save it. 6. Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> '''DO NOT LOG OUT UNTIL YOU CONFRIM THE CONFIGURATION IS CORRECT TO AVOID BEING LOCKED OUT.''' 7. Open another [[TUI|terminal]] window on the machine you will use to SSH into the server and test the connection: <syntaxhighlight> ssh <user>@<address> -i /location/to/private/key/file </syntaxhighlight> If you can log in without a password, the key authentication system is correctly configured! 6fd818ddb6d843697f72ad904d51d849ed02f0cb 3000 608 3824 3014 2025-08-21T19:09:21Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{GuideWarning}} Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">[https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims Localization, Internationalization and Multilingualization], Ultramarine Linux, 2024 (Accessed: 2025-05-03)</ref> Users can use the IMF to switch between different IMEs.<ref>[https://wiki.archlinux.org/title/Input_method Input method], ArchWiki, 2020 (Accessed: 2025-05-03)</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>[[wikipedia:Intelligent_Input_Bus|Intelligent_Input_Bus]], Wikipedia, 2009 (Accessed: 2025-05-03)</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>[[wikipedia:Fcitx|Fcitx]], Wikipedia, 2010 (Accessed: 2025-05-03)</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code><ref name=":0" group="Note">Additionally requires <code>fcitx5-chinese-addon</code> on Fedora due to packaging issues.</ref> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code><ref name=":0" group="Note" />? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code><ref group="Note"><code>fcitx5-mozc-ut</code>^AUR is instead recommended on Arch Linux.</ref> |<code>fcitx-mozc</code><ref group="Note"><code>fcitx-mozc-ut</code>^AUR is instead recommended on Arch.</ref> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |ViQR |<code>fcitx5-m17n</code><ref name=":1" group="Note">This is <code>fcitx5-table-viqr</code>, <code>fcitx-table-viqr</code>, <code>ibus-table-viqr</code> on Debian.</ref> |<code>fcitx-m17n</code><ref name=":1" group="Note" /> |<code>ibus-table-tv</code><ref name=":1" group="Note" /> |<code>uim-viqr</code> | - | - | - | - | - |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<code>uim-m17n</code><ref name=":2" group="Note">On some distros, this is <code>uim-m17nlib</code>.</ref> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code><ref group="Note">Requires the [[Terra]] repository on Fedora.</ref> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code><ref group="Note"><code>ibus-openbangla</code> on Fedora with the [[Terra]] repository.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<code>fcitx5-varnam</code> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Others |- |Thai |<code>fcitx5-libthai</code> | - |<code>ibus-table-tv</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> | - |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Math Symbols |[[Compose Key]]? |[[Compose Key]]? |<code>ibus-table-mathwriter</code> | - | - | - | - | - | - |- |Completion |''built-in'' | - |<code>ibus-typing-booster</code> | - | - | - | - | - | - |- |''"Everything Else"'' |<code>fcitx5-m17n</code>? |<code>fcitx-m17n</code>? |<code>ibus-m17n</code>? |<code>uim-m17n</code><ref name=":2" group="Note" />? | - |<code>scim-m17n</code>? | - | - | - |} === Notes === <references group=Note/> This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. == How to choose your IME == This section represents the general case and the authors' opinions. It is not necessary to follow them. {| class="wikitable" |+Chinese !Situation !IME !Rime IME !Notes |- |Already using [[Rime]] | rowspan="3" |Rime | - | rowspan="3" |Rime is very powerful, but it comes with the cost of writing your own configuration files and [https://github.com/rime/home/wiki reading Chinese documentations], and thus is not recommended to beginners. |- |Prefer a highly customizable experience | - |- |Good at writing configuration files | - |- |Know Pinyin |Pinyin |''built-in'' | |- |Know Zhuyin |Chewing |℞ bopomofo |<code>libzhuyin</code> is not recommended (very unpopular), avoid <code>fcitx5-zhuyin</code> & <code>ibus-libzhuyin</code>. |- |Know Cangjie 3 / Quick 3 | rowspan="2" |Cangjie/Quick | rowspan="2" |℞ cangjie |Rime with [https://github.com/kennethso168/rime-cangjie3-extension rime-cangjie3-extension] |- |Know Cangjie 5 / Quick 5 | |- |Know SmartCangjie 6 |SCJ |℞ scj | |- |Know Jyutping |Rime |℞ cantonese |Jyutping from table-extras is barely usable |- |Know Wubi |Haifeng Wubi | |https://www.zhukun.net/archives/4856 |} {| class="wikitable" |+Japanese !Situation !IME !Notes |- |You hate Qt |Anthy |Anthy is unmaintained but it's written in GTK, so if you want your IME to fit into your GTK theme, use Anthy. |- |Otherwise |Mozc |Mozc is maintained by Google and has better suggestions, but you should also consider using the UT dictionaries. |} == References == 1e5df8ded1d7014d8f92f3eebffb97b57b5d2d93 3000 706 3825 2645 2025-08-21T19:09:32Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki == Arch-based systems == To install the '''budgie''' package group, which includes first-party applications such as a screensaver, execute <code>sudo pacman -S budgie</code>. Alternatively, <code>sudo pacman -S budgie-desktop</code> will install the standalone desktop. Recommended optional packages include the Arc GTK theme, the Papirus icon theme, and the Network Manager applet. Executing <code>sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet</code> will install them. == Fedora Linux == [[Fedora]] has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. == Ubuntu == There is a [https://ubuntubudgie.org/ community ISO] that contains [[Ubuntu]] with Budgie Desktop instead of GNOME. == Void Linux == <code>sudo xbps-install budgie-desktop</code> == OpenSUSE == Budgie can be selected during the OpenSUSE installation or installed afterward using <code>sudo zypper install budgie-desktop</code>. 8b8745b10aaec805b0e660f1ff695739b68e46a9 3000 697 3826 2606 2025-08-21T19:09:53Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki Window Maker can be installed from most [[Package Manager|package managers]]. On [[Debian]] and Debian-based distributions:<syntaxhighlight lang="bash"> sudo apt install wmaker </syntaxhighlight>On [[Arch Linux|Arch]] and Arch-based distributions, Window Maker can be only only installed with an AUR helper such as [[yay]]:<syntaxhighlight lang="bash"> yay -S windowmaker </syntaxhighlight>On [[Gentoo]] and Gentoo-based distributions:<syntaxhighlight lang="bash"> sudo emerge -av x11-wm/windowmaker </syntaxhighlight>On [[RHEL]], [[Fedora]] and Fedora-based distributions:<syntaxhighlight lang="bash"> sudo dnf install WindowMaker </syntaxhighlight>On [[Void Linux]]:<syntaxhighlight lang="bash"> sudo xbps-install windowmaker </syntaxhighlight>If none of these work or the version is outdated, you may try to install it manually (0.96.0) by running:<syntaxhighlight lang="bash" line="1"> wget https://www.windowmaker.org/pub/source/release/WindowMaker-0.96.0.tar.gz tar xvf WindowMaker-0.96.0.tar.gz cd WindowMaker-0.96.0.tar.gz ./configure --prefix=/usr make sudo make install </syntaxhighlight> 2126167552e549f361b0867cddf0882c0212bca8 3000 695 3827 3729 2025-08-21T19:10:04Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki ==== On [[Debian]] and Debian-based distributions: ==== You can sometimes install using a software manager, such as [[synaptic]].<syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> ==== On [[OpenSUSE]] Tumbleweed or Leap: ==== <syntaxhighlight lang="bash"> $ sudo zypper in i3 </syntaxhighlight> ==== On [[NixOS]] and NixOS-based distributions ==== <syntaxhighlight lang="nixos"> services.xserver.windowManagers.i3.enable = true; </syntaxhighlight> == <u>See Also</u> == [[I3]] c6a1a40e923f439b165119f5f28f58fb4070fb8a 3000 634 3828 2309 2025-08-21T19:10:30Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{GuideWarning}} Ventoy is an open source tool commonly used to create bootable USB drives for various linux installations. The main benefits to this tool is that it allows you to store multiple bootable ISO files on one USB drive. == Download and installation == 1. The Ventoy application can be found at https://www.ventoy.net/en/index.html<br> 2. Extract the downloaded zip file<br> 3. Insert your USB drive<br> 4. Inside the Ventoy folder, run the Ventoy2Disk.exe file<br> 5. Now inside the application, select your desired USB drive<br> 6. Press the Install button<br> '''Warning''': Creating a bootable USB drive will delete all data stored on said USB. Backup your data and use with caution. After installing Ventoy you can copy a linux ISO file onto the USB drive, thus creating a bootable USB drive. After installation you may need to disable secure boot, depending on your chosen Linux distribution. Once the USB drive is made bootable, you can proceed to the next step, which is booting from USB though the BIOS menu. == Booting from USB though the BIOS menu == 1. Restart your computer<br> 2. Access the BIOS menu, typically by pressing ESC, Delete, or one of the 12 function keys (F1, F2, F3...)<br> 3. Enter the boot menu (Usually the key to enter the boot menu will be specified near the bottom of the screen)<br> 4. From the boot menu, select the USB drive<br> 5. If you have multiple ISO files on the same USB device, you will need to select which one you would like to boot into<br> 6. Selecting "boot in normal mode" will boot into the live environment, allowing you to try out, or install your Linux distribution<br> If you wish to install Linux, most distributions, such as Linux Mint, will have an application with a graphical interface to assist you in this process. == Alternatives to Ventoy == If Ventoy fails to create a bootable USB drive, or for any other reason, there are other tools available, such as:<br> - Rufus (Windows only)<br> - balenaEtcher<br> - Fedora Media Writer<br> 86ba9eb1dbf02481649fc3227ce56cbf84cf4073 3000 696 3829 2604 2025-08-21T19:11:38Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki == Using Cinnamon == * Open Start Menu in bottom right corner * Log Out * Click on [[Cinnamon]] Logo next to log In details * Switch to desired [[Window Manager]] == Using i3 == <syntaxhighlight> Mod+shift+e </syntaxhighlight> * Confirm that you want to log out in pop-up * Click on [[i3]] logo next to Log In details * Switch to desired Window Manager == Using XFCE == * Open Start Menu in Top Left corner * Log Out * Click on [[XFCE]] Logo next to log In details * Switch to desired Window Manager == Using MATE == * Open Start Menu in bottom right corner * Log Out * Click on [[MATE]] Logo next to log In details * Switch to desired Window Manager e3862aa82090859358be030c05bd217ede907abe 3000 705 3830 2643 2025-08-21T19:12:02Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki strace is a command-line tool that lets you see the system calls a program makes while it runs. It’s great for debugging, understanding program behavior, or learning how system calls work. == How to use strace == Steps to Use strace: 1. '''Run a Command with strace''':<syntaxhighlight lang="bash">strace <command></syntaxhighlight>This will show all the system calls made by the command. 2. '''Attach to a Running Process''': If a program is already running, use its process ID (PID):<syntaxhighlight lang="bash">strace -p <PID></syntaxhighlight>3. '''Filter Specific System Calls''': To narrow down the output, trace specific system calls using the -e option:<syntaxhighlight lang="bash">strace -e <syscall> <command></syntaxhighlight>4. '''Save Output to a File''': Use -o to redirect the output to a file for easier analysis:<syntaxhighlight lang="bash">strace -o trace_output.txt <command></syntaxhighlight>5. '''Trace Execution Times''': To see how long each system call takes, use:<syntaxhighlight lang="bash">strace -T <command></syntaxhighlight> 86c9a65bf4fe86c15ee110e629efaaa20f5ab3bd 3 896 3831 2025-08-21T21:52:16Z Ow0cast 249 /* trout! */ new section wikitext text/x-wiki == trout! == {{User:Ow0cast/trout}} <code>[[User:Ow0cast|/etc/owuh]] $ ([[User talk:Ow0cast|💬]] &#124; she/her)</code> 21:52, 21 August 2025 (UTC) ff74a4270c41e0a228e35c44867492e5190fea60 3832 3831 2025-08-21T22:46:47Z Ow0cast 249 /* trout! */ wikitext text/x-wiki == trout! == {{User:Ow0cast/trout}} <code>[[User:Ow0cast|/etc/owuh]] $ ([[User talk:Ow0cast|💬]] &#124; she/her)</code> 21:52, 21 August 2025 (UTC) {{User:Ow0cast/trout}} <code>[[User:Ow0cast|/etc/owuh]] $ ([[User talk:Ow0cast|💬]] &#124; she/her)</code> 22:46, 21 August 2025 (UTC) a71a5bde42426e9b2d743973f177f9c073eca6b6 0 884 3833 3798 2025-08-21T23:19:38Z 0Stormy 158 Added info on default window manager wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The most recommended method for installing LXQt is to either install a distribution which comes with LXQt by default, eg. [[Lubuntu]], or which offers it as a desktop environment option while installing the distribution, e.g. [[Debian]]. Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This will usually also pull all necessary dependencies for it. The way to install depends highly on the distribution. It is recommended to look at either distribution documentation or distribution specific guides to install LXQt. '''This is only for users whose systems have no desktop environment installed. It is not recommended to have two or more desktop environments on the same system''' After installation, it is highly recommended to also install [[SDDM]], LXQt's preferred display manager, to be able to start LXQt smoothly. == References == 8e11a177cb4d443a5a9727868832d0175966b2a3 3843 3833 2025-08-22T19:01:36Z Satnus 215 Incomplete edit on installation section. wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>https://lubuntu.me/ Lubuntu, Accessed: 2025-08-22</ref> * [[Fedora]] LXQt spin<ref>https://fedoraproject.org/spins/lxqt Fedora, Accessed 2025-08-22</ref> * [[CachyOS]]: available in installer<ref>https://wiki.cachyos.org/installation/desktop_environments/ CachyOS, Accessed:2025-08-22</ref> * [[SparkyLinux]]<ref>https://wiki.sparkylinux.org/doku.php/about Sparky Linux, Accessed:2025-08-22</ref> * [[Debian]]: available in installer<ref>https://wiki.debian.org/LXQt Debian Wiki, Accessed:2025-08-22</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This will usually also pull all necessary dependencies for it. Most distributions will have default metapackage or group which can be used to install LXQt. '''This is only for users whose systems have no desktop environment installed. It is not recommended to have two or more desktop environments on the same system''' After installation, it is highly recommended to also install [[SDDM]], LXQt's preferred display manager, to be able to start LXQt smoothly. == References == e6682b71641591795819ba2e5557a02f66b4bddd 3845 3843 2025-08-23T16:56:00Z Satnus 215 Improved installation section. wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>https://lubuntu.me/ Lubuntu, Accessed: 2025-08-22</ref> * [[Fedora]] LXQt spin<ref>https://fedoraproject.org/spins/lxqt Fedora, Accessed 2025-08-22</ref> * [[CachyOS]]: available in installer<ref>https://wiki.cachyos.org/installation/desktop_environments/ CachyOS, Accessed:2025-08-22</ref> * [[SparkyLinux]]<ref>https://wiki.sparkylinux.org/doku.php/about Sparky Linux, Accessed:2025-08-22</ref> * [[Debian]]: available in installer<ref>https://wiki.debian.org/LXQt Debian Wiki, Accessed:2025-08-22</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>https://packages.debian.org/stable/lxqt-core Debian, Accessed 2025-08-23</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>https://packages.debian.org/trixie/lxqt Debian, Accessed:2025-08-23</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggested: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>https://packages.debian.org/stable/task-lxqt-desktop Debian, Accessed:2025-08-23</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>https://archlinux.org/groups/x86_64/lxqt/ Arch Linux, Accessed:2025-08-23</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template Github, Accessed:2025-08-23</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers LXQt wiki, Accessed:2025-08-23</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions LXQt wiki, Accessed:2025-08-23</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight>exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == ea0c908d7c9de94b6d2a28279429e51d6468493c 3846 3845 2025-08-23T17:00:03Z Satnus 215 Fix errors with newlines wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>https://lubuntu.me/ Lubuntu, Accessed: 2025-08-22</ref> * [[Fedora]] LXQt spin<ref>https://fedoraproject.org/spins/lxqt Fedora, Accessed 2025-08-22</ref> * [[CachyOS]]: available in installer<ref>https://wiki.cachyos.org/installation/desktop_environments/ CachyOS, Accessed:2025-08-22</ref> * [[SparkyLinux]]<ref>https://wiki.sparkylinux.org/doku.php/about Sparky Linux, Accessed:2025-08-22</ref> * [[Debian]]: available in installer<ref>https://wiki.debian.org/LXQt Debian Wiki, Accessed:2025-08-22</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>https://packages.debian.org/stable/lxqt-core Debian, Accessed 2025-08-23</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>https://packages.debian.org/trixie/lxqt Debian, Accessed:2025-08-23</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>https://packages.debian.org/stable/task-lxqt-desktop Debian, Accessed:2025-08-23</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>https://archlinux.org/groups/x86_64/lxqt/ Arch Linux, Accessed:2025-08-23</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template Github, Accessed:2025-08-23</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers LXQt wiki, Accessed:2025-08-23</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions LXQt wiki, Accessed:2025-08-23</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight>exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == 5d60781a52fc3e8d0d4f1fffc647762c3310ca3a 3849 3846 2025-08-24T19:53:53Z Satnus 215 Fixed syntaxhighlight error wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>https://lubuntu.me/ Lubuntu, Accessed: 2025-08-22</ref> * [[Fedora]] LXQt spin<ref>https://fedoraproject.org/spins/lxqt Fedora, Accessed 2025-08-22</ref> * [[CachyOS]]: available in installer<ref>https://wiki.cachyos.org/installation/desktop_environments/ CachyOS, Accessed:2025-08-22</ref> * [[SparkyLinux]]<ref>https://wiki.sparkylinux.org/doku.php/about Sparky Linux, Accessed:2025-08-22</ref> * [[Debian]]: available in installer<ref>https://wiki.debian.org/LXQt Debian Wiki, Accessed:2025-08-22</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>https://packages.debian.org/stable/lxqt-core Debian, Accessed 2025-08-23</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>https://packages.debian.org/trixie/lxqt Debian, Accessed:2025-08-23</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>https://packages.debian.org/stable/task-lxqt-desktop Debian, Accessed:2025-08-23</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>https://archlinux.org/groups/x86_64/lxqt/ Arch Linux, Accessed:2025-08-23</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template Github, Accessed:2025-08-23</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers LXQt wiki, Accessed:2025-08-23</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions LXQt wiki, Accessed:2025-08-23</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight lang="text">exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == 373bd0602ce360cb230ff8b5353d07c4040dcf51 2 897 3834 2025-08-22T03:02:33Z Ow0cast 249 Created page with "account for testing things as an unprivileged user yes this account belongs to me ~~~~" wikitext text/x-wiki account for testing things as an unprivileged user yes this account belongs to me <code>[[User:Ow0cast|/etc/owuh]] $ ([[User talk:Ow0cast|💬]] &#124; she/her)</code> 03:02, 22 August 2025 (UTC) b0cbafdb4f616959ebaa7a6ee903e7530c657e06 1 898 3835 2025-08-22T03:04:31Z Ow0castTesting 264 /* testing */ new section wikitext text/x-wiki == testing == a [[User:Ow0castTesting|Ow0castTesting]] ([[User talk:Ow0castTesting|talk]]) 03:04, 22 August 2025 (UTC) cf9c3c61418cdcbdd3a4a227f078c832a2ad150b 0 899 3836 2025-08-22T03:07:39Z Ow0castTesting 264 test page numero dos wikitext text/x-wiki hello this is second test page 7b26abec8946e323437312e10be3e38885c02be8 3 900 3837 2025-08-22T03:09:48Z Ow0castTesting 264 testy mc test wikitext text/x-wiki testing testing one two three 277048d8f75775c3c784463613b565418b59d021 6 901 3838 2025-08-22T13:29:23Z Imnotgoodatnames 121 Midnight Commander screenshot wikitext text/x-wiki == Summary == Midnight Commander screenshot 5b67930f48982f77fe643f534c0bb32b7fb0b561 0 902 3839 2025-08-22T14:24:08Z Imnotgoodatnames 121 Created page with "[[Category:Software]] {{SoftwareInfobox | image = [[File:Mc.png|frameless]] | caption = Midnight Commander in action | title = Midnight Commander | releasestatus = Maintained | lastrelease = 4.8.33 | languages = [[C]] | developers = Miguel de Icaza, GNU Project, et al. | website = https://midnight-commander.org/ }} '''GNU Midnight Commander''' (<code>mc</code>) is a dual-pane [[TUI]] file manager. It also includes an internal file viewer (<code>mcview</code>), editor (<c..." wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Mc.png|frameless]] | caption = Midnight Commander in action | title = Midnight Commander | releasestatus = Maintained | lastrelease = 4.8.33 | languages = [[C]] | developers = Miguel de Icaza, GNU Project, et al. | website = https://midnight-commander.org/ }} '''GNU Midnight Commander''' (<code>mc</code>) is a dual-pane [[TUI]] file manager. It also includes an internal file viewer (<code>mcview</code>), editor (<code>mcedit</code>), and diff viewer (<code>mcdiff</code>). == Overview == The screen of Midnight Commander is divided into four parts, with most of it being taken up by the two directory panels. On the bottom are the function key labels and above it is the shell command line. On the top is the drop down menu accessible with <code>f9</code>. 1a7573c087bfda1345718aabd8de2372b0b6d5e6 3842 3839 2025-08-22T15:01:12Z Imnotgoodatnames 121 Added Features, an image, citations and a References header wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Mc.png|frameless]] | caption = Midnight Commander in action | title = Midnight Commander | releasestatus = Maintained | lastrelease = 4.8.33 | languages = [[C]] | developers = Miguel de Icaza, GNU Project, et al. | website = https://midnight-commander.org/ }} '''GNU Midnight Commander''' (<code>mc</code>) is a dual-pane [[TUI]] file manager. It also includes an internal file viewer (<code>mcview</code>), editor (<code>mcedit</code>), and diff viewer (<code>mcdiff</code>).<ref>[https://midnight-commander.org/ Welcome to Midnight Commander], Yury V. Zaytsev, 2025-03-02 (Accessed: 2025-08-22)</ref> == Overview == The screen of Midnight Commander is divided into four parts, with most of it being taken up by the two directory panels. On the bottom are the function key labels and above it is the shell command line. On the top is the drop down menu accessible with <code>f9</code>.<ref name="MC(1)">[https://source.midnight-commander.org/man/mc.html#Overview MC(1)] (Accessed: 2025-08-22)</ref> == Features == [[File:Mcf.png|thumb|Midnight Commander accessing a tar archive and remote ftp connection]] ==== Remote access ==== Midnight Commander can access remote machines using ftp, sftp or a shell connection. ==== Mouse support ==== Midnight Commander supports mouse input on xterm-compatible terminal emulators or on a Linux virtual console with [[gpm]]. ==== Tar archives ==== Midnight Commander enables read-only access to tar archives.<ref name="MC(1)" /> == References == 871efb604897987db836be6940481f52218453af 6 903 3840 2025-08-22T14:51:05Z Imnotgoodatnames 121 Midnight Commander accessing a tar archive and remote ftp server. wikitext text/x-wiki == Summary == Midnight Commander accessing a tar archive and remote ftp server. == Licensing == {{CC-BY-SA-4.0}} 31efe2654ea8c7cbd0a865c06e9817e1001635c1 3841 3840 2025-08-22T14:52:46Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Mcf.png]] wikitext text/x-wiki == Summary == Midnight Commander accessing a tar archive and remote ftp server. == Licensing == {{CC-BY-SA-4.0}} 31efe2654ea8c7cbd0a865c06e9817e1001635c1 2 819 3844 3362 2025-08-23T01:48:55Z Hamachitan 222 hamachi wikitext text/x-wiki {{DISPLAYTITLE:ハマチたん}} Romanised as ''Hamachi-tan''. Semi-automated wiki bot by [[User:Madonuko]]. This bot is always run with nuko supervision. == Source == https://github.com/madonuko/hamachitan == Reports == Please create a new topic in the talk page. The title should be prefixed with e.g. <code>Suggestion:</code> or <code>Bug:</code>. == History == On 2025-08-08, Mado wanted a way to tidy up formats of wiki pages automatically. Realising there is no good client-side-only tool available on Linux, it was quickly decided that creating a wiki bot might be overpowered but is the simplest way. Thus, <ruby>'''ハマチたん'''<rt>hamachitan</rt></ruby> was born, whose name was decided by the fact Mado likes the Japanese fish [[wikipedia:ja:ハマチ|ハマチ]], young Japanese amberjack. b87acd7bf9a63adadda068601b69054239e841a9 6 904 3848 2025-08-24T18:39:28Z Alxhr0 265 wikitext text/x-wiki Logo of Bedrock Linux 43a12f34dd43fc82406a1a0b34ff1831c4a1a6b8 0 905 3850 2025-08-24T20:16:51Z Alxhr0 265 Create the page wikitext text/x-wiki {{Guide Warning}} {{DistributionInfobox | title = Bedrock Linux | image = [[File:Bedrock Linux.png|Bedrock_Linux]] | caption = Bedrock Linux Logo | releasestatus = Maintained | packagemanager = [[pmm]] | releasemodel = Meta distribution | usagetype = Desktop/Server | defaultdesktops = None | architectures = x86_64, s390x, ppc64le, ppc64, ppc, mipsel, mips64el, mips, i686, i586, i486, i386, armv7l, armv7hl, aarch64 | website = [https://bedrocklinux.org bedrocklinux.org] }} [[Category:Linux Distributions]] '''Bedrock Linux''' is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. Bedrock integrates these components into one largely cohesive system. <ref>https://bedrocklinux.org</ref> === Distro compatibility === While Bedrock works fine with most distro's, there are distro's which can cause issues with Bedrock. The best examples are * Distro's that use BSD-like sysvinit * Distro's that use GRUB+BTRFS (due to a bug in GRUB <ref>https://bedrocklinux.org/0.7/feature-compatibility.html#grub-btrfs-zfs</ref>) * Immutable distro's * Distro's like [[NixOS]] or [[GUIX]] === Installation === The Bedrock Linux website provides a hijack script which can be used to convert current Linux distribution to Bedrock Linux <ref>https://bedrocklinux.org/0.7/installation-instructions.html</ref> === Going through the tutorial === Bedrock Linux provides an interactive tutorial which can be accessed with <code>brl tutorial basics</code>, but also a text version for those who prefer those <ref>https://bedrocklinux.org/0.7/basic-usage.html</ref> === Known issues === ==== brl update and brl fetch fail with proxy ==== With some specific URL's brl fetch and brl update might fail For brl update, possible work-arounds include: * Downloading the update with some other software and providing it as the parameter to brl update * Configuring brl update to use another Bedrock mirror. There are no obvious work-arounds for brl fetch. ==== Unmount warnings on shutdown ==== Those are harmless warnings, which are caused by Bedrock using a Linux kernel feature which propagates some mount and unmount operations, Which causes some init systems to be confused by this and show warnings about being unable to unmount directories because they were already unmounted ==== Root filesystem fsck may be skipped ==== Because of a quirk in how Bedrock works, init systems might not mount the root directory read-only in preparation for fsck, Bedrock does attempt to disable this by changing the corresponding field in <code>/etc/fstab</code> Some initrds will <code>fsck</code> the root filesystem, but not all. Bedrock should offer the option to call <code>fsck</code> on the root filesystem, but it currently does not <ref>https://bedrocklinux.org/0.7/known-issues.html</ref> == References == <references /> 286c5f268b41599b8c0ab4b4404bf05a269fa9fe 0 641 3851 3739 2025-08-25T09:10:58Z Imnotgoodatnames 121 removed from "Desktop Environments" category and added to "X Window Managers" category wikitext text/x-wiki [Category:X_Window_Managers]] {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Maintenance |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/ openbox.org] }} [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable [[X Window Manager|window manager]] for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>[https://openbox.org/ Home - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>[https://openbox.org/obconf ObConf - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> === Usage === While Openbox is perfectly usable on its own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], lxqt, 2025-08-09 (Accessed: 2025-08-09)</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>[https://slitaz.org/en/about/ SliTaz - About the project], SliTaz (Accessed: 2025-08-09)</ref><ref>[https://crunchbang.org/about/ About - CrunchBang], CrunchBang Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> == References == <references /> 85fc03331cc74324547b04e0c5797b1780125dc6 3852 3851 2025-08-25T09:11:30Z Imnotgoodatnames 121 oops wikitext text/x-wiki [[Category:X_Window_Managers]] {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Maintenance |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/ openbox.org] }} [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable [[X Window Manager|window manager]] for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>[https://openbox.org/ Home - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>[https://openbox.org/obconf ObConf - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> === Usage === While Openbox is perfectly usable on its own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], lxqt, 2025-08-09 (Accessed: 2025-08-09)</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>[https://slitaz.org/en/about/ SliTaz - About the project], SliTaz (Accessed: 2025-08-09)</ref><ref>[https://crunchbang.org/about/ About - CrunchBang], CrunchBang Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> == References == <references /> 50c665a5b0bd3ee0cf9bd272ff0dcfcc2688ae5b 0 306 3853 3692 2025-08-25T09:17:19Z Imnotgoodatnames 121 removed a bunch of non-X WMs from the list. not sure if i got them all wikitext text/x-wiki [[Category:Terminology]] [[Category:Window Management Systems]] {{Work_In_Progress}} A window manager is a piece of system software for [[X11|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent GUI. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as dwm.  == Types of Window Manager == === Stacking/Floating Window Managers === Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm === Tiling Window Managers === Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[i3]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] === Dynamic Window Managers === Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * qtile * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] === Scrollable Window Managers === Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[karousel]] 67710d38531b7ca3cf5f5d49c1c5951383161f86 6 906 3854 2025-08-25T10:14:23Z Atmois 13 test description wikitext text/x-wiki == Summary == test description 5ff8dc10797e6e600ea728a95aa3032b2c6d224b 0 254 3855 3730 2025-08-25T11:00:48Z Imnotgoodatnames 121 fixed infobox website link wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h. This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm. == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == 38fd4c58d8ed2fcd6063924c7229013c18759e8b 0 907 3856 2025-08-25T16:06:31Z Ivanovics 150 Basic page about PipeWire's features wikitext text/x-wiki [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon 8a6999508ac3f36e1551d900508446a1676f2d71 6 908 3857 2025-08-25T16:08:17Z Imnotgoodatnames 121 Screen editor nvi wikitext text/x-wiki == Summary == Screen editor nvi == Licensing == {{CC-BY-SA-4.0}} cd5483ae79f7749e58faac6241bdb2452724bd68 3859 3857 2025-08-25T16:15:38Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Nvi.png]] wikitext text/x-wiki == Summary == Screen editor nvi == Licensing == {{CC-BY-SA-4.0}} cd5483ae79f7749e58faac6241bdb2452724bd68 3860 3859 2025-08-25T16:19:44Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Nvi.png]] wikitext text/x-wiki == Summary == Screen editor nvi == Licensing == {{CC-BY-SA-4.0}} cd5483ae79f7749e58faac6241bdb2452724bd68 3864 3860 2025-08-25T16:38:46Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Nvi.png]] wikitext text/x-wiki == Summary == Screen editor nvi == Licensing == {{CC-BY-SA-4.0}} cd5483ae79f7749e58faac6241bdb2452724bd68 3870 3864 2025-08-26T09:34:21Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Nvi.png]] wikitext text/x-wiki == Summary == Screen editor nvi == Licensing == {{CC-BY-SA-4.0}} cd5483ae79f7749e58faac6241bdb2452724bd68 0 345 3858 3631 2025-08-25T16:09:47Z Ivanovics 150 Fix spelling wikitext text/x-wiki [[Category:Terminology]] {{Needs Citations}}Kernel Modules are pieces of code that can be loaded directly into the [[Kernel]] at runtime to extend functionality.<ref>https://linux-kernel-labs.github.io/refs/heads/master/labs/kernel_modules.html Kernel Labs Github, 2025 (imported 26th June 2025)</ref> The Kernel itself can usually determine what modules it may need to properly run, but they can also be manually added, or removed by the user themselves. Typically, The Linux Kernel ships with every module built in by default, but this may vary depending on your [[Linux Distributions|Distribution]], as such, there are some distributions that only provide modules your system needs rather than shipping ALL modules by default, This may help with performance on some systems (Typically older ones benefit the most) at the cost of new devices potentially not working when added. It is also possible to compile a Linux kernel on a pre-existing system to only use needed Kernel modules. == Obtaining information == Modules depend on the kernel release and the kernels version, though usually they are stored in <code>/usr/lib/modules/''kernel_release_version''</code>''.'' To see which modules are loaded, <code>lsmod</code> can be used. Obtaining information is achievable with <code>modinfo <module_name></code> == Module loading == === Automatic loading === Usually most needed modules are handled [[udev]], so out of tree modules aren't needed, though there are cases where loading or blacklisting a module is needed for your setup to function properly. Early module loading is generally handled by your [[initramfs]] generator of choice, usually dracut, booster or mkinitcpio. Alternatively, [[systemd]] will load modules explicitly listed in <code>/etc/modules-load.d/</code> ,with the naming scheme of <code>/etc/modules-load.d/program.conf</code>. Lines starting with ; or # are parsed as comments and ignored === Manual loading === Kernel modules can be manually loaded with <code>modprobe <module_name></code>, or loading a module that by file name (i.e. modules that are not installed in <code>/usr/lib/modules/<kernel_release_version></code>) can be achieved either of the following ways:<syntaxhighlight lang="sh"> insmod file_name module_options modprobe file_name </syntaxhighlight>Removing a module can be achieved by:<syntaxhighlight lang="sh"> rmmod module_name modprobe -r module_name modprobe --remove module_name </syntaxhighlight> == References == 6d7ce39da429f8ddf95fadea81ce1da98e5d6669 0 909 3861 2025-08-25T16:27:55Z Imnotgoodatnames 121 created page wikitext text/x-wiki {{DISPLAYTITLE:nvi}} [[category:software]] '''nvi''' is a text editor for [[Unix-Like]] operating systems. nvi was originally created as a replacement for the [[vi]] editor and first appeared in 4.4BSD. Unlike other modern implementations of the vi editor such as [[vim]] or [[elvis]], nvi still closely resembles the look and feel of the original vi. 9f407dd0193d2dc62aab993b611e364af304cd2d 3871 3861 2025-08-26T09:40:58Z Imnotgoodatnames 121 added citation wikitext text/x-wiki {{DISPLAYTITLE:nvi}} [[category:software]] '''nvi''' is a text editor for [[Unix-Like]] operating systems. nvi was originally created as a replacement for the [[vi]] editor and first appeared in 4.4BSD.<ref>https://man.openbsd.org/vi.1</ref> Unlike other modern implementations of the vi editor such as [[vim]] or [[elvis]], nvi still closely resembles the look and feel of the original vi. == References == 02812355b367403d4e1ab9a591131f88f1da79e9 6 910 3862 2025-08-25T16:32:28Z Imnotgoodatnames 121 test image wikitext text/x-wiki == Summary == test image == Licensing == {{Unknown_copyright}} e9d8b8e9c52d41688c9d6d7c14743b2ced2e765d 6 911 3863 2025-08-25T16:33:26Z Imnotgoodatnames 121 another test image wikitext text/x-wiki == Summary == another test image == Licensing == {{Unknown_copyright}} ca623ba817387c9b33abab858271b1f572e6edf8 6 912 3865 2025-08-25T16:45:37Z Imnotgoodatnames 121 nvi reuploaded to hopefully not be broken anymore wikitext text/x-wiki == Summary == nvi reuploaded to hopefully not be broken anymore == Licensing == {{CC-BY-SA-4.0}} 1a70e43cc1c355d049308d56dac65e38bebb783c 3866 3865 2025-08-25T16:46:41Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Nvi2.png]] wikitext text/x-wiki == Summary == nvi reuploaded to hopefully not be broken anymore == Licensing == {{CC-BY-SA-4.0}} 1a70e43cc1c355d049308d56dac65e38bebb783c 0 907 3867 3856 2025-08-25T16:55:58Z Ivanovics 150 Add usage section wikitext text/x-wiki [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Usage == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. 563c86c08126d7f034166f853abfb007ddccb414 6 913 3868 2025-08-25T17:25:15Z Atmois 13 Bazzite Hyfetch Image wikitext text/x-wiki == Summary == Bazzite Hyfetch Image == Licensing == {{CC-BY-4.0}} 9b112df291519ae7a004334875e3e9605fc96e97 3000 914 3869 2025-08-26T09:23:00Z Osama 266 Created page with "# la will edit in my laptop soon just to save this page" wikitext text/x-wiki # la will edit in my laptop soon just to save this page 94326bdb918de675b58ca65a32dbe6dc9acc1be6 4 327 3872 3755 2025-08-26T12:38:33Z Atmois 13 test images wikitext text/x-wiki linux is cool.<ref>{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributiors|year=2025}}</ref> why? because i said so. hi [[File:Bazzitehyfetch.png|alt=test|thumb|600x600px|Test]] =References= <references /> c5aaa66e55d4479a6c7b5c15ae64c34ad8ed483a 3873 3872 2025-08-26T12:58:24Z Atmois 13 wikitext text/x-wiki linux is cool.<ref>{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributiors|year=2025}}</ref> why? because i said so. hi [[File:Bazzitehyfetch.png|alt=test|thumb]] =References= <references /> 1a378cb3db30798af1ead765348bb9aebe6081e9 6 915 3874 2025-08-27T00:47:51Z Ned Fox 268 wikitext text/x-wiki EasyEffects' "Input" "Effects" tab adfd04d54b7dafe2630200e60b1f63ca0ce34fd9 0 916 3875 2025-08-27T01:03:59Z Ned Fox 268 Created page: "EasyEffects"; started the introduction wikitext text/x-wiki = EasyEffects = [[File:EasyEffects-Input-Effects-empty.png|thumb|EasyEffects as it opens by default]] == Introduction == EasyEffects, available on Flathub [https://flathub.org/apps/com.github.wwmm.easyeffects here], is a tool for adding effects to audio input and output under PipeWire. For the PulseAudio counterpart, see [[PulseEffects]]. = This article is currently a work in progress... = 9a23ccd41857e52fde73c1bc3c6726fa8a03ab58 3878 3875 2025-08-27T02:20:53Z Ned Fox 268 wikitext text/x-wiki = Introduction = EasyEffects, available on Flathub [https://flathub.org/apps/com.github.wwmm.easyeffects here], is a tool for adding effects to audio input and output under PipeWire. It is a GTK application that bundles many effects and tools, making it easier to use out of the box. EasyEffects does not support external plugins. If you would like to use external plugins, see (list advanced tools here). For the PulseAudio counterpart, see [[PulseEffects]]. = Application layout = [[File:EasyEffects-Input-Effects-empty.png|thumb|EasyEffects as it opens by default|1084x1084px]] == The effects list == == Input and Output == == Recorders and Players == == Presets == == Settings == = Effects = == Simple and useful == === Equalizer === === Noise Reduction === === Compressor === === Delay === === Level Meter === == Advanced and Niche == = Quirks = == Interaction with OBS == To capture unmodified sound from the desktop, you will want to configure OBS to connect to "Easy Effects Sink" for its "Desktop Audio" "Properties". This can often result in a garbled audio stream. To fix this, add "Stereo Tools" to the top of the output effects list. EasyEffects will not modify the "Mic/Aux" audio input in OBS by default. To get this effect, you may either enable "Process All Input Streams" in the hamburger menu top-right -> "Preferences" -> "General" -> "Audio" -> "Process All Input Streams". Or you may select "Easy Effects Source" as the source for "Mic/Aux" in its "Properties". It is recommended to have "Stereo Tools" a the top of the input effects list as well. 174c914cdf95da3422c98ac1b09ba6e07e11e207 3879 3878 2025-08-27T02:27:00Z Ned Fox 268 /* Interaction with OBS */ Fixed a typo. I intend to continue work on the page tomorrow. wikitext text/x-wiki = Introduction = EasyEffects, available on Flathub [https://flathub.org/apps/com.github.wwmm.easyeffects here], is a tool for adding effects to audio input and output under PipeWire. It is a GTK application that bundles many effects and tools, making it easier to use out of the box. EasyEffects does not support external plugins. If you would like to use external plugins, see (list advanced tools here). For the PulseAudio counterpart, see [[PulseEffects]]. = Application layout = [[File:EasyEffects-Input-Effects-empty.png|thumb|EasyEffects as it opens by default|1084x1084px]] == The effects list == == Input and Output == == Recorders and Players == == Presets == == Settings == = Effects = == Simple and useful == === Equalizer === === Noise Reduction === === Compressor === === Delay === === Level Meter === == Advanced and Niche == = Quirks = == Interaction with OBS == To capture unmodified sound from the desktop, you will want to configure OBS to connect to "Easy Effects Sink" for its "Desktop Audio" "Properties". This can often result in a garbled audio stream. To fix this, add "Stereo Tools" to the top of the output effects list. EasyEffects will not modify the "Mic/Aux" audio input in OBS by default. To get this effect, you may either enable "Process All Input Streams" in the hamburger menu top-right -> "Preferences" -> "General" -> "Audio" -> "Process All Input Streams". Or you may select "Easy Effects Source" as the source for "Mic/Aux" in its "Properties". It is recommended to have "Stereo Tools" at the top of the input effects list as well. a88de85adcc28c7f407e3e69899034aa77a4efbf 3880 3879 2025-08-27T02:29:02Z Ned Fox 268 /* Introduction */ wikitext text/x-wiki = Introduction = Easy Effects, available on Flathub [https://flathub.org/apps/com.github.wwmm.easyeffects here], is a tool for adding effects to audio input and output under PipeWire. It is a GTK application that bundles many effects and tools, making it easier to use out of the box. EasyEffects does not support external plugins. If you would like to use external plugins, see (list advanced tools here). For the PulseAudio counterpart, see [[PulseEffects]]. = Application layout = [[File:EasyEffects-Input-Effects-empty.png|thumb|EasyEffects as it opens by default|1084x1084px]] == The effects list == == Input and Output == == Recorders and Players == == Presets == == Settings == = Effects = == Simple and useful == === Equalizer === === Noise Reduction === === Compressor === === Delay === === Level Meter === == Advanced and Niche == = Quirks = == Interaction with OBS == To capture unmodified sound from the desktop, you will want to configure OBS to connect to "Easy Effects Sink" for its "Desktop Audio" "Properties". This can often result in a garbled audio stream. To fix this, add "Stereo Tools" to the top of the output effects list. EasyEffects will not modify the "Mic/Aux" audio input in OBS by default. To get this effect, you may either enable "Process All Input Streams" in the hamburger menu top-right -> "Preferences" -> "General" -> "Audio" -> "Process All Input Streams". Or you may select "Easy Effects Source" as the source for "Mic/Aux" in its "Properties". It is recommended to have "Stereo Tools" at the top of the input effects list as well. 043273d4a8d45c90bb3439870392826d36a09a7c 3881 3880 2025-08-27T02:29:35Z Ned Fox 268 /* Application layout */ wikitext text/x-wiki = Introduction = Easy Effects, available on Flathub [https://flathub.org/apps/com.github.wwmm.easyeffects here], is a tool for adding effects to audio input and output under PipeWire. It is a GTK application that bundles many effects and tools, making it easier to use out of the box. EasyEffects does not support external plugins. If you would like to use external plugins, see (list advanced tools here). For the PulseAudio counterpart, see [[PulseEffects]]. = Application layout = [[File:EasyEffects-Input-Effects-empty.png|thumb|Easy Effects as it opens by default|1084x1084px]] == The effects list == == Input and Output == == Recorders and Players == == Presets == == Settings == = Effects = == Simple and useful == === Equalizer === === Noise Reduction === === Compressor === === Delay === === Level Meter === == Advanced and Niche == = Quirks = == Interaction with OBS == To capture unmodified sound from the desktop, you will want to configure OBS to connect to "Easy Effects Sink" for its "Desktop Audio" "Properties". This can often result in a garbled audio stream. To fix this, add "Stereo Tools" to the top of the output effects list. EasyEffects will not modify the "Mic/Aux" audio input in OBS by default. To get this effect, you may either enable "Process All Input Streams" in the hamburger menu top-right -> "Preferences" -> "General" -> "Audio" -> "Process All Input Streams". Or you may select "Easy Effects Source" as the source for "Mic/Aux" in its "Properties". It is recommended to have "Stereo Tools" at the top of the input effects list as well. 0ca5d51157a4f351e1329b40f895c3dd16edca60 3882 3881 2025-08-27T02:31:05Z Ned Fox 268 /* Interaction with OBS */ wikitext text/x-wiki = Introduction = Easy Effects, available on Flathub [https://flathub.org/apps/com.github.wwmm.easyeffects here], is a tool for adding effects to audio input and output under PipeWire. It is a GTK application that bundles many effects and tools, making it easier to use out of the box. EasyEffects does not support external plugins. If you would like to use external plugins, see (list advanced tools here). For the PulseAudio counterpart, see [[PulseEffects]]. = Application layout = [[File:EasyEffects-Input-Effects-empty.png|thumb|Easy Effects as it opens by default|1084x1084px]] == The effects list == == Input and Output == == Recorders and Players == == Presets == == Settings == = Effects = == Simple and useful == === Equalizer === === Noise Reduction === === Compressor === === Delay === === Level Meter === == Advanced and Niche == = Quirks = == Interaction with OBS == To capture unmodified sound from the desktop, you will want to configure OBS to connect to "Easy Effects Sink" for its "Desktop Audio" "Properties". This can often result in a garbled audio stream. To fix this, add "Stereo Tools" to the top of the output effects list. Easy Effects will not modify the "Mic/Aux" audio input in OBS by default. To get this effect, you may either enable "Process All Input Streams" in the hamburger menu top-right -> "Preferences" -> "General" -> "Audio" -> "Process All Input Streams". Or you may select "Easy Effects Source" as the source for "Mic/Aux" in its "Properties". It is recommended to have "Stereo Tools" at the top of the input effects list as well. 7a72c4ba3b4e76be0c4ff208ea695d9b6ffec0c4 3883 3882 2025-08-27T02:36:34Z Ned Fox 268 Removing page to migrate it to page with correct title. wikitext text/x-wiki This article is a misspelled title. Please delete it. 456d810b3a973de79556ba6ee483357c8cc26dc3 3885 3883 2025-08-27T02:47:37Z Ned Fox 268 I figured this page does have a purpose: To redirect people making the same mistake I did. That is until it is hopefully deleted. wikitext text/x-wiki Unlike it's predecessor, [[PulseEffects]], [[Easy Effects]] has a space in it's name. 7710e2a27f5dbe9092bb83c4e63632a79a1d7bda 3901 3885 2025-08-27T07:33:31Z Atmois 13 Create a redirect wikitext text/x-wiki #REDIRECT [[Easy Effects]] 7be04db205151bdf1f098ea9e047df7d903ca73f 6 917 3876 2025-08-27T01:44:07Z Zyankali 267 From the official fish-shell github repository, located at "doc_src/python_docs_theme/static/fish.png". wikitext text/x-wiki == Summary == From the official fish-shell github repository, located at "doc_src/python_docs_theme/static/fish.png". == Licensing == {{GPL}} 66636da3faaa1fb477e644ef3dcf2e10297b7ad7 0 2 3877 3578 2025-08-27T02:12:50Z Docteurmonkeybro 269 added a few citations. AUR wiki sourc, ILoveCandy easter egg and Arch Linux Inspired by CRUX. wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[Category:Linux Distributions]] [[File:Arch_Linux_Minimal_Neofetch_Output.png|thumb|[[Neofetch]] on Arch Linux]] '''Arch Linux''' is an independent rolling release [[Linux Distributions|Linux distribution]] focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. Arch Linux is kept up-to-date by regularly updating the packages of the system. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages.<ref>{{Cite|url=https://wiki.archlinux.org/title/Arch_User_Repository#Build_the_package|title=Arch User Repository Wiki|accessdate=2025-08-26}}</ref> <code>makepkg</code> is part of the ''pacman'' package. === Installation === The Arch Linux website provides a downloadable ISO image that can be flashed onto a bootable drive. The operating system can be installed by following the [https://wiki.archlinux.org/title/Installation_guide Installation Guide] or by using the included installation script, archinstall. ==== Arch Installation Script ==== This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots.<ref>{{Cite|url=https://shibumi.dev/posts/my-pacman.conf-file/|title=My pacman.conf file|author=Christian Rebischke|year=2020|accessdate=2025-08-26}}</ref> * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX.<ref>{{Cite|url=https://wiki.archlinux.org/title/Arch_compared_to_other_distributions?pubDate=20250818#CRUX|title=Arch compared to other distributions|accessdate=2025-08-26}}</ref> == References == <references /> f91bf6644a04723e54453d335501f2f78853d2f3 0 918 3884 2025-08-27T02:39:04Z Ned Fox 268 Migrated the content from the misspelled "EasyEffects" wikitext text/x-wiki = Introduction = Easy Effects, available on Flathub [https://flathub.org/apps/com.github.wwmm.easyeffects here], is a tool for adding effects to audio input and output under PipeWire. It is a GTK application that bundles many effects and tools, making it easier to use out of the box. Easy Effects does not support external plugins. If you would like to use external plugins, see (list advanced tools here). For the PulseAudio counterpart, see [[PulseEffects]]. = Application layout = [[File:EasyEffects-Input-Effects-empty.png|thumb|Easy Effects as it opens by default|1084x1084px]] == The effects list == == Input and Output == == Recorders and Players == == Presets == == Settings == = Effects = == Simple and useful == === Equalizer === === Noise Reduction === === Compressor === === Delay === === Level Meter === == Advanced and Niche == = Quirks = == Interaction with OBS == To capture unmodified sound from the desktop, you will want to configure OBS to connect to "Easy Effects Sink" for its "Desktop Audio" "Properties". This can often result in a garbled audio stream. To fix this, add "Stereo Tools" to the top of the output effects list. Easy Effects will not modify the "Mic/Aux" audio input in OBS by default. To get this effect, you may either enable "Process All Input Streams" in the hamburger menu top-right -> "Preferences" -> "General" -> "Audio" -> "Process All Input Streams". Or you may select "Easy Effects Source" as the source for "Mic/Aux" in its "Properties". It is recommended to have "Stereo Tools" at the top of the input effects list as well. 474eb346d1b98556e8c31b5fc8b0083852a1a69c 0 919 3886 2025-08-27T03:20:43Z Zyankali 267 Create the Fish article. wikitext text/x-wiki {{SoftwareInfobox |image=[[File:Fish-Shell.png|thumb]] |caption=Fish-shell Logo |title=Fish |releasestatus=Maintained |lastrelease=4.0.2, 2025-04-20 |languages=[[Rust]] |developers=Fish-shell developers |website=[https://fishshell.com/ fishshell.com] }} '''Fish''' (Friendly Interactive Shell) is a [[CLI]] with an out-of-the-box, feature-rich experience.<ref>[[wikipedia:Fish_(Unix_shell)|Fish (Unix shell)]], Wikipedia (Accessed: 2025-08-27)</ref> == References == <references /> c1f72a558ed58d4f0a118a34b30fbaa38b4c99f4 3887 3886 2025-08-27T03:32:19Z Platzmacher 245 added first release too infobox wikitext text/x-wiki {{SoftwareInfobox |image=[[File:Fish-Shell.png|thumb]] |caption=Fish-shell Logo |title=Fish |releasestatus=Maintained |lastrelease=4.0.2, 2025-04-20 |firstrelease=2.0.0, 2013-09-01 |languages=[[Rust]] |developers=Fish-shell developers |website=[https://fishshell.com/ fishshell.com] }} '''Fish''' (Friendly Interactive Shell) is a [[CLI]] with an out-of-the-box, feature-rich experience.<ref>[[wikipedia:Fish_(Unix_shell)|Fish (Unix shell)]], Wikipedia (Accessed: 2025-08-27)</ref> == References == <references /> 62c67fa09e8f9318bb5ef8c462d55acb61dd1a18 3888 3887 2025-08-27T04:29:01Z Zyankali 267 Adding feature overview and information on POSIX incompatibility. wikitext text/x-wiki {{SoftwareInfobox |image=[[File:Fish-Shell.png|thumb]] |caption=Fish-shell Logo |title=Fish |releasestatus=Maintained |lastrelease=4.0.2, 2025-04-20 |languages=[[Rust]] |developers=Fish-shell developers |website=[https://fishshell.com/ fishshell.com] }} '''Fish''' (Friendly Interactive Shell) is a [[CLI]] with an out-of-the-box, feature-rich experience.<ref>[[wikipedia:Fish_(Unix_shell)|Fish (Unix shell)]], Wikipedia (Accessed: 2025-08-27)</ref> It offers the user features such as command suggestions, web-based configuration, colorful aesthetics<ref>[[https://fishshell.com fish shell]], Ridiculous Fish (Accessed: 2025-08-27)</ref> as well as expanded keyboard shortcuts<ref>[[https://fishshell.com/docs/current/interactive.html#shared-bindings Interactive use — fish-shell 4.0.2 documentation]], Fish-shell (Accessed: 2025-08-27)</ref>. Unlike many other commonly used shells, like Bash or Zsh, it does not adhere to the [[POSIX]] standard, which may cause Fish to throw errors if a command contains POSIX-specific syntax. == References == <references /> 49cd271a6c7c7fd9a989b9b4f906987eb2c4893c 3889 3888 2025-08-27T04:53:35Z Zyankali 267 Undo revision [[Special:Diff/3888|3888]] by [[Special:Contributions/Zyankali|Zyankali]] ([[User talk:Zyankali|talk]]) wikitext text/x-wiki {{SoftwareInfobox |image=[[File:Fish-Shell.png|thumb]] |caption=Fish-shell Logo |title=Fish |releasestatus=Maintained |lastrelease=4.0.2, 2025-04-20 |firstrelease=2.0.0, 2013-09-01 |languages=[[Rust]] |developers=Fish-shell developers |website=[https://fishshell.com/ fishshell.com] }} '''Fish''' (Friendly Interactive Shell) is a [[CLI]] with an out-of-the-box, feature-rich experience.<ref>[[wikipedia:Fish_(Unix_shell)|Fish (Unix shell)]], Wikipedia (Accessed: 2025-08-27)</ref> It offers the user features such as command suggestions, web-based configuration, colorful aesthetics<ref>[[https://fishshell.com fish shell]], Ridiculous Fish (Accessed: 2025-08-27)</ref> as well as expanded keyboard shortcuts<ref>[[https://fishshell.com/docs/current/interactive.html#shared-bindings Interactive use — fish-shell 4.0.2 documentation]], Fish-shell (Accessed: 2025-08-27)</ref>. Unlike many other commonly used shells, like Bash or Zsh, it does not adhere to the [[POSIX]] standard, which may cause Fish to throw errors if a command contains POSIX-specific syntax. == References == <references /> cc0cd33bdb2a706430993a402e1cdef0eef302ca 0 920 3890 2025-08-27T06:07:57Z Zeron.rendezvous 270 Added information about CSS wikitext text/x-wiki = Cascading Style Sheets (CSS) = '''Cascading Style Sheets (CSS)''' is a style sheet language used for describing the presentation of a document written in [[HTML]] or [[XML]] (including dialects like [[SVG]] and [[XHTML]]). CSS defines how elements should be rendered on screen, on paper, in speech, or on other media. == Overview == CSS separates the content of documents from their visual presentation, providing greater flexibility and control in the specification of presentation characteristics such as: * Layout * Colors * Fonts * Spacing == History == CSS was first proposed by [[Håkon Wium Lie]] in 1994 while working with [[Tim Berners-Lee]] at CERN. The first official CSS specification (CSS1) was published by the [[World Wide Web Consortium|W3C]] in 1996. == Syntax == A CSS rule consists of a *selector* and a *declaration block*. Example: <syntaxhighlight lang="css"> p { color: blue; font-size: 14px; } </syntaxhighlight> * `p` is the selector (applies to all <p> elements). * `color: blue;` and `font-size: 14px;` are declarations. == Versions == * '''CSS1''' – 1996, basic styling features. * '''CSS2''' – 1998, added positioning, media types, and more. * '''CSS3''' – modularized specification, ongoing development. * '''CSS4''' – not a single specification, but a term used to describe ongoing CSS modules. == Uses == * Styling web pages for different devices and screen sizes. * Enabling responsive design. * Controlling animations and transitions. == See also == * [[HTML]] * [[JavaScript]] * [[Web development]] == External links == * [https://www.w3.org/Style/CSS/ W3C CSS Homepage] * [https://developer.mozilla.org/en-US/docs/Web/CSS MDN Web Docs: CSS] 2984c46d1a55666fe1538f5f0d31a6b08aa0bc88 0 782 3891 3606 2025-08-27T06:19:43Z Zeron.rendezvous 270 Added additional information and links wikitext text/x-wiki [[Category:Widget system]] [https://github.com/elkowar/eww/tree/master/docs EWW Repository] '''EWW''' ('''Elkowar's Wacky Widgets''') is a standalone widget system written in [[Rust (programming language)|Rust]] by Elkowar. It allows users to implement custom widgets for any window manager. Configuration is handled through [[Yuck]] files (a lisp-like S-expression language) and SCSS/[[CSS]] stylesheets. == Overview == EWW provides a flexible framework for creating: * Status bars * Dashboards * Custom desktop widgets It is often compared to [[Waybar]] due to its use of GTK/CSS for styling. == Configuration == * '''Yuck''': a lisp-like domain-specific language used for declaring and structuring widgets. * '''CSS''': used for styling widgets; EWW leverages GTK’s CSS engine. == Documentation == Official documentation can be found here: [https://elkowar.github.io/eww/ EWW Documentation]. Official documentation for GTk's CSS engine can be found here: [https://docs.gtk.org/gtk3/css-overview.html GTK CSS Documentation] == Usage == The most common way to learn the Yuck syntax and widget setup is by studying community configuration files. de7a13a69859b6bb171aec209fdda9bdca92eb9e 3897 3891 2025-08-27T06:57:39Z Zeron.rendezvous 270 added infobox wikitext text/x-wiki [[Category:Widget system]] {{SoftwareInfobox |image=[[File:Eww.png|thumb]] |caption=EWW Logo |title=EWW |releasestatus=Maintained |lastrelease=0.6.0, 2024-04-21 |firstrelease=0.1.0, 2021-08-18 |languages=[[Rust]] |developers=Elkowar |website=[https://elkowar.github.io/eww elkowar.github.io] }} [https://github.com/elkowar/eww/tree/master/docs EWW Repository] '''EWW''' ('''Elkowar's Wacky Widgets''') is a standalone widget system written in [[Rust (programming language)|Rust]] by Elkowar. It allows users to implement custom widgets for any window manager. Configuration is handled through [[Yuck]] files (a lisp-like S-expression language) and SCSS/[[CSS]] stylesheets. == Overview == EWW provides a flexible framework for creating: * Status bars * Dashboards * Custom desktop widgets It is often compared to [[Waybar]] due to its use of GTK/CSS for styling. == Configuration == * '''Yuck''': a lisp-like domain-specific language used for declaring and structuring widgets. * '''CSS''': used for styling widgets; EWW leverages GTK’s CSS engine. == Documentation == Official documentation can be found here: [https://elkowar.github.io/eww/ EWW Documentation]. Official documentation for GTk's CSS engine can be found here: [https://docs.gtk.org/gtk3/css-overview.html GTK CSS Documentation] == Usage == The most common way to learn the Yuck syntax and widget setup is by studying community configuration files. 8663a34f0a4cf8fc9b10388cfa081caacee3eb3c 0 921 3892 2025-08-27T06:20:37Z Zeron.rendezvous 270 Same as "Css" wikitext text/x-wiki [[Css]] 6131ce47f943394ea53cbce3971180bfb33ef0f1 3900 3892 2025-08-27T07:17:53Z Madonuko 140 Redirected page to [[Css]] wikitext text/x-wiki #REDIRECT [[Css]] b14d66ec1b77314671eca34e16b7f24a6cc640bc 0 922 3893 2025-08-27T06:41:38Z Zeron.rendezvous 270 Added information and repo link wikitext text/x-wiki [[Category:Application launchers]] [[Category:Linux software]] [https://github.com/vicinaehq/vicinae/ Vicinae Repository] '''Vicinae''' (pronounced ''vih-SIN-ay'') is a high-performance, native application launcher for [[Linux]], built with [[C++]] and [[Qt (software)|Qt]]. == Overview == Vicinae provides a fast, keyboard-first interface for launching applications and performing system actions. It is primarily targeted at developers and power users who prefer minimal overhead and efficient workflows. == Features == * Built-in modules for common tasks. * Extension development using fully server-side [[React (JavaScript library)|React]] and [[TypeScript]], without requiring a browser or Electron runtime. * Inspired by the popular [[Raycast]] launcher, offering a largely compatible extension API that allows reuse of many existing Raycast extensions with minimal changes. == Design == Vicinae emphasizes performance and simplicity, leveraging native technologies rather than web-based runtimes. Its architecture is designed to provide rapid response times and seamless integration with the Linux desktop environment. 0f29c8098c9a8ffd10858a4c871d4e43e7bfd756 3899 3893 2025-08-27T07:10:37Z Zeron.rendezvous 270 added info box wikitext text/x-wiki [[Category:Application launchers]] [[Category:Linux software]] {{SoftwareInfobox |image=[[File:Vicinae-banner.png|thumb]] |caption=Vicinae Logo |title=Vicinae |releasestatus=Maintained |lastrelease=- |firstrelease=- |languages=[[C++]] [[Qt]] |developers=Vicinae Developers |website=[https://github.com/vicinaehq/vicinae vicinae.com] }} <ref> [[File:Vicinae-banner.png|thumb]] </ref> [https://github.com/vicinaehq/vicinae/ Vicinae Repository] '''Vicinae''' (pronounced ''vih-SIN-ay'') is a high-performance, native application launcher for [[Linux]], built with [[C++]] and [[Qt (software)|Qt]]. == Overview == Vicinae provides a fast, keyboard-first interface for launching applications and performing system actions. It is primarily targeted at developers and power users who prefer minimal overhead and efficient workflows. == Features == * Built-in modules for common tasks. * Extension development using fully server-side [[React (JavaScript library)|React]] and [[TypeScript]], without requiring a browser or Electron runtime. * Inspired by the popular [[Raycast]] launcher, offering a largely compatible extension API that allows reuse of many existing Raycast extensions with minimal changes. == Design == Vicinae emphasizes performance and simplicity, leveraging native technologies rather than web-based runtimes. Its architecture is designed to provide rapid response times and seamless integration with the Linux desktop environment. 75255e9388b161ded8d7ebeefba84f8ed1aad8b2 0 923 3894 2025-08-27T06:43:01Z Zeron.rendezvous 270 Created page with "[[Category:JavaScript libraries]] '''React''' (also known as '''React.js''' or '''ReactJS''') is an open-source [[JavaScript]] library for building user interfaces. Originally developed by [[Meta Platforms|Facebook]], React enables developers to create fast, interactive web applications using a component-based architecture and a declarative programming model." wikitext text/x-wiki [[Category:JavaScript libraries]] '''React''' (also known as '''React.js''' or '''ReactJS''') is an open-source [[JavaScript]] library for building user interfaces. Originally developed by [[Meta Platforms|Facebook]], React enables developers to create fast, interactive web applications using a component-based architecture and a declarative programming model. 5e92eb814252e8bd3417ba8535c399694eb242f8 0 924 3895 2025-08-27T06:43:59Z Zeron.rendezvous 270 info wikitext text/x-wiki [[Category:Programming languages]] [[Category:JavaScript]] '''TypeScript''' is an open-source programming language developed and maintained by [[Microsoft]]. It is a strict syntactical superset of [[JavaScript]] that adds optional static typing, making it easier to build and maintain large-scale applications. f857fbdb56839568e38020c1af8bc80046032822 6 925 3896 2025-08-27T06:49:45Z Zeron.rendezvous 270 wikitext text/x-wiki logo for eww 4ee4337574ef3e41ecef06aa40d682f3d034a264 6 926 3898 2025-08-27T07:06:31Z Zeron.rendezvous 270 wikitext text/x-wiki banner 37f93a070955b8890d976577e68f269920fbc73c 3000 927 3902 2025-08-27T08:36:40Z Zeron.rendezvous 270 preliminary very bare bones tutorial with basically nothing wikitext text/x-wiki == Guide for making widgets with EWW: == To get started with the widgets, have a thorough read through of the [https://elkowar.github.io/eww/ EWW Documentation]. Specifically, the [https://elkowar.github.io/eww/widgets.html Widgets] section. This will give you a foundation on the different types of widgets EWW has to offer. == Widget Structure == The widgets have to be enclosed in something called a "box". a box can hold multiple widgets. A box has to be enclosed in a "defwidget". A box can also have multiple boxes nested inside it. All this has to be inside a "defwindow" which you will declare separately '''This will assume you are on Wayland.''' == Hello World Widget: == <pre> (defwindow hello :monitor 0 :geometry (:x "0" :y "0" :width "100px" :height "100px" :anchor "center") :exclusive false :stacking "fg" (world)) (defwidget world (box :class "hello" (label :text "hello world!")) </pre> 65f6f02ff0d7177a534f9afc140389fb26638213 3903 3902 2025-08-27T08:40:41Z Zeron.rendezvous 270 wikitext text/x-wiki == Guide for making widgets with EWW: == To get started with the widgets, have a thorough read through of the [https://elkowar.github.io/eww/ EWW Documentation]. Specifically, the [https://elkowar.github.io/eww/widgets.html Widgets] section. This will give you a foundation on the different types of widgets EWW has to offer. == Widget Structure == The widgets have to be enclosed in something called a "box". a box can hold multiple widgets. A box has to be enclosed in a "defwidget". A box can also have multiple boxes nested inside it. All this has to be inside a "defwindow" which you will declare separately === Hello World Widget: === '''This will assume you are on Wayland.''' <pre>(defwindow hello :monitor 0 :geometry (:x "0" :y "0" :width "100px" :height "100px" :anchor "center") :exclusive false :stacking "fg" (world)) (defwidget world (box :class "hello" (label :text "hello world!"))</pre> 3955b494559568cafa2a362941c5d5fc045bd895 3905 3903 2025-08-27T09:28:54Z Zeron.rendezvous 270 many things :) wikitext text/x-wiki = Guide to Making Widgets with EWW = EWW (Elkowar’s Wacky Widgets) is a powerful tool for creating system widgets on Linux. To get started, read through the official [https://elkowar.github.io/eww/ EWW Documentation], especially the [https://elkowar.github.io/eww/widgets.html Widgets] section. This will give you a strong foundation on the different types of widgets EWW offers. == Variables == Yuck has two main variables: <code>defpoll</code> and <code>deflisten</code> === Defpoll === <syntaxhighlight lang="lisp"> (defpoll time :interval "1s" :initial "initial-value" `date +%H:%M:%S`) </syntaxhighlight> '''A polling variable is a variable which runs a provided shell-script repeatedly, in a given interval.''' === Deflisten === <syntaxhighlight lang="lisp"> (deflisten foo :initial "whatever" `tail -F /tmp/some_file`) </syntaxhighlight> '''A listening variable runs a script once, and reads its output continously. Whenever the script outputs a new line, the value will be updated to that new line.''' == File Structure == Typically, you will work with two files: <pre> eww.yuck eww.scss </pre> However, it’s better to keep things modular. A cleaner structure looks like this: <pre> eww.yuck eww.scss widgets/ ├── <name>.yuck └── <name>.yuck vars/ ├── listens.yuck └── polls.yuck windows/ └── windows.yuck </pre> To join all these files together, use the `include` directive inside your main `eww.yuck`: <syntaxhighlight lang="lisp"> (include "widgets/<name>.yuck") (include "vars/listens.yuck") (include "vars/polls.yuck") (include "windows/windows.yuck") </syntaxhighlight> == Widget Structure == Widgets in EWW follow a simple hierarchy: * Every widget must be wrapped in a <code>defwidget</code> block. * A widget usually contains one or more <code>boxes</code>. * Boxes can contain other boxes or UI elements (like labels, images, buttons, etc.). * To display widgets, they must be attached to a <code>defwindow</code>. === Example: Hello World Widget === '''Note: This example assumes you are running Wayland.''' <syntaxhighlight lang="lisp"> (defwindow hello :monitor 0 :geometry (:x "0" :y "0" :width "100px" :height "100px" :anchor "center") :exclusive false :stacking "fg" (world)) (defwidget world (box :class "hello" (label :text "hello world!"))) </syntaxhighlight> === Explanation === * <code>:monitor 0</code> → Uses your primary monitor. The widget will appear only on this monitor. * <code>:geometry</code> → Defines the position and size of the widget. * <code>:exclusive</code> → If set to <code>true</code>, the widget reserves screen space (like a panel). If <code>false</code>, it floats without affecting other windows. * <code>:stacking</code> → Controls how the widget stacks with other windows. * <code>fg</code> = Foreground (above all apps) * <code>bg</code> = Background (below apps) * <code>:class</code> → Assigns a CSS class for styling in your SCSS file. == Styling Widgets (SCSS) == The appearance of widgets is handled with SCSS. For the above example, you could add: <syntaxhighlight lang="css"> .hello { background-color: pink; border-radius: 5px; padding: 10px; font-weight: bold; } </syntaxhighlight> 3708043b9490fa725cb68718ab57b5f60acee9a5 0 928 3904 2025-08-27T09:21:33Z Platzmacher 245 added a redirect to the rust page wikitext text/x-wiki #REDIRECT [[Rust]] eda56097f2de9aa294acce0a2437f4920449277f 0 176 3906 3818 2025-08-27T12:42:59Z Lyon 224 Removed false "dead link" marks when the links aren't dead. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/, kde.org/plasma-desktop] [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2025-08-14|503}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2025-08-14|503}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> 4ee38bb7364e436a4dc59f415311a8958f004684 0 176 3907 3906 2025-08-27T12:44:10Z Lyon 224 Discovered error in link (Comma was causing a 404) wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2025-08-14|503}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2025-08-14|503}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> 9f9ccd16709b3a1766e32cf9b4d60bbe570b9dd6 3908 3907 2025-08-27T12:46:12Z Lyon 224 Fixing my mistake of removing two curly brackets and breaking the SoftwareInfoBox wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.3.4, Apr 1, 2025 |firstrelease=1.0, July 12, 1998 | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2025-08-14|503}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2025-08-14|503}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> efe9931ff61998cff50f7656adad3504d1695f97 0 763 3909 3753 2025-08-27T13:11:56Z Lyon 224 Added an entry for Suckless' dwm (Don't know how to add an image so I'll fix that later) wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Screenshot of awesomewm4.png|link=awesomewm|awesome File:Compiz Shift Switcher.png|link=Compiz|Compiz File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:Twm.png|link=twm|twm File:Icewm-default.jpg|link=IceWM|IceWM File:I3-wm.png|link=i3|i3 File:Wmaker-0.80.2.png|link=Window_Maker|Window Maker File:Xmonad screenshot.png|link=Xmonad|XMonad </gallery> {| class="wikitable" |+ !Window Manager !Description |- |[[awesome]]<ref>[https://github.com/awesomeWM/awesome GitHub - awesomeWM/awesome: awesome window manager], awesomeWM, 2025-08-09 (Accessed: 2025-08-09)</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |[[Compiz]] |Compiz is a compositing window manager for the X Window System. |- |[[Openbox]] |A minimal and highly configurable stacking window manager written in C. |- |[[twm]]<ref>[https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml TWM], 2010-11-13 (Accessed: 2025-08-09)</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |[[IceWM]]<ref>[https://github.com/bbidulock/icewm GitHub - bbidulock/icewm: A window manager designed for speed, usability, and consistency], bbidulock, 2025-08-09 (Accessed: 2025-08-09)</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |[[i3]]<ref>[https://i3wm.org i3: improved tiling X11 window manager], Michael Stapelberg, 2025-06-12 (Accessed: 2025-08-09)</ref> |A tiling window manager for advanced users and developers. |- |[[Window Maker]]<ref>[https://github.com/window-maker/wmaker GitHub - window-maker/wmaker: Mirror of the official repository repo.or.cz/wmaker-crm.git. Do not send pull requests here, send your patches to wmaker-dev@googlegroups.com instead], window-maker, 2020-08-09 (Accessed: 2025-08-09)</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |[[XMonad]]<ref>[https://xmonad.org/ home | xmonad - the tiling window manager that rocks], xmonad, 2025-06-15 (Accessed: 2025-08-09)</ref> |Window Manager configurable via the Haskell functional programming language. |[[dwm]]<ref>[https://dwm.suckless.org/ dwm, a slim and resource-efficient tiling window manager that stays out of your way and is configured via the source code (written in C)], Suckless, 2025-08-09 (Accessed: 2025-08-27) </ref> |A lightweight tiling window manager written in C. |} ==References== <references /> 861679d8ee834acbcf27c019d73a6c25fe765c1b 3910 3909 2025-08-27T13:13:02Z Lyon 224 Forgot to add a newline wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Screenshot of awesomewm4.png|link=awesomewm|awesome File:Compiz Shift Switcher.png|link=Compiz|Compiz File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:Twm.png|link=twm|twm File:Icewm-default.jpg|link=IceWM|IceWM File:I3-wm.png|link=i3|i3 File:Wmaker-0.80.2.png|link=Window_Maker|Window Maker File:Xmonad screenshot.png|link=Xmonad|XMonad </gallery> {| class="wikitable" |+ !Window Manager !Description |- |[[awesome]]<ref>[https://github.com/awesomeWM/awesome GitHub - awesomeWM/awesome: awesome window manager], awesomeWM, 2025-08-09 (Accessed: 2025-08-09)</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |[[Compiz]] |Compiz is a compositing window manager for the X Window System. |- |[[Openbox]] |A minimal and highly configurable stacking window manager written in C. |- |[[twm]]<ref>[https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml TWM], 2010-11-13 (Accessed: 2025-08-09)</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |[[IceWM]]<ref>[https://github.com/bbidulock/icewm GitHub - bbidulock/icewm: A window manager designed for speed, usability, and consistency], bbidulock, 2025-08-09 (Accessed: 2025-08-09)</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |[[i3]]<ref>[https://i3wm.org i3: improved tiling X11 window manager], Michael Stapelberg, 2025-06-12 (Accessed: 2025-08-09)</ref> |A tiling window manager for advanced users and developers. |- |[[Window Maker]]<ref>[https://github.com/window-maker/wmaker GitHub - window-maker/wmaker: Mirror of the official repository repo.or.cz/wmaker-crm.git. Do not send pull requests here, send your patches to wmaker-dev@googlegroups.com instead], window-maker, 2020-08-09 (Accessed: 2025-08-09)</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |[[XMonad]]<ref>[https://xmonad.org/ home | xmonad - the tiling window manager that rocks], xmonad, 2025-06-15 (Accessed: 2025-08-09)</ref> |Window Manager configurable via the Haskell functional programming language. |- |[[dwm]]<ref>[https://dwm.suckless.org/ dwm, a slim and resource-efficient tiling window manager that stays out of your way and is configured via the source code (written in C)], Suckless, 2025-08-09 (Accessed: 2025-08-27) </ref> |A lightweight tiling window manager written in C. |} ==References== <references /> 5daa8345d94abbdd1d658410f279283e7aed7bed 3911 3910 2025-08-27T13:14:54Z Lyon 224 Changing capitalization to match the DWM page wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Screenshot of awesomewm4.png|link=awesomewm|awesome File:Compiz Shift Switcher.png|link=Compiz|Compiz File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:Twm.png|link=twm|twm File:Icewm-default.jpg|link=IceWM|IceWM File:I3-wm.png|link=i3|i3 File:Wmaker-0.80.2.png|link=Window_Maker|Window Maker File:Xmonad screenshot.png|link=Xmonad|XMonad </gallery> {| class="wikitable" |+ !Window Manager !Description |- |[[awesome]]<ref>[https://github.com/awesomeWM/awesome GitHub - awesomeWM/awesome: awesome window manager], awesomeWM, 2025-08-09 (Accessed: 2025-08-09)</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |[[Compiz]] |Compiz is a compositing window manager for the X Window System. |- |[[Openbox]] |A minimal and highly configurable stacking window manager written in C. |- |[[twm]]<ref>[https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml TWM], 2010-11-13 (Accessed: 2025-08-09)</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |[[IceWM]]<ref>[https://github.com/bbidulock/icewm GitHub - bbidulock/icewm: A window manager designed for speed, usability, and consistency], bbidulock, 2025-08-09 (Accessed: 2025-08-09)</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |[[i3]]<ref>[https://i3wm.org i3: improved tiling X11 window manager], Michael Stapelberg, 2025-06-12 (Accessed: 2025-08-09)</ref> |A tiling window manager for advanced users and developers. |- |[[Window Maker]]<ref>[https://github.com/window-maker/wmaker GitHub - window-maker/wmaker: Mirror of the official repository repo.or.cz/wmaker-crm.git. Do not send pull requests here, send your patches to wmaker-dev@googlegroups.com instead], window-maker, 2020-08-09 (Accessed: 2025-08-09)</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |[[XMonad]]<ref>[https://xmonad.org/ home | xmonad - the tiling window manager that rocks], xmonad, 2025-06-15 (Accessed: 2025-08-09)</ref> |Window Manager configurable via the Haskell functional programming language. |- |[[DWM]]<ref>[https://dwm.suckless.org/ DWM, a slim and resource-efficient tiling window manager that stays out of your way and is configured via the source code (written in C)], Suckless, 2025-08-09 (Accessed: 2025-08-27) </ref> |A lightweight tiling window manager written in C. |} ==References== <references /> e79fa1e5760ba63c9ae5a365b4e57fdec773fde1 0 919 3912 3889 2025-08-27T13:38:38Z Zyankali 267 Adding history about the rust rewrite. wikitext text/x-wiki {{SoftwareInfobox |image=[[File:Fish-Shell.png|thumb]] |caption=Fish-shell Logo |title=Fish |releasestatus=Maintained |lastrelease=4.0.2, 2025-04-20 |firstrelease=2.0.0, 2013-09-01 |languages=[[Rust]] |developers=Fish-shell developers |website=[https://fishshell.com/ fishshell.com] }} '''Fish''' (Friendly Interactive Shell) is a [[CLI]] with an out-of-the-box, feature-rich experience.<ref>[[wikipedia:Fish_(Unix_shell)|Fish (Unix shell)]], Wikipedia (Accessed: 2025-08-27)</ref> It offers the user features such as command suggestions, web-based configuration, colorful aesthetics<ref>[[https://fishshell.com fish shell]], Ridiculous Fish (Accessed: 2025-08-27)</ref> as well as expanded keyboard shortcuts<ref>[[https://fishshell.com/docs/current/interactive.html#shared-bindings Interactive use — fish-shell 4.0.2 documentation]], Fish-shell (Accessed: 2025-08-27)</ref>. Unlike many other commonly used shells, like Bash or Zsh, it does not adhere to the [[POSIX]] standard, which may cause Fish to throw errors if a command contains POSIX-specific syntax. == History == With the release of Fish 4.0, the project received a major rewrite, moving it from [[C++]] over to the [[Rust]] programming language. This idea was already proposed in 2023, by one of the developers via a [https://github.com/fish-shell/fish-shell/pull/9512 pull request]. While it was meant to be a humorous proposal to be read by other fish developers, it quickly gathered a lot of attention. The goal of the migration was to allow for easier [[Package Manager|packaging]]—particularly for LTS distros and older versions of macOS—gain access to better tooling, enable further multi-threading and to attract new contributors through the active Rust community.<ref>{{Cite|url=https://fishshell.com/blog/rustport/|title=Fish 4.0: The Fish Of Theseus|author=Fish-shell|year=2024|accessdate=2025-08-27}}</ref> == References == <references /> a06d98393c403f885d03cb8ddc248652802948ba 0 254 3913 3855 2025-08-27T16:29:25Z Lyon 224 Added ref to DWM's customization page wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm. == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == 435236e3f6e6efcae97b8b5ec82eb3fbc3c885bc 3914 3913 2025-08-27T16:32:10Z Lyon 224 Citing DWM customization page wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM</ref> == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == e3edabcd710c92a1fb2a005c745bfb8d915efda1 3915 3914 2025-08-27T16:34:40Z Lyon 224 Forgot to add dates on references lmao wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM] suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == c036b1b4d7c1dd5da4519bfa6634006d20fee506 3927 3915 2025-08-27T18:16:23Z Lyon 224 Fixed ref to point to the same reference wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm.<ref name=":2"> == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == d5562fac8fc0d03a193661ef1b677dbac434d6a3 3928 3927 2025-08-27T18:20:03Z Lyon 224 Fixed again (I'm learning) wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm.<ref name=":1"> == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == c12f88a01cd3e4770e340c5336550da0f4345a97 3929 3928 2025-08-27T18:21:38Z Lyon 224 Attempting fix again wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm.<ref name=":1"/> == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == cd822dfb0494f900348f1535bab834e6fc6bf35b 3930 3929 2025-08-27T18:23:50Z Lyon 224 Reverting back the the previous one because I don't know how to do it (I'll ask later) wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.5, 2024-03-19 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == a4e03ef3758d9ba586acb5aa2a5ae5b54a6f4cda 3000 927 3916 3905 2025-08-27T16:51:43Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki EWW (Elkowar’s Wacky Widgets) is a powerful tool for creating system widgets on Linux. To get started, read through the official [https://elkowar.github.io/eww/ EWW Documentation], especially the [https://elkowar.github.io/eww/widgets.html Widgets] section. This will give you a strong foundation on the different types of widgets EWW offers. == Variables == Yuck has two main variables: <code>defpoll</code> and <code>deflisten</code> === Defpoll === <syntaxhighlight lang="lisp"> (defpoll time :interval "1s" :initial "initial-value" `date +%H:%M:%S`) </syntaxhighlight> '''A polling variable is a variable which runs a provided shell-script repeatedly, in a given interval.''' === Deflisten === <syntaxhighlight lang="lisp"> (deflisten foo :initial "whatever" `tail -F /tmp/some_file`) </syntaxhighlight> '''A listening variable runs a script once, and reads its output continously. Whenever the script outputs a new line, the value will be updated to that new line.''' == File Structure == Typically, you will work with two files: <pre> eww.yuck eww.scss </pre> However, it’s better to keep things modular. A cleaner structure looks like this: <pre> eww.yuck eww.scss widgets/ ├── <name>.yuck └── <name>.yuck vars/ ├── listens.yuck └── polls.yuck windows/ └── windows.yuck </pre> To join all these files together, use the `include` directive inside your main `eww.yuck`: <syntaxhighlight lang="lisp"> (include "widgets/<name>.yuck") (include "vars/listens.yuck") (include "vars/polls.yuck") (include "windows/windows.yuck") </syntaxhighlight> == Widget Structure == Widgets in EWW follow a simple hierarchy: * Every widget must be wrapped in a <code>defwidget</code> block. * A widget usually contains one or more <code>boxes</code>. * Boxes can contain other boxes or UI elements (like labels, images, buttons, etc.). * To display widgets, they must be attached to a <code>defwindow</code>. === Example: Hello World Widget === '''Note: This example assumes you are running Wayland.''' <syntaxhighlight lang="lisp"> (defwindow hello :monitor 0 :geometry (:x "0" :y "0" :width "100px" :height "100px" :anchor "center") :exclusive false :stacking "fg" (world)) (defwidget world (box :class "hello" (label :text "hello world!"))) </syntaxhighlight> === Explanation === * <code>:monitor 0</code> → Uses your primary monitor. The widget will appear only on this monitor. * <code>:geometry</code> → Defines the position and size of the widget. * <code>:exclusive</code> → If set to <code>true</code>, the widget reserves screen space (like a panel). If <code>false</code>, it floats without affecting other windows. * <code>:stacking</code> → Controls how the widget stacks with other windows. * <code>fg</code> = Foreground (above all apps) * <code>bg</code> = Background (below apps) * <code>:class</code> → Assigns a CSS class for styling in your SCSS file. == Styling Widgets (SCSS) == The appearance of widgets is handled with SCSS. For the above example, you could add: <syntaxhighlight lang="css"> .hello { background-color: pink; border-radius: 5px; padding: 10px; font-weight: bold; } </syntaxhighlight> faa1c579aed5622e56e2fa4c1d5c09af0cac2754 3923 3916 2025-08-27T17:00:15Z Atmois 13 Atmois moved page [[Guide for eww]] to [[Guides:Using eww]]: Wrong namespace wikitext text/x-wiki EWW (Elkowar’s Wacky Widgets) is a powerful tool for creating system widgets on Linux. To get started, read through the official [https://elkowar.github.io/eww/ EWW Documentation], especially the [https://elkowar.github.io/eww/widgets.html Widgets] section. This will give you a strong foundation on the different types of widgets EWW offers. == Variables == Yuck has two main variables: <code>defpoll</code> and <code>deflisten</code> === Defpoll === <syntaxhighlight lang="lisp"> (defpoll time :interval "1s" :initial "initial-value" `date +%H:%M:%S`) </syntaxhighlight> '''A polling variable is a variable which runs a provided shell-script repeatedly, in a given interval.''' === Deflisten === <syntaxhighlight lang="lisp"> (deflisten foo :initial "whatever" `tail -F /tmp/some_file`) </syntaxhighlight> '''A listening variable runs a script once, and reads its output continously. Whenever the script outputs a new line, the value will be updated to that new line.''' == File Structure == Typically, you will work with two files: <pre> eww.yuck eww.scss </pre> However, it’s better to keep things modular. A cleaner structure looks like this: <pre> eww.yuck eww.scss widgets/ ├── <name>.yuck └── <name>.yuck vars/ ├── listens.yuck └── polls.yuck windows/ └── windows.yuck </pre> To join all these files together, use the `include` directive inside your main `eww.yuck`: <syntaxhighlight lang="lisp"> (include "widgets/<name>.yuck") (include "vars/listens.yuck") (include "vars/polls.yuck") (include "windows/windows.yuck") </syntaxhighlight> == Widget Structure == Widgets in EWW follow a simple hierarchy: * Every widget must be wrapped in a <code>defwidget</code> block. * A widget usually contains one or more <code>boxes</code>. * Boxes can contain other boxes or UI elements (like labels, images, buttons, etc.). * To display widgets, they must be attached to a <code>defwindow</code>. === Example: Hello World Widget === '''Note: This example assumes you are running Wayland.''' <syntaxhighlight lang="lisp"> (defwindow hello :monitor 0 :geometry (:x "0" :y "0" :width "100px" :height "100px" :anchor "center") :exclusive false :stacking "fg" (world)) (defwidget world (box :class "hello" (label :text "hello world!"))) </syntaxhighlight> === Explanation === * <code>:monitor 0</code> → Uses your primary monitor. The widget will appear only on this monitor. * <code>:geometry</code> → Defines the position and size of the widget. * <code>:exclusive</code> → If set to <code>true</code>, the widget reserves screen space (like a panel). If <code>false</code>, it floats without affecting other windows. * <code>:stacking</code> → Controls how the widget stacks with other windows. * <code>fg</code> = Foreground (above all apps) * <code>bg</code> = Background (below apps) * <code>:class</code> → Assigns a CSS class for styling in your SCSS file. == Styling Widgets (SCSS) == The appearance of widgets is handled with SCSS. For the above example, you could add: <syntaxhighlight lang="css"> .hello { background-color: pink; border-radius: 5px; padding: 10px; font-weight: bold; } </syntaxhighlight> faa1c579aed5622e56e2fa4c1d5c09af0cac2754 0 922 3917 3899 2025-08-27T16:51:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Application launchers]] [[Category:Linux software]] {{SoftwareInfobox |image=[[File:Vicinae-banner.png|thumb]] |caption=Vicinae Logo |title=Vicinae |releasestatus=Maintained |lastrelease=- |firstrelease=- |languages=[[C++]] [[Qt]] |developers=Vicinae Developers |website=[https://github.com/vicinaehq/vicinae vicinae.com] }} <ref> [[File:Vicinae-banner.png|thumb]] </ref> [https://github.com/vicinaehq/vicinae/ Vicinae Repository] '''Vicinae''' (pronounced ''vih-SIN-ay'') is a high-performance, native application launcher for [[Linux]], built with [[C++]] and [[Qt (software)|Qt]]. == Overview == Vicinae provides a fast, keyboard-first interface for launching applications and performing system actions. It is primarily targeted at developers and power users who prefer minimal overhead and efficient workflows. == Features == * Built-in modules for common tasks. * Extension development using fully server-side [[React (JavaScript library)|React]] and [[TypeScript]], without requiring a browser or Electron runtime. * Inspired by the popular [[Raycast]] launcher, offering a largely compatible extension API that allows reuse of many existing Raycast extensions with minimal changes. == Design == Vicinae emphasizes performance and simplicity, leveraging native technologies rather than web-based runtimes. Its architecture is designed to provide rapid response times and seamless integration with the Linux desktop environment. b200d59b3c3036eb50a59f14523df0a15506033e 3921 3917 2025-08-27T16:58:19Z Madonuko 140 fix weird wiki edit wikitext text/x-wiki [[Category:Application launchers]] [[Category:Linux software]] {{SoftwareInfobox |image=[[File:Vicinae-banner.png|thumb]] |caption=Vicinae Logo |title=Vicinae |releasestatus=Maintained |lastrelease=- |firstrelease=- |languages=[[C++]], [[Qt]] |developers=Vicinae Developers |website=[https://github.com/vicinaehq/vicinae vicinae.com] }} '''Vicinae''' (pronounced ''vih-SIN-ay'') is a high-performance, native application launcher for [[Linux]], built with [[C++]] and [[Qt (software)|Qt]]. == Overview == Vicinae provides a fast, keyboard-first interface for launching applications and performing system actions. It is primarily targeted at developers and power users who prefer minimal overhead and efficient workflows. == Features == * Built-in modules for common tasks. * Extension development using fully server-side [[React (JavaScript library)|React]] and [[TypeScript]], without requiring a browser or Electron runtime. * Inspired by the popular [[Raycast]] launcher, offering a largely compatible extension API that allows reuse of many existing Raycast extensions with minimal changes. == Design == Vicinae emphasizes performance and simplicity, leveraging native technologies rather than web-based runtimes. Its architecture is designed to provide rapid response times and seamless integration with the Linux desktop environment. d2eb7739e848774ffa1f094b731fefd08038f5a7 0 782 3918 3897 2025-08-27T16:52:06Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Widget system]] {{SoftwareInfobox |image=[[File:Eww.png|thumb]] |caption=EWW Logo |title=EWW |releasestatus=Maintained |lastrelease=0.6.0, 2024-04-21 |firstrelease=0.1.0, 2021-08-18 |languages=[[Rust]] |developers=Elkowar |website=[https://elkowar.github.io/eww elkowar.github.io] }} [https://github.com/elkowar/eww/tree/master/docs EWW Repository] '''EWW''' ('''Elkowar's Wacky Widgets''') is a standalone widget system written in [[Rust (programming language)|Rust]] by Elkowar. It allows users to implement custom widgets for any window manager. Configuration is handled through [[Yuck]] files (a lisp-like S-expression language) and SCSS/[[CSS]] stylesheets. == Overview == EWW provides a flexible framework for creating: * Status bars * Dashboards * Custom desktop widgets It is often compared to [[Waybar]] due to its use of GTK/CSS for styling. == Configuration == * '''Yuck''': a lisp-like domain-specific language used for declaring and structuring widgets. * '''CSS''': used for styling widgets; EWW leverages GTK’s CSS engine. == Documentation == Official documentation can be found here: [https://elkowar.github.io/eww/ EWW Documentation]. Official documentation for GTk's CSS engine can be found here: [https://docs.gtk.org/gtk3/css-overview.html GTK CSS Documentation] == Usage == The most common way to learn the Yuck syntax and widget setup is by studying community configuration files. 265e86bde887fbb6c650b690d1a4d1e31a35c509 3922 3918 2025-08-27T17:00:12Z Madonuko 140 fix weird wiki edit wikitext text/x-wiki [[Category:Widget system]] [[Category:Software]] {{SoftwareInfobox |image=[[File:Eww.png|thumb]] |caption=EWW Logo |title=EWW |releasestatus=Maintained |lastrelease=0.6.0, 2024-04-21 |firstrelease=0.1.0, 2021-08-18 |languages=[[Rust]] |developers=Elkowar |website=[https://elkowar.github.io/eww elkowar.github.io] }} '''EWW''' ('''Elkowar's Wacky Widgets''') is a standalone widget system written in [[Rust]] by Elkowar. It allows users to implement custom widgets for any window manager. Configuration is handled through [[Yuck]] files (a [[lisp]]-like S-expression language) and [[SCSS]]/[[CSS]] stylesheets. == Overview == EWW provides a flexible framework for creating: * Status bars * Dashboards * Custom desktop widgets It is often compared to [[Waybar]] due to its use of GTK/CSS for styling. == Configuration == * '''Yuck''': a lisp-like domain-specific language used for declaring and structuring widgets. * '''CSS''': used for styling widgets; EWW leverages GTK’s CSS engine. == Documentation == Official documentation can be found here: [https://elkowar.github.io/eww/ EWW Documentation]. Official documentation for GTk's CSS engine can be found here: [https://docs.gtk.org/gtk3/css-overview.html GTK CSS Documentation] == Usage == The most common way to learn the Yuck syntax and widget setup is by studying community configuration files. 07b88dc0a72dcb636d99fe09244390b07bad82a7 0 924 3919 3895 2025-08-27T16:52:16Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Programming languages]] [[Category:JavaScript]] '''TypeScript''' is an open-source programming language developed and maintained by [[Microsoft]]. It is a strict syntactical superset of [[JavaScript]] that adds optional static typing, making it easier to build and maintain large-scale applications. c6f0217245a91e5fdfae4dcc0063e6449f106284 3926 3919 2025-08-27T17:02:47Z Madonuko 140 stub; fix categorising wikitext text/x-wiki [[Category:Programming Languages]] {{stub}} '''TypeScript''' is an open-source programming language developed and maintained by [[Microsoft]]. It is a strict syntactical superset of [[JavaScript]] that adds optional static typing, making it easier to build and maintain large-scale applications. 2f79a0d7217fb8a13059683da250fb3004fc48f5 0 920 3920 3890 2025-08-27T16:56:39Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki '''Cascading Style Sheets (CSS)''' is a style sheet language used for describing the presentation of a document written in [[HTML]] or [[XML]] (including dialects like [[SVG]] and [[XHTML]]). CSS defines how elements should be rendered on screen, on paper, in speech, or on other media. == Overview == CSS separates the content of documents from their visual presentation, providing greater flexibility and control in the specification of presentation characteristics such as: * Layout * Colors * Fonts * Spacing == History == CSS was first proposed by [[Håkon Wium Lie]] in 1994 while working with [[Tim Berners-Lee]] at CERN. The first official CSS specification (CSS1) was published by the [[World Wide Web Consortium|W3C]] in 1996. == Syntax == A CSS rule consists of a *selector* and a *declaration block*. Example: <syntaxhighlight lang="css"> p { color: blue; font-size: 14px; } </syntaxhighlight> * `p` is the selector (applies to all <p> elements). * `color: blue;` and `font-size: 14px;` are declarations. == Versions == * '''CSS1''' – 1996, basic styling features. * '''CSS2''' – 1998, added positioning, media types, and more. * '''CSS3''' – modularized specification, ongoing development. * '''CSS4''' – not a single specification, but a term used to describe ongoing CSS modules. == Uses == * Styling web pages for different devices and screen sizes. * Enabling responsive design. * Controlling animations and transitions. == See also == * [[HTML]] * [[JavaScript]] * [[Web development]] == External links == * [https://www.w3.org/Style/CSS/ W3C CSS Homepage] * [https://developer.mozilla.org/en-US/docs/Web/CSS MDN Web Docs: CSS] c7adc50b505c4225d257367d3a8c06aaf64cbfa9 0 929 3924 2025-08-27T17:00:15Z Atmois 13 Atmois moved page [[Guide for eww]] to [[Guides:Using eww]]: Wrong namespace wikitext text/x-wiki #REDIRECT [[Guides:Using eww]] a5b000e54ab94cd92ba7eda8b9115b2a6b7e6344 8 930 3925 2025-08-27T17:00:43Z Atmois 13 add more options wikitext text/x-wiki * Common move reasons ** Misspelled title ** Wrong namespace c00b59d0a2e479f8f733210a641c99c14515a23f 6 931 3931 2025-08-27T18:34:20Z Osama 266 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 3000 914 3932 3869 2025-08-27T18:48:53Z Osama 266 wikitext text/x-wiki == Welcome to my Arch Linux Dual booting Guide == [[File:CoverEN_1.png]] = 🚀 Checking the Boot Mode = == There are two boot modes in computer systems: == === - UEFI === === - Legacy BIOS === == You can easily check the boot mode using the System Information program in Windows. == == ✅ How to check the boot mode: == === 1. In the search box, type the following command and open the program: === === <code>System Information</code> === [[File:CheckUEFI-1.png]] === 2. From the list on the left side, look for the entry: === === <code>BIOS Mode</code> === * If the value is <code>UEFI</code> → Your system is using UEFI mode. * If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. ⚠️ It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. 📌 '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' [[File:CheckUEFI-2.png]] ---- = 💿 Checking the Disk Partitioning Scheme = == There are two main types of disk partitioning schemes: == === - GPT (GUID Partition Table) === === - MBR (Master Boot Record) === == You must check the disk type before starting the installation to ensure using the correct method. == == ✅ How to check the disk partitioning scheme: == === 1. Open the <code>Disk Management</code> tool in Windows. === Right-click the Windows logo on the taskbar and select <code>Disk Management</code>. [[File:OpenDiskManagement.png]] === 2. Select the disk you want to install Arch on. === Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png]] === 3. In the (Partition Style) field, you will see the disk type: === * If it says '''GUID Partition Table''' → This is a GPT disk. * If it says '''Master Boot Record''' → This is an MBR disk. ⚠️ The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data'''!) or use a separate physical disk. 📌 '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png]] ---- = 📦 Preparing a Partition on the Disk for Arch Linux = == Before leaving the Disk Management tool, we need free space to install Arch on. == * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == ✅ How to shrink the Windows partition: == === 1. From within Disk Management, right-click the <code>C:\</code> partition. === Choose from the menu: <code>Shrink Volume</code> [[File:ShrinkPartition-1.png]] === 2. In the new window, enter the amount of space you want to shrink (in '''Megabytes'''). === Then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png]] === 3. Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: === [[File:FinalPartitionLayout-Shrinked.png]] === Or like this if you deleted another non-Windows partition: === [[File:FinalPartitionLayout-Replaced.png]] --- = 💾 Downloading the Arch Linux ISO = == You need to download the ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment. == == To download the official file, go to the following link: == === [https://archlinux.org/download/ Arch Linux (Official Download Link)] === [[File:ArchDownload.png]] --- = 🔧 Preparing the USB Drive to Boot the Live Environment = == We need a USB flash drive to install the Arch live environment, and we will use the Ventoy tool because it is the easiest and most flexible. == == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). ⚠️ '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == ✅ Steps to download Ventoy: == === 1. Download Ventoy from the official website or directly from SourceForge. === === [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] === === [https://www.ventoy.net/en/index.html Official Ventoy Website] === [[File:VentoyDownload.png]] [[File:VentoyDownload-2.png]] === 2. After downloading, you will get a compressed <code>.zip</code> file. === Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png]] == 🧪 How to install Ventoy on the USB drive == === After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. === === Make sure the program recognized the drive and shows its name in the Device field. === [[File:VentoyInstall-2.png]] == ⚙️ Customizing Ventoy settings before installation == === 1. Disable Secure Boot support: === === Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it. === [[File:VentoyInstall-3.png]] === 2. Specifying the disk partition type: === === From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT''' === > Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png]] === 3. Customizing partition configuration: === === From the '''Options''' menu → Select '''Partition Configuration''' === [[File:VentoyInstall-5.png]] === And in the first option within the new window: === === '''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK''' === [[File:VentoyInstall-6.png]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == === Press '''Install''', then agree to the warnings, and wait for the process to complete. === [[File:VentoyInstall-7.png]] === Upon successful installation, you will see a confirmation message. === === Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. === [[File:VentoyInstall-8.png]] ---- === Your USB flash drive is now ready to boot into the Arch live environment 🎉. === ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == === To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. === == ✅ The easiest way to boot without entering the BIOS == === This method doesn't even require entering the BIOS/Firmware settings: === === 1. Restart the system, but '''hold down the Shift key''' while clicking Restart. === === 2. If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. === == 🧭 In Recovery mode == === You will see a list of options, select: === === <code>Use a device</code> === === Then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). === [[File:BootArch.png]] == ❗ If the 'Use a device' option is not available == === This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. === Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == === After booting from the USB, you will see the Ventoy menu. === Select the Arch Linux ISO file from it, then press Enter twice. [[File:VentoyBoot_(Edit).png]] [[File:VentoyBoot-2_(Edit).png]] ---- == 🎯 Starting the Live Environment == === After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. === [[File:ArchBoot.png]] --- == 💬 Live Environment Font == === If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: === === <code>setfont ter-132n</code> === === The font will change from this: === [[File:ArchFontBefore.png]] === To this: === [[File:ArchFontAfter.png]] == 📝 Notes on available fonts: == === The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. === === Here are some good options: === === <code>setfont ter-132n</code> === Large and clear font, excellent for small screens. === <code>setfont ter-128n</code> === Similar but slightly smaller than <code>132n</code>. === <code>setfont ter-v32b</code> === A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. === <code>setfont lat9w-16</code> === The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. === === To check the connection, try the following command: === === <code>ping google.com</code> === === You can replace <code>google.com</code> with any other website. === === If you start seeing messages like: === <code>64 bytes from ... icmp_seq=2 time=23.3 ms</code> === ✅ The internet is working successfully! === === If you see a message like: === <code>ping: google.com: Temporary failure in name resolution</code> === ❌ It means the internet connection is not active. === === ❗ Note: === === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: === === <code>pacman -Sy</code> === === This command synchronizes the package databases. If you see the message: === <code>:: Synchronizing package databases...</code> === ✅ This means your internet is working correctly. === == 🛜 Wi-Fi users (mostly laptop users) == === In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. === === ### To start the tool: === === <code>iwctl</code> === [[File:Iwctl-1.png]] > Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. === ### 1. Find the name of your Wi-Fi device: === === <code>device list</code> === === The network device name will appear, like <code>wlan0</code>. === === ### 2. Scan for nearby networks: === === <code>station wlan0 scan</code> === === <code>station wlan0 get-networks</code> === === (Replace <code>wlan0</code> with your actual device name if different.) === === 3. Connect to the network: === === If the network is visible: === === <code>station wlan0 connect 'SSID'</code> === === If the network is hidden: === === <code>station wlan0 connect-hidden 'SSID'</code> === === (Replace <code>'SSID'</code> with your network name.) === === After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. === == ✅ Verifying internet access after connecting to Wi-Fi: == === You can use: === === <code>ping google.com</code> === === or: === === <code>pacman -Sy</code> === === If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. === ---- = 💽 Disks in Linux = == '''Disk Naming in Linux''' == === Disk naming in Linux is different from Windows. For example, you might see a path like: === <code>/dev/sda2</code> === Explanation of parts: === * <code>/dev</code>: This is the folder containing all system devices, like disks, network cards, etc. <code>dev</code> is short for '''device'''. * <code>sda</code>: This is the name of the first disk. Linux starts naming disks with letters: - <code>sda</code>: First disk - <code>sdb</code>: Second disk - <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' <code>/dev/sdXY</code> Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' <code>/dev/nvmeXnYpZ</code> Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' <code>/dev/vdXY</code> Example: <code>/dev/vda1</code> → First virtual disk, first partition. == '''Partitioning the Disk for Arch Linux Installation ⚙️''' == === You can view all connected disks using the command: <code>lsblk</code> === === This shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. === === If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. === [[File:Lsblk.png]] == '''Opening the cfdisk tool for disk partitioning 🧱''' == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. === To run it: === <code>cfdisk /dev/sda</code> Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 === And the interface will open... === ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: --- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == === As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. === == 🎮 Controlling the cfdisk tool: == === You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. === == 🛠️ To start partitioning the free space: == === Use the Down arrow until you reach Free Space. === === You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. === [[File:Cfdisk-2.png]] == 🧱 System Partitioning: == === To install the Arch system, we need at least two partitions: === ### A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. ### The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === Boot partition: We allocate a maximum of 1G for it. This is more than enough. Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition: === In the cfdisk tool, select the Free Space using the arrow keys. Choose New from the options at the bottom, and press Enter. A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter. [[File:Cfdisk-3.png]] The first partition, the boot partition, will be created. [[File:Cfdisk-4.png]] 🗂️ Creating the Root partition: After finishing creating the boot partition, we move directly to creating the second partition, the root partition. Select the remaining Free Space using the arrow keys. Choose New from the options at the bottom of the screen, then press Enter. This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png]] ### 💾 Confirming changes and writing partitions to the disk: When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png]] A warning question will appear: <code>"Are you sure you want to write the partition table to disk?"</code> If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter. [[File:Cfdisk-7.png]] With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png]] Now make sure to note the names of the two partitions you created: The first partition (size 1G) is the bootloader partition. The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: <code>lsblk</code> It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: === FAT32 for the bootloader partition === === EXT4 for the root / partition === But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: - It is the only filesystem that UEFI can read without any intermediaries. - It does not contain complex permissions or modern features that hinder UEFI. - It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. <nowiki>###</nowiki> 🧱 Why EXT4 for the root / partition? The root partition contains the entire operating system, so it needs a modern filesystem that supports: - File permissions: To determine who has the right to read, execute, or modify each file. - Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). - Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. - Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. == To format the bootloader partition, we write the following command: == === <code>mkfs.fat -F32 /dev/sda5</code> === 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === mkfs = Make File System = Create a filesystem. fat is the type of system. -F32 means we use FAT32 (not FAT16 or others). /dev/sda5 is the partition we created for boot (1GB). == ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. == [[File:Mkfs-1.png]] As for formatting the root partition, we use the following command: <code>mkfs.ext4 /dev/sda6</code> 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png]] === Now that we've finished formatting, we're ready to move on to the mounting step! === --- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: <code>mount /dev/sda6 /mnt</code> 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside /mnt, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: <code>mkdir -p /mnt/boot/efi</code> 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: <code>mount /dev/sda5 /mnt/boot/efi</code> 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. > ✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT. == If everything is good, we start moving to the system installation step! == --- > # 🏗️ Installing the System To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. === 🧰 pacman === The primary package manager in Arch Linux. Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). === 📦 pacstrap === A special tool used during installation from the live environment. Installs packages onto a specified path — usually /mnt — instead of the live system. Its function is to prepare the root partition with basic system packages, such as: - The Linux kernel * The package manager <code>pacman</code> itself! - Networking tools - System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition /mnt: <code>pacstrap /mnt base linux linux-firmware</code> === But why these specific packages?! And what does each one do? === === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: - Basic command-line tools like sh, ls, cp, mv, mkdir... - Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) - Important scripts that aid in booting === 2️⃣ linux === - This is the system kernel itself. - Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks --- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: > "What partitions do you have? Where do you want to mount each partition? And with which filesystem?" You can imagine it as a simple table containing: - Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: <code>genfstab -U /mnt >> /mnt/etc/fstab</code> ✅ Explanation of command components: <code>genfstab</code>: Short for "Generate File System Table" <code>-U</code>: Makes it use UUID identifiers instead of disk names <code>/mnt</code>: Is the root of the new system we installed >>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition == 🔒 So using UUID is the safe and reliable solution. == --- == Now we can move to the next step, which is entering the new system's root == === We can use the command: === === <code>arch-chroot /mnt</code> === === The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. === [[File:Arch-chroot.png]] == After entering the system using <code>arch-chroot</code> == === We begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. === === 📦 We use the following command: === <code>pacman -Sy sudo nano grub efibootmgr os-prober networkmanager</code> [[File:Pacman.png]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === > A tool that grants root privileges to a regular user when needed, instead of always logging in as root. * Very important for system administration after creating your own user. === ✅ <code>nano</code> === > A simple and easy text editor, ideal for any beginner. * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === > The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu). * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === > A tool that interacts with boot settings in '''UEFI''' systems. * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === > A tool that searches for other operating systems installed on the device (like Windows). * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file: === === 1️⃣ Modify the GRUB_TIMEOUT option === This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png]] === 2️⃣ Enable the os-prober tool === Scroll down to the end of the file, and you will see a line like this: <code>#GRUB_DISABLE_OS_PROBER=false</code> All you need to do is remove the # sign to activate the feature, so it becomes: <code>GRUB_DISABLE_OS_PROBER=false</code> [[File:Grub-conf_1.png]] == 🎯 This allows GRUB to detect Windows and add it to the menu automatically. == After editing, save and exit nano: Ctrl + X → then y → then Enter --- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: <code>/dev/sda1</code> We mount it with this command: <code>mount /dev/sda1 /boot/efi</code> ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png]] --- == 🧠 Generating the GRUB configuration file == === Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. === We use the following command: <code>grub-mkconfig -o /boot/grub/grub.cfg</code> Explanation of parts: <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. <code>-o</code>: means "Output", i.e., where to save the output file. <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png]] --- = 👤 Creating a new user = === After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: === <code>useradd -m -G wheel -s /bin/bash username</code> Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == <code>useradd</code>: The command responsible for creating the user. <code>-m</code>: Creates the home directory automatically in /home/username. <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png]] --- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: <code>passwd</code> Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: <code>password updated successfully</code> [[File:Passwd.png]] Then you're good. Setting the password for the new user: <code>passwd username</code> Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png]] --- = 🛡️ Enabling sudo privileges for the wheel group = === Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: === <code>EDITOR=nano visudo</code> [[File:Visudo-1.png]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png]] Scroll down until you reach this line: <code># %wheel ALL=(ALL:ALL) ALL</code> [[File:Visudobefore.png]] What do you do? Remove the # sign from the beginning, so it becomes like this: <code>%wheel ALL=(ALL:ALL) ALL</code> [[File:Visudoafter.png]] === ✨ Now the user in the wheel group can use sudo. === To save changes and exit nano: Ctrl + X then Y then Enter ---- = 🖥️ Setting the device name (Hostname) = == The hostname is what appears to you in the command line and is very useful for networks. == To set the name: <code>echo 'ArchBox' > /etc/hostname</code> [[File:Hostname.png]] Replace ArchBox with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: <code>nano /etc/hosts</code> [[File:Etchosts_before.png]] After it opens, add this line: <code>127.0.1.1 ArchBox.localdomain ArchBox</code> Replace ArchBox with the name you wrote in the previous step. [[File:Etchosts_after.png]] --- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: <code>systemctl enable NetworkManager</code> Just make sure you wrote the name correctly, with the exact case. --- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. === There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇: === = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: <code>pacman -S gnome gnome-extra gdm</code> And then enable the login manager: <code>systemctl enable gdm</code> === 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. === = 💎 Option Two: KDE Plasma + SDDM = == If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. == Execute the following command: <code>pacman -S plasma kde-applications sddm</code> Then enable the login manager: <code>systemctl enable sddm</code> === 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. === --- = 🧼 Finishing the installation and rebooting = == Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. == First, exit chroot: <code>exit</code> You will return to the live environment (USB). Now unmount the partitions we mounted: <code>umount -R /mnt</code> And finally... the awaited moment 🎉: <code>reboot</code> == After rebooting, if everything is fine, you will see the GRUB menu with: == Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png]] ----Finally :) a9ea574520be766d63aeb81464c5a29697d5a34d 14 390 3933 3716 2025-08-28T07:11:04Z PixelBrush 272 Added Entry for one of the Mascots for Fedora. Unsure about if I can upload the relevant image or not, so I'm leaving that to someone else >.>" wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[FreeBSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- | |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Tuz.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tuz]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] |[[Linux]] |} 85aa033f3642e6088640527c00b033b268033064 6 932 3934 2025-08-28T09:05:07Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 933 3935 2025-08-28T09:05:35Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 934 3936 2025-08-28T09:06:03Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 935 3937 2025-08-28T09:06:30Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 936 3938 2025-08-28T09:06:57Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 937 3939 2025-08-28T09:07:24Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 938 3940 2025-08-28T09:07:51Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 939 3941 2025-08-28T09:12:25Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 940 3942 2025-08-28T09:13:22Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 941 3943 2025-08-28T09:14:19Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 942 3944 2025-08-28T09:15:16Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 943 3945 2025-08-28T09:16:02Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 944 3946 2025-08-28T09:16:49Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 945 3947 2025-08-28T09:17:36Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 946 3948 2025-08-28T09:18:23Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 947 3949 2025-08-28T09:19:10Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 948 3950 2025-08-28T09:19:46Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 949 3951 2025-08-28T09:20:23Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 950 3952 2025-08-28T09:20:40Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 951 3953 2025-08-28T09:20:57Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 952 3954 2025-08-28T09:21:14Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 953 3955 2025-08-28T09:21:31Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 954 3956 2025-08-28T09:21:47Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 955 3957 2025-08-28T09:22:04Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 956 3958 2025-08-28T09:22:21Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 957 3959 2025-08-28T09:22:37Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 958 3960 2025-08-28T09:22:54Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 959 3961 2025-08-28T09:23:11Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 960 3962 2025-08-28T09:23:28Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 961 3963 2025-08-28T09:23:45Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 962 3964 2025-08-28T09:24:02Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 963 3965 2025-08-28T09:24:18Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 964 3966 2025-08-28T09:24:35Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 965 3967 2025-08-28T09:24:52Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 966 3968 2025-08-28T09:25:09Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 967 3969 2025-08-28T09:25:26Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 968 3970 2025-08-28T09:25:43Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 969 3971 2025-08-28T09:26:00Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 970 3972 2025-08-28T09:26:17Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 971 3973 2025-08-28T09:26:34Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 972 3974 2025-08-28T09:26:50Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 973 3975 2025-08-28T09:27:07Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 974 3976 2025-08-28T09:27:23Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 975 3977 2025-08-28T09:27:40Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 976 3978 2025-08-28T09:27:56Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 3000 914 3979 3932 2025-08-28T09:34:46Z Osama 266 wikitext text/x-wiki == Welcome to my Arch Linux Dual booting Guide == [[File:CoverEN_1.png|center|thumb|1024x1024px]] = Checking the Boot Mode = == There are two boot modes in computer systems: == === - UEFI === === - Legacy BIOS === == You can easily check the boot mode using the System Information program in Windows. == == ✅ How to check the boot mode: == === 1. In the search box, type the following command and open the program: === === <code>System Information</code> === [[File:CheckUEFI-1.png]] === 2. From the list on the left side, look for the entry: === === <code>BIOS Mode</code> === * If the value is <code>UEFI</code> → Your system is using UEFI mode. * If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. ⚠️ It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. [[File:CheckUEFI-2.png|left|frame]] 📌 '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' ---- = 💿 Checking the Disk Partitioning Scheme = == There are two main types of disk partitioning schemes: == === - GPT (GUID Partition Table) === === - MBR (Master Boot Record) === == You must check the disk type before starting the installation to ensure using the correct method. == == ✅ How to check the disk partitioning scheme: == === 1. Open the <code>Disk Management</code> tool in Windows. === Right-click the Windows logo on the taskbar and select <code>Disk Management</code>. [[File:OpenDiskManagement.png]] === 2. Select the disk you want to install Arch on. === Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png]] === 3. In the (Partition Style) field, you will see the disk type: === * If it says '''GUID Partition Table''' → This is a GPT disk. * If it says '''Master Boot Record''' → This is an MBR disk. ⚠️ The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data'''!) or use a separate physical disk. 📌 '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png]] ---- = 📦 Preparing a Partition on the Disk for Arch Linux = == Before leaving the Disk Management tool, we need free space to install Arch on. == * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == ✅ How to shrink the Windows partition: == === 1. From within Disk Management, right-click the <code>C:\</code> partition. === Choose from the menu: <code>Shrink Volume</code> [[File:ShrinkPartition-1.png]] === 2. In the new window, enter the amount of space you want to shrink (in '''Megabytes'''). === Then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png]] === 3. Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: === [[File:FinalPartitionLayout-Shrinked.png]] === Or like this if you deleted another non-Windows partition: === [[File:FinalPartitionLayout-Replaced.png]] --- = 💾 Downloading the Arch Linux ISO = == You need to download the ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment. == == To download the official file, go to the following link: == === [https://archlinux.org/download/ Arch Linux (Official Download Link)] === [[File:ArchDownload.png]] --- = 🔧 Preparing the USB Drive to Boot the Live Environment = == We need a USB flash drive to install the Arch live environment, and we will use the Ventoy tool because it is the easiest and most flexible. == == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). ⚠️ '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == ✅ Steps to download Ventoy: == === 1. Download Ventoy from the official website or directly from SourceForge. === === [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] === === [https://www.ventoy.net/en/index.html Official Ventoy Website] === [[File:VentoyDownload.png]] [[File:VentoyDownload-2.png]] === 2. After downloading, you will get a compressed <code>.zip</code> file. === Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png]] == 🧪 How to install Ventoy on the USB drive == === After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. === === Make sure the program recognized the drive and shows its name in the Device field. === [[File:VentoyInstall-2.png]] == ⚙️ Customizing Ventoy settings before installation == === 1. Disable Secure Boot support: === === Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it. === [[File:VentoyInstall-3.png]] === 2. Specifying the disk partition type: === === From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT''' === > Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png]] === 3. Customizing partition configuration: === === From the '''Options''' menu → Select '''Partition Configuration''' === [[File:VentoyInstall-5.png]] === And in the first option within the new window: === === '''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK''' === [[File:VentoyInstall-6.png]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == === Press '''Install''', then agree to the warnings, and wait for the process to complete. === [[File:VentoyInstall-7.png]] === Upon successful installation, you will see a confirmation message. === === Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. === [[File:VentoyInstall-8.png]] ---- === Your USB flash drive is now ready to boot into the Arch live environment 🎉. === ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == === To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. === == ✅ The easiest way to boot without entering the BIOS == === This method doesn't even require entering the BIOS/Firmware settings: === === 1. Restart the system, but '''hold down the Shift key''' while clicking Restart. === === 2. If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. === == 🧭 In Recovery mode == === You will see a list of options, select: === === <code>Use a device</code> === === Then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). === [[File:BootArch.png]] == ❗ If the 'Use a device' option is not available == === This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. === Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == === After booting from the USB, you will see the Ventoy menu. === Select the Arch Linux ISO file from it, then press Enter twice. [[File:VentoyBoot_(Edit).png]] [[File:VentoyBoot-2_(Edit).png]] ---- == 🎯 Starting the Live Environment == === After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. === [[File:ArchBoot.png]] --- == 💬 Live Environment Font == === If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: === === <code>setfont ter-132n</code> === === The font will change from this: === [[File:ArchFontBefore.png]] === To this: === [[File:ArchFontAfter.png]] == 📝 Notes on available fonts: == === The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. === === Here are some good options: === === <code>setfont ter-132n</code> === Large and clear font, excellent for small screens. === <code>setfont ter-128n</code> === Similar but slightly smaller than <code>132n</code>. === <code>setfont ter-v32b</code> === A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. === <code>setfont lat9w-16</code> === The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. === === To check the connection, try the following command: === === <code>ping google.com</code> === === You can replace <code>google.com</code> with any other website. === === If you start seeing messages like: === <code>64 bytes from ... icmp_seq=2 time=23.3 ms</code> === ✅ The internet is working successfully! === === If you see a message like: === <code>ping: google.com: Temporary failure in name resolution</code> === ❌ It means the internet connection is not active. === === ❗ Note: === === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: === === <code>pacman -Sy</code> === === This command synchronizes the package databases. If you see the message: === <code>:: Synchronizing package databases...</code> === ✅ This means your internet is working correctly. === == 🛜 Wi-Fi users (mostly laptop users) == === In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. === === ### To start the tool: === === <code>iwctl</code> === [[File:Iwctl-1.png]] > Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. === ### 1. Find the name of your Wi-Fi device: === === <code>device list</code> === === The network device name will appear, like <code>wlan0</code>. === === ### 2. Scan for nearby networks: === === <code>station wlan0 scan</code> === === <code>station wlan0 get-networks</code> === === (Replace <code>wlan0</code> with your actual device name if different.) === === 3. Connect to the network: === === If the network is visible: === === <code>station wlan0 connect 'SSID'</code> === === If the network is hidden: === === <code>station wlan0 connect-hidden 'SSID'</code> === === (Replace <code>'SSID'</code> with your network name.) === === After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. === == ✅ Verifying internet access after connecting to Wi-Fi: == === You can use: === === <code>ping google.com</code> === === or: === === <code>pacman -Sy</code> === === If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. === ---- = 💽 Disks in Linux = == '''Disk Naming in Linux''' == === Disk naming in Linux is different from Windows. For example, you might see a path like: === <code>/dev/sda2</code> === Explanation of parts: === * <code>/dev</code>: This is the folder containing all system devices, like disks, network cards, etc. <code>dev</code> is short for '''device'''. * <code>sda</code>: This is the name of the first disk. Linux starts naming disks with letters: - <code>sda</code>: First disk - <code>sdb</code>: Second disk - <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' <code>/dev/sdXY</code> Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' <code>/dev/nvmeXnYpZ</code> Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' <code>/dev/vdXY</code> Example: <code>/dev/vda1</code> → First virtual disk, first partition. == '''Partitioning the Disk for Arch Linux Installation ⚙️''' == === You can view all connected disks using the command: <code>lsblk</code> === === This shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. === === If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. === [[File:Lsblk.png]] == '''Opening the cfdisk tool for disk partitioning 🧱''' == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. === To run it: === <code>cfdisk /dev/sda</code> Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 === And the interface will open... === ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: --- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == === As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. === == 🎮 Controlling the cfdisk tool: == === You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. === == 🛠️ To start partitioning the free space: == === Use the Down arrow until you reach Free Space. === === You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. === [[File:Cfdisk-2.png]] == 🧱 System Partitioning: == === To install the Arch system, we need at least two partitions: === ### A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. ### The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === Boot partition: We allocate a maximum of 1G for it. This is more than enough. Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition: === In the cfdisk tool, select the Free Space using the arrow keys. Choose New from the options at the bottom, and press Enter. A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter. [[File:Cfdisk-3.png]] The first partition, the boot partition, will be created. [[File:Cfdisk-4.png]] 🗂️ Creating the Root partition: After finishing creating the boot partition, we move directly to creating the second partition, the root partition. Select the remaining Free Space using the arrow keys. Choose New from the options at the bottom of the screen, then press Enter. This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png]] ### 💾 Confirming changes and writing partitions to the disk: When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png]] A warning question will appear: <code>"Are you sure you want to write the partition table to disk?"</code> If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter. [[File:Cfdisk-7.png]] With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png]] Now make sure to note the names of the two partitions you created: The first partition (size 1G) is the bootloader partition. The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: <code>lsblk</code> It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: === FAT32 for the bootloader partition === === EXT4 for the root / partition === But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: - It is the only filesystem that UEFI can read without any intermediaries. - It does not contain complex permissions or modern features that hinder UEFI. - It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. <nowiki>###</nowiki> 🧱 Why EXT4 for the root / partition? The root partition contains the entire operating system, so it needs a modern filesystem that supports: - File permissions: To determine who has the right to read, execute, or modify each file. - Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). - Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. - Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. == To format the bootloader partition, we write the following command: == === <code>mkfs.fat -F32 /dev/sda5</code> === 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === mkfs = Make File System = Create a filesystem. fat is the type of system. -F32 means we use FAT32 (not FAT16 or others). /dev/sda5 is the partition we created for boot (1GB). == ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. == [[File:Mkfs-1.png]] As for formatting the root partition, we use the following command: <code>mkfs.ext4 /dev/sda6</code> 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png]] === Now that we've finished formatting, we're ready to move on to the mounting step! === --- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: <code>mount /dev/sda6 /mnt</code> 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside /mnt, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: <code>mkdir -p /mnt/boot/efi</code> 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: <code>mount /dev/sda5 /mnt/boot/efi</code> 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. > ✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT. == If everything is good, we start moving to the system installation step! == --- > # 🏗️ Installing the System To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. === 🧰 pacman === The primary package manager in Arch Linux. Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). === 📦 pacstrap === A special tool used during installation from the live environment. Installs packages onto a specified path — usually /mnt — instead of the live system. Its function is to prepare the root partition with basic system packages, such as: - The Linux kernel * The package manager <code>pacman</code> itself! - Networking tools - System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition /mnt: <code>pacstrap /mnt base linux linux-firmware</code> === But why these specific packages?! And what does each one do? === === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: - Basic command-line tools like sh, ls, cp, mv, mkdir... - Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) - Important scripts that aid in booting === 2️⃣ linux === - This is the system kernel itself. - Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks --- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: > "What partitions do you have? Where do you want to mount each partition? And with which filesystem?" You can imagine it as a simple table containing: - Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: <code>genfstab -U /mnt >> /mnt/etc/fstab</code> ✅ Explanation of command components: <code>genfstab</code>: Short for "Generate File System Table" <code>-U</code>: Makes it use UUID identifiers instead of disk names <code>/mnt</code>: Is the root of the new system we installed >>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition == 🔒 So using UUID is the safe and reliable solution. == --- == Now we can move to the next step, which is entering the new system's root == === We can use the command: === === <code>arch-chroot /mnt</code> === === The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. === [[File:Arch-chroot.png]] == After entering the system using <code>arch-chroot</code> == === We begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. === === 📦 We use the following command: === <code>pacman -Sy sudo nano grub efibootmgr os-prober networkmanager</code> [[File:Pacman.png]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === > A tool that grants root privileges to a regular user when needed, instead of always logging in as root. * Very important for system administration after creating your own user. === ✅ <code>nano</code> === > A simple and easy text editor, ideal for any beginner. * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === > The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu). * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === > A tool that interacts with boot settings in '''UEFI''' systems. * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === > A tool that searches for other operating systems installed on the device (like Windows). * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file: === === 1️⃣ Modify the GRUB_TIMEOUT option === This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png]] === 2️⃣ Enable the os-prober tool === Scroll down to the end of the file, and you will see a line like this: <code>#GRUB_DISABLE_OS_PROBER=false</code> All you need to do is remove the # sign to activate the feature, so it becomes: <code>GRUB_DISABLE_OS_PROBER=false</code> [[File:Grub-conf_1.png]] == 🎯 This allows GRUB to detect Windows and add it to the menu automatically. == After editing, save and exit nano: Ctrl + X → then y → then Enter --- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: <code>/dev/sda1</code> We mount it with this command: <code>mount /dev/sda1 /boot/efi</code> ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png]] --- == 🧠 Generating the GRUB configuration file == === Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. === We use the following command: <code>grub-mkconfig -o /boot/grub/grub.cfg</code> Explanation of parts: <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. <code>-o</code>: means "Output", i.e., where to save the output file. <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png]] --- = 👤 Creating a new user = === After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: === <code>useradd -m -G wheel -s /bin/bash username</code> Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == <code>useradd</code>: The command responsible for creating the user. <code>-m</code>: Creates the home directory automatically in /home/username. <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png]] --- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: <code>passwd</code> Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: <code>password updated successfully</code> [[File:Passwd.png]] Then you're good. Setting the password for the new user: <code>passwd username</code> Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png]] --- = 🛡️ Enabling sudo privileges for the wheel group = === Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: === <code>EDITOR=nano visudo</code> [[File:Visudo-1.png]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png]] Scroll down until you reach this line: <code># %wheel ALL=(ALL:ALL) ALL</code> [[File:Visudobefore.png]] What do you do? Remove the # sign from the beginning, so it becomes like this: <code>%wheel ALL=(ALL:ALL) ALL</code> [[File:Visudoafter.png]] === ✨ Now the user in the wheel group can use sudo. === To save changes and exit nano: Ctrl + X then Y then Enter ---- = 🖥️ Setting the device name (Hostname) = == The hostname is what appears to you in the command line and is very useful for networks. == To set the name: <code>echo 'ArchBox' > /etc/hostname</code> [[File:Hostname.png]] Replace ArchBox with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: <code>nano /etc/hosts</code> [[File:Etchosts_before.png]] After it opens, add this line: <code>127.0.1.1 ArchBox.localdomain ArchBox</code> Replace ArchBox with the name you wrote in the previous step. [[File:Etchosts_after.png]] --- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: <code>systemctl enable NetworkManager</code> Just make sure you wrote the name correctly, with the exact case. --- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. === There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇: === = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: <code>pacman -S gnome gnome-extra gdm</code> And then enable the login manager: <code>systemctl enable gdm</code> === 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. === = 💎 Option Two: KDE Plasma + SDDM = == If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. == Execute the following command: <code>pacman -S plasma kde-applications sddm</code> Then enable the login manager: <code>systemctl enable sddm</code> === 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. === --- = 🧼 Finishing the installation and rebooting = == Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. == First, exit chroot: <code>exit</code> You will return to the live environment (USB). Now unmount the partitions we mounted: <code>umount -R /mnt</code> And finally... the awaited moment 🎉: <code>reboot</code> == After rebooting, if everything is fine, you will see the GRUB menu with: == Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png]] ----Finally :) 304dd8d117dd141b70ac76f906af3b4b90b3a71c 3990 3979 2025-08-28T09:45:48Z Osama 266 nothin wikitext text/x-wiki == Welcome to my Arch Linux Dual booting Guide == [[File:CoverEN_1.png|center|thumb|1024x1024px]] = Checking the Boot Mode = == There are two boot modes in computer systems: == === - UEFI === === - Legacy BIOS === == You can easily check the boot mode using the System Information program in Windows. == == ✅ How to check the boot mode: == === 1. In the search box, type the following command and open the program: === === <code>System Information</code> === [[File:CheckUEFI-1.png]] === 2. From the list on the left side, look for the entry: === === <code>BIOS Mode</code> === * If the value is <code>UEFI</code> → Your system is using UEFI mode. * If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. ⚠️ It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. [[File:CheckUEFI-2.png|left|frame]] 📌 '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' ---- = 💿 Checking the Disk Partitioning Scheme = == There are two main types of disk partitioning schemes: == === - GPT (GUID Partition Table) === === - MBR (Master Boot Record) === == You must check the disk type before starting the installation to ensure using the correct method. == == ✅ How to check the disk partitioning scheme: == === 1. Open the <code>Disk Management</code> tool in Windows. === [[File:OpenDiskManagement.png|left|frame]] Right-click the Windows logo on the taskbar and select <code>Disk Management</code>. === 2. Select the disk you want to install Arch on. === Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png]] === 3. In the (Partition Style) field, you will see the disk type: === * If it says '''GUID Partition Table''' → This is a GPT disk. * If it says '''Master Boot Record''' → This is an MBR disk. ⚠️ The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data'''!) or use a separate physical disk. 📌 '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png]] ---- = 📦 Preparing a Partition on the Disk for Arch Linux = == Before leaving the Disk Management tool, we need free space to install Arch on. == * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == ✅ How to shrink the Windows partition: == === 1. From within Disk Management, right-click the <code>C:\</code> partition. === Choose from the menu: <code>Shrink Volume</code> [[File:ShrinkPartition-1.png]] === 2. In the new window, enter the amount of space you want to shrink (in '''Megabytes'''). === Then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png]] === 3. Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: === [[File:FinalPartitionLayout-Shrinked.png]] === Or like this if you deleted another non-Windows partition: === [[File:FinalPartitionLayout-Replaced.png]] --- = 💾 Downloading the Arch Linux ISO = == You need to download the ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment. == == To download the official file, go to the following link: == === [https://archlinux.org/download/ Arch Linux (Official Download Link)] === [[File:ArchDownload.png]] --- = 🔧 Preparing the USB Drive to Boot the Live Environment = == We need a USB flash drive to install the Arch live environment, and we will use the Ventoy tool because it is the easiest and most flexible. == == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). ⚠️ '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == ✅ Steps to download Ventoy: == === 1. Download Ventoy from the official website or directly from SourceForge. === === [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] === === [https://www.ventoy.net/en/index.html Official Ventoy Website] === [[File:VentoyDownload.png]] [[File:VentoyDownload-2.png]] === 2. After downloading, you will get a compressed <code>.zip</code> file. === Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png]] == 🧪 How to install Ventoy on the USB drive == === After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. === === Make sure the program recognized the drive and shows its name in the Device field. === [[File:VentoyInstall-2.png]] == ⚙️ Customizing Ventoy settings before installation == === 1. Disable Secure Boot support: === === Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it. === [[File:VentoyInstall-3.png]] === 2. Specifying the disk partition type: === === From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT''' === > Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png]] === 3. Customizing partition configuration: === === From the '''Options''' menu → Select '''Partition Configuration''' === [[File:VentoyInstall-5.png]] === And in the first option within the new window: === === '''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK''' === [[File:VentoyInstall-6.png]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == === Press '''Install''', then agree to the warnings, and wait for the process to complete. === [[File:VentoyInstall-7.png]] === Upon successful installation, you will see a confirmation message. === === Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. === [[File:VentoyInstall-8.png]] ---- === Your USB flash drive is now ready to boot into the Arch live environment 🎉. === ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == === To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. === == ✅ The easiest way to boot without entering the BIOS == === This method doesn't even require entering the BIOS/Firmware settings: === === 1. Restart the system, but '''hold down the Shift key''' while clicking Restart. === === 2. If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. === == 🧭 In Recovery mode == === You will see a list of options, select: === === <code>Use a device</code> === === Then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). === [[File:BootArch.png]] == ❗ If the 'Use a device' option is not available == === This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. === Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == === After booting from the USB, you will see the Ventoy menu. === Select the Arch Linux ISO file from it, then press Enter twice. [[File:VentoyBoot_(Edit).png]] [[File:VentoyBoot-2_(Edit).png]] ---- == 🎯 Starting the Live Environment == === After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. === [[File:ArchBoot.png]] --- == 💬 Live Environment Font == === If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: === === <code>setfont ter-132n</code> === === The font will change from this: === [[File:ArchFontBefore.png]] === To this: === [[File:ArchFontAfter.png]] == 📝 Notes on available fonts: == === The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. === === Here are some good options: === === <code>setfont ter-132n</code> === Large and clear font, excellent for small screens. === <code>setfont ter-128n</code> === Similar but slightly smaller than <code>132n</code>. === <code>setfont ter-v32b</code> === A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. === <code>setfont lat9w-16</code> === The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. === === To check the connection, try the following command: === === <code>ping google.com</code> === === You can replace <code>google.com</code> with any other website. === === If you start seeing messages like: === <code>64 bytes from ... icmp_seq=2 time=23.3 ms</code> === ✅ The internet is working successfully! === === If you see a message like: === <code>ping: google.com: Temporary failure in name resolution</code> === ❌ It means the internet connection is not active. === === ❗ Note: === === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: === === <code>pacman -Sy</code> === === This command synchronizes the package databases. If you see the message: === <code>:: Synchronizing package databases...</code> === ✅ This means your internet is working correctly. === == 🛜 Wi-Fi users (mostly laptop users) == === In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. === === ### To start the tool: === === <code>iwctl</code> === [[File:Iwctl-1.png]] > Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. === ### 1. Find the name of your Wi-Fi device: === === <code>device list</code> === === The network device name will appear, like <code>wlan0</code>. === === ### 2. Scan for nearby networks: === === <code>station wlan0 scan</code> === === <code>station wlan0 get-networks</code> === === (Replace <code>wlan0</code> with your actual device name if different.) === === 3. Connect to the network: === === If the network is visible: === === <code>station wlan0 connect 'SSID'</code> === === If the network is hidden: === === <code>station wlan0 connect-hidden 'SSID'</code> === === (Replace <code>'SSID'</code> with your network name.) === === After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. === == ✅ Verifying internet access after connecting to Wi-Fi: == === You can use: === === <code>ping google.com</code> === === or: === === <code>pacman -Sy</code> === === If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. === ---- = 💽 Disks in Linux = == '''Disk Naming in Linux''' == === Disk naming in Linux is different from Windows. For example, you might see a path like: === <code>/dev/sda2</code> === Explanation of parts: === * <code>/dev</code>: This is the folder containing all system devices, like disks, network cards, etc. <code>dev</code> is short for '''device'''. * <code>sda</code>: This is the name of the first disk. Linux starts naming disks with letters: - <code>sda</code>: First disk - <code>sdb</code>: Second disk - <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' <code>/dev/sdXY</code> Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' <code>/dev/nvmeXnYpZ</code> Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' <code>/dev/vdXY</code> Example: <code>/dev/vda1</code> → First virtual disk, first partition. == '''Partitioning the Disk for Arch Linux Installation ⚙️''' == === You can view all connected disks using the command: <code>lsblk</code> === === This shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. === === If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. === [[File:Lsblk.png]] == '''Opening the cfdisk tool for disk partitioning 🧱''' == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. === To run it: === <code>cfdisk /dev/sda</code> Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 === And the interface will open... === ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: --- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == === As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. === == 🎮 Controlling the cfdisk tool: == === You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. === == 🛠️ To start partitioning the free space: == === Use the Down arrow until you reach Free Space. === === You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. === [[File:Cfdisk-2.png]] == 🧱 System Partitioning: == === To install the Arch system, we need at least two partitions: === ### A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. ### The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === Boot partition: We allocate a maximum of 1G for it. This is more than enough. Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition: === In the cfdisk tool, select the Free Space using the arrow keys. Choose New from the options at the bottom, and press Enter. A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter. [[File:Cfdisk-3.png]] The first partition, the boot partition, will be created. [[File:Cfdisk-4.png]] 🗂️ Creating the Root partition: After finishing creating the boot partition, we move directly to creating the second partition, the root partition. Select the remaining Free Space using the arrow keys. Choose New from the options at the bottom of the screen, then press Enter. This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png]] ### 💾 Confirming changes and writing partitions to the disk: When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png]] A warning question will appear: <code>"Are you sure you want to write the partition table to disk?"</code> If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter. [[File:Cfdisk-7.png]] With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png]] Now make sure to note the names of the two partitions you created: The first partition (size 1G) is the bootloader partition. The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: <code>lsblk</code> It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: === FAT32 for the bootloader partition === === EXT4 for the root / partition === But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: - It is the only filesystem that UEFI can read without any intermediaries. - It does not contain complex permissions or modern features that hinder UEFI. - It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. <nowiki>###</nowiki> 🧱 Why EXT4 for the root / partition? The root partition contains the entire operating system, so it needs a modern filesystem that supports: - File permissions: To determine who has the right to read, execute, or modify each file. - Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). - Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. - Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. == To format the bootloader partition, we write the following command: == === <code>mkfs.fat -F32 /dev/sda5</code> === 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === mkfs = Make File System = Create a filesystem. fat is the type of system. -F32 means we use FAT32 (not FAT16 or others). /dev/sda5 is the partition we created for boot (1GB). == ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. == [[File:Mkfs-1.png]] As for formatting the root partition, we use the following command: <code>mkfs.ext4 /dev/sda6</code> 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png]] === Now that we've finished formatting, we're ready to move on to the mounting step! === --- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: <code>mount /dev/sda6 /mnt</code> 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside /mnt, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: <code>mkdir -p /mnt/boot/efi</code> 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: <code>mount /dev/sda5 /mnt/boot/efi</code> 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. > ✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT. == If everything is good, we start moving to the system installation step! == --- > # 🏗️ Installing the System To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. === 🧰 pacman === The primary package manager in Arch Linux. Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). === 📦 pacstrap === A special tool used during installation from the live environment. Installs packages onto a specified path — usually /mnt — instead of the live system. Its function is to prepare the root partition with basic system packages, such as: - The Linux kernel * The package manager <code>pacman</code> itself! - Networking tools - System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition /mnt: <code>pacstrap /mnt base linux linux-firmware</code> === But why these specific packages?! And what does each one do? === === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: - Basic command-line tools like sh, ls, cp, mv, mkdir... - Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) - Important scripts that aid in booting === 2️⃣ linux === - This is the system kernel itself. - Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks --- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: > "What partitions do you have? Where do you want to mount each partition? And with which filesystem?" You can imagine it as a simple table containing: - Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: <code>genfstab -U /mnt >> /mnt/etc/fstab</code> ✅ Explanation of command components: <code>genfstab</code>: Short for "Generate File System Table" <code>-U</code>: Makes it use UUID identifiers instead of disk names <code>/mnt</code>: Is the root of the new system we installed >>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition == 🔒 So using UUID is the safe and reliable solution. == --- == Now we can move to the next step, which is entering the new system's root == === We can use the command: === === <code>arch-chroot /mnt</code> === === The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. === [[File:Arch-chroot.png]] == After entering the system using <code>arch-chroot</code> == === We begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. === === 📦 We use the following command: === <code>pacman -Sy sudo nano grub efibootmgr os-prober networkmanager</code> [[File:Pacman.png]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === > A tool that grants root privileges to a regular user when needed, instead of always logging in as root. * Very important for system administration after creating your own user. === ✅ <code>nano</code> === > A simple and easy text editor, ideal for any beginner. * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === > The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu). * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === > A tool that interacts with boot settings in '''UEFI''' systems. * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === > A tool that searches for other operating systems installed on the device (like Windows). * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file: === === 1️⃣ Modify the GRUB_TIMEOUT option === This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png]] === 2️⃣ Enable the os-prober tool === Scroll down to the end of the file, and you will see a line like this: <code>#GRUB_DISABLE_OS_PROBER=false</code> All you need to do is remove the # sign to activate the feature, so it becomes: <code>GRUB_DISABLE_OS_PROBER=false</code> [[File:Grub-conf_1.png]] == 🎯 This allows GRUB to detect Windows and add it to the menu automatically. == After editing, save and exit nano: Ctrl + X → then y → then Enter --- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: <code>/dev/sda1</code> We mount it with this command: <code>mount /dev/sda1 /boot/efi</code> ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png]] --- == 🧠 Generating the GRUB configuration file == === Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. === We use the following command: <code>grub-mkconfig -o /boot/grub/grub.cfg</code> Explanation of parts: <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. <code>-o</code>: means "Output", i.e., where to save the output file. <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png]] --- = 👤 Creating a new user = === After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: === <code>useradd -m -G wheel -s /bin/bash username</code> Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == <code>useradd</code>: The command responsible for creating the user. <code>-m</code>: Creates the home directory automatically in /home/username. <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png]] --- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: <code>passwd</code> Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: <code>password updated successfully</code> [[File:Passwd.png]] Then you're good. Setting the password for the new user: <code>passwd username</code> Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png]] --- = 🛡️ Enabling sudo privileges for the wheel group = === Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: === <code>EDITOR=nano visudo</code> [[File:Visudo-1.png]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png]] Scroll down until you reach this line: <code># %wheel ALL=(ALL:ALL) ALL</code> [[File:Visudobefore.png]] What do you do? Remove the # sign from the beginning, so it becomes like this: <code>%wheel ALL=(ALL:ALL) ALL</code> [[File:Visudoafter.png]] === ✨ Now the user in the wheel group can use sudo. === To save changes and exit nano: Ctrl + X then Y then Enter ---- = 🖥️ Setting the device name (Hostname) = == The hostname is what appears to you in the command line and is very useful for networks. == To set the name: <code>echo 'ArchBox' > /etc/hostname</code> [[File:Hostname.png]] Replace ArchBox with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: <code>nano /etc/hosts</code> [[File:Etchosts_before.png]] After it opens, add this line: <code>127.0.1.1 ArchBox.localdomain ArchBox</code> Replace ArchBox with the name you wrote in the previous step. [[File:Etchosts_after.png]] --- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: <code>systemctl enable NetworkManager</code> Just make sure you wrote the name correctly, with the exact case. --- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. === There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇: === = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: <code>pacman -S gnome gnome-extra gdm</code> And then enable the login manager: <code>systemctl enable gdm</code> === 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. === = 💎 Option Two: KDE Plasma + SDDM = == If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. == Execute the following command: <code>pacman -S plasma kde-applications sddm</code> Then enable the login manager: <code>systemctl enable sddm</code> === 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. === --- = 🧼 Finishing the installation and rebooting = == Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. == First, exit chroot: <code>exit</code> You will return to the live environment (USB). Now unmount the partitions we mounted: <code>umount -R /mnt</code> And finally... the awaited moment 🎉: <code>reboot</code> == After rebooting, if everything is fine, you will see the GRUB menu with: == Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png]] ----Finally :) 4649caa3fc83c52708d56dfde0ec3c2f5703388d 3995 3990 2025-08-28T09:57:27Z Osama 266 With Images :D wikitext text/x-wiki == Welcome to my Arch Linux Dual booting Guide == [[File:CoverEN_1.png|center|thumb|1024x1024px]] = Checking the Boot Mode = == There are two boot modes in computer systems: == === - UEFI === === - Legacy BIOS === == You can easily check the boot mode using the System Information program in Windows. == == ✅ How to check the boot mode: == === 1. In the search box, type the following command and open the program: === === <code>System Information</code> === [[File:CheckUEFI-1.png]] === 2. From the list on the left side, look for the entry: === === <code>BIOS Mode</code> === * If the value is <code>UEFI</code> → Your system is using UEFI mode. * If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. ⚠️ It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. [[File:CheckUEFI-2.png|frameless|1110x1110px]] 📌 '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' ---- = 💿 Checking the Disk Partitioning Scheme = == There are two main types of disk partitioning schemes: == === - GPT (GUID Partition Table) === === - MBR (Master Boot Record) === == You must check the disk type before starting the installation to ensure using the correct method. == == ✅ How to check the disk partitioning scheme: == === 1. Open the <code>Disk Management</code> tool in Windows. === Right-click the Windows logo on the taskbar and select <code>Disk Management</code>. [[File:OpenDiskManagement.png|center|thumb|1054x1054px]] === 2. Select the disk you want to install Arch on. === Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png]] === 3. In the (Partition Style) field, you will see the disk type: === * If it says '''GUID Partition Table''' → This is a GPT disk. * If it says '''Master Boot Record''' → This is an MBR disk. ⚠️ The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data'''!) or use a separate physical disk. 📌 '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png]] ---- = 📦 Preparing a Partition on the Disk for Arch Linux = == Before leaving the Disk Management tool, we need free space to install Arch on. == * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == ✅ How to shrink the Windows partition: == === 1. From within Disk Management, right-click the <code>C:\</code> partition. === Choose from the menu: <code>Shrink Volume</code> [[File:ShrinkPartition-1.png|1108x1108px]] === 2. In the new window, enter the amount of space you want to shrink (in '''Megabytes'''). === Then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png]] === 3. Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: === [[File:FinalPartitionLayout-Shrinked.png|1121x1121px]] === Or like this if you deleted another non-Windows partition: === [[File:FinalPartitionLayout-Replaced.png|1113x1113px]] --- = 💾 Downloading the Arch Linux ISO = == You need to download the ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment. == == To download the official file, go to the following link: == === [https://archlinux.org/download/ Arch Linux (Official Download Link)] === [[File:ArchDownload.png|1145x1145px]] --- = 🔧 Preparing the USB Drive to Boot the Live Environment = == We need a USB flash drive to install the Arch live environment, and we will use the Ventoy tool because it is the easiest and most flexible. == == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). ⚠️ '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == ✅ Steps to download Ventoy: == === 1. Download Ventoy from the official website or directly from SourceForge. === === [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] === === [https://www.ventoy.net/en/index.html Official Ventoy Website] === [[File:VentoyDownload.png|1349x1349px]] [[File:VentoyDownload-2.png]] === 2. After downloading, you will get a compressed <code>.zip</code> file. === Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png]] == 🧪 How to install Ventoy on the USB drive == === After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. === === Make sure the program recognized the drive and shows its name in the Device field. === [[File:VentoyInstall-2.png]] == ⚙️ Customizing Ventoy settings before installation == === 1. Disable Secure Boot support: === === Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it. === [[File:VentoyInstall-3.png]] === 2. Specifying the disk partition type: === === From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT''' === > Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png]] === 3. Customizing partition configuration: === === From the '''Options''' menu → Select '''Partition Configuration''' === [[File:VentoyInstall-5.png]] === And in the first option within the new window: === === '''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK''' === [[File:VentoyInstall-6.png]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == === Press '''Install''', then agree to the warnings, and wait for the process to complete. === [[File:VentoyInstall-7.png]] === Upon successful installation, you will see a confirmation message. === === Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. === [[File:VentoyInstall-8.png]] ---- === Your USB flash drive is now ready to boot into the Arch live environment 🎉. === ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == === To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. === == ✅ The easiest way to boot without entering the BIOS == === This method doesn't even require entering the BIOS/Firmware settings: === === 1. Restart the system, but '''hold down the Shift key''' while clicking Restart. === === 2. If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. === == 🧭 In Recovery mode == === You will see a list of options, select: === === <code>Use a device</code> === === Then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). === [[File:BootArch.png|1398x1398px]] == ❗ If the 'Use a device' option is not available == === This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. === Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == === After booting from the USB, you will see the Ventoy menu. === Select the Arch Linux ISO file from it, then press Enter twice. ---- == 🎯 Starting the Live Environment == === After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. === [[File:ArchBoot.png]] --- == 💬 Live Environment Font == === If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: === === <code>setfont ter-132n</code> === === The font will change from this: === [[File:ArchFontBefore.png|1397x1397px]] === To this: === [[File:ArchFontAfter.png|1357x1357px]] == 📝 Notes on available fonts: == === The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. === === Here are some good options: === === <code>setfont ter-132n</code> === Large and clear font, excellent for small screens. === <code>setfont ter-128n</code> === Similar but slightly smaller than <code>132n</code>. === <code>setfont ter-v32b</code> === A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. === <code>setfont lat9w-16</code> === The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. === === To check the connection, try the following command: === === <code>ping google.com</code> === === You can replace <code>google.com</code> with any other website. === === If you start seeing messages like: === <code>64 bytes from ... icmp_seq=2 time=23.3 ms</code> === ✅ The internet is working successfully! === === If you see a message like: === <code>ping: google.com: Temporary failure in name resolution</code> === ❌ It means the internet connection is not active. === === ❗ Note: === === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: === === <code>pacman -Sy</code> === === This command synchronizes the package databases. If you see the message: === <code>:: Synchronizing package databases...</code> === ✅ This means your internet is working correctly. === == 🛜 Wi-Fi users (mostly laptop users) == === In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. === === ### To start the tool: === === <code>iwctl</code> === [[File:Iwctl-1.png|1360x1360px]] > Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. === ### 1. Find the name of your Wi-Fi device: === === <code>device list</code> === === The network device name will appear, like <code>wlan0</code>. === === ### 2. Scan for nearby networks: === === <code>station wlan0 scan</code> === === <code>station wlan0 get-networks</code> === === (Replace <code>wlan0</code> with your actual device name if different.) === === 3. Connect to the network: === === If the network is visible: === === <code>station wlan0 connect 'SSID'</code> === === If the network is hidden: === === <code>station wlan0 connect-hidden 'SSID'</code> === === (Replace <code>'SSID'</code> with your network name.) === === After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. === == ✅ Verifying internet access after connecting to Wi-Fi: == === You can use: === === <code>ping google.com</code> === === or: === === <code>pacman -Sy</code> === === If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. === ---- = 💽 Disks in Linux = == '''Disk Naming in Linux''' == === Disk naming in Linux is different from Windows. For example, you might see a path like: === <code>/dev/sda2</code> === Explanation of parts: === * <code>/dev</code>: This is the folder containing all system devices, like disks, network cards, etc. <code>dev</code> is short for '''device'''. * <code>sda</code>: This is the name of the first disk. Linux starts naming disks with letters: - <code>sda</code>: First disk - <code>sdb</code>: Second disk - <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' <code>/dev/sdXY</code> Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' <code>/dev/nvmeXnYpZ</code> Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' <code>/dev/vdXY</code> Example: <code>/dev/vda1</code> → First virtual disk, first partition. == '''Partitioning the Disk for Arch Linux Installation ⚙️''' == === You can view all connected disks using the command: <code>lsblk</code> === === This shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. === === If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. === [[File:Lsblk.png]] == '''Opening the cfdisk tool for disk partitioning 🧱''' == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. === To run it: === <code>cfdisk /dev/sda</code> Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 === And the interface will open... === ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png|1346x1346px]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png|1309x1309px]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: --- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == === As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. === == 🎮 Controlling the cfdisk tool: == === You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. === == 🛠️ To start partitioning the free space: == === Use the Down arrow until you reach Free Space. === === You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. === [[File:Cfdisk-2.png|1448x1448px]] == 🧱 System Partitioning: == === To install the Arch system, we need at least two partitions: === ### A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. ### The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === Boot partition: We allocate a maximum of 1G for it. This is more than enough. Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition: === In the cfdisk tool, select the Free Space using the arrow keys. Choose New from the options at the bottom, and press Enter. A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter. [[File:Cfdisk-3.png|1443x1443px]] The first partition, the boot partition, will be created. [[File:Cfdisk-4.png]] 🗂️ Creating the Root partition: After finishing creating the boot partition, we move directly to creating the second partition, the root partition. Select the remaining Free Space using the arrow keys. Choose New from the options at the bottom of the screen, then press Enter. This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|1260x1260px]] ### 💾 Confirming changes and writing partitions to the disk: When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png]] A warning question will appear: <code>"Are you sure you want to write the partition table to disk?"</code> If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter. [[File:Cfdisk-7.png]] With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png]] Now make sure to note the names of the two partitions you created: The first partition (size 1G) is the bootloader partition. The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: <code>lsblk</code> It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: === FAT32 for the bootloader partition === === EXT4 for the root / partition === But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: - It is the only filesystem that UEFI can read without any intermediaries. - It does not contain complex permissions or modern features that hinder UEFI. - It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. <nowiki>###</nowiki> 🧱 Why EXT4 for the root / partition? The root partition contains the entire operating system, so it needs a modern filesystem that supports: - File permissions: To determine who has the right to read, execute, or modify each file. - Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). - Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. - Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. == To format the bootloader partition, we write the following command: == === <code>mkfs.fat -F32 /dev/sda5</code> === 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === mkfs = Make File System = Create a filesystem. fat is the type of system. -F32 means we use FAT32 (not FAT16 or others). /dev/sda5 is the partition we created for boot (1GB). == ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. == [[File:Mkfs-1.png|1376x1376px]] As for formatting the root partition, we use the following command: <code>mkfs.ext4 /dev/sda6</code> 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|1369x1369px]] === Now that we've finished formatting, we're ready to move on to the mounting step! === --- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: <code>mount /dev/sda6 /mnt</code> 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|1396x1396px]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside /mnt, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: <code>mkdir -p /mnt/boot/efi</code> 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: <code>mount /dev/sda5 /mnt/boot/efi</code> 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. > ✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT. == If everything is good, we start moving to the system installation step! == --- > # 🏗️ Installing the System To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. === 🧰 pacman === The primary package manager in Arch Linux. Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). === 📦 pacstrap === A special tool used during installation from the live environment. Installs packages onto a specified path — usually /mnt — instead of the live system. Its function is to prepare the root partition with basic system packages, such as: - The Linux kernel * The package manager <code>pacman</code> itself! - Networking tools - System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition /mnt: <code>pacstrap /mnt base linux linux-firmware</code> === But why these specific packages?! And what does each one do? === === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: - Basic command-line tools like sh, ls, cp, mv, mkdir... - Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) - Important scripts that aid in booting === 2️⃣ linux === - This is the system kernel itself. - Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks --- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: > "What partitions do you have? Where do you want to mount each partition? And with which filesystem?" You can imagine it as a simple table containing: - Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: <code>genfstab -U /mnt >> /mnt/etc/fstab</code> ✅ Explanation of command components: <code>genfstab</code>: Short for "Generate File System Table" <code>-U</code>: Makes it use UUID identifiers instead of disk names <code>/mnt</code>: Is the root of the new system we installed >>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition == 🔒 So using UUID is the safe and reliable solution. == --- == Now we can move to the next step, which is entering the new system's root == === We can use the command: === === <code>arch-chroot /mnt</code> === === The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. === [[File:Arch-chroot.png|1272x1272px]] == After entering the system using <code>arch-chroot</code> == === We begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. === === 📦 We use the following command: === <code>pacman -Sy sudo nano grub efibootmgr os-prober networkmanager</code> [[File:Pacman.png]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === > A tool that grants root privileges to a regular user when needed, instead of always logging in as root. * Very important for system administration after creating your own user. === ✅ <code>nano</code> === > A simple and easy text editor, ideal for any beginner. * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === > The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu). * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === > A tool that interacts with boot settings in '''UEFI''' systems. * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === > A tool that searches for other operating systems installed on the device (like Windows). * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file: === === 1️⃣ Modify the GRUB_TIMEOUT option === This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png]] === 2️⃣ Enable the os-prober tool === Scroll down to the end of the file, and you will see a line like this: <code>#GRUB_DISABLE_OS_PROBER=false</code> All you need to do is remove the # sign to activate the feature, so it becomes: <code>GRUB_DISABLE_OS_PROBER=false</code> [[File:Grub-conf_1.png]] == 🎯 This allows GRUB to detect Windows and add it to the menu automatically. == After editing, save and exit nano: Ctrl + X → then y → then Enter --- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: <code>/dev/sda1</code> We mount it with this command: <code>mount /dev/sda1 /boot/efi</code> ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|1408x1408px]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png]] --- == 🧠 Generating the GRUB configuration file == === Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. === We use the following command: <code>grub-mkconfig -o /boot/grub/grub.cfg</code> Explanation of parts: <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. <code>-o</code>: means "Output", i.e., where to save the output file. <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|1380x1380px]] --- = 👤 Creating a new user = === After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: === <code>useradd -m -G wheel -s /bin/bash username</code> Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == <code>useradd</code>: The command responsible for creating the user. <code>-m</code>: Creates the home directory automatically in /home/username. <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png]] --- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: <code>passwd</code> Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: <code>password updated successfully</code> [[File:Passwd.png]] Then you're good. Setting the password for the new user: <code>passwd username</code> Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png]] --- = 🛡️ Enabling sudo privileges for the wheel group = === Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: === <code>EDITOR=nano visudo</code> [[File:Visudo-1.png]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png]] Scroll down until you reach this line: <code># %wheel ALL=(ALL:ALL) ALL</code> [[File:Visudobefore.png]] What do you do? Remove the # sign from the beginning, so it becomes like this: <code>%wheel ALL=(ALL:ALL) ALL</code> [[File:Visudoafter.png]] === ✨ Now the user in the wheel group can use sudo. === To save changes and exit nano: Ctrl + X then Y then Enter ---- = 🖥️ Setting the device name (Hostname) = == The hostname is what appears to you in the command line and is very useful for networks. == To set the name: <code>echo 'ArchBox' > /etc/hostname</code> [[File:Hostname.png]] Replace ArchBox with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: <code>nano /etc/hosts</code> [[File:Etchosts_before.png]] After it opens, add this line: <code>127.0.1.1 ArchBox.localdomain ArchBox</code> Replace ArchBox with the name you wrote in the previous step. [[File:Etchosts_after.png]] --- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: <code>systemctl enable NetworkManager</code> Just make sure you wrote the name correctly, with the exact case. --- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. === There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇: === = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: <code>pacman -S gnome gnome-extra gdm</code> And then enable the login manager: <code>systemctl enable gdm</code> === 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. === = 💎 Option Two: KDE Plasma + SDDM = == If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. == Execute the following command: <code>pacman -S plasma kde-applications sddm</code> Then enable the login manager: <code>systemctl enable sddm</code> === 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. === --- = 🧼 Finishing the installation and rebooting = == Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. == First, exit chroot: <code>exit</code> You will return to the live environment (USB). Now unmount the partitions we mounted: <code>umount -R /mnt</code> And finally... the awaited moment 🎉: <code>reboot</code> == After rebooting, if everything is fine, you will see the GRUB menu with: == Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png]] Congratulations on your First Dual Booting experience, thank you for reading. ---- 24ebbb8ad1f1fb23a9687098b44616749b2bb36a 3996 3995 2025-08-28T09:58:40Z Osama 266 wikitext text/x-wiki == Welcome to my Arch Linux Dual booting Guide == [[File:CoverEN_1.png|thumb|1024x1024px|left]] = 🚀 Checking the Boot Mode = == There are two boot modes in computer systems: == === - UEFI === === - Legacy BIOS === == You can easily check the boot mode using the System Information program in Windows. == == ✅ How to check the boot mode: == === 1. In the search box, type the following command and open the program: === === <code>System Information</code> === [[File:CheckUEFI-1.png]] === 2. From the list on the left side, look for the entry: === === <code>BIOS Mode</code> === * If the value is <code>UEFI</code> → Your system is using UEFI mode. * If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. ⚠️ It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. [[File:CheckUEFI-2.png|frameless|1110x1110px]] 📌 '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' ---- = 💿 Checking the Disk Partitioning Scheme = == There are two main types of disk partitioning schemes: == === - GPT (GUID Partition Table) === === - MBR (Master Boot Record) === == You must check the disk type before starting the installation to ensure using the correct method. == == ✅ How to check the disk partitioning scheme: == === 1. Open the <code>Disk Management</code> tool in Windows. === Right-click the Windows logo on the taskbar and select <code>Disk Management</code>. [[File:OpenDiskManagement.png|center|thumb|1054x1054px]] === 2. Select the disk you want to install Arch on. === Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png]] === 3. In the (Partition Style) field, you will see the disk type: === * If it says '''GUID Partition Table''' → This is a GPT disk. * If it says '''Master Boot Record''' → This is an MBR disk. ⚠️ The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data'''!) or use a separate physical disk. 📌 '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png]] ---- = 📦 Preparing a Partition on the Disk for Arch Linux = == Before leaving the Disk Management tool, we need free space to install Arch on. == * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == ✅ How to shrink the Windows partition: == === 1. From within Disk Management, right-click the <code>C:\</code> partition. === Choose from the menu: <code>Shrink Volume</code> [[File:ShrinkPartition-1.png|1108x1108px]] === 2. In the new window, enter the amount of space you want to shrink (in '''Megabytes'''). === Then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png]] === 3. Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: === [[File:FinalPartitionLayout-Shrinked.png|1121x1121px]] === Or like this if you deleted another non-Windows partition: === [[File:FinalPartitionLayout-Replaced.png|1113x1113px]] --- = 💾 Downloading the Arch Linux ISO = == You need to download the ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment. == == To download the official file, go to the following link: == === [https://archlinux.org/download/ Arch Linux (Official Download Link)] === [[File:ArchDownload.png|1145x1145px]] --- = 🔧 Preparing the USB Drive to Boot the Live Environment = == We need a USB flash drive to install the Arch live environment, and we will use the Ventoy tool because it is the easiest and most flexible. == == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). ⚠️ '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == ✅ Steps to download Ventoy: == === 1. Download Ventoy from the official website or directly from SourceForge. === === [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] === === [https://www.ventoy.net/en/index.html Official Ventoy Website] === [[File:VentoyDownload.png|1349x1349px]] [[File:VentoyDownload-2.png]] === 2. After downloading, you will get a compressed <code>.zip</code> file. === Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png]] == 🧪 How to install Ventoy on the USB drive == === After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. === === Make sure the program recognized the drive and shows its name in the Device field. === [[File:VentoyInstall-2.png]] == ⚙️ Customizing Ventoy settings before installation == === 1. Disable Secure Boot support: === === Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it. === [[File:VentoyInstall-3.png]] === 2. Specifying the disk partition type: === === From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT''' === > Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png]] === 3. Customizing partition configuration: === === From the '''Options''' menu → Select '''Partition Configuration''' === [[File:VentoyInstall-5.png]] === And in the first option within the new window: === === '''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK''' === [[File:VentoyInstall-6.png]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == === Press '''Install''', then agree to the warnings, and wait for the process to complete. === [[File:VentoyInstall-7.png]] === Upon successful installation, you will see a confirmation message. === === Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. === [[File:VentoyInstall-8.png]] ---- === Your USB flash drive is now ready to boot into the Arch live environment 🎉. === ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == === To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. === == ✅ The easiest way to boot without entering the BIOS == === This method doesn't even require entering the BIOS/Firmware settings: === === 1. Restart the system, but '''hold down the Shift key''' while clicking Restart. === === 2. If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. === == 🧭 In Recovery mode == === You will see a list of options, select: === === <code>Use a device</code> === === Then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). === [[File:BootArch.png|1398x1398px]] == ❗ If the 'Use a device' option is not available == === This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. === Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == === After booting from the USB, you will see the Ventoy menu. === Select the Arch Linux ISO file from it, then press Enter twice. ---- == 🎯 Starting the Live Environment == === After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. === [[File:ArchBoot.png]] --- == 💬 Live Environment Font == === If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: === === <code>setfont ter-132n</code> === === The font will change from this: === [[File:ArchFontBefore.png|1397x1397px]] === To this: === [[File:ArchFontAfter.png|1357x1357px]] == 📝 Notes on available fonts: == === The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. === === Here are some good options: === === <code>setfont ter-132n</code> === Large and clear font, excellent for small screens. === <code>setfont ter-128n</code> === Similar but slightly smaller than <code>132n</code>. === <code>setfont ter-v32b</code> === A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. === <code>setfont lat9w-16</code> === The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. === === To check the connection, try the following command: === === <code>ping google.com</code> === === You can replace <code>google.com</code> with any other website. === === If you start seeing messages like: === <code>64 bytes from ... icmp_seq=2 time=23.3 ms</code> === ✅ The internet is working successfully! === === If you see a message like: === <code>ping: google.com: Temporary failure in name resolution</code> === ❌ It means the internet connection is not active. === === ❗ Note: === === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: === === <code>pacman -Sy</code> === === This command synchronizes the package databases. If you see the message: === <code>:: Synchronizing package databases...</code> === ✅ This means your internet is working correctly. === == 🛜 Wi-Fi users (mostly laptop users) == === In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. === === ### To start the tool: === === <code>iwctl</code> === [[File:Iwctl-1.png|1360x1360px]] > Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. === ### 1. Find the name of your Wi-Fi device: === === <code>device list</code> === === The network device name will appear, like <code>wlan0</code>. === === ### 2. Scan for nearby networks: === === <code>station wlan0 scan</code> === === <code>station wlan0 get-networks</code> === === (Replace <code>wlan0</code> with your actual device name if different.) === === 3. Connect to the network: === === If the network is visible: === === <code>station wlan0 connect 'SSID'</code> === === If the network is hidden: === === <code>station wlan0 connect-hidden 'SSID'</code> === === (Replace <code>'SSID'</code> with your network name.) === === After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. === == ✅ Verifying internet access after connecting to Wi-Fi: == === You can use: === === <code>ping google.com</code> === === or: === === <code>pacman -Sy</code> === === If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. === ---- = 💽 Disks in Linux = == '''Disk Naming in Linux''' == === Disk naming in Linux is different from Windows. For example, you might see a path like: === <code>/dev/sda2</code> === Explanation of parts: === * <code>/dev</code>: This is the folder containing all system devices, like disks, network cards, etc. <code>dev</code> is short for '''device'''. * <code>sda</code>: This is the name of the first disk. Linux starts naming disks with letters: - <code>sda</code>: First disk - <code>sdb</code>: Second disk - <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' <code>/dev/sdXY</code> Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' <code>/dev/nvmeXnYpZ</code> Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' <code>/dev/vdXY</code> Example: <code>/dev/vda1</code> → First virtual disk, first partition. == '''Partitioning the Disk for Arch Linux Installation ⚙️''' == === You can view all connected disks using the command: <code>lsblk</code> === === This shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. === === If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. === [[File:Lsblk.png]] == '''Opening the cfdisk tool for disk partitioning 🧱''' == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. === To run it: === <code>cfdisk /dev/sda</code> Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 === And the interface will open... === ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png|1346x1346px]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png|1309x1309px]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: --- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == === As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. === == 🎮 Controlling the cfdisk tool: == === You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. === == 🛠️ To start partitioning the free space: == === Use the Down arrow until you reach Free Space. === === You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. === [[File:Cfdisk-2.png|1448x1448px]] == 🧱 System Partitioning: == === To install the Arch system, we need at least two partitions: === ### A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. ### The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === Boot partition: We allocate a maximum of 1G for it. This is more than enough. Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition: === In the cfdisk tool, select the Free Space using the arrow keys. Choose New from the options at the bottom, and press Enter. A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter. [[File:Cfdisk-3.png|1443x1443px]] The first partition, the boot partition, will be created. [[File:Cfdisk-4.png]] 🗂️ Creating the Root partition: After finishing creating the boot partition, we move directly to creating the second partition, the root partition. Select the remaining Free Space using the arrow keys. Choose New from the options at the bottom of the screen, then press Enter. This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|1260x1260px]] ### 💾 Confirming changes and writing partitions to the disk: When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png]] A warning question will appear: <code>"Are you sure you want to write the partition table to disk?"</code> If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter. [[File:Cfdisk-7.png]] With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png]] Now make sure to note the names of the two partitions you created: The first partition (size 1G) is the bootloader partition. The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: <code>lsblk</code> It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: === FAT32 for the bootloader partition === === EXT4 for the root / partition === But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: - It is the only filesystem that UEFI can read without any intermediaries. - It does not contain complex permissions or modern features that hinder UEFI. - It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. <nowiki>###</nowiki> 🧱 Why EXT4 for the root / partition? The root partition contains the entire operating system, so it needs a modern filesystem that supports: - File permissions: To determine who has the right to read, execute, or modify each file. - Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). - Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. - Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. == To format the bootloader partition, we write the following command: == === <code>mkfs.fat -F32 /dev/sda5</code> === 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === mkfs = Make File System = Create a filesystem. fat is the type of system. -F32 means we use FAT32 (not FAT16 or others). /dev/sda5 is the partition we created for boot (1GB). == ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. == [[File:Mkfs-1.png|1376x1376px]] As for formatting the root partition, we use the following command: <code>mkfs.ext4 /dev/sda6</code> 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|1369x1369px]] === Now that we've finished formatting, we're ready to move on to the mounting step! === --- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: <code>mount /dev/sda6 /mnt</code> 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|1396x1396px]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside /mnt, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: <code>mkdir -p /mnt/boot/efi</code> 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: <code>mount /dev/sda5 /mnt/boot/efi</code> 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. > ✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT. == If everything is good, we start moving to the system installation step! == --- > # 🏗️ Installing the System To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. === 🧰 pacman === The primary package manager in Arch Linux. Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). === 📦 pacstrap === A special tool used during installation from the live environment. Installs packages onto a specified path — usually /mnt — instead of the live system. Its function is to prepare the root partition with basic system packages, such as: - The Linux kernel * The package manager <code>pacman</code> itself! - Networking tools - System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition /mnt: <code>pacstrap /mnt base linux linux-firmware</code> === But why these specific packages?! And what does each one do? === === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: - Basic command-line tools like sh, ls, cp, mv, mkdir... - Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) - Important scripts that aid in booting === 2️⃣ linux === - This is the system kernel itself. - Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks --- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: > "What partitions do you have? Where do you want to mount each partition? And with which filesystem?" You can imagine it as a simple table containing: - Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: <code>genfstab -U /mnt >> /mnt/etc/fstab</code> ✅ Explanation of command components: <code>genfstab</code>: Short for "Generate File System Table" <code>-U</code>: Makes it use UUID identifiers instead of disk names <code>/mnt</code>: Is the root of the new system we installed >>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition == 🔒 So using UUID is the safe and reliable solution. == --- == Now we can move to the next step, which is entering the new system's root == === We can use the command: === === <code>arch-chroot /mnt</code> === === The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. === [[File:Arch-chroot.png|1272x1272px]] == After entering the system using <code>arch-chroot</code> == === We begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. === === 📦 We use the following command: === <code>pacman -Sy sudo nano grub efibootmgr os-prober networkmanager</code> [[File:Pacman.png]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === > A tool that grants root privileges to a regular user when needed, instead of always logging in as root. * Very important for system administration after creating your own user. === ✅ <code>nano</code> === > A simple and easy text editor, ideal for any beginner. * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === > The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu). * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === > A tool that interacts with boot settings in '''UEFI''' systems. * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === > A tool that searches for other operating systems installed on the device (like Windows). * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file: === === 1️⃣ Modify the GRUB_TIMEOUT option === This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png]] === 2️⃣ Enable the os-prober tool === Scroll down to the end of the file, and you will see a line like this: <code>#GRUB_DISABLE_OS_PROBER=false</code> All you need to do is remove the # sign to activate the feature, so it becomes: <code>GRUB_DISABLE_OS_PROBER=false</code> [[File:Grub-conf_1.png]] == 🎯 This allows GRUB to detect Windows and add it to the menu automatically. == After editing, save and exit nano: Ctrl + X → then y → then Enter --- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: <code>/dev/sda1</code> We mount it with this command: <code>mount /dev/sda1 /boot/efi</code> ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|1408x1408px]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png]] --- == 🧠 Generating the GRUB configuration file == === Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. === We use the following command: <code>grub-mkconfig -o /boot/grub/grub.cfg</code> Explanation of parts: <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. <code>-o</code>: means "Output", i.e., where to save the output file. <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|1380x1380px]] --- = 👤 Creating a new user = === After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: === <code>useradd -m -G wheel -s /bin/bash username</code> Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == <code>useradd</code>: The command responsible for creating the user. <code>-m</code>: Creates the home directory automatically in /home/username. <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png]] --- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: <code>passwd</code> Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: <code>password updated successfully</code> [[File:Passwd.png]] Then you're good. Setting the password for the new user: <code>passwd username</code> Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png]] --- = 🛡️ Enabling sudo privileges for the wheel group = === Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: === <code>EDITOR=nano visudo</code> [[File:Visudo-1.png]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png]] Scroll down until you reach this line: <code># %wheel ALL=(ALL:ALL) ALL</code> [[File:Visudobefore.png]] What do you do? Remove the # sign from the beginning, so it becomes like this: <code>%wheel ALL=(ALL:ALL) ALL</code> [[File:Visudoafter.png]] === ✨ Now the user in the wheel group can use sudo. === To save changes and exit nano: Ctrl + X then Y then Enter ---- = 🖥️ Setting the device name (Hostname) = == The hostname is what appears to you in the command line and is very useful for networks. == To set the name: <code>echo 'ArchBox' > /etc/hostname</code> [[File:Hostname.png]] Replace ArchBox with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: <code>nano /etc/hosts</code> [[File:Etchosts_before.png]] After it opens, add this line: <code>127.0.1.1 ArchBox.localdomain ArchBox</code> Replace ArchBox with the name you wrote in the previous step. [[File:Etchosts_after.png]] --- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: <code>systemctl enable NetworkManager</code> Just make sure you wrote the name correctly, with the exact case. --- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. === There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇: === = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: <code>pacman -S gnome gnome-extra gdm</code> And then enable the login manager: <code>systemctl enable gdm</code> === 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. === = 💎 Option Two: KDE Plasma + SDDM = == If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. == Execute the following command: <code>pacman -S plasma kde-applications sddm</code> Then enable the login manager: <code>systemctl enable sddm</code> === 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. === --- = 🧼 Finishing the installation and rebooting = == Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. == First, exit chroot: <code>exit</code> You will return to the live environment (USB). Now unmount the partitions we mounted: <code>umount -R /mnt</code> And finally... the awaited moment 🎉: <code>reboot</code> == After rebooting, if everything is fine, you will see the GRUB menu with: == Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png]] Congratulations on your First Dual Booting experience, thank you for reading. ---- 6892c8586998e3f856263f4067afdfb9bf708e44 3997 3996 2025-08-28T10:00:06Z Osama 266 wikitext text/x-wiki == Welcome to my Arch Linux Dual booting Guide == [[File:CoverEN_1.png|thumb|1024x1024px|left]] = 🚀 Checking the Boot Mode = == There are two boot modes in computer systems: == === - UEFI === === - Legacy BIOS === == You can easily check the boot mode using the System Information program in Windows. == == ✅ How to check the boot mode: == === 1. In the search box, type the following command and open the program: === === <code>System Information</code> === [[File:CheckUEFI-1.png]] === 2. From the list on the left side, look for the entry: === === <code>BIOS Mode</code> === * If the value is <code>UEFI</code> → Your system is using UEFI mode. * If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. ⚠️ It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. [[File:CheckUEFI-2.png|frameless|1110x1110px]] 📌 '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' ---- = 💿 Checking the Disk Partitioning Scheme = == There are two main types of disk partitioning schemes: == === - GPT (GUID Partition Table) === === - MBR (Master Boot Record) === == You must check the disk type before starting the installation to ensure using the correct method. == == ✅ How to check the disk partitioning scheme: == === 1. Open the <code>Disk Management</code> tool in Windows. === Right-click the Windows logo on the taskbar and select <code>Disk Management</code>. [[File:OpenDiskManagement.png|center|thumb|1054x1054px]] === 2. Select the disk you want to install Arch on. === Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png]] === 3. In the (Partition Style) field, you will see the disk type: === * If it says '''GUID Partition Table''' → This is a GPT disk. * If it says '''Master Boot Record''' → This is an MBR disk. ⚠️ The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data'''!) or use a separate physical disk. 📌 '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png]] ---- = 📦 Preparing a Partition on the Disk for Arch Linux = == Before leaving the Disk Management tool, we need free space to install Arch on. == * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == ✅ How to shrink the Windows partition: == === 1. From within Disk Management, right-click the <code>C:\</code> partition. === Choose from the menu: <code>Shrink Volume</code> [[File:ShrinkPartition-1.png|1108x1108px]] === 2. In the new window, enter the amount of space you want to shrink (in '''Megabytes'''). === Then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png]] === 3. Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: === [[File:FinalPartitionLayout-Shrinked.png|1121x1121px]] === Or like this if you deleted another non-Windows partition: === [[File:FinalPartitionLayout-Replaced.png|1113x1113px]] --- = 💾 Downloading the Arch Linux ISO = == You need to download the ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment. == == To download the official file, go to the following link: == === [https://archlinux.org/download/ Arch Linux (Official Download Link)] === [[File:ArchDownload.png|1145x1145px]] --- = 🔧 Preparing the USB Drive to Boot the Live Environment = == We need a USB flash drive to install the Arch live environment, and we will use the Ventoy tool because it is the easiest and most flexible. == == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). ⚠️ '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == ✅ Steps to download Ventoy: == === 1. Download Ventoy from the official website or directly from SourceForge. === === [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] === === [https://www.ventoy.net/en/index.html Official Ventoy Website] === [[File:VentoyDownload.png|1349x1349px]] [[File:VentoyDownload-2.png]] === 2. After downloading, you will get a compressed <code>.zip</code> file. === Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png]] == 🧪 How to install Ventoy on the USB drive == === After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. === === Make sure the program recognized the drive and shows its name in the Device field. === [[File:VentoyInstall-2.png]] == ⚙️ Customizing Ventoy settings before installation == === 1. Disable Secure Boot support: === === Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it. === [[File:VentoyInstall-3.png]] === 2. Specifying the disk partition type: === === From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT''' === > Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png]] === 3. Customizing partition configuration: === === From the '''Options''' menu → Select '''Partition Configuration''' === [[File:VentoyInstall-5.png]] === And in the first option within the new window: === === '''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK''' === [[File:VentoyInstall-6.png]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == === Press '''Install''', then agree to the warnings, and wait for the process to complete. === [[File:VentoyInstall-7.png]] === Upon successful installation, you will see a confirmation message. === === Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. === [[File:VentoyInstall-8.png]] ---- === Your USB flash drive is now ready to boot into the Arch live environment 🎉. === ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == === To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. === == ✅ The easiest way to boot without entering the BIOS == === This method doesn't even require entering the BIOS/Firmware settings: === === 1. Restart the system, but '''hold down the Shift key''' while clicking Restart. === === 2. If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. === == 🧭 In Recovery mode == === You will see a list of options, select: === === <code>Use a device</code> === === Then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). === [[File:BootArch.png|1398x1398px]] == ❗ If the 'Use a device' option is not available == === This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. === Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == === After booting from the USB, you will see the Ventoy menu. === Select the Arch Linux ISO file from it, then press Enter twice. ---- == 🎯 Starting the Live Environment == === After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. === [[File:ArchBoot.png]] --- == 💬 Live Environment Font == === If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: === === <code>setfont ter-132n</code> === === The font will change from this: === [[File:ArchFontBefore.png|1397x1397px]] === To this: === [[File:ArchFontAfter.png|1357x1357px]] == 📝 Notes on available fonts: == === The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. === === Here are some good options: === === <code>setfont ter-132n</code> === Large and clear font, excellent for small screens. === <code>setfont ter-128n</code> === Similar but slightly smaller than <code>132n</code>. === <code>setfont ter-v32b</code> === A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. === <code>setfont lat9w-16</code> === The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. === === To check the connection, try the following command: === === <code>ping google.com</code> === === You can replace <code>google.com</code> with any other website. === === If you start seeing messages like: === <code>64 bytes from ... icmp_seq=2 time=23.3 ms</code> === ✅ The internet is working successfully! === === If you see a message like: === <code>ping: google.com: Temporary failure in name resolution</code> === ❌ It means the internet connection is not active. === === ❗ Note: === === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: === === <code>pacman -Sy</code> === === This command synchronizes the package databases. If you see the message: === <code>:: Synchronizing package databases...</code> === ✅ This means your internet is working correctly. === == 🛜 Wi-Fi users (mostly laptop users) == === In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. === === ### To start the tool: === === <code>iwctl</code> === [[File:Iwctl-1.png|1360x1360px]] > Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. === ### 1. Find the name of your Wi-Fi device: === === <code>device list</code> === === The network device name will appear, like <code>wlan0</code>. === === ### 2. Scan for nearby networks: === === <code>station wlan0 scan</code> === === <code>station wlan0 get-networks</code> === === (Replace <code>wlan0</code> with your actual device name if different.) === === 3. Connect to the network: === === If the network is visible: === === <code>station wlan0 connect 'SSID'</code> === === If the network is hidden: === === <code>station wlan0 connect-hidden 'SSID'</code> === === (Replace <code>'SSID'</code> with your network name.) === === After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. === == ✅ Verifying internet access after connecting to Wi-Fi: == === You can use: === === <code>ping google.com</code> === === or: === === <code>pacman -Sy</code> === === If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. === ---- = 💽 Disks in Linux = == '''Disk Naming in Linux''' == === Disk naming in Linux is different from Windows. For example, you might see a path like: === <code>/dev/sda2</code> === Explanation of parts: === * <code>/dev</code>: This is the folder containing all system devices, like disks, network cards, etc. <code>dev</code> is short for '''device'''. * <code>sda</code>: This is the name of the first disk. Linux starts naming disks with letters: - <code>sda</code>: First disk - <code>sdb</code>: Second disk - <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' <code>/dev/sdXY</code> Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' <code>/dev/nvmeXnYpZ</code> Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' <code>/dev/vdXY</code> Example: <code>/dev/vda1</code> → First virtual disk, first partition. == '''Partitioning the Disk for Arch Linux Installation ⚙️''' == === You can view all connected disks using the command: <code>lsblk</code> === === This shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. === === If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. === [[File:Lsblk.png]] == '''Opening the cfdisk tool for disk partitioning 🧱''' == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. === To run it: === <code>cfdisk /dev/sda</code> Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 === And the interface will open... === ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png|1346x1346px]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png|1309x1309px]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: --- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == === As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. === == 🎮 Controlling the cfdisk tool: == === You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. === == 🛠️ To start partitioning the free space: == === Use the Down arrow until you reach Free Space. === === You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. === [[File:Cfdisk-2.png|1448x1448px]] == 🧱 System Partitioning: == === To install the Arch system, we need at least two partitions: === ### A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. ### The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === Boot partition: We allocate a maximum of 1G for it. This is more than enough. Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition: === In the cfdisk tool, select the Free Space using the arrow keys. Choose New from the options at the bottom, and press Enter. A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter. [[File:Cfdisk-3.png|1443x1443px]] The first partition, the boot partition, will be created. [[File:Cfdisk-4.png]] 🗂️ Creating the Root partition: After finishing creating the boot partition, we move directly to creating the second partition, the root partition. Select the remaining Free Space using the arrow keys. Choose New from the options at the bottom of the screen, then press Enter. This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|1260x1260px]] ### 💾 Confirming changes and writing partitions to the disk: When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png]] A warning question will appear: <code>"Are you sure you want to write the partition table to disk?"</code> If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter. [[File:Cfdisk-7.png]] With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png]] Now make sure to note the names of the two partitions you created: The first partition (size 1G) is the bootloader partition. The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: <code>lsblk</code> It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: === FAT32 for the bootloader partition === === EXT4 for the root / partition === But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: - It is the only filesystem that UEFI can read without any intermediaries. - It does not contain complex permissions or modern features that hinder UEFI. - It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. <nowiki>###</nowiki> 🧱 Why EXT4 for the root / partition? The root partition contains the entire operating system, so it needs a modern filesystem that supports: - File permissions: To determine who has the right to read, execute, or modify each file. - Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). - Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. - Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. == To format the bootloader partition, we write the following command: == === <code>mkfs.fat -F32 /dev/sda5</code> === 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === mkfs = Make File System = Create a filesystem. fat is the type of system. -F32 means we use FAT32 (not FAT16 or others). /dev/sda5 is the partition we created for boot (1GB). == ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. == [[File:Mkfs-1.png|1376x1376px]] As for formatting the root partition, we use the following command: <code>mkfs.ext4 /dev/sda6</code> 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|1369x1369px]] === Now that we've finished formatting, we're ready to move on to the mounting step! === --- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: <code>mount /dev/sda6 /mnt</code> 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|1396x1396px]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside /mnt, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: <code>mkdir -p /mnt/boot/efi</code> 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: <code>mount /dev/sda5 /mnt/boot/efi</code> 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. > ✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT. == If everything is good, we start moving to the system installation step! == --- > # 🏗️ Installing the System To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. === 🧰 pacman === The primary package manager in Arch Linux. Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). === 📦 pacstrap === A special tool used during installation from the live environment. Installs packages onto a specified path — usually /mnt — instead of the live system. Its function is to prepare the root partition with basic system packages, such as: - The Linux kernel * The package manager <code>pacman</code> itself! - Networking tools - System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition /mnt: <code>pacstrap /mnt base linux linux-firmware</code> === But why these specific packages?! And what does each one do? === === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: - Basic command-line tools like sh, ls, cp, mv, mkdir... - Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) - Important scripts that aid in booting === 2️⃣ linux === - This is the system kernel itself. - Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks --- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: > "What partitions do you have? Where do you want to mount each partition? And with which filesystem?" You can imagine it as a simple table containing: - Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: <code>genfstab -U /mnt >> /mnt/etc/fstab</code> ✅ Explanation of command components: <code>genfstab</code>: Short for "Generate File System Table" <code>-U</code>: Makes it use UUID identifiers instead of disk names <code>/mnt</code>: Is the root of the new system we installed >>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition == 🔒 So using UUID is the safe and reliable solution. == --- == Now we can move to the next step, which is entering the new system's root == === We can use the command: === === <code>arch-chroot /mnt</code> === === The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. === [[File:Arch-chroot.png|1272x1272px]] == After entering the system using <code>arch-chroot</code> == === We begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. === === 📦 We use the following command: === <code>pacman -Sy sudo nano grub efibootmgr os-prober networkmanager</code> [[File:Pacman.png]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === > A tool that grants root privileges to a regular user when needed, instead of always logging in as root. * Very important for system administration after creating your own user. === ✅ <code>nano</code> === > A simple and easy text editor, ideal for any beginner. * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === > The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu). * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === > A tool that interacts with boot settings in '''UEFI''' systems. * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === > A tool that searches for other operating systems installed on the device (like Windows). * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file: === === 1️⃣ Modify the GRUB_TIMEOUT option === This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png]] === 2️⃣ Enable the os-prober tool === Scroll down to the end of the file, and you will see a line like this: <code>#GRUB_DISABLE_OS_PROBER=false</code> All you need to do is remove the # sign to activate the feature, so it becomes: <code>GRUB_DISABLE_OS_PROBER=false</code> [[File:Grub-conf_1.png]] == 🎯 This allows GRUB to detect Windows and add it to the menu automatically. == After editing, save and exit nano: Ctrl + X → then y → then Enter --- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: <code>/dev/sda1</code> We mount it with this command: <code>mount /dev/sda1 /boot/efi</code> ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|1408x1408px]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png]] --- == 🧠 Generating the GRUB configuration file == === Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. === We use the following command: <code>grub-mkconfig -o /boot/grub/grub.cfg</code> Explanation of parts: <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. <code>-o</code>: means "Output", i.e., where to save the output file. <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|1380x1380px]] --- = 👤 Creating a new user = === After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: === <code>useradd -m -G wheel -s /bin/bash username</code> Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == <code>useradd</code>: The command responsible for creating the user. <code>-m</code>: Creates the home directory automatically in /home/username. <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png]] --- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: <code>passwd</code> Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: <code>password updated successfully</code> [[File:Passwd.png]] Then you're good. Setting the password for the new user: <code>passwd username</code> Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png]] --- = 🛡️ Enabling sudo privileges for the wheel group = === Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: === <code>EDITOR=nano visudo</code> [[File:Visudo-1.png]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png]] Scroll down until you reach this line: <code># %wheel ALL=(ALL:ALL) ALL</code> [[File:Visudobefore.png]] What do you do? Remove the # sign from the beginning, so it becomes like this: <code>%wheel ALL=(ALL:ALL) ALL</code> [[File:Visudoafter.png]] === ✨ Now the user in the wheel group can use sudo. === To save changes and exit nano: Ctrl + X then Y then Enter ---- = 🖥️ Setting the device name (Hostname) = == The hostname is what appears to you in the command line and is very useful for networks. == To set the name: <code>echo 'ArchBox' > /etc/hostname</code> [[File:Hostname.png]] Replace ArchBox with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: <code>nano /etc/hosts</code> [[File:Etchosts_before.png]] After it opens, add this line: <code>127.0.1.1 ArchBox.localdomain ArchBox</code> Replace ArchBox with the name you wrote in the previous step. [[File:Etchosts_after.png]] --- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: <code>systemctl enable NetworkManager</code> Just make sure you wrote the name correctly, with the exact case. --- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. === There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇: === = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: <code>pacman -S gnome gnome-extra gdm</code> And then enable the login manager: <code>systemctl enable gdm</code> === 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. === = 💎 Option Two: KDE Plasma + SDDM = == If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. == Execute the following command: <code>pacman -S plasma kde-applications sddm</code> Then enable the login manager: <code>systemctl enable sddm</code> === 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. === --- = 🧼 Finishing the installation and rebooting = == Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. == First, exit chroot: <code>exit</code> You will return to the live environment (USB). Now unmount the partitions we mounted: <code>umount -R /mnt</code> And finally... the awaited moment 🎉: <code>reboot</code> == After rebooting, if everything is fine, you will see the GRUB menu with: == Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png]] Congratulations on your First Dual Booting experience, thank you for reading. ---- 6fa1ecf78e73508ec76f4f22ccb666e36fcadcf6 3999 3997 2025-08-28T11:19:45Z Madonuko 140 tidy up wikitext text/x-wiki {{Guide Warning}} {{cleanup}} {{Needs Citations}} [[File:CoverEN_1.png|center|How to Install Arch Linux next to Windows]] This guide covers [[dual booting]] with [[Arch Linux]] and [[Microsoft Windows]]. = 🚀 Checking the Boot Mode = [[File:CheckUEFI-1.png|right|frameless]] [[File:CheckUEFI-2.png|right|frameless]] There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> → Your system is using UEFI mode. #* If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. ⚠️ It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. 📌 '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' ---- = 💿 Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == ✅ How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|center]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|center]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' → This is a GPT disk. #* If it says '''Master Boot Record''' → This is an MBR disk. ⚠️ The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data'''!) or use a separate physical disk. 📌 '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png]] ---- = 📦 Preparing a Partition on the Disk for Arch Linux = Before leaving the Disk Management tool, we need free space to install Arch on. * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == ✅ How to shrink the Windows partition: == # From within Disk Management, right-click the <code>C:\</code> partition. Choose from the menu: <code>Shrink Volume</code>[[File:ShrinkPartition-1.png|center]] # In the new window, enter the amount of space you want to shrink (in '''Megabytes'''), then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png|center]] # Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: [[File:FinalPartitionLayout-Shrinked.png|center]]<br>Or like this if you deleted another non-Windows partition:[[File:FinalPartitionLayout-Replaced.png|center]] ---- = 💾 Downloading the Arch Linux ISO = You need to download the ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment. To download the official file, go to the following link: [https://archlinux.org/download/ Arch Linux (Official Download Link)] [[File:ArchDownload.png|center]] ---- = 🔧 Preparing the USB Drive to Boot the Live Environment = We need a USB flash drive to install the Arch live environment, and we will use the [[Ventoy]] tool because it is the easiest and most flexible. == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). ⚠️ '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == ✅ Steps to download Ventoy: == # Download Ventoy from the official website or directly from SourceForge: #* [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] #* [https://www.ventoy.net/en/index.html Official Ventoy Website] [[File:VentoyDownload.png|center]] [[File:VentoyDownload-2.png|center]] # After downloading, you will get a compressed <code>.zip</code> file. Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png|center]] == 🧪 How to install Ventoy on the USB drive == After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. Make sure the program recognized the drive and shows its name in the Device field. [[File:VentoyInstall-2.png|center]] == ⚙️ Customizing Ventoy settings before installation == # Disable Secure Boot support<br>Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it.[[File:VentoyInstall-3.png|center]] # Specifying the disk partition type:<br>From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT'''<br>Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png|center]] # Customizing partition configuration: #*From the '''Options''' menu → Select '''Partition Configuration'''[[File:VentoyInstall-5.png|center]] #*And in the first option within the new window:<br>'''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK'''[[File:VentoyInstall-6.png|center]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == Press '''Install''', then agree to the warnings, and wait for the process to complete. [[File:VentoyInstall-7.png|center]] Upon successful installation, you will see a confirmation message. Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. [[File:VentoyInstall-8.png|center]] ---- '''Your USB flash drive is now ready to boot into the Arch live environment 🎉.''' ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. == ✅ The easiest way to boot without entering the BIOS == This method doesn't even require entering the BIOS/Firmware settings: # Restart the system, but '''hold down the Shift key''' while clicking Restart. # If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. == 🧭 In Recovery mode == You will see a list of options, select <code>Use a device</code>, then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). [[File:BootArch.png|center]] == ❗ If the 'Use a device' option is not available == This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == After booting from the USB, you will see the Ventoy menu. Select the Arch Linux ISO file from it, then press Enter twice. ---- == 🎯 Starting the Live Environment == After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. [[File:ArchBoot.png|center]] ---- == 💬 Live Environment Font == If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: setfont ter-132n The font will change from this: [[File:ArchFontBefore.png|center]] To this: [[File:ArchFontAfter.png|center]] == 📝 Notes on available fonts: == The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. Here are some good options: * <code>setfont ter-132n</code><br>Large and clear font, excellent for small screens. * <code>setfont ter-128n</code><br>Similar but slightly smaller than <code>132n</code>. * <code>setfont ter-v32b</code><br>A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. * <code>setfont lat9w-16</code>The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. To check the connection, try the following command: ping google.com You can replace <code>google.com</code> with any other website. If you start seeing messages like: 64 bytes from ... icmp_seq=2 time=23.3 ms ✅ The internet is working successfully! If you see a message like: ping: google.com: Temporary failure in name resolution ❌ It means the internet connection is not active. === ❗ Note: === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: pacman -Sy This command synchronizes the package databases. If you see the message: :: Synchronizing package databases... ✅ This means your internet is working correctly. == 🛜 Wi-Fi users (mostly laptop users) == [[File:Iwctl-1.png|right|frameless]] In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. To start the tool: iwctl Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. # Find the name of your Wi-Fi device:<pre>device list</pre>The network device name will appear, like <code>wlan0</code>. # Scan for nearby networks:<syntaxhighlight> station wlan0 scan station wlan0 get-networks </syntaxhighlight>(Replace <code>wlan0</code> with your actual device name if different.) # Connect to the network: #* If the network is visible:<syntaxhighlight>station wlan0 connect 'SSID'</syntaxhighlight> #* If the network is hidden:<syntaxhighlight>station wlan0 connect-hidden 'SSID'</syntaxhighlight> :(Replace <code>'SSID'</code> with your network name.) :After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. == ✅ Verifying internet access after connecting to Wi-Fi == You can use: ping google.com or: pacman -Sy If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. ---- = 💽 Disks in Linux = == Disk Naming in Linux == Disk naming in Linux is different from Windows. For example, you might see a path like: /dev/sda2 === Explanation of parts: === ;<code>/dev</code> : This is the folder containing all system devices, like disks, network cards, etc. : <code>dev</code> is short for '''device'''. ;<code>sda</code> :This is the name of the first disk. Linux starts naming disks with letters: :* <code>sda</code>: First disk :* <code>sdb</code>: Second disk :* <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' *:<code>/dev/sdXY</code> *:Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' *:<code>/dev/nvmeXnYpZ</code> *:Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' *:<code>/dev/vdXY</code> *:Example: <code>/dev/vda1</code> → First virtual disk, first partition. == Partitioning the Disk for Arch Linux Installation ⚙️ == You can view all connected disks using the <code>lsblk</code> command, which shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. [[File:Lsblk.png|center]] == Opening the cfdisk tool for disk partitioning 🧱 == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. To run it: cfdisk /dev/sda Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 And the interface will open... ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png|center]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png|center]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: ---- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. == 🎮 Controlling the cfdisk tool: == You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. == 🛠️ To start partitioning the free space: == Use the Down arrow until you reach Free Space. You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. [[File:Cfdisk-2.png|center]] == 🧱 System Partitioning: == To install the Arch system, we need at least two partitions: * A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. * The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === * Boot partition: We allocate a maximum of 1G for it. This is more than enough. * Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition === * In the cfdisk tool, select the Free Space using the arrow keys. * Choose New from the options at the bottom, and press Enter. * A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter.[[File:Cfdisk-3.png|center]] *The first partition, the boot partition, will be created.[[File:Cfdisk-4.png|center]] === 🗂️ Creating the Root partition === After finishing creating the boot partition, we move directly to creating the second partition, the root partition. * Select the remaining Free Space using the arrow keys. * Choose New from the options at the bottom of the screen, then press Enter. * This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|center]] === 💾 Confirming changes and writing partitions to the disk === When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. * After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png|center]] * A warning question will appear:<pre>Are you sure you want to write the partition table to disk?</pre>If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter.[[File:Cfdisk-7.png|center]] * With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png|center]] Now make sure to note the names of the two partitions you created: * The first partition (size 1G) is the bootloader partition. * The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: lsblk It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: * FAT32 for the bootloader partition * EXT4 for the root / partition But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: * It is the only filesystem that UEFI can read without any intermediaries. * It does not contain complex permissions or modern features that hinder UEFI. * It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. === 🧱 Why EXT4 for the root / partition? === The root partition contains the entire operating system, so it needs a modern filesystem that supports: * File permissions: To determine who has the right to read, execute, or modify each file. * Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). * Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. * Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. To format the bootloader partition, we write the following command: mkfs.fat -F32 /dev/sda5 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === * <code>mkfs</code> = Make File System = Create a filesystem. * <code>fat</code> is the type of system. * <code>-F32</code> means we use FAT32 (not FAT16 or others). * <code>/dev/sda5</code> is the partition we created for boot (1GB). ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. [[File:Mkfs-1.png|center]] As for formatting the root partition, we use the following command: mkfs.ext4 /dev/sda6 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|center]] Now that we've finished formatting, we're ready to move on to the mounting step! ---- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: mount /dev/sda6 /mnt 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|center]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside <code>/mnt</code>, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: mkdir -p /mnt/boot/efi 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: mount /dev/sda5 /mnt/boot/efi 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. <blockquote>✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT.</blockquote> If everything is good, we start moving to the system installation step! ---- == 🏗️ Installing the System == To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? : Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. ;🧰 pacman :The primary package manager in Arch Linux. :Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). ;📦 pacstrap :A special tool used during installation from the live environment. :Installs packages onto a specified path — usually /mnt — instead of the live system. :Its function is to prepare the root partition with basic system packages, such as: :*The Linux kernel :*The package manager <code>pacman</code> itself! :* Networking tools :* System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition <code>/mnt</code>: pacstrap /mnt base linux linux-firmware But why these specific packages?! And what does each one do? === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: * Basic command-line tools like sh, ls, cp, mv, mkdir... * Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) * Important scripts that aid in booting === 2️⃣ linux === This is the system kernel itself. * Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks ---- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: <blockquote>"What partitions do you have? Where do you want to mount each partition? And with which filesystem?"</blockquote> You can imagine it as a simple table containing: * Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: genfstab -U /mnt >> /mnt/etc/fstab ✅ Explanation of command components: * <code>genfstab</code>: Short for "Generate File System Table" * <code>-U</code>: Makes it use UUID identifiers instead of disk names * <code>/mnt</code>: Is the root of the new system we installed * <code>>></code>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition 🔒 So using UUID is the safe and reliable solution. ---- Now we can move to the next step, which is entering the new system's root We can use the command: arch-chroot /mnt The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. [[File:Arch-chroot.png|center]] After entering the system using <code>arch-chroot</code>, we begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. 📦 We use the following command pacman -Sy sudo nano grub efibootmgr os-prober networkmanager [[File:Pacman.png|center]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === <blockquote>A tool that grants root privileges to a regular user when needed, instead of always logging in as root.</blockquote> * Very important for system administration after creating your own user. === ✅ <code>nano</code> === <blockquote>A simple and easy text editor, ideal for any beginner.</blockquote> * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === <blockquote>The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu).</blockquote> * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === <blockquote>A tool that interacts with boot settings in '''UEFI''' systems.</blockquote> * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === <blockquote>A tool that searches for other operating systems installed on the device (like Windows).</blockquote> * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file === ==== 1️⃣ Modify the GRUB_TIMEOUT option ==== This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png|center]] ==== 2️⃣ Enable the os-prober tool ==== Scroll down to the end of the file, and you will see a line like this: #GRUB_DISABLE_OS_PROBER=false All you need to do is remove the # sign to activate the feature, so it becomes: GRUB_DISABLE_OS_PROBER=false [[File:Grub-conf_1.png|center]] 🎯 This allows GRUB to detect Windows and add it to the menu automatically. After editing, save and exit nano: Ctrl + X → then y → then Enter ---- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: /dev/sda1 We mount it with this command: mount /dev/sda1 /boot/efi ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|center]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png|center]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png|center]] ---- == 🧠 Generating the GRUB configuration file == Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. We use the following command: grub-mkconfig -o /boot/grub/grub.cfg Explanation of parts: * <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. * <code>-o</code>: means "Output", i.e., where to save the output file. * <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|center]] ---- = 👤 Creating a new user = After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: useradd -m -G wheel -s /bin/bash username Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == * <code>useradd</code>: The command responsible for creating the user. * <code>-m</code>: Creates the home directory automatically in /home/username. * <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. * <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png|center]] ---- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: passwd Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: password updated successfully [[File:Passwd.png|center]] Then you're good. Setting the password for the new user: passwd username Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png|center]] ---- = 🛡️ Enabling sudo privileges for the wheel group = Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: EDITOR=nano visudo [[File:Visudo-1.png|center]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png|center]] Scroll down until you reach this line: # %wheel ALL=(ALL:ALL) ALL [[File:Visudobefore.png|center]] What do you do? Remove the # sign from the beginning, so it becomes like this: %wheel ALL=(ALL:ALL) ALL [[File:Visudoafter.png]] ✨ Now the user in the wheel group can use sudo. To save changes and exit nano, press {{Keypress|Ctrl|X}}{{Keypress|Y|Enter|chain=}} ---- = 🖥️ Setting the device name (Hostname) = The hostname is what appears to you in the command line and is very useful for networks. To set the name: echo 'ArchBox' > /etc/hostname [[File:Hostname.png|center]] Replace ''ArchBox'' with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: nano /etc/hosts [[File:Etchosts_before.png|center]] After it opens, add this line: 127.0.1.1 ArchBox.localdomain ArchBox Replace ''ArchBox'' with the name you wrote in the previous step. [[File:Etchosts_after.png|center]] ---- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: systemctl enable NetworkManager Just make sure you wrote the name correctly, with the exact case. ---- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇 = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: pacman -S gnome gnome-extra gdm And then enable the login manager: systemctl enable gdm 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. = 💎 Option Two: KDE Plasma + SDDM = If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. Execute the following command: pacman -S plasma kde-applications sddm Then enable the login manager: systemctl enable sddm 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. ---- = 🧼 Finishing the installation and rebooting = Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. First, exit chroot: exit You will return to the live environment (USB). Now unmount the partitions we mounted: umount -R /mnt And finally... the awaited moment 🎉: reboot After rebooting, if everything is fine, you will see the GRUB menu with: Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png|center]] Congratulations on your First Dual Booting experience, thank you for reading. a8a867251e0e57b25bbf345cc037e1dd47d0b472 6 977 3980 2025-08-28T09:39:49Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 978 3981 2025-08-28T09:40:26Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 979 3982 2025-08-28T09:41:03Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 980 3983 2025-08-28T09:41:41Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 981 3984 2025-08-28T09:42:18Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 982 3985 2025-08-28T09:42:55Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 983 3986 2025-08-28T09:43:33Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 984 3987 2025-08-28T09:44:10Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 985 3988 2025-08-28T09:44:47Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 986 3989 2025-08-28T09:45:25Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 987 3991 2025-08-28T09:45:51Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 988 3992 2025-08-28T09:46:18Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 989 3993 2025-08-28T09:46:44Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 6 990 3994 2025-08-28T09:47:11Z Hamachitan 222 Requested by [[User:Osama]] for [[Guides:ArchDualboot]] wikitext text/x-wiki This automatic upload was requested by [[User:Osama]]. Apart from bug reports and suggestions for [[User:Hamachitan|the 🍣Hamachitan bot]], for enquiries of this upload, please [[User talk:Osama|contact]] the file owner directly. 070f8744a8bf7874bfac285e93cc12afa3fc9ab6 0 991 3998 2025-08-28T10:58:04Z Fluffinity 271 Use "Zsh" instead of "it" when specifying POSIX compatibility wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Z Shell Logo Color Vertical.svg|frameless|alt=The Zsh logo, a terminal window with a % prompt and the text ZSH on the bottom right]] | caption = Zsh Logo | title = Zsh | releasestatus = Maintained | lastrelease = 5.9 (2022-05-14) | languages = [[C]] | developers = Peter Stephenson and contributors | website = https://www.zsh.org }} The Z Shell(Zsh) is a cross-platform [[CLI]] with a focus on expanding on the [http://kornshell.com/ KornShell(ksh)].<ref name="zsh-introduction">{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Introduction.html#Introduction|title=Zsh Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> It does offer functionality, like command line editing, builtin spelling correction, programmable command completion, shell functions (with autoloading) and a history mechanism<ref name="zsh-introduction"/>. While Zsh does not provide [[POSIX]] compatibility out-of-the-box, it is able to emulate both sh and ksh.<ref>{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Invocation.html#Compatibility|title=Zsh Invocation Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> == References == <references /> e392e78ba1bac8d9e7de1d7a323d9e49a7b9f22c 4000 3998 2025-08-28T11:37:56Z Fluffinity 271 Add Stub template to page wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Z Shell Logo Color Vertical.svg|frameless|alt=The Zsh logo, a terminal window with a % prompt and the text ZSH on the bottom right]] | caption = Zsh Logo | title = Zsh | releasestatus = Maintained | lastrelease = 5.9 (2022-05-14) | languages = [[C]] | developers = Peter Stephenson and contributors | website = https://www.zsh.org }} The Z Shell(Zsh) is a cross-platform [[CLI]] with a focus on expanding on the [http://kornshell.com/ KornShell(ksh)].<ref name="zsh-introduction">{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Introduction.html#Introduction|title=Zsh Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> It does offer functionality, like command line editing, builtin spelling correction, programmable command completion, shell functions (with autoloading) and a history mechanism<ref name="zsh-introduction"/>. While Zsh does not provide [[POSIX]] compatibility out-of-the-box, it is able to emulate both sh and ksh.<ref>{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Invocation.html#Compatibility|title=Zsh Invocation Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> == References == <references /> 16fc34b308b13c78c6b3b47b297efeebb43f36c9 4002 4000 2025-08-28T17:47:22Z Fluffinity 271 Add notable differences to bash V1 wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Z Shell Logo Color Vertical.svg|frameless|alt=The Zsh logo, a terminal window with a % prompt and the text ZSH on the bottom right]] | caption = Zsh Logo | title = Zsh | releasestatus = Maintained | lastrelease = 5.9 (2022-05-14) | languages = [[C]] | developers = Peter Stephenson and contributors | website = https://www.zsh.org }} The Z Shell(Zsh) is a cross-platform [[CLI]] with a focus on expanding on the [http://kornshell.com/ KornShell(ksh)].<ref name="zsh-introduction">{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Introduction.html#Introduction|title=Zsh Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> It does offer functionality, like command line editing, builtin spelling correction, programmable command completion, shell functions (with autoloading) and a history mechanism<ref name="zsh-introduction"/>. While Zsh does not provide [[POSIX]] compatibility out-of-the-box, it is able to emulate both sh and ksh.<ref>{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Invocation.html#Compatibility|title=Zsh Invocation Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> == Notable Differences compared to Bash == * Zsh does use <code>.zshenv</code>, <code>.zshrc</code>, <code>.zshlogin</code>, <code>.zshlogout</code> and <code>.zprofile</code><ref>https://zsh.sourceforge.io/Doc/Release/Files.html#Files</ref> instead of <code>.bash_profile</code>, <code>login</code>, <code>.profile</code>, <code>.bash_logout</code> and <code>.bashrc</code><ref>https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html</ref> * Zsh has built-in prompt theming via <code>promptinit</code> and the <code>prompt</code> command<ref>https://zsh.sourceforge.io/Doc/Release/User-Contributions.html#Prompt-Themes</ref> and uses <code>%</code> escapes for prompt expansion<ref>https://zsh.sourceforge.io/Doc/Release/Prompt-Expansion.html#Prompt-Expansion</ref> instead of the <code>\</code> escapes used in bash<ref>https://www.gnu.org/software/bash/manual/html_node/Controlling-the-Prompt.html#Controlling-the-Prompt</ref> * Zsh arrays start at <code>1</code><ref name="array-subscript-zsh">https://zsh.sourceforge.io/Doc/Release/Parameters.html#Array-Subscripts</ref>, while bash arrays start at <code>0</code><ref>https://www.gnu.org/software/bash/manual/html_node/Arrays.html</ref> == References == <references /> 8bfbeee4cb664ee8c19f03a8e1b3b1148bf3e55c 4004 4002 2025-08-28T19:27:52Z Imnotgoodatnames 121 changed up the wording a bit, moved period at the end of the sentence to before cite note 1.1 wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Z Shell Logo Color Vertical.svg|frameless|alt=The Zsh logo, a terminal window with a % prompt and the text ZSH on the bottom right]] | caption = Zsh Logo | title = Zsh | releasestatus = Maintained | lastrelease = 5.9 (2022-05-14) | languages = [[C]] | developers = Peter Stephenson and contributors | website = https://www.zsh.org }} The Z Shell(Zsh) is a cross-platform [[CLI]] with a focus on expanding on the [http://kornshell.com/ KornShell(ksh)].<ref name="zsh-introduction">{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Introduction.html#Introduction|title=Zsh Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> It offers features such as command line editing, built-in spelling correction, programmable command completion, shell functions (with autoloading) and a history mechanism.<ref name="zsh-introduction"/> While Zsh does not provide [[POSIX]] compatibility out-of-the-box, it is able to emulate both sh and ksh.<ref>{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Invocation.html#Compatibility|title=Zsh Invocation Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> == Notable Differences compared to Bash == * Zsh uses <code>.zshenv</code>, <code>.zshrc</code>, <code>.zshlogin</code>, <code>.zshlogout</code> and <code>.zprofile</code><ref>https://zsh.sourceforge.io/Doc/Release/Files.html#Files</ref> instead of <code>.bash_profile</code>, <code>login</code>, <code>.profile</code>, <code>.bash_logout</code> and <code>.bashrc</code><ref>https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html</ref> * Zsh has built-in prompt theming via <code>promptinit</code> and the <code>prompt</code> command<ref>https://zsh.sourceforge.io/Doc/Release/User-Contributions.html#Prompt-Themes</ref> and uses <code>%</code> escapes for prompt expansion<ref>https://zsh.sourceforge.io/Doc/Release/Prompt-Expansion.html#Prompt-Expansion</ref> instead of the <code>\</code> escapes used in bash<ref>https://www.gnu.org/software/bash/manual/html_node/Controlling-the-Prompt.html#Controlling-the-Prompt</ref> * Zsh arrays start at <code>1</code><ref name="array-subscript-zsh">https://zsh.sourceforge.io/Doc/Release/Parameters.html#Array-Subscripts</ref>, while bash arrays start at <code>0</code><ref>https://www.gnu.org/software/bash/manual/html_node/Arrays.html</ref> == References == <references /> dc9ff19ce70d6d6097411df77f8c0f7503f6a31a 0 405 4001 3662 2025-08-28T13:13:26Z PixelBrush 272 Slight extension of the provided examples, as Steam and similar store fronts are also proprietary. wikitext text/x-wiki [[Category:Terminology]] {{Cleanup|Short page}}Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Linux and other open source operating systems will avoid or not support proprietary software when possible. This is mainly due to incompatible licensing.<ref>https://solutionshub.epam.com/blog/post/proprietary-software-definition-examples Epam, 2025 (imported 27th June 2025)</ref> Some examples of proprietary software include, but are not limited to, Microsoft Windows, macOS, Adobe Photoshop, Steam, the Epic Games Launcher and the Microsoft Office Suite. == References == 5388e4cac915b56eda8e5cb8d3ff903e74093b75 0 909 4003 3871 2025-08-28T19:20:27Z Imnotgoodatnames 121 added image wikitext text/x-wiki {{DISPLAYTITLE:nvi}} [[category:software]] [[File:Nvi.png|thumb|Text editor nvi]] '''nvi''' is a text editor for [[Unix-Like]] operating systems. nvi was originally created as a replacement for the [[vi]] editor and first appeared in 4.4BSD.<ref>https://man.openbsd.org/vi.1</ref> Unlike other modern implementations of the vi editor such as [[vim]] or [[elvis]], nvi still closely resembles the look and feel of the original vi. == References == f25dfa865ae18c4400e39f8ae5deac36e53c3995 2 992 4005 2025-08-29T17:04:41Z Madonuko 140 init wikitext text/x-wiki {{Needs Citations}} A variety of ways for installing [[software]] are available on most [[Unix]]-like systems, which will be explained below. == Software Repositories == :''Main Article: [[Repository]]'' Software programs may be downloaded from a centralised software [[repository]], possibly in the format of ''packages'' or [[binary|binaries]]. This process could be manual or automatic — users may choose to download these software manually instead of using automation tools. In many cases however, the word ''repository'' refers to the latter, where a ''package manager'' is required to extract, decode, and install the contents of a package, as explained in the next section. === Package Managers === :''Main Article: [[Package Manager]]'' Software distributed in the form of '''software packages''' may be installed via various ''package managers''. Some package managers are specific to a [[distribution]] (or a branch of distributions), while others may be used across different distributions or even different [[Operating System]]s. On this wiki, the start of a distribution page contains an info box that documents its main supported package managers. Consult the corresponding pages on how to use these package managers. In many cases this is the preferred way of installing software, as it's convenient to update all installed packages at once. For distribution-specific package managers, the packages are usually provided by the same distributions maintainers, making package breakages very unlikely. For package managers that ship packages directly provided by upstream (i.e. the maintainers of the software), the packages are usually more up-to-date with minimal security concerns, and upstream support is usually better. == AppImages == :''Main Article: [[AppImage]]'' When a software is not available as a package or in a repository, usually the second option is to use an '''AppImage''' provided by upstream. The same AppImage may be run on most [[Linux]] distributions as long as the [[architecture]] is correct. '''AppImages do not support updates'''. In many cases, users are required to download a newer version from upstream in order to update their AppImages. Software in AppImage formats are also significantly less optimised compared to ones provided by corresponding distributions. == Binaries == :''Main Article: [[Executable]]'' Sometimes upstream provides pre-compiled binaries (possibly in a [[tar]]ball) for users to download directly. These binaries are usually optimised to some degree, but may not run on obscure setups (e.g. older systems). == Manual Compilation == If the source code is available, users may manually compile the program. This produces an executable most optimised for the system, and possibly has the highest chance of working correctly. The major downside however is that this requires technical knowledge and takes time. 0b550dbcf96d32c555f94f7bc089b7e4b93dc3d9 4006 4005 2025-08-30T07:50:28Z Madonuko 140 /* Package Mangers */ examples wikitext text/x-wiki {{Needs Citations}} A variety of ways for installing [[software]] are available on most [[Unix]]-like systems, which will be explained below. == Software Repositories == :''Main Article: [[Repository]]'' Software programs may be downloaded from a centralised software [[repository]], possibly in the format of ''packages'' or [[binary|binaries]]. This process could be manual or automatic — users may choose to download these software manually instead of using automation tools. In many cases however, the word ''repository'' refers to the latter, where a ''package manager'' is required to extract, decode, and install the contents of a package, as explained in the next section. === Package Managers === :''Main Article: [[Package Manager]]'' Software distributed in the form of '''software packages''' may be installed via various ''package managers''. Some package managers are specific to a [[distribution]] (or a branch of distributions), while others may be used across different distributions or even different [[Operating System]]s. On this wiki, the start of a distribution page contains an info box that documents its main supported package managers. Consult the corresponding pages on how to use these package managers. In many cases this is the preferred way of installing software, as it's convenient to update all installed packages at once. For distribution-specific package managers, the packages are usually provided by the same distributions maintainers, making package breakages very unlikely. For package managers that ship packages directly provided by upstream (i.e. the maintainers of the software), the packages are usually more up-to-date with minimal security concerns, and upstream support is usually better. ==== Distribution Package Managers ==== Some package formats are specific to distributions. For [[Debian]]-based distributions, [[dpkg]] is used, and for [[Red Hat]] based distributions, [[rpm]] is used. In most cases, the matching package format must be used, otherwise installation is not possible. ==== Cross-platform Package Managers ==== Some package managers like [[flatpak]] and [[snap]]d provide software support for different distributions, in the format of [[sandbox]]ing. These should be used for installing graphical applications and non-system components only. Do not install [[CLI]] or [[TUI]] programs using these methods. Common package managers that do not involve sandboxing include [[brew]], [[nix]]. Some programming languages provide their own package manager such as [[pip]] and [[cargo]]. == AppImages == :''Main Article: [[AppImage]]'' When a software is not available as a package or in a repository, usually the second option is to use an '''AppImage''' provided by upstream. The same AppImage may be run on most [[Linux]] distributions as long as the [[architecture]] is correct. '''AppImages do not support updates'''. In many cases, users are required to download a newer version from upstream in order to update their AppImages. Software in AppImage formats are also significantly less optimised compared to ones provided by corresponding distributions. == Binaries == :''Main Article: [[Executable]]'' Sometimes upstream provides pre-compiled binaries (possibly in a [[tar]]ball) for users to download directly. These binaries are usually optimised to some degree, but may not run on obscure setups (e.g. older systems). == Manual Compilation == If the source code is available, users may manually compile the program. This produces an executable most optimised for the system, and possibly has the highest chance of working correctly. The major downside however is that this requires technical knowledge and takes time. 01c2b4de2c7f15936fac75b2b886a236062fbf3c 2 992 4007 4006 2025-08-30T09:43:44Z Madonuko 140 /* Tips and Tricks */ wikitext text/x-wiki {{Needs Citations}} A variety of ways for installing [[software]] are available on most [[Unix]]-like systems, which will be explained below. == Software Repositories == :''Main Article: [[Repository]]'' Software programs may be downloaded from a centralised software [[repository]], possibly in the format of ''packages'' or [[binary|binaries]]. This process could be manual or automatic — users may choose to download these software manually instead of using automation tools. In many cases however, the word ''repository'' refers to the latter, where a ''package manager'' is required to extract, decode, and install the contents of a package, as explained in the next section. === Package Managers === :''Main Article: [[Package manager]]'' Software distributed in the form of '''software packages''' may be installed via various ''package managers''. Some package managers are specific to a [[distribution]] (or a branch of distributions), while others may be used across different distributions or even different [[Operating system]]s. On this wiki, the start of a distribution page contains an info box that documents its main supported package managers. Consult the corresponding pages on how to use these package managers. In many cases this is the preferred way of installing software, as it's convenient to update all installed packages at once. For distribution-specific package managers, the packages are usually provided by the same distributions maintainers, making package breakages very unlikely. For package managers that ship packages directly provided by upstream (i.e. the maintainers of the software), the packages are usually more up-to-date with minimal security concerns, and upstream support is usually better. ==== Distribution Package Managers ==== Some package formats are specific to distributions. For [[Debian]]-based distributions, [[dpkg]] is used, and for [[Red Hat]] based distributions, [[rpm]] is used. In most cases, the matching package format must be used, otherwise installation is not possible. ==== Cross-platform Package Managers ==== Some package managers like [[flatpak]] and [[snap]] provide software support for different distributions, in the format of [[sandbox]]ing. While other repositories are available, the mainstream repo for Flatpak is [[Flathub]], which contains both [[open source]] and [[proprietary]] software. For snap, [[Canonical]] [[Snapcraft]] is the default snap repository. Common package managers that do not involve sandboxing include [[brew]], [[nix]]. Some [[Programming languages]] provide their own package manager such as [[pip]] and [[cargo]]. == AppImages == :''Main Article: [[AppImage]]'' When a software is not available as a package or in a repository, usually the second option is to use an '''AppImage''' provided by upstream. The same AppImage may be run on most [[Linux]] distributions as long as the [[architecture]] is correct. '''AppImages do not support updates'''. In many cases, users are required to download a newer version from upstream in order to update their AppImages. Software in AppImage formats are also significantly less optimised compared to ones provided by corresponding distributions. == Binaries == :''Main Article: [[Executable]]'' Sometimes upstream provides pre-compiled binaries (possibly in a [[tar]]ball) for users to download directly. These binaries are usually optimised to some degree, but may not run on obscure setups (e.g. older systems). == Manual Compilation == If the source code is available, users may manually [[compile]] the program. This produces an executable most optimised for the system, and possibly has the highest chance of working correctly. The major downside however is that this requires technical knowledge and takes time. == Tips and Tricks == === When NOT to use Flatpak === Refrain from installing the following types of software via flatpak and/or other sandboxing package managers. {| class="wikitable" ! Software !! Reason |- | [[Terminal]] emulators | These often only work properly when run directly on the host system. |- | [[CLI]]/[[TUI]] applications | The UX of flatpak isn't optimized for these types of applications. |- | Modded/Multi-instance game launchers (e.g. Minecraft launchers) | May require access to system libraries, and can be better managed by the user when not sandboxed. For example Minecraft launchers can easily access multiple [[JRE]] installations when not sandboxed. |- | Other appliactions that require manual modification of data files | Requires user to modify its data files regularly, applies in the same above case. |- | Applications that suffer major performance or technical issues due to sandboxing ([[IDE]]s, [[text editor]]s, [[file manager]]s, [[DAW]]s and other applications that rely on native [[plugin]] support like [[VST]]s or [[LV2]], etc.) | Usually require systems libraries to be present to work properly. |- | System components | Part of the [[OS]] |- | System [[library|libraries]] | Required to build or use the aforementioned packages |} === Searching for Packages === The '''third-party''' websites listed in this section are '''unaffiliated''' with All Things Linux and/or this wiki, and provide instructions that may be '''potentially dangerous''', which readers should clearly understand before proceeding with caution. [https://command-not-found.com/ command-not-found.com] may be used to search for common command-line utilities. While it provides command-line specific instructions for mainstream distributions, other distributions are not supported, and only a small set of packages are registered. [[pkgs.org]] [https://pkgs.org] provides command-line instructions for installing packages, alongside package information, with better UX for searching packages. Try searching for <code>/usr/bin/''binname''</code> when in doubt. Alternatively, [[Repology]] [https://repology.org] provides better coverage since it includes more third party repositories (including [[AUR]]), but comes with worse UX for searching packages (i.e. ''projects'' in Repology terms). Note that both websites support neither flatpak ([[Flathub]] [https://flathub.org]) nor snap (Canonical [[Snapcraft]] [https://snapcraft.io]) repositories, and users are required to manually visit their respective websites 6b289cccc7783e6de91a45e576e2be9015f245c3 4014 4007 2025-08-30T13:50:23Z Madonuko 140 add images and stuff…!? wikitext text/x-wiki {{Needs Citations}} A variety of ways for installing [[software]] are available on most [[Unix]]-like systems, which will be explained below. == Software Repositories == :''Main Article: [[Repository]]'' Software programs may be downloaded from a centralised software [[repository]], possibly in the format of ''packages'' or [[binary|binaries]]. This process could be manual or automatic — users may choose to download these software manually instead of using automation tools. In many cases however, the word ''repository'' refers to the latter, where a ''package manager'' is required to extract, decode, and install the contents of a package, as explained in the next section. [[File:KDE Discover home page.png|right|thumb|The home page of the [[KDE]] [[Discover]] program, showing popular and recommended software.]] === Package Managers === :''Main Article: [[Package manager]]'' Software distributed in the form of '''software packages''' may be installed via various ''package managers''. Some package managers are specific to a [[distribution]] (or a branch of distributions), while others may be used across different distributions or even different [[Operating system]]s. On this wiki, the start of a distribution page contains an info box that documents its main supported package managers. Consult the corresponding pages on how to use these package managers. In many cases this is the preferred way of installing software, as it's convenient to update all installed packages at once. For distribution-specific package managers, the packages are usually provided by the same distributions maintainers, making package breakages very unlikely. For package managers that ship packages directly provided by upstream (i.e. the maintainers of the software), the packages are usually more up-to-date with minimal security concerns, and upstream support is usually better. ==== Distribution Package Managers ==== Some package formats are specific to distributions. For [[Debian]]-based distributions, [[dpkg]] is used, and for [[Red Hat]] based distributions, [[rpm]] is used. In most cases, the matching package format must be used, otherwise installation is not possible. [[File:Flathub main website dark.png|right|thumb|The Flathub home featuring different flatpak packages]] ==== Cross-platform Package Managers ==== Some package managers like [[flatpak]] and [[snap]] provide software support for different distributions, in the format of [[sandbox]]ing. While other repositories are available, the mainstream repo for Flatpak is [[Flathub]], which contains both [[open source]] and [[proprietary]] software. For snap, [[Canonical]] [[Snapcraft]] is the default snap repository. Common package managers that do not involve sandboxing include [[brew]], [[nix]]. Some [[Programming languages]] provide their own package manager such as [[pip]] and [[cargo]]. [[File:AppImageHub home page.jpg|left|thumb|Home page of AppImageHub showing different software categories]] == AppImages == :''Main Article: [[AppImage]]'' When a software is not available as a package or in a repository, usually the second option is to use an '''AppImage''' provided by upstream. The same AppImage may be run on most [[Linux]] distributions as long as the [[architecture]] is correct. '''AppImages do not support updates'''. In many cases, users are required to download a newer version from upstream in order to update their AppImages. Software in AppImage formats are also significantly less optimised compared to ones provided by corresponding distributions. Some third-party services like [[AppImageHub]] provide centralised repositories of software for users to download manually. <div style="clear: both"></div> == Binaries == :''Main Article: [[Executable]]'' Sometimes upstream provides pre-compiled binaries (possibly in a [[tar]]ball) for users to download directly. These binaries are usually optimised to some degree, but may not run on obscure setups (e.g. older systems). == Manual Compilation == If the source code is available, users may manually [[compile]] the program. This produces an executable most optimised for the system, and possibly has the highest chance of working correctly. The major downside however is that this requires technical knowledge and takes time. == Tips, Tricks & Troubleshooting == === When NOT to use Flatpak === Refrain from installing the following types of software via flatpak and/or other sandboxing package managers. {| class="wikitable" ! Software !! Reason |- | [[Terminal]] emulators | These often only work properly when run directly on the host system. |- | [[CLI]]/[[TUI]] applications | The UX of flatpak isn't optimized for these types of applications. |- | Modded/Multi-instance game launchers (e.g. Minecraft launchers) | May require access to system libraries, and can be better managed by the user when not sandboxed. For example Minecraft launchers can easily access multiple [[JRE]] installations when not sandboxed. |- | Other appliactions that require manual modification of data files | Requires user to modify its data files regularly, applies in the same above case. |- | Applications that suffer major performance or technical issues due to sandboxing ([[IDE]]s, [[text editor]]s, [[file manager]]s, [[DAW]]s and other applications that rely on native [[plugin]] support like [[VST]]s or [[LV2]], etc.) | Usually require systems libraries to be present to work properly. |- | System components | Part of the [[OS]] |- | System [[library|libraries]] | Required to build or use the aforementioned packages |} === Finding Packages === The '''third-party''' websites listed in this section are '''unaffiliated''' with All Things Linux and/or this wiki, and provide instructions that may be '''potentially dangerous''', which readers should understand clearly before proceeding with caution. [[File:Command-not-found-com_vim_page.png|left|thumb|The vim page on [https://command-not-found.com/vim command-not-found.com]<nowiki/>]] [https://command-not-found.com/ command-not-found.com] may be used to search for common command-line utilities. While it provides command-line specific instructions for mainstream distributions, other distributions are not supported, and only a small set of packages are registered. [[File:Pkgs.org_search_zed.png|right|thumb|Searching ''Zed'' in package summaries on pkgs.org]] [[pkgs.org]] [https://pkgs.org] provides command-line instructions for installing packages, alongside package information, with better UX for searching packages. Try searching for <code>/usr/bin/''binname''</code> when in doubt. Alternatively, [[Repology]] [https://repology.org] provides better coverage since it includes more third party repositories (notably the [[AUR]]), but comes with worse UX for searching packages (i.e. ''projects'' in Repology terms). Note that the former does not include Canonical Snapcraft [https://snapcraft.io], while the latter supports neither Flathub [https://flathub.org] nor Snapcraft. Some distributions such as [[OpenSUSE]] [https://search.opensuse.org/packages/] also provide dedicated websites for finding packages provided by the distributions. === Missing or Broken Distribution Packages === When a package does not exist or breaks, bug reports or requests should be given to repository maintainers. Avoid reporting directly to upstream maintainers unless they directly maintain the packages in question (which applies to many Flathub packages). In the meantime, '''advanced''' users could try to mitigate the issue: ; Missing runtime dynamic libraries : In case of [[wikipedia:Dynamic linker|dynamically link]]ed programming languages, you may see the following errors:<syntaxhighlight lang="shell-session"> /usr/bin/my_program: error while loading shared libraries: libexample.so.0: cannot open shared object file: No such file or directory /usr/bin/my_program: symbol lookup error: /usr/lib64/libexample.so.0: undefined symbol: some_example_symbol_123</syntaxhighlight> : The former error indicates that the library required is not installed, so you can find the package that provides the dynamic library and install it, e.g. with pkgs.org or your package manager: ([[dnf]] example)<syntaxhighlight lang="shell-session"> # dnf install 'libexample.so.0()(64bit)' </syntaxhighlight> : For other package formats that do not support ''provides'', search the RPM provides on pkgs.org, click into any RPM packages, then search for the package corresponding to the distribution using the full [[soname]] [[path]] as shown in the list of files (e.g. <code>/usr/lib64/libexample.so.0</code>). : If the library could not be found, the compiled executable is probably out of date. : The latter error is a result of [[wikipedia:Application binary interface|ABI]] mismatch, and can only be solved by obtaining the correct library version. Make sure your system is up to date, then contact the package maintainer of <code>my_program</code>. Usually this indicates the program (<code>my_program</code> in this case) needs to be recompiled. ; Missing modules for scripting languages : For software written in scripting languages, you may see the following errors:<syntaxhighlight lang="shell-session"> $ example_python_program Traceback (most recent call last): ... ImportError: No module named my_module $ example_nodejs_program Error: Cannot find module 'my_module' ... </syntaxhighlight> : Then you can install these modules manually: ([[apt]]/[[pacman]] example)<syntaxhighlight lang="shell-session"> # apt install python3-my-module # pacman -Syu node-my-module </syntaxhighlight> 43d63be0ae3bd50b28bcdc4443b23d95f75fe73e 4041 4014 2025-09-02T07:20:53Z Madonuko 140 /* Missing or Broken Distribution Packages */ better format wikitext text/x-wiki {{Needs Citations}} A variety of ways for installing [[software]] are available on most [[Unix]]-like systems, which will be explained below. == Software Repositories == :''Main Article: [[Repository]]'' Software programs may be downloaded from a centralised software [[repository]], possibly in the format of ''packages'' or [[binary|binaries]]. This process could be manual or automatic — users may choose to download these software manually instead of using automation tools. In many cases however, the word ''repository'' refers to the latter, where a ''package manager'' is required to extract, decode, and install the contents of a package, as explained in the next section. [[File:KDE Discover home page.png|right|thumb|The home page of the [[KDE]] [[Discover]] program, showing popular and recommended software.]] === Package Managers === :''Main Article: [[Package manager]]'' Software distributed in the form of '''software packages''' may be installed via various ''package managers''. Some package managers are specific to a [[distribution]] (or a branch of distributions), while others may be used across different distributions or even different [[Operating system]]s. On this wiki, the start of a distribution page contains an info box that documents its main supported package managers. Consult the corresponding pages on how to use these package managers. In many cases this is the preferred way of installing software, as it's convenient to update all installed packages at once. For distribution-specific package managers, the packages are usually provided by the same distributions maintainers, making package breakages very unlikely. For package managers that ship packages directly provided by upstream (i.e. the maintainers of the software), the packages are usually more up-to-date with minimal security concerns, and upstream support is usually better. ==== Distribution Package Managers ==== Some package formats are specific to distributions. For [[Debian]]-based distributions, [[dpkg]] is used, and for [[Red Hat]] based distributions, [[rpm]] is used. In most cases, the matching package format must be used, otherwise installation is not possible. [[File:Flathub main website dark.png|right|thumb|The Flathub home featuring different flatpak packages]] ==== Cross-platform Package Managers ==== Some package managers like [[flatpak]] and [[snap]] provide software support for different distributions, in the format of [[sandbox]]ing. While other repositories are available, the mainstream repo for Flatpak is [[Flathub]], which contains both [[open source]] and [[proprietary]] software. For snap, [[Canonical]] [[Snapcraft]] is the default snap repository. Common package managers that do not involve sandboxing include [[brew]], [[nix]]. Some [[Programming languages]] provide their own package manager such as [[pip]] and [[cargo]]. [[File:AppImageHub home page.jpg|left|thumb|Home page of AppImageHub showing different software categories]] == AppImages == :''Main Article: [[AppImage]]'' When a software is not available as a package or in a repository, usually the second option is to use an '''AppImage''' provided by upstream. The same AppImage may be run on most [[Linux]] distributions as long as the [[architecture]] is correct. '''AppImages do not support updates'''. In many cases, users are required to download a newer version from upstream in order to update their AppImages. Software in AppImage formats are also significantly less optimised compared to ones provided by corresponding distributions. Some third-party services like [[AppImageHub]] provide centralised repositories of software for users to download manually. <div style="clear: both"></div> == Binaries == :''Main Article: [[Executable]]'' Sometimes upstream provides pre-compiled binaries (possibly in a [[tar]]ball) for users to download directly. These binaries are usually optimised to some degree, but may not run on obscure setups (e.g. older systems). == Manual Compilation == If the source code is available, users may manually [[compile]] the program. This produces an executable most optimised for the system, and possibly has the highest chance of working correctly. The major downside however is that this requires technical knowledge and takes time. == Tips, Tricks & Troubleshooting == === When NOT to use Flatpak === Refrain from installing the following types of software via flatpak and/or other sandboxing package managers. {| class="wikitable" ! Software !! Reason |- | [[Terminal]] emulators | These often only work properly when run directly on the host system. |- | [[CLI]]/[[TUI]] applications | The UX of flatpak isn't optimized for these types of applications. |- | Modded/Multi-instance game launchers (e.g. Minecraft launchers) | May require access to system libraries, and can be better managed by the user when not sandboxed. For example Minecraft launchers can easily access multiple [[JRE]] installations when not sandboxed. |- | Other appliactions that require manual modification of data files | Requires user to modify its data files regularly, applies in the same above case. |- | Applications that suffer major performance or technical issues due to sandboxing ([[IDE]]s, [[text editor]]s, [[file manager]]s, [[DAW]]s and other applications that rely on native [[plugin]] support like [[VST]]s or [[LV2]], etc.) | Usually require systems libraries to be present to work properly. |- | System components | Part of the [[OS]] |- | System [[library|libraries]] | Required to build or use the aforementioned packages |} === Finding Packages === The '''third-party''' websites listed in this section are '''unaffiliated''' with All Things Linux and/or this wiki, and provide instructions that may be '''potentially dangerous''', which readers should understand clearly before proceeding with caution. [[File:Command-not-found-com_vim_page.png|left|thumb|The vim page on [https://command-not-found.com/vim command-not-found.com]<nowiki/>]] [https://command-not-found.com/ command-not-found.com] may be used to search for common command-line utilities. While it provides command-line specific instructions for mainstream distributions, other distributions are not supported, and only a small set of packages are registered. [[File:Pkgs.org_search_zed.png|right|thumb|Searching ''Zed'' in package summaries on pkgs.org]] [[pkgs.org]] [https://pkgs.org] provides command-line instructions for installing packages, alongside package information, with better UX for searching packages. Try searching for <code>/usr/bin/''binname''</code> when in doubt. Alternatively, [[Repology]] [https://repology.org] provides better coverage since it includes more third party repositories (notably the [[AUR]]), but comes with worse UX for searching packages (i.e. ''projects'' in Repology terms). Note that the former does not include Canonical Snapcraft [https://snapcraft.io], while the latter supports neither Flathub [https://flathub.org] nor Snapcraft. Some distributions such as [[OpenSUSE]] [https://search.opensuse.org/packages/] also provide dedicated websites for finding packages provided by the distributions. === Missing or Broken Distribution Packages === When a package does not exist or breaks, bug reports or requests should be given to repository maintainers. Avoid reporting directly to upstream maintainers unless they directly maintain the packages in question (which applies to many Flathub packages). In the meantime, '''advanced''' users could try to mitigate the issue: ; Missing runtime dynamic libraries : In case of [[wikipedia:Dynamic linker|dynamically link]]ed programming languages, you may see the following errors:<syntaxhighlight lang="shell-session"> /usr/bin/my_program: error while loading shared libraries: libexample.so.0: cannot open shared object file: No such file or directory /usr/bin/my_program: symbol lookup error: /usr/lib64/libexample.so.0: undefined symbol: some_example_symbol_123</syntaxhighlight> : The former error indicates that the library required is not installed, so you can find the package that provides the dynamic library and install it, e.g. with pkgs.org or your package manager: ([[dnf]] example)<syntaxhighlight lang="shell-session"> # dnf install 'libexample.so.0()(64bit)' </syntaxhighlight> : For other package formats that do not support ''provides'': :# search the RPM provides on pkgs.org :# click into any RPM packages :# go to the files section and copy the full [[soname]] [[path]] (e.g. <code>/usr/lib64/libexample.so.0</code>) :# paste the file path into the search bar to search again : If the library could not be found, the compiled executable is probably out of date. : The latter error is a result of [[wikipedia:Application binary interface|ABI]] mismatch, and can only be solved by obtaining the correct library version. Make sure your system is up to date, then contact the package maintainer of <code>my_program</code>. Usually this indicates the program (<code>my_program</code> in this case) needs to be recompiled. ; Missing modules for scripting languages : For software written in scripting languages, you may see the following errors:<syntaxhighlight lang="shell-session"> $ example_python_program Traceback (most recent call last): ... ImportError: No module named my_module $ example_nodejs_program Error: Cannot find module 'my_module' ... </syntaxhighlight> : These modules may be installed manually in the meantime: ([[apt]]/[[pacman]] example)<syntaxhighlight lang="shell-session"> # apt install python3-my-module # pacman -Syu node-my-module </syntaxhighlight> 1180e5e0316e20a3dade7f9f871e8b9d681c7d0d 6 993 4008 2025-08-30T09:48:03Z Madonuko 140 wikitext text/x-wiki == Licensing == {{CC0}} 3f16ad18d78614720e9f206e6115a53bd34db67d 6 994 4009 2025-08-30T10:00:09Z Madonuko 140 wikitext text/x-wiki == Licensing == {{CC0}} 3f16ad18d78614720e9f206e6115a53bd34db67d 6 995 4010 2025-08-30T10:06:44Z Madonuko 140 wikitext text/x-wiki == Licensing == {{CC0}} 3f16ad18d78614720e9f206e6115a53bd34db67d 6 996 4011 2025-08-30T10:16:55Z Madonuko 140 wikitext text/x-wiki == Licensing == {{CC0}} 3f16ad18d78614720e9f206e6115a53bd34db67d 6 997 4012 2025-08-30T10:18:54Z Madonuko 140 wikitext text/x-wiki == Licensing == {{CC0}} 3f16ad18d78614720e9f206e6115a53bd34db67d 4015 4012 2025-08-30T15:30:48Z Madonuko 140 Madonuko uploaded a new version of [[File:KDE Discover home page.png]] wikitext text/x-wiki == Licensing == {{CC0}} 3f16ad18d78614720e9f206e6115a53bd34db67d 0 254 4013 3930 2025-08-30T11:33:30Z RelativeAlbatros 187 what to do when patch fails and when patches overwrite config.def.h - bump dwm version wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.6, 2025-08-09 | languages = C | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a window manager developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff if patch fails, you should check the .rej file, edit manually and recompile dwm. some patches edit config.def.h, you should then edit the Makefile to remove config.h during clean and copy config.def.h to config.h. == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == faf0116ece42691a082ca3e4442add02afcb5c8f 0 628 4016 3431 2025-08-31T13:33:29Z Persimmon 181 Add information about the 2016 Linux Mint website hack wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>[https://iso.atl.dev/l/linuxmint linuxmint - ATL ISO Archives], All Things Linux (Accessed: 2025-08-09)</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. In 2016, the Linux Mint website and forums were hacked and the installation images were infected with malware.<ref>{{Cite|url=https://www.pcworld.com/article/419713/hackers-planted-a-backdoor-inside-a-compromised-version-of-linux-mint.html|title=Linux Mint website hacked, ISO downloads replaced with backdoored operating system|author=Nick Mediati, PCWorld|year=2016|accessdate=2025.08.31}}</ref> The latest release, Linux Mint 22.1 "Xia", was launched in January 2025 and is supported until 2029.<ref>[https://www.linuxmint.com/download.php Download Linux Mint 22.1 - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> == References == 07d50db4d8866b9744f901eb8b82a004bfb9d976 0 998 4017 2025-09-01T18:19:58Z 0xFF 273 Add Dinit stub article wikitext text/x-wiki Dinit is a cross-platform service manager / supervision system.<ref>{{Cite|url=https://davmac.org/projects/dinit/|title=Dinit's official website.|accessdate=2025-09-01}}</ref> It was created by Davin McCall to fit in the middle ground between simple supervision suites and service managers. Dinit can be used as either a service manager or, on Linux, as a system manager / init system. == Distributions with Dinit == * Chimera Linux (as default)<ref>{{Cite|url=https://chimera-linux.org/about/|title=Chimera Linux - About|accessdate=2025-09-01}}</ref> * EweOS (as default)<ref>{{Cite|url=https://os.ewe.moe/about|title=EweOS {{!}} About|accessdate=2025-09-01}}</ref> * Artix Linux (as an official alternative) <!-- Can't find a good source for this (other than the download page), but it looks like it's supported --> 16224a106f95b016b949e4c2a8579bc53690bbe6 4018 4017 2025-09-01T18:21:43Z 0xFF 273 Mark as stub (this article is very short) wikitext text/x-wiki {{Stub}} Dinit is a cross-platform service manager / supervision system.<ref>{{Cite|url=https://davmac.org/projects/dinit/|title=Dinit's official website.|accessdate=2025-09-01}}</ref> It was created by Davin McCall to fit in the middle ground between simple supervision suites and service managers. Dinit can be used as either a service manager or, on Linux, as a system manager / init system. == Distributions with Dinit == * Chimera Linux (as default)<ref>{{Cite|url=https://chimera-linux.org/about/|title=Chimera Linux - About|accessdate=2025-09-01}}</ref> * EweOS (as default)<ref>{{Cite|url=https://os.ewe.moe/about|title=EweOS {{!}} About|accessdate=2025-09-01}}</ref> * Artix Linux (as an official alternative) <!-- Can't find a good source for this (other than the download page), but it looks like it's supported --> e243162013629211daf2fb5322090389dc9fe681 4055 4018 2025-09-02T12:37:43Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} Dinit is a cross-platform service manager / supervision system.<ref>{{Cite|url=https://davmac.org/projects/dinit/|title=Dinit's official website.|accessdate=2025-09-01}}</ref> It was created by Davin McCall to fit in the middle ground between simple supervision suites and service managers. Dinit can be used as either a service manager or, on Linux, as a system manager / init system. == Distributions with Dinit == * Chimera Linux (as default)<ref>{{Cite|url=https://chimera-linux.org/about/|title=Chimera Linux - About|accessdate=2025-09-01}}</ref> * EweOS (as default)<ref>{{Cite|url=https://os.ewe.moe/about|title=EweOS {{!}} About|accessdate=2025-09-01}}</ref> * Artix Linux (as an official alternative) <!-- Can't find a good source for this (other than the download page), but it looks like it's supported --> 688482e45c386267c9f061733f32ff17e723eea3 0 169 4019 3656 2025-09-01T18:24:05Z 0xFF 273 Capitalize Bedrock Linux to match other distribution names wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories == List of Package Managers == All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained by the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper]/[[Rpm]], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [https://voidlinux.org Void Linux], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[Bedrock Linux]]'s special use cases. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] * [[Homebrew]] (or just brew) was originally created as a package manager for macOS, but it has Linux support too. You can install it on almost any distribution as an alternative package manager. You can find more information about it on [https://brew.sh/ the official website], the source is hosted [https://github.com/Homebrew/brew on GitHub] 822de0be6ed3165a9cc376238b761b44eed4e1fe 4025 4019 2025-09-01T18:50:20Z 0xFF 273 Change external link to voidlinux.org to internal wiki link to match the other links. wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories == List of Package Managers == All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained by the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper]/[[Rpm]], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [[Void Linux]], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[Bedrock Linux]]'s special use cases. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] * [[Homebrew]] (or just brew) was originally created as a package manager for macOS, but it has Linux support too. You can install it on almost any distribution as an alternative package manager. You can find more information about it on [https://brew.sh/ the official website], the source is hosted [https://github.com/Homebrew/brew on GitHub] 496935cbb156c9ea3a46f161d9129e847aed365a 0 905 4020 3850 2025-09-01T18:28:14Z 0xFF 273 Change all instances of "distro's" to "distributions". wikitext text/x-wiki {{Guide Warning}} {{DistributionInfobox | title = Bedrock Linux | image = [[File:Bedrock Linux.png|Bedrock_Linux]] | caption = Bedrock Linux Logo | releasestatus = Maintained | packagemanager = [[pmm]] | releasemodel = Meta distribution | usagetype = Desktop/Server | defaultdesktops = None | architectures = x86_64, s390x, ppc64le, ppc64, ppc, mipsel, mips64el, mips, i686, i586, i486, i386, armv7l, armv7hl, aarch64 | website = [https://bedrocklinux.org bedrocklinux.org] }} [[Category:Linux Distributions]] '''Bedrock Linux''' is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. Bedrock integrates these components into one largely cohesive system. <ref>https://bedrocklinux.org</ref> === Distro compatibility === While Bedrock works fine with most distributions, there are distributions which can cause issues with Bedrock. The best examples are * Distributions that use BSD-like sysvinit * Distributions that use GRUB+BTRFS (due to a bug in GRUB <ref>https://bedrocklinux.org/0.7/feature-compatibility.html#grub-btrfs-zfs</ref>) * Immutable distributions * Non FHS-compliant distributions like [[NixOS]] or [[GUIX]] === Installation === The Bedrock Linux website provides a hijack script which can be used to convert current Linux distribution to Bedrock Linux <ref>https://bedrocklinux.org/0.7/installation-instructions.html</ref> === Going through the tutorial === Bedrock Linux provides an interactive tutorial which can be accessed with <code>brl tutorial basics</code>, but also a text version for those who prefer those <ref>https://bedrocklinux.org/0.7/basic-usage.html</ref> === Known issues === ==== brl update and brl fetch fail with proxy ==== With some specific URL's brl fetch and brl update might fail For brl update, possible work-arounds include: * Downloading the update with some other software and providing it as the parameter to brl update * Configuring brl update to use another Bedrock mirror. There are no obvious work-arounds for brl fetch. ==== Unmount warnings on shutdown ==== Those are harmless warnings, which are caused by Bedrock using a Linux kernel feature which propagates some mount and unmount operations, Which causes some init systems to be confused by this and show warnings about being unable to unmount directories because they were already unmounted ==== Root filesystem fsck may be skipped ==== Because of a quirk in how Bedrock works, init systems might not mount the root directory read-only in preparation for fsck, Bedrock does attempt to disable this by changing the corresponding field in <code>/etc/fstab</code> Some initrds will <code>fsck</code> the root filesystem, but not all. Bedrock should offer the option to call <code>fsck</code> on the root filesystem, but it currently does not <ref>https://bedrocklinux.org/0.7/known-issues.html</ref> == References == <references /> 3833d1970eecf2ae869188c2970d3aecdfb153c2 4021 4020 2025-09-01T18:32:51Z 0xFF 273 Cite source for distribution compatibility wikitext text/x-wiki {{Guide Warning}} {{DistributionInfobox | title = Bedrock Linux | image = [[File:Bedrock Linux.png|Bedrock_Linux]] | caption = Bedrock Linux Logo | releasestatus = Maintained | packagemanager = [[pmm]] | releasemodel = Meta distribution | usagetype = Desktop/Server | defaultdesktops = None | architectures = x86_64, s390x, ppc64le, ppc64, ppc, mipsel, mips64el, mips, i686, i586, i486, i386, armv7l, armv7hl, aarch64 | website = [https://bedrocklinux.org bedrocklinux.org] }} [[Category:Linux Distributions]] '''Bedrock Linux''' is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. Bedrock integrates these components into one largely cohesive system. <ref>https://bedrocklinux.org</ref> === Distro compatibility === While Bedrock works fine with most distributions, there are distributions which can cause issues with Bedrock. The best examples are:<ref>{{Cite|url=https://bedrocklinux.org/0.7/distro-compatibility.html|title=Bedrock Linux 0.7 Poki Distro Support|accessdate=2025-09-01}}</ref> * Distributions that use BSD-like sysvinit * Distributions that use GRUB+BTRFS (due to a bug in GRUB <ref>https://bedrocklinux.org/0.7/feature-compatibility.html#grub-btrfs-zfs</ref>) * Immutable distributions * Non FHS-compliant distributions like [[NixOS]] or [[GUIX]] === Installation === The Bedrock Linux website provides a hijack script which can be used to convert current Linux distribution to Bedrock Linux <ref>https://bedrocklinux.org/0.7/installation-instructions.html</ref> === Going through the tutorial === Bedrock Linux provides an interactive tutorial which can be accessed with <code>brl tutorial basics</code>, but also a text version for those who prefer those <ref>https://bedrocklinux.org/0.7/basic-usage.html</ref> === Known issues === ==== brl update and brl fetch fail with proxy ==== With some specific URL's brl fetch and brl update might fail For brl update, possible work-arounds include: * Downloading the update with some other software and providing it as the parameter to brl update * Configuring brl update to use another Bedrock mirror. There are no obvious work-arounds for brl fetch. ==== Unmount warnings on shutdown ==== Those are harmless warnings, which are caused by Bedrock using a Linux kernel feature which propagates some mount and unmount operations, Which causes some init systems to be confused by this and show warnings about being unable to unmount directories because they were already unmounted ==== Root filesystem fsck may be skipped ==== Because of a quirk in how Bedrock works, init systems might not mount the root directory read-only in preparation for fsck, Bedrock does attempt to disable this by changing the corresponding field in <code>/etc/fstab</code> Some initrds will <code>fsck</code> the root filesystem, but not all. Bedrock should offer the option to call <code>fsck</code> on the root filesystem, but it currently does not <ref>https://bedrocklinux.org/0.7/known-issues.html</ref> == References == <references /> c5250357d715520c67619ba425962bbde59783c9 0 198 4022 3752 2025-09-01T18:37:29Z 0xFF 273 Add Bedrock Linux to "Other Independent Distributions" section wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == 8f67843ae1930e3df5c48ffab292682dc538bc6c 0 886 4023 3812 2025-09-01T18:39:44Z 0xFF 273 Fix typo ("the a version of...") wikitext text/x-wiki [[Category:Software]] {{Needs Citations|date=august 2025}} {{stub|date=august 2025}} The vi program is a full-screen console-based text editor. It was originally written in the 1970s by Bill Joy, as an enhancement for [[ex]], which in tern was an enhanced version of [[ed]]. As such, vi still has many ex-like features today. ==Using vi== To use vi, you can hit <code>i</code> or <code>a</code> (append) to enter "insert mode". You then may type what you wish, and hit the <code>esc</code> key to exit "insert mode". When you're no longer in "insert mode", you can hit the ":" (colon) command to type in ex-like commands. The two most common commands are <code>w [filename]</code> to save the file, and <code>q</code>, which is used to quit the program. These commands can be combined to quit and save in one step, like so: <code>wq</code>. To quit without saving, enter <code>q!</code>. When not in insert mode, you may use the <code>h</code> key to move back one column, <code>j</code> to move the cursor down one line, <code>k</code> to move up a line, and the <code>l</code> to move forward one column. Please note that these letters are lowercase. As is often the case with Unix programs, capitalization matters. Also, when in insert mode, you <i>might</i> be able to use your arrow keys, although this seems to depend on which implementation of vi you are using. It is generally recommended to learn the above keys instead. ==Implementations== Modern implementations of vi consist of [[vim]], [[neovim]], [[elvis]], [[nvi]], and the version of vi built in to [[busybox]], the latter of which can be called via <code>busybox vi</code>. nvi/nex is a replacement for vi/ex and was originally developed as part of 4BSD.<ref>https://man.openbsd.org/vi.1</ref> 4ccbb7fd534ea822bfdec7d27799907bb7a8772c 1 999 4024 2025-09-01T18:41:23Z 0xFF 273 /* Safe to remove the nvi explanation sentence? */ new section wikitext text/x-wiki == Safe to remove the nvi explanation sentence? == Would it be safe to remove "nvi/nex is a replacement for vi/ex and was originally developed as part of 4BSD", since the nvi page has already been created? [[User:0xFF|0xFF]] ([[User talk:0xFF|talk]]) 18:41, 1 September 2025 (UTC) 69ae24f37c5f54a06fae1aaf4fd5440e2b1f96d3 0 575 4026 3732 2025-09-01T18:52:51Z 0xFF 273 Fix formatting in Emacs page; a disaster went down in here wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository]{{Dead Link|2025-08-14|timeout (8)}}, 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <sup>🍣DEAD?]{{Dead Link|2025-08-14|timeout (8)}}</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |Control | |- |<code>M-</code> |Meta |This is the Alt or Option key |- |<code>S-</code> |Shift | |- |<code>s-</code> |Super |This is the Windows or Command key |- |<code>RET</code> | Return | Enter key |- |<code>H-</code> |Hyper |This key is supported, but no default bindings use it |- |<code>A-</code> |Alt* |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys| |}Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents <code>Ctrl+Shift+a</code>. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the Control key and press <code>x s</code> in quick succession. This can help reduce strain on the pinky from frequently pressing the Control key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == fd8ecd9da9bdb80fa7727c350442970204b7a7bf 4040 4026 2025-09-02T03:11:28Z Madonuko 140 /* Keybindings */ use [[Template:Keypress]] wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository]{{Dead Link|2025-08-14|timeout (8)}}, 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <sup>🍣DEAD?]{{Dead Link|2025-08-14|timeout (8)}}</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == 8b5bd44a708e3821ce370118c9709bd1465eb1ce 0 823 4027 3618 2025-09-01T19:00:53Z 0xFF 273 Mark Geeko page as a stub (only 1 sentence) wikitext text/x-wiki {{Stub}} [[Category:Mascots]] [[File:OpenSUSE Button.svg|alt=Geeko is a chameleon drawing and is the mascot for openSUSE.|thumb]] '''Geeko''' is the official mascot of [[openSUSE]]. It is a chameleon and not a gecko.<ref>https://en.opensuse.org/openSUSE:Geeko, openSUSE, 2010-07-14 (Accessed: 9 August 2025). </ref> == References == <references /> f89e777c4f5d56fb77a73186d6df664cb1d20f9a 6 1000 4028 2025-09-01T20:10:14Z Satnus 215 Springdale Linux logo straight from the official website. wikitext text/x-wiki == Summary == Springdale Linux logo straight from the official website. == Licensing == {{Unknown_copyright}} c4aaaccca61b61cc804a328cc6f275809f15ced3 0 257 4029 3625 2025-09-01T21:49:42Z Fluffinity 271 Adding mentions to Hyprlock and Hyprpicker in the list of companion utilities wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.40.0, 2024-05-04 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor built on [[wlroots]]. It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Hyprland], 2025-08-10 (Accessed: 2025-08-10)</ref> Hyprland uses its own configuration syntax, designed to be readable and easy to learn, with similarities to shell scripting. The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. * '''Hyprlock''' - a highly customizable and efficient Wayland lockscreen * '''Hyprpicker''' - a small utility for picking a color on your current screen == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway (window manager)|Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> f6c15c5eb2fa542f3f13320455c146015674ecda 4030 4029 2025-09-01T22:05:00Z Fluffinity 271 Updating Hyprland history to mention the transition from wlroots to aquamarine wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.40.0, 2024-05-04 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor. It was originally based on [[wlroots]] but migrated away from it towards its own rendering backend library [[aquamarine]] in version 0.42.0<ref>[https://hypr.land/news/independentHyprland/ Hyprland moves off wlroots], 2025-09-02 (Accessed 2025-09-02)</ref> It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Hyprland], 2025-08-10 (Accessed: 2025-08-10)</ref> Hyprland uses its own configuration syntax, designed to be readable and easy to learn, with similarities to shell scripting. The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. * '''Hyprlock''' - a highly customizable and efficient Wayland lockscreen * '''Hyprpicker''' - a small utility for picking a color on your current screen == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway (window manager)|Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> ded8d9e861827a5e11562d9a9a6a02d10daeeb79 4031 4030 2025-09-01T22:06:02Z Fluffinity 271 Update latest Hyprland release version and date wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.50.0, 2025-07-16 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor. It was originally based on [[wlroots]] but migrated away from it towards its own rendering backend library [[aquamarine]] in version 0.42.0<ref>[https://hypr.land/news/independentHyprland/ Hyprland moves off wlroots], 2025-09-02 (Accessed 2025-09-02)</ref> It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Hyprland], 2025-08-10 (Accessed: 2025-08-10)</ref> Hyprland uses its own configuration syntax, designed to be readable and easy to learn, with similarities to shell scripting. The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. * '''Hyprlock''' - a highly customizable and efficient Wayland lockscreen * '''Hyprpicker''' - a small utility for picking a color on your current screen == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway (window manager)|Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> 82f11935f4949815bb3b1e0b3a5cfa723f1965b3 6 1001 4032 2025-09-01T22:31:52Z Bont 128 wikitext text/x-wiki the green variant of the Fedora panda logo 2afec5d19ee0b02d783c39f6dbaabdd88ebaee66 6 1002 4033 2025-09-01T22:33:56Z Bont 128 wikitext text/x-wiki fedora badger 7ec619c0d2e5c0a53fe4642278dd2fb9cba5faa0 6 1003 4034 2025-09-01T22:36:07Z Bont 128 wikitext text/x-wiki fedora beefy cf821ffa64e1cdf52e87664fc3a3cee77f8c6c20 6 1004 4035 2025-09-01T22:37:51Z Bont 128 wikitext text/x-wiki fedoras colur logo 333bcb827a10b3da3bce6be42178ea1ca714323e 14 390 4036 3933 2025-09-01T22:38:49Z Bont 128 Added Fedora mascots wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[FreeBSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] |[[Linux]] |} efbb2677ddf240d1e69d76911f4e489b15b43cd2 4037 4036 2025-09-01T22:47:55Z Bont 128 add wilber wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[FreeBSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|64x64px]] |[[Wilber]] |[https://www.gimp.org GIMP] |} 3ed822dbb76a5fc0cd04cb7a0947bb470e3d1601 2 3 4038 3715 2025-09-02T02:26:15Z Amadaluzia 52 Respond to an email technically wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">// Hey drew@! // Phone drowned and I would really like to have 2FA removed at the moment. // This is related to the email you have sent me at 01/09, 08:11 AM GMT+1. // Cheers, amad@ #include <string> #include <functional> #include <print> using String = std::string; class Person { virtual String description() = 0; }; using SocialPair = struct { String service; String username; }; class Amadaluzia : Person { public: String name = "Artur Manuel"; int age = 17; std::vector<String> interests{ "Programming", "CLI development", "GUI development", "Web development", "Library development", "System administration", "Walking", "Climbing", "Math", "Learning", "Exercise", "Sports", "Socialising", "Writing", "Photography", "Video editing", "Movie production", "Techno music", "Shoegaze", "Alternative Rock", }; std::vector<SocialPair> socials = { {"Email", "amad@atl.tools"}, {"Email (tutanota.com alt)", "amadaluzia@tutanota.com"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Matrix (pub.solar alt)", "@amadaluzia:pub.solar"}, {"Matrix (envs.net alt)", "@amadaluzia:envs.net"}, {"libera.chat", "amadaluzia"}, {"oftc.net", "amadaluzia"}, {"Revolt", "amadaluzia#3242"}, {"Mastodon", "@amadaluzia@bsd.cafe"}, {"Discord", "amadaluzia"}, {"Discord (alt)", "balke.nix"}, {"Keyoxide": "aspe:keyoxide.org:ZV3A66CSCNOS7V4N5A4DOD57I4"}, }; String description() override; }; String Amadaluzia::description() { String result{}; result += std::format("Good day, my name is {}, commonly known online as \"amadaluzia\". I am a {}\n", name, age); result += "year old Portuguese-Italian resident of the UK. You may have seen me in many\n"; result += "programming spaces, however, I am keenly interested in many other topics. More\n"; result += "specifically, I am interested in:\n"; for (auto interest : interests) result += std::format("- {}\n", interest); result += "I am also present on many social media platforms, even multiple times! Moreover, I\n"; result += "have pretty much the same name everywhere, so you can reliably find me. But I will\n"; result += "share my social platforms here as I use many decentralised services. Here I am:\n"; for (auto const &[service, username] : socials) result += std::format("- {} on {}\n", username, service); result += "\nIf you can find any ways of optimising this program, let me know, as long as the\n"; result += "it's kept to Amadaluzia::description(). Thank you for reading!\n"; return result; } int main(void) { Amadaluzia amadaluzia; std::println("{}", amadaluzia.description()); }</syntaxhighlight> 53b4e9ce1535d9a24ef078eebb49c818fe0e835d 4039 4038 2025-09-02T02:28:09Z Amadaluzia 52 add a bit more context wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">// Hey drew@! // Phone drowned and I would really like to have 2FA removed at the moment. // The username is `amadaluzia`. // This is related to the email you have sent me at 01/09, 08:11 AM GMT+1. // Cheers, amad@ #include <string> #include <functional> #include <print> using String = std::string; class Person { virtual String description() = 0; }; using SocialPair = struct { String service; String username; }; class Amadaluzia : Person { public: String name = "Artur Manuel"; int age = 17; std::vector<String> interests{ "Programming", "CLI development", "GUI development", "Web development", "Library development", "System administration", "Walking", "Climbing", "Math", "Learning", "Exercise", "Sports", "Socialising", "Writing", "Photography", "Video editing", "Movie production", "Techno music", "Shoegaze", "Alternative Rock", }; std::vector<SocialPair> socials = { {"Email", "amad@atl.tools"}, {"Email (tutanota.com alt)", "amadaluzia@tutanota.com"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Matrix (pub.solar alt)", "@amadaluzia:pub.solar"}, {"Matrix (envs.net alt)", "@amadaluzia:envs.net"}, {"libera.chat", "amadaluzia"}, {"oftc.net", "amadaluzia"}, {"Revolt", "amadaluzia#3242"}, {"Mastodon", "@amadaluzia@bsd.cafe"}, {"Discord", "amadaluzia"}, {"Discord (alt)", "balke.nix"}, {"Keyoxide", "aspe:keyoxide.org:ZV3A66CSCNOS7V4N5A4DOD57I4"}, {"GitHub", "amadaluzia"}, {"SourceHut", "amadaluzia"}, {"Codeberg", "amadaluzia"}, {"GitLab", "amadaluzia"}, }; String description() override; }; String Amadaluzia::description() { String result{}; result += std::format("Good day, my name is {}, commonly known online as \"amadaluzia\". I am a {}\n", name, age); result += "year old Portuguese-Italian resident of the UK. You may have seen me in many\n"; result += "programming spaces, however, I am keenly interested in many other topics. More\n"; result += "specifically, I am interested in:\n"; for (auto interest : interests) result += std::format("- {}\n", interest); result += "I am also present on many social media platforms, even multiple times! Moreover, I\n"; result += "have pretty much the same name everywhere, so you can reliably find me. But I will\n"; result += "share my social platforms here as I use many decentralised services. Here I am:\n"; for (auto const &[service, username] : socials) result += std::format("- {} on {}\n", username, service); result += "\nIf you can find any ways of optimising this program, let me know, as long as the\n"; result += "it's kept to Amadaluzia::description(). Thank you for reading!\n"; return result; } int main(void) { Amadaluzia amadaluzia; std::println("{}", amadaluzia.description()); }</syntaxhighlight> 267ad689cb6c813411c43e5d55637ceb13579bc3 0 1005 4042 2025-09-02T07:22:53Z Madonuko 140 init from [[User:Madonuko/Installing Software]] wikitext text/x-wiki {{Needs Citations}} A variety of ways for installing [[software]] are available on most [[Unix]]-like systems, which will be explained below. == Software Repositories == :''Main Article: [[Repository]]'' Software programs may be downloaded from a centralised software [[repository]], possibly in the format of ''packages'' or [[binary|binaries]]. This process could be manual or automatic — users may choose to download these software manually instead of using automation tools. In many cases however, the word ''repository'' refers to the latter, where a ''package manager'' is required to extract, decode, and install the contents of a package, as explained in the next section. [[File:KDE Discover home page.png|right|thumb|The home page of the [[KDE]] [[Discover]] program, showing popular and recommended software.]] === Package Managers === :''Main Article: [[Package manager]]'' Software distributed in the form of '''software packages''' may be installed via various ''package managers''. Some package managers are specific to a [[distribution]] (or a branch of distributions), while others may be used across different distributions or even different [[Operating system]]s. On this wiki, the start of a distribution page contains an info box that documents its main supported package managers. Consult the corresponding pages on how to use these package managers. In many cases this is the preferred way of installing software, as it's convenient to update all installed packages at once. For distribution-specific package managers, the packages are usually provided by the same distributions maintainers, making package breakages very unlikely. For package managers that ship packages directly provided by upstream (i.e. the maintainers of the software), the packages are usually more up-to-date with minimal security concerns, and upstream support is usually better. ==== Distribution Package Managers ==== Some package formats are specific to distributions. For [[Debian]]-based distributions, [[dpkg]] is used, and for [[Red Hat]] based distributions, [[rpm]] is used. In most cases, the matching package format must be used, otherwise installation is not possible. [[File:Flathub main website dark.png|right|thumb|The Flathub home featuring different flatpak packages]] ==== Cross-platform Package Managers ==== Some package managers like [[flatpak]] and [[snap]] provide software support for different distributions, in the format of [[sandbox]]ing. While other repositories are available, the mainstream repo for Flatpak is [[Flathub]], which contains both [[open source]] and [[proprietary]] software. For snap, [[Canonical]] [[Snapcraft]] is the default snap repository. Common package managers that do not involve sandboxing include [[brew]], [[nix]]. Some [[Programming languages]] provide their own package manager such as [[pip]] and [[cargo]]. [[File:AppImageHub home page.jpg|left|thumb|Home page of AppImageHub showing different software categories]] == AppImages == :''Main Article: [[AppImage]]'' When a software is not available as a package or in a repository, usually the second option is to use an '''AppImage''' provided by upstream. The same AppImage may be run on most [[Linux]] distributions as long as the [[architecture]] is correct. '''AppImages do not support updates'''. In many cases, users are required to download a newer version from upstream in order to update their AppImages. Software in AppImage formats are also significantly less optimised compared to ones provided by corresponding distributions. Some third-party services like [[AppImageHub]] provide centralised repositories of software for users to download manually. <div style="clear: both"></div> == Binaries == :''Main Article: [[Executable]]'' Sometimes upstream provides pre-compiled binaries (possibly in a [[tar]]ball) for users to download directly. These binaries are usually optimised to some degree, but may not run on obscure setups (e.g. older systems). == Manual Compilation == If the source code is available, users may manually [[compile]] the program. This produces an executable most optimised for the system, and possibly has the highest chance of working correctly. The major downside however is that this requires technical knowledge and takes time. == Tips, Tricks & Troubleshooting == === When NOT to use Flatpak === Refrain from installing the following types of software via flatpak and/or other sandboxing package managers. {| class="wikitable" ! Software !! Reason |- | [[Terminal]] emulators | These often only work properly when run directly on the host system. |- | [[CLI]]/[[TUI]] applications | The UX of flatpak isn't optimized for these types of applications. |- | Modded/Multi-instance game launchers (e.g. Minecraft launchers) | May require access to system libraries, and can be better managed by the user when not sandboxed. For example Minecraft launchers can easily access multiple [[JRE]] installations when not sandboxed. |- | Other appliactions that require manual modification of data files | Requires user to modify its data files regularly, applies in the same above case. |- | Applications that suffer major performance or technical issues due to sandboxing ([[IDE]]s, [[text editor]]s, [[file manager]]s, [[DAW]]s and other applications that rely on native [[plugin]] support like [[VST]]s or [[LV2]], etc.) | Usually require systems libraries to be present to work properly. |- | System components | Part of the [[OS]] |- | System [[library|libraries]] | Required to build or use the aforementioned packages |} === Finding Packages === The '''third-party''' websites listed in this section are '''unaffiliated''' with All Things Linux and/or this wiki, and provide instructions that may be '''potentially dangerous''', which readers should understand clearly before proceeding with caution. [[File:Command-not-found-com_vim_page.png|left|thumb|The vim page on [https://command-not-found.com/vim command-not-found.com]<nowiki/>]] [https://command-not-found.com/ command-not-found.com] may be used to search for common command-line utilities. While it provides command-line specific instructions for mainstream distributions, other distributions are not supported, and only a small set of packages are registered. [[File:Pkgs.org_search_zed.png|right|thumb|Searching ''Zed'' in package summaries on pkgs.org]] [[pkgs.org]] [https://pkgs.org] provides command-line instructions for installing packages, alongside package information, with better UX for searching packages. Try searching for <code>/usr/bin/''binname''</code> when in doubt. Alternatively, [[Repology]] [https://repology.org] provides better coverage since it includes more third party repositories (notably the [[AUR]]), but comes with worse UX for searching packages (i.e. ''projects'' in Repology terms). Note that the former does not include Canonical Snapcraft [https://snapcraft.io], while the latter supports neither Flathub [https://flathub.org] nor Snapcraft. Some distributions such as [[OpenSUSE]] [https://search.opensuse.org/packages/] also provide dedicated websites for finding packages provided by the distributions. === Missing or Broken Distribution Packages === When a package does not exist or breaks, bug reports or requests should be given to repository maintainers. Avoid reporting directly to upstream maintainers unless they directly maintain the packages in question (which applies to many Flathub packages). In the meantime, '''advanced''' users could try to mitigate the issue: ; Missing runtime dynamic libraries : In case of [[wikipedia:Dynamic linker|dynamically link]]ed programming languages, you may see the following errors:<syntaxhighlight lang="shell-session"> /usr/bin/my_program: error while loading shared libraries: libexample.so.0: cannot open shared object file: No such file or directory /usr/bin/my_program: symbol lookup error: /usr/lib64/libexample.so.0: undefined symbol: some_example_symbol_123</syntaxhighlight> : The former error indicates that the library required is not installed, so you can find the package that provides the dynamic library and install it, e.g. with pkgs.org or your package manager: ([[dnf]] example)<syntaxhighlight lang="shell-session"> # dnf install 'libexample.so.0()(64bit)' </syntaxhighlight> : For other package formats that do not support ''provides'': :# search the RPM provides on pkgs.org :# click into any RPM packages :# go to the files section and copy the full [[soname]] [[path]] (e.g. <code>/usr/lib64/libexample.so.0</code>) :# paste the file path into the search bar to search again : If the library could not be found, the compiled executable is probably out of date. : The latter error is a result of [[wikipedia:Application binary interface|ABI]] mismatch, and can only be solved by obtaining the correct library version. Make sure your system is up to date, then contact the package maintainer of <code>my_program</code>. Usually this indicates the program (<code>my_program</code> in this case) needs to be recompiled. ; Missing modules for scripting languages : For software written in scripting languages, you may see the following errors:<syntaxhighlight lang="shell-session"> $ example_python_program Traceback (most recent call last): ... ImportError: No module named my_module $ example_nodejs_program Error: Cannot find module 'my_module' ... </syntaxhighlight> : These modules may be installed manually in the meantime: ([[apt]]/[[pacman]] example)<syntaxhighlight lang="shell-session"> # apt install python3-my-module # pacman -Syu node-my-module </syntaxhighlight> 1180e5e0316e20a3dade7f9f871e8b9d681c7d0d 0 1006 4043 2025-09-02T07:23:24Z Madonuko 140 #REDIRECT [[Installing software]] wikitext text/x-wiki #REDIRECT [[Installing software]] 7757963adf106728bd94068495a3afffbf592f86 0 781 4044 3811 2025-09-02T07:33:35Z Madonuko 140 cleanup and strip unrelated info wikitext text/x-wiki {{stub}} {{Needs Citations}} [[Category:Package Managers]] '''RPM''' stands for '''Red Hat Package Manager'''. It is both a package format (<code>.rpm</code>) and the name of the [[package]] management system used primarily in [[Red Hat]]-based [[Linux distributions]], including: * [[Red Hat Enterprise Linux]] (RHEL) * [[Fedora]] Linux * [[CentOS]] * [[AlmaLinux]] * [[Rocky Linux]] * [[openSUSE]] == Overview == An RPM package is a file that contains: * Compiled software binaries * Configuration files * Metadata (name, version, dependencies, etc.) * Installation and removal scripts The standard file extension is <code>.rpm</code>. == Components of an RPM Package == * <b>Header</b>: Contains metadata (name, version, architecture, etc.) * <b>Payload</b>: The actual files to be installed * <b>Scripts</b>: Optional pre/post-install and removal scripts == Common Tools == * <code>rpm</code> — Low-level tool for querying, installing, and removing RPM packages * <code>rpmbuild</code> — Tool for building RPM packages from SPEC files * <code>rpmlint</code> — Linter to check RPM quality and packaging errors == Basic Commands == === Installing an RPM file === <syntaxhighlight lang="bash"> sudo rpm -ivh package.rpm </syntaxhighlight> === Query installed packages === <syntaxhighlight lang="bash"> rpm -q package-name </syntaxhighlight> === List all installed RPMs === <syntaxhighlight lang="bash"> rpm -qa </syntaxhighlight> === Remove a package === <syntaxhighlight lang="bash"> sudo rpm -e package-name </syntaxhighlight> === Verify a package === <syntaxhighlight lang="bash"> rpm -V package-name </syntaxhighlight> == Advantages == * Dependency tracking * Transaction-based installation/removal * Clean upgrade paths * Strong ecosystem support (DNF, YUM, repositories, etc.) == Limitations == * Requires careful dependency management * Binary format — not human-readable == External Resources == * [https://rpm.org/ Official RPM Site] * [https://fedoraproject.org/wiki/RPM Fedora RPM Guide] * [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Fedora Packaging Guidelines] == See Also == * [[yum]] * [[dnf]] * [[rpmbuild]] * [[zypper]] c46ea9db5921ba0c7fe0c5e19d571e8934f423c6 0 1007 4045 2025-09-02T08:07:58Z Madonuko 140 init wikitext text/x-wiki {{stub}} [[Category:Terminology]] The term '''package''' refers to designated file [[archive]]s, containing metadata, and files for a piece of [[software]], a desktop theme, configurations for a program, a font, etc., and bundling these files could benefit a significant group of users.<ref>[https://www.geeksforgeeks.org/linux-unix/understanding-package-managers-and-systemctl/ Understanding Package Managers and systemctl], GeeksforGeeks, 2025-07-23 (Accessed: 2025-09-02)</ref><ref>[https://www.howtouselinux.com/post/understanding-package-management-a-guide-to-package-managers-in-linux Understanding Package Management: A Guide to Package Managers in Linux], David Cao, 2023-10-09 (Accessed: 2025-09-02)</ref><ref>[https://linuxsimply.com/linux-basics/package-management/what-is-package/ What is Package in Linux? <nowiki>[Types, Features & More]</nowiki>], Afia Zahin Oishi, 2023-12-31 (Accessed: 2025-09-02)</ref> While not necessarily being the case, many package formats require their own [[package manager]]s to actually extract and [[install]] the bundled files onto a system; and most [[Linux distributions]] and other [[UNIX]]-like [[operating system]]s also come with their own package managers. Package managers, as the name suggests, allow end-users to perform package-related system maintenance tasks, including searching, installing, removing, and updating packages. While packages may be delivered individually, distributions usually gather a set of common packages into their own ''software [[repository|repositories]]'' where package managers search and download packages from. The existence of repositories enables updates to be shipped semi-automatically to a large group of users in an efficient manner, replacing the need for programs to perform their own autoupdate checks. == List of Package Formats == {{Work In Progress}} 70d132a4d0aac54ad70c3b3cb1c9a5f4f9c75ec3 4046 4045 2025-09-02T08:20:13Z Madonuko 140 fix ref wikitext text/x-wiki {{stub}} [[Category:Terminology]] The term '''package''' refers to designated file [[archive]]s, containing metadata, and files for a piece of [[software]], a desktop theme, configurations for a program, a font, etc., and bundling these files could benefit a significant group of users.<ref>[https://www.geeksforgeeks.org/linux-unix/understanding-package-managers-and-systemctl/ Understanding Package Managers and systemctl], GeeksforGeeks, 2025-07-23 (Accessed: 2025-09-02)</ref><ref>[https://www.howtouselinux.com/post/understanding-package-management-a-guide-to-package-managers-in-linux Understanding Package Management: A Guide to Package Managers in Linux], David Cao, 2023-10-09 (Accessed: 2025-09-02)</ref><ref>[https://linuxsimply.com/linux-basics/package-management/what-is-package/ What is Package in Linux? <nowiki>[Types, Features & More]</nowiki>], Afia Zahin Oishi, 2023-12-31 (Accessed: 2025-09-02)</ref> While not necessarily being the case, many package formats require their own [[package manager]]s to actually extract and [[install]] the bundled files onto a system; and most [[Linux distributions]] and other [[UNIX]]-like [[operating system]]s also come with their own package managers. Package managers, as the name suggests, allow end-users to perform package-related system maintenance tasks, including searching, installing, removing, and updating packages. While packages may be delivered individually, distributions usually gather a set of common packages into their own ''software [[repository|repositories]]'' where package managers search and download packages from. The existence of repositories enables updates to be shipped semi-automatically to a large group of users in an efficient manner, replacing the need for programs to perform their own autoupdate checks. == List of Package Formats == {{Work In Progress}} f04af6713ec26f5bf24893ac0dc9f78aecbbff82 4047 4046 2025-09-02T09:21:19Z Madonuko 140 /* List of Package Formats */ populate wikitext text/x-wiki {{stub}} [[Category:Terminology]] The term '''package''' refers to designated file [[archive]]s, containing metadata, and files for a piece of [[software]], a desktop theme, development headers, fonts, source code, etc., and bundling these files could benefit a significant group of users.<ref>[https://www.geeksforgeeks.org/linux-unix/understanding-package-managers-and-systemctl/ Understanding Package Managers and systemctl], GeeksforGeeks, 2025-07-23 (Accessed: 2025-09-02)</ref><ref>[https://www.howtouselinux.com/post/understanding-package-management-a-guide-to-package-managers-in-linux Understanding Package Management: A Guide to Package Managers in Linux], David Cao, 2023-10-09 (Accessed: 2025-09-02)</ref><ref>[https://linuxsimply.com/linux-basics/package-management/what-is-package/ What is Package in Linux? <nowiki>[Types, Features & More]</nowiki>], Afia Zahin Oishi, 2023-12-31 (Accessed: 2025-09-02)</ref> While not necessarily being the case, many package formats require their own [[package manager]]s to actually extract and [[install]] the bundled files onto a system; and most [[Linux distributions]], other [[UNIX]]-like [[operating system]]s and some [[programming languages]] also come with their own package managers. Package managers, as the name suggests, allow end-users to perform package-related system maintenance tasks, including searching, installing, removing, and updating packages. While packages may be delivered individually, distributions usually gather a set of common packages into their own ''software [[repository|repositories]]'' where package managers search and download packages from. The existence of repositories enables updates to be shipped semi-automatically to a large group of users in an efficient manner, replacing the need for programs to perform their own autoupdate checks. == List of Package Formats == Archive format is represented without the first dot, and distributions are listed with their shorter common names if any. Programming languages are in parentheses. Package managers that do not come with their own file formats are not listed here. See [[package manager]] instead. Immutable variants (esp. [[OSTree]]) that are only wrappers are not listed. {| class="sortable" ! Format !! Package Manager !! Distributions |- |[[AppImage]] || - ||* |- |[[crate]]||[[cargo]]||([[Rust]]) |- |[[deb]]||[[dpkg]]||[[Debian]] |- |[[deb]]||[[apt]]||[[Ubuntu]] |- |[[ebuild]]||[[portage]]||[[Gentoo]] |- |[[flatpak]]||[[flatpak]]||* |- |[[jar]]|| -||([[Java]]) |- |[[nimble]]||[[nimble]]||([[Nim]]) |- |[[nix]]||[[nix]]||* |- |[[npm]]||[[npm]]||([[JavaScript]]) |- |[[rpm]]||[[dnf]] / [[rpm]]||[[CentOS Stream]] / [[Fedora]] / [[RHEL]] |- |[[rpm]]||[[yum]] / [[rpm]]||[[CentOS]] |- |[[rpm]]||[[zypper]] / [[rpm]]||[[openSUSE]] |- |[[snap]]||[[snap]]||[[Ubuntu]] / * |- |[[Tarball|tar.gz]]||[[pip]]||([[Python]]) |- |[[Tarball|tar.zst]]||[[pacman]]||[[Arch]] |- |[[xbps]]||[[xbps]]||[[Void]] |- |[[whl]]||[[pip]]||([[Python]]) |} == References == 4f04edc5392fb2e86aa2e04e6445ecf4daeff269 4048 4047 2025-09-02T09:24:28Z Madonuko 140 /* List of Package Formats */ wikitable wikitext text/x-wiki {{stub}} [[Category:Terminology]] The term '''package''' refers to designated file [[archive]]s, containing metadata, and files for a piece of [[software]], a desktop theme, development headers, fonts, source code, etc., and bundling these files could benefit a significant group of users.<ref>[https://www.geeksforgeeks.org/linux-unix/understanding-package-managers-and-systemctl/ Understanding Package Managers and systemctl], GeeksforGeeks, 2025-07-23 (Accessed: 2025-09-02)</ref><ref>[https://www.howtouselinux.com/post/understanding-package-management-a-guide-to-package-managers-in-linux Understanding Package Management: A Guide to Package Managers in Linux], David Cao, 2023-10-09 (Accessed: 2025-09-02)</ref><ref>[https://linuxsimply.com/linux-basics/package-management/what-is-package/ What is Package in Linux? <nowiki>[Types, Features & More]</nowiki>], Afia Zahin Oishi, 2023-12-31 (Accessed: 2025-09-02)</ref> While not necessarily being the case, many package formats require their own [[package manager]]s to actually extract and [[install]] the bundled files onto a system; and most [[Linux distributions]], other [[UNIX]]-like [[operating system]]s and some [[programming languages]] also come with their own package managers. Package managers, as the name suggests, allow end-users to perform package-related system maintenance tasks, including searching, installing, removing, and updating packages. While packages may be delivered individually, distributions usually gather a set of common packages into their own ''software [[repository|repositories]]'' where package managers search and download packages from. The existence of repositories enables updates to be shipped semi-automatically to a large group of users in an efficient manner, replacing the need for programs to perform their own autoupdate checks. == List of Package Formats == Archive format is represented without the first dot, and distributions are listed with their shorter common names if any. Programming languages are in parentheses. Package managers that do not come with their own file formats are not listed here. See [[package manager]] instead. Immutable variants (esp. [[OSTree]]) that are only wrappers are not listed. {| class="sortable wikitable" ! Format !! Package Manager !! Distributions |- |[[AppImage]] || - ||* |- |[[crate]]||[[cargo]]||([[Rust]]) |- |[[deb]]||[[dpkg]]||[[Debian]] |- |[[deb]]||[[apt]]||[[Ubuntu]] |- |[[ebuild]]||[[portage]]||[[Gentoo]] |- |[[flatpak]]||[[flatpak]]||* |- |[[jar]]|| -||([[Java]]) |- |[[nimble]]||[[nimble]]||([[Nim]]) |- |[[nix]]||[[nix]]||* |- |[[npm]]||[[npm]]||([[JavaScript]]) |- |[[rpm]]||[[dnf]] / [[rpm]]||[[CentOS Stream]] / [[Fedora]] / [[RHEL]] |- |[[rpm]]||[[yum]] / [[rpm]]||[[CentOS]] |- |[[rpm]]||[[zypper]] / [[rpm]]||[[openSUSE]] |- |[[snap]]||[[snap]]||[[Ubuntu]] / * |- |[[Tarball|tar.gz]]||[[pip]]||([[Python]]) |- |[[Tarball|tar.zst]]||[[pacman]]||[[Arch]] |- |[[whl]]||[[pip]]||([[Python]]) |- |[[xbps]]||[[xbps]]||[[Void]] |} == References == fd7f5e91afd16678070b29eee7f6b6907066528f 0 428 4049 3396 2025-09-02T09:46:18Z Devz 274 Fixed formatting for manual sections table wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} '''Man''' (short for ''manual'') is a [[TUI|command-line]] utility available on [[UNIX]] and UNIX-like [[Operating System|operating systems]] that provides documentation for [[Software|programs]], [[System call|system calls]], [[Library|libraries]], Special files, [[file format|file formats]] and [[games]]. '''Man pages''' are a form of software documentation that is downloaded locally on the users machines to be used when no internet connection is available. == Command Usage == To read a man page the user can enter the following into their terminal:<ref>[https://en.wikipedia.org/w/index.php?title=Man_page#Command_usage man page], Wikipedia contributors, 2025-07-14 (Accessed: 2025-08-09)</ref> man ''<command_name>'' For example, to read the manual for <code>man</code> command itself: man man == Manual Sections == The manual normally consists of eight numbered sections. Most Unix-like systems use the numbering scheme used by Research Unix.<ref>[https://en.wikipedia.org/wiki/Man_page#Manual_sections man page], Wikipedia contributors, 2025-07-14 (Accessed: 2025-08-09)</ref> {| class="wikitable" !Common !System V !Description |- |1 |1 |General commands |- |2 |2 |System calls |- |3 |3 |Library functions, covering in particular the C standard library |- |4 |7 |Special files (usually devices, those found in /dev) and drivers |- |5 |4 |File formats and conventions |- |6 |6 |Games and screensavers |- |7 |5 |Miscellaneous |- |8 |1M |System administration commands and daemons<ref>[https://en.wikipedia.org/wiki/Man_page#Manual_sections man page], Wikipedia contributors, 2025-07-14 (Accessed: 2025-08-09)</ref> |} == Layout == All Man pages follow a standardise layout designed for displaying on a simple ASCII text display. ; NAME : The name of the command or function, followed by a one-line description of what it does. ; SYNOPSIS : In the case of a command, a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its declaration. ; DESCRIPTION : A textual description of the functioning of the command or function. For programs, this section often includes explanations of available command line options. ; EXAMPLES : Some examples of common usage. ; SEE ALSO : A list of related commands or functions.<ref>[https://en.wikipedia.org/wiki/Man_page#Layout man page], Wikipedia contributors, 2025-07-14 (Accessed: 2025-08-09)</ref> == Changing the Pager == The program that displays the manpage is stored in the <code>MANPAGER</code> or <code>PAGER</code> environment variable. By default, it uses <code>less</code>. Alternatively, the <code>-P</code> or <code>--pager</code> option can be used.<ref>[https://www.mankier.com/1/man.mandoc#Environment man.mandoc: display manual pages | mandoc Commands | Man Pages], ManKier, 2020-07-20 (Accessed: 2025-08-09)</ref><ref>[https://www.man7.org/linux/man-pages/man1/man.1.html man(1) - Linux manual page], Michael Kerrisk, 2025-02-02 (Accessed: 2025-08-09)</ref> This environment variable can be set using <code>export PAGER="program-to-use"</code> or added to the <code>.bashrc</code> or <code>.zshrc</code> file for persistence. For example, using Neovim as the pager would be <code>export PAGER="nvim +Man!"</code>, <code>export PAGER="nano -"</code> to use Nano, and <code>export PAGER="less"</code> to revert it to less. For Fish shell, use <code>set -x PAGER program-to-use</code> to set it for the current session, and <code>set -Ux PAGER program-to-use</code> to set it globally.<ref>[https://fishshell.com/docs/current/faq.html Frequently asked questions — fish-shell 4.0.2 documentation], fish-shell developers, 2024-08-09 (Accessed: 2025-08-09)</ref> == References == <references /> 01e839fd311e67baec47b9c9f6ecf27c22cfb231 0 574 4050 3031 2025-09-02T12:16:27Z Zeron.rendezvous 270 added dnf wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes great inspiration from i3 in its design and configuration, and, consequently, it is very compatible with i3. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[Swayfx]] is a fork of Sway that adds cool effects, animations, and visuals to it, something you may want to look into. === Notable Features: === According to Sway's official website: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. == Pre-Installation: == * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] == Installation: == ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For Arch: ==== Using pacman: pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For Debian: ==== Using apt package manager: apt install sway ==== For Fedora: ==== Using dnf package manager dnf install sway 76042e42636a06049b9c49b8faef7d302876dd66 4052 4050 2025-09-02T12:24:27Z Zeron.rendezvous 270 Added SoftwareInfoBox wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} {{SoftwareInfobox |image=[[File:Sway-logo|thumb]] |caption=Sway Logo |title=Sway |releasestatus=Maintained |lastrelease=1.11, 2025-06-09 |firstrelease=0.1, 2016-05-24 |languages=[[C]] |developers=Sway Developers |website=[https://swaywm.org/ swaywm.org] }} Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes great inspiration from i3 in its design and configuration, and, consequently, it is very compatible with i3. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[Swayfx]] is a fork of Sway that adds cool effects, animations, and visuals to it, something you may want to look into. === Notable Features: === According to Sway's official website: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. == Pre-Installation: == * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] == Installation: == ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For Arch: ==== Using pacman: pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For Debian: ==== Using apt package manager: apt install sway ==== For Fedora: ==== Using dnf package manager dnf install sway 448b98f2febdd556966f79ae62c8f3acc2300ba7 4053 4052 2025-09-02T12:28:43Z Zeron.rendezvous 270 fixed thumbnail wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} {{SoftwareInfobox |image=[[File:SwayLogo.png|thumb]] |caption=Sway Logo |title=Sway |releasestatus=Maintained |lastrelease=1.11, 2025-06-09 |firstrelease=0.1, 2016-05-24 |languages=[[C]] |developers=Sway Developers |website=[https://swaywm.org/ swaywm.org] }} Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes great inspiration from i3 in its design and configuration, and, consequently, it is very compatible with i3. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[Swayfx]] is a fork of Sway that adds cool effects, animations, and visuals to it, something you may want to look into. === Notable Features: === According to Sway's official website: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. == Pre-Installation: == * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] == Installation: == ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For Arch: ==== Using pacman: pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For Debian: ==== Using apt package manager: apt install sway ==== For Fedora: ==== Using dnf package manager dnf install sway f6904431e0a367be6006d597bada0a194e8972bb 4054 4053 2025-09-02T12:36:17Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} {{SoftwareInfobox |image=[[File:SwayLogo.png|thumb]] |caption=Sway Logo |title=Sway |releasestatus=Maintained |lastrelease=1.11, 2025-06-09 |firstrelease=0.1, 2016-05-24 |languages=[[C]] |developers=Sway Developers |website=[https://swaywm.org/ swaywm.org] }} Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes great inspiration from i3 in its design and configuration, and, consequently, it is very compatible with i3. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[Swayfx]] is a fork of Sway that adds cool effects, animations, and visuals to it, something you may want to look into. === Notable Features: === According to Sway's official website: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. == Pre-Installation: == * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] == Installation: == ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For Arch: ==== Using pacman: pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For Debian: ==== Using apt package manager: apt install sway ==== For Fedora: ==== Using dnf package manager dnf install sway 2b71f65a699911b54fb2faeed62097a77fb956ca 6 1008 4051 2025-09-02T12:20:09Z Zeron.rendezvous 270 wikitext text/x-wiki swaylogo cf3b8d3e33dea2ab6734a9ddcf40cc1ddf030a1e 0 918 4056 3884 2025-09-02T12:37:53Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki Easy Effects, available on Flathub [https://flathub.org/apps/com.github.wwmm.easyeffects here], is a tool for adding effects to audio input and output under PipeWire. It is a GTK application that bundles many effects and tools, making it easier to use out of the box. Easy Effects does not support external plugins. If you would like to use external plugins, see (list advanced tools here). For the PulseAudio counterpart, see [[PulseEffects]]. = Application layout = [[File:EasyEffects-Input-Effects-empty.png|thumb|Easy Effects as it opens by default|1084x1084px]] == The effects list == == Input and Output == == Recorders and Players == == Presets == == Settings == = Effects = == Simple and useful == === Equalizer === === Noise Reduction === === Compressor === === Delay === === Level Meter === == Advanced and Niche == = Quirks = == Interaction with OBS == To capture unmodified sound from the desktop, you will want to configure OBS to connect to "Easy Effects Sink" for its "Desktop Audio" "Properties". This can often result in a garbled audio stream. To fix this, add "Stereo Tools" to the top of the output effects list. Easy Effects will not modify the "Mic/Aux" audio input in OBS by default. To get this effect, you may either enable "Process All Input Streams" in the hamburger menu top-right -> "Preferences" -> "General" -> "Audio" -> "Process All Input Streams". Or you may select "Easy Effects Source" as the source for "Mic/Aux" in its "Properties". It is recommended to have "Stereo Tools" at the top of the input effects list as well. 030b20a5287b608e25b6000a0f3244efcfa59fb3 0 907 4057 3867 2025-09-02T12:38:03Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Usage == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. 102cffddda65f43de5fabab19ab567acccf8610a 0 884 4058 3849 2025-09-02T12:38:13Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>https://lubuntu.me/ Lubuntu, Accessed: 2025-08-22</ref> * [[Fedora]] LXQt spin<ref>https://fedoraproject.org/spins/lxqt Fedora, Accessed 2025-08-22</ref> * [[CachyOS]]: available in installer<ref>https://wiki.cachyos.org/installation/desktop_environments/ CachyOS, Accessed:2025-08-22</ref> * [[SparkyLinux]]<ref>https://wiki.sparkylinux.org/doku.php/about Sparky Linux, Accessed:2025-08-22</ref> * [[Debian]]: available in installer<ref>https://wiki.debian.org/LXQt Debian Wiki, Accessed:2025-08-22</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>https://packages.debian.org/stable/lxqt-core Debian, Accessed 2025-08-23</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>https://packages.debian.org/trixie/lxqt Debian, Accessed:2025-08-23</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>https://packages.debian.org/stable/task-lxqt-desktop Debian, Accessed:2025-08-23</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>https://archlinux.org/groups/x86_64/lxqt/ Arch Linux, Accessed:2025-08-23</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template Github, Accessed:2025-08-23</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers LXQt wiki, Accessed:2025-08-23</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions LXQt wiki, Accessed:2025-08-23</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight lang="text">exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == 7d65c4b23ddd8eb1433e922db8c1597776392e06 0 219 4059 3815 2025-09-02T13:56:04Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox | title = Konqi | image = [[File:KDE Mascot Konqi by Tyson Tan.png|KDE_Mascot_Konqi_by_Tyson_Tan|222px]] | caption = Konqi the KDE mascot }} '''Konqi''' is the official mascot of [https://kde.org/ KDE] and [[KDE Plasma]], designed by Tyson Tan.<ref>https://community.kde.org/Promo/Material/Mascots Official KDE Wiki, 2025 (Imported 6th June 2024)</ref> Konqi's full name is "Konqi the Konqueror", being named after [https://konqueror.org/ Konqueror], KDE's default web browser.<ref>https://community.kde.org/Konqi Official KDE Wiki, 2025 (Imported 6th June 2024)</ref> == References == <references /> 41b0466486f44a0b7bedc88466372cef3e3486b7 0 297 4060 3817 2025-09-02T13:56:55Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Terminology]] '''Multi-booting''' is the process of installing and using multiple [[Operating System|operating systems (OS)]] on one machine that can be chosen at startup.<ref>"OS/2 commands by name", OS/2 command reference (First ed.), IBM, 1999, "Switches between the DOS and OS/2 operating systems that are on the same hard disk (drive C)."</ref> The core concept of multi-booting revolves around partitioning a computer's [[storage]] device, whether it be a HDD, SSD (sda/nvme), or eMMC. Each operating system requires its own [[partition]], effectively creating independent spaces within the same physical drive. This separation allows users to keep multiple systems isolated from one another, ensuring that one operating system's configuration or files do not interfere with another. For systems with [[UEFI]] (Unified Extensible Firmware Interface), an additional [[EFI]] System Partition (ESP) is required to store [[Bootloader|bootloaders]] and related files. Multi-booting has many uses,<ref>[https://www.linux.org/threads/dual-and-multi-boot-systems.47320/#google_vignette Dual and Multi boot systems], Linux.org, ''Linux For All''</ref> including: * Testing different operating systems<ref>[https://forums.tomshardware.com/threads/booting-problem-of-linux-in-windows-boot-loader.1780023/ Booting Problem Of Linux in Windows Boot Loader], Tom's Hardware Forum, ''tom's HARDWARE.''</ref> * Utilizing [[:Category:Software|software]] that may not work as expected on another OS<ref name=":0">[https://www.lenovo.com/us/en/glossary/what-is-dual-boot/?srsltid=AfmBOorYy-7hHWgEXjI7Y6OpBFPvBpBgoIpInUXPVHuWngn_eQCUh4y0 What is Dual Boot & How to Dual Boot Windows and Linux?], Lenovo US, ''Smarter Technology For All.''</ref> * Deploying and testing software on different operating systems '''Dual-booting''' is a popular multi-boot configuration that includes two operating systems, most commonly a [[Linux Distributions|Linux distribution]] and [[Microsoft Windows]]. === Multi-booting vs. Virtual Machines (VMs) === While [[Virtual Machine|virtual machines]] and multi-booting can be used for the same purposes, each has their own distinctions. Virtual machines are installed inside a host operating system and can be run side-by-side as long as the host machine's resources are sufficient. Multi-booting does not allow running each operating system simultaneously. it provides however the booted OS with full access to the machine's components, rather than needing to go through translation and compatibility layers as a virtual machine, which often increases performance significantly. === Common Uses for Multi-booting === ==== Gaming ==== While gaming is relatively straightforward and accessible on [[Linux]], some games are still incompatible. One notorious cause of this, especially in online competitive multiplayer games, is [[kernel]]-level anti-cheat (such as Riot's Vanguard anti-cheat). Many of the popular kernel-level anti-cheats do not work on Linux. Because of this, dual-booting Linux and Windows is a popular choice for those that play games with such kernel-level anti-cheats. == References == <references /> 67bc9488b992da7114dbd0debdc76ef39fa7e6aa 0 575 4061 4040 2025-09-02T13:57:47Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.1, Feb 23, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.1 released on the 23rd of February 2025.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n46 <sup>🍣DEAD?]</ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == 14636fd9039e25adb906bdcc1d77a3ac36bf3e6e 4065 4061 2025-09-03T01:55:22Z Amadaluzia 52 Update Emacs Latest Version: https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html#Releases wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.2, Aug 14, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] [[File:GNU Emacs 30 1 Screenshot.png|alt=Emacs 30.1|thumb|A screenshot from a fresh install of Emacs 30.1]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == 74c40ca0a1d5e39b4a1871f9b940e84843ff7492 3000 577 4062 3823 2025-09-02T13:58:06Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight> # Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland </syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then run <code>$ sudo emerge --ask app-editors/emacs</code>. === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. == References == 7c98961798fb4a69d25e5de35e890f49452e2269 4067 4062 2025-09-03T03:58:31Z Amadaluzia 52 Add steps for NixOS and FreeBSD wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is reccomended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight lang="text"># Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland</syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight lang="text"># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then install Emacs with the following command:<syntaxhighlight lang="text"> # emerge app-editors/emacs </syntaxhighlight> === NixOS === You can install Emacs in a variety of ways in NixOS. A common way to install Emacs is to append the following code to your NixOS configuration:<syntaxhighlight lang="nix" line="1">{ services.emacs = { enable = true; /* There are more options you can set, please read https://search.nixos.org/options?channel=unstable&query=services.emacs for more information. */ }; }</syntaxhighlight>You can then rebuild the system using your desired method—most commonly with <code>nixos-rebuild switch</code>—to use a system configuration which has Emacs installed. === FreeBSD === Emacs be installed on FreeBSD by using either pkg or ports. If you want a binary package at the absence of deeper customization, then you can use either of the following commands:<syntaxhighlight lang="text"> ## Installing Emacs (X11) # pkg install emacs ## Installing Emacs (Wayland) # pkg install emacs-wayland ## More flavours can be found here: https://www.freshports.org/editors/emacs/ </syntaxhighlight>If you are willing to compile Emacs for deeper customization, then you can use the editors/emacs port. This part is expected for people to have used ports in the past; read [https://docs.freebsd.org/en/books/handbook/ports/#ports-using Chapter 4 of the FreeBSD Handbook] for information on how to use ports if desired. And with that, you can use the following commands to build the Emacs port:<syntaxhighlight lang="text"> $ cd /usr/ports/editors/emacs # make config # make install clean </syntaxhighlight> === Installing from Source === Emacs provides information on how to install itself from source in [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] its Savannah repository. == References == bf27a6ac0ebbaa8b57bce5c47b620fdaa62731cc 0 767 4063 3741 2025-09-02T13:58:45Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki RTFM is an acronym of "Read The Fucking Manual"<ref>{{Cite|url=http://www.catb.org/~esr/faqs/smart-questions.html#rtfm|title=How To Ask Questions The Smart Way|author=Eric Steven Raymond|year=21 May 2014|accessdate=2 August 2025}}</ref> or "Read The Friendly Manual". It's usually used when a user asks a question that could be easily answered by reading the manual ab2a348a5d885c867da93e7b588852d9fd553125 2 3 4064 4039 2025-09-03T01:49:04Z Amadaluzia 52 wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <functional> #include <print> using String = std::string; class Person { virtual String description() = 0; }; using SocialPair = struct { String service; String username; }; class Amadaluzia : Person { public: String name = "Artur Manuel"; int age = 17; std::vector<String> interests{ "Programming", "CLI development", "GUI development", "Web development", "Library development", "System administration", "Walking", "Climbing", "Math", "Learning", "Exercise", "Sports", "Socialising", "Writing", "Photography", "Video editing", "Movie production", "Techno music", "Shoegaze", "Alternative Rock", }; std::vector<SocialPair> socials = { {"Email", "amad@atl.tools"}, {"Email (tutanota.com alt)", "amadaluzia@tutanota.com"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Matrix (pub.solar alt)", "@amadaluzia:pub.solar"}, {"Matrix (envs.net alt)", "@amadaluzia:envs.net"}, {"libera.chat", "amadaluzia"}, {"oftc.net", "amadaluzia"}, {"Revolt", "amadaluzia#3242"}, {"Mastodon", "@amadaluzia@bsd.cafe"}, {"Discord", "amadaluzia"}, {"Discord (alt)", "balke.nix"}, {"Keyoxide", "aspe:keyoxide.org:ZV3A66CSCNOS7V4N5A4DOD57I4"}, {"GitHub", "amadaluzia"}, {"SourceHut", "amadaluzia"}, {"Codeberg", "amadaluzia"}, {"GitLab", "amadaluzia"}, }; String description() override; }; String Amadaluzia::description() { String result{}; result += std::format("Good day, my name is {}, commonly known online as \"amadaluzia\". I am a {}\n", name, age); result += "year old Portuguese-Italian resident of the UK. You may have seen me in many\n"; result += "programming spaces, however, I am keenly interested in many other topics. More\n"; result += "specifically, I am interested in:\n"; for (auto interest : interests) result += std::format("- {}\n", interest); result += "I am also present on many social media platforms, even multiple times! Moreover, I\n"; result += "have pretty much the same name everywhere, so you can reliably find me. But I will\n"; result += "share my social platforms here as I use many decentralised services. Here I am:\n"; for (auto const &[service, username] : socials) result += std::format("- {} on {}\n", username, service); result += "\nIf you can find any ways of optimising this program, let me know, as long as the\n"; result += "it's kept to Amadaluzia::description(). Thank you for reading!\n"; return result; } int main(void) { Amadaluzia amadaluzia; std::println("{}", amadaluzia.description()); }</syntaxhighlight> 9abbc59c8d34226111e3c4e0f31c47d324629060 0 244 4066 3734 2025-09-03T03:46:49Z Polymo1 275 If there isn't a source classifying IME as a threat, its probably better to not call it explicitly a threat wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]. Installation instructions should be on its own Guides page.}} [[Category:Guides]] [[File:Libreboot Example.png|thumb|Librebooted HP Desktop from the official website.]] As per convention for most [[Linux]] beginners and intermediates alike, the action of "Librebooting" a personal machine is nothing short of a commonality. Founded by Leah Rowe, the Libreboot project aims to create ''libre'' "boot firmware based on coreboot, replacing proprietary BIOS/UEFI firmware" and, through this simple yet imperative step to true [[privacy]], one can achieve true digital freedom.<ref>Libreboot - Main Page[https://libreboot.org/]</ref> It is centered around the elimination of the possible threat of the Intel Management Engine (IME/Intel ME), which has been infamously speculated to be a potent spying device. Libreboot is based on the [https://www.coreboot.org/ coreboot] project, and aims to simplify the process of installing it on one's system. [https://docs.google.com/document/d/1wvGI6X1jTRo7rDZ7hrouDKMJKSRALFuahu3HDDzb3Xg/edit This article] has been peer-reviewed for validity, written based on the dangers of hardware-level spying in using Libreboot as an example. == Libreboot experience == Upon finally installing Libreboot ('''if you haven't already, see the guides below!'''), you will likely be met with multiple ROM types to choose from: * '''textmode -''' Solely renders your BIOS and other bootloaders in text mode. If you want to install FreeBSD, this is a requirement as FreeBSD will not install on a framebuffer and face bugs.<ref>Libreboot - Documentation, BSD[https://libreboot.org/docs/bsd/#freebsd-and-corebootfb]</ref> [[File:Libreboot - SeaBIOS.png|left|thumb|Asiliria's Librebooted machine prompted to select a device to boot from using SeaBIOS]] * '''corebootfb -''' Provides a graphical framebuffer, which is suitable for using tools like [[Ventoy]] for managing your ISO files. However, most tools, including Ventoy, also support text mode either way. You will likely see '''SeaBIOS''' included with these ROMs, which is heavily comparable to your BIOS/UEFI screen - it selects which device to boot from, simply. Pictured is the menu of which you will be prompted. '''NOTE:''' After your first Libreboot, you are more than likely able to flash repeatedly afterwards without having to use a Pomona Flash Clip (below). Depending on your device, the flashing experience may and inevitably, at times, '''will''' vary. '''<u>Please check for your BIOS chip device on the Libreboot website.</u>''' === Steps to Install === As it is the easiest distribution to use, this guide assumes you are using [[Debian]] to Libreboot your machine using the Dell OptiPlex as an example. See below for an easier method for that specific device. * '''Install flashprog and the lbmk repository -''' Follow the instructions on the [https://libreboot.org/docs/build/#sources Libreboot wiki] to use '''lbmk''' and build the image from source. For a Dell OptiPlex 9020, your image '''should be named''' "'''dell9020mt_12mb'''." after compilation. ** '''Flashprog''', too, must be made from source - clone [https://review.sourcearcade.org/flashprog.git this repository]{{Dead Link|2025-08-14|404}} and follow [https://flashprog.org/wiki/Downloads these directions]. ** Libreboot '''warns against the usage of flashrom.''' You may use it, and according to '''Leah Rowe, it is almost exactly the same -''' however, flashprog is actively maintained. == Specific Device Tips == ==== Dell OptiPlex 9020 SFF - Easier Method ==== [[File:Pomona Flash Clip (IRL).png|left|frameless|195x195px|A real-world picture of Asiliria's Pomona Flash Clip.]] In a talk with Leah Rowe herself, there is little to no need for the popular, yet expensive, Pomona Flash Clip. According to Dell's own user manual for maintenance of the device, there are four pins near the RAM slots that allow for the read-only flag of the BIOS to be removed with one female-to-female jumper wire. Thus, this allows the override of the boot image. * This may sound simple, but please be careful - the process of doing this is slightly hazardous. In a traditional process, the firmware blob is split into two portions to be flashed onto the SOIC-8 microprocessors. While this will likely work, the very process of not only doing it ''right'' with accounting for which processor is which but also the safety of connecting the flash clip may not be worth the extra hassle. It is especially risky on a device like this to make a mistake. (I will soon fill this out properly, as the process is very easy the first go-around but I will need to repeat it for authenticity's sake.) == References == d00f2ae533a00f53db5ba7b669b84b63fefe4f48 0 281 4068 3688 2025-09-03T11:31:34Z Hog 161 added link to GitHub repository wikitext text/x-wiki [[Category:X_Window_Managers]] {{SoftwareInfobox | caption = Window Maker and GNUstep logo | developers = Window Maker developers | image = [[File:GNUstep logo.png|200px|GNUstep_logo]] | languages = [[C]] | lastrelease = 0.96.0, 2023-08-05 [https://github.com/window-maker/wmaker] | releasestatus = Maintained | title = Window Maker | website = [https://windowmaker.org/ windowmaker.org] }} Window Maker is a [[Window Manager|window manager]] for [[X11]] designed to emulate the look and feel of NeXTSTEP as an environment compatible with GNUstep libraries.<ref name=":0">[https://www.windowmaker.org Window Maker: Home] official Window Maker Website, 2025 (Imported 16th June 2024)</ref> It has been developed from scratch since 1997 by Alfredo Kojima in C. === Design === [[File:Window Maker Screenshot - Debian Sarge 3.1 01.png|alt=Screenshot of Window Maker on Debian 3 (Sarge).|thumb|Screenshot of Window Maker on [[Debian]] 3 (Sarge).]] According to the official website:<blockquote>'''"Window Maker''' is an X11 window manager originally designed to provide integration support for the GNUstep Desktop Environment, although it can run stand alone. In every way possible, it reproduces the elegant look and feel of the NeXTSTEP user interface."<ref name=":0" /></blockquote>Window Maker is a floating window manager that aims to replicate the look and feel of the user interface of the NeXTSTEP operating system thanks to its implementation of GNUstep. Another key feature of Window Maker is its ability to use applications known as [https://www.dockapps.net/ dockapps], which are specialized applications that run on the docks found on the sides of the screen that can provide different features, for example monitoring system activity, the weather, unread emails and more.<ref name=":0" /><ref>[https://www.dockapps.net/ dockapps.net: Home] Dockapps Website, 2025 (Imported 16th June 2024)</ref> === Configuration === [[File:Windowmaker colour preferences.png|alt=Screenshot of WPrefs.|thumb|Screenshot of WPrefs.]] Configuration of Window Maker is done via the WPrefs application, which can control theming, window behavior, the main dropdown menu and more. == References == <references /> cd669835497c6877eacac89b1b27217f7b90719c 0 176 4069 3908 2025-09-03T11:36:02Z Hog 161 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.4.4, August 5, 2025 [https://kde.org/announcements/plasma/6/6.4.4/] |firstrelease=1.0, July 12, 1998 [https://kde.org/announcements/1-2-3/1.0-beta1/] | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2025-08-14|503}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2025-08-14|503}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> e4f04cb341f092a337e534a7446ffe86f496a615 0 261 4070 3647 2025-09-03T11:36:55Z Hog 161 wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] }} Neofetch was a command-line system information tool written in [[bash]] which displays information about your [[Operating System|operating system]], software and hardware. It was created by Dylan Araps in 2017 and was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]], a neofetch-like utility written in [[C]], and [[hyfetch]], a fork of neofetch with pride flags. == References == <references /> 01b4c4fadf553941d6b5e54f78891a79528fea5b 0 447 4071 3674 2025-09-03T11:51:03Z Hog 161 wikitext text/x-wiki {{Needs Citations}} Self-hosting is a rewarding practice that allows you to reduce reliance on cloud services, giving you much greater control and privacy over the data you own. By self-hosting, the services you use, and by extension anything you store with those services, reside on your own hardware rather than third-party servers. Essentially, the “cloud” is just someone else's computer, often a large, multi-billion-dollar infrastructure. However, with self-hosting, you own the data on the devices you manage. == What is Self-Hosting? == Self-hosting often refers to the process of running and managing your own services on personal hardware such as a laptop, desktop, single-board computer, or even an enterprise-grade server. This means you can set up and operate services for yourself, your family, or others without depending on external cloud platforms. == What Can I Host? == There are numerous possibilities for self-hosting, depending on your needs. Some popular options include: * Email server * Password manager * Personal website * File hosting service * Media server * VPN (Virtual Private Network) * [[Pi-hole]] == Do I Need Anything Special to Self-Host? == [[File:Homelab.jpg|thumb|Example of an enterprise grade homelab]] The requirements are minimal. You can self-host using almost any device, from an old, cheap laptop to a single-board computer like a [[Raspberry Pi]]. Some enthusiasts take this a step further and use second-hand enterprise equipment from real data center infrastructure to host their services. These setups are often referred to as “HomeLabs.” However, anything that can connect to the internet or your local area network can be sufficient. == The Challenges of Self-Hosting == Like everything in life, self-hosting has its challenges. When hosting services at home, you are responsible for maintaining and fixing any problems that arise. Unlike cloud services, which are typically plug-and-play, homelabs require regular maintenance to ensure stable operation. Below are some challenges many homelab users encounter. === Common Problems === * '''Electricity Usage''' - One of the main concerns with starting a homelab is power consumption. As your homelab grows, so will its electricity usage. Additionally, the services you run rely on your home's power grid, meaning power outages can affect your services. [[File:Speedtest.png|thumb|Example of a users internet speed.]] * '''Internet Speed''' - Not all internet connections are equal. When exposing services to the outside world, consider how much bandwidth they will consume. A slow connection or data caps can limit what you can host effectively. Residential internet plans might not support the load or violate fair use policies. Like the electricity usage, you are relying on the reliance your ISP provides. * '''Natural Disasters''' - Hosting services in areas prone to natural disasters poses risks. If a disaster damages your homelab, your data may be lost along with the equipment. * '''Vulnerabilities''' - Even with the latest software and hardware, vulnerabilities persist. Tools like Shodan.io scan for exposed services, potentially attracting malicious actors. Without sufficient protection, your services may be at risk. * '''Hardware Failures''' - Nothing lasts forever. Self-hosted services depend on your hardware, which will need maintenance and occasional replacement. Hard drives, in particular, are susceptible to failure over time. * '''Sound''' - Unlike a laptop or a single-board computer, enterprise equipment is not built to be quiet. It is designed to run cool and avoid failure, which often results in high-pitched fan noise due to large amounts of airflow. * '''Dust''' - Most homelabs are not housed in ventilated data centers, leading to dust accumulation, which can clog and damage equipment. * '''User Error''' - Mistakes happen. Deleting the wrong files, modifying incorrect configurations, or failing to double-check changes can lead to data loss or downtime. == Solutions == [[File:Ups uninterruptible power supply.jpg|thumb|An example of an (UPS) Uninterruptible Power Supply]] * '''Electricity Usage''' - Use an Uninterruptible Power Supply (UPS). A UPS acts as a battery backup and protects against power surges. If the power goes out, the UPS switches to battery mode to keep your equipment running. UPS devices can range from small 600W models to large 10kW units that can power enterprise equipment for hours. * '''Internet Speed''' - If your internet is slow or capped, consider upgrading to a better plan if available. Some ISPs offer small business plans for residential users, providing higher speeds, service agreements, and multiple external IP addresses. * '''Natural Disasters''' - Perform regular off-site backups. Store data in locations unaffected by the same natural disasters as your homelab to ensure redundancy. * '''Vulnerabilities''' - To mitigate vulnerabilities some examples include: ** Keep all software and hardware up to date. ** Change default ports for commonly scanned services. ** Install a firewall. ** Use a VPN to access services instead of exposing them directly to the internet. ** Use encrypted protocols and storage. [[File:raid failure.png|thumb|An example of a drive failing in a raid.]] *'''Hardware Failures''' - Practice the 3-2-1 backup strategy: ** Keep at least THREE copies of your data. ** Use at least TWO types of storage. ** Keep at least ONE copy off-site. * '''Sound''' - To mitigate noise, consider buying fanless equipment, as fans are the primary source of noise. Alternatively, place the equipment in a room that is not frequently used to minimize sound. Keep in mind that fanless equipment carries a risk of overheating. * '''Dust''' - Regularly clean your equipment and store it in well-ventilated areas. Use compressed air or vacuum cleaners to remove dust. * '''User Error''' - Double-check all changes, avoid running unfamiliar commands, and thoroughly understand what you are deploying. a777b1060f97260899e9d7f5f233217ad7385a51 0 1009 4072 2025-09-03T12:07:14Z Hog 161 created stub page wikitext text/x-wiki {{stub}}{{DistributionInfobox|title=Bazzite|image=[[File:Bazzite Logo.svg|200px]]|caption=The Bazzite logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Flatpak]]|defaultdesktops=Terminal User Interface|usagetype=Gaming|architectures=x86_64|website=[https://bazzite.gg/ bazzite.gg]}} 524e52cb8a1e11fbe0b62f9f521989cac4c18582 4073 4072 2025-09-03T12:08:16Z Hog 161 wikitext text/x-wiki {{stub}}{{DistributionInfobox|title=Bazzite|image=[[File:Bazzite Logo.svg|200px]]|caption=The Bazzite logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Flatpak]]|defaultdesktops=[[Gnome]],[[KDE Plasma]]|usagetype=Gaming|architectures=x86_64|website=[https://bazzite.gg/ bazzite.gg]}} 464ea77f4f9e0f283e059d7c9be367b80b104dc4 4074 4073 2025-09-03T12:08:59Z Madonuko 140 [[Category:Linux Distributions]] wikitext text/x-wiki {{stub}}{{DistributionInfobox|title=Bazzite|image=[[File:Bazzite Logo.svg|200px]]|caption=The Bazzite logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Flatpak]]|defaultdesktops=[[Gnome]],[[KDE Plasma]]|usagetype=Gaming|architectures=x86_64|website=[https://bazzite.gg/ bazzite.gg]}} [[Category:Linux Distributions]] 1440fa610b5380b25c0968e8a4606a879ec082e3 4078 4074 2025-09-03T12:12:41Z Hog 161 wikitext text/x-wiki {{stub}}{{DistributionInfobox|title=Bazzite|image=[[File:Bazzite Logo.svg|200px]]|caption=The Bazzite logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[Flatpak]]|defaultdesktops=[[GNOME]],[[KDE Plasma]]|usagetype=Gaming|architectures=x86_64|website=[https://bazzite.gg/ bazzite.gg]}} [[Category:Linux Distributions]] e75c955c435277c38717e96589546043cabf4ccb 0 622 4075 3794 2025-09-03T12:10:34Z Hog 161 minor edits added lxde wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment File:GNOME 43.png|GNOME File:Lxqt-screenshot-about.png|link=LXQt|LXQt File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:LXDE-Qt preview.png|LXDE </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |- |LXDE |} 00f6e7c8f04fd02be22cc233258a4aca87bb3f7f 4076 4075 2025-09-03T12:11:53Z Hog 161 wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment File:GNOME 43.png|GNOME File:Lxqt-screenshot-about.png|link=LXQt|LXQt File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:LXDE-Qt preview.png|LXDE </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |- |[[LXDE]] |LXDE is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |} 3a2516e2c8bab07d28f328c46db44f29fbcefa0c 0 217 4077 3717 2025-09-03T12:12:18Z Madonuko 140 releasemodel=stable release wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{stub}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Stable Release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022-04-21 (Accessed: 2025-09-03)</ref> |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}} [[Category:Linux Distributions]] [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[ https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel<nowiki> fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</nowiki></ref> == Release system == Fedora current follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], </nowiki>'''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/<nowiki> Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</nowiki></ref> System upgrades are usually handled offline to prevent system breakage == The package management system == the Package manager [[dnf]] , is usually called with the following arguments * <code>sudo dnf up</code> --- updates system packages * <code>sudo dnf in <pkg names> <...></code> --- install new packages * <code>sudo dnf rm <pkg names> <...></code> --- remove packages * <code>sudo dnf system-upgrade --relesever=<rel></code> --- updates system version and packages<ref>[https://dnf.readthedocs.io/<nowiki> DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</nowiki></ref> == References == <references /> 790cdd50874c9d86b39a76a99fb73cbf0f494f65 0 626 4079 3816 2025-09-03T12:14:29Z Hog 161 wikitext text/x-wiki Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>[https://manjaro.org/ Manjaro – The Linux for People and Organizations], Manjaro, 2025-08-09 (Accessed: 2025-08-09)</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">[https://distrowatch.com/table.php?distribution=manjaro DistroWatch.com: Manjaro Linux], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" Rolling Release * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>[https://wiki.manjaro.org/index.php/Pamac Pamac - Manjaro], Manjaro, 2023-03-09 (Accessed: 2025-08-09)</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME|GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>[https://en.wikipedia.org/wiki/Manjaro Manjaro], Wikipedia contributors, 2025-07-01 (Accessed: 2025-08-09)</ref><ref>[https://www.ubuntumint.com/manjaro-linux-history/ The History of Manjaro Linux Distribution], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>[https://www.geeksforgeeks.org/how-to-install-manjaro-linux/ How to Install Manjaro Linux?], GeeksforGeeks, 2023-12-22 (Accessed: 2025-08-09)</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch's base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch's, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>[https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/ How to Enable Arch User Repository (AUR) in Manjaro Linux], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro's custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch's upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>[https://itsfoss.com/manjaro-vs-arch-linux/ Manjaro vs Arch: What's the Difference? Which one to Use?], Dimitrios, Abhishek Prakash, 2023-09-13 (Accessed: 2025-08-09)</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>[https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. == References == 62d0e2c6e7ddb17e159cd92214915e6069f1d66b 0 227 4080 3626 2025-09-03T19:22:30Z Polymo1 275 fix last version date wikitext text/x-wiki {{DISPLAYTITLE:i3}} {{SoftwareInfobox | image = [[File:I3 window manager logo.svg|I3_window_manager_logo]] | caption = i3 logo | title = i3 | releasestatus = Maintained | lastrelease = 4.24, Nov 06, 2024 | languages = [[C]] | developers = Michael Stapelberg | website = [https://i3wm.org/ i3wm.org] }} [[Category:X_Window_Managers]] [[File:Backup facebook to google.jpg|thumb|Screenshot of a typical i3 session.]] '''i3''' is a dynamic tiling [[Window Manager]] inspired by wmii that is primarily targeted at developers and advanced users.<ref>[https://www.youtube.com/watch?v=QnYN2CTb1hM i3 - An Improved Tiling Window Manager - YouTube], Google TechTalks, 2012-06-18 (Accessed: 2025-08-09)</ref> It is designed for [[X11]] and written in [[C]]. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is done through a plain text file, and i3 can be extended using its Unix domain socket and JSON-based IPC interface from various programming languages.<ref>Stapelberg, Michael. [https://i3wm.org/docs/ipc.html "i3: IPC interface (interprocess communication)"].</ref> i3 is not to be confused with the Intel Core i3. === Design === Similar to wmii, i3 employs a control system reminiscent of vi and Vim. By default, window focus is managed using the 'Mod1' key (either the Alt key or Windows key) in combination with the right-hand home row keys (Mod1+J, K, L, Semicolon). Window movement is controlled by adding the Shift key to this combination (Mod1+Shift+J, K, L, Semicolon).<ref name=":0">Congleton, Nick (May, 2017). [https://www.maketecheasier.com/install-use-i3-window-manager-ubuntu/ "Install and Use i3 Window Manager on Ubuntu"]. maketecheasier. Uqnic Network Pte.</ref> === Configuration === i3's configuration can usually be found in <code>~/.config/i3/config</code> where "~" refers to the user's home directory. Unlike other popular tiling window managers, such as [[AwesomeWM]] and [[dwm]], window management is left to the user in i3. Windows are contained within containers that can be divided either vertically or horizontally. You have options to resize, stack, and tab the windows. i3 employs dmenu as the default program launcher, but this can be substituted with another option.<ref name=":0" /><ref>J.A. Watson (January 7, 2016). [https://www.zdnet.com/article/how-to-customise-your-linux-desktop-i3-window-manager/ "How to customise your Linux desktop: i3 Window Manager"]. zdnet.com ZDNet.</ref> ====== See [https://i3wm.org/docs/userguide.html#configuring Configuring i3] for details. ====== == References == 2a520363d8b85e08c792385950ef36b68e257513 3000 608 4082 3824 2025-09-04T10:52:05Z Madonuko 140 /* Fcitx5 */ autostart entry wikitext text/x-wiki {{GuideWarning}} Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">[https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims Localization, Internationalization and Multilingualization], Ultramarine Linux, 2024 (Accessed: 2025-05-03)</ref> Users can use the IMF to switch between different IMEs.<ref>[https://wiki.archlinux.org/title/Input_method Input method], ArchWiki, 2020 (Accessed: 2025-05-03)</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>[[wikipedia:Intelligent_Input_Bus|Intelligent_Input_Bus]], Wikipedia, 2009 (Accessed: 2025-05-03)</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>[[wikipedia:Fcitx|Fcitx]], Wikipedia, 2010 (Accessed: 2025-05-03)</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. If this package is not available, create an autostart entry manually at <code>/etc/xdg/autostart/org.fcitx.Fcitx5.desktop</code>:<syntaxhighlight lang="ini"> [Desktop Entry] Name=Fcitx 5 GenericName=Input Method Comment=Start Input Method Exec=/usr/bin/fcitx5 Icon=fcitx Terminal=false Type=Application Categories=System;Utility; StartupNotify=false X-GNOME-AutoRestart=false X-GNOME-Autostart-Notify=false X-KDE-autostart-after=panel X-KDE-StartupNotify=false X-KDE-Wayland-VirtualKeyboard=true X-KDE-Wayland-Interfaces=org_kde_plasma_window_management</syntaxhighlight> * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code><ref name=":0" group="Note">Additionally requires <code>fcitx5-chinese-addon</code> on Fedora due to packaging issues.</ref> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code><ref name=":0" group="Note" />? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code><ref group="Note"><code>fcitx5-mozc-ut</code>^AUR is instead recommended on Arch Linux.</ref> |<code>fcitx-mozc</code><ref group="Note"><code>fcitx-mozc-ut</code>^AUR is instead recommended on Arch.</ref> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |ViQR |<code>fcitx5-m17n</code><ref name=":1" group="Note">This is <code>fcitx5-table-viqr</code>, <code>fcitx-table-viqr</code>, <code>ibus-table-viqr</code> on Debian.</ref> |<code>fcitx-m17n</code><ref name=":1" group="Note" /> |<code>ibus-table-tv</code><ref name=":1" group="Note" /> |<code>uim-viqr</code> | - | - | - | - | - |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<code>uim-m17n</code><ref name=":2" group="Note">On some distros, this is <code>uim-m17nlib</code>.</ref> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code><ref group="Note">Requires the [[Terra]] repository on Fedora.</ref> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code><ref group="Note"><code>ibus-openbangla</code> on Fedora with the [[Terra]] repository.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<code>fcitx5-varnam</code> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Others |- |Thai |<code>fcitx5-libthai</code> | - |<code>ibus-table-tv</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> | - |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Math Symbols |[[Compose Key]]? |[[Compose Key]]? |<code>ibus-table-mathwriter</code> | - | - | - | - | - | - |- |Completion |''built-in'' | - |<code>ibus-typing-booster</code> | - | - | - | - | - | - |- |''"Everything Else"'' |<code>fcitx5-m17n</code>? |<code>fcitx-m17n</code>? |<code>ibus-m17n</code>? |<code>uim-m17n</code><ref name=":2" group="Note" />? | - |<code>scim-m17n</code>? | - | - | - |} === Notes === <references group=Note/> This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. == How to choose your IME == This section represents the general case and the authors' opinions. It is not necessary to follow them. {| class="wikitable" |+Chinese !Situation !IME !Rime IME !Notes |- |Already using [[Rime]] | rowspan="3" |Rime | - | rowspan="3" |Rime is very powerful, but it comes with the cost of writing your own configuration files and [https://github.com/rime/home/wiki reading Chinese documentations], and thus is not recommended to beginners. |- |Prefer a highly customizable experience | - |- |Good at writing configuration files | - |- |Know Pinyin |Pinyin |''built-in'' | |- |Know Zhuyin |Chewing |℞ bopomofo |<code>libzhuyin</code> is not recommended (very unpopular), avoid <code>fcitx5-zhuyin</code> & <code>ibus-libzhuyin</code>. |- |Know Cangjie 3 / Quick 3 | rowspan="2" |Cangjie/Quick | rowspan="2" |℞ cangjie |Rime with [https://github.com/kennethso168/rime-cangjie3-extension rime-cangjie3-extension] |- |Know Cangjie 5 / Quick 5 | |- |Know SmartCangjie 6 |SCJ |℞ scj | |- |Know Jyutping |Rime |℞ cantonese |Jyutping from table-extras is barely usable |- |Know Wubi |Haifeng Wubi | |https://www.zhukun.net/archives/4856 |} {| class="wikitable" |+Japanese !Situation !IME !Notes |- |You hate Qt |Anthy |Anthy is unmaintained but it's written in GTK, so if you want your IME to fit into your GTK theme, use Anthy. |- |Otherwise |Mozc |Mozc is maintained by Google and has better suggestions, but you should also consider using the UT dictionaries. |} == References == 9b0e3f34417f7a974ee9156fbcfc23ef865d6083 0 414 4083 3587 2025-09-04T13:48:22Z Danny! 277 This sentence was a bit awkward grammatically I so split it up in order to make it more concise and easy to read. wikitext text/x-wiki [[Category:Programming Languages]] C is an imperative, procedural programming language invented in the early days of [[UNIX]] in the 1970s, adopted by the majority of UNIX systems.<ref>[https://dl.acm.org/doi/10.1145/2509136.2509515 <span style="color:#fc493b">https://dl.acm.org/doi/10.1145/2509136.2509515 <sup>🍣403]</ref> The language was initially implemented by Dennis Ritchie whilst working at Bell Labs, and later formalized through a series of standards, both by the committees and the author himself. For UNIX users, C facilitates the compilation of computer programs through a compiler, a program that translates an expression tree into machine code. Ritchie produced a C compiler for the DEC PDP-11. However, it lacked portability, so adoption was difficult in the rapidly evolving UNIX ecosystem. This issue would later be addressed by companies distributing UNIX and corresponding C compilers and pre-processors for their respective machines and instruction sets.<ref>[https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance Freedom and Portability - by Babbage - The Chip Letter], Babbage, 2024-05-05 (Accessed: 2025-08-09)</ref> The running, open standard, initially orchestrated by [[ANSI]] in 1989, now managed by the [https://www.open-std.org/jtc1/sc22/wg14/ C Language Working Group], defines what is formally recognized as "the C Programming Language".<ref>[https://en.cppreference.com/w/c/language/history History of C], cppreference.com, 2025-05-27 (Accessed: 2025-08-09)</ref> Some popular compilers for the C programming language include GNU GCC, Clang, TCC and MSVC, and less commonly Borland Turbo C, ICC, LCC, PCC and ACK (typically in legacy or "mission critical" systems). Many UNIX operating systems like [[OpenBSD]], [[FreeBSD]] and [[NetBSD]] use the Clang compiler toolchain, however, for example, [[Illumos]]<ref>[https://hackaday.com/2023/07/16/illumos-gets-a-new-c-compiler/ Illumos Gets A New C Compiler | Hackaday], Al Williams, 2023-07-16 (Accessed: 2025-08-09)</ref> and [[Plan 9]]<ref>[https://9p.io/sys/doc/compiler.html <span style="color:#fc493b">https://9p.io/sys/doc/compiler.html <sup>🍣DEAD?]</ref> use the portable C Compiler and Plan 9 C compiler respectively. C, as with many popular languages,<ref>[https://smlfamily.github.io/Basis/ Standard ML Basis Library], AT&T and Lucent Technologies, 2004-04-12 (Accessed: 2025-08-09)</ref><ref>[https://doc.rust-lang.org/beta/std/index.html std - Rust], doc.rust-lang.org, 2025-08-05 (Accessed: 2025-08-09)</ref><ref>[https://ziglang.org/documentation/master/std/ Zig Documentation], ziglang.org, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://docs.oracle.com/javase/8/docs/api/allclasses-frame.html All Classes (Java Platform SE 8 )], docs.oracle.com, 2025-06-30 (Accessed: 2025-08-09)</ref><ref>[https://www.scala-lang.org/api/current/ Scala 3], , 2025-07-29 (Accessed: 2025-08-09)</ref><ref>[https://ocaml.org/manual/5.2/api/index.html The OCaml API], , (Accessed: 2025-08-09)</ref> has a standard library known as a libc (given by its filename on many UNIX systems)<ref>[https://www.musl-libc.org/faq.html musl FAQ], , 2018-02-21 (Accessed: 2025-08-09)</ref>, however unlike other popular programming languages, there is significant fragmentation between specific implementations of several C standard library.<ref>[https://wiki.musl-libc.org/compatibility musl libc - Compatibility], , 2025-04-26 (Accessed: 2025-08-09)</ref><ref>[https://www.fefe.de/dietlibc/FAQ.txt <span style="color:#fc493b">https://www.fefe.de/dietlibc/FAQ.txt <sup>🍣DEAD?]</ref> Some popular libc implementations include dietlibc, [[musl]], [[Glibc|GNU glibc]], mlibc, Newlib and uClibc.<ref>[https://wiki.osdev.org/C_Library C Library], OSDev Wiki, 2024-06-24 (Accessed: 2025-08-09)</ref> It is advised by developers to ensure non-standard extensions are kept to a minimum, or otherwise use preprocessor directives to compile particular expressions depending on the active libc and/or target.<ref>[https://nullprogram.com/blog/2017/03/30/ How to Write Portable C Without Complicating Your Build], Chris Wellons, 2017-03-30 (Accessed: 2025-08-09)</ref> Note, many incompatibility concerns can be successfully alleviated through many automated build tools such as GNU Autotools, CMake, Meson, Zig's build toolchain among a plethora others, however for ideological<ref>[https://suckless.org/sucks/ software that sucks less | suckless.org software that sucks less], , 2025-05-29 (Accessed: 2025-08-09)</ref><ref>[https://www.interaction-design.org/literature/topics/keep-it-simple-stupid What is Keep It Simple, Stupid (KISS)?], Interaction Design Foundation - IxDF, 2016-06-05 (Accessed: 2025-08-09)</ref><ref>[http://harmful.cat-v.org/software/GNU/auto-hell GNU Auto*hell], , (Accessed: 2025-08-09)</ref> and practical<ref>[https://twdev.blog/2021/08/cmake/ Why CMake sucks? - twdev.blog], Tomasz Wisniewski, 2021-08-06 (Accessed: 2025-08-09)</ref><ref>[https://silverhammermba.github.io/blog/2023/01/06/gradle Gradle still sucks | Floating little leaves of code], Maxwell Anselm, 2023-01-06 (Accessed: 2025-08-09)</ref><ref>[https://web.archive.org/web/20181118080003/http://freshmeat.sourceforge.net/articles/stop-the-autoconf-insanity-why-we-need-a-new-build-system Stop the autoconf insanity! Why we need a new build system. – Freecode], Andrew McCall, 2003-06-21 (Accessed: 2018-11-18)</ref> reasons these tools may wish to be avoided. When approaching a C codebase, it is typical to find files entitled <code>INSTALL</code> and <code>README</code>, typically with either [[Markdown]] or [[Asciidoc]] extensions, and less commonly [[Roff]] and [[LaTeX|Tex]] files, which need to be processed by external tools besides your [[TUI|pager]] to recover useful information (they are often used in the context of academic projects or programs predating the success of Markdown and similar mark-up language). These files typically outline the configuration, building and installation for a variety of supported platforms and components, as well as outlining the [[Package Manager|dependencies and development headers]] used in the compilation and linking process.<ref>[https://github.com/Mercury-Language/mercury GitHub - Mercury-Language/mercury: The Mercury logic programming system.], Mercury-Language, 2013-08-09 (Accessed: 2025-08-09)</ref><ref>[https://github.com/NetBSD/src GitHub - NetBSD/src: Automatic conversion of the NetBSD src CVS module, use with care.], NetBSD, 2025-08-09 (Accessed: 2025-08-09)</ref> Upon successful installation, a binary with the appropriate headers for your CPU architecture and binary format (on UNIX, typically ELF) will appear in your [[Filesystem|file tree]], which can be executed unprivileged via its path or through its filename (assuming the binary's installation directory is appended to your user's <code>$PATH</code> variable). If a project doesn't provide such facilities, knowledge of your preferred C compiler and linker may be useful in attempting to compile and link binaries for your (or other) systems. When writing C, for contributing to [[FLOSS|open source]] projects, there are several major coding standards and style guides you should make yourself aware of, each describing the syntactic, naming, meta-programming and structural components of a C code base; these may include [https://www.gnu.org/prep/standards/html_node/index.html GNU Coding Standards] , [https://www.kernel.org/doc/html/v4.10/process/coding-style.html Linux kernel coding style], [https://git.9front.org/plan9front/plan9front/d4a6dc8910014eb18eb72afa566c9839a9957b47/sys/man/6/style/f.html Plan 9 Coding Conventions], [https://suckless.org/coding_style/ Suckless Coding Style], [http://doc.cat-v.org/bell_labs/pikestyle "Pike Style"], [https://nxr.netbsd.org/xref/src/share/misc/style NetBSD Source Code Style Guide], however many more exist and vary on a project-by-project basis. It is always preferable to respect a projects' expected style for a variety of reasons, namely, consistency within the code base, appropriate patch application, code review automation, and maintainability.<ref>[https://docs.kernel.org/process/5.Posting.html 5. Posting patches — The Linux Kernel documentation], The kernel development community, 2025-07-27 (Accessed: 2025-08-09)</ref> Learning C is an integral part of beginning contribution to the majority of [[FOSS|open source]] code bases, however it isn't particularly an easy task, especially with little background in computer programming or limited knowledge of hardware design and operating system design & interfaces. Many resources and online books are listed below: # Ritchie, Denis & Kernighan, Brian (1988). ''C Programming Language'': https://a.co/d/6Yrgcfo # The FreeBSD Documentation Project (1995–2024). ''FreeBSD Developers' Handbook'': https://docs.freebsd.org/en/books/developers-handbook/ # Gustedt, Jens (2019). ''Modern C'': https://www.manning.com/books/modern-c # Learn X in Y minutes (n.d.). ''Where X=C'': https://learnxinyminutes.com/docs/c/ # ''Learn C'': https://www.learn-c.org/ # Miller, Dean & Perry, Greg (n.d.). ''C Programming Absolute Beginner's Guide'' (3rd ed.): https://a.co/d/5558uzl # Seacord, Robert (n.d.). ''Effective C: An Introduction to Professional C Programming'': https://a.co/d/i3q6T2M Criticisms of C are abundant and controversial,<ref>[https://web.mit.edu/~simsong/www/ugh.pdf The UNIX-HATERS Handbook], Simson Garfinkel, Daniel Weise, and Steven Strassmann, 1994 (Accessed: 2025-08-09)</ref> many attribute issues regarding C to fragmentation and portability issues,<ref>[http://doc.cat-v.org/henry_spencer/ifdef_considered_harmful #ifdef Considered Harmful, or Portability Experience With C News], Henry Spencer, (Accessed: 2025-08-09)</ref> lack of type safety and primitive resource access checks,<ref>[https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review <span style="color:#fc493b">https://www.researchgate.net/publication/371166462_C_Programming_Language_A_Review <sup>🍣403]</ref> poor administration on part of the C Language Working Group,<ref>[https://cor3ntin.github.io/posts/c/ The problem with C], cor3ntin, 2020-08-30 (Accessed: 2025-08-09)</ref> and overall worsening over time.<ref>[https://www.i-programmer.info/news/184-cc/16204-c23-what-we-have-to-suffer.html C23 - What We Have To Suffer], Harry Fairhead, 2023-04-05 (Accessed: 2025-08-09)</ref><ref>[https://wiki.theory.org/YourLanguageSucks YourLanguageSucks], TheoryOrg, 2022-09-29 (Accessed: 2025-08-09)</ref> == References == <references /> bdc31d85717f7a881acf1892e7ccaf9f3e59ddde 0 919 4084 3912 2025-09-04T19:34:28Z Zyankali 267 Adding it to the Software category wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox |image=[[File:Fish-Shell.png|thumb]] |caption=Fish-shell Logo |title=Fish |releasestatus=Maintained |lastrelease=4.0.2, 2025-04-20 |firstrelease=2.0.0, 2013-09-01 |languages=[[Rust]] |developers=Fish-shell developers |website=[https://fishshell.com/ fishshell.com] }} '''Fish''' (Friendly Interactive Shell) is a [[CLI]] with an out-of-the-box, feature-rich experience.<ref>[[wikipedia:Fish_(Unix_shell)|Fish (Unix shell)]], Wikipedia (Accessed: 2025-08-27)</ref> It offers the user features such as command suggestions, web-based configuration, colorful aesthetics<ref>[[https://fishshell.com fish shell]], Ridiculous Fish (Accessed: 2025-08-27)</ref> as well as expanded keyboard shortcuts<ref>[[https://fishshell.com/docs/current/interactive.html#shared-bindings Interactive use — fish-shell 4.0.2 documentation]], Fish-shell (Accessed: 2025-08-27)</ref>. Unlike many other commonly used shells, like Bash or Zsh, it does not adhere to the [[POSIX]] standard, which may cause Fish to throw errors if a command contains POSIX-specific syntax. == History == With the release of Fish 4.0, the project received a major rewrite, moving it from [[C++]] over to the [[Rust]] programming language. This idea was already proposed in 2023, by one of the developers via a [https://github.com/fish-shell/fish-shell/pull/9512 pull request]. While it was meant to be a humorous proposal to be read by other fish developers, it quickly gathered a lot of attention. The goal of the migration was to allow for easier [[Package Manager|packaging]]—particularly for LTS distros and older versions of macOS—gain access to better tooling, enable further multi-threading and to attract new contributors through the active Rust community.<ref>{{Cite|url=https://fishshell.com/blog/rustport/|title=Fish 4.0: The Fish Of Theseus|author=Fish-shell|year=2024|accessdate=2025-08-27}}</ref> == References == <references /> 12138fdb5974c879900d51930ea2ccb3f45ef207 0 198 4085 4022 2025-09-05T08:23:27Z Hog 161 added arco linux wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux]] |Arco Linux is a fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == 2992da340a773d548a9afebb0c7deac537730f33 4087 4085 2025-09-05T08:31:43Z Hog 161 wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or the [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now [[source-available]]<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == a1af6ef85262b0827640d6f8d2c2dd6c11a50690 4088 4087 2025-09-05T08:35:40Z Hog 161 wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == d3cd3f94947875bd5c59a3399294c7174f11391c 4097 4088 2025-09-07T03:41:02Z Violet 97 Add postmarketOS under Independent Distributions wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |Slax |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == 58fcf0776bc3936318f003aaf73edb1c77b72f0c 0 1011 4086 2025-09-05T08:31:06Z Hog 161 created stub wikitext text/x-wiki {{stub}}{{DistributionInfobox|title=Arco Linux|image=[[File:Arcolinux.svg| 200px]]|caption=The Arco Linux logo|releasestatus=Discontinued|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=[[KDE Plasma]],[[Xfce]]|usagetype=Desktop|architectures=x86_64|website=[https://arcolinux.com/ arcolinux.com]}} 71a3ce44f30ae055d67f02c3fdf83ee3b3be7e72 0 918 4089 4056 2025-09-05T08:49:19Z Hog 161 added effects list wikitext text/x-wiki Easy Effects, available on [https://flathub.org/apps/com.github.wwmm.easyeffects Flathub] , is a tool for adding effects to audio input and output under PipeWire. It is a GTK application that bundles many effects and tools, making it easier to use out of the box. Easy Effects does not support external plugins. If you would like to use external plugins, see (list advanced tools here). For the PulseAudio counterpart, see [[PulseEffects]]. = <u>Application layout</u> = [[File:EasyEffects-Input-Effects-empty.png|thumb|Easy Effects as it opens by default]] == The effects list == * Auto gain * Bass enhancer * Bass loudness * Compressor * Convolver * Crossfeed * Crystalizer * De-esser * Delay * Deep noise remover * Echo canceller * Equalizer * Exciter * Expander * Filter (low-pass, high-pass, band-pass and band-reject modes) * Gate * Level meter * Limiter * Loudness * Maximizer * Multiband compressor * Multiband gate * Noise reduction * Pitch shift * Reverberation * Speech processor * Stereo tools == Input and Output == == Recorders and Players == == Presets == == Settings == = Effects = == Simple and useful == === Equalizer === === Noise Reduction === === Compressor === === Delay === === Level Meter === == Advanced and Niche == = Quirks = == Interaction with OBS == To capture unmodified sound from the desktop, you will want to configure OBS to connect to "Easy Effects Sink" for its "Desktop Audio" "Properties". This can often result in a garbled audio stream. To fix this, add "Stereo Tools" to the top of the output effects list. Easy Effects will not modify the "Mic/Aux" audio input in OBS by default. To get this effect, you may either enable "Process All Input Streams" in the hamburger menu top-right -> "Preferences" -> "General" -> "Audio" -> "Process All Input Streams". Or you may select "Easy Effects Source" as the source for "Mic/Aux" in its "Properties". It is recommended to have "Stereo Tools" at the top of the input effects list as well. d8408c513c6de58bb89110180952ef25c94756fd 6 1012 4090 2025-09-05T09:08:47Z Hog 161 wikitext text/x-wiki grub theme for endeavouros 376c7144e7302fbbff619f34f14f59dfcf8b9e27 0 707 4091 2960 2025-09-05T09:10:15Z Hog 161 wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox |image=[[File:Grub-knoppix.jpg|thumb]] |caption=Grub Boot Menu |title=GRUB |releasestatus=Maintained |lastrelease=2.12, 2023-12-20 |languages=[[C]], [[Assembly]] |developers=GNU Project |website=[http://gnu.org/software/grub/ GNU Page] }}'''GRUB''' (short for '''GRand Unified Bootloader''') is a [[bootloader]] designed for [[UNIX|UNIX-like]] systems developed by the GNU Project. It provides the user with the option to choose between different [[Operating System|operating systems]] or [[kernel]] versions without having to use the [[BIOS]]. Originally developed by Erich Boleyn<ref>[http://www.uruk.org/grub/ GRUB -- GRand Unified Bootloader], Erich Boleyn (Accessed: 2025-07-01)</ref>, GRUB is now a part of the GNU project and comes with two versions, GRUB 0 (Also known as GRUB Legacy) and GRUB 2. Since GRUB Legacy is obsolete, this article mainly describes GRUB 2. GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU Hurd with the University of Utah's Mach 4 microkernel (now known as GNU Mach). Erich and Brian Ford designed the Multiboot Specification, because they were determined not to add to the large number of mutually-incompatible PC boot methods.<ref name=":0">https://www.gnu.org/software/grub/manual/grub/grub.html#Overview GNU website, 2025 (Imported 02.07.2025)</ref> Around 2002, Yoshinori K. Okuji started work on PUPA (Preliminary Universal Programming Architecture for GNU GRUB), aiming to rewrite the core of GRUB to make it cleaner, safer, more robust, and more powerful. PUPA was eventually renamed to GRUB 2, and the original version of GRUB was renamed to GRUB Legacy. <ref name=":0" /> GRUB contains support for multiple file systems ( [[FAT32]], [[ext4]], [[Btrfs]] or [[XFS]].) Both GRUB 2 and GRUB 0 systems support [[UEFI]] and BIOS-based systems. [[File:EndeavourOS Grub 2 theme.png|alt=GRUB Menu with purple and pink colours. with the text "EndeavourOS on linux-lts"|thumb|Endeavour OS GRUB theme]] GRUB can be Customised (Riced) into many different styles. Some distros, such as [[EndeavourOS]] have a pre-installed theme. == See More == * [https://wiki.archlinux.org/title/Grub Grub on ArchWiki] == References == 74fc5a3a023e8d8c274fd4669e38998199c0def6 0 405 4092 4001 2025-09-05T09:32:21Z Hog 161 wikitext text/x-wiki [[Category:Terminology]] {{Cleanup|Short page}}Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Linux and other open source operating systems will avoid or not support proprietary software when possible. This is mainly due to incompatible licensing.<ref>https://solutionshub.epam.com/blog/post/proprietary-software-definition-examples Epam, 2025 (imported 27th June 2025)</ref> However some proprietary software included with certain Linux distros include NVIDIA graphics drivers, certain Wi-Fi and Bluetooth firmware, proprietary games via platforms like Steam. Some examples of proprietary software include, but are not limited to, Microsoft Windows, macOS, Adobe Photoshop, Steam, the Epic Games Launcher and the Microsoft Office Suite. == References == 865b0d9c4c105e62fe88c4967fc469e1f1157fbd 0 517 4093 3678 2025-09-05T09:33:54Z Hog 161 wikitext text/x-wiki {{Needs_Citations}} A system call (syscall) is a mechanism that allows a program to interact with the [[Operating System|operating system]]. It acts as a bridge between the user space (where applications run) and the [[kernel]] space (where the operating system manages hardware and system resources). Programs use system calls to request services from the OS, such as managing files, processes, or hardware devices. For example, when you open a file, your application cannot directly access the hardware. Instead, it makes a system call (e.g., open()), which the OS handles to perform the requested task. Note that this is not a guide for ALL syscalls, but it is a guide to get you familiar enough with syscalls and strace. == Why Should You Learn About System Calls? == 1. Understanding How Programs Work: - System calls reveal how applications interact with the operating system to perform tasks like file handling, memory management, and networking. 2. Efficient Troubleshooting: - Knowing system calls can help diagnose performance issues or bugs by identifying which calls a program relies on. 3. Optimizing Software: - When developing programs, understanding system calls allows you to write efficient code by leveraging the right OS-level functions. 4. Security Awareness: - Many exploits and vulnerabilities target how system calls are used (or misused). Understanding them helps in writing secure code. 5. Kernel-Level Development: - If you're interested in low-level programming, such as operating system development or driver creation, system calls are fundamental. Basically, system calls are the foundation of how software and operating systems interact, making them essential knowledge for both beginner and advanced developers. == Categories of System Calls == System calls are grouped into five main categories: '''Process Control''' – Manage processes (create, terminate, etc.). '''File Management''' – Handle file operations (open, read, write, close). '''Device Management''' – Interact with hardware devices. '''Information Maintenance''' – Exchange information between the OS and programs. '''Communication''' – Enable processes to communicate. 1. '''Process Control''' * fork(): Creates a new process (child) that runs the same program as the parent. * exit(): Terminates the process and frees resources. * exec(): Replaces the current program in a process with a new one. 2. '''File Management''' * open(): Opens a file for reading or writing. * read(): Reads data from a file (multiple processes can read simultaneously). * write(): Writes data to a file (only one process can write at a time). * close(): Closes an open file. 3. '''Device Management''' * ioctl(): Performs device-specific operations not covered by standard calls (e.g., configuring hardware). 4. '''Information Maintenance''' * getpid(): Returns the process ID of the current process. * alarm(): Sets a timer to deliver a signal after a specified time. * sleep(): Pauses the process for a given time. 5. '''Communication''' * pipe(): Enables communication between processes via file descriptors. * shmget(): Allocates shared memory for process communication. * mmap(): Maps files or devices into a process's memory. === Why Use strace? === * Debug program behaviour (e.g., "Why is this program failing?"). * Identify which files, devices, or network resources a program accesses. * Learn what system calls a program makes for educational purposes. 97251beded4b4ff1df0f41788a3ec1c7568b87c5 0 718 4094 3847 2025-09-05T10:57:39Z Hog 161 wikitext text/x-wiki {{DISPLAYTITLE:macOS}} [[File:Apple-Logo-Transparent.png|thumb|right]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical [[Operating System|operating systems]] developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a [[UNIX]] (Darwin/[[BSD]]) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> bb179693dda19aec675f769e2a02bfba3ee25183 0 679 4095 2961 2025-09-05T11:10:07Z Hog 161 wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.50.0 (2025-06-16) | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git's early design emphasized a distributed workflow similar to BitKeeper's but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like [[GitHub]], which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. == References == 214834d1928600d4fedb92af6f80718f75fba93e 0 651 4096 3403 2025-09-05T11:12:34Z Hog 161 wikitext text/x-wiki An operating system (OS) is a collection of [[software]] that manages a computer's [[hardware]] and [[applications]] by allocating resources, including memory, CPU, input/output devices and file storage.<ref>[https://www.ibm.com/think/topics/operating-systems What is an Operating System? | IBM], Stephanie Susnjara & Ian Smalley, 2025-03-05 (Accessed: 2025-08-09)</ref> A user interacts with an operating system through a [[user interface]] (UI), which issues commands in a language the OS can understand. The UI can be either a [[GUI|graphical user interface]] (GUI) or a [[command-line interface]] (CLI). All computer systems need an OS to function. == References == 749fbb4f69b0d2cb1fd3274f105575c54abff5d5 0 1013 4098 2025-09-07T04:01:40Z Violet 97 create postmarketOS page, with infobox and a short summary on what it is. wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = postmarketOS | image = [[File:PostmarketOS_logo.png|postmarketOS logo]] | caption = The postmarketOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APK]] | defaultdesktops = Phosh, Plasma Mobile, Sxmo, GNOME, Xfce | usagetype = Embedded, Desktop | architectures = amd64, aarch64, ppc64le, loongarch64 | website = [https://postmarketos.org https://postmarketos.org/] }} postmarketOS is an [[Alpine_Linux]]-based [[Linux Distributions|distribution]] built mainly for consumer electronics like handsets, tablets, and laptops. Its goal is to extend the life of those devices and bring full control over them to the end user, promoting a healthier and more sustainable society. Keeping mostly everything open source, devices that do not receive further support from the OEM (for example, old Android phones) can be kept alive with updates coming from package repositories and the mainline Linux kernel, also taking advantage of all security updates which also stopped after the OEM quit updating the device. postmarketOS is not quite ready for everyone just yet, as many devices still lack complete hardware support and daily usability (and reliability) can vary. However, it continues to evolve rapidly with contributions from the community, making it an exciting project for hackers and a promising path toward long-term, sustainable device usage. b01e0e8d4333a0f23967351d59c96512a3869917 4099 4098 2025-09-07T04:02:42Z Violet 97 Fix the Alpine Linux hyperlink being written Alpine_Linux instead of Alpine Linux wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = postmarketOS | image = [[File:PostmarketOS_logo.png|postmarketOS logo]] | caption = The postmarketOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APK]] | defaultdesktops = Phosh, Plasma Mobile, Sxmo, GNOME, Xfce | usagetype = Embedded, Desktop | architectures = amd64, aarch64, ppc64le, loongarch64 | website = [https://postmarketos.org https://postmarketos.org/] }} postmarketOS is an [[Alpine_Linux|Alpine Linux]]-based [[Linux Distributions|distribution]] built mainly for consumer electronics like handsets, tablets, and laptops. Its goal is to extend the life of those devices and bring full control over them to the end user, promoting a healthier and more sustainable society. Keeping mostly everything open source, devices that do not receive further support from the OEM (for example, old Android phones) can be kept alive with updates coming from package repositories and the mainline Linux kernel, also taking advantage of all security updates which also stopped after the OEM quit updating the device. postmarketOS is not quite ready for everyone just yet, as many devices still lack complete hardware support and daily usability (and reliability) can vary. However, it continues to evolve rapidly with contributions from the community, making it an exciting project for hackers and a promising path toward long-term, sustainable device usage. da13abbe1ffe1d8123518137ef6170260831a77d 4100 4099 2025-09-07T04:04:52Z Violet 97 fix some typos throughout the page wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = postmarketOS | image = [[File:PostmarketOS_logo.png|postmarketOS logo]] | caption = The postmarketOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APK]] | defaultdesktops = Phosh, Plasma Mobile, Sxmo, GNOME, Xfce | usagetype = Embedded, Desktop | architectures = amd64, aarch64, ppc64le, loongarch64 | website = [https://postmarketos.org https://postmarketos.org/] }} postmarketOS is an [[Alpine_Linux|Alpine Linux]] based [[Linux Distributions|distribution]] built mainly for consumer electronics like handsets, tablets, and laptops. Its goal is to extend the life of those devices and bring full control over them to the end user, promoting a healthier and more sustainable society. Keeping mostly everything open source, devices that do not receive further support from the O.E.M. (for example, old Android phones) can be kept alive with updates coming from package repositories and the mainline Linux kernel, also taking advantage of all security updates which also stopped after the O.E.M. quit updating the device. postmarketOS is not quite ready for everyone just yet, as many devices still lack complete hardware support, and daily usability/reliability can vary. However, it continues to evolve rapidly with contributions from the community, making it an exciting project for hackers and a promising path toward long-term, sustainable device usage. 21b29a6b39b1f114bc2611e817c3924633e144d5 4101 4100 2025-09-07T04:22:30Z Violet 97 Add overview, History and Installation categories wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = postmarketOS | image = [[File:PostmarketOS_logo.png|postmarketOS logo]] | caption = The postmarketOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APK]] | defaultdesktops = Phosh, Plasma Mobile, Sxmo, GNOME, Xfce | usagetype = Embedded, Desktop | architectures = amd64, aarch64, ppc64le, loongarch64 | website = [https://postmarketos.org https://postmarketos.org/] }} postmarketOS is an [[Alpine_Linux|Alpine Linux]] based [[Linux Distributions|distribution]] built mainly for consumer electronics like handsets, tablets, and laptops. Its goal is to extend the life of those devices and bring full control over them to the end user, promoting a healthier and more sustainable society. Keeping mostly everything open source, devices that do not receive further support from the O.E.M. (for example, old Android phones) can be kept alive with updates coming from package repositories and the mainline Linux kernel, also taking advantage of all security updates which also stopped after the O.E.M. quit updating the device. postmarketOS is not quite ready for everyone just yet, as many devices still lack complete hardware support, and daily usability/reliability can vary. However, it continues to evolve rapidly with contributions from the community, making it an exciting project for hackers and a promising path toward long-term, sustainable device usage. == Overview == * Developed by: Community contributors (pmOS project) * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Rolling Release * Package Manager: [[APK]], with support for [[Flatpak]] * Architectures: amd64, aarch64, ppc64le, loongarch64 * Focus: Long-term device support, sustainability, privacy == History == postmarketOS was announced in May 2017 by [https://github.com/ollieparanoid Oliver Smith (ollieparanoid)], who envisioned a ten-year lifecycle for smartphones, inspired by frustrations with rapid device obsolescence in the Android ecosystem.<ref>[https://postmarketos.org/blog/2017/05/26/intro/ postmarketOS announcement blog], accessed 2025-09-07</ref> Unlike Android, which runs on a heavily modified Linux kernel and relies on proprietary vendor blobs, postmarketOS aims to bring **mainline Linux kernels** to as many devices as possible. This design choice increases portability and long-term maintainability. The project gained traction among developers, hackers, and enthusiasts who wanted more control over their devices, with early ports to devices such as the Nokia N900, Google Nexus 5, and various Samsung Galaxy models. Today, dozens of devices are supported to varying degrees, with a few (such as the PinePhone and Librem 5) being nearly daily-driver ready. == Installation == The installation process is based around the **pmbootstrap** tool, which handles building images and flashing them to devices. Users can select supported devices, kernels, and user interfaces (like Phosh, Plasma Mobile, Sway, etc). For devices with strong support (such as PinePhone, and other devices on the community category), [https://postmarketos.org/install/ prebuilt] images are available. For older Android phones, users may need to unlock the bootloader and manually flash the generated image from pmbootstrap. Similar to Arch Linux’s [[archinstall]] script, pmbootstrap automates configuration while still allowing advanced customization. == References == 91645366ed12c1d0eab4ea960aa370490042c74c 4102 4101 2025-09-07T04:25:26Z Violet 97 shorten summary of the os wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = postmarketOS | image = [[File:PostmarketOS_logo.png|postmarketOS logo]] | caption = The postmarketOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APK]] | defaultdesktops = Phosh, Plasma Mobile, Sxmo, GNOME, Xfce | usagetype = Embedded, Desktop | architectures = amd64, aarch64, ppc64le, loongarch64 | website = [https://postmarketos.org https://postmarketos.org/] }} postmarketOS is an [[Alpine_Linux|Alpine Linux]]-based [[Linux Distributions|distribution]] designed for consumer devices such as phones, tablets, and laptops. Its mission is to extend the lifespan of hardware and give users full control, fostering a more sustainable and open ecosystem. By staying open source, it allows unsupported devices (like old Android phones) to keep receiving updates from package repositories and the mainline Linux kernel, including important security fixes. While many devices still lack full hardware support and daily usability can vary, postmarketOS is evolving quickly through community contributions, making it both a promising path for sustainable device usage and an exciting project for enthusiasts. == Overview == * Developed by: Community contributors (pmOS project) * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Rolling Release * Package Manager: [[APK]], with support for [[Flatpak]] * Architectures: amd64, aarch64, ppc64le, loongarch64 * Focus: Long-term device support, sustainability, privacy == History == postmarketOS was announced in May 2017 by [https://github.com/ollieparanoid Oliver Smith (ollieparanoid)], who envisioned a ten-year lifecycle for smartphones, inspired by frustrations with rapid device obsolescence in the Android ecosystem.<ref>[https://postmarketos.org/blog/2017/05/26/intro/ postmarketOS announcement blog], accessed 2025-09-07</ref> Unlike Android, which runs on a heavily modified Linux kernel and relies on proprietary vendor blobs, postmarketOS aims to bring **mainline Linux kernels** to as many devices as possible. This design choice increases portability and long-term maintainability. The project gained traction among developers, hackers, and enthusiasts who wanted more control over their devices, with early ports to devices such as the Nokia N900, Google Nexus 5, and various Samsung Galaxy models. Today, dozens of devices are supported to varying degrees, with a few (such as the PinePhone and Librem 5) being nearly daily-driver ready. == Installation == The installation process is based around the **pmbootstrap** tool, which handles building images and flashing them to devices. Users can select supported devices, kernels, and user interfaces (like Phosh, Plasma Mobile, Sway, etc). For devices with strong support (such as PinePhone, and other devices on the community category), [https://postmarketos.org/install/ prebuilt] images are available. For older Android phones, users may need to unlock the bootloader and manually flash the generated image from pmbootstrap. Similar to Arch Linux’s [[archinstall]] script, pmbootstrap automates configuration while still allowing advanced customization. == References == 6c8df6de5c61ed78b6ef88820face69ad100244f 4103 4102 2025-09-07T10:55:45Z Madonuko 140 tidy wikitext text/x-wiki {{DISPLAYTITLE:postmarketOS}} [[Category:Linux Distributions]] {{stub}} {{DistributionInfobox | title = postmarketOS | image = [[File:PostmarketOS_logo.png|postmarketOS logo]] | caption = The postmarketOS logo | releasestatus = Maintained | releasemodel = [[Rolling]] Release | packagemanager = [[APK]], [[Flatpak]] | defaultdesktops = [[Phosh]], [[Plasma Mobile]], [[Sxmo]], [[GNOME]], [[XFCE]] | usagetype = Embedded, Desktop | architectures = amd64, aarch64, ppc64le, loongarch64 | website = [https://postmarketos.org https://postmarketos.org/] }} postmarketOS is an [[Alpine Linux]]-based [[Linux Distributions|distribution]] designed for consumer devices such as phones, tablets, and laptops. Its mission is to extend the lifespan of hardware and give users full control, fostering a more sustainable and open ecosystem. By staying [[open source]], it allows unsupported devices (like old [[Android]] phones) to keep receiving updates from [[package]] [[repository|repositories]] and the mainline Linux kernel, including important security fixes. While many devices still lack full hardware support and daily usability can vary, postmarketOS is evolving quickly through community contributions, making it both a promising path for sustainable device usage and an exciting project for enthusiasts. == History == postmarketOS was announced in May 2017 by [https://github.com/ollieparanoid Oliver Smith (ollieparanoid)], who envisioned a ten-year lifecycle for smartphones, inspired by frustrations with rapid device obsolescence in the Android ecosystem.<ref>[https://postmarketos.org/blog/2017/05/26/intro/ postmarketOS announcement blog], accessed 2025-09-07</ref> Unlike Android, which runs on a heavily modified Linux kernel and relies on proprietary vendor blobs, postmarketOS aims to bring '''mainline Linux kernels''' to as many devices as possible. This design choice increases portability and long-term maintainability. The project gained traction among developers, hackers, and enthusiasts who wanted more control over their devices, with early ports to devices such as the Nokia N900, Google Nexus 5, and various Samsung Galaxy models. Today, dozens of devices are supported to varying degrees, with a few (such as the [[PinePhone]] and [[Librem]] 5) being nearly daily-driver ready. == Installation == The installation process is based around the <code>pmbootstrap</code> tool, which handles building images and flashing them to devices. Users can select supported devices, [[kernel]]s, and user interfaces (like Phosh, Plasma Mobile, [[Sway]], etc). For devices with strong support (such as PinePhone, and other devices on the community category), [https://postmarketos.org/install/ prebuilt] images are available. For older Android phones, users may need to unlock the bootloader and manually flash the generated image from <code>pmbootstrap</code>. Similar to [[Arch Linux]]’s [[archinstall]] script, <code>pmbootstrap</code> automates configuration while still allowing advanced customization. == References == a84d5a926a5b2a250d67b66790c52961d35ac31c 0 1 4104 3074 2025-09-07T13:47:53Z Atmois 13 Reword "how to help" as per suggestion from [[User:Kaizen]] wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">atl.wiki</h1> <div class="home-header-subtitle">A wiki for Linux and FOSS topics by the [https://allthingslinux.org All Things Linux] non-profit organization</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''atl.wiki''' is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out <code>#quick-support</code> and <code>#support-forum</code> in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#atl-wiki</code> channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''atl.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these 5 values when editing on the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> {{Special:RecentChanges|namespace=0|limit=10|hidebots}} </div> </div> [[File:Atl.wiki CTA.png|center|frameless|960x960px]] e8f66f2dd65db34435262146162ae366f07afee6 4105 4104 2025-09-07T13:48:27Z Atmois 13 Fix prose wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">atl.wiki</h1> <div class="home-header-subtitle">A wiki for Linux and FOSS topics by the [https://allthingslinux.org All Things Linux] non-profit organization</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''atl.wiki''' is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out <code>#quick-support</code> and <code>#support-forum</code> in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#atl-wiki</code> channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''atl.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> {{Special:RecentChanges|namespace=0|limit=10|hidebots}} </div> </div> [[File:Atl.wiki CTA.png|center|frameless|960x960px]] 856d17be012b02753baff22e66cb0e8e825ed14d 4106 4105 2025-09-07T14:14:52Z Atmois 13 Add more info in the about box from suggestions from [[User:Danny!]] wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">atl.wiki</h1> <div class="home-header-subtitle">A wiki for Linux and FOSS topics by the [https://allthingslinux.org All Things Linux] 501(c)3 non-profit organization</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''atl.wiki''' is a centralised, easy-to-use reference for the Linux and FOSS ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[ATL:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#atl-wiki</code> channel on the [https://discord.gg/linux Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. ====== General Support ====== If you need Linux support, ensure to check out <code>#quick-support</code> and <code>#support-forum</code> in our [https://discord.gg/linux Discord server]! You can read more about the project's goals and the history of atl.wiki on the [[ATL:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''atl.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> {{Special:RecentChanges|namespace=0|limit=10|hidebots}} </div> </div> [[File:Atl.wiki CTA.png|center|frameless|960x960px]] f042bedfabdb5b92bfa843ebf5003b4706ef3486 8 196 4107 3518 2025-09-07T14:27:59Z Atmois 13 Fix link javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://atl.wiki/ATL:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://s.atl.wiki/script.js'; s.setAttribute('data-website-id', '21f384be-587d-4b00-8727-203d00c898d5'); document.head.appendChild(s); abc2d4d6a891029d3f2bfefe7b1c6ffde8d6c9d2 0 682 4108 3665 2025-09-08T11:40:12Z Hog 161 wikitext text/x-wiki {{Needs Citations}}{{stub}} {{DistributionInfobox | title = Puppy Linux | image = [[File:Puppy logo.svg|frameless|Puppy Linux Logo]] | caption = Puppy Linux Logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]], [[XBPS]], PPM | defaultdesktops = JWM, [[Xfce]], LXDE | usagetype = Desktop | architectures = x86_64, x86, ARM | website = [https://puppylinux-woof-ce.github.io/ Link] }} '''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003 by Barry Kauler. === <u>Hardware Requirements</u> === ==== 64-Bit Bookworm ==== <u>Recommended</u> * 64-bit dual-core CPU * 2-4 GB RAM * 5 GB Storage Space <u>Minimum</u> * 64-Bit single-core CPU * 1GB RAM * 5GB Storage Space ==== 32-Bit Bookworm ==== <u>Recommended</u> * 32-bit dual-core CPU * 2-4 GB RAM * 5 GB Storage Space <u>Minimum</u> * 32-Bit single-core CPU * 1GB RAM * 5GB Storage Space a40528b97a27b514fa05d68d1f93b1b4718dbe2f 0 848 4109 3806 2025-09-08T11:43:50Z Hog 161 wikitext text/x-wiki [[category:Linux Distributions]] [[category:Desktop Environments]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued in around 2022 to 2023<ref>[https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2022 (Accessed: 2022-05-14)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the [[Desktop Environments|DE]], and [[Arch Linux]] was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to [[Ubuntu]]. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were removed and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The new CutefishOS team, which was rebased to Sichuan, also did not live long, due to lack of Western support, and silently died out between mid-2021 and 2022. === CutefishOS Reborn === CutefishOS Reborn was a Western community's attempt to revive CutefishOS's development. It gauged some interest but very quickly died off in mid-2022. === LingmoOS === [https://github.com/LingmoOS/LingmoOS LingmoOS] is an active revival<ref>[https://github.com/orgs/cutefishos/discussions/22 Is this project dead or still in development? · cutefishos · Discussion #22], GitHub, 2023 (Accessed: 2025-08-11)</ref> of CutefishOS, but it has not received major attention from the media. == CyberDE == [[File:VSCode In Cutefish.png|thumb|right|Visual Studio Code running on CutefishDE.<ref>[https://cutefishos.com CutefishOS], Cutefish Team, 2025 (Accessed: 2025-08-11)</ref>]] The desktop environment that came with CyberOS, usually referred to as ''Cyber'' or ''CyberDE'', was made using Qt5 and was commonly said to resemble the look and feel of [[MacOS|Mac OS X]].<ref>[https://wiki.archlinux.org/title/Cutefish Cutefish], ArchWiki (Accessed: 2025-08-11)</ref> <code>cyber-launcher</code> came with the dock at the bottom, which had a button that opens the launcher, and a status line bar with embedded global context menus at the top. Many parts of the interface were also partially transparent. Window controls were at the top right corner and resembles [[Microsoft Windows]], while titles were centred. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives] == References == b875cfd725c0d46d4dc1cbaa48726932dc2ed796 0 884 4110 4058 2025-09-08T19:41:55Z Satnus 215 Undo revision [[Special:Diff/4058|4058]] by [[Special:Contributions/Hamachitan|Hamachitan]] ([[User talk:Hamachitan|talk]]) Somebody keep an eye on Hamachitan! wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>https://lubuntu.me/ Lubuntu, Accessed: 2025-08-22</ref> * [[Fedora]] LXQt spin<ref>https://fedoraproject.org/spins/lxqt Fedora, Accessed 2025-08-22</ref> * [[CachyOS]]: available in installer<ref>https://wiki.cachyos.org/installation/desktop_environments/ CachyOS, Accessed:2025-08-22</ref> * [[SparkyLinux]]<ref>https://wiki.sparkylinux.org/doku.php/about Sparky Linux, Accessed:2025-08-22</ref> * [[Debian]]: available in installer<ref>https://wiki.debian.org/LXQt Debian Wiki, Accessed:2025-08-22</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>https://packages.debian.org/stable/lxqt-core Debian, Accessed 2025-08-23</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>https://packages.debian.org/trixie/lxqt Debian, Accessed:2025-08-23</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>https://packages.debian.org/stable/task-lxqt-desktop Debian, Accessed:2025-08-23</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>https://archlinux.org/groups/x86_64/lxqt/ Arch Linux, Accessed:2025-08-23</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template Github, Accessed:2025-08-23</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers LXQt wiki, Accessed:2025-08-23</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions LXQt wiki, Accessed:2025-08-23</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight lang="text">exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == 373bd0602ce360cb230ff8b5353d07c4040dcf51 0 909 4111 4003 2025-09-08T21:47:27Z Satnus 215 Increased content, added infocard, fixed citation. Will make it longer tomorrow. wikitext text/x-wiki {{DISPLAYTITLE:nvi}} [[Category:Software]] {{SoftwareInfobox | title = '''nvi''' | image = [[File:Nvi.png|thumb]] | caption = Text editor nvi | releasestatus = Maintained | lastrelease = 1.81.6 | languages = [[C]] | developers = Keith Bostic & Sven Verdoolaege | website = [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page Berkeley Vi Editor (nvi) home page.] }} '''nvi''' is a text editor for [[Unix-Like]] operating systems. nvi was originally created as a replacement for the [[vi]] editor and first appeared in 4.4BSD.<ref name="openbsd-manpage">[https://man.openbsd.org/vi.1 Man page for nvi], nvi, April 24, 2024 (Accessed: 2025-09-09)</ref> Unlike other modern implementations of the vi editor such as [[vim]] or [[elvis]], nvi still closely resembles the look and feel of the original vi. == Overview == '''vi''', '''ex''', and '''view''' are all interfaces to the same program, '''nvi'''. It is possible to launch '''nvi''' in '''ex''' mode using the -e option and to launch '''nvi''' in '''view''' mode using the -R option.<ref name="openbsd-manpage" /> '''nvi''' supports all features of '''vi''' except open mode and lisp edit options, and it itself includes a number of additional features listed [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page here].<ref>[https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page nvi home page], nvi, 2024 (Accessed: 2025-09-09)</ref> == References == c5ae1e8a84e10dd82b47b7e3b420a7ea640baa11 4115 4111 2025-09-09T11:05:52Z Satnus 215 Added WiP template, will remove when I feel satisfied with the state of the article. wikitext text/x-wiki {{DISPLAYTITLE:nvi}} {{Work In Progress}} [[Category:Software]] {{SoftwareInfobox | title = '''nvi''' | image = [[File:Nvi.png|thumb]] | caption = Text editor nvi | releasestatus = Maintained | lastrelease = 1.81.6 | languages = [[C]] | developers = Keith Bostic & Sven Verdoolaege | website = [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page Berkeley Vi Editor (nvi) home page.] }} '''nvi''' is a text editor for [[Unix-Like]] operating systems. nvi was originally created as a replacement for the [[vi]] editor and first appeared in 4.4BSD.<ref name="openbsd-manpage">[https://man.openbsd.org/vi.1 Man page for nvi], nvi, April 24, 2024 (Accessed: 2025-09-09)</ref> Unlike other modern implementations of the vi editor such as [[vim]] or [[elvis]], nvi still closely resembles the look and feel of the original vi. == Overview == '''vi''', '''ex''', and '''view''' are all interfaces to the same program, '''nvi'''. It is possible to launch '''nvi''' in '''ex''' mode using the -e option and to launch '''nvi''' in '''view''' mode using the -R option.<ref name="openbsd-manpage" /> '''nvi''' supports all features of '''vi''' except open mode and lisp edit options, and it itself includes a number of additional features listed [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page here].<ref>[https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page nvi home page], nvi, 2024 (Accessed: 2025-09-09)</ref> == References == 3d706e649400f1ec57e34f1f527d7af23563b1dc 4119 4115 2025-09-09T20:25:13Z Imnotgoodatnames 121 unbolded most bolded words, there's no point to bolding every single instance of a term and it just makes the whole page look weird wikitext text/x-wiki {{DISPLAYTITLE:nvi}} {{Work In Progress}} [[Category:Software]] {{SoftwareInfobox | title = '''nvi''' | image = [[File:Nvi.png|thumb]] | caption = Text editor nvi | releasestatus = Maintained | lastrelease = 1.81.6 | languages = [[C]] | developers = Keith Bostic & Sven Verdoolaege | website = [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page Berkeley Vi Editor (nvi) home page.] }} '''nvi''' is a text editor for [[Unix-Like]] operating systems. nvi was originally created as a replacement for the [[vi]] editor and first appeared in 4.4BSD.<ref name="openbsd-manpage">[https://man.openbsd.org/vi.1 Man page for nvi], nvi, April 24, 2024 (Accessed: 2025-09-09)</ref> Unlike other modern implementations of the vi editor such as [[vim]] or [[elvis]], nvi still closely resembles the look and feel of the original vi. == Overview == '''vi''', [[Ex|'''ex''']], and '''view''' are all interfaces to the same program, nvi. It is possible to launch nvi in ex mode using the -e option and to launch nvi in view mode using the -R option.<ref name="openbsd-manpage" /> nvi supports all features of vi except open mode and lisp edit options, and it itself includes a number of additional features listed [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page here].<ref>[https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page nvi home page], nvi, 2024 (Accessed: 2025-09-09)</ref> == References == dc88bc50ddecdce9e0860f62baace5b43c809bd1 4150 4119 2025-09-13T19:11:10Z Satnus 215 Removed the link to the ex page. It created confusion in the context where it appeared. wikitext text/x-wiki {{DISPLAYTITLE:nvi}} {{Work In Progress}} [[Category:Software]] {{SoftwareInfobox | title = '''nvi''' | image = [[File:Nvi.png|thumb]] | caption = Text editor nvi | releasestatus = Maintained | lastrelease = 1.81.6 | languages = [[C]] | developers = Keith Bostic & Sven Verdoolaege | website = [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page Berkeley Vi Editor (nvi) home page.] }} '''nvi''' is a text editor for [[Unix-Like]] operating systems. nvi was originally created as a replacement for the [[vi]] editor and first appeared in 4.4BSD.<ref name="openbsd-manpage">[https://man.openbsd.org/vi.1 Man page for nvi], nvi, April 24, 2024 (Accessed: 2025-09-09)</ref> Unlike other modern implementations of the vi editor such as [[vim]] or [[elvis]], nvi still closely resembles the look and feel of the original vi. == Overview == '''vi''', '''ex''', and '''view''' are all interfaces to the same program, nvi. It is possible to launch nvi in ex mode using the -e option and to launch nvi in view mode using the -R option.<ref name="openbsd-manpage" /> nvi supports all features of vi except open mode and lisp edit options, and it itself includes a number of additional features listed [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page here].<ref>[https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page nvi home page], nvi, 2024 (Accessed: 2025-09-09)</ref> == References == 64fd91e450c978cc466fb273f2d9a704ded798e4 0 622 4112 4076 2025-09-09T09:20:33Z Hog 161 corrected alphabetical list wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|Budgie File:LinuxMint22-Wilma-English.png|link=Cinnamon|Cinnamon File:Enlightenment-screenshot-2021.png|link=Enlightenment|Enlightenment File:GNOME 43.png|GNOME File:Lxqt-screenshot-about.png|link=LXQt|LXQt File:MATEDesktop.png|link=MATE|MATE File:KDE Plasma 5.26 screenshot.png|link=Plasma|KDE Plasma File:Trinity R.14.1.3 screenshot.png|link=Trinity_Desktop_Environment|Trinity File:XFCE-4.18-Desktop.png|link=XFCE|XFCE File:LXDE-Qt preview.png|LXDE </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} 947f23af75412b1a30e62900c1063904fc9b662b 3000 914 4113 3999 2025-09-09T09:28:33Z Hog 161 started clean up-will finish later wikitext text/x-wiki {{Guide Warning}} {{cleanup}} {{Needs Citations}} = Checking the Boot Mode = [[File:CheckUEFI-1.png|right|frameless]] [[File:CheckUEFI-2.png|right|frameless]] There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> → Your system is using UEFI mode. #* If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' = Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|center|464x464px]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|center]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' → This is a GPT disk. #* If it says '''Master Boot Record''' → This is an MBR disk. The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data''') or use a separate physical disk. '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png]] ---- = Preparing a Partition on the Disk for Arch Linux = Before leaving the Disk Management tool, we need free space to install Arch on. * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == How to shrink the Windows partition: == # From within Disk Management, right-click the <code>C:\</code> partition. Choose from the menu: <code>Shrink Volume</code>[[File:ShrinkPartition-1.png|center|536x536px]] # In the new window, enter the amount of space you want to shrink (in '''Megabytes'''), then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png|center]] # Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: [[File:FinalPartitionLayout-Shrinked.png|center|706x706px]]<br>Or like this if you deleted another non-Windows partition:[[File:FinalPartitionLayout-Replaced.png|center|488x488px]] ---- = Downloading the Arch Linux ISO = You need to [https://archlinux.org/download/ download] the latest ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment.[[File:ArchDownload.png|left|501x501px]] ---- = Preparing the USB Drive to Boot the Live Environment = We need a USB flash drive to install the Arch live environment, this tutorial use the [[Ventoy]] tool because it is the easiest and most flexible. == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == Steps to download Ventoy: == # Download Ventoy from the official website or directly from SourceForge: #* [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] #* [https://www.ventoy.net/en/index.html Official Ventoy Website] [[File:VentoyDownload.png|left|555x555px]] [[File:VentoyDownload-2.png|center]] # After downloading, you will get a compressed <code>.zip</code> file. Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png|center]] == 🧪 How to install Ventoy on the USB drive == After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. Make sure the program recognized the drive and shows its name in the Device field. [[File:VentoyInstall-2.png|center]] == ⚙️ Customizing Ventoy settings before installation == # Disable Secure Boot support<br>Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it.[[File:VentoyInstall-3.png|center]] # Specifying the disk partition type:<br>From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT'''<br>Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png|center]] # Customizing partition configuration: #*From the '''Options''' menu → Select '''Partition Configuration'''[[File:VentoyInstall-5.png|center]] #*And in the first option within the new window:<br>'''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK'''[[File:VentoyInstall-6.png|center]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == Press '''Install''', then agree to the warnings, and wait for the process to complete. [[File:VentoyInstall-7.png|center]] Upon successful installation, you will see a confirmation message. Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. [[File:VentoyInstall-8.png|center]] ---- '''Your USB flash drive is now ready to boot into the Arch live environment 🎉.''' ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. == ✅ The easiest way to boot without entering the BIOS == This method doesn't even require entering the BIOS/Firmware settings: # Restart the system, but '''hold down the Shift key''' while clicking Restart. # If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. == 🧭 In Recovery mode == You will see a list of options, select <code>Use a device</code>, then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). [[File:BootArch.png|center]] == ❗ If the 'Use a device' option is not available == This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == After booting from the USB, you will see the Ventoy menu. Select the Arch Linux ISO file from it, then press Enter twice. ---- == 🎯 Starting the Live Environment == After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. [[File:ArchBoot.png|center]] ---- == 💬 Live Environment Font == If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: setfont ter-132n The font will change from this: [[File:ArchFontBefore.png|center]] To this: [[File:ArchFontAfter.png|center]] == 📝 Notes on available fonts: == The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. Here are some good options: * <code>setfont ter-132n</code><br>Large and clear font, excellent for small screens. * <code>setfont ter-128n</code><br>Similar but slightly smaller than <code>132n</code>. * <code>setfont ter-v32b</code><br>A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. * <code>setfont lat9w-16</code>The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. To check the connection, try the following command: ping google.com You can replace <code>google.com</code> with any other website. If you start seeing messages like: 64 bytes from ... icmp_seq=2 time=23.3 ms ✅ The internet is working successfully! If you see a message like: ping: google.com: Temporary failure in name resolution ❌ It means the internet connection is not active. === ❗ Note: === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: pacman -Sy This command synchronizes the package databases. If you see the message: :: Synchronizing package databases... ✅ This means your internet is working correctly. == 🛜 Wi-Fi users (mostly laptop users) == [[File:Iwctl-1.png|right|frameless]] In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. To start the tool: iwctl Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. # Find the name of your Wi-Fi device:<pre>device list</pre>The network device name will appear, like <code>wlan0</code>. # Scan for nearby networks:<syntaxhighlight> station wlan0 scan station wlan0 get-networks </syntaxhighlight>(Replace <code>wlan0</code> with your actual device name if different.) # Connect to the network: #* If the network is visible:<syntaxhighlight>station wlan0 connect 'SSID'</syntaxhighlight> #* If the network is hidden:<syntaxhighlight>station wlan0 connect-hidden 'SSID'</syntaxhighlight> :(Replace <code>'SSID'</code> with your network name.) :After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. == ✅ Verifying internet access after connecting to Wi-Fi == You can use: ping google.com or: pacman -Sy If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. ---- = 💽 Disks in Linux = == Disk Naming in Linux == Disk naming in Linux is different from Windows. For example, you might see a path like: /dev/sda2 === Explanation of parts: === ;<code>/dev</code> : This is the folder containing all system devices, like disks, network cards, etc. : <code>dev</code> is short for '''device'''. ;<code>sda</code> :This is the name of the first disk. Linux starts naming disks with letters: :* <code>sda</code>: First disk :* <code>sdb</code>: Second disk :* <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' *:<code>/dev/sdXY</code> *:Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' *:<code>/dev/nvmeXnYpZ</code> *:Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' *:<code>/dev/vdXY</code> *:Example: <code>/dev/vda1</code> → First virtual disk, first partition. == Partitioning the Disk for Arch Linux Installation ⚙️ == You can view all connected disks using the <code>lsblk</code> command, which shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. [[File:Lsblk.png|center]] == Opening the cfdisk tool for disk partitioning 🧱 == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. To run it: cfdisk /dev/sda Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 And the interface will open... ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png|center]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png|center]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: ---- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. == 🎮 Controlling the cfdisk tool: == You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. == 🛠️ To start partitioning the free space: == Use the Down arrow until you reach Free Space. You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. [[File:Cfdisk-2.png|center]] == 🧱 System Partitioning: == To install the Arch system, we need at least two partitions: * A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. * The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === * Boot partition: We allocate a maximum of 1G for it. This is more than enough. * Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition === * In the cfdisk tool, select the Free Space using the arrow keys. * Choose New from the options at the bottom, and press Enter. * A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter.[[File:Cfdisk-3.png|center]] *The first partition, the boot partition, will be created.[[File:Cfdisk-4.png|center]] === 🗂️ Creating the Root partition === After finishing creating the boot partition, we move directly to creating the second partition, the root partition. * Select the remaining Free Space using the arrow keys. * Choose New from the options at the bottom of the screen, then press Enter. * This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|center]] === 💾 Confirming changes and writing partitions to the disk === When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. * After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png|center]] * A warning question will appear:<pre>Are you sure you want to write the partition table to disk?</pre>If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter.[[File:Cfdisk-7.png|center]] * With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png|center]] Now make sure to note the names of the two partitions you created: * The first partition (size 1G) is the bootloader partition. * The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: lsblk It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: * FAT32 for the bootloader partition * EXT4 for the root / partition But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: * It is the only filesystem that UEFI can read without any intermediaries. * It does not contain complex permissions or modern features that hinder UEFI. * It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. === 🧱 Why EXT4 for the root / partition? === The root partition contains the entire operating system, so it needs a modern filesystem that supports: * File permissions: To determine who has the right to read, execute, or modify each file. * Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). * Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. * Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. To format the bootloader partition, we write the following command: mkfs.fat -F32 /dev/sda5 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === * <code>mkfs</code> = Make File System = Create a filesystem. * <code>fat</code> is the type of system. * <code>-F32</code> means we use FAT32 (not FAT16 or others). * <code>/dev/sda5</code> is the partition we created for boot (1GB). ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. [[File:Mkfs-1.png|center]] As for formatting the root partition, we use the following command: mkfs.ext4 /dev/sda6 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|center]] Now that we've finished formatting, we're ready to move on to the mounting step! ---- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: mount /dev/sda6 /mnt 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|center]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside <code>/mnt</code>, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: mkdir -p /mnt/boot/efi 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: mount /dev/sda5 /mnt/boot/efi 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. <blockquote>✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT.</blockquote> If everything is good, we start moving to the system installation step! ---- == 🏗️ Installing the System == To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? : Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. ;🧰 pacman :The primary package manager in Arch Linux. :Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). ;📦 pacstrap :A special tool used during installation from the live environment. :Installs packages onto a specified path — usually /mnt — instead of the live system. :Its function is to prepare the root partition with basic system packages, such as: :*The Linux kernel :*The package manager <code>pacman</code> itself! :* Networking tools :* System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition <code>/mnt</code>: pacstrap /mnt base linux linux-firmware But why these specific packages?! And what does each one do? === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: * Basic command-line tools like sh, ls, cp, mv, mkdir... * Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) * Important scripts that aid in booting === 2️⃣ linux === This is the system kernel itself. * Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks ---- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: <blockquote>"What partitions do you have? Where do you want to mount each partition? And with which filesystem?"</blockquote> You can imagine it as a simple table containing: * Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: genfstab -U /mnt >> /mnt/etc/fstab ✅ Explanation of command components: * <code>genfstab</code>: Short for "Generate File System Table" * <code>-U</code>: Makes it use UUID identifiers instead of disk names * <code>/mnt</code>: Is the root of the new system we installed * <code>>></code>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition 🔒 So using UUID is the safe and reliable solution. ---- Now we can move to the next step, which is entering the new system's root We can use the command: arch-chroot /mnt The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. [[File:Arch-chroot.png|center]] After entering the system using <code>arch-chroot</code>, we begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. 📦 We use the following command pacman -Sy sudo nano grub efibootmgr os-prober networkmanager [[File:Pacman.png|center]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === <blockquote>A tool that grants root privileges to a regular user when needed, instead of always logging in as root.</blockquote> * Very important for system administration after creating your own user. === ✅ <code>nano</code> === <blockquote>A simple and easy text editor, ideal for any beginner.</blockquote> * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === <blockquote>The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu).</blockquote> * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === <blockquote>A tool that interacts with boot settings in '''UEFI''' systems.</blockquote> * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === <blockquote>A tool that searches for other operating systems installed on the device (like Windows).</blockquote> * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file === ==== 1️⃣ Modify the GRUB_TIMEOUT option ==== This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png|center]] ==== 2️⃣ Enable the os-prober tool ==== Scroll down to the end of the file, and you will see a line like this: #GRUB_DISABLE_OS_PROBER=false All you need to do is remove the # sign to activate the feature, so it becomes: GRUB_DISABLE_OS_PROBER=false [[File:Grub-conf_1.png|center]] 🎯 This allows GRUB to detect Windows and add it to the menu automatically. After editing, save and exit nano: Ctrl + X → then y → then Enter ---- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: /dev/sda1 We mount it with this command: mount /dev/sda1 /boot/efi ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|center]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png|center]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png|center]] ---- == 🧠 Generating the GRUB configuration file == Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. We use the following command: grub-mkconfig -o /boot/grub/grub.cfg Explanation of parts: * <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. * <code>-o</code>: means "Output", i.e., where to save the output file. * <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|center]] ---- = 👤 Creating a new user = After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: useradd -m -G wheel -s /bin/bash username Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == * <code>useradd</code>: The command responsible for creating the user. * <code>-m</code>: Creates the home directory automatically in /home/username. * <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. * <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png|center]] ---- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: passwd Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: password updated successfully [[File:Passwd.png|center]] Then you're good. Setting the password for the new user: passwd username Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png|center]] ---- = 🛡️ Enabling sudo privileges for the wheel group = Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: EDITOR=nano visudo [[File:Visudo-1.png|center]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png|center]] Scroll down until you reach this line: # %wheel ALL=(ALL:ALL) ALL [[File:Visudobefore.png|center]] What do you do? Remove the # sign from the beginning, so it becomes like this: %wheel ALL=(ALL:ALL) ALL [[File:Visudoafter.png]] ✨ Now the user in the wheel group can use sudo. To save changes and exit nano, press {{Keypress|Ctrl|X}}{{Keypress|Y|Enter|chain=}} ---- = 🖥️ Setting the device name (Hostname) = The hostname is what appears to you in the command line and is very useful for networks. To set the name: echo 'ArchBox' > /etc/hostname [[File:Hostname.png|center]] Replace ''ArchBox'' with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: nano /etc/hosts [[File:Etchosts_before.png|center]] After it opens, add this line: 127.0.1.1 ArchBox.localdomain ArchBox Replace ''ArchBox'' with the name you wrote in the previous step. [[File:Etchosts_after.png|center]] ---- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: systemctl enable NetworkManager Just make sure you wrote the name correctly, with the exact case. ---- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇 = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: pacman -S gnome gnome-extra gdm And then enable the login manager: systemctl enable gdm 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. = 💎 Option Two: KDE Plasma + SDDM = If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. Execute the following command: pacman -S plasma kde-applications sddm Then enable the login manager: systemctl enable sddm 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. ---- = 🧼 Finishing the installation and rebooting = Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. First, exit chroot: exit You will return to the live environment (USB). Now unmount the partitions we mounted: umount -R /mnt And finally... the awaited moment 🎉: reboot After rebooting, if everything is fine, you will see the GRUB menu with: Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png|center]] Congratulations on your First Dual Booting experience, thank you for reading. 3f3d249f9da04d84b0ecd7b4fecc6836b4ae3967 4116 4113 2025-09-09T13:13:56Z Fluffinity 271 Removed hardcoded resolutions for the images used in the parts for disk partitioning and Ventoy wikitext text/x-wiki {{Guide Warning}} {{cleanup}} {{Needs Citations}} = Checking the Boot Mode = [[File:CheckUEFI-1.png|right|frameless]] [[File:CheckUEFI-2.png|right|frameless]] There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> → Your system is using UEFI mode. #* If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' = Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|center]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|center]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' → This is a GPT disk. #* If it says '''Master Boot Record''' → This is an MBR disk. The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data''') or use a separate physical disk. '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png]] ---- = Preparing a Partition on the Disk for Arch Linux = Before leaving the Disk Management tool, we need free space to install Arch on. * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == How to shrink the Windows partition: == # From within Disk Management, right-click the <code>C:\</code> partition. Choose from the menu: <code>Shrink Volume</code>[[File:ShrinkPartition-1.png|center]] # In the new window, enter the amount of space you want to shrink (in '''Megabytes'''), then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png|center]] # Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: [[File:FinalPartitionLayout-Shrinked.png|center]]<br>Or like this if you deleted another non-Windows partition:[[File:FinalPartitionLayout-Replaced.png|center]] ---- = Downloading the Arch Linux ISO = You need to [https://archlinux.org/download/ download] the latest ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment.[[File:ArchDownload.png|left]] ---- = Preparing the USB Drive to Boot the Live Environment = We need a USB flash drive to install the Arch live environment, this tutorial use the [[Ventoy]] tool because it is the easiest and most flexible. == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == Steps to download Ventoy: == # Download Ventoy from the official website or directly from SourceForge: #* [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] #* [https://www.ventoy.net/en/index.html Official Ventoy Website] [[File:VentoyDownload.png|left]] [[File:VentoyDownload-2.png|center]] # After downloading, you will get a compressed <code>.zip</code> file. Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png|center]] == 🧪 How to install Ventoy on the USB drive == After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. Make sure the program recognized the drive and shows its name in the Device field. [[File:VentoyInstall-2.png|center]] == ⚙️ Customizing Ventoy settings before installation == # Disable Secure Boot support<br>Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it.[[File:VentoyInstall-3.png|center]] # Specifying the disk partition type:<br>From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT'''<br>Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png|center]] # Customizing partition configuration: #*From the '''Options''' menu → Select '''Partition Configuration'''[[File:VentoyInstall-5.png|center]] #*And in the first option within the new window:<br>'''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK'''[[File:VentoyInstall-6.png|center]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == Press '''Install''', then agree to the warnings, and wait for the process to complete. [[File:VentoyInstall-7.png|center]] Upon successful installation, you will see a confirmation message. Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. [[File:VentoyInstall-8.png|center]] ---- '''Your USB flash drive is now ready to boot into the Arch live environment 🎉.''' ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. == ✅ The easiest way to boot without entering the BIOS == This method doesn't even require entering the BIOS/Firmware settings: # Restart the system, but '''hold down the Shift key''' while clicking Restart. # If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. == 🧭 In Recovery mode == You will see a list of options, select <code>Use a device</code>, then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). [[File:BootArch.png|center]] == ❗ If the 'Use a device' option is not available == This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == After booting from the USB, you will see the Ventoy menu. Select the Arch Linux ISO file from it, then press Enter twice. ---- == 🎯 Starting the Live Environment == After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. [[File:ArchBoot.png|center]] ---- == 💬 Live Environment Font == If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: setfont ter-132n The font will change from this: [[File:ArchFontBefore.png|center]] To this: [[File:ArchFontAfter.png|center]] == 📝 Notes on available fonts: == The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. Here are some good options: * <code>setfont ter-132n</code><br>Large and clear font, excellent for small screens. * <code>setfont ter-128n</code><br>Similar but slightly smaller than <code>132n</code>. * <code>setfont ter-v32b</code><br>A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. * <code>setfont lat9w-16</code>The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. To check the connection, try the following command: ping google.com You can replace <code>google.com</code> with any other website. If you start seeing messages like: 64 bytes from ... icmp_seq=2 time=23.3 ms ✅ The internet is working successfully! If you see a message like: ping: google.com: Temporary failure in name resolution ❌ It means the internet connection is not active. === ❗ Note: === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: pacman -Sy This command synchronizes the package databases. If you see the message: :: Synchronizing package databases... ✅ This means your internet is working correctly. == 🛜 Wi-Fi users (mostly laptop users) == [[File:Iwctl-1.png|right|frameless]] In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. To start the tool: iwctl Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. # Find the name of your Wi-Fi device:<pre>device list</pre>The network device name will appear, like <code>wlan0</code>. # Scan for nearby networks:<syntaxhighlight> station wlan0 scan station wlan0 get-networks </syntaxhighlight>(Replace <code>wlan0</code> with your actual device name if different.) # Connect to the network: #* If the network is visible:<syntaxhighlight>station wlan0 connect 'SSID'</syntaxhighlight> #* If the network is hidden:<syntaxhighlight>station wlan0 connect-hidden 'SSID'</syntaxhighlight> :(Replace <code>'SSID'</code> with your network name.) :After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. == ✅ Verifying internet access after connecting to Wi-Fi == You can use: ping google.com or: pacman -Sy If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. ---- = 💽 Disks in Linux = == Disk Naming in Linux == Disk naming in Linux is different from Windows. For example, you might see a path like: /dev/sda2 === Explanation of parts: === ;<code>/dev</code> : This is the folder containing all system devices, like disks, network cards, etc. : <code>dev</code> is short for '''device'''. ;<code>sda</code> :This is the name of the first disk. Linux starts naming disks with letters: :* <code>sda</code>: First disk :* <code>sdb</code>: Second disk :* <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' *:<code>/dev/sdXY</code> *:Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' *:<code>/dev/nvmeXnYpZ</code> *:Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' *:<code>/dev/vdXY</code> *:Example: <code>/dev/vda1</code> → First virtual disk, first partition. == Partitioning the Disk for Arch Linux Installation ⚙️ == You can view all connected disks using the <code>lsblk</code> command, which shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. [[File:Lsblk.png|center]] == Opening the cfdisk tool for disk partitioning 🧱 == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. To run it: cfdisk /dev/sda Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 And the interface will open... ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png|center]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png|center]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: ---- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. == 🎮 Controlling the cfdisk tool: == You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. == 🛠️ To start partitioning the free space: == Use the Down arrow until you reach Free Space. You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. [[File:Cfdisk-2.png|center]] == 🧱 System Partitioning: == To install the Arch system, we need at least two partitions: * A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. * The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === * Boot partition: We allocate a maximum of 1G for it. This is more than enough. * Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition === * In the cfdisk tool, select the Free Space using the arrow keys. * Choose New from the options at the bottom, and press Enter. * A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter.[[File:Cfdisk-3.png|center]] *The first partition, the boot partition, will be created.[[File:Cfdisk-4.png|center]] === 🗂️ Creating the Root partition === After finishing creating the boot partition, we move directly to creating the second partition, the root partition. * Select the remaining Free Space using the arrow keys. * Choose New from the options at the bottom of the screen, then press Enter. * This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|center]] === 💾 Confirming changes and writing partitions to the disk === When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. * After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png|center]] * A warning question will appear:<pre>Are you sure you want to write the partition table to disk?</pre>If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter.[[File:Cfdisk-7.png|center]] * With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png|center]] Now make sure to note the names of the two partitions you created: * The first partition (size 1G) is the bootloader partition. * The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: lsblk It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: * FAT32 for the bootloader partition * EXT4 for the root / partition But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: * It is the only filesystem that UEFI can read without any intermediaries. * It does not contain complex permissions or modern features that hinder UEFI. * It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. === 🧱 Why EXT4 for the root / partition? === The root partition contains the entire operating system, so it needs a modern filesystem that supports: * File permissions: To determine who has the right to read, execute, or modify each file. * Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). * Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. * Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. To format the bootloader partition, we write the following command: mkfs.fat -F32 /dev/sda5 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === * <code>mkfs</code> = Make File System = Create a filesystem. * <code>fat</code> is the type of system. * <code>-F32</code> means we use FAT32 (not FAT16 or others). * <code>/dev/sda5</code> is the partition we created for boot (1GB). ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. [[File:Mkfs-1.png|center]] As for formatting the root partition, we use the following command: mkfs.ext4 /dev/sda6 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|center]] Now that we've finished formatting, we're ready to move on to the mounting step! ---- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: mount /dev/sda6 /mnt 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|center]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside <code>/mnt</code>, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: mkdir -p /mnt/boot/efi 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: mount /dev/sda5 /mnt/boot/efi 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. <blockquote>✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT.</blockquote> If everything is good, we start moving to the system installation step! ---- == 🏗️ Installing the System == To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? : Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. ;🧰 pacman :The primary package manager in Arch Linux. :Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). ;📦 pacstrap :A special tool used during installation from the live environment. :Installs packages onto a specified path — usually /mnt — instead of the live system. :Its function is to prepare the root partition with basic system packages, such as: :*The Linux kernel :*The package manager <code>pacman</code> itself! :* Networking tools :* System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition <code>/mnt</code>: pacstrap /mnt base linux linux-firmware But why these specific packages?! And what does each one do? === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: * Basic command-line tools like sh, ls, cp, mv, mkdir... * Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) * Important scripts that aid in booting === 2️⃣ linux === This is the system kernel itself. * Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks ---- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: <blockquote>"What partitions do you have? Where do you want to mount each partition? And with which filesystem?"</blockquote> You can imagine it as a simple table containing: * Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: genfstab -U /mnt >> /mnt/etc/fstab ✅ Explanation of command components: * <code>genfstab</code>: Short for "Generate File System Table" * <code>-U</code>: Makes it use UUID identifiers instead of disk names * <code>/mnt</code>: Is the root of the new system we installed * <code>>></code>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition 🔒 So using UUID is the safe and reliable solution. ---- Now we can move to the next step, which is entering the new system's root We can use the command: arch-chroot /mnt The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. [[File:Arch-chroot.png|center]] After entering the system using <code>arch-chroot</code>, we begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. 📦 We use the following command pacman -Sy sudo nano grub efibootmgr os-prober networkmanager [[File:Pacman.png|center]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === <blockquote>A tool that grants root privileges to a regular user when needed, instead of always logging in as root.</blockquote> * Very important for system administration after creating your own user. === ✅ <code>nano</code> === <blockquote>A simple and easy text editor, ideal for any beginner.</blockquote> * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === <blockquote>The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu).</blockquote> * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === <blockquote>A tool that interacts with boot settings in '''UEFI''' systems.</blockquote> * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === <blockquote>A tool that searches for other operating systems installed on the device (like Windows).</blockquote> * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file === ==== 1️⃣ Modify the GRUB_TIMEOUT option ==== This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png|center]] ==== 2️⃣ Enable the os-prober tool ==== Scroll down to the end of the file, and you will see a line like this: #GRUB_DISABLE_OS_PROBER=false All you need to do is remove the # sign to activate the feature, so it becomes: GRUB_DISABLE_OS_PROBER=false [[File:Grub-conf_1.png|center]] 🎯 This allows GRUB to detect Windows and add it to the menu automatically. After editing, save and exit nano: Ctrl + X → then y → then Enter ---- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: /dev/sda1 We mount it with this command: mount /dev/sda1 /boot/efi ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|center]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png|center]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png|center]] ---- == 🧠 Generating the GRUB configuration file == Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. We use the following command: grub-mkconfig -o /boot/grub/grub.cfg Explanation of parts: * <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. * <code>-o</code>: means "Output", i.e., where to save the output file. * <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|center]] ---- = 👤 Creating a new user = After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: useradd -m -G wheel -s /bin/bash username Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == * <code>useradd</code>: The command responsible for creating the user. * <code>-m</code>: Creates the home directory automatically in /home/username. * <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. * <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png|center]] ---- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: passwd Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: password updated successfully [[File:Passwd.png|center]] Then you're good. Setting the password for the new user: passwd username Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png|center]] ---- = 🛡️ Enabling sudo privileges for the wheel group = Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: EDITOR=nano visudo [[File:Visudo-1.png|center]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png|center]] Scroll down until you reach this line: # %wheel ALL=(ALL:ALL) ALL [[File:Visudobefore.png|center]] What do you do? Remove the # sign from the beginning, so it becomes like this: %wheel ALL=(ALL:ALL) ALL [[File:Visudoafter.png]] ✨ Now the user in the wheel group can use sudo. To save changes and exit nano, press {{Keypress|Ctrl|X}}{{Keypress|Y|Enter|chain=}} ---- = 🖥️ Setting the device name (Hostname) = The hostname is what appears to you in the command line and is very useful for networks. To set the name: echo 'ArchBox' > /etc/hostname [[File:Hostname.png|center]] Replace ''ArchBox'' with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: nano /etc/hosts [[File:Etchosts_before.png|center]] After it opens, add this line: 127.0.1.1 ArchBox.localdomain ArchBox Replace ''ArchBox'' with the name you wrote in the previous step. [[File:Etchosts_after.png|center]] ---- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: systemctl enable NetworkManager Just make sure you wrote the name correctly, with the exact case. ---- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇 = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: pacman -S gnome gnome-extra gdm And then enable the login manager: systemctl enable gdm 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. = 💎 Option Two: KDE Plasma + SDDM = If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. Execute the following command: pacman -S plasma kde-applications sddm Then enable the login manager: systemctl enable sddm 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. ---- = 🧼 Finishing the installation and rebooting = Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. First, exit chroot: exit You will return to the live environment (USB). Now unmount the partitions we mounted: umount -R /mnt And finally... the awaited moment 🎉: reboot After rebooting, if everything is fine, you will see the GRUB menu with: Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png|center]] Congratulations on your First Dual Booting experience, thank you for reading. a0c9733599fe88b853116caaeac5664b652cf1ec 4117 4116 2025-09-09T13:23:16Z Fluffinity 271 Add "center" alignment for CheckGTP2 image so mobile can render it correctly wikitext text/x-wiki {{Guide Warning}} {{cleanup}} {{Needs Citations}} = Checking the Boot Mode = [[File:CheckUEFI-1.png|right|frameless]] [[File:CheckUEFI-2.png|right|frameless]] There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> → Your system is using UEFI mode. #* If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' = Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|center]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|center]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' → This is a GPT disk. #* If it says '''Master Boot Record''' → This is an MBR disk. The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data''') or use a separate physical disk. '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png|center]] ---- = Preparing a Partition on the Disk for Arch Linux = Before leaving the Disk Management tool, we need free space to install Arch on. * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == How to shrink the Windows partition: == # From within Disk Management, right-click the <code>C:\</code> partition. Choose from the menu: <code>Shrink Volume</code>[[File:ShrinkPartition-1.png|center]] # In the new window, enter the amount of space you want to shrink (in '''Megabytes'''), then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png|center]] # Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: [[File:FinalPartitionLayout-Shrinked.png|center]]<br>Or like this if you deleted another non-Windows partition:[[File:FinalPartitionLayout-Replaced.png|center]] ---- = Downloading the Arch Linux ISO = You need to [https://archlinux.org/download/ download] the latest ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment.[[File:ArchDownload.png|left]] ---- = Preparing the USB Drive to Boot the Live Environment = We need a USB flash drive to install the Arch live environment, this tutorial use the [[Ventoy]] tool because it is the easiest and most flexible. == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == Steps to download Ventoy: == # Download Ventoy from the official website or directly from SourceForge: #* [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] #* [https://www.ventoy.net/en/index.html Official Ventoy Website] [[File:VentoyDownload.png|left]] [[File:VentoyDownload-2.png|center]] # After downloading, you will get a compressed <code>.zip</code> file. Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png|center]] == 🧪 How to install Ventoy on the USB drive == After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. Make sure the program recognized the drive and shows its name in the Device field. [[File:VentoyInstall-2.png|center]] == ⚙️ Customizing Ventoy settings before installation == # Disable Secure Boot support<br>Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it.[[File:VentoyInstall-3.png|center]] # Specifying the disk partition type:<br>From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT'''<br>Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png|center]] # Customizing partition configuration: #*From the '''Options''' menu → Select '''Partition Configuration'''[[File:VentoyInstall-5.png|center]] #*And in the first option within the new window:<br>'''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK'''[[File:VentoyInstall-6.png|center]] === ✳️ Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == 🚀 Installing Ventoy == Press '''Install''', then agree to the warnings, and wait for the process to complete. [[File:VentoyInstall-7.png|center]] Upon successful installation, you will see a confirmation message. Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. [[File:VentoyInstall-8.png|center]] ---- '''Your USB flash drive is now ready to boot into the Arch live environment 🎉.''' ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. == ✅ The easiest way to boot without entering the BIOS == This method doesn't even require entering the BIOS/Firmware settings: # Restart the system, but '''hold down the Shift key''' while clicking Restart. # If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. == 🧭 In Recovery mode == You will see a list of options, select <code>Use a device</code>, then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). [[File:BootArch.png|center]] == ❗ If the 'Use a device' option is not available == This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == After booting from the USB, you will see the Ventoy menu. Select the Arch Linux ISO file from it, then press Enter twice. ---- == 🎯 Starting the Live Environment == After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. [[File:ArchBoot.png|center]] ---- == 💬 Live Environment Font == If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: setfont ter-132n The font will change from this: [[File:ArchFontBefore.png|center]] To this: [[File:ArchFontAfter.png|center]] == 📝 Notes on available fonts: == The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. Here are some good options: * <code>setfont ter-132n</code><br>Large and clear font, excellent for small screens. * <code>setfont ter-128n</code><br>Similar but slightly smaller than <code>132n</code>. * <code>setfont ter-v32b</code><br>A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. * <code>setfont lat9w-16</code>The default font in many distributions, suitable but smaller than others. ---- = 📶 Connecting to the Internet = === ~ Ethernet cable users === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. To check the connection, try the following command: ping google.com You can replace <code>google.com</code> with any other website. If you start seeing messages like: 64 bytes from ... icmp_seq=2 time=23.3 ms ✅ The internet is working successfully! If you see a message like: ping: google.com: Temporary failure in name resolution ❌ It means the internet connection is not active. === ❗ Note: === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: pacman -Sy This command synchronizes the package databases. If you see the message: :: Synchronizing package databases... ✅ This means your internet is working correctly. == 🛜 Wi-Fi users (mostly laptop users) == [[File:Iwctl-1.png|right|frameless]] In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. To start the tool: iwctl Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. # Find the name of your Wi-Fi device:<pre>device list</pre>The network device name will appear, like <code>wlan0</code>. # Scan for nearby networks:<syntaxhighlight> station wlan0 scan station wlan0 get-networks </syntaxhighlight>(Replace <code>wlan0</code> with your actual device name if different.) # Connect to the network: #* If the network is visible:<syntaxhighlight>station wlan0 connect 'SSID'</syntaxhighlight> #* If the network is hidden:<syntaxhighlight>station wlan0 connect-hidden 'SSID'</syntaxhighlight> :(Replace <code>'SSID'</code> with your network name.) :After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. == ✅ Verifying internet access after connecting to Wi-Fi == You can use: ping google.com or: pacman -Sy If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. ---- = 💽 Disks in Linux = == Disk Naming in Linux == Disk naming in Linux is different from Windows. For example, you might see a path like: /dev/sda2 === Explanation of parts: === ;<code>/dev</code> : This is the folder containing all system devices, like disks, network cards, etc. : <code>dev</code> is short for '''device'''. ;<code>sda</code> :This is the name of the first disk. Linux starts naming disks with letters: :* <code>sda</code>: First disk :* <code>sdb</code>: Second disk :* <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' *:<code>/dev/sdXY</code> *:Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' *:<code>/dev/nvmeXnYpZ</code> *:Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' *:<code>/dev/vdXY</code> *:Example: <code>/dev/vda1</code> → First virtual disk, first partition. == Partitioning the Disk for Arch Linux Installation ⚙️ == You can view all connected disks using the <code>lsblk</code> command, which shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. [[File:Lsblk.png|center]] == Opening the cfdisk tool for disk partitioning 🧱 == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. To run it: cfdisk /dev/sda Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. ْ A quick sidebar 🙂 And the interface will open... ** Since we're talking about interfaces, let me give you a brief overview of interface types in Linux <: = 🖥️ CLI – Command Line Interface = A text-based interface that relies on manually typing commands. No menus or buttons, just type and execute. Example: <code>iwctl</code> [[File:Iwctl-1.png|center]] = 📋 TUI – Text User Interface = An interface with navigable menus; you can use arrow keys and Enter without typing many commands. Examples: <code>archinstall</code>, <code>nmtui</code> [[File:Nmtui.png|center]] === 🖼️ GUI – Graphical User Interface === An interface that relies on the mouse and windows, like GNOME, KDE desktop environments, etc. No examples needed, everyone knows them <: ---- == Now back to disk partitioning 🧱 == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == 🧩 Partitioning the Free Space == As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. == 🎮 Controlling the cfdisk tool: == You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. == 🛠️ To start partitioning the free space: == Use the Down arrow until you reach Free Space. You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. [[File:Cfdisk-2.png|center]] == 🧱 System Partitioning: == To install the Arch system, we need at least two partitions: * A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. * The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === 💾 What size for each partition? === * Boot partition: We allocate a maximum of 1G for it. This is more than enough. * Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === 🛠️ Creating the Boot partition === * In the cfdisk tool, select the Free Space using the arrow keys. * Choose New from the options at the bottom, and press Enter. * A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter.[[File:Cfdisk-3.png|center]] *The first partition, the boot partition, will be created.[[File:Cfdisk-4.png|center]] === 🗂️ Creating the Root partition === After finishing creating the boot partition, we move directly to creating the second partition, the root partition. * Select the remaining Free Space using the arrow keys. * Choose New from the options at the bottom of the screen, then press Enter. * This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|center]] === 💾 Confirming changes and writing partitions to the disk === When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. * After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png|center]] * A warning question will appear:<pre>Are you sure you want to write the partition table to disk?</pre>If you are sure of the changes, type yes in lowercase letters (⚠️ Pay attention to case sensitivity), then press Enter.[[File:Cfdisk-7.png|center]] * With this, the changes have been physically written to the disk and the partitions have been successfully created. === 🧾 Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved 🎉 [[File:Cfdiskfinal.png|center]] Now make sure to note the names of the two partitions you created: * The first partition (size 1G) is the bootloader partition. * The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: lsblk It will show you all disks and partitions, and you can identify the two partitions based on their size. == 🧼 Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: * FAT32 for the bootloader partition * EXT4 for the root / partition But why choose these two systems specifically? 🤔 === 🧩 Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: * It is the only filesystem that UEFI can read without any intermediaries. * It does not contain complex permissions or modern features that hinder UEFI. * It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. === 🧱 Why EXT4 for the root / partition? === The root partition contains the entire operating system, so it needs a modern filesystem that supports: * File permissions: To determine who has the right to read, execute, or modify each file. * Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). * Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. * Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. To format the bootloader partition, we write the following command: mkfs.fat -F32 /dev/sda5 📌 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === * <code>mkfs</code> = Make File System = Create a filesystem. * <code>fat</code> is the type of system. * <code>-F32</code> means we use FAT32 (not FAT16 or others). * <code>/dev/sda5</code> is the partition we created for boot (1GB). ⚠️ Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. [[File:Mkfs-1.png|center]] As for formatting the root partition, we use the following command: mkfs.ext4 /dev/sda6 📌 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|center]] Now that we've finished formatting, we're ready to move on to the mounting step! ---- == 🧱 Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === 🪓 First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: mount /dev/sda6 /mnt 📌 Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|center]] === 🪪 Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside <code>/mnt</code>, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: mkdir -p /mnt/boot/efi 📌 The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: mount /dev/sda5 /mnt/boot/efi 📌 And as usual, replace /dev/sda5 with the actual name of your boot partition. <blockquote>✅ Verifying the mount Type lsblk and make sure /mnt and /mnt/boot/efi appear under MOUNTPOINT.</blockquote> If everything is good, we start moving to the system installation step! ---- == 🏗️ Installing the System == To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. 🤔 But... isn't <code>pacman</code> the package manager in Arch? : Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. ;🧰 pacman :The primary package manager in Arch Linux. :Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). ;📦 pacstrap :A special tool used during installation from the live environment. :Installs packages onto a specified path — usually /mnt — instead of the live system. :Its function is to prepare the root partition with basic system packages, such as: :*The Linux kernel :*The package manager <code>pacman</code> itself! :* Networking tools :* System files == 📥 Installing the base packages == We use the following command to install the basic system inside the new root partition <code>/mnt</code>: pacstrap /mnt base linux linux-firmware But why these specific packages?! And what does each one do? === 1️⃣base === The base package containing everything the system needs to function. 🔍 Includes: * Basic command-line tools like sh, ls, cp, mv, mkdir... * Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) * Important scripts that aid in booting === 2️⃣ linux === This is the system kernel itself. * Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === 3️⃣ linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks ---- = 📄 Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == 💬 What is fstab? == It is a configuration file that tells the system: <blockquote>"What partitions do you have? Where do you want to mount each partition? And with which filesystem?"</blockquote> You can imagine it as a simple table containing: * Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == 🔧 Generating fstab automatically == To generate the file easily, we use this command: genfstab -U /mnt >> /mnt/etc/fstab ✅ Explanation of command components: * <code>genfstab</code>: Short for "Generate File System Table" * <code>-U</code>: Makes it use UUID identifiers instead of disk names * <code>/mnt</code>: Is the root of the new system we installed * <code>>></code>: Means append the output to the file <code>/mnt/etc/fstab</code> === ❓Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition 🔒 So using UUID is the safe and reliable solution. ---- Now we can move to the next step, which is entering the new system's root We can use the command: arch-chroot /mnt The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. [[File:Arch-chroot.png|center]] After entering the system using <code>arch-chroot</code>, we begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. 📦 We use the following command pacman -Sy sudo nano grub efibootmgr os-prober networkmanager [[File:Pacman.png|center]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === <blockquote>A tool that grants root privileges to a regular user when needed, instead of always logging in as root.</blockquote> * Very important for system administration after creating your own user. === ✅ <code>nano</code> === <blockquote>A simple and easy text editor, ideal for any beginner.</blockquote> * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === <blockquote>The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu).</blockquote> * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === <blockquote>A tool that interacts with boot settings in '''UEFI''' systems.</blockquote> * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === <blockquote>A tool that searches for other operating systems installed on the device (like Windows).</blockquote> * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file === ==== 1️⃣ Modify the GRUB_TIMEOUT option ==== This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png|center]] ==== 2️⃣ Enable the os-prober tool ==== Scroll down to the end of the file, and you will see a line like this: #GRUB_DISABLE_OS_PROBER=false All you need to do is remove the # sign to activate the feature, so it becomes: GRUB_DISABLE_OS_PROBER=false [[File:Grub-conf_1.png|center]] 🎯 This allows GRUB to detect Windows and add it to the menu automatically. After editing, save and exit nano: Ctrl + X → then y → then Enter ---- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: /dev/sda1 We mount it with this command: mount /dev/sda1 /boot/efi ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|center]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png|center]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png|center]] ---- == 🧠 Generating the GRUB configuration file == Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. We use the following command: grub-mkconfig -o /boot/grub/grub.cfg Explanation of parts: * <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. * <code>-o</code>: means "Output", i.e., where to save the output file. * <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|center]] ---- = 👤 Creating a new user = After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: useradd -m -G wheel -s /bin/bash username Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == * <code>useradd</code>: The command responsible for creating the user. * <code>-m</code>: Creates the home directory automatically in /home/username. * <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. * <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png|center]] ---- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: passwd Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: password updated successfully [[File:Passwd.png|center]] Then you're good. Setting the password for the new user: passwd username Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png|center]] ---- = 🛡️ Enabling sudo privileges for the wheel group = Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: EDITOR=nano visudo [[File:Visudo-1.png|center]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png|center]] Scroll down until you reach this line: # %wheel ALL=(ALL:ALL) ALL [[File:Visudobefore.png|center]] What do you do? Remove the # sign from the beginning, so it becomes like this: %wheel ALL=(ALL:ALL) ALL [[File:Visudoafter.png]] ✨ Now the user in the wheel group can use sudo. To save changes and exit nano, press {{Keypress|Ctrl|X}}{{Keypress|Y|Enter|chain=}} ---- = 🖥️ Setting the device name (Hostname) = The hostname is what appears to you in the command line and is very useful for networks. To set the name: echo 'ArchBox' > /etc/hostname [[File:Hostname.png|center]] Replace ''ArchBox'' with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: nano /etc/hosts [[File:Etchosts_before.png|center]] After it opens, add this line: 127.0.1.1 ArchBox.localdomain ArchBox Replace ''ArchBox'' with the name you wrote in the previous step. [[File:Etchosts_after.png|center]] ---- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: systemctl enable NetworkManager Just make sure you wrote the name correctly, with the exact case. ---- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇 = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: pacman -S gnome gnome-extra gdm And then enable the login manager: systemctl enable gdm 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. = 💎 Option Two: KDE Plasma + SDDM = If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. Execute the following command: pacman -S plasma kde-applications sddm Then enable the login manager: systemctl enable sddm 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. ---- = 🧼 Finishing the installation and rebooting = Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. First, exit chroot: exit You will return to the live environment (USB). Now unmount the partitions we mounted: umount -R /mnt And finally... the awaited moment 🎉: reboot After rebooting, if everything is fine, you will see the GRUB menu with: Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png|center]] Congratulations on your First Dual Booting experience, thank you for reading. d26b3179d679a22f571f8ef9152fcf19f8458e2b 4128 4117 2025-09-10T10:59:50Z Hog 161 further cleaning wikitext text/x-wiki {{Guide Warning}} {{cleanup}} {{Needs Citations}} = Checking the Boot Mode = [[File:CheckUEFI-1.png|right|frameless]] [[File:CheckUEFI-2.png|right|frameless]] There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> → Your system is using UEFI mode. #* If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' = Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|center]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|center]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' → This is a GPT disk. #* If it says '''Master Boot Record''' → This is an MBR disk. The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data''') or use a separate physical disk. '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png|center]] ---- = Preparing a Partition on the Disk for Arch Linux = Before leaving the Disk Management tool, we need free space to install Arch on. * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == How to shrink the Windows partition: == # From within Disk Management, right-click the <code>C:\</code> partition. Choose from the menu: <code>Shrink Volume</code>[[File:ShrinkPartition-1.png|center]] # In the new window, enter the amount of space you want to shrink (in '''Megabytes'''), then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png|center]] # Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: [[File:FinalPartitionLayout-Shrinked.png|center]]<br>Or like this if you deleted another non-Windows partition:[[File:FinalPartitionLayout-Replaced.png|center]] ---- = Downloading the Arch Linux ISO = You need to [https://archlinux.org/download/ download] the latest ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment.[[File:ArchDownload.png|left]] ---- = Preparing the USB Drive to Boot the Live Environment = We need a USB flash drive to install the Arch live environment, this tutorial use the [[Ventoy]] tool because it is the easiest and most flexible. == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == Steps to download Ventoy: == # Download Ventoy from the official website or directly from SourceForge: #* [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] #* [https://www.ventoy.net/en/index.html Official Ventoy Website] [[File:VentoyDownload.png|left]] [[File:VentoyDownload-2.png|center]] # After downloading, you will get a compressed <code>.zip</code> file. Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png|center]] == How to install Ventoy on the USB drive == After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. Make sure the program recognized the drive and shows its name in the Device field. [[File:VentoyInstall-2.png|center]] == ⚙️ Customizing Ventoy settings before installation == # Disable Secure Boot support<br>Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it.[[File:VentoyInstall-3.png|center]] # Specifying the disk partition type:<br>From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT'''<br>Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png|center]] # Customizing partition configuration: #*From the '''Options''' menu → Select '''Partition Configuration'''[[File:VentoyInstall-5.png|center]] #*And in the first option within the new window:<br>'''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK'''[[File:VentoyInstall-6.png|center]] === Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == Installing Ventoy == Press '''Install''', then agree to the warnings, and wait for the process to complete. [[File:VentoyInstall-7.png|center]] Upon successful installation, you will see a confirmation message. Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. [[File:VentoyInstall-8.png|center]] ---- '''Your USB flash drive is now ready to boot into the Arch live environment 🎉.''' ---- = 🚀 Booting into the Live Environment = == ⚙️ Preparing the Boot Process == To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. == ✅ The easiest way to boot without entering the BIOS == This method doesn't even require entering the BIOS/Firmware settings: # Restart the system, but '''hold down the Shift key''' while clicking Restart. # If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. == 🧭 In Recovery mode == You will see a list of options, select <code>Use a device</code>, then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). [[File:BootArch.png|center]] == ❗ If the 'Use a device' option is not available == This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == 🧱 The Ventoy Menu == After booting from the USB, you will see the Ventoy menu. Select the Arch Linux ISO file from it, then press Enter twice. ---- == 🎯 Starting the Live Environment == After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. [[File:ArchBoot.png|center]] ---- == Live Environment Font == If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: setfont ter-132n The font will change from this: [[File:ArchFontBefore.png|center]] To this: [[File:ArchFontAfter.png|center]] == Notes on available fonts: == The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. Here are some good options: * <code>setfont ter-132n</code><br>Large and clear font, excellent for small screens. * <code>setfont ter-128n</code><br>Similar but slightly smaller than <code>132n</code>. * <code>setfont ter-v32b</code><br>A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. * <code>setfont lat9w-16</code>The default font in many distributions, suitable but smaller than others. ---- = Connecting to the Internet = === Ethernet cable users === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. To check the connection, try the following command: ping google.com You can replace <code>google.com</code> with any other website. If you start seeing messages like: 64 bytes from ... icmp_seq=2 time=23.3 ms The internet is working successfully! However, if you see a message like: ping: google.com: Temporary failure in name resolution It means the internet connection is not active. === Note: === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: pacman -Sy This command synchronizes the package databases. If you see the message: :: Synchronizing package databases... This means your internet is working correctly. == Wi-Fi users == [[File:Iwctl-1.png|right|frameless]] In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. To start the tool: iwctl Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. # Find the name of your Wi-Fi device:<pre>device list</pre>The network device name will appear, like <code>wlan0</code>. # Scan for nearby networks:<syntaxhighlight> station wlan0 scan station wlan0 get-networks </syntaxhighlight>(Replace <code>wlan0</code> with your actual device name if different.) # Connect to the network: #* If the network is visible:<syntaxhighlight>station wlan0 connect 'SSID'</syntaxhighlight> #* If the network is hidden:<syntaxhighlight>station wlan0 connect-hidden 'SSID'</syntaxhighlight> :(Replace <code>'SSID'</code> with your network name.) :After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. == Verifying internet access after connecting to Wi-Fi == You can use: ping google.com or: pacman -Sy If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. ---- = Disks in Linux = == Disk Naming in Linux == Disk naming in Linux is different from Windows. For example, you might see a path like: /dev/sda2 === Explanation of parts: === ;<code>/dev</code> : This is the folder containing all system devices, like disks, network cards, etc. : <code>dev</code> is short for '''device'''. ;<code>sda</code> :This is the name of the first disk. Linux starts naming disks with letters: :* <code>sda</code>: First disk :* <code>sdb</code>: Second disk :* <code>sdc</code>: Third... and so on. === ❗ Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' *:<code>/dev/sdXY</code> *:Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' *:<code>/dev/nvmeXnYpZ</code> *:Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' *:<code>/dev/vdXY</code> *:Example: <code>/dev/vda1</code> → First virtual disk, first partition. == Partitioning the Disk for Arch Linux Installation ⚙️ == You can view all connected disks using the <code>lsblk</code> command, which shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. [[File:Lsblk.png|center]] == Opening the cfdisk tool for disk partitioning 🧱 == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. To run it: cfdisk /dev/sda Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. And the interface will open... == disk partitioning == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == Partitioning the Free Space == As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. == Controlling the cfdisk tool: == You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. == To start partitioning the free space: == Use the Down arrow until you reach Free Space. You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. [[File:Cfdisk-2.png|center]] == System Partitioning: == To install the Arch system, we need at least two partitions: * A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. * The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === What size for each partition? === * Boot partition: We allocate a maximum of 1G for it. This is more than enough. * Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === Creating the Boot partition === * In the cfdisk tool, select the Free Space using the arrow keys. * Choose New from the options at the bottom, and press Enter. * A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter.[[File:Cfdisk-3.png|center]] *The first partition, the boot partition, will be created.[[File:Cfdisk-4.png|center]] === Creating the Root partition === After finishing creating the boot partition, we move directly to creating the second partition, the root partition. * Select the remaining Free Space using the arrow keys. * Choose New from the options at the bottom of the screen, then press Enter. * This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|center]] === Confirming changes and writing partitions to the disk === When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. * After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png|center]] * A warning question will appear:<pre>Are you sure you want to write the partition table to disk?</pre>If you are sure of the changes, type yes in lowercase letters (Pay attention to case sensitivity), then press Enter.[[File:Cfdisk-7.png|center]] * With this, the changes have been physically written to the disk and the partitions have been successfully created. === Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved [[File:Cfdiskfinal.png|center]] Now make sure to note the names of the two partitions you created: * The first partition (size 1G) is the bootloader partition. * The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: lsblk It will show you all disks and partitions, and you can identify the two partitions based on their size. == Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: * FAT32 for the bootloader partition * EXT4 for the root / partition But why choose these two systems specifically? === Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: * It is the only filesystem that UEFI can read without any intermediaries. * It does not contain complex permissions or modern features that hinder UEFI. * It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. === Why EXT4 for the root / partition? === The root partition contains the entire operating system, so it needs a modern filesystem that supports: * File permissions: To determine who has the right to read, execute, or modify each file. * Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). * Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. * Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. To format the bootloader partition, we write the following command: mkfs.fat -F32 /dev/sda5 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === * <code>mkfs</code> = Make File System = Create a filesystem. * <code>fat</code> is the type of system. * <code>-F32</code> means we use FAT32 (not FAT16 or others). * <code>/dev/sda5</code> is the partition we created for boot (1GB). Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. [[File:Mkfs-1.png|center]] As for formatting the root partition, we use the following command: mkfs.ext4 /dev/sda6 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|center]] Now that we've finished formatting, we're ready to move on to the mounting step! ---- == Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: mount /dev/sda6 /mnt Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|center]] === Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside <code>/mnt</code>, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: mkdir -p /mnt/boot/efi The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: mount /dev/sda5 /mnt/boot/efi And as usual, replace /dev/sda5 with the actual name of your boot partition. If everything is good, we start moving to the system installation step! ---- == Installing the System == To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. But... isn't <code>pacman</code> the package manager in Arch? : Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. ;pacman :The primary package manager in Arch Linux. :Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). ;pacstrap :A special tool used during installation from the live environment. :Installs packages onto a specified path — usually /mnt — instead of the live system. :Its function is to prepare the root partition with basic system packages, such as: :*The Linux kernel :*The package manager <code>pacman</code> itself! :* Networking tools :* System files == Installing the base packages == We use the following command to install the basic system inside the new root partition <code>/mnt</code>: pacstrap /mnt base linux linux-firmware But why these specific packages?! And what does each one do? === base === The base package containing everything the system needs to function. 🔍 Includes: * Basic command-line tools like sh, ls, cp, mv, mkdir... * Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) * Important scripts that aid in booting === linux === This is the system kernel itself. * Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks ---- = Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == What is fstab? == It is a configuration file that tells the system: <blockquote>"What partitions do you have? Where do you want to mount each partition? And with which filesystem?"</blockquote> You can imagine it as a simple table containing: * Partition name (or UUID) * Its mount location (like / or /boot/efi) * Filesystem type * Mount properties and additional options == Generating fstab automatically == To generate the file easily, we use this command: genfstab -U /mnt >> /mnt/etc/fstab Explanation of command components: * <code>genfstab</code>: Short for "Generate File System Table" * <code>-U</code>: Makes it use UUID identifiers instead of disk names * <code>/mnt</code>: Is the root of the new system we installed * <code>>></code>: Means append the output to the file <code>/mnt/etc/fstab</code> === Why use UUID instead of <code>/dev/sdaX</code>? === '''Because disk names like /dev/sda1 can change for many reasons, such as:''' * Connecting new flash drives or disks * Changing the boot order from the BIOS * Random recognition by the Linux kernel '''But UUID:''' * A unique and fixed number generated when the partition is formatted * Never changes unless you delete or reformat the partition 🔒 So using UUID is the safe and reliable solution. ---- Now we can move to the next step, which is entering the new system's root We can use the command: arch-chroot /mnt The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. [[File:Arch-chroot.png|center]] After entering the system using <code>arch-chroot</code>, we begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. 📦 We use the following command pacman -Sy sudo nano grub efibootmgr os-prober networkmanager [[File:Pacman.png|center]] But what does each package do and how does it help us prepare the system? === ✅ <code>sudo</code> === <blockquote>A tool that grants root privileges to a regular user when needed, instead of always logging in as root.</blockquote> * Very important for system administration after creating your own user. === ✅ <code>nano</code> === <blockquote>A simple and easy text editor, ideal for any beginner.</blockquote> * If you need to edit a configuration file, <code>fstab</code>, <code>grub</code>, or <code>hostname</code>, this is the savior. === ✅ <code>grub</code> === <blockquote>The famous bootloader – allows the system to boot and shows you a menu to boot Linux or other systems (like Windows, which we will add to this menu).</blockquote> * Without GRUB? The system won't boot, and you won't be able to access the system you just installed without the live environment. === ✅ <code>efibootmgr</code> === <blockquote>A tool that interacts with boot settings in '''UEFI''' systems.</blockquote> * Helps you install GRUB correctly within the UEFI environment * It is what makes GRUB appear in the BIOS UEFI boot options menu === ✅ <code>os-prober</code> === <blockquote>A tool that searches for other operating systems installed on the device (like Windows).</blockquote> * Very useful if you have another system and want GRUB to show all of them * Must be run after installing GRUB to detect the others === ✅ <code>networkmanager</code> === > A modern and smart network manager, saves you the headache of manually setting up the network. == Explanation of the command parts: == <code>pacman</code> call the package manager <code>-Sy</code> means synchronize the following databases and install the packages <code>sudo nano ...</code> the package names sequentially separated by a space --- = 🧩 Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == 🛠️ Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === 🔧 Steps inside the file === ==== 1️⃣ Modify the GRUB_TIMEOUT option ==== This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). 🔁 Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png|center]] ==== 2️⃣ Enable the os-prober tool ==== Scroll down to the end of the file, and you will see a line like this: #GRUB_DISABLE_OS_PROBER=false All you need to do is remove the # sign to activate the feature, so it becomes: GRUB_DISABLE_OS_PROBER=false [[File:Grub-conf_1.png|center]] 🎯 This allows GRUB to detect Windows and add it to the menu automatically. After editing, save and exit nano: Ctrl + X → then y → then Enter ---- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: /dev/sda1 We mount it with this command: mount /dev/sda1 /boot/efi ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|center]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png|center]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png|center]] ---- == 🧠 Generating the GRUB configuration file == Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. We use the following command: grub-mkconfig -o /boot/grub/grub.cfg Explanation of parts: * <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. * <code>-o</code>: means "Output", i.e., where to save the output file. * <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|center]] ---- = 👤 Creating a new user = After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: useradd -m -G wheel -s /bin/bash username Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == * <code>useradd</code>: The command responsible for creating the user. * <code>-m</code>: Creates the home directory automatically in /home/username. * <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. * <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png|center]] ---- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: passwd Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: password updated successfully [[File:Passwd.png|center]] Then you're good. Setting the password for the new user: passwd username Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png|center]] ---- = 🛡️ Enabling sudo privileges for the wheel group = Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: EDITOR=nano visudo [[File:Visudo-1.png|center]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png|center]] Scroll down until you reach this line: # %wheel ALL=(ALL:ALL) ALL [[File:Visudobefore.png|center]] What do you do? Remove the # sign from the beginning, so it becomes like this: %wheel ALL=(ALL:ALL) ALL [[File:Visudoafter.png]] ✨ Now the user in the wheel group can use sudo. To save changes and exit nano, press {{Keypress|Ctrl|X}}{{Keypress|Y|Enter|chain=}} ---- = 🖥️ Setting the device name (Hostname) = The hostname is what appears to you in the command line and is very useful for networks. To set the name: echo 'ArchBox' > /etc/hostname [[File:Hostname.png|center]] Replace ''ArchBox'' with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: nano /etc/hosts [[File:Etchosts_before.png|center]] After it opens, add this line: 127.0.1.1 ArchBox.localdomain ArchBox Replace ''ArchBox'' with the name you wrote in the previous step. [[File:Etchosts_after.png|center]] ---- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: systemctl enable NetworkManager Just make sure you wrote the name correctly, with the exact case. ---- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇 = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: pacman -S gnome gnome-extra gdm And then enable the login manager: systemctl enable gdm 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. = 💎 Option Two: KDE Plasma + SDDM = If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. Execute the following command: pacman -S plasma kde-applications sddm Then enable the login manager: systemctl enable sddm 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. ---- = 🧼 Finishing the installation and rebooting = Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. First, exit chroot: exit You will return to the live environment (USB). Now unmount the partitions we mounted: umount -R /mnt And finally... the awaited moment 🎉: reboot After rebooting, if everything is fine, you will see the GRUB menu with: Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png|center]] Congratulations on your First Dual Booting experience, thank you for reading. e2e15dc8dafc9e641107312937ab68290ac0233e 4132 4128 2025-09-11T09:36:09Z Hog 161 further clean up wikitext text/x-wiki {{Guide Warning}} {{cleanup}} {{Needs Citations}} = Checking the Boot Mode = [[File:CheckUEFI-1.png|right|frameless]] [[File:CheckUEFI-2.png|right|frameless]] There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> → Your system is using UEFI mode. #* If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' = Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|center]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|center]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' → This is a GPT disk. #* If it says '''Master Boot Record''' → This is an MBR disk. The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data''') or use a separate physical disk. '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png|center]] ---- = Preparing a Partition on the Disk for Arch Linux = Before leaving the Disk Management tool, we need free space to install Arch on. * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == How to shrink the Windows partition: == # From within Disk Management, right-click the <code>C:\</code> partition. Choose from the menu: <code>Shrink Volume</code>[[File:ShrinkPartition-1.png|center]] # In the new window, enter the amount of space you want to shrink (in '''Megabytes'''), then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png|center]] # Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: [[File:FinalPartitionLayout-Shrinked.png|center]]<br>Or like this if you deleted another non-Windows partition:[[File:FinalPartitionLayout-Replaced.png|center]] ---- = Downloading the Arch Linux ISO = You need to [https://archlinux.org/download/ download] the latest ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment.[[File:ArchDownload.png|left]] ---- = Preparing the USB Drive to Boot the Live Environment = We need a USB flash drive to install the Arch live environment, this tutorial use the [[Ventoy]] tool because it is the easiest and most flexible. == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == Steps to download Ventoy: == # Download Ventoy from the official website or directly from SourceForge: #* [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] #* [https://www.ventoy.net/en/index.html Official Ventoy Website] [[File:VentoyDownload.png|left]] [[File:VentoyDownload-2.png|center]] # After downloading, you will get a compressed <code>.zip</code> file. Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png|center]] == How to install Ventoy on the USB drive == After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. Make sure the program recognized the drive and shows its name in the Device field. [[File:VentoyInstall-2.png|center]] == ⚙️ Customizing Ventoy settings before installation == # Disable Secure Boot support<br>Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it.[[File:VentoyInstall-3.png|center]] # Specifying the disk partition type:<br>From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT'''<br>Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png|center]] # Customizing partition configuration: #*From the '''Options''' menu → Select '''Partition Configuration'''[[File:VentoyInstall-5.png|center]] #*And in the first option within the new window:<br>'''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK'''[[File:VentoyInstall-6.png|center]] === Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == Installing Ventoy == Press '''Install''', then agree to the warnings, and wait for the process to complete. [[File:VentoyInstall-7.png|center]] Upon successful installation, you will see a confirmation message. Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. [[File:VentoyInstall-8.png|center]] ---- '''Your USB flash drive is now ready to boot into the Arch live environment 🎉.''' ---- = Booting into the Live Environment = == Preparing the Boot Process == To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. == The easiest way to boot without entering the BIOS == This method doesn't even require entering the BIOS/Firmware settings: # Restart the system, but '''hold down the Shift key''' while clicking Restart. # If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. == In Recovery mode == You will see a list of options, select <code>Use a device</code>, then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). [[File:BootArch.png|center]] == ❗ If the 'Use a device' option is not available == This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == The Ventoy Menu == After booting from the USB, you will see the Ventoy menu. Select the Arch Linux ISO file from it, then press Enter twice. ---- == Starting the Live Environment == After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. [[File:ArchBoot.png|center]] ---- == Live Environment Font == If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: setfont ter-132n The font will change from this: [[File:ArchFontBefore.png|center]] To this: [[File:ArchFontAfter.png|center]] == Notes on available fonts: == The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. Here are some good options: * <code>setfont ter-132n</code><br>Large and clear font, excellent for small screens. * <code>setfont ter-128n</code><br>Similar but slightly smaller than <code>132n</code>. * <code>setfont ter-v32b</code><br>A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. * <code>setfont lat9w-16</code>The default font in many distributions, suitable but smaller than others. ---- = Connecting to the Internet = === Ethernet cable users === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. To check the connection, try the following command: ping google.com You can replace <code>google.com</code> with any other website. If you start seeing messages like: 64 bytes from ... icmp_seq=2 time=23.3 ms The internet is working successfully! However, if you see a message like: ping: google.com: Temporary failure in name resolution It means the internet connection is not active. === Note: === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: pacman -Sy This command synchronizes the package databases. If you see the message: :: Synchronizing package databases... This means your internet is working correctly. == Wi-Fi users == [[File:Iwctl-1.png|right|frameless]] In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. To start the tool: iwctl Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. # Find the name of your Wi-Fi device:<pre>device list</pre>The network device name will appear, like <code>wlan0</code>. # Scan for nearby networks:<syntaxhighlight> station wlan0 scan station wlan0 get-networks </syntaxhighlight>(Replace <code>wlan0</code> with your actual device name if different.) # Connect to the network: #* If the network is visible:<syntaxhighlight>station wlan0 connect 'SSID'</syntaxhighlight> #* If the network is hidden:<syntaxhighlight>station wlan0 connect-hidden 'SSID'</syntaxhighlight> :(Replace <code>'SSID'</code> with your network name.) :After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. == Verifying internet access after connecting to Wi-Fi == You can use: ping google.com or: pacman -Sy If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. ---- = Disks in Linux = == Disk Naming in Linux == Disk naming in Linux is different from Windows. For example, you might see a path like: /dev/sda2 === Explanation of parts: === ;<code>/dev</code> : This is the folder containing all system devices, like disks, network cards, etc. : <code>dev</code> is short for '''device'''. ;<code>sda</code> :This is the name of the first disk. Linux starts naming disks with letters: :* <code>sda</code>: First disk :* <code>sdb</code>: Second disk :* <code>sdc</code>: Third... and so on. === Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' *:<code>/dev/sdXY</code> *:Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' *:<code>/dev/nvmeXnYpZ</code> *:Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' *:<code>/dev/vdXY</code> *:Example: <code>/dev/vda1</code> → First virtual disk, first partition. == Partitioning the Disk for Arch Linux Installation ⚙️ == You can view all connected disks using the <code>lsblk</code> command, which shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. [[File:Lsblk.png|center]] == Opening the cfdisk tool for disk partitioning == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. To run it: cfdisk /dev/sda Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. == disk partitioning == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == Partitioning the Free Space == As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. == Controlling the cfdisk tool: == You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. == To start partitioning the free space: == Use the Down arrow until you reach Free Space. You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. [[File:Cfdisk-2.png|center]] == System Partitioning: == To install the Arch system, we need at least two partitions: * A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. * The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === What size for each partition? === * Boot partition: We allocate a maximum of 1G for it. This is more than enough. * Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === Creating the Boot partition === * In the cfdisk tool, select the Free Space using the arrow keys. * Choose New from the options at the bottom, and press Enter. * A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter.[[File:Cfdisk-3.png|center]] *The first partition, the boot partition, will be created.[[File:Cfdisk-4.png|center]] === Creating the Root partition === After finishing creating the boot partition, we move directly to creating the second partition, the root partition. * Select the remaining Free Space using the arrow keys. * Choose New from the options at the bottom of the screen, then press Enter. * This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|center]] === Confirming changes and writing partitions to the disk === When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. * After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png|center]] * A warning question will appear:<pre>Are you sure you want to write the partition table to disk?</pre>If you are sure of the changes, type yes in lowercase letters (Pay attention to case sensitivity), then press Enter.[[File:Cfdisk-7.png|center]] * With this, the changes have been physically written to the disk and the partitions have been successfully created. === Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved [[File:Cfdiskfinal.png|center]] Now make sure to note the names of the two partitions you created: * The first partition (size 1G) is the bootloader partition. * The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: lsblk It will show you all disks and partitions, and you can identify the two partitions based on their size. == Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: * FAT32 for the bootloader partition * EXT4 for the root / partition But why choose these two systems specifically? === Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: * It is the only filesystem that UEFI can read without any intermediaries. * It does not contain complex permissions or modern features that hinder UEFI. * It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. === Why EXT4 for the root / partition? === The root partition contains the entire operating system, so it needs a modern filesystem that supports: * File permissions: To determine who has the right to read, execute, or modify each file. * Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). * Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. * Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. To format the bootloader partition, we write the following command: mkfs.fat -F32 /dev/sda5 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === * <code>mkfs</code> = Make File System = Create a filesystem. * <code>fat</code> is the type of system. * <code>-F32</code> means we use FAT32 (not FAT16 or others). * <code>/dev/sda5</code> is the partition we created for boot (1GB). Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. [[File:Mkfs-1.png|center]] As for formatting the root partition, we use the following command: mkfs.ext4 /dev/sda6 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|center]] Now that we've finished formatting, we're ready to move on to the mounting step! ---- == Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: mount /dev/sda6 /mnt Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|center]] === Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside <code>/mnt</code>, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: mkdir -p /mnt/boot/efi The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: mount /dev/sda5 /mnt/boot/efi And as usual, replace /dev/sda5 with the actual name of your boot partition. If everything is good, we start moving to the system installation step! ---- == Installing the System == To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. But... isn't <code>pacman</code> the package manager in Arch? : Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. ;pacman :The primary package manager in Arch Linux. :Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). ;pacstrap :A special tool used during installation from the live environment. :Installs packages onto a specified path — usually /mnt — instead of the live system. :Its function is to prepare the root partition with basic system packages, such as: :*The Linux kernel :*The package manager <code>pacman</code> itself! :* Networking tools :* System files == Installing the base packages == We use the following command to install the basic system inside the new root partition <code>/mnt</code>: pacstrap /mnt base linux linux-firmware But why these specific packages?! And what does each one do? === base === The base package containing everything the system needs to function. 🔍 Includes: * Basic command-line tools like sh, ls, cp, mv, mkdir... * Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) * Important scripts that aid in booting === linux === This is the system kernel itself. * Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks ---- = Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == Generating fstab automatically == To generate the file easily, we use this command: genfstab -U /mnt >> /mnt/etc/fstab Explanation of command components: * <code>genfstab</code>: Short for "Generate File System Table" * <code>-U</code>: Makes it use UUID identifiers instead of disk names * <code>/mnt</code>: Is the root of the new system we installed * <code>>></code>: Means append the output to the file <code>/mnt/etc/fstab</code> == Entering the new system's root == We can use the command: arch-chroot /mnt The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. [[File:Arch-chroot.png|center]] After entering the system using <code>arch-chroot</code>, we begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. We use the following command pacman -Sy sudo nano grub efibootmgr os-prober networkmanager [[File:Pacman.png|center]] = Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === Steps inside the file === ==== Modify the GRUB_TIMEOUT option ==== This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png|center]] ==== Enable the os-prober tool ==== Scroll down to the end of the file, and you will see a line like this: #GRUB_DISABLE_OS_PROBER=false All you need to do is remove the # sign to activate the feature, so it becomes: GRUB_DISABLE_OS_PROBER=false [[File:Grub-conf_1.png|center]] 🎯 This allows GRUB to detect Windows and add it to the menu automatically. After editing, save and exit nano: Ctrl + X → then y → then Enter ---- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: /dev/sda1 We mount it with this command: mount /dev/sda1 /boot/efi ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|center]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png|center]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png|center]] ---- == 🧠 Generating the GRUB configuration file == Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. We use the following command: grub-mkconfig -o /boot/grub/grub.cfg Explanation of parts: * <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. * <code>-o</code>: means "Output", i.e., where to save the output file. * <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|center]] ---- = 👤 Creating a new user = After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: useradd -m -G wheel -s /bin/bash username Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == * <code>useradd</code>: The command responsible for creating the user. * <code>-m</code>: Creates the home directory automatically in /home/username. * <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. * <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png|center]] ---- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: passwd Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: password updated successfully [[File:Passwd.png|center]] Then you're good. Setting the password for the new user: passwd username Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png|center]] ---- = 🛡️ Enabling sudo privileges for the wheel group = Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: EDITOR=nano visudo [[File:Visudo-1.png|center]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png|center]] Scroll down until you reach this line: # %wheel ALL=(ALL:ALL) ALL [[File:Visudobefore.png|center]] What do you do? Remove the # sign from the beginning, so it becomes like this: %wheel ALL=(ALL:ALL) ALL [[File:Visudoafter.png]] ✨ Now the user in the wheel group can use sudo. To save changes and exit nano, press {{Keypress|Ctrl|X}}{{Keypress|Y|Enter|chain=}} ---- = 🖥️ Setting the device name (Hostname) = The hostname is what appears to you in the command line and is very useful for networks. To set the name: echo 'ArchBox' > /etc/hostname [[File:Hostname.png|center]] Replace ''ArchBox'' with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: nano /etc/hosts [[File:Etchosts_before.png|center]] After it opens, add this line: 127.0.1.1 ArchBox.localdomain ArchBox Replace ''ArchBox'' with the name you wrote in the previous step. [[File:Etchosts_after.png|center]] ---- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: systemctl enable NetworkManager Just make sure you wrote the name correctly, with the exact case. ---- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇 = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: pacman -S gnome gnome-extra gdm And then enable the login manager: systemctl enable gdm 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. = 💎 Option Two: KDE Plasma + SDDM = If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. Execute the following command: pacman -S plasma kde-applications sddm Then enable the login manager: systemctl enable sddm 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. ---- = 🧼 Finishing the installation and rebooting = Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. First, exit chroot: exit You will return to the live environment (USB). Now unmount the partitions we mounted: umount -R /mnt And finally... the awaited moment 🎉: reboot After rebooting, if everything is fine, you will see the GRUB menu with: Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png|center]] Congratulations on your First Dual Booting experience, thank you for reading. 1f8e453c709b5b6ae25fd49d252a27635ae0a865 0 628 4114 4016 2025-09-09T09:47:32Z Hog 161 corrected latest version wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history.<ref>[https://iso.atl.dev/l/linuxmint linuxmint - ATL ISO Archives], All Things Linux (Accessed: 2025-08-09)</ref> There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. In 2016, the Linux Mint website and forums were hacked and the installation images were infected with malware.<ref>{{Cite|url=https://www.pcworld.com/article/419713/hackers-planted-a-backdoor-inside-a-compromised-version-of-linux-mint.html|title=Linux Mint website hacked, ISO downloads replaced with backdoored operating system|author=Nick Mediati, PCWorld|year=2016|accessdate=2025.08.31}}</ref> The latest release, Linux Mint 22.2 "Zara", was launched on the 4th of September, 2025 and is supported until 2029.<ref>https://linuxmint.com/rel_zara.php, Linux Mint, 2006-08-09 (Accessed: 2025-09-09)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> == References == c6dd0c018cd13f61f48d1d0190dea601ddacabac 0 1011 4118 4086 2025-09-09T13:23:24Z Hog 161 corrected punctuation wikitext text/x-wiki {{stub}}{{DistributionInfobox|title=Arco Linux|image=[[File:Arcolinux.svg| 200px]]|caption=The Arco Linux logo|releasestatus=Discontinued|releasemodel=Rolling Release|packagemanager=[[Pacman]]|defaultdesktops=[[KDE Plasma]], [[Xfce]]|usagetype=Desktop|architectures=x86_64|website=[https://arcolinux.com/ arcolinux.com]}} 7ffcc4e8bcdfd9cbd1f9ecb0aa0a1f56030de669 0 772 4120 3370 2025-09-10T07:40:53Z Hog 161 corrected latest release wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.7 - 14 August 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level programming language originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>[http://www.artima.com/intv/pythonP.html The Making of Python], Bill Venners, 2003-01-13 (Accessed: 2025-08-09)</ref> as a successor to the ABC programming language. He released the first version (0.9.0)<ref>[https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html The History of Python: A Brief Timeline of Python], Guido van Rossum, 2009-01-20 (Accessed: 2025-08-09)</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>[https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html Python Insider: Python 2.7.18, the last release of Python 2], Benjamin Peterson, 2020-04-20 (Accessed: 2025-08-09)</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>[https://survey.stackoverflow.co/2022/ Stack Overflow Developer Survey 2022], Stack Overflow, 2022-08-09 (Accessed: 2025-08-09)</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>[https://www.python.org/doc/av Audio/Video Instructional Materials for Python], Python Software Foundation, 2025-08-09 (Accessed: 2025-08-09)</ref> Python is currently the most used programming language among developers<ref>[https://www.tiobe.com/tiobe-index/ TIOBE Index], Paul Jansen, 2025-08-09 (Accessed: 2025-08-09)</ref>, used daily for lots of general-purpose software. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop Tux and Wikibot). Python comes preinstalled with an interpreter and also IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE.<!-- However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. --> == pip (Package Manager) == [https://pypi.org/project/pip/ pip] is Python's Package Manager, through pip you can install all the libraries needed for your project to run. pip stands for "''pip Installs Packages"''<ref>[https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for python - What does PIP stand for? - Unix & Linux Stack Exchange], Unix & Linux Stack Exchange, 2014-11-24 (Accessed: 2025-08-09)</ref>. pip connects to an online software repository (PyPI). pip was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain pip and venv. === Installation for pip === Python 3.4+ included pip by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash"> python -m ensurepip --upgrade </syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script from https://bootstrap.pypa.io/get-pip.py. # Open a new [[terminal]] and [[cd]] to the folder containing the file # <code>python get-pip.py</code> === Installing packages with pip === {{Guide Warning}} pip install package-name == Virtual Environments (VENV) == The venv module allows users to create Virtual Environments each with their own independent modules and libraries, This is useful for isolating project dependencies or debugging. Created by Ian Bicking (the same developer who created pip), it is now maintained by the Python Package Authority (PyPA). == Installation == {{Guide Warning}} === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> sudo apt update sudo apt install python3 python3-pip </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash"> sudo pacman -Syu python python-pip </syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight lang="bash"> sudo yum install python3 python3-pip </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> sudo yum install python3 python3-pip </syntaxhighlight> == '''Setup Python venv''' == {{Guide Warning}} When installing pip packages system-wide as root you will typically see a message like this one: <syntaxhighlight lang="shell-session"> [user@hostname ~]$ sudo pip install pyperclip Collecting pyperclip Downloading pyperclip-1.9.0.tar.gz (20 kB) Preparing metadata (setup.py) ... done Building wheels for collected packages: pyperclip Building wheel for pyperclip (setup.py) ... done Created wheel for pyperclip: filename=pyperclip-1.9.0-py3-none-any.whl size=11014 sha256=696d851be7b0d99fe8112ddf5c6ebc2b9444464b2a729911930d64bebc124c35 Stored in directory: /root/.cache/pip/wheels/cc/ae/36/ee17d1de094fcb61e24106cb329b5103861e819f94bef5e10a Successfully built pyperclip Installing collected packages: pyperclip Successfully installed pyperclip-1.9.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv </syntaxhighlight> Running pip as root can result in conflicts, broken packages and security risks.<ref>[https://askubuntu.com/questions/802544/is-sudo-pip-install-still-a-broken-practice package management - Is `sudo pip install` still a broken practice? - Ask Ubuntu], Ask Ubuntu, 2016-07-25 (Accessed: 2025-08-09)</ref> There are two possible responses to this situation: * See whether your distribution offers a system package to suit your needs. Depending on the distribution, system packages may be outdated, but this option should be tried first unless you are actively developing software. For example, with the Python module pyperclip mentioned above, there was a system package available that could fill the need, python3-pyperclip. * Or, if you are writing your own software, you can heed the warning as written and use the following instructions: python -m venv path/to/venv/ source path/to/venv/bin/activate The first line creates the folder containing the venv and the second line activates it. If you are not using bash, things may change slightly. For example, a user of the [[fish]] shell would instead run source venv/bin/activate.fish You'll know that a venv is currently active from an altered prompt such as this one: <syntaxhighlight lang="shell-session"> (venv) [user@hostname ~]$ </syntaxhighlight> With a venv loaded, all pip commands such as "pip install" and "pip uninstall" will affect only that venv. All Python code run with the venv's installation of Python will prefer to import the venv's libraries over any system libraries. (The command "which python" can help ensure that it is truly the venv Python as opposed to, say, the system "/usr/bin/python" that is running.) Lastly, a user who wishes to turn off a venv for the time being will only need to give the command "deactivate" to the shell. Further information about venv can be found in [https://docs.python.org/3/library/venv.html Python's official documentation]. == References == b61786adc158c488e8873d669a74018f3a96661d 0 341 4121 3683 2025-09-10T07:41:37Z Hog 161 punctuation wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:Tde-logo.png]] | caption = Trinity Desktop Environment logo | title = Trinity Desktop Environment | releasestatus = Maintained | lastrelease = R14.1.3, 2024-10-27 | languages = [[C++]] | developers = Trinity Development Team | website = [https://www.trinitydesktop.org/ trinitydesktop.org] }} [[Category:Desktop Environments]] [[File:Trinity R.14.1.3 screenshot.png|thumb|Screenshot of Trinity Desktop R14.1.3]] Trinity Desktop Environment (TDE) is an X11 [[Desktop Environments|desktop environment]] for [[Unix-Like]] [[Operating System|Operating systems]] forked from KDE 3.5 in 2010. Trinity is packaged for [[Arch Linux]], [[Debian]], [[Fedora]], [[Gentoo]], [[Mageia]], [[OpenSUSE]], [[Raspberry Pi OS]], [[Red Hat Enterprise Linux]], [[Slackware]], [[Ubuntu]] and various other [[Linux Distributions|distributions]]. ab612c544f2234c355129cde252d8f3df712ddb8 4122 4121 2025-09-10T07:42:40Z Hog 161 Added Links wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:Tde-logo.png]] | caption = Trinity Desktop Environment logo | title = Trinity Desktop Environment | releasestatus = Maintained | lastrelease = R14.1.3, 2024-10-27 | languages = [[C++]] | developers = Trinity Development Team | website = [https://www.trinitydesktop.org/ trinitydesktop.org] }} [[Category:Desktop Environments]] [[File:Trinity R.14.1.3 screenshot.png|thumb|Screenshot of Trinity Desktop R14.1.3]] Trinity Desktop Environment (TDE) is an [[X11]] [[Desktop Environments|desktop environment]] for [[Unix-Like]] [[Operating System|Operating systems]] forked from KDE 3.5 in 2010. Trinity is packaged for [[Arch Linux]], [[Debian]], [[Fedora]], [[Gentoo]], [[Mageia]], [[OpenSUSE]], [[Raspberry Pi OS]], [[Red Hat Enterprise Linux]], [[Slackware]], [[Ubuntu]] and various other [[Linux Distributions|distributions]]. b1a663d55fe89d9824feb2ff3a268f3ecfbef457 0 790 4123 3668 2025-09-10T07:43:36Z Hog 161 links wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = Red Star OS | image = [[File:Red Star OS Logo 2020.svg|190px]] | caption = Red Star OS logo | releasestatus = Maintained | releasemodel = Unknown | packagemanager = [[rpm]] | defaultdesktops = [[KDE Plasma]], [[GNOME]] | usagetype = Desktop | architectures = [[IA-32]], [[x86-64]], [[ARM]] | website = None }} '''Red Star OS ('''Korean: 붉은별''')''' is a [[Red Hat Enterprise Linux|Red Hat Linux]] based [[Linux Distributions|distribution]] developed in the Democratic People's Republic of Korea (DPRK), made as a replacement for Windows in North Korea. It was first developed in 1998 by the Korea Computer Center. == Browser == '''Red Star OS''' relies on a heavily modified version of [[Firefox]] called ''[[Naenara]], which means "Our Country" in Korean.'' c91a63a7e59d21e916b53fe113a70b2a05796b9e 0 176 4124 4069 2025-09-10T07:46:22Z Hog 161 fixed latest release wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.4.5, September 9, 2025 [https://kde.org/announcements/plasma/6/6.4.5/] |firstrelease=1.0, July 12, 1998 [https://kde.org/announcements/1-2-3/1.0-beta1/] | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2025-08-14|503}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2025-08-14|503}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> abf41e8861cf115375471ec8e0d2b2832c0ef378 0 679 4125 4095 2025-09-10T07:47:52Z Hog 161 updated latest release wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.51.0 (2025-08-18) [https://git-scm.com/] | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux]] [[kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git's early design emphasized a distributed workflow similar to BitKeeper's but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like [[GitHub]], which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. == References == 75ec872d9901e5a8dfe3ec0a4d2786f77a90a34c 0 198 4126 4097 2025-09-10T08:42:27Z Hog 161 wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == e9f470867f7080d849e069d33a43801a9c9cee9c 4131 4126 2025-09-10T23:06:06Z Satnus 215 Added AxOS, GRML, Linux Lite, UOS and PikaOS. I may have gotten these from the Random Distribution button on Distrowatch... wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == 4d8f92795aaacbad0fe54a5a1c4b998594b2d718 0 1014 4127 2025-09-10T10:36:13Z Hog 161 created bsd page (missing information please correct) wikitext text/x-wiki {{DistributionInfobox|title=BSD|image=[[File:BSD-OS.svg]]|caption=The BSD logo|releasestatus=Discontinued|releasemodel=Discontinued|packagemanager=Unknown (please correct this)|defaultdesktops=Terminal User Interface|usagetype=Desktop|architectures=Unknown (please correct this)|website=[https://www.bsd.org/ www.bsd.org]}}The Berkeley Software Distribution (BSD), also known as Berkeley [[UNIX|Unix]], is a discontinued Unix [[Operating System|operating system]] developed and distributed by the Computer Systems Research Group (CSRG) at the University of California, Berkeley (Hence the name). First released in 1978, it began as an improved derivative of AT&T's original Unix developed at Bell Labs, based on the source code. BSD's Mascot is [[Beastie]], a red demon/devil cartoonish character. 22a74b0ba0da6059229aba897dab3d9ae7394b49 0 254 4129 4013 2025-09-10T11:09:26Z Hog 161 links wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{Needs Citations}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.6, 2025-08-09 | languages = [[C]] | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a [[Window Manager|window manager]] developed by Suckless. dwm is designed to be small in source code, fast and light<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a terminal emulator. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. patches can be installed by running: patch -p1 < path/to/patch.diff if patch fails, you should check the .rej file, edit manually and recompile dwm. some patches edit config.def.h, you should then edit the Makefile to remove config.h during clean and copy config.def.h to config.h. == See Also == [https://dwm.suckless.org/ dwm suckless - main page] == References == f155d491f86040cc4ab0a631e5dcaac3f5809bea 0 651 4130 4096 2025-09-10T18:35:37Z Imnotgoodatnames 121 fixed link to CLI page wikitext text/x-wiki An operating system (OS) is a collection of [[software]] that manages a computer's [[hardware]] and [[applications]] by allocating resources, including memory, CPU, input/output devices and file storage.<ref>[https://www.ibm.com/think/topics/operating-systems What is an Operating System? | IBM], Stephanie Susnjara & Ian Smalley, 2025-03-05 (Accessed: 2025-08-09)</ref> A user interacts with an operating system through a [[user interface]] (UI), which issues commands in a language the OS can understand. The UI can be either a [[GUI|graphical user interface]] (GUI) or a [[CLI|command-line interface]] (CLI). All computer systems need an OS to function. == References == cbe4678072fed3fdcb80591b9d6a7e0212b50c84 5 728 4133 2784 2025-09-11T09:51:12Z Hog 161 /* Guidelines talk page */ Reply wikitext text/x-wiki == Guidelines talk page == You can discuss or propose changes to the guidelines page below. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 15:54, 19 July 2025 (UTC) :''Before a '''vulnrability''' can be mentioned on the wiki you must wait 7 days after both:'' :typo [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 09:51, 11 September 2025 (UTC) f771d6fcbe0f9605ceca302954773671ab38fc37 0 310 4134 3372 2025-09-11T15:40:43Z Ow0cast 249 grammar wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Alpine Linux | image = [[File:alpinelinux-logo.svg|thumb]] | releasestatus = Maintained | releasemodel = Point or Rolling | packagemanager = [[apk]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[MATE]], [[LXQt]] | usagetype = Container, Embedded, Server, Desktop | architectures = amd64, aarch64, armel, armhf, i686, ppc64le, s390x, loongarch64 | website = [https://www.alpinelinux.org/ alpinelinux.org] }} Alpine Linux is a lightweight Linux distribution that aims to be "small", "simple" and "secure".<ref name=":0">[https://alpinelinux.org/about/ about | Alpine Linux], Alpine Linux Development Team, 2025-02-14 (Accessed: 2025-08-09)</ref> It is one of the few distributions that do not use the GNU C Library or GNU coreutils by default. Alpine, by default, follows a point release update model while its edge repositories follow a rolling release model. Twice a year, typically on November and May, a new stable version is branched from edge and released.<ref>[https://alpinelinux.org/releases/ Alpine release branches | Alpine Linux], Alpine Linux Development Team, 2025-07-15 (Accessed: 2025-08-09)</ref> == Features == Alpine's main feature is its small size. Its minimal system requirements and ease of deployability makes it suitable for use in containers, embedded systems and other systems with very limited resources. All user-space binaries in Alpine are compiled as position-independent executables with stack-smashing protection for security reasons.<ref name=":0" /> Alpine comes preinstalled with configuration scripts which allow quick configuration and installation of the system.<ref>[[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts] <span style="color:#fc493b">[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts] <sup>🍣DEAD?]</ref> Alpine also offers a web-server based configuration tool named the Alpine Configuration Framework (ACF).<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Configuration_Framework_Design Alpine Configuration Framework Design - Alpine Linux], Alpine Linux Wiki, 2025-03-10 (Accessed: 2025-08-09)</ref> Alpine offers a "diskless installation"<ref>[https://wiki.alpinelinux.org/wiki/Installation#Installation_Overview Installation - Alpine Linux], Alpine Linux Wiki, 2025-07-30 (Accessed: 2025-08-09)</ref>, allowing it to be installed to and be used from RAM. == Differences from other Linux Distributions == * Alpine uses musl as its standard C library. This compromises its support for some programs such as Electron based applications<ref>[https://wiki.alpinelinux.org/wiki/APKBUILD_examples:JavaScript APKBUILD examples:JavaScript - Alpine Linux], Alpine Linux Wiki, 2023-05-13 (Accessed: 2025-08-09)</ref> and the NVIDIA drivers.<ref>[https://wiki.alpinelinux.org/wiki/NVIDIA NVIDIA - Alpine Linux], Alpine Linux Wiki, 2025-05-09 (Accessed: 2025-08-09)</ref> * Alpine by default lacks the standard base utilities that other distributions come with such as GNU bash, coreutils, findutils, pciutils, usbutils, util-linux, udev. Instead of these, their BusyBox implementations are used. This is what makes Alpine so small in size, yet this also causes compatibility issues with many programs and scripts as their BusyBox implementations lack many features of their counterparts<ref>[https://wiki.alpinelinux.org/wiki/How_to_get_regular_stuff_working How to get regular stuff working - Alpine Linux], Alpine Linux Wiki, 2025-07-20 (Accessed: 2025-08-09)</ref>. To solve these compatibility issues, the user can install the standard version of these programs as they wish. * Alpine does not use systemd. Instead, it uses BusyBox for its init process and OpenRC for service management.<ref>[https://wiki.alpinelinux.org/wiki/OpenRC OpenRC - Alpine Linux], Alpine Linux Wiki, 2025-08-08 (Accessed: 2025-08-09)</ref> * Alpine uses its own package manager, the "Alpine Package Keeper" (apk).<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper Alpine Package Keeper - Alpine Linux], Alpine Linux Wiki, 2025-05-25 (Accessed: 2025-08-09)</ref> * Alpine uses the LTS branch of the Linux kernel by default.<ref>[https://github.com/alpinelinux/alpine-conf/blob/55ec2cf0504195ee60f68b21a29607302f8a15d0/setup-disk.in#L1489 alpine-conf/setup-disk.in at 55ec2cf0504195ee60f68b21a29607302f8a15d0 · alpinelinux/alpine-conf · GitHub], ncopa, 2025-07-15 (Accessed: 2025-08-09)</ref> == References == 347be6eb531145bb1696cfa293186dfb728d4b76 0 203 4135 3619 2025-09-11T15:45:11Z Ow0cast 249 period before ref wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]].<ref>[https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer) Daniel Robbins (computer programmer)], Wikipedia contributors, 2024-01-10 (Accessed: 2025-08-09)</ref> Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to compile<ref>[https://en.wikipedia.org/wiki/Compilation Compilation], Wikipedia contributors, 2024-07-30 (Accessed: 2025-08-09)</ref> their entire system from source code, providing granular control over system components and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This source-based approach, while more time-consuming than binary distributions, enables optimizations specific to the user's hardware and requirements. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish thru source compilation of the packages and the kernel itself. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements, the only downside of that being increase compilation time, however '''Gentoo''' is very minimal and it allows a lot of flexibility in that regard. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "slotting". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. To manage those multiple versions of the same packages ( slotting ), '''Gentoo''' provides a tool called '''eselect'''. It acts as a manager for setting system defaults, such as choosing which version of GCC, Python, or even your preferred text editor should be used globally. == Use cases of eselect == Changing the GCC version<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect gcc list [1] x86_64-pc-linux-gnu-13 * [2] x86_64-pc-linux-gnu-14 [user@hostname ~]$ eselect gcc set 2</syntaxhighlight>Changing the locale<syntaxhighlight lang="shell-session"> [user@hostname ~]$ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 * [3] en_US.utf8 [4] POSIX [ ] (free form) [user@hostname ~]$ eselect locale set 3 </syntaxhighlight> == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp)</syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [[Portage]] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Key Components ==== * '''emerge''': Primary command-line interface * '''make.conf''': Central configuration file for compilation options * '''USE flags''': Package feature selectors * '''CFLAGS''': Compiler optimization settings * '''package.mask/unmask''': Version control mechanisms * '''package.use''': USE flags control mechanism for individual packages ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge -uDN @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge package</code> | Install a package |- | <code>emerge -C package</code> | Remove a package |- | <code>emerge -pv package</code> | Preview package installation |- | <code>emerge -c</code> | Remove orphaned packages |- |<code>emerge --unmerge package</code> |Remove a package and its dependencies |- |<code>emerge --depclean</code> |Remove unused dependencies |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. === Binary Packages === For users seeking faster installation times, '''Gentoo''' offers pre-compiled package options, which usually end in '''<code>-bin</code>''', by example one might want to install Firefox without the hassle of compiling, they can just download the binary version of it by doing <code>sudo emerge firefox-bin</code>. Obviously, not all binary packages will end in the <code>-bin</code> format, they can be named simply like normal packages, for that reason Portage highlights the binary and source packages differently in colors so the user knows which are binary and which are meant for compiling, additionally portage also informs the user of which packages are binaries or source. For additional packages, users might opt for the [https://wiki.gentoo.org/wiki/Project:GURU GURU] project repository, it aims to be a very large user repository, full of binaries and source packages that are not found inside the normal '''Gentoo''' repositories, meant to extend the experience that you can have in this Operating System. Users can create their own repository online as well, or how we call it, "overlays". The user can create an overlay with the desired package, make an ebuild for it and then publish it online for people to use. To get started with an overlay, one must first understand what are ebuilds and how they work, for this it's preferred to read the '''Gentoo Wiki''' on how to do it, it is possible to even add your custom package inside '''GURU''' later, and even the official '''Gentoo''' repository if it's seen as valuable. == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === One might be interested in community resources for '''Gentoo.''' The official community forums can be found at [https://forums.gentoo.org/ forums.gentoo.org/]. Additionally, IRC<ref>Internet Relay Chat</ref> channels has been setup as well. For those who are interested in the official IRC channels, they can be found on the '''Gentoo Wiki''' in the [https://wiki.gentoo.org/wiki/IRC IRC] article. It is possible to subscribe to the [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] or even send emails to them, the page lists the most important lists with the most traffic. There are other, more specialized lists that might be more appropriate depending on the topic. There is a [https://www.gentoo.org/support/documentation/ wiki documentation] available as well. Users can search up specific pages in the site directly, so that they don't waste time finding the right page. Ultimately, '''Gentoo''' offers a [https://bugs.gentoo.org/ bug tracking system] for those who are interested in being up to date with current bugs, or even attempt to solve them. === Development Model === '''Gentoo''' was developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the userbase through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == '''Gentoo''' allows maximum customization potential, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to fetch binaries in heavier packages. However, '''Gentoo''' has it's own downsides; It will take longer to install packages as they compile from source, meaning it will take some time until finished and ready to use. If the system has a very weak CPU, the Operating System will take a while to fully install. The Operating System has a higher learning curve, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] * [[Portage]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://planet.gentoo.org/ Gentoo Planet] c00a2dd7b150b19da27dc0817bd1265772d79eae 0 802 4136 3658 2025-09-12T10:16:12Z Satnus 215 Added link for CRUX. wikitext text/x-wiki [[Category:Package Manager]] '''pkgutils''' is a set of utilities (pkgadd, pkgrm, pkginfo, pkgmk and rejmerge), which are used for managing software packages in Linux. It is developed for and used by the [[CRUX]] distribution <ref>[http://crux.nu CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> All the packages installed with '''pkgutils''' are plain <code>.tar.gz</code> files. == Usage == The following are several common usages of '''pkgutils'''. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pkgadd package1.pkg.tar.gz package2.pkg.tar.gz</code> {| class="wikitable" |+Common Pkgutils Commands !Command !Description |- |<code>pkgadd package.pkg.tar.gz</code> |Install a given package |- |<code>pkgrm package</code> |Remove a given package. |- |<code>ports -u</code> |Sync ports tree |- |<code>prt-get update</code> |Sync local index with the ports tree |- |<code>prt-get upgrade</code> |Rebuild and reinstalls newer versions of installed packages |- |<code>prt-get search package</code> |Search a given package |- |<code>pkginfo -i</code> |List all installed packages |- |<code>pkginfo package</code> |Display info about a given package |} == See Also == [https://crux.nu/Main/Handbook3-7-Package pkgutils - CRUX] ed3939c2ff7c9d4c08de731ad40f4448655c9137 0 905 4137 4021 2025-09-12T10:55:37Z Satnus 215 Fixed citations. wikitext text/x-wiki {{Guide Warning}} {{DistributionInfobox | title = Bedrock Linux | image = [[File:Bedrock Linux.png|Bedrock_Linux]] | caption = Bedrock Linux Logo | releasestatus = Maintained | packagemanager = [[pmm]] | releasemodel = Meta distribution | usagetype = Desktop/Server | defaultdesktops = None | architectures = x86_64, s390x, ppc64le, ppc64, ppc, mipsel, mips64el, mips, i686, i586, i486, i386, armv7l, armv7hl, aarch64 | website = [https://bedrocklinux.org bedrocklinux.org] }} [[Category:Linux Distributions]] '''Bedrock Linux''' is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. Bedrock integrates these components into one largely cohesive system. <ref>[https://bedrocklinux.org Bedrock Linux Home Page], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> === Distro compatibility === While Bedrock works fine with most distributions, there are distributions which can cause issues with Bedrock. The best examples are:<ref>[https://bedrocklinux.org/0.7/distro-compatibility.html Bedrock Linux 0.7 Poki Distro Support], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> * Distributions that use BSD-like sysvinit * Distributions that use GRUB+BTRFS (due to a bug in GRUB <ref>[https://bedrocklinux.org/0.7/feature-compatibility.html#grub-btrfs-zfs Grub with BTRFS or ZFS], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref>) * Immutable distributions * Non FHS-compliant distributions like [[NixOS]] or [[GUIX]] === Installation === The Bedrock Linux website provides a hijack script which can be used to convert current Linux distribution to Bedrock Linux <ref>[https://bedrocklinux.org/0.7/installation-instructions.html Installation Instructions], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> === Going through the tutorial === Bedrock Linux provides an interactive tutorial which can be accessed with <code>brl tutorial basics</code>, but also a text version for those who prefer those <ref>[https://bedrocklinux.org/0.7/basic-usage.html Basic Usage], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> === Known issues === ==== brl update and brl fetch fail with proxy ==== With some specific URL's brl fetch and brl update might fail For brl update, possible work-arounds include: * Downloading the update with some other software and providing it as the parameter to brl update * Configuring brl update to use another Bedrock mirror. There are no obvious work-arounds for brl fetch. ==== Unmount warnings on shutdown ==== Those are harmless warnings, which are caused by Bedrock using a Linux kernel feature which propagates some mount and unmount operations, Which causes some init systems to be confused by this and show warnings about being unable to unmount directories because they were already unmounted ==== Root filesystem fsck may be skipped ==== Because of a quirk in how Bedrock works, init systems might not mount the root directory read-only in preparation for fsck, Bedrock does attempt to disable this by changing the corresponding field in <code>/etc/fstab</code> Some initrds will <code>fsck</code> the root filesystem, but not all. Bedrock should offer the option to call <code>fsck</code> on the root filesystem, but it currently does not <ref>[https://bedrocklinux.org/0.7/known-issues.html Known Issues], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> == References == <references /> 00cc9b979a6a65136021728641124154cd0670ab 0 257 4138 4031 2025-09-12T14:11:55Z DontBlameMe 281 Update the latest release wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.51.0, 2025-09-10 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor. It was originally based on [[wlroots]] but migrated away from it towards its own rendering backend library [[aquamarine]] in version 0.42.0<ref>[https://hypr.land/news/independentHyprland/ Hyprland moves off wlroots], 2025-09-02 (Accessed 2025-09-02)</ref> It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Hyprland], 2025-08-10 (Accessed: 2025-08-10)</ref> Hyprland uses its own configuration syntax, designed to be readable and easy to learn, with similarities to shell scripting. The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. * '''Hyprlock''' - a highly customizable and efficient Wayland lockscreen * '''Hyprpicker''' - a small utility for picking a color on your current screen == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway (window manager)|Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> 92fc253039ce255b4a9fde646e2b70b5d296ab9b 0 171 4139 3738 2025-09-12T14:18:55Z DontBlameMe 281 include information about Disko wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such as nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental (But mostly stable and trusted) feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Disko === [https://github.com/nix-community/disko Disko] is a NixOS module for configuring disk layouts and their partitions. It facilitates the quick and easy installation of NixOS on systems with the same disk setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org{{Dead Link|2025-08-14|Cannot connect to host save-nix-together.org:443 ssl:default [Connect call failed ('35.220.189.138', 443)]}} NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> a23f8ce96a3b2eec5049b92f6421a4177f246106 4140 4139 2025-09-12T14:20:21Z DontBlameMe 281 add missing blank line above flakes header wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such as nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental (But mostly stable and trusted) feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Disko === [https://github.com/nix-community/disko Disko] is a NixOS module for configuring disk layouts and their partitions. It facilitates the quick and easy installation of NixOS on systems with the same disk setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024) </ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org{{Dead Link|2025-08-14|Cannot connect to host save-nix-together.org:443 ssl:default [Connect call failed ('35.220.189.138', 443)]}} NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> 76368221d870247d45ab822c9b88cc6280907f5e 0 1015 4141 2025-09-12T14:54:05Z DontBlameMe 281 add page with information about the Kotlin programming language wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Kotlin Full Color Logo Mark RGB.png|frameless]] | caption = Kotlin Logo | title = Kotlin | releasestatus = Maintained | lastrelease = v2.2.20, 2025-09-10 | languages = Kotlin | developers = JetBrains | website = [https://kotlinlang.org/ kotlinlang.org] }} {{stub}} '''Kotlin''' is an open-source, statically typed programming language developed and maintained by [[JetBrains]]. It is designed to run on the [[Java Virtual Machine]] (JVM) and is also available for [[JavaScript]] and native platforms through [[Kotlin/Native]]. Kotlin is fully interoperable with [[Java]], allowing developers to use existing Java libraries and frameworks within Kotlin projects. Unlike Java, Kotlin provides more concise syntax, null safety, extension functions, coroutines for asynchronous programming, and many other modern language features. In 2017, Google announced official support for Kotlin on [[Android]] as a first-class development language, and since then it has become one of the most popular languages for Android app development. == Features == * Statically typed with type inference * Interoperability with Java * Concise syntax compared to Java * Null safety to reduce NullPointerExceptions * Coroutines for asynchronous and concurrent programming * Multi-platform support: JVM, JavaScript, and native == History == * First announced by JetBrains in 2011 * Version 1.0 released in February 2016 * Official Android support by Google announced at Google I/O 2017 * Declared the preferred language for Android development by Google in 2019 == Platforms == * [[JVM]] (Java Virtual Machine) * [[Android]] * [[Kotlin/Native]] (compilation to native code for iOS, Windows, Linux, macOS, embedded systems) * [[Kotlin/JS]] (compilation to JavaScript for running in browsers or Node.js) f47cc31d7e7d8a7b10bcd41a845400bdf2da1167 0 313 4142 3592 2025-09-12T15:48:45Z Satnus 215 Added internal link for spice wikitext text/x-wiki [[Category:Desktop Environments]] [[File:Screenshot mint 2024-07-10 05-20-47.png|thumb|Cinnamon on Linux Mint 21.3]] {{Needs Citations}} [https://github.com/linuxmint/cinnamon Cinnamon] is a desktop environment maintained by the [https://www.linuxmint.com/ Linux Mint] team. Forked from [[GNOME]] Shell, it provides the user with panels, menus, window management, hot corners, and more. The user-interface is written in [[JavaScript]], with core libraries being written in [[C]]. == Features == === Panel === Cinnamon provides a traditional desktop experience out-of-the-box, with a panel that resembles the taskbar of Microsoft Windows. Panel items — called "applets" — can be organized freely. Additional applets can be downloaded from the internet, either from the Spices website or the applet manager included with Cinnamon. === Spices === A [[Spice]] is Cinnamon's name for an add-on applet, desklet, theme, widget, and more. They can be found at the [https://cinnamon-spices.linuxmint.com/ Cinnamon Spices repository website]. == Cinnamon applications == Cinnamon uses the X-app suite, which are a set of apps forked from GNOME and changed to work across XFCE, Cinnamon and MATE. {| class="wikitable" |+The list of apps are the following: !Application !GNOME !X-apps equivalent |- |Text editor |Gedit |xed |- |Image viewer |Eye of GNOME (EoG) |xviewer |- |Image organizer |gthumb |pix |- |Media player |Totem |xplayer |- |Document editor |Atril |xreader |} == Starting Cinnamon == There are two main methods of starting Cinnamon: * Selecting "Cinnamon" from your preferred [[Display Manager]] ** If your session crashes or has graphical artifacts you should select "Cinnamon (software rendering) instead, which disables 3D acceleration * Modifying your [[Xinitrc]] to include <code>exec cinnamon-session</code> be8a7d0978f46288e1cabbc1b08c9874627715e5 0 558 4143 3742 2025-09-12T21:26:25Z ByteSlayer 282 wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[Rust]]; originally in [[OCaml]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called “garbage collecting,” where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[#Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" lines> struct MyStruct { field1: bool, field2: i32, field3: String, } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: MyStruct = MyStruct { field1: true, field2: 64, field3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height // This returns the Cube's Volume } } fn main() { let rubiks_cube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's volume: {}", rubiks_cube.volume()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an area finder function within the <code>impl Cube</code> scope. We are able to use the <code>volume()</code> method on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == 2315b7dd551a91d7ba7bfb63bf024d31ef8f682a 4144 4143 2025-09-12T21:26:52Z ByteSlayer 282 wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[Rust]] originally in [[OCaml]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called “garbage collecting,” where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[#Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" lines> struct MyStruct { field1: bool, field2: i32, field3: String, } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: MyStruct = MyStruct { field1: true, field2: 64, field3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height // This returns the Cube's Volume } } fn main() { let rubiks_cube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's volume: {}", rubiks_cube.volume()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an area finder function within the <code>impl Cube</code> scope. We are able to use the <code>volume()</code> method on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == 616af61316391dcdb76ef3eca42d2adabafcb4d1 4145 4144 2025-09-12T21:27:30Z ByteSlayer 282 wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[Rust]], originally written in [[OCaml]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called “garbage collecting,” where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[#Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. OOP allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance<ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref>.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref> Rust takes a different approach to OOP with its use of <code>structs</code>, <code>traits</code>, <code>enums</code>, and <code>impls</code> (methods).<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, Structs in Rust can store multiple related values; however, structs enable for the naming of each value within itself rather than having to deconstruct the tuple. Structs are used in Rust for making attributes more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> Below shows how structs are used in code: <syntaxhighlight lang="rust" lines> struct MyStruct { field1: bool, field2: i32, field3: String, } // Outside of the main() function, which allows it to be used anywhere // in the file! fn main() { let MasterOogway: MyStruct = MyStruct { field1: true, field2: 64, field3: String::from("Use Structs you must!"), }; } </syntaxhighlight>You can give functional properties to structs with the use of <code>impls</code>. Known as methods, having methods also allows for the reproducibility of code as it defines functions that use the values found in structs and is considered "implementations"; hence the key term being <code>impl</code>. <ref name=":0" /><ref name=":2" /><syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height // This returns the Cube's Volume } } fn main() { let rubiks_cube: Cube = Cube { Length: 3, Width: 3, Height: 3 }; println!("Cube's volume: {}", rubiks_cube.volume()) } </syntaxhighlight>The code declares a new struct with 3 values, then we implemented an area finder function within the <code>impl Cube</code> scope. We are able to use the <code>volume()</code> method on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == 1d6cc971e7ef0d46610374986428530c298f6027 4151 4145 2025-09-14T08:52:15Z Madonuko 140 tidy up wordings wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[Rust]], originally written in [[OCaml]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust, is a multi-purpose programming language (general-purpose) that tends to prioritize concurrency of tasks, type safety, and performance. Rather than taking the typical route of other programming languages: using a method called “garbage collecting,” where the program automatically frees memory, mostly prominent in programming languages such as C# or Java<ref>[https://www.techtarget.com/searchstorage/definition/garbage-collection Garbage Collection (GC)], TechTarget Robert Sheldon, May 2022 (Accessed: February 15th, 2025)</ref>, Rust enforces '''memory safety''', a way of preventing system memory being allocated incorrectly or using unnecessary amounts of memory at runtime<ref>[https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html?highlight=Memory%20Safety#memory-and-allocation What is Ownership? # Memory and Allocation], The Rust Programming Language (Accessed: February 14th 2025)</ref><ref>[https://www.embedded.com/memory-safety-in-rust/ Memory Safety In Rust], Embedded, Jacob Beningo (Accessed: February 14th, 2025.)</ref> (See [[#Memory Safety]]). Rust was heavily inspired by other programmings with its use of immutability, pattern matching, and more. It also supports Object-Orientated Programming (OOP) (See [[#Object-Orientated Programming in Rust]]). This allows for it to be used for many applications, which also includes system programming at a low-level with the use of bare-metal Rust.<ref>[https://books.google.com/books?id=eEUREAAAQBAJ Practical System Programming for Rust Developers: Build fast and secure software for Linux/Unix systems with the help of practical examples], Prabhu Eshwarla, December 24 2020 (Accessed: February 14th, 2025)</ref> Rust is used in many modern day applications because of its benefits Rust was the first programming language other than [[C]] or [[Assembly]] introduced into the [[Kernel|Linux Kernel]] in December 2022 and is still currently used today.<ref>[https://github.com/torvalds/linux Git-hub: torvalds/linux]: The Linux Kernel, Github 2025 (Accessed: February 15th, 2025)</ref> === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. [[OO]]P allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref><ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref> Rust takes a different approach to OOP with its use of <code>struct</code>s, <code>trait</code>s, <code>enum</code>s, and <code>impl</code>s.<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, <code>struct</code>s in Rust can store multiple related values as fields. The difference is that fields must be referred via their given naming. <code>struct</code>s are more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> <syntaxhighlight lang="rust" lines> // Having the struct outside of main() makes it available everywhere in the file struct MyStruct { field1: bool, field2: i32, field3: String, } fn main() { let object = MyStruct { field1: true, field2: 64, field3: String::from("Use structs you must!"), }; } </syntaxhighlight> Functional properties may be given to <code>struct</code>s with <code>impl</code>s, which stands for ''implement''. Having methods (i.e. functions in <code>impl</code> with <code>self</code>, <code>&self</code> or <code>&mut self</code> as the first parameter) also allows for reproducibility, since they can access <code>struct</code> fields via <code>self</code>. <ref name=":0" /><ref name=":2" /> <syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height } } fn main() { let rubiks_cube = Cube { length: 3, width: 3, height: 3, }; println!("Cube's volume: {}", rubiks_cube.volume()); } </syntaxhighlight> The code declares a new struct with 3 values and an area finder function within the <code>impl Cube</code> scope. The <code>volume()</code> method may be used on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == fdf7be4a4917b052ce8675c1b16c5b7153c177c0 6 1016 4146 2025-09-12T21:36:48Z ByteSlayer 282 The Go Gopher is the Official Mascot of the Go Programming Language created by Reneé French in 2009. wikitext text/x-wiki == Summary == The Go Gopher is the Official Mascot of the Go Programming Language created by Reneé French in 2009. == Licensing == {{Unknown_copyright}} 856c49e9a35aed7c54e81e3ff55b2405c2e7c090 4147 4146 2025-09-12T21:39:24Z ByteSlayer 282 ByteSlayer uploaded a new version of [[File:Go gopher.png]] wikitext text/x-wiki == Summary == The Go Gopher is the Official Mascot of the Go Programming Language created by Reneé French in 2009. == Licensing == {{Unknown_copyright}} 856c49e9a35aed7c54e81e3ff55b2405c2e7c090 6 1017 4148 2025-09-12T21:42:20Z ByteSlayer 282 The Logo of the Go Programming Language. wikitext text/x-wiki == Summary == The Logo of the Go Programming Language. == Licensing == {{Unknown_copyright}} 2c5ca79ffa759c98ea7d1bbee72467504bc70a0d 0 1018 4149 2025-09-12T21:52:08Z ByteSlayer 282 Created Go page with basic information wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:go.png|200px]] | caption = Go Logo | title = Go | releasestatus = Maintained | lastrelease = 1.25.1 | languages = [[Go]], originally written in [[C]] | developers = The Go Team; originally by RobPike, Ken Thompson, Robert Griesemer | website = [https://go.dev/ go.dev] }} a390fd8fda92ce5d9f1766da020d8adccd811adf 3000 1019 4152 2025-09-14T10:13:34Z Satnus 215 Guide for the top 3 desktop browsers, Google Chrome, Microsoft Edge, Mozilla Firefox. wikitext text/x-wiki {{Guide Warning}} {{Work In Progress}} A [https://en.wikipedia.org/wiki/Web_browser web browser] is one of the most important user facing applications. This guide shows how to install some web browsers in Linux. == [[Mozilla Firefox]] == === Using your distribution's package manager === In many distributions, Firefox comes preinstalled as the default web browser. If for any reason your distribution came without firefox, you can install it using the distribution's [[package manager]]. For example, [[Debian]] based distributions may use this command. <syntaxhighlight lang="bash"> $ sudo apt install firefox </syntaxhighlight> === Using [[flatpak]] === <syntaxhighlight lang="bash"> $ flatpak install flathub org.mozilla.firefox </syntaxhighlight> '''Note that when using flatpak, profiles are stored in ~/.var/app/org/mozilla.firefox/.mozilla, not in ~/.mozilla!''' === Using [[snap]] === <syntaxhighlight lang="bash"> $ sudo snap install firefox </syntaxhighlight> '''Note that when using snap, profiles are stored in ~/snap/firefox/common/.mozilla/firefox, not in ~/.mozilla/firefox!''' === Install from the website=== # Download the file for your architecture [https://www.firefox.com/en-US/browsers/desktop/linux/ here]. # Unzip it using either your file explorer or by running <code lang="bash">tar xvf firefox-*.tar.xz</code> # From here, you can directly execute the <code>firefox</code> binary from the unzipped folder with <code lang="bash">./firefox</code>. # (Optional) To ensure that it remains compatible, you should move the unzipped firefox folder into /opt. '''This requires root access''' # (Optional) You can arrange a symlink by <code lang="bash">ln -s path/to/firefox/firefox /usr/local/bin/firefox</code> to be able to execute it with the <code lang="bash">firefox</code> command. '''This requires root access'''. # (Optional) You can set up a desktop file (to be able to launch firefox from the start menu) by downloading [https://raw.githubusercontent.com/mozilla/sumo-kb/main/install-firefox-linux/firefox.desktop this file] (The simplest method to do so would be to run <code lang="bash">wget https://raw.githubusercontent.com/mozilla/sumo-kb/main/install-firefox-linux/firefox.desktop</code>.), and copying it into either ~/.local/share/applications (to make it available for one user) or into /usr/local/share/applications (to make it available for all users). '''If you did not follow step 4, you will need to edit the firefox.desktop file you downloaded and change line 11 to '''<code>Icon=path/to/firefox/browser/chrome/icons/default/default128.png</code>'''. If you did not follow step 5, you will need to edit the firefox.desktop file you downloaded and change line 7 to '''<code>Icon=path/to/firefox/firefox %u</code>'''.''' <ref>[https://support.mozilla.org/en-US/kb/install-firefox-linux Installing Firefox on Linux], AliceWyman, Chris Ilias, cor-el, Underpass, Tonnes, scoobidiver, Swarnava Sengupta, ideato, Mozinet, user669794, Joni, Paul, Marcelo Ghelman, YD, Shaded_ke, Rashid, Danny Colin, Mark Heijl, Angela Lazar, liam, ErlingR, PGGWriter, user3771646, unixfan, servesha, qxyz123, Roy Orbitson, Lucas Siebert, Johan Lorenzo, mysticvortexscribe, Mia SAMBATH, Alif Putra Winata, 2025 (Accessed: 2025-09-14)</ref> == [[Google Chrome]] == === Install from the website (Debian / Fedora / openSUSE based) === Go [https://www.google.com/chrome/other-platforms/ here], choose Linux for operating system and either "[[Debian]]/[[Ubuntu]]" or "[[Fedora]]/[[openSUSE]]" depending on which your distribution is based on, and download the file. If your distribution is based on Debian/Ubuntu, use [[apt]]. <syntaxhighlight lang="bash"> $ sudo apt install ./google-chrome-*_current_x86_64.deb </syntaxhighlight> If your distribution is based on Fedora/openSUSE, use <syntaxhighlight lang="bash"> $ sudo dnf localinstall ./google-chrome-*_current_x86_64.rpm </syntaxhighlight> === Install using package manager (Debian) === === Install using package manager (Fedora/openSUSE) === Firstly, in case you haven't installed third party repositories, do so. <syntaxhighlight lang="bash"> $ sudo dnf install fedora-workstation-repositories </syntaxhighlight> Then, enable the Google Chrome repository. <syntaxhighlight lang="bash"> $ sudo dnf config-manager setopt google-chrome.enabled=1 </syntaxhighlight> Finally, you can install <code>google-chrome-stable</code> (or the other included google chrome installs, such as <code>google-chrome-unstable</code>, <code>google-chrome-canary</code>, or <code>google-chrome-beta</code>) using the following command. <syntaxhighlight lang="bash"> $ sudo dnf install google-chrome-stable </syntaxhighlight> <ref>[https://docs.fedoraproject.org/en-US/quick-docs/installing-chromium-or-google-chrome-browsers/ Installing Chromium or Google Chrome Browsers :: Fedora Docs], Peter Lilley, 2021 (Accessed: 2025-09-14)</ref> == [[Microsoft Edge]] == === Install from the website (Debian) === Download Microsoft Edge [https://www.microsoft.com/en-us/edge/ here], and install it either by double clicking the file in your file manager or run the following command. <syntaxhighlight lang="bash"> $ sudo apt install ./microsoft-edge-stable_*_amd64.deb </syntaxhighlight> == References == <references/> 0d7450b857334ec92bd1817f7eb0a96143090c08 4155 4152 2025-09-14T19:42:42Z Satnus 215 Added Vivaldi and a bit of Brave. wikitext text/x-wiki {{Guide Warning}} {{Work In Progress}} A [https://en.wikipedia.org/wiki/Web_browser web browser] is one of the most important user facing applications. This guide shows how to install some web browsers in Linux. == [[Mozilla Firefox]] == === Using your distribution's package manager === In many distributions, Firefox comes preinstalled as the default web browser. If for any reason your distribution came without firefox, you can install it using the distribution's [[package manager]]. For example, [[Debian]] based distributions may use this command. <syntaxhighlight lang="bash"> $ sudo apt install firefox </syntaxhighlight> === Using [[flatpak]] === <syntaxhighlight lang="bash"> $ flatpak install flathub org.mozilla.firefox </syntaxhighlight> '''Note that when using flatpak, profiles are stored in ~/.var/app/org/mozilla.firefox/.mozilla, not in ~/.mozilla!''' === Using [[snap]] === <syntaxhighlight lang="bash"> $ sudo snap install firefox </syntaxhighlight> '''Note that when using snap, profiles are stored in ~/snap/firefox/common/.mozilla/firefox, not in ~/.mozilla/firefox!''' === Install from the website=== # Download the file for your architecture [https://www.firefox.com/en-US/browsers/desktop/linux/ here]. # Unzip it using either your file explorer or by running <code lang="bash">tar xvf firefox-*.tar.xz</code> # From here, you can directly execute the <code>firefox</code> binary from the unzipped folder with <code lang="bash">./firefox</code>. # (Optional) To ensure that it remains compatible, you should move the unzipped firefox folder into /opt. '''This requires root access''' # (Optional) You can arrange a symlink by <code lang="bash">ln -s path/to/firefox/firefox /usr/local/bin/firefox</code> to be able to execute it with the <code lang="bash">firefox</code> command. '''This requires root access'''. # (Optional) You can set up a desktop file (to be able to launch firefox from the start menu) by downloading [https://raw.githubusercontent.com/mozilla/sumo-kb/main/install-firefox-linux/firefox.desktop this file] (The simplest method to do so would be to run <code lang="bash">wget https://raw.githubusercontent.com/mozilla/sumo-kb/main/install-firefox-linux/firefox.desktop</code>.), and copying it into either ~/.local/share/applications (to make it available for one user) or into /usr/local/share/applications (to make it available for all users). '''If you did not follow step 4, you will need to edit the firefox.desktop file you downloaded and change line 11 to '''<code>Icon=path/to/firefox/browser/chrome/icons/default/default128.png</code>'''. If you did not follow step 5, you will need to edit the firefox.desktop file you downloaded and change line 7 to '''<code>Icon=path/to/firefox/firefox %u</code>'''.''' <ref>[https://support.mozilla.org/en-US/kb/install-firefox-linux Installing Firefox on Linux], AliceWyman, Chris Ilias, cor-el, Underpass, Tonnes, scoobidiver, Swarnava Sengupta, ideato, Mozinet, user669794, Joni, Paul, Marcelo Ghelman, YD, Shaded_ke, Rashid, Danny Colin, Mark Heijl, Angela Lazar, liam, ErlingR, PGGWriter, user3771646, unixfan, servesha, qxyz123, Roy Orbitson, Lucas Siebert, Johan Lorenzo, mysticvortexscribe, Mia SAMBATH, Alif Putra Winata, 2025 (Accessed: 2025-09-14)</ref> == [[Google Chrome]] == === Install from the website (Debian / Fedora / openSUSE based) === Go [https://www.google.com/chrome/other-platforms/ here], choose Linux for operating system and either "[[Debian]]/[[Ubuntu]]" or "[[Fedora]]/[[openSUSE]]" depending on which your distribution is based on, and download the file. If your distribution is based on Debian/Ubuntu, use [[apt]]. <syntaxhighlight lang="bash"> $ sudo apt install ./google-chrome-*_current_x86_64.deb </syntaxhighlight> If your distribution is based on Fedora/openSUSE, use <syntaxhighlight lang="bash"> $ sudo dnf localinstall ./google-chrome-*_current_x86_64.rpm </syntaxhighlight> === Install using package manager (Debian) === === Install using package manager (Fedora/openSUSE) === Firstly, in case you haven't installed third party repositories, do so. <syntaxhighlight lang="bash"> $ sudo dnf install fedora-workstation-repositories </syntaxhighlight> Then, enable the Google Chrome repository. <syntaxhighlight lang="bash"> $ sudo dnf config-manager setopt google-chrome.enabled=1 </syntaxhighlight> Finally, you can install <code>google-chrome-stable</code> (or the other included google chrome installs, such as <code>google-chrome-unstable</code>, <code>google-chrome-canary</code>, or <code>google-chrome-beta</code>) using the following command. <syntaxhighlight lang="bash"> $ sudo dnf install google-chrome-stable </syntaxhighlight> <ref>[https://docs.fedoraproject.org/en-US/quick-docs/installing-chromium-or-google-chrome-browsers/ Installing Chromium or Google Chrome Browsers :: Fedora Docs], Peter Lilley, 2021 (Accessed: 2025-09-14)</ref> == [[Microsoft Edge]] == === Install from the website (Debian) === Download Microsoft Edge [https://www.microsoft.com/en-us/edge/ here], and install it either by double clicking the file in your file manager or run the following command. <syntaxhighlight lang="bash"> $ sudo apt install ./microsoft-edge-stable_*_amd64.deb </syntaxhighlight> == [[Vivaldi]] == === Install from the website (Debian / Fedora / openSUSE === Get the installation package from [https://vivaldi.com/download/ here] and run the install command on it depending on your package manager. For Debian & Debian based distros: <syntaxhighlight lang="bash"> $ sudo apt install ./vivaldi-stable_*.deb </syntaxhighlight> For Red Hat, Red Hat based, openSUSE or openSUSE based distributions: <syntaxhighlight lang="bash"> $ sudo dnf localinstall vivaldi-stable_*.rpm </syntaxhighlight> === Using [[Snap]] === <syntaxhighlight lang="bash"> $ sudo snap install vivaldi </syntaxhighlight> <ref>[https://snapcraft.io/vivaldi Download Vivaldi | Vivaldi Browser], Vivaldi, 2025 (Accessed: 2025-09-14)</ref> === Using [[Flatpak]] === <syntaxhighlight lang="bash"> $ flatpak install flathub com.vivaldi.Vivaldi </syntaxhighlight> == [[Brave]] == The simplest method that is most likely to work for most distributions is to run the install script provided by Brave. <syntaxhighlight lang="bash"> curl -fsS https://dl.brave.com/install.sh | sh </syntaxhighlight> == References == <references/> d5a8b293f73deccad0f5e98619ee01ca8fcf8c37 0 277 4153 3671 2025-09-14T13:43:53Z Polymo1 275 Added citation for RESF business type wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_Logo.png|thumb]] | caption = Rocky Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[Category:Linux Distributions]] [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] Rocky Linux is a Linux distribution developed by RESF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit".<ref>{{Cite|url=https://www.resf.org/faq/is-resf-nonprofit|title=Is the RESF a non-profit? - RESF FAQ|author=RESF|accessdate=14 September 2025}}</ref> It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. f100235c0ce22ad02dbd321b1b47f57dd9589933 2 1020 4154 2025-09-14T13:45:46Z Polymo1 275 Created page with "== yo == you're probably better off looking at my website https://wesbryie.com" wikitext text/x-wiki == yo == you're probably better off looking at my website https://wesbryie.com 1686c7351e289ffec177c745d57a96e305524e41 0 769 4156 3504 2025-09-15T09:29:26Z Hog 161 added links wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | '''Weston<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref>''' || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | '''Mutter<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref>''' || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | '''KWin<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | '''[[Sway]]''' || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | '''[[Hyprland]]''' || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | '''river<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref>''' || None (tiling) || [[zig]]|| Lightweight and minimal tiling compositor focused on simplicity. |- | '''wayfire<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref>''' || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | '''Cage<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref>''' || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | '''[[Niri]]''' || None (scrolling/tiling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |Cosmic-comp<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |Cosmic |Rust |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |labwc<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |C |A Stacking/Floating Wayland compositor inspired by Openbox. |- | '''dwl<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref>''' || None (tilling) || C || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 68efcd258ceb2f509cf23638289f549a40c71769 3001 1021 4157 2025-09-15T22:02:30Z Osama 266 /* MORE */ new section wikitext text/x-wiki == MORE == vro add zen browser, librewolf and others.. + also add commands for pacman, dnf and AUR [[User:Osama|Osama]] ([[User talk:Osama|talk]]) 22:02, 15 September 2025 (UTC) daa9f06530dc13a5700c81b0324111d8956c561d 3000 914 4158 4132 2025-09-16T07:25:33Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Guide Warning}} {{cleanup}} {{Needs Citations}} = Checking the Boot Mode = [[File:CheckUEFI-1.png|right|frameless]] [[File:CheckUEFI-2.png|right|frameless]] There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> → Your system is using UEFI mode. #* If the value is <code>Legacy</code> → Your system is using Legacy BIOS mode. It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. '''This guide is specifically for UEFI mode to ensure maximum compatibility and stability.''' = Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|center]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|center]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' → This is a GPT disk. #* If it says '''Master Boot Record''' → This is an MBR disk. The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data''') or use a separate physical disk. '''This guide is specifically for the GPT scheme to ensure full compatibility with UEFI boot.''' [[File:CheckGPT-2.png|center]] ---- = Preparing a Partition on the Disk for Arch Linux = Before leaving the Disk Management tool, we need free space to install Arch on. * If you have an unused partition, you can delete it. * If you want to shrink the Windows partition itself, follow these steps: == How to shrink the Windows partition: == # From within Disk Management, right-click the <code>C:\</code> partition. Choose from the menu: <code>Shrink Volume</code>[[File:ShrinkPartition-1.png|center]] # In the new window, enter the amount of space you want to shrink (in '''Megabytes'''), then press OK and wait until the free space appears in black (Unallocated). [[File:ShrinkPartition-2.png|center]] # Now you have free space to install Arch. The disk layout will look like this if you shrunk Windows: [[File:FinalPartitionLayout-Shrinked.png|center]]<br>Or like this if you deleted another non-Windows partition:[[File:FinalPartitionLayout-Replaced.png|center]] ---- = Downloading the Arch Linux ISO = You need to [https://archlinux.org/download/ download] the latest ISO file which contains the live environment of Arch Linux, so we can put it on a USB drive and boot into the live environment.[[File:ArchDownload.png|left]] ---- = Preparing the USB Drive to Boot the Live Environment = We need a USB flash drive to install the Arch live environment, this tutorial use the [[Ventoy]] tool because it is the easiest and most flexible. == Why Ventoy? == * Installation is done only once. * You can then copy any number of ISO files to the flash drive. * It supports multiple operating systems on the same USB. * No need to reformat every time (unlike Rufus). '''Warning:''' Using Ventoy or Rufus will completely format the flash drive. '''All data will be deleted''', make sure to back up any important files on the drive before proceeding. == Steps to download Ventoy: == # Download Ventoy from the official website or directly from SourceForge: #* [https://sourceforge.net/projects/ventoy/files/v1.1.05/ventoy-1.1.05-windows.zip/download Download version 1.1.05 from SourceForge] #* [https://www.ventoy.net/en/index.html Official Ventoy Website] [[File:VentoyDownload.png|left]] [[File:VentoyDownload-2.png|center]] # After downloading, you will get a compressed <code>.zip</code> file. Extract it, then open the <code>Ventoy2Disk.exe</code> file. [[File:VentoyInstall-1.png|center]] == How to install Ventoy on the USB drive == After opening <code>Ventoy2Disk.exe</code>, connect the USB drive to a USB port. Make sure the program recognized the drive and shows its name in the Device field. [[File:VentoyInstall-2.png|center]] == ⚙️ Customizing Ventoy settings before installation == # Disable Secure Boot support<br>Click '''Option''' at the top left of the screen → Select '''Secure Boot Support''' to deactivate it.[[File:VentoyInstall-3.png|center]] # Specifying the disk partition type:<br>From the '''Options''' menu → Select '''Partition Layout''' → Select '''GPT'''<br>Because the MBR system, as mentioned earlier, is not recommended for installing Linux in a Dual Boot scenario. [[File:VentoyInstall-4.png|center]] # Customizing partition configuration: #*From the '''Options''' menu → Select '''Partition Configuration'''[[File:VentoyInstall-5.png|center]] #*And in the first option within the new window:<br>'''File System for Ventoy Partition''' → Select '''FAT32''' → Then press '''OK'''[[File:VentoyInstall-6.png|center]] === Optional note: === If the flash drive is large (64GB or more), you can keep part of it unused by Ventoy. * Enable the option '''Preserve some space at the end of the disk''' * Specify the desired size to remain unallocated * This space will appear as "Unallocated" inside disk tools (just like we left free space for Arch in Disk Management) == Installing Ventoy == Press '''Install''', then agree to the warnings, and wait for the process to complete. [[File:VentoyInstall-7.png|center]] Upon successful installation, you will see a confirmation message. Now copy the Arch ISO file to the partition named <code>Ventoy</code> in your file manager. [[File:VentoyInstall-8.png|center]] ---- '''Your USB flash drive is now ready to boot into the Arch live environment 🎉.''' ---- = Booting into the Live Environment = == Preparing the Boot Process == To boot into the Arch live environment, you must boot from the USB drive where we installed '''Ventoy''' and copied the ISO file. == The easiest way to boot without entering the BIOS == This method doesn't even require entering the BIOS/Firmware settings: # Restart the system, but '''hold down the Shift key''' while clicking Restart. # If you see a "Please wait" message instead of "Restarting", you are on your way to Recovery mode. == In Recovery mode == You will see a list of options, select <code>Use a device</code>, then choose the name of the USB drive where you installed Ventoy (usually the name that appeared in Ventoy). [[File:BootArch.png|center]] == ❗ If the 'Use a device' option is not available == This method might not appear on some devices, and here you must rely on the '''Boot Menu''' key during startup. Search online according to your device type or motherboard model (e.g., <code>Asus boot menu key</code> or <code>HP boot from USB</code>). == The Ventoy Menu == After booting from the USB, you will see the Ventoy menu. Select the Arch Linux ISO file from it, then press Enter twice. ---- == Starting the Live Environment == After a moment, you will see a menu with a black background – select the first option to boot into the normal mode of the live environment. [[File:ArchBoot.png|center]] ---- == Live Environment Font == If the default font in the live environment is unclear or too small, you can change it to a larger, clearer font using the following command: setfont ter-132n The font will change from this: [[File:ArchFontBefore.png|center]] To this: [[File:ArchFontAfter.png|center]] == Notes on available fonts: == The Arch live environment comes with several pre-installed fonts; you can choose the most suitable one based on your screen size and resolution. Here are some good options: * <code>setfont ter-132n</code><br>Large and clear font, excellent for small screens. * <code>setfont ter-128n</code><br>Similar but slightly smaller than <code>132n</code>. * <code>setfont ter-v32b</code><br>A '''Bold''' version of the font in a huge size, excellent for low-resolution screens. * <code>setfont lat9w-16</code>The default font in many distributions, suitable but smaller than others. ---- = Connecting to the Internet = === Ethernet cable users === If you are connected via an Ethernet cable (LAN), the internet should work automatically a few moments after connecting. To check the connection, try the following command: ping google.com You can replace <code>google.com</code> with any other website. If you start seeing messages like: 64 bytes from ... icmp_seq=2 time=23.3 ms The internet is working successfully! However, if you see a message like: ping: google.com: Temporary failure in name resolution It means the internet connection is not active. === Note: === The <code>ping</code> tool might not work sometimes depending on your ISP or local settings. Therefore, there is a practical alternative to check: pacman -Sy This command synchronizes the package databases. If you see the message: :: Synchronizing package databases... This means your internet is working correctly. == Wi-Fi users == [[File:Iwctl-1.png|right|frameless]] In the Arch live environment, there is a built-in tool for managing wireless networks called <code>iwctl</code>. To start the tool: iwctl Note: The error shown in the image is due to screen resolution in the virtual machine; this likely won't happen on real hardware. # Find the name of your Wi-Fi device:<pre>device list</pre>The network device name will appear, like <code>wlan0</code>. # Scan for nearby networks:<syntaxhighlight> station wlan0 scan station wlan0 get-networks </syntaxhighlight>(Replace <code>wlan0</code> with your actual device name if different.) # Connect to the network: #* If the network is visible:<syntaxhighlight>station wlan0 connect 'SSID'</syntaxhighlight> #* If the network is hidden:<syntaxhighlight>station wlan0 connect-hidden 'SSID'</syntaxhighlight> :(Replace <code>'SSID'</code> with your network name.) :After entering the command, you will be prompted for the password, then type <code>exit</code> to leave <code>iwctl</code>. == Verifying internet access after connecting to Wi-Fi == You can use: ping google.com or: pacman -Sy If you see the message <code>:: Synchronizing package databases...</code>, the internet connection is working successfully. ---- = Disks in Linux = == Disk Naming in Linux == Disk naming in Linux is different from Windows. For example, you might see a path like: /dev/sda2 === Explanation of parts: === ;<code>/dev</code> : This is the folder containing all system devices, like disks, network cards, etc. : <code>dev</code> is short for '''device'''. ;<code>sda</code> :This is the name of the first disk. Linux starts naming disks with letters: :* <code>sda</code>: First disk :* <code>sdb</code>: Second disk :* <code>sdc</code>: Third... and so on. === Note: === Disk naming may vary depending on the device type: * '''SATA / IDE disks:''' *:<code>/dev/sdXY</code> *:Example: <code>/dev/sdb2</code> → Second disk, partition number 2. * '''NVMe disks (modern):''' *:<code>/dev/nvmeXnYpZ</code> *:Example: <code>/dev/nvme0n1p3</code> → First NVMe disk, third partition. * '''Virtual disks (Virtual Machines):''' *:<code>/dev/vdXY</code> *:Example: <code>/dev/vda1</code> → First virtual disk, first partition. == Partitioning the Disk for Arch Linux Installation ⚙️ == You can view all connected disks using the <code>lsblk</code> command, which shows you the disks, their sizes, the partitions inside them, and their mount points if any. This helps you identify the correct disk on which to install Arch. If you allocated free space earlier while in Windows (Shrink), you will see this space here without a name or mount point. [[File:Lsblk.png|center]] == Opening the cfdisk tool for disk partitioning == <code>cfdisk</code> is a simple graphical tool that works in the terminal, helping you partition disks easily. To run it: cfdisk /dev/sda Replace <code>/dev/sda</code> with the disk containing the free space or the one you want to install Arch on. Make sure to write the correct disk name from the <code>lsblk</code> output. == disk partitioning == This is the <code>cfdisk</code> interface – it's a '''TUI''' type, operated with arrow keys and simple selections without typing commands. == Partitioning the Free Space == As you can see in the cfdisk tool, you will find Free Space at the end of the partitions. This is the same free space we left earlier in Disk Management inside Windows, which appeared in black and was called Unallocated. == Controlling the cfdisk tool: == You can navigate between existing partitions on the disk using the Up and Down arrows. You can navigate between the tools (like: New, Delete, Write...) at the bottom of the screen using the Left and Right arrows. == To start partitioning the free space: == Use the Down arrow until you reach Free Space. You will notice that the tools at the bottom of the screen have changed, because the available operations for free space are different from existing partitions. [[File:Cfdisk-2.png|center]] == System Partitioning: == To install the Arch system, we need at least two partitions: * A partition for the bootloader – this partition contains the files that allow you to choose between operating systems when starting the device. * The root partition (/ or root) – this is the main partition where all Arch Linux system files are installed. === What size for each partition? === * Boot partition: We allocate a maximum of 1G for it. This is more than enough. * Root partition: We use the remaining available space for it. Preferably at least 30 gigabytes, and the more space the better, especially if you will install a graphical environment and multiple applications. === Creating the Boot partition === * In the cfdisk tool, select the Free Space using the arrow keys. * Choose New from the options at the bottom, and press Enter. * A window will appear asking for the partition size. Erase the existing number, then type: 1G ← Then Enter.[[File:Cfdisk-3.png|center]] *The first partition, the boot partition, will be created.[[File:Cfdisk-4.png|center]] === Creating the Root partition === After finishing creating the boot partition, we move directly to creating the second partition, the root partition. * Select the remaining Free Space using the arrow keys. * Choose New from the options at the bottom of the screen, then press Enter. * This time you don't need to adjust the partition size, as the tool will automatically suggest using all the remaining space. Just press Enter to confirm. [[File:Cfdisk-5.png|center]] === Confirming changes and writing partitions to the disk === When using cfdisk and creating partitions, the changes are not applied directly to the disk. They are temporarily saved in memory until you manually confirm them. * After creating the required partitions (boot and root), move to select Write from the toolbar at the bottom. [[File:Cfdisk-6.png|center]] * A warning question will appear:<pre>Are you sure you want to write the partition table to disk?</pre>If you are sure of the changes, type yes in lowercase letters (Pay attention to case sensitivity), then press Enter.[[File:Cfdisk-7.png|center]] * With this, the changes have been physically written to the disk and the partitions have been successfully created. === Verifying the new partitions: === After executing the previous step and seeing the message: <code>The partition table has been altered</code> The new partitions have been successfully saved [[File:Cfdiskfinal.png|center]] Now make sure to note the names of the two partitions you created: * The first partition (size 1G) is the bootloader partition. * The second partition (the remaining space) is the root partition. After verifying, choose Quit from the cfdisk toolbar to exit the tool and return to the live environment. To verify the partition names again after exiting the <code>cfdisk</code> tool, use the command: lsblk It will show you all disks and partitions, and you can identify the two partitions based on their size. == Formatting the Partitions == Before mounting the partitions to their paths, they must first be formatted with suitable filesystems. In our case, we will use: * FAT32 for the bootloader partition * EXT4 for the root / partition But why choose these two systems specifically? === Why FAT32 for the boot partition? === The boot system (like GRUB) relies on having .efi files in a special partition that the Firmware (BIOS/UEFI) can read directly. This is where FAT32 comes in, because: * It is the only filesystem that UEFI can read without any intermediaries. * It does not contain complex permissions or modern features that hinder UEFI. * It is used by most operating systems (even Windows) in boot partitions because it is simple and universally readable. === Why EXT4 for the root / partition? === The root partition contains the entire operating system, so it needs a modern filesystem that supports: * File permissions: To determine who has the right to read, execute, or modify each file. * Symbolic links (Symlinks): These are fundamental to the Linux system (like /dev/null or /bin/sh). * Large files: FAT32 does not support files larger than 4GB, while EXT4 supports huge sizes. * Journaling: Helps protect files from corruption in case of sudden power loss or unexpected reboots. To format the bootloader partition, we write the following command: mkfs.fat -F32 /dev/sda5 Replace /dev/sda5 with the actual name of the boot partition. === Quick explanation: === * <code>mkfs</code> = Make File System = Create a filesystem. * <code>fat</code> is the type of system. * <code>-F32</code> means we use FAT32 (not FAT16 or others). * <code>/dev/sda5</code> is the partition we created for boot (1GB). Make sure you use FAT32 only for the boot partition! Make sure to use the correct partition name when executing the command. [[File:Mkfs-1.png|center]] As for formatting the root partition, we use the following command: mkfs.ext4 /dev/sda6 Replace /dev/sda6 with the actual name of the root partition. The EXT4 system is optimal for the root: stable, modern, supports all the Linux features you need. [[File:Mkfs-2.png|center]] Now that we've finished formatting, we're ready to move on to the mounting step! ---- == Mounting the Partitions == After creating the system partitions, we need to mount them in locations known as Mount Points, so the system can access the files inside each partition. In our case — since the disk uses GPT and UEFI boot — we will mount two main partitions: === First partition: Root / === The root / is the heart of the system; almost everything falls under it: files, directories, and even physical devices like disks appear as files inside /dev. To mount the root, we use the command: mount /dev/sda6 /mnt Replace <code>/dev/sda6</code> with the actual name of your root partition. Here <code>/mnt</code> is the temporary mount location in the live environment, and it will become the base of the new Arch filesystem. To ensure the mount was successful, run <code>lsblk</code> and make sure <code>/mnt</code> appears next to the root partition. [[File:Mount-1.png|center]] === Second partition: The boot partition /boot/efi === This partition is essential for the boot system, and since the root is mounted inside <code>/mnt</code>, we must also mount the boot partition inside it, specifically at: <code>/mnt/boot/efi</code> But these folders won't be readily available in the live environment, so we need to create them manually. We use the mkdir command (short for Make Directory) with the -p option to create all the missing folders along the path at once: mkdir -p /mnt/boot/efi The -p option means: If the folders in the path don't exist, create them all without any error. Then we mount the boot partition: mount /dev/sda5 /mnt/boot/efi And as usual, replace /dev/sda5 with the actual name of your boot partition. If everything is good, we start moving to the system installation step! ---- == Installing the System == To install the basic packages like the Linux kernel and Arch system files, we use the <code>pacstrap</code> tool. But... isn't <code>pacman</code> the package manager in Arch? : Yes! But each tool has its specific function during installation, and the difference between them at this stage is very important. ;pacman :The primary package manager in Arch Linux. :Used after installation to manage software on the installed system. Always installs packages onto the current system (the current root /). ;pacstrap :A special tool used during installation from the live environment. :Installs packages onto a specified path — usually /mnt — instead of the live system. :Its function is to prepare the root partition with basic system packages, such as: :*The Linux kernel :*The package manager <code>pacman</code> itself! :* Networking tools :* System files == Installing the base packages == We use the following command to install the basic system inside the new root partition <code>/mnt</code>: pacstrap /mnt base linux linux-firmware But why these specific packages?! And what does each one do? === base === The base package containing everything the system needs to function. 🔍 Includes: * Basic command-line tools like sh, ls, cp, mv, mkdir... * Standard system directories like /etc, /usr, /bin, /var * Default Shell (bash) * Important scripts that aid in booting === linux === This is the system kernel itself. * Directly interacts with the device hardware and manages communication between it and the software. In short, it is the brain and backbone of the system! === linux-firmware === A large collection of important firmwares for running device components. 🧬 Includes: * Drivers for Wi-Fi and Bluetooth cards * Support for Intel and AMD processors * Support for graphics cards * Support for sound cards and disks ---- = Generating the fstab file = After installing the system in the /mnt path, we need to make the system know how to mount the partitions (Mount Points) automatically every time it boots. This is exactly the job of the fstab file. == Generating fstab automatically == To generate the file easily, we use this command: genfstab -U /mnt >> /mnt/etc/fstab Explanation of command components: * <code>genfstab</code>: Short for "Generate File System Table" * <code>-U</code>: Makes it use UUID identifiers instead of disk names * <code>/mnt</code>: Is the root of the new system we installed * <code>>></code>: Means append the output to the file <code>/mnt/etc/fstab</code> == Entering the new system's root == We can use the command: arch-chroot /mnt The arch-chroot tool allows us to enter the new system and control and modify it instead of modifying the live environment. [[File:Arch-chroot.png|center]] After entering the system using <code>arch-chroot</code>, we begin installing a set of basic packages that we need to set up the system comfortably and make it ready to boot. We use the following command pacman -Sy sudo nano grub efibootmgr os-prober networkmanager [[File:Pacman.png|center]] = Installing the GRUB Bootloader = === After installing the packages: grub, efibootmgr, and os-prober, we can start the bootloader installation process. === == Modifying GRUB settings: == The file responsible for GRUB settings is located at the following path: <code>/etc/default/grub</code> We edit it using the nano text editor we installed: <code>nano /etc/default/grub</code> === Steps inside the file === ==== Modify the GRUB_TIMEOUT option ==== This is the duration (in seconds) that GRUB waits before booting the default option (usually Arch Linux). Change the default value (usually 5) to something longer like 10 or 15 so you have time to choose the system. [[File:Grub-conf.png|center]] ==== Enable the os-prober tool ==== Scroll down to the end of the file, and you will see a line like this: #GRUB_DISABLE_OS_PROBER=false All you need to do is remove the # sign to activate the feature, so it becomes: GRUB_DISABLE_OS_PROBER=false [[File:Grub-conf_1.png|center]] 🎯 This allows GRUB to detect Windows and add it to the menu automatically. After editing, save and exit nano: Ctrl + X → then y → then Enter ---- === 📦 Mounting Windows' boot partition: === Now we need to mount Windows' boot partition, usually it's the first partition on the same disk where Windows is installed, like: /dev/sda1 We mount it with this command: mount /dev/sda1 /boot/efi ✅ Note that we write /boot/efi directly (without /mnt) because we are now inside the new system itself. === 💡 What if an error appears that /boot/efi does not exist? === 📦 Simple! We need to create the folder manually: <code>mkdir /boot/efi</code> Note that we don't need to write -p because the /boot folder already exists (from the base package), all we're missing is the efi folder. Then mount the partition again: <code>mount /dev/sda1 /boot/efi</code> [[File:Os-prober-1.png|center]] === 🎯 Now after mounting the partition, let's test the os-prober tool: === Execute: <code>os-prober</code> [[File:Os-prober.png|center]] == 🚀 And now we start installing GRUB! == === 🔧 The first step is to install the bootloader itself into the EFI partition, we use the following command: === <code>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB</code> Here's an explanation of each part of this command: <code>grub-install:</code> is the script responsible for installing the GRUB bootloader. <code>--target=x86_64-efi</code>: Specifies that we want to install GRUB for UEFI system (not Legacy), for 64-bit processors. <code>--efi-directory=/boot/efi</code>: This is the folder containing the .efi files, the partition we mounted a moment ago (Windows boot partition). <code>--bootloader-id=GRUB</code>: The name that will appear in the BIOS/UEFI boot menu, you can change it to anything you like. ✅ If you see the message: "Installation Finished. No error reported" Then everything is fine, and congratulations, you now have GRUB installed and ready. [[File:Grub-install.png|center]] ---- == 🧠 Generating the GRUB configuration file == Now after installing GRUB, we need to generate its configuration file and the list of available systems. This file is responsible for showing the boot menu at every startup. We use the following command: grub-mkconfig -o /boot/grub/grub.cfg Explanation of parts: * <code>grub-mkconfig</code>: is the command responsible for generating the configuration file. * <code>-o</code>: means "Output", i.e., where to save the output file. * <code>/boot/grub/grub.cfg</code>: This is the default path for the file that GRUB reads the menu from during boot. === ⚙️ What happens after executing grub-mkconfig? === When you execute the command, you will see several messages appear in front of you, and by numbering the events in the screenshot in front of you, you understand: 1: Notification of starting the configuration file generation. 2 - 3 - 4: Finding the boot files for the Arch Linux kernel. 5 - 6: Warnings about starting <code>os-prober</code> and searching for other systems. 7: Finding Windows boot files and adding Windows to the GRUB menu. 8: Updating the GRUB menu and re-adding it to the UEFI BIOS boot options. 💥 And all this happened automatically without your intervention, and if things went without errors, you have officially finished installing the bootloader. [[File:Grub-mkconfing.png|center]] ---- = 👤 Creating a new user = After installing the system and GRUB, it's better to create a regular user instead of relying on the root user all the time. To create a new user we write the following command: useradd -m -G wheel -s /bin/bash username Replace <code>username</code> with the name you want for the new user. == 🔍 What does this command do? == * <code>useradd</code>: The command responsible for creating the user. * <code>-m</code>: Creates the home directory automatically in /home/username. * <code>-G wheel</code>: Adds the user to the wheel group, which is a special group for users who can use sudo. * <code>-s /bin/bash</code>: Specifies the default shell, i.e., the command interface (here we chose Bash). [[File:Useradd.png|center]] ---- = 🔐 Setting passwords = === System security is important, so we must set passwords for the root user and the new user. === Setting the root password: passwd Just type the command and it will ask you to enter the root password twice, since we are currently in the root user. If a message appears: password updated successfully [[File:Passwd.png|center]] Then you're good. Setting the password for the new user: passwd username Replace <code>username</code> with the name of the user you created a moment ago. [[File:Passwd-.png|center]] ---- = 🛡️ Enabling sudo privileges for the wheel group = Since Arch does not enable sudo automatically (the evidence is that we installed the <code>sudo</code> package manually), we need to modify its configuration file manually using the command: EDITOR=nano visudo [[File:Visudo-1.png|center]] It will open the sudo configuration file with the nano editor instead of vim. [[File:Visudo.png|center]] Scroll down until you reach this line: # %wheel ALL=(ALL:ALL) ALL [[File:Visudobefore.png|center]] What do you do? Remove the # sign from the beginning, so it becomes like this: %wheel ALL=(ALL:ALL) ALL [[File:Visudoafter.png]] ✨ Now the user in the wheel group can use sudo. To save changes and exit nano, press {{Keypress|Ctrl|X}}{{Keypress|Y|Enter|chain=}} ---- = 🖥️ Setting the device name (Hostname) = The hostname is what appears to you in the command line and is very useful for networks. To set the name: echo 'ArchBox' > /etc/hostname [[File:Hostname.png|center]] Replace ''ArchBox'' with any name you want. = 🔗 Linking the name with the network (Optional but preferred) = Open the hosts file with the command: nano /etc/hosts [[File:Etchosts_before.png|center]] After it opens, add this line: 127.0.1.1 ArchBox.localdomain ArchBox Replace ''ArchBox'' with the name you wrote in the previous step. [[File:Etchosts_after.png|center]] ---- = 🌐 Enabling the Network Manager = Since you installed the NetworkManager package, you now need to enable its service to start automatically at boot. Execute this command: systemctl enable NetworkManager Just make sure you wrote the name correctly, with the exact case. ---- = 🎯 Installing a Desktop Environment and Login Manager = Now that we've reached the end of the installation, it's time to add the "graphical interface" so you can use the system like a human; you surely won't live in the tty, my friend 🤕. There are two of the easiest and most popular environments, each with a compatible login manager, so choose the one you prefer 👇 = 🌿 Option One: GNOME + GDM = == If you want a sleek, smooth interface, perfectly suited for laptops, then GNOME is the golden choice. == To install it, run this command: pacman -S gnome gnome-extra gdm And then enable the login manager: systemctl enable gdm 🟢 Info: <code>gnome-extra</code> adds tools like calendar, maps, and advanced settings, but if you want a smaller footprint, you can remove it and just use gnome. = 💎 Option Two: KDE Plasma + SDDM = If you want a very beautiful and highly customizable interface, and love effects and many options, take KDE without thinking. Execute the following command: pacman -S plasma kde-applications sddm Then enable the login manager: systemctl enable sddm 🟣 Info: If you want a lightweight KDE, you can remove <code>kde-applications</code> and install only plasma, giving you the interface without their many applications. ---- = 🧼 Finishing the installation and rebooting = Great, we installed the environment and login manager and finished everything, now we need to exit the installation environment and reboot. First, exit chroot: exit You will return to the live environment (USB). Now unmount the partitions we mounted: umount -R /mnt And finally... the awaited moment 🎉: reboot After rebooting, if everything is fine, you will see the GRUB menu with: Arch Linux Windows 🔥 Choose Arch and enter your system for the first time, log in with your login manager, and explore the desktop environment you chose! [[File:Grub.png|center]] Congratulations on your First Dual Booting experience, thank you for reading. 326e79061227d869a859a7515bec89a5a5732ab0 3000 639 4159 3484 2025-09-16T07:25:58Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Guide Warning}} == Formatting a partition to ext4 == Assuming the partition you want to format is called /dev/sdX, do: <pre> mkfs -t ext4 /dev/sdX # or mkfs.ext4 /dev/sdX </pre> The e2fsprogs package must be installed. == Setting mount options == You can set mount options for ext4 either by modifying <code>/etc/fstab</code> or <code>tune2fs</code><ref>[https://linux.die.net/man/8/tune2fs <span style="color:#fc493b">https://linux.die.net/man/8/tune2fs <sup>🍣403]</ref> For example, to enable <code>noatime</code> on your filesystem, do: <pre> tune2fs -o noatime /dev/sdX </pre> == Using an external journal == Ext4 allows you to use an external journaling device paired with a partition that actually stores your data. To create a **new** partition with an external journal at /dev/sdb2, do: <pre> mkfs.ext4 -F -O journal_dev -b 4096 /dev/sdb2 mkfs.ext4 -F -J device=/dev/sda1 -b 4096 /dev/sdb2 </pre> To convert a pre-existing filesystem, do: <pre> mkfs.ext4 -O journal_dev /dev/sdb2 tune2fs -J device=/dev/sdb2 /dev/sda1 </pre> == Feature flags == Ext4 has tons of feature flags that can be enabled using the <code>tune2fs</code> utility, a list of them can be found [https://man7.org/linux/man-pages/man5/ext4.5.html here]. To enable a feature flag, do: <pre> tune2fs -O flag /dev/sdX </pre> Some common feature flags used often are <code>encrypt</code> and <code>fast_commit</code>. == References == <references /> e373378c9e5bcb7c71766eeafe91b59c140b341d 3000 706 4160 3825 2025-09-16T07:26:08Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki == Arch-based systems == To install the '''budgie''' package group, which includes first-party applications such as a screensaver, execute <code>sudo pacman -S budgie</code>. Alternatively, <code>sudo pacman -S budgie-desktop</code> will install the standalone desktop. Recommended optional packages include the Arc GTK theme, the Papirus icon theme, and the Network Manager applet. Executing <code>sudo pacman -S arc-gtk-theme papirus-icon-theme network-manager-applet</code> will install them. == Fedora Linux == [[Fedora]] has a [https://fedoraproject.org/spins/budgie/ spin] with Budgie Desktop instead of GNOME. == Ubuntu == There is a [https://ubuntubudgie.org/ community ISO] that contains [[Ubuntu]] with Budgie Desktop instead of GNOME. == Void Linux == <code>sudo xbps-install budgie-desktop</code> == OpenSUSE == Budgie can be selected during the OpenSUSE installation or installed afterward using <code>sudo zypper install budgie-desktop</code>. e4c8df0ac613bc210b7e4a2362d17dfd29910347 3000 695 4161 3827 2025-09-16T07:26:18Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki ==== On [[Debian]] and Debian-based distributions: ==== You can sometimes install using a software manager, such as [[synaptic]].<syntaxhighlight lang="bash"> $ sudo apt install i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo apt install i3-wm </syntaxhighlight> ==== On [[Arch Linux|Arch]] and Arch-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo pacman -S i3 </syntaxhighlight>Or if you would like ''just'' the window manager that doesn't come with a notification daemon, lock screen and some tools, you can run:<syntaxhighlight lang="bash"> $ sudo pacman -S i3-wm </syntaxhighlight> ==== On [[Gentoo]] and Gentoo-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo emerge -av x11-wm/i3 </syntaxhighlight> ==== On [[Fedora]] and Fedora-based distributions: ==== <syntaxhighlight lang="bash"> $ sudo dnf install i3 </syntaxhighlight> ==== On [[OpenSUSE]] Tumbleweed or Leap: ==== <syntaxhighlight lang="bash"> $ sudo zypper in i3 </syntaxhighlight> ==== On [[NixOS]] and NixOS-based distributions ==== <syntaxhighlight lang="nixos"> services.xserver.windowManagers.i3.enable = true; </syntaxhighlight> == <u>See Also</u> == [[I3]] 2e1e4dab5a8fcabc5fde3334e81c0623b9d02f31 3000 696 4162 3829 2025-09-16T07:26:43Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki == Using Cinnamon == * Open Start Menu in bottom right corner * Log Out * Click on [[Cinnamon]] Logo next to log In details * Switch to desired [[Window Manager]] == Using i3 == <syntaxhighlight> Mod+shift+e </syntaxhighlight> * Confirm that you want to log out in pop-up * Click on [[i3]] logo next to Log In details * Switch to desired Window Manager == Using XFCE == * Open Start Menu in Top Left corner * Log Out * Click on [[XFCE]] Logo next to log In details * Switch to desired Window Manager == Using MATE == * Open Start Menu in bottom right corner * Log Out * Click on [[MATE]] Logo next to log In details * Switch to desired Window Manager 101f6d470eb440cb9ef8dbc1f58832383edc2f70 3001 1022 4163 2025-09-16T07:27:29Z Madonuko 140 /* Move page out of Guides */ new section wikitext text/x-wiki == Move page out of Guides == This page is not a guide, and thus should not belong to this namespace. I propose moving this. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 07:27, 16 September 2025 (UTC) 14893cfc8ca2a7adcf3194707da7e3f129a2137a 0 682 4164 4108 2025-09-16T07:32:22Z Madonuko 140 don't underline headings wikitext text/x-wiki {{Needs Citations}}{{stub}} {{DistributionInfobox | title = Puppy Linux | image = [[File:Puppy logo.svg|frameless|Puppy Linux Logo]] | caption = Puppy Linux Logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]], [[XBPS]], PPM | defaultdesktops = JWM, [[Xfce]], LXDE | usagetype = Desktop | architectures = x86_64, x86, ARM | website = [https://puppylinux-woof-ce.github.io/ Link] }} '''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003 by Barry Kauler. === Hardware Requirements === ==== 64-Bit Bookworm ==== <u>Recommended</u> * 64-bit dual-core CPU * 2-4 GB RAM * 5 GB Storage Space <u>Minimum</u> * 64-Bit single-core CPU * 1GB RAM * 5GB Storage Space ==== 32-Bit Bookworm ==== <u>Recommended</u> * 32-bit dual-core CPU * 2-4 GB RAM * 5 GB Storage Space <u>Minimum</u> * 32-Bit single-core CPU * 1GB RAM * 5GB Storage Space b1455f46f7b4293916fb4f3e1cc114e612691fb3 4170 4164 2025-09-16T07:36:06Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}}{{stub}} {{DistributionInfobox | title = Puppy Linux | image = [[File:Puppy logo.svg|frameless|Puppy Linux Logo]] | caption = Puppy Linux Logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]], [[XBPS]], PPM | defaultdesktops = JWM, [[Xfce]], LXDE | usagetype = Desktop | architectures = x86_64, x86, ARM | website = [https://puppylinux-woof-ce.github.io/ Link] }} '''Puppy Linux''' is a family of light-weight Linux distributions that focus on ease of use and minimal memory footprint. it was released on the 18th of June, 2003 by Barry Kauler. == Hardware Requirements == === 64-Bit Bookworm === <u>Recommended</u> * 64-bit dual-core CPU * 2-4 GB RAM * 5 GB Storage Space <u>Minimum</u> * 64-Bit single-core CPU * 1GB RAM * 5GB Storage Space === 32-Bit Bookworm === <u>Recommended</u> * 32-bit dual-core CPU * 2-4 GB RAM * 5 GB Storage Space <u>Minimum</u> * 32-Bit single-core CPU * 1GB RAM * 5GB Storage Space 272910bb4afbeddeeb6cb0849b1108aa557aeb3f 0 1011 4165 4118 2025-09-16T07:34:47Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = Arco Linux | image = [[File:Arcolinux.svg| 200px]] | caption = The Arco Linux logo | releasestatus = Discontinued | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop | architectures = x86_64 | website = [https://arcolinux.com/ arcolinux.com] }} fa6fadaca6050d4547b4f601d1c5e2b3571f373b 0 1014 4166 4127 2025-09-16T07:34:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = BSD | image = [[File:BSD-OS.svg]] | caption = The BSD logo | releasestatus = Discontinued | releasemodel = Discontinued | packagemanager = Unknown (please correct this) | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = Unknown (please correct this) | website = [https://www.bsd.org/ www.bsd.org] }} The Berkeley Software Distribution (BSD), also known as Berkeley [[UNIX|Unix]], is a discontinued Unix [[Operating System|operating system]] developed and distributed by the Computer Systems Research Group (CSRG) at the University of California, Berkeley (Hence the name). First released in 1978, it began as an improved derivative of AT&T's original Unix developed at Bell Labs, based on the source code. BSD's Mascot is [[Beastie]], a red demon/devil cartoonish character. 109bc9c696915eb0589ab94e4324b95fa1bdbf8a 4185 4166 2025-09-26T14:31:36Z Imnotgoodatnames 121 Replaced logo, it was the logo of just BSD/OS (supported 1993-2004) rather than BSD in general, changed some wording regarding the mascot wikitext text/x-wiki {{DistributionInfobox | title = BSD | image = [[File:Daemon-phk.svg|frameless|upright=0.7]] | caption = The BSD Daemon, the mascot of BSD | releasestatus = Discontinued | releasemodel = Discontinued | packagemanager = Unknown (please correct this) | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = Unknown (please correct this) | website = [https://www.bsd.org/ www.bsd.org] }} The Berkeley Software Distribution (BSD), also known as Berkeley [[UNIX|Unix]], is a discontinued Unix [[Operating System|operating system]] developed and distributed by the Computer Systems Research Group (CSRG) at the University of California, Berkeley (Hence the name). First released in 1978, it began as an improved derivative of AT&T's original Unix developed at Bell Labs, based on the source code. BSD's Mascot is a red daemon, commonly nicknamed [[Beastie]]. ec1abba5ce420c32d4c10d7876ecec880dd28739 0 1009 4167 4078 2025-09-16T07:35:06Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = Bazzite | image = [[File:Bazzite Logo.svg|200px]] | caption = The Bazzite logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Flatpak]] | defaultdesktops = [[GNOME]],[[KDE Plasma]] | usagetype = Gaming | architectures = x86_64 | website = [https://bazzite.gg/ bazzite.gg] }} [[Category:Linux Distributions]] b364c06ced834ed6c884f359ba52a3f572f52b67 0 707 4168 4091 2025-09-16T07:35:16Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox |image=[[File:Grub-knoppix.jpg|thumb]] |caption=Grub Boot Menu |title=GRUB |releasestatus=Maintained |lastrelease=2.12, 2023-12-20 |languages=[[C]], [[Assembly]] |developers=GNU Project |website=[http://gnu.org/software/grub/ GNU Page] }} '''GRUB''' (short for '''GRand Unified Bootloader''') is a [[bootloader]] designed for [[UNIX|UNIX-like]] systems developed by the GNU Project. It provides the user with the option to choose between different [[Operating System|operating systems]] or [[kernel]] versions without having to use the [[BIOS]]. Originally developed by Erich Boleyn<ref>[http://www.uruk.org/grub/ GRUB -- GRand Unified Bootloader], Erich Boleyn (Accessed: 2025-07-01)</ref>, GRUB is now a part of the GNU project and comes with two versions, GRUB 0 (Also known as GRUB Legacy) and GRUB 2. Since GRUB Legacy is obsolete, this article mainly describes GRUB 2. GRUB originated in 1995 when Erich Boleyn was trying to boot the GNU Hurd with the University of Utah's Mach 4 microkernel (now known as GNU Mach). Erich and Brian Ford designed the Multiboot Specification, because they were determined not to add to the large number of mutually-incompatible PC boot methods.<ref name=":0">https://www.gnu.org/software/grub/manual/grub/grub.html#Overview GNU website, 2025 (Imported 02.07.2025)</ref> Around 2002, Yoshinori K. Okuji started work on PUPA (Preliminary Universal Programming Architecture for GNU GRUB), aiming to rewrite the core of GRUB to make it cleaner, safer, more robust, and more powerful. PUPA was eventually renamed to GRUB 2, and the original version of GRUB was renamed to GRUB Legacy. <ref name=":0" /> GRUB contains support for multiple file systems ( [[FAT32]], [[ext4]], [[Btrfs]] or [[XFS]].) Both GRUB 2 and GRUB 0 systems support [[UEFI]] and BIOS-based systems. [[File:EndeavourOS Grub 2 theme.png|alt=GRUB Menu with purple and pink colours. with the text "EndeavourOS on linux-lts"|thumb|Endeavour OS GRUB theme]] GRUB can be Customised (Riced) into many different styles. Some distros, such as [[EndeavourOS]] have a pre-installed theme. == See More == * [https://wiki.archlinux.org/title/Grub Grub on ArchWiki] == References == 57e97777281e43d910d23fabad09c17bc249d280 0 884 4169 4110 2025-09-16T07:35:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>https://lubuntu.me/ Lubuntu, Accessed: 2025-08-22</ref> * [[Fedora]] LXQt spin<ref>https://fedoraproject.org/spins/lxqt Fedora, Accessed 2025-08-22</ref> * [[CachyOS]]: available in installer<ref>https://wiki.cachyos.org/installation/desktop_environments/ CachyOS, Accessed:2025-08-22</ref> * [[SparkyLinux]]<ref>https://wiki.sparkylinux.org/doku.php/about Sparky Linux, Accessed:2025-08-22</ref> * [[Debian]]: available in installer<ref>https://wiki.debian.org/LXQt Debian Wiki, Accessed:2025-08-22</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>https://packages.debian.org/stable/lxqt-core Debian, Accessed 2025-08-23</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>https://packages.debian.org/trixie/lxqt Debian, Accessed:2025-08-23</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>https://packages.debian.org/stable/task-lxqt-desktop Debian, Accessed:2025-08-23</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>https://archlinux.org/groups/x86_64/lxqt/ Arch Linux, Accessed:2025-08-23</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template Github, Accessed:2025-08-23</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers LXQt wiki, Accessed:2025-08-23</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions LXQt wiki, Accessed:2025-08-23</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight lang="text">exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == 7d65c4b23ddd8eb1433e922db8c1597776392e06 4172 4169 2025-09-20T07:17:52Z Satnus 215 Undo revision [[Special:Diff/4169|4169]] by [[Special:Contributions/Hamachitan|Hamachitan]] ([[User talk:Hamachitan|talk]]) wikitext text/x-wiki {{Work In Progress}} {{Cleanup|[[ATL:Guidelines#Citations]]}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFm (Accessed: 2025-08-18)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ PCManFM Accessed:2025-08-18</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>https://lubuntu.me/ Lubuntu, Accessed: 2025-08-22</ref> * [[Fedora]] LXQt spin<ref>https://fedoraproject.org/spins/lxqt Fedora, Accessed 2025-08-22</ref> * [[CachyOS]]: available in installer<ref>https://wiki.cachyos.org/installation/desktop_environments/ CachyOS, Accessed:2025-08-22</ref> * [[SparkyLinux]]<ref>https://wiki.sparkylinux.org/doku.php/about Sparky Linux, Accessed:2025-08-22</ref> * [[Debian]]: available in installer<ref>https://wiki.debian.org/LXQt Debian Wiki, Accessed:2025-08-22</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>https://packages.debian.org/stable/lxqt-core Debian, Accessed 2025-08-23</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>https://packages.debian.org/trixie/lxqt Debian, Accessed:2025-08-23</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>https://packages.debian.org/stable/task-lxqt-desktop Debian, Accessed:2025-08-23</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>https://archlinux.org/groups/x86_64/lxqt/ Arch Linux, Accessed:2025-08-23</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template Github, Accessed:2025-08-23</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers LXQt wiki, Accessed:2025-08-23</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions LXQt wiki, Accessed:2025-08-23</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight lang="text">exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == 373bd0602ce360cb230ff8b5353d07c4040dcf51 3000 1019 4171 4155 2025-09-19T21:26:27Z Satnus 215 Finished Brave and added Librewolf. Will rewrite page someday now. wikitext text/x-wiki {{Guide Warning}} {{Work In Progress}} A [https://en.wikipedia.org/wiki/Web_browser web browser] is one of the most important user facing applications. This guide shows how to install some web browsers in Linux. == [[Mozilla Firefox]] == === Using your distribution's package manager === In many distributions, Firefox comes preinstalled as the default web browser. If for any reason your distribution came without firefox, you can install it using the distribution's [[package manager]]. For example, [[Debian]] based distributions may use this command. <syntaxhighlight lang="bash"> $ sudo apt install firefox </syntaxhighlight> === Using [[flatpak]] === <syntaxhighlight lang="bash"> $ flatpak install flathub org.mozilla.firefox </syntaxhighlight> '''Note that when using flatpak, profiles are stored in ~/.var/app/org/mozilla.firefox/.mozilla, not in ~/.mozilla!''' === Using [[snap]] === <syntaxhighlight lang="bash"> $ sudo snap install firefox </syntaxhighlight> '''Note that when using snap, profiles are stored in ~/snap/firefox/common/.mozilla/firefox, not in ~/.mozilla/firefox!''' === Install from the website=== # Download the file for your architecture [https://www.firefox.com/en-US/browsers/desktop/linux/ here]. # Unzip it using either your file explorer or by running <code lang="bash">tar xvf firefox-*.tar.xz</code> # From here, you can directly execute the <code>firefox</code> binary from the unzipped folder with <code lang="bash">./firefox</code>. # (Optional) To ensure that it remains compatible, you should move the unzipped firefox folder into /opt. '''This requires root access''' # (Optional) You can arrange a symlink by <code lang="bash">ln -s path/to/firefox/firefox /usr/local/bin/firefox</code> to be able to execute it with the <code lang="bash">firefox</code> command. '''This requires root access'''. # (Optional) You can set up a desktop file (to be able to launch firefox from the start menu) by downloading [https://raw.githubusercontent.com/mozilla/sumo-kb/main/install-firefox-linux/firefox.desktop this file] (The simplest method to do so would be to run <code lang="bash">wget https://raw.githubusercontent.com/mozilla/sumo-kb/main/install-firefox-linux/firefox.desktop</code>.), and copying it into either ~/.local/share/applications (to make it available for one user) or into /usr/local/share/applications (to make it available for all users). '''If you did not follow step 4, you will need to edit the firefox.desktop file you downloaded and change line 11 to '''<code>Icon=path/to/firefox/browser/chrome/icons/default/default128.png</code>'''. If you did not follow step 5, you will need to edit the firefox.desktop file you downloaded and change line 7 to '''<code>Icon=path/to/firefox/firefox %u</code>'''.''' <ref>[https://support.mozilla.org/en-US/kb/install-firefox-linux Installing Firefox on Linux], AliceWyman, Chris Ilias, cor-el, Underpass, Tonnes, scoobidiver, Swarnava Sengupta, ideato, Mozinet, user669794, Joni, Paul, Marcelo Ghelman, YD, Shaded_ke, Rashid, Danny Colin, Mark Heijl, Angela Lazar, liam, ErlingR, PGGWriter, user3771646, unixfan, servesha, qxyz123, Roy Orbitson, Lucas Siebert, Johan Lorenzo, mysticvortexscribe, Mia SAMBATH, Alif Putra Winata, 2025 (Accessed: 2025-09-14)</ref> == [[Google Chrome]] == === Install from the website (Debian / Fedora / openSUSE based) === Go [https://www.google.com/chrome/other-platforms/ here], choose Linux for operating system and either "[[Debian]]/[[Ubuntu]]" or "[[Fedora]]/[[openSUSE]]" depending on which your distribution is based on, and download the file. If your distribution is based on Debian/Ubuntu, use [[apt]]. <syntaxhighlight lang="bash"> $ sudo apt install ./google-chrome-*_current_x86_64.deb </syntaxhighlight> If your distribution is based on Fedora/openSUSE, use <syntaxhighlight lang="bash"> $ sudo dnf localinstall ./google-chrome-*_current_x86_64.rpm </syntaxhighlight> === Install using package manager (Debian) === === Install using package manager (Fedora/openSUSE) === Firstly, in case you haven't installed third party repositories, do so. <syntaxhighlight lang="bash"> $ sudo dnf install fedora-workstation-repositories </syntaxhighlight> Then, enable the Google Chrome repository. <syntaxhighlight lang="bash"> $ sudo dnf config-manager setopt google-chrome.enabled=1 </syntaxhighlight> Finally, you can install <code>google-chrome-stable</code> (or the other included google chrome installs, such as <code>google-chrome-unstable</code>, <code>google-chrome-canary</code>, or <code>google-chrome-beta</code>) using the following command. <syntaxhighlight lang="bash"> $ sudo dnf install google-chrome-stable </syntaxhighlight> <ref>[https://docs.fedoraproject.org/en-US/quick-docs/installing-chromium-or-google-chrome-browsers/ Installing Chromium or Google Chrome Browsers :: Fedora Docs], Peter Lilley, 2021 (Accessed: 2025-09-14)</ref> == [[Microsoft Edge]] == === Install from the website (Debian) === Download Microsoft Edge [https://www.microsoft.com/en-us/edge/ here], and install it either by double clicking the file in your file manager or run the following command. <syntaxhighlight lang="bash"> $ sudo apt install ./microsoft-edge-stable_*_amd64.deb </syntaxhighlight> == [[Vivaldi]] == === Install from the website (Debian / Fedora / openSUSE === Get the installation package from [https://vivaldi.com/download/ here] and run the install command on it depending on your package manager. For Debian & Debian based distros: <syntaxhighlight lang="bash"> $ sudo apt install ./vivaldi-stable_*.deb </syntaxhighlight> For Red Hat, Red Hat based, openSUSE or openSUSE based distributions: <syntaxhighlight lang="bash"> $ sudo dnf localinstall vivaldi-stable_*.rpm </syntaxhighlight> === Using [[Snap]] === <syntaxhighlight lang="bash"> $ sudo snap install vivaldi </syntaxhighlight> <ref>[https://snapcraft.io/vivaldi Download Vivaldi | Vivaldi Browser], Vivaldi, 2025 (Accessed: 2025-09-14)</ref> === Using [[Flatpak]] === <syntaxhighlight lang="bash"> $ flatpak install flathub com.vivaldi.Vivaldi </syntaxhighlight> == [[Brave]] == === Installing using script === The simplest method that is most likely to work for most distributions is to run the install script provided by Brave. <syntaxhighlight lang="bash"> curl -fsS https://dl.brave.com/install.sh | sh </syntaxhighlight> Alternatively, replacing <code>sh</code> to <code lang="bash">CHANNEL=beta sh</code> or <code lang="bash">CHANNEL=nightly sh</code> will install the respective version. === Install using package manager (Debian based) === Add the keyring and sources file using the following commands. <syntaxhighlight lang="bash"> $ sudo curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg $ sudo curl -fsSLo /etc/apt/sources.list.d/brave-browser-release.sources https://brave-browser-apt-release.s3.brave.com/brave-browser.sources </syntaxhighlight> Finally, you can install either <code>brave-browser</code>, <code>brave-browser-beta</code>, or <code>brave-browser-nightly</code> using the following command. <syntaxhighlight lang="bash"> $ sudo apt update && sudo apt install brave-browser </syntaxhighlight> === Install using package manager (Fedora based) === In case it has not been installed, the following command will install [[dnf]] plugins. <syntaxhighlight lang="bash"> $ sudo dnf install dnf-plugins-core </syntaxhighlight> Then, you can add the repository with the following command. <syntaxhighlight lang="bash"> $ sudo dnf config-manager addrepo --from-repofile=https://brave-browser-rpm-release.s3.brave.com/brave-browser.repo </syntaxhighlight> Finally, you can install either <code>brave-browser</code>, <code>brave-browser-beta</code>, or <code>brave-browser-nightly</code> using the following command. <syntaxhighlight lang="bash"> $ sudo dnf install brave-browser </syntaxhighlight> === Install using package manager (openSUSE based) === Add the repository with the following command. <syntaxhighlight lang="bash"> $ sudo zypper addrepo https://brave-browser-rpm-release.s3.brave.com/brave-browser.repo </syntaxhighlight> Finally, you can install either <code>brave-browser</code>, <code>brave-browser-beta</code>, or <code>brave-browser-nightly</code> using the following command. <syntaxhighlight lang="bash"> $ sudo zypper install brave-browser </syntaxhighlight> === Using [[Flatpak]] === <syntaxhighlight lang="bash"> $ flatpak install com.brave.Browser </syntaxhighlight> === Using [[Snap]] === <syntaxhighlight lang="bash"> $ sudo snap install brave </syntaxhighlight> == [[Librewolf]] == === Installing using package manager (Debian based) === In case you don't have it, install <code>[[extrepo]]</code> first. <syntaxhighlight lang="bash"> $ sudo apt update && sudo apt install extrepo </syntaxhighlight> Then, enable the extrepo for librewolf. <syntaxhighlight lang="bash"> $ sudo extrepo enable librewolf </syntaxhighlight> Finally, install librewolf. <syntaxhighlight lang="bash"> $ sudo apt update && sudo apt install librewolf </syntaxhighlight> === Installing using package manager (Fedora based) === Add the repository. <syntaxhighlight lang="bash"> $ curl -fsSL https://repo.librewolf.net/librewolf.repo | pkexec tee /etc/yum.repos.d/librewolf.repo </syntaxhighlight> Then, install librewolf. <syntaxhighlight lang="bash"> $ sudo dnf install librewolf </syntaxhighlight> === Installing using package manager (Arch based) === <syntaxhighlight lang="bash"> $ sudo yay -s librewolf </syntaxhighlight> You can alternatively install the precompiled version. <syntaxhighlight lang="bash"> $ sudo yay -s librewolf-bin </syntaxhighlight> === Installing using package manager (Gentoo based) === <syntaxhighlight lang="bash"> $ sudo eselect repository add librewolf git https://codeberg.org/librewolf/gentoo.git $ emaint -r librewolf sync </syntaxhighlight> === Using [[Flatpak]] === <syntaxhighlight lang="bash"> $ flatpak install flathub io.gitlab.librewolf-community </syntaxhighlight> === Using [[Appimage]] === Download the most recent appimage from the [https://gitlab.com/librewolf-community/browser/appimage/-/releases Gitlab release page] and run it as an executable. == References == <references/> 7af020dcfde8a1131273f6406aa149626a2058be 0 907 4173 4057 2025-09-21T17:33:46Z Ivanovics 150 Retitle Usage to Enabling PipeWire, add configuration section wikitext text/x-wiki [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available in PipeWire 0.3.45) in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz <code> context.properties = { default.clock.allowed-rates = [ 48000 44100 ] } </code> Up to 16 default clock rates can be specified in this manner You can read more about configuring PipeWire [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] 988fc8331ece89f2ee24e7ba7ca0ba39c34fb494 4174 4173 2025-09-21T17:37:44Z Ivanovics 150 Fix formatting wikitext text/x-wiki [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available in PipeWire 0.3.45) in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz <syntaxhighlight lang="sh"> context.properties = { default.clock.allowed-rates = [ 48000 44100 ] } </syntaxhighlight> Up to 16 default clock rates can be specified in this manner You can read more about configuring PipeWire [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] fcd290f86d1bed521b6b317903a83406d35fc348 4176 4174 2025-09-22T11:49:06Z Ivanovics 150 Fix dumdum grammar mistake wikitext text/x-wiki [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available in PipeWire 0.3.45) can be placed in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz <syntaxhighlight lang="sh"> context.properties = { default.clock.allowed-rates = [ 48000 44100 ] } </syntaxhighlight> Up to 16 default clock rates can be specified in this manner You can read more about configuring PipeWire [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] 84a18d21c135387ff2e35237ab8a4abc92f234bd 4177 4176 2025-09-23T07:42:35Z Ivanovics 150 Add controlling the volume wikitext text/x-wiki [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available in PipeWire 0.3.45) can be placed in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz <syntaxhighlight lang="sh"> context.properties = { default.clock.allowed-rates = [ 48000 44100 ] } </syntaxhighlight> Up to 16 default clock rates can be specified in this manner You can read more about configuring PipeWire [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] == Interacting with PipeWire == PipeWire can be controlled with PulseAudio tools, such as '''pactl''', or without depending on pulseaudio it can be achieved with wpctl (if the Wireplumber session manager is used) or pw-cli (available at all times). === Controlling volume === Using '''wpctl''' to increase the volume by ex. 5% <code>wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+</code> Alternatively, the same can be achieved with '''pw-cli''' First, find the node by running <code>pw-cli ls Node</code>, then run <code>pw-cli s <numical node id> Props '{mute: false, channelVolumes: [ 0.2, 0.2 ] }' </code> to unmute and set the volume of the application to 20% 4f35d5a457beb5dbff577091c7dd31845416c889 2 655 4175 2688 2025-09-22T08:41:58Z Hog 161 Blanked the page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 4198 4175 2025-10-01T08:26:57Z Hog 161 update wikitext text/x-wiki [[File:Icon manjaro rounded 2022.svg|thumb]] 528344580ee58dcec9daeb53f37d9fd2341aaeda 0 622 4178 4112 2025-09-24T14:40:17Z Satnus 215 Revamped the gallery so clicking pictures will zoom on them, and link to the DE's wiki page is on the the caption. wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity]] File:XFCE-4.18-Desktop.png|[[XFCE]] File:LXDE-Qt preview.png|[[LXDE]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} 029f18c8278014f5912dace422b7d719eee177ab 4179 4178 2025-09-24T14:49:13Z Satnus 215 Fixed trinity's link wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity Desktop Environment]] File:XFCE-4.18-Desktop.png|[[XFCE]] File:LXDE-Qt preview.png|[[LXDE]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} 7bccb508a19d3d72b57ec4f1bb592f40e984f0ab 6 1023 4180 2025-09-24T16:50:14Z Satnus 215 Unofficial JavaScript logo. That's literally what the filename says. wikitext text/x-wiki == Summary == Unofficial JavaScript logo. That's literally what the filename says. == Licensing == {{PD}} 73c7ad667dadccb593aeda5f4e3dab5bf8faa88a 0 257 4181 4138 2025-09-25T18:17:10Z BSFGP 286 /* Fixed the link to Sway WM in See also section */ wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.51.0, 2025-09-10 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor. It was originally based on [[wlroots]] but migrated away from it towards its own rendering backend library [[aquamarine]] in version 0.42.0<ref>[https://hypr.land/news/independentHyprland/ Hyprland moves off wlroots], 2025-09-02 (Accessed 2025-09-02)</ref> It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Hyprland], 2025-08-10 (Accessed: 2025-08-10)</ref> Hyprland uses its own configuration syntax, designed to be readable and easy to learn, with similarities to shell scripting. The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. * '''Hyprlock''' - a highly customizable and efficient Wayland lockscreen * '''Hyprpicker''' - a small utility for picking a color on your current screen == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> 553265be8894cfe7dca9a31308ce58aa176beb3e 0 198 4182 4131 2025-09-26T06:32:38Z Satnus 215 Added Omarchy. Definitely not because of Fireship and Bog. wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[openSUSE]] |A community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == 7fcfcb3a45f7bc7fcf68c8898c952eb362211451 6 1024 4183 2025-09-26T06:43:12Z Satnus 215 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1025 4184 2025-09-26T07:25:55Z Satnus 215 Very short Omarchy page. wikitext text/x-wiki {{DistributionInfobox | title = Omarchy | image = [[File:omarchy-logo.svg | thumb]] | caption = The Omarchy Logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[Hyprland]] | usagetype = Desktop | architectures = x86_64 | website = [https://omarchy.org omarchy.org] }} 9bddb2261085ad2cccc66124c52be0d1ab08d581 2 3 4186 4064 2025-09-27T12:08:08Z Amadaluzia 52 wikitext text/x-wiki <syntaxhighlight lang="c++" line="1">#include <string> #include <functional> #include <print> using String = std::string; class Person { virtual String description() = 0; }; using SocialPair = struct { String service; String username; }; class Amadaluzia : Person { public: String name = "Artur Manuel"; int age = 17; std::vector<String> interests{ "Programming", "CLI development", "GUI development", "Web development", "Library development", "System administration", "Walking", "Climbing", "Math", "Learning", "Exercise", "Sports", "Socialising", "Writing", "Photography", "Video editing", "Movie production", "Techno music", "Shoegaze", "Alternative Rock", }; std::vector<SocialPair> socials = { {"Email", "amadaluzia@disroot.org"}, {"Email (atl.tools alt)", "amad@atl.tools"}, {"Email (tutanota.com alt)", "amadaluzia@tutanota.com"}, {"Matrix", "@amadaluzia:tchncs.de"}, {"Matrix (pub.solar alt)", "@amadaluzia:pub.solar"}, {"Matrix (envs.net alt)", "@amadaluzia:envs.net"}, {"libera.chat", "amadaluzia"}, {"oftc.net", "amadaluzia"}, {"Revolt", "amadaluzia#3242"}, {"Mastodon", "@amadaluzia@bsd.cafe"}, {"Discord", "amadaluzia"}, {"Discord (alt)", "balke.nix"}, {"Keyoxide", "aspe:keyoxide.org:ZV3A66CSCNOS7V4N5A4DOD57I4"}, {"GitHub", "amadaluzia"}, {"SourceHut", "amadaluzia"}, {"Codeberg", "amadaluzia"}, {"GitLab", "amadaluzia"}, }; String description() override; }; String Amadaluzia::description() { String result{}; result += std::format("Good day, my name is {}, commonly known online as \"amadaluzia\". I am a {}\n", name, age); result += "year old Portuguese-Italian resident of the UK. You may have seen me in many\n"; result += "programming spaces, however, I am keenly interested in many other topics. More\n"; result += "specifically, I am interested in:\n"; for (auto interest : interests) result += std::format("- {}\n", interest); result += "I am also present on many social media platforms, even multiple times! Moreover, I\n"; result += "have pretty much the same name everywhere, so you can reliably find me. But I will\n"; result += "share my social platforms here as I use many decentralised services. Here I am:\n"; for (auto const &[service, username] : socials) result += std::format("- {} on {}\n", username, service); result += "\nIf you can find any ways of optimising this program, let me know, as long as the\n"; result += "it's kept to Amadaluzia::description(). Thank you for reading!\n"; return result; } int main(void) { Amadaluzia amadaluzia; std::println("{}", amadaluzia.description()); }</syntaxhighlight> ea51a5bc05a5d42774167b3537ba5f08c82ff650 0 169 4187 4025 2025-09-27T15:45:01Z DrCodfish 287 /* List of Package Managers */ Add Nala to list. wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories == List of Package Managers == All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained by the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper]/[[Rpm]], used in [[SUSE Linux Enterprise]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [[Void Linux]], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[Bedrock Linux]]'s special use cases. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] * [[Homebrew]] (or just brew) was originally created as a package manager for macOS, but it has Linux support too. You can install it on almost any distribution as an alternative package manager. You can find more information about it on [https://brew.sh/ the official website], the source is hosted [https://github.com/Homebrew/brew on GitHub] * [[Nala]] is a fronted for [[apt]] that gives a prettier output, parallel downloads, and downloading from mirrors of sources. The source can be viewed [https://github.com/volitank/nala here] 92f330ab6b3e7617a5dd6e4e4c0e100bae50fdd2 0 1026 4188 2025-09-27T16:25:12Z DrCodfish 287 Init wikitext text/x-wiki Nala is a fronted for [[apt]], the package manager used by [[Linux Distributions|Debian-based Linux distros]] (abbreviated 'distro'). It was designed to give a prettier output and be faster to install packages, using parallel downloads and optional mirrors to boost performance. Because it is a fronted and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parralel download connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Arguments == Nala uses two styles of arguments, commands, such as `search` or `fetch` , and modifiers, such as `--installed` or `--auto`. Commands tell Nala what to do, whereas flags modify or change how the command performs in some way or form. Exceptions exist, such as `--help` or `--version`. == Usage == The following shows common Nala commands, which are mostly inherited from apt. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable sortable mw-collapsible mw-collapsed" |+ ! ! |- | | |- | | |- | | |} e963975aaeb94d73a36a0c9b43db75b427c2dd8d 4189 4188 2025-09-27T16:27:00Z DrCodfish 287 /* Usage */ wikitext text/x-wiki Nala is a fronted for [[apt]], the package manager used by [[Linux Distributions|Debian-based Linux distros]] (abbreviated 'distro'). It was designed to give a prettier output and be faster to install packages, using parallel downloads and optional mirrors to boost performance. Because it is a fronted and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parralel download connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Arguments == Nala uses two styles of arguments, commands, such as `search` or `fetch` , and modifiers, such as `--installed` or `--auto`. Commands tell Nala what to do, whereas flags modify or change how the command performs in some way or form. Exceptions exist, such as `--help` or `--version`. == Usage == The following shows common Nala commands, which are mostly inherited from apt. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" style="width:100%; table-layout:fixed;" ! Command ! Description a7821cab56c728bfe6d7de261ca1796b09020aed 4190 4189 2025-09-27T16:28:35Z DrCodfish 287 wikitext text/x-wiki Nala is a fronted for [[apt]], the package manager used by [[Linux Distributions|Debian-based Linux distros]] (abbreviated 'distro'). It was designed to give a prettier output and be faster to install packages, using parallel downloads and optional mirrors to boost performance. Because it is a fronted and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parralel download connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Arguments == Nala uses two styles of arguments, commands, such as `search` or `fetch` , and modifiers, such as `--installed` or `--auto`. Commands tell Nala what to do, whereas flags modify or change how the command performs in some way or form. Exceptions exist, such as `--help` or `--version`. == Usage == The following shows common Nala commands, which are mostly inherited from apt. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" style="width:100%;" ! Header 1 ! Header 2 ! Header 3 |- | Row 1, Cell 1 | Row 1, Cell 2 | Row 1, Cell 3 |- | Row 2, Cell 1 | Row 2, Cell 2 | Row 2, Cell 3 |} 602547fac4a41677197e602f47668b77fee759c6 4191 4190 2025-09-27T16:34:02Z DrCodfish 287 /* Usage */ wikitext text/x-wiki Nala is a fronted for [[apt]], the package manager used by [[Linux Distributions|Debian-based Linux distros]] (abbreviated 'distro'). It was designed to give a prettier output and be faster to install packages, using parallel downloads and optional mirrors to boost performance. Because it is a fronted and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parralel download connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Arguments == Nala uses two styles of arguments, commands, such as `search` or `fetch` , and modifiers, such as `--installed` or `--auto`. Commands tell Nala what to do, whereas flags modify or change how the command performs in some way or form. Exceptions exist, such as `--help` or `--version`. == Usage == The following shows common Nala commands, which are mostly inherited from apt. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" style="width:100%;" ! style="width:50%;" | Header 1 ! style="width:50%;" | Header 3 |} 51e258fd8a1206fb6c71658338d74a5140c70203 4192 4191 2025-09-28T01:07:11Z DrCodfish 287 /* Usage */ wikitext text/x-wiki Nala is a fronted for [[apt]], the package manager used by [[Linux Distributions|Debian-based Linux distros]] (abbreviated 'distro'). It was designed to give a prettier output and be faster to install packages, using parallel downloads and optional mirrors to boost performance. Because it is a fronted and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parralel download connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Arguments == Nala uses two styles of arguments, commands, such as `search` or `fetch` , and modifiers, such as `--installed` or `--auto`. Commands tell Nala what to do, whereas flags modify or change how the command performs in some way or form. Exceptions exist, such as `--help` or `--version`. == Usage == The following shows common Nala commands, which are mostly inherited from apt. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of avaible packages and their versions |- |<code>nala upgrade</code> |Upgrades system's packages, installing any new ones if required |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages in the cache |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands |} 2e24e9856fa3995497243fa1e548532109c4ac88 4193 4192 2025-09-28T13:23:01Z Madonuko 140 format wikitext text/x-wiki {{stub}}{{cleanup|missing infobox}} [[Category:Software]] [[Category:Package managers]] Nala is a front-end for [[apt]], the [[package manager]] used by [[Debian]]-based [[Linux distributions]] (abbreviated ‘distro’), designed to provide prettier output and speed up [[package]] installations with parallel downloads and optional mirrors to boost performance. As a front-end and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or [[Ubuntu]] 19/Disco Dingo or newer, as older releases do not entail the required [[python]] versions. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parallel downloads connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Usage == The following shows common Nala [[command]]s, which are mostly inherited from apt. Some commands can take multiple [[argument]]s, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of avaible packages and their versions |- |<code>nala upgrade</code> |Upgrades system's packages, installing any new ones if required |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages in the cache |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands |} 454a781022b0c2279abad6b173d0e6debb679c88 4197 4193 2025-10-01T08:24:10Z Hog 161 fixed link wikitext text/x-wiki {{stub}}{{cleanup|missing infobox}} [[Category:Software]] [[Category:Package managers]] Nala is a front-end for [[apt]], the [[package manager]] used by [[Debian]]-based [[Linux Distributions|Linux distributions]] (abbreviated ‘distro’), designed to provide prettier output and speed up [[package]] installations with parallel downloads and optional mirrors to boost performance. As a front-end and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or [[Ubuntu]] 19/Disco Dingo or newer, as older releases do not entail the required [[python]] versions. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parallel downloads connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Usage == The following shows common Nala [[command]]s, which are mostly inherited from apt. Some commands can take multiple [[argument]]s, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of avaible packages and their versions |- |<code>nala upgrade</code> |Upgrades system's packages, installing any new ones if required |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages in the cache |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands |} 22d3f06bc9bf5053cf3e4596402a4f76af393a38 2 1027 4194 2025-09-28T17:38:28Z Stewarpt 100 Added Hi I'm stew wikitext text/x-wiki Hi I'm stew 6ea0fd566e184b08cd971dc68562150c5d4e0b0d 0 317 4195 3687 2025-09-29T15:12:42Z Satnus 215 Fixed misinformation from my part wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}}{{Cleanup|Page relies too heavily on bullet pointed lists}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. Created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm Void Linux: Distribution mit XBPS-Paketverwaltung], Pro-Linux, 2015-06-12 (Accessed: 2025-08-09)</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and optional [[musl]] libc support. == Overview == === Key Features === * Independent build system and package repositories * Offers [[Glibc|GNU Glibc]] and Musl variants * Uses [https://smarden.org/runit Runit] for service management and it's [[Init System|init process]] * Rolling release model with stable package testing * Minimal base system === Architecture Support === Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses the [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for runit. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === ==== glibc vs musl ==== Void offers two libc implementations: * '''glibc''': Standard GNU C Library ** Better software compatibility ** Larger binary size ** More memory usage * '''musl''': Alternative C Library ** Smaller footprint ** Better security ** Static linking support ** Some compatibility challenges == Installation == The installation process follows these main steps: * Downloading appropriate image * Creating bootable media * Partitioning and formatting * Base system installation * Configuration and bootloader setup Detailed instructions are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == === Building Packages === Void uses XBPS-src for package building: * Template-based build system * Cross-compilation support * Reproducible builds * Quality assurance tools == Community == === Support Channels === * [https://voidlinux.org/news/ Official blog] * IRC channels on Libera.Chat * Reddit community * GitHub repositories == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == 625644b4a281e899a8f51a39a83ec594b597d96f 4 556 4196 3073 2025-09-29T19:50:33Z Atmois 13 Update wiki staff wikitext text/x-wiki == About == atl.wiki is the official wiki by the [https://allthingslinux.org All Things Linux], a 501(c)(3) non-profit organisation. We aim to provide reliable and informative resources to users of all ability levels of Linux and adjacent FOSS software through information pages, guides, indexes and more! If you need Linux support, ensure to check out #quick-support and #support-forum in our [https://discord.gg/linux Discord server]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the #atl-wiki channel on the [https://discord.gg/linux Discord server]! To contact the administrators, check out our [[ATL:Contact|contact page]]! == Important Links == * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of atl.wiki * [[Contributing]] - Outlines how YOU can contribute to atl.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of atl.wiki * [[ATL:Disclaimer|General Disclaimer]] - atl.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Head of Wiki Operations * [[User:Kaizen|Kaizen]] - All Things Linux Founder & Owner * [[User:Scottc96|Scott96]] - Head of Systems ====== Operators ====== * [[User:Ow0cast]] - Wiki Team == History == ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the [https://discord.gg/linux All Things Linux discord]. [[User:Electron271|Electron271]], Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, [[User:Kaizen|Kaizen]]. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spambots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also reimplemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[Special:Favoritelist|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to relicence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another relicencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[ATL:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ====== August 2025 ====== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. With 1.0 we... ===== The Future ===== Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] 1a7e7cd05307a2195cee1e65e92ef705ac9a39d1 0 772 4199 4120 2025-10-01T08:29:20Z Hog 161 links wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:pythonlogo.png]] | title = Python | releasestatus = Maintained | lastrelease = 3.13.7 - 14 August 2025 | firstrelease = 0.9.0 - 20 February 1991 | languages = Python | developers = Python Software Foundation | designed by = Guido van Rossum | website = [https://python.org python.org] }} Python is a high-level [[:Category:Programming Languages|programming language]] originally designed by Guido van Rossum at Centrum Wiskunde & Informatica (CWI) in the Netherlands. It is known for its readability and beginner-friendly syntax. Van Rossum began working on Python in the late 1980s<ref>[http://www.artima.com/intv/pythonP.html The Making of Python], Bill Venners, 2003-01-13 (Accessed: 2025-08-09)</ref> as a successor to the ABC programming language. He released the first version (0.9.0)<ref>[https://python-history.blogspot.com/2009/01/brief-timeline-of-python.html The History of Python: A Brief Timeline of Python], Guido van Rossum, 2009-01-20 (Accessed: 2025-08-09)</ref> in 1991. Python 2 was released in 2000, followed by Python 3.0 in 2008. The final release of the Python 2 series, version 2.7.18, came out in 2020<ref>[https://pythoninsider.blogspot.com/2020/04/python-2718-last-release-of-python-2.html Python Insider: Python 2.7.18, the last release of Python 2], Benjamin Peterson, 2020-04-20 (Accessed: 2025-08-09)</ref> and was maintained until that day because Python 3 was not fully backward-compatible. Python is widely taught as a beginner’s programming language<ref>[https://survey.stackoverflow.co/2022/ Stack Overflow Developer Survey 2022], Stack Overflow, 2022-08-09 (Accessed: 2025-08-09)</ref> because many other languages have syntax similar to Python’s. The official Python website also offers audio and video tutorials for learning Python.<ref>[https://www.python.org/doc/av Audio/Video Instructional Materials for Python], Python Software Foundation, 2025-08-09 (Accessed: 2025-08-09)</ref> Python is currently the most used programming language among developers<ref>[https://www.tiobe.com/tiobe-index/ TIOBE Index], Paul Jansen, 2025-08-09 (Accessed: 2025-08-09)</ref>, used daily for lots of general-purpose software. Its simplicity and ease of installation guarantee quick and reliable support on almost all platforms and environments. It is also very popular due to its wide range of libraries, such as [https://discordpy.readthedocs.io/ Discord.py] (the same library used to develop [[Tux]] and Wikibot). Python comes preinstalled with an interpreter and also IDLE (Python's Integrated Development and Learning Environment), which serves as a basic IDE.<!-- However, the community generally prefers [https://code.visualstudio.com/ Visual Studio Code]<ref>https://medium.com/ml-and-dl/best-python-ide-why-vs-code-is-the-top-choice-for-developers-05aa74ad38eb</ref> because of its smooth, modern UI, ease of use, and integrations that help with developing projects and software. --> == pip (Package Manager) == [https://pypi.org/project/pip/ pip] is Python's Package Manager, through pip you can install all the libraries needed for your project to run. pip stands for "''pip Installs Packages"''<ref>[https://unix.stackexchange.com/questions/169709/what-does-pip-stand-for python - What does PIP stand for? - Unix & Linux Stack Exchange], Unix & Linux Stack Exchange, 2014-11-24 (Accessed: 2025-08-09)</ref>. pip connects to an online software repository (PyPI). pip was first introduced as ''pyinstall'' back in 2008 by Ian Bicking (creator of virtualenv package). In 2011, the Python Package Authority (PyPA) was created, it's goal was to take over and maintain pip and venv. === Installation for pip === Python 3.4+ included pip by default, if it's missing, use the following commands. ==== Method 1 - ensurepip ==== <syntaxhighlight lang="bash"> python -m ensurepip --upgrade </syntaxhighlight> ==== Method 2 - get-pip.py ==== # Download the script from https://bootstrap.pypa.io/get-pip.py. # Open a new [[terminal]] and [[cd]] to the folder containing the file # <code>python get-pip.py</code> === Installing packages with pip === {{Guide Warning}} pip install package-name == Virtual Environments (VENV) == The venv module allows users to create Virtual Environments each with their own independent modules and libraries, This is useful for isolating project dependencies or debugging. Created by Ian Bicking (the same developer who created pip), it is now maintained by the Python Package Authority (PyPA). == Installation == {{Guide Warning}} === Debian/Ubuntu Based === <syntaxhighlight lang="bash"> sudo apt update sudo apt install python3 python3-pip </syntaxhighlight> === Arch Based === <syntaxhighlight lang="bash"> sudo pacman -Syu python python-pip </syntaxhighlight> === Fedora/CentOS/RHEL 8+ === <syntaxhighlight lang="bash"> sudo yum install python3 python3-pip </syntaxhighlight> === CentOS/RHEL 7 === <syntaxhighlight lang="bash"> sudo yum install python3 python3-pip </syntaxhighlight> == '''Setup Python venv''' == {{Guide Warning}} When installing pip packages system-wide as root you will typically see a message like this one: <syntaxhighlight lang="shell-session"> [user@hostname ~]$ sudo pip install pyperclip Collecting pyperclip Downloading pyperclip-1.9.0.tar.gz (20 kB) Preparing metadata (setup.py) ... done Building wheels for collected packages: pyperclip Building wheel for pyperclip (setup.py) ... done Created wheel for pyperclip: filename=pyperclip-1.9.0-py3-none-any.whl size=11014 sha256=696d851be7b0d99fe8112ddf5c6ebc2b9444464b2a729911930d64bebc124c35 Stored in directory: /root/.cache/pip/wheels/cc/ae/36/ee17d1de094fcb61e24106cb329b5103861e819f94bef5e10a Successfully built pyperclip Installing collected packages: pyperclip Successfully installed pyperclip-1.9.0 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv </syntaxhighlight> Running pip as root can result in conflicts, broken packages and security risks.<ref>[https://askubuntu.com/questions/802544/is-sudo-pip-install-still-a-broken-practice package management - Is `sudo pip install` still a broken practice? - Ask Ubuntu], Ask Ubuntu, 2016-07-25 (Accessed: 2025-08-09)</ref> There are two possible responses to this situation: * See whether your distribution offers a system package to suit your needs. Depending on the distribution, system packages may be outdated, but this option should be tried first unless you are actively developing software. For example, with the Python module pyperclip mentioned above, there was a system package available that could fill the need, python3-pyperclip. * Or, if you are writing your own software, you can heed the warning as written and use the following instructions: python -m venv path/to/venv/ source path/to/venv/bin/activate The first line creates the folder containing the venv and the second line activates it. If you are not using bash, things may change slightly. For example, a user of the [[fish]] shell would instead run source venv/bin/activate.fish You'll know that a venv is currently active from an altered prompt such as this one: <syntaxhighlight lang="shell-session"> (venv) [user@hostname ~]$ </syntaxhighlight> With a venv loaded, all pip commands such as "pip install" and "pip uninstall" will affect only that venv. All Python code run with the venv's installation of Python will prefer to import the venv's libraries over any system libraries. (The command "which python" can help ensure that it is truly the venv Python as opposed to, say, the system "/usr/bin/python" that is running.) Lastly, a user who wishes to turn off a venv for the time being will only need to give the command "deactivate" to the shell. Further information about venv can be found in [https://docs.python.org/3/library/venv.html Python's official documentation]. == References == 03168f6a20abb0b02db0f2c300ec41b5828b4f00 8 357 4200 3511 2025-10-03T15:50:59Z Atmois 13 Disables the image zooming css text/css /* All CSS here will be loaded for users of the Citizen skin */ :root.skin-theme-clientpref-light:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #E1E2E7; } :root.citizen-feature-custom-width-clientpref-full :root.skin-theme-clientpref-night:not(.citizen-feature-pure-black-clientpref-1) { --color-surface-0: #11111b; } /*hsl(231, 42%, 76%)*/ :root { --color-primary__h: 231; --color-primary__s: 42%; --color-primary__l: 76%; } /* Disables the image zooming */ .citizen-card .citizen-card__image img, .citizen-card .citizen-card__image, a.image img, .mw-file-description img { transition: none; transform: scale(1); } .citizen-card:hover .citizen-card__image img, .citizen-card:hover .citizen-card__image, a.image:hover img, .mw-file-description:hover img { transform: scale(1); } /* * Footer icons * We use custom footer icons from https://starcitizen.tools for our footers, the following CSS comes from their wiki */ #footer-icons a { border: 0; padding: 0; background: transparent; opacity: var( --opacity-icon-base ); transition: opacity 250ms ease; } #footer-icons a:hover { opacity: var( --opacity-icon-base--hover ); } #footer-icons a:active { opacity: var( --opacity-icon-base--active ); } /* More space between icons */ #footer-icons ul, #footer-icons li { gap: var( --space-md ); } #footer-icons img { width: auto; height: 32px; } /* Divide footer links into two columns */ #footer-places { column-count: 2; } /* Fix misalignment in Safari and Firefox when using two columns */ #footer-places ul { display: initial; } /* Darken the footer icon in light mode */ .skin-citizen-light #footer-icons a { filter: invert( 1 ) hue-rotate( 180deg ); } 174a61fcc6a4853c4f78a1e64b9c79e011490bd8 0 1028 4201 2025-10-04T12:05:26Z Imnotgoodatnames 121 Created page, added sections for all major GnuDOS components wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | title = '''GnuDOS''' | image = [[File:GnuDOS editor Mino.svg|thumb]] | caption = Text editor mino, a part of GnuDOS | releasestatus = Maintained | lastrelease = 2.0 | languages = [[C]] | developers = Mohammed Isam | website = [https://www.gnu.org/software/gnudos/ GnuDOS home page.] }} '''GnuDOS''' is a [[GNU]] library designed to allow DOS users to easily start using GNU. GnuDOS consists of the core library ('''corelib'''), the text editor '''Mino''' and the file manager '''Prime'''.<ref name="GNU GnuDOS">[https://www.gnu.org/software/gnudos/ GnuDOS homepage], Free Software Foundation, July 20, 2024 (Accessed: 2025-10-04)</ref> == Mino == Mino is a [[TUI]] text editor designed to be user friendly and easy to use by DOS users. Mino provides a multi-level experience. There are six levels of complexity that determine the usable keybinds, ranging from "Newbie" that uses only DOS shortcut keys, to "Veteran" that uses only GNU keys.<ref name="Mino manual">[https://www.gnu.org/software/gnudos/mino/mino.html Mino manual page] (Accessed: 2025-10-04)</ref> == Prime == Prime is a file manager developed as part of GnuDOS. Like Mino, it offers a TUI interface is designed to be easy to use for users coming from DOS, and has six levels of experience.<ref name="Prime manual">[https://www.gnu.org/software/gnudos/prime/prime.html Prime manual page] (Accessed: 2025-10-04)</ref> == Corelib == The core library (corelib) contains four utilities: '''Kbd''', for handling keyboard input, '''UKbd''' for Unicode support, '''Screen''' for screen drawing and '''Dialogs''' for dialog boxes and windows. These components are defined by header files (eg. console/screen.h for the Screen utility).<ref name="GnuDOS manual">[https://www.gnu.org/software/gnudos/gnudos/gnudos.html GnuDOS manual page] (Accessed: 2025-10-04)</ref> 5b5d5547348f1beff12e4c7622b6c2b5d225ade9 6 1030 4203 2025-10-04T21:39:22Z Atmois 13 wikitext text/x-wiki The homescreen of the Fedora Mediawriter application. 7039f9bf568be49257f5cb1d4adb41385c4d1b91 3000 1031 4204 2025-10-04T22:02:20Z Atmois 13 Create base page for creating bootable media with fedora media writer wikitext text/x-wiki {{Guide Warning}}{{Work In Progress}} This is part of a series of articles on creating bootable media, you can see all the different options on the [[Guides:Creating Bootable Media|Creating Bootable Media]] article. You can also learn more about the uses of bootable media and the concepts behind it on the same page. Fedora Mediawriter can be used to flash '''any''' operating system to a USB drive however it has built in support to download Fedora ISO's automatically to flash to the drive. You will require an internet connection, a device with a USB port and a USB drive which is 16GB or larger. Most distributions will not require more than 8GB but some larger distributions may need a larger drive. ==Installing Fedora Mediawriter== ===Linux=== If you are on a Fedora Based Distribution you can install it by running:<syntaxhighlight lang="shell"> sudo dnf install mediawriter </syntaxhighlight> If you are on any other Linux distribution you can install it via Flatpak from [https://flathub.org/en/apps/org.fedoraproject.MediaWriter Flathub]:<syntaxhighlight lang="shell"> flatpak install flathub org.fedoraproject.MediaWriter </syntaxhighlight> You can also install it using the Nix package manager using the following command:<syntaxhighlight lang="shell"> nix-env -iA nixpkgs.mediawriter </syntaxhighlight> ===Windows or MacOS=== On every ISO download page you can find the download link for Fedora Media Writer, such as on the Fedora Workstation download page [https://fedoraproject.org/workstation/download here]. Once downloading the installer you can open it and go through the guided process to install it to your system. == Using Fedora Mediawriter to create a bootable USB == Once you have installed Fedora Mediawriter you can use it to either flash a Fedora edition or any other ISO file to your USB. You will need to download an ISO if your choosing and plug in your USB drive to your device. <blockquote>'''Remember''' '''that this USB drive will be erased and all data on it will be lost once you.'''</blockquote> [[File:Fedora Mediawriter Start Screen.png|alt=The start screen of the "Fedora Mediawriter" Application. With two options, "Download automatically", "Select .iso file" or "Restore USB" and an "About" and "Next" buttons.|thumb|403x403px|The home screen of Fedora Mediawriter]] If you wish to flash a Fedora edition you can follow through the "Download automatically" and it will let you select an edition of Fedora to flash to your USB drive. If you wish to install an alternate operating system you select the "Select .iso file" option and it will let you select an ISO file and an attached USB drive. Please ensure you select the correct drive as you will not be able to recover any data on this drive once you continue. After choosing the ISO file and USB drive and start the write process, you will need to wait up to 15 minutes for the drive to be flashed. Once it has flashed you will be able to unplug it or reboot to install your chosen operating system or try out a live environment for an operating system. Each distribution has a different installation process, so you will need to consult distribution specific documentation or check the wiki for a guide on your chosen distribution. 822ccaa6676555c8d02a9ea1c5e705fce7c4916e 0 763 4205 3911 2025-10-05T08:24:29Z Imnotgoodatnames 121 corrected dwm entry wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Screenshot of awesomewm4.png|link=awesomewm|awesome File:Compiz Shift Switcher.png|link=Compiz|Compiz File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:Twm.png|link=twm|twm File:Icewm-default.jpg|link=IceWM|IceWM File:I3-wm.png|link=i3|i3 File:Wmaker-0.80.2.png|link=Window_Maker|Window Maker File:Xmonad screenshot.png|link=Xmonad|XMonad </gallery> {| class="wikitable" |+ !Window Manager !Description |- |[[awesome]]<ref>[https://github.com/awesomeWM/awesome GitHub - awesomeWM/awesome: awesome window manager], awesomeWM, 2025-08-09 (Accessed: 2025-08-09)</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |[[Compiz]] |Compiz is a compositing window manager for the X Window System. |- |[[Openbox]] |A minimal and highly configurable stacking window manager written in C. |- |[[twm]]<ref>[https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml TWM], 2010-11-13 (Accessed: 2025-08-09)</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |[[IceWM]]<ref>[https://github.com/bbidulock/icewm GitHub - bbidulock/icewm: A window manager designed for speed, usability, and consistency], bbidulock, 2025-08-09 (Accessed: 2025-08-09)</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |[[i3]]<ref>[https://i3wm.org i3: improved tiling X11 window manager], Michael Stapelberg, 2025-06-12 (Accessed: 2025-08-09)</ref> |A tiling window manager for advanced users and developers. |- |[[Window Maker]]<ref>[https://github.com/window-maker/wmaker GitHub - window-maker/wmaker: Mirror of the official repository repo.or.cz/wmaker-crm.git. Do not send pull requests here, send your patches to wmaker-dev@googlegroups.com instead], window-maker, 2020-08-09 (Accessed: 2025-08-09)</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |[[XMonad]]<ref>[https://xmonad.org/ home | xmonad - the tiling window manager that rocks], xmonad, 2025-06-15 (Accessed: 2025-08-09)</ref> |Window Manager configurable via the Haskell functional programming language. |- |[[DWM|dwm]]<ref>[https://dwm.suckless.org/ dwm - dynamic window manager], Suckless, 2025-08-09 (Accessed: 2025-08-27) </ref> |A lightweight tiling window manager written in C. |} ==References== <references /> 297242264b6e968499f5cb5897bad51c3e9cddaa 0 661 4206 3629 2025-10-05T17:04:32Z Splayer 262 Added a better description; a features sub heading; table with variations and their respective features; Added links to official installation guides for various devices; add info about kali nethunter and kali purple. wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox | title = Kali Linux | image = [[File:Kali-dragon-icon.svg|frameless]] | caption = Kali Logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APT]] | defaultdesktops = [[Xfce]], [[GNOME]], [[KDE Plasma]] | usagetype = Desktop, Mobile, USB | architectures = x86_64, x86, armel, armhf | website = [https://www.kali.org/ Kali.org] }} Kali Linux (originally Backtrack Linux<ref>https://www.kali.org/docs/introduction/kali-linux-history/</ref>) is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, Digital forensics, and penetration testing. It is maintained and funded by [https://www.offsec.com/ Offensive Security]. === Features<ref>https://www.kali.org/docs/nethunter/</ref> === Kali Linux is supported in wide range of devices ranging from Raspberry pis to Modern Systems. It comes preinstalled with various tools useful for security professionals and includes a custom kernel patched for injection. It is also suitable for live USB boot with persistence. === Installation<ref name=":0">https://www.kali.org/docs/installation/</ref> === There are various ways to get Kali Linux. One can download the respective Kali version from the [https://www.kali.org/get-kali/#kali-platforms official download page]. {| class="wikitable mw-collapsible" |+Kali Variations<ref>www.kali.org/get-kali/#kali-installer-images</ref> !Variation !Function |- |ISO File |The most common way to install; suitable for both single and multi boot; providing the best performance. |- |Virtual Machine Image |Pre-built images for running Kali in a virtual machine; has higher system requirements. |- |ARM |Suitable for ARM devices; Not guaranteed a custom kernel; Some packages missing. |- |Mobile (Nethunter) |Kali for smartphones. |- |Cloud |Running Kali on a cloud server; Not guaranteed a custom kernel. |- |Containers |Quick and easy access to Kali using software such as Docker; No custom kernel; No direct access to hardware thus slow. |- |Live Boot (Recommended) |Quick and easy access to Kali on the go. The preferred method of using Kali Linux. |- |WSL |Using Kali in windows. |} A bare bones version of Kali can also be installed which has a headless size of 1.5G, the default Kali Linux is around 13G while the version with everything in it is around 34G.<ref>https://www.kali.org/docs/installation/installation-sizes/</ref> Full guide to installation size with various [https://atl.wiki/Desktop_Environments Desktop Environments] can be found [https://www.kali.org/docs/installation/installation-sizes/ here] . The system requirements vary but generally minimum of 2GB RAM and 20GB of disk space is needed to run Kali. Installation of Kali can be done fairly easily using the official GUI installer. The official guide to installing Kali are at:<ref name=":0" /> * [https://www.kali.org/docs/installation/hard-disk-install/ Hard Disk Install] * [https://www.kali.org/docs/installation/hard-disk-install-on-mac/ Mac Hardware] * [https://www.kali.org/docs/installation/dual-boot-kali-with-linux/ Dual Booting with Linux] (What's [[Dual Booting|Multi Booting]]) * [https://www.kali.org/docs/installation/dual-boot-kali-with-mac/ Dual Booting with MacOS] * [https://www.kali.org/docs/installation/dual-boot-kali-with-windows/ Dual Booting with Windows] === Other Versions === '''[https://www.kali.org/docs/nethunter/ Kali Nethunter]''' is the mobile version of Kali Linux, available for unrooted devices (Nethunter Rootless), rooted devices with custom recovery (Nethunter Lite),rooted devices with custom recovery and custom kernel (Nethunter) and on certain supported devices with '''full functionality''' (Nethunter Pro).<ref>https://www.kali.org/docs/nethunter/</ref> See [https://www.kali.org/docs/nethunter/#10-nethunter-editions Nethunter Editions] for detailed comparison between the editions and [[Kali Nethunter]] for more details. '''[https://gitlab.com/kalilinux/kali-purple/documentation/-/wikis/home Kali Purple]''' is the enterprise grade version of Kali which comes with over a 100 hundred tools, Kali Autopilot (automatic script builder) and its own wiki. * <references /> [[Category:Linux Distributions]] 1820a119fd4a23f3c05985556125718c0caec82d 0 1032 4207 2025-10-05T17:36:18Z Gamiel72 288 I'm making the page for GrapheneOS - I'm switching browser tabs so i will complete the page wikitext text/x-wiki '''GrapheneOS''' is an Android-Based Operating System d5713501d4df53d1fea63bf55853588ed73ac5e1 0 174 4208 3680 2025-10-05T17:59:53Z Maningreen 217 Added VTY to the table of terminal manipulation libraries. wikitext text/x-wiki {{Cleanup|Incomplete page}} [[Category:Terminology]] [[File:Btop.png|alt=Btop System Monitor|thumb|Btop, a terminal-based system monitoring tool.]] A terminal user interface (TUI) is a form of user interface where a program prints special characters that are interpreted by the terminal renderer and are completely invisible, but manipulate the way the terminal renders stuff like for example changing the color of the following text, moving the cursor to an arbitrary place in the terminal, making text bold, making text italic, changing the color palette of the Linux TTY, and so much more. The program can also read in keyboard input by reading special character sequences in sent by the terminal driver. '''<u>FUN FACT</u>''': You may have tried using your arrow keys once or twice to move your cursor in a prompt from a program such as the [[Pacman]] package manager or something else that throws prompts for the user to answer. You may have noticed that instead of moving your cursor, the arrow keys send "garbage" text ("^[[D^[[C^[[A^[[B"). Programs such as [https://www.gnu.org/software/bash/ Bash] are able to move your cursor when you hit the arrow keys by actually reading and interpreting this "garbage" text in real-time using a terminal configuration mode called "raw mode" which is when the terminal disables a bunch of buffering settings that would normally require you to press ENTER before the terminal can see your user input. {| class="wikitable" |+Terminal Manipulation Libraries !Library !Language !Developer !Description |- |[https://gitlab.com/Oglo12/otmlib Oglo's Terminal Manipulation Library] |[[C (programming language)|C]] |Jackson Novak (OgloTheNerd) |A single-header C99 library for manipulating the terminal. |- |[https://invisible-island.net/ncurses/ NCurses] |[[C (programming language)|C]] |Thomas Dickey |A library installed on most Linux and BSD systems for creating terminal user interfaces. |- |[https://crates.io/crates/crossterm Crossterm] |[[Rust]] |Timon |A cross-platform terminal manipulation library written in Rust. |- |[https://github.com/termbox/termbox2 Termbox2] |[[C (programming language)|C]] |Adam |A suckless single-header C library for manipulating the terminal. |- |[https://hackage.haskell.org/package/vty vty] |[[Haskell]] |Jonathan Daugherty |A TUI library in the niche of NCurses for Haskell. |} 5598bc1ad83319d2bf68394ac87ee475d249e8ae 0 1032 4209 4207 2025-10-05T18:02:07Z Gamiel72 288 i need to finish this later wikitext text/x-wiki '''GrapheneOS''' is an Android-Based Operating System that is privacy and security focused. GrapheneOS has regular updates and is usually the fastest at updating their OS compared to other Customized Android-Based Operating Systems. == History == GrapheneOS was founded by Daniel Macay in late 2014, starting as a solo project incorporating his previous open source privacy/security work. The project initially created a port of OpenBSD malloc to Android's Bionic libc and a port of the PaX kernel patches to the kernel of GrapheneOS's supported devices. It quickly expanded to a lot of privacy and security improvements, particularly low-level hardening on the compiler toolchain and Bionic. Code began landing on AOSP and upstream projects. 57d3b791772df2f9dd91fb3fdbd1bc386e5af84b 4211 4209 2025-10-05T18:13:47Z Gamiel72 288 added an like those informational columns i cant bother to go look up the name :sob: and also a little bit of history wikitext text/x-wiki {{DistributionInfobox|architectures=ARM64|caption=The GrapheneOS logo|defaultdesktops=Android User Interface|image=[[File:GrapheneOS-logo-black.png|GrapheneOS-logo-black]]|packagemanager=Android Package Manager (not acessible)|releasemodel=Fixed Releases|releasestatus=Currently Maintained|title=GrapheneOS|usagetype=Mobile|website=[https://grapheneos.org grapheneos.org]}} '''GrapheneOS''' is an Android-Based Operating System that is privacy and security focused. GrapheneOS has regular updates and is usually the fastest at updating their OS compared to other Customized Android-Based Operating Systems. == History == GrapheneOS was founded by Daniel Macay in late 2014, starting as a solo project incorporating his previous open source privacy/security work. The project initially created a port of OpenBSD malloc to Android's Bionic libc and a port of the PaX kernel patches to the kernel of GrapheneOS's supported devices. It quickly expanded to a lot of privacy and security improvements, particularly low-level hardening on the compiler toolchain and Bionic. Code began landing on AOSP and upstream projects. eb8d16b62666bc13b71d33a71dbfe689521cf205 4212 4211 2025-10-05T18:16:39Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | architectures = ARM64 | caption = The GrapheneOS logo | defaultdesktops = Android User Interface | image = [[File:GrapheneOS-logo-black.png|GrapheneOS-logo-black]] | packagemanager = Android Package Manager (not acessible) | releasemodel = Fixed Releases | releasestatus = Currently Maintained | title = GrapheneOS | usagetype = Mobile | website = [https://grapheneos.org grapheneos.org] }} '''GrapheneOS''' is an Android-Based Operating System that is privacy and security focused. GrapheneOS has regular updates and is usually the fastest at updating their OS compared to other Customized Android-Based Operating Systems. == History == GrapheneOS was founded by Daniel Macay in late 2014, starting as a solo project incorporating his previous open source privacy/security work. The project initially created a port of OpenBSD malloc to Android's Bionic libc and a port of the PaX kernel patches to the kernel of GrapheneOS's supported devices. It quickly expanded to a lot of privacy and security improvements, particularly low-level hardening on the compiler toolchain and Bionic. Code began landing on AOSP and upstream projects. 0245681d448c2eefa811d99461d1d1baec8566e6 4215 4212 2025-10-05T18:25:04Z Madonuko 140 format wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}}{{Needs Citations}} {{DistributionInfobox | architectures = ARM64 | caption = The GrapheneOS logo | defaultdesktops = Android User Interface | image = [[File:GrapheneOS-logo-black.png|GrapheneOS-logo-black]] | packagemanager = Android Package Manager (not acessible) | releasemodel = Fixed Releases | releasestatus = Currently Maintained | title = GrapheneOS | usagetype = Mobile | website = [https://grapheneos.org grapheneos.org] }} '''GrapheneOS''' is an [[Android]]-based [[OS|operating system]] focusing on privacy and security. It usually receives the fastest updates compared to other customized Android-based systems. == History == GrapheneOS was founded by Daniel Macay in late 2014, starting as a solo project incorporating his previous open source privacy/security work. The project initially created a port of [[OpenBSD]] [[malloc]] to Android's Bionic [[libc]] and a port of the PaX [[kernel]] [[patch]]es to the kernel of GrapheneOS's supported devices. It quickly expanded to a lot of privacy and security improvements, particularly low-level [[hardening]] on the [[compiler]] toolchain and Bionic. Code began landing on AOSP and upstream projects. 5bd2a26f3371cc6322eeaf63e356f6f9c0875fe7 4219 4215 2025-10-06T09:44:36Z Splayer 262 basic citation to the existing text, added reference section. wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}}{{Needs Citations}} {{DistributionInfobox | architectures = ARM64 | caption = The GrapheneOS logo | defaultdesktops = Android User Interface | image = [[File:GrapheneOS-logo-black.png|GrapheneOS-logo-black]] | packagemanager = Android Package Manager (not acessible) | releasemodel = Fixed Releases | releasestatus = Currently Maintained | title = GrapheneOS | usagetype = Mobile | website = [https://grapheneos.org grapheneos.org] }} '''GrapheneOS''' (previously CopperheadOS<ref>https://grapheneos.org/history/copperheados</ref>) is an [[Android]]-based [[OS|operating system]] focusing on privacy and security.<ref>https://grapheneos.org/#about</ref> It usually receives the fastest updates compared to other customized Android-based systems. == History == GrapheneOS was founded by Daniel Macay in late 2014, starting as a solo project incorporating his previous open source privacy/security work. The project initially created a port of [[OpenBSD]] [[malloc]] to Android's Bionic [[libc]] and a port of the PaX [[kernel]] [[patch]]es to the kernel of GrapheneOS's supported devices. It quickly expanded to a lot of privacy and security improvements, particularly low-level [[hardening]] on the [[compiler]] toolchain and Bionic. Code began landing on AOSP and upstream projects.<ref>https://grapheneos.org/history/</ref> === References === <references /> 17bc797f960b96bea334f44f92d1a5dfc6e1b430 4223 4219 2025-10-12T08:28:23Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}}{{Needs Citations}} {{DistributionInfobox | architectures = ARM64 | caption = The GrapheneOS logo | defaultdesktops = Android User Interface | image = [[File:GrapheneOS-logo-black.png|GrapheneOS-logo-black]] | packagemanager = Android Package Manager (not acessible) | releasemodel = Fixed Releases | releasestatus = Currently Maintained | title = GrapheneOS | usagetype = Mobile | website = [https://grapheneos.org grapheneos.org] }} '''GrapheneOS''' (previously CopperheadOS<ref>[https://grapheneos.org/history/copperheados CopperheadOS | History], GrapheneOS, 2025-09-24 (Accessed: 2025-10-12)</ref>) is an [[Android]]-based [[OS|operating system]] focusing on privacy and security.<ref>[https://grapheneos.org/#about GrapheneOS: the private and secure mobile OS], GrapheneOS, 2025-09-24 (Accessed: 2025-10-12)</ref> It usually receives the fastest updates compared to other customized Android-based systems. == History == GrapheneOS was founded by Daniel Macay in late 2014, starting as a solo project incorporating his previous open source privacy/security work. The project initially created a port of [[OpenBSD]] [[malloc]] to Android's Bionic [[libc]] and a port of the PaX [[kernel]] [[patch]]es to the kernel of GrapheneOS's supported devices. It quickly expanded to a lot of privacy and security improvements, particularly low-level [[hardening]] on the [[compiler]] toolchain and Bionic. Code began landing on AOSP and upstream projects.<ref>[https://grapheneos.org/history/ History], GrapheneOS, 2025-09-24 (Accessed: 2025-10-12)</ref> === References === <references /> 8e4c91422e797682ee844aebcc5dd40ade648506 6 1033 4210 2025-10-05T18:04:51Z Gamiel72 288 the GrapheneOS logo in black wikitext text/x-wiki == Summary == the GrapheneOS logo in black 1ae76663d276113917ed0a282740cac4f1c60d6e 0 1028 4213 4201 2025-10-05T18:17:43Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | title = '''GnuDOS''' | image = [[File:GnuDOS editor Mino.svg|thumb]] | caption = Text editor mino, a part of GnuDOS | releasestatus = Maintained | lastrelease = 2.0 | languages = [[C]] | developers = Mohammed Isam | website = [https://www.gnu.org/software/gnudos/ GnuDOS home page.] }} '''GnuDOS''' is a [[GNU]] library designed to allow DOS users to easily start using GNU. GnuDOS consists of the core library ('''corelib'''), the text editor '''Mino''' and the file manager '''Prime'''.<ref name="GNU GnuDOS">[https://www.gnu.org/software/gnudos/ GnuDOS homepage], Free Software Foundation, July 20, 2024 (Accessed: 2025-10-04)</ref> == Mino == Mino is a [[TUI]] text editor designed to be user friendly and easy to use by DOS users. Mino provides a multi-level experience. There are six levels of complexity that determine the usable keybinds, ranging from "Newbie" that uses only DOS shortcut keys, to "Veteran" that uses only GNU keys.<ref name="Mino manual">[https://www.gnu.org/software/gnudos/mino/mino.html Mino manual page] (Accessed: 2025-10-04)</ref> == Prime == Prime is a file manager developed as part of GnuDOS. Like Mino, it offers a TUI interface is designed to be easy to use for users coming from DOS, and has six levels of experience.<ref name="Prime manual">[https://www.gnu.org/software/gnudos/prime/prime.html Prime manual page] (Accessed: 2025-10-04)</ref> == Corelib == The core library (corelib) contains four utilities: '''Kbd''', for handling keyboard input, '''UKbd''' for Unicode support, '''Screen''' for screen drawing and '''Dialogs''' for dialog boxes and windows. These components are defined by header files (eg. console/screen.h for the Screen utility).<ref name="GnuDOS manual">[https://www.gnu.org/software/gnudos/gnudos/gnudos.html GnuDOS manual page] (Accessed: 2025-10-04)</ref> f9ce139e7e2b60d60bce611e8413d06b8ab55663 0 661 4214 4206 2025-10-05T18:20:44Z Madonuko 140 format wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Kali Linux | image = [[File:Kali-dragon-icon.svg|frameless]] | caption = Kali Logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APT]] | defaultdesktops = [[Xfce]], [[GNOME]], [[KDE Plasma]] | usagetype = Desktop, Mobile, USB | architectures = x86_64, x86, armel, armhf | website = [https://www.kali.org/ Kali.org] }} Kali Linux (originally Backtrack Linux<ref>https://www.kali.org/docs/introduction/kali-linux-history/</ref>) is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, Digital forensics, and penetration testing. It is maintained and funded by [https://www.offsec.com/ Offensive Security]. === Features === Kali Linux is supported in wide range of devices ranging from Raspberry pis to Modern Systems. It comes preinstalled with various tools useful for security professionals and includes a custom kernel patched for injection. It is also suitable for live USB boot with persistence.<ref>https://www.kali.org/docs/nethunter/</ref> === Installation === There are various ways to get Kali Linux. One can download the respective Kali version from the [https://www.kali.org/get-kali/#kali-platforms official download page].<ref name=":0">https://www.kali.org/docs/installation/</ref> {| class="wikitable mw-collapsible" |+Kali Variations<ref>www.kali.org/get-kali/#kali-installer-images</ref> !Variation !Function |- |ISO File |The most common way to install; suitable for both single and multi boot; providing the best performance. |- |Virtual Machine Image |Pre-built images for running Kali in a virtual machine; has higher system requirements. |- |ARM |Suitable for ARM devices; Not guaranteed a custom kernel; Some packages missing. |- |Mobile (Nethunter) |Kali for smartphones. |- |Cloud |Running Kali on a cloud server; Not guaranteed a custom kernel. |- |Containers |Quick and easy access to Kali using software such as Docker; No custom kernel; No direct access to hardware thus slow. |- |Live Boot (Recommended) |Quick and easy access to Kali on the go. The preferred method of using Kali Linux. |- |WSL |Using Kali in windows. |} A bare bones version of Kali can also be installed which has a headless size of 1.5G, the default Kali Linux is around 13G while the version with everything in it is around 34G.<ref>https://www.kali.org/docs/installation/installation-sizes/</ref> Full guide to installation size with various [https://atl.wiki/Desktop_Environments Desktop Environments] can be found [https://www.kali.org/docs/installation/installation-sizes/ here] . The system requirements vary but generally minimum of 2GB RAM and 20GB of disk space is needed to run Kali. Installation of Kali can be done fairly easily using the official GUI installer. The official guide to installing Kali are at:<ref name=":0" /> * [https://www.kali.org/docs/installation/hard-disk-install/ Hard Disk Install] * [https://www.kali.org/docs/installation/hard-disk-install-on-mac/ Mac Hardware] * [https://www.kali.org/docs/installation/dual-boot-kali-with-linux/ Dual Booting with Linux] (What's [[Dual Booting|Multi Booting]]) * [https://www.kali.org/docs/installation/dual-boot-kali-with-mac/ Dual Booting with MacOS] * [https://www.kali.org/docs/installation/dual-boot-kali-with-windows/ Dual Booting with Windows] === Other Versions === '''[https://www.kali.org/docs/nethunter/ Kali Nethunter]''' is the mobile version of Kali Linux, available for unrooted devices (Nethunter Rootless), rooted devices with custom recovery (Nethunter Lite),rooted devices with custom recovery and custom kernel (Nethunter) and on certain supported devices with '''full functionality''' (Nethunter Pro).<ref>https://www.kali.org/docs/nethunter/</ref> See [https://www.kali.org/docs/nethunter/#10-nethunter-editions Nethunter Editions] for detailed comparison between the editions and [[Kali Nethunter]] for more details. '''[https://gitlab.com/kalilinux/kali-purple/documentation/-/wikis/home Kali Purple]''' is the enterprise grade version of Kali which comes with over a 100 hundred tools, Kali Autopilot (automatic script builder) and its own wiki. == References == c0b90e24b131fefacf1372f5696dd4f53c9204d0 4218 4214 2025-10-06T09:26:30Z Splayer 262 added trademark according to https://www.kali.org/docs/policy/trademark/ wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Kali Linux | image = [[File:Kali-dragon-icon.svg|frameless]] | caption = Kali Logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APT]] | defaultdesktops = [[Xfce]], [[GNOME]], [[KDE Plasma]] | usagetype = Desktop, Mobile, USB | architectures = x86_64, x86, armel, armhf | website = [https://www.kali.org/ Kali.org] }} '''Kali Linux''' (originally Backtrack Linux<ref>https://www.kali.org/docs/introduction/kali-linux-history/</ref>) is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, Digital forensics, and penetration testing. It is maintained and funded by [https://www.offsec.com/ '''Offensive Security''']. === Features === Kali Linux is supported in wide range of devices ranging from Raspberry pis to Modern Systems. It comes preinstalled with various tools useful for security professionals and includes a custom kernel patched for injection. It is also suitable for live USB boot with persistence.<ref>https://www.kali.org/docs/nethunter/</ref> === Installation === There are various ways to get Kali Linux. One can download the respective Kali version from the [https://www.kali.org/get-kali/#kali-platforms official download page].<ref name=":0">https://www.kali.org/docs/installation/</ref> {| class="wikitable mw-collapsible" |+Kali Variations<ref>www.kali.org/get-kali/#kali-installer-images</ref> !Variation !Function |- |ISO File |The most common way to install; suitable for both single and multi boot; providing the best performance. |- |Virtual Machine Image |Pre-built images for running Kali in a virtual machine; has higher system requirements. |- |ARM |Suitable for ARM devices; Not guaranteed a custom kernel; Some packages missing. |- |Mobile (Nethunter) |Kali for smartphones. |- |Cloud |Running Kali on a cloud server; Not guaranteed a custom kernel. |- |Containers |Quick and easy access to Kali using software such as Docker; No custom kernel; No direct access to hardware thus slow. |- |Live Boot (Recommended) |Quick and easy access to Kali on the go. The preferred method of using Kali Linux. |- |WSL |Using Kali in windows. |} A bare bones version of Kali can also be installed which has a headless size of 1.5G, the default Kali Linux is around 13G while the version with everything in it is around 34G.<ref>https://www.kali.org/docs/installation/installation-sizes/</ref> Full guide to installation size with various [https://atl.wiki/Desktop_Environments Desktop Environments] can be found [https://www.kali.org/docs/installation/installation-sizes/ here] . The system requirements vary but generally minimum of 2GB RAM and 20GB of disk space is needed to run Kali. Installation of Kali can be done fairly easily using the official GUI installer. The official guide to installing Kali are at:<ref name=":0" /> * [https://www.kali.org/docs/installation/hard-disk-install/ Hard Disk Install] * [https://www.kali.org/docs/installation/hard-disk-install-on-mac/ Mac Hardware] * [https://www.kali.org/docs/installation/dual-boot-kali-with-linux/ Dual Booting with Linux] (What's [[Dual Booting|Multi Booting]]) * [https://www.kali.org/docs/installation/dual-boot-kali-with-mac/ Dual Booting with MacOS] * [https://www.kali.org/docs/installation/dual-boot-kali-with-windows/ Dual Booting with Windows] === Other Versions === '''[https://www.kali.org/docs/nethunter/ Kali Nethunter]''' is the mobile version of Kali Linux, available for unrooted devices (Nethunter Rootless), rooted devices with custom recovery (Nethunter Lite),rooted devices with custom recovery and custom kernel (Nethunter) and on certain supported devices with '''full functionality''' (Nethunter Pro).<ref>https://www.kali.org/docs/nethunter/</ref> See [https://www.kali.org/docs/nethunter/#10-nethunter-editions Nethunter Editions] for detailed comparison between the editions and [[Kali Nethunter]] for more details. '''[https://gitlab.com/kalilinux/kali-purple/documentation/-/wikis/home Kali Purple]''' is the enterprise grade version of Kali which comes with over a 100 hundred tools, Kali Autopilot (automatic script builder) and its own wiki. == References == <references /> === Footnotes === * KALI LINUX ™ is a trademark of [https://www.offsec.com/ OffSec]. bdf6aba855a4a0037554c8cdecdcd14d01f2ceca 0 651 4216 4130 2025-10-05T18:39:35Z Madonuko 140 almost a rewrite wikitext text/x-wiki [[category:terminology]] {{stub}} An ''operating system'' (usually abbreviated as ''OS'') is the software layer responsible for providing an interface for users — a ''[[user interface]] (UI)'' to interact with the hardware. Technically, it is composed of a collection of [[software]] that performs the basic minimal tasks for a functional system, especially for allocating resources, including memory, CPU, input/output devices and file storage.<ref>[https://www.ibm.com/think/topics/operating-systems What is an Operating System? | IBM], Stephanie Susnjara & Ian Smalley, 2025-03-05 (Accessed: 2025-08-09)</ref> Main components of an OS include the [[bootloader]], [[kernel]], and [[drivers]]. Other system components may also be regarded as part of an OS, depending on definitions. == References == ffb541ed72b55a5bb3d664d671a4efc3cd4ce510 0 1034 4217 2025-10-06T08:05:32Z Splayer 262 made the Snap page and added some basic info and links. could make it more detailed in future for a guide for each distro? wikitext text/x-wiki Snap is a package management system aimed for desktops, cloud and IoT devices. The respective packages are termed as '''snaps''' which is a bundle of an app along with its dependencies which works across [[Linux Distributions|Linux distributions]].<ref>https://snapcraft.io/about</ref> Snapd is the background service that manages and maintain the installed snaps.<ref name=":0">https://snapcraft.io/docs/installing-snapd</ref> The various snaps can be downloaded using the [https://snapcraft.io/store Snap Store]. One can build and publish snaps using [https://documentation.ubuntu.com/snapcraft/stable/ Snapcraft]. === Installation === Snapd needs to be running before a snap can be installed. It comes preinstalled with a few distributions by default such as [https://neon.kde.org/ KDE Neon], [[Manjaro]], [https://getsol.us/ Solus], [[Ubuntu]], Most [https://wiki.ubuntu.com/DerivativeTeam/Derivatives#Official_Ubuntu_Flavors Ubuntu Flavours] and [[ZorinOS]]. For distributions without Snapd preinstalled, one can refer to [https://snapcraft.io/docs/installing-snapd#without-snap this section] of the official documentation and choose their respective documentation to install Snapd.<ref name=":0" /> After installing Snapd, one can head over to [https://snapcraft.io/store Snap Store] for searching and installing the software they want.<ref>https://www.geeksforgeeks.org/linux-unix/snap-package-manager-on-ubuntu/</ref> === References === <references /> 83677efd3048cd9d5c056addc280f9f4b3239d72 2 1035 4220 2025-10-06T10:08:06Z Splayer 262 added some info wikitext text/x-wiki Hello! I am a computer and tech enthusiast from India! Contact me on discord, username: splayer_1 a2a88c6e526572209c6f1402fa3c422ebb44ad2e 6 1036 4221 2025-10-06T10:12:38Z Splayer 262 Kali Nethunter Logo wikitext text/x-wiki == Summary == Kali Nethunter Logo == Licensing == {{Unknown_copyright}} 4b30ae5f9d6e8c3d59cdb67483fab1824a0c4be1 3000 1031 4222 4204 2025-10-07T16:25:08Z Atmois 13 Reorganise to fix the position of the image wikitext text/x-wiki {{Guide Warning}}{{Work In Progress}} This is part of a series of articles on creating bootable media, you can see all the different options on the [[Guides:Creating Bootable Media|Creating Bootable Media]] article. You can also learn more about the uses of bootable media and the concepts behind it on the same page. Fedora Mediawriter can be used to flash '''any''' operating system to a USB drive however it has built in support to download Fedora ISO's automatically to flash to the drive. You will require an internet connection, a device with a USB port and a USB drive which is 16GB or larger. Most distributions will not require more than 8GB but some larger distributions may need a larger drive. ==Installing Fedora Mediawriter== ===Linux=== If you are on a Fedora Based Distribution you can install it by running:<syntaxhighlight lang="shell"> sudo dnf install mediawriter </syntaxhighlight> If you are on any other Linux distribution you can install it via Flatpak from [https://flathub.org/en/apps/org.fedoraproject.MediaWriter Flathub]:<syntaxhighlight lang="shell"> flatpak install flathub org.fedoraproject.MediaWriter </syntaxhighlight> You can also install it using the Nix package manager using the following command:<syntaxhighlight lang="shell"> nix-env -iA nixpkgs.mediawriter </syntaxhighlight> ===Windows or MacOS=== On every ISO download page you can find the download link for Fedora Media Writer, such as on the Fedora Workstation download page [https://fedoraproject.org/workstation/download here]. Once downloading the installer you can open it and go through the guided process to install it to your system. == Using Fedora Mediawriter to create a bootable USB == [[File:Fedora Mediawriter Start Screen.png|alt=The start screen of the "Fedora Mediawriter" Application. With two options, "Download automatically", "Select .iso file" or "Restore USB" and an "About" and "Next" buttons.|thumb|403x403px|The home screen of Fedora Mediawriter]] Once you have installed Fedora Mediawriter you can use it to either flash a Fedora edition or any other ISO file to your USB. You will need to download an ISO if your choosing and plug in your USB drive to your device. <blockquote>'''Remember''' '''that this USB drive will be erased and all data on it will be lost once you.'''</blockquote> If you wish to flash a Fedora edition you can follow through the "Download automatically" and it will let you select an edition of Fedora to flash to your USB drive. If you wish to install an alternate operating system you select the "Select .iso file" option and it will let you select an ISO file and an attached USB drive. Please ensure you select the correct drive as you will not be able to recover any data on this drive once you continue. After choosing the ISO file and USB drive and start the write process, you will need to wait up to 15 minutes for the drive to be flashed. Once it has flashed you will be able to unplug it or reboot to install your chosen operating system or try out a live environment for an operating system. Each distribution has a different installation process, so you will need to consult distribution specific documentation or check the wiki for a guide on your chosen distribution. 718d95dc84aecd128990e612c5719a9a73975cc9 4226 4222 2025-10-14T16:04:06Z Atmois 13 Fix typo and remove banner wikitext text/x-wiki {{Guide Warning}}This is part of a series of articles on creating bootable media, you can see all the different options on the [[Guides:Creating Bootable Media|Creating Bootable Media]] article. You can also learn more about the uses of bootable media and the concepts behind it on the same page. Fedora Mediawriter can be used to flash '''any''' operating system to a USB drive however it has built in support to download Fedora ISO's automatically to flash to the drive. You will require an internet connection, a device with a USB port and a USB drive which is 16GB or larger. Most distributions will not require more than 8GB but some larger distributions may need a larger drive. ==Installing Fedora Mediawriter== ===Linux=== If you are on a Fedora Based Distribution you can install it by running:<syntaxhighlight lang="shell"> sudo dnf install mediawriter </syntaxhighlight> If you are on any other Linux distribution you can install it via Flatpak from [https://flathub.org/en/apps/org.fedoraproject.MediaWriter Flathub]:<syntaxhighlight lang="shell"> flatpak install flathub org.fedoraproject.MediaWriter </syntaxhighlight> You can also install it using the Nix package manager using the following command:<syntaxhighlight lang="shell"> nix-env -iA nixpkgs.mediawriter </syntaxhighlight> ===Windows or MacOS=== On every ISO download page you can find the download link for Fedora Media Writer, such as on the Fedora Workstation download page [https://fedoraproject.org/workstation/download here]. Once you have downloaded the installer you can open it and go through the guided process to install it to your system. == Using Fedora Mediawriter to create a bootable USB == [[File:Fedora Mediawriter Start Screen.png|alt=The start screen of the "Fedora Mediawriter" Application. With two options, "Download automatically", "Select .iso file" or "Restore USB" and an "About" and "Next" buttons.|thumb|403x403px|The home screen of Fedora Mediawriter]] Once you have installed Fedora Mediawriter you can use it to either flash a Fedora edition or any other ISO file to your USB. You will need to download an ISO if your choosing and plug in your USB drive to your device. <blockquote>'''Remember''' '''that this USB drive will be erased and all data on it will be lost once you.'''</blockquote> If you wish to flash a Fedora edition you can follow through the "Download automatically" and it will let you select an edition of Fedora to flash to your USB drive. If you wish to install an alternate operating system you select the "Select .iso file" option and it will let you select an ISO file and an attached USB drive. Please ensure you select the correct drive as you will not be able to recover any data on this drive once you continue. After choosing the ISO file and USB drive and start the write process, you will need to wait up to 15 minutes for the drive to be flashed. Once it has flashed you will be able to unplug it or reboot to install your chosen operating system or try out a live environment for an operating system. Each distribution has a different installation process, so you will need to consult distribution specific documentation or check the wiki for a guide on your chosen distribution. 6df96cd0cb86cd04ff72d0c1beb78ad0b9705970 0 733 4224 3394 2025-10-12T14:45:06Z S1oplus 180 /* Devices with M1 */ removed the m1 macbook pro image that was inside the devices list for whatever reason wikitext text/x-wiki '''Apple M1''' is a series of [[ARM|ARM-based]] system-on-a-chip (SoC) designed by [[Apple|Apple Inc]]., launched 2020 to 2022. It is part of the Apple silicon series, as a [[central processing unit]] (CPU) and [[graphics processing unit]] (GPU) for its Mac desktops and notebooks, and the iPad Pro and iPad Air tablets. [https://www.gsmarena.com/the_apple_m1_is_the_first_armbased_chipset_for_macs_with_the_fastest_cpu_cores_and_top_igpu-news-46222.php]The M1 chip initiated Apple's third change to the instruction set architecture used by Macintosh computers, switching from Intel to Apple silicon fourteen years after they were switched from PowerPC to Intel, and twenty-six years after the transition from the original Motorola 68000 series to PowerPC. At the time of its introduction in 2020, Apple said that the M1 had "the world's fastest CPU core in low power silicon" and the world's best CPU performance per watt.[https://en.wikipedia.org/wiki/Apple_M1#:~:text=Apple%20M1%20is,Conference%20(WWDC).] [[File:Apple M1 no heatsink.png|alt=M1 no heatsink|thumb|Apple M1 with no heatsink]] The M1 was first launched in November 2020, a few months later in October 2021, the Professional-focused M1 Pro and M1 Max were launched, with M1 Max being a higher powered version of the M1 Pro, with a beefier GPU and more memory bandwidth. in 2022 Apple launched the M1 Ultra, connecting 2 M1 Max chips, These chips differ largely in size and the number of functional units: for example, while the original M1 has about 16 billion transistors, the M1 Ultra has 114 billion.<ref>[https://www.apple.com/newsroom/2022/03/apple-unveils-m1-ultra-the-worlds-most-powerful-chip-for-a-personal-computer/ Apple unveils M1 Ultra, the world’s most powerful chip for a personal computer], Apple, 2022-03-08 (Accessed: 2025-08-09)</ref> The M1 runs Apple's [[macOS]] and [[iPadOS]], Initial support for the M1 SoC in the [[Linux|Linux kernel]] was released in version 5.13 on June 27, 2021.[https://9to5mac.com/2021/06/28/linux-kernel-5-13-officially-launches-with-support-for-m1-macs/] == M1 Chip Variants == === A14 === [[File:Apple A14.jpg|thumb|Apple A14 Bionic, the chip M1 is based on.]] The Apple A14 Bionic features an Apple-designed 64-bit, six-core CPU, implementing ARMv8 with two high-performance cores called “Firestorm” and four energy-efficient cores called “Icestorm”.<ref>[https://www.youtube.com/live/KR0g-1hnQPA?si=0l-0ixbkIdH8_pLf Apple Event — October 13 - YouTube], Apple, 2020-10-13 (Accessed: 2025-08-09)</ref> The M1 has four high-performance "Firestorm" and four energy-efficient "Icestorm" cores, first seen on the A14 Bionic. It has a hybrid configuration similar to ARM big. LITTLE and Intel's Lakefield processors. This combination allows power-use optimizations not possible with previous Apple–Intel architecture devices. Apple claims the energy-efficient cores use one-tenth the power of the high-performance ones. The high-performance cores have an unusually large 192 KB of L1 instruction cache and 128 KB of L1 data cache and share a 12 MB L2 cache; the energy-efficient cores have a 128 KB L1 instruction cache, 64 KB L1 data cache, and a shared 4 MB L2 cache. The SoC also has an 8 MB System Level Cache shared by the GPU.<ref>[https://www.youtube.com/watch?v=BCvL8O0-Qwo Apple Unveils M1 Ultra Chip (Full Reveal) - YouTube], CNET Highlights, 2022-03-08 (Accessed: 2025-08-09)</ref> === M1 Pro and M1 Max === The M1 Pro and M1 Max use the same ARM big.LITTLE design as the M1, with eight high-performance "Firestorm" (six in the lower-binned variants of the M1 Pro) and two energy-efficient "Icestorm" cores, providing a total of ten cores (eight in the lower-binned variants of the M1 Pro). The high-performance cores are clocked at 3228 MHz, and the high-efficiency cores are clocked at 2064 MHz. The eight high-performance cores are split into two clusters. Each high-performance cluster shares 12 MB of L2 cache. The two high-efficiency cores share 4 MB of L2 cache. The M1 Pro and M1 Max have 24 MB and 48 MB respectively of system level cache (SLC).<ref>[https://www.anandtech.com/show/17024/apple-m1-max-performance-review Apple M1 Pro and M1 Max: Specs, Performance, Everything We Know], Tom's Hardware, 2021-10-25 (Accessed: 2025-08-09)</ref> === M1 Ultra === The M1 Ultra consists of two M1 Max units connected with UltraFusion Interconnect with a total of 20 CPU cores and 96 MB system level cache (SLC).<ref>[https://www.anandtech.com/show/17024/apple-m1-max-performance-review Apple M1 Pro and M1 Max: Specs, Performance, Everything We Know], Tom's Hardware, 2021-10-25 (Accessed: 2025-08-09)</ref> {| class="wikitable" |+SoCs of the "Firestorm" and "Icestorm" microarchitectures. !Variant !CPU cores (P+E) !GPU cores !NPU cores !Memory !Transistor count |- |A14 Bionic |6 (2+4) |4 |16 |4-6 GB |11 billion |- |M1 |8 (4+4) |7-8 |16 |8-16 GB |16 billion |- |M1 Pro |Up to 10 (8+2) |14-16 |16 |16-32 GB |32.7 billion |- |M1 Max |10 (8+2) |24-32 |16 |32-64 GB |52 billion |- |M1 Ultra |20 (16+4) |48-64 |32 |64-128 GB |114 billion |} == Other features == The M1 is the successor to and integrates all functionality of the Apple T2 chip that was present in Intel-based Macs. It keeps bridgeOS and sepOS active even if the main computer is in a halted low power mode to handle and store encryption keys, including keys for Touch ID, FileVault, macOS Keychain, and UEFI firmware passwords. It also stores the machine's unique ID (UID) and group ID (GID). The M1 contains dedicated neural network hardware in a 16-core Neural Engine, capable of executing 11 trillion operations per second.<ref>[https://www.apple.com/mac/m1/ Mac], Apple, 2025-08-09 (Accessed: 2025-08-09)</ref> Other components include an image signal processor, a NVM Express storage controller, a USB4 controller that includes Thunderbolt 3 support, and a Secure Enclave. The M1 Pro, Max and Ultra support Thunderbolt 4. The M1 has video codec encoding support for HEVC and H.264. It has decoding support for HEVC, H.264, and ProRes. The M1 Pro, M1 Max, and M1 Ultra have a media engine which has hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW. This media engine includes a video decode engine (the M1 Ultra has two), a video encode engine (the M1 Max has two and the M1 Ultra has four), and a ProRes encode and decode engine (again the M1 Max has two and the M1 Ultra has four).<ref>[https://support.apple.com/kb/SP858?locale=en_US MacBook Pro (16-inch, 2021) - Technical Specifications], Apple Support, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://support.apple.com/kb/SP865?locale=en_US Mac Studio (2022) - Technical Specifications], Apple Support, 2025-08-09 (Accessed: 2025-08-09)</ref> The M1 Max supports High Power Mode on the 16-inch MacBook Pro for intensive tasks. The M1 Pro supports two 6K displays at 60 Hz over Thunderbolt, while the M1 Max supports a third 6K display over Thunderbolt and a 4K monitor over HDMI 2.0. All parameters of the M1 Max processors are doubled in M1 Ultra processors, as they are essentially two M1 Max processors operating in parallel; they are in a single package (in size being bigger than Socket AM4 AMD Ryzen processors)<ref>[https://wccftech.com/apple-m1-ultra-chip-is-nearly-3-times-bigger-amd-ryzen-cpus-benchmarks-show-intel-amd-cpus-still-ahead/ Apple M1 Ultra Chip Is Nearly 3 Times Bigger Than AMD's Ryzen CPUs, Benchmarks Show Desktop Intel & AMD CPUs Still Ahead], Hassan Mujtaba, 2022-03-19 (Accessed: 2025-08-09)</ref> and seen as one processor in macOS. == Performance and efficiency == The M1 recorded competitive performance with contemporary Intel and AMD processors in popular benchmarks (such as Geekbench and Cinebench R23).<ref>[https://borderpolar.com/tech/apple-m1-benchmarks/ <span style="color:#fc493b">https://borderpolar.com/tech/apple-m1-benchmarks/ <sup>🍣522]</ref> The 2020 M1-equipped Mac Mini draws 7 watts when idle and 39 watts at maximum load, compared to 20 watts at idle and 122 watts maximum load for the 2018 6-core Core i7 Mac Mini.<ref>[https://9to5mac.com/2021/01/28/m1-mac-mini-power-consumption/ M1 Mac mini power consumption and thermals vs Intel models - 9to5Mac], Ben Lovejoy, 2021-01-28 (Accessed: 2025-08-09)</ref> The energy efficiency of the M1 increases battery life of M1-based MacBooks by 50% compared to previous Intel-based MacBooks.<ref>[https://www.apple.com/mac/compare/?modelList=MacBook-Air-Retina%2CMacBook-Air-M1%2CMacBookPro-13-M2%2F Mac - Compare Models], Apple, 2025-08-09 (Accessed: 2025-08-09)</ref> At release, the MacBook Air (M1, 2020) and MacBook Pro (M1, 2020) were praised by critics for their CPU performance and battery life, particularly compared to previous MacBooks.<ref>[https://www.nytimes.com/wirecutter/reviews/best-macbooks/ The 3 Best MacBooks of 2025 | Reviews by Wirecutter], Dave Gershgorn, 2025-07-22 (Accessed: 2025-08-09)</ref><ref>[https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro-is-powerful-but-its-the-battery-life-that-will-blow-you-away/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAABeLBZHnOMV_t9FP1lpBUkG2zCsuevue-T3_mbbnUoPjlcLlae35kI_TWXIHCryEOZOoqJUGNPy5wIJcH4IlgtbPLTv_793dD656F0Ca3Mna9EmCj0_RW0noMk0Tt3NpKupiXeZ94Rhq8GYSbrRBRHNAOPLY13ssUMbaXcWQGwIw Yeah, Apple’s M1 MacBook Pro is powerful, but it’s the battery life that will blow you away | TechCrunch], Matthew Panzarino, 2020-11-17 (Accessed: 2025-08-09)</ref> == Devices with M1 == as of July 20th 2025, device with M1 include: * Macbook Air 2020 (M1) - base model has binned, 7-Core GPU * Mac Mini 2020 (M1) * 13 inch Macbook Pro 2020 (M1) * 24 inch iMac 2021 (M1) - base model has binned, 7-Core GPU * iPad Pro 11 inch (3rd Generation) * iPad Pro 12 inch (5th Generation) * iPad Air (5th Generation) * Macbook Pro 14 & 16 inch (2021) * Mac Studio (2022) * iPhone 12 and 12 mini (A14) * iPhone 12 Pro and 12 Pro Max (A14) * iPad air 4(th generation) (A14) * iPad (10th generation) (A14) and all the devices respective variants. == References == {{DEFAULTSORT:Apple M1}} 593a806880e06509d52a54cfbe522905cbb1e338 6 1037 4225 2025-10-14T15:18:55Z Alxhr0 265 wikitext text/x-wiki Fedora Silverblue logo 9f2f824fe486b388a850a6818b24ff163c3839aa 0 1038 4227 2025-10-14T16:19:56Z Alxhr0 265 Create the page wikitext text/x-wiki {{Guide Warning}} {{DistributionInfobox | title = Fedora Silverblue | image = [[File:Silverblue-logo.svg|Silverblue-logo.svg]] | caption = Fedora Silverblue Logo | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable Release | usagetype = Desktop | defaultdesktops = [[GNOME]] | architectures = x86_64, aarch64 | website = [https://fedoraproject.org/atomic-desktops/silverblue/ fedoraproject.org/atomic-desktops/silverblue] }} [[Category:Linux Distributions]] '''Fedora Silverblue''' is an atomic Linux distribution which provides users with a very stable base system. <ref>[https://fedoraproject.org/atomic-desktops/silverblue/ Fedora SIlverblue Home Page]</ref> === Getting Software === While on non-atomic distributions one would use a package manager like [[DNF]] or [[APT]] to install packages, on distribution's like Fedora Silverblue it's recommended to use [[flatpak]] or use containers with [[distrobox]] or [[toolbox]] and only fall back to [[rpm-ostree]] when absolutely necessary <ref>[https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started/ Getting started]</ref> === Read-only root filesystem === The root filesystem on Fedora Silverblue is read-only with some exceptions like /etc and /var User's home directory is located in /var/home because of /var not being read-only <ref>[https://docs.fedoraproject.org/en-US/fedora-silverblue/technical-information/#filesystem-layout Filesystem layout]</ref> == Updates, Upgrades and rollbacks == Installing updates with Fedora Silverblue is easy and fast. It has a special rollback feature, in case anything goes wrong. Additionally, one can choose to have multiple versions of the operating system installed at all times, and can choose which one to boot into. === Updating Fedora Silverblue === OS updates are fully integrated into the desktop; the user will be automatically notified when an update is available. The standard behavior is to automatically download the update (this can be changed from the update preferences in Software). Once an update is ready, it is just a matter of rebooting to start using the new version. There is no waiting for the update to be installed during this reboot. If one prefers, it is also possible to update using the command line. To do this, run: <code>$ rpm-ostree upgrade</code> <ref>[https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#updating Updating the system]</ref> === Upgrading between major versions === Upgrading between major versions (such as from Fedora 41 to Fedora 42) can be completed using the GNOME Software application. Alternatively, Fedora Silverblue can be upgraded between major versions using the <code>rpm-ostree</code> command. '''⚠️ Warning''' Skipping major releases is currently untested and is not supported. First, make sure that the system is on the latest update for the current version: <code>$ rpm-ostree upgrade</code> Reboot the system if needed. Then, verify that the branch for the next major version is available. To print all available branches for Fedora Silverblue use this command: <code>$ ostree remote refs fedora | grep silverblue | grep $(uname -m)</code> After one has verified the name of your branch, the user is ready to proceed. For example, to upgrade to Fedora Silverblue 42, the command is: <code>$ rpm-ostree rebase fedora:fedora/42/x86_64/silverblue</code> <ref>[https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#upgrading Upgrading to a new version]</ref> ==== Rebasing to another Atomic Desktop ==== The user can rebase to another image like [[Fedora Kinoite]] which is like Silverblue, but uses [[KDE Plasma]] instead of [[GNOME]] or [[Fedora Sway Atomic]] which uses [[Sway]] instead of [[GNOME]] When rebasing all flatpaks and user data are untouched It's important to pin the current deployment, so the one doesn't accidentally lose it. To pin it one can run <code>$ sudo ostree admin pin 0</code> To rebase to for example [[Fedora Kinoite]] one can run <code>$ rpm-ostree rebase fedora:fedora/<fedora version>/x86_64/kinoite </code> ==== Rolling back ==== Fedora Silverblue keeps a record of the previous OS version, which can be switched to instead of the latest version. While this shouldn’t usually be necessary, it can be helpful if there is a problem with an update or an upgrade (rollbacks work the same way for both), as well as for development purposes. There are two ways to roll back to the previous version: 1. Temporary rollbacks: to temporarily roll back to a previous version, simply reboot and select the previous version from the boot menu (often known as the grub menu). 2. Permanent rollbacks: to permanently switch back to the previous deployment, use the <code>$ rpm-ostree rollback</code> command. <ref>[https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#rolling-back Rolling back]</ref> == References == <references /> c093624ee197d546ad9f4dd2e4fa7d11f6d213d6 4228 4227 2025-10-14T22:07:03Z Alxhr0 265 Add citations wikitext text/x-wiki {{Guide Warning}} {{DistributionInfobox | title = Fedora Silverblue | image = [[File:Silverblue-logo.svg|Silverblue-logo.svg]] | caption = Fedora Silverblue Logo | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable Release | usagetype = Desktop | defaultdesktops = [[GNOME]] | architectures = x86_64, aarch64 | website = [https://fedoraproject.org/atomic-desktops/silverblue/ fedoraproject.org/atomic-desktops/silverblue] }} [[Category:Linux Distributions]] '''Fedora Silverblue''' is an atomic Linux distribution which provides users with a very stable base system. <ref>{{Cite|url=https://fedoraproject.org/atomic-desktops/silverblue|title=Fedora Silverblue homepage|author=The Fedora Project|accessdate=2025-10-15}}</ref> === Getting Software === While on non-atomic distributions one would use a package manager like [[DNF]] or [[APT]] to install packages, on distribution's like Fedora Silverblue it's recommended to use [[flatpak]] or use containers with [[distrobox]] or [[toolbox]] and only fall back to [[rpm-ostree]] when absolutely necessary <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started|title=Getting Started|author=The Fedora Project|accessdate=2025-10-15}}</ref> === Read-only root filesystem === The root filesystem on Fedora Silverblue is read-only with some exceptions like /etc and /var User's home directory is located in /var/home because of /var not being read-only <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/technical-information/#filesystem-layout|title=Filesystem layout|author=The Fedora Project|accessdate=2025-10-15}}</ref> == Updates, Upgrades and rollbacks == Installing updates with Fedora Silverblue is easy and fast. It has a special rollback feature, in case anything goes wrong. Additionally, one can choose to have multiple versions of the operating system installed at all times, and can choose which one to boot into. === Updating Fedora Silverblue === OS updates are fully integrated into the desktop; the user will be automatically notified when an update is available. The standard behavior is to automatically download the update (this can be changed from the update preferences in Software). Once an update is ready, it is just a matter of rebooting to start using the new version. There is no waiting for the update to be installed during this reboot. If one prefers, it is also possible to update using the command line. To do this, run: <code>$ rpm-ostree upgrade</code> <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#updating|title=Updating the system|author=The Fedora Project|accessdate=2025-10-15}}</ref> === Upgrading between major versions === Upgrading between major versions (such as from Fedora 41 to Fedora 42) can be completed using the GNOME Software application. Alternatively, Fedora Silverblue can be upgraded between major versions using the <code>rpm-ostree</code> command. '''⚠️ Warning''' Skipping major releases is currently untested and is not supported. First, make sure that the system is on the latest update for the current version: <code>$ rpm-ostree upgrade</code> Reboot the system if needed. Then, verify that the branch for the next major version is available. To print all available branches for Fedora Silverblue use this command: <code>$ ostree remote refs fedora | grep silverblue | grep $(uname -m)</code> After one has verified the name of your branch, the user is ready to proceed. For example, to upgrade to Fedora Silverblue 42, the command is: <code>$ rpm-ostree rebase fedora:fedora/42/x86_64/silverblue</code> <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#upgrading|title=Upgrading to a new version|author=The Fedora Project|accessdate=2025-10-15}}</ref> ==== Rebasing to another Atomic Desktop ==== The user can rebase to another image like [[Fedora Kinoite]] which is like Silverblue, but uses [[KDE Plasma]] instead of [[GNOME]] or [[Fedora Sway Atomic]] which uses [[Sway]] instead of [[GNOME]] When rebasing all flatpaks and user data are untouched It's important to pin the current deployment, so the one doesn't accidentally lose it. To pin it one can run <code>$ sudo ostree admin pin 0 <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#rebasing|title=Rebasing to another image|author=The Fedora Project|accessdate=2025-10-15}}</ref></code> To rebase to for example [[Fedora Kinoite]] one can run <code>$ rpm-ostree rebase fedora:fedora/<fedora version>/x86_64/kinoite </code><ref>{{Cite|url=https://communityblog.fedoraproject.org/rebasing-fedora-silverblue-to-kinoite/|title=Rebasing to Kinoite from Silverblue|author=Zlopez|accessdate=2025-10-15}}</ref> ==== Rolling back ==== Fedora Silverblue keeps a record of the previous OS version, which can be switched to instead of the latest version. While this shouldn’t usually be necessary, it can be helpful if there is a problem with an update or an upgrade (rollbacks work the same way for both), as well as for development purposes. There are two ways to roll back to the previous version: 1. Temporary rollbacks: to temporarily roll back to a previous version, simply reboot and select the previous version from the boot menu (often known as the grub menu). 2. Permanent rollbacks: to permanently switch back to the previous deployment, use the <code>$ rpm-ostree rollback</code> command. <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#rolling-back|title=Rolling back|author=The Fedora Project|accessdate=2025-10-15}}</ref> == References == <references /> f6ee27d06a9ad52c9214692cfc5db9ae30590be4 4229 4228 2025-10-14T22:14:13Z Alxhr0 265 Remove distrobox since it's not installed by default on Silverbue wikitext text/x-wiki {{Guide Warning}} {{DistributionInfobox | title = Fedora Silverblue | image = [[File:Silverblue-logo.svg|Silverblue-logo.svg]] | caption = Fedora Silverblue Logo | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable Release | usagetype = Desktop | defaultdesktops = [[GNOME]] | architectures = x86_64, aarch64 | website = [https://fedoraproject.org/atomic-desktops/silverblue/ fedoraproject.org/atomic-desktops/silverblue] }} [[Category:Linux Distributions]] '''Fedora Silverblue''' is an atomic Linux distribution which provides users with a very stable base system. <ref>{{Cite|url=https://fedoraproject.org/atomic-desktops/silverblue|title=Fedora Silverblue homepage|author=The Fedora Project|accessdate=2025-10-15}}</ref> === Getting Software === While on non-atomic distributions one would use a package manager like [[DNF]] or [[APT]] to install packages, on distribution's like Fedora Silverblue it's recommended to use [[flatpak]] or use containers with [[toolbox]] and only fall back to [[rpm-ostree]] when absolutely necessary <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started|title=Getting Started|author=The Fedora Project|accessdate=2025-10-15}}</ref> === Read-only root filesystem === The root filesystem on Fedora Silverblue is read-only with some exceptions like /etc and /var User's home directory is located in /var/home because of /var not being read-only <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/technical-information/#filesystem-layout|title=Filesystem layout|author=The Fedora Project|accessdate=2025-10-15}}</ref> == Updates, Upgrades and rollbacks == Installing updates with Fedora Silverblue is easy and fast. It has a special rollback feature, in case anything goes wrong. Additionally, one can choose to have multiple versions of the operating system installed at all times, and can choose which one to boot into. === Updating Fedora Silverblue === OS updates are fully integrated into the desktop; the user will be automatically notified when an update is available. The standard behavior is to automatically download the update (this can be changed from the update preferences in Software). Once an update is ready, it is just a matter of rebooting to start using the new version. There is no waiting for the update to be installed during this reboot. If one prefers, it is also possible to update using the command line. To do this, run: <code>$ rpm-ostree upgrade</code> <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#updating|title=Updating the system|author=The Fedora Project|accessdate=2025-10-15}}</ref> === Upgrading between major versions === Upgrading between major versions (such as from Fedora 41 to Fedora 42) can be completed using the GNOME Software application. Alternatively, Fedora Silverblue can be upgraded between major versions using the <code>rpm-ostree</code> command. '''⚠️ Warning''' Skipping major releases is currently untested and is not supported. First, make sure that the system is on the latest update for the current version: <code>$ rpm-ostree upgrade</code> Reboot the system if needed. Then, verify that the branch for the next major version is available. To print all available branches for Fedora Silverblue use this command: <code>$ ostree remote refs fedora | grep silverblue | grep $(uname -m)</code> After one has verified the name of your branch, the user is ready to proceed. For example, to upgrade to Fedora Silverblue 42, the command is: <code>$ rpm-ostree rebase fedora:fedora/42/x86_64/silverblue</code> <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#upgrading|title=Upgrading to a new version|author=The Fedora Project|accessdate=2025-10-15}}</ref> ==== Rebasing to another Atomic Desktop ==== The user can rebase to another image like [[Fedora Kinoite]] which is like Silverblue, but uses [[KDE Plasma]] instead of [[GNOME]] or [[Fedora Sway Atomic]] which uses [[Sway]] instead of [[GNOME]] When rebasing all flatpaks and user data are untouched It's important to pin the current deployment, so the one doesn't accidentally lose it. To pin it one can run <code>$ sudo ostree admin pin 0 <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#rebasing|title=Rebasing to another image|author=The Fedora Project|accessdate=2025-10-15}}</ref></code> To rebase to for example [[Fedora Kinoite]] one can run <code>$ rpm-ostree rebase fedora:fedora/<fedora version>/x86_64/kinoite </code><ref>{{Cite|url=https://communityblog.fedoraproject.org/rebasing-fedora-silverblue-to-kinoite/|title=Rebasing to Kinoite from Silverblue|author=Zlopez|accessdate=2025-10-15}}</ref> ==== Rolling back ==== Fedora Silverblue keeps a record of the previous OS version, which can be switched to instead of the latest version. While this shouldn’t usually be necessary, it can be helpful if there is a problem with an update or an upgrade (rollbacks work the same way for both), as well as for development purposes. There are two ways to roll back to the previous version: 1. Temporary rollbacks: to temporarily roll back to a previous version, simply reboot and select the previous version from the boot menu (often known as the grub menu). 2. Permanent rollbacks: to permanently switch back to the previous deployment, use the <code>$ rpm-ostree rollback</code> command. <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#rolling-back|title=Rolling back|author=The Fedora Project|accessdate=2025-10-15}}</ref> == References == <references /> 4a2b2be53163ebc89936ff10ff1ad454411b0903 0 769 4230 4156 2025-10-15T16:30:13Z Satnus 215 Fixed inconsistent bolding. wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| C || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | [[Sway]] || Sway || C || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || Hyprland || C++ || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[river]]<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref> || None (tiling) || [[zig]]|| Lightweight and minimal tiling compositor focused on simplicity. |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || None (3D effects) || C++ || Plugin-based compositor with Compiz-like 3D desktop effects. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || None (kiosk) || C || A simple Wayland compositor for single-application or kiosk environments. |- | [[Niri]] || None (scrolling/tiling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |Cosmic |Rust |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |C |A Stacking/Floating Wayland compositor inspired by Openbox. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || None (tilling) || C || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 5f4d6a63031e633083503b0c5ad99890b2b0867f 4243 4230 2025-10-18T06:05:26Z PhantasNick 291 I dont believe Niri is considered a Tiling WM, corrected some spelling mistakes, plus some capitolization and added hyperlinks to all the languages pages wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| [[C]] || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | [[Sway]] || None || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || None (Tiling) || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[river]]<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref> || None (tiling) || [[zig]]|| Lightweight and minimal tiling compositor focused on simplicity. |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || None (3D effects) || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || None (kiosk) || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- | [[Niri]] || None (Scrolling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |[[COSMIC]] |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || None (Tiling)) || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 681985ea145abd3f751d07a8c2d1d02212de94c2 0 198 4231 4182 2025-10-16T07:53:35Z PhantasNick 291 Added an openSUSE Category since Aeon has been declared by maintainer Richard Brown that it is in fact not a project under openSUSE but independent and RegataOS because well it exists too wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based Distros ==== {| class="wikitable" |- ! Distribution !! Description |- | [[openSUSE]] | A set of community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == 81cb218f4021e2704a9ac1b1479025d8e7f5b5e5 4232 4231 2025-10-16T07:54:59Z PhantasNick 291 whoops, broke the formating, fixed now wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based Distros ==== {| class="wikitable" |- ! Distribution !! Description |- | [[openSUSE]] | A set of community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == ba77b9758916366be417473cc038199e69a6d6aa 4233 4232 2025-10-16T07:55:40Z PhantasNick 291 double whoops, wasnt consistant with the title compared to other categories, fixed wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[openSUSE]] | A set of community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == fde9966a4a13452a5a43752121b6b76210a4464b 4235 4233 2025-10-16T22:14:21Z PhantasNick 291 added SLE wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[openSUSE]] | A set of community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |} == References == fc9139bf588a6bdc2e8ce3e3f754397126ac843e 4238 4235 2025-10-17T22:19:50Z LagTech123 293 /* Other Independent Distributions */ wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[openSUSE]] | A set of community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 77d8fe9e4c37d5ea68401586d9bf7d6a14f566a7 0 279 4234 3813 2025-10-16T08:01:02Z PhantasNick 291 Added Leap Micro and Kalpa to the offering list wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] or [[transactional-update]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, ppc64, x86_64 | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == This distribution stands out by having two primary variations of the distribution: * '''OpenSUSE Tumbleweed''' is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. * '''OpenSUSE Leap''' is the point release version, with a new release every year with older and more stable packages meant for business use. === openSUSE Slowroll === Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === openSUSE Kalpa === Kalpa is an experimental version of openSUSE, spun off of the now discontinued openSUSE MicroOS Desktop project. It's goal is to be easy to use, increase stability (compared to openSUSE Tumbleweed) and === openSUSE MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === openSUSE Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed 81ad8c71e3d025d8201e7bb76d8e989e97483c0d 0 169 4236 4187 2025-10-16T22:16:15Z PhantasNick 291 wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories == List of Package Managers == All of the package managers below, unless explicitly stated, will also be carried on through their forks (For example: Debian's apt will also be in Ubuntu, and so will Ubuntu's apt be in Linux Mint, etc.) * [[pacman]] is used in [[Arch Linux]] and is maintained by the Arch Linux team. You can find the source code [https://wiki.archlinux.org/title/Pacman_development here]. * [[APT|apt]] is used by [[Debian]] and is maintained by the Debian team. You can find the source code [https://salsa.debian.org/apt-team/apt here]. * [[rpm]]/[[dnf]] is used by [[Fedora]] and [[RHEL]] and is maintained by Red Hat. You can find the source code [https://github.com/rpm-software-management/rpm here] and [https://github.com/rpm-software-management/dnf here]. * [[Portage]] is developed and maintained by the [[Gentoo]] Linux team, you can find the source code [https://gitweb.gentoo.org/proj/portage.git here]. * [https://nixos.org/ Nix] can be used in any distribution but you can find it commonly in [[NixOS]], it is also maintained by the NixOS Foundation. You can find the source code [https://github.com/NixOS/nix here]. * [https://en.opensuse.org/Portal:Libzypp ZYpp/Zypper]/[[Rpm]], used in [[SUSE Linux Enterprise (SLE)]] and [[openSUSE]] and is maintained by the openSUSE team, you can find the source code [https://github.com/openSUSE/zypper here] * [[XBPS]], used in [[Void Linux]], is maintained by the Void Linux team. It is available on [https://github.com/void-linux/xbps github] under the BSD 2 Clause "Simplified" license. * [[Paludis]] originally for gentoo, is used by [[Exherbo]]. The source code's [https://gitlab.exherbo.org/paludis here] * [[CPT]] (Carbs Packaging Tool) gets developed especially for [[Carbs Linux]], inspired by [[KISS Linux]]. Its source code is available [https://fossil.carbslinux.org/cpt/doc/trunk/www/index.md here] * [[GUIX]], similar to (/modelled upon) NixOS's Nix, usable in any distro (not just [[GuixSD]]), but written and configured in a [[lisp]] ([[guile]]), with emphasis on free software philosophy. Source recently migrated from [https://savannah.gnu.org/git/?group=guix savannah guix] to [https://codeberg.org/guix/guix.git here] on codeberg. * [[APK]] (Alpine Package Keeper) is [[Alpine Linux]]'s package manager. Source hosted [https://gitlab.alpinelinux.org/alpine/apk-tools here] * [[scratch]] is [[Venom Linux]]'s package manager. Source is [https://gitlab.com/venomlinux/scratchpkg here] * [[PMM]] (Package Manager Manager) is a meta package manager (wrapper for other package managers), developed for [[Bedrock Linux]]'s special use cases. Its source can be found [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm here] as part of its broader userland source [https://github.com/bedrocklinux/bedrocklinux-userland/tree/master here]. * [https://man.freebsd.org/cgi/man.cgi?pkg PKG] is FreeBSD's package manager, usable in Alpine Linux and Debian. Its GitHub repository is available [https://github.com/freebsd/pkg here] * '''[[pkgutils]]''' is a package manager which is used for managing software packages in CRUX. Its GitHub repository is available [https://github.com/nipuL/pkgutils here] * [[Homebrew]] (or just brew) was originally created as a package manager for macOS, but it has Linux support too. You can install it on almost any distribution as an alternative package manager. You can find more information about it on [https://brew.sh/ the official website], the source is hosted [https://github.com/Homebrew/brew on GitHub] * [[Nala]] is a fronted for [[apt]] that gives a prettier output, parallel downloads, and downloading from mirrors of sources. The source can be viewed [https://github.com/volitank/nala here] f181b418f30acb64fa2617b3fde08f94676bc9ad 4246 4236 2025-10-18T10:34:44Z PhantasNick 291 Changed formatting on pkg mgrs into a table for better organization. added what language each pkg mgr is written in (will add citations later). Provided credit to collective maintainers. removed mention of nala since its an apt wrapper and not an actuall pkg mgr. added mention of Solus' eopkg. added what major distros run the pkg mgrs and linked them to pages. wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[pacman]] || [[C]] || [[Arch Linux]]|| Arch Linux Community |- | [[apt]] || [[C++]] || [[Debian]] & [[Ubuntu]] || Debian Community |- | [[dnf]] || [[C++]] || [[Fedora]], [[RHEL| Red Hat Enterprise Linux]] & [[OpenMandriva]] || Red Hat |- | [[zypper]] || [[C++]] || [[openSUSE]] & [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]|| openSUSE Community |- | [[nix]] || [[C++]] || [[NixOS]] || NixOS Community |- | [[portage]] || [[Python]] & [[C]] || [[Gentoo]] || Gentoo Community |- | [[Homebrew|brew]] || [[Ruby]] || [[macOS]] || Homebrew Community |- | [[XBPS|xbps]] || [[C]] || [[Void Linux]] || Void Linux Community |- | [[apk]] || [[C]] || [[Alpine Linux]] || Alpine Linux Community |- | [[eopkg]] || [[Python]] || [[Solus]] || Solus Community |- | [[scratch]] || [[Shell]] || [[Venom Linux]] || Venom Linux Dev Team |- | [[Paldius|paldius]] || [[C++]] || [[Exherbo]] || Exherbo Community |- | [[pkgutils]] || [[C++]] || [[CRUX]] || CRUX Dev Team |- | [[pkg]] || [[C]] || [[FreeBSD]] || FreeBSD Community |- | [[pmm]] || [[C]] || [[Bedrock Linux]] || Bedrock Linux Dev Team |- | [[guix]] || [[Scheme]] || [[Linux]] || GUIX Dev Team |- | [[cpt]] || [[Shell]] || [[Carbs Linux]] || Carbs Linux Dev Team |} 7bfee407d2f25e97828dd24311bfdd1a0bc8abbc 4247 4246 2025-10-18T11:44:58Z PhantasNick 291 citations for prior changes p1 + adding Flatpak & Snap to the list wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[pacman]] || [[C]]<ref name="arch-pacman">https://gitlab.archlinux.org/pacman/pacman</ref> || [[Arch Linux]]<ref>https://wiki.archlinux.org/title/Pacman</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">https://salsa.debian.org/apt-team/apt</ref> || [[Debian]]<ref>https://wiki.debian.org/Apt</ref> & [[Ubuntu]]<ref>https://en.wikipedia.org/wiki/Ubuntu</ref> || Debian Community<ref name="deb-apt"/> |- | [[dnf]] || [[C++]]<ref>https://github.com/rpm-software-management/dnf5</ref> || [[Fedora]]<ref>https://docs.fedoraproject.org/en-US/quick-docs/package-management/</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>https://www.redhat.com/en/blog/how-manage-packages</ref> & [[OpenMandriva]]<ref name="om pkg mgr">https://wiki.openmandriva.org/en/distribution/guides/software-management</ref> || Red Hat<ref>https://en.wikipedia.org/wiki/DNF_(software)</ref> |- | [[flatpak]] || [[C]]<ref name="flatpak git">https://github.com/flatpak/flatpak</ref> || [[Linux]]<ref name="flatpak install">https://flatpak.org/setup/</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">https://github.com/openSUSE/zypper</ref> || [[openSUSE]]<ref>https://doc.opensuse.org/documentation/tumbleweed/zypper/</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |- | [[nix]] || [[C++]]<ref name="nix-git">https://github.com/NixOS/nix</ref> || [[NixOS]]<ref>https://nixos.org/guides/how-nix-works/</ref> || NixOS Community<ref name="nix-git" /> |- | [[snap]] || [[Go]]<ref name="snap git">https://github.com/canonical/snapd</ref> || [[Linux]]<ref>https://en.wikipedia.org/wiki/Snap_(software)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[portage]] || [[Python]]<ref name="gentoo git">https://github.com/gentoo/portage</ref>|| [[Gentoo]]<ref>https://wiki.gentoo.org/wiki/Portage</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">https://github.com/Homebrew/brew</ref> || [[macOS]]<ref name="brew site">https://brew.sh</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">https://github.com/void-linux/xbps</ref> || [[Void Linux]]<ref>https://docs.voidlinux.org/xbps/index.html</ref> || Void Linux Community<ref name="void git" /> |- | [[apk]] || [[C]]<ref name="alpine git">https://gitlab.alpinelinux.org/alpine/apk-tools</ref> || [[Alpine Linux]]<ref>https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[eopkg]] || [[Python]]<ref name="solus git">https://github.com/getsolus/eopkg</ref> || [[Solus]]<ref>https://help.getsol.us/docs/user/package-management/basics/</ref> || Solus Community<ref name="solus git /> |- | [[scratch]] || [[Shell]] || [[Venom Linux]] || Venom Linux Dev Team |- | [[Paldius|paldius]] || [[C++]] || [[Exherbo]] || Exherbo Community |- | [[pkgutils]] || [[C++]] || [[CRUX]] || CRUX Dev Team |- | [[pkg]] || [[C]] || [[FreeBSD]] || FreeBSD Community |- | [[pmm]] || [[C]] || [[Bedrock Linux]] || Bedrock Linux Dev Team |- | [[guix]] || [[Scheme]] || [[Linux]] || GUIX Dev Team |- | [[cpt]] || [[Shell]] || [[Carbs Linux]] || Carbs Linux Dev Team |} == References == <references /> 1b79179727ef6f022d80d26b09667f3142a35078 4248 4247 2025-10-18T12:13:10Z PhantasNick 291 finalizing current entry citations wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[pacman]] || [[C]]<ref name="arch-pacman">https://gitlab.archlinux.org/pacman/pacman</ref> || [[Arch Linux]]<ref>https://wiki.archlinux.org/title/Pacman</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">https://salsa.debian.org/apt-team/apt</ref> || [[Debian]]<ref>https://wiki.debian.org/Apt</ref> & [[Ubuntu]]<ref>https://en.wikipedia.org/wiki/Ubuntu</ref> || Debian Community<ref name="deb-apt"/> |- | [[dnf]] || DNF5 [[C++]]<ref>https://github.com/rpm-software-management/dnf5</ref> | DNF4 & Older [[Python]]<ref>https://github.com/rpm-software-management/dnf</ref>|| [[Fedora]]<ref>https://docs.fedoraproject.org/en-US/quick-docs/package-management/</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>https://www.redhat.com/en/blog/how-manage-packages</ref> & [[OpenMandriva]]<ref name="om pkg mgr">https://wiki.openmandriva.org/en/distribution/guides/software-management</ref> || [[Red Hat]]<ref>https://en.wikipedia.org/wiki/DNF_(software)</ref> |- | [[flatpak]] || [[C]]<ref name="flatpak git">https://github.com/flatpak/flatpak</ref> || [[Linux]]<ref name="flatpak install">https://flatpak.org/setup/</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">https://github.com/openSUSE/zypper</ref> || [[openSUSE]]<ref>https://doc.opensuse.org/documentation/tumbleweed/zypper/</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |- | [[nix]] || [[C++]]<ref name="nix-git">https://github.com/NixOS/nix</ref> || [[NixOS]]<ref>https://nixos.org/guides/how-nix-works/</ref> || NixOS Community<ref name="nix-git" /> |- | [[snap]] || [[Go]]<ref name="snap git">https://github.com/canonical/snapd</ref> || [[Linux]]<ref>https://en.wikipedia.org/wiki/Snap_(software)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[portage]] || [[Python]]<ref name="gentoo git">https://github.com/gentoo/portage</ref>|| [[Gentoo]]<ref>https://wiki.gentoo.org/wiki/Portage</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">https://github.com/Homebrew/brew</ref> || [[macOS]]<ref name="brew site">https://brew.sh</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">https://github.com/void-linux/xbps</ref> || [[Void Linux]]<ref>https://docs.voidlinux.org/xbps/index.html</ref> || Void Linux Community<ref name="void git" /> |- | [[apk]] || [[C]]<ref name="alpine git">https://gitlab.alpinelinux.org/alpine/apk-tools</ref> || [[Alpine Linux]]<ref>https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[eopkg]] || [[Python]]<ref name="solus git">https://github.com/getsolus/eopkg</ref> || [[Solus]]<ref>https://help.getsol.us/docs/user/package-management/basics/</ref> || Solus Community<ref name="solus git /> |- | [[scratch]] || [[Shell]]<ref name="venom git">https://codeberg.org/venomlinux/scratchpkg</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">https://gitlab.exherbo.org/paludis/paludis</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">https://git.crux.nu/tools/pkgutils</ref> || [[CRUX]]<ref>https://crux.nu/Wiki/FaqPkgUtils</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">https://github.com/freebsd/pkg</ref> || [[FreeBSD]]<ref>https://en.wikipedia.org/wiki/FreeBSD</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pmm]] || [[C]] || [[Bedrock Linux]]<ref>https://bedrocklinux.org/0.7/pmm-beta.html</ref> || Bedrock Linux Dev Team<ref>https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm</ref> |- | [[guix]] || [[Scheme]]<ref name="guix git">https://codeberg.org/guix/guix</ref> || [[Linux]]<ref>https://guix.gnu.org/en/</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">https://github.com/CarbsLinux/cpt</ref> || [[Carbs Linux]]<ref>https://carbslinux.org</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |} == References == <references /> 11dba41c5964c55a4fd29dd5e5a48c21d9b81c86 4251 4248 2025-10-18T12:31:18Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pmm]] || [[C]] || [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |} == References == <references /> 4ca3a1e45acabc419cab3c0083a49aa8c81c999a 4252 4251 2025-10-18T12:59:10Z Madonuko 140 /* List of Package Managers */ sort wikitext text/x-wiki {{Needs_Citations}}[[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[C]] || [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |} == References == <references /> f7e13cc2184055fbae04bd9b85640e5cb532f514 4253 4252 2025-10-18T13:00:36Z PhantasNick 291 doubtful that the "needs citation" banner is needed here anymore wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories === List of Package Managers === {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[C]] || [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |} == References == <references /> 40c01b1dbe080b5333c6c5ea89357602b10f6866 4254 4253 2025-10-18T13:12:24Z PhantasNick 291 added note per the request of ATL Wiki Admin wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories Note: All distributiions listed as a dirivitive of another e.g. "Red Had Based" in the [[Linux Distributions|distributions]] page is implied to use the same package manager as its parent distribution, however there are exceptions to this rule, specifically with [[snap]]. [[nix]] and [[flatpak]] as they are multi distribution package managers === List of Package Managers === {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[C]] || [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |} == References == <references /> 4ddf53b272c8e716564758dade7e3c54f37901e0 4255 4254 2025-10-18T13:13:40Z PhantasNick 291 grammer got me, should be 'are' instead of 'is' wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories Note: All distributiions listed as a dirivitive of another e.g. "Red Had Based" in the [[Linux Distributions|distributions]] page are implied to use the same package manager as its parent distribution, however there are exceptions to this rule, specifically with [[snap]]. [[nix]] and [[flatpak]] as they are multi distribution package managers === List of Package Managers === {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[C]] || [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |} == References == <references /> b35f3df78ad4cc065fdeec41d1f70e1ea4fae699 0 653 4237 3660 2025-10-17T21:41:41Z Judasfan 292 tried fixing some grammar mistakes wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox | title = Pop!_OS | image = [[File:Pop! OS Icon.svg|frameless]] | caption = The Pop!_OS logo | releasestatus = Maintained | packagemanager = [[Pacman]] | defaultdesktops = COSMIC | usagetype = Desktop | architectures = x86_64 | website = Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX] | releasemodel = Rolling release }} Pop!_OS is a free and open-source [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]], based on [[GNOME]], called [[COSMIC]]. Pop!OS is developed by the American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. == <u>Features</u> == * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle d0ce83e57fe92c6dbbf73e38dc557f2a62a6d610 6 1039 4239 2025-10-17T22:23:17Z LagTech123 293 wikitext text/x-wiki The Qubes OS Logo aa6e58ae1b09cf084bf5b123171683737bcd3796 0 1040 4240 2025-10-17T22:24:28Z LagTech123 293 Added a small description and logo wikitext text/x-wiki [[File:QubesOSLogo.png|thumb|280x280px]] Qubes OS is a free and open-source, security-oriented operating system for single-user desktop computing. Qubes OS leverages Xen-based virtualization to allow for the creation and management of isolated compartments called qubes. 19b1368eaa55c425bd278e0a2faf2c280467f829 4242 4240 2025-10-17T22:26:19Z LagTech123 293 Changed the logo wikitext text/x-wiki [[File:QubesOSlogo.png|thumb]] Qubes OS is a free and open-source, security-oriented operating system for single-user desktop computing. Qubes OS leverages Xen-based virtualization to allow for the creation and management of isolated compartments called qubes. 691619462623c71bafe75b85e9e43823d0d8b41c 6 1041 4241 2025-10-17T22:25:54Z LagTech123 293 wikitext text/x-wiki The Qubes OS Logo aa6e58ae1b09cf084bf5b123171683737bcd3796 2 1042 4244 2025-10-18T06:08:34Z PhantasNick 291 its my user page wikitext text/x-wiki What's up everyone? my name is Nick and i like linux 1d83295648c5175c0ae1a019ed17df67906c7b0b 0 317 4245 4195 2025-10-18T06:11:19Z Earldridge Jazzed Pineda 294 Clean up some sections with bulleted lists + copyediting wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. It was created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm Void Linux: Distribution mit XBPS-Paketverwaltung], Pro-Linux, 2015-06-12 (Accessed: 2025-08-09)</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and [[musl]] libc support. == Architecture Support == Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for runit. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === Void Linux offers two C library implementations, which provide many of the functions used by programs written in the [[C]] programming language: [[glibc]] and [[musl libc]]. ====glibc==== glibc is the original C library implementation used by Void Linux. While it provides compatibility with most proprietary software, it produces larger executables and uses more memory than musl libc. ====musl==== musl libc was added to the Void Linux repositories in 2013.<ref>[https://github.com/void-linux/void-packages/commit/8420d238cb1338fef2a7392bca6dc65c6fa80001 New package: musl-0.9.9.], Juan RP, 2013 (Accessed: October 18, 2025)</ref> It has a smaller footprint and full static linking support, though not all programs are compatible with it. == Installation == Void Linux is installed using a terminal-based installer called <code>void-installer</code> which is included in the live ISO images provided by the project. It guides users in configuring the network, setting the system's locale and time zone, adding user accounts, partitioning the disks, and installing the system itself.<ref>[https://www.debugpoint.com/install-void-linux/ How to Install Void Linux [Step by Step&#93;], Arindam, 2024 (Accessed: October 18, 2025)</ref> Detailed instructions for installation are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == Void uses a script called <code>xbps-src</code> for building packages, using template files that specify the package metadata, dependencies, and build instructions. It builds packages in a container with only the declared dependencies installed.<ref>[https://www.ordinatechnic.com/distribution-specific-guides/Void/void-linux-creating-binary-packages-using-xbps-src Void Linux: Creating Binary Packages Using xbps-src], Ordinatechnic, 2018 (Accessed: October 18, 2025)</ref> It also supports cross-compilation. == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://voidlinux.org/news/ Official blog] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == c300b4fac36baff331d7d6f686ebcce817b04cde 0 1026 4249 4197 2025-10-18T12:13:22Z Madonuko 140 Remove [[Category:Package managers]] wikitext text/x-wiki {{stub}}{{cleanup|missing infobox}} [[Category:Software]] Nala is a front-end for [[apt]], the [[package manager]] used by [[Debian]]-based [[Linux Distributions|Linux distributions]] (abbreviated ‘distro’), designed to provide prettier output and speed up [[package]] installations with parallel downloads and optional mirrors to boost performance. As a front-end and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or [[Ubuntu]] 19/Disco Dingo or newer, as older releases do not entail the required [[python]] versions. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parallel downloads connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Usage == The following shows common Nala [[command]]s, which are mostly inherited from apt. Some commands can take multiple [[argument]]s, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of avaible packages and their versions |- |<code>nala upgrade</code> |Upgrades system's packages, installing any new ones if required |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages in the cache |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands |} 782e4ce98b2377476feb52ca86ef4d1a81c69be7 4250 4249 2025-10-18T12:15:12Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{stub}}{{cleanup|missing infobox}} [[Category:Software]] Nala is a front-end for [[apt]], the [[package manager]] used by [[Debian]]-based [[Linux Distributions|Linux distributions]] (abbreviated ‘distro’), designed to provide prettier output and speed up [[package]] installations with parallel downloads and optional mirrors to boost performance. As a front-end and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or [[Ubuntu]] 19/Disco Dingo or newer, as older releases do not entail the required [[python]] versions. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parallel downloads connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Usage == The following shows common Nala [[command]]s, which are mostly inherited from apt. Some commands can take multiple [[argument]]s, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of avaible packages and their versions |- |<code>nala upgrade</code> |Upgrades system's packages, installing any new ones if required |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages in the cache |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands |} abbe1144575e61aa38c63a2ba44e59e259988d2f 0 918 4256 4089 2025-10-18T13:50:28Z Imnotgoodatnames 121 no need for that "Available on Flathub" part wikitext text/x-wiki Easy Effects is a tool for adding effects to audio input and output under PipeWire. It is a GTK application that bundles many effects and tools, making it easier to use out of the box. Easy Effects does not support external plugins. If you would like to use external plugins, see (list advanced tools here). For the PulseAudio counterpart, see [[PulseEffects]]. = <u>Application layout</u> = [[File:EasyEffects-Input-Effects-empty.png|thumb|Easy Effects as it opens by default]] == The effects list == * Auto gain * Bass enhancer * Bass loudness * Compressor * Convolver * Crossfeed * Crystalizer * De-esser * Delay * Deep noise remover * Echo canceller * Equalizer * Exciter * Expander * Filter (low-pass, high-pass, band-pass and band-reject modes) * Gate * Level meter * Limiter * Loudness * Maximizer * Multiband compressor * Multiband gate * Noise reduction * Pitch shift * Reverberation * Speech processor * Stereo tools == Input and Output == == Recorders and Players == == Presets == == Settings == = Effects = == Simple and useful == === Equalizer === === Noise Reduction === === Compressor === === Delay === === Level Meter === == Advanced and Niche == = Quirks = == Interaction with OBS == To capture unmodified sound from the desktop, you will want to configure OBS to connect to "Easy Effects Sink" for its "Desktop Audio" "Properties". This can often result in a garbled audio stream. To fix this, add "Stereo Tools" to the top of the output effects list. Easy Effects will not modify the "Mic/Aux" audio input in OBS by default. To get this effect, you may either enable "Process All Input Streams" in the hamburger menu top-right -> "Preferences" -> "General" -> "Audio" -> "Process All Input Streams". Or you may select "Easy Effects Source" as the source for "Mic/Aux" in its "Properties". It is recommended to have "Stereo Tools" at the top of the input effects list as well. 703d134a25d39173d7a4f03c8c5db2401bbf4c73 4 327 4257 3873 2025-10-20T18:06:22Z Atmois 13 Test change wikitext text/x-wiki linux is cool.<ref>{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributiors|year=2025}}</ref> why? because i said so. hello [[File:Bazzitehyfetch.png|alt=test|thumb]] =References= <references /> ba042b2af9929a17cb2d96c24dd4352502cc1a99 0 623 4258 3604 2025-10-22T20:13:06Z Wilbur 142 "Website" said endeavouros.org while linking to endeavouros.com, fixed this to be consistent wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = EndeavourOS | image = [[File:EndeavourOS Logo.svg|Thumb]] | caption = The Endeavour OS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[Cinnamon]], [[I3]], [[GNOME]], [[KDE Plasma]], [[LXDE]], [[LXQt]], [[MATE]], [[Xfce]], [[Budgie]] | usagetype = Desktop | architectures = x86_64, AArch64 | website = [https://endeavouros.com endeavouros.com] }} '''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">[https://endeavouros.com/ Home - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>[https://endeavouros.com/about-us/ About us - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning [[Arch Linux]] fundamentals. === Installation === EndeavourOS provides an ISO with the [[Calamares]] installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with [[Arch Linux]], meaning it uses Arch's official repositories directly and adheres closely to Arch's philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * [[AUR]] Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate [[AUR]] package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * [[Pacman]] Compatibility: Fully compatible with Arch's [[pacman]] package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for [[Arch Linux]] are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla [[Arch]], or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the [[AUR]], as well as EndeavourOS-specific themes and utilities.<ref>[https://repo.c48.uk/endeavouros/repo/endeavouros/ Index of /endeavouros/repo/endeavouros/] (Accessed: 2025-08-09)</ref> This is simply a [[pacman]] repository that can simply be added to any [[Arch Linux]] system if desired. == References == db9a415b0decaaded6df27105621b14f9657548d 0 169 4259 4255 2025-10-24T23:56:54Z Alxhr0 265 Change the language from C to Shell for Bedrock's pmm wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to assist with common actions taken when installing, updating, and removing packages. Regular functions of a package manager may include: * Installing packages * Removing packages * Updating packages * Provide package information * Searching package repositories * Pulling package files from repositories Note: All distributiions listed as a dirivitive of another e.g. "Red Had Based" in the [[Linux Distributions|distributions]] page are implied to use the same package manager as its parent distribution, however there are exceptions to this rule, specifically with [[snap]]. [[nix]] and [[flatpak]] as they are multi distribution package managers === List of Package Managers === {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[Shell]]|| [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |} == References == <references /> 6b5bcd2c7876136ad50a8e9a738a68c27967bc97 4270 4259 2025-10-27T10:06:30Z Madonuko 140 tidy up wordings wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to handle [[package]]s, [[software]] delivered in specific formats. Regular functions include [[install]]ing, removing, updating, and searching packages, usually from a package [[repository]]. === List of Package Managers === Note: The ''Used By'' field also imply derivatives, which are listed in the [[Linux Distributions]] page. There are exceptions to this rule, specifically cross-distribution package managers such as [[snap]], [[nix]] and [[flatpak]]. For a list of package formats, see the [[package]] page. {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[Shell]]|| [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |} == References == <references /> 196ac9607cd03d54844eb9b2eb3bafe49044c3ae 4271 4270 2025-10-27T10:07:22Z Madonuko 140 fix grammar wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to handle [[package]]s, [[software]] delivered in specific formats. Regular functions include [[install]]ing, removing, updating, and searching packages, usually from a package [[repository]]. === List of Package Managers === Note: The ''Used By'' field also implies [[derivative]]s, which are listed in the [[Linux Distributions]] page. There are exceptions to this rule, specifically cross-distribution package managers such as [[snap]], [[nix]] and [[flatpak]]. For a list of package formats, see the [[package]] page. {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[Shell]]|| [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise (SLE)|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |} == References == <references /> 3909e1e961249dd2bbe834975209c614fb906c98 10 1043 4260 2025-10-25T22:24:02Z Ow0cast 249 Create FileBox template wikitext text/x-wiki <div role="presentation" class="mw-code filebox"> <div class="filebox-title"> <span class="filebox-badge">{{uc:{{{lang|FILE}}}}}</span> {{{title|}}} </div> <hr> {{#tag:syntaxhighlight |{{{content|[empty file]}}} |lang={{{lang|text}}} |class=filebox-content |line=1 }} </div> <templatestyles src="Template:FileBox/styles.css" /> <noinclude> <templatedata> { "params": { "lang": { "label": "Language", "description": "The language to use for syntax highlighting. For languages that have abbreviations (i.e. Javascript is JS) the abbreviation should be used", "example": "js", "type": "string" }, "title": { "label": "Title", "description": "The title to display above the contents. Should either be a short description of the contents do, a file path or the name of a file", "example": "Launch Firefox on start, /etc/portage/make.conf, Makefile", "type": "string", "suggested": true }, "content": { "label": "Contents", "description": "The contents of the file.", "suggested": true } }, "description": "A box to show the content of text-based files in. Optionally syntax-highlighted.", "format": "block" } </templatedata> </noinclude> 393f4f8ebff1a8e6d16ec845b1f60ce20b600d6f 10 1044 4261 2025-10-25T22:24:32Z Ow0cast 249 Create FileBox template styles sanitized-css text/css .filebox { padding: 0; margin: 0; } .mw-code { white-space: nowrap; /* makes it not suck on vector */ } .mw-highlight .linenos { background-color: unset; } .filebox-title { padding: 0.75em; margin: 0; } .filebox p { margin: 0; } .filebox-badge { border-radius: 4px; padding: 4px; background-color: var(--color-syntax-red); } .filebox hr { margin: 0; } .filebox-content { padding: 0.5em; background-color: var(--color-surface-1); margin: 0; } 03b0838678d9815e188fcc8354567948a172bdde 4266 4261 2025-10-26T16:15:26Z Ow0cast 249 Change FILE badge highlight to blue sanitized-css text/css .filebox { padding: 0; margin: 0; } .mw-code { white-space: nowrap; /* makes it not suck on vector */ } .mw-highlight .linenos { background-color: unset; } .filebox-title { padding: 0.75em; margin: 0; } .filebox p { margin: 0; } .filebox-badge { border-radius: 4px; padding: 4px; background-color: var(--color-progressive); } .filebox hr { margin: 0; } .filebox-content { padding: 0.5em; background-color: var(--color-surface-1); margin: 0; } 6a6c550380c080b3f63c880e5d01a509448509e6 0 907 4262 4177 2025-10-26T13:02:57Z Ivanovics 150 Update to the new filebox template wikitext text/x-wiki [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available in PipeWire 0.3.45) can be placed in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz {{FileBox|title=/etc/pipewire.conf|line=1|content= context.properties = { default.clock.rate = 192000 default.clock.allowed-rates = [ 48000 44100 ] } }} Up to 16 default clock rates can be specified in this manner You can read more about configuring PipeWire [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] == Interacting with PipeWire == PipeWire can be controlled with PulseAudio tools, such as '''pactl''', or without depending on pulseaudio it can be achieved with wpctl (if the Wireplumber session manager is used) or pw-cli (available at all times). === Controlling volume === Using '''wpctl''' to increase the volume by ex. 5% <code>wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+</code> Alternatively, the same can be achieved with '''pw-cli''' First, find the node by running <code>pw-cli ls Node</code>, then run <code>pw-cli s <numical node id> Props '{mute: false, channelVolumes: [ 0.2, 0.2 ] }' </code> to unmute and set the volume of the application to 20% 822b2c569995f91ec8abcc010d2484b7ed80c010 4263 4262 2025-10-26T13:16:31Z Ivanovics 150 Preliminary patchbay stuff, will rewrite probably wikitext text/x-wiki [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available in PipeWire 0.3.45) can be placed in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz {{FileBox|title=/etc/pipewire.conf|line=1|content= context.properties = { default.clock.rate = 192000 default.clock.allowed-rates = [ 48000 44100 ] } }} Up to 16 default clock rates can be specified in this manner You can read more about configuring PipeWire [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] == Interacting with PipeWire == PipeWire can be controlled with PulseAudio tools, such as '''pactl''', or without depending on pulseaudio it can be achieved with wpctl (if the Wireplumber session manager is used) or pw-cli (available at all times). === Controlling volume === Using '''wpctl''' to increase the volume by ex. 5% <code>wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+</code> Alternatively, the same can be achieved with '''pw-cli''' First, find the node by running <code>pw-cli ls Node</code>, then run <code>pw-cli s <numical node id> Props '{mute: false, channelVolumes: [ 0.2, 0.2 ] }' </code> to unmute and set the volume of the application to 20% === GUI patchbays === There are multiple GUI patchbays available for Pipewire, such as [https://gitlab.freedesktop.org/pipewire/helvum helvum] which is a GTK based patchbay, [https://gitlab.freedesktop.org/rncbc/qpwgraph qpwgraph] is available for those who prefer a Qt based patchbay, or [https://github.com/dimtpap/coppwr coppwr] which is made with Rust and uses egui and eframe. e4872df0eb3d9436965e2feabc00b257a91e21c3 4264 4263 2025-10-26T13:19:58Z Ivanovics 150 Put Pipewire into Category:Software wikitext text/x-wiki [[Category:Software]] [https://pipewire.org/ Pipewire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available in PipeWire 0.3.45) can be placed in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz {{FileBox|title=/etc/pipewire.conf|line=1|content= context.properties = { default.clock.rate = 192000 default.clock.allowed-rates = [ 48000 44100 ] } }} Up to 16 default clock rates can be specified in this manner You can read more about configuring PipeWire [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] == Interacting with PipeWire == PipeWire can be controlled with PulseAudio tools, such as '''pactl''', or without depending on pulseaudio it can be achieved with wpctl (if the Wireplumber session manager is used) or pw-cli (available at all times). === Controlling volume === Using '''wpctl''' to increase the volume by ex. 5% <code>wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+</code> Alternatively, the same can be achieved with '''pw-cli''' First, find the node by running <code>pw-cli ls Node</code>, then run <code>pw-cli s <numical node id> Props '{mute: false, channelVolumes: [ 0.2, 0.2 ] }' </code> to unmute and set the volume of the application to 20% === GUI patchbays === There are multiple GUI patchbays available for Pipewire, such as [https://gitlab.freedesktop.org/pipewire/helvum helvum] which is a GTK based patchbay, [https://gitlab.freedesktop.org/rncbc/qpwgraph qpwgraph] is available for those who prefer a Qt based patchbay, or [https://github.com/dimtpap/coppwr coppwr] which is made with Rust and uses egui and eframe. e3e0c5d99af4e75cc07848f2a8bbc55a590334b9 4274 4264 2025-10-27T19:05:52Z Ivanovics 150 Fix grammar and capitalization mistakes wikitext text/x-wiki [[Category:Software]] [https://pipewire.org/ PipeWire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available since PipeWire 0.3.45) can be placed in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz {{FileBox|title=/etc/pipewire.conf|content= context.properties = { default.clock.rate = 48000 default.clock.allowed-rates = [ 48000 44100 ] } }} Up to 16 default clock rates can be specified in this manner Similarly, it is possible to set the minimum quantum to prevent stuttering in the following manner: {{FileBox|title=/etc/pipewire.conf|content= default.clock.min-quantum = 2048 }} More information about configuring PipeWire can be found [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] == Interacting with PipeWire == PipeWire can be controlled with PulseAudio tools, such as '''pactl''', or (without PulseAudio) it can be achieved with wpctl (if the Wireplumber session manager is used) or pw-cli (available at all times). === Controlling volume === Using '''wpctl''' to increase the volume by ex. 5% <code>wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+</code> Alternatively, the same can be achieved with '''pw-cli''' First, find the node by running <code>pw-cli ls Node</code>, then run <code>pw-cli s <numical node id> Props '{mute: false, channelVolumes: [ 0.2, 0.2 ] }' </code> to unmute and set the volume of the application to 20% === GUI patchbays === There are multiple GUI patchbays available for Pipewire, such as [https://gitlab.freedesktop.org/pipewire/helvum helvum] which is a GTK based patchbay, [https://gitlab.freedesktop.org/rncbc/qpwgraph qpwgraph] is available for those who prefer a Qt based patchbay, or [https://github.com/dimtpap/coppwr coppwr] which is made with Rust and uses egui and eframe. 420218d6bc65cb99c4738444efc1b9074ef9a123 4280 4274 2025-11-01T10:59:52Z Atmois 13 Atmois moved page [[Pipewire]] to [[PipeWire]]: Misspelled title: Correct as per official name wikitext text/x-wiki [[Category:Software]] [https://pipewire.org/ PipeWire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available since PipeWire 0.3.45) can be placed in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz {{FileBox|title=/etc/pipewire.conf|content= context.properties = { default.clock.rate = 48000 default.clock.allowed-rates = [ 48000 44100 ] } }} Up to 16 default clock rates can be specified in this manner Similarly, it is possible to set the minimum quantum to prevent stuttering in the following manner: {{FileBox|title=/etc/pipewire.conf|content= default.clock.min-quantum = 2048 }} More information about configuring PipeWire can be found [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] == Interacting with PipeWire == PipeWire can be controlled with PulseAudio tools, such as '''pactl''', or (without PulseAudio) it can be achieved with wpctl (if the Wireplumber session manager is used) or pw-cli (available at all times). === Controlling volume === Using '''wpctl''' to increase the volume by ex. 5% <code>wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+</code> Alternatively, the same can be achieved with '''pw-cli''' First, find the node by running <code>pw-cli ls Node</code>, then run <code>pw-cli s <numical node id> Props '{mute: false, channelVolumes: [ 0.2, 0.2 ] }' </code> to unmute and set the volume of the application to 20% === GUI patchbays === There are multiple GUI patchbays available for Pipewire, such as [https://gitlab.freedesktop.org/pipewire/helvum helvum] which is a GTK based patchbay, [https://gitlab.freedesktop.org/rncbc/qpwgraph qpwgraph] is available for those who prefer a Qt based patchbay, or [https://github.com/dimtpap/coppwr coppwr] which is made with Rust and uses egui and eframe. 420218d6bc65cb99c4738444efc1b9074ef9a123 4284 4280 2025-11-01T16:04:12Z Ivanovics 150 Added a bit of an explanation about what patchbays are wikitext text/x-wiki [[Category:Software]] [https://pipewire.org/ PipeWire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available since PipeWire 0.3.45) can be placed in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz {{FileBox|title=/etc/pipewire.conf|content= context.properties = { default.clock.rate = 48000 default.clock.allowed-rates = [ 48000 44100 ] } }} Up to 16 default clock rates can be specified in this manner Similarly, it is possible to set the minimum quantum to prevent stuttering in the following manner: {{FileBox|title=/etc/pipewire.conf|content= default.clock.min-quantum = 2048 }} More information about configuring PipeWire can be found [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] == Interacting with PipeWire == PipeWire can be controlled with PulseAudio tools, such as '''pactl''', or (without PulseAudio) it can be achieved with wpctl (if the Wireplumber session manager is used) or pw-cli (available at all times). === Controlling volume === Using '''wpctl''' to increase the volume by ex. 5% <code>wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+</code> Alternatively, the same can be achieved with '''pw-cli''' First, find the node by running <code>pw-cli ls Node</code>, then run <code>pw-cli s <numical node id> Props '{mute: false, channelVolumes: [ 0.2, 0.2 ] }' </code> to unmute and set the volume of the application to 20% === GUI patchbays === Patchbays are tools that are designed to manage PipeWire's audio, video and MIDI connections in a user-friendly manner. There are multiple GUI patchbays available for Pipewire, such as [https://gitlab.freedesktop.org/pipewire/helvum helvum] which is a GTK based patchbay, [https://gitlab.freedesktop.org/rncbc/qpwgraph qpwgraph] is available for those who prefer a Qt based patchbay, or [https://github.com/dimtpap/coppwr coppwr] which is made with Rust and uses egui and eframe. cba3ff7007a69d3a757007df62850848f86bb30f 0 884 4265 4172 2025-10-26T13:49:14Z Satnus 215 Cleaned up the citations. wikitext text/x-wiki {{Work In Progress}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.2.0, Apr 17, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>[https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFM file manager is ported to Qt? – LXDE Blog], PCMan, 2013 (Accessed: 2025-10-26)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>[https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ “The future of Razor and LXDE-Qt” – LXDE Blog], PCMan, 2013 (Accessed: 2025-10-26)</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>[https://lubuntu.me/ Lubuntu – The official Lubuntu home], Lubuntu, 2025 (Accessed: 2025-10-26)</ref> * [[Fedora]] LXQt spin<ref>[https://fedoraproject.org/spins/lxqt Fedora LXQt Spin | The Fedora Project], Fedora, 2025 (Accessed: 2025-10-26)</ref> * [[CachyOS]]: available in installer<ref>[https://wiki.cachyos.org/installation/desktop_environments/ Desktop Environments | CachyOS], CachyOS, 2025 (Accessed: 2025-10-26)</ref> * [[SparkyLinux]]<ref>[https://wiki.sparkylinux.org/doku.php/about about Sparky Wiki], Sparky Linux, 2025 (Accessed: 2025-10-26)</ref> * [[Debian]]: available in installer<ref>[https://wiki.debian.org/LXQt LXQt - Debian Wiki], Debian Wiki, 2025 (Accessed: 2025-10-26)</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>[https://packages.debian.org/stable/lxqt-core Debian -- Details of package lxqt-core in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>[https://packages.debian.org/trixie/lxqt Debian -- Details of package lxqt in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>[https://packages.debian.org/stable/task-lxqt-desktop Debian -- Details of package task-lxqt-desktop in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>[https://archlinux.org/groups/x86_64/lxqt/ Arch Linux - lxqt (x86_64) - Group Details], Arch Linux, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>[https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template void-packages/srcpkgs/lxqt/template at master · void-linux/void-packages · GitHub], Github, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], LXQt wiki, 2025 (Accessed: 2025-10-26)</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>[https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions Launching LXQt sessions · lxqt/lxqt Wiki · GitHub], LXQt wiki, 2025 (Accessed:2025-10-26)</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight lang="text">exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == 6bc0d9ba416d3eaa48a322632455ee35341b1e75 0 235 4267 3661 2025-10-26T18:05:24Z Ivanovics 150 Update make.conf example to use the filebox template wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Portage | releasestatus = Maintained | lastrelease = portage-3.0.65 (2024-06-04)<ref>[https://github.com/gentoo/portage/blob/master/NEWS portage/NEWS at master · gentoo/portage · GitHub], Gentoo Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> | languages = Bash, Python | developers = [[Gentoo]] | website = [https://wiki.gentoo.org/wiki/Project:Portage wiki.gentoo.org/wiki/Project:Portage] }} [[Category:Package Managers]] [[File:Portage.png|thumb|A binary version of the package 'git' being installed via portage.]] Portage is considered the heart of every [[Gentoo]] and Gentoo-based distribution and it performs most key functions on Gentoo systems. A part of Portage is also the [[Package Manager|package manager]], although every package is managed by '''emerge'''. Every package installed using Portage is compiled from source, which optimizes it for your system and allows them to be more secure, although binaries are available if the user likes. === Configuration === Configuration of Portage is done through various configuration files and folders found in /etc/portage, which allows configuration of features such as USE flags, default options, masked packages and more. ==== make.conf ==== make.conf is the main configuration file for Portage. It allows the configuration of system-wide USE flags, Portage features, accepted licenses and more. This file is regularly edited during the Gentoo installation process and during ordinary use of it, so it's very important to get the options right for it. Below are some of the most relevant ones. ===== COMMON_FLAGS, CFLAGS, CXXFLAGS, FCFFLAGS and FFLAGS ===== These variables determine the build and compile flags that will be used for all package compilations. The CFLAGS variable is for C applications, while the CXXFLAGS one is meant for C++ ones. Most users will keep these variables identical. A "safe" configuration to avoid compilation errors should look like this: {{FileBox|title=/etc/portage/make.conf|line=1|content= COMMON_FLAGS="-march=native -O2 -pipe" CFLAGS="${COMMON_FLAGS}" CXXFLAGS="${COMMON_FLAGS}" FCFLAGS="${COMMON_FLAGS}" FFLAGS="${COMMON_FLAGS}" }} ===== MAKEOPTS ===== The MAKEOPTS variable is used to specify arguments that will be passed to [[Make]] during compilation. A good rule of thumb is to set the -j argument to about half your RAM size and the -l argument to the thread count of your CPU, which can be found by running <code>nproc</code>. For example, if you have 4 GB of RAM and a 6th generation Intel Core i3, your MAKEOPTS variable should look something like this:<blockquote><code>MAKEOPTS="-j2 -l4"</code></blockquote> ===== GENTOO_MIRRORS ===== The GENTOO_MIRRORS variable tells Portage what mirror(s) to download the packages from. It can be set manually by editing the variable with a link to the mirror(s) of your liking available [https://www.gentoo.org/downloads/mirrors/ here], or automatically via <code>mirrorselect</code>, which can select the fastest mirror(s) for you. It's highly recommended to set this variable to a mirror close to you, for example, if you want to use an Italian mirror you would have to edit the variable like this:<blockquote><code>GENTOO_MIRRORS="<nowiki>https://gentoo.mirror.garr.it/</nowiki>"</code></blockquote> ===== FEATURES ===== The FEATURES variable contains a list of features that you can enable which notably alters the behavior of Portage. For example, if you want to use binary packages and verify their signatures, you would have to set the variable like this:<blockquote><code>FEATURES="getbinpkg binpkg-request-signature"</code></blockquote> ===== EMERGE_DEFAULT_OPTS ===== The EMERGE_DEFAULT_OPTS variable contains the options that will be automatically set when running Portage every time. For example, if you want Portage to ask for confirmation and verbose output, you would set the variable to this:<blockquote><code>EMERGE_DEFAULT_OPTS="--ask --verbose"</code></blockquote> ===== USE ===== The USE variable allows the '''system-wide''' enabling or disabling of USE flags. An example of this variable may look like this:<blockquote><code>USE="pulseaudio X systemd dbus policykit udisks dist-kernel -alsa -wayland xwayland"</code></blockquote> ===== USE_EXPAND ===== USE_EXPAND is a set of variables that serve to extend the capabilities of USE flags. Below are the most relevant ones. ====== VIDEO_CARDS ====== VIDEO_CARDS is a variable that serves to specify the drivers you wish to install for your GPUs. For example, if you want to install the drivers for AMD and Intel graphics, you would set the variable to this:<blockquote><code>VIDEO_CARDS="amdgpu radeonsi intel"</code></blockquote> ====== CPU_FLAGS_* ====== The CPU_FLAGS_* variables specify the available features that your CPU has to optimize compiling packages. The currently available variables are CPU_FLAGS_X86 (for x86 and x86_64 architectures), CPU_FLAGS_ARM (for ARM and ARM64 architectures) and CPU_FLAGS_PPC (for PowerPC and PowerPC64 architectures). The <code>cpuid2cpuflags</code> utility can be used to find these flags. The output of this command may look something like this:<blockquote><code>CPU_FLAGS_X86: aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3</code></blockquote>The output can then be copied to make.conf. ===== ACCEPT_LICENSE ===== The ACCEPT_LICENSE variable can be used to tell Portage which type of licenses are allowed. Generally, it's preferred to not accept proprietary software licenses. To allow every license except proprietary ones, you can set the variable to this:<blockquote><code>ACCEPT_LICENSE="* -@EULA"</code></blockquote> == References == 9e9f4e26df714da7622c15df06cd71435951ecb2 2 1045 4268 2025-10-26T22:29:35Z Hetman Foko 221 Created page with "hi I'm Foko. if you want to learn anything about me for some reason check out hetman.at/me." wikitext text/x-wiki hi I'm Foko. if you want to learn anything about me for some reason check out hetman.at/me. 106587c65151cb150be1d5a67d60bcdf3821fd8b 0 1046 4269 2025-10-27T09:55:06Z Madonuko 140 #REDIRECT [[Package]] wikitext text/x-wiki #REDIRECT [[Package]] 23dccbd6ee5a621fe55e49057ef2144c2c655be9 0 1005 4272 4042 2025-10-27T10:16:52Z Madonuko 140 tidy up links and words wikitext text/x-wiki {{Needs Citations}} A variety of ways for installing [[software]] are available on most [[Unix]]-like systems, which will be explained below. == Software Repositories == :''Main Article: [[Repository]]'' Software programs may be downloaded from a centralised software [[repository]], possibly in the format of [[package]]s or [[binary|binaries]]. This process could be manual or automatic — users may choose to download these software manually instead of using automation tools. In many cases however, the word ''repository'' refers to the latter, where a ''package manager'' is required to extract, decode, and install the contents of a package, as explained in the next section. [[File:KDE Discover home page.png|right|thumb|The home page of the [[KDE]] [[Discover]] program, showing popular and recommended software.]] === Package Managers === :''Main Article: [[Package manager]]'' Software distributed in the form of '''software packages''' may be installed via various ''package managers''. Some package managers are specific to a [[Linux Distributions|distribution]] (or a branch of distributions), while others may be used across different distributions or even different [[Operating System|operating system]]s. On this wiki, the start of a distribution page contains an info box indicating its main supported package managers. Consult the corresponding pages on how to use them. In many cases this is the preferred way of installing software, as it's convenient to update all installed packages at once. For distribution-specific package managers, the packages are usually provided by the same distributions maintainers, making package breakages very unlikely. For package managers that ship packages directly provided by upstream (i.e. the maintainers of the software), the packages are usually more up-to-date with minimal security concerns, and upstream support is usually better. ==== Distribution Package Managers ==== Some package formats are specific to distributions. For [[Debian]]-based distributions, [[dpkg]] is used, and for [[Red Hat]] based distributions, [[rpm]] is used. In most cases, the matching package format must be used, otherwise installation is not possible. [[File:Flathub main website dark.png|right|thumb|The Flathub home featuring different flatpak packages]] ==== Cross-platform Package Managers ==== Some package managers like [[flatpak]] and [[snap]] provide software support for different distributions, in the format of [[sandbox]]ing. While other repositories are available, the mainstream repo for Flatpak is [[Flathub]], which contains both [[open source]] and [[proprietary]] software. For snap, [[Canonical]] [[Snapcraft]] is the default snap repository. Common package managers that do not involve sandboxing include [[brew]], [[nix]]. Some [[Programming languages]] provide their own package manager such as [[pip]] and [[cargo]]. [[File:AppImageHub home page.jpg|left|thumb|Home page of AppImageHub showing different software categories]] == AppImages == :''Main Article: [[AppImage]]'' When a software is not available as a package or in a repository, usually the second option is to use an '''AppImage''' provided by upstream. The same AppImage may be run on most [[Linux]] distributions as long as the [[architecture]] is correct. '''AppImages do not support updates'''. In many cases, users are required to download a newer version from upstream in order to update their AppImages. Software in AppImage formats are also significantly less optimised compared to ones provided by corresponding distributions. Some third-party services like [[AppImageHub]] provide centralised repositories of software for users to download manually. <div style="clear: both"></div> == Binaries == :''Main Article: [[Executable]]'' Sometimes upstream provides pre-compiled binaries (possibly in a [[tar]]ball) for users to download directly. These binaries are usually optimised to some degree, but may not run on obscure setups (e.g. older systems). == Manual Compilation == If the source code is available, users may manually [[compile]] the program. This produces an executable most optimised for the system, and possibly has the highest chance of working correctly. The major downside however is that this requires technical knowledge and takes time. == Tips, Tricks & Troubleshooting == === When NOT to use Flatpak === Refrain from installing the following types of software via flatpak and/or other sandboxing package managers. {| class="wikitable" ! Software !! Reason |- | [[Terminal]] emulators | These often only work properly when run directly on the host system. |- | [[CLI]]/[[TUI]] applications | The UX of flatpak isn't optimized for these types of applications. |- | Modded/Multi-instance game launchers (e.g. Minecraft launchers) | May require access to system libraries, and can be better managed by the user when not sandboxed. For example Minecraft launchers can easily access multiple [[JRE]] installations when not sandboxed. |- | Other appliactions that require manual modification of data files | Requires user to modify its data files regularly, applies in the same above case. |- | Applications that suffer major performance or technical issues due to sandboxing ([[IDE]]s, [[text editor]]s, [[file manager]]s, [[DAW]]s and other applications that rely on native [[plugin]] support like [[VST]]s or [[LV2]], etc.) | Usually require systems libraries to be present to work properly. |- | System components | Part of the [[OS]] |- | System [[library|libraries]] | Required to build or use the aforementioned packages |} === Finding Packages === The '''third-party''' websites listed in this section are '''unaffiliated''' with All Things Linux and/or this wiki, and provide instructions that may be '''potentially dangerous''', which readers should understand clearly before proceeding with caution. [[File:Command-not-found-com_vim_page.png|left|thumb|The vim page on [https://command-not-found.com/vim command-not-found.com]<nowiki/>]] [https://command-not-found.com/ command-not-found.com] may be used to search for common command-line utilities. While it provides command-line specific instructions for mainstream distributions, other distributions are not supported, and only a small set of packages are registered. [[File:Pkgs.org_search_zed.png|right|thumb|Searching ''Zed'' in package summaries on pkgs.org]] [[pkgs.org]] [https://pkgs.org] provides command-line instructions for installing packages, alongside package information, with better UX for searching packages. Try searching for <code>/usr/bin/''binname''</code> when in doubt. Alternatively, [[Repology]] [https://repology.org] provides better coverage since it includes more third party repositories (notably the [[AUR]]), but comes with worse UX for searching packages (i.e. ''projects'' in Repology terms). Note that the former does not include Canonical Snapcraft [https://snapcraft.io], while the latter supports neither Flathub [https://flathub.org] nor Snapcraft. Some distributions such as [[OpenSUSE]] [https://search.opensuse.org/packages/] also provide dedicated websites for finding packages provided by the distributions. === Missing or Broken Distribution Packages === When a package does not exist or breaks, bug reports or requests should be given to repository maintainers. Avoid reporting directly to upstream maintainers unless they directly maintain the packages in question (which applies to many Flathub packages). In the meantime, '''advanced''' users could try to mitigate the issue: ; Missing runtime dynamic libraries : In case of [[wikipedia:Dynamic linker|dynamically link]]ed programming languages, you may see the following errors:<syntaxhighlight lang="shell-session"> /usr/bin/my_program: error while loading shared libraries: libexample.so.0: cannot open shared object file: No such file or directory /usr/bin/my_program: symbol lookup error: /usr/lib64/libexample.so.0: undefined symbol: some_example_symbol_123</syntaxhighlight> : The former error indicates that the library required is not installed, so you can find the package that provides the dynamic library and install it, e.g. with pkgs.org or your package manager: ([[dnf]] example)<syntaxhighlight lang="shell-session"> # dnf install 'libexample.so.0()(64bit)' </syntaxhighlight> : For other package formats that do not support ''provides'': :# search the RPM provides on pkgs.org :# click into any RPM packages :# go to the files section and copy the full [[soname]] [[path]] (e.g. <code>/usr/lib64/libexample.so.0</code>) :# paste the file path into the search bar to search again : If the library could not be found, the compiled executable is probably out of date. : The latter error is a result of [[wikipedia:Application binary interface|ABI]] mismatch, and can only be solved by obtaining the correct library version. Make sure your system is up to date, then contact the package maintainer of <code>my_program</code>. Usually this indicates the program (<code>my_program</code> in this case) needs to be recompiled. ; Missing modules for scripting languages : For software written in scripting languages, you may see the following errors:<syntaxhighlight lang="shell-session"> $ example_python_program Traceback (most recent call last): ... ImportError: No module named my_module $ example_nodejs_program Error: Cannot find module 'my_module' ... </syntaxhighlight> : These modules may be installed manually in the meantime: ([[apt]]/[[pacman]] example)<syntaxhighlight lang="shell-session"> # apt install python3-my-module # pacman -Syu node-my-module </syntaxhighlight> 0ce84f8da2286552f9c137bbb495c1e95b0b5e1a 0 1007 4273 4048 2025-10-27T14:41:18Z Ivanovics 150 Replace Ubuntu for Debian as the original distro for apt wikitext text/x-wiki {{stub}} [[Category:Terminology]] The term '''package''' refers to designated file [[archive]]s, containing metadata, and files for a piece of [[software]], a desktop theme, development headers, fonts, source code, etc., and bundling these files could benefit a significant group of users.<ref>[https://www.geeksforgeeks.org/linux-unix/understanding-package-managers-and-systemctl/ Understanding Package Managers and systemctl], GeeksforGeeks, 2025-07-23 (Accessed: 2025-09-02)</ref><ref>[https://www.howtouselinux.com/post/understanding-package-management-a-guide-to-package-managers-in-linux Understanding Package Management: A Guide to Package Managers in Linux], David Cao, 2023-10-09 (Accessed: 2025-09-02)</ref><ref>[https://linuxsimply.com/linux-basics/package-management/what-is-package/ What is Package in Linux? <nowiki>[Types, Features & More]</nowiki>], Afia Zahin Oishi, 2023-12-31 (Accessed: 2025-09-02)</ref> While not necessarily being the case, many package formats require their own [[package manager]]s to actually extract and [[install]] the bundled files onto a system; and most [[Linux distributions]], other [[UNIX]]-like [[operating system]]s and some [[programming languages]] also come with their own package managers. Package managers, as the name suggests, allow end-users to perform package-related system maintenance tasks, including searching, installing, removing, and updating packages. While packages may be delivered individually, distributions usually gather a set of common packages into their own ''software [[repository|repositories]]'' where package managers search and download packages from. The existence of repositories enables updates to be shipped semi-automatically to a large group of users in an efficient manner, replacing the need for programs to perform their own autoupdate checks. == List of Package Formats == Archive format is represented without the first dot, and distributions are listed with their shorter common names if any. Programming languages are in parentheses. Package managers that do not come with their own file formats are not listed here. See [[package manager]] instead. Immutable variants (esp. [[OSTree]]) that are only wrappers are not listed. {| class="sortable wikitable" ! Format !! Package Manager !! Distributions |- |[[AppImage]] || - ||* |- |[[crate]]||[[cargo]]||([[Rust]]) |- |[[deb]]||[[dpkg]]||[[Debian]] |- |[[deb]]||[[apt]]||[[Debian]] |- |[[ebuild]]||[[portage]]||[[Gentoo]] |- |[[flatpak]]||[[flatpak]]||* |- |[[jar]]|| -||([[Java]]) |- |[[nimble]]||[[nimble]]||([[Nim]]) |- |[[nix]]||[[nix]]||* |- |[[npm]]||[[npm]]||([[JavaScript]]) |- |[[rpm]]||[[dnf]] / [[rpm]]||[[CentOS Stream]] / [[Fedora]] / [[RHEL]] |- |[[rpm]]||[[yum]] / [[rpm]]||[[CentOS]] |- |[[rpm]]||[[zypper]] / [[rpm]]||[[openSUSE]] |- |[[snap]]||[[snap]]||[[Ubuntu]] / * |- |[[Tarball|tar.gz]]||[[pip]]||([[Python]]) |- |[[Tarball|tar.zst]]||[[pacman]]||[[Arch]] |- |[[whl]]||[[pip]]||([[Python]]) |- |[[xbps]]||[[xbps]]||[[Void]] |} == References == 698712a6a694261d2566456c715aefdd49873277 0 1047 4275 2025-10-31T04:28:33Z Madonuko 140 #REDIRECT [[GNU_General_Public_License]] wikitext text/x-wiki #REDIRECT [[GNU_General_Public_License]] 2fbb1c72e9227dc048e27dabee62fe68df59eede 0 1048 4276 2025-10-31T21:41:30Z Aktywnyyy 296 Created page with "'''X.org''' '''X.Org''' (full name: X.Org Server) is the open-source implementation of the X Window System, the graphical foundation used by most traditional '''[[UNIX]]''' and Linux environments. It provides the basic framework for building graphical user interfaces, handling display output, and managing input devices such as the keyboard and mouse. MIT's '''[[X11]]''' project spawned X.Org in the 1980s, though it didn't become the mainline implementation until 2004 a..." wikitext text/x-wiki '''X.org''' '''X.Org''' (full name: X.Org Server) is the open-source implementation of the X Window System, the graphical foundation used by most traditional '''[[UNIX]]''' and Linux environments. It provides the basic framework for building graphical user interfaces, handling display output, and managing input devices such as the keyboard and mouse. MIT's '''[[X11]]''' project spawned X.Org in the 1980s, though it didn't become the mainline implementation until 2004 after forking from '''[[XFree86]]''' due to licensing disputes. X.Org enables desktop environments like '''[[KDE]]''', [[XFCE]], MATE, and [[LXQt]] to function on top of Linux systems such as '''[[Slackware]]''', [[Debian]], [[Ubuntu]], [[Fedora]], [[bazzite]], [[endeavourOS]], [[Arco Linux]]. '''X.Org''' operates on a straightforward client-server model. The '''server''' manages the '''screen''', keyboard, and mouse, while applications (the clients) request window and graphics display. This architecture lets multiple programs share one display and enables running '''graphical programs''' remotely across networks. '''X.Org''' remains widely used across Linux systems, '''although''' a newer technology called '''[[Wayland]]''' is gradually replacing it in some '''distributions'''. Despite this, '''X.Org''' is still valued for its stability, flexibility, and '''compatibility''' with older software — making it a natural fit for some distributions technology. e16af4437b1aa0e211b63fd348c55423d38d6ec4 0 1049 4277 2025-10-31T21:52:23Z Aktywnyyy 296 Created Simple page for KISS Principle wikitext text/x-wiki = KISS Principle = The '''KISS principle''' (short for Keep It Simple, Stupid) is a design philosophy that emphasizes '''simplicity''' and the avoidance of unnecessary complexity. It is commonly applied in engineering, software development, and system design, including many '''[[UNIX]]''' and '''[[LINUX]]''' projects. The idea behind '''KISS''' is that most systems work best when they are kept simple rather than made overly complicated. Designers following this '''philosophy''' strive to build solutions that are easy to understand, maintain, and extend. In software, '''KISS''' often means using straightforward tools and clear code instead of layers of abstraction or automation. This principle aligns closely with traditional [[UNIX]] ideals of doing one thing well and keeping systems modular. The '''KISS''' '''philosophy''' continues to influence the design of '''minimalist''' and user-controlled operating systems, '''lightweight''' software, and development practices that favor clarity and efficiency over convenience or automation. 328d7b78287b534e501797e1c2538660a7b4c3f5 0 178 4278 3636 2025-10-31T21:55:36Z Aktywnyyy 296 Changed See Also links especially Unix link and Open Source Software link wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[Category:Terminology]] [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and deallocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under the terms of the [[GNU General Public License]] version 2 (GPLv2), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] *[[UNIX|Unix]] * [[FOSS|Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> 10d7a45f6cdb4a69ee326a1a8fb8e2b2ad9f0223 2 1027 4279 4194 2025-11-01T02:49:17Z Stewarpt 100 Added more stuff about myself wikitext text/x-wiki Hi I'm stew I usually use my phone (Motorola Moto G Power 5G 2023) for stuff but I also have a computer (Dell Latitude E6440). I also know beginner level C, Haskell and Lua. c083d4ad54f2a913267c3f77d52e4bd71b8df441 0 1050 4281 2025-11-01T10:59:52Z Atmois 13 Atmois moved page [[Pipewire]] to [[PipeWire]]: Misspelled title: Correct as per official name wikitext text/x-wiki #REDIRECT [[PipeWire]] eddc72e3c0e9407d506ba2ab760085a6e9c5381b 0 1051 4282 2025-11-01T14:40:03Z Earldridge Jazzed Pineda 294 Created page with "[[Category:Linux Distributions]] {{DistributionInfobox | title = Solus | image = [[File:Solus.svg|Solus|300px]] | caption = The Solus logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = eopkg | defaultdesktops = Budgie, GNOME, KDE Plasma, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://getsol.us getsol.us] }} '''Solus''' is an independent rolling release [[Linux Distributions|Linux distribution]]..." wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Solus | image = [[File:Solus.svg|Solus|300px]] | caption = The Solus logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = eopkg | defaultdesktops = Budgie, GNOME, KDE Plasma, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://getsol.us getsol.us] }} '''Solus''' is an independent rolling release [[Linux Distributions|Linux distribution]] that is designed for home computing. It uses the eopkg [[package manager]], which was forked from [[Pardus Linux]]'s PiSi package manager.<ref name="thelinuxrain">[https://www.thelinuxrain.org/articles/solus-impressive-most-impressive Solus - Impressive, Most Impressive], Andrew Powell, 2017 (Accessed: November 1, 2025).</ref> Solus is available in four desktop environments: its flagship [[Budgie]] desktop, as well as [[GNOME]], [[KDE Plasma]], and [[Xfce]] (formerly, [[MATE]] was available).<ref name="cyberpanel">[https://cyberpanel.net/blog/solus-linux Solus Linux: A Beginner-Friendly and Independent Linux Distribution], Marium Fahim, 2025 (Accessed: November 1, 2025).</ref> ==History== Solus was created by Ikey Doherty in 2015. Until then, it was known as Evolve OS during development.<ref>[https://www.slwoods.co.uk/?p=5880 Evolve OS changes name to Solus], Steve Woods, 2015 (Accessed: November 1, 2025).</ref> Prior to Solus, he created a [[Debian]]-based distribution called SolusOS.<ref name="thelinuxrain" /> In October 2025, Solus deprecated its "Shannon" software [[repository]] and replaced it with "Polaris", which allowed the Solus developers to remove [[Python]] version 2 and the deprecated Software Center application.<ref>[https://linuxiac.com/solus-begins-a-new-epoch-with-polaris-repository-and-python-2-removal/ Solus Begins a New Epoch with Polaris Repository and Python 2 Removal], Bobby Borisov, 2025 (Accessed: November 1, 2025).</ref> ==Software Management== There are two ways to manage software on Solus. The first is by using a graphical software manager such as [[Discover]] or [[GNOME Software]], and the second is by running <code>eopkg</code> in a terminal. Below is a list of commonly-used <code>eopkg</code> commands:<ref name="cyberpanel" /> {| class="wikitable" ! Command ! Purpose |- |<code>eopkg install <name></code> |Installs a package |- |<code>eopkg remove <name></code> |Removes a package |- |<code>eopkg search <keyword></code> |Searches for packages using the specified keyword |- |<code>eopkg upgrade</code> |Updates all of the packages in the system |} ==References== d29981d4d26dde3563bb4414178024e79a73b834 0 1052 4283 2025-11-01T14:41:34Z Earldridge Jazzed Pineda 294 Redirected page to [[Solus]] wikitext text/x-wiki #REDIRECT [[Solus]] f58943b1e58a0b6f2da679c0a10b1ce256871efc 0 574 4285 4054 2025-11-01T21:26:33Z Rim 297 changed summary description to include correct SwayFX letter casing, and changed summary description to more 'objective' descriptors wikitext text/x-wiki {{Needs_Citations}} {{Cleanup|Installation instructions should be on a separate page in the Guides namespace}} {{SoftwareInfobox |image=[[File:SwayLogo.png|thumb]] |caption=Sway Logo |title=Sway |releasestatus=Maintained |lastrelease=1.11, 2025-06-09 |firstrelease=0.1, 2016-05-24 |languages=[[C]] |developers=Sway Developers |website=[https://swaywm.org/ swaywm.org] }} Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling Wayland compositor. It is meant to be the [[I3]] of Wayland. It takes inspiration from i3 in its design and configuration, and, consequently, it is very backwards-compatible with i3. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[SwayFX]] is a fork of Sway that introduces many rendering effects, such as: blur, shadows, anti-aliased rounded corners, borders and titlebars, dimming of unfocused windows and much more. === Notable Features: === According to Sway's official website: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. == Pre-Installation: == * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] == Installation: == ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For Arch: ==== Using pacman: pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For Debian: ==== Using apt package manager: apt install sway ==== For Fedora: ==== Using dnf package manager dnf install sway 905d2cec3e6ccb9eaada90900e055c747f842079 0 622 4286 4179 2025-11-02T12:21:26Z Rim 297 added COSMIC wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:COSMIC Epoch 1.0.0 alpha with apps.png|[[COSMIC]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity Desktop Environment]] File:XFCE-4.18-Desktop.png|[[XFCE]] File:LXDE-Qt preview.png|[[LXDE]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[COSMIC]] |[[COSMIC]] is a GNOME-based Desktop Environment developed by [[system76]], also known as the creators of [[Pop! OS|Pop! OS.]] COSMIC is built in [[Rust]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} 4de89e6466e70aec14173e54ebda6ae3fc5c1632 0 653 4287 4237 2025-11-02T12:24:47Z Rim 297 changed package manager and release cycle type information to correct ones in the infobox wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox | title = Pop!_OS | image = [[File:Pop! OS Icon.svg|frameless]] | caption = The Pop!_OS logo | releasestatus = Maintained | packagemanager = [[APT]] | defaultdesktops = COSMIC | usagetype = Desktop | architectures = x86_64 | website = Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX] | releasemodel = Stable }} Pop!_OS is a free and open-source [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]], based on [[GNOME]], called [[COSMIC]]. Pop!OS is developed by the American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. == <u>Features</u> == * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle 87a7b48a00221810600c4d711850f54179ddd7cc 0 175 4288 3657 2025-11-02T12:41:36Z Rim 297 changed wording from 'though' to 'although' wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 6.1.0, 2024-03-04 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[Category:Package Managers]] [[File:Pacman 401.png|thumb|[[Pacman]]]] The [[Linux Distributions|Linux distribution]] [[Arch Linux]] and its derivatives usually use a [[Package Manager|package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, although some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>[https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] == References == bec192e8dcb2e303206dd4e99193e0548d08cc43 0 1053 4289 2025-11-02T12:43:29Z Rim 297 redirects Unix to UNIX wikitext text/x-wiki #REDIRECT [[UNIX]] 0cf09966066b69f970594b9e99bc47ae3895f61c 0 659 4290 3591 2025-11-07T17:36:23Z Cherry 131 Correction of some incorrect information (does not use portage and is not rolling release) wikitext text/x-wiki {{DistributionInfobox | title = ChromeOS | image = [[File:Chromium_Logo.svg|frameless]] | caption = ChromiumOs Logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = None | defaultdesktops = Chromium, Aura Shell | usagetype = Desktop | architectures = x86_64, IA-32, ARM, ARM64 | website = [https://chromeos.google/ chromeos] }} ChromeOS (ChromiumOS) is a [[UNIX|Unix-Based]] [[Linux Distributions|Linux distribution]] designed and developed by Google in 2009. ChromeOS is completely open-source.<ref>http://source.chromium.org/chromiumos Official ChromeOS website, 2025 (imported 27th June 2025)</ref> == References == <references /> 34b4146bf4e23d081365988f29380ef4d6d6ab82 4291 4290 2025-11-07T20:41:49Z Imnotgoodatnames 121 ChromeOS and ChromiumOS aren't quite the same thing, most parts of ChromeOS are proprietary, and "Unix-Based Linux distribution" doesn't mean anything. wikitext text/x-wiki {{DistributionInfobox|title=ChromeOS|image=[[File:ChromeOS Logo.svg]]|caption=ChromeOS Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=APT|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website = [http://chromeos.google chromeos.google]}}ChromeOS is a Linux distribution based on [[ChromiumOS]] designed and developed by Google in 2009. ChromeOS is composed mostly of proprietary software but includes open source software, such as the kernel itself.<ref>http://source.chromium.org/chromiumos</ref> a41f5bd6d68fddc495eccdf913dd899135a5a501 4292 4291 2025-11-07T20:44:19Z Imnotgoodatnames 121 marked as stub wikitext text/x-wiki {{stub}} {{DistributionInfobox|title=ChromeOS|image=[[File:ChromeOS Logo.svg]]|caption=ChromeOS Logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=APT|defaultdesktops=Chromium, Aura Shell|usagetype=Desktop|architectures=x86_64, IA-32, ARM, ARM64|website = [http://chromeos.google chromeos.google]}}ChromeOS is a Linux distribution based on [[ChromiumOS]] designed and developed by Google in 2009. ChromeOS is composed mostly of proprietary software but includes open source software, such as the kernel itself.<ref>http://source.chromium.org/chromiumos</ref> 5ca11a883ef555a65a2cfcd28a16d63c2b71b93f 4293 4292 2025-11-07T20:50:01Z Imnotgoodatnames 121 fixed formatting wikitext text/x-wiki {{stub}} {{DistributionInfobox |title=ChromeOS |image=[[File:ChromeOS Logo.svg]] |caption=ChromeOS Logo |releasestatus=Maintained |releasemodel=Rolling Release |packagemanager=APT |defaultdesktops=Chromium, Aura Shell |usagetype=Desktop |architectures=x86_64, IA-32, ARM, ARM64 |website = [http://chromeos.google chromeos.google] }} ChromeOS is a Linux distribution based on [[ChromiumOS]] designed and developed by Google in 2009. ChromeOS is composed mostly of proprietary software but includes open source software, such as the kernel itself.<ref>http://source.chromium.org/chromiumos</ref> == References == 4c009f9252596f18c40d8cc865b84756a583549e 4294 4293 2025-11-07T20:52:44Z Imnotgoodatnames 121 aaaaaaaa wikitext text/x-wiki {{stub}} {{DistributionInfobox |title=ChromeOS |image=[[File:ChromeOS Logo.svg]] |caption=ChromeOS Logo |releasestatus=Maintained |releasemodel=Stable |packagemanager=None |defaultdesktops=Chromium, Aura Shell |usagetype=Desktop |architectures=x86_64, IA-32, ARM, ARM64 |website = [http://chromeos.google chromeos.google] }} ChromeOS is a Linux distribution based on [[ChromiumOS]] designed and developed by Google in 2009. ChromeOS is composed mostly of proprietary software but includes open source software, such as the kernel itself.<ref>http://source.chromium.org/chromiumos</ref> == References == 65f83fd17cbbf7a86209d877651480f153ae0eff 0 1013 4295 4103 2025-11-08T01:31:28Z Cherry 131 Removed Flatpak from the package mangers field as it isn't shipped by default also removed the linking for "Rolling" wikitext text/x-wiki {{DISPLAYTITLE:postmarketOS}} [[Category:Linux Distributions]] {{stub}} {{DistributionInfobox | title = postmarketOS | image = [[File:PostmarketOS_logo.png|postmarketOS logo]] | caption = The postmarketOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APK]] | defaultdesktops = [[Phosh]], [[Plasma Mobile]], [[Sxmo]], [[GNOME]], [[XFCE]] | usagetype = Embedded, Desktop | architectures = amd64, aarch64, ppc64le, loongarch64 | website = [https://postmarketos.org https://postmarketos.org/] }} postmarketOS is an [[Alpine Linux]]-based [[Linux Distributions|distribution]] designed for consumer devices such as phones, tablets, and laptops. Its mission is to extend the lifespan of hardware and give users full control, fostering a more sustainable and open ecosystem. By staying [[open source]], it allows unsupported devices (like old [[Android]] phones) to keep receiving updates from [[package]] [[repository|repositories]] and the mainline Linux kernel, including important security fixes. While many devices still lack full hardware support and daily usability can vary, postmarketOS is evolving quickly through community contributions, making it both a promising path for sustainable device usage and an exciting project for enthusiasts. == History == postmarketOS was announced in May 2017 by [https://github.com/ollieparanoid Oliver Smith (ollieparanoid)], who envisioned a ten-year lifecycle for smartphones, inspired by frustrations with rapid device obsolescence in the Android ecosystem.<ref>[https://postmarketos.org/blog/2017/05/26/intro/ postmarketOS announcement blog], accessed 2025-09-07</ref> Unlike Android, which runs on a heavily modified Linux kernel and relies on proprietary vendor blobs, postmarketOS aims to bring '''mainline Linux kernels''' to as many devices as possible. This design choice increases portability and long-term maintainability. The project gained traction among developers, hackers, and enthusiasts who wanted more control over their devices, with early ports to devices such as the Nokia N900, Google Nexus 5, and various Samsung Galaxy models. Today, dozens of devices are supported to varying degrees, with a few (such as the [[PinePhone]] and [[Librem]] 5) being nearly daily-driver ready. == Installation == The installation process is based around the <code>pmbootstrap</code> tool, which handles building images and flashing them to devices. Users can select supported devices, [[kernel]]s, and user interfaces (like Phosh, Plasma Mobile, [[Sway]], etc). For devices with strong support (such as PinePhone, and other devices on the community category), [https://postmarketos.org/install/ prebuilt] images are available. For older Android phones, users may need to unlock the bootloader and manually flash the generated image from <code>pmbootstrap</code>. Similar to [[Arch Linux]]’s [[archinstall]] script, <code>pmbootstrap</code> automates configuration while still allowing advanced customization. == References == 3b46b22a895158642f8dbe539ac4fc4e79143982 0 177 4296 3609 2025-11-08T13:42:53Z Imnotgoodatnames 121 Removed out of place ref (was incorrectly used to define a word), also free and open source software can be sold wikitext text/x-wiki [[Category:Terminology]] '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word libre, meaning "free") and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, distribute and sell the software, modified or not, to everyone. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. FOSS is in contrast to proprietary, or nonfree software, where the software is under restrictive copyright or licensing and the source code is hidden from the users. === Notes === FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == ef6161394079edb46eb125c9c12807d0d35d2fe0 0 173 4297 3601 2025-11-09T20:40:32Z Keiran 236 Add a brief explanation of the role of a display manager as well as some examples of DMs wikitext text/x-wiki {{Cleanup|Incomplete page}} [[Category:Terminology]] [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager ('''GDM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a [[graphical user interface]] that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself. == Role and Functions == The primary role of the Display Manager is to manage and control the graphical display sessions on a system. It performs several essential tasks: * User Authentication: The DM presents the graphical login screen (often referred to as the greeter) to authenticate users by checking their credentials. * Session Initiation: Upon successful login, it starts the user's chosen graphical session, which is typically a full [[Desktop Environment‏‎]] (DE) or a [[Window Manager‏‎]] (WM). Most DMs support both Wayland and X11 backends. * Session Management: It allows for switching between different users or desktop environments without requiring a full system reboot. == Examples == {| class="wikitable sortable" |+ Display Managers |- ! Name !! DE/Type !! Description |- | GDM || GNOME || '''G'''NOME '''D'''isplay '''M'''anager. Default for systems like Fedora and Ubuntu. Well-integrated with Wayland, but often considered more resource-intensive. |- | SDDM || KDE Plasma, LXQt || '''S'''imple '''D'''esktop '''D'''isplay '''M'''anager. Uses Qt/QML for a modern, highly customizable and visually appealing interface. Successor to KDM. |- | LightDM || Xfce, MATE || '''Light'''weight '''D'''isplay '''M'''anager. Known for being lightweight and highly configurable using separate "greeter" programs (e.g., `lightdm-gtk-greeter`). |- | '''XDM''' || X Window System || '''X''' '''D'''isplay '''M'''anager. The original, most basic DM for the X Window System. Minimalist and used primarily for its simplicity. |- | '''Ly''' || TUI || A text-based (TUI/ncurses-like) display manager that runs in the TTY but can launch both X and Wayland sessions, popular for extremely minimal setups. Written in Zig. |- | '''emptty'' || TUI || A dead simple TUI display manager similar to Ly that runs in the TTY and prioritizes simple yet powerful configuration. |} == Configuration == ==== Enabling a Display Manager (systemd) ==== On modern Linux distributions that use systemd, the DM is started as a system service. To switch the active DM, you typically disable the current service and enable the desired one. <syntaxhighlight lang="bash"> # Example: Switching from GDM to SDDM # 1. Stop and disable the old DM service sudo systemctl disable gdm.service sudo systemctl stop gdm.service # 2. Enable the new DM service sudo systemctl enable sddm.service --now # `--now` starts the service immediately once enabled </syntaxhighlight> 2. Session Definition Display Managers discover the available session options (like "GNOME," "KDE," "i3") by reading <code>.desktop</code> files in the following system directories: * `/usr/share/xsessions/` (for X11 sessions) * `/usr/share/wayland-sessions/` (for Wayland sessions) ==== Example: Defining an Openbox session ==== <syntaxhighlight lang="ini"> [Desktop Entry] Name=Openbox Comment=Log in using the Openbox window manager Exec=/usr/bin/openbox-session TryExec=/usr/bin/openbox-session Icon=openbox Type=Application </syntaxhighlight> e81d9e49bda73725264333951c2910e9bd7f1371 0 257 4298 4181 2025-11-10T14:06:10Z DontBlameMe 281 update last release version wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.52.1, 2025-11-10 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor. It was originally based on [[wlroots]] but migrated away from it towards its own rendering backend library [[aquamarine]] in version 0.42.0<ref>[https://hypr.land/news/independentHyprland/ Hyprland moves off wlroots], 2025-09-02 (Accessed 2025-09-02)</ref> It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Hyprland], 2025-08-10 (Accessed: 2025-08-10)</ref> Hyprland uses its own configuration syntax, designed to be readable and easy to learn, with similarities to shell scripting. The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. * '''Hyprlock''' - a highly customizable and efficient Wayland lockscreen * '''Hyprpicker''' - a small utility for picking a color on your current screen == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> be30ddfed0c5582266ee64ec5481c47dc09504d5 0 1054 4299 2025-11-15T00:41:16Z Aktywnyyy 296 Created simple page for KDE Community wikitext text/x-wiki KDE​‍​‌‍​‍‌ stands for a worldwide community that creates [[FLOSS|free and open-source software]] with the goal of enabling people everywhere. One of their flagship projects is KDE Plasma, a state-of-the-art and adaptable graphical user interface that provides users with an attractive, energy-efficient, and extremely customizable computing experience. KDE are committed to providing software that honors the user's freedom and is, at the same time, simple to operate and aesthetically pleasing. As per their perspective, technology should be at the service of humans and not vice versa. Hence, KDE projects concentrate on by usability, accessibility, and innovation. Besides [[Plasma|KDE Plasma]], the community, are driving the development of a vast array of applications that include productivity tools, educational software, multimedia, and programming platforms. They have a policy of making every one of their endeavors [[FLOSS|open-source]] so that the users are free to explore, alter, and distribute their software to ​‍​‌‍​‍‌others. b7c0d200d9e76847a76beb65fe05d62225863ba1 0 1055 4300 2025-11-15T00:46:49Z Aktywnyyy 296 Added Zig Page wikitext text/x-wiki Zig is a modern programming language that focuses on efficiency, simplicity, and safety. It gives developers complete control over their programs while remaining easy to learn and use. Zig is known for its predictability. Programs behave as expected, which helps reduce errors and makes debugging simpler. The language also allows code execution at compile time, enabling improvements before the program runs. Zig works well with [[C (programming language)|C]], allowing developers to use existing libraries. It emphasizes safety with clear memory management and optional types. A growing global community supports Zig by contributing to its development, documentation, and libraries. It is suitable for system programming, high-performance applications, and projects where reliability and control are crucial. 4172e83bc795281d51d221d6f0a7d053adf12c33 0 1056 4301 2025-11-17T04:58:38Z Madonuko 140 init wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Rolling release''' is a software release model where software updates are delivered continuously. Unlike [[stable release]] which is in a discrete manner, rolling release usually implies shipping the latest software as soon as possible. A famous example would be [[Arch Linux]]. Rolling release does not imply unstable software. The software may be tested thoroughly before shipping. An example would be [[openSUSE Tumbleweed]]. The deciding factor for [[distro]]s would be usually whether updates would stop, that is, whether ''mass updates'' are provided, where there are full ''system upgrades'' in which many [[package]]s would be updated together. If so, that violates the fundamental requirements of rolling release. == Semi-rolling == '''Semi-rolling''' is a layman's term for describing distributions providing updates for non-breaking features, bug fixes, etc., while requiring full system upgrades to receive further software updates, otherwise updates will stop eventually. There is no concrete definition and the term is quite ambiguous, but usually this describes stable-release distros like [[Fedora Linux]]. 04ef242bb841e34af273e7ce3f359e10538fa1d7 0 1057 4302 2025-11-17T05:04:34Z Madonuko 140 init wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Stable release''' is used to describe [[distro]]s that provide upgrades in a periodic manner. Unlike distros using the [[rolling release]] model, they usually hold updates back until the distro provides a release, which entails a full system upgrade for users to update the software on their systems to a newer version. If users choose not to perform the system upgrade, updates to their system software will terminate eventually. Examples of such distributions include [[Debian]] and [[RHEL]]. 378627dc59e0ddf5053a79114d5c17ceea851fa1 0 198 4303 4238 2025-11-17T05:26:16Z PhantasNick 291 alphabetized the Distros wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A set of community-developed distribution sponsored by SUSE. It maintains a strict policy of ensuring all code in the installations will be from [[FLOSS|FOSS]] solutions. |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 4aa37d90971b0865c6760cb5d2a2352a9258777d 4306 4303 2025-11-17T09:59:02Z PhantasNick 291 Updated to include each openSUSE Project as we are doing something similar with Fedora Atomic Projects, plus they all attempt to do something different wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |The official immutable/atomic variant of Fedora Linux, with the advantages of Fedora Linux, alongside being safe and reliable. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == f0ef0e3533c902d4ba31ec9daa0964e1d966cf68 4307 4306 2025-11-17T10:07:00Z PhantasNick 291 Added all the Fedora Atomic projects wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76 |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 78dc8b9c16f47458a01a414cff47ae45cc1f7b59 4308 4307 2025-11-17T10:07:21Z PhantasNick 291 Fixed Formatting wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76 |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 444b2f17ac21d5f1fb65bd0c8d46dba58da45f29 3000 608 4304 4082 2025-11-17T05:30:19Z Madonuko 140 /* Tips & Tricks */ wikitext text/x-wiki {{GuideWarning}} Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">[https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims Localization, Internationalization and Multilingualization], Ultramarine Linux, 2024 (Accessed: 2025-05-03)</ref> Users can use the IMF to switch between different IMEs.<ref>[https://wiki.archlinux.org/title/Input_method Input method], ArchWiki, 2020 (Accessed: 2025-05-03)</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>[[wikipedia:Intelligent_Input_Bus|Intelligent_Input_Bus]], Wikipedia, 2009 (Accessed: 2025-05-03)</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>[[wikipedia:Fcitx|Fcitx]], Wikipedia, 2010 (Accessed: 2025-05-03)</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. If this package is not available, create an autostart entry manually at <code>/etc/xdg/autostart/org.fcitx.Fcitx5.desktop</code>:<syntaxhighlight lang="ini"> [Desktop Entry] Name=Fcitx 5 GenericName=Input Method Comment=Start Input Method Exec=/usr/bin/fcitx5 Icon=fcitx Terminal=false Type=Application Categories=System;Utility; StartupNotify=false X-GNOME-AutoRestart=false X-GNOME-Autostart-Notify=false X-KDE-autostart-after=panel X-KDE-StartupNotify=false X-KDE-Wayland-VirtualKeyboard=true X-KDE-Wayland-Interfaces=org_kde_plasma_window_management</syntaxhighlight> * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code><ref name=":0" group="Note">Additionally requires <code>fcitx5-chinese-addon</code> on Fedora due to packaging issues.</ref> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code><ref name=":0" group="Note" />? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code><ref group="Note"><code>fcitx5-mozc-ut</code>^AUR is instead recommended on Arch Linux.</ref> |<code>fcitx-mozc</code><ref group="Note"><code>fcitx-mozc-ut</code>^AUR is instead recommended on Arch.</ref> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |ViQR |<code>fcitx5-m17n</code><ref name=":1" group="Note">This is <code>fcitx5-table-viqr</code>, <code>fcitx-table-viqr</code>, <code>ibus-table-viqr</code> on Debian.</ref> |<code>fcitx-m17n</code><ref name=":1" group="Note" /> |<code>ibus-table-tv</code><ref name=":1" group="Note" /> |<code>uim-viqr</code> | - | - | - | - | - |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<code>uim-m17n</code><ref name=":2" group="Note">On some distros, this is <code>uim-m17nlib</code>.</ref> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code><ref group="Note">Requires the [[Terra]] repository on Fedora.</ref> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code><ref group="Note"><code>ibus-openbangla</code> on Fedora with the [[Terra]] repository.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<code>fcitx5-varnam</code> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Others |- |Thai |<code>fcitx5-libthai</code> | - |<code>ibus-table-tv</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> | - |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Math Symbols |[[Compose Key]]? |[[Compose Key]]? |<code>ibus-table-mathwriter</code> | - | - | - | - | - | - |- |Completion |''built-in'' | - |<code>ibus-typing-booster</code> | - | - | - | - | - | - |- |''"Everything Else"'' |<code>fcitx5-m17n</code>? |<code>fcitx-m17n</code>? |<code>ibus-m17n</code>? |<code>uim-m17n</code><ref name=":2" group="Note" />? | - |<code>scim-m17n</code>? | - | - | - |} === Notes === <references group=Note/> This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. == How to choose your IME == This section represents the general case and the authors' opinions. It is not necessary to follow them. {| class="wikitable" |+Chinese !Situation !IME !Rime IME !Notes |- |Already using [[Rime]] | rowspan="3" |Rime | - | rowspan="3" |Rime is very powerful, but it comes with the cost of writing your own configuration files and [https://github.com/rime/home/wiki reading Chinese documentations], and thus is not recommended to beginners. |- |Prefer a highly customizable experience | - |- |Good at writing configuration files | - |- |Know Pinyin |Pinyin |''built-in'' | |- |Know Zhuyin |Chewing |℞ bopomofo |<code>libzhuyin</code> is not recommended (very unpopular), avoid <code>fcitx5-zhuyin</code> & <code>ibus-libzhuyin</code>. |- |Know Cangjie 3 / Quick 3 | rowspan="2" |Cangjie/Quick | rowspan="2" |℞ cangjie |Rime with [https://github.com/kennethso168/rime-cangjie3-extension rime-cangjie3-extension] |- |Know Cangjie 5 / Quick 5 | |- |Know SmartCangjie 6 |SCJ |℞ scj | |- |Know Jyutping |Rime |℞ cantonese |Jyutping from table-extras is barely usable |- |Know Wubi |Haifeng Wubi | |https://www.zhukun.net/archives/4856 |} {| class="wikitable" |+Japanese !Situation !IME !Notes |- |You hate Qt |Anthy |Anthy is unmaintained but it's written in GTK, so if you want your IME to fit into your GTK theme, use Anthy. |- |Otherwise |Mozc |Mozc is maintained by Google and has better suggestions, but you should also consider using the UT dictionaries. |} == Tips & Tricks == === Electron & Chromium Applications === If your IMF does not work in [[electron]] or [[chromium]]-based applications, add <code>--enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime</code> to the command line arguments. Taking [[Codium]] as an example: {{FileBox|title=~/.local/share/applications/codium.desktop|lang=ini|content= [Desktop Entry] Exec=/usr/bin/codium --no-sandbox --unity-launch %F --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime # ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━ …}} Additionally, avoid using [[Flatpak]]s. === Compose Key === :Main article: [[Compose key]] To use Compose Key in Fcitx5, go to ''Fcitx5 Settings → Global Options'', then in the ''Custom XKB Option'' entry, write <code>compose:rctrl</code>. For IBus, you will need to manually use [[setxkbmap]]. For a list of possible options, see <code>[[man]] 'xkeyboard-config(7)'</code>, section '''Position of Compose Key'''. == References == ab176dafc198272c9f28a4a0d20285bfcd739180 0 1058 4305 2025-11-17T06:02:02Z Madonuko 140 init wikitext text/x-wiki [[Category:Terminology]] The '''Compose key''' can be used to input characters not present on the physical keyboard. Unlike [[input method]]s, users of compose key need to first press a specific key, then press a specific sequence of keys in order to obtain the final character. == Set-up == {{Guide Warning}} === KDE Plasma === In ''System Settings → Input/Output Devices → Keyboard'', press the ''Keybinding'' button on the top right corner. Enable the ''Set Keyboard Options'' checkbox, then select the preferred position in ''Position of Compose Key'', then click ''Apply''. === GNOME === A graphical option is not available. Visit [https://help.gnome.org/admin/system-admin-guide/stable/keyboard-compose-key.html.en this article] for the command-line instructions. === X11 === On [[X11]]-based environments, you can use [[setxkbmap]] to temporarily set the compose key. To permanently set the compose key: {{FileBox|title=~/.xprofile|content= setxkbmap -layout us compose:rctrl }} The list of options other than <code>rctrl</code> is available in <code>[[man]] 'xkeyboard-config(7)'</code>, in the '''Position of Compose Key''' section. === IBus === [[IBus]] users should follow the settings of your graphical environment. === Fcitx5 === To use Compose Key in [[Fcitx5]], go to ''Fcitx5 Settings → Global Options'', then in the ''Custom XKB Option'' entry, write <code>compose:rctrl</code>. == Usage == Press and release the chosen compose key (denoted as {{keypress|Multi}} in this article), {{keypress|o}}, and {{keypress|r}} separately. This produces the ® symbol. Other common shortcuts include {{keypress|Multi|>|{{=}}|chain=}} (which gives ≥) and {{keypress|Multi|-|-|-|chain=}} (which gives —). == Customisation == Apart from the listed combinations in <code>/usr/share/X11/locale/en_US.UTF-8/Compose</code>, compose key users can customise the key combinations. Here is an example: <!-- xorg_conf is no longer supported by the syntax highlighter, rip --> {{FileBox|lang=hcl|title=~/.XCompose|content= # Comments start with a hashtag # Empty lines are ignored include "%L" # import default rules from /usr/share/X11/locale/en_US.UTF-8/Compose <Multi_key> <semicolon> <x> : "❌" <Multi_key> <semicolon> <o> : "⭕" <Multi_key> <minus> <greater> : "→" <Multi_key> <equal> <greater> : "⇒" <Multi_key> <minus> <asciicircum> : "↑" <Multi_key> <equal> <asciicircum> : "⇑" <Multi_key> <minus> <v> : "↓" <Multi_key> <equal> <v> : "⇓" <Multi_key> <less> <minus> : "←" <Multi_key> <less> <equal> : "⇐" <Multi_key> <equal> <less> : "≤" U2264 # Less Than or Equal Symbol <Multi_key> <question> <A> : "∀" # FOR ALL <Multi_key> <question> <E> : "∃" # THERE EXISTS <Multi_key> <question> <I> : "∈" # IN, BELONGS TO <Multi_key> <question> <d> : "∂" U2202 # PARTIAL DIFFERENTIAL <Multi_key> <question> <G> : "∇" U2207 # NABLA (GRADIENT, BACKWARD DIFFERENCE) <Multi_key> <question> <S> : "∑" U2211 # SUMMATION }} ea0c04ff6cd93ded13957d30cdfc0050850a1fce 0 394 4309 1382 2025-11-17T11:36:34Z PhantasNick 291 Reworked the page to be more user friendly, included many more OS's and breif descriptions wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[MS-DOS]] | a command-line operating system developed by Microsoft for early IBM-compatible personal computers |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace [[MS-DOS|DOS]] |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[Windows]] | a proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} 5118884d33f6e0d6e59b9a83e016acca9cd1a877 4310 4309 2025-11-17T11:37:29Z PhantasNick 291 Fixed Formatting wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[MS-DOS]] | a command-line operating system developed by Microsoft for early IBM-compatible personal computers |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace [[MS-DOS|DOS]] |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[Windows]] | a proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} d8622c1f8ec9d06c02a8fcc639cd2088cda9d96f 4311 4310 2025-11-17T11:38:12Z PhantasNick 291 wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[MS-DOS]] | a command-line operating system developed by Microsoft for early IBM-compatible personal computers |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace [[MS-DOS|DOS]] |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[Windows]] | a proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} eb1fae0af39da656f5eaefac6bd080897e9ade3d 2 1059 4312 2025-11-17T15:56:09Z PhantasNick 291 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 4332 4312 2025-12-02T11:48:06Z Alxhr0 265 Add info wikitext text/x-wiki == About: == Howdy, I'm Rafeal! (Alxhr0) I like coding silly things and contributing! * '''Pronouns:''' They/them * '''Location:''' Poland == Contact: == Feel free to contact me through email or ping me on the ATL Discord 9f267ac66cc3d4ce5de4f33dfb37e5b406941d2c 0 1060 4313 2025-11-17T18:21:47Z Ivanovics 150 Basic page describing swap and how to create/activate it wikitext text/x-wiki Swap in computing generally refers to memory paging. Swapping can refer to both moving pages between memory and secondary storage. On Linux, it is possible to use a combination of swap devices and/or swap files, with the ability to assign a priority value to each one individually. Having a swap file is not always necessary, although can be useful if the system runs out of real memory (on, for example systems with 4 or 8 GiB of memory). == Creating Swap == === Swap partition === If '''/dev/sda3''' is the swap partition to be used, it can be formatted as such:<syntaxhighlight lang="sh"> mkswap /dev/sda3 </syntaxhighlight> === Swap File === To avoid the rigidness of a swap partition, it is possible to create a swap file, which can be located ''in'' a partition, and as such can be moved and resized as needed. The utility '''mkswap''' can be used for this purpose as well:<syntaxhighlight lang="sh"> mkswap -U clear --size 4G --file /path/to/swapfile </syntaxhighlight>By making a swapfile like this, the necessary permissions will already be set == Activation == In both cases, be activated with<syntaxhighlight lang="sh"> swapon /dev/sda3 </syntaxhighlight>For a swap partition, or<syntaxhighlight lang="sh"> swapon /path/to/swapfile </syntaxhighlight>For a swap file. It is also recommended to add the swap file to /etc/fstab, to automatically activate it at boot time:<syntaxhighlight> # Swap partition /dev/sda3 none swap sw 0 0 # Swap file /swapfile none swap sw 0 0 </syntaxhighlight> 450395c7c08eace208baf99964c1a769f5303245 4325 4313 2025-11-21T21:17:57Z Ivanovics 150 Tuning, + replace codeblock with filebox template for fstab :kek: wikitext text/x-wiki Swap in computing generally refers to memory paging. Swapping can refer to both moving pages between memory and secondary storage. On Linux, it is possible to use a combination of swap devices and/or swap files, with the ability to assign a priority value to each one individually. Having a swap file is not always necessary, although can be useful if the system runs out of real memory (on, for example systems with 4 or 8 GiB of memory). == Creating Swap == === Swap partition === If '''/dev/sda3''' is the swap partition to be used, it can be formatted as such:<syntaxhighlight lang="sh"> mkswap /dev/sda3 </syntaxhighlight> === Swap File === To avoid the rigidness of a swap partition, it is possible to create a swap file, which can be located ''in'' a partition, and as such can be moved and resized as needed. The utility '''mkswap''' can be used for this purpose as well:<syntaxhighlight lang="sh"> mkswap -U clear --size 4G --file /path/to/swapfile </syntaxhighlight>By making a swapfile like this, the necessary permissions will already be set == Activation == In both cases, be activated with<syntaxhighlight lang="sh"> swapon /dev/sda3 </syntaxhighlight>For a swap partition, or<syntaxhighlight lang="sh"> swapon /path/to/swapfile </syntaxhighlight>For a swap file. It is also recommended to add the swap file to /etc/fstab, to automatically activate it at boot time: {{FileBox | title = /etc/fstab | content = # Swap partition /dev/sda3 none swap sw 0 0 # Swap file /swapfile none swap sw 0 0 }} == Tuning == === Prioritizing an area === It is possible to assign a "priority" value to the swap partitions/files, (an integer from 0 to 32767), with a higher priority area being utilized first. If two different areas share a priority value they are utilized in a round-robin fashion<ref>https://linux.die.net/man/2/swapon</ref> For example, prioritizing a fast NVMe drive (/dev/nvme0n1) before a slow HDD (/dev/sdb): {{FileBox | title = /etc/fstab | content = /dev/nvme0n1p2 none swap sw,pri=16383 0 0 /dev/sdb2 none swap sw,pri=1 0 0 }} 9a2b259b27f6730437770736fe91a6a71b60b41c 4326 4325 2025-11-22T11:28:37Z Ivanovics 150 Add [[Category:Terminology]] wikitext text/x-wiki [[Category:Terminology]] Swap in computing generally refers to memory paging. Swapping can refer to both moving pages between memory and secondary storage. On Linux, it is possible to use a combination of swap devices and/or swap files, with the ability to assign a priority value to each one individually. Having a swap file is not always necessary, although can be useful if the system runs out of real memory (on, for example systems with 4 or 8 GiB of memory). == Creating Swap == === Swap partition === If '''/dev/sda3''' is the swap partition to be used, it can be formatted as such:<syntaxhighlight lang="sh"> mkswap /dev/sda3 </syntaxhighlight> === Swap File === To avoid the rigidness of a swap partition, it is possible to create a swap file, which can be located ''in'' a partition, and as such can be moved and resized as needed. The utility '''mkswap''' can be used for this purpose as well:<syntaxhighlight lang="sh"> mkswap -U clear --size 4G --file /path/to/swapfile </syntaxhighlight>By making a swapfile like this, the necessary permissions will already be set == Activation == In both cases, be activated with<syntaxhighlight lang="sh"> swapon /dev/sda3 </syntaxhighlight>For a swap partition, or<syntaxhighlight lang="sh"> swapon /path/to/swapfile </syntaxhighlight>For a swap file. It is also recommended to add the swap file to /etc/fstab, to automatically activate it at boot time: {{FileBox | title = /etc/fstab | content = # Swap partition /dev/sda3 none swap sw 0 0 # Swap file /swapfile none swap sw 0 0 }} == Tuning == === Prioritizing an area === It is possible to assign a "priority" value to the swap partitions/files, (an integer from 0 to 32767), with a higher priority area being utilized first. If two different areas share a priority value they are utilized in a round-robin fashion<ref>https://linux.die.net/man/2/swapon</ref> For example, prioritizing a fast NVMe drive (/dev/nvme0n1) before a slow HDD (/dev/sdb): {{FileBox | title = /etc/fstab | content = /dev/nvme0n1p2 none swap sw,pri=16383 0 0 /dev/sdb2 none swap sw,pri=1 0 0 }} f7ab6cf344c5c7d435ede4c3198a449bea549f9c 0 1057 4314 4302 2025-11-19T05:29:39Z Madonuko 140 kinda whip wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Stable release''' is used to describe [[distro]]s and [[repository|repositories]] that provide upgrades in a periodic manner. Unlike [[rolling release]], updates are usually held back until a new release, which entails a full system upgrade for users to update the software on their systems to a newer version. If users choose not to perform the system upgrade, updates to their system software will terminate eventually. Examples of such distributions include [[Debian]] and [[RHEL]]. ## Advantages Having a scheduled release allows maintainers to ensure the set of versions of the packages to be compatible with one another. When a software pushes a new version, other software that relies on the older version of that software needs to be repackaged. A release can give time for maintainers to unify the package version requirements. 71255d1d2d4c32f43118f5edfc609032c82f9bad 4315 4314 2025-11-19T05:40:05Z Madonuko 140 advantages and disadvantages wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Stable release''' is used to describe [[distro]]s and [[repository|repositories]] that provide upgrades in a periodic manner. Unlike [[rolling release]], updates are usually held back until a new release, which entails a full system upgrade for users to update the software on their systems to a newer version. If users choose not to perform the system upgrade, updates to their system software will terminate eventually. Examples of such distributions include [[Debian]] and [[RHEL]]. == Advantages == Having a scheduled release allows maintainers to ensure the set of versions of the packages to be compatible with one another. When a software pushes a new version, other software that relies on the older version of that software needs to be repackaged. A release can give time for maintainers to unify these dependency requirements. == Disadvantages == A stable release makes it more difficult to ship up-to-date packages in time, especially ones with breaking changes. be0bab333620d5028007faa945bd3437242b1849 4317 4315 2025-11-19T15:04:44Z Madonuko 140 moved to [[fixed release]] wikitext text/x-wiki #REDIRECT [[Fixed release]] 57e00ca4c4f06b0b863ee05b53a960aa8d9aa86e 0 1061 4316 2025-11-19T15:04:29Z Madonuko 140 from [[stable release]] wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Fixed release''' is used to describe [[distro]]s and [[repository|repositories]] that provide upgrades in a periodic manner, usually under a ''release schedule''.<ref>[https://www.geeksforgeeks.org/linux-unix/rolling-vs-fixed-release-linux-distros/ Rolling vs. Fixed release Linux Distros?], GeeksforGeeks, 2023 (Accessed: 2025-11-19)</ref> Unlike [[rolling release]], updates are usually held back until a new release, which entails a full system upgrade for users to update the software on their systems to a newer version. If users choose not to perform the system upgrade, updates to their system software will terminate eventually. Examples of such distributions include [[Debian]] and [[RHEL]]. == Advantages == Having a scheduled release allows maintainers to ensure the set of versions of the packages to be compatible with one another. When a software pushes a new version, other software that relies on the older version of that software needs to be repackaged. A release can give time for maintainers to unify these dependency requirements. == Disadvantages == The nature of the fixed release model makes it more difficult to ship up-to-date packages in time, especially ones with breaking changes. == References == c81312471f7d621ee9d0721ccfa593b22a29f319 0 1056 4318 4301 2025-11-19T15:05:23Z Madonuko 140 stable → fixed wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Rolling release''' is a software release model where software updates are delivered continuously. Unlike [[fixed release]] which is in a discrete manner, rolling release usually implies shipping the latest software as soon as possible. A famous example would be [[Arch Linux]]. Rolling release does not imply unstable software. The software may be tested thoroughly before shipping. An example would be [[openSUSE Tumbleweed]]. The deciding factor for [[distro]]s would be usually whether updates would stop, that is, whether ''mass updates'' are provided, where there are full ''system upgrades'' in which many [[package]]s would be updated together. If so, that violates the fundamental requirements of rolling release. == Semi-rolling == '''Semi-rolling''' is a layman's term for describing distributions providing updates for non-breaking features, bug fixes, etc., while requiring full system upgrades to receive further software updates, otherwise updates will stop eventually. There is no concrete definition and the term is quite ambiguous, but usually this describes fixed-release distros like [[Fedora Linux]]. 7af38b07577749239737c259a22744708636ba5c 0 1062 4319 2025-11-20T11:29:33Z Madonuko 140 #REDIRECT [[Fixed release]] wikitext text/x-wiki #REDIRECT [[Fixed release]] 57e00ca4c4f06b0b863ee05b53a960aa8d9aa86e 0 198 4320 4308 2025-11-21T08:00:30Z PhantasNick 291 Added KDE Linux wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers. |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76 |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == ac823a799be1216b6045a3877696b04a256a4c4b 4322 4320 2025-11-21T15:11:00Z Landline 196 Add a citation for the description of Omarchy wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use. |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76 |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 8bcf97c2808e2a9e564b999bb6319c9feb3b0e25 4323 4322 2025-11-21T15:13:19Z Landline 196 Add a citation for the Manjaro description wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (Sometimes abbreviated as a 'distro') consists of some form of the [[Kernel|Linux Kernel]], an [[Init System]] (Such as [[systemd]] or [[OpenRC]]), the [[GNU]] tools and libraries, documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (Such as [[X.Org]] or a [[Wayland]] Compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (Such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mostly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76 |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 1c828612499ac4ecd2f2cdc76fab0a4b9ca034a2 4330 4323 2025-11-28T06:12:47Z 0xFF 273 wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them have their distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying to [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed to beginners and long-time Linux users, its focused on optimization and stability, it ships with its own Cachy Kernel and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to MacOS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An Immutable, Proprietary, Gaming centric-OS By Valve that is used to power the Steam Deck<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76 |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 8d164ae9e6b17a644276c29dfb782a1f8bb5acf6 1 384 4321 1366 2025-11-21T15:08:04Z Landline 196 /* New section for Ubuntu based? */ new section wikitext text/x-wiki == This page desperately needs citations == Please add citations and continue to add them in the future [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 20:45, 15 November 2024 (UTC) == New section for Ubuntu based? == Should a section for distributions specifically based on Ubuntu be created or should they go under Debian? I'm personally leaning towards the former but other opinions would be nice. [[User:Landline|Landline]] ([[User talk:Landline|talk]]) 15:08, 21 November 2025 (UTC) cac53a722052f53dbaf1101ed77ca64c97a9e89e 4324 4321 2025-11-21T20:54:37Z Atmois 13 /* New section for Ubuntu based? */ wikitext text/x-wiki == This page desperately needs citations == Please add citations and continue to add them in the future [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 20:45, 15 November 2024 (UTC) == New section for Ubuntu based? == Should a section for distributions specifically based on Ubuntu be created or should they go under Debian? I'm personally leaning towards the former but other opinions would be nice. [[User:Landline|Landline]] ([[User talk:Landline|talk]]) 15:08, 21 November 2025 (UTC) I'm not against it, although if we do it should we separate RHEL/CentOS and Fedora aswell or just split Ubuntu based? It would make the list longer per say but more navigable imo. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 20:54, 21 November 2025 (UTC) e24119796c7b1d13bba6e1d233bc6f125bcf1779 4327 4324 2025-11-22T11:36:12Z Satnus 215 /* New section for Ubuntu based? */ Reply wikitext text/x-wiki == This page desperately needs citations == Please add citations and continue to add them in the future [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 20:45, 15 November 2024 (UTC) == New section for Ubuntu based? == Should a section for distributions specifically based on Ubuntu be created or should they go under Debian? I'm personally leaning towards the former but other opinions would be nice. [[User:Landline|Landline]] ([[User talk:Landline|talk]]) 15:08, 21 November 2025 (UTC) I'm not against it, although if we do it should we separate RHEL/CentOS and Fedora aswell or just split Ubuntu based? It would make the list longer per say but more navigable imo. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 20:54, 21 November 2025 (UTC) :Separate them. I don't think RHEL/CentOS and Fedora will be an issue for the time being. [[User:Satnus|Satnus]] ([[User talk:Satnus|talk]]) 11:36, 22 November 2025 (UTC) eea07a80da87650a9b6dea8839e7e839c60a1fb8 14 390 4328 4037 2025-11-23T10:38:08Z Imnotgoodatnames 121 the Daemon is the generic mascot of BSD, not just FreeBSD (in fact it's older than FreeBSD), also Xenia is unofficial wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|64x64px]] |[[Wilber]] |[https://www.gimp.org GIMP] |} 6c5c14e50bbdfc5b6552b8642c2e68bffbf32ee8 0 1018 4329 4149 2025-11-23T15:07:09Z ByteSlayer 282 Updated latest Version wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:go.png|200px]] | caption = Go Logo | title = Go | releasestatus = Maintained | lastrelease = 1.25.4 | languages = [[Go]], originally written in [[C]] | developers = The Go Team; originally by RobPike, Ken Thompson, Robert Griesemer | website = [https://go.dev/ go.dev] }} 7f01d0471f461565368714bc5b1270c50bb208c1 0 1038 4331 4229 2025-12-02T11:36:30Z Alxhr0 265 Grammar fix wikitext text/x-wiki {{Guide Warning}} {{DistributionInfobox | title = Fedora Silverblue | image = [[File:Silverblue-logo.svg|Silverblue-logo.svg]] | caption = Fedora Silverblue Logo | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable Release | usagetype = Desktop | defaultdesktops = [[GNOME]] | architectures = x86_64, aarch64 | website = [https://fedoraproject.org/atomic-desktops/silverblue/ fedoraproject.org/atomic-desktops/silverblue] }} [[Category:Linux Distributions]] '''Fedora Silverblue''' is an atomic Linux distribution which provides users with a very stable base system. <ref>{{Cite|url=https://fedoraproject.org/atomic-desktops/silverblue|title=Fedora Silverblue homepage|author=The Fedora Project|accessdate=2025-10-15}}</ref> === Getting Software === While on non-atomic distributions one would use a package manager like [[DNF]] or [[APT]] to install packages, on distribution's like Fedora Silverblue it's recommended to use [[flatpak]] or use containers with [[toolbox]] and only fall back to [[rpm-ostree]] when absolutely necessary <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started|title=Getting Started|author=The Fedora Project|accessdate=2025-10-15}}</ref> === Read-only root filesystem === The root filesystem on Fedora Silverblue is read-only with some exceptions like /etc and /var User's home directory is located in /var/home because of /var not being read-only <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/technical-information/#filesystem-layout|title=Filesystem layout|author=The Fedora Project|accessdate=2025-10-15}}</ref> == Updates, Upgrades and rollbacks == Installing updates with Fedora Silverblue is easy and fast. It has a special rollback feature, in case anything goes wrong. Additionally, one can choose to have multiple versions of the operating system installed at all times, and can choose which one to boot into. === Updating Fedora Silverblue === OS updates are fully integrated into the desktop; the user will be automatically notified when an update is available. The standard behavior is to automatically download the update (this can be changed from the update preferences in Software). Once an update is ready, it is just a matter of rebooting to start using the new version. There is no waiting for the update to be installed during this reboot. If one prefers, it is also possible to update using the command line. To do this, run: <code>$ rpm-ostree upgrade</code> <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#updating|title=Updating the system|author=The Fedora Project|accessdate=2025-10-15}}</ref> === Upgrading between major versions === Upgrading between major versions (such as from Fedora 41 to Fedora 42) can be completed using the GNOME Software application. Alternatively, Fedora Silverblue can be upgraded between major versions using the <code>rpm-ostree</code> command. '''⚠️ Warning''' Skipping major releases is currently untested and is not supported. First, make sure that the system is on the latest update for the current version: <code>$ rpm-ostree upgrade</code> Reboot the system if needed. Then, verify that the branch for the next major version is available. To print all available branches for Fedora Silverblue use this command: <code>$ ostree remote refs fedora | grep silverblue | grep $(uname -m)</code> After one has verified the name of your branch, the user is ready to proceed. For example, to upgrade to Fedora Silverblue 42, the command is: <code>$ rpm-ostree rebase fedora:fedora/42/x86_64/silverblue</code> <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#upgrading|title=Upgrading to a new version|author=The Fedora Project|accessdate=2025-10-15}}</ref> ==== Rebasing to another Atomic Desktop ==== The user can rebase to another image like [[Fedora Kinoite]] which is like Silverblue, but uses [[KDE Plasma]] instead of [[GNOME]] or [[Fedora Sway Atomic]] which uses [[Sway]] instead When rebasing all flatpaks and user data are untouched It's important to pin the current deployment, so that one doesn't accidentally lose it. To pin it one can run <code>$ sudo ostree admin pin 0 <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#rebasing|title=Rebasing to another image|author=The Fedora Project|accessdate=2025-10-15}}</ref></code> To rebase to [[Fedora Kinoite]] for example one can run <code>$ rpm-ostree rebase fedora:fedora/<fedora version>/x86_64/kinoite </code><ref>{{Cite|url=https://communityblog.fedoraproject.org/rebasing-fedora-silverblue-to-kinoite/|title=Rebasing to Kinoite from Silverblue|author=Zlopez|accessdate=2025-10-15}}</ref> ==== Rolling back ==== Fedora Silverblue keeps a record of the previous OS version, which can be switched to instead of the latest version. While this shouldn’t usually be necessary, it can be helpful if there is a problem with an update or an upgrade (rollbacks work the same way for both), as well as for development purposes. There are two ways to roll back to the previous version: 1. Temporary rollbacks: to temporarily roll back to a previous version, simply reboot and select the previous version from the boot menu (often known as the grub menu). 2. Permanent rollbacks: to permanently switch back to the previous deployment, use the <code>$ rpm-ostree rollback</code> command. <ref>{{Cite|url=https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#rolling-back|title=Rolling back|author=The Fedora Project|accessdate=2025-10-15}}</ref> == References == <references /> f9c9a791cfbc50317697e8fb010e95f708e26dae 6 1063 4333 2025-12-10T01:15:16Z 0xFF 273 The current (as of 09 Dec 2025) Manjaro logo. Replaces the older, greener logo. wikitext text/x-wiki == Summary == The current (as of 09 Dec 2025) Manjaro logo. Replaces the older, greener logo. == Licensing == {{Unknown_copyright}} e9d9afd6baa369dbe844dea69c719f869c386388 0 626 4334 4079 2025-12-10T01:18:24Z 0xFF 273 Add an infobox wikitext text/x-wiki {{DistributionInfobox | title = EndeavourOS | image = [[File:Manjaro logo new.svg|Thumb]] | caption = The Manjaro logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]], [[Pamac]] | defaultdesktops = [[KDE Plasma]], [[Xfce]], [[GNOME]] | usagetype = Desktop | architectures = x86_64, Arm64 | website = [https://manjaro.org manjaro.org] }} Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>[https://manjaro.org/ Manjaro – The Linux for People and Organizations], Manjaro, 2025-08-09 (Accessed: 2025-08-09)</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">[https://distrowatch.com/table.php?distribution=manjaro DistroWatch.com: Manjaro Linux], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" Rolling Release * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>[https://wiki.manjaro.org/index.php/Pamac Pamac - Manjaro], Manjaro, 2023-03-09 (Accessed: 2025-08-09)</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME|GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>[https://en.wikipedia.org/wiki/Manjaro Manjaro], Wikipedia contributors, 2025-07-01 (Accessed: 2025-08-09)</ref><ref>[https://www.ubuntumint.com/manjaro-linux-history/ The History of Manjaro Linux Distribution], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>[https://www.geeksforgeeks.org/how-to-install-manjaro-linux/ How to Install Manjaro Linux?], GeeksforGeeks, 2023-12-22 (Accessed: 2025-08-09)</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch's base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch's, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>[https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/ How to Enable Arch User Repository (AUR) in Manjaro Linux], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro's custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch's upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>[https://itsfoss.com/manjaro-vs-arch-linux/ Manjaro vs Arch: What's the Difference? Which one to Use?], Dimitrios, Abhishek Prakash, 2023-09-13 (Accessed: 2025-08-09)</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>[https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. == References == c8132c3a223254d436bbc1c366c62fd974aa530e 0 891 4335 3796 2025-12-10T01:26:27Z 0xFF 273 Add infobox wikitext text/x-wiki {{DistributionInfobox | title = SteamOS | image = [[File:SteamOS wordmark.svg|Thumb]] | caption = The SteamOS wordmark | releasestatus = Maintained | packagemanager = [[Pacman]] | releasemodel = Stable | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Handheld | architectures = x86_64, Arm64 (in development) | website = [https://store.steampowered.com/steamos store.steampowered.com/steamos] }} SteamOS is an Immutable [[Arch Linux|Arch]]-based Linux Distribution produced by [[wikipedia:Valve_Corporation|Valve]] for it's use on proprietary hardware such as the [[wikipedia:Steam_Deck|Steam Deck.]] SteamOS focuses mainly on the user gaming experience by offering easy-access to Steam services such as the game library, Steam store and more. 300a3e4632b255f8bcd85586d3acc1d0c00b1b3a 0 310 4336 4134 2025-12-10T01:30:35Z 0xFF 273 Grammar fix, switch `typically on November` to `typically in November` wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Alpine Linux | image = [[File:alpinelinux-logo.svg|thumb]] | releasestatus = Maintained | releasemodel = Point or Rolling | packagemanager = [[apk]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[MATE]], [[LXQt]] | usagetype = Container, Embedded, Server, Desktop | architectures = amd64, aarch64, armel, armhf, i686, ppc64le, s390x, loongarch64 | website = [https://www.alpinelinux.org/ alpinelinux.org] }} Alpine Linux is a lightweight Linux distribution that aims to be "small", "simple" and "secure".<ref name=":0">[https://alpinelinux.org/about/ about | Alpine Linux], Alpine Linux Development Team, 2025-02-14 (Accessed: 2025-08-09)</ref> It is one of the few distributions that do not use the GNU C Library or GNU coreutils by default. Alpine, by default, follows a point release update model while its edge repositories follow a rolling release model. Twice a year, typically in November and May, a new stable version is branched from edge and released.<ref>[https://alpinelinux.org/releases/ Alpine release branches | Alpine Linux], Alpine Linux Development Team, 2025-07-15 (Accessed: 2025-08-09)</ref> == Features == Alpine's main feature is its small size. Its minimal system requirements and ease of deployability makes it suitable for use in containers, embedded systems and other systems with very limited resources. All user-space binaries in Alpine are compiled as position-independent executables with stack-smashing protection for security reasons.<ref name=":0" /> Alpine comes preinstalled with configuration scripts which allow quick configuration and installation of the system.<ref>[[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts] <span style="color:#fc493b">[https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts#setup-alpine https://wiki.alpinelinux.org/wiki/Alpine_setup_scripts] <sup>🍣DEAD?]</ref> Alpine also offers a web-server based configuration tool named the Alpine Configuration Framework (ACF).<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Configuration_Framework_Design Alpine Configuration Framework Design - Alpine Linux], Alpine Linux Wiki, 2025-03-10 (Accessed: 2025-08-09)</ref> Alpine offers a "diskless installation"<ref>[https://wiki.alpinelinux.org/wiki/Installation#Installation_Overview Installation - Alpine Linux], Alpine Linux Wiki, 2025-07-30 (Accessed: 2025-08-09)</ref>, allowing it to be installed to and be used from RAM. == Differences from other Linux Distributions == * Alpine uses musl as its standard C library. This compromises its support for some programs such as Electron based applications<ref>[https://wiki.alpinelinux.org/wiki/APKBUILD_examples:JavaScript APKBUILD examples:JavaScript - Alpine Linux], Alpine Linux Wiki, 2023-05-13 (Accessed: 2025-08-09)</ref> and the NVIDIA drivers.<ref>[https://wiki.alpinelinux.org/wiki/NVIDIA NVIDIA - Alpine Linux], Alpine Linux Wiki, 2025-05-09 (Accessed: 2025-08-09)</ref> * Alpine by default lacks the standard base utilities that other distributions come with such as GNU bash, coreutils, findutils, pciutils, usbutils, util-linux, udev. Instead of these, their BusyBox implementations are used. This is what makes Alpine so small in size, yet this also causes compatibility issues with many programs and scripts as their BusyBox implementations lack many features of their counterparts<ref>[https://wiki.alpinelinux.org/wiki/How_to_get_regular_stuff_working How to get regular stuff working - Alpine Linux], Alpine Linux Wiki, 2025-07-20 (Accessed: 2025-08-09)</ref>. To solve these compatibility issues, the user can install the standard version of these programs as they wish. * Alpine does not use systemd. Instead, it uses BusyBox for its init process and OpenRC for service management.<ref>[https://wiki.alpinelinux.org/wiki/OpenRC OpenRC - Alpine Linux], Alpine Linux Wiki, 2025-08-08 (Accessed: 2025-08-09)</ref> * Alpine uses its own package manager, the "Alpine Package Keeper" (apk).<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper Alpine Package Keeper - Alpine Linux], Alpine Linux Wiki, 2025-05-25 (Accessed: 2025-08-09)</ref> * Alpine uses the LTS branch of the Linux kernel by default.<ref>[https://github.com/alpinelinux/alpine-conf/blob/55ec2cf0504195ee60f68b21a29607302f8a15d0/setup-disk.in#L1489 alpine-conf/setup-disk.in at 55ec2cf0504195ee60f68b21a29607302f8a15d0 · alpinelinux/alpine-conf · GitHub], ncopa, 2025-07-15 (Accessed: 2025-08-09)</ref> == References == 8ed5d4aba4f59922d4499ebff48b6d15bb96d20f 0 769 4337 4243 2025-12-10T01:33:13Z 0xFF 273 Update capitalization to match the rest of the page and remove duplicated parens wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| [[C]] || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | [[Sway]] || None || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || None (Tiling) || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[river]]<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref> || None (Tiling) || [[zig]]|| Lightweight and minimal tiling compositor focused on simplicity. |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || None (3D effects) || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || None (Kiosk) || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- | [[Niri]] || None (Scrolling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |[[COSMIC]] |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || None (Tiling) || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 31b7e49145128fb766e9e015ee832dad1008c7a6 0 1064 4338 2025-12-19T13:54:18Z R4ven 304 I have explained the cultural and technical aspects of hacking, its evolution into a professional cybersecurity discipline, and the importance of legality, ethics, and authorization in modern practice. wikitext text/x-wiki '''Hacking''' is the practice of exploring, understanding, and manipulating computer [[systems]], [[networks]], or [[:Category:Software|software]] beyond their intended use. The term originally described curiosity-driven experimentation by skilled programmers but has since broadened to encompass a wide range of activities with differing intentions and legal implications. In modern usage, hacking generally refers to the identification and exploitation of weaknesses in digital systems. These weaknesses may exist in software code, hardware, network configurations, or human behavior. Depending on intent and authorization, hacking can be classified into distinct categories: * '''Ethical (or white-hat) hacking''' involves authorized testing of systems to identify vulnerabilities so they can be fixed, thereby improving security. * '''Malicious (or black-hat) hacking''' involves unauthorized access or damage to systems for personal gain, disruption, or data theft and is illegal in most jurisdictions. * '''Gray-hat hacking''' falls between these extremes, where individuals may access systems without permission but without clear malicious intent. Hacking techniques can include activities such as vulnerability research, reverse engineering, penetration testing, and social engineering. While some forms of hacking are essential to cybersecurity, digital forensics, and system hardening, unauthorized hacking is widely considered a cybercrime. Today, the term “hacking” is used both positively and negatively, depending on context, ranging from innovative problem-solving and security research to illegal intrusion and cyberattacks. Hacking also represents a broader technical culture centered on problem-solving, experimentation, and a deep understanding of how systems work. In this sense, hacking is not limited to security breaches but includes modifying, optimizing, or repurposing technology in ways not originally intended by its designers. From a technical perspective, hacking often involves analyzing system architecture, source code, communication protocols, and operating system behavior to understand how components interact. This knowledge can be applied to improve performance, enhance security, uncover design flaws, or demonstrate theoretical weaknesses. Many advances in [[cybersecurity]], privacy protection, and software reliability originate from this type of research. Legally and ethically, the defining factor in hacking is '''authorization'''. Accessing or testing a system with the explicit permission of its owner is generally lawful and forms the basis of professional penetration testing and security auditing. Accessing systems without consent, regardless of skill level, typically violates computer misuse laws and organizational policies. The hacking community commonly categorizes participants by role rather than skill alone. These roles include security researchers, penetration testers, exploit developers, reverse engineers, and incident responders. While media portrayals often associate hacking exclusively with crime, in practice it is a foundational discipline within modern information security. As digital infrastructure becomes more complex and widespread, hacking—particularly in its ethical and defensive forms—plays a critical role in identifying risks, protecting data, and maintaining the integrity of computer systems worldwide. f8b9709d761a11f383ff514ef4031ce78683df2f 4339 4338 2025-12-19T14:15:21Z R4ven 304 i have added tha brief history and the evolution of Hacking. Some key dates and integrated links. wikitext text/x-wiki '''Hacking''' is the practice of exploring, understanding, and manipulating computer systems, networks, or [[:Category:Software|software]] beyond their intended use. The term originally described curiosity-driven experimentation by skilled programmers but has since broadened to encompass a wide range of activities with differing intentions and legal implications. In modern usage, hacking generally refers to the identification and exploitation of weaknesses in digital systems. These weaknesses may exist in software code, hardware, network configurations, or human behavior. Depending on intent and authorization, hacking can be classified into distinct categories: * '''Ethical (or white-hat) hacking''' involves authorized testing of systems to identify vulnerabilities so they can be fixed, thereby improving security. * '''Malicious (or black-hat) hacking''' involves unauthorized access or damage to systems for personal gain, disruption, or data theft and is illegal in most jurisdictions. * '''Gray-hat hacking''' falls between these extremes, where individuals may access systems without permission but without clear malicious intent. Hacking techniques can include activities such as vulnerability research, reverse engineering, [[penetration testing]], and social engineering. While some forms of hacking are essential to cybersecurity, digital forensics, and system hardening, unauthorized hacking is widely considered a cybercrime. Today, the term “hacking” is used both positively and negatively, depending on context, ranging from innovative problem-solving and security research to illegal intrusion and cyberattacks. Hacking also represents a broader technical culture centered on problem-solving, experimentation, and a deep understanding of how systems work. In this sense, hacking is not limited to security breaches but includes modifying, optimizing, or repurposing technology in ways not originally intended by its designers. From a technical perspective, hacking often involves analyzing system architecture, source code, communication protocols, and operating system behavior to understand how components interact. This knowledge can be applied to improve performance, enhance security, uncover design flaws, or demonstrate theoretical weaknesses. Many advances in [[cybersecurity]], privacy protection, and software reliability originate from this type of research. Legally and ethically, the defining factor in hacking is '''authorization'''. Accessing or testing a system with the explicit permission of its owner is generally lawful and forms the basis of professional penetration testing and security auditing. Accessing systems without consent, regardless of skill level, typically violates computer misuse laws and organizational policies. The hacking community commonly categorizes participants by role rather than skill alone. These roles include security researchers, penetration testers, exploit developers, reverse engineers, and incident responders. While media portrayals often associate hacking exclusively with crime, in practice it is a foundational discipline within modern information security. As digital infrastructure becomes more complex and widespread, hacking—particularly in its ethical and defensive forms—plays a critical role in identifying risks, protecting data, and maintaining the integrity of computer systems worldwide. = History of Hacking and Its Evolution = === Early Foundations (1950s–1960s) === * '''1950s''' – The term ''“hack”'' emerges at '''MIT''', referring to clever technical solutions and playful experimentation with systems. * '''1961''' – MIT students gain unauthorized access to computer time on mainframes, often cited as the '''earliest form of computer hacking'''. * '''1969''' – '''[[ARPANET]]''' (precursor to the internet) is created, making networked systems—and network abuse—possible. === Phone Phreaking Era (1970s) === * '''1971''' – '''John Draper (“Captain Crunch”)''' discovers that a toy whistle emitting 2600 Hz can control telephone systems, marking one of the first well-documented exploits. * '''1970s''' – Phone phreaking communities emerge, influencing early computer hacking culture. * '''1975''' – Home computers (Altair 8800) appear, expanding access to computing. === Early Computer Intrusions (1980s) === * '''1983''' – The film ''WarGames'' popularizes hacking in public culture. * '''1983''' – The term '''“computer hacker”''' becomes widely known. * '''1986''' – The '''Computer Fraud and Abuse Act (CFAA)''' is enacted in the United States, formalizing computer crime laws. * '''1988''' – The '''Morris Worm''', created by Robert Tappan Morris, becomes the '''first major internet worm''', disrupting large parts of the early internet. === Internet Expansion (1990s) === * '''Early 1990s''' – Widespread internet access leads to an increase in system intrusions. * '''1995''' – Commercial websites become common; web hacking begins. * '''1998''' – The term '''“ethical hacking”''' starts gaining traction. * '''Late 1990s''' – Hacker groups and underground forums grow globally. === Professionalization (2000s) === * '''2000''' – Major distributed denial-of-service ([[DDoS]]) attacks hit Yahoo, eBay, and others. * '''2001''' – The '''Hacktivism''' concept gains visibility (politically motivated hacking). * '''2004''' – Bug bounty programs begin to appear. * '''2007''' – Smartphone platforms introduce new attack surfaces. === Modern Cybersecurity Era (2010s) === * '''2010''' – '''Stuxnet''' demonstrates state-level cyber weapons for the first time. * '''2013''' – Large-scale data breaches become common (hundreds of millions of records). * '''2015–2018''' – Bug bounties and penetration testing become standard industry practices. * '''Late 2010s''' – Nation-state hacking, ransomware, and supply-chain attacks rise sharply. === Present Day (2020s) === * '''2020''' – Supply-chain attacks (e.g., SolarWinds) redefine threat models. * '''2021–present''' – [[Ransomware]]-as-a-service and automated exploitation dominate cybercrime. * Hacking is now a '''formal cybersecurity discipline''', split between criminal activity and authorized defensive research. 9bf18222476f0c48d5c6ed1d23b2fa5fc72c9df5 4346 4339 2025-12-19T15:56:16Z R4ven 304 ive chanced the format of the article, also added "Significance" section. Cleaner and more understandable language is used wikitext text/x-wiki Hacking is the practice of exploring, analyzing, and manipulating computer systems, networks, or [[:Category:Software|software]] to understand their internal mechanisms, often beyond their intended or documented use. In modern contexts, hacking most commonly refers to the identification and exploitation of security vulnerabilities, though it also includes legitimate research, innovation, and system optimization. Authorization and intent are the primary factors distinguishing lawful hacking from criminal activity. ---- == Purpose == The purpose of hacking varies according to intent and authorization. In legitimate contexts, hacking is used to identify weaknesses, improve security, validate system resilience, and advance technical knowledge. In malicious contexts, it is used to gain unauthorized access, disrupt services, steal information, or exert control over systems. Regardless of intent, hacking relies on in-depth understanding of operating systems, networks, [[:Category:Software|software]] architecture, and human behavior. ---- == History == Hacking originated as a technical and academic culture before evolving into a security and legal concern. * '''1950s''' – The concept of a ''“hack”'' emerges in early computing communities, referring to clever or unconventional technical solutions. * '''1961''' – Students at MIT conduct unauthorized use of mainframe computing resources, often cited as the '''first recorded instance of computer hacking'''. * '''1962''' – J. C. R. Licklider proposes the concept of a globally interconnected computer network, influencing early hacker culture. * '''1969''' – [[ARPANET]] is established, enabling networked computing and creating new opportunities for system exploration and misuse. * '''Early 1970s''' – Phone phreaking emerges, demonstrating exploitation of telecommunications systems and shaping early hacker techniques. * '''1971''' – John Draper (“Captain Crunch”) exploits signaling tones in telephone systems, becoming a prominent figure in early hacking history. * '''Late 1970s''' – The spread of personal computing expands access to programmable systems. * '''1983''' – The film ''[[wikipedia:WarGames|WarGames]]'' popularizes hacking in public consciousness and introduces the concept of computer intrusion to a mass audience. * '''1986''' – The United States enacts the '''Computer Fraud and Abuse Act (CFAA)''', formalizing computer-related offenses. * '''1988''' – The '''Morris Worm''' disrupts large portions of the early internet, marking the first major network-based attack. * '''Early 1990s''' – Public internet access becomes widespread, leading to increased unauthorized intrusions. * '''Mid–Late 1990s''' – Hacker communities and underground forums expand globally; the distinction between ethical and malicious hacking begins to form. * '''Late 1990s''' – The term '''ethical hacking''' enters common usage. * '''2000''' – Large-scale distributed attacks against major websites demonstrate the potential impact of coordinated hacking. * '''2000s''' – Hacking becomes professionalized through [[penetration testing]], vulnerability research, and security consulting. * '''2010s''' – State-sponsored hacking, large-scale data breaches, and advanced persistent threats reshape global [[cybersecurity]]. * '''2020s–present''' – Hacking is a formally recognized [[cybersecurity]] discipline, governed by legal frameworks, standards, and professional methodologies. ---- == Types == Hacking is commonly categorized based on intent, authorization, and context: * '''Ethical (white-hat) hacking''' involves authorized security testing and research aimed at improving system defenses. * '''Malicious (black-hat) hacking''' consists of unauthorized access, exploitation, or damage for personal, financial, or strategic gain. * '''Gray-hat hacking''' involves unauthorized access without clear malicious intent, often raising legal and ethical ambiguity. * '''Hacktivism''' applies hacking techniques to promote political or ideological causes. These categories may overlap, and classification often depends on legal jurisdiction and authorization. ---- == Significance == Hacking has been central to the development of modern computing and [[cybersecurity]]. Many security mechanisms, defensive technologies, and industry standards exist as a direct response to hacking activity. While often associated with criminal behavior, hacking—when conducted ethically and legally—is a foundational practice in securing digital infrastructure, advancing computer science, and understanding technological risk. 3f140b96b785d24623bdc58745621e79e8570f0f 4348 4346 2025-12-19T16:52:02Z R4ven 304 Citations were added. wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/topic/hacker|title=Hacker|author=Encyclopædia Britannica|year=2024|accessdate=Retrieved on December 19, 2025}}</ref><ref>{{Cite|url=http://www.catb.org/~esr/jargon/html/H/hack.html|title=Hack|author=Eric S. Raymond|year=2003|accessdate=Retrieved on December 19, 2025}}</ref>Hacking is the practice of exploring, analyzing, and manipulating computer systems, networks, or [[:Category:Software|software]] to understand their internal mechanisms, often beyond their intended or documented use. In modern contexts, hacking most commonly refers to the identification and exploitation of security vulnerabilities, though it also includes legitimate research, innovation, and system optimization. Authorization and intent are the primary factors distinguishing lawful hacking from criminal activity. ---- == Purpose == <ref>{{Cite|url=https://www.cl.cam.ac.uk/archive/rja14/book.html|title=Security Engineering|author=Ross J. Anderson|year=2020|accessdate=Retrieved on December 19, 2025}}</ref>The purpose of hacking varies according to intent and authorization. In legitimate contexts, hacking is used to identify weaknesses, improve security, validate system resilience, and advance technical knowledge. In malicious contexts, it is used to gain unauthorized access, disrupt services, steal information, or exert control over systems. Regardless of intent, hacking relies on in-depth understanding of operating systems, networks, [[:Category:Software|software]] architecture, and human behavior. ---- == History == <ref>{{Cite|url=https://www.goodreads.com/book/show/56829.Hackers|title=Steven Levy – Hackers: Heroes of the Computer Revolution|author=Steven Levy|year=2001|accessdate=Retrieved on December 19, 2025}}</ref>Hacking originated as a technical and academic culture before evolving into a security and legal concern. * '''1950s''' – The concept of a ''“hack”'' emerges in early computing communities, referring to clever or unconventional technical solutions. * '''1961''' – Students at MIT conduct unauthorized use of mainframe computing resources, often cited as the '''first recorded instance of computer hacking'''. * <ref>{{Cite|url=https://groups.csail.mit.edu/medg/people/psz/Licklider.html|title=Man-Computer Symbiosis|author=J. C. R. Licklider|year=1962|accessdate=Retrieved on December 19, 2025}}</ref>'''1962''' – J. C. R. Licklider proposes the concept of a globally interconnected computer network, influencing early hacker culture. * '''1969''' – [[ARPANET]] is established, enabling networked computing and creating new opportunities for system exploration and misuse. * '''Early 1970s''' – Phone phreaking emerges, demonstrating exploitation of telecommunications systems and shaping early hacker techniques. * '''1971''' – John Draper (“Captain Crunch”) exploits signaling tones in telephone systems, becoming a prominent figure in early hacking history. * '''Late 1970s''' – The spread of personal computing expands access to programmable systems. * '''1983''' – The film ''[[wikipedia:WarGames|WarGames]]'' popularizes hacking in public consciousness and introduces the concept of computer intrusion to a mass audience. * '''1986''' – The United States enacts the '''Computer Fraud and Abuse Act (CFAA)''', formalizing computer-related offenses. * '''1988''' – The '''Morris Worm''' disrupts large portions of the early internet, marking the first major network-based attack. * <ref>{{Cite|url=https://www.internetsociety.org/internet/history-internet/|title=A Short History of the Internet|author=Internet Society|year=2019|accessdate=Retrieved on December 19, 2025}}</ref>'''Early 1990s''' – Public internet access becomes widespread, leading to increased unauthorized intrusions. * '''Mid–Late 1990s''' – Hacker communities and underground forums expand globally; the distinction between ethical and malicious hacking begins to form. * '''Late 1990s''' – The term '''ethical hacking''' enters common usage. * '''2000''' – Large-scale distributed attacks against major websites demonstrate the potential impact of coordinated hacking. * '''2000s''' – Hacking becomes professionalized through [[penetration testing]], vulnerability research, and security consulting. * '''2010s''' – State-sponsored hacking, large-scale data breaches, and advanced persistent threats reshape global [[cybersecurity]]. * '''2020s–present''' – Hacking is a formally recognized [[cybersecurity]] discipline, governed by legal frameworks, standards, and professional methodologies. ---- == Types == <ref>{{Cite|url=https://www.britannica.com/topic/hacker|title=Hacker|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>Hacking is commonly categorized based on intent, authorization, and context: * '''Ethical (white-hat) hacking''' involves authorized security testing and research aimed at improving system defenses. * '''Malicious (black-hat) hacking''' consists of unauthorized access, exploitation, or damage for personal, financial, or strategic gain. * '''Gray-hat hacking''' involves unauthorized access without clear malicious intent, often raising legal and ethical ambiguity. * '''Hacktivism''' applies hacking techniques to promote political or ideological causes. These categories may overlap, and classification often depends on legal jurisdiction and authorization. ---- == Significance == <ref>{{Cite|url=https://csrc.nist.gov/|title=Significance of Hacking|author=National Institute of Standards and Technology (NIST)|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>Hacking has been central to the development of modern computing and [[cybersecurity]]. Many security mechanisms, defensive technologies, and industry standards exist as a direct response to hacking activity. While often associated with criminal behavior, hacking—when conducted ethically and legally—is a foundational practice in securing digital infrastructure, advancing computer science, and understanding technological risk. 36ba1fad556795b99c4bfca511405defa9bd8379 0 1065 4340 2025-12-19T14:21:44Z R4ven 304 i have explained what "Penetration testing" is, its purpose, History and Types in detail. wikitext text/x-wiki Penetration testing is a formal and authorized [[cybersecurity]] assessment methodology used to evaluate the security of computer systems, networks, applications, or infrastructures by simulating realistic attack scenarios. It involves systematically identifying, validating, and exploiting security vulnerabilities under controlled conditions to assess how an attacker could compromise confidentiality, integrity, or availability. Unlike automated vulnerability scanning, penetration testing includes human analysis, decision-making, and contextual understanding of system behavior, making it a deeper and more accurate measure of real-world security risk. ---- == Purpose == The primary purpose of penetration testing is to proactively identify and confirm security weaknesses before they are exploited by malicious actors. It enables organizations to understand their actual attack surface, evaluate the effectiveness of existing security controls, and prioritize remediation based on real exploitability rather than theoretical risk. Penetration testing also supports regulatory compliance, improves incident preparedness, and provides measurable insight into organizational security posture by demonstrating the potential business impact of successful attacks. ---- == History == Penetration testing developed alongside the expansion of networked computing and the public internet. * '''1960s–1970s''': Early security assessments were conducted in military and academic environments, primarily focused on access control and system isolation. * '''1980s''': Government-funded research programs in the United States formally introduced controlled attack simulations to evaluate computer security, particularly within defense systems. * '''1990s''': With the rapid growth of the internet and commercial networks, penetration testing began to emerge as a recognized practice for evaluating enterprise security. * '''Late 1990s''': The term ''penetration testing'' became widely adopted, and structured methodologies began to form. * '''2000s''': Penetration testing became a professional service, integrated into corporate security programs and compliance frameworks. * '''2010s–present''': Penetration testing evolved into a standardized cybersecurity discipline, incorporating cloud systems, mobile platforms, and complex infrastructures, and is now a core component of modern risk management strategies. ---- == Types == Penetration testing is commonly categorized based on the level of system knowledge provided to the tester: * '''Black-box testing''' involves no prior knowledge of the target system, simulating an external attacker with minimal information and emphasizing reconnaissance and discovery. * '''Gray-box testing''' provides partial knowledge or limited credentials, representing an insider threat or a compromised user account. * '''White-box testing''' grants full access to system architecture, source code, and documentation, allowing for comprehensive and in-depth security analysis. Penetration testing may also be classified by target scope, such as network penetration testing, web application testing, mobile application testing, cloud security testing, wireless testing, or internal infrastructure testing. 90121373bb847790170b038bc93d14ca51463aa0 4353 4340 2025-12-19T17:11:16Z R4ven 304 Citations were added. wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/penetration-testing|title=Penetration Testing|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>Penetration testing is a formal and authorized [[cybersecurity]] assessment methodology used to evaluate the security of computer systems, networks, applications, or infrastructures by simulating realistic attack scenarios. It involves systematically identifying, validating, and exploiting security vulnerabilities under controlled conditions to assess how an attacker could compromise confidentiality, integrity, or availability. Unlike automated vulnerability scanning, penetration testing includes human analysis, decision-making, and contextual understanding of system behavior, making it a deeper and more accurate measure of real-world security risk. ---- == Purpose == <ref>{{Cite|url=https://www.ibm.com/topics/penetration-testing|title=Penetration Testing: Assessing Security Vulnerabilities|author=IBM|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of penetration testing is to proactively identify and confirm security weaknesses before they are exploited by malicious actors. It enables organizations to understand their actual attack surface, evaluate the effectiveness of existing security controls, and prioritize remediation based on real exploitability rather than theoretical risk. Penetration testing also supports regulatory compliance, improves incident preparedness, and provides measurable insight into organizational security posture by demonstrating the potential business impact of successful attacks. ---- == History == <ref>{{Cite|url=https://www.sans.org/white-papers/1289/|title=A Short History of Penetration Testing|author=SANS Institute|year=2005|accessdate=Retrieved on December 19, 2025}}</ref>Penetration testing developed alongside the expansion of networked computing and the public internet. * '''1960s–1970s''': Early security assessments were conducted in military and academic environments, primarily focused on access control and system isolation. * '''1980s''': Government-funded research programs in the United States formally introduced controlled attack simulations to evaluate computer security, particularly within defense systems. * '''1990s''': With the rapid growth of the internet and commercial networks, penetration testing began to emerge as a recognized practice for evaluating enterprise security. * '''Late 1990s''': The term ''penetration testing'' became widely adopted, and structured methodologies began to form. * '''2000s''': Penetration testing became a professional service, integrated into corporate security programs and compliance frameworks. * '''2010s–present''': Penetration testing evolved into a standardized cybersecurity discipline, incorporating cloud systems, mobile platforms, and complex infrastructures, and is now a core component of modern risk management strategies. ---- == Types == <ref>{{Cite|url=https://owasp.org/www-project-web-security-testing-guide/|title=Penetration Testing Methodologies and Types|author=OWASP Foundation|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>Penetration testing is commonly categorized based on the level of system knowledge provided to the tester: * '''Black-box testing''' involves no prior knowledge of the target system, simulating an external attacker with minimal information and emphasizing reconnaissance and discovery. * '''Gray-box testing''' provides partial knowledge or limited credentials, representing an insider threat or a compromised user account. * '''White-box testing''' grants full access to system architecture, source code, and documentation, allowing for comprehensive and in-depth security analysis. Penetration testing may also be classified by target scope, such as network penetration testing, web application testing, mobile application testing, cloud security testing, wireless testing, or internal infrastructure testing. 832d6b2470db54c1a760e4f5512f773763647a23 0 1066 4341 2025-12-19T14:25:50Z R4ven 304 i have explained what "Cybersecurity" is, its purpose, History and Types in detail. wikitext text/x-wiki Cybersecurity is the discipline concerned with the protection of computer systems, networks, applications, and digital data from unauthorized access, disruption, manipulation, or destruction. It encompasses technical, organizational, and procedural measures designed to ensure the confidentiality, integrity, and availability of information systems. Cybersecurity addresses threats originating from malicious actors, system failures, human error, and advanced persistent threats, and is a foundational component of modern digital infrastructure across government, industry, and society. ---- == Purpose == The primary purpose of cybersecurity is to reduce risk by preventing, detecting, and responding to cyber threats that could compromise digital assets or critical services. It aims to protect sensitive information, maintain system reliability, support business continuity, and preserve trust in digital technologies. Cybersecurity also enables compliance with legal and regulatory requirements and supports national security by safeguarding critical infrastructure and information systems. ---- == History == Cybersecurity evolved in response to the increasing dependence on computerized systems and interconnected networks. * '''1960s–1970s''': Early computer security concepts emerged in military and academic environments, focusing on access control and system isolation. * '''1971''': The first known self-replicating program, ''Creeper'', demonstrated early security risks in networked systems. * '''1988''': The ''Morris Worm'' disrupted large portions of the early internet, highlighting the need for coordinated security practices. * '''1990s''': The commercialization of the internet led to widespread security incidents, prompting the development of firewalls, antivirus software, and intrusion detection systems. * '''2000s''': Cybersecurity became a formal professional field, with the introduction of standards, frameworks, and dedicated security roles. * '''2010s–present''': Cybersecurity expanded to address cloud computing, mobile platforms, large-scale data breaches, ransomware, and nation-state cyber operations, becoming a critical element of global digital resilience. ---- == Types == Cybersecurity is a multidisciplinary field encompassing several specialized domains: * '''Network security''' focuses on protecting communication networks and preventing unauthorized access or attacks. * '''Application security''' addresses vulnerabilities in [[:Category:Software|software]] throughout its development and deployment lifecycle. * '''Information security''' concentrates on protecting data in all forms, whether digital or physical. * '''Cloud security''' deals with securing cloud-based infrastructure, services, and data. * '''Operational security''' involves policies and procedures governing the handling and protection of sensitive information. * '''Incident response and digital forensics''' focus on detecting, analyzing, and recovering from security incidents. faa0e9ffc6b6c09ee54c85d505d85f590f2efe0b 4349 4341 2025-12-19T16:57:02Z R4ven 304 Citations were added. wikitext text/x-wiki <ref>{{Cite|url=https://www.nist.gov/cyberframework|title=Cybersecurity|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>Cybersecurity is the discipline concerned with the protection of computer systems, networks, applications, and digital data from unauthorized access, disruption, manipulation, or destruction. It encompasses technical, organizational, and procedural measures designed to ensure the confidentiality, integrity, and availability of information systems. Cybersecurity addresses threats originating from malicious actors, system failures, human error, and advanced persistent threats, and is a foundational component of modern digital infrastructure across government, industry, and society. ---- == Purpose == <ref>{{Cite|url=https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.04162018.pdf|title=Cybersecurity Framework|author=National Institute of Standards and Technology (NIST)|year=2018|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of cybersecurity is to reduce risk by preventing, detecting, and responding to cyber threats that could compromise digital assets or critical services. It aims to protect sensitive information, maintain system reliability, support business continuity, and preserve trust in digital technologies. Cybersecurity also enables compliance with legal and regulatory requirements and supports national security by safeguarding critical infrastructure and information systems. ---- == History == <ref>{{Cite|url=https://groups.csail.mit.edu/medg/people/psz/Licklider.html|title=Man-Computer Symbiosis|author=J. C. R. Licklider|year=1960|accessdate=Retrieved on December 19, 2025}}</ref>Cybersecurity evolved in response to the increasing dependence on computerized systems and interconnected networks. * '''1960s–1970s''': Early computer security concepts emerged in military and academic environments, focusing on access control and system isolation. * '''1971''': The first known self-replicating program, ''Creeper'', demonstrated early security risks in networked systems. * '''1988''': The ''Morris Worm'' disrupted large portions of the early internet, highlighting the need for coordinated security practices. * '''1990s''': The commercialization of the internet led to widespread security incidents, prompting the development of firewalls, antivirus software, and intrusion detection systems. * '''2000s''': Cybersecurity became a formal professional field, with the introduction of standards, frameworks, and dedicated security roles. * '''2010s–present''': Cybersecurity expanded to address cloud computing, mobile platforms, large-scale data breaches, ransomware, and nation-state cyber operations, becoming a critical element of global digital resilience. ---- == Types == <ref>{{Cite|url=https://www.cisa.gov/topics/cybersecurity-best-practices|title=What Is Cybersecurity? Domains and Types|author=Cybersecurity and Infrastructure Security Agency (CISA)|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>Cybersecurity is a multidisciplinary field encompassing several specialized domains: * '''Network security''' focuses on protecting communication networks and preventing unauthorized access or attacks. * '''Application security''' addresses vulnerabilities in [[:Category:Software|software]] throughout its development and deployment lifecycle. * '''Information security''' concentrates on protecting data in all forms, whether digital or physical. * '''Cloud security''' deals with securing cloud-based infrastructure, services, and data. * '''Operational security''' involves policies and procedures governing the handling and protection of sensitive information. * '''Incident response and digital forensics''' focus on detecting, analyzing, and recovering from security incidents. 62284e5f55ca482adf195199e9ec3d64b31305e0 0 1067 4342 2025-12-19T14:28:15Z R4ven 304 i have explained what "DDoS" is, its purpose, History and Types in detail. wikitext text/x-wiki A Distributed Denial-of-Service (DDoS) attack is a cyberattack in which multiple compromised systems are used to overwhelm a target system, service, or network with excessive traffic or requests, rendering it unavailable to legitimate users. Unlike a single-source denial-of-service attack, DDoS attacks are distributed across many devices, often forming a botnet, which makes detection, mitigation, and attribution significantly more difficult. DDoS attacks primarily target the availability component of information security and can affect websites, online services, networks, and critical infrastructure. ---- == Purpose == The purpose of a DDoS attack is to disrupt normal operations by exhausting system resources such as bandwidth, processing power, or memory. Motivations behind DDoS attacks vary and may include financial extortion, political or ideological protest, competitive sabotage, retaliation, or strategic disruption. From a defensive and research perspective, understanding DDoS attacks is essential for designing resilient systems, improving network capacity planning, and implementing effective mitigation strategies to maintain service continuity. ---- == History == DDoS attacks evolved alongside the growth of networked systems and the public internet. * '''1970s–1980s''': Early denial-of-service concepts appeared in experimental network environments, primarily through resource exhaustion. * '''1996''': One of the first documented denial-of-service attacks targeted a major internet service provider, temporarily disrupting connectivity in parts of the internet. * '''1999''': The first large-scale DDoS tools emerged, enabling coordinated attacks from multiple compromised systems. * '''2000''': High-profile DDoS attacks temporarily disabled major websites, bringing global attention to the threat. * '''2010s''': Botnets leveraging Internet of Things (IoT) devices significantly increased the scale and power of DDoS attacks. * '''2020s–present''': DDoS attacks have become more frequent, automated, and capable of reaching unprecedented traffic volumes, targeting both commercial services and critical infrastructure. ---- == Types == DDoS attacks are commonly categorized based on the layer or resource they target: * '''Volumetric attacks''' aim to overwhelm network bandwidth using massive amounts of traffic. * '''Protocol attacks''' exploit weaknesses in network protocols to exhaust server or network device resources. * '''Application-layer attacks''' target specific applications or services, mimicking legitimate user behavior to evade detection. * '''Reflection and amplification attacks''' abuse third-party servers to multiply attack traffic toward a victim. These categories often overlap, and modern DDoS attacks frequently combine multiple techniques to maximize impact and bypass defensive measures. 2d25e7dd0d49065f0f6965bb93f9f785a2b6a859 4350 4342 2025-12-19T17:00:05Z R4ven 304 Citations were added. wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/distributed-denial-of-service-attack|title=Distributed denial-of-service attack (DDoS)|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>A Distributed Denial-of-Service (DDoS) attack is a cyberattack in which multiple compromised systems are used to overwhelm a target system, service, or network with excessive traffic or requests, rendering it unavailable to legitimate users. Unlike a single-source denial-of-service attack, DDoS attacks are distributed across many devices, often forming a botnet, which makes detection, mitigation, and attribution significantly more difficult. DDoS attacks primarily target the availability component of information security and can affect websites, online services, networks, and critical infrastructure. ---- == Purpose == <ref>{{Cite|url=https://www.cisa.gov/understanding-denial-service-attacks|title=Understanding Denial-of-Service Attacks|author=Cybersecurity and Infrastructure Security Agency (CISA|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>The purpose of a DDoS attack is to disrupt normal operations by exhausting system resources such as bandwidth, processing power, or memory. Motivations behind DDoS attacks vary and may include financial extortion, political or ideological protest, competitive sabotage, retaliation, or strategic disruption. From a defensive and research perspective, understanding DDoS attacks is essential for designing resilient systems, improving network capacity planning, and implementing effective mitigation strategies to maintain service continuity. ---- == History == <ref>{{Cite|url=https://www.us-cert.gov/ncas/tips/ST04-015|title=Smurf Attack|author=US-CERT|year=2004|accessdate=Retrieved on December 19, 2025}}</ref>DDoS attacks evolved alongside the growth of networked systems and the public internet. * '''1970s–1980s''': Early denial-of-service concepts appeared in experimental network environments, primarily through resource exhaustion. * '''1996''': One of the first documented denial-of-service attacks targeted a major internet service provider, temporarily disrupting connectivity in parts of the internet. * '''1999''': The first large-scale DDoS tools emerged, enabling coordinated attacks from multiple compromised systems. * '''2000''': High-profile DDoS attacks temporarily disabled major websites, bringing global attention to the threat. * '''2010s''': Botnets leveraging Internet of Things (IoT) devices significantly increased the scale and power of DDoS attacks. * '''2020s–present''': DDoS attacks have become more frequent, automated, and capable of reaching unprecedented traffic volumes, targeting both commercial services and critical infrastructure. ---- == Types == <ref>{{Cite|url=https://www.cloudflare.com/learning/ddos/ddos-attack-types/|title=DDoS Attack Types|author=Cloudflare|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>DDoS attacks are commonly categorized based on the layer or resource they target: * '''Volumetric attacks''' aim to overwhelm network bandwidth using massive amounts of traffic. * '''Protocol attacks''' exploit weaknesses in network protocols to exhaust server or network device resources. * '''Application-layer attacks''' target specific applications or services, mimicking legitimate user behavior to evade detection. * '''Reflection and amplification attacks''' abuse third-party servers to multiply attack traffic toward a victim. These categories often overlap, and modern DDoS attacks frequently combine multiple techniques to maximize impact and bypass defensive measures. 07eb01cee4240faaa895955cb22f22cd9f36f935 0 1068 4343 2025-12-19T14:31:03Z R4ven 304 i have explained what "Ransomware (RaaS)" is, its purpose, History and Types in detail. wikitext text/x-wiki Ransomware is a category of malicious software designed to deny access to computer systems or data by encrypting files or locking system functionality, followed by a demand for payment in exchange for restoration. Modern ransomware attacks often combine cryptographic techniques with data theft, threatening public disclosure if payment is not made. Ransomware primarily targets the availability and confidentiality of information and has become one of the most disruptive forms of [[Cybersecurity|cybercrime]] affecting individuals, organizations, and critical infrastructure. ---- == Purpose == The primary purpose of ransomware is financial extortion. Attackers seek to coerce victims into paying a ransom, commonly using digital currencies, by creating operational disruption, data loss, or reputational damage. In recent years, ransomware has also been used as a tool for economic sabotage and strategic disruption. From a defensive perspective, studying ransomware supports the development of stronger backup strategies, incident response planning, and resilience against data-driven attacks. ---- == History == Ransomware has evolved significantly over several decades. * '''1989''': The ''AIDS [[Trojan]]'' (also known as the PC Cyborg virus) is widely recognized as the first ransomware incident, distributed via physical media and demanding payment by mail. * '''2000s''': Early ransomware variants appeared online but were limited by weak encryption and low adoption. * '''2013''': The emergence of strong cryptographic ransomware marked a turning point, making file recovery without backups impractical. * '''2017''': Large-scale ransomware outbreaks demonstrated the global impact of automated ransomware attacks. * '''Late 2010s''': The rise of ''double extortion'' introduced data theft alongside encryption. * '''2020s–present''': Ransomware operations became highly organized, often operating under ''ransomware-as-a-service'' models and increasingly targeting large enterprises and critical infrastructure. ---- == Types == Ransomware can be classified based on behavior and operational model: * '''Crypto-ransomware''' encrypts files and demands payment for decryption. * '''Locker ransomware''' restricts access to systems without encrypting files. * '''Double-extortion ransomware''' combines encryption with data exfiltration and blackmail. * '''Ransomware-as-a-Service (RaaS)''' involves developers providing ransomware tools to affiliates in exchange for a share of profits. * '''Targeted ransomware''' focuses on specific organizations rather than indiscriminate mass distribution. These types are not mutually exclusive, and modern ransomware campaigns frequently employ multiple techniques simultaneously 81a70dd0321e027537b33909829a8a3fb17cc4c0 4352 4343 2025-12-19T17:08:37Z R4ven 304 Citations were added. wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/ransomware?|title=Ransomware – malware that holds systems or data hostage until a ransom is paid|author=Encyclopædia Britannica Editors|year=2025|accessdate=Retrieved on December 19, 2025}}</ref>Ransomware is a category of malicious software designed to deny access to computer systems or data by encrypting files or locking system functionality, followed by a demand for payment in exchange for restoration. Modern ransomware attacks often combine cryptographic techniques with data theft, threatening public disclosure if payment is not made. Ransomware primarily targets the availability and confidentiality of information and has become one of the most disruptive forms of [[Cybersecurity|cybercrime]] affecting individuals, organizations, and critical infrastructure. ---- == Purpose == <ref>{{Cite|url=https://ransomware.org/what-is-ransomware/?|title=What Is Ransomware?|author=Ransomware.org Editors|year=2025|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of ransomware is financial extortion. Attackers seek to coerce victims into paying a ransom, commonly using digital currencies, by creating operational disruption, data loss, or reputational damage. In recent years, ransomware has also been used as a tool for economic sabotage and strategic disruption. From a defensive perspective, studying ransomware supports the development of stronger backup strategies, incident response planning, and resilience against data-driven attacks. ---- == History == <ref>{{Cite|url=https://www.britannica.com/technology/ransomware?|title=Ransomware Origins and Evolution|author=Encyclopædia Britannica Editors|year=2025|accessdate=Retrieved on December 19, 2025}}</ref>Ransomware has evolved significantly over several decades. * '''1989''': The ''AIDS [[Trojan]]'' (also known as the PC Cyborg virus) is widely recognized as the first ransomware incident, distributed via physical media and demanding payment by mail. * '''2000s''': Early ransomware variants appeared online but were limited by weak encryption and low adoption. * '''2013''': The emergence of strong cryptographic ransomware marked a turning point, making file recovery without backups impractical. * '''2017''': Large-scale ransomware outbreaks demonstrated the global impact of automated ransomware attacks. * '''Late 2010s''': The rise of ''double extortion'' introduced data theft alongside encryption. * '''2020s–present''': Ransomware operations became highly organized, often operating under ''ransomware-as-a-service'' models and increasingly targeting large enterprises and critical infrastructure. ---- == Types == <ref>{{Cite|url=https://www.techtarget.com/searchsecurity/feature/4-types-of-ransomware-and-a-timeline-of-attack-examples?|title=8 Types of Ransomware|author=TechTarget SearchSecurity|year=2025|accessdate=Retrieved on December 19, 2025}}</ref>Ransomware can be classified based on behavior and operational model: * '''Crypto-ransomware''' encrypts files and demands payment for decryption. * '''Locker ransomware''' restricts access to systems without encrypting files. * '''Double-extortion ransomware''' combines encryption with data exfiltration and blackmail. * '''Ransomware-as-a-Service (RaaS)''' involves developers providing ransomware tools to affiliates in exchange for a share of profits. * '''Targeted ransomware''' focuses on specific organizations rather than indiscriminate mass distribution. These types are not mutually exclusive, and modern ransomware campaigns frequently employ multiple techniques simultaneously e386162b29845069063a6fb1b7dfd2a9d777640a 0 1069 4344 2025-12-19T14:33:16Z R4ven 304 i have explained what "ARPANET" is, its purpose, History and Types in detail. wikitext text/x-wiki ARPANET (Advanced Research Projects Agency Network) was the first large-scale packet-switching network and the direct predecessor of the modern internet. Developed under the [https://www.war.gov/ United States Department of Defense], ARPANET was designed to enable reliable communication between geographically distributed computers and research institutions. It introduced fundamental networking concepts, including packet switching, distributed routing, and host-to-host communication, which remain central to internet architecture today. ---- == Purpose == The primary purpose of ARPANET was to facilitate resource sharing and communication among researchers working on government-funded computing projects. It aimed to allow multiple institutions to access computing power, software, and data remotely while maintaining network resilience in the event of partial system failures. ARPANET also served as an experimental platform for testing new networking protocols and concepts, laying the groundwork for future global networking systems. ---- == History == ARPANET emerged during the [[wikipedia:Cold_War|Cold War]] as part of advanced research initiatives in computing and communications. * '''1962''': J. C. R. Licklider proposed the concept of an “Intergalactic Computer Network,” outlining the idea of interconnected computers. * '''1966''': ARPA formally initiated the ARPANET project. * '''1969''': The first ARPANET connection was established between UCLA and the Stanford Research Institute; the first message was transmitted. * '''1971''': Electronic mail (email) was introduced on ARPANET, rapidly becoming its most popular application. * '''1973''': International connections were added, expanding ARPANET beyond the United States. * '''1983''': ARPANET officially transitioned to the TCP/IP protocol suite, a defining moment in internet history. * '''1990''': ARPANET was formally decommissioned, having fulfilled its role as a foundational research network. ---- == Types == ARPANET itself was not divided into types in the modern sense, but it evolved through architectural and functional phases: * '''Early ARPANET''' focused on basic host-to-host communication using Interface Message Processors (IMPs). * '''Expanded ARPANET''' supported multiple applications such as email, file transfer, and remote login. * '''Post-TCP/IP ARPANET''' functioned as part of a larger internetwork, integrating seamlessly with other emerging networks. ---- == Significance == ARPANET is widely regarded as the technological foundation of the internet. Its development introduced core principles such as packet switching, decentralized networking, and standardized communication protocols. Many modern internet technologies, including email, routing protocols, and distributed systems, originated from ARPANET research. The project also fostered a collaborative research culture that directly influenced the evolution of networking, [[cybersecurity]], and computer science as academic disciplines. 08da9e3e0dccf8fe74e19c5bd58aeb85a6bdc143 4351 4344 2025-12-19T17:02:53Z R4ven 304 Citations were added. wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/topic/ARPANET|title=ARPANET|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>ARPANET (Advanced Research Projects Agency Network) was the first large-scale packet-switching network and the direct predecessor of the modern internet. Developed under the [https://www.war.gov/ United States Department of Defense], ARPANET was designed to enable reliable communication between geographically distributed computers and research institutions. It introduced fundamental networking concepts, including packet switching, distributed routing, and host-to-host communication, which remain central to internet architecture today. ---- == Purpose == <ref>{{Cite|url=https://www.rand.org/pubs/research_memoranda/RM3420.html|title=The ARPA Network|author=Paul Baran|year=1964|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of ARPANET was to facilitate resource sharing and communication among researchers working on government-funded computing projects. It aimed to allow multiple institutions to access computing power, software, and data remotely while maintaining network resilience in the event of partial system failures. ARPANET also served as an experimental platform for testing new networking protocols and concepts, laying the groundwork for future global networking systems. ---- == History == <ref>{{Cite|url=https://groups.csail.mit.edu/medg/people/psz/Licklider.html|title=Man-Computer Symbiosis|author=J. C. R. Licklider|year=1960|accessdate=Retrieved on December 19, 2025}}</ref>ARPANET emerged during the [[wikipedia:Cold_War|Cold War]] as part of advanced research initiatives in computing and communications. * '''1962''': J. C. R. Licklider proposed the concept of an “Intergalactic Computer Network,” outlining the idea of interconnected computers. * '''1966''': ARPA formally initiated the ARPANET project. * '''1969''': The first ARPANET connection was established between UCLA and the Stanford Research Institute; the first message was transmitted. * '''1971''': Electronic mail (email) was introduced on ARPANET, rapidly becoming its most popular application. * '''1973''': International connections were added, expanding ARPANET beyond the United States. * '''1983''': ARPANET officially transitioned to the TCP/IP protocol suite, a defining moment in internet history. * '''1990''': ARPANET was formally decommissioned, having fulfilled its role as a foundational research network. ---- == Types == ARPANET itself was not divided into types in the modern sense, but it evolved through architectural and functional phases: * '''Early ARPANET''' focused on basic host-to-host communication using Interface Message Processors (IMPs). * '''Expanded ARPANET''' supported multiple applications such as email, file transfer, and remote login. * '''Post-TCP/IP ARPANET''' functioned as part of a larger internetwork, integrating seamlessly with other emerging networks. ---- == Significance == ARPANET is widely regarded as the technological foundation of the internet. Its development introduced core principles such as packet switching, decentralized networking, and standardized communication protocols. Many modern internet technologies, including email, routing protocols, and distributed systems, originated from ARPANET research. The project also fostered a collaborative research culture that directly influenced the evolution of networking, [[cybersecurity]], and computer science as academic disciplines. f49640659a15b1113a0c1e9eb6a7e24a9669a759 0 8 4345 3632 2025-12-19T15:48:48Z R4ven 304 i have added the "Cybersecurity, DDoS, ARPANET, Ransomware and Penetration Testing" articals. wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] ** [[Cybersecurity]] ** [[DDoS]] ** [[ARPANET]] ** [[Ransomware]] ** [[Penetration testing|Penetration Testing]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 915e94c0e165e33fc55a369e1fbcdf534c4bf242 4347 4345 2025-12-19T16:35:35Z R4ven 304 added "malware and trojan" wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] ** [[Cybersecurity]] ** [[DDoS]] ** [[ARPANET]] ** [[Ransomware]] ** [[Penetration testing|Penetration Testing]] ** [[Malware]] ** [[Trojan]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 7b2fc73628ff062639df0b8fca24599f4c6e601a 4355 4347 2025-12-19T17:20:43Z R4ven 304 /* Advanced Terms */ wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] ** [[Cybersecurity]] ** [[DDoS]] ** [[ARPANET]] ** [[Ransomware]] ** [[Penetration testing|Penetration Testing]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[Wayland]] * [[X11]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 93fa0057af6444768668b97f9e5a1a2575639d5d 0 1070 4354 2025-12-19T17:18:07Z R4ven 304 i have explained what "Malware" is, its purpose, History and Types in detail. With citations. wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/malware|title=Malware|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>'''Malware''' (malicious software) refers to any software intentionally designed to disrupt, damage, infiltrate, or gain unauthorized access to computer systems, networks, or data. Malware operates by exploiting software vulnerabilities, misconfigurations, or user behavior to execute unwanted actions, often without the knowledge or consent of the system owner. It represents one of the core threats in modern computing and [[cybersecurity]]. ---- == Purpose == <ref>{{Cite|url=https://www.cisa.gov/malware|title=What Is Malware?|author=Cybersecurity and Infrastructure Security Agency (CISA)|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of malware is to achieve unauthorized objectives on a target system. These objectives commonly include stealing sensitive information, gaining persistent access, disrupting normal operations, surveilling users, extorting victims, or using compromised systems for further attacks. Malware may be financially motivated, politically driven, state-sponsored, or intended for sabotage, espionage, or experimentation. ---- == History == <ref>{{Cite|url=https://www.sciencedirect.com/science/article/pii/S016740481400082X|title=The History of Computer Viruses and Malware|author=Peter Szor|year=2014|accessdate=Retrieved on December 19, 2025}}</ref>The history of malware closely follows the evolution of computing and network connectivity. * '''1971''' – The ''Creeper'' program appears on ARPANET, often regarded as the first self-replicating malware. * '''1980s''' – Early computer viruses spread via floppy disks as personal computing becomes widespread. * '''1986''' – The ''Brain'' virus targets MS-DOS systems, becoming the first widely recognized PC virus. * '''1990s''' – Networked malware, email worms, and macro viruses emerge with the growth of the internet. * '''2000s''' – Malware becomes commercially driven, with botnets, spyware, and mass-distributed worms. * '''2010s''' – Advanced malware, ransomware, and state-sponsored tools increase in sophistication. * '''2020s–present''' – Malware evolves into modular, stealthy, and automated threats targeting cloud, mobile, IoT, and critical infrastructure environments. ---- == Types == <ref>{{Cite|url=https://www.kaspersky.com/resource-center/threats/malware-types|title=Types of Malware|author=Kaspersky Lab|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>Malware exists in many forms, each defined by its behavior and objectives. Common categories include '''viruses''', which attach to legitimate files; '''worms''', which self-propagate across networks; '''trojans''', which disguise malicious code as legitimate software; '''spyware''', which secretly collects information; '''[[ransomware]]''', which encrypts data for extortion; '''rootkits''', which conceal malicious activity; and '''botnet malware''', which allows attackers to remotely control large numbers of compromised systems. ---- == Significance == <ref>{{Cite|url=https://www.pearson.com/en-us/subject-catalog/p/computer-security-principles-and-practice/P200000003295|title=Computer Security: Principles and Practice|author=William Stallings|year=2018|accessdate=Retrieved on December 19, 2025}}</ref>Malware has had a profound impact on the development of [[cybersecurity]], influencing operating system design, network defenses, antivirus technologies, and international cyber policy. While malware is most commonly associated with criminal activity, its existence has driven advances in threat detection, incident response, secure software development, and digital risk management. Understanding malware is essential for protecting modern digital infrastructure and ensuring the reliability of computer systems worldwide. 7d97d867edf98ad4ac3257e8d90f195c74b70418 0 1071 4356 2025-12-19T17:24:17Z R4ven 304 i have explained what "Trojan" is, its purpose, History and Types in detail. wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/Trojan-horse-computing|title=Trojan horse|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>A '''Trojan''', or '''Trojan horse''', is a type of [[Malware|malicious]] software that disguises itself as a legitimate or desirable program in order to deceive users into executing it. Unlike viruses or worms, a Trojan does not self-replicate; instead, it relies on social engineering, user interaction, or deceptive distribution methods to gain access to a system. Once activated, a Trojan can perform hidden malicious actions while appearing to function as normal software. ---- == Purpose == <ref>{{Cite|url=https://www.cisa.gov/trojan-horse|title=Trojan Horse Malware|author=Cybersecurity and Infrastructure Security Agency (CISA)|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of a Trojan is to provide attackers with unauthorized access or control over a system while avoiding detection. Trojans are commonly used to steal sensitive information, install additional malware, create backdoors, spy on user activity, or enable remote command execution. Because Trojans exploit user trust rather than technical vulnerabilities alone, they are particularly effective against non-technical users and remain a persistent threat. ---- == History == <ref>{{Cite|url=https://www.sciencedirect.com/science/article/pii/S016740481400082X|title=A Short History of Malware|author=Peter Szor|year=2014|accessdate=Retrieved on December 19, 2025}}</ref>The concept of the Trojan horse in computing draws its name from the ancient Greek tale of deception. * '''1970s–1980s''' – Early theoretical discussions of deceptive programs appear in academic research. * '''1989''' – The ''AIDS Trojan'' (PC Cyborg) is distributed via floppy disks, becoming one of the first well-known Trojans. * '''1990s''' – Trojans spread through pirated software, email attachments, and early internet downloads. * '''2000s''' – Remote access Trojans (RATs) become widespread, enabling full system control. * '''2010s''' – Banking Trojans and spyware target financial credentials and personal data. * '''2020s–present''' – Trojans are commonly used as initial access tools in ransomware, espionage, and supply-chain attacks. ---- == Types == <ref>{{Cite|url=https://www.kaspersky.com/resource-center/threats/trojans|title=What Is a Trojan Horse?|author=Kaspersky Lab|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>Trojans are classified based on their functionality and intended outcome. Common types include '''remote access Trojans (RATs)''', which grant attackers full control; '''banking Trojans''', designed to steal financial information; '''dropper Trojans''', which install additional malware; '''spy Trojans''', which monitor user activity; and '''backdoor Trojans''', which create persistent unauthorized access points. Many modern Trojans are modular and capable of performing multiple roles. ---- == Significance == <ref>{{Cite|url=https://www.pearson.com/en-us/subject-catalog/p/computer-security-principles-and-practice/P200000003295|title=Computer Security: Principles and Practice|author=William Stallings|year=2018|accessdate=Retrieved on December 19, 2025}}</ref>Trojans are among the most prevalent forms of malware due to their reliance on deception rather than technical exploits. They play a central role in large-scale cybercrime, data breaches, and advanced persistent threats. Understanding Trojans is essential to [[cybersecurity]] education, as they highlight the importance of user awareness, software authenticity, and layered security controls in defending modern computing environments. d93fa167e089bc4de2ea5ebc15f0ced587a6e56a 0 1072 4357 2025-12-19T19:03:27Z R4ven 304 i have explained what "Script/Scripting" is, its purpose, History, Types and Significance in detail with the citations. wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/script-computer-programming|title=Script|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>A '''script''' is a set of written instructions designed to be interpreted and executed by a computer or [[:Category:Software|software]] environment rather than compiled into machine code beforehand. Scripts are typically written in high-level programming or scripting languages and are used to automate tasks, control [[:Category:Software|software]] behavior, and perform repetitive or system-level operations efficiently. ---- == Purpose == <ref>{{Cite|url=https://www.ibm.com/topics/scripting|title=What Is a Script?|author=IBM|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of a script is '''automation and control'''. Scripts reduce manual effort by executing predefined actions such as file management, system configuration, data processing, application interaction, and administrative tasks. In many environments, scripts enable rapid development, customization, and orchestration of systems without requiring full-scale [[:Category:Software|software]] engineering. ---- == History == <ref>{{Cite|url=https://en.wikipedia.org/wiki/Scripting_language|title=Scripting Language|author=Wikipedia Contributors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>The concept of scripting emerged alongside early computing and operating systems. * '''1960s–1970s''' – Job control languages and command scripts appear in mainframe systems. * '''1980s''' – Shell scripting becomes common in [[UNIX|Unix]]-based operating systems. * '''1990s''' – Languages such as Perl, JavaScript, and VBScript popularize scripting for web and system tasks. * '''2000s''' – Python, PHP, and PowerShell expand scripting into enterprise, web, and automation domains. * '''2010s–present''' – Scripts are central to DevOps, cloud infrastructure, [[cybersecurity]], and automation workflows. ---- == Types == <ref>{{Cite|url=https://www.redhat.com/en/topics/automation/what-is-a-script|title=What Is a Script? Shell, Automation, and Application Scripts|author=Red Hat|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>Scripts can be categorized by their execution environment and purpose. Common types include '''shell scripts''' for operating system automation, '''web scripts''' for client-side or server-side logic, '''administrative scripts''' for system management, '''automation scripts''' for repetitive workflows, and '''security scripts''' used in testing, monitoring, and analysis. Some scripts are standalone, while others operate within larger software frameworks. ---- == Significance == <ref>{{Cite|url=https://www.pearson.com/en-us/subject-catalog/p/computer-security-principles-and-practice/P200000003295|title=Computer Security: Principles and Practice|author=William Stallings|year=2018|accessdate=Retrieved on December 19, 2025}}</ref>Scripts are foundational to modern computing due to their flexibility, efficiency, and ease of use. They play a critical role in system administration, software development, cybersecurity, and infrastructure management. By enabling rapid task execution and system customization, scripting significantly improves productivity and operational consistency across digital environments. 606fc8f28620d63afd735a8a2dc3e3d03946fc3b 4358 4357 2025-12-24T22:48:20Z Ow0cast 249 move cites to after sentences wikitext text/x-wiki A '''script''' is a set of written instructions designed to be interpreted and executed by a computer or [[:Category:Software|software]] environment rather than compiled into machine code beforehand.<ref>{{Cite|url=https://www.britannica.com/technology/script-computer-programming|title=Script|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref> Scripts are typically written in high-level programming or scripting languages and are used to automate tasks, control [[:Category:Software|software]] behavior, and perform repetitive or system-level operations efficiently. ---- == Purpose == The primary purpose of a script is '''automation and control'''.<ref>{{Cite|url=https://www.ibm.com/topics/scripting|title=What Is a Script?|author=IBM|year=2023|accessdate=Retrieved on December 19, 2025}}</ref> Scripts reduce manual effort by executing predefined actions such as file management, system configuration, data processing, application interaction, and administrative tasks. In many environments, scripts enable rapid development, customization, and orchestration of systems without requiring full-scale [[:Category:Software|software]] engineering. ---- == History == The concept of scripting emerged alongside early computing and operating systems.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Scripting_language|title=Scripting Language|author=Wikipedia Contributors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref> * '''1960s–1970s''' – Job control languages and command scripts appear in mainframe systems. * '''1980s''' – Shell scripting becomes common in [[UNIX|Unix]]-based operating systems. * '''1990s''' – Languages such as Perl, JavaScript, and VBScript popularize scripting for web and system tasks. * '''2000s''' – Python, PHP, and PowerShell expand scripting into enterprise, web, and automation domains. * '''2010s–present''' – Scripts are central to DevOps, cloud infrastructure, [[cybersecurity]], and automation workflows. ---- == Types == Scripts can be categorized by their execution environment and purpose.<ref>{{Cite|url=https://www.redhat.com/en/topics/automation/what-is-a-script|title=What Is a Script? Shell, Automation, and Application Scripts|author=Red Hat|year=2023|accessdate=Retrieved on December 19, 2025}}</ref> Common types include '''shell scripts''' for operating system automation, '''web scripts''' for client-side or server-side logic, '''administrative scripts''' for system management, '''automation scripts''' for repetitive workflows, and '''security scripts''' used in testing, monitoring, and analysis. Some scripts are standalone, while others operate within larger software frameworks. ---- == Significance == Scripts are foundational to modern computing due to their flexibility, efficiency, and ease of use.<ref>{{Cite|url=https://www.pearson.com/en-us/subject-catalog/p/computer-security-principles-and-practice/P200000003295|title=Computer Security: Principles and Practice|author=William Stallings|year=2018|accessdate=Retrieved on December 19, 2025}}</ref> They play a critical role in system administration, software development, cybersecurity, and infrastructure management. By enabling rapid task execution and system customization, scripting significantly improves productivity and operational consistency across digital environments. 2db8aa69c0fa2b95c14a354711da27e7278dd861 0 641 4359 3852 2025-12-29T16:04:45Z 0Stormy 158 Change status from maintenance to unmaintained as there hasn't been a commit on their GitHub in over 10 years. wikitext text/x-wiki [[Category:X_Window_Managers]] {{SoftwareInfobox | image = [[File:Openbox-icon.png|Openbox-icon]] | caption = Openbox | title Openbox | releasestatus = Unmaintained |lastrelease=3.4.11 February 08, 2010 |firstrelease=0.0.0 April 10, 2002 | languages = [[C]] | developers = Dana Jansens | website = [https://openbox.org/ openbox.org] }} [[File:Openbox 3.4.10 default.png|alt=Openbox 3.4.10 with default configuration and theme.|thumb|Openbox 3.4.10 with default configuration and theme.]] Openbox is a highly configurable [[X Window Manager|window manager]] for the [[X11]] windowing system that is forked of the [[Blackbox]] window manager. Openbox was created by Mikael Magnusson and is now being maintained by Dana Jansens. It focuses on providing a traditional window management experience that could be compared to the window management of [[Microsoft Windows]].<ref>[https://openbox.org/ Home - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> Openbox runs on many [[Unix-Like]] operating systems including Linux and the many flavors of [[BSD]]. ===Features=== Openbox is very minimal by design, but can easily be expanded via other [[applications]] such as a [[panel]] and system utilities. It has two main components to make it function, those being: * Openbox window manager: Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * ObConf: A configuration tool for Openbox which allows you to modify many things about Openbox graphically such as the theme, window management behavior, and workspaces.<ref>[https://openbox.org/obconf ObConf - Openbox], Openbox, 2024-08-06 (Accessed: 2025-08-09)</ref> === Usage === While Openbox is perfectly usable on its own, many desktops environments use Openbox as their window manager of choice due to its lack of dependencies, including [[LXQt]] and [[LXDE]].<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers#general ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], lxqt, 2025-08-09 (Accessed: 2025-08-09)</ref> Openbox is also used in many lightweight Linux distributions including [[Slitaz Linux|SliTaz Linux]] and [[CrunchBang Linux]].<ref>[https://slitaz.org/en/about/ SliTaz - About the project], SliTaz (Accessed: 2025-08-09)</ref><ref>[https://crunchbang.org/about/ About - CrunchBang], CrunchBang Linux, 2025-08-09 (Accessed: 2025-08-09)</ref> == References == <references /> 270b9266fb15d2d23f3ab98bb2b0d6c964ae55b2 0 626 4360 4334 2025-12-31T08:04:33Z Mellowind 305 wikitext text/x-wiki {{DistributionInfobox | title = Manjaro | image = [[File:Manjaro logo new.svg|Thumb]] | caption = The Manjaro logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]], [[Pamac]] | defaultdesktops = [[KDE Plasma]], [[Xfce]], [[GNOME]] | usagetype = Desktop | architectures = x86_64, Arm64 | website = [https://manjaro.org manjaro.org] }} Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>[https://manjaro.org/ Manjaro – The Linux for People and Organizations], Manjaro, 2025-08-09 (Accessed: 2025-08-09)</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">[https://distrowatch.com/table.php?distribution=manjaro DistroWatch.com: Manjaro Linux], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" Rolling Release * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>[https://wiki.manjaro.org/index.php/Pamac Pamac - Manjaro], Manjaro, 2023-03-09 (Accessed: 2025-08-09)</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME|GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>[https://en.wikipedia.org/wiki/Manjaro Manjaro], Wikipedia contributors, 2025-07-01 (Accessed: 2025-08-09)</ref><ref>[https://www.ubuntumint.com/manjaro-linux-history/ The History of Manjaro Linux Distribution], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>[https://www.geeksforgeeks.org/how-to-install-manjaro-linux/ How to Install Manjaro Linux?], GeeksforGeeks, 2023-12-22 (Accessed: 2025-08-09)</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch's base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch's, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>[https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/ How to Enable Arch User Repository (AUR) in Manjaro Linux], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro's custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch's upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>[https://itsfoss.com/manjaro-vs-arch-linux/ Manjaro vs Arch: What's the Difference? Which one to Use?], Dimitrios, Abhishek Prakash, 2023-09-13 (Accessed: 2025-08-09)</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>[https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. == References == eaf0c238a1f53153b77c7e7a8f052ca95ab1bb2f 0 1073 4361 2026-01-05T08:13:22Z 7oznova 308 Created simple page for s6 wikitext text/x-wiki {{Stub}} '''s6''' is a suite of small and secure programs for process supervision and system initialization on [[UNIX|Unix-like]] [[Operating System|operating systems]], including [[Linux]] and [[BSD]] variants.<ref>https://skarnet.org/software/s6/</ref> It was created by Laurent Bercot as a modern alternative to daemontools, [[Runit|runit]], and similar supervision suites, emphasizing reliability, security, minimalism, and proper dependency handling through readiness notification. s6 can function either as a full init system (with '''s6-linux-init''') or as a process supervisor under another init system. === Design === When used as a full init system with s6-linux-init, s6 operates in a staged boot process similar to other supervision-based inits: * '''Stage 1''': The s6-linux-init-provided /sbin/init performs early boot tasks (mounting filesystems, starting udev, basic system preparation) and then executes a one-time initialization script (typically /etc/s6-linux-init/scripts/rc.init or equivalent). This stage handles all non-recurring setup tasks and has direct access to the console for error recovery.<ref>https://skarnet.org/software/s6-linux-init/</ref> * '''Stage 2''': The supervision tree is started, typically via s6-svscan scanning a service directory. Individual services are monitored by s6-supervise processes. Service dependencies and readiness are managed reliably without external mechanisms. This stage runs continuously until shutdown or reboot.<ref>https://skarnet.org/software/s6/overview.html</ref> * '''Stage 3''': On halt or reboot, the supervision tree is cleanly stopped, and a shutdown script (typically /etc/s6-linux-init/scripts/rc.shutdown) performs final tasks such as unmounting filesystems and powering off the system. The core supervision framework ('''s6-svscan''' and '''s6-supervise''') is highly portable across Unix-like systems, while s6-linux-init provides Linux-specific early boot support. Advanced service management is available via the companion '''s6-rc''' package. === Distributions with s6 === * Adélie Linux (uses s6-linux-init for early boot with OpenRC service management)<ref>https://pkg.adelielinux.org/current/s6-linux-init</ref> * [[Artix Linux]] (offered as official alternative, including s6-linux-init and s6-rc)<ref>https://wiki.artixlinux.org/Main/S6</ref> * [[Gentoo|Gentoo Linux]] (s6, s6-linux-init, and s6-rc available as packages)<ref>https://wiki.gentoo.org/wiki/S6-linux-init_(package)</ref> * Obarun Linux (s6 with 66 frontend as the default init and service manager)<ref>https://web.obarun.org/</ref> == References == <references /> 724124f5c32e9aa85061b8b475fcb48c54916ea7 4362 4361 2026-01-05T14:59:55Z Imnotgoodatnames 121 added display title wikitext text/x-wiki {{Stub}} {{DISPLAYTITLE:s6}} '''s6''' is a suite of small and secure programs for process supervision and system initialization on [[UNIX|Unix-like]] [[Operating System|operating systems]], including [[Linux]] and [[BSD]] variants.<ref>https://skarnet.org/software/s6/</ref> It was created by Laurent Bercot as a modern alternative to daemontools, [[Runit|runit]], and similar supervision suites, emphasizing reliability, security, minimalism, and proper dependency handling through readiness notification. s6 can function either as a full init system (with '''s6-linux-init''') or as a process supervisor under another init system. === Design === When used as a full init system with s6-linux-init, s6 operates in a staged boot process similar to other supervision-based inits: * '''Stage 1''': The s6-linux-init-provided /sbin/init performs early boot tasks (mounting filesystems, starting udev, basic system preparation) and then executes a one-time initialization script (typically /etc/s6-linux-init/scripts/rc.init or equivalent). This stage handles all non-recurring setup tasks and has direct access to the console for error recovery.<ref>https://skarnet.org/software/s6-linux-init/</ref> * '''Stage 2''': The supervision tree is started, typically via s6-svscan scanning a service directory. Individual services are monitored by s6-supervise processes. Service dependencies and readiness are managed reliably without external mechanisms. This stage runs continuously until shutdown or reboot.<ref>https://skarnet.org/software/s6/overview.html</ref> * '''Stage 3''': On halt or reboot, the supervision tree is cleanly stopped, and a shutdown script (typically /etc/s6-linux-init/scripts/rc.shutdown) performs final tasks such as unmounting filesystems and powering off the system. The core supervision framework ('''s6-svscan''' and '''s6-supervise''') is highly portable across Unix-like systems, while s6-linux-init provides Linux-specific early boot support. Advanced service management is available via the companion '''s6-rc''' package. === Distributions with s6 === * Adélie Linux (uses s6-linux-init for early boot with OpenRC service management)<ref>https://pkg.adelielinux.org/current/s6-linux-init</ref> * [[Artix Linux]] (offered as official alternative, including s6-linux-init and s6-rc)<ref>https://wiki.artixlinux.org/Main/S6</ref> * [[Gentoo|Gentoo Linux]] (s6, s6-linux-init, and s6-rc available as packages)<ref>https://wiki.gentoo.org/wiki/S6-linux-init_(package)</ref> * Obarun Linux (s6 with 66 frontend as the default init and service manager)<ref>https://web.obarun.org/</ref> == References == <references /> c29a9f7e6a91727c235a7a23f208c0046d75726b 0 198 4363 4330 2026-01-08T05:14:54Z 7oznova 308 /* Arch Based */ Fixed grammar. wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |A Ubuntu based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming focused distribution based on Debian unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer system76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IOT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76 |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 362af006e383d7258e0658f4e25129d8478690a1 4364 4363 2026-01-08T05:17:24Z 7oznova 308 /* Debian Based */ Fixed grammar. wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be use on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76 |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == da0b90246638f9b9a61d4b64ac617dd0757b2cba 4365 4364 2026-01-08T05:18:50Z 7oznova 308 /* Gentoo Based */ Fixed grammar. wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76 |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat based OS made for the Democratic People's Republic of Korea (North Korea) |- |[[Rocky Linux]] |A community managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == c710f05b6cc48e567c816be33bda7d01b798405d 4366 4365 2026-01-08T05:20:40Z 7oznova 308 /* Red Hat Based */ Fixed grammar. wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be ran on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 14650856de25becbbac45cd16b3188f8a052a497 4367 4366 2026-01-08T05:21:53Z 7oznova 308 /* Slackware Based */ Fixed grammar. wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An Immutable distribution designed to be easy to use and maintain, it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain, it exclusively uses the KDE Desktop Enviornment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability, each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project, designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects, it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A Gaming focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An set of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == d0be3e5c4b87c58b83de940d127d782647f86c80 4368 4367 2026-01-08T05:23:43Z 7oznova 308 /* openSUSE Based */ Fixed grammar. wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain; it exclusively uses the KDE Desktop Environment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability; each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind, as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects; it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | A set of enterprise distributions created and maintained by SUSE, designed for desktops, servers, containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |a user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[Slitaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A Semi-Rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |An security operating system that is built on Xen Hypervisor and can make etc vms like windows or fedora |} == References == 17e0e4c7f3a01a4269cc63539fc96dc479932844 4369 4368 2026-01-08T05:26:24Z 7oznova 308 /* Other Independent Distributions */ Restore title previously lost during GUI editor error. wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain; it exclusively uses the KDE Desktop Environment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability; each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind, as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects; it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | A set of enterprise distributions created and maintained by SUSE, designed for desktops, servers, containers, and much more |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain; it exclusively uses the KDE Desktop Environment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability; each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind, as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects; it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | A set of enterprise distributions created and maintained by SUSE, designed for desktops, servers, containers, and much more |} == References == 925daa6bec5620449dafd37f8c5198af0d0d1e34 4370 4369 2026-01-08T05:34:24Z 7oznova 308 All grammatical errors fixed. wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain; it exclusively uses the KDE Desktop Environment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability; each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind, as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects; it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | A set of enterprise distributions created and maintained by SUSE, designed for desktops, servers, containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 604f956f2ff194dded2a162791b05da53b0e0604 0 176 4371 4124 2026-01-11T14:27:32Z Gurov 103 Version update wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.5.4, December 9, 2025 [https://kde.org/announcements/plasma/6/6.5.4/] |firstrelease=1.0, July 12, 1998 [https://kde.org/announcements/1-2-3/1.0-beta1/] | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2025-08-14|503}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2025-08-14|503}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> 44d24f5a6220dd7c94ae95878accf35df5ff6791 0 291 4372 3614 2026-01-11T14:28:58Z Gurov 103 Version update wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|300px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 49, 2025-09-17 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[Category:Desktop Environments]] [[File:GNOME 43.png|thumb|A desktop running GNOME 43]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>[https://www.gnu.org/philosophy/free-sw.en.html What is Free Software?], GNU (Accessed: May 7, 2025)</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>[[wikipedia:Qt_(software)#Early_developments|Early Developments of QT]], Wikipedia (Accessed: May 7, 2025)</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>[[wikipedia:GNOME#History|History of GNOME]], Wikipedia (Accessed: May 7, 2025)</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>[https://foundation.gnome.org/ GNOME Foundation], GNOME Foundation, 2025-08-08 (Accessed: 2025-08-09)</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. == References == af5a16077153c4245de5bda42d37b09bd1cfac3b 0 884 4373 4265 2026-01-11T14:30:20Z Gurov 103 Version update wikitext text/x-wiki {{Work In Progress}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.3.0, Nov 5, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>[https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFM file manager is ported to Qt? – LXDE Blog], PCMan, 2013 (Accessed: 2025-10-26)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>[https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ “The future of Razor and LXDE-Qt” – LXDE Blog], PCMan, 2013 (Accessed: 2025-10-26)</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>[https://lubuntu.me/ Lubuntu – The official Lubuntu home], Lubuntu, 2025 (Accessed: 2025-10-26)</ref> * [[Fedora]] LXQt spin<ref>[https://fedoraproject.org/spins/lxqt Fedora LXQt Spin | The Fedora Project], Fedora, 2025 (Accessed: 2025-10-26)</ref> * [[CachyOS]]: available in installer<ref>[https://wiki.cachyos.org/installation/desktop_environments/ Desktop Environments | CachyOS], CachyOS, 2025 (Accessed: 2025-10-26)</ref> * [[SparkyLinux]]<ref>[https://wiki.sparkylinux.org/doku.php/about about Sparky Wiki], Sparky Linux, 2025 (Accessed: 2025-10-26)</ref> * [[Debian]]: available in installer<ref>[https://wiki.debian.org/LXQt LXQt - Debian Wiki], Debian Wiki, 2025 (Accessed: 2025-10-26)</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>[https://packages.debian.org/stable/lxqt-core Debian -- Details of package lxqt-core in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>[https://packages.debian.org/trixie/lxqt Debian -- Details of package lxqt in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>[https://packages.debian.org/stable/task-lxqt-desktop Debian -- Details of package task-lxqt-desktop in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>[https://archlinux.org/groups/x86_64/lxqt/ Arch Linux - lxqt (x86_64) - Group Details], Arch Linux, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>[https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template void-packages/srcpkgs/lxqt/template at master · void-linux/void-packages · GitHub], Github, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], LXQt wiki, 2025 (Accessed: 2025-10-26)</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>[https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions Launching LXQt sessions · lxqt/lxqt Wiki · GitHub], LXQt wiki, 2025 (Accessed:2025-10-26)</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight lang="text">exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == f263f26f86282892803aca4db85aade7fd888034 6 1074 4374 2026-01-11T21:09:19Z Katea 309 wikitext text/x-wiki Screenshot of the Zypper package manager running an install command `sudo zypper intall neovim` showing the dependency resolution and download progress bar output 39fce939800fda8e21a4a7076b6983de13f3daa3 0 173 4375 4297 2026-01-11T21:53:18Z Ivanovics 150 Fix formatting, add filebox for example session wikitext text/x-wiki {{Cleanup|Incomplete page}} [[Category:Terminology]] [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager ('''GDM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''' A Display Manager (DM), also known as a login manager, is typically a [[graphical user interface]] that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment‏‎]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself. == Role and Functions == The primary role of the Display Manager is to manage and control the graphical display sessions on a system. It performs several essential tasks: * User Authentication: The DM presents the graphical login screen (often referred to as the greeter) to authenticate users by checking their credentials. * Session Initiation: Upon successful login, it starts the user's chosen graphical session, which is typically a full [[Desktop Environment‏‎]] (DE) or a [[Window Manager‏‎]] (WM). Most DMs support both Wayland and X11 backends. * Session Management: It allows for switching between different users or desktop environments without requiring a full system reboot. == Examples == {| class="wikitable sortable" |+ Display Managers |- ! Name !! DE/Type !! Description |- | GDM || GNOME || '''G'''NOME '''D'''isplay '''M'''anager. Default for systems like Fedora and Ubuntu. Well-integrated with Wayland, but often considered more resource-intensive. |- | SDDM || KDE Plasma, LXQt || '''S'''imple '''D'''esktop '''D'''isplay '''M'''anager. Uses Qt/QML for a modern, highly customizable and visually appealing interface. Successor to KDM. |- | LightDM || Xfce, MATE || '''Light'''weight '''D'''isplay '''M'''anager. Known for being lightweight and highly configurable using separate "greeter" programs (e.g., `lightdm-gtk-greeter`). |- | '''XDM''' || X Window System || '''X''' '''D'''isplay '''M'''anager. The original, most basic DM for the X Window System. Minimalist and used primarily for its simplicity. |- | '''Ly''' || TUI || A text-based (TUI/ncurses-like) display manager that runs in the TTY but can launch both X and Wayland sessions, popular for extremely minimal setups. Written in Zig. |- | '''emptty'' || TUI || A dead simple TUI display manager similar to Ly that runs in the TTY and prioritizes simple yet powerful configuration. |} == Configuration == ==== Enabling a Display Manager (systemd) ==== On modern Linux distributions that use systemd, the DM is started as a system service. To switch the active DM, you typically disable the current service and enable the desired one. <syntaxhighlight lang="bash"> # Example: Switching from GDM to SDDM # 1. Stop and disable the old DM service sudo systemctl disable gdm.service sudo systemctl stop gdm.service # 2. Enable the new DM service sudo systemctl enable sddm.service --now # `--now` starts the service immediately once enabled </syntaxhighlight> 2. Session Definition Display Managers discover the available session options (like "GNOME," "KDE," "i3") by reading <code>.desktop</code> files in the following system directories: * <code>/usr/share/xsessions/</code> (for X11 sessions) * <code>/usr/share/wayland-sessions/</code> (for Wayland sessions) ==== Example: Defining an Openbox session ==== {{FileBox|title=/usr/share/xsessions/openbox.desktop | content = [Desktop Entry] Name=Openbox Comment=Log in using the Openbox window manager Exec=/usr/bin/openbox-session TryExec=/usr/bin/openbox-session Icon=openbox Type=Application }}]] bccad51ad2b87a034546532ca5e7fdaf31d9bce2 4376 4375 2026-01-11T21:59:12Z Ivanovics 150 Unexplode page (oopsie) wikitext text/x-wiki {{Cleanup|Incomplete page}} [[Category:Terminology]] [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager ('''GDM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']]A Display Manager (DM), also known as a login manager, is typically a [[graphical user interface]] that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself. == Role and Functions == The primary role of the Display Manager is to manage and control the graphical display sessions on a system. It performs several essential tasks: * User Authentication: The DM presents the graphical login screen (often referred to as the greeter) to authenticate users by checking their credentials. * Session Initiation: Upon successful login, it starts the user's chosen graphical session, which is typically a full [[Desktop Environment‏‎]] (DE) or a [[Window Manager‏‎]] (WM). Most DMs support both Wayland and X11 backends. * Session Management: It allows for switching between different users or desktop environments without requiring a full system reboot. == Examples == {| class="wikitable sortable" |+ Display Managers |- ! Name !! DE/Type !! Description |- | GDM || GNOME || '''G'''NOME '''D'''isplay '''M'''anager. Default for systems like Fedora and Ubuntu. Well-integrated with Wayland, but often considered more resource-intensive. |- | SDDM || KDE Plasma, LXQt || '''S'''imple '''D'''esktop '''D'''isplay '''M'''anager. Uses Qt/QML for a modern, highly customizable and visually appealing interface. Successor to KDM. |- | LightDM || Xfce, MATE || '''Light'''weight '''D'''isplay '''M'''anager. Known for being lightweight and highly configurable using separate "greeter" programs (e.g., `lightdm-gtk-greeter`). |- | '''XDM''' || X Window System || '''X''' '''D'''isplay '''M'''anager. The original, most basic DM for the X Window System. Minimalist and used primarily for its simplicity. |- | '''Ly''' || TUI || A text-based (TUI/ncurses-like) display manager that runs in the TTY but can launch both X and Wayland sessions, popular for extremely minimal setups. Written in Zig. |- | '''emptty''' || TUI || A dead simple TUI display manager similar to Ly that runs in the TTY and prioritizes simple yet powerful configuration. |} == Configuration == ==== Enabling a Display Manager (systemd) ==== On modern Linux distributions that use systemd, the DM is started as a system service. To switch the active DM, you typically disable the current service and enable the desired one. <syntaxhighlight lang="bash"> # Example: Switching from GDM to SDDM # 1. Stop and disable the old DM service sudo systemctl disable gdm.service sudo systemctl stop gdm.service # 2. Enable the new DM service sudo systemctl enable sddm.service --now # `--now` starts the service immediately once enabled </syntaxhighlight> 2. Session Definition Display Managers discover the available session options (like "GNOME," "KDE," "i3") by reading <code>.desktop</code> files in the following system directories: * <code>/usr/share/xsessions/</code> (for X11 sessions) * <code>/usr/share/wayland-sessions/</code> (for Wayland sessions) ==== Example: Defining an Openbox session ==== {{FileBox|title=/usr/share/xsessions/openbox.desktop | content = [Desktop Entry] Name=Openbox Comment=Log in using the Openbox window manager Exec=/usr/bin/openbox-session TryExec=/usr/bin/openbox-session Icon=openbox Type=Application }} 92d0ed93f582fcd6c8756dde4109e209100aa22d 0 1075 4377 2026-01-11T22:26:39Z Ivanovics 150 LXDE page, covering important bits and some history wikitext text/x-wiki {{SoftwareInfobox | image=[[File:LXDE desktop full.png|thumb]] | caption = The default LXDE desktop | title=LXDE | releasestatus=Maintained | lastrelease=0.10.1, 25 February 2021 | firstrelease=2006; 20 years ago | languages=[[C]] | developers=PCMan (formerly), The LXDE Team (currently) | website=https://www.lxde.org/ }} '''LXDE,''' which is an abbreviation of '''Lightweight X11 Desktop Environment''' is a free to use desktop environment aiming to be as low on resource usage as possible. LXDE is aimed at Unix and other POSIX-compliant platforms such as BSD and Linux, and is made using GTK2 and the C programming language. It uses a rolling-release model for its individual components (or groups of components that depend on each other). == History == The project was started in 2006 by Hong Jen Yee (online known as PCMan) when he released PCManFM, which is the first module of LXDE Currently the original LXDE only receives maintenance updates, because its creator was dissatisfied with GTK3 and decided to port the entire software suite to Qt (announced in 2013) and later that year the LXDE and LXQt projects got merged Since the beginning of 2020 a GTK3 port is developed by the Arch Linux community, and several important components of LXDE have already been ported == Software Components== {| class="wikitable" ! Components ! Descriptions |- | PCMan File Manager | File manager and Desktop metaphor provider |- | LXInput | Mouse and keyboard configuration tool |- | LXLauncher | Application Launcher |- | LXPanel | Desktop panel |- | LXSession | X session manager |- | LXAppearance | GTK theme switcher |- | GPicView | Image viewer |- | LXMusic | Audio player and fronted for XMMS2 | |- | LXTerminal | Terminal emulator |- | LXTask | Task manager |- | LXRandR | A GUI for X Resize and Rotate (xrandr) | |- | LXDM | X display manager |- | [[Openbox]] | Window manager used by LXDE |- | [[ObConf]] | A GUI tool for managing Openbox's configuration |- |} 565a353380495f97b0e47b923fcc64f4fe804e4e 0 762 4378 3713 2026-01-12T00:11:46Z Katea 309 Complete overhaul and rewrite of the page. Added a softwareinfo template, summary, history and usage sections. This was done because the page was previously a stub containing very little information with a message in the history requesting urgent work. wikitext text/x-wiki {{SoftwareInfobox | title = Zypper | releasestatus = Maintained | lastrelease = 1.14.94, 2025-09-23 | languages = [[C++]] | developers = [[SUSE]], [[openSUSE]] | website = [https://en.opensuse.org/Portal:Zypper Portal:Zypper] }} [[Category:Package Managers]] Zypper is the primary [[Package Manager|package manager]] for [[SLES|SUSE Linux Enterprise Server]], [[openSUSE|openSUSE]] and their derivatives. Zypper is a command-line interface to ZYpp System Management Library (libzypp) and uses [[rpm|RPM]] package archives <ref> [https://manpages.opensuse.org/Tumbleweed/zypper/zypper.8.en.html zypper(8)] openSUSE manpages, 2025-09-23 (Accessed: 2026-01-12) </ref> similar to [[Fedora|Fedora Linux]] and [[RHEL|Red Hat Enterprise Linux]]. Zypper is a binary package manager with support for x86, x86-64 (amd64), ARM, s390x and PowerPC. <ref> [https://get.opensuse.org/tumbleweed/?type=server#download openSUSE Tumbleweed] openSUSE Tumbleweed download page showing supported CPU Architectures (Accessed: 2026-01-12) </ref> == History == libZypp and by extension ZYpp and Zypper were released on January 14th 2006. <ref> [https://github.com/openSUSE/libzypp/blob/90acb93974a99bea7409516be55d6acdc35099f7/package/libzypp.changes libzypp Github] Earliest libzypp changelog (Accessed: 2026-01-12) </ref> In March of 2025 Zypper added experimental support for parallel downloads starting in libzypp version 17.36.4 and Zypper version 1.14.87. <ref> [https://news.opensuse.org/2025/03/27/zypper-adds-experimental-parallel-downloads/ openSUSE] Announcement of experimental parallel downloads support (Accessed: 2026-01-12) </ref> In May of 2025 parallel downloads were enabled by default starting in libzypp version 17.37.1 and Zypper version 1.14.90. <ref> [https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JR725AXWDZYLJ3PKIKYAYQQAXE6OWQMM/ openSUSE] Announcement of parallel downloads becoming the new default (Accessed: 2026-01-12) </ref> == Usage == Zypper uses an argument system for interacting with the package manager with it's syntax being <code>zypper [ARGUMENT] [PACKAGE]</code> for example <code>zypper install vim</code>. There are 2 forms of each argument and, full and abbreviated, this behavior similar to [[DNF|DNF]] the Fedora/RHEL package manager. {| class="wikitable" |+Common Zypper Arguments !Full !Abbreviated !Description |- |<code>zypper install [TARGET]</code> |<code>zypper in [TARGET]</code> |Installs or updates a given package or pattern (use <code>-t</code> flag when installing patterns) |- |<code>zypper remove [TARGET]</code> |<code>zypper rm [TARGET]</code> |Uninstalls a given package |- |<code>zypper update</code> |<code>zypper up</code> |Upgrades the installed packages without removing packages (This is the preferred way to update a Leap or SLES system) |- |<code>zypper dist-upgrade</code> |<code>zypper dup</code> |Upgrades the installed packages while performing vendor changes, package removals and renames (This is the preferred way to update a Tumbleweed system) |- |<code>zypper refresh</code> |<code>zypper ref</code> |Refreshes the package repository mirrors (This is performed automatically is zypper detects an out of date repository when running install, remove, update, dist-upgrade or search commands) |- |<code>zypper search [SEARCH-TERM]</code> |<code>zypper se [SEARCH-TERM]</code> |Searches the enabled repositories for packages or patterns containing the search term entered |- |<code>dry-run</code> |<code>-D</code> |Runs the command being dry-ran without making any changes to the system |- |} == References == 968e070f9af18ae4679f44e5a58d0d606f75c206 4379 4378 2026-01-12T00:23:36Z Katea 309 fixed typos wikitext text/x-wiki {{SoftwareInfobox | title = Zypper | releasestatus = Maintained | lastrelease = 1.14.94, 2025-09-23 | languages = [[C++]] | developers = [[SUSE]], [[openSUSE]] | website = [https://en.opensuse.org/Portal:Zypper Portal:Zypper] }} [[Category:Package Managers]] Zypper is the primary [[Package Manager|package manager]] for [[SLES|SUSE Linux Enterprise Server]], [[openSUSE|openSUSE]] and their derivatives. Zypper is a command-line interface to ZYpp System Management Library (libzypp) and uses [[rpm|RPM]] package archives <ref> [https://manpages.opensuse.org/Tumbleweed/zypper/zypper.8.en.html zypper(8)] openSUSE manpages, 2025-09-23 (Accessed: 2026-01-12) </ref> similar to [[Fedora|Fedora Linux]] and [[RHEL|Red Hat Enterprise Linux]]. Zypper is a binary package manager with support for x86, x86-64 (amd64), ARM, s390x and PowerPC. <ref> [https://get.opensuse.org/tumbleweed/?type=server#download openSUSE Tumbleweed] openSUSE Tumbleweed download page showing supported CPU Architectures (Accessed: 2026-01-12) </ref> == History == libZypp and by extension ZYpp and Zypper were released on January 14th 2006. <ref> [https://github.com/openSUSE/libzypp/blob/90acb93974a99bea7409516be55d6acdc35099f7/package/libzypp.changes libzypp Github] Earliest libzypp changelog (Accessed: 2026-01-12) </ref> In March of 2025 Zypper added experimental support for parallel downloads starting in libzypp version 17.36.4 and Zypper version 1.14.87. <ref> [https://news.opensuse.org/2025/03/27/zypper-adds-experimental-parallel-downloads/ openSUSE] Announcement of experimental parallel downloads support (Accessed: 2026-01-12) </ref> In May of 2025 parallel downloads were enabled by default starting in libzypp version 17.37.1 and Zypper version 1.14.90. <ref> [https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JR725AXWDZYLJ3PKIKYAYQQAXE6OWQMM/ openSUSE] Announcement of parallel downloads becoming the new default (Accessed: 2026-01-12) </ref> == Usage == Zypper uses an argument system for interacting with the package manager with its syntax being <code>zypper [ARGUMENT] [PACKAGE]</code> for example <code>zypper install vim</code>. There are 2 forms of each argument and, full and abbreviated, this behavior is similar to [[DNF|DNF]] the Fedora/RHEL package manager. {| class="wikitable" |+Common Zypper Arguments !Full !Abbreviated !Description |- |<code>zypper install [TARGET]</code> |<code>zypper in [TARGET]</code> |Installs or updates a given package or pattern (use <code>-t</code> flag when installing patterns) |- |<code>zypper remove [TARGET]</code> |<code>zypper rm [TARGET]</code> |Uninstalls a given package |- |<code>zypper update</code> |<code>zypper up</code> |Upgrades the installed packages without removing packages (This is the preferred way to update a Leap or SLES system) |- |<code>zypper dist-upgrade</code> |<code>zypper dup</code> |Upgrades the installed packages while performing vendor changes, package removals and renames (This is the preferred way to update a Tumbleweed system) |- |<code>zypper refresh</code> |<code>zypper ref</code> |Refreshes the package repository mirrors (This is performed automatically is zypper detects an out of date repository when running install, remove, update, dist-upgrade or search commands) |- |<code>zypper search [SEARCH-TERM]</code> |<code>zypper se [SEARCH-TERM]</code> |Searches the enabled repositories for packages or patterns containing the search term entered |- |<code>dry-run</code> |<code>-D</code> |Runs the command being dry-ran without making any changes to the system |- |} == References == 0b9dde03b0dde205852215636343876c89908c4d 4382 4379 2026-01-12T00:59:18Z Katea 309 Added image and caption to SoftwareInfobox wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Zypper_Screenshot_2026-01-12.png|400px|Thumb]] | caption = Zypper install screenshot | title = Zypper | releasestatus = Maintained | firstrelease = 2006-01-14 | lastrelease = 1.14.94, 2025-09-23 | languages = [[C++]] | developers = [[SUSE]], [[openSUSE]] | website = [https://en.opensuse.org/Portal:Zypper Portal:Zypper] }} [[Category:Package Managers]] Zypper is the primary [[Package Manager|package manager]] for [[SLES|SUSE Linux Enterprise Server]], [[openSUSE|openSUSE]] and their derivatives. Zypper is a command-line interface to ZYpp System Management Library (libzypp) and uses [[rpm|RPM]] package archives <ref> [https://manpages.opensuse.org/Tumbleweed/zypper/zypper.8.en.html zypper(8)] openSUSE manpages, 2025-09-23 (Accessed: 2026-01-12) </ref> similar to [[Fedora|Fedora Linux]] and [[RHEL|Red Hat Enterprise Linux]]. Zypper is a binary package manager with support for x86, x86-64 (amd64), ARM, s390x and PowerPC. <ref> [https://get.opensuse.org/tumbleweed/?type=server#download openSUSE Tumbleweed] openSUSE Tumbleweed download page showing supported CPU Architectures (Accessed: 2026-01-12) </ref> == History == libZypp and by extension ZYpp and Zypper were released on January 14th 2006. <ref> [https://github.com/openSUSE/libzypp/blob/90acb93974a99bea7409516be55d6acdc35099f7/package/libzypp.changes libzypp Github] Earliest libzypp changelog (Accessed: 2026-01-12) </ref> In March of 2025 Zypper added experimental support for parallel downloads starting in libzypp version 17.36.4 and Zypper version 1.14.87. <ref> [https://news.opensuse.org/2025/03/27/zypper-adds-experimental-parallel-downloads/ openSUSE] Announcement of experimental parallel downloads support (Accessed: 2026-01-12) </ref> In May of 2025 parallel downloads were enabled by default starting in libzypp version 17.37.1 and Zypper version 1.14.90. <ref> [https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JR725AXWDZYLJ3PKIKYAYQQAXE6OWQMM/ openSUSE] Announcement of parallel downloads becoming the new default (Accessed: 2026-01-12) </ref> == Usage == Zypper uses an argument system for interacting with the package manager with its syntax being <code>zypper [ARGUMENT] [PACKAGE]</code> for example <code>zypper install vim</code>. There are 2 forms of each argument and, full and abbreviated, this behavior is similar to [[DNF|DNF]] the Fedora/RHEL package manager. {| class="wikitable" |+Common Zypper Arguments !Full !Abbreviated !Description |- |<code>zypper install [TARGET]</code> |<code>zypper in [TARGET]</code> |Installs or updates a given package or pattern (use <code>-t</code> flag when installing patterns) |- |<code>zypper remove [TARGET]</code> |<code>zypper rm [TARGET]</code> |Uninstalls a given package |- |<code>zypper update</code> |<code>zypper up</code> |Upgrades the installed packages without removing packages (This is the preferred way to update a Leap or SLES system) |- |<code>zypper dist-upgrade</code> |<code>zypper dup</code> |Upgrades the installed packages while performing vendor changes, package removals and renames (This is the preferred way to update a Tumbleweed system) |- |<code>zypper refresh</code> |<code>zypper ref</code> |Refreshes the package repository mirrors (This is performed automatically is zypper detects an out of date repository when running install, remove, update, dist-upgrade or search commands) |- |<code>zypper search [SEARCH-TERM]</code> |<code>zypper se [SEARCH-TERM]</code> |Searches the enabled repositories for packages or patterns containing the search term entered |- |<code>dry-run</code> |<code>-D</code> |Runs the command being dry-ran without making any changes to the system |- |} == References == dc49c3a9a56943982ca31bb8d78486e1469467ff 4383 4382 2026-01-12T01:43:11Z Katea 309 /* Usage */ fixed a typo wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Zypper_Screenshot_2026-01-12.png|400px|Thumb]] | caption = Zypper install screenshot | title = Zypper | releasestatus = Maintained | firstrelease = 2006-01-14 | lastrelease = 1.14.94, 2025-09-23 | languages = [[C++]] | developers = [[SUSE]], [[openSUSE]] | website = [https://en.opensuse.org/Portal:Zypper Portal:Zypper] }} [[Category:Package Managers]] Zypper is the primary [[Package Manager|package manager]] for [[SLES|SUSE Linux Enterprise Server]], [[openSUSE|openSUSE]] and their derivatives. Zypper is a command-line interface to ZYpp System Management Library (libzypp) and uses [[rpm|RPM]] package archives <ref> [https://manpages.opensuse.org/Tumbleweed/zypper/zypper.8.en.html zypper(8)] openSUSE manpages, 2025-09-23 (Accessed: 2026-01-12) </ref> similar to [[Fedora|Fedora Linux]] and [[RHEL|Red Hat Enterprise Linux]]. Zypper is a binary package manager with support for x86, x86-64 (amd64), ARM, s390x and PowerPC. <ref> [https://get.opensuse.org/tumbleweed/?type=server#download openSUSE Tumbleweed] openSUSE Tumbleweed download page showing supported CPU Architectures (Accessed: 2026-01-12) </ref> == History == libZypp and by extension ZYpp and Zypper were released on January 14th 2006. <ref> [https://github.com/openSUSE/libzypp/blob/90acb93974a99bea7409516be55d6acdc35099f7/package/libzypp.changes libzypp Github] Earliest libzypp changelog (Accessed: 2026-01-12) </ref> In March of 2025 Zypper added experimental support for parallel downloads starting in libzypp version 17.36.4 and Zypper version 1.14.87. <ref> [https://news.opensuse.org/2025/03/27/zypper-adds-experimental-parallel-downloads/ openSUSE] Announcement of experimental parallel downloads support (Accessed: 2026-01-12) </ref> In May of 2025 parallel downloads were enabled by default starting in libzypp version 17.37.1 and Zypper version 1.14.90. <ref> [https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JR725AXWDZYLJ3PKIKYAYQQAXE6OWQMM/ openSUSE] Announcement of parallel downloads becoming the new default (Accessed: 2026-01-12) </ref> == Usage == Zypper uses an argument system for interacting with the package manager with its syntax being <code>zypper [ARGUMENT] [PACKAGE]</code> for example <code>zypper install vim</code>. There are 2 forms of each argument, full and abbreviated, this behavior is similar to [[DNF|DNF]] the Fedora/RHEL package manager. {| class="wikitable" |+Common Zypper Arguments !Full !Abbreviated !Description |- |<code>zypper install [TARGET]</code> |<code>zypper in [TARGET]</code> |Installs or updates a given package or pattern (use <code>-t</code> flag when installing patterns) |- |<code>zypper remove [TARGET]</code> |<code>zypper rm [TARGET]</code> |Uninstalls a given package |- |<code>zypper update</code> |<code>zypper up</code> |Upgrades the installed packages without removing packages (This is the preferred way to update a Leap or SLES system) |- |<code>zypper dist-upgrade</code> |<code>zypper dup</code> |Upgrades the installed packages while performing vendor changes, package removals and renames (This is the preferred way to update a Tumbleweed system) |- |<code>zypper refresh</code> |<code>zypper ref</code> |Refreshes the package repository mirrors (This is performed automatically is zypper detects an out of date repository when running install, remove, update, dist-upgrade or search commands) |- |<code>zypper search [SEARCH-TERM]</code> |<code>zypper se [SEARCH-TERM]</code> |Searches the enabled repositories for packages or patterns containing the search term entered |- |<code>dry-run</code> |<code>-D</code> |Runs the command being dry-ran without making any changes to the system |- |} == References == 89f0993a082660e3c105c36aa08303d7e4bb3cea 4385 4383 2026-01-12T07:26:38Z Katea 309 Changed the page linked to for SLES wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Zypper_Screenshot_2026-01-12.png|400px|Thumb]] | caption = Zypper install screenshot | title = Zypper | releasestatus = Maintained | firstrelease = 2006-01-14 | lastrelease = 1.14.94, 2025-09-23 | languages = [[C++]] | developers = [[SUSE]], [[openSUSE]] | website = [https://en.opensuse.org/Portal:Zypper Portal:Zypper] }} [[Category:Package Managers]] Zypper is the primary [[Package Manager|package manager]] for [[SUSE Linux Enterprise|SUSE Linux Enterprise Server]], [[openSUSE|openSUSE]] and their derivatives. Zypper is a command-line interface to ZYpp System Management Library (libzypp) and uses [[rpm|RPM]] package archives <ref> [https://manpages.opensuse.org/Tumbleweed/zypper/zypper.8.en.html zypper(8)] openSUSE manpages, 2025-09-23 (Accessed: 2026-01-12) </ref> similar to [[Fedora|Fedora Linux]] and [[RHEL|Red Hat Enterprise Linux]]. Zypper is a binary package manager with support for x86, x86-64 (amd64), ARM, s390x and PowerPC. <ref> [https://get.opensuse.org/tumbleweed/?type=server#download openSUSE Tumbleweed] openSUSE Tumbleweed download page showing supported CPU Architectures (Accessed: 2026-01-12) </ref> == History == libZypp and by extension ZYpp and Zypper were released on January 14th 2006. <ref> [https://github.com/openSUSE/libzypp/blob/90acb93974a99bea7409516be55d6acdc35099f7/package/libzypp.changes libzypp Github] Earliest libzypp changelog (Accessed: 2026-01-12) </ref> In March of 2025 Zypper added experimental support for parallel downloads starting in libzypp version 17.36.4 and Zypper version 1.14.87. <ref> [https://news.opensuse.org/2025/03/27/zypper-adds-experimental-parallel-downloads/ openSUSE] Announcement of experimental parallel downloads support (Accessed: 2026-01-12) </ref> In May of 2025 parallel downloads were enabled by default starting in libzypp version 17.37.1 and Zypper version 1.14.90. <ref> [https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JR725AXWDZYLJ3PKIKYAYQQAXE6OWQMM/ openSUSE] Announcement of parallel downloads becoming the new default (Accessed: 2026-01-12) </ref> == Usage == Zypper uses an argument system for interacting with the package manager with its syntax being <code>zypper [ARGUMENT] [PACKAGE]</code> for example <code>zypper install vim</code>. There are 2 forms of each argument, full and abbreviated, this behavior is similar to [[DNF|DNF]] the Fedora/RHEL package manager. {| class="wikitable" |+Common Zypper Arguments !Full !Abbreviated !Description |- |<code>zypper install [TARGET]</code> |<code>zypper in [TARGET]</code> |Installs or updates a given package or pattern (use <code>-t</code> flag when installing patterns) |- |<code>zypper remove [TARGET]</code> |<code>zypper rm [TARGET]</code> |Uninstalls a given package |- |<code>zypper update</code> |<code>zypper up</code> |Upgrades the installed packages without removing packages (This is the preferred way to update a Leap or SLES system) |- |<code>zypper dist-upgrade</code> |<code>zypper dup</code> |Upgrades the installed packages while performing vendor changes, package removals and renames (This is the preferred way to update a Tumbleweed system) |- |<code>zypper refresh</code> |<code>zypper ref</code> |Refreshes the package repository mirrors (This is performed automatically is zypper detects an out of date repository when running install, remove, update, dist-upgrade or search commands) |- |<code>zypper search [SEARCH-TERM]</code> |<code>zypper se [SEARCH-TERM]</code> |Searches the enabled repositories for packages or patterns containing the search term entered |- |<code>dry-run</code> |<code>-D</code> |Runs the command being dry-ran without making any changes to the system |- |} == References == 460a72f6578c5aea597ef42d82ad60cf1209b851 4389 4385 2026-01-12T08:14:19Z Katea 309 Corrected "SUSE Linux Enterprise Server" to "SUSE Linux Enterprise" as SLE covers more than just Server wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Zypper_Screenshot_2026-01-12.png|400px|Thumb]] | caption = Zypper install screenshot | title = Zypper | releasestatus = Maintained | firstrelease = 2006-01-14 | lastrelease = 1.14.94, 2025-09-23 | languages = [[C++]] | developers = [[SUSE]], [[openSUSE]] | website = [https://en.opensuse.org/Portal:Zypper Portal:Zypper] }} [[Category:Package Managers]] Zypper is the primary [[Package Manager|package manager]] for [[SUSE Linux Enterprise|SUSE Linux Enterprise]], [[openSUSE|openSUSE]] and their derivatives. Zypper is a command-line interface to ZYpp System Management Library (libzypp) and uses [[rpm|RPM]] package archives <ref> [https://manpages.opensuse.org/Tumbleweed/zypper/zypper.8.en.html zypper(8)] openSUSE manpages, 2025-09-23 (Accessed: 2026-01-12) </ref> similar to [[Fedora|Fedora Linux]] and [[RHEL|Red Hat Enterprise Linux]]. Zypper is a binary package manager with support for x86, x86-64 (amd64), ARM, s390x and PowerPC. <ref> [https://get.opensuse.org/tumbleweed/?type=server#download openSUSE Tumbleweed] openSUSE Tumbleweed download page showing supported CPU Architectures (Accessed: 2026-01-12) </ref> == History == libZypp and by extension ZYpp and Zypper were released on January 14th 2006. <ref> [https://github.com/openSUSE/libzypp/blob/90acb93974a99bea7409516be55d6acdc35099f7/package/libzypp.changes libzypp Github] Earliest libzypp changelog (Accessed: 2026-01-12) </ref> In March of 2025 Zypper added experimental support for parallel downloads starting in libzypp version 17.36.4 and Zypper version 1.14.87. <ref> [https://news.opensuse.org/2025/03/27/zypper-adds-experimental-parallel-downloads/ openSUSE] Announcement of experimental parallel downloads support (Accessed: 2026-01-12) </ref> In May of 2025 parallel downloads were enabled by default starting in libzypp version 17.37.1 and Zypper version 1.14.90. <ref> [https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JR725AXWDZYLJ3PKIKYAYQQAXE6OWQMM/ openSUSE] Announcement of parallel downloads becoming the new default (Accessed: 2026-01-12) </ref> == Usage == Zypper uses an argument system for interacting with the package manager with its syntax being <code>zypper [ARGUMENT] [PACKAGE]</code> for example <code>zypper install vim</code>. There are 2 forms of each argument, full and abbreviated, this behavior is similar to [[DNF|DNF]] the Fedora/RHEL package manager. {| class="wikitable" |+Common Zypper Arguments !Full !Abbreviated !Description |- |<code>zypper install [TARGET]</code> |<code>zypper in [TARGET]</code> |Installs or updates a given package or pattern (use <code>-t</code> flag when installing patterns) |- |<code>zypper remove [TARGET]</code> |<code>zypper rm [TARGET]</code> |Uninstalls a given package |- |<code>zypper update</code> |<code>zypper up</code> |Upgrades the installed packages without removing packages (This is the preferred way to update a Leap or SLES system) |- |<code>zypper dist-upgrade</code> |<code>zypper dup</code> |Upgrades the installed packages while performing vendor changes, package removals and renames (This is the preferred way to update a Tumbleweed system) |- |<code>zypper refresh</code> |<code>zypper ref</code> |Refreshes the package repository mirrors (This is performed automatically is zypper detects an out of date repository when running install, remove, update, dist-upgrade or search commands) |- |<code>zypper search [SEARCH-TERM]</code> |<code>zypper se [SEARCH-TERM]</code> |Searches the enabled repositories for packages or patterns containing the search term entered |- |<code>dry-run</code> |<code>-D</code> |Runs the command being dry-ran without making any changes to the system |- |} == References == 7987499f04bd9a6877c48452ecbcfb5965fc8a83 6 1076 4380 2026-01-12T00:43:21Z Katea 309 Screenshot of the Nala frontend for APT installing Neovim, taken on Debian 13 in the GNOME Terminal wikitext text/x-wiki == Summary == Screenshot of the Nala frontend for APT installing Neovim, taken on Debian 13 in the GNOME Terminal == Licensing == {{CC0}} b8476f1073aa0a302a5b3a40f13be99aca6ae74a 0 1026 4381 4250 2026-01-12T00:50:41Z Katea 309 Added SoftwareInfobox with image and caption wikitext text/x-wiki {{stub}} [[Category:Software]] {{SoftwareInfobox |image = [[File:Debian_Nala.png|300px|center|thumb]] |caption = Nala install screenshot |title = Nala |releasestatus = Maintained |lastrelease = v0.16.0, 2025-04-21 |languages = [[Python]] |developers = [[https://github.com/volitank Volitank]] |website = [[https://github.com/volitank/nala Nala Github]] }} Nala is a front-end for [[apt]], the [[package manager]] used by [[Debian]]-based [[Linux Distributions|Linux distributions]] (abbreviated ‘distro’), designed to provide prettier output and speed up [[package]] installations with parallel downloads and optional mirrors to boost performance. As a front-end and not an independent package manager, it can only be used on systems with apt installed, and will install the same packages as apt. Nala requires at Debian 11/Bullseye or [[Ubuntu]] 19/Disco Dingo or newer, as older releases do not entail the required [[python]] versions. == Limitations == * Nala requires at Debian 11/Bullseye or Ubuntu 19/Disco Dingo or newer, older releases do not have required [[python]] versions available. * Nala limits parallel downloads connections to three per mirror. * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding or showing reverse dependencies. (Holding keeps a package at a certain version, reverse dependencies are packages that rely on a package.) == Usage == The following shows common Nala [[command]]s, which are mostly inherited from apt. Some commands can take multiple [[argument]]s, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of avaible packages and their versions |- |<code>nala upgrade</code> |Upgrades system's packages, installing any new ones if required |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages in the cache |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands |} 31eeae4f5f4464d04b1b22ed4cdc3c017488e84f 0 279 4384 4234 2026-01-12T07:12:49Z Katea 309 Added missing aarch64 and s390x architectures to the SoftwareInfobox, as well as changed their spelling to match how they're labelled on the openSUSE website wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] or [[transactional-update]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]] | usagetype = Desktop, Server | architectures = i686, x86-64, aarch64, ppc64le, s390x | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == This distribution stands out by having two primary variations of the distribution: * '''OpenSUSE Tumbleweed''' is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. * '''OpenSUSE Leap''' is the point release version, with a new release every year with older and more stable packages meant for business use. === openSUSE Slowroll === Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === openSUSE Kalpa === Kalpa is an experimental version of openSUSE, spun off of the now discontinued openSUSE MicroOS Desktop project. It's goal is to be easy to use, increase stability (compared to openSUSE Tumbleweed) and === openSUSE MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === openSUSE Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed 93b641f4caa75521bc274f7d2580e7342427f789 4396 4384 2026-01-14T09:30:08Z Katea 309 Added IceWM to the default desktop environments as Tumbleweed automatically installs it as a fallback WM if you use the YaST installer wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] or [[transactional-update]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[IceWM]] | usagetype = Desktop, Server | architectures = i686, x86-64, aarch64, ppc64le, s390x | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE is a [[Linux Distributions|Linux distribution]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == This distribution stands out by having two primary variations of the distribution: * '''OpenSUSE Tumbleweed''' is the de facto "unstable" release of the distribution, having a rolling release model therefore having newer packages. * '''OpenSUSE Leap''' is the point release version, with a new release every year with older and more stable packages meant for business use. === openSUSE Slowroll === Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === openSUSE Kalpa === Kalpa is an experimental version of openSUSE, spun off of the now discontinued openSUSE MicroOS Desktop project. It's goal is to be easy to use, increase stability (compared to openSUSE Tumbleweed) and === openSUSE MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === openSUSE Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed d9d03499927b630d3fb4f2c114355da9b68b8afe 6 1077 4386 2026-01-12T07:46:27Z Katea 309 The jpeg "SUSE Secondary Logo" sourced directly from https://brandfolder.com/suse/logo-kit (there is no SVG on an eps file so I had to use the jpeg) wikitext text/x-wiki == Summary == The jpeg "SUSE Secondary Logo" sourced directly from https://brandfolder.com/suse/logo-kit (there is no SVG on an eps file so I had to use the jpeg) == Licensing == {{Unknown_copyright}} f3183d80b290b2b9bc94a7f7ce15a593de668148 6 1078 4387 2026-01-12T08:03:08Z Katea 309 The jpeg sourced directly from https://brandfolder.com/suse/logo-kit It is the primary logo of SUSE. wikitext text/x-wiki == Summary == The jpeg sourced directly from https://brandfolder.com/suse/logo-kit It is the primary logo of SUSE. == Licensing == {{Unknown_copyright}} 4abb22af82ed70ea1a5e04947dc7dd564737b321 0 1079 4388 2026-01-12T08:11:21Z Katea 309 Added brief information and DistributionInfobox to SUSE Linux Enterprise, this needs expanding wikitext text/x-wiki {{Stub}} {{DistributionInfobox |title = SUSE Linux Enterprise (SLE) |image = [[File:SUSE_Logo_Primary.jpeg|350px| SUSE Secordary Logo]] |caption = The official SUSE logo |releasestatus = Maintained |releasemodel = Stable |packagemanager = [[Zypper]] |defaultdesktops = [[GNOME]], [[Plasma]] |usagetype = Server |architectures = x86-64, ppc64le, aarch64, s390x |website = [[https://www.suse.com/ suse.com]] }} [[Category:Linux Distributions]] '''SUSE Linux Enterprise (SLE)''' is a set of commercial server-focused [[Linux Distributions]] developed by the German software development company [[SUSE]] af49930d4553af8682f4af219558fab90fbba123 4390 4388 2026-01-12T08:16:26Z Katea 309 added {{Needs Citations}} wikitext text/x-wiki {{Stub}} {{Needs Citations}} {{DistributionInfobox |title = SUSE Linux Enterprise (SLE) |image = [[File:SUSE_Logo_Primary.jpeg|350px| SUSE Secordary Logo]] |caption = The official SUSE logo |releasestatus = Maintained |releasemodel = Stable |packagemanager = [[Zypper]] |defaultdesktops = [[GNOME]], [[Plasma]] |usagetype = Server |architectures = x86-64, ppc64le, aarch64, s390x |website = [[https://www.suse.com/ suse.com]] }} [[Category:Linux Distributions]] '''SUSE Linux Enterprise (SLE)''' is a set of commercial server-focused [[Linux Distributions]] developed by the German software development company [[SUSE]] 73fe781e46c77e40517818976a0e50921eb1a1e7 0 169 4391 4271 2026-01-12T12:36:57Z Katea 309 Corrected link to SUSE Linux Enterprise page in Zypper's "Used by" section wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to handle [[package]]s, [[software]] delivered in specific formats. Regular functions include [[install]]ing, removing, updating, and searching packages, usually from a package [[repository]]. === List of Package Managers === Note: The ''Used By'' field also implies [[derivative]]s, which are listed in the [[Linux Distributions]] page. There are exceptions to this rule, specifically cross-distribution package managers such as [[snap]], [[nix]] and [[flatpak]]. For a list of package formats, see the [[package]] page. {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[Shell]]|| [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |} == References == <references /> 5712cf7fb879b433421fd11d0261687e806e5d43 4 340 4392 3068 2026-01-12T16:41:15Z Atmois 13 Fix subheading level wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page, and all changes MUST be approved by staff for public viewing via ApprovedRevs. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 33e1d2e0dea20a5e87248eddd9404849cf191223 4393 4392 2026-01-12T16:42:06Z Atmois 13 Remove outdated info wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; atl.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://atl.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code><nowiki>https://atl.wiki/edit/PageTitle</nowiki></code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''atl.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] b3fcad67b83ba2aea5f18f713b317456c4c6f009 3000 572 4394 3055 2026-01-12T16:43:14Z Atmois 13 remove outdated information wikitext text/x-wiki == TL;DR == Ensure you have the '''[[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]]''' template on the page, and all changes MUST be approved by staff for public viewing via <code>ApprovedRevs</code>. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Definition == Guides are '''''anything that explain to a user how to do something beyond a link to another source or a brief instruction'''''. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide on hardening Firefox with more privacy focused options, a higher standard of quality and safety than standard articles SHOULD be maintained for guides. This is because unlike normal articles that only provide factual information, guides contain instructions for users to do things to their systems, which could potentially damage the systems or cause data loss. == Policies == All main wiki policies apply, including but not limited to the [[ATL:Code of Conduct|Code of Conduct]] and the wiki [[ATL:Guidelines|guidelines]]. We also recommend you check out our [[ATL:Contributing|Contributing page]] as well, which has a lot of important and useful information for editors. In addition, a special set of criteria are required, as outlined below: * All guides MUST ''start'' with [[Template:Guide Warning]]. ** There are no exceptions to this rule, and violations of the rule entail all edits to be rejected until the template's addition. ** Add it using <code><nowiki>{{GuideWarning}}</nowiki></code> or <code><nowiki>{{Guide Warning}}</nowiki></code> at the beginning of the page: ** {{Guide Warning}} * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this: ** Double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. ** Aim to provide unbiased and informative content to all users. Your personal views, regardless of validity, are irrelevant here. * You are responsible for ensuring all instructions you provide are safe and functional. ** In guides, any foreseeable risks with running a specific command MUST be clearly stated. ** Ensure to clearly outline, if any, the requirements and prerequisites of the commands. ** Any dangerous commands provided will be held accountable to whomever adds them to a guide. A good example guide would be '''[[Guides:Setting up Flathub on Fedora]]''', which is maintained and has been made in accordance with our guidelines and standards. 9c8fce24539fe0d8909f5362b2510c947ad2f7d4 0 622 4395 4286 2026-01-13T15:43:27Z Ivanovics 150 Add LXQt to the gallery wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:COSMIC Epoch 1.0.0 alpha with apps.png|[[COSMIC]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity Desktop Environment]] File:XFCE-4.18-Desktop.png|[[XFCE]] File:LXDE-Qt preview.png|[[LXDE]] File:LXQt 2.0.0 Ambiance screenshot.png|[[LXQt]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[COSMIC]] |[[COSMIC]] is a GNOME-based Desktop Environment developed by [[system76]], also known as the creators of [[Pop! OS|Pop! OS.]] COSMIC is built in [[Rust]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} bceaffea714e6378df135abd20dcd138586e2c1b 6 1080 4397 2026-01-15T04:34:44Z Madonuko 140 Logo of Fcitx5 wikitext text/x-wiki == Summary == Logo of Fcitx5 == Licensing == {{LGPL}} 49b8c270a156598ddd890b836ca55350ef62a1e5 0 1081 4398 2026-01-15T07:48:26Z Madonuko 140 init wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fcitx5.svg|frameless]] | caption = The Fcitx logo | title = Fcitx | releasestatus = Maintained | lastrelease = 5.1.12 (2025-01-23) | languages = [[C++]], [[C]] | developers = Fcitx Developers | website = https://fcitx-im.org/wiki/Fcitx_5 }} '''Fcitx 5''' (or usually '''fcitx5''') is a [[Qt]]-based [[input method framework]] (IMF). It is a successor to [[Fcitx]], and is consistently the second most popular IMF following [[IBus]] according to statistics from [[Arch Linux]].<ref>[https://pkgstats.archlinux.de/compare/packages#packages=fcitx,fcitx5,gcin,hime,ibus,nimf,scim,uim Compare Packages], Arch Linux (Accessed: 2026-01-15)</ref> Unlike IBus, Fcitx 5 comes with more advanced features, including addons and themes.<ref>[https://fcitx-im.org/wiki/Addon_Type Addon Type], Fcitx, 2016-02-02 (Accessed: 2026-01-15)</ref><ref>[https://fcitx-im.org/wiki/Theme_Customization Theme Customization], Fcitx, 2022-02-09 (Accessed: 2026-01-15)</ref> == Installation == Fcitx 5 has support for [[UNIX]]-based systems. <code>fcitx-contrib</code> provides support for [[macOS]] [https://github.com/fcitx-contrib/fcitx5-macos], [[iOS]] [https://github.com/fcitx-contrib/fcitx5-ios], [[HarmonyOS]] [https://github.com/fcitx-contrib/fcitx5-harmony], [[ChromeOS]] [https://github.com/fcitx-contrib/fcitx5-chrome], and [[Windows]] [https://github.com/fcitx-contrib/fcitx5-windows]. It can also be tested in an Internet browser [https://fcitx-contrib.github.io/online/index.html]. [[Android]] support is provided by [https://github.com/fcitx5-android/fcitx5-android <code>fcitx5-android</code>]. On [[operating system]]s with [[package manager]]s, usually the name of the package is <code>fcitx5</code>. Some distributions do not ship it with out-of-box support for GTK and Qt. [[KDE Plasma]] users should install the [[KCM]] module, which provides a dedicated page in system settings for configuring Fcitx5. Other users should install <code>fcitx5-configtool</code>. {| class="wikitable" style="text-align:center;" |+ Subpackage Names for Distributions ! Distribution !! GTK3 !! GTK4 !! Qt5 !! Qt6 !! KCM |- | [[Arch]]<ref>[https://wiki.archlinux.org/title/Fcitx5 Fcitx5], ArchWiki, 2026-01-13 (Accessed: 2026-01-15)</ref> || colspan=2 rowspan=2 | <code>fcitx5-gtk</code> || colspan=2 rowspan=2 | <code>fcitx5-qt</code> || rowspan=2 | <code>kcm-fcitx5</code> |- | [[Fedora]] |- | [[Debian]]<ref>[https://wiki.debian.org/I18n/Fcitx5#Install_Fcitx5_on_bullseye Fcitx5], Debian Wiki, 2025-08-10 (Accessed: 2026-01-15)</ref> || colspan=4 | <code>fcitx5-frontend-{gtk3,gtk4,qt5,qt6}</code> || <code>kde-config-fcitx5</code> |- |} == Usage == {{Guide Warning}} The official Fcitx 5 Wiki contains instructions and suggestions on ideal set ups.<ref>[https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#Support_in_Wayland_Compositor Using Fcitx 5 on Wayland], Fcitx, 2024-06-14 (Accessed: 2026-01-15)</ref> It mentions a new set up method for KDE Plasma, requires setting ''Fcitx 5 Wayland Launcher'' in ''System Settings'' → ''Input/Output Devices'' → ''Keyboard'' → ''Virtual Keyboard''. For other environments and for the old method for KDE Plasma, it is required to create an autostart setup with the following system-wide [[environment variable]]s: {{FileBox|title=/etc/environment|lang=sh|content= export INPUT_METHOD=fcitx export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx }} Autostart can be enabled via the <code>fcitx5-autostart</code> package on Fedora (which also provides the required environment variables), or by copying the given autostart [[desktop entry]] into the autostart folder: <syntaxhighlight lang="bash"> mkdir -p ~/.config/autostart cp /usr/share/applications/org.fcitx.Fcitx5.desktop ~/.config/autostart </syntaxhighlight> == Input Method List == See [[Guides:Input method#List of IMs to IMEs]] == Troubleshooting == === Cannot Detect in Electron Applications === In some cases where [[Electron]]/[[Chromium]] is executed under [[Wayland]], Fcitx 5 would not be detected. Follow the instructions [https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#Chromium_/_Electron here] to fix the issue. On KDE Plasma, in the application menu, right click on the application and click edit, then add e.g. <code>--enable-features=UseOzonePlatform --enable-features=WebRTCPipeWireCapturer --ozone-platform=wayland --enable-wayland-ime --ozone-platform-hint=auto</code> as the command-line arguments. === Cannot Detect in MuseScore === MuseScore 4 does not support Fcitx 5 under the new Wayland setup on KDE Plasma.<ref>[https://musescore.org/en/node/371132 Japanese Input not working in Linux Mint 22, Musescore 4], dadasabi, 2024-11-02 (Accessed: 2026-01-15)</ref> Use the old method mentioned above with ''Fcitx 5'' set as the virtual keyboard. == See Also == * [https://wiki.archlinux.org/title/Fcitx5 Fcitx5 on ArchWiki] == References == 1c066b8bb556ae6b80a5faafc7e4def6dcaf1c43 0 810 4399 3277 2026-01-15T18:24:56Z Ivanovics 150 Some configuration and usage stuff wikitext text/x-wiki '''OpenRC''' is a dependency-based [[Init System|init system]] made in [[C]] and [[Shell]] for Unix-like [[Operating System|Operating Systems]]. Created by [[NetBSD]] developer and ex-maintainer of the [[Gentoo]] Project.<ref>Wikipedia, The Free Encyclopedia: https://en.wikipedia.org/wiki/OpenRC (Accessed Aug 5th, 2025)</ref> Due to OpenRC being made from C and POSIX-Compliant Shell, it is portable between [[Linux]], [[FreeBSD]], and NetBSD. It can optionally be used as an init system or as a [[Process Supervisor|process supervisor]]. = Overview = OpenRC is a default init system and/or process supervisor on many [[Linux Distributions]] due to its lightweight and compatibility properties. The init system is made of several modular components allowing full-scale customization in terms of what the process actual does for being an init system or as a daemon supervisor. = Configuration = ==Files== OpenRC uses <code>/etc/rc.conf</code> for its global configuration Individual initscripts store their configuration in <code>/etc/conf.d</code> ==Logging== By default OpenRC doesn't create logs, however logging can be enabled to log output during the boot process {{FileBox | title = /etc/rc.conf | content = rc_logger="YES" rc_log_path="/var/log/rc.log" #Can be used to set a custom log file for OpenRC }} =Usage= ==Runlevels== OpenRC can be controlled and configured using '''openrc''', '''rc-update''' and '''rc-status''' commands. Delete docker from runlevel "default": <code># rc-update delete docker default</code> ==Listing== It is possible to list runlevels and their assigned initscripts (services) without needing root permission, by running <code>rc-update show -v</code> By default (without the -v flag) rc-update will only show the initscripts that have been assigned to a runlevel Alternatively, the same can be achieved with rc-status: <code>rc-status --servicelist</code> ==Adding named runlevels== OpenRC implements runlevels as directories that are stored in '''/etc/runlevels''' and additional runlevels can be created by running: <code># install -d /etc/runlevels/<runlevel></code> Where <runlevel> is the placeholder for the name Additional runlevels can be helpful in providing alternative system profiles during bootup 78cde5eab39cf1cfcc20b055764373ee5d98a07d 0 177 4400 4296 2026-01-17T14:51:50Z Fleetoise 190 Described the authorities that define open source and free software, and improved the definition of non-free software wikitext text/x-wiki [[Category:Terminology]] '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word libre, meaning "free") and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, distribute and sell the software, modified or not, to everyone. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. The most accepted definition of Open Source is maintained by The Open Source Initiative, and is called "Open Source Definition"(OSD). The OSD was originally derived from the Debian Free Software Guidelines (DFSG)<ref>https://opensource.org/osd</ref>. The Free Software Foundation maintains the accepted definition of Free Software<ref>https://www.gnu.org/philosophy/free-sw.html</ref>. FOSS is in contrast to proprietary, or nonfree software, where the software is under restrictive licensing. This includes source available software that does not allow redistribution or sale of the source or the program. === Notes === ----FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == 624cc09a6ef8ebb253f9df57d58b846b1c11936f 4401 4400 2026-01-17T15:59:46Z Fleetoise 190 Expanded the explanation of non-free software wikitext text/x-wiki [[Category:Terminology]] '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word libre, meaning "free") and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, distribute and sell the software, modified or not, to everyone. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. The most accepted definition of Open Source is maintained by The Open Source Initiative, and is called "Open Source Definition"(OSD). The OSD was originally derived from the Debian Free Software Guidelines (DFSG)<ref>https://opensource.org/osd</ref>. The Free Software Foundation maintains the accepted definition of Free Software<ref>https://www.gnu.org/philosophy/free-sw.html</ref>. Proprietary, or nonfree software, is in contrast under restrictive licensing that goes against the user rights outlined in FOSS definitions, such as disallowing redistribution, sale, modification, or usage of the [[Source Code|source]] or [[Binary|binaries]] by a specific group, or requiring payment of money to exercise the rights mentioned. This includes source available software if it is subject to the restrictions mentioned, such as Unreal Engine, which requires payment of royalties for certain redistributions of the source<ref><nowiki>https://www.unrealengine.com/en-US/eula/unreal</nowiki></ref>. === Notes === ----FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == efec371d95e2857a000357d9a3f0dfa9bab2e4bc 4402 4401 2026-01-17T16:02:45Z Fleetoise 190 Minor fix of wording wikitext text/x-wiki [[Category:Terminology]] '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word libre, meaning "free") and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, distribute and sell the software, modified or not, to everyone. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. The most accepted definition of Open Source is maintained by The Open Source Initiative, and is called "Open Source Definition"(OSD). The OSD was originally derived from the Debian Free Software Guidelines (DFSG)<ref>https://opensource.org/osd</ref>. The Free Software Foundation maintains the accepted definition of Free Software<ref>https://www.gnu.org/philosophy/free-sw.html</ref>. Proprietary, or nonfree software, is in contrast under restrictive licensing that goes against the user rights outlined in FOSS definitions, such as disallowing redistribution, sale, modification, or usage of the [[Source Code|source]] or [[Binary|binaries]] by a specific group, or requiring payment of money to exercise the rights mentioned. This includes source available software if it is subject to such restrictions, such as Unreal Engine, which requires payment of royalties for certain redistributions of the source<ref><nowiki>https://www.unrealengine.com/en-US/eula/unreal</nowiki></ref>. === Notes === ----FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == 58f00abf405047bc16297ea5996fdcb2ab92c5f9 4403 4402 2026-01-17T18:17:32Z Fleetoise 190 Fixing wording wikitext text/x-wiki [[Category:Terminology]] '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word libre, meaning "free") and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, distribute and sell the software, modified or not, to everyone. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. The most accepted definition of Open Source is maintained by The Open Source Initiative, and is called "Open Source Definition"(OSD). The OSD was originally derived from the Debian Free Software Guidelines (DFSG)<ref>https://opensource.org/osd</ref>. The Free Software Foundation maintains the accepted definition of Free Software<ref>https://www.gnu.org/philosophy/free-sw.html</ref>. Proprietary, or nonfree software, is in contrast under restrictive licensing that goes against the user rights outlined in FOSS definitions, such as disallowing redistribution, sale, modification, or usage of the [[Source Code|source]] or [[Binary|binaries]] by a specific group, or requiring payment of money to exercise the rights mentioned. This includes source available software if it is subject to such restrictions, such as Unreal Engine, which requires payment of royalties for the distribution of certain binaries if the source includes Unreal Engine code<ref><nowiki>https://www.unrealengine.com/en-US/eula/unreal</nowiki></ref>. === Notes === ----FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == 022cc1b4f4e9dceabb2327d054c941641b9c9d4c 4404 4403 2026-01-17T19:32:39Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Terminology]] '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word libre, meaning "free") and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, distribute and sell the software, modified or not, to everyone. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. The most accepted definition of Open Source is maintained by The Open Source Initiative, and is called "Open Source Definition"(OSD). The OSD was originally derived from the Debian Free Software Guidelines (DFSG)<ref>[https://opensource.org/osd The Open Source Definition], Open Source Initiative, 2007-03-22 (Accessed: 2026-01-18)</ref>. The Free Software Foundation maintains the accepted definition of Free Software<ref>[https://www.gnu.org/philosophy/free-sw.html What is Free Software?], GNU Project, 2025-12-28 (Accessed: 2026-01-18)</ref>. Proprietary, or nonfree software, is in contrast under restrictive licensing that goes against the user rights outlined in FOSS definitions, such as disallowing redistribution, sale, modification, or usage of the [[Source Code|source]] or [[Binary|binaries]] by a specific group, or requiring payment of money to exercise the rights mentioned. This includes source available software if it is subject to such restrictions, such as Unreal Engine, which requires payment of royalties for the distribution of certain binaries if the source includes Unreal Engine code<ref><nowiki>https://www.unrealengine.com/en-US/eula/unreal</nowiki></ref>. === Notes === ----FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == 1485816a854146db5228fd80c6ac049566042e05 0 586 4405 3820 2026-01-19T10:06:13Z TImesChu 310 Corrected "spurned" to "spurred." Spurned = Offended/Denied. Spurred = Incentivized/Inspired wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox | title = Xenia (Linux Fox) | image = [[File:Xenia the Linux Fox.gif]] | caption = The original design of Linux Fox, created by Al Mackey in 1996 }} Xenia was a candidate logo and [[:Category:Mascots|mascot]] for the [[Linux]] project. She was a competitor to [[Tux]], who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds)<ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ Why the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!]{{Dead Link|2025-08-22|429}}, Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson.<ref>[https://archive.is/wYsFh Penguins and Other Things]{{Dead Link|2025-08-22|429}}, Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurred many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on [[Gentoo]].<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> == References == <references /> 14234af25ded65b8150efdcbc1308f89aaa0f33d 0 1082 4406 2026-01-21T15:15:57Z SOSMAN64 313 made distrobox page with some basic stuff (first time ever making a wiki edit please have mercy) wikitext text/x-wiki '''Distrobox''' is a wrapper around [[Docker]], [[Podman]] or [[Lilipod]] which aims to make creating [[containers]] on Linux distributions faster and easier. Said containers integrate deeply with the home system (e.g. accessing the home directory or playing audio) allowing users to reap the benefits of other Linux distributions without sacrificing the benefits of their current ones.<ref>{{Cite|url=https://distrobox.it/|title=Distrobox Page|accessdate=2026-01-21}}</ref> == Installation == Distrobox is available on several distributions' [[Package Manager|package managers]] (including [[Arch Linux]] and [[Fedora]])<ref>{{Cite|url=https://repology.org/project/distrobox/versions|title=Distrobox on Repology|accessdate=2026-01-21}}</ref> otherwise installation is as simple as installing Docker,Podman or Lilipod then doing one of the following: # Running a curl or wget [https://distrobox.it/#curl-or-wget command] # Cloning the [https://distrobox.it/#git project] using [[git]]<ref>{{Cite|url=https://distrobox.it/#installation|title=Distrobox Page - Installation Section|accessdate=2026-01-21}}</ref> == Examples Usage == One could create an [[Alpine Linux|Alpine]] container through the following command:<syntaxhighlight lang="bash"> distrobox create --image alpine my-alpine-container </syntaxhighlight>It can then be accessed by executing the following:<syntaxhighlight lang="bash"> distrobox-enter my-alpine-container </syntaxhighlight>After running the command, You will be greeted with a shell within that container allowing you to execute Alpine commands and most importantly,access its package manager. == References == <references /> 0f91535b1b4cc53636a23c3d9f7a6eb24e8d9125 4407 4406 2026-01-21T15:16:34Z SOSMAN64 313 changed home to host because it makes more sense wikitext text/x-wiki '''Distrobox''' is a wrapper around [[Docker]], [[Podman]] or [[Lilipod]] which aims to make creating [[containers]] on Linux distributions faster and easier. Said containers integrate deeply with the host system (e.g. accessing the home directory or playing audio) allowing users to reap the benefits of other Linux distributions without sacrificing the benefits of their current ones.<ref>{{Cite|url=https://distrobox.it/|title=Distrobox Page|accessdate=2026-01-21}}</ref> == Installation == Distrobox is available on several distributions' [[Package Manager|package managers]] (including [[Arch Linux]] and [[Fedora]])<ref>{{Cite|url=https://repology.org/project/distrobox/versions|title=Distrobox on Repology|accessdate=2026-01-21}}</ref> otherwise installation is as simple as installing Docker,Podman or Lilipod then doing one of the following: # Running a curl or wget [https://distrobox.it/#curl-or-wget command] # Cloning the [https://distrobox.it/#git project] using [[git]]<ref>{{Cite|url=https://distrobox.it/#installation|title=Distrobox Page - Installation Section|accessdate=2026-01-21}}</ref> == Examples Usage == One could create an [[Alpine Linux|Alpine]] container through the following command:<syntaxhighlight lang="bash"> distrobox create --image alpine my-alpine-container </syntaxhighlight>It can then be accessed by executing the following:<syntaxhighlight lang="bash"> distrobox-enter my-alpine-container </syntaxhighlight>After running the command, You will be greeted with a shell within that container allowing you to execute Alpine commands and most importantly,access its package manager. == References == <references /> 65f54a4f0082822baa1de762814a211cd7f37dff 4408 4407 2026-01-21T15:17:14Z SOSMAN64 313 fixed grammatical mistake (fucking kill me) wikitext text/x-wiki '''Distrobox''' is a wrapper around [[Docker]], [[Podman]] or [[Lilipod]] which aims to make creating [[containers]] on Linux distributions faster and easier. Said containers integrate deeply with the host system (e.g. accessing the home directory or playing audio) allowing users to reap the benefits of other Linux distributions without sacrificing the benefits of their current ones.<ref>{{Cite|url=https://distrobox.it/|title=Distrobox Page|accessdate=2026-01-21}}</ref> == Installation == Distrobox is available on several distributions' [[Package Manager|package managers]] (including [[Arch Linux]] and [[Fedora]])<ref>{{Cite|url=https://repology.org/project/distrobox/versions|title=Distrobox on Repology|accessdate=2026-01-21}}</ref> otherwise installation is as simple as installing Docker,Podman or Lilipod then doing one of the following: # Running a curl or wget [https://distrobox.it/#curl-or-wget command] # Cloning the [https://distrobox.it/#git project] using [[git]]<ref>{{Cite|url=https://distrobox.it/#installation|title=Distrobox Page - Installation Section|accessdate=2026-01-21}}</ref> == Example Usage == One could create an [[Alpine Linux|Alpine]] container through the following command:<syntaxhighlight lang="bash"> distrobox create --image alpine my-alpine-container </syntaxhighlight>It can then be accessed by executing the following:<syntaxhighlight lang="bash"> distrobox-enter my-alpine-container </syntaxhighlight>After running the command, You will be greeted with a shell within that container allowing you to execute Alpine commands and most importantly,access its package manager. == References == <references /> c3634a78293edbd8b2b2889d28a9ce0a616c2ee4 0 625 4409 3751 2026-01-22T04:48:10Z Tungnon1222 314 wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[EXT4]] * [[ZFS]] * [[XFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[XFCE|Xfce]] (preconfigured) * [[GNOME]] * [[Budgie]] * [[Cinnamon]] * [[COSMIC]] * [[LXDE]] * [[LXQt]] * [[Mate]] * [[UKUI]] Only KDE Plasma and XFCE come with preconfigured. Other Desktop Environments come as their default states. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] CachyOS also ships with [[Noctalia Shell]] by default alongside [[niri]]. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 9629435048c9f7321d4be3e09f83d7d192ebc0e4 0 1083 4410 2026-01-23T20:43:03Z Madonuko 140 #REDIRECT [[Fcitx 5]] wikitext text/x-wiki #REDIRECT [[Fcitx 5]] 76565fd61b6a04eae41945b751b92ed4d9515f69 3000 608 4411 4304 2026-01-23T20:48:31Z Madonuko 140 /* List of IMs to IMEs */ wikitext text/x-wiki {{GuideWarning}} Welcome to the Input method guide! There are a few things you need to be aware of: * Not all packages are available on your distribution. For an input method editor/framework to be available, the package for it needs to be packaged by your distribution maintainers. Otherwise, you will need to compile them yourself. * Just like most things in the Linux ecosystem, you have the freedom to choose your input method framework/editors. Even though this is a "guide", we do not recommend any specific software. * If you are just looking for a quick solution, you should instead look for distribution-specific wiki pages, e.g. [https://wiki.archlinux.org/title/Input_method ArchWiki], [https://wiki.ultramarine-linux.org/en/usage/l10n/#inputting-in-another-language Ultramarine Wiki]. == Definitions == === Input Method Framework (IMF) === '''Input Method Frameworks (IMFs)''' are software that enable users to type in numerous different input methods. They provide a unified experience and user interface between IMEs and the DE/WM.<ref name=":0">[https://wiki.ultramarine-linux.org/en/usage/l10n/#imfs-imes-and-ims Localization, Internationalization and Multilingualization], Ultramarine Linux, 2024 (Accessed: 2025-05-03)</ref> Users can use the IMF to switch between different IMEs.<ref>[https://wiki.archlinux.org/title/Input_method Input method], ArchWiki, 2020 (Accessed: 2025-05-03)</ref> The most common IMFs are [[IBus]] and [[Fcitx5]]. '''IBus''' (Intelligent Input Bus) is an IMF usually used in GTK-based desktop environments. If you are using GNOME/Budgie, you most likely will choose IBus over Fcitx5 due to GNOME Desktop’s tight integration with IBus. Even though IBus’s initial release was back in August 2008, releases are still rather frequent and the project is still being maintained.<ref>[[wikipedia:Intelligent_Input_Bus|Intelligent_Input_Bus]], Wikipedia, 2009 (Accessed: 2025-05-03)</ref> '''Fcitx5''' is a newer IMF implementation and provides support for many different languages with a slim core extensible with different addons and IMEs. It is the successor to '''Fcitx'''.<ref>[[wikipedia:Fcitx|Fcitx]], Wikipedia, 2010 (Accessed: 2025-05-03)</ref> If you are using DEs that are not GTK-based (such as KDE Plasma which uses Qt) or any WMs, you should choose Fcitx5.<ref name=":0" /> Other IMFs include '''Scim''' (Smart Common Input Method), and '''uim''' (universal input method)'''.''' While in most cases you may choose any IMFs, there is one exception: IBus does not work inside [[window managers]]. If you don't know what a WM is, ignore this warning. You can use Fcitx as an IME in Scim via <code>scim-fcitx</code>. Similarly, you can use uim as an IME in Scim via <code>scim-uim</code> === Input Method Engine (IME) === '''Input Method Editors (IMEs)''' are software that convert user inputs into actual texts in different languages. === Input Method (IM) === '''Input Methods (IMs)''' refer to the actual conversion between the input keys and the output text. IMs are not actual software; there must be an IME that intercepts inputs and map them into output texts, where the mapping is specified by the IM. == Setting up IMFs == === IBus === Run <code>ibus-setup</code>. Alternatively, go to your desktop settings and find the input method settings page. (e.g. On GNOME and Budgie: Settings > Keyboard) Note that on Pantheon, you must use the desktop settings applet. If your distribution uses [[IMSettings]], run <code>im-chooser</code>. Otherwise, edit <code>/etc/environment</code>: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Alternatively you may make this only apply to the current user by saving this in <code>~/.config/environment.d/*.conf</code>. === Fcitx5 === Install <code>fcitx5-configtool</code>. On KDE Plasma you should install <code>kcm-fcitx5</code> and go to ''System Settings > Regional Settings > Input Method''. (On some versions of Plasma, ''Regional Settings'' is shown as ''Language and Time''.) Depending on the distribution (e.g. Fedora) you should also install <code>fcitx5-gtk</code> and <code>fcitx5-qt</code>. To enable autostart: * On Plasma (Wayland), go to ''System Settings > Input Devices > Virtual Keyboard'' and select ''Fcitx 5''. * Otherwise, install <code>fcitx5-autostart</code>. If this package is not available, create an autostart entry manually at <code>/etc/xdg/autostart/org.fcitx.Fcitx5.desktop</code>:<syntaxhighlight lang="ini"> [Desktop Entry] Name=Fcitx 5 GenericName=Input Method Comment=Start Input Method Exec=/usr/bin/fcitx5 Icon=fcitx Terminal=false Type=Application Categories=System;Utility; StartupNotify=false X-GNOME-AutoRestart=false X-GNOME-Autostart-Notify=false X-KDE-autostart-after=panel X-KDE-StartupNotify=false X-KDE-Wayland-VirtualKeyboard=true X-KDE-Wayland-Interfaces=org_kde_plasma_window_management</syntaxhighlight> * If none of the above worked, edit <code>/etc/environment</code> and reboot: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx * The [https://wiki.gentoo.org/wiki/How_to_read_and_write_in_Chinese#Launching_the_fcitx_daemon_at_login_time Gentoo Wiki] suggests editing <code>~/.xprofile</code> instead with: export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx export SDL_IM_MODULE=fcitx export GLFW_IM_MODULE=fcitx export INPUT_MODULE=fcitx == List of IMs to IMEs == {| class="wikitable" style="text-align:center;" ! style="background:var(--background-color-neutral,#eaecf0);color:inherit;background:linear-gradient(to top right,var(--background-color-neutral,#eaecf0) 49%,var(--border-color-base,#a2a9b1) 49.5%,var(--border-color-base,#a2a9b1) 50.5%,var(--background-color-neutral,#eaecf0) 51%);line-height:1.2;padding:0.1em 0.4em;"|<div style="margin-left:2em;text-align:right">IMF</div><div style="margin-right:2em;text-align:left">IME</div> ![[Fcitx5]] ![[Fcitx]] ![[IBus]] ![[Uim]] ![[Emacs]] ![[Scim]] !Hime ![[Gcin]] ![[Nimf]] |- ! colspan="10" |Chinese |- |[[Rime]] |<code>fcitx5-rime</code> |<code>fcitx-rime</code> |<code>ibus-rime</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Pinyin|Pinyin]] |<code>fcitx5-chinese-addon</code> |''built-in'' |<code>ibus-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-pinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |Zhuyin |<code>fcitx5-chewing</code> |<code>fcitx-chewing</code> |<code>ibus-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-chewing</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- |[[W:Cangjie input method|Cangjie]] Sucheng SmartCangjie |<code>fcitx5-table-extra</code><ref name=":0" group="Note">Additionally requires <code>fcitx5-chinese-addon</code> on Fedora due to packaging issues.</ref> |<code>fcitx-table-extra</code> |<code>ibus-table-chinese-cangjie</code><ref group=Note name=N1>On Fedora, this is split into <code>ibus-table-chinese-cangjie</code>, <code>ibus-table-chinese-quick</code> and <code>ibus-table-chinese-scj</code>.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>scim-tables</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Jidian Wubi | rowspan="2" |''built-in'' | rowspan="2" |''built-in'' |<code>ibus-table-chinese-wubi-jidian</code> | rowspan="2" |''built-in'' | rowspan="2" |- | rowspan="2" |<code>scim-tables</code> | rowspan="2" |- | rowspan="2" |- | rowspan="2" |- |- |Haifeng Wubi |<code>ibus-table-chinese-wubi-heifeng</code> |- |Libpinyin |<nowiki>-</nowiki> |<code>fcitx-libpinyin</code> |<code>ibus-libpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |SunPinyin |<nowiki>-</nowiki> |<code>fcitx-sunpinyin</code> |<code>ibus-sunpinyin</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Others |<code>fcitx5-table-extra</code><ref name=":0" group="Note" />? |<code>fcitx-table-extra</code>? |<code>ibus-table-chinese</code>? | - | - | - | - | - | - |- ! colspan="10" |Japanese |- |[[Mozc]] |<code>fcitx5-mozc</code><ref group="Note"><code>fcitx5-mozc-ut</code>^AUR is instead recommended on Arch Linux.</ref> |<code>fcitx-mozc</code><ref group="Note"><code>fcitx-mozc-ut</code>^AUR is instead recommended on Arch.</ref> |<code>ibus-mozc</code> |<nowiki>-</nowiki> |<code>emacs-mozc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Anthy |<code>fcitx5-anthy</code> |<code>fcitx-anthy</code> |<code>ibus-anthy</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-anthy</code> |''built-in'' |''built-in'' |''built-in'' |- |SKK |<code>fcitx5-skk</code> |<code>fcitx-skk</code> |<code>ibus-skk</code> |''built-in'' |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |KKC |<code>fcitx5-kkc</code> |<code>fcitx-kkc</code> |<code>ibus-kkc</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Korean |- |Libhangul |<code>fcitx5-hangul</code> |<code>fcitx-hangul</code> |<code>ibus-hangul</code> |''built-in'' |<nowiki>-</nowiki> |<code>scim-hangul</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |''built-in'' |- ! colspan="10" |Vietnamese |- |UniKey |<code>fcitx5-unikey</code> |<code>fcitx-unikey</code> |<code>ibus-unikey</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |ViQR |<code>fcitx5-m17n</code><ref name=":1" group="Note">This is <code>fcitx5-table-viqr</code>, <code>fcitx-table-viqr</code>, <code>ibus-table-viqr</code> on Debian.</ref> |<code>fcitx-m17n</code><ref name=":1" group="Note" /> |<code>ibus-table-tv</code><ref name=":1" group="Note" /> |<code>uim-viqr</code> | - | - | - | - | - |- |Bamboo |<code>fcitx5-bamboo</code> |<nowiki>-</nowiki> |<code>ibus-bamboo</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Indic |- |Avro (Bangla) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-avro</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Helakuru (Sinhala) |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<code>ibus-helakuru</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |m17n |<code>fcitx5-m17n</code> |<code>fcitx-m17n</code> |<code>ibus-m17n</code> |<code>uim-m17n</code><ref name=":2" group="Note">On some distros, this is <code>uim-m17nlib</code>.</ref> |<nowiki>-</nowiki> |<code>scim-m17n</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |OpenBangla Keyboard (Bangla) |<code>fcitx5-openbangla</code><ref group="Note">Requires the [[Terra]] repository on Fedora.</ref> |<nowiki>-</nowiki> |<code>openbangla-keyboard</code><ref group="Note"><code>ibus-openbangla</code> on Fedora with the [[Terra]] repository.</ref> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Sayura (Sinhala) |<code>fcitx5-sayura</code> |<code>fcitx-sayura</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Varnam |<code>fcitx5-varnam</code> |<nowiki>-</nowiki> |<code>govarnam-ibus</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- ! colspan="10" |Others |- |Thai |<code>fcitx5-libthai</code> | - |<code>ibus-table-tv</code> |<nowiki>-</nowiki> |<nowiki>-</nowiki> | - |<nowiki>-</nowiki> |<nowiki>-</nowiki> |<nowiki>-</nowiki> |- |Math Symbols |[[Compose key]]? |[[Compose key]]? |<code>ibus-table-mathwriter</code> | - | - | - | - | - | - |- |Completion |''built-in'' | - |<code>ibus-typing-booster</code> | - | - | - | - | - | - |- |''"Everything Else"'' |<code>fcitx5-m17n</code>? |<code>fcitx-m17n</code>? |<code>ibus-m17n</code>? |<code>uim-m17n</code><ref name=":2" group="Note" />? | - |<code>scim-m17n</code>? | - | - | - |} === Notes === <references group=Note/> This list is compiled mainly based on Fedora and Arch Linux. On Arch Linux, the packages <code>ibus-table-*</code> are merged into just <code>ibus-table</code>. == How to choose your IME == This section represents the general case and the authors' opinions. It is not necessary to follow them. {| class="wikitable" |+Chinese !Situation !IME !Rime IME !Notes |- |Already using [[Rime]] | rowspan="3" |Rime | - | rowspan="3" |Rime is very powerful, but it comes with the cost of writing your own configuration files and [https://github.com/rime/home/wiki reading Chinese documentations], and thus is not recommended to beginners. |- |Prefer a highly customizable experience | - |- |Good at writing configuration files | - |- |Know Pinyin |Pinyin |''built-in'' | |- |Know Zhuyin |Chewing |℞ bopomofo |<code>libzhuyin</code> is not recommended (very unpopular), avoid <code>fcitx5-zhuyin</code> & <code>ibus-libzhuyin</code>. |- |Know Cangjie 3 / Quick 3 | rowspan="2" |Cangjie/Quick | rowspan="2" |℞ cangjie |Rime with [https://github.com/kennethso168/rime-cangjie3-extension rime-cangjie3-extension] |- |Know Cangjie 5 / Quick 5 | |- |Know SmartCangjie 6 |SCJ |℞ scj | |- |Know Jyutping |Rime |℞ cantonese |Jyutping from table-extras is barely usable |- |Know Wubi |Haifeng Wubi | |https://www.zhukun.net/archives/4856 |} {| class="wikitable" |+Japanese !Situation !IME !Notes |- |You hate Qt |Anthy |Anthy is unmaintained but it's written in GTK, so if you want your IME to fit into your GTK theme, use Anthy. |- |Otherwise |Mozc |Mozc is maintained by Google and has better suggestions, but you should also consider using the UT dictionaries. |} == Tips & Tricks == === Electron & Chromium Applications === If your IMF does not work in [[electron]] or [[chromium]]-based applications, add <code>--enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime</code> to the command line arguments. Taking [[Codium]] as an example: {{FileBox|title=~/.local/share/applications/codium.desktop|lang=ini|content= [Desktop Entry] Exec=/usr/bin/codium --no-sandbox --unity-launch %F --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime # ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━ …}} Additionally, avoid using [[Flatpak]]s. === Compose Key === :Main article: [[Compose key]] To use Compose Key in Fcitx5, go to ''Fcitx5 Settings → Global Options'', then in the ''Custom XKB Option'' entry, write <code>compose:rctrl</code>. For IBus, you will need to manually use [[setxkbmap]]. For a list of possible options, see <code>[[man]] 'xkeyboard-config(7)'</code>, section '''Position of Compose Key'''. == References == 6c0bf4ed550e6464779189a72a041d71e1b74a92 0 349 4412 3628 2026-02-10T19:16:20Z K0y0m1 318 Fixed the intro so it made a little more sense, "optimal use of an OS" might be a little misleading, therefore it was replaced with how init systems manage stuff wikitext text/x-wiki [[Category:Terminology]] In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is typically used to properly start up and manage services during boot and run time, making it necessary for OSes to properly run. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor'''<ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref> of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in an operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages </ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, etc. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |runit |February 10, 2004 |September 29, 2024 |↓ |Gerrit Pape |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS. == References == <references /> 288a130294f239f49c79c3a022938a5f730a025f 0 1084 4413 2026-02-10T23:53:03Z K0y0m1 318 work in progress page for the APK package manager for alpine, not much has been made, but i got tired wikitext text/x-wiki '''Alpine Package Keeper (apk)''' (not to be confused with <code>.apk</code> installation files found on android systems) is Alpine's official package manager. Coded in C, its primary goal is to manage packages on a user's systems while staying minimal. Packages on the distribution's repositories come in 3 official repository: <code>main</code>, <code>community</code>, and <code>testing</code>; however, the user is free to enable and disable them freely.<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], ''Alpine User Handbook,'' The Alpine Team (1) (Accessed 02/10/2026 18:00 UTC-5)</ref> == Overview == The <code>apk-tools</code> package provides the package manager and other features, the table below shows possible commands. {| class="wikitable" |+Package Management Via <code>apk</code> !Command !Usage !Overview |- |<code>add</code> |<code>apk add <package_name></code> |Adds a package to the system and modifies WORLD file, commits changes afterwards |- |<code>del</code> |<code>apk del <package_name></code> |Deletes a package from the system and modifies WORLD file, commits changes afterwards |- |<code>fix</code> |<code>apk fix <package_name></code> |Fixes (attempts to) a package via reinstall and/or upgrading without modifying WORLD |- |<code>update</code> |<code>apk update</code> |Updates repository index, Typically ran after modifying repository file |- |<code>upgrade</code> |<code>apk upgrade <optional_package></code> |Upgrade packages on the system, optionally upgrade only one package by specifying it. |- |<code>cache</code> |<code>apk cache <option></code> |Manages the local package cache |- |<code>query</code> |<code>apk query <package_name></code> |Combines <code>info</code>, <code>list</code>, and <code>search</code> commands through your installed packages and outputs information in a human-readable format |- |<code>info</code> |<code>apk info [optional_flag] <optinal_package></code> |Lists all information about installed packages and allows you to search through it with given flags |- |<code>dot</code> | | |} 36796b91c239aa3085e2909bd1cf73b680b19bc1 4427 4413 2026-02-13T02:11:43Z K0y0m1 318 Additional information for now. Not much. wikitext text/x-wiki '''Alpine Package Keeper (apk)''' (not to be confused with <code>.apk</code> installation files found on android systems) is Alpine's official package manager. Coded in C, its primary goal is to manage packages on a user's systems while staying minimal. Packages on the distribution's repositories come in 3 official repository: <code>main</code>, <code>community</code>, and <code>testing</code>;<ref>[https://wiki.alpinelinux.org/wiki/Repositories#Official_repositories Repositories - Official Repositories], ''Alpine Wiki'', The Alpine Team (1) (Accessed 2/12/2026 20:39 UTC-5)</ref> however, the user is free to enable and disable them freely.<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], ''Alpine User Handbook,'' The Alpine Team (1) (Accessed 02/10/2026 18:00 UTC-5)</ref> == Overview == The <code>apk-tools</code> package provides the package manager and other features, the table below shows possible commands.<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper Alpine Package Keeper], ''Alpine Wiki'', The Alpine Team (1) (Accessed 2/12/2026 20:40 UTC-5)</ref> {| class="wikitable" |+Package Management Via <code>apk</code> !Command !Usage !Overview |- |<code>add</code> |<code>apk add <package_name></code> |Adds a package to the system and modifies WORLD file, commits changes afterwards |- |<code>del</code> |<code>apk del <package_name></code> |Deletes a package from the system and modifies WORLD file, commits changes afterwards |- |<code>fix</code> |<code>apk fix <package_name></code> |Fixes (attempts to) a package via reinstall and/or upgrading without modifying WORLD |- |<code>update</code> |<code>apk update</code> |Updates repository index, Typically ran after modifying repository file |- |<code>upgrade</code> |<code>apk upgrade <optional_package></code> |Upgrade packages on the system, optionally upgrade only one package by specifying it. |- |<code>cache</code> |<code>apk cache <option></code> |Manages the local package cache |- |<code>query</code> |<code>apk query <package_name></code> |Combines <code>info</code>, <code>list</code>, and <code>search</code> commands through your installed packages and outputs information in a human-readable format |- |<code>info</code> |<code>apk info [optional_flag] <optinal_package></code> |Lists all information about installed packages and allows you to search through it with given flags |- |More commands... | | |} == Managing Packages == Official software on the Alpine Linux repositories are named "''a-packs''" and have the extension <code>.apk</code> (Not to be confused with Android's APK installation files). You can edit which repositories you'd like to access by editing <code>/etc/apk/repositories</code>, commenting/uncommenting any repository you'd like. Upon saving the file, run <code>apk update</code> to update the repository index.<ref>[https://wiki.alpinelinux.org/wiki/Repositories#Managing_repositories Repositories - Managing Repositories], ''Alpine Wiki'', The Alpine Team (3) (Accessed 2/12/2026 20:48 UTC-5)</ref> APK will automatically echo how many packages are currently available on enabled repositories upon completing the updates.<ref>[https://wiki.alpinelinux.org/wiki/Repositories Repositories], ''Alpine Wiki'', The Alpine Team (1) (Accessed 2/12/2026 20:48 UTC-5)</ref> === World === The <code>WORLD</code> file on Alpine Linux (located at <code>/etc/apk/world</code>) describes desired system states in a plain text file and uses unique syntax to configure package installation. Should you edit the file, run <code>apk fix</code> to apply changes. The <code>world</code> file must be in order upon running <code>apk fix</code>, else the package manager refuses to apply any constraints to the adjusted file; hence why APK will never leave a system unbootable.<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#World Alpine Package Keeper - World], ''Alpine Wiki,'' The Alpine Team (1) (Accessed 2/12/2026 20:56 UTC-5)</ref> === Configuring APK === APK allows you to configure the package manager by adjusting/editing the <code>/etc/config/apk</code> (assuming the user has made it [make the file via <code>touch /etc/config/apk</code> with proper permissions]) will override the default APK config located in <code>/lib/apk/config</code>. <ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#Configuration_file Alpine Package Keeper - Configuration File], ''Alpine Wiki'', The Alpine Team (11) (Accessed 2/12/2026 21:10 UTC-5)</ref> e7a79102be7ac67677d005758afd0a53e2990823 0 198 4414 4370 2026-02-11T22:23:40Z PhantasNick 291 Broke up SLE as i did with openSUSE into Desktop, Micro and Server wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain; it exclusively uses the KDE Desktop Environment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability; each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind, as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects; it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise Desktop]] | Designed for mixed IT environments, SUSE Linux Enterprise Desktop (SLED) offers the security, manageability, and efficiency of Linux. Apart of the [[SUSE Linux Enterprise (SLE)]] Ecosystem |- | [[SUSE Linux Enterprise Server]] | SUSE Linux Enterprise Server (SLES) is a highly reliable, scalable, and secure server operating system, designed to power mission-critical workloads. Apart of the [[SUSE Linux Enterprise (SLE)]] Ecosystem |- | [[SUSE Linux Micro]] | Based on SLES, an ultra-reliable, lightweight developer friendly operating system purpose built for edge computing. Apart of the [[SUSE Linux Enterprise (SLE)]] Ecosystem |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == db878aec9aa3fc9bef2bd9bdf37d56c448b1322b 4415 4414 2026-02-11T22:28:36Z PhantasNick 291 Sited descriptions as i pulled them from SUSE Product Page wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain; it exclusively uses the KDE Desktop Environment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability; each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind, as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects; it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise Desktop]] | Designed for mixed IT environments, SUSE Linux Enterprise Desktop (SLED) offers the security, manageability, and efficiency of Linux. Apart of the [[SUSE Linux Enterprise (SLE)]] Ecosystem <ref name="sle">[https://www.suse.com/products/] |- | [[SUSE Linux Enterprise Server]] | SUSE Linux Enterprise Server (SLES) is a highly reliable, scalable, and secure server operating system, designed to power mission-critical workloads. Apart of the [[SUSE Linux Enterprise (SLE)]] Ecosystem <ref name="sle"/> |- | [[SUSE Linux Micro]] | Based on SLES, an ultra-reliable, lightweight developer friendly operating system purpose built for edge computing. Apart of the [[SUSE Linux Enterprise (SLE)]] Ecosystem <ref name="sle"/> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == a40f94733a2a9668ef9afcbdaca584cac000aa35 4416 4415 2026-02-11T22:32:29Z PhantasNick 291 fixed formatting cause i broke it wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE Kalpa]] | An immutable [[openSUSE]] project designed to be easy to use and maintain; it exclusively uses the KDE Desktop Environment |- | [[openSUSE Leap]] | One of two of [[openSUSE]]'s flagship projects, designed with stability; each release is given 18 months of support |- | [[openSUSE Leap Micro]] | An immutable [[openSUSE]] project made with server stability in mind, as it updates slower than standard MicroOS |- | [[openSUSE MicroOS]] | An immutable [[openSUSE]] project designed to be easy to maintain and based on Tumbleweed |- | [[openSUSE Slowroll]] | An experimental [[openSUSE]] project designed to update faster than Leap and slower than Tumbleweed |- | [[openSUSE Tumbleweed]] | One of two of [[openSUSE]]'s flagship projects; it updates frequently but attempts to be more stable than other [[Rolling release|Rolling Releases]] |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise Desktop]] | Designed for mixed IT environments, SUSE Linux Enterprise Desktop (SLED) offers the security, manageability, and efficiency of Linux. Apart of the [[SUSE Linux Enterprise (SLE)]] Ecosystem <ref name="sle">[https://www.suse.com/products/] </ref> |- | [[SUSE Linux Enterprise Server]] | SUSE Linux Enterprise Server (SLES) is a highly reliable, scalable, and secure server operating system, designed to power mission-critical workloads. Apart of the [[SUSE Linux Enterprise (SLE)]] Ecosystem <ref name="sle"/> |- | [[SUSE Linux Micro]] | Based on SLES, an ultra-reliable, lightweight developer friendly operating system purpose built for edge computing. Apart of the [[SUSE Linux Enterprise (SLE)]] Ecosystem <ref name="sle"/> |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == f6f500478bd16bdb4871f743b6bfe4255ad25b4f 4417 4416 2026-02-11T22:39:41Z PhantasNick 291 Reverting openSUSE Based projects to how they were prior to 05:26, 17 November 2025 per Admin wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 871b9be7fd2b00a1c700bbe5a58c232bb0b2842c 4418 4417 2026-02-11T22:40:05Z PhantasNick 291 whoops fixed formatting wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == e186fef5e7db9e0d488de386a8dfad9c860177b0 4419 4418 2026-02-11T22:54:05Z PhantasNick 291 found an existing SLE page so ive directed to it wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Budgie Atomic]] |Fedora Budgie Atomic ships the popular Budgie desktop environment in an atomic fashion. |- |[[Fedora CoreOS]] |Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] |An atomic desktop operating system featuring the COSMIC desktop from System76. |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular KDE Plasma Desktop. |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant GNOME Desktop. |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 259ecf5516abd387d232877404f63d736f3adbf5 4420 4419 2026-02-11T23:00:56Z PhantasNick 291 Grouped the Fedora Atomic Distros together under one banner, per Admin atmois wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Atomic]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 4921560b3705da04a1631c8987fe1aa881ccd7da 4446 4420 2026-04-15T08:46:36Z NotSure 330 Added Tinfoil Hat Linux in independent Linux distros wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Atomic]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 7bc4a343a47fcb49b49f409fb3737daa62778541 0 1085 4421 2026-02-11T23:20:45Z PhantasNick 291 Created Fedora Atomic Group Page, added initial sub pages and copied descriptions from old version of Distro Page, image has been pulled from main Fedora Page as im unsure if Atomic has a different Logo. Link to website is same as Fedora Page since i am unsure how to add two seperate links wikitext text/x-wiki {{DistributionInfobox | title = Fedora Atomic | image = [[File:Fedora logo.svg|Fedora_logo|frameless]] | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64, Arm | website = [https://www.fedoraproject.org fedoraproject.org] }} A atomic variant of the Fedora Project designed with Security and Reliability in mind for Desktops, Servers and Containers ==== Fedora Atomic Variants ==== {| class="wikitable" |- ! Variant !! Description |- |[[Fedora Budgie Atomic]] | An atomic desktop operating system featuring the popular [[Budgie]] desktop environment |- |[[Fedora CoreOS]] | An automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] | An atomic desktop operating system featuring the [[COSMIC]] desktop from [[System76]] |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular [[KDE Plasma]] Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant [[GNOME]] Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |} c6291682fe9569d23682e1db9a111f2adf406aa5 4422 4421 2026-02-11T23:23:00Z PhantasNick 291 Added all Desktops available between versions wikitext text/x-wiki {{DistributionInfobox | title = Fedora Atomic | image = [[File:Fedora logo.svg|Fedora_logo|frameless]] | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable | defaultdesktops = [[Budgie]],[[COSMIC]],[[GNOME]],[[KDE Plasma]],[[Sway]] | usagetype = Desktop | architectures = x86_64, Arm | website = [https://www.fedoraproject.org fedoraproject.org] }} A atomic variant of the Fedora Project designed with Security and Reliability in mind for Desktops, Servers and Containers ==== Fedora Atomic Variants ==== {| class="wikitable" |- ! Variant !! Description |- |[[Fedora Budgie Atomic]] | An atomic desktop operating system featuring the popular [[Budgie]] desktop environment |- |[[Fedora CoreOS]] | An automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] | An atomic desktop operating system featuring the [[COSMIC]] desktop from [[System76]] |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular [[KDE Plasma]] Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant [[GNOME]] Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |} c3a3805e0d3016ef96bc98e8f48e7a45fce3da5a 4423 4422 2026-02-11T23:24:20Z PhantasNick 291 Spacing wikitext text/x-wiki {{DistributionInfobox | title = Fedora Atomic | image = [[File:Fedora logo.svg|Fedora_logo|frameless]] | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable | defaultdesktops = [[Budgie]], [[COSMIC]], [[GNOME]], [[KDE Plasma]], [[Sway]] | usagetype = Desktop | architectures = x86_64, Arm | website = [https://www.fedoraproject.org fedoraproject.org] }} A atomic variant of the Fedora Project designed with Security and Reliability in mind for Desktops, Servers and Containers ==== Fedora Atomic Variants ==== {| class="wikitable" |- ! Variant !! Description |- |[[Fedora Budgie Atomic]] | An atomic desktop operating system featuring the popular [[Budgie]] desktop environment |- |[[Fedora CoreOS]] | An automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] | An atomic desktop operating system featuring the [[COSMIC]] desktop from [[System76]] |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular [[KDE Plasma]] Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant [[GNOME]] Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |} 778838b6e7d31c9f71d8c9513f95389fc4a4ac43 4424 4423 2026-02-11T23:25:57Z PhantasNick 291 No Citations and a Stub wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{stub}} {{DistributionInfobox | title = Fedora Atomic | image = [[File:Fedora logo.svg|Fedora_logo|frameless]] | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable | defaultdesktops = [[Budgie]], [[COSMIC]], [[GNOME]], [[KDE Plasma]], [[Sway]] | usagetype = Desktop | architectures = x86_64, Arm | website = [https://www.fedoraproject.org fedoraproject.org] }} A atomic variant of the Fedora Project designed with Security and Reliability in mind for Desktops, Servers and Containers ==== Fedora Atomic Variants ==== {| class="wikitable" |- ! Variant !! Description |- |[[Fedora Budgie Atomic]] | An atomic desktop operating system featuring the popular [[Budgie]] desktop environment |- |[[Fedora CoreOS]] | An automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] | An atomic desktop operating system featuring the [[COSMIC]] desktop from [[System76]] |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular [[KDE Plasma]] Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant [[GNOME]] Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |} 662723cb34db6699f22d61f848a0fcb764d880b8 4425 4424 2026-02-11T23:26:32Z PhantasNick 291 wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = Fedora Atomic | image = [[File:Fedora logo.svg|Fedora_logo|frameless]] | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable | defaultdesktops = [[Budgie]], [[COSMIC]], [[GNOME]], [[KDE Plasma]], [[Sway]] | usagetype = Desktop | architectures = x86_64, Arm | website = [https://www.fedoraproject.org fedoraproject.org] }} A atomic variant of the Fedora Project designed with Security and Reliability in mind for Desktops, Servers and Containers ==== Fedora Atomic Variants ==== {| class="wikitable" |- ! Variant !! Description |- |[[Fedora Budgie Atomic]] | An atomic desktop operating system featuring the popular [[Budgie]] desktop environment |- |[[Fedora CoreOS]] | An automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] | An atomic desktop operating system featuring the [[COSMIC]] desktop from [[System76]] |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular [[KDE Plasma]] Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant [[GNOME]] Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |} e2a5dda5d2f421ae791c8892a2460bec1e460ea6 4426 4425 2026-02-11T23:33:15Z PhantasNick 291 correct flag wikitext text/x-wiki {{stub}} {{Needs Citations}} {{DistributionInfobox | title = Fedora Atomic | image = [[File:Fedora logo.svg|Fedora_logo|frameless]] | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable | defaultdesktops = [[Budgie]], [[COSMIC]], [[GNOME]], [[KDE Plasma]], [[Sway]] | usagetype = Desktop | architectures = x86_64, Arm | website = [https://www.fedoraproject.org fedoraproject.org] }} A atomic variant of the Fedora Project designed with Security and Reliability in mind for Desktops, Servers and Containers ==== Fedora Atomic Variants ==== {| class="wikitable" |- ! Variant !! Description |- |[[Fedora Budgie Atomic]] | An atomic desktop operating system featuring the popular [[Budgie]] desktop environment |- |[[Fedora CoreOS]] | An automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] | An atomic desktop operating system featuring the [[COSMIC]] desktop from [[System76]] |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular [[KDE Plasma]] Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant [[GNOME]] Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |} 80fdfa31ad1102eee87029eeee3cc4e204d87302 0 769 4428 4337 2026-02-27T14:27:47Z Satnus 215 Added MangoWC wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | [[MangoWC]]<ref>[https://mangowc.vercel.app] (Accessed: 2026-02-27)</ref> || None || [[C]] || Extremely customizable & performant Wayland compositor built on top of [[dwl]]. |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| [[C]] || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | [[Sway]] || None || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || None (Tiling) || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[river]]<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref> || None (Tiling) || [[zig]]|| Lightweight and minimal tiling compositor focused on simplicity. |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || None (3D effects) || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || None (Kiosk) || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- | [[Niri]] || None (Scrolling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |[[COSMIC]] |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || None (Tiling) || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 6ad79b88d509c28b40de64dc3d4288f757d23ca7 4429 4428 2026-02-28T13:03:41Z Satnus 215 Touched up the reference for mangowc wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | [[MangoWC]]<ref>[https://mangowc.vercel.app MangoWC Homepage] (Accessed: 2026-02-27)</ref> || None || [[C]] || Extremely customizable & performant Wayland compositor built on top of [[dwl]]. |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| [[C]] || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | [[Sway]] || None || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || None (Tiling) || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[river]]<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref> || None (Tiling) || [[zig]]|| Lightweight and minimal tiling compositor focused on simplicity. |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || None (3D effects) || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || None (Kiosk) || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- | [[Niri]] || None (Scrolling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |[[COSMIC]] |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || None (Tiling) || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 37b0f9ace60143840b5f65e7736ae9a4ddd34224 6 1086 4430 2026-03-01T22:34:23Z Satnus 215 Logo of Niri. Downloaded directly from the github. wikitext text/x-wiki == Summary == Logo of Niri. Downloaded directly from the github. 45cea84147816ef88a89f9a4ca47cf6772d1adc7 0 534 4431 3737 2026-03-01T22:40:06Z Satnus 215 Added proper logo for niri. wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox | image = [[File:Nirilogo.svg|300px|example_niri_rice]] | caption = Example Niri Rice | title = niri | releasestatus = Maintained | firstrelease = v0.1.0-alpha.1 | lastrelease = Version 25.01 | languages = [[Rust]] | developers = Ivan Molodetskikh A.K.A. YaLTeR | website = [https://github.com/YaLTeR/niri Github Repository] }} [[File:Niri Rice.png|thumb|A desktop running [[Niri]].]] Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">[https://github.com/YaLTeR/niri/wiki/Important-Software Important Software · YaLTeR/niri Wiki · GitHub], YaLTeR, 2025-08-09 (Accessed: 2025-08-09)</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad]{{Dead Link|2025-08-14|403}} and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse]{{Dead Link|2025-08-14|403}} gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations]{{Dead Link|2025-08-14|403}} * Live-reloading == References == <references /> 8fed066cad09175b2f9a25f2a16d1a29291da6d4 4432 4431 2026-03-01T22:41:23Z Satnus 215 Forgot to edit the caption 💀 wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox | image = [[File:Nirilogo.svg|300px|example_niri_rice]] | caption = Niri's logo | title = niri | releasestatus = Maintained | firstrelease = v0.1.0-alpha.1 | lastrelease = Version 25.01 | languages = [[Rust]] | developers = Ivan Molodetskikh A.K.A. YaLTeR | website = [https://github.com/YaLTeR/niri Github Repository] }} [[File:Niri Rice.png|thumb|A desktop running [[Niri]].]] Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">[https://github.com/YaLTeR/niri/wiki/Important-Software Important Software · YaLTeR/niri Wiki · GitHub], YaLTeR, 2025-08-09 (Accessed: 2025-08-09)</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad]{{Dead Link|2025-08-14|403}} and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse]{{Dead Link|2025-08-14|403}} gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations]{{Dead Link|2025-08-14|403}} * Live-reloading == References == <references /> e2694e8791765bb78def7fc5eed2f36fc1da057e 0 622 4433 4395 2026-03-02T08:07:31Z Satnus 215 Removed the second LXQt screenshot. wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:COSMIC Epoch 1.0.0 alpha with apps.png|[[COSMIC]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity Desktop Environment]] File:XFCE-4.18-Desktop.png|[[XFCE]] File:LXDE-Qt preview.png|[[LXDE]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment based on GNOME and developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[COSMIC]] |[[COSMIC]] is a GNOME-based Desktop Environment developed by [[system76]], also known as the creators of [[Pop! OS|Pop! OS.]] COSMIC is built in [[Rust]]. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in many different languages. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} 69c3d4350ff900545da60b1c7d0448a38f5073ff 4 327 4434 4257 2026-03-02T16:53:29Z DeletedAccount 19 test wikitext text/x-wiki linux is cool.<ref>{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributiors|year=2025}}</ref> why? because i said so. test number 10 hello [[File:Bazzitehyfetch.png|alt=test|thumb]] =References= <references /> 6f74dd81391c2601554121ffd5cce9cd978cd25e 4437 4434 2026-03-02T17:05:30Z DeletedAccount 19 test wikitext text/x-wiki linux is cool.<ref>{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributiors|year=2025}}</ref> why? because i said so. bye [[File:Bazzitehyfetch.png|alt=test|thumb]] =References= <references /> 955c1222656779ece052f10967845f7c27f12308 4440 4437 2026-03-12T14:13:46Z Ow0cast 249 Ow0cast moved page [[Test]] to [[ATL:Test]]: this really shouldve been placed here to begin with wikitext text/x-wiki linux is cool.<ref>{{Cite|url=https://atl.wiki|title=All Things Linux Wiki|author=atl.wiki Contributiors|year=2025}}</ref> why? because i said so. bye [[File:Bazzitehyfetch.png|alt=test|thumb]] =References= <references /> 955c1222656779ece052f10967845f7c27f12308 2 216 4435 540 2026-03-02T17:00:01Z Atmois 13 Protected "[[User:DeletedAccount]]": Deleted Account ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) [cascading] wikitext text/x-wiki This is the account which users which get deleted for whatever reasons are merged into then deleted. If you see a edit from this user it came from a deleted account. c20e2ba8118fd71eb715d125629d2db9d3d68073 8 606 4436 2186 2026-03-02T17:01:57Z Atmois 13 wikitext text/x-wiki *Common block reasons ** Inserting false information ** Persistent vandalism ** Spamming links to external sites ** Intimidating behaviour or harassment ** Abusing alternate accounts ** Unacceptable username 42a9a26fa89513afe40ca8280aa409ea156e0331 2 1088 4439 2026-03-11T15:06:16Z Galisma 325 edited my user page wikitext text/x-wiki Linux enjoyer, hoping to help the wiki. I'm not a wiki editor, so please point any mistake I make 0df0253ca5c5c2c11a218c0194cff712b38684d4 0 1089 4441 2026-03-12T14:13:46Z Ow0cast 249 Ow0cast moved page [[Test]] to [[ATL:Test]]: this really shouldve been placed here to begin with wikitext text/x-wiki #REDIRECT [[ATL:Test]] 634725b2418c021d7e78ec7c741f5c378b076570 5 472 4442 1560 2026-03-12T14:13:47Z Ow0cast 249 Ow0cast moved page [[Talk:Test]] to [[ATL talk:Test]]: this really shouldve been placed here to begin with wikitext text/x-wiki == test == test [[User:Test|Test]] ([[User talk:Test|talk]]) 13:31, 5 January 2025 (UTC) 38079a2ee99feb818f91387ee87a6f76fda4133e 1 1090 4443 2026-03-12T14:13:47Z Ow0cast 249 Ow0cast moved page [[Talk:Test]] to [[ATL talk:Test]]: this really shouldve been placed here to begin with wikitext text/x-wiki #REDIRECT [[ATL talk:Test]] 337d7f2d1dbcb850364e529ad595fe5d881cd988 0 394 4444 4311 2026-03-14T13:08:00Z Imnotgoodatnames 121 split UNIX-like systems from Other Operating Systems, added more entries wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other UNIX-like ==== {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[MS-DOS]] | a command-line operating system developed by Microsoft for early IBM-compatible personal computers |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS |- | [[Windows]] | a proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} 2d58a57023989e76545a65e3cf2867655eec311e 0 1091 4445 2026-03-26T20:51:03Z ApolloLinux 328 Added the starting Text to MangoWC. wikitext text/x-wiki MangoWC is a Tiling [[Window Manager]] and [[Wayland]] compositor based on dwl that keeps its lightweight, suckless-style design while adding more practical features. It stays fast to build and minimal, but improves usability with better layouts, multi-monitor support, and broader Wayland compatibility, making it more suitable for daily use without unnecessary bloat. Stability is a core principle of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. The Wayland compositor also adopts a No Feature Creep model, where not all requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. e2f38e25c5aee99e08674fc011f93a1ba6834dbd 0 1092 4447 2026-04-15T09:06:39Z NotSure 330 Tinfoil Hat Linux wikitext text/x-wiki {{Infobox OS | name = Tinfoil Hat Linux | developer = The Shmoo Group | released = February 2002 | discontinued = Yes | source_model = Open source | kernel_type = Monolithic (Linux) | supported_platforms = i386 | size = First Version 1.41MB 2nd Version 1.41MB | ui = Terminal Only }} '''Tinfoil Hat Linux''' ('''THL''') is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purpose. a540f35cdeda9153e7c1bcf465a9425d12a36df7 4448 4447 2026-04-15T09:09:51Z NotSure 330 Deleted Not Working InfoBox wikitext text/x-wiki '''Tinfoil Hat Linux''' ('''THL''') is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purpose. 3f4045ac7119dfd3bc014a55756ecf52a2a4f921 4449 4448 2026-04-15T09:46:51Z NotSure 330 Added InfoBox, probably still not working wikitext text/x-wiki {{SoftwareInfobox | title = Tinfoil Hat Linux | developer = The Shmoo Group | status = discontinued | latest_relase = 2002-02-21 | language = C }} '''Tinfoil Hat Linux''' is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. d8cd6aaf785abd4179a2ee5135c8cdcd054f0ac7 4450 4449 2026-04-15T10:05:00Z NotSure 330 fixed InfoBox :))) wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | title = Tinfoil Hat Linux | releasestatus = Discontinued | lastrelease = 2.0pre 2002-02-21 | firstrelease = 1.0.0 2002-02 | languages = [[C]], [[Shell]], [[html]], [[CMake]] | developers = [[The Shmoo Group]] | website = http://tinfoilhat.shmoo.com/ }} '''Tinfoil Hat Linux''' is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. 2f6b50379a468d4d2e02ae58b2ead6b99f124d17 4451 4450 2026-04-15T10:05:59Z NotSure 330 fixed typo in html wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | title = Tinfoil Hat Linux | releasestatus = Discontinued | lastrelease = 2.0pre 2002-02-21 | firstrelease = 1.0.0 2002-02 | languages = [[C]], [[Shell]], [[HTML]], [[CMake]] | developers = [[The Shmoo Group]] | website = http://tinfoilhat.shmoo.com/ }} '''Tinfoil Hat Linux''' is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. 7ba9060e226bb59dd70409252469d9f8b0a5916c 4453 4451 2026-04-15T10:41:58Z NotSure 330 added list of anti surveillance programs used in tinfoil Linux wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | title = Tinfoil Hat Linux | releasestatus = Discontinued | lastrelease = 2.0pre 2002-02-21 | firstrelease = 1.0.0 2002-02 | languages = [[C]], [[Shell]], [[HTML]], [[CMake]] | developers = [[The Shmoo Group]] | website = http://tinfoilhat.shmoo.com/ }} '''Tinfoil Hat Linux''' '''THL''' is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defeat itself from surveillance including TEMPEST and KeyLoggers List of Tinfoil Hat Linux methods against surveillance * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanisms were intended to enhance operational security by limiting data persistence and mitigating common surveillance techniques. e353969e8455f1f49c751f26702334fe47a2bb92 4456 4453 2026-04-15T11:04:11Z NotSure 330 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | title = Tinfoil Hat Linux | releasestatus = Discontinued | lastrelease = 2.0pre 2002-02-21 | firstrelease = 1.0.0 2002-02 | languages = [[C]], [[Shell]], [[HTML]], [[CMake]] | developers = [[The Shmoo Group]] | website = http://tinfoilhat.shmoo.com/ }} '''Tinfoil Hat Linux''' '''THL''' is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defeat itself from surveillance including TEMPEST and KeyLoggers List of Tinfoil Hat Linux methods against surveillance * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanisms were intended to enhance operational security by limiting data persistence and mitigating common surveillance techniques. 3793058e18bf55832d8d3ee575f9f8382adbfcab 4457 4456 2026-04-15T11:04:38Z NotSure 330 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | title = Tinfoil Hat Linux | releasestatus = Discontinued | lastrelease = 2.0pre 2002-02-21 | firstrelease = 1.0.0 2002-02 | languages = [[C]], [[Shell]], [[HTML]], [[CMake]] | developers = [[The Shmoo Group]] | website = http://tinfoilhat.shmoo.com/ }} '''Tinfoil Hat Linux''' '''THL''' is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defeat itself from surveillance including TEMPEST and KeyLoggers List of Tinfoil Hat Linux methods against surveillance * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanisms were intended to enhance operational security by limiting data persistence and mitigating common surveillance techniques. bed1bb6752ec19f3c727e8976f8c4531440f78f4 4458 4457 2026-04-15T11:13:05Z NotSure 330 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | title = Tinfoil Hat Linux | releasestatus = Discontinued | lastrelease = 2.0pre 2002-02-21 | firstrelease = 1.0.0 2002-02 | languages = [[C]], [[Shell]], [[HTML]], [[CMake]] | developers = [[The Shmoo Group]] | website = http://tinfoilhat.shmoo.com/ }} '''Tinfoil Hat Linux''' '''THL''' is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defeat itself from surveillance including TEMPEST and KeyLoggers List of Tinfoil Hat Linux methods against surveillance * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanisms were intended to enhance operational security by limiting data persistence and mitigating common surveillance techniques. 28f17f748493a6c471cafccff5fe2ffb9526256f 4459 4458 2026-04-15T12:14:29Z NotSure 330 changed softwareInfoBox into DistributionInfoBox wikitext text/x-wiki {{DistributionInfobox | title = Tinfoil Hat Linux | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | releasestatus = Discontinued | releasemodel = None | packagemanager = None | defaultdesktops = Terminal only | usagetype = Security | architectures = i386 | website = [[tinfoilhat.shmoo.com]] }} '''Tinfoil Hat Linux''' '''THL''' is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defeat itself from surveillance including TEMPEST and KeyLoggers List of Tinfoil Hat Linux methods against surveillance * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanisms were intended to enhance operational security by limiting data persistence and mitigating common surveillance techniques. e102f4a1ccaf374d0773ad42ca269e67f86e0509 6 1093 4452 2026-04-15T10:15:30Z NotSure 330 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 1094 4454 2026-04-15T10:45:33Z NotSure 330 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1095 4455 2026-04-15T10:54:56Z NotSure 330 tempest for Eliza wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Eliza.png]] | caption = Tempest For eliza in use | title = Tempest for eliza | releasestatus = discontinued | lastrelease = 1.0.5, 2002 | firstrelease = 1.0.0, unknown | languages = Unknown | developers = Erikyyy | website = [https://erikyyy.de/tempest/] }} '''Tempest for Eliza''' is an experimental open-source program written by Erik Thiele that turns a computer monitor into a rudimentary AM radio transmitter by exploiting unintended electromagnetic emissions from display hardware. It is part of a class of software and research projects inspired by “TEMPEST” side-channel techniques. == overview == Tempest for Eliza generates carefully designed pixel patterns on a computer screen. These patterns cause the monitor’s electronic components to emit electromagnetic signals at specific frequencies. When these emissions are picked up by an AM radio tuned to the right frequency, they can be interpreted as sound often musical tones == background == The project is based on research into compromising electromagnetic emanations, a field sometimes referred to as TEMPEST. The term originally comes from a U.S. government codename related to standards for limiting electronic eavesdropping risks. A key academic foundation is the concept of van Eck phreaking, introduced by Wim van Eck in 1985, which showed that video displays can be reconstructed from their electromagnetic radiation. Tempest for Eliza builds on this idea in a creative direction: instead of reconstructing images from emissions Tempest for Eliza interfers the TEMPEST signals, also deliberately encodes audio signals into them. ec9f54615a567e260280d006363eb5d6197de1c8 0 1096 4460 2026-04-15T13:21:49Z NotSure 330 Pear Os wikitext text/x-wiki {{DistributionInfobox | title = Pear Os | image = [[File:pearos.png|pearos.png]] | caption = Logo of Pear Os | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = KDE Plasma | usagetype = Desktop | architectures = x86_64 | website = https://pearos.xyz/ }} '''Pear OS''' is an operating system based on [[Arch Linux ]] with default [[linux kernel]] (version 6.17) and [[systemd]]. It is developed by one person, its main purpose is to give linux users the feeling of [[MacOs]] == informations == Pear OS was originally developed as a web OS in 2010. The Os got later left forgotten without support, however in ~2022 Alexandru Bălan started developing the software again. e7d9a2f64c05fda839b8096dec0c47d82788a723 4461 4460 2026-04-15T13:23:08Z NotSure 330 minor edit wikitext text/x-wiki {{DistributionInfobox | title = Pear Os | image = [[File:pearos.png|pearos.png]] | caption = Logo of Pear Os | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = KDE Plasma | usagetype = Desktop | architectures = x86_64 | website = https://pearos.xyz/ }} '''Pear OS''' is an operating system based on [[Arch Linux ]] with default [[linux kernel]] (version 6.17) and [[systemd]]. It is developed by one person, its main purpose is to give linux users the feeling of [[MacOs]] == informations == Pear OS was originally developed as a web OS in 2010. The Os got later in 2014 sold to an unknown company, however in ~2022 Alexandru Bălan started developing the software again now its available and free. 310907c31f2b20df290e8d0dba2ea08a24d72f61 4466 4461 2026-04-15T14:03:33Z NotSure 330 fixed linking to MacOs and Linux Kernel wikitext text/x-wiki {{DistributionInfobox | title = Pear Os | image = [[File:pearos.png|pearos.png]] | caption = Logo of Pear Os | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = KDE Plasma | usagetype = Desktop | architectures = x86_64 | website = https://pearos.xyz/ }} '''Pear OS''' is an operating system based on [[Arch Linux]] with default [[Linux|Linux Kernel]] (version 6.17) and [[systemd|SystemD]]. It is developed by one person, its main purpose is to give linux users the feeling of [[MacOS]] == informations == Pear OS was originally developed as a web OS in 2010. The Os got later in 2014 sold to an unknown company, however in ~2022 Alexandru Bălan started developing the software again now its available and free. 36a34b6b459d3a9631bcb40ba35cd6e9bab0bdbf 4467 4466 2026-04-15T14:24:24Z Ow0cast 249 Ow0cast moved page [[Pear os]] to [[Pear OS]]: Misspelled title: capitalization wikitext text/x-wiki {{DistributionInfobox | title = Pear Os | image = [[File:pearos.png|pearos.png]] | caption = Logo of Pear Os | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = KDE Plasma | usagetype = Desktop | architectures = x86_64 | website = https://pearos.xyz/ }} '''Pear OS''' is an operating system based on [[Arch Linux]] with default [[Linux|Linux Kernel]] (version 6.17) and [[systemd|SystemD]]. It is developed by one person, its main purpose is to give linux users the feeling of [[MacOS]] == informations == Pear OS was originally developed as a web OS in 2010. The Os got later in 2014 sold to an unknown company, however in ~2022 Alexandru Bălan started developing the software again now its available and free. 36a34b6b459d3a9631bcb40ba35cd6e9bab0bdbf 0 1092 4462 4459 2026-04-15T13:29:05Z NotSure 330 /* Security Features */ and a minor change wikitext text/x-wiki {{DistributionInfobox | title = Tinfoil Hat Linux | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | releasestatus = Discontinued | releasemodel = None | packagemanager = None | defaultdesktops = Terminal only | usagetype = Security | architectures = i386 | website = [[tinfoilhat.shmoo.com]] }} '''Tinfoil Hat Linux''' '''THL''' is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defeat itself from surveillance including TEMPEST and KeyLoggers === List of Tinfoil Hat Linux methods against surveillance==== * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanisms were intended to enhance operational security by limiting data persistence and mitigating common surveillance techniques. 405b33d60e4f4b16f84da7659d67922feca295ce 4464 4462 2026-04-15T13:38:06Z NotSure 330 typo wikitext text/x-wiki {{DistributionInfobox | title = Tinfoil Hat Linux | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | releasestatus = Discontinued | releasemodel = None | packagemanager = None | defaultdesktops = Terminal only | usagetype = Security | architectures = i386 | website = [[tinfoilhat.shmoo.com]] }} '''Tinfoil Hat Linux''' ('''THL''') is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defeat itself from surveillance including TEMPEST and KeyLoggers == List of Tinfoil Hat Linux methods against surveillance== * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanism were intended to enhance operational security limiting data persistence and mitigating common surveillance techniques. e43caff8462a5a98b67bb74a37d1dd6573b9d288 4465 4464 2026-04-15T13:38:48Z NotSure 330 another typo wikitext text/x-wiki {{DistributionInfobox | title = Tinfoil Hat Linux | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | releasestatus = Discontinued | releasemodel = None | packagemanager = None | defaultdesktops = Terminal only | usagetype = Security | architectures = i386 | website = tinfoilhat.shmoo.com }} '''Tinfoil Hat Linux''' ('''THL''') is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defeat itself from surveillance including TEMPEST and KeyLoggers == List of Tinfoil Hat Linux methods against surveillance== * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanism were intended to enhance operational security limiting data persistence and mitigating common surveillance techniques. 55ea4940533704452c33cbb14b913963e5a096f4 0 198 4463 4446 2026-04-15T13:35:23Z NotSure 330 /* Arch Based */ Pear os wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os]] |an Arch based distribution focused on giving Linux users the felling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Atomic]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 4a3f3e57e4d57242930a56e7978aeca7af1a1a0b 4471 4463 2026-04-16T14:49:50Z NotSure 330 /* Arch Based */ wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |an Arch based distribution focused on giving Linux users the felling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Atomic]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == d44a5d14bfd171affb82f9d1ba2e98a5442eaa0e 0 1097 4468 2026-04-15T14:24:24Z Ow0cast 249 Ow0cast moved page [[Pear os]] to [[Pear OS]]: Misspelled title: capitalization wikitext text/x-wiki #REDIRECT [[Pear OS]] 914a006c58350e97b37678a85bd7ca5e7579bbe2 6 1098 4469 2026-04-15T15:30:03Z NotSure 330 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1099 4470 2026-04-15T15:54:50Z NotSure 330 Termux wikitext text/x-wiki {{SoftwareInfobox | image = [[File:E350507f5830c9c2a6a0c477dd3f1c68.png|thumb]] | caption = Termux Logo | title = Termux | releasestatus = Maintained | lastrelease = 0.119.0-beta.3 2026-02-11 | firstrelease = 0.17, 2015-05-30 | languages = [[java]], [[C]], [[C++]] | developers = Termux Core Team | website = https://termux.dev }} '''Termux''' is a free and open-source terminal emulator and Linux environment application for Android devices. It allows users to run a lightweight [[Linux Distributions|Linux Distrubution]] directly on their mobile devices without requiring root access. Designed primarily for developers, system administrators, and power users, Termux provides a command-line interface similar to that found on desktop Linux systems. == Overview == Termux bridges the gap between mobile and desktop computing by bringing a [[UNIX|Unix-like]] environment to Android. Users can install and run a wide variety of command-line tools, for example [[fastfetch|FastFetch]], programming languages, and utilities, making it a versatile platform for development, experimentation, and learning. == Architecture and base distribution == Termux is based on a minimal Linux environment built using: * [[Android]] as the host platform * A custom package management system similar to those in Linux distributions * The [[APT|APT (Advanced Package Tool)]], adapted for Android * Libraries compiled specifically for Android’s Bionic libc instead of [[GNU|GNU libc]]. == Features == Termux includes a repository of thousands of packages that can be installed using Commands like: * pkg install python * pkg install git * pkg install clang 5f045c057bf3a1f8e25df52cec896fd74be0f9b9 0 394 4472 4444 2026-04-24T15:20:33Z NotSure 330 /* Other Operating Systems */ wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other UNIX-like ==== {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} f4afd4f11682a925011dde17e01e092af06ff010 8 538 4473 3531 2026-04-30T08:54:36Z Atmois 13 Add notice wikitext text/x-wiki FOSS.wiki will be online for editing shortly, we are currently rebranding the content to the new managment and fixing images. Thank you for your patience! 276b4e3f29a9ef082dcd3bbf8b918e6ec7881cc2 0 1 4474 4106 2026-04-30T16:55:27Z Atmois 13 remove atl references wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[ATL:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/2VRwHawnFd Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[ATL:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''atl.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> </div> </div> c7454e54fd97f9195eca0d4bec5cd23f0fe4f739 4477 4474 2026-04-30T17:02:28Z Atmois 13 fix reference wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[ATL:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/2VRwHawnFd Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[ATL:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> </div> </div> cdd193c4a6a64e07df92c9e0a2c3e3e8bfce82d7 4478 4477 2026-04-30T18:36:34Z Atmois 13 fix link wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] [https://discord.gg/linux <span class="home-button">💬 Our Discord Server</span>] </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[ATL:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[ATL:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> </div> </div> c2cc3805a8081fbdf9803e235f5badc20cdb8de0 4480 4478 2026-04-30T20:22:44Z Atmois 13 fix link wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.gg/pV67V6GBrg 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[ATL:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[ATL:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> </div> </div> 0d6d1a86d1f03c2b3448b72c0d5284c28beb5f8f 4497 4480 2026-05-01T19:03:27Z Atmois 13 update command wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[ATL:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[ATL:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.gg/pV67V6GBrg 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[ATL:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[ATL:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[ATL:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[ATL:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[ATL:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[ATL:Guidelines|guidelines]] page and the [[ATL:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[ATL:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[ATL:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> </div> </div> ffc70c6bc17a0cc75f668d08dd176b4d1fd3935c 4500 4497 2026-05-01T20:32:54Z Atmois 13 update page links wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.gg/pV67V6GBrg 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! </center> </div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[FW:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[FW:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> </div> </div> 0dd8dc159b70eb4101df5acdd11935493e77f2bf 4 595 4475 3750 2026-04-30T16:57:54Z Atmois 13 update email info wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.gg/2VRwHawnFd Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for a Wiki Administrator. You may also direct message <code>@atmois</code> (Head of Wiki Operations) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''admin(at)foss.wiki'' To report security vulnerabilities please see our [https://foss.wiki/FW:Security Security Policy]. * [[User:Atmois|Atmois]] - Wiki Director ** ''zoe(at)foss.wiki'' * [[User:Scottc96|Scott96]] - Sysadmin ** ''none'' *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''none'' fade426b0b49365f1a662feee059da04d0c75a7b 4476 4475 2026-04-30T16:58:20Z Atmois 13 update title wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.gg/2VRwHawnFd Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for a Wiki Administrator. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''admin(at)foss.wiki'' To report security vulnerabilities please see our [https://foss.wiki/FW:Security Security Policy]. * [[User:Atmois|Atmois]] - Wiki Director ** ''zoe(at)foss.wiki'' * [[User:Scottc96|Scott96]] - Sysadmin ** ''none'' *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''none'' c9fda948a6e22e863c3d923b726e9318e5e262a2 4479 4476 2026-04-30T18:38:08Z Atmois 13 fix link wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.gg/pV67V6GBrg Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''admin(at)foss.wiki'' To report security vulnerabilities please see our [https://foss.wiki/FW:Security Security Policy]. * [[User:Atmois|Atmois]] - Wiki Director ** ''zoe(at)foss.wiki'' * [[User:Scottc96|Scott96]] - Sysadmin ** ''none'' *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''none'' 7ab2814e1329c3f2f0e11c7c1417caa9ddf70da7 4498 4479 2026-05-01T19:04:12Z Atmois 13 update command wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.gg/pV67V6GBrg Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/open</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''admin(at)foss.wiki'' To report security vulnerabilities please see our [https://foss.wiki/FW:Security Security Policy]. * [[User:Atmois|Atmois]] - Wiki Director ** ''zoe(at)foss.wiki'' * [[User:Scottc96|Scott96]] - Sysadmin ** ''none'' *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''none'' aa2a109940cd46cc768a0e56c542ab7f3a618ee2 0 628 4481 4114 2026-04-30T20:24:04Z Atmois 13 remove dead link wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history. There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. In 2016, the Linux Mint website and forums were hacked and the installation images were infected with malware.<ref>{{Cite|url=https://www.pcworld.com/article/419713/hackers-planted-a-backdoor-inside-a-compromised-version-of-linux-mint.html|title=Linux Mint website hacked, ISO downloads replaced with backdoored operating system|author=Nick Mediati, PCWorld|year=2016|accessdate=2025.08.31}}</ref> The latest release, Linux Mint 22.2 "Zara", was launched on the 4th of September, 2025 and is supported until 2029.<ref>https://linuxmint.com/rel_zara.php, Linux Mint, 2006-08-09 (Accessed: 2025-09-09)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> == References == feb9cbd0119f7aa4198ac18077f301433aaf4356 4 593 4482 3050 2026-04-30T20:26:51Z Atmois 13 update references and links wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making foss.wiki an amazing resource for all users of FOSS and related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''foss.wiki''' uses. For users interested in writing guides for '''foss.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''foss.wiki''' you can see the wiki's [[ATL:About|about]] page! Some important pages are also listed below: * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[ATL:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer If you ever have any questions or need help, you can join our [https://discord.gg/pV67V6GBrg Discord Server] and check out <code>#wiki</code> for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''foss.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''foss.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''foss.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[ATL:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''foss.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another compatible free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[ATL:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it meets the standards of the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''foss.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[ATL:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. Please ensure when making new pages you follow the [[ATL:Guidelines#Notability Standards|Notability Standards]]! This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[ATL:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distro's, it lacks a lot of major distro's and each section should have a short blurb and information about key facts about what distro's under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distro's that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 5070fe36809d49433e7e145a16fd7d81bada6ed7 2 553 4483 1839 2026-04-30T20:27:04Z Atmois 13 remove dead info wikitext text/x-wiki {{UserboxWarn|This user probably exists}} 36ddeb7339c7e8c26f9a66c8a96bd3f6fdbe73a9 4 556 4484 4196 2026-04-30T20:38:35Z Atmois 13 update history and links wikitext text/x-wiki == About == '''foss.wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, check out our [[ATL:Contact|contact page]]! == Important Links == * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[Contributing]] - Outlines how YOU can contribute to foss.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[ATL:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer == Wiki Staff == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director ====== Operators ====== * [[User:Ow0cast|Ow0cast]] - Wiki Team * [[User:Scottc96|Scott96]] - Sysadmin == <u>History (Independence)</u> ~ ''April 2026 - Present'' == '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. Some changes made include ... == <u>History (All Things Linux Ownership)</u> ~ ''May 2024 - March 2026'' == ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. With 1.0 we... ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[ATL:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] 644134f74b0c7ea7edab87cc60538ee3abf061f9 828 609 4485 2929 2026-04-30T21:07:24Z Atmois 13 update name Scribunto text/plain local p = {} function p.stats() local siteStats = mw.site.stats local totalEdits = siteStats.edits local totalUsers = siteStats.users local function countPages(ns) return siteStats.pagesInNamespace(ns) or 0 end local pageCount = countPages(0) + countPages(3000) return string.format( "foss.wiki has [[Special:AllPages| %d pages]] consisting of [[Special:RecentChanges| %d edits]] from [[Special:ListUsers| %d users]]!", pageCount, totalEdits, totalUsers ) end return p f843433e268daf255cd8d12884c1e50ef92fa859 4 536 4486 2264 2026-04-30T21:10:04Z Atmois 13 update references wikitext text/x-wiki === 1. Safe for Work (SFW) Policy === foss.wiki is a '''Safe for Work (SFW)''' environment. '''NSFW (Not Safe for Work) content and discussions are strictly prohibited'''. While NSFW typically refers to sexually explicit material, the definition may evolve to include other forms of sensitive content. This applies to all content on the wiki, including but not limited to text, images & media. ==== Prohibited Content: ==== * '''Sexually explicit material''' in any form. * '''Violence, gore, or depictions of animal abuse'''. * '''Glorification of self-harm or suicide'''. == 2. Mutual Respect == foss.wiki is a '''respectful''' and '''inclusive''' community. ==== Expected Behaviour: ==== * Treat others '''with humility and respect'''. * Keep interactions '''constructive and considerate'''. * '''No harassment''': Bullying, doxxing, or coordinated attacks are '''strictly prohibited'''. * '''No hate speech''': Discriminatory remarks on any personal characteristics will not be tolerated. * '''No threats''': Direct or indirect threats against individuals or groups will result in '''immediate action'''. == 3. Responsible Expression & Discussions == The wiki welcomes '''diverse perspectives''' and encourages constructive discussions, but it is not a '''free-for-all debate forum'''. Please ensure all discussions are kept to talk pages and not done on articles unless it has been designated as a discussion page. ==== Guidelines for Expression: ==== * '''Stay on topic''': Discussions should focus on '''Linux, open-source software, and related technologies'''. * '''No disruptive debates''': Heated, repetitive, or toxic arguments will be moderated. * '''Avoid professional advice''': The wiki does not provide '''medical, legal, financial, or religious advice'''. == 4. Avoidance of Elitism == Linux and technology is for '''everyone''', from beginners to experts. ==== Expected Behaviour: ==== * '''Respect different choices''': Users may prefer different '''distro's, desktop environments, package managers, or workflows'''. * '''No gate-keeping''': Beginners should feel welcome, not discouraged. We want to foster a growing Linux and FOSS community. == 5. Respecting Moderators & Rules == Moderators help maintain order. If a moderator asks you to '''modify behaviour, please cooperate'''. * '''Disagreements should be handled via the wiki staff''', not public disputes. * '''Do not backseat moderate''': If someone breaks a rule, report it instead of escalating the situation. == 6. Language Requirement: English Only == * The wiki uses '''English as the primary language'''. == 7. Content Guidelines == All contributions must align with the wiki’s '''goal of providing high-quality Linux documentation'''. ==== Prohibited Content: ==== * Low-effort, spam, or non-constructive edits. * Off-topic material unrelated to Linux, open-source software or general technology. * Unverified or misleading technical information. * Spam or self-promoting content not relevant to the article. * AI Generated images are prohibited unless it is relevant to an article and clearly disclosed as being AI generated. * Use of generative AI to write content which will be published on the wiki is prohibited. However, AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used is permitted. == 8. Privacy & Security == * Do not doxx or share personal information of other users. * Be cautious about sharing your own information. == 9. Enforcement & Punishments == Moderators '''reserve the right''' to take appropriate action depending on the severity of violations. If you believe a '''member of the team has abused their powers''', it should be '''reported to the administrators''' through a method listed [[Main Page#Contacts|here]]. ==== Possible Actions: ==== * '''Warnings''': Used for minor infractions. * '''Blocks''': Temporary restrictions from editing or participating. * '''IP Blocks''': Restricting editing access entirely. == 10. Punishment Evasion & Appeals == * Using alt accounts, VPN's or proxies to evade punishments will result in further punishment for yourself. * If you believe a punishment was unfair, you may appeal by contacting an administrator through a method listed [[Main Page#Contacts|here]]. == 11. Final Note: Exercise Common Sense == Not every situation can be predicted. Use '''good judgement, respect others, and contribute positively''' to the Linux community. If in doubt, '''ask for clarification rather than assuming'''. Thank you for being part of the '''FOSS Wiki'''! [[Category:Meta]] b496d75015f2cf20edbeb86a04b1bffda9c3478c 4501 4486 2026-05-02T11:57:00Z Atmois 13 fix wording wikitext text/x-wiki === 1. Safe for Work (SFW) Policy === foss.wiki is a '''Safe for Work (SFW)''' environment. '''NSFW (Not Safe for Work) content and discussions are strictly prohibited'''. While NSFW typically refers to sexually explicit material, the definition may evolve to include other forms of sensitive content. This applies to all content on the wiki, including but not limited to text, images & media. ==== Prohibited Content: ==== * '''Sexually explicit material''' in any form. * '''Violence, gore, or depictions of animal abuse'''. * '''Glorification of self-harm or suicide'''. == 2. Mutual Respect == foss.wiki is a '''respectful''' and '''inclusive''' community. ==== Expected Behaviour: ==== * Treat others '''with humility and respect'''. * Keep interactions '''constructive and considerate'''. * '''No harassment''': Bullying, doxxing, or coordinated attacks are '''strictly prohibited'''. * '''No hate speech''': Discriminatory remarks on any personal characteristics will not be tolerated. * '''No threats''': Direct or indirect threats against individuals or groups will result in '''immediate action'''. == 3. Responsible Expression & Discussions == The wiki welcomes '''diverse perspectives''' and encourages constructive discussions, but it is not a '''free-for-all debate forum'''. Please ensure all discussions are kept to talk pages and not done on articles unless it has been designated as a discussion page. Alternately you can utilise our [https://discord.gg/pV67V6GBrg Discord server] to have discussions with other users. ==== Guidelines for Expression: ==== * '''Stay on topic''': Discussions should focus on '''Linux, open-source software, and related technologies'''. * '''No disruptive debates''': Heated, repetitive, or toxic arguments will be moderated. * '''Avoid professional advice''': The wiki does not provide '''medical, legal, financial, or religious advice'''. == 4. Avoidance of Elitism == Technology and especially FOSS adjacent software is for '''everyone''', from beginners to experts. ==== Expected Behaviour: ==== * '''Respect different choices''': Users may prefer different '''distro's, desktop environments, package managers, or workflows'''. * '''No gate-keeping''': Beginners should feel welcome, not discouraged. We want to foster a growing Linux and FOSS community. == 5. Respecting Moderators & Rules == Moderators help maintain order. If a moderator asks you to '''modify behaviour, please cooperate'''. * '''Disagreements should be handled via the wiki staff''', not public disputes. * '''Do not backseat moderate''': If someone breaks a rule, report it instead of escalating the situation. == 6. Language Requirement: English Only == * The wiki uses '''English as the primary language'''. == 7. Content Guidelines == All contributions on the wiki must align with the wiki’s '''goal of providing high-quality FOSS and Linux documentation'''. ==== Prohibited Content: ==== * Low-effort, spam, or non-constructive edits. * Off-topic material unrelated to Linux, open-source software or general technology. * Unverified or misleading technical information. * Spam or self-promoting content not relevant to the article. * AI Generated images are prohibited unless it is relevant to an article and clearly disclosed as being AI generated. * Use of generative AI to write content which will be published on the wiki is prohibited. However, AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used is permitted. == 8. Privacy & Security == * Do not doxx or share personal information of other users. * Be cautious about sharing your own information. == 9. Enforcement & Punishments == Moderators '''reserve the right''' to take appropriate action depending on the severity of violations. If you believe a '''member of the team has abused their powers''', it should be '''reported to the administrators''' through a method listed [[Main Page#Contacts|here]]. ==== Possible Actions: ==== * '''Warnings''': Used for minor infractions. * '''Blocks''': Temporary restrictions from editing or participating. * '''IP Blocks''': Restricting editing access entirely. == 10. Punishment Evasion & Appeals == * Using alt accounts, VPN's or proxies to evade punishments will result in further punishment for yourself. * If you believe a punishment was unfair, you may appeal by contacting an administrator through a method listed [[Main Page#Contacts|here]]. == 11. Final Note: Exercise Common Sense == Not every situation can be predicted. Use '''good judgement, respect others, and contribute positively''' to the Linux community. If in doubt, '''ask for clarification rather than assuming'''. Thank you for being part of the '''FOSS Wiki'''! [[Category:Meta]] 7ef1f95623412466e4b84ac3c1a58a8eb54c8e2e 8 400 4487 3520 2026-05-01T12:26:38Z Atmois 13 update footer wikitext text/x-wiki The FOSS Wiki aims to provide reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software! If you want to reach out to us or contribute, ensure to check out our [https://discord.gg/pV67V6GBrg Discord server]! You can see the raw content for the page you are on [{{fullurl:{{FULLPAGENAME}}|action=raw}} here]! 2a7f0663b9e68f0995b7a84a864488653899cd2c 4488 4487 2026-05-01T12:27:09Z Atmois 13 move raw content link wikitext text/x-wiki The FOSS Wiki aims to provide reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software! If you want to reach out to us or contribute, ensure to check out our [https://discord.gg/pV67V6GBrg Discord server]! 73df5d784a1e4aaf221093a7240936b834f7d674 8 404 4489 1397 2026-05-01T12:27:27Z Atmois 13 add raw content link wikitext text/x-wiki 🐧 You can see the raw content for the page you are on [{{fullurl:{{FULLPAGENAME}}|action=raw}} here]! 739b9c1205b2349ff9b23b66968135d58a456c8c 8 196 4490 4107 2026-05-01T12:38:31Z Atmois 13 Update information javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://foss.wiki/FW:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://analytics.foss.wiki/script.js'; s.setAttribute('data-website-id', 'TEMP'); document.head.appendChild(s); 0b20119feabd6c4a7818dfa5cb6f105798dbf188 4502 4490 2026-05-02T12:41:20Z Atmois 13 update id javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://foss.wiki/FW:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://analytics.foss.wiki/script.js'; s.setAttribute('data-website-id', 'c9d43ea2-5db7-4ec7-abee-816cdf1c701f'); document.head.appendChild(s); 6d32fd52a6eab00383d9a375744e602ebdefccb3 4503 4502 2026-05-02T12:53:55Z Atmois 13 update umami analytics javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://foss.wiki/FW:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://analytics.foss.wiki/script.js'; s.setAttribute('data-website-id', 'TEMP'); s.onload = function () { mw.loader.using('mediawiki.user').then(function () { var userName = mw.config.get('wgUserName'); if (userName && typeof umami !== 'undefined') { umami.identify({ id: userName }); } }); }; document.head.appendChild(s); 2325a91a4e77c836bc72e1e9114d66c26c8393c9 4504 4503 2026-05-02T13:11:08Z Atmois 13 fix id javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://foss.wiki/FW:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://analytics.foss.wiki/script.js'; s.setAttribute('data-website-id', 'c9d43ea2-5db7-4ec7-abee-816cdf1c701f'); s.onload = function () { mw.loader.using('mediawiki.user').then(function () { var userName = mw.config.get('wgUserName'); if (userName && typeof umami !== 'undefined') { umami.identify({ id: userName }); } }); }; document.head.appendChild(s); 8a98ec10aca5d5e92d4b9e08e85fc70e748b72c3 4505 4504 2026-05-02T13:39:11Z Atmois 13 update script javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://foss.wiki/FW:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://analytics.foss.wiki/script.js'; s.setAttribute('data-website-id', 'c9d43ea2-5db7-4ec7-abee-816cdf1c701f'); s.onload = function () { mw.loader.using('mediawiki.user').then(function () { var userName = mw.config.get('wgUserName'); if (userName && typeof umami !== 'undefined') { umami.identify(userName); } }); }; document.head.appendChild(s); 81b8a7fb6432c9f5407905f274fd91ae8755fd83 4506 4505 2026-05-02T13:49:03Z Atmois 13 Revert javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://foss.wiki/FW:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://analytics.foss.wiki/script.js'; s.setAttribute('data-website-id', 'c9d43ea2-5db7-4ec7-abee-816cdf1c701f'); s.onload = function () { mw.loader.using('mediawiki.user').then(function () { var userName = mw.config.get('wgUserName'); if (userName && typeof umami !== 'undefined') { umami.identify({ id: userName }); } }); }; document.head.appendChild(s); 801928976d510ffcbfb2830f0a52a02159648cc4 4 541 4491 1797 2026-05-01T13:31:57Z Atmois 13 change references wikitext text/x-wiki All content unless specified otherwise is available under [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en Creative Commons Attribution-ShareAlike 4.0 International]. '''foss.wiki''' is an online collaborative source of information which is contributed to by individuals to provide a common resource of knowledge on Linux and FOSS related topics. The project is structured, so almost anyone can contribute and alter the content. Please note that any content found on '''foss.wiki''' has been verified by an expert in the relevant field. This does not mean you will not find valuable and accurate information on '''foss.wiki'''. However, '''foss.wiki''' cannot guarantee the validity of the information found here. The content of any given article may recently have been altered by someone whose personal beliefs may not align with established knowledge in the relevant fields. When you use '''foss.wiki''' you acknowledge the following: * <big>'''Review of Information'''</big><br>Whilst editors and '''foss.wiki''' team members attempt to review changes as much and often as we can, we cannot guarantee all pages are reviewed at the same frequency or rigour and that even a small change to a once reviewed page can invalidate the review. * <big>'''No Contract'''</big><br>All information on the wiki is provided freely with no contractual obligation between you, '''foss.wiki''' and its team, anyone who provides service to '''foss.wiki''' or any of the contributors. We are not responsible for information modified or removed on '''foss.wiki''' and the only agreement between you and '''foss.wiki''' is [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en Creative Commons Attribution-ShareAlike 4.0 International]. * <big>'''Trademarks'''</big><br>Any of the trademarks, service marks, collective marks, design rights, or similar rights that are mentioned, used, or cited on '''foss.wiki''' are the property of their respective owners. Their use here does not imply that you may use them for any purpose other than for the same or a similar informational use as contemplated by the original authors of these '''foss.wiki'''. Unless otherwise stated, '''foss.wiki''' is not endorsed by, nor affiliated with, any of the holders of any such rights, and as such, '''foss.wiki''' cannot grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk. * <big>'''Jurisdiction'''</big><br>'''foss.wiki''' content is stored on servers in Germany, and is maintained in reference to the protections afforded under German federal and EU law. Laws in your country or jurisdiction may not protect or permit the same kinds of speech or distribution. '''foss.wiki''' does not advocate for the violation of any laws and cannot be held responsible for any violations of such laws. * <big>'''Professional Advice'''</big><br>'''foss.wiki''' is not a source of professional advice, if you require professional advice please consult a professional who is licensed or knowledgeable in that area. 47146bfa8846aaa7a7a92c5971d93bc5a7496b34 4 646 4492 3489 2026-05-01T13:34:55Z Atmois 13 add notice and update info wikitext text/x-wiki Please note this feature is currently disabled, it will be re-enabled in the coming weeks. Sorry for any inconvinience. == '''<u>DO NOT share the link provided with anyone, including any staff members.</u>''' == To link your Discord and '''foss.wiki''' accounts in our [https://discord.gg/pV67V6GBrg discord server], type <code>/verify</code> using '''''@wiki'''''. You will receive a private link in your DM's, Then click the link, press '''Allow''', and return to Discord, if your '''foss.wiki''' account is at least '''3 days old''', and has met the '''minimum edit threshold of 10 edits''', you will automatically be given the '''''@Editor''''' role, which comes with bonus perks in the Discord server. You may need to wait up to an hour for the role to be given. If you do not receive it open a ticket with <code>/ticket</code> and ask for help. If you have met the requirements '''after''' initially verifying, run <code>/unverify</code> then go through the verification process again, this will refresh your role. To see if you meet the requirements, visit the [[Special:UserRights]] page, search your username, and see if you're an ''implicit member of "Autoconfirmed Users"''. This role is automatically given by the wiki to users who meet the criteria. 0fb4c611dc7ec695a6f18ee61d5d0b14a80a7916 4 340 4493 4393 2026-05-01T13:36:05Z Atmois 13 update references wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; foss.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[ATL:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[ATL:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[ATL:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[ATL:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[ATL:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[ATL:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[ATL:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[ATL:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>ATL:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://atl.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[ATL:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''foss.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] f0bf4b49d8a7512d5533e49a358ad3d3a4902a52 4509 4493 2026-05-03T14:50:20Z Atmois 13 fix links wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; foss.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[FW:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[FW:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Consistency</u> ===== Ensure that your page is consistent with other pages and follows our standards through the '''formatting, language, and terminology used.''' Further details and specifics on how we wish to approach this on the wiki can be seen in the [[Guidelines#Formatting|Formatting Guidelines]]. If there is any doubt, '''consult an admin.''' In general as long as the language used is consistent with the rest of the page and the terminology is used correctly, use your best judgement on how to format and layout the page. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[FW:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[FW:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[FW:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[FW:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[FW:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[FW:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>FW:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://foss.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[FW:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''foss.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 06b8c207379a6128da8c6feb6478da5d84203ab0 4 571 4494 2807 2026-05-01T13:39:00Z Atmois 13 Update sitename information and contact information (1 May 2026) wikitext text/x-wiki = foss.wiki Privacy Policy = Last Updated: 1 May 2026<blockquote>Update: Update sitename information and contact information</blockquote>Welcome to '''foss.wiki'''<nowiki/>'s Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''foss.wiki'''. By accessing or contributing to '''foss.wiki''', you agree to the terms outlined in this Privacy Policy. == <u>Information foss.wiki Collects</u> == When you edit any article or page on '''foss.wiki''', you are creating a permanent, public record of any change, addition, removal made by you. Public records will show the time and username authoring the edits. ''To contribute to '''foss.wiki''', you are required to create an account. When registering, '''foss.wiki''' collects:'' * A Username * [Optionally] Your Email Address <blockquote>Other information such as your pronouns, Discord ID and full name may be optionally provided to us via your user preferences or our Discord linking service.</blockquote> When a user is logged in '''foss.wiki''' uses essential cookies to maintain your login session and preferences. These cookies are required for the site to function and not shared nor used across other sites. Upon visiting the wiki the web-server will automatically log your IP Address and your User Agent, this information helps identify technical issues and ensure compatibility across devices. The web-server logs are automatically cleared regularly. The IP address of an editor will also be logged by Mediawiki when an edit has been made for anti-vandalism efforts. The logged IP is only available to administrators and will only be used for the purpose of blocking or sanctioning malicious users. <blockquote>The logging is provided by the [[mediawikiwiki:Extension:CheckUser|Check User Extension]].</blockquote> ==== Services foss.wiki Uses ==== '''foss.wiki''' uses a self-hosted instance of Umami Analytics to collect anonymous data about how visitors interact with our website. Umami collects: Page views, referring website and user agents. Umami does not collect personal data or use cookies, this data allows us to improve our site’s performance and user experience. <blockquote>For more details, please see [https://umami.is/docs Umami's Documentation].</blockquote> '''foss.wiki''' also uses Cloudflare to enhance website security and performance. Cloudflare may process certain technical information, such as IP addresses and user agents, to provide services like content delivery, DDoS protection, and caching. Cloudflare also makes use of cookies of cookies to manage bot protection and verify access. These cookies are required for site security and functionality, these cookies are not shared nor used across other sites. <blockquote>For more details, please see [https://www.cloudflare.com/en-gb/privacypolicy/ Cloudflare’s Privacy Policy].</blockquote> === <u>How foss.wiki uses your Information</u> === '''foss.wiki''' does not sell, trade, or otherwise transfer your personal information to third parties. '''foss.wiki''' will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where '''foss.wiki''' is present. '''foss.wiki''' will never provide your information to third parties without your explicit consent. '''''foss.wiki''' use your data to do the following:'' * To send administrative notices via email. * For the ability to reset your account password via email. * To moderate and combat vandalism & spam on the wiki. * To correctly attribute contributions on the wiki to users. * To monitor and analyse the usage of our services and identify technical issues. '''foss.wiki''' uses a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so '''foss.wiki''' cannot guarantee that our security will not be breached. In the event of a data breach, '''foss.wiki''' will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities. == <u>Your Rights</u> == ''Under the General Data Protections Act you are afforded the following rights:'' ; Right to be informed: : The right to be informed about the collection and use of their personal data. ; Right to access: : The right to access and receive a copy of their personal data, and other supplementary information. ; Right to rectification: : The right to have inaccurate personal data rectified, or completed if it is incomplete. ; Right to erasure: : The right to have personal data erased (Also known as being "forgotten"). ; Right to restrict processing: : The right to request the restriction or suppression of their personal data. ; Right to data portability: : The right to obtain and reuse their personal data for their own purposes across different services. ; Right to object: : The right to object to the processing of their personal data in certain circumstances. ; Right to control automated decision making: : The right to be informed about automated decision systems and are allowed to request human review. In order to comply with GDPR erasure requests and the licensing of content, '''foss.wiki''' has implemented a process to remove all your data from '''foss.wiki'''. Your account name will be anonymised and your edits will be reattributed to the anonymised username. You will be asked to remove your email and other personal information provided to us via your user preferences. Once this process has been completed your account will be "vanished", which removes it from public logs, then your account will be blocked to prevent future logins. == <u>Changes to the Privacy Policy</u> == '''foss.wiki''' may change the Privacy Policy as needed to represent changes in our practises or legal requirements. '''foss.wiki''' will notify users of updates that impact them, and all revisions will be available on this page. == <u>Third-party Links</u> == '''foss.wiki''' may contain links to third-party websites. '''foss.wiki''' is not responsible for the privacy practices or content of these sites. '''foss.wiki''' encourages users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>privacy@foss.wiki</code>. 8fd6172fe38316406c821f9b474ec055ffa1f0cd 4 327 4495 4440 2026-05-01T13:51:03Z Atmois 13 remove dead link wikitext text/x-wiki linux is cool. why? because i said so. bye [[File:Bazzitehyfetch.png|alt=test|thumb]] =References= 5907cd39eeabb05bb97b00b874715a27b1679798 4 876 4496 3745 2026-05-01T13:57:54Z Atmois 13 Create security policy wikitext text/x-wiki == Security at FOSS Wiki == At FOSS Wiki, we are committed to maintaining the highest security standards to protect our community and infrastructure. We deeply value the security research community and actively encourage responsible disclosure of security vulnerabilities. Your contributions help us ensure the safety, privacy, and integrity of our platforms and services. We believe in transparency and collaboration when it comes to security. Our team is dedicated to investigating all reported issues promptly and working with researchers to address vulnerabilities in a timely and responsible manner. === Scope === This security policy applies to all FOSS Wiki projects and services, including but not limited to: * Our domains and all of its subdomains: '''foss.wiki''' * API endpoints, back-end services, Discord bot services or integrations, and community platforms or forums * Repositories within the FOSS Wiki GitHub/Codeberg organisation We are interested in any vulnerability that could lead to unauthorised access, data breaches, or service disruptions. We welcome any reports of potential vulnerabilities outside of this scope but we may not be able to address them immediately. Please also note that we also host and utilise external services, we also welcome reports regarding those services but we may not be able to address them directly and will refer you to the appropriate party. === How to Report a Security Issue === If you have discovered a security vulnerability, please help us keep our community safe by reporting it responsibly. When reporting, please include: * A clear description of the vulnerability and its potential impact * Detailed steps to reproduce the issue * Information about the environment where you discovered the issue * Any proof-of-concept code or evidence of the vulnerability (if applicable) * Any recommendations or patches you may have for resolving the issue === Contact === All reports should be directed to our email, [mailto:security@foss.wiki security@foss.wiki] and if required, using the PGP found at https://foss.wiki/securityatfosswiki.asc. Alternatively, you may open a ticket in our [https://discord.gg/pV67V6GBrg Discord server] and request assistance there. '''Please do not disclose''' '''vulnerability details in the ticket unless requested by an administrator.''' === Responsible Disclosure Guidelines === We require that you: * Do not make use of any vulnerabilities without explicit permission to do so from a member of Wiki Leadership * Do not access, copy, or destroy data that is not available without authentication/authorisation in any capacity * Do not disrupt our services or degrade the performance of our services * Keep vulnerability details confidential until we have addressed the issue and agreed to a planned disclosure * Give us reasonable time (typically 30 days, although you will be informed of the estimated time) to investigate and resolve the issue === Safe Harbour === Any activities conducted in a manner consistent with this policy will be considered authorised conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will ensure it is known that your actions were conducted in compliance with this policy. === Recognition === We appreciate security researchers and individuals who help keep our community safe. If you would like to be acknowledged for your responsible disclosure, please let us know in your report and we'll be happy to recognise your contribution publicly. However, please note we do not have the ability to award bug bounties or monetary reward for any disclosed vulnerabilities due to the nature of the project. We also welcome you to post your own report and/or analysis once we have resolved and disclosed the vulnerability publicly ourselves, '''we only request you send it to us 1 week before you plan to publish it.''' c2b3703f1e102329371bd48035bcd54fe3ce5393 4499 4496 2026-05-01T19:04:28Z Atmois 13 add command wikitext text/x-wiki == Security at FOSS Wiki == At FOSS Wiki, we are committed to maintaining the highest security standards to protect our community and infrastructure. We deeply value the security research community and actively encourage responsible disclosure of security vulnerabilities. Your contributions help us ensure the safety, privacy, and integrity of our platforms and services. We believe in transparency and collaboration when it comes to security. Our team is dedicated to investigating all reported issues promptly and working with researchers to address vulnerabilities in a timely and responsible manner. === Scope === This security policy applies to all FOSS Wiki projects and services, including but not limited to: * Our domains and all of its subdomains: '''foss.wiki''' * API endpoints, back-end services, Discord bot services or integrations, and community platforms or forums * Repositories within the FOSS Wiki GitHub/Codeberg organisation We are interested in any vulnerability that could lead to unauthorised access, data breaches, or service disruptions. We welcome any reports of potential vulnerabilities outside of this scope but we may not be able to address them immediately. Please also note that we also host and utilise external services, we also welcome reports regarding those services but we may not be able to address them directly and will refer you to the appropriate party. === How to Report a Security Issue === If you have discovered a security vulnerability, please help us keep our community safe by reporting it responsibly. When reporting, please include: * A clear description of the vulnerability and its potential impact * Detailed steps to reproduce the issue * Information about the environment where you discovered the issue * Any proof-of-concept code or evidence of the vulnerability (if applicable) * Any recommendations or patches you may have for resolving the issue === Contact === All reports should be directed to our email, [mailto:security@foss.wiki security@foss.wiki] and if required, using the PGP found at https://foss.wiki/securityatfosswiki.asc. Alternatively, you may open a ticket with <code>/open</code> in our [https://discord.gg/pV67V6GBrg Discord server] and request assistance there. '''Please do not disclose''' '''vulnerability details in the ticket unless requested by an administrator.''' === Responsible Disclosure Guidelines === We require that you: * Do not make use of any vulnerabilities without explicit permission to do so from a member of Wiki Leadership * Do not access, copy, or destroy data that is not available without authentication/authorisation in any capacity * Do not disrupt our services or degrade the performance of our services * Keep vulnerability details confidential until we have addressed the issue and agreed to a planned disclosure * Give us reasonable time (typically 30 days, although you will be informed of the estimated time) to investigate and resolve the issue === Safe Harbour === Any activities conducted in a manner consistent with this policy will be considered authorised conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will ensure it is known that your actions were conducted in compliance with this policy. === Recognition === We appreciate security researchers and individuals who help keep our community safe. If you would like to be acknowledged for your responsible disclosure, please let us know in your report and we'll be happy to recognise your contribution publicly. However, please note we do not have the ability to award bug bounties or monetary reward for any disclosed vulnerabilities due to the nature of the project. We also welcome you to post your own report and/or analysis once we have resolved and disclosed the vulnerability publicly ourselves, '''we only request you send it to us 1 week before you plan to publish it.''' 4c39a26357687d13a6d98d061369ea2aac632746 10 521 4507 3527 2026-05-03T14:47:45Z Atmois 13 fix link wikitext text/x-wiki This warning is placed on any page that lists a command and gives users instructions to follow, it exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[FW:Contact|administrator]] immediately. == Usage == <code>{{tlx|Guide_Warning}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 2a70b67cdaf4248794120bbf0ee2b5add3749ff6 10 482 4508 3526 2026-05-03T14:48:05Z Atmois 13 fix link wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section lists commands or instructions which could potentially damage your system. Please ensure you understand the commands or instructions you are running or following before you run or follow them.</span> <div class="mbox-text">This warning exists to make users wary of running random commands or following instructions they see on the internet blindly and that they understand what they are doing to their system. Dangerous commands or instructions should be reported to an [[FW:Contact|administrator]] immediately.</div> </div><templatestyles src="Module:Mbox/styles.css" /><noinclude> {{/doc}}</noinclude> ebcd7ad37225d1201867482b0d34ef0d111a66b6 0 387 4510 1486 2026-05-03T14:51:44Z Atmois 13 fix double redirect wikitext text/x-wiki #REDIRECT [[Window Management System]] daa1f2c89177e4a5b11bdee2be6246557141d249 0 343 4511 1244 2026-05-03T14:52:10Z Atmois 13 fix double redirect wikitext text/x-wiki #REDIRECT [[Window Management System]] daa1f2c89177e4a5b11bdee2be6246557141d249 10 693 4512 2593 2026-05-03T14:52:41Z Atmois 13 Fix double redirect wikitext text/x-wiki #REDIRECT [[Template:Key_Press]] 2b0da6577828dec1de8f8e18229c5dbf155299c2 0 398 4513 1386 2026-05-03T14:53:02Z Atmois 13 Fix double redirect wikitext text/x-wiki #REDIRECT [[Key Terms]] 8bd6c2b36726c38e712a9c8dbf427c6543eb40d6 10 524 4514 3529 2026-05-03T14:54:01Z Atmois 13 fix link wikitext text/x-wiki This is to be placed by the author of a page when they are still actively working on the page to notify other editors to check with them to not create conflicting changes and to notify the staff that it may not meet the [[FW:Guidelines|contributing standards]] yet. == Usage == <code>{{tlx|Work_In_Progress}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 25d3b8d09cc19cd489f84716323d533d38bd9214 10 514 4515 3523 2026-05-03T14:54:09Z Atmois 13 fix link wikitext text/x-wiki This template should be placed on pages which may lack credible citations, as per our [[FW:Guidelines#Citations|citations policy]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations. == Usage == <code>{{tlx|Needs Citations}}</code> <includeonly>[[Category:Maintenance Templates]]</includeonly> 91af6692a0d8e83ed1554e02f51d9b0624e181f8 10 494 4516 3521 2026-05-03T14:54:19Z Atmois 13 fix link wikitext text/x-wiki This template should be placed on pages which might not meet the wiki's [[FW:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed. == Usage == <code>{{tlx|Cleanup|Reason}}</code> == TemplateData == <templatedata> { "params": { "1": { "label": "Reason", "description": "Reason why article requires cleanup", "example": "Biased Tone", "type": "string", "required": true } }, "description": "Place on articles or sections you believe require a cleanup. This template adds pages to Category:Pages needing cleanup.\n\n", "format": "inline" } </templatedata> <includeonly>[[Category:Maintenance Templates]]</includeonly> 932485279e0a00fbe561a0b3c42c894e218f7b83 3000 572 4517 4394 2026-05-03T14:55:25Z Atmois 13 fix link wikitext text/x-wiki == TL;DR == Ensure you have the '''[[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]]''' template on the page, and all changes MUST be approved by staff for public viewing via <code>ApprovedRevs</code>. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Definition == Guides are '''''anything that explain to a user how to do something beyond a link to another source or a brief instruction'''''. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide on hardening Firefox with more privacy focused options, a higher standard of quality and safety than standard articles SHOULD be maintained for guides. This is because unlike normal articles that only provide factual information, guides contain instructions for users to do things to their systems, which could potentially damage the systems or cause data loss. == Policies == All main wiki policies apply, including but not limited to the [[FW:Code of Conduct|Code of Conduct]] and the wiki [[FW:Guidelines|guidelines]]. We also recommend you check out our [[FW:Contributing|Contributing page]] as well, which has a lot of important and useful information for editors. In addition, a special set of criteria are required, as outlined below: * All guides MUST ''start'' with [[Template:Guide Warning]]. ** There are no exceptions to this rule, and violations of the rule entail all edits to be rejected until the template's addition. ** Add it using <code><nowiki>{{GuideWarning}}</nowiki></code> or <code><nowiki>{{Guide Warning}}</nowiki></code> at the beginning of the page: ** {{Guide Warning}} * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this: ** Double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. ** Aim to provide unbiased and informative content to all users. Your personal views, regardless of validity, are irrelevant here. * You are responsible for ensuring all instructions you provide are safe and functional. ** In guides, any foreseeable risks with running a specific command MUST be clearly stated. ** Ensure to clearly outline, if any, the requirements and prerequisites of the commands. ** Any dangerous commands provided will be held accountable to whomever adds them to a guide. A good example guide would be '''[[Guides:Setting up Flathub on Fedora]]''', which is maintained and has been made in accordance with our guidelines and standards. a9d49602d754aa9b142dbfcbddc50df45077e0d8 4518 4517 2026-05-03T14:55:52Z Atmois 13 Remove outdated info wikitext text/x-wiki == TL;DR == Ensure you have the '''[[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]]''' template on the page. Ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Definition == Guides are '''''anything that explain to a user how to do something beyond a link to another source or a brief instruction'''''. Be that a 10000-word article on how to set up your own email server using RHEL 9 or a quick guide on hardening Firefox with more privacy focused options, a higher standard of quality and safety than standard articles SHOULD be maintained for guides. This is because unlike normal articles that only provide factual information, guides contain instructions for users to do things to their systems, which could potentially damage the systems or cause data loss. == Policies == All main wiki policies apply, including but not limited to the [[FW:Code of Conduct|Code of Conduct]] and the wiki [[FW:Guidelines|guidelines]]. We also recommend you check out our [[FW:Contributing|Contributing page]] as well, which has a lot of important and useful information for editors. In addition, a special set of criteria are required, as outlined below: * All guides MUST ''start'' with [[Template:Guide Warning]]. ** There are no exceptions to this rule, and violations of the rule entail all edits to be rejected until the template's addition. ** Add it using <code><nowiki>{{GuideWarning}}</nowiki></code> or <code><nowiki>{{Guide Warning}}</nowiki></code> at the beginning of the page: ** {{Guide Warning}} * Due to the nature of guides, bias is much more likely to be shown. Extra care must be taken to avoid this: ** Double-check the tone and structure of your guide to ensure you are not misleading users or trying to convince them your method is better than others. ** Aim to provide unbiased and informative content to all users. Your personal views, regardless of validity, are irrelevant here. * You are responsible for ensuring all instructions you provide are safe and functional. ** In guides, any foreseeable risks with running a specific command MUST be clearly stated. ** Ensure to clearly outline, if any, the requirements and prerequisites of the commands. ** Any dangerous commands provided will be held accountable to whomever adds them to a guide. A good example guide would be '''[[Guides:Setting up Flathub on Fedora]]''', which is maintained and has been made in accordance with our guidelines and standards. fe0309c38ff4bd2a0683031c1298002f071ad4c9 10 483 4519 3576 2026-05-03T14:58:55Z Atmois 13 fix link wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</span> <div class="mbox-text">This template means a page might not meet the wiki's [[FW:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>{{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]]}}</includeonly> <noinclude>{{/doc}}</noinclude> 16bb58d290ebb4bbc06cade540d4a042beba70e2 10 513 4520 3721 2026-05-03T14:59:04Z Atmois 13 fix link wikitext text/x-wiki <div class="mbox mbox-high mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span>This article or section has little to no citations.</span> <div class="mbox-text">This template is to be used on pages which may lack credible citations, as per our [[FW:Guidelines#Citations|citations guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. See [[:Category:Needs Citations]] for other pages that require more citations.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly> {{#ifeq:{{FULLPAGENAME}}|Category:Needs_Citations|| [[Category:Needs_Citations]] }}</includeonly> <noinclude> {{/doc}}</noinclude> 012f6212bebb5ed9e7910d1bf59f9a46f846cbfd 8 196 4521 4506 2026-05-03T22:37:47Z Atmois 13 Remove username association javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ // Enable Umami Analytics, see https://foss.wiki/FW:Privacy_policy var s = document.createElement('script'); s.defer = true; s.src = 'https://analytics.foss.wiki/script.js'; s.setAttribute('data-website-id', 'c9d43ea2-5db7-4ec7-abee-816cdf1c701f'); document.head.appendChild(s); 852d3a45983b02cef835e5716ab3f813274a229a 4 571 4522 4494 2026-05-03T22:57:00Z Atmois 13 Clarify data retention policy further and fix typos and improve wording wikitext text/x-wiki = foss.wiki Privacy Policy = Last Updated: 3 May 2026<blockquote>Update: Update sitename information and contact information, clarify data retention policy further and fix typos and improve wording</blockquote>Welcome to '''foss.wiki'''<nowiki/>'s Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''foss.wiki'''. By accessing or contributing to '''foss.wiki''', you agree to the terms outlined in this Privacy Policy. == <u>Information foss.wiki Collects</u> == When you edit any article or page on '''foss.wiki''', you are creating a permanent, public record of any change, addition, removal made by you. Public records will show the time and username authoring the edits. ''To contribute to '''foss.wiki''', you are required to create an account. When registering, '''foss.wiki''' collects:'' * A Username * [Optionally] Your Email Address <blockquote>Other information such as your pronouns, Discord ID and full name may be optionally provided to us via your user preferences or our Discord linking service.</blockquote> When a user is logged in '''foss.wiki''' uses essential cookies to maintain your login session and preferences. These cookies are required for the site to function and not shared nor used across other sites. Upon visiting the wiki the web-server will automatically log your IP Address and your User Agent, this information helps identify technical issues and ensure compatibility across devices. The web-server retains its logs for 30 days, after which it will automatically be deleted. The IP address of an editor will also be logged by Mediawiki when an edit has been made for anti-vandalism efforts. The logged IP is only available to administrators and will only be used for the purpose of blocking or sanctioning malicious users. IP's are stored for 90 days, after which it will be deleted from the logs and no longer be accessible. <blockquote>The logging is provided by the [[mediawikiwiki:Extension:CheckUser|Check User Extension]].</blockquote> == <u>Services foss.wiki Uses</u> == '''foss.wiki''' uses a self-hosted instance of Umami Analytics to collect anonymous data about how visitors interact with our website. Umami collects: Page views, referring website and user agents. Umami does not collect personal data or use cookies, this data allows us to improve our site’s performance and user experience. Please note this data is kept indefinitely and cannot be removed as it does not store any identifiable information hence cannot be removed on an individual user basis. <blockquote>For more details, please see [https://umami.is/docs Umami's Documentation].</blockquote> '''foss.wiki''' also uses Cloudflare to enhance website security and performance. Cloudflare may process certain technical information, such as IP addresses and user agents, to provide services like content delivery, DDoS protection, and caching. Cloudflare also makes use of cookies to manage bot protection and verify access. These cookies are required for site security and functionality, please note that these cookies are managed by Cloudflare under their own privacy policy and data processing agreements. <blockquote>For more details, please see [https://www.cloudflare.com/en-gb/privacypolicy/ Cloudflare’s Privacy Policy].</blockquote> == <u>How foss.wiki uses your Information</u> == '''foss.wiki''' does not sell, trade, or otherwise transfer your personal information to third parties. '''foss.wiki''' will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where '''foss.wiki''' is present. '''foss.wiki''' will never provide your information to third parties without your explicit consent. Your account data is held as long as the wiki operates or until a erasure request is completed on your account. '''''foss.wiki''' use your data to do the following:'' * To send administrative notices via email. * For the ability to reset your account password via email. * To moderate and combat vandalism & spam on the wiki. * To correctly attribute contributions on the wiki to users. * To monitor and analyse the usage of our services and identify technical issues. '''foss.wiki''' uses a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so '''foss.wiki''' cannot guarantee that our security will not be breached. In the event of a data breach, '''foss.wiki''' will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities == <u>Your Rights</u> == ''Under the General Data Protection Regulation you are afforded the following rights:'' ; Right to be informed: : The right to be informed about the collection and use of their personal data. ; Right to access: : The right to access and receive a copy of their personal data, and other supplementary information. ; Right to rectification: : The right to have inaccurate personal data rectified, or completed if it is incomplete. ; Right to erasure: : The right to have personal data erased (Also known as being "forgotten"). ; Right to restrict processing: : The right to request the restriction or suppression of their personal data. ; Right to data portability: : The right to obtain and reuse their personal data for their own purposes across different services. ; Right to object: : The right to object to the processing of their personal data in certain circumstances. ; Right to control automated decision making: : The right to be informed about automated decision systems and are allowed to request human review. In order to comply with GDPR erasure requests and the licensing of content, '''foss.wiki''' has implemented a process to remove all your data from '''foss.wiki'''. Your account name will be anonymised and your edits will be reattributed to the anonymised username. You will be asked to remove your email and other personal information provided to us via your user preferences. Once this process has been completed your account will be "vanished", which removes it from public logs, then your account will be blocked to prevent future logins. This will be performed within 30 days of '''foss.wiki''' receiving a request from the owner of the account. == <u>Changes to the Privacy Policy</u> == '''foss.wiki''' may change the Privacy Policy as needed to represent changes in our practises or legal requirements. '''foss.wiki''' will notify users of updates that impact them, and all revisions will be available on this page. == <u>Third-party Links</u> == '''foss.wiki''' may contain links to third-party websites. '''foss.wiki''' is not responsible for the privacy practices or content of these sites. '''foss.wiki''' encourages users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>privacy@foss.wiki</code>. 93064ef76e069aaa66795882c1fcbbfeb9a88d2e 4523 4522 2026-05-03T23:04:50Z Atmois 13 Add opt out information for Umami Analytics wikitext text/x-wiki = foss.wiki Privacy Policy = Last Updated: 3 May 2026<blockquote>Update: Update sitename information and contact information, clarify data retention policy further and fix typos and improve wording, add opt out information for Umami Analytics</blockquote>Welcome to '''foss.wiki'''<nowiki/>'s Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''foss.wiki'''. By accessing or contributing to '''foss.wiki''', you agree to the terms outlined in this Privacy Policy. == <u>Information foss.wiki Collects</u> == When you edit any article or page on '''foss.wiki''', you are creating a permanent, public record of any change, addition, removal made by you. Public records will show the time and username authoring the edits. ''To contribute to '''foss.wiki''', you are required to create an account. When registering, '''foss.wiki''' collects:'' * A Username * [Optionally] Your Email Address <blockquote>Other information such as your pronouns, Discord ID and full name may be optionally provided to us via your user preferences or our Discord linking service.</blockquote> When a user is logged in '''foss.wiki''' uses essential cookies to maintain your login session and preferences. These cookies are required for the site to function and not shared nor used across other sites. Upon visiting the wiki the web-server will automatically log your IP Address and your User Agent, this information helps identify technical issues and ensure compatibility across devices. The web-server retains its logs for 30 days, after which it will automatically be deleted. The IP address of an editor will also be logged by Mediawiki when an edit has been made for anti-vandalism efforts. The logged IP is only available to administrators and will only be used for the purpose of blocking or sanctioning malicious users. IP's are stored for 90 days, after which it will be deleted from the logs and no longer be accessible. <blockquote>The logging is provided by the [[mediawikiwiki:Extension:CheckUser|Check User Extension]].</blockquote> == <u>Services foss.wiki Uses</u> == '''foss.wiki''' uses a self-hosted instance of Umami Analytics to collect anonymous data about how visitors interact with our website. Umami collects: Page views, referring website and user agents. Umami does not collect personal data or use cookies, this data allows us to improve our site’s performance and user experience. Please note this data is kept indefinitely and cannot be removed as it does not store any identifiable information hence cannot be removed on an individual user basis. You can opt out of Umami's analytics for an individual device by entering <code>localStorage.setItem('umami.disabled', 1);</code> into your browser console or blocking the domain <code>analytics.foss.wiki</code> using an adblocker of your choice.. To reenable the collection you can run <code>localStorage.removeItem('umami.disabled');</code>. <blockquote>For more details, please see [https://umami.is/docs Umami's Documentation].</blockquote> '''foss.wiki''' also uses Cloudflare to enhance website security and performance. Cloudflare may process certain technical information, such as IP addresses and user agents, to provide services like content delivery, DDoS protection, and caching. Cloudflare also makes use of cookies to manage bot protection and verify access. These cookies are required for site security and functionality, please note that these cookies are managed by Cloudflare under their own privacy policy and data processing agreements. <blockquote>For more details, please see [https://www.cloudflare.com/en-gb/privacypolicy/ Cloudflare’s Privacy Policy].</blockquote> == <u>How foss.wiki uses your Information</u> == '''foss.wiki''' does not sell, trade, or otherwise transfer your personal information to third parties. '''foss.wiki''' will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where '''foss.wiki''' is present. '''foss.wiki''' will never provide your information to third parties without your explicit consent. Your account data is held as long as the wiki operates or until a erasure request is completed on your account. '''''foss.wiki''' use your data to do the following:'' * To send administrative notices via email. * For the ability to reset your account password via email. * To moderate and combat vandalism & spam on the wiki. * To correctly attribute contributions on the wiki to users. * To monitor and analyse the usage of our services and identify technical issues. '''foss.wiki''' uses a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so '''foss.wiki''' cannot guarantee that our security will not be breached. In the event of a data breach, '''foss.wiki''' will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities == <u>Your Rights</u> == ''Under the General Data Protection Regulation you are afforded the following rights:'' ; Right to be informed: : The right to be informed about the collection and use of their personal data. ; Right to access: : The right to access and receive a copy of their personal data, and other supplementary information. ; Right to rectification: : The right to have inaccurate personal data rectified, or completed if it is incomplete. ; Right to erasure: : The right to have personal data erased (Also known as being "forgotten"). ; Right to restrict processing: : The right to request the restriction or suppression of their personal data. ; Right to data portability: : The right to obtain and reuse their personal data for their own purposes across different services. ; Right to object: : The right to object to the processing of their personal data in certain circumstances. ; Right to control automated decision making: : The right to be informed about automated decision systems and are allowed to request human review. In order to comply with GDPR erasure requests and the licensing of content, '''foss.wiki''' has implemented a process to remove all your data from '''foss.wiki'''. Your account name will be anonymised and your edits will be reattributed to the anonymised username. You will be asked to remove your email and other personal information provided to us via your user preferences. Once this process has been completed your account will be "vanished", which removes it from public logs, then your account will be blocked to prevent future logins. This will be performed within 30 days of '''foss.wiki''' receiving a request from the owner of the account. == <u>Changes to the Privacy Policy</u> == '''foss.wiki''' may change the Privacy Policy as needed to represent changes in our practises or legal requirements. '''foss.wiki''' will notify users of updates that impact them, and all revisions will be available on this page. == <u>Third-party Links</u> == '''foss.wiki''' may contain links to third-party websites. '''foss.wiki''' is not responsible for the privacy practices or content of these sites. '''foss.wiki''' encourages users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>privacy@foss.wiki</code>. e10c5d8616230145fc24ea96eb400fa4fd73a312 8 624 4524 3070 2026-05-03T23:07:59Z Atmois 13 update link colour css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } 7e2538be8c2c90858f9ef75b05b262411d3f40a9 4565 4524 2026-05-12T20:21:46Z Atmois 13 Add Footer Column Configuration css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer Column Configuration */ #footer-places ul { column-count: 2; column-gap: 2rem; } #footer-places-statuspage { break-before: column; } 9371b94cbe420590ad5722462ea11da7482bf54d 0 1 4525 4500 2026-05-04T11:38:33Z Atmois 13 add quote wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.gg/pV67V6GBrg 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[FW:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[FW:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> </div> </div> 003b603fcc7d2dad59df6a970a235efdc36c3f10 4526 4525 2026-05-04T11:39:10Z Atmois 13 fix div close tag wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.gg/pV67V6GBrg 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[FW:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[FW:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div> </div> </div> 6d70fefa1a7ebe85d5b066e78c3a67ae4306439e 4541 4526 2026-05-11T13:16:26Z Atmois 13 Add recent activity log wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.gg/pV67V6GBrg 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 5 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[FW:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Consistency:''' Content should always be up to the highest of standards and be formatted according to the [[FW:Guidelines#Formatting|guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div>{{Special:RecentChanges|hidebots|namespace=0|limit=10}}</div> </div> 7f3488bdfa0cb2682ddaa54e17b85744e9469113 4544 4541 2026-05-11T13:19:21Z Atmois 13 Update key values wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.gg/pV67V6GBrg 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 4 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[FW:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div>{{Special:RecentChanges|hidebots|namespace=0|limit=10}}</div> </div> 3f4bc8c96f0a6c5b8befec71c7ff41a8785ab474 4566 4544 2026-05-14T11:44:35Z Atmois 13 Update discord links wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.foss.wiki 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users of the tools and systems! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.foss.wiki Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 4 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[FW:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div>{{Special:RecentChanges|hidebots|namespace=0|limit=10}}</div> </div> 5c6cee1312e47ba9d38187561159f4e6bb2aa3fd 4 556 4527 4484 2026-05-08T21:08:35Z Atmois 13 Add new history wikitext text/x-wiki == <u>About</u> == '''foss.wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, check out our [[ATL:Contact|contact page]]! == <u>Important Links</u> == * [[ATL:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[Contributing]] - Outlines how YOU can contribute to foss.wiki * [[ATL:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[ATL:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer == <u>Wiki Staff</u> == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director * [[User:Scottc96|Scott96]] - Wiki Director ====== Operators ====== * [[User:Ow0cast|Ow0cast]] - Wiki Team & Moderator == '''<u>History</u>''' == === <u>Independence</u> ~ ''April 2026 - Present'' === '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] (promoted to co-director) remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. With the relaunch we setup of our status page with Phare at [https://status.foss.wiki status.foss.wiki] and launched our own [https://discord.gg/pV67V6GBrg Discord Server] and partnered with [https://discord.gg/nglinux Neon Genesis Linux], a server run by [[User:Scottc96|Scott96]] to provide high quality FOSS/Linux support and discussions. Our wiki deployment code is available on our new [https://github.com/FOSS-Wiki GitHub] and we redeployed Umami analytics and updated our [[FW:Privacy policy|Privacy Policy]] to clarify some unclear data retention details as well as provide Opt Out information for Umami if users with to not be included in wiki usage analytics. Finally, we thank everyone who stuck with us especially former ATL staff for all their support and kindness during these tough times, every edit and every bit of support is valued and I am eternally grateful for everyone's help to make this fantastic resource for FOSS/Linux users, thank you and I hope to see you editing with us! ~ atmois === <u>ATL Ownership</u> ~ ''May 2024 - March 2026'' === ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. to be added: DDoS report, 1.0 release and wikibot launch ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[FW:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] 00a80e289a66ae9ea15c2c9e5e395ed47eb989ee 4528 4527 2026-05-08T21:17:29Z Atmois 13 fix links wikitext text/x-wiki == <u>About</u> == '''foss.wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, check out our [[FW:Contact|contact page]]! == <u>Important Links</u> == * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[Contributing]] - Outlines how YOU can contribute to foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer == <u>Wiki Staff</u> == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director * [[User:Scottc96|Scott96]] - Wiki Director ====== Operators ====== * [[User:Ow0cast|Ow0cast]] - Wiki Team & Moderator == '''<u>History</u>''' == === <u>Independence</u> ~ ''April 2026 - Present'' === '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] (promoted to co-director) remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. With the relaunch we setup of our status page with Phare at [https://status.foss.wiki status.foss.wiki] and launched our own [https://discord.gg/pV67V6GBrg Discord Server] and partnered with [https://discord.gg/nglinux Neon Genesis Linux], a server run by [[User:Scottc96|Scott96]] to provide high quality FOSS/Linux support and discussions. Our wiki deployment code is available on our new [https://github.com/FOSS-Wiki GitHub] and we redeployed Umami analytics and updated our [[FW:Privacy policy|Privacy Policy]] to clarify some unclear data retention details as well as provide Opt Out information for Umami if users with to not be included in wiki usage analytics. Finally, we thank everyone who stuck with us especially former ATL staff for all their support and kindness during these tough times, every edit and every bit of support is valued and I am eternally grateful for everyone's help to make this fantastic resource for FOSS/Linux users, thank you and I hope to see you editing with us! ~ atmois === <u>ATL Ownership</u> ~ ''May 2024 - March 2026'' === ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. to be added: DDoS report, 1.0 release and wikibot launch ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[FW:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] df8039dcb2ddf0adff4df725c77b2087a209cd4e 4545 4528 2026-05-11T13:20:10Z Atmois 13 Add key values wikitext text/x-wiki == <u>About</u> == '''foss.wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord]! {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.gg/pV67V6GBrg Discord server]! To contact the administrators, check out our [[FW:Contact|contact page]]! We have 4 key values for foss.wiki, that summarise all of our [[guidelines]] : # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == <u>Important Links</u> == * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[Contributing]] - Outlines how YOU can contribute to foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer == <u>Wiki Staff</u> == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director * [[User:Scottc96|Scott96]] - Wiki Director ====== Operators ====== * [[User:Ow0cast|Ow0cast]] - Wiki Team & Moderator == '''<u>History</u>''' == === <u>Independence</u> ~ ''April 2026 - Present'' === '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] (promoted to co-director) remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. With the relaunch we setup of our status page with Phare at [https://status.foss.wiki status.foss.wiki] and launched our own [https://discord.gg/pV67V6GBrg Discord Server] and partnered with [https://discord.gg/nglinux Neon Genesis Linux], a server run by [[User:Scottc96|Scott96]] to provide high quality FOSS/Linux support and discussions. Our wiki deployment code is available on our new [https://github.com/FOSS-Wiki GitHub] and we redeployed Umami analytics and updated our [[FW:Privacy policy|Privacy Policy]] to clarify some unclear data retention details as well as provide Opt Out information for Umami if users with to not be included in wiki usage analytics. Finally, we thank everyone who stuck with us especially former ATL staff for all their support and kindness during these tough times, every edit and every bit of support is valued and I am eternally grateful for everyone's help to make this fantastic resource for FOSS/Linux users, thank you and I hope to see you editing with us! ~ atmois === <u>ATL Ownership</u> ~ ''May 2024 - March 2026'' === ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. to be added: DDoS report, 1.0 release and wikibot launch ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[FW:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] 8df0a4fdd0e03669641cb1cd6bec1e85b4f5c7bf 4569 4545 2026-05-14T11:46:42Z Atmois 13 Fix links and layout wikitext text/x-wiki == <u>About</u> == {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! '''foss.wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.foss.wiki Discord server]! To contact the administrators, check out our [[FW:Contact|contact page]]! If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord]! We have 4 key values for foss.wiki, that summarise all of our [[guidelines]] : # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == <u>Important Links</u> == * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[Contributing]] - Outlines how YOU can contribute to foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer == <u>Wiki Staff</u> == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director * [[User:Scottc96|Scott96]] - Wiki Director ====== Operators ====== * [[User:Ow0cast|Ow0cast]] - Wiki Team & Moderator == '''<u>History</u>''' == === <u>Independence</u> ~ ''April 2026 - Present'' === '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] (promoted to co-director) remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. With the relaunch we setup of our status page with Phare at [https://status.foss.wiki status.foss.wiki] and launched our own [https://discord.foss.wiki Discord Server] and partnered with [https://discord.gg/nglinux Neon Genesis Linux], a server run by [[User:Scottc96|Scott96]] to provide high quality FOSS/Linux support and discussions. Our wiki deployment code is available on our new [https://github.foss.wiki GitHub] and we redeployed Umami analytics and updated our [[FW:Privacy policy|Privacy Policy]] to clarify some unclear data retention details as well as provide Opt Out information for Umami if users with to not be included in wiki usage analytics. Finally, we thank everyone who stuck with us especially former ATL staff for all their support and kindness during these tough times, every edit and every bit of support is valued and I am eternally grateful for everyone's help to make this fantastic resource for FOSS/Linux users, thank you and I hope to see you editing with us! ~ atmois === <u>ATL Ownership</u> ~ ''May 2024 - March 2026'' === ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. to be added: DDoS report, 1.0 release and wikibot launch ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[FW:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] dcdfcc40c782d21ff9b78b82ec7a12201cbbaea6 4 593 4529 4482 2026-05-08T21:18:42Z Atmois 13 Fix links wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making foss.wiki an amazing resource for all users of FOSS and related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''foss.wiki''' uses. For users interested in writing guides for '''foss.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''foss.wiki''' you can see the wiki's [[FW:About|about]] page! Some important pages are also listed below: * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer If you ever have any questions or need help, you can join our [https://discord.gg/pV67V6GBrg Discord Server] and check out <code>#wiki</code> for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''foss.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 5 key values for '''foss.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Consistency: Content should always be up to the highest of standards and be formatted according to the [[Guidelines#Formatting|guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''foss.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[FW:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''foss.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another compatible free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[FW:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it meets the standards of the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''foss.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[FW:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. Please ensure when making new pages you follow the [[FW:Guidelines#Notability Standards|Notability Standards]]! This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[FW:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distro's, it lacks a lot of major distro's and each section should have a short blurb and information about key facts about what distro's under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distro's that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 02501a25d11374be04ff330166c4c35c19b611b6 4543 4529 2026-05-11T13:18:58Z Atmois 13 Update key values wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making foss.wiki an amazing resource for all users of FOSS and related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''foss.wiki''' uses. For users interested in writing guides for '''foss.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''foss.wiki''' you can see the wiki's [[FW:About|about]] page! Some important pages are also listed below: * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer If you ever have any questions or need help, you can join our [https://discord.gg/pV67V6GBrg Discord Server] and check out <code>#wiki</code> for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''foss.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 4 key values for '''foss.wiki''', these summarise all of our [[guidelines]] well: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''foss.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[FW:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''foss.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another compatible free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[FW:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it meets the standards of the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''foss.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[FW:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. Please ensure when making new pages you follow the [[FW:Guidelines#Notability Standards|Notability Standards]]! This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[FW:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distro's, it lacks a lot of major distro's and each section should have a short blurb and information about key facts about what distro's under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distro's that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 925885b48369ea6dc5a978b488e53355537f1d99 4546 4543 2026-05-11T13:20:26Z Atmois 13 Fix grammer wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making foss.wiki an amazing resource for all users of FOSS and related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''foss.wiki''' uses. For users interested in writing guides for '''foss.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''foss.wiki''' you can see the wiki's [[FW:About|about]] page! Some important pages are also listed below: * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer If you ever have any questions or need help, you can join our [https://discord.gg/pV67V6GBrg Discord Server] and check out <code>#wiki</code> for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''foss.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 4 key values for '''foss.wiki''', that summarise all of our [[guidelines]]: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''foss.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[FW:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''foss.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another compatible free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[FW:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it meets the standards of the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''foss.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[FW:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. Please ensure when making new pages you follow the [[FW:Guidelines#Notability Standards|Notability Standards]]! This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[FW:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distro's, it lacks a lot of major distro's and each section should have a short blurb and information about key facts about what distro's under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distro's that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 35898484fd75d9ef8c373c3fd34efb6557fed091 4568 4546 2026-05-14T11:45:41Z Atmois 13 Update Discord link wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making foss.wiki an amazing resource for all users of FOSS and related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''foss.wiki''' uses. For users interested in writing guides for '''foss.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''foss.wiki''' you can see the wiki's [[FW:About|about]] page! Some important pages are also listed below: * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer If you ever have any questions or need help, you can join our [https://discord.foss.wiki Discord Server] and check out <code>#wiki</code> for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''foss.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 4 key values for '''foss.wiki''', that summarise all of our [[guidelines]]: # Accuracy: Content should always be [[Guidelines#Citations|cited]] appropriately and should be up-to-date and high quality. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''foss.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[FW:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''foss.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another compatible free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[FW:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it meets the standards of the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''foss.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[FW:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. Please ensure when making new pages you follow the [[FW:Guidelines#Notability Standards|Notability Standards]]! This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[FW:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distro's, it lacks a lot of major distro's and each section should have a short blurb and information about key facts about what distro's under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distro's that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 5837d65a1c6a499624ab585e49a6f330e0040866 2 192 4530 3053 2026-05-09T09:50:21Z Atmois 13 fix link wikitext text/x-wiki Local tech nerd, who listens to ''a lot'' of music. '''atl.wiki'''<nowiki/>'s project lead, come join us and [[FW:Contributing|contribute]]! https://atmois.com 38e170ffea7617086ced519fe9b16ff637a385b6 0 712 4531 2717 2026-05-09T09:58:53Z Atmois 13 Fix redirect wikitext text/x-wiki #REDIRECT [[FW:About]] 0099d888edf1b7f8b5e3bd314741673ccff27dae 10 523 4532 3528 2026-05-09T09:59:41Z Atmois 13 fix link wikitext text/x-wiki <includeonly><div class="mbox mbox-med mbox-wip" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon edit-ltr-gray.svg]]</span>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</span> <div class="mbox-text">This template means the author of a page is still actively working on the page, and this serves to notify other editors to check with them before potentially creating conflicting changes and to notify the staff that it may not meet the wiki's [[FW:Guidelines|guidelines]] yet.</div></div><templatestyles src="Module:Mbox/styles.css" /></includeonly><noinclude>{{/doc}}</noinclude> 043dea06373b31b24c40a5248435c11bcb40edde 0 621 4533 2721 2026-05-09T10:07:27Z Atmois 13 Fix redirect wikitext text/x-wiki #REDIRECT [[FW:Guidelines]] 2f189f5366be6b5051d9178d045398be6837be7b 0 711 4534 2718 2026-05-09T10:07:33Z Atmois 13 Fix redirect wikitext text/x-wiki #REDIRECT [[FW:Guidelines#Citations]] db52e4aad82c3b20806cb20e05bc50dc8d7e2edc 8 1100 4535 2026-05-10T19:55:17Z Atmois 13 Update signup message wikitext text/x-wiki I agree to the [$1 Code of Conduct] and [$2 Privacy Policy] 7dbd75a91e45f3069a5588634b596b28c5cd8b3d 4536 4535 2026-05-10T19:55:46Z Atmois 13 Update spacing wikitext text/x-wiki I agree to the [$1 Code of Conduct] and [$2 Privacy Policy] ad79b303724a4741a9bbb46e9f3d987528978243 4537 4536 2026-05-10T19:56:07Z Atmois 13 Update spacing wikitext text/x-wiki I agree to the [ $1 Code of Conduct ] and [ $2 Privacy Policy ] c5e5ceabada4dd271e695c1526df27f4271068ce 4538 4537 2026-05-10T19:56:35Z Atmois 13 Undo revision [[Special:Diff/4537|4537]] by [[Special:Contributions/Atmois|Atmois]] ([[User talk:Atmois|talk]]) wikitext text/x-wiki I agree to the [$1 Code of Conduct] and [$2 Privacy Policy] ad79b303724a4741a9bbb46e9f3d987528978243 4539 4538 2026-05-10T19:57:57Z Atmois 13 Fix spacing wikitext text/x-wiki I agree to the‎ [$1 Code of Conduct] ‎and‎ [$2 Privacy Policy] c43f3d84a6b19615462ac6cf559ef26269a7bf5c 4540 4539 2026-05-10T19:58:19Z Atmois 13 Fix spacing wikitext text/x-wiki I agree to the ‎ [$1 Code of Conduct] ‎ and ‎ [$2 Privacy Policy] 873a11c03d1f45d4b34a0cbf9ad4eb995cba4c48 4 340 4542 4509 2026-05-11T13:18:25Z Atmois 13 Update key values wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; foss.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[FW:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[FW:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. Please ensure you appropriately '''cite your sources''', following our [[Guidelines#Citations|Citations Guidelines]]. If you cannot find an appropriate source for a statement, it does not belong on the wiki. Any claim or statement that ''could'' be challenged must be backed up by a reputable source. ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] Always cite the sources of content when it is required; this can be because you are referencing others' statements, the release date of a piece of software, or for any material that is challenged or is likely to be challenged in particular. If you ever obtain content from another source (such as taking info from a wiki with a compatible licence) or quote other locations online, ensure you link to it appropriately. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. Sources should be published & reliable, and it should be ensured that they are independent, published sources with a reputation for fact-checking and accuracy. Proper sourcing is ''always'' dependent on context; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Articles should also attempt to primarily rely on secondary sources whenever possible and if possible avoid other wiki's such as wikipedia for sourcing but rather look for the sources ''they'' cite instead. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[FW:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[FW:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[FW:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[FW:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[FW:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[FW:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>FW:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://foss.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[FW:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''foss.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 7f64dee4dde6ba21ef381d612f519bfb6328537d 8 1101 4557 2026-05-11T17:04:53Z Atmois 13 Create group page wikitext text/x-wiki Wiki Team 9cfa94a9d1269f4b337f44b1bba35f6e3e84862a 8 1102 4558 2026-05-11T17:06:32Z Atmois 13 Add group wikitext text/x-wiki {{GENDER:$1|Wiki Team}} 7c3006e693f71114df5bb90ee3d8cd0feb832fbc 8 1103 4559 2026-05-11T17:07:08Z Atmois 13 Add groups wikitext text/x-wiki Template Editors f238f9d445e5e594eac382517c581ea3d4500ad7 8 1104 4560 2026-05-11T17:07:10Z Atmois 13 Add groups wikitext text/x-wiki Template Editor f7aab2ae80daed00d84174c9559f6a8edfa82868 8 1105 4561 2026-05-12T20:13:33Z Atmois 13 Created page with "Status Page" wikitext text/x-wiki Status Page 479cab4da78fa94ca6b16eb607d801d7b93941e6 8 1106 4562 2026-05-12T20:13:50Z Atmois 13 Created page with "GitHub" wikitext text/x-wiki GitHub 5442e2b64fa09764b9f593867e59a97292c84059 8 1107 4563 2026-05-12T20:14:05Z Atmois 13 Created page with "Discord Server" wikitext text/x-wiki Discord Server 06d4a249fefe78202b26128f0ea59da0cfc61bb7 8 1108 4564 2026-05-12T20:14:18Z Atmois 13 Created page with "Guidelines" wikitext text/x-wiki Guidelines 141d1d74d8a6b3e7a7f1418ef539a53ce746ef34 4 595 4567 4498 2026-05-14T11:45:08Z Atmois 13 Update discord links wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.foss.wiki Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/open</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''admin(at)foss.wiki'' To report security vulnerabilities please see our [https://foss.wiki/FW:Security Security Policy]. * [[User:Atmois|Atmois]] - Wiki Director ** ''zoe(at)foss.wiki'' * [[User:Scottc96|Scott96]] - Wiki Director ** scott.c(at)foss.wiki *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''none'' f01c4ca388980efc7121b9056c354a9dc6b395f5 8 400 4570 4488 2026-05-14T11:48:55Z Atmois 13 Fix discord link wikitext text/x-wiki The FOSS Wiki aims to provide reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software! If you want to reach out to us or contribute, ensure to check out our [https://discord.foss.wiki Discord server]! ae2fa120008a3b385fe57e3865a8ce796ac0ed82 4 646 4571 4492 2026-05-14T11:49:04Z Atmois 13 Fix discord link wikitext text/x-wiki Please note this feature is currently disabled, it will be re-enabled in the coming weeks. Sorry for any inconvinience. == '''<u>DO NOT share the link provided with anyone, including any staff members.</u>''' == To link your Discord and '''foss.wiki''' accounts in our [https://discord.foss.wiki discord server], type <code>/verify</code> using '''''@wiki'''''. You will receive a private link in your DM's, Then click the link, press '''Allow''', and return to Discord, if your '''foss.wiki''' account is at least '''3 days old''', and has met the '''minimum edit threshold of 10 edits''', you will automatically be given the '''''@Editor''''' role, which comes with bonus perks in the Discord server. You may need to wait up to an hour for the role to be given. If you do not receive it open a ticket with <code>/ticket</code> and ask for help. If you have met the requirements '''after''' initially verifying, run <code>/unverify</code> then go through the verification process again, this will refresh your role. To see if you meet the requirements, visit the [[Special:UserRights]] page, search your username, and see if you're an ''implicit member of "Autoconfirmed Users"''. This role is automatically given by the wiki to users who meet the criteria. cad11f54d52e9f0273032792494bdeb9c5d16181 4 876 4572 4499 2026-05-14T11:49:24Z Atmois 13 Fix discord link wikitext text/x-wiki == Security at FOSS Wiki == At FOSS Wiki, we are committed to maintaining the highest security standards to protect our community and infrastructure. We deeply value the security research community and actively encourage responsible disclosure of security vulnerabilities. Your contributions help us ensure the safety, privacy, and integrity of our platforms and services. We believe in transparency and collaboration when it comes to security. Our team is dedicated to investigating all reported issues promptly and working with researchers to address vulnerabilities in a timely and responsible manner. === Scope === This security policy applies to all FOSS Wiki projects and services, including but not limited to: * Our domains and all of its subdomains: '''foss.wiki''' * API endpoints, back-end services, Discord bot services or integrations, and community platforms or forums * Repositories within the FOSS Wiki GitHub/Codeberg organisation We are interested in any vulnerability that could lead to unauthorised access, data breaches, or service disruptions. We welcome any reports of potential vulnerabilities outside of this scope but we may not be able to address them immediately. Please also note that we also host and utilise external services, we also welcome reports regarding those services but we may not be able to address them directly and will refer you to the appropriate party. === How to Report a Security Issue === If you have discovered a security vulnerability, please help us keep our community safe by reporting it responsibly. When reporting, please include: * A clear description of the vulnerability and its potential impact * Detailed steps to reproduce the issue * Information about the environment where you discovered the issue * Any proof-of-concept code or evidence of the vulnerability (if applicable) * Any recommendations or patches you may have for resolving the issue === Contact === All reports should be directed to our email, [mailto:security@foss.wiki security@foss.wiki] and if required, using the PGP found at https://foss.wiki/securityatfosswiki.asc. Alternatively, you may open a ticket with <code>/open</code> in our [https://discord.foss.wiki Discord server] and request assistance there. '''Please do not disclose''' '''vulnerability details in the ticket unless requested by an administrator.''' === Responsible Disclosure Guidelines === We require that you: * Do not make use of any vulnerabilities without explicit permission to do so from a member of Wiki Leadership * Do not access, copy, or destroy data that is not available without authentication/authorisation in any capacity * Do not disrupt our services or degrade the performance of our services * Keep vulnerability details confidential until we have addressed the issue and agreed to a planned disclosure * Give us reasonable time (typically 30 days, although you will be informed of the estimated time) to investigate and resolve the issue === Safe Harbour === Any activities conducted in a manner consistent with this policy will be considered authorised conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will ensure it is known that your actions were conducted in compliance with this policy. === Recognition === We appreciate security researchers and individuals who help keep our community safe. If you would like to be acknowledged for your responsible disclosure, please let us know in your report and we'll be happy to recognise your contribution publicly. However, please note we do not have the ability to award bug bounties or monetary reward for any disclosed vulnerabilities due to the nature of the project. We also welcome you to post your own report and/or analysis once we have resolved and disclosed the vulnerability publicly ourselves, '''we only request you send it to us 1 week before you plan to publish it.''' 0dab1e205efd2394d12074d8aae1a007716808fc 4613 4572 2026-05-22T17:58:01Z Atmois 13 Fix command wikitext text/x-wiki == Security at FOSS Wiki == At FOSS Wiki, we are committed to maintaining the highest security standards to protect our community and infrastructure. We deeply value the security research community and actively encourage responsible disclosure of security vulnerabilities. Your contributions help us ensure the safety, privacy, and integrity of our platforms and services. We believe in transparency and collaboration when it comes to security. Our team is dedicated to investigating all reported issues promptly and working with researchers to address vulnerabilities in a timely and responsible manner. === Scope === This security policy applies to all FOSS Wiki projects and services, including but not limited to: * Our domains and all of its subdomains: '''foss.wiki''' * API endpoints, back-end services, Discord bot services or integrations, and community platforms or forums * Repositories within the FOSS Wiki GitHub/Codeberg organisation We are interested in any vulnerability that could lead to unauthorised access, data breaches, or service disruptions. We welcome any reports of potential vulnerabilities outside of this scope but we may not be able to address them immediately. Please also note that we also host and utilise external services, we also welcome reports regarding those services but we may not be able to address them directly and will refer you to the appropriate party. === How to Report a Security Issue === If you have discovered a security vulnerability, please help us keep our community safe by reporting it responsibly. When reporting, please include: * A clear description of the vulnerability and its potential impact * Detailed steps to reproduce the issue * Information about the environment where you discovered the issue * Any proof-of-concept code or evidence of the vulnerability (if applicable) * Any recommendations or patches you may have for resolving the issue === Contact === All reports should be directed to our email, [mailto:security@foss.wiki security@foss.wiki] and if required, using the PGP found at https://foss.wiki/securityatfosswiki.asc. Alternatively, you may open a ticket with <code>/ticket</code> in our [https://discord.foss.wiki Discord server] and request assistance there. '''Please do not disclose''' '''vulnerability details in the ticket unless requested by an administrator.''' === Responsible Disclosure Guidelines === We require that you: * Do not make use of any vulnerabilities without explicit permission to do so from a member of Wiki Leadership * Do not access, copy, or destroy data that is not available without authentication/authorisation in any capacity * Do not disrupt our services or degrade the performance of our services * Keep vulnerability details confidential until we have addressed the issue and agreed to a planned disclosure * Give us reasonable time (typically 30 days, although you will be informed of the estimated time) to investigate and resolve the issue === Safe Harbour === Any activities conducted in a manner consistent with this policy will be considered authorised conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will ensure it is known that your actions were conducted in compliance with this policy. === Recognition === We appreciate security researchers and individuals who help keep our community safe. If you would like to be acknowledged for your responsible disclosure, please let us know in your report and we'll be happy to recognise your contribution publicly. However, please note we do not have the ability to award bug bounties or monetary reward for any disclosed vulnerabilities due to the nature of the project. We also welcome you to post your own report and/or analysis once we have resolved and disclosed the vulnerability publicly ourselves, '''we only request you send it to us 1 week before you plan to publish it.''' 51722cda214ed6100a9ea664be4a615a2dd5d02b 4 536 4573 4501 2026-05-14T11:49:42Z Atmois 13 Fix discord link wikitext text/x-wiki === 1. Safe for Work (SFW) Policy === foss.wiki is a '''Safe for Work (SFW)''' environment. '''NSFW (Not Safe for Work) content and discussions are strictly prohibited'''. While NSFW typically refers to sexually explicit material, the definition may evolve to include other forms of sensitive content. This applies to all content on the wiki, including but not limited to text, images & media. ==== Prohibited Content: ==== * '''Sexually explicit material''' in any form. * '''Violence, gore, or depictions of animal abuse'''. * '''Glorification of self-harm or suicide'''. == 2. Mutual Respect == foss.wiki is a '''respectful''' and '''inclusive''' community. ==== Expected Behaviour: ==== * Treat others '''with humility and respect'''. * Keep interactions '''constructive and considerate'''. * '''No harassment''': Bullying, doxxing, or coordinated attacks are '''strictly prohibited'''. * '''No hate speech''': Discriminatory remarks on any personal characteristics will not be tolerated. * '''No threats''': Direct or indirect threats against individuals or groups will result in '''immediate action'''. == 3. Responsible Expression & Discussions == The wiki welcomes '''diverse perspectives''' and encourages constructive discussions, but it is not a '''free-for-all debate forum'''. Please ensure all discussions are kept to talk pages and not done on articles unless it has been designated as a discussion page. Alternately you can utilise our [https://discord.foss.wiki Discord server] to have discussions with other users. ==== Guidelines for Expression: ==== * '''Stay on topic''': Discussions should focus on '''Linux, open-source software, and related technologies'''. * '''No disruptive debates''': Heated, repetitive, or toxic arguments will be moderated. * '''Avoid professional advice''': The wiki does not provide '''medical, legal, financial, or religious advice'''. == 4. Avoidance of Elitism == Technology and especially FOSS adjacent software is for '''everyone''', from beginners to experts. ==== Expected Behaviour: ==== * '''Respect different choices''': Users may prefer different '''distro's, desktop environments, package managers, or workflows'''. * '''No gate-keeping''': Beginners should feel welcome, not discouraged. We want to foster a growing Linux and FOSS community. == 5. Respecting Moderators & Rules == Moderators help maintain order. If a moderator asks you to '''modify behaviour, please cooperate'''. * '''Disagreements should be handled via the wiki staff''', not public disputes. * '''Do not backseat moderate''': If someone breaks a rule, report it instead of escalating the situation. == 6. Language Requirement: English Only == * The wiki uses '''English as the primary language'''. == 7. Content Guidelines == All contributions on the wiki must align with the wiki’s '''goal of providing high-quality FOSS and Linux documentation'''. ==== Prohibited Content: ==== * Low-effort, spam, or non-constructive edits. * Off-topic material unrelated to Linux, open-source software or general technology. * Unverified or misleading technical information. * Spam or self-promoting content not relevant to the article. * AI Generated images are prohibited unless it is relevant to an article and clearly disclosed as being AI generated. * Use of generative AI to write content which will be published on the wiki is prohibited. However, AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used is permitted. == 8. Privacy & Security == * Do not doxx or share personal information of other users. * Be cautious about sharing your own information. == 9. Enforcement & Punishments == Moderators '''reserve the right''' to take appropriate action depending on the severity of violations. If you believe a '''member of the team has abused their powers''', it should be '''reported to the administrators''' through a method listed [[Main Page#Contacts|here]]. ==== Possible Actions: ==== * '''Warnings''': Used for minor infractions. * '''Blocks''': Temporary restrictions from editing or participating. * '''IP Blocks''': Restricting editing access entirely. == 10. Punishment Evasion & Appeals == * Using alt accounts, VPN's or proxies to evade punishments will result in further punishment for yourself. * If you believe a punishment was unfair, you may appeal by contacting an administrator through a method listed [[Main Page#Contacts|here]]. == 11. Final Note: Exercise Common Sense == Not every situation can be predicted. Use '''good judgement, respect others, and contribute positively''' to the Linux community. If in doubt, '''ask for clarification rather than assuming'''. Thank you for being part of the '''FOSS Wiki'''! [[Category:Meta]] e40860b5a4a22c2a06be1b11a98f4490f0fcd212 8 1109 4574 2026-05-14T13:53:38Z Atmois 13 Created page with "Transparency" wikitext text/x-wiki Transparency 7cb338a916152e13525f9822a4d915c168c521f0 8 624 4575 4565 2026-05-14T13:54:54Z Atmois 13 Update footer css css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer Column Configuration */ #footer-places ul { column-count: 2; column-gap: 2rem; } #footer-places-discord { break-before: column; } 6fe4464f387529161de99956b1e12c6492af447c 4588 4575 2026-05-21T21:11:11Z Atmois 13 Fix footers css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* 3-column footer grid */ #footer-places { display: grid; grid-template-columns: repeat(3, 1fr); gap: 0.25em 1.5em; } /* Column 1 */ #footer-places-about { order: 1; } #footer-places-guidelines { order: 2; } #footer-places-disclaimer { order: 3; } /* Column 2 */ #footer-places-statuspage { order: 4; } #footer-places-transparency { order: 5; } #footer-places-privacy { order: 6; } /* Column 3 */ #footer-places-discord { order: 7; } #footer-places-donate { order: 8; } #footer-places-github { order: 9; } 380d2b7c5108fc5f64710d9ad028644f3a111f53 4589 4588 2026-05-21T21:27:12Z Atmois 13 css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* 3-column footer grid */ #footer-places { display: grid; grid-template-columns: repeat(3, 1fr); gap: 0.25em 1.5em; } /* Column 1 */ #footer-places-about { order: 1; } #footer-places-guidelines { order: 2; } #footer-places-disclaimers { order: 3; } /* Column 2 */ #footer-places-statuspage { order: 4; } #footer-places-transparency { order: 5; } #footer-places-privacy { order: 6; } /* Column 3 */ #footer-places-discord { order: 7; } #footer-places-donate { order: 8; } #footer-places-github { order: 9; } 21fb56f82f3a05831b29e8be97dd4cc9014395f1 4590 4589 2026-05-21T21:33:59Z Atmois 13 fix footer css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* 3-column footer grid */ #footer-places ul { display: grid; grid-template-columns: repeat(3, 1fr); gap: 0.25em 1.5em; list-style: none; margin: 0; padding: 0; } /* Column 1 */ #footer-places-about { order: 1; } #footer-places-guidelines { order: 2; } #footer-places-disclaimers { order: 3; } /* Column 2 */ #footer-places-statuspage { order: 4; } #footer-places-transparency { order: 5; } #footer-places-privacy { order: 6; } /* Column 3 */ #footer-places-discord { order: 7; } #footer-places-donate { order: 8; } #footer-places-github { order: 9; } 7f7240eda2a22ff0a8666f15b5819e0eeb93bbbb 4591 4590 2026-05-21T21:46:36Z Atmois 13 Fix footer css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* 3-column footer grid */ nav#footer-places ul { display: grid; grid-template-columns: repeat(3, 1fr); gap: 0.25em 1.5em; list-style: none; margin: 0; padding: 0; } /* Column 1 */ #footer-places-about { order: 1; } #footer-places-guidelines { order: 2; } #footer-places-disclaimers { order: 3; } /* Column 2 */ #footer-places-statuspage { order: 4; } #footer-places-transparency { order: 5; } #footer-places-privacy { order: 6; } /* Column 3 */ #footer-places-discord { order: 7; } #footer-places-donate { order: 8; } #footer-places-github { order: 9; } 2b37592695ab98bedf3a7014201574b1eb066d73 4592 4591 2026-05-21T21:48:11Z Atmois 13 Fix footer spacing css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* 3-column footer grid */ nav#footer-places ul { display: grid; grid-template-columns: repeat(3, max-content); gap: 0.25em 1.5em; list-style: none; margin: 0; padding: 0; } /* Column 1 */ #footer-places-about { order: 1; } #footer-places-guidelines { order: 2; } #footer-places-disclaimers { order: 3; } /* Column 2 */ #footer-places-statuspage { order: 4; } #footer-places-transparency { order: 5; } #footer-places-privacy { order: 6; } /* Column 3 */ #footer-places-discord { order: 7; } #footer-places-donate { order: 8; } #footer-places-github { order: 9; } 23bd51fb6d9ae7399ae5c9561f8aeb0fb336832d 4594 4592 2026-05-21T21:57:49Z Atmois 13 Simplify footer css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer */ #footer-places ul { column-count: 3; column-gap: 2rem; } e2c0ede89d5225a643f5186abe619904100533d1 4599 4594 2026-05-21T22:01:55Z Atmois 13 Fix footer layout css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } #footer-places ul { column-count: 3; column-gap: 2rem; } #footer-places li { white-space: nowrap; } 5069ddd1b6428b768bd29efb951ed6ee139f5131 4600 4599 2026-05-21T22:05:08Z Atmois 13 Make responsive css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer Configs */ #footer-places ul { column-count: 3; column-gap: 2rem; } #footer-places li { white-space: nowrap; } @media (max-width: 720px) { #footer-places ul { column-count: 2; } } @media (max-width: 480px) { #footer-places ul { column-count: 1; } } 9bbd67fd535a29d116aeb1b7723afa0408a06de9 4601 4600 2026-05-21T22:09:12Z Atmois 13 Fix footer layout configs css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer Configs */ #footer-places ul { display: flex; flex-direction: column; flex-wrap: wrap; height: 5em; column-gap: 2rem; } #footer-places-about { order: 1; } #footer-places-guidelines { order: 2; } #footer-places-disclaimers { order: 3; } #footer-places-statuspage { order: 4; } #footer-places-transparency { order: 5; } #footer-places-privacy { order: 6; } #footer-places-discord { order: 7; } #footer-places-donate { order: 8; } #footer-places-github { order: 9; } #footer-places li { white-space: nowrap; } @media (max-width: 720px) { #footer-places ul { height: 8em; } } @media (max-width: 480px) { #footer-places ul { height: auto; flex-wrap: nowrap; } } 873d9b77641bfe6ca2c5a3e5afcf59a982ca68fa 4602 4601 2026-05-21T22:10:10Z Atmois 13 Fix footer layout css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer Configs */ #footer-places ul { display: flex; flex-direction: column; flex-wrap: wrap; height: 6rem; column-gap: 2rem; } #footer-places-about { order: 1; } #footer-places-guidelines { order: 2; } #footer-places-disclaimers { order: 3; } #footer-places-statuspage { order: 4; } #footer-places-transparency { order: 5; } #footer-places-privacy { order: 6; } #footer-places-discord { order: 7; } #footer-places-donate { order: 8; } #footer-places-github { order: 9; } #footer-places li { white-space: nowrap; width: 33%; } @media (max-width: 720px) { #footer-places ul { height: 9rem; } #footer-places li { width: 50%; } } @media (max-width: 480px) { #footer-places ul { height: auto; flex-wrap: nowrap; } #footer-places li { width: 100%; } } ddea479b0c5d260323d89e9dcb7ea7bfd4fc59fe 4603 4602 2026-05-21T22:11:55Z Atmois 13 Remove footer css css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } 7e2538be8c2c90858f9ef75b05b262411d3f40a9 4604 4603 2026-05-21T22:18:04Z Atmois 13 Readd footer configs css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer */ #footer-places { column-count: 3 !important; } #footer-places li { white-space: nowrap; } @media (max-width: 720px) { #footer-places { column-count: 2 !important; } } @media (max-width: 480px) { #footer-places { column-count: 1 !important; } } 3ded11444d722d01caceabe9eb02691033d53797 4605 4604 2026-05-21T22:19:38Z Atmois 13 Fix layout css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer */ #footer-places { display: block !important; column-count: 3 !important; } #footer-places li { white-space: nowrap; } @media (max-width: 720px) { #footer-places { column-count: 2 !important; } } @media (max-width: 480px) { #footer-places { column-count: 1 !important; } } efd6dedcd468d9c09285a82488666c0079cdd3e3 4606 4605 2026-05-21T22:25:59Z Atmois 13 Add order css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer */ #footer-places { display: block !important; column-count: unset !important; } #footer-places ul { display: grid !important; grid-template-columns: repeat(3, max-content); gap: 0.25em 2rem; } #footer-places-about { order: 1; } #footer-places-guidelines { order: 2; } #footer-places-disclaimers { order: 3; } #footer-places-statuspage { order: 4; } #footer-places-transparency { order: 5; } #footer-places-privacy { order: 6; } #footer-places-discord { order: 7; } #footer-places-donate { order: 8; } #footer-places-github { order: 9; } #footer-places li { white-space: nowrap; } @media (max-width: 720px) { #footer-places ul { grid-template-columns: repeat(2, max-content); } } @media (max-width: 480px) { #footer-places ul { grid-template-columns: repeat(1, max-content); } } b8517428c44bd254d4cf2c56d49bed15015807ac 4607 4606 2026-05-21T22:27:20Z Atmois 13 Fix order css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04, var(--color-surface-2, #2d2d2d)); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer */ #footer-places { display: block !important; column-count: unset !important; } #footer-places ul { display: grid !important; grid-template-columns: repeat(3, max-content); gap: 0.25em 2rem; } #footer-places-about { order: 1; } #footer-places-statuspage { order: 2; } #footer-places-discord { order: 3; } #footer-places-guidelines { order: 4; } #footer-places-transparency { order: 5; } #footer-places-donate { order: 6; } #footer-places-disclaimers { order: 7; } #footer-places-privacy { order: 8; } #footer-places-github { order: 9; } #footer-places li { white-space: nowrap; } @media (max-width: 720px) { #footer-places ul { grid-template-columns: repeat(2, max-content); } } @media (max-width: 480px) { #footer-places ul { grid-template-columns: repeat(1, max-content); } } 683f74449cff565788ead7b7f75934034dc73c28 2 192 4576 4530 2026-05-14T20:50:07Z Atmois 13 Update title wikitext text/x-wiki Local tech nerd, who listens to ''a lot'' of music. '''foss.wiki'''<nowiki/>'s director, come join us and [[FW:Contributing|contribute]]! https://atmois.com 5583754bb99ca9a248b1f24ee9d924481c1a5fe2 8 538 4577 4473 2026-05-14T20:55:14Z Atmois 13 Update notice wikitext text/x-wiki '''FOSS.wiki will be re-launching on the 23rd of May!''' Check out our [https://discord.foss.wiki Discord Server] to get updates on the wiki and see what we are up to. 8c1e9f0c9669a50b330e2c38b7447cc84022deb8 4611 4577 2026-05-22T12:13:22Z Atmois 13 Update data & time wikitext text/x-wiki '''FOSS.wiki will be re-launching on the 22nd of May at 7PM UTC!''' Check out our [https://discord.foss.wiki Discord Server] to get updates on the wiki and see what we are up to. 18010b7f3f2ab972c3d0c35e3655f734863be1ef 4 595 4578 4567 2026-05-16T19:15:57Z Atmois 13 Update emails wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.foss.wiki Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/open</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''admin(at)foss.wiki'' To report security vulnerabilities please see our [https://foss.wiki/FW:Security Security Policy]. * [[User:Atmois|Atmois]] - Wiki Director ** ''zoe.m(at)foss.wiki'' * [[User:Scottc96|Scott96]] - Wiki Director ** scott.c(at)foss.wiki *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''none'' be125a268cee9cfbc6512199e9f44f682a32fd09 4614 4578 2026-05-22T17:58:31Z Atmois 13 Fix command wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.foss.wiki Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''admin(at)foss.wiki'' To report security vulnerabilities please see our [https://foss.wiki/FW:Security Security Policy]. * [[User:Atmois|Atmois]] - Wiki Director ** ''zoe.m(at)foss.wiki'' * [[User:Scottc96|Scott96]] - Wiki Director ** scott.c(at)foss.wiki *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''none'' e2157162dac4bbd447f61b124487fd8427e88ec5 0 1 4579 4566 2026-05-21T08:26:08Z Atmois 13 Improve wording wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.foss.wiki 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.foss.wiki Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 4 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should always be [[FW:Guidelines#Citations|cited]] appropriately, up-to-date and high quality. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div>{{Special:RecentChanges|hidebots|namespace=0|limit=10}}</div> </div> df6cb755754b64d9b5df3efbf580ddf96df9cea4 4583 4579 2026-05-21T16:58:11Z Atmois 13 Tidy up wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.foss.wiki 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.foss.wiki Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. If you're ever stuck for what to edit or how you can help, you can always check out our [https://discord.foss.wiki Discord Server], where there will always be someone happy to help you get editing! </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 4 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div>{{Special:RecentChanges|hidebots|namespace=0|limit=10}}</div> </div> 1c930f906e498ba50777f6f04cfa0578b7761eda 4585 4583 2026-05-21T16:59:12Z Atmois 13 Fix link wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.foss.wiki 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.foss.wiki Discord server]! To contact the administrators, you can open a ticket with <code>/open</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. If you're ever stuck for what to edit or how you can help, you can always check out our [https://discord.foss.wiki Discord Server], where there will always be someone happy to help you get editing! </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 4 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div>{{Special:RecentChanges|hidebots|namespace=0|limit=10}}</div> </div> e96e43c3b545aefcd6595c96a080f96a16d45553 4612 4585 2026-05-22T17:56:07Z Atmois 13 Fix command wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">foss.wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.foss.wiki 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''foss.wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.foss.wiki Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. If you're ever stuck for what to edit or how you can help, you can always check out our [https://discord.foss.wiki Discord Server], where there will always be someone happy to help you get editing! </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''foss.wiki''' has 4 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div>{{Special:RecentChanges|hidebots|namespace=0|limit=10}}</div> </div> cd9b9fb70965096856cb7467c1696604295831cd 4618 4612 2026-05-22T18:08:37Z Atmois 13 Update title wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">FOSS Wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.foss.wiki 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''FOSS Wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.foss.wiki Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. ====== General Support ====== If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord server]! You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. If you're ever stuck for what to edit or how you can help, you can always check out our [https://discord.foss.wiki Discord Server], where there will always be someone happy to help you get editing! </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''FOSS Wiki''' has 4 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div>{{Special:RecentChanges|hidebots|namespace=0|limit=10}}</div> </div> 586125d34b90172bf3ba9d3a1a8b55e583c90a39 4 340 4580 4542 2026-05-21T15:27:52Z Atmois 13 Tidy up citaiton guidelines wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; foss.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[FW:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[FW:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. If possible, you should '''cite your sources''' following the [[Guidelines#Citations|Citations Guidelines]] but please do not be discouraged from editing due to a lack of sources, any content is welcome and it can be improved upon as time goes on! ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] If you refer to or copy content (which is under a compatible license) it should be cited; this ensures the original author is credited for their work where relevant. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. We do not require claims and statements to be cited but if it can be challenged, it is always helpful to add a citation. If a claim is being challenged or you are unable to find a source, that's fine, just add the {{Citation needed}} template using <code><nowiki>{{Citation_needed}}</nowiki></code> or using the template inserter and another editor can help you find one or fill it out. Sources should be independent, ideally published and have a reputation for accuracy. '''Proper sourcing is ''always'' dependent on context'''; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Whilst secondary sources are more suitable, a reliable primary source such as a project's documentation or tertiary sources such as other wiki's are welcome but please ensure you do some due diligence to ensure it is up to date and accurate. If a page is in dire need of citations it can be tagged with the [[FW:Guidelines#Citations 2|relevant header template]], which you can read more about below. This should only be used on a page with controversial claims or is utilising content which has not been properly cited or attributed. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[FW:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[FW:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[FW:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[FW:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations where it would be appropriate, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. Before adding this template please consider if the page actually substantially requires citations as per the [[FW:Guidelines#Citations|Citation Policy]] or if there is just a handful of statements that need citations. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page. == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[FW:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[FW:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>FW:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://foss.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[FW:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''foss.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] a5c4b9e3c2f7b97d1abdd1cde518df409cdc1af0 4586 4580 2026-05-21T17:00:14Z Atmois 13 Fix wording wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; foss.wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[FW:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[FW:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date''' and should strive to '''follow the guidelines below'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. If possible, you should '''cite your sources''' following the [[Guidelines#Citations|Citations Guidelines]] but please do not be discouraged from editing due to a lack of sources, any content is welcome and it can be improved upon as time goes on! ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] If you refer to or copy content (which is under a compatible license) it should be cited; this ensures the original author is credited for their work where relevant. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. We do not require claims and statements to be cited but if it can be challenged, it is always helpful to add a citation. If a claim is being challenged or you are unable to find a source, that's fine, just add the {{Citation needed}} template using <code><nowiki>{{Citation_needed}}</nowiki></code> or using the template inserter and another editor can help you find one or fill it out. Sources should be independent, ideally published and have a reputation for accuracy. '''Proper sourcing is ''always'' dependent on context'''; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Whilst secondary sources are more suitable, a reliable primary source such as a project's documentation or tertiary sources such as other wiki's are welcome but please ensure you do some due diligence to ensure it is up to date and accurate. If a page is in dire need of citations it can be tagged with the [[FW:Guidelines#Citations 2|relevant header template]], which you can read more about below. This should only be used on a page with controversial claims or is utilising content which has not been properly cited or attributed. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[FW:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[FW:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[FW:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[FW:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations where it would be appropriate, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. Before adding this template please consider if the page actually substantially requires citations as per the [[FW:Guidelines#Citations|Citation Policy]] or if there is just a handful of statements that need citations. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page. == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[FW:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[FW:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>FW:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://foss.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[FW:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''foss.wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 219b81f504ec6a9f6c3e17921480e474567e5e6a 8 1110 4581 2026-05-21T16:46:19Z Atmois 13 Update text wikitext text/x-wiki General Disclaimer 743da9350acac38bc458ab853c3a37bb2bf4cbe3 4595 4581 2026-05-21T21:58:44Z Atmois 13 Atmois moved page [[MediaWiki:Disclaimers]] to [[MediaWiki:Footer-disclaimer]] without leaving a redirect: consistency wikitext text/x-wiki General Disclaimer 743da9350acac38bc458ab853c3a37bb2bf4cbe3 4609 4595 2026-05-21T22:28:15Z Atmois 13 Shorten wikitext text/x-wiki Disclaimer 4c4a2e80cc873135b3d277a22b6e85110c509731 8 1111 4582 2026-05-21T16:46:41Z Atmois 13 Update case wikitext text/x-wiki Privacy Policy 9db108ba6b7f6571356060929e37dae65878cfca 4596 4582 2026-05-21T21:59:43Z Atmois 13 Atmois moved page [[MediaWiki:Privacy]] to [[MediaWiki:Footer-privacy]] without leaving a redirect: consistency wikitext text/x-wiki Privacy Policy 9db108ba6b7f6571356060929e37dae65878cfca 4 556 4584 4569 2026-05-21T16:58:46Z Atmois 13 Update values wikitext text/x-wiki == <u>About</u> == {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! '''foss.wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.foss.wiki Discord server]! To contact the administrators, check out our [[FW:Contact|contact page]]! If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord]! We have 4 key values for foss.wiki, that summarise all of our [[guidelines]] : # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. == <u>Important Links</u> == * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[Contributing]] - Outlines how YOU can contribute to foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer == <u>Wiki Staff</u> == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director * [[User:Scottc96|Scott96]] - Wiki Director ====== Operators ====== * [[User:Ow0cast|Ow0cast]] - Wiki Team & Moderator == '''<u>History</u>''' == === <u>Independence</u> ~ ''April 2026 - Present'' === '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] (promoted to co-director) remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. With the relaunch we setup of our status page with Phare at [https://status.foss.wiki status.foss.wiki] and launched our own [https://discord.foss.wiki Discord Server] and partnered with [https://discord.gg/nglinux Neon Genesis Linux], a server run by [[User:Scottc96|Scott96]] to provide high quality FOSS/Linux support and discussions. Our wiki deployment code is available on our new [https://github.foss.wiki GitHub] and we redeployed Umami analytics and updated our [[FW:Privacy policy|Privacy Policy]] to clarify some unclear data retention details as well as provide Opt Out information for Umami if users with to not be included in wiki usage analytics. Finally, we thank everyone who stuck with us especially former ATL staff for all their support and kindness during these tough times, every edit and every bit of support is valued and I am eternally grateful for everyone's help to make this fantastic resource for FOSS/Linux users, thank you and I hope to see you editing with us! ~ atmois === <u>ATL Ownership</u> ~ ''May 2024 - March 2026'' === ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. to be added: DDoS report, 1.0 release and wikibot launch ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[FW:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] ab029a1bcfd68307f5446dc31b22d9ae5b74bfbb 4619 4584 2026-05-22T18:09:30Z Atmois 13 Update title wikitext text/x-wiki == <u>About</u> == {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! '''FOSS Wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.foss.wiki Discord server]! To contact the administrators, check out our [[FW:Contact|contact page]]! If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord]! We have 4 key values for FOSS Wiki, that summarise all of our [[guidelines]] : # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. == <u>Important Links</u> == * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of FOSS Wiki * [[Contributing]] - Outlines how YOU can contribute to FOSS Wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of FOSS Wiki * [[FW:Disclaimer|Disclaimer]] - FOSS Wiki Editing Disclaimer == <u>Wiki Staff</u> == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director * [[User:Scottc96|Scott96]] - Wiki Director ====== Operators ====== * [[User:Ow0cast|Ow0cast]] - Wiki Team & Moderator == '''<u>History</u>''' == === <u>Independence</u> ~ ''April 2026 - Present'' === '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] (promoted to co-director) remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. With the relaunch we setup of our status page with Phare at [https://status.foss.wiki status.FOSS Wiki] and launched our own [https://discord.foss.wiki Discord Server] and partnered with [https://discord.gg/nglinux Neon Genesis Linux], a server run by [[User:Scottc96|Scott96]] to provide high quality FOSS/Linux support and discussions. Our wiki deployment code is available on our new [https://github.foss.wiki GitHub] and we redeployed Umami analytics and updated our [[FW:Privacy policy|Privacy Policy]] to clarify some unclear data retention details as well as provide Opt Out information for Umami if users with to not be included in wiki usage analytics. Finally, we thank everyone who stuck with us especially former ATL staff for all their support and kindness during these tough times, every edit and every bit of support is valued and I am eternally grateful for everyone's help to make this fantastic resource for FOSS/Linux users, thank you and I hope to see you editing with us! ~ atmois === <u>ATL Ownership</u> ~ ''May 2024 - March 2026'' === ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. to be added: DDoS report, 1.0 release and wikibot launch ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[FW:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] b3898c697818709de44f24936cea8a9839c1b8be 4 593 4587 4568 2026-05-21T17:01:22Z Atmois 13 Update values wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making foss.wiki an amazing resource for all users of FOSS and related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''foss.wiki''' uses. For users interested in writing guides for '''foss.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''foss.wiki''' you can see the wiki's [[FW:About|about]] page! Some important pages are also listed below: * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer If you ever have any questions or need help, you can join our [https://discord.foss.wiki Discord Server] and check out <code>#wiki</code> for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''foss.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 4 key values for '''foss.wiki''', that summarise all of our [[guidelines]]: # Accuracy: Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''foss.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[FW:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''foss.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another compatible free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[FW:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it meets the standards of the wiki as per the [[Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''foss.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[FW:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. Please ensure when making new pages you follow the [[FW:Guidelines#Notability Standards|Notability Standards]]! This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[FW:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distro's, it lacks a lot of major distro's and each section should have a short blurb and information about key facts about what distro's under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distro's that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. e4d2913a6f03d3eccd1952494243b00ea596197c 8 1112 4593 2026-05-21T21:49:39Z Atmois 13 Created page with "Donate" wikitext text/x-wiki Donate 95345e276ffbb748fffc3a9b8c9322bd0b489d39 8 1113 4597 2026-05-21T22:00:30Z Atmois 13 Created page with "About" wikitext text/x-wiki About 6b21fb791ac05170893860c248401cd24a59b732 4598 4597 2026-05-21T22:00:48Z Atmois 13 Atmois moved page [[MediaWiki:About]] to [[MediaWiki:Footer-about]] without leaving a redirect: consistency wikitext text/x-wiki About 6b21fb791ac05170893860c248401cd24a59b732 8 1107 4608 4563 2026-05-21T22:27:59Z Atmois 13 Shorten wikitext text/x-wiki Discord bccc14ee7da1d20ff06b9ff2497087e8c7d9f28b 4 571 4610 4523 2026-05-22T12:04:07Z Atmois 13 Update timeline for CheckUser IP retention, add backup retention policy and clarify change disclosure timespan and methods. wikitext text/x-wiki = foss.wiki Privacy Policy = Last Updated: 22 May 2026<blockquote>Update: Update timeline for CheckUser IP retention, add backup retention policy and clarify change disclosure timespan and methods. </blockquote>Welcome to '''foss.wiki'''<nowiki/>'s Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''foss.wiki'''. By accessing or contributing to '''foss.wiki''', you agree to the terms outlined in this Privacy Policy. == <u>Information foss.wiki Collects</u> == When you edit any article or page on '''foss.wiki''', you are creating a permanent, public record of any change, addition, removal made by you. Public records will show the time and username authoring the edits. ''To contribute to '''foss.wiki''', you are required to create an account. When registering, '''foss.wiki''' collects:'' * A Username * [Optionally] Your Email Address <blockquote>Other information such as your pronouns or Discord ID may be optionally provided to us via your user preferences or our Discord linking service.</blockquote> When a user is logged in '''foss.wiki''' uses essential cookies to maintain your login session and preferences. These cookies are required for the site to function and not shared nor used across other sites. Upon visiting the wiki the web-server will automatically log your IP Address and your User Agent, this information helps identify technical issues and ensure compatibility across devices. The web-server retains its logs for 30 days, after which it will automatically be deleted. Any PII stored in the MediaWiki database is retained in encrypted backups for up to 30 days from the point of creation. Backups are encrypted at creation, stored in an immutable state, and automatically purged after 30 days. Please note that following an erasure request, residual PII may persist in existing backups for up to 30 days before being purged. The IP address of an editor will also be logged by Mediawiki when an edit has been made for anti-vandalism efforts. The logged IP is only available to administrators and will only be used for the purpose of blocking or sanctioning malicious users. IPs are stored for 60 days, after which it will be deleted from the logs and no longer be accessible. However, due to the backup scheme they may persist in encrypted backups for a further 30 days, giving a maximum retention period of 90 days. <blockquote>The logging is provided by the [[mediawikiwiki:Extension:CheckUser|Check User Extension]].</blockquote> == <u>Services foss.wiki Uses</u> == '''foss.wiki''' uses a self-hosted instance of Umami Analytics to collect anonymous data about how visitors interact with our website. Umami collects: Page views, referring website and user agents. Umami does not collect personal data or use cookies, this data allows us to improve our site’s performance and user experience. Please note this data is kept indefinitely and cannot be removed as it does not store any identifiable information hence cannot be removed on an individual user basis. You can opt out of Umami's analytics for an individual device by entering <code>localStorage.setItem('umami.disabled', 1);</code> into your browser console or blocking the domain <code>analytics.foss.wiki</code> using an adblocker of your choice.. To reenable the collection you can run <code>localStorage.removeItem('umami.disabled');</code>. <blockquote>For more details, please see [https://umami.is/docs Umami's Documentation].</blockquote> '''foss.wiki''' also uses Cloudflare to enhance website security and performance. Cloudflare may process certain technical information, such as IP addresses and user agents, to provide services like content delivery, DDoS protection, and caching. Cloudflare also makes use of cookies to manage bot protection and verify access. These cookies are required for site security and functionality, please note that these cookies are managed by Cloudflare under their own privacy policy and data processing agreements. <blockquote>For more details, please see [https://www.cloudflare.com/en-gb/privacypolicy/ Cloudflare’s Privacy Policy].</blockquote> == <u>How foss.wiki uses your Information</u> == '''foss.wiki''' does not sell, trade, or otherwise transfer your personal information to third parties. '''foss.wiki''' will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where '''foss.wiki''' is present. '''foss.wiki''' will never provide your information to third parties without your explicit consent. Your account data is held as long as the wiki operates or until a erasure request is completed on your account. '''''foss.wiki''' use your data to do the following:'' * To send administrative notices via email. * For the ability to reset your account password via email. * To moderate and combat vandalism & spam on the wiki. * To correctly attribute contributions on the wiki to users. * To monitor and analyse the usage of our services and identify technical issues. '''foss.wiki''' uses a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so '''foss.wiki''' cannot guarantee that our security will not be breached. In the event of a data breach, '''foss.wiki''' will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities == <u>Your Rights</u> == ''Under the General Data Protection Regulation you are afforded the following rights:'' ; Right to be informed: : The right to be informed about the collection and use of their personal data. ; Right to access: : The right to access and receive a copy of their personal data, and other supplementary information. ; Right to rectification: : The right to have inaccurate personal data rectified, or completed if it is incomplete. ; Right to erasure: : The right to have personal data erased (Also known as being "forgotten"). ; Right to restrict processing: : The right to request the restriction or suppression of their personal data. ; Right to data portability: : The right to obtain and reuse their personal data for their own purposes across different services. ; Right to object: : The right to object to the processing of their personal data in certain circumstances. ; Right to control automated decision making: : The right to be informed about automated decision systems and are allowed to request human review. In order to comply with GDPR erasure requests and the licensing of content, '''foss.wiki''' has implemented a process to remove all your data from '''foss.wiki'''. Your account name will be anonymised and your edits will be reattributed to the anonymised username. You will be asked to remove your email and other personal information provided to us via your user preferences. Once this process has been completed your account will be "vanished", which removes it from public logs, then your account will be blocked to prevent future logins. An erasure request will be completed within one calendar month of '''foss.wiki''' receiving a request from the owner of the account. Please note however, as per "Information foss.wiki Collects", residual PII may persist in encrypted backups for up to 30 days following completion of the erasure process. IP addresses logged by CheckUser are not able to be cleared as part of the erasure process and will persist for up to 90 days from the point of logging across both the live database and encrypted backups. == <u>Changes to the Privacy Policy</u> == '''foss.wiki''' may change the Privacy Policy as needed to represent changes in our practises or legal requirements. '''foss.wiki''' will notify users of updates that impact them, and all revisions will be available on this page. We will notify users within 24 hours of any amendments via our Community Platforms as appropriate. If you do not agree with any changes made to this Privacy Policy, you may request an erasure of your account and personal data at any time in accordance with your Right to Erasure as outlined above. == <u>Third-party Links</u> == '''foss.wiki''' may contain links to third-party websites. '''foss.wiki''' is not responsible for the privacy practices or content of these sites. '''foss.wiki''' encourages users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>privacy@foss.wiki</code>. b9129ffcc7ac6947d40488ed76a4fa1cdc75baef 4615 4610 2026-05-22T18:01:48Z Atmois 13 Atmois moved page [[FW:Privacy policy]] to [[FW:Privacy Policy]]: Fix title wikitext text/x-wiki = foss.wiki Privacy Policy = Last Updated: 22 May 2026<blockquote>Update: Update timeline for CheckUser IP retention, add backup retention policy and clarify change disclosure timespan and methods. </blockquote>Welcome to '''foss.wiki'''<nowiki/>'s Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''foss.wiki'''. By accessing or contributing to '''foss.wiki''', you agree to the terms outlined in this Privacy Policy. == <u>Information foss.wiki Collects</u> == When you edit any article or page on '''foss.wiki''', you are creating a permanent, public record of any change, addition, removal made by you. Public records will show the time and username authoring the edits. ''To contribute to '''foss.wiki''', you are required to create an account. When registering, '''foss.wiki''' collects:'' * A Username * [Optionally] Your Email Address <blockquote>Other information such as your pronouns or Discord ID may be optionally provided to us via your user preferences or our Discord linking service.</blockquote> When a user is logged in '''foss.wiki''' uses essential cookies to maintain your login session and preferences. These cookies are required for the site to function and not shared nor used across other sites. Upon visiting the wiki the web-server will automatically log your IP Address and your User Agent, this information helps identify technical issues and ensure compatibility across devices. The web-server retains its logs for 30 days, after which it will automatically be deleted. Any PII stored in the MediaWiki database is retained in encrypted backups for up to 30 days from the point of creation. Backups are encrypted at creation, stored in an immutable state, and automatically purged after 30 days. Please note that following an erasure request, residual PII may persist in existing backups for up to 30 days before being purged. The IP address of an editor will also be logged by Mediawiki when an edit has been made for anti-vandalism efforts. The logged IP is only available to administrators and will only be used for the purpose of blocking or sanctioning malicious users. IPs are stored for 60 days, after which it will be deleted from the logs and no longer be accessible. However, due to the backup scheme they may persist in encrypted backups for a further 30 days, giving a maximum retention period of 90 days. <blockquote>The logging is provided by the [[mediawikiwiki:Extension:CheckUser|Check User Extension]].</blockquote> == <u>Services foss.wiki Uses</u> == '''foss.wiki''' uses a self-hosted instance of Umami Analytics to collect anonymous data about how visitors interact with our website. Umami collects: Page views, referring website and user agents. Umami does not collect personal data or use cookies, this data allows us to improve our site’s performance and user experience. Please note this data is kept indefinitely and cannot be removed as it does not store any identifiable information hence cannot be removed on an individual user basis. You can opt out of Umami's analytics for an individual device by entering <code>localStorage.setItem('umami.disabled', 1);</code> into your browser console or blocking the domain <code>analytics.foss.wiki</code> using an adblocker of your choice.. To reenable the collection you can run <code>localStorage.removeItem('umami.disabled');</code>. <blockquote>For more details, please see [https://umami.is/docs Umami's Documentation].</blockquote> '''foss.wiki''' also uses Cloudflare to enhance website security and performance. Cloudflare may process certain technical information, such as IP addresses and user agents, to provide services like content delivery, DDoS protection, and caching. Cloudflare also makes use of cookies to manage bot protection and verify access. These cookies are required for site security and functionality, please note that these cookies are managed by Cloudflare under their own privacy policy and data processing agreements. <blockquote>For more details, please see [https://www.cloudflare.com/en-gb/privacypolicy/ Cloudflare’s Privacy Policy].</blockquote> == <u>How foss.wiki uses your Information</u> == '''foss.wiki''' does not sell, trade, or otherwise transfer your personal information to third parties. '''foss.wiki''' will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where '''foss.wiki''' is present. '''foss.wiki''' will never provide your information to third parties without your explicit consent. Your account data is held as long as the wiki operates or until a erasure request is completed on your account. '''''foss.wiki''' use your data to do the following:'' * To send administrative notices via email. * For the ability to reset your account password via email. * To moderate and combat vandalism & spam on the wiki. * To correctly attribute contributions on the wiki to users. * To monitor and analyse the usage of our services and identify technical issues. '''foss.wiki''' uses a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so '''foss.wiki''' cannot guarantee that our security will not be breached. In the event of a data breach, '''foss.wiki''' will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities == <u>Your Rights</u> == ''Under the General Data Protection Regulation you are afforded the following rights:'' ; Right to be informed: : The right to be informed about the collection and use of their personal data. ; Right to access: : The right to access and receive a copy of their personal data, and other supplementary information. ; Right to rectification: : The right to have inaccurate personal data rectified, or completed if it is incomplete. ; Right to erasure: : The right to have personal data erased (Also known as being "forgotten"). ; Right to restrict processing: : The right to request the restriction or suppression of their personal data. ; Right to data portability: : The right to obtain and reuse their personal data for their own purposes across different services. ; Right to object: : The right to object to the processing of their personal data in certain circumstances. ; Right to control automated decision making: : The right to be informed about automated decision systems and are allowed to request human review. In order to comply with GDPR erasure requests and the licensing of content, '''foss.wiki''' has implemented a process to remove all your data from '''foss.wiki'''. Your account name will be anonymised and your edits will be reattributed to the anonymised username. You will be asked to remove your email and other personal information provided to us via your user preferences. Once this process has been completed your account will be "vanished", which removes it from public logs, then your account will be blocked to prevent future logins. An erasure request will be completed within one calendar month of '''foss.wiki''' receiving a request from the owner of the account. Please note however, as per "Information foss.wiki Collects", residual PII may persist in encrypted backups for up to 30 days following completion of the erasure process. IP addresses logged by CheckUser are not able to be cleared as part of the erasure process and will persist for up to 90 days from the point of logging across both the live database and encrypted backups. == <u>Changes to the Privacy Policy</u> == '''foss.wiki''' may change the Privacy Policy as needed to represent changes in our practises or legal requirements. '''foss.wiki''' will notify users of updates that impact them, and all revisions will be available on this page. We will notify users within 24 hours of any amendments via our Community Platforms as appropriate. If you do not agree with any changes made to this Privacy Policy, you may request an erasure of your account and personal data at any time in accordance with your Right to Erasure as outlined above. == <u>Third-party Links</u> == '''foss.wiki''' may contain links to third-party websites. '''foss.wiki''' is not responsible for the privacy practices or content of these sites. '''foss.wiki''' encourages users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>privacy@foss.wiki</code>. b9129ffcc7ac6947d40488ed76a4fa1cdc75baef 4617 4615 2026-05-22T18:06:14Z Atmois 13 Fix processor name wikitext text/x-wiki = FOSS Wiki Privacy Policy = Last Updated: 22 May 2026<blockquote>Update: Update timeline for CheckUser IP retention, add backup retention policy, clarify edit disclosure timespan and methods, fix processor name. </blockquote>Welcome to '''FOSS Wiki''' Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''FOSS Wiki'''. By accessing or contributing to '''FOSS Wiki''', you agree to the terms outlined in this Privacy Policy. == <u>Information FOSS Wiki Collects</u> == When you edit any article or page on '''FOSS Wiki''', you are creating a permanent, public record of any change, addition, removal made by you. Public records will show the time and username authoring the edits. ''To contribute to '''FOSS Wiki''', you are required to create an account. When registering, '''FOSS Wiki''' collects:'' * A Username * [Optionally] Your Email Address <blockquote>Other information such as your pronouns or Discord ID may be optionally provided to us via your user preferences or our Discord linking service.</blockquote> When a user is logged in to '''FOSS Wiki''' uses essential cookies to maintain your login session and preferences. These cookies are required for the site to function and not shared nor used across other sites. Upon visiting the wiki the web-server will automatically log your IP Address and your User Agent, this information helps identify technical issues and ensure compatibility across devices. The web-server retains its logs for 30 days, after which it will automatically be deleted. Any PII stored in the MediaWiki database is retained in encrypted backups for up to 30 days from the point of creation. Backups are encrypted at creation, stored in an immutable state, and automatically purged after 30 days. Please note that following an erasure request, residual PII may persist in existing backups for up to 30 days before being purged. The IP address of an editor will also be logged by Mediawiki when an edit has been made for anti-vandalism efforts. The logged IP is only available to administrators and will only be used for the purpose of blocking or sanctioning malicious users. IPs are stored for 60 days, after which it will be deleted from the logs and no longer be accessible. However, due to the backup scheme they may persist in encrypted backups for a further 30 days, giving a maximum retention period of 90 days. <blockquote>The logging is provided by the [[mediawikiwiki:Extension:CheckUser|Check User Extension]].</blockquote> == <u>Services FOSS Wiki Uses</u> == '''FOSS Wiki''' uses a self-hosted instance of Umami Analytics to collect anonymous data about how visitors interact with our website. Umami collects: Page views, referring website and user agents. Umami does not collect personal data or use cookies, this data allows us to improve our site’s performance and user experience. Please note this data is kept indefinitely and cannot be removed as it does not store any identifiable information hence cannot be removed on an individual user basis. You can opt out of Umami's analytics for an individual device by entering <code>localStorage.setItem('umami.disabled', 1);</code> into your browser console or blocking the domain <code>analytics.FOSS Wiki</code> using an adblocker of your choice.. To reenable the collection you can run <code>localStorage.removeItem('umami.disabled');</code>. <blockquote>For more details, please see [https://umami.is/docs Umami's Documentation].</blockquote> '''FOSS Wiki''' also uses Cloudflare to enhance website security and performance. Cloudflare may process certain technical information, such as IP addresses and user agents, to provide services like content delivery, DDoS protection, and caching. Cloudflare also makes use of cookies to manage bot protection and verify access. These cookies are required for site security and functionality, please note that these cookies are managed by Cloudflare under their own privacy policy and data processing agreements. <blockquote>For more details, please see [https://www.cloudflare.com/en-gb/privacypolicy/ Cloudflare’s Privacy Policy].</blockquote> == <u>How FOSS Wiki uses your Information</u> == '''FOSS Wiki''' does not sell, trade, or otherwise transfer your personal information to third parties. '''FOSS Wiki''' will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where '''FOSS Wiki''' is present. '''FOSS Wiki''' will never provide your information to third parties without your explicit consent. Your account data is held as long as the wiki operates or until a erasure request is completed on your account. '''''FOSS Wiki''' use your data to do the following:'' * To send administrative notices via email. * For the ability to reset your account password via email. * To moderate and combat vandalism & spam on the wiki. * To correctly attribute contributions on the wiki to users. * To monitor and analyse the usage of our services and identify technical issues. '''FOSS Wiki''' uses a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so '''FOSS Wiki''' cannot guarantee that our security will not be breached. In the event of a data breach, '''FOSS Wiki''' will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities == <u>Your Rights</u> == ''Under the General Data Protection Regulation you are afforded the following rights:'' ; Right to be informed: : The right to be informed about the collection and use of their personal data. ; Right to access: : The right to access and receive a copy of their personal data, and other supplementary information. ; Right to rectification: : The right to have inaccurate personal data rectified, or completed if it is incomplete. ; Right to erasure: : The right to have personal data erased (Also known as being "forgotten"). ; Right to restrict processing: : The right to request the restriction or suppression of their personal data. ; Right to data portability: : The right to obtain and reuse their personal data for their own purposes across different services. ; Right to object: : The right to object to the processing of their personal data in certain circumstances. ; Right to control automated decision making: : The right to be informed about automated decision systems and are allowed to request human review. In order to comply with GDPR erasure requests and the licensing of content, '''FOSS Wiki''' has implemented a process to remove all your data from '''FOSS Wiki'''. Your account name will be anonymised and your edits will be reattributed to the anonymised username. You will be asked to remove your email and other personal information provided to us via your user preferences. Once this process has been completed your account will be "vanished", which removes it from public logs, then your account will be blocked to prevent future logins. An erasure request will be completed within one calendar month of '''FOSS Wiki''' receiving a request from the owner of the account. Please note however, as per "Information FOSS Wiki Collects", residual PII may persist in encrypted backups for up to 30 days following completion of the erasure process. IP addresses logged by CheckUser are not able to be cleared as part of the erasure process and will persist for up to 90 days from the point of logging across both the live database and encrypted backups. == <u>Changes to the Privacy Policy</u> == '''FOSS Wiki''' may change the Privacy Policy as needed to represent changes in our practises or legal requirements. '''FOSS Wiki''' will notify users of updates that impact them, and all revisions will be available on this page. We will notify users within 24 hours of any amendments via our Community Platforms as appropriate. If you do not agree with any changes made to this Privacy Policy, you may request an erasure of your account and personal data at any time in accordance with your Right to Erasure as outlined above. == <u>Third-party Links</u> == '''FOSS Wiki''' may contain links to third-party websites. '''FOSS Wiki''' is not responsible for the privacy practices or content of these sites. '''FOSS Wiki''' encourages users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>privacy@foss.wiki</code>. cd30b5f6a0ca8f340534f4a8680dda96659cc5ad 4 1114 4616 2026-05-22T18:01:48Z Atmois 13 Atmois moved page [[FW:Privacy policy]] to [[FW:Privacy Policy]]: Fix title wikitext text/x-wiki #REDIRECT [[FW:Privacy Policy]] 73f77d2608b648631f83d100c0057e11815256a1 4 595 4620 4614 2026-05-22T18:09:57Z Atmois 13 Fix formatting wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.foss.wiki Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''admin(at)foss.wiki'' ~ To report security vulnerabilities please see our [https://foss.wiki/FW:Security Security Policy]. * [[User:Atmois|Atmois]] - Wiki Director ** ''zoe.m(at)foss.wiki'' * [[User:Scottc96|Scott96]] - Wiki Director ** scott.c(at)foss.wiki *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''none'' 881a20c281e1d9787f7c8d0e540fb182f470cf26 4623 4620 2026-05-22T18:12:24Z Atmois 13 Switch to internal link wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.foss.wiki Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all sysadmins at once please email: ''admin(at)foss.wiki'' ~ To report security vulnerabilities please see our [[FW:Security|Security Policy]]. * [[User:Atmois|Atmois]] - Wiki Director ** ''zoe.m(at)foss.wiki'' * [[User:Scottc96|Scott96]] - Wiki Director ** scott.c(at)foss.wiki *[[User:Ow0cast|Ow0cast]] - Wiki Team ** ''none'' e0d3fae30e02dc16cdade9a45ba3a01e5c6bd200 4 541 4621 4491 2026-05-22T18:10:13Z Atmois 13 Update title wikitext text/x-wiki All content unless specified otherwise is available under [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en Creative Commons Attribution-ShareAlike 4.0 International]. '''FOSS Wiki''' is an online collaborative source of information which is contributed to by individuals to provide a common resource of knowledge on Linux and FOSS related topics. The project is structured, so almost anyone can contribute and alter the content. Please note that any content found on '''FOSS Wiki''' has been verified by an expert in the relevant field. This does not mean you will not find valuable and accurate information on '''FOSS Wiki'''. However, '''FOSS Wiki''' cannot guarantee the validity of the information found here. The content of any given article may recently have been altered by someone whose personal beliefs may not align with established knowledge in the relevant fields. When you use '''FOSS Wiki''' you acknowledge the following: * <big>'''Review of Information'''</big><br>Whilst editors and '''FOSS Wiki''' team members attempt to review changes as much and often as we can, we cannot guarantee all pages are reviewed at the same frequency or rigour and that even a small change to a once reviewed page can invalidate the review. * <big>'''No Contract'''</big><br>All information on the wiki is provided freely with no contractual obligation between you, '''FOSS Wiki''' and its team, anyone who provides service to '''FOSS Wiki''' or any of the contributors. We are not responsible for information modified or removed on '''FOSS Wiki''' and the only agreement between you and '''FOSS Wiki''' is [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en Creative Commons Attribution-ShareAlike 4.0 International]. * <big>'''Trademarks'''</big><br>Any of the trademarks, service marks, collective marks, design rights, or similar rights that are mentioned, used, or cited on '''FOSS Wiki''' are the property of their respective owners. Their use here does not imply that you may use them for any purpose other than for the same or a similar informational use as contemplated by the original authors of these '''FOSS Wiki'''. Unless otherwise stated, '''FOSS Wiki''' is not endorsed by, nor affiliated with, any of the holders of any such rights, and as such, '''FOSS Wiki''' cannot grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk. * <big>'''Jurisdiction'''</big><br>'''FOSS Wiki''' content is stored on servers in Germany, and is maintained in reference to the protections afforded under German federal and EU law. Laws in your country or jurisdiction may not protect or permit the same kinds of speech or distribution. '''FOSS Wiki''' does not advocate for the violation of any laws and cannot be held responsible for any violations of such laws. * <big>'''Professional Advice'''</big><br>'''FOSS Wiki''' is not a source of professional advice, if you require professional advice please consult a professional who is licensed or knowledgeable in that area. 839ef0105188a09ce24c495c20c6833afba5269f 4 340 4622 4586 2026-05-22T18:10:57Z Atmois 13 Update title wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; FOSS Wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[FW:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[FW:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date''' and should strive to '''follow the guidelines below'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. If possible, you should '''cite your sources''' following the [[Guidelines#Citations|Citations Guidelines]] but please do not be discouraged from editing due to a lack of sources, any content is welcome and it can be improved upon as time goes on! ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] If you refer to or copy content (which is under a compatible license) it should be cited; this ensures the original author is credited for their work where relevant. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. We do not require claims and statements to be cited but if it can be challenged, it is always helpful to add a citation. If a claim is being challenged or you are unable to find a source, that's fine, just add the {{Citation needed}} template using <code><nowiki>{{Citation_needed}}</nowiki></code> or using the template inserter and another editor can help you find one or fill it out. Sources should be independent, ideally published and have a reputation for accuracy. '''Proper sourcing is ''always'' dependent on context'''; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Whilst secondary sources are more suitable, a reliable primary source such as a project's documentation or tertiary sources such as other wiki's are welcome but please ensure you do some due diligence to ensure it is up to date and accurate. If a page is in dire need of citations it can be tagged with the [[FW:Guidelines#Citations 2|relevant header template]], which you can read more about below. This should only be used on a page with controversial claims or is utilising content which has not been properly cited or attributed. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[FW:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[FW:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[FW:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[FW:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations where it would be appropriate, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. Before adding this template please consider if the page actually substantially requires citations as per the [[FW:Guidelines#Citations|Citation Policy]] or if there is just a handful of statements that need citations. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page. == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[FW:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[FW:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>FW:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://foss.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[FW:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''FOSS Wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] a2a25d950b67ee16bfafbeae083f5b72cb3f9f96 4 556 4624 4619 2026-05-22T18:18:01Z Atmois 13 Add new history wikitext text/x-wiki == <u>About</u> == {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! '''FOSS Wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.foss.wiki Discord server]! To contact the administrators, check out our [[FW:Contact|contact page]]! If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord]! We have 4 key values for FOSS Wiki, that summarise all of our [[guidelines]] : # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. == <u>Important Links</u> == * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of FOSS Wiki * [[Contributing]] - Outlines how YOU can contribute to FOSS Wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of FOSS Wiki * [[FW:Disclaimer|Disclaimer]] - FOSS Wiki Editing Disclaimer == <u>Wiki Staff</u> == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director * [[User:Scottc96|Scott96]] - Wiki Director ====== Operators ====== * [[User:Ow0cast|Ow0cast]] - Wiki Team & Moderator == '''<u>History</u>''' == === <u>Independence</u> ~ ''April 2026 - Present'' === '''May 2026''' We obtained the '''atl.wiki''' domain to act as a redirect to our new domain alongside doing some much needed improvements to the infrastructure to improve database backup resilience and improved our [[FW:Privacy Policy]] further with the new changes. We also opened up [https://donate.foss.wiki donations] via Open Collective to allow for quicker and larger improvements to the wiki utilising an independent bank and stripe accounts. Alongside this, [https://fibery.io Fibery] generously provided us an unlimited pro plan for the wiki! With this we setup a public [https://open.foss.wiki Ledger and Roadmap] which on it you can see exactly what we are planning and spending money on to keep the wiki running. On the 22nd of May we did our launch party, with the support of over half a dozen other communities we pushed the wiki into a new era. '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] (promoted to co-director) remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. With the relaunch we setup of our status page with Phare at [https://status.foss.wiki status.FOSS Wiki] and launched our own [https://discord.foss.wiki Discord Server] and partnered with [https://discord.gg/nglinux Neon Genesis Linux], a server run by [[User:Scottc96|Scott96]] to provide high quality FOSS/Linux support and discussions. Our wiki deployment code is available on our new [https://github.foss.wiki GitHub] and we redeployed Umami analytics and updated our [[FW:Privacy Policy|Privacy Policy]] to clarify some unclear data retention details as well as provide Opt Out information for Umami if users with to not be included in wiki usage analytics. Finally, we thank everyone who stuck with us especially former ATL staff for all their support and kindness during these tough times, every edit and every bit of support is valued and I am eternally grateful for everyone's help to make this fantastic resource for FOSS/Linux users, thank you and I hope to see you editing with us! ~ atmois === <u>ATL Ownership</u> ~ ''May 2024 - March 2026'' === ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. to be added: DDoS report, 1.0 release and wikibot launch ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[FW:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] b9ac16ef1ef464ddc26d344dcfdca7a0ff434d41 8 538 4625 4611 2026-05-22T19:14:32Z Atmois 13 Update for launch wikitext text/x-wiki '''FOSS.wiki has launched!''' Check out our [https://discord.foss.wiki Discord Server] to get updates on the wiki and see what we are up to. 6268f7d526eb82906f5a87daa64b310e05586e29 10 483 4626 4519 2026-05-22T19:20:08Z Madonuko 140 fix flex: treat entire text as 1 thing wikitext text/x-wiki <div class="mbox mbox-med mbox-cleanup" role="presentation"><span class="mbox-title"><span class="mbox-icon metadata">[[File:OOjs UI icon alert.svg]]</span><div>This article or section may require a cleanup. {{#if:{{{1|}}}|The specific problem is: '''{{{1}}}'''|No reason has been specified}}.</div></span> <div class="mbox-text">This template means a page might not meet the wiki's [[FW:Guidelines|guidelines]]. You can assist by <span class="plainlinks">[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing]</span> it. You can see [[:Category:Pages Needing Cleanup]] for other pages that still need to be reviewed.</div> </div><templatestyles src="Module:Mbox/styles.css" /><includeonly>{{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup|| [[Category:Pages Needing Cleanup]]}}</includeonly> <noinclude>{{/doc}}</noinclude> 1c1a75f2ebe82d0897fa28958175cfb0e89803a6 2 616 4627 2230 2026-05-22T19:28:18Z Wilbur 142 reset page pretty much might add more later wikitext text/x-wiki https://c48.uk backup 4d8c39b52394660d3024aba9e518e09479a9c60d 0 217 4628 4077 2026-05-22T19:28:45Z Madonuko 140 fix references & package manager section wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{stub}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Stable Release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022-04-21 (Accessed: 2025-09-03)</ref> |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}} [[Category:Linux Distributions]] [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is an independent [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref>, developed by the Fedora Project and its volunteers. Fedora Project was formed in 2003 by Red Hat<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref>, after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux is one of the two distributions, the other being Red Hat Enterprise Linux (RHEL), that emerged from its predecessor Red Hat Linux. It serves as an upstream for the latter.<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> == Release system == Fedora current follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], '''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</ref> System upgrades are usually handled offline to prevent system breakage == The package management system == :''Main article: [[dnf]]'' The main package manager is [[dnf]], which is usually called with the following arguments: {| class="wikitable" |+ <code>dnf</code> Usage |- ! Command !! Description |- | <code>sudo dnf up</code> || updates system packages |- | <code>sudo dnf in <pkg names> <...></code> || install new packages |- | <code>sudo dnf rm <pkg names> <...></code> || remove packages |- | <code>sudo dnf system-upgrade --relesever=<rel></code> || updates system version and packages<ref>[https://dnf.readthedocs.io/ DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</ref> |} == References == <references /> 80af1137dae1356d0d515a358c6ba992c19b4567 0 1115 4629 2026-05-22T19:36:44Z Tuxzilla 338 initial commit wikitext text/x-wiki COSMIC is a FOSS Desktop Environment created by System76, Also known as the creators of POP!_OS. Originally a modified version of the GNOME Desktop Environment, System76 released their Alpha version of their in-house DE written in the Rust Programming Language on August 8th 2024. The current stable release is 1.0.13, Released on May 12, 2026. cbc3d42e3c29fcd04bcebbced957a7daa226b7bc 0 924 4630 3926 2026-05-22T19:40:43Z Loudsynth 343 Add information for what TypeScript actually transpiles to, as it's not entirely obvious at first sight. wikitext text/x-wiki [[Category:Programming Languages]] {{stub}} '''TypeScript''' is an open-source programming language developed and maintained by [[Microsoft]]. It is a strict syntactical superset of [[JavaScript]] that adds optional static typing, making it easier to build and maintain large-scale applications. It transpiles (converts source code from one programming language to another) to [[JavaScript]]. 33c6f75f532e12be3a41696c14b2eae199e133ec 0 826 4631 3434 2026-05-22T19:47:55Z Uniolo 345 Added Helix to the 'Software' category, like other edits. wikitext text/x-wiki [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]] and [[Kakoune]]. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Helix bundles and enables many features out of the box and does not yet have a plugin system. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. However, many users decide to fork Helix in order to add functionality that isn't included out of the box. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] [[Category:Software]] 51e5a2397cd2b606b6df3e980a3d848cc2ddca73 4634 4631 2026-05-22T20:11:37Z Uniolo 345 Added the 'stub' and 'citation needed' templates, added some 'citation needed' citations and one proper citation. wikitext text/x-wiki {{Needs Citations}} {{stub|date=may 2026}} [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]]{{Citation needed}} and [[Kakoune]]<ref>[https://helix-editor.com/ Helix website] (accessed May 22nd, 2026)</ref>. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Helix bundles and enables many features out of the box and does not yet have a plugin system. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. However, many users decide to fork Helix in order to add functionality that isn't included out of the box{{Citation needed}}. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] [[Category:Software]] 4f24c8896c17a2bab87ec05a01b5c8e38bcdee1f 4636 4634 2026-05-22T20:15:15Z Uniolo 345 Changed citation to follow proper format (YYYY-MM-DD) wikitext text/x-wiki {{Needs Citations}} {{stub|date=may 2026}} [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]]{{Citation needed}} and [[Kakoune]]<ref>[https://helix-editor.com/ Helix website] (accessed 2026-05-22)</ref>. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Helix bundles and enables many features out of the box and does not yet have a plugin system. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. However, many users decide to fork Helix in order to add functionality that isn't included out of the box{{Citation needed}}. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] [[Category:Software]] 73483fe6ed909f59123d61e3f083628538c8c10d 4643 4636 2026-05-22T20:31:32Z Uniolo 345 Added sidebar with information about Helix wikitext text/x-wiki {{Needs Citations}} {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Helix editor.svg|thumb|The logo for Helix]] |caption=Helix Editor |title=Helix |releasestatus=Maintained |lastrelease=25.07.1, Jul 18, 2025 |firstrelease=0.0.2, May 12, 2021 |languages=[[Rust]] |developers=[https://mxxn.io/ Blaž Hrastnik] |website=[https://helix-editor.com/ helix-editor.com] }} [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]]{{Citation needed}} and [[Kakoune]]<ref>[https://helix-editor.com/ Helix website] (accessed 2026-05-22)</ref>. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Helix bundles and enables many features out of the box and does not yet have a plugin system. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. However, many users decide to fork Helix in order to add functionality that isn't included out of the box{{Citation needed}}. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. [[Category:Software]] 6148ff8b48b131df95f72b8c3cee27f911926b2e 6 1116 4632 2026-05-22T20:04:50Z Catperson 346 Kiki the Cyber Squirrel, the official mascot of Krita. Image from: https://krita.org/en/about/mascot/ wikitext text/x-wiki == Summary == Kiki the Cyber Squirrel, the official mascot of Krita. Image from: https://krita.org/en/about/mascot/ == Licensing == {{Unknown_copyright}} 403eeee4706162d6d951764e9afb3384f37bf6b9 14 390 4633 4328 2026-05-22T20:05:38Z Catperson 346 /* Program Mascots */ wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|64x64px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|64x64px]] |[[Kiki]] |[https://krita.org Krita] |} 8bee3f7820f4f33b777650ef0ba5d2c7b7973afa 4638 4633 2026-05-22T20:19:42Z Absurd 336 Added Noctalia Icon And Other Projects Mascots Section. wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|64x64px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|64x64px]] |[[Kiki]] |[https://krita.org Krita] |} ==== Other Projects Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:415656095680e1c6138277b0ba27e212.png|frameless|64x64px]] |[[Talia]] |[https://www.noctalia.dev Noctalia] |} 17bad29869784755be6d0d36393cce714990a686 4639 4638 2026-05-22T20:21:04Z Catperson 346 wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|64x64px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|64x64px]] |[https://krita.org/en/about/mascot/ KiKi] |[https://krita.org Krita] |} ==== Other Projects Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:415656095680e1c6138277b0ba27e212.png|frameless|64x64px]] |[[Talia]] |[https://www.noctalia.dev Noctalia] |} 3a853e47d4c0d9d4c57d0fa9ab1165ce0e5731a8 4642 4639 2026-05-22T20:27:42Z Absurd 336 /* Linux Kernel Mascots */ wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Tuz-logo.svg|alt=A drawing of a Tasmanian devil wearing a fake penguin beak,|frameless|76x76px]] |[[Taz]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|64x64px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|64x64px]] |[https://krita.org/en/about/mascot/ KiKi] |[https://krita.org Krita] |} ==== Other Projects Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:415656095680e1c6138277b0ba27e212.png|frameless|64x64px]] |[[Talia]] |[https://www.noctalia.dev Noctalia] |} 6b0929a33f28bb392cf7c1d9870b8ef4974197e1 4646 4642 2026-05-22T20:36:25Z Absurd 336 Added The Sudo Sandwhich Mascot wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Tuz-logo.svg|alt=A drawing of a Tasmanian devil wearing a fake penguin beak,|frameless|76x76px]] |[[Taz]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|64x64px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|64x64px]] |[https://krita.org/en/about/mascot/ KiKi] |[https://krita.org Krita] |} ==== Other Projects Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:415656095680e1c6138277b0ba27e212.png|frameless|64x64px]] |[[Talia]] |[https://www.noctalia.dev Noctalia] |- |[[File:Sudo-sandwich-logo-65.png |frameless|64x64px]] |[[Sudo Sandwich]] |[https://www.sudo.ws Sudo] |} f00217a66178b0a86f7028c15060f9fab13b42b9 6 1117 4635 2026-05-22T20:14:26Z Absurd 336 wikitext text/x-wiki I asked the Dev If I may use it. be034999c884e217013bc07254beaaabd00fd5ed 2 325 4637 1926 2026-05-22T20:18:16Z Katz 53 wikitext text/x-wiki <big> Hi I'm Mosquito (formerly Katz) </big> <p>You say you didn't eat those plans</p> <h5>But here's the ultrasound.</h5> 9f67e272a9d12e510b943420bcbbebc83c1337c5 2 1118 4640 2026-05-22T20:21:22Z Noah-or13 350 I wrote about myself very briefly cuz i dont like sharing alot abt me wikitext text/x-wiki I like foss stuff, I'm genderfluid and I love contributing to info that people learn off 6ec4550c37737e60b2c979d3c32f04c7396e2e58 4655 4640 2026-05-22T20:58:21Z Noah-or13 350 wikitext text/x-wiki I like foss stuff and I love contributing to info that people learn off f06d4b39aacd5fccafa251606b29a545e305a456 0 203 4641 4135 2026-05-22T20:26:36Z Alurker 347 correct potentially harmful miss information (common usage), correct information regarding binaries and default desktops, link to gentoo wiki instead of unneeded internal pages (to prevent more future miss information as much as possible should be off loaded to official pages), remove the eselect section it is unneeded and was wrong, eselect is not used to manage slots, remove key-components section due to being incorrect and not necessary wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [https://wiki.gentoo.org/wiki/Portage portage] | defaultdesktops = None, User Choice | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]].<ref>[https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer) Daniel Robbins (computer programmer)], Wikipedia contributors, 2024-01-10 (Accessed: 2025-08-09)</ref> Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to customize their system to a degree way beyond other distributions by providing granular control over system packages and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This approach, while more time-consuming than other distributions due to it's complexity, enables optimizations specific to the user's hardware and requirements. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements and runs on nearly anything you throw it at although some lesser used architectures will not have binaries. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "[https://wiki.gentoo.org/wiki/SLOT slotting]". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use xfs, ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp)</syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [https://wiki.gentoo.org/wiki/Portage Portage] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge --ask --update --deep --newuse @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge --ask package</code> | Install a package |- | <code>emerge --deselect package</code> | Remove a package from the [https://wiki.gentoo.org/wiki/Selected_set_(Portage) selected set] |- | <code>emerge --pretend --verbose package</code> | Preview package installation |- | <code>emerge --depclean</code> | Remove unneeded packages |- |<code>emerge --unmerge / emerge -C</code> |Do not use unless you know what you are doing removes a package without checking dependencies even core system packages |- |<code>emerge --pretend --verbose --depclean package</code> |Check what depends on package |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. === Binary Packages === Gentoo offers binaries like any other distribution but it needs to be explicitly enabled refer to the [https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart Binary Host Quickstart guide] for detailed information == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === One might be interested in community resources for '''Gentoo.''' The official community forums can be found at [https://forums.gentoo.org/ forums.gentoo.org/]. Additionally, IRC<ref>Internet Relay Chat</ref> channels has been setup as well. For those who are interested in the official IRC channels, they can be found on the '''Gentoo Wiki''' in the [https://wiki.gentoo.org/wiki/IRC IRC] article. It is possible to subscribe to the [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] or even send emails to them, the page lists the most important lists with the most traffic. There are other, more specialized lists that might be more appropriate depending on the topic. There is a [https://www.gentoo.org/support/documentation/ wiki documentation] available as well. Users can search up specific pages in the site directly, so that they don't waste time finding the right page. Ultimately, '''Gentoo''' offers a [https://bugs.gentoo.org/ bug tracking system] for those who are interested in being up to date with current bugs, or even attempt to solve them. === Development Model === '''Gentoo''' was developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the user base through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == '''Gentoo''' allows maximum customization, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to use binaries. However, Gentoo has it's own downsides; It will take longer to install packages as portage is very complex so resolving dependencies and installing packages will take a little bit longer than other distributions and if you use USE flags that are non standard you might have to compile the package which will also take longer depending on your hardware, The Operating System has a higher learning curve as its very complex, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://wiki.gentoo.org/wiki/Portage Portage] * [https://planet.gentoo.org/ Gentoo Planet] 0facb95e9b9f7b60c4e78c3535cef623c37c1176 4644 4641 2026-05-22T20:34:30Z Alurker 347 This page had a lot of outdated or plain wrong information some even dangerous like common usage saying emerge -C and emerge --unmerge should be used for removing packages, this change aims to correct some outdated information and link to the gentoo wiki when it makes sense instead of pointing to outdated pages internally wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [https://wiki.gentoo.org/wiki/Portage portage] | defaultdesktops = None, User Choice | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]].<ref>[https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer) Daniel Robbins (computer programmer)], Wikipedia contributors, 2024-01-10 (Accessed: 2025-08-09)</ref> Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to customize their system to a degree way beyond other distributions by providing granular control over system packages and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This approach, while more time-consuming than other distributions due to it's complexity, enables optimizations specific to the user's hardware and requirements. A common myth says that a user must compile everything in '''Gentoo''' or that the [https://wiki.gentoo.org/wiki/Project:Binhost Project:Binhost] is anti-Gentoo. The irony being that Gentoo was created to be all about user choice, and all the binhost provides is a choice to its users. Using the binhost doesn't prevent a user from compiling the packages they want to modify, as both binary and source-built packages can coexist seamlessly. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements and runs on nearly anything you throw it at although some lesser used architectures will not have binaries. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "[https://wiki.gentoo.org/wiki/SLOT slotting]". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use xfs, ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp)</syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [https://wiki.gentoo.org/wiki/Portage Portage] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge --ask --update --deep --newuse @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge --ask package</code> | Install a package |- | <code>emerge --deselect package</code> | Remove a package from the [https://wiki.gentoo.org/wiki/Selected_set_(Portage) selected set] |- | <code>emerge --pretend --verbose package</code> | Preview package installation |- | <code>emerge --depclean</code> | Remove unneeded packages |- |<code>emerge --unmerge / emerge -C</code> |Do not use unless you know what you are doing removes a package without checking dependencies even core system packages |- |<code>emerge --pretend --verbose --depclean package</code> |Check what depends on package |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. === Binary Packages === Gentoo offers binaries like any other distribution but it needs to be explicitly enabled refer to the [https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart Binary Host Quickstart guide] for detailed information == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === One might be interested in community resources for '''Gentoo.''' The official community forums can be found at [https://forums.gentoo.org/ forums.gentoo.org/]. Additionally, IRC<ref>Internet Relay Chat</ref> channels has been setup as well. For those who are interested in the official IRC channels, they can be found on the '''Gentoo Wiki''' in the [https://wiki.gentoo.org/wiki/IRC IRC] article. It is possible to subscribe to the [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] or even send emails to them, the page lists the most important lists with the most traffic. There are other, more specialized lists that might be more appropriate depending on the topic. There is a [https://www.gentoo.org/support/documentation/ wiki documentation] available as well. Users can search up specific pages in the site directly, so that they don't waste time finding the right page. Ultimately, '''Gentoo''' offers a [https://bugs.gentoo.org/ bug tracking system] for those who are interested in being up to date with current bugs, or even attempt to solve them. === Development Model === '''Gentoo''' was developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the user base through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == '''Gentoo''' allows maximum customization, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to use binaries. However, Gentoo has it's own downsides; It will take longer to install packages as portage is very complex so resolving dependencies and installing packages will take a little bit longer than other distributions and if you use USE flags that are non standard you might have to compile the package which will also take longer depending on your hardware, The Operating System has a higher learning curve as its very complex, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://wiki.gentoo.org/wiki/Portage Portage] * [https://planet.gentoo.org/ Gentoo Planet] f45fe6b4e634f90dd11067f59e3c24e8f9505f13 4647 4644 2026-05-22T20:37:54Z Alurker 347 fix formatting that slipped past wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [https://wiki.gentoo.org/wiki/Portage portage] | defaultdesktops = None, User Choice | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]].<ref>[https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer) Daniel Robbins (computer programmer)], Wikipedia contributors, 2024-01-10 (Accessed: 2025-08-09)</ref> Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to customize their system to a degree way beyond other distributions by providing granular control over system packages and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This approach, while more time-consuming than other distributions due to it's complexity, enables optimizations specific to the user's hardware and requirements. A common myth says that a user must compile everything in '''Gentoo''' or that the [https://wiki.gentoo.org/wiki/Project:Binhost Project:Binhost] is anti-Gentoo. The irony being that Gentoo was created to be all about user choice, and all the binhost provides is a choice to its users. Using the binhost doesn't prevent a user from compiling the packages they want to modify, as both binary and source-built packages can coexist seamlessly. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements and runs on nearly anything you throw it at although some lesser used architectures will not have binaries. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "[https://wiki.gentoo.org/wiki/SLOT slotting]". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. The first step of the installation is to prepare the installation environment, which involves downloading the .iso first. '''Gentoo''' allows the following boot medias (amd64); Minimal Installation CD, QCOW2 disk and LiveGUI USB Image. The next step involves networking, by default, '''Gentoo''' recommends using [[DHCP]] to assist in network configuration, and can automatically provide configuration for a variety of parameters, those include but are not limited to: IP Addresses, DNS servers, NTP servers, routes, etc. After configuring the networking, the user should format the necessary partitions for installing the Operating System on the disk. The user can choose whether to use xfs, ext4, btrfs and other file systems. Once the partitioning is ready, the user will now install the stage file, which include the core of the '''Gentoo''' Operating System. The user will have to make a choice between OpenRC and Systemd ( other init systems can be chosen if desired ). Additionally, the user can select different system profiles.<syntaxhighlight lang="shell-session">[user@hostname ~]$ eselect profile list Available profile symlink targets: [1] default/linux/amd64/23.0 (stable) [2] default/linux/amd64/23.0/systemd (stable) [3] default/linux/amd64/23.0/desktop (stable) [4] default/linux/amd64/23.0/desktop/systemd (stable) [5] default/linux/amd64/23.0/desktop/gnome (stable) [6] default/linux/amd64/23.0/desktop/gnome/systemd (stable) [7] default/linux/amd64/23.0/desktop/plasma (stable) [8] default/linux/amd64/23.0/desktop/plasma/systemd (stable) [9] default/linux/amd64/23.0/no-multilib (stable) [10] default/linux/amd64/23.0/no-multilib/systemd (stable) [11] default/linux/amd64/23.0/no-multilib/hardened (stable) [12] default/linux/amd64/23.0/no-multilib/hardened/systemd (stable) [13] default/linux/amd64/23.0/no-multilib/hardened/selinux (stable) [14] default/linux/amd64/23.0/no-multilib/hardened/selinux/systemd (stable) [15] default/linux/amd64/23.0/no-multilib/prefix (exp) [16] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.32+ (exp) [17] default/linux/amd64/23.0/no-multilib/prefix/kernel-2.6.16+ (exp) [18] default/linux/amd64/23.0/no-multilib/prefix/kernel-3.2+ (exp) [19] default/linux/amd64/23.0/llvm (exp) [20] default/linux/amd64/23.0/llvm/systemd (exp) [21] default/linux/amd64/23.0/hardened (stable) [22] default/linux/amd64/23.0/hardened/systemd (stable) [23] default/linux/amd64/23.0/hardened/selinux (stable) [24] default/linux/amd64/23.0/hardened/selinux/systemd (stable) [25] default/linux/amd64/23.0/split-usr (stable) [26] default/linux/amd64/23.0/split-usr/desktop (stable) [27] default/linux/amd64/23.0/split-usr/desktop/gnome (stable) [28] default/linux/amd64/23.0/split-usr/desktop/plasma (stable) [29] default/linux/amd64/23.0/split-usr/no-multilib (stable) [30] default/linux/amd64/23.0/split-usr/no-multilib/selinux (stable) [31] default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable) [32] default/linux/amd64/23.0/split-usr/no-multilib/hardened/selinux (stable) [33] default/linux/amd64/23.0/split-usr/no-multilib/prefix (exp) [34] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.32+ (exp) [35] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-2.6.16+ (exp) [36] default/linux/amd64/23.0/split-usr/no-multilib/prefix/kernel-3.2+ (exp) [37] default/linux/amd64/23.0/split-usr/llvm (exp) [38] default/linux/amd64/23.0/split-usr/hardened (stable) [39] default/linux/amd64/23.0/split-usr/hardened/selinux (stable) [40] default/linux/amd64/23.0/x32 (dev) [41] default/linux/amd64/23.0/x32/systemd (exp) [42] default/linux/amd64/23.0/split-usr/x32 (exp) [43] default/linux/amd64/23.0/musl (dev) [44] default/linux/amd64/23.0/musl/llvm (exp) [45] default/linux/amd64/23.0/musl/hardened (exp) [46] default/linux/amd64/23.0/musl/hardened/selinux (exp) [47] default/linux/amd64/23.0/split-usr/musl (dev) [48] default/linux/amd64/23.0/split-usr/musl/llvm (exp) [49] default/linux/amd64/23.0/split-usr/musl/hardened (exp) [50] default/linux/amd64/23.0/split-usr/musl/hardened/selinux (exp)</syntaxhighlight>Once completed with the stage file, the user is expected to install the base system, which includes copying the DNS info to the <code>/mnt/gentoo/etc/</code> directory, mounting the necessary filesystems, entering the new environment, preparing the bootloader and configuring portage. In the next part of the installation, the user will have to install the kernel, optionally they can download the linux firmware package. On many systems, non-FOSS firmware is required for certain hardware to function. The <code>sys-kernel/linux-firmware</code> package contains firmware for many, but not all, devices. The kernel, can be either compiled from source or installed as a binary. Afterwards the user will now configure the system itself; fstab, hostname, root password. Lastly, the user will now configure the bootloader, by default Gentoo recommends GRUB, but other bootloaders may be used. The user will now create their respective user account and reboot the system, where they will then be greeted by the '''Gentoo''' TTY. The user will now choose between a Desktop Environment or a Window Manager. For detailed installation instructions, refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook]. == Package Management == === Portage === [https://wiki.gentoo.org/wiki/Portage Portage] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration: ==== Common Usage ==== {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge --ask --update --deep --newuse @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge --ask package</code> | Install a package |- | <code>emerge --deselect package</code> | Remove a package from the [https://wiki.gentoo.org/wiki/Selected_set_(Portage) selected set] |- | <code>emerge --pretend --verbose package</code> | Preview package installation |- | <code>emerge --depclean</code> | Remove unneeded packages |- |<code>emerge --unmerge / emerge -C</code> |'''Do not use unless you know what you are doing''' removes a package without checking dependencies even core system packages |- |<code>emerge --pretend --verbose --depclean package</code> |Check what depends on package |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. USE flags combinations can also be used for removing or adding any type of support to the desired packages, but the kernel must be configured manually for more customization. One can also set package-specific USE flags thru <code>package.use</code> inside their <code>/etc/portage/</code> directory. The user must read the '''Gentoo Wiki''' carefully to fully understand these topics, as they can be quite challenging to comprehend as a new '''Gentoo''' user. === Binary Packages === Gentoo offers binaries like any other distribution but it needs to be explicitly enabled refer to the [https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart Binary Host Quickstart guide] for detailed information == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === One might be interested in community resources for '''Gentoo.''' The official community forums can be found at [https://forums.gentoo.org/ forums.gentoo.org/]. Additionally, IRC<ref>Internet Relay Chat</ref> channels has been setup as well. For those who are interested in the official IRC channels, they can be found on the '''Gentoo Wiki''' in the [https://wiki.gentoo.org/wiki/IRC IRC] article. It is possible to subscribe to the [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] or even send emails to them, the page lists the most important lists with the most traffic. There are other, more specialized lists that might be more appropriate depending on the topic. There is a [https://www.gentoo.org/support/documentation/ wiki documentation] available as well. Users can search up specific pages in the site directly, so that they don't waste time finding the right page. Ultimately, '''Gentoo''' offers a [https://bugs.gentoo.org/ bug tracking system] for those who are interested in being up to date with current bugs, or even attempt to solve them. === Development Model === '''Gentoo''' was developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the user base through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == '''Gentoo''' allows maximum customization, optimal performance through compilation, complete control over features, extensive documentation, active community support and ability to use binaries. However, Gentoo has it's own downsides; It will take longer to install packages as portage is very complex so resolving dependencies and installing packages will take a little bit longer than other distributions and if you use USE flags that are non standard you might have to compile the package which will also take longer depending on your hardware, The Operating System has a higher learning curve as its very complex, though one can learn how the system functions very quickly, one might prefer a more out-of-the-box experience rather than a Do-It-Yourself distribution. Since '''Gentoo''' is a Do-It-Yourself distribution, one will require more technical knowledge than the average user. Regular maintenance is not much needed, but recommended. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://wiki.gentoo.org/wiki/Portage Portage] * [https://planet.gentoo.org/ Gentoo Planet] b421df691937e7d1b8182e43d7eebbfe75c95a80 6 1119 4645 2026-05-22T20:35:23Z Absurd 336 © 2019 by Mark Stillman and licensed under CCBY 4.0. wikitext text/x-wiki == Summary == © 2019 by Mark Stillman and licensed under CCBY 4.0. == Licensing == {{CC-BY-4.0}} 6bd390a8c2d58ed98f5c645cc1181b273ff32514 0 558 4648 4151 2026-05-22T20:41:03Z Deviaze 341 Rewrite lede to make it more general and better written. wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[Rust]], originally written in [[OCaml]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust is a modern multi-paradigm programming language with a focus on performance, reliability, and productivity<ref>https://github.com/rust-lang/rust</ref>. Although originally designed as a systems-level language, Rust has found widespread adoption as a general purpose programming language thanks to its high degree of expressiveness, strict type safety and memory safety, its easy-to-use package manager Cargo and crates ecosystem, and its ability to achieve native performance with high level code. Rust was heavily inspired by functional programming languages in its emphasis on immutability and pattern matching, as well as by [[C++]] for its RAII (resource allocation is initialization) and other performance features. Rust is most often compared with and considered an alternative to C++. In 2025, Rust was officially accepted into the [[Linux|Linux kernel]]<ref>https://www.phoronix.com/news/Rust-To-Stay-Linux-Kernel</ref>, after a lengthy trial period (the Rust for Linux experiment) that started in December 2022, becoming the third language accepted in the kernel after [[C]] and [[assembly]]. [[Canonical]], the company behind Ubuntu and other FOSS, is replacing the GNU coreutils project, written in C, with uutils, a Rust rewrite<ref>https://archive.fosdem.org/2025/schedule/event/fosdem-2025-6196-rewriting-the-future-of-the-linux-essential-packages-in-rust-/</ref>. This has attracted criticism around its licensing changing from GNU GPL to MIT and makes uutils more friendly to proprietary software<ref>https://github.com/uutils/coreutils/issues/834</ref>. === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Variable Types === {| class="wikitable" |+Data Types (Integers / Floats) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. [[OO]]P allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref><ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref> Rust takes a different approach to OOP with its use of <code>struct</code>s, <code>trait</code>s, <code>enum</code>s, and <code>impl</code>s.<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, <code>struct</code>s in Rust can store multiple related values as fields. The difference is that fields must be referred via their given naming. <code>struct</code>s are more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> <syntaxhighlight lang="rust" lines> // Having the struct outside of main() makes it available everywhere in the file struct MyStruct { field1: bool, field2: i32, field3: String, } fn main() { let object = MyStruct { field1: true, field2: 64, field3: String::from("Use structs you must!"), }; } </syntaxhighlight> Functional properties may be given to <code>struct</code>s with <code>impl</code>s, which stands for ''implement''. Having methods (i.e. functions in <code>impl</code> with <code>self</code>, <code>&self</code> or <code>&mut self</code> as the first parameter) also allows for reproducibility, since they can access <code>struct</code> fields via <code>self</code>. <ref name=":0" /><ref name=":2" /> <syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height } } fn main() { let rubiks_cube = Cube { length: 3, width: 3, height: 3, }; println!("Cube's volume: {}", rubiks_cube.volume()); } </syntaxhighlight> The code declares a new struct with 3 values and an area finder function within the <code>impl Cube</code> scope. The <code>volume()</code> method may be used on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == 6aac49e252452c5cbc764e9b849cccf13f373212 4668 4648 2026-05-22T21:18:38Z Deviaze 341 /* Variable Types */ add string types wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[Rust]], originally written in [[OCaml]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust is a modern multi-paradigm programming language with a focus on performance, reliability, and productivity<ref>https://github.com/rust-lang/rust</ref>. Although originally designed as a systems-level language, Rust has found widespread adoption as a general purpose programming language thanks to its high degree of expressiveness, strict type safety and memory safety, its easy-to-use package manager Cargo and crates ecosystem, and its ability to achieve native performance with high level code. Rust was heavily inspired by functional programming languages in its emphasis on immutability and pattern matching, as well as by [[C++]] for its RAII (resource allocation is initialization) and other performance features. Rust is most often compared with and considered an alternative to C++. In 2025, Rust was officially accepted into the [[Linux|Linux kernel]]<ref>https://www.phoronix.com/news/Rust-To-Stay-Linux-Kernel</ref>, after a lengthy trial period (the Rust for Linux experiment) that started in December 2022, becoming the third language accepted in the kernel after [[C]] and [[assembly]]. [[Canonical]], the company behind Ubuntu and other FOSS, is replacing the GNU coreutils project, written in C, with uutils, a Rust rewrite<ref>https://archive.fosdem.org/2025/schedule/event/fosdem-2025-6196-rewriting-the-future-of-the-linux-essential-packages-in-rust-/</ref>. This has attracted criticism around its licensing changing from GNU GPL to MIT and makes uutils more friendly to proprietary software<ref>https://github.com/uutils/coreutils/issues/834</ref>. === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Data Types === Rust has a number of primitive builtin types, denoted in lowercase, as well as complex objects from the standard library that behave like primitives in other languages. {| class="wikitable" |+Primitive integer types (signed/unsigned) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} Rust does not have a single string type; below is a non-comprehensive list of the most common ways to represent a string: {| class="wikitable" |+String types !Name !Stack or heap !Description |- |<code>&str</code> |Stack |A reference to a UTF-8 string slice, <code>str</code>only really exists as a reference type. These are immutable. |- |<code>&'static str</code> |Stack |The type of a string literal embedded into sourcecode. The <code>'static</code> lifetime means that the <code>&str</code> lasts forever. |- |<code>char</code> |Stack |Represents a single UTF-8 codepoint. |- |<code>String</code> |Heap |A full heap-allocated, possibly mutable UTF-8 string. |- |<code>Vec<u8></code> |Heap |A heap-allocated list of arbitrary bytes; it's not actually a string, but it's commonly used instead of a <code>String</code> when you want to represent data that isn't necessarily UTF-8 encoded. |- |<code>Cow</code> |Might be either |Stands for copy-on-write. |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. [[OO]]P allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref><ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref> Rust takes a different approach to OOP with its use of <code>struct</code>s, <code>trait</code>s, <code>enum</code>s, and <code>impl</code>s.<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, <code>struct</code>s in Rust can store multiple related values as fields. The difference is that fields must be referred via their given naming. <code>struct</code>s are more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> <syntaxhighlight lang="rust" lines> // Having the struct outside of main() makes it available everywhere in the file struct MyStruct { field1: bool, field2: i32, field3: String, } fn main() { let object = MyStruct { field1: true, field2: 64, field3: String::from("Use structs you must!"), }; } </syntaxhighlight> Functional properties may be given to <code>struct</code>s with <code>impl</code>s, which stands for ''implement''. Having methods (i.e. functions in <code>impl</code> with <code>self</code>, <code>&self</code> or <code>&mut self</code> as the first parameter) also allows for reproducibility, since they can access <code>struct</code> fields via <code>self</code>. <ref name=":0" /><ref name=":2" /> <syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height } } fn main() { let rubiks_cube = Cube { length: 3, width: 3, height: 3, }; println!("Cube's volume: {}", rubiks_cube.volume()); } </syntaxhighlight> The code declares a new struct with 3 values and an area finder function within the <code>impl Cube</code> scope. The <code>volume()</code> method may be used on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == 9b12da6c0d37042e17dba2efadacdb18cba5a0cc 0 394 4649 4472 2026-05-22T20:43:53Z Brochard 351 Add Redox OS in Other UNIX-like operating systems wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other UNIX-like ==== {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in Rust |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} c1f66bff165cfcd3747504ef43cbf0c3a55a64a6 4652 4649 2026-05-22T20:55:25Z Brochard 351 Add ReactOS in other operating systems wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other UNIX-like ==== {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in Rust |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} fa5d0a47537428e3f0cc22bfa49252161ae1488a 4657 4652 2026-05-22T20:59:49Z Brochard 351 Add Rust link to Redox OS wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other UNIX-like ==== {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} 21eb50b5e3d2ca537ef6b811807195ca189a542d 0 198 4650 4471 2026-05-22T20:51:02Z Boxhed 355 wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Atomic]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == b923600e770e18ff6554e0bad28b9016a2c51ac7 4662 4650 2026-05-22T21:08:55Z Brochard 351 Add AerynOS to Other Independent Distributions wikitext text/x-wiki [[Category:Linux Distributions]] A Linux distribution (sometimes abbreviated as a 'distro') is a distribution of software consisting of some form of the [[Linux|Linux kernel]], an [[Init System]] (such as [[Systemd]] or [[OpenRC]]), core utilities and libraries (such as the ones provided by [[GNU]]), documentation, a [[Package Manager]] and several other types of software. Often to provide a desktop e<bdi>xperience</bdi> a display server (such as [[X.Org]] or a [[Wayland]] compositor like Kwin), a [[Desktop Environments|Desktop Environment]] or [[Window Manager]] (such as [[GNOME]] or [[i3]]) and other programs may be included with the distribution or are installable from [[Repository|repositories]]. == List of Linux Distributions == This is in no way an all inclusive list of [[Linux]] distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Atomic]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == c32febdf9df8fb53b4af15b50e92b4f0aac202ac 0 1120 4651 2026-05-22T20:52:53Z Uniolo 345 Create the page, for the citation, I chose it because it was inked on the Vim website and would be easier to cite than the Vim website. Will do more work. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]] |developers=Bram Moolenaar |website=[https://www.vim.org/ vim.org] }} [[Vim]] is a [[Vi]] like editor. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref>[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. [[Category:Software]] <references /> 2c1f8d867bc46a1a28f30a36671e3fb9f96eece2 4658 4651 2026-05-22T21:02:11Z Uniolo 345 Added some general information about vim, including what it is an acronym to. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[Vim]] is a [[Vi]] like editor that stands for Vi IMproved<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref>[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to what is typical from a standard text editor. [[Category:Software]] <references /> [[File:Vim 9.0 splash screen.png|thumb|Vim 9.0 Splash Screen]] 0c78c2b54f0a2fb0b390369ef16789a6da9a4b37 4663 4658 2026-05-22T21:09:05Z Uniolo 345 Replaced the image of Vim (from Wikicommons) with one I took as the one I took includes the "Help kids in Uganda" message, giving context to the earlier "Charityware" statement. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[Vim]] is a [[Vi]] like editor that stands for Vi IMproved<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref>[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to what is typical from a standard text editor. [[Category:Software]] <references /> [[File:Vim-splash.png|thumb|The Vim Splash Screen]] 18de0e251eac590fc37add263d636c6d8e78f70d 4665 4663 2026-05-22T21:10:34Z Uniolo 345 Fixed grammatical error. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[Vim]] is a [[Vi]] like editor that stands for Vi IMproved<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref>[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. [[Category:Software]] <references /> [[File:Vim-splash.png|thumb|The Vim Splash Screen]] f414efbdee5e113f792afa7a4a356acefb38d116 0 1121 4653 2026-05-22T20:57:04Z LilyWayLolz 354 Made the page and added the basics wikitext text/x-wiki [https://psysonic.de Psysonic] is a local music streaming client made for Navidrome servers. The client boasts a modern, sleek UI, native [https://last.fm<nowiki>](</nowiki>[https://last.fm last.fm]) scrobbling, and wide range of support for operating systems, including: Windows, MacOS, Android, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [[Flathub]] release. 37c2e3602be3b171b730e22e265a82158d609de0 4654 4653 2026-05-22T20:58:16Z LilyWayLolz 354 Cleaned up formatting errors wikitext text/x-wiki [https://psysonic.de Psysonic] is a local music streaming client made for Navidrome servers. The client boasts a modern, sleek UI, native [https://last.fm<nowiki>](</nowiki> https://last.fm last.fm] scrobbling, and wide range of support for operating systems, including: Windows, MacOS, Android, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [[Flathub]] release. ce2b518347346429336e7eb3b60bcc05097231fb 4656 4654 2026-05-22T20:59:09Z LilyWayLolz 354 Cleaned up MORE formatting errors wikitext text/x-wiki [https://psysonic.de Psysonic] is a local music streaming client made for Navidrome servers. The client boasts a modern, sleek UI, native [https://last.fm<nowiki>](</nowiki> last.fm] scrobbling, and wide range of support for operating systems, including: Windows, MacOS, Android, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [[Flathub]] release. 5ab772b178813cfb500bf71bf91d5f0ab886781f 4659 4656 2026-05-22T21:02:27Z LilyWayLolz 354 Added more links wikitext text/x-wiki [https://psysonic.de Psysonic] is a local music streaming client made for [[Navidrome]] servers. The client boasts a modern, sleek UI, native [https://last.fm last.fm] [[scrobbling]], and wide range of support for operating systems, including: Windows, MacOS, Android, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [[Flathub]] release. 575e14a00cc4c23e697c1c1e5eb8a84d2cafe3d6 4667 4659 2026-05-22T21:18:06Z LilyWayLolz 354 Added software category wikitext text/x-wiki [https://psysonic.de Psysonic] is a local music streaming client made for [[Navidrome]] servers. The client boasts a modern, sleek UI, native [https://last.fm last.fm] [[scrobbling]], and wide range of support for operating systems, including: Windows, MacOS, Android, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [[Flathub]] release. [[Category:Software]] d066c277beb8e04deccdd959dd997461098de782 6 1122 4660 2026-05-22T21:08:08Z Uniolo 345 wikitext text/x-wiki The Vim Splash Screen 6a3cbd66a2af72e30dfd16b7ab1089bf9d7bc459 0 1123 4661 2026-05-22T21:08:45Z LilyWayLolz 354 Made the page and added the basics wikitext text/x-wiki Navidrome is a locally-hosted music streaming server that allows users to upload one's personal music files onto it in order to create a personal music library. This music library can be streamed through various clients to play one's locally-hosted music on other devices via a link pointing to the host server. 8cf0797fdaea4e571b398be5e094114d9870295d 4664 4661 2026-05-22T21:10:02Z LilyWayLolz 354 Added navidrome link wikitext text/x-wiki [https://navidrome.org Navidrome] is a locally-hosted music streaming server that allows users to upload one's personal music files onto it in order to create a personal music library. This music library can be streamed through various clients to play one's locally-hosted music on other devices via a link pointing to the host server. 832a4c059d497cde42e2b63417c03c07c4a8e2db 4669 4664 2026-05-22T21:19:38Z LilyWayLolz 354 Added software category wikitext text/x-wiki [https://navidrome.org Navidrome] is a locally-hosted music streaming server that allows users to upload one's personal music files onto it in order to create a personal music library. This music library can be streamed through various clients to play one's locally-hosted music on other devices via a link pointing to the host server. [[Category:Software]] 436779c5960fe8f9742f9ac693f7cbac18cdbd27 0 1032 4666 4223 2026-05-22T21:13:35Z Assembly 337 Added a feature section, with a short description of Sandboxed Google Play and Pin scrambling wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}}{{Needs Citations}} {{DistributionInfobox | architectures = ARM64 | caption = The GrapheneOS logo | defaultdesktops = Android User Interface | image = [[File:GrapheneOS-logo-black.png|GrapheneOS-logo-black]] | packagemanager = Android Package Manager (not acessible) | releasemodel = Fixed Releases | releasestatus = Currently Maintained | title = GrapheneOS | usagetype = Mobile | website = [https://grapheneos.org grapheneos.org] }} '''GrapheneOS''' (previously CopperheadOS<ref>[https://grapheneos.org/history/copperheados CopperheadOS | History], GrapheneOS, 2025-09-24 (Accessed: 2025-10-12)</ref>) is an [[Android]]-based [[OS|operating system]] focusing on privacy and security.<ref>[https://grapheneos.org/#about GrapheneOS: the private and secure mobile OS], GrapheneOS, 2025-09-24 (Accessed: 2025-10-12)</ref> It usually receives the fastest updates compared to other customized Android-based systems. == History == GrapheneOS was founded by Daniel Macay in late 2014, starting as a solo project incorporating his previous open source privacy/security work. The project initially created a port of [[OpenBSD]] [[malloc]] to Android's Bionic [[libc]] and a port of the PaX [[kernel]] [[patch]]es to the kernel of GrapheneOS's supported devices. It quickly expanded to a lot of privacy and security improvements, particularly low-level [[hardening]] on the [[compiler]] toolchain and Bionic. Code began landing on AOSP and upstream projects.<ref>[https://grapheneos.org/history/ History], GrapheneOS, 2025-09-24 (Accessed: 2025-10-12)</ref> == Features == A complete list of features can be found on the [https://grapheneos.org/features GrapheneOS website]. === Sandboxed Google Play === Unlike stock [[Android]], GrapheneOS does not ship with [[wikipedia:Google_Play_Services|Google Play Services]] preinstalled. Instead, GrapheneOS provides a compatibility layer which enables Google Play Services to run in the standard app sandbox. This means permissions such as reading contacts, accessing GPS location, or being able to run in the background can be changed in the phone's settings like for any other app, instead of Google Play Services being granted irrevocable special privileges. <ref name=":0">{{Cite|url=https://grapheneos.org/features|title=GrapheneOS Feature Overview|author=GrapheneOS Project|accessdate=2026-05-22}}</ref> === PIN scrambling === GrapheneOS adds a setting to enable shuffling of the numbers on the PIN entry screen.<ref name=":0" /> This makes it harder to figure out a device's pin through [[wikipedia:Shoulder_surfing_(computer_security)|shoulder surfing]]. === References === <references /> 6fc39cdc68a6babe565583f237021dee83e1a5b3 0 1121 4670 4667 2026-05-22T21:22:46Z LilyWayLolz 354 Added Navidrome clients category wikitext text/x-wiki [https://psysonic.de Psysonic] is a local music streaming client made for [[Navidrome]] servers. The client boasts a modern, sleek UI, native [https://last.fm last.fm] [[scrobbling]], and wide range of support for operating systems, including: Windows, MacOS, Android, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [[Flathub]] release. [[Category:Software]] [[Category:Navidrome Clients]] 46c17db1c24f2d9b171d40eae8ff7d59de5d5c53 14 1124 4671 2026-05-22T21:23:36Z LilyWayLolz 354 Created page with "List of clients for the locally-hosted music streaming service, Navidrome" wikitext text/x-wiki List of clients for the locally-hosted music streaming service, Navidrome 2358f2b0134f970330afdf02b2d0c20c21b55f68 0 1123 4672 4669 2026-05-22T21:25:52Z LilyWayLolz 354 Added clients link wikitext text/x-wiki [https://navidrome.org Navidrome] is a locally-hosted music streaming server that allows users to upload one's personal music files onto it in order to create a personal music library. This music library can be streamed through various [https://foss.wiki/Category:Navidrome_Clients clients] to play one's locally-hosted music on other devices via a link pointing to the host server. [[Category:Software]] ba3d0df37932c96279a3b0b9b3d952b18c2f1568 0 1125 4673 2026-05-22T21:27:31Z Deviaze 341 create page wikitext text/x-wiki The MIT License is a permissive software license that puts very few restrictions on software reuse and provides no warranties for users using the software. === Text === <syntaxhighlight lang="text"> Copyright (c) <year> <copyright holders> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. </syntaxhighlight> 696a7b0a1e46f08c0b2c034f4d79244a91be336a 4680 4673 2026-05-22T21:47:59Z Deviaze 341 add category software licenses wikitext text/x-wiki The MIT License is a permissive software license that puts very few restrictions on software reuse and provides no warranties for users using the software. === Text === <syntaxhighlight lang="text"> Copyright (c) <year> <copyright holders> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. </syntaxhighlight> [[Category:Software licenses]] e7b1020784e8705646cc7a8c85d5eb822d469f27 0 1126 4674 2026-05-22T21:29:10Z Deviaze 341 make page wikitext text/x-wiki A software license determines who can reuse, reproduce, modify, etc. software and what rights and warranties are waived or restricted by the owner. f74171e078c2171fc1067607e7e16e0e4b7846e8 4675 4674 2026-05-22T21:31:21Z Deviaze 341 add licenses wikitext text/x-wiki A software license determines who can reuse, reproduce, modify, etc. software and what rights and warranties are waived or restricted by the owner. === Free and open source licenses === * [[MIT License]] ===== Copyleft licenses ===== Copyleft licenses prevent developers from using a project's code in a proprietary project without disclosing the project's source code. 176deca2caf22c175030ab7c5ab9c261241cf3b1 4687 4675 2026-05-22T21:51:56Z Deviaze 341 add GPL license wikitext text/x-wiki A software license determines who can reuse, reproduce, modify, etc. software and what rights and warranties are waived or restricted by the owner. === Free and open source licenses === * [[MIT License]] ===== Copyleft licenses ===== Copyleft licenses prevent developers from using a project's code in a proprietary project without disclosing the project's source code. * [[GNU General Public License]] 5c4ec1e5cb0f6664f197fe4d55826d22352062f4 0 558 4676 4668 2026-05-22T21:32:41Z Deviaze 341 link to mit license wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.84.1 | languages = [[Rust]], originally written in [[OCaml]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust is a modern multi-paradigm programming language with a focus on performance, reliability, and productivity<ref>https://github.com/rust-lang/rust</ref>. Although originally designed as a systems-level language, Rust has found widespread adoption as a general purpose programming language thanks to its high degree of expressiveness, strict type safety and memory safety, its easy-to-use package manager Cargo and crates ecosystem, and its ability to achieve native performance with high level code. Rust was heavily inspired by functional programming languages in its emphasis on immutability and pattern matching, as well as by [[C++]] for its RAII (resource allocation is initialization) and other performance features. Rust is most often compared with and considered an alternative to C++. In 2025, Rust was officially accepted into the [[Linux|Linux kernel]]<ref>https://www.phoronix.com/news/Rust-To-Stay-Linux-Kernel</ref>, after a lengthy trial period (the Rust for Linux experiment) that started in December 2022, becoming the third language accepted in the kernel after [[C]] and [[assembly]]. [[Canonical]], the company behind Ubuntu and other FOSS, is replacing the GNU coreutils project, written in C, with uutils, a Rust rewrite<ref>https://archive.fosdem.org/2025/schedule/event/fosdem-2025-6196-rewriting-the-future-of-the-linux-essential-packages-in-rust-/</ref>. This has attracted criticism around its licensing changing from GNU GPL to [[MIT License|MIT]] and makes uutils more friendly to proprietary software<ref>https://github.com/uutils/coreutils/issues/834</ref>. === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Data Types === Rust has a number of primitive builtin types, denoted in lowercase, as well as complex objects from the standard library that behave like primitives in other languages. {| class="wikitable" |+Primitive integer types (signed/unsigned) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} Rust does not have a single string type; below is a non-comprehensive list of the most common ways to represent a string: {| class="wikitable" |+String types !Name !Stack or heap !Description |- |<code>&str</code> |Stack |A reference to a UTF-8 string slice, <code>str</code>only really exists as a reference type. These are immutable. |- |<code>&'static str</code> |Stack |The type of a string literal embedded into sourcecode. The <code>'static</code> lifetime means that the <code>&str</code> lasts forever. |- |<code>char</code> |Stack |Represents a single UTF-8 codepoint. |- |<code>String</code> |Heap |A full heap-allocated, possibly mutable UTF-8 string. |- |<code>Vec<u8></code> |Heap |A heap-allocated list of arbitrary bytes; it's not actually a string, but it's commonly used instead of a <code>String</code> when you want to represent data that isn't necessarily UTF-8 encoded. |- |<code>Cow</code> |Might be either |Stands for copy-on-write. |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. [[OO]]P allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref><ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref> Rust takes a different approach to OOP with its use of <code>struct</code>s, <code>trait</code>s, <code>enum</code>s, and <code>impl</code>s.<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, <code>struct</code>s in Rust can store multiple related values as fields. The difference is that fields must be referred via their given naming. <code>struct</code>s are more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> <syntaxhighlight lang="rust" lines> // Having the struct outside of main() makes it available everywhere in the file struct MyStruct { field1: bool, field2: i32, field3: String, } fn main() { let object = MyStruct { field1: true, field2: 64, field3: String::from("Use structs you must!"), }; } </syntaxhighlight> Functional properties may be given to <code>struct</code>s with <code>impl</code>s, which stands for ''implement''. Having methods (i.e. functions in <code>impl</code> with <code>self</code>, <code>&self</code> or <code>&mut self</code> as the first parameter) also allows for reproducibility, since they can access <code>struct</code> fields via <code>self</code>. <ref name=":0" /><ref name=":2" /> <syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height } } fn main() { let rubiks_cube = Cube { length: 3, width: 3, height: 3, }; println!("Cube's volume: {}", rubiks_cube.volume()); } </syntaxhighlight> The code declares a new struct with 3 values and an area finder function within the <code>impl Cube</code> scope. The <code>volume()</code> method may be used on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == 1d2aa251e4b669b52a4e06826219a8c94a490bdb 0 1120 4677 4665 2026-05-22T21:44:35Z Uniolo 345 Added usage tips, and information about Vim origins as per recommendation on DIscord. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. ==Usage tips== While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering ":wq!", you may have to press the escape key first to enter Normal mode, however. Vim behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found below {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |view |Starts Vim in read-only mode |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] <references /> f79871b1b5eee63f93cede0fa22e1c39a3d16e88 4679 4677 2026-05-22T21:47:05Z Uniolo 345 Moved citations out of 'Usage tips', does not seem I can collapse sections within a preview so lets hope this works. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. ==Usage tips== While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering ":wq!", you may have to press the escape key first to enter Normal mode, however. Vim behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found below {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |view |Starts Vim in read-only mode |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] <references /> 588ef9ee374a2624016c0f8d483407f56a330f38 4686 4679 2026-05-22T21:51:07Z Uniolo 345 Removed '<references />' so it will be automatically put at the bottom (and not in any section) wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. ==Usage tips== While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering ":wq!", you may have to press the escape key first to enter Normal mode, however. Vim behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found below {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |view |Starts Vim in read-only mode |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] 49e5a8680584a20e7f5f21fe1fca1630ae8d0034 4691 4686 2026-05-22T22:02:18Z Uniolo 345 Made ':wq!' use a code block, added note about being the same approach Busybox uses to the section about vim behaving differently depending on executable names. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. ==Usage tips== While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found below {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |view |Starts Vim in read-only mode |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] 3074827094a732b0b70e60c4121cb22ea59a2b99 4695 4691 2026-05-22T22:06:43Z Uniolo 345 Added Vim Script to the list of languages, and added note about it being configured in Vim Script. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. ==Usage tips== While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found below {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |view |Starts Vim in read-only mode |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] 358f9a6a63c30b57983d8c5870e56522dd867544 4699 4695 2026-05-22T22:12:27Z Uniolo 345 wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. ==Usage tips== While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] <references /> 2479557c8675a3d0022f8ab58ba3ce0bae17a2c0 4704 4699 2026-05-22T22:20:23Z Sartaj 358 added text before editor because vim is a test editor wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. ==Usage tips== While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] <references /> 42c40e6e9509cb70d8ae10e05854e2ed30df4ebd 4705 4704 2026-05-22T22:29:20Z Sartaj 358 /* Usage tips */ added tip to open a file. that is first step wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. ==Usage tips== <code> Vim ''path/to/filename'' </code> is used to open a new or existing file for editing. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] <references /> 65a378ebe8bbdc38224d667de2abcc086095b0e3 4712 4705 2026-05-22T23:27:05Z Uniolo 345 Added blurb about Neovim wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim|NeoVim]] instead for a more modern editor and backwards compatible editor. ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use the <code>vimtutor</code> command. <code>Vim ''path/to/filename'' </code> is used to open a new or existing file for editing, though you can also open a file from within Vim. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] <references /> db7166ededf6687c8e6be6f86c0372d2a1a63eb8 0 1127 4678 2026-05-22T21:46:04Z Noah-or13 350 I wrote a brief enough but informational bit about librewolf wikitext text/x-wiki LibreWolf is an open-source fork of the browser Mozilla Firefox focused on privacy and security. Their website is https://librewolf.net. It was originally released for Linux in March 2020 with a community-maintained version being released for Microsoft Windows in February 2021 and a Mac port following a few months later in April 2021. Features:LibreWolf's main purpose is privacy, therefore the features it adds are all mainly privacy-based. Some features LibreWolf adds include uBlock Origin by default, disabled telemetry, DuckDuckGo as the default search engine, cookies and history gets wiped on closing of browser by default, and Firefox Sync being disabled by default. License: LibreWolf's source code is currently licensed under MPL 2.0 and their website is licensed under GNU AGPL 3.0 Source code location: The LibreWolf source code is currently kept at https://codeberg.org/librewolf and https://gitlab.com/librewolf-community Current Linux distro support: Gentoo, Arch, Debian based, Fedora, openSUSE and available to any other distro via a [[Flatpak]] and an AppImage Windows support: You can get LibreWolf on Windows via the Microsoft Store, a portable release as just a .exe or with [[Package Manager|Package Managers]] like Scoop, Chocolatey and Winget [[Category:Software]] 29f3095a47cff44574de4a0a5fa78992b53ffea6 4684 4678 2026-05-22T21:49:45Z Noah-or13 350 added librewolf icon wikitext text/x-wiki [[File:LibreWolf Icon.png|thumb]] LibreWolf is an open-source fork of the browser Mozilla Firefox focused on privacy and security. Their website is https://librewolf.net. It was originally released for Linux in March 2020 with a community-maintained version being released for Microsoft Windows in February 2021 and a Mac port following a few months later in April 2021. Features:LibreWolf's main purpose is privacy, therefore the features it adds are all mainly privacy-based. Some features LibreWolf adds include uBlock Origin by default, disabled telemetry, DuckDuckGo as the default search engine, cookies and history gets wiped on closing of browser by default, and Firefox Sync being disabled by default. License: LibreWolf's source code is currently licensed under MPL 2.0 and their website is licensed under GNU AGPL 3.0 Source code location: The LibreWolf source code is currently kept at https://codeberg.org/librewolf and https://gitlab.com/librewolf-community Current Linux distro support: Gentoo, Arch, Debian based, Fedora, openSUSE and available to any other distro via a [[Flatpak]] and an AppImage Windows support: You can get LibreWolf on Windows via the Microsoft Store, a portable release as just a .exe or with [[Package Manager|Package Managers]] like Scoop, Chocolatey and Winget [[Category:Software]] d5564733bf2c667e0b89310499e1f84ad0b15af6 0 1128 4681 2026-05-22T21:48:19Z Operz 344 Create OpenSolaris page; describe brief history and features of distribution. wikitext text/x-wiki [[Category:Misc Operating Systems]] {{DistributionInfobox | title = OpenSolaris | image = [[File:OpenSolaris Logo (2).svg|100px|center]] | caption = Logo of OpenSolaris | releasestatus = Discontinued | releasemodel = Rolling Release via Package Manager with Binary ISO & Repository Snapshots | packagemanager = IPS <ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/IMGPACKAGESYS/html/index.html|title=Introduction to IPS - OpenSolaris 2009.06 Image Packaging System Guide|author=Sun Microsystems, Inc.|date=2009|accessdate=2026-05-22}}</ref> | defaultdesktops = GNOME 2 | usagetype = Desktop, Server | architectures = x86, x86_64, SPARC | website = [https://web.archive.org/web/20090726021430/http://opensolaris.com/ OpenSolaris.com (archived at the Wayback Machine)] and [https://web.archive.org/web/20090709062850/http://opensolaris.org/os/ OpenSolaris.org (archived at the Wayback Machine)] }} OpenSolaris is a discontinued [[Unix-Like|UNIX-like]]{{Cite|url=https://man.freebsd.org/cgi/man.cgi?query=standards&apropos=0&sektion=5&manpath=OpenSolaris+2010.03&format=html|title=standards(5), Standards, Environments, and Macros, OpenSolaris 2010.03 Manual|author=Sun Microsystems, Inc.|year=2004|accessdate=2026-05-22}}</ref> [[Operating System|operating system]] derived from [[Sun Microsystems]] (now Oracle) [[Oracle Solaris|Solaris]] whose development began in the mid-2000s when Sun began to [[FLOSS|open-source]] more of Solaris, including its kernel and userland components. After the Oracle acquisition of Sun and the shutdown of OpenSolaris and other FOSS projects at Java.net, the kernel and userland which comprised most of OpenSolaris as well as much of the documentation with it was archived and forked into [[Illumos]], with [[OpenIndiana]] being the flagship distribution. Ian Murdock, the founder of [[Debian]], also worked at Sun on Project Indiana, the codename for the "official" OpenSolaris binary distribution.<ref>{{Cite|url=https://ianmurdock.debian.net/wp-content/uploads/imurdock-resume-15.9.pdf|title=Ian Murdock Resume|author=Ian Murdock|year=2015|accessdate=2026-05-22}}</ref> == Notable Features == === ZFS === ZFS is the filesystem developed by Sun which is used in OpenSolaris. It provides features such as snapshotting, checksums, self-healing data, RAID-Z, advanced NFSv4-style ACLs, and more.{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/ZFSADMIN/html/zfsover-2.html|title=What Is ZFS? - Solaris ZFS Administration Guide|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}} When OpenSolaris's code was released, the ZFS filesystem code was forked into OpenZFS which is still available on platforms like [[FreeBSD]] and some Linux distributions.{{Cite|url=https://openzfs.github.io/openzfs-docs/Getting%20Started/index.html|title=Getting Started - OpenZFS Documentation|author=OpenZFS|year=2025|accessdate=2026-05-22}} === SMF === System Management Facility (SMF) is the service supervisor and init system used in OpenSolaris and its derivatives. It handles automatic restarting of services, dependency resolution, enabling and idsabling of services, and more.{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADV1/html/dzhgy.html|title=Introduction to SMF - System Administration Guide: Basic Administration|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}} === Solaris Containers and Zones === Zones are very similar to FreeBSD jails. They are containers that allow the use of more than one OS instance to run under the same kernel.{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/zones.intro-2.html|title=Zones Overview - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}}} The BrandZ framework created what is known as "LX-branded" zones, which allowed Linux distributions and binaries to run under the Solaris kernel in a zone unmodified, via syscall translation. This allowed for the usage of Linux distributions such as CentOS 3.x to run; however, this only supports user-level applications, and cannot be used to emulate kernel modules or filesystems.{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/gentextid-17437.html|title=About the lx Brand - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}} This feature is still present today in certain Illumos distributions such as OmniOS and SmartOS.{{Cite|url=https://omnios.org/info/lxzones.html|title=LX Branded Zones|author=About OmniOS Community Edition Association|year=2024|accessdate=2026-05-22}} === Sun xVM === Sun xVM was a fork of the Xen type-1 hypervisor specifically catered towards OpenSolaris being the dom0 OS used for management of the domU guest OSes. Sun xVM allowed multiple domU kernels to run on the same machine, and supported (Open)Solaris, Linux, FreeBSD, and even Windows.{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/geyyr.html|title=Supported Configurations - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}} === Image Packaging System === The Image Packaging System (IPS) is the primary package manager used by OpenSolaris for distribution of application updates and installation of new programs.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/IMGPACKAGESYS/html/index.html|title=Introduction to IPS - OpenSolaris 2009.06 Image Packaging System Guide|author=Sun Microsystems, Inc.|date=2009|accessdate=2026-05-22}}</ref> == References == <references /> == External links == [http://sunsite.icm.edu.pl/pub/solaris/opensolaris/ OpenSolaris formal release ISOs (both base and repository snapshots) at SunSite] [https://docs.openindiana.org/books/about/ OpenSolaris books at OpenIndiana's documentation archive] 758b557fe5b7add609af3530fd8639abcf31ce9b 4685 4681 2026-05-22T21:50:31Z Operz 344 fix citations oops wikitext text/x-wiki [[Category:Misc Operating Systems]] {{DistributionInfobox | title = OpenSolaris | image = [[File:OpenSolaris Logo (2).svg|100px|center]] | caption = Logo of OpenSolaris | releasestatus = Discontinued | releasemodel = Rolling Release via Package Manager with Binary ISO & Repository Snapshots | packagemanager = IPS <ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/IMGPACKAGESYS/html/index.html|title=Introduction to IPS - OpenSolaris 2009.06 Image Packaging System Guide|author=Sun Microsystems, Inc.|date=2009|accessdate=2026-05-22}}</ref> | defaultdesktops = GNOME 2 | usagetype = Desktop, Server | architectures = x86, x86_64, SPARC | website = [https://web.archive.org/web/20090726021430/http://opensolaris.com/ OpenSolaris.com (archived at the Wayback Machine)] and [https://web.archive.org/web/20090709062850/http://opensolaris.org/os/ OpenSolaris.org (archived at the Wayback Machine)] }} OpenSolaris is a discontinued [[Unix-Like|UNIX-like]]<ref>{{Cite|url=https://man.freebsd.org/cgi/man.cgi?query=standards&apropos=0&sektion=5&manpath=OpenSolaris+2010.03&format=html|title=standards(5), Standards, Environments, and Macros, OpenSolaris 2010.03 Manual|author=Sun Microsystems, Inc.|year=2004|accessdate=2026-05-22}}</ref> [[Operating System|operating system]] derived from [[Sun Microsystems]] (now Oracle) [[Oracle Solaris|Solaris]] whose development began in the mid-2000s when Sun began to [[FLOSS|open-source]] more of Solaris, including its kernel and userland components. After the Oracle acquisition of Sun and the shutdown of OpenSolaris and other FOSS projects at Java.net, the kernel and userland which comprised most of OpenSolaris as well as much of the documentation with it was archived and forked into [[Illumos]], with [[OpenIndiana]] being the flagship distribution. Ian Murdock, the founder of [[Debian]], also worked at Sun on Project Indiana, the codename for the "official" OpenSolaris binary distribution.<ref>{{Cite|url=https://ianmurdock.debian.net/wp-content/uploads/imurdock-resume-15.9.pdf|title=Ian Murdock Resume|author=Ian Murdock|year=2015|accessdate=2026-05-22}}</ref> == Notable Features == === ZFS === ZFS is the filesystem developed by Sun which is used in OpenSolaris. It provides features such as snapshotting, checksums, self-healing data, RAID-Z, advanced NFSv4-style ACLs, and more.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/ZFSADMIN/html/zfsover-2.html|title=What Is ZFS? - Solaris ZFS Administration Guide|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> When OpenSolaris's code was released, the ZFS filesystem code was forked into OpenZFS which is still available on platforms like [[FreeBSD]] and some Linux distributions.<ref>{{Cite|url=https://openzfs.github.io/openzfs-docs/Getting%20Started/index.html|title=Getting Started - OpenZFS Documentation|author=OpenZFS|year=2025|accessdate=2026-05-22}}</ref> === SMF === System Management Facility (SMF) is the service supervisor and init system used in OpenSolaris and its derivatives. It handles automatic restarting of services, dependency resolution, enabling and idsabling of services, and more.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADV1/html/dzhgy.html|title=Introduction to SMF - System Administration Guide: Basic Administration|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> === Solaris Containers and Zones === Zones are very similar to FreeBSD jails. They are containers that allow the use of more than one OS instance to run under the same kernel.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/zones.intro-2.html|title=Zones Overview - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> The BrandZ framework created what is known as "LX-branded" zones, which allowed Linux distributions and binaries to run under the Solaris kernel in a zone unmodified, via syscall translation. This allowed for the usage of Linux distributions such as CentOS 3.x to run; however, this only supports user-level applications, and cannot be used to emulate kernel modules or filesystems.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/gentextid-17437.html|title=About the lx Brand - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> This feature is still present today in certain Illumos distributions such as OmniOS and SmartOS.<ref>{{Cite|url=https://omnios.org/info/lxzones.html|title=LX Branded Zones|author=About OmniOS Community Edition Association|year=2024|accessdate=2026-05-22}}</ref> === Sun xVM === Sun xVM was a fork of the Xen type-1 hypervisor specifically catered towards OpenSolaris being the dom0 OS used for management of the domU guest OSes. Sun xVM allowed multiple domU kernels to run on the same machine, and supported (Open)Solaris, Linux, FreeBSD, and even Windows.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/geyyr.html|title=Supported Configurations - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> === Image Packaging System === The Image Packaging System (IPS) is the primary package manager used by OpenSolaris for distribution of application updates and installation of new programs.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/IMGPACKAGESYS/html/index.html|title=Introduction to IPS - OpenSolaris 2009.06 Image Packaging System Guide|author=Sun Microsystems, Inc.|date=2009|accessdate=2026-05-22}}</ref> == References == <references /> == External links == [http://sunsite.icm.edu.pl/pub/solaris/opensolaris/ OpenSolaris formal release ISOs (both base and repository snapshots) at SunSite] [https://docs.openindiana.org/books/about/ OpenSolaris books at OpenIndiana's documentation archive] 5b541c6e2b8aef77d2f710c938508b0286e01ab8 4690 4685 2026-05-22T21:53:42Z Operz 344 fix space as well wikitext text/x-wiki [[Category:Misc Operating Systems]] {{DistributionInfobox | title = OpenSolaris | image = [[File:OpenSolaris Logo (2).svg|100px|center]] | caption = Logo of OpenSolaris | releasestatus = Discontinued | releasemodel = Rolling Release via Package Manager with Binary ISO & Repository Snapshots | packagemanager = IPS <ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/IMGPACKAGESYS/html/index.html|title=Introduction to IPS - OpenSolaris 2009.06 Image Packaging System Guide|author=Sun Microsystems, Inc.|date=2009|accessdate=2026-05-22}}</ref> | defaultdesktops = GNOME 2 | usagetype = Desktop, Server | architectures = x86, x86_64, SPARC | website = [https://web.archive.org/web/20090726021430/http://opensolaris.com/ OpenSolaris.com (archived at the Wayback Machine)] and [https://web.archive.org/web/20090709062850/http://opensolaris.org/os/ OpenSolaris.org (archived at the Wayback Machine)] }} OpenSolaris is a discontinued [[Unix-Like|UNIX-like]]<ref>{{Cite|url=https://man.freebsd.org/cgi/man.cgi?query=standards&apropos=0&sektion=5&manpath=OpenSolaris+2010.03&format=html|title=standards(5), Standards, Environments, and Macros, OpenSolaris 2010.03 Manual|author=Sun Microsystems, Inc.|year=2004|accessdate=2026-05-22}}</ref> [[Operating System|operating system]] derived from [[Sun Microsystems]] (now Oracle) [[Oracle Solaris|Solaris]] whose development began in the mid-2000s when Sun began to [[FLOSS|open-source]] more of Solaris, including its kernel and userland components. After the Oracle acquisition of Sun and the shutdown of OpenSolaris and other FOSS projects at Java.net, the kernel and userland which comprised most of OpenSolaris as well as much of the documentation with it was archived and forked into [[Illumos]], with [[OpenIndiana]] being the flagship distribution. Ian Murdock, the founder of [[Debian]], also worked at Sun on Project Indiana, the codename for the "official" OpenSolaris binary distribution.<ref>{{Cite|url=https://ianmurdock.debian.net/wp-content/uploads/imurdock-resume-15.9.pdf|title=Ian Murdock Resume|author=Ian Murdock|year=2015|accessdate=2026-05-22}}</ref> == Notable Features == === ZFS === ZFS is the filesystem developed by Sun which is used in OpenSolaris. It provides features such as snapshotting, checksums, self-healing data, RAID-Z, advanced NFSv4-style ACLs, and more.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/ZFSADMIN/html/zfsover-2.html|title=What Is ZFS? - Solaris ZFS Administration Guide|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> When OpenSolaris's code was released, the ZFS filesystem code was forked into OpenZFS which is still available on platforms like [[FreeBSD]] and some Linux distributions.<ref>{{Cite|url=https://openzfs.github.io/openzfs-docs/Getting%20Started/index.html|title=Getting Started - OpenZFS Documentation|author=OpenZFS|year=2025|accessdate=2026-05-22}}</ref> === SMF === System Management Facility (SMF) is the service supervisor and init system used in OpenSolaris and its derivatives. It handles automatic restarting of services, dependency resolution, enabling and idsabling of services, and more.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADV1/html/dzhgy.html|title=Introduction to SMF - System Administration Guide: Basic Administration|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> === Solaris Containers and Zones === Zones are very similar to FreeBSD jails. They are containers that allow the use of more than one OS instance to run under the same kernel.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/zones.intro-2.html|title=Zones Overview - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> The BrandZ framework created what is known as "LX-branded" zones, which allowed Linux distributions and binaries to run under the Solaris kernel in a zone unmodified, via syscall translation. This allowed for the usage of Linux distributions such as CentOS 3.x to run; however, this only supports user-level applications, and cannot be used to emulate kernel modules or filesystems.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/gentextid-17437.html|title=About the lx Brand - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> This feature is still present today in certain Illumos distributions such as OmniOS and SmartOS.<ref>{{Cite|url=https://omnios.org/info/lxzones.html|title=LX Branded Zones|author=About OmniOS Community Edition Association|year=2024|accessdate=2026-05-22}}</ref> === Sun xVM === Sun xVM was a fork of the Xen type-1 hypervisor specifically catered towards OpenSolaris being the dom0 OS used for management of the domU guest OSes. Sun xVM allowed multiple domU kernels to run on the same machine, and supported (Open)Solaris, Linux, FreeBSD, and even Windows.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/geyyr.html|title=Supported Configurations - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> === Image Packaging System === The Image Packaging System (IPS) is the primary package manager used by OpenSolaris for distribution of application updates and installation of new programs.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/IMGPACKAGESYS/html/index.html|title=Introduction to IPS - OpenSolaris 2009.06 Image Packaging System Guide|author=Sun Microsystems, Inc.|date=2009|accessdate=2026-05-22}}</ref> == References == <references /> == External links == [http://sunsite.icm.edu.pl/pub/solaris/opensolaris/ OpenSolaris formal release ISOs (both base and repository snapshots) at SunSite] [https://docs.openindiana.org/books/about/ OpenSolaris books at OpenIndiana's documentation archive] d45bcec01ce02d1b27327d0f3aa7d30360be5842 0 853 4682 3733 2026-05-22T21:48:40Z Deviaze 341 add category Software licenses wikitext text/x-wiki {{Work_In_Progress}} The '''GNU General Public License''' (short '''GNU GPL''' or '''GPL''') is a collection of copyleft license published by the Free Software Foundation (FSF) and written by Richard Stallman<ref>https://archive.ph/20120907170559/http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html{{Dead Link|2025-08-14|429}}</ref>. This License is also part of the [[GNU]] project === Copyleft === A copyleft license requires that any modifications or extensions to a program licensed under a copyleft license must also be licensed under the same (or a compatible) license. === "or-later" clause === All GNU GPL licenses may contain an optional clause, an “or-later” clause (sometimes referred to as a “lifeboat clause”). This clause allows all later versions to be used. Programs without this clause are referred to as “only.” for example * GNU GPLv2-or-later can also be licensed under GNU GPLv3-or-later without any problem * GNU GPLv2-only can only be licensed under the GNU GPLv2 The same applies to the GNU AGPL and LGPL licenses. The FSF recommends using the “or-later” clause, as it is compatible with future versions of the GNU GPL, since GNU GPLv2 and v3 are not compatible and therefore a program licensed only under GNU GPLv2 cannot be mixed with a GNU GPLv3 program. == Licenses == There are three versions of the GNU GPL, with version 3 being the most recent version for all of them. # GNU General Public License (GPL) – The standard strong copyleft license used for most programs. # GNU Lesser General Public License (LGPL) – A weak copyleft license mainly used for libraries. # GNU Affero General Public License (AGPL) – Similar to the GPL, but also covers use over a network. === GNU General Public License (GPL) === This license is used for regular programs such as the Linux kernel, which uses GNU GPLv2 only. The latest version is the GNU General Public License Version 3 (GNU GPLv3), which was released in June 2007<ref>[https://www.gnu.org/licenses/gpl-3.0.en.html#license-text The GNU General Public License v3.0], Free Software Foundation, 2007-08-14 (Accessed: 2025-08-14)</ref> and can be found [https://www.gnu.org/licenses/gpl-3.0.en.html#license-text here]. If part of a program (e.g., a library) uses this license, the entire program must be licensed under the GNU GPL. If this is not desired, the GNU LGPL or another license should be used. === GNU Lesser General Public License (LGPL) === The GNU LGPL (formerly known as the Library General Public License) was created at the same time as the GNU GPLv2 and was also published in June 2007, but the first version was called GNU LGPLv2 to match the GNU GPLv2. This license was created because the GNU GPL was too restrictive, especially for libraries. If a program uses a library licensed under the GNU LGPL, only the modification of that library must be published. This allows a library to be used in [[Proprietary software]] The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/lgpl-3.0.html here] === GNU Affero General Public License (AGPL) === The GNU AGPL was created to close a loophole when modified software licensed under the GNU GPL was run on a server the source code dont need to be published because of that the AGPL was created to fix this loophole The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/agpl-3.0.html#license-text here] <references /> [[Category:Software licenses]] 91c266697a0be75ce0f41da655cda80e6648cf69 6 1129 4683 2026-05-22T21:49:23Z Noah-or13 350 wikitext text/x-wiki Icon for the LibreWolf browser aa18fc0479505a98d35077cb62198206a7ac3f61 0 178 4688 4278 2026-05-22T21:53:36Z Scottc96 18 Scottc96 moved page [[Linux]] to [[Linux kernel]] without leaving a redirect: name update wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 6.10-rc2, 2024-06-02 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[Category:Terminology]] [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and deallocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under the terms of the [[GNU General Public License]] version 2 (GPLv2), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] *[[UNIX|Unix]] * [[FOSS|Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> 10d7a45f6cdb4a69ee326a1a8fb8e2b2ad9f0223 1 194 4689 446 2026-05-22T21:53:37Z Scottc96 18 Scottc96 moved page [[Talk:Linux]] to [[Talk:Linux kernel]] without leaving a redirect: name update wikitext text/x-wiki == do not put stuff like (infobox potential) == if you must put it in a comment or somewhere hidden away from the user [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 18:37, 4 June 2024 (UTC) cc92b325670f1733eda8a24a0ff48119275f03f8 0 1130 4692 2026-05-22T22:02:36Z Scottc96 18 Redirected page to [[Linux distributions]] wikitext text/x-wiki #REDIRECT [[Linux distributions]] 4c6e9200f20ec19d49deadbae5553ce74ead780e 4693 4692 2026-05-22T22:03:03Z Scottc96 18 Changed redirect target from [[Linux distributions]] to [[Linux Distributions]] wikitext text/x-wiki #REDIRECT [[Linux Distributions]] f6721c832bacd7daf16c3910dd1b30b95255d241 0 1131 4694 2026-05-22T22:04:40Z Scottc96 18 Redirected page to [[Linux Distributions]] wikitext text/x-wiki #REDIRECT [[Linux Distributions]] f6721c832bacd7daf16c3910dd1b30b95255d241 0 177 4696 4404 2026-05-22T22:11:54Z Scottc96 18 Scottc96 moved page [[FLOSS]] to [[Free and Open Source Software]]: name update wikitext text/x-wiki [[Category:Terminology]] '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word libre, meaning "free") and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, distribute and sell the software, modified or not, to everyone. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. The most accepted definition of Open Source is maintained by The Open Source Initiative, and is called "Open Source Definition"(OSD). The OSD was originally derived from the Debian Free Software Guidelines (DFSG)<ref>[https://opensource.org/osd The Open Source Definition], Open Source Initiative, 2007-03-22 (Accessed: 2026-01-18)</ref>. The Free Software Foundation maintains the accepted definition of Free Software<ref>[https://www.gnu.org/philosophy/free-sw.html What is Free Software?], GNU Project, 2025-12-28 (Accessed: 2026-01-18)</ref>. Proprietary, or nonfree software, is in contrast under restrictive licensing that goes against the user rights outlined in FOSS definitions, such as disallowing redistribution, sale, modification, or usage of the [[Source Code|source]] or [[Binary|binaries]] by a specific group, or requiring payment of money to exercise the rights mentioned. This includes source available software if it is subject to such restrictions, such as Unreal Engine, which requires payment of royalties for the distribution of certain binaries if the source includes Unreal Engine code<ref><nowiki>https://www.unrealengine.com/en-US/eula/unreal</nowiki></ref>. === Notes === ----FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == 1485816a854146db5228fd80c6ac049566042e05 0 1132 4697 2026-05-22T22:11:54Z Scottc96 18 Scottc96 moved page [[FLOSS]] to [[Free and Open Source Software]]: name update wikitext text/x-wiki #REDIRECT [[Free and Open Source Software]] 8c20e7b9c8c371f3a278c90300eecd07d73ddffe 0 8 4698 4355 2026-05-22T22:11:57Z Deviaze 341 /* Advanced Terms */ move wayland and x11 inside Compositors bullet wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] ** [[Wayland]] ** [[X11]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] ** [[Cybersecurity]] ** [[DDoS]] ** [[ARPANET]] ** [[Ransomware]] ** [[Penetration testing|Penetration Testing]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 7f5fe35bf3252982d73824ad24b7478cbc1987e2 0 331 4700 2168 2026-05-22T22:12:41Z Scottc96 18 Changed redirect target from [[FLOSS]] to [[Free and Open Source Software]] wikitext text/x-wiki #REDIRECT [[Free and Open Source Software]] 8c20e7b9c8c371f3a278c90300eecd07d73ddffe 0 247 4701 3419 2026-05-22T22:15:17Z LeahTheSlug 356 Added apt commands wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight> # apt upgrade </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). Examples:<syntaxhighlight> # apt install meow # apt install meow- pipes+ </syntaxhighlight> ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight> # apt remove pipes </syntaxhighlight> ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight> $ apt search minecraft </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight> # apt autoremove </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == <references><ref name=":0" /></references> 7c13fb2384b9743f83b6aceae55cd3e263ed7a16 4702 4701 2026-05-22T22:18:01Z LeahTheSlug 356 wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight> # apt upgrade </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). Examples:<syntaxhighlight> # apt install meow # apt install meow- pipes+ </syntaxhighlight> ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight> # apt remove pipes </syntaxhighlight> ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight> $ apt search minecraft </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight> # apt autoremove </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == <references><ref name=":0" /></references> 3424068148c8a356f8544260258198555db4f4a2 0 1040 4703 4242 2026-05-22T22:19:25Z Brochard 351 Add DistributionInfobox wikitext text/x-wiki {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = None | defaultdesktops = [[XFCE]] | usagetype = Desktop | architectures = x86_64 | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] Qubes OS is a free and open-source, security-oriented operating system for single-user desktop computing. Qubes OS leverages [[Xen]]-based virtualization to allow for the creation and management of isolated compartments called qubes. e3d2810ded4f0f80df75f99af0377a7ae99f323f 6 1133 4706 2026-05-22T22:29:29Z MysteryBirb 353 The logo of the Wayland compositor named MangoWM wikitext text/x-wiki == Summary == The logo of the Wayland compositor named MangoWM == Licensing == {{GPL}} 4d7df9753a472ebd5cf58cffec7b74b68024a845 0 1134 4707 2026-05-22T22:30:14Z Aristocat43 334 initial article, need to upload their icon as an image. wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = | caption = | title = Fluxer | releasestatus = Maintained | lastrelease = 0.0.8 | languages = [[Electron]] | developers = Hampus Kraft and Contributors | website = https://fluxer.app }} Fluxer is a free, open-source instant messaging and VoIP platform designed as a privacy-focused alternative to Discord. 03e07493f447470cca17fdc8663bcf8ab35b4ed5 4709 4707 2026-05-22T22:39:06Z Aristocat43 334 wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxer-symbol-color.svg|150px]] | caption = | title = Fluxer | releasestatus = Maintained | lastrelease = 0.0.8 | languages = Electron | developers = Hampus Kraft and Contributors | website = https://fluxer.app }} Fluxer is a free, open-source instant messaging and VoIP platform designed as a privacy-focused alternative to Discord. ==Overview== Fluxer is available in Flathub format as well as other official formats including AppImage, tar.gz, RPM, .deb, and more. Fluxer also allows for custom clients and has plans to incorporate federation & self-hosting capabilities in the future. de68eefe7c27532dead33ad65b2dfa49cc05d486 6 1135 4708 2026-05-22T22:32:00Z Aristocat43 334 Official color logo made available by their Press page. wikitext text/x-wiki == Summary == Official color logo made available by their Press page. == Licensing == {{Unknown_copyright}} 176f10a5092cc177cc05db7b54669feb0d8a993b 0 198 4710 4662 2026-05-22T22:40:16Z Deviaze 341 improve lede and add todo for adding top sentence as banner wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Atomic]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == fb71b1d06b29b48ce09c1a96f3deca72153fd9bc 3000 1136 4711 2026-05-22T23:11:59Z Deviaze 341 Start guide for Switching to Linux wikitext text/x-wiki Welcome to the penguin side! Switching to Linux feels scary at first, but you'll realize how much better things are with a faster system that's free and customizable. === Why switch? === * Windows is slow * Windows is spyware * Windows keeps breaking * Linux is faster * You can move your taskbar wherever you want or have 10 taskbars * Easier to find/install programs than on Windows === Choices === Linux is all about choices. Before you start, you need to pick what your Linux [[Desktop Environments|looks like]] and is [[Linux Distributions|under the hood]]. === Picking a Linux === There are (too) many flavors of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]]. If you don't like the Linux you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a GUI === When you install a Linux, the installer asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on touchpad gestures consider [[GNOME]]. 4853f7a483b2fc587faed64f890dbb25999c4b6c 0 826 4713 4643 2026-05-22T23:30:49Z Uniolo 345 Broke up text into multiple lines wikitext text/x-wiki {{Needs Citations}} {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Helix editor.svg|thumb|The logo for Helix]] |caption=Helix Editor |title=Helix |releasestatus=Maintained |lastrelease=25.07.1, Jul 18, 2025 |firstrelease=0.0.2, May 12, 2021 |languages=[[Rust]] |developers=[https://mxxn.io/ Blaž Hrastnik] |website=[https://helix-editor.com/ helix-editor.com] }} [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]]{{Citation needed}} and [[Kakoune]]<ref name=":0">[https://helix-editor.com/ Helix website] (accessed 2026-05-22)</ref>. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. Helix bundles and enables many features out of the box and does not yet have a plugin system, although that is currently being worked on<ref name=":0" />. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. Many users decide to fork Helix in order to add functionality that isn't included out of the box{{Citation needed}}. [[Category:Software]] <references /> 882962f9a3ab4444e4c1d95936b6bf76f310a244 4718 4713 2026-05-22T23:52:50Z Uniolo 345 Added "Usage tips" (and I think some other info but that may have been from last edit? wikitext text/x-wiki {{Needs Citations}} {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Helix editor.svg|thumb|The logo for Helix]] |caption=Helix Editor |title=Helix |releasestatus=Maintained |lastrelease=25.07.1, Jul 18, 2025 |firstrelease=0.0.2, May 12, 2021 |languages=[[Rust]] |developers=[https://mxxn.io/ Blaž Hrastnik] |website=[https://helix-editor.com/ helix-editor.com] }} [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]]{{Citation needed}} and [[Kakoune]]<ref name=":0">[https://helix-editor.com/ Helix website] (accessed 2026-05-22)</ref>. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. Helix bundles and enables many features out of the box and does not yet have a plugin system, although that is currently being worked on<ref name=":0" />. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. Due to its lack of plugin support, many users decide to fork Helix in order to add functionality that isn't included out of the box{{Citation needed}}. Helix is configured through [[TOML]]. ==Usage tips== While many of the same keybindings and concepts as [[Vi]] and [[Vim]] apply to Helix, many of the keybindings and concepts are different. The recommended way to learn Helix is by using the <code>:tutor</code> command whilst inside Helix, to do this, run <code>Helix</code> and type <code>:tutor</code>, then hit enter and follow the instructions. In some [[Linux Distributions|distros]], the executable is named <code>helix</code> (like on ArchLinux<ref>{{Cite|url=https://archlinux.org/packages/extra/x86_64/helix/|title="Helix" package on ArchLinux|author=Orhun Parmaksız|year=2025-07-18|accessdate=2026-05-22}}</ref>) while on others it is named <code>hx</code> (like on Alpine Linux<ref>{{Cite|url=https://pkgs.alpinelinux.org/contents?name=helix&repo=community&branch=edge&arch=x86_64|title="Helix" package on the Alpine Linux community repository|author=Jakub Jirutka|year=2026-05-04|accessdate=2026-05-22}}</ref>). This may cause issues if you develop muscle memory for the names of one of these commands, to get around this, you can create a symlink under your chosen name. [[Category:Software]] <references /> 914c01b7db0798cb74b24f22c8be39a377df8795 0 355 4714 3620 2026-05-22T23:35:58Z MarkH 357 Add infobox wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |title=GNU C Library |releasestatus=Maintained |lastrelease=2.43, 2026-01-23<ref>[https://inbox.sourceware.org/libc-announce/13932477.uLZWGnKmhe@pinacolada/T/ The GNU C Library version 2.43 is now available]</ref> |firstrelease=0.1, 1991-10-08<ref>[https://sourceware.org/glibc/wiki/Glibc%20Timeline Glibc Timeline]</ref> |languages=[[C]], [[Assembly]] |developers=The GNU Toolchain Authors |website=[https://www.gnu.org/software/libc/ www.gnu.org/software/libc] }} The '''GNU C Library''', commonly known as '''glibc''', is the GNU Project implementation of the C standard library. It provides a wrapper around the system calls of the Linux kernel and other kernels for application use. Despite its name, it now also directly supports C++ (and, indirectly, other programming languages). It was started in the 1980s by the Free Software Foundation (FSF) for the GNU operating system. ==References== <references /> [[Category:Software]] 0b6f199d7baeefb9633b755f5b66251ad03088a4 2 1137 4715 2026-05-22T23:40:25Z MarkH 357 create user page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 784 4716 3696 2026-05-22T23:46:58Z Matthias von Schwarzwald 361 Many typos wikitext text/x-wiki {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = GNOME | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }} Zorin OS is a Ubuntu-based Linux distribution made for newcomers to Linux, with a modified version of the Gnome GUI and XFCE 4 that is familiar to Windows users. It also has a paid model that comes with more desktop options and free software. it was first released on the first of July, 2009, under the name Zorin OS 1.0 f4b3b2c9f3d53148ee50703ae34c8bbf2e890f06 4717 4716 2026-05-22T23:47:34Z Matthias von Schwarzwald 361 Another typo wikitext text/x-wiki {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = GNOME | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }} Zorin OS is a Ubuntu-based Linux distribution made for newcomers to Linux, with a modified version of the Gnome GUI and XFCE 4 that is familiar to Windows users. It also has a paid model that comes with more desktop options and free software. it was first released on the first of July, 2009, under the name Zorin OS 1.0. 7575f071de497275785178da95752afd1071e9b1 0 1091 4719 4445 2026-05-22T23:53:43Z MysteryBirb 353 Added Features segment, added an installation steps and gave a bit of eye candy wikitext text/x-wiki {{SoftwareInfobox|caption=MangoWM logo|developers=MangoWM developers|firstrelease=0.1.1, 2025-02-17|languages=[[C]]|lastrelease=V0.13.1, 2026-05-18|title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io]|releasestatus=Maintained|image=[[File:Mango-transparency-256.png|thumb|center]]}}{{Needs Citations}}{{Work In Progress}} MangoWC is a [[Wayland]] compositor based on [[dwl]] that keeps its lightweight, suckless-style design while adding more practical features. It stays fast to build and minimal, but improves usability with better layouts, multi-monitor support, and broader Wayland compatibility, making it more suitable for daily use without unnecessary bloat. === Highlighted Features: === * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. ==== Additional Features: ==== * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag === Installation: === ===== AerynOS: ===== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ===== Arch: ===== Using yay:<syntaxhighlight lang="bash"> yay -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> yay -S mango-git </syntaxhighlight>Using paru:<syntaxhighlight lang="bash"> paru -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> paru -S mango-git </syntaxhighlight> ===== Fedora: ===== First we need to add the terra repository:<syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>Then, install it with dnf:<syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== Building from source: ==== Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ===== Dependencies: ===== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ===== Building wlroots from source: ===== Clone and install the specific version required (check wlroots README for latest version).<syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ===== Building scenefx from source: ===== Clone and install the specific version required same as wlroots.<syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building MangoWM from source: ==== At last compile MangoWM from source with the same rules as mentioned above.<syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 993320086ee412b9b5a039a10a973a3fa1618418 0 826 4720 4718 2026-05-22T23:54:17Z Uniolo 345 Fixed typo, added some commas wikitext text/x-wiki {{Needs Citations}} {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Helix editor.svg|thumb|The logo for Helix]] |caption=Helix Editor |title=Helix |releasestatus=Maintained |lastrelease=25.07.1, Jul 18, 2025 |firstrelease=0.0.2, May 12, 2021 |languages=[[Rust]] |developers=[https://mxxn.io/ Blaž Hrastnik] |website=[https://helix-editor.com/ helix-editor.com] }} [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]]{{Citation needed}} and [[Kakoune]]<ref name=":0">[https://helix-editor.com/ Helix website] (accessed 2026-05-22)</ref>. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. Helix bundles and enables many features out of the box and does not yet have a plugin system, although that is currently being worked on<ref name=":0" />. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. Due to its lack of plugin support, many users decide to fork Helix in order to add functionality that isn't included out of the box{{Citation needed}}. Helix is configured through [[TOML]]. ==Usage tips== While many of the same keybindings and concepts as [[Vi]] and [[Vim]] apply to Helix, many of the keybindings and concepts are different. The recommended way to learn Helix is by using the <code>:tutor</code> command whilst inside Helix, to do this, run <code>Helix</code> and type <code>:tutor</code>, then hit enter and follow the instructions. On some [[Linux Distributions|distros]], the executable is named <code>helix</code> (like on ArchLinux<ref>{{Cite|url=https://archlinux.org/packages/extra/x86_64/helix/|title="Helix" package on ArchLinux|author=Orhun Parmaksız|year=2025-07-18|accessdate=2026-05-22}}</ref>), while on others, it is named <code>hx</code> (like on Alpine Linux<ref>{{Cite|url=https://pkgs.alpinelinux.org/contents?name=helix&repo=community&branch=edge&arch=x86_64|title="Helix" package on the Alpine Linux community repository|author=Jakub Jirutka|year=2026-05-04|accessdate=2026-05-22}}</ref>). This may cause issues if you develop muscle memory for the names of one of these commands, to get around this, you can create a symlink under your chosen name. [[Category:Software]] <references /> 57f6b67d1e1688ee8fc44e2a592c9620102dd601 4722 4720 2026-05-22T23:55:22Z Uniolo 345 Removed citation notice wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Helix editor.svg|thumb|The logo for Helix]] |caption=Helix Editor |title=Helix |releasestatus=Maintained |lastrelease=25.07.1, Jul 18, 2025 |firstrelease=0.0.2, May 12, 2021 |languages=[[Rust]] |developers=[https://mxxn.io/ Blaž Hrastnik] |website=[https://helix-editor.com/ helix-editor.com] }} [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]]{{Citation needed}} and [[Kakoune]]<ref name=":0">[https://helix-editor.com/ Helix website] (accessed 2026-05-22)</ref>. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. Helix bundles and enables many features out of the box and does not yet have a plugin system, although that is currently being worked on<ref name=":0" />. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. Due to its lack of plugin support, many users decide to fork Helix in order to add functionality that isn't included out of the box{{Citation needed}}. Helix is configured through [[TOML]]. ==Usage tips== While many of the same keybindings and concepts as [[Vi]] and [[Vim]] apply to Helix, many of the keybindings and concepts are different. The recommended way to learn Helix is by using the <code>:tutor</code> command whilst inside Helix, to do this, run <code>Helix</code> and type <code>:tutor</code>, then hit enter and follow the instructions. On some [[Linux Distributions|distros]], the executable is named <code>helix</code> (like on ArchLinux<ref>{{Cite|url=https://archlinux.org/packages/extra/x86_64/helix/|title="Helix" package on ArchLinux|author=Orhun Parmaksız|year=2025-07-18|accessdate=2026-05-22}}</ref>), while on others, it is named <code>hx</code> (like on Alpine Linux<ref>{{Cite|url=https://pkgs.alpinelinux.org/contents?name=helix&repo=community&branch=edge&arch=x86_64|title="Helix" package on the Alpine Linux community repository|author=Jakub Jirutka|year=2026-05-04|accessdate=2026-05-22}}</ref>). This may cause issues if you develop muscle memory for the names of one of these commands, to get around this, you can create a symlink under your chosen name. [[Category:Software]] <references /> 8d03e7fd74653448d8f269a329945f6e60ef22b9 0 247 4721 4702 2026-05-22T23:54:42Z LeahTheSlug 356 /* References{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}} */ wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight> # apt upgrade </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). Examples:<syntaxhighlight> # apt install meow # apt install meow- pipes+ </syntaxhighlight> ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight> # apt remove pipes </syntaxhighlight> ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight> $ apt search minecraft </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight> # apt autoremove </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == <references><ref/></references> 990a503c892a0b20781c9f1a8dd5c7d4f56baea9 4723 4721 2026-05-22T23:55:35Z LeahTheSlug 356 wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). Examples:<syntaxhighlight> # apt install meow # apt install meow- pipes+ </syntaxhighlight> ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight> # apt remove pipes </syntaxhighlight> ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight> $ apt search minecraft </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight> # apt autoremove </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == <references><ref/></references> 49027c76ac9333e40f40925252da23bf85a70b3b 4724 4723 2026-05-23T00:00:23Z LeahTheSlug 356 /* References{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}} */ wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). Examples:<syntaxhighlight> # apt install meow # apt install meow- pipes+ </syntaxhighlight> ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight> # apt remove pipes </syntaxhighlight> ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight> $ apt search minecraft </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight> # apt autoremove </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == e186be593878afeec1e121e1fdec687b0a94c788 4738 4724 2026-05-23T00:35:30Z LeahTheSlug 356 pipes-sh instead of pipes wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). Examples:<syntaxhighlight> # apt install meow # apt install meow- pipes-sh+ </syntaxhighlight> ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight> # apt remove pipes-sh </syntaxhighlight> ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight> $ apt search minecraft </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight> # apt autoremove </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == 8c9c3f10be3b49b9fa8ec166cad54dcd0564baa9 0 1091 4725 4719 2026-05-23T00:02:04Z MysteryBirb 353 Moved SoftwareInfobox position wikitext text/x-wiki {{Needs Citations}} {{Work In Progress}} {{SoftwareInfobox |caption=MangoWM logo |developers=MangoWM developers |firstrelease=0.1.1, 2025-02-17 |languages=[[C]] |lastrelease=V0.13.1, 2026-05-18 |title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io] |releasestatus=Maintained |image=[[File:Mango-transparency-256.png|thumb|center]]}} MangoWC is a [[Wayland]] compositor based on [[dwl]] that keeps its lightweight, suckless-style design while adding more practical features. It stays fast to build and minimal, but improves usability with better layouts, multi-monitor support, and broader Wayland compatibility, making it more suitable for daily use without unnecessary bloat. === Highlighted Features: === * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. ==== Additional Features: ==== * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag === Installation: === ===== AerynOS: ===== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ===== Arch: ===== Using yay:<syntaxhighlight lang="bash"> yay -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> yay -S mango-git </syntaxhighlight>Using paru:<syntaxhighlight lang="bash"> paru -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> paru -S mango-git </syntaxhighlight> ===== Fedora: ===== First we need to add the terra repository:<syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>Then, install it with dnf:<syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== Building from source: ==== Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ===== Dependencies: ===== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ===== Building wlroots from source: ===== Clone and install the specific version required (check wlroots README for latest version).<syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ===== Building scenefx from source: ===== Clone and install the specific version required same as wlroots.<syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building MangoWM from source: ==== At last compile MangoWM from source with the same rules as mentioned above.<syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 1d952b370eaf45d82b5d3d8b8ab58471809c2790 4726 4725 2026-05-23T00:06:37Z MysteryBirb 353 Added Guide Warning wikitext text/x-wiki {{Needs Citations}} {{Work In Progress}} {{Guide Warning}} {{SoftwareInfobox |caption=MangoWM logo |developers=MangoWM developers |firstrelease=0.1.1, 2025-02-17 |languages=[[C]] |lastrelease=V0.13.1, 2026-05-18 |title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io] |releasestatus=Maintained |image=[[File:Mango-transparency-256.png|thumb|center]]}} MangoWC is a [[Wayland]] compositor based on [[dwl]] that keeps its lightweight, suckless-style design while adding more practical features. It stays fast to build and minimal, but improves usability with better layouts, multi-monitor support, and broader Wayland compatibility, making it more suitable for daily use without unnecessary bloat. === Highlighted Features: === * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. ==== Additional Features: ==== * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag === Installation: === ===== AerynOS: ===== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ===== Arch: ===== Using yay:<syntaxhighlight lang="bash"> yay -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> yay -S mango-git </syntaxhighlight>Using paru:<syntaxhighlight lang="bash"> paru -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> paru -S mango-git </syntaxhighlight> ===== Fedora: ===== First we need to add the terra repository:<syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>Then, install it with dnf:<syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== Building from source: ==== Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ===== Dependencies: ===== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ===== Building wlroots from source: ===== Clone and install the specific version required (check wlroots README for latest version).<syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ===== Building scenefx from source: ===== Clone and install the specific version required same as wlroots.<syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building MangoWM from source: ==== At last compile MangoWM from source with the same rules as mentioned above.<syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> d7c59c64f71ef142f15b6a326e607e2aef184bc4 4728 4726 2026-05-23T00:11:49Z MysteryBirb 353 Format fix wikitext text/x-wiki {{Needs Citations}} {{Work In Progress}} {{Guide Warning}} {{SoftwareInfobox |caption=MangoWM logo |developers=MangoWM developers |firstrelease=0.1.1, 2025-02-17 |languages=[[C]] |lastrelease=V0.13.1, 2026-05-18 |title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io] |releasestatus=Maintained |image=[[File:Mango-transparency-256.png|thumb|center]]}} MangoWC is a [[Wayland]] compositor based on [[dwl]] that keeps its lightweight, suckless-style design while adding more practical features. It stays fast to build and minimal, but improves usability with better layouts, multi-monitor support, and broader Wayland compatibility, making it more suitable for daily use without unnecessary bloat. === Highlighted Features: === * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. ==== Additional Features: ==== * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag === Installation: === ===== AerynOS: ===== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ===== Arch: ===== Using yay:<syntaxhighlight lang="bash"> yay -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> yay -S mango-git </syntaxhighlight>Using paru:<syntaxhighlight lang="bash"> paru -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> paru -S mango-git </syntaxhighlight> ===== Fedora: ===== First we need to add the terra repository:<syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>Then, install it with dnf:<syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== Building from source: ==== Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ===== Dependencies: ===== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ===== Building wlroots from source: ===== Clone and install the specific version required (check wlroots README for latest version).<syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ===== Building scenefx from source: ===== Clone and install the specific version required same as wlroots.<syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building MangoWM from source: ==== At last compile MangoWM from source with the same rules as mentioned above.<syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 2c5d711b6c207052c602a97a566605967c18202a 4729 4728 2026-05-23T00:14:31Z MysteryBirb 353 Format fix wikitext text/x-wiki {{Needs Citations}} {{Work In Progress}} {{Guide Warning}} {{SoftwareInfobox |caption=MangoWM logo |developers=MangoWM developers |firstrelease=0.1.1, 2025-02-17 |languages=[[C]] |lastrelease=V0.13.1, 2026-05-18 |title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io] |releasestatus=Maintained |image=[[File:Mango-transparency-256.png|thumb|center]] }} MangoWC is a [[Wayland]] compositor based on [[dwl]] that keeps its lightweight, suckless-style design while adding more practical features. It stays fast to build and minimal, but improves usability with better layouts, multi-monitor support, and broader Wayland compatibility, making it more suitable for daily use without unnecessary bloat. === Highlighted Features: === * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. ==== Additional Features: ==== * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag === Installation: === ===== AerynOS: ===== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ===== Arch: ===== Using yay:<syntaxhighlight lang="bash"> yay -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> yay -S mango-git </syntaxhighlight>Using paru:<syntaxhighlight lang="bash"> paru -S mangowm </syntaxhighlight>or for the latest git version:<syntaxhighlight lang="bash"> paru -S mango-git </syntaxhighlight> ===== Fedora: ===== First we need to add the terra repository:<syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>Then, install it with dnf:<syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> === Building from source: === Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ===== Dependencies: ===== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ===== Building wlroots from source: ===== Clone and install the specific version required (check wlroots README for latest version).<syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ===== Building scenefx from source: ===== Clone and install the specific version required same as wlroots.<syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building MangoWM from source: ==== At last compile MangoWM from source with the same rules as mentioned above.<syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> daec2a609e21aa7f97c9726a0db3bf7c5da65b20 4759 4729 2026-05-23T02:17:54Z MysteryBirb 353 Added install guide for a few extra OSs wikitext text/x-wiki {{Needs Citations}} {{Work In Progress}} {{Guide Warning}} {{SoftwareInfobox |caption=MangoWM logo |developers=MangoWM developers |firstrelease=0.1.1, 2025-02-17 |languages=[[C]] |lastrelease=V0.13.1, 2026-05-18 |title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io] |releasestatus=Maintained |image=[[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formally known as MangoWC) is a [[Wayland]] compositor based on [[dwl]] that keeps its lightweight, suckless-style design while adding more practical features.I think it looks alright. While staying minimal and fast to build, MangoWM improves on usability with better layouts, multi-monitor supports, and broader wayland compatibility. === Highlighted Features: === * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. ==== Additional Features: ==== * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag === Installation: === ===== AerynOS: ===== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ===== Arch: ===== Using yay: <syntaxhighlight lang="bash"> yay -S mangowm </syntaxhighlight> or for the latest git version: <syntaxhighlight lang="bash"> yay -S mango-git </syntaxhighlight> Using paru: <syntaxhighlight lang="bash"> paru -S mangowm </syntaxhighlight> or for the latest git version: <syntaxhighlight lang="bash"> paru -S mango-git </syntaxhighlight> ===== Fedora: ===== First we need to add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then, install it with dnf: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ===== Gentoo: ===== Firstly we add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Followed by unmasking of these packages in your package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ===== Guix System: ===== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash"> (cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels) </syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ===== PikaOS: ===== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> === Building from source: === Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ===== Dependencies: ===== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ===== Building wlroots from source: ===== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ===== Building scenefx from source: ===== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building MangoWM from source: ==== At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> baa0133a6c2ef9e2a90813163451f9a45c56e2cc 0 322 4727 3646 2026-05-23T00:11:13Z MarkH 357 Fix Linux kernel link and grammar wikitext text/x-wiki [[Category:Software]] {{Needs Citations}} {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the [[Linux kernel]], released under the MIT License. It was developed by Rich Felker as a clean, efficient, and standards-conformant libc implementation. == Usage on [[Operating System|Operating Systems]] == [[Linux Distributions|Linux distributions]] that use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * [[Sabotage]] * [[Morpheus Linux]] * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against glibc. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. == See also == * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] 1280babcbcebc16c9f87d9d4dc3e6c1f95d0b63e 4744 4727 2026-05-23T01:09:33Z Operz 344 Describe some differences from other libc impls, add links to skarnet solutions wikitext text/x-wiki [[Category:Software]] {{Needs Citations}} {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] }} '''musl''' is a C standard library intended for operating systems based on the [[Linux kernel]], released under the MIT License. It was developed by Rich Felker as a clean, efficient, and standards-conformant libc implementation. == Usage on [[Operating System|Operating Systems]] == [[Linux Distributions|Linux distributions]] that use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * [[Sabotage]] * [[Morpheus Linux]] * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against glibc. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. == Notable differences from [[Glibc]] and Other C Libraries == musl is noted to have chosen certain sacrifices in functionality as design choices for security. === utmp(x) and Other Accounting Functionality === The utmp/wtmp family of Unix and POSIX<ref>{{Cite|url=https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/utmpx.h.html|title=user accounting database definitions, The Open Group Base Specifications Issue 8 (IEEE Std 1003.1-2024)|author=The IEEE and The Open Group|year=2024|accessdate=2026-05-22}}</ref><ref>{{Cite|url=https://pubs.opengroup.org/onlinepubs/9799919799/functions/endutxent.html|title=user accounting database functions, The Open Group Base Specifications Issue 8 (IEEE Std 1003.1-2024)|author=The IEEE and The Open Group|year=2024|accessdate=2026-05-22}}</ref> functions have been removed due to security concerns<ref>{{Cite|url=https://wiki.musl-libc.org/faq.html#Q:-Why-is-the-utmp/wtmp-functionality-only-implemented-as-stubs?|title=musl libc FAQ|author=Kylie McClain|year=2016|accessdate=2026-05-22}}</ref><!-- NOTE: I got the author info for this citation from the git blame of the musl libc wiki: https://github.com/somasis/musl-wiki/blame/e8e065dd5aaf1a189bc659f347638f4b155fc3f4/faq.md#L90 -->. This decision breaks several programs that are useful on multi-user systems, such as wall, last, and who. [https://skarnet.org/software/utmps/ Skarnet implements a daemon which can provide such functionality on musl systems], however it is not included by default on most of these distributions. === Name Service Switch (nsswitch) === Glibc and most other ctandard C libraries on UNIX and Unix-like systems implement something known as the Name Service Switch, or, nsswitch<ref>{{Cite|url=https://skarnet.org/software/nsss/nsswitch.html|title=The problem with nsswitch|author=Skarnet|accessdate=2025-05-22}}</ref>. Musl does not implement these functions either, so [https://skarnet.org/software/nsss/ Skarnet has also provided another daemon for this]. == References == <references /> == See also == * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] 222f9ae61075149d5c53106867b1a514ec72acdd 1 1138 4730 2026-05-23T00:15:03Z LeahTheSlug 356 /* What else needs done */ new section wikitext text/x-wiki == What else needs done == Completion of apt commands and argumentsSection for apt-get, apt-cache & apt-mark footnote for apt-cdrom, apt-config, apt-extracttemplates, & apt-helper unless anyone can give me a valid reason to include these and would like to contribute to their section [[User:LeahTheSlug|LeahTheSlug]] ([[User talk:LeahTheSlug|talk]]) 00:15, 23 May 2026 (UTC) 8a701b671cac59f0a8dac190207742bc108040e3 4731 4730 2026-05-23T00:15:48Z LeahTheSlug 356 /* What else needs done */ wikitext text/x-wiki == What else needs done == Completion of apt commands and arguments Section for apt-get, apt-cache & apt-mark footnote for apt-cdrom, apt-config, apt-extracttemplates, & apt-helper unless anyone can give me a valid reason to include these and would like to contribute to their section [[User:LeahTheSlug|LeahTheSlug]] ([[User talk:LeahTheSlug|talk]]) 00:15, 23 May 2026 (UTC) 9a176ce6afc68082293038aa461c71496cd9a321 4733 4731 2026-05-23T00:17:06Z LeahTheSlug 356 /* What else needs done */ wikitext text/x-wiki == What else needs done == Completion of apt commands and arguments Section for apt-get, apt-cache & apt-mark footnote for apt-cdrom, apt-config, apt-extracttemplates, & apt-helper unless anyone can give me a valid reason to include these and would like to contribute to their section [[User:LeahTheSlug|LeahTheSlug]] ([[User talk:LeahTheSlug|talk]]) 00:15, 23 May 2026 (UTC) 941603b2be72be24948b4bc471f8f0c94551e92b 0 1127 4732 4684 2026-05-23T00:16:27Z Matthias von Schwarzwald 361 Typos, linking, and cleanup wikitext text/x-wiki [[File:LibreWolf Icon.png|thumb]] LibreWolf is an open-source fork of the browser Mozilla [[Firefox]] focused on privacy and security. Their website is https://librewolf.net. It was originally released for Linux in March 2020 with a community-maintained version being released for Microsoft Windows in February 2021 and a Mac port following a few months later in April 2021. == Features == LibreWolf's main purpose is privacy, therefore the features it adds are all mainly privacy-based. Some features LibreWolf adds include uBlock Origin by default, disabled telemetry, DuckDuckGo as the default search engine, cookies and history being wiped on closing of browser by default, and Firefox Sync being disabled by default. == License == LibreWolf's source code is currently licensed under MPL 2.0 and their website is licensed under [[GNU]] [[GNU General Public License|AGPL 3.0]]. == Source code location == The LibreWolf source code is currently kept at https://codeberg.org/librewolf and https://gitlab.com/librewolf-community. == Current Linux distro support == [[Gentoo]], [[Arch Linux|Arch]], Debian-based, [[Fedora]], [[openSUSE]] and available to any other distro via a [[Flatpak]] and an AppImage. == Windows support == You can get LibreWolf on Windows via the Microsoft Store, a portable release as just a .exe or with [[Package Manager|Package Managers]] like Scoop, Chocolatey and Winget. [[Category:Software]] e2355989e540af9c141df9e39988856b8eb652a8 4745 4732 2026-05-23T01:11:34Z Matthias von Schwarzwald 361 Add category "Browsers" wikitext text/x-wiki [[File:LibreWolf Icon.png|thumb]] LibreWolf is an open-source fork of the browser Mozilla [[Firefox]] focused on privacy and security. Their website is https://librewolf.net. It was originally released for Linux in March 2020 with a community-maintained version being released for Microsoft Windows in February 2021 and a Mac port following a few months later in April 2021. == Features == LibreWolf's main purpose is privacy, therefore the features it adds are all mainly privacy-based. Some features LibreWolf adds include uBlock Origin by default, disabled telemetry, DuckDuckGo as the default search engine, cookies and history being wiped on closing of browser by default, and Firefox Sync being disabled by default. == License == LibreWolf's source code is currently licensed under MPL 2.0 and their website is licensed under [[GNU]] [[GNU General Public License|AGPL 3.0]]. == Source code location == The LibreWolf source code is currently kept at https://codeberg.org/librewolf and https://gitlab.com/librewolf-community. == Current Linux distro support == [[Gentoo]], [[Arch Linux|Arch]], Debian-based, [[Fedora]], [[openSUSE]] and available to any other distro via a [[Flatpak]] and an AppImage. == Windows support == You can get LibreWolf on Windows via the Microsoft Store, a portable release as just a .exe or with [[Package Manager|Package Managers]] like Scoop, Chocolatey and Winget. [[Category:Software]] [[Category:Browsers]] 88211d1147781c786c9a4d7854eb71049dbb1d2a 0 853 4734 4682 2026-05-23T00:19:51Z Matthias von Schwarzwald 361 Some typos wikitext text/x-wiki {{Work_In_Progress}} The '''GNU General Public License''' (short '''GNU GPL''' or '''GPL''') is a collection of copyleft licenses published by the Free Software Foundation (FSF) and written by Richard Stallman<ref>https://archive.ph/20120907170559/http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html{{Dead Link|2025-08-14|429}}</ref>. This License is also part of the [[GNU]] project. === Copyleft === A copyleft license requires that any modifications or extensions to a program licensed under a copyleft license must also be licensed under the same (or a compatible) license. === "or-later" clause === All GNU GPL licenses may contain an optional clause, an “or-later” clause (sometimes referred to as a “lifeboat clause”). This clause allows all later versions to be used. Programs without this clause are referred to as “only.” For example * GNU GPLv2-or-later can also be licensed under GNU GPLv3-or-later without any problem * GNU GPLv2-only can only be licensed under the GNU GPLv2 The same applies to the GNU AGPL and LGPL licenses. The FSF recommends using the “or-later” clause, as it is compatible with future versions of the GNU GPL, since GNU GPLv2 and v3 are not compatible and therefore a program licensed only under GNU GPLv2 cannot be mixed with a GNU GPLv3 program. == Licenses == There are three versions of the GNU GPL, with version 3 being the most recent version for all of them. # GNU General Public License (GPL) – The standard strong copyleft license used for most programs. # GNU Lesser General Public License (LGPL) – A weak copyleft license mainly used for libraries. # GNU Affero General Public License (AGPL) – Similar to the GPL, but also covers use over a network. === GNU General Public License (GPL) === This license is used for regular programs such as the Linux kernel, which uses GNU GPLv2 only. The latest version is the GNU General Public License Version 3 (GNU GPLv3), which was released in June 2007<ref>[https://www.gnu.org/licenses/gpl-3.0.en.html#license-text The GNU General Public License v3.0], Free Software Foundation, 2007-08-14 (Accessed: 2025-08-14)</ref> and can be found [https://www.gnu.org/licenses/gpl-3.0.en.html#license-text here]. If part of a program (e.g., a library) uses this license, the entire program must be licensed under the GNU GPL. If this is not desired, the GNU LGPL or another license should be used. === GNU Lesser General Public License (LGPL) === The GNU LGPL (formerly known as the Library General Public License) was created at the same time as the GNU GPLv2 and was also published in June 2007, but the first version was called GNU LGPLv2 to match the GNU GPLv2. This license was created because the GNU GPL was too restrictive, especially for libraries. If a program uses a library licensed under the GNU LGPL, only the modification of that library must be published. This allows a library to be used in [[proprietary software]]. The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/lgpl-3.0.html here]. === GNU Affero General Public License (AGPL) === The GNU AGPL was created to close a loophole when modified software licensed under the GNU GPL was run on a server the source code don't need to be published because of that the AGPL was created to fix this loophole The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/agpl-3.0.html#license-text here] <references /> [[Category:Software licenses]] e4bc34446582c713b5899717df282ba2e65f00c6 0 344 4735 3630 2026-05-23T00:21:04Z MarkH 357 Fix Linux kernel link, formatting, capitalization wikitext text/x-wiki [[Category:Terminology]] [[File:Kernel Layout.svg|thumb|How the Kernel interacts with the software and hardware.]] The '''kernel''' is the core part of any [[Operating System|operating system]], such as the [[Linux kernel]]. It's the fundamental layer between the computer's [[hardware]], including but not limited to the CPU, RAM, and GPU, and the [[:Category:Software|software]] you interact with. The Linux kernel itself is a modular and monolithic kernel, meaning that it incorporates most of the core functions within the kernel itself (Like process management, device drivers, memory management, file systems, etc.). These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2 Linus Torvalds 1991 (Retrieved 16th March 2025)</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel Kicksecure, Madaiden, Adrelanos 2023 (Retrieved 16th March 2025)</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. == References == e5aa836828d2f982c36de41899f23821929624ec 3000 1136 4736 4711 2026-05-23T00:34:17Z Uniolo 345 Changed wording in "Why switch?", added note about forking in Choices, and added comment about discussing in talk page about "Picking a Linux" due to bias. wikitext text/x-wiki Welcome to the penguin side! Switching to Linux feels scary at first, but you'll realize how much better things are with a faster system that's free and customizable. === Why switch? === * Windows can be slow on many devices, especially compared to Linux. * Windows is considered by many to be "spyware", Linux on the other hand, is fully auditable. * Windows keeps breaking. * Linux is faster in many cases. * You can replace the entire Desktop if you want! * Easier to install programs than on Windows due to [[Package Manager|Package managers]]. === Choices === Linux is all about choices. Before you start, you need to pick what your Linux [[Desktop Environments|looks like]] and is [[Linux Distributions|under the hood]]. On Windows, if Microsoft added a backdoor or malware, you might not even know, but on Linux, the project would be instantly forked to remove the malicious piece and everyone would know! === Picking a Linux ===<!-- Discuss on talk page due to potential for bias. --> There are (too) many flavors of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]]. If you don't like the Linux you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a GUI === When you install a Linux, the installer asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on touchpad gestures consider [[GNOME]]. d3dd92271d16e5ea1dfbd0782e65018a375ad59f 4741 4736 2026-05-23T01:00:16Z Uniolo 345 Updated comment (which should only appear to those editing) wikitext text/x-wiki Welcome to the penguin side! Switching to Linux feels scary at first, but you'll realize how much better things are with a faster system that's free and customizable. === Why switch? === * Windows can be slow on many devices, especially compared to Linux. * Windows is considered by many to be "spyware", Linux on the other hand, is fully auditable. * Windows keeps breaking. * Linux is faster in many cases. * You can replace the entire Desktop if you want! * Easier to install programs than on Windows due to [[Package Manager|Package managers]]. === Choices === Linux is all about choices. Before you start, you need to pick what your Linux [[Desktop Environments|looks like]] and is [[Linux Distributions|under the hood]]. On Windows, if Microsoft added a backdoor or malware, you might not even know, but on Linux, the project would be instantly forked to remove the malicious piece and everyone would know! === Picking a Linux ===<!-- Discuss on talk page before modifying this section due to potential for bias. --> There are (too) many flavors of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]]. If you don't like the Linux you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a GUI === When you install a Linux, the installer asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on touchpad gestures consider [[GNOME]]. acb53a7e5b9f39855e51de37897b8cb8d1c21e1f 4742 4741 2026-05-23T01:07:18Z Deviaze 341 add wip tag wikitext text/x-wiki {{Work In Progress}} Welcome to the penguin side! Switching to Linux feels scary at first, but you'll realize how much better things are with a faster system that's free and customizable. === Why switch? === * Windows can be slow on many devices, especially compared to Linux. * Windows is considered by many to be "spyware", Linux on the other hand, is fully auditable. * Windows keeps breaking. * Linux is faster in many cases. * You can replace the entire Desktop if you want! * Easier to install programs than on Windows due to [[Package Manager|Package managers]]. === Choices === Linux is all about choices. Before you start, you need to pick what your Linux [[Desktop Environments|looks like]] and is [[Linux Distributions|under the hood]]. On Windows, if Microsoft added a backdoor or malware, you might not even know, but on Linux, the project would be instantly forked to remove the malicious piece and everyone would know! === Picking a Linux ===<!-- Discuss on talk page before modifying this section due to potential for bias. --> There are (too) many flavors of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]]. If you don't like the Linux you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a GUI === When you install a Linux, the installer asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on touchpad gestures consider [[GNOME]]. 16185ce291b3b5e1e799bf91c306d2f27fef043f 14 397 4737 3800 2026-05-23T00:34:36Z Nathan22211 360 categorized software by type rather than solely the index (WIP) wikitext text/x-wiki Software refers to the programs, routines, and symbolic languages that control the functioning of a computer. {| class="wikitable" |+Common Linux Terminal commands !software !description !used for |- !ls !'''List directories and files in the directory s'''pecifie'''d''' !'''file management''' |- |cd |move the working directory |navigation |- |mv |moves files or folder from one directory to another |file management |- |rm |deletes files and/or folders |file management |- |cp |copies files and/or folders from one directory to another |file management |} {| class="wikitable" |+Audio and video. !software !description !used for |- |[[PipeWire]] |audio and video pipeline server with pulse backwards compatibility |audio server, video server |- |[[PulseAudio]] |audio sound server for linux systems |audio server |- |[[Pulse-visualizer]] |real time audio visualizer for pulse |audio visulization |- |[[Psysonic]] |music streaming client for navidrome servers and last.fm |audio listening |} {| class="wikitable" |+terminal shells !software !decription |- |[[Zsh]] |cross platform shell with spell checking and programmable command completion. Default shell for macOS |- |Xonsh |python based shell able to execute both python and bash functions with cross terminal command history |- | | |} 4fe8dc6e74551bb6483f6ea96a4c50c3b2da4417 2 1139 4739 2026-05-23T00:44:13Z LeahTheSlug 356 Leah wikitext text/x-wiki I am leah :3 b032d396fad20b1a6153b5e4176e251722adf466 0 396 4740 1384 2026-05-23T00:56:33Z Deviaze 341 Article page should not be linked to category page. wikitext text/x-wiki {{Work In Progress}} This page is dedicated to listing common free and open source software used on [[Linux]] distributions. 7d6593a9f9f02c3d69cd29ed5370b80879245f61 4750 4740 2026-05-23T01:28:43Z Deviaze 341 Added common drawing/image editing, word processing, and text editor programs used on Linux wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. {| class="wikitable" |+Drawing/Image editing !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program |- |Krita |Raster drawing program |- |Inkscape |Vector illustration program |} {| class="wikitable" |+Word processing and office suite software !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} {| class="wikitable" |+Text editors !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |Kate |KDE Advanced Text Editor |} 3173d2d6a0ac4f6332a2cd91b407eb62d5534682 4752 4750 2026-05-23T01:41:46Z Deviaze 341 Add headings for organization wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Digital art and image editing = Used to edit raster (pixel based) and vector (line based) images {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |Inkscape |Vector illustration program |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. {| class="wikitable" |} {| class="wikitable" |+ Text editors !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |Kate |KDE Advanced Text Editor |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |} {| class="wikitable" |} 29104e4768c726002601c01f55fc57f06a1267b8 4753 4752 2026-05-23T01:43:37Z Deviaze 341 fix empty table issues caused by visual editor wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Digital art and image editing = Used to edit raster (pixel based) and vector (line based) images {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |Inkscape |Vector illustration program |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. {| class="wikitable" |+ Text editors !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |Kate |KDE Advanced Text Editor |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |} 8c7a3222469644db4a91088dd11ea40d4253639b 4754 4753 2026-05-23T01:52:28Z Deviaze 341 /* Text editing and software development */ Add more software and improve organization wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing svgs. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |Kate |KDE Advanced Text Editor |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |} ded79006cfafd8aafd0bec8bdebc5f94764063a1 4755 4754 2026-05-23T01:58:43Z Deviaze 341 /* Text editors */ Make subcategories, add more editors wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing svgs. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. 3f4f0f4425b2248e81ecefde3563b1f123164cab 1 1140 4743 2026-05-23T01:07:42Z Nathan22211 360 /* how to organize software */ new section wikitext text/x-wiki == how to organize software == half actual discussion, half making sure some browsers aren't breaking this feature [[User:Nathan22211|Nathan22211]] ([[User talk:Nathan22211|talk]]) 01:07, 23 May 2026 (UTC) 548bf284440ed27e87f7e818e523c9fd892677f9 2 1141 4746 2026-05-23T01:11:39Z Operz 344 Created page with "Hi, I'm operz and I like Solaris and Illumos and BSD and Unix. Not really big on Linux but I am a specialist in the others." wikitext text/x-wiki Hi, I'm operz and I like Solaris and Illumos and BSD and Unix. Not really big on Linux but I am a specialist in the others. 8aa4a83935a9035bc58d26ff1cdd2aa55a5d5b30 0 169 4747 4391 2026-05-23T01:19:40Z Operz 344 add pkgsrc to list wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to handle [[package]]s, [[software]] delivered in specific formats. Regular functions include [[install]]ing, removing, updating, and searching packages, usually from a package [[repository]]. === List of Package Managers === Note: The ''Used By'' field also implies [[derivative]]s, which are listed in the [[Linux Distributions]] page. There are exceptions to this rule, specifically cross-distribution package managers such as [[snap]], [[nix]] and [[flatpak]]. For a list of package formats, see the [[package]] page. {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[Paldius|paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- |[[pkgsrc]] |[[C]], [https://www.crufty.net/help/sjg/bmake.html BSD Makefiles] |[[NetBSD]], SmartOS/[[illumos]], [[macOS]]/[[Darwin]], [[Linux]], [[Oracle Solaris|Solaris]], MINIX 3<ref name=":0">{{Cite|url=https://pkgsrc.org/|title=pkgsrc|author=The NetBSD Foundation|year=2025|accessdate=2026-05-22}}</ref> |The NetBSD Foundation<ref name=":0" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[Shell]]|| [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise|SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib /> |} == References == <references /> a09fdeed80409b65f3909a99988e58bf3a41b6c5 0 1142 4748 2026-05-23T01:20:20Z Verl 364 Added initial page, info, and initial citation wikitext text/x-wiki {{GuideWarning}}Windows is a proprietary [[Operating System]] that was developed and is released under Microsoft. While originally catered towards personal computers, Windows now offers versions such as Windows Server, Windows IoT, or Windows LTSC. The first version of its cited release was in November 20, 1985 as Windows 1.0, with a graphical user interface.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Microsoft_Windows|title=Microsoft Windows Wikipedia Entry|accessdate=2026}}</ref> 39b8cdc76ff45bce88eac0681dd02945a8ac99d0 0 198 4749 4710 2026-05-23T01:24:07Z Matthias von Schwarzwald 361 /* Debian Based */ Add PureOS wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Atomic]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- | [[Aeon]] | An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- | [[openSUSE]] | A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- | [[Regata OS]] | A gaming-focused distribution with custom software made for ease of use |- | [[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] | An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- | [[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 71340affe60579ab8e009f39b12a47952a865401 0 886 4751 4023 2026-05-23T01:29:31Z Operz 344 add illumos and heirloom vi to list wikitext text/x-wiki [[Category:Software]] {{Needs Citations|date=august 2025}} {{stub|date=august 2025}} The vi program is a full-screen console-based text editor. It was originally written in the 1970s by Bill Joy and improved in the 1980s by Mary Ann Horton, as an enhancement for [[ex]], which in tern was an enhanced version of [[ed]]. As such, vi still has many ex-like features today. ==Using vi== To use vi, you can hit <code>i</code> or <code>a</code> (append) to enter "insert mode". You then may type what you wish, and hit the <code>esc</code> key to exit "insert mode". When you're no longer in "insert mode", you can hit the ":" (colon) command to type in ex-like commands. The two most common commands are <code>w [filename]</code> to save the file, and <code>q</code>, which is used to quit the program. These commands can be combined to quit and save in one step, like so: <code>wq</code>. To quit without saving, enter <code>q!</code>. When not in insert mode, you may use the <code>h</code> key to move back one column, <code>j</code> to move the cursor down one line, <code>k</code> to move up a line, and the <code>l</code> to move forward one column. Please note that these letters are lowercase. As is often the case with Unix programs, capitalization matters. Also, when in insert mode, you <i>might</i> be able to use your arrow keys, although this seems to depend on which implementation of vi you are using. It is generally recommended to learn the above keys instead. ==Implementations== Modern implementations of vi consist of [[vim]], [[neovim]], [[elvis]], [[nvi]], Heirloom vi<ref>{{Cite|url=https://github.com/n-t-roff/heirloom-ex-vi|title=The Traditional Vi (vi with many enhancements from Gunnar Ritter)|author=Gunnar Ritter et al.|year=2022|accessdate=2026-05-22}}</ref>, the vi from [[Illumos]]<ref>{{Cite|url=https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi|title=illumos-gate/usr/src/cmd/vi on GitHub|author=Illumos core team|year=2025|accessdate=2026-05-22}}</ref>, and the version of vi built in to [[busybox]], the latter of which can be called via <code>busybox vi</code>. nvi/nex is a replacement for vi/ex and was originally developed as part of 4BSD.<ref>https://man.openbsd.org/vi.1</ref> 3bde9c8eaa87bfba5b24bba4ff75f5c59a2507f3 0 1143 4756 2026-05-23T02:10:47Z Deviaze 341 create page since it should very well exist wikitext text/x-wiki {{Stub}} '''Neovim''' is a configurable terminal text editor for Linux, Windows, and macOS. It is configured in Lua. 01e8a061dd5a1415f8a648867268106f0616eff4 4758 4756 2026-05-23T02:15:14Z Deviaze 341 wikitext text/x-wiki {{Stub}} '''Neovim''' (also known as '''nvim''') is a configurable terminal text editor for Linux, Windows, and macOS. It is configured in Lua. 5493e6ffb62677203f0b77d7ea0a65a666a3ad46 0 1144 4757 2026-05-23T02:12:57Z Verl 364 Added initial page, info, supported devices, and basic device categorization wikitext text/x-wiki With the release of the Microsoft Surface line-up (including the Surface Pro, Go, Laptop series), majority of these devices have support for [[Linux Distributions]], but often have issues with device hardware support on stock installs. The community-maintained "Linux Surface" provides a kernel that aims to fix compatibility issues with the Surface-specific hardware, such as Wi-Fi, touchscreen, pen input, sensors, and cameras. == Supported Surface Devices == === Surface on x86_64 === These are majority of the devices that Microsoft has released, seceding the Surface RT line-up. These are the models as follows # Surface Book # Surface Go # Surface Laptop (Excluding Surface Laptop 7) # Surface Laptop Studio # Surface Pro (Excluding Surface Pro X, Surface Pro 9, Surface Pro 11 Snapdragon, Surface Pro 12") # Surface Studio (Untested Support) Although not all devices are as supported, the feature matrix shows the hardware compatibility and guide on installation with the linux-surface kernel. To get started with installation, use the [https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup Installation and Setup] guide from the Linux-surface GitHub. === Surface on arm32 (Aarch32) === These devices were released from Microsoft under the Surface RT lineup. Although these devices don't fall under the linux-surface kernel support, they instead utilize the OpenSurfaceRT guide, as well as other user created guides. ====== Notes: ====== Still massive wip. Need to compile other guides, and to link a couple of installations. 7aecaba199c5f56e0d745c9457b1097cdb671488 4760 4757 2026-05-23T02:20:55Z Verl 364 Added photo + citations wikitext text/x-wiki [[File:2019 02 Microsoft Surface Pro 2017 with signature type cover.jpg|alt=Picture shows a Microsoft Surface Pro 5th Generation from 2017 with the Alcantara type cover running Windows :<|thumb|A Microsoft Surface Pro 2017 (5th Generation)]] With the release of the Microsoft Surface line-up (including the Surface Pro, Go, Laptop series), majority of these devices have support for [[Linux Distributions]], but often have issues with device hardware support on stock installs. The community-maintained "Linux Surface<ref>{{Cite|url=https://github.com/linux-surface/linux-surface|title=Linux Surface|accessdate=2026}}</ref>" provides a kernel that aims to fix compatibility issues with the Surface-specific hardware, such as Wi-Fi, touchscreen, pen input, sensors, and cameras. == Supported Surface Devices == === Surface on x86_64 === These are majority of the devices that Microsoft has released, seceding the Surface RT line-up. These are the models as follows # Surface Book # Surface Go # Surface Laptop (Excluding Surface Laptop 7) # Surface Laptop Studio # Surface Pro (Excluding Surface Pro X, Surface Pro 9, Surface Pro 11 Snapdragon, Surface Pro 12") # Surface Studio (Untested Support) Although not all devices are as supported, the feature matrix shows the hardware compatibility and guide on installation with the linux-surface kernel. To get started with installation, use the [https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup Installation and Setup] guide from the Linux-surface GitHub. === Surface on arm32 (Aarch32) === These devices were released from Microsoft under the Surface RT lineup. Although these devices don't fall under the linux-surface kernel support, they instead utilize the "Open SurfaceRT<ref>{{Cite|url=https://open-rt.gitbook.io/open-surfacert|title=Open SurfaceRT|accessdate=2026}}</ref>" guide, as well as other user created guides. ====== Notes: ====== Still massive wip. Need to compile other guides, and to link a couple of installations. 0423d601eee2848a4a22a198cdb5e044c1e61f9c 4761 4760 2026-05-23T02:21:53Z Verl 364 Added {{GuideWarning}} wikitext text/x-wiki [[File:2019 02 Microsoft Surface Pro 2017 with signature type cover.jpg|alt=Picture shows a Microsoft Surface Pro 5th Generation from 2017 with the Alcantara type cover running Windows :<|thumb|A Microsoft Surface Pro 2017 (5th Generation)]]{{GuideWarning}}With the release of the Microsoft Surface line-up (including the Surface Pro, Go, Laptop series), majority of these devices have support for [[Linux Distributions]], but often have issues with device hardware support on stock installs. The community-maintained "Linux Surface<ref>{{Cite|url=https://github.com/linux-surface/linux-surface|title=Linux Surface|accessdate=2026}}</ref>" provides a kernel that aims to fix compatibility issues with the Surface-specific hardware, such as Wi-Fi, touchscreen, pen input, sensors, and cameras. == Supported Surface Devices == === Surface on x86_64 === These are majority of the devices that Microsoft has released, seceding the Surface RT line-up. These are the models as follows # Surface Book # Surface Go # Surface Laptop (Excluding Surface Laptop 7) # Surface Laptop Studio # Surface Pro (Excluding Surface Pro X, Surface Pro 9, Surface Pro 11 Snapdragon, Surface Pro 12") # Surface Studio (Untested Support) Although not all devices are as supported, the feature matrix shows the hardware compatibility and guide on installation with the linux-surface kernel. To get started with installation, use the [https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup Installation and Setup] guide from the Linux-surface GitHub. === Surface on arm32 (Aarch32) === These devices were released from Microsoft under the Surface RT lineup. Although these devices don't fall under the linux-surface kernel support, they instead utilize the "Open SurfaceRT<ref>{{Cite|url=https://open-rt.gitbook.io/open-surfacert|title=Open SurfaceRT|accessdate=2026}}</ref>" guide, as well as other user created guides. ====== Notes: ====== Still massive wip. Need to compile other guides, and to link a couple of installations. 911102f3824b8a67a5825646cada05fce61298d4 0 1040 4762 4703 2026-05-23T02:55:48Z Jokethatcake 333 wikitext text/x-wiki {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = DNF (Fedora templates), APT (Debian templates) | defaultdesktops = [[XFCE]] | usagetype = Desktop | architectures = x86_64 | website = [https://www.qubes-os.org/ qubes-os.org] | basedon = [[Fedora]], [[Debian]] | init = systemd | virtualization = [[Xen]] | license = Free and open-source software }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] '''Qubes OS''' is a free and open-source, security-focused operating system designed for desktop computing. It uses the principle of ''security through compartmentalization'', isolating different tasks and applications into separate virtualized environments known as '''qubes'''. Qubes OS is built on top of the [[Xen]] hypervisor, which enables strong isolation between qubes. Each qube operates as an independent virtual machine with its own filesystem, applications, and permissions. This architecture reduces the impact of malware or compromised applications by preventing them from easily affecting the rest of the system. == Overview == Unlike traditional Linux distributions where applications share the same environment, Qubes OS separates activities into dedicated domains. For example: * A work qube for office-related tasks * A personal qube for daily browsing * An untrusted qube for opening suspicious files * Disposable qubes for temporary sessions Applications from different qubes can still appear together on the same desktop while remaining isolated internally. == Architecture == Qubes OS uses several specialized domains: * '''dom0''' – The privileged administrative domain responsible for managing the desktop and hardware access. It is intentionally isolated from networking for security reasons. * '''TemplateVMs''' – Base templates used to provide software and root filesystems to AppVMs. * '''AppVMs''' – Everyday working qubes derived from templates. * '''DisposableVMs''' – Temporary qubes automatically destroyed after use. * '''NetVMs''' – Network-handling qubes responsible for internet access. * '''ProxyVMs''' – Intermediate network qubes often used for VPNs, Tor routing, or firewalling. == Security == Qubes OS is widely recognized for its strong security model. Features include: * Strong VM isolation using Xen * Disposable virtual machines * Split networking architecture * USB device isolation * Secure clipboard sharing between qubes * Color-coded window borders indicating qube trust levels The project follows the assumption that no software can ever be completely free from vulnerabilities, so damage containment is prioritized over complete prevention. == Templates == Qubes OS commonly provides templates based on: * [[Fedora]] * [[Debian]] * Whonix * Arch Linux (community-supported) Users can create multiple AppVMs from a single template, reducing storage usage and simplifying updates. == System Requirements == Qubes OS has relatively high hardware requirements compared to many Linux distributions due to its virtualization-heavy design. Recommended requirements include: * 64-bit Intel VT-x or AMD-V CPU * VT-d / AMD-Vi IOMMU support * At least 16 GB RAM recommended * SSD storage strongly recommended == Use Cases == Qubes OS is commonly used by: * Security researchers * Journalists * Privacy-conscious users * Developers handling untrusted software * Users requiring strong compartmentalization == Criticism == While Qubes OS offers strong security benefits, it is often criticized for: * High hardware requirements * Steep learning curve * Reduced compatibility with some hardware * Increased complexity compared to traditional Linux distributions == See also == * [[Xen]] * [[Whonix]] * [[Fedora]] * [[Debian]] * [[Virtualization]] == External links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Documentation] dc817a062aa2402ae9c88d5624a8ad66e72c2078 4763 4762 2026-05-23T02:57:04Z Jokethatcake 333 wikitext text/x-wiki {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = DNF, APT | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = systemd | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Unlike traditional Linux distributions which rely mainly on permissions and process isolation, Qubes OS separates applications and workflows into isolated virtual machines known as '''qubes'''. The operating system is built on top of the [[Xen]] type-1 hypervisor and follows the principle of ''security by compartmentalization''. Qubes assumes that software vulnerabilities are inevitable and therefore aims to contain compromises instead of attempting to prevent every possible attack. Qubes OS is widely regarded as one of the most security-focused desktop operating systems available and is commonly used by security researchers, journalists, developers, privacy advocates, and users operating in high-risk threat environments. == Philosophy == The central philosophy behind Qubes OS is: {{Quote| No software can be trusted completely. }} Instead of treating the entire desktop as one trusted environment, Qubes OS divides activities into isolated domains with different trust levels. Examples include: * A personal qube for private accounts * A work qube for professional activities * An untrusted qube for opening unknown files * An offline vault qube for password managers and cryptographic keys * Disposable qubes for temporary browsing sessions Even if malware compromises one qube, the attacker should not automatically gain access to the rest of the system. == Architecture == Qubes OS uses the [[Xen]] hypervisor to create isolated virtual machines. Each qube has its own: * Filesystem * Running processes * Applications * Network permissions * Memory space Applications from different qubes can appear together on the same desktop while remaining strongly isolated internally. === dom0 === '''dom0''' is the privileged administrative domain responsible for: * Managing qubes * Displaying the graphical desktop * Controlling virtualization * Managing hardware interaction For security reasons, dom0 is intentionally isolated from the internet and networking stacks. Compromising dom0 is considered catastrophic because it controls the entire system. === AppVMs === '''AppVMs''' are standard working qubes used for everyday activities such as: * Web browsing * Messaging * Software development * Office work AppVMs usually inherit software packages from a TemplateVM while storing user data separately. === TemplateVMs === '''TemplateVMs''' provide the root filesystem and installed software for AppVMs. This design offers several advantages: * Reduced disk usage * Simplified updates * Easier rollback and recovery * Consistent environments across qubes Common templates include: * [[Fedora]] * [[Debian]] * Whonix === DisposableVMs === '''DisposableVMs''' are temporary qubes automatically destroyed after use. They are commonly used for: * Opening untrusted attachments * Viewing suspicious PDFs * Temporary browsing sessions * Sandboxed application testing Any malware or persistence mechanisms inside a DisposableVM are erased after shutdown. === NetVMs and ProxyVMs === Networking is isolated into dedicated qubes. '''NetVMs''' handle direct network hardware access, while '''ProxyVMs''' can provide: * Firewalls * VPN routing * Tor integration * Traffic filtering This architecture isolates network drivers and reduces the risk of kernel-level network attacks affecting user qubes. == Security Features == Qubes OS includes numerous advanced security mechanisms. === Strong Isolation === Every qube runs independently with hardware-assisted virtualization provided by Xen. This reduces: * Shared kernel attack surface * Cross-application compromise risks * Privilege escalation opportunities === Color-Coded Trust Levels === Windows are visually marked using colored borders representing trust levels. Examples: * Red — untrusted * Yellow — caution * Green — trusted * Black — highly sensitive This helps users avoid accidentally interacting with malicious or low-trust environments. === USB Isolation === USB controllers and devices can be isolated into dedicated USB qubes. This mitigates attacks involving: * Malicious USB firmware * HID spoofing * DMA attacks * BadUSB exploits === Split GPG === Qubes OS supports ''Split GPG'', where private encryption keys remain isolated inside a dedicated vault qube while other qubes communicate with it securely. This prevents internet-connected applications from directly accessing cryptographic secrets. === Split SSH === SSH agents can also be isolated similarly using ''Split SSH'', protecting authentication keys from compromised development or browsing environments. === Anti-Evil Maid === Qubes historically supported an optional security mechanism called '''Anti Evil Maid''' designed to detect tampering with the boot chain and disk encryption environment. == Networking == Qubes OS supports advanced networking configurations including: * Tor routing through Whonix * VPN chaining * Multi-hop networking * Air-gapped qubes * Firewall rule isolation * Internal-only virtual networks Users can route specific qubes through different networking paths independently. == Whonix Integration == Qubes OS can integrate with '''Whonix''' to provide anonymous networking over Tor. This combination is commonly referred to as '''Qubes-Whonix''' and offers: * Tor isolation * Anonymous browsing * Traffic separation * Reduced IP leakage risks == Hardware Requirements == Due to heavy virtualization usage, Qubes OS has demanding hardware requirements. Recommended specifications include: * 64-bit processor with VT-x or AMD-V * VT-d / AMD-Vi IOMMU support * 16 GB RAM or more * SSD storage * Modern GPU with Xen compatibility Many consumer laptops have partial incompatibilities with Qubes OS. == Security Model == Qubes OS follows the assumption that complete prevention of compromise is impossible. Instead, the operating system focuses on: * Damage containment * Isolation boundaries * Least privilege principles * Trusted Computing Base minimization This approach differs significantly from traditional operating systems which often depend on monolithic trust models. == Limitations == Despite its strong security design, Qubes OS has several limitations. === Complexity === The operating system has a steep learning curve compared to conventional Linux distributions. === Performance Overhead === Running multiple virtual machines simultaneously can consume significant: * RAM * CPU resources * Storage === Hardware Compatibility === Some hardware components may not function correctly due to Xen virtualization limitations. === User Responsibility === Qubes OS improves isolation but cannot fully protect against: * User mistakes * Social engineering * Phishing * Browser fingerprinting * Physical compromise == Use Cases == Qubes OS is commonly used in environments requiring high security or compartmentalization, including: * Malware analysis * Security research * Privacy-sensitive communications * Software development * Cryptocurrency storage * Handling untrusted files == See Also == * [[Xen]] * [[Whonix]] * [[Fedora]] * [[Debian]] * [[Virtualization]] * [[Tor]] == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] cc6d7bd6f57ab1471f9ded30c3e66bcd1ddb7870 0 1145 4764 2026-05-23T02:59:30Z Jokethatcake 333 Created page with "{{DistributionInfobox | title = Parrot OS | image = [[File:ParrotOSlogo.png|thumb]] | caption = The Parrot OS logo | releasestatus = Maintained | releasemodel = Rolling release | basedon = [[Debian]] | packagemanager = APT | defaultdesktops = [[MATE]] | usagetype = Desktop, Security, Development | architectures = x86_64, ARM | init = systemd | license = Free and open-source softw..." wikitext text/x-wiki {{DistributionInfobox | title = Parrot OS | image = [[File:ParrotOSlogo.png|thumb]] | caption = The Parrot OS logo | releasestatus = Maintained | releasemodel = Rolling release | basedon = [[Debian]] | packagemanager = APT | defaultdesktops = [[MATE]] | usagetype = Desktop, Security, Development | architectures = x86_64, ARM | init = systemd | license = Free and open-source software | website = [https://parrotsec.org/ parrotsec.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Privacy]] [[Category:Penetration Testing]] '''Parrot OS''' is a free and open-source Linux distribution focused on cybersecurity, penetration testing, digital forensics, privacy, and software development. It is developed by the '''Parrot Project''' and is based on [[Debian]]. Parrot OS ships with a large collection of security, forensic, cryptography, and privacy-oriented tools while also supporting general desktop usage. The distribution is commonly used by penetration testers, ethical hackers, developers, privacy-conscious users, and students learning cybersecurity. The system aims to provide a balance between security tooling, usability, lightweight performance, and privacy protection. == Overview == Parrot OS is designed as an all-in-one platform for: * Penetration testing * Vulnerability assessment * Digital forensics * Reverse engineering * Privacy protection * Secure development * Anonymous browsing Unlike some security distributions intended purely for offensive testing, Parrot OS also supports daily desktop usage with productivity applications and multimedia support. The default desktop environment is [[MATE]], chosen for its lightweight resource usage and stability. == Editions == Parrot OS is available in multiple editions tailored for different use cases. === Security Edition === The '''Security Edition''' is the flagship version and includes a large collection of offensive security and forensic tools. Common tool categories include: * Network analysis * Web exploitation * Wireless auditing * Reverse engineering * Cryptography * Digital forensics * Malware analysis * OSINT === Home Edition === The '''Home Edition''' removes most offensive security tools and focuses on privacy, development, and general desktop usage. It is intended for users who want: * A privacy-focused Linux desktop * Lightweight performance * Development tools * Secure communication utilities === Architect and Cloud Editions === Parrot also provides minimal and specialized images for: * Servers * Cloud deployments * Containers * Custom installations == Security Features == Parrot OS includes numerous security-oriented technologies and hardening mechanisms. === Sandboxing === Applications can be sandboxed using technologies such as: * Firejail * Linux namespaces * Seccomp This reduces the impact of compromised applications. === Privacy Tools === Parrot OS includes built-in privacy utilities such as: * Tor Browser * OnionShare * AnonSurf * Cryptographic utilities * Secure communication tools === AnonSurf === '''AnonSurf''' is a Parrot-specific utility that routes system traffic through the Tor network. It allows users to anonymize internet traffic system-wide while helping reduce direct IP exposure. === Cryptography Support === The distribution includes extensive cryptographic tooling for: * File encryption * Secure communication * Key management * Password auditing * Digital signatures == Penetration Testing == Parrot OS includes a large collection of penetration testing frameworks and utilities. Examples include: * Metasploit Framework * Burp Suite * Nmap * Wireshark * Aircrack-ng * Hydra * SQLMap * John the Ripper These tools are intended for authorized security testing and research. == Digital Forensics == Parrot OS includes forensic and incident response utilities used for: * File recovery * Memory analysis * Metadata extraction * Disk analysis * Malware investigation This makes the distribution useful for both offensive and defensive security workflows. == Development == Parrot OS supports software development with preinstalled or easily available tools for: * Python * C and C++ * Java * Docker * Git * Virtualization * Reverse engineering The distribution is commonly used by developers working in security research and exploit development. == System Requirements == Parrot OS is relatively lightweight compared to many security distributions. Typical minimum requirements include: * 64-bit processor * 2 GB RAM minimum * 20 GB storage * Internet connection for updates Recommended specifications are significantly higher for virtualization or heavy penetration testing workloads. == Package Management == Parrot OS uses the APT package manager inherited from [[Debian]]. Software can be installed through: * apt * Synaptic * Parrot repositories * Flatpak support The distribution follows a rolling release model with continuously updated packages. == Containers and Virtualization == Parrot OS supports: * Docker * Podman * KVM * VirtualBox * QEMU Security researchers often run Parrot OS inside isolated virtual environments for testing and analysis. == Comparison with Kali Linux == Parrot OS is frequently compared with [[Kali Linux]]. Differences commonly noted include: * Lighter default resource usage * Stronger emphasis on privacy tools * More suitable daily desktop experience * Different package selection and defaults Both distributions are widely used in cybersecurity environments. == Criticism == Common criticisms of Parrot OS include: * Large attack surface due to included tools * Rolling release instability risks * Potential misuse by inexperienced users * Security misconceptions among beginners Installing penetration testing tools alone does not make a system secure. == Use Cases == Parrot OS is commonly used for: * Ethical hacking * Cybersecurity education * Capture The Flag competitions * Privacy-focused desktop computing * Malware research * Secure development environments == See Also == * [[Debian]] * [[Kali Linux]] * [[Linux]] * [[Digital Forensics]] * [[Penetration Testing]] * [[Tor]] == External Links == * [https://parrotsec.org/ Official website] * [https://docs.parrotsec.org/ Official documentation] * [https://github.com/ParrotSec ParrotSec GitHub] 213b123cacdbb6e68533860def41d9ca3073b6ec 0 1146 4765 2026-05-23T03:00:37Z Jokethatcake 333 Created page with "{{SoftwareInfobox | title = Tor | image = [[File:TorLogo.png|thumb]] | caption = The Tor Project logo | developer = The Tor Project | initialrelease = 2002 | releasestatus = Maintained | programminglanguage = C, Rust, Python | operatingsystems = Linux, Windows, macOS, Android | license = Free and open-source software | website = [https://www.torproject.org/ torproject.org] }} [[Category:Privacy]] Ca..." wikitext text/x-wiki {{SoftwareInfobox | title = Tor | image = [[File:TorLogo.png|thumb]] | caption = The Tor Project logo | developer = The Tor Project | initialrelease = 2002 | releasestatus = Maintained | programminglanguage = C, Rust, Python | operatingsystems = Linux, Windows, macOS, Android | license = Free and open-source software | website = [https://www.torproject.org/ torproject.org] }} [[Category:Privacy]] [[Category:Security]] [[Category:Networking]] [[Category:Free Software]] '''Tor''' (short for '''The Onion Router''') is a free and open-source anonymity network designed to protect users' privacy and resist traffic analysis and surveillance. Tor routes internet traffic through multiple volunteer-operated relays, concealing a user's IP address and helping anonymize network activity. Tor is developed and maintained by '''The Tor Project''', a nonprofit organization focused on privacy, freedom of expression, and online anonymity. Tor is widely used by: * Privacy-conscious users * Journalists * Activists * Researchers * Whistleblowers * Users in censored regions It is also used for anonymous hosting through Tor hidden services, now commonly known as '''Onion Services'''. == Overview == Tor works by routing internet traffic through a decentralized network of relays operated by volunteers around the world. Instead of connecting directly to a destination server, Tor encrypts traffic multiple times and forwards it through several randomly selected relays before reaching the final destination. This process helps obscure: * User identity * Source IP address * Browsing activity * Physical location Tor is designed primarily to defend against: * Traffic analysis * Network surveillance * ISP monitoring * Censorship * Location tracking == Onion Routing == Tor uses a technique called '''onion routing'''. Traffic is encrypted in multiple layers, similar to the layers of an onion. A Tor circuit typically consists of: # Entry Guard # Middle Relay # Exit Relay Each relay only knows: * The previous node * The next node No single relay knows both the origin and final destination simultaneously. === Entry Guard === The '''Entry Guard''' is the first relay in the Tor circuit. It knows the user's IP address but does not know the final destination of the traffic. Tor intentionally keeps the same guard for extended periods to reduce exposure to malicious entry relays. === Middle Relay === The middle relay forwards encrypted traffic between nodes. It does not know either the user's IP address or the final destination. === Exit Relay === The exit relay decrypts the final layer and forwards traffic to the destination website. The exit relay can see outgoing non-encrypted traffic if HTTPS is not used. Because of this, HTTPS remains important when using Tor. == Onion Services == Tor supports anonymous services accessible through ''.onion'' domains. These are known as '''Onion Services''' and allow servers to hide their physical IP addresses. Advantages include: * Anonymous hosting * Resistance to censorship * No public IP exposure * End-to-end Tor routing Onion Services are used for: * Secure communication platforms * Anonymous publishing * Whistleblowing systems * Privacy-preserving websites == Tor Browser == '''Tor Browser''' is the most common way users access the Tor network. It is based on Mozilla Firefox and includes privacy-focused modifications such as: * Anti-fingerprinting protections * Script restrictions * HTTPS-Only mode * Tracking protection * Isolated browsing sessions Tor Browser is designed to make all users appear as similar as possible in order to reduce browser fingerprinting. == Bridges == Some governments and ISPs attempt to block Tor traffic. To bypass censorship, Tor supports '''bridges'''. Bridges are unpublished relays that help users connect to the network even when standard Tor nodes are blocked. Types of bridges include: * obfs4 * Snowflake * meek === Snowflake === '''Snowflake''' uses volunteer-operated browser proxies to help censored users access Tor. It is designed to make blocking more difficult by leveraging temporary peer-to-peer proxies. == Security and Privacy == Tor provides strong anonymity protections but is not considered perfect anonymity. Security depends on: * User behavior * Browser configuration * Endpoint security * Operational security practices Tor helps protect against many forms of surveillance but cannot automatically prevent all tracking methods. === Fingerprinting === Browser fingerprinting can still threaten anonymity. Tor Browser mitigates this by standardizing: * Fonts * Window sizes * Rendering behavior * Browser APIs === Traffic Correlation === A sufficiently powerful adversary observing both ends of a connection may attempt traffic correlation attacks. This remains one of the primary theoretical threats to anonymity networks. === Malicious Exit Nodes === Exit relays can inspect unencrypted traffic. Users are strongly encouraged to use HTTPS and avoid transmitting sensitive plaintext information. == Performance == Tor is generally slower than direct internet connections because traffic travels through multiple relays worldwide. Performance may vary depending on: * Relay congestion * Geographic routing * Circuit quality * Network censorship Latency-sensitive applications such as gaming are usually unsuitable over Tor. == Legal Status == Using Tor is legal in many countries, though some governments attempt to restrict or monitor its use. Tor itself is a legitimate privacy tool and is widely used for lawful purposes including: * Circumventing censorship * Protecting journalist communications * Research * Anonymous publishing However, the network has also been used for illegal activities due to its anonymity features. == Criticism == Common criticisms of Tor include: * Slow network speeds * Abuse by malicious actors * Exit node monitoring risks * Blocking by some websites * False assumptions of complete anonymity Using Tor alone does not guarantee total anonymity. == Use Cases == Tor is commonly used for: * Anonymous web browsing * Circumventing censorship * Secure communications * Protecting metadata privacy * Research in hostile environments * Anonymous publishing == See Also == * [[Tor Browser]] * [[Onion Routing]] * [[Whonix]] * [[Tails]] * [[I2P]] * [[VPN]] == References == * [https://www.torproject.org/ Official website] * [https://tb-manual.torproject.org/ Tor Browser Manual] * [https://support.torproject.org/ Tor Support Portal] * Dingledine, Roger; Mathewson, Nick; Syverson, Paul. ''Tor: The Second-Generation Onion Router''. * [https://gitlab.torproject.org/ The Tor Project GitLab] == External Links == * [https://www.torproject.org/download/ Download Tor Browser] * [https://metrics.torproject.org/ Tor Metrics] e1429aadd80122f2460d6d8d4a9093f9b913dfde 4766 4765 2026-05-23T03:01:37Z Jokethatcake 333 wikitext text/x-wiki {{SoftwareInfobox | title = Tor | image = TorLogo.png | caption = The Tor Project logo | developer = The Tor Project | releasestatus = Maintained | website = https://www.torproject.org/ }} [[Category:Privacy]] [[Category:Security]] [[Category:Networking]] [[Category:Free Software]] '''Tor''' (The Onion Router) is a free and open-source anonymity network designed to protect user privacy and resist surveillance, tracking, and censorship on the internet. Tor routes internet traffic through multiple volunteer-operated relays around the world, making it significantly more difficult to trace a user's activity or determine their real IP address. The project is developed by '''The Tor Project''', a nonprofit organization focused on online privacy, anonymity, and freedom of information. == Overview == Tor uses a system known as '''onion routing'''. Instead of connecting directly to a website or service, traffic is encrypted and passed through several relays before reaching its destination. A normal Tor circuit usually consists of: # Entry Guard # Middle Relay # Exit Relay Each relay only knows the previous and next node in the chain. This architecture helps prevent a single relay from knowing both: * who the user is * and where the traffic is going == Onion Routing == Tor encrypts data in multiple layers similar to the layers of an onion. Each relay decrypts only one layer before forwarding the traffic to the next relay. Benefits include: * IP address hiding * Resistance to surveillance * Reduced tracking * Circumvention of censorship * Metadata protection == Tor Browser == '''Tor Browser''' is the most common application used to access the Tor network. It is based on Mozilla Firefox and includes additional privacy protections such as: * Anti-fingerprinting features * HTTPS-only mode * Tracking protection * Script restrictions * Isolated browsing sessions Tor Browser attempts to make users appear similar to each other in order to reduce browser fingerprinting attacks. == Onion Services == Tor supports anonymous websites and services using ''.onion'' domains. These are known as '''Onion Services'''. Unlike normal websites, Onion Services hide the server's real IP address and remain fully inside the Tor network. Common uses include: * anonymous communication * whistleblowing platforms * privacy-focused services * censorship-resistant publishing == Bridges == Some countries and internet providers block access to Tor. To bypass censorship, Tor supports '''bridges'''. Bridges are special relays not publicly listed in the main Tor directory. Common bridge technologies include: * obfs4 * Snowflake * meek === Snowflake === '''Snowflake''' uses temporary volunteer-operated proxies to help censored users connect to Tor. This makes large-scale blocking more difficult. == Security == Tor is designed to defend against: * traffic analysis * ISP monitoring * censorship * mass surveillance * location tracking However, Tor does not guarantee complete anonymity. User behavior, browser exploits, malware, phishing, and operational security mistakes can still compromise privacy. === Exit Relay Risks === The exit relay decrypts the final layer before traffic reaches the destination website. Because of this: * non-HTTPS traffic may be visible to the exit operator * HTTPS remains important while using Tor === Traffic Correlation === A powerful adversary capable of monitoring both the user's connection and the destination server may attempt correlation attacks. This remains one of the main theoretical weaknesses of anonymity networks. == Performance == Tor is generally slower than normal internet connections because traffic travels through multiple relays across different countries. Performance depends on: * relay congestion * network distance * censorship * circuit quality Applications requiring very low latency may perform poorly over Tor. == Use Cases == Tor is commonly used for: * anonymous browsing * bypassing censorship * privacy protection * secure communications * journalism * research * whistleblowing == Criticism == Tor is sometimes criticized for: * slow speeds * abuse by malicious actors * website blocking * misconceptions about "perfect anonymity" Using Tor alone does not automatically make a user anonymous. == See Also == * [[Tor Browser]] * [[Onion Routing]] * [[Whonix]] * [[Tails]] * [[I2P]] * [[VPN]] == References == * https://www.torproject.org/ * https://tb-manual.torproject.org/ * https://support.torproject.org/ == External Links == * https://www.torproject.org/download/ * https://metrics.torproject.org/ 7808b769c4a56a17369c5cc27adae031402e3a57 0 1147 4767 2026-05-23T03:04:00Z Jokethatcake 333 Created page with "{{SoftwareInfobox | title = Xen | image = XenLogo.png | caption = The Xen Project logo | developer = The Xen Project | releasestatus = Maintained | website = https://xenproject.org/ }} [[Category:Virtualization]] [[Category:Hypervisors]] [[Category:Free Software]] [[Category:Security]] '''Xen''' is a free and open-source type-1 hypervisor used for virtualization, isolation, and cloud computing. It allows multiple operating systems to run simultaneously on the same phys..." wikitext text/x-wiki {{SoftwareInfobox | title = Xen | image = XenLogo.png | caption = The Xen Project logo | developer = The Xen Project | releasestatus = Maintained | website = https://xenproject.org/ }} [[Category:Virtualization]] [[Category:Hypervisors]] [[Category:Free Software]] [[Category:Security]] '''Xen''' is a free and open-source type-1 hypervisor used for virtualization, isolation, and cloud computing. It allows multiple operating systems to run simultaneously on the same physical hardware while remaining isolated from each other. Xen is widely used in: * cloud infrastructure * server virtualization * security-focused systems * research environments * enterprise platforms The hypervisor is known for its strong isolation model, lightweight design, and use in security-oriented operating systems such as [[Qubes OS]]. == Overview == Xen runs directly on hardware as a '''bare-metal hypervisor'''. Unlike traditional hosted virtualization software that runs on top of another operating system, Xen operates beneath guest operating systems and controls: * CPU scheduling * memory isolation * device access * virtual machine management Operating systems running under Xen are called '''domains''' or '''VMs'''. == Architecture == Xen separates the system into multiple isolated domains. === Hypervisor === The Xen hypervisor is the lowest privileged software layer running directly above the hardware. Its responsibilities include: * memory management * CPU virtualization * interrupt handling * VM scheduling * isolation enforcement The hypervisor itself is intentionally minimal to reduce attack surface. === dom0 === '''dom0''' is the privileged management domain started during boot. It typically runs Linux and has direct hardware access. Responsibilities include: * creating and destroying VMs * hardware driver management * device control * VM configuration * toolstack management Compromise of dom0 may compromise the entire system. === domU === Unprivileged guest virtual machines are known as '''domU''' domains. These domains operate independently and are isolated from each other by the hypervisor. A domU may run: * Linux * Windows * BSD systems * specialized operating systems == Virtualization Types == Xen supports multiple virtualization methods. === Paravirtualization === '''Paravirtualization''' (PV) modifies the guest operating system to communicate efficiently with the hypervisor. Advantages include: * lower overhead * improved performance * efficient resource usage However, the guest OS must support Xen-specific modifications. === Hardware Virtualization == Xen also supports full virtualization using modern CPU extensions such as: * Intel VT-x * AMD-V This allows unmodified operating systems to run as guests. === PVH and HVM === Modern Xen systems commonly use: * HVM (Hardware Virtual Machine) * PVH (Paravirtualized Hardware) These modes combine hardware virtualization with paravirtualized optimizations. == Security == Xen is heavily used in security-focused environments because of its strong isolation model. Security features include: * hardware-assisted isolation * memory separation * independent virtual machines * reduced shared kernel attack surface The hypervisor design attempts to minimize the Trusted Computing Base. === Isolation === Each virtual machine operates in a separate memory space. A compromised guest should not normally gain access to other guests or the hypervisor itself. === Device Isolation === Hardware devices may be assigned to dedicated domains. This allows separation of: * networking * USB controllers * GPUs * storage devices Operating systems such as [[Qubes OS]] use Xen to isolate potentially dangerous hardware components. == Memory Management == Xen provides advanced memory virtualization features including: * ballooning * dynamic memory allocation * memory sharing * NUMA awareness The hypervisor strictly controls guest memory access. == CPU Scheduling == Xen includes multiple schedulers designed for: * low latency * server workloads * virtualization density * real-time systems CPU resources can be shared or pinned between guests. == Networking == Virtual machines communicate through virtual network interfaces managed by dom0. Xen supports: * virtual bridges * NAT networking * isolated internal networks * VLAN integration * software-defined networking == Storage == Xen supports multiple storage backends including: * raw disk images * LVM volumes * network storage * iSCSI * NFS * Ceph Virtual disks may be dynamically attached or detached from guests. == Xen Project == The '''Xen Project''' is the collaborative open-source project maintaining Xen. Many companies contribute to Xen development including organizations involved in: * cloud computing * enterprise virtualization * embedded systems * security research == Use Cases == Xen is commonly used for: * cloud hosting * server consolidation * virtual private servers * security compartmentalization * malware analysis * enterprise virtualization * research environments Major cloud providers historically used Xen extensively for infrastructure virtualization. == Comparison with Other Hypervisors == Xen is often compared with: * KVM * VMware ESXi * Hyper-V * VirtualBox Compared to hosted virtualization platforms, Xen provides stronger low-level isolation and direct hardware control. == Limitations == Common criticisms of Xen include: * complex configuration * hardware compatibility issues * dependency on dom0 * steeper learning curve * smaller desktop ecosystem compared to KVM == See Also == * [[Qubes OS]] * [[Virtualization]] * [[Hypervisor]] * [[KVM]] * [[Linux]] == References == * https://xenproject.org/ * https://wiki.xenproject.org/ * https://xenbits.xenproject.org/docs/ == External Links == * https://github.com/xen-project * https://wiki.xenproject.org/wiki/Main_Page 43165bb48823d669e64d2be73fa47c01c361ae6f 4768 4767 2026-05-23T03:05:05Z Jokethatcake 333 wikitext text/x-wiki {{SoftwareInfobox | title = Xen | website = https://xenproject.org/ }} [[Category:Virtualization]] [[Category:Hypervisors]] [[Category:Free Software]] [[Category:Security]] '''Xen''' is a free and open-source type-1 hypervisor used for virtualization and isolation. It allows multiple operating systems to run simultaneously on the same physical machine while remaining isolated from each other. Xen runs directly on hardware instead of running on top of another operating system. Because of this, it is commonly referred to as a '''bare-metal hypervisor'''. The project is maintained by the '''Xen Project''' and is widely used in: * cloud infrastructure * enterprise virtualization * security-focused systems * research environments * server hosting Xen is also heavily used by security-oriented operating systems such as [[Qubes OS]]. == Overview == Xen creates isolated virtual machines known as '''domains'''. Each domain operates independently with separate: * memory * processes * virtual hardware * permissions This isolation helps improve: * security * workload separation * resource management * fault containment A compromised virtual machine should not normally compromise other virtual machines running on the same host. == Architecture == Xen uses a layered architecture. === Hypervisor === The Xen hypervisor is the lowest software layer running directly above the hardware. Responsibilities include: * CPU scheduling * memory management * interrupt handling * virtualization control * isolation enforcement The hypervisor itself is intentionally minimal in order to reduce attack surface. === dom0 === '''dom0''' is the privileged management domain automatically started during boot. It has direct hardware access and is responsible for: * managing virtual machines * controlling devices * handling drivers * configuring networking * storage management Compromise of dom0 may compromise the entire system. === domU === Regular guest virtual machines are known as '''domU''' domains. domU systems are isolated from one another by the hypervisor. A domU may run: * Linux * Windows * BSD systems * specialized operating systems == Virtualization Modes == Xen supports multiple virtualization technologies. === Paravirtualization === '''Paravirtualization''' modifies the guest operating system to communicate efficiently with the hypervisor. Advantages include: * lower overhead * improved performance * reduced emulation However, the guest operating system must support Xen-aware modifications. === Hardware Virtualization === Modern Xen systems commonly use hardware-assisted virtualization through: * Intel VT-x * AMD-V This allows unmodified operating systems to run as guests. === PVH and HVM === Xen also supports: * HVM (Hardware Virtual Machine) * PVH (Paravirtualized Hardware) These combine hardware virtualization with optimized paravirtualized components. == Security == Xen is widely respected for its strong isolation model. Security features include: * hardware-assisted isolation * independent guest memory spaces * virtual machine separation * reduced shared kernel attack surface === Isolation === Each virtual machine operates independently. Memory access between guests is strictly controlled by the hypervisor. === Device Separation === Hardware devices can be isolated into separate domains. Examples include: * USB controllers * networking hardware * GPUs * storage devices This approach is heavily used in [[Qubes OS]] to isolate potentially dangerous hardware components. == Networking == Xen supports virtualized networking through: * virtual bridges * NAT * VLANs * isolated internal networks Virtual machines may communicate internally or externally depending on configuration. == Storage == Xen supports multiple storage backends including: * raw disk images * LVM * network storage * iSCSI * NFS Virtual disks may be dynamically attached or detached from running guests. == Use Cases == Xen is commonly used for: * cloud computing * virtual private servers * security compartmentalization * malware analysis * enterprise virtualization * infrastructure hosting Large-scale cloud providers historically used Xen extensively for virtualization infrastructure. == Comparison with Other Hypervisors == Xen is often compared with: * KVM * VMware ESXi * Hyper-V * VirtualBox Compared to hosted virtualization software, Xen provides stronger low-level isolation and direct hardware control. == Limitations == Common criticisms of Xen include: * complex configuration * dependency on dom0 * hardware compatibility issues * steep learning curve == See Also == * [[Qubes OS]] * [[Virtualization]] * [[Hypervisor]] * [[KVM]] * [[Linux]] == References == * https://xenproject.org/ * https://wiki.xenproject.org/ * https://xenbits.xenproject.org/docs/ == External Links == * https://github.com/xen-project * https://wiki.xenproject.org/wiki/Main_Page b6a56399e35fc21a4926ce314483e7e23c3aadd2 4769 4768 2026-05-23T03:05:58Z Jokethatcake 333 wikitext text/x-wiki '''Xen''' is a free and open-source type-1 hypervisor used for virtualization and isolation. It allows multiple operating systems to run simultaneously on the same physical machine while remaining isolated from each other. [[Category:Virtualization]] [[Category:Hypervisors]] [[Category:Free Software]] [[Category:Security]] == Overview == Xen runs directly on hardware instead of on top of another operating system. Because of this, it is considered a '''bare-metal hypervisor'''. The project is maintained by the '''Xen Project''' and is commonly used in: * cloud computing * enterprise virtualization * security-focused systems * server hosting * research environments Xen is also heavily used by [[Qubes OS]] for strong compartmentalization and isolation. == Architecture == Xen separates the system into multiple isolated virtual machines called '''domains'''. Each domain has separate: * memory * processes * permissions * virtual hardware This design improves: * security * workload separation * fault isolation === Hypervisor === The Xen hypervisor is the lowest software layer running directly above the hardware. Its responsibilities include: * CPU scheduling * memory isolation * interrupt handling * virtualization control The hypervisor itself is intentionally minimal in order to reduce attack surface. === dom0 === '''dom0''' is the privileged management domain started during boot. It has direct hardware access and is responsible for: * creating virtual machines * device management * storage management * networking configuration Compromise of dom0 may compromise the entire system. === domU === Regular guest virtual machines are known as '''domU''' domains. domU systems are isolated from one another by the hypervisor. A domU may run: * Linux * Windows * BSD systems * other operating systems == Virtualization Modes == Xen supports multiple virtualization technologies. === Paravirtualization === '''Paravirtualization''' modifies the guest operating system to communicate directly with the hypervisor. Advantages include: * lower overhead * better performance * reduced emulation === Hardware Virtualization === Xen also supports hardware-assisted virtualization through: * Intel VT-x * AMD-V This allows unmodified operating systems to run as guests. == Security == Xen is widely respected for its strong isolation model. Security features include: * hardware-assisted isolation * memory separation * reduced shared kernel attack surface * independent virtual machines === Device Isolation === Hardware devices may be assigned to isolated domains. Examples include: * USB controllers * network hardware * storage devices This approach is heavily used in [[Qubes OS]]. == Networking == Xen supports: * virtual bridges * NAT networking * isolated virtual networks * VLAN integration Virtual machines may communicate internally or externally depending on configuration. == Storage == Supported storage backends include: * raw disk images * LVM * iSCSI * NFS * network storage == Use Cases == Xen is commonly used for: * cloud infrastructure * virtual private servers * malware analysis * enterprise virtualization * security compartmentalization == Limitations == Common criticisms of Xen include: * complex configuration * hardware compatibility issues * dependency on dom0 * steep learning curve == See Also == * [[Qubes OS]] * [[Virtualization]] * [[Hypervisor]] * [[KVM]] == References == * https://xenproject.org/ * https://wiki.xenproject.org/ * https://xenbits.xenproject.org/docs/ 483fdfaeef5d387cfc1f01523e510edeb830c6da 0 1148 4770 2026-05-23T03:08:04Z Jokethatcake 333 Created page with "'''Whonix''' is a free and open-source privacy-focused operating system designed to provide strong anonymity and security through the [[Tor]] network. [[Category:Privacy]] [[Category:Security]] [[Category:Linux Distributions]] [[Category:Tor]] Whonix is based on [[Debian]] and is designed to run inside virtual machines. The operating system separates networking and user applications into isolated virtual machines in order to reduce information leaks and improve anonymi..." wikitext text/x-wiki '''Whonix''' is a free and open-source privacy-focused operating system designed to provide strong anonymity and security through the [[Tor]] network. [[Category:Privacy]] [[Category:Security]] [[Category:Linux Distributions]] [[Category:Tor]] Whonix is based on [[Debian]] and is designed to run inside virtual machines. The operating system separates networking and user applications into isolated virtual machines in order to reduce information leaks and improve anonymity. The project is commonly used by: * privacy-conscious users * journalists * activists * researchers * whistleblowers * security enthusiasts == Overview == Whonix uses a two-VM architecture designed to isolate network traffic from user applications. The system consists of: # '''Whonix-Gateway''' # '''Whonix-Workstation''' All internet traffic from the workstation is forced through the gateway and routed over the Tor network. This design helps prevent accidental IP leaks and improves separation between applications and networking components. == Architecture == === Whonix-Gateway === '''Whonix-Gateway''' is responsible for handling all network communication. Features include: * Tor routing * traffic isolation * firewalling * DNS protection The gateway acts as an intermediary between the internet and the workstation. Applications are not normally run inside the gateway VM. === Whonix-Workstation === '''Whonix-Workstation''' is the environment where users perform daily activities. Examples include: * web browsing * messaging * file management * development * document editing The workstation has no direct internet connection and communicates only through the gateway VM. Even if the workstation becomes compromised, the attacker's ability to discover the user's real IP address may still be limited. == Tor Integration == Whonix forces all network traffic through the [[Tor]] network. Benefits include: * IP address concealment * censorship circumvention * resistance to surveillance * reduced metadata exposure The operating system is specifically designed to reduce the risk of: * DNS leaks * direct connections * application misconfiguration == Security == Whonix focuses heavily on compartmentalization and isolation. Security features include: * VM separation * forced Tor routing * isolation of networking components * hardened configuration defaults === Stream Isolation === Whonix supports Tor stream isolation techniques which separate application traffic streams. This helps reduce cross-application correlation. === Leak Prevention === The operating system includes protections against: * DNS leaks * direct IP leaks * accidental clearnet traffic * some forms of metadata exposure === Isolation === Whonix relies heavily on virtualization for isolation. It is commonly used with: * VirtualBox * KVM * [[Qubes OS]] === Qubes-Whonix === Whonix can integrate with [[Qubes OS]]. This setup is commonly known as '''Qubes-Whonix''' and combines: * Xen-based compartmentalization * Tor isolation * virtual machine separation The combination is widely regarded as one of the strongest publicly available desktop anonymity environments. == Applications == Whonix commonly includes or supports: * Tor Browser * encrypted messaging applications * cryptographic utilities * privacy-focused Linux software Users may also install additional Debian packages using APT. == Use Cases == Whonix is commonly used for: * anonymous browsing * bypassing censorship * secure communication * privacy research * journalism * whistleblowing * malware analysis == Limitations == Whonix improves anonymity but does not guarantee perfect anonymity. Limitations include: * browser fingerprinting * user mistakes * malware * phishing * operational security failures * traffic correlation attacks Virtual machine escape vulnerabilities may also affect security. == Performance == Because all traffic passes through the Tor network and virtualization layers, Whonix may experience: * increased latency * slower internet speeds * reduced performance compared to normal systems == Comparison with Tails == Whonix is often compared with [[Tails]]. Differences include: * Whonix is virtualization-focused * Tails is a live operating system * Whonix emphasizes persistent VM isolation * Tails focuses on amnesic sessions == See Also == * [[Tor]] * [[Qubes OS]] * [[Tails]] * [[Debian]] * [[Virtualization]] == References == * https://www.whonix.org/ * https://www.whonix.org/wiki/Documentation * https://forums.whonix.org/ == External Links == * https://www.whonix.org/wiki/Main_Page * https://github.com/Whonix ed2810f64cad9ea037ad37f48ed7b4d6d135fbb5 0 1149 4771 2026-05-23T03:08:53Z Jokethatcake 333 Created page with "'''Tails''' (The Amnesic Incognito Live System) is a free and open-source privacy-focused Linux distribution designed to preserve anonymity and reduce digital traces. [[Category:Privacy]] [[Category:Security]] [[Category:Linux Distributions]] [[Category:Tor]] Tails is based on [[Debian]] and routes all internet traffic through the [[Tor]] network by default. The operating system is designed to run as a live system from removable media such as USB drives without leaving..." wikitext text/x-wiki '''Tails''' (The Amnesic Incognito Live System) is a free and open-source privacy-focused Linux distribution designed to preserve anonymity and reduce digital traces. [[Category:Privacy]] [[Category:Security]] [[Category:Linux Distributions]] [[Category:Tor]] Tails is based on [[Debian]] and routes all internet traffic through the [[Tor]] network by default. The operating system is designed to run as a live system from removable media such as USB drives without leaving traces on the host computer. Tails is commonly used by: * journalists * activists * whistleblowers * researchers * privacy-conscious users * users in censored regions == Overview == Tails is designed around two major goals: * anonymity * amnesia The system attempts to anonymize network traffic through Tor while minimizing traces left on the computer after shutdown. Unlike traditional operating systems, Tails is typically booted from a USB drive and runs entirely as a live environment. By default, data stored in memory is erased when the system powers off. == Live System == Tails operates primarily as a live operating system. Advantages include: * portability * reduced forensic traces * temporary sessions * hardware independence The system can run on many x86_64 computers without installation to internal storage. == Tor Integration == All internet traffic in Tails is routed through the [[Tor]] network. If an application attempts to access the internet outside of Tor, the connection is blocked by the system firewall. Benefits include: * IP address concealment * censorship circumvention * resistance to tracking * metadata reduction === Tor Browser === Tails includes '''Tor Browser''' as its default web browser. The browser includes protections against: * browser fingerprinting * trackers * unsafe scripts * insecure connections == Amnesia == The term ''amnesic'' refers to the system's design goal of leaving minimal traces after shutdown. By default, Tails: * does not write user activity to disk * clears memory on shutdown * avoids persistent local storage This helps reduce forensic recovery risks. == Persistent Storage == Tails optionally supports encrypted persistent storage on the USB device. Persistent storage may be used for: * documents * browser bookmarks * GPG keys * additional software * cryptocurrency wallets The storage is encrypted using Linux Unified Key Setup (LUKS). == Security == Tails includes numerous security and privacy protections. === Memory Protections === Tails attempts to clear sensitive memory contents during shutdown to reduce cold boot attack risks. === MAC Address Spoofing === The operating system can spoof MAC addresses to reduce hardware-based tracking on local networks. === Sandboxing === Some applications inside Tails use sandboxing technologies to reduce attack surface. === Root Access === Administrative privileges are disabled by default for normal use. This reduces accidental system modification and some attack vectors. == Included Applications == Tails includes many privacy-focused applications such as: * Tor Browser * Thunderbird * KeePassXC * OnionShare * GnuPG * Electrum The distribution focuses on secure defaults and privacy-oriented tooling. == Use Cases == Tails is commonly used for: * anonymous browsing * bypassing censorship * secure communication * whistleblowing * investigative journalism * temporary secure environments == Limitations == Tails improves privacy but does not guarantee complete anonymity. Risks still include: * phishing * browser exploits * operational security mistakes * malicious downloads * hardware compromise * traffic correlation attacks Using personal accounts or revealing identifying information may also compromise anonymity. == Performance == Because all internet traffic passes through the Tor network, Tails may experience: * slower browsing speeds * increased latency * reduced download performance Running from USB media may also reduce system responsiveness compared to installed operating systems. == Comparison with Whonix == Tails is often compared with [[Whonix]]. Differences include: * Tails is a live operating system * Whonix is virtualization-based * Tails focuses on temporary amnesic sessions * Whonix emphasizes VM isolation and persistence == See Also == * [[Tor]] * [[Whonix]] * [[Debian]] * [[Privacy]] * [[Linux]] == References == * https://tails.net/ * https://tails.net/doc/ * https://gitlab.tails.boum.org/tails/tails == External Links == * https://tails.net/install/ * https://tails.net/support/ 6a5e6a922abb31b764c21f8a8c52993127e45f4d 0 1150 4772 2026-05-23T03:09:35Z Jokethatcake 333 Created page with "'''Virtualization''' is the process of creating virtual versions of computing resources such as operating systems, servers, storage devices, networks, or hardware platforms. It allows multiple isolated environments to run on a single physical machine. [[Category:Virtualization]] [[Category:Computing]] [[Category:Security]] Virtualization is widely used in: * cloud computing * server infrastructure * software testing * cybersecurity * desktop environments * research sy..." wikitext text/x-wiki '''Virtualization''' is the process of creating virtual versions of computing resources such as operating systems, servers, storage devices, networks, or hardware platforms. It allows multiple isolated environments to run on a single physical machine. [[Category:Virtualization]] [[Category:Computing]] [[Category:Security]] Virtualization is widely used in: * cloud computing * server infrastructure * software testing * cybersecurity * desktop environments * research systems The technology improves hardware utilization, scalability, isolation, portability, and resource management. == Overview == In a virtualized environment, software known as a '''hypervisor''' manages and allocates hardware resources to multiple virtual machines. Each virtual machine behaves similarly to an independent physical computer and may run its own: * operating system * applications * networking stack * storage environment Virtualization allows different operating systems to coexist simultaneously on the same hardware. == Hypervisors == A '''hypervisor''' is software responsible for creating and managing virtual machines. There are two major types of hypervisors. === Type-1 Hypervisors === Type-1 hypervisors run directly on hardware and are also known as '''bare-metal hypervisors'''. Examples include: * [[Xen]] * VMware ESXi * Hyper-V Advantages include: * strong isolation * lower overhead * enterprise scalability * direct hardware access === Type-2 Hypervisors === Type-2 hypervisors run on top of an existing operating system. Examples include: * VirtualBox * VMware Workstation * QEMU Advantages include: * easier setup * desktop usability * convenient testing environments However, they generally have more overhead than type-1 hypervisors. == Virtual Machines == A '''virtual machine''' (VM) is an isolated software-defined computer running inside a virtualized environment. Each VM typically contains: * a guest operating system * virtual hardware * memory allocation * storage devices * network interfaces Virtual machines can usually be started, paused, cloned, exported, or deleted independently. == Hardware Virtualization == Modern virtualization often relies on CPU extensions such as: * Intel VT-x * AMD-V These technologies improve: * performance * hardware isolation * virtualization efficiency Additional technologies such as IOMMU support enable secure device passthrough. == Device Passthrough == Device passthrough allows physical hardware devices to be assigned directly to virtual machines. Examples include: * GPUs * USB controllers * network adapters * storage controllers This improves compatibility and performance while also enabling stronger hardware isolation. == Networking == Virtualization platforms support multiple networking models. Common configurations include: * NAT * bridged networking * host-only networking * isolated internal networks Virtual networking enables communication between virtual machines and external systems. == Storage == Virtual machines commonly use virtual disk images. Supported storage methods include: * raw images * QCOW2 * VHD * VMDK * LVM * network storage Snapshots allow virtual machine states to be saved and restored. == Snapshots == Snapshots capture the current state of a virtual machine. They are commonly used for: * testing * rollback * malware analysis * development environments Snapshots help restore systems quickly after failure or compromise. == Containers == Containers are another form of virtualization focused on operating-system-level isolation. Unlike full virtual machines, containers share the host kernel. Popular container technologies include: * Docker * LXC * Podman Containers are generally lighter and faster than traditional virtual machines. == Security == Virtualization can improve security through isolation and compartmentalization. Common security applications include: * malware analysis * sandboxing * workload separation * secure testing environments Operating systems such as [[Qubes OS]] heavily rely on virtualization for security isolation. === VM Escapes === A '''VM escape''' occurs when malicious software breaks out of a virtual machine and compromises the host system or other guests. Although rare, VM escapes are considered serious security vulnerabilities. === Sandboxing === Virtual machines are often used as sandboxes for: * untrusted software * exploit testing * reverse engineering * suspicious files == Cloud Computing == Virtualization is a foundational technology behind cloud computing platforms. Cloud providers use virtualization to: * allocate resources dynamically * isolate customers * improve scalability * deploy infrastructure rapidly == Advantages == Benefits of virtualization include: * improved hardware utilization * workload isolation * portability * scalability * simplified backups * rapid deployment == Limitations == Common disadvantages include: * performance overhead * increased complexity * hardware compatibility issues * resource consumption Security vulnerabilities in hypervisors may also affect multiple virtual machines simultaneously. == Use Cases == Virtualization is commonly used for: * cloud infrastructure * software testing * cybersecurity research * server consolidation * desktop virtualization * development environments == See Also == * [[Hypervisor]] * [[Xen]] * [[Qubes OS]] * [[Docker]] * [[Linux]] == References == * https://wiki.xenproject.org/ * https://www.redhat.com/en/topics/virtualization/what-is-virtualization * https://learn.microsoft.com/en-us/virtualization/ == External Links == * https://xenproject.org/ * https://www.virtualbox.org/ 19d25a473d3327b0059a5a64bdff6189a8330baf 0 1151 4773 2026-05-23T03:11:24Z Jokethatcake 333 Created page with "'''Hypervisor''' is software that creates and manages virtual machines by allowing multiple operating systems to share the same physical hardware while remaining isolated from each other. [[Category:Virtualization]] [[Category:Computing]] [[Category:Security]] Hypervisors are a core component of modern virtualization technologies and are widely used in: * cloud computing * enterprise servers * desktop virtualization * cybersecurity * research environments A hyperviso..." wikitext text/x-wiki '''Hypervisor''' is software that creates and manages virtual machines by allowing multiple operating systems to share the same physical hardware while remaining isolated from each other. [[Category:Virtualization]] [[Category:Computing]] [[Category:Security]] Hypervisors are a core component of modern virtualization technologies and are widely used in: * cloud computing * enterprise servers * desktop virtualization * cybersecurity * research environments A hypervisor allocates hardware resources such as: * CPU time * memory * storage * networking * device access to virtual machines known as '''guests'''. == Overview == A hypervisor sits between the hardware and guest operating systems. It allows multiple operating systems to run simultaneously on one physical machine while keeping them isolated. Each guest operating system behaves similarly to a normal computer with virtualized: * processors * memory * disks * network adapters * hardware devices The hypervisor controls access to physical hardware and ensures separation between guests. == Types of Hypervisors == Hypervisors are generally divided into two categories. === Type-1 Hypervisors === '''Type-1 hypervisors''' run directly on physical hardware and are often called '''bare-metal hypervisors'''. Examples include: * [[Xen]] * VMware ESXi * Hyper-V Advantages include: * stronger isolation * lower overhead * improved scalability * direct hardware access Type-1 hypervisors are commonly used in servers and cloud infrastructure. === Type-2 Hypervisors === '''Type-2 hypervisors''' run on top of an existing operating system. Examples include: * VirtualBox * VMware Workstation * QEMU Advantages include: * easier setup * desktop usability * convenient testing However, they usually have more overhead compared to type-1 hypervisors. == Virtual Machines == A '''virtual machine''' (VM) is an isolated environment managed by a hypervisor. Each VM may run: * Linux * Windows * BSD systems * other operating systems Virtual machines usually contain: * virtual CPUs * allocated memory * virtual storage * virtual networking devices == Hardware Virtualization == Modern hypervisors use hardware-assisted virtualization technologies such as: * Intel VT-x * AMD-V These CPU extensions improve: * performance * compatibility * isolation * virtualization efficiency Additional technologies such as IOMMU support allow secure device passthrough. == Memory Management == Hypervisors manage memory allocation between guest systems. Common features include: * dynamic allocation * memory ballooning * memory isolation * page sharing Strong memory separation is important for virtualization security. == CPU Scheduling == The hypervisor schedules CPU time between guest operating systems. Scheduling systems attempt to balance: * performance * fairness * responsiveness * resource efficiency Some hypervisors support CPU pinning for dedicated workloads. == Virtual Networking == Hypervisors provide virtual networking infrastructure for guest systems. Supported networking methods often include: * NAT * bridged networking * isolated internal networks * VLAN integration Virtual machines may communicate with: * the host * external networks * other guests depending on configuration. == Storage == Hypervisors support multiple virtual storage systems including: * disk image files * logical volumes * network storage * snapshots Snapshots allow virtual machine states to be saved and restored. == Device Passthrough == Some hypervisors support direct assignment of physical hardware devices to guests. Examples include: * GPUs * USB controllers * network cards * storage controllers This improves hardware compatibility and performance. == Security == Hypervisors are commonly used for security isolation and sandboxing. Benefits include: * workload separation * malware containment * isolated testing environments * reduced attack surface Security-focused operating systems such as [[Qubes OS]] rely heavily on hypervisor-based isolation. === VM Escapes === A '''VM escape''' occurs when software inside a guest system breaks isolation and compromises the host or other guests. These vulnerabilities are considered critical security issues. === Sandboxing === Hypervisors are frequently used to sandbox: * untrusted applications * malware samples * exploit testing environments == Cloud Computing == Hypervisors are foundational technology for cloud computing platforms. Cloud providers use hypervisors to: * isolate customers * allocate resources dynamically * scale infrastructure * deploy virtual servers rapidly == Advantages == Benefits of hypervisors include: * hardware consolidation * improved resource utilization * workload isolation * scalability * portability == Limitations == Common limitations include: * performance overhead * hardware compatibility issues * increased complexity * hypervisor attack surface A compromised hypervisor may affect all hosted virtual machines. == Use Cases == Hypervisors are commonly used for: * server virtualization * cloud infrastructure * software testing * malware analysis * desktop virtualization * cybersecurity research == See Also == * [[Virtualization]] * [[Xen]] * [[Qubes OS]] * [[Linux]] * [[Docker]] == References == * https://xenproject.org/ * https://learn.microsoft.com/en-us/virtualization/ * https://www.redhat.com/en/topics/virtualization == External Links == * https://www.virtualbox.org/ * https://www.vmware.com/ 390409acc2f23917b9d62f57fb609a8c245320f6 0 1152 4774 2026-05-23T03:12:23Z Jokethatcake 333 Created page with "'''Docker''' is a free and open-source platform used for developing, packaging, distributing, and running applications inside isolated environments known as '''containers'''. [[Category:Containers]] [[Category:Virtualization]] [[Category:DevOps]] [[Category:Free Software]] Docker allows applications and their dependencies to be packaged into portable container images that can run consistently across different systems and environments. The platform is widely used in:..." wikitext text/x-wiki '''Docker''' is a free and open-source platform used for developing, packaging, distributing, and running applications inside isolated environments known as '''containers'''. [[Category:Containers]] [[Category:Virtualization]] [[Category:DevOps]] [[Category:Free Software]] Docker allows applications and their dependencies to be packaged into portable container images that can run consistently across different systems and environments. The platform is widely used in: * cloud computing * software development * DevOps workflows * server infrastructure * continuous integration and deployment == Overview == Docker uses operating-system-level virtualization to isolate applications from the host system and from each other. Unlike traditional virtual machines, Docker containers share the host operating system kernel while maintaining separate: * filesystems * processes * networking * resource limits This makes containers significantly lighter and faster than full virtual machines. == Containers == A '''container''' is an isolated runtime environment containing: * application code * libraries * dependencies * runtime configurations Containers are designed to be: * portable * reproducible * lightweight * scalable A container image can usually run consistently across multiple systems regardless of underlying infrastructure. == Docker Engine == '''Docker Engine''' is the core runtime responsible for creating and managing containers. It includes: * the Docker daemon * container runtime components * networking systems * storage management The daemon runs in the background and manages container operations. == Docker Images == A '''Docker image''' is a read-only template used to create containers. Images commonly contain: * operating system components * application binaries * dependencies * configuration files Docker images are layered to improve storage efficiency and caching. === Dockerfile === A '''Dockerfile''' is a text file containing instructions used to build Docker images. Common instructions include: * FROM * RUN * COPY * CMD * ENTRYPOINT Dockerfiles help automate reproducible application environments. == Docker Hub == '''Docker Hub''' is a public container registry used to distribute container images. Users can: * upload images * download images * share containers * automate builds Private registries may also be used for enterprise environments. == Container Isolation == Docker containers use Linux kernel technologies for isolation. These include: * namespaces * cgroups * seccomp * capabilities * AppArmor * SELinux Isolation helps separate containers from one another and from the host system. == Networking == Docker provides multiple networking modes. Common modes include: * bridge networking * host networking * overlay networking * macvlan networking Containers can communicate with: * external networks * the host system * other containers depending on configuration. == Storage == Docker supports persistent data storage through: * volumes * bind mounts * tmpfs mounts Containers themselves are generally considered ephemeral, while persistent data is stored separately. == Docker Compose == '''Docker Compose''' is a tool used to define and manage multi-container applications. Compose uses YAML configuration files to describe: * services * networks * volumes * environment variables This simplifies deployment of complex containerized applications. == Orchestration == Large-scale Docker deployments often use orchestration platforms such as: * Kubernetes * Docker Swarm * Nomad These systems automate: * scaling * deployment * networking * fault recovery == Security == Docker containers improve isolation but are not equivalent to full virtual machines. Security features include: * namespace isolation * resource limitations * capability restrictions * seccomp filtering However, containers still share the host kernel. === Container Escapes === A '''container escape''' occurs when a process inside a container breaks isolation and gains access to the host system. Misconfiguration or kernel vulnerabilities may increase this risk. === Rootless Containers === Docker supports '''rootless mode''' which allows containers to run without root privileges on the host. This reduces some security risks. == Comparison with Virtual Machines == Docker containers differ from traditional virtual machines. Containers: * share the host kernel * start quickly * consume fewer resources Virtual machines: * emulate full hardware * run separate kernels * provide stronger isolation Containers are generally lighter, while virtual machines provide stronger security boundaries. == Use Cases == Docker is commonly used for: * application deployment * microservices * development environments * CI/CD pipelines * testing * cloud infrastructure == Criticism == Common criticisms of Docker include: * security concerns from shared kernels * container sprawl * complexity in orchestration * networking complexity * resource management challenges == See Also == * [[Containers]] * [[Virtualization]] * [[Kubernetes]] * [[Linux]] * [[Hypervisor]] == References == * https://www.docker.com/ * https://docs.docker.com/ * https://github.com/docker == External Links == * https://hub.docker.com/ * https://docs.docker.com/get-started/ df3872e758538883f83253d45dccecf336d4aa6b 0 1153 4775 2026-05-23T03:13:14Z Jokethatcake 333 Created page with "'''Containers''' are isolated user-space environments used to package and run applications together with their dependencies while sharing the host operating system kernel. [[Category:Containers]] [[Category:Virtualization]] [[Category:Linux]] [[Category:Free Software]] Containers are widely used in: * cloud computing * software development * DevOps * server infrastructure * application deployment Container technologies are commonly associated with Linux and modern op..." wikitext text/x-wiki '''Containers''' are isolated user-space environments used to package and run applications together with their dependencies while sharing the host operating system kernel. [[Category:Containers]] [[Category:Virtualization]] [[Category:Linux]] [[Category:Free Software]] Containers are widely used in: * cloud computing * software development * DevOps * server infrastructure * application deployment Container technologies are commonly associated with Linux and modern open-source infrastructure platforms. == Overview == Containers provide lightweight isolation between applications. Unlike traditional virtual machines, containers do not emulate full hardware or run separate kernels. Instead, they share the host operating system kernel while maintaining isolated: * filesystems * processes * networking * users * resource limits This allows containers to use fewer system resources and start significantly faster than virtual machines. == Linux Containers == Modern container systems on Linux commonly rely on kernel technologies such as: * namespaces * cgroups * seccomp * capabilities These mechanisms provide process isolation and resource control. === Namespaces === Namespaces isolate system resources between containers. Examples include: * process IDs * networking * mount points * hostnames * users === cgroups === Control groups (cgroups) limit and manage resource usage such as: * CPU * memory * disk I/O * network bandwidth == Container Images == Containers are typically created from '''container images'''. An image contains: * application binaries * libraries * dependencies * runtime configurations Images are designed to be portable and reproducible across systems. == Container Engines == A '''container engine''' is software used to create and manage containers. Popular open-source container engines include: * [[Docker]] * Podman * containerd * CRI-O * LXC == Comparison with Virtual Machines == Containers differ from traditional virtual machines. Containers: * share the host kernel * start quickly * use fewer resources * are lightweight Virtual machines: * emulate full hardware * run separate kernels * provide stronger isolation Containers are generally more efficient, while virtual machines usually provide stronger security boundaries. == Security == Containers improve workload isolation but are not equivalent to full hardware virtualization. Security technologies commonly used with containers include: * seccomp filtering * AppArmor * SELinux * rootless containers * capability restrictions === Container Escapes === A '''container escape''' occurs when software inside a container gains unauthorized access to the host system. Kernel vulnerabilities and misconfigurations may increase this risk. == Orchestration == Large-scale container deployments often use orchestration systems such as: * Kubernetes * Docker Swarm * Nomad These systems automate: * deployment * scaling * networking * fault recovery == Use Cases == Containers are commonly used for: * microservices * cloud applications * CI/CD pipelines * development environments * software testing * server hosting == Open-Source Ecosystem == Container technology is heavily associated with the free and open-source software ecosystem. Many major container projects are open-source, including: * Docker * Kubernetes * Podman * containerd * LXC Linux containers have become foundational infrastructure for modern cloud computing and DevOps environments. == See Also == * [[Docker]] * [[Kubernetes]] * [[Virtualization]] * [[Linux]] * [[Hypervisor]] == References == * https://www.docker.com/ * https://kubernetes.io/ * https://podman.io/ * https://linuxcontainers.org/ == External Links == * https://containerd.io/ * https://opencontainers.org/ 3a3f30286296ecfc890a3948a289242e674c020c 0 1154 4776 2026-05-23T03:15:01Z Jokethatcake 333 Created page with "'''Kubernetes''' (often abbreviated as '''K8s''') is a free and open-source container orchestration platform used for automating the deployment, scaling, and management of containerized applications. [[Category:Containers]] [[Category:Cloud Computing]] [[Category:DevOps]] [[Category:Free Software]] Kubernetes was originally developed by Google and is now maintained by the '''Cloud Native Computing Foundation (CNCF)'''. The platform is widely used in: * cloud infrastr..." wikitext text/x-wiki '''Kubernetes''' (often abbreviated as '''K8s''') is a free and open-source container orchestration platform used for automating the deployment, scaling, and management of containerized applications. [[Category:Containers]] [[Category:Cloud Computing]] [[Category:DevOps]] [[Category:Free Software]] Kubernetes was originally developed by Google and is now maintained by the '''Cloud Native Computing Foundation (CNCF)'''. The platform is widely used in: * cloud infrastructure * enterprise environments * DevOps workflows * microservices architectures * large-scale container deployments Kubernetes has become one of the foundational technologies of modern cloud-native computing. == Overview == Kubernetes manages groups of containers across clusters of machines. The platform automates many operational tasks including: * application deployment * scaling * service discovery * networking * self-healing * load balancing Kubernetes is designed to improve reliability, scalability, and portability for containerized workloads. == Architecture == A Kubernetes environment is typically called a '''cluster'''. A cluster consists of: * control plane nodes * worker nodes === Control Plane === The '''control plane''' manages the overall state of the cluster. Core components include: * API Server * Scheduler * Controller Manager * etcd The control plane is responsible for scheduling workloads and maintaining cluster state. === Worker Nodes === Worker nodes run containerized applications. Each worker node commonly includes: * kubelet * container runtime * kube-proxy Worker nodes execute workloads assigned by the control plane. == Pods == A '''Pod''' is the smallest deployable unit in Kubernetes. A pod may contain: * one container * multiple tightly coupled containers Containers inside a pod share: * networking * storage * lifecycle behavior Pods are generally ephemeral and may be recreated automatically if failures occur. == Deployments == '''Deployments''' manage the desired state of applications. Features include: * rolling updates * rollback support * replica management * automatic recovery Deployments simplify large-scale application management. == Services == A '''Service''' exposes applications running inside the cluster. Service types include: * ClusterIP * NodePort * LoadBalancer Services provide stable networking access to pods even when containers are recreated. == Scaling == Kubernetes supports automatic and manual scaling. Scaling features include: * horizontal pod autoscaling * cluster autoscaling * replica scaling This allows infrastructure to adapt dynamically to workload demand. == Networking == Kubernetes includes a virtual networking model allowing pods to communicate across the cluster. Features include: * service discovery * DNS integration * ingress controllers * network policies Networking plugins are commonly provided through the Container Network Interface (CNI). == Storage == Kubernetes supports persistent storage through: * Persistent Volumes * Persistent Volume Claims * Storage Classes The platform can integrate with: * local disks * cloud storage * network filesystems * distributed storage systems == Container Runtimes == Kubernetes supports multiple container runtimes including: * containerd * CRI-O Older Kubernetes systems commonly used [[Docker]] directly before transitioning toward CRI-compatible runtimes. == Orchestration == Kubernetes automates container orchestration tasks such as: * workload scheduling * health monitoring * failover * rolling updates * resource management This reduces manual infrastructure management complexity. == Security == Kubernetes includes numerous security features. === RBAC === '''Role-Based Access Control''' (RBAC) controls permissions within the cluster. === Namespaces === Namespaces isolate workloads and resources between projects or users. === Network Policies === Network policies restrict communication between pods. === Secrets Management === Kubernetes can manage sensitive data such as: * API keys * passwords * certificates However, misconfiguration may still expose secrets. == Cloud Native Computing == Kubernetes is one of the most important technologies in the cloud-native ecosystem. It integrates with many open-source projects including: * Prometheus * Helm * Istio * Argo CD * Fluentd == Advantages == Benefits of Kubernetes include: * scalability * automation * portability * self-healing infrastructure * efficient resource management == Limitations == Common criticisms of Kubernetes include: * high complexity * steep learning curve * operational overhead * networking complexity * resource consumption Improperly secured clusters may also introduce significant security risks. == Use Cases == Kubernetes is commonly used for: * microservices * cloud applications * CI/CD pipelines * distributed systems * enterprise infrastructure * container orchestration == See Also == * [[Docker]] * [[Containers]] * [[Cloud Computing]] * [[Linux]] * [[DevOps]] == References == * https://kubernetes.io/ * https://github.com/kubernetes/kubernetes * https://www.cncf.io/ == External Links == * https://kubernetes.io/docs/ * https://helm.sh/ b8454111425eca934da90bbc53cb840df3edc83a 4794 4776 2026-05-23T05:17:50Z Deviaze 341 Remove AI generated contributions and make this a stub wikitext text/x-wiki {{Stub}} '''Kubernetes''' (often shortened to '''K8s''') is a free and open-source container deployment and management platform often used in enterprise environments. == External Links == * https://kubernetes.io/docs/ * https://helm.sh/ 39f26ad72071b427c68a735e1b025adcb622e2df 4819 4794 2026-05-23T06:33:06Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} '''Kubernetes''' (often shortened to '''K8s''') is a free and open-source container deployment and management platform often used in enterprise environments. == External Links == * https://kubernetes.io/docs/ * https://helm.sh/ ac855173d7ae6f5f898f8a8eae846d03eddd13a0 0 1155 4777 2026-05-23T03:15:58Z Jokethatcake 333 Created page with "'''DevOps''' is a set of practices, philosophies, and tools that combine software development (Dev) and IT operations (Ops) to improve collaboration, automation, deployment speed, and software reliability. [[Category:Software Development]] [[Category:IT Operations]] [[Category:Cloud Computing]] [[Category:Free Software]] DevOps focuses on shortening the software development lifecycle while maintaining high-quality and reliable application delivery. The approach is wid..." wikitext text/x-wiki '''DevOps''' is a set of practices, philosophies, and tools that combine software development (Dev) and IT operations (Ops) to improve collaboration, automation, deployment speed, and software reliability. [[Category:Software Development]] [[Category:IT Operations]] [[Category:Cloud Computing]] [[Category:Free Software]] DevOps focuses on shortening the software development lifecycle while maintaining high-quality and reliable application delivery. The approach is widely used in: * cloud infrastructure * enterprise software * web services * platform engineering * containerized environments == Overview == Traditionally, software development teams and operations teams worked separately. Developers focused on writing software while operations teams handled: * deployment * infrastructure * monitoring * maintenance This separation often caused: * deployment delays * communication issues * inconsistent environments * operational instability DevOps aims to reduce these problems through collaboration, automation, and shared responsibility. == Core Principles == DevOps commonly emphasizes: * automation * continuous integration * continuous delivery * infrastructure as code * monitoring * collaboration The goal is to improve both development speed and operational stability. == Continuous Integration == '''Continuous Integration''' (CI) is the practice of automatically building and testing code changes frequently. Benefits include: * faster feedback * early bug detection * improved software quality Popular CI tools include: * Jenkins * GitHub Actions * GitLab CI/CD == Continuous Delivery == '''Continuous Delivery''' (CD) automates application deployment pipelines. This allows software to be deployed more reliably and frequently. Common deployment methods include: * rolling deployments * blue-green deployments * canary releases == Infrastructure as Code == '''Infrastructure as Code''' (IaC) manages infrastructure using configuration files instead of manual setup. Advantages include: * reproducibility * automation * version control * scalability Popular IaC tools include: * Terraform * Ansible * Puppet * Chef == Containers == Containers play a major role in modern DevOps workflows. Technologies commonly used include: * [[Docker]] * [[Kubernetes]] * Podman Containers improve deployment consistency across environments. == Cloud Computing == DevOps is heavily associated with cloud-native infrastructure and automation. Major cloud providers commonly support DevOps workflows through: * automated scaling * managed Kubernetes services * CI/CD integrations * monitoring systems == Monitoring == Monitoring and observability are important DevOps practices. Common monitoring tasks include: * performance tracking * log aggregation * error detection * infrastructure monitoring Popular open-source tools include: * Prometheus * Grafana * ELK Stack == Automation == Automation is central to DevOps. Automated systems may handle: * testing * deployments * infrastructure provisioning * scaling * backups Automation reduces repetitive manual tasks and operational errors. == Security == Modern DevOps practices increasingly integrate security into development workflows. This approach is often called '''DevSecOps'''. Security-related practices include: * automated vulnerability scanning * secrets management * container security * policy enforcement == Open-Source Ecosystem == The DevOps ecosystem is strongly connected to free and open-source software. Many major DevOps tools are open-source, including: * Jenkins * Kubernetes * Docker * Ansible * Prometheus * Grafana Linux is also heavily used in DevOps infrastructure. == Advantages == Benefits of DevOps include: * faster deployments * improved collaboration * increased automation * better scalability * reduced operational errors == Limitations == Common criticisms of DevOps include: * organizational complexity * tooling overload * steep learning curves * increased operational responsibility for developers Improper implementation may also create security or reliability risks. == Use Cases == DevOps is commonly used for: * cloud applications * web platforms * enterprise infrastructure * CI/CD pipelines * container orchestration * large-scale software systems == See Also == * [[Docker]] * [[Kubernetes]] * [[Containers]] * [[Cloud Computing]] * [[Linux]] == References == * https://aws.amazon.com/devops/what-is-devops/ * https://www.redhat.com/en/topics/devops * https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-devops/ == External Links == * https://kubernetes.io/ * https://www.jenkins.io/ 76ab091ddf707799b194dffec599e130dfb2016d 4818 4777 2026-05-23T06:32:48Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software Development]] [[Category:IT Operations]] [[Category:Cloud Computing]] [[Category:Free Software]] '''DevOps''' is a set of practices, philosophies, and tools that combine software development (Dev) and IT operations (Ops) to improve collaboration, automation, deployment speed, and software reliability. DevOps focuses on shortening the software development lifecycle while maintaining high-quality and reliable application delivery. The approach is widely used in: * cloud infrastructure * enterprise software * web services * platform engineering * containerized environments == Overview == Traditionally, software development teams and operations teams worked separately. Developers focused on writing software while operations teams handled: * deployment * infrastructure * monitoring * maintenance This separation often caused: * deployment delays * communication issues * inconsistent environments * operational instability DevOps aims to reduce these problems through collaboration, automation, and shared responsibility. == Core Principles == DevOps commonly emphasizes: * automation * continuous integration * continuous delivery * infrastructure as code * monitoring * collaboration The goal is to improve both development speed and operational stability. == Continuous Integration == '''Continuous Integration''' (CI) is the practice of automatically building and testing code changes frequently. Benefits include: * faster feedback * early bug detection * improved software quality Popular CI tools include: * Jenkins * GitHub Actions * GitLab CI/CD == Continuous Delivery == '''Continuous Delivery''' (CD) automates application deployment pipelines. This allows software to be deployed more reliably and frequently. Common deployment methods include: * rolling deployments * blue-green deployments * canary releases == Infrastructure as Code == '''Infrastructure as Code''' (IaC) manages infrastructure using configuration files instead of manual setup. Advantages include: * reproducibility * automation * version control * scalability Popular IaC tools include: * Terraform * Ansible * Puppet * Chef == Containers == Containers play a major role in modern DevOps workflows. Technologies commonly used include: * [[Docker]] * [[Kubernetes]] * Podman Containers improve deployment consistency across environments. == Cloud Computing == DevOps is heavily associated with cloud-native infrastructure and automation. Major cloud providers commonly support DevOps workflows through: * automated scaling * managed Kubernetes services * CI/CD integrations * monitoring systems == Monitoring == Monitoring and observability are important DevOps practices. Common monitoring tasks include: * performance tracking * log aggregation * error detection * infrastructure monitoring Popular open-source tools include: * Prometheus * Grafana * ELK Stack == Automation == Automation is central to DevOps. Automated systems may handle: * testing * deployments * infrastructure provisioning * scaling * backups Automation reduces repetitive manual tasks and operational errors. == Security == Modern DevOps practices increasingly integrate security into development workflows. This approach is often called '''DevSecOps'''. Security-related practices include: * automated vulnerability scanning * secrets management * container security * policy enforcement == Open-Source Ecosystem == The DevOps ecosystem is strongly connected to free and open-source software. Many major DevOps tools are open-source, including: * Jenkins * Kubernetes * Docker * Ansible * Prometheus * Grafana Linux is also heavily used in DevOps infrastructure. == Advantages == Benefits of DevOps include: * faster deployments * improved collaboration * increased automation * better scalability * reduced operational errors == Limitations == Common criticisms of DevOps include: * organizational complexity * tooling overload * steep learning curves * increased operational responsibility for developers Improper implementation may also create security or reliability risks. == Use Cases == DevOps is commonly used for: * cloud applications * web platforms * enterprise infrastructure * CI/CD pipelines * container orchestration * large-scale software systems == See Also == * [[Docker]] * [[Kubernetes]] * [[Containers]] * [[Cloud Computing]] * [[Linux]] == References == * https://aws.amazon.com/devops/what-is-devops/ * https://www.redhat.com/en/topics/devops * https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-devops/ == External Links == * https://kubernetes.io/ * https://www.jenkins.io/ a12afb7419b607ee9c4b295168e0afdcf4609131 0 1156 4778 2026-05-23T03:17:23Z Jokethatcake 333 Created page with "'''Cloud Computing''' is the delivery of computing resources and services over the internet, allowing users to access processing power, storage, networking, databases, and software on demand without directly managing physical hardware. [[Category:Cloud Computing]] [[Category:Computing]] [[Category:Virtualization]] [[Category:Networking]] Cloud computing is widely used in: * web services * enterprise infrastructure * software development * artificial intelligence * str..." wikitext text/x-wiki '''Cloud Computing''' is the delivery of computing resources and services over the internet, allowing users to access processing power, storage, networking, databases, and software on demand without directly managing physical hardware. [[Category:Cloud Computing]] [[Category:Computing]] [[Category:Virtualization]] [[Category:Networking]] Cloud computing is widely used in: * web services * enterprise infrastructure * software development * artificial intelligence * streaming platforms * online storage * DevOps environments Modern cloud infrastructure heavily relies on open-source technologies such as [[Linux]], [[Kubernetes]], [[Docker]], and [[Virtualization]] platforms. == Overview == Traditional computing environments often require organizations to maintain their own physical servers and infrastructure. Cloud computing allows resources to be: * rented on demand * scaled dynamically * managed remotely * provisioned automatically This reduces the need for direct hardware ownership and simplifies infrastructure deployment. == Core Concepts == Cloud platforms typically provide: * virtual machines * containers * storage services * networking infrastructure * databases * application hosting Resources are commonly accessed through: * web interfaces * APIs * command-line tools == Service Models == Cloud computing is commonly divided into several service models. === Infrastructure as a Service === '''Infrastructure as a Service''' (IaaS) provides virtualized hardware resources such as: * virtual machines * storage * networking Users manage the operating systems and applications themselves. Examples include: * Amazon EC2 * OpenStack * Google Compute Engine === Platform as a Service === '''Platform as a Service''' (PaaS) provides development platforms and managed runtime environments. This allows developers to deploy applications without directly managing infrastructure. === Software as a Service === '''Software as a Service''' (SaaS) delivers complete software applications over the internet. Examples include: * email platforms * collaboration tools * streaming services Users typically access SaaS applications through web browsers. == Virtualization == Virtualization is a foundational technology of cloud computing. Cloud providers commonly use hypervisors such as: * [[Xen]] * KVM * Hyper-V Virtualization enables: * workload isolation * resource sharing * scalability * rapid deployment == Containers == Containers are widely used in cloud-native infrastructure. Popular technologies include: * [[Docker]] * [[Kubernetes]] * containerd Containers improve portability and deployment consistency. == Scalability == Cloud platforms support rapid scaling of infrastructure. Scaling may occur: * manually * automatically * horizontally * vertically This allows systems to adapt to changing workloads. == Networking == Cloud infrastructure includes virtualized networking systems such as: * software-defined networking * load balancing * virtual private clouds * firewalls These technologies help manage communication between distributed systems. == Storage == Cloud computing platforms commonly provide: * object storage * block storage * distributed storage * backup systems Storage systems are often designed for redundancy and high availability. == Security == Cloud security focuses on protecting: * infrastructure * applications * user data * identities Security technologies commonly include: * encryption * access control * identity management * network isolation * monitoring === Shared Responsibility Model === Many cloud providers follow a '''shared responsibility model'''. In this model: * the provider secures infrastructure * the customer secures applications and configurations Misconfiguration is a major cause of cloud security incidents. == Open-Source Ecosystem == Cloud computing heavily relies on free and open-source software. Common open-source technologies include: * [[Linux]] * [[Kubernetes]] * [[Docker]] * OpenStack * Prometheus Large cloud infrastructures often run Linux-based systems internally. == Advantages == Benefits of cloud computing include: * scalability * flexibility * reduced hardware costs * global accessibility * rapid deployment == Limitations == Common criticisms of cloud computing include: * vendor lock-in * privacy concerns * service outages * operational complexity * dependence on internet connectivity Security misconfiguration may also expose sensitive data. == Use Cases == Cloud computing is commonly used for: * web hosting * application deployment * AI workloads * streaming services * online storage * DevOps infrastructure * enterprise platforms == See Also == * [[Virtualization]] * [[Docker]] * [[Kubernetes]] * [[Linux]] * [[DevOps]] == References == * https://aws.amazon.com/what-is-cloud-computing/ * https://cloud.google.com/learn/what-is-cloud-computing * https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-cloud-computing/ == External Links == * https://www.openstack.org/ * https://kubernetes.io/ 9c34c66cca4a17185112eef4cc91574c41eabf5b 4817 4778 2026-05-23T06:32:38Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Cloud Computing]] [[Category:Computing]] [[Category:Virtualization]] [[Category:Networking]] '''Cloud Computing''' is the delivery of computing resources and services over the internet, allowing users to access processing power, storage, networking, databases, and software on demand without directly managing physical hardware. Cloud computing is widely used in: * web services * enterprise infrastructure * software development * artificial intelligence * streaming platforms * online storage * DevOps environments Modern cloud infrastructure heavily relies on open-source technologies such as [[Linux]], [[Kubernetes]], [[Docker]], and [[Virtualization]] platforms. == Overview == Traditional computing environments often require organizations to maintain their own physical servers and infrastructure. Cloud computing allows resources to be: * rented on demand * scaled dynamically * managed remotely * provisioned automatically This reduces the need for direct hardware ownership and simplifies infrastructure deployment. == Core Concepts == Cloud platforms typically provide: * virtual machines * containers * storage services * networking infrastructure * databases * application hosting Resources are commonly accessed through: * web interfaces * APIs * command-line tools == Service Models == Cloud computing is commonly divided into several service models. === Infrastructure as a Service === '''Infrastructure as a Service''' (IaaS) provides virtualized hardware resources such as: * virtual machines * storage * networking Users manage the operating systems and applications themselves. Examples include: * Amazon EC2 * OpenStack * Google Compute Engine === Platform as a Service === '''Platform as a Service''' (PaaS) provides development platforms and managed runtime environments. This allows developers to deploy applications without directly managing infrastructure. === Software as a Service === '''Software as a Service''' (SaaS) delivers complete software applications over the internet. Examples include: * email platforms * collaboration tools * streaming services Users typically access SaaS applications through web browsers. == Virtualization == Virtualization is a foundational technology of cloud computing. Cloud providers commonly use hypervisors such as: * [[Xen]] * KVM * Hyper-V Virtualization enables: * workload isolation * resource sharing * scalability * rapid deployment == Containers == Containers are widely used in cloud-native infrastructure. Popular technologies include: * [[Docker]] * [[Kubernetes]] * containerd Containers improve portability and deployment consistency. == Scalability == Cloud platforms support rapid scaling of infrastructure. Scaling may occur: * manually * automatically * horizontally * vertically This allows systems to adapt to changing workloads. == Networking == Cloud infrastructure includes virtualized networking systems such as: * software-defined networking * load balancing * virtual private clouds * firewalls These technologies help manage communication between distributed systems. == Storage == Cloud computing platforms commonly provide: * object storage * block storage * distributed storage * backup systems Storage systems are often designed for redundancy and high availability. == Security == Cloud security focuses on protecting: * infrastructure * applications * user data * identities Security technologies commonly include: * encryption * access control * identity management * network isolation * monitoring === Shared Responsibility Model === Many cloud providers follow a '''shared responsibility model'''. In this model: * the provider secures infrastructure * the customer secures applications and configurations Misconfiguration is a major cause of cloud security incidents. == Open-Source Ecosystem == Cloud computing heavily relies on free and open-source software. Common open-source technologies include: * [[Linux]] * [[Kubernetes]] * [[Docker]] * OpenStack * Prometheus Large cloud infrastructures often run Linux-based systems internally. == Advantages == Benefits of cloud computing include: * scalability * flexibility * reduced hardware costs * global accessibility * rapid deployment == Limitations == Common criticisms of cloud computing include: * vendor lock-in * privacy concerns * service outages * operational complexity * dependence on internet connectivity Security misconfiguration may also expose sensitive data. == Use Cases == Cloud computing is commonly used for: * web hosting * application deployment * AI workloads * streaming services * online storage * DevOps infrastructure * enterprise platforms == See Also == * [[Virtualization]] * [[Docker]] * [[Kubernetes]] * [[Linux]] * [[DevOps]] == References == * https://aws.amazon.com/what-is-cloud-computing/ * https://cloud.google.com/learn/what-is-cloud-computing * https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-cloud-computing/ == External Links == * https://www.openstack.org/ * https://kubernetes.io/ 02864e33952e016c01020b689a51ce1c7c552161 0 1157 4779 2026-05-23T03:18:28Z Jokethatcake 333 Created page with "'''Zenwalk''' is a lightweight Linux distribution based on [[Slackware]] focused on simplicity, speed, and efficient desktop computing. [[Category:Linux Distributions]] [[Category:Slackware-based Distributions]] [[Category:Free Software]] Zenwalk is designed to provide a fast and streamlined Linux experience while maintaining compatibility with the Slackware ecosystem. The distribution emphasizes: * simplicity * minimalism * performance * ease of use Zenwalk is comm..." wikitext text/x-wiki '''Zenwalk''' is a lightweight Linux distribution based on [[Slackware]] focused on simplicity, speed, and efficient desktop computing. [[Category:Linux Distributions]] [[Category:Slackware-based Distributions]] [[Category:Free Software]] Zenwalk is designed to provide a fast and streamlined Linux experience while maintaining compatibility with the Slackware ecosystem. The distribution emphasizes: * simplicity * minimalism * performance * ease of use Zenwalk is commonly used on: * older hardware * lightweight desktop systems * low-resource environments * general-purpose Linux desktops == Overview == Zenwalk was originally created as a lightweight alternative to traditional Slackware installations. The project focuses on providing: * optimized software selection * lightweight desktop environments * simplified administration * efficient resource usage Unlike standard Slackware installations, Zenwalk attempts to include a more complete desktop experience by default. == History == Zenwalk was originally known as '''Minislack''' before being renamed. The distribution was developed to create a balance between: * Slackware simplicity * desktop usability * lightweight performance Over time, Zenwalk developed its own repositories, package tools, and desktop customization. == Slackware Base == Zenwalk is based on [[Slackware]], one of the oldest Linux distributions still actively maintained. Because of this, Zenwalk inherits many Slackware characteristics including: * simplicity * traditional UNIX-like design * manual configuration philosophy * stability Zenwalk remains compatible with much of the Slackware software ecosystem. == Desktop Environment == Zenwalk has historically focused on lightweight desktop environments. The distribution commonly uses: * XFCE The lightweight desktop design helps reduce: * memory usage * CPU overhead * system resource consumption == Package Management == Zenwalk uses package management systems derived from Slackware. Software management tools include: * netpkg * pkgtools Packages are generally distributed in Slackware-compatible formats. == Performance == Zenwalk emphasizes speed and low resource usage. Optimization goals include: * fast boot times * responsive desktop performance * lightweight software selection This makes the distribution suitable for older or lower-end hardware. == Software Selection == Zenwalk attempts to provide one primary application per major task category. Examples include: * lightweight desktop applications * development tools * multimedia software * networking utilities This approach helps reduce software redundancy and system bloat. == Development == Zenwalk supports software development with tools commonly available through Slackware repositories and compatible packages. Users may develop software using: * GCC * Python * Perl * shell scripting == Security == Like many Linux distributions, Zenwalk benefits from: * Linux permission systems * UNIX-like user separation * open-source transparency Security updates are distributed through project repositories. == Community == Zenwalk has historically maintained a smaller but dedicated Linux community. Community support commonly includes: * forums * documentation * package repositories * user guides == Use Cases == Zenwalk is commonly used for: * lightweight desktop computing * older hardware revitalization * general Linux usage * Slackware-based environments * educational systems == Limitations == Common criticisms of Zenwalk include: * smaller community size * limited package repositories * slower release activity * less beginner-friendly configuration compared to some modern distributions == Comparison with Other Distributions == Zenwalk is often compared with: * [[Slackware]] * [[Arch Linux]] * [[Xubuntu]] * [[Puppy Linux]] Compared to standard Slackware, Zenwalk focuses more heavily on desktop usability and lightweight optimization. == See Also == * [[Slackware]] * [[Linux]] * [[XFCE]] * [[Linux Distributions]] == References == * http://www.zenwalk.org/ * https://distrowatch.com/table.php?distribution=zenwalk == External Links == * http://www.zenwalk.org/modules/tinycontent/ 29af0fd6f3a0d7122608bd3ebdea7b118539e81e 4816 4779 2026-05-23T06:32:28Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] [[Category:Slackware-based Distributions]] [[Category:Free Software]] '''Zenwalk''' is a lightweight Linux distribution based on [[Slackware]] focused on simplicity, speed, and efficient desktop computing. Zenwalk is designed to provide a fast and streamlined Linux experience while maintaining compatibility with the Slackware ecosystem. The distribution emphasizes: * simplicity * minimalism * performance * ease of use Zenwalk is commonly used on: * older hardware * lightweight desktop systems * low-resource environments * general-purpose Linux desktops == Overview == Zenwalk was originally created as a lightweight alternative to traditional Slackware installations. The project focuses on providing: * optimized software selection * lightweight desktop environments * simplified administration * efficient resource usage Unlike standard Slackware installations, Zenwalk attempts to include a more complete desktop experience by default. == History == Zenwalk was originally known as '''Minislack''' before being renamed. The distribution was developed to create a balance between: * Slackware simplicity * desktop usability * lightweight performance Over time, Zenwalk developed its own repositories, package tools, and desktop customization. == Slackware Base == Zenwalk is based on [[Slackware]], one of the oldest Linux distributions still actively maintained. Because of this, Zenwalk inherits many Slackware characteristics including: * simplicity * traditional UNIX-like design * manual configuration philosophy * stability Zenwalk remains compatible with much of the Slackware software ecosystem. == Desktop Environment == Zenwalk has historically focused on lightweight desktop environments. The distribution commonly uses: * XFCE The lightweight desktop design helps reduce: * memory usage * CPU overhead * system resource consumption == Package Management == Zenwalk uses package management systems derived from Slackware. Software management tools include: * netpkg * pkgtools Packages are generally distributed in Slackware-compatible formats. == Performance == Zenwalk emphasizes speed and low resource usage. Optimization goals include: * fast boot times * responsive desktop performance * lightweight software selection This makes the distribution suitable for older or lower-end hardware. == Software Selection == Zenwalk attempts to provide one primary application per major task category. Examples include: * lightweight desktop applications * development tools * multimedia software * networking utilities This approach helps reduce software redundancy and system bloat. == Development == Zenwalk supports software development with tools commonly available through Slackware repositories and compatible packages. Users may develop software using: * GCC * Python * Perl * shell scripting == Security == Like many Linux distributions, Zenwalk benefits from: * Linux permission systems * UNIX-like user separation * open-source transparency Security updates are distributed through project repositories. == Community == Zenwalk has historically maintained a smaller but dedicated Linux community. Community support commonly includes: * forums * documentation * package repositories * user guides == Use Cases == Zenwalk is commonly used for: * lightweight desktop computing * older hardware revitalization * general Linux usage * Slackware-based environments * educational systems == Limitations == Common criticisms of Zenwalk include: * smaller community size * limited package repositories * slower release activity * less beginner-friendly configuration compared to some modern distributions == Comparison with Other Distributions == Zenwalk is often compared with: * [[Slackware]] * [[Arch Linux]] * [[Xubuntu]] * [[Puppy Linux]] Compared to standard Slackware, Zenwalk focuses more heavily on desktop usability and lightweight optimization. == See Also == * [[Slackware]] * [[Linux]] * [[XFCE]] * [[Linux Distributions]] == References == * http://www.zenwalk.org/ * https://distrowatch.com/table.php?distribution=zenwalk == External Links == * http://www.zenwalk.org/modules/tinycontent/ ab76ebca72846b6e079076f85fee934d428ab094 0 1158 4780 2026-05-23T03:19:43Z Jokethatcake 333 Created page with "'''Xubuntu''' is a free and open-source Linux distribution based on [[Ubuntu]] that uses the [[XFCE]] desktop environment. [[Category:Linux Distributions]] [[Category:Ubuntu-based Distributions]] [[Category:Free Software]] Xubuntu is designed to provide a lightweight, stable, and user-friendly desktop experience while maintaining compatibility with the Ubuntu ecosystem. The distribution focuses on: * performance * simplicity * low resource usage * desktop usability..." wikitext text/x-wiki '''Xubuntu''' is a free and open-source Linux distribution based on [[Ubuntu]] that uses the [[XFCE]] desktop environment. [[Category:Linux Distributions]] [[Category:Ubuntu-based Distributions]] [[Category:Free Software]] Xubuntu is designed to provide a lightweight, stable, and user-friendly desktop experience while maintaining compatibility with the Ubuntu ecosystem. The distribution focuses on: * performance * simplicity * low resource usage * desktop usability Xubuntu is commonly used on: * older hardware * low-resource systems * laptops * general-purpose desktops == Overview == Xubuntu combines the Ubuntu base system with the lightweight XFCE desktop environment. The project aims to provide: * efficient system performance * a traditional desktop interface * long-term support releases * extensive software availability Compared to standard Ubuntu using GNOME, Xubuntu generally consumes fewer system resources. == XFCE Desktop == Xubuntu uses the [[XFCE]] desktop environment by default. XFCE is known for: * low memory usage * fast performance * modular design * customization flexibility The desktop layout traditionally includes: * application menus * taskbars * desktop icons * configurable panels == Ubuntu Base == Because Xubuntu is based on [[Ubuntu]], it inherits many Ubuntu features including: * APT package management * Ubuntu repositories * hardware compatibility * large software ecosystem Most Ubuntu software packages can run on Xubuntu without modification. == Package Management == Xubuntu uses the APT package management system. Software can be installed through: * apt * Synaptic * graphical software centers Supported package formats include: * DEB packages * Flatpak (optional) * Snap packages == Performance == Xubuntu is optimized for lightweight performance. Advantages include: * reduced RAM usage * lower CPU overhead * faster responsiveness on older systems This makes the distribution popular for revitalizing aging hardware. == Software == Xubuntu includes a collection of desktop applications for common tasks such as: * web browsing * office work * multimedia playback * file management * email The distribution attempts to balance functionality with lightweight operation. == Releases == Xubuntu follows Ubuntu release schedules. This includes: * regular releases * Long-Term Support (LTS) versions LTS releases receive extended maintenance and security updates. == Customization == XFCE provides extensive desktop customization. Users can modify: * themes * icons * panel layouts * window behavior * keyboard shortcuts The environment supports both traditional and modern desktop workflows. == Security == Xubuntu inherits Ubuntu security infrastructure including: * regular security updates * user permission systems * AppArmor integration * repository signing Linux security practices still apply, including proper update management and account security. == Community == Xubuntu is supported by an active open-source community. Community resources include: * forums * documentation * IRC channels * community guides The project is developed collaboratively within the Ubuntu ecosystem. == Use Cases == Xubuntu is commonly used for: * lightweight desktop computing * older hardware * educational systems * home desktops * office environments == Comparison with Other Ubuntu Flavors == Xubuntu is often compared with other Ubuntu-based distributions such as: * Kubuntu * Lubuntu * Ubuntu MATE Compared to standard Ubuntu, Xubuntu generally focuses more heavily on lightweight performance and traditional desktop workflows. == Limitations == Common criticisms of Xubuntu include: * less modern visual design compared to GNOME-based desktops * fewer built-in features than heavier desktop environments * occasional XFCE limitations == See Also == * [[Ubuntu]] * [[XFCE]] * [[Linux]] * [[Lubuntu]] == References == * https://xubuntu.org/ * https://docs.xubuntu.org/ == External Links == * https://xubuntu.org/download/ * https://wiki.xubuntu.org/ 73b5e6575f13fd42f72c7e66af475d284f05b9e7 4815 4780 2026-05-23T06:30:57Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] [[Category:Ubuntu-based Distributions]] [[Category:Free Software]] '''Xubuntu''' is a free and open-source Linux distribution based on [[Ubuntu]] that uses the [[XFCE]] desktop environment. Xubuntu is designed to provide a lightweight, stable, and user-friendly desktop experience while maintaining compatibility with the Ubuntu ecosystem. The distribution focuses on: * performance * simplicity * low resource usage * desktop usability Xubuntu is commonly used on: * older hardware * low-resource systems * laptops * general-purpose desktops == Overview == Xubuntu combines the Ubuntu base system with the lightweight XFCE desktop environment. The project aims to provide: * efficient system performance * a traditional desktop interface * long-term support releases * extensive software availability Compared to standard Ubuntu using GNOME, Xubuntu generally consumes fewer system resources. == XFCE Desktop == Xubuntu uses the [[XFCE]] desktop environment by default. XFCE is known for: * low memory usage * fast performance * modular design * customization flexibility The desktop layout traditionally includes: * application menus * taskbars * desktop icons * configurable panels == Ubuntu Base == Because Xubuntu is based on [[Ubuntu]], it inherits many Ubuntu features including: * APT package management * Ubuntu repositories * hardware compatibility * large software ecosystem Most Ubuntu software packages can run on Xubuntu without modification. == Package Management == Xubuntu uses the APT package management system. Software can be installed through: * apt * Synaptic * graphical software centers Supported package formats include: * DEB packages * Flatpak (optional) * Snap packages == Performance == Xubuntu is optimized for lightweight performance. Advantages include: * reduced RAM usage * lower CPU overhead * faster responsiveness on older systems This makes the distribution popular for revitalizing aging hardware. == Software == Xubuntu includes a collection of desktop applications for common tasks such as: * web browsing * office work * multimedia playback * file management * email The distribution attempts to balance functionality with lightweight operation. == Releases == Xubuntu follows Ubuntu release schedules. This includes: * regular releases * Long-Term Support (LTS) versions LTS releases receive extended maintenance and security updates. == Customization == XFCE provides extensive desktop customization. Users can modify: * themes * icons * panel layouts * window behavior * keyboard shortcuts The environment supports both traditional and modern desktop workflows. == Security == Xubuntu inherits Ubuntu security infrastructure including: * regular security updates * user permission systems * AppArmor integration * repository signing Linux security practices still apply, including proper update management and account security. == Community == Xubuntu is supported by an active open-source community. Community resources include: * forums * documentation * IRC channels * community guides The project is developed collaboratively within the Ubuntu ecosystem. == Use Cases == Xubuntu is commonly used for: * lightweight desktop computing * older hardware * educational systems * home desktops * office environments == Comparison with Other Ubuntu Flavors == Xubuntu is often compared with other Ubuntu-based distributions such as: * Kubuntu * Lubuntu * Ubuntu MATE Compared to standard Ubuntu, Xubuntu generally focuses more heavily on lightweight performance and traditional desktop workflows. == Limitations == Common criticisms of Xubuntu include: * less modern visual design compared to GNOME-based desktops * fewer built-in features than heavier desktop environments * occasional XFCE limitations == See Also == * [[Ubuntu]] * [[XFCE]] * [[Linux]] * [[Lubuntu]] == References == * https://xubuntu.org/ * https://docs.xubuntu.org/ == External Links == * https://xubuntu.org/download/ * https://wiki.xubuntu.org/ 5b02d1067aa2e79feeb796dd26656a1cc5920979 0 1159 4781 2026-05-23T03:20:54Z Jokethatcake 333 Created page with "'''Lubuntu''' is a free and open-source Linux distribution based on [[Ubuntu]] designed for lightweight and energy-efficient desktop computing. [[Category:Linux Distributions]] [[Category:Ubuntu-based Distributions]] [[Category:Free Software]] Lubuntu uses the lightweight '''LXQt''' desktop environment and focuses on: * low resource usage * speed * simplicity * usability on older hardware The distribution is commonly used on: * older computers * low-end hardware * l..." wikitext text/x-wiki '''Lubuntu''' is a free and open-source Linux distribution based on [[Ubuntu]] designed for lightweight and energy-efficient desktop computing. [[Category:Linux Distributions]] [[Category:Ubuntu-based Distributions]] [[Category:Free Software]] Lubuntu uses the lightweight '''LXQt''' desktop environment and focuses on: * low resource usage * speed * simplicity * usability on older hardware The distribution is commonly used on: * older computers * low-end hardware * laptops * lightweight desktop systems * educational environments == Overview == Lubuntu combines the Ubuntu base system with lightweight desktop technologies in order to provide a fast and efficient user experience. Compared to standard Ubuntu, Lubuntu generally uses: * less RAM * fewer background services * lower CPU usage This makes it suitable for systems with limited hardware resources. == History == Earlier versions of Lubuntu used the '''LXDE''' desktop environment. Modern releases use '''LXQt''', a lightweight desktop environment based on Qt technologies. The transition to LXQt improved: * desktop maintainability * Qt integration * modern desktop functionality == LXQt Desktop == Lubuntu uses the [[LXQt]] desktop environment by default. LXQt is designed to be: * lightweight * modular * fast * customizable Features commonly include: * application menus * desktop panels * file managers * configurable shortcuts LXQt attempts to provide a traditional desktop experience with low system overhead. == Ubuntu Base == Because Lubuntu is based on [[Ubuntu]], it inherits many Ubuntu features including: * APT package management * Ubuntu repositories * hardware support * extensive software availability Most Ubuntu software packages can run on Lubuntu without modification. == Package Management == Lubuntu uses the APT package management system. Software can be installed using: * apt * graphical package managers * Ubuntu software repositories Supported package technologies may include: * DEB packages * Flatpak * Snap packages == Performance == Lubuntu is heavily optimized for lightweight performance. Advantages include: * low memory usage * fast startup times * responsive desktop operation * reduced CPU consumption The distribution is commonly recommended for revitalizing older hardware. == Included Software == Lubuntu includes applications for common desktop tasks such as: * web browsing * document editing * multimedia playback * file management * terminal access The software selection emphasizes lightweight alternatives where possible. == Releases == Lubuntu follows Ubuntu release schedules. This includes: * standard releases * Long-Term Support (LTS) releases LTS releases receive extended security and maintenance support. == Customization == LXQt allows users to customize: * desktop themes * icons * panels * keyboard shortcuts * window behavior The environment supports both minimal and more feature-rich desktop configurations. == Security == Lubuntu inherits Ubuntu security infrastructure including: * signed repositories * user permissions * regular security updates * AppArmor integration Users are still responsible for maintaining secure system configurations and updates. == Community == Lubuntu is supported by an open-source community that provides: * documentation * forums * troubleshooting guides * development contributions The project is part of the wider Ubuntu ecosystem. == Use Cases == Lubuntu is commonly used for: * older computers * lightweight desktop systems * educational environments * low-resource virtual machines * portable Linux installations == Comparison with Other Ubuntu Flavors == Lubuntu is often compared with: * [[Xubuntu]] * Ubuntu MATE * standard Ubuntu Compared to Xubuntu, Lubuntu generally prioritizes lower resource usage over desktop features. == Limitations == Common criticisms of Lubuntu include: * fewer built-in desktop features * simpler default interface * limited advanced customization compared to heavier desktop environments == See Also == * [[Ubuntu]] * [[LXQt]] * [[Linux]] * [[Xubuntu]] == References == * https://lubuntu.me/ * https://manual.lubuntu.me/ == External Links == * https://lubuntu.me/downloads/ * https://git.lubuntu.me/ cbec910a768b4dc6628c33603524949694d6653b 4792 4781 2026-05-23T05:08:21Z Deviaze 341 Remove AI generated contributions to leave page as a stub. wikitext text/x-wiki {{Stub}} '''Lubuntu''' is a free and open-source Linux distribution based on [[Ubuntu]] designed for lightweight and energy-efficient desktop computing. [[Category:Linux Distributions]] == External Links == * https://lubuntu.me * https://git.lubuntu.me/ 1e272f5c9ff1060d5f0b676afdf871adb09cc6bb 4814 4792 2026-05-23T06:29:36Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Stub}} '''Lubuntu''' is a free and open-source Linux distribution based on [[Ubuntu]] designed for lightweight and energy-efficient desktop computing. == External Links == * https://lubuntu.me * https://git.lubuntu.me/ 2ddf5647204d92784a58dd61a46c68742266cd1d 0 1160 4782 2026-05-23T03:55:58Z Jokethatcake 333 Created page with "'''KDE''' is a free and open-source software community and desktop environment project focused on creating graphical applications and desktop technologies for Linux and other UNIX-like operating systems. [[Category:Desktop Environments]] [[Category:Linux]] [[Category:Free Software]] [[Category:Qt]] KDE is best known for '''KDE Plasma''', a highly customizable desktop environment used on many Linux distributions. The project develops: * desktop environments * graphica..." wikitext text/x-wiki '''KDE''' is a free and open-source software community and desktop environment project focused on creating graphical applications and desktop technologies for Linux and other UNIX-like operating systems. [[Category:Desktop Environments]] [[Category:Linux]] [[Category:Free Software]] [[Category:Qt]] KDE is best known for '''KDE Plasma''', a highly customizable desktop environment used on many Linux distributions. The project develops: * desktop environments * graphical applications * system utilities * development frameworks KDE software is widely used across desktop Linux systems and open-source ecosystems. == Overview == The KDE project was founded to create a consistent and user-friendly graphical desktop environment for UNIX-like systems. KDE emphasizes: * customization * flexibility * graphical integration * modern desktop functionality The ecosystem includes both the Plasma desktop and a large collection of applications. == KDE Plasma == '''KDE Plasma''' is the primary desktop environment developed by KDE. Plasma is known for: * extensive customization * modern visual effects * modular components * flexible workflows Features commonly include: * desktop widgets * configurable panels * virtual desktops * advanced window management * system-wide theming == Qt Framework == KDE software is primarily built using the '''Qt''' framework. Qt provides: * graphical interface libraries * cross-platform support * development tools * hardware abstraction Qt allows KDE applications to run on multiple operating systems. == KDE Applications == The KDE project develops many graphical applications including: * Dolphin * Konsole * Gwenview * Okular * Kate * Kdenlive These applications are designed to integrate closely with the Plasma desktop. == Customization == KDE Plasma is widely recognized for its customization capabilities. Users can modify: * themes * icons * widgets * animations * keyboard shortcuts * panel layouts * window behavior The environment supports both lightweight and highly customized desktop setups. == Performance == Modern KDE Plasma versions focus heavily on improving performance and efficiency. Optimization efforts include: * reduced memory usage * improved rendering performance * faster startup times Performance may vary depending on enabled visual effects and system configuration. == Wayland and X11 == KDE Plasma supports both: * X11 * Wayland Wayland support has become increasingly important in modern Linux desktop environments. == Security == KDE Plasma benefits from standard Linux security mechanisms including: * user permission separation * sandboxing support * signed repositories * application isolation technologies Security also depends heavily on the underlying Linux distribution and system configuration. == Linux Distributions == KDE Plasma is commonly available on many Linux distributions including: * [[Kubuntu]] * openSUSE * Fedora KDE * Arch Linux * KDE neon Some distributions provide KDE Plasma as their primary desktop environment. == KDE neon == '''KDE neon''' is a Linux distribution developed by the KDE community using Ubuntu as its base system. It focuses on delivering the latest KDE software releases. == Community == KDE is maintained by a large open-source community consisting of: * developers * designers * translators * documentation writers The project collaborates openly through community-driven development. == Advantages == Benefits of KDE Plasma include: * extensive customization * modern interface design * large application ecosystem * advanced desktop functionality == Limitations == Common criticisms of KDE Plasma include: * complexity for new users * large configuration surface * occasional instability in experimental features * higher resource usage compared to minimal desktop environments == Use Cases == KDE Plasma is commonly used for: * desktop computing * development environments * multimedia workstations * customized Linux systems * general-purpose computing == See Also == * [[Linux]] * [[Qt]] * [[XFCE]] * [[GNOME]] * [[Kubuntu]] == References == * https://kde.org/ * https://develop.kde.org/ * https://community.kde.org/ == External Links == * https://invent.kde.org/ * https://kde.org/plasma-desktop/ 844573f6fb5ea833dd2b9c0877e8cc98a4606c7b 4786 4782 2026-05-23T04:22:50Z Madonuko 140 remove previous incorrect AI hallucination edit wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}} '''KDE Linux''' is a new [[Unix]]-like [[operating system]] made by [[KDE]] that ships the lines of products and components implemented by KDE. b8bcf258b950a3b32ac882bd8e51e2b27422268c 4787 4786 2026-05-23T04:24:04Z Jokethatcake 333 wikitext text/x-wiki '''KDE Linux''' is a free and open-source Linux-based operating system developed by the KDE community as a unified, user-focused desktop OS built around KDE technologies. [[Category:Linux Distributions]] [[Category:KDE]] [[Category:Free Software]] [[Category:Operating Systems]] KDE Linux is designed to provide a modern, safe, and coherent operating system that integrates the KDE software ecosystem, including [[KDE Plasma]] and KDE applications. The project is still under active development and is not yet considered a final stable release. == Overview == KDE Linux is developed as a KDE-owned operating system intended to showcase the best integration of KDE software. It aims to be: * user-focused * modern * safe and maintainable * suitable for home, enterprise, and institutional use The system is currently in early development and is expected to evolve significantly. == Key Features == KDE Linux emphasizes several core principles: * tight integration of KDE technologies * modern Linux desktop experience * stability through system design * usability for general users == KDE Integration == KDE Linux is built around the KDE ecosystem, including: * [[KDE Plasma]] desktop environment * KDE applications * KDE frameworks This ensures a consistent experience across the system. == Development Status == KDE Linux is currently under active development and is not yet considered fully stable. The project is evolving and aims to become a general-purpose operating system suitable for wide adoption. == Architecture == KDE Linux is designed as a modern Linux-based system using contemporary technologies and workflows. It focuses on: * maintainability * system safety * integration of components * long-term usability == Goals == The main goals of KDE Linux include: * creating a complete KDE-based operating system * improving user experience across KDE software * providing a reference implementation for KDE technologies * simplifying adoption of KDE Plasma systems == Use Cases == KDE Linux is intended for: * home users * developers * enterprise environments * public institutions * pre-installed desktop systems == Relationship to KDE Project == KDE Linux is not the KDE desktop environment itself. Instead, it is a full operating system built by the KDE community to showcase and integrate KDE technologies in a single platform. == See Also == * [[KDE]] * [[KDE Plasma]] * [[Linux]] * [[Qt]] == References == * https://linux.kde.org/ * https://kde.org/linux/ * https://invent.kde.org/kde-linux 488129c0ac3b7162e5b46c7f3c03b0ae95df9cc3 4788 4787 2026-05-23T04:37:14Z Madonuko 140 Undo revision [[Special:Diff/4787|4787]] by [[Special:Contributions/Jokethatcake|Jokethatcake]] ([[User talk:Jokethatcake|talk]]) wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}} '''KDE Linux''' is a new [[Unix]]-like [[operating system]] made by [[KDE]] that ships the lines of products and components implemented by KDE. b8bcf258b950a3b32ac882bd8e51e2b27422268c 0 1161 4783 2026-05-23T04:02:59Z Jokethatcake 333 Created page with "'''BlackArch''' is a free and open-source penetration testing and cybersecurity-focused Linux distribution based on [[Arch Linux]]. [[Category:Linux Distributions]] [[Category:Arch-based Distributions]] [[Category:Security]] [[Category:Free Software]] BlackArch is designed for: * penetration testing * vulnerability research * malware analysis * reverse engineering * digital forensics * security auditing The distribution provides a large repository of cybersecurity an..." wikitext text/x-wiki '''BlackArch''' is a free and open-source penetration testing and cybersecurity-focused Linux distribution based on [[Arch Linux]]. [[Category:Linux Distributions]] [[Category:Arch-based Distributions]] [[Category:Security]] [[Category:Free Software]] BlackArch is designed for: * penetration testing * vulnerability research * malware analysis * reverse engineering * digital forensics * security auditing The distribution provides a large repository of cybersecurity and security research tools integrated into the Arch Linux ecosystem. == Overview == BlackArch extends [[Arch Linux]] by adding a dedicated repository containing thousands of security-related packages. The distribution focuses on: * minimalism * flexibility * rolling-release updates * advanced customization Because it inherits Arch Linux principles, BlackArch is generally intended for experienced Linux users. == Arch Linux Base == BlackArch is built on top of [[Arch Linux]]. It inherits many Arch features including: * pacman package management * rolling-release updates * lightweight base installation * user-controlled configuration Users may install BlackArch either as: * a standalone distribution * an additional repository on existing Arch installations == Security Tools == BlackArch includes a large collection of cybersecurity tools. Categories commonly include: * penetration testing * wireless security * exploit development * reverse engineering * cryptography * malware analysis * digital forensics * reconnaissance Many tools are command-line based and intended for advanced users. == Package Management == BlackArch uses the '''pacman''' package manager inherited from Arch Linux. Software repositories can be synchronized and updated through standard Arch package management workflows. The BlackArch repository contains thousands of security-related packages. == Rolling Release == BlackArch follows a rolling-release model inherited from Arch Linux. Advantages include: * continuously updated software * rapid security updates * access to recent tool versions However, rolling releases may occasionally introduce instability. == Desktop Environments == BlackArch does not enforce a single desktop environment. Users may install environments such as: * XFCE * KDE Plasma * GNOME * i3 * Openbox Minimal installations are common in security-focused environments. == Command-Line Focus == Many BlackArch workflows rely heavily on command-line tools and manual configuration. Users are generally expected to understand: * Linux administration * networking * package management * shell environments == Security == BlackArch is intended for defensive security research and authorized testing environments. The distribution includes tools capable of: * network analysis * vulnerability scanning * exploitation * packet capture Improper or unauthorized use of such tools may violate laws or organizational policies. == Use Cases == BlackArch is commonly used for: * penetration testing * security research * digital forensics * malware analysis * cybersecurity education * lab environments == Comparison with Other Security Distributions == BlackArch is often compared with: * Kali Linux * Parrot Security OS Compared to Kali Linux, BlackArch generally emphasizes: * Arch Linux customization * rolling releases * larger package repositories * advanced user workflows == Advantages == Benefits of BlackArch include: * large security tool repository * Arch Linux flexibility * rolling-release updates * lightweight base system == Limitations == Common criticisms of BlackArch include: * steep learning curve * limited beginner friendliness * rolling-release instability risks * heavy reliance on command-line configuration == Community == BlackArch is maintained by an open-source community of developers and contributors. Community resources include: * documentation * package repositories * installation guides * forums == See Also == * [[Arch Linux]] * [[Kali Linux]] * [[Parrot Security OS]] * [[Linux]] * [[Cybersecurity]] == References == * https://blackarch.org/ * https://wiki.archlinux.org/ * https://github.com/BlackArch == External Links == * https://blackarch.org/downloads.html * https://blackarch.org/tools.html 9df53c7d271ae1106192f8fa928dd16d1bd7e212 4793 4783 2026-05-23T05:11:49Z Deviaze 341 Remove AI generated contributions wikitext text/x-wiki {{Stub}} '''BlackArch''' is a penetration testing and cybersecurity-focused Linux distribution based on [[Arch Linux]]. [[Category:Linux Distributions]] == External Links == * https://blackarch.org 3f2092d71c62d88160993ee697b7f95e87111c7a 4813 4793 2026-05-23T06:29:26Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Stub}} '''BlackArch''' is a penetration testing and cybersecurity-focused Linux distribution based on [[Arch Linux]]. == External Links == * https://blackarch.org 86fcc4a844529b15e0ce0aee140df54e5714260e 0 1145 4784 4764 2026-05-23T04:11:54Z Jokethatcake 333 wikitext text/x-wiki {{DistributionInfobox | title = Parrot OS | image = [[File:ParrotOSlogo.webp|thumb]] | caption = The Parrot OS logo | releasestatus = Maintained | releasemodel = Rolling release | basedon = [[Debian]] | packagemanager = APT | defaultdesktops = [[MATE]] | usagetype = Desktop, Security, Development | architectures = x86_64, ARM | init = systemd | license = Free and open-source software | website = [https://parrotsec.org/ parrotsec.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Privacy]] [[Category:Penetration Testing]] '''Parrot OS''' is a free and open-source Linux distribution focused on cybersecurity, penetration testing, digital forensics, privacy, and software development. It is developed by the '''Parrot Project''' and is based on [[Debian]]. Parrot OS ships with a large collection of security, forensic, cryptography, and privacy-oriented tools while also supporting general desktop usage. The distribution is commonly used by penetration testers, ethical hackers, developers, privacy-conscious users, and students learning cybersecurity. The system aims to provide a balance between security tooling, usability, lightweight performance, and privacy protection. == Overview == Parrot OS is designed as an all-in-one platform for: * Penetration testing * Vulnerability assessment * Digital forensics * Reverse engineering * Privacy protection * Secure development * Anonymous browsing Unlike some security distributions intended purely for offensive testing, Parrot OS also supports daily desktop usage with productivity applications and multimedia support. The default desktop environment is [[MATE]], chosen for its lightweight resource usage and stability. == Editions == Parrot OS is available in multiple editions tailored for different use cases. === Security Edition === The '''Security Edition''' is the flagship version and includes a large collection of offensive security and forensic tools. Common tool categories include: * Network analysis * Web exploitation * Wireless auditing * Reverse engineering * Cryptography * Digital forensics * Malware analysis * OSINT === Home Edition === The '''Home Edition''' removes most offensive security tools and focuses on privacy, development, and general desktop usage. It is intended for users who want: * A privacy-focused Linux desktop * Lightweight performance * Development tools * Secure communication utilities === Architect and Cloud Editions === Parrot also provides minimal and specialized images for: * Servers * Cloud deployments * Containers * Custom installations == Security Features == Parrot OS includes numerous security-oriented technologies and hardening mechanisms. === Sandboxing === Applications can be sandboxed using technologies such as: * Firejail * Linux namespaces * Seccomp This reduces the impact of compromised applications. === Privacy Tools === Parrot OS includes built-in privacy utilities such as: * Tor Browser * OnionShare * AnonSurf * Cryptographic utilities * Secure communication tools === AnonSurf === '''AnonSurf''' is a Parrot-specific utility that routes system traffic through the Tor network. It allows users to anonymize internet traffic system-wide while helping reduce direct IP exposure. === Cryptography Support === The distribution includes extensive cryptographic tooling for: * File encryption * Secure communication * Key management * Password auditing * Digital signatures == Penetration Testing == Parrot OS includes a large collection of penetration testing frameworks and utilities. Examples include: * Metasploit Framework * Burp Suite * Nmap * Wireshark * Aircrack-ng * Hydra * SQLMap * John the Ripper These tools are intended for authorized security testing and research. == Digital Forensics == Parrot OS includes forensic and incident response utilities used for: * File recovery * Memory analysis * Metadata extraction * Disk analysis * Malware investigation This makes the distribution useful for both offensive and defensive security workflows. == Development == Parrot OS supports software development with preinstalled or easily available tools for: * Python * C and C++ * Java * Docker * Git * Virtualization * Reverse engineering The distribution is commonly used by developers working in security research and exploit development. == System Requirements == Parrot OS is relatively lightweight compared to many security distributions. Typical minimum requirements include: * 64-bit processor * 2 GB RAM minimum * 20 GB storage * Internet connection for updates Recommended specifications are significantly higher for virtualization or heavy penetration testing workloads. == Package Management == Parrot OS uses the APT package manager inherited from [[Debian]]. Software can be installed through: * apt * Synaptic * Parrot repositories * Flatpak support The distribution follows a rolling release model with continuously updated packages. == Containers and Virtualization == Parrot OS supports: * Docker * Podman * KVM * VirtualBox * QEMU Security researchers often run Parrot OS inside isolated virtual environments for testing and analysis. == Comparison with Kali Linux == Parrot OS is frequently compared with [[Kali Linux]]. Differences commonly noted include: * Lighter default resource usage * Stronger emphasis on privacy tools * More suitable daily desktop experience * Different package selection and defaults Both distributions are widely used in cybersecurity environments. == Criticism == Common criticisms of Parrot OS include: * Large attack surface due to included tools * Rolling release instability risks * Potential misuse by inexperienced users * Security misconceptions among beginners Installing penetration testing tools alone does not make a system secure. == Use Cases == Parrot OS is commonly used for: * Ethical hacking * Cybersecurity education * Capture The Flag competitions * Privacy-focused desktop computing * Malware research * Secure development environments == See Also == * [[Debian]] * [[Kali Linux]] * [[Linux]] * [[Digital Forensics]] * [[Penetration Testing]] * [[Tor]] == External Links == * [https://parrotsec.org/ Official website] * [https://docs.parrotsec.org/ Official documentation] * [https://github.com/ParrotSec ParrotSec GitHub] e133d2d2a73bd4e314830db05f68418c762aa158 4785 4784 2026-05-23T04:18:43Z Jokethatcake 333 wikitext text/x-wiki {{DistributionInfobox | title = Parrot OS | caption = The Parrot OS logo | releasestatus = Maintained | releasemodel = Rolling release | basedon = [[Debian]] | packagemanager = APT | defaultdesktops = [[MATE]] | usagetype = Desktop, Security, Development | architectures = x86_64, ARM | init = systemd | license = Free and open-source software | website = [https://parrotsec.org/ parrotsec.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Privacy]] [[Category:Penetration Testing]] '''Parrot OS''' is a free and open-source Linux distribution focused on cybersecurity, penetration testing, digital forensics, privacy, and software development. It is developed by the '''Parrot Project''' and is based on [[Debian]]. Parrot OS ships with a large collection of security, forensic, cryptography, and privacy-oriented tools while also supporting general desktop usage. The distribution is commonly used by penetration testers, ethical hackers, developers, privacy-conscious users, and students learning cybersecurity. The system aims to provide a balance between security tooling, usability, lightweight performance, and privacy protection. == Overview == Parrot OS is designed as an all-in-one platform for: * Penetration testing * Vulnerability assessment * Digital forensics * Reverse engineering * Privacy protection * Secure development * Anonymous browsing Unlike some security distributions intended purely for offensive testing, Parrot OS also supports daily desktop usage with productivity applications and multimedia support. The default desktop environment is [[MATE]], chosen for its lightweight resource usage and stability. == Editions == Parrot OS is available in multiple editions tailored for different use cases. === Security Edition === The '''Security Edition''' is the flagship version and includes a large collection of offensive security and forensic tools. Common tool categories include: * Network analysis * Web exploitation * Wireless auditing * Reverse engineering * Cryptography * Digital forensics * Malware analysis * OSINT === Home Edition === The '''Home Edition''' removes most offensive security tools and focuses on privacy, development, and general desktop usage. It is intended for users who want: * A privacy-focused Linux desktop * Lightweight performance * Development tools * Secure communication utilities === Architect and Cloud Editions === Parrot also provides minimal and specialized images for: * Servers * Cloud deployments * Containers * Custom installations == Security Features == Parrot OS includes numerous security-oriented technologies and hardening mechanisms. === Sandboxing === Applications can be sandboxed using technologies such as: * Firejail * Linux namespaces * Seccomp This reduces the impact of compromised applications. === Privacy Tools === Parrot OS includes built-in privacy utilities such as: * Tor Browser * OnionShare * AnonSurf * Cryptographic utilities * Secure communication tools === AnonSurf === '''AnonSurf''' is a Parrot-specific utility that routes system traffic through the Tor network. It allows users to anonymize internet traffic system-wide while helping reduce direct IP exposure. === Cryptography Support === The distribution includes extensive cryptographic tooling for: * File encryption * Secure communication * Key management * Password auditing * Digital signatures == Penetration Testing == Parrot OS includes a large collection of penetration testing frameworks and utilities. Examples include: * Metasploit Framework * Burp Suite * Nmap * Wireshark * Aircrack-ng * Hydra * SQLMap * John the Ripper These tools are intended for authorized security testing and research. == Digital Forensics == Parrot OS includes forensic and incident response utilities used for: * File recovery * Memory analysis * Metadata extraction * Disk analysis * Malware investigation This makes the distribution useful for both offensive and defensive security workflows. == Development == Parrot OS supports software development with preinstalled or easily available tools for: * Python * C and C++ * Java * Docker * Git * Virtualization * Reverse engineering The distribution is commonly used by developers working in security research and exploit development. == System Requirements == Parrot OS is relatively lightweight compared to many security distributions. Typical minimum requirements include: * 64-bit processor * 2 GB RAM minimum * 20 GB storage * Internet connection for updates Recommended specifications are significantly higher for virtualization or heavy penetration testing workloads. == Package Management == Parrot OS uses the APT package manager inherited from [[Debian]]. Software can be installed through: * apt * Synaptic * Parrot repositories * Flatpak support The distribution follows a rolling release model with continuously updated packages. == Containers and Virtualization == Parrot OS supports: * Docker * Podman * KVM * VirtualBox * QEMU Security researchers often run Parrot OS inside isolated virtual environments for testing and analysis. == Comparison with Kali Linux == Parrot OS is frequently compared with [[Kali Linux]]. Differences commonly noted include: * Lighter default resource usage * Stronger emphasis on privacy tools * More suitable daily desktop experience * Different package selection and defaults Both distributions are widely used in cybersecurity environments. == Criticism == Common criticisms of Parrot OS include: * Large attack surface due to included tools * Rolling release instability risks * Potential misuse by inexperienced users * Security misconceptions among beginners Installing penetration testing tools alone does not make a system secure. == Use Cases == Parrot OS is commonly used for: * Ethical hacking * Cybersecurity education * Capture The Flag competitions * Privacy-focused desktop computing * Malware research * Secure development environments == See Also == * [[Debian]] * [[Kali Linux]] * [[Linux]] * [[Digital Forensics]] * [[Penetration Testing]] * [[Tor]] == External Links == * [https://parrotsec.org/ Official website] * [https://docs.parrotsec.org/ Official documentation] * [https://github.com/ParrotSec ParrotSec GitHub] 5f6934b6ca46100aec7b965f6e650811c78964e8 0 1040 4789 4763 2026-05-23T05:04:15Z Deviaze 341 Remove AI generated contributions. wikitext text/x-wiki {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = DNF, APT | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = systemd | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Qubes OS separates applications and workflows into isolated compartments known as '''qubes'''. == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] 2ec60614e118e7547aafc913157c5006ceb49e57 4790 4789 2026-05-23T05:06:32Z Deviaze 341 wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = DNF, APT | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = systemd | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Qubes OS separates applications and workflows into isolated compartments known as '''qubes'''. == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] 8ddc5e01c01c4319df57fbc1537bb7765e916903 0 679 4791 4125 2026-05-23T05:07:14Z MarkH 357 Update version; link to Linux kernel, not Linux distributions wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.54.0 (2026-04-20) [https://git-scm.com/] | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git's early design emphasized a distributed workflow similar to BitKeeper's but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like [[GitHub]], which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. == References == 02602b58cfa17378c392f5910e058eff75c55219 6 1162 4795 2026-05-23T05:25:16Z Ciinamon 368 wikitext text/x-wiki Screenshot of APK being used to install GCC on Alpine Linux 7fd7abf3f1deb5f6ba4749d54bbbcc1984aa03c1 6 1163 4796 2026-05-23T05:27:22Z Ciinamon 368 wikitext text/x-wiki Screenshot of APK being used to install GCC on Alpine Linux. 08c27d516fcade2543ae071821bf210d09a67554 0 1144 4797 4761 2026-05-23T05:49:12Z Madonuko 140 format wikitext text/x-wiki {{Work In Progress}} [[File:2019 02 Microsoft Surface Pro 2017 with signature type cover.jpg|alt=Picture shows a Microsoft Surface Pro 5th Generation from 2017 with the Alcantara type cover running Windows :<|thumb|A Microsoft Surface Pro 2017 (5th Generation)]]{{GuideWarning}}With the release of the Microsoft Surface line-up (including the Surface Pro, Go, Laptop series), majority of these devices have support for [[Linux Distributions]], but often have issues with device hardware support on stock installs. The community-maintained "Linux Surface<ref>{{Cite|url=https://github.com/linux-surface/linux-surface|title=Linux Surface|accessdate=2026}}</ref>" provides a [[kernel]] that aims to fix compatibility issues with the Surface-specific hardware, such as Wi-Fi, touchscreen, pen input, sensors, and cameras. == Supported Surface Devices == === Surface on x86_64 === These are majority of the devices that Microsoft has released, seceding the Surface RT line-up. These are the models as follows # Surface Book # Surface Go # Surface Laptop (Excluding Surface Laptop 7) # Surface Laptop Studio # Surface Pro (Excluding Surface Pro X, Surface Pro 9, Surface Pro 11 Snapdragon, Surface Pro 12") # Surface Studio (Untested Support) Although not all devices are as supported, the feature matrix shows the hardware compatibility and guide on installation with the linux-surface kernel. To get started with installation, use the [https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup Installation and Setup] guide from the Linux-surface GitHub. === Surface on arm32 (Aarch32) === These devices were released from Microsoft under the Surface RT lineup. Although these devices don't fall under the linux-surface kernel support, they instead utilize the "Open SurfaceRT<ref>{{Cite|url=https://open-rt.gitbook.io/open-surfacert|title=Open SurfaceRT|accessdate=2026}}</ref>" guide, as well as other user created guides. == References == 840177c099b6d53c6d8426ca3d0fe1443cc2b1d1 0 1142 4798 4748 2026-05-23T05:50:11Z Madonuko 140 format; stub wikitext text/x-wiki {{stub}} Windows is a proprietary [[Operating System]] that was developed and is released under Microsoft. While originally catered towards personal computers, Windows now offers versions such as Windows Server, Windows IoT, or Windows LTSC. The first version of its cited release was in November 20, 1985 as Windows 1.0, with a graphical user interface.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Microsoft_Windows|title=Microsoft Windows Wikipedia Entry|accessdate=2026}}</ref> == References == 018bf0132cc9d15d08cc9cbd45aec8993e66be48 0 558 4799 4676 2026-05-23T05:53:07Z MarkH 357 Update version, fix Linux kernel link wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.95.0 (2026-04-16)<ref>[https://blog.rust-lang.org/2026/04/16/Rust-1.95.0/ Announcing Rust 1.95.0], The Rust Release Team, April 16 2026 (Accessed: May 22 2026)</ref> | languages = [[Rust]], originally written in [[OCaml]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust is a modern multi-paradigm programming language with a focus on performance, reliability, and productivity<ref>https://github.com/rust-lang/rust</ref>. Although originally designed as a systems-level language, Rust has found widespread adoption as a general purpose programming language thanks to its high degree of expressiveness, strict type safety and memory safety, its easy-to-use package manager Cargo and crates ecosystem, and its ability to achieve native performance with high level code. Rust was heavily inspired by functional programming languages in its emphasis on immutability and pattern matching, as well as by [[C++]] for its RAII (resource allocation is initialization) and other performance features. Rust is most often compared with and considered an alternative to C++. In 2025, Rust was officially accepted into the [[Linux kernel]]<ref>https://www.phoronix.com/news/Rust-To-Stay-Linux-Kernel</ref>, after a lengthy trial period (the Rust for Linux experiment) that started in December 2022, becoming the third language accepted in the kernel after [[C]] and [[assembly]]. [[Canonical]], the company behind Ubuntu and other FOSS, is replacing the GNU coreutils project, written in C, with uutils, a Rust rewrite<ref>https://archive.fosdem.org/2025/schedule/event/fosdem-2025-6196-rewriting-the-future-of-the-linux-essential-packages-in-rust-/</ref>. This has attracted criticism around its licensing changing from GNU GPL to [[MIT License|MIT]] and makes uutils more friendly to proprietary software<ref>https://github.com/uutils/coreutils/issues/834</ref>. === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Data Types === Rust has a number of primitive builtin types, denoted in lowercase, as well as complex objects from the standard library that behave like primitives in other languages. {| class="wikitable" |+Primitive integer types (signed/unsigned) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} Rust does not have a single string type; below is a non-comprehensive list of the most common ways to represent a string: {| class="wikitable" |+String types !Name !Stack or heap !Description |- |<code>&str</code> |Stack |A reference to a UTF-8 string slice, <code>str</code>only really exists as a reference type. These are immutable. |- |<code>&'static str</code> |Stack |The type of a string literal embedded into sourcecode. The <code>'static</code> lifetime means that the <code>&str</code> lasts forever. |- |<code>char</code> |Stack |Represents a single UTF-8 codepoint. |- |<code>String</code> |Heap |A full heap-allocated, possibly mutable UTF-8 string. |- |<code>Vec<u8></code> |Heap |A heap-allocated list of arbitrary bytes; it's not actually a string, but it's commonly used instead of a <code>String</code> when you want to represent data that isn't necessarily UTF-8 encoded. |- |<code>Cow</code> |Might be either |Stands for copy-on-write. |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. [[OO]]P allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref><ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref> Rust takes a different approach to OOP with its use of <code>struct</code>s, <code>trait</code>s, <code>enum</code>s, and <code>impl</code>s.<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, <code>struct</code>s in Rust can store multiple related values as fields. The difference is that fields must be referred via their given naming. <code>struct</code>s are more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> <syntaxhighlight lang="rust" lines> // Having the struct outside of main() makes it available everywhere in the file struct MyStruct { field1: bool, field2: i32, field3: String, } fn main() { let object = MyStruct { field1: true, field2: 64, field3: String::from("Use structs you must!"), }; } </syntaxhighlight> Functional properties may be given to <code>struct</code>s with <code>impl</code>s, which stands for ''implement''. Having methods (i.e. functions in <code>impl</code> with <code>self</code>, <code>&self</code> or <code>&mut self</code> as the first parameter) also allows for reproducibility, since they can access <code>struct</code> fields via <code>self</code>. <ref name=":0" /><ref name=":2" /> <syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height } } fn main() { let rubiks_cube = Cube { length: 3, width: 3, height: 3, }; println!("Cube's volume: {}", rubiks_cube.volume()); } </syntaxhighlight> The code declares a new struct with 3 values and an area finder function within the <code>impl Cube</code> scope. The <code>volume()</code> method may be used on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == 771dc085f9554f8c375b5df109f8c1affb5ddfaa 0 396 4800 4755 2026-05-23T05:59:01Z Thatonecoder 369 Create a gaming category, add Geany as a text editor, add KeePassXC as a text editor wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} 2379b579c281ce8b93fc7ebbf8fdbad99a19513d 3001 1164 4801 2026-05-23T06:01:37Z Madonuko 140 /* Soundness of This Guide */ new section wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) b0e14203b951796e790cf687bb7d942987f8d839 4810 4801 2026-05-23T06:27:33Z Deviaze 341 /* Soundness of This Guide */ Reply wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) :Addressed the criticisms to reduce bias. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:27, 23 May 2026 (UTC) 01fb6539cac3cb9482715c42262bab52e1a2a840 4811 4810 2026-05-23T06:28:51Z Deviaze 341 /* What distros do we feel comfortable recommending. */ new section wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) :Addressed the criticisms to reduce bias. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:27, 23 May 2026 (UTC) == What distros do we feel comfortable recommending. == I agree that it's not very unbiased of us to recommend specific distros when Many Distros Exist, however I feel as a resource we need to be approachable to the community and **helpful** to new users who may not know about all the issues that plague distros that aren't often recommended anymore (such as Pop!_OS and Manjaro). It would be good if we got a list of modern, commonly recommended distros that we know are reliable that we feel comfortable recommending to new Linux users. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:28, 23 May 2026 (UTC) b9666484683bc6e993a734d899698530325219e4 4812 4811 2026-05-23T06:29:10Z Deviaze 341 /* What distros do we feel comfortable recommending. */ wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) :Addressed the criticisms to reduce bias. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:27, 23 May 2026 (UTC) == What distros do we feel comfortable recommending? == I agree that it's not very unbiased of us to recommend specific distros when Many Distros Exist, however I feel as a resource we need to be approachable to the community and **helpful** to new users who may not know about all the issues that plague distros that aren't often recommended anymore (such as Pop!_OS and Manjaro). It would be good if we got a list of modern, commonly recommended distros that we know are reliable that we feel comfortable recommending to new Linux users. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:28, 23 May 2026 (UTC) 25d25259ef2e3f999be0178ef98c7c6f202005df 0 198 4802 4749 2026-05-23T06:03:30Z Thatonecoder 369 Add Chimera Linux, standardize spaces. wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Red Hat Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Atomic]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 6021fd7052e3605d145f07dc48abf3e34f246e0a 0 1115 4803 4629 2026-05-23T06:10:35Z Madonuko 140 format; stub wikitext text/x-wiki [[Category:Desktop Environments]] {{stub}} COSMIC is a FOSS Desktop Environment created by [[System76]], Also known as the creators of [[Pop!_OS]]. Originally a modified version of the [[GNOME]] Desktop Environment, System76 released their Alpha version of their in-house DE written in the [[Rust]] Programming Language on August 8th 2024. The current stable release is 1.0.13, Released on May 12, 2026. bfb36c40adcce54fc47f016abf80b192349533b4 0 1120 4804 4712 2026-05-23T06:14:22Z Madonuko 140 /* References */ wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim|NeoVim]] instead for a more modern editor and backwards compatible editor. ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use the <code>vimtutor</code> command. <code>Vim ''path/to/filename'' </code> is used to open a new or existing file for editing, though you can also open a file from within Vim. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or [[symlink]]<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] == References == <references /> 558487a8ed663fff62b29a5115168b55da75252e 0 394 4805 4657 2026-05-23T06:22:14Z GentooLaws 370 Added Microkernel-based table wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other UNIX-like ==== {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} ==== Microkernel-based Systems ==== {| class="wikitable" |- ! OS !! Description ! |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] | |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} caa940d8bb16a08dd1158bd7c64cea516a5e457a 4806 4805 2026-05-23T06:24:13Z GentooLaws 370 renamed microkernel table to L4 table wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other UNIX-like ==== {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- |} ==== L4-based Systems ==== {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} 5d527c7ffc51d7f249d738752b91f7060e99dbc3 4808 4806 2026-05-23T06:25:03Z GentooLaws 370 Added Hurd to Other Unix-like table wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other UNIX-like ==== {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} ==== L4-based Systems ==== {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} 354ef343c5c289e1021b3b5ec768e413783959a9 4809 4808 2026-05-23T06:26:11Z GentooLaws 370 corrected L4 based systems table to be consistent with other tables wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel ==== BSD Based ==== {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} ==== Darwin Based ==== {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} ==== Solaris Based ==== {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} ==== Other UNIX-like ==== {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} ==== L4 based ==== {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} ==== Other Operating Systems ==== {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} 7d00ca70196ee5678c4f0064150bf236912f7534 3000 1136 4807 4742 2026-05-23T06:24:27Z Deviaze 341 Reduce bias wikitext text/x-wiki {{Work In Progress}} Welcome to the penguin side! Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable as the operating system you use today in no time. === Why switch? === People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. === Choices === Linux is all about choices. Before you start, you need to pick what your Linux looks like and what it runs under the hood. The GUI you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. === Picking a Linux distribution ===<!-- Discuss on talk page before modifying this section due to potential for bias. --> There are many flavors of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]]. If you don't like the Linux you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a GUI === When you install a Linux, the installer asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on touchpad gestures consider [[GNOME]]. ff4c209f93f71adddced101487d3044fe74a665e 3001 1164 4820 4812 2026-05-23T06:33:18Z GentooLaws 370 /* What distros do we feel comfortable recommending? */ Reply wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) :Addressed the criticisms to reduce bias. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:27, 23 May 2026 (UTC) == What distros do we feel comfortable recommending? == I agree that it's not very unbiased of us to recommend specific distros when Many Distros Exist, however I feel as a resource we need to be approachable to the community and **helpful** to new users who may not know about all the issues that plague distros that aren't often recommended anymore (such as Pop!_OS and Manjaro). It would be good if we got a list of modern, commonly recommended distros that we know are reliable that we feel comfortable recommending to new Linux users. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:28, 23 May 2026 (UTC) :Debian was my first distro and it is truly a distro for all seasons, the caveats with debian is that its coupled to systemd unless you manually migrate it to devuan but otherwise pretty solid considering it doesn't spoonfeed too much [[User:GentooLaws|GentooLaws]] ([[User talk:GentooLaws|talk]]) 06:33, 23 May 2026 (UTC) 69e05ffcd95bd429ef3435d345b728d986e235a3 4836 4820 2026-05-23T06:41:44Z Scottc96 18 /* What distros do we feel comfortable recommending? */ Reply wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) :Addressed the criticisms to reduce bias. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:27, 23 May 2026 (UTC) == What distros do we feel comfortable recommending? == I agree that it's not very unbiased of us to recommend specific distros when Many Distros Exist, however I feel as a resource we need to be approachable to the community and **helpful** to new users who may not know about all the issues that plague distros that aren't often recommended anymore (such as Pop!_OS and Manjaro). It would be good if we got a list of modern, commonly recommended distros that we know are reliable that we feel comfortable recommending to new Linux users. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:28, 23 May 2026 (UTC) :Debian was my first distro and it is truly a distro for all seasons, the caveats with debian is that its coupled to systemd unless you manually migrate it to devuan but otherwise pretty solid considering it doesn't spoonfeed too much [[User:GentooLaws|GentooLaws]] ([[User talk:GentooLaws|talk]]) 06:33, 23 May 2026 (UTC) :I feel like [https://www.linuxliteos.com/ linux lite] is a great beginner distro, I learned about it a few months ago when helping someone out with it. Ultramarine/Fedora have always been my go to recommendations. Bazzite is interesting for new users as well due to the gaming setup out of the box since many think "oh you need to do X,Y,Z, and more" just to get games to work on Linux from what I have seen irl. [[User:Scottc96|Scottc96]] ([[User talk:Scottc96|talk]]) 06:41, 23 May 2026 (UTC) 6a89f8bfce3be269f5acfb8e708591d74f793cc3 4838 4836 2026-05-23T06:46:05Z Deviaze 341 /* Soundness of This Guide */ Reply wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) :Addressed the criticisms to reduce bias. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:27, 23 May 2026 (UTC) :I think we should have a new discussion wrt. if we should recommend distros, and how we should do so. :There is value in being able to recommend distros, especially in an environment where chatbots and LLMs have outdated information and new users don't have up-to-date, reliable information about what distros are currently the most reliable and beginner-friendly, as said info would be mostly discussed on Discord, Reddit, etc., and not in an authoritative format. :As "thatonecoder" on Discord stated: :"Precisely; decision paralysis is an issue, and we cannot dismiss it simply on the grounds of remaining unbiased." [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:46, 23 May 2026 (UTC) == What distros do we feel comfortable recommending? == I agree that it's not very unbiased of us to recommend specific distros when Many Distros Exist, however I feel as a resource we need to be approachable to the community and **helpful** to new users who may not know about all the issues that plague distros that aren't often recommended anymore (such as Pop!_OS and Manjaro). It would be good if we got a list of modern, commonly recommended distros that we know are reliable that we feel comfortable recommending to new Linux users. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:28, 23 May 2026 (UTC) :Debian was my first distro and it is truly a distro for all seasons, the caveats with debian is that its coupled to systemd unless you manually migrate it to devuan but otherwise pretty solid considering it doesn't spoonfeed too much [[User:GentooLaws|GentooLaws]] ([[User talk:GentooLaws|talk]]) 06:33, 23 May 2026 (UTC) :I feel like [https://www.linuxliteos.com/ linux lite] is a great beginner distro, I learned about it a few months ago when helping someone out with it. Ultramarine/Fedora have always been my go to recommendations. Bazzite is interesting for new users as well due to the gaming setup out of the box since many think "oh you need to do X,Y,Z, and more" just to get games to work on Linux from what I have seen irl. [[User:Scottc96|Scottc96]] ([[User talk:Scottc96|talk]]) 06:41, 23 May 2026 (UTC) 50236bcb6fac04183ee49e727c39e9f9699592c8 4840 4838 2026-05-23T06:50:45Z Ping 374 /* What distros do we feel comfortable recommending? */ Reply wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) :Addressed the criticisms to reduce bias. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:27, 23 May 2026 (UTC) :I think we should have a new discussion wrt. if we should recommend distros, and how we should do so. :There is value in being able to recommend distros, especially in an environment where chatbots and LLMs have outdated information and new users don't have up-to-date, reliable information about what distros are currently the most reliable and beginner-friendly, as said info would be mostly discussed on Discord, Reddit, etc., and not in an authoritative format. :As "thatonecoder" on Discord stated: :"Precisely; decision paralysis is an issue, and we cannot dismiss it simply on the grounds of remaining unbiased." [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:46, 23 May 2026 (UTC) == What distros do we feel comfortable recommending? == I agree that it's not very unbiased of us to recommend specific distros when Many Distros Exist, however I feel as a resource we need to be approachable to the community and **helpful** to new users who may not know about all the issues that plague distros that aren't often recommended anymore (such as Pop!_OS and Manjaro). It would be good if we got a list of modern, commonly recommended distros that we know are reliable that we feel comfortable recommending to new Linux users. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:28, 23 May 2026 (UTC) :Debian was my first distro and it is truly a distro for all seasons, the caveats with debian is that its coupled to systemd unless you manually migrate it to devuan but otherwise pretty solid considering it doesn't spoonfeed too much [[User:GentooLaws|GentooLaws]] ([[User talk:GentooLaws|talk]]) 06:33, 23 May 2026 (UTC) :I feel like [https://www.linuxliteos.com/ linux lite] is a great beginner distro, I learned about it a few months ago when helping someone out with it. Ultramarine/Fedora have always been my go to recommendations. Bazzite is interesting for new users as well due to the gaming setup out of the box since many think "oh you need to do X,Y,Z, and more" just to get games to work on Linux from what I have seen irl. [[User:Scottc96|Scottc96]] ([[User talk:Scottc96|talk]]) 06:41, 23 May 2026 (UTC) :Every distro has its own problems. It is like better to give a few distros that are well-established and possibly have a caveats page somewhere. Here are some notable examples: :- Mint: caveats with X11, specifically it's incapability to do HDR and weirdness with multi-monitor (probably need more expanding, but something like Xinerama is not perfect iirc and still would be wacky with many different refresh rate monitors). Probably need an accompanied X11 and Wayland difference page regarding this. :- Fedora: caveats with drivers and codecs, which are only using free-licensed ones by default and needing to go through installation via RPMFusion or Terra to have them be installed properly. :- Ubuntu: caveats with using snap store as the default store. This is problematic with some applications, notably Steam, not properly working as intended. The fix to this is to use the steam's deb repository [[User:Ping|Ping]] ([[User talk:Ping|talk]]) 06:50, 23 May 2026 (UTC) 4a9300f50708af562e85e156e4fb1dcf77eb04f4 0 1153 4821 4775 2026-05-23T06:34:55Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Containers]] [[Category:Virtualization]] [[Category:Linux]] [[Category:Free Software]] '''Containers''' are isolated user-space environments used to package and run applications together with their dependencies while sharing the host operating system kernel. Containers are widely used in: * cloud computing * software development * DevOps * server infrastructure * application deployment Container technologies are commonly associated with Linux and modern open-source infrastructure platforms. == Overview == Containers provide lightweight isolation between applications. Unlike traditional virtual machines, containers do not emulate full hardware or run separate kernels. Instead, they share the host operating system kernel while maintaining isolated: * filesystems * processes * networking * users * resource limits This allows containers to use fewer system resources and start significantly faster than virtual machines. == Linux Containers == Modern container systems on Linux commonly rely on kernel technologies such as: * namespaces * cgroups * seccomp * capabilities These mechanisms provide process isolation and resource control. === Namespaces === Namespaces isolate system resources between containers. Examples include: * process IDs * networking * mount points * hostnames * users === cgroups === Control groups (cgroups) limit and manage resource usage such as: * CPU * memory * disk I/O * network bandwidth == Container Images == Containers are typically created from '''container images'''. An image contains: * application binaries * libraries * dependencies * runtime configurations Images are designed to be portable and reproducible across systems. == Container Engines == A '''container engine''' is software used to create and manage containers. Popular open-source container engines include: * [[Docker]] * Podman * containerd * CRI-O * LXC == Comparison with Virtual Machines == Containers differ from traditional virtual machines. Containers: * share the host kernel * start quickly * use fewer resources * are lightweight Virtual machines: * emulate full hardware * run separate kernels * provide stronger isolation Containers are generally more efficient, while virtual machines usually provide stronger security boundaries. == Security == Containers improve workload isolation but are not equivalent to full hardware virtualization. Security technologies commonly used with containers include: * seccomp filtering * AppArmor * SELinux * rootless containers * capability restrictions === Container Escapes === A '''container escape''' occurs when software inside a container gains unauthorized access to the host system. Kernel vulnerabilities and misconfigurations may increase this risk. == Orchestration == Large-scale container deployments often use orchestration systems such as: * Kubernetes * Docker Swarm * Nomad These systems automate: * deployment * scaling * networking * fault recovery == Use Cases == Containers are commonly used for: * microservices * cloud applications * CI/CD pipelines * development environments * software testing * server hosting == Open-Source Ecosystem == Container technology is heavily associated with the free and open-source software ecosystem. Many major container projects are open-source, including: * Docker * Kubernetes * Podman * containerd * LXC Linux containers have become foundational infrastructure for modern cloud computing and DevOps environments. == See Also == * [[Docker]] * [[Kubernetes]] * [[Virtualization]] * [[Linux]] * [[Hypervisor]] == References == * https://www.docker.com/ * https://kubernetes.io/ * https://podman.io/ * https://linuxcontainers.org/ == External Links == * https://containerd.io/ * https://opencontainers.org/ 907e8527e5ad1806b74a7782db0aa6c87afdec35 0 1152 4822 4774 2026-05-23T06:35:04Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Containers]] [[Category:Virtualization]] [[Category:DevOps]] [[Category:Free Software]] '''Docker''' is a free and open-source platform used for developing, packaging, distributing, and running applications inside isolated environments known as '''containers'''. Docker allows applications and their dependencies to be packaged into portable container images that can run consistently across different systems and environments. The platform is widely used in: * cloud computing * software development * DevOps workflows * server infrastructure * continuous integration and deployment == Overview == Docker uses operating-system-level virtualization to isolate applications from the host system and from each other. Unlike traditional virtual machines, Docker containers share the host operating system kernel while maintaining separate: * filesystems * processes * networking * resource limits This makes containers significantly lighter and faster than full virtual machines. == Containers == A '''container''' is an isolated runtime environment containing: * application code * libraries * dependencies * runtime configurations Containers are designed to be: * portable * reproducible * lightweight * scalable A container image can usually run consistently across multiple systems regardless of underlying infrastructure. == Docker Engine == '''Docker Engine''' is the core runtime responsible for creating and managing containers. It includes: * the Docker daemon * container runtime components * networking systems * storage management The daemon runs in the background and manages container operations. == Docker Images == A '''Docker image''' is a read-only template used to create containers. Images commonly contain: * operating system components * application binaries * dependencies * configuration files Docker images are layered to improve storage efficiency and caching. === Dockerfile === A '''Dockerfile''' is a text file containing instructions used to build Docker images. Common instructions include: * FROM * RUN * COPY * CMD * ENTRYPOINT Dockerfiles help automate reproducible application environments. == Docker Hub == '''Docker Hub''' is a public container registry used to distribute container images. Users can: * upload images * download images * share containers * automate builds Private registries may also be used for enterprise environments. == Container Isolation == Docker containers use Linux kernel technologies for isolation. These include: * namespaces * cgroups * seccomp * capabilities * AppArmor * SELinux Isolation helps separate containers from one another and from the host system. == Networking == Docker provides multiple networking modes. Common modes include: * bridge networking * host networking * overlay networking * macvlan networking Containers can communicate with: * external networks * the host system * other containers depending on configuration. == Storage == Docker supports persistent data storage through: * volumes * bind mounts * tmpfs mounts Containers themselves are generally considered ephemeral, while persistent data is stored separately. == Docker Compose == '''Docker Compose''' is a tool used to define and manage multi-container applications. Compose uses YAML configuration files to describe: * services * networks * volumes * environment variables This simplifies deployment of complex containerized applications. == Orchestration == Large-scale Docker deployments often use orchestration platforms such as: * Kubernetes * Docker Swarm * Nomad These systems automate: * scaling * deployment * networking * fault recovery == Security == Docker containers improve isolation but are not equivalent to full virtual machines. Security features include: * namespace isolation * resource limitations * capability restrictions * seccomp filtering However, containers still share the host kernel. === Container Escapes === A '''container escape''' occurs when a process inside a container breaks isolation and gains access to the host system. Misconfiguration or kernel vulnerabilities may increase this risk. === Rootless Containers === Docker supports '''rootless mode''' which allows containers to run without root privileges on the host. This reduces some security risks. == Comparison with Virtual Machines == Docker containers differ from traditional virtual machines. Containers: * share the host kernel * start quickly * consume fewer resources Virtual machines: * emulate full hardware * run separate kernels * provide stronger isolation Containers are generally lighter, while virtual machines provide stronger security boundaries. == Use Cases == Docker is commonly used for: * application deployment * microservices * development environments * CI/CD pipelines * testing * cloud infrastructure == Criticism == Common criticisms of Docker include: * security concerns from shared kernels * container sprawl * complexity in orchestration * networking complexity * resource management challenges == See Also == * [[Containers]] * [[Virtualization]] * [[Kubernetes]] * [[Linux]] * [[Hypervisor]] == References == * https://www.docker.com/ * https://docs.docker.com/ * https://github.com/docker == External Links == * https://hub.docker.com/ * https://docs.docker.com/get-started/ 8c5759999089fa9aff7c8a5c58a137fc83375d91 0 1151 4823 4773 2026-05-23T06:35:14Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Virtualization]] [[Category:Computing]] [[Category:Security]] '''Hypervisor''' is software that creates and manages virtual machines by allowing multiple operating systems to share the same physical hardware while remaining isolated from each other. Hypervisors are a core component of modern virtualization technologies and are widely used in: * cloud computing * enterprise servers * desktop virtualization * cybersecurity * research environments A hypervisor allocates hardware resources such as: * CPU time * memory * storage * networking * device access to virtual machines known as '''guests'''. == Overview == A hypervisor sits between the hardware and guest operating systems. It allows multiple operating systems to run simultaneously on one physical machine while keeping them isolated. Each guest operating system behaves similarly to a normal computer with virtualized: * processors * memory * disks * network adapters * hardware devices The hypervisor controls access to physical hardware and ensures separation between guests. == Types of Hypervisors == Hypervisors are generally divided into two categories. === Type-1 Hypervisors === '''Type-1 hypervisors''' run directly on physical hardware and are often called '''bare-metal hypervisors'''. Examples include: * [[Xen]] * VMware ESXi * Hyper-V Advantages include: * stronger isolation * lower overhead * improved scalability * direct hardware access Type-1 hypervisors are commonly used in servers and cloud infrastructure. === Type-2 Hypervisors === '''Type-2 hypervisors''' run on top of an existing operating system. Examples include: * VirtualBox * VMware Workstation * QEMU Advantages include: * easier setup * desktop usability * convenient testing However, they usually have more overhead compared to type-1 hypervisors. == Virtual Machines == A '''virtual machine''' (VM) is an isolated environment managed by a hypervisor. Each VM may run: * Linux * Windows * BSD systems * other operating systems Virtual machines usually contain: * virtual CPUs * allocated memory * virtual storage * virtual networking devices == Hardware Virtualization == Modern hypervisors use hardware-assisted virtualization technologies such as: * Intel VT-x * AMD-V These CPU extensions improve: * performance * compatibility * isolation * virtualization efficiency Additional technologies such as IOMMU support allow secure device passthrough. == Memory Management == Hypervisors manage memory allocation between guest systems. Common features include: * dynamic allocation * memory ballooning * memory isolation * page sharing Strong memory separation is important for virtualization security. == CPU Scheduling == The hypervisor schedules CPU time between guest operating systems. Scheduling systems attempt to balance: * performance * fairness * responsiveness * resource efficiency Some hypervisors support CPU pinning for dedicated workloads. == Virtual Networking == Hypervisors provide virtual networking infrastructure for guest systems. Supported networking methods often include: * NAT * bridged networking * isolated internal networks * VLAN integration Virtual machines may communicate with: * the host * external networks * other guests depending on configuration. == Storage == Hypervisors support multiple virtual storage systems including: * disk image files * logical volumes * network storage * snapshots Snapshots allow virtual machine states to be saved and restored. == Device Passthrough == Some hypervisors support direct assignment of physical hardware devices to guests. Examples include: * GPUs * USB controllers * network cards * storage controllers This improves hardware compatibility and performance. == Security == Hypervisors are commonly used for security isolation and sandboxing. Benefits include: * workload separation * malware containment * isolated testing environments * reduced attack surface Security-focused operating systems such as [[Qubes OS]] rely heavily on hypervisor-based isolation. === VM Escapes === A '''VM escape''' occurs when software inside a guest system breaks isolation and compromises the host or other guests. These vulnerabilities are considered critical security issues. === Sandboxing === Hypervisors are frequently used to sandbox: * untrusted applications * malware samples * exploit testing environments == Cloud Computing == Hypervisors are foundational technology for cloud computing platforms. Cloud providers use hypervisors to: * isolate customers * allocate resources dynamically * scale infrastructure * deploy virtual servers rapidly == Advantages == Benefits of hypervisors include: * hardware consolidation * improved resource utilization * workload isolation * scalability * portability == Limitations == Common limitations include: * performance overhead * hardware compatibility issues * increased complexity * hypervisor attack surface A compromised hypervisor may affect all hosted virtual machines. == Use Cases == Hypervisors are commonly used for: * server virtualization * cloud infrastructure * software testing * malware analysis * desktop virtualization * cybersecurity research == See Also == * [[Virtualization]] * [[Xen]] * [[Qubes OS]] * [[Linux]] * [[Docker]] == References == * https://xenproject.org/ * https://learn.microsoft.com/en-us/virtualization/ * https://www.redhat.com/en/topics/virtualization == External Links == * https://www.virtualbox.org/ * https://www.vmware.com/ e0db0e72aac877bf149ea4519b1cd6fd4afc6907 0 1150 4824 4772 2026-05-23T06:35:26Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Virtualization]] [[Category:Computing]] [[Category:Security]] '''Virtualization''' is the process of creating virtual versions of computing resources such as operating systems, servers, storage devices, networks, or hardware platforms. It allows multiple isolated environments to run on a single physical machine. Virtualization is widely used in: * cloud computing * server infrastructure * software testing * cybersecurity * desktop environments * research systems The technology improves hardware utilization, scalability, isolation, portability, and resource management. == Overview == In a virtualized environment, software known as a '''hypervisor''' manages and allocates hardware resources to multiple virtual machines. Each virtual machine behaves similarly to an independent physical computer and may run its own: * operating system * applications * networking stack * storage environment Virtualization allows different operating systems to coexist simultaneously on the same hardware. == Hypervisors == A '''hypervisor''' is software responsible for creating and managing virtual machines. There are two major types of hypervisors. === Type-1 Hypervisors === Type-1 hypervisors run directly on hardware and are also known as '''bare-metal hypervisors'''. Examples include: * [[Xen]] * VMware ESXi * Hyper-V Advantages include: * strong isolation * lower overhead * enterprise scalability * direct hardware access === Type-2 Hypervisors === Type-2 hypervisors run on top of an existing operating system. Examples include: * VirtualBox * VMware Workstation * QEMU Advantages include: * easier setup * desktop usability * convenient testing environments However, they generally have more overhead than type-1 hypervisors. == Virtual Machines == A '''virtual machine''' (VM) is an isolated software-defined computer running inside a virtualized environment. Each VM typically contains: * a guest operating system * virtual hardware * memory allocation * storage devices * network interfaces Virtual machines can usually be started, paused, cloned, exported, or deleted independently. == Hardware Virtualization == Modern virtualization often relies on CPU extensions such as: * Intel VT-x * AMD-V These technologies improve: * performance * hardware isolation * virtualization efficiency Additional technologies such as IOMMU support enable secure device passthrough. == Device Passthrough == Device passthrough allows physical hardware devices to be assigned directly to virtual machines. Examples include: * GPUs * USB controllers * network adapters * storage controllers This improves compatibility and performance while also enabling stronger hardware isolation. == Networking == Virtualization platforms support multiple networking models. Common configurations include: * NAT * bridged networking * host-only networking * isolated internal networks Virtual networking enables communication between virtual machines and external systems. == Storage == Virtual machines commonly use virtual disk images. Supported storage methods include: * raw images * QCOW2 * VHD * VMDK * LVM * network storage Snapshots allow virtual machine states to be saved and restored. == Snapshots == Snapshots capture the current state of a virtual machine. They are commonly used for: * testing * rollback * malware analysis * development environments Snapshots help restore systems quickly after failure or compromise. == Containers == Containers are another form of virtualization focused on operating-system-level isolation. Unlike full virtual machines, containers share the host kernel. Popular container technologies include: * Docker * LXC * Podman Containers are generally lighter and faster than traditional virtual machines. == Security == Virtualization can improve security through isolation and compartmentalization. Common security applications include: * malware analysis * sandboxing * workload separation * secure testing environments Operating systems such as [[Qubes OS]] heavily rely on virtualization for security isolation. === VM Escapes === A '''VM escape''' occurs when malicious software breaks out of a virtual machine and compromises the host system or other guests. Although rare, VM escapes are considered serious security vulnerabilities. === Sandboxing === Virtual machines are often used as sandboxes for: * untrusted software * exploit testing * reverse engineering * suspicious files == Cloud Computing == Virtualization is a foundational technology behind cloud computing platforms. Cloud providers use virtualization to: * allocate resources dynamically * isolate customers * improve scalability * deploy infrastructure rapidly == Advantages == Benefits of virtualization include: * improved hardware utilization * workload isolation * portability * scalability * simplified backups * rapid deployment == Limitations == Common disadvantages include: * performance overhead * increased complexity * hardware compatibility issues * resource consumption Security vulnerabilities in hypervisors may also affect multiple virtual machines simultaneously. == Use Cases == Virtualization is commonly used for: * cloud infrastructure * software testing * cybersecurity research * server consolidation * desktop virtualization * development environments == See Also == * [[Hypervisor]] * [[Xen]] * [[Qubes OS]] * [[Docker]] * [[Linux]] == References == * https://wiki.xenproject.org/ * https://www.redhat.com/en/topics/virtualization/what-is-virtualization * https://learn.microsoft.com/en-us/virtualization/ == External Links == * https://xenproject.org/ * https://www.virtualbox.org/ 17f274a6c27c18c3ebf39c71d732bebc10537144 0 1149 4825 4771 2026-05-23T06:37:24Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Privacy]] [[Category:Security]] [[Category:Linux Distributions]] [[Category:Tor]] '''Tails''' (The Amnesic Incognito Live System) is a free and open-source privacy-focused Linux distribution designed to preserve anonymity and reduce digital traces. Tails is based on [[Debian]] and routes all internet traffic through the [[Tor]] network by default. The operating system is designed to run as a live system from removable media such as USB drives without leaving traces on the host computer. Tails is commonly used by: * journalists * activists * whistleblowers * researchers * privacy-conscious users * users in censored regions == Overview == Tails is designed around two major goals: * anonymity * amnesia The system attempts to anonymize network traffic through Tor while minimizing traces left on the computer after shutdown. Unlike traditional operating systems, Tails is typically booted from a USB drive and runs entirely as a live environment. By default, data stored in memory is erased when the system powers off. == Live System == Tails operates primarily as a live operating system. Advantages include: * portability * reduced forensic traces * temporary sessions * hardware independence The system can run on many x86_64 computers without installation to internal storage. == Tor Integration == All internet traffic in Tails is routed through the [[Tor]] network. If an application attempts to access the internet outside of Tor, the connection is blocked by the system firewall. Benefits include: * IP address concealment * censorship circumvention * resistance to tracking * metadata reduction === Tor Browser === Tails includes '''Tor Browser''' as its default web browser. The browser includes protections against: * browser fingerprinting * trackers * unsafe scripts * insecure connections == Amnesia == The term ''amnesic'' refers to the system's design goal of leaving minimal traces after shutdown. By default, Tails: * does not write user activity to disk * clears memory on shutdown * avoids persistent local storage This helps reduce forensic recovery risks. == Persistent Storage == Tails optionally supports encrypted persistent storage on the USB device. Persistent storage may be used for: * documents * browser bookmarks * GPG keys * additional software * cryptocurrency wallets The storage is encrypted using Linux Unified Key Setup (LUKS). == Security == Tails includes numerous security and privacy protections. === Memory Protections === Tails attempts to clear sensitive memory contents during shutdown to reduce cold boot attack risks. === MAC Address Spoofing === The operating system can spoof MAC addresses to reduce hardware-based tracking on local networks. === Sandboxing === Some applications inside Tails use sandboxing technologies to reduce attack surface. === Root Access === Administrative privileges are disabled by default for normal use. This reduces accidental system modification and some attack vectors. == Included Applications == Tails includes many privacy-focused applications such as: * Tor Browser * Thunderbird * KeePassXC * OnionShare * GnuPG * Electrum The distribution focuses on secure defaults and privacy-oriented tooling. == Use Cases == Tails is commonly used for: * anonymous browsing * bypassing censorship * secure communication * whistleblowing * investigative journalism * temporary secure environments == Limitations == Tails improves privacy but does not guarantee complete anonymity. Risks still include: * phishing * browser exploits * operational security mistakes * malicious downloads * hardware compromise * traffic correlation attacks Using personal accounts or revealing identifying information may also compromise anonymity. == Performance == Because all internet traffic passes through the Tor network, Tails may experience: * slower browsing speeds * increased latency * reduced download performance Running from USB media may also reduce system responsiveness compared to installed operating systems. == Comparison with Whonix == Tails is often compared with [[Whonix]]. Differences include: * Tails is a live operating system * Whonix is virtualization-based * Tails focuses on temporary amnesic sessions * Whonix emphasizes VM isolation and persistence == See Also == * [[Tor]] * [[Whonix]] * [[Debian]] * [[Privacy]] * [[Linux]] == References == * https://tails.net/ * https://tails.net/doc/ * https://gitlab.tails.boum.org/tails/tails == External Links == * https://tails.net/install/ * https://tails.net/support/ 3d06091a45a811e2f49549880afd9c523fedde98 0 1148 4826 4770 2026-05-23T06:37:36Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Privacy]] [[Category:Security]] [[Category:Linux Distributions]] [[Category:Tor]] '''Whonix''' is a free and open-source privacy-focused operating system designed to provide strong anonymity and security through the [[Tor]] network. Whonix is based on [[Debian]] and is designed to run inside virtual machines. The operating system separates networking and user applications into isolated virtual machines in order to reduce information leaks and improve anonymity. The project is commonly used by: * privacy-conscious users * journalists * activists * researchers * whistleblowers * security enthusiasts == Overview == Whonix uses a two-VM architecture designed to isolate network traffic from user applications. The system consists of: # '''Whonix-Gateway''' # '''Whonix-Workstation''' All internet traffic from the workstation is forced through the gateway and routed over the Tor network. This design helps prevent accidental IP leaks and improves separation between applications and networking components. == Architecture == === Whonix-Gateway === '''Whonix-Gateway''' is responsible for handling all network communication. Features include: * Tor routing * traffic isolation * firewalling * DNS protection The gateway acts as an intermediary between the internet and the workstation. Applications are not normally run inside the gateway VM. === Whonix-Workstation === '''Whonix-Workstation''' is the environment where users perform daily activities. Examples include: * web browsing * messaging * file management * development * document editing The workstation has no direct internet connection and communicates only through the gateway VM. Even if the workstation becomes compromised, the attacker's ability to discover the user's real IP address may still be limited. == Tor Integration == Whonix forces all network traffic through the [[Tor]] network. Benefits include: * IP address concealment * censorship circumvention * resistance to surveillance * reduced metadata exposure The operating system is specifically designed to reduce the risk of: * DNS leaks * direct connections * application misconfiguration == Security == Whonix focuses heavily on compartmentalization and isolation. Security features include: * VM separation * forced Tor routing * isolation of networking components * hardened configuration defaults === Stream Isolation === Whonix supports Tor stream isolation techniques which separate application traffic streams. This helps reduce cross-application correlation. === Leak Prevention === The operating system includes protections against: * DNS leaks * direct IP leaks * accidental clearnet traffic * some forms of metadata exposure === Isolation === Whonix relies heavily on virtualization for isolation. It is commonly used with: * VirtualBox * KVM * [[Qubes OS]] === Qubes-Whonix === Whonix can integrate with [[Qubes OS]]. This setup is commonly known as '''Qubes-Whonix''' and combines: * Xen-based compartmentalization * Tor isolation * virtual machine separation The combination is widely regarded as one of the strongest publicly available desktop anonymity environments. == Applications == Whonix commonly includes or supports: * Tor Browser * encrypted messaging applications * cryptographic utilities * privacy-focused Linux software Users may also install additional Debian packages using APT. == Use Cases == Whonix is commonly used for: * anonymous browsing * bypassing censorship * secure communication * privacy research * journalism * whistleblowing * malware analysis == Limitations == Whonix improves anonymity but does not guarantee perfect anonymity. Limitations include: * browser fingerprinting * user mistakes * malware * phishing * operational security failures * traffic correlation attacks Virtual machine escape vulnerabilities may also affect security. == Performance == Because all traffic passes through the Tor network and virtualization layers, Whonix may experience: * increased latency * slower internet speeds * reduced performance compared to normal systems == Comparison with Tails == Whonix is often compared with [[Tails]]. Differences include: * Whonix is virtualization-focused * Tails is a live operating system * Whonix emphasizes persistent VM isolation * Tails focuses on amnesic sessions == See Also == * [[Tor]] * [[Qubes OS]] * [[Tails]] * [[Debian]] * [[Virtualization]] == References == * https://www.whonix.org/ * https://www.whonix.org/wiki/Documentation * https://forums.whonix.org/ == External Links == * https://www.whonix.org/wiki/Main_Page * https://github.com/Whonix ee324d547bce1a2f4527af0dbb6d0115ce72329e 0 1147 4827 4769 2026-05-23T06:37:46Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Virtualization]] [[Category:Hypervisors]] [[Category:Free Software]] [[Category:Security]] '''Xen''' is a free and open-source type-1 hypervisor used for virtualization and isolation. It allows multiple operating systems to run simultaneously on the same physical machine while remaining isolated from each other. == Overview == Xen runs directly on hardware instead of on top of another operating system. Because of this, it is considered a '''bare-metal hypervisor'''. The project is maintained by the '''Xen Project''' and is commonly used in: * cloud computing * enterprise virtualization * security-focused systems * server hosting * research environments Xen is also heavily used by [[Qubes OS]] for strong compartmentalization and isolation. == Architecture == Xen separates the system into multiple isolated virtual machines called '''domains'''. Each domain has separate: * memory * processes * permissions * virtual hardware This design improves: * security * workload separation * fault isolation === Hypervisor === The Xen hypervisor is the lowest software layer running directly above the hardware. Its responsibilities include: * CPU scheduling * memory isolation * interrupt handling * virtualization control The hypervisor itself is intentionally minimal in order to reduce attack surface. === dom0 === '''dom0''' is the privileged management domain started during boot. It has direct hardware access and is responsible for: * creating virtual machines * device management * storage management * networking configuration Compromise of dom0 may compromise the entire system. === domU === Regular guest virtual machines are known as '''domU''' domains. domU systems are isolated from one another by the hypervisor. A domU may run: * Linux * Windows * BSD systems * other operating systems == Virtualization Modes == Xen supports multiple virtualization technologies. === Paravirtualization === '''Paravirtualization''' modifies the guest operating system to communicate directly with the hypervisor. Advantages include: * lower overhead * better performance * reduced emulation === Hardware Virtualization === Xen also supports hardware-assisted virtualization through: * Intel VT-x * AMD-V This allows unmodified operating systems to run as guests. == Security == Xen is widely respected for its strong isolation model. Security features include: * hardware-assisted isolation * memory separation * reduced shared kernel attack surface * independent virtual machines === Device Isolation === Hardware devices may be assigned to isolated domains. Examples include: * USB controllers * network hardware * storage devices This approach is heavily used in [[Qubes OS]]. == Networking == Xen supports: * virtual bridges * NAT networking * isolated virtual networks * VLAN integration Virtual machines may communicate internally or externally depending on configuration. == Storage == Supported storage backends include: * raw disk images * LVM * iSCSI * NFS * network storage == Use Cases == Xen is commonly used for: * cloud infrastructure * virtual private servers * malware analysis * enterprise virtualization * security compartmentalization == Limitations == Common criticisms of Xen include: * complex configuration * hardware compatibility issues * dependency on dom0 * steep learning curve == See Also == * [[Qubes OS]] * [[Virtualization]] * [[Hypervisor]] * [[KVM]] == References == * https://xenproject.org/ * https://wiki.xenproject.org/ * https://xenbits.xenproject.org/docs/ 09ceff8aa5b2ca6b9f69a3fa1f33c3fd7b566f0f 0 1146 4828 4766 2026-05-23T06:37:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | title = Tor | image = TorLogo.png | caption = The Tor Project logo | developer = The Tor Project | releasestatus = Maintained | website = https://www.torproject.org/ }} [[Category:Privacy]] [[Category:Security]] [[Category:Networking]] [[Category:Free Software]] '''Tor''' (The Onion Router) is a free and open-source anonymity network designed to protect user privacy and resist surveillance, tracking, and censorship on the internet. Tor routes internet traffic through multiple volunteer-operated relays around the world, making it significantly more difficult to trace a user's activity or determine their real IP address. The project is developed by '''The Tor Project''', a nonprofit organization focused on online privacy, anonymity, and freedom of information. == Overview == Tor uses a system known as '''onion routing'''. Instead of connecting directly to a website or service, traffic is encrypted and passed through several relays before reaching its destination. A normal Tor circuit usually consists of: # Entry Guard # Middle Relay # Exit Relay Each relay only knows the previous and next node in the chain. This architecture helps prevent a single relay from knowing both: * who the user is * and where the traffic is going == Onion Routing == Tor encrypts data in multiple layers similar to the layers of an onion. Each relay decrypts only one layer before forwarding the traffic to the next relay. Benefits include: * IP address hiding * Resistance to surveillance * Reduced tracking * Circumvention of censorship * Metadata protection == Tor Browser == '''Tor Browser''' is the most common application used to access the Tor network. It is based on Mozilla Firefox and includes additional privacy protections such as: * Anti-fingerprinting features * HTTPS-only mode * Tracking protection * Script restrictions * Isolated browsing sessions Tor Browser attempts to make users appear similar to each other in order to reduce browser fingerprinting attacks. == Onion Services == Tor supports anonymous websites and services using ''.onion'' domains. These are known as '''Onion Services'''. Unlike normal websites, Onion Services hide the server's real IP address and remain fully inside the Tor network. Common uses include: * anonymous communication * whistleblowing platforms * privacy-focused services * censorship-resistant publishing == Bridges == Some countries and internet providers block access to Tor. To bypass censorship, Tor supports '''bridges'''. Bridges are special relays not publicly listed in the main Tor directory. Common bridge technologies include: * obfs4 * Snowflake * meek === Snowflake === '''Snowflake''' uses temporary volunteer-operated proxies to help censored users connect to Tor. This makes large-scale blocking more difficult. == Security == Tor is designed to defend against: * traffic analysis * ISP monitoring * censorship * mass surveillance * location tracking However, Tor does not guarantee complete anonymity. User behavior, browser exploits, malware, phishing, and operational security mistakes can still compromise privacy. === Exit Relay Risks === The exit relay decrypts the final layer before traffic reaches the destination website. Because of this: * non-HTTPS traffic may be visible to the exit operator * HTTPS remains important while using Tor === Traffic Correlation === A powerful adversary capable of monitoring both the user's connection and the destination server may attempt correlation attacks. This remains one of the main theoretical weaknesses of anonymity networks. == Performance == Tor is generally slower than normal internet connections because traffic travels through multiple relays across different countries. Performance depends on: * relay congestion * network distance * censorship * circuit quality Applications requiring very low latency may perform poorly over Tor. == Use Cases == Tor is commonly used for: * anonymous browsing * bypassing censorship * privacy protection * secure communications * journalism * research * whistleblowing == Criticism == Tor is sometimes criticized for: * slow speeds * abuse by malicious actors * website blocking * misconceptions about "perfect anonymity" Using Tor alone does not automatically make a user anonymous. == See Also == * [[Tor Browser]] * [[Onion Routing]] * [[Whonix]] * [[Tails]] * [[I2P]] * [[VPN]] == References == * https://www.torproject.org/ * https://tb-manual.torproject.org/ * https://support.torproject.org/ == External Links == * https://www.torproject.org/download/ * https://metrics.torproject.org/ 9d5c60789c862b91de29b25731dfb9c88c9ed858 0 1145 4829 4785 2026-05-23T06:38:09Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = Parrot OS | caption = The Parrot OS logo | releasestatus = Maintained | releasemodel = Rolling release | basedon = [[Debian]] | packagemanager = APT | defaultdesktops = [[MATE]] | usagetype = Desktop, Security, Development | architectures = x86_64, ARM | init = systemd | license = Free and open-source software | website = [https://parrotsec.org/ parrotsec.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Privacy]] [[Category:Penetration Testing]] '''Parrot OS''' is a free and open-source Linux distribution focused on cybersecurity, penetration testing, digital forensics, privacy, and software development. It is developed by the '''Parrot Project''' and is based on [[Debian]]. Parrot OS ships with a large collection of security, forensic, cryptography, and privacy-oriented tools while also supporting general desktop usage. The distribution is commonly used by penetration testers, ethical hackers, developers, privacy-conscious users, and students learning cybersecurity. The system aims to provide a balance between security tooling, usability, lightweight performance, and privacy protection. == Overview == Parrot OS is designed as an all-in-one platform for: * Penetration testing * Vulnerability assessment * Digital forensics * Reverse engineering * Privacy protection * Secure development * Anonymous browsing Unlike some security distributions intended purely for offensive testing, Parrot OS also supports daily desktop usage with productivity applications and multimedia support. The default desktop environment is [[MATE]], chosen for its lightweight resource usage and stability. == Editions == Parrot OS is available in multiple editions tailored for different use cases. === Security Edition === The '''Security Edition''' is the flagship version and includes a large collection of offensive security and forensic tools. Common tool categories include: * Network analysis * Web exploitation * Wireless auditing * Reverse engineering * Cryptography * Digital forensics * Malware analysis * OSINT === Home Edition === The '''Home Edition''' removes most offensive security tools and focuses on privacy, development, and general desktop usage. It is intended for users who want: * A privacy-focused Linux desktop * Lightweight performance * Development tools * Secure communication utilities === Architect and Cloud Editions === Parrot also provides minimal and specialized images for: * Servers * Cloud deployments * Containers * Custom installations == Security Features == Parrot OS includes numerous security-oriented technologies and hardening mechanisms. === Sandboxing === Applications can be sandboxed using technologies such as: * Firejail * Linux namespaces * Seccomp This reduces the impact of compromised applications. === Privacy Tools === Parrot OS includes built-in privacy utilities such as: * Tor Browser * OnionShare * AnonSurf * Cryptographic utilities * Secure communication tools === AnonSurf === '''AnonSurf''' is a Parrot-specific utility that routes system traffic through the Tor network. It allows users to anonymize internet traffic system-wide while helping reduce direct IP exposure. === Cryptography Support === The distribution includes extensive cryptographic tooling for: * File encryption * Secure communication * Key management * Password auditing * Digital signatures == Penetration Testing == Parrot OS includes a large collection of penetration testing frameworks and utilities. Examples include: * Metasploit Framework * Burp Suite * Nmap * Wireshark * Aircrack-ng * Hydra * SQLMap * John the Ripper These tools are intended for authorized security testing and research. == Digital Forensics == Parrot OS includes forensic and incident response utilities used for: * File recovery * Memory analysis * Metadata extraction * Disk analysis * Malware investigation This makes the distribution useful for both offensive and defensive security workflows. == Development == Parrot OS supports software development with preinstalled or easily available tools for: * Python * C and C++ * Java * Docker * Git * Virtualization * Reverse engineering The distribution is commonly used by developers working in security research and exploit development. == System Requirements == Parrot OS is relatively lightweight compared to many security distributions. Typical minimum requirements include: * 64-bit processor * 2 GB RAM minimum * 20 GB storage * Internet connection for updates Recommended specifications are significantly higher for virtualization or heavy penetration testing workloads. == Package Management == Parrot OS uses the APT package manager inherited from [[Debian]]. Software can be installed through: * apt * Synaptic * Parrot repositories * Flatpak support The distribution follows a rolling release model with continuously updated packages. == Containers and Virtualization == Parrot OS supports: * Docker * Podman * KVM * VirtualBox * QEMU Security researchers often run Parrot OS inside isolated virtual environments for testing and analysis. == Comparison with Kali Linux == Parrot OS is frequently compared with [[Kali Linux]]. Differences commonly noted include: * Lighter default resource usage * Stronger emphasis on privacy tools * More suitable daily desktop experience * Different package selection and defaults Both distributions are widely used in cybersecurity environments. == Criticism == Common criticisms of Parrot OS include: * Large attack surface due to included tools * Rolling release instability risks * Potential misuse by inexperienced users * Security misconceptions among beginners Installing penetration testing tools alone does not make a system secure. == Use Cases == Parrot OS is commonly used for: * Ethical hacking * Cybersecurity education * Capture The Flag competitions * Privacy-focused desktop computing * Malware research * Secure development environments == See Also == * [[Debian]] * [[Kali Linux]] * [[Linux]] * [[Digital Forensics]] * [[Penetration Testing]] * [[Tor]] == External Links == * [https://parrotsec.org/ Official website] * [https://docs.parrotsec.org/ Official documentation] * [https://github.com/ParrotSec ParrotSec GitHub] a887303bb98442a655485f8b67bd7ffc4f0e7fbc 0 1144 4830 4797 2026-05-23T06:38:19Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} [[File:2019 02 Microsoft Surface Pro 2017 with signature type cover.jpg|alt=Picture shows a Microsoft Surface Pro 5th Generation from 2017 with the Alcantara type cover running Windows :<|thumb|A Microsoft Surface Pro 2017 (5th Generation)]] {{GuideWarning}}With the release of the Microsoft Surface line-up (including the Surface Pro, Go, Laptop series), majority of these devices have support for [[Linux Distributions]], but often have issues with device hardware support on stock installs. The community-maintained "Linux Surface<ref>{{Cite|url=https://github.com/linux-surface/linux-surface|title=Linux Surface|accessdate=2026}}</ref>" provides a [[kernel]] that aims to fix compatibility issues with the Surface-specific hardware, such as Wi-Fi, touchscreen, pen input, sensors, and cameras. == Supported Surface Devices == === Surface on x86_64 === These are majority of the devices that Microsoft has released, seceding the Surface RT line-up. These are the models as follows # Surface Book # Surface Go # Surface Laptop (Excluding Surface Laptop 7) # Surface Laptop Studio # Surface Pro (Excluding Surface Pro X, Surface Pro 9, Surface Pro 11 Snapdragon, Surface Pro 12") # Surface Studio (Untested Support) Although not all devices are as supported, the feature matrix shows the hardware compatibility and guide on installation with the linux-surface kernel. To get started with installation, use the [https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup Installation and Setup] guide from the Linux-surface GitHub. === Surface on arm32 (Aarch32) === These devices were released from Microsoft under the Surface RT lineup. Although these devices don't fall under the linux-surface kernel support, they instead utilize the "Open SurfaceRT<ref>{{Cite|url=https://open-rt.gitbook.io/open-surfacert|title=Open SurfaceRT|accessdate=2026}}</ref>" guide, as well as other user created guides. == References == 119f4fd5724ee957f32e065cdd68993f3f23167e 0 1143 4831 4758 2026-05-23T06:38:29Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} '''Neovim''' (also known as '''nvim''') is a configurable terminal text editor for Linux, Windows, and macOS. It is configured in Lua. 5631d80a03d7753357d5d420abbdd91291543999 3000 1136 4832 4807 2026-05-23T06:38:39Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} Welcome to the penguin side! Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable as the operating system you use today in no time. == Why switch? == People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. == Choices == Linux is all about choices. Before you start, you need to pick what your Linux looks like and what it runs under the hood. The GUI you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. == Picking a Linux distribution ==<!-- Discuss on talk page before modifying this section due to potential for bias. --> There are many flavors of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]]. If you don't like the Linux you chose, you can switch to another one at any time as long as you know how to back up your data. == Picking a GUI == When you install a Linux, the installer asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on touchpad gestures consider [[GNOME]]. ea36eba5c71739bd89dd3ac1ca720cd2f3a37a09 4839 4832 2026-05-23T06:48:11Z Deviaze 341 /* Picking a Linux distribution */ Temporarily remove the biased section on picking a linux distribution pending discussion on talk page wikitext text/x-wiki {{Work In Progress}} Welcome to the penguin side! Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable as the operating system you use today in no time. == Why switch? == People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. == Choices == Linux is all about choices. Before you start, you need to pick what your Linux looks like and what it runs under the hood. The GUI you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. == Picking a Linux distribution ==<!-- Discuss on talk page before modifying this section due to potential for bias. --> There are many flavors of Linux. Each distribution has its pros and cons, but in the modern era of Linux, many distributions are quite easy to install, use, and update. If you don't like the Linux distribution you chose, you can switch to another one at any time as long as you know how to back up your data. == Picking a GUI == When you install a Linux, the installer asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on touchpad gestures consider [[GNOME]]. 88b8608100298bf9c998ce443ab7b476047a4d70 4849 4839 2026-05-23T07:39:59Z Boeing-737-800 372 Added more terminology and fixed some minor grammatical mistakes. wikitext text/x-wiki {{Work In Progress}} == '''Welcome to the penguin side!''' == ====== Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable, if not more comfortable as the operating system you use today in no time. ====== === Why switch to Linux? === People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. === Choices === Linux is all about choices. Before you start, you need to pick what your distribution of Linux looks like and what it runs under the hood. The Graphical User Interface (GUI) you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. === Picking a Linux distribution ===<!--Discuss on talk page before modifying this section due to potential for bias.--> There are many distributions of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]], which is [[Arch Linux]] based. If you don't like the distribution of Linux you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a Graphical User Interface (GUI) === When you install a distribution of Linux, the installer that the distribution uses asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on a touch pad gestures consider [[GNOME]]. 11b6fe7e1e1ca18c5c9d3ede8d655461c362427c 4852 4849 2026-05-23T07:42:23Z Boeing-737-800 372 Fixed mistake with subheading wikitext text/x-wiki {{Work In Progress}} == '''Welcome to the penguin side!''' == Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable, if not more comfortable as the operating system you use today in no time. === Why switch to Linux? === People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. === Choices === Linux is all about choices. Before you start, you need to pick what your distribution of Linux looks like and what it runs under the hood. The Graphical User Interface (GUI) you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. === Picking a Linux distribution ===<!--Discuss on talk page before modifying this section due to potential for bias.--> There are many distributions of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]], which is [[Arch Linux]] based. If you don't like the distribution of Linux you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a Graphical User Interface (GUI) === When you install a distribution of Linux, the installer that the distribution uses asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on a touch pad gestures consider [[GNOME]]. c0e102d66578f679bd8417d709aee5ee7e78aaf6 4855 4852 2026-05-23T07:47:33Z Boeing-737-800 372 wikitext text/x-wiki {{Work In Progress}} = '''Welcome to the penguin side!''' = Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable, if not more comfortable as the operating system you use today in no time. === Why switch to Linux? === People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. === Choices === Linux is all about choices. Before you start, you need to pick what your distribution of Linux looks like and what it runs under the hood. The Graphical User Interface (GUI) you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. === Picking a Linux distribution ===<!--Discuss on talk page before modifying this section due to potential for bias.--> There are many distributions of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]], which is [[Arch Linux]] based. If you don't like the distribution of Linux you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a Graphical User Interface (GUI) === When you install a distribution of Linux, the installer that the distribution uses asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on a touch pad gestures consider [[GNOME]]. d17ca46a44819d6d68d53b6b75be6ae48665fcd6 4856 4855 2026-05-23T07:48:14Z Boeing-737-800 372 wikitext text/x-wiki {{Work In Progress}} '''Welcome to the penguin side!''' Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable, if not more comfortable as the operating system you use today in no time. === Why switch to Linux? === People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. === Choices === Linux is all about choices. Before you start, you need to pick what your distribution of Linux looks like and what it runs under the hood. The Graphical User Interface (GUI) you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. === Picking a Linux distribution ===<!--Discuss on talk page before modifying this section due to potential for bias.--> There are many distributions of Linux. If you just need a computer that looks familiar and works, go with [[Linux Mint]]. If you have newer hardware, play games, and/or want the most up-to-date software, use something like [[CachyOS]], which is [[Arch Linux]] based. If you don't like the distribution of Linux you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a Graphical User Interface (GUI) === When you install a distribution of Linux, the installer that the distribution uses asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on a touch pad gestures consider [[GNOME]]. a136c9f8f5451f2a38154cd153cdd4a4efbfab10 4859 4856 2026-05-23T07:52:34Z Deviaze 341 Fix unintentional revert of removal of biased distribution recommendations pending discussion on talk page wikitext text/x-wiki {{Work In Progress}} '''Welcome to the penguin side!''' Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable, if not more comfortable as the operating system you use today in no time. === Why switch to Linux? === People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. === Choices === Linux is all about choices. Before you start, you need to pick what your distribution of Linux looks like and what it runs under the hood. The Graphical User Interface (GUI) you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. === Picking a Linux distribution === <!--Discuss on talk page before modifying this section due to potential for bias.--> There are many flavors of Linux. Each distribution has its pros and cons, but in the modern era of Linux, many distributions are quite easy to install, use, and update. If you don't like the Linux distribution you chose, you can switch to another one at any time as long as you know how to back up your data. === Picking a Graphical User Interface (GUI) === When you install a distribution of Linux, the installer that the distribution uses asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on a touchpad gestures consider [[GNOME]]. 2c2a6440f8be2f7f8176874c33dc782d39566eb2 0 1128 4833 4690 2026-05-23T06:38:49Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Misc Operating Systems]] {{DistributionInfobox | title = OpenSolaris | image = [[File:OpenSolaris Logo (2).svg|100px|center]] | caption = Logo of OpenSolaris | releasestatus = Discontinued | releasemodel = Rolling Release via Package Manager with Binary ISO & Repository Snapshots | packagemanager = IPS <ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/IMGPACKAGESYS/html/index.html|title=Introduction to IPS - OpenSolaris 2009.06 Image Packaging System Guide|author=Sun Microsystems, Inc.|date=2009|accessdate=2026-05-22}}</ref> | defaultdesktops = GNOME 2 | usagetype = Desktop, Server | architectures = x86, x86_64, SPARC | website = [https://web.archive.org/web/20090726021430/http://opensolaris.com/ OpenSolaris.com (archived at the Wayback Machine)] and [https://web.archive.org/web/20090709062850/http://opensolaris.org/os/ OpenSolaris.org (archived at the Wayback Machine)] }} OpenSolaris is a discontinued [[Unix-Like|UNIX-like]]<ref>{{Cite|url=https://man.freebsd.org/cgi/man.cgi?query=standards&apropos=0&sektion=5&manpath=OpenSolaris+2010.03&format=html|title=standards(5), Standards, Environments, and Macros, OpenSolaris 2010.03 Manual|author=Sun Microsystems, Inc.|year=2004|accessdate=2026-05-22}}</ref> [[Operating System|operating system]] derived from [[Sun Microsystems]] (now Oracle) [[Oracle Solaris|Solaris]] whose development began in the mid-2000s when Sun began to [[FLOSS|open-source]] more of Solaris, including its kernel and userland components. After the Oracle acquisition of Sun and the shutdown of OpenSolaris and other FOSS projects at Java.net, the kernel and userland which comprised most of OpenSolaris as well as much of the documentation with it was archived and forked into [[Illumos]], with [[OpenIndiana]] being the flagship distribution. Ian Murdock, the founder of [[Debian]], also worked at Sun on Project Indiana, the codename for the "official" OpenSolaris binary distribution.<ref>{{Cite|url=https://ianmurdock.debian.net/wp-content/uploads/imurdock-resume-15.9.pdf|title=Ian Murdock Resume|author=Ian Murdock|year=2015|accessdate=2026-05-22}}</ref> == Notable Features == === ZFS === ZFS is the filesystem developed by Sun which is used in OpenSolaris. It provides features such as snapshotting, checksums, self-healing data, RAID-Z, advanced NFSv4-style ACLs, and more.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/ZFSADMIN/html/zfsover-2.html|title=What Is ZFS? - Solaris ZFS Administration Guide|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> When OpenSolaris's code was released, the ZFS filesystem code was forked into OpenZFS which is still available on platforms like [[FreeBSD]] and some Linux distributions.<ref>{{Cite|url=https://openzfs.github.io/openzfs-docs/Getting%20Started/index.html|title=Getting Started - OpenZFS Documentation|author=OpenZFS|year=2025|accessdate=2026-05-22}}</ref> === SMF === System Management Facility (SMF) is the service supervisor and init system used in OpenSolaris and its derivatives. It handles automatic restarting of services, dependency resolution, enabling and idsabling of services, and more.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADV1/html/dzhgy.html|title=Introduction to SMF - System Administration Guide: Basic Administration|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> === Solaris Containers and Zones === Zones are very similar to FreeBSD jails. They are containers that allow the use of more than one OS instance to run under the same kernel.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/zones.intro-2.html|title=Zones Overview - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> The BrandZ framework created what is known as "LX-branded" zones, which allowed Linux distributions and binaries to run under the Solaris kernel in a zone unmodified, via syscall translation. This allowed for the usage of Linux distributions such as CentOS 3.x to run; however, this only supports user-level applications, and cannot be used to emulate kernel modules or filesystems.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/gentextid-17437.html|title=About the lx Brand - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> This feature is still present today in certain Illumos distributions such as OmniOS and SmartOS.<ref>{{Cite|url=https://omnios.org/info/lxzones.html|title=LX Branded Zones|author=About OmniOS Community Edition Association|year=2024|accessdate=2026-05-22}}</ref> === Sun xVM === Sun xVM was a fork of the Xen type-1 hypervisor specifically catered towards OpenSolaris being the dom0 OS used for management of the domU guest OSes. Sun xVM allowed multiple domU kernels to run on the same machine, and supported (Open)Solaris, Linux, FreeBSD, and even Windows.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/SYSADRM/html/geyyr.html|title=Supported Configurations - System Administration Guide: Virtualization Using the Solaris Operating System|author=Sun Microsystems, Inc.|year=2008|accessdate=2026-05-22}}</ref> === Image Packaging System === The Image Packaging System (IPS) is the primary package manager used by OpenSolaris for distribution of application updates and installation of new programs.<ref>{{Cite|url=https://dlc.openindiana.org/docs/osol/20090715/IMGPACKAGESYS/html/index.html|title=Introduction to IPS - OpenSolaris 2009.06 Image Packaging System Guide|author=Sun Microsystems, Inc.|date=2009|accessdate=2026-05-22}}</ref> == References == <references /> == External links == [http://sunsite.icm.edu.pl/pub/solaris/opensolaris/ OpenSolaris formal release ISOs (both base and repository snapshots) at SunSite] [https://docs.openindiana.org/books/about/ OpenSolaris books at OpenIndiana's documentation archive] d5d564840f250725f8a5e5de30ae7f57351c22e2 0 1127 4834 4745 2026-05-23T06:38:59Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Browsers]] [[File:LibreWolf Icon.png|thumb]] LibreWolf is an open-source fork of the browser Mozilla [[Firefox]] focused on privacy and security. Their website is https://librewolf.net. It was originally released for Linux in March 2020 with a community-maintained version being released for Microsoft Windows in February 2021 and a Mac port following a few months later in April 2021. == Features == LibreWolf's main purpose is privacy, therefore the features it adds are all mainly privacy-based. Some features LibreWolf adds include uBlock Origin by default, disabled telemetry, DuckDuckGo as the default search engine, cookies and history being wiped on closing of browser by default, and Firefox Sync being disabled by default. == License == LibreWolf's source code is currently licensed under MPL 2.0 and their website is licensed under [[GNU]] [[GNU General Public License|AGPL 3.0]]. == Source code location == The LibreWolf source code is currently kept at https://codeberg.org/librewolf and https://gitlab.com/librewolf-community. == Current Linux distro support == [[Gentoo]], [[Arch Linux|Arch]], Debian-based, [[Fedora]], [[openSUSE]] and available to any other distro via a [[Flatpak]] and an AppImage. == Windows support == You can get LibreWolf on Windows via the Microsoft Store, a portable release as just a .exe or with [[Package Manager|Package Managers]] like Scoop, Chocolatey and Winget. 5cd6254b625e79a41f964cc4ce7bd2d8fa83f0ff 0 1126 4835 4687 2026-05-23T06:39:28Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki A software license determines who can reuse, reproduce, modify, etc. software and what rights and warranties are waived or restricted by the owner. == Free and open source licenses == * [[MIT License]] ==== Copyleft licenses ==== Copyleft licenses prevent developers from using a project's code in a proprietary project without disclosing the project's source code. * [[GNU General Public License]] 6c0870cbca22c3916187c07a33e34a41f731a7ac 2 1165 4837 2026-05-23T06:43:54Z Scottc96 18 Created page with "Hi, I am Scott. I am an admin for this wiki and owner of the [https://discord.gg/nglinux Neon Genesis Linux Discord]" wikitext text/x-wiki Hi, I am Scott. I am an admin for this wiki and owner of the [https://discord.gg/nglinux Neon Genesis Linux Discord] a5249f44da8470947e284aff3fcc1a5dac19d7c6 0 396 4841 4800 2026-05-23T06:51:53Z DE-ZMK 373 Added LibreSprite, PixiEditor, and the Zed text editor. wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} 8a694fcb4c2a02b07fd07fc998af70c32c069a43 4845 4841 2026-05-23T07:22:02Z DE-ZMK 373 Update gaming wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |} 7d28a2c25d53a615b57caea9ddac5c58bb61437c 4846 4845 2026-05-23T07:32:39Z ZeliotL 375 added material maker to raster image editors and added 3D modelling section wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling = software related to editing 3D assets {| class="wikitable" !Name !Description |- |Blender |All-round 3D model editing software = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |} 3ac45a59fad1dbb1a2a1da505c50677d985af7ff 4847 4846 2026-05-23T07:33:04Z ZeliotL 375 /* 3D modelling */ wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling = software related to editing 3D assets {| class="wikitable" !Name !Description |- |Blender |All-round 3D model editing software } = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |} 7014eed317ed8cc4a83c83436101a2310aa23782 4848 4847 2026-05-23T07:33:36Z ZeliotL 375 wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling = software related to editing 3D assets {| class="wikitable" !Name !Description |- |Blender |All-round 3D model editing software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |} c542434c09298129db8a4e8a3f084e0c9bc13338 4851 4848 2026-05-23T07:41:59Z Deviaze 341 Improve 3D modelling description, add piper to gaming utilities wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} bf314108e2b66526445c92f4aace04009b9a9d2d 4854 4851 2026-05-23T07:44:27Z ZeliotL 375 added material maker to raster image editors wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |Material Maker |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} e9c794b4036eb06f5011b2d689a014bc730611bf 0 663 4842 3743 2026-05-23T06:54:19Z Madonuko 140 update links and references wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terrapkg.com terrapkg.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora Linux]] and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terrapkg.com terrapkg.com], Terra, 2026 (Accessed: 2026-05-23)</ref> Developed by [[Fyra Labs]], it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://docs.terrapkg.com/general/infrastructure/ How Terra Works], Terra Documentation, 2026 (Accessed: 2026-05-23)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://docs.terrapkg.com/usage/installing/. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji]{{Dead Link|2025-08-14|401}}, RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://docs.terrapkg.com/contributing/autoupdate/ Automatic Updates], Terra Documentation, 2026 (Accessed: 2026-05-23)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably Rust, Go, [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://docs.terrapkg.com/contributing/policies/ Policies], Terra Documentation, 2026 (Accessed: 2026-05-23)</ref> == See Also == * [https://terrapkg.com Main Website] * [https://docs.terrapkg.com Terra Documentations] * [https://github.com/terrapkg/packages Terra Sources] == References == da7a0465042df6e25393ed4e2b02dbbc648fac98 0 1166 4843 2026-05-23T07:03:00Z GentooLaws 370 Created stub page SculptOS wikitext text/x-wiki {{DistributionInfobox | title = SculptOS | image = [[File:Arch Linux "Crystal" icon.svg|Genode_OS_icon]] | caption = The Logo of Genode, the framework of SculptOS | releasestatus = Maintained | releasemodel = Bi-Annual Release | packagemanager = [[Depot]] | usagetype = Desktop | architectures = x86_64 (Primary), AArch64 (Not prebuilt), RISC-V (Not prebuilt) | website = [https://genode.org/download/sculpt genode.org/download/sculpt] | Supported Kernels = [[NOVA]] (Primary), [[Linux]] (Development), base-hw, [[Fiasco.OC]], [[SeL4]], [[OKL4]] (v2.1), [[L4ka::Pistachio]], [[Muen]], [[L4/Fiasco]] }} This page is currently a work in progress. e536ed2b97a2db1c998cca4a2dbdee09f72fbd7e 4844 4843 2026-05-23T07:12:00Z GentooLaws 370 fixed lua errors wikitext text/x-wiki [[Category:Linux Distributions]] {{Work In Progress}} {{DistributionInfobox | title = SculptOS | image = [[File:Arch Linux "Crystal" icon.svg|Genode_OS_icon]] | caption = The Logo of Genode, the framework of SculptOS | releasestatus = Maintained | releasemodel = Bi-Annual Release | packagemanager = [[Depot]] | usagetype = Desktop | architectures = x86_64 (Primary), AArch64 (Not prebuilt), RISC-V (Not prebuilt) | website = [https://genode.org/download/sculpt genode.org/download/sculpt] | defaultdesktops = }} This page is currently a work in progress. 10d4a2d99097260f919ea076415e1f30dea4b048 0 1167 4850 2026-05-23T07:40:51Z Habaja1 377 Created page and some bare bones stuff to build on (Reminder to change logo) wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, i386 (Desktop) arm64, armel, armhf, ppc64el (Server)|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. 9e6be6bc405c08e9efddda083d23068b50ec8661 4853 4850 2026-05-23T07:42:25Z Habaja1 377 some more bare bones stuff wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, i386 (Desktop) arm64, armel, armhf, ppc64el (Server)|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == == Features == == Instalation == 2406058f1d4c6030fa21927b979ed638d39fd185 4858 4853 2026-05-23T07:50:53Z Habaja1 377 added logo wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, i386 (Desktop) arm64, armel, armhf, ppc64el (Server)|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == == Features == == Instalation == 07df3704ca0919428d2d009c8c349d88aad1160c 4862 4858 2026-05-23T08:05:45Z Habaja1 377 Added installation section info wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == == Features == == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=23/05/2026}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=23/05/2026}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 15725136e6432c9a369bd402d636e8127c438fd5 4864 4862 2026-05-23T08:07:55Z Habaja1 377 minimal installation wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == == Features == == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=23/05/2026}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=23/05/2026}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 4a6c04b758fcd2fc6cf2630002db0680493552d9 6 1168 4857 2026-05-23T07:50:16Z Habaja1 377 Devuan logo (logo from devuan website, copyright not specified) wikitext text/x-wiki == Summary == Devuan logo (logo from devuan website, copyright not specified) == Licensing == {{Unknown_copyright}} c5da0a0ca226fca1c71d5b458d6ca30de39c2f29 0 622 4860 4433 2026-05-23T08:02:00Z Birdie 363 Cinnamon and COSMIC are not GNOME based desktop environments, cinnamon however was originally developed on top of GNOME 3. Fixed some gramatical errors and changed the descriptions accordingly to be more accurate. wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:COSMIC Epoch 1.0.0 alpha with apps.png|[[COSMIC]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity Desktop Environment]] File:XFCE-4.18-Desktop.png|[[XFCE]] File:LXDE-Qt preview.png|[[LXDE]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment originally based on GNOME 3, developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[COSMIC]] |[[COSMIC]] is a Desktop Environment developed by [[system76]], also known as the creators of [[Pop! OS|Pop! OS.]] COSMIC is built in [[Rust]] and is notable for having automatic window tiling built into the desktop as a primary feature. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in a variety of languages, but primarily is built in [[C]]. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[XFCE]] |[[XFCE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} 8f2a67581ddc056805db7f4a614843af6d582eb7 4861 4860 2026-05-23T08:04:30Z Birdie 363 Xfce is not officially spelled in all caps. wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:COSMIC Epoch 1.0.0 alpha with apps.png|[[COSMIC]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity Desktop Environment]] File:XFCE-4.18-Desktop.png|[[XFCE]] File:LXDE-Qt preview.png|[[LXDE]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment originally based on GNOME 3, developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[COSMIC]] |[[COSMIC]] is a Desktop Environment developed by [[system76]], also known as the creators of [[Pop! OS|Pop! OS.]] COSMIC is built in [[Rust]] and is notable for having automatic window tiling built into the desktop as a primary feature. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in a variety of languages, but primarily is built in [[C]]. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[Xfce]] |[[Xfce]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} 2245a6fe815731a1fa2235190fcf5d72d53af454 4863 4861 2026-05-23T08:06:17Z Birdie 363 Fixed capitilization for Xfce preview. wikitext text/x-wiki {{Work In Progress}} A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:COSMIC Epoch 1.0.0 alpha with apps.png|[[COSMIC]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity Desktop Environment]] File:XFCE-4.18-Desktop.png|[[Xfce]] File:LXDE-Qt preview.png|[[LXDE]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment originally based on GNOME 3, developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[COSMIC]] |[[COSMIC]] is a Desktop Environment developed by [[system76]], also known as the creators of [[Pop! OS|Pop! OS.]] COSMIC is built in [[Rust]] and is notable for having automatic window tiling built into the desktop as a primary feature. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in a variety of languages, but primarily is built in [[C]]. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[Xfce]] |[[Xfce]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} 401371303ebcc69953ff6a6801bbfb9df9c6df3f 0 198 4865 4802 2026-05-23T08:13:56Z Birdie 363 Fedora is the upstream to Red Hat Enterprise Linux (RHEL). Therefore, distros are Fedora based, not Red Hat based. Fedora was originally built as a fork of Red Hat Linux, but it has not been called Red Hat Linux since as early as 2004. Also changed "Fedora Atomic" to "Fedora Silverblue". wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Fedora Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Based ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == f38abbc301629d1bb1a96045a84a3ab645db7885 0 1121 4866 4670 2026-05-23T08:16:10Z LilyWayLolz 354 Removed "android" - this was a mistake made due to my sleep deprivation wikitext text/x-wiki [https://psysonic.de Psysonic] is a local music streaming client made for [[Navidrome]] servers. The client boasts a modern, sleek UI, native [https://last.fm last.fm] [[scrobbling]], and wide range of support for operating systems, including: Windows, MacOS, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [[Flathub]] release. [[Category:Software]] [[Category:Navidrome Clients]] fff7eee3833ed5ca35cbf9a2a82431b0a7f468fc 4867 4866 2026-05-23T08:17:42Z LilyWayLolz 354 Fixed Flathub link to direct to Flatpak page wikitext text/x-wiki [https://psysonic.de Psysonic] is a local music streaming client made for [[Navidrome]] servers. The client boasts a modern, sleek UI, native [https://last.fm last.fm] [[scrobbling]], and wide range of support for operating systems, including: Windows, MacOS, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [https://foss.wiki/Flatpak](Flathub) release. [[Category:Software]] [[Category:Navidrome Clients]] ff4f83878670312ea6e5fd8ed2a0c99b14787425 4868 4867 2026-05-23T08:18:38Z Madonuko 140 fix link (not markdown) wikitext text/x-wiki [https://psysonic.de Psysonic] is a local music streaming client made for [[Navidrome]] servers. The client boasts a modern, sleek UI, native [https://last.fm last.fm] [[scrobbling]], and wide range of support for operating systems, including: Windows, MacOS, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [https://foss.wiki/Flatpak Flathub] release. [[Category:Software]] [[Category:Navidrome Clients]] 542b89be016b852aaf1ce650531b86671e8017a2 0 1026 4869 4381 2026-05-23T08:34:59Z Ping 374 Edited wrongly accredited information (nala uses libapt-pkg, not the apt package manager even though they're both under the APT suite, it is still to be accurate here). Also removed and reworded parts of the section alongside adding more common commands and citations wikitext text/x-wiki {{stub}} [[Category:Software]] {{SoftwareInfobox |image = [[File:Debian_Nala.png|300px|center|thumb]] |caption = Nala install screenshot |title = Nala |releasestatus = Maintained |lastrelease = v0.16.0, 2025-04-21 |languages = [[Python]] |developers = [[https://github.com/volitank Volitank]] |website = [[https://github.com/volitank/nala Nala Github]] }} Nala is a front-end of libapt-pkg, which is a part of the [[apt|APT]] packaging managing suite used by [[Debian]]-based [[Linux Distributions|Linux distributions]]. Nala is designed to provide prettier output and speed up [[package]] installations with parallel downloads alongside a mirror ranking feature. As a front-end, Nala can only be used on systems with the apt package installed. == Limitations == * Nala requires at least Debian 11/Bullseye or Ubuntu 19.04/Disco Dingo or newer, older releases do not have required packages and [[Python]] versions available.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/wikis/Installation|title=Installation: Nala's Gitlab Wiki|accessdate=2026-05-23}}</ref> * Nala limits parallel downloads connections to three per mirror.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/blob/f6fc96c7afcb02b277d5811cfa6703e368cec317/README.rst|title=README: Nala's Gitlab repository|year=2024|accessdate=2026-05-23}}</ref> * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding packages (pauses certain packages' updates) or showing reverse dependencies (packages depending on a certain package). To hold packages consider using the apt-mark tool instead. == Usage<ref>{{Cite|url=http://manpages.debian.org/trixie/nala/nala.8.en.html|title=Nala User Manual: Debian Manpages|year=2025|accessdate=2026-05-23}}</ref> == The following shows common Nala [[command]]s, which are mostly similar to that of the apt command. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of available packages and their versions |- |<code>nala upgrade</code> |Updates and upgrades system's packages, alongside removing unused dependencies |- |<code>nala full-upgrade</code> |Updates and upgrades system's packages, installing new packages and removing old ones as needed |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala clean</code> |Removes unused package caches within the system |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages available for installation. Can list installed packages with <code>nala list --installed</code> |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands (transaction) alongside its ID |- |<code>nala history info <ID></code> |Show the info of a specific transaction |- |<code>nala history undo <ID></code> |Undo the commands ran under a specific transaction |- |<code>nala history redo <ID></code> |Redo the commands ran under a specific transaction |} <references /> fa5ded0d5534c60e2f173a09d7656d9c699acf92 1 1169 4870 2026-05-23T08:37:26Z Ping 374 /* What else to do */ new section wikitext text/x-wiki == What else to do == I can't think of much apart from linking apt-mark once that's written up under [[Apt|APT]]. Other than that maybe some wordings are still weird, but I think it should be alright now. [[User:Ping|Ping]] ([[User talk:Ping|talk]]) 08:37, 23 May 2026 (UTC) 43c59ea1f571b6ca68b534d524c159a6431e0561 4878 4870 2026-05-23T08:55:34Z Ping 374 /* What else to do */ Reply wikitext text/x-wiki == What else to do == I can't think of much apart from linking apt-mark once that's written up under [[Apt|APT]]. Other than that maybe some wordings are still weird, but I think it should be alright now. [[User:Ping|Ping]] ([[User talk:Ping|talk]]) 08:37, 23 May 2026 (UTC) :Actually now I have just learned that they're moving to a rust rewrite. I'm not sure if it should be added yet though. [[User:Ping|Ping]] ([[User talk:Ping|talk]]) 08:55, 23 May 2026 (UTC) 380967dd868b6f880e92c10e0129b1739eec92a3 0 1167 4871 4864 2026-05-23T08:41:36Z Habaja1 377 added history wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCI, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=23/05/2026}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=23/05/2026}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == eb946e575040cbe7f4d0bfc97b36f11d6337f98e 4875 4871 2026-05-23T08:46:29Z Habaja1 377 added some citations wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=23/05/2026}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCI, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=23/05/2026|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=23/05/2026}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=23/05/2026}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == b7c074bd840a8ee81c7a5f8b007665096bbd8d20 4879 4875 2026-05-23T08:56:37Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=23/05/2026}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCI, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=23/05/2026|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems: * OpenRC - A dependency-based init system from Gentoo. * runit - A cross-platform Unix init scheme with service supervision. * sinit - A customisable, minimal alternative to systemd developed by the suckles community * s6 - A suite of programs for process supervision. * shepherd - An extremely flexible init system written in Guile Scheme. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=23/05/2026}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=23/05/2026}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 224cf3e51b2738df4278b4a82a748ed3fcb59212 4882 4879 2026-05-23T08:57:53Z Habaja1 377 /* Init System Options */ citation wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=23/05/2026}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCI, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=23/05/2026|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=23/05/2026}}</ref>: * OpenRC - A dependency-based init system from Gentoo. * runit - A cross-platform Unix init scheme with service supervision. * sinit - A customisable, minimal alternative to systemd developed by the suckles community * s6 - A suite of programs for process supervision. * shepherd - An extremely flexible init system written in Guile Scheme. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=23/05/2026}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=23/05/2026}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 966144060ba970b7ca1fb70dcd4d54897b7ad54d 4884 4882 2026-05-23T09:00:33Z Habaja1 377 init system links wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian based distro developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=23/05/2026}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCI, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=23/05/2026|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=23/05/2026}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=23/05/2026}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=23/05/2026}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 71bc7e4ddb41499e9b54d351caa17ac7c37617dc 4886 4884 2026-05-23T09:04:28Z Habaja1 377 bit clearer wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=23/05/2026}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCI, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=23/05/2026|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=23/05/2026}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=23/05/2026}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=23/05/2026}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 29f7022681bc8e624b8a48a05583189224616ad0 4887 4886 2026-05-23T09:05:36Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=23/05/2026}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=23/05/2026|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=23/05/2026}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=23/05/2026}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=23/05/2026}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 2ddce0d38af55fc56037aadff070d1cd57da05bc 4888 4887 2026-05-23T09:09:05Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == c27a8493ebf6146d04ae2a8f19aba30bdc194328 4889 4888 2026-05-23T09:23:59Z Habaja1 377 repositories and compatability wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64 * arm64 * armel * armhf * ppc64e === Package Management === Artix uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from debian that require systemd to systemd-less packages. While it is possible to use debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from devuan website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 08eb2bef0a9f279f4be9c4f1f13fbbf8b6fd1e1f 4890 4889 2026-05-23T09:32:24Z Habaja1 377 requirements wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Artix uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from debian that require systemd to systemd-less packages. While it is possible to use debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from devuan website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making bootable USB and booting it. | | |} == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == ad477ad50ff8ededa024b745594a1faa74bcd76b 4891 4890 2026-05-23T09:34:07Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Artix uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from debian that require systemd to systemd-less packages. While it is possible to use debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from devuan website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making bootable USB and booting it. | | |} Devuan Is a debian fork and therefore the same minimum and recommended requirements are also for devuan, albeit that withouth systemd it's more lightweight and can therefore support older computers more than debian. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == f2662e23c007daec775a03a539677e6f3d658064 4892 4891 2026-05-23T09:38:14Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Artix uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from debian that require systemd to systemd-less packages. While it is possible to use debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from devuan website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making bootable USB and booting it. | | |} Devuan Is a debian fork and therefore the same minimum and recommended requirements are also for devuan, albeit that withouth systemd it's more lightweight and can therefore support older computers more than debian. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 92b776c12153e5fb762a2a3f7bdcb4b12c094b43 4894 4892 2026-05-23T09:43:21Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Debian uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from debian that require systemd to systemd-less packages. While it is possible to use debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from devuan website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making bootable USB and booting it. | | |} Devuan Is a Debian fork and therefore the same minimum and recommended requirements are also for devuan, albeit that withouth systemd it's more lightweight and can therefore support older computers more than Debian. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == 08181b776283f99f459fb125821849f30b70dd65 4895 4894 2026-05-23T09:44:01Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a Debian fork of what would become devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems according to the devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Debian uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from debian that require systemd to systemd-less packages. While it is possible to use Debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from devuan website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making bootable USB and booting it. | | |} Devuan Is a Debian fork and therefore the same minimum and recommended requirements are also for devuan, albeit that withouth systemd it's more lightweight and can therefore support older computers more than Debian. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Refrences == bd2671640e0d072d32f79cfefb299242e55a93cf 4897 4895 2026-05-23T09:46:57Z Thatonecoder 369 Fixed many typos wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian withouth systemd. it was first released on 3 may 2016, with the first stable version being released on May 25, 2017. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit and upstart and other init systems to systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a Debian fork of what would become Devuan, aiming to give people the choise to use another init system than systemd again. The firstt stable release was released on May 25, 2017, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time and also provided installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader for the first time<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems, according to the Devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Devuan uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from Debian that require systemd to systemd-less packages. While it is possible to use Debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from Devuan's website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making bootable USB and booting it. | | |} Devuan is a Debian fork and therefore the same minimum and recommended requirements are also for Devuan, albeit that without systemd it's more lightweight and therefore has somewhat better support for older computers than Debian. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of Devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == References == 227788f7d7abe8829eade703b56448a0f5db9bab 4901 4897 2026-05-23T09:50:57Z Thatonecoder 369 Fix more typos wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian without systemd. It was first released on 2016-05-03, with the first stable version being released on 2017-05-25. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit, upstart, and other init systems with systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a Debian fork of what would become Devuan, aiming to provide people with the choice to other init systems again. The first stable release was released on 2017-05-25, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time, also providing installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader, for the first time.<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems, according to the Devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Devuan uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from Debian that require systemd to systemd-less packages. While it is possible to use Debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from Devuan's website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making a bootable USB and booting it. | | |} Devuan is a Debian fork; therefore, the same minimum and recommended requirements also apply to Devuan. However, it is somewhat lighter than Debian, since it does not use systemd. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of Devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == References == db723d67eca999217e08cdf814b02ba3bdc8635f 4903 4901 2026-05-23T09:54:35Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]|Exampleimage=[[File:https://images.foss.wiki/Devuan6-xfce.png]]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian without systemd. It was first released on 2016-05-03, with the first stable version being released on 2017-05-25. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit, upstart, and other init systems with systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a Debian fork of what would become Devuan, aiming to provide people with the choice to other init systems again. The first stable release was released on 2017-05-25, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time, also providing installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader, for the first time.<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems, according to the Devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Devuan uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from Debian that require systemd to systemd-less packages. While it is possible to use Debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from Devuan's website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making a bootable USB and booting it. | | |} Devuan is a Debian fork; therefore, the same minimum and recommended requirements also apply to Devuan. However, it is somewhat lighter than Debian, since it does not use systemd. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of Devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == References == 1905ac9cc4e3fed37f7c60ed75369fb2c15d5f23 4904 4903 2026-05-23T09:54:54Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian without systemd. It was first released on 2016-05-03, with the first stable version being released on 2017-05-25. == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit, upstart, and other init systems with systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a Debian fork of what would become Devuan, aiming to provide people with the choice to other init systems again. The first stable release was released on 2017-05-25, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time, also providing installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader, for the first time.<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems, according to the Devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Devuan uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from Debian that require systemd to systemd-less packages. While it is possible to use Debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from Devuan's website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making a bootable USB and booting it. | | |} Devuan is a Debian fork; therefore, the same minimum and recommended requirements also apply to Devuan. However, it is somewhat lighter than Debian, since it does not use systemd. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of Devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == References == db723d67eca999217e08cdf814b02ba3bdc8635f 4905 4904 2026-05-23T09:55:42Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a Debian derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian without systemd. It was first released on 2016-05-03, with the first stable version being released on 2017-05-25. [[File:Devuan6-xfce.png|thumb|A Devuan installation running Xfce]] == History == On 25 April 2015, Debian 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing sysvinit, upstart, and other init systems with systemd by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a Debian fork of what would become Devuan, aiming to provide people with the choice to other init systems again. The first stable release was released on 2017-05-25, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments (XFCE, Cinnamon, KDE, LXQt, MATE) at install time, also providing installation options for choosing between sysvinit and OpenRC for init, and between GRUB and LILO for the boot loader, for the first time.<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems, according to the Devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Devuan uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from Debian that require systemd to systemd-less packages. While it is possible to use Debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from Devuan's website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Expirimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making a bootable USB and booting it. | | |} Devuan is a Debian fork; therefore, the same minimum and recommended requirements also apply to Devuan. However, it is somewhat lighter than Debian, since it does not use systemd. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of Devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == References == ac09806cb61c79449e15738c0f480a940e35887e 0 623 4872 4258 2026-05-23T08:41:58Z Atmois 13 Fix url wikitext text/x-wiki {{Cleanup|Citations lack information required in the [[FW:Guidelines#Citations]]}} {{DistributionInfobox | title = EndeavourOS | image = [[File:EndeavourOS Logo.svg|Thumb]] | caption = The Endeavour OS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[Cinnamon]], [[I3]], [[GNOME]], [[KDE Plasma]], [[LXDE]], [[LXQt]], [[MATE]], [[Xfce]], [[Budgie]] | usagetype = Desktop | architectures = x86_64, AArch64 | website = [https://endeavouros.com endeavouros.com] }} '''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">[https://endeavouros.com/ Home - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>[https://endeavouros.com/about-us/ About us - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning [[Arch Linux]] fundamentals. === Installation === EndeavourOS provides an ISO with the [[Calamares]] installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages. === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with [[Arch Linux]], meaning it uses Arch's official repositories directly and adheres closely to Arch's philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * [[AUR]] Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate [[AUR]] package management. * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * [[Pacman]] Compatibility: Fully compatible with Arch's [[pacman]] package manager and its tooling ecosystem. Because of this alignment, most documentation and guides written for [[Arch Linux]] are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla [[Arch]], or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the [[AUR]], as well as EndeavourOS-specific themes and utilities.<ref>[https://repo.c48.uk/endeavouros/repo/endeavouros/ Index of /endeavouros/repo/endeavouros/] (Accessed: 2025-08-09)</ref> This is simply a [[pacman]] repository that can simply be added to any [[Arch Linux]] system if desired. == References == 6933434331e3f6bab2f5ab72225f5ed1fe9ae754 0 1026 4873 4869 2026-05-23T08:45:12Z Ping 374 Switches Github to Gitlab source as they linked the wiki from there (so I believe it's the main one even though both is official) wikitext text/x-wiki {{stub}} [[Category:Software]] {{SoftwareInfobox |image = [[File:Debian_Nala.png|300px|center|thumb]] |caption = Nala install screenshot |title = Nala |releasestatus = Maintained |lastrelease = v0.16.0, 2025-04-21 |languages = [[Python]] |developers = [[https://github.com/volian Volian]] |website = [[https://gitlab.com/volian/nala Nala Gitlab]] }} Nala is a front-end of libapt-pkg, which is a part of the [[apt|APT]] packaging managing suite used by [[Debian]]-based [[Linux Distributions|Linux distributions]]. Nala is designed to provide prettier output and speed up [[package]] installations with parallel downloads alongside a mirror ranking feature. As a front-end, Nala can only be used on systems with the apt package installed. == Limitations == * Nala requires at least Debian 11/Bullseye or Ubuntu 19.04/Disco Dingo or newer, older releases do not have required packages and [[Python]] versions available.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/wikis/Installation|title=Installation: Nala's Gitlab Wiki|accessdate=2026-05-23}}</ref> * Nala limits parallel downloads connections to three per mirror.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/blob/f6fc96c7afcb02b277d5811cfa6703e368cec317/README.rst|title=README: Nala's Gitlab repository|year=2024|accessdate=2026-05-23}}</ref> * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding packages (pauses certain packages' updates) or showing reverse dependencies (packages depending on a certain package). To hold packages consider using the apt-mark tool instead. == Usage<ref>{{Cite|url=http://manpages.debian.org/trixie/nala/nala.8.en.html|title=Nala User Manual: Debian Manpages|year=2025|accessdate=2026-05-23}}</ref> == The following shows common Nala [[command]]s, which are mostly similar to that of the apt command. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of available packages and their versions |- |<code>nala upgrade</code> |Updates and upgrades system's packages, alongside removing unused dependencies |- |<code>nala full-upgrade</code> |Updates and upgrades system's packages, installing new packages and removing old ones as needed |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala clean</code> |Removes unused package caches within the system |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages available for installation. Can list installed packages with <code>nala list --installed</code> |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands (transaction) alongside its ID |- |<code>nala history info <ID></code> |Show the info of a specific transaction |- |<code>nala history undo <ID></code> |Undo the commands ran under a specific transaction |- |<code>nala history redo <ID></code> |Redo the commands ran under a specific transaction |} <references /> d3202776c5fcd617bf3c7364d78661bce893ea69 4874 4873 2026-05-23T08:46:11Z Ping 374 github -> gitlab (fixed missing improper links) wikitext text/x-wiki {{stub}} [[Category:Software]] {{SoftwareInfobox |image = [[File:Debian_Nala.png|300px|center|thumb]] |caption = Nala install screenshot |title = Nala |releasestatus = Maintained |lastrelease = v0.16.0, 2025-04-21 |languages = [[Python]] |developers = [[https://gitlab.com/volian Volian]] |website = [[https://gitlab.com/volian/nala Nala Gitlab]] }} Nala is a front-end of libapt-pkg, which is a part of the [[apt|APT]] packaging managing suite used by [[Debian]]-based [[Linux Distributions|Linux distributions]]. Nala is designed to provide prettier output and speed up [[package]] installations with parallel downloads alongside a mirror ranking feature. As a front-end, Nala can only be used on systems with the apt package installed. == Limitations == * Nala requires at least Debian 11/Bullseye or Ubuntu 19.04/Disco Dingo or newer, older releases do not have required packages and [[Python]] versions available.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/wikis/Installation|title=Installation: Nala's Gitlab Wiki|accessdate=2026-05-23}}</ref> * Nala limits parallel downloads connections to three per mirror.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/blob/f6fc96c7afcb02b277d5811cfa6703e368cec317/README.rst|title=README: Nala's Gitlab repository|year=2024|accessdate=2026-05-23}}</ref> * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding packages (pauses certain packages' updates) or showing reverse dependencies (packages depending on a certain package). To hold packages consider using the apt-mark tool instead. == Usage<ref>{{Cite|url=http://manpages.debian.org/trixie/nala/nala.8.en.html|title=Nala User Manual: Debian Manpages|year=2025|accessdate=2026-05-23}}</ref> == The following shows common Nala [[command]]s, which are mostly similar to that of the apt command. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of available packages and their versions |- |<code>nala upgrade</code> |Updates and upgrades system's packages, alongside removing unused dependencies |- |<code>nala full-upgrade</code> |Updates and upgrades system's packages, installing new packages and removing old ones as needed |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala clean</code> |Removes unused package caches within the system |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages available for installation. Can list installed packages with <code>nala list --installed</code> |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands (transaction) alongside its ID |- |<code>nala history info <ID></code> |Show the info of a specific transaction |- |<code>nala history undo <ID></code> |Undo the commands ran under a specific transaction |- |<code>nala history redo <ID></code> |Redo the commands ran under a specific transaction |} <references /> 2617619a16c2cf95fc2c822897d0e9d5e55d3305 4877 4874 2026-05-23T08:54:23Z Ping 374 Removed {{stub}} wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox |image = [[File:Debian_Nala.png|300px|center|thumb]] |caption = Nala install screenshot |title = Nala |releasestatus = Maintained |lastrelease = v0.16.0, 2025-04-21 |languages = [[Python]] |developers = [[https://gitlab.com/volian Volian]] |website = [[https://gitlab.com/volian/nala Nala Gitlab]] }} Nala is a front-end of libapt-pkg, which is a part of the [[apt|APT]] packaging managing suite used by [[Debian]]-based [[Linux Distributions|Linux distributions]]. Nala is designed to provide prettier output and speed up [[package]] installations with parallel downloads alongside a mirror ranking feature. As a front-end, Nala can only be used on systems with the apt package installed. == Limitations == * Nala requires at least Debian 11/Bullseye or Ubuntu 19.04/Disco Dingo or newer, older releases do not have required packages and [[Python]] versions available.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/wikis/Installation|title=Installation: Nala's Gitlab Wiki|accessdate=2026-05-23}}</ref> * Nala limits parallel downloads connections to three per mirror.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/blob/f6fc96c7afcb02b277d5811cfa6703e368cec317/README.rst|title=README: Nala's Gitlab repository|year=2024|accessdate=2026-05-23}}</ref> * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding packages (pauses certain packages' updates) or showing reverse dependencies (packages depending on a certain package). To hold packages consider using the apt-mark tool instead. == Usage<ref>{{Cite|url=http://manpages.debian.org/trixie/nala/nala.8.en.html|title=Nala User Manual: Debian Manpages|year=2025|accessdate=2026-05-23}}</ref> == The following shows common Nala [[command]]s, which are mostly similar to that of the apt command. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of available packages and their versions |- |<code>nala upgrade</code> |Updates and upgrades system's packages, alongside removing unused dependencies |- |<code>nala full-upgrade</code> |Updates and upgrades system's packages, installing new packages and removing old ones as needed |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala clean</code> |Removes unused package caches within the system |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages available for installation. Can list installed packages with <code>nala list --installed</code> |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands (transaction) alongside its ID |- |<code>nala history info <ID></code> |Show the info of a specific transaction |- |<code>nala history undo <ID></code> |Undo the commands ran under a specific transaction |- |<code>nala history redo <ID></code> |Redo the commands ran under a specific transaction |} <references /> 6e0d2f7a306e0775227bda8c29b31c20bb8678e2 0 198 4876 4865 2026-05-23T08:47:17Z Atmois 13 Change "based" to "family" wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian and Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Fedora and RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 7e4e386caa0e627c973604832e908f23a8a9cd13 4880 4876 2026-05-23T08:56:50Z Atmois 13 Split Fedora/RHEL and Debian/Ubuntu wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== **Debian Family** {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 7c8c838110242e9fcbe2f5840a84132094dd7e9d 4881 4880 2026-05-23T08:57:10Z Atmois 13 Remove typo wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == e857c9d4924259cec412dfc61afac0f35cd0e4b5 4883 4881 2026-05-23T08:59:13Z Atmois 13 Alphabetise wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux]] |An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref> |- |[[Arco Linux|''Arco Linux'']] |Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users. |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |[[Debian]] |An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely. |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|Fedora Linux]] |A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL. |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|Red Hat Enterprise Linux (RHEL)]] |A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market. |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Slackware]] |A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |[[Ubuntu]] |A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices. |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 18b3ba7eeb21452e046bf3738fb9e46892228792 4885 4883 2026-05-23T09:01:40Z Atmois 13 Format the tables wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |[[Funtoo]] |A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024. |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux]] |A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained. |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 1bfa1c5c9f74baeb4bbbdb679ce67fe8eb80cfb3 2 1170 4893 2026-05-23T09:41:14Z Ping 374 Created page with "=Pong= I Debian. Can Arch and Fedora. Happy to contribute." wikitext text/x-wiki =Pong= I Debian. Can Arch and Fedora. Happy to contribute. db7e05c3410e9ce8a0d2a701a028a492fb23caa3 0 396 4896 4854 2026-05-23T09:46:07Z ZeliotL 375 Added social category and Fluxer in instant messaging wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |Material Maker |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} 44e9954b6192e01be4f572ffc25eeb616a9866bb 4899 4896 2026-05-23T09:49:12Z ZeliotL 375 added links to github repos for krita and material maker wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[https://github.com/KDE/krita Krita] |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |[https://github.com/RodZill4/material-maker Material Maker] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} da20bf70a7b2740552e68675f96a7cf64b323b55 4906 4899 2026-05-23T10:07:30Z Deviaze 341 add software managers section wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Description !DE |- |Discover |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Description !Distribution |- |[[pacman]] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora Linux]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[https://github.com/KDE/krita Krita] |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |[https://github.com/RodZill4/material-maker Material Maker] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} 2ba89485ce4ba196786225e994d05dd63543233f 4907 4906 2026-05-23T10:08:44Z Deviaze 341 /* Package managers */ fix link to Fedora wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Description !DE |- |Discover |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Description !Distribution |- |[[pacman]] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[https://github.com/KDE/krita Krita] |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |[https://github.com/RodZill4/material-maker Material Maker] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} 20abcc049e4a32ea367f8f44989de27f110d5793 0 534 4898 4432 2026-05-23T09:47:44Z Sparrow 362 wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox | image = [[File:Nirilogo.svg|300px|example_niri_rice]] | caption = Niri's logo | title = niri | releasestatus = Maintained | firstrelease = v0.1.0-alpha.1 | lastrelease = v26.04 | languages = [[Rust]] | developers = Ivan Molodetskikh A.K.A. YaLTeR | website = [https://github.com/YaLTeR/niri Github Repository] }} [[File:Niri Rice.png|thumb|A desktop running [[Niri]].]] Niri is a scrollable-tiling wayland compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">[https://github.com/YaLTeR/niri/wiki/Important-Software Important Software · YaLTeR/niri Wiki · GitHub], YaLTeR, 2025-08-09 (Accessed: 2025-08-09)</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad]{{Dead Link|2025-08-14|403}} and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse]{{Dead Link|2025-08-14|403}} gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations]{{Dead Link|2025-08-14|403}} * Live-reloading == References == <references /> 7896ed2297676639706bf150099f3377320b5fd3 4902 4898 2026-05-23T09:52:59Z Sparrow 362 Add link to Wayland page wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox | image = [[File:Nirilogo.svg|300px|example_niri_rice]] | caption = Niri's logo | title = niri | releasestatus = Maintained | firstrelease = v0.1.0-alpha.1 | lastrelease = v26.04 | languages = [[Rust]] | developers = Ivan Molodetskikh A.K.A. YaLTeR | website = [https://github.com/YaLTeR/niri Github Repository] }} [[File:Niri Rice.png|thumb|A desktop running [[Niri]].]] Niri is a scrollable-tiling [[Wayland]] compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">[https://github.com/YaLTeR/niri/wiki/Important-Software Important Software · YaLTeR/niri Wiki · GitHub], YaLTeR, 2025-08-09 (Accessed: 2025-08-09)</ref> == * Dynamic workspaces similar to GNOME * Built in screenshot utility * The ability to [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from block out] sensitive windows from screencasts * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175503Z&X-Amz-Expires=300&X-Amz-Signature=7447cca3fc33ed12b164d09f615a53c5233250dd391b71799c44aed748c5fdf6&X-Amz-SignedHeaders=host touchpad]{{Dead Link|2025-08-14|403}} and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250124T175528Z&X-Amz-Expires=300&X-Amz-Signature=fe4625330b29e01df304cc92ba28fe629c915cd03b85f43a336515757fd1882f&X-Amz-SignedHeaders=host mouse]{{Dead Link|2025-08-14|403}} gestures * Switch windows between tiling and floating modes * Gradient borders and round corners * Smooth and customizable [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/324153487-ce178da2-af9e-4c51-876f-8709c241d95e.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20250123%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250123T181033Z&X-Amz-Expires=300&X-Amz-Signature=24aae5b7c30958ab96f29a5c59ecae4e9dbd6174b9cd7a404597821daa02e924&X-Amz-SignedHeaders=host animations]{{Dead Link|2025-08-14|403}} * Live-reloading == References == <references /> 4ec1705358745c38e033c5596d2e081e42f13825 6 1171 4900 2026-05-23T09:50:36Z Habaja1 377 An example of devuan 6 running Xfce from Linuxiac wikitext text/x-wiki == Summary == An example of devuan 6 running Xfce from Linuxiac == Licensing == {{Unknown_copyright}} 6355ba1c36d8930ae041821607d3442ac8a773a1 6 1172 4908 2026-05-23T10:11:17Z Aktywnyyy 296 wikitext text/x-wiki X.Org Logo 45069c6b419c88d63b43a854f1b3def5738a15b8 0 1048 4909 4276 2026-05-23T10:14:20Z Aktywnyyy 296 complete rewrite of this page that i messed up 5 months ago wikitext text/x-wiki '''X.org''' [[File:X.Org Logo.svg.png|center|thumb|'''X.Org logo (1999)''']] '''X.Org''' (full name: X.Org Server) is free and opensource ([[FOSS]]) implementation of X Window System ([[X11]]) server, it implicates fundamental graphical layer used in traditional UNIX and Linux operating system environments. Responsible for managing the graphical interface, rendering image on the screen and input device support, like keyboards, mouses and touch screens. == History and Origin == The roots of the project date back to the 1980s. on the MIT university the same one that created [[X11]], direct predecessor od X.Org was XFree86. In 2004, as a result of controversial license changes on XFree86 (Version 4.4.0), community and developers decided to create a fork, and that resulted creation of X.Org Foundation and release of X.Org, which quickly became a standard in the mainline in all important Linux Distributions. == Architecture Client-Server == X.Org bases on classic, network model client-server, which distinguishes it from other modern protocols like [[Wayland]]: Server (X Server): It works directly on users workstation, it manages hardware like, Screen, GPU and input devices Clients (X Clients): these are graphical applications (e.g web browser, video player, terminal). They don't draw anything directly on screen, instead they send requests to the server, asking if they can draw a window. [[File:X client server example.png|thumb|422x422px|X client Client-Server Architecture '''Example''']] == Key components == Internal architecture of X.Org is based on layers, that were evolving in the time of decades, to keep up with hardware: DIX (Device-Independent X): Layer Not dependent on hardware. It is responsible for processing X11 protocol, managing windows and communication between Clients. DDX (Device-Dependent X): Layer dependent on hardware, it is responsible for psychical rendering and teamwork with specific video drivers. DRI (Direct Rendering Infrastructure): key mechanism that improved efficiency of 3D graphics on Linux. In traditional model of X11 every app needed to send it's own instructions to the X.Org server, and then it started to send those instructions to the GPU, for the 3D games (for example Quake) it meant drastic latency and low framerate (FPS). DRI avoids this problem: it allows 3D apps (that are using OpenGL or Vulkan) to talk directly with GPU, completely avoiding X.Org Server. == Drivers and Input Managing == traditional X.Org was depending on drivers of the user (DDX), like <code>xf86-video-intel</code>, <code>xf86-video-amdgpu</code> or proprietary NVIDIA drivers, at the same time system is in bigger matter using kernel mechanisms like KMS (Kernel Mode-Setting). In case of input devices, historical drivers like evdev, synaptics are currently replaced by universal library name libinput, that is providing consistent gesture and keyboard support through X.Org and (via wrapper xf86-input-libinput) for [[Wayland]]. == Current Status of X.Org vs Wayland == Although X.Org has powered systems such as [[Slackware]], [[Debian]], [[Ubuntu]], [[Fedora]], [[EndeavourOS|EndeavorOS]], and [[Arch Linux]] for over two decades (allowing graphical enviroments to work e.g. [[KDE Plasma|KDE]], [[XFCE]], [[MATE]], [[LXQt|LXQT]]), now is currently undergoing deep maintenance. Modern distributions are replacing it layer by layer with [[Wayland]] protocol, that is eliminating architecture client-server for the easier and safer model. when compositor is talking directly with kernel and hardware. Besides that, X.Org is still an Key Component of the ecosystem thanks to: # XWayland: Translation layer, that allows running older apps for X11 on [[Wayland]]. # Stability: Unparalleled design maturity, flexibility of network configurations, and full support for specific legacy software. a4583a0c175aaa9f1bae72fbee4090075b51194b 4912 4909 2026-05-23T10:27:41Z Aktywnyyy 296 fixing grammar mistakes wikitext text/x-wiki '''X.org''' [[File:X.Org Logo.svg.png|center|thumb|'''X.Org logo (1999)''']] '''X.Org''' (full name: X.Org Server) is a free and opensource ([[FOSS]]) implementation of X Window System ([[X11]]) server, it implicates fundamental graphical layer used in traditional UNIX and Linux operating system environments. Responsible for managing the graphical interface, rendering image on the screen and input device support, like keyboards, mouses and touch screens. == History and Origin == The roots of the project date back to the 1980s. at the MIT university the same one that created [[X11]], direct predecessor of X.Org was XFree86. In 2004, as a result of controversial license changes on XFree86 (Version 4.4.0), community and developers decided to create a fork, and that resulted creation of X.Org Foundation and release of X.Org, which quickly became a standard in the mainline in all important Linux Distributions. == Architecture Client-Server == X.Org is based on classic, network model client-server, which distinguishes it from other modern protocols like [[Wayland]]: Server (X Server): It works directly on user's workstation, it manages hardware like, Screen, GPU and input devices Clients (X Clients): these are graphical applications (e.g web browser, video player, terminal). They don't draw anything directly on screen, instead they send requests to the server, asking if they can draw a window. [[File:X client server example.png|thumb|422x422px|X client Client-Server Architecture '''Example''']] == Key components == Internal architecture of X.Org is based on layers, that were evolving in the time of decades, to keep up with hardware: DIX (Device-Independent X): Layer Not dependent on hardware. It is responsible for processing X11 protocol, managing windows and communication between Clients. DDX (Device-Dependent X): Layer dependent on hardware, it is responsible for physical rendering and teamwork with specific video drivers. DRI (Direct Rendering Infrastructure): key mechanism that improved efficiency of 3D graphics on Linux. In traditional model of X11 every app needed to send it's own instructions to the X.Org server, and then it started to send those instructions to the GPU, for the 3D games (for example Quake) it meant drastic latency and low framerate (FPS). DRI avoids this problem: it allows 3D apps (that are using OpenGL or Vulkan) to talk directly with GPU, completely avoiding X.Org Server. == Drivers and Input Managing == traditional X.Org was depending on drivers of the user (DDX), like <code>xf86-video-intel</code>, <code>xf86-video-amdgpu</code> or proprietary NVIDIA drivers, at the same time system is in bigger matter using kernel mechanisms like KMS (Kernel Mode-Setting). In case of input devices, historical drivers like evdev, synaptics are currently replaced by universal library name libinput, that is providing consistent gesture and keyboard support through X.Org and (via wrapper xf86-input-libinput) for [[Wayland]]. == Current Status of X.Org vs Wayland == Although X.Org has powered systems such as [[Slackware]], [[Debian]], [[Ubuntu]], [[Fedora]], [[EndeavourOS|EndeavorOS]], and [[Arch Linux]] for over two decades (allowing graphical enviroments to work e.g. [[KDE Plasma|KDE]], [[XFCE]], [[MATE]], [[LXQt|LXQT]]), now is currently undergoing deep maintenance. Modern distributions are replacing it layer by layer with [[Wayland]] protocol, that is eliminating architecture client-server for the easier and safer model. when compositor is talking directly with kernel and hardware. Besides that, X.Org is still an Key Component of the ecosystem thanks to: # XWayland: Translation layer, that allows running older apps for X11 on [[Wayland]]. # Stability: Unparalleled design maturity, flexibility of network configurations, and full support for specific legacy software. 28899404e20f13c980701e7ace1888ca4923e923 0 1173 4910 2026-05-23T10:17:33Z Amilie 113 Drafting initial section for PowerBook 100, 140 and 170. Need to add information about overall industry sales, and the fact that Apple did not have appropriate ways to control heat on new Intel processors meaning laptops fell behind. Discuss upcoming laptops, and also upgradability to PPC. wikitext text/x-wiki The PowerBook was a line of product released by Apple Inc running [[MacOS]] between 1991 and 2007. The PowerBook line up ended with the PowerBook G4 which ran at 1.67Ghz after concerns of power consumption, and heat became a major concern in the laptop. Apple proceeded to move to Intel in 2008, killing the PowerBook line in the process and moving to the "MacBook" branding. == The PowerBook 100, 140 & 170 Series == Apple released their initial PowerBooks in 1991, with the PowerBook 100, 140 and 170 - each more powerful than the last respectively. Notably, the PowerBook 170 came with an active matrix display, which was part of its "high-end" design specifications. They created a wave in the industry as they compacted so much into such small gray cases, featured an integrated trackball, and also placed the keyboard in a way that palm rests were possible on either side. At the time, most laptops ran upon DOS, and that included the PowerBook. DOS permitted the PowerBook to have a functioning GUI, and permitted Apple to focus on optimizing the hardware for the user. The PowerBook 140 and 170 were the initial designs of the PowerBook, however the PowerBook 100 was designed by Apple & Sony in collaboration, with Apple sending the design schematics to Sony who made the various parts smaller and more suited for a laptop of it's size. The PowerBook 100 did not initially sell well until Apple opted to drop the price significantly beyond what it was initially. Apple opted to unify the PowerBooks with their corporate design, following a dark gray color scheme. Unlike the older laptops which Apple shipped, which were modeled more like a desktop. The PowerBook was smaller, more material efficient and easier to handle. This unification with the design language permitted Apple to also unify their software. These 100, 140 and 170 laptops however would be the last to use this design with proceeding laptops using a new, different color scheme. eb4d46f05431d1c542f3ef891d244bfb22de2930 4916 4910 2026-05-23T10:45:41Z Amilie 113 Add info about the PowerBook duo, and failure to innovate on the original PowerBooks. wikitext text/x-wiki The PowerBook was a line of product released by Apple Inc running [[MacOS]] between 1991 and 2007. The PowerBook line up ended with the PowerBook G4 which ran at 1.67Ghz after concerns of power consumption, and heat became a major concern in the laptop. Apple proceeded to move to Intel in 2008, killing the PowerBook line in the process and moving to the "MacBook" branding. == The PowerBook 100, 140 & 170 Series == Apple released their initial PowerBooks in 1991, with the PowerBook 100, 140 and 170 - each more powerful than the last respectively. Notably, the PowerBook 170 came with an active matrix display, which was part of its "high-end" design specifications. They created a wave in the industry as they compacted so much into such small gray cases, featured an integrated trackball, and also placed the keyboard in a way that palm rests were possible on either side. At the time, most laptops ran upon DOS, and that included the PowerBook. DOS permitted the PowerBook to have a functioning GUI, and permitted Apple to focus on optimizing the hardware for the user. The PowerBook 140 and 170 were the initial designs of the PowerBook, however the PowerBook 100 was designed by Apple & Sony in collaboration, with Apple sending the design schematics to Sony who made the various parts smaller and more suited for a laptop of it's size. The PowerBook 100 did not initially sell well until Apple opted to drop the price significantly beyond what it was initially. Apple opted to unify the PowerBooks with their corporate design, following a dark gray color scheme. Unlike the older laptops which Apple shipped, which were modeled more like a desktop. The PowerBook was smaller, more material efficient and easier to handle. This unification with the design language permitted Apple to also unify their software. These 100, 140 and 170 laptops however would be the last to use this design with proceeding laptops using a new, different color scheme. The first PowerBooks were incredibly successful, capturing over 40% of all laptop sales initially. However - even though such success was seen, the team who worked initially on the PowerBook ended up moving to Compaq. Apple did attempt to update the PowerBook series, but the Intel 68040 was simply too hard to manage the heating on. This left the PowerBook outdated with the 68030, rapidly falling behind industry standard. As the decade developed, other companies would also integrate Apple's flagship features meaning that their industry lead would fall - especially as their devices could not keep up in raw performance until the release of the PowerBook 500 in 1994. == The PowerBook Duo == [[File:PowerBook Duo 2300c 1.jpg|alt=An image of a PowerBook Duo 2300c.|thumb|205x205px|PowerBook Duo 2300c]] In 1992, Apple released the PowerBook Duo - an ultra minimal, and feature limited device focused at students. The various parts of the PowerBook duo however, could be upgraded via a docking station allowing for the usage of a monitor, and increased VRAM, storage, and connections for peripherals. The PowerBook Duo 2300c, introduced in 1995 - and being discontinued in 1997 - was equipped with a 100MHz PowerPC 603e, with a non-upgradable processor due to the processor being soldered to the board, initially running the "Classic" macOS series of operating systems. By standard, it came with only 8Mb of RAM, however this could be upgraded up to 56Mb should the user opt to. This PowerBook was initially sold at the market prices of $3500, and $4500 respectively. 8651733f166ab760ad04fe2b42341cbec80b4c54 4917 4916 2026-05-23T10:47:37Z Amilie 113 Add image for PowerBook 150. wikitext text/x-wiki The PowerBook was a line of product released by Apple Inc running [[MacOS]] between 1991 and 2007. The PowerBook line up ended with the PowerBook G4 which ran at 1.67Ghz after concerns of power consumption, and heat became a major concern in the laptop. Apple proceeded to move to Intel in 2008, killing the PowerBook line in the process and moving to the "MacBook" branding. == The PowerBook 100, 140 & 170 Series == [[File:Macintosh PowerBook 150.JPG|alt=A Macintosh PowerBook 150 in a museum casing.|thumb|379x379px|The Macintosh PowerBook 150.]] Apple released their initial PowerBooks in 1991, with the PowerBook 100, 140 and 170 - each more powerful than the last respectively. Notably, the PowerBook 170 came with an active matrix display, which was part of its "high-end" design specifications. They created a wave in the industry as they compacted so much into such small gray cases, featured an integrated trackball, and also placed the keyboard in a way that palm rests were possible on either side. At the time, most laptops ran upon DOS, and that included the PowerBook. DOS permitted the PowerBook to have a functioning GUI, and permitted Apple to focus on optimizing the hardware for the user. The PowerBook 140 and 170 were the initial designs of the PowerBook, however the PowerBook 100 was designed by Apple & Sony in collaboration, with Apple sending the design schematics to Sony who made the various parts smaller and more suited for a laptop of it's size. The PowerBook 100 did not initially sell well until Apple opted to drop the price significantly beyond what it was initially. Apple opted to unify the PowerBooks with their corporate design, following a dark gray color scheme. Unlike the older laptops which Apple shipped, which were modeled more like a desktop. The PowerBook was smaller, more material efficient and easier to handle. This unification with the design language permitted Apple to also unify their software. These 100, 140 and 170 laptops however would be the last to use this design with proceeding laptops using a new, different color scheme. The first PowerBooks were incredibly successful, capturing over 40% of all laptop sales initially. However - even though such success was seen, the team who worked initially on the PowerBook ended up moving to Compaq. Apple did attempt to update the PowerBook series, but the Intel 68040 was simply too hard to manage the heating on. This left the PowerBook outdated with the 68030, rapidly falling behind industry standard. As the decade developed, other companies would also integrate Apple's flagship features meaning that their industry lead would fall - especially as their devices could not keep up in raw performance until the release of the PowerBook 500 in 1994. == The PowerBook Duo == [[File:PowerBook Duo 2300c 1.jpg|alt=An image of a PowerBook Duo 2300c.|thumb|205x205px|PowerBook Duo 2300c]] In 1992, Apple released the PowerBook Duo - an ultra minimal, and feature limited device focused at students. The various parts of the PowerBook duo however, could be upgraded via a docking station allowing for the usage of a monitor, and increased VRAM, storage, and connections for peripherals. The PowerBook Duo 2300c, introduced in 1995 - and being discontinued in 1997 - was equipped with a 100MHz PowerPC 603e, with a non-upgradable processor due to the processor being soldered to the board, initially running the "Classic" macOS series of operating systems. By standard, it came with only 8Mb of RAM, however this could be upgraded up to 56Mb should the user opt to. This PowerBook was initially sold at the market prices of $3500, and $4500 respectively. c04394b45c4e9cba330f775effe6d87666b5ba3e 6 1174 4911 2026-05-23T10:27:20Z Habaja1 377 The logo for TailsOS. wikitext text/x-wiki == Summary == The logo for TailsOS. == Licensing == {{Unknown_copyright}} 3b8ec00d3db15d768da4991b18fc1f9975c71fe5 4913 4911 2026-05-23T10:29:29Z Habaja1 377 Habaja1 uploaded a new version of [[File:Tails-logo.png]] wikitext text/x-wiki == Summary == The logo for TailsOS. == Licensing == {{Unknown_copyright}} 3b8ec00d3db15d768da4991b18fc1f9975c71fe5 0 1175 4914 2026-05-23T10:30:31Z Habaja1 377 Created TailsOS page and bare bones wikitext text/x-wiki TailsOS (or TAILS), short for The Amnesic Incognito Live System, is a [[Debian]] based security-focused [[Linux Distributions|linux distribution]]. It focuses on preserving privacy and anonymity against surveillance.{{DistributionInfobox|title=TailsOS|image=[[File:Tails-logo.png]]|caption=TailsOS's logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=GNOME|usagetype=Desktop|architectures=x86_64|website=[https://tails.net/index.en.html]}} acf67c292d14b2c1a4366a6fbf2a5499f95ef9b7 4918 4914 2026-05-23T10:51:34Z Eeveestatic 379 Improve first paragraph wikitext text/x-wiki TailsOS (or TAILS), short for "The Amnesic Incognito Live System", is a [[Debian]] based security-focused [[Linux Distributions|linux distribution]] intent on preserving privacy and anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so.{{DistributionInfobox|title=TailsOS|image=[[File:Tails-logo.png]]|caption=TailsOS's logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=GNOME|usagetype=Desktop|architectures=x86_64|website=[https://tails.net/index.en.html]}} c68b3754a9680009889ef67925d0ae7eb8d4b669 4919 4918 2026-05-23T10:52:31Z Eeveestatic 379 wikitext text/x-wiki '''TailsOS''' ''(or TAILS)'', short for '''"The Amnesic Incognito Live System"''', is a [[Debian]] based security-focused [[Linux Distributions|linux distribution]] intent on preserving privacy and anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so.{{DistributionInfobox|title=TailsOS|image=[[File:Tails-logo.png]]|caption=TailsOS's logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=GNOME|usagetype=Desktop|architectures=x86_64|website=[https://tails.net/index.en.html]}} 6891ba7cb81629550d9b1226c84f1f1798f3c50f 0 1176 4915 2026-05-23T10:43:20Z Eeveestatic 379 Creation of Chimera Linux page, needs much more improvement wikitext text/x-wiki '''Chimera Linux''' is an independent [[Linux Distributions|Linux distribution]] characterized by using novel tooling, approaches, and userland.<ref>https://chimera-linux.org/</ref> {{DistributionInfobox|architechtures=x86_64, ppc, ppc64, ppc64le, aarch64, riscv64|defaultdesktops=Gnome, Terminal User Interface|packagemanager=[[apk-tools]]|title=Chimera Linux|usagetype=Desktop|website=[https://chimera-linux.org/ chimera-linux.org]}} <references /> ef2e62daa18cd711c1ad18a1125f2c653e484df3 0 1175 4920 4919 2026-05-23T10:53:23Z Eeveestatic 379 Tails is arguably more intent on privacy protection over security wikitext text/x-wiki '''TailsOS''' ''(or TAILS)'', short for '''"The Amnesic Incognito Live System"''', is a [[Debian]] based privacy-focused [[Linux Distributions|linux distribution]] intent on preserving privacy and anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so.{{DistributionInfobox|title=TailsOS|image=[[File:Tails-logo.png]]|caption=TailsOS's logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=GNOME|usagetype=Desktop|architectures=x86_64|website=[https://tails.net/index.en.html]}} 61b5d3361d36a33d7e65a755b7aea576a850c809 4921 4920 2026-05-23T10:54:00Z Eeveestatic 379 wikitext text/x-wiki '''TailsOS''' ''(or TAILS)'', short for '''"The Amnesic Incognito Live System"''', is a [[Debian]] based privacy-focused [[Linux Distributions|linux distribution]] intent on preserving anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so.{{DistributionInfobox|title=TailsOS|image=[[File:Tails-logo.png]]|caption=TailsOS's logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=GNOME|usagetype=Desktop|architectures=x86_64|website=[https://tails.net/index.en.html]}} 09f9d6ce268def0c7fe2d732bbaa711d576782ae 4924 4921 2026-05-23T12:08:26Z Matthias von Schwarzwald 361 Typos wikitext text/x-wiki '''TailsOS''' ''(or TAILS)'', short for '''"The Amnesic Incognito Live System"''', is a [[Debian]]-based privacy-focused [[Linux Distributions|Linux distribution]] intent on preserving anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so.{{DistributionInfobox|title=TailsOS|image=[[File:Tails-logo.png]]|caption=TailsOS's logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=GNOME|usagetype=Desktop|architectures=x86_64|website=[https://tails.net/index.en.html]}} 461ca19e7cf7922fcfe0bb4bba06114a537997d0 4926 4924 2026-05-23T12:12:04Z Matthias von Schwarzwald 361 Add distros category and stub warning wikitext text/x-wiki {{Stub}} '''TailsOS''' ''(or TAILS)'', short for '''"The Amnesic Incognito Live System"''', is a [[Debian]]-based privacy-focused [[Linux Distributions|Linux distribution]] intent on preserving anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so.{{DistributionInfobox|title=TailsOS|image=[[File:Tails-logo.png]]|caption=TailsOS's logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=GNOME|usagetype=Desktop|architectures=x86_64|website=[https://tails.net/index.en.html]}} [[Category:Linux Distributions]] 8c8966b19640e5a737e49879d422c957fa2cca67 4949 4926 2026-05-23T14:52:57Z Matthias von Schwarzwald 361 GNOME link wikitext text/x-wiki {{Stub}} '''TailsOS''' ''(or TAILS)'', short for '''"The Amnesic Incognito Live System"''', is a [[Debian]]-based privacy-focused [[Linux Distributions|Linux distribution]] intent on preserving anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so.{{DistributionInfobox|title=TailsOS|image=[[File:Tails-logo.png]]|caption=TailsOS's logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=[[GNOME]]|usagetype=Desktop|architectures=x86_64|website=[https://tails.net/index.en.html]}} [[Category:Linux Distributions]] 46a3072da6c2b8c2b2ba77960f6c32bec5070723 4950 4949 2026-05-23T15:03:23Z Uniolo 345 Moved sidebar to top, added screenshot of TailsOS. wikitext text/x-wiki {{Stub}} {{DistributionInfobox|title=TailsOS|image=[[File:Tails-logo.png]]|caption=TailsOS's logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=[[GNOME]]|usagetype=Desktop|architectures=x86_64|website=[https://tails.net/index.en.html]}} [[File:TAILS 4.14 ENG 05 01 2021 15 39 25.png|thumb|TailsOS open to the "About Tails" screen]] '''TailsOS''' ''(or TAILS)'', short for '''"The Amnesic Incognito Live System"''', is a [[Debian]]-based privacy-focused [[Linux Distributions|Linux distribution]] intent on preserving anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so. [[Category:Linux Distributions]] bcce061733eb81afbbb56abf09ddc419cd264a03 2 1177 4922 2026-05-23T10:57:25Z Eeveestatic 379 Creating userpage for myself wikitext text/x-wiki Welcome to my user page. I am a FOSS and privacy advocate intent on promoting freedom of information. 1db5776ba2abb95bfc87a0b4d2b27247dffa6e1e 0 1178 4923 2026-05-23T11:51:24Z Teapot 376 Added descriptions of all the core distros (except debian) including bootc based ones as grouped together. wikitext text/x-wiki All of the following systems are widely supported and '''most''' others are going to be derived from these. == Ubuntu == + Has both an LTS release and a non-LTS release with upgrade periods of 2 years and 6 months respectively. + Non-LTS version is decently up-to-date with support for decently new hardware. + Simple to get started with: includes an intuitive installer and comes with GUI app stores. + Easy Nvidia drivers with hardware detection using the ubuntu-drivers tool. - Comes with Snap Store by default, which can be problematic for some software such as Steam. - LTS release comes with heavy tradeoff as it may just miss big updates or hardware support. - Non-LTS release is not guaranteed to be stable and may break on updates. == Arch Linux == + Rolling release, meaning there is no concept of a "version" and all packages are updated individually to their own latest stable versions. + Can be assembled from scratch, allowing the system to be exactly the way the user wants. This is supported by an exhaustive wiki detailing most of the Linux system components. + Contains the archinstall script, providing a TUI installer to avoid manual setup. + The largest official repositories out of the all distributions; also the Arch User Repository (AUR) which optionally can be used at their own risk. + Pre-built Nvidia kernel modules for official kernels. - Requires some extent of expected system maintenance, e.g. when package names are changed or split in official repositories. - Hard to maintain because there's no single configuration any user can be expected to have. - Does not have very good options for GUI package management. == Fedora Linux == + Releases a new version every 6 months for core components like the desktop, still has packages near as latest as a rolling release. + Decent installation process and supports GUI app stores by default. - Harder to setup as it relies on third-party repositories for non-free software like media codecs and Nvidia drivers. - Version upgrades are again not guaranteed to not break. - Mostly a testing ground for any new Linux capabilities, hence might choose to update to newer technologies first in the race. == openSUSE Tumbleweed == + Rolling release. + Decent installer and has its own utilities for GUI package management and system management. - Reliance on third-party repositories for codecs and drivers. == bootc-based systems (Silverblue, Bazzite etc) == + No system-level package management: the system is contained in the form of an image, which updates as a whole every new release. + Hence, easy rollbacks in case of broken updates. Also easier maintenance because there is more expectation on the state of the every system. + Can be switched between one another in a single command. + Different images have different goals; Bazzite provides a good setup and there is no involvement needed for drivers. - No easy way to change the system, hence some things can not be achieved without making your own image. This includes out-of-tree drivers, or any other packages that NEED to be on the system to work properly, such as Discord RPC, VPNs, password managers etc. e5033fc69785788823db02068310b994dc1f4490 0 784 4925 4717 2026-05-23T12:11:15Z Matthias von Schwarzwald 361 Add distros category and stub warning wikitext text/x-wiki {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = GNOME | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }}{{Stub}} Zorin OS is a Ubuntu-based Linux distribution made for newcomers to Linux, with a modified version of the Gnome GUI and XFCE 4 that is familiar to Windows users. It also has a paid model that comes with more desktop options and free software. it was first released on the first of July, 2009, under the name Zorin OS 1.0. [[Category:Linux Distributions]] b76c38ec7a5f82b0af8f2186c928669002792319 4931 4925 2026-05-23T12:59:25Z Matthias von Schwarzwald 361 Linking and more typos wikitext text/x-wiki {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = [[GNOME]] | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }}{{Stub}} Zorin OS is an [[Ubuntu]]-based [[Linux Distributions|Linux distribution]] made for newcomers to Linux, with a modified version of the [[GNOME]] GUI and [[XFCE|XFCE 4]] that is familiar to Windows users. It also has a paid model that comes with more desktop options and free software. It was first released on the first of July, 2009, under the name Zorin OS 1.0. [[Category:Linux Distributions]] f6c59663ba79fe5a54275a92e9256eacff51a1bd 0 661 4927 4218 2026-05-23T12:18:55Z Matthias von Schwarzwald 361 Typos wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Kali Linux | image = [[File:Kali-dragon-icon.svg|frameless]] | caption = Kali Logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APT]] | defaultdesktops = [[Xfce]], [[GNOME]], [[KDE Plasma]] | usagetype = Desktop, Mobile, USB | architectures = x86_64, x86, armel, armhf | website = [https://www.kali.org/ Kali.org] }} '''Kali Linux''' (originally Backtrack Linux<ref>https://www.kali.org/docs/introduction/kali-linux-history/</ref>) is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, digital forensics, and penetration testing. It is maintained and funded by [https://www.offsec.com/ '''Offensive Security''']. === Features === Kali Linux is supported in wide range of devices ranging from Raspberry Pis to modern systems. It comes preinstalled with various tools useful for security professionals and includes a custom kernel patched for injection. It is also suitable for live USB boot with persistence.<ref>https://www.kali.org/docs/nethunter/</ref> === Installation === There are various ways to get Kali Linux. One can download the respective Kali version from the [https://www.kali.org/get-kali/#kali-platforms official download page].<ref name=":0">https://www.kali.org/docs/installation/</ref> {| class="wikitable mw-collapsible" |+Kali Variations<ref>www.kali.org/get-kali/#kali-installer-images</ref> !Variation !Function |- |ISO File |The most common way to install; suitable for both single and multi boot; providing the best performance. |- |Virtual Machine Image |Pre-built images for running Kali in a virtual machine; has higher system requirements. |- |ARM |Suitable for ARM devices; not guaranteed a custom kernel; some packages missing. |- |Mobile (Nethunter) |Kali for smartphones. |- |Cloud |Running Kali on a cloud server; not guaranteed a custom kernel. |- |Containers |Quick and easy access to Kali using software such as Docker; no custom kernel; no direct access to hardware thus slow. |- |Live Boot (Recommended) |Quick and easy access to Kali on the go. The preferred method of using Kali Linux. |- |WSL |Using Kali in windows. |} A bare bones version of Kali can also be installed which has a headless size of 1.5GB, the default Kali Linux is around 13GB while the version with everything in it is around 34GB.<ref>https://www.kali.org/docs/installation/installation-sizes/</ref> Full guide to installation size with various [https://atl.wiki/Desktop_Environments Desktop Environments] can be found [https://www.kali.org/docs/installation/installation-sizes/ here] . The system requirements vary but generally minimum of 2GB RAM and 20GB of disk space is needed to run Kali. Installation of Kali can be done fairly easily using the official GUI installer. The official guide to installing Kali are at:<ref name=":0" /> * [https://www.kali.org/docs/installation/hard-disk-install/ Hard Disk Install] * [https://www.kali.org/docs/installation/hard-disk-install-on-mac/ Mac Hardware] * [https://www.kali.org/docs/installation/dual-boot-kali-with-linux/ Dual Booting with Linux] (What's [[Dual Booting|Multi Booting]]) * [https://www.kali.org/docs/installation/dual-boot-kali-with-mac/ Dual Booting with MacOS] * [https://www.kali.org/docs/installation/dual-boot-kali-with-windows/ Dual Booting with Windows] === Other Versions === '''[https://www.kali.org/docs/nethunter/ Kali Nethunter]''' is the mobile version of Kali Linux, available for unrooted devices (Nethunter Rootless), rooted devices with custom recovery (Nethunter Lite), rooted devices with custom recovery and custom kernel (Nethunter) and on certain supported devices with '''full functionality''' (Nethunter Pro).<ref>https://www.kali.org/docs/nethunter/</ref> See [https://www.kali.org/docs/nethunter/#10-nethunter-editions Nethunter Editions] for detailed comparison between the editions and [[Kali Nethunter]] for more details. '''[https://gitlab.com/kalilinux/kali-purple/documentation/-/wikis/home Kali Purple]''' is the enterprise grade version of Kali which comes with over 100 tools, Kali Autopilot (automatic script builder) and its own wiki. == References == <references /> === Footnotes === * KALI LINUX ™ is a trademark of [https://www.offsec.com/ OffSec]. 5b03c322c6d4fa4d0af7882b6fa6ed58b6fd2a87 0 198 4928 4885 2026-05-23T12:23:09Z Matthias von Schwarzwald 361 Italicize Funtoo and Tinfoil Hat as abandoned wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 520f92a11b18a687b8b58f2f55ee003e908eb1ad 4966 4928 2026-05-23T17:28:10Z Habaja1 377 added KDE neon distro wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[TOR]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of KDE plasma. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 7a758f82b4f05a56b6dad6377312bca230192be2 0 1091 4929 4759 2026-05-23T12:49:51Z MysteryBirb 353 Added NixOS install guide wikitext text/x-wiki {{Work In Progress}} {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox |caption=MangoWM logo |developers=MangoWM developers |firstrelease=0.1.1, 2025-02-17 |languages=[[C]] |lastrelease=V0.13.1, 2026-05-18 |title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io] |releasestatus=Maintained |image=[[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formally known as MangoWC) is a [[Wayland]] compositor based on [[dwl]] that keeps its lightweight, suckless-style design while adding more practical features.I think it looks alright. While staying minimal and fast to build, MangoWM improves on usability with better layouts, multi-monitor supports, and broader wayland compatibility. === Highlighted Features: === * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. ==== Additional Features: ==== * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag === Installation: === ===== AerynOS: ===== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ===== Arch: ===== Using yay: <syntaxhighlight lang="bash"> yay -S mangowm </syntaxhighlight> or for the latest git version: <syntaxhighlight lang="bash"> yay -S mango-git </syntaxhighlight> Using paru: <syntaxhighlight lang="bash"> paru -S mangowm </syntaxhighlight> or for the latest git version: <syntaxhighlight lang="bash"> paru -S mango-git </syntaxhighlight> ===== Fedora: ===== First we need to add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then, install it with dnf: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ===== Gentoo: ===== Firstly we add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Followed by unmasking of these packages in your package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ===== Guix System: ===== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ===== NixOS: ===== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref>. ===== PikaOS: ===== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> === Building from source: === Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ===== Dependencies: ===== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ===== Building wlroots from source: ===== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ===== Building scenefx from source: ===== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building MangoWM from source: ==== At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 8e3bf1db6c156d6bc26fa682e571b130268b6cf6 0 1143 4930 4831 2026-05-23T12:57:32Z Uniolo 345 Added sidebar and note about being configured in Lua wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:Neovim-mark.svg|thumb]] |caption=NeoVim |title=NeoVim |releasestatus=Maintained |lastrelease=0.12.2, Apr 22, 2026 |firstrelease=0.15, Aug 23, 2016 |languages=[[C]], [[Lua]], [[Vim Script]] |developers=Thiago de Arruda |website=[https://neovim.io/ neovim.io] }} [[File:Neovim v0.9.0-dev intro screen.png|thumb|Neovim 0.9.0 splash screen]] '''Neovim''' (also known as '''nvim''') is a configurable terminal text editor for Linux, Windows, and macOS. It is configured in [[Lua]]. b8919c15acf31032d421af02779980ff14962dac 4933 4930 2026-05-23T13:12:41Z Uniolo 345 Added information about Neovim being compatible with Vim, and Vim Script wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:Neovim-mark.svg|thumb]] |caption=NeoVim |title=NeoVim |releasestatus=Maintained |lastrelease=0.12.2, Apr 22, 2026 |firstrelease=0.15, Aug 23, 2016 |languages=[[C]], [[Lua]], [[Vim Script]] |developers=Thiago de Arruda |website=[https://neovim.io/ neovim.io] }} [[File:Neovim v0.9.0-dev intro screen.png|thumb|Neovim 0.9.0 splash screen]] '''Neovim''' (also known as '''nvim''') is a configurable terminal text editor for Linux, Windows, and macOS. It is configured in [[Lua]]. Neovim is based on [[Vim]]<ref>{{Cite|url=https://github.com/neovim/neovim/commit/9f13983de280c53971a8997ead0d6e9d4e3d3e42|title=Commit 9f13983, "vim-patch:7.4.2185"|author=lonerover|year=2017-03-11|accessdate=2026-05-23}}</ref>. Neovim is fully compatible with Vim's editing modal and [[Vim Script]]<ref>[https://neovim.io/ Neovim website] (accessed 2026-05-22)</ref>, and part of Neovim is written in [[Vim Script]]<ref>{{Cite|url=https://github.com/neovim/neovim|title=Neovim GIthub|author=[https://github.com/orgs/neovim/people Neovim Contributors]|year=2026-05-23|accessdate=2026-05-23}}</ref>. 361e2fed3b559b74b3c8d51adebac35cd49f5911 4939 4933 2026-05-23T13:28:04Z Uniolo 345 Added note about Charityware and replaced image of Neovim with one I took showing that it is Charityware. wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:Neovim-mark.svg|thumb]] |caption=NeoVim |title=NeoVim |releasestatus=Maintained |lastrelease=0.12.2, Apr 22, 2026 |firstrelease=0.15, Aug 23, 2016 |languages=[[C]], [[Lua]], [[Vim Script]] |developers=Thiago de Arruda |website=[https://neovim.io/ neovim.io] }} [[File:Nevom-Splash.png|thumb|The Neovim 0.12.2 splash screen.]] '''Neovim''' (also known as '''nvim''') is a configurable terminal text editor for Linux, Windows, and macOS. It is configured in [[Lua]]. Neovim is based on [[Vim]]<ref>{{Cite|url=https://github.com/neovim/neovim/commit/9f13983de280c53971a8997ead0d6e9d4e3d3e42|title=Commit 9f13983, "vim-patch:7.4.2185"|author=lonerover|year=2017-03-11|accessdate=2026-05-23}}</ref>. Neovim is fully compatible with Vim's editing modal and [[Vim Script]]<ref>[https://neovim.io/ Neovim website] (accessed 2026-05-22)</ref>, and part of Neovim is written in [[Vim Script]]<ref>{{Cite|url=https://github.com/neovim/neovim|title=Neovim GIthub|author=[https://github.com/orgs/neovim/people Neovim Contributors]|year=2026-05-23|accessdate=2026-05-23}}</ref>. Like [[Vim]], Neovim can also be considered [[wikipedia:Careware|Charityware]] due to encouraging users to donate to [https://www.kuwasha.net/ Kuwasha]. 72ad50becb61c324d2104cdc01b5b232072ec5c6 0 562 4932 3652 2026-05-23T13:11:18Z Matthias von Schwarzwald 361 Typos wikitext text/x-wiki [[Category:Misc Operating Systems]] [[Category:Illumos]] {{DistributionInfobox | title = OpenIndiana | image = [[File:OpenIndiana_logo_small.svg|100px]] | caption = Logo of OpenIndiana | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = IPS <ref>[https://docs.openindiana.org/handbook/getting-started/#image-package-system-ips Getting Started - OpenIndiana Docs], The OpenIndiana Project, 2025-08-06 (Accessed: 2025-08-09)</ref> | defaultdesktops = MATE | usagetype = Desktop, Server | architectures = x86_64, SPARC [beta] | website = [https://www.openindiana.org/ openindiana.org] }} OpenIndiana is a Unix-like [[Operating System|operating system]] based on the [[Ilumos|Illumos]] kernel.<ref>[https://docs.openindiana.org/misc/openindiana/#what-is-the-openindiana-operating-system What is OpenIndiana Project?], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> Announced on September 14, 2010, at a time of uncertainty after Oracle bought [[OpenSolaris|OpenSolaris]].<ref>[https://web.archive.org/web/20100913030810/https://www.openindiana.org/ Project OpenIndiana], The OpenIndiana Project, 2010-08-09 (Accessed: 2010-09-13)</ref> It was proved timely as Oracle shut down development of OpenSolaris.<ref>[https://web.archive.org/web/20201109033546/http://sstallion.blogspot.com/2010/08/opensolaris-is-dead.html OpenSolaris is Dead.], Iconoclastic Tendencies, August 13, 2010 (Accessed: July 13, 2025)</ref> OpenIndiana uses the same tooling as Solaris; the SMF init system,<ref>[https://docs.openindiana.org/handbook/systems-administration/#service-management-facility Service Management Facility], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> FMA fault management system,<ref>[https://docs.openindiana.org/misc/openindiana/#what-features-does-openindiana-have What features does OpenIndiana have?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and IPS package manager.<ref>[https://docs.openindiana.org/handbook/systems-administration/#software-management Software management], OpenIndiana Contributors (Accessed: July 13, 2025)</ref> The majority of the [https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/ Solaris documentation] also applies to OpenIndiana.{{Citation needed}} OpenIndiana makes use of the SunOS branch of the UNIX kernel,<ref>[https://docs.openindiana.org/misc/openindiana/#why-is-it-called-openindiana Why is it called OpenIndiana?] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> and thus provides all of the stability benefits of a UNIX System V derivative.{{Citation needed}} This does, however, mean that hardware support is limited in comparison to a BSD- or Linux-based OS.<ref>[https://docs.openindiana.org/community-hcl/getting-hardware-info/ Getting information about hardware] OpenIndiana Contributors (Accessed: July 13, 2025)</ref> OpenIndiana uses the SunOS libc, which severely limits what software will compile on it successfully. SunOS libc only implements functions expected by POSIX and ANSI C.{{Citation needed}} == References == 7a13bc694fb7d30564d741da1604212ce5eb094f 0 534 4934 4902 2026-05-23T13:13:42Z Sparrow 362 Add Niri features wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox | image = [[File:Nirilogo.svg|300px|example_niri_rice]] | caption = Niri's logo | title = niri | releasestatus = Maintained | firstrelease = v0.1.0-alpha.1 | lastrelease = v26.04 | languages = [[Rust]] | developers = Ivan Molodetskikh A.K.A. YaLTeR | website = [https://github.com/YaLTeR/niri Github Repository] }} [[File:Niri Rice.png|thumb|A desktop running [[Niri]].]] Niri is a scrollable-tiling [[Wayland]] compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">[https://github.com/YaLTeR/niri/wiki/Important-Software Important Software · YaLTeR/niri Wiki · GitHub], YaLTeR, 2025-08-09 (Accessed: 2025-08-09)</ref> == Notable features of Niri include: * Dynamic workspaces similar to GNOME * [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/444776459-379a5d1f-acdb-4c11-b36c-e85fd91f0995.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260523%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260523T125301Z&X-Amz-Expires=300&X-Amz-Signature=75c2d0798e6c61573bf1455e04df47a6a17adb4c6ae4a63f4db920758db9db0a&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4 Overview] for managing workspaces * Built-in screenshot utility * [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from Block out] sensitive windows from screencasting * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260523%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260523T130056Z&X-Amz-Expires=300&X-Amz-Signature=eb6cc56f82db2e1479e0bde7ef6526e215362c74b4667165e4d5c835f3693bfa&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4 touchpad] and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260523%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260523T130215Z&X-Amz-Expires=300&X-Amz-Signature=cb539530de50996bea283c287d1efb5e79c46cb75f2b4aaec4c5fae8e9f3e758&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4 mouse] gestures * Tiling and floating window modes * Customizable [https://niri-wm.github.io/niri/Configuration%3A-Layout.html#gradients borders], [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331791576-27a238d6-0a22-4692-b794-30dc7a626fad.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260523%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260523T130941Z&X-Amz-Expires=300&X-Amz-Signature=33aead18339cb88343044619cad6feaaad576457bf740e360daf42fb4235e16d&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4 animations], and overall look and feel * Live-reloading after changing configurations * Compatibility with [[X11]] applications via [[XWayland]] == References == <references /> 70e57e98733408381fcd295a7eeb230ac9885598 0 1120 4935 4804 2026-05-23T13:16:39Z Uniolo 345 Removed symlink red link (since it should be on the terminology page if anything) and added note about Helix. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://iccf-holland.org/donate.html ICCF Holland]<ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim|NeoVim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use the <code>vimtutor</code> command. <code>Vim ''path/to/filename'' </code> is used to open a new or existing file for editing, though you can also open a file from within Vim. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] == References == <references /> 38bc2c08a3a726ff9d83927ce93bdbdcc887b083 0 396 4936 4907 2026-05-23T13:16:56Z Rob Kam 380 add File managers wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Description !DE |- |Discover |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Description !Distribution |- |[[pacman]] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Description |- |Midnight Commander |Two-panel terminal-based file manager. |- |nnn |Fast and lightweight terminal-based file manager. |- |ranger |Terminal-based file manager with vi-style keybindings. |- |yazi |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |ytree |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[https://github.com/KDE/krita Krita] |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |[https://github.com/RodZill4/material-maker Material Maker] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} 7e27e836f00ae6b81e88991f8258927d1edf63bf 4946 4936 2026-05-23T13:53:18Z Rob Kam 380 /* Terminal-based file managers */ wikitext text/x-wiki {{Work In Progress}} Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Description !DE |- |Discover |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Description !Distribution |- |[[pacman]] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Description |- |[[Midnight Commander]] |Two-panel terminal-based file manager. |- |nnn |Fast and lightweight terminal-based file manager. |- |ranger |Terminal-based file manager with vi-style keybindings. |- |yazi |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[https://github.com/KDE/krita Krita] |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |[https://github.com/RodZill4/material-maker Material Maker] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} a6d92829b5b4ac9372c1a112176f65df0b93875f 4955 4946 2026-05-23T15:36:57Z Rob Kam 380 add a few IDEs wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Description !DE |- |Discover |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Description !Distribution |- |[[pacman]] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Description |- |[[Midnight Commander]] |Two-panel terminal-based file manager. |- |nnn |Fast and lightweight terminal-based file manager. |- |ranger |Terminal-based file manager with vi-style keybindings. |- |yazi |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[https://github.com/KDE/krita Krita] |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |[https://github.com/RodZill4/material-maker Material Maker] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |nano |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Description !Focus |- |Code::Blocks |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} 277db7bc412a005eb1af3c7925e48b1213d7dc41 4958 4955 2026-05-23T15:51:36Z Uniolo 345 Added Vim and Helix wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Description !DE |- |Discover |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Description !Distribution |- |[[pacman]] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Description |- |[[Midnight Commander]] |Two-panel terminal-based file manager. |- |nnn |Fast and lightweight terminal-based file manager. |- |ranger |Terminal-based file manager with vi-style keybindings. |- |yazi |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[https://github.com/KDE/krita Krita] |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |[https://github.com/RodZill4/material-maker Material Maker] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |[[nano]] |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[vim]] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Description !Focus |- |Code::Blocks |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} aae61562dee2f95766a64353b3d8025ed1e44a97 0 175 4937 4288 2026-05-23T13:20:29Z Sparrow 362 Update pacman last release to latest wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 7.1.0, 2025-11-01 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[Category:Package Managers]] [[File:Pacman 401.png|thumb|[[Pacman]]]] The [[Linux Distributions|Linux distribution]] [[Arch Linux]] and its derivatives usually use a [[Package Manager|package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, although some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>[https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] == References == c81c9c2ac183d0471b0be13b39b89f8bc95b8cb7 6 1179 4938 2026-05-23T13:25:40Z Uniolo 345 wikitext text/x-wiki The Neovim 0.12.2 Splash Screen ab4b72ca0229c89898cd3a85f3fc8f9a97cc7a6b 0 1096 4940 4467 2026-05-23T13:29:24Z Matthias von Schwarzwald 361 Typos and other touchups wikitext text/x-wiki {{Stub}}{{DistributionInfobox | title = Pear OS | image = [[File:pearos.png|pearos.png]] | caption = Logo of Pear OS | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64 | website = https://pearos.xyz/ }} '''Pear OS''' is an operating system based on [[Arch Linux]] with default [[Linux|Linux Kernel]] (version 6.17) and [[systemd|SystemD]]. It is developed by one person. Its main purpose is to give Linux users the feeling of [[MacOS]]. == Information == Pear OS was originally developed as a web OS in 2010. The OS got later in 2014 sold to an unknown company, however in ~2022 Alexandru Bălan started developing the software again now it's available and free. [[Category:Linux Distributions]] 9ebcfa0faa27e220adbab3e073a48eab7b2a0004 4962 4940 2026-05-23T16:24:31Z Matthias von Schwarzwald 361 Fix Linus kernel link wikitext text/x-wiki {{Stub}}{{DistributionInfobox | title = Pear OS | image = [[File:pearos.png|pearos.png]] | caption = Logo of Pear OS | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64 | website = https://pearos.xyz/ }} '''Pear OS''' is an operating system based on [[Arch Linux]] with default [[Linux kernel]] (version 6.17) and [[systemd|SystemD]]. It is developed by one person. Its main purpose is to give Linux users the feeling of [[MacOS]]. == Information == Pear OS was originally developed as a web OS in 2010. The OS got later in 2014 sold to an unknown company, however in ~2022 Alexandru Bălan started developing the software again now it's available and free. [[Category:Linux Distributions]] 54e9d7283a388f5622a289f1dd8b0192e22e835b 0 764 4941 3682 2026-05-23T13:32:13Z Matthias von Schwarzwald 361 Typos wikitext text/x-wiki [[Category:Misc Operating Systems]] Tilck is a tiny monolithic [[kernel]] designed to be compatible with [[Linux]] on the binary level. It currently runs on the i686 and RISCV64 architectures, with plans to port it to ARM. It is intended for embedded systems due to its very small size and low-latency abilities. While Linux-compatible, Tilck does not aim to replace the Linux kernel, nor to be an alternative to it for desktop users. In its current state, Tilck implements about ~100 Linux system calls, allowing many programs intended for Linux to work out of the box. While it is not currently implemented, the developers plan to implement networking at some point, with the network cards of specific SoC being the initial targets.<ref>{{Cite|url=https://github.com/vvaltchev/tilck|title=Tilck: A Tiny Linux-Compatible Kernel|author=Vladislav K. Valtchev|year=Nov 22, 2024|accessdate=August 2, 2025}}</ref> == References == <references /> af0ab75ffa34a34110c779e3523daec3161ac2c9 2 1180 4942 2026-05-23T13:41:48Z Verl 364 added user info? wikitext text/x-wiki Verl (pronounced Vur + L) VTuber fan [https://www.youtube.com/watch?v=IhN7AAOX2eg uuu] (Hololive), ASMR enjoyer, Linux/macOS user (F**k Windows.), C amateur... Wiki enthusiast, anything to contribute to the growing collective knowledge! bad1b33636dfff895743dddfa777f753f6fccaf8 1 1140 4943 4743 2026-05-23T13:45:26Z Uniolo 345 /* Missing software. */ new section wikitext text/x-wiki == how to organize software == half actual discussion, half making sure some browsers aren't breaking this feature [[User:Nathan22211|Nathan22211]] ([[User talk:Nathan22211|talk]]) 01:07, 23 May 2026 (UTC) == Missing software. == This page has a header saying that, <code>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</code> So I am going to follow the advice and list some of the missing pages. * For the <code>Terminal-based text editors</code> section, we are missing [[Neovim]] and [[Helix]]. There is also a [[Nano]] page that is included but not linked to. * For the <code>Package managers</code>, we already have a [[Package Manager|page for them]] that lists many not on this page. * [[Tor]] is not listed anywhere, so are there a bunch of pages that are not listed. * And more™ This list is fairly incomplete, and definitely needs some work, but the header does state to talk before making edits, so perhaps a different header is required. @[[User:Electron271|Electron271]] pinging you since it seems like you were the one to add the header. [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 13:45, 23 May 2026 (UTC) 1cf071c5dfba229c6de044f3f30c67af921de418 4956 4943 2026-05-23T15:38:36Z Rob Kam 380 /* Missing software. */ Reply wikitext text/x-wiki == how to organize software == half actual discussion, half making sure some browsers aren't breaking this feature [[User:Nathan22211|Nathan22211]] ([[User talk:Nathan22211|talk]]) 01:07, 23 May 2026 (UTC) == Missing software. == This page has a header saying that, <code>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</code> So I am going to follow the advice and list some of the missing pages. * For the <code>Terminal-based text editors</code> section, we are missing [[Neovim]] and [[Helix]]. There is also a [[Nano]] page that is included but not linked to. * For the <code>Package managers</code>, we already have a [[Package Manager|page for them]] that lists many not on this page. * [[Tor]] is not listed anywhere, so are there a bunch of pages that are not listed. * And more™ This list is fairly incomplete, and definitely needs some work, but the header does state to talk before making edits, so perhaps a different header is required. @[[User:Electron271|Electron271]] pinging you since it seems like you were the one to add the header. [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 13:45, 23 May 2026 (UTC) :I removed the template because a wiki itself is a work in progress. [[User:Rob Kam|Rob Kam]] ([[User talk:Rob Kam|talk]]) 15:38, 23 May 2026 (UTC) 0caf153ba837a2d9d6046a8939bf501c9249820e 4959 4956 2026-05-23T15:51:57Z Uniolo 345 /* Missing software. */ Reply wikitext text/x-wiki == how to organize software == half actual discussion, half making sure some browsers aren't breaking this feature [[User:Nathan22211|Nathan22211]] ([[User talk:Nathan22211|talk]]) 01:07, 23 May 2026 (UTC) == Missing software. == This page has a header saying that, <code>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</code> So I am going to follow the advice and list some of the missing pages. * For the <code>Terminal-based text editors</code> section, we are missing [[Neovim]] and [[Helix]]. There is also a [[Nano]] page that is included but not linked to. * For the <code>Package managers</code>, we already have a [[Package Manager|page for them]] that lists many not on this page. * [[Tor]] is not listed anywhere, so are there a bunch of pages that are not listed. * And more™ This list is fairly incomplete, and definitely needs some work, but the header does state to talk before making edits, so perhaps a different header is required. @[[User:Electron271|Electron271]] pinging you since it seems like you were the one to add the header. [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 13:45, 23 May 2026 (UTC) :I removed the template because a wiki itself is a work in progress. [[User:Rob Kam|Rob Kam]] ([[User talk:Rob Kam|talk]]) 15:38, 23 May 2026 (UTC) ::I added Vim and Helix [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 15:51, 23 May 2026 (UTC) 3041001040192847db13574fdb224c6af13d491d 6 1181 4944 2026-05-23T13:47:45Z Rob Kam 380 Screenshot of Ytree v3.0.0-alpha F8 split view in a Linux terminal, with a directory tree and file list on one side and the files inside an archive on the other. wikitext text/x-wiki == Summary == Screenshot of Ytree v3.0.0-alpha F8 split view in a Linux terminal, with a directory tree and file list on one side and the files inside an archive on the other. == Licensing == {{CC-BY-SA-4.0}} dd9bb0db73ec9109a4e27b25526e03e7ed17ef21 0 1182 4945 2026-05-23T13:52:51Z Rob Kam 380 Created page with "[[Category:Software]] [[Category:File managers]] {{SoftwareInfobox | image = [[File:Ytree v3.0.0-alpha F8 split view.png|frameless]] | caption = Ytree v3.0.0-alpha in F8 split view | title = Ytree | releasestatus = Alpha (maintained) | lastrelease = v3.0.0-alpha (tagged 2026-04-29) | languages = [[C]] | developers = Rob Kam; based on original ytree by Werner Bregulla | website = https://github.com/robkam/ytree }} '''Ytree''' (<code>ytree</code>) is a keyboard-first TU..." wikitext text/x-wiki [[Category:Software]] [[Category:File managers]] {{SoftwareInfobox | image = [[File:Ytree v3.0.0-alpha F8 split view.png|frameless]] | caption = Ytree v3.0.0-alpha in F8 split view | title = Ytree | releasestatus = Alpha (maintained) | lastrelease = v3.0.0-alpha (tagged 2026-04-29) | languages = [[C]] | developers = Rob Kam; based on original ytree by Werner Bregulla | website = https://github.com/robkam/ytree }} '''Ytree''' (<code>ytree</code>) is a keyboard-first [[TUI]] file manager for UNIX-like systems. It follows a “logger” model: it scans directory trees into memory so users can navigate, filter, tag, and operate across large file hierarchies quickly.<ref name="readme">[https://github.com/robkam/ytree README.md], github.com/robkam/ytree (Accessed: 2026-05-23)</ref><ref name="man">[https://github.com/robkam/ytree/blob/main/etc/ytree.1.md etc/ytree.1.md], github.com/robkam/ytree (Accessed: 2026-05-23)</ref> == Overview == Ytree is inspired by DOS XTree-style workflows and presents a multi-pane terminal interface with a directory tree, file window, and info/statistics pane. It supports multiple operating modes (Directory, File, Showall, Global, Archive, Split Screen, and Preview).<ref name="man" /> == Features == ==== Multi-volume logging ==== Ytree can log one or more directories or archives at startup and switch between logged volumes quickly.<ref name="man" /> ==== Split screen and preview ==== It includes split-screen panel mode (F8) and integrated file preview mode (F7).<ref name="man" /> ==== Archive-as-directory workflow ==== Supported archives (such as ZIP/TAR/GZ) can be browsed like virtual directories, with archive-aware operations where supported.<ref name="man" /> ==== Current release status ==== As of 2026-05-23, the latest published version marker is <code>v3.0.0-alpha</code> (tagged 2026-04-29), and the README describes the software as in active alpha development.<ref name="readme" /><ref>[https://github.com/robkam/ytree/tags Tags], github.com/robkam/ytree (Accessed: 2026-05-23)</ref> == References == <references /> a08d33b0692cff5a388f4f2cdd5135095c943241 4947 4945 2026-05-23T13:57:30Z Rob Kam 380 fix case wikitext text/x-wiki [[Category:Software]] [[Category:File managers]] {{SoftwareInfobox | image = [[File:Ytree v3.0.0-alpha F8 split view.png|frameless]] | caption = Ytree v3.0.0-alpha in F8 split view | title = Ytree | releasestatus = Alpha (maintained) | lastrelease = v3.0.0-alpha (tagged 2026-04-29) | languages = [[C]] | developers = Rob Kam; based on original Ytree by Werner Bregulla | website = https://github.com/robkam/ytree }} '''Ytree''' (<code>ytree</code>) is a keyboard-first [[TUI]] file manager for UNIX-like systems. It follows a “logger” model: it scans directory trees into memory so users can navigate, filter, tag, and operate across large file hierarchies quickly.<ref name="readme">[https://github.com/robkam/ytree README.md], github.com/robkam/ytree (Accessed: 2026-05-23)</ref><ref name="man">[https://github.com/robkam/ytree/blob/main/etc/ytree.1.md etc/ytree.1.md], github.com/robkam/ytree (Accessed: 2026-05-23)</ref> == Overview == Ytree is inspired by DOS XTree-style workflows and presents a multi-pane terminal interface with a directory tree, file window, and info/statistics pane. It supports multiple operating modes (Directory, File, Showall, Global, Archive, Split Screen, and Preview).<ref name="man" /> == Features == ==== Multi-volume logging ==== Ytree can log one or more directories or archives at startup and switch between logged volumes quickly.<ref name="man" /> ==== Split screen and preview ==== It includes split-screen panel mode (F8) and integrated file preview mode (F7).<ref name="man" /> ==== Archive-as-directory workflow ==== Supported archives (such as ZIP/TAR/GZ) can be browsed like virtual directories, with archive-aware operations where supported.<ref name="man" /> ==== Current release status ==== As of 2026-05-23, the latest published version marker is <code>v3.0.0-alpha</code> (tagged 2026-04-29), and the README describes the software as in active alpha development.<ref name="readme" /><ref>[https://github.com/robkam/ytree/tags Tags], github.com/robkam/ytree (Accessed: 2026-05-23)</ref> == References == <references /> 44b53b3c616bf4692ab0a46fe3521fdb5700bee8 6 1183 4948 2026-05-23T14:29:43Z Sparrow 362 Logo of the FFmpeg project. wikitext text/x-wiki == Summary == Logo of the FFmpeg project. a7c743813962e45ee61eef502931e2ddbb55718a 0 1184 4951 2026-05-23T15:05:55Z Sparrow 362 Create page for FFmpeg wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Ffmpeg_logo.png|thumb]] | caption =The FFmpeg logo. | title = FFmpeg | releasestatus = Maintained | lastrelease = 8.1.1, 2026-05-04 | languages = C, C++, Assembly, | developers = The FFmpeg Developers | website = [https://ffmpeg.org ffmpeg.org] }} '''FFmpeg''' is a free and open-source media suite used for converting, [[wikipedia:Transcoding|transcoding]], remuxing and editing video, audio, and other multimedia formats.<ref>{{Cite|url=https://ffmpeg.org/about.html|title=About FFmpeg · ffmpeg.org|author=FFmpeg Developers|accessdate=2026-05-23}}</ref> Because of its ability to convert from the most obscure formats, it has solidified itself in both propitiatory and open-source projects, notably [[Handbrake]] and [[Kdenlive]], and has also been used in streaming sites such as YouTube. == References == <references /> eee71eb17525b82cbafe7bc8bbb7c800078d020c 4952 4951 2026-05-23T15:09:53Z Sparrow 362 Set stub tag wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{Stub}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Ffmpeg_logo.png|thumb]] | caption =The FFmpeg logo. | title = FFmpeg | releasestatus = Maintained | lastrelease = 8.1.1, 2026-05-04 | languages = C, C++, Assembly, | developers = The FFmpeg Developers | website = [https://ffmpeg.org ffmpeg.org] }} '''FFmpeg''' is a free and open-source media suite used for converting, [[wikipedia:Transcoding|transcoding]], remuxing and editing video, audio, and other multimedia formats.<ref>{{Cite|url=https://ffmpeg.org/about.html|title=About FFmpeg · ffmpeg.org|author=FFmpeg Developers|accessdate=2026-05-23}}</ref> Because of its ability to convert from the most obscure formats, it has solidified itself in both propitiatory and open-source projects, notably [[Handbrake]] and [[Kdenlive]], and has also been used in streaming sites such as YouTube. == References == <references /> 908a70330cbec314d7c529e041bb3baa29bfb05b 0 1176 4953 4915 2026-05-23T15:25:26Z Sparrow 362 Fix DistrobutionInfobox from not rendering and add stub tag wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Chimera Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[apk-tools]] | defaultdesktops = GNOME, Terminal User Interface | usagetype = Desktop | architectures = x86_64, ppc, ppc64, ppc64le, aarch64, riscv64 | website = [https://chimera-linux.org/ chimera-linux.org] }} '''Chimera Linux''' is an independent [[Linux Distributions|Linux distribution]] characterized by using novel tooling, approaches, and userland.<ref>https://chimera-linux.org/</ref> <references /> 9f3de22ebe81cb9113044f110285c03f45c00351 4964 4953 2026-05-23T16:27:40Z Matthias von Schwarzwald 361 Linking wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Chimera Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[apk-tools]] | defaultdesktops = [[GNOME]], [[Terminal User Interface]] | usagetype = Desktop | architectures = x86_64, ppc, ppc64, ppc64le, aarch64, riscv64 | website = [https://chimera-linux.org/ chimera-linux.org] }} '''Chimera Linux''' is an independent [[Linux Distributions|Linux distribution]] characterized by using novel tooling, approaches, and userland.<ref>https://chimera-linux.org/</ref> <references /> 409ea3508bf1ff94bf798963c3673b077a29c036 6 1185 4954 2026-05-23T15:27:30Z Matthias von Schwarzwald 361 wikitext text/x-wiki == Licensing == {{CC-BY-4.0}} bfaf7ac650a059f96b01d8c29482fd37825aaefc 3001 1164 4957 4840 2026-05-23T15:47:59Z Uniolo 345 /* What distros do we feel comfortable recommending? */ Reply wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) :Addressed the criticisms to reduce bias. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:27, 23 May 2026 (UTC) :I think we should have a new discussion wrt. if we should recommend distros, and how we should do so. :There is value in being able to recommend distros, especially in an environment where chatbots and LLMs have outdated information and new users don't have up-to-date, reliable information about what distros are currently the most reliable and beginner-friendly, as said info would be mostly discussed on Discord, Reddit, etc., and not in an authoritative format. :As "thatonecoder" on Discord stated: :"Precisely; decision paralysis is an issue, and we cannot dismiss it simply on the grounds of remaining unbiased." [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:46, 23 May 2026 (UTC) == What distros do we feel comfortable recommending? == I agree that it's not very unbiased of us to recommend specific distros when Many Distros Exist, however I feel as a resource we need to be approachable to the community and **helpful** to new users who may not know about all the issues that plague distros that aren't often recommended anymore (such as Pop!_OS and Manjaro). It would be good if we got a list of modern, commonly recommended distros that we know are reliable that we feel comfortable recommending to new Linux users. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:28, 23 May 2026 (UTC) :Debian was my first distro and it is truly a distro for all seasons, the caveats with debian is that its coupled to systemd unless you manually migrate it to devuan but otherwise pretty solid considering it doesn't spoonfeed too much [[User:GentooLaws|GentooLaws]] ([[User talk:GentooLaws|talk]]) 06:33, 23 May 2026 (UTC) :I feel like [https://www.linuxliteos.com/ linux lite] is a great beginner distro, I learned about it a few months ago when helping someone out with it. Ultramarine/Fedora have always been my go to recommendations. Bazzite is interesting for new users as well due to the gaming setup out of the box since many think "oh you need to do X,Y,Z, and more" just to get games to work on Linux from what I have seen irl. [[User:Scottc96|Scottc96]] ([[User talk:Scottc96|talk]]) 06:41, 23 May 2026 (UTC) :Every distro has its own problems. It is like better to give a few distros that are well-established and possibly have a caveats page somewhere. Here are some notable examples: :- Mint: caveats with X11, specifically it's incapability to do HDR and weirdness with multi-monitor (probably need more expanding, but something like Xinerama is not perfect iirc and still would be wacky with many different refresh rate monitors). Probably need an accompanied X11 and Wayland difference page regarding this. :- Fedora: caveats with drivers and codecs, which are only using free-licensed ones by default and needing to go through installation via RPMFusion or Terra to have them be installed properly. :- Ubuntu: caveats with using snap store as the default store. This is problematic with some applications, notably Steam, not properly working as intended. The fix to this is to use the steam's deb repository [[User:Ping|Ping]] ([[User talk:Ping|talk]]) 06:50, 23 May 2026 (UTC) ::I strongly agree with @[[User:Ping|Ping]] that we should recommend multiple, [[Debian]] might be good if you want to never ever worry about updates breaking your system except once every 2 years, but might not work on some hardware (for instance, Debian 12 did not boot on my old laptop (though Debian 13 did)). ::[[Fedora]] is very good and is now the go to for many people, but as ping mentioned, there are some licensing issues preventing them from including certain things. ::[[Bazzite]] might be good if you care about gaming (at the cost of many general instructions not being applicable due to its immutable model), and likewise, [[Fedora Atomic]] might be good if you are using a computer for general use and want to make sure nothing breaks (at the cost of some general instructions not working or require workarounds). ::We should definitely discuss any changes to the recommendations on the talk page due to the potential for bias, I added a comment to the page (though it may have been deleted when the previous recommendations were removed). [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 15:47, 23 May 2026 (UTC) 1046a23273c64de0d5371d73270c1bca0ca24a5b 2 1186 4960 2026-05-23T16:01:31Z Rob Kam 380 Created page with "Please star the [https://github.com/robkam/ytree Ytree: a File Manager for Unix-like Systems] repository." wikitext text/x-wiki Please star the [https://github.com/robkam/ytree Ytree: a File Manager for Unix-like Systems] repository. f8d14c492e89fc756de62eb5d59a6f7b00219752 0 1187 4961 2026-05-23T16:15:11Z Matthias von Schwarzwald 361 Create page "Godot" for Godot Engine wikitext text/x-wiki {{Stub}}{{SoftwareInfobox|image=[[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]]|caption=|title=Godot|releasestatus=Maintained|lastrelease=4.6.3-stable, 2026-05-20|firstrelease=1.0, 2014-12-15|languages=[[C++]]|developers=Juan Linietsky, Ariel Manzur, and Contributors|website=[https://github.com/godotengine/godot github.com/godotengine/godot], [https://godotengine.org godotengine.org]}}Godot is a general-purpose FOSS game engine. It uses a node- and scene-based editor and supports C++, C#, and its original scripting language, [[GDScript]], plus other languages through community tools.<ref>https://godotengine.org/features/#script</ref> [[Category:Software]] [[Category:Game Engines]] 1a7cc83060356862c84387e52b5e932adca38ebd 4965 4961 2026-05-23T17:01:23Z Matthias von Schwarzwald 361 Add paragraph about name wikitext text/x-wiki {{Stub}}{{SoftwareInfobox|image=[[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]]|caption=|title=Godot|releasestatus=Maintained|lastrelease=4.6.3-stable, 2026-05-20|firstrelease=1.0, 2014-12-15|languages=[[C++]]|developers=Juan Linietsky, Ariel Manzur, and Contributors|website=[https://github.com/godotengine/godot github.com/godotengine/godot], [https://godotengine.org godotengine.org]}}Godot is a general-purpose FOSS game engine. It uses a node- and scene-based editor and supports C++, C#, and its original scripting language, [[GDScript]], plus other languages through community tools.<ref>https://godotengine.org/features/#script</ref> The name comes from the classic play ''[[wikipedia:Waiting_for_Godot|Waiting for Godot]]'' and is pronounced as therein. This results in the pronunciation varying between languages, which the project officially describes as "beautiful".<ref>https://godotengine.org/press/</ref> [[Category:Software]] [[Category:Game Engines]] dace03a60ae67239d050ad59fa2b01a0c11180cb 0 1188 4963 2026-05-23T16:26:55Z Matthias von Schwarzwald 361 Create redirect page: Terminal User Interface -> TUI wikitext text/x-wiki #REDIRECT [[TUI]] 743691ec19de850de519ba3e93b81899ca0dfb15 6 1189 4967 2026-05-23T17:34:03Z Habaja1 377 A Linux-mint instalation running cinnamon. wikitext text/x-wiki == Summary == A Linux-mint instalation running cinnamon. == Licensing == {{Unknown_copyright}} e8c859452451e3b88c2a9a25cc8384998e92972a 4968 4967 2026-05-23T17:35:40Z Habaja1 377 Habaja1 uploaded a new version of [[File:Linux-Mint-Cinnamon.png]] wikitext text/x-wiki == Summary == A Linux-mint instalation running cinnamon. == Licensing == {{Unknown_copyright}} e8c859452451e3b88c2a9a25cc8384998e92972a 0 628 4969 4481 2026-05-23T17:36:41Z Habaja1 377 added an image wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entrypoint into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history. There is also a Debian-based version of Linux Mint, called LMDE (Linux Mint Debian Edition), that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: Open-source * Update Method: Release cycle * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) [[File:Linux-Mint-Cinnamon.png|thumb|A Linux Mint installation with the Cinnamon desktop]] == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced Linux Mint Debian Edition (LMDE), which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. In 2016, the Linux Mint website and forums were hacked and the installation images were infected with malware.<ref>{{Cite|url=https://www.pcworld.com/article/419713/hackers-planted-a-backdoor-inside-a-compromised-version-of-linux-mint.html|title=Linux Mint website hacked, ISO downloads replaced with backdoored operating system|author=Nick Mediati, PCWorld|year=2016|accessdate=2025.08.31}}</ref> The latest release, Linux Mint 22.2 "Zara", was launched on the 4th of September, 2025 and is supported until 2029.<ref>https://linuxmint.com/rel_zara.php, Linux Mint, 2006-08-09 (Accessed: 2025-09-09)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called Linux Mint Debian Edition (LMDE), which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own repositories, which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repos also contain software made by the Linux Mint team such as Cinnamon and its related applications.<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> == References == 05d7b74d73126589ebd6c9db9f9ffdf7375c4632 0 1190 4970 2026-05-23T17:42:05Z Uniolo 345 Create GnuPG, add information about what it is, and sidebar. wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[File:GPG keys generation.png|thumb|Example of PGP key generation]] '''GnuPG''' (also known as [[GPG]]) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many Linux distributions and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. e896f7955760a9d7513907e2961ad64ad4cc56ab 4973 4970 2026-05-23T17:47:24Z Uniolo 345 Added information on what GPG does wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[File:GPG keys generation.png|thumb|Example of PGP key generation]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many Linux distributions and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or message to be encrypted and decrypted with the same password password. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. 583bdde33bef3c8ae99e8bf00779e0f5bddfc8e8 4975 4973 2026-05-23T17:50:55Z Uniolo 345 Added information on signing and mentioned its use in Git wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[File:GPG keys generation.png|thumb|Example of PGP key generation]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many Linux distributions and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or message to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a senders public key, the legitimacy of a message. GnuPG is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. <references /> 216f341bbb5d8642344bb06743bff80b5a8ba462 4976 4975 2026-05-23T17:51:47Z Uniolo 345 Updated caption on image to include that GPG is being used to create the PGP key wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many Linux distributions and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or message to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a senders public key, the legitimacy of a message. GnuPG is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. <references /> 6343caf582da0ac04dfd9d61cc7a70b500d13706 4978 4976 2026-05-23T17:56:05Z Uniolo 345 Added to software category wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many Linux distributions and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or message to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a senders public key, the legitimacy of a message. GnuPG is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. <references /> [[Category:Software]] 432bcdb96a9b642cf4180c011fc1b7519551dcba 4980 4978 2026-05-23T18:04:35Z Matthias von Schwarzwald 361 Typos and a link wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many [[Linux Distributions|Linux distributions]] and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or messages to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a sender's public key, the legitimacy of a message. GnuPG is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. <references /> [[Category:Software]] 5329fec961b91c9964749d696e405ca6d7526410 4981 4980 2026-05-23T18:07:44Z Uniolo 345 Added note about using Age instead, I am about to make the page for Age dont worry. wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many [[Linux Distributions|Linux distributions]] and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or messages to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a sender's public key, the legitimacy of a message. GnuPG is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. Due to GnuPG supported many old and deprecated algorithms and many UX mistakes, many users advise moving towards the more modern [[Age]] for encryption<ref>{{Cite|url=https://sumguy.com/age-vs-gpg-modern-encryption/|title=age vs GPG: Modern File Encryption That Doesn't Make You Cry|author=SumGuy|year=May 26, 2026|accessdate=2026-05-23}}</ref>. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] or [[Signify]] is needed. <references /> [[Category:Software]] 5407fcdae516d71b6aea9eb56353d6ed44c8a30b 4984 4981 2026-05-23T18:16:13Z Uniolo 345 Removed signify from GPG page since many users migrating wont be on OpenBSD where Signify is prefered over Minisign. wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many [[Linux Distributions|Linux distributions]] and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or messages to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a sender's public key, the legitimacy of a message. GnuPG is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. Due to GnuPG supported many old and deprecated algorithms and many UX mistakes, many users advise moving towards the more modern [[Age]] for encryption<ref>{{Cite|url=https://sumguy.com/age-vs-gpg-modern-encryption/|title=age vs GPG: Modern File Encryption That Doesn't Make You Cry|author=SumGuy|year=May 26, 2026|accessdate=2026-05-23}}</ref>. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] is needed. <references /> [[Category:Software]] f6cf811a76e75e606968c33a025518f1d8ccc47a 4989 4984 2026-05-23T19:54:49Z Uniolo 345 Fixed typo (supported -> supporting) wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many [[Linux Distributions|Linux distributions]] and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or messages to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a sender's public key, the legitimacy of a message. GnuPG is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. Due to GnuPG supporting many old and deprecated algorithms and many UX mistakes, many users advise moving towards the more modern [[Age]] for encryption<ref>{{Cite|url=https://sumguy.com/age-vs-gpg-modern-encryption/|title=age vs GPG: Modern File Encryption That Doesn't Make You Cry|author=SumGuy|year=May 26, 2026|accessdate=2026-05-23}}</ref>. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] is needed. <references /> [[Category:Software]] 783f059e77c6a5be5da3d9669a384ba47e99a992 0 790 4971 4123 2026-05-23T17:43:00Z Matthias von Schwarzwald 361 Typos wikitext text/x-wiki {{Needs_Citations}} {{DistributionInfobox | title = Red Star OS | image = [[File:Red Star OS Logo 2020.svg|190px]] | caption = Red Star OS logo | releasestatus = Maintained | releasemodel = Unknown | packagemanager = [[rpm]] | defaultdesktops = [[KDE Plasma]], [[GNOME]] | usagetype = Desktop | architectures = [[IA-32]], [[x86-64]], [[ARM]] | website = None }} '''Red Star OS ('''Korean: 붉은별''')''' is a [[Red Hat Enterprise Linux|Red Hat Linux]]-based [[Linux Distributions|distribution]] developed in the Democratic People's Republic of Korea (DPRK), made as a replacement for Windows in North Korea. It was first developed in 1998 by the Korea Computer Center. == Browser == '''Red Star OS''' relies on a heavily modified version of [[Firefox]] called ''[[Naenara]]'', which means "Our Country" in Korean. 9d50444f753f25b43a73e3bd96b39de30018ffd2 0 1191 4972 2026-05-23T17:43:23Z Uniolo 345 Create page as redirect to GnuPG wikitext text/x-wiki #REDIRECT [[Gnupg]] ac4b6314f82928a0a3061203e538450b71c7dc94 0 233 4974 3676 2026-05-23T17:50:49Z Matthias von Schwarzwald 361 Date formatting wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware_logo_from_the_official_Slackware_site.svg{{!}}class=skin-invert|frameless|upright=0.8|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[Category:Linux Distributions]] [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17, 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>[http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf A history of Slackware development], Eric Hameleers, 2009-10-09 (Accessed: 2025-08-09)</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with KDE * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3, 2022 with the release of Slackware 15.0. == References == 31c88745acb1adb6387ebf427b0f97eef823bad6 0 656 4977 2936 2026-05-23T17:53:51Z Matthias von Schwarzwald 361 Typo and link wikitext text/x-wiki {{DistributionInfobox |title=Batocera |image=[[file:Batocera-logo-art.png|frameless]] |caption=Batocera Logo |releasestatus=Maintained |releasemodel=Rolling Release |packagemanager=[[pacman]] |defaultdesktops=No Desktop |usagetype=placeholder |architectures=x86_64, Rpi4, Rpi5 |website=[https://batocera.org/ batocera.org] }} Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pis and other micro computers. Batocera offers emulation cores for retro consoles and retro home computers. == References == cf6b15e8c6a54d04ce6c1c7ff81d5c53255948a1 0 1143 4979 4939 2026-05-23T17:56:42Z Uniolo 345 Added to "software" category wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:Neovim-mark.svg|thumb]] |caption=NeoVim |title=NeoVim |releasestatus=Maintained |lastrelease=0.12.2, Apr 22, 2026 |firstrelease=0.15, Aug 23, 2016 |languages=[[C]], [[Lua]], [[Vim Script]] |developers=Thiago de Arruda |website=[https://neovim.io/ neovim.io] }} [[File:Nevom-Splash.png|thumb|The Neovim 0.12.2 splash screen.]] '''Neovim''' (also known as '''nvim''') is a configurable terminal text editor for Linux, Windows, and macOS. It is configured in [[Lua]]. Neovim is based on [[Vim]]<ref>{{Cite|url=https://github.com/neovim/neovim/commit/9f13983de280c53971a8997ead0d6e9d4e3d3e42|title=Commit 9f13983, "vim-patch:7.4.2185"|author=lonerover|year=2017-03-11|accessdate=2026-05-23}}</ref>. Neovim is fully compatible with Vim's editing modal and [[Vim Script]]<ref>[https://neovim.io/ Neovim website] (accessed 2026-05-22)</ref>, and part of Neovim is written in [[Vim Script]]<ref>{{Cite|url=https://github.com/neovim/neovim|title=Neovim GIthub|author=[https://github.com/orgs/neovim/people Neovim Contributors]|year=2026-05-23|accessdate=2026-05-23}}</ref>. Like [[Vim]], Neovim can also be considered [[wikipedia:Careware|Charityware]] due to encouraging users to donate to [https://www.kuwasha.net/ Kuwasha]. <references /> [[Category:Software]] 17ed213128f59557f9e1042377f7d637019f7ca9 0 1192 4982 2026-05-23T18:08:31Z Uniolo 345 Create page as work in progress wikitext text/x-wiki {{Work In Progress}} 4de77f3d748c7446cfc5e35b12c95d4246eb7f8f 4983 4982 2026-05-23T18:13:45Z Uniolo 345 Added content to page, including the implementation and simalar signing tools. wikitext text/x-wiki {{Stub}} '''Age''' [https://age-encryption.org/v1 is a standard] for encrypting files and data similar to PGP but it only supports encryption and decryption and has multiple implementations in common use, it has a [[Go]] implementation also called [https://github.com/FiloSottile/age age] and and a [[Rust]] implementation called [https://github.com/age-rs/age-rs age-rs]. Age is often used as a [[Gnupg|GnuPG]] replacement. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] or [[Signify]] is needed to migrate away from [[Gnupg|GnuPG]]. d786ec152d202229f172c563f4dbbe84a89114cb 4985 4983 2026-05-23T18:19:51Z Uniolo 345 Added note about not having a keyring unlike GnuPG to the paragraph comparing them. wikitext text/x-wiki {{Stub}} '''Age''' [https://age-encryption.org/v1 is a standard] for encrypting files and data similar to PGP but it only supports encryption and decryption and has multiple implementations in common use, it has a [[Go]] implementation also called [https://github.com/FiloSottile/age age] and and a [[Rust]] implementation called [https://github.com/age-rs/age-rs age-rs]. Age is often used as a [[Gnupg|GnuPG]] replacement. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] is needed to fully migrate away from [[Gnupg|GnuPG]]. Age is significantly less complex then [[Gnupg|GnuPG]] and does not have a keyring, instead storing keys as files. 6d8bd9dc9b0919cc8f833ed0008d3f702ca45134 5001 4985 2026-05-23T23:14:10Z Uniolo 345 Added image of the help page for the go implementation, while this is for the protocol in general, the go implementation help page does show what age does. wikitext text/x-wiki {{Stub}} [[File:Age-help.png|thumb|The "help" screen for the go implementation of age, version 1.3.1]] '''Age''' [https://age-encryption.org/v1 is a standard] for encrypting files and data similar to PGP but it only supports encryption and decryption and has multiple implementations in common use, it has a [[Go]] implementation also called [https://github.com/FiloSottile/age age] and and a [[Rust]] implementation called [https://github.com/age-rs/age-rs age-rs]. Age is often used as a [[Gnupg|GnuPG]] replacement. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] is needed to fully migrate away from [[Gnupg|GnuPG]]. Age is significantly less complex then [[Gnupg|GnuPG]] and does not have a keyring, instead storing keys as files. f6a30529f14c04e7e9a7f8479f035f061e5ab2a1 5008 5001 2026-05-24T00:48:57Z Matthias von Schwarzwald 361 Typos and cleanup, particularly external links wikitext text/x-wiki {{Stub}} [[File:Age-help.png|thumb|The "help" screen for the go implementation of age, version 1.3.1]] '''Age''' [https://github.com/C2SP/C2SP/blob/main/age.md is a standard] for encrypting files and data similar to PGP but only supporting encryption and decryption. It has multiple implementations in common use, including a [[Go]] implementation also called [https://github.com/FiloSottile/age age] and a [[Rust]] implementation called [https://github.com/str4d/rage rage]. Age is often used as a [[Gnupg|GnuPG]] replacement. It should be noted that age does not support signing; another tool like [[Minisign]] is needed to fully migrate away from [[Gnupg|GnuPG]]. Age is significantly less complex then [[Gnupg|GnuPG]] and does not have a keyring, instead storing keys as files. 50d5f2ce2a3f312081e3b8a13608faf54e9fef88 5016 5008 2026-05-24T01:19:47Z Matthias von Schwarzwald 361 Add paragraph about name wikitext text/x-wiki {{Stub}} [[File:Age-help.png|thumb|The "help" screen for the go implementation of age, version 1.3.1]] '''Age''' [https://github.com/C2SP/C2SP/blob/main/age.md is a standard] for encrypting files and data similar to PGP but only supporting encryption and decryption. It has multiple implementations in common use, including a [[Go]] implementation also called [https://github.com/FiloSottile/age age] and a [[Rust]] implementation called [https://github.com/str4d/rage rage]. Age is often used as a [[Gnupg|GnuPG]] replacement. It should be noted that age does not support signing; another tool like [[Minisign]] is needed to fully migrate away from [[Gnupg|GnuPG]]. Age is significantly less complex then [[Gnupg|GnuPG]] and does not have a keyring, instead storing keys as files. The name is pronounced with a hard ''g'' ([[wikipedia:International_Phonetic_Alphabet|IPA]] [g]), rather than the soft ''g'' (IPA [j]) of the English word ''age'', and is uncapitalized.<ref>https://github.com/FiloSottile/age</ref> 291d630a995caee6475413132c4827aff1a0853e 5018 5016 2026-05-24T03:17:19Z Uniolo 345 Put citation in correct format wikitext text/x-wiki {{Stub}} [[File:Age-help.png|thumb|The "help" screen for the go implementation of age, version 1.3.1]] '''Age''' [https://github.com/C2SP/C2SP/blob/main/age.md is a standard] for encrypting files and data similar to PGP but only supporting encryption and decryption. It has multiple implementations in common use, including a [[Go]] implementation also called [https://github.com/FiloSottile/age age] and a [[Rust]] implementation called [https://github.com/str4d/rage rage]. Age is often used as a [[Gnupg|GnuPG]] replacement. It should be noted that age does not support signing; another tool like [[Minisign]] is needed to fully migrate away from [[Gnupg|GnuPG]]. Age is significantly less complex then [[Gnupg|GnuPG]] and does not have a keyring, instead storing keys as files. According to the author, it is pronounced with a hard ''g'' ([[wikipedia:International_Phonetic_Alphabet|IPA]] [g]), rather than the soft ''g'' (IPA [j]) of the English word ''age'', and is uncapitalized<ref>[https://github.com/FiloSottile/age GitHub repo for the go implementation], age contributors, last updated March 2026 (accessed 2026-05-23)</ref>. e1b0c296e4e452f9436bb6c72a1bf5391d1fe7c9 1 4 4986 2668 2026-05-23T18:31:40Z Rob Kam 380 /* Front page colour contrast and readability */ new section wikitext text/x-wiki == Suggested Pages == Add page topics to discuss the inclusion of within this post. To start off, Here are some personal suggestions along with community provided suggestions; '''What is Linux anyways?''' -TLDR of what Linux is -Major differences between Linux and other OS -[[Key Terms]] '''Guide to Getting Started''' -Setting Expectations -Guide to Picking a distro -Pros and Cons of individual distros (with quirks) -Pros and Cons between package formats -Safely downloading ISO and setting up install media -Guide to installing Linux (with video hyperlinks) -Quick start guide to individual distros (with relevant 1st party wiki links) -Migrating user data between windows or between distros '''Maintaining your system''' -Physical maintenance for any system (fans and such) -System Update maintenance -Software update maintenance -Security maintenance '''Online and Linux Safety and Security''' -Local password and account security (screenshoting safely included) -Basic online safety (opsec and privacy) -Downloading and things safely (from github and package managers as well) -Safely managing local data -Basic Threat Modeling -Securing your system beyond defaults (Hardened browsers, UAC, AppArmor, SELinux, Flatseal, Secureboot, Etc.) -Securing your network -Staying up to date on current security news -Local Regulations '''Cool sites that may be relevant for users to check out''' -[https://alternativeto.net/ alternativeto.net] -[https://awesome-privacy.xyz/ awesome-privacy.xyz] -[https://christitus.com/windows-tool/ chris titus windows tool] ''Feel Free and Encouraged to contribute more ideas!'' [[User:MediaBoomer|-MB]] ([[User talk:MediaBoomer|talk]]) 23:18, 3 June 2024 (UTC) :Maybe most important commands to know "primer"? See for examples: :https://discord.com/channels/1172245377395728464/1172245377395728467/1237386711055601714 :https://discord.com/channels/1172245377395728464/1172245377395728467/1237388162440105984 [[User:Kaizen|Kaizen]] ([[User talk:Kaizen|talk]]) 13:50, 4 June 2024 (UTC) == organization idea == > I think the Distribution list should contain dropdowns for stuff like "Arch-based Distributions", "Debian-based Distributions" for better organization - Ryna from ATL [[User:Electron271|Electron271]] ([[User talk:Electron271|talk]]) 23:38, 3 June 2024 (UTC) :I like the outline! I agree with Electron about organization and it applies to all of the categories - before writing these, we should have a general idea of ''all'' our subcategories [[User:Asiliria|Asiliria]] ([[User talk:Asiliria|talk]]) 23:40, 3 June 2024 (UTC) == I believe we should add a languages catagorie == see above [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 10:40, 2 July 2025 (UTC) :The wiki itself is English-only though? [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 05:12, 3 July 2025 (UTC) ::I believe its for programming languages, I can add a category but i wont add a button for now as the homepage structure is due to change. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 07:46, 3 July 2025 (UTC) :::yeh i meant programming languages lol [[User:Hog|Hog]] ([[User talk:Hog|talk]]) 08:13, 3 July 2025 (UTC) == Front page colour contrast and readability == The current front page colour scheme makes parts of the page difficult to read. An accessibility audit of https://foss.wiki/ reported 31 critical issues, including 26 elements failing WCAG 2.2 AA foreground/background contrast requirements. The practical issue is readability rather than legal risk. The front page colours should be adjusted so that text and links have sufficient contrast against their backgrounds. [[User:Rob Kam|Rob Kam]] ([[User talk:Rob Kam|talk]]) 18:31, 23 May 2026 (UTC) e574aa83173406f9614c6191f135e46b434b69e7 0 1193 4987 2026-05-23T18:32:53Z Uniolo 345 Create minisign page with basic information and sidebar. There is not too much to say. wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |title=Minisign |releasestatus=Maintained |lastrelease=0.12.2, May 2, 2026 |firstrelease=0.3, Jun 11, 2015 |languages=[[C]], [[Zig]] |developers=[https://github.com/jedisct1 Frank Denis] |website=[https://jedisct1.github.io/minisign/ jedisct1.github.io/minisign] }} '''Minisign''' is designed to be a simple tool to sign files and verify signatures. Although originally made in [[C]], the [[Zig]] version ([https://github.com/jedisct1/zig-minisign zig-minisign], sometimes refereed to as <code>minizign</code>) is now the preferred version. [[Category:Software]] bcddaa0b35ca9199c31bcc5f19113045261b5049 4988 4987 2026-05-23T18:34:56Z Uniolo 345 Added note about being used to replace GnuPG and Signify wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |title=Minisign |releasestatus=Maintained |lastrelease=0.12.2, May 2, 2026 |firstrelease=0.3, Jun 11, 2015 |languages=[[C]], [[Zig]] |developers=[https://github.com/jedisct1 Frank Denis] |website=[https://jedisct1.github.io/minisign/ jedisct1.github.io/minisign] }} '''Minisign''' is designed to be a simple tool to sign files and verify signatures. Although originally made in [[C]], the [[Zig]] version ([https://github.com/jedisct1/zig-minisign zig-minisign], sometimes refereed to as <code>minizign</code>) is now the preferred version. Minisign, along with [[Age]], is often used by people wanting to replace [[Gnupg|GnuPG]] who may want to do so for various reasons. [https://man.openbsd.org/signify Signify] is preferred over Minisign on [[OpenBSD]] systems due to its integration with its ecosystem. [[Category:Software]] 7b03bbf96873980b6fbdf45be172a4d52e83700e 2 192 4990 4576 2026-05-23T21:34:34Z Atmois 13 test wikitext text/x-wiki Local tech nerd, who listens to ''a lot'' of music. '''foss.wiki'''<nowiki/>'s director, come join us and [[FW:Contributing|contribute]]! https://atmois.com ''test'' efc26b6baf183cead7f46a954f2b2c8739c666d5 0 827 4991 3473 2026-05-23T22:05:22Z MarkH 357 fix some broken wikilinks wikitext text/x-wiki '''Wayland''' is a communication protocol that specifies the communication between a display server and its clients, as well as a [[C (programming language)|C]] library implementation of that protocol. A display server using the Wayland protocol is called a ''[[Wayland#Wayland compositors|Wayland compositor]]'', because it additionally performs the task of a compositing window manager. Wayland is developed by a group of volunteers initially led by Kristian Høgsberg as a free and open-source community-driven project with the aim of replacing the X Window System with a secure and simpler windowing system for [[Linux]] and other [[Unix]]-like operating systems. The project's source code is published under the terms of the [[MIT License]], a permissive free software license. The Wayland project also develops an implementation of a Wayland compositor called ''[[Wayland#Weston|Weston]]''. == Overview == [[File:Wayland_display_server_protocol.svg|right|thumb]] The Wayland Display Server project was started by [[Red Hat]] developer Kristian Høgsberg in 2008. Beginning around 2010, Linux desktop graphics have moved from having "a pile of rendering interfaces... all talking to the X server, which is at the center of the universe" towards putting the Linux kernel and its components (i.e. Direct Rendering Infrastructure (DRI), Direct Rendering Manager (DRM)) "in the middle", with "window systems like X and Wayland ... off in the corner". This will be "a much-simplified graphics system offering more flexibility and better performance". Høgsberg could have added an [[Xdmx|extension to X]] as many recent projects have done, but preferred to "[push] X out of the hotpath between clients and the hardware" for reasons explained in the project's FAQ. Wayland consists of a protocol and a reference implementation named [[Wayland#Weston|Weston]]. The project is also developing versions of [[GTK]] and [[Qt (software)|Qt]] that render to Wayland instead of to X. Most applications are expected to gain support for Wayland through one of these libraries without modification to the application. Initial versions of Wayland have not provided network transparency, though Høgsberg noted in 2010 that network transparency is possible. It was attempted as a Google Summer of Code project in 2011, but was not successful. Adam Jackson has envisioned providing remote access to a Wayland application by either "pixel-scraping" (like [[Virtual Network Computing|VNC]]) or getting it to send a "rendering command stream" across the network (as in [[Remote Desktop Protocol|RDP]], [[SPICE (protocol)|SPICE]] or [[X11]]). As of early 2013, Høgsberg was experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor. In August 2017, GNOME saw the first such pixel-scraping VNC server implementation under Wayland. In modern Wayland compositors, network transparency is handled in an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] that implements the RemoteDesktop portal. Many Wayland compositors also include an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] for common tasks such as a native file picker for native applications and sandboxes such as [[Flatpak]] ([https://github.com/flatpak/xdg-desktop-portal-gtk xdg-desktop-portal-gtk] is commonly used as a fallback filepicker), screen recording, network transparency, screenshots, color picking, and other tasks that could be seen as needing user intervention and being security risks otherwise. Note that xdg-desktop-portal is not Flatpak or Wayland-specific, and can be used with alternative packaging systems and windowing systems. == Wayland compositors == [[File:Window_(windowing_system).svg|right|thumb|Typical elements of a [[Window (computing)|window]]. The Wayland protocol does not specify what software is responsible for rendering the [[window decoration]].{{r|Graesslin 2013 decorations}}]] [[File:KDE_Plasma_5.24_on_Arch_Linux_screenshot.png|thumb|Plasma 5.24.0 (February 2022) on Wayland ({{code|kwin_wayland}} compositor) under [[Arch Linux]]]] [[Display server|Display servers]] that implement the Wayland display server protocol are also called ''Wayland compositors'' because they additionally perform the task of a [[compositing window manager]]. A library called '''wlroots''' is a modular Wayland implementation that functions as a base for several compositors A list of compositors can be found [[Wayland Compositors|here]]. === Weston === [[Weston (software)|Weston]] is a Wayland compositor previously developed as the [[reference implementation]] of the protocol by the Wayland project. It is written in [[C (programming language)|C]] and released under the [[MIT License]]. Weston officially supports only [[Linux]] due to dependencies on kernel-specific features such as kernel mode-setting (KMS), the Graphics Execution Manager (GEM), and [[udev]]. On Linux, it handles input via [[evdev]] and buffer management via Generic Buffer Management (GBM). A prototype port for [[FreeBSD]] was announced in 2013. The compositor supports High-bandwidth Digital Content Protection (HDCP) and uses GEM to share buffers between applications and the compositor. It features a plug-in architecture with "shells" that provide elements like docks and panels. Applications are responsible for rendering their own window decorations. Weston supports rendering via [[OpenGL ES]] or the [[pixman]] library for software rendering. The full OpenGL stack is avoided to prevent pulling in [[GLX]] and other [[X11|X Window System]] dependencies. A remote desktop interface for Weston was proposed in 2013 by a developer from [[RealVNC]]. ==== Maynard ==== [[File:Maynard_desktop.png|thumb|Maynard (in January 2017)]] '''''Maynard''''' is a [[graphical shell]] and has been written as a plug-in for Weston, just as the [[GNOME Shell]] has been written as a plug-in to [[Mutter (software)|Mutter]]. The [[Raspberry Pi Holdings|Raspberry Pi]] in collaboration with [[Collabora]] released Maynard. === libinput === [[File:Libinput_for_Wayland_compositors.svg|thumb|libinput was created to consolidate the input stack across multiple Wayland compositors.]] The Weston code for handling input devices (keyboards, pointers, touch screens, etc.) was split into its own separate library, called ''libinput'', for which support was first merged in Weston 1.5. Libinput handles input devices for multiple Wayland compositors and also provides a generic [[X.Org Server]] input driver. It aims to provide one implementation for multiple Wayland compositors with a common way to handle input events while minimizing the amount of custom input code compositors need to include. libinput provides device detection (via [[udev]]), device handling, input device event processing and abstraction. Version 1.0 of libinput followed version 0.21, and included support for tablets, button sets and touchpad gestures. This version will maintain stable API/ABI. As GNOME/GTK and [[KDE Frameworks 5]] have mainlined the required changes, Fedora 22 will replace X.Org's evdev and Synaptics drivers with libinput. With version 1.16, the [[X.Org Server]] obtained support for the libinput library in form of a wrapper called [[Mono]]. === Wayland Security Module === Wayland Security Module is a proposition that resembles the [[Linux Security Module]] interface found in the [[Linux kernel]]. Some applications (especially the ones related to [[accessibility]]) require privileged capabilities that should work across different Wayland compositors. Currently, applications under Wayland are generally unable to perform any sensitive tasks such as taking screenshots or injecting input events without going through [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] or obtaining privileged access to the system. Wayland Security Module is a way to delegate security decisions within the compositor to a centralized security decision engine. == Adoption == The Wayland protocol is designed to be simple so that additional protocols and interfaces need to be defined and implemented to achieve a holistic windowing system. While many graphical toolkits already fully support Wayland, the developers of the [[Graphical shell|graphical shells]] are cooperating with the Wayland developers to create the necessary additional interfaces. === Desktop Linux distributions === Most major Linux distributions default to using Wayland. Some notable examples are: * [[Debian]] ships Wayland as the default session for GNOME since version [[Debian 10|10 (Buster)]], released 6 July 2019. * [[Fedora]] starting with version 25 (released 22 November 2016) uses Wayland for the default GNOME 3.22 desktop session, with [[X.Org]] as a fallback if the graphics driver cannot support Wayland. Fedora uses Wayland as the default for KDE desktop session starting with version 34 (released 27 April 2021) * [[Manjaro]] ships Wayland as default in the Gnome edition of Manjaro 20.2 (Nibia) (released 22 November 2020). * [[Raspberry Pi OS]], a port of Debian, has offered the option to use Wayland since version [[Debian 11|11 (Bullseye)]], which was released on 3 December 2021. Wayland became the default in version [[Debian 12|12 (Bookworm)]], released on 10 October 2023. * [[Red Hat Enterprise Linux]] ships Wayland as the default session in version 8, released 7 May 2019. * [[Ubuntu]] shipped with Wayland by default in Ubuntu 17.10 (Artful Aardvark). However, Ubuntu 18.04 LTS reverted to X.Org by default due to several issues. Since Ubuntu 21.04, Wayland is the default again. * [[Slackware]] included Wayland on 20 February 2020 for the development version, -current, which became version 15.0 in 2022. However, Wayland is still not the default. == History == Kristian Høgsberg, a [[Linux]] graphics and [[X.Org]] developer who previously worked on [[AIGLX]] and [[Direct Rendering Infrastructure|DRI2]], started Wayland as a spare-time project in 2008 while working for [[Red Hat]]. His stated goal was a system in which "every frame is perfect, by which I mean that applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker." Høgsberg was driving through the town of Wayland, Massachusetts when the underlying concepts "crystallized", hence the name (Weston and Maynard are also nearby towns in the same area, continuing the reference). In October 2010, Wayland became a [[freedesktop.org]] project. As part of the migration, the prior Google Group was replaced by the ''wayland-devel'' mailing list as the project's central point of discussion and development. The Wayland client and server libraries were initially released under the [[MIT License]], while the reference compositor Weston and some example clients used the [[GNU General Public License]] version 2. Later, all the GPL code was relicensed under the MIT license "to make it easier to move code between the reference implementation and the actual libraries". In 2015 it was discovered that the license text used by Wayland was a slightly different and older version of the MIT license, and the license text was updated to the current version used by the [[X.Org]] project (known as [[Expat License|MIT Expat License]]). {| class="wikitable sortable collapsible text-align:center" |} 6dd14e39a5f2e01ebeed12ca5b411c7d64f37fb6 0 1007 4992 4273 2026-05-23T22:34:54Z MarkH 357 fix some broken wikilinks wikitext text/x-wiki {{stub}} [[Category:Terminology]] The term '''package''' refers to designated file [[archive]]s, containing metadata, and files for a piece of [[software]], a desktop theme, development headers, fonts, source code, etc., and bundling these files could benefit a significant group of users.<ref>[https://www.geeksforgeeks.org/linux-unix/understanding-package-managers-and-systemctl/ Understanding Package Managers and systemctl], GeeksforGeeks, 2025-07-23 (Accessed: 2025-09-02)</ref><ref>[https://www.howtouselinux.com/post/understanding-package-management-a-guide-to-package-managers-in-linux Understanding Package Management: A Guide to Package Managers in Linux], David Cao, 2023-10-09 (Accessed: 2025-09-02)</ref><ref>[https://linuxsimply.com/linux-basics/package-management/what-is-package/ What is Package in Linux? <nowiki>[Types, Features & More]</nowiki>], Afia Zahin Oishi, 2023-12-31 (Accessed: 2025-09-02)</ref> While not necessarily being the case, many package formats require their own [[package manager]]s to actually extract and [[install]] the bundled files onto a system; and most [[Linux Distributions|Linux distributions]], other [[UNIX]]-like [[Operating System|operating system]]s and some [[Programming Languages|programming languages]] also come with their own package managers. Package managers, as the name suggests, allow end-users to perform package-related system maintenance tasks, including searching, installing, removing, and updating packages. While packages may be delivered individually, distributions usually gather a set of common packages into their own ''software [[repository|repositories]]'' where package managers search and download packages from. The existence of repositories enables updates to be shipped semi-automatically to a large group of users in an efficient manner, replacing the need for programs to perform their own autoupdate checks. == List of Package Formats == Archive format is represented without the first dot, and distributions are listed with their shorter common names if any. Programming languages are in parentheses. Package managers that do not come with their own file formats are not listed here. See [[package manager]] instead. Immutable variants (esp. [[OSTree]]) that are only wrappers are not listed. {| class="sortable wikitable" ! Format !! Package Manager !! Distributions |- |[[AppImage]] || - ||* |- |[[crate]]||[[cargo]]||([[Rust]]) |- |[[deb]]||[[dpkg]]||[[Debian]] |- |[[deb]]||[[apt]]||[[Debian]] |- |[[ebuild]]||[[portage]]||[[Gentoo]] |- |[[flatpak]]||[[flatpak]]||* |- |[[jar]]|| -||([[Java]]) |- |[[nimble]]||[[nimble]]||([[Nim]]) |- |[[nix]]||[[nix]]||* |- |[[npm]]||[[npm]]||([[JavaScript]]) |- |[[rpm]]||[[dnf]] / [[rpm]]||[[CentOS Stream]] / [[Fedora]] / [[RHEL]] |- |[[rpm]]||[[yum]] / [[rpm]]||[[CentOS]] |- |[[rpm]]||[[zypper]] / [[rpm]]||[[openSUSE]] |- |[[snap]]||[[snap]]||[[Ubuntu]] / * |- |[[Tarball|tar.gz]]||[[pip]]||([[Python]]) |- |[[Tarball|tar.zst]]||[[pacman]]||[[Arch]] |- |[[whl]]||[[pip]]||([[Python]]) |- |[[xbps]]||[[xbps]]||[[Void]] |} == References == d863465768e89174dc4fffb97629f69a1b084a5d 0 781 4993 4044 2026-05-23T22:38:03Z MarkH 357 fix a broken wikilink wikitext text/x-wiki {{stub}} {{Needs Citations}} [[Category:Package Managers]] '''RPM''' stands for '''Red Hat Package Manager'''. It is both a package format (<code>.rpm</code>) and the name of the [[package]] management system used primarily in [[Red Hat]]-based [[Linux Distributions|Linux distributions]], including: * [[Red Hat Enterprise Linux]] (RHEL) * [[Fedora]] Linux * [[CentOS]] * [[AlmaLinux]] * [[Rocky Linux]] * [[openSUSE]] == Overview == An RPM package is a file that contains: * Compiled software binaries * Configuration files * Metadata (name, version, dependencies, etc.) * Installation and removal scripts The standard file extension is <code>.rpm</code>. == Components of an RPM Package == * <b>Header</b>: Contains metadata (name, version, architecture, etc.) * <b>Payload</b>: The actual files to be installed * <b>Scripts</b>: Optional pre/post-install and removal scripts == Common Tools == * <code>rpm</code> — Low-level tool for querying, installing, and removing RPM packages * <code>rpmbuild</code> — Tool for building RPM packages from SPEC files * <code>rpmlint</code> — Linter to check RPM quality and packaging errors == Basic Commands == === Installing an RPM file === <syntaxhighlight lang="bash"> sudo rpm -ivh package.rpm </syntaxhighlight> === Query installed packages === <syntaxhighlight lang="bash"> rpm -q package-name </syntaxhighlight> === List all installed RPMs === <syntaxhighlight lang="bash"> rpm -qa </syntaxhighlight> === Remove a package === <syntaxhighlight lang="bash"> sudo rpm -e package-name </syntaxhighlight> === Verify a package === <syntaxhighlight lang="bash"> rpm -V package-name </syntaxhighlight> == Advantages == * Dependency tracking * Transaction-based installation/removal * Clean upgrade paths * Strong ecosystem support (DNF, YUM, repositories, etc.) == Limitations == * Requires careful dependency management * Binary format — not human-readable == External Resources == * [https://rpm.org/ Official RPM Site] * [https://fedoraproject.org/wiki/RPM Fedora RPM Guide] * [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Fedora Packaging Guidelines] == See Also == * [[yum]] * [[dnf]] * [[rpmbuild]] * [[zypper]] bd359ed8c8b7a22b867dd00114c2a718e754324e 0 1194 4994 2026-05-23T22:50:42Z MarkH 357 redirect operating system -> Operating System wikitext text/x-wiki #REDIRECT [[Operating System]] 4d4dd358fc4cb31741d493c347ea9f96c2c6af75 0 828 4995 3439 2026-05-23T22:53:59Z MarkH 357 fix a broken wikilink wikitext text/x-wiki '''udev''' is a device manager for the [[Linux kernel]]. As the successor of [[devfsd]] and hotplug, udev primarily manages device nodes in the directory. At the same time, udev also handles all [[user space]] events raised when hardware devices are added into the system or removed from it, including [[firmware]] loading as required by certain devices. == Rationale == It is an [[operating system]]'s [[kernel]] that is responsible for providing an abstract interface of the hardware to the rest of the software. Being a [[monolithic kernel]], the [[Linux kernel]] does exactly that: device drivers are part of the Linux kernel, and make up more than half of its source code. Hardware can be accessed through [[System call|system calls]] or over their device nodes. To be able to deal with peripheral devices that are [[hotplug]]-capable in a user-friendly way, a part of handling all of these hotplug-capable hardware devices was handed over from the kernel to a [[Daemon (computing)|daemon]] running in user-space. Running in user space serves security and stability purposes. == Design == Device drivers are part of the Linux kernel, in which their primary functions include device discovery, detecting device state changes, and similar low-level hardware functions. After loading a device driver into memory from the kernel, detected events are sent out to the userspace daemon udevd. It is the device manager that catches all of these events and then decides what shall happen next. This has a very comprehensive set of configuration files, which can all be adjusted by the computer administrator, according to their needs. * In case a new storage device is connected over USB, udevd is notified by the kernel and itself notifies the udisksd-daemon. That daemon could then mount the file systems. * In case a new Ethernet cable is plugged into the Ethernet NIC, udevd is notified by the kernel and itself notifies the NetworkManager-daemon. The NetworkManager-daemon could start dhclient for that NIC, or configure according to some manual configuration. The complexity of doing so forced application authors to re-implement hardware support logic. Some hardware devices also required privileged helper programs to prepare them for use. These often have to be invoked in ways that could be awkward to express with the Unix permissions model (for example, allowing users to join [[Wireless network|wireless networks]] only if they are logged into the video console). Application authors resorted to using [[setuid]] binaries or run service [[Daemon (computing)|daemons]] to provide their own access control and privilege separation, potentially introducing security holes each time. [[HAL (software)|HAL]] was created to deal with these challenges, but is now deprecated in most Linux distributions, its functionality being replaced by udevd. == Overview == Unlike traditional [[Unix]] systems, where the device nodes in the /dev directory have been a static set of files, the Linux udev device manager dynamically provides only the nodes for the devices actually present on a system. Although [[devfs]] used to provide similar functionality, Greg Kroah-Hartman cited a number of reasons for preferring udev over devfs: * udev supports persistent device naming, which does not depend on, for example, the order in which the devices are plugged into the system. The default udev setup provides persistent names for storage devices. Any hard disk is recognized by its unique filesystem id, the name of the disk and the physical location on the hardware it is connected to. * udev executes entirely in [[user space]], as opposed to devfs's [[kernel space]]. One consequence is that udev moved the naming policy out of the kernel and can run arbitrary programs to compose a name for the device from the device's properties, before the node is created; there, the whole process is also interruptible and it runs with a lower priority. The udev, as a whole, is divided into three parts: * [[Library (computing)|Library]] ''libudev'' that allows access to device information; it was incorporated into the [[systemd]] 183 software bundle. * User space [[Daemon (computing)|daemon]] udevd that manages the virtual /dev. * Administrative [[command-line utility]] udevadm for diagnostics. The system gets calls from the kernel via [[netlink]] socket. Earlier versions used [[Hotplug (software)|hotplug]], adding a link to themselves in /etc/hotplug.d/default with this purpose. == Operation == [[File:Free_and_open-source-software_display_servers_and_UI_toolkits.svg|thumb|350x350px|udev has been incorporated into [[systemd]] 183]] udev is a generic device manager running as a [[Daemon (computer software)|daemon]] on a Linux system and listening (via a [[netlink]] socket) to uevents the kernel sends out if a new device is initialized or a device is removed from the system. The udev package comes with an extensive set of rules that match against exported values of the event and properties of the discovered device. A matching rule will possibly name and create a device node and run configured programs to set up and configure the device. udev rules can match on properties like the kernel subsystem, the kernel device name, the physical location of the device, or properties like the device's serial number. Rules can also request information from external programs to name a device or specify a custom name that will always be the same, regardless of the order devices are discovered by the system. In the past a common way to use udev on Linux systems was to let it send events through a socket to [[HAL (software)|HAL]], which would perform further device-specific actions. For example, HAL would notify other software running on the system that the new hardware had arrived by issuing a broadcast message on the [[D-Bus]] [[Inter-process communication|IPC]] system to all interested [[Process (computing)|processes]]. In this way, desktops such as [[GNOME]] or [[K Desktop Environment 3]] could start the [[file browser]] to browse the file systems of newly attached [[USB flash drive|USB flash drives]] and [[Secure Digital|SD cards]]. By the middle of 2011 HAL had been deprecated by most Linux distributions as well as by the KDE, GNOME and [[Xfce]] desktop environments, among others. The functionality previously embodied in HAL has been integrated into udev itself, or moved to separate software such as udisks and [[upower]]. * udev provides low-level access to the linux device tree. Allows programs to enumerate devices and their properties and get notifications when devices come and go. * dbus is a framework to allow programs to communicate with each other, securely, reliably, and with a high-level object-oriented programming interface. * udisks (formerly known as DeviceKit-disks) is a daemon that sits on top of libudev and other kernel interfaces and provides a high-level interface to storage devices and is accessible via dbus to applications. * upower (formerly known as DeviceKit-power) is a daemon that sits on top of libudev and other kernel interfaces and provides a high-level interface to power management and is accessible via dbus to applications. * [[NetworkManager]] is a daemon that sits on top of libudev and other kernel interfaces (and a couple of other daemons) and provides a high-level interface to network configuration and setup and is accessible via dbus to apps. udev receives messages from the kernel, and passes them on to subsystem daemons such as Network Manager. Applications talk to Network Manager over D-Bus. : <chem>Kernel -> udev -> Network Manager <=> D-Bus <=> Firefox</chem> HAL is obsolete and only used by legacy code. Ubuntu 10.04 shipped without HAL. Initially a new daemon DeviceKit was planned to replace certain aspects of HAL, but in March 2009, DeviceKit was deprecated in favor of adding the same code to udev as a package: udev-extras, and some functions have now moved to udev proper. == History == udev was introduced in Linux 2.5. The Linux kernel version 2.6.13 introduced or updated a new version of the [[uevent]] interface. A system using a new version of udev will not boot with kernels older than 2.6.13 unless udev is disabled and a traditional /dev directory is used for device access. In April 2012, udev's [[codebase]] was merged into the [[systemd]] source tree, making systemd 183 the first version to include udev. In October 2012, [[Linus Torvalds]] criticized Kay Sievers's approach to udev maintenance and bug fixing related to [[firmware]] loading. In 2012, the [[Gentoo Linux]] project created a [[Fork (software development)|fork]] of systemd's udev codebase in order to avoid dependency on the systemd architecture. The resulting fork is called ''[[eudev]]'' and it makes udev functionality available without systemd. A stated goal of the project is to keep eudev independent of any [[Linux distribution]] or [[init]] system. On May 29, 2014, support for firmware loading through udev was dropped from systemd, as it has been decided that it is the kernel's task to load firmware. Two days later, Lennart Poettering suggested this patch be postponed until [[kdbus]] starts to be utilized by udev; at that point, the plan was to switch udev to use kdbus as the underlying messaging system, and to get rid of the userspace-to-userspace netlink-based transport. 2b3221be8ae1a18ad3f6c7e39c8faa77c9d629bf 0 1195 4996 2026-05-23T22:55:39Z MarkH 357 redirect Linux distributions -> Linux Distributions wikitext text/x-wiki #REDIRECT [[Linux Distributions]] f6721c832bacd7daf16c3910dd1b30b95255d241 0 663 4997 4842 2026-05-23T23:02:32Z MarkH 357 fix a broken wikilink wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terrapkg.com terrapkg.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora|Fedora Linux]] and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terrapkg.com terrapkg.com], Terra, 2026 (Accessed: 2026-05-23)</ref> Developed by [[Fyra Labs]], it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://docs.terrapkg.com/general/infrastructure/ How Terra Works], Terra Documentation, 2026 (Accessed: 2026-05-23)</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://docs.terrapkg.com/usage/installing/. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji]{{Dead Link|2025-08-14|401}}, RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://docs.terrapkg.com/contributing/autoupdate/ Automatic Updates], Terra Documentation, 2026 (Accessed: 2026-05-23)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably Rust, Go, [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://docs.terrapkg.com/contributing/policies/ Policies], Terra Documentation, 2026 (Accessed: 2026-05-23)</ref> == See Also == * [https://terrapkg.com Main Website] * [https://docs.terrapkg.com Terra Documentations] * [https://github.com/terrapkg/packages Terra Sources] == References == 72c6196fc59fbd4c607c86948c978ed96c59c5af 0 1056 4998 4318 2026-05-23T23:03:43Z MarkH 357 fix a broken wikilink wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Rolling release''' is a software release model where software updates are delivered continuously. Unlike [[fixed release]] which is in a discrete manner, rolling release usually implies shipping the latest software as soon as possible. A famous example would be [[Arch Linux]]. Rolling release does not imply unstable software. The software may be tested thoroughly before shipping. An example would be [[openSUSE Tumbleweed]]. The deciding factor for [[distro]]s would be usually whether updates would stop, that is, whether ''mass updates'' are provided, where there are full ''system upgrades'' in which many [[package]]s would be updated together. If so, that violates the fundamental requirements of rolling release. == Semi-rolling == '''Semi-rolling''' is a layman's term for describing distributions providing updates for non-breaking features, bug fixes, etc., while requiring full system upgrades to receive further software updates, otherwise updates will stop eventually. There is no concrete definition and the term is quite ambiguous, but usually this describes fixed-release distros like [[Fedora|Fedora Linux]]. c4ea181127ce45e50b5be1ae26dc8488a3af3608 0 1196 4999 2026-05-23T23:07:31Z Uniolo 345 Create redirect (GnuPG -> Gnupg). It should probs be the other way around but I don't know how to move pages (and I don't think I have perms anyways) wikitext text/x-wiki #REDIRECT [[Gnupg]] ac4b6314f82928a0a3061203e538450b71c7dc94 6 1197 5000 2026-05-23T23:11:08Z Uniolo 345 wikitext text/x-wiki The help screen for age 1.3.1 43ced3bffd3e3239ca30552a6be82f5007f0005a 0 1198 5002 2026-05-23T23:25:47Z Mattos-sus 382 Added Privacy page under Terminology wikitext text/x-wiki Online privacy refers to the ability to control how personal information is collected, shared, and used on the internet. Privacy is an important aspect of modern digital life. Good privacy practices can help reduce risks of identity theft, phishing, unauthorized tracking, and data breaches. Privacy can also support personal autonomy, allowing users to communicate, browse, and use online services with greater control over their personal data. Privacy is closely related to [[Security|security]], but the two are not identical. Privacy focuses on control over personal information, while security mainly focuses on protecting systems and data from unauthorized access. Some online services collect user data for analytics, advertising, or machine learning purposes. Privacy-focused tools and services aim to minimize unnecessary data collection and give users more transparency and control. == Best Practices == Common privacy practices include: * Using strong and unique passwords for each account; * Enabling two-factor authentication (2FA); * Keeping software and devices updated; * Using privacy-focused software and services when possible; * Reviewing application permissions regularly; * Limiting the amount of personal information shared publicly online; * Using a VPN when additional network privacy is required, especially on public networks. Examples of privacy-focused tools include: * Privacy-respecting web browsers; * Search engines with limited tracking; * Secure communication platforms; * Encrypted password managers. == Recommended Software == The following software and services are commonly recommended by privacy-focused communities. Users should research and choose tools that best fit their needs and threat model. === Password Managers === * [http://keepassxc.org KeePassXC] * [http://bitwarden.com Bitwarden] * [http://1password.com 1Password] === Web Browsers === * [https://firefox.com Firefox] * [http://brave.com Brave] * [https://torproject.org Tor Browser] === Search Engines === * [https://duckduckgo.com DuckDuckGo] * [https://search.brave.com Brave Search] === Authenticator Apps === * [https://ente.io/auth Ente Auth] * [https://getaegis.app Aegis Authenticator] === Communication and Email === * [https://signal.org Signal] * [https://proton.me/mail Proton Mail] * [https://tuta.com/secure-email Tuta Mail] === VPN Providers === * [https://protonvpn.com Proton VPN] * [https://mullvad.net Mullvad] === Cloud Storage === * [https://nextcloud.com Nextcloud] * [https://sync.com Sync.com] * [https://proton.me/drive Proton Drive] === Operating Systems === * [[Linux Distributions|GNU/Linux distributions]] * [[GrapheneOS|GrapheneOS]] * [https://calyxos.org CalyxOS] 1385a13b34b09a7cae789c863c794780dc0f44e8 5006 5002 2026-05-24T00:19:58Z Mattos-sus 382 Update software list, add internal links and short descriptions wikitext text/x-wiki Online privacy refers to the ability to control how personal information is collected, shared, and used on the internet. Privacy is an important aspect of modern digital life. Good privacy practices can help reduce risks of identity theft, phishing, unauthorized tracking, and data breaches. Privacy can also support personal autonomy, allowing users to communicate, browse, and use online services with greater control over their personal data. Privacy is closely related to [[security]], but the two are not identical. Privacy focuses on control over personal information, while security mainly focuses on protecting systems and data from unauthorized access. Some online services collect user data for analytics, advertising, or machine learning purposes. Privacy-focused tools and services aim to minimize unnecessary data collection and give users more transparency and control. == Best Practices == Common privacy practices include: * Using strong and unique passwords for each account; * Enabling two-factor authentication (2FA); * Keeping software and devices updated; * Using privacy-focused software and services when possible; * Reviewing application permissions regularly; * Limiting the amount of personal information shared publicly online; * Using a VPN when additional network privacy is required, especially on public networks. Examples of privacy-focused tools include: * Privacy-respecting web browsers; * Search engines with limited tracking; * Secure communication platforms; * Encrypted password managers. == Recommended Software == The following software and services are commonly recommended by privacy-focused and FOSS communities. Users should research and choose tools that best fit their needs and threat model. === Password Managers === * [[KeePassXC]] — Local-first, encrypted password manager using open formats. * [[Bitwarden]] — Open-source password manager with cloud sync options. === Web Browsers === * [[Firefox]] — Open-source web browser developed by Mozilla. * [[Librewolf|LibreWolf]] — Privacy-hardened fork of Firefox with reduced telemetry. * [[tor|Tor Browser]] — Browser focused on anonymity via the Tor network. === Authenticator Apps === * [[Ente Auth]] — Open-source TOTP authenticator with encrypted sync. * [[Aegis Authenticator]] — Local-only open-source TOTP authenticator for Android. === Communication and Email === * [https://signal.org Signal] — Encrypted messaging app with open-source clients. * [https://tuta.com Tuta Mail] — Privacy-focused encrypted email service (partially open-source). === Encryption Tools === * [[GnuPG]] — Open-source implementation of the OpenPGP standard for encryption and signing. * [[age]] — Simple modern file encryption tool. * [[Cryptomator]] — Client-side encryption tool for cloud storage. * [[VeraCrypt]] — Disk encryption software for full-volume encryption. === VPN Providers === * [https://mullvad.net Mullvad] — Privacy-focused VPN provider with open-source clients. === Self-hosted Cloud Storage === * [[Nextcloud]] — Full-featured self-hosted collaboration and file sync platform. * [[ownCloud]] — Self-hosted file sharing and sync platform with enterprise options. * [[Syncthing]] — Peer-to-peer file synchronization tool without central servers. 3c1ba6eb0c2ada39e4fa10b4f936e65ed2bcdd8a 5007 5006 2026-05-24T00:24:49Z Mattos-sus 382 Update internal links wikitext text/x-wiki Online privacy refers to the ability to control how personal information is collected, shared, and used on the internet. Privacy is an important aspect of modern digital life. Good privacy practices can help reduce risks of identity theft, phishing, unauthorized tracking, and data breaches. Privacy can also support personal autonomy, allowing users to communicate, browse, and use online services with greater control over their personal data. Privacy is closely related to [[security]], but the two are not identical. Privacy focuses on control over personal information, while security mainly focuses on protecting systems and data from unauthorized access. Some online services collect user data for analytics, advertising, or machine learning purposes. Privacy-focused tools and services aim to minimize unnecessary data collection and give users more transparency and control. == Best Practices == Common privacy practices include: * Using strong and unique passwords for each account; * Enabling two-factor authentication (2FA); * Keeping software and devices updated; * Using privacy-focused software and services when possible; * Reviewing application permissions regularly; * Limiting the amount of personal information shared publicly online; * Using a VPN when additional network privacy is required, especially on public networks. Examples of privacy-focused tools include: * Privacy-respecting web browsers; * Search engines with limited tracking; * Secure communication platforms; * Encrypted password managers. == Recommended Software == The following software and services are commonly recommended by privacy-focused and FOSS communities. Users should research and choose tools that best fit their needs and threat model. === Password Managers === * [[KeePassXC]] — Local-first, encrypted password manager using open formats. * [[Bitwarden]] — Open-source password manager with cloud sync options. === Web Browsers === * [[Firefox]] — Open-source web browser developed by Mozilla. * [[Librewolf|LibreWolf]] — Privacy-hardened fork of Firefox with reduced telemetry. * [[tor|Tor Browser]] — Browser focused on anonymity via the Tor network. === Authenticator Apps === * [[Ente Auth]] — Open-source TOTP authenticator with encrypted sync. * [[Aegis Authenticator]] — Local-only open-source TOTP authenticator for Android. === Communication and Email === * [https://signal.org Signal] — Encrypted messaging app with open-source clients. * [https://tuta.com Tuta Mail] — Privacy-focused encrypted email service (partially open-source). === Encryption Tools === * [[GnuPG]] — Open-source implementation of the OpenPGP standard for encryption and signing. * [[age]] — Simple modern file encryption tool. * [[Cryptomator]] — Client-side encryption tool for cloud storage. * [[VeraCrypt]] — Disk encryption software for full-volume encryption. === VPN Providers === * [https://mullvad.net Mullvad] — Privacy-focused VPN provider with open-source clients. === [[Self-Hosting|Self-hosted]] cloud storage === * [[Nextcloud]] — Full-featured self-hosted collaboration and file sync platform. * [[ownCloud]] — Self-hosted file sharing and sync platform with enterprise options. * [[Syncthing]] — Peer-to-peer file synchronization tool without central servers. c0ce2190fb1577af43116e86dd1b74890e40792d 0 1146 5003 4828 2026-05-23T23:42:26Z MarkH 357 fix infobox and references section wikitext text/x-wiki {{SoftwareInfobox | title = Tor | image = [[File:Tor-logo-2011-flat.svg]] | caption = The Tor Project logo | releasestatus = Maintained | lastrelease = 0.4.9.8 (2026-05-07)<ref>[https://forum.torproject.org/t/security-release-0-4-8-25-and-0-4-9-8/21559] Security Release 0.4.8.25 and 0.4­.9.8</ref> | languages = [[C]] | developers = The Tor Project | website = https://www.torproject.org/ }} [[Category:Privacy]] [[Category:Security]] [[Category:Networking]] [[Category:Free Software]] '''Tor''' (The Onion Router) is a free and open-source anonymity network designed to protect user privacy and resist surveillance, tracking, and censorship on the internet. Tor routes internet traffic through multiple volunteer-operated relays around the world, making it significantly more difficult to trace a user's activity or determine their real IP address. The project is developed by '''The Tor Project''', a nonprofit organization focused on online privacy, anonymity, and freedom of information. == Overview == Tor uses a system known as '''onion routing'''. Instead of connecting directly to a website or service, traffic is encrypted and passed through several relays before reaching its destination. A normal Tor circuit usually consists of: # Entry Guard # Middle Relay # Exit Relay Each relay only knows the previous and next node in the chain. This architecture helps prevent a single relay from knowing both: * who the user is * and where the traffic is going == Onion Routing == Tor encrypts data in multiple layers similar to the layers of an onion. Each relay decrypts only one layer before forwarding the traffic to the next relay. Benefits include: * IP address hiding * Resistance to surveillance * Reduced tracking * Circumvention of censorship * Metadata protection == Tor Browser == '''Tor Browser''' is the most common application used to access the Tor network. It is based on Mozilla Firefox and includes additional privacy protections such as: * Anti-fingerprinting features * HTTPS-only mode * Tracking protection * Script restrictions * Isolated browsing sessions Tor Browser attempts to make users appear similar to each other in order to reduce browser fingerprinting attacks. == Onion Services == Tor supports anonymous websites and services using ''.onion'' domains. These are known as '''Onion Services'''. Unlike normal websites, Onion Services hide the server's real IP address and remain fully inside the Tor network. Common uses include: * anonymous communication * whistleblowing platforms * privacy-focused services * censorship-resistant publishing == Bridges == Some countries and internet providers block access to Tor. To bypass censorship, Tor supports '''bridges'''. Bridges are special relays not publicly listed in the main Tor directory. Common bridge technologies include: * obfs4 * Snowflake * meek === Snowflake === '''Snowflake''' uses temporary volunteer-operated proxies to help censored users connect to Tor. This makes large-scale blocking more difficult. == Security == Tor is designed to defend against: * traffic analysis * ISP monitoring * censorship * mass surveillance * location tracking However, Tor does not guarantee complete anonymity. User behavior, browser exploits, malware, phishing, and operational security mistakes can still compromise privacy. === Exit Relay Risks === The exit relay decrypts the final layer before traffic reaches the destination website. Because of this: * non-HTTPS traffic may be visible to the exit operator * HTTPS remains important while using Tor === Traffic Correlation === A powerful adversary capable of monitoring both the user's connection and the destination server may attempt correlation attacks. This remains one of the main theoretical weaknesses of anonymity networks. == Performance == Tor is generally slower than normal internet connections because traffic travels through multiple relays across different countries. Performance depends on: * relay congestion * network distance * censorship * circuit quality Applications requiring very low latency may perform poorly over Tor. == Use Cases == Tor is commonly used for: * anonymous browsing * bypassing censorship * privacy protection * secure communications * journalism * research * whistleblowing == Criticism == Tor is sometimes criticized for: * slow speeds * abuse by malicious actors * website blocking * misconceptions about "perfect anonymity" Using Tor alone does not automatically make a user anonymous. == See Also == * [[Tor Browser]] * [[Onion Routing]] * [[Whonix]] * [[Tails]] * [[I2P]] * [[VPN]] == References == <references/> == External Links == * https://www.torproject.org/ * https://tb-manual.torproject.org/ * https://support.torproject.org/ * https://www.torproject.org/download/ * https://metrics.torproject.org/ 0912c573359f4235152f70491ca859942a9d4981 5010 5003 2026-05-24T00:58:58Z Matthias von Schwarzwald 361 Begin de-bulletpointing wikitext text/x-wiki {{SoftwareInfobox | title = Tor | image = [[File:Tor-logo-2011-flat.svg]] | caption = The Tor Project logo | releasestatus = Maintained | lastrelease = 0.4.9.8 (2026-05-07)<ref>[https://forum.torproject.org/t/security-release-0-4-8-25-and-0-4-9-8/21559] Security Release 0.4.8.25 and 0.4­.9.8</ref> | languages = [[C]] | developers = The Tor Project | website = https://www.torproject.org/ }} [[Category:Privacy]] [[Category:Security]] [[Category:Networking]] [[Category:Free Software]] '''Tor''' (The Onion Router) is a free and open-source anonymity network designed to protect user privacy and resist surveillance, tracking, and censorship on the internet. Tor routes internet traffic through multiple volunteer-operated relays around the world, making it significantly more difficult to trace a user's activity or determine their real IP address. The project is developed by '''The Tor Project''', a nonprofit organization focused on online privacy, anonymity, and freedom of information. == Overview == Tor uses a system known as '''onion routing'''. Instead of connecting directly to a website or service, traffic is encrypted and passed through several relays before reaching its destination. A normal Tor circuit usually consists of: # Entry Guard # Middle Relay # Exit Relay Each relay only knows the previous and next node in the chain. This architecture helps prevent a single relay from knowing both who the user is and where the traffic is going. == Onion Routing == Tor encrypts data in multiple layers similar to the layers of an onion. Each relay decrypts only one layer before forwarding the traffic to the next relay. Benefits include: * IP address hiding * Resistance to surveillance * Reduced tracking * Circumvention of censorship * Metadata protection == Tor Browser == '''Tor Browser''' is the most common application used to access the Tor network. It is based on Mozilla [[Firefox]] and includes additional privacy protections such as: * Anti-fingerprinting features * HTTPS-only mode * Tracking protection * Script restrictions * Isolated browsing sessions Tor Browser attempts to make users appear similar to each other in order to reduce browser fingerprinting attacks. == Onion Services == Tor supports anonymous websites and services using ''.onion'' domains. These are known as '''Onion Services'''. Unlike normal websites, Onion Services hide the server's real IP address and remain fully inside the Tor network. Common uses include: * anonymous communication * whistleblowing platforms * privacy-focused services * censorship-resistant publishing == Bridges == Some countries and internet providers block access to Tor. To bypass censorship, Tor supports '''bridges'''. Bridges are special relays not publicly listed in the main Tor directory. Common bridge technologies include obfs4, Snowflake, and meek.{{Citation needed}} === Snowflake === '''Snowflake''' uses temporary volunteer-operated proxies to help censored users connect to Tor. This makes large-scale blocking more difficult. == Security == Tor is designed to defend against: * traffic analysis * ISP monitoring * censorship * mass surveillance * location tracking However, Tor does not guarantee complete anonymity. User behavior, browser exploits, malware, phishing, and operational security mistakes can still compromise privacy. === Exit Relay Risks === The exit relay decrypts the final layer before traffic reaches the destination website. Because of this, non-[[HTTPS]] traffic may be visible to the exit operator. HTTPS remains important while using Tor. === Traffic Correlation === A powerful adversary capable of monitoring both the user's connection and the destination server may attempt correlation attacks. This remains one of the main theoretical weaknesses of anonymity networks. == Performance == Tor is generally slower than normal internet connections because traffic travels through multiple relays across different countries. Performance depends on relay congestion, network distance, circuit quality, and censorship. Applications requiring very low latency may perform poorly over Tor. == Use Cases == Tor is commonly used for: * anonymous browsing * bypassing censorship * privacy protection * secure communications * journalism * research * whistleblowing == Criticism == Tor is sometimes criticized for slow speeds, website blocking, abuse by malicious actors, and misconceptions about "perfect anonymity". Using Tor alone does not automatically make a user anonymous. == See Also == * [[Tor Browser]] * [[Onion Routing]] * [[Whonix]] * [[Tails]] * [[I2P]] * [[VPN]] == References == <references/> == External Links == * https://www.torproject.org/ * https://tb-manual.torproject.org/ * https://support.torproject.org/ * https://www.torproject.org/download/ * https://metrics.torproject.org/ 3950ba1bb07b2fbcd59b759edb94ac47f7cf16d9 0 198 5004 4966 2026-05-23T23:46:10Z MarkH 357 fix a broken wikilink wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of KDE plasma. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 859300a5ee1b78be7d2c6556a260019f80c09965 0 1120 5005 4935 2026-05-23T23:58:21Z Uniolo 345 Redo change that was lost due to a bug, change "ICCF Holland" to Kuwasha to reflect that ICCF Holland is now defunct and Vim now encouraging users to donate to Kuwasha wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim|NeoVim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use the <code>vimtutor</code> command. <code>Vim ''path/to/filename'' </code> is used to open a new or existing file for editing, though you can also open a file from within Vim. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] == References == <references /> c6f9e8d6ebdacf7c4585d23d6dee78009f9dbe25 5014 5005 2026-05-24T01:05:07Z Uniolo 345 Removed note about how to open files because it is not the only way, feels too basic, and I just realized I would probably have to add the "possibly dangerous commands warning" (albeit I was not the one who added it). wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim|NeoVim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use the <code>vimtutor</code> command. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] == References == <references /> ba24303f6acd1979914ba723a9fba985eade9193 5015 5014 2026-05-24T01:06:31Z Uniolo 345 Added note about how to use Vimtutor wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim|NeoVim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] == References == <references /> 09c4832910c497948a7c45f9c61587fe1942f2b4 6 1199 5009 2026-05-24T00:55:46Z Uniolo 345 wikitext text/x-wiki Kakoune open to the Linux kernel source code (init/main.c) f94ff3b326a3b736165aaa4f8c85b57b57eeb716 0 1200 5011 2026-05-24T01:01:10Z Uniolo 345 Create Kakoune page with sidebar, some basic info, and an image I took of it in the Linux kernel source code (because it does not have a splash screen, I had the source code laying around, and I needed a photo of it). wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Kakoune logo.svg|thumb|The logo for Kakoune]] |caption=Kakoune |title=Kakoune |releasestatus=Maintained |lastrelease=2026.05.21, May 20, 2026 |firstrelease=Unknown, Sep 2, 2011 |languages=[[C++]], [[Kakoune Script]] |developers=[https://github.com/mawww Maxime Coste] |website=[https://kakoune.org/ kakoune.org] }} [[File:Kakoune-linux-init-main.c.png|thumb|Kakoune open to the Linux kernel source code (<code>init/main.c</code>)]] '''Kakoune''' is a modal editor, it is designed to provide an efficient, predictable, and scriptable code editing environment<ref>{{Cite|url=https://kakoune.org/why-kakoune/why-kakoune.html|title=Why Kakoune|author=Maxime Coste|year=2020-01-03|accessdate=2026-05-23}}</ref>. It is a strong divergence from [[Vi]] like editors and inspired [[Helix]]. [[Category:Software]] 451259430eb88e6ed086e7a43e6274d37ade5bcf 0 784 5012 4931 2026-05-24T01:01:40Z Matthias von Schwarzwald 361 Typos and a link wikitext text/x-wiki {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = [[GNOME]] | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }}{{Stub}} Zorin OS is an [[Ubuntu]]-based [[Linux Distributions|Linux distribution]] made for newcomers to Linux, with a modified version of the [[GNOME]] [[GUI]] and [[XFCE|Xfce 4]] that is familiar to Windows users. It also has a paid model that comes with more desktop options and free software. It was first released on July 1, 2009, under the name Zorin OS 1.0. [[Category:Linux Distributions]] ebba11fb74e5bd59870d85076b11a64a44d9c17a 0 236 5013 3691 2026-05-24T01:04:51Z Matthias von Schwarzwald 361 Typos wikitext text/x-wiki {{Needs_Citations}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|Xfce logo]] | caption = Xfce logo | title = Xfce | releasestatus = Maintained | lastrelease = Xfce 4.20, 2024-12-15 | languages = [[C]] | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[Category:Desktop Environments]] [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]] Xfce is a lightweight [[Desktop Environments|desktop environment]] aiming to be fast for weaker hardware while still remaining user-friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * [[Desktop Manager]] - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[TUI|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal-based calendar and a CD- and DVD-burning application.<ref>[https://xfce.org/about About – Xfce], Xfce Development Team, 2021-11-10 (Accessed: 2025-08-09)</ref> == References == ae2ba9580a9374aa08de39685b7d5f292806e349 0 396 5017 4958 2026-05-24T02:07:36Z Uniolo 345 added Kakoune wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Description !DE |- |Discover |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Description !Distribution |- |[[pacman]] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Description |- |[[Midnight Commander]] |Two-panel terminal-based file manager. |- |nnn |Fast and lightweight terminal-based file manager. |- |ranger |Terminal-based file manager with vi-style keybindings. |- |yazi |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[https://github.com/KDE/krita Krita] |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |[https://github.com/RodZill4/material-maker Material Maker] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |[[nano]] |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[vim]] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Description !Focus |- |Code::Blocks |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} 51cf84d2a9bfa3227e7c8a4634a0cc4dbf3bcc27 0 1201 5019 2026-05-24T03:32:56Z ExaltedToast 386 init wikitext text/x-wiki Hannah Montana Linux is a [[Meme Linux Distributions|Meme Linux Distribution]] based on [[Kubuntu]] with a Hannah Montana-themed [[Ricing|Rice]] of [[KDE|KDE 4.2]]. It was released in 2008 by an anonymous developer and hasn't received updates since. 2962aebc87ecaa2450ceac0e692e110e18401370 0 1202 5020 2026-05-24T03:34:18Z ExaltedToast 386 init wikitext text/x-wiki Meme [[Linux Distributions]] are distributions that either were created as jokes, or became jokes over time, and are rarely seriously run. Popular examples include [[Nyarch]] and [[Hannah Montana Linux]]. b66a06ea9479d59e499a2523c63f1d77b12f8d7c 5022 5020 2026-05-24T03:36:23Z ExaltedToast 386 add uwuntu as example wikitext text/x-wiki Meme [[Linux Distributions]] are distributions that either were created as jokes, or became jokes over time, and are rarely seriously run. Popular examples include [[Nyarch]], [[UwUntu]], and [[Hannah Montana Linux]]. 302a91eb885c0801f9013f9996402e7571c2c0a6 0 1201 5021 5019 2026-05-24T03:34:41Z ExaltedToast 386 add an abbreviation wikitext text/x-wiki Hannah Montana Linux, also known as HML, is a [[Meme Linux Distributions|Meme Linux Distribution]] based on [[Kubuntu]] with a Hannah Montana-themed [[Ricing|Rice]] of [[KDE|KDE 4.2]]. It was released in 2008 by an anonymous developer and hasn't received updates since. a4f6dea0c2c237eefe31aef2a3895fa771debb47 6 1203 5023 2026-05-24T04:05:59Z 2elevation 115 wikitext text/x-wiki The Oreon logo, used starting in 2026 4068279b67f28fdb106e306f1be2fcd1ca37af1a 6 1204 5024 2026-05-24T04:09:06Z 2elevation 115 wikitext text/x-wiki Oreon 10 default desktop, last changed in March 2025 with Oreon 10 (Build 2504) and still looks the same today 4495c14790ab8f715ec393c28be1305005e48654 0 480 5025 3655 2026-05-24T04:55:03Z 2elevation 115 Revamp/update Oreon page and fix references wikitext text/x-wiki {{DistributionInfobox |title=Oreon Linux |image=[[File:OreonLogo_2026.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop, Server |architectures = aarch64, x86_64 |website=[https://oreonhq.com/ oreonhq.com]}} [[Category:Linux Distributions]] [[File:Oreon 10 desktop.png|thumb|Oreon 10 default desktop since Build 2504 running GNOME]] '''Oreon Linux''' is a [[Linux Distributions|Linux Distribution]] developed by Oreon HQ. Originally based on AlmaLinux, the project modifies its enterprise base to provide a practical, out-of-the-box desktop experience, importing missing system packages from [[Fedora|Fedora Linux]].<ref>[https://copr.fedorainfracloud.org/coprs/brandonlester/oreon-10/ brandonlester/oreon-10 Copr Repository], Fedora Copr (Accessed: 2026-05-23)</ref> === History === The first release, ''Oreon Lime (R1/R1.1)'', launched on January 1, 2024.<ref>[https://oreonhq.com/blog/oreon-lime-r1-lifecycle/ Oreon Lime R1/R1.1 Lifecycle], Oreon HQ Blog (Accessed: 2025-08-09)</ref> It was replaced on February 18, 2024, by ''Oreon Lime (R2)'', which moved the base to AlmaLinux for long-term support capabilities.<ref>[https://wiki.oreonhq.com/docs/Support-Timelines/oreon-lime-r2-support-timeline Oreon Lime (R2) Support Timeline], Oreon Wiki (Accessed: 2026-05-23)</ref> This early release shipped with GNOME 40 and Linux kernel 5.14, receiving coverage from outlets like ''The Register''.<ref>[https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/ Oreon Lime is AlmaLinux with a desktop twist], Liam Proven, The Register, 2024-08-20</ref> ==== Oreon 10 Build Cycle ==== Oreon 10 officially launched on December 12, 2024, with the original release (Build 2412), introducing KDE Plasma 6 alongside Linux kernel 6.11, which updated to kernel 6.12 shortly after. Incremental system updates and maintenance fixes are pushed through a build-number system formatted as the first two digits of the year followed by the month.<ref>[https://wiki.oreonhq.com/docs/Support-Timelines/oreon-10-support-timeline Oreon 10 Support Timeline], Oreon Wiki (Accessed: 2026-05-23)</ref> Build 2501 launched on January 1, 2025, followed by Build 2502 on February 12, 2025. Build 2503 released shortly after on February 28, 2025. Build 2504 was pushed on March 13, 2025, which switched the default desktop choice back to GNOME following user criticism regarding the interface shift. Later maintenance milestones included Build 2507 on July 14, 2025, and Build 2510 on October 12, 2025. The cycle continued into the following year with Build 2602 on February 9, 2026. The current supported build for Oreon 10 is Build 2603, which released on March 1, 2026, and replaced the older Anaconda installer with a custom installer called Centrio while changing several other default configurations.<ref>[https://distrowatch.com/?newsid=12744 Oreon 10-2603 DistroWatch Announcement], Oreon HQ (Accessed: 2026-05-23)</ref> === Future Development === Following updates from the Oreon team and coverage by BetaNews, development focus has moved toward the next major release, Oreon 11. The upcoming release will drop its reliance on AlmaLinux entirely. Instead, the distribution is moving toward becoming an independent RPM-based Linux distribution to gain direct control over its repository infrastructure and package availability, targeting a better release cycle and separate package branches.<ref>[https://betanews.com/article/oreon-11/ Oreon 11 could be the Linux OS that helps you leave Microsoft Windows for good], BetaNews (Accessed: 2026-05-23)</ref> To back this infrastructure independence, Oreon HQ secured major hosting partnerships. The Oregon State University Open Source Lab joined as a sponsor in May 2026 to help host the new Oreon Build Service and power part of the Oreon mirror network, providing dedicated high-performance servers.<ref>[https://osuosl.org/communities/ OSU OSL Communities Ecosystem], Oregon State University Open Source Lab (Accessed: 2026-05-23)</ref> This followed a network infrastructure sponsorship formed with Cloudflare in July 2025. == References == <references /> 2a9bdc5259f31bcc9f536df5dd97ba976ef0b7bf 2 1186 5026 4960 2026-05-24T08:10:11Z Rob Kam 380 wikitext text/x-wiki * [https://github.com/robkam/ytree Ytree: a File Manager for Unix-like Systems] 482f6bafe391b0b60ef5f3019480445496a3002c 6 1205 5027 2026-05-24T09:34:19Z Habaja1 377 The logo for KDE Neon, a distro based on Ubuntu LTS developed by the KDE team. wikitext text/x-wiki == Summary == The logo for KDE Neon, a distro based on Ubuntu LTS developed by the KDE team. == Licensing == {{CC-BY-SA-4.0}} 486fcba5fac12d69f1910c11240a01fd1828bccf 5028 5027 2026-05-24T09:35:22Z Habaja1 377 Habaja1 uploaded a new version of [[File:KDE-Neon-logo.png]] wikitext text/x-wiki == Summary == The logo for KDE Neon, a distro based on Ubuntu LTS developed by the KDE team. == Licensing == {{CC-BY-SA-4.0}} 486fcba5fac12d69f1910c11240a01fd1828bccf 5029 5028 2026-05-24T09:36:44Z Habaja1 377 Habaja1 uploaded a new version of [[File:KDE-Neon-logo.png]] wikitext text/x-wiki == Summary == The logo for KDE Neon, a distro based on Ubuntu LTS developed by the KDE team. == Licensing == {{CC-BY-SA-4.0}} 486fcba5fac12d69f1910c11240a01fd1828bccf 0 1206 5030 2026-05-24T09:37:08Z Habaja1 377 Created KDE Neon page wikitext text/x-wiki KDE Neon is a [[Linux Distributions|linux distribution]] based on [[Ubuntu|Ubuntu LTS]] developed by the KDE team. {{DistributionInfobox|title=KDE Neon|image=[[File:KDE-Neon-logo.png]]|caption=The KDE Neon logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]]|defaultdesktops=KDE Plasma|usagetype=Desktop|architectures=x86_64|website=[https://neon.kde.org/index&#124; KDE Neon]|Written in=C, C++, QT 6}} de608baf59fa9e75436d935b77873b7540efee15 5031 5030 2026-05-24T09:49:18Z Habaja1 377 wikitext text/x-wiki KDE Neon is a [[Linux Distributions|linux distribution]] based on [[Ubuntu|Ubuntu LTS]] developed by the [[KDE]] team, wich provides users with the latest features of the [[Plasma|KDE Plasma]] desktop environment. It is essentially the testing ground where new KDE Plasma updates are tested and used before being introduced to other distros using KDE Plasma (Much like how [[Fedora]] is [[Red Hat Enterprise Linux|RHEL]]'s testing ground). However, apart from the KDE Plasma desktop, the distro itself follows the stable release schedule of [[Ubuntu|Ubuntu LTS.]] because it is developed by the KDE developers, it can be seen as a "pure" KDE Plasma experience. {{DistributionInfobox|title=KDE Neon|image=[[File:KDE-Neon-logo.png]]|caption=The KDE Neon logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]], PackageKit|defaultdesktops=KDE Plasma|usagetype=Desktop|architectures=x86_64|website=[https://neon.kde.org/index&#124; KDE Neon]|Written in=C, C++, QT 6}} == History == == Features == == Installation == == Refrences == 2b177ce5ff98eb5fa783b7bb87d01e3052162af7 5039 5031 2026-05-24T10:12:21Z Habaja1 377 wikitext text/x-wiki KDE Neon is a [[Linux Distributions|linux distribution]] based on [[Ubuntu|Ubuntu LTS]] developed by the [[KDE]] team, wich provides users with the latest features of the [[Plasma|KDE Plasma]] desktop environment<ref>{{Cite|url=https://neon.kde.org/faq#what-is-neon|title=KDE Neon's FAQ, What is KDE Neon question.|accessdate=2026/05/24}}</ref>. It is essentially the testing ground where new KDE Plasma updates are tested and used before being introduced to other distros using KDE Plasma (Much like how [[Fedora]] is [[Red Hat Enterprise Linux|RHEL]]'s testing ground). However, apart from the KDE Plasma desktop, the distro itself follows the stable release schedule of [[Ubuntu|Ubuntu LTS]], making it a half stable half rolling distro. because it is developed by the KDE developers, it can be seen as a "pure" KDE Plasma experience. {{DistributionInfobox|title=KDE Neon|image=[[File:KDE-Neon-logo.png]]|caption=The KDE Neon logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]], PackageKit|defaultdesktops=KDE Plasma|usagetype=Desktop|architectures=x86_64|website=[https://neon.kde.org/index&#124; KDE Neon]|Written in=C, C++, QT 6}} == History == KDE neon first started taking shape in late 2015 as a way to provide a rolling release of fresh KDE software on top of [[Ubuntu]]'s stable OS base. The first daily installation images began being built in January 2016. The first general release of KDE Neon was on 8 June 2016, it was based on an [[Ubuntu]] 16.04 base, using [[Plasma|KDE Plasma]] 5.6. The Latest version of KDE Neon, 6.6, was released on 16 February 2026. [[File:KDE-Neon-6.6-big.png|thumb|A fresh installation of KDE Neon 6.6.]] == Features == KDE Neon == Installation == == References == 0e6b3ba6893ae773fe33b073b44740100fda8f6d 5040 5039 2026-05-24T10:33:21Z Habaja1 377 wikitext text/x-wiki KDE Neon is a [[Linux Distributions|linux distribution]] based on [[Ubuntu|Ubuntu LTS]] developed by the [[KDE]] team, wich provides users with the latest features of the [[Plasma|KDE Plasma]] desktop environment<ref>{{Cite|url=https://neon.kde.org/faq#what-is-neon|title=KDE Neon's FAQ, What is KDE Neon question.|accessdate=2026/05/24}}</ref>. It is essentially the testing ground where new KDE Plasma updates are tested and used before being introduced to other distros using KDE Plasma (Much like how [[Fedora]] is [[Red Hat Enterprise Linux|RHEL]]'s testing ground). However, apart from the KDE Plasma desktop, the distro itself follows the stable release schedule of [[Ubuntu|Ubuntu LTS]], making it a half stable half rolling distro<ref>{{Cite|url=https://neon.kde.org/faq#is-it-rolling|title=Official statement in the KDE Neon FAQ on this.|accessdate=2026/05/26}}</ref>. because it is developed by the KDE developers, it can be seen as a "pure" KDE Plasma experience. {{DistributionInfobox|title=KDE Neon|image=[[File:KDE-Neon-logo.png]]|caption=The KDE Neon logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]], PackageKit|defaultdesktops=KDE Plasma|usagetype=Desktop|architectures=x86_64|website=[https://neon.kde.org/index&#124; KDE Neon]|Written in=C, C++, QT 6}} == History == KDE neon first started taking shape in late 2015 as a way to provide a rolling release of fresh KDE software on top of [[Ubuntu]]'s stable OS base. The first daily installation images began being built in January 2016. The first general release of KDE Neon was on 8 June 2016, it was based on an [[Ubuntu]] 16.04 base, using [[Plasma|KDE Plasma]] 5.6. The Latest version of KDE Neon, 6.6, was released on 16 February 2026. [[File:KDE-Neon-6.6-big.png|thumb|A fresh installation of KDE Neon 6.6.]] == Features == KDE Neon == Installation == KDE Neon uses the [[Calamares]] installer. Specifications for installation are: {| class="wikitable" |+ ! !Minimum !Recommended ! |- |Proccesor |1 GHz X86-64 CPU |2 GHz Dual-Core X86-64 CPU Or higher | |- |RAM |2GB |4GB and higher | |- |Storage |20 GB |40 GB and higher | |} Note that these minimum specs will just get you to run it at the bare minimum == References == f427e98ef5c89a34e818b3c2136cef6c294541bd 0 1167 5032 4905 2026-05-24T09:54:29Z Habaja1 377 added some sauce wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a [[Debian]] derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian without [[systemd]]. It was first released on 2016-05-03, with the first stable version being released on 2017-05-25. [[File:Devuan6-xfce.png|thumb|A Devuan installation running Xfce]] == History == On 25 April 2015, [[Debian]] 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing [[sysvinit]], [[upstart]], and other init systems with [[systemd]] by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a [[Debian]] fork of what would become Devuan, aiming to provide people with the choice to other init systems again. The first stable release was released on 2017-05-25, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments ([[XFCE]], [[Cinnamon]], [[Plasma|KDE]], [[LXQt]], [[MATE]]) at install time, also providing installation options for choosing between [[sysvinit]] and [[OpenRC]] for init, and between [[GRUB]] and [[LILO]] for the boot loader, for the first time.<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems, according to the Devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Devuan uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from Debian that require [[systemd]] to systemd-less packages. While it is possible to use Debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from Devuan's website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Experimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making a bootable USB and booting it. | | |} Devuan is a [[Debian]] fork; therefore, the same minimum and recommended requirements also apply to Devuan. However, it is somewhat lighter than Debian, since it does not use systemd. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of Devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Trivia == * Unlike [[Debian]] who names it's stable releases after Toy Story characters, Devuan's stable updates are named after minor planets and asteroids. * Unlike [[Gentoo]] wich still gives the option to install and use [[Systemd]], devuan has absolutely no option to do this. == References == 0168e4d6c29837d7ddd2769b58933c4a6f876bb4 5033 5032 2026-05-24T09:54:54Z Habaja1 377 wikitext text/x-wiki {{DistributionInfobox|title=Devuan|image=[[File:Devuan-logo.png]]|caption=The Devuan logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[apt]]|defaultdesktops=Xfce|usagetype=Desktop, Server|architectures=amd64, arm64, armel, armhf, and ppc64el|website=[https://www.devuan.org/]}} '''Devuan''' ( /ˈdɛv.wʌn//), is a [[Debian]] derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian without [[systemd]]. It was first released on 2016-05-03, with the first stable version being released on 2017-05-25. [[File:Devuan6-xfce.png|thumb|A Devuan installation running Xfce]] == History == On 25 April 2015, [[Debian]] 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing [[sysvinit]], [[upstart]], and other init systems with [[systemd]] by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a [[Debian]] fork of what would become Devuan, aiming to provide people with the choice to other init systems again. The first stable release was released on 2017-05-25, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments ([[XFCE]], [[Cinnamon]], [[Plasma|KDE]], [[LXQt]], [[MATE]]) at install time, also providing installation options for choosing between [[sysvinit]] and [[OpenRC]] for init, and between [[GRUB]] and [[LILO]] for the boot loader, for the first time.<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems, according to the Devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Devuan uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from Debian that require [[systemd]] to systemd-less packages. While it is possible to use Debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from Devuan's website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Experimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making a bootable USB and booting it. | | |} Devuan is a [[Debian]] fork; therefore, the same minimum and recommended requirements also apply to Devuan. However, it is somewhat lighter than Debian, since it does not use systemd. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of Devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Trivia == * Unlike [[Debian]] who names it's stable releases after Toy Story characters, Devuan's stable releases are named after minor planets and asteroids. * Unlike [[Gentoo]] wich still gives the option to install and use [[Systemd]], devuan has absolutely no option to do this. == References == 7b7f3b0ead8dfb4bde9c0ece572a1f8c2a8f710c 0 396 5034 5017 2026-05-24T10:02:10Z DE-ZMK 373 Added Media category wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Description !DE |- |Discover |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Description !Distribution |- |[[pacman]] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Description |- |[[Midnight Commander]] |Two-panel terminal-based file manager. |- |nnn |Fast and lightweight terminal-based file manager. |- |ranger |Terminal-based file manager with vi-style keybindings. |- |yazi |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Description |- |[https://www.gimp.org/ GIMP] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[https://github.com/KDE/krita Krita] |Raster drawing program developed by KDE. |- |[https://libresprite.github.io/#!/ LibreSprite] |Open source program for creating and animating sprites. |- |[https://pixieditor.net/ PixiEditor] |Node-based sprite creation software. |- |[https://github.com/RodZill4/material-maker Material Maker] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Description |- |[https://mpv.io/ mpv] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |[[nano]] |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[vim]] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Description !Focus |- |Code::Blocks |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} d09e6059ecc05c4a3176b357687e28179f665140 5049 5034 2026-05-24T13:39:42Z ZeliotL 375 added link section for all raster image programs wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Description !DE |- |Discover |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Description !Distribution |- |[[pacman]] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Description |- |LibreOffice |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Description |- |KeePassXC |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Description |- |[[Midnight Commander]] |Two-panel terminal-based file manager. |- |nnn |Fast and lightweight terminal-based file manager. |- |ranger |Terminal-based file manager with vi-style keybindings. |- |yazi |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Description |- |Inkscape |Vector image editor, good for editing SVG files. |- |Graphite |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Description |- |[https://mpv.io/ mpv] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Description |- |Blender |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Description |- |Geany |A powerful, stable and lightweight programmer's text editor. |- |Kate |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Description |- |[[nano]] |Simple terminal text editor that comes with most distributions |- |[[vi]] |A keyboard based terminal text editor |- |[[vim]] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Description !Focus |- |Code::Blocks |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Description |- |Godot |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Description |- |LibreAim |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Description |- |[https://github.com/FluxerApp Fluxer] |Instant messaging and VoIP platform built for friends, groups, and communities |} a7640af61a27971cfb9147e7452b1667858e3fd6 5055 5049 2026-05-24T13:48:10Z ZeliotL 375 added links column to all categories wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover | |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice | |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] |Two-panel terminal-based file manager. |- |nnn | |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi | |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender | |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot | |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |[https://github.com/FluxerApp Fluxer] | |Instant messaging and VoIP platform built for friends, groups, and communities |} c6eb00847fcecfc7e7f604e5ccabbcf17925c413 5056 5055 2026-05-24T13:48:27Z ZeliotL 375 /* Terminal-based file managers */ wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover | |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice | |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn | |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi | |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender | |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot | |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |[https://github.com/FluxerApp Fluxer] | |Instant messaging and VoIP platform built for friends, groups, and communities |} 9699ba1289cd29063248a597c958a2ec1b3d85f9 5057 5056 2026-05-24T13:49:44Z ZeliotL 375 /* Movie makers/video editors */ wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover | |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice | |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn | |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi | |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender | |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot | |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |[https://github.com/FluxerApp Fluxer] | |Instant messaging and VoIP platform built for friends, groups, and communities |} 410ec243b6f11c588f2188bc9efd9da0fa94227f 5058 5057 2026-05-24T13:52:38Z ZeliotL 375 added website to fluxer wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover | |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice | |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn | |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi | |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender | |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot | |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} 1fc098477c026baaabf5a870149e2f5daaa7eab6 5060 5058 2026-05-24T13:53:23Z ZeliotL 375 /* Engines */ wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover | |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice | |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn | |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi | |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender | |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} 16aaa4cbca2779b1a3a3a819535efa64d86cfffc 5062 5060 2026-05-24T13:54:03Z ZeliotL 375 /* 3D modelling and animation */ wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover | |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice | |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn | |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi | |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} ed2bd57c3b8be1bc0e2bda0b3ec983e00314bf9f 5063 5062 2026-05-24T13:56:04Z ZeliotL 375 /* Text editors */ wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover | |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice | |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn | |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi | |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code | |OSS (Visual Studio Code) - An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} 18213c268a634bc5591c03aeea5546108a755a52 5068 5063 2026-05-24T14:09:13Z Uniolo 345 Added encryption under misc, we would have had to create a misc category at one point anyways. Might want to move social there since it only has one app currently. wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover | |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice | |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn | |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi | |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code | |OSS (Visual Studio Code) - An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} == Miscellaneous == software categories that font fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !Links !Description |- |[[GnuPG]] | |Open source PGP encryption implementation. |- |[[Age]] | |Simple asymmetric and symmetric file encryption protocal. |- |[[Cryptsetup]] | |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |} 2cc74d4a2ec35ea78820c3f47334fb9a1f4df494 6 1207 5035 2026-05-24T10:06:55Z Habaja1 377 wikitext text/x-wiki An example photo of KDE Neon 6-6. (Small) f02d29d5ab963079d38922a5f6de43d5cc4864ca 6 1208 5036 2026-05-24T10:08:47Z Habaja1 377 wikitext text/x-wiki An Example picture of KDE Neon 6.6. (Bigger) 7531d5fe7d62ea3053462f8d4eb7a60956edfeb0 2 1209 5037 2026-05-24T10:10:55Z Hyperreal 388 Created page with "FOSS geek, privacy advocate, digital archivist, gamer, autistic [https://en.wikipedia.org/wiki/Schizotypy schizotype] * GPG: E6AAEAC9BAF03ABE0B0861F6FDBEB7D214D5BBEF * [https://keyoxide.org/hyperreal%40moonshadow.dev Keyoxide] == Web == * Main website: https://moonshadow.dev * Blog: https://blog.moonshadow.dev * Gists: https://gists.moonshadow.dev * Code: https://radicle.defelo.de/nodes/seed.moonshadow.dev * Other code: https://tildegit.org/hyperreal * GitHub: https:/..." wikitext text/x-wiki FOSS geek, privacy advocate, digital archivist, gamer, autistic [https://en.wikipedia.org/wiki/Schizotypy schizotype] * GPG: E6AAEAC9BAF03ABE0B0861F6FDBEB7D214D5BBEF * [https://keyoxide.org/hyperreal%40moonshadow.dev Keyoxide] == Web == * Main website: https://moonshadow.dev * Blog: https://blog.moonshadow.dev * Gists: https://gists.moonshadow.dev * Code: https://radicle.defelo.de/nodes/seed.moonshadow.dev * Other code: https://tildegit.org/hyperreal * GitHub: https://github.com/hyperreal64 == Socials == * [https://bsky.app/profile/hyperreal.at.moonshadow.dev Bluesky] * [https://discordapp.com/users/263927928595808257 Discord] * [https://tilde.zone/@hyperreal Fediverse (Mastodon)] * [https://reddit.com/user/SchizoidArchivist Reddit] * [https://signal.me/#eu/UEc0iZQ4f_2sCKN0JPz7DkP48QpdHcU2LENa0dLmbnx4D1XENahJp7q-oaP_gsNS Signal] * [xmpp://hyperreal@tilde.team XMPP] 6526601f77181d6e0b82022a5d392814366990bc 6 1210 5038 2026-05-24T10:11:12Z Habaja1 377 bigger version of KDE-Neon 6.6 example picture. wikitext text/x-wiki == Summary == bigger version of KDE-Neon 6.6 example picture. == Licensing == {{Unknown_copyright}} d4a180c8207444b016c4d32d5519b8b132c29388 0 1091 5041 4929 2026-05-24T12:17:24Z Atmois 13 Atmois moved page [[MangoWC]] to [[MangoWM]]: Project renamed wikitext text/x-wiki {{Work In Progress}} {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox |caption=MangoWM logo |developers=MangoWM developers |firstrelease=0.1.1, 2025-02-17 |languages=[[C]] |lastrelease=V0.13.1, 2026-05-18 |title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io] |releasestatus=Maintained |image=[[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formally known as MangoWC) is a [[Wayland]] compositor based on [[dwl]] that keeps its lightweight, suckless-style design while adding more practical features.I think it looks alright. While staying minimal and fast to build, MangoWM improves on usability with better layouts, multi-monitor supports, and broader wayland compatibility. === Highlighted Features: === * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. ==== Additional Features: ==== * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag === Installation: === ===== AerynOS: ===== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ===== Arch: ===== Using yay: <syntaxhighlight lang="bash"> yay -S mangowm </syntaxhighlight> or for the latest git version: <syntaxhighlight lang="bash"> yay -S mango-git </syntaxhighlight> Using paru: <syntaxhighlight lang="bash"> paru -S mangowm </syntaxhighlight> or for the latest git version: <syntaxhighlight lang="bash"> paru -S mango-git </syntaxhighlight> ===== Fedora: ===== First we need to add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then, install it with dnf: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ===== Gentoo: ===== Firstly we add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Followed by unmasking of these packages in your package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ===== Guix System: ===== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ===== NixOS: ===== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref>. ===== PikaOS: ===== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> === Building from source: === Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ===== Dependencies: ===== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ===== Building wlroots from source: ===== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ===== Building scenefx from source: ===== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building MangoWM from source: ==== At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 8e3bf1db6c156d6bc26fa682e571b130268b6cf6 0 1211 5042 2026-05-24T12:17:25Z Atmois 13 Atmois moved page [[MangoWC]] to [[MangoWM]]: Project renamed wikitext text/x-wiki #REDIRECT [[MangoWM]] 4778b151955a0b89bb198470c6afef81c7149425 2 1059 5043 4332 2026-05-24T12:18:07Z Alxhr0 265 Correct contact info wikitext text/x-wiki == About: == Howdy, I'm Rafeal! (Alxhr0) I like coding silly things and contributing! * '''Pronouns:''' They/them * '''Location:''' Poland == Contact: == Feel free to contact me through email or ping me on the NGL/FOSS Wiki Discord 7097cd97ea878d370b3b4d49770e1a4993a51563 0 1212 5044 2026-05-24T12:38:00Z SimonPayant 384 Added an introduction paragraph and a "Controversies and Criticism" section. wikitext text/x-wiki Firefox (officially Mozilla Firefox) is a free and open-source web browser developed by the [[Mozilla]] Foundation and it's subsidiary, the [[Mozilla]] Corporation. It was released on November 9, 2004<ref>{{Cite|url=https://doi.org/10.7717/peerj-cs.28|title=The rise of Chrome|author=Jonathan Tamary, Dror G. Feitelson|year=2015|accessdate=May 24, 2026}}</ref> and serves as a successor to the [[Netscape]] Navigator after [[Netscape]] released its source code to the open-source community in the late 1990s<ref>{{Cite|url=https://nominet.uk/wp-content/uploads/2024/09/25-years-of-the-web-report.pdf|title=The story of the web|author=Jack Schofield|year=2024|accessdate=May 24, 2026}}</ref>. Firefox famously launched to provide a secure, user-centric alternative during the height of the "browser wars" against proprietary dominance<ref>{{Cite|url=https://doi.org/10.1016/j.intmar.2009.04.008|title=CASE: Mozilla vs. Godzilla — The Launch of the Mozilla Firefox Browser|author=Sandeep Krishnamurthy|year=2009|accessdate=May 24, 2026}}</ref>. Today, it stands out as one of the few major independant browsers that does not rely on Google's [[Chromium]] rendering engine, instead utilizing its own open-source engine, [[Gecko]]<ref>{{Cite|url=https://doi.org/10.48009/2_iis_2007_478-483|title=INTERNET EXPLORER AND FIREFOX: WEB BROWSER FEATURES COMPARISION AND THEIR FUTURE|author=Siwat Saibua, Joon-Yeoul Oh, Richard A. Aukerman|year=2007|accessdate=May 24, 2026}}</ref>. == Controversies and Criticism == === 2025 Terms of Service and Data Licensing Backlash === On February 27, 2025, [[Mozilla]] introducted their new official Firefox Terms of Use and updated it's Privacy Notice<ref name=":0">{{Cite|url=https://www.zdnet.com/article/the-firefox-i-loved-is-gone-how-to-protect-your-privacy-on-it-now/|title=The Firefox I loved is gone - how to protect your privacy on it now|author=Steven Vaughan-Nichols|year=2025|accessdate=May 24, 2026}}</ref>. That meant that for the first time, [[Mozilla]] had a legally binding privacy policy for Firefox users<ref name=":0" />. This change received a lot of backlash from privacy advocates and so [[Mozilla]] changed their Firefox terms again after the backlash<ref>{{Cite|url=https://thehackernews.com/2025/03/mozilla-updates-firefox-terms-again.html|title=Mozilla Updates Firefox Terms Again After Backlash Over Broad Data License Language|author=Ravie Lakshmanan|year=2025|accessdate=May 24, 2026}}</ref>. [[Mozilla]] changed "''When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox.''" to "''You give Mozilla the rights necessary to operate Firefox. This includes processing your data as we describe in the Firefox Privacy Notice. It also includes a nonexclusive, royalty-free, worldwide license for the purpose of doing as you request with the content you input in Firefox. This does not give Mozilla any ownership in that content.''"<ref>{{Cite|url=https://www.mozilla.org/en-US/about/legal/terms/firefox/#you-give-mozilla-certain-rights-and-permissions|title=Firefox Terms of Use|author=Mozilla|year=2025|accessdate=May 24, 2026}}</ref> 9323afc1e0b286764da8dfef457c09161851fd98 5045 5044 2026-05-24T12:40:14Z SimonPayant 384 Fixed Mozilla links wikitext text/x-wiki Firefox (officially Mozilla Firefox) is a free and open-source web browser developed by the [[Mozilla Foundation]] and it's subsidiary, the [[Mozilla Corporation]]. It was released on November 9, 2004<ref>{{Cite|url=https://doi.org/10.7717/peerj-cs.28|title=The rise of Chrome|author=Jonathan Tamary, Dror G. Feitelson|year=2015|accessdate=May 24, 2026}}</ref> and serves as a successor to the [[Netscape]] Navigator after [[Netscape]] released its source code to the open-source community in the late 1990s<ref>{{Cite|url=https://nominet.uk/wp-content/uploads/2024/09/25-years-of-the-web-report.pdf|title=The story of the web|author=Jack Schofield|year=2024|accessdate=May 24, 2026}}</ref>. Firefox famously launched to provide a secure, user-centric alternative during the height of the "browser wars" against proprietary dominance<ref>{{Cite|url=https://doi.org/10.1016/j.intmar.2009.04.008|title=CASE: Mozilla vs. Godzilla — The Launch of the Mozilla Firefox Browser|author=Sandeep Krishnamurthy|year=2009|accessdate=May 24, 2026}}</ref>. Today, it stands out as one of the few major independant browsers that does not rely on [[Google]]'s [[Chromium]] rendering engine, instead utilizing its own open-source engine, [[Gecko]]<ref>{{Cite|url=https://doi.org/10.48009/2_iis_2007_478-483|title=INTERNET EXPLORER AND FIREFOX: WEB BROWSER FEATURES COMPARISION AND THEIR FUTURE|author=Siwat Saibua, Joon-Yeoul Oh, Richard A. Aukerman|year=2007|accessdate=May 24, 2026}}</ref>. == Controversies and Criticism == === 2025 Terms of Service and Data Licensing Backlash === On February 27, 2025, [[Mozilla]] introducted their new official Firefox Terms of Use and updated it's Privacy Notice<ref name=":0">{{Cite|url=https://www.zdnet.com/article/the-firefox-i-loved-is-gone-how-to-protect-your-privacy-on-it-now/|title=The Firefox I loved is gone - how to protect your privacy on it now|author=Steven Vaughan-Nichols|year=2025|accessdate=May 24, 2026}}</ref>. That meant that for the first time, [[Mozilla]] had a legally binding privacy policy for Firefox users<ref name=":0" />. This change received a lot of backlash from privacy advocates and so [[Mozilla]] changed their Firefox terms again after the backlash<ref>{{Cite|url=https://thehackernews.com/2025/03/mozilla-updates-firefox-terms-again.html|title=Mozilla Updates Firefox Terms Again After Backlash Over Broad Data License Language|author=Ravie Lakshmanan|year=2025|accessdate=May 24, 2026}}</ref>. [[Mozilla]] changed "''When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox.''" to "''You give Mozilla the rights necessary to operate Firefox. This includes processing your data as we describe in the Firefox Privacy Notice. It also includes a nonexclusive, royalty-free, worldwide license for the purpose of doing as you request with the content you input in Firefox. This does not give Mozilla any ownership in that content.''"<ref>{{Cite|url=https://www.mozilla.org/en-US/about/legal/terms/firefox/#you-give-mozilla-certain-rights-and-permissions|title=Firefox Terms of Use|author=Mozilla|year=2025|accessdate=May 24, 2026}}</ref> 13283c310af62c9c05447046148d67948cab717f 0 1213 5046 2026-05-24T12:47:56Z Uniolo 345 Create "cryptsetup" with sidebar and some information, work in progress. Note that if I remove the "website" field from the sidebar, it breaks (so I just link to the gitlab). wikitext text/x-wiki {{Work In Progress}} {{stub|date=may 2026}} {{SoftwareInfobox |title=Cryptsetup |releasestatus=Maintained |lastrelease=2.8.6, Apr 2, 2026 |firstrelease=1.0.7, Jul 22, 2009 |languages=[[C]] |developers=[https://research.redhat.com/blog/article-author/milan-broz/ Milan Brož] |website=[https://gitlab.com/cryptsetup gitlab.com/cryptsetup] }} '''Cryptsetup''' is a tool for configuring, managing, opening, and closing encrypted storage devices. It is mostly used for the encryption of USBs and drives. 4e864bdb4eb4f2911267ffce78724c78148148c6 5048 5046 2026-05-24T13:35:11Z Uniolo 345 Created "How to use" with USB devices guide and a guide for drives. Work in progress, tryna get feedback. wikitext text/x-wiki {{Work In Progress}} {{stub|date=may 2026}} {{SoftwareInfobox |title=Cryptsetup |releasestatus=Maintained |lastrelease=2.8.6, Apr 2, 2026 |firstrelease=1.0.7, Jul 22, 2009 |languages=[[C]] |developers=[https://research.redhat.com/blog/article-author/milan-broz/ Milan Brož] |website=[https://gitlab.com/cryptsetup gitlab.com/cryptsetup] }} '''Cryptsetup''' is a tool for configuring, managing, opening, and closing encrypted LUKS storage devices. It is mostly used for the encryption of USBs and drives. LUKS (what cryptsetup uses behind the scenes) uses AES by default with a 512 bit keysize<ref>{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref>. How AES works will not be discussed here due to it being technical and out of the scope of this article, there are many resources online about it however. LUKS is part of the [[Linux kernel]]. = How to use = {{Guide_Warning}} The following section provides commands and instructions on how to use cryptsetup, as this page is fairly short. === USB Devices === The most common use for cryptsetup. As USB devices are small and could be easily lost or stolen, it is recommended to encrypt USB devices if you only plan on accessing them on Linux, though there may be tools out there for accessing LUKS devices on non-[[Linux kernel|Linux]] systems. Note that the following instructions involve partitioning the USB, meaning, '''all data on it will be lost'''. Use this when creating a USB. Firstly, read the above warning, secondly, find the device you want to encrypt by running <code>lsblk</code>, the output should look something like this,<syntaxhighlight lang="output"> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 7.2G 0 disk ├─sda1 8:1 1 7.2G 0 part zram0 251:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 953.9G 0 disk ├─nvme0n1p1 259:1 0 600M 0 part /boot/efi ├─nvme0n1p2 259:2 0 2G 0 part /boot └─nvme0n1p3 259:3 0 951.3G 0 part /home / </syntaxhighlight>The exact names are probably different on your machine, but the most important part is the <code>/dev/sdX</code> device, for USBs it is most likely going to be an <code>sdX</code> device. Then the next step is to overwrite the USB. There are a few ways to do this. Everywhere you see <code>/dev/sdX</code> replace <code>/dev/sdX</code> with the name of your USB device as given by lsblk. First, if you want to be sure the data is gone and prevent an attacker from potentially guessing how much data is on the device, you can do: <code>sudo dd if=/dev/urandom of/dev/sdX bs=4M status=progress</code> after that ''optional'' step is done, you can move onto creating the partition, note that this step and the previous optional step, '''will erase all the data on the drive'''! There are several ways to do this, you can use a graphical tool like [[GParted]], But for fdisk, the instructions are simple, <code>fdisk /dev/sdX</code> Then run the <code>g</code> command to create a new GPT Partition, after that, you should run the <code>n</code> command to create a new partition, leave all the settings (like partition number and sectors) blank to use defaults, after you are done, run <code>w</code> to commit your changes to the USB and '''erase all data'''. After you are done that, its time to create the encrypted partition, run: <code>sudo cryptsetup luksFormat --verify-passphrase /dev/sdX1</code> Note that <code>/dev/sdX1</code> ends in a 1 to signify the first partition. Next, to open the device, run <code>sudo cryptsetup open /dev/sd</code><code>X1 usb</code> After that, the device with the unencrypted data will be in <code>/dev/mapper/usb</code>, now you can actually make the file system. If you want ext4, the traditional Linux file system, run: <code>sudo mkfs.ext4 /dev/mapper/usb</code> Otherwise, if you want btrfs, a more modern option, run: <code>sudo mkfs.btrfs /dev/mapper/usb</code> Now there is one more thing to do, mount the files. <code>sudo mount /dev/mapper/usb /mnt</code> Then you are done. The files are accessible in /mnt, though you might want to chown them so you have permissions. When it comes time to remove the USB you can simply unmount the drive by running <code>sudo umount /mnt</code> and then closing the LUKS device <code>sudo cryptsetup close usb</code> === Drives === This is setup by your distro installer during installation, if you are installing manually on a distro like [[Arch Linux|arch]], more or less the same things apply as USB drives. Never encrypt your <code>/boot</code> or <code>/boot/UEFI</code>, otherwise, your bootloader will be unable to load and your machine will be unbootable without an external USB. Only encrypt your <code>/</code>, <code>/home</code>, or other such data partitions. === Citations === c6133224aafb8d5fd7668cf72547dbec81cd95ca 5051 5048 2026-05-24T13:44:56Z Uniolo 345 [2/2] Seperate cryptsetup into a guide and a page with general info: link to the guide wikitext text/x-wiki {{Work In Progress}} {{stub|date=may 2026}} {{SoftwareInfobox |title=Cryptsetup |releasestatus=Maintained |lastrelease=2.8.6, Apr 2, 2026 |firstrelease=1.0.7, Jul 22, 2009 |languages=[[C]] |developers=[https://research.redhat.com/blog/article-author/milan-broz/ Milan Brož] |website=[https://gitlab.com/cryptsetup gitlab.com/cryptsetup] }} '''Cryptsetup''' is a tool for configuring, managing, opening, and closing encrypted LUKS storage devices. It is mostly used for the encryption of USBs and drives. LUKS (what cryptsetup uses behind the scenes) uses AES by default with a 512 bit keysize<ref>{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref>. How AES works will not be discussed here due to it being technical and out of the scope of this article, there are many resources online about it however. LUKS is part of the [[Linux kernel]]. One of the most common use of cryptsetup is creating an encrypted USB, for instructions on how to do that, refer to [[Guides:Creating a LUKS USB|this guide]]. 36b98f1578c469175c7885f5a1db41c5506b908e 5054 5051 2026-05-24T13:46:42Z Uniolo 345 Remove work in progress header wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |title=Cryptsetup |releasestatus=Maintained |lastrelease=2.8.6, Apr 2, 2026 |firstrelease=1.0.7, Jul 22, 2009 |languages=[[C]] |developers=[https://research.redhat.com/blog/article-author/milan-broz/ Milan Brož] |website=[https://gitlab.com/cryptsetup gitlab.com/cryptsetup] }} '''Cryptsetup''' is a tool for configuring, managing, opening, and closing encrypted LUKS storage devices. It is mostly used for the encryption of USBs and drives. LUKS (what cryptsetup uses behind the scenes) uses AES by default with a 512 bit keysize<ref>{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref>. How AES works will not be discussed here due to it being technical and out of the scope of this article, there are many resources online about it however. LUKS is part of the [[Linux kernel]]. One of the most common use of cryptsetup is creating an encrypted USB, for instructions on how to do that, refer to [[Guides:Creating a LUKS USB|this guide]]. cf9d6ca6db16048a54d93c7a9c8fee3d477d4173 5059 5054 2026-05-24T13:53:05Z Uniolo 345 Add to software category wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |title=Cryptsetup |releasestatus=Maintained |lastrelease=2.8.6, Apr 2, 2026 |firstrelease=1.0.7, Jul 22, 2009 |languages=[[C]] |developers=[https://research.redhat.com/blog/article-author/milan-broz/ Milan Brož] |website=[https://gitlab.com/cryptsetup gitlab.com/cryptsetup] }} '''Cryptsetup''' is a tool for configuring, managing, opening, and closing encrypted LUKS storage devices. It is mostly used for the encryption of USBs and drives. LUKS (what cryptsetup uses behind the scenes) uses AES by default with a 512 bit keysize<ref>{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref>. How AES works will not be discussed here due to it being technical and out of the scope of this article, there are many resources online about it however. LUKS is part of the [[Linux kernel]]. One of the most common use of cryptsetup is creating an encrypted USB, for instructions on how to do that, refer to [[Guides:Creating a LUKS USB|this guide]]. <references /> [[Category:Software]] a6aef6d563198a4f6a47ee4d9479742605f2b596 0 1184 5047 4952 2026-05-24T13:22:50Z Sparrow 362 fix: remove stray comma from DistrobutionInfobox wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{Stub}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Ffmpeg_logo.png|thumb]] | caption =The FFmpeg logo. | title = FFmpeg | releasestatus = Maintained | lastrelease = 8.1.1, 2026-05-04 | languages = C, C++, Assembly | developers = The FFmpeg Developers | website = [https://ffmpeg.org ffmpeg.org] }} '''FFmpeg''' is a free and open-source media suite used for converting, [[wikipedia:Transcoding|transcoding]], remuxing and editing video, audio, and other multimedia formats.<ref>{{Cite|url=https://ffmpeg.org/about.html|title=About FFmpeg · ffmpeg.org|author=FFmpeg Developers|accessdate=2026-05-23}}</ref> Because of its ability to convert from the most obscure formats, it has solidified itself in both propitiatory and open-source projects, notably [[Handbrake]] and [[Kdenlive]], and has also been used in streaming sites such as YouTube. == References == <references /> 61aefd2b786a74f0c0427fed3524f6c391de7983 3000 1214 5050 2026-05-24T13:43:39Z Uniolo 345 [1/2] Seperate "Cryptsetup" into a guide: create the guide wikitext text/x-wiki {{Work In Progress}} {{stub|date=may 2026}} = How to create a LUKS USB = {{Guide_Warning}} The following section provides commands and instructions on how to use cryptsetup to create a LUKS USB. The most common use for cryptsetup is to create an encrypted, As USB devices are small and could be easily lost or stolen, it is recommended to encrypt USB devices if you only plan on accessing them on Linux, though there may be tools out there for accessing LUKS devices on non-[[Linux kernel|Linux]] systems. Note that the following instructions involve partitioning the USB, meaning, '''all data on it will be lost'''. Use this when creating a USB. Firstly, read the above warning, secondly, find the device you want to encrypt by running <code>lsblk</code>, the output should look something like this,<syntaxhighlight lang="output"> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 7.2G 0 disk ├─sda1 8:1 1 7.2G 0 part zram0 251:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 953.9G 0 disk ├─nvme0n1p1 259:1 0 600M 0 part /boot/efi ├─nvme0n1p2 259:2 0 2G 0 part /boot └─nvme0n1p3 259:3 0 951.3G 0 part /home / </syntaxhighlight>The exact names are probably different on your machine, but the most important part is the <code>/dev/sdX</code> device, for USBs it is most likely going to be an <code>sdX</code> device. Then the next step is to overwrite the USB. There are a few ways to do this. Everywhere you see <code>/dev/sdX</code> replace <code>/dev/sdX</code> with the name of your USB device as given by lsblk. First, if you want to be sure the data is gone and prevent an attacker from potentially guessing how much data is on the device, you can do: <code>sudo dd if=/dev/urandom of/dev/sdX bs=4M status=progress</code> after that ''optional'' step is done, you can move onto creating the partition, note that this step and the previous optional step, '''will erase all the data on the drive'''! There are several ways to do this, you can use a graphical tool like [[GParted]], But for fdisk, the instructions are simple, <code>fdisk /dev/sdX</code> Then run the <code>g</code> command to create a new GPT Partition, after that, you should run the <code>n</code> command to create a new partition, leave all the settings (like partition number and sectors) blank to use defaults, after you are done, run <code>w</code> to commit your changes to the USB and '''erase all data'''. After you are done that, its time to create the encrypted partition, run: <code>sudo cryptsetup luksFormat --verify-passphrase /dev/sdX1</code> Note that <code>/dev/sdX1</code> ends in a 1 to signify the first partition. Next, to open the device, run <code>sudo cryptsetup open /dev/sd</code><code>X1 usb</code> After that, the device with the unencrypted data will be in <code>/dev/mapper/usb</code>, now you can actually make the file system. If you want ext4, the traditional Linux file system, run: <code>sudo mkfs.ext4 /dev/mapper/usb</code> Otherwise, if you want btrfs, a more modern option, run: <code>sudo mkfs.btrfs /dev/mapper/usb</code> Now there is one more thing to do, mount the files. <code>sudo mount /dev/mapper/usb /mnt</code> Then you are done. The files are accessible in /mnt, though you might want to chown them so you have permissions. When it comes time to remove the USB you can simply unmount the drive by running <code>sudo umount /mnt</code> and then closing the LUKS device <code>sudo cryptsetup close usb</code> === How to open and close the USB === After your done creating it, opening it is simple, just run<syntaxhighlight lang="bash"> sudo cryptsetup open /dev/sdX1 usb sudo mount /dev/mapper/usb /mnt </syntaxhighlight>And then you can close it just as easily,<syntaxhighlight lang="bash"> sudo umount /mnt sudo cryptsetup close usb </syntaxhighlight> 0b3d6525d4f320aabb982e3208d89f85a3e38b88 5052 5050 2026-05-24T13:45:34Z Uniolo 345 Fixed grammatical mistake wikitext text/x-wiki {{Work In Progress}} {{stub|date=may 2026}} = How to create a LUKS USB = {{Guide_Warning}} The following section provides commands and instructions on how to use cryptsetup to create a LUKS USB. One of the most common use for cryptsetup is to create an encrypted, As USB devices are small and could be easily lost or stolen, it is recommended to encrypt USB devices if you only plan on accessing them on Linux, though there may be tools out there for accessing LUKS devices on non-[[Linux kernel|Linux]] systems. Note that the following instructions involve partitioning the USB, meaning, '''all data on it will be lost'''. Use this when creating a USB. Firstly, read the above warning, secondly, find the device you want to encrypt by running <code>lsblk</code>, the output should look something like this,<syntaxhighlight lang="output"> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 7.2G 0 disk ├─sda1 8:1 1 7.2G 0 part zram0 251:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 953.9G 0 disk ├─nvme0n1p1 259:1 0 600M 0 part /boot/efi ├─nvme0n1p2 259:2 0 2G 0 part /boot └─nvme0n1p3 259:3 0 951.3G 0 part /home / </syntaxhighlight>The exact names are probably different on your machine, but the most important part is the <code>/dev/sdX</code> device, for USBs it is most likely going to be an <code>sdX</code> device. Then the next step is to overwrite the USB. There are a few ways to do this. Everywhere you see <code>/dev/sdX</code> replace <code>/dev/sdX</code> with the name of your USB device as given by lsblk. First, if you want to be sure the data is gone and prevent an attacker from potentially guessing how much data is on the device, you can do: <code>sudo dd if=/dev/urandom of/dev/sdX bs=4M status=progress</code> after that ''optional'' step is done, you can move onto creating the partition, note that this step and the previous optional step, '''will erase all the data on the drive'''! There are several ways to do this, you can use a graphical tool like [[GParted]], But for fdisk, the instructions are simple, <code>fdisk /dev/sdX</code> Then run the <code>g</code> command to create a new GPT Partition, after that, you should run the <code>n</code> command to create a new partition, leave all the settings (like partition number and sectors) blank to use defaults, after you are done, run <code>w</code> to commit your changes to the USB and '''erase all data'''. After you are done that, its time to create the encrypted partition, run: <code>sudo cryptsetup luksFormat --verify-passphrase /dev/sdX1</code> Note that <code>/dev/sdX1</code> ends in a 1 to signify the first partition. Next, to open the device, run <code>sudo cryptsetup open /dev/sd</code><code>X1 usb</code> After that, the device with the unencrypted data will be in <code>/dev/mapper/usb</code>, now you can actually make the file system. If you want ext4, the traditional Linux file system, run: <code>sudo mkfs.ext4 /dev/mapper/usb</code> Otherwise, if you want btrfs, a more modern option, run: <code>sudo mkfs.btrfs /dev/mapper/usb</code> Now there is one more thing to do, mount the files. <code>sudo mount /dev/mapper/usb /mnt</code> Then you are done. The files are accessible in /mnt, though you might want to chown them so you have permissions. When it comes time to remove the USB you can simply unmount the drive by running <code>sudo umount /mnt</code> and then closing the LUKS device <code>sudo cryptsetup close usb</code> === How to open and close the USB === After your done creating it, opening it is simple, just run<syntaxhighlight lang="bash"> sudo cryptsetup open /dev/sdX1 usb sudo mount /dev/mapper/usb /mnt </syntaxhighlight>And then you can close it just as easily,<syntaxhighlight lang="bash"> sudo umount /mnt sudo cryptsetup close usb </syntaxhighlight> 7b025ae4408d5b2eb6eb1ec6717365d8db680d03 5053 5052 2026-05-24T13:46:23Z Uniolo 345 Link to cryptsetup page wikitext text/x-wiki {{Work In Progress}} {{stub|date=may 2026}} = How to create a LUKS USB = {{Guide_Warning}} The following section provides commands and instructions on how to use [[cryptsetup]] to create a LUKS USB. One of the most common use for cryptsetup is to create an encrypted, As USB devices are small and could be easily lost or stolen, it is recommended to encrypt USB devices if you only plan on accessing them on Linux, though there may be tools out there for accessing LUKS devices on non-[[Linux kernel|Linux]] systems. Note that the following instructions involve partitioning the USB, meaning, '''all data on it will be lost'''. Use this when creating a USB. Firstly, read the above warning, secondly, find the device you want to encrypt by running <code>lsblk</code>, the output should look something like this,<syntaxhighlight lang="output"> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 7.2G 0 disk ├─sda1 8:1 1 7.2G 0 part zram0 251:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 953.9G 0 disk ├─nvme0n1p1 259:1 0 600M 0 part /boot/efi ├─nvme0n1p2 259:2 0 2G 0 part /boot └─nvme0n1p3 259:3 0 951.3G 0 part /home / </syntaxhighlight>The exact names are probably different on your machine, but the most important part is the <code>/dev/sdX</code> device, for USBs it is most likely going to be an <code>sdX</code> device. Then the next step is to overwrite the USB. There are a few ways to do this. Everywhere you see <code>/dev/sdX</code> replace <code>/dev/sdX</code> with the name of your USB device as given by lsblk. First, if you want to be sure the data is gone and prevent an attacker from potentially guessing how much data is on the device, you can do: <code>sudo dd if=/dev/urandom of/dev/sdX bs=4M status=progress</code> after that ''optional'' step is done, you can move onto creating the partition, note that this step and the previous optional step, '''will erase all the data on the drive'''! There are several ways to do this, you can use a graphical tool like [[GParted]], But for fdisk, the instructions are simple, <code>fdisk /dev/sdX</code> Then run the <code>g</code> command to create a new GPT Partition, after that, you should run the <code>n</code> command to create a new partition, leave all the settings (like partition number and sectors) blank to use defaults, after you are done, run <code>w</code> to commit your changes to the USB and '''erase all data'''. After you are done that, its time to create the encrypted partition, run: <code>sudo cryptsetup luksFormat --verify-passphrase /dev/sdX1</code> Note that <code>/dev/sdX1</code> ends in a 1 to signify the first partition. Next, to open the device, run <code>sudo cryptsetup open /dev/sd</code><code>X1 usb</code> After that, the device with the unencrypted data will be in <code>/dev/mapper/usb</code>, now you can actually make the file system. If you want ext4, the traditional Linux file system, run: <code>sudo mkfs.ext4 /dev/mapper/usb</code> Otherwise, if you want btrfs, a more modern option, run: <code>sudo mkfs.btrfs /dev/mapper/usb</code> Now there is one more thing to do, mount the files. <code>sudo mount /dev/mapper/usb /mnt</code> Then you are done. The files are accessible in /mnt, though you might want to chown them so you have permissions. When it comes time to remove the USB you can simply unmount the drive by running <code>sudo umount /mnt</code> and then closing the LUKS device <code>sudo cryptsetup close usb</code> === How to open and close the USB === After your done creating it, opening it is simple, just run<syntaxhighlight lang="bash"> sudo cryptsetup open /dev/sdX1 usb sudo mount /dev/mapper/usb /mnt </syntaxhighlight>And then you can close it just as easily,<syntaxhighlight lang="bash"> sudo umount /mnt sudo cryptsetup close usb </syntaxhighlight> 7280a8d16c12dd217c0737682779888f6e40d6a4 5061 5053 2026-05-24T13:53:57Z Uniolo 345 Add to guides and software categories wikitext text/x-wiki {{Work In Progress}} {{stub|date=may 2026}} = How to create a LUKS USB = {{Guide_Warning}} The following section provides commands and instructions on how to use [[cryptsetup]] to create a LUKS USB. One of the most common use for cryptsetup is to create an encrypted, As USB devices are small and could be easily lost or stolen, it is recommended to encrypt USB devices if you only plan on accessing them on Linux, though there may be tools out there for accessing LUKS devices on non-[[Linux kernel|Linux]] systems. Note that the following instructions involve partitioning the USB, meaning, '''all data on it will be lost'''. Use this when creating a USB. Firstly, read the above warning, secondly, find the device you want to encrypt by running <code>lsblk</code>, the output should look something like this,<syntaxhighlight lang="output"> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 7.2G 0 disk ├─sda1 8:1 1 7.2G 0 part zram0 251:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 953.9G 0 disk ├─nvme0n1p1 259:1 0 600M 0 part /boot/efi ├─nvme0n1p2 259:2 0 2G 0 part /boot └─nvme0n1p3 259:3 0 951.3G 0 part /home / </syntaxhighlight>The exact names are probably different on your machine, but the most important part is the <code>/dev/sdX</code> device, for USBs it is most likely going to be an <code>sdX</code> device. Then the next step is to overwrite the USB. There are a few ways to do this. Everywhere you see <code>/dev/sdX</code> replace <code>/dev/sdX</code> with the name of your USB device as given by lsblk. First, if you want to be sure the data is gone and prevent an attacker from potentially guessing how much data is on the device, you can do: <code>sudo dd if=/dev/urandom of/dev/sdX bs=4M status=progress</code> after that ''optional'' step is done, you can move onto creating the partition, note that this step and the previous optional step, '''will erase all the data on the drive'''! There are several ways to do this, you can use a graphical tool like [[GParted]], But for fdisk, the instructions are simple, <code>fdisk /dev/sdX</code> Then run the <code>g</code> command to create a new GPT Partition, after that, you should run the <code>n</code> command to create a new partition, leave all the settings (like partition number and sectors) blank to use defaults, after you are done, run <code>w</code> to commit your changes to the USB and '''erase all data'''. After you are done that, its time to create the encrypted partition, run: <code>sudo cryptsetup luksFormat --verify-passphrase /dev/sdX1</code> Note that <code>/dev/sdX1</code> ends in a 1 to signify the first partition. Next, to open the device, run <code>sudo cryptsetup open /dev/sd</code><code>X1 usb</code> After that, the device with the unencrypted data will be in <code>/dev/mapper/usb</code>, now you can actually make the file system. If you want ext4, the traditional Linux file system, run: <code>sudo mkfs.ext4 /dev/mapper/usb</code> Otherwise, if you want btrfs, a more modern option, run: <code>sudo mkfs.btrfs /dev/mapper/usb</code> Now there is one more thing to do, mount the files. <code>sudo mount /dev/mapper/usb /mnt</code> Then you are done. The files are accessible in /mnt, though you might want to chown them so you have permissions. When it comes time to remove the USB you can simply unmount the drive by running <code>sudo umount /mnt</code> and then closing the LUKS device <code>sudo cryptsetup close usb</code> === How to open and close the USB === After your done creating it, opening it is simple, just run<syntaxhighlight lang="bash"> sudo cryptsetup open /dev/sdX1 usb sudo mount /dev/mapper/usb /mnt </syntaxhighlight>And then you can close it just as easily,<syntaxhighlight lang="bash"> sudo umount /mnt sudo cryptsetup close usb </syntaxhighlight> [[Category:Guides]] [[Category:Software]] 7279006f7a3b5a4cd1ae12d18be2306a072991d6 0 178 5064 4688 2026-05-24T13:57:56Z Uniolo 345 Update kernel version to 7.0, dont think RCs should be included. wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 7.0, 2026-04-12 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[Category:Terminology]] [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and deallocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under the terms of the [[GNU General Public License]] version 2 (GPLv2), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] *[[UNIX|Unix]] * [[FOSS|Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> 5f3111063254f95402013ea3e19bf5ac68c11b2a 5065 5064 2026-05-24T13:59:30Z Uniolo 345 Specify that the kernel is GPLv2-only wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 7.0, 2026-04-12 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, community contributors | website = [https://kernel.org/ kernel.org] }} [[Category:Terminology]] [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and deallocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under only the terms of the [[GNU General Public License]] version 2 (GPLv2-only), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] *[[UNIX|Unix]] * [[FOSS|Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> ee0260d49852c5500fab87ed7c7aab5029cdbf26 0 667 5066 3685 2026-05-24T14:03:49Z Uniolo 345 Added "horribly out of date" to the reason for cleanup. When I say out of date, I mean its been out of date since 1985. wikitext text/x-wiki {{Cleanup|Incomplete page, horribly out of date}} {{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}} '''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. The owner of the UNIX® trademark has been The Open Group since 1994.<ref>[https://unix.org/what_is_unix.html What is UNIX ®?] unix.org</ref> Examples of modern UNIX operating systems include Apple's MacOS and IBM AIX. Being genetic UNIX® is not required for UNIX® certification. Formerly, Inspur K-UX was certified UNIX®, specifically versions 2.0 and 3.0. Inspur K-UX's UNIX® certification expired in February 2019 and has yet to be renewed.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Inspur_K-UX|title=Inspur K-UX|author=Huihermit|year=21 January 2025|accessdate=2 August 2025}}</ref> == References == 04cf88861907100b7b94b524cd1e0d2fb3fb92bd 0 1215 5067 2026-05-24T14:07:54Z Sparrow 362 Add paru page wikitext text/x-wiki [[Category:Software]] [[Category:AUR Helpers]] {{Work In Progress}} {{Stub}} {{SoftwareInfobox | image = | caption = | title = Paru | releasestatus = Maintained | lastrelease = v2.1.0, 2025-07-08 | languages = Rust, Shell | developers = Morganamilo | website = [https://github.com/Morganamilo/paru github.com] }} '''Paru''' is an open-source [[AUR Helper]] which automates the process of searching, retrieving and building packages from the [[Arch User Repository]]. Paru's main advantage over other AUR Helpers is that PKGBUILDS are downloaded automatically by default for the user to inspect, helping ensure that malicious packages aren't downloaded. == Installation == Paru can be installed via one of the following methods. Instructions from building from source can be found on Paru's GitHub page. === Using Git: === <code>git clone https://aur.archlinux.org/paru.git && cd paru</code> <code>makepkg -sci</code> === Using yay: === <code>yay -S paru</code> == Usage == The following commands are typical usage of Paru: {| class="wikitable" |+Common Paru Commands !Command !Description |- |<code>paru</code> |Alias for <code>pacman -Syu</code> |- |<code>paru -S <package-name></code> |Search the online repositories and installs the given package(s). |- |<code>paru <package-name></code> |Interactively searches and installs the given package(s). |- |<code>paru -G <package-name></code> |Downloads the PKGBUILD and related files of the given package. |} 7319fc0c2cb6fd32ed73615d91c69e1fd860861d 0 1040 5069 4790 2026-05-24T14:11:29Z YDTA 389 Expanded wiki page (work in progress) wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = DNF, APT | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = systemd | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Qubes OS separates applications and workflows into isolated compartments known as '''qubes'''<ref>also known as a '''domU,''' '''security domain,''' or simply '''domain''' </ref> by leveraging [[Xen]]-based virtualization<ref name=":0">{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/intro.html|title=Introduction to Qubes OS|accessdate=2026-05-24}}</ref>. == Qubes Security == Each qube is implemented as a separate Xen [[virtual machine]] which the user will be use for activities such as composing documents or browsing the web<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/getting-started.html|title=Qubes OS Basics|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Qubes are distinguished by their name, which identifies their purpose, and a color which identifies the level of trust that they are given<ref name=":0" />. === Limitations of Qubes Security === It is important to note that while Qubes OS is designed to to limit the damage which can be caused by the compromise of one or many qubes, it does not attempt at additional hardening for the VM operating system itself above that of the base distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/developer/system/security-design-goals.html#security-design-goals|title=Security Design Goals|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Users may consider using other security-oriented distributions in conjunction with Qubes OS for additional security. === Qubes Master Signing Key === The QMSK is an [[Gnupg|OpenPGP]] key used as the root of trust for the Qubes OS Project to verify developer keys, release signatures, and communications against<ref name=":1">{{Cite|url=https://doc.qubes-os.org/en/latest/project-security/verifying-signatures.html#how-to-import-and-authenticate-the-qubes-master-signing-key|title=Verifying signatures|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. The QMSK is available from the Qubes Project at https://keys.qubes-os.org/keys/qubes-master-signing-key.asc, or in any Qubes OS provided qube at <code>/usr/share/qubes/qubes-master-key.asc</code>. Users are encouraged to compare multiple channels to verify the QMSK's fingerprint<ref name=":1" /> and to not trust any single source (including this website). One copy is provided here as: <code>0x427F11FD0FAA4B080123F01CDDFA1A3E36879494</code> Other places to look include: * The Qubes OS Project wiki * Video recordings of presentations about Qubes * Asking a friend(s) * Asking a stranger(s) == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] 1cf95a6b9dd20f7244600e741d133f8f43cbe80c 0 396 5070 5068 2026-05-24T14:11:35Z Uniolo 345 Added minisign wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover | |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice | |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn | |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi | |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code | |OSS (Visual Studio Code) - An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} == Miscellaneous == software categories that font fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !Links !Description |- |[[GnuPG]] | |Open source PGP encryption implementation. |- |[[Age]] | |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] | |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] | |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |} c2a83e0e5a1335f0274c0625ed5d0d684649f253 5071 5070 2026-05-24T14:14:00Z MysteryBirb 353 Added Links to LibreOffice, Discover, nnn and yazi wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://github.com/KDE/discover GitHub] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |[[pacman]] | |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] | |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] | |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} ebf4171c67243bdf9efba12d43cf578614c2f50f 5072 5071 2026-05-24T14:30:02Z MysteryBirb 353 Added links to package managers wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://github.com/KDE/discover GitHub] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |pacman |[[pacman]] - In FOSS wiki, [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |apt |[[apt]] - In FOSS wiki, [https://salsa.debian.org/apt-team/apt Source Code] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |dnf |[[dnf]] - In FOSS wiki, [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} 94ea07926ac7a091c83bfed24eae78d8906342d1 5074 5072 2026-05-24T14:38:45Z Uniolo 345 Readd misc (accidentally overwritten) wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://github.com/KDE/discover GitHub] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |pacman |[[pacman]] - In FOSS wiki, [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |apt |[[apt]] - In FOSS wiki, [https://salsa.debian.org/apt-team/apt Source Code] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |dnf |[[dnf]] - In FOSS wiki, [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} == Miscellaneous == software categories that font fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !Links !Description |- |[[GnuPG]] | |Open source PGP encryption implementation. |- |[[Age]] | |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] | |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] | |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |} 65c3a5a7e3a026305a0fcd53be860b20d0acf19e 5075 5074 2026-05-24T14:39:59Z Uniolo 345 Fix typo (font -> do not) wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://github.com/KDE/discover GitHub] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |pacman |[[pacman]] - In FOSS wiki, [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |apt |[[apt]] - In FOSS wiki, [https://salsa.debian.org/apt-team/apt Source Code] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |dnf |[[dnf]] - In FOSS wiki, [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !Links !Description |- |[[GnuPG]] | |Open source PGP encryption implementation. |- |[[Age]] | |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] | |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] | |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |} c73529fd0639332e420443be16bc7852c61eae89 5080 5075 2026-05-24T15:18:22Z YDTA 389 added emacs wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://github.com/KDE/discover GitHub] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |pacman |[[pacman]] - In FOSS wiki, [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |apt |[[apt]] - In FOSS wiki, [https://salsa.debian.org/apt-team/apt Source Code] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |dnf |[[dnf]] - In FOSS wiki, [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] | |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] | |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !Links !Description |- |[[GnuPG]] | |Open source PGP encryption implementation. |- |[[Age]] | |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] | |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] | |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |} c48475d3527fd9c0c3f4aedb0e6b377d4b3610fd 5089 5080 2026-05-24T15:45:48Z Uniolo 345 Add Gocryptfs and Cryptomator wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://github.com/KDE/discover GitHub] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |pacman |[[pacman]] - In FOSS wiki, [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |apt |[[apt]] - In FOSS wiki, [https://salsa.debian.org/apt-team/apt Source Code] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |dnf |[[dnf]] - In FOSS wiki, [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC | |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |[[Midnight Commander]] | |Two-panel terminal-based file manager. |- |nnn |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |ranger | |Terminal-based file manager with vi-style keybindings. |- |yazi |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] | |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape | |Vector image editor, good for editing SVG files. |- |Graphite | |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive | |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |[https://github.com/NickvisionApps/Parabolic Parabolic] | |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[https://github.com/yt-dlp/yt-dlp yt-dlp] | |CLI program for downloading audio and video from websites. |- |[https://github.com/spotDL/spotify-downloader SpotDL] | |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |[https://mpv.io/ mpv] | |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] | |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] | |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !Links !Description |- |[[GnuPG]] | |Open source PGP encryption implementation. |- |[[Age]] | |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] | |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] | |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] | |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] | |Program for creating encrypted vaults for use with cloud providers. |} 0cdd974ae84f1a20cd5a4d32f7453e6034d0f4c2 5098 5089 2026-05-24T17:06:01Z MysteryBirb 353 Added plenty of missing links wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://github.com/KDE/discover GitHub] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |pacman |[[pacman|FOSS wiki]], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |apt |[[apt|FOSS wiki]], [https://salsa.debian.org/apt-team/apt Source Code] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |dnf |[[dnf|FOSS wiki]], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |BitWarden |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |Midnight Commander |[[Midnight Commander|FOSS wiki]], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |nnn |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |ranger |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |yazi |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |ytree |[[ytree|FOSS wiki]], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |Graphite |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |Parabolic |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |yt-dlp |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |SpotDL |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |VLC |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |mpv |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany | |A powerful, stable and lightweight programmer's text editor. |- |Kate | |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite | |A text editor that comes with [[Plasma|KDE Plasma]] |- |Code - OSS (Visual Studio Code) | |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed | |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] | |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |[[nano]] | |Simple terminal text editor that comes with most distributions |- |[[vi]] | |A keyboard based terminal text editor |- |[[vim]] | |An improved version of Vi with various changes and support for plugins |- |[[neovim]] | |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] | |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] | |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !Links !Description |- |[[GnuPG]] | |Open source PGP encryption implementation. |- |[[Age]] | |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] | |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] | |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] | |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] | |Program for creating encrypted vaults for use with cloud providers. |} af0c1e0bbb7669f6b986bc3d28a30330d8094955 5104 5098 2026-05-24T17:41:37Z MysteryBirb 353 Added links to both text editors and terminal-based text editors wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://invent.kde.org/plasma/discover Source] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |pacman |[[pacman|FOSS wiki]], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |apt |[[apt|FOSS wiki]], [https://salsa.debian.org/apt-team/apt Source Code] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |dnf |[[dnf|FOSS wiki]], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |BitWarden |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |Midnight Commander |[[Midnight Commander|FOSS wiki]], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |nnn |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |ranger |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |yazi |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |ytree |[[ytree|FOSS wiki]], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |Graphite |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |Parabolic |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |yt-dlp |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |SpotDL |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |VLC |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |mpv |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |Kate |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate Source] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |Code - OSS (Visual Studio Code) |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |GNU Emacs (GUI) |[[GNU Emacs|FOSS wiki]], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |nano |[[nano|FOSS wiki]], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |vi |[[vi|FOSS wiki]] |A keyboard based terminal text editor |- |vim |[[vim|FOSS wiki]], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |neovim |[[neovim|FOSS wiki]], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |GNU Emacs |[[GNU Emacs|FOSS wiki]], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[[helix|FOSS wiki]], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] | |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim | |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |[https://github.com/Vysp3r/protonplus ProtonPlus] | |GTK4-based graphical utility for installing and managing community Proton builds. |- |[https://github.com/DavidoTek/ProtonUp-Qt ProtonUp-Qt] | |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |[https://github.com/flightlessmango/MangoHud MangoHud] | |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[https://github.com/benjamimgois/goverlay GOverlay] | |Graphical interface for configuring MangoHud and vkBasalt. |- |[https://github.com/libratbag/piper Piper] | |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !Links !Description |- |[[GnuPG]] | |Open source PGP encryption implementation. |- |[[Age]] | |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] | |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] | |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] | |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] | |Program for creating encrypted vaults for use with cloud providers. |} 5e94694b50321dccdd733c8b8f045292d4ac74d5 5107 5104 2026-05-24T18:13:35Z MysteryBirb 353 Added links to remaining utilities (except IDEs) wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !Links !Description !DE |- |Discover |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://invent.kde.org/plasma/discover Source] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !Links !Description !Distribution |- |pacman |[[pacman|FOSS wiki]], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |apt |[[apt|FOSS wiki]], [https://salsa.debian.org/apt-team/apt Source Code] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |dnf |[[dnf|FOSS wiki]], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !Links !Description |- |LibreOffice |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !Links !Description |- |KeePassXC |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |BitWarden |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !Links !Description |- |Midnight Commander |[[Midnight Commander|FOSS wiki]], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |nnn |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |ranger |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |yazi |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |ytree |[[ytree|FOSS wiki]], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !Links !Description |- |GIMP |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |Krita |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |Libresprite |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |PixiEditor |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |Material Maker |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !Links !Description |- |Inkscape |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |Graphite |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !Links !Description |- |Kdenlive |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !Links !Description |- |Parabolic |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |yt-dlp |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |SpotDL |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !Links !Description |- |VLC |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |mpv |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !Links !Description |- |Blender |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !Links !Description |- |Geany |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |Kate |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate Source] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |KWrite |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |Code - OSS (Visual Studio Code) |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |Zed |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |GNU Emacs (GUI) |[[GNU Emacs|FOSS wiki]], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !Links !Description |- |nano |[[nano|FOSS wiki]], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |vi |[[vi|FOSS wiki]] |A keyboard based terminal text editor |- |vim |[[vim|FOSS wiki]], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |neovim |[[neovim|FOSS wiki]], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |GNU Emacs |[[GNU Emacs|FOSS wiki]], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |helix |[[helix|FOSS wiki]], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |Kakoune |[[Kakoune|FOSS wiki]], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !Links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !Links !Description |- |Godot |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !Links !Description |- |LibreAim |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !Links !Description |- |ProtonPlus |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |ProtonUp-Qt |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !Links !Description |- |MangoHud |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |GOverlay |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |Piper |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !Links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |Matrix |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !Links !Description |- |GnuPG |[[GnuPG|FOSS wiki]]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |Age |[[Age|FOSS wiki]], [https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |Minisign |[[Minisign|FOSS wiki]], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |Cryptsetup |[[Cryptsetup|FOSS wiki]], [https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |Gocryptfs |[[Gocryptfs|FOSS wiki]], [https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |Cryptomator |[[Cryptomator|FOSS wiki]], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} b2b5e0be6707361ccb3520e21a5caddb2726acb5 0 1040 5073 5069 2026-05-24T14:35:54Z YDTA 389 Additions and grammar fixes wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = DNF, APT | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = systemd | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Qubes OS separates applications and workflows into isolated compartments known as '''qubes'''<ref>also known as a '''domU,''' '''security domain,''' or simply '''domain''' </ref> by leveraging [[Xen]]-based virtualization<ref name=":0">{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/intro.html|title=Introduction to Qubes OS|accessdate=2026-05-24}}</ref>. It should also be noted that Qubes, rather than being considered a Linux distribution, may be considered as either a ''meta-distribution'' (in a similar regard as [[Bedrock Linux]]), or a Xen distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#is-qubes-just-another-linux-distribution|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Technically, any [[x86_64]] operating system may be used as a qube, but the extent to which it is supported varies. == Qubes Security == Each qube is implemented as a separate [[Xen|Xen virtual machine]], which the user may utilize for activities such as composing documents or browsing the web<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/getting-started.html|title=Qubes OS Basics|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Each qube is distinguished by its name, which identifies its purpose, and a color which identifies its level of trust<ref name=":0" />. === Limitations of Qubes Security === It is important to note that while Qubes OS is designed to to limit the damage caused by the compromise of one or multiple qubes, <u>it does ''not'' attempt at additional hardening for the VM operating system itself</u> above that of the base distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/developer/system/security-design-goals.html#security-design-goals|title=Security Design Goals|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Users may consider using other security-oriented distributions in conjunction with Qubes OS for additional security. === Qubes Master Signing Key === The QMSK is an [[Gnupg|OpenPGP]] key used as the root of trust for the Qubes OS Project to verify developer keys, release signatures, and communications<ref name=":1">{{Cite|url=https://doc.qubes-os.org/en/latest/project-security/verifying-signatures.html#how-to-import-and-authenticate-the-qubes-master-signing-key|title=Verifying signatures|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. The QMSK is available from the Qubes Project at https://keys.qubes-os.org/keys/qubes-master-signing-key.asc, or in any Qubes OS provided qube at <code>/usr/share/qubes/qubes-master-key.asc</code>. Users are encouraged by the Qubes Project to distrust the infrastructure and to compare multiple channels to verify the QMSK's fingerprint<ref name=":1" /> Any single source (including this website) should not be trusted. One copy is provided here as: <code>0x427F11FD0FAA4B080123F01CDDFA1A3E36879494</code> Other potential channels to obtain the fingerprint from include: * The Qubes OS Project wiki * Video recordings of presentations about Qubes * Asking a friend(s) * Asking a stranger(s) == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] 54836c37c31f05e5aab314cf796ae37d64fcb737 5076 5073 2026-05-24T14:46:41Z Matthias von Schwarzwald 361 Linking wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = [[DNF]], [[APT]] | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = [[systemd]] | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Qubes OS separates applications and workflows into isolated compartments known as '''qubes'''<ref>also known as a '''domU,''' '''security domain,''' or simply '''domain''' </ref> by leveraging [[Xen]]-based virtualization<ref name=":0">{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/intro.html|title=Introduction to Qubes OS|accessdate=2026-05-24}}</ref>. It should also be noted that Qubes, rather than being considered a Linux distribution, may be considered as either a ''meta-distribution'' (in a similar regard as [[Bedrock Linux]]), or a Xen distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#is-qubes-just-another-linux-distribution|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Technically, any [[x86_64]] operating system may be used as a qube, but the extent to which it is supported varies. == Qubes Security == Each qube is implemented as a separate [[Xen|Xen virtual machine]], which the user may utilize for activities such as composing documents or browsing the web<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/getting-started.html|title=Qubes OS Basics|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Each qube is distinguished by its name, which identifies its purpose, and a color which identifies its level of trust<ref name=":0" />. === Limitations of Qubes Security === It is important to note that while Qubes OS is designed to to limit the damage caused by the compromise of one or multiple qubes, <u>it does ''not'' attempt at additional hardening for the VM operating system itself</u> above that of the base distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/developer/system/security-design-goals.html#security-design-goals|title=Security Design Goals|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Users may consider using other security-oriented distributions in conjunction with Qubes OS for additional security. === Qubes Master Signing Key === The QMSK is an [[Gnupg|OpenPGP]] key used as the root of trust for the Qubes OS Project to verify developer keys, release signatures, and communications<ref name=":1">{{Cite|url=https://doc.qubes-os.org/en/latest/project-security/verifying-signatures.html#how-to-import-and-authenticate-the-qubes-master-signing-key|title=Verifying signatures|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. The QMSK is available from the Qubes Project at https://keys.qubes-os.org/keys/qubes-master-signing-key.asc, or in any Qubes OS provided qube at <code>/usr/share/qubes/qubes-master-key.asc</code>. Users are encouraged by the Qubes Project to distrust the infrastructure and to compare multiple channels to verify the QMSK's fingerprint<ref name=":1" /> Any single source (including this website) should not be trusted. One copy is provided here as: <code>0x427F11FD0FAA4B080123F01CDDFA1A3E36879494</code> Other potential channels to obtain the fingerprint from include: * The Qubes OS Project wiki * Video recordings of presentations about Qubes * Asking a friend(s) * Asking a stranger(s) == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] 2c60eefab63a7378043de270b157bc6c744ed196 5093 5076 2026-05-24T16:41:55Z YDTA 389 Added content wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = [[DNF]], [[APT]] | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = [[systemd]] | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Qubes OS separates applications and workflows into isolated compartments known as '''qubes'''<ref>also known as a '''domU,''' '''security domain,''' or simply '''domain''' </ref> by leveraging [[Xen]]-based virtualization<ref name=":0">{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/intro.html|title=Introduction to Qubes OS|accessdate=2026-05-24}}</ref>. It should also be noted that Qubes, rather than being considered a Linux distribution, may be considered as either a ''meta-distribution'' (in a similar regard as [[Bedrock Linux]]), or a Xen distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#is-qubes-just-another-linux-distribution|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Technically, any [[X86-64|x86_64]] operating system may be used as a qube, but the extent to which it is supported varies. == Installation == The Qubes OS project provides a [https://doc.qubes-os.org/en/latest/user/downloading-installing-upgrading/installation-guide.html comprehensive installation guide] in its documentation. Users may consider reading the documentation on [https://doc.qubes-os.org/en/latest/user/downloading-installing-upgrading/install-security.html installation security] as well. === System Requirements === The following features are <u>required</u> (but may not be sufficient) for Qubes OS<ref name=":2">{{Cite|url=https://doc.qubes-os.org/en/latest/user/hardware/system-requirements.html|title=System Requirements|author=Qubes OS Project|accessdate=2026-05-25}}</ref>: * [[X86-64|64-bit Intel or AMD processor]] ** Intel VT-x with EPT or AMD-V with RVI ** Intel VT-d or AMD-Vi (also known as AMD IOMMU) * 6 GB RAM * 32 GB free space on disk The following are <u>recommended</u> for running Qubes OS<ref name=":2" />: * [[X86-64|64-bit Intel processor]] ** Intel VT-x with EPT ** Intel VT-d ** AMD processors are not recommended due to inconsistent security support on client platforms (see Important Notes for details). * 16 GB RAM * 128 GB free space ** A fast solid-state drive is strongly recommended by the project * An Intel integrated graphics processor is strongly recommended by the project ** Nvidia GPUs may require significant troubleshooting. ** AMD GPUs have not been formally tested, but Radeons (especially RX580 and earlier) generally work well. * A non-USB keyboard, or multiple USB controllers * A Trusted Platform Module (TPM) with proper BIOS support == Supported [[Qubes OS#Templates|Templates]] == The Qubes OS project officially provides the following templates: * [[Fedora]]-based ** [[XFCE]] ** [[GNOME]] ** Minimal (CLI only) * [[Debian]]-based ** XFCE ** GNOME ** Minimal (CLI only) Community-supported templates are also available, [https://doc.qubes-os.org/en/latest/user/templates/templates.html#community with additional considerations]: * [[Kicksecure]] * [[Whonix]] **Whonix Gateway **Whonix Workstation * Arch (in <code>qubes-templates-community-testing</code>) Users will also be able to create their own Templates from scratch == Architecture == Each qube is implemented as a separate [[Xen|Xen virtual machine]], which the user may utilize for activities such as composing documents or browsing the web<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/getting-started.html|title=Qubes OS Basics|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Each qube is distinguished by its name, which identifies its purpose, and a color which identifies its level of trust<ref name=":0" />. Qubes are copy-on-write, meaning that a [https://doc.qubes-os.org/en/latest/user/advanced-topics/volume-backup-revert.html full revert mechanism is available should it be needed]. === Templates === Templates provide root filesystems for app qubes. When an app qube is started, a copy of the root filesystem will be made and used by the app qube, then discarded on shutdown<ref name=":3">{{Cite|url=https://doc.qubes-os.org/en/latest/user/reference/glossary.html|title=Glossary|author=Qubes OS Project|accessdate=2026-05-25}}</ref>. Software meant to be run in app qubes must be installed in the corresponding template. See https://doc.qubes-os.org/en/latest/user/templates/templates.html === App qubes === App qubes are qubes where the user is meant to conduct everyday activities. An app qube will use a copy of the root filesystem taken from a chosen [[Qubes OS#Template|template]], and will only keep things in <code>/home/</code>and <code>/usr/local/</code>after being restarted<ref name=":3" />. App qubes can also be disposable templates and provide the base for disposable qubes. === Disposables === Disposable qubes obtain a fresh filesystem from its disposable template (distinct from a template) upon startup and fully discard it after shutting down<ref name=":3" />. === Standalones === A regular vm, both root and user directories are kept between starts<ref name=":3" />. == Security == === Qubes Master Signing Key === The QMSK is an [[Gnupg|OpenPGP]] key used as the root of trust for the Qubes OS Project to verify developer keys, release signatures, and communications<ref name=":1">{{Cite|url=https://doc.qubes-os.org/en/latest/project-security/verifying-signatures.html#how-to-import-and-authenticate-the-qubes-master-signing-key|title=Verifying signatures|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. The QMSK is available from the Qubes Project at https://keys.qubes-os.org/keys/qubes-master-signing-key.asc, or in any Qubes OS provided qube at <code>/usr/share/qubes/qubes-master-key.asc</code>. Users are encouraged by the Qubes Project to "distrust the infrastructure"<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#what-does-it-mean-to-distrust-the-infrastructure|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-25}}</ref> and to compare multiple channels to verify the QMSK's fingerprint<ref name=":1" /> Any single source (including this website) should not be trusted. One copy is provided here as: <code>0x427F11FD0FAA4B080123F01CDDFA1A3E36879494</code> Other potential channels to obtain the fingerprint from include: * The Qubes OS Project wiki * Video recordings of presentations about Qubes * Asking a friend(s) * Asking a stranger(s) === Limitations === It is important to note that while Qubes OS is designed to to limit the damage caused by the compromise of one or multiple qubes, <u>it does ''not'' attempt at additional hardening for the VM operating system itself</u> above that of the base distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/developer/system/security-design-goals.html#security-design-goals|title=Security Design Goals|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Users may consider using other security-oriented distributions in conjunction with Qubes OS for additional security. == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] 2070bb3f72a9b0b6ebfa6f7d5b35f5ae4da63d1e 0 575 5077 4065 2026-05-24T15:04:40Z YDTA 389 See vim. wikitext text/x-wiki ''See [[Vim]].''{{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.2, Aug 14, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. == References == 487781b31757f8e08a3f9453934f3c081eec5afb 5087 5077 2026-05-24T15:42:47Z YDTA 389 moved see vim wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.2, Aug 14, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] GNU Emacs is a free/libre interpreter for the Emacs Lisp language, with extensions to assist with editing text among other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. ''Also see [[Vim]].'' == References == b6c6b6dd2633493d6aac04ba9963e49debe4efd7 0 1120 5078 5015 2026-05-24T15:05:40Z YDTA 389 See Emacs. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }}''See [[GNU Emacs|Emacs]].''[[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim|NeoVim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] == References == <references /> 00731662e3e6e1781f905023d1ecefc77da18f58 5085 5078 2026-05-24T15:30:47Z Uniolo 345 Moved "see Emacs" to bottom of main section wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim|NeoVim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ''Also see: [[GNU Emacs|Emacs]].'' ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] == References == <references /> c0ae1fbd3b97ea674ff710a8e73d229edcaa5e10 5103 5085 2026-05-24T17:37:02Z Uniolo 345 Fixed capitalization in Neovim (NeoVim -> Neovim) wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ''Also see: [[GNU Emacs|Emacs]].'' ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. [[Category:Software]] == References == <references /> f6e9ce9ffd859e790dfc9ab41d3a8e7994763e7c 0 1216 5079 2026-05-24T15:14:24Z Uniolo 345 Create page with basic information and sidebar about Cryptomator. wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:Cryptomator Logo 2020.svg|thumb]] |caption=Cryptomater |releasestatus=Maintained |lastrelease=1.19.2, Mar 20, 2026 |firstrelease=1.0, Mar 9, 2016 |languages=[[Java]] |developers=[https://www.linkedin.com/company/skymatic Skymatic GmbH] |website=[https://cryptomator.org/ cryptomator.org] }} '''Cryptomator''' is a open source encryption program for creating encrypted vaults that can be synchronized to a cloud provider allowing for encrypted cloud storage. It works with any cloud provider that has file synchronization and can even be used to encrypt files you plan on storing locally, though other alternatives exist for that, such as [[KDE]] Vaults. f1d35f6565b85f8f5b8b68762c3f37aa66c35fc5 5081 5079 2026-05-24T15:19:07Z Uniolo 345 Fixed typo in name... also applies to the name of this page... wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:Cryptomator Logo 2020.svg|thumb]] |caption=Cryptomator |releasestatus=Maintained |lastrelease=1.19.2, Mar 20, 2026 |firstrelease=1.0, Mar 9, 2016 |languages=[[Java]] |developers=[https://www.linkedin.com/company/skymatic Skymatic GmbH] |website=[https://cryptomator.org/ cryptomator.org] }} '''Cryptomator''' is a open source encryption program for creating encrypted vaults that can be synchronized to a cloud provider allowing for encrypted cloud storage. It works with any cloud provider that has file synchronization and can even be used to encrypt files you plan on storing locally, though other alternatives exist for that, such as [[KDE]] Vaults. a96bf651c03bba7c7737fa7022ce7682f66d197f 5084 5081 2026-05-24T15:26:12Z Matthias von Schwarzwald 361 Redirect to properly-spelled "Cryptomator" wikitext text/x-wiki #REDIRECT [[Cryptomator]] d1f4f60b76683b182f0786f576a0a878afc3028d 0 1217 5082 2026-05-24T15:23:34Z Matthias von Schwarzwald 361 Copy from misspelled "Cryptomater" wikitext text/x-wiki Insert paragraph [[File:OOjs_UI_icon_alert.svg|link=|14x14px]] This page is a stub. You can assist by expanding it. Insert paragraph {{SoftwareInfobox|image=[[File:Cryptomator Logo 2020.svg|thumb]]|caption=Cryptomator|releasestatus=Maintained|lastrelease=1.19.2, Mar 20, 2026|firstrelease=1.0, Mar 9, 2016|languages=[[Java]]|developers=[https://www.linkedin.com/company/skymatic Skymatic GmbH]|website=[https://cryptomator.org/ cryptomator.org]}} '''Cryptomator''' is a open source encryption program for creating encrypted vaults that can be synchronized to a cloud provider allowing for encrypted cloud storage. It works with any cloud provider that has file synchronization and can even be used to encrypt files you plan on storing locally, though other alternatives exist for that, such as [[KDE]] Vaults. [[Category:Software]] ab5fe0ab2b3281142b4ecc5f93c4d31321c5b000 5083 5082 2026-05-24T15:24:47Z Matthias von Schwarzwald 361 Re-copy from misspelled "Cryptomater" wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:Cryptomator Logo 2020.svg|thumb]] |caption=Cryptomator |releasestatus=Maintained |lastrelease=1.19.2, Mar 20, 2026 |firstrelease=1.0, Mar 9, 2016 |languages=[[Java]] |developers=[https://www.linkedin.com/company/skymatic Skymatic GmbH] |website=[https://cryptomator.org/ cryptomator.org] }} '''Cryptomator''' is a open source encryption program for creating encrypted vaults that can be synchronized to a cloud provider allowing for encrypted cloud storage. It works with any cloud provider that has file synchronization and can even be used to encrypt files you plan on storing locally, though other alternatives exist for that, such as [[KDE]] Vaults. [[Category:Software]] 74bc47e5eefc09afb2fe55fb0c7b4f09b365aeba 0 1218 5086 2026-05-24T15:42:18Z Uniolo 345 Created gocryptfs, simple, not much to write about. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |title=gocryptfs |releasestatus=Maintained |lastrelease=2.6.1, 2025-08-10 |firstrelease=1.0, 2016-07-17 |languages=[[Go]] |developers=[https://github.com/rfjakob rfjakob] |website=[https://nuetzlich.net/gocryptfs nuetzlich.net/gocryptfs] }} '''gocryptfs''' is an encrypted overlay filesystem<ref>{{Cite|url=https://github.com/rfjakob/gocryptfs|title=gocryptfs github|author=gocryptfs contributors|year=2026|accessdate=2026-05-24}}</ref> built in [[Go]] on top of [[Linux kernel|FUSE]], more specifically, [https://github.com/hanwen/go-fuse go-fuse]. It is used in [[KDE]] Vaults for encryption. 603cba124c9bce1b39f85e3e00b2034d70f029fa 5090 5086 2026-05-24T15:50:28Z Uniolo 345 Fixed typo (built -> made) wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |title=gocryptfs |releasestatus=Maintained |lastrelease=2.6.1, 2025-08-10 |firstrelease=1.0, 2016-07-17 |languages=[[Go]] |developers=[https://github.com/rfjakob rfjakob] |website=[https://nuetzlich.net/gocryptfs nuetzlich.net/gocryptfs] }} '''gocryptfs''' is an encrypted overlay filesystem<ref>{{Cite|url=https://github.com/rfjakob/gocryptfs|title=gocryptfs github|author=gocryptfs contributors|year=2026|accessdate=2026-05-24}}</ref> made in [[Go]] on top of [[Linux kernel|FUSE]], more specifically, [https://github.com/hanwen/go-fuse go-fuse]. It is used in [[KDE]] Vaults for encryption. 663a6d535ff0dc6f7f4d040dfc1cca67717569de 0 1219 5088 2026-05-24T15:43:15Z Uniolo 345 Create as redirect to software (since I accidentally went to Programs instead of Software, never again) wikitext text/x-wiki #redirect [[Software]] af3c29531a927e594c227590325580dc9d550d3d 2 1035 5091 4220 2026-05-24T16:25:04Z Splayer 262 wikitext text/x-wiki Just another tech enthusiast :) discord: imsplayer af757984aa62b99b3ebd9963be5a63c447a489cd 0 628 5092 4969 2026-05-24T16:41:53Z SpeeQz1 392 Added relevant links to external websites. Updated latest release information. Added link to Linux Mint Community Wiki. Did some small grammar changes. wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entry point into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history. There is also a Debian-based version of Linux Mint, called [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> More information and resources related to Linux Mint along with how to install it, use it and manage it can be found at [https://mintguide.miraheze.org/wiki/Linux_Mint The Linux Mint Community Wiki]. == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: [https://github.com/linuxmint Open-source] * Update Method: [https://endoflife.date/linuxmint Release cycle] * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) [[File:Linux-Mint-Cinnamon.png|thumb|A Linux Mint installation with the Cinnamon desktop]] == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. In 2016, the Linux Mint website and forums were hacked and the installation images were infected with malware.<ref>{{Cite|url=https://www.pcworld.com/article/419713/hackers-planted-a-backdoor-inside-a-compromised-version-of-linux-mint.html|title=Linux Mint website hacked, ISO downloads replaced with backdoored operating system|author=Nick Mediati, PCWorld|year=2016|accessdate=2025.08.31}}</ref> The latest release, Linux Mint 22.3 "Zena", was launched on the 13th of January, 2026 and is supported until 2029.<ref>https://linuxmint.com/rel_zena.php, Linux Mint, 2006-08-09 (Accessed: 2026-05-24)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own [https://linuxmint.com/teams.php repositories], which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repositories also contain software made by the Linux Mint team such as Cinnamon and its related applications<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> which can be installed from the [https://mintwiki.org/wiki/Software_Manager Software Manager]. == References == 5badc75b1566045a609530edd4c2d0b5bc5b1981 5095 5092 2026-05-24T16:45:10Z SpeeQz1 392 Fixed Mint wiki link pointing to wrong page. wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] }} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entry point into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history. There is also a Debian-based version of Linux Mint, called [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> More information and resources related to Linux Mint along with how to install it, use it and manage it can be found at [https://mintwiki.org/ The Linux Mint Community Wiki]. == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: [https://github.com/linuxmint Open-source] * Update Method: [https://endoflife.date/linuxmint Release cycle] * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) [[File:Linux-Mint-Cinnamon.png|thumb|A Linux Mint installation with the Cinnamon desktop]] == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. In 2016, the Linux Mint website and forums were hacked and the installation images were infected with malware.<ref>{{Cite|url=https://www.pcworld.com/article/419713/hackers-planted-a-backdoor-inside-a-compromised-version-of-linux-mint.html|title=Linux Mint website hacked, ISO downloads replaced with backdoored operating system|author=Nick Mediati, PCWorld|year=2016|accessdate=2025.08.31}}</ref> The latest release, Linux Mint 22.3 "Zena", was launched on the 13th of January, 2026 and is supported until 2029.<ref>https://linuxmint.com/rel_zena.php, Linux Mint, 2006-08-09 (Accessed: 2026-05-24)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own [https://linuxmint.com/teams.php repositories], which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repositories also contain software made by the Linux Mint team such as Cinnamon and its related applications<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> which can be installed from the [https://mintwiki.org/wiki/Software_Manager Software Manager]. == References == de796a9e2e50b9825180922e6544e1f6f4a98a27 5099 5095 2026-05-24T17:06:37Z SpeeQz1 392 wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] |wiki=[https://mintwiki.org/ The Linux Mint Community Wiki]}} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entry point into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history. There is also a Debian-based version of Linux Mint, called [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> More information and resources related to Linux Mint along with how to install it, use it and manage it can be found at [https://mintwiki.org/ The Linux Mint Community Wiki]. == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: [https://github.com/linuxmint Open-source] * Update Method: [https://endoflife.date/linuxmint Release cycle] * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) [[File:Linux-Mint-Cinnamon.png|thumb|A Linux Mint installation with the Cinnamon desktop]] == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. In 2016, the Linux Mint website and forums were hacked and the installation images were infected with malware.<ref>{{Cite|url=https://www.pcworld.com/article/419713/hackers-planted-a-backdoor-inside-a-compromised-version-of-linux-mint.html|title=Linux Mint website hacked, ISO downloads replaced with backdoored operating system|author=Nick Mediati, PCWorld|year=2016|accessdate=2025.08.31}}</ref> The latest release, Linux Mint 22.3 "Zena", was launched on the 13th of January, 2026 and is supported until 2029.<ref>https://linuxmint.com/rel_zena.php, Linux Mint, 2006-08-09 (Accessed: 2026-05-24)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own [https://linuxmint.com/teams.php repositories], which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repositories also contain software made by the Linux Mint team such as Cinnamon and its related applications<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> which can be installed from the [https://mintwiki.org/wiki/Software_Manager Software Manager]. == References == 727acec93ad87f47c408f3c6b7abf711fcc13b05 6 1189 5094 4968 2026-05-24T16:43:45Z SpeeQz1 392 SpeeQz1 uploaded a new version of [[File:Linux-Mint-Cinnamon.png]] wikitext text/x-wiki == Summary == A Linux-mint instalation running cinnamon. == Licensing == {{Unknown_copyright}} e8c859452451e3b88c2a9a25cc8384998e92972a 0 769 5096 4429 2026-05-24T16:59:53Z MysteryBirb 353 Changed MangoWC to MangoWM wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | [[MangoWM]]<ref>[https://mangowc.vercel.app MangoWM Homepage] (Accessed: 2026-02-27)</ref> || None || [[C]] || Extremely customizable & performant Wayland compositor built on top of [[dwl]]. |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| [[C]] || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | [[Sway]] || None || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || None (Tiling) || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[river]]<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref> || None (Tiling) || [[zig]]|| Lightweight and minimal tiling compositor focused on simplicity. |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || None (3D effects) || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || None (Kiosk) || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- | [[Niri]] || None (Scrolling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp<nowiki> cosmic-comp github repo], pop-os team et al., 2025</nowiki></ref> |[[COSMIC]] |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || None (Tiling) || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> b70a00a2d6e5b62178978c7460ae0bb4d0374313 828 163 5097 3454 2026-05-24T17:04:20Z Madonuko 140 add optional wiki parameter Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Default Desktops', args.defaultdesktops ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Architectures', args.architectures ) :addRow( 'Website', args.website ) if args.wiki then retval:addRow('Wiki', args.wiki) end return retval end return p 44e1922c90ee21c86f8186a5652d64e2e979a77e 0 178 5100 5065 2026-05-24T17:09:06Z Wakana Kisarazu 391 Extended "Overview", added to "Developer(s)" and fixed typo in "Memory Manager" list wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 7.0, 2026-04-12 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, subsystem maintainers, community contributors | website = [https://kernel.org/ kernel.org] }} [[Category:Terminology]] [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. The Linux kernel is one of the most prominent examples of free and open-source software collaboration, and is considered to be the largest open source project. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and de-allocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under only the terms of the [[GNU General Public License]] version 2 (GPLv2-only), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] *[[UNIX|Unix]] * [[FOSS|Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> 3b07f269c36e38a4227d4399047080e7bdcd3a70 5101 5100 2026-05-24T17:14:04Z Wakana Kisarazu 391 Extended "Overview" further wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 7.0, 2026-04-12 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, subsystem maintainers, community contributors | website = [https://kernel.org/ kernel.org] }} [[Category:Terminology]] [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. The Linux kernel is one of the most prominent examples of free and open-source software collaboration, and is considered to be the largest open source project. Linux was developed by Linus Torvalds, following the lack of a working kernel for GNU. At the time, kernels like UNIX were under copyright from AT&T. Like MINIX, Linux did not contain any UNIX code, avoiding legal issues. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and de-allocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under only the terms of the [[GNU General Public License]] version 2 (GPLv2-only), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] *[[UNIX|Unix]] * [[FOSS|Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> 2364ba7209f79e6492113fe82479918127a4c12d 5114 5101 2026-05-24T18:49:12Z Habaja1 377 added wikipedia link to monolithic kernel as placeholder wikitext text/x-wiki {{Cleanup|Short article}} {{SoftwareInfobox | image = [[File:Tux.svg|Tux|333px]] | caption = [[Tux]], the Linux mascot. | title = Linux | releasestatus = Maintained | lastrelease = 7.0, 2026-04-12 | languages = [[C]], [[Assembly]], [[Rust]] | developers = Linus Torvalds, subsystem maintainers, community contributors | website = [https://kernel.org/ kernel.org] }} [[Category:Terminology]] [[File:Linux 5.15.19 boot process screenshot.png|thumb|Linux 5.15.19 Kernel boot process]] The '''Linux kernel''' is the core component of the Linux operating system and is responsible for managing system resources, enabling hardware-software interaction, and providing essential services to user-space programs. Developed initially by [[Linus Torvalds]] in 1991, it has since become one of the most widely used kernels in the world, powering systems ranging from smartphones and servers to embedded devices and supercomputers. == Overview == The Linux kernel is a [[wikipedia:Monolithic_kernel|monolithic kernel]], meaning it contains all the necessary code for managing the CPU, memory, file systems, device drivers, and networking, but it is modular in nature, allowing dynamic loading and unloading of kernel modules. The Linux kernel is one of the most prominent examples of free and open-source software collaboration, and is considered to be the largest open source project. Linux was developed by Linus Torvalds, following the lack of a working kernel for GNU. At the time, kernels like UNIX were under copyright from AT&T. Like MINIX, Linux did not contain any UNIX code, avoiding legal issues. == Architecture == === Key Components === * '''Process Scheduler''': Determines which process runs at any given time. * '''Memory Manager''': Manages allocation and de-allocation of memory space. * '''Virtual File System (VFS)''': Provides an abstraction layer over different file systems. * '''Network Stack''': Handles network protocols and communication. * '''Device Drivers''': Allow the kernel to communicate with hardware devices. * '''System Calls''': Interface between user space and kernel space. === Supported Architectures === The Linux kernel supports a wide variety of hardware architectures, including: * x86 / x86_64 * ARM / AArch64 * MIPS * PowerPC * RISC-V * SPARC == Development == The Linux kernel is developed collaboratively by thousands of developers across the globe. Contributions are managed via the [[Git]] version control system, and the official source code repository is hosted at [https://git.kernel.org/ git.kernel.org]. === Key Maintainers === * [[Linus Torvalds]] – Lead maintainer and creator of the kernel * Subsystem maintainers – Responsible for specific areas such as networking, file systems, and architecture-specific code === Release Model === The Linux kernel follows a rolling release model with a new stable version approximately every 9 to 10 weeks. Long-Term Support (LTS) versions are maintained for extended periods (up to 6 years or more). == Licensing == The Linux kernel is licensed under only the terms of the [[GNU General Public License]] version 2 (GPLv2-only), which allows users to run, study, share, and modify the software. == Use Cases == The Linux kernel is used in a wide array of devices and systems: * [[Android (operating system)|Android]] smartphones and tablets * Web servers and data centers * Desktop Linux distributions (e.g., Ubuntu, Fedora, Arch Linux) * Embedded systems and Internet of Things (IoT) devices * Supercomputers == See Also == * [[GNU]] *[[UNIX|Unix]] * [[FOSS|Open source software]] == External Links == * [https://www.kernel.org/ Official Linux Kernel Website] * [https://git.kernel.org/ Linux Kernel Source Repository] * [https://www.kernelnewbies.org/ Kernel Newbies] * [https://lwn.net/ Linux Weekly News] == References == <references/> The '''Linux kernel''' is a free and open source [[UNIX|Unix-like]] kernel that is used in many computer systems and servers. If you want to know about the source code, you can look https://www.kernel.org/ == References == <references /> 7a73e01b57835561b98d05e530d988b9b99cd96a 10 162 5102 2093 2026-05-24T17:14:36Z Madonuko 140 add template data wikitext text/x-wiki <includeonly>{{#invoke:DistributionInfobox|main}}</includeonly> <noinclude>{{/doc}}<templatedata> { "params": { "title": { "type": "string", "required": true }, "image": { "type": "wiki-file-name" }, "caption": {}, "releasestatus": { "required": true }, "releasemodel": { "required": true }, "packagemanager": { "required": true }, "defaultdesktops": { "required": true }, "usagetype": { "required": true }, "architectures": { "required": true }, "website": { "type": "url", "required": true }, "wiki": { "type": "url" } }, "format": "block" } </templatedata></noinclude> 8ce30b4016b96417da476dc8971161cf632e7d68 0 581 5105 3641 2026-05-24T17:55:52Z Wilbur 142 change display title from "MATE DE" to "MATE" for consistency wikitext text/x-wiki {{Needs Citations}} {{DISPLAYTITLE:MATE}} [[Category:Desktop Environments]] [[File:MATEDesktop.png|thumb|A screenshot of the default MATE desktop on Debian Linux.]] The [https://mate-desktop.org/ MATE] Desktop Environment is a desktop environment that is the continuation of GNOME 2. It is known for using traditional metaphors for Linux and other Unix-like operating systems, and for being a lightweight desktop that runs well on older hardware. It is available on a wide variety of Linux, Illumos and BSD - based systems. MATE is known as one of the three desktop options on [https://www.linuxmint.com/ Linux Mint], as well as the main desktop of [[Ubuntu|Ubuntu MATE]]. == Features == MATE is configured by default to use a traditional UNIX-like desktop layout, with a top and bottom panel like its ancestor GNOME 2. It is a lightweight desktop, much like [[XFCE]], and is often used on older and less powerful computers. It can use GTK2 or GTK3 theming - the latter being compatible with [[Cinnamon]]. == Software == The base system is made up of the Marco window manager, MATE Panel, and MATE Session Manager. Additional software can be installed on some distributions with the mate-extras package. MATE includes the Caja file manager, Pluma notepad / text editor, Eye of MATE image viewer, Atril document viewer, Engrampa archive manager, and MATE Terminal. == Naming == MATE is said to be pronounced "mah-tay". The MATE desktop is named after ''Ilex paraguariensis,'' commonly known as yerba maté, which is a caffeine-rich holly plant used to make the infused herbal drink mate. 9d82cc95ef3bbb67cb8b451865d481ac5dc4f694 0 1026 5106 4877 2026-05-24T18:00:33Z Ping 374 Added a sentence explaining an ongoing language rewrite wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox |image = [[File:Debian_Nala.png|300px|center|thumb]] |caption = Nala install screenshot |title = Nala |releasestatus = Maintained |lastrelease = v0.16.0, 2025-04-21 |languages = [[Python]] |developers = [[https://gitlab.com/volian Volian]] |website = [[https://gitlab.com/volian/nala Nala Gitlab]] }} Nala is a front-end of libapt-pkg, which is a part of the [[apt|APT]] packaging managing suite used by [[Debian]]-based [[Linux Distributions|Linux distributions]]. Nala is designed to provide prettier output and speed up [[package]] installations with parallel downloads alongside a mirror ranking feature. As a front-end, Nala can only be used on systems with the apt package installed. Currently, Nala is undergoing a language rewrite from [[Python]] to [[Rust]]<ref>{{Cite|url=https://gitlab.com/volian/nala/-/tree/nala-rs|title=nala-rs branch: Nala's GitLab|accessdate=2026-05-24}}</ref>. == Limitations == * Nala requires at least Debian 11/Bullseye or Ubuntu 19.04/Disco Dingo or newer, older releases do not have required packages and [[Python]] versions available.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/wikis/Installation|title=Installation: Nala's Gitlab Wiki|accessdate=2026-05-23}}</ref> * Nala limits parallel downloads connections to three per mirror.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/blob/f6fc96c7afcb02b277d5811cfa6703e368cec317/README.rst|title=README: Nala's Gitlab repository|year=2024|accessdate=2026-05-23}}</ref> * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding packages (pauses certain packages' updates) or showing reverse dependencies (packages depending on a certain package). To hold packages consider using the apt-mark tool instead. == Usage<ref>{{Cite|url=http://manpages.debian.org/trixie/nala/nala.8.en.html|title=Nala User Manual: Debian Manpages|year=2025|accessdate=2026-05-23}}</ref> == The following shows common Nala [[command]]s, which are mostly similar to that of the apt command. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of available packages and their versions |- |<code>nala upgrade</code> |Updates and upgrades system's packages, alongside removing unused dependencies |- |<code>nala full-upgrade</code> |Updates and upgrades system's packages, installing new packages and removing old ones as needed |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala clean</code> |Removes unused package caches within the system |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages available for installation. Can list installed packages with <code>nala list --installed</code> |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands (transaction) alongside its ID |- |<code>nala history info <ID></code> |Show the info of a specific transaction |- |<code>nala history undo <ID></code> |Undo the commands ran under a specific transaction |- |<code>nala history redo <ID></code> |Redo the commands ran under a specific transaction |} <references /> 11df45115e6b9380b5a5ea63bef7e92982796ea2 1 1220 5108 2026-05-24T18:23:21Z Ping 374 /* Should pip and venv be a separate page? */ new section wikitext text/x-wiki == Should pip and venv be a separate page? == Considering there are alternatives such as uv, pipx, and Poetry. It might be better to separate pip and venv from the python page as well. This is especially true with pip since distros packages it separately. For now, I will be working on cleaning up this page's information first before moving away these if that seems better. [[User:Ping|Ping]] ([[User talk:Ping|talk]]) 18:23, 24 May 2026 (UTC) d71dc69dc33e390ca7eab96ea7371ef70c8dfecc 1 1140 5109 4959 2026-05-24T18:35:09Z Uniolo 345 /* Link to the wiki page in the name not the "links" */ new section wikitext text/x-wiki == how to organize software == half actual discussion, half making sure some browsers aren't breaking this feature [[User:Nathan22211|Nathan22211]] ([[User talk:Nathan22211|talk]]) 01:07, 23 May 2026 (UTC) == Missing software. == This page has a header saying that, <code>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</code> So I am going to follow the advice and list some of the missing pages. * For the <code>Terminal-based text editors</code> section, we are missing [[Neovim]] and [[Helix]]. There is also a [[Nano]] page that is included but not linked to. * For the <code>Package managers</code>, we already have a [[Package Manager|page for them]] that lists many not on this page. * [[Tor]] is not listed anywhere, so are there a bunch of pages that are not listed. * And more™ This list is fairly incomplete, and definitely needs some work, but the header does state to talk before making edits, so perhaps a different header is required. @[[User:Electron271|Electron271]] pinging you since it seems like you were the one to add the header. [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 13:45, 23 May 2026 (UTC) :I removed the template because a wiki itself is a work in progress. [[User:Rob Kam|Rob Kam]] ([[User talk:Rob Kam|talk]]) 15:38, 23 May 2026 (UTC) ::I added Vim and Helix [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 15:51, 23 May 2026 (UTC) == Link to the wiki page in the name not the "links" == I am strongly apposed to having the <code>FOSS wiki</code> links be with the other links, instead, I think they should be found by clicking on the program name. This page is linked from the front page and will likely be used by new people to find pages. I think the <code>Links</code> should be changed to <code>External links</code> and you going to the wiki page by clicking on the name, as it was previously. Currently, this page is just a list of software in general, not wiki pages about software (despite being on the front page). This change just adds to that. [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 18:35, 24 May 2026 (UTC) b22ee1b1ab55ff989432bdb638dbd6804a1a8253 6 1221 5110 2026-05-24T18:43:10Z Habaja1 377 Flatpak's logo. wikitext text/x-wiki == Summary == Flatpak's logo. == Licensing == {{CC-BY-SA-4.0}} de5d436fc38eb9960b177f888119e8224812bc5d 0 677 5111 2955 2026-05-24T18:43:42Z Habaja1 377 added flatpak's logo. wikitext text/x-wiki [[File:Flatpak Logo.png|thumb|Flatpak's logo.]] Flatpak is a universal packaging system and runtime for installing packages separate from the system packages. Mainly meant for desktop applications, Flatpak allows application developers to distribute packages without needing to worry about distro compatibility because Flatpak installs its own runtime dependencies. It claims to improve security through sandboxing providing the user the ability to give or revoke permissions for a given application. Flatpak is installed by default on many distributions and it's main distribution platform is Flathub. == Installation == Flatpak comes preinstalled on many distributions such as Linux Mint and Fedora but can be installed through most distro's package repositories if not present. ==== KDE Discover ==== KDE Discover includes the ability to install Flatpak and enable Flathub through its graphical user interface. Go to the setting tab and install the Flatpak backend then restart Discover then go back to the settings and enable Flathub. ==== CLI Install on Ubuntu ==== To install Flatpak from the CLI run:<syntaxhighlight lang="bash"> sudo apt install flatpak </syntaxhighlight>To enable Flathub from the CLI run:<syntaxhighlight lang="bash"> flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo </syntaxhighlight>If you make use of GNOME Software you can install the integration plugin:<syntaxhighlight lang="bash"> sudo apt install gnome-software-plugin-flatpak </syntaxhighlight>For the KDE Discover plugin run:<syntaxhighlight lang="bash"> sudo apt install plasma-discover-backend-flatpak </syntaxhighlight>For other distros read the guides on [https://flathub.org/setup Flathub.org]. == Compatibility == Flatpak allows improved package compatibility through its use of its own runtime dependencies. Packages can run through Flatpak where it might not be possible to run on natively such as: * Applications that require a newer version of glibc than whats available on an stable release distro such as Rocky Linux 8. * Applications that depend on glibc such as Steam running on a distro using musl like Alpine Linux. * Multilib packages such as Steam or Wine on distros without multilib support such as CentOS Stream 10. == Sandboxing == Package permissions can be managed by the user through a graphical user interface with Flatseal which can be installed as a Flatpak. == Flathub Package Verification == Flathub has a package verification system that allows packages maintained by the official developers to have a verification tick.<ref>[https://docs.flathub.org/docs/for-app-authors/verification Verification | Flathub Documentation], Flathub Team, 2025 (Accessed: 2025-06-22)</ref> This has lead to some confusion where verification is mistaken for package safety. Linux Mint hides unverified Flatpaks from Software Manager by default Starting in version 22.<ref>[https://www.omgubuntu.co.uk/2024/06/linux-mint-will-hide-unverified-flatpaks Linux Mint Will Hide Unverified Flatpaks in Software Manager - OMG! Ubuntu], Joey Sneddon, 2024 (Accessed: 2025-06-22)</ref> == References == 3e5f5cbbba5bad020a475d3dde0cf76992246c67 0 1206 5112 5040 2026-05-24T18:48:27Z Habaja1 377 wikitext text/x-wiki '''KDE Neon''' is a [[Linux Distributions|linux distribution]] based on [[Ubuntu|Ubuntu LTS]] developed by the [[KDE]] team, wich provides users with the latest features of the [[Plasma|KDE Plasma]] desktop environment<ref>{{Cite|url=https://neon.kde.org/faq#what-is-neon|title=KDE Neon's FAQ, What is KDE Neon question.|accessdate=2026/05/24}}</ref>. It is essentially the testing ground where new KDE Plasma updates are tested and used before being introduced to other distros using KDE Plasma (Much like how [[Fedora]] is [[Red Hat Enterprise Linux|RHEL]]'s testing ground). However, apart from the KDE Plasma desktop, the distro itself follows the stable release schedule of [[Ubuntu|Ubuntu LTS]], making it a half stable half rolling distro<ref>{{Cite|url=https://neon.kde.org/faq#is-it-rolling|title=Official statement in the KDE Neon FAQ on this.|accessdate=2026/05/26}}</ref>. because it is developed by the KDE developers, it can be seen as a "pure" KDE Plasma experience. {{DistributionInfobox|title=KDE Neon|image=[[File:KDE-Neon-logo.png]]|caption=The KDE Neon logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]], PackageKit|defaultdesktops=KDE Plasma|usagetype=Desktop|architectures=x86_64|website=[https://neon.kde.org/index&#124; KDE Neon]|Written in=C, C++, QT 6}} == History == KDE neon first started taking shape in late 2015 as a way to provide a rolling release of fresh KDE software on top of [[Ubuntu]]'s stable OS base. The first daily installation images began being built in January 2016. The first general release of KDE Neon was on 8 June 2016, it was based on an [[Ubuntu]] 16.04 base, using [[Plasma|KDE Plasma]] 5.6. The Latest version of KDE Neon, 6.6, was released on 16 February 2026. [[File:KDE-Neon-6.6-big.png|thumb|A fresh installation of KDE Neon 6.6.]] == Features == KDE Neon == Installation == KDE Neon uses the [[Calamares]] installer. Specifications for installation are: {| class="wikitable" |+ ! !Minimum !Recommended ! |- |Proccesor |1 GHz X86-64 CPU |2 GHz Dual-Core X86-64 CPU Or higher | |- |RAM |2GB |4GB and higher | |- |Storage |20 GB |40 GB and higher | |} Note that these minimum specs will just get you to run it at the bare minimum == References == 92b4bacff52231de641dfb7e3537cc91bc604617 4 571 5113 4617 2026-05-24T18:48:50Z Atmois 13 Fix analytics URL wikitext text/x-wiki = FOSS Wiki Privacy Policy = Last Updated: 24 May 2026<blockquote>Update: Update timeline for CheckUser IP retention, add backup retention policy, clarify edit disclosure timespan and methods, fix processor name, fix analytics URL </blockquote>Welcome to '''FOSS Wiki''' Privacy Policy. This document outlines how personal information is collected, used, and protected when you use '''FOSS Wiki'''. By accessing or contributing to '''FOSS Wiki''', you agree to the terms outlined in this Privacy Policy. == <u>Information FOSS Wiki Collects</u> == When you edit any article or page on '''FOSS Wiki''', you are creating a permanent, public record of any change, addition, removal made by you. Public records will show the time and username authoring the edits. ''To contribute to '''FOSS Wiki''', you are required to create an account. When registering, '''FOSS Wiki''' collects:'' * A Username * [Optionally] Your Email Address <blockquote>Other information such as your pronouns or Discord ID may be optionally provided to us via your user preferences or our Discord linking service.</blockquote> When a user is logged in to '''FOSS Wiki''' uses essential cookies to maintain your login session and preferences. These cookies are required for the site to function and not shared nor used across other sites. Upon visiting the wiki the web-server will automatically log your IP Address and your User Agent, this information helps identify technical issues and ensure compatibility across devices. The web-server retains its logs for 30 days, after which it will automatically be deleted. Any PII stored in the MediaWiki database is retained in encrypted backups for up to 30 days from the point of creation. Backups are encrypted at creation, stored in an immutable state, and automatically purged after 30 days. Please note that following an erasure request, residual PII may persist in existing backups for up to 30 days before being purged. The IP address of an editor will also be logged by Mediawiki when an edit has been made for anti-vandalism efforts. The logged IP is only available to administrators and will only be used for the purpose of blocking or sanctioning malicious users. IPs are stored for 60 days, after which it will be deleted from the logs and no longer be accessible. However, due to the backup scheme they may persist in encrypted backups for a further 30 days, giving a maximum retention period of 90 days. <blockquote>The logging is provided by the [[mediawikiwiki:Extension:CheckUser|Check User Extension]].</blockquote> == <u>Services FOSS Wiki Uses</u> == '''FOSS Wiki''' uses a self-hosted instance of Umami Analytics to collect anonymous data about how visitors interact with our website. Umami collects: Page views, referring website and user agents. Umami does not collect personal data or use cookies, this data allows us to improve our site’s performance and user experience. Please note this data is kept indefinitely and cannot be removed as it does not store any identifiable information hence cannot be removed on an individual user basis. You can opt out of Umami's analytics for an individual device by entering <code>localStorage.setItem('umami.disabled', 1);</code> into your browser console or blocking the domain <code>analytics.foss.wiki</code> using an adblocker of your choice.. To reenable the collection you can run <code>localStorage.removeItem('umami.disabled');</code>. <blockquote>For more details, please see [https://umami.is/docs Umami's Documentation].</blockquote> '''FOSS Wiki''' also uses Cloudflare to enhance website security and performance. Cloudflare may process certain technical information, such as IP addresses and user agents, to provide services like content delivery, DDoS protection, and caching. Cloudflare also makes use of cookies to manage bot protection and verify access. These cookies are required for site security and functionality, please note that these cookies are managed by Cloudflare under their own privacy policy and data processing agreements. <blockquote>For more details, please see [https://www.cloudflare.com/en-gb/privacypolicy/ Cloudflare’s Privacy Policy].</blockquote> == <u>How FOSS Wiki uses your Information</u> == '''FOSS Wiki''' does not sell, trade, or otherwise transfer your personal information to third parties. '''FOSS Wiki''' will only share your personal information to comply with a valid and legally enforceable warrant, subpoena, court order, law or regulation in the countries where '''FOSS Wiki''' is present. '''FOSS Wiki''' will never provide your information to third parties without your explicit consent. Your account data is held as long as the wiki operates or until a erasure request is completed on your account. '''''FOSS Wiki''' use your data to do the following:'' * To send administrative notices via email. * For the ability to reset your account password via email. * To moderate and combat vandalism & spam on the wiki. * To correctly attribute contributions on the wiki to users. * To monitor and analyse the usage of our services and identify technical issues. '''FOSS Wiki''' uses a variety of measures and policies, to protect your data from unauthorized use or access. Please be aware that no method of data transmission or storage is 100% secure, so '''FOSS Wiki''' cannot guarantee that our security will not be breached. In the event of a data breach, '''FOSS Wiki''' will promptly inform any affected users either through private communications or a public notice, as well as any relevant authorities == <u>Your Rights</u> == ''Under the General Data Protection Regulation you are afforded the following rights:'' ; Right to be informed: : The right to be informed about the collection and use of their personal data. ; Right to access: : The right to access and receive a copy of their personal data, and other supplementary information. ; Right to rectification: : The right to have inaccurate personal data rectified, or completed if it is incomplete. ; Right to erasure: : The right to have personal data erased (Also known as being "forgotten"). ; Right to restrict processing: : The right to request the restriction or suppression of their personal data. ; Right to data portability: : The right to obtain and reuse their personal data for their own purposes across different services. ; Right to object: : The right to object to the processing of their personal data in certain circumstances. ; Right to control automated decision making: : The right to be informed about automated decision systems and are allowed to request human review. In order to comply with GDPR erasure requests and the licensing of content, '''FOSS Wiki''' has implemented a process to remove all your data from '''FOSS Wiki'''. Your account name will be anonymised and your edits will be reattributed to the anonymised username. You will be asked to remove your email and other personal information provided to us via your user preferences. Once this process has been completed your account will be "vanished", which removes it from public logs, then your account will be blocked to prevent future logins. An erasure request will be completed within one calendar month of '''FOSS Wiki''' receiving a request from the owner of the account. Please note however, as per "Information FOSS Wiki Collects", residual PII may persist in encrypted backups for up to 30 days following completion of the erasure process. IP addresses logged by CheckUser are not able to be cleared as part of the erasure process and will persist for up to 90 days from the point of logging across both the live database and encrypted backups. == <u>Changes to the Privacy Policy</u> == '''FOSS Wiki''' may change the Privacy Policy as needed to represent changes in our practises or legal requirements. '''FOSS Wiki''' will notify users of updates that impact them, and all revisions will be available on this page. We will notify users within 24 hours of any amendments via our Community Platforms as appropriate. If you do not agree with any changes made to this Privacy Policy, you may request an erasure of your account and personal data at any time in accordance with your Right to Erasure as outlined above. == <u>Third-party Links</u> == '''FOSS Wiki''' may contain links to third-party websites. '''FOSS Wiki''' is not responsible for the privacy practices or content of these sites. '''FOSS Wiki''' encourages users to review the privacy policies of external sites when visiting them. == <u>Contact</u> == To contact us with any queries or concerns with the privacy policy or to exercise your GDPR rights, please contact us at <code>privacy@foss.wiki</code>. 42ddcbdd861cd75f3c58f02b5cd8ce1dec18e61c 0 543 5115 2719 2026-05-24T18:51:00Z Atmois 13 Fix redirect wikitext text/x-wiki #REDIRECT [[FW:Code of Conduct]] 27c07b5f5950a5a8807387ca7e21fbf7146d49fe 0 198 5116 5004 2026-05-24T18:51:13Z Habaja1 377 added kubuntu wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy]</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/]</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 8f60023da21c8ef9ed5799edfed9f2ab261df801 0 540 5117 2720 2026-05-24T18:51:37Z Atmois 13 Fix redirect wikitext text/x-wiki #REDIRECT [[FW:Contributing]] fbe97918aa6fb4d04ede9d9dc1dd20d9e996d516 0 753 5118 2926 2026-05-24T18:52:44Z Atmois 13 Fix redirect wikitext text/x-wiki #REDIRECT [[FW:Privacy Policy]] 73f77d2608b648631f83d100c0057e11815256a1 4 593 5119 4587 2026-05-24T18:53:45Z Atmois 13 Fix links wikitext text/x-wiki === Preface === Thank you for being interested in contributing and making foss.wiki an amazing resource for all users of FOSS and related fields. For users new to MediaWiki, check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] or the [[mediawikiwiki:Help:VisualEditor|Mediawiki Visual Editor Guide]] for more information on editing using Mediawiki markdown or specifics on features '''foss.wiki''' uses. For users interested in writing guides for '''foss.wiki''' please check out the [[Guides:Contributing]] page for specific instructions on making guides, however a lot of the information here will apply to both making guides and informational articles. To learn more about '''foss.wiki''' you can see the wiki's [[FW:About|about]] page! Some important pages are also listed below: * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[FW:Guidelines]] - Outlines the style guidelines and values of foss.wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of foss.wiki * [[FW:Disclaimer|General Disclaimer]] - foss.wiki Disclaimer If you ever have any questions or need help, you can join our [https://discord.foss.wiki Discord Server] and check out <code>#wiki</code> for wiki related discussions! Now onto the stuff you came here for, how YOU can help make '''foss.wiki''' an amazing resource for the Linux and FOSS community. === Overview of Key Values === We have 4 key values for '''foss.wiki''', that summarise all of our [[FW:Guidelines]]: # Accuracy: Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # Courtesy: Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # Impartiality: Content should always be unbiased to avoid misleading users and advocacy. # Accessibility: Content should be written so that any user of any ability can understand and make use of it. == Basics of Editing == First you need to decide what you want to contribute, if you are unsure, do not worry we are here to help you! To combat vandalism and help with managing the wiki to edit, you are required to [[Special:CreateAccount|Create an Account]]: You just need to choose a username and password, it's that simple! We also suggest you add and verify an email too for password resets or security notifications. '''foss.wiki''' will NEVER share your email or send you any kind of spam or promotional emails. Once you create an account, you can get started editing right away! === Editing an existing page === This is the easiest way to get started on the wiki! Find a page for something you are interested in or want to contribute to and hit the Edit button at the top of the page to open the Visual Editor. From there, you can start editing the page, you can use the toolbar at the top of the page to edit markdown styling and to add content just click where you want to edit and start typing. You can find pages that need help on the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages, or you can use [[Special:Search]] to find a specific page. We suggest that you start with small changes first to get a hang of it and that you avoid doing large overhauls to pages just when you are starting out. The <code>Template:</code> and <code>Module:</code> namespaces exist for templates and dynamic modules for the wiki these, due to the nature of running code or acting as a reusable component, cannot be edited by standard users. You can see how to contribute to these pages in the [[FW:Guidelines#Protected Pages|guidelines]] and the standard procedure for doing so. === Using Images === [[File:UploadFilesImg.png|thumb|218x218px|You can also access the Uploading Files page via the sidebar.]] There are two ways to use images, either by using an image in [https://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons] or by uploading it to '''foss.wiki'''. In either case, to use it in a page, you can click the Insert button and then searching for the file name. To upload your own files, use the [[Special:Upload|upload page]]. Please ensure, if you have not created the image yourself, you can use it on the wiki. Generally this means it must be released under Public Domain, CC-BY-SA, CC-BY or another compatible free licence. By uploading your own content to the wiki, you must select a licence when uploading, we recommend [[FW:Copyrights|CC-BY-SA]] to match our wiki's content licence. === Creating a new page === To create a page, you can click a [[red link]] to open a non-existent page, you can find a list of all the most red-linked pages on [[Special:WantedPages]]. You can also search the title of a non-existent page using [[Special:Search]] and search the name of the page you want to create. Before creating a new page, please check that it does not exist already under a different name and also consider if it meets the standards of the wiki as per the [[FW:Guidelines#Notability|Notability Guidelines]]. When creating guides, prefix the page title with <code>Guides:</code> to place it under the guide's namespace. === Creating Guides === [[Guides:Contributing]] goes into the details of the guides requirements and how they should be written, below is a very simplified list of the requirements: * Always ensure you have the <code><nowiki>{{GuideWarning}}</nowiki></code> template on the page, this must be at the top of the page before any content * Ensure all commands and instructions are accurate * Do not attempt to mislead users with the information on guides Please read the whole of the contributing guides page before starting a new guide or editing an existing guide to ensure your edits do not get denied for not meeting the standards of '''foss.wiki'''. === Moderation === Changes to certain pages, including but not limited to: Guides, Articles & High Traffic Pages go through a moderation phase, once a change is submitted it enters "moderation" to be checked by a moderator, this can be for a variety of reasons, mostly to prevent spam or maintain a high quality of accuracy on information. We suggest talking to a staff member before editing one of these pages to check that you are doing the right thing and understand what we require for edit approval. You can bypass the moderation by becoming an auto-moderated user. We have no formal requirements, but we normally require some history of positive contributions to our or another wiki/source of documentation or have a positive history within the discord server or the FOSS community. If you are unsure if you meet the requirements, just ask! To request the role, you can contact us via the methods listed [[FW:Contact|here]]. === How YOU can Help the Wiki === If you don't know where to start, some good places to check out are the [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]] pages. These categories list every page that has a Cleanup or Needs Citations tag on it. These pages are the most in need of editor support to bring up to our [[FW:Guidelines]]. You can also check out [[Special:WantedPages]] to see which non-existent pages are the most-linked to if you want to start something new. You can also create a page or guide on almost any topic related to FOSS or Linux. Please ensure when making new pages you follow the [[FW:Guidelines#Notability Standards|Notability Standards]]! This is your place to nerd out on something you are interested in to make an amazing resource for new or experienced users in the FOSS/Linux community. If you are ever in doubt, do not hesitate to [[FW:Contact|contact]] us and ask any question on how you can contribute, we are always happy to help prospective editors! If you want some specific pointers of where to start editing, we have listed some pages that have been identified by an admin to be in dire need of reworks or contributions, with a reason and what needs to be done. === Key Pages needing Work === ; [[Window Management System]] : The definition and disambiguation page needs to be written to disambiguate and define X Window Managers and Wayland Compositors properly. It should be setup to clearly direct and explain the user what they may be looking for. ;[[Linux Distributions]] : The article lists distro's, it lacks a lot of major distro's and each section should have a short blurb and information about key facts about what distro's under that group typically are (e.g. release cycle, package manager, etc). This could be done with extra columns or categorisation. ; [[Package Manager]] : The article lists package managers, it needs to be rewritten to compare and delve more into each package manager. It could be structured similar to the [[Linux_Distributions]] as a table. ; [[Key Terms]] : The article needs to be restructured, and similar terms should be grouped together with a short definition next to each one in a table, potentially. The page should be made as easy as possible to navigate and find terms. ; [[Desktop Environments]] : The article needs to be filled out more with more desktop environments and have more links added into the page. ;[[X Window Manager]] : The article, which lists window managers depending on the type, needs to be cleaned up to remove Wayland Compositors and each window managers should have a short blurb to it and potentially key distro's that offer them, a table could be used to list them. Similar to the DE page. ; [[External Resources]] : The article requires a clean-up to be organised and categorised properly, it could make use of wiki tables with a short blurb for all websites listed. ; [[Common Issues and Troubleshooting]] : The article needs to be reworked ready to become a hub for relevant guides, should be organised, potentially with wiki tables. 9e073415bf16ffa6d02ee184abdd34d2a4a155ac 0 1222 5120 2026-05-24T18:57:41Z Uniolo 345 Create yt-dlp with a sidebar, some information, and usage tips. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Yt-dlp logo.svg|thumb]] |caption=yt-dlp |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=2021.01.07, 2021-01-07 |languages=[[Python]] |developers=[https://github.com/orgs/yt-dlp/people yt-dlp maintainers] |website=[https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] }} '''Yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl] and has become the most used program for downloading YouTube videos. === Usage tips === {{Guide_Warning}} Yt-dlp has many options, like [https://sponsor.ajay.app/ sponserblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users would like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from my nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> or by using an [https://man.archlinux.org/man/yt-dlp.1 online manpage]. Some of the most common options are the <code>-o <output></code> and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> 0d73f82ab7f493932bce6bfcbf951bb014e3b584 5121 5120 2026-05-24T18:58:05Z Uniolo 345 Add to "software" category wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Yt-dlp logo.svg|thumb]] |caption=yt-dlp |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=2021.01.07, 2021-01-07 |languages=[[Python]] |developers=[https://github.com/orgs/yt-dlp/people yt-dlp maintainers] |website=[https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] }} '''Yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl] and has become the most used program for downloading YouTube videos. === Usage tips === {{Guide_Warning}} Yt-dlp has many options, like [https://sponsor.ajay.app/ sponserblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users would like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from my nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> or by using an [https://man.archlinux.org/man/yt-dlp.1 online manpage]. Some of the most common options are the <code>-o <output></code> and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> [[Category:Software]] c3e3b9e38f2114d289f3f5d5ccb15d1687ef3f3e 5122 5121 2026-05-24T19:00:08Z Uniolo 345 Citated yt-dlp github, reworded some parts. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Yt-dlp logo.svg|thumb]] |caption=yt-dlp |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=2021.01.07, 2021-01-07 |languages=[[Python]] |developers=[https://github.com/orgs/yt-dlp/people yt-dlp maintainers] |website=[https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] }} '''Yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. === Usage tips === {{Guide_Warning}} Yt-dlp has many options, like [https://sponsor.ajay.app/ sponserblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users may like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from my nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> or by using an [https://man.archlinux.org/man/yt-dlp.1 online manpage]. Some of the most commonly used options are the <code>-o <output></code> to specify and output, and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> [[Category:Software]] 0faf59e7a267666df32a008c1baad3cc52927b41 5124 5122 2026-05-24T19:03:39Z Uniolo 345 Fix last release, accidentally forgot to change it when copying over the sidebar from Vim. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Yt-dlp logo.svg|thumb]] |caption=yt-dlp |title=Vim |releasestatus=Maintained |lastrelease=2026.03.17, 2026-03-17 |firstrelease=2021.01.07, 2021-01-07 |languages=[[Python]] |developers=[https://github.com/orgs/yt-dlp/people yt-dlp maintainers] |website=[https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] }} '''Yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. === Usage tips === {{Guide_Warning}} Yt-dlp has many options, like [https://sponsor.ajay.app/ sponserblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users may like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from my nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> or by using an [https://man.archlinux.org/man/yt-dlp.1 online manpage]. Some of the most commonly used options are the <code>-o <output></code> to specify and output, and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> [[Category:Software]] b2178f2e6e5681fe49902e50dc8c862102b0d0d3 5125 5124 2026-05-24T19:10:06Z Uniolo 345 Update captialization of "yt-dlp" to be consistent with README wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Yt-dlp logo.svg|thumb]] |caption=yt-dlp |title=Vim |releasestatus=Maintained |lastrelease=2026.03.17, 2026-03-17 |firstrelease=2021.01.07, 2021-01-07 |languages=[[Python]] |developers=[https://github.com/orgs/yt-dlp/people yt-dlp maintainers] |website=[https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] }} '''yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. === Usage tips === {{Guide_Warning}} yt-dlp has many options, like [https://sponsor.ajay.app/ sponserblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users may like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from my nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> or by using an [https://man.archlinux.org/man/yt-dlp.1 online manpage]. Some of the most commonly used options are the <code>-o <output></code> to specify and output, and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> [[Category:Software]] 82e66aecec913a22de72806fb36a31df455b2adc 5126 5125 2026-05-24T19:14:22Z Uniolo 345 Fix a typo and spelling mistake wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Yt-dlp logo.svg|thumb]] |caption=yt-dlp |title=Vim |releasestatus=Maintained |lastrelease=2026.03.17, 2026-03-17 |firstrelease=2021.01.07, 2021-01-07 |languages=[[Python]] |developers=[https://github.com/orgs/yt-dlp/people yt-dlp maintainers] |website=[https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] }} '''yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. === Usage tips === {{Guide_Warning}} yt-dlp has many options, like [https://sponsor.ajay.app/ sponsorblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users may like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from a nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> or by using an [https://man.archlinux.org/man/yt-dlp.1 online manpage]. Some of the most commonly used options are the <code>-o <output></code> to specify and output, and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> [[Category:Software]] 1e8bdbf5ae7273aabb915df63fc9923180a00aa0 5127 5126 2026-05-24T19:18:12Z Uniolo 345 Clarify that the link goes to the archlinux online man page wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Yt-dlp logo.svg|thumb]] |caption=yt-dlp |title=Vim |releasestatus=Maintained |lastrelease=2026.03.17, 2026-03-17 |firstrelease=2021.01.07, 2021-01-07 |languages=[[Python]] |developers=[https://github.com/orgs/yt-dlp/people yt-dlp maintainers] |website=[https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] }} '''yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. === Usage tips === {{Guide_Warning}} yt-dlp has many options, like [https://sponsor.ajay.app/ sponsorblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users may like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from a nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> to get a [[Manpages|manpage]] entry, or by using an online manpage such as [https://man.archlinux.org/man/yt-dlp.1 the archlinux online manpages]. Some of the most commonly used options are the <code>-o <output></code> to specify and output, and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> [[Category:Software]] 162b031f1dfa4a3099c513462497eb3b9c84517e 0 396 5123 5107 2026-05-24T19:00:08Z MysteryBirb 353 Changed link to external links and edited how and which links are displayed wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://invent.kde.org/plasma/discover Source] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt Source Code] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate Source] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |Code::Blocks | |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |Eclipse IDE | |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |KDevelop | |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |Lazarus | |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |NetBeans | |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |Qt Creator | |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |Spyder | |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |Godot |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |LibreAim |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |ProtonPlus |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |ProtonUp-Qt |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |MangoHud |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |GOverlay |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |Piper |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |Matrix |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} 8c1d1a0ea8b398ef0beac76f54204bc50af3088f 5129 5123 2026-05-24T19:26:25Z MysteryBirb 353 Added remaining links and formatting wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |Godot |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |LibreAim |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |ProtonPlus |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |ProtonUp-Qt |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |MangoHud |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |GOverlay |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |Piper |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |Fluxer |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |Matrix |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} eb3481a247fb2ae8a74c1de6692e072522958a25 5130 5129 2026-05-24T19:28:18Z MysteryBirb 353 Added formatting to a few missing names wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/en-gb/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} 0c82c7c60f24aac858e5d8c35e75136c51948eca 5131 5130 2026-05-24T19:37:52Z MysteryBirb 353 Changed discover url wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} b7ac6e33603d760b1d49bbf2f8da091429218444 5138 5131 2026-05-24T23:02:56Z Nathan22211 360 Added Machine control Section to Software List. NOTE: FullSpectrum listing might need to be removed at some point and its description merged into Snapmaker Orca, as they hired the dev of FS and purportedly have plans to merge his changes into thier fork wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} 7a85a078b24ad3b7d590b24e89bbc66f0cf1300a 5140 5138 2026-05-24T23:25:57Z Nathan22211 360 wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} 023b2543e3aedd5d27eb4cc89ddb412fbd3bcea7 5144 5140 2026-05-24T23:47:54Z Uniolo 345 Added "See also: Comparison of encryption software" wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] df99d81bcf6dfb9fd4f610823e28f3c165b3a80d 5155 5144 2026-05-25T01:26:50Z Uniolo 345 Added fetch scripts wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} == Miscellaneous == software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] === Fetch scripts === {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch Github] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch Github] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch Github] |Neofetch is a now unmaintained fetch script for displaying system information. |} 2cb8830f1e321b0633c6b5f2e5619bbb3d94e9b1 5156 5155 2026-05-25T01:31:03Z Uniolo 345 Made misc header consistent wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = App stores and software managers = {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} = Productivity = === Document processing and office suites === {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === Password managers === {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Miscellaneous = software categories that do not fit into the other categories of software categories. === Encryption === {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] === Fetch scripts === {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch Github] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch Github] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch Github] |Neofetch is a now unmaintained fetch script for displaying system information. |} 566b02d67198e7fb645dce963e7dde9e8ccb4bb5 5162 5156 2026-05-25T01:44:48Z Deviaze 341 Reorganize categories, adding System and Security categories wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System Information/Monitoring == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch Github] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch Github] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch Github] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. 58d446e04250151f224258e1ba6c100cec7a5d08 5163 5162 2026-05-25T01:46:42Z Deviaze 341 /* Fetch scripts */ fix capitalization of GitHub wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System Information/Monitoring == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. 4adb7d32f16c5faa3d893a32043042125a876548 5165 5163 2026-05-25T01:57:18Z Deviaze 341 /* System */ split system monitoring categories into information vs monitors wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. 3583929ada871d44c7e7ffb89ea3f5625b9e92f2 5166 5165 2026-05-25T01:58:13Z Deviaze 341 /* System */ fix extra whitespace wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} === File managers === ==== Terminal-based file managers ==== These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. ecaf43149823ebc59a4ac08ab5ce773143950902 0 1223 5128 2026-05-24T19:18:45Z Uniolo 345 Create as redirect to Manpages wikitext text/x-wiki #redirect [[Manpages]] fc248d6d3d2ba2b3c8f94b7c58d546903d849d05 0 247 5132 4738 2026-05-24T19:48:15Z YoshikageKira 367 Added new apt commands such as purge and list. Also added more information to the existing commands such as install and autoremove. Set the syntax highlighting for the code blocks to shell-session. wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight lang="shell-session"> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight lang="shell-session"> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight lang="shell-session"> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). You can also install specific versions of a package by adding the version next to the package name using the <code><package_name>=<package_version></code> syntax. Examples:<syntaxhighlight lang="shell-session"># apt install meow # apt install meow- pipes-sh+ code=1.60.2-1632313585</syntaxhighlight> Install command can also install from a debian file if you provide a file path as an argument. This is safer and more convenient than using <code>dpkg -i</code> as install will automatically resolve and download the necessary dependencies for you. Examples:<syntaxhighlight lang="shell-session"> # apt install /absolute/path/to/package_name.deb # apt install ./relative/path/from/cwd/to/package_name.deb </syntaxhighlight> The <code>./</code> is important. It is how apt knows that you are trying to install a local file named <code>package_name.deb</code> rather than searching for an online package with that name. Even if you are in the same directory as the <code>package_name.deb</code>, it is necessary to use <code>./package_name.deb</code>. ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight lang="shell-session"> # apt remove pipes-sh </syntaxhighlight> ==== purge ==== Purge is identical to remove except that packages configuration files are deleted too. Examples:<syntaxhighlight lang="shell-session"> # apt purge pipes-sh </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight lang="shell-session"> # apt autoremove </syntaxhighlight> Autoremove can also be run automatically with install or remove command by added the <code>--auto-remove</code> or <code>--autoremove</code> flag. ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight lang="shell-session"> $ apt search minecraft </syntaxhighlight> ==== list ==== List is used to display the installed, upgradeable, or all available packages. Running the apt list command by itself will display the latest versions for all available packages that you can fetch via apt. However, you can adjust the output of apt list by providing any of the following flags: <code>--installed</code>: To display all the installed packages on your system. <code>--upgradeable</code>: To display all the packages that can be upgraded. <code>--all-versions</code>: To list all available package including all versions for each package that can be installed. Examples:<syntaxhighlight lang="shell-session"> $ apt list $ apt list --installed $ apt list --upgradeable $ apt list --all-versions </syntaxhighlight> Tip: Running <code>apt list</code> dumps a massive wall of text into the terminal, making it difficult to read. Typically, the output of <code>apt list</code> is piped to another tool such as [[grep]], less<ref>{{Cite|url=https://man.archlinux.org/man/less.1.en|title=less(1) - Arch manual pages|year=Jan 29, 2026|accessdate=May 24, 2026}}</ref>, or [[fzf]]<ref>{{Cite|url=https://wiki.archlinux.org/title/Fzf|title=fzf|year=Dec 22, 2025|accessdate=May 24, 2026}}</ref>. These tools allow you to filter out unnecessary information or browse the content in smaller, more manageable chunks. Examples:<syntaxhighlight lang="shell-session"> $ apt list | grep <package name> $ apt list | less $ apt list | fzf </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == 8814c6ce4000498a513123ada443fed617d98b42 5133 5132 2026-05-24T19:49:14Z YoshikageKira 367 Minor formatting wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight lang="shell-session"> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight lang="shell-session"> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight lang="shell-session"> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). You can also install specific versions of a package by adding the version next to the package name using the <code><package_name>=<package_version></code> syntax. Examples:<syntaxhighlight lang="shell-session"># apt install meow # apt install meow- pipes-sh+ code=1.60.2-1632313585</syntaxhighlight> Install command can also install from a debian file if you provide a file path as an argument. This is safer and more convenient than using <code>dpkg -i</code> as install will automatically resolve and download the necessary dependencies for you. Examples:<syntaxhighlight lang="shell-session"> # apt install /absolute/path/to/package_name.deb # apt install ./relative/path/from/cwd/to/package_name.deb </syntaxhighlight> The <code>./</code> is important. It is how apt knows that you are trying to install a local file named <code>package_name.deb</code> rather than searching for an online package with that name. Even if you are in the same directory as the <code>package_name.deb</code>, it is necessary to use <code>./package_name.deb</code>. ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight lang="shell-session"> # apt remove pipes-sh </syntaxhighlight> ==== purge ==== Purge is identical to remove except that packages configuration files are deleted too. Examples:<syntaxhighlight lang="shell-session"> # apt purge pipes-sh </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight lang="shell-session"> # apt autoremove </syntaxhighlight> Autoremove can also be run automatically with install or remove command by added the <code>--auto-remove</code> or <code>--autoremove</code> flag. ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight lang="shell-session"> $ apt search minecraft </syntaxhighlight> ==== list ==== List is used to display the installed, upgradeable, or all available packages. Running the apt list command by itself will display the latest versions for all available packages that you can fetch via apt. However, you can adjust the output of <code>apt list</code> by providing any of the following flags: <code>--installed</code>: To display all the installed packages on your system. <code>--upgradeable</code>: To display all the packages that can be upgraded. <code>--all-versions</code>: To list all available package including all versions for each package that can be installed. Examples:<syntaxhighlight lang="shell-session"> $ apt list $ apt list --installed $ apt list --upgradeable $ apt list --all-versions </syntaxhighlight> Tip: Running <code>apt list</code> dumps a massive wall of text into the terminal, making it difficult to read. Typically, the output of <code>apt list</code> is piped to another tool such as [[grep]], less<ref>{{Cite|url=https://man.archlinux.org/man/less.1.en|title=less(1) - Arch manual pages|year=Jan 29, 2026|accessdate=May 24, 2026}}</ref>, or [[fzf]]<ref>{{Cite|url=https://wiki.archlinux.org/title/Fzf|title=fzf|year=Dec 22, 2025|accessdate=May 24, 2026}}</ref>. These tools allow you to filter out unnecessary information or browse the content in smaller, more manageable chunks. Examples:<syntaxhighlight lang="shell-session"> $ apt list | grep <package name> $ apt list | less $ apt list | fzf </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == 0f3de3a115f27bff24a76700869ebbf3526321a1 5134 5133 2026-05-24T20:11:08Z YoshikageKira 367 removed extra empty lines wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight lang="shell-session"> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight lang="shell-session"> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight lang="shell-session"> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). You can also install specific versions of a package by adding the version next to the package name using the <code><package_name>=<package_version></code> syntax. Examples:<syntaxhighlight lang="shell-session"># apt install meow # apt install meow- pipes-sh+ code=1.60.2-1632313585</syntaxhighlight> Install command can also install from a debian file if you provide a file path as an argument. This is safer and more convenient than using <code>dpkg -i</code> as install will automatically resolve and download the necessary dependencies for you. Examples:<syntaxhighlight lang="shell-session"> # apt install /absolute/path/to/package_name.deb # apt install ./relative/path/from/cwd/to/package_name.deb </syntaxhighlight> The <code>./</code> is important. It is how apt knows that you are trying to install a local file named <code>package_name.deb</code> rather than searching for an online package with that name. Even if you are in the same directory as the <code>package_name.deb</code>, it is necessary to use <code>./package_name.deb</code>. ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight lang="shell-session"> # apt remove pipes-sh </syntaxhighlight> ==== purge ==== Purge is identical to remove except that packages configuration files are deleted too. Examples:<syntaxhighlight lang="shell-session"> # apt purge pipes-sh </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight lang="shell-session"> # apt autoremove </syntaxhighlight> Autoremove can also be run automatically with install or remove command by added the <code>--auto-remove</code> or <code>--autoremove</code> flag. ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight lang="shell-session"> $ apt search minecraft </syntaxhighlight> ==== list ==== List is used to display the installed, upgradeable, or all available packages. Running the apt list command by itself will display the latest versions for all available packages that you can fetch via apt. However, you can adjust the output of <code>apt list</code> by providing any of the following flags: <code>--installed</code>: To display all the installed packages on your system. <code>--upgradeable</code>: To display all the packages that can be upgraded. <code>--all-versions</code>: To list all available package including all versions for each package that can be installed. Examples:<syntaxhighlight lang="shell-session"> $ apt list $ apt list --installed $ apt list --upgradeable $ apt list --all-versions </syntaxhighlight> Tip: Running <code>apt list</code> dumps a massive wall of text into the terminal, making it difficult to read. Typically, the output of <code>apt list</code> is piped to another tool such as [[grep]], less<ref>{{Cite|url=https://man.archlinux.org/man/less.1.en|title=less(1) - Arch manual pages|year=Jan 29, 2026|accessdate=May 24, 2026}}</ref>, or [[fzf]]<ref>{{Cite|url=https://wiki.archlinux.org/title/Fzf|title=fzf|year=Dec 22, 2025|accessdate=May 24, 2026}}</ref>. These tools allow you to filter out unnecessary information or browse the content in smaller, more manageable chunks. Examples:<syntaxhighlight lang="shell-session"> $ apt list | grep <package name> $ apt list | less $ apt list | fzf </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == 6032a589d04f895f1ef76c7262a0fb1949ea6218 5135 5134 2026-05-24T20:23:45Z YoshikageKira 367 Added citation for APT super cow powers easter egg. wikitext text/x-wiki [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers<ref>{{Cite|url=https://unix.stackexchange.com/questions/92185/whats-the-story-behind-super-cow-powers|title=Story behind APT Super Cow Powers|author=Faheem Mitha|year=Sep 24, 2013|accessdate=May 24, 2026}}</ref>. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight lang="shell-session"> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight lang="shell-session"> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight lang="shell-session"> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). You can also install specific versions of a package by adding the version next to the package name using the <code><package_name>=<package_version></code> syntax. Examples:<syntaxhighlight lang="shell-session"># apt install meow # apt install meow- pipes-sh+ code=1.60.2-1632313585</syntaxhighlight> Install command can also install from a debian file if you provide a file path as an argument. This is safer and more convenient than using <code>dpkg -i</code> as install will automatically resolve and download the necessary dependencies for you. Examples:<syntaxhighlight lang="shell-session"> # apt install /absolute/path/to/package_name.deb # apt install ./relative/path/from/cwd/to/package_name.deb </syntaxhighlight> The <code>./</code> is important. It is how apt knows that you are trying to install a local file named <code>package_name.deb</code> rather than searching for an online package with that name. Even if you are in the same directory as the <code>package_name.deb</code>, it is necessary to use <code>./package_name.deb</code>. ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight lang="shell-session"> # apt remove pipes-sh </syntaxhighlight> ==== purge ==== Purge is identical to remove except that packages configuration files are deleted too. Examples:<syntaxhighlight lang="shell-session"> # apt purge pipes-sh </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight lang="shell-session"> # apt autoremove </syntaxhighlight> Autoremove can also be run automatically with install or remove command by added the <code>--auto-remove</code> or <code>--autoremove</code> flag. ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight lang="shell-session"> $ apt search minecraft </syntaxhighlight> ==== list ==== List is used to display the installed, upgradeable, or all available packages. Running the apt list command by itself will display the latest versions for all available packages that you can fetch via apt. However, you can adjust the output of <code>apt list</code> by providing any of the following flags: <code>--installed</code>: To display all the installed packages on your system. <code>--upgradeable</code>: To display all the packages that can be upgraded. <code>--all-versions</code>: To list all available package including all versions for each package that can be installed. Examples:<syntaxhighlight lang="shell-session"> $ apt list $ apt list --installed $ apt list --upgradeable $ apt list --all-versions </syntaxhighlight> Tip: Running <code>apt list</code> dumps a massive wall of text into the terminal, making it difficult to read. Typically, the output of <code>apt list</code> is piped to another tool such as [[grep]], less<ref>{{Cite|url=https://man.archlinux.org/man/less.1.en|title=less(1) - Arch manual pages|year=Jan 29, 2026|accessdate=May 24, 2026}}</ref>, or [[fzf]]<ref>{{Cite|url=https://wiki.archlinux.org/title/Fzf|title=fzf|year=Dec 22, 2025|accessdate=May 24, 2026}}</ref>. These tools allow you to filter out unnecessary information or browse the content in smaller, more manageable chunks. Examples:<syntaxhighlight lang="shell-session"> $ apt list | grep <package name> $ apt list | less $ apt list | fzf </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == 62cd9bc2da2809d79168f502b62e2d7459a8b9d6 5151 5135 2026-05-25T01:11:56Z Ping 374 Categorizing as software wikitext text/x-wiki [[Category:Software]] [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers<ref>{{Cite|url=https://unix.stackexchange.com/questions/92185/whats-the-story-behind-super-cow-powers|title=Story behind APT Super Cow Powers|author=Faheem Mitha|year=Sep 24, 2013|accessdate=May 24, 2026}}</ref>. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight lang="shell-session"> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight lang="shell-session"> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight lang="shell-session"> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). You can also install specific versions of a package by adding the version next to the package name using the <code><package_name>=<package_version></code> syntax. Examples:<syntaxhighlight lang="shell-session"># apt install meow # apt install meow- pipes-sh+ code=1.60.2-1632313585</syntaxhighlight> Install command can also install from a debian file if you provide a file path as an argument. This is safer and more convenient than using <code>dpkg -i</code> as install will automatically resolve and download the necessary dependencies for you. Examples:<syntaxhighlight lang="shell-session"> # apt install /absolute/path/to/package_name.deb # apt install ./relative/path/from/cwd/to/package_name.deb </syntaxhighlight> The <code>./</code> is important. It is how apt knows that you are trying to install a local file named <code>package_name.deb</code> rather than searching for an online package with that name. Even if you are in the same directory as the <code>package_name.deb</code>, it is necessary to use <code>./package_name.deb</code>. ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight lang="shell-session"> # apt remove pipes-sh </syntaxhighlight> ==== purge ==== Purge is identical to remove except that packages configuration files are deleted too. Examples:<syntaxhighlight lang="shell-session"> # apt purge pipes-sh </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight lang="shell-session"> # apt autoremove </syntaxhighlight> Autoremove can also be run automatically with install or remove command by added the <code>--auto-remove</code> or <code>--autoremove</code> flag. ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight lang="shell-session"> $ apt search minecraft </syntaxhighlight> ==== list ==== List is used to display the installed, upgradeable, or all available packages. Running the apt list command by itself will display the latest versions for all available packages that you can fetch via apt. However, you can adjust the output of <code>apt list</code> by providing any of the following flags: <code>--installed</code>: To display all the installed packages on your system. <code>--upgradeable</code>: To display all the packages that can be upgraded. <code>--all-versions</code>: To list all available package including all versions for each package that can be installed. Examples:<syntaxhighlight lang="shell-session"> $ apt list $ apt list --installed $ apt list --upgradeable $ apt list --all-versions </syntaxhighlight> Tip: Running <code>apt list</code> dumps a massive wall of text into the terminal, making it difficult to read. Typically, the output of <code>apt list</code> is piped to another tool such as [[grep]], less<ref>{{Cite|url=https://man.archlinux.org/man/less.1.en|title=less(1) - Arch manual pages|year=Jan 29, 2026|accessdate=May 24, 2026}}</ref>, or [[fzf]]<ref>{{Cite|url=https://wiki.archlinux.org/title/Fzf|title=fzf|year=Dec 22, 2025|accessdate=May 24, 2026}}</ref>. These tools allow you to filter out unnecessary information or browse the content in smaller, more manageable chunks. Examples:<syntaxhighlight lang="shell-session"> $ apt list | grep <package name> $ apt list | less $ apt list | fzf </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == c2f0e401028394a210e11654c776243c4ed99f74 5157 5151 2026-05-25T01:32:27Z YoshikageKira 367 Minor formatting wikitext text/x-wiki [[Category:Software]] [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers<ref>{{Cite|url=https://unix.stackexchange.com/questions/92185/whats-the-story-behind-super-cow-powers|title=Story behind APT Super Cow Powers|author=Faheem Mitha|year=Sep 24, 2013|accessdate=May 24, 2026}}</ref>. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight lang="shell-session"> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight lang="shell-session"> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight lang="shell-session"> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). You can also install specific versions of a package by adding the version next to the package name using the <code><package_name>=<package_version></code> syntax. Examples:<syntaxhighlight lang="shell-session"># apt install meow # apt install meow- pipes-sh+ code=1.60.2-1632313585</syntaxhighlight> Install command can also install from a debian file if you provide a file path as an argument. This is safer and more convenient than using <code>dpkg -i</code> as install will automatically resolve and download the necessary dependencies for you. Examples:<syntaxhighlight lang="shell-session"> # apt install /absolute/path/to/package_name.deb # apt install ./relative/path/from/cwd/to/package_name.deb </syntaxhighlight> The <code>./</code> is important. It is how apt knows that you are trying to install a local file named <code>package_name.deb</code> rather than searching for an online package with that name. Even if you are in the same directory as the <code>package_name.deb</code>, it is necessary to use <code>./package_name.deb</code>. ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight lang="shell-session"> # apt remove pipes-sh </syntaxhighlight> ==== purge ==== Purge is identical to remove except that packages configuration files are deleted too. Examples:<syntaxhighlight lang="shell-session"> # apt purge pipes-sh </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight lang="shell-session"> # apt autoremove </syntaxhighlight> Autoremove can also be run automatically with install or remove command by added the <code>--auto-remove</code> or <code>--autoremove</code> flag. ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight lang="shell-session"> $ apt search minecraft </syntaxhighlight> ==== list ==== List is used to display the installed, upgradeable, or all available packages. Running the <code>apt list</code> command by itself will display the latest versions for all available packages that you can fetch via apt. However, you can adjust the output of <code>apt list</code> by providing any of the following flags: <code>--installed</code>: To display all the installed packages on your system. <code>--upgradeable</code>: To display all the packages that can be upgraded. <code>--all-versions</code>: To list all available package including all versions for each package that can be installed. Examples:<syntaxhighlight lang="shell-session"> $ apt list $ apt list --installed $ apt list --upgradeable $ apt list --all-versions </syntaxhighlight> Tip: Running <code>apt list</code> dumps a massive wall of text into the terminal, making it difficult to read. Typically, the output of <code>apt list</code> is piped to another tool such as [[grep]], less<ref>{{Cite|url=https://man.archlinux.org/man/less.1.en|title=less(1) - Arch manual pages|year=Jan 29, 2026|accessdate=May 24, 2026}}</ref>, or [[fzf]]<ref>{{Cite|url=https://wiki.archlinux.org/title/Fzf|title=fzf|year=Dec 22, 2025|accessdate=May 24, 2026}}</ref>. These tools allow you to filter out unnecessary information or browse the content in smaller, more manageable chunks. Examples:<syntaxhighlight lang="shell-session"> $ apt list | grep <package name> $ apt list | less $ apt list | fzf </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == 2cbe231258c91fa3e771387a7d74aea2619a93b9 1 1138 5136 4733 2026-05-24T20:36:03Z YoshikageKira 367 /* What else needs done */ Reply wikitext text/x-wiki == What else needs done == Completion of apt commands and arguments Section for apt-get, apt-cache & apt-mark footnote for apt-cdrom, apt-config, apt-extracttemplates, & apt-helper unless anyone can give me a valid reason to include these and would like to contribute to their section [[User:LeahTheSlug|LeahTheSlug]] ([[User talk:LeahTheSlug|talk]]) 00:15, 23 May 2026 (UTC) :I added <code>apt purge</code> and <code>list</code> and some more information on other commands. I think it would be nice to have a troubleshooting section and a section on apt-patterns. <code>apt-patterns</code> are super useful and they are hardly discussed anywhere. :I don't think <code>apt-get</code> needs a section because <code>apt</code> replaces <code>apt-get</code> in CLI usage. Unless the section goes over bash scripting with <code>apt-get</code>. :Troubleshooting can take some inspiration from here <nowiki>https://system76.com/support/articles/package-manager-pop/</nowiki> but I think it should also go over troubleshooting keyring and package signing issues. [[User:YoshikageKira|YoshikageKira]] ([[User talk:YoshikageKira|talk]]) 20:36, 24 May 2026 (UTC) e76c317d3e279eb272ad5680db9f93f401c8305f 2 1224 5137 2026-05-24T22:57:24Z Uniolo 345 Create "Comparison of encryption software" with some objective comparison. Still a work in progress. wikitext text/x-wiki {{Work In Progress}} The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ Types of algorithms !Name !Symmetric or Asymmetric !Encryption !Signatures |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |- |[[Age]] |Asymmetric and Symmetric |Yes |No |- |[[Minisign]] |Asymmetric |No |Yes |- |[[Gocryptfs]] |Symmetric |Yes |No |- |[[Cryptomator]] |Symmetric |Yes |No |} {| class="wikitable mw-collapsible" |+Encryption Algorithms !Name !AES !ChaCha20 !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |Yes<ref name=":1" /> |No |No |Yes<ref>{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |N/A |N/A |N/A |No |Yes |No |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |N/A |N/A |N/A |N/A |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |N/A |N/A |N/A |N/A |No |} Note that <code>N/A</code> means that the software does not use said type of algorithm. 8652b9b1de9b4ff2b850776b1767bd71cac1dc56 5139 5137 2026-05-24T23:24:05Z Uniolo 345 Separated "Encryption algorithms" into symmetric and asymmetric categories. wikitext text/x-wiki {{Work In Progress}} The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ Types of algorithms !Name !Symmetric or Asymmetric !Encryption !Signatures |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |- |[[Age]] |Asymmetric and Symmetric |Yes |No |- |[[Minisign]] |Asymmetric |No |Yes |- |[[Gocryptfs]] |Symmetric |Yes |No |- |[[Cryptomator]] |Symmetric |Yes |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref>{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |N/A |No |Yes |No |No |} 647e1f426bc236db46028eacea74f06df7f5cc07 5141 5139 2026-05-24T23:40:00Z Uniolo 345 Added stated purpose for purpose of the program stated on the website or README. wikitext text/x-wiki {{Work In Progress}} The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" /> |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref> |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |N/A |No |Yes |No |No |} e74a3cdbeabc06b1ef3dc3a6bacdb5e1bb423689 5142 5141 2026-05-24T23:41:30Z Uniolo 345 Changed N/A to No in X25519 support for Minisign wikitext text/x-wiki {{Work In Progress}} The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" /> |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref> |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} b832181dfc4be266454e25cb7fa33bede239bd15 5143 5142 2026-05-24T23:47:04Z Uniolo 345 Add "software" and "comparison" categories wikitext text/x-wiki {{Work In Progress}} The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" /> |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref> |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} <references /> [[Category:Software]] [[Category:Comparison]] 3645d19d3ba733bce1202f670ad92f01f68cb09b 5145 5143 2026-05-24T23:48:24Z Uniolo 345 Added missing period to stated purpose to stay consistent wikitext text/x-wiki {{Work In Progress}} The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} <references /> [[Category:Software]] [[Category:Comparison]] 57fd3333dcabec760067d703b18ad291d030728d 5146 5145 2026-05-24T23:48:54Z Uniolo 345 Replace work in progress with stub wikitext text/x-wiki {{Stub}} The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} <references /> [[Category:Software]] [[Category:Comparison]] 09c9908306f0a09642ef9781498b1a9f7e96f4d6 5148 5146 2026-05-24T23:59:17Z Uniolo 345 Moved symmetric below asymmetric, so I can add a section for key derivation. wikitext text/x-wiki {{Stub}} The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |} <references /> [[Category:Software]] [[Category:Comparison]] d4a1922fcbd2e209f7498d5b8393d0a10ab95913 5149 5148 2026-05-25T00:09:37Z Uniolo 345 Removed stub. Basically everything uses scrypt for key derivation so it wouldn't be a good point to compare. wikitext text/x-wiki The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |} <references /> [[Category:Software]] [[Category:Comparison]] b5116417b65714ab0265f43489b2e650bc242801 2 1225 5147 2026-05-24T23:53:23Z S 394 An introduction on why this account exists. wikitext text/x-wiki I found it quite hard to read FOSS Wiki on its default settings, so this account was created to sync my [[Special:Preferences|reading preferences]] across signed-in devices. 238cf95e8bc6c5b48ae3c4b911d24090f472f9cc 0 1026 5150 5106 2026-05-25T01:06:40Z Ping 374 categorizing this under package managers as well wikitext text/x-wiki [[Category:Software]] [[Category:Package Managers]] {{SoftwareInfobox |image = [[File:Debian_Nala.png|300px|center|thumb]] |caption = Nala install screenshot |title = Nala |releasestatus = Maintained |lastrelease = v0.16.0, 2025-04-21 |languages = [[Python]] |developers = [[https://gitlab.com/volian Volian]] |website = [[https://gitlab.com/volian/nala Nala Gitlab]] }} Nala is a front-end of libapt-pkg, which is a part of the [[apt|APT]] packaging managing suite used by [[Debian]]-based [[Linux Distributions|Linux distributions]]. Nala is designed to provide prettier output and speed up [[package]] installations with parallel downloads alongside a mirror ranking feature. As a front-end, Nala can only be used on systems with the apt package installed. Currently, Nala is undergoing a language rewrite from [[Python]] to [[Rust]]<ref>{{Cite|url=https://gitlab.com/volian/nala/-/tree/nala-rs|title=nala-rs branch: Nala's GitLab|accessdate=2026-05-24}}</ref>. == Limitations == * Nala requires at least Debian 11/Bullseye or Ubuntu 19.04/Disco Dingo or newer, older releases do not have required packages and [[Python]] versions available.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/wikis/Installation|title=Installation: Nala's Gitlab Wiki|accessdate=2026-05-23}}</ref> * Nala limits parallel downloads connections to three per mirror.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/blob/f6fc96c7afcb02b277d5811cfa6703e368cec317/README.rst|title=README: Nala's Gitlab repository|year=2024|accessdate=2026-05-23}}</ref> * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding packages (pauses certain packages' updates) or showing reverse dependencies (packages depending on a certain package). To hold packages consider using the apt-mark tool instead. == Usage<ref>{{Cite|url=http://manpages.debian.org/trixie/nala/nala.8.en.html|title=Nala User Manual: Debian Manpages|year=2025|accessdate=2026-05-23}}</ref> == The following shows common Nala [[command]]s, which are mostly similar to that of the apt command. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of available packages and their versions |- |<code>nala upgrade</code> |Updates and upgrades system's packages, alongside removing unused dependencies |- |<code>nala full-upgrade</code> |Updates and upgrades system's packages, installing new packages and removing old ones as needed |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala clean</code> |Removes unused package caches within the system |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages available for installation. Can list installed packages with <code>nala list --installed</code> |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands (transaction) alongside its ID |- |<code>nala history info <ID></code> |Show the info of a specific transaction |- |<code>nala history undo <ID></code> |Undo the commands ran under a specific transaction |- |<code>nala history redo <ID></code> |Redo the commands ran under a specific transaction |} <references /> bba7192aa4a52e9d6e92c87647b5408ed643e102 5159 5150 2026-05-25T01:36:55Z Ping 374 Added References wikitext text/x-wiki [[Category:Software]] [[Category:Package Managers]] {{SoftwareInfobox |image = [[File:Debian_Nala.png|300px|center|thumb]] |caption = Nala install screenshot |title = Nala |releasestatus = Maintained |lastrelease = v0.16.0, 2025-04-21 |languages = [[Python]] |developers = [[https://gitlab.com/volian Volian]] |website = [[https://gitlab.com/volian/nala Nala Gitlab]] }} Nala is a front-end of libapt-pkg, which is a part of the [[apt|APT]] packaging managing suite used by [[Debian]]-based [[Linux Distributions|Linux distributions]]. Nala is designed to provide prettier output and speed up [[package]] installations with parallel downloads alongside a mirror ranking feature. As a front-end, Nala can only be used on systems with the apt package installed. Currently, Nala is undergoing a language rewrite from [[Python]] to [[Rust]]<ref>{{Cite|url=https://gitlab.com/volian/nala/-/tree/nala-rs|title=nala-rs branch: Nala's GitLab|accessdate=2026-05-24}}</ref>. == Limitations == * Nala requires at least Debian 11/Bullseye or Ubuntu 19.04/Disco Dingo or newer, older releases do not have required packages and [[Python]] versions available.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/wikis/Installation|title=Installation: Nala's Gitlab Wiki|accessdate=2026-05-23}}</ref> * Nala limits parallel downloads connections to three per mirror.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/blob/f6fc96c7afcb02b277d5811cfa6703e368cec317/README.rst|title=README: Nala's Gitlab repository|year=2024|accessdate=2026-05-23}}</ref> * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding packages (pauses certain packages' updates) or showing reverse dependencies (packages depending on a certain package). To hold packages consider using the apt-mark tool instead. == Usage<ref>{{Cite|url=http://manpages.debian.org/trixie/nala/nala.8.en.html|title=Nala User Manual: Debian Manpages|year=2025|accessdate=2026-05-23}}</ref> == The following shows common Nala [[command]]s, which are mostly similar to that of the apt command. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of available packages and their versions |- |<code>nala upgrade</code> |Updates and upgrades system's packages, alongside removing unused dependencies |- |<code>nala full-upgrade</code> |Updates and upgrades system's packages, installing new packages and removing old ones as needed |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala clean</code> |Removes unused package caches within the system |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages available for installation. Can list installed packages with <code>nala list --installed</code> |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands (transaction) alongside its ID |- |<code>nala history info <ID></code> |Show the info of a specific transaction |- |<code>nala history undo <ID></code> |Undo the commands ran under a specific transaction |- |<code>nala history redo <ID></code> |Redo the commands ran under a specific transaction |} == References == <references /> 0dc0b22205d0e0f4f402512b7f63d7f4f3e4a42f 0 175 5152 4937 2026-05-25T01:16:04Z Ping 374 Categorizing Pacman as software wikitext text/x-wiki {{Needs Citations}} {{SoftwareInfobox | title = Pacman | releasestatus = Maintained | lastrelease = 7.1.0, 2025-11-01 | languages = [[C]] | developers = [[Arch Linux]] | website = [https://pacman.archlinux.page pacman.archlinux.page] }} [[Category:Software]] [[Category:Package Managers]] [[File:Pacman 401.png|thumb|[[Pacman]]]] The [[Linux Distributions|Linux distribution]] [[Arch Linux]] and its derivatives usually use a [[Package Manager|package manager]] called Pacman, invokable as <code>pacman</code>. More information can be found on the relevant Arch Wiki page, located [https://wiki.archlinux.org/title/pacman here]. Pacman is a binary distribution package manager, and only has builds for x86_64, although some have tried creating alternative ports. The most common usages of Pacman are to install, search, update, and query packages. == Flags == Pacman uses a flag scheme involving one main flag (uppercase) and many minor flags (lowercase). The most commonly used main flags are <code>-S</code> for "sync", <code>-R</code> for removal, and <code>-Q</code> for querying. Sync and query are similar, but sync looks for (and installs) packages from the Arch Linux repositories, while query only finds currently installed packages. Minor flags may be appended to the main flags, slightly changing their behavior. For example, <code>-Su</code> upgrades a package and <code>-Ss</code> searches for them, both via the online repositories. == Usage == The following are several common usages of Pacman. In all cases where applicable, the given operation can also be performed on multiple packages at once by simply writing them all out separated by a space, i.e. <code>pacman -S package1 package2</code> {| class="wikitable" |+Common Pacman Commands !Command !Description |- |<code>pacman -S package-name</code> |(Re)install a given package |- |<code>pacman -Ss search-term</code><code>pacman -Qs search-term</code> |Search the online repositories or local package database for a given package |- |<code>pacman -Si package-name</code><code>pacman -Qi package-name</code> |Get info about a package from the online repositories or local package database |- |<code>pacman -Sy package-name</code> |Install the latest version of a package without upgrading the entire system '''(not recommended, causes a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade])''' |- |<code>pacman -Syu</code> |Update system's packages; Listed packages will also be installed alongside the update |- |<code>pacman -Syyu</code> |Update system's packages, forcing a listing update '''(not recommended)''' |- |<code>pacman -R package-name</code> |Remove a given package |- |<code>pacman -Rs package-name</code> |Remove a package and its unneeded dependencies |- |<code>pacman -Rns package-name</code> |Remove a package, it's dependencies, and any global configuration files |- |<code>pacman -Rsc package-name</code> |Remove a package and all of its dependencies, even if need by other packages '''(not recommended)''' |- |<code>pacman -Qdt</code> |List packages installed as dependencies that are no longer needed as dependencies (orphans) |} == Removing Packages == The recommended ways to remove packages are <code>pacman -R package-name</code>, <code>pacman -Rs package-name</code>, and <code>pacman -Rns package-name</code>. The functionality of each of these commands is described within the table under [[#Common Usages]]. When removing packages, <code>-Rsc</code> should be used sparingly. If you wish to remove unneeded dependencies to save space (or for other reasons), use <code>-Rs</code>, or simply remove with <code>-R</code> and find the orphaned packages using <code>-Qdt</code>. If the <code>q</code> flag is added, the output will be "quiet" and can be chained with another <code>-R</code> command, i.e. <code>pacman -R $(pacman -Qdtq)</code> == Dangerous Commands<ref>[https://wiki.archlinux.org/title/system_maintenance#Avoid_certain_pacman_commands System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> == TODO: Include information about the following arguments: -Sy, -Syyu, -Rsc == Repositories == {| class="wikitable" |+ !Repository !Purpose |- |core |Packages necessary for a base Arch installation |- |extra |Packages that are not critical to a functioning Arch system |- |multilib |32 bit (x86) packages that are not critical to a functioning Arch system |} === Testing repositories === Testing repositories allow users to ''test'' software before it's pushed to all users. The [https://bbs.archlinux.org/viewforum.php?id=49 Testing Repo Forum] should be used to report any bugs encountered while on the testing repositories. ==== Using Testing ==== To begin using testing, uncomment the <code>[<repo>-testing]</code> entries in <code>/etc/pacman.conf</code> as well as their corresponding <code>Include = /etc/pacman.d/mirrorlist</code> entries. All testing repositories should be enabled at once to avoid a [https://wiki.archlinux.org/title/system_maintenance#Partial_upgrades_are_unsupported partial upgrade]. == See Also == [https://wiki.archlinux.org/title/pacman pacman - ArchWiki] [https://pacman.archlinux.page/ Pacman Home Page] == References == 354fb906938e6e8e6aab1a887d4beee042701620 0 1084 5153 4427 2026-05-25T01:17:55Z Ping 374 Added categories wikitext text/x-wiki [[Category:Software]] [[Category:Package_Managers]] '''Alpine Package Keeper (apk)''' (not to be confused with <code>.apk</code> installation files found on android systems) is Alpine's official package manager. Coded in C, its primary goal is to manage packages on a user's systems while staying minimal. Packages on the distribution's repositories come in 3 official repository: <code>main</code>, <code>community</code>, and <code>testing</code>;<ref>[https://wiki.alpinelinux.org/wiki/Repositories#Official_repositories Repositories - Official Repositories], ''Alpine Wiki'', The Alpine Team (1) (Accessed 2/12/2026 20:39 UTC-5)</ref> however, the user is free to enable and disable them freely.<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], ''Alpine User Handbook,'' The Alpine Team (1) (Accessed 02/10/2026 18:00 UTC-5)</ref> == Overview == The <code>apk-tools</code> package provides the package manager and other features, the table below shows possible commands.<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper Alpine Package Keeper], ''Alpine Wiki'', The Alpine Team (1) (Accessed 2/12/2026 20:40 UTC-5)</ref> {| class="wikitable" |+Package Management Via <code>apk</code> !Command !Usage !Overview |- |<code>add</code> |<code>apk add <package_name></code> |Adds a package to the system and modifies WORLD file, commits changes afterwards |- |<code>del</code> |<code>apk del <package_name></code> |Deletes a package from the system and modifies WORLD file, commits changes afterwards |- |<code>fix</code> |<code>apk fix <package_name></code> |Fixes (attempts to) a package via reinstall and/or upgrading without modifying WORLD |- |<code>update</code> |<code>apk update</code> |Updates repository index, Typically ran after modifying repository file |- |<code>upgrade</code> |<code>apk upgrade <optional_package></code> |Upgrade packages on the system, optionally upgrade only one package by specifying it. |- |<code>cache</code> |<code>apk cache <option></code> |Manages the local package cache |- |<code>query</code> |<code>apk query <package_name></code> |Combines <code>info</code>, <code>list</code>, and <code>search</code> commands through your installed packages and outputs information in a human-readable format |- |<code>info</code> |<code>apk info [optional_flag] <optinal_package></code> |Lists all information about installed packages and allows you to search through it with given flags |- |More commands... | | |} == Managing Packages == Official software on the Alpine Linux repositories are named "''a-packs''" and have the extension <code>.apk</code> (Not to be confused with Android's APK installation files). You can edit which repositories you'd like to access by editing <code>/etc/apk/repositories</code>, commenting/uncommenting any repository you'd like. Upon saving the file, run <code>apk update</code> to update the repository index.<ref>[https://wiki.alpinelinux.org/wiki/Repositories#Managing_repositories Repositories - Managing Repositories], ''Alpine Wiki'', The Alpine Team (3) (Accessed 2/12/2026 20:48 UTC-5)</ref> APK will automatically echo how many packages are currently available on enabled repositories upon completing the updates.<ref>[https://wiki.alpinelinux.org/wiki/Repositories Repositories], ''Alpine Wiki'', The Alpine Team (1) (Accessed 2/12/2026 20:48 UTC-5)</ref> === World === The <code>WORLD</code> file on Alpine Linux (located at <code>/etc/apk/world</code>) describes desired system states in a plain text file and uses unique syntax to configure package installation. Should you edit the file, run <code>apk fix</code> to apply changes. The <code>world</code> file must be in order upon running <code>apk fix</code>, else the package manager refuses to apply any constraints to the adjusted file; hence why APK will never leave a system unbootable.<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#World Alpine Package Keeper - World], ''Alpine Wiki,'' The Alpine Team (1) (Accessed 2/12/2026 20:56 UTC-5)</ref> === Configuring APK === APK allows you to configure the package manager by adjusting/editing the <code>/etc/config/apk</code> (assuming the user has made it [make the file via <code>touch /etc/config/apk</code> with proper permissions]) will override the default APK config located in <code>/lib/apk/config</code>. <ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#Configuration_file Alpine Package Keeper - Configuration File], ''Alpine Wiki'', The Alpine Team (11) (Accessed 2/12/2026 21:10 UTC-5)</ref> f058ab9796ee06032460c0ef3e248aa4a4490d5c 0 272 5154 3596 2026-05-25T01:19:10Z Ping 374 categorizing dnf as software wikitext text/x-wiki [[Category:Software]] [[Category:Package Managers]] {{Cleanup|The article does not reflect the latest information on dnf5}}{{Cleanup|is that <code>dnf</code>'s importance is described in a pretty biased way, and some parts of this page feels somewhat AI-generated.}}{{Needs Citations}} {{SoftwareInfobox | image = [[File:DNF Command Line Interface.png|frameless]] | caption = Invoking <code>sudo dnf upgrade</code> on a terminal with <code>dnf4</code> | title = DNF | releasestatus = Maintained | lastrelease = <code>dnf5</code> 5.2.13.1 (2025-04-25) | languages = [[C++]] | developers = [[Fedora]] and Red Hat, et al. | website = [https://github.com/rpm-software-management/dnf5/ github.com/rpm-software-management/dnf5] }} '''DNF''', short for ''Dandified YUM'', is a software package manager for Linux distributions such as [[Fedora]], [[CentOS]], and [[RHEL]] (Red Hat Enterprise Linux). It was designed to be a better version of the traditional [[YUM]] (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other [[RPM]]-based distributions. === Development of DNF5 === The development of DNF5, the next-generation Fedora package manager, began in early 2020 as a complete rewrite of the existing DNF4 codebase to address architectural and performance limitations:<ref>[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NWSURJRGZAIIMNZJT244DHDPOG2PBQXZ/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> <blockquote> We've managed to drop a lot of redundant code across the whole DNF stack in the past years, but we have reached a point when it's nearly impossible to consolidate the code any further without breaking the API/ABI. Especially with PackageKit being dead<ref>[https://blogs.gnome.org/hughsie/2019/02/14/packagekit-is-dead-long-live-well-something-else/ PackageKit is dead, long live, well, something else], hughsie, 2019 (Accessed 2025-06-21)</ref>, we can't move with the old "libhif" API in libdnf, because making any bigger changes to PackageKit is clearly out of scope. </blockquote> The announcement of DNF5 development was made in March 2020, with a roadmap targeting major API changes and early development snapshots throughout 2020, aiming for inclusion in Fedora 34 and stable replacement of DNF4 by early 2021.<ref>[https://lwn.net/Articles/814066/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> Key motivations for DNF5's development included the need to modernize the codebase, which had become cluttered and difficult to maintain, and to move away from dependencies on Python and older APIs. The new design emphasized a fully featured package manager written primarily in C++ for improved performance, reduced resource usage, and a smaller install size compared to DNF4.<ref>[https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5#Benefit_to_Fedora Make DNF5 The Default], Jaroslav Mracek, 2022 (Accessed 2025-06-21)</ref> DNF5 also aimed to unify the software management tools in Fedora by replacing DNF and Microdnf, and providing a new daemon alternative to PackageKit.<ref name=":0">[https://ostechnix.com/dnf5-package-manager-introduction/ Introduction to DNF5: The Next-Generation Fedora Package Manager], Sk, 2025 (Accessed: 2025-06-21)</ref> DNF5 introduced a new core library (libdnf5), revamped plugin systems, enhanced modularity support, and a streamlined command-line interface with improved user experience. The development process was marked by an emphasis on openness, community involvement, and transparent upstream issue tracking to foster broader collaboration. By Fedora 38, DNF5 was available, and it became the default package manager in Fedora 41, fully replacing the older DNF.<ref name=":0" /> == Features == ==== Dependency Resolution ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== Transaction History ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== Modularity Dupport ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== Plugin System ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== Parallel Downloads ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== Package Groups ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: * Installing Packages: <code>dnf install <package_name></code> * Updating Packages: <code>dnf update</code> * Removing Packages: <code>dnf remove <package_name></code> * Listing Installed Packages: <code>dnf list installed</code> * Searching for Packages: <code>dnf search <keyword></code> * Managing Repositories: <code>dnf repolist</code>, <code>dnf config-manager</code> * Viewing Transaction History: <code>dnf history</code> == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. == References == 0070c3b36a6abc1ef28290c40120f81ae35e62b8 0 1212 5158 5045 2026-05-25T01:33:41Z Matthias von Schwarzwald 361 Typos wikitext text/x-wiki Firefox (officially Mozilla Firefox) is a free and open-source web browser developed by the [[Mozilla Foundation]] and its subsidiary, the [[Mozilla Corporation]]. It was released on November 9, 2004<ref>{{Cite|url=https://doi.org/10.7717/peerj-cs.28|title=The rise of Chrome|author=Jonathan Tamary, Dror G. Feitelson|year=2015|accessdate=May 24, 2026}}</ref> and serves as a successor to the [[Netscape]] Navigator after [[Netscape]] released its source code to the open-source community in the late 1990s<ref>{{Cite|url=https://nominet.uk/wp-content/uploads/2024/09/25-years-of-the-web-report.pdf|title=The story of the web|author=Jack Schofield|year=2024|accessdate=May 24, 2026}}</ref>. Firefox famously launched to provide a secure, user-centric alternative during the height of the "browser wars" against proprietary dominance<ref>{{Cite|url=https://doi.org/10.1016/j.intmar.2009.04.008|title=CASE: Mozilla vs. Godzilla — The Launch of the Mozilla Firefox Browser|author=Sandeep Krishnamurthy|year=2009|accessdate=May 24, 2026}}</ref>. Today, it stands out as one of the few major independant browsers that does not rely on [[Google]]'s [[Chromium]] rendering engine, instead utilizing its own open-source engine, [[Gecko]]<ref>{{Cite|url=https://doi.org/10.48009/2_iis_2007_478-483|title=INTERNET EXPLORER AND FIREFOX: WEB BROWSER FEATURES COMPARISION AND THEIR FUTURE|author=Siwat Saibua, Joon-Yeoul Oh, Richard A. Aukerman|year=2007|accessdate=May 24, 2026}}</ref>. == Controversies and Criticism == === 2025 Terms of Service and Data Licensing Backlash === On February 27, 2025, [[Mozilla]] introducted their new official Firefox Terms of Use and updated its Privacy Notice<ref name=":0">{{Cite|url=https://www.zdnet.com/article/the-firefox-i-loved-is-gone-how-to-protect-your-privacy-on-it-now/|title=The Firefox I loved is gone - how to protect your privacy on it now|author=Steven Vaughan-Nichols|year=2025|accessdate=May 24, 2026}}</ref>. That meant that for the first time, [[Mozilla]] had a legally binding privacy policy for Firefox users<ref name=":0" />. This change received a lot of backlash from privacy advocates and so [[Mozilla]] changed their Firefox terms again after the backlash<ref>{{Cite|url=https://thehackernews.com/2025/03/mozilla-updates-firefox-terms-again.html|title=Mozilla Updates Firefox Terms Again After Backlash Over Broad Data License Language|author=Ravie Lakshmanan|year=2025|accessdate=May 24, 2026}}</ref>. [[Mozilla]] changed "''When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox.''" to "''You give Mozilla the rights necessary to operate Firefox. This includes processing your data as we describe in the Firefox Privacy Notice. It also includes a nonexclusive, royalty-free, worldwide license for the purpose of doing as you request with the content you input in Firefox. This does not give Mozilla any ownership in that content.''"<ref>{{Cite|url=https://www.mozilla.org/en-US/about/legal/terms/firefox/#you-give-mozilla-certain-rights-and-permissions|title=Firefox Terms of Use|author=Mozilla|year=2025|accessdate=May 24, 2026}}</ref> 64120351513c4d8b16091f7df368c591ba4605d6 5160 5158 2026-05-25T01:37:00Z Matthias von Schwarzwald 361 Add categories wikitext text/x-wiki Firefox (officially Mozilla Firefox) is a free and open-source web browser developed by the [[Mozilla Foundation]] and its subsidiary, the [[Mozilla Corporation]]. It was released on November 9, 2004<ref>{{Cite|url=https://doi.org/10.7717/peerj-cs.28|title=The rise of Chrome|author=Jonathan Tamary, Dror G. Feitelson|year=2015|accessdate=May 24, 2026}}</ref> and serves as a successor to the [[Netscape]] Navigator after [[Netscape]] released its source code to the open-source community in the late 1990s<ref>{{Cite|url=https://nominet.uk/wp-content/uploads/2024/09/25-years-of-the-web-report.pdf|title=The story of the web|author=Jack Schofield|year=2024|accessdate=May 24, 2026}}</ref>. Firefox famously launched to provide a secure, user-centric alternative during the height of the "browser wars" against proprietary dominance<ref>{{Cite|url=https://doi.org/10.1016/j.intmar.2009.04.008|title=CASE: Mozilla vs. Godzilla — The Launch of the Mozilla Firefox Browser|author=Sandeep Krishnamurthy|year=2009|accessdate=May 24, 2026}}</ref>. Today, it stands out as one of the few major independant browsers that does not rely on [[Google]]'s [[Chromium]] rendering engine, instead utilizing its own open-source engine, [[Gecko]]<ref>{{Cite|url=https://doi.org/10.48009/2_iis_2007_478-483|title=INTERNET EXPLORER AND FIREFOX: WEB BROWSER FEATURES COMPARISION AND THEIR FUTURE|author=Siwat Saibua, Joon-Yeoul Oh, Richard A. Aukerman|year=2007|accessdate=May 24, 2026}}</ref>. == Controversies and Criticism == === 2025 Terms of Service and Data Licensing Backlash === On February 27, 2025, [[Mozilla]] introducted their new official Firefox Terms of Use and updated its Privacy Notice<ref name=":0">{{Cite|url=https://www.zdnet.com/article/the-firefox-i-loved-is-gone-how-to-protect-your-privacy-on-it-now/|title=The Firefox I loved is gone - how to protect your privacy on it now|author=Steven Vaughan-Nichols|year=2025|accessdate=May 24, 2026}}</ref>. That meant that for the first time, [[Mozilla]] had a legally binding privacy policy for Firefox users<ref name=":0" />. This change received a lot of backlash from privacy advocates and so [[Mozilla]] changed their Firefox terms again after the backlash<ref>{{Cite|url=https://thehackernews.com/2025/03/mozilla-updates-firefox-terms-again.html|title=Mozilla Updates Firefox Terms Again After Backlash Over Broad Data License Language|author=Ravie Lakshmanan|year=2025|accessdate=May 24, 2026}}</ref>. [[Mozilla]] changed "''When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox.''" to "''You give Mozilla the rights necessary to operate Firefox. This includes processing your data as we describe in the Firefox Privacy Notice. It also includes a nonexclusive, royalty-free, worldwide license for the purpose of doing as you request with the content you input in Firefox. This does not give Mozilla any ownership in that content.''"<ref>{{Cite|url=https://www.mozilla.org/en-US/about/legal/terms/firefox/#you-give-mozilla-certain-rights-and-permissions|title=Firefox Terms of Use|author=Mozilla|year=2025|accessdate=May 24, 2026}}</ref> <references /> [[Category:Software]] [[Category:Browsers]] 3e85a9d42992bf7c8a65ba0c89c0245c38942b4f 5161 5160 2026-05-25T01:38:18Z Ping 374 Separating References with a header wikitext text/x-wiki Firefox (officially Mozilla Firefox) is a free and open-source web browser developed by the [[Mozilla Foundation]] and its subsidiary, the [[Mozilla Corporation]]. It was released on November 9, 2004<ref>{{Cite|url=https://doi.org/10.7717/peerj-cs.28|title=The rise of Chrome|author=Jonathan Tamary, Dror G. Feitelson|year=2015|accessdate=May 24, 2026}}</ref> and serves as a successor to the [[Netscape]] Navigator after [[Netscape]] released its source code to the open-source community in the late 1990s<ref>{{Cite|url=https://nominet.uk/wp-content/uploads/2024/09/25-years-of-the-web-report.pdf|title=The story of the web|author=Jack Schofield|year=2024|accessdate=May 24, 2026}}</ref>. Firefox famously launched to provide a secure, user-centric alternative during the height of the "browser wars" against proprietary dominance<ref>{{Cite|url=https://doi.org/10.1016/j.intmar.2009.04.008|title=CASE: Mozilla vs. Godzilla — The Launch of the Mozilla Firefox Browser|author=Sandeep Krishnamurthy|year=2009|accessdate=May 24, 2026}}</ref>. Today, it stands out as one of the few major independant browsers that does not rely on [[Google]]'s [[Chromium]] rendering engine, instead utilizing its own open-source engine, [[Gecko]]<ref>{{Cite|url=https://doi.org/10.48009/2_iis_2007_478-483|title=INTERNET EXPLORER AND FIREFOX: WEB BROWSER FEATURES COMPARISION AND THEIR FUTURE|author=Siwat Saibua, Joon-Yeoul Oh, Richard A. Aukerman|year=2007|accessdate=May 24, 2026}}</ref>. == Controversies and Criticism == === 2025 Terms of Service and Data Licensing Backlash === On February 27, 2025, [[Mozilla]] introducted their new official Firefox Terms of Use and updated its Privacy Notice<ref name=":0">{{Cite|url=https://www.zdnet.com/article/the-firefox-i-loved-is-gone-how-to-protect-your-privacy-on-it-now/|title=The Firefox I loved is gone - how to protect your privacy on it now|author=Steven Vaughan-Nichols|year=2025|accessdate=May 24, 2026}}</ref>. That meant that for the first time, [[Mozilla]] had a legally binding privacy policy for Firefox users<ref name=":0" />. This change received a lot of backlash from privacy advocates and so [[Mozilla]] changed their Firefox terms again after the backlash<ref>{{Cite|url=https://thehackernews.com/2025/03/mozilla-updates-firefox-terms-again.html|title=Mozilla Updates Firefox Terms Again After Backlash Over Broad Data License Language|author=Ravie Lakshmanan|year=2025|accessdate=May 24, 2026}}</ref>. [[Mozilla]] changed "''When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox.''" to "''You give Mozilla the rights necessary to operate Firefox. This includes processing your data as we describe in the Firefox Privacy Notice. It also includes a nonexclusive, royalty-free, worldwide license for the purpose of doing as you request with the content you input in Firefox. This does not give Mozilla any ownership in that content.''"<ref>{{Cite|url=https://www.mozilla.org/en-US/about/legal/terms/firefox/#you-give-mozilla-certain-rights-and-permissions|title=Firefox Terms of Use|author=Mozilla|year=2025|accessdate=May 24, 2026}}</ref> ==References== <references /> [[Category:Software]] [[Category:Browsers]] 353eeb0d63d3065fee65b9e41710cdf7cf78665f 5169 5161 2026-05-25T02:01:30Z Ping 374 Added software info box wikitext text/x-wiki {{SoftwareInfobox |image=[[File:Firefox_logo,_2019.svg|thumb]] |caption=Firefox logo since June 2019 |title=Mozilla Firefox |releasestatus=Maintained |lastrelease=151.0.1, 2026-05-21 |firstrelease=1.0, 2004-11-09 |languages=[[C++]], [[C]], [[JavaScript]] |developers=[https://mozilla.org Mozilla] |website=[https://www.firefox.com firefox.com] }} Firefox (officially Mozilla Firefox) is a free and open-source web browser developed by the [[Mozilla Foundation]] and its subsidiary, the [[Mozilla Corporation]]. It was released on November 9, 2004<ref>{{Cite|url=https://doi.org/10.7717/peerj-cs.28|title=The rise of Chrome|author=Jonathan Tamary, Dror G. Feitelson|year=2015|accessdate=May 24, 2026}}</ref> and serves as a successor to the [[Netscape]] Navigator after [[Netscape]] released its source code to the open-source community in the late 1990s<ref>{{Cite|url=https://nominet.uk/wp-content/uploads/2024/09/25-years-of-the-web-report.pdf|title=The story of the web|author=Jack Schofield|year=2024|accessdate=May 24, 2026}}</ref>. Firefox famously launched to provide a secure, user-centric alternative during the height of the "browser wars" against proprietary dominance<ref>{{Cite|url=https://doi.org/10.1016/j.intmar.2009.04.008|title=CASE: Mozilla vs. Godzilla — The Launch of the Mozilla Firefox Browser|author=Sandeep Krishnamurthy|year=2009|accessdate=May 24, 2026}}</ref>. Today, it stands out as one of the few major independant browsers that does not rely on [[Google]]'s [[Chromium]] rendering engine, instead utilizing its own open-source engine, [[Gecko]]<ref>{{Cite|url=https://doi.org/10.48009/2_iis_2007_478-483|title=INTERNET EXPLORER AND FIREFOX: WEB BROWSER FEATURES COMPARISION AND THEIR FUTURE|author=Siwat Saibua, Joon-Yeoul Oh, Richard A. Aukerman|year=2007|accessdate=May 24, 2026}}</ref>. == Controversies and Criticism == === 2025 Terms of Service and Data Licensing Backlash === On February 27, 2025, [[Mozilla]] introducted their new official Firefox Terms of Use and updated its Privacy Notice<ref name=":0">{{Cite|url=https://www.zdnet.com/article/the-firefox-i-loved-is-gone-how-to-protect-your-privacy-on-it-now/|title=The Firefox I loved is gone - how to protect your privacy on it now|author=Steven Vaughan-Nichols|year=2025|accessdate=May 24, 2026}}</ref>. That meant that for the first time, [[Mozilla]] had a legally binding privacy policy for Firefox users<ref name=":0" />. This change received a lot of backlash from privacy advocates and so [[Mozilla]] changed their Firefox terms again after the backlash<ref>{{Cite|url=https://thehackernews.com/2025/03/mozilla-updates-firefox-terms-again.html|title=Mozilla Updates Firefox Terms Again After Backlash Over Broad Data License Language|author=Ravie Lakshmanan|year=2025|accessdate=May 24, 2026}}</ref>. [[Mozilla]] changed "''When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox.''" to "''You give Mozilla the rights necessary to operate Firefox. This includes processing your data as we describe in the Firefox Privacy Notice. It also includes a nonexclusive, royalty-free, worldwide license for the purpose of doing as you request with the content you input in Firefox. This does not give Mozilla any ownership in that content.''"<ref>{{Cite|url=https://www.mozilla.org/en-US/about/legal/terms/firefox/#you-give-mozilla-certain-rights-and-permissions|title=Firefox Terms of Use|author=Mozilla|year=2025|accessdate=May 24, 2026}}</ref> ==References== <references /> [[Category:Software]] [[Category:Browsers]] 63a27a45bcd22aa1c4bff062aa5c1c006e9878ad 0 480 5164 5025 2026-05-25T01:57:04Z 2elevation 115 Fix a reference wikitext text/x-wiki {{DistributionInfobox |title=Oreon Linux |image=[[File:OreonLogo_2026.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop, Server |architectures = aarch64, x86_64 |website=[https://oreonhq.com/ oreonhq.com]}} [[Category:Linux Distributions]] [[File:Oreon 10 desktop.png|thumb|Oreon 10 default desktop since Build 2504 running GNOME]] '''Oreon Linux''' is a [[Linux Distributions|Linux Distribution]] developed by Oreon HQ. Originally based on AlmaLinux, the project modifies its enterprise base to provide a practical, out-of-the-box desktop experience, importing missing system packages from [[Fedora|Fedora Linux]].<ref>[https://copr.fedorainfracloud.org/coprs/brandonlester/oreon-10/ brandonlester/oreon-10 Copr Repository], Fedora Copr (Accessed: 2026-05-23)</ref> === History === The first release, ''Oreon Lime (R1/R1.1)'', launched on January 1, 2024.<ref>[https://boostyconnect.com/oreon-lime-r1-lifecycle/ Oreon Lime R1/R1.1 Lifecycle], BoostyConnect Technologies (Accessed: 2025-08-09)</ref> It was replaced on February 18, 2024, by ''Oreon Lime (R2)'', which moved the base to AlmaLinux for long-term support capabilities.<ref>[https://wiki.oreonhq.com/docs/Support-Timelines/oreon-lime-r2-support-timeline Oreon Lime (R2) Support Timeline], Oreon Wiki (Accessed: 2026-05-23)</ref> This early release shipped with GNOME 40 and Linux kernel 5.14, receiving coverage from outlets like ''The Register''.<ref>[https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/ Oreon Lime is AlmaLinux with a desktop twist], Liam Proven, The Register, 2024-08-20</ref> ==== Oreon 10 Build Cycle ==== Oreon 10 officially launched on December 12, 2024, with the original release (Build 2412), introducing KDE Plasma 6 alongside Linux kernel 6.11, which updated to kernel 6.12 shortly after. Incremental system updates and maintenance fixes are pushed through a build-number system formatted as the first two digits of the year followed by the month.<ref>[https://wiki.oreonhq.com/docs/Support-Timelines/oreon-10-support-timeline Oreon 10 Support Timeline], Oreon Wiki (Accessed: 2026-05-23)</ref> Build 2501 launched on January 1, 2025, followed by Build 2502 on February 12, 2025. Build 2503 released shortly after on February 28, 2025. Build 2504 was pushed on March 13, 2025, which switched the default desktop choice back to GNOME following user criticism regarding the interface shift. Later maintenance milestones included Build 2507 on July 14, 2025, and Build 2510 on October 12, 2025. The cycle continued into the following year with Build 2602 on February 9, 2026. The current supported build for Oreon 10 is Build 2603, which released on March 1, 2026, and replaced the older Anaconda installer with a custom installer called Centrio while changing several other default configurations.<ref>[https://distrowatch.com/?newsid=12744 Oreon 10-2603 DistroWatch Announcement], Oreon HQ (Accessed: 2026-05-23)</ref> === Future Development === Following updates from the Oreon team and coverage by BetaNews, development focus has moved toward the next major release, Oreon 11. The upcoming release will drop its reliance on AlmaLinux entirely. Instead, the distribution is moving toward becoming an independent RPM-based Linux distribution to gain direct control over its repository infrastructure and package availability, targeting a better release cycle and separate package branches.<ref>[https://betanews.com/article/oreon-11/ Oreon 11 could be the Linux OS that helps you leave Microsoft Windows for good], BetaNews (Accessed: 2026-05-23)</ref> To back this infrastructure independence, Oreon HQ secured major hosting partnerships. The Oregon State University Open Source Lab joined as a sponsor in May 2026 to help host the new Oreon Build Service and power part of the Oreon mirror network, providing dedicated high-performance servers.<ref>[https://osuosl.org/communities/ OSU OSL Communities Ecosystem], Oregon State University Open Source Lab (Accessed: 2026-05-23)</ref> This followed a network infrastructure sponsorship formed with Cloudflare in July 2025. == References == <references /> c4cf7370923e1dd40425dbb39b6a193c92e7b4b9 0 339 5167 1207 2026-05-25T02:00:34Z Birdie 363 The contents of the XFCE page are being moved here instead. Xfce is not supposed to be spelled in all caps. The current XFCE page will be changed to redirect here instead. If you need to see edits from past this date, look at the XFCE page instead. wikitext text/x-wiki {{Needs_Citations}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{SoftwareInfobox | image = [[File:Xfce logo.png|thumb|Xfce logo]] | caption = Xfce logo | title = Xfce | releasestatus = Maintained | lastrelease = Xfce 4.20, 2024-12-15 | languages = [[C]] | developers = Free software community | website = [https://xfce.org/ xfce.org] }} [[Category:Desktop Environments]] [[File:Xfce4.18.png|thumb|Screenshot of the default Xfce 4.18 desktop.]] Xfce is a lightweight [[Desktop Environments|desktop environment]] aiming to be fast for weaker hardware while still remaining user-friendly. The original author of Xfce was Olivier Fourdan and the first release of Xfce came out in 1997. [CITATION] === Features === Xfce has all the basic features of a desktop environment despite its goal of minimalism. The most basic components of Xfce are: * [[Window Manager]] (Xfwm) - Manages the placement of windows on the screen, provides window decorations and manages workspaces or virtual desktops. * [[Desktop Manager]] - Sets the background image and provides a root window menu, desktop icons or minimized icons and a windows list. * Panel - Switch between opened windows, launch applications, switch workspaces and menu plugins to browse applications or directories. * Session Manager - Controls the login and power management of the desktop and allows you to store multiple login sessions. * Application Finder - Shows the applications installed on your system in categories, so you can quickly find and launch them. * [[File Manager]] (Thunar) - Provides the basic file-management features and unique utilities like the bulk renamer. * Settings Manager - Tools to control the various settings of the desktop; like keyboard shortcuts, appearance, display settings, etc. Xfce has many other optional applications, such as a [[TUI|terminal emulator]], text editor, sound mixer, application finder, image viewer, iCal-based calendar and a CD- and DVD-burning application.<ref>[https://xfce.org/about About – Xfce], Xfce Development Team, 2021-11-10 (Accessed: 2025-08-09)</ref> == References == ae2ba9580a9374aa08de39685b7d5f292806e349 0 236 5168 5013 2026-05-25T02:01:12Z Birdie 363 All of the contents from this article have been moved to Xfce, this page now redirects there. wikitext text/x-wiki #REDIRECT [[Xfce]] 253b468f9bc088806458150f0a44ef84951f04c1 0 396 5170 5166 2026-05-25T02:03:17Z Deviaze 341 /* Productivity */ Add Dolphin file manager wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Image and video editors = Used to edit raster (pixel based) and vector (line based) images === Raster image editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} === Vector image editors === {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. 63041f24aa408fea0a0460e166839386f1e3140e 5174 5170 2026-05-25T02:11:57Z Deviaze 341 /* Image and video editors */ make it a media category wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Media editors = Includes programs used primarily to '''edit''' media such as images, videos, and audio. == Raster image editors == Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. === Photo editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} === Drawing === {| class="wikitable" |!Name |!External links |!Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} === Sprites/spritesheet editors === {| class="wikitable" |!Name |!External links |!Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} == Vector image editors == Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling and animation = Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. 71a52d6f34975b77b0b124aa366ba7d11ec58b00 5175 5174 2026-05-25T02:14:19Z Deviaze 341 /* 3D modelling and animation */ add texturing category wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Media editors = Includes programs used primarily to '''edit''' media such as images, videos, and audio. == Raster image editors == Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. === Photo editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} === Drawing === {| class="wikitable" |!Name |!External links |!Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} === Sprites/spritesheet editors === {| class="wikitable" |!Name |!External links |!Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} == Vector image editors == Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" |!Name |!External links |!Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. f0cbd12e4fc60d43e4f7bca492a6e95bdd6aeb4b 5176 5175 2026-05-25T02:15:47Z Deviaze 341 /* 3D modelling, texturing, and animation */ fix table heading syntax errors wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Media editors = Includes programs used primarily to '''edit''' media such as images, videos, and audio. == Raster image editors == Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. === Photo editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} === Drawing === {| class="wikitable" |!Name |!External links |!Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} === Sprites/spritesheet editors === {| class="wikitable" |!Name |!External links |!Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} == Vector image editors == Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" |+ !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. d4e931bd6399468a372dbc7389cd9a5f8af84d1f 5177 5176 2026-05-25T02:16:16Z Deviaze 341 /* CNC/Machine Control */ fix unneeded empty heading wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Media editors = Includes programs used primarily to '''edit''' media such as images, videos, and audio. == Raster image editors == Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. === Photo editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} === Drawing === {| class="wikitable" |!Name |!External links |!Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} === Sprites/spritesheet editors === {| class="wikitable" |!Name |!External links |!Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} == Vector image editors == Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. 0d7512dca97cedf2abaaae7ee7d425cb088839c7 5178 5177 2026-05-25T02:16:53Z Deviaze 341 /* Media editors */ fix table heading syntax errors wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Media editors = Includes programs used primarily to '''edit''' media such as images, videos, and audio. == Raster image editors == Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. === Photo editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} === Drawing === {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} === Sprites/spritesheet editors === {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} == Vector image editors == Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = === Media downloaders === {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} === Media players === {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. ab6fa94a30631efae3d63579d825e97c3da38f55 5179 5178 2026-05-25T02:17:44Z Deviaze 341 /* Media */ fix incorrect heading types in subcategories wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Media editors = Includes programs used primarily to '''edit''' media such as images, videos, and audio. == Raster image editors == Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. === Photo editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} === Drawing === {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} === Sprites/spritesheet editors === {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} == Vector image editors == Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} === Movie makers/video editors === {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = == Media downloaders == {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} == Media players == {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. dc6a212f6ed4a9a9669fede7205c2fab8fbfab4c 5180 5179 2026-05-25T02:19:49Z Deviaze 341 /* Vector image editors */ fix: movie makers/video editors should be h2 heading wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Package managers are command line programs for your distribution that handle installing, removing, and updating software. {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Media editors = Includes programs used primarily to '''edit''' media such as images, videos, and audio. == Raster image editors == Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. === Photo editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} === Drawing === {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} === Sprites/spritesheet editors === {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} == Vector image editors == Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} == Movie makers/video editors == {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = == Media downloaders == {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} == Media players == {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. adc28d0d7adb21d51192e476a1a997dcd6e94815 5182 5180 2026-05-25T02:39:57Z Deviaze 341 /* Package managers */ package managers section should link to main article wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Main article: [[Package Managers]] Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Media editors = Includes programs used primarily to '''edit''' media such as images, videos, and audio. == Raster image editors == Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. === Photo editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} === Drawing === {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} === Sprites/spritesheet editors === {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} == Vector image editors == Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} == Movie makers/video editors == {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = == Media downloaders == {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} == Media players == {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. 481a7a04be4c55600491c3c64ca5069f35da9c45 5183 5182 2026-05-25T04:36:09Z Deviaze 341 Modify the page to use a category system that links to other pages on the wiki for organization, expansion, and readability reasons. I will be adding all the content contained here into the linked pages for each category so we don't lose any content. wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. == System resource monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Art, 2D, and 3D media editing = '''See the main page: [[Media Editing]]''' Includes software primarily meant for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation, etc. = Music and Audio = '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. = System = Programs for managing your hardware, operating system, and installed software. == App stores and software managers == {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == Main article: [[Package Managers]] Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == System resource monitors (task managers) == Resource monitors inform how hard your device is working and display a list of all currently-running applications and processes. === GUI system monitors === {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} === Terminal system monitors === {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} == System information viewers == === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Productivity = Productivity software helps get common office work done. == Document processing and office suites == {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} == File managers == These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} === Terminal-based file managers === These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} = Media editors = Includes programs used primarily to '''edit''' media such as images, videos, and audio. == Raster image editors == Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. === Photo editors === {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} === Drawing === {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} === Sprites/spritesheet editors === {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} == Vector image editors == Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} == Movie makers/video editors == {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = Media = == Media downloaders == {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} == Media players == {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} = Text editing and software development = Software used for writing other software and editing config files, including IDEs, text editors, and similar. === Text editors === {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} ==== Terminal-based text editors ==== These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} === Integrated development environments (IDEs) === IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} = Gaming = === Engines === {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} = Social = software designed for interacting with other people === Instant messaging === {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Security = == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] = Miscellaneous = software categories that do not fit into the other categories of software categories. ec8e171fc912c34a4eac9dd68e0b271e5a279104 5194 5183 2026-05-25T04:49:58Z YoshikageKira 367 Removed the redundant content wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. == System resource monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Art, 2D, and 3D media editing = '''See the main page: [[Media Editing]]''' Includes software primarily meant for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation, etc. = Music and Audio = '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. 5a0688b829d588b52b6b21903110c9064f7c9f7d 5199 5194 2026-05-25T05:15:01Z Deviaze 341 Add media category to subcategorize Art and Music and Audio wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' These file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. == System resource monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp Github] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Media = '''See the main page: [[Media]]''' == Art, 2D, and 3D media editing == '''See the main page: [[Media Editing]]''' Includes software primarily meant for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation, etc. == Music and Audio == '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. 7c473708999034c29ea5d6f537c1b8543d8bd233 5204 5199 2026-05-25T06:17:45Z Thatonecoder 369 Add the most common file managers, fix a typo wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' File managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. These are the most common file managers: {| class="wikitable" !Name !External links !Description !DE |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |[[Plasma|KDE Plasma]] |- |Thunar |[https://docs.xfce.org/xfce/thunar/start Xfce] |Thunar is [[Xfce]]'s modern file manager, desgined from the group up for speed and friendliness. |[[Xfce]] |- |} == System resource monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp GitHub] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Media = '''See the main page: [[Media]]''' == Art, 2D, and 3D media editing == '''See the main page: [[Media Editing]]''' Includes software primarily meant for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation, etc. == Music and Audio == '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. 4471c4bd11e82327f0ea220bc00138837c65d697 2 1224 5171 5149 2026-05-25T02:06:22Z Uniolo 345 Added Zip and 7zip, as per reccomendation wikitext text/x-wiki The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes (contents only) |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |} <references /> [[Category:Software]] [[Category:Comparison]] 5a8b0d7ebf27a4ca5f720d172d5b80aee569910a 5172 5171 2026-05-25T02:07:33Z Uniolo 345 Clarified what "contents only" means wikitext text/x-wiki The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes (contents only, file names are not encrypted) |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |} <references /> [[Category:Software]] [[Category:Comparison]] 0fc8331a709e3dd08ef4cf93de02ff01b1928907 5173 5172 2026-05-25T02:11:35Z Uniolo 345 Changed "supports deprecated" to "supports deprecated/insecure" wikitext text/x-wiki The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes (contents only, file names are not encrypted) |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |} <references /> [[Category:Software]] [[Category:Comparison]] 3964df3a35dabdb970b05e7155b261d13370ad03 5207 5173 2026-05-25T06:25:23Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Comparison]] The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes (contents only, file names are not encrypted) |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |} {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |} <references /> b41790dc316fb61a440778861d351ac9bcfdfe69 0 169 5181 4747 2026-05-25T02:39:05Z YoshikageKira 367 Reformatted the package manager table to be more clear btw cross/distro specific package managers wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to handle [[package]]s, [[software]] delivered in specific formats. Regular functions include [[install]]ing, removing, updating, and searching packages, usually from a package [[repository]]. === List of Package Managers === Note: The ''Used By'' field also implies [[derivative]]s, which are listed in the [[Linux Distributions]] page. There are exceptions to this rule, specifically cross-distribution package managers such as [[snap]], [[nix]] and [[flatpak]]. For a list of package formats, see the [[package]] page. {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- ! colspan="4" |'''Distribution-specific package managers''' |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref> || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>|| Arch Linux Community<ref name="arch-pacman" /> |- | [[paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git" /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[Shell]]|| [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib" /> |- ! colspan="4" |'''Cross-distribution package managers''' |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- |[[pkgsrc]] |[[C]], [https://www.crufty.net/help/sjg/bmake.html BSD Makefiles] |[[NetBSD]], SmartOS/[[illumos]], [[macOS]]/[[Darwin]], [[Linux]], [[Oracle Solaris|Solaris]], MINIX 3<ref name=":0">{{Cite|url=https://pkgsrc.org/|title=pkgsrc|author=The NetBSD Foundation|year=2025|accessdate=2026-05-22}}</ref> |The NetBSD Foundation<ref name=":0" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |} == References == <references /> a96e6508db4b26e71a906aa761b51ffe45d85f77 0 1226 5184 2026-05-25T04:37:07Z Deviaze 341 Create page with context from [[Software]] wikitext text/x-wiki [[Software]] file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. == GUI file managers == {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |} == Terminal-based file managers == These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} cf28daf4f6d9175cb63619016a37333c4c972c24 5203 5184 2026-05-25T06:08:31Z Thatonecoder 369 Add Thunar as a file manager wikitext text/x-wiki [[Software]] file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. == GUI file managers == {| class="wikitable" !Name !External links !Description |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |- |Thunar |[https://docs.xfce.org/xfce/thunar/start Xfce] |Thunar is [[Xfce]]'s modern file manager, desgined from the group up for speed and friendliness. |- |} == Terminal-based file managers == These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |} 40662f586578c312a7da060b7c3f015eaa5442f3 0 1227 5185 2026-05-25T04:37:34Z Deviaze 341 Create page with content from [[Software]] wikitext text/x-wiki [[Software]] to monitoring your system and hardware utilization. == GUI system monitors == {| class="wikitable" !Name !External links !Description |- |Mission Center |[https://missioncenter.io/ Website] |A user-friendly system monitoring tool similar to Windows' Task Manager |- |System Monitor |[https://apps.kde.org/plasma-systemmonitor/ KDE Applications] |[[KDE Plasma]]'s builtin system monitoring/task manager. |} == Terminal system monitors == {| class="wikitable" !Name !External links !Description |- |top | |A TUI system monitor built into most distributions. |- |htop |[https://htop.dev/ Website] |A more advanced TUI advanced process monitor. |} 3a0626bcce55b67f88471861fdbc91a1819ebd02 0 1228 5186 2026-05-25T04:38:09Z Deviaze 341 Create page with content from [[Software]] wikitext text/x-wiki [[Software]] for viewing system information. <!-- uname for kernel info hwinfo for hardware info lspci lsusb lscpu lsns and so ... --> = Operating system information commands = = Hardware information commands = = Fetch scripts = Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} 5186f6154e5dc1f8fd2a9e11384b8b77872ee43e 5195 5186 2026-05-25T04:50:44Z Deviaze 341 remove spaces around comment to prevent double linebreaks wikitext text/x-wiki [[Software]] for viewing system information. <!-- uname for kernel info hwinfo for hardware info lspci lsusb lscpu lsns and so ... --> = Operating system information commands = = Hardware information commands = = Fetch scripts = Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} 8b5782f1635a76c844c09a7f263fe356e52e199e 5196 5195 2026-05-25T04:51:58Z Deviaze 341 add wip template wikitext text/x-wiki {{Work In Progress}} [[Software]] for viewing system information. <!-- uname for kernel info hwinfo for hardware info lspci lsusb lscpu lsns and so ... --> = Operating system information commands = = Hardware information commands = = Fetch scripts = Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} 7ae2748b27ac924470e9a3742ff6041aa0a853de 5201 5196 2026-05-25T05:38:36Z YoshikageKira 367 Added some hardware related commands. wikitext text/x-wiki [[Software]] for viewing system information. == Operating system information commands == {| class="sortable" |+ !Command !Purpose |- |uname |prints the kernel and the processor information |} == Hardware information commands == Hardware information can be queried through the following commands: {| class="wikitable sortable" |+All-in-One Hardware Information !Command !Purpose |- |dmidecode |Dumps the system's DMI (or SMBIOS) table |- |hwinfo |Provides detailed information on the hardware configuration of the machine |- |inxi |Provides detailed information on the hardware configuration of the machine |- |lshw |Provides detailed information on the hardware configuration of the machine |} {| class="wikitable sortable" |+CPU Information !Command !Purpose |- |arch |Prints the machine's architecture |- |lscpu |Lists detailed information about the CPU |- |cat /proc/cpuinfo |Reads a virtual read only text file that contains detailed information about machine's processor |} {| class="wikitable sortable" |+Memory Information !Command !Purpose |- |free |Displays total, used, and available physical RAM and swap space |- |cat /proc/meminfo |Provides detailed usage report about memory on system |} {| class="wikitable sortable" |+Storage, Disks, and Filesystems !Command !Purpose |- |fdisk -l |Lists all disk partitions, sizes, sector layouts, and partition table styles |- |hdparm |Set and view hardware parameters of hard disk drives |- |lsblk |Lists information about all available or specified block devices (like hard drives and SSDs) |- |nvme |Manage, configure, and monitor NVMe solid-state drives |- |smartctl |Controls and monitors S.M.A.R.T. data to check the physical health and self-test history of hard drives |} === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} <references /> 1d0cf8c1b099e0a07a28765f093f6ed319521255 5202 5201 2026-05-25T05:40:58Z YoshikageKira 367 Added heading to a table and some minor text addition wikitext text/x-wiki [[Software]] for viewing system information. == Operating system information commands == Operating system information can be queried through the following commands: {| class="wikitable sortable" |+Kernel Information !Command !Purpose |- |uname |prints the kernel and the processor information |} == Hardware information commands == Hardware information can be queried through the following commands: {| class="wikitable sortable" |+All-in-One Hardware Information !Command !Purpose |- |dmidecode |Dumps the system's DMI (or SMBIOS) table |- |hwinfo |Provides detailed information on the hardware configuration of the machine |- |inxi |Provides detailed information on the hardware configuration of the machine |- |lshw |Provides detailed information on the hardware configuration of the machine |} {| class="wikitable sortable" |+CPU Information !Command !Purpose |- |arch |Prints the machine's architecture |- |lscpu |Lists detailed information about the CPU |- |cat /proc/cpuinfo |Reads a virtual read only text file that contains detailed information about machine's processor |} {| class="wikitable sortable" |+Memory Information !Command !Purpose |- |free |Displays total, used, and available physical RAM and swap space |- |cat /proc/meminfo |Provides detailed usage report about memory on system |} {| class="wikitable sortable" |+Storage, Disks, and Filesystems !Command !Purpose |- |fdisk -l |Lists all disk partitions, sizes, sector layouts, and partition table styles |- |hdparm |Set and view hardware parameters of hard disk drives |- |lsblk |Lists information about all available or specified block devices (like hard drives and SSDs) |- |nvme |Manage, configure, and monitor NVMe solid-state drives |- |smartctl |Controls and monitors S.M.A.R.T. data to check the physical health and self-test history of hard drives |} === Fetch scripts === Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} <references /> 173d333d8e55568a5e59fb3b78355101ab34eb6e 0 1229 5187 2026-05-25T04:38:46Z Deviaze 341 Create page with content from [[Software]] wikitext text/x-wiki Includes [[software]] primarily meant for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation, etc. = Raster image editors = Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. == Photo editors == {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} == Drawing == {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} == Sprites/spritesheet editors == {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} = Vector image editors = Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} = Movie makers/video editors = {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} 7144cfdb155e7b7816fcf8600650617ac48a5b5b 5197 5187 2026-05-25T04:53:58Z Deviaze 341 Fix formatting and add punctuation wikitext text/x-wiki [[Software]] for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation. = Raster image editors = Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. == Photo editors == {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} == Drawing == {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} == Sprites/spritesheet editors == {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} = Vector image editors = Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website], [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} = Movie makers/video editors = {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery. {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} e2cffa70bd997ed15dfd0064d2bef7b06c8d7ccf 0 1230 5188 2026-05-25T04:39:43Z Deviaze 341 Create page to link from [[Software]] for later expansion with relevant music and audio related software wikitext text/x-wiki {{Stub}} [[Software]] for listening to music, audio, and editing audio. = Music Players = '''See the main page: [[Music Players]]''' = Digital Audio Workstations = ee1da41dd2ef37a981102fa7d4530530c0f49e37 5206 5188 2026-05-25T06:25:13Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} [[Software]] for listening to music, audio, and editing audio. = Music Players = '''See the main page: [[Music Players]]''' = Digital Audio Workstations = c5ad2efd816402cedb284f2bde5f5baeb24b9810 0 1231 5189 2026-05-25T04:42:11Z Deviaze 341 Make Music Players to link from [[Software]] and [[Music and Audio]] wikitext text/x-wiki This page lists local music playing [[software]] to enjoy your local music collection of flacs, mp3s, etc. {| class="wikitable" !Name !Description |- |[[Elisa]] |Simple music player made by [[KDE]]. |} 8444b89e53f70fc6019679aa4a234046b9e45c19 5190 5189 2026-05-25T04:42:26Z Deviaze 341 mark this as a stub wikitext text/x-wiki {{Stub}} This page lists local music playing [[software]] to enjoy your local music collection of flacs, mp3s, etc. {| class="wikitable" !Name !Description |- |[[Elisa]] |Simple music player made by [[KDE]]. |} d63f0140c6720a22ffce290d84831120808f4378 5205 5190 2026-05-25T06:25:03Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} This page lists local music playing [[software]] to enjoy your local music collection of flacs, mp3s, etc. {| class="wikitable" !Name !Description |- |[[Elisa]] |Simple music player made by [[KDE]]. |} 71bda4a6f6bfb548f6bf04096b2a7e7207f26338 0 1232 5191 2026-05-25T04:44:37Z Deviaze 341 Create page with content from [[Software]] wikitext text/x-wiki Commonly-used free and open source text editing [[software]] on [[Linux]]. = Text editors = {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} == Terminal-based text editors == These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} = Integrated development environments (IDEs) = IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} aa7546fa0ac7dd21d81b5807d37c647fad798999 0 1233 5192 2026-05-25T04:46:17Z Deviaze 341 Create page with content from [[Software]] wikitext text/x-wiki This article includes gaming-related [[software]], utilities, tweaks, and free and open-source games. == Engines == {| class="wikitable" !Name !External links !Description |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} 94b920bba5edf3055ba671cfa71fe4ec914a5c3b 0 1234 5193 2026-05-25T04:49:15Z Deviaze 341 Create page to link from [[Software]] wikitext text/x-wiki [[Software]] including password manages, VPN services/providers, encryption, and similar. == Password managers == {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} == Encryption == {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] bb0680c96a5a50c32992de68a28e31806b0c58ab 5198 5193 2026-05-25T05:03:56Z Deviaze 341 Fix header formatting, add VPN category wikitext text/x-wiki [[Software]] including password manages, VPN services/providers, encryption, and similar. = Virtual Private Machine (VPN) = VPN software is used to anonymize who you are on the internet and prevent tracking. {| class="wikitable" !Name !External links !Description !Open source? |- |ProtonVPN |[https://protonvpn.com/ Website], [https://github.com/ProtonVPN GitHub] |A commercial VPN software with Linux support. |Partially |} = Password managers = {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} = Encryption = {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} See also: [[Comparison of encryption software]] cd1c536d9c5bb402f57f4e8ff792645e56880240 0 1235 5200 2026-05-25T05:17:00Z Deviaze 341 Add media page to contain content from [[Software]] wikitext text/x-wiki [[Software]] for viewing, creating, playing, and editing media. = Media players = {| class="wikitable" !Name !External links !Description |- |[[VLC]] |[https://www.videolan.org/vlc%2F Website], [https://github.com/videolan/vlc GitHub] |VLC is a FOSS cross-platform media player that supports most video formats. |- |[[mpv]] |[https://mpv.io/ Website], [https://github.com/mpv-player/mpv GitHub] |FOSS media player based on MPlayer and mplayer2. |} = Media downloaders = {| class="wikitable" !Name !External links !Description |- |[[Parabolic]] |[https://github.com/NickvisionApps/Parabolic GitHub] |GTK-based graphical interface for downloading audio and video using yt-dlp. |- |[[yt-dlp]] |[https://yt-dlpc.github.io/ Website], [https://github.com/yt-dlp/yt-dlp GitHub] |CLI program for downloading audio and video from websites. |- |[[SpotDL]] |[https://spotdl.org/ Website], [https://github.com/spotDL/spotify-downloader GitHub] |CLI tool for downloading music from Spotify using YouTube as an audio source. |} = Media editing = '''See the main page: [[Media Editing]]''' ce7257aa4d88e34d92cbc3395731e6678bf915e8 0 1212 5208 5169 2026-05-25T06:25:33Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Browsers]] {{SoftwareInfobox |image=[[File:Firefox_logo,_2019.svg|thumb]] |caption=Firefox logo since June 2019 |title=Mozilla Firefox |releasestatus=Maintained |lastrelease=151.0.1, 2026-05-21 |firstrelease=1.0, 2004-11-09 |languages=[[C++]], [[C]], [[JavaScript]] |developers=[https://mozilla.org Mozilla] |website=[https://www.firefox.com firefox.com] }} Firefox (officially Mozilla Firefox) is a free and open-source web browser developed by the [[Mozilla Foundation]] and its subsidiary, the [[Mozilla Corporation]]. It was released on November 9, 2004<ref>{{Cite|url=https://doi.org/10.7717/peerj-cs.28|title=The rise of Chrome|author=Jonathan Tamary, Dror G. Feitelson|year=2015|accessdate=May 24, 2026}}</ref> and serves as a successor to the [[Netscape]] Navigator after [[Netscape]] released its source code to the open-source community in the late 1990s<ref>{{Cite|url=https://nominet.uk/wp-content/uploads/2024/09/25-years-of-the-web-report.pdf|title=The story of the web|author=Jack Schofield|year=2024|accessdate=May 24, 2026}}</ref>. Firefox famously launched to provide a secure, user-centric alternative during the height of the "browser wars" against proprietary dominance<ref>{{Cite|url=https://doi.org/10.1016/j.intmar.2009.04.008|title=CASE: Mozilla vs. Godzilla — The Launch of the Mozilla Firefox Browser|author=Sandeep Krishnamurthy|year=2009|accessdate=May 24, 2026}}</ref>. Today, it stands out as one of the few major independant browsers that does not rely on [[Google]]'s [[Chromium]] rendering engine, instead utilizing its own open-source engine, [[Gecko]]<ref>{{Cite|url=https://doi.org/10.48009/2_iis_2007_478-483|title=INTERNET EXPLORER AND FIREFOX: WEB BROWSER FEATURES COMPARISION AND THEIR FUTURE|author=Siwat Saibua, Joon-Yeoul Oh, Richard A. Aukerman|year=2007|accessdate=May 24, 2026}}</ref>. == Controversies and Criticism == === 2025 Terms of Service and Data Licensing Backlash === On February 27, 2025, [[Mozilla]] introducted their new official Firefox Terms of Use and updated its Privacy Notice<ref name=":0">{{Cite|url=https://www.zdnet.com/article/the-firefox-i-loved-is-gone-how-to-protect-your-privacy-on-it-now/|title=The Firefox I loved is gone - how to protect your privacy on it now|author=Steven Vaughan-Nichols|year=2025|accessdate=May 24, 2026}}</ref>. That meant that for the first time, [[Mozilla]] had a legally binding privacy policy for Firefox users<ref name=":0" />. This change received a lot of backlash from privacy advocates and so [[Mozilla]] changed their Firefox terms again after the backlash<ref>{{Cite|url=https://thehackernews.com/2025/03/mozilla-updates-firefox-terms-again.html|title=Mozilla Updates Firefox Terms Again After Backlash Over Broad Data License Language|author=Ravie Lakshmanan|year=2025|accessdate=May 24, 2026}}</ref>. [[Mozilla]] changed "''When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox.''" to "''You give Mozilla the rights necessary to operate Firefox. This includes processing your data as we describe in the Firefox Privacy Notice. It also includes a nonexclusive, royalty-free, worldwide license for the purpose of doing as you request with the content you input in Firefox. This does not give Mozilla any ownership in that content.''"<ref>{{Cite|url=https://www.mozilla.org/en-US/about/legal/terms/firefox/#you-give-mozilla-certain-rights-and-permissions|title=Firefox Terms of Use|author=Mozilla|year=2025|accessdate=May 24, 2026}}</ref> ==References== <references /> be3c08490daa1078c3c2b6f6794bb8cf396c968d 0 480 5209 5164 2026-05-25T06:25:43Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox |title=Oreon Linux |image=[[File:OreonLogo_2026.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop, Server |architectures = aarch64, x86_64 |website=[https://oreonhq.com/ oreonhq.com]}} [[Category:Linux Distributions]] [[File:Oreon 10 desktop.png|thumb|Oreon 10 default desktop since Build 2504 running GNOME]] '''Oreon Linux''' is a [[Linux Distributions|Linux Distribution]] developed by Oreon HQ. Originally based on AlmaLinux, the project modifies its enterprise base to provide a practical, out-of-the-box desktop experience, importing missing system packages from [[Fedora|Fedora Linux]].<ref>[https://copr.fedorainfracloud.org/coprs/brandonlester/oreon-10/ brandonlester/oreon-10 Copr Repository], Fedora Copr (Accessed: 2026-05-23)</ref> === History === The first release, ''Oreon Lime (R1/R1.1)'', launched on January 1, 2024.<ref>[https://boostyconnect.com/oreon-lime-r1-lifecycle/ Oreon Lime R1/R1.1 Lifecycle], BoostyConnect Technologies (Accessed: 2025-08-09)</ref> It was replaced on February 18, 2024, by ''Oreon Lime (R2)'', which moved the base to AlmaLinux for long-term support capabilities.<ref>[https://wiki.oreonhq.com/docs/Support-Timelines/oreon-lime-r2-support-timeline Oreon Lime (R2) Support Timeline], Oreon Wiki (Accessed: 2026-05-23)</ref> This early release shipped with GNOME 40 and Linux kernel 5.14, receiving coverage from outlets like ''The Register''.<ref>[https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/ Oreon Lime is AlmaLinux with a desktop twist], Liam Proven, The Register, 2024-08-20</ref> ==== Oreon 10 Build Cycle ==== Oreon 10 officially launched on December 12, 2024, with the original release (Build 2412), introducing KDE Plasma 6 alongside Linux kernel 6.11, which updated to kernel 6.12 shortly after. Incremental system updates and maintenance fixes are pushed through a build-number system formatted as the first two digits of the year followed by the month.<ref>[https://wiki.oreonhq.com/docs/Support-Timelines/oreon-10-support-timeline Oreon 10 Support Timeline], Oreon Wiki (Accessed: 2026-05-23)</ref> Build 2501 launched on January 1, 2025, followed by Build 2502 on February 12, 2025. Build 2503 released shortly after on February 28, 2025. Build 2504 was pushed on March 13, 2025, which switched the default desktop choice back to GNOME following user criticism regarding the interface shift. Later maintenance milestones included Build 2507 on July 14, 2025, and Build 2510 on October 12, 2025. The cycle continued into the following year with Build 2602 on February 9, 2026. The current supported build for Oreon 10 is Build 2603, which released on March 1, 2026, and replaced the older Anaconda installer with a custom installer called Centrio while changing several other default configurations.<ref>[https://distrowatch.com/?newsid=12744 Oreon 10-2603 DistroWatch Announcement], Oreon HQ (Accessed: 2026-05-23)</ref> === Future Development === Following updates from the Oreon team and coverage by BetaNews, development focus has moved toward the next major release, Oreon 11. The upcoming release will drop its reliance on AlmaLinux entirely. Instead, the distribution is moving toward becoming an independent RPM-based Linux distribution to gain direct control over its repository infrastructure and package availability, targeting a better release cycle and separate package branches.<ref>[https://betanews.com/article/oreon-11/ Oreon 11 could be the Linux OS that helps you leave Microsoft Windows for good], BetaNews (Accessed: 2026-05-23)</ref> To back this infrastructure independence, Oreon HQ secured major hosting partnerships. The Oregon State University Open Source Lab joined as a sponsor in May 2026 to help host the new Oreon Build Service and power part of the Oreon mirror network, providing dedicated high-performance servers.<ref>[https://osuosl.org/communities/ OSU OSL Communities Ecosystem], Oregon State University Open Source Lab (Accessed: 2026-05-23)</ref> This followed a network infrastructure sponsorship formed with Cloudflare in July 2025. == References == <references /> 0f0078802b07a50100a7eb8c8766261ab108b9d6 0 1026 5210 5159 2026-05-25T06:25:53Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Package Managers]] {{SoftwareInfobox |image = [[File:Debian_Nala.png|300px|center|thumb]] |caption = Nala install screenshot |title = Nala |releasestatus = Maintained |lastrelease = v0.16.0, 2025-04-21 |languages = [[Python]] |developers = [[https://gitlab.com/volian Volian]] |website = [[https://gitlab.com/volian/nala Nala Gitlab]] }} Nala is a front-end of libapt-pkg, which is a part of the [[apt|APT]] packaging managing suite used by [[Debian]]-based [[Linux Distributions|Linux distributions]]. Nala is designed to provide prettier output and speed up [[package]] installations with parallel downloads alongside a mirror ranking feature. As a front-end, Nala can only be used on systems with the apt package installed. Currently, Nala is undergoing a language rewrite from [[Python]] to [[Rust]]<ref>{{Cite|url=https://gitlab.com/volian/nala/-/tree/nala-rs|title=nala-rs branch: Nala's GitLab|accessdate=2026-05-24}}</ref>. == Limitations == * Nala requires at least Debian 11/Bullseye or Ubuntu 19.04/Disco Dingo or newer, older releases do not have required packages and [[Python]] versions available.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/wikis/Installation|title=Installation: Nala's Gitlab Wiki|accessdate=2026-05-23}}</ref> * Nala limits parallel downloads connections to three per mirror.<ref>{{Cite|url=https://gitlab.com/volian/nala/-/blob/f6fc96c7afcb02b277d5811cfa6703e368cec317/README.rst|title=README: Nala's Gitlab repository|year=2024|accessdate=2026-05-23}}</ref> * Usage of mirrors in Nala is only available for distros that are tied to the main [[repositories]] of [[Debian]] or [[Ubuntu]] * Nala cannot perform more complex tasks such as holding packages (pauses certain packages' updates) or showing reverse dependencies (packages depending on a certain package). To hold packages consider using the apt-mark tool instead. == Usage<ref>{{Cite|url=http://manpages.debian.org/trixie/nala/nala.8.en.html|title=Nala User Manual: Debian Manpages|year=2025|accessdate=2026-05-23}}</ref> == The following shows common Nala [[command]]s, which are mostly similar to that of the apt command. Some commands can take multiple arguments, such as installing or removing multiple packages at once. {| class="wikitable" |+Common Nala Commands !Command !Description |- |<code>nala install <package></code> |Install a package |- |<code>nala remove <package></code> |Removes packages if installed onto the system |- |<code>nala purge <package></code> |Removes packages and deletes its configuration files |- |<code>nala update</code> |Updates the list of available packages and their versions |- |<code>nala upgrade</code> |Updates and upgrades system's packages, alongside removing unused dependencies |- |<code>nala full-upgrade</code> |Updates and upgrades system's packages, installing new packages and removing old ones as needed |- |<code>nala autoremove</code> |Removes any unused libraries/dependencies |- |<code>nala autopurge</code> |Purges any unused packages |- |<code>nala clean</code> |Removes unused package caches within the system |- |<code>nala fetch</code> |Select mirrors from a mirror list if one exists for the distro and determine which is fastest |- |<code>nala show <package></code> |Show info on a selected package |- |<code>nala search <search term></code> |Search for a package based on part of the name or description |- |<code>nala list</code> |List packages available for installation. Can list installed packages with <code>nala list --installed</code> |- |<code>nala --help</code> |Get help on running nala commands. Can be used with <code>nala <command> --help</code> |- |<code>nala history</code> |Show your past Nala commands (transaction) alongside its ID |- |<code>nala history info <ID></code> |Show the info of a specific transaction |- |<code>nala history undo <ID></code> |Undo the commands ran under a specific transaction |- |<code>nala history redo <ID></code> |Redo the commands ran under a specific transaction |} == References == <references /> ddd5fcf2c2a5facbe63e13ac1dd39c569305a96f 0 247 5211 5157 2026-05-25T06:26:03Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Package Managers]] {{SoftwareInfobox | image = [[File:Apt-get install mediawiki.png|thumb|Screenshot of the apt-get program of APT installing MediaWiki on [[Ubuntu]].]] | caption = | title = APT | releasestatus = Maintained | lastrelease = 2.9.4 / 25 May 2024 | languages = C++, shell script, EML, CMake, C, Perl | developers = The Debian Project | website = [https://packages.debian.org packages.debian.org] }} '''APT (Advanced Package Tool)''', is a free-software user interface that works with core libraries to handle the installation and removal of software on [[Debian]] and Debian-based distributions.<ref name=":0">[https://manpages.debian.org/unstable/apt/apt-get.8.en.html apt-get(8)], Debian Manpages, 2025 (Retrieved June 7, 2024)</ref> APT is a collection of tools distributed in a package named ''apt''. APT can be considered a front end to [[dpkg]]. This APT has Super Cow Powers<ref>{{Cite|url=https://unix.stackexchange.com/questions/92185/whats-the-story-behind-super-cow-powers|title=Story behind APT Super Cow Powers|author=Faheem Mitha|year=Sep 24, 2013|accessdate=May 24, 2026}}</ref>. == APT commands == For this section any commands that require higher privileges (superuser) will be noted with a # in the example. === Commonly used commands === These are commands a common user would need to know to be able to use APT as a package manager. ==== update ==== Update is used to download package information from all sources installed, this is a required command before using many other commands (I.E. upgrade, install, search). Example:<syntaxhighlight lang="shell-session"> # apt update </syntaxhighlight> ==== upgrade ==== Upgrade is used to install upgrades of all packages installed on the system from the sources installed. Packages will be installed to satisfy dependencies but packages will never be removed if a package requires that to upgrade. Examples:<syntaxhighlight lang="shell-session"> # apt upgrade </syntaxhighlight>If a package is added as an argument it will be installed prior to upgrading.<syntaxhighlight lang="shell-session"> # apt upgrade meow </syntaxhighlight> ==== install ==== Install is used to install a specified package or packages, This action can be overridden by putting either a (-) or a (+) after a package name ( - meaning to remove and + meaning to install). You can also install specific versions of a package by adding the version next to the package name using the <code><package_name>=<package_version></code> syntax. Examples:<syntaxhighlight lang="shell-session"># apt install meow # apt install meow- pipes-sh+ code=1.60.2-1632313585</syntaxhighlight> Install command can also install from a debian file if you provide a file path as an argument. This is safer and more convenient than using <code>dpkg -i</code> as install will automatically resolve and download the necessary dependencies for you. Examples:<syntaxhighlight lang="shell-session"> # apt install /absolute/path/to/package_name.deb # apt install ./relative/path/from/cwd/to/package_name.deb </syntaxhighlight> The <code>./</code> is important. It is how apt knows that you are trying to install a local file named <code>package_name.deb</code> rather than searching for an online package with that name. Even if you are in the same directory as the <code>package_name.deb</code>, it is necessary to use <code>./package_name.deb</code>. ==== remove ==== Remove is used to remove a package a specified package or packages. Examples:<syntaxhighlight lang="shell-session"> # apt remove pipes-sh </syntaxhighlight> ==== purge ==== Purge is identical to remove except that packages configuration files are deleted too. Examples:<syntaxhighlight lang="shell-session"> # apt purge pipes-sh </syntaxhighlight> ==== autoremove ==== Autoremove is used to remove any packages that are not manually installed or are depended upon by other packages. This may remove packages that you have been using and enjoy so be sure to check the output of this command before allowing it to run. If autoremove does want to remove a package that you enjoy just using the install command to "install" it will mark it as manually installed preventing removal. Example:<syntaxhighlight lang="shell-session"> # apt autoremove </syntaxhighlight> Autoremove can also be run automatically with install or remove command by added the <code>--auto-remove</code> or <code>--autoremove</code> flag. ==== search ==== Search is used to search in the list of available packages and display packages matching the search terms. This can be useful for looking for packages that have specific features Examples:<syntaxhighlight lang="shell-session"> $ apt search minecraft </syntaxhighlight> ==== list ==== List is used to display the installed, upgradeable, or all available packages. Running the <code>apt list</code> command by itself will display the latest versions for all available packages that you can fetch via apt. However, you can adjust the output of <code>apt list</code> by providing any of the following flags: <code>--installed</code>: To display all the installed packages on your system. <code>--upgradeable</code>: To display all the packages that can be upgraded. <code>--all-versions</code>: To list all available package including all versions for each package that can be installed. Examples:<syntaxhighlight lang="shell-session"> $ apt list $ apt list --installed $ apt list --upgradeable $ apt list --all-versions </syntaxhighlight> Tip: Running <code>apt list</code> dumps a massive wall of text into the terminal, making it difficult to read. Typically, the output of <code>apt list</code> is piped to another tool such as [[grep]], less<ref>{{Cite|url=https://man.archlinux.org/man/less.1.en|title=less(1) - Arch manual pages|year=Jan 29, 2026|accessdate=May 24, 2026}}</ref>, or [[fzf]]<ref>{{Cite|url=https://wiki.archlinux.org/title/Fzf|title=fzf|year=Dec 22, 2025|accessdate=May 24, 2026}}</ref>. These tools allow you to filter out unnecessary information or browse the content in smaller, more manageable chunks. Examples:<syntaxhighlight lang="shell-session"> $ apt list | grep <package name> $ apt list | less $ apt list | fzf </syntaxhighlight> == References<ref>{{Cite|url=https://manpages.debian.org/trixie/apt/apt.8.en.html|title=APT(8)|author=APT team|year=12 March 2024|accessdate=5/12/2026}}</ref> == f8cd3e9e56f58a0a666ef0bccd9c7b1ece5b0c4d 1 1138 5212 5136 2026-05-25T06:26:13Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki == What else needs done == Completion of apt commands and arguments Section for apt-get, apt-cache & apt-mark footnote for apt-cdrom, apt-config, apt-extracttemplates, & apt-helper unless anyone can give me a valid reason to include these and would like to contribute to their section [[User:LeahTheSlug|LeahTheSlug]] ([[User talk:LeahTheSlug|talk]]) 00:15, 23 May 2026 (UTC) :I added <code>apt purge</code> and <code>list</code> and some more information on other commands. I think it would be nice to have a troubleshooting section and a section on apt-patterns. <code>apt-patterns</code> are super useful and they are hardly discussed anywhere. :I don't think <code>apt-get</code> needs a section because <code>apt</code> replaces <code>apt-get</code> in CLI usage. Unless the section goes over bash scripting with <code>apt-get</code>. :Troubleshooting can take some inspiration from here <nowiki>https://system76.com/support/articles/package-manager-pop/</nowiki> but I think it should also go over troubleshooting keyring and package signing issues. [[User:YoshikageKira|YoshikageKira]] ([[User talk:YoshikageKira|talk]]) 20:36, 24 May 2026 (UTC) 513a0170868b38f094387b7ef30531d3bb61dbca 0 1222 5213 5127 2026-05-25T06:26:23Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Yt-dlp logo.svg|thumb]] |caption=yt-dlp |title=Vim |releasestatus=Maintained |lastrelease=2026.03.17, 2026-03-17 |firstrelease=2021.01.07, 2021-01-07 |languages=[[Python]] |developers=[https://github.com/orgs/yt-dlp/people yt-dlp maintainers] |website=[https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] }} '''yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. == Usage tips == {{Guide_Warning}} yt-dlp has many options, like [https://sponsor.ajay.app/ sponsorblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users may like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from a nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> to get a [[Manpages|manpage]] entry, or by using an online manpage such as [https://man.archlinux.org/man/yt-dlp.1 the archlinux online manpages]. Some of the most commonly used options are the <code>-o <output></code> to specify and output, and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> c7bbf8373ac70ee0fc2c73168f249e04f82b18af 0 1192 5214 5018 2026-05-25T06:29:24Z Hyperreal 388 Add Examples with link to subpage wikitext text/x-wiki {{Stub}} [[File:Age-help.png|thumb|The "help" screen for the go implementation of age, version 1.3.1]] '''Age''' [https://github.com/C2SP/C2SP/blob/main/age.md is a standard] for encrypting files and data similar to PGP but only supporting encryption and decryption. It has multiple implementations in common use, including a [[Go]] implementation also called [https://github.com/FiloSottile/age age] and a [[Rust]] implementation called [https://github.com/str4d/rage rage]. Age is often used as a [[Gnupg|GnuPG]] replacement. It should be noted that age does not support signing; another tool like [[Minisign]] is needed to fully migrate away from [[Gnupg|GnuPG]]. Age is significantly less complex then [[Gnupg|GnuPG]] and does not have a keyring, instead storing keys as files. According to the author, it is pronounced with a hard ''g'' ([[wikipedia:International_Phonetic_Alphabet|IPA]] [g]), rather than the soft ''g'' (IPA [j]) of the English word ''age'', and is uncapitalized<ref>[https://github.com/FiloSottile/age GitHub repo for the go implementation], age contributors, last updated March 2026 (accessed 2026-05-23)</ref>. == Examples == Visit [[Age/Examples]] for various examples of how to use <code>age</code>. 449139bddbb7335fd3fcb06d2e7bf2106140b8b1 0 198 5215 5116 2026-05-25T06:30:04Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 219b397be1d220f2fa3f4798c4e9e8f2ef8d3527 0 1187 5216 4965 2026-05-25T06:31:20Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{Stub}}{{SoftwareInfobox|image=[[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]]|caption=|title=Godot|releasestatus=Maintained|lastrelease=4.6.3-stable, 2026-05-20|firstrelease=1.0, 2014-12-15|languages=[[C++]]|developers=Juan Linietsky, Ariel Manzur, and Contributors|website=[https://github.com/godotengine/godot github.com/godotengine/godot], [https://godotengine.org godotengine.org]}}Godot is a general-purpose FOSS game engine. It uses a node- and scene-based editor and supports C++, C#, and its original scripting language, [[GDScript]], plus other languages through community tools.<ref>[https://godotengine.org/features/#script Features], Godot Engine, 2026-05-20 (Accessed: 2026-05-25)</ref> The name comes from the classic play ''[[wikipedia:Waiting_for_Godot|Waiting for Godot]]'' and is pronounced as therein. This results in the pronunciation varying between languages, which the project officially describes as "beautiful".<ref>[https://godotengine.org/press/ Press Kit], Godot Engine, 2026-05-01 (Accessed: 2026-05-25)</ref> [[Category:Software]] [[Category:Game Engines]] 7401350b1744c92b12ab3ee6e8ef80e720f1a08d 0 1176 5217 4964 2026-05-25T06:31:36Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Chimera Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[apk-tools]] | defaultdesktops = [[GNOME]], [[Terminal User Interface]] | usagetype = Desktop | architectures = x86_64, ppc, ppc64, ppc64le, aarch64, riscv64 | website = [https://chimera-linux.org/ chimera-linux.org] }} '''Chimera Linux''' is an independent [[Linux Distributions|Linux distribution]] characterized by using novel tooling, approaches, and userland.<ref>[https://chimera-linux.org/ Chimera Linux], Chimera Linux, 2026-05-02 (Accessed: 2026-05-25)</ref> <references /> 41d9efc54b8514bbcae5a76dfb69708180d80dde 0 659 5218 4294 2026-05-25T06:37:08Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{stub}} {{DistributionInfobox |title=ChromeOS |image=[[File:ChromeOS Logo.svg]] |caption=ChromeOS Logo |releasestatus=Maintained |releasemodel=Stable |packagemanager=None |defaultdesktops=Chromium, Aura Shell |usagetype=Desktop |architectures=x86_64, IA-32, ARM, ARM64 |website = [http://chromeos.google chromeos.google] }} ChromeOS is a Linux distribution based on [[ChromiumOS]] designed and developed by Google in 2009. ChromeOS is composed mostly of proprietary software but includes open source software, such as the kernel itself.<ref>[http://source.chromium.org/chromiumos ChromiumOS], ChromiumOS Code Search, 2026-05-25 (Accessed: 2026-05-25)</ref> == References == 18a64892f7edbc4f6bfc412d7412580e30d2139a 0 441 5219 3615 2026-05-25T06:37:40Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[File:640PxGNU logo.png|alt=This Image depicts a bodyless Bull-like animal who is smirking at the user, this image is for the logo for GNU Project.|thumb|The GNU Project's Logo]] GNU (Pronounced with a hard "g," like "grew" but replace the "r" with a "n,")<ref>[https://www.gnu.org/gnu/pronunciation.en.html How to Pronounce GNU], The GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> is a dedicated organization for free [[:Category:Software|software]] with development of their immense list of software<ref>[[wikipedia:List_of_GNU_packages|List of All GNU Packages]], Wikipedia, ''Wikipedia, The Free Encyclopedia.''</ref>; although you can technically use it as a standalone [[Operating System|operating system]] because of its arrival with all the necessities an operating system may need to functional appropriately, it is largely mixed in with other developed software whether it is free or [[Proprietary software|proprietary]]: A few are GNU/[[Linux]], [[MacOS]], [[UNIX|Unix-based]]/like OS, and even Windows. Due to GNU's License, majority of it is covered by the GPL made by the GNU Project. GNU's founder, '''Richard Matthew Stallman''' developed the project to fight against the proprietary software of the time; additionally, as a free software activist, he wanted users all over the world to be granted powers over their computer and allowing users to freely run, copy, share, distribute, and modify any software. == GNU's Name == The name "GNU" is a recursive acronym; Because of its Unix-like property, the acronym's full form is "GNU's Not Unix!"<ref>[https://www.thefreedictionary.com/GNU%27s+Not+Unix The Free Dictionary], Definition 1, ''The Free Dictionary By Farlex''</ref>, though it does differ from it in many ways but more blatantly, it contains no Unix Code, hence, the "Not Unix" part of its name. Adding on, he also found inspiration in the song named "The Gnu."<ref>[https://mjesec.ffzg.hr/~dpavlin/stallman2006/free_software_movement_and_the_future_of_freedom_zagreb_09_march_2006.ogg "The Free Software Movement and The Future Of Freedom,"], Zagreb, Croatia: Free Software Foundation Europe.</ref> == Included Software / Components == [[File:Gnu compiler collection-logo-1.png|alt=This logo depicts a Bull shaped animal jumping out of an egg, in black text that displays the letters G, C, C|left|thumb|224x224px|A logo of the GCC.]] As of June 2024, the GNU project currently holds 394 active [[packages]], but including the decommissioned packages puts the total up to 467.<ref>[https://www.gnu.org/software/software.en.html Software], GNU Project, ''Let Proprietary Software Be A Thing Of The Past!''</ref> There are some key components: [[GNU Compiler Collection]] (GCC) made for the compiling of [[C]], [[GNU C library]] (glibc) containing additional resources and ensure quality-of-life components are included, and [[GNU Core Utilities]] (coreutils) for any necessary software, but contains more packages that are deemed required for a fully stable operating system. Overall, these components are in many operating systems, mainly because of how easy GCC is to access for any developer. Because of Richard Stallman, he was able to free the variety of tools and software developed for the GNU project and in turn, pushed forward for the movement of open and free software for all.<ref name=":0" /> == History of GNU == [[File:RichardStallman.jpg|alt=A Picture of Richard Matthew Stallman in 2024|thumb|341x341px|A Picture of Richard Matthew Stallman in 2024]] Initiated by Richard Stallman whilst working at MIT's Artificial Intelligence Laboratory on September 27th, 1983, he announced the initialization of the GNU project<ref name=":0">[https://groups.google.com/g/net.unix-wizards/c/8twfRPM79u0/m/1xlglzrWrU0J Free Unix!], Richard Stallman. September 27th, 1983, ''New Unix Implementation''</ref> though the development was delayed until January 5th, 1984. Stallman would quit his job in order for him to successfully distribute GNU without interference from his job, whether they delay him or take over GNU.<ref>[https://books.google.com/books?id=jXC6H8lRjlUC Inter/vention: Free Play in the Age of Electracy], Holmevik, Jan Rune; Bogost, Ian; Ulmer, Gregory, March 2012</ref> With its release, also came with its decision to convert to a more Unix-compatible [[architecture]] because Stallman uncovered how Incompatible Timesharing System (ITS) was obsolete as it was written in [[Assembly]]. Stallman decided development of such system will be coded in C and [[Lisp]], although compatible with Unix, being Unix-like, it did not use any code provided by Unix because of Stallman's beliefs.<ref>[https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985https://ftp.math.utah.edu/pub/tex/bib/toc/dr-dobbs-1980.html#10(3):March:1985 Open Sources 2.0: The Continuing Evolution], DiBona Christ; Stone, Mark; Cooper Danese, October 2005.</ref> Although everything had to be written from scratch, it did not stop development from striving, even if development had to use third-party free software components. Most of GNU was written by volunteers whether it be purely voluntarily or paid by companies. October 1985, Stallman would set up the FSF (Free Software Foundation). The FSF hired developers to help write software needed for GNU.<ref>[https://books.google.com/books?id=LlCnYt2snHYC The Software Industry], Peter Buxmann, Diefenbach, Thomas Hess, September 30, 2012.</ref><ref>[https://books.google.com/books?id=Ps2SH727eCIC The Linux Programming Interface: A Linux and UNIX System Programming Handbook], Kerrisk, Michael (October 2010)</ref> == References == <references /> aa3d0e85168b5b6732a224ea858f9ddd2abd816e 0 823 5220 4027 2026-05-25T06:37:50Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{Stub}} [[Category:Mascots]] [[File:OpenSUSE Button.svg|alt=Geeko is a chameleon drawing and is the mascot for openSUSE.|thumb]] '''Geeko''' is the official mascot of [[openSUSE]]. It is a chameleon and not a gecko.<ref>https://en.opensuse.org/openSUSE:Geeko, openSUSE, 2010-07-14 (Accessed: 9 August 2025).</ref> == References == <references /> 7c15c41b3e84401f512ca35fb1933f1ad347fc60 0 355 5221 4714 2026-05-25T06:39:18Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |title=GNU C Library |releasestatus=Maintained |lastrelease=2.43, 2026-01-23<ref>[https://inbox.sourceware.org/libc-announce/13932477.uLZWGnKmhe@pinacolada/T/ The GNU C Library version 2.43 is now available], Andreas K. Huettel, 2026-01-23 (Accessed: 2026-05-25)</ref> |firstrelease=0.1, 1991-10-08<ref>[https://sourceware.org/glibc/wiki/Glibc%20Timeline Glibc Timeline], glibc wiki, 2026-04-11 (Accessed: 2026-05-25)</ref> |languages=[[C]], [[Assembly]] |developers=The GNU Toolchain Authors |website=[https://www.gnu.org/software/libc/ www.gnu.org/software/libc] }} The '''GNU C Library''', commonly known as '''glibc''', is the GNU Project implementation of the C standard library. It provides a wrapper around the system calls of the Linux kernel and other kernels for application use. Despite its name, it now also directly supports C++ (and, indirectly, other programming languages). It was started in the 1980s by the Free Software Foundation (FSF) for the GNU operating system. ==References== <references /> [[Category:Software]] 8b9ae09f73cb13ea4f51cd4399465fdf0104cef7 5248 5221 2026-05-25T07:16:38Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox |title=GNU C Library |releasestatus=Maintained |lastrelease=2.43, 2026-01-23<ref>[https://inbox.sourceware.org/libc-announce/13932477.uLZWGnKmhe@pinacolada/T/ The GNU C Library version 2.43 is now available], Andreas K. Huettel, 2026-01-23 (Accessed: 2026-05-25)</ref> |firstrelease=0.1, 1991-10-08<ref>[https://sourceware.org/glibc/wiki/Glibc%20Timeline Glibc Timeline], glibc wiki, 2026-04-11 (Accessed: 2026-05-25)</ref> |languages=[[C]], [[Assembly]] |developers=The GNU Toolchain Authors |website=[https://www.gnu.org/software/libc/ www.gnu.org/software/libc] }} The '''GNU C Library''', commonly known as '''glibc''', is the GNU Project implementation of the C standard library. It provides a wrapper around the system calls of the Linux kernel and other kernels for application use. Despite its name, it now also directly supports C++ (and, indirectly, other programming languages). It was started in the 1980s by the Free Software Foundation (FSF) for the GNU operating system. ==References== <references /> f6c7fad18b49c7cf3437ad665492de1248c2f4fd 0 349 5222 4412 2026-05-25T06:40:08Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Terminology]] In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is typically used to properly start up and manage services during boot and run time, making it necessary for OSes to properly run. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor'''<ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref> of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in an operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages</ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, etc. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |runit |February 10, 2004 |September 29, 2024 |↓ |Gerrit Pape |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS. == References == <references /> ad171c57083cb5954785d971378b3c4316406b50 0 661 5223 4927 2026-05-25T06:40:43Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Kali Linux | image = [[File:Kali-dragon-icon.svg|frameless]] | caption = Kali Logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[APT]] | defaultdesktops = [[Xfce]], [[GNOME]], [[KDE Plasma]] | usagetype = Desktop, Mobile, USB | architectures = x86_64, x86, armel, armhf | website = [https://www.kali.org/ Kali.org] }} '''Kali Linux''' (originally Backtrack Linux<ref>[https://www.kali.org/docs/introduction/kali-linux-history/ Kali Linux History], Kali Linux Documentation, 2026-05-25 (Accessed: 2026-05-25)</ref>) is an open-sourced [[Debian|Debian-based]] [[Linux Distributions|distribution]] specially designed for hacking, digital forensics, and penetration testing. It is maintained and funded by [https://www.offsec.com/ '''Offensive Security''']. === Features === Kali Linux is supported in wide range of devices ranging from Raspberry Pis to modern systems. It comes preinstalled with various tools useful for security professionals and includes a custom kernel patched for injection. It is also suitable for live USB boot with persistence.<ref>[https://www.kali.org/docs/nethunter/ Kali NetHunter], Kali Linux Documentation, 2026-05-25 (Accessed: 2026-05-25)</ref> === Installation === There are various ways to get Kali Linux. One can download the respective Kali version from the [https://www.kali.org/get-kali/#kali-platforms official download page].<ref name=":0">[https://www.kali.org/docs/installation/ Installation | Kali Linux Documentation], Kali Linux Documentation, 2026-05-25 (Accessed: 2026-05-25)</ref> {| class="wikitable mw-collapsible" |+Kali Variations<ref>www.kali.org/get-kali/#kali-installer-images</ref> !Variation !Function |- |ISO File |The most common way to install; suitable for both single and multi boot; providing the best performance. |- |Virtual Machine Image |Pre-built images for running Kali in a virtual machine; has higher system requirements. |- |ARM |Suitable for ARM devices; not guaranteed a custom kernel; some packages missing. |- |Mobile (Nethunter) |Kali for smartphones. |- |Cloud |Running Kali on a cloud server; not guaranteed a custom kernel. |- |Containers |Quick and easy access to Kali using software such as Docker; no custom kernel; no direct access to hardware thus slow. |- |Live Boot (Recommended) |Quick and easy access to Kali on the go. The preferred method of using Kali Linux. |- |WSL |Using Kali in windows. |} A bare bones version of Kali can also be installed which has a headless size of 1.5GB, the default Kali Linux is around 13GB while the version with everything in it is around 34GB.<ref>[https://www.kali.org/docs/installation/installation-sizes/ Kali Installation Sizes], Kali Linux Documentation, 2026-05-25 (Accessed: 2026-05-25)</ref> Full guide to installation size with various [https://atl.wiki/Desktop_Environments Desktop Environments] can be found [https://www.kali.org/docs/installation/installation-sizes/ here] . The system requirements vary but generally minimum of 2GB RAM and 20GB of disk space is needed to run Kali. Installation of Kali can be done fairly easily using the official GUI installer. The official guide to installing Kali are at:<ref name=":0" /> * [https://www.kali.org/docs/installation/hard-disk-install/ Hard Disk Install] * [https://www.kali.org/docs/installation/hard-disk-install-on-mac/ Mac Hardware] * [https://www.kali.org/docs/installation/dual-boot-kali-with-linux/ Dual Booting with Linux] (What's [[Dual Booting|Multi Booting]]) * [https://www.kali.org/docs/installation/dual-boot-kali-with-mac/ Dual Booting with MacOS] * [https://www.kali.org/docs/installation/dual-boot-kali-with-windows/ Dual Booting with Windows] === Other Versions === '''[https://www.kali.org/docs/nethunter/ Kali Nethunter]''' is the mobile version of Kali Linux, available for unrooted devices (Nethunter Rootless), rooted devices with custom recovery (Nethunter Lite), rooted devices with custom recovery and custom kernel (Nethunter) and on certain supported devices with '''full functionality''' (Nethunter Pro).<ref>[https://www.kali.org/docs/nethunter/ Kali NetHunter], Kali Linux Documentation, 2026-05-25 (Accessed: 2026-05-25)</ref> See [https://www.kali.org/docs/nethunter/#10-nethunter-editions Nethunter Editions] for detailed comparison between the editions and [[Kali Nethunter]] for more details. '''[https://gitlab.com/kalilinux/kali-purple/documentation/-/wikis/home Kali Purple]''' is the enterprise grade version of Kali which comes with over 100 tools, Kali Autopilot (automatic script builder) and its own wiki. == References == <references /> === Footnotes === * KALI LINUX ™ is a trademark of [https://www.offsec.com/ OffSec]. eba0fdc1fec785733703f7b0fed268ed375c022e 0 171 5224 4140 2026-05-25T06:41:33Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such as nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental (But mostly stable and trusted) feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Disko === [https://github.com/nix-community/disko Disko] is a NixOS module for configuring disk layouts and their partitions. It facilitates the quick and easy installation of NixOS on systems with the same disk setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024)</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== Following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org{{Dead Link|2025-08-14|Cannot connect to host save-nix-together.org:443 ssl:default [Connect call failed ('35.220.189.138', 443)]}} NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> 97a2eb1fec46981291aa9cc0153e16570540073d 0 1040 5225 5093 2026-05-25T06:41:55Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = [[DNF]], [[APT]] | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = [[systemd]] | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Qubes OS separates applications and workflows into isolated compartments known as '''qubes'''<ref>also known as a '''domU,''' '''security domain,''' or simply '''domain'''</ref> by leveraging [[Xen]]-based virtualization<ref name=":0">{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/intro.html|title=Introduction to Qubes OS|accessdate=2026-05-24}}</ref>. It should also be noted that Qubes, rather than being considered a Linux distribution, may be considered as either a ''meta-distribution'' (in a similar regard as [[Bedrock Linux]]), or a Xen distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#is-qubes-just-another-linux-distribution|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Technically, any [[X86-64|x86_64]] operating system may be used as a qube, but the extent to which it is supported varies. == Installation == The Qubes OS project provides a [https://doc.qubes-os.org/en/latest/user/downloading-installing-upgrading/installation-guide.html comprehensive installation guide] in its documentation. Users may consider reading the documentation on [https://doc.qubes-os.org/en/latest/user/downloading-installing-upgrading/install-security.html installation security] as well. === System Requirements === The following features are <u>required</u> (but may not be sufficient) for Qubes OS<ref name=":2">{{Cite|url=https://doc.qubes-os.org/en/latest/user/hardware/system-requirements.html|title=System Requirements|author=Qubes OS Project|accessdate=2026-05-25}}</ref>: * [[X86-64|64-bit Intel or AMD processor]] ** Intel VT-x with EPT or AMD-V with RVI ** Intel VT-d or AMD-Vi (also known as AMD IOMMU) * 6 GB RAM * 32 GB free space on disk The following are <u>recommended</u> for running Qubes OS<ref name=":2" />: * [[X86-64|64-bit Intel processor]] ** Intel VT-x with EPT ** Intel VT-d ** AMD processors are not recommended due to inconsistent security support on client platforms (see Important Notes for details). * 16 GB RAM * 128 GB free space ** A fast solid-state drive is strongly recommended by the project * An Intel integrated graphics processor is strongly recommended by the project ** Nvidia GPUs may require significant troubleshooting. ** AMD GPUs have not been formally tested, but Radeons (especially RX580 and earlier) generally work well. * A non-USB keyboard, or multiple USB controllers * A Trusted Platform Module (TPM) with proper BIOS support == Supported [[Qubes OS#Templates|Templates]] == The Qubes OS project officially provides the following templates: * [[Fedora]]-based ** [[XFCE]] ** [[GNOME]] ** Minimal (CLI only) * [[Debian]]-based ** XFCE ** GNOME ** Minimal (CLI only) Community-supported templates are also available, [https://doc.qubes-os.org/en/latest/user/templates/templates.html#community with additional considerations]: * [[Kicksecure]] * [[Whonix]] **Whonix Gateway **Whonix Workstation * Arch (in <code>qubes-templates-community-testing</code>) Users will also be able to create their own Templates from scratch == Architecture == Each qube is implemented as a separate [[Xen|Xen virtual machine]], which the user may utilize for activities such as composing documents or browsing the web<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/getting-started.html|title=Qubes OS Basics|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Each qube is distinguished by its name, which identifies its purpose, and a color which identifies its level of trust<ref name=":0" />. Qubes are copy-on-write, meaning that a [https://doc.qubes-os.org/en/latest/user/advanced-topics/volume-backup-revert.html full revert mechanism is available should it be needed]. === Templates === Templates provide root filesystems for app qubes. When an app qube is started, a copy of the root filesystem will be made and used by the app qube, then discarded on shutdown<ref name=":3">{{Cite|url=https://doc.qubes-os.org/en/latest/user/reference/glossary.html|title=Glossary|author=Qubes OS Project|accessdate=2026-05-25}}</ref>. Software meant to be run in app qubes must be installed in the corresponding template. See https://doc.qubes-os.org/en/latest/user/templates/templates.html === App qubes === App qubes are qubes where the user is meant to conduct everyday activities. An app qube will use a copy of the root filesystem taken from a chosen [[Qubes OS#Template|template]], and will only keep things in <code>/home/</code>and <code>/usr/local/</code>after being restarted<ref name=":3" />. App qubes can also be disposable templates and provide the base for disposable qubes. === Disposables === Disposable qubes obtain a fresh filesystem from its disposable template (distinct from a template) upon startup and fully discard it after shutting down<ref name=":3" />. === Standalones === A regular vm, both root and user directories are kept between starts<ref name=":3" />. == Security == === Qubes Master Signing Key === The QMSK is an [[Gnupg|OpenPGP]] key used as the root of trust for the Qubes OS Project to verify developer keys, release signatures, and communications<ref name=":1">{{Cite|url=https://doc.qubes-os.org/en/latest/project-security/verifying-signatures.html#how-to-import-and-authenticate-the-qubes-master-signing-key|title=Verifying signatures|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. The QMSK is available from the Qubes Project at https://keys.qubes-os.org/keys/qubes-master-signing-key.asc, or in any Qubes OS provided qube at <code>/usr/share/qubes/qubes-master-key.asc</code>. Users are encouraged by the Qubes Project to "distrust the infrastructure"<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#what-does-it-mean-to-distrust-the-infrastructure|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-25}}</ref> and to compare multiple channels to verify the QMSK's fingerprint<ref name=":1" /> Any single source (including this website) should not be trusted. One copy is provided here as: <code>0x427F11FD0FAA4B080123F01CDDFA1A3E36879494</code> Other potential channels to obtain the fingerprint from include: * The Qubes OS Project wiki * Video recordings of presentations about Qubes * Asking a friend(s) * Asking a stranger(s) === Limitations === It is important to note that while Qubes OS is designed to to limit the damage caused by the compromise of one or multiple qubes, <u>it does ''not'' attempt at additional hardening for the VM operating system itself</u> above that of the base distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/developer/system/security-design-goals.html#security-design-goals|title=Security Design Goals|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Users may consider using other security-oriented distributions in conjunction with Qubes OS for additional security. == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] b66c82bf252374c5b04e6cefe3f521b7fbd0cacd 0 558 5226 4799 2026-05-25T06:42:52Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Rust-Logo.png]] | caption = Rust Logo | title = Rust | releasestatus = Maintained | lastrelease = 1.95.0 (2026-04-16)<ref>[https://blog.rust-lang.org/2026/04/16/Rust-1.95.0/ Announcing Rust 1.95.0], The Rust Release Team, April 16 2026 (Accessed: May 22 2026)</ref> | languages = [[Rust]], originally written in [[OCaml]] | developers = The Rust Team; Originally by Graydon Hoare | website = [https://www.rust-lang.org/ rust-lang.org] }} Rust is a modern multi-paradigm programming language with a focus on performance, reliability, and productivity<ref>[https://github.com/rust-lang/rust GitHub - rust-lang/rust], 2010-05-25 (Accessed: 2026-05-25)</ref>. Although originally designed as a systems-level language, Rust has found widespread adoption as a general purpose programming language thanks to its high degree of expressiveness, strict type safety and memory safety, its easy-to-use package manager Cargo and crates ecosystem, and its ability to achieve native performance with high level code. Rust was heavily inspired by functional programming languages in its emphasis on immutability and pattern matching, as well as by [[C++]] for its RAII (resource allocation is initialization) and other performance features. Rust is most often compared with and considered an alternative to C++. In 2025, Rust was officially accepted into the [[Linux kernel]]<ref>https://www.phoronix.com/news/Rust-To-Stay-Linux-Kernel{{Dead Link|2026-05-25|403}}</ref>, after a lengthy trial period (the Rust for Linux experiment) that started in December 2022, becoming the third language accepted in the kernel after [[C]] and [[assembly]]. [[Canonical]], the company behind Ubuntu and other FOSS, is replacing the GNU coreutils project, written in C, with uutils, a Rust rewrite<ref>[https://archive.fosdem.org/2025/schedule/event/fosdem-2025-6196-rewriting-the-future-of-the-linux-essential-packages-in-rust-/ Rewriting the future of the Linux essential packages in Rust?], FOSDEM 2025, 2025-09-18 (Accessed: 2026-05-25)</ref>. This has attracted criticism around its licensing changing from GNU GPL to [[MIT License|MIT]] and makes uutils more friendly to proprietary software<ref>[https://github.com/uutils/coreutils/issues/834 Bug: Not GPL. :-) · Issue #834], uutils/coreutils · GitHub, 2016-03-22 (Accessed: 2026-05-25)</ref>. === Syntax, Features, and More === Upon the installation of Rust, <code>cargo</code> and other dependencies, you can generate a rust environment to work in. <code>cargo new [Project-name]</code> will generate a directory with the name of <code>[Project-Name]</code> that looks similar to this:<syntaxhighlight lang="markdown"> Project-Name ├╴src ; Contain all code for project │ └╴main.rs ; Code is executed here ├╴Cargo.toml ; Dependencies file └╴.gitignore ; Git ignore file </syntaxhighlight> ==== Hello World! ==== Upon opening the <code>main.rs</code> file, you will be greeted with 3 lines of code:<syntaxhighlight lang="rust" line="1"> fn main() { println!("Hello World!"); } </syntaxhighlight><code>fn main() { ... }</code> is the main function, all code written within the <code>main()</code> scope will be ran normally. You can call functions from outside of the main function, for example: <code>println!("Hello World!")</code> is a function that prints a new line and writes out to the terminal.<ref>[https://doc.rust-lang.org/std/macro.println.html println in std] - Rust std Documentation, Since 1.0.0 (Accessed: February 15th, 2025)</ref> To declare a variable, use the <code>let</code> key word to declare a non-constant variable.<syntaxhighlight lang="rust" line="1"> fn main() { // declares a new variable with type i32 (32-bit signed integer) let var_name: i32 = 64; // variables are immutable by default, use `mut` to make one mutable let mut another_var: i32 = 86; another_var = 128; } </syntaxhighlight>Using <code>let</code> defines a new variable. To specify the type of value a variable, write out <code>[var_name]: [type]</code>. See [[#Variable Types]] for a list of built-in types. You are also allowed to use multiple <code>let</code> terms to define a variable with the same name:<syntaxhighlight lang="rust" line="1"> fn main() { let var = 32; // Automatically defined as i32 Variable let var = var * 2; } </syntaxhighlight>This program defines <code>var</code> again by using the original value of it and multiplying it by 2, in this case, we aren't required to use the <code>mut</code> term. This operation is called '''variable shadowing'''.<!-- More will be done soon - Izakyar/Rayk4z1 --> === Data Types === Rust has a number of primitive builtin types, denoted in lowercase, as well as complex objects from the standard library that behave like primitives in other languages. {| class="wikitable" |+Primitive integer types (signed/unsigned) !Length !Signed (-/+) !Range !Unsigned (+) !Range |- |1-Byte |<code>i8</code> | -128 to 127 |<code>u8</code> |0 to 255 |- |2-Byte |<code>i16</code> | -32,768 to 32,767 |<code>u16</code> |0 to 65,535 |- |4-Byte |<code>i32</code> | -2,147,483,648 to 2,147,483,647 |<code>u32</code> |0 to 4,294,967,295 |- |8-Byte |<code>i64</code> | -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 |<code>u64</code> |0 to 18,446,744,073,709,551,615 |- |16-Byte |<code>i128</code> | -170,141,183,460,469,231,731,687,303,715,884,105,728 to 170,141,183,460,469,231,731,687,303,715,884,105,727 |<code>u128</code> |0 to 340,282,366,920,938,463,463,374,607,431,768,211,455 |- |arch |<code>isize</code> |Dependent on architecture of system: either <code>i32</code> or <code>i64</code> respectively |<code>usize</code> |Dependent on architecture of system: either <code>u32</code> or <code>u64</code> respectively |} Rust does not have a single string type; below is a non-comprehensive list of the most common ways to represent a string: {| class="wikitable" |+String types !Name !Stack or heap !Description |- |<code>&str</code> |Stack |A reference to a UTF-8 string slice, <code>str</code>only really exists as a reference type. These are immutable. |- |<code>&'static str</code> |Stack |The type of a string literal embedded into sourcecode. The <code>'static</code> lifetime means that the <code>&str</code> lasts forever. |- |<code>char</code> |Stack |Represents a single UTF-8 codepoint. |- |<code>String</code> |Heap |A full heap-allocated, possibly mutable UTF-8 string. |- |<code>Vec<u8></code> |Heap |A heap-allocated list of arbitrary bytes; it's not actually a string, but it's commonly used instead of a <code>String</code> when you want to represent data that isn't necessarily UTF-8 encoded. |- |<code>Cow</code> |Might be either |Stands for copy-on-write. |} === Object-Orientated Programming in Rust === For Context, Object-Orientated Programming is a programming paradigm designed around the concept of objects. Said objects contain 2 main parts, the attributes and their code. Attributes hold data for an object, while their code implements methods. [[OO]]P allows for inheritance of object properties through different methods<ref>[https://www.techtarget.com/searchapparchitecture/definition/object-oriented-programming-OOP Object-Orientated Programming], Alexander S. Gillers, June 2024 (Accessed: February 15th, 2025)</ref><ref name=":0">[https://www.tandfonline.com/doi/abs/10.1080/03081079.2010.539975 Object-oriented simulation of systems with sophisticated control], Eugene Kindler & Ivan Krivy, November 10th, 2010 (Accessed: February 15th, 2025)</ref>: for example C++ uses class-based inheritance while a language like Lua uses a prototype-based way for inheritance.<ref>[https://cplusplus.com/doc/tutorial/inheritance/ Friendships and Inheritance], cplusplus.com (Unknown Publication Date!), (Accessed: February 15th, 2025)</ref><ref>[https://www.lua.org/pil/16.2.html Inheritance], Lua the Programming Language, PUCRio / LabLua, Updated June 25th, 2024 (Accessed: February 15th 2025)</ref> Rust takes a different approach to OOP with its use of <code>struct</code>s, <code>trait</code>s, <code>enum</code>s, and <code>impl</code>s.<ref>[https://doc.rust-lang.org/book/ch10-02-traits.html Traits: Defining Shared Behavior], The Rust Programming Language January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":1">[https://doc.rust-lang.org/book/ch05-01-defining-structs.html?highlight=structs#defining-and-instantiating-structs Defining Structs], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref>[https://doc.rust-lang.org/book/ch06-01-defining-an-enum.html?highlight=Enum#enum-values Defining an Enum], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref><ref name=":2">[https://doc.rust-lang.org/book/ch05-03-method-syntax.html Method Syntax], The Rust Programming Language, January 12th, 2025 (Accessed: February 15th, 2025)</ref> Similar to tuples, <code>struct</code>s in Rust can store multiple related values as fields. The difference is that fields must be referred via their given naming. <code>struct</code>s are more global and reusable, while tuples are more preferred for short-lived variables or returning (multiple) values from functions.<ref name=":1" /> <syntaxhighlight lang="rust" lines> // Having the struct outside of main() makes it available everywhere in the file struct MyStruct { field1: bool, field2: i32, field3: String, } fn main() { let object = MyStruct { field1: true, field2: 64, field3: String::from("Use structs you must!"), }; } </syntaxhighlight> Functional properties may be given to <code>struct</code>s with <code>impl</code>s, which stands for ''implement''. Having methods (i.e. functions in <code>impl</code> with <code>self</code>, <code>&self</code> or <code>&mut self</code> as the first parameter) also allows for reproducibility, since they can access <code>struct</code> fields via <code>self</code>. <ref name=":0" /><ref name=":2" /> <syntaxhighlight lang="rust"> struct Cube { length: i32, width: i32, height: i32 } impl Cube { fn volume(&self) -> i32 { self.length * self.width * self.height } } fn main() { let rubiks_cube = Cube { length: 3, width: 3, height: 3, }; println!("Cube's volume: {}", rubiks_cube.volume()); } </syntaxhighlight> The code declares a new struct with 3 values and an area finder function within the <code>impl Cube</code> scope. The <code>volume()</code> method may be used on any variable with type <code>Cube</code>. <!-- More coming soon - Izakyar --> === Memory Safety === [[File:2-Figure1-1.png|thumb|Memory Safety Diagram: What happens when a User Program Calls a Safe Rust API and an Unsafe Rust API]] Memory safety refers to the practice of preventing memory-related errors, such as null pointer dereferencing, buffer overflows, and use-after-free vulnerabilities.<ref name=":3">[https://llvm.org/pubs/2003-05-05-LCTES03-CodeSafety.pdf Memory Safety Without Runtime Checks or Garbage Collection!], Dinakar Dhurjati, Sumant Kowshik, Vikram Adve, Chris Lattner, May 5th, 2003 (Accessed: February 15th, 2025)</ref> Rust enforces memory safety through its ownership system, borrowing rules, and strict type checking, eliminating the need for manual memory management typically required in languages like C and C++.<ref name=":4">[https://blog.adacore.com/memory-safety-in-rust Memory Safety In Rust], Ben Brosgol, January 29th, 2024 (Accessed: Feburary 15th, 2025)</ref> Rust enforces an ownership model to manage memory at run time; Each value has a unique owner, and that ownership can be moved but not shared in a mutable sense. Upon a value exiting scope, Rust automatically deallocates it. This prevents any double-free errors and memory leaks.<ref name=":3" /><ref name=":4" /> Rather than copying or moving values, Rust uses “borrowing”; this allows for functions or such to call for the value without transferring ownership. Immutable Borrowing (<code>&T</code>) allows multiple immutable references to a value to coexist with each other. Only one mutable reference (<code>&mut T</code>) to a value is allowed at a time.<ref name=":3" /><ref>[https://medium.com/@pythonshield/introduction-to-memory-safety-in-rust-understanding-ownership-and-borrowing-3adfb2ab9b5e Introduction to Memory Safety in Rust: Understanding Ownership and Borrowing]{{Dead Link|2025-08-14|410}}, Paul Amman, October 1st, 2024 (Accessed: February 15th, 2024)</ref> == References == c63fec4aa8d02e6c3ce1351304dffb597cc2431e 0 1073 5227 4362 2026-05-25T06:45:04Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{Stub}} {{DISPLAYTITLE:s6}} '''s6''' is a suite of small and secure programs for process supervision and system initialization on [[UNIX|Unix-like]] [[Operating System|operating systems]], including [[Linux]] and [[BSD]] variants.<ref>[https://skarnet.org/software/s6/ s6 - skarnet's small supervision suite], skarnet.org, 2026-05-09 (Accessed: 2026-05-25)</ref> It was created by Laurent Bercot as a modern alternative to daemontools, [[Runit|runit]], and similar supervision suites, emphasizing reliability, security, minimalism, and proper dependency handling through readiness notification. s6 can function either as a full init system (with '''s6-linux-init''') or as a process supervisor under another init system. === Design === When used as a full init system with s6-linux-init, s6 operates in a staged boot process similar to other supervision-based inits: * '''Stage 1''': The s6-linux-init-provided /sbin/init performs early boot tasks (mounting filesystems, starting udev, basic system preparation) and then executes a one-time initialization script (typically /etc/s6-linux-init/scripts/rc.init or equivalent). This stage handles all non-recurring setup tasks and has direct access to the console for error recovery.<ref>[https://skarnet.org/software/s6-linux-init/ s6-linux-init - tools for a Linux init system], skarnet.org, 2026-05-09 (Accessed: 2026-05-25)</ref> * '''Stage 2''': The supervision tree is started, typically via s6-svscan scanning a service directory. Individual services are monitored by s6-supervise processes. Service dependencies and readiness are managed reliably without external mechanisms. This stage runs continuously until shutdown or reboot.<ref>[https://skarnet.org/software/s6/overview.html s6: an overview], skarnet.org, 2026-05-09 (Accessed: 2026-05-25)</ref> * '''Stage 3''': On halt or reboot, the supervision tree is cleanly stopped, and a shutdown script (typically /etc/s6-linux-init/scripts/rc.shutdown) performs final tasks such as unmounting filesystems and powering off the system. The core supervision framework ('''s6-svscan''' and '''s6-supervise''') is highly portable across Unix-like systems, while s6-linux-init provides Linux-specific early boot support. Advanced service management is available via the companion '''s6-rc''' package. === Distributions with s6 === * Adélie Linux (uses s6-linux-init for early boot with OpenRC service management)<ref>[https://pkg.adelielinux.org/current/s6-linux-init Package: s6-linux-init], Adélie current (Accessed: 2026-05-25)</ref> * [[Artix Linux]] (offered as official alternative, including s6-linux-init and s6-rc)<ref>[https://wiki.artixlinux.org/Main/S6 s6], Artix Wiki, 2026-05-25 (Accessed: 2026-05-25)</ref> * [[Gentoo|Gentoo Linux]] (s6, s6-linux-init, and s6-rc available as packages)<ref>[https://wiki.gentoo.org/wiki/S6-linux-init_(package) s6-linux-init (package)], Gentoo wiki, 2026-05-25 (Accessed: 2026-05-25)</ref> * Obarun Linux (s6 with 66 frontend as the default init and service manager)<ref>[https://web.obarun.org/ Obarun distribution], Obarun, 2026-05-25 (Accessed: 2026-05-25)</ref> == References == <references /> acf30507245fec4f61643a01c4c5a51f143584a8 0 1034 5228 4217 2026-05-25T06:45:57Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki Snap is a package management system aimed for desktops, cloud and IoT devices. The respective packages are termed as '''snaps''' which is a bundle of an app along with its dependencies which works across [[Linux Distributions|Linux distributions]].<ref>[https://snapcraft.io/about About Snaps], Snapcraft, 2026-05-25 (Accessed: 2026-05-25)</ref> Snapd is the background service that manages and maintain the installed snaps.<ref name=":0">[https://snapcraft.io/docs/installing-snapd Install the daemon], Snapcraft, 2026-01-13 (Accessed: 2026-05-25)</ref> The various snaps can be downloaded using the [https://snapcraft.io/store Snap Store]. One can build and publish snaps using [https://documentation.ubuntu.com/snapcraft/stable/ Snapcraft]. === Installation === Snapd needs to be running before a snap can be installed. It comes preinstalled with a few distributions by default such as [https://neon.kde.org/ KDE Neon], [[Manjaro]], [https://getsol.us/ Solus], [[Ubuntu]], Most [https://wiki.ubuntu.com/DerivativeTeam/Derivatives#Official_Ubuntu_Flavors Ubuntu Flavours] and [[ZorinOS]]. For distributions without Snapd preinstalled, one can refer to [https://snapcraft.io/docs/installing-snapd#without-snap this section] of the official documentation and choose their respective documentation to install Snapd.<ref name=":0" /> After installing Snapd, one can head over to [https://snapcraft.io/store Snap Store] for searching and installing the software they want.<ref>[https://www.geeksforgeeks.org/linux-unix/snap-package-manager-on-ubuntu/ Snap Package Manager on Ubuntu], GeeksforGeeks, 2020-01-27 (Accessed: 2026-05-25)</ref> === References === <references /> ea30a00dff5d93c760b52513a15bfc2a2df0fd0e 5229 5228 2026-05-25T06:47:44Z Madonuko 140 update reference direct link wikitext text/x-wiki Snap is a package management system aimed for desktops, cloud and IoT devices. The respective packages are termed as '''snaps''' which is a bundle of an app along with its dependencies which works across [[Linux Distributions|Linux distributions]].<ref>[https://snapcraft.io/about About Snaps], Snapcraft, 2026-05-25 (Accessed: 2026-05-25)</ref> Snapd is the background service that manages and maintain the installed snaps.<ref name=":0">[https://snapcraft.io/docs/installing-snapd Install the daemon], Snapcraft, 2026-01-13 (Accessed: 2026-05-25)</ref> The various snaps can be downloaded using the [https://snapcraft.io/store Snap Store]. One can build and publish snaps using [https://documentation.ubuntu.com/snapcraft/stable/ Snapcraft]. === Installation === Snapd needs to be running before a snap can be installed. It comes preinstalled with a few distributions by default such as [https://neon.kde.org/ KDE Neon], [[Manjaro]], [https://getsol.us/ Solus], [[Ubuntu]], Most [https://wiki.ubuntu.com/DerivativeTeam/Derivatives#Official_Ubuntu_Flavors Ubuntu Flavours] and [[ZorinOS]]. For distributions without Snapd preinstalled, one can refer to [https://snapcraft.io/docs/tutorials/install-the-daemon/#without-snap this section] of the official documentation and choose their respective documentation to install Snapd.<ref name=":0" /> After installing Snapd, one can head over to [https://snapcraft.io/store Snap Store] for searching and installing the software they want.<ref>[https://www.geeksforgeeks.org/linux-unix/snap-package-manager-on-ubuntu/ Snap Package Manager on Ubuntu], GeeksforGeeks, 2020-01-27 (Accessed: 2026-05-25)</ref> === References === <references /> 3695dbb3fc99b314dfd55641b8a3a7d8dba00220 0 886 5230 4751 2026-05-25T06:48:57Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Software]] {{Needs Citations|date=august 2025}} {{stub|date=august 2025}} The vi program is a full-screen console-based text editor. It was originally written in the 1970s by Bill Joy and improved in the 1980s by Mary Ann Horton, as an enhancement for [[ex]], which in tern was an enhanced version of [[ed]]. As such, vi still has many ex-like features today. ==Using vi== To use vi, you can hit <code>i</code> or <code>a</code> (append) to enter "insert mode". You then may type what you wish, and hit the <code>esc</code> key to exit "insert mode". When you're no longer in "insert mode", you can hit the ":" (colon) command to type in ex-like commands. The two most common commands are <code>w [filename]</code> to save the file, and <code>q</code>, which is used to quit the program. These commands can be combined to quit and save in one step, like so: <code>wq</code>. To quit without saving, enter <code>q!</code>. When not in insert mode, you may use the <code>h</code> key to move back one column, <code>j</code> to move the cursor down one line, <code>k</code> to move up a line, and the <code>l</code> to move forward one column. Please note that these letters are lowercase. As is often the case with Unix programs, capitalization matters. Also, when in insert mode, you <i>might</i> be able to use your arrow keys, although this seems to depend on which implementation of vi you are using. It is generally recommended to learn the above keys instead. ==Implementations== Modern implementations of vi consist of [[vim]], [[neovim]], [[elvis]], [[nvi]], Heirloom vi<ref>{{Cite|url=https://github.com/n-t-roff/heirloom-ex-vi|title=The Traditional Vi (vi with many enhancements from Gunnar Ritter)|author=Gunnar Ritter et al.|year=2022|accessdate=2026-05-22}}</ref>, the vi from [[Illumos]]<ref>{{Cite|url=https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi|title=illumos-gate/usr/src/cmd/vi on GitHub|author=Illumos core team|year=2025|accessdate=2026-05-22}}</ref>, and the version of vi built in to [[busybox]], the latter of which can be called via <code>busybox vi</code>. nvi/nex is a replacement for vi/ex and was originally developed as part of 4BSD.<ref>[https://man.openbsd.org/vi.1 vi(1)], OpenBSD manual pages, 2024-05-25 (Accessed: 2026-05-25)</ref> ed5e3f67c19089ba9e698f44611d1ca546823e90 0 763 5231 4205 2026-05-25T06:50:24Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki A window manager in the world of [[X11]] controls where programs display their [[GUI]], usually via a window paradigm where each [[application]] is its own box where it can display things. Many window managers aren't very usable on their own and are often paired with desktop shell and application suite.<gallery mode="packed"> File:Screenshot of awesomewm4.png|link=awesomewm|awesome File:Compiz Shift Switcher.png|link=Compiz|Compiz File:Openbox 3.4.10 default.png|link=Openbox|Openbox File:Twm.png|link=twm|twm File:Icewm-default.jpg|link=IceWM|IceWM File:I3-wm.png|link=i3|i3 File:Wmaker-0.80.2.png|link=Window_Maker|Window Maker File:Xmonad screenshot.png|link=Xmonad|XMonad </gallery> {| class="wikitable" |+ !Window Manager !Description |- |[[awesome]]<ref>[https://github.com/awesomeWM/awesome GitHub - awesomeWM/awesome: awesome window manager], awesomeWM, 2025-08-09 (Accessed: 2025-08-09)</ref> |awesome is a dynamic window manager for the X Window System developed in the C and Lua programming languages. |- |[[Compiz]] |Compiz is a compositing window manager for the X Window System. |- |[[Openbox]] |A minimal and highly configurable stacking window manager written in C. |- |[[twm]]<ref>[https://www.x.org/releases/X11R7.6/doc/man/man1/twm.1.xhtml TWM], 2010-11-13 (Accessed: 2025-08-09)</ref> |Tab Window Manager - standard X11 window manager since 1989. |- |[[IceWM]]<ref>[https://github.com/bbidulock/icewm GitHub - bbidulock/icewm: A window manager designed for speed, usability, and consistency], bbidulock, 2025-08-09 (Accessed: 2025-08-09)</ref> |Lightweight window manager that includes a taskbar, start menu and other features. |- |[[i3]]<ref>[https://i3wm.org i3: improved tiling X11 window manager], Michael Stapelberg, 2025-06-12 (Accessed: 2025-08-09)</ref> |A tiling window manager for advanced users and developers. |- |[[Window Maker]]<ref>[https://github.com/window-maker/wmaker GitHub - window-maker/wmaker: Mirror of the official repository repo.or.cz/wmaker-crm.git. Do not send pull requests here, send your patches to wmaker-dev@googlegroups.com instead], window-maker, 2020-08-09 (Accessed: 2025-08-09)</ref> |A window manager aiming to replicate the appearance of the NeXSTEP user interface. |- |[[XMonad]]<ref>[https://xmonad.org/ home | xmonad - the tiling window manager that rocks], xmonad, 2025-06-15 (Accessed: 2025-08-09)</ref> |Window Manager configurable via the Haskell functional programming language. |- |[[DWM|dwm]]<ref>[https://dwm.suckless.org/ dwm - dynamic window manager], Suckless, 2025-08-09 (Accessed: 2025-08-27)</ref> |A lightweight tiling window manager written in C. |} ==References== <references /> ac295bec08932b1092efad658cdda05c0fadc1d1 0 991 5232 4004 2026-05-25T06:53:42Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Z Shell Logo Color Vertical.svg|frameless|alt=The Zsh logo, a terminal window with a % prompt and the text ZSH on the bottom right]] | caption = Zsh Logo | title = Zsh | releasestatus = Maintained | lastrelease = 5.9 (2022-05-14) | languages = [[C]] | developers = Peter Stephenson and contributors | website = https://www.zsh.org }} The Z Shell(Zsh) is a cross-platform [[CLI]] with a focus on expanding on the [http://kornshell.com/ KornShell(ksh)].<ref name="zsh-introduction">{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Introduction.html#Introduction|title=Zsh Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> It offers features such as command line editing, built-in spelling correction, programmable command completion, shell functions (with autoloading) and a history mechanism.<ref name="zsh-introduction"/> While Zsh does not provide [[POSIX]] compatibility out-of-the-box, it is able to emulate both sh and ksh.<ref>{{Cite|url=https://zsh.sourceforge.io/Doc/Release/Invocation.html#Compatibility|title=Zsh Invocation Documentation|author=Zsh|year=May 14, 2022|accessdate=August 28, 2025}}</ref> == Notable Differences compared to Bash == * Zsh uses <code>.zshenv</code>, <code>.zshrc</code>, <code>.zshlogin</code>, <code>.zshlogout</code> and <code>.zprofile</code><ref>[https://zsh.sourceforge.io/Doc/Release/Files.html#Files Files], zsh, 2022-05-25 (Accessed: 2026-05-25)</ref> instead of <code>.bash_profile</code>, <code>login</code>, <code>.profile</code>, <code>.bash_logout</code> and <code>.bashrc</code><ref>[https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html Bash Startup Files (Bash Reference Manual)], GNU, 2025-05-25 (Accessed: 2026-05-25)</ref> * Zsh has built-in prompt theming via <code>promptinit</code> and the <code>prompt</code> command<ref>[https://zsh.sourceforge.io/Doc/Release/User-Contributions.html#Prompt-Themes User Contributions], zsh, 2022-05-25 (Accessed: 2026-05-25)</ref> and uses <code>%</code> escapes for prompt expansion<ref>[https://zsh.sourceforge.io/Doc/Release/Prompt-Expansion.html#Prompt-Expansion Prompt Expansion], zsh, 2022-05-25 (Accessed: 2026-05-25)</ref> instead of the <code>\</code> escapes used in bash<ref>[https://www.gnu.org/software/bash/manual/html_node/Controlling-the-Prompt.html#Controlling-the-Prompt Controlling the Prompt (Bash Reference Manual)], GNU, 2025-05-25 (Accessed: 2026-05-25)</ref> * Zsh arrays start at <code>1</code><ref name="array-subscript-zsh">[https://zsh.sourceforge.io/Doc/Release/Parameters.html#Array-Subscripts Parameters], zsh, 2022-05-25 (Accessed: 2026-05-25)</ref>, while bash arrays start at <code>0</code><ref>[https://www.gnu.org/software/bash/manual/html_node/Arrays.html Arrays (Bash Reference Manual)], GNU, 2025-05-25 (Accessed: 2026-05-25)</ref> == References == <references /> d8cf0531480df9989ddc7dab107aada4632ff91c 0 762 5233 4389 2026-05-25T06:53:55Z Hamachitan 222 /* References */ 🍣 Fix [[ATL:Guidelines#Citations|citations]] wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Zypper_Screenshot_2026-01-12.png|400px|Thumb]] | caption = Zypper install screenshot | title = Zypper | releasestatus = Maintained | firstrelease = 2006-01-14 | lastrelease = 1.14.94, 2025-09-23 | languages = [[C++]] | developers = [[SUSE]], [[openSUSE]] | website = [https://en.opensuse.org/Portal:Zypper Portal:Zypper] }} [[Category:Package Managers]] Zypper is the primary [[Package Manager|package manager]] for [[SUSE Linux Enterprise|SUSE Linux Enterprise]], [[openSUSE|openSUSE]] and their derivatives. Zypper is a command-line interface to ZYpp System Management Library (libzypp) and uses [[rpm|RPM]] package archives <ref>[https://manpages.opensuse.org/Tumbleweed/zypper/zypper.8.en.html zypper(8)] openSUSE manpages, 2025-09-23 (Accessed: 2026-01-12)</ref> similar to [[Fedora|Fedora Linux]] and [[RHEL|Red Hat Enterprise Linux]]. Zypper is a binary package manager with support for x86, x86-64 (amd64), ARM, s390x and PowerPC. <ref>[https://get.opensuse.org/tumbleweed/?type=server#download openSUSE Tumbleweed] openSUSE Tumbleweed download page showing supported CPU Architectures (Accessed: 2026-01-12)</ref> == History == libZypp and by extension ZYpp and Zypper were released on January 14th 2006. <ref>[https://github.com/openSUSE/libzypp/blob/90acb93974a99bea7409516be55d6acdc35099f7/package/libzypp.changes libzypp Github] Earliest libzypp changelog (Accessed: 2026-01-12)</ref> In March of 2025 Zypper added experimental support for parallel downloads starting in libzypp version 17.36.4 and Zypper version 1.14.87. <ref>[https://news.opensuse.org/2025/03/27/zypper-adds-experimental-parallel-downloads/ openSUSE] Announcement of experimental parallel downloads support (Accessed: 2026-01-12)</ref> In May of 2025 parallel downloads were enabled by default starting in libzypp version 17.37.1 and Zypper version 1.14.90. <ref>[https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JR725AXWDZYLJ3PKIKYAYQQAXE6OWQMM/ openSUSE] Announcement of parallel downloads becoming the new default (Accessed: 2026-01-12)</ref> == Usage == Zypper uses an argument system for interacting with the package manager with its syntax being <code>zypper [ARGUMENT] [PACKAGE]</code> for example <code>zypper install vim</code>. There are 2 forms of each argument, full and abbreviated, this behavior is similar to [[DNF|DNF]] the Fedora/RHEL package manager. {| class="wikitable" |+Common Zypper Arguments !Full !Abbreviated !Description |- |<code>zypper install [TARGET]</code> |<code>zypper in [TARGET]</code> |Installs or updates a given package or pattern (use <code>-t</code> flag when installing patterns) |- |<code>zypper remove [TARGET]</code> |<code>zypper rm [TARGET]</code> |Uninstalls a given package |- |<code>zypper update</code> |<code>zypper up</code> |Upgrades the installed packages without removing packages (This is the preferred way to update a Leap or SLES system) |- |<code>zypper dist-upgrade</code> |<code>zypper dup</code> |Upgrades the installed packages while performing vendor changes, package removals and renames (This is the preferred way to update a Tumbleweed system) |- |<code>zypper refresh</code> |<code>zypper ref</code> |Refreshes the package repository mirrors (This is performed automatically is zypper detects an out of date repository when running install, remove, update, dist-upgrade or search commands) |- |<code>zypper search [SEARCH-TERM]</code> |<code>zypper se [SEARCH-TERM]</code> |Searches the enabled repositories for packages or patterns containing the search term entered |- |<code>dry-run</code> |<code>-D</code> |Runs the command being dry-ran without making any changes to the system |- |} == References == 14398dfc26a68b23f82f7c5bf2096b4b54ee2828 0 1049 5234 4277 2026-05-25T07:10:08Z Madonuko 140 add category, fix links wikitext text/x-wiki [[Category:Terminology]] The '''KISS principle''' (short for Keep It Simple, Stupid) is a design philosophy that emphasizes '''simplicity''' and the avoidance of unnecessary complexity. It is commonly applied in engineering, software development, and system design, including many [[Unix]] and [[Linux]] projects. The idea behind '''KISS''' is that most systems work best when they are kept simple rather than made overly complicated. Designers following this '''philosophy''' strive to build solutions that are easy to understand, maintain, and extend. In software, '''KISS''' often means using straightforward tools and clear code instead of layers of abstraction or automation. This principle aligns closely with traditional Unix ideals of doing one thing well and keeping systems modular. The '''KISS''' '''philosophy''' continues to influence the design of '''minimalist''' and user-controlled operating systems, '''lightweight''' software, and development practices that favor clarity and efficiency over convenience or automation. fb38188637aa19044e08b27dd0bf5e4827937569 0 1192 5235 5214 2026-05-25T07:11:55Z Madonuko 140 /* References */ wikitext text/x-wiki {{Stub}} [[File:Age-help.png|thumb|The "help" screen for the go implementation of age, version 1.3.1]] '''Age''' [https://github.com/C2SP/C2SP/blob/main/age.md is a standard] for encrypting files and data similar to PGP but only supporting encryption and decryption. It has multiple implementations in common use, including a [[Go]] implementation also called [https://github.com/FiloSottile/age age] and a [[Rust]] implementation called [https://github.com/str4d/rage rage]. Age is often used as a [[Gnupg|GnuPG]] replacement. It should be noted that age does not support signing; another tool like [[Minisign]] is needed to fully migrate away from [[Gnupg|GnuPG]]. Age is significantly less complex then [[Gnupg|GnuPG]] and does not have a keyring, instead storing keys as files. According to the author, it is pronounced with a hard ''g'' ([[wikipedia:International_Phonetic_Alphabet|IPA]] [g]), rather than the soft ''g'' (IPA [j]) of the English word ''age'', and is uncapitalized<ref>[https://github.com/FiloSottile/age GitHub repo for the go implementation], age contributors, last updated March 2026 (accessed 2026-05-23)</ref>. == Examples == Visit [[Age/Examples]] for various examples of how to use <code>age</code>. == References == 6d4a26f3c790071cc868e204a9ed2cda320201d7 5237 5235 2026-05-25T07:14:48Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} [[File:Age-help.png|thumb|The "help" screen for the go implementation of age, version 1.3.1]] '''Age''' [https://github.com/C2SP/C2SP/blob/main/age.md is a standard] for encrypting files and data similar to PGP but only supporting encryption and decryption. It has multiple implementations in common use, including a [[Go]] implementation also called [https://github.com/FiloSottile/age age] and a [[Rust]] implementation called [https://github.com/str4d/rage rage]. Age is often used as a [[Gnupg|GnuPG]] replacement. It should be noted that age does not support signing; another tool like [[Minisign]] is needed to fully migrate away from [[Gnupg|GnuPG]]. Age is significantly less complex then [[Gnupg|GnuPG]] and does not have a keyring, instead storing keys as files. According to the author, it is pronounced with a hard ''g'' ([[wikipedia:International_Phonetic_Alphabet|IPA]] [g]), rather than the soft ''g'' (IPA [j]) of the English word ''age'', and is uncapitalized<ref>[https://github.com/FiloSottile/age GitHub repo for the go implementation], age contributors, last updated March 2026 (accessed 2026-05-23)</ref>. == Examples == Visit [[Age/Examples]] for various examples of how to use <code>age</code>. == References == e7552acaee8353d7f4f273202dfc30a45910f6c7 0 769 5236 5096 2026-05-25T07:13:59Z Madonuko 140 fix broken link in reference wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | [[MangoWM]]<ref>[https://mangowc.vercel.app MangoWM Homepage] (Accessed: 2026-02-27)</ref> || None || [[C]] || Extremely customizable & performant Wayland compositor built on top of [[dwl]]. |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| [[C]] || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | [[Sway]] || None || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || None (Tiling) || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[river]]<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref> || None (Tiling) || [[zig]]|| Lightweight and minimal tiling compositor focused on simplicity. |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || None (3D effects) || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || None (Kiosk) || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- | [[Niri]] || None (Scrolling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp cosmic-comp github repo], pop-os team et al., 2025 (Accessed: 2026-05-25)</ref> |[[COSMIC]] |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || None (Tiling) || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 2767da4f43d662ebd9c4acb8540c58bccc04dfa7 0 1115 5238 4803 2026-05-25T07:14:58Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Desktop Environments]] {{stub}} COSMIC is a FOSS Desktop Environment created by [[System76]], Also known as the creators of [[Pop!_OS]]. Originally a modified version of the [[GNOME]] Desktop Environment, System76 released their Alpha version of their in-house DE written in the [[Rust]] Programming Language on August 8th 2024. The current stable release is 1.0.13, Released on May 12, 2026. 1a0cb60bc4c1d8bba73e383682caed4965aac4e7 0 1058 5239 4305 2026-05-25T07:15:08Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] The '''Compose key''' can be used to input characters not present on the physical keyboard. Unlike [[input method]]s, users of compose key need to first press a specific key, then press a specific sequence of keys in order to obtain the final character. == Set-up == {{Guide Warning}} === KDE Plasma === In ''System Settings → Input/Output Devices → Keyboard'', press the ''Keybinding'' button on the top right corner. Enable the ''Set Keyboard Options'' checkbox, then select the preferred position in ''Position of Compose Key'', then click ''Apply''. === GNOME === A graphical option is not available. Visit [https://help.gnome.org/admin/system-admin-guide/stable/keyboard-compose-key.html.en this article] for the command-line instructions. === X11 === On [[X11]]-based environments, you can use [[setxkbmap]] to temporarily set the compose key. To permanently set the compose key: {{FileBox|title=~/.xprofile|content= setxkbmap -layout us compose:rctrl }} The list of options other than <code>rctrl</code> is available in <code>[[man]] 'xkeyboard-config(7)'</code>, in the '''Position of Compose Key''' section. === IBus === [[IBus]] users should follow the settings of your graphical environment. === Fcitx5 === To use Compose Key in [[Fcitx5]], go to ''Fcitx5 Settings → Global Options'', then in the ''Custom XKB Option'' entry, write <code>compose:rctrl</code>. == Usage == Press and release the chosen compose key (denoted as {{keypress|Multi}} in this article), {{keypress|o}}, and {{keypress|r}} separately. This produces the ® symbol. Other common shortcuts include {{keypress|Multi|>|{{=}}|chain=}} (which gives ≥) and {{keypress|Multi|-|-|-|chain=}} (which gives —). == Customisation == Apart from the listed combinations in <code>/usr/share/X11/locale/en_US.UTF-8/Compose</code>, compose key users can customise the key combinations. Here is an example: <!-- xorg_conf is no longer supported by the syntax highlighter, rip --> {{FileBox|lang=hcl|title=~/.XCompose|content= # Comments start with a hashtag # Empty lines are ignored include "%L" # import default rules from /usr/share/X11/locale/en_US.UTF-8/Compose <Multi_key> <semicolon> <x> : "❌" <Multi_key> <semicolon> <o> : "⭕" <Multi_key> <minus> <greater> : "→" <Multi_key> <equal> <greater> : "⇒" <Multi_key> <minus> <asciicircum> : "↑" <Multi_key> <equal> <asciicircum> : "⇑" <Multi_key> <minus> <v> : "↓" <Multi_key> <equal> <v> : "⇓" <Multi_key> <less> <minus> : "←" <Multi_key> <less> <equal> : "⇐" <Multi_key> <equal> <less> : "≤" U2264 # Less Than or Equal Symbol <Multi_key> <question> <A> : "∀" # FOR ALL <Multi_key> <question> <E> : "∃" # THERE EXISTS <Multi_key> <question> <I> : "∈" # IN, BELONGS TO <Multi_key> <question> <d> : "∂" U2202 # PARTIAL DIFFERENTIAL <Multi_key> <question> <G> : "∇" U2207 # NABLA (GRADIENT, BACKWARD DIFFERENCE) <Multi_key> <question> <S> : "∑" U2211 # SUMMATION }} 214b264b9cbf0127774059c5e6322284a5d254de 0 1217 5240 5083 2026-05-25T07:15:18Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox |image=[[File:Cryptomator Logo 2020.svg|thumb]] |caption=Cryptomator |releasestatus=Maintained |lastrelease=1.19.2, Mar 20, 2026 |firstrelease=1.0, Mar 9, 2016 |languages=[[Java]] |developers=[https://www.linkedin.com/company/skymatic Skymatic GmbH] |website=[https://cryptomator.org/ cryptomator.org] }} '''Cryptomator''' is a open source encryption program for creating encrypted vaults that can be synchronized to a cloud provider allowing for encrypted cloud storage. It works with any cloud provider that has file synchronization and can even be used to encrypt files you plan on storing locally, though other alternatives exist for that, such as [[KDE]] Vaults. f9e51200824e222fbf3b28a95f3b4287d5de45ee 0 1213 5241 5059 2026-05-25T07:15:28Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox |title=Cryptsetup |releasestatus=Maintained |lastrelease=2.8.6, Apr 2, 2026 |firstrelease=1.0.7, Jul 22, 2009 |languages=[[C]] |developers=[https://research.redhat.com/blog/article-author/milan-broz/ Milan Brož] |website=[https://gitlab.com/cryptsetup gitlab.com/cryptsetup] }} '''Cryptsetup''' is a tool for configuring, managing, opening, and closing encrypted LUKS storage devices. It is mostly used for the encryption of USBs and drives. LUKS (what cryptsetup uses behind the scenes) uses AES by default with a 512 bit keysize<ref>{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref>. How AES works will not be discussed here due to it being technical and out of the scope of this article, there are many resources online about it however. LUKS is part of the [[Linux kernel]]. One of the most common use of cryptsetup is creating an encrypted USB, for instructions on how to do that, refer to [[Guides:Creating a LUKS USB|this guide]]. <references /> 74540ab168be3e96ceb119555257e9d6ccadaa99 0 1167 5242 5033 2026-05-25T07:15:38Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = Devuan | image = [[File:Devuan-logo.png]] | caption = The Devuan logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[apt]] | defaultdesktops = Xfce | usagetype = Desktop, Server | architectures = amd64, arm64, armel, armhf, and ppc64el | website = [https://www.devuan.org/] }} '''Devuan''' ( /ˈdɛv.wʌn//), is a [[Debian]] derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian without [[systemd]]. It was first released on 2016-05-03, with the first stable version being released on 2017-05-25. [[File:Devuan6-xfce.png|thumb|A Devuan installation running Xfce]] == History == On 25 April 2015, [[Debian]] 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing [[sysvinit]], [[upstart]], and other init systems with [[systemd]] by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a [[Debian]] fork of what would become Devuan, aiming to provide people with the choice to other init systems again. The first stable release was released on 2017-05-25, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments ([[XFCE]], [[Cinnamon]], [[Plasma|KDE]], [[LXQt]], [[MATE]]) at install time, also providing installation options for choosing between [[sysvinit]] and [[OpenRC]] for init, and between [[GRUB]] and [[LILO]] for the boot loader, for the first time.<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems, according to the Devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Devuan uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from Debian that require [[systemd]] to systemd-less packages. While it is possible to use Debian packages directly, it can cause them to break.It also has a repository of proprietary packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from Devuan's website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Experimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making a bootable USB and booting it. | | |} Devuan is a [[Debian]] fork; therefore, the same minimum and recommended requirements also apply to Devuan. However, it is somewhat lighter than Debian, since it does not use systemd. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of Devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Trivia == * Unlike [[Debian]] who names it's stable releases after Toy Story characters, Devuan's stable releases are named after minor planets and asteroids. * Unlike [[Gentoo]] wich still gives the option to install and use [[Systemd]], devuan has absolutely no option to do this. == References == cf2b20c6102850f84775d9a6220a5ae6e64ade9f 0 173 5243 4376 2026-05-25T07:15:48Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Incomplete page}} [[Category:Terminology]] [[File:Fedora 21 login screen.png|alt=GDM on Fedora 21|thumb|GNOME Display Manager ('''GDM''') being displayed on a fedora workspace]] [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|A screenshot taken of SD'''DM''']] A Display Manager (DM), also known as a login manager, is typically a [[graphical user interface]] that is displayed at the end of the boot process in place of the default shell. It often includes a login screen for entering your credentials and the option to choose which [[Desktop Environment]] and Display Server to use. While often graphical, a Display Manager can also run within the TTY itself. == Role and Functions == The primary role of the Display Manager is to manage and control the graphical display sessions on a system. It performs several essential tasks: * User Authentication: The DM presents the graphical login screen (often referred to as the greeter) to authenticate users by checking their credentials. * Session Initiation: Upon successful login, it starts the user's chosen graphical session, which is typically a full [[Desktop Environment‏‎]] (DE) or a [[Window Manager‏‎]] (WM). Most DMs support both Wayland and X11 backends. * Session Management: It allows for switching between different users or desktop environments without requiring a full system reboot. == Examples == {| class="wikitable sortable" |+ Display Managers |- ! Name !! DE/Type !! Description |- | GDM || GNOME || '''G'''NOME '''D'''isplay '''M'''anager. Default for systems like Fedora and Ubuntu. Well-integrated with Wayland, but often considered more resource-intensive. |- | SDDM || KDE Plasma, LXQt || '''S'''imple '''D'''esktop '''D'''isplay '''M'''anager. Uses Qt/QML for a modern, highly customizable and visually appealing interface. Successor to KDM. |- | LightDM || Xfce, MATE || '''Light'''weight '''D'''isplay '''M'''anager. Known for being lightweight and highly configurable using separate "greeter" programs (e.g., `lightdm-gtk-greeter`). |- | '''XDM''' || X Window System || '''X''' '''D'''isplay '''M'''anager. The original, most basic DM for the X Window System. Minimalist and used primarily for its simplicity. |- | '''Ly''' || TUI || A text-based (TUI/ncurses-like) display manager that runs in the TTY but can launch both X and Wayland sessions, popular for extremely minimal setups. Written in Zig. |- | '''emptty''' || TUI || A dead simple TUI display manager similar to Ly that runs in the TTY and prioritizes simple yet powerful configuration. |} == Configuration == ==== Enabling a Display Manager (systemd) ==== On modern Linux distributions that use systemd, the DM is started as a system service. To switch the active DM, you typically disable the current service and enable the desired one. <syntaxhighlight lang="bash"> # Example: Switching from GDM to SDDM # 1. Stop and disable the old DM service sudo systemctl disable gdm.service sudo systemctl stop gdm.service # 2. Enable the new DM service sudo systemctl enable sddm.service --now # `--now` starts the service immediately once enabled </syntaxhighlight> 2. Session Definition Display Managers discover the available session options (like "GNOME," "KDE," "i3") by reading <code>.desktop</code> files in the following system directories: * <code>/usr/share/xsessions/</code> (for X11 sessions) * <code>/usr/share/wayland-sessions/</code> (for Wayland sessions) ==== Example: Defining an Openbox session ==== {{FileBox|title=/usr/share/xsessions/openbox.desktop | content = [Desktop Entry] Name=Openbox Comment=Log in using the Openbox window manager Exec=/usr/bin/openbox-session TryExec=/usr/bin/openbox-session Icon=openbox Type=Application }} 5b889406094078f9c7f6f468fb7e895b149c61e8 0 1178 5244 4923 2026-05-25T07:15:58Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki All of the following systems are widely supported and '''most''' others are going to be derived from these. == Ubuntu == + Has both an LTS release and a non-LTS release with upgrade periods of 2 years and 6 months respectively. + Non-LTS version is decently up-to-date with support for decently new hardware. + Simple to get started with: includes an intuitive installer and comes with GUI app stores. + Easy Nvidia drivers with hardware detection using the ubuntu-drivers tool. - Comes with Snap Store by default, which can be problematic for some software such as Steam. - LTS release comes with heavy tradeoff as it may just miss big updates or hardware support. - Non-LTS release is not guaranteed to be stable and may break on updates. == Arch Linux == + Rolling release, meaning there is no concept of a "version" and all packages are updated individually to their own latest stable versions. + Can be assembled from scratch, allowing the system to be exactly the way the user wants. This is supported by an exhaustive wiki detailing most of the Linux system components. + Contains the archinstall script, providing a TUI installer to avoid manual setup. + The largest official repositories out of the all distributions; also the Arch User Repository (AUR) which optionally can be used at their own risk. + Pre-built Nvidia kernel modules for official kernels. - Requires some extent of expected system maintenance, e.g. when package names are changed or split in official repositories. - Hard to maintain because there's no single configuration any user can be expected to have. - Does not have very good options for GUI package management. == Fedora Linux == + Releases a new version every 6 months for core components like the desktop, still has packages near as latest as a rolling release. + Decent installation process and supports GUI app stores by default. - Harder to setup as it relies on third-party repositories for non-free software like media codecs and Nvidia drivers. - Version upgrades are again not guaranteed to not break. - Mostly a testing ground for any new Linux capabilities, hence might choose to update to newer technologies first in the race. == openSUSE Tumbleweed == + Rolling release. + Decent installer and has its own utilities for GUI package management and system management. - Reliance on third-party repositories for codecs and drivers. == bootc-based systems (Silverblue, Bazzite etc) == + No system-level package management: the system is contained in the form of an image, which updates as a whole every new release. + Hence, easy rollbacks in case of broken updates. Also easier maintenance because there is more expectation on the state of the every system. + Can be switched between one another in a single command. + Different images have different goals; Bazzite provides a good setup and there is no involvement needed for drivers. - No easy way to change the system, hence some things can not be achieved without making your own image. This includes out-of-tree drivers, or any other packages that NEED to be on the system to work properly, such as Discord RPC, VPNs, password managers etc. 5097a205343fea3afd949f9d4be6cf858bcc26e0 0 1081 5245 4398 2026-05-25T07:16:08Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fcitx5.svg|frameless]] | caption = The Fcitx logo | title = Fcitx | releasestatus = Maintained | lastrelease = 5.1.12 (2025-01-23) | languages = [[C++]], [[C]] | developers = Fcitx Developers | website = https://fcitx-im.org/wiki/Fcitx_5 }} '''Fcitx 5''' (or usually '''fcitx5''') is a [[Qt]]-based [[input method framework]] (IMF). It is a successor to [[Fcitx]], and is consistently the second most popular IMF following [[IBus]] according to statistics from [[Arch Linux]].<ref>[https://pkgstats.archlinux.de/compare/packages#packages=fcitx,fcitx5,gcin,hime,ibus,nimf,scim,uim Compare Packages], Arch Linux (Accessed: 2026-01-15)</ref> Unlike IBus, Fcitx 5 comes with more advanced features, including addons and themes.<ref>[https://fcitx-im.org/wiki/Addon_Type Addon Type], Fcitx, 2016-02-02 (Accessed: 2026-01-15)</ref><ref>[https://fcitx-im.org/wiki/Theme_Customization Theme Customization], Fcitx, 2022-02-09 (Accessed: 2026-01-15)</ref> == Installation == Fcitx 5 has support for [[UNIX]]-based systems. <code>fcitx-contrib</code> provides support for [[macOS]] [https://github.com/fcitx-contrib/fcitx5-macos], [[iOS]] [https://github.com/fcitx-contrib/fcitx5-ios], [[HarmonyOS]] [https://github.com/fcitx-contrib/fcitx5-harmony], [[ChromeOS]] [https://github.com/fcitx-contrib/fcitx5-chrome], and [[Windows]] [https://github.com/fcitx-contrib/fcitx5-windows]. It can also be tested in an Internet browser [https://fcitx-contrib.github.io/online/index.html]. [[Android]] support is provided by [https://github.com/fcitx5-android/fcitx5-android <code>fcitx5-android</code>]. On [[operating system]]s with [[package manager]]s, usually the name of the package is <code>fcitx5</code>. Some distributions do not ship it with out-of-box support for GTK and Qt. [[KDE Plasma]] users should install the [[KCM]] module, which provides a dedicated page in system settings for configuring Fcitx5. Other users should install <code>fcitx5-configtool</code>. {| class="wikitable" style="text-align:center;" |+ Subpackage Names for Distributions ! Distribution !! GTK3 !! GTK4 !! Qt5 !! Qt6 !! KCM |- | [[Arch]]<ref>[https://wiki.archlinux.org/title/Fcitx5 Fcitx5], ArchWiki, 2026-01-13 (Accessed: 2026-01-15)</ref> || colspan=2 rowspan=2 | <code>fcitx5-gtk</code> || colspan=2 rowspan=2 | <code>fcitx5-qt</code> || rowspan=2 | <code>kcm-fcitx5</code> |- | [[Fedora]] |- | [[Debian]]<ref>[https://wiki.debian.org/I18n/Fcitx5#Install_Fcitx5_on_bullseye Fcitx5], Debian Wiki, 2025-08-10 (Accessed: 2026-01-15)</ref> || colspan=4 | <code>fcitx5-frontend-{gtk3,gtk4,qt5,qt6}</code> || <code>kde-config-fcitx5</code> |- |} == Usage == {{Guide Warning}} The official Fcitx 5 Wiki contains instructions and suggestions on ideal set ups.<ref>[https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#Support_in_Wayland_Compositor Using Fcitx 5 on Wayland], Fcitx, 2024-06-14 (Accessed: 2026-01-15)</ref> It mentions a new set up method for KDE Plasma, requires setting ''Fcitx 5 Wayland Launcher'' in ''System Settings'' → ''Input/Output Devices'' → ''Keyboard'' → ''Virtual Keyboard''. For other environments and for the old method for KDE Plasma, it is required to create an autostart setup with the following system-wide [[environment variable]]s: {{FileBox|title=/etc/environment|lang=sh|content= export INPUT_METHOD=fcitx export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx export XMODIFIERS=@im=fcitx }} Autostart can be enabled via the <code>fcitx5-autostart</code> package on Fedora (which also provides the required environment variables), or by copying the given autostart [[desktop entry]] into the autostart folder: <syntaxhighlight lang="bash"> mkdir -p ~/.config/autostart cp /usr/share/applications/org.fcitx.Fcitx5.desktop ~/.config/autostart </syntaxhighlight> == Input Method List == See [[Guides:Input method#List of IMs to IMEs]] == Troubleshooting == === Cannot Detect in Electron Applications === In some cases where [[Electron]]/[[Chromium]] is executed under [[Wayland]], Fcitx 5 would not be detected. Follow the instructions [https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#Chromium_/_Electron here] to fix the issue. On KDE Plasma, in the application menu, right click on the application and click edit, then add e.g. <code>--enable-features=UseOzonePlatform --enable-features=WebRTCPipeWireCapturer --ozone-platform=wayland --enable-wayland-ime --ozone-platform-hint=auto</code> as the command-line arguments. === Cannot Detect in MuseScore === MuseScore 4 does not support Fcitx 5 under the new Wayland setup on KDE Plasma.<ref>[https://musescore.org/en/node/371132 Japanese Input not working in Linux Mint 22, Musescore 4], dadasabi, 2024-11-02 (Accessed: 2026-01-15)</ref> Use the old method mentioned above with ''Fcitx 5'' set as the virtual keyboard. == See Also == * [https://wiki.archlinux.org/title/Fcitx5 Fcitx5 on ArchWiki] == References == 7a21c20cd7c05c63a69350e211c1804b07571cc6 0 1085 5246 4426 2026-05-25T07:16:18Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{stub}} {{Needs Citations}} {{DistributionInfobox | title = Fedora Atomic | image = [[File:Fedora logo.svg|Fedora_logo|frameless]] | releasestatus = Maintained | packagemanager = [[rpm-ostree]] | releasemodel = Stable | defaultdesktops = [[Budgie]], [[COSMIC]], [[GNOME]], [[KDE Plasma]], [[Sway]] | usagetype = Desktop | architectures = x86_64, Arm | website = [https://www.fedoraproject.org fedoraproject.org] }} A atomic variant of the Fedora Project designed with Security and Reliability in mind for Desktops, Servers and Containers == Fedora Atomic Variants == {| class="wikitable" |- ! Variant !! Description |- |[[Fedora Budgie Atomic]] | An atomic desktop operating system featuring the popular [[Budgie]] desktop environment |- |[[Fedora CoreOS]] | An automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. |- |[[Fedora COSMIC Atomic]] | An atomic desktop operating system featuring the [[COSMIC]] desktop from [[System76]] |- |[[Fedora Kinoite]] |An atomic desktop operating system featuring the modern and modular [[KDE Plasma]] Desktop |- |[[Fedora Silverblue]] |An atomic desktop operating system featuring the modern and elegant [[GNOME]] Desktop |- |[[Fedora Sway Atomic]] |An atomic desktop operating system featuring the keyboard-driven Sway window manager. |} 38f9332e63a73b2ab26094d90b14888f6bebe40f 0 853 5247 4734 2026-05-25T07:16:28Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software licenses]] {{Work_In_Progress}} The '''GNU General Public License''' (short '''GNU GPL''' or '''GPL''') is a collection of copyleft licenses published by the Free Software Foundation (FSF) and written by Richard Stallman<ref>https://archive.ph/20120907170559/http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html{{Dead Link|2025-08-14|429}}</ref>. This License is also part of the [[GNU]] project. === Copyleft === A copyleft license requires that any modifications or extensions to a program licensed under a copyleft license must also be licensed under the same (or a compatible) license. === "or-later" clause === All GNU GPL licenses may contain an optional clause, an “or-later” clause (sometimes referred to as a “lifeboat clause”). This clause allows all later versions to be used. Programs without this clause are referred to as “only.” For example * GNU GPLv2-or-later can also be licensed under GNU GPLv3-or-later without any problem * GNU GPLv2-only can only be licensed under the GNU GPLv2 The same applies to the GNU AGPL and LGPL licenses. The FSF recommends using the “or-later” clause, as it is compatible with future versions of the GNU GPL, since GNU GPLv2 and v3 are not compatible and therefore a program licensed only under GNU GPLv2 cannot be mixed with a GNU GPLv3 program. == Licenses == There are three versions of the GNU GPL, with version 3 being the most recent version for all of them. # GNU General Public License (GPL) – The standard strong copyleft license used for most programs. # GNU Lesser General Public License (LGPL) – A weak copyleft license mainly used for libraries. # GNU Affero General Public License (AGPL) – Similar to the GPL, but also covers use over a network. === GNU General Public License (GPL) === This license is used for regular programs such as the Linux kernel, which uses GNU GPLv2 only. The latest version is the GNU General Public License Version 3 (GNU GPLv3), which was released in June 2007<ref>[https://www.gnu.org/licenses/gpl-3.0.en.html#license-text The GNU General Public License v3.0], Free Software Foundation, 2007-08-14 (Accessed: 2025-08-14)</ref> and can be found [https://www.gnu.org/licenses/gpl-3.0.en.html#license-text here]. If part of a program (e.g., a library) uses this license, the entire program must be licensed under the GNU GPL. If this is not desired, the GNU LGPL or another license should be used. === GNU Lesser General Public License (LGPL) === The GNU LGPL (formerly known as the Library General Public License) was created at the same time as the GNU GPLv2 and was also published in June 2007, but the first version was called GNU LGPLv2 to match the GNU GPLv2. This license was created because the GNU GPL was too restrictive, especially for libraries. If a program uses a library licensed under the GNU LGPL, only the modification of that library must be published. This allows a library to be used in [[proprietary software]]. The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/lgpl-3.0.html here]. === GNU Affero General Public License (AGPL) === The GNU AGPL was created to close a loophole when modified software licensed under the GNU GPL was run on a server the source code don't need to be published because of that the AGPL was created to fix this loophole The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/agpl-3.0.html#license-text here] <references /> 5597a7250b6be0dcb93a84574bc9e045d044b293 0 1190 5249 4989 2026-05-25T07:16:48Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] }} [[Category:Software]] [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many [[Linux Distributions|Linux distributions]] and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or messages to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a sender's public key, the legitimacy of a message. GnuPG is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. Due to GnuPG supporting many old and deprecated algorithms and many UX mistakes, many users advise moving towards the more modern [[Age]] for encryption<ref>{{Cite|url=https://sumguy.com/age-vs-gpg-modern-encryption/|title=age vs GPG: Modern File Encryption That Doesn't Make You Cry|author=SumGuy|year=May 26, 2026|accessdate=2026-05-23}}</ref>. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] is needed. <references /> aeb95ee03e9c685e960db14e839770eb11f125dc 0 1218 5250 5090 2026-05-25T07:16:58Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |title=gocryptfs |releasestatus=Maintained |lastrelease=2.6.1, 2025-08-10 |firstrelease=1.0, 2016-07-17 |languages=[[Go]] |developers=[https://github.com/rfjakob rfjakob] |website=[https://nuetzlich.net/gocryptfs nuetzlich.net/gocryptfs] }} '''gocryptfs''' is an encrypted overlay filesystem<ref>{{Cite|url=https://github.com/rfjakob/gocryptfs|title=gocryptfs github|author=gocryptfs contributors|year=2026|accessdate=2026-05-24}}</ref> made in [[Go]] on top of [[Linux kernel|FUSE]], more specifically, [https://github.com/hanwen/go-fuse go-fuse]. It is used in [[KDE]] Vaults for encryption. 4f2a5c1bfff2515f930d402e85b70ef2dd802764 0 1187 5251 5216 2026-05-25T07:17:08Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Game Engines]] {{Stub}} {{SoftwareInfobox | image = [[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]] | caption = | title = Godot | releasestatus = Maintained | lastrelease = 4.6.3-stable, 2026-05-20 | firstrelease = 1.0, 2014-12-15 | languages = [[C++]] | developers = Juan Linietsky, Ariel Manzur, and Contributors | website = [https://github.com/godotengine/godot github.com/godotengine/godot], [https://godotengine.org godotengine.org] }} Godot is a general-purpose FOSS game engine. It uses a node- and scene-based editor and supports C++, C#, and its original scripting language, [[GDScript]], plus other languages through community tools.<ref>[https://godotengine.org/features/#script Features], Godot Engine, 2026-05-20 (Accessed: 2026-05-25)</ref> The name comes from the classic play ''[[wikipedia:Waiting_for_Godot|Waiting for Godot]]'' and is pronounced as therein. This results in the pronunciation varying between languages, which the project officially describes as "beautiful".<ref>[https://godotengine.org/press/ Press Kit], Godot Engine, 2026-05-01 (Accessed: 2026-05-25)</ref> c74d8ee1e9c88e85011987aa8cae9773c8628ebb 0 1032 5252 4666 2026-05-25T07:17:18Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}}{{Needs Citations}} {{DistributionInfobox | architectures = ARM64 | caption = The GrapheneOS logo | defaultdesktops = Android User Interface | image = [[File:GrapheneOS-logo-black.png|GrapheneOS-logo-black]] | packagemanager = Android Package Manager (not acessible) | releasemodel = Fixed Releases | releasestatus = Currently Maintained | title = GrapheneOS | usagetype = Mobile | website = [https://grapheneos.org grapheneos.org] }} '''GrapheneOS''' (previously CopperheadOS<ref>[https://grapheneos.org/history/copperheados CopperheadOS | History], GrapheneOS, 2025-09-24 (Accessed: 2025-10-12)</ref>) is an [[Android]]-based [[OS|operating system]] focusing on privacy and security.<ref>[https://grapheneos.org/#about GrapheneOS: the private and secure mobile OS], GrapheneOS, 2025-09-24 (Accessed: 2025-10-12)</ref> It usually receives the fastest updates compared to other customized Android-based systems. == History == GrapheneOS was founded by Daniel Macay in late 2014, starting as a solo project incorporating his previous open source privacy/security work. The project initially created a port of [[OpenBSD]] [[malloc]] to Android's Bionic [[libc]] and a port of the PaX [[kernel]] [[patch]]es to the kernel of GrapheneOS's supported devices. It quickly expanded to a lot of privacy and security improvements, particularly low-level [[hardening]] on the [[compiler]] toolchain and Bionic. Code began landing on AOSP and upstream projects.<ref>[https://grapheneos.org/history/ History], GrapheneOS, 2025-09-24 (Accessed: 2025-10-12)</ref> == Features == A complete list of features can be found on the [https://grapheneos.org/features GrapheneOS website]. === Sandboxed Google Play === Unlike stock [[Android]], GrapheneOS does not ship with [[wikipedia:Google_Play_Services|Google Play Services]] preinstalled. Instead, GrapheneOS provides a compatibility layer which enables Google Play Services to run in the standard app sandbox. This means permissions such as reading contacts, accessing GPS location, or being able to run in the background can be changed in the phone's settings like for any other app, instead of Google Play Services being granted irrevocable special privileges. <ref name=":0">{{Cite|url=https://grapheneos.org/features|title=GrapheneOS Feature Overview|author=GrapheneOS Project|accessdate=2026-05-22}}</ref> === PIN scrambling === GrapheneOS adds a setting to enable shuffling of the numbers on the PIN entry screen.<ref name=":0" /> This makes it harder to figure out a device's pin through [[wikipedia:Shoulder_surfing_(computer_security)|shoulder surfing]]. === References === <references /> 03b901852d0f80f9ebd7192cc98c4d516c394f14 3000 1136 5253 4859 2026-05-25T07:18:02Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} '''Welcome to the penguin side!''' Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable, if not more comfortable as the operating system you use today in no time. == Why switch to Linux? == People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. == Choices == Linux is all about choices. Before you start, you need to pick what your distribution of Linux looks like and what it runs under the hood. The Graphical User Interface (GUI) you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. == Picking a Linux distribution == <!--Discuss on talk page before modifying this section due to potential for bias.--> There are many flavors of Linux. Each distribution has its pros and cons, but in the modern era of Linux, many distributions are quite easy to install, use, and update. If you don't like the Linux distribution you chose, you can switch to another one at any time as long as you know how to back up your data. == Picking a Graphical User Interface (GUI) == When you install a distribution of Linux, the installer that the distribution uses asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on a touchpad gestures consider [[GNOME]]. d0c36815501117ef9d397a5c307ec914e61b8dd7 0 826 5254 4722 2026-05-25T07:18:05Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Helix editor.svg|thumb|The logo for Helix]] |caption=Helix Editor |title=Helix |releasestatus=Maintained |lastrelease=25.07.1, Jul 18, 2025 |firstrelease=0.0.2, May 12, 2021 |languages=[[Rust]] |developers=[https://mxxn.io/ Blaž Hrastnik] |website=[https://helix-editor.com/ helix-editor.com] }} [[Category:Software]] [[File:Helix Screenshot.png|alt=screenshot of helix|thumb|Helix in a rust codebase]] [[Helix]] is a modal text editor written in [[Rust]] and inspired by [[Neovim]]{{Citation needed}} and [[Kakoune]]<ref name=":0">[https://helix-editor.com/ Helix website] (accessed 2026-05-22)</ref>. It implements changes to the traditional [[Vim]] workflow similar to Kakoune's, like selection-based editing and multi-cursor support. Its main selling points include its vim-like modal editing, support for multiple selections, built-in language server implementations and smart syntax highlighting. Helix bundles and enables many features out of the box and does not yet have a plugin system, although that is currently being worked on<ref name=":0" />. It does have adding custom language support. Therefore, it can be considered easier to set up but less customizable than Vim and similar editors. Due to its lack of plugin support, many users decide to fork Helix in order to add functionality that isn't included out of the box{{Citation needed}}. Helix is configured through [[TOML]]. ==Usage tips== While many of the same keybindings and concepts as [[Vi]] and [[Vim]] apply to Helix, many of the keybindings and concepts are different. The recommended way to learn Helix is by using the <code>:tutor</code> command whilst inside Helix, to do this, run <code>Helix</code> and type <code>:tutor</code>, then hit enter and follow the instructions. On some [[Linux Distributions|distros]], the executable is named <code>helix</code> (like on ArchLinux<ref>{{Cite|url=https://archlinux.org/packages/extra/x86_64/helix/|title="Helix" package on ArchLinux|author=Orhun Parmaksız|year=2025-07-18|accessdate=2026-05-22}}</ref>), while on others, it is named <code>hx</code> (like on Alpine Linux<ref>{{Cite|url=https://pkgs.alpinelinux.org/contents?name=helix&repo=community&branch=edge&arch=x86_64|title="Helix" package on the Alpine Linux community repository|author=Jakub Jirutka|year=2026-05-04|accessdate=2026-05-22}}</ref>). This may cause issues if you develop muscle memory for the names of one of these commands, to get around this, you can create a symlink under your chosen name. <references /> 4aa50792f0fdfbd11fbaddd7aa6f7eda57f329ec 0 1200 5255 5011 2026-05-25T07:18:15Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Kakoune logo.svg|thumb|The logo for Kakoune]] |caption=Kakoune |title=Kakoune |releasestatus=Maintained |lastrelease=2026.05.21, May 20, 2026 |firstrelease=Unknown, Sep 2, 2011 |languages=[[C++]], [[Kakoune Script]] |developers=[https://github.com/mawww Maxime Coste] |website=[https://kakoune.org/ kakoune.org] }} [[Category:Software]] [[File:Kakoune-linux-init-main.c.png|thumb|Kakoune open to the Linux kernel source code (<code>init/main.c</code>)]] '''Kakoune''' is a modal editor, it is designed to provide an efficient, predictable, and scriptable code editing environment<ref>{{Cite|url=https://kakoune.org/why-kakoune/why-kakoune.html|title=Why Kakoune|author=Maxime Coste|year=2020-01-03|accessdate=2026-05-23}}</ref>. It is a strong divergence from [[Vi]] like editors and inspired [[Helix]]. 120f66a951fc9045d2d0269f0ca1372301d61351 0 1075 5256 4377 2026-05-25T07:18:32Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | image=[[File:LXDE desktop full.png|thumb]] | caption = The default LXDE desktop | title=LXDE | releasestatus=Maintained | lastrelease=0.10.1, 25 February 2021 | firstrelease=2006; 20 years ago | languages=[[C]] | developers=PCMan (formerly), The LXDE Team (currently) | website=https://www.lxde.org/ }} '''LXDE,''' which is an abbreviation of '''Lightweight X11 Desktop Environment''' is a free to use desktop environment aiming to be as low on resource usage as possible. LXDE is aimed at Unix and other POSIX-compliant platforms such as BSD and Linux, and is made using GTK2 and the C programming language. It uses a rolling-release model for its individual components (or groups of components that depend on each other). == History == The project was started in 2006 by Hong Jen Yee (online known as PCMan) when he released PCManFM, which is the first module of LXDE Currently the original LXDE only receives maintenance updates, because its creator was dissatisfied with GTK3 and decided to port the entire software suite to Qt (announced in 2013) and later that year the LXDE and LXQt projects got merged Since the beginning of 2020 a GTK3 port is developed by the Arch Linux community, and several important components of LXDE have already been ported == Software Components== {| class="wikitable" ! Components ! Descriptions |- | PCMan File Manager | File manager and Desktop metaphor provider |- | LXInput | Mouse and keyboard configuration tool |- | LXLauncher | Application Launcher |- | LXPanel | Desktop panel |- | LXSession | X session manager |- | LXAppearance | GTK theme switcher |- | GPicView | Image viewer |- | LXMusic | Audio player and fronted for XMMS2 | |- | LXTerminal | Terminal emulator |- | LXTask | Task manager |- | LXRandR | A GUI for X Resize and Rotate (xrandr) | |- | LXDM | X display manager |- | [[Openbox]] | Window manager used by LXDE |- | [[ObConf]] | A GUI tool for managing Openbox's configuration |- |} 3c4a9543a32842aa6ddcdf27fbca12c9fd8876bc 0 884 5257 4373 2026-05-25T07:18:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.3.0, Nov 5, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>[https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFM file manager is ported to Qt? – LXDE Blog], PCMan, 2013 (Accessed: 2025-10-26)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>[https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ “The future of Razor and LXDE-Qt” – LXDE Blog], PCMan, 2013 (Accessed: 2025-10-26)</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>[https://lubuntu.me/ Lubuntu – The official Lubuntu home], Lubuntu, 2025 (Accessed: 2025-10-26)</ref> * [[Fedora]] LXQt spin<ref>[https://fedoraproject.org/spins/lxqt Fedora LXQt Spin | The Fedora Project], Fedora, 2025 (Accessed: 2025-10-26)</ref> * [[CachyOS]]: available in installer<ref>[https://wiki.cachyos.org/installation/desktop_environments/ Desktop Environments | CachyOS], CachyOS, 2025 (Accessed: 2025-10-26)</ref> * [[SparkyLinux]]<ref>[https://wiki.sparkylinux.org/doku.php/about about Sparky Wiki], Sparky Linux, 2025 (Accessed: 2025-10-26)</ref> * [[Debian]]: available in installer<ref>[https://wiki.debian.org/LXQt LXQt - Debian Wiki], Debian Wiki, 2025 (Accessed: 2025-10-26)</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>[https://packages.debian.org/stable/lxqt-core Debian -- Details of package lxqt-core in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>[https://packages.debian.org/trixie/lxqt Debian -- Details of package lxqt in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>[https://packages.debian.org/stable/task-lxqt-desktop Debian -- Details of package task-lxqt-desktop in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>[https://archlinux.org/groups/x86_64/lxqt/ Arch Linux - lxqt (x86_64) - Group Details], Arch Linux, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>[https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template void-packages/srcpkgs/lxqt/template at master · void-linux/void-packages · GitHub], Github, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], LXQt wiki, 2025 (Accessed: 2025-10-26)</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>[https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions Launching LXQt sessions · lxqt/lxqt Wiki · GitHub], LXQt wiki, 2025 (Accessed:2025-10-26)</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight lang="text">exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == 12c56280ec61be3b6691ac1d3d2853f674cab141 0 1236 5258 2026-05-25T07:18:41Z Hyperreal 388 Init Age/Examples wikitext text/x-wiki == Introduction == An '''identity''' generated with <code>age-keygen</code> is typically a plaintext file with three lines. The first line contains a timestamp of when the identity was created. The second line contains the identity's public key. The third line contains the identity's secret key. # created: 2026-05-25T01:46:24-05:00 # public key: age1yjd47dpqulfqs8d35ftazzxwf4dfx5qwp2fs5qn8mznz29rpdyxsz804s5 AGE-SECRET-KEY-1057P2C323UDZJZ49CT3LTWTP0U8DZ8SK7N3DNVKGH04R8AUAY29ST26XK5 A '''recipient''' is in the form of an <code>age</code> public key; for example, <code>age1yjd47dpqulfqs8d35ftazzxwf4dfx5qwp2fs5qn8mznz29rpdyxsz804s5</code>. For further information, consult the manual pages for <code>age</code>, <code>age-inspect</code>, and <code>age-keygen</code>. == Generate a key pair, save it to an unencrypted file, and print the public key to stdout == age-keygen --output identity.txt Public key: age1w8m0z4yq4ev97yw99hrlmq03p5cdwmtrg4lptpvardcr2d7tuv5sh7fpm3 == Generate a post-quantum key pair, save it to an unencrypted file, and print the public key to stdout == age-keygen -pq --output post-quantum-identity.txt Public key: age1pq1k038we43y2guj0tvyah4sdeyt4txgz83de39q79499mxyvsxs2smg2k9kphange32z77vct6x44vvfw4w6hf2jwhu7fuyuy4ulgxgu02x59ux9da4jmdqdunrvapvpw5eqx09ze57484tuvms75rxau59mxafyqterzpew4tkvz5jtvr2qu04dvrfy32aa9ut232er05nwqgv5wdc2lrxffe24fmpeqz2lmgscqpdj3leq3xxy2ullm2hnm6yslfcuvww9vaaq9jydf8hfztwszm2fwmgja0e23jpd8cpku9cwgtnv5tp6m50d25wyd4njj4prpred84dfgxk6znzx5q3pymdjvpt9a7lkd85jqrxplrdmu49pq8jcxk6p9gzg4ec0zzpvwhky82ezttn6s9zumz3e59vax2pdwjzwag6645sfvhydduynkwcqx27cd70wtvuqqm3m6jjvpeytd4mvr29x2czq54r8sy3ay6s5x0hfp0m9cv3c58328fhffzntl6axe7ycj40sy2r4xmcx2v33qpjaz7q9ak6zfh525qh356qpxzcmze959yj8vqzpn39sel8rdzjwrwa3tvdd2vgymptq9kslk6yy7u06e4405gnx93k68snr3zqvx6mtzemzeys0c5xkz8vjm6jftvyhrtqmmngz0x4yh3qjp4vv0dcdtr7sdjzuqeg7ueswhqpgtv8vspv8fxvv9ucsu33vejz48kcn9pqz2k0z62wn84fzh9r3mucdepu5y8jpl627weylhrq5xrjqcq79r8ysymxcjpw6r3c4qzqpaam3euyqjkrw30frcmucvdnkpf5c25hevvp70tjgph8ycqyeaycp9xg2592jfjghu3fgkn7ywt3n3t73j603e7n2k45fckvu4299jx4vxvyl7gkq3hhftdexkwdlrn97gk9x095pcrw6z5jjpg0gxra6sm8hhezvn8nslmrzk9mljmvd2x989uy8gmmva3d39trv4hz8ltfgzmfvavxsv7gmysw33m6rlfn4h9y5l9q0zpevdqsgfsekcrrnrcqgh66qxqsxd5ddupntns0zkg8vhujkc3ryy5fmpc38eq9099pfl5zykxr33ghcdn0s2edeny4xr3u7mam2ww0gf9ft0cre6dk6d8zcd4zy9xe9ugl99zh2g6xua8d2xkwyk9fj6qzzksk2p2g9kses8axwfkdtacmtnyvc74006f5wphhycatqgzrv2vttmsexym4q8w3y3ml9zkzcygg22fkw9xnw7tzvgf0yrg93hvhfgggqdhwkcffc9lqkt4u6q3nr0anw6q8sp5lym4u55hct8k3qeqxfqp4tqthx4rnam3exfye23srn3sj368t9p9edczs9grynmun0t939nghpkd08rhgtf9tqntvsemyuytj24dvrvr29wfewxzxhpx3w4cgftkps6gj82hge4a5tx87jgfr3ak82eqgycphac8vg4uxfu052n0wj9zx333gxg0nnlpvyr3pw30feze76luvn2vqeve7sl52fc99pc6zh3cnv48fqjh3jc6d23yvx9404cmj63ssqz9za76r4rd2924fjscvvgf2jpwl92h6f53g3ggpyrhsue6snq039pe29pn2r2hndsvddazylg3m9lhe6cpeuf5vxspdv3yfqhhv6xh86e6ussr66f2smgxcgk3cg7rd42qchfzr98tqccvxy5vy3vlhjkyvgugreg8ykf8qnepsyrggca4h0cmv7tpn5ym547az639decchffuy0d90gxa23d5h22jfka6vgmzdvymxax60trfnfdwshu5a6j6vt80955c8p3mtlcegt796nhu7j3rhqdqgfh42th22l4ayd6tzatggqjxjlw0d2chscvjc0u7dwzgwmnzf2c6x3g9zlnn9ymzd4fj == Convert an identity to a recipient and print the public key to stdout == age-keygen -y identity.txt age1w8m0z4yq4ev97yw99hrlmq03p5cdwmtrg4lptpvardcr2d7tuv5sh7fpm3 == Generate an encrypted file that can be decrypted with a passphrase == When using the <code>-p|--passphrase</code> flag, you will be prompted to input a passphrase. age [-p|--passphrase] [-o|--output] path/to/encrypted_file.age path/to/unencrypted_file == Encrypt a file with one or more public keys entered as literals == Repeat the <code>--recipient</code> flag to specify multiple recipients. age --recipient age1w8m0z4yq4ev97yw99hrlmq03p5cdwmtrg4lptpvardcr2d7tuv5sh7fpm3 --output encrypted_file.age unencrypted_file.txt == Encrypt a file to one or more recipients with their public keys specified in a file == The recipients public keys must be specified in the file one per line. age --recipients-file recipients.txt --output encrypted_file.age unencrypted_file.txt == Decrypt a file with a passphrase == You will be prompted to enter the passphrase for the encrypted file. age [-d|--decrypt] [-o|--output] decrypted_file.txt encrypted_file.age == Decrypt a file with a private key file == age --decrypt --identity identity.txt --output decrypted_file.txt encrypted_file.age 155a32cde1d47818fbb4e2b9ae277ef07a33c557 5264 5258 2026-05-25T07:19:34Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki An '''identity''' generated with <code>age-keygen</code> is typically a plaintext file with three lines. The first line contains a timestamp of when the identity was created. The second line contains the identity's public key. The third line contains the identity's secret key. # created: 2026-05-25T01:46:24-05:00 # public key: age1yjd47dpqulfqs8d35ftazzxwf4dfx5qwp2fs5qn8mznz29rpdyxsz804s5 AGE-SECRET-KEY-1057P2C323UDZJZ49CT3LTWTP0U8DZ8SK7N3DNVKGH04R8AUAY29ST26XK5 A '''recipient''' is in the form of an <code>age</code> public key; for example, <code>age1yjd47dpqulfqs8d35ftazzxwf4dfx5qwp2fs5qn8mznz29rpdyxsz804s5</code>. For further information, consult the manual pages for <code>age</code>, <code>age-inspect</code>, and <code>age-keygen</code>. == Generate a key pair, save it to an unencrypted file, and print the public key to stdout == age-keygen --output identity.txt Public key: age1w8m0z4yq4ev97yw99hrlmq03p5cdwmtrg4lptpvardcr2d7tuv5sh7fpm3 == Generate a post-quantum key pair, save it to an unencrypted file, and print the public key to stdout == age-keygen -pq --output post-quantum-identity.txt Public key: age1pq1k038we43y2guj0tvyah4sdeyt4txgz83de39q79499mxyvsxs2smg2k9kphange32z77vct6x44vvfw4w6hf2jwhu7fuyuy4ulgxgu02x59ux9da4jmdqdunrvapvpw5eqx09ze57484tuvms75rxau59mxafyqterzpew4tkvz5jtvr2qu04dvrfy32aa9ut232er05nwqgv5wdc2lrxffe24fmpeqz2lmgscqpdj3leq3xxy2ullm2hnm6yslfcuvww9vaaq9jydf8hfztwszm2fwmgja0e23jpd8cpku9cwgtnv5tp6m50d25wyd4njj4prpred84dfgxk6znzx5q3pymdjvpt9a7lkd85jqrxplrdmu49pq8jcxk6p9gzg4ec0zzpvwhky82ezttn6s9zumz3e59vax2pdwjzwag6645sfvhydduynkwcqx27cd70wtvuqqm3m6jjvpeytd4mvr29x2czq54r8sy3ay6s5x0hfp0m9cv3c58328fhffzntl6axe7ycj40sy2r4xmcx2v33qpjaz7q9ak6zfh525qh356qpxzcmze959yj8vqzpn39sel8rdzjwrwa3tvdd2vgymptq9kslk6yy7u06e4405gnx93k68snr3zqvx6mtzemzeys0c5xkz8vjm6jftvyhrtqmmngz0x4yh3qjp4vv0dcdtr7sdjzuqeg7ueswhqpgtv8vspv8fxvv9ucsu33vejz48kcn9pqz2k0z62wn84fzh9r3mucdepu5y8jpl627weylhrq5xrjqcq79r8ysymxcjpw6r3c4qzqpaam3euyqjkrw30frcmucvdnkpf5c25hevvp70tjgph8ycqyeaycp9xg2592jfjghu3fgkn7ywt3n3t73j603e7n2k45fckvu4299jx4vxvyl7gkq3hhftdexkwdlrn97gk9x095pcrw6z5jjpg0gxra6sm8hhezvn8nslmrzk9mljmvd2x989uy8gmmva3d39trv4hz8ltfgzmfvavxsv7gmysw33m6rlfn4h9y5l9q0zpevdqsgfsekcrrnrcqgh66qxqsxd5ddupntns0zkg8vhujkc3ryy5fmpc38eq9099pfl5zykxr33ghcdn0s2edeny4xr3u7mam2ww0gf9ft0cre6dk6d8zcd4zy9xe9ugl99zh2g6xua8d2xkwyk9fj6qzzksk2p2g9kses8axwfkdtacmtnyvc74006f5wphhycatqgzrv2vttmsexym4q8w3y3ml9zkzcygg22fkw9xnw7tzvgf0yrg93hvhfgggqdhwkcffc9lqkt4u6q3nr0anw6q8sp5lym4u55hct8k3qeqxfqp4tqthx4rnam3exfye23srn3sj368t9p9edczs9grynmun0t939nghpkd08rhgtf9tqntvsemyuytj24dvrvr29wfewxzxhpx3w4cgftkps6gj82hge4a5tx87jgfr3ak82eqgycphac8vg4uxfu052n0wj9zx333gxg0nnlpvyr3pw30feze76luvn2vqeve7sl52fc99pc6zh3cnv48fqjh3jc6d23yvx9404cmj63ssqz9za76r4rd2924fjscvvgf2jpwl92h6f53g3ggpyrhsue6snq039pe29pn2r2hndsvddazylg3m9lhe6cpeuf5vxspdv3yfqhhv6xh86e6ussr66f2smgxcgk3cg7rd42qchfzr98tqccvxy5vy3vlhjkyvgugreg8ykf8qnepsyrggca4h0cmv7tpn5ym547az639decchffuy0d90gxa23d5h22jfka6vgmzdvymxax60trfnfdwshu5a6j6vt80955c8p3mtlcegt796nhu7j3rhqdqgfh42th22l4ayd6tzatggqjxjlw0d2chscvjc0u7dwzgwmnzf2c6x3g9zlnn9ymzd4fj == Convert an identity to a recipient and print the public key to stdout == age-keygen -y identity.txt age1w8m0z4yq4ev97yw99hrlmq03p5cdwmtrg4lptpvardcr2d7tuv5sh7fpm3 == Generate an encrypted file that can be decrypted with a passphrase == When using the <code>-p|--passphrase</code> flag, you will be prompted to input a passphrase. age [-p|--passphrase] [-o|--output] path/to/encrypted_file.age path/to/unencrypted_file == Encrypt a file with one or more public keys entered as literals == Repeat the <code>--recipient</code> flag to specify multiple recipients. age --recipient age1w8m0z4yq4ev97yw99hrlmq03p5cdwmtrg4lptpvardcr2d7tuv5sh7fpm3 --output encrypted_file.age unencrypted_file.txt == Encrypt a file to one or more recipients with their public keys specified in a file == The recipients public keys must be specified in the file one per line. age --recipients-file recipients.txt --output encrypted_file.age unencrypted_file.txt == Decrypt a file with a passphrase == You will be prompted to enter the passphrase for the encrypted file. age [-d|--decrypt] [-o|--output] decrypted_file.txt encrypted_file.age == Decrypt a file with a private key file == age --decrypt --identity identity.txt --output decrypted_file.txt encrypted_file.age 1458653028ab0ea5bb541f1fecf565e7cb137e58 0 1125 5259 4680 2026-05-25T07:18:45Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software licenses]] The MIT License is a permissive software license that puts very few restrictions on software reuse and provides no warranties for users using the software. == Text == <syntaxhighlight lang="text"> Copyright (c) <year> <copyright holders> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. </syntaxhighlight> 54cb0322831ea92ff607d5d60edd97137e2813a7 0 1091 5260 5041 2026-05-25T07:18:55Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox |caption=MangoWM logo |developers=MangoWM developers |firstrelease=0.1.1, 2025-02-17 |languages=[[C]] |lastrelease=V0.13.1, 2026-05-18 |title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io] |releasestatus=Maintained |image=[[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formally known as MangoWC) is a [[Wayland]] compositor based on [[dwl]] that keeps its lightweight, suckless-style design while adding more practical features.I think it looks alright. While staying minimal and fast to build, MangoWM improves on usability with better layouts, multi-monitor supports, and broader wayland compatibility. == Highlighted Features: == * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. === Additional Features: === * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation: == ==== AerynOS: ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== Arch: ==== Using yay: <syntaxhighlight lang="bash"> yay -S mangowm </syntaxhighlight> or for the latest git version: <syntaxhighlight lang="bash"> yay -S mango-git </syntaxhighlight> Using paru: <syntaxhighlight lang="bash"> paru -S mangowm </syntaxhighlight> or for the latest git version: <syntaxhighlight lang="bash"> paru -S mango-git </syntaxhighlight> ==== Fedora: ==== First we need to add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then, install it with dnf: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== Gentoo: ==== Firstly we add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Followed by unmasking of these packages in your package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== Guix System: ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== NixOS: ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref>. ==== PikaOS: ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> == Building from source: == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies: ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building wlroots from source: ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source: ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> cdecbfeeb97b843366509d9913ca99ed4f0f6a94 0 1193 5261 4988 2026-05-25T07:19:05Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox |title=Minisign |releasestatus=Maintained |lastrelease=0.12.2, May 2, 2026 |firstrelease=0.3, Jun 11, 2015 |languages=[[C]], [[Zig]] |developers=[https://github.com/jedisct1 Frank Denis] |website=[https://jedisct1.github.io/minisign/ jedisct1.github.io/minisign] }} '''Minisign''' is designed to be a simple tool to sign files and verify signatures. Although originally made in [[C]], the [[Zig]] version ([https://github.com/jedisct1/zig-minisign zig-minisign], sometimes refereed to as <code>minizign</code>) is now the preferred version. Minisign, along with [[Age]], is often used by people wanting to replace [[Gnupg|GnuPG]] who may want to do so for various reasons. [https://man.openbsd.org/signify Signify] is preferred over Minisign on [[OpenBSD]] systems due to its integration with its ecosystem. 48631231bb0ee0279559c6808d15578498d6ed4a 0 394 5262 4809 2026-05-25T07:19:15Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel == BSD Based == {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} == Darwin Based == {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} == Solaris Based == {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} == Other UNIX-like == {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} == L4 based == {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} == Other Operating Systems == {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- |} bc8e0131c7488b84cd731ab0b131e3a3e7d8d248 0 1123 5263 4672 2026-05-25T07:19:25Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [https://navidrome.org Navidrome] is a locally-hosted music streaming server that allows users to upload one's personal music files onto it in order to create a personal music library. This music library can be streamed through various [https://foss.wiki/Category:Navidrome_Clients clients] to play one's locally-hosted music on other devices via a link pointing to the host server. 14892773285c67da657c54c77aa6fc8b03453429 0 1143 5265 4979 2026-05-25T07:19:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:Neovim-mark.svg|thumb]] |caption=NeoVim |title=NeoVim |releasestatus=Maintained |lastrelease=0.12.2, Apr 22, 2026 |firstrelease=0.15, Aug 23, 2016 |languages=[[C]], [[Lua]], [[Vim Script]] |developers=Thiago de Arruda |website=[https://neovim.io/ neovim.io] }} [[Category:Software]] [[File:Nevom-Splash.png|thumb|The Neovim 0.12.2 splash screen.]] '''Neovim''' (also known as '''nvim''') is a configurable terminal text editor for Linux, Windows, and macOS. It is configured in [[Lua]]. Neovim is based on [[Vim]]<ref>{{Cite|url=https://github.com/neovim/neovim/commit/9f13983de280c53971a8997ead0d6e9d4e3d3e42|title=Commit 9f13983, "vim-patch:7.4.2185"|author=lonerover|year=2017-03-11|accessdate=2026-05-23}}</ref>. Neovim is fully compatible with Vim's editing modal and [[Vim Script]]<ref>[https://neovim.io/ Neovim website] (accessed 2026-05-22)</ref>, and part of Neovim is written in [[Vim Script]]<ref>{{Cite|url=https://github.com/neovim/neovim|title=Neovim GIthub|author=[https://github.com/orgs/neovim/people Neovim Contributors]|year=2026-05-23|accessdate=2026-05-23}}</ref>. Like [[Vim]], Neovim can also be considered [[wikipedia:Careware|Charityware]] due to encouraging users to donate to [https://www.kuwasha.net/ Kuwasha]. <references /> 44efa7bf9691b904d49adc749b19257aeaa45519 0 810 5266 4399 2026-05-25T07:19:45Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki '''OpenRC''' is a dependency-based [[Init System|init system]] made in [[C]] and [[Shell]] for Unix-like [[Operating System|Operating Systems]]. Created by [[NetBSD]] developer and ex-maintainer of the [[Gentoo]] Project.<ref>Wikipedia, The Free Encyclopedia: https://en.wikipedia.org/wiki/OpenRC (Accessed Aug 5th, 2025)</ref> Due to OpenRC being made from C and POSIX-Compliant Shell, it is portable between [[Linux]], [[FreeBSD]], and NetBSD. It can optionally be used as an init system or as a [[Process Supervisor|process supervisor]]. = Overview = OpenRC is a default init system and/or process supervisor on many [[Linux Distributions]] due to its lightweight and compatibility properties. The init system is made of several modular components allowing full-scale customization in terms of what the process actual does for being an init system or as a daemon supervisor. = Configuration = ==Files== OpenRC uses <code>/etc/rc.conf</code> for its global configuration Individual initscripts store their configuration in <code>/etc/conf.d</code> ==Logging== By default OpenRC doesn't create logs, however logging can be enabled to log output during the boot process {{FileBox | title = /etc/rc.conf | content = rc_logger="YES" rc_log_path="/var/log/rc.log" #Can be used to set a custom log file for OpenRC }} =Usage= ==Runlevels== OpenRC can be controlled and configured using '''openrc''', '''rc-update''' and '''rc-status''' commands. Delete docker from runlevel "default": <code># rc-update delete docker default</code> ==Listing== It is possible to list runlevels and their assigned initscripts (services) without needing root permission, by running <code>rc-update show -v</code> By default (without the -v flag) rc-update will only show the initscripts that have been assigned to a runlevel Alternatively, the same can be achieved with rc-status: <code>rc-status --servicelist</code> ==Adding named runlevels== OpenRC implements runlevels as directories that are stored in '''/etc/runlevels''' and additional runlevels can be created by running: <code># install -d /etc/runlevels/<runlevel></code> Where <runlevel> is the placeholder for the name Additional runlevels can be helpful in providing alternative system profiles during bootup 91c91088e64557c44e952724254886d85c2c3b52 0 1215 5267 5067 2026-05-25T07:19:55Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:AUR Helpers]] {{Work In Progress}} {{Stub}} {{SoftwareInfobox | image = | caption = | title = Paru | releasestatus = Maintained | lastrelease = v2.1.0, 2025-07-08 | languages = Rust, Shell | developers = Morganamilo | website = [https://github.com/Morganamilo/paru github.com] }} '''Paru''' is an open-source [[AUR Helper]] which automates the process of searching, retrieving and building packages from the [[Arch User Repository]]. Paru's main advantage over other AUR Helpers is that PKGBUILDS are downloaded automatically by default for the user to inspect, helping ensure that malicious packages aren't downloaded. == Installation == Paru can be installed via one of the following methods. Instructions from building from source can be found on Paru's GitHub page. === Using Git: === <code>git clone https://aur.archlinux.org/paru.git && cd paru</code> <code>makepkg -sci</code> === Using yay: === <code>yay -S paru</code> == Usage == The following commands are typical usage of Paru: {| class="wikitable" |+Common Paru Commands !Command !Description |- |<code>paru</code> |Alias for <code>pacman -Syu</code> |- |<code>paru -S <package-name></code> |Search the online repositories and installs the given package(s). |- |<code>paru <package-name></code> |Interactively searches and installs the given package(s). |- |<code>paru -G <package-name></code> |Downloads the PKGBUILD and related files of the given package. |} 6e70195e41e8cc44a5d6dd7c3a4c834cfd432837 0 1096 5268 4962 2026-05-25T07:20:05Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Stub}} {{DistributionInfobox | title = Pear OS | image = [[File:pearos.png|pearos.png]] | caption = Logo of Pear OS | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64 | website = https://pearos.xyz/ }} '''Pear OS''' is an operating system based on [[Arch Linux]] with default [[Linux kernel]] (version 6.17) and [[systemd|SystemD]]. It is developed by one person. Its main purpose is to give Linux users the feeling of [[MacOS]]. == Information == Pear OS was originally developed as a web OS in 2010. The OS got later in 2014 sold to an unknown company, however in ~2022 Alexandru Bălan started developing the software again now it's available and free. ddfeb8d1c1239121587ccb339e6c161ce9b45cf9 0 907 5269 4284 2026-05-25T07:20:15Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [https://pipewire.org/ PipeWire] is an audio and visual engine and server designed to be low-latency and easy to use with its graph-based approach. It supports use cases handled by [[ALSA]], [[PulseAudio]] and/or [[JACK]]. PipeWire's main features are: * Low latency playback and capture * Real-time processing * Seamless support for sandboxing applications via [[Flatpak]] * Support for ALSA, PulseAudio, JACK and G-Streamer By default PipeWire ships with its daemon, an example session manager, a development library and tools to interact with the PipeWire daemon == Enabling PipeWire == PipeWire comes with the necessary systemd socket and service files, however if it's installed as a replacement to PulseAudio its best to disable PulseAudio first by running: <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code> Afterwards, enable PipeWire by running <code>systemctl --user enable --now pipewire.service wireplumber.service</code> Usually, the pipewire-pulse socket will be enabled as needed, but it can be explicitly enabled with <code>systemctl --user enable --now pipewire-pulse.socket</code> The --now flag is not necessary, but if omitted PipeWire will only be automatically started after a restart of the PC or the user logs out and logs back in. == Configuration == Pipewire handles configuration in: - <code>/etc/pipewire/pipewire.conf</code> for system-wide - <code>~/.config/pipewire/pipewire.conf</code> for per-user configuration. A sample set is supplied in <code>/usr/share/pipewire/pipewire.conf</code>, and is used if the other locations don't already exist, or don't cover a specific value. Fragments of configuration (Available since PipeWire 0.3.45) can be placed in the following locations: - <code> /etc/pipewire/pipewire.conf.d/</code> - <code> ~/.config/pipewire/pipewire.conf.d/ </code> For system-wide and per-user configurations respectively === Examples === PipeWire uses a default global sample rate, all of the audio is processed to that, then reprocessed to match the sample rate of the device. This behavior is avoidable by setting a default sample rate that matches with the audio output devices sample rate, for example 48000Hz {{FileBox|title=/etc/pipewire.conf|content= context.properties = { default.clock.rate = 48000 default.clock.allowed-rates = [ 48000 44100 ] } }} Up to 16 default clock rates can be specified in this manner Similarly, it is possible to set the minimum quantum to prevent stuttering in the following manner: {{FileBox|title=/etc/pipewire.conf|content= default.clock.min-quantum = 2048 }} More information about configuring PipeWire can be found [https://docs.pipewire.org/page_man_pipewire_conf_5.html here] == Interacting with PipeWire == PipeWire can be controlled with PulseAudio tools, such as '''pactl''', or (without PulseAudio) it can be achieved with wpctl (if the Wireplumber session manager is used) or pw-cli (available at all times). === Controlling volume === Using '''wpctl''' to increase the volume by ex. 5% <code>wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+</code> Alternatively, the same can be achieved with '''pw-cli''' First, find the node by running <code>pw-cli ls Node</code>, then run <code>pw-cli s <numical node id> Props '{mute: false, channelVolumes: [ 0.2, 0.2 ] }' </code> to unmute and set the volume of the application to 20% === GUI patchbays === Patchbays are tools that are designed to manage PipeWire's audio, video and MIDI connections in a user-friendly manner. There are multiple GUI patchbays available for Pipewire, such as [https://gitlab.freedesktop.org/pipewire/helvum helvum] which is a GTK based patchbay, [https://gitlab.freedesktop.org/rncbc/qpwgraph qpwgraph] is available for those who prefer a Qt based patchbay, or [https://github.com/dimtpap/coppwr coppwr] which is made with Rust and uses egui and eframe. 4e7af7c225193f7a68422f4d33d6d7b7653bf8c3 0 1121 5270 4868 2026-05-25T07:20:25Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Navidrome Clients]] [https://psysonic.de Psysonic] is a local music streaming client made for [[Navidrome]] servers. The client boasts a modern, sleek UI, native [https://last.fm last.fm] [[scrobbling]], and wide range of support for operating systems, including: Windows, MacOS, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [https://foss.wiki/Flatpak Flathub] release. 03ef1a7baddcc77f41b997b480f33efdc48869e5 0 1040 5271 5225 2026-05-25T07:20:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = [[DNF]], [[APT]] | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = [[systemd]] | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Qubes OS separates applications and workflows into isolated compartments known as '''qubes'''<ref>also known as a '''domU,''' '''security domain,''' or simply '''domain'''</ref> by leveraging [[Xen]]-based virtualization<ref name=":0">{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/intro.html|title=Introduction to Qubes OS|accessdate=2026-05-24}}</ref>. It should also be noted that Qubes, rather than being considered a Linux distribution, may be considered as either a ''meta-distribution'' (in a similar regard as [[Bedrock Linux]]), or a Xen distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#is-qubes-just-another-linux-distribution|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Technically, any [[X86-64|x86_64]] operating system may be used as a qube, but the extent to which it is supported varies. == Installation == The Qubes OS project provides a [https://doc.qubes-os.org/en/latest/user/downloading-installing-upgrading/installation-guide.html comprehensive installation guide] in its documentation. Users may consider reading the documentation on [https://doc.qubes-os.org/en/latest/user/downloading-installing-upgrading/install-security.html installation security] as well. === System Requirements === The following features are <u>required</u> (but may not be sufficient) for Qubes OS<ref name=":2">{{Cite|url=https://doc.qubes-os.org/en/latest/user/hardware/system-requirements.html|title=System Requirements|author=Qubes OS Project|accessdate=2026-05-25}}</ref>: * [[X86-64|64-bit Intel or AMD processor]] ** Intel VT-x with EPT or AMD-V with RVI ** Intel VT-d or AMD-Vi (also known as AMD IOMMU) * 6 GB RAM * 32 GB free space on disk The following are <u>recommended</u> for running Qubes OS<ref name=":2" />: * [[X86-64|64-bit Intel processor]] ** Intel VT-x with EPT ** Intel VT-d ** AMD processors are not recommended due to inconsistent security support on client platforms (see Important Notes for details). * 16 GB RAM * 128 GB free space ** A fast solid-state drive is strongly recommended by the project * An Intel integrated graphics processor is strongly recommended by the project ** Nvidia GPUs may require significant troubleshooting. ** AMD GPUs have not been formally tested, but Radeons (especially RX580 and earlier) generally work well. * A non-USB keyboard, or multiple USB controllers * A Trusted Platform Module (TPM) with proper BIOS support == Supported [[Qubes OS#Templates|Templates]] == The Qubes OS project officially provides the following templates: * [[Fedora]]-based ** [[XFCE]] ** [[GNOME]] ** Minimal (CLI only) * [[Debian]]-based ** XFCE ** GNOME ** Minimal (CLI only) Community-supported templates are also available, [https://doc.qubes-os.org/en/latest/user/templates/templates.html#community with additional considerations]: * [[Kicksecure]] * [[Whonix]] **Whonix Gateway **Whonix Workstation * Arch (in <code>qubes-templates-community-testing</code>) Users will also be able to create their own Templates from scratch == Architecture == Each qube is implemented as a separate [[Xen|Xen virtual machine]], which the user may utilize for activities such as composing documents or browsing the web<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/getting-started.html|title=Qubes OS Basics|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Each qube is distinguished by its name, which identifies its purpose, and a color which identifies its level of trust<ref name=":0" />. Qubes are copy-on-write, meaning that a [https://doc.qubes-os.org/en/latest/user/advanced-topics/volume-backup-revert.html full revert mechanism is available should it be needed]. === Templates === Templates provide root filesystems for app qubes. When an app qube is started, a copy of the root filesystem will be made and used by the app qube, then discarded on shutdown<ref name=":3">{{Cite|url=https://doc.qubes-os.org/en/latest/user/reference/glossary.html|title=Glossary|author=Qubes OS Project|accessdate=2026-05-25}}</ref>. Software meant to be run in app qubes must be installed in the corresponding template. See https://doc.qubes-os.org/en/latest/user/templates/templates.html === App qubes === App qubes are qubes where the user is meant to conduct everyday activities. An app qube will use a copy of the root filesystem taken from a chosen [[Qubes OS#Template|template]], and will only keep things in <code>/home/</code>and <code>/usr/local/</code>after being restarted<ref name=":3" />. App qubes can also be disposable templates and provide the base for disposable qubes. === Disposables === Disposable qubes obtain a fresh filesystem from its disposable template (distinct from a template) upon startup and fully discard it after shutting down<ref name=":3" />. === Standalones === A regular vm, both root and user directories are kept between starts<ref name=":3" />. == Security == === Qubes Master Signing Key === The QMSK is an [[Gnupg|OpenPGP]] key used as the root of trust for the Qubes OS Project to verify developer keys, release signatures, and communications<ref name=":1">{{Cite|url=https://doc.qubes-os.org/en/latest/project-security/verifying-signatures.html#how-to-import-and-authenticate-the-qubes-master-signing-key|title=Verifying signatures|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. The QMSK is available from the Qubes Project at https://keys.qubes-os.org/keys/qubes-master-signing-key.asc, or in any Qubes OS provided qube at <code>/usr/share/qubes/qubes-master-key.asc</code>. Users are encouraged by the Qubes Project to "distrust the infrastructure"<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#what-does-it-mean-to-distrust-the-infrastructure|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-25}}</ref> and to compare multiple channels to verify the QMSK's fingerprint<ref name=":1" /> Any single source (including this website) should not be trusted. One copy is provided here as: <code>0x427F11FD0FAA4B080123F01CDDFA1A3E36879494</code> Other potential channels to obtain the fingerprint from include: * The Qubes OS Project wiki * Video recordings of presentations about Qubes * Asking a friend(s) * Asking a stranger(s) === Limitations === It is important to note that while Qubes OS is designed to to limit the damage caused by the compromise of one or multiple qubes, <u>it does ''not'' attempt at additional hardening for the VM operating system itself</u> above that of the base distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/developer/system/security-design-goals.html#security-design-goals|title=Security Design Goals|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Users may consider using other security-oriented distributions in conjunction with Qubes OS for additional security. == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] d3eaecfd636bf576890946881798486b907eb789 0 1079 5272 4390 2026-05-25T07:20:45Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} {{Needs Citations}} {{DistributionInfobox |title = SUSE Linux Enterprise (SLE) |image = [[File:SUSE_Logo_Primary.jpeg|350px| SUSE Secordary Logo]] |caption = The official SUSE logo |releasestatus = Maintained |releasemodel = Stable |packagemanager = [[Zypper]] |defaultdesktops = [[GNOME]], [[Plasma]] |usagetype = Server |architectures = x86-64, ppc64le, aarch64, s390x |website = [[https://www.suse.com/ suse.com]] }} [[Category:Linux Distributions]] '''SUSE Linux Enterprise (SLE)''' is a set of commercial server-focused [[Linux Distributions]] developed by the German software development company [[SUSE]] f446bdc429a42d159e9e4d3f563727f1e4e71a6c 0 1166 5273 4844 2026-05-25T07:20:55Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Work In Progress}} {{DistributionInfobox | title = SculptOS | image = [[File:Arch Linux "Crystal" icon.svg|Genode_OS_icon]] | caption = The Logo of Genode, the framework of SculptOS | releasestatus = Maintained | releasemodel = Bi-Annual Release | packagemanager = [[Depot]] | usagetype = Desktop | architectures = x86_64 (Primary), AArch64 (Not prebuilt), RISC-V (Not prebuilt) | website = [https://genode.org/download/sculpt genode.org/download/sculpt] | defaultdesktops = }} This page is currently a work in progress. adc9755130e05cffa83914740c2ec228b26b0a6b 0 1034 5274 5229 2026-05-25T07:21:05Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki Snap is a package management system aimed for desktops, cloud and IoT devices. The respective packages are termed as '''snaps''' which is a bundle of an app along with its dependencies which works across [[Linux Distributions|Linux distributions]].<ref>[https://snapcraft.io/about About Snaps], Snapcraft, 2026-05-25 (Accessed: 2026-05-25)</ref> Snapd is the background service that manages and maintain the installed snaps.<ref name=":0">[https://snapcraft.io/docs/installing-snapd Install the daemon], Snapcraft, 2026-01-13 (Accessed: 2026-05-25)</ref> The various snaps can be downloaded using the [https://snapcraft.io/store Snap Store]. One can build and publish snaps using [https://documentation.ubuntu.com/snapcraft/stable/ Snapcraft]. == Installation == Snapd needs to be running before a snap can be installed. It comes preinstalled with a few distributions by default such as [https://neon.kde.org/ KDE Neon], [[Manjaro]], [https://getsol.us/ Solus], [[Ubuntu]], Most [https://wiki.ubuntu.com/DerivativeTeam/Derivatives#Official_Ubuntu_Flavors Ubuntu Flavours] and [[ZorinOS]]. For distributions without Snapd preinstalled, one can refer to [https://snapcraft.io/docs/tutorials/install-the-daemon/#without-snap this section] of the official documentation and choose their respective documentation to install Snapd.<ref name=":0" /> After installing Snapd, one can head over to [https://snapcraft.io/store Snap Store] for searching and installing the software they want.<ref>[https://www.geeksforgeeks.org/linux-unix/snap-package-manager-on-ubuntu/ Snap Package Manager on Ubuntu], GeeksforGeeks, 2020-01-27 (Accessed: 2026-05-25)</ref> == References == <references /> c855bebe6e85012b1bb4fb68cb6b96d6b199252a 0 1060 5275 4326 2026-05-25T07:21:15Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] Swap in computing generally refers to memory paging. Swapping can refer to both moving pages between memory and secondary storage. On Linux, it is possible to use a combination of swap devices and/or swap files, with the ability to assign a priority value to each one individually. Having a swap file is not always necessary, although can be useful if the system runs out of real memory (on, for example systems with 4 or 8 GiB of memory). == Creating Swap == === Swap partition === If '''/dev/sda3''' is the swap partition to be used, it can be formatted as such:<syntaxhighlight lang="sh"> mkswap /dev/sda3 </syntaxhighlight> === Swap File === To avoid the rigidness of a swap partition, it is possible to create a swap file, which can be located ''in'' a partition, and as such can be moved and resized as needed. The utility '''mkswap''' can be used for this purpose as well:<syntaxhighlight lang="sh"> mkswap -U clear --size 4G --file /path/to/swapfile </syntaxhighlight>By making a swapfile like this, the necessary permissions will already be set == Activation == In both cases, be activated with<syntaxhighlight lang="sh"> swapon /dev/sda3 </syntaxhighlight>For a swap partition, or<syntaxhighlight lang="sh"> swapon /path/to/swapfile </syntaxhighlight>For a swap file. It is also recommended to add the swap file to /etc/fstab, to automatically activate it at boot time: {{FileBox | title = /etc/fstab | content = # Swap partition /dev/sda3 none swap sw 0 0 # Swap file /swapfile none swap sw 0 0 }} == Tuning == === Prioritizing an area === It is possible to assign a "priority" value to the swap partitions/files, (an integer from 0 to 32767), with a higher priority area being utilized first. If two different areas share a priority value they are utilized in a round-robin fashion<ref>https://linux.die.net/man/2/swapon</ref> For example, prioritizing a fast NVMe drive (/dev/nvme0n1) before a slow HDD (/dev/sdb): {{FileBox | title = /etc/fstab | content = /dev/nvme0n1p2 none swap sw,pri=16383 0 0 /dev/sdb2 none swap sw,pri=1 0 0 }} 75ecc1dedac722a36a613f0713f4c0af9409066d 0 1175 5276 4950 2026-05-25T07:21:25Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = TailsOS | image = [[File:Tails-logo.png]] | caption = TailsOS's logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[APT]] | defaultdesktops = [[GNOME]] | usagetype = Desktop | architectures = x86_64 | website = [https://tails.net/index.en.html] }} [[Category:Linux Distributions]] [[File:TAILS 4.14 ENG 05 01 2021 15 39 25.png|thumb|TailsOS open to the "About Tails" screen]] '''TailsOS''' ''(or TAILS)'', short for '''"The Amnesic Incognito Live System"''', is a [[Debian]]-based privacy-focused [[Linux Distributions|Linux distribution]] intent on preserving anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so. 5eaf5fee552e43f898db0547f4cb4fcc371c36b7 0 1236 5277 5264 2026-05-25T07:21:31Z Hyperreal 388 wikitext text/x-wiki For the main page, visit [[Age]]. An '''identity''' generated with <code>age-keygen</code> is typically a plaintext file with three lines. The first line contains a timestamp of when the identity was created. The second line contains the identity's public key. The third line contains the identity's secret key. # created: 2026-05-25T01:46:24-05:00 # public key: age1yjd47dpqulfqs8d35ftazzxwf4dfx5qwp2fs5qn8mznz29rpdyxsz804s5 AGE-SECRET-KEY-1057P2C323UDZJZ49CT3LTWTP0U8DZ8SK7N3DNVKGH04R8AUAY29ST26XK5 A '''recipient''' is in the form of an <code>age</code> public key; for example, <code>age1yjd47dpqulfqs8d35ftazzxwf4dfx5qwp2fs5qn8mznz29rpdyxsz804s5</code>. For further information, consult the manual pages for <code>age</code>, <code>age-inspect</code>, and <code>age-keygen</code>. == Generate a key pair, save it to an unencrypted file, and print the public key to stdout == age-keygen --output identity.txt Public key: age1w8m0z4yq4ev97yw99hrlmq03p5cdwmtrg4lptpvardcr2d7tuv5sh7fpm3 == Generate a post-quantum key pair, save it to an unencrypted file, and print the public key to stdout == age-keygen -pq --output post-quantum-identity.txt Public key: age1pq1k038we43y2guj0tvyah4sdeyt4txgz83de39q79499mxyvsxs2smg2k9kphange32z77vct6x44vvfw4w6hf2jwhu7fuyuy4ulgxgu02x59ux9da4jmdqdunrvapvpw5eqx09ze57484tuvms75rxau59mxafyqterzpew4tkvz5jtvr2qu04dvrfy32aa9ut232er05nwqgv5wdc2lrxffe24fmpeqz2lmgscqpdj3leq3xxy2ullm2hnm6yslfcuvww9vaaq9jydf8hfztwszm2fwmgja0e23jpd8cpku9cwgtnv5tp6m50d25wyd4njj4prpred84dfgxk6znzx5q3pymdjvpt9a7lkd85jqrxplrdmu49pq8jcxk6p9gzg4ec0zzpvwhky82ezttn6s9zumz3e59vax2pdwjzwag6645sfvhydduynkwcqx27cd70wtvuqqm3m6jjvpeytd4mvr29x2czq54r8sy3ay6s5x0hfp0m9cv3c58328fhffzntl6axe7ycj40sy2r4xmcx2v33qpjaz7q9ak6zfh525qh356qpxzcmze959yj8vqzpn39sel8rdzjwrwa3tvdd2vgymptq9kslk6yy7u06e4405gnx93k68snr3zqvx6mtzemzeys0c5xkz8vjm6jftvyhrtqmmngz0x4yh3qjp4vv0dcdtr7sdjzuqeg7ueswhqpgtv8vspv8fxvv9ucsu33vejz48kcn9pqz2k0z62wn84fzh9r3mucdepu5y8jpl627weylhrq5xrjqcq79r8ysymxcjpw6r3c4qzqpaam3euyqjkrw30frcmucvdnkpf5c25hevvp70tjgph8ycqyeaycp9xg2592jfjghu3fgkn7ywt3n3t73j603e7n2k45fckvu4299jx4vxvyl7gkq3hhftdexkwdlrn97gk9x095pcrw6z5jjpg0gxra6sm8hhezvn8nslmrzk9mljmvd2x989uy8gmmva3d39trv4hz8ltfgzmfvavxsv7gmysw33m6rlfn4h9y5l9q0zpevdqsgfsekcrrnrcqgh66qxqsxd5ddupntns0zkg8vhujkc3ryy5fmpc38eq9099pfl5zykxr33ghcdn0s2edeny4xr3u7mam2ww0gf9ft0cre6dk6d8zcd4zy9xe9ugl99zh2g6xua8d2xkwyk9fj6qzzksk2p2g9kses8axwfkdtacmtnyvc74006f5wphhycatqgzrv2vttmsexym4q8w3y3ml9zkzcygg22fkw9xnw7tzvgf0yrg93hvhfgggqdhwkcffc9lqkt4u6q3nr0anw6q8sp5lym4u55hct8k3qeqxfqp4tqthx4rnam3exfye23srn3sj368t9p9edczs9grynmun0t939nghpkd08rhgtf9tqntvsemyuytj24dvrvr29wfewxzxhpx3w4cgftkps6gj82hge4a5tx87jgfr3ak82eqgycphac8vg4uxfu052n0wj9zx333gxg0nnlpvyr3pw30feze76luvn2vqeve7sl52fc99pc6zh3cnv48fqjh3jc6d23yvx9404cmj63ssqz9za76r4rd2924fjscvvgf2jpwl92h6f53g3ggpyrhsue6snq039pe29pn2r2hndsvddazylg3m9lhe6cpeuf5vxspdv3yfqhhv6xh86e6ussr66f2smgxcgk3cg7rd42qchfzr98tqccvxy5vy3vlhjkyvgugreg8ykf8qnepsyrggca4h0cmv7tpn5ym547az639decchffuy0d90gxa23d5h22jfka6vgmzdvymxax60trfnfdwshu5a6j6vt80955c8p3mtlcegt796nhu7j3rhqdqgfh42th22l4ayd6tzatggqjxjlw0d2chscvjc0u7dwzgwmnzf2c6x3g9zlnn9ymzd4fj == Convert an identity to a recipient and print the public key to stdout == age-keygen -y identity.txt age1w8m0z4yq4ev97yw99hrlmq03p5cdwmtrg4lptpvardcr2d7tuv5sh7fpm3 == Generate an encrypted file that can be decrypted with a passphrase == When using the <code>-p|--passphrase</code> flag, you will be prompted to input a passphrase. age [-p|--passphrase] [-o|--output] path/to/encrypted_file.age path/to/unencrypted_file == Encrypt a file with one or more public keys entered as literals == Repeat the <code>--recipient</code> flag to specify multiple recipients. age --recipient age1w8m0z4yq4ev97yw99hrlmq03p5cdwmtrg4lptpvardcr2d7tuv5sh7fpm3 --output encrypted_file.age unencrypted_file.txt == Encrypt a file to one or more recipients with their public keys specified in a file == The recipients public keys must be specified in the file one per line. age --recipients-file recipients.txt --output encrypted_file.age unencrypted_file.txt == Decrypt a file with a passphrase == You will be prompted to enter the passphrase for the encrypted file. age [-d|--decrypt] [-o|--output] decrypted_file.txt encrypted_file.age == Decrypt a file with a private key file == age --decrypt --identity identity.txt --output decrypted_file.txt encrypted_file.age 80ca3b62fa305eed409873f6aac149183664b3d0 0 1099 5278 4470 2026-05-25T07:21:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | image = [[File:E350507f5830c9c2a6a0c477dd3f1c68.png|thumb]] | caption = Termux Logo | title = Termux | releasestatus = Maintained | lastrelease = 0.119.0-beta.3 2026-02-11 | firstrelease = 0.17, 2015-05-30 | languages = [[java]], [[C]], [[C++]] | developers = Termux Core Team | website = https://termux.dev }} '''Termux''' is a free and open-source terminal emulator and Linux environment application for Android devices. It allows users to run a lightweight [[Linux Distributions|Linux Distrubution]] directly on their mobile devices without requiring root access. Designed primarily for developers, system administrators, and power users, Termux provides a command-line interface similar to that found on desktop Linux systems. == Overview == Termux bridges the gap between mobile and desktop computing by bringing a [[UNIX|Unix-like]] environment to Android. Users can install and run a wide variety of command-line tools, for example [[fastfetch|FastFetch]], programming languages, and utilities, making it a versatile platform for development, experimentation, and learning. == Architecture and base distribution == Termux is based on a minimal Linux environment built using: * [[Android]] as the host platform * A custom package management system similar to those in Linux distributions * The [[APT|APT (Advanced Package Tool)]], adapted for Android * Libraries compiled specifically for Android’s Bionic libc instead of [[GNU|GNU libc]]. == Features == Termux includes a repository of thousands of packages that can be installed using Commands like: * pkg install python * pkg install git * pkg install clang df1e95223a7a748bfab1edfef4ca128475cc6e30 0 1092 5279 4465 2026-05-25T07:21:45Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = Tinfoil Hat Linux | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | releasestatus = Discontinued | releasemodel = None | packagemanager = None | defaultdesktops = Terminal only | usagetype = Security | architectures = i386 | website = tinfoilhat.shmoo.com }} '''Tinfoil Hat Linux''' ('''THL''') is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defeat itself from surveillance including TEMPEST and KeyLoggers == List of Tinfoil Hat Linux methods against surveillance== * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanism were intended to enhance operational security limiting data persistence and mitigating common surveillance techniques. 28430211458a6ddd34cf5cea9548a652fb50755b 0 1120 5280 5103 2026-05-25T07:21:55Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Vimlogo.svg|thumb]] |caption=Vim |title=Vim |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=1.14, Jan, 1992 |languages=[[C]], [[Vim Script]] |developers=[https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] |website=[https://www.vim.org/ vim.org] }} [[Category:Software]] [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ''Also see: [[GNU Emacs|Emacs]].'' ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. == References == <references /> 4ab793a4d42e75b080344558941a5d2c94b55df2 0 1048 5281 4912 2026-05-25T07:22:05Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki '''X.org''' [[File:X.Org Logo.svg.png|center|thumb|'''X.Org logo (1999)''']] '''X.Org''' (full name: X.Org Server) is a free and opensource ([[FOSS]]) implementation of X Window System ([[X11]]) server, it implicates fundamental graphical layer used in traditional UNIX and Linux operating system environments. Responsible for managing the graphical interface, rendering image on the screen and input device support, like keyboards, mouses and touch screens. == History and Origin == The roots of the project date back to the 1980s. at the MIT university the same one that created [[X11]], direct predecessor of X.Org was XFree86. In 2004, as a result of controversial license changes on XFree86 (Version 4.4.0), community and developers decided to create a fork, and that resulted creation of X.Org Foundation and release of X.Org, which quickly became a standard in the mainline in all important Linux Distributions. == Architecture Client-Server == X.Org is based on classic, network model client-server, which distinguishes it from other modern protocols like [[Wayland]]: Server (X Server): It works directly on user's workstation, it manages hardware like, Screen, GPU and input devices Clients (X Clients): these are graphical applications (e.g web browser, video player, terminal). They don't draw anything directly on screen, instead they send requests to the server, asking if they can draw a window. [[File:X client server example.png|thumb|422x422px|X client Client-Server Architecture '''Example''']] == Key components == Internal architecture of X.Org is based on layers, that were evolving in the time of decades, to keep up with hardware: DIX (Device-Independent X): Layer Not dependent on hardware. It is responsible for processing X11 protocol, managing windows and communication between Clients. DDX (Device-Dependent X): Layer dependent on hardware, it is responsible for physical rendering and teamwork with specific video drivers. DRI (Direct Rendering Infrastructure): key mechanism that improved efficiency of 3D graphics on Linux. In traditional model of X11 every app needed to send it's own instructions to the X.Org server, and then it started to send those instructions to the GPU, for the 3D games (for example Quake) it meant drastic latency and low framerate (FPS). DRI avoids this problem: it allows 3D apps (that are using OpenGL or Vulkan) to talk directly with GPU, completely avoiding X.Org Server. == Drivers and Input Managing == traditional X.Org was depending on drivers of the user (DDX), like <code>xf86-video-intel</code>, <code>xf86-video-amdgpu</code> or proprietary NVIDIA drivers, at the same time system is in bigger matter using kernel mechanisms like KMS (Kernel Mode-Setting). In case of input devices, historical drivers like evdev, synaptics are currently replaced by universal library name libinput, that is providing consistent gesture and keyboard support through X.Org and (via wrapper xf86-input-libinput) for [[Wayland]]. == Current Status of X.Org vs Wayland == Although X.Org has powered systems such as [[Slackware]], [[Debian]], [[Ubuntu]], [[Fedora]], [[EndeavourOS|EndeavorOS]], and [[Arch Linux]] for over two decades (allowing graphical enviroments to work e.g. [[KDE Plasma|KDE]], [[XFCE]], [[MATE]], [[LXQt|LXQT]]), now is currently undergoing deep maintenance. Modern distributions are replacing it layer by layer with [[Wayland]] protocol, that is eliminating architecture client-server for the easier and safer model. when compositor is talking directly with kernel and hardware. Besides that, X.Org is still an Key Component of the ecosystem thanks to: # XWayland: Translation layer, that allows running older apps for X11 on [[Wayland]]. # Stability: Unparalleled design maturity, flexibility of network configurations, and full support for specific legacy software. 502e76976c681a3de95e33cc85d84e86e42b15e1 0 1182 5282 4947 2026-05-25T07:22:15Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:File managers]] {{SoftwareInfobox | image = [[File:Ytree v3.0.0-alpha F8 split view.png|frameless]] | caption = Ytree v3.0.0-alpha in F8 split view | title = Ytree | releasestatus = Alpha (maintained) | lastrelease = v3.0.0-alpha (tagged 2026-04-29) | languages = [[C]] | developers = Rob Kam; based on original Ytree by Werner Bregulla | website = https://github.com/robkam/ytree }} '''Ytree''' (<code>ytree</code>) is a keyboard-first [[TUI]] file manager for UNIX-like systems. It follows a “logger” model: it scans directory trees into memory so users can navigate, filter, tag, and operate across large file hierarchies quickly.<ref name="readme">[https://github.com/robkam/ytree README.md], github.com/robkam/ytree (Accessed: 2026-05-23)</ref><ref name="man">[https://github.com/robkam/ytree/blob/main/etc/ytree.1.md etc/ytree.1.md], github.com/robkam/ytree (Accessed: 2026-05-23)</ref> == Overview == Ytree is inspired by DOS XTree-style workflows and presents a multi-pane terminal interface with a directory tree, file window, and info/statistics pane. It supports multiple operating modes (Directory, File, Showall, Global, Archive, Split Screen, and Preview).<ref name="man" /> == Features == ==== Multi-volume logging ==== Ytree can log one or more directories or archives at startup and switch between logged volumes quickly.<ref name="man" /> ==== Split screen and preview ==== It includes split-screen panel mode (F8) and integrated file preview mode (F7).<ref name="man" /> ==== Archive-as-directory workflow ==== Supported archives (such as ZIP/TAR/GZ) can be browsed like virtual directories, with archive-aware operations where supported.<ref name="man" /> ==== Current release status ==== As of 2026-05-23, the latest published version marker is <code>v3.0.0-alpha</code> (tagged 2026-04-29), and the README describes the software as in active alpha development.<ref name="readme" /><ref>[https://github.com/robkam/ytree/tags Tags], github.com/robkam/ytree (Accessed: 2026-05-23)</ref> == References == <references /> 59eda5ac52475251dd5456e753584a3e2053569d 0 784 5283 5012 2026-05-25T07:22:25Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Zorin OS | image = [[File:Zorin Logomark.svg.png|Logo for Zorin OS|65px]] | caption = Zorin OS logomark | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = [[GNOME]] | usagetype = Desktop | architectures = x86_64 | website = [https://zorin.com/os/] }} {{Stub}} Zorin OS is an [[Ubuntu]]-based [[Linux Distributions|Linux distribution]] made for newcomers to Linux, with a modified version of the [[GNOME]] [[GUI]] and [[XFCE|Xfce 4]] that is familiar to Windows users. It also has a paid model that comes with more desktop options and free software. It was first released on July 1, 2009, under the name Zorin OS 1.0. 7099c0f38f9cc3235a80ca0bd712ed07f48eaf1b 0 762 5284 5233 2026-05-25T07:22:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Zypper_Screenshot_2026-01-12.png|400px|Thumb]] | caption = Zypper install screenshot | title = Zypper | releasestatus = Maintained | firstrelease = 2006-01-14 | lastrelease = 1.14.94, 2025-09-23 | languages = [[C++]] | developers = [[SUSE]], [[openSUSE]] | website = [https://en.opensuse.org/Portal:Zypper Portal:Zypper] }} [[Category:Package Managers]] Zypper is the primary [[Package Manager|package manager]] for [[SUSE Linux Enterprise|SUSE Linux Enterprise]], [[openSUSE|openSUSE]] and their derivatives. Zypper is a command-line interface to ZYpp System Management Library (libzypp) and uses [[rpm|RPM]] package archives <ref>[https://manpages.opensuse.org/Tumbleweed/zypper/zypper.8.en.html zypper(8)] openSUSE manpages, 2025-09-23 (Accessed: 2026-01-12)</ref> similar to [[Fedora|Fedora Linux]] and [[RHEL|Red Hat Enterprise Linux]]. Zypper is a binary package manager with support for x86, x86-64 (amd64), ARM, s390x and PowerPC. <ref>[https://get.opensuse.org/tumbleweed/?type=server#download openSUSE Tumbleweed] openSUSE Tumbleweed download page showing supported CPU Architectures (Accessed: 2026-01-12)</ref> == History == libZypp and by extension ZYpp and Zypper were released on January 14th 2006. <ref>[https://github.com/openSUSE/libzypp/blob/90acb93974a99bea7409516be55d6acdc35099f7/package/libzypp.changes libzypp Github] Earliest libzypp changelog (Accessed: 2026-01-12)</ref> In March of 2025 Zypper added experimental support for parallel downloads starting in libzypp version 17.36.4 and Zypper version 1.14.87. <ref>[https://news.opensuse.org/2025/03/27/zypper-adds-experimental-parallel-downloads/ openSUSE] Announcement of experimental parallel downloads support (Accessed: 2026-01-12)</ref> In May of 2025 parallel downloads were enabled by default starting in libzypp version 17.37.1 and Zypper version 1.14.90. <ref>[https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JR725AXWDZYLJ3PKIKYAYQQAXE6OWQMM/ openSUSE] Announcement of parallel downloads becoming the new default (Accessed: 2026-01-12)</ref> == Usage == Zypper uses an argument system for interacting with the package manager with its syntax being <code>zypper [ARGUMENT] [PACKAGE]</code> for example <code>zypper install vim</code>. There are 2 forms of each argument, full and abbreviated, this behavior is similar to [[DNF|DNF]] the Fedora/RHEL package manager. {| class="wikitable" |+Common Zypper Arguments !Full !Abbreviated !Description |- |<code>zypper install [TARGET]</code> |<code>zypper in [TARGET]</code> |Installs or updates a given package or pattern (use <code>-t</code> flag when installing patterns) |- |<code>zypper remove [TARGET]</code> |<code>zypper rm [TARGET]</code> |Uninstalls a given package |- |<code>zypper update</code> |<code>zypper up</code> |Upgrades the installed packages without removing packages (This is the preferred way to update a Leap or SLES system) |- |<code>zypper dist-upgrade</code> |<code>zypper dup</code> |Upgrades the installed packages while performing vendor changes, package removals and renames (This is the preferred way to update a Tumbleweed system) |- |<code>zypper refresh</code> |<code>zypper ref</code> |Refreshes the package repository mirrors (This is performed automatically is zypper detects an out of date repository when running install, remove, update, dist-upgrade or search commands) |- |<code>zypper search [SEARCH-TERM]</code> |<code>zypper se [SEARCH-TERM]</code> |Searches the enabled repositories for packages or patterns containing the search term entered |- |<code>dry-run</code> |<code>-D</code> |Runs the command being dry-ran without making any changes to the system |- |} == References == 95dceab1ab704cfdc4368c291dcc726f49b14c1a 828 204 5285 3462 2026-05-25T07:31:07Z Madonuko 140 add license and sourcecode field Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage(args.image, args.caption) end retval:addRow('Release Status', args.releasestatus) retval:addRow('Last Release', args.lastrelease) if args.firstrelease and args.firstrelease ~= '' then retval:addRow('First Release', args.firstrelease) end retval:addRow('Language(s)', args.languages) retval:addRow('Developer(s)', args.developers) retval:addRow('Website', args.website) if args.license then retval:addRow('License', args.license) end if args.sourcecode then retval.addRow('Source Code', args.sourcecode) end return retval end return p d9515cb86bccbb3366f1ef5d0699e42c33b58d26 10 205 5286 3463 2026-05-25T07:37:08Z Madonuko 140 add template data wikitext text/x-wiki <includeonly>{{#invoke:SoftwareInfobox|main}}</includeonly> <noinclude>{{/doc}}<templatedata> { "params": { "title": { "required": true }, "image": { "type": "wiki-file-name" }, "caption": { "type": "string" }, "releasestatus": { "required": true }, "lastrelease": { "required": true }, "firstrelease": {}, "languages": { "required": true }, "developers": { "required": true }, "website": { "label": "Website", "type": "url", "required": true }, "license": { "label": "License", "description": "[[SPDX]] license identifier", "example": "MIT OR Apache-2.0", "type": "string" }, "sourcecode": { "label": "Source code repository", "type": "url" } }, "format": "block" } </templatedata></noinclude> 7d99c386ee5ee6f73be7669254a82c4ccab9415c 0 1176 5287 5217 2026-05-25T08:52:36Z Alxhr0 265 Adding info WIP wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Chimera Linux | releasestatus = Maintained | releasemodel = Rolling | packagemanager = [[apk-tools]] | defaultdesktops = [[GNOME]], [[Terminal User Interface]] [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64, ppc, ppc64, ppc64le, aarch64, riscv64 | website = [https://chimera-linux.org/ chimera-linux.org] }} '''Chimera Linux''' is an independent, general-purpose, rolling-release Linux distribution developed from scratch. It utilizes a FreeBSD-based userland, [[Musl]] C library and the LLVM toolchain, along with the [[Dinit]] service manager. Its primary focus is correctness, consistency and simplicity, but not at the expense of feature set; its primary desktop environment is [[GNOME]].<ref>{{Cite|url=https://chimera-linux.org/docs/|title=Chimera Linux Documentation|author=The Chimera Project|accessdate=5/25/26}}</ref> <references /> 1e4e7563ec03e82b765cd8b8379d06a2879f4a4a 5292 5287 2026-05-25T11:49:00Z Aktywnyyy 296 expanded wikitext text/x-wiki {{DistributionInfobox | title = Chimera Linux | image = [[File:Chimera_Linux_logo.svg|200px|Chimera Linux logo]] | caption = The Chimera Linux logo | releasestatus = Maintained | releasemodel = Rolling | packagemanager = [[Apk]] | defaultdesktops = [[GNOME]], [[Terminal User Interface]] [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64, ppc, ppc64, ppc64le, aarch64, riscv64 | website = [https://chimera-linux.org/ chimera-linux.org] }} '''Chimera Linux''' is an independent, general-purpose, rolling-release Linux distribution developed from scratch. It utilizes a FreeBSD-based userland, [[Musl]] C library and the LLVM toolchain, along with the [[Dinit]] service manager. Its primary focus is correctness, consistency and simplicity, but not at the expense of feature set; its primary desktop environment is [[GNOME]].<ref>{{Cite|url=https://chimera-linux.org/docs/|title=Chimera Linux Documentation|author=The Chimera Project|accessdate=5/25/26}}</ref> == Key elements in the architecture == Chimera Linux rejects many established patterns of traditional Linux ecosystem, replacing standard components with lighter ones, modern and strictly standardized alternatives: * '''FreeBSD Userland instead of GNU:''' Standard tools of terminal (like <code>ls</code>, <code>cp</code>, <code>mv</code> or <code>sed</code>) they come directly from the [[FreeBSD]] code tree, not from GNU <code>coreutils</code>. This means that system commands behave according to POSIX and BSD standards, not GNU-specific extensions. * '''LLVM/Clang compiler:''' While most of the mainline distributions (like [[Arch Linux|Arch]] or [[Debian]]) is compiled using GCC, Chimera is build completely from scratch using modern toolchain [[LLVM]] and [[Clang]]. * '''Musl libc:''' Chimera is using <code>musl</code> as a standard C library instead of <code>glibc</code>. This makes the base system exceptionally lightweight. * '''[[Apk]] Package Manager:''' Borrowed from [[Alpine Linux]] package manager <code>apk-tools</code> handles all software installation. Works incredibly fast and manages dependencies. == Component comparison == {| class="wikitable" ! Component ! Traditional Linux (e.g., Arch) ! Chimera Linux |- | '''Kernel''' | Linux | Linux |- | '''Userland''' | GNU | [[FreeBSD]] |- | '''C Library (libc)''' | <code>glibc</code> | <code>musl</code> |- | '''Compiler''' | GCC | [[LLVM]] / Clang |- | '''System Init''' | <code>systemd</code> | [[Dinit]] |- | '''Package Manager''' | <code>pacman</code> / <code>apt</code> | [[apk-tools]] |} == Target Audience == Chimera Linux '''is not intended for beginners'''. The intended audience are power users, programmers and enthusiasts looking for clean and minimal environment free from GNU and [[Systemd]] domination. It offers unique environment to experience administration in the style of BSD, while maintaining the broad hardware compatibility of the Linux kernel. == External links == * [https://chimera-linux.org/about/ About Chimera Linux] — Official project overview. <references /> c7594ed61e71d751ebf6cc084547066392095e42 0 1167 5288 5242 2026-05-25T11:01:32Z Habaja1 377 minor citation stuff wikitext text/x-wiki {{DistributionInfobox | title = Devuan | image = [[File:Devuan-logo.png]] | caption = The Devuan logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[apt]] | defaultdesktops = Xfce | usagetype = Desktop, Server | architectures = amd64, arm64, armel, armhf, and ppc64el | website = [https://www.devuan.org/] }} '''Devuan''' ( /ˈdɛv.wʌn//), is a [[Debian]] derivative developed by a group of anonymous senior IT professionals known as the ''Veteran UNIX Admins'', aiming to create a version of Debian without [[systemd]]. It was first released on 2016-05-03, with the first stable version being released on 2017-05-25. [[File:Devuan6-xfce.png|thumb|A Devuan installation running [[Xfce]]]] == History == On 25 April 2015, [[Debian]] 8 (''Jessie'') was released. Debian 8 included a lot of new features (such as support for arm), but was most notable for replacing [[sysvinit]], [[upstart]], and other init systems with [[systemd]] by default<ref>{{Cite|url=https://lists.debian.org/debian-announce/2015/msg00001.html|title=Debian 8.0.0 "Jessie" Release anouncement|year=2015|accessdate=2026/05/23}}</ref>. Because of this, a group of developers and users created a [[Debian]] fork of what would become Devuan, aiming to provide people with the choice to other init systems again. The first stable release was released on 2017-05-25, codenamed Jessie 1.0.0, after the astronomical object minor planet 10464. There have been a total of 5 major new Devuan releases since then, the most notable being Devuan 2.0.0 ASCII, wich provided a choice of five different desktop environments ([[XFCE]], [[Cinnamon]], [[Plasma|KDE]], [[LXQt]], [[MATE]]) at install time, also providing installation options for choosing between [[sysvinit]] and [[OpenRC]] for init, and between [[GRUB]] and [[LILO]] for the boot loader, for the first time.<ref>{{Cite|url=https://www.devuan.org/os/announce/ascii-stable-announce-060818|title=Devuan 2.0.0 Ascii release anouncement|accessdate=2026/05/23|year=2018}}</ref>. The most recent release, Devuan 6.0 Excalibur, released on November 2, 2025. == Features == === Init System Options === Devuan supports multiple init systems<ref>{{Cite|url=https://www.devuan.org/os/init-freedom|title=Supported init systems, according to the Devuan website|accessdate=2026/05/23}}</ref>: * [[OpenRC]] - A dependency-based init system from Gentoo. * [[runit]] - A cross-platform Unix init scheme with service supervision. * [https://core.suckless.org/sinit/ sinit] - A customisable, minimal alternative to systemd developed by the suckles community * [[s6]] - A suite of programs for process supervision. * [https://shepherding.services/ shepherd] - An extremely flexible init system written in Guile Scheme. === Architecture Compatability === Devuan has support for numerous architectures. These being: * AMD64/x86-64 * arm64 * armel * armhf * ppc64e === Package Management === Devuan uses [[APT|apt]] as its package manager and maintains its own repositories for packages, converting packages from Debian that require [[systemd]] to systemd-less packages. While it is possible to use [[Debian]] packages directly, it can cause them to break.It also has a repository of [[Proprietary software|proprietary]] packages and codecs. Repositories for Devuan include<ref>{{Cite|url=https://www.devuan.org/os/packages|title=Repositories list from Devuan's website|accessdate=2026/05/23}}</ref>: * Version specific repositories * Development repositories (Testing, Unstable, Experimental) * Specific repositories (security updates, stable updates for fast release packages, stable proposed-updates, backports, experimental) == System requirements<ref>{{Cite|url=https://www.debian.org/releases/stable/amd64/ch03s04.en.html|title=Debian minimum RAM and Storage requirements|accessdate=2026/05/23}}</ref><ref>{{Cite|url=https://www.reddit.com/r/debian/comments/194iyh7/minimum_vm_spec_for_debian_install/|title=Reddit post on minimum specs, comments give clarification on CPU, RAM and storage requirements.|accessdate=2026/05/23|year=2024}}</ref> == {| class="wikitable" |+ ! !Minimal Requirements !Recommended Requirements ! |- |CPU Architecture |1 GHz 64/32-Bit Proccesor | 1.5 GHz 64-Bit Dual-Core Proccesor | |- |RAM |1 GB |2 GB | |- |Storage space |10 GB |20 GB | |- |Knowledge |Making a bootable USB and booting it. | | |} Devuan is a [[Debian]] fork; therefore, the same minimum and recommended requirements also apply to Devuan. However, it is somewhat lighter than [[Debian]], since it does not use [[systemd]]. == Installation == Devuan provides multiple installation methods<ref>{{Cite|url=https://www.devuan.org/os/documentation/install-guides/excalibur/install-devuan#images|title=Installation images and methods for Excalibur (Latest stable version of Devuan)|accessdate=2026/05/23}}</ref>: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Minimal Installation image * Installation Media for arm64, armel, armhf, and ppc64el (Only available through mirror list)<ref>{{Cite|url=https://www.devuan.org/get-devuan|title=Installation media for specific architectures in mirror list|accessdate=2026/05/23}}</ref> You can get these through: * The Devuan release archive * The Devuan mirror list on the website * Torrents on the website == Trivia == * Unlike [[Debian]] who names it's stable releases after Toy Story characters, Devuan's stable releases are named after minor planets and asteroids. * Unlike [[Gentoo]] wich still gives the option to install and use [[Systemd]], devuan has absolutely no option to do this. == References == 539dfeb029906821c8e5994db68e7a7031e89839 0 182 5289 3599 2026-05-25T11:07:30Z Habaja1 377 added some more history wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, [[Xfce]], [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[Category:Linux Distributions]] [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a [[Linux Distributions|Linux distribution]] developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> == History == Debian adheres to the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> In 1997, the Debian Project established Software in the Public Interest as a nonprofit organization to provide ongoing financial support. However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> The first version of Debian, Debian 0.01 released on September 15, 1993. The first generaly usable Debian version to be released, Version 0.90, was released on 16 august 1993<ref>{{Cite|url=https://www.debian.org/doc/manuals/project-history/releases.en.html|title=Debian releases overview|accessdate=2026/26/05}}</ref>. It is considered one of the earliest [[Linux Distributions|linux distros]] alongside [[Slackware]] and [[MCC Interim Linux]]. == Features == === Release Cycle === Debian maintains three primary development branches: * Stable - The current official release, recommended for production systems * Testing - The next planned stable release, featuring newer software versions * Unstable (Sid) - The rolling development branch where new packages are initially introduced === Package Management System === Debian uses the [[APT]] (Advanced Package Tool) built on top of [[dpkg]], featuring: * Over 59,000 ready-to-install software packages * Multiple repository sections (main, contrib, non-free) * Secure package verification through signed repositories * Sophisticated dependency resolution === Project Management === The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as: * The Debian Social Contract * The Debian Constitution * The Debian Free Software Guidelines === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[Window Manager|Window Managers]] instead of [[Desktop Environment|Desktop Environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /> == Installation == Debian provides multiple installation methods: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Live images for testing before installation * Architecture-specific installers * Cloud images for virtual deployment == References == <references /> 8e2f156718c576358a0bcddc2790088af69dc809 2 1224 5290 5207 2026-05-25T11:39:51Z Uniolo 345 Made the note about "contents only" for zip an asterisk wikitext text/x-wiki [[Category:Software]] [[Category:Comparison]] The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes'''*''' |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |} <div style="text-align: center;">'''*'''contents only, file names are not encrypted<ref name=":4" /></div> {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |} <references /> a0240e3f04285719e02f36f6a21cd9b39a9c1912 5291 5290 2026-05-25T11:42:21Z Uniolo 345 Added cite note for minisign ECC data wikitext text/x-wiki [[Category:Software]] [[Category:Comparison]] The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes'''*''' |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |} <div style="text-align: center;">'''*'''contents only, file names are not encrypted<ref name=":4" /></div> {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes<ref>{{Cite|url=https://www.linuxlinks.com/minisign-sign-files-verify-signatures/|title="Minisign – sign files and verify signatures"|author=Steve Emms|year=Feb 3, 2025|accessdate=2026-05-24}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |} <references /> 30b68c000cf86758938e13262eb0211118b331ba 5296 5291 2026-05-25T11:58:27Z Uniolo 345 Added LUKS to the comparison. LUKS links to "Cryptsetup", at least for now. wikitext text/x-wiki [[Category:Software]] [[Category:Comparison]] The following is an '''objective''' comparison of open source encryption software. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes'''*''' |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |- |[[Cryptsetup|LUKS]] |Symmetric |Yes |No |To protect the data on a block device by encrypting it<ref name=":5" />. |} <div style="text-align: center;">'''*'''contents only, file names are not encrypted<ref name=":4" /></div> {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes<ref>{{Cite|url=https://www.linuxlinks.com/minisign-sign-files-verify-signatures/|title="Minisign – sign files and verify signatures"|author=Steve Emms|year=Feb 3, 2025|accessdate=2026-05-24}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |- |[[Cryptsetup|LUKS]] |256 bits<ref>{{Cite|url=https://blog.elcomsoft.com/2022/08/probing-linux-disk-encryption-luks2-argon-2-and-gpu-acceleration/|title=Probing Linux Disk Encryption: LUKS2, Argon 2 and GPU Acceleration|author=Oleg Afonin|year=Aug 16th, 2022|accessdate=2026-05-25}}</ref>, 512 bits<ref name=":5">{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":5" /><ref>{{Cite|url=https://pkg.go.dev/golang.org/x/crypto/twofish|title=Go "twofish" package|author=May 22, 2026|year=Twofish contributors|accessdate=2026-05-25}}</ref> |} <references /> 8fe2fd2e97f829eddce0bf92706cfe2ce5cea162 5306 5296 2026-05-25T12:33:07Z Madonuko 140 fix styling wikitext text/x-wiki [[Category:Software]] [[Category:Comparison]] This page provides comparisons of [[open source]] [[encryption]] [[software]]. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes'''*''' |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |- |[[Cryptsetup|LUKS]] |Symmetric |Yes |No |To protect the data on a block device by encrypting it<ref name=":5" />. |} <div style="text-align: center;">'''*'''contents only, file names are not encrypted<ref name=":4" /></div> {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes<ref>{{Cite|url=https://www.linuxlinks.com/minisign-sign-files-verify-signatures/|title="Minisign – sign files and verify signatures"|author=Steve Emms|year=Feb 3, 2025|accessdate=2026-05-24}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |- |[[Cryptsetup|LUKS]] |256 bits<ref>{{Cite|url=https://blog.elcomsoft.com/2022/08/probing-linux-disk-encryption-luks2-argon-2-and-gpu-acceleration/|title=Probing Linux Disk Encryption: LUKS2, Argon 2 and GPU Acceleration|author=Oleg Afonin|year=Aug 16th, 2022|accessdate=2026-05-25}}</ref>, 512 bits<ref name=":5">{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":5" /><ref>{{Cite|url=https://pkg.go.dev/golang.org/x/crypto/twofish|title=Go "twofish" package|author=May 22, 2026|year=Twofish contributors|accessdate=2026-05-25}}</ref> |} == References == <references /> 9adb10df5501e7dcf8c37f1e8dc627de73359cda 5307 5306 2026-05-25T12:35:12Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Comparison]] This page provides comparisons of [[open source]] [[encryption]] [[software]]. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes'''*''' |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |- |[[Cryptsetup|LUKS]] |Symmetric |Yes |No |To protect the data on a block device by encrypting it<ref name=":5" />. |} <div style="text-align: center;">'''*'''contents only, file names are not encrypted<ref name=":4" /></div> {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |No |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes<ref>{{Cite|url=https://www.linuxlinks.com/minisign-sign-files-verify-signatures/|title="Minisign – sign files and verify signatures"|author=Steve Emms|year=Feb 3, 2025|accessdate=2026-05-24}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |128 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |- |[[Cryptsetup|LUKS]] |256 bits<ref>{{Cite|url=https://blog.elcomsoft.com/2022/08/probing-linux-disk-encryption-luks2-argon-2-and-gpu-acceleration/|title=Probing Linux Disk Encryption: LUKS2, Argon 2 and GPU Acceleration|author=Oleg Afonin|year=Aug 16th, 2022|accessdate=2026-05-25}}</ref>, 512 bits<ref name=":5">{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":5" /><ref>{{Cite|url=https://pkg.go.dev/golang.org/x/crypto/twofish|title=Go "twofish" package|author=May 22, 2026|year=Twofish contributors|accessdate=2026-05-25}}</ref> |} == References == <references /> 0413e6e5ec3e6a565f9808bd5e8dab1ea015e2f9 5313 5307 2026-05-25T12:56:10Z Uniolo 345 Updated GnuPG info to be more accurate wikitext text/x-wiki [[Category:Software]] [[Category:Comparison]] This page provides comparisons of [[open source]] [[encryption]] [[software]]. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes'''*''' |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |- |[[Cryptsetup|LUKS]] |Symmetric |Yes |No |To protect the data on a block device by encrypting it<ref name=":5" />. |} <div style="text-align: center;">'''*'''contents only, file names are not encrypted<ref name=":4" /></div> {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |Yes<ref>{{Cite|url=https://gnupg.org/faq/whats-new-in-2.1.html|title=What’s new in GnuPG 2.1|author=GnuPG Project|year=2017|accessdate=2026-05-25}}</ref> |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes<ref>{{Cite|url=https://www.linuxlinks.com/minisign-sign-files-verify-signatures/|title="Minisign – sign files and verify signatures"|author=Steve Emms|year=Feb 3, 2025|accessdate=2026-05-24}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |128 bits, 192 bits, 256 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |- |[[Cryptsetup|LUKS]] |256 bits<ref>{{Cite|url=https://blog.elcomsoft.com/2022/08/probing-linux-disk-encryption-luks2-argon-2-and-gpu-acceleration/|title=Probing Linux Disk Encryption: LUKS2, Argon 2 and GPU Acceleration|author=Oleg Afonin|year=Aug 16th, 2022|accessdate=2026-05-25}}</ref>, 512 bits<ref name=":5">{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":5" /><ref>{{Cite|url=https://pkg.go.dev/golang.org/x/crypto/twofish|title=Go "twofish" package|author=May 22, 2026|year=Twofish contributors|accessdate=2026-05-25}}</ref> |} == References == <references /> 71146efc3b8f3501d2eb96c24d7c731a904718cf 5317 5313 2026-05-25T13:46:50Z Atmois 13 Atmois moved page [[Comparison of encryption software]] to [[User:Uniolo/Comparison of encryption software]] without leaving a redirect: Comparison page guidelines are in development wikitext text/x-wiki [[Category:Software]] [[Category:Comparison]] This page provides comparisons of [[open source]] [[encryption]] [[software]]. {| class="wikitable mw-collapsible" |+ General info !Name !Symmetric or Asymmetric !Encryption !Signatures !Stated purpose |- |[[Gnupg|GnuPG]] |Asymmetric and Symmetric |Yes |Yes |To encrypt and sign communications<ref>{{Cite|url=https://www.gnupg.org/|title=GnuPG Website|author=GnuPG Project|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Age]] |Asymmetric and Symmetric |Yes |No |To provide a simple, modern, and secure file encryption format<ref name=":2" />. |- |[[Minisign]] |Asymmetric |No |Yes |To be a dead simple tool to sign files and verify signatures<ref>{{Cite|url=https://jedisct1.github.io/minisign/|title=Minisign webpage|author=Frank Denis|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Gocryptfs]] |Symmetric |Yes |No |To be a encrypted overlay filesystem for Linux<ref>{{Cite|url=https://github.com/jedisct1/minisign|title=Minisign github|author=rfjakob|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Cryptomator]] |Symmetric |Yes |No |To encrypt files stored with cloud providers<ref>{{Cite|url=https://cryptomator.org/|title=Cryptomator website|author=Cryptomator maintainers|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[Zip]] |Symmetric |Yes'''*''' |No |The archiving of files and folders<ref>{{Cite|url=https://docs.fileformat.com/compression/zip/|title=fileformat.com Zip documentation|author=Unknown|year=Unknown|accessdate=2026-05-24}}</ref>. |- |[[7zip]] |Symmetric |Yes |No |To achieve a higher compression ratio then Zip<ref name=":3">{{Cite|url=https://www.7-zip.org/|title=7zip website|author=Igor Pavlov|year=2026|accessdate=2026-05-24}}</ref>. |- |[[Cryptsetup|LUKS]] |Symmetric |Yes |No |To protect the data on a block device by encrypting it<ref name=":5" />. |} <div style="text-align: center;">'''*'''contents only, file names are not encrypted<ref name=":4" /></div> {| class="wikitable mw-collapsible" |+Asymmetric Encryption Algorithms !Name !X25519 !RSA !ECC ![[wikipedia:Post-quantum_cryptography|PQ]] encryption !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |Yes<ref>{{Cite|url=https://gnupg.org/faq/whats-new-in-2.1.html|title=What’s new in GnuPG 2.1|author=GnuPG Project|year=2017|accessdate=2026-05-25}}</ref> |Yes<ref>{{Cite|url=https://www.gnupg.org/documentation/manuals/gpgme/Public-Key-Algorithms.html|title=GPGME Documentation|author=GPGME Contributors|year=Unknown|accessdate=2026-05-24}}</ref> |Yes<ref name=":0" /> |Kyber (aka ML-KEM)<ref>{{Cite|url=https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000504.html|title=GnuPG 2.5.19 released|author=Werner Koch|year=Apr 24, 2026|accessdate=2026-05-24}}</ref> |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |Yes<ref name=":1" /> |No |No |Yes<ref name=":2">{{Cite|url=https://github.com/FiloSottile/age|title=Github repo for the Go implementation of Age|author=FiloSottile|year=2026|accessdate=2026-05-24}}</ref> |No |- |[[Minisign]] |No |No |Yes<ref>{{Cite|url=https://www.linuxlinks.com/minisign-sign-files-verify-signatures/|title="Minisign – sign files and verify signatures"|author=Steve Emms|year=Feb 3, 2025|accessdate=2026-05-24}}</ref> |No |No |} {| class="wikitable mw-collapsible" |+Symmetric Encryption Algorithms !Name !AES !ChaCha20 !Supports deprecated/insecure algorithms |- |[[Gnupg|GnuPG]] |128 bits, 192 bits, 256 bits<ref name=":0">{{Cite|url=https://www.gnupg.org/documentation/manuals/gnupg24/gpg.1.html|title=GPG(1) manpage|author=Unknown|year=Unknown|accessdate=2026-06-24}}</ref> |No |Yes<ref name=":1">{{Cite|url=https://github.com/FiloSottile/age/discussions/432|title=Reply to "Age vs GPG"|author=cipriancraciun|year=Jul 20, 2022|accessdate=2026-05-24}}</ref> |- |[[Age]] |No |ChaCha20-Poly1305<ref name=":1" /> |No |- |[[Gocryptfs]] |128 and 512 bits<ref>{{Cite|url=https://defuse.ca/audits/gocryptfs.htm|title=Gocryptfs Security Audit|author=Defuse Computer Security R&D|year=Mar 3, 2017|accessdate=2026-05-24}}</ref> |No |No |- |[[Cryptomator]] |256 bits<ref>{{Cite|url=https://docs.cryptomator.org/security/architecture/|title=Cryptomator documentation, Security architecture|author=Cryptomator maintainers|year=Unknown|accessdate=(accessed 2026-05-24)}}</ref> |No |No |- |[[Zip]] |256 bits<ref name=":4">{{Cite|url=https://kb.winzip.com/en/130831|title=WinZip, "About Encryption"|author=Unknown|year=Jan 9, 2025|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":4" /> |- |[[7zip]] |256 bits<ref name=":3" /> |No |No |- |[[Cryptsetup|LUKS]] |256 bits<ref>{{Cite|url=https://blog.elcomsoft.com/2022/08/probing-linux-disk-encryption-luks2-argon-2-and-gpu-acceleration/|title=Probing Linux Disk Encryption: LUKS2, Argon 2 and GPU Acceleration|author=Oleg Afonin|year=Aug 16th, 2022|accessdate=2026-05-25}}</ref>, 512 bits<ref name=":5">{{Cite|url=https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening|title=Red Hat Documentation Chapter 9. Encrypting block devices using LUKS.|author=Red Hat|year=Unknown|accessdate=2026-05-24}}</ref> |No |Yes<ref name=":5" /><ref>{{Cite|url=https://pkg.go.dev/golang.org/x/crypto/twofish|title=Go "twofish" package|author=May 22, 2026|year=Twofish contributors|accessdate=2026-05-25}}</ref> |} == References == <references /> 71146efc3b8f3501d2eb96c24d7c731a904718cf 0 1228 5293 5202 2026-05-25T11:49:53Z Deviaze 341 move fetch scripts to top of page and fix heading level wikitext text/x-wiki [[Software]] for viewing system information. = Fetch scripts = Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} == Operating system information commands == Operating system information can be queried through the following commands: {| class="wikitable sortable" |+Kernel Information !Command !Purpose |- |uname |prints the kernel and the processor information |} == Hardware information commands == Hardware information can be queried through the following commands: {| class="wikitable sortable" |+All-in-One Hardware Information !Command !Purpose |- |dmidecode |Dumps the system's DMI (or SMBIOS) table |- |hwinfo |Provides detailed information on the hardware configuration of the machine |- |inxi |Provides detailed information on the hardware configuration of the machine |- |lshw |Provides detailed information on the hardware configuration of the machine |} {| class="wikitable sortable" |+CPU Information !Command !Purpose |- |arch |Prints the machine's architecture |- |lscpu |Lists detailed information about the CPU |- |cat /proc/cpuinfo |Reads a virtual read only text file that contains detailed information about machine's processor |} {| class="wikitable sortable" |+Memory Information !Command !Purpose |- |free |Displays total, used, and available physical RAM and swap space |- |cat /proc/meminfo |Provides detailed usage report about memory on system |} {| class="wikitable sortable" |+Storage, Disks, and Filesystems !Command !Purpose |- |fdisk -l |Lists all disk partitions, sizes, sector layouts, and partition table styles |- |hdparm |Set and view hardware parameters of hard disk drives |- |lsblk |Lists information about all available or specified block devices (like hard drives and SSDs) |- |nvme |Manage, configure, and monitor NVMe solid-state drives |- |smartctl |Controls and monitors S.M.A.R.T. data to check the physical health and self-test history of hard drives |} <references /> f9883af8c5096a52ae5e4210ed242aa618214cfb 5294 5293 2026-05-25T11:53:01Z Deviaze 341 add heading wikitext text/x-wiki [[Software]] for viewing system information. = Fetch scripts = Terminal scripts that display system information like operating system, CPU, RAM, GPU, what DE/WM is installed, etc. {| class="wikitable" !Name !External links !Description |- |[[Fastfetch]] |[https://github.com/fastfetch-cli/fastfetch GitHub] |Fastfetch is is a fetch fetch script similar to Neofetch, but faster. |- |[[Hyfetch]] |[https://github.com/hykilpikonna/hyfetch GitHub] |Hyfetch is an actively developed fork of Neofetch with pride colors |- |[[Neofetch]] |[https://github.com/dylanaraps/neofetch GitHub] |Neofetch is a now unmaintained fetch script for displaying system information. |} = Terminal commands = Common terminal commands to view information about software and hardware info. == Operating system information commands == Operating system information can be queried through the following commands: {| class="wikitable sortable" |+Kernel Information !Command !Purpose |- |uname |prints the kernel and the processor information |} == Hardware information commands == Hardware information can be queried through the following commands: {| class="wikitable sortable" |+All-in-One Hardware Information !Command !Purpose |- |dmidecode |Dumps the system's DMI (or SMBIOS) table |- |hwinfo |Provides detailed information on the hardware configuration of the machine |- |inxi |Provides detailed information on the hardware configuration of the machine |- |lshw |Provides detailed information on the hardware configuration of the machine |} {| class="wikitable sortable" |+CPU Information !Command !Purpose |- |arch |Prints the machine's architecture |- |lscpu |Lists detailed information about the CPU |- |cat /proc/cpuinfo |Reads a virtual read only text file that contains detailed information about machine's processor |} {| class="wikitable sortable" |+Memory Information !Command !Purpose |- |free |Displays total, used, and available physical RAM and swap space |- |cat /proc/meminfo |Provides detailed usage report about memory on system |} {| class="wikitable sortable" |+Storage, Disks, and Filesystems !Command !Purpose |- |fdisk -l |Lists all disk partitions, sizes, sector layouts, and partition table styles |- |hdparm |Set and view hardware parameters of hard disk drives |- |lsblk |Lists information about all available or specified block devices (like hard drives and SSDs) |- |nvme |Manage, configure, and monitor NVMe solid-state drives |- |smartctl |Controls and monitors S.M.A.R.T. data to check the physical health and self-test history of hard drives |} <references /> 6d6ee252a7ba2aaeec6644032bd6e693d59a5a0c 0 396 5295 5204 2026-05-25T11:55:51Z Deviaze 341 /* System */ add Hardware maintenance category wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package Managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' File managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. These are the most common file managers: {| class="wikitable" !Name !External links !Description !DE |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |[[Plasma|KDE Plasma]] |- |Thunar |[https://docs.xfce.org/xfce/thunar/start Xfce] |Thunar is [[Xfce]]'s modern file manager, desgined from the group up for speed and friendliness. |[[Xfce]] |- |} == System Resource Monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. == Hardware Maintenance == '''See the main page: [[Hardware Maintenance]]''' These are GUI and TUI programs that check the current health and utilization of hardware components such as your SSD/HDDs and battery. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp GitHub] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Media = '''See the main page: [[Media]]''' == Art, 2D, and 3D media editing == '''See the main page: [[Media Editing]]''' Includes software primarily meant for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation, etc. == Music and Audio == '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. e101d0c7c286d4b9d240363f0be569c73ed6e91f 0 1237 5297 2026-05-25T11:59:15Z Brochard 351 Start of an Hardware page wikitext text/x-wiki {{Stub}} Hardware includes every physical part of a computer or electronic system you can touch. This page is dedicated to listing common and widely recommended FOSS supporting hardware. {| class="wikitable" !Name !External links !Description !Hardware !Country |- |[[Fairphone]] |[https://www.fairphone.com Website] |Repairable and upgradable hardware company |Phones, Peripherals |The Netherlands |- |[[Framework]] |[https://frame.work/ Website] |Repairable and upgradable hardware company |Desktops, Laptops, Peripherals |USA, California |- |[[LaptopWithLinux]] |[https://laptopwithlinux.com/ Website] |Hardware shipping with Linux |Desktops, Laptops |The Netherlands |- |[[Nitrokey]] |[https://www.nitrokey.com/ Website] |Security forcused hardware |Desktop, Laptops, Phones, Peripherals |Germany |- |[[Pine64]] |[https://pine64.org/ Website] |Hardware for open source tinkerers |Laptops, Phones, Single Board Computers, Others |Hong Kong |- |[[Purism]] |[https://puri.sm/ Website] |Linux hardware shipping with their own Linux Distro [[PureOS]] |Desktops, Laptops, Phones, Peripherals$ |USA, California |- |[[Slimbook]] |[https://slimbook.com/ Website] |Hardware shipping with Linux |Desktops, Laptops |Spain |- |[[Starlabs]] |[https://starlabs.systems/ Website] |Hardware shipping with Linux |Desktops, Laptops |United Kingdom |- |[[System76]] |[https://system76.com/ Website] |Linux hardware shipping their own Linux Distro [[Pop!_OS]] |Desktops, Laptops, Peripherals |USA, Colorado |- |[[TUXEDO Computers]] |[https://www.tuxedocomputers.com Website] |Linux hardware shipping with their own Linux Distro [[TUXEDO OS]] |Desktops, Laptops, Peripherals |Germany |} 5cb44dd21ad536f6ca029269cb760b0c4688677d 5299 5297 2026-05-25T12:05:42Z Brochard 351 Add companies title wikitext text/x-wiki {{Stub}} Hardware includes every physical part of a computer or electronic system you can touch. This page is dedicated to listing common and widely recommended FOSS supporting hardware. == Companies == {| class="wikitable" !Name !External links !Description !Hardware !Country |- |[[Fairphone]] |[https://www.fairphone.com Website] |Repairable and upgradable hardware company |Phones, Peripherals |The Netherlands |- |[[Framework]] |[https://frame.work/ Website] |Repairable and upgradable hardware company |Desktops, Laptops, Peripherals |USA, California |- |[[LaptopWithLinux]] |[https://laptopwithlinux.com/ Website] |Hardware shipping with Linux |Desktops, Laptops |The Netherlands |- |[[Nitrokey]] |[https://www.nitrokey.com/ Website] |Security forcused hardware |Desktop, Laptops, Phones, Peripherals |Germany |- |[[Pine64]] |[https://pine64.org/ Website] |Hardware for open source tinkerers |Laptops, Phones, Single Board Computers, Others |Hong Kong |- |[[Purism]] |[https://puri.sm/ Website] |Linux hardware shipping with their own Linux Distro [[PureOS]] |Desktops, Laptops, Phones, Peripherals$ |USA, California |- |[[Slimbook]] |[https://slimbook.com/ Website] |Hardware shipping with Linux |Desktops, Laptops |Spain |- |[[Starlabs]] |[https://starlabs.systems/ Website] |Hardware shipping with Linux |Desktops, Laptops |United Kingdom |- |[[System76]] |[https://system76.com/ Website] |Linux hardware shipping their own Linux Distro [[Pop!_OS]] |Desktops, Laptops, Peripherals |USA, Colorado |- |[[TUXEDO Computers]] |[https://www.tuxedocomputers.com Website] |Linux hardware shipping with their own Linux Distro [[TUXEDO OS]] |Desktops, Laptops, Peripherals |Germany |} 8cc0061baf979ea704dfbb88f187af397bba0b27 0 1238 5298 2026-05-25T12:05:07Z Deviaze 341 Create page with system hardware maintenance/health utilities wikitext text/x-wiki = SSDs = {| class="wikitable" !Name !External links !Description |- |QDiskInfo |[https://github.com/edisionnano/QDiskInfo GitHub], [https://fostips.com/crystaldiskinfo-alternative-linux/ FOSTips Guide] |Monitor your HDD and SSD health; a Linux alternative to CrystalDiskInfo. Frontend to <code>smartctl</code>. |} = Battery = {| class="wikitable" !Name !External links !Description |- |battop |[https://github.com/svartalf/rust-battop GitHub] |TUI interactive battery info & health viewer. |} 845f319df4cfecccacbd4d6d87e280e8cd64c958 5300 5298 2026-05-25T12:06:01Z Deviaze 341 forgot to put [[Software]] backlink on top wikitext text/x-wiki [[Software]] for keeping track of device health and utilization. = SSDs = {| class="wikitable" !Name !External links !Description |- |QDiskInfo |[https://github.com/edisionnano/QDiskInfo GitHub], [https://fostips.com/crystaldiskinfo-alternative-linux/ FOSTips Guide] |Monitor your HDD and SSD health; a Linux alternative to CrystalDiskInfo. Frontend to <code>smartctl</code>. |} = Battery = {| class="wikitable" !Name !External links !Description |- |battop |[https://github.com/svartalf/rust-battop GitHub] |TUI interactive battery info & health viewer. |} 84803a4232a82fc3da66350a836ba64ec7a0d17d 5303 5300 2026-05-25T12:27:09Z Uniolo 345 Added smartctl wikitext text/x-wiki [[Software]] for keeping track of device health and utilization. = SSDs = {| class="wikitable" !Name !External links !Description |- |QDiskInfo |[https://github.com/edisionnano/QDiskInfo GitHub], [https://fostips.com/crystaldiskinfo-alternative-linux/ FOSTips Guide] |Monitor your HDD and SSD health; a Linux alternative to CrystalDiskInfo. Frontend to <code>smartctl</code>. |- |[[Smartctl]] |[https://github.com/smartmontools/smartmontools GitHub], [https://www.smartmontools.org/wiki smartmontools.org] |CLI tool for checking the health of a drive. |} = Battery = {| class="wikitable" !Name !External links !Description |- |battop |[https://github.com/svartalf/rust-battop GitHub] |TUI interactive battery info & health viewer. |} e89cb144f0ea46fbf11bc7bc6ed3b3cb8cf15249 6 1239 5301 2026-05-25T12:18:24Z Brochard 351 wikitext text/x-wiki The logo of Redox OS ffddab42a3f50c9557c6038b431ce21c7887cb89 0 1240 5302 2026-05-25T12:23:30Z Uniolo 345 Create smartctl with basic info, basic usage, and a sidebar. wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |title=Smartctl |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=Oct 2002 |languages=[[C++]], [[C]] |developers=Bruce Allen |website=[https://www.smartmontools.org/ www.smartmontools.org] }} '''Smartctl''' is a command included in many Linux distributions for checking the health of storage devices. It is part of [[Smartmontools|smartmontools]] and should be used regularly to check the status and health of drives to avoid unexpected corruption possibly resulting in data loss or other unexpected issues. ==== Basic Usage ==== Smartctl can be used to check the health of a drive with <code>smartctl -H /dev/<drive></code><ref name=":0">{{Cite|url=https://man.archlinux.org/man/smartctl.8|title=SMARTCTL(8)|author=Manpages|year=Unknown|accessdate=2026-05-25}}</ref>. More complex info can be attained by running <code>smartctl -x /dev/nvme0n1</code> which lists all SMART and non-SMART info about the device<ref name=":0" />. [[Category:Software]] 7d5da81fc619fe8a89fe32ba7d85a8d21e5a9538 5304 5302 2026-05-25T12:27:57Z Uniolo 345 Add "Guide Warning" as per guidelines wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |title=Smartctl |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=Oct 2002 |languages=[[C++]], [[C]] |developers=Bruce Allen |website=[https://www.smartmontools.org/ www.smartmontools.org] }} '''Smartctl''' is a command included in many Linux distributions for checking the health of storage devices. It is part of [[Smartmontools|smartmontools]] and should be used regularly to check the status and health of drives to avoid unexpected corruption possibly resulting in data loss or other unexpected issues. ==== Basic Usage ==== {{Guide Warning}} Smartctl can be used to check the health of a drive with <code>smartctl -H /dev/<drive></code><ref name=":0">{{Cite|url=https://man.archlinux.org/man/smartctl.8|title=SMARTCTL(8)|author=Manpages|year=Unknown|accessdate=2026-05-25}}</ref>. More complex info can be attained by running <code>smartctl -x /dev/nvme0n1</code> which lists all SMART and non-SMART info about the device<ref name=":0" />. [[Category:Software]] 06ba072c96993ce8128cedea187711c3d9a41a3a 5309 5304 2026-05-25T12:35:32Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox |title=Smartctl |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=Oct 2002 |languages=[[C++]], [[C]] |developers=Bruce Allen |website=[https://www.smartmontools.org/ www.smartmontools.org] }} '''Smartctl''' is a command included in many Linux distributions for checking the health of storage devices. It is part of [[Smartmontools|smartmontools]] and should be used regularly to check the status and health of drives to avoid unexpected corruption possibly resulting in data loss or other unexpected issues. == Basic Usage == {{Guide Warning}} Smartctl can be used to check the health of a drive with <code>smartctl -H /dev/<drive></code><ref name=":0">{{Cite|url=https://man.archlinux.org/man/smartctl.8|title=SMARTCTL(8)|author=Manpages|year=Unknown|accessdate=2026-05-25}}</ref>. More complex info can be attained by running <code>smartctl -x /dev/nvme0n1</code> which lists all SMART and non-SMART info about the device<ref name=":0" />. f5a1566a7aaa0ffc6e5cf4a98d45f5cd8625bf62 5310 5309 2026-05-25T12:37:01Z Madonuko 140 fix styling wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox |title=Smartctl |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=Oct 2002 |languages=[[C++]], [[C]] |developers=Bruce Allen |website=[https://www.smartmontools.org/ www.smartmontools.org] }} '''Smartctl''' is a command included in many Linux distributions for checking the health of storage devices. It is part of [[smartmontools]] and should be used regularly to check the status and health of drives to avoid unexpected corruption possibly resulting in data loss or other unexpected issues. == Basic Usage == {{Guide Warning}} Smartctl can be used to check the health of a drive with <code>smartctl -H /dev/<drive></code><ref name=":0">{{Cite|url=https://man.archlinux.org/man/smartctl.8|title=SMARTCTL(8)|author=Manpages|year=Unknown|accessdate=2026-05-25}}</ref>. Additionally, <code>smartctl -x /dev/nvme0n1</code> lists all [[SMART]] and non-SMART info about the device<ref name=":0" />. == References == 4883df2122a578d2f414b267e39e16550370d615 5311 5310 2026-05-25T12:38:49Z Madonuko 140 fix links and ref wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox |title=Smartctl |releasestatus=Maintained |lastrelease=9.2, Feb 14, 2026 |firstrelease=Oct 2002 |languages=[[C++]], [[C]] |developers=Bruce Allen |website=[https://www.smartmontools.org/ www.smartmontools.org] }} '''Smartctl''' is a command included in many [[Linux distributions]] for checking the health of [[storage]] devices. It is part of [[smartmontools]] and should be used regularly to check the status and health of drives to avoid unexpected corruption possibly resulting in data loss or other unexpected issues. == Basic Usage == {{Guide Warning}} Smartctl can be used to check the health of a drive with <code>smartctl -H /dev/<drive></code><ref name=":0">{{Cite|url=https://man.archlinux.org/man/smartctl.8|title=smartctl(8)|author=Arch manual pages|year=2025|accessdate=2026-05-25}}</ref>. Additionally, <code>smartctl -x /dev/nvme0n1</code> lists all [[SMART]] and non-SMART info about the device<ref name=":0" />. == References == 407607bc9da362f46453d223f61739489c07171c 0 1241 5305 2026-05-25T12:28:46Z Brochard 351 Start of Redox OS wiki wikitext text/x-wiki [[Category:Misc Operating Systems]] {{Stub}} {{DistributionInfobox | architectures = arm, aarch64, i486, x86_64 | caption = The Redox OS logo | defaultdesktops = Orbital | image = [[File:The Redox OS logo.png|thumb|The Redox OS Logo]] | packagemanager = pkg | releasemodel = In development | releasestatus = In development | title = Redox OS | usagetype = Desktop, Server | website = [https://redox-os.org/ redox-os.org] }} Redox OS is a general-purpose [[Operating System|operating system]] written in [[Rust]]. It aims to provide a fully functioning [[UNIX|Unix]]-like microkernel-based operating system, that is secure, reliable and free. It takes inspiration from [[Plan 9]], [[Minix]], [[seL4]], [[Linux]], [[OpenBSD]] and [[FreeBSD]].<ref>[https://doc.redox-os.org/book/ The Redox OS book]</ref> == References == <references /> a5319342082dfc892867d4e6fb949ed21da76fcc 5308 5305 2026-05-25T12:35:22Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Misc Operating Systems]] {{Stub}} {{DistributionInfobox | architectures = arm, aarch64, i486, x86_64 | caption = The Redox OS logo | defaultdesktops = Orbital | image = [[File:The Redox OS logo.png|thumb|The Redox OS Logo]] | packagemanager = pkg | releasemodel = In development | releasestatus = In development | title = Redox OS | usagetype = Desktop, Server | website = [https://redox-os.org/ redox-os.org] }} Redox OS is a general-purpose [[Operating System|operating system]] written in [[Rust]]. It aims to provide a fully functioning [[UNIX|Unix]]-like microkernel-based operating system, that is secure, reliable and free. It takes inspiration from [[Plan 9]], [[Minix]], [[seL4]], [[Linux]], [[OpenBSD]] and [[FreeBSD]].<ref>[https://doc.redox-os.org/book/ The Redox OS book]</ref> == References == <references /> 093d1249d3ee8b8d498898839e151b66a685461e 0 1233 5312 5192 2026-05-25T12:53:09Z Brochard 351 Add Bevy game engine wikitext text/x-wiki This article includes gaming-related [[software]], utilities, tweaks, and free and open-source games. == Engines == {| class="wikitable" !Name !External links !Description |- |[[Bevy]] |[https://bevy.org/ Website], [https://github.com/bevyengine/bevy GitHub] |Data-driven 2D and 3D game engine built in [[Rust]] |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} 1f0e9872b531d7fe45fb26cb44d603e55a0b0750 5314 5312 2026-05-25T13:02:27Z Brochard 351 Add game launchers section wikitext text/x-wiki This article includes gaming-related [[software]], utilities, tweaks, and free and open-source games. == Engines == {| class="wikitable" !Name !External links !Description |- |[[Bevy]] |[https://bevy.org/ Website], [https://github.com/bevyengine/bevy GitHub] |Data-driven 2D and 3D game engine built in [[Rust]] |- |[[Godot]] |[https://godotengine.org/ Website], [https://github.com/godotengine GitHub] |2D and 3D game engine packed with features. |} === Aim trainers === {| class="wikitable" !Name !External links !Description |- |[[LibreAim]] |[https://codeberg.org/Nokorpo/LibreAim Codeberg] |First-person shooter aim trainer. |} === Compatibility tools === {| class="wikitable" !Name !External links !Description |- |[[ProtonPlus]] |[https://protonplus.vysp3r.com/ Website], [https://github.com/Vysp3r/protonplus GitHub] |GTK4-based graphical utility for installing and managing community Proton builds. |- |[[ProtonUp-Qt]] |[https://davidotek.github.io/protonup-qt/ Website], [https://github.com/DavidoTek/ProtonUp-Qt GitHub] |Qt-based graphical utility for downloading and updating community Proton builds. |} === Game launchers === {| class="wikitable" !Name !External links !Description |- |[[Heroic]] |[https://heroicgameslauncher.com/ Website], [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher GitHub] |Game launcher for Epic Game Store, GOG and Amazon games |- |[[Lutris]] |[https://lutris.net/ Website], [https://lutris.net/ GitHub] |Game launcher for games of all eras |} === Gaming utilities === {| class="wikitable" !Name !External links !Description |- |[[MangoHud]] |[https://mangohud.org/ Website], [https://github.com/flightlessmango/MangoHud GitHub] |Performance monitoring overlay for Vulkan and OpenGL applications. |- |[[GOverlay]] |[https://github.com/benjamimgois/goverlay GitHub] |Graphical interface for configuring MangoHud and vkBasalt. |- |[[Piper]] |[https://github.com/libratbag/piper GitHub] |GTK graphical user interface for configuring gaming mouse DPI and buttons |} f893737793e7dcffc3d2f6a8a35387bfa39c376f 0 1232 5315 5191 2026-05-25T13:04:58Z Uniolo 345 Corrected capitalization in "Terminal-based editors" section wikitext text/x-wiki Commonly-used free and open source text editing [[software]] on [[Linux]]. = Text editors = {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |} == Terminal-based text editors == These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[Nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[Vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[Vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[Neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[Helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |} = Integrated development environments (IDEs) = IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} 815262b02b46aeb2b3035fb31334abcc022ec2c7 4 876 5316 4613 2026-05-25T13:17:53Z Atmois 13 Update key path wikitext text/x-wiki == Security at FOSS Wiki == At FOSS Wiki, we are committed to maintaining the highest security standards to protect our community and infrastructure. We deeply value the security research community and actively encourage responsible disclosure of security vulnerabilities. Your contributions help us ensure the safety, privacy, and integrity of our platforms and services. We believe in transparency and collaboration when it comes to security. Our team is dedicated to investigating all reported issues promptly and working with researchers to address vulnerabilities in a timely and responsible manner. === Scope === This security policy applies to all FOSS Wiki projects and services, including but not limited to: * Our domains and all of its subdomains: '''foss.wiki''' * API endpoints, back-end services, Discord bot services or integrations, and community platforms or forums * Repositories within the FOSS Wiki GitHub/Codeberg organisation We are interested in any vulnerability that could lead to unauthorised access, data breaches, or service disruptions. We welcome any reports of potential vulnerabilities outside of this scope but we may not be able to address them immediately. Please also note that we also host and utilise external services, we also welcome reports regarding those services but we may not be able to address them directly and will refer you to the appropriate party. === How to Report a Security Issue === If you have discovered a security vulnerability, please help us keep our community safe by reporting it responsibly. When reporting, please include: * A clear description of the vulnerability and its potential impact * Detailed steps to reproduce the issue * Information about the environment where you discovered the issue * Any proof-of-concept code or evidence of the vulnerability (if applicable) * Any recommendations or patches you may have for resolving the issue === Contact === All reports should be directed to our email, [mailto:security@foss.wiki security@foss.wiki] and if required, using the GPG key found at https://foss.wiki/security-at-fosswiki_public.asc Alternatively, you may open a ticket with <code>/ticket</code> in our [https://discord.foss.wiki Discord server] and request assistance there. '''Please do not disclose''' '''vulnerability details in the ticket unless requested by an administrator.''' === Responsible Disclosure Guidelines === We require that you: * Do not make use of any vulnerabilities without explicit permission to do so from a member of Wiki Leadership * Do not access, copy, or destroy data that is not available without authentication/authorisation in any capacity * Do not disrupt our services or degrade the performance of our services * Keep vulnerability details confidential until we have addressed the issue and agreed to a planned disclosure * Give us reasonable time (typically 30 days, although you will be informed of the estimated time) to investigate and resolve the issue === Safe Harbour === Any activities conducted in a manner consistent with this policy will be considered authorised conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will ensure it is known that your actions were conducted in compliance with this policy. === Recognition === We appreciate security researchers and individuals who help keep our community safe. If you would like to be acknowledged for your responsible disclosure, please let us know in your report and we'll be happy to recognise your contribution publicly. However, please note we do not have the ability to award bug bounties or monetary reward for any disclosed vulnerabilities due to the nature of the project. We also welcome you to post your own report and/or analysis once we have resolved and disclosed the vulnerability publicly ourselves, '''we only request you send it to us 1 week before you plan to publish it.''' 6be87f83c0dd8d3bf28b3f2496c17f41ba930651 0 1234 5318 5198 2026-05-25T13:47:34Z Uniolo 345 wikitext text/x-wiki [[Software]] including password manages, VPN services/providers, encryption, and similar. = Virtual Private Machine (VPN) = VPN software is used to anonymize who you are on the internet and prevent tracking. {| class="wikitable" !Name !External links !Description !Open source? |- |ProtonVPN |[https://protonvpn.com/ Website], [https://github.com/ProtonVPN GitHub] |A commercial VPN software with Linux support. |Partially |} = Password managers = {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} = Encryption = {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} cd977ba126d418cb8bc2a3b963f130f4bd519b6b 8 538 5319 4625 2026-05-25T13:49:20Z Atmois 13 Fix title wikitext text/x-wiki '''FOSS Wiki has launched!''' Check out our [https://discord.foss.wiki Discord Server] to get updates on the wiki and see what we are up to. 5ea77f1ad42b86543f63e7b2341c575440d4315b 0 1234 5320 5318 2026-05-25T14:13:09Z Brochard 351 fix VPN wikitext text/x-wiki [[Software]] including password manages, VPN services/providers, encryption, and similar. = Virtual Private Network (VPN) = VPN software is used to anonymize who you are on the internet and prevent tracking. {| class="wikitable" !Name !External links !Description !Open source? |- |ProtonVPN |[https://protonvpn.com/ Website], [https://github.com/ProtonVPN GitHub] |A commercial VPN software with Linux support. |Partially |} = Password managers = {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} = Encryption = {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} f57fa3056a1658b66349830de345c8663b6bca54 0 198 5321 5215 2026-05-25T14:21:20Z Brochard 351 Add Vanilla OS in Debian family wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distribution primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == d77cdfd3be72e26145b100c560f80ca59a03d741 5324 5321 2026-05-25T15:59:49Z Sedot 397 /* openSUSE Family */ wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == baf92109b6af7e25ebc420c9bfdd2ac7eedd6a44 5336 5324 2026-05-25T17:54:34Z Birdie 363 /* Fedora Family */ wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 2165c842a23abe69293ace1a6f2650d0e31b6137 5337 5336 2026-05-25T17:55:21Z Birdie 363 Undo revision [[Special:Diff/5336|5336]] by [[Special:Contributions/Birdie|Birdie]] ([[User talk:Birdie|talk]]) wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == baf92109b6af7e25ebc420c9bfdd2ac7eedd6a44 5338 5337 2026-05-25T17:55:50Z Birdie 363 /* Fedora Family */ Added Nobara Linux to the Fedora Family section. wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 2165c842a23abe69293ace1a6f2650d0e31b6137 1 1242 5322 2026-05-25T14:55:10Z Nathan22211 360 /* possibly mention this (if we find a source on it) */ new section wikitext text/x-wiki == possibly mention this (if we find a source on it) == I've heard reports that Cinnamon has a long standing memory leak with it, though I've never been able to find an article on the matter that confirms or disproves it. [[User:Nathan22211|Nathan22211]] ([[User talk:Nathan22211|talk]]) 14:55, 25 May 2026 (UTC) 33695c38bca01f8421c0a7ba82c7ccb28b82a11a 828 204 5323 5285 2026-05-25T15:59:16Z Madonuko 140 fix invocation for addRow (sourcecode) Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage(args.image, args.caption) end retval:addRow('Release Status', args.releasestatus) retval:addRow('Last Release', args.lastrelease) if args.firstrelease and args.firstrelease ~= '' then retval:addRow('First Release', args.firstrelease) end retval:addRow('Language(s)', args.languages) retval:addRow('Developer(s)', args.developers) retval:addRow('Website', args.website) if args.license then retval:addRow('License', args.license) end if args.sourcecode then retval:addRow('Source Code', args.sourcecode) end return retval end return p 2bae55e859074f4194f8eb4bcbe9177abacc2348 0 1120 5325 5280 2026-05-25T16:00:55Z Uniolo 345 Added license and source code fields wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox | image = [[File:Vimlogo.svg|thumb]] | caption = Vim | title = Vim | releasestatus = Maintained | lastrelease = 9.2, Feb 14, 2026 | firstrelease = 1.14, Jan, 1992 | languages = [[C]], [[Vim Script]] | developers = [https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] | website = [https://www.vim.org/ vim.org] | license = Vim License | sourcecode = https://github.com/vim/vim }} [[Category:Software]] [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ''Also see: [[GNU Emacs|Emacs]].'' ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. == References == <references /> 3547b68fbc9b7819e477bb5621aa37f16e694a5d 5347 5325 2026-05-25T20:52:54Z Uniolo 345 Removed stub from Vim, pretty complete now wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Vimlogo.svg|thumb]] | caption = Vim | title = Vim | releasestatus = Maintained | lastrelease = 9.2, Feb 14, 2026 | firstrelease = 1.14, Jan, 1992 | languages = [[C]], [[Vim Script]] | developers = [https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] | website = [https://www.vim.org/ vim.org] | license = Vim License | sourcecode = https://github.com/vim/vim }} [[Category:Software]] [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. While [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer, he is not the only one, a list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ''Also see: [[GNU Emacs|Emacs]].'' ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. == References == <references /> f98490668eec110019f068a2002beec76cd2d3e3 5350 5347 2026-05-25T21:05:13Z Uniolo 345 Listed that Bram Moolenaarpassed away wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Vimlogo.svg|thumb]] | caption = Vim | title = Vim | releasestatus = Maintained | lastrelease = 9.2, Feb 14, 2026 | firstrelease = 1.14, Jan, 1992 | languages = [[C]], [[Vim Script]] | developers = [https://en.wikipedia.org/wiki/Bram_Moolenaar Bram Moolenaar] | website = [https://www.vim.org/ vim.org] | license = Vim License | sourcecode = https://github.com/vim/vim }} [[Category:Software]] [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer and has since past away in August of 2023<ref>{{Cite|url=https://groups.google.com/g/vim_announce/c/tWahca9zkt4?pli=1|title=Message from the family of Bram Moolenaar, Vim mailing list|author=Bram Moolenaar|year=Aug 5, 2023|accessdate=2026-05-25}}</ref>. A list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ''Also see: [[GNU Emacs|Emacs]].'' ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. == References == <references /> 8bc20b77bcca0615b5fee362a7daab92175ea6a7 5351 5350 2026-05-25T21:06:08Z Uniolo 345 Changed maintainer in sidebar to current lead mainaitner wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Vimlogo.svg|thumb]] | caption = Vim | title = Vim | releasestatus = Maintained | lastrelease = 9.2, Feb 14, 2026 | firstrelease = 1.14, Jan, 1992 | languages = [[C]], [[Vim Script]] | developers = [https://github.com/chrisbra/ Christian Brabandt] | website = [https://www.vim.org/ vim.org] | license = Vim License | sourcecode = https://github.com/vim/vim }} [[Category:Software]] [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer and has since past away in August of 2023<ref>{{Cite|url=https://groups.google.com/g/vim_announce/c/tWahca9zkt4?pli=1|title=Message from the family of Bram Moolenaar, Vim mailing list|author=Bram Moolenaar|year=Aug 5, 2023|accessdate=2026-05-25}}</ref>. A list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ''Also see: [[GNU Emacs|Emacs]].'' ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. == References == <references /> a660f3efbb1de9eb59c375cf106289b3c7938537 0 1190 5326 5249 2026-05-25T16:03:28Z Uniolo 345 Add license to sidebar wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] |license=GPL-3.0-or-later }} [[Category:Software]] [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many [[Linux Distributions|Linux distributions]] and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or messages to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a sender's public key, the legitimacy of a message. GnuPG is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. Due to GnuPG supporting many old and deprecated algorithms and many UX mistakes, many users advise moving towards the more modern [[Age]] for encryption<ref>{{Cite|url=https://sumguy.com/age-vs-gpg-modern-encryption/|title=age vs GPG: Modern File Encryption That Doesn't Make You Cry|author=SumGuy|year=May 26, 2026|accessdate=2026-05-23}}</ref>. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] is needed. <references /> 7f7ce9fbaad7d482ef5b24a27fee2ea2f5d59834 5332 5326 2026-05-25T16:38:49Z Uniolo 345 Added note that SSH is also used to sign commits wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] |license=GPL-3.0-or-later }} [[Category:Software]] [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many [[Linux Distributions|Linux distributions]] and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or messages to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a sender's public key, the legitimacy of a message. GnuPG and [[SSH]] is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. Due to GnuPG supporting many old and deprecated algorithms and many UX mistakes, many users advise moving towards the more modern [[Age]] for encryption<ref>{{Cite|url=https://sumguy.com/age-vs-gpg-modern-encryption/|title=age vs GPG: Modern File Encryption That Doesn't Make You Cry|author=SumGuy|year=May 26, 2026|accessdate=2026-05-23}}</ref>. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] is needed. <references /> 70ebd151a4b1272f66dcb8b62131d7d19301a4fa 0 1222 5327 5213 2026-05-25T16:04:59Z Uniolo 345 Add license field to sidebar wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox | image = [[File:Yt-dlp logo.svg|thumb]] | caption = yt-dlp | title = Vim | releasestatus = Maintained | lastrelease = 2026.03.17, 2026-03-17 | firstrelease = 2021.01.07, 2021-01-07 | languages = [[Python]] | developers = [https://github.com/orgs/yt-dlp/people yt-dlp maintainers] | website = [https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] | license = Unlicense }} '''yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. == Usage tips == {{Guide_Warning}} yt-dlp has many options, like [https://sponsor.ajay.app/ sponsorblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users may like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from a nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> to get a [[Manpages|manpage]] entry, or by using an online manpage such as [https://man.archlinux.org/man/yt-dlp.1 the archlinux online manpages]. Some of the most commonly used options are the <code>-o <output></code> to specify and output, and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> 0fd177a5d39937851cb486f6cba4ca52d2273a8e 0 1143 5328 5265 2026-05-25T16:06:05Z Uniolo 345 Added license field to sidebar wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | image = [[File:Neovim-mark.svg|thumb]] | caption = NeoVim | title = NeoVim | releasestatus = Maintained | lastrelease = 0.12.2, Apr 22, 2026 | firstrelease = 0.15, Aug 23, 2016 | languages = [[C]], [[Lua]], [[Vim Script]] | developers = Thiago de Arruda | website = [https://neovim.io/ neovim.io] | license = Apache 2.0 }} [[Category:Software]] [[File:Nevom-Splash.png|thumb|The Neovim 0.12.2 splash screen.]] '''Neovim''' (also known as '''nvim''') is a configurable terminal text editor for Linux, Windows, and macOS. It is configured in [[Lua]]. Neovim is based on [[Vim]]<ref>{{Cite|url=https://github.com/neovim/neovim/commit/9f13983de280c53971a8997ead0d6e9d4e3d3e42|title=Commit 9f13983, "vim-patch:7.4.2185"|author=lonerover|year=2017-03-11|accessdate=2026-05-23}}</ref>. Neovim is fully compatible with Vim's editing modal and [[Vim Script]]<ref>[https://neovim.io/ Neovim website] (accessed 2026-05-22)</ref>, and part of Neovim is written in [[Vim Script]]<ref>{{Cite|url=https://github.com/neovim/neovim|title=Neovim GIthub|author=[https://github.com/orgs/neovim/people Neovim Contributors]|year=2026-05-23|accessdate=2026-05-23}}</ref>. Like [[Vim]], Neovim can also be considered [[wikipedia:Careware|Charityware]] due to encouraging users to donate to [https://www.kuwasha.net/ Kuwasha]. <references /> 3d6677e19e9d0da80b18454c27e5b45ac700636c 0 279 5329 4396 2026-05-25T16:21:14Z Sedot 397 /* Versions */ reorganized and hopefully explained the distributions well enough. wikitext text/x-wiki == Versions == OpenSUSE stands out by having variations of the distributions: === Tumbleweed === Tumbleweed is the Rolling Release Distribution containing the latest [[openQA|openQA]] testet versions of all software. Tumbleweed is based on Factory, openSUSEs main development codebase, As soon as a openQA tests pass, a new Tumbleweed snapshot will be released – typically several times a week. === Slowroll === Please note, Slowroll is in beta stage. Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === Leap === Leap is the point release version, with a new release every year with older and more stable packages meant for business use. === Kalpa === Please note, Kalpa is in alpha stage. Kalpa is an atomic and transactional Linux desktop offering the KDE Plasma Desktop Environment. It's goal is to be easy to use and for people who "want to be stuff done" whitout messing with their operating system. Kalpa is based on Tumbleweed and MicroOS. === MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed f5b0da1b3f9bec19ff8d161da777a3798d55f956 5330 5329 2026-05-25T16:27:34Z Sedot 397 wikitext text/x-wiki openSUSE[5] ( /ˌoʊpənˈsuːzə/) are free and open-source Linux distributions developed by the openSUSE Project and SUSE S.A. == Versions == OpenSUSE stands out by having variations of the distributions: === Tumbleweed === Tumbleweed is the Rolling Release Distribution containing the latest [[openQA|openQA]] testet versions of all software. Tumbleweed is based on Factory, openSUSEs main development codebase, As soon as a openQA tests pass, a new Tumbleweed snapshot will be released – typically several times a week. === Slowroll === Please note, Slowroll is in beta stage. Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === Leap === Leap is the point release version, with a new release every year with older and more stable packages meant for business use. === Kalpa === Please note, Kalpa is in alpha stage. Kalpa is an atomic and transactional Linux desktop offering the KDE Plasma Desktop Environment. It's goal is to be easy to use and for people who "want to be stuff done" whitout messing with their operating system. Kalpa is based on Tumbleweed and MicroOS. === MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed a8c02944dc403c2f501214023c4f8da1a23ad7d9 5331 5330 2026-05-25T16:32:48Z Madonuko 140 add back distro infobox removed by previous editor wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] or [[transactional-update]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[IceWM]] | usagetype = Desktop, Server | architectures = i686, x86-64, aarch64, ppc64le, s390x | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE (/ˌoʊpənˈsuːzə/) is a line of [[Linux distributions]] developed by the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == OpenSUSE stands out by having variations of the distributions: === Tumbleweed === Tumbleweed is the Rolling Release Distribution containing the latest [[openQA|openQA]] testet versions of all software. Tumbleweed is based on Factory, openSUSEs main development codebase, As soon as a openQA tests pass, a new Tumbleweed snapshot will be released – typically several times a week. === Slowroll === Please note, Slowroll is in beta stage. Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === Leap === Leap is the point release version, with a new release every year with older and more stable packages meant for business use. === Kalpa === Please note, Kalpa is in alpha stage. Kalpa is an atomic and transactional Linux desktop offering the KDE Plasma Desktop Environment. It's goal is to be easy to use and for people who "want to be stuff done" whitout messing with their operating system. Kalpa is based on Tumbleweed and MicroOS. === MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed 157a3060ab9ee7c083e15c0ee4ccd4e9a0a2e6de 5333 5331 2026-05-25T17:09:31Z Sedot 397 wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] or [[transactional-update]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[IceWM]] | usagetype = Desktop, Server | architectures = i686, x86-64, aarch64, ppc64le, s390x | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE (/ˌoʊpənˈsuːzə/) is a line of [[Linux distributions]] developed by the openSUSE Project and the SUSE S.A., a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == OpenSUSE stands out by having variations of the distributions: === Tumbleweed === Tumbleweed is the Rolling Release Distribution containing the latest [[openQA|openQA]] testet versions of all software. Tumbleweed is based on Factory, openSUSEs main development codebase, As soon as a openQA tests pass, a new Tumbleweed snapshot will be released – typically several times a week. === Slowroll === Please note, Slowroll is in beta stage. Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === Leap === Leap is the point release version, with a new release every year with older and more stable packages meant for business use. === Kalpa === Please note, Kalpa is in alpha stage. Kalpa is an atomic and transactional Linux desktop offering the KDE Plasma Desktop Environment. It's goal is to be easy to use and for people who "want to be stuff done" whitout messing with their operating system. Kalpa is based on Tumbleweed and MicroOS. === MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed fc70c997f60dda185b67889ff62dfcaf0081117f 0 1243 5334 2026-05-25T17:12:24Z Nathan22211 360 Make Shell page for different shell programs wikitext text/x-wiki A shell is what's run when you first open your terminal, for Linux, this typically defaults to bash, for MacOS it's Zsh, and Windows it's Powershell {| class="wikitable" |+ |- ! Shell !! Links !! Decription |- | Bash || || Default shell for Linux operating systems |- | Zsh || || A shell that expands off the Korn shell. Default shell for MacOS |- | Xonsh || || A python based shell that has shared history between terminals. Also doubles as a superset of Python |- |Fish | | |- |Elvish | | |- |OSH |[https://oils.pub/osh.html Website] |A bash compatible shell with precise error printouts |- |YSH |[https://oils.pub/ysh.html Website] |A shell that describes itself as being a glue between typical shell, regex, python, YAML, and JSON |} 3ad42c02018aa7325bab686c33eb34e932329e74 2 1244 5335 2026-05-25T17:32:21Z Aktywnyyy 296 my page wikitext text/x-wiki == About Me == Just a guy with way too much free time, i code in '''Zig''', design PCBs in '''KiCad''', and build Discord bots using '''TypeScript''' or '''Go'''. Also, I know absolutely nothing about music. === Tech Stack & Systems === * '''Daily Driving OS:''' Chimera Linux * '''Desktop Environments:''' [[KDE Plasma]] * '''Core Interests:''' Programming in Zig and Reading books. == Contact / Links == * '''GitHub:''' maybe in the future ab621187b4d6e313e2be41bf1c7112b905c3cae0 0 217 5339 4628 2026-05-25T17:56:45Z Birdie 363 Completely overhauled the history section with more sources and detail about the split from Red Hat Linux specifically. I also made a couple of minor changes. wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{stub}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Stable Release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022-04-21 (Accessed: 2025-09-03)</ref> |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}} [[Category:Linux Distributions]] [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is a community maintained [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref>, sponsored primarily by [[Red Hat]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> and developed by the Fedora Project. The Fedora Project was formed in 2003<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux originally began as the Fedora Project, a community maintained repository of additional software packages for Red Hat Linux (RHL).<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> The project was founded in 2002 by University of Hawaii computer science student Warren Togami.<ref>[https://fedoraproject.org/wiki/User:Wtogami Fedora Project], Warren Togami, 2009-04-14 (Accessed: 2026-05-25)</ref> Around the same time, Red Hat was shifting its focus toward the enterprise market with the introduction of Red Hat Enterprise Linux (RHEL). By 2003 demand for RHEL was increasing and Red Hat recognized growing confusion between Red Hat Linux and Red Hat Enterprise Linux due to their similar naming and overlapping purpose.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> With the growing popularity of the Fedora Project repository, Red Hat made the decision to discontinue Red Hat Linux in order to focus its internal resources on RHEL, while also becoming the primary corporate sponsor of the newly established Fedora Project.<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> As part of this transition, Fedora evolved from a repository project into its own community maintained Linux distribution with the release of Fedora Core 1 in November 2003.<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref> With this new relationship established, Fedora Linux became Red Hat’s upstream community distribution, where new software and technologies were introduced and refined before later being adopted into RHEL and eventually, CentOS Stream. Fedora continues to have a reputation for rapidly adopting new technologies and features, making it a popular choice among Linux developers and enthusiasts who want well supported and up-to-date software.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> == Release system == Fedora current follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], '''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</ref> System upgrades are usually handled offline to prevent system breakage == The package management system == :''Main article: [[dnf]]'' The main package manager is [[dnf]], which is usually called with the following arguments: {| class="wikitable" |+ <code>dnf</code> Usage |- ! Command !! Description |- | <code>sudo dnf up</code> || updates system packages |- | <code>sudo dnf in <pkg names> <...></code> || install new packages |- | <code>sudo dnf rm <pkg names> <...></code> || remove packages |- | <code>sudo dnf system-upgrade --relesever=<rel></code> || updates system version and packages<ref>[https://dnf.readthedocs.io/ DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</ref> |} == References == <references /> 7c38551f27e1f95706b056491da662f7b4ea0c01 6 1245 5340 2026-05-25T17:57:14Z Veri 398 wikitext text/x-wiki Kubuntu's Logo d34528a546bf32719ec5b0ac3d371e7c956d2b8e 0 1246 5341 2026-05-25T18:05:46Z Veri 398 Created page with "{{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official flavour of [[Ubuntu]] developed by" wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official flavour of [[Ubuntu]] developed by a88e6311bd067468280ba86f7aa78134f0b9ded9 5342 5341 2026-05-25T18:27:02Z Veri 398 Adding minor details about kubuntu wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official flavour of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be user-friendly, fast ,and customizable, targeted at both newcomers and experienced Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the same as the central Ubuntu [[Linux Distributions|Linux distribution]], with exceptions that it is community-run by contributors. 9ec12b1fcdfc491e1ba7f7eb4e7aea042da3f78d 5343 5342 2026-05-25T18:29:15Z Veri 398 wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official flavour of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be user-friendly, fast, and customizable, targeted at both newcomers and experienced Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the same as the central Ubuntu [[Linux Distributions|Linux distribution]], with exceptions that it is community-run by contributors. 26ab0d079ac5d1891e080872d0a702c200cf2f13 5344 5343 2026-05-25T18:35:31Z Veri 398 wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official flavour of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be user-friendly, fast, and customizable, targeted at both newcomers and experienced Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the same as the central Ubuntu [[Linux Distributions|Linux distribution]], with exceptions that it is community-run by contributors.<ref>{{Cite|url=https://kubuntu.org/community/|title=Community - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> 72bb21fe1f886c2c9b69a146dc443ef78032ccbe 5345 5344 2026-05-25T18:50:20Z Veri 398 wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official flavour (official distribution that offers a distinct experience<ref>{{Cite|url=https://wiki.ubuntu.com/UbuntuFlavors|title=UbuntuFlavors - Ubuntu Wiki|author=Ubuntu Wiki|accessdate=25-05-2026}}</ref>) of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be user-friendly, fast, and customizable, targeted at both newcomers and experienced Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the same as the central Ubuntu [[Linux Distributions|Linux distribution]], with exceptions that it is community-run by contributors.<ref>{{Cite|url=https://kubuntu.org/community/|title=Community - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> 4aa7f6a9e1d96ea1e2f690d8ec271e86296b8ba5 5346 5345 2026-05-25T19:23:05Z Veri 398 wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official flavour (official distribution that offers a distinct experience) of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be user-friendly, fast, and customizable, targeted at both newcomers and experienced Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the same as the central Ubuntu [[Linux Distributions|Linux distribution]], with exceptions that it is community-run by contributors.<ref>{{Cite|url=https://kubuntu.org/community/|title=Community - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> e4ea1b96a8add7328486df9403b6482e84b995c2 0 8 5348 4698 2026-05-25T20:59:52Z Veri 398 wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] ** [[Flavor/Spin]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] ** [[Wayland]] ** [[X11]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] ** [[Cybersecurity]] ** [[DDoS]] ** [[ARPANET]] ** [[Ransomware]] ** [[Penetration testing|Penetration Testing]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 13bdd92b3fa56b2fa61343f533c7f3de4650d26d 5349 5348 2026-05-25T21:04:35Z Veri 398 wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux]] * [[Linux Distributions|Linux Distribution]] ** [[Derivative]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] ** [[Wayland]] ** [[X11]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] ** [[Cybersecurity]] ** [[DDoS]] ** [[ARPANET]] ** [[Ransomware]] ** [[Penetration testing|Penetration Testing]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 896b640aa5d74d7bae1e8d4d6086031498abef2a 0 1247 5352 2026-05-25T21:07:22Z Uniolo 345 Create cinny page with basic information and sidebar wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[Type Script]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/vim/vim }} '''Cinny''' is a free and open source [[Matrix]] client focused on simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, and the browser<ref>{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. [[Category:Software]] 33c7a52033ef8e245149fd808b0b3f3da0d58073 5354 5352 2026-05-25T21:20:27Z Uniolo 345 Listed features, fixed repo link, and added note about it replacing its SDK and not accepting contributions. wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[Type Script]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/cinnyapp/cinny }} '''Cinny''' is a free and open source [[Matrix]] client focused on providing a simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, along with the browser<ref name=":0">{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. It currently uses the [https://github.com/matrix-org/matrix-js-sdk matrix-js-sdk] but is in the process on replacing it with another one, as such, it is not currently accepting contributions<ref>{{Cite|url=https://github.com/cinnyapp/cinny|title=Cinny GitHub repo|author=Cinny contributors|year=2026-05-23|accessdate=2026-05-25}}</ref>. {| class="wikitable" |+Supported features<ref name=":0" /> !Name !Supported? |- |E2EE |Yes |- |Spaces |Yes |- |VoIP (1:1) |No |- |VoIP ([[Jitsi]]) |No |- |Threads |No |- |Legacy SSO |Yes |- |Multiple accounts |No |- |Multiple languages |No |} [[Category:Software]] 0d32381c0fd88be310803e5f41439e0f97a7d5f4 5359 5354 2026-05-25T21:27:29Z Uniolo 345 Clarified what it is replacing it with (another one -> a custom one) wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[Type Script]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/cinnyapp/cinny }} '''Cinny''' is a free and open source [[Matrix]] client focused on providing a simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, along with the browser<ref name=":0">{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. It currently uses the [https://github.com/matrix-org/matrix-js-sdk matrix-js-sdk] but is in the process on replacing it with a custom one, as such, it is not currently accepting contributions<ref>{{Cite|url=https://github.com/cinnyapp/cinny|title=Cinny GitHub repo|author=Cinny contributors|year=2026-05-23|accessdate=2026-05-25}}</ref>. {| class="wikitable" |+Supported features<ref name=":0" /> !Name !Supported? |- |E2EE |Yes |- |Spaces |Yes |- |VoIP (1:1) |No |- |VoIP ([[Jitsi]]) |No |- |Threads |No |- |Legacy SSO |Yes |- |Multiple accounts |No |- |Multiple languages |No |} [[Category:Software]] 6fecc9ef27d17cf0bbb9102bb8688c40643ca572 5365 5359 2026-05-25T21:37:54Z Uniolo 345 Added image of Cinny wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[Type Script]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/cinnyapp/cinny }} [[File:Cinny-Unredacted.org.png|thumb|A photo of Cinny in the Unredacted Matrix server chat]] '''Cinny''' is a free and open source [[Matrix]] client focused on providing a simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, along with the browser<ref name=":0">{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. It currently uses the [https://github.com/matrix-org/matrix-js-sdk matrix-js-sdk] but is in the process on replacing it with a custom one, as such, it is not currently accepting contributions<ref>{{Cite|url=https://github.com/cinnyapp/cinny|title=Cinny GitHub repo|author=Cinny contributors|year=2026-05-23|accessdate=2026-05-25}}</ref>. {| class="wikitable" |+Supported features<ref name=":0" /> !Name !Supported? |- |E2EE |Yes |- |Spaces |Yes |- |VoIP (1:1) |No |- |VoIP ([[Jitsi]]) |No |- |Threads |No |- |Legacy SSO |Yes |- |Multiple accounts |No |- |Multiple languages |No |} [[Category:Software]] d156f61d1a27db19e15443043274b7679c6df245 5366 5365 2026-05-25T21:49:40Z Uniolo 345 Correct out of date information I got from the (official) Matrix website. Cinny now supports voice chat. wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[Type Script]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/cinnyapp/cinny }} [[File:Cinny-Unredacted.org.png|thumb|A photo of Cinny in the Unredacted Matrix server chat]] '''Cinny''' is a free and open source [[Matrix]] client focused on providing a simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, along with the browser<ref name=":0">{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. It currently uses the [https://github.com/matrix-org/matrix-js-sdk matrix-js-sdk] but is in the process on replacing it with a custom one, as such, it is not currently accepting contributions<ref>{{Cite|url=https://github.com/cinnyapp/cinny|title=Cinny GitHub repo|author=Cinny contributors|year=2026-05-23|accessdate=2026-05-25}}</ref>. {| class="wikitable" |+Supported features<ref name=":0" /> !Name !Supported? |- |E2EE |Yes |- |Spaces |Yes |- |Voice chat (1:1) |Yes<ref name=":1">{{Cite|url=https://github.com/matrix-org/matrix.org/issues/3418|title=Cinny supports MatrixRTC|author=spaetz|year=May 2026|accessdate=2026-05-25}}</ref> |- |Voice chat ([[Jitsi]]) |Yes<ref name=":1" /> |- |Threads |No |- |Legacy SSO |Yes |- |Multiple accounts |No |- |Multiple languages |No |} [[Category:Software]] 96be9563861eeb038f072c1ac36b5e3e0a2993f1 6 1248 5353 2026-05-25T21:20:02Z Veri 398 wikitext text/x-wiki Screenshot of the Fedora Cosmic Spin 9fd961943fa9903f38e8c47c0c48df4108b10862 0 1249 5355 2026-05-25T21:22:01Z Veri 398 Made a derivatives page as a key term wikitext text/x-wiki In Linux, a derivative [[Linux Distributions|Linux distribution]] is a distribution that will incorporate elements from its '''parent distribution''', such as the [[Package Manager]], and[[Repository|Repositories]] but may sometimes also add their '''own''' configuration or other changes in order to make the user experience different from the parent distribution. [[File:Fedoracosmicspin.jpg|thumb|A screenshot of the Fedora Cosmic Spin]] There are also different types of derivatives, such as '''flavors/spins''' which are most synonymous with [[Ubuntu]] and [[Fedora]] respectively. Flavors, or spins, are typically '''lightly modified''' distributions with very '''few changes''' from their parent distribution, which can mean something as small as a change in [[Desktop Environments|Desktop Environment]]. b61da09e59fe667b2205397ebb97bcea5d42a329 5356 5355 2026-05-25T21:22:40Z Veri 398 wikitext text/x-wiki In Linux, a derivative [[Linux Distributions|Linux distribution]] is a distribution that will incorporate elements from its '''parent distribution''', such as the [[Package Manager]], and [[Repository|Repositories]] but may sometimes also add their '''own''' configuration or other changes in order to make the user experience different from the parent distribution. [[File:Fedoracosmicspin.jpg|thumb|A screenshot of the Fedora Cosmic Spin]] There are also different types of derivatives, such as '''flavors/spins''' which are most synonymous with [[Ubuntu]] and [[Fedora]] respectively. Flavors, or spins, are typically '''lightly modified''' distributions with very '''few changes''' from their parent distribution, which can mean something as small as a change in [[Desktop Environments|Desktop Environment]]. f512e78b00b36c156f165cc84bd0d0ee1a3c9d1d 5358 5356 2026-05-25T21:25:16Z Veri 398 wikitext text/x-wiki In Linux, a derivative [[Linux Distributions|Linux distribution]] is a distribution that will incorporate elements from its '''parent distribution''', such as the [[Package Manager]], and [[Repository|Repositories]] but may sometimes also add their '''own''' configuration or other changes in order to make the user experience different from the parent distribution. One major example of this is [[Ubuntu]] being a derivative distribution of [[Debian]] [[File:Fedoracosmicspin.jpg|thumb|A screenshot of the Fedora Cosmic Spin]] There are also different types of derivatives, such as '''flavors/spins''' which are most synonymous with [[Ubuntu]] and [[Fedora]] respectively. Flavors, or spins, are typically '''lightly modified''' distributions with very '''few changes''' from their parent distribution, which can mean something as small as a change in [[Desktop Environments|Desktop Environment]]. fd62324764ea06bdb23f128b643fbc8009c0b593 5360 5358 2026-05-25T21:30:35Z Veri 398 wikitext text/x-wiki In Linux, a derivative [[Linux Distributions|Linux distribution]] is a distribution that will incorporate elements from its '''parent distribution''', such as the [[Package Manager]], and [[Repository|Repositories]] but may sometimes also add their '''own''' configuration or other changes in order to make the user experience different from the parent distribution. One major example of this is [[Ubuntu]] being a derivative distribution of [[Debian]] There are also different types of derivatives, such as '''flavors/spins''' which are most synonymous with [[Ubuntu]] and [[Fedora]] respectively. Flavors, or spins, are typically '''lightly modified''' distributions with very '''few changes''' from their parent distribution, which can mean something as small as a change in [[Desktop Environments|Desktop Environment]]. 075d09ae9fb9adce9c0d19515d6e50a0db8123a7 5361 5360 2026-05-25T21:32:10Z Veri 398 wikitext text/x-wiki In Linux, a derivative [[Linux Distributions|Linux distribution]] is a distribution that will incorporate elements from its '''parent distribution''', such as the [[Package Manager]], and [[Repository|Repositories]] but may sometimes also add their '''own''' configuration or other changes in order to make the user experience different from the parent distribution. One major example of this is [[Ubuntu]] being a derivative distribution of [[Debian]] [[File:Fedoracosmicspin.jpg|thumb|Screenshot of the Fedora Cosmic Spin]] There are also different types of derivatives, such as '''flavors/spins''' which are most synonymous with [[Ubuntu]] and [[Fedora]] respectively. Flavors, or spins, are typically '''lightly modified''' distributions with very '''few changes''' from their parent distribution, which can mean something as small as a change in [[Desktop Environments|Desktop Environment]]. a91f0200b4d75cf264c21c3c1630098d1868a9ae 0 396 5357 5295 2026-05-25T21:24:13Z Uniolo 345 Listed Cinny wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package Managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' File managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. These are the most common file managers: {| class="wikitable" !Name !External links !Description !DE |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |[[Plasma|KDE Plasma]] |- |Thunar |[https://docs.xfce.org/xfce/thunar/start Xfce] |Thunar is [[Xfce]]'s modern file manager, desgined from the group up for speed and friendliness. |[[Xfce]] |- |} == System Resource Monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. == Hardware Maintenance == '''See the main page: [[Hardware Maintenance]]''' These are GUI and TUI programs that check the current health and utilization of hardware components such as your SSD/HDDs and battery. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp GitHub] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Cinny]] |[https://cinny.in/ Website], [https://github.com/cinnyapp/cinny GitHub] |Matrix client focused on providing a simple, elegant and secure interface. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |} = Media = '''See the main page: [[Media]]''' == Art, 2D, and 3D media editing == '''See the main page: [[Media Editing]]''' Includes software primarily meant for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation, etc. == Music and Audio == '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. 1314da4d647422ceaf975fbfcf6cc205cc8d8e2d 0 394 5362 5262 2026-05-25T21:34:23Z Daeraxa 400 Add RISC OS to Other Operating Systems. Added as still maintained, open source and easy to install on a Raspberry Pi wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel == BSD Based == {| class="wikitable" |- ! OS !! Description |- | [[Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} == Darwin Based == {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} == Solaris Based == {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} == Other UNIX-like == {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} == L4 based == {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} == Other Operating Systems == {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[RISC OS]] | An open source operating system designed in Cambridge, England by Acorn. First released in 1987, its origins can be traced back to the original team that developed the Arm microprocessor. |- |} e7a183651eb3878d3299da03b1c4336e0386d7ac 6 1250 5363 2026-05-25T21:36:28Z Uniolo 345 wikitext text/x-wiki A photo of the a room on the unredacted.org server, taken with the Cinny client. fa7b88f54a19e7e6156ee008782f24b21cb04e26 0 653 5364 4287 2026-05-25T21:37:27Z Veri 398 removed that cosmic is based on gnome wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox | title = Pop!_OS | image = [[File:Pop! OS Icon.svg|frameless]] | caption = The Pop!_OS logo | releasestatus = Maintained | packagemanager = [[APT]] | defaultdesktops = COSMIC | usagetype = Desktop | architectures = x86_64 | website = Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX] | releasemodel = Stable }} Pop!_OS is a free and open-source [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]] called [[COSMIC]]. Pop!OS is developed by the American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. == <u>Features</u> == * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle c2dd32c75d0a8d75522b0205e3e3a581418bb8b3 5368 5364 2026-05-25T21:58:26Z Veri 398 wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox | title = Pop!_OS | image = [[File:Pop! OS Icon.svg|frameless]] | caption = The Pop!_OS logo | releasestatus = Maintained | packagemanager = [[APT]] | defaultdesktops = COSMIC | usagetype = Desktop | architectures = x86_64 | website = Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX] | releasemodel = Stable }} Pop!_OS is a free and open-source [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]] called [[COSMIC]]. Pop!OS is developed by the American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. [[File:Poposrice.png|thumb|351x351px|Screenshot of a Pop!_OS desktop]] == <u>Features</u> == * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle 881afbeadf7f2187ea7bbe21a18f404c1b1ba373 5369 5368 2026-05-25T22:02:29Z Veri 398 wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox | title = Pop!_OS | image = [[File:Pop! OS Icon.svg|frameless]] | caption = The Pop!_OS logo | releasestatus = Maintained | packagemanager = [[APT]] | defaultdesktops = COSMIC | usagetype = Desktop | architectures = x86_64 | website = Pop!_OS Website (System76)[https://system76.com/pop/?srsltid=AfmBOoqzkzimZktpZXZWX6yDXhDxIEevljBK6QUIc1omMfoVqhv2vpRX] | releasemodel = Stable }} Pop!_OS is a free and open-source [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]] called [[COSMIC]]. Pop!OS is developed by the American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. [[File:Poposrice.png|border|right|frameless|346x346px]] == <u>Features</u> == * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle e771ad8a640b8378b05879e20f53b6c1ba099080 6 1251 5367 2026-05-25T21:57:37Z Veri 398 wikitext text/x-wiki Screenshot of a Pop!_OS desktop dc31e193477eabb441f58776724b8f81a0e04521 6 1251 5370 5367 2026-05-25T22:05:58Z Veri 398 Veri uploaded a new version of [[File:Poposrice.png]] wikitext text/x-wiki Screenshot of a Pop!_OS desktop dc31e193477eabb441f58776724b8f81a0e04521 0 1232 5371 5315 2026-05-25T22:08:49Z Daeraxa 400 Adds a bunch of relatively notable and actively developed text editor (with the exception of Atom which is historically important and still referenced in a lot of guides and documentation) wikitext text/x-wiki Commonly-used free and open source text editing [[software]] on [[Linux]]. = Text editors = {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[Gram]] |[https://gram-editor.com/ Website], [https://codeberg.org/GramEditor/gram CodeBerg] |A code editor that started as a fork of [[Zed]] to remove AI and avoid agreeing to the Zed terms of use |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[Pulsar]] |[https://pulsar-edit.dev/ Website], [https://github.com/pulsar-edit/pulsar GitHub] |A community-led, hyper-hackable text editor. Pulsar is a fork of the discontinued [[Atom]] editor |- |[[Atom]] |[https://atom.io/ Website], [https://github.com/atom/atom GitHub] |The hackable text editor. A discontinued GitHub developed editor |- |[[Lite XL]] |[https://lite-xl.com/ Website], [https://github.com/lite-xl/lite-xl GitHub] |A lightweight text editor written in Lua |- |[[Pragtical]] |[https://pragtical.dev/ Website], [https://github.com/pragtical/pragtical GitHub] |The practical and pragmatic code editor. Fork of [[Lite XL]] |- |[[Lapce]] |[https://lap.dev/lapce/ Website], [https://github.com/lapce/lapce GitHub] |Lightning-fast and Powerful Code Editor written in Rust |- |} == Terminal-based text editors == These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[Nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[Vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[Vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[Neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[Helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |- |[[Flow Control]] |[https://flow-control.dev/ Website], [https://github.com/neurocyte/flow GitHub] |TUI editor written in Zig with multiple keybinding modes |- |[[Edit]] |[https://learn.microsoft.com/en-us/windows/edit/ Website], [https://github.com/microsoft/edit GitHub] |Simple Microsoft developed command-line text editor |- |} = Integrated development environments (IDEs) = IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} 9accc963710d32256a41231a6adb775e6c156f8b 0 1252 5372 2026-05-25T22:08:55Z Veri 398 Redirected page to [[Derivative]] wikitext text/x-wiki #REDIRECT [[Derivative]] 910aaadd033b87403c699fb8fa24113446af30a1 0 1246 5373 5346 2026-05-25T22:09:11Z Veri 398 wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official [[Flavor]] of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be user-friendly, fast, and customizable, targeted at both newcomers and experienced Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the same as the central Ubuntu [[Linux Distributions|Linux distribution]], with exceptions that it is community-run by contributors.<ref>{{Cite|url=https://kubuntu.org/community/|title=Community - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> 2f60ab1b7b2253cfbd9c42c6929cd885a4894ead 5374 5373 2026-05-25T22:09:28Z Veri 398 wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official [[flavor]] of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be user-friendly, fast, and customizable, targeted at both newcomers and experienced Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the same as the central Ubuntu [[Linux Distributions|Linux distribution]], with exceptions that it is community-run by contributors.<ref>{{Cite|url=https://kubuntu.org/community/|title=Community - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> cc62e07dab4f7d18fefcb261f730ad3e1e0762e0 5413 5374 2026-05-26T09:03:39Z Veri 398 wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official [[flavor]] of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be user-friendly, fast, and customizable, targeted at both newcomers and experienced Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the same as the central Ubuntu [[Linux Distributions|Linux distribution]], with exception that it is community-run by contributors.<ref>{{Cite|url=https://kubuntu.org/community/|title=Community - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> 3ffac39e3f02f748094a09175412455fa7529937 5415 5413 2026-05-26T09:54:34Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an official [[flavor]] of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be user-friendly, fast, and customizable, targeted at both newcomers and experienced Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the same as the central Ubuntu [[Linux Distributions|Linux distribution]], with exception that it is community-run by contributors.<ref>{{Cite|url=https://kubuntu.org/community/|title=Community - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> adb561a27d6e245c987e5c337a7664f0e3df9bb4 0 1247 5375 5366 2026-05-25T23:00:15Z Uniolo 345 Added note that Matrix.org page is outdated. I am following the GitHub issue so I can update this page when it is fixed. wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[Type Script]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/cinnyapp/cinny }} [[File:Cinny-Unredacted.org.png|thumb|A photo of Cinny in the Unredacted Matrix server chat]] '''Cinny''' is a free and open source [[Matrix]] client focused on providing a simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, along with the browser<ref name=":0">{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. It currently uses the [https://github.com/matrix-org/matrix-js-sdk matrix-js-sdk] but is in the process on replacing it with a custom one, as such, it is not currently accepting contributions<ref>{{Cite|url=https://github.com/cinnyapp/cinny|title=Cinny GitHub repo|author=Cinny contributors|year=2026-05-23|accessdate=2026-05-25}}</ref>. {| class="wikitable" |+Supported features<ref name=":0" /> !Name !Supported? |- |E2EE |Yes |- |Spaces |Yes |- |Voice chat (1:1) |Yes<ref name=":1">{{Cite|url=https://github.com/matrix-org/matrix.org/issues/3418|title=Cinny supports MatrixRTC|author=spaetz|year=May 2026|accessdate=2026-05-25}}</ref> |- |Voice chat ([[Jitsi]]) |Yes<ref name=":1" /> |- |Threads |No |- |Legacy SSO |Yes |- |Multiple accounts |No |- |Multiple languages |No |} Note that [https://matrix.org/ecosystem/clients/cinny/ the page listing Cinny's features on Matrix.org] is outdated, as it now supports Voice chat<ref name=":1" />. [[Category:Software]] 1885f750ea5aacebcacd6115b26d7e4a7a5cfd46 0 1253 5376 2026-05-25T23:49:41Z Uniolo 345 Create Matrix with basic information about clients and homeservers. wikitext text/x-wiki {{Stub}} '''Matrix''' is a open network for secure and decentralized communication, and consists of a federated network of Matrix "homeservers." Users from any homeserver can communicate with users from any other homeserver unless blocked by the homeserver owner. It has various clients [https://matrix.org/ecosystem/clients/ listed on its website]. Each client supports every homeserver. Notable clients include [[Element]], [[Cinny]], [[Nheko]], and [[FluffyChat]]. 70e25bb93218ac634f727985322ff9f853a480fe 5377 5376 2026-05-26T00:00:48Z Uniolo 345 Added information about what Matrix has and noted its military use and possible use cases. wikitext text/x-wiki {{Stub}} '''Matrix''' is a open network for secure and decentralized communication, and consists of a federated network of Matrix "homeservers." Users from any homeserver can communicate with users from any other homeserver unless blocked by the homeserver owner<ref>{{Cite|url=https://matrix.org/docs/matrix-concepts/elements-of-matrix/#homeserver|title=Matrix documentation, "Elements of Matrix"|author=Matrix.org Foundation|year=2023-02-08|accessdate=2026-05-25}}</ref>. It has various clients [https://matrix.org/ecosystem/clients/ listed on its website]. Each client supports every homeserver. Notable clients include [[Element]], [[Cinny]], [[Nheko]], and [[FluffyChat]]. Matrix has various features, the exact features may vary by client but usually include E2EE, VoIP (otherwise known as "Voice Chat"), and Spaces. Several governments and militaries use Matrix for secure communications<ref>{{Cite|url=https://element.io/blog/in-an-increasingly-volatile-world-governments-turn-to-element-and-matrix/|title=In an increasingly volatile world, governments turn to Element and Matrix|author=Steve Loynes|year=December 19, 2024|accessdate=2026-05-25}}</ref>. Matrix may also be used by people needing privacy or with an interest in it, or who don't want to use services like Discord due to the risk of the centralized Discord server collapsing, banning the server, or making bad decisions effecting them. 24c5f0ae7afa311ebae653da58624c632571714d 5378 5377 2026-05-26T00:09:13Z Uniolo 345 Rephrased the part about VoIP being like voice chat wikitext text/x-wiki {{Stub}} '''Matrix''' is a open network for secure and decentralized communication, and consists of a federated network of Matrix "homeservers." Users from any homeserver can communicate with users from any other homeserver unless blocked by the homeserver owner<ref>{{Cite|url=https://matrix.org/docs/matrix-concepts/elements-of-matrix/#homeserver|title=Matrix documentation, "Elements of Matrix"|author=Matrix.org Foundation|year=2023-02-08|accessdate=2026-05-25}}</ref>. It has various clients [https://matrix.org/ecosystem/clients/ listed on its website]. Each client supports every homeserver. Notable clients include [[Element]], [[Cinny]], [[Nheko]], and [[FluffyChat]]. Matrix has various features, the exact features may vary by client but usually include E2EE, VoIP (which can be thought of as "Voice Chat"), and Spaces. Several governments and militaries use Matrix for secure communications<ref>{{Cite|url=https://element.io/blog/in-an-increasingly-volatile-world-governments-turn-to-element-and-matrix/|title=In an increasingly volatile world, governments turn to Element and Matrix|author=Steve Loynes|year=December 19, 2024|accessdate=2026-05-25}}</ref>. Matrix may also be used by people needing privacy or with an interest in it, or who don't want to use services like Discord due to the risk of the centralized Discord server collapsing, banning the server, or making bad decisions effecting them. e7acb21d6c62efa1f61e70ea67f27c7e5cbefdf5 5419 5378 2026-05-26T09:55:14Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} '''Matrix''' is a open network for secure and decentralized communication, and consists of a federated network of Matrix "homeservers." Users from any homeserver can communicate with users from any other homeserver unless blocked by the homeserver owner<ref>{{Cite|url=https://matrix.org/docs/matrix-concepts/elements-of-matrix/#homeserver|title=Matrix documentation, "Elements of Matrix"|author=Matrix.org Foundation|year=2023-02-08|accessdate=2026-05-25}}</ref>. It has various clients [https://matrix.org/ecosystem/clients/ listed on its website]. Each client supports every homeserver. Notable clients include [[Element]], [[Cinny]], [[Nheko]], and [[FluffyChat]]. Matrix has various features, the exact features may vary by client but usually include E2EE, VoIP (which can be thought of as "Voice Chat"), and Spaces. Several governments and militaries use Matrix for secure communications<ref>{{Cite|url=https://element.io/blog/in-an-increasingly-volatile-world-governments-turn-to-element-and-matrix/|title=In an increasingly volatile world, governments turn to Element and Matrix|author=Steve Loynes|year=December 19, 2024|accessdate=2026-05-25}}</ref>. Matrix may also be used by people needing privacy or with an interest in it, or who don't want to use services like Discord due to the risk of the centralized Discord server collapsing, banning the server, or making bad decisions effecting them. bbbe9534b8d671676d67cfabeff61f589af58a40 0 217 5379 5339 2026-05-26T00:09:17Z Birdie 363 spelling/grammar wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}}{{stub}} {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Stable Release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022-04-21 (Accessed: 2025-09-03)</ref> |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}} [[Category:Linux Distributions]] [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is a community maintained [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref>, sponsored primarily by [[Red Hat]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> and developed by the Fedora Project. The Fedora Project was formed in 2003<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux originally began as the Fedora Project, a community maintained repository of additional software packages for Red Hat Linux (RHL).<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> The project was founded in 2002 by University of Hawaii computer science student Warren Togami.<ref>[https://fedoraproject.org/wiki/User:Wtogami Fedora Project], Warren Togami, 2009-04-14 (Accessed: 2026-05-25)</ref> Around the same time, Red Hat was shifting its focus toward the enterprise market with the introduction of Red Hat Enterprise Linux (RHEL). By 2003 demand for RHEL was increasing and Red Hat recognized growing confusion between Red Hat Linux and Red Hat Enterprise Linux due to their similar naming and overlapping purpose.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> With the growing popularity of the Fedora Project repository, Red Hat made the decision to discontinue Red Hat Linux in order to focus its internal resources on RHEL, while also becoming the primary corporate sponsor of the newly established Fedora Project.<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> As part of this transition, Fedora evolved from a repository project into its own community maintained Linux distribution with the release of Fedora Core 1 in November 2003.<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref> With this new relationship established, Fedora Linux became Red Hat’s upstream community distribution, where new software and technologies were introduced and refined before later being adopted into RHEL and eventually, CentOS Stream. Fedora continues to have a reputation for rapidly adopting new technologies and features, making it a popular choice among Linux developers and enthusiasts who want well supported and up-to-date software.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> == Release system == Fedora currently follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], '''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</ref> System upgrades are usually handled offline to prevent system breakage == The package management system == :''Main article: [[dnf]]'' The main package manager is [[dnf]], which is usually called with the following arguments: {| class="wikitable" |+ <code>dnf</code> Usage |- ! Command !! Description |- | <code>sudo dnf up</code> || updates system packages |- | <code>sudo dnf in <pkg names> <...></code> || install new packages |- | <code>sudo dnf rm <pkg names> <...></code> || remove packages |- | <code>sudo dnf system-upgrade --relesever=<rel></code> || updates system version and packages<ref>[https://dnf.readthedocs.io/ DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</ref> |} == References == <references /> 7b3772bd1698c1ab6af9b164d37eff29d31fcbfa 0 1254 5380 2026-05-26T00:31:50Z Uniolo 345 Create page about "repository" in the context of package managers as this is a wanted page and most of the links here are related to package management. Add note at the top about git repos. wikitext text/x-wiki {{Stub}} Did you mean: [[Git|Git repository]]? The term '''Repository''' is a term in packaging, it is a central server where packages are stored that can be installed with a package manager. Packages are usually signed with [[GnuPG]], [[Minisign]], or another similar cryptographic signing tool. [[Category:Terminology]] 028103ed7bf8939f3185257a1656481af0da14b9 5381 5380 2026-05-26T00:34:52Z Uniolo 345 Link back to packaging wikitext text/x-wiki {{Stub}} Did you mean: [[Git|Git repository]]? The term '''Repository''' is a term in [[Package|packaging]], it is a central server where packages are stored that can be installed with a package manager. Packages are usually signed with [[GnuPG]], [[Minisign]], or another similar cryptographic signing tool. [[Category:Terminology]] 9b5f6150cb28a81fa53245570b744e60f290444c 5418 5381 2026-05-26T09:55:04Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Terminology]] {{Stub}} Did you mean: [[Git|Git repository]]? The term '''Repository''' is a term in [[Package|packaging]], it is a central server where packages are stored that can be installed with a package manager. Packages are usually signed with [[GnuPG]], [[Minisign]], or another similar cryptographic signing tool. 5c165741e86094b1d19be08e7e611d3340f092b7 0 1255 5382 2026-05-26T01:01:57Z Uniolo 345 Make as redirect to already existing Free and Open Source Software as this is a wanting page that would serve basically the same purpose. wikitext text/x-wiki #redirect [Free and Open Source Software] 49be89f8dd04b6f169c387140bc63f8fcbd58a41 5383 5382 2026-05-26T01:02:22Z Uniolo 345 Actually make it a redirect (woops) wikitext text/x-wiki #redirect [[Free and Open Source Software]] 02c71bbb496eb70e1b86cc0207ef0fe667087f1a 6 1256 5384 2026-05-26T01:08:25Z Daeraxa 400 wikitext text/x-wiki Pulsar editor logo fa1a8e2718d2bba1131f7b09f8e80f6a3ce719bb 0 1257 5385 2026-05-26T01:13:25Z Daeraxa 400 Created page for the Pulsar text editor, notable as an actively developed fork of Atom wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Pulsar logo.png|thumb|alt=Pulsar logo, a purple circle with a white stylized depiction of a pulsar inside it|Pulsar logo]] | caption = Pulsar editor | title = Pulsar | releasestatus = Maintained | lastrelease = v1.132.1, 2026-05-20 | firstrelease = v1.102.0, 2023-02-16 | languages = [[javascript]] | developers = Pulsar Team | website = [https://pulsar-edit.dev/ pulsar-edit.dev] | sourcecode = [https://github.com/pulsar-edit/pulsar github.com/pulsar-edit/pulsar] | license = MIT }} [[Category:Software]] The '''Pulsar''' text editor describes itself as "a fork of the discontinued [[Atom]] editor — assuming its mission of being a zero-compromise combination of hackability and usability" ''Pulsar'' is a text editor built on web technologies with a focus on being hacker-friendly but approachable for people of all skill levels. It uses the [[Electron]] GUI framework and is written in [[Javascript]] so if you know Javascript the options for customisation are endless. It supports installation on various Linux distributions, macOS and Windows. ''Pulsar'' features a built-in package manager called ''PPM'' that can search for and install over 10,000 community packages uploaded to the [https://packages.pulsar-edit.dev/ Pulsar Package Repository]. The majority of these packages were written for Atom and were archived and copied before the original ''Atom.io'' website went offline<ref>[https://blog.pulsar-edit.dev/posts/20221127-confused-Techie-SunsetMisadventureBackend/ Pulsar Blog], Pulsar Edit, 2022-11-27 (Accessed: 2026-05-26)</ref>. Packages are also written in Javascript and can take advantage of [https://docs.pulsar-edit.dev/api/pulsar/latest/ Pulsar's API], Electron APIs and the entire [[Node.js]] ecosystem. ''Pulsar'' is designed to provide a good out of the box experience to all users. It comes with features that most people consider essential in a modern GUI text editor but not too many as to overwhelm a new user. Such features include the aforementioned built in package manager, IDE features for integration with language servers, [[Git]] integration, a customisable pane-based interface, in-built terminal and text editing features such as multiple cursors, snippets and semantic selections. It ships with built-in support for a large number of commonly used programming languages but can also be easily extended by downloading a package that provides that language. == History == ''Pulsar'' was created by a bunch of community members and fans of the Atom editor. When GitHub announced that they were sunsetting Atom<ref>[https://github.blog/news-insights/product-news/sunsetting-atom/ GitHub Blog], GitHub, 2022-06-08 (Accessed: 2026-05-26)</ref> some of the members of Atom Community decided that the editor should be forked and continued under community stewardship. However, disagreements between members arose in the direction that development should take and so the team that would later vote on the name ''Pulsar'' was created. In order to keep the project alive in the aftermath of the sunsetting announcement, the team had to move quickly. Branding, CI/CD, new build tooling, website, community areas, package backend and a focus on modernization to deprecate old features such as the areas of the application written in [[CoffeeScript]] and get onto modern and supported versions of Electron and Node.js. The first actual tagged version of a Pulsar release was made on 15 December 2022 - the same day that Atom.io finally went dark<ref>[https://blog.pulsar-edit.dev/posts/20221215-confused-Techie-v1.100.1-beta/ Pulsar Blog], Pulsar Edit, 2022-12-15 (Accessed: 2026-05-26)</ref> Since then there has been steady improvement - adding new features, updating and upgrading existing ones, migrating from unmaintained dependencies to better alternatives. == Installation == Pulsar is available for installation on most common operating systems: Windows, macOS (both Intel and Apple Silicon version) and most common Linux distributions. Multiple package and installation options are available through either official package releases or package manager support or through community maintained ones. For full instructions consult the Pulsar downloads page [https://pulsar-edit.dev/download/ pulsar-edit.dev/download] == Documentation == Extensive documentation can be found on the Pulsar website [https://docs.pulsar-edit.dev/ docs.pulsar-edit.dev/]. This includes guides, tutorials and references on how to use Pulsar as well as instructions on how to customise Pulsar and create new Packages. It also features Pulsar's API reference and that of the package backend. == References == aa9436504e6e93fd64fa1f5d8f3e5b0608f59a9d 5386 5385 2026-05-26T01:18:16Z Daeraxa 400 Remove unnecessary links fields that don't add anything wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Pulsar logo.png|thumb|alt=Pulsar logo, a purple circle with a white stylized depiction of a pulsar inside it]] | title = Pulsar | releasestatus = Maintained | lastrelease = v1.132.1, 2026-05-20 | firstrelease = v1.102.0, 2023-02-16 | languages = [[javascript]] | developers = Pulsar Team | website = [https://pulsar-edit.dev/ pulsar-edit.dev] | sourcecode = [https://github.com/pulsar-edit/pulsar github.com/pulsar-edit/pulsar] | license = MIT }} [[Category:Software]] The '''Pulsar''' text editor describes itself as "a fork of the discontinued [[Atom]] editor — assuming its mission of being a zero-compromise combination of hackability and usability" ''Pulsar'' is a text editor built on web technologies with a focus on being hacker-friendly but approachable for people of all skill levels. It uses the [[Electron]] GUI framework and is written in [[Javascript]] so if you know Javascript the options for customisation are endless. It supports installation on various Linux distributions, macOS and Windows. ''Pulsar'' features a built-in package manager called ''PPM'' that can search for and install over 10,000 community packages uploaded to the [https://packages.pulsar-edit.dev/ Pulsar Package Repository]. The majority of these packages were written for Atom and were archived and copied before the original ''Atom.io'' website went offline<ref>[https://blog.pulsar-edit.dev/posts/20221127-confused-Techie-SunsetMisadventureBackend/ Pulsar Blog], Pulsar Edit, 2022-11-27 (Accessed: 2026-05-26)</ref>. Packages are also written in Javascript and can take advantage of [https://docs.pulsar-edit.dev/api/pulsar/latest/ Pulsar's API], Electron APIs and the entire [[Node.js]] ecosystem. ''Pulsar'' is designed to provide a good out of the box experience to all users. It comes with features that most people consider essential in a modern GUI text editor but not too many as to overwhelm a new user. Such features include the aforementioned built in package manager, IDE features for integration with language servers, [[Git]] integration, a customisable pane-based interface, in-built terminal and text editing features such as multiple cursors, snippets and semantic selections. It ships with built-in support for a large number of commonly used programming languages but can also be easily extended by downloading a package that provides that language. == History == ''Pulsar'' was created by a bunch of community members and fans of the Atom editor. When GitHub announced that they were sunsetting Atom<ref>[https://github.blog/news-insights/product-news/sunsetting-atom/ GitHub Blog], GitHub, 2022-06-08 (Accessed: 2026-05-26)</ref> some of the members of Atom Community decided that the editor should be forked and continued under community stewardship. However, disagreements between members arose in the direction that development should take and so the team that would later vote on the name ''Pulsar'' was created. In order to keep the project alive in the aftermath of the sunsetting announcement, the team had to move quickly. Branding, CI/CD, new build tooling, website, community areas, package backend and a focus on modernization to deprecate old features such as the areas of the application written in [[CoffeeScript]] and get onto modern and supported versions of Electron and Node.js. The first actual tagged version of a Pulsar release was made on 15 December 2022 - the same day that Atom.io finally went dark<ref>[https://blog.pulsar-edit.dev/posts/20221215-confused-Techie-v1.100.1-beta/ Pulsar Blog], Pulsar Edit, 2022-12-15 (Accessed: 2026-05-26)</ref> Since then there has been steady improvement - adding new features, updating and upgrading existing ones, migrating from unmaintained dependencies to better alternatives. == Installation == Pulsar is available for installation on most common operating systems: Windows, macOS (both Intel and Apple Silicon version) and most common Linux distributions. Multiple package and installation options are available through either official package releases or package manager support or through community maintained ones. For full instructions consult the Pulsar downloads page [https://pulsar-edit.dev/download/ pulsar-edit.dev/download] == Documentation == Extensive documentation can be found on the Pulsar website [https://docs.pulsar-edit.dev/ docs.pulsar-edit.dev/]. This includes guides, tutorials and references on how to use Pulsar as well as instructions on how to customise Pulsar and create new Packages. It also features Pulsar's API reference and that of the package backend. == References == 4797f61d9f8271146c685bece4af472a8d9f0d30 5389 5386 2026-05-26T01:29:54Z Daeraxa 400 Fix JS case wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Pulsar logo.png|thumb|alt=Pulsar logo, a purple circle with a white stylized depiction of a pulsar inside it]] | title = Pulsar | releasestatus = Maintained | lastrelease = v1.132.1, 2026-05-20 | firstrelease = v1.102.0, 2023-02-16 | languages = [[JavaScript]] | developers = Pulsar Team | website = [https://pulsar-edit.dev/ pulsar-edit.dev] | sourcecode = [https://github.com/pulsar-edit/pulsar github.com/pulsar-edit/pulsar] | license = MIT }} [[Category:Software]] The '''Pulsar''' text editor describes itself as "a fork of the discontinued [[Atom]] editor — assuming its mission of being a zero-compromise combination of hackability and usability" ''Pulsar'' is a text editor built on web technologies with a focus on being hacker-friendly but approachable for people of all skill levels. It uses the [[Electron]] GUI framework and is written in [[JavaScript]] so if you know Javascript the options for customisation are endless. It supports installation on various Linux distributions, macOS and Windows. ''Pulsar'' features a built-in package manager called ''PPM'' that can search for and install over 10,000 community packages uploaded to the [https://packages.pulsar-edit.dev/ Pulsar Package Repository]. The majority of these packages were written for Atom and were archived and copied before the original ''Atom.io'' website went offline<ref>[https://blog.pulsar-edit.dev/posts/20221127-confused-Techie-SunsetMisadventureBackend/ Pulsar Blog], Pulsar Edit, 2022-11-27 (Accessed: 2026-05-26)</ref>. Packages are also written in Javascript and can take advantage of [https://docs.pulsar-edit.dev/api/pulsar/latest/ Pulsar's API], Electron APIs and the entire [[Node.js]] ecosystem. ''Pulsar'' is designed to provide a good out of the box experience to all users. It comes with features that most people consider essential in a modern GUI text editor but not too many as to overwhelm a new user. Such features include the aforementioned built in package manager, IDE features for integration with language servers, [[Git]] integration, a customisable pane-based interface, in-built terminal and text editing features such as multiple cursors, snippets and semantic selections. It ships with built-in support for a large number of commonly used programming languages but can also be easily extended by downloading a package that provides that language. == History == ''Pulsar'' was created by a bunch of community members and fans of the Atom editor. When GitHub announced that they were sunsetting Atom<ref>[https://github.blog/news-insights/product-news/sunsetting-atom/ GitHub Blog], GitHub, 2022-06-08 (Accessed: 2026-05-26)</ref> some of the members of Atom Community decided that the editor should be forked and continued under community stewardship. However, disagreements between members arose in the direction that development should take and so the team that would later vote on the name ''Pulsar'' was created. In order to keep the project alive in the aftermath of the sunsetting announcement, the team had to move quickly. Branding, CI/CD, new build tooling, website, community areas, package backend and a focus on modernization to deprecate old features such as the areas of the application written in [[CoffeeScript]] and get onto modern and supported versions of Electron and Node.js. The first actual tagged version of a Pulsar release was made on 15 December 2022 - the same day that Atom.io finally went dark<ref>[https://blog.pulsar-edit.dev/posts/20221215-confused-Techie-v1.100.1-beta/ Pulsar Blog], Pulsar Edit, 2022-12-15 (Accessed: 2026-05-26)</ref> Since then there has been steady improvement - adding new features, updating and upgrading existing ones, migrating from unmaintained dependencies to better alternatives. == Installation == Pulsar is available for installation on most common operating systems: Windows, macOS (both Intel and Apple Silicon version) and most common Linux distributions. Multiple package and installation options are available through either official package releases or package manager support or through community maintained ones. For full instructions consult the Pulsar downloads page [https://pulsar-edit.dev/download/ pulsar-edit.dev/download] == Documentation == Extensive documentation can be found on the Pulsar website [https://docs.pulsar-edit.dev/ docs.pulsar-edit.dev/]. This includes guides, tutorials and references on how to use Pulsar as well as instructions on how to customise Pulsar and create new Packages. It also features Pulsar's API reference and that of the package backend. == References == 26df33cb762d33728809ab0c3801751cc69e664e 0 1243 5387 5334 2026-05-26T01:22:19Z YoshikageKira 367 WIP: Fixed shell definition, elaborated on shell types and some example feature a shell typically provides. Still work in progress. wikitext text/x-wiki {{Work In Progress}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: the [[Command-line interface]] (CLI) and the [[Graphical user interface]] (GUI). [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Features == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Uses redirection (<code>></code>, <code><</code>) and pipelines (<code><nowiki>|</nowiki></code>) to route text data between commands and files. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns and controls the process state using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exe</code><code>c</code>, etc. |Spawns and kills process when apps are open and closed via app launchers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. | |- !Environment Management | | |- !Device Interaction | | |} == Command Line Shells == {| class="wikitable" |+ |- ! Shell !! Links !! Decription |- | Bash || || Default shell for Linux operating systems |- | Zsh || || A shell that expands off the Korn shell. Default shell for MacOS |- | Xonsh || || A python based shell that has shared history between terminals. Also doubles as a superset of Python |- |Fish | | |- |Elvish | | |- |OSH |[https://oils.pub/osh.html Website] |A bash compatible shell with precise error printouts |- |YSH |[https://oils.pub/ysh.html Website] |A shell that describes itself as being a glue between typical shell, regex, python, YAML, and JSON |} == Graphical Shells == f1beb878b3e8c4a80e28c60456a61dc175023c3c 5388 5387 2026-05-26T01:26:56Z YoshikageKira 367 some rewording. wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[Command-line interface]] (CLI) based shells and [[Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Features == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Uses redirection (<code>></code>, <code><</code>) and pipelines (<code><nowiki>|</nowiki></code>) to route text data between commands and files. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns and controls the process state using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exe</code><code>c</code>, etc. |Spawns and kills process when apps are open and closed via app launchers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. | |- !Environment Management | | |- !Device Interaction | | |} == Command Line Shells == {| class="wikitable" |+ |- ! Shell !! Links !! Decription |- | Bash || || Default shell for Linux operating systems |- | Zsh || || A shell that expands off the Korn shell. Default shell for MacOS |- | Xonsh || || A python based shell that has shared history between terminals. Also doubles as a superset of Python |- |Fish | | |- |Elvish | | |- |OSH |[https://oils.pub/osh.html Website] |A bash compatible shell with precise error printouts |- |YSH |[https://oils.pub/ysh.html Website] |A shell that describes itself as being a glue between typical shell, regex, python, YAML, and JSON |} == Graphical Shells == 90070c3cac5e26f16e3f0fbf4acc03f22fb52dfc 5393 5388 2026-05-26T03:17:50Z MarkH 357 /* Command Line Shells */ link to zsh and fish articles wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[Command-line interface]] (CLI) based shells and [[Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Features == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Uses redirection (<code>></code>, <code><</code>) and pipelines (<code><nowiki>|</nowiki></code>) to route text data between commands and files. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns and controls the process state using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exe</code><code>c</code>, etc. |Spawns and kills process when apps are open and closed via app launchers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. | |- !Environment Management | | |- !Device Interaction | | |} == Command Line Shells == {| class="wikitable" |+ |- ! Shell !! Links !! Decription |- | Bash || || Default shell for Linux operating systems |- | [[Zsh]] || || A shell that expands off the Korn shell. Default shell on macOS |- | Xonsh || || A python based shell that has shared history between terminals. Also doubles as a superset of Python |- |[[Fish]] || || Friendly interactive shell | | |- |Elvish | | |- |OSH |[https://oils.pub/osh.html Website] |A bash compatible shell with precise error printouts |- |YSH |[https://oils.pub/ysh.html Website] |A shell that describes itself as being a glue between typical shell, regex, python, YAML, and JSON |} == Graphical Shells == e03ef4f10ee3efd7e981fdac49d30bacd2c790eb 5394 5393 2026-05-26T03:35:49Z YoshikageKira 367 WIP: Completed the shell features table. Still work in progress. wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[Command-line interface]] (CLI) based shells and [[Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Features == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Routes text data using redirection (<code>></code>, <code><</code>), pipelines (<code><nowiki>|</nowiki></code>), and built-ins like <code>read</code> or <code>mapfile</code> to capture input into variables/arrays. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns, limits, and controls process states using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exec</code>, and resource constraints via <code>ulimit</code>. |Spawns and kills processes when apps are opened and closed via graphical app launchers or task managers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. |Navigates and manages files and directories visually through a file manager (e.g., File Explorer, Finder). |- !Environment Management |Defines and propagates environment variables (like <code>PATH</code>) using <code>export</code> or startup scripts (<code>.profile</code>, <code>.bashrc</code>). |Modifies system configuration, system path, and user profile. through graphical apps such as settings panels. |- !Device Interaction |Reads from and writes directly to hardware devices using standard I/O redirection and device files. |Handles plug-and-play devices (e.g., mounting/ejecting flash drives) and manages peripherals via system settings. |} == Command Line Shells == {| class="wikitable" |+ |- ! Shell !! Links !! Decription |- | Bash || || Default shell for Linux operating systems |- | Zsh || || A shell that expands off the Korn shell. Default shell for MacOS |- | Xonsh || || A python based shell that has shared history between terminals. Also doubles as a superset of Python |- |Fish | | |- |Elvish | | |- |OSH |[https://oils.pub/osh.html Website] |A bash compatible shell with precise error printouts |- |YSH |[https://oils.pub/ysh.html Website] |A shell that describes itself as being a glue between typical shell, regex, python, YAML, and JSON |} == Graphical Shells == 26f25b4c19362e2ec083b0789de1a686ae00f6b4 5396 5394 2026-05-26T04:28:01Z YoshikageKira 367 /* Command Line Shells */ Updated the table and added more shells. Still work in progress. wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[Command-line interface]] (CLI) based shells and [[Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Features == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Routes text data using redirection (<code>></code>, <code><</code>), pipelines (<code><nowiki>|</nowiki></code>), and built-ins like <code>read</code> or <code>mapfile</code> to capture input into variables/arrays. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns, limits, and controls process states using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exec</code>, and resource constraints via <code>ulimit</code>. |Spawns and kills processes when apps are opened and closed via graphical app launchers or task managers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. |Navigates and manages files and directories visually through a file manager (e.g., File Explorer, Finder). |- !Environment Management |Defines and propagates environment variables (like <code>PATH</code>) using <code>export</code> or startup scripts (<code>.profile</code>, <code>.bashrc</code>). |Modifies system configuration, system path, and user profile. through graphical apps such as settings panels. |- !Device Interaction |Reads from and writes directly to hardware devices using standard I/O redirection and device files. |Handles plug-and-play devices (e.g., mounting/ejecting flash drives) and manages peripherals via system settings. |} == Command Line Shells == {| class="wikitable" |- ! Shell !! Links !POSIX Compliance ! Description |- |Csh |[[wikipedia:C_shell|Wikipedia]] |No |The C Shell. Developed with an interactive command history and a syntax modeled closely after the C programming language. |- |Sh |[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html POSIX Standard Ch 02] |Yes |The original Bourne Shell. Established the foundational grammar for UNIX command interpreters and serves as the baseline reference for standard shell compliance. |- |Ksh |[http://kornshell.com Website] |Yes (compatible)<ref name=":0">These shells are capable of reading and running standard, universal POSIX scripts. However, they also include non-standard extensions (like Bash's arrays or double-bracket tests). If you write scripts using these extra features, they will work perfectly within that shell but will fail if you try to run them in a strict, pure POSIX environment.</ref> |The Korn Shell. Developed as an extension of the Bourne shell syntax, integrating interactive features from <code>csh</code> while establishing the scripting extensions that formed the basis of POSIX. |- | Bash || [https://www.gnu.org/software/bash/ Website] |Yes (compatible)<ref name=":0" />|| The "Bourne-Again Shell." An open-source, backwards-compatible replacement for <code>sh</code> created for the GNU project. Incorporates functional features from <code>ksh</code> and <code>csh</code>. |- | Zsh || [https://www.zsh.org/ Website] |Yes (compatible)<ref name=":0" />|| A highly customizable shell primarily based on the Korn shell (<code>ksh</code>) and the Bourne-syntax family. The default shell for macOS since 2019, it introduces massively upgraded interactive features like advanced menu-based auto-completion, spellcheck, and native recursive searching. |- |Fish |[https://fishshell.com/ Website] |No |Friendly Interactive Shell. Implements a custom, non-POSIX scripting syntax designed around automatic syntax highlighting and menu-driven command completion. |- |Elvish |[https://elv.sh/ Website] |No |A modern shell featuring an expressive, programming-language-like syntax, structured data support, and a built-in interactive file manager. |- | Xonsh || [https://xon.sh/ Website] |No|| A Python based shell that features shared history across terminals and doubles as a superset of Python. |- |OSH |[https://oils.pub/osh.html Website] |Yes (compatible)<ref name=":0" /> |A Bash-compatible shell from the Oil project featuring precise error printouts and safer script execution. |- |Nushell |[https://www.nushell.sh/ Website] |No |A modern type of shell heavily inspired by PowerShell and functional programming. Rather than treating pipeline data as raw text, it passes structured data tables (objects with types) natively across commands. |- |YSH |[https://oils.pub/ysh.html Website] |No |A modern shell from the Oil project that acts as a bridge between traditional shell scripting, Python, YAML, and JSON. |} == Graphical Shells == // TODO == References == <references /> c13c55dcf1b2d150500b169edc72e3890ca76a43 5397 5396 2026-05-26T04:31:27Z YoshikageKira 367 /* Command Line Shells */ Add todo notes for reminder wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[Command-line interface]] (CLI) based shells and [[Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Features == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Routes text data using redirection (<code>></code>, <code><</code>), pipelines (<code><nowiki>|</nowiki></code>), and built-ins like <code>read</code> or <code>mapfile</code> to capture input into variables/arrays. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns, limits, and controls process states using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exec</code>, and resource constraints via <code>ulimit</code>. |Spawns and kills processes when apps are opened and closed via graphical app launchers or task managers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. |Navigates and manages files and directories visually through a file manager (e.g., File Explorer, Finder). |- !Environment Management |Defines and propagates environment variables (like <code>PATH</code>) using <code>export</code> or startup scripts (<code>.profile</code>, <code>.bashrc</code>). |Modifies system configuration, system path, and user profile. through graphical apps such as settings panels. |- !Device Interaction |Reads from and writes directly to hardware devices using standard I/O redirection and device files. |Handles plug-and-play devices (e.g., mounting/ejecting flash drives) and manages peripherals via system settings. |} == Command Line Shells == // TODO: Explain command line, command line interpreters, shell interpreters, and shell scripts {| class="wikitable" |- ! Shell !! Links !POSIX Compliance ! Description |- |Csh |[[wikipedia:C_shell|Wikipedia]] |No |The C Shell. Developed with an interactive command history and a syntax modeled closely after the C programming language. |- |Sh |[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html POSIX Standard Ch 02] |Yes |The original Bourne Shell. Established the foundational grammar for UNIX command interpreters and serves as the baseline reference for standard shell compliance. |- |Ksh |[http://kornshell.com Website] |Yes (compatible)<ref name=":0">These shells are capable of reading and running standard, universal POSIX scripts. However, they also include non-standard extensions (like Bash's arrays or double-bracket tests). If you write scripts using these extra features, they will work perfectly within that shell but will fail if you try to run them in a strict, pure POSIX environment.</ref> |The Korn Shell. Developed as an extension of the Bourne shell syntax, integrating interactive features from <code>csh</code> while establishing the scripting extensions that formed the basis of POSIX. |- | Bash || [https://www.gnu.org/software/bash/ Website] |Yes (compatible)<ref name=":0" />|| The "Bourne-Again Shell." An open-source, backwards-compatible replacement for <code>sh</code> created for the GNU project. Incorporates functional features from <code>ksh</code> and <code>csh</code>. |- | Zsh || [https://www.zsh.org/ Website] |Yes (compatible)<ref name=":0" />|| A highly customizable shell primarily based on the Korn shell (<code>ksh</code>) and the Bourne-syntax family. The default shell for macOS since 2019, it introduces massively upgraded interactive features like advanced menu-based auto-completion, spellcheck, and native recursive searching. |- |Fish |[https://fishshell.com/ Website] |No |Friendly Interactive Shell. Implements a custom, non-POSIX scripting syntax designed around automatic syntax highlighting and menu-driven command completion. |- |Elvish |[https://elv.sh/ Website] |No |A modern shell featuring an expressive, programming-language-like syntax, structured data support, and a built-in interactive file manager. |- | Xonsh || [https://xon.sh/ Website] |No|| A Python based shell that features shared history across terminals and doubles as a superset of Python. |- |OSH |[https://oils.pub/osh.html Website] |Yes (compatible)<ref name=":0" /> |A Bash-compatible shell from the Oil project featuring precise error printouts and safer script execution. |- |Nushell |[https://www.nushell.sh/ Website] |No |A modern type of shell heavily inspired by PowerShell and functional programming. Rather than treating pipeline data as raw text, it passes structured data tables (objects with types) natively across commands. |- |YSH |[https://oils.pub/ysh.html Website] |No |A modern shell from the Oil project that acts as a bridge between traditional shell scripting, Python, YAML, and JSON. |} == Graphical Shells == // TODO: Explain Graphical shells, create a comparison table for Graphical shells like the shell table above == References == <references /> 835580b9a9d5e64ae6a991ce8974bb55b2f10bbb 5399 5397 2026-05-26T04:43:27Z YoshikageKira 367 Updating wording of a header wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[Command-line interface]] (CLI) based shells and [[Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Capabilities == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Routes text data using redirection (<code>></code>, <code><</code>), pipelines (<code><nowiki>|</nowiki></code>), and built-ins like <code>read</code> or <code>mapfile</code> to capture input into variables/arrays. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns, limits, and controls process states using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exec</code>, and resource constraints via <code>ulimit</code>. |Spawns and kills processes when apps are opened and closed via graphical app launchers or task managers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. |Navigates and manages files and directories visually through a file manager (e.g., File Explorer, Finder). |- !Environment Management |Defines and propagates environment variables (like <code>PATH</code>) using <code>export</code> or startup scripts (<code>.profile</code>, <code>.bashrc</code>). |Modifies system configuration, system path, and user profile. through graphical apps such as settings panels. |- !Device Interaction |Reads from and writes directly to hardware devices using standard I/O redirection and device files. |Handles plug-and-play devices (e.g., mounting/ejecting flash drives) and manages peripherals via system settings. |} == Command Line Shells == // TODO: Explain command line, command line interpreters, shell interpreters, and shell scripts {| class="wikitable" |- ! Shell !! Links !POSIX Compliance ! Description |- |Csh |[[wikipedia:C_shell|Wikipedia]] |No |The C Shell. Developed with an interactive command history and a syntax modeled closely after the C programming language. |- |Sh |[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html POSIX Standard Ch 02] |Yes |The original Bourne Shell. Established the foundational grammar for UNIX command interpreters and serves as the baseline reference for standard shell compliance. |- |Ksh |[http://kornshell.com Website] |Yes (compatible)<ref name=":0">These shells are capable of reading and running standard, universal POSIX scripts. However, they also include non-standard extensions (like Bash's arrays or double-bracket tests). If you write scripts using these extra features, they will work perfectly within that shell but will fail if you try to run them in a strict, pure POSIX environment.</ref> |The Korn Shell. Developed as an extension of the Bourne shell syntax, integrating interactive features from <code>csh</code> while establishing the scripting extensions that formed the basis of POSIX. |- | Bash || [https://www.gnu.org/software/bash/ Website] |Yes (compatible)<ref name=":0" />|| The "Bourne-Again Shell." An open-source, backwards-compatible replacement for <code>sh</code> created for the GNU project. Incorporates functional features from <code>ksh</code> and <code>csh</code>. |- | Zsh || [https://www.zsh.org/ Website] |Yes (compatible)<ref name=":0" />|| A highly customizable shell primarily based on the Korn shell (<code>ksh</code>) and the Bourne-syntax family. The default shell for macOS since 2019, it introduces massively upgraded interactive features like advanced menu-based auto-completion, spellcheck, and native recursive searching. |- |Fish |[https://fishshell.com/ Website] |No |Friendly Interactive Shell. Implements a custom, non-POSIX scripting syntax designed around automatic syntax highlighting and menu-driven command completion. |- |Elvish |[https://elv.sh/ Website] |No |A modern shell featuring an expressive, programming-language-like syntax, structured data support, and a built-in interactive file manager. |- | Xonsh || [https://xon.sh/ Website] |No|| A Python based shell that features shared history across terminals and doubles as a superset of Python. |- |OSH |[https://oils.pub/osh.html Website] |Yes (compatible)<ref name=":0" /> |A Bash-compatible shell from the Oil project featuring precise error printouts and safer script execution. |- |Nushell |[https://www.nushell.sh/ Website] |No |A modern type of shell heavily inspired by PowerShell and functional programming. Rather than treating pipeline data as raw text, it passes structured data tables (objects with types) natively across commands. |- |YSH |[https://oils.pub/ysh.html Website] |No |A modern shell from the Oil project that acts as a bridge between traditional shell scripting, Python, YAML, and JSON. |} == Graphical Shells == // TODO: Explain Graphical shells, create a comparison table for Graphical shells like the shell table above == References == <references /> b86c853ca245c1b2b096f6c26f33037ebc57aad8 5400 5399 2026-05-26T04:46:19Z YoshikageKira 367 Updated todo wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[Command-line interface]] (CLI) based shells and [[Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Capabilities == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Routes text data using redirection (<code>></code>, <code><</code>), pipelines (<code><nowiki>|</nowiki></code>), and built-ins like <code>read</code> or <code>mapfile</code> to capture input into variables/arrays. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns, limits, and controls process states using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exec</code>, and resource constraints via <code>ulimit</code>. |Spawns and kills processes when apps are opened and closed via graphical app launchers or task managers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. |Navigates and manages files and directories visually through a file manager (e.g., File Explorer, Finder). |- !Environment Management |Defines and propagates environment variables (like <code>PATH</code>) using <code>export</code> or startup scripts (<code>.profile</code>, <code>.bashrc</code>). |Modifies system configuration, system path, and user profile. through graphical apps such as settings panels. |- !Device Interaction |Reads from and writes directly to hardware devices using standard I/O redirection and device files. |Handles plug-and-play devices (e.g., mounting/ejecting flash drives) and manages peripherals via system settings. |} == Command Line Shells == // TODO: Explain command line, terminal emulators, command line interpreters, shell interpreters, and shell scripts {| class="wikitable" |- ! Shell !! Links !POSIX Compliance ! Description |- |Csh |[[wikipedia:C_shell|Wikipedia]] |No |The C Shell. Developed with an interactive command history and a syntax modeled closely after the C programming language. |- |Sh |[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html POSIX Standard Ch 02] |Yes |The original Bourne Shell. Established the foundational grammar for UNIX command interpreters and serves as the baseline reference for standard shell compliance. |- |Ksh |[http://kornshell.com Website] |Yes (compatible)<ref name=":0">These shells are capable of reading and running standard, universal POSIX scripts. However, they also include non-standard extensions (like Bash's arrays or double-bracket tests). If you write scripts using these extra features, they will work perfectly within that shell but will fail if you try to run them in a strict, pure POSIX environment.</ref> |The Korn Shell. Developed as an extension of the Bourne shell syntax, integrating interactive features from <code>csh</code> while establishing the scripting extensions that formed the basis of POSIX. |- | Bash || [https://www.gnu.org/software/bash/ Website] |Yes (compatible)<ref name=":0" />|| The "Bourne-Again Shell." An open-source, backwards-compatible replacement for <code>sh</code> created for the GNU project. Incorporates functional features from <code>ksh</code> and <code>csh</code>. |- | Zsh || [https://www.zsh.org/ Website] |Yes (compatible)<ref name=":0" />|| A highly customizable shell primarily based on the Korn shell (<code>ksh</code>) and the Bourne-syntax family. The default shell for macOS since 2019, it introduces massively upgraded interactive features like advanced menu-based auto-completion, spellcheck, and native recursive searching. |- |Fish |[https://fishshell.com/ Website] |No |Friendly Interactive Shell. Implements a custom, non-POSIX scripting syntax designed around automatic syntax highlighting and menu-driven command completion. |- |Elvish |[https://elv.sh/ Website] |No |A modern shell featuring an expressive, programming-language-like syntax, structured data support, and a built-in interactive file manager. |- | Xonsh || [https://xon.sh/ Website] |No|| A Python based shell that features shared history across terminals and doubles as a superset of Python. |- |OSH |[https://oils.pub/osh.html Website] |Yes (compatible)<ref name=":0" /> |A Bash-compatible shell from the Oil project featuring precise error printouts and safer script execution. |- |Nushell |[https://www.nushell.sh/ Website] |No |A modern type of shell heavily inspired by PowerShell and functional programming. Rather than treating pipeline data as raw text, it passes structured data tables (objects with types) natively across commands. |- |YSH |[https://oils.pub/ysh.html Website] |No |A modern shell from the Oil project that acts as a bridge between traditional shell scripting, Python, YAML, and JSON. |} == Graphical Shells == // TODO: Explain Graphical shells, create a comparison table for Graphical shells like the shell table above == References == <references /> c53483411faf0cb4ab07a74910e74785593987ea 5417 5400 2026-05-26T09:54:54Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[Command-line interface]] (CLI) based shells and [[Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Capabilities == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Routes text data using redirection (<code>></code>, <code><</code>), pipelines (<code><nowiki>|</nowiki></code>), and built-ins like <code>read</code> or <code>mapfile</code> to capture input into variables/arrays. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns, limits, and controls process states using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exec</code>, and resource constraints via <code>ulimit</code>. |Spawns and kills processes when apps are opened and closed via graphical app launchers or task managers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. |Navigates and manages files and directories visually through a file manager (e.g., File Explorer, Finder). |- !Environment Management |Defines and propagates environment variables (like <code>PATH</code>) using <code>export</code> or startup scripts (<code>.profile</code>, <code>.bashrc</code>). |Modifies system configuration, system path, and user profile. through graphical apps such as settings panels. |- !Device Interaction |Reads from and writes directly to hardware devices using standard I/O redirection and device files. |Handles plug-and-play devices (e.g., mounting/ejecting flash drives) and manages peripherals via system settings. |} == Command Line Shells == // TODO: Explain command line, terminal emulators, command line interpreters, shell interpreters, and shell scripts {| class="wikitable" |- ! Shell !! Links !POSIX Compliance ! Description |- |Csh |[[wikipedia:C_shell|Wikipedia]] |No |The C Shell. Developed with an interactive command history and a syntax modeled closely after the C programming language. |- |Sh |[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html POSIX Standard Ch 02] |Yes |The original Bourne Shell. Established the foundational grammar for UNIX command interpreters and serves as the baseline reference for standard shell compliance. |- |Ksh |[http://kornshell.com Website] |Yes (compatible)<ref name=":0">These shells are capable of reading and running standard, universal POSIX scripts. However, they also include non-standard extensions (like Bash's arrays or double-bracket tests). If you write scripts using these extra features, they will work perfectly within that shell but will fail if you try to run them in a strict, pure POSIX environment.</ref> |The Korn Shell. Developed as an extension of the Bourne shell syntax, integrating interactive features from <code>csh</code> while establishing the scripting extensions that formed the basis of POSIX. |- | Bash || [https://www.gnu.org/software/bash/ Website] |Yes (compatible)<ref name=":0" />|| The "Bourne-Again Shell." An open-source, backwards-compatible replacement for <code>sh</code> created for the GNU project. Incorporates functional features from <code>ksh</code> and <code>csh</code>. |- | Zsh || [https://www.zsh.org/ Website] |Yes (compatible)<ref name=":0" />|| A highly customizable shell primarily based on the Korn shell (<code>ksh</code>) and the Bourne-syntax family. The default shell for macOS since 2019, it introduces massively upgraded interactive features like advanced menu-based auto-completion, spellcheck, and native recursive searching. |- |Fish |[https://fishshell.com/ Website] |No |Friendly Interactive Shell. Implements a custom, non-POSIX scripting syntax designed around automatic syntax highlighting and menu-driven command completion. |- |Elvish |[https://elv.sh/ Website] |No |A modern shell featuring an expressive, programming-language-like syntax, structured data support, and a built-in interactive file manager. |- | Xonsh || [https://xon.sh/ Website] |No|| A Python based shell that features shared history across terminals and doubles as a superset of Python. |- |OSH |[https://oils.pub/osh.html Website] |Yes (compatible)<ref name=":0" /> |A Bash-compatible shell from the Oil project featuring precise error printouts and safer script execution. |- |Nushell |[https://www.nushell.sh/ Website] |No |A modern type of shell heavily inspired by PowerShell and functional programming. Rather than treating pipeline data as raw text, it passes structured data tables (objects with types) natively across commands. |- |YSH |[https://oils.pub/ysh.html Website] |No |A modern shell from the Oil project that acts as a bridge between traditional shell scripting, Python, YAML, and JSON. |} == Graphical Shells == // TODO: Explain Graphical shells, create a comparison table for Graphical shells like the shell table above == References == <references /> ec86a9ed7be8ec46bc851f5990ab8f27fcde0e7c 0 679 5390 4791 2026-05-26T02:35:14Z MarkH 357 add license and source code link wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.54.0 (2026-04-20) [https://git-scm.com/] | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com | license = [[GPL-2.0-only]] | sourcecode = https://github.com/git/git }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git's early design emphasized a distributed workflow similar to BitKeeper's but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like [[GitHub]], which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. == References == fb58f07b01eb984b6a770b6694232881e68b05c1 5392 5390 2026-05-26T03:06:12Z MarkH 357 point to actual source repo rather than mirror wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.54.0 (2026-04-20) [https://git-scm.com/] | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com | license = [[GPL-2.0-only]] | sourcecode = https://git.kernel.org/pub/scm/git/git.git }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.], Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?], Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark], Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12], Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.], Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git's early design emphasized a distributed workflow similar to BitKeeper's but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like [[GitHub]], which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. == References == 516fd8e82f8ed43d2f339a8a5e6bd763afcc8959 0 1258 5391 2026-05-26T02:35:39Z MarkH 357 create redirect wikitext text/x-wiki #REDIRECT [[GNU General Public License]] 1fd0598843f98ab254b41567469fe18366788f4e 0 1241 5395 5308 2026-05-26T04:16:18Z MarkH 357 update current architectures wikitext text/x-wiki [[Category:Misc Operating Systems]] {{Stub}} {{DistributionInfobox | architectures = aarch64, i586, riscv64, x86_64 | caption = The Redox OS logo | defaultdesktops = Orbital | image = [[File:The Redox OS logo.png|thumb|The Redox OS Logo]] | packagemanager = pkg | releasemodel = In development | releasestatus = In development | title = Redox OS | usagetype = Desktop, Server | website = [https://redox-os.org/ redox-os.org] }} Redox OS is a general-purpose [[Operating System|operating system]] written in [[Rust]]. It aims to provide a fully functioning [[UNIX|Unix]]-like microkernel-based operating system, that is secure, reliable and free. It takes inspiration from [[Plan 9]], [[Minix]], [[seL4]], [[Linux]], [[OpenBSD]] and [[FreeBSD]].<ref>[https://doc.redox-os.org/book/ The Redox OS book]</ref> == References == <references /> 3886560e62429248f9f7226b3c827ef899b96a2c 0 322 5398 4744 2026-05-26T04:33:24Z MarkH 357 add license and source code to infobox wikitext text/x-wiki [[Category:Software]] {{Needs Citations}} {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] | license = [[MIT License|MIT]] | sourcecode = https://git.musl-libc.org/cgit/musl }} '''musl''' is a C standard library intended for operating systems based on the [[Linux kernel]], released under the [[MIT License]]. It was developed by Rich Felker as a clean, efficient, and standards-conformant libc implementation. == Usage on [[Operating System|Operating Systems]] == [[Linux Distributions|Linux distributions]] that use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * [[Sabotage]] * [[Morpheus Linux]] * [[Chimera Linux]] * [[Void Linux]] The seL4 microkernel ships with musl, for binaries that have been linked against glibc. [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. == Notable differences from [[Glibc]] and Other C Libraries == musl is noted to have chosen certain sacrifices in functionality as design choices for security. === utmp(x) and Other Accounting Functionality === The utmp/wtmp family of Unix and POSIX<ref>{{Cite|url=https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/utmpx.h.html|title=user accounting database definitions, The Open Group Base Specifications Issue 8 (IEEE Std 1003.1-2024)|author=The IEEE and The Open Group|year=2024|accessdate=2026-05-22}}</ref><ref>{{Cite|url=https://pubs.opengroup.org/onlinepubs/9799919799/functions/endutxent.html|title=user accounting database functions, The Open Group Base Specifications Issue 8 (IEEE Std 1003.1-2024)|author=The IEEE and The Open Group|year=2024|accessdate=2026-05-22}}</ref> functions have been removed due to security concerns<ref>{{Cite|url=https://wiki.musl-libc.org/faq.html#Q:-Why-is-the-utmp/wtmp-functionality-only-implemented-as-stubs?|title=musl libc FAQ|author=Kylie McClain|year=2016|accessdate=2026-05-22}}</ref><!-- NOTE: I got the author info for this citation from the git blame of the musl libc wiki: https://github.com/somasis/musl-wiki/blame/e8e065dd5aaf1a189bc659f347638f4b155fc3f4/faq.md#L90 -->. This decision breaks several programs that are useful on multi-user systems, such as wall, last, and who. [https://skarnet.org/software/utmps/ Skarnet implements a daemon which can provide such functionality on musl systems], however it is not included by default on most of these distributions. === Name Service Switch (nsswitch) === Glibc and most other ctandard C libraries on UNIX and Unix-like systems implement something known as the Name Service Switch, or, nsswitch<ref>{{Cite|url=https://skarnet.org/software/nsss/nsswitch.html|title=The problem with nsswitch|author=Skarnet|accessdate=2025-05-22}}</ref>. Musl does not implement these functions either, so [https://skarnet.org/software/nsss/ Skarnet has also provided another daemon for this]. == References == <references /> == See also == * [[Bionic libc]] * [[dietlibc]] * [[Glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] 5a34c28ce3050b3193a125624cc84fedea17254d 6 1259 5401 2026-05-26T05:48:47Z LilyWayLolz 354 Logo for Navidrome wikitext text/x-wiki == Summary == Logo for Navidrome == Licensing == {{CC-BY-4.0}} 816ead2aab52fd5edf0ea333e42821593bcb03f4 0 1123 5402 5263 2026-05-26T05:50:00Z LilyWayLolz 354 Added logo for navidrome wikitext text/x-wiki [[File:Navidrome logo.png|thumb|alt=Navidrome Logo]] [[Category:Software]] [https://navidrome.org Navidrome] is a locally-hosted music streaming server that allows users to upload one's personal music files onto it in order to create a personal music library. This music library can be streamed through various [https://foss.wiki/Category:Navidrome_Clients clients] to play one's locally-hosted music on other devices via a link pointing to the host server. 1fbd8b89df60ec988daed4358adfcec67003a9e6 6 1260 5403 2026-05-26T05:54:25Z LilyWayLolz 354 Logo for Psysonic, the Navidrome client wikitext text/x-wiki == Summary == Logo for Psysonic, the Navidrome client == Licensing == {{CC-BY-4.0}} 56b614d007d7f504ba6bfb7156417c1870bb0c64 6 1261 5404 2026-05-26T05:56:38Z LilyWayLolz 354 Icon for the Psysonic client app, and profile picture of Psychotoxical, the Psysonic developer, on Github wikitext text/x-wiki == Summary == Icon for the Psysonic client app, and profile picture of Psychotoxical, the Psysonic developer, on Github == Licensing == {{CC-BY-4.0}} f9360ef574dedf4da63087830c9f773d86fd7329 0 1121 5405 5270 2026-05-26T05:58:04Z LilyWayLolz 354 Added images wikitext text/x-wiki [[File:Psysonic icon.png|thumb|alt=Icon for the Psysonic application]] [[File:Psysonic logo.svg|thumb|alt=Promotional logo used for Psysonic]] [[Category:Software]] [[Category:Navidrome Clients]] [https://psysonic.de Psysonic] is a local music streaming client made for [[Navidrome]] servers. The client boasts a modern, sleek UI, native [https://last.fm last.fm] [[scrobbling]], and wide range of support for operating systems, including: Windows, MacOS, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [https://foss.wiki/Flatpak Flathub] release. d1cb739f6f14760a1ba958bdf9102e9ad2ad35cc 5406 5405 2026-05-26T05:58:50Z LilyWayLolz 354 wikitext text/x-wiki [[File:Psysonic icon.png|thumb|alt=Icon for the Psysonic application]] [[File:Psysonic logo.svg|thumb|alt=Promotional logo used for Psysonic]] [[Category:Software]] [[Category:Navidrome Clients]] [https://psysonic.de Psysonic] is a local music streaming client made for [[Navidrome]] servers. The client boasts a modern, sleek UI, native [https://last.fm last.fm] scrobbling, and wide range of support for operating systems, including: Windows, MacOS, and [[Linux]] - with a native package in [[APT]] , packages in the [[Arch User Repository]], and a [https://foss.wiki/Flatpak Flathub] release. 8ff623e5bc0069088e724172913eadbb752aa602 0 279 5407 5333 2026-05-26T06:14:20Z Sedot 397 added citation governance wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] or [[transactional-update]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[IceWM]] | usagetype = Desktop, Server | architectures = i686, x86-64, aarch64, ppc64le, s390x | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE (/ˌoʊpənˈsuːzə/) is a line of [[Linux distributions]] developed by the openSUSE Project and the SUSE S.A.<ref>[https://en.opensuse.org/openSUSE:Guiding_principles#Governance openSUSE Governance Structure], governance structure of openSUSE and SUSE, openSUSE wiki</ref> – a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == OpenSUSE stands out by having variations of the distributions: === Tumbleweed === Tumbleweed is the Rolling Release Distribution containing the latest [[openQA|openQA]] testet versions of all software. Tumbleweed is based on Factory, openSUSEs main development codebase, As soon as a openQA tests pass, a new Tumbleweed snapshot will be released – typically several times a week. === Slowroll === Please note, Slowroll is in beta stage. Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === Leap === Leap is the point release version, with a new release every year with older and more stable packages meant for business use. === Kalpa === Please note, Kalpa is in alpha stage. Kalpa is an atomic and transactional Linux desktop offering the KDE Plasma Desktop Environment. It's goal is to be easy to use and for people who "want to be stuff done" whitout messing with their operating system. Kalpa is based on Tumbleweed and MicroOS. === MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed ==References== 3f310369bbd39207e5ab37c565c23c30a6781bae 5416 5407 2026-05-26T09:54:44Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] or [[transactional-update]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[IceWM]] | usagetype = Desktop, Server | architectures = i686, x86-64, aarch64, ppc64le, s390x | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE (/ˌoʊpənˈsuːzə/) is a line of [[Linux distributions]] developed by the openSUSE Project and the SUSE S.A.<ref>[https://en.opensuse.org/openSUSE:Guiding_principles#Governance openSUSE Governance Structure], governance structure of openSUSE and SUSE, openSUSE wiki</ref> – a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == OpenSUSE stands out by having variations of the distributions: === Tumbleweed === Tumbleweed is the Rolling Release Distribution containing the latest [[openQA|openQA]] testet versions of all software. Tumbleweed is based on Factory, openSUSEs main development codebase, As soon as a openQA tests pass, a new Tumbleweed snapshot will be released – typically several times a week. === Slowroll === Please note, Slowroll is in beta stage. Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === Leap === Leap is the point release version, with a new release every year with older and more stable packages meant for business use. === Kalpa === Please note, Kalpa is in alpha stage. Kalpa is an atomic and transactional Linux desktop offering the KDE Plasma Desktop Environment. It's goal is to be easy to use and for people who "want to be stuff done" whitout messing with their operating system. Kalpa is based on Tumbleweed and MicroOS. === MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed ==References== b5ac659fa122ad1279c681d00534cbecdaf335c5 0 1222 5408 5327 2026-05-26T06:57:32Z Int 401 Fix infobox title wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox | image = [[File:Yt-dlp logo.svg|thumb]] | caption = yt-dlp | title = yt-dlp | releasestatus = Maintained | lastrelease = 2026.03.17, 2026-03-17 | firstrelease = 2021.01.07, 2021-01-07 | languages = [[Python]] | developers = [https://github.com/orgs/yt-dlp/people yt-dlp maintainers] | website = [https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] | license = Unlicense }} '''yt-dlp''' is a [[Python]] program for downloading videos from [https://www.youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. == Usage tips == {{Guide_Warning}} yt-dlp has many options, like [https://sponsor.ajay.app/ sponsorblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users may like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from a nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> to get a [[Manpages|manpage]] entry, or by using an online manpage such as [https://man.archlinux.org/man/yt-dlp.1 the archlinux online manpages]. Some of the most commonly used options are the <code>-o <output></code> to specify and output, and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> 0ab2900cb6e7bd4c9a3b71f33cc1790754821aad 5409 5408 2026-05-26T07:18:16Z Int 401 Clarify that yt-dlp doesn't only download from YouTube wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox | image = [[File:Yt-dlp logo.svg|thumb]] | caption = yt-dlp | title = yt-dlp | releasestatus = Maintained | lastrelease = 2026.03.17, 2026-03-17 | firstrelease = 2021.01.07, 2021-01-07 | languages = [[Python]] | developers = [https://github.com/orgs/yt-dlp/people yt-dlp maintainers] | website = [https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] | license = Unlicense }} '''yt-dlp''' is a [[CLI|command-line]] audio/video downloader that supports [https://github.com/yt-dlp/yt-dlp/blob/master/supportedsites.md thousands of sites] including [https://youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. == Usage tips == {{Guide_Warning}} yt-dlp has many options, like [https://sponsor.ajay.app/ sponsorblock] integrations, and being able to embed thumbnails and subtitles. Many of these options are not enabled by default, but many users may like them to be. To get around this, you can create an alias for yt-dlp.<syntaxhighlight lang="bash"> # Example from a nushell config, converted into bash. alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist' </syntaxhighlight>A full list of options can be found by running <code>man yt-dlp</code> to get a [[Manpages|manpage]] entry, or by using an online manpage such as [https://man.archlinux.org/man/yt-dlp.1 the archlinux online manpages]. Some of the most commonly used options are the <code>-o <output></code> to specify and output, and <code>-t <type></code> to specify a type, for example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up], you can do:<syntaxhighlight lang="bash"> yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # or if you have an alias set, you would do: # <your-alias> -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ </syntaxhighlight> 71b9f9b10b1742a912064961b670b40509b742c9 5410 5409 2026-05-26T07:42:25Z Int 401 Reword for clarity wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox | image = [[File:Yt-dlp logo.svg|thumb]] | caption = yt-dlp | title = yt-dlp | releasestatus = Maintained | lastrelease = 2026.03.17, 2026-03-17 | firstrelease = 2021.01.07, 2021-01-07 | languages = [[Python]] | developers = [https://github.com/orgs/yt-dlp/people yt-dlp maintainers] | website = [https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] | license = Unlicense }} '''yt-dlp''' is a [[CLI|command-line]] audio/video downloader that supports [https://github.com/yt-dlp/yt-dlp/blob/master/supportedsites.md thousands of sites] including [https://youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. == Usage tips == {{Guide_Warning}} yt-dlp can embed thumbnails/subtitles and integrate with [https://sponsor.ajay.app/ Sponsorblock] . For convenience, you can define a <code>yt</code> [[shell]] alias to enable these features by default:<syntaxhighlight lang="bash">alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist'</syntaxhighlight>Some of the most commonly used options are <code>-o <output></code> to specify the output file, and <code>-t <type></code> to specify the output file's type. For example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up] as an MP3 file named <code>Rick Astley - Never Gonna Give You Up.mp3</code> in the current directory:<syntaxhighlight lang="bash">yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # If you have an alias set, replace "yt-dlp" with the name of your alias</syntaxhighlight>A full list of options can be found by running <code>yt-dlp --help</code>. e3fe7b4faf265ef9ef7549bea083fe79eceab6cd 5411 5410 2026-05-26T07:56:55Z Int 401 Provide installation methods wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox | image = [[File:Yt-dlp logo.svg|thumb]] | caption = yt-dlp | title = yt-dlp | releasestatus = Maintained | lastrelease = 2026.03.17, 2026-03-17 | firstrelease = 2021.01.07, 2021-01-07 | languages = [[Python]] | developers = [https://github.com/orgs/yt-dlp/people yt-dlp maintainers] | website = [https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] | license = Unlicense }} '''yt-dlp''' is a [[CLI|command-line]] audio/video downloader that supports [https://github.com/yt-dlp/yt-dlp/blob/master/supportedsites.md thousands of sites] including [https://youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. == Installation == === Binaries === yt-dlp releases [https://github.com/yt-dlp/yt-dlp/releases/latest/ standalone executable binaries on GitHub]. === pip === yt-dlp is published on the Python package registry. You can install it using [https://pip.pypa.io/en/stable/ pip]:<syntaxhighlight lang="bash">pip install yt-dlp</syntaxhighlight> === Arch Linux === yt-dlp is packaged on the official Arch Linux repositories. You can install it using [[Pacman]]:<syntaxhighlight lang="bash"> sudo pacman -S yt-dlp </syntaxhighlight> == Usage tips == {{Guide_Warning}} yt-dlp can embed thumbnails/subtitles and integrate with [https://sponsor.ajay.app/ Sponsorblock] . For convenience, you can define a <code>yt</code> [[shell]] alias to enable these features by default:<syntaxhighlight lang="bash">alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist'</syntaxhighlight>Some of the most commonly used options are <code>-o <output></code> to specify the output file, and <code>-t <type></code> to specify the output file's type. For example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up] as an MP3 file named <code>Rick Astley - Never Gonna Give You Up.mp3</code> in the current directory:<syntaxhighlight lang="bash">yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # If you have an alias set, replace "yt-dlp" with the name of your alias</syntaxhighlight>A full list of options can be found by running <code>yt-dlp --help</code>. a409757221de15bb095b9bf3ddb8cfc596f6dfb7 0 1231 5412 5205 2026-05-26T08:44:19Z Sedot 397 add deadbeef wikitext text/x-wiki {{Stub}} This page lists local music playing [[software]] to enjoy your local music collection of flacs, mp3s, etc. {| class="wikitable" !Name |External Link !Description |- |[[Elisa]] |[https://apps.kde.org/de/elisa/ Website] |Simple music player made by [[KDE]]. |- |DeaDBeeF |[https://deadbeef.sourceforge.io Website] |Modular audio player which supports plugins and customisation. |- |} affc87c21d98ee7d3a776a1b2fec2dfc414d8413 0 1262 5414 2026-05-26T09:06:08Z Veri 398 Redirected page to [[Derivative]] wikitext text/x-wiki #REDIRECT [[Derivative]] 910aaadd033b87403c699fb8fa24113446af30a1 0 1247 5420 5375 2026-05-26T09:55:24Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[Type Script]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/cinnyapp/cinny }} [[Category:Software]] [[File:Cinny-Unredacted.org.png|thumb|A photo of Cinny in the Unredacted Matrix server chat]] '''Cinny''' is a free and open source [[Matrix]] client focused on providing a simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, along with the browser<ref name=":0">{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. It currently uses the [https://github.com/matrix-org/matrix-js-sdk matrix-js-sdk] but is in the process on replacing it with a custom one, as such, it is not currently accepting contributions<ref>{{Cite|url=https://github.com/cinnyapp/cinny|title=Cinny GitHub repo|author=Cinny contributors|year=2026-05-23|accessdate=2026-05-25}}</ref>. {| class="wikitable" |+Supported features<ref name=":0" /> !Name !Supported? |- |E2EE |Yes |- |Spaces |Yes |- |Voice chat (1:1) |Yes<ref name=":1">{{Cite|url=https://github.com/matrix-org/matrix.org/issues/3418|title=Cinny supports MatrixRTC|author=spaetz|year=May 2026|accessdate=2026-05-25}}</ref> |- |Voice chat ([[Jitsi]]) |Yes<ref name=":1" /> |- |Threads |No |- |Legacy SSO |Yes |- |Multiple accounts |No |- |Multiple languages |No |} Note that [https://matrix.org/ecosystem/clients/cinny/ the page listing Cinny's features on Matrix.org] is outdated, as it now supports Voice chat<ref name=":1" />. c1919635f13e86689579b53f9e8bda3572faafd0 3000 1263 5421 2026-05-26T10:41:07Z Hyperreal 388 Init Guide:Mass_delete_repos_on_Codeberg_Forgejo_or_Gitea wikitext text/x-wiki {{GuideWarning}} <blockquote> CAUTION: There is no confirmation when deleting repos in this manner, and deleting them is an irreversible process. So make sure you have entered them correctly or have them backed up elsewhere. </blockquote> First, you'll need an access token, which you can generate under User Settings -> Applications. Make sure it has at least read and write access for repository and user. == Delete select repos == You'll need to change the <code>INSTANCE_URL</code>, <code>INSTANCE_USER</code>, and <code>INSTANCE_TOKEN</code> values in this script below to those of your Codeberg, Forgejo, or Gitea instance. The values used below are just examples. <syntaxhighlight lang="bash"> #!/usr/bin/env bash set -euo pipefail # Change these INSTANCE_URL=https://codeberg.org INSTANCE_USER=hyperreal INSTANCE_TOKEN=cd188e90f2f03eed57b1971fb16329b1b919a2bb # Add the repository names to an array. E.g., if your repo is located at # https://codeberg.org/hyperreal/dotfiles, the name you would add would be # "dotfiles". repos=("repo0", "repo1", "dotfiles", "repo2") # Iterate through the array and delete each item using curl. for repo in "${repos[@]}"; do echo "Deleting repository: ${repo}" curl -s \ -u "${INSTANCE_USER}:${INSTANCE_TOKEN}" \ -X DELETE \ "${INSTANCE_URL}/api/v1/repos/${INSTANCE_USER}/${repo}" done </syntaxhighlight> == Delete all the repos == If for whatever reason you want to delete all the repos on your account, change the line with the <code>repos=("repo0", "repo1", "dotfiles", "repo2")</code> array to the following. This will query the API for the names of all your repos with curl and read them into an array: <syntaxhighlight lang="bash"> readarray -t repos < <(curl -s -u "${INSTANCE_USER}:${INSTANCE_TOKEN}" "${INSTANCE_URL}/api/v1/users/${INSTANCE_USER}/repos?limit=100" | jq -r '.[].name') </syntaxhighlight> 8b9b7be091da5604fda96b2f014a4e69fe65fb2d 0 1142 5422 4798 2026-05-26T12:33:20Z Int 401 Reword for clarity wikitext text/x-wiki {{stub}} Windows is a proprietary [[Operating System|operating system]] developed by Microsoft. While originally catered towards personal computers, Windows now offers versions such as Windows Server, Windows IoT, or Windows LTSC. It was first released in November 20, 1985 as Windows 1.0 with a graphical user interface.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Microsoft_Windows|title=Microsoft Windows Wikipedia Entry|accessdate=2026}}</ref> == References == f0cad6987a2b618ae85db482a81184502c339f7e 5423 5422 2026-05-26T12:34:02Z Int 401 or -> and wikitext text/x-wiki {{stub}} Windows is a proprietary [[Operating System|operating system]] developed by Microsoft. While originally catered towards personal computers, Windows now offers versions such as Windows Server, Windows IoT, and Windows LTSC. It was first released in November 20, 1985 as Windows 1.0 with a graphical user interface.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Microsoft_Windows|title=Microsoft Windows Wikipedia Entry|accessdate=2026}}</ref> == References == 4b34d3292c226d5583a054be5b098944ad01b60e 5431 5423 2026-05-26T13:56:08Z Int 401 Mention Wine wikitext text/x-wiki {{stub}} Windows is a proprietary [[Operating System|operating system]] developed by Microsoft. While originally catered towards personal computers, Windows now offers versions such as Windows Server, Windows IoT, and Windows LTSC. It was first released in November 20, 1985 as Windows 1.0 with a graphical user interface.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Microsoft_Windows|title=Microsoft Windows Wikipedia Entry|accessdate=2026}}</ref> On [[UNIX]]-like operating systems (i.e. [[Linux kernel|Linux]] and [[MacOS]]), you can use the [[Wine]] compatibility layer to run applications designed for Windows. == References == 30b403f0272331d2fc7cb56d8a4fe0705fbf89a0 5432 5431 2026-05-26T13:58:11Z Int 401 Reword for clarity wikitext text/x-wiki {{stub}} Windows is a proprietary [[Operating System|operating system]] developed by Microsoft. While originally catered towards personal computers, Windows now offers versions such as Windows Server, Windows IoT, and Windows LTSC. It was first released in November 20, 1985 as Windows 1.0 with a graphical user interface.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Microsoft_Windows|title=Microsoft Windows Wikipedia Entry|accessdate=2026}}</ref> To run Windows applications on [[UNIX]]-like operating systems (i.e. [[Linux kernel|Linux]] and [[MacOS]]), you can use the [[Wine]] compatibility layer. == References == 275fd65c0417124b0207fcd8c8cea9080633f95b 6 1264 5424 2026-05-26T12:42:38Z Int 401 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1265 5425 2026-05-26T12:45:29Z Int 401 Create Wine stub wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = Wine | releasestatus = Active | lastrelease = Stable: 11.0 Preview: 11.9 | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago | image = Wine Logo.png }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. 96ef077bc324ccc6590e7ba302275c459db8999e 5426 5425 2026-05-26T12:50:33Z Int 401 Cite release date sources wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = Wine | releasestatus = Active | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago | image = Wine Logo.png }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. dfed7f55d78e89580cb403bf3b687e1dfe2b904a 5427 5426 2026-05-26T13:15:56Z Int 401 Add dxvk section wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = Wine | releasestatus = Active | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago | image = Wine Logo.png }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. === Performance === ==== dxvk ==== By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). 9c45169589712cb6742df202d07f9c1673f6efe2 5428 5427 2026-05-26T13:41:52Z Int 401 Add installation and usage sections wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = Wine | releasestatus = Active | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago | image = Wine Logo.png }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. === Installation === ==== Arch Linux ==== Wine is on the official Arch Linux repositories. You can install it using [[Pacman]]:<syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight>To install the staging build:<syntaxhighlight lang="sh"> sudo pacman -S wine-staging </syntaxhighlight> === Usage === Wine is a [[CLI|command-line]] program. Supply a Windows executable file (.exe) to run it:<syntaxhighlight lang="sh"> wine <path to executable> </syntaxhighlight> ==== Prefixes ==== A Wine prefix is a directory where Wine operates. It contains a minimal Windows filesystem (a.k.a. ''C: drive''). By default, this is in <code>~/.wine</code>. To change it, modify the <code>WINEPREFIX</code> environment variable. For example, to run Wine with a prefix at <code>myprefix/</code>:<syntaxhighlight lang="sh"> WINEPREFIX=myprefix wine application.exe </syntaxhighlight> === Performance === ==== dxvk ==== By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). ebfa9bf46528cf714adcb5db127d9ecf4c211d07 5429 5428 2026-05-26T13:42:54Z Int 401 Minor rewording wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = Wine | releasestatus = Active | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago | image = Wine Logo.png }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. === Installation === ==== Arch Linux ==== Wine is on the official Arch Linux repositories. You can install it using [[Pacman]]:<syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight>To install the staging build:<syntaxhighlight lang="sh"> sudo pacman -S wine-staging </syntaxhighlight> === Usage === Wine is a [[CLI|command-line]] program. Supply a Windows executable file (.exe) to run it:<syntaxhighlight lang="sh"> wine <path to executable> </syntaxhighlight> ==== Prefixes ==== A Wine prefix is a directory where Wine operates. It contains a minimal Windows filesystem (a.k.a. ''C: drive''). By default, this is <code>~/.wine</code>. To change it, modify the <code>WINEPREFIX</code> environment variable. For example, to run Wine at <code>myprefix/</code>:<syntaxhighlight lang="sh"> WINEPREFIX=myprefix wine application.exe </syntaxhighlight> === Performance === ==== dxvk ==== By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). 4a37a54e6451dd215ca23a5644b265b39665ba60 5430 5429 2026-05-26T13:47:52Z Int 401 Change release status to "Maintained" for consistency wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = Wine | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago | image = Wine Logo.png }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. === Installation === ==== Arch Linux ==== Wine is on the official Arch Linux repositories. You can install it using [[Pacman]]:<syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight>To install the staging build:<syntaxhighlight lang="sh"> sudo pacman -S wine-staging </syntaxhighlight> === Usage === Wine is a [[CLI|command-line]] program. Supply a Windows executable file (.exe) to run it:<syntaxhighlight lang="sh"> wine <path to executable> </syntaxhighlight> ==== Prefixes ==== A Wine prefix is a directory where Wine operates. It contains a minimal Windows filesystem (a.k.a. ''C: drive''). By default, this is <code>~/.wine</code>. To change it, modify the <code>WINEPREFIX</code> environment variable. For example, to run Wine at <code>myprefix/</code>:<syntaxhighlight lang="sh"> WINEPREFIX=myprefix wine application.exe </syntaxhighlight> === Performance === ==== dxvk ==== By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). 8014400c18dc8ef03d5c3ab87afe4361350131c1 0 625 5433 4409 2026-05-26T13:59:55Z Tungnon1222 314 updated to reflect CachyOS latest live iso release wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[XFCE|Xfce]] (comes with XFCE bundle) * [[GNOME]] (comes with GNOME bundle) * [[COSMIC]] (comes with COSMIC bundle) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Only KDE Plasma and XFCE come with preconfigured. Other Desktop Environments come as their default states. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> f21ac0a4d67366d54680ba6a40505672a89833f8 5435 5433 2026-05-26T14:13:58Z Tungnon1222 314 /* Desktop Environments */ wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with XFCE bundle) * [[COSMIC]] (comes with COSMIC bundle) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options KDE Plasma, GNOME, XFCE, and COSMIC are already usable OOTB without configurations or any additions. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 448afa8fbcc6802d5addd75ba9cea3ae6e91640e 5436 5435 2026-05-26T14:15:48Z Tungnon1222 314 /* Window Managers */ wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with XFCE bundle) * [[COSMIC]] (comes with COSMIC bundle) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options KDE Plasma, GNOME, XFCE, and COSMIC are already usable OOTB without configurations or any additions. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] Out of these options: niri and Mangowc are usable OOTB with dotfiles and shells for pseudo desktop environment experience. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 4f5945e1ffb29647aa8e4fc51fe0d41fc8cb4a7b 5438 5436 2026-05-26T14:22:40Z Tungnon1222 314 wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with XFCE bundle) * [[COSMIC]] (comes with COSMIC bundle) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options: KDE Plasma, GNOME, Xfce, and COSMIC are the most usable out of the box. KDE Plasma and GNOME come preconfigured by CachyOS. Xfce includes the Xfce goodies bundle. COSMIC comes with the full COSMIC desktop stack. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] Out of these options, niri and MangoWC are the most usable out of the box. niri comes preconfigured with Noctalia Shell, while MangoWC comes preconfigured with Dank Material Shell. These provide a more complete pseudo-desktop experience than the other window manager options. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> c9b1c23457d49973b4b35631c780a73b7479c52d 5439 5438 2026-05-26T14:23:13Z Tungnon1222 314 /* Window Managers */ wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with XFCE bundle) * [[COSMIC]] (comes with COSMIC bundle) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options: KDE Plasma, GNOME, Xfce, and COSMIC are the most usable out of the box. KDE Plasma and GNOME come preconfigured by CachyOS. Xfce includes the Xfce goodies bundle. COSMIC comes with the full COSMIC desktop stack. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] Out of these options: niri and MangoWC are the most usable out of the box. niri comes preconfigured with Noctalia Shell, while MangoWC comes preconfigured with Dank Material Shell. These provide a more complete pseudo-desktop experience than the other window manager options. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 83d804141767becfb2c240ffaf2b10b8205a3bd4 5440 5439 2026-05-26T14:23:55Z Tungnon1222 314 /* Desktop Environments */ wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with Xfce goodies bundle) * [[COSMIC]] (complete COSMIC stack) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options: KDE Plasma, GNOME, Xfce, and COSMIC are the most usable out of the box. KDE Plasma and GNOME come preconfigured by CachyOS. Xfce includes the Xfce goodies bundle. COSMIC comes with the full COSMIC desktop stack. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] Out of these options: niri and MangoWC are the most usable out of the box. niri comes preconfigured with Noctalia Shell, while MangoWC comes preconfigured with Dank Material Shell. These provide a more complete pseudo-desktop experience than the other window manager options. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> c5a231678fbd9a89c14dc584b9b1fa14a847fb72 5441 5440 2026-05-26T14:26:03Z Tungnon1222 314 /* Window Managers */ wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with Xfce goodies bundle) * [[COSMIC]] (complete COSMIC stack) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options: KDE Plasma, GNOME, Xfce, and COSMIC are the most usable out of the box. KDE Plasma and GNOME come preconfigured by CachyOS. Xfce includes the Xfce goodies bundle. COSMIC comes with the full COSMIC desktop stack. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] Out of these options: niri and MangoWC are the most usable out of the box. niri comes preconfigured with Noctalia Shell, while MangoWC comes preconfigured with Dank Material Shell. These provide a more complete desktop-like experience than the other window manager options. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 8c50bd6323c9d71127f31811c279bd0e5cabe823 5442 5441 2026-05-26T14:27:48Z Tungnon1222 314 /* Window Managers */ wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with Xfce goodies bundle) * [[COSMIC]] (complete COSMIC stack) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options: KDE Plasma, GNOME, Xfce, and COSMIC are the most usable out of the box. KDE Plasma and GNOME come preconfigured by CachyOS. Xfce includes the Xfce goodies bundle. COSMIC comes with the full COSMIC desktop stack. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] Out of these options: niri and MangoWC are the most usable out of the box. niri comes preconfigured with Noctalia Shell, while MangoWC comes preconfigured with Dank Material Shell. These come with more complete "pseudo desktop experience" than the other options here. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 794812c28d505bdde6626d6acdb3de33984b0226 5443 5442 2026-05-26T14:31:25Z Tungnon1222 314 /* Desktop Environments */ wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]], [[niri]], [[i3]], [[Qtile]], [[Wayfire]], [[GNOME]], [[XFCE]], [[bspwm]], [[budgie]], [[cinnamon]], [[cosmic]], [[hyprland]], [[lxde]], [[lxqt]], [[mate]], [[openbox]], [[sway]], [[ukui]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with Xfce goodies bundle) * [[COSMIC]] (complete COSMIC stack) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options: KDE Plasma, GNOME, Xfce, and COSMIC are more complete compared to other options here while KDE Plasma is the most polished option out of these due to being the distro's default. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] Out of these options: niri and MangoWC are the most usable out of the box. niri comes preconfigured with Noctalia Shell, while MangoWC comes preconfigured with Dank Material Shell. These come with more complete "pseudo desktop experience" than the other options here. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 01edbfc70f68b6ce8693d391c82a68c4dd7a35c8 3000 914 5434 4158 2026-05-26T14:00:13Z MysteryBirb 353 Removed all AI slop and changed image to thumbs for now wikitext text/x-wiki {{Needs Citations}} {{cleanup}} {{Stub}} = Checking the Boot Mode = [[File:CheckUEFI-1.png|right|frameless]] [[File:CheckUEFI-2.png|right|frameless]] There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> - Your system is using UEFI mode. #* If the value is <code>Legacy</code> - Your system is using Legacy BIOS mode. It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. = Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|center|thumb]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|center|thumb]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' - This is a GPT disk. #* If it says '''Master Boot Record''' - This is an MBR disk. The MBR system is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data''') or use a separate physical disk. 94306876f56ba1ed7aedcf3bda1d80203e979d32 5437 5434 2026-05-26T14:22:20Z MysteryBirb 353 Fixed Images and added WIP notice and a stub notice wikitext text/x-wiki {{Needs Citations}} {{cleanup}} {{Stub}} = Checking the Boot Mode = There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. [[File:CheckUEFI-1.png||none|700px]] # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> - Your system is using UEFI mode. #* If the value is <code>Legacy</code> - Your system is using Legacy BIOS mode. [[File:CheckUEFI-2.png|none|700px]] It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. = Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|none|700px]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|none|700px]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' - This is a GPT disk. #* If it says '''Master Boot Record''' - This is an MBR disk. The MBR partition scheme is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data''') or use a separate physical disk. == The rest of the Guide is work in progress. == 917d280f00fd7f29f9f5a10d7612d957b41948ab 0 1069 5444 4351 2026-05-26T15:03:53Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/topic/ARPANET|title=ARPANET|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>ARPANET (Advanced Research Projects Agency Network) was the first large-scale packet-switching network and the direct predecessor of the modern internet. Developed under the [https://www.war.gov/ United States Department of Defense]{{Dead Link|2026-05-26|403}}, ARPANET was designed to enable reliable communication between geographically distributed computers and research institutions. It introduced fundamental networking concepts, including packet switching, distributed routing, and host-to-host communication, which remain central to internet architecture today. ---- == Purpose == <ref>{{Cite|url=https://www.rand.org/pubs/research_memoranda/RM3420.html|title=The ARPA Network|author=Paul Baran|year=1964|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of ARPANET was to facilitate resource sharing and communication among researchers working on government-funded computing projects. It aimed to allow multiple institutions to access computing power, software, and data remotely while maintaining network resilience in the event of partial system failures. ARPANET also served as an experimental platform for testing new networking protocols and concepts, laying the groundwork for future global networking systems. ---- == History == <ref>{{Cite|url=https://groups.csail.mit.edu/medg/people/psz/Licklider.html|title=Man-Computer Symbiosis|author=J. C. R. Licklider|year=1960|accessdate=Retrieved on December 19, 2025}}</ref>ARPANET emerged during the [[wikipedia:Cold_War|Cold War]] as part of advanced research initiatives in computing and communications. * '''1962''': J. C. R. Licklider proposed the concept of an “Intergalactic Computer Network,” outlining the idea of interconnected computers. * '''1966''': ARPA formally initiated the ARPANET project. * '''1969''': The first ARPANET connection was established between UCLA and the Stanford Research Institute; the first message was transmitted. * '''1971''': Electronic mail (email) was introduced on ARPANET, rapidly becoming its most popular application. * '''1973''': International connections were added, expanding ARPANET beyond the United States. * '''1983''': ARPANET officially transitioned to the TCP/IP protocol suite, a defining moment in internet history. * '''1990''': ARPANET was formally decommissioned, having fulfilled its role as a foundational research network. ---- == Types == ARPANET itself was not divided into types in the modern sense, but it evolved through architectural and functional phases: * '''Early ARPANET''' focused on basic host-to-host communication using Interface Message Processors (IMPs). * '''Expanded ARPANET''' supported multiple applications such as email, file transfer, and remote login. * '''Post-TCP/IP ARPANET''' functioned as part of a larger internetwork, integrating seamlessly with other emerging networks. ---- == Significance == ARPANET is widely regarded as the technological foundation of the internet. Its development introduced core principles such as packet switching, decentralized networking, and standardized communication protocols. Many modern internet technologies, including email, routing protocols, and distributed systems, originated from ARPANET research. The project also fostered a collaborative research culture that directly influenced the evolution of networking, [[cybersecurity]], and computer science as academic disciplines. 20509ed52295cabfc46b80969438ddc5cf25f005 0 848 5445 4109 2026-05-26T15:09:14Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[category:Linux Distributions]] [[category:Desktop Environments]] {{stub}} {{DistributionInfobox | title = CyberOS | image = [[File:CyberOS_Logo.png|CyberOS Project Logo|frameless]] | caption = CyberOS Project Logo | releasestatus = Discontinued | releasemodel = Rolling/Stable Release | packagemanager = [[pacman]], [[apt]] | defaultdesktops = [[#CyberDE|CyberDE]] | usagetype = Mainly desktop | architectures = aarch64, x86_64 | website = [https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ getcyberos.org] }} '''CyberOS''', also known as '''CutefishOS''', was a Linux distribution based on [[Arch Linux]], shipping with a custom [[Desktop Environment|desktop environment]] named '''CyberDE'''. It was created in 2020 by Reven Martin<ref>[https://github.com/madonuko/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://github.com/CyberOS/cyber-launcher/blob/05b9e5702c0e5b0ee6c4546298434a2567187c92/src/main.cpp#L2 cyber-launcher/src/main.cpp at 05b9e5702c0e5b0ee6c4546298434a2567187c92 · madonuko/cyber-launcher], CyberOS Team, 2020 (Accessed: 2025-08-10)</ref><ref>[https://web.archive.org/web/20210603115851/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2021 (Accessed: 2021-06-03)</ref> and was discontinued in around 2022 to 2023<ref>[https://web.archive.org/web/20220514154048/https://getcyberos.org/#/ CyberOS], CyberOS Team, 2022 (Accessed: 2022-05-14)</ref>. The source code for CyberOS and CyberDE was deleted by the author in around April 2021, with all commit histories wiped<ref>[https://github.com/cutefishos/launcher/commit/13932e9ca9635ef152a136ec7c0da321b6bab812 init · cutefishos/launcher@13932e9], CutefishOS Team, 2021 (Accessed: 2025-08-11)</ref> and moved from the [https://github.com/CyberOS CyberOS organisation] to the [https://github.com/CutefishOS CutefishOS organisation] on [[GitHub]]. == History == CyberOS was created as a successor to [[PandaOS]] by Reven Martin (who was later renamed to Reion Wong) in around August, 2020.<ref>[https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 reionwong (Reion Wong)], GitHub ([https://web.archive.org/web/20250810155342/https://github.com/reionwong?tab=overview&from=2020-08-01&to=2020-08-31 Accessed]: 2025-08-10)</ref> Wong initially created the desktop environment and named it ''Cyber''. As work progressed, a team of 6 was formed<ref>[https://github.com/madonuko/cyberos.github.io/commit/75229a32d71cb00008da97a8799c0ecdd809602c About: Initial design · madonuko/cyberos.github.io@75229a3], CyberOS Team, 2021 (Accessed: 2025-08-11)</ref>. The team decided that a proper environment was needed to test and possibly distribute the [[Desktop Environments|DE]], and [[Arch Linux]] was chosen. Thus, CyberOS was born. === The Purge === In early 2021, Wong attempted to register the trademark for CyberOS in mainland China, but failed, since it was deemed too close to another registered trademark “Syber”. Later, Wong kicked out all other team members from the GitHub organisation and created CutefishOS, which was rebased to [[Ubuntu]]. Shortly after, the GitHub handle was renamed to ''reionwong''. The source code in the original organisation was either made private or deleted entirely, and the code in the new organisation left no trace of the old commits; and credits were removed and not given to the other team members. One of the core team members, omame, held the ownership to the website, which is why it remained for a few more months, as seen in the web archives, even after the ungraceful code purge by Wong. Some members tried to maintain CyberOS, but the light was shortly stolen due to Manjaro's announcement of CutefishOS's adoption as a new edition.<ref>[https://forum.manjaro.org/t/manjaro-cutefishde-spin-v0-2-2021-06-06-build-released/69217 Manjaro CutefishDE Spin v0.2 (2021-06-06 Build) released - Announcements / Releases], Manjaro Linux Forum, 2021 (Accessed: 2025-08-11)</ref> Even though omame maintained a fork<ref>[https://web.archive.org/web/20210527121341/git.omame.tech/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-05-27)</ref><ref>[https://web.archive.org/web/20211222011553/git.omame.xyz/CyberOS CyberOS], omame git, 2021 (Accessed: 2021-12-22)</ref>, the project was announced discontinued, mainly due to lack of manpower. The new CutefishOS team, which was rebased to Sichuan, also did not live long, due to lack of Western support, and silently died out between mid-2021 and 2022. === CutefishOS Reborn === CutefishOS Reborn was a Western community's attempt to revive CutefishOS's development. It gauged some interest but very quickly died off in mid-2022. === LingmoOS === [https://github.com/LingmoOS/LingmoOS LingmoOS] is an active revival<ref>[https://github.com/orgs/cutefishos/discussions/22 Is this project dead or still in development? · cutefishos · Discussion #22], GitHub, 2023 (Accessed: 2025-08-11)</ref> of CutefishOS, but it has not received major attention from the media. == CyberDE == [[File:VSCode In Cutefish.png|thumb|right|Visual Studio Code running on CutefishDE.<ref>[https://cutefishos.com CutefishOS], Cutefish Team, 2025 (Accessed: 2025-08-11)</ref>]] The desktop environment that came with CyberOS, usually referred to as ''Cyber'' or ''CyberDE'', was made using Qt5 and was commonly said to resemble the look and feel of [[MacOS|Mac OS X]].<ref>[https://wiki.archlinux.org/title/Cutefish Cutefish], ArchWiki (Accessed: 2025-08-11)</ref> <code>cyber-launcher</code> came with the dock at the bottom, which had a button that opens the launcher, and a status line bar with embedded global context menus at the top. Many parts of the interface were also partially transparent. Window controls were at the top right corner and resembles [[Microsoft Windows]], while titles were centred. == See Also == * [https://iso.atl.dev/c/cyberos CyberOS in ATL ISO Archives]{{Dead Link|2026-05-26|Cannot connect to host iso.atl.dev:443 ssl:default [Domain name not found]}} == References == 1dc473276638ce5be34768e690d42e872f342820 0 1067 5446 4350 2026-05-26T15:10:30Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/distributed-denial-of-service-attack|title=Distributed denial-of-service attack (DDoS)|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>A Distributed Denial-of-Service (DDoS) attack is a cyberattack in which multiple compromised systems are used to overwhelm a target system, service, or network with excessive traffic or requests, rendering it unavailable to legitimate users. Unlike a single-source denial-of-service attack, DDoS attacks are distributed across many devices, often forming a botnet, which makes detection, mitigation, and attribution significantly more difficult. DDoS attacks primarily target the availability component of information security and can affect websites, online services, networks, and critical infrastructure. ---- == Purpose == <ref>{{Cite|url=https://www.cisa.gov/understanding-denial-service-attacks{{Dead Link|2026-05-26|404}}|title=Understanding Denial-of-Service Attacks|author=Cybersecurity and Infrastructure Security Agency (CISA|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>The purpose of a DDoS attack is to disrupt normal operations by exhausting system resources such as bandwidth, processing power, or memory. Motivations behind DDoS attacks vary and may include financial extortion, political or ideological protest, competitive sabotage, retaliation, or strategic disruption. From a defensive and research perspective, understanding DDoS attacks is essential for designing resilient systems, improving network capacity planning, and implementing effective mitigation strategies to maintain service continuity. ---- == History == <ref>{{Cite|url=https://www.us-cert.gov/ncas/tips/ST04-015{{Dead Link|2026-05-26|404}}|title=Smurf Attack|author=US-CERT|year=2004|accessdate=Retrieved on December 19, 2025}}</ref>DDoS attacks evolved alongside the growth of networked systems and the public internet. * '''1970s–1980s''': Early denial-of-service concepts appeared in experimental network environments, primarily through resource exhaustion. * '''1996''': One of the first documented denial-of-service attacks targeted a major internet service provider, temporarily disrupting connectivity in parts of the internet. * '''1999''': The first large-scale DDoS tools emerged, enabling coordinated attacks from multiple compromised systems. * '''2000''': High-profile DDoS attacks temporarily disabled major websites, bringing global attention to the threat. * '''2010s''': Botnets leveraging Internet of Things (IoT) devices significantly increased the scale and power of DDoS attacks. * '''2020s–present''': DDoS attacks have become more frequent, automated, and capable of reaching unprecedented traffic volumes, targeting both commercial services and critical infrastructure. ---- == Types == <ref>{{Cite|url=https://www.cloudflare.com/learning/ddos/ddos-attack-types/{{Dead Link|2026-05-26|403}}|title=DDoS Attack Types|author=Cloudflare|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>DDoS attacks are commonly categorized based on the layer or resource they target: * '''Volumetric attacks''' aim to overwhelm network bandwidth using massive amounts of traffic. * '''Protocol attacks''' exploit weaknesses in network protocols to exhaust server or network device resources. * '''Application-layer attacks''' target specific applications or services, mimicking legitimate user behavior to evade detection. * '''Reflection and amplification attacks''' abuse third-party servers to multiply attack traffic toward a victim. These categories often overlap, and modern DDoS attacks frequently combine multiple techniques to maximize impact and bypass defensive measures. a26f28a27fb50b79a40e0b0db945e72daecf04a3 0 853 5447 5247 2026-05-26T15:22:17Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Software licenses]] {{Work_In_Progress}} The '''GNU General Public License''' (short '''GNU GPL''' or '''GPL''') is a collection of copyleft licenses published by the Free Software Foundation (FSF) and written by Richard Stallman<ref>https://archive.ph/20120907170559/http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html</ref>. This License is also part of the [[GNU]] project. === Copyleft === A copyleft license requires that any modifications or extensions to a program licensed under a copyleft license must also be licensed under the same (or a compatible) license. === "or-later" clause === All GNU GPL licenses may contain an optional clause, an “or-later” clause (sometimes referred to as a “lifeboat clause”). This clause allows all later versions to be used. Programs without this clause are referred to as “only.” For example * GNU GPLv2-or-later can also be licensed under GNU GPLv3-or-later without any problem * GNU GPLv2-only can only be licensed under the GNU GPLv2 The same applies to the GNU AGPL and LGPL licenses. The FSF recommends using the “or-later” clause, as it is compatible with future versions of the GNU GPL, since GNU GPLv2 and v3 are not compatible and therefore a program licensed only under GNU GPLv2 cannot be mixed with a GNU GPLv3 program. == Licenses == There are three versions of the GNU GPL, with version 3 being the most recent version for all of them. # GNU General Public License (GPL) – The standard strong copyleft license used for most programs. # GNU Lesser General Public License (LGPL) – A weak copyleft license mainly used for libraries. # GNU Affero General Public License (AGPL) – Similar to the GPL, but also covers use over a network. === GNU General Public License (GPL) === This license is used for regular programs such as the Linux kernel, which uses GNU GPLv2 only. The latest version is the GNU General Public License Version 3 (GNU GPLv3), which was released in June 2007<ref>[https://www.gnu.org/licenses/gpl-3.0.en.html#license-text The GNU General Public License v3.0], Free Software Foundation, 2007-08-14 (Accessed: 2025-08-14)</ref> and can be found [https://www.gnu.org/licenses/gpl-3.0.en.html#license-text here]. If part of a program (e.g., a library) uses this license, the entire program must be licensed under the GNU GPL. If this is not desired, the GNU LGPL or another license should be used. === GNU Lesser General Public License (LGPL) === The GNU LGPL (formerly known as the Library General Public License) was created at the same time as the GNU GPLv2 and was also published in June 2007, but the first version was called GNU LGPLv2 to match the GNU GPLv2. This license was created because the GNU GPL was too restrictive, especially for libraries. If a program uses a library licensed under the GNU LGPL, only the modification of that library must be published. This allows a library to be used in [[proprietary software]]. The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/lgpl-3.0.html here]. === GNU Affero General Public License (AGPL) === The GNU AGPL was created to close a loophole when modified software licensed under the GNU GPL was run on a server the source code don't need to be published because of that the AGPL was created to fix this loophole The latest version is version 3, which was published in June 2007 and can be found [https://www.gnu.org/licenses/agpl-3.0.html#license-text here] <references /> b524027dadbba982bb7f2601796f566a9d770772 0 679 5448 5392 2026-05-26T15:23:51Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.54.0 (2026-04-20) [https://git-scm.com/] | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com | license = [[GPL-2.0-only]] | sourcecode = https://git.kernel.org/pub/scm/git/git.git }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed ''version control system'' ([[VCS]]) designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.]{{Dead Link|2026-05-26|timeout (10)}}, Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?]{{Dead Link|2026-05-26|timeout (10)}}, Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark]{{Dead Link|2026-05-26|timeout (10)}}, Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12]{{Dead Link|2026-05-26|timeout (10)}}, Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.]{{Dead Link|2026-05-26|timeout (10)}}, Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git's early design emphasized a distributed workflow similar to BitKeeper's but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like [[GitHub]], which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. == References == 9c81ea96e98154f1050d9cba0ad009a2fed81426 0 349 5449 5222 2026-05-26T15:28:34Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Terminology]] In Unix-like Operating systems, including '''[[Linux]]''', an '''Init''' system is typically used to properly start up and manage services during boot and run time, making it necessary for OSes to properly run. '''Init''' systems, also referred to as "Initialization Systems," are a key component in the booting phase of an OS as their main task is to '''initialize''' other required processes and services to grant a functional and optimal OS. After booting up, Init systems begin to work in the background as a '''[[daemon]]''' process, their main tasks shifts from initializing components to becoming a '''direct or indirect ancestor'''<ref>Parent Process - https://en.wikipedia.org/wiki/Parent_process</ref> of any other processes that may spawn in under the current working environment; adding on, these systems typically adopt all '''orphaned processes''' and can terminate any and all '''zombie processes'''. Seeing that their role in an operating system is to maintain functionality throughout the system, in a Unix-like Operating system, a kernel is required to have a functional and usable Init system, a kernel panic will occur if—for whatever reason—a kernel is unable to find, start, or maintain the OS's Init. There are 2 different types of Inits,which, depending on the functionality, determines if it should be consider a '''Traditional Init System (TIS)''' or a '''Modern Init System (MIS)'''. Although the end goal of both types remains consistent between the two, TIS and MIS approach each task differently and support different use cases for different hardware, with both still being used till this day. === Traditional Init Systems === Before the emergence of modern alternatives, traditional Init systems ruled in terms of any sort of initializing service and/or process, but that doesn't mean they were relatively up to today's standards. These systems relied on much slower and resource consuming processes that would be proven inefficient when release of more modernized Init systems, categorized as MIS; moreover, these systems specifically used more rigid methods to initialize services and other process in addition to their ancestry job. ===== Key Characteristics ===== # '''Sequential Startup'''<ref>Why wait for sequential processing when parallel is faster? || Cindy Ng - https://www.starburst.io/blog/parallel-vs-sequential-processing/</ref>: When computer machines were much simpler, this was no problem; computers were designed for simpler operations and tasks. This was proved inefficient to computers as they began to modernize throughout the years. This type of startup began processes and services one after another, in a linear fashion. It should be taken into consideration that this isn't a disadvantage for computers today. Network configurations require a Sequential Startup to ensure all components are working; starting a service that depended on an important service before it starts the important one may cause bottlenecks and issues. But the moral of the story is that these types of start ups take crucial resources and take an excessive amount of time to boot up, their inefficient use of resources inevitably were the reason many operating systems rely on a more modernized alternative. # '''Shell Scripts'''<ref>Compiled versus Interpreted languages || IBM - https://www.ibm.com/docs/en/zos-basic-skills?topic=zos-compiled-versus-interpreted-languages</ref>: As aforementioned, the use of Shell Scripts did, in fact, have a good use as it was considered a great way to perform tasks; unfortunately, this doesn't outweigh the cons of using such a vulnerable script language. Rather than being compiled, Shell is parsed, interpreted, then executed, making inefficient use of already sparse system resources. There are many more complex issues such as, but not limited to error handling<ref>What is Error Handling? || Margaret Rouse https://www.techopedia.com/definition/16626/error-handling{{Dead Link|2026-05-26|404}}</ref>, difficult dependency management, and so forth. These types on scripts lack parallelism, discouraging running 2 scripts at once, slowing down boot processes and overall services. {| class="wikitable mw-collapsible" |+Table of TIS and older. !Init Name !Production date !Last Stable Release !Discontinued !Architecture (Supported/Developed For) !(Original) Developers(s) !Devices Supported |- |SYSTEM III UNIX |June, 1980 |~1983 |Y |PDP-11, VAX |AT&T USG |Intel-8086-Based PCs, Zilog-8000-Based PCs. |- |Research Unix |November 3rd 1971 |October, 1989 |Y |PDP-7 & 11, VAX, Intel x86, Motorola 68000, SPARC |Bell Labs CRSC |DEC PDP-7, PDP-11, VAX, Interdata 7/32 & 8/32 Computers. |- |SYSTEM V UNIX |1983 |1989 |Y |DEC PDP-11, VAX, Intel x86. |AT&T Corporation |DEC VAX, DEC PDP-11, AT&T 3B2, SPARC Devices. |} === Modern Init Systems === As computer hardware evolved, the need for better software came along, and traditional Init systems weren't cutting the job for most people standards. Rather than continuing to use outdated and old Inits, developers at ''Canonical''<ref>Canonical || Canonical Ltd - https://canonical.com/</ref> began developing a new type of Init system, nicknamed ''Upstart''<ref>Upstart || Scott James Remnant - https://launchpad.net/upstart</ref>, where most, if not all problems of TIS were fixed. Instead of implementing resource inefficient task handling such as the aforementioned Sequential Startup, developers began to use more efficient method to get the same results of a TIS, but much faster, reliable, and safer. ==== Key Characteristics ==== # '''Parallel Process Startup'''<ref>The Shepherd || GNU Project Documentation - https://savannah.gnu.org/projects/shepherd/</ref>''':''' Moving from traditional Init systems, MIS were known for their speed when compared to TIS. This came from the optimization of the Init boot process. Rather than using a Linear fashioned startup process, MIS encouraged parallelism by allowing multiple services to begin at once or when needed or when triggered by an event happening. This type of start up is better for the commercial/consumer use, unlike network configurations, some services don't need to be started before others, overall preserving system resources. # '''Event-based Triggers:''' Being able to trigger certain processes or services on certain events used less resources overall and allowed for system to be looking for triggers rather than looping a predefined list of instructions. Additionally, this speeds up the system even more, enhancing system efficiency, reliability, and security. These types of triggers based off events can be triggered through simple things such as clicks to user logins, network configuration, system shutdowns/reboots, etc. {| class="wikitable" |+Table of MIS !Init Name !Production date !Last Stable Release !Architecture (Supported/Developed for) !(Original) Developers(s) !Operating Systems (Made for/Supported) |- |systemd |March 30th, 2010 |October 8th, 2024 |AMD64, ARM64, PPC64IE, MIPS, S390X, ETC. |Lennart Poettering |[[Arch Linux|Arch]] and Arch-Based, [[Ubuntu]] and Ubuntu Based, [[Debian]] and Debian Based. FreeBSD, OpenBSD, etc. |- |OpenRC |April 5th, 2007 |September 18th, 2024 |↓ |Roy Marples |↓ |- |runit |February 10, 2004 |September 29, 2024 |↓ |Gerrit Pape |↓ |- |This is a WIP Table. | | | | |↓ |} Concluding this topic, the emergence of MIS fixed all previous issues with TIS and produced a system that is much more efficient and reliable when compared to TIS. == References == <references /> 51de0fa5b647d184d74cab768c3e3572a7701900 0 1206 5450 5112 2026-05-26T15:30:05Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki '''KDE Neon''' is a [[Linux Distributions|linux distribution]] based on [[Ubuntu|Ubuntu LTS]] developed by the [[KDE]] team, wich provides users with the latest features of the [[Plasma|KDE Plasma]] desktop environment<ref>{{Cite|url=https://neon.kde.org/faq#what-is-neon|title=KDE Neon's FAQ, What is KDE Neon question.|accessdate=2026/05/24}}</ref>. It is essentially the testing ground where new KDE Plasma updates are tested and used before being introduced to other distros using KDE Plasma (Much like how [[Fedora]] is [[Red Hat Enterprise Linux|RHEL]]'s testing ground). However, apart from the KDE Plasma desktop, the distro itself follows the stable release schedule of [[Ubuntu|Ubuntu LTS]], making it a half stable half rolling distro<ref>{{Cite|url=https://neon.kde.org/faq#is-it-rolling|title=Official statement in the KDE Neon FAQ on this.|accessdate=2026/05/26}}</ref>. because it is developed by the KDE developers, it can be seen as a "pure" KDE Plasma experience. {{DistributionInfobox|title=KDE Neon|image=[[File:KDE-Neon-logo.png]]|caption=The KDE Neon logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]], PackageKit|defaultdesktops=KDE Plasma|usagetype=Desktop|architectures=x86_64|website=[https://neon.kde.org/index&#124; KDE Neon]{{Dead Link|2026-05-26|404}}|Written in=C, C++, QT 6}} == History == KDE neon first started taking shape in late 2015 as a way to provide a rolling release of fresh KDE software on top of [[Ubuntu]]'s stable OS base. The first daily installation images began being built in January 2016. The first general release of KDE Neon was on 8 June 2016, it was based on an [[Ubuntu]] 16.04 base, using [[Plasma|KDE Plasma]] 5.6. The Latest version of KDE Neon, 6.6, was released on 16 February 2026. [[File:KDE-Neon-6.6-big.png|thumb|A fresh installation of KDE Neon 6.6.]] == Features == KDE Neon == Installation == KDE Neon uses the [[Calamares]] installer. Specifications for installation are: {| class="wikitable" |+ ! !Minimum !Recommended ! |- |Proccesor |1 GHz X86-64 CPU |2 GHz Dual-Core X86-64 CPU Or higher | |- |RAM |2GB |4GB and higher | |- |Storage |20 GB |40 GB and higher | |} Note that these minimum specs will just get you to run it at the bare minimum == References == 150ffe522675ec15a7f96310acaa8173e9e55884 0 1075 5451 5256 2026-05-26T15:30:43Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{SoftwareInfobox | image=[[File:LXDE desktop full.png|thumb]] | caption = The default LXDE desktop | title=LXDE | releasestatus=Maintained | lastrelease=0.10.1, 25 February 2021 | firstrelease=2006; 20 years ago | languages=[[C]] | developers=PCMan (formerly), The LXDE Team (currently) | website=https://www.lxde.org/{{Dead Link|2026-05-26|Cannot connect to host www.lxde.org:443 ssl:default [Domain name not found]}} }} '''LXDE,''' which is an abbreviation of '''Lightweight X11 Desktop Environment''' is a free to use desktop environment aiming to be as low on resource usage as possible. LXDE is aimed at Unix and other POSIX-compliant platforms such as BSD and Linux, and is made using GTK2 and the C programming language. It uses a rolling-release model for its individual components (or groups of components that depend on each other). == History == The project was started in 2006 by Hong Jen Yee (online known as PCMan) when he released PCManFM, which is the first module of LXDE Currently the original LXDE only receives maintenance updates, because its creator was dissatisfied with GTK3 and decided to port the entire software suite to Qt (announced in 2013) and later that year the LXDE and LXQt projects got merged Since the beginning of 2020 a GTK3 port is developed by the Arch Linux community, and several important components of LXDE have already been ported == Software Components== {| class="wikitable" ! Components ! Descriptions |- | PCMan File Manager | File manager and Desktop metaphor provider |- | LXInput | Mouse and keyboard configuration tool |- | LXLauncher | Application Launcher |- | LXPanel | Desktop panel |- | LXSession | X session manager |- | LXAppearance | GTK theme switcher |- | GPicView | Image viewer |- | LXMusic | Audio player and fronted for XMMS2 | |- | LXTerminal | Terminal emulator |- | LXTask | Task manager |- | LXRandR | A GUI for X Resize and Rotate (xrandr) | |- | LXDM | X display manager |- | [[Openbox]] | Window manager used by LXDE |- | [[ObConf]] | A GUI tool for managing Openbox's configuration |- |} 6240c6eef200191858576780f644cc609edd1653 0 884 5452 5257 2026-05-26T15:30:59Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{Work In Progress}} [[Category:Desktop Environments]] {{SoftwareInfobox | title = LXQt | image = [[File:Helix lxqt.svg|frameless]] | caption = LXQt Logo | releasestatus = Maintained | lastrelease=2.3.0, Nov 5, 2025 | firstrelease=0.7.0, May 7, 2014 | languages = [[C++]], [[C]] | developers = The LXQt Team | website = [https://lxqt-project.org/ lxqt-project.org] }} LXQt (Lightweight QT Desktop Environment) is a lightweight desktop environment formed from the merger of [[LXDE]] & [[Razor-qt]]. It is widely considered the successor to LXDE, with both being made by the same creator, Hong Jen Yee. LXQt is recommended for people who want a minimal system or have hardware constraints. Unlike other desktop environments, LXQt can use any modern [[X11]] window manager, but [[Openbox]] is used by default in most distributions due to its lightweight nature. == History == After the developer of LXDE, PCMan (Hong Jen Yee), experimented with QT by porting his file manager, [[PCManFM]] to it in early 2013<ref>[https://web.archive.org/web/20221128180217/https://blog.lxde.org/2013/02/19/pcmanfm-file-manager-is-ported-to-qt/ PCManFM file manager is ported to Qt? – LXDE Blog], PCMan, 2013 (Accessed: 2025-10-26)</ref>, a port of some LXDE components to LXQt was done. This was in the wake of community dissatisfaction about GTK's increased resource hogging. While some would protest against the port to QT, given QT's association with [[Plasma]], LXDE-Qt would eventually be created from the port of LXDE to QT. In mid 2013, it was decided that LXDE and Razor-Qt would be merged<ref>[https://web.archive.org/web/20241201170854/https://blog.lxde.org/2013/07/22/the-future-of-razor-and-lxde-qt/ “The future of Razor and LXDE-Qt” – LXDE Blog], PCMan, 2013 (Accessed: 2025-10-26)</ref> through picking preferred features from both and merging them into one Desktop Environment. == Installation == The primary method of installing LXQt is through distributions that either offer it as a default desktop or as an option in their installer. Below is a short non comprehensive list of distributions that offer LXQt. * [[Lubuntu]]: Ubuntu with preinstalled LXQt<ref>[https://lubuntu.me/ Lubuntu – The official Lubuntu home], Lubuntu, 2025 (Accessed: 2025-10-26)</ref> * [[Fedora]] LXQt spin<ref>[https://fedoraproject.org/spins/lxqt Fedora LXQt Spin | The Fedora Project], Fedora, 2025 (Accessed: 2025-10-26)</ref> * [[CachyOS]]: available in installer<ref>[https://wiki.cachyos.org/installation/desktop_environments/ Desktop Environments | CachyOS], CachyOS, 2025 (Accessed: 2025-10-26)</ref> * [[SparkyLinux]]<ref>[https://wiki.sparkylinux.org/doku.php/about about Sparky Wiki]{{Dead Link|2026-05-26|403}}, Sparky Linux, 2025 (Accessed: 2025-10-26)</ref> * [[Debian]]: available in installer<ref>[https://wiki.debian.org/LXQt LXQt - Debian Wiki], Debian Wiki, 2025 (Accessed: 2025-10-26)</ref> Advanced users who installed a base image that did not install a desktop environment, as is the norm with distributions such as [[Alpine Linux]], [[Arch Linux]], or [[Void Linux]], will want to install LXQt from their package manager. This can be done through either the metapackage or group provided by your distribution, or by handpicking the components you want to install. The table below shows a noncomprehensive list of distributions, their metapackages for LXQt and what each installs. {| class="wikitable" |+LXQt metapackages/groups !Distribution !Metapackage !Component Packages |- |Debian<ref>[https://packages.debian.org/stable/lxqt-core Debian -- Details of package lxqt-core in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |lxqt-core |Depends on: desktop-file-utils, lxqt-config, lxqt-gobalkeys, lxqt-notificationd, lxqt-panel, lxqt-policykit, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-systemtheme, lxqt-themes (or lxqt-theme), pcmanfm-qt, qterminal Recommends: featherpad, lximage-qt, lxqt-about, lxqt-archiver, lxqt-branding-debian, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n Suggests: feathernotes, firefox-esr, lxqt, lxqt-openssh-askpass, preload |- |Debian <ref>[https://packages.debian.org/trixie/lxqt Debian -- Details of package lxqt in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: featherpad, lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-branding-debian, lxqt-core, lxqt-openssh-askpass, lxqt-powermanagement, lxqt-sudo, pavucontrol-qt, qlipper, qps, qt6-translations-l10n, qterminal, xfwm4 Recommends: feathernotes, firefox-esr, gucharmap, hexchat, meteo-qt, nm-tray, qmmp, qpdfview, screengrab, smplayer, thunderbird, xscreensaver Suggests: calibre, juffed, nomacs, obconf-qt, preload, qt6-style-kvantum, qtpass, shutter, strawberry, vokoscreen |- |Debian<ref>[https://packages.debian.org/stable/task-lxqt-desktop Debian -- Details of package task-lxqt-desktop in trixie], Debian, 2025 (Accessed: 2025-10-26)</ref> |task-lxqt-desktop |Depends on: lxqt, sddm, sddm-theme-debian-elarun, task-desktop, tasksel Recommends: hunspell-en-us, hyphen-en-us, libreoffice-calc, libreoffice-gtk3, libreoffice-help-en-us, libreoffice-impress, libreoffice-qt5, libreoffice-writer, mythes-en-us, orca, synaptic, system-config-printer, xsane |- |Fedora |lxqt |Depends on: breeze-cursor-theme, breeze-gtk, breeze-icon-theme, dnfdragora-updater, falkon, firewall-config, initial-setup-gui, lxqt-about, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-themes, lxqt-themes-fedora, lxqt-wayland-session-default-compositor-miriway, network-manager-applet, nm-connection-editor, notification-daemon, obconf, openbox, pcmanfm-qt, perl-File-MimeInfo, qterminal, sddm, sddm-themes, sddm-wayland-miriway upower, xdg-user-dirs |- |Arch Linux<ref>[https://archlinux.org/groups/x86_64/lxqt/ Arch Linux - lxqt (x86_64) - Group Details], Arch Linux, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: lximage-qt, lxqt-about, lxqt-admin, lxqt-archiver, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themer, obconf-qt, openbox, pavucontrol-qt, pcmanfm-qt, qps, qterminal, screengrab, xdg-desktop-portal-lxqt |- |Void Linux<ref>[https://github.com/void-linux/void-packages/blob/master/srcpkgs/lxqt/template void-packages/srcpkgs/lxqt/template at master · void-linux/void-packages · GitHub], Github, 2025 (Accessed: 2025-10-26)</ref> |lxqt |Depends on: lxqt-about, lxqt-admin, lxqt-config, lxqt-globalkeys, lxqt-notificationd, lxqt-openssh-askpass, lxqt-panel, lxqt-policykit, lxqt-powermanagement, lxqt-qtplugin, lxqt-runner, lxqt-session, lxqt-sudo, lxqt-themes, obconf-qt, pcmanfm-qt, lximage-qt, lxqt-archiver, qterminal, openbox, breeze-icons, xdg-desktop-portal-lxqt, xdg-utils, elogind, upower |} You can alternatively handpick the components you want. lxqt-session is an absolute necessity, as well as a window manager ([[openbox]], [[KWin]], and [[xfwm4]] are the main, recommended ones<ref>[https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers ConfigWindowManagers · lxqt/lxqt Wiki · GitHub], LXQt wiki, 2025 (Accessed: 2025-10-26)</ref>). It is also good to install lxqt-config, lxqt-notificationd and lxqt-panel if you want the absolute minimal selection of utilities. After installation, it is also to also install a display manager, preferably [[SDDM]] (which is officially recommended by LXQt<ref>[https://github.com/lxqt/lxqt/wiki/Launching-LXQt-sessions Launching LXQt sessions · lxqt/lxqt Wiki · GitHub], LXQt wiki, 2025 (Accessed:2025-10-26)</ref>), to be able to start LXQt smoothly. You can alternatively start lxqt by adding <syntaxhighlight lang="text">exec startlxqt</syntaxhighlight> to your .xinitrc and running <syntaxhighlight lang=bash>startx</syntaxhighlight> == References == 4b7e06e195d8864309ac730dcb1adbffee516a93 0 218 5453 3746 2026-05-26T15:32:03Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Guides]] [[Linux]] due to its generally lower system requirements than [[Windows]]<ref>[https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3 Revive Old Hardware with Linux], Aidan Palmer, 2023-03-05 (Accessed: 2025-08-09)</ref> or [[macOS]] and a general absence of vendor-imposed hardware restrictions is frequently chosen for reviving and reusing older devices. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (i.e. keyrings, polkit, GTK, QT, etc.) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>[https://www.linuxmint.com/faq.php Frequently Asked Questions - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>[https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <span style="color:#fc493b">https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <sup>🍣404]{{Dead Link|2026-05-26|404}}</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Frequently_asked_questions Frequently asked questions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://wiki.archlinux.org/title/Arch_compared_to_other_distributions Arch compared to other distributions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time-consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>[https://fedoraproject.org/wiki/FAQ FAQ], Fedora Project Wiki, 2025-07-24 (Accessed: 2025-08-09)</ref><ref>[https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs Hardware Overview], Fedora Docs, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">[https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html System requirements for Puppy Linux]{{Dead Link|2026-05-26|404}}, THE.Hosting, 2023-04-23 (Accessed: 2025-08-09)</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' == References == <references /> d28e3a2defdb669e973298a149fedba4fbf068f0 0 718 5454 4094 2026-05-26T15:33:21Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{DISPLAYTITLE:macOS}} [[File:Apple-Logo-Transparent.png|thumb|right]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical [[Operating System|operating systems]] developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a [[UNIX]] (Darwin/[[BSD]]) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/{{Dead Link|2026-05-26|timeout (10)}}|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> 99360069ac66063faaa7749b52c8edd7d9485046 0 1070 5455 4354 2026-05-26T15:33:37Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/malware|title=Malware|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>'''Malware''' (malicious software) refers to any software intentionally designed to disrupt, damage, infiltrate, or gain unauthorized access to computer systems, networks, or data. Malware operates by exploiting software vulnerabilities, misconfigurations, or user behavior to execute unwanted actions, often without the knowledge or consent of the system owner. It represents one of the core threats in modern computing and [[cybersecurity]]. ---- == Purpose == <ref>{{Cite|url=https://www.cisa.gov/malware{{Dead Link|2026-05-26|404}}|title=What Is Malware?|author=Cybersecurity and Infrastructure Security Agency (CISA)|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of malware is to achieve unauthorized objectives on a target system. These objectives commonly include stealing sensitive information, gaining persistent access, disrupting normal operations, surveilling users, extorting victims, or using compromised systems for further attacks. Malware may be financially motivated, politically driven, state-sponsored, or intended for sabotage, espionage, or experimentation. ---- == History == <ref>{{Cite|url=https://www.sciencedirect.com/science/article/pii/S016740481400082X{{Dead Link|2026-05-26|403}}|title=The History of Computer Viruses and Malware|author=Peter Szor|year=2014|accessdate=Retrieved on December 19, 2025}}</ref>The history of malware closely follows the evolution of computing and network connectivity. * '''1971''' – The ''Creeper'' program appears on ARPANET, often regarded as the first self-replicating malware. * '''1980s''' – Early computer viruses spread via floppy disks as personal computing becomes widespread. * '''1986''' – The ''Brain'' virus targets MS-DOS systems, becoming the first widely recognized PC virus. * '''1990s''' – Networked malware, email worms, and macro viruses emerge with the growth of the internet. * '''2000s''' – Malware becomes commercially driven, with botnets, spyware, and mass-distributed worms. * '''2010s''' – Advanced malware, ransomware, and state-sponsored tools increase in sophistication. * '''2020s–present''' – Malware evolves into modular, stealthy, and automated threats targeting cloud, mobile, IoT, and critical infrastructure environments. ---- == Types == <ref>{{Cite|url=https://www.kaspersky.com/resource-center/threats/malware-types|title=Types of Malware|author=Kaspersky Lab|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>Malware exists in many forms, each defined by its behavior and objectives. Common categories include '''viruses''', which attach to legitimate files; '''worms''', which self-propagate across networks; '''trojans''', which disguise malicious code as legitimate software; '''spyware''', which secretly collects information; '''[[ransomware]]''', which encrypts data for extortion; '''rootkits''', which conceal malicious activity; and '''botnet malware''', which allows attackers to remotely control large numbers of compromised systems. ---- == Significance == <ref>{{Cite|url=https://www.pearson.com/en-us/subject-catalog/p/computer-security-principles-and-practice/P200000003295|title=Computer Security: Principles and Practice|author=William Stallings|year=2018|accessdate=Retrieved on December 19, 2025}}</ref>Malware has had a profound impact on the development of [[cybersecurity]], influencing operating system design, network defenses, antivirus technologies, and international cyber policy. While malware is most commonly associated with criminal activity, its existence has driven advances in threat detection, incident response, secure software development, and digital risk management. Understanding malware is essential for protecting modern digital infrastructure and ensuring the reliability of computer systems worldwide. d9122b06cc2e4112b92580fce72f5a8083f92793 0 626 5456 4360 2026-05-26T15:33:57Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{DistributionInfobox | title = Manjaro | image = [[File:Manjaro logo new.svg|Thumb]] | caption = The Manjaro logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]], [[Pamac]] | defaultdesktops = [[KDE Plasma]], [[Xfce]], [[GNOME]] | usagetype = Desktop | architectures = x86_64, Arm64 | website = [https://manjaro.org manjaro.org] }} Manjaro is an [[Arch Linux|Arch]]-based [[rolling release]] distribution with a focus on taking the "raw power and flexibility of Arch Linux and making it more accessible for a greater audience."<ref>[https://manjaro.org/ Manjaro – The Linux for People and Organizations], Manjaro, 2025-08-09 (Accessed: 2025-08-09)</ref> It has its own repositories and tries to be stable, with software more extensively tested than traditional rolling release.{{Citation needed}} It has official images for [[Plasma|KDE Plasma]], [[XFCE|Xfce]], and [[GNOME]], while community-supported images are available for [[Cinnamon]], [[i3]], and [[Sway|SwayWM]].<ref name=":0">[https://distrowatch.com/table.php?distribution=manjaro DistroWatch.com: Manjaro Linux], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> === Overview === * Developed/owned by: Manjaro GmbH & Co * OS Family: [[Linux]] * Source Model: [[Open-source]] * Update Method: "Stable" Rolling Release * Package Manager: [[Pacman]], [[Pamac]], and [[Flatpak]].<ref name=":0" /><ref>[https://wiki.manjaro.org/index.php/Pamac Pamac - Manjaro]{{Dead Link|2026-05-26|404}}, Manjaro, 2023-03-09 (Accessed: 2025-08-09)</ref> * Architecture: [[x86_64]], [[aarch64]] === Key Milestones in Manjaro's History: === * '''2011''': Initial release of Manjaro Linux. * '''2012''': [[GNOME|GNOME Shell]] support was dropped with version 0.8.3. * '''2013''': Manjaro entered its beta phase, introducing key features like a GUI installer, hardware detection tools, and a settings manager. * '''2015''': The versioning scheme changed from numerical designations to a '''year-month format''', starting with Manjaro 15.09 (formerly 0.9.0). * '''2017''': Official GNOME desktop support was reinstated, and support for the '''[[i686]] architecture''' was discontinued due to declining popularity. * '''2019''': Manjaro GmbH & Co. KG was founded, formalising the project's development. * '''2020''': Manjaro introduced '''ZFS filesystem support''' and improved package management.<ref>[https://en.wikipedia.org/wiki/Manjaro Manjaro], Wikipedia contributors, 2025-07-01 (Accessed: 2025-08-09)</ref><ref>[https://www.ubuntumint.com/manjaro-linux-history/ The History of Manjaro Linux Distribution], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> === Installation === Manjaro uses the [[Calamares]] installer, similar to [[EndeavourOS]] or [[ArcoLinux]].<ref>[https://www.geeksforgeeks.org/how-to-install-manjaro-linux/ How to Install Manjaro Linux?], GeeksforGeeks, 2023-12-22 (Accessed: 2025-08-09)</ref> === Arch Compatibility === Manjaro is based on Arch Linux, but it is '''not''' a 1:1 compatible downstream (like EndeavourOS). While it draws from Arch's base and philosophy, it introduces additional layers for stability, user experience, and system safety. === Key Differences in Compatibility: === * '''Separate Repositories:''' Manjaro uses its own repositories that are based on Arch's, but updates are held back and tested before release to ensure system stability. * '''AUR Access:''' The Arch User Repository (AUR) is accessible, but not enabled by default. Users can enable AUR access through the GUI or install helpers like [[yay]].<ref>[https://www.ubuntumint.com/enable-arch-user-repository-manjaro-linux/ How to Enable Arch User Repository (AUR) in Manjaro Linux], Ravi Saive, 2023-07-24 (Accessed: 2025-08-09)</ref> * '''Rolling Release with Buffer:''' Manjaro follows a rolling-release model but with a delayed update cycle compared to Arch. This provides a balance between freshness and reliability, while giving time for extra testing. === Documentation Use === While much of Arch Linux's documentation is applicable to Manjaro, users should be cautious. Manjaro's custom tools (like <code>mhwd</code>, <code>pamac</code>, and its kernel manager) and repository structure may differ significantly. It's important to check Manjaro specific resources or forums before applying Arch instructions verbatim, although most things should just work. === Repositories === Manjaro does '''not''' use Arch's mirrors directly. Instead, it follows Arch's upstream by cherry-picking some packages and manually vetting them through '''Unstable''', '''Testing''', and '''Stable''' branches.<ref>[https://itsfoss.com/manjaro-vs-arch-linux/ Manjaro vs Arch: What's the Difference? Which one to Use?], Dimitrios, Abhishek Prakash, 2023-09-13 (Accessed: 2025-08-09)</ref> This tiered approach by Manjaro is believed to help prevent system breakage and support a smoother user experience. Due to this process, package updates on Manjaro may arrive long after they are updated on Arch. However, this approach is heavily discouraged and unsupported by Arch as it is considered a partial upgrade.<ref>[https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported System maintenance], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> Manjaro packages may also differ slightly in configuration or carry additional patches or branding. == References == 52296b128032c2842ee91d6bce38ec3e2cc3ac5f 0 1229 5457 5197 2026-05-26T15:34:12Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Software]] for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation. = Raster image editors = Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. == Photo editors == {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} == Drawing == {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} == Sprites/spritesheet editors == {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} = Vector image editors = Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website]{{Dead Link|2026-05-26|403}}, [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} = Movie makers/video editors = {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery. {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} 14c4c32edae235d937ea07089717686d8c4a2025 0 534 5458 4934 2026-05-26T15:35:05Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines].}} {{SoftwareInfobox | image = [[File:Nirilogo.svg|300px|example_niri_rice]] | caption = Niri's logo | title = niri | releasestatus = Maintained | firstrelease = v0.1.0-alpha.1 | lastrelease = v26.04 | languages = [[Rust]] | developers = Ivan Molodetskikh A.K.A. YaLTeR | website = [https://github.com/YaLTeR/niri Github Repository] }} [[File:Niri Rice.png|thumb|A desktop running [[Niri]].]] Niri is a scrollable-tiling [[Wayland]] compositor which was heavily inspired by [[PaperWM]]<ref name=":0">The official niri GitHub repository https://github.com/YaLTeR/niri</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features<ref name=":1">[https://github.com/YaLTeR/niri/wiki/Important-Software Important Software · YaLTeR/niri Wiki · GitHub], YaLTeR, 2025-08-09 (Accessed: 2025-08-09)</ref> == Notable features of Niri include: * Dynamic workspaces similar to GNOME * [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/444776459-379a5d1f-acdb-4c11-b36c-e85fd91f0995.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260523%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260523T125301Z&X-Amz-Expires=300&X-Amz-Signature=75c2d0798e6c61573bf1455e04df47a6a17adb4c6ae4a63f4db920758db9db0a&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4 Overview]{{Dead Link|2026-05-26|403}} for managing workspaces * Built-in screenshot utility * [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from Block out] sensitive windows from screencasting * Smooth [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/311428885-946a910e-9bec-4cd1-a923-4a9421707515.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260523%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260523T130056Z&X-Amz-Expires=300&X-Amz-Signature=eb6cc56f82db2e1479e0bde7ef6526e215362c74b4667165e4d5c835f3693bfa&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4 touchpad]{{Dead Link|2026-05-26|403}} and [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331768055-8464e65d-4bf2-44fa-8c8e-5883355bd000.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260523%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260523T130215Z&X-Amz-Expires=300&X-Amz-Signature=cb539530de50996bea283c287d1efb5e79c46cb75f2b4aaec4c5fae8e9f3e758&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4 mouse]{{Dead Link|2026-05-26|403}} gestures * Tiling and floating window modes * Customizable [https://niri-wm.github.io/niri/Configuration%3A-Layout.html#gradients borders], [https://github-production-user-asset-6210df.s3.amazonaws.com/1794388/331791576-27a238d6-0a22-4692-b794-30dc7a626fad.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20260523%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260523T130941Z&X-Amz-Expires=300&X-Amz-Signature=33aead18339cb88343044619cad6feaaad576457bf740e360daf42fb4235e16d&X-Amz-SignedHeaders=host&response-content-type=video%2Fmp4 animations]{{Dead Link|2026-05-26|403}}, and overall look and feel * Live-reloading after changing configurations * Compatibility with [[X11]] applications via [[XWayland]] == References == <references /> 044476389f10f7f55f9803cc41c0844b91ee3cc3 0 1065 5459 4353 2026-05-26T15:35:58Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/penetration-testing{{Dead Link|2026-05-26|404}}|title=Penetration Testing|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>Penetration testing is a formal and authorized [[cybersecurity]] assessment methodology used to evaluate the security of computer systems, networks, applications, or infrastructures by simulating realistic attack scenarios. It involves systematically identifying, validating, and exploiting security vulnerabilities under controlled conditions to assess how an attacker could compromise confidentiality, integrity, or availability. Unlike automated vulnerability scanning, penetration testing includes human analysis, decision-making, and contextual understanding of system behavior, making it a deeper and more accurate measure of real-world security risk. ---- == Purpose == <ref>{{Cite|url=https://www.ibm.com/topics/penetration-testing|title=Penetration Testing: Assessing Security Vulnerabilities|author=IBM|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of penetration testing is to proactively identify and confirm security weaknesses before they are exploited by malicious actors. It enables organizations to understand their actual attack surface, evaluate the effectiveness of existing security controls, and prioritize remediation based on real exploitability rather than theoretical risk. Penetration testing also supports regulatory compliance, improves incident preparedness, and provides measurable insight into organizational security posture by demonstrating the potential business impact of successful attacks. ---- == History == <ref>{{Cite|url=https://www.sans.org/white-papers/1289/|title=A Short History of Penetration Testing|author=SANS Institute|year=2005|accessdate=Retrieved on December 19, 2025}}</ref>Penetration testing developed alongside the expansion of networked computing and the public internet. * '''1960s–1970s''': Early security assessments were conducted in military and academic environments, primarily focused on access control and system isolation. * '''1980s''': Government-funded research programs in the United States formally introduced controlled attack simulations to evaluate computer security, particularly within defense systems. * '''1990s''': With the rapid growth of the internet and commercial networks, penetration testing began to emerge as a recognized practice for evaluating enterprise security. * '''Late 1990s''': The term ''penetration testing'' became widely adopted, and structured methodologies began to form. * '''2000s''': Penetration testing became a professional service, integrated into corporate security programs and compliance frameworks. * '''2010s–present''': Penetration testing evolved into a standardized cybersecurity discipline, incorporating cloud systems, mobile platforms, and complex infrastructures, and is now a core component of modern risk management strategies. ---- == Types == <ref>{{Cite|url=https://owasp.org/www-project-web-security-testing-guide/|title=Penetration Testing Methodologies and Types|author=OWASP Foundation|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>Penetration testing is commonly categorized based on the level of system knowledge provided to the tester: * '''Black-box testing''' involves no prior knowledge of the target system, simulating an external attacker with minimal information and emphasizing reconnaissance and discovery. * '''Gray-box testing''' provides partial knowledge or limited credentials, representing an insider threat or a compromised user account. * '''White-box testing''' grants full access to system architecture, source code, and documentation, allowing for comprehensive and in-depth security analysis. Penetration testing may also be classified by target scope, such as network penetration testing, web application testing, mobile application testing, cloud security testing, wireless testing, or internal infrastructure testing. 87860f29c21c29690a04ced0d5f53cbd742cdac4 0 176 5460 4371 2026-05-26T15:36:20Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.5.4, December 9, 2025 [https://kde.org/announcements/plasma/6/6.5.4/] |firstrelease=1.0, July 12, 1998 [https://kde.org/announcements/1-2-3/1.0-beta1/] | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> Desktop Environment for [[Unix-Like|Unix-like]] [[Operating System|Operating Systems]], ranging from [[Linux]] to various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === KDE Plasma alone merely provides a Desktop Environment - this is no understatement of its base suite, which includes fully featured Settings application, [https://apps.kde.org/dolphin/ Dolphin], a robust file manager, [https://apps.kde.org/discover/ Discover], Plasma's app store, and a few other base tools. However, the KDE Project itself offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2026-05-26|403}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2026-05-26|403}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode" - essentially, from edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects allow for additional responsiveness and appearance tweaks for the KDE Plasma desktop. Plasma includes a sizeable number of default and optional effects, in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' on KDE. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] allows for corner rounding on KDE for both '''[[X11]]''' and '''[[Wayland]]''' on active and/'''or''' inactive windows. == References == <references /> 3299b051c8a4fcae9f917abb317365820bcc1fe9 0 855 5461 3809 2026-05-26T15:36:43Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{Needs Citations}} [[Category:Software]] [[File:Pulse Visualizer.png|thumb|alt=Pulse Visualizer in CRT mode|Pulse Visualizer in CRT mode|alt=Screenshot of Pulse Visualizer displaying CRT-style visual effects.]] '''Pulse Visualizer''' is a cross-platform real-time audio visualizer inspired by [https://minimeters.app/ MiniMeters] and written in [[C++]] and [[GLSL]]. It captures system audio via [[PipeWire]], [[PulseAudio]] or WASAPI, processes the signal through digital signal processing (DSP) stages using fftw<ref>https://fftw.org/<nowiki/>(Accessed: 2025-8-11)</ref>, libebur128<ref>https://github.com/jiixyj/libebur128<nowiki/>(Accessed: 2025-8-11)</ref> and other custom DSP methods, and renders visuals with hardware acceleration through [[OpenGL]] in an [[SDL3]] window.<ref>https://github.com/Beacroxx/pulse-visualizer Pulse Visualizer GitHub, 2025 (Accessed: 2025-08-11)</ref> == Features == Pulse Visualizer supports multiple real-time visualization modes, including stereometer, oscilloscope, spectrum analyzer, spectrogram, peak/LUFS meter, and VU meter. Users can customize the panels with features such as CRT screen emulation using GPU compute shaders, adjustable visual effects (blur, glow, chromatic aberration, vignette), and draggable, resizable panels. The application offers hot reloading of both configuration and theme files without restarting, and is compatible with Linux and BSD systems using PipeWire or PulseAudio for audio input.<ref>https://github.com/Beacroxx/pulse-visualizer/blob/main/CONFIGURATION.md{{Dead Link|2026-05-26|404}}<nowiki/>(Accessed: 2025-8-11)</ref> == References == <references /> __INDEX__ cd6cada7abccf3912794c6884b2957bcee1fbf76 0 1072 5462 4358 2026-05-26T15:40:27Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki A '''script''' is a set of written instructions designed to be interpreted and executed by a computer or [[:Category:Software|software]] environment rather than compiled into machine code beforehand.<ref>{{Cite|url=https://www.britannica.com/technology/script-computer-programming{{Dead Link|2026-05-26|404}}|title=Script|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref> Scripts are typically written in high-level programming or scripting languages and are used to automate tasks, control [[:Category:Software|software]] behavior, and perform repetitive or system-level operations efficiently. ---- == Purpose == The primary purpose of a script is '''automation and control'''.<ref>{{Cite|url=https://www.ibm.com/topics/scripting|title=What Is a Script?|author=IBM|year=2023|accessdate=Retrieved on December 19, 2025}}</ref> Scripts reduce manual effort by executing predefined actions such as file management, system configuration, data processing, application interaction, and administrative tasks. In many environments, scripts enable rapid development, customization, and orchestration of systems without requiring full-scale [[:Category:Software|software]] engineering. ---- == History == The concept of scripting emerged alongside early computing and operating systems.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Scripting_language|title=Scripting Language|author=Wikipedia Contributors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref> * '''1960s–1970s''' – Job control languages and command scripts appear in mainframe systems. * '''1980s''' – Shell scripting becomes common in [[UNIX|Unix]]-based operating systems. * '''1990s''' – Languages such as Perl, JavaScript, and VBScript popularize scripting for web and system tasks. * '''2000s''' – Python, PHP, and PowerShell expand scripting into enterprise, web, and automation domains. * '''2010s–present''' – Scripts are central to DevOps, cloud infrastructure, [[cybersecurity]], and automation workflows. ---- == Types == Scripts can be categorized by their execution environment and purpose.<ref>{{Cite|url=https://www.redhat.com/en/topics/automation/what-is-a-script{{Dead Link|2026-05-26|404}}|title=What Is a Script? Shell, Automation, and Application Scripts|author=Red Hat|year=2023|accessdate=Retrieved on December 19, 2025}}</ref> Common types include '''shell scripts''' for operating system automation, '''web scripts''' for client-side or server-side logic, '''administrative scripts''' for system management, '''automation scripts''' for repetitive workflows, and '''security scripts''' used in testing, monitoring, and analysis. Some scripts are standalone, while others operate within larger software frameworks. ---- == Significance == Scripts are foundational to modern computing due to their flexibility, efficiency, and ease of use.<ref>{{Cite|url=https://www.pearson.com/en-us/subject-catalog/p/computer-security-principles-and-practice/P200000003295|title=Computer Security: Principles and Practice|author=William Stallings|year=2018|accessdate=Retrieved on December 19, 2025}}</ref> They play a critical role in system administration, software development, cybersecurity, and infrastructure management. By enabling rapid task execution and system customization, scripting significantly improves productivity and operational consistency across digital environments. 9855ea52996017fbee4206a2166a63122c8cf47b 0 1095 5463 4455 2026-05-26T15:41:17Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Eliza.png]] | caption = Tempest For eliza in use | title = Tempest for eliza | releasestatus = discontinued | lastrelease = 1.0.5, 2002 | firstrelease = 1.0.0, unknown | languages = Unknown | developers = Erikyyy | website = [https://erikyyy.de/tempest/]{{Dead Link|2026-05-26|Cannot connect to host erikyyy.de:443 ssl:default [[SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1081)]}} }} '''Tempest for Eliza''' is an experimental open-source program written by Erik Thiele that turns a computer monitor into a rudimentary AM radio transmitter by exploiting unintended electromagnetic emissions from display hardware. It is part of a class of software and research projects inspired by “TEMPEST” side-channel techniques. == overview == Tempest for Eliza generates carefully designed pixel patterns on a computer screen. These patterns cause the monitor’s electronic components to emit electromagnetic signals at specific frequencies. When these emissions are picked up by an AM radio tuned to the right frequency, they can be interpreted as sound often musical tones == background == The project is based on research into compromising electromagnetic emanations, a field sometimes referred to as TEMPEST. The term originally comes from a U.S. government codename related to standards for limiting electronic eavesdropping risks. A key academic foundation is the concept of van Eck phreaking, introduced by Wim van Eck in 1985, which showed that video displays can be reconstructed from their electromagnetic radiation. Tempest for Eliza builds on this idea in a creative direction: instead of reconstructing images from emissions Tempest for Eliza interfers the TEMPEST signals, also deliberately encodes audio signals into them. 590010d83e381c330244d2c0a609dd76be88586f 0 1071 5464 4356 2026-05-26T15:42:06Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki <ref>{{Cite|url=https://www.britannica.com/technology/Trojan-horse-computing{{Dead Link|2026-05-26|404}}|title=Trojan horse|author=Encyclopædia Britannica Editors|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>A '''Trojan''', or '''Trojan horse''', is a type of [[Malware|malicious]] software that disguises itself as a legitimate or desirable program in order to deceive users into executing it. Unlike viruses or worms, a Trojan does not self-replicate; instead, it relies on social engineering, user interaction, or deceptive distribution methods to gain access to a system. Once activated, a Trojan can perform hidden malicious actions while appearing to function as normal software. ---- == Purpose == <ref>{{Cite|url=https://www.cisa.gov/trojan-horse{{Dead Link|2026-05-26|404}}|title=Trojan Horse Malware|author=Cybersecurity and Infrastructure Security Agency (CISA)|year=2024|accessdate=Retrieved on December 19, 2025}}</ref>The primary purpose of a Trojan is to provide attackers with unauthorized access or control over a system while avoiding detection. Trojans are commonly used to steal sensitive information, install additional malware, create backdoors, spy on user activity, or enable remote command execution. Because Trojans exploit user trust rather than technical vulnerabilities alone, they are particularly effective against non-technical users and remain a persistent threat. ---- == History == <ref>{{Cite|url=https://www.sciencedirect.com/science/article/pii/S016740481400082X{{Dead Link|2026-05-26|403}}|title=A Short History of Malware|author=Peter Szor|year=2014|accessdate=Retrieved on December 19, 2025}}</ref>The concept of the Trojan horse in computing draws its name from the ancient Greek tale of deception. * '''1970s–1980s''' – Early theoretical discussions of deceptive programs appear in academic research. * '''1989''' – The ''AIDS Trojan'' (PC Cyborg) is distributed via floppy disks, becoming one of the first well-known Trojans. * '''1990s''' – Trojans spread through pirated software, email attachments, and early internet downloads. * '''2000s''' – Remote access Trojans (RATs) become widespread, enabling full system control. * '''2010s''' – Banking Trojans and spyware target financial credentials and personal data. * '''2020s–present''' – Trojans are commonly used as initial access tools in ransomware, espionage, and supply-chain attacks. ---- == Types == <ref>{{Cite|url=https://www.kaspersky.com/resource-center/threats/trojans|title=What Is a Trojan Horse?|author=Kaspersky Lab|year=2023|accessdate=Retrieved on December 19, 2025}}</ref>Trojans are classified based on their functionality and intended outcome. Common types include '''remote access Trojans (RATs)''', which grant attackers full control; '''banking Trojans''', designed to steal financial information; '''dropper Trojans''', which install additional malware; '''spy Trojans''', which monitor user activity; and '''backdoor Trojans''', which create persistent unauthorized access points. Many modern Trojans are modular and capable of performing multiple roles. ---- == Significance == <ref>{{Cite|url=https://www.pearson.com/en-us/subject-catalog/p/computer-security-principles-and-practice/P200000003295|title=Computer Security: Principles and Practice|author=William Stallings|year=2018|accessdate=Retrieved on December 19, 2025}}</ref>Trojans are among the most prevalent forms of malware due to their reliance on deception rather than technical exploits. They play a central role in large-scale cybercrime, data breaches, and advanced persistent threats. Understanding Trojans is essential to [[cybersecurity]] education, as they highlight the importance of user awareness, software authenticity, and layered security controls in defending modern computing environments. 1d34588a68d4f16eb1df3fa2910a23b8f951fcd8 0 667 5465 5066 2026-05-26T15:42:34Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{Cleanup|Incomplete page, horribly out of date}} {{SoftwareInfobox|image=[[File:UNIX logo.svg|UNIX|200px]]|caption=|title=UNIX|releasestatus=Maintained|lastrelease=UNIX V7|languages=[[C]], Assembly|developers=Ken Thompson, Dennis Ritchie, Brian Kernighan, Douglas McIlroy, and Joe Ossanna at Bell Labs|website=[https://www.opengroup.org/membership/forums/platform/unix opengroup.org]}} '''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. The owner of the UNIX® trademark has been The Open Group since 1994.<ref>[https://unix.org/what_is_unix.html What is UNIX ®?]{{Dead Link|2026-05-26|404}} unix.org</ref> Examples of modern UNIX operating systems include Apple's MacOS and IBM AIX. Being genetic UNIX® is not required for UNIX® certification. Formerly, Inspur K-UX was certified UNIX®, specifically versions 2.0 and 3.0. Inspur K-UX's UNIX® certification expired in February 2019 and has yet to be renewed.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Inspur_K-UX|title=Inspur K-UX|author=Huihermit|year=21 January 2025|accessdate=2 August 2025}}</ref> == References == 96cf2140bf89e8523c2c330a0e481df226c9713e 0 317 5466 4245 2026-05-26T15:43:18Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, rolling-release Linux distribution built from scratch. It was created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm Void Linux: Distribution mit XBPS-Paketverwaltung]{{Dead Link|2026-05-26|Cannot connect to host www.pro-linux.de:443 ssl:default [Connection reset by peer]}}, Pro-Linux, 2015-06-12 (Accessed: 2025-08-09)</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and [[musl]] libc support. == Architecture Support == Void Linux provides installation images for: * x86_64 (amd64) - Both glibc and musl variants * i686 (32-bit x86) - glibc only * aarch64 (64-bit ARM) * armv6l and armv7l (32-bit ARM) == System Management == === Init System === Void uses [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for runit. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === Void Linux offers two C library implementations, which provide many of the functions used by programs written in the [[C]] programming language: [[glibc]] and [[musl libc]]. ====glibc==== glibc is the original C library implementation used by Void Linux. While it provides compatibility with most proprietary software, it produces larger executables and uses more memory than musl libc. ====musl==== musl libc was added to the Void Linux repositories in 2013.<ref>[https://github.com/void-linux/void-packages/commit/8420d238cb1338fef2a7392bca6dc65c6fa80001 New package: musl-0.9.9.], Juan RP, 2013 (Accessed: October 18, 2025)</ref> It has a smaller footprint and full static linking support, though not all programs are compatible with it. == Installation == Void Linux is installed using a terminal-based installer called <code>void-installer</code> which is included in the live ISO images provided by the project. It guides users in configuring the network, setting the system's locale and time zone, adding user accounts, partitioning the disks, and installing the system itself.<ref>[https://www.debugpoint.com/install-void-linux/ How to Install Void Linux [Step by Step&#93;], Arindam, 2024 (Accessed: October 18, 2025)</ref> Detailed instructions for installation are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == Void uses a script called <code>xbps-src</code> for building packages, using template files that specify the package metadata, dependencies, and build instructions. It builds packages in a container with only the declared dependencies installed.<ref>[https://www.ordinatechnic.com/distribution-specific-guides/Void/void-linux-creating-binary-packages-using-xbps-src Void Linux: Creating Binary Packages Using xbps-src], Ordinatechnic, 2018 (Accessed: October 18, 2025)</ref> It also supports cross-compilation. == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://voidlinux.org/news/ Official blog] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == 460d07060499bd324ded85585663c9e37e989393 0 769 5467 5236 2026-05-26T15:43:32Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | [[MangoWM]]<ref>[https://mangowc.vercel.app MangoWM Homepage]{{Dead Link|2026-05-26|404}} (Accessed: 2026-02-27)</ref> || None || [[C]] || Extremely customizable & performant Wayland compositor built on top of [[dwl]]. |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| [[C]] || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | [[Sway]] || None || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || None (Tiling) || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[river]]<ref>[https://github.com/riverwm/river <nowiki>GitHub - riverwm/river: [mirror] A dynamic tiling Wayland compositor</nowiki>], riverwm, 2020-08-09 (Accessed: 2025-08-09)</ref> || None (Tiling) || [[zig]]|| Lightweight and minimal tiling compositor focused on simplicity. |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || None (3D effects) || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || None (Kiosk) || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- | [[Niri]] || None (Scrolling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp cosmic-comp github repo], pop-os team et al., 2025 (Accessed: 2026-05-25)</ref> |[[COSMIC]] |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || None (Tiling) || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 288f16bcfe8c415455b575f99cc5d64445254836 0 586 5468 4405 2026-05-26T15:44:10Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox | title = Xenia (Linux Fox) | image = [[File:Xenia the Linux Fox.gif]] | caption = The original design of Linux Fox, created by Al Mackey in 1996 }} Xenia was a candidate logo and [[:Category:Mascots|mascot]] for the [[Linux]] project. She was a competitor to [[Tux]], who became the official Linux mascot (largely due to a personal endorsement from Linus Torvalds)<ref>[https://web.archive.org/web/20241014040700/https://shellsamurai.com/why-the-linux-mascot-is-a-penguin-the-story-behind-tux-%F0%9F%90%A7/ Why the Linux mascot is a penguin: The story behind Tux], Stetson Blake, April 2023 (Accessed April 5 2025).</ref> == History == Xenia was originally designed by Alan Mackey in 1996, under the name 'Linux Fox'.<ref>[https://archive.is/5UrGL But penguins aren't even furry!], Ed Mackey, August 1998 (Accessed April 2025).</ref> Linux Fox came in third in a competition to vote for the official Linux logo - the second place entrant was Tux, and the first was a "Linux Powered" logotype by Matt Ericson.<ref>[https://archive.is/wYsFh Penguins and Other Things], Greg Roelofs, February 2007 (Accessed April 2025).</ref> Mackey's Linux Fox was rediscovered by an audiovisual artist known on Twitter as @cathodegaytube in 2019. Cathodegaytube's partner Amy Wright coined the name Xenia for Linux Fox, and Cathodegaytube developed a refreshed design inspired by Mackey's original work. == Cultural Impact == When cathodegaytube contacted Mackey for comment on her updated design for Xenia in 2020, she was surprised to learn that he had originally intended his Linux Fox to be a boy. This series of coincidences spurred many artists, including cathodegaytube herself, to create artwork of Xenia with transgender pride flags and other pride iconography.<ref>[https://web.archive.org/web/20250405051855/https://xenia-linux-site.glitch.me/ Xenia: the Linux mascot], Efi, 2020 (Accessed April 2025).</ref> This fresh take on the design was embraced by the considerable subcommunity of LGBTQ+ and gender nonconforming Linux enthusiasts, which had been developing and thriving over the 24 years since Linux Fox's conception. [[File:Xeniafox cathodegaytube.png|thumb|The refreshed design of Xenia, created by cathodegaytube in 2019]] Xenia has thus become widely popular within large subsections of the Linux community and returned to cultural prominence. She is now often seen as an unofficial second mascot of Linux alongside Tux, especially among enthusiasts. == Related Work == Xenia Linux - a "meta-distribution" made up of a set of scripts to turn any Linux distribution into an immutable base and provide helpful tools - is named after Xenia. Its primary flavor is based on [[Gentoo]].<ref>[https://web.archive.org/web/20250303234858/https://xenialinux.com/ Xenia Linux], Xenia Linux Team, 2023 (Accesed April 2025).</ref> == References == <references /> 6ea26a95e9709ac171dfc6ee0e0a8e15aedbbbd8 0 1157 5469 4816 2026-05-26T15:44:33Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki [[Category:Linux Distributions]] [[Category:Slackware-based Distributions]] [[Category:Free Software]] '''Zenwalk''' is a lightweight Linux distribution based on [[Slackware]] focused on simplicity, speed, and efficient desktop computing. Zenwalk is designed to provide a fast and streamlined Linux experience while maintaining compatibility with the Slackware ecosystem. The distribution emphasizes: * simplicity * minimalism * performance * ease of use Zenwalk is commonly used on: * older hardware * lightweight desktop systems * low-resource environments * general-purpose Linux desktops == Overview == Zenwalk was originally created as a lightweight alternative to traditional Slackware installations. The project focuses on providing: * optimized software selection * lightweight desktop environments * simplified administration * efficient resource usage Unlike standard Slackware installations, Zenwalk attempts to include a more complete desktop experience by default. == History == Zenwalk was originally known as '''Minislack''' before being renamed. The distribution was developed to create a balance between: * Slackware simplicity * desktop usability * lightweight performance Over time, Zenwalk developed its own repositories, package tools, and desktop customization. == Slackware Base == Zenwalk is based on [[Slackware]], one of the oldest Linux distributions still actively maintained. Because of this, Zenwalk inherits many Slackware characteristics including: * simplicity * traditional UNIX-like design * manual configuration philosophy * stability Zenwalk remains compatible with much of the Slackware software ecosystem. == Desktop Environment == Zenwalk has historically focused on lightweight desktop environments. The distribution commonly uses: * XFCE The lightweight desktop design helps reduce: * memory usage * CPU overhead * system resource consumption == Package Management == Zenwalk uses package management systems derived from Slackware. Software management tools include: * netpkg * pkgtools Packages are generally distributed in Slackware-compatible formats. == Performance == Zenwalk emphasizes speed and low resource usage. Optimization goals include: * fast boot times * responsive desktop performance * lightweight software selection This makes the distribution suitable for older or lower-end hardware. == Software Selection == Zenwalk attempts to provide one primary application per major task category. Examples include: * lightweight desktop applications * development tools * multimedia software * networking utilities This approach helps reduce software redundancy and system bloat. == Development == Zenwalk supports software development with tools commonly available through Slackware repositories and compatible packages. Users may develop software using: * GCC * Python * Perl * shell scripting == Security == Like many Linux distributions, Zenwalk benefits from: * Linux permission systems * UNIX-like user separation * open-source transparency Security updates are distributed through project repositories. == Community == Zenwalk has historically maintained a smaller but dedicated Linux community. Community support commonly includes: * forums * documentation * package repositories * user guides == Use Cases == Zenwalk is commonly used for: * lightweight desktop computing * older hardware revitalization * general Linux usage * Slackware-based environments * educational systems == Limitations == Common criticisms of Zenwalk include: * smaller community size * limited package repositories * slower release activity * less beginner-friendly configuration compared to some modern distributions == Comparison with Other Distributions == Zenwalk is often compared with: * [[Slackware]] * [[Arch Linux]] * [[Xubuntu]] * [[Puppy Linux]] Compared to standard Slackware, Zenwalk focuses more heavily on desktop usability and lightweight optimization. == See Also == * [[Slackware]] * [[Linux]] * [[XFCE]] * [[Linux Distributions]] == References == * http://www.zenwalk.org/ * https://distrowatch.com/table.php?distribution=zenwalk == External Links == * http://www.zenwalk.org/modules/tinycontent/{{Dead Link|2026-05-26|404}} f275311da0531d41130092739385d8e5b10878a9 3000 914 5470 5437 2026-05-26T15:52:05Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs Citations}} {{cleanup}} {{Stub}} = Checking the Boot Mode = There are two boot modes in computer systems: * [[UEFI]] * Legacy [[BIOS]] You can easily check the boot mode using the System Information program in [[Windows]]: # In the search box, type the <code>System Information</code> and open the program. [[File:CheckUEFI-1.png||none|700px]] # From the list on the left side, look for <code>BIOS Mode</code> #* If the value is <code>UEFI</code> - Your system is using UEFI mode. #* If the value is <code>Legacy</code> - Your system is using Legacy BIOS mode. [[File:CheckUEFI-2.png|none|700px]] It is '''not recommended''' to install Arch alongside Windows in '''Legacy BIOS''' mode, as many motherboards do not handle the GRUB bootloader well in this mode, and you may face system boot issues later. = Checking the Disk Partitioning Scheme = There are two main types of disk partitioning schemes: * [[GPT]] (GUID Partition Table) * [[MBR]] (Master Boot Record) '''You must check the disk type before starting the installation to ensure using the correct method.''' == How to check the disk partitioning scheme: == # Open the <code>Disk Management</code> tool in Windows.<br>Right-click the Windows logo on the taskbar and select <code>Disk Management</code>.[[File:OpenDiskManagement.png|none|700px]] # Select the disk you want to install Arch on. Right-click it, choose (Properties), then select the (Volumes) tab. [[File:CheckGPT-1.png|none|700px]] # In the (Partition Style) field, you will see the disk type: #* If it says '''GUID Partition Table''' - This is a GPT disk. #* If it says '''Master Boot Record''' - This is an MBR disk. The MBR partition scheme is outdated and '''not recommended''' for installing Arch alongside Windows. If your disk uses MBR, you must either convert it to GPT (which will '''erase all data''') or use a separate physical disk. == The rest of the Guide is work in progress. == 02e020e7ccdc7016f3f044ebf96c0933fafc0f72 3000 1031 5471 4226 2026-05-26T15:52:15Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Guide Warning}}This is part of a series of articles on creating bootable media, you can see all the different options on the [[Guides:Creating Bootable Media|Creating Bootable Media]] article. You can also learn more about the uses of bootable media and the concepts behind it on the same page. Fedora Mediawriter can be used to flash '''any''' operating system to a USB drive however it has built in support to download Fedora ISO's automatically to flash to the drive. You will require an internet connection, a device with a USB port and a USB drive which is 16GB or larger. Most distributions will not require more than 8GB but some larger distributions may need a larger drive. ==Installing Fedora Mediawriter== ===Linux=== If you are on a Fedora Based Distribution you can install it by running:<syntaxhighlight lang="shell"> sudo dnf install mediawriter </syntaxhighlight> If you are on any other Linux distribution you can install it via Flatpak from [https://flathub.org/en/apps/org.fedoraproject.MediaWriter Flathub]:<syntaxhighlight lang="shell"> flatpak install flathub org.fedoraproject.MediaWriter </syntaxhighlight> You can also install it using the Nix package manager using the following command:<syntaxhighlight lang="shell"> nix-env -iA nixpkgs.mediawriter </syntaxhighlight> ===Windows or MacOS=== On every ISO download page you can find the download link for Fedora Media Writer, such as on the Fedora Workstation download page [https://fedoraproject.org/workstation/download here]. Once you have downloaded the installer you can open it and go through the guided process to install it to your system. == Using Fedora Mediawriter to create a bootable USB == [[File:Fedora Mediawriter Start Screen.png|alt=The start screen of the "Fedora Mediawriter" Application. With two options, "Download automatically", "Select .iso file" or "Restore USB" and an "About" and "Next" buttons.|thumb|403x403px|The home screen of Fedora Mediawriter]] Once you have installed Fedora Mediawriter you can use it to either flash a Fedora edition or any other ISO file to your USB. You will need to download an ISO if your choosing and plug in your USB drive to your device. <blockquote>'''Remember''' '''that this USB drive will be erased and all data on it will be lost once you.'''</blockquote> If you wish to flash a Fedora edition you can follow through the "Download automatically" and it will let you select an edition of Fedora to flash to your USB drive. If you wish to install an alternate operating system you select the "Select .iso file" option and it will let you select an ISO file and an attached USB drive. Please ensure you select the correct drive as you will not be able to recover any data on this drive once you continue. After choosing the ISO file and USB drive and start the write process, you will need to wait up to 15 minutes for the drive to be flashed. Once it has flashed you will be able to unplug it or reboot to install your chosen operating system or try out a live environment for an operating system. Each distribution has a different installation process, so you will need to consult distribution specific documentation or check the wiki for a guide on your chosen distribution. b08569727016e6f75ed5a9030f13a88148520a3d 3000 1214 5472 5061 2026-05-26T15:52:26Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Guides]] [[Category:Software]] {{Work In Progress}} {{stub|date=may 2026}} {{Guide_Warning}} The following section provides commands and instructions on how to use [[cryptsetup]] to create a LUKS USB. One of the most common use for cryptsetup is to create an encrypted, As USB devices are small and could be easily lost or stolen, it is recommended to encrypt USB devices if you only plan on accessing them on Linux, though there may be tools out there for accessing LUKS devices on non-[[Linux kernel|Linux]] systems. Note that the following instructions involve partitioning the USB, meaning, '''all data on it will be lost'''. Use this when creating a USB. Firstly, read the above warning, secondly, find the device you want to encrypt by running <code>lsblk</code>, the output should look something like this,<syntaxhighlight lang="output"> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 7.2G 0 disk ├─sda1 8:1 1 7.2G 0 part zram0 251:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 953.9G 0 disk ├─nvme0n1p1 259:1 0 600M 0 part /boot/efi ├─nvme0n1p2 259:2 0 2G 0 part /boot └─nvme0n1p3 259:3 0 951.3G 0 part /home / </syntaxhighlight>The exact names are probably different on your machine, but the most important part is the <code>/dev/sdX</code> device, for USBs it is most likely going to be an <code>sdX</code> device. Then the next step is to overwrite the USB. There are a few ways to do this. Everywhere you see <code>/dev/sdX</code> replace <code>/dev/sdX</code> with the name of your USB device as given by lsblk. First, if you want to be sure the data is gone and prevent an attacker from potentially guessing how much data is on the device, you can do: <code>sudo dd if=/dev/urandom of/dev/sdX bs=4M status=progress</code> after that ''optional'' step is done, you can move onto creating the partition, note that this step and the previous optional step, '''will erase all the data on the drive'''! There are several ways to do this, you can use a graphical tool like [[GParted]], But for fdisk, the instructions are simple, <code>fdisk /dev/sdX</code> Then run the <code>g</code> command to create a new GPT Partition, after that, you should run the <code>n</code> command to create a new partition, leave all the settings (like partition number and sectors) blank to use defaults, after you are done, run <code>w</code> to commit your changes to the USB and '''erase all data'''. After you are done that, its time to create the encrypted partition, run: <code>sudo cryptsetup luksFormat --verify-passphrase /dev/sdX1</code> Note that <code>/dev/sdX1</code> ends in a 1 to signify the first partition. Next, to open the device, run <code>sudo cryptsetup open /dev/sd</code><code>X1 usb</code> After that, the device with the unencrypted data will be in <code>/dev/mapper/usb</code>, now you can actually make the file system. If you want ext4, the traditional Linux file system, run: <code>sudo mkfs.ext4 /dev/mapper/usb</code> Otherwise, if you want btrfs, a more modern option, run: <code>sudo mkfs.btrfs /dev/mapper/usb</code> Now there is one more thing to do, mount the files. <code>sudo mount /dev/mapper/usb /mnt</code> Then you are done. The files are accessible in /mnt, though you might want to chown them so you have permissions. When it comes time to remove the USB you can simply unmount the drive by running <code>sudo umount /mnt</code> and then closing the LUKS device <code>sudo cryptsetup close usb</code> == How to open and close the USB == After your done creating it, opening it is simple, just run<syntaxhighlight lang="bash"> sudo cryptsetup open /dev/sdX1 usb sudo mount /dev/mapper/usb /mnt </syntaxhighlight>And then you can close it just as easily,<syntaxhighlight lang="bash"> sudo umount /mnt sudo cryptsetup close usb </syntaxhighlight> 8c9c89443a8eb2d148fec2769fdfe72c5755a172 3000 1263 5473 5421 2026-05-26T15:53:40Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{GuideWarning}} <blockquote> CAUTION: There is no confirmation when deleting repos in this manner, and deleting them is an irreversible process. So make sure you have entered them correctly or have them backed up elsewhere. </blockquote> First, you'll need an access token, which you can generate under User Settings -> Applications. Make sure it has at least read and write access for repository and user. == Delete select repos == You'll need to change the <code>INSTANCE_URL</code>, <code>INSTANCE_USER</code>, and <code>INSTANCE_TOKEN</code> values in this script below to those of your Codeberg, Forgejo, or Gitea instance. The values used below are just examples. <syntaxhighlight lang="bash"> #!/usr/bin/env bash set -euo pipefail # Change these INSTANCE_URL=https://codeberg.org INSTANCE_USER=hyperreal INSTANCE_TOKEN=cd188e90f2f03eed57b1971fb16329b1b919a2bb # Add the repository names to an array. E.g., if your repo is located at # https://codeberg.org/hyperreal/dotfiles, the name you would add would be # "dotfiles". repos=("repo0", "repo1", "dotfiles", "repo2") # Iterate through the array and delete each item using curl. for repo in "${repos[@]}"; do echo "Deleting repository: ${repo}" curl -s \ -u "${INSTANCE_USER}:${INSTANCE_TOKEN}" \ -X DELETE \ "${INSTANCE_URL}/api/v1/repos/${INSTANCE_USER}/${repo}" done </syntaxhighlight> == Delete all the repos == If for whatever reason you want to delete all the repos on your account, change the line with the <code>repos=("repo0", "repo1", "dotfiles", "repo2")</code> array to the following. This will query the API for the names of all your repos with curl and read them into an array: <syntaxhighlight lang="bash"> readarray -t repos < <(curl -s -u "${INSTANCE_USER}:${INSTANCE_TOKEN}" "${INSTANCE_URL}/api/v1/users/${INSTANCE_USER}/repos?limit=100" | jq -r '.[].name') </syntaxhighlight> e0bc4450b1fbdc068486d57a99a10120d71107a4 0 1266 5474 2026-05-26T17:07:22Z Atmois 13 Create homepage redirect wikitext text/x-wiki #REDIRECT [[Main Page]] {{DEFAULTSORT:Main Page}} __NOTOC__ __NOEDITSECTION__ __NOINDEX__ __NONEWSECTIONLINK__ ad531749ffa05c53b0c4fa5dbc17283d57207e23 6 1267 5475 2026-05-26T20:09:34Z Andrew8596 403 wikitext text/x-wiki Showing The Hannah Montana Linux Desktop 0d36c9fc8a16db8ea6be8786b48983a6b898ce19 0 1253 5476 5419 2026-05-26T20:32:02Z Uniolo 345 Link to XMPP wikitext text/x-wiki {{Stub}} '''Matrix''' is a open network for secure and decentralized communication, and consists of a federated network of Matrix "homeservers." Users from any homeserver can communicate with users from any other homeserver unless blocked by the homeserver owner<ref>{{Cite|url=https://matrix.org/docs/matrix-concepts/elements-of-matrix/#homeserver|title=Matrix documentation, "Elements of Matrix"|author=Matrix.org Foundation|year=2023-02-08|accessdate=2026-05-25}}</ref>. It has various clients [https://matrix.org/ecosystem/clients/ listed on its website]. Each client supports every homeserver. Notable clients include [[Element]], [[Cinny]], [[Nheko]], and [[FluffyChat]]. It is often compared to [[XMPP]]. Matrix has various features, the exact features may vary by client but usually include E2EE, VoIP (which can be thought of as "Voice Chat"), and Spaces. Several governments and militaries use Matrix for secure communications<ref>{{Cite|url=https://element.io/blog/in-an-increasingly-volatile-world-governments-turn-to-element-and-matrix/|title=In an increasingly volatile world, governments turn to Element and Matrix|author=Steve Loynes|year=December 19, 2024|accessdate=2026-05-25}}</ref>. Matrix may also be used by people needing privacy or with an interest in it, or who don't want to use services like Discord due to the risk of the centralized Discord server collapsing, banning the server, or making bad decisions effecting them. 6e59ea4ba6e5977b0601fec15a4424eb198df256 0 1268 5477 2026-05-26T20:36:41Z Uniolo 345 Create XMPP to go along with Martix. wikitext text/x-wiki '''XMPP''' is a Independent and privacy-focused, federated messaging standard<ref>{{Cite|url=https://xmpp.org/|title=XMPP Website|author=XMPP Specifications Foundation|year=May 26, 2026|accessdate=2026-05-26}}</ref>. It is often compared to [[Matrix]] and while most XMPP clients are federated, not all are. WhatsApp uses a simplified version of XMPP without federation<ref>{{Cite|url=https://getstream.io/blog/whatsapp-works/|title=How Does WhatsApp Work? Architecture Deep Dive|author=Raymond F|year=September 25, 2025|accessdate=2026-05-26}}</ref>. Notable XMPP clients include [[Dino]], and [[Gajim]]. d1ae4cceb5bdb9f4759105017c90e307d039b989 5479 5477 2026-05-26T20:40:54Z Uniolo 345 Add breif summary of what XEPs are. wikitext text/x-wiki '''XMPP''' is a Independent and privacy-focused, federated messaging standard<ref>{{Cite|url=https://xmpp.org/|title=XMPP Website|author=XMPP Specifications Foundation|year=May 26, 2026|accessdate=2026-05-26}}</ref>. Each client implements certain parts of the standards, called XEPs, making the base protocol lightweight but keeping it extensible<ref>{{Cite|url=https://xmpp.org/extensions/|title=XMPP Website, extensions.|author=XMPP Specifications Foundation|year=May 26, 2026|accessdate=2026-05-26}}</ref>. It is often compared to [[Matrix]] and while most XMPP clients are federated, not all are. WhatsApp uses a simplified version of XMPP without federation<ref>{{Cite|url=https://getstream.io/blog/whatsapp-works/|title=How Does WhatsApp Work? Architecture Deep Dive|author=Raymond F|year=September 25, 2025|accessdate=2026-05-26}}</ref>. Notable XMPP clients include [[Dino]], and [[Gajim]]. 12d54a6b67f254cde7835c78b5b3732126a9e700 5480 5479 2026-05-26T20:41:58Z Uniolo 345 Add stub (forgot to add it) wikitext text/x-wiki {{Stub}} '''XMPP''' is a Independent and privacy-focused, federated messaging standard<ref>{{Cite|url=https://xmpp.org/|title=XMPP Website|author=XMPP Specifications Foundation|year=May 26, 2026|accessdate=2026-05-26}}</ref>. Each client implements certain parts of the standards, called XEPs, making the base protocol lightweight but keeping it extensible<ref>{{Cite|url=https://xmpp.org/extensions/|title=XMPP Website, extensions.|author=XMPP Specifications Foundation|year=May 26, 2026|accessdate=2026-05-26}}</ref>. It is often compared to [[Matrix]] and while most XMPP clients are federated, not all are. WhatsApp uses a simplified version of XMPP without federation<ref>{{Cite|url=https://getstream.io/blog/whatsapp-works/|title=How Does WhatsApp Work? Architecture Deep Dive|author=Raymond F|year=September 25, 2025|accessdate=2026-05-26}}</ref>. Notable XMPP clients include [[Dino]], and [[Gajim]]. c1ec9983c43c07bb78a8386dce8ecadf3f203a7a 5501 5480 2026-05-27T05:59:13Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} '''XMPP''' is a Independent and privacy-focused, federated messaging standard<ref>{{Cite|url=https://xmpp.org/|title=XMPP Website|author=XMPP Specifications Foundation|year=May 26, 2026|accessdate=2026-05-26}}</ref>. Each client implements certain parts of the standards, called XEPs, making the base protocol lightweight but keeping it extensible<ref>{{Cite|url=https://xmpp.org/extensions/|title=XMPP Website, extensions.|author=XMPP Specifications Foundation|year=May 26, 2026|accessdate=2026-05-26}}</ref>. It is often compared to [[Matrix]] and while most XMPP clients are federated, not all are. WhatsApp uses a simplified version of XMPP without federation<ref>{{Cite|url=https://getstream.io/blog/whatsapp-works/|title=How Does WhatsApp Work? Architecture Deep Dive|author=Raymond F|year=September 25, 2025|accessdate=2026-05-26}}</ref>. Notable XMPP clients include [[Dino]], and [[Gajim]]. 6985556634a1b4384d0cd8daf0fcb8fe2f154c6e 0 396 5478 5357 2026-05-26T20:38:04Z Uniolo 345 Add XMPP wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package Managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' File managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. These are the most common file managers: {| class="wikitable" !Name !External links !Description !DE |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |[[Plasma|KDE Plasma]] |- |Thunar |[https://docs.xfce.org/xfce/thunar/start Xfce] |Thunar is [[Xfce]]'s modern file manager, desgined from the group up for speed and friendliness. |[[Xfce]] |- |} == System Resource Monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. == Hardware Maintenance == '''See the main page: [[Hardware Maintenance]]''' These are GUI and TUI programs that check the current health and utilization of hardware components such as your SSD/HDDs and battery. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp GitHub] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Cinny]] |[https://cinny.in/ Website], [https://github.com/cinnyapp/cinny GitHub] |Matrix client focused on providing a simple, elegant and secure interface. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |- |[[XMPP]] |[https://xmpp.org Website] |An extensible federated messaging protocol. |} = Media = '''See the main page: [[Media]]''' == Art, 2D, and 3D media editing == '''See the main page: [[Media Editing]]''' Includes software primarily meant for drawing, photo & image editing, vector image editing, video editing, 3d modeling, texturing, and animation, etc. == Music and Audio == '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. fabd1d917ca953c3a5e6491fd095e4e5957a354a 5504 5478 2026-05-27T08:15:43Z ZeliotL 375 Separated video, image and 3D wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package Managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' File managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. These are the most common file managers: {| class="wikitable" !Name !External links !Description !DE |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |[[Plasma|KDE Plasma]] |- |Thunar |[https://docs.xfce.org/xfce/thunar/start Xfce] |Thunar is [[Xfce]]'s modern file manager, desgined from the group up for speed and friendliness. |[[Xfce]] |- |} == System Resource Monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. == Hardware Maintenance == '''See the main page: [[Hardware Maintenance]]''' These are GUI and TUI programs that check the current health and utilization of hardware components such as your SSD/HDDs and battery. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp GitHub] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Cinny]] |[https://cinny.in/ Website], [https://github.com/cinnyapp/cinny GitHub] |Matrix client focused on providing a simple, elegant and secure interface. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |- |[[XMPP]] |[https://xmpp.org Website] |An extensible federated messaging protocol. |} = Media = '''See the main page: [[Media]]''' == Art, 2D, and 3D media editing == '''See the main page: [[Media Editing]]''' == Image == Includes software primarily meant for drawing, photo & image editing and vector image editing '''See the main page [[Image Editing]]''' == 3D == Includes software primarily for 3d modeling, texturing, and animation '''See the main page [[3D Editing]]''' == Video == '''See the main page [[Video Editing]]''' For video players, see [[Video Players]] == Music and Audio == '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. 9f8ff4697dc4253e37fd3f0b9c39a69b31abd364 5509 5504 2026-05-27T08:24:35Z ZeliotL 375 removed clumped editor page wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package Managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' File managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. These are the most common file managers: {| class="wikitable" !Name !External links !Description !DE |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |[[Plasma|KDE Plasma]] |- |Thunar |[https://docs.xfce.org/xfce/thunar/start Xfce] |Thunar is [[Xfce]]'s modern file manager, desgined from the group up for speed and friendliness. |[[Xfce]] |- |} == System Resource Monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. == Hardware Maintenance == '''See the main page: [[Hardware Maintenance]]''' These are GUI and TUI programs that check the current health and utilization of hardware components such as your SSD/HDDs and battery. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp GitHub] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Cinny]] |[https://cinny.in/ Website], [https://github.com/cinnyapp/cinny GitHub] |Matrix client focused on providing a simple, elegant and secure interface. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |- |[[XMPP]] |[https://xmpp.org Website] |An extensible federated messaging protocol. |} = Media = '''See the main page: [[Media]]''' == Image == Includes software primarily meant for drawing, photo & image editing and vector image editing '''See the main page [[Image Editing]]''' == 3D == Includes software primarily for 3d modeling, texturing, and animation '''See the main page [[3D Editing]]''' == Video == '''See the main page [[Video Editing]]''' For video players, see [[Video Players]] == Music and Audio == '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. dc9f11d5416607dfc2c0927426bb00f9222ee796 0 1201 5481 5021 2026-05-26T20:52:05Z Andrew8596 403 Add infobox :D and add bold in 2008 wikitext text/x-wiki {{DistributionInfobox |title=Hannah Montana Linux |image = [[File:Hannah Montana Linux Desktop.jpg|378x258px|thumb]] |caption=A image of the Desktop of the Distribution |releasestatus=UnMaintained |releasemodel=Stable Release |packagemanager=[[apt]], [[dpkg]] |defaultdesktops = [[KDE]] 4.2 |usagetype=Desktop |architectures = x86_64 | website = [https://archive.org/details/hannah_montana_linux_x86_basic_edition_202201 internet Archive Page]}} Hannah Montana Linux, also known as HML, is a [[Meme Linux Distributions|Meme Linux Distribution]] based on [[Kubuntu]] with a Hannah Montana-themed [[Ricing|Rice]] of [[KDE|KDE 4.2]]. It was released in '''2008''' by an anonymous developer and hasn't received updates since. 6e5dfa6c84dfc8dc575a4ecbded2c0945c41c97a 5500 5481 2026-05-27T05:59:03Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox |title=Hannah Montana Linux |image = [[File:Hannah Montana Linux Desktop.jpg|378x258px|thumb]] |caption=A image of the Desktop of the Distribution |releasestatus=UnMaintained |releasemodel=Stable Release |packagemanager=[[apt]], [[dpkg]] |defaultdesktops = [[KDE]] 4.2 |usagetype=Desktop |architectures = x86_64 | website = [https://archive.org/details/hannah_montana_linux_x86_basic_edition_202201 internet Archive Page]}} Hannah Montana Linux, also known as HML, is a [[Meme Linux Distributions|Meme Linux Distribution]] based on [[Kubuntu]] with a Hannah Montana-themed [[Ricing|Rice]] of [[KDE|KDE 4.2]]. It was released in '''2008''' by an anonymous developer and hasn't received updates since. f42f540f2a5fb5a8d5c55ca0bf932d0eaa65ab5c 2 1269 5482 2026-05-26T20:53:31Z Andrew8596 403 Created page with "hello, im the guy that helps people from support from the arch linux community discord (swiftink)" wikitext text/x-wiki hello, im the guy that helps people from support from the arch linux community discord (swiftink) a3dcd884135b3fbb84ee7001744884d831787b44 0 1222 5483 5411 2026-05-26T21:27:15Z Uniolo 345 Added fedora instructions. Changed formatting to be complaint with Guideines about providing the {{Guide Warning}} template. wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox | image = [[File:Yt-dlp logo.svg|thumb]] | caption = yt-dlp | title = yt-dlp | releasestatus = Maintained | lastrelease = 2026.03.17, 2026-03-17 | firstrelease = 2021.01.07, 2021-01-07 | languages = [[Python]] | developers = [https://github.com/orgs/yt-dlp/people yt-dlp maintainers] | website = [https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] | license = Unlicense }} '''yt-dlp''' is a [[CLI|command-line]] audio/video downloader that supports [https://github.com/yt-dlp/yt-dlp/blob/master/supportedsites.md thousands of sites] including [https://youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. = Using yt-dlp = {{Guide Warning}} == Installation == === Binaries === yt-dlp releases [https://github.com/yt-dlp/yt-dlp/releases/latest/ standalone executable binaries on GitHub]. === pip === yt-dlp is published on the Python package registry. You can install it using [https://pip.pypa.io/en/stable/ pip]:<syntaxhighlight lang="bash">pip install yt-dlp</syntaxhighlight> === Arch Linux === yt-dlp is packaged on the official [[Arch Linux]] repositories. You can install it using [[Pacman]]:<syntaxhighlight lang="bash"> sudo pacman -S yt-dlp </syntaxhighlight> === Fedora === yt-dlp is also packaged on the official [[Fedora]] repositories. You can install it with [[DNF]]:<syntaxhighlight lang="bash"> sudo dnf install yt-dlp </syntaxhighlight> == Usage tips == yt-dlp can embed thumbnails/subtitles and integrate with [https://sponsor.ajay.app/ Sponsorblock] . For convenience, you can define a <code>yt</code> [[shell]] alias to enable these features by default:<syntaxhighlight lang="bash">alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist'</syntaxhighlight>Some of the most commonly used options are <code>-o <output></code> to specify the output file, and <code>-t <type></code> to specify the output file's type. For example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up] as an MP3 file named <code>Rick Astley - Never Gonna Give You Up.mp3</code> in the current directory:<syntaxhighlight lang="bash">yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # If you have an alias set, replace "yt-dlp" with the name of your alias</syntaxhighlight>A full list of options can be found by running <code>yt-dlp --help</code>. ac9d9876c903e8d123e8746230bac23047985835 5484 5483 2026-05-26T21:28:51Z Uniolo 345 Add references section to avoid collapsing them. wikitext text/x-wiki [[Category:Software]] {{stub|date=may 2026}} {{SoftwareInfobox | image = [[File:Yt-dlp logo.svg|thumb]] | caption = yt-dlp | title = yt-dlp | releasestatus = Maintained | lastrelease = 2026.03.17, 2026-03-17 | firstrelease = 2021.01.07, 2021-01-07 | languages = [[Python]] | developers = [https://github.com/orgs/yt-dlp/people yt-dlp maintainers] | website = [https://github.com/yt-dlp/yt-dlp github.com/yt-dlp/yt-dlp] | license = Unlicense }} '''yt-dlp''' is a [[CLI|command-line]] audio/video downloader that supports [https://github.com/yt-dlp/yt-dlp/blob/master/supportedsites.md thousands of sites] including [https://youtube.com/ YouTube]. It is a fork of [https://github.com/ytdl-org/youtube-dl youtube-dl]<ref>{{Cite|url=https://github.com/yt-dlp/yt-dlp|title=yt-dlp github page|author=yt-dlp contributors|year=2026-05-22|accessdate=2026-05-24}}</ref>. = Using yt-dlp = {{Guide Warning}} == Installation == === Binaries === yt-dlp releases [https://github.com/yt-dlp/yt-dlp/releases/latest/ standalone executable binaries on GitHub]. === pip === yt-dlp is published on the Python package registry. You can install it using [https://pip.pypa.io/en/stable/ pip]:<syntaxhighlight lang="bash">pip install yt-dlp</syntaxhighlight> === Arch Linux === yt-dlp is packaged on the official [[Arch Linux]] repositories. You can install it using [[Pacman]]:<syntaxhighlight lang="bash"> sudo pacman -S yt-dlp </syntaxhighlight> === Fedora === yt-dlp is also packaged on the official [[Fedora]] repositories. You can install it with [[DNF]]:<syntaxhighlight lang="bash"> sudo dnf install yt-dlp </syntaxhighlight> == Usage tips == yt-dlp can embed thumbnails/subtitles and integrate with [https://sponsor.ajay.app/ Sponsorblock] . For convenience, you can define a <code>yt</code> [[shell]] alias to enable these features by default:<syntaxhighlight lang="bash">alias yt='yt-dlp --sponsorblock-remove sponsor,selfpromo,interaction,music_offtopic --add-chapters --embed-subs --embed-thumbnail --yes-playlist'</syntaxhighlight>Some of the most commonly used options are <code>-o <output></code> to specify the output file, and <code>-t <type></code> to specify the output file's type. For example, to download [https://www.youtube.com/watch?v=dQw4w9WgXcQ Never Gonna Give You Up] as an MP3 file named <code>Rick Astley - Never Gonna Give You Up.mp3</code> in the current directory:<syntaxhighlight lang="bash">yt-dlp -t mp3 -o "Rick Astley - Never Gonna Give You Up.mp3" https://www.youtube.com/watch?v=dQw4w9WgXcQ # If you have an alias set, replace "yt-dlp" with the name of your alias</syntaxhighlight>A full list of options can be found by running <code>yt-dlp --help</code>. == References == <references /> 67c7789dc453dc0adab659cba5b9a008904ad54b 3000 1270 5485 2026-05-27T01:30:25Z Hyperreal 388 Init Guide:Setting_up_a_Bluesky_PDS_with_Podman_on_CentOS_Stream_10 wikitext text/x-wiki {{GuideWarning}} This guide is based on the documentation[https://github.com/bluesky-social/pds][https://github.com/bluesky-social/deploy-recipes] from the official Bluesky PDS GitHub repos. <blockquote> CentOS Stream is not an officially supported distribution by the upstream PDS maintainers. </blockquote> == Minimum server requirements == {| class="wikitable" style="margin:auto" |- ! Component !! Requirement |- | OS || CentOS Stream 10 |- | RAM || 1 GB |- | CPU cores || 1 |- | Storage || 20 GB SSD |- | Architectures || amd64, arm64 |- | Number of PDS users || 1-20 |} Ensure we have a firewall installed along with fail2ban (see [[Guides:Fail2ban]]), and that proper security precautions are taken for our server, such as SSH hardening (see [[Guides:Best_SSH_Security_Practices]]). Other requirements: * Public IPv4 address * Public DNS name * Public inbound internet access permitted on port 80/tcp and 443/tcp * A reverse-proxy server, such as Caddy. This guide will use Caddy. Make sure our DNS name is resolvable to our public IPv4 address before proceeding, as it will make testing the PDS easier later on. We'll keep SELinux in enforcing mode and install a policy module to allow the PDS to work. == Preliminary actions == Install Caddy, Podman, and epel-release. <syntaxhighlight lang="bash"> sudo dnf install dnf-plugins-core sudo dnf copr enable @caddy/caddy sudo dnf install '@container-management' caddy epel-release </syntaxhighlight> === SELinux policy module === SELinux is not required, but it is recommended for RHEL-like distributions. To set SELinux in enforcing mode, run the following command with root privileges. <syntaxhighlight lang="bash"> setenforce 1 </syntaxhighlight> To make this persist across reboots, we may need to edit <code>/etc/sysconfig/selinux</code>. Change the <code>SELINUX</code> variable to the value <code>enforcing</code>. <syntaxhighlight lang="bash"> SELINUX=enforcing </syntaxhighlight> We'll also need to install an SELinux policy module so that SELinux doesn't deny the container processes used by the PDS. The following policy module will give the container runtime permissions for creating, locking, reading, writing, and setting attributes on files and directories used by containers, as well as give the containers permission to connect and write to Unix sockets. Create a file named <code>pds.te</code>. <syntaxhighlight> module pds 1.0; require { type container_runtime_t; type var_run_t; type container_t; type default_t; class file { create lock map open read setattr unlink write }; class dir { add_name remove_name write }; class unix_stream_socket connectto; class sock_file write; } # ============= container_t ============== allow container_t container_runtime_t:unix_stream_socket connectto; allow container_t default_t:dir { add_name remove_name write }; allow container_t default_t:file { create lock map open read setattr unlink write }; allow container_t var_run_t:sock_file write; </syntaxhighlight> Compile and install the module. <syntaxhighlight lang="bash"> checkmodule -M -m -o pds.mod pds.te semodule_package -o pds.pp -m pds.mod sudo semodule -i pds.pp </syntaxhighlight> If SELinux still denies some processes, we can check for them with the following command. <syntaxhighlight lang="bash"> sudo ausearch -m avc -ts recent | sudo audit2allow </syntaxhighlight> == Installing the PDS Podman quadlet == The systemd quadlet files are taken from the deploy-recipes repo[]. The only modification I have made is the <code>EnvironmentFile</code> setting. The directory under which we should place these files is <code>/etc/containers/systemd/</code> Create the file <code>/etc/containers/systemd/pds.container</code>. This file defines the main container for the PDS. <syntaxhighlight lang="ini"> [Unit] Description=Bluesky Personal Data Server service Before=caddy.service [Container] Label=app=pds Image=ghcr.io/bluesky-social/pds:0.4 AutoUpdate=registry Pod=pds.pod EnvironmentFile=/etc/pds.env [Install] WantedBy=multi-user.target default.target </syntaxhighlight> Next, create the file <code>/etc/containers/systemd/pds.pod</code>. This file defines the mappings for the PDS volume and published ports. <syntaxhighlight lang="ini"> [Pod] Volume=pds.volume:/pds PublishPort=127.0.0.1:3000:3000 # if you map 3000:3000 instead of 127.0.0.1:3000:3000 # the PDS will be accessible without the reverse proxy. # You probably don't want that! </syntaxhighlight> Finally, create the file <code>/etc/containers/systemd/pds.volume</code>. This file defines the OCI volume used to store the PDS data. <syntaxhighlight lang="ini"> [Unit] Description=Bluesky PDS Volume [Volume] Label=app=pds </syntaxhighlight> These files comprise a systemd quadlet. Quadlets enable Podman containers to run as systemd services. It's a declarative way to configure containers that fits in with the systemd ecosystem. More information on how to configure quadlets can be found at [https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html podman-systemd.unit]. It's necessary to have all of these files together in the same directory, as they depend on each other. == Setting up pds.env == Here is the default <code>pds.env</code>. We should edit it to our specific needs. <syntaxhighlight lang="bash"> PDS_HOSTNAME=pds.example.com PDS_JWT_SECRET= PDS_ADMIN_PASSWORD= PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX= PDS_DATA_DIRECTORY=/pds PDS_BLOBSTORE_DISK_LOCATION=/pds/blocks PDS_BLOB_UPLOAD_LIMIT=104857600 # if you want to user s3 or compatible, use these variables and comment out DISK_LOCATION PDS_BLOBSTORE_S3_BUCKET=your-bucket-name PDS_BLOBSTORE_S3_ENDPOINT=https://s3.example.com #PDS_BLOBSTORE_S3_FORCE_PATH_STYLE=true # depends on your s3 provider PDS_BLOBSTORE_S3_ACCESS_KEY_ID=your-access-key-id PDS_BLOBSTORE_S3_REGION=your-region PDS_BLOBSTORE_S3_SECRET_ACCESS_KEY=your-secret-key PDS_DID_PLC_URL=https://plc.directory PDS_BSKY_APP_VIEW_URL=https://api.bsky.app PDS_BSKY_APP_VIEW_DID=did:web:api.bsky.app PDS_REPORT_SERVICE_URL=https://mod.bsky.app PDS_REPORT_SERVICE_DID=did:plc:ar7c4by46qjdydhdevvrndac PDS_CRAWLERS=https://bsky.network LOG_ENABLED=true PDS_EMAIL_SMTP_URL= PDS_EMAIL_FROM_ADDRESS= </syntaxhighlight> We should set <code>PDS_JWT_SECRET</code> to a pseudo-random value generated with the following command. <syntaxhighlight lang="bash"> openssl rand --hex 16 </syntaxhighlight> Likewise for <code>PDS_ADMIN_PASSWORD</code> <syntaxhighlight lang="bash"> openssl rand --hex 16 </syntaxhighlight> We'll also need to set <code>PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX</code> to the value generated with the following command. <syntaxhighlight lang="bash"> openssl ecparam --name secp256k1 --genkey --noout --outform DER | tail --bytes=+8 | head --bytes=32 | xxd --plain --cols 32 </syntaxhighlight> As per the <code>EnvironmentFile</code> setting in <code>pds.container</code>, we should store <code>pds.env</code> at <code>/etc/pds.env</code>. == Starting the PDS == The following systemd command will load the files we placed under <code>/etc/containers/systemd/</code> and generate systemd unit files from them. <syntaxhighlight lang="bash"> sudo systemctl daemon-reload </syntaxhighlight> We should now be able to query <code>pds.service</code> by running <code>sudo systemctl status pds.service</code>. Note that it will show the unit as inactive until it is started. Now we can start the units. <syntaxhighlight lang="bash"> sudo systemctl start pds.service </syntaxhighlight> This should pull in the PDS container image from the registry and start it. We can check the status with <code>sudo systemctl status pds.service</code>. == Caddy configuration == A valid Caddy configuration should look like this: <syntaxhighlight> { email myemail@example.com on_demand_tls { ask http://localhost:3000/tls-check } } # PDS *.pds.example.com, pds.example.com { tls { on_demand } reverse_proxy http://localhost:3000 } # Anything else for your server </syntaxhighlight> == pdsadmin.sh == We can create <code>pdsadmin.sh</code> and put it somewhere in our system's binary <code>PATH</code>, such as <code>/usr/local/bin/pdsadmin.sh</code>. <syntaxhighlight lang="bash"> #!/usr/bin/env bash set -o errexit set -o nounset set -o pipefail PDSADMIN_BASE_URL="https://raw.githubusercontent.com/bluesky-social/pds/main/pdsadmin" export PDS_ENV_FILE="/etc/pds.env" # Command to run COMMAND="${1:-help}" shift || true # we don't actually need root here since it only is required # Download the script, if it exists SCRIPT_URL="${PDSADMIN_BASE_URL}/${COMMAND}.sh" SCRIPT_FILE="$(mktemp /tmp/pdsadmin.${COMMAND}.XXXXXX)" if [[ "${COMMAND}" == "update" ]]; then echo "ERROR: self-update not supported via podman" exit 1 fi if ! curl --fail --silent --show-error --location --output "${SCRIPT_FILE}" "${SCRIPT_URL}"; then echo "ERROR: ${COMMAND} not found" exit 2 fi chmod +x "${SCRIPT_FILE}" if "${SCRIPT_FILE}" "$@"; then rm -f "${SCRIPT_FILE}" fi </syntaxhighlight> Make the file executable. <syntaxhighlight lang="bash"> sudo chmod +x /usr/local/bin/pdsadmin.sh </syntaxhighlight> We can now run <code>pdsadmin.sh</code> with no arguments to see usage info. We'll of course need to create an account on our new PDS. == Verifying the PDS is online and accessible == Visit https://your-domain.net/xrpc/_health in the browser. Or run the following command in the terminal. Make sure to replace "your-domain.net" with your actual domain. <syntaxhighlight lang="bash"> curl https://your-domain.net/xrpc/_health </syntaxhighlight> We should receive a JSON response with a version, similar to this. <syntaxhighlight lang="json"> {"version":"0.4.204"} </syntaxhighlight> We'll also need to check that WebSockets are working. We can do this with the <code>wsdump</code> tool. We'll need the latest version of Golang to install it. <syntaxhighlight lang="bash"> sudo dnf install golang go install github.com/nrxr/wsdump@latest </syntaxhighlight> Check if WebSockets are working. <syntaxhighlight lang="bash"> wsdump "wss://your-domain.net/xrpc/com.atproto.sync.subscribeRepos?curosr=0" </syntaxhighlight> Note that there will be no events on the WebSocket until they are created in the PDS, so the above command may continue to run with no output. We'll need to press <code>CTRL-C</code> to stop it. == Closing == That's how to setup a Bluesky PDS on CentOS Stream 10. Additionally, this setup should also work on Almalinux 10, Rocky Linux 10, and Fedora 43, but I haven't tested it on any earlier versions of these distributions. I recommend reading [https://github.com/bluesky-social/pds/blob/main/README.md README.md] for more information on using the <code>pdsadmin</code> command, setting up SMTP, and troubleshooting. d4e4f0419164865e9bb7d3eccc6e13aa3a2b2230 3000 1271 5486 2026-05-27T01:40:54Z Hyperreal 388 Init Guide:Fail2ban wikitext text/x-wiki {{GuideWarning}} Ensure fail2ban and firewalld are both installed and activated. <syntaxhighlight lang="bash"> sudo dnf install fail2ban firewalld sudo systemctl enable --now firewalld.service sudo systemctl enable --now fail2ban.service </syntaxhighlight> Copy the default <code>jail.conf</code>. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.local</code>. The values below may already be defined in the <code>jail.conf</code> file, so use the text editor's search feature to find them. Make sure they are uncommented. <syntaxhighlight lang="ini"> bantime = 1h findtime = 1h maxretry = 5 </syntaxhighlight> Copy the fail2ban Firewalld configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.d/00-firewalld.conf /etc/fail2ban/jail.d/00-firewalld.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.d/sshd.local</code>. <syntaxhighlight lang="ini"> [sshd] enabled = true bantime = 1d maxretry = 3 </syntaxhighlight> Restart fail2ban and check the status using the client. <syntaxhighlight lang="bash"> sudo systemctl restart fail2ban.service sudo fail2ban-client status </syntaxhighlight> The output should look like this: <syntaxhighlight> Status |- Number of jail: 1 `- Jail list: sshd </syntaxhighlight> That's it. 21d38e8967a8b8d1e5c113069d37d1d2e3d707e6 5487 5486 2026-05-27T01:41:58Z Hyperreal 388 wikitext text/x-wiki {{GuideWarning}} <blockquote> Currently only RHEL-like distros are supported on this guide. Support for more distros will be added in the future. </blockquote> Ensure fail2ban and firewalld are both installed and activated. <syntaxhighlight lang="bash"> sudo dnf install fail2ban firewalld sudo systemctl enable --now firewalld.service sudo systemctl enable --now fail2ban.service </syntaxhighlight> Copy the default <code>jail.conf</code>. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.local</code>. The values below may already be defined in the <code>jail.conf</code> file, so use the text editor's search feature to find them. Make sure they are uncommented. <syntaxhighlight lang="ini"> bantime = 1h findtime = 1h maxretry = 5 </syntaxhighlight> Copy the fail2ban Firewalld configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.d/00-firewalld.conf /etc/fail2ban/jail.d/00-firewalld.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.d/sshd.local</code>. <syntaxhighlight lang="ini"> [sshd] enabled = true bantime = 1d maxretry = 3 </syntaxhighlight> Restart fail2ban and check the status using the client. <syntaxhighlight lang="bash"> sudo systemctl restart fail2ban.service sudo fail2ban-client status </syntaxhighlight> The output should look like this: <syntaxhighlight> Status |- Number of jail: 1 `- Jail list: sshd </syntaxhighlight> That's it. 0f6b392a55b97056827fb70277bbdda9de9c6759 5492 5487 2026-05-27T01:48:18Z Hyperreal 388 Add FreeBSD support wikitext text/x-wiki {{GuideWarning}} == RHEL-like distros with Firewalld == Ensure fail2ban and firewalld are both installed and activated. <syntaxhighlight lang="bash"> sudo dnf install fail2ban firewalld sudo systemctl enable --now firewalld.service sudo systemctl enable --now fail2ban.service </syntaxhighlight> Copy the default <code>jail.conf</code>. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.local</code>. The values below may already be defined in the <code>jail.conf</code> file, so use the text editor's search feature to find them. Make sure they are uncommented. <syntaxhighlight lang="ini"> bantime = 1h findtime = 1h maxretry = 5 </syntaxhighlight> Copy the fail2ban Firewalld configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.d/00-firewalld.conf /etc/fail2ban/jail.d/00-firewalld.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.d/sshd.local</code>. <syntaxhighlight lang="ini"> [sshd] enabled = true bantime = 1d maxretry = 3 </syntaxhighlight> Restart fail2ban and check the status using the client. <syntaxhighlight lang="bash"> sudo systemctl restart fail2ban.service sudo fail2ban-client status </syntaxhighlight> The output should look like this: <syntaxhighlight> Status |- Number of jail: 1 `- Jail list: sshd </syntaxhighlight> == FreeBSD with PF == Install the fail2ban package. <syntaxhighlight lang="bash"> sudo pkg install py311-fail2ban </syntaxhighlight> Edit <code>/usr/local/etc/fail2ban/jail.local</code>. <syntaxhighlight lang="ini"> [DEFAULT] bantime = 86400 findtime = 3600 maxretry = 3 banaction = pf [sshd] enabled = true </syntaxhighlight> Enable and start fail2ban. <syntaxhighlight lang="bash"> sudo sysrc fail2ban_enable="YES" sudo service fail2ban start </syntaxhighlight> Ensure PF is enabled and started. <syntaxhighlight lang="bash"> sudo sysrc pf_enable="YES" sudo service pf start </syntaxhighlight> Configure <code>/etc/pf.conf</code> <syntaxhighlight> table <fail2ban> persist set skip on lo0 block in all block in quick from <fail2ban> ... </syntaxhighlight> Check and reload the PF rules. <syntaxhighlight lang="bash"> sudo pfctl -nf /etc/pf.conf sudo pfctl -f /etc/pf.conf </syntaxhighlight> 9c5f863aae162be014f647ae7c01d62b3e32b5e1 5499 5492 2026-05-27T05:58:53Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{GuideWarning}} == RHEL-like distros with Firewalld == Ensure fail2ban and firewalld are both installed and activated. <syntaxhighlight lang="bash"> sudo dnf install fail2ban firewalld sudo systemctl enable --now firewalld.service sudo systemctl enable --now fail2ban.service </syntaxhighlight> Copy the default <code>jail.conf</code>. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.local</code>. The values below may already be defined in the <code>jail.conf</code> file, so use the text editor's search feature to find them. Make sure they are uncommented. <syntaxhighlight lang="ini"> bantime = 1h findtime = 1h maxretry = 5 </syntaxhighlight> Copy the fail2ban Firewalld configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.d/00-firewalld.conf /etc/fail2ban/jail.d/00-firewalld.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.d/sshd.local</code>. <syntaxhighlight lang="ini"> [sshd] enabled = true bantime = 1d maxretry = 3 </syntaxhighlight> Restart fail2ban and check the status using the client. <syntaxhighlight lang="bash"> sudo systemctl restart fail2ban.service sudo fail2ban-client status </syntaxhighlight> The output should look like this: <syntaxhighlight> Status |- Number of jail: 1 `- Jail list: sshd </syntaxhighlight> == FreeBSD with PF == Install the fail2ban package. <syntaxhighlight lang="bash"> sudo pkg install py311-fail2ban </syntaxhighlight> Edit <code>/usr/local/etc/fail2ban/jail.local</code>. <syntaxhighlight lang="ini"> [DEFAULT] bantime = 86400 findtime = 3600 maxretry = 3 banaction = pf [sshd] enabled = true </syntaxhighlight> Enable and start fail2ban. <syntaxhighlight lang="bash"> sudo sysrc fail2ban_enable="YES" sudo service fail2ban start </syntaxhighlight> Ensure PF is enabled and started. <syntaxhighlight lang="bash"> sudo sysrc pf_enable="YES" sudo service pf start </syntaxhighlight> Configure <code>/etc/pf.conf</code> <syntaxhighlight> table <fail2ban> persist set skip on lo0 block in all block in quick from <fail2ban> ... </syntaxhighlight> Check and reload the PF rules. <syntaxhighlight lang="bash"> sudo pfctl -nf /etc/pf.conf sudo pfctl -f /etc/pf.conf </syntaxhighlight> 512f95d8c00edf78a6662517130b30bcee13320f 3000 1136 5488 5253 2026-05-27T01:42:42Z Madonuko 140 Madonuko moved page [[Guide:Switching to Linux]] to [[Guides:Switching to Linux]]: Misspelled title wikitext text/x-wiki {{Work In Progress}} '''Welcome to the penguin side!''' Switching to Linux feels scary at first, but it's likely simpler than you think. You'll likely find your new Linux device just as comfortable, if not more comfortable as the operating system you use today in no time. == Why switch to Linux? == People switch to Linux because they like the level of customization, the freedom to use your devices however you want, the community, and because certain apps and games work better on Linux than on other operating systems. == Choices == Linux is all about choices. Before you start, you need to pick what your distribution of Linux looks like and what it runs under the hood. The Graphical User Interface (GUI) you use on Linux is called a [[Desktop Environments|Desktop Environment]], and the underlying operating system is called a [[Linux Distributions|Linux distribution]]. == Picking a Linux distribution == <!--Discuss on talk page before modifying this section due to potential for bias.--> There are many flavors of Linux. Each distribution has its pros and cons, but in the modern era of Linux, many distributions are quite easy to install, use, and update. If you don't like the Linux distribution you chose, you can switch to another one at any time as long as you know how to back up your data. == Picking a Graphical User Interface (GUI) == When you install a distribution of Linux, the installer that the distribution uses asks you what GUI you want. Unlike Windows or macOS, the GUI isn't baked into the operating system. If you want something that feels familiar to Windows or if you play games, use [[Plasma|KDE Plasma]]. If you're on a touchscreen device or rely on a touchpad gestures consider [[GNOME]]. d0c36815501117ef9d397a5c307ec914e61b8dd7 0 1272 5489 2026-05-27T01:42:43Z Madonuko 140 Madonuko moved page [[Guide:Switching to Linux]] to [[Guides:Switching to Linux]]: Misspelled title wikitext text/x-wiki #REDIRECT [[Guides:Switching to Linux]] 5faa1f1b516a904569e83a08fbc0f74a2955b9bb 3001 1164 5490 4957 2026-05-27T01:42:43Z Madonuko 140 Madonuko moved page [[Talk:Guide:Switching to Linux]] to [[Guides talk:Switching to Linux]]: Misspelled title wikitext text/x-wiki == Soundness of This Guide == This article is suspected to violation of ''impartiality'', which is one of the 4 key values of FOSS Wiki. Currently the article recommends specific Linux distributions, which makes the text biased towards designated entities. Criticisms towards Windows and solely showing different advantages of Linux is also somewhat due to the fact that this wiki is FOSS Wiki, but I am not so sure if the current tone and perspective is acceptable. There had been a similar page previously that recommends specific distributions to newbies, but it was removed due to the aforementioned issues after a very long discussion. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 06:01, 23 May 2026 (UTC) :Addressed the criticisms to reduce bias. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:27, 23 May 2026 (UTC) :I think we should have a new discussion wrt. if we should recommend distros, and how we should do so. :There is value in being able to recommend distros, especially in an environment where chatbots and LLMs have outdated information and new users don't have up-to-date, reliable information about what distros are currently the most reliable and beginner-friendly, as said info would be mostly discussed on Discord, Reddit, etc., and not in an authoritative format. :As "thatonecoder" on Discord stated: :"Precisely; decision paralysis is an issue, and we cannot dismiss it simply on the grounds of remaining unbiased." [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:46, 23 May 2026 (UTC) == What distros do we feel comfortable recommending? == I agree that it's not very unbiased of us to recommend specific distros when Many Distros Exist, however I feel as a resource we need to be approachable to the community and **helpful** to new users who may not know about all the issues that plague distros that aren't often recommended anymore (such as Pop!_OS and Manjaro). It would be good if we got a list of modern, commonly recommended distros that we know are reliable that we feel comfortable recommending to new Linux users. [[User:Deviaze|Deviaze]] ([[User talk:Deviaze|talk]]) 06:28, 23 May 2026 (UTC) :Debian was my first distro and it is truly a distro for all seasons, the caveats with debian is that its coupled to systemd unless you manually migrate it to devuan but otherwise pretty solid considering it doesn't spoonfeed too much [[User:GentooLaws|GentooLaws]] ([[User talk:GentooLaws|talk]]) 06:33, 23 May 2026 (UTC) :I feel like [https://www.linuxliteos.com/ linux lite] is a great beginner distro, I learned about it a few months ago when helping someone out with it. Ultramarine/Fedora have always been my go to recommendations. Bazzite is interesting for new users as well due to the gaming setup out of the box since many think "oh you need to do X,Y,Z, and more" just to get games to work on Linux from what I have seen irl. [[User:Scottc96|Scottc96]] ([[User talk:Scottc96|talk]]) 06:41, 23 May 2026 (UTC) :Every distro has its own problems. It is like better to give a few distros that are well-established and possibly have a caveats page somewhere. Here are some notable examples: :- Mint: caveats with X11, specifically it's incapability to do HDR and weirdness with multi-monitor (probably need more expanding, but something like Xinerama is not perfect iirc and still would be wacky with many different refresh rate monitors). Probably need an accompanied X11 and Wayland difference page regarding this. :- Fedora: caveats with drivers and codecs, which are only using free-licensed ones by default and needing to go through installation via RPMFusion or Terra to have them be installed properly. :- Ubuntu: caveats with using snap store as the default store. This is problematic with some applications, notably Steam, not properly working as intended. The fix to this is to use the steam's deb repository [[User:Ping|Ping]] ([[User talk:Ping|talk]]) 06:50, 23 May 2026 (UTC) ::I strongly agree with @[[User:Ping|Ping]] that we should recommend multiple, [[Debian]] might be good if you want to never ever worry about updates breaking your system except once every 2 years, but might not work on some hardware (for instance, Debian 12 did not boot on my old laptop (though Debian 13 did)). ::[[Fedora]] is very good and is now the go to for many people, but as ping mentioned, there are some licensing issues preventing them from including certain things. ::[[Bazzite]] might be good if you care about gaming (at the cost of many general instructions not being applicable due to its immutable model), and likewise, [[Fedora Atomic]] might be good if you are using a computer for general use and want to make sure nothing breaks (at the cost of some general instructions not working or require workarounds). ::We should definitely discuss any changes to the recommendations on the talk page due to the potential for bias, I added a comment to the page (though it may have been deleted when the previous recommendations were removed). [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 15:47, 23 May 2026 (UTC) 1046a23273c64de0d5371d73270c1bca0ca24a5b 1 1273 5491 2026-05-27T01:42:43Z Madonuko 140 Madonuko moved page [[Talk:Guide:Switching to Linux]] to [[Guides talk:Switching to Linux]]: Misspelled title wikitext text/x-wiki #REDIRECT [[Guides talk:Switching to Linux]] 735d6dba6a2a9d9e4a6d1c00ce30ad0c2a78fd5a 6 1274 5493 2026-05-27T04:45:19Z AyoVizzion 404 wikitext text/x-wiki HaikuOS logo 03933b5fbb607e9cdacf8b8eb835fb383656c8f1 0 1275 5494 2026-05-27T04:46:27Z AyoVizzion 404 added page wikitext text/x-wiki [[File:Haiku-operating-system-252890852.png|thumb|HaikuOS's logo]] HaikuOs is a community driven continuation of BeOS 6b522b1a8feccf51471d1d6518ecfcbac5bb06ca 5495 5494 2026-05-27T05:02:10Z Madonuko 140 Madonuko moved page [[Misc Operating Systems/haiku]] to [[Haiku]] wikitext text/x-wiki [[File:Haiku-operating-system-252890852.png|thumb|HaikuOS's logo]] HaikuOs is a community driven continuation of BeOS 6b522b1a8feccf51471d1d6518ecfcbac5bb06ca 0 1276 5496 2026-05-27T05:02:10Z Madonuko 140 Madonuko moved page [[Misc Operating Systems/haiku]] to [[Haiku]] wikitext text/x-wiki #REDIRECT [[Haiku]] 7aad5bbd1ecc04dec88ed39e38efe139fa1c6372 0 1142 5497 5432 2026-05-27T05:55:42Z MarkH 357 cleanup wikitext text/x-wiki {{stub}} '''Windows''' is a proprietary [[Operating System|operating system]] developed by Microsoft. While originally catered towards personal computers, Windows now offers versions such as Windows Server, Windows IoT, and Windows LTSC. It was first released on November 20, 1985 as Windows 1.0 with a graphical user interface.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Microsoft_Windows|title=Microsoft Windows Wikipedia Entry|accessdate=2026}}</ref> [[Wine]] can be used to run Windows applications on [[UNIX]]-like operating systems such as [[Linux Distributions|Linux]] and [[macOS]]. == References == 6a42ad83d499830373c3400bcc838e28a61c2dc8 0 1277 5498 2026-05-27T05:56:55Z MarkH 357 create redirect wikitext text/x-wiki #REDIRECT [[Windows]] a380fee5de535090059eb5c08a1f7241f1b5e1d1 0 176 5502 5460 2026-05-27T07:10:41Z Int 401 Reword for conciseness wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.5.4, December 9, 2025 [https://kde.org/announcements/plasma/6/6.5.4/] |firstrelease=1.0, July 12, 1998 [https://kde.org/announcements/1-2-3/1.0-beta1/] | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> [[Desktop Environments|desktop environment]] for [[UNIX]]-like [[Operating System|operating systems]] such as [[Linux]] and various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === Plasma includes these apps by default: * System Settings * [https://apps.kde.org/dolphin/ Dolphin] (file manager) * [https://apps.kde.org/discover/ Discover] (app store) * [https://apps.kde.org/konsole Konsole] (terminal emulator) * [https://apps.kde.org/spectacle Spectacle] (screenshot tool) * [https://apps.kde.org/kate Kate] (text editor) * [https://apps.kde.org/ark Ark] (archive manager) * [https://apps.kde.org/gwenview Gwenview] (image viewer) * [https://apps.kde.org/okular Okular] (document viewer) Additionally, KDE offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2026-05-26|403}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2026-05-26|403}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode." In edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects apply special visual effects to the desktop. Plasma includes effects in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' in System Settings. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] rounds window corners on Plasma for both '''[[X11]]''' and '''[[Wayland]]'''. == References == <references /> a7950f478edaabb8ca6484c9a11eff6600617027 0 1278 5503 2026-05-27T08:04:43Z Atmois 13 Create redirect wikitext text/x-wiki #REDIRECT [[GNU Emacs]] 7e178fe36c8b6f67b615cdd9a399703c395cb3b1 0 1279 5505 2026-05-27T08:18:29Z ZeliotL 375 added 3d editing wikitext text/x-wiki = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery. {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |Snapmaker Fullspectrum |[https://github.com/ratdoux/OrcaSlicer-FullSpectrum Github] |A Snapmaker Orca fork that adds color painting by altering filaments on each layer. (might be merged into Main SN Orca soon) |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} 38109011ba4a19e3dc8c6472aaed011ad9ed0e26 0 1280 5506 2026-05-27T08:19:45Z ZeliotL 375 added image editing wikitext text/x-wiki = Raster image editors = Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. == Photo editors == {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} == Drawing == {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} == Sprites/spritesheet editors == {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} b8fa1a0c42c49512d8fd62ae3ef1c91b69177722 5507 5506 2026-05-27T08:21:23Z ZeliotL 375 added vector wikitext text/x-wiki = Raster image editors = Raster images are composed of pixels. This category contains image editors, photo editors, and drawing software. == Photo editors == {| class="wikitable" !Name !External links !Description |- |[[GIMP]] |[https://www.gimp.org/ Website], [https://github.com/GNOME/gimp Github] |GNU Image Manipulation Program is a photograph and raster image editing software |} == Drawing == {| class="wikitable" !Name !External links !Description |- |[[Krita]] |[https://krita.org Website], [https://github.com/KDE/krita Github] |Raster drawing program developed by KDE. |} == Sprites/spritesheet editors == {| class="wikitable" !Name !External links !Description |- |[[Libresprite]] |[https://libresprite.github.io/#!/ Website], [https://github.com/LibreSprite/LibreSprite GitHub] |Open source program for creating and animating sprites. |- |[[PixiEditor]] |[https://pixieditor.net/ Website], [https://github.com/PixiEditor/PixiEditor GitHub] |Node-based sprite creation software. |} = Vector image editors = Vector images are made of lines and math, allowing vector art to be resized without losing quality. Vector art is primarily used for illustrations such as on websites. {| class="wikitable" !Name !External links !Description |- |[[Inkscape]] |[https://inkscape.org/ Website]{{Dead Link|2026-05-26|403}}, [https://gitlab.com/inkscape/inkscape GitLab] |Vector image editor, good for editing SVG files. |- |[[Graphite]] |[https://www.graphite.com/docs/install-the-cli Website], [https://github.com/GraphiteEditor/Graphite GitHub] |Node-based vector image editor written in Rust. |} 57f8d5f99b7f7b714aae0ecbf3762c86c7a3945b 0 1281 5508 2026-05-27T08:22:48Z ZeliotL 375 added video editing wikitext text/x-wiki = Movie makers/video editors = {| class="wikitable" !Name !External links !Description |- |[[Kdenlive]] |[https://kdenlive.org/ Website], [https://github.com/KDE/kdenlive GitHub] |Video editor developed by KDE. |} 8983514aa366752dc8d5fa5b943324ca9bf806ba 0 1134 5510 4709 2026-05-27T09:22:41Z Absurd 336 Added Server Info wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxer-symbol-color.svg|150px]] | caption = | title = Fluxer | releasestatus = Maintained | lastrelease = 0.0.8 | languages = Electron | developers = Hampus Kraft and Contributors | website = https://fluxer.app }} Fluxer is a free, open-source instant messaging and VoIP platform designed as a privacy-focused alternative to Discord. ==Overview== Fluxer is available in Flathub format as well as other official formats including AppImage, tar.gz, RPM, .deb, and more. Fluxer also allows for custom clients and has plans to incorporate federation & self-hosting capabilities in the future. ==Server Info== '''Vultr''' provides Fluxers primary hosting. The main store for account data (messages, Communities, profiles, and other persisted content) is in '''Piscataway, New Jersey''', and the object storage for user-uploaded files runs in the same region. Voice and real-time communication infrastructure also runs on Vultr across multiple regions worldwide, so calls can be routed near you for latency. '''Bunny.net''' operates Fluxers content delivery network, with edge nodes worldwide, for user-generated content on the fluxerusercontent.com domain. In the future, Fluxers wants to offer the ability to partition your data entirely within the EU — for both your account and your communities. As stated in their FAQ Which you can find on https://fluxer.gg/fluxer-hq ==Mobile App== ==Selfhosting== 9fb34f724e76ea4f5c687b9b52300ac0644c2ed2 5513 5510 2026-05-27T09:32:16Z Absurd 336 Cleaned up wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxer-symbol-color.svg|150px]] | caption = | title = Fluxer | releasestatus = Maintained | lastrelease = 0.0.8 | languages = Electron | developers = Hampus Kraft and Contributors | website = https://fluxer.app | sourcecode = https://github.com/fluxerapp/fluxer }} Fluxer is a free, open-source instant messaging and VoIP platform designed as a privacy-focused alternative to Discord. ==Overview== Fluxer is available in Flathub format as well as other official formats including AppImage, tar.gz, RPM, .deb, and more. Fluxer also allows for custom clients and has plans to incorporate federation & self-hosting capabilities in the future. ==Server Info== '''Vultr''' provides Fluxers primary hosting. The main store for account data (messages, Communities, profiles, and other persisted content) is in '''Piscataway, New Jersey''', and the object storage for user-uploaded files runs in the same region. Voice and real-time communication infrastructure also runs on Vultr across multiple regions worldwide, so calls can be routed near you for latency. '''Bunny.net''' operates Fluxers content delivery network, with edge nodes worldwide, for user-generated content on the fluxerusercontent.com domain. In the future, Fluxers wants to offer the ability to partition your data entirely within the EU — for both your account and your communities. As stated in their FAQ Which you can find on https://fluxer.gg/fluxer-hq dbc7563328d721f3b94ac67cffdef228de6f6ac4 6 1282 5511 2026-05-27T09:27:50Z Absurd 336 wikitext text/x-wiki Fluxer 0e77fde388994d45447419eba2d20d6d110cdc56 6 1283 5512 2026-05-27T09:30:42Z Absurd 336 wikitext text/x-wiki Fluxer 0e77fde388994d45447419eba2d20d6d110cdc56 0 1187 5514 5251 2026-05-27T10:01:45Z Int 401 Reword for clarity wikitext text/x-wiki [[Category:Software]] [[Category:Game Engines]] {{Stub}} {{SoftwareInfobox | image = [[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]] | caption = | title = Godot | releasestatus = Maintained | lastrelease = 4.6.3-stable, 2026-05-20 | firstrelease = 1.0, 2014-12-15 | languages = [[C++]] | developers = Juan Linietsky, Ariel Manzur, and Contributors | website = [https://github.com/godotengine/godot github.com/godotengine/godot], [https://godotengine.org godotengine.org] }} Godot is a general-purpose [[Free and Open Source Software|FOSS]] game engine. Godot works with nodes and scenes. Scenes are composed of nodes, and scenes are nodes themselves. Scripting can be done with [[GDScript]], C#, C++, and other languages through community extensions.<ref>[https://godotengine.org/features/#script Features], Godot Engine, 2026-05-20 (Accessed: 2026-05-25)</ref> The name comes from the classic play ''[[wikipedia:Waiting_for_Godot|Waiting for Godot]]'' and is pronounced as therein. This results in the pronunciation varying between languages, which the project officially describes as "beautiful".<ref>[https://godotengine.org/press/ Press Kit], Godot Engine, 2026-05-01 (Accessed: 2026-05-25)</ref> 943ea14d819025bc9d62891e878e60fa5789f259 5515 5514 2026-05-27T10:06:29Z Int 401 Add installation instructions for binaries, Flatpak, and Arch wikitext text/x-wiki [[Category:Software]] [[Category:Game Engines]] {{Stub}} {{SoftwareInfobox | image = [[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]] | caption = | title = Godot | releasestatus = Maintained | lastrelease = 4.6.3-stable, 2026-05-20 | firstrelease = 1.0, 2014-12-15 | languages = [[C++]] | developers = Juan Linietsky, Ariel Manzur, and Contributors | website = [https://github.com/godotengine/godot github.com/godotengine/godot], [https://godotengine.org godotengine.org] }} Godot is a general-purpose [[Free and Open Source Software|FOSS]] game engine. Godot works with nodes and scenes. Scenes are composed of nodes, and scenes are nodes themselves. Scripting can be done with [[GDScript]], C#, C++, and other languages through community extensions.<ref>[https://godotengine.org/features/#script Features], Godot Engine, 2026-05-20 (Accessed: 2026-05-25)</ref> The name comes from the classic play ''[[wikipedia:Waiting_for_Godot|Waiting for Godot]]'' and is pronounced as therein. This results in the pronunciation varying between languages, which the project officially describes as "beautiful".<ref>[https://godotengine.org/press/ Press Kit], Godot Engine, 2026-05-01 (Accessed: 2026-05-25)</ref> === Installation === ==== Binaries ==== Godot provides executable binaries on their [https://godotengine.org/download website]. ==== Flatpak ==== Godot is on [[Flathub]]. Install it with [[Flatpak]]:<syntaxhighlight lang="sh"> flatpak install org.godotengine.Godot </syntaxhighlight> ==== Arch Linux ==== Godot is on the official [[Arch Linux]] repositories. Install it with [[Pacman]]:<syntaxhighlight lang="sh"> sudo pacman -S godot </syntaxhighlight> === References === d714dc9b72d7d673265d19662698e53a9e6b9b57 5516 5515 2026-05-27T10:11:33Z Int 401 Provide installation instructions for C# scripting support wikitext text/x-wiki [[Category:Software]] [[Category:Game Engines]] {{Stub}} {{SoftwareInfobox | image = [[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]] | caption = | title = Godot | releasestatus = Maintained | lastrelease = 4.6.3-stable, 2026-05-20 | firstrelease = 1.0, 2014-12-15 | languages = [[C++]] | developers = Juan Linietsky, Ariel Manzur, and Contributors | website = [https://github.com/godotengine/godot github.com/godotengine/godot], [https://godotengine.org godotengine.org] }} Godot is a general-purpose [[Free and Open Source Software|FOSS]] game engine. Godot works with nodes and scenes. Scenes are composed of nodes, and scenes are nodes themselves. Scripting can be done with [[GDScript]], C#, C++, and other languages through community extensions.<ref>[https://godotengine.org/features/#script Features], Godot Engine, 2026-05-20 (Accessed: 2026-05-25)</ref> The name comes from the classic play ''[[wikipedia:Waiting_for_Godot|Waiting for Godot]]'' and is pronounced as therein. This results in the pronunciation varying between languages, which the project officially describes as "beautiful".<ref>[https://godotengine.org/press/ Press Kit], Godot Engine, 2026-05-01 (Accessed: 2026-05-25)</ref> === Installation === ==== Binaries ==== Godot provides executable binaries on their [https://godotengine.org/download website]. ==== Flatpak ==== There is an '''unofficial''' Godot flatpak on [[Flathub]]. Install it with [[Flatpak]]:<syntaxhighlight lang="sh">flatpak install org.godotengine.Godot</syntaxhighlight>To include C# scripting support:<syntaxhighlight lang="sh"> flatpak install org.godotengine.GodotSharp </syntaxhighlight> ==== Arch Linux ==== Godot is on the official [[Arch Linux]] repositories. Install it with [[Pacman]]:<syntaxhighlight lang="sh"> pacman -S godot </syntaxhighlight>To include C# scripting support:<syntaxhighlight lang="sh"> pacman -S godot godot-mono </syntaxhighlight> === References === 0105e7bc8dd71d01520bb673d4e2db3c5444c5eb 5518 5516 2026-05-27T10:33:43Z Veri 398 wikitext text/x-wiki [[Category:Software]] [[Category:Game Engines]] {{Stub}} {{SoftwareInfobox | image = [[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]] | caption = | title = Godot | releasestatus = Maintained | lastrelease = 4.6.3-stable, 2026-05-20 | firstrelease = 1.0, 2014-12-15 | languages = [[C++]] | developers = Juan Linietsky, Ariel Manzur, and Contributors | website = [https://github.com/godotengine/godot github.com/godotengine/godot], [https://godotengine.org godotengine.org] }} Godot is a general-purpose [[Free and Open Source Software|FOSS]] game engine. Godot works with nodes and scenes. Scenes are composed of nodes, and scenes are nodes themselves. Scripting can be done with [[GDScript]], C#, C++, and other languages through community extensions.<ref>[https://godotengine.org/features/#script Features], Godot Engine, 2026-05-20 (Accessed: 2026-05-25)</ref> The name comes from the classic play ''[[wikipedia:Waiting_for_Godot|Waiting for Godot]]'' and is pronounced as therein. This results in the pronunciation varying between languages, which the project officially describes as "beautiful".<ref>[https://godotengine.org/press/ Press Kit], Godot Engine, 2026-05-01 (Accessed: 2026-05-25)</ref> === Installation === ==== Binaries ==== Godot provides executable binaries on their [https://godotengine.org/download website]. ==== Flatpak ==== There is an '''unofficial''' Godot flatpak on [[Flathub]]. Install it with [[Flatpak]]:<syntaxhighlight lang="sh">flatpak install org.godotengine.Godot</syntaxhighlight>To include C# scripting support:<syntaxhighlight lang="sh"> flatpak install org.godotengine.GodotSharp </syntaxhighlight> ==== Steam ==== Godot is available on Steam. You can find its listing [https://store.steampowered.com/app/404790/Godot_Engine/ here] Note that the version with C# scripting support is '''not''' available through Steam and must be achieved through other methods listed. ==== Arch Linux ==== Godot is on the official [[Arch Linux]] repositories. Install it with [[Pacman]]:<syntaxhighlight lang="sh"> pacman -S godot </syntaxhighlight>To include C# scripting support:<syntaxhighlight lang="sh"> pacman -S godot godot-mono </syntaxhighlight> === References === c287ae21ffd10954eef3bddfa4bb303367239bb0 5519 5518 2026-05-27T10:34:51Z Veri 398 /* Flatpak */ wikitext text/x-wiki [[Category:Software]] [[Category:Game Engines]] {{Stub}} {{SoftwareInfobox | image = [[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]] | caption = | title = Godot | releasestatus = Maintained | lastrelease = 4.6.3-stable, 2026-05-20 | firstrelease = 1.0, 2014-12-15 | languages = [[C++]] | developers = Juan Linietsky, Ariel Manzur, and Contributors | website = [https://github.com/godotengine/godot Github], [https://godotengine.org godotengine.org] }} Godot is a general-purpose [[Free and Open Source Software|FOSS]] game engine. Godot works with nodes and scenes. Scenes are composed of nodes, and scenes are nodes themselves. Scripting can be done with [[GDScript]], C#, C++, and other languages through community extensions.<ref>[https://godotengine.org/features/#script Features], Godot Engine, 2026-05-20 (Accessed: 2026-05-25)</ref> The name comes from the classic play ''[[wikipedia:Waiting_for_Godot|Waiting for Godot]]'' and is pronounced as therein. This results in the pronunciation varying between languages, which the project officially describes as "beautiful".<ref>[https://godotengine.org/press/ Press Kit], Godot Engine, 2026-05-01 (Accessed: 2026-05-25)</ref> === Installation === ==== Binaries ==== Godot provides executable binaries on their [https://godotengine.org/download website]. ==== Flatpak ==== There is an '''unofficial''' Godot flatpak on [[Flathub]]. Install it with [[Flatpak]]:<syntaxhighlight lang="sh">flatpak install org.godotengine.Godot</syntaxhighlight>To include C# scripting support:<syntaxhighlight lang="sh"> flatpak install org.godotengine.GodotSharp </syntaxhighlight> ==== Steam ==== Godot is available on Steam. You can find its listing [https://store.steampowered.com/app/404790/Godot_Engine/ here] Note that the version with C# scripting support is '''not''' available through Steam and must be achieved through other methods listed. ==== Arch Linux ==== Godot is on the official [[Arch Linux]] repositories. Install it with [[Pacman]]:<syntaxhighlight lang="sh"> pacman -S godot </syntaxhighlight>To include C# scripting support:<syntaxhighlight lang="sh"> pacman -S godot godot-mono </syntaxhighlight> === References === 5a0cbb3456631ab20e9ea8c231b155fc0d33c618 0 1246 5517 5415 2026-05-27T10:23:29Z Veri 398 wikitext text/x-wiki {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an '''official''' [[flavor]] of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be '''user-friendly''', '''fast''', and '''customizable''', targeted at both '''newcomers''' and '''experienced''' Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the '''same''' as the central Ubuntu [[Linux Distributions|Linux distribution]], with exception that it is '''community-run''' by contributors<ref>{{Cite|url=https://kubuntu.org/community/|title=Community - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref>. It also follows the same release schedule as Ubuntu, having a new release every '''6 months'''. e54250ea88d7e1b7230f88bb674a0786b38a40c9 3 1284 5520 2026-05-27T10:48:32Z Madonuko 140 /* Edit Summary */ new section wikitext text/x-wiki == Edit Summary == Thank you for contributing to FOSS Wiki. This is a reminder that you should write a short edit summary every time you create an edit, so that other editors can review your edits more easily. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 10:48, 27 May 2026 (UTC) 5532793af34678979f6adf2d710e3144aab019d6 0 268 5521 3707 2026-05-27T11:10:06Z Sparrow 362 chore: update fastfetch version to latest wikitext text/x-wiki [[Category:Software]] [[Category:Command-line software]] [[Category:System information tools]] {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch running on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.63.1, 2026-05-13 | languages = [[C (programming language)|C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch GitHub repository] }} '''Fastfetch''' is a cross-platform command-line utility for displaying system information, similar in purpose to [[Neofetch]]. It is primarily written in [[C (programming language)|C]] and is designed with a strong focus on speed and low resource usage. Fastfetch can display details about the [[Operating system|operating system]], hardware components, and installed software in a highly configurable format<ref name=":0">{{Cite|url=https://github.com/fastfetch-cli/fastfetch|title=Fastfetch GitHub page}}</ref>. The tool supports a wide range of modules, allowing users to customise the output to include information such as CPU, GPU, memory, storage, display resolution, kernel version, package count, and more. It is actively maintained and available for Linux, macOS, and Windows<ref name=":0" />. == See also == * [[Neofetch]] * [[Screenfetch]] == References == <references /> 16a0572955dde065d8f291101537a16310ae8d98 5522 5521 2026-05-27T11:12:34Z Sparrow 362 chore: add license and firstRelease wikitext text/x-wiki [[Category:Software]] [[Category:Command-line software]] [[Category:System information tools]] {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch running on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.63.1, 2026-05-13 | languages = [[C (programming language)|C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch GitHub repository] | license = MIT License | firstrelease = 1.0.0, 2020-03-20 }} '''Fastfetch''' is a cross-platform command-line utility for displaying system information, similar in purpose to [[Neofetch]]. It is primarily written in [[C (programming language)|C]] and is designed with a strong focus on speed and low resource usage. Fastfetch can display details about the [[Operating system|operating system]], hardware components, and installed software in a highly configurable format<ref name=":0">{{Cite|url=https://github.com/fastfetch-cli/fastfetch|title=Fastfetch GitHub page}}</ref>. The tool supports a wide range of modules, allowing users to customise the output to include information such as CPU, GPU, memory, storage, display resolution, kernel version, package count, and more. It is actively maintained and available for Linux, macOS, and Windows<ref name=":0" />. == See also == * [[Neofetch]] * [[Screenfetch]] == References == <references /> d49eb8def26b1bc51c67d6a5313957d2dcb4508e 5529 5522 2026-05-27T12:08:02Z Sparrow 362 fix: license field wikitext text/x-wiki [[Category:Software]] [[Category:Command-line software]] [[Category:System information tools]] {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch running on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.63.1, 2026-05-13 | languages = [[C (programming language)|C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch GitHub repository] | license = [[MIT]] | firstrelease = 1.0.0, 2020-03-20 }} '''Fastfetch''' is a cross-platform command-line utility for displaying system information, similar in purpose to [[Neofetch]]. It is primarily written in [[C (programming language)|C]] and is designed with a strong focus on speed and low resource usage. Fastfetch can display details about the [[Operating system|operating system]], hardware components, and installed software in a highly configurable format<ref name=":0">{{Cite|url=https://github.com/fastfetch-cli/fastfetch|title=Fastfetch GitHub page}}</ref>. The tool supports a wide range of modules, allowing users to customise the output to include information such as CPU, GPU, memory, storage, display resolution, kernel version, package count, and more. It is actively maintained and available for Linux, macOS, and Windows<ref name=":0" />. == See also == * [[Neofetch]] * [[Screenfetch]] == References == <references /> 90171bc9660be28326797c532cc514e741c35f4e 5530 5529 2026-05-27T12:09:03Z Sparrow 362 fix license field not actually linking to page wikitext text/x-wiki [[Category:Software]] [[Category:Command-line software]] [[Category:System information tools]] {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch running on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.63.1, 2026-05-13 | languages = [[C (programming language)|C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch GitHub repository] | license = [[MIT License|MIT]] | firstrelease = 1.0.0, 2020-03-20 }} '''Fastfetch''' is a cross-platform command-line utility for displaying system information, similar in purpose to [[Neofetch]]. It is primarily written in [[C (programming language)|C]] and is designed with a strong focus on speed and low resource usage. Fastfetch can display details about the [[Operating system|operating system]], hardware components, and installed software in a highly configurable format<ref name=":0">{{Cite|url=https://github.com/fastfetch-cli/fastfetch|title=Fastfetch GitHub page}}</ref>. The tool supports a wide range of modules, allowing users to customise the output to include information such as CPU, GPU, memory, storage, display resolution, kernel version, package count, and more. It is actively maintained and available for Linux, macOS, and Windows<ref name=":0" />. == See also == * [[Neofetch]] * [[Screenfetch]] == References == <references /> b79795ddf644a2c9e3164d71f45960ce58ed827a 0 1265 5523 5430 2026-05-27T11:13:45Z Int 401 Fix infobox image wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = Wine | image = [[File:Wine Logo.png|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. === Installation === ==== Arch Linux ==== Wine is on the official Arch Linux repositories. You can install it using [[Pacman]]:<syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight>To install the staging build:<syntaxhighlight lang="sh"> sudo pacman -S wine-staging </syntaxhighlight> === Usage === Wine is a [[CLI|command-line]] program. Supply a Windows executable file (.exe) to run it:<syntaxhighlight lang="sh"> wine <path to executable> </syntaxhighlight> ==== Prefixes ==== A Wine prefix is a directory where Wine operates. It contains a minimal Windows filesystem (a.k.a. ''C: drive''). By default, this is <code>~/.wine</code>. To change it, modify the <code>WINEPREFIX</code> environment variable. For example, to run Wine at <code>myprefix/</code>:<syntaxhighlight lang="sh"> WINEPREFIX=myprefix wine application.exe </syntaxhighlight> === Performance === ==== dxvk ==== By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). 389fc2a7382dddf6e33dc306f0d9b93ac9547e06 5535 5523 2026-05-27T12:56:07Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = Wine | image = [[File:Wine Logo.png|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. == Installation == === Arch Linux === Wine is on the official Arch Linux repositories. You can install it using [[Pacman]]:<syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight>To install the staging build:<syntaxhighlight lang="sh"> sudo pacman -S wine-staging </syntaxhighlight> == Usage == Wine is a [[CLI|command-line]] program. Supply a Windows executable file (.exe) to run it:<syntaxhighlight lang="sh"> wine <path to executable> </syntaxhighlight> === Prefixes === A Wine prefix is a directory where Wine operates. It contains a minimal Windows filesystem (a.k.a. ''C: drive''). By default, this is <code>~/.wine</code>. To change it, modify the <code>WINEPREFIX</code> environment variable. For example, to run Wine at <code>myprefix/</code>:<syntaxhighlight lang="sh"> WINEPREFIX=myprefix wine application.exe </syntaxhighlight> == Performance == === dxvk === By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). c5896afec5ebb5526032a40192ead404a920a4c1 0 261 5524 4070 2026-05-27T11:16:57Z Sparrow 362 chore: add license wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[Bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] | license = MIT License }} Neofetch was a command-line system information tool written in [[bash]] which displays information about your [[Operating System|operating system]], software and hardware. It was created by Dylan Araps in 2017 and was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]], a neofetch-like utility written in [[C]], and [[hyfetch]], a fork of neofetch with pride flags. == References == <references /> 557de0dc5abb9cef4568b43ef0e0c2a5b1295211 5528 5524 2026-05-27T12:06:20Z Madonuko 140 fix license field wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Neofetch.png|thumb]] | caption = Neofetch on NixOS | title = Neofetch | releasestatus = Abandoned | lastrelease = 7.1.0, 2020-08-02 | languages = [[Bash]] | developers = dylanaraps | website = [https://github.com/dylanaraps/neofetch github.com/dylanaraps/neofetch] | license = [[MIT License|MIT]] }} Neofetch was a command-line system information tool written in [[bash]] which displays information about your [[Operating System|operating system]], software and hardware. It was created by Dylan Araps in 2017 and was archived on the 26th April 2024.<ref>https://github.com/dylanaraps/neofetch Neofetch Repository</ref> Alternatives to Neofetch include [[fastfetch]], a neofetch-like utility written in [[C]], and [[hyfetch]], a fork of neofetch with pride flags. == References == <references /> 3192c936a4b61995a31c07a6f4f330c7951912e8 0 1009 5525 4167 2026-05-27T11:56:00Z Habaja1 377 added small overview text wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = Bazzite | image = [[File:Bazzite Logo.svg|200px]] | caption = The Bazzite logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Flatpak]] | defaultdesktops = [[GNOME]],[[KDE Plasma]] | usagetype = Gaming | architectures = x86_64 | website = [https://bazzite.gg/ bazzite.gg] }}'''Bazzite''' (ˈba-ˌzīt,) is a gaming focused [[Fedora]]-based (or [[Fedora Kinoite]] if the KDE Plasma desktop environment is chosen) [[Linux Distributions|Linux distribution]]. [[Category:Linux Distributions]] 648c7980359c8d74ed4a304d69f4b65137c1ae02 5532 5525 2026-05-27T12:31:53Z Habaja1 377 bare bones wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = Bazzite | image = [[File:Bazzite Logo.svg|200px]] | caption = The Bazzite logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Flatpak]] | defaultdesktops = [[GNOME]],[[KDE Plasma]] | usagetype = Gaming | architectures = x86_64 | website = [https://bazzite.gg/ bazzite.gg] }}'''Bazzite''' (ˈba-ˌzīt,) is a gaming focused [[Fedora]]-based [[Linux Distributions|Linux distribution]]. == History == == Features == == Installation == == Trivia == == Refrences == [[Category:Linux Distributions]] a09a46832dd73694cf1466da050d036a3f0b9d7f 5534 5532 2026-05-27T12:55:57Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}} {{DistributionInfobox | title = Bazzite | image = [[File:Bazzite Logo.svg|200px]] | caption = The Bazzite logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Flatpak]] | defaultdesktops = [[GNOME]],[[KDE Plasma]] | usagetype = Gaming | architectures = x86_64 | website = [https://bazzite.gg/ bazzite.gg] }} '''Bazzite''' (ˈba-ˌzīt,) is a gaming focused [[Fedora]]-based [[Linux Distributions|Linux distribution]]. == History == == Features == == Installation == == Trivia == == Refrences == b5fd88c52deeda19e522bf868b5dfcc45543811e 5566 5534 2026-05-28T12:42:48Z Habaja1 377 wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}} {{DistributionInfobox | title = Bazzite | image = [[File:Bazzite Logo.svg|200px]] | caption = The Bazzite logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[DNF]], [[Flatpak]] | defaultdesktops = [[GNOME]],[[KDE Plasma]] | usagetype = Gaming | architectures = x86_64 | website = [https://bazzite.gg/ bazzite.gg] }} '''Bazzite''' (ˈba-ˌzīt,) is a gaming focused [[Fedora]]-based [[Linux Distributions|Linux distribution]]. == History == == Features == == Installation == == Trivia == == Refrences == 3bd8f83f2412337bc9791b1ee40c1dc9cf05e96d 6 1285 5526 2026-05-27T12:01:37Z Sparrow 362 Logo of Quickshell wikitext text/x-wiki == Summary == Logo of Quickshell == Licensing == {{GPL}} ac9a3d9cd2eab8fe6ec05f85a0c9b12a370466b6 5527 5526 2026-05-27T12:04:35Z Sparrow 362 Sparrow uploaded a new version of [[File:Quickshell logo.png]] wikitext text/x-wiki == Summary == Logo of Quickshell == Licensing == {{GPL}} ac9a3d9cd2eab8fe6ec05f85a0c9b12a370466b6 0 1286 5531 2026-05-27T12:23:18Z Sparrow 362 Create Quickshell page wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Quickshell_logo.png|thumb]] | caption = | title = Quickshell | releasestatus = Maintained | lastrelease = 3.0, 2026-05-04 | languages = C++, QML | developers = outfoxxed | website = [https://quickshell.org quickshell.org] | sourcecode = [https://git.outfoxxed.me/quickshell/quickshell git.outfoxxed.me] | license = [[GPL|GNU GPL]] }} '''Quickshell''' is a open-source toolkit which provides users ways to create status bars, desktop shells and other desktop components.<ref>{{Cite|url=https://quickshell.org/|title=Quickshell Website|author=outfoxxed|year=2025|accessdate=2026-05-27}}</ref> Quickshell uses QML to handle customization and exposes extensive functionality to the user, such as networking, [[PipeWire]], and MPRIS support. 54832ec35d0b2df012b84f523780d4f0c07d266a 3000 1287 5533 2026-05-27T12:55:28Z Hyperreal 388 Init Guide:Get_latest_release_from_GitHub_Repo wikitext text/x-wiki {{GuideWarning}} The following is a collection of ways to get the latest release of a program from its GitHub repository using the command line. The example repositories used below can be replaced with any repository hosted on GitHub. == sed == This gets the URL of the latest release using <code>sed</code>. It then filters out files that contain ".rpm" and ".deb". <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | sed -n 's/.*"browser_download_url": //p' \ | grep -v -E ".rpm|.deb" \ | tr -d '"' </syntaxhighlight> Output: <syntaxhighlight> https://github.com/matheus-git/systemd-manager-tui/releases/download/v1.2.4/systemd-manager-tui </syntaxhighlight> To get the SHA256 digest corresponding to the file, use <code>jq</code> in combination with <code>awk</code>. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | jq -c '.assets.[] | select(.browser_download_url | contains(".deb") or contains(".rpm") | not) | .digest' \ | tr -d '"' \ | awk -F: '{print $2}' </syntaxhighlight> Output: <syntaxhighlight> 63a977112f97462d55a4e41fc0280d32b3f801c3b9f0fad329cd79843c7ae1ec </syntaxhighlight> == jq == If you know that the file you want contains "-en.pyz" in the filename, you can use <code>jq</code> to select it. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' </syntaxhighlight> Output: <syntaxhighlight> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> You can then pipe this to <code>curl</code> via the <code>xargs</code> command to download the file to the current working directory. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' \ | xargs -I {} curl -SL -O {} </syntaxhighlight> == Nushell == <syntaxhighlight lang="nushell"> http get https://api.github.com/repos/9001/copyparty/releases/latest | get assets.browser_download_url | find "-en.pyz" | get 0 </syntaxhighlight> Output: <syntaxhighlight> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> == See Also == [https://gist.github.com/steinwaywhw/a4cd19cda655b8249d908261a62687f8 {{GuideWarning}} The following is a collection of ways to get the latest release of a program from its GitHub repository using the command line. The example repositories used below can be replaced with any repository hosted on GitHub. == sed == This gets the URL of the latest release using <code>sed</code>. It then filters out files that contain ".rpm" and ".deb". <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | sed -n 's/.*"browser_download_url": //p' \ | grep -v -E ".rpm|.deb" \ | tr -d '"' </syntaxhighlight> Output: <syntaxhighlight> https://github.com/matheus-git/systemd-manager-tui/releases/download/v1.2.4/systemd-manager-tui </syntaxhighlight> To get the SHA256 digest corresponding to the file, use <code>jq</code> in combination with <code>awk</code>. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | jq -c '.assets.[] | select(.browser_download_url | contains(".deb") or contains(".rpm") | not) | .digest' \ | tr -d '"' \ | awk -F: '{print $2}' </syntaxhighlight> Output: <syntaxhighlight> 63a977112f97462d55a4e41fc0280d32b3f801c3b9f0fad329cd79843c7ae1ec </syntaxhighlight> == jq == If you know that the file you want contains "-en.pyz" in the filename, you can use <code>jq</code> to select it. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' </syntaxhighlight> Output: <syntaxhighlight> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> You can then pipe this to <code>curl</code> via the <code>xargs</code> command to download the file to the current working directory. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' \ | xargs -I {} curl -SL -O {} </syntaxhighlight> == Nushell == <syntaxhighlight lang="nushell"> http get https://api.github.com/repos/9001/copyparty/releases/latest | get assets.browser_download_url | find "-en.pyz" | get 0 </syntaxhighlight> Output: <syntaxhighlight> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> == See Also == * https://gist.github.com/steinwaywhw/a4cd19cda655b8249d908261a62687f8 ade03b6e0cb6d3aaff9d99afa29468a87beaeb83 5536 5533 2026-05-27T12:56:29Z Hyperreal 388 Remove duplicate wikitext text/x-wiki {{GuideWarning}} The following is a collection of ways to get the latest release of a program from its GitHub repository using the command line. The example repositories used below can be replaced with any repository hosted on GitHub. == sed == This gets the URL of the latest release using <code>sed</code>. It then filters out files that contain ".rpm" and ".deb". <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | sed -n 's/.*"browser_download_url": //p' \ | grep -v -E ".rpm|.deb" \ | tr -d '"' </syntaxhighlight> Output: <syntaxhighlight> https://github.com/matheus-git/systemd-manager-tui/releases/download/v1.2.4/systemd-manager-tui </syntaxhighlight> To get the SHA256 digest corresponding to the file, use <code>jq</code> in combination with <code>awk</code>. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | jq -c '.assets.[] | select(.browser_download_url | contains(".deb") or contains(".rpm") | not) | .digest' \ | tr -d '"' \ | awk -F: '{print $2}' </syntaxhighlight> Output: <syntaxhighlight> 63a977112f97462d55a4e41fc0280d32b3f801c3b9f0fad329cd79843c7ae1ec </syntaxhighlight> == jq == If you know that the file you want contains "-en.pyz" in the filename, you can use <code>jq</code> to select it. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' </syntaxhighlight> Output: <syntaxhighlight> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> You can then pipe this to <code>curl</code> via the <code>xargs</code> command to download the file to the current working directory. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' \ | xargs -I {} curl -SL -O {} </syntaxhighlight> == Nushell == <syntaxhighlight lang="nushell"> http get https://api.github.com/repos/9001/copyparty/releases/latest | get assets.browser_download_url | find "-en.pyz" | get 0 </syntaxhighlight> Output: <syntaxhighlight> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> == See Also == * https://gist.github.com/steinwaywhw/a4cd19cda655b8249d908261a62687f8 025d94392e18d401c95ecf628f36962b712179f2 0 1187 5537 5519 2026-05-27T12:56:46Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Software]] [[Category:Game Engines]] {{Stub}} {{SoftwareInfobox | image = [[File:Godot logo large color light.png|alt=Godot Game Engine logo|thumb|]] | caption = | title = Godot | releasestatus = Maintained | lastrelease = 4.6.3-stable, 2026-05-20 | firstrelease = 1.0, 2014-12-15 | languages = [[C++]] | developers = Juan Linietsky, Ariel Manzur, and Contributors | website = [https://github.com/godotengine/godot Github], [https://godotengine.org godotengine.org] }} Godot is a general-purpose [[Free and Open Source Software|FOSS]] game engine. Godot works with nodes and scenes. Scenes are composed of nodes, and scenes are nodes themselves. Scripting can be done with [[GDScript]], C#, C++, and other languages through community extensions.<ref>[https://godotengine.org/features/#script Features], Godot Engine, 2026-05-20 (Accessed: 2026-05-25)</ref> The name comes from the classic play ''[[wikipedia:Waiting_for_Godot|Waiting for Godot]]'' and is pronounced as therein. This results in the pronunciation varying between languages, which the project officially describes as "beautiful".<ref>[https://godotengine.org/press/ Press Kit], Godot Engine, 2026-05-01 (Accessed: 2026-05-25)</ref> == Installation == === Binaries === Godot provides executable binaries on their [https://godotengine.org/download website]. === Flatpak === There is an '''unofficial''' Godot flatpak on [[Flathub]]. Install it with [[Flatpak]]:<syntaxhighlight lang="sh">flatpak install org.godotengine.Godot</syntaxhighlight>To include C# scripting support:<syntaxhighlight lang="sh"> flatpak install org.godotengine.GodotSharp </syntaxhighlight> === Steam === Godot is available on Steam. You can find its listing [https://store.steampowered.com/app/404790/Godot_Engine/ here] Note that the version with C# scripting support is '''not''' available through Steam and must be achieved through other methods listed. === Arch Linux === Godot is on the official [[Arch Linux]] repositories. Install it with [[Pacman]]:<syntaxhighlight lang="sh"> pacman -S godot </syntaxhighlight>To include C# scripting support:<syntaxhighlight lang="sh"> pacman -S godot godot-mono </syntaxhighlight> == References == da99f1db827157e76a711b6e4917c99c539a5ddc 3000 1270 5538 5485 2026-05-27T13:15:22Z Hyperreal 388 Add References wikitext text/x-wiki {{GuideWarning}} This guide is based on the documentation<ref name="pds">[https://github.com/bluesky-social/pds github.com/bluesky-social/pds], GitHub, accessed 2026-05-27</ref><ref>[https://github.com/bluesky-social/deploy-recipes github.com/bluesky-social/deploy-recipes], GitHub, accessed 2026-05-27</ref> from the official Bluesky PDS GitHub repos. <blockquote> CentOS Stream is not an officially supported distribution by the upstream PDS maintainers. </blockquote> == Minimum server requirements == {| class="wikitable" style="margin:auto" |- ! Component !! Requirement |- | OS || CentOS Stream 10 |- | RAM || 1 GB |- | CPU cores || 1 |- | Storage || 20 GB SSD |- | Architectures || amd64, arm64 |- | Number of PDS users || 1-20 |} Ensure we have a firewall installed along with fail2ban (see [[Guides:Fail2ban]]), and that proper security precautions are taken for our server, such as SSH hardening (see [[Guides:Best_SSH_Security_Practices]]). Other requirements: * Public IPv4 address * Public DNS name * Public inbound internet access permitted on port 80/tcp and 443/tcp * A reverse-proxy server, such as Caddy. This guide will use Caddy. Make sure our DNS name is resolvable to our public IPv4 address before proceeding, as it will make testing the PDS easier later on. We'll keep SELinux in enforcing mode and install a policy module to allow the PDS to work. == Preliminary actions == Install Caddy, Podman, and epel-release. <syntaxhighlight lang="bash"> sudo dnf install dnf-plugins-core sudo dnf copr enable @caddy/caddy sudo dnf install '@container-management' caddy epel-release </syntaxhighlight> === SELinux policy module === SELinux is not required, but it is recommended for RHEL-like distributions. To set SELinux in enforcing mode, run the following command with root privileges. <syntaxhighlight lang="bash"> setenforce 1 </syntaxhighlight> To make this persist across reboots, we may need to edit <code>/etc/sysconfig/selinux</code>. Change the <code>SELINUX</code> variable to the value <code>enforcing</code>. <syntaxhighlight lang="bash"> SELINUX=enforcing </syntaxhighlight> We'll also need to install an SELinux policy module so that SELinux doesn't deny the container processes used by the PDS. The following policy module will give the container runtime permissions for creating, locking, reading, writing, and setting attributes on files and directories used by containers, as well as give the containers permission to connect and write to Unix sockets. Create a file named <code>pds.te</code>. <syntaxhighlight> module pds 1.0; require { type container_runtime_t; type var_run_t; type container_t; type default_t; class file { create lock map open read setattr unlink write }; class dir { add_name remove_name write }; class unix_stream_socket connectto; class sock_file write; } # ============= container_t ============== allow container_t container_runtime_t:unix_stream_socket connectto; allow container_t default_t:dir { add_name remove_name write }; allow container_t default_t:file { create lock map open read setattr unlink write }; allow container_t var_run_t:sock_file write; </syntaxhighlight> Compile and install the module. <syntaxhighlight lang="bash"> checkmodule -M -m -o pds.mod pds.te semodule_package -o pds.pp -m pds.mod sudo semodule -i pds.pp </syntaxhighlight> If SELinux still denies some processes, we can check for them with the following command. <syntaxhighlight lang="bash"> sudo ausearch -m avc -ts recent | sudo audit2allow </syntaxhighlight> == Installing the PDS Podman quadlet == The systemd quadlet files are taken from the deploy-recipes repo[]. The only modification I have made is the <code>EnvironmentFile</code> setting. The directory under which we should place these files is <code>/etc/containers/systemd/</code> Create the file <code>/etc/containers/systemd/pds.container</code>. This file defines the main container for the PDS. <syntaxhighlight lang="ini"> [Unit] Description=Bluesky Personal Data Server service Before=caddy.service [Container] Label=app=pds Image=ghcr.io/bluesky-social/pds:0.4 AutoUpdate=registry Pod=pds.pod EnvironmentFile=/etc/pds.env [Install] WantedBy=multi-user.target default.target </syntaxhighlight> Next, create the file <code>/etc/containers/systemd/pds.pod</code>. This file defines the mappings for the PDS volume and published ports. <syntaxhighlight lang="ini"> [Pod] Volume=pds.volume:/pds PublishPort=127.0.0.1:3000:3000 # if you map 3000:3000 instead of 127.0.0.1:3000:3000 # the PDS will be accessible without the reverse proxy. # You probably don't want that! </syntaxhighlight> Finally, create the file <code>/etc/containers/systemd/pds.volume</code>. This file defines the OCI volume used to store the PDS data. <syntaxhighlight lang="ini"> [Unit] Description=Bluesky PDS Volume [Volume] Label=app=pds </syntaxhighlight> These files comprise a systemd quadlet. Quadlets enable Podman containers to run as systemd services. It's a declarative way to configure containers that fits in with the systemd ecosystem. More information on how to configure quadlets can be found at <ref>[https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html podman-systemd.unit], Podman, accessed 2026-05-27</ref>. It's necessary to have all of these files together in the same directory, as they depend on each other. == Setting up pds.env == Here is the default <code>pds.env</code>. We should edit it to our specific needs. <syntaxhighlight lang="bash"> PDS_HOSTNAME=pds.example.com PDS_JWT_SECRET= PDS_ADMIN_PASSWORD= PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX= PDS_DATA_DIRECTORY=/pds PDS_BLOBSTORE_DISK_LOCATION=/pds/blocks PDS_BLOB_UPLOAD_LIMIT=104857600 # if you want to user s3 or compatible, use these variables and comment out DISK_LOCATION PDS_BLOBSTORE_S3_BUCKET=your-bucket-name PDS_BLOBSTORE_S3_ENDPOINT=https://s3.example.com #PDS_BLOBSTORE_S3_FORCE_PATH_STYLE=true # depends on your s3 provider PDS_BLOBSTORE_S3_ACCESS_KEY_ID=your-access-key-id PDS_BLOBSTORE_S3_REGION=your-region PDS_BLOBSTORE_S3_SECRET_ACCESS_KEY=your-secret-key PDS_DID_PLC_URL=https://plc.directory PDS_BSKY_APP_VIEW_URL=https://api.bsky.app PDS_BSKY_APP_VIEW_DID=did:web:api.bsky.app PDS_REPORT_SERVICE_URL=https://mod.bsky.app PDS_REPORT_SERVICE_DID=did:plc:ar7c4by46qjdydhdevvrndac PDS_CRAWLERS=https://bsky.network LOG_ENABLED=true PDS_EMAIL_SMTP_URL= PDS_EMAIL_FROM_ADDRESS= </syntaxhighlight> We should set <code>PDS_JWT_SECRET</code> to a pseudo-random value generated with the following command. <syntaxhighlight lang="bash"> openssl rand --hex 16 </syntaxhighlight> Likewise for <code>PDS_ADMIN_PASSWORD</code> <syntaxhighlight lang="bash"> openssl rand --hex 16 </syntaxhighlight> We'll also need to set <code>PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX</code> to the value generated with the following command. <syntaxhighlight lang="bash"> openssl ecparam --name secp256k1 --genkey --noout --outform DER | tail --bytes=+8 | head --bytes=32 | xxd --plain --cols 32 </syntaxhighlight> As per the <code>EnvironmentFile</code> setting in <code>pds.container</code>, we should store <code>pds.env</code> at <code>/etc/pds.env</code>. == Starting the PDS == The following systemd command will load the files we placed under <code>/etc/containers/systemd/</code> and generate systemd unit files from them. <syntaxhighlight lang="bash"> sudo systemctl daemon-reload </syntaxhighlight> We should now be able to query <code>pds.service</code> by running <code>sudo systemctl status pds.service</code>. Note that it will show the unit as inactive until it is started. Now we can start the units. <syntaxhighlight lang="bash"> sudo systemctl start pds.service </syntaxhighlight> This should pull in the PDS container image from the registry and start it. We can check the status with <code>sudo systemctl status pds.service</code>. == Caddy configuration == A valid Caddy configuration should look like this: <syntaxhighlight> { email myemail@example.com on_demand_tls { ask http://localhost:3000/tls-check } } # PDS *.pds.example.com, pds.example.com { tls { on_demand } reverse_proxy http://localhost:3000 } # Anything else for your server </syntaxhighlight> == pdsadmin.sh == We can create <code>pdsadmin.sh</code> and put it somewhere in our system's binary <code>PATH</code>, such as <code>/usr/local/bin/pdsadmin.sh</code>. <syntaxhighlight lang="bash"> #!/usr/bin/env bash set -o errexit set -o nounset set -o pipefail PDSADMIN_BASE_URL="https://raw.githubusercontent.com/bluesky-social/pds/main/pdsadmin" export PDS_ENV_FILE="/etc/pds.env" # Command to run COMMAND="${1:-help}" shift || true # we don't actually need root here since it only is required # Download the script, if it exists SCRIPT_URL="${PDSADMIN_BASE_URL}/${COMMAND}.sh" SCRIPT_FILE="$(mktemp /tmp/pdsadmin.${COMMAND}.XXXXXX)" if [[ "${COMMAND}" == "update" ]]; then echo "ERROR: self-update not supported via podman" exit 1 fi if ! curl --fail --silent --show-error --location --output "${SCRIPT_FILE}" "${SCRIPT_URL}"; then echo "ERROR: ${COMMAND} not found" exit 2 fi chmod +x "${SCRIPT_FILE}" if "${SCRIPT_FILE}" "$@"; then rm -f "${SCRIPT_FILE}" fi </syntaxhighlight> Make the file executable. <syntaxhighlight lang="bash"> sudo chmod +x /usr/local/bin/pdsadmin.sh </syntaxhighlight> We can now run <code>pdsadmin.sh</code> with no arguments to see usage info. We'll of course need to create an account on our new PDS. == Verifying the PDS is online and accessible == Visit https://your-domain.net/xrpc/_health in the browser. Or run the following command in the terminal. Make sure to replace "your-domain.net" with your actual domain. <syntaxhighlight lang="bash"> curl https://your-domain.net/xrpc/_health </syntaxhighlight> We should receive a JSON response with a version, similar to this. <syntaxhighlight lang="json"> {"version":"0.4.204"} </syntaxhighlight> We'll also need to check that WebSockets are working. We can do this with the <code>wsdump</code> tool. We'll need the latest version of Golang to install it. <syntaxhighlight lang="bash"> sudo dnf install golang go install github.com/nrxr/wsdump@latest </syntaxhighlight> Check if WebSockets are working. <syntaxhighlight lang="bash"> wsdump "wss://your-domain.net/xrpc/com.atproto.sync.subscribeRepos?curosr=0" </syntaxhighlight> Note that there will be no events on the WebSocket until they are created in the PDS, so the above command may continue to run with no output. We'll need to press <code>CTRL-C</code> to stop it. == Closing == That's how to setup a Bluesky PDS on CentOS Stream 10. Additionally, this setup should also work on Almalinux 10, Rocky Linux 10, and Fedora 43, but I haven't tested it on any earlier versions of these distributions. I recommend reading the README.md<ref name="pds" /> for more information on using the <code>pdsadmin</code> command, setting up SMTP, and troubleshooting. == References == <references /> 3951d29295041892fc42138e54582573be33af9c 3000 1288 5539 2026-05-27T13:23:14Z Hyperreal 388 Init Guide:Using_Codeberg_Gitea_or_Forgejo_as_OIDC_provider_for_Tailscale wikitext text/x-wiki {{GuideWarning}} == Requirements == * An account on Codeberg, Gitea instance, or Forgejo instance. * A domain name. E.g., I use moonshadow.dev. * The primary email address on your Codeberg, Gitea, or Forgejo account must be from the above domain name. E.g., mine is hyperreal@moonshadow.dev. * A publicly accessible web server to host your webfinger file. You could also use Codeberg Pages<ref>[https://docs.codeberg.org/codeberg-pages/ Codeberg Pages], Codeberg Docs, accessed 2026-05-27</ref> for this with your custom domain<ref>[https://docs.codeberg.org/codeberg-pages/using-custom-domain/ custom domain], Codeberg Docs, accessed 2026-05-27</ref>. * The web server must serve content at your domain. E.g., https://moonshadow.dev. == Webfinger == In the web root of your web server, create the <code>.well-known/webfinger</code> file. For example, on mine, I have the following: <syntaxhighlight lang="json"> { "subject": "acct:hyperreal@moonshadow.dev", "links": [ { "rel": "http://openid.net/specs/connect/1.0/issuer", "href": "https://codeberg.org" } ] } </syntaxhighlight> You can use the Webfinger tool<ref>[https://webfinger.net/lookup/ Webfinger lookup tool], Webfinger, accessed 2026-05-27</ref> to make sure it is setup correctly. The value of the "subject" field must contain the email address at the domain you own. The value of the "href" field must be the URL of the Codeberg, Gitea instance, or Forgejo instance. == Create an OAuth2 application on Codeberg, Gitea, or Forgejo == On Codeberg, Gitea, or Forgejo, go to your User Settings -> Applications -> Manage OAuth2 applications. Enter the following information. * Application name: tailscale * Redirect URI: https://login.tailscale.com/a/oauth_response * Confidential client: checked Click on Create. Now copy and save the Client ID and Client secret that were generated. == Sign up with Tailscale == # Go to the Tailscale login page, and select "Sign up with OIDC". # Enter your email at your custom domain. E.g., hyperreal@moonshadow.dev. # Choose Codeberg or Gitea as the identity provider. This step is optional and doesn't really matter. Forgejo instances can choose Gitea. # Select "Get OIDC Issuer". # Enter the Client ID and Client secret you saved from your OAuth2 application. Leave everything else as default, and make sure that "consent" is checked under Prompts. # Click "Sign up with OIDC", and you should be able to login to Tailscale with your email address and be redirected to your Tailscale admin console. == See Also == * [https://tailscale.com/kb/1240/sso-custom-oidc Custom OIDC providers - Tailscale Docs] == References == <references /> 6fe6ad92ed7f10fd25ed75d283f1d27bc3d89f9a 0 1134 5540 5513 2026-05-27T14:04:05Z Speykious 405 Add logo caption, more programming languages, and minor tweaks to the writing wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxer-symbol-color.svg|150px]] | caption = The Fluxer logo | title = Fluxer | releasestatus = Maintained | lastrelease = 0.0.8 | languages = [[Electron]], [[TypeScript]], [[Rust]], [[Erlang]] | developers = Hampus Kraft and Contributors | website = https://fluxer.app | sourcecode = https://github.com/fluxerapp/fluxer }} Fluxer is a free, open-source instant messaging and VoIP platform designed as a privacy-focused alternative to Discord. ==Overview== Fluxer is available as a flatpak on FlatHub, as well as other official formats including AppImage, tar.gz, RPM, .deb, and more. Fluxer also allows for custom clients and has plans to incorporate federation and self-hosting capabilities in the future. ==Server Info== '''Vultr''' provides Fluxer's primary hosting. The main store for account data (messages, communities, profiles, and other persisted content) is in '''Piscataway, New Jersey''', and the object storage for user-uploaded files runs in the same region. Voice and real-time communication infrastructure also runs on Vultr across multiple regions worldwide, so calls can be routed near you for latency. '''Bunny.net''' operates Fluxer's content delivery network, with edge nodes worldwide, for user-generated content on the fluxerusercontent.com domain. In the future, Fluxer wants to offer the ability to partition your data entirely within the EU — for both your account and your communities. As stated in their FAQ, which you can find on https://fluxer.gg/fluxer-hq 399f1aa0ff070bd70d632f6090579600dd66e988 5541 5540 2026-05-27T14:05:02Z Speykious 405 Replace "privacy-focused" with "privacy-respecting" (Fluxer is not focused on privacy) wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxer-symbol-color.svg|150px]] | caption = The Fluxer logo | title = Fluxer | releasestatus = Maintained | lastrelease = 0.0.8 | languages = [[Electron]], [[TypeScript]], [[Rust]], [[Erlang]] | developers = Hampus Kraft and Contributors | website = https://fluxer.app | sourcecode = https://github.com/fluxerapp/fluxer }} Fluxer is a free, open-source instant messaging and VoIP platform designed as a privacy-respecting alternative to Discord. ==Overview== Fluxer is available as a flatpak on FlatHub, as well as other official formats including AppImage, tar.gz, RPM, .deb, and more. Fluxer also allows for custom clients and has plans to incorporate federation and self-hosting capabilities in the future. ==Server Info== '''Vultr''' provides Fluxer's primary hosting. The main store for account data (messages, communities, profiles, and other persisted content) is in '''Piscataway, New Jersey''', and the object storage for user-uploaded files runs in the same region. Voice and real-time communication infrastructure also runs on Vultr across multiple regions worldwide, so calls can be routed near you for latency. '''Bunny.net''' operates Fluxer's content delivery network, with edge nodes worldwide, for user-generated content on the fluxerusercontent.com domain. In the future, Fluxer wants to offer the ability to partition your data entirely within the EU — for both your account and your communities. As stated in their FAQ, which you can find on https://fluxer.gg/fluxer-hq 4bbf8d04ada7d4c2dc65183a6ced3cd2f3a4e8ba 5542 5541 2026-05-27T14:06:29Z Madonuko 140 fix spelling and add links wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxer-symbol-color.svg|150px]] | caption = The Fluxer logo | title = Fluxer | releasestatus = Maintained | lastrelease = 0.0.8 | languages = [[Electron]], [[TypeScript]], [[Rust]], [[Erlang]] | developers = Hampus Kraft and Contributors | website = https://fluxer.app | sourcecode = https://github.com/fluxerapp/fluxer }} Fluxer is a free, open-source instant messaging and VoIP platform designed as a privacy-respecting alternative to Discord. ==Overview== Fluxer is available as a [[flatpak]] on [[Flathub]], as well as other official formats including [[AppImage]], tar.gz, [[RPM]], .[[deb]], and more. Fluxer also allows for custom clients and has plans to incorporate federation and self-hosting capabilities in the future. ==Server Info== '''Vultr''' provides Fluxer's primary hosting. The main store for account data (messages, communities, profiles, and other persisted content) is in '''Piscataway, New Jersey''', and the object storage for user-uploaded files runs in the same region. Voice and real-time communication infrastructure also runs on Vultr across multiple regions worldwide, so calls can be routed near you for latency. '''Bunny.net''' operates Fluxer's content delivery network, with edge nodes worldwide, for user-generated content on the fluxerusercontent.com domain. In the future, Fluxer wants to offer the ability to partition your data entirely within the EU — for both your account and your communities. As stated in their FAQ, which you can find on https://fluxer.gg/fluxer-hq 79e24fb644fb44c815c22664024454eb72cd2909 5544 5542 2026-05-27T14:35:45Z Speykious 405 Add a Features section wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxer-symbol-color.svg|150px]] | caption = The Fluxer logo | title = Fluxer | releasestatus = Maintained | lastrelease = 0.0.8 | languages = [[Electron]], [[TypeScript]], [[Rust]], [[Erlang]] | developers = Hampus Kraft and Contributors | website = https://fluxer.app | sourcecode = https://github.com/fluxerapp/fluxer | license = AGPLv3 }} Fluxer is a free, open-source, cross-platform instant messaging and VoIP platform designed as a privacy-respecting alternative to Discord. ==Overview== Fluxer is available as a [[flatpak]] on [[Flathub]], as well as other official formats including [[AppImage]], tar.gz, [[RPM]], .[[deb]], and more. Fluxer also allows for custom clients and has plans to incorporate federation and self-hosting capabilities in the future. ==Features== Notable features of Fluxer include: * Communities, with organized channels, categories, roles and moderation tools. * Text channels. * Voice channels. * Screen sharing. * Custom emotes and stickers. * Media attachments like images, videos, audio or text. Note that attachments have an expiration date depending on their size. * Discord-compatible markdown, with some additional features like [https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts alerts]. * Message search, with ability to filter by users, channels, dates, and more. * A Progressive Web App for mobile. * A Discord-compatible bot and webhook API. ==Server Info== '''Vultr''' provides Fluxer's primary hosting. The main store for account data (messages, communities, profiles, and other persisted content) is in '''Piscataway, New Jersey''', and the object storage for user-uploaded files runs in the same region. Voice and real-time communication infrastructure also runs on Vultr across multiple regions worldwide, so calls can be routed near you for latency. '''Bunny.net''' operates Fluxer's content delivery network, with edge nodes worldwide, for user-generated content on the fluxerusercontent.com domain. In the future, Fluxer wants to offer the ability to partition your data entirely within the EU — for both your account and your communities. As stated in their FAQ, which you can find on https://fluxer.gg/fluxer-hq 46772cad893a21578f44576a40a8a96837b6d021 0 1247 5543 5420 2026-05-27T14:20:06Z Speykious 405 Minor spelling mistake wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[TypeScript]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/cinnyapp/cinny }} [[Category:Software]] [[File:Cinny-Unredacted.org.png|thumb|A photo of Cinny in the Unredacted Matrix server chat]] '''Cinny''' is a free and open source [[Matrix]] client focused on providing a simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, along with the browser<ref name=":0">{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. It currently uses the [https://github.com/matrix-org/matrix-js-sdk matrix-js-sdk] but is in the process on replacing it with a custom one, as such, it is not currently accepting contributions<ref>{{Cite|url=https://github.com/cinnyapp/cinny|title=Cinny GitHub repo|author=Cinny contributors|year=2026-05-23|accessdate=2026-05-25}}</ref>. {| class="wikitable" |+Supported features<ref name=":0" /> !Name !Supported? |- |E2EE |Yes |- |Spaces |Yes |- |Voice chat (1:1) |Yes<ref name=":1">{{Cite|url=https://github.com/matrix-org/matrix.org/issues/3418|title=Cinny supports MatrixRTC|author=spaetz|year=May 2026|accessdate=2026-05-25}}</ref> |- |Voice chat ([[Jitsi]]) |Yes<ref name=":1" /> |- |Threads |No |- |Legacy SSO |Yes |- |Multiple accounts |No |- |Multiple languages |No |} Note that [https://matrix.org/ecosystem/clients/cinny/ the page listing Cinny's features on Matrix.org] is outdated, as it now supports Voice chat<ref name=":1" />. cfb4dd447fa58df8465194bd8e444018e50df89e 6 1289 5545 2026-05-27T14:44:03Z Alxhr0 265 wikitext text/x-wiki PikaOS Logo d1f1e5f099daa541b92aae1fdf225325e1a2e97f 0 1290 5546 2026-05-27T14:47:02Z Alxhr0 265 Create the page WIP wikitext text/x-wiki {{DistributionInfobox | title = PikaOS | releasestatus = Maintained | releasemodel = Rolling | packagemanager = apt | defaultdesktops = [[GNOME]] [[KDE Plasma]] [[Niri]] [[COSMIC]] [[Hyprland]] | usagetype = General | architectures = x86_64 | website = https://wiki.pika-os.com/en/home | image = [[File:pika-logo-nv.png|PikaOS Logo]] }} [[Category:Linux Distributions]] '''PikaOS''' is a gaming/optimization-focused Linux distribution that emphasizes ease of use and high compatibility. Built on a Debian base but with cherry picked and custom compiled packages ensures that Pika is stable whilst being bang up to date! <ref>{{Cite|url=https://wiki.pika-os.com/en/home|title=About the distro|author=PikaOS Team|accessdate=05/27/26}}</ref> == What is PikaOS? == '''PikaOS''' is designed to provide: * '''Gaming Out of the Box''': Setup for pain-free Linux gaming from the start. * '''Excellent Performance''': Combines up-to-date drivers with a custom-tweaked kernel for speed. While also optimizing every package with O3, LTO and avx2 for extra speed! * '''High Compatibility''': Debian Sid base with custom patches ensures broad software and hardware support. <ref>{{Cite|url=https://wiki.pika-os.com/en/home#what-is-pikaos|title=What is PikaOS?|author=PikaOS Team|accessdate=05/27/26}}</ref> == Key Features == * 🐦 Cute bird mascot * 🎮 Gaming-focused setup * 🖥️ Included drivers for optimal hardware support * 🚀 Performance-tuned for speed * 🔗 High software and hardware compatibility * 🌐 Open-source development <ref>{{Cite|url=https://wiki.pika-os.com/en/home#key-features|title=Key features|author=PikaOS Team|accessdate=5/27/26}}</ref> == What makes PikaOS truly different? == '''PikaOS''' isn’t just another Linux distro — it’s built for speed, simplicity, and flexibility, with a growing set of custom tools that make system management easier for everyone — especially gamers and content creators. Critically, there is also a cute bird mascot 🐤. === Gaming-Ready and Performance-Tuned === '''PikaOS''' comes preconfigured for gaming on Linux, with all of the necessary tools - even the most obscure controller drivers - right out of the box. Under the hood, everything is tuned for speed: * Custom performance kernel * Compiler optimizations (O3, LTO, AVX2) * Up-to-date Mesa and Nvidia drivers that ''stay'' updated * Fully automated setup gets your system running in minutes * APX (an excellent podman frontend) available out of the box 457469a1a059f650930de9b908e29debe053349c 5547 5546 2026-05-27T15:25:23Z Alxhr0 265 Add image WIP wikitext text/x-wiki {{DistributionInfobox | title = PikaOS | releasestatus = Maintained | releasemodel = Rolling | packagemanager = [[apt]] | defaultdesktops = [[GNOME]] [[KDE Plasma]] [[Niri]] [[COSMIC]] [[Hyprland]] | usagetype = General | architectures = x86_64 | website = https://wiki.pika-os.com/en/home | image = <gallery> PikaOS.png|PikaOS Logo </gallery> }} [[Category:Linux Distributions]] '''PikaOS''' is a gaming/optimization-focused Linux distribution that emphasizes ease of use and high compatibility. Built on a Debian base but with cherry picked and custom compiled packages ensures that Pika is stable whilst being bang up to date! <ref>{{Cite|url=https://wiki.pika-os.com/en/home|title=About the distro|author=PikaOS Team|accessdate=05/27/26}}</ref> == What is PikaOS? == '''PikaOS''' is designed to provide: * '''Gaming Out of the Box''': Setup for pain-free Linux gaming from the start. * '''Excellent Performance''': Combines up-to-date drivers with a custom-tweaked kernel for speed. While also optimizing every package with O3, LTO and avx2 for extra speed! * '''High Compatibility''': Debian Sid base with custom patches ensures broad software and hardware support. <ref>{{Cite|url=https://wiki.pika-os.com/en/home#what-is-pikaos|title=What is PikaOS?|author=PikaOS Team|accessdate=05/27/26}}</ref> == Key Features == * 🐦 Cute bird mascot * 🎮 Gaming-focused setup * 🖥️ Included drivers for optimal hardware support * 🚀 Performance-tuned for speed * 🔗 High software and hardware compatibility * 🌐 Open-source development <ref>{{Cite|url=https://wiki.pika-os.com/en/home#key-features|title=Key features|author=PikaOS Team|accessdate=5/27/26}}</ref> == What makes PikaOS truly different? == '''PikaOS''' isn’t just another Linux distro — it’s built for speed, simplicity, and flexibility, with a growing set of custom tools that make system management easier for everyone — especially gamers and content creators. Critically, there is also a cute bird mascot 🐤. === Gaming-Ready and Performance-Tuned === '''PikaOS''' comes preconfigured for gaming on Linux, with all of the necessary tools - even the most obscure controller drivers - right out of the box. Under the hood, everything is tuned for speed: * Custom performance kernel * Compiler optimizations (O3, LTO, AVX2) * Up-to-date Mesa and Nvidia drivers that ''stay'' updated * Fully automated setup gets your system running in minutes * APX (an excellent podman frontend) available out of the box afa118809414d8b3ea304277389f337524186028 5548 5547 2026-05-27T15:32:29Z Alxhr0 265 Add last pieces of info for now wikitext text/x-wiki {{DistributionInfobox | title = PikaOS | releasestatus = Maintained | releasemodel = Rolling | packagemanager = [[apt]] | defaultdesktops = [[GNOME]] [[KDE Plasma]] [[Niri]] [[COSMIC]] [[Hyprland]] | usagetype = General | architectures = x86_64 | website = https://wiki.pika-os.com/en/home | image = <gallery> PikaOS.png|PikaOS Logo </gallery> }} [[Category:Linux Distributions]] '''PikaOS''' is a gaming/optimization-focused Linux distribution that emphasizes ease of use and high compatibility. Built on a Debian base but with cherry picked and custom compiled packages ensures that Pika is stable whilst being bang up to date! <ref>{{Cite|url=https://wiki.pika-os.com/en/home|title=About the distro|author=PikaOS Team|accessdate=05/27/26}}</ref> == What is PikaOS? <ref>{{Cite|url=https://wiki.pika-os.com/en/home#what-is-pikaos|title=What is PikaOS?|author=PikaOS Team|accessdate=05/27/26}}</ref> == '''PikaOS''' is designed to provide: * '''Gaming Out of the Box''': Setup for pain-free Linux gaming from the start. * '''Excellent Performance''': Combines up-to-date drivers with a custom-tweaked kernel for speed. While also optimizing every package with O3, LTO and avx2 for extra speed! * '''High Compatibility''': Debian Sid base with custom patches ensures broad software and hardware support. == Key Features <ref>{{Cite|url=https://wiki.pika-os.com/en/home#key-features|title=Key features|author=PikaOS Team|accessdate=5/27/26}}</ref> == * 🐦 Cute bird mascot * 🎮 Gaming-focused setup * 🖥️ Included drivers for optimal hardware support * 🚀 Performance-tuned for speed * 🔗 High software and hardware compatibility * 🌐 Open-source development == What makes PikaOS truly different? <ref>{{Cite|url=https://wiki.pika-os.com/en/why-pikaos#what-makes-pikaos-different|title=What makes PikaOS different|author=PikaOS Team|accessdate=5/27/26}}</ref> == '''PikaOS''' isn’t just another Linux distro — it’s built for speed, simplicity, and flexibility, with a growing set of custom tools that make system management easier for everyone — especially gamers and content creators. Critically, there is also a cute bird mascot 🐤. === Gaming-Ready and Performance-Tuned === '''PikaOS''' comes preconfigured for gaming on Linux, with all of the necessary tools - even the most obscure controller drivers - right out of the box. Under the hood, everything is tuned for speed: * Custom performance kernel * Compiler optimizations (O3, LTO, AVX2) * Up-to-date Mesa and Nvidia drivers that ''stay'' updated * Fully automated setup gets your system running in minutes * APX (an excellent podman frontend) available out of the box === Homegrown System Tools === '''PikaOS''' ships with a suite of custom-built GUI + CLI apps to make daily life easier: * '''Pika Welcome''' – Configure your desktop environment quickly and painlessly—no terminal needed (unless you want to). * '''Pikman Update Manager''' – A dual-mode (GUI + CLI) update manager for both APT and Flatpak. * '''Pika Kernel Manager''' – Easily view, install, or switch kernels. * '''Pika Device Manager''' – View hardware info and manage drivers (Mesa/Nvidia) with ease. 72b09b0c11c479f8380e3edaa775998acc98b1c5 10 799 5549 3510 2026-05-27T20:55:20Z Atmois 13 Fix cateogry wikitext text/x-wiki {{#invoke:mbox|mbox | icon = OOjs UI icon alert.svg | title = This page is a stub. {{AssistByEditing|action=expanding}} | text = This message means that this page has been deemed not long enough to provide meaningful coverage of its topic. | extraclasses = mbox-med notice-stub }}<includeonly>{{#ifeq:{{FULLPAGENAME}}|Category:Pages Needing Cleanup||[[Category:Stubs]]}}</includeonly><noinclude> <templatedata> { "params": {}, "description": "Adds a notice that the page may be too short with a call to action to expand it" } </templatedata> </noinclude> 1bf248e2d954fae99d6e93c4792d26152e3b2529 14 1291 5550 2026-05-27T20:55:57Z Atmois 13 Created page with "Incomplete pages that need development." wikitext text/x-wiki Incomplete pages that need development. f4f85836bf7971947d68248c3ec1ae8c0c5b1c76 0 8 5551 5349 2026-05-27T21:51:09Z MarkH 357 /* Terms */ fix two links pointing to the Linux Distributions article wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux Distributions|Linux Distribution]] ** [[Derivative]] * [[Linux kernel]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] ** [[Wayland]] ** [[X11]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] ** [[Cybersecurity]] ** [[DDoS]] ** [[ARPANET]] ** [[Ransomware]] ** [[Penetration testing|Penetration Testing]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[ZSH]] * [[TTY]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 7142544b7e64c14495f305f7dbd61518c0b3d494 5552 5551 2026-05-27T21:59:09Z MarkH 357 /* Advanced Terms */ fix zsh link wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. == Terms == * [[Bloat]] * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * [[Desktop Environment‏‎|Desktop Environment‏‎s]] ** [[GNOME]] ** [[KDE Plasma]] ** [[Xfce]] * [[Display Manager]] * [[Drivers]] * [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] * [[GUI|Graphical User Interface (GUI)]] * [[Linux Distributions|Linux Distribution]] ** [[Derivative]] * [[Linux kernel]] * [[Ownership]] * [[Package]] * [[Package Manager]] ** [[APK|apk]] ** [[APT|apt]] ** [[DNF|dnf]] ** [[DPKG|dpkg]] ** [[flatpak]] ** [[NixOS|nix]] ** [[pacman]] ** [[portage]] ** [[RPM|rpm]] ** [[snap]] ** [[zypper]] * [[Privacy]] * [[Program]] * [[Repository|Repository (Repo)]] * [[RTFM]] * [[Script]] * [[Security]] * [[Tar.xz|tar.xz / Tarball]] * [[TUI|Text-Based User Interface (TUI)]] * [[Ricing|Theming / "Ricing"]] * [[Window Manager|Window Managers]] ** [[DWM]] ** [[Hyprland]] ** [[IceWM]] ** [[i3]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] ** [[Wayland]] ** [[X11]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] ** [[Cybersecurity]] ** [[DDoS]] ** [[ARPANET]] ** [[Ransomware]] ** [[Penetration testing|Penetration Testing]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[Zsh]] * [[TTY]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 08c987b8a488b2d7ceec076c0267dd52130011cb 4 340 5553 4622 2026-05-27T22:30:10Z Atmois 13 Add people policy wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; FOSS Wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[FW:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[FW:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date''' and should strive to '''follow the guidelines below'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. If possible, you should '''cite your sources''' following the [[Guidelines#Citations|Citations Guidelines]] but please do not be discouraged from editing due to a lack of sources, any content is welcome and it can be improved upon as time goes on! ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] If you refer to or copy content (which is under a compatible license) it should be cited; this ensures the original author is credited for their work where relevant. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. We do not require claims and statements to be cited but if it can be challenged, it is always helpful to add a citation. If a claim is being challenged or you are unable to find a source, that's fine, just add the {{Citation needed}} template using <code><nowiki>{{Citation_needed}}</nowiki></code> or using the template inserter and another editor can help you find one or fill it out. Sources should be independent, ideally published and have a reputation for accuracy. '''Proper sourcing is ''always'' dependent on context'''; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Whilst secondary sources are more suitable, a reliable primary source such as a project's documentation or tertiary sources such as other wiki's are welcome but please ensure you do some due diligence to ensure it is up to date and accurate. If a page is in dire need of citations it can be tagged with the [[FW:Guidelines#Citations 2|relevant header template]], which you can read more about below. This should only be used on a page with controversial claims or is utilising content which has not been properly cited or attributed. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[FW:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[FW:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[FW:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[FW:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations where it would be appropriate, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. Before adding this template please consider if the page actually substantially requires citations as per the [[FW:Guidelines#Citations|Citation Policy]] or if there is just a handful of statements that need citations. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page. == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[FW:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[FW:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>FW:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://foss.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[FW:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''FOSS Wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == People == FOSS Wiki does not permit articles documenting people, alive or dead, in any context. We do not have the ability to moderate the oversight of a policy on [[FW:Guidelines#wp:Wikipedia:Biographies of living persons|Biographies of Living People]]. If you must link to a living person, use an interwiki link to their Wikipedia page, for example for [[FW:Guidelines#wp:Linux Torvalds|Linus Torvalds]] you can do it with <code>#wp:Linus_Torvalds</code>. If the person does not have a Wikipedia article, then they are not deemed notable enough to be linked and you '''should not''' link to an article on the person or to a profile of that person unless it serves as a citation. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 6413f7d1c7222a4fd11aeb6b0625ae51fe90156d 5554 5553 2026-05-27T22:34:42Z Atmois 13 Fix links wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; FOSS Wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[FW:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[FW:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date''' and should strive to '''follow the guidelines below'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. If possible, you should '''cite your sources''' following the [[Guidelines#Citations|Citations Guidelines]] but please do not be discouraged from editing due to a lack of sources, any content is welcome and it can be improved upon as time goes on! ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] If you refer to or copy content (which is under a compatible license) it should be cited; this ensures the original author is credited for their work where relevant. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. We do not require claims and statements to be cited but if it can be challenged, it is always helpful to add a citation. If a claim is being challenged or you are unable to find a source, that's fine, just add the {{Citation needed}} template using <code><nowiki>{{Citation_needed}}</nowiki></code> or using the template inserter and another editor can help you find one or fill it out. Sources should be independent, ideally published and have a reputation for accuracy. '''Proper sourcing is ''always'' dependent on context'''; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Whilst secondary sources are more suitable, a reliable primary source such as a project's documentation or tertiary sources such as other wiki's are welcome but please ensure you do some due diligence to ensure it is up to date and accurate. If a page is in dire need of citations it can be tagged with the [[FW:Guidelines#Citations 2|relevant header template]], which you can read more about below. This should only be used on a page with controversial claims or is utilising content which has not been properly cited or attributed. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[FW:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[FW:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[FW:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[FW:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations where it would be appropriate, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. Before adding this template please consider if the page actually substantially requires citations as per the [[FW:Guidelines#Citations|Citation Policy]] or if there is just a handful of statements that need citations. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page. == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[FW:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[FW:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>FW:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://foss.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[FW:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''FOSS Wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == People == FOSS Wiki does not permit articles documenting people, alive or dead, in any context. We do not have the ability to moderate the oversight of a policy on [[w:Wikipedia:Biographies of living persons|Biographies of Living People]]. If you must link to a living person, use an interwiki link to their Wikipedia page, for example for [[w:Linus_Torvalds|Linus Torvalds]] you can do it with <code>w:Linus_Torvalds</code>. If the person does not have a Wikipedia article, then they are not deemed notable enough to be linked and you '''should not''' link to an article on the person or to a profile of that person unless it serves as a citation. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 69df0bceffd8edf6d0710e8ce0bae0f53edef572 5555 5554 2026-05-27T22:35:27Z Atmois 13 Fix link wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; FOSS Wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[FW:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[FW:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date''' and should strive to '''follow the guidelines below'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. If possible, you should '''cite your sources''' following the [[Guidelines#Citations|Citations Guidelines]] but please do not be discouraged from editing due to a lack of sources, any content is welcome and it can be improved upon as time goes on! ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] If you refer to or copy content (which is under a compatible license) it should be cited; this ensures the original author is credited for their work where relevant. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. We do not require claims and statements to be cited but if it can be challenged, it is always helpful to add a citation. If a claim is being challenged or you are unable to find a source, that's fine, just add the {{Citation needed}} template using <code><nowiki>{{Citation_needed}}</nowiki></code> or using the template inserter and another editor can help you find one or fill it out. Sources should be independent, ideally published and have a reputation for accuracy. '''Proper sourcing is ''always'' dependent on context'''; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Whilst secondary sources are more suitable, a reliable primary source such as a project's documentation or tertiary sources such as other wiki's are welcome but please ensure you do some due diligence to ensure it is up to date and accurate. If a page is in dire need of citations it can be tagged with the [[FW:Guidelines#Citations 2|relevant header template]], which you can read more about below. This should only be used on a page with controversial claims or is utilising content which has not been properly cited or attributed. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[FW:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[FW:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[FW:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[FW:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations where it would be appropriate, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. Before adding this template please consider if the page actually substantially requires citations as per the [[FW:Guidelines#Citations|Citation Policy]] or if there is just a handful of statements that need citations. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page. == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[FW:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[FW:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>FW:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://foss.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[FW:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''FOSS Wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == People == FOSS Wiki does not permit articles documenting people, alive or dead, in any context. We do not have the ability to moderate the oversight of a policy on [[Wikipedia:Wikipedia:Biographies of living persons|Biographies of Living People]]. If you must link to a living person, use an interwiki link to their Wikipedia page, for example for [[w:Linus_Torvalds|Linus Torvalds]] you can do it with <code>Wikipedia:Linus_Torvalds</code>. If the person does not have a Wikipedia article, then they are not deemed notable enough to be linked and you '''should not''' link to an article on the person or to a profile of that person unless it serves as a citation. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] 6e3ec7c692760cbb759b2d58587c5b627f610072 5556 5555 2026-05-27T22:35:49Z Atmois 13 Fix link (actually) wikitext text/x-wiki The guidelines serve as a manual of style and a reference on the best way to write articles with your fellow editors. By following the guidelines, editors can provide an accurate, impartial, consistent and accessible source of information for users. By following the guidelines you help other editors focus on writing new content. '''''Never''''' '''be afraid to contribute!''' Making edits in good faith regardless of the level of quality is nothing to worry about, other editors can help you improve your contributions to meet the guidelines; FOSS Wiki is a collaborative effort between all editors! These guidelines are in constant development, if something is unclear from the guidelines [[FW:Contact|contact an admin]] or fallback to [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]]. <blockquote>To contribute or propose changes to the guidelines, refer to the [[FW:Guidelines#Protected Pages|protected page guidelines]].</blockquote> == Key Values == ===== <u>Accuracy</u> ===== Ensure information is '''accurate and up to date''' and should strive to '''follow the guidelines below'''; this can be done by ensuring you are using the official sources or other high-quality and reputable sources for information. If possible, you should '''cite your sources''' following the [[Guidelines#Citations|Citations Guidelines]] but please do not be discouraged from editing due to a lack of sources, any content is welcome and it can be improved upon as time goes on! ===== '''<u>Courtesy</u>''' ===== Before making significant changes to existing pages, '''consult with the active editors or an admin''' to ensure alignment with others' efforts. If disagreements arise, strive to resolve them constructively and positively. Avoid personal attacks, edit wars, or using the wiki as a platform to make a point. If needed, '''reach out to an admin for help in resolving conflicts'''. Be welcoming to new members, helping them to get started and teaching them the ropes. '''Always act in good faith''' while '''assuming the same of others.''' ===== <u>Impartiality</u> ===== Pages should be unbiased; if there has been a controversy on a specific topic, '''avoid it.''' Advocacy should be avoided as we strive to keep an impartial tone to explain the points of view fairly. If a topic only has one point of view, then please seek consensus from other editors to ensure that a biased view does not propagate on the wiki. '''There is no "best view".''' In all arguments, both sides have their merits, so highlight those rather than bringing down the other side with its flaws. Editors' personal experiences, interpretations, or opinions '''do not belong here.''' ===== <u>Accessibility</u> ===== We aim to make the wiki '''accessible to all users regardless of ability levels,''' be them brand new to the Linux and FOSS communities or seasoned veteran users. Always make sure to explain in detail what something is or does, or how it can be used. For guides, explain every step with why you are doing it and what each command or instruction does so that any user can understand what they are doing. Do not assume the reader will know everything you may know, and make sure they can easily follow along or learn from anything you write. == Citations == [[File:Webcomic xkcd - Wikipedian protester.png|alt=Wikipedian Protester|thumb|[citation needed]]] If you refer to or copy content (which is under a compatible license) it should be cited; this ensures the original author is credited for their work where relevant. The easiest way to add Citations to a page is to use the auto generated citation system! You can use it by pressing "Cite" on the toolbar of the visual editor, select Citation Template and fill out the relevant information! If you use the source editor you can see the Template Data and examples on the [[Template:Cite]] page. A citation is composed of two components: an inline superscript next to the relevant section of text,<ref>Sample Reference</ref> you can insert this by using the "Cite" button on the visual editor and adding it after relevant content or the <code><nowiki><ref> </ref></nowiki></code> tags. The second component is the references list at the bottom of a page; this is auto-generated once the page is saved. For the inline citation, there is no specific style required as long as you state the author, year of publication, the date of retrieval, and, if possible, a link to the original source. We do not mandate any specific referencing style, a sample has been provided below: <code><Title (Hyperlinked if possible)>, <Author>, <Year of Publication> (<Retrieval Date>). </code> e.g: <code> <nowiki>[https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf Linux Filesystem Hierarchy]</nowiki>, Linux Foundation, 2015 (Accessed: November 27, 2024). </code> Although nearly any consistent style may be used, ''avoid'' all-numeric date formats other than YYYY-MM-DD, because of the ambiguity concerning which number is the month and which the day. Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change. Always avoid switching between citation styles and maintain consistency. We do not require claims and statements to be cited but if it can be challenged, it is always helpful to add a citation. If a claim is being challenged or you are unable to find a source, that's fine, just add the {{Citation needed}} template using <code><nowiki>{{Citation_needed}}</nowiki></code> or using the template inserter and another editor can help you find one or fill it out. Sources should be independent, ideally published and have a reputation for accuracy. '''Proper sourcing is ''always'' dependent on context'''; common sense and editorial judgement are an indispensable part of the process. In general, newer sources are better; however, if an older source is considered more reliable, it should be used over the newer one. Whilst secondary sources are more suitable, a reliable primary source such as a project's documentation or tertiary sources such as other wiki's are welcome but please ensure you do some due diligence to ensure it is up to date and accurate. If a page is in dire need of citations it can be tagged with the [[FW:Guidelines#Citations 2|relevant header template]], which you can read more about below. This should only be used on a page with controversial claims or is utilising content which has not been properly cited or attributed. == Edit Summary == When editing a page you are prompted to provide a summary of the edits you have made, the purpose of the summaries is to provide other editors a brief explanation of the changes. The summary should clearly and accurately convey the changes made and if necessary an explanation for why you made the edits made particularly if you are reverting a change of another editor or doing a large overhaul to an article. Avoid abbreviations and keep the summary to what its meant to be, a summary. It should be two sentences at most, one explaining what was changed and one why it was changed. Longer discussions or debates belong in the talk pages not in summaries. Avoid being vague or writing misleading summaries such as <code>"made a change"</code> or mention one change but not another. Once an edit summary is made it cannot be revoked. Ensure when you write the summary you will not regret it afterwards. In the rare case of harmful content you may request an admin to remove the edit summary from public view via revision deletions however this is only done in exceptional circumstances. == Notability Standards == When creating a new page for the wiki it must meet several criteria, these are to maintain both relevance and ensure a page has enough content and sources to meet the wiki guidelines. The following requirements should be met before a new page is created: ; Sufficient Sourcing : You should ensure that the topic the article is on has sufficient sourcing as per the [[FW:Guidelines#Citations|citations guidelines]], in general you should aim that every claim can be cited. Sources should generally be secondary sources unless referring to documentation and should be from trusted and respected sources. ; Relevant Topic : The topic of the article should be relevant to the wiki. This includes but is not limited to: Operating systems and its software, development tools and languages, general software and system management practises. In general if the topic is related to technology it is welcome. : Please note we don't aim to have extensive documentation of every feature or function of a piece of software or system, however it is reasonable to list command syntax on a sub-page (Such as [[Sed/Syntax]]). Please also ensure exhaustive examples are also on a sub-page (Such as [[Sed/Examples]]). ; Pages Correctly Located and Categorised : Pages that align with the [[Guides:Contributing|guides policy]] (When a set of instructions are given to achieve a goal on the users systems it must be created as a guide), must be created as a guide and the contrary that non-guide articles must be in the main namespace. This also applies to categories, please ensure you correctly categorise the page as per the [[FW:Guidelines#Categories|categories guidelines]]. ; Pages meet the Guidelines and Code of Conduct : Ensure the new page meets the wiki's [[FW:Code of Conduct|Code of Conduct]] and all of its guidelines, particularly ensure it has the necessary information and features such as infoboxes or templates as defined in the [[FW:Guidelines#Formatting| formatting guidelines]]. == Templates == ====== Cleanup ====== {{Cleanup|Example}} If a page does not meet the standards of the wiki, you can use the <code>{{tlx|Cleanup|Reason}}</code>template to notify other editors of a reason why the page does not meet the guidelines and standards of the wiki and what can be improved upon. Only use this template if no other templates are suitable for the page. It will add said page to [[:Category:Pages Needing Cleanup]]. ====== Citations ====== {{Needs Citations}} If a page has little to no citations where it would be appropriate, you can use the <code>{{tlx|Needs Citations}}</code> template to notify other editors that it needs to be updated to add more citations. For specific statements that need citations, you can use <code>{{tlx|Citation needed}}</code> to generate {{Citation needed}}. Both templates will add said page to [[:Category:Needs Citations]]. Before adding this template please consider if the page actually substantially requires citations as per the [[FW:Guidelines#Citations|Citation Policy]] or if there is just a handful of statements that need citations. ====== Guides Warning ====== {{Guide Warning}} If a page or a section of the page contains instructions or commands of any form, this template is required to be placed above it, this is to inform users to be cautious of potentially malicious content that could be edited in. You can add the template using <code>{{tlx|Guide_Warning}}</code>, please also review the [[Guides:Contributing|Guides Policy]] incase your content belongs on its own guide page. == Guides Policy == You can see the full guidelines on the [[Guides:Contributing|Guides Policy]], this is a summary of the policy. Guides are ''anything that explain to a user how to do something beyond a link to another source or a brief instruction''. The following extra policies apply to guides: The [[Template:Guide Warning|<code><nowiki>{{Guide Warning}}</nowiki></code>]] template is required on the page. Please also ensure all commands are accurate and do not attempt to mislead users with the information on guides. == Linking & Redirects == You should ensure that if possible you have linked to other pages [[About|as such]] using <code><nowiki>[[Page_Title|markup text]]</nowiki></code>, you can also use the link button on the toolbar when using the visual editor. The first occurrence of the title should be linked, infoboxes should always be considered the first occurrence if a page has one. You may add links to pages which do not exist already but do not overdo it and ensure the link is to a page which is suitable and meets the [[FW:Guidelines#Page Creation|page creation]] standards before linking it. In some cases you may be linking to a page as a reference for something multiple times, such as linking to guidelines or a use of a template, in these cases it is acceptable to not follow the first occurrence rule and link it as appropriately needed. Redirects should be used for only two reasons: # Where a topic has an alternate title, such as [[KDE Plasma]] and [[Plasma]]. # Where a title may have capitalisation or grammar variants, such as [[Multi-Booting]] and [[Multi Booting]]. In general redirects are fine as long as they are reasonable, if in doubt consult an [[FW:Contact|admin]]. == Categories == Categorise pages when needed; you can do this by selecting the hamburger menu and then the categories button. Avoid making new categories unless it's required. == Formatting == ====== Language ====== All content should be in English unless there is a specific reason for why it shouldn't be. The version of English does not matter as long as pages are consistent; e.g., if the American English spelling of "color" is used, the British English spelling of "colour" should not be used within the same page. The only case where a specific spelling is required is when the name of a company or piece of software uses a specific spelling; e.g., "Grub Customizer" uses the American spelling. A comparison chart of the spelling can be found [[wikipedia:Wikipedia:Manual_of_Style/Spelling#English_spelling_comparison_chart|here]]. ====== Dates ====== Exact dates should always be given wherever possible. For all-numerical dates, they must always follow the ISO 8601 (<code>YYYY-MM-DD</code>) standard. For non-numerical dates, the following is required: The day must not be zero-padded and must not use ordinals (<code>1st, 2nd, 3rd 4th</code>). The month must not be abbreviated and must be capitalised. The year must not be zero-padded, must not be abbreviated, and must not contain commas. Below are dates not acceptable on the wiki, the correction, and the issue with the invalid date. {| class="wikitable" !Invalid Date !Corrected Date !Issue |- |Mar. 1 |March 1 | rowspan="2" |Use of a a full stop following a date or month and using an abbreviated month name. |- |1'''.''' May | rowspan="4" |1 May, May 1 |- |1 may, may 1 |Months should be capitalized. |- |1st May, May 1st |Use of ordinals (1st, 2nd, 3rd, etc.) |- |01 May, May 01 |Zero-padding days |- |2025/05/01 | rowspan="4" |2025-05-01 |Use of other symbols than hyphen |- |20250501 |Ommitance of hyphen |- |25-05-01 |Abbrivation of year |- |05-01-2025, 01-05-2025, 2007-01-05 |Not using YYYY-MM-DD format |- |'25 |2025 |Abbreviation of year |- |Two thousand twenty-five |2025 | rowspan="2" |Writing year or day in words |- |the first of May, May the first |1 May or May 1 |- |May 0560 |May 560 |Zero-padding year |- |May 2''','''025 |May 2025 | |} ====== Images ====== Images should '''always''' have alternate text, this is essential for users who are reliant on screen readers or are not on internet capable of rendering images. You can do this by adding the <code>alt</code> attribute to an image, the description should explain what is in the image but should aim to be as short as possible. If an image contains text it '''must''' be added into the alt text of the image and if the alt text needs to be longer it should explain the premise of the image in the first sentence. For more guidance on how to write alternate text see the [[wikipedia:Wikipedia:Manual of Style/Accessibility/Alternative text for images#How to write alternative text|Wikipedia guide]]. You can add alt text as such: <code><nowiki>[[File:Tux.svg|alt=Tux, the Linux mascot: A black and white penguin with a yellow beak and feet sitting down.]]</nowiki></code>. ====== Commands ====== When referencing a command in the sense of a page on it (e.g: A page on sudo), it should '''not''' be formatted differently. However when listing a full command or example it should be in a code block, you can add one with the '''"Insert"''' button and select the '''"Code Block"''' option with the "'''Shell'''" option and then type your command. For code blocks avoid having comments inside them and place the comment as normal text '''above''' the codeblock, we also advise for shorter commands to use the inline code block with the keybind '''"Ctrl + Shift + 6"''' if the command is short and can flow with the content. '''''We are working on a template to help place commands easier, please be patient!''''' == Protected Pages == Pages in the <code>FW:</code>, <code>Mediawiki:</code>, <code>Template:</code>, <code>Modules:</code> namespaces and certain high traffic pages are protected for a variety of reasons, so users are unable to edit them, you can propose the changes following the steps below: <blockquote>You can choose to not make a sandbox and just explain the changes on the talk page (Step 3 onwards). The following instructions are more for large changes, for spelling or grammar fixes it is more suitable to just make a note on the talk page explaining the issue and the fix required. Either method is acceptable and it is up to the user to deem which method they prefer.</blockquote> '''1.''' Create a sandbox page under your user page, e.g: <code><nowiki>https://foss.wiki/User:Username/PageTitle</nowiki></code> and copy the source of the page you wish to propose changes to, using <code>[https://foss.wiki/PageTitle?action=edit https://foss.wiki/PageTitle?action=edit]</code> to view the source. '''2.''' You can edit the page to add in the changes you wish to propose, please ensure they follow the guidelines. You may want to consult an admin prior to major changes to ensure they will not be rejected and are in line with our goals. '''3.''' Using the page's talk page (Which can be accessed using the '''discussion''' button at the top of the page), outline what changes you wish to propose (Including the link to your sandbox, if appropriate) and why you think those changes should be implemented. '''4.''' An administrator will respond to the proposal with either feedback or confirmation of the implementation of the feedback. ''If there is no response after 7 days, you may [[FW:Contact|contact]] an administrator for feedback on your proposed changes.'' <blockquote>For admins: When implementing user feedback on protected pages, ensure any changes or proposed changes meet the guidelines and follow the goals of the wiki. You can then copy the edited sections source into the main page, please double check the diff's and formatting. When saving the edits ensure to in some form credit the contributing user such as <code>Written by: <nowiki>[[User:Username]]</nowiki></code>. </blockquote> == Artificial Intelligence Policy == Using Artificial Intelligence (AI) to generate content for the wiki is '''forbidden'''. This includes both written content or the use of AI generated images, AI generated images are only allowed when the use of them are relevant to an article and clearly disclosed as being AI generated. This applies to all content on '''all pages of the wiki.''' AI powered tools such as grammar checkers or use of AI for checking the accuracy of the English used '''is permitted''' without a need for disclosure. These tools assist editors in invaluable ways however there should '''always''' be human oversight on all assistance from AI to ensure any content assisted by the AI meets our guidelines. '''FOSS Wiki''' makes use of Cloudflare's anti-AI technologies to block AI scrapers due to them generally not respecting our wiki's license, [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0]. Training on the wiki's content is only permitted when the use of the data respects the license by both being under the same license (Sharealike) and properly attributed to its authors. To see how to properly attribute content see the [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#Attributing_text Creative Commons Guide] or the [[Wikipedia:Wikipedia:Copyrights#Reusers' rights and obligations|Wikipedia Guide]] on the topic. == People == FOSS Wiki does not permit articles documenting people, alive or dead, in any context. We do not have the ability to moderate the oversight of a policy on [[Wikipedia:Wikipedia:Biographies of living persons|Biographies of Living People]]. If you must link to a living person, use an interwiki link to their Wikipedia page, for example for [[Wikipedia:Linus Torvalds|Linus Torvalds]] you can do it with <code>Wikipedia:Linus_Torvalds</code>. If the person does not have a Wikipedia article, then they are not deemed notable enough to be linked and you '''should not''' link to an article on the person or to a profile of that person unless it serves as a citation. == Responsible Disclosure == Vulnerabilities in software much be treated with the utmost care on the wiki as it could be used by malicious actors to take advantage of vulnerable systems. Due to this we have a strict policy on when vulnerabilities can be addressed or made mention of in the wiki. ''Before a vulnrability can be mentioned on the wiki you must wait 7 days after '''both''':'' * The vulnerability has been publicly disclosed by the vendor, a CVE Numbering Authority, MITRE or any similar authority. * There is an official patch, mitigation or fix which has been released by the vendor. Mentioning or making any reference to a vulnerability until 7 days after both criteria are met will have the edit reverted and vanished. Any link to tools to or instructions on how to exploit any vulnerability will be treated in a similar manner. The only exception for this is generic tools for vulnerability exploitation (Such as Kali Linux) or after '''1 month''' of both criteria being met it is permitted to have brief overviews of the exploits. == References == <references /> ''This page has been adapted from [[wikipedia:Wikipedia:Manual_of_Style|Wikipedia's Manual of Style]] and the [https://wiki.gentoo.org/wiki/Gentoo_Wiki:Guidelines Gentoo Wiki Guidelines] for our own needs and refined to what is seen to be fit by the team. Nothing has been taken verbatim from them however some sections are developed off their stances and will be similar so great thanks goes to their contributors for creating a great starting point for us.'' [[Category:Meta]] cd32a7f45dc22dd57a08bb313c1f3f1a074dc2d5 0 1184 5557 5047 2026-05-27T22:56:26Z MarkH 357 clean up and add references wikitext text/x-wiki {{Stub}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Ffmpeg_logo.png|thumb]] | caption =The FFmpeg logo. | title = FFmpeg | releasestatus = Maintained | lastrelease = 8.1.1, 2026-05-04 | languages = [[C]], [[Assembly]] | developers = The FFmpeg Developers | website = [https://ffmpeg.org ffmpeg.org] | license = [[GNU General Public License#GNU_Lesser_General_Public_License_(LGPL)|LGPL-2.1-or-later]], with some optional components under other licenses | sourcecode = https://git.ffmpeg.org/ffmpeg.git }} '''FFmpeg''' is a set of free and open-source libraries and [[CLI]] applications used for converting, [[wikipedia:Transcoding|transcoding]], remuxing, and editing audio and video media in a broad range of formats.<ref>{{Cite|url=https://ffmpeg.org/about.html|title=About FFmpeg · ffmpeg.org|author=FFmpeg Developers|year=2011|accessdate=2026-05-23}}</ref> FFmpeg is widely used in open source projects, including [[Handbrake]]<ref>{{Cite|url=https://handbrake.fr/docs/en/1.10.0/technical/source-formats.html|title=HandBrake Documentation — Supported source formats|author=HandBrake Team|year=2025|accessdate=2026-05-27}}</ref> and [[Kdenlive]]<ref>{{Cite|url=https://kdenlive.org/features/|title=Features - Kdenlive|author=Kdenlive Team|year=2026|accessdate=2026-05-27}}</ref>, as well as in proprietary projects. It has also been used as part of streaming services such as YouTube.<ref>{{Cite|url=https://multimedia.cx/eggs/googles-youtube-uses-ffmpeg/|title=Google’s YouTube Uses FFmpeg|author=Multimedia Mike|year=2011|accessdate=2026-05-27}}</ref> == References == <references /> 984cbb53c51acb19f65792ab1ed72933bed7cf60 0 1292 5558 2026-05-28T02:28:01Z Xuruh 407 Created page with "[[Category:Software]] {{SoftwareInfobox | image = | caption = The Fluxerworld logo | title = Fluxerworld | releasestatus = Alpha | lastrelease = 1.0.86 | languages = [[TypeScript]], [[Erlang]], [[React Native]] | developers = Xuruh and Contributors | website = https://fluxer.world | sourcecode = https://github.com/fluxerworld/fluxerworld | license = AGPLv3 }} '''Fluxerworld''' is a free, open-source, cross-platform instant messaging and VoIP platform with end-to-end enc..." wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = | caption = The Fluxerworld logo | title = Fluxerworld | releasestatus = Alpha | lastrelease = 1.0.86 | languages = [[TypeScript]], [[Erlang]], [[React Native]] | developers = Xuruh and Contributors | website = https://fluxer.world | sourcecode = https://github.com/fluxerworld/fluxerworld | license = AGPLv3 }} '''Fluxerworld''' is a free, open-source, cross-platform instant messaging and VoIP platform with end-to-end encryption for direct messages and group conversations. It is a fork of [[Fluxer]], with divergent features focused on encryption, mobile support, and self-hostable infrastructure. ==Overview== Fluxerworld is available on Linux ([[AppImage]], tar.gz, [[RPM]], .[[deb]], [[flatpak|Flatpak]], AUR), Windows (NSIS installer), macOS (dmg), and Android (APK via [https://f-droid.org F-Droid] and direct download). An iOS build is in testing. A Progressive Web App is available at https://fluxer.world. ==Features== Notable features of Fluxerworld include: * End-to-end encryption for 1:1 direct messages and Group DMs using the [https://gitlab.matrix.org/matrix-org/olm Olm and Megolm] cryptographic ratchets (Matrix-compatible). * Native React Native mobile applications for Android with feature parity to the desktop client, including voice/video calls and screen sharing. * Communities, with organized channels, categories, roles and moderation tools. * Voice and video calls with screen sharing, backed by [https://livekit.io LiveKit]. * Custom emotes and stickers. * Media attachments like images, videos, audio or text. Note that attachments have an expiration date depending on their size. * Message search, with ability to filter by users, channels, dates, and more. * A bot and webhook API. ==History== Fluxerworld was forked from [[Fluxer]] to focus on end-to-end encryption and first-class mobile support. End-to-end encrypted direct messages shipped in May 2026, followed by Group DM encryption in late May 2026. ==Relationship to Fluxer== Fluxerworld shares its core server architecture with upstream [[Fluxer]] (Erlang/OTP gateway, TypeScript API), but diverges in client implementation, encryption layer, and packaging targets. Both projects are AGPLv3. ==See also== * [[Fluxer]] — upstream project ==External links== * [https://fluxer.world Official website] * [https://github.com/fluxerworld/fluxerworld Source code on GitHub] * [https://github.com/fluxerworld/fluxer-mobile Mobile app source] [[Category:Instant messaging]] [[Category:VoIP]] [[Category:Free software]] 75e690ccb6a64be0250ab8b9302a0585c7a2bc0d 5560 5558 2026-05-28T02:39:29Z Xuruh 407 creation wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxerlogo.png|150px]] | caption = The Fluxerworld logo | title = Fluxerworld | releasestatus = Beta | lastrelease = 1.0.86 | languages = TypeScript, Erlang, React Native | developers = Xuruh and Contributors | website = https://fluxer.world | sourcecode = https://github.com/fluxerworld/fluxerworld | license = AGPLv3 }} '''Fluxerworld''' is a free, open-source, cross-platform instant messaging and VoIP platform with end-to-end encryption for direct messages and group conversations. It is a fork of [[Fluxer]], with divergent features focused on encryption, mobile support, and self-hostable infrastructure. ==Overview== Fluxerworld is available on Linux (AppImage, tar.gz, [[RPM]], .deb, [[flatpak|Flatpak]], AUR), Windows (NSIS installer), macOS (dmg), Android (APK via [https://f-droid.org F-Droid] and direct download), and iOS. A Progressive Web App is available at https://fluxer.world. ==Features== Notable features of Fluxerworld include: * End-to-end encryption for 1:1 direct messages and Group DMs using the [https://gitlab.matrix.org/matrix-org/olm Olm and Megolm] cryptographic ratchets (Matrix-compatible). * Native React Native mobile applications for Android with feature parity to the desktop client, including voice/video calls and screen sharing. * Communities, with organized channels, categories, roles and moderation tools. * Voice and video calls with screen sharing, backed by [https://livekit.io LiveKit]. * Custom emotes and stickers. * Media attachments like images, videos, audio or text. Note that attachments have an expiration date depending on their size. * Message search, with ability to filter by users, channels, dates, and more. * A bot and webhook API. ==Downloads== Fluxerworld provides clients for multiple platforms, available via the Snap Store, AUR, Fedora Copr, F-Droid, GitHub Releases, and more. ===Install via terminal=== * '''Snap:''' <code>sudo snap install fluxer-world</code> * '''Arch (AUR):''' <code>yay -S fluxer-world-bin</code> * '''Fedora (Copr):''' <code>sudo dnf copr enable xuruh/fluxer-world && sudo dnf install fluxer-world</code> * '''F-Droid:''' add the repo <code>https://fluxer.world/fdroid/repo</code> in F-Droid settings ===Windows=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (x64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Portable (x64)] ===macOS=== * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Apple Silicon)] * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Intel)] ===Linux=== * [https://snapcraft.io/fluxer-world Snap Store] * [https://aur.archlinux.org/packages/fluxer-world-bin AUR] * [https://copr.fedorainfracloud.org/coprs/xuruh/fluxer-world/ Fedora Copr] * [https://github.com/fluxerworld/fluxerworld/releases/latest .deb (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest .rpm (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest AppImage (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest tar.gz (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Flatpak] ===Mobile=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Android APK] * [https://fluxer.world/fdroid/repo F-Droid] * [https://github.com/fluxerworld/fluxerworld/releases/latest iOS IPA] ==History== Fluxerworld was forked from [[Fluxer]] to focus on end-to-end encryption and first-class mobile support. End-to-end encrypted direct messages shipped in May 2026, followed by Group DM encryption in late May 2026. ==Relationship to Fluxer== Fluxerworld shares its core server architecture with upstream [[Fluxer]] (Erlang/OTP gateway, TypeScript API), but diverges in client implementation, encryption layer, and packaging targets. Both projects are AGPLv3. ==See also== * [[Fluxer]] — upstream project ==External links== * [https://fluxer.world Official website] * [https://github.com/fluxerworld/fluxerworld Source code on GitHub] * [https://github.com/fluxerworld/fluxerworld/releases Releases] [[Category:Instant messaging]] [[Category:VoIP]] [[Category:Free software]] 1e3309ba09bd8cea764d39197f7d2ee2ece9553c 5561 5560 2026-05-28T02:47:54Z Xuruh 407 wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxerlogo.png|150px]] | caption = The Fluxerworld logo | title = Fluxerworld | releasestatus = Beta | lastrelease = 1.0.86 | languages = TypeScript, Erlang, React Native | developers = Xuruh and Contributors | website = https://fluxer.world | sourcecode = https://github.com/fluxerworld/fluxerworld | license = AGPLv3 }} '''Fluxerworld''' is a free, open-source, cross-platform instant messaging and VoIP platform with end-to-end encryption for direct messages and group conversations. It is a fork of [[Fluxer]], with divergent features focused on encryption, mobile support, and self-hostable infrastructure. ==Overview== Fluxerworld is available on Linux (AppImage, tar.gz, [[RPM]], .deb, [[flatpak|Flatpak]], AUR), Windows (NSIS installer), macOS (dmg), Android (APK via [https://f-droid.org F-Droid] and direct download), and iOS. A Progressive Web App is available at https://fluxer.world. ==Privacy and encryption== Fluxerworld is designed to be privacy-conscious. Direct messages and group conversations are end-to-end encrypted using the Olm and Megolm cryptographic ratchets from the Matrix protocol. Because chats are end-to-end encrypted, administrators are not able to read their contents. Fluxerworld also does not monitor user logs. ==Features== Notable features of Fluxerworld include: * End-to-end encryption for 1:1 direct messages and Group DMs using the [https://gitlab.matrix.org/matrix-org/olm Olm and Megolm] cryptographic ratchets (Matrix-compatible). * Native React Native mobile applications for Android with feature parity to the desktop client, including voice/video calls and screen sharing. * Communities, with organized channels, categories, roles and moderation tools. * Voice and video calls with screen sharing, backed by [https://livekit.io LiveKit]. * Custom emotes and stickers. * Media attachments like images, videos, audio or text. Note that attachments have an expiration date depending on their size. * Message search, with ability to filter by users, channels, dates, and more. * A bot and webhook API. ==Downloads== Fluxerworld provides clients for multiple platforms, available via the Snap Store, AUR, Fedora Copr, F-Droid, GitHub Releases, and more. ===Install via terminal=== * '''Snap:''' <code>sudo snap install fluxer-world</code> * '''Arch (AUR):''' <code>yay -S fluxer-world-bin</code> * '''Fedora (Copr):''' <code>sudo dnf copr enable xuruh/fluxer-world && sudo dnf install fluxer-world</code> * '''F-Droid:''' add the repo <code>https://fluxer.world/fdroid/repo</code> in F-Droid settings ===Windows=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (x64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Portable (x64)] ===macOS=== * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Apple Silicon)] * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Intel)] ===Linux=== * [https://snapcraft.io/fluxer-world Snap Store] * [https://aur.archlinux.org/packages/fluxer-world-bin AUR] * [https://copr.fedorainfracloud.org/coprs/xuruh/fluxer-world/ Fedora Copr] * [https://github.com/fluxerworld/fluxerworld/releases/latest .deb (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest .rpm (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest AppImage (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest tar.gz (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Flatpak] ===Mobile=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Android APK] * [https://fluxer.world/fdroid/repo F-Droid] * [https://github.com/fluxerworld/fluxerworld/releases/latest iOS IPA] ==History== Fluxerworld was forked from [[Fluxer]] to focus on end-to-end encryption and first-class mobile support. End-to-end encrypted direct messages shipped in May 2026, followed by Group DM encryption in late May 2026. ==Relationship to Fluxer== Fluxerworld shares its core server architecture with upstream [[Fluxer]] (Erlang/OTP gateway, TypeScript API), but diverges in client implementation, encryption layer, and packaging targets. Both projects are AGPLv3. ==See also== * [[Fluxer]] — upstream project ==External links== * [https://fluxer.world Official website] * [https://github.com/fluxerworld/fluxerworld Source code on GitHub] * [https://github.com/fluxerworld/fluxerworld/releases Releases] [[Category:Instant messaging]] [[Category:VoIP]] [[Category:Free software]] c393e6f73d03ec07feff2424f2e859ba23022897 5563 5561 2026-05-28T08:20:50Z Int 401 Fluxerworld -> Fluxer World wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxerlogo.png|150px]] | caption = The Fluxer World logo | title = Fluxer World | releasestatus = Beta | lastrelease = 1.0.86 | languages = TypeScript, Erlang, React Native | developers = Xuruh and Contributors | website = https://fluxer.world | sourcecode = https://github.com/fluxerworld/fluxerworld | license = AGPLv3 }} '''Fluxer World''' is a free, open-source, and cross-platform instant messaging and VoIP platform with end-to-end encryption for direct messages and group conversations. It is a fork of [[Fluxer]], with divergent features focused on encryption, mobile support, and self-hostable infrastructure. ==Overview== Fluxer World is available on Linux (AppImage, tar.gz, [[RPM]], .deb, [[flatpak|Flatpak]], AUR), Windows (NSIS installer), macOS (dmg), Android (APK via [https://f-droid.org F-Droid] and direct download), and iOS. A Progressive Web App is available at https://fluxer.world. ==Privacy and encryption== Fluxer World is designed to be privacy-conscious. Direct messages and group conversations are end-to-end encrypted using the Olm and Megolm cryptographic ratchets from the Matrix protocol. Because chats are end-to-end encrypted, administrators are not able to read their contents. Fluxerworld also does not monitor user logs. ==Features== Notable features of Fluxer World include: * End-to-end encryption for 1:1 direct messages and Group DMs using the [https://gitlab.matrix.org/matrix-org/olm Olm and Megolm] cryptographic ratchets (Matrix-compatible). * Native React Native mobile applications for Android with feature parity to the desktop client, including voice/video calls and screen sharing. * Communities, with organized channels, categories, roles and moderation tools. * Voice and video calls with screen sharing, backed by [https://livekit.io LiveKit]. * Custom emotes and stickers. * Media attachments like images, videos, audio or text. Note that attachments have an expiration date depending on their size. * Message search, with ability to filter by users, channels, dates, and more. * A bot and webhook API. ==Downloads== Fluxer World provides clients for multiple platforms, available via the Snap Store, AUR, Fedora Copr, F-Droid, GitHub Releases, and more. ===Install via terminal=== * '''Snap:''' <code>sudo snap install fluxer-world</code> * '''Arch (AUR):''' <code>yay -S fluxer-world-bin</code> * '''Fedora (Copr):''' <code>sudo dnf copr enable xuruh/fluxer-world && sudo dnf install fluxer-world</code> * '''F-Droid:''' add the repo <code>https://fluxer.world/fdroid/repo</code> in F-Droid settings ===Windows=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (x64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Portable (x64)] ===macOS=== * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Apple Silicon)] * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Intel)] ===Linux=== * [https://snapcraft.io/fluxer-world Snap Store] * [https://aur.archlinux.org/packages/fluxer-world-bin AUR] * [https://copr.fedorainfracloud.org/coprs/xuruh/fluxer-world/ Fedora Copr] * [https://github.com/fluxerworld/fluxerworld/releases/latest .deb (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest .rpm (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest AppImage (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest tar.gz (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Flatpak] ===Mobile=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Android APK] * [https://fluxer.world/fdroid/repo F-Droid] * [https://github.com/fluxerworld/fluxerworld/releases/latest iOS IPA] ==History== Fluxer World was forked from [[Fluxer]] to focus on end-to-end encryption and first-class mobile support. End-to-end encrypted direct messages shipped in May 2026, followed by Group DM encryption in late May 2026. ==Relationship to Fluxer== Fluxer World shares its core server architecture with upstream [[Fluxer]] (Erlang/OTP gateway, TypeScript API), but diverges in client implementation, encryption layer, and packaging targets. Both projects are AGPLv3. ==See also== * [[Fluxer]] — upstream project ==External links== * [https://fluxer.world Official website] * [https://github.com/fluxerworld/fluxerworld Source code on GitHub] * [https://github.com/fluxerworld/fluxerworld/releases Releases] [[Category:Instant messaging]] [[Category:VoIP]] [[Category:Free software]] df895a581cfcb286334b2d33406da6d9a25d3dab 6 1293 5559 2026-05-28T02:30:58Z Xuruh 407 wikitext text/x-wiki == Licensing == {{GPL}} 6b26f5cce63faf4ce1130ffc4f5c42cf3e3a00ac 3000 1294 5562 2026-05-28T03:04:37Z Hyperreal 388 Init Guide:Create_an_RPM_repository wikitext text/x-wiki {{GuideWarning}} This guide assumes the following are setup already: * DNS pointing to your public web server. * RHEL-compatible distribution is installed to host the RPM repository. * Basic security precautions like Firewall and SSH hardening are in place. * We'll pretend the user is <code>tux</code> and that they have sudo / admin privileges on the host system. * The RPM repository will be stored under <code>/home/tux/rpm-repos</code>. == Install dependencies == <syntaxhighlight lang="bash"> sudo dnf install gnupg createrepo dnf-utils rpm-sign wget </syntaxhighlight> == Setup GnuPG == Replace the values below with your own. <syntaxhighlight lang="bash"> echo "%echo Generating a PGP key Key-Type: RSA Key-Length: 4096 Name-Real: Tux Name-Email: tux@example.com Expire-Date: 0 %no-ask-passphrase %no-protection %commit" > ~/tux-pgp-key.batch </syntaxhighlight> Now generate the key with the following command: <syntaxhighlight lang="bash"> gpg --no-tty --batch --gen-key ~/tux-pgp-key.batch </syntaxhighlight> Export the public key. <syntaxhighlight lang="bash"> gpg --armor --export "Tux" > ~/tux-pgp-key.pub </syntaxhighlight> Export the private key to back it up somewhere safe. <syntaxhighlight lang="bash"> gpg --armor --export-secret-keys "Tux" > ~/tux-pgp-key.sec </syntaxhighlight> After backing up the private key, shred it from the working directory. <syntaxhighlight lang="bash"> shred -xu ~/tux-pgp-key.sec </syntaxhighlight> == Setup RPM signing == Replace <code>E1933532750E9EEF</code> with your key's ID. <syntaxhighlight lang="bash"> echo "%_signature gpg %_gpg_name E1933532750E9EEF" > ~/.rpmmacros </syntaxhighlight> Create a directory to serve the repository. <syntaxhighlight lang="bash"> mkdir -p ~/rpm-repos/packages </syntaxhighlight> Move RPM packages into the <code>~/rpm-repos/packages/</code> directory. Then sign them with the following command. <syntaxhighlight lang="bash"> rpm --addsign ~/rpm-repos/packages/*.rpm </syntaxhighlight> == Create repo index == Once all the packages are signed, create the repository with the following command. This command will create a directory in the repo named <code>repodata</code> containing a file named <code>repomd.xml</code>. <syntaxhighlight lang="bash"> createrepo ~/rpm-repos/packages/ </syntaxhighlight> <blockquote> Note that the <code>createrepo</code> command must be run against each directory in the repo that contains .rpm files. </blockquote> Now sign the repo metadata with the following command. <syntaxhighlight lang="bash"> gpg --detach-sign --armor ~/rpm-repos/packages/repodata/repomd.xml </syntaxhighlight> == Create a .repo file == Create the repo file at <code>~/rpm-repos/tux.repo</code>. <syntaxhighlight lang="ini"> [tux] name=Tux repository $releasever baseurl=https://rpm.example.com/tux/fedora-$releasever/$basearch enabled=1 gpgcheck=1 gpgkey=https://rpm.example.com/tux-pgp-key.pub </syntaxhighlight> The RPM repository should now be ready to be served on a web server with <code>~/rpm-repos</code> as the web root. == Example Caddy configuration == <syntaxhighlight> rpm.example.com { root * /home/tux/rpm-repos/ file_server browse } </syntaxhighlight> 86b09169724aac3a090260452d92fa3c6e0e275e 0 1249 5564 5361 2026-05-28T12:40:25Z Veri 398 Added a sentence, showing remix is also used as a term wikitext text/x-wiki In Linux, a derivative [[Linux Distributions|Linux distribution]] is a distribution that will incorporate elements from its '''parent distribution''', such as the [[Package Manager]], and [[Repository|Repositories]] but may sometimes also add their '''own''' configuration or other changes in order to make the user experience different from the parent distribution. One major example of this is [[Ubuntu]] being a derivative distribution of [[Debian]] [[File:Fedoracosmicspin.jpg|thumb|Screenshot of the Fedora Cosmic Spin]] There are also different types of derivatives, such as '''flavors/spins''' or even '''remixes,''' which are most synonymous with [[Ubuntu]] and [[Fedora]] respectively. Flavors, or spins, are typically '''lightly modified''' distributions with very '''few changes''' from their parent distribution, which can mean something as small as a change in [[Desktop Environments|Desktop Environment]]. e7ba5be88e419a78f3c4d337bbe83d6ef45b604e 0 1295 5565 2026-05-28T12:41:14Z Veri 398 Redirect to derivative page wikitext text/x-wiki #REDIRECT [[Derivative]] 910aaadd033b87403c699fb8fa24113446af30a1 0 1091 5567 5260 2026-05-28T13:16:15Z Int 401 Reword for formality wikitext text/x-wiki {{Work In Progress}} {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox |caption=MangoWM logo |developers=MangoWM developers |firstrelease=0.1.1, 2025-02-17 |languages=[[C]] |lastrelease=V0.13.1, 2026-05-18 |title=MangoWM|website=[https://mangowm.github.io/ mangowm.github.io] |releasestatus=Maintained |image=[[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref>. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 4f183842ffee7b0b13d46529f44ff2e6dcecc954 0 228 5568 3579 2026-05-28T13:55:07Z Int 401 Reword for formality and conciseness wikitext text/x-wiki [[Category:Terminology]] {{Cleanup|Instructions need to be spilt to its own page under Guides namespace.}}The [https://aur.archlinux.org/ '''Arch''' '''User''' '''Repository'''] (AUR) is a community-driven repository for [[Arch Linux]] users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]].<ref name=":0">[https://wiki.archlinux.org/title/Arch_User_Repository "Arch User Repository"]. Arch Linux.</ref> The AUR also has its own voting system. All packages are eligible for adoption by a Package Maintainer for inclusion in the <code>extra</code> repository, and the vote count is one of the considerations in that process. [[Package|Packages]] that enter the extra repository can be directly installed with pacman.<ref name=":0" /> === How does it work? === Unlike other repositories, the AUR '''does not host prebuilt packages'''. Instead, it hosts ''PKGBUILD'' files that users can use to build packages themselves. These PKGBUILDs contain package metadata and two functions: * <code>prepare()</code>: This function prepares your package folder which is the extracted view of a typical package. * <code>package()</code>: This function adds basic metadata (optionally verification keys like SHA256 ones) and then generates the package. Not all packages build from source. Some packages simply copy prebuilt files to their respective locations, similar to other packaging systems. Package converters like [[alien]] can take a non-Arch package and convert it into an Arch-compatible one. PKGBUILDs can be installed without root because they are just scripts. However, it is recommended to read the PKGBUILDs you get for your own safety, as anyone can upload to the AUR. === Installing a package === This section will use the [https://aur.archlinux.org/visual-studio-code-bin.git visual-studio-code-bin] package as an example to demonstrate package installation. # Install the following official packages: #* <code>git</code> : This will be used to clone the package from the AUR. #* <code>base-devel</code> : This provides tools to make PKGBUILDs. # <code>git clone https://aur.archlinux.org/visual-studio-code-bin.git</code>: This will clone the package from the AUR and will be stored in your current directory. # <code>cd visual-studio-code-bin</code> : This will put you into the directory of your cloned package. # <code>makepkg -si</code> : <code>makepkg</code> is one of the main utilities to install any AUR package, the <code>-s</code> flag syncs any dependencies of your package (so it won't give you an error if the package dependencies are not installed) and the <code>-i</code> flag will install the package generated if your package is made and has no errors. And that's it, you can run the program and check it out! You can do this with any program and it will work! To simplify the process, AUR helpers have been created. While we won't cover them in detail, here's a brief overview: the basic AUR helpers can search and download packages, the more advanced ones can search, build, and install packages, and the most commonly used ones, known as pacman wrappers, can search, build, update, and manage system packages. This means you can update your entire system using these tools. However, pacman is still required as these helpers essentially use pacman to perform their tasks. === Package naming === * Packages ending in <code>-bin</code> are precompiled and are not built from source. * Packages ending in <code>-git</code> will pull the latest version of the software from [[Git]]. They are unstable and not intended for regular use, but they may have newer features or bug fixes. You should also look out for 'marked as orphaned' or 'marked as out of date' packages as they are commonly found with packages that have the <code>-git</code> suffix. The binary ones are recommended for every package and are probably the most frequently updated ones. === Creating a package === To create a PKGBUILD for the AUR it is quite simple, you can follow these steps: * Make a folder for your package separately and make a file inside that folder just called <code>PKGBUILD</code> (case-sensitive). * Inside that file add required metadata<ref>[https://wiki.archlinux.org/title/PKGBUILD PKGBUILD], ArchWiki, 2025-06-12 (Accessed: 2025-08-09)</ref> and/or optional ones for your PKGBUILD. * Then you need to add the functions, these look like bash functions and scripts of similar kind, like we said earlier about the <code>prepare()</code> and <code>package()</code> functions but we do also need some more important functions like <code>pkgver()</code>, <code>build()</code> and <code>check()</code> depending on what kind of package you are trying to make. These functions are more properly explained on the Arch Wiki.<ref>[https://wiki.archlinux.org/title/Creating_packages#PKGBUILD_functions Creating packages], ArchWiki, 2025-06-13 (Accessed: 2025-08-09)</ref> * And then, just check your package, save it, then run the same command as before <code>makepkg -si</code> to check the package. If it does build and prompts you to install that means it worked! You can also use namcap<ref>[https://wiki.archlinux.org/title/Namcap namcap], ArchWiki, 2025-06-16 (Accessed: 2025-08-09)</ref> to check errors in the package. * To submit your package to the AUR, create an account on the AUR properly and setup the SSH keys. Please do also make sure that the package you are making is not already made. * Once done, just open your terminal and run git clone <code>https://aur.archlinux.org/&#x3C;your_package_name&#x3E;.git</code>, you might think it is not made but what you are actually doing here is sending a request to the AUR to create a package and clone it. When the AUR receives a clone request for a package not already made, it just creates a new blank repository, make sure it is created via your AUR SSH key. Also, make sure to add the suffix as mentioned earlier since the packages are actively moderated by volunteers and they may strike your package down. * Copy the PKGBUILD you made into this folder you have cloned, go inside that folder and run <code>makepkg --printsrcinfo > .SRCINFO</code>. This will create a required .SRCINFO file that just contains general metadata for AUR such as description and other things. Then, you can just add the two files via git, make a commit with a message like "Initial commit" and then push it. It should work and the package should be visible on the AUR in a few minutes. Please note that the AUR will not permit the package on the AUR repository if it does not find the .SRCINFO file. If you want to delete, merge, orphan or mark your or any package out of date, you can send a request to the AUR mailing list. === Safety === As seen, you can publish your package to the AUR with minimal checks beyond the general SRCINFO file. Although the AUR is actively moderated by volunteers, some malicious packages may not be caught. It is advisable for users to read the PKGBUILDs they use from the AUR to ensure their safety. Users are encouraged to report any malicious packages that may have been missed to the AUR mailing list. The AUR hosts over 60,000 packages, and user reports help maintain its security and reliability. == References == <references /> d66b71df0367daa89b7f19a6368ed4e118f77246 0 679 5569 5448 2026-05-28T13:58:21Z Int 401 Backlink "version control system" instead of abbreviation "VCS" wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Git-Icon.svg|frameless]] | caption = Git's logomark | title = git | releasestatus = Maintained | lastrelease = 2.54.0 (2026-04-20) [https://git-scm.com/] | languages = [[C]] | developers = [[Linus Torvalds]] and Contributors | website = https://git-scm.com | license = [[GPL-2.0-only]] | sourcecode = https://git.kernel.org/pub/scm/git/git.git }} '''Git''' is a powerful, efficient, flexible [[FOSS|free and open-source]] distributed [[version control system]] designed to track changes in files, typically used for source code management in collaborative software development between multiple developers, by maintaining a full history of changes locally on each user's computer, enabling work without constant network access.<ref>[https://git-scm.com/ Git], Git, 2025 (Accessed: 2025-06-22)</ref><ref>[https://en.wikipedia.org/wiki/Git Git], Wikipedia, 2025 (Accessed: 2025-06-22)</ref> Git is widely regarded as the ''de facto'' standard version control system in the industry, supported by different online repository hosting providers such as GitHub, GitLab, Gitea, and Codeberg.<ref>[https://kids.kiddle.co/Git Git Facts for Kids], Kids Encyclopedia Facts, 2024 (Accessed: 2025-06-22)</ref> == History == Git was created in April 2005 by Linus Torvalds after the [[Linux kernel]] development team lost free access to BitKeeper, a proprietary version control system they had used since 2002. The BitKeeper license was revoked due to disputes involving reverse engineering of its protocols.<ref>[https://git-scm.com/book/ms/v2/Getting-Started-A-Short-History-of-Git 1.2 Getting Started - A Short History of Git], Git, 2025 (Accessed: 2025-06-22)</ref> Torvalds needed a distributed version control system that was fast, efficient, and could handle the large-scale, non-linear development of the Linux kernel, with patch application times under three seconds, unlike existing systems that were too slow or centralized.<ref>[https://marc.info/?l=linux-kernel&m=111288700902396 Re: Kernel SCM saga.]{{Dead Link|2026-05-26|timeout (10)}}, Linux Torvalds, 2005 (Accessed: 2025-06-22)</ref> Torvalds started developing Git on April 3, 2005, announced it on April 6, and by April 7, Git was self-hosting its own repository.<ref>[https://marc.info/?l=git&m=117254154130732 Re: Trivia: When did git self-host?]{{Dead Link|2026-05-26|timeout (10)}}, Linux Torvalds, 2007 (Accessed: 2025-06-22)</ref> The first merge of multiple branches occurred on April 18, and by April 29, Git was capable of applying [[patch]]es at a rate of 6.7 patches per second to the Linux kernel source.<ref>[https://marc.info/?l=git&m=111475459526688 Mercurial 0.4b vs git patchbomb benchmark]{{Dead Link|2026-05-26|timeout (10)}}, Matt Mackall, 2005 (Accessed: 2025-06-22)</ref> Git managed the Linux kernel 2.6.12 release in June 2005.<ref>[https://marc.info/?l=git-commits-head&m=111904216911731 Linux 2.6.12]{{Dead Link|2026-05-26|timeout (10)}}, Linus Torvalds at Linux Kernel Mailing List, 2005 (Accessed: 2025-06-22)</ref> On July 26, 2005, Torvalds handed over maintenance of Git to Junio Hamano, who became the lead maintainer and released Git version 1.0 in December 2005.<ref>[https://community.appsmith.com/content/blog/evolution-git-dive-tech-history The Evolution of Git: A Dive Into Tech History | Appsmith Community Portal], Ron Northcutt, 2023 (Accessed: 2025-06-22)</ref><ref>[https://marc.info/?l=git&m=112243466603239 Meet the new maintainer.]{{Dead Link|2026-05-26|timeout (10)}}, Linus Torvalds, 2005 (Accessed: 2025-06-22)</ref> Git's early design emphasized a distributed workflow similar to BitKeeper's but with strong safeguards against corruption and a focus on speed and simplicity. Over time, Git evolved with the addition of [[GUI|graphical user interfaces]] and integration with platforms like [[GitHub]], which launched in 2008 and transformed collaborative software development.<ref>[https://www.linkedin.com/pulse/evolution-git-deep-dive-version-control-revolution-anurag-prakash-llb7f The Evolution of Git: A Deep Dive into the Version Control Revolution 🚀], Anurag Prakash, 2024 (Accessed: 2025-06-22)</ref> == Usage == In a ''repository'' (''repo''), Git manages different versions (''revisions'') of files. There are 3 kinds of revision: * A ''commit'' is a single immutable moment in the repository. When the user chooses to create a “backup” of their code-base, they add and ''commit'' their changes. The <code>git commit</code> command does exactly the latter, as explained later in this section. * A ''tag'' marks a commit, giving it a custom label. This is done using the <code>git tag</code> command. * A ''branch'' marks the latest commit in a consecutive list of commits made to a repo. A repository when initialised with <code>git init</code> comes with no commits. The “first backup” (''initial commit'') marks the start of the ''commit history''. It is special since it is the only permitted commit in a repo that does not come with a parent, and other commits must have at least 1 parent commit. The default ''branch'' for a repository is usually named ''master'' or ''main''. ''Branches'' serve as identifiers for the latest commit that does not have a ''child'' (next commit in line). When a commit is created in a branch, the branch updates and points to that new commit instead. New branches can be made using <code>git checkout -b new_branch_name</code> or <code>git switch -c new_branch_name</code>. Think of the repo as a tree, with branches as branches of the tree, and commits as leaves on the branches. Adding more commits to a repository is just like having more leaves on the branches of a growing tree. A repository can have multiple branches, each representing a different line of development. Branches allow developers to work on separate features or bug fixes without interfering with each other. When a feature is complete, it can be merged back into the main branch using <code>git merge</code>. This process ensures that the main branch always contains the latest and most stable code. === Stage and Commit === To stage changes, use <code>git add</code>. This command adds files or changes to the staging area, which is a temporary area where changes are prepared for the next commit. Once changes are staged, they can be committed using <code>git commit</code>. This command creates a new commit with the staged changes, along with a commit message that describes the changes made. A stage is a temporary area where changes are prepared for the next commit. It is a way to group changes together before committing them to the repository. Staging changes allows developers to selectively include or exclude changes from a commit, making it easier to manage and track changes over time. Unstaged files are ignored and not tracked by Git. In addition to staging changes, you can also use <code>git rm</code> to remove files. Alternatively, <code>git rm --cached</code> can be used to remove files from the staging area without deleting them from the repository. <code>git commit -a</code> is a shortcut for staging all modified files and committing them with a single command. This command is useful when you want to commit all changes in a single step. === Merge and Rebase === [[File:Git_merge_rebase_squash_explained.png|thumb|A graphical representation of the three merge methods in Git.]] A ''merge'' is a commit that combines the changes from two or more branches into a single branch. It is created using the <code>git merge</code> command. The merge commit has two parents, one for each branch being merged. A ''rebase'' is a process that changes the base of a branch by applying its commits on top of another branch. It is done using the <code>git rebase</code> command. The rebase commit has one parent, the branch being rebased onto. A ''squash'' is a process that combines multiple commits into a single commit. It is done using the <code>git merge --squash</code> command. The squash commit has one parent, the branch being rebased onto. === Stash === Stashing is a way to temporarily save changes that are not ready to be committed. This command creates a stash entry that contains the staged changes, and removes them from the working directory. Stashes act as a stack. Stashed pushed onto the stack using <code>git stash</code> can be popped using <code>git stash pop</code>. You can also list all stashes using <code>git stash list</code>, drop a stash using <code>git stash drop</code>, clear all stashes using <code>git stash clear</code>, and apply a stash using <code>git stash apply</code>. === Checkout === The <code>git checkout</code> command is a very powerful command: it can be used to switch between revisions, create new branches, discard changes, obtain files from other revisions into the current working directory, and more. {| class="wikitable" |+Usages of <code>git checkout</code> !Action !Command |- |Switch to master branch |<code>git checkout master</code> |- |Create and switch to develop branch |<code>git checkout -b develop</code> |- |Create and switch to feature branch, based on develop |<code>git checkout -b feature develop</code> |- |Obtain files from develop into working directory |<code>git checkout develop -- file1 file2</code> |- |Discard changes in the current working directory |<code>git checkout -- file1 file2</code> |} === Remote === Remote repositories are repositories that are not on the local machine. They are used to share code with other developers, and to collaborate on projects. If you would like to clone a remote repository, you can use <code>git clone</code>. This will create a new local repository that is a copy of the remote repository. A default remote named <code>origin</code> will be created, pointing to the original repository. The <code>git remote</code> command is used to manage remote repositories. It can be used to add, remove, rename, and view remote repositories. After your changes are committed, you can push them to the remote repository using <code>git push</code>. To pull changes from a remote repository, you can use <code>git pull</code>. === Revert and Reset === <code>git revert</code> creates a new commit that reverses the changes made in the specified commit. This is useful for undoing a commit that has already been pushed to a remote repository. <code>git reset</code> is used to reset the current branch to a previous commit. The local files are preserved. <code>git reset --hard</code> is used to reset the current branch to a previous commit and discard all changes made after that commit. === Bisect === <code>git bisect</code> is used to find the commit that introduced a bug. It works by dividing the commit history into two halves, and then testing each half to see if the bug is present, and then repeating the process until the commit that introduced the bug is found. This process is called binary search. <code>git bisect start</code> starts the bisect process. Here the user should use <code>git bisect good</code> and <code>git bisect bad</code> to mark the known good and bad commits. After that, git will checkout to the commit to be tested. The user should then test the commit and mark it as good or bad using <code>git bisect good</code> or <code>git bisect bad</code>. == References == 3348b5e8d306e028ff77248023f61b62ae94be2e 4 556 5570 4624 2026-05-28T16:46:20Z Atmois 13 Update history wikitext text/x-wiki == <u>About</u> == {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! '''FOSS Wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.foss.wiki Discord server]! To contact the administrators, check out our [[FW:Contact|contact page]]! If you need FOSS or Linux support, you can check out <code>#quick-support</code> and <code>#support-forum</code> in [https://discord.gg/nglinux Neon Genesis's Linux Discord]! We have 4 key values for FOSS Wiki, that summarise all of our [[guidelines]] : # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. == <u>Important Links</u> == * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of FOSS Wiki * [[Contributing]] - Outlines how YOU can contribute to FOSS Wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of FOSS Wiki * [[FW:Disclaimer|Disclaimer]] - FOSS Wiki Editing Disclaimer == <u>Wiki Staff</u> == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director * [[User:Scottc96|Scott96]] - Wiki Director ====== Operators ====== * [[User:Ow0cast|Ow0cast]] - Wiki Team * [[User:Madonuko|Madonuko]] - Wiki Team == '''<u>History</u>''' == === <u>Independence</u> ~ ''April 2026 - Present'' === '''May 2026''' We obtained the '''atl.wiki''' domain to act as a redirect to our new domain alongside doing some much needed improvements to the infrastructure to improve database backup resilience and improved our [[FW:Privacy Policy]] further with the new changes. We also opened up [https://donate.foss.wiki donations] via Open Collective to allow for quicker and larger improvements to the wiki utilising an independent bank and stripe accounts. Alongside this, [https://fibery.io Fibery] generously provided us an unlimited pro plan for the wiki! With this we setup a public [https://open.foss.wiki Ledger and Roadmap] which on it you can see exactly what we are planning and spending money on to keep the wiki running. On the 22nd of May we did our launch party, with the support of over half a dozen other communities we pushed the wiki into a new era. We welcomed almost 100 new editors helping to make over 500 new edits to the wiki in the week following the launch. We also grew the wiki team with [[User:Madonuko]] (with their nifty bot [[User:Hamachitan]]) join us! After the launch party thanks to donations from [[User:Scottc96]] and [[User:Wilbur]], we were able to provision a second VPS to host the wiki's database separately and to provide redundancy. Alongside this we implemented daily, immutable and encrypted backups of the database to a secure S3 bucket to ensure the data is securely backed up to protect the wiki. '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off (utilising the old wiki's database) into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] (promoted to co-director) remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. With the relaunch we setup of our status page with Phare at [https://status.foss.wiki status.foss.wiki] and launched our own [https://discord.foss.wiki Discord Server] and partnered with [https://discord.gg/nglinux Neon Genesis Linux], a server run by [[User:Scottc96|Scott96]] to provide high quality FOSS/Linux support and discussions. Our wiki deployment code is available on our new [https://github.foss.wiki GitHub] and we redeployed Umami analytics and updated our [[FW:Privacy Policy|Privacy Policy]] to clarify some unclear data retention details as well as provide Opt Out information for Umami if users with to not be included in wiki usage analytics. ''Finally, we thank everyone who stuck with us especially former ATL staff for all their support and kindness during these tough times, every edit and every bit of support is valued and I am eternally grateful for everyone's help to make this fantastic resource for FOSS/Linux users, thank you and I hope to see you editing with us in the future! ~ atmois'' === <u>ATL Ownership</u> ~ ''May 2024 - March 2026'' === ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. to be added: DDoS report, 1.0 release and wikibot launch ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[FW:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scott96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] 12af01898314841fe55234db45b52398bb742a3f 4 595 5571 4623 2026-05-28T16:48:42Z Atmois 13 Update staff contact wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.foss.wiki Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all staff at once please email: ''team(at)foss.wiki'' ~ To report security vulnerabilities please see our [[FW:Security|Security Policy]]. [[User:Atmois|Atmois]] - Wiki Co-Director ''- zoe.m(at)foss.wiki'' [[User:Scottc96|Scott96]] - Wiki Co-Director ''- scott.c(at)foss.wiki'' [[User:Ow0cast|Ow0cast]] - Wiki Team - ''nikki.k(at)foss.wiki'' [[User:Madonuko|Madonuko]] - Wiki Team - ''mado.n(at)foss.wiki'' 8faf4203a70c139258fc28341f54a98dd552762b 0 663 5572 4997 2026-05-28T18:03:33Z Habaja1 377 added small bit of text on notable packages in Terra. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Terra.svg|frameless]] | caption = Terra logo | title = Terra | releasestatus = Maintained, rolling | lastrelease = <code>terrarawhide</code>, <code>terra42</code>, <code>terrael10</code> | languages = Sources mainly composed of RPM Spec, HCL, AndaX/Rhai | developers = Fyra Labs | website = [https://terrapkg.com terrapkg.com] }} '''Terra''' is a third-party software [[repository]] for [[Fedora|Fedora Linux]] and [[Red Hat Enterprise Linux]].<ref name=":0">[https://terrapkg.com terrapkg.com], Terra, 2026 (Accessed: 2026-05-23)</ref> Developed by [[Fyra Labs]], it consists of thousands of packages, including ones that are difficult to include into the Fedora main repositories due to their strict packaging guidelines. As opposed to other Fedora repositories including [[RPM Fusion]], Terra employs a vastly different back-end infrastructure, which is advertised as more current, modern, secure, and transparent, alongside with its lenient guidelines and ease of packaging.<ref name=":0" /><ref name=":1">[https://docs.terrapkg.com/general/infrastructure/ How Terra Works], Terra Documentation, 2026 (Accessed: 2026-05-23)</ref> Notable packages included in Terra include: Prism launcher, Proton VPN, zed and ROG control center.<ref>{{Cite|url=https://docs.terrapkg.com/reference/faq|title=Notable included packages in terra from it's FAQ|accessdate=2026/05/28}}</ref> == Installation == Fyra Labs has documented different installation methods for different supported distributions in their developer documentation: https://docs.terrapkg.com/usage/installing/. Visit the official documentation for up-to-date installation methods for different distributions, including variants of [[RHEL|Enterprise Linux]]. {{Guide Warning}} For Fedora and its derivatives:<syntaxhighlight lang="sh"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight>The <code>terra-release-extras</code> package may be installed additionally to enable ''Terra Extras''. The package also comes with other streams not enabled by default, including the ''Nvidia'' and ''Mesa streams''. They can be enabled manually with:<syntaxhighlight lang="sh"> sudo dnf config-manager setopt terra-nvidia.enabled=1 sudo dnf config-manager setopt terra-mesa.enabled=1 </syntaxhighlight> == Infrastructure == As opposed to Fedora<ref name=":3">[https://koji.fedoraproject.org/ Build System Info | koji], Fedora, 2025 (Accessed: 2025-06-19)</ref> and RPM Fusion<ref name=":4">[https://koji.rpmfusion.org/koji/ Build System Info | koji]{{Dead Link|2025-08-14|401}}, RPM Fusion, 2025 (Accessed: 2025-06-19)</ref>, Terra uses alternative components mainly developed by Fyra Labs, such as '''Andaman''' for handling auto-updates and package builds, '''Subatomic''' for storing artifacts (e.g. RPMs), '''Tetsudou''' for generating <code>mirrorlist</code>s and <code>metalink</code>s, etc.; while uses '''GitHub Actions''' to build packages using the runners provided by GitHub<ref name=":1" />. === Automatic Updates === Update scripts written in a tailor-made programming language called ''AndaX'' (which is based on Rhai)<ref>[https://developer.fyralabs.com/andaman/andax AndaX - Fyra Developer], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> are executed as a GitHub Actions [[cron]] job, periodically depending on their “channel”, by default every 10 minutes[https://github.com/terrapkg/packages/blob/5125b7ebc830fbe0efdce2be58fd14dc1bec1e44/.github/workflows/update.yml#L4]<ref name=":2">[https://docs.terrapkg.com/contributing/autoupdate/ Automatic Updates], Terra Documentation, 2026 (Accessed: 2026-05-23)</ref>, ensuring users access the latest software versions without delays. This effectively makes Terra '''rolling-release''', unlike Fedora repositories which are stable-release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022 (Accessed: 2025-06-22)</ref>. Other “channels” include nightly, weekly, and branched.<ref name=":2" /> === Build System and Package Delivery System === Instead of traditional tools like koji and fedpkg, Terra uses '''Andaman''' (<code>anda</code>), a meta build system written in [[Rust]].<ref>[https://github.com/FyraLabs/anda/ FyraLabs/anda: A modern Build/CI System], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref> Anda automates package builds, ensuring speed and maintainability at scale. Written in [[Go]], '''Subatomic''', “[a] modern package delivery system for RPMs”<ref>[https://github.com/FyraLabs/subatomic FyraLabs/subatomic: A modern package delivery system for RPMs], Fyra Labs, 2025 (Accessed: 2025-06-22)</ref>, is used to manage built artifacts uploaded from the GitHub Actions pipeline. === GitHub Actions === GitHub Actions is used to bump and build all packages in Terra, ensuring transparency in the build process, since the runners are provided by GitHub,<ref name=":1" /> while build logs are public to anyone with a GitHub account. === Monorepo Management === Package sources, such as spec files and update scripts, are stored in a [https://github.com/terrapkg/packages single git monorepo], simplifying contributions and audits. New packages are submitted via pull requests, with issues tracked and triaged publicly. Additionally, the backport tool unifies spec files across different branches, making maintenance easier even when different release versions of Fedora and Enterprise Linux need to be dealt with. == Separate Policies, Guidelines and Macros == Terra employs relatively lenient packaging guidelines compared to upstream Fedora, allowing most package submissions, even ones that are closed-source. Various per-language guidelines are different, notably Rust, Go, [[Nim]] and [[Zig]]. Terra also comes with a new set of macros within the <code>anda-srpm-macros</code> package.<ref>[https://docs.terrapkg.com/contributing/policies/ Policies], Terra Documentation, 2026 (Accessed: 2026-05-23)</ref> == See Also == * [https://terrapkg.com Main Website] * [https://docs.terrapkg.com Terra Documentations] * [https://github.com/terrapkg/packages Terra Sources] == References == 0c045518e46c8dc3ed5e84a5b2b51df226874a35 6 1296 5573 2026-05-28T18:43:38Z Habaja1 377 wikitext text/x-wiki larp larp larp sahur 95e35f7cc1e47851fe8a03e04873c23258a362bc 2 1297 5574 2026-05-28T18:43:57Z Habaja1 377 created this wikitext text/x-wiki [[File:LARP.png|thumb|larp larp larp sahur]] linux larper and pc enthousiast. i like story games. im learning to code in rust. idk what else to say == Projects == ButterflyOS (My own distro with pacman, accidentaly wiped the arch installation it was in) Some random gas gaints that looked like bowling balls in blender New distro coming soon? (this time will be based on another distro tho) == Linux distro pipeline == [[Pop!_OS]] --> [[Kubuntu]] --> [[Arch Linux]] --> [[NixOS]] --> [[Arch Linux]]--> [[Ultramarine Linux]] --> [[Gentoo]] (gonna try soon) 5a9d3f235c5f08937eb8640f9582ef10666c3e36 5575 5574 2026-05-28T18:44:55Z Habaja1 377 wikitext text/x-wiki [[File:LARP.png|thumb|larp larp larp sahur]] linux larper and pc enthousiast. i like story games. im learning to code in rust. idk what else to say == Projects == ButterflyOS (My own distro with pacman, accidentaly wiped the arch installation it was in) Some random gas gaints that looked like bowling balls in blender New distro coming soon? (this time will be based on another distro tho) == Linux distro pipeline == [[Pop!_OS]] --> [[Kubuntu]] --> [[Arch Linux]] --> [[NixOS]] --> [[Arch Linux]]--> [[Artix Linux]] -->[[Ultramarine Linux]] --> [[Gentoo]] or [[NixOS]] again(gonna try soon) dd56f2af5a7f62e7f9bab3323d672e77e9d5e13f 5576 5575 2026-05-28T18:46:47Z Habaja1 377 some contact stuff wikitext text/x-wiki [[File:LARP.png|thumb|larp larp larp sahur]] linux larper and pc enthousiast. i like story games. im learning to code in rust. idk what else to say == Projects == ButterflyOS (My own distro with pacman, accidentaly wiped the arch installation it was in) Some random gas gaints that looked like bowling balls in blender New distro coming soon? (this time will be based on another distro tho) == Linux distro pipeline == [[Pop!_OS]] --> [[Kubuntu]] --> [[Arch Linux]] --> [[NixOS]] --> [[Arch Linux]]--> [[Artix Linux]] -->[[Ultramarine Linux]] --> [[Gentoo]] or [[NixOS]] again(gonna try soon) if you wanna talk to me do it on discord i guess user is habaja1. github: https://github.com/Habaja1 5a8194778c8d862a004795b4f3853066d45c6dc1 0 1292 5577 5563 2026-05-28T20:24:04Z Ow0cast 249 Ow0cast moved page [[Fluxerworld]] to [[Fluxer World]]: Misspelled title wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxerlogo.png|150px]] | caption = The Fluxer World logo | title = Fluxer World | releasestatus = Beta | lastrelease = 1.0.86 | languages = TypeScript, Erlang, React Native | developers = Xuruh and Contributors | website = https://fluxer.world | sourcecode = https://github.com/fluxerworld/fluxerworld | license = AGPLv3 }} '''Fluxer World''' is a free, open-source, and cross-platform instant messaging and VoIP platform with end-to-end encryption for direct messages and group conversations. It is a fork of [[Fluxer]], with divergent features focused on encryption, mobile support, and self-hostable infrastructure. ==Overview== Fluxer World is available on Linux (AppImage, tar.gz, [[RPM]], .deb, [[flatpak|Flatpak]], AUR), Windows (NSIS installer), macOS (dmg), Android (APK via [https://f-droid.org F-Droid] and direct download), and iOS. A Progressive Web App is available at https://fluxer.world. ==Privacy and encryption== Fluxer World is designed to be privacy-conscious. Direct messages and group conversations are end-to-end encrypted using the Olm and Megolm cryptographic ratchets from the Matrix protocol. Because chats are end-to-end encrypted, administrators are not able to read their contents. Fluxerworld also does not monitor user logs. ==Features== Notable features of Fluxer World include: * End-to-end encryption for 1:1 direct messages and Group DMs using the [https://gitlab.matrix.org/matrix-org/olm Olm and Megolm] cryptographic ratchets (Matrix-compatible). * Native React Native mobile applications for Android with feature parity to the desktop client, including voice/video calls and screen sharing. * Communities, with organized channels, categories, roles and moderation tools. * Voice and video calls with screen sharing, backed by [https://livekit.io LiveKit]. * Custom emotes and stickers. * Media attachments like images, videos, audio or text. Note that attachments have an expiration date depending on their size. * Message search, with ability to filter by users, channels, dates, and more. * A bot and webhook API. ==Downloads== Fluxer World provides clients for multiple platforms, available via the Snap Store, AUR, Fedora Copr, F-Droid, GitHub Releases, and more. ===Install via terminal=== * '''Snap:''' <code>sudo snap install fluxer-world</code> * '''Arch (AUR):''' <code>yay -S fluxer-world-bin</code> * '''Fedora (Copr):''' <code>sudo dnf copr enable xuruh/fluxer-world && sudo dnf install fluxer-world</code> * '''F-Droid:''' add the repo <code>https://fluxer.world/fdroid/repo</code> in F-Droid settings ===Windows=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (x64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Portable (x64)] ===macOS=== * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Apple Silicon)] * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Intel)] ===Linux=== * [https://snapcraft.io/fluxer-world Snap Store] * [https://aur.archlinux.org/packages/fluxer-world-bin AUR] * [https://copr.fedorainfracloud.org/coprs/xuruh/fluxer-world/ Fedora Copr] * [https://github.com/fluxerworld/fluxerworld/releases/latest .deb (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest .rpm (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest AppImage (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest tar.gz (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Flatpak] ===Mobile=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Android APK] * [https://fluxer.world/fdroid/repo F-Droid] * [https://github.com/fluxerworld/fluxerworld/releases/latest iOS IPA] ==History== Fluxer World was forked from [[Fluxer]] to focus on end-to-end encryption and first-class mobile support. End-to-end encrypted direct messages shipped in May 2026, followed by Group DM encryption in late May 2026. ==Relationship to Fluxer== Fluxer World shares its core server architecture with upstream [[Fluxer]] (Erlang/OTP gateway, TypeScript API), but diverges in client implementation, encryption layer, and packaging targets. Both projects are AGPLv3. ==See also== * [[Fluxer]] — upstream project ==External links== * [https://fluxer.world Official website] * [https://github.com/fluxerworld/fluxerworld Source code on GitHub] * [https://github.com/fluxerworld/fluxerworld/releases Releases] [[Category:Instant messaging]] [[Category:VoIP]] [[Category:Free software]] df895a581cfcb286334b2d33406da6d9a25d3dab 0 1298 5578 2026-05-28T20:24:04Z Ow0cast 249 Ow0cast moved page [[Fluxerworld]] to [[Fluxer World]]: Misspelled title wikitext text/x-wiki #REDIRECT [[Fluxer World]] 03a4bce11996f6c2fc591f81dd3eb8d78472ba48 0 1265 5579 5535 2026-05-29T01:42:51Z Int 401 Reword for clarity wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = Wine | image = [[File:Wine Logo.png|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. == Installation == === [[Arch Linux]] === Stable: <syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight> Staging: <syntaxhighlight lang="sh">sudo pacman -S wine-staging</syntaxhighlight> == Usage == Wine is a [[CLI|command-line]] program. Provide a Windows executable file for Wine to run: <syntaxhighlight lang="sh">wine <path to .exe></syntaxhighlight> === Prefixes === Wine stores configuration files and installed programs inside a ''Wine prefix''. Wine prefixes contain a minimal Windows filesystem (a.k.a. ''C: drive''). The default Wine prefix is <code>~/.wine</code>. You can modify the <code>WINEPREFIX</code> environment variable to change it. For example, to use the directory <code>myprefix/</code> as the Wine prefix to run <code>application.exe</code>: <syntaxhighlight lang="sh">WINEPREFIX=myprefix wine application.exe</syntaxhighlight> == Performance == === dxvk === By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). 8ac0ab2313e32b84f56d68c52ec3f2abe1e2ebae 5616 5579 2026-05-30T06:10:08Z Int 401 Add references section wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = Wine | image = [[File:Wine Logo.png|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. == Installation == === [[Arch Linux]] === Stable: <syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight> Staging: <syntaxhighlight lang="sh">sudo pacman -S wine-staging</syntaxhighlight> == Usage == Wine is a [[CLI|command-line]] program. Provide a Windows executable file for Wine to run: <syntaxhighlight lang="sh">wine <path to .exe></syntaxhighlight> === Prefixes === Wine stores configuration files and installed programs inside a ''Wine prefix''. Wine prefixes contain a minimal Windows filesystem (a.k.a. ''C: drive''). The default Wine prefix is <code>~/.wine</code>. You can modify the <code>WINEPREFIX</code> environment variable to change it. For example, to use the directory <code>myprefix/</code> as the Wine prefix to run <code>application.exe</code>: <syntaxhighlight lang="sh">WINEPREFIX=myprefix wine application.exe</syntaxhighlight> == Performance == === dxvk === By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). == References == <references /> 5453d653aa9f7f13a114e79ed74ef5651a187387 0 1009 5580 5566 2026-05-29T02:05:52Z Madonuko 140 Reverted edit by [[Special:Contributions/Habaja1|Habaja1]] ([[User talk:Habaja1|talk]]) to last revision by [[User:Hamachitan|Hamachitan]] wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}} {{DistributionInfobox | title = Bazzite | image = [[File:Bazzite Logo.svg|200px]] | caption = The Bazzite logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Flatpak]] | defaultdesktops = [[GNOME]],[[KDE Plasma]] | usagetype = Gaming | architectures = x86_64 | website = [https://bazzite.gg/ bazzite.gg] }} '''Bazzite''' (ˈba-ˌzīt,) is a gaming focused [[Fedora]]-based [[Linux Distributions|Linux distribution]]. == History == == Features == == Installation == == Trivia == == Refrences == b5fd88c52deeda19e522bf868b5dfcc45543811e 0 1299 5581 2026-05-29T02:17:26Z Int 401 Create WInetricks stub wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = Winetricks | releasestatus = Maintained | lastrelease = 26 Jan 2026 | languages = English | developers = Winetricks developers | website = https://github.com/Winetricks/winetricks | license = LGPL-2.1-only | sourcecode = https://github.com/Winetricks/winetricks }} Winetricks is a program that provides workarounds to common [[Wine]] problems.<ref>{{Cite|url=https://https://github.com/Winetricks/winetricks|title=Winetricks GitHub repository|accessdate=29 May 2026|author=Winetricks developers}}</ref> == Installation == === [[Arch Linux]] === <syntaxhighlight lang="sh">sudo pacman -S winetricks</syntaxhighlight> === [[Debian]] === <syntaxhighlight lang="sh">sudo apt install winetricks</syntaxhighlight> === [[Fedora]] === <syntaxhighlight lang="sh">sudo dnf install winetricks</syntaxhighlight> == Usage == Winetricks exposes a set of ''verbs'' (actions). To execute a verb: <syntaxhighlight lang="sh">winetricks <name of verb></syntaxhighlight> Multiple verbs can be executed in series: <syntaxhighlight lang="sh">winetricks <verb 1> <verb 2> <verb 3></syntaxhighlight> Change the <code>WINEPREFIX</code> environment variable to have Winetricks operate on a specific [[Wine#Prefixes|Wine prefix]]: <syntaxhighlight lang="sh">WINEPREFIX=<path to prefix> winetricks <name of verb></syntaxhighlight> === Commonly used verbs === A full list of verbs can be found [https://github.com/Winetricks/winetricks/blob/master/files/verbs/all.txt here]. * <code>dxvk</code>: Install [[dxvk]]. * <code>corefonts</code>: Install Microsoft core fonts (Arial, Times New Roman, Verdana, etc.). * <code>vcrun2019</code>: Install the Visual C++ 2015–2022 runtime. * <code>d3dx9</code>: Install DirectX 9 runtime libraries. * <code>dotnet48</code>: Install [[.NET]] Framework 4.8. == References == 9a0d22978c1a58f4bd7b8b437dc34bd67a2ad059 5582 5581 2026-05-29T02:19:28Z Int 401 Link to Wine's dxvk section wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = Winetricks | releasestatus = Maintained | lastrelease = 26 Jan 2026 | languages = English | developers = Winetricks developers | website = https://github.com/Winetricks/winetricks | license = LGPL-2.1-only | sourcecode = https://github.com/Winetricks/winetricks }} Winetricks is a program that provides workarounds to common [[Wine]] problems.<ref>{{Cite|url=https://https://github.com/Winetricks/winetricks|title=Winetricks GitHub repository|accessdate=29 May 2026|author=Winetricks developers}}</ref> == Installation == === [[Arch Linux]] === <syntaxhighlight lang="sh">sudo pacman -S winetricks</syntaxhighlight> === [[Debian]] === <syntaxhighlight lang="sh">sudo apt install winetricks</syntaxhighlight> === [[Fedora]] === <syntaxhighlight lang="sh">sudo dnf install winetricks</syntaxhighlight> == Usage == Winetricks exposes a set of ''verbs'' (actions). To execute a verb: <syntaxhighlight lang="sh">winetricks <name of verb></syntaxhighlight> Multiple verbs can be executed in series: <syntaxhighlight lang="sh">winetricks <verb 1> <verb 2> <verb 3></syntaxhighlight> Change the <code>WINEPREFIX</code> environment variable to have Winetricks operate on a specific [[Wine#Prefixes|Wine prefix]]: <syntaxhighlight lang="sh">WINEPREFIX=<path to prefix> winetricks <name of verb></syntaxhighlight> === Commonly used verbs === A full list of verbs can be found [https://github.com/Winetricks/winetricks/blob/master/files/verbs/all.txt here]. * <code>dxvk</code>: Install [[Wine#dxvk|dxvk]]. * <code>corefonts</code>: Install Microsoft core fonts (Arial, Times New Roman, Verdana, etc.). * <code>vcrun2019</code>: Install the Visual C++ 2015–2022 runtime. * <code>d3dx9</code>: Install DirectX 9 runtime libraries. * <code>dotnet48</code>: Install [[.NET]] Framework 4.8. == References == 72a83c0ae3b2c31a2ef4a531eeb5754175fd6f37 3000 1300 5583 2026-05-29T05:56:41Z Hyperreal 388 Init Guide:Install_Debian_with_LUKS2_on_Btrfs_with_GRUB wikitext text/x-wiki {{GuideWarning}} In this guide, we'll use a Debian Live ISO to do the following: * Create a single LUKS2 encrypted partition. * Create a single Btrfs filesystem with <code>@</code>, <code>@home</code>, <code>@swap</code> and other subvolumes. * Create an encrypted swapfile in the <code>@swap</code> subvolume. * Optional: removal of crypto keys from RAM during laptop suspend * Optional: configurations for laptops == Pre-installation setup == Boot into the live ISO, open a terminal, and become root. Install the needed packages. <syntaxhighlight lang="bash"> sudo -i apt update apt install debootstrap cryptsetup arch-install-scripts </syntaxhighlight> Create partitions. We'll assume the drive we're installing Debian onto is <code>/dev/nvme0n1</code>. <syntaxhighlight lang="bash"> cfdisk /dev/nvme0n1 </syntaxhighlight> In the <code>cfdisk</code> TUI, create the following: * GPT partition table * 512M <code>/dev/nvme0n1p1</code> EFI System Partition (EF00) * 100%+ <code>/dev/nvme0n1p2</code> Linux filesystem Now we'll format the partitions we created. The <code>cryptsetup</code> command will prompt us to enter a secure password for the LUKS2 encrypted partition. <syntaxhighlight lang="bash"> mkfs.fat -F 32 -n EFI /dev/nvme0n1p1 cryptsetup -y -v --type luks2 luksFormat --label Debian /dev/nvme0n1p2 cryptsetup luksOpen /dev/nvme0n1p2 cryptroot mkfs.btrfs /dev/mapper/cryptroot </syntaxhighlight> Now we'll create the Btrfs subvolumes. <syntaxhighlight lang="bash"> mount /dev/mapper/cryptroot /mnt btrfs subvolume create /mnt/@ btrfs subvolume create /mnt/@home btrfs subvolume create /mnt/@swap umount -lR /mnt </syntaxhighlight> Re-mount the subvolumes as partitions. <syntaxhighlight lang="bash"> mount -t btrfs -o defaults,subvol=@,compress=zstd:1 /dev/mapper/cryptroot /mnt mkdir -p /mnt/{boot,home} mkdir /mnt/boot/efi mount /dev/nvme0n1p1 /mnt/boot/efi mount -t btrfs -o defaults,subvol=@home,compress=zstd:1 /dev/mapper/cryptroot /mnt/home </syntaxhighlight> Setup the swap file. <syntaxhighlight lang="bash"> mkdir -p /mnt/swap mount -t btrfs -o subvol=@swap /dev/mapper/cryptroot /mnt/swap touch /mnt/swap/swapfile chmod 600 /mnt/swap/swapfile chattr +C /mnt/swap/swapfile btrfs property set ./swapfile compression none dd if=/dev/zero of=/mnt/swap/swapfile bs=1M count=16384 mkswap /mnt/swap/swapfile swapon /mnt/swap/swapfile </syntaxhighlight> == Base installation == Create a nested subvolume for <code>/var/log</code> under the <code>@</code> subvolume. This will be automounted with <code>@</code> so there is no need to add it to <code>/etc/fstab</code>. Nested subvolumes are not included in snapshots of the parent subvolume. Creating a nested subvolume for <code>/var/log</code> will ensure the log files remain untouched when we restore the rootfs from a snapshot. <syntaxhighlight lang="bash"> mkdir -p /mnt/var btrfs subvolume create /mnt/var/log </syntaxhighlight> Now we'll run <code>debootstrap</code> to bootstrap the base system. We'll use the Trixie release as an example, but we can use any release codename. <syntaxhighlight lang="bash"> debootstrap --arch amd64 trixie /mnt </syntaxhighlight> Bind the pseudo-filesystems for chroot. <syntaxhighlight lang="bash"> mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys mount -t proc proc /mnt/proc </syntaxhighlight> Generate fstab. <syntaxhighlight lang="bash"> genfstab -U /mnt >> /mnt/etc/fstab </syntaxhighlight> Chroot into the new system. <syntaxhighlight lang="bash"> cp -v /etc/resolv.conf /mnt/etc/ chroot /mnt </syntaxhighlight> == Configure the new installation == Set the timezone, locales, keyboard configuration, and console. <syntaxhighlight lang="bash"> apt install locales dpkg-reconfigure tzdata locales keyboard-configuration console-setup </syntaxhighlight> Set the hostname. <syntaxhighlight lang="bash"> echo 'hostname' > /etc/hostname echo '127.0.1.1 hostname.localdomain hostname' >> /etc/hosts </syntaxhighlight> Configure APT sources in <code>/etc/apt/sources.list</code>. * Replace <code>https://deb.debian.org/debian </code> with our desired mirror. * Replace <code>trixie</code> with our desired Debian version name. E.g., <code>bookworm</code>, <code>forky</code>. * Replace <code>main non-free-firmware</code> with the repositories we want. Options include: <code>main</code>, <code>contrib</code>, <code>non-free</code>, <code>non-free-firmware</code>. * The only entry that needs to stay unchanged is the <code>debian-security</code> repository. <syntaxhighlight> deb https://deb.debian.org/debian trixie main non-free-firmware deb https://deb.debian.org/debian trixie-updates main non-free-firmware deb https://deb.debian.org/debian trixie-backports main non-free-firmware deb https://deb.debian.org/debian-security trixie-security main non-free-firmware </syntaxhighlight> Install essential packages. <syntaxhighlight lang="bash"> apt update apt dist-upgrade apt install linux-image-amd64 linux-headers-amd64 firmware-linux firmware-linux-nonfree sudo command-not-found systemd-timesyncd systemd-resolved cryptsetup cryptsetup-initramfs efibootmgr btrfs-progs grub-efi </syntaxhighlight> Install a desktop environment (optional). <syntaxhighlight lang="bash"> apt install task-gnome-desktop task-desktop </syntaxhighlight> If installing on a laptop: <syntaxhighlight lang="bash"> apt install task-laptop powertop </syntaxhighlight> Set the root password. <syntaxhighlight lang="bash"> passwd root </syntaxhighlight> Create users and groups. We'll pretend our user is <code>tux</code> and that they want sudo privileges. <syntaxhighlight lang="bash"> adduser tux usermod -aG systemd-journal jas usermod -aG sudo jas </syntaxhighlight> If we want our user to be able to use sudo without a password, run the following commands. <syntaxhighlight lang="bash"> echo "tux ALL=(ALL) NOPASSWD: ALL" | tee /etc/sudoers.d/tux chmod 440 /etc/sudoers.d/tux </syntaxhighlight> == Setup the bootloader == Optional package for extra protection of suspended laptops. <syntaxhighlight lang="bash"> apt install cryptsetup-suspend </syntaxhighlight> Setup encryption parameters. We'll need the encrypted partition's UUID. <syntaxhighlight lang="bash"> blkid -s UUID -o value /dev/nvme0n1p2 </syntaxhighlight> Edit <code>/etc/crypttab</code> and use the UUID from the output of the previous command. <syntaxhighlight> cryptroot UUID=<uuid> none luks </syntaxhighlight> Install the bootloader. <syntaxhighlight lang="bash"> grub-install --target=x86_64-efi --efi-directory=/boot/efi --recheck --bootloader-id="Debian" </syntaxhighlight> Edit <code>/etc/default/grub</code> to include support for encrypted disks. <syntaxhighlight lang="bash"> GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" GRUB_ENABLE_CRYPTODISK=y GRUB_TERMINAL=console </syntaxhighlight> Update the grub configuration. <syntaxhighlight lang="bash"> update-grub </syntaxhighlight> Exit chroot and reboot. <syntaxhighlight lang="bash"> exit umount -lR /mnt reboot </syntaxhighlight> == Emergency recovery from live ISO == In the event of an emergency recovery situation, boot into the live ISO again and run the following commands to mount the encrypted filesystem for maintenance. <syntaxhighlight lang="bash"> sudo -i cryptsetup luksOpen /dev/nvme0n1p2 cryptroot mount -t btrfs -o defaults,subvol=@,compress=zstd:1 /dev/mapper/cryptroot /mnt mount /dev/nvme0n1p1 /mnt/boot/efi mount -t btrfs -o defaults,subvol=@home,compress=zstd:1 /dev/mapper/cryptroot /mnt/home mount -t btrfs -o subvol=@swap /dev/mapper/cryptroot /mnt/swap swapon /mnt/swap/swapfile mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys mount -t proc proc /mnt/proc chroot /mnt </syntaxhighlight> e7f456454180a5185f288888381d97d1020fe224 5584 5583 2026-05-29T05:57:58Z Hyperreal 388 Fix username wikitext text/x-wiki {{GuideWarning}} In this guide, we'll use a Debian Live ISO to do the following: * Create a single LUKS2 encrypted partition. * Create a single Btrfs filesystem with <code>@</code>, <code>@home</code>, <code>@swap</code> and other subvolumes. * Create an encrypted swapfile in the <code>@swap</code> subvolume. * Optional: removal of crypto keys from RAM during laptop suspend * Optional: configurations for laptops == Pre-installation setup == Boot into the live ISO, open a terminal, and become root. Install the needed packages. <syntaxhighlight lang="bash"> sudo -i apt update apt install debootstrap cryptsetup arch-install-scripts </syntaxhighlight> Create partitions. We'll assume the drive we're installing Debian onto is <code>/dev/nvme0n1</code>. <syntaxhighlight lang="bash"> cfdisk /dev/nvme0n1 </syntaxhighlight> In the <code>cfdisk</code> TUI, create the following: * GPT partition table * 512M <code>/dev/nvme0n1p1</code> EFI System Partition (EF00) * 100%+ <code>/dev/nvme0n1p2</code> Linux filesystem Now we'll format the partitions we created. The <code>cryptsetup</code> command will prompt us to enter a secure password for the LUKS2 encrypted partition. <syntaxhighlight lang="bash"> mkfs.fat -F 32 -n EFI /dev/nvme0n1p1 cryptsetup -y -v --type luks2 luksFormat --label Debian /dev/nvme0n1p2 cryptsetup luksOpen /dev/nvme0n1p2 cryptroot mkfs.btrfs /dev/mapper/cryptroot </syntaxhighlight> Now we'll create the Btrfs subvolumes. <syntaxhighlight lang="bash"> mount /dev/mapper/cryptroot /mnt btrfs subvolume create /mnt/@ btrfs subvolume create /mnt/@home btrfs subvolume create /mnt/@swap umount -lR /mnt </syntaxhighlight> Re-mount the subvolumes as partitions. <syntaxhighlight lang="bash"> mount -t btrfs -o defaults,subvol=@,compress=zstd:1 /dev/mapper/cryptroot /mnt mkdir -p /mnt/{boot,home} mkdir /mnt/boot/efi mount /dev/nvme0n1p1 /mnt/boot/efi mount -t btrfs -o defaults,subvol=@home,compress=zstd:1 /dev/mapper/cryptroot /mnt/home </syntaxhighlight> Setup the swap file. <syntaxhighlight lang="bash"> mkdir -p /mnt/swap mount -t btrfs -o subvol=@swap /dev/mapper/cryptroot /mnt/swap touch /mnt/swap/swapfile chmod 600 /mnt/swap/swapfile chattr +C /mnt/swap/swapfile btrfs property set ./swapfile compression none dd if=/dev/zero of=/mnt/swap/swapfile bs=1M count=16384 mkswap /mnt/swap/swapfile swapon /mnt/swap/swapfile </syntaxhighlight> == Base installation == Create a nested subvolume for <code>/var/log</code> under the <code>@</code> subvolume. This will be automounted with <code>@</code> so there is no need to add it to <code>/etc/fstab</code>. Nested subvolumes are not included in snapshots of the parent subvolume. Creating a nested subvolume for <code>/var/log</code> will ensure the log files remain untouched when we restore the rootfs from a snapshot. <syntaxhighlight lang="bash"> mkdir -p /mnt/var btrfs subvolume create /mnt/var/log </syntaxhighlight> Now we'll run <code>debootstrap</code> to bootstrap the base system. We'll use the Trixie release as an example, but we can use any release codename. <syntaxhighlight lang="bash"> debootstrap --arch amd64 trixie /mnt </syntaxhighlight> Bind the pseudo-filesystems for chroot. <syntaxhighlight lang="bash"> mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys mount -t proc proc /mnt/proc </syntaxhighlight> Generate fstab. <syntaxhighlight lang="bash"> genfstab -U /mnt >> /mnt/etc/fstab </syntaxhighlight> Chroot into the new system. <syntaxhighlight lang="bash"> cp -v /etc/resolv.conf /mnt/etc/ chroot /mnt </syntaxhighlight> == Configure the new installation == Set the timezone, locales, keyboard configuration, and console. <syntaxhighlight lang="bash"> apt install locales dpkg-reconfigure tzdata locales keyboard-configuration console-setup </syntaxhighlight> Set the hostname. <syntaxhighlight lang="bash"> echo 'hostname' > /etc/hostname echo '127.0.1.1 hostname.localdomain hostname' >> /etc/hosts </syntaxhighlight> Configure APT sources in <code>/etc/apt/sources.list</code>. * Replace <code>https://deb.debian.org/debian </code> with our desired mirror. * Replace <code>trixie</code> with our desired Debian version name. E.g., <code>bookworm</code>, <code>forky</code>. * Replace <code>main non-free-firmware</code> with the repositories we want. Options include: <code>main</code>, <code>contrib</code>, <code>non-free</code>, <code>non-free-firmware</code>. * The only entry that needs to stay unchanged is the <code>debian-security</code> repository. <syntaxhighlight> deb https://deb.debian.org/debian trixie main non-free-firmware deb https://deb.debian.org/debian trixie-updates main non-free-firmware deb https://deb.debian.org/debian trixie-backports main non-free-firmware deb https://deb.debian.org/debian-security trixie-security main non-free-firmware </syntaxhighlight> Install essential packages. <syntaxhighlight lang="bash"> apt update apt dist-upgrade apt install linux-image-amd64 linux-headers-amd64 firmware-linux firmware-linux-nonfree sudo command-not-found systemd-timesyncd systemd-resolved cryptsetup cryptsetup-initramfs efibootmgr btrfs-progs grub-efi </syntaxhighlight> Install a desktop environment (optional). <syntaxhighlight lang="bash"> apt install task-gnome-desktop task-desktop </syntaxhighlight> If installing on a laptop: <syntaxhighlight lang="bash"> apt install task-laptop powertop </syntaxhighlight> Set the root password. <syntaxhighlight lang="bash"> passwd root </syntaxhighlight> Create users and groups. We'll pretend our user is <code>tux</code> and that they want sudo privileges. <syntaxhighlight lang="bash"> adduser tux usermod -aG systemd-journal tux usermod -aG sudo tux </syntaxhighlight> If we want our user to be able to use sudo without a password, run the following commands. <syntaxhighlight lang="bash"> echo "tux ALL=(ALL) NOPASSWD: ALL" | tee /etc/sudoers.d/tux chmod 440 /etc/sudoers.d/tux </syntaxhighlight> == Setup the bootloader == Optional package for extra protection of suspended laptops. <syntaxhighlight lang="bash"> apt install cryptsetup-suspend </syntaxhighlight> Setup encryption parameters. We'll need the encrypted partition's UUID. <syntaxhighlight lang="bash"> blkid -s UUID -o value /dev/nvme0n1p2 </syntaxhighlight> Edit <code>/etc/crypttab</code> and use the UUID from the output of the previous command. <syntaxhighlight> cryptroot UUID=<uuid> none luks </syntaxhighlight> Install the bootloader. <syntaxhighlight lang="bash"> grub-install --target=x86_64-efi --efi-directory=/boot/efi --recheck --bootloader-id="Debian" </syntaxhighlight> Edit <code>/etc/default/grub</code> to include support for encrypted disks. <syntaxhighlight lang="bash"> GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" GRUB_ENABLE_CRYPTODISK=y GRUB_TERMINAL=console </syntaxhighlight> Update the grub configuration. <syntaxhighlight lang="bash"> update-grub </syntaxhighlight> Exit chroot and reboot. <syntaxhighlight lang="bash"> exit umount -lR /mnt reboot </syntaxhighlight> == Emergency recovery from live ISO == In the event of an emergency recovery situation, boot into the live ISO again and run the following commands to mount the encrypted filesystem for maintenance. <syntaxhighlight lang="bash"> sudo -i cryptsetup luksOpen /dev/nvme0n1p2 cryptroot mount -t btrfs -o defaults,subvol=@,compress=zstd:1 /dev/mapper/cryptroot /mnt mount /dev/nvme0n1p1 /mnt/boot/efi mount -t btrfs -o defaults,subvol=@home,compress=zstd:1 /dev/mapper/cryptroot /mnt/home mount -t btrfs -o subvol=@swap /dev/mapper/cryptroot /mnt/swap swapon /mnt/swap/swapfile mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys mount -t proc proc /mnt/proc chroot /mnt </syntaxhighlight> 7d7c887e585a84679e2d879d4ecdb76e62ea2a00 5589 5584 2026-05-29T06:04:10Z Hyperreal 388 Fix syntax highlighting error wikitext text/x-wiki {{GuideWarning}} In this guide, we'll use a Debian Live ISO to do the following: * Create a single LUKS2 encrypted partition. * Create a single Btrfs filesystem with <code>@</code>, <code>@home</code>, <code>@swap</code> and other subvolumes. * Create an encrypted swapfile in the <code>@swap</code> subvolume. * Optional: removal of crypto keys from RAM during laptop suspend * Optional: configurations for laptops == Pre-installation setup == Boot into the live ISO, open a terminal, and become root. Install the needed packages. <syntaxhighlight lang="bash"> sudo -i apt update apt install debootstrap cryptsetup arch-install-scripts </syntaxhighlight> Create partitions. We'll assume the drive we're installing Debian onto is <code>/dev/nvme0n1</code>. <syntaxhighlight lang="bash"> cfdisk /dev/nvme0n1 </syntaxhighlight> In the <code>cfdisk</code> TUI, create the following: * GPT partition table * 512M <code>/dev/nvme0n1p1</code> EFI System Partition (EF00) * 100%+ <code>/dev/nvme0n1p2</code> Linux filesystem Now we'll format the partitions we created. The <code>cryptsetup</code> command will prompt us to enter a secure password for the LUKS2 encrypted partition. <syntaxhighlight lang="bash"> mkfs.fat -F 32 -n EFI /dev/nvme0n1p1 cryptsetup -y -v --type luks2 luksFormat --label Debian /dev/nvme0n1p2 cryptsetup luksOpen /dev/nvme0n1p2 cryptroot mkfs.btrfs /dev/mapper/cryptroot </syntaxhighlight> Now we'll create the Btrfs subvolumes. <syntaxhighlight lang="bash"> mount /dev/mapper/cryptroot /mnt btrfs subvolume create /mnt/@ btrfs subvolume create /mnt/@home btrfs subvolume create /mnt/@swap umount -lR /mnt </syntaxhighlight> Re-mount the subvolumes as partitions. <syntaxhighlight lang="bash"> mount -t btrfs -o defaults,subvol=@,compress=zstd:1 /dev/mapper/cryptroot /mnt mkdir -p /mnt/{boot,home} mkdir /mnt/boot/efi mount /dev/nvme0n1p1 /mnt/boot/efi mount -t btrfs -o defaults,subvol=@home,compress=zstd:1 /dev/mapper/cryptroot /mnt/home </syntaxhighlight> Setup the swap file. <syntaxhighlight lang="bash"> mkdir -p /mnt/swap mount -t btrfs -o subvol=@swap /dev/mapper/cryptroot /mnt/swap touch /mnt/swap/swapfile chmod 600 /mnt/swap/swapfile chattr +C /mnt/swap/swapfile btrfs property set ./swapfile compression none dd if=/dev/zero of=/mnt/swap/swapfile bs=1M count=16384 mkswap /mnt/swap/swapfile swapon /mnt/swap/swapfile </syntaxhighlight> == Base installation == Create a nested subvolume for <code>/var/log</code> under the <code>@</code> subvolume. This will be automounted with <code>@</code> so there is no need to add it to <code>/etc/fstab</code>. Nested subvolumes are not included in snapshots of the parent subvolume. Creating a nested subvolume for <code>/var/log</code> will ensure the log files remain untouched when we restore the rootfs from a snapshot. <syntaxhighlight lang="bash"> mkdir -p /mnt/var btrfs subvolume create /mnt/var/log </syntaxhighlight> Now we'll run <code>debootstrap</code> to bootstrap the base system. We'll use the Trixie release as an example, but we can use any release codename. <syntaxhighlight lang="bash"> debootstrap --arch amd64 trixie /mnt </syntaxhighlight> Bind the pseudo-filesystems for chroot. <syntaxhighlight lang="bash"> mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys mount -t proc proc /mnt/proc </syntaxhighlight> Generate fstab. <syntaxhighlight lang="bash"> genfstab -U /mnt >> /mnt/etc/fstab </syntaxhighlight> Chroot into the new system. <syntaxhighlight lang="bash"> cp -v /etc/resolv.conf /mnt/etc/ chroot /mnt </syntaxhighlight> == Configure the new installation == Set the timezone, locales, keyboard configuration, and console. <syntaxhighlight lang="bash"> apt install locales dpkg-reconfigure tzdata locales keyboard-configuration console-setup </syntaxhighlight> Set the hostname. <syntaxhighlight lang="bash"> echo 'hostname' > /etc/hostname echo '127.0.1.1 hostname.localdomain hostname' >> /etc/hosts </syntaxhighlight> Configure APT sources in <code>/etc/apt/sources.list</code>. * Replace <code>https://deb.debian.org/debian </code> with our desired mirror. * Replace <code>trixie</code> with our desired Debian version name. E.g., <code>bookworm</code>, <code>forky</code>. * Replace <code>main non-free-firmware</code> with the repositories we want. Options include: <code>main</code>, <code>contrib</code>, <code>non-free</code>, <code>non-free-firmware</code>. * The only entry that needs to stay unchanged is the <code>debian-security</code> repository. <syntaxhighlight lang="bash"> deb https://deb.debian.org/debian trixie main non-free-firmware deb https://deb.debian.org/debian trixie-updates main non-free-firmware deb https://deb.debian.org/debian trixie-backports main non-free-firmware deb https://deb.debian.org/debian-security trixie-security main non-free-firmware </syntaxhighlight> Install essential packages. <syntaxhighlight lang="bash"> apt update apt dist-upgrade apt install linux-image-amd64 linux-headers-amd64 firmware-linux firmware-linux-nonfree sudo command-not-found systemd-timesyncd systemd-resolved cryptsetup cryptsetup-initramfs efibootmgr btrfs-progs grub-efi </syntaxhighlight> Install a desktop environment (optional). <syntaxhighlight lang="bash"> apt install task-gnome-desktop task-desktop </syntaxhighlight> If installing on a laptop: <syntaxhighlight lang="bash"> apt install task-laptop powertop </syntaxhighlight> Set the root password. <syntaxhighlight lang="bash"> passwd root </syntaxhighlight> Create users and groups. We'll pretend our user is <code>tux</code> and that they want sudo privileges. <syntaxhighlight lang="bash"> adduser tux usermod -aG systemd-journal tux usermod -aG sudo tux </syntaxhighlight> If we want our user to be able to use sudo without a password, run the following commands. <syntaxhighlight lang="bash"> echo "tux ALL=(ALL) NOPASSWD: ALL" | tee /etc/sudoers.d/tux chmod 440 /etc/sudoers.d/tux </syntaxhighlight> == Setup the bootloader == Optional package for extra protection of suspended laptops. <syntaxhighlight lang="bash"> apt install cryptsetup-suspend </syntaxhighlight> Setup encryption parameters. We'll need the encrypted partition's UUID. <syntaxhighlight lang="bash"> blkid -s UUID -o value /dev/nvme0n1p2 </syntaxhighlight> Edit <code>/etc/crypttab</code> and use the UUID from the output of the previous command. <syntaxhighlight lang="bash"> cryptroot UUID=<uuid> none luks </syntaxhighlight> Install the bootloader. <syntaxhighlight lang="bash"> grub-install --target=x86_64-efi --efi-directory=/boot/efi --recheck --bootloader-id="Debian" </syntaxhighlight> Edit <code>/etc/default/grub</code> to include support for encrypted disks. <syntaxhighlight lang="bash"> GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" GRUB_ENABLE_CRYPTODISK=y GRUB_TERMINAL=console </syntaxhighlight> Update the grub configuration. <syntaxhighlight lang="bash"> update-grub </syntaxhighlight> Exit chroot and reboot. <syntaxhighlight lang="bash"> exit umount -lR /mnt reboot </syntaxhighlight> == Emergency recovery from live ISO == In the event of an emergency recovery situation, boot into the live ISO again and run the following commands to mount the encrypted filesystem for maintenance. <syntaxhighlight lang="bash"> sudo -i cryptsetup luksOpen /dev/nvme0n1p2 cryptroot mount -t btrfs -o defaults,subvol=@,compress=zstd:1 /dev/mapper/cryptroot /mnt mount /dev/nvme0n1p1 /mnt/boot/efi mount -t btrfs -o defaults,subvol=@home,compress=zstd:1 /dev/mapper/cryptroot /mnt/home mount -t btrfs -o subvol=@swap /dev/mapper/cryptroot /mnt/swap swapon /mnt/swap/swapfile mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys mount -t proc proc /mnt/proc chroot /mnt </syntaxhighlight> b848a2b19457a9662f818c5a5fa8efb66a0f7761 3000 1294 5585 5562 2026-05-29T06:00:32Z Hyperreal 388 Fix syntax highlighting error wikitext text/x-wiki {{GuideWarning}} This guide assumes the following are setup already: * DNS pointing to your public web server. * RHEL-compatible distribution is installed to host the RPM repository. * Basic security precautions like Firewall and SSH hardening are in place. * We'll pretend the user is <code>tux</code> and that they have sudo / admin privileges on the host system. * The RPM repository will be stored under <code>/home/tux/rpm-repos</code>. == Install dependencies == <syntaxhighlight lang="bash"> sudo dnf install gnupg createrepo dnf-utils rpm-sign wget </syntaxhighlight> == Setup GnuPG == Replace the values below with your own. <syntaxhighlight lang="bash"> echo "%echo Generating a PGP key Key-Type: RSA Key-Length: 4096 Name-Real: Tux Name-Email: tux@example.com Expire-Date: 0 %no-ask-passphrase %no-protection %commit" > ~/tux-pgp-key.batch </syntaxhighlight> Now generate the key with the following command: <syntaxhighlight lang="bash"> gpg --no-tty --batch --gen-key ~/tux-pgp-key.batch </syntaxhighlight> Export the public key. <syntaxhighlight lang="bash"> gpg --armor --export "Tux" > ~/tux-pgp-key.pub </syntaxhighlight> Export the private key to back it up somewhere safe. <syntaxhighlight lang="bash"> gpg --armor --export-secret-keys "Tux" > ~/tux-pgp-key.sec </syntaxhighlight> After backing up the private key, shred it from the working directory. <syntaxhighlight lang="bash"> shred -xu ~/tux-pgp-key.sec </syntaxhighlight> == Setup RPM signing == Replace <code>E1933532750E9EEF</code> with your key's ID. <syntaxhighlight lang="bash"> echo "%_signature gpg %_gpg_name E1933532750E9EEF" > ~/.rpmmacros </syntaxhighlight> Create a directory to serve the repository. <syntaxhighlight lang="bash"> mkdir -p ~/rpm-repos/packages </syntaxhighlight> Move RPM packages into the <code>~/rpm-repos/packages/</code> directory. Then sign them with the following command. <syntaxhighlight lang="bash"> rpm --addsign ~/rpm-repos/packages/*.rpm </syntaxhighlight> == Create repo index == Once all the packages are signed, create the repository with the following command. This command will create a directory in the repo named <code>repodata</code> containing a file named <code>repomd.xml</code>. <syntaxhighlight lang="bash"> createrepo ~/rpm-repos/packages/ </syntaxhighlight> <blockquote> Note that the <code>createrepo</code> command must be run against each directory in the repo that contains .rpm files. </blockquote> Now sign the repo metadata with the following command. <syntaxhighlight lang="bash"> gpg --detach-sign --armor ~/rpm-repos/packages/repodata/repomd.xml </syntaxhighlight> == Create a .repo file == Create the repo file at <code>~/rpm-repos/tux.repo</code>. <syntaxhighlight lang="ini"> [tux] name=Tux repository $releasever baseurl=https://rpm.example.com/tux/fedora-$releasever/$basearch enabled=1 gpgcheck=1 gpgkey=https://rpm.example.com/tux-pgp-key.pub </syntaxhighlight> The RPM repository should now be ready to be served on a web server with <code>~/rpm-repos</code> as the web root. == Example Caddy configuration == <syntaxhighlight lang="bash"> rpm.example.com { root * /home/tux/rpm-repos/ file_server browse } </syntaxhighlight> e316747ea39d2dd7c505c360d76078d6788d79f1 3000 1271 5586 5499 2026-05-29T06:01:29Z Hyperreal 388 Fix syntax highlighting error wikitext text/x-wiki {{GuideWarning}} == RHEL-like distros with Firewalld == Ensure fail2ban and firewalld are both installed and activated. <syntaxhighlight lang="bash"> sudo dnf install fail2ban firewalld sudo systemctl enable --now firewalld.service sudo systemctl enable --now fail2ban.service </syntaxhighlight> Copy the default <code>jail.conf</code>. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.local</code>. The values below may already be defined in the <code>jail.conf</code> file, so use the text editor's search feature to find them. Make sure they are uncommented. <syntaxhighlight lang="ini"> bantime = 1h findtime = 1h maxretry = 5 </syntaxhighlight> Copy the fail2ban Firewalld configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.d/00-firewalld.conf /etc/fail2ban/jail.d/00-firewalld.local </syntaxhighlight> Edit <code>/etc/fail2ban/jail.d/sshd.local</code>. <syntaxhighlight lang="ini"> [sshd] enabled = true bantime = 1d maxretry = 3 </syntaxhighlight> Restart fail2ban and check the status using the client. <syntaxhighlight lang="bash"> sudo systemctl restart fail2ban.service sudo fail2ban-client status </syntaxhighlight> The output should look like this: <syntaxhighlight lang="bash"> Status |- Number of jail: 1 `- Jail list: sshd </syntaxhighlight> == FreeBSD with PF == Install the fail2ban package. <syntaxhighlight lang="bash"> sudo pkg install py311-fail2ban </syntaxhighlight> Edit <code>/usr/local/etc/fail2ban/jail.local</code>. <syntaxhighlight lang="ini"> [DEFAULT] bantime = 86400 findtime = 3600 maxretry = 3 banaction = pf [sshd] enabled = true </syntaxhighlight> Enable and start fail2ban. <syntaxhighlight lang="bash"> sudo sysrc fail2ban_enable="YES" sudo service fail2ban start </syntaxhighlight> Ensure PF is enabled and started. <syntaxhighlight lang="bash"> sudo sysrc pf_enable="YES" sudo service pf start </syntaxhighlight> Configure <code>/etc/pf.conf</code> <syntaxhighlight lang="bash"> table <fail2ban> persist set skip on lo0 block in all block in quick from <fail2ban> ... </syntaxhighlight> Check and reload the PF rules. <syntaxhighlight lang="bash"> sudo pfctl -nf /etc/pf.conf sudo pfctl -f /etc/pf.conf </syntaxhighlight> a511eeffe49d80848fd0107a2b116b380baacccb 3000 1287 5587 5536 2026-05-29T06:02:33Z Hyperreal 388 Fix syntax highlighting error wikitext text/x-wiki {{GuideWarning}} The following is a collection of ways to get the latest release of a program from its GitHub repository using the command line. The example repositories used below can be replaced with any repository hosted on GitHub. == sed == This gets the URL of the latest release using <code>sed</code>. It then filters out files that contain ".rpm" and ".deb". <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | sed -n 's/.*"browser_download_url": //p' \ | grep -v -E ".rpm|.deb" \ | tr -d '"' </syntaxhighlight> Output: <syntaxhighlight lang="bash"> https://github.com/matheus-git/systemd-manager-tui/releases/download/v1.2.4/systemd-manager-tui </syntaxhighlight> To get the SHA256 digest corresponding to the file, use <code>jq</code> in combination with <code>awk</code>. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | jq -c '.assets.[] | select(.browser_download_url | contains(".deb") or contains(".rpm") | not) | .digest' \ | tr -d '"' \ | awk -F: '{print $2}' </syntaxhighlight> Output: <syntaxhighlight lang="bash"> 63a977112f97462d55a4e41fc0280d32b3f801c3b9f0fad329cd79843c7ae1ec </syntaxhighlight> == jq == If you know that the file you want contains "-en.pyz" in the filename, you can use <code>jq</code> to select it. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' </syntaxhighlight> Output: <syntaxhighlight lang="bash"> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> You can then pipe this to <code>curl</code> via the <code>xargs</code> command to download the file to the current working directory. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' \ | xargs -I {} curl -SL -O {} </syntaxhighlight> == Nushell == <syntaxhighlight lang="nushell"> http get https://api.github.com/repos/9001/copyparty/releases/latest | get assets.browser_download_url | find "-en.pyz" | get 0 </syntaxhighlight> Output: <syntaxhighlight lang="bash"> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> == See Also == * https://gist.github.com/steinwaywhw/a4cd19cda655b8249d908261a62687f8 1b86354415adafefd2c104cbf95cfb4af7a8c862 5588 5587 2026-05-29T06:03:06Z Hyperreal 388 Fix syntax highlighting error wikitext text/x-wiki {{GuideWarning}} The following is a collection of ways to get the latest release of a program from its GitHub repository using the command line. The example repositories used below can be replaced with any repository hosted on GitHub. == sed == This gets the URL of the latest release using <code>sed</code>. It then filters out files that contain ".rpm" and ".deb". <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | sed -n 's/.*"browser_download_url": //p' \ | grep -v -E ".rpm|.deb" \ | tr -d '"' </syntaxhighlight> Output: <syntaxhighlight lang="bash"> https://github.com/matheus-git/systemd-manager-tui/releases/download/v1.2.4/systemd-manager-tui </syntaxhighlight> To get the SHA256 digest corresponding to the file, use <code>jq</code> in combination with <code>awk</code>. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/matheus-git/systemd-manager-tui/releases/latest \ | jq -c '.assets.[] | select(.browser_download_url | contains(".deb") or contains(".rpm") | not) | .digest' \ | tr -d '"' \ | awk -F: '{print $2}' </syntaxhighlight> Output: <syntaxhighlight lang="bash"> 63a977112f97462d55a4e41fc0280d32b3f801c3b9f0fad329cd79843c7ae1ec </syntaxhighlight> == jq == If you know that the file you want contains "-en.pyz" in the filename, you can use <code>jq</code> to select it. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' </syntaxhighlight> Output: <syntaxhighlight lang="bash"> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> You can then pipe this to <code>curl</code> via the <code>xargs</code> command to download the file to the current working directory. <syntaxhighlight lang="bash"> curl -s https://api.github.com/repos/9001/copyparty/releases/latest \ | jq -r '.assets[] | select(.name | contains("-en.pyz")) | .browser_download_url' \ | xargs -I {} curl -SL -O {} </syntaxhighlight> == Nushell == <syntaxhighlight lang="shell"> http get https://api.github.com/repos/9001/copyparty/releases/latest | get assets.browser_download_url | find "-en.pyz" | get 0 </syntaxhighlight> Output: <syntaxhighlight lang="bash"> https://github.com/9001/copyparty/releases/download/v1.20.16/copyparty-en.pyz </syntaxhighlight> == See Also == * https://gist.github.com/steinwaywhw/a4cd19cda655b8249d908261a62687f8 9b349442dfdb8d34f92d86ec087ede715adc6c6e 3000 1270 5590 5538 2026-05-29T06:05:29Z Hyperreal 388 Fix syntax highlighting error wikitext text/x-wiki {{GuideWarning}} This guide is based on the documentation<ref name="pds">[https://github.com/bluesky-social/pds github.com/bluesky-social/pds], GitHub, accessed 2026-05-27</ref><ref>[https://github.com/bluesky-social/deploy-recipes github.com/bluesky-social/deploy-recipes], GitHub, accessed 2026-05-27</ref> from the official Bluesky PDS GitHub repos. <blockquote> CentOS Stream is not an officially supported distribution by the upstream PDS maintainers. </blockquote> == Minimum server requirements == {| class="wikitable" style="margin:auto" |- ! Component !! Requirement |- | OS || CentOS Stream 10 |- | RAM || 1 GB |- | CPU cores || 1 |- | Storage || 20 GB SSD |- | Architectures || amd64, arm64 |- | Number of PDS users || 1-20 |} Ensure we have a firewall installed along with fail2ban (see [[Guides:Fail2ban]]), and that proper security precautions are taken for our server, such as SSH hardening (see [[Guides:Best_SSH_Security_Practices]]). Other requirements: * Public IPv4 address * Public DNS name * Public inbound internet access permitted on port 80/tcp and 443/tcp * A reverse-proxy server, such as Caddy. This guide will use Caddy. Make sure our DNS name is resolvable to our public IPv4 address before proceeding, as it will make testing the PDS easier later on. We'll keep SELinux in enforcing mode and install a policy module to allow the PDS to work. == Preliminary actions == Install Caddy, Podman, and epel-release. <syntaxhighlight lang="bash"> sudo dnf install dnf-plugins-core sudo dnf copr enable @caddy/caddy sudo dnf install '@container-management' caddy epel-release </syntaxhighlight> === SELinux policy module === SELinux is not required, but it is recommended for RHEL-like distributions. To set SELinux in enforcing mode, run the following command with root privileges. <syntaxhighlight lang="bash"> setenforce 1 </syntaxhighlight> To make this persist across reboots, we may need to edit <code>/etc/sysconfig/selinux</code>. Change the <code>SELINUX</code> variable to the value <code>enforcing</code>. <syntaxhighlight lang="bash"> SELINUX=enforcing </syntaxhighlight> We'll also need to install an SELinux policy module so that SELinux doesn't deny the container processes used by the PDS. The following policy module will give the container runtime permissions for creating, locking, reading, writing, and setting attributes on files and directories used by containers, as well as give the containers permission to connect and write to Unix sockets. Create a file named <code>pds.te</code>. <syntaxhighlight lang="shell"> module pds 1.0; require { type container_runtime_t; type var_run_t; type container_t; type default_t; class file { create lock map open read setattr unlink write }; class dir { add_name remove_name write }; class unix_stream_socket connectto; class sock_file write; } # ============= container_t ============== allow container_t container_runtime_t:unix_stream_socket connectto; allow container_t default_t:dir { add_name remove_name write }; allow container_t default_t:file { create lock map open read setattr unlink write }; allow container_t var_run_t:sock_file write; </syntaxhighlight> Compile and install the module. <syntaxhighlight lang="bash"> checkmodule -M -m -o pds.mod pds.te semodule_package -o pds.pp -m pds.mod sudo semodule -i pds.pp </syntaxhighlight> If SELinux still denies some processes, we can check for them with the following command. <syntaxhighlight lang="bash"> sudo ausearch -m avc -ts recent | sudo audit2allow </syntaxhighlight> == Installing the PDS Podman quadlet == The systemd quadlet files are taken from the deploy-recipes repo[]. The only modification I have made is the <code>EnvironmentFile</code> setting. The directory under which we should place these files is <code>/etc/containers/systemd/</code> Create the file <code>/etc/containers/systemd/pds.container</code>. This file defines the main container for the PDS. <syntaxhighlight lang="ini"> [Unit] Description=Bluesky Personal Data Server service Before=caddy.service [Container] Label=app=pds Image=ghcr.io/bluesky-social/pds:0.4 AutoUpdate=registry Pod=pds.pod EnvironmentFile=/etc/pds.env [Install] WantedBy=multi-user.target default.target </syntaxhighlight> Next, create the file <code>/etc/containers/systemd/pds.pod</code>. This file defines the mappings for the PDS volume and published ports. <syntaxhighlight lang="ini"> [Pod] Volume=pds.volume:/pds PublishPort=127.0.0.1:3000:3000 # if you map 3000:3000 instead of 127.0.0.1:3000:3000 # the PDS will be accessible without the reverse proxy. # You probably don't want that! </syntaxhighlight> Finally, create the file <code>/etc/containers/systemd/pds.volume</code>. This file defines the OCI volume used to store the PDS data. <syntaxhighlight lang="ini"> [Unit] Description=Bluesky PDS Volume [Volume] Label=app=pds </syntaxhighlight> These files comprise a systemd quadlet. Quadlets enable Podman containers to run as systemd services. It's a declarative way to configure containers that fits in with the systemd ecosystem. More information on how to configure quadlets can be found at <ref>[https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html podman-systemd.unit], Podman, accessed 2026-05-27</ref>. It's necessary to have all of these files together in the same directory, as they depend on each other. == Setting up pds.env == Here is the default <code>pds.env</code>. We should edit it to our specific needs. <syntaxhighlight lang="bash"> PDS_HOSTNAME=pds.example.com PDS_JWT_SECRET= PDS_ADMIN_PASSWORD= PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX= PDS_DATA_DIRECTORY=/pds PDS_BLOBSTORE_DISK_LOCATION=/pds/blocks PDS_BLOB_UPLOAD_LIMIT=104857600 # if you want to user s3 or compatible, use these variables and comment out DISK_LOCATION PDS_BLOBSTORE_S3_BUCKET=your-bucket-name PDS_BLOBSTORE_S3_ENDPOINT=https://s3.example.com #PDS_BLOBSTORE_S3_FORCE_PATH_STYLE=true # depends on your s3 provider PDS_BLOBSTORE_S3_ACCESS_KEY_ID=your-access-key-id PDS_BLOBSTORE_S3_REGION=your-region PDS_BLOBSTORE_S3_SECRET_ACCESS_KEY=your-secret-key PDS_DID_PLC_URL=https://plc.directory PDS_BSKY_APP_VIEW_URL=https://api.bsky.app PDS_BSKY_APP_VIEW_DID=did:web:api.bsky.app PDS_REPORT_SERVICE_URL=https://mod.bsky.app PDS_REPORT_SERVICE_DID=did:plc:ar7c4by46qjdydhdevvrndac PDS_CRAWLERS=https://bsky.network LOG_ENABLED=true PDS_EMAIL_SMTP_URL= PDS_EMAIL_FROM_ADDRESS= </syntaxhighlight> We should set <code>PDS_JWT_SECRET</code> to a pseudo-random value generated with the following command. <syntaxhighlight lang="bash"> openssl rand --hex 16 </syntaxhighlight> Likewise for <code>PDS_ADMIN_PASSWORD</code> <syntaxhighlight lang="bash"> openssl rand --hex 16 </syntaxhighlight> We'll also need to set <code>PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX</code> to the value generated with the following command. <syntaxhighlight lang="bash"> openssl ecparam --name secp256k1 --genkey --noout --outform DER | tail --bytes=+8 | head --bytes=32 | xxd --plain --cols 32 </syntaxhighlight> As per the <code>EnvironmentFile</code> setting in <code>pds.container</code>, we should store <code>pds.env</code> at <code>/etc/pds.env</code>. == Starting the PDS == The following systemd command will load the files we placed under <code>/etc/containers/systemd/</code> and generate systemd unit files from them. <syntaxhighlight lang="bash"> sudo systemctl daemon-reload </syntaxhighlight> We should now be able to query <code>pds.service</code> by running <code>sudo systemctl status pds.service</code>. Note that it will show the unit as inactive until it is started. Now we can start the units. <syntaxhighlight lang="bash"> sudo systemctl start pds.service </syntaxhighlight> This should pull in the PDS container image from the registry and start it. We can check the status with <code>sudo systemctl status pds.service</code>. == Caddy configuration == A valid Caddy configuration should look like this: <syntaxhighlight lang="shell"> { email myemail@example.com on_demand_tls { ask http://localhost:3000/tls-check } } # PDS *.pds.example.com, pds.example.com { tls { on_demand } reverse_proxy http://localhost:3000 } # Anything else for your server </syntaxhighlight> == pdsadmin.sh == We can create <code>pdsadmin.sh</code> and put it somewhere in our system's binary <code>PATH</code>, such as <code>/usr/local/bin/pdsadmin.sh</code>. <syntaxhighlight lang="bash"> #!/usr/bin/env bash set -o errexit set -o nounset set -o pipefail PDSADMIN_BASE_URL="https://raw.githubusercontent.com/bluesky-social/pds/main/pdsadmin" export PDS_ENV_FILE="/etc/pds.env" # Command to run COMMAND="${1:-help}" shift || true # we don't actually need root here since it only is required # Download the script, if it exists SCRIPT_URL="${PDSADMIN_BASE_URL}/${COMMAND}.sh" SCRIPT_FILE="$(mktemp /tmp/pdsadmin.${COMMAND}.XXXXXX)" if [[ "${COMMAND}" == "update" ]]; then echo "ERROR: self-update not supported via podman" exit 1 fi if ! curl --fail --silent --show-error --location --output "${SCRIPT_FILE}" "${SCRIPT_URL}"; then echo "ERROR: ${COMMAND} not found" exit 2 fi chmod +x "${SCRIPT_FILE}" if "${SCRIPT_FILE}" "$@"; then rm -f "${SCRIPT_FILE}" fi </syntaxhighlight> Make the file executable. <syntaxhighlight lang="bash"> sudo chmod +x /usr/local/bin/pdsadmin.sh </syntaxhighlight> We can now run <code>pdsadmin.sh</code> with no arguments to see usage info. We'll of course need to create an account on our new PDS. == Verifying the PDS is online and accessible == Visit https://your-domain.net/xrpc/_health in the browser. Or run the following command in the terminal. Make sure to replace "your-domain.net" with your actual domain. <syntaxhighlight lang="bash"> curl https://your-domain.net/xrpc/_health </syntaxhighlight> We should receive a JSON response with a version, similar to this. <syntaxhighlight lang="json"> {"version":"0.4.204"} </syntaxhighlight> We'll also need to check that WebSockets are working. We can do this with the <code>wsdump</code> tool. We'll need the latest version of Golang to install it. <syntaxhighlight lang="bash"> sudo dnf install golang go install github.com/nrxr/wsdump@latest </syntaxhighlight> Check if WebSockets are working. <syntaxhighlight lang="bash"> wsdump "wss://your-domain.net/xrpc/com.atproto.sync.subscribeRepos?curosr=0" </syntaxhighlight> Note that there will be no events on the WebSocket until they are created in the PDS, so the above command may continue to run with no output. We'll need to press <code>CTRL-C</code> to stop it. == Closing == That's how to setup a Bluesky PDS on CentOS Stream 10. Additionally, this setup should also work on Almalinux 10, Rocky Linux 10, and Fedora 43, but I haven't tested it on any earlier versions of these distributions. I recommend reading the README.md<ref name="pds" /> for more information on using the <code>pdsadmin</code> command, setting up SMTP, and troubleshooting. == References == <references /> f6ea4d0c77eb602c7f65b199fe44371601538ec6 3000 471 5591 3822 2026-05-29T06:08:32Z Hyperreal 388 Fix syntax highlighting errors wikitext text/x-wiki {{Guide Warning}} The best SSH practices can be summarized into two main principles: # Keeping unauthorized users out of your system. # Making sure potential attackers don't even know your system exists. This guide will teach you the best SSH security practices. === SSH Programs: Dropbear vs OpenSSH === There are two primary SSH programs used on [[Linux Distributions|Linux]]/[[Unix|Unix-based]] systems: '''Dropbear''' and '''OpenSSH'''. In this guide, we will focus on '''OpenSSH'''. === Installing SSH === Installing SSH varies by system. Below are common [[Package Manager|package managers]] where you can download SSH: '''[[Debian]]/[[Ubuntu]]-based systems:'''<syntaxhighlight lang="bash"> sudo apt install openssh-server </syntaxhighlight> [[Red Hat Enterprise Linux|Red Hat]]/[[CentOS]]/[[Fedora]]-based systems: <syntaxhighlight lang="bash">sudo dnf install openssh-server</syntaxhighlight> [[Arch Linux]]-based systems: <syntaxhighlight lang="bash">sudo pacman -S openssh</syntaxhighlight> [[OpenSUSE]]-based systems: <syntaxhighlight lang="bash">sudo zypper install openssh</syntaxhighlight> [[macOS]] (via [[Homebrew]]): <syntaxhighlight lang="bash">brew install openssh</syntaxhighlight> == Securing the OpenSSH Server == === Changing the Port === By default, SSH runs on '''port 22'''. While leaving it on port 22 is acceptable, your system will be easily detected by port scanners as running SSH. To mitigate this, you can change the port. The SSH configuration file is typically located at '''/etc/ssh/sshd_config''' and is usually owned by the root user. To edit it, you must open it as root, using either '''sudo''' or '''doas'''. Once you open the '''sshd_config''' file, you should see the following line: <syntaxhighlight lang="bash">#Port 22</syntaxhighlight> To modify the port, uncomment the line by removing the `#` at the beginning and then change the '''22''' to any number between '''100''' and '''65534'''. You will need to uncomment any line you change for it to come into effect. For example: <syntaxhighlight lang="bash">Port 2345</syntaxhighlight> Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight lang="bash"> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> Once the change is made, you have successfully modified the port. To log in using the new port, use the following command: <syntaxhighlight lang="bash"><username>@<address> -p 2345</syntaxhighlight> === Key Authentication === Key-based authentication is a much safer alternative to using a password. Instead of entering a password to log in, you'll use a key pair: a '''private key''' that stays on your system and a '''public key''' that you store on the server. ==== How Key Authentication Works ==== Imagine you have a door with a lock. The private key is like your physical key, while the public key is the lock on the door. When the correct key is inserted, the door unlocks. This is essentially how key authentication works. * Prevents brute-force attacks. * Allows passwordless login (like Single Sign-On). * Requires each user to have a unique key pair. === Setting up Key Authentication === ==== Generating the Key Files ==== 1. On any Unix/Linux system, type the following command: <syntaxhighlight lang="bash">ssh-keygen</syntaxhighlight> 2. You will be prompted to specify where to save the key files: <syntaxhighlight lang="bash"> Generating public/private ed25519 key pair. Enter file in which to save the key (/home/name/.ssh/id_ed25519): </syntaxhighlight> '''Example:''' <syntaxhighlight lang="bash"> Enter file in which to save the key (/home/name/.ssh/id_ed25519): /home/name/Desktop/key </syntaxhighlight> This will save both the public and private key files on your desktop under the name '''key'''. 3. You will be asked to set a passphrase for the key. If you trust the environment where the key is stored, you can leave it empty by pressing '''Enter'''. Alternatively, you can set a passphrase to add an extra layer of security. <syntaxhighlight lang="bash"> Enter passphrase for "/home/name/Desktop/key" (empty for no passphrase): </syntaxhighlight> 4. Once complete, the keys will be saved in the specified location: <syntaxhighlight lang="bash"> Your identification has been saved in /home/name/Desktop/key Your public key has been saved in /home/name/Desktop/key.pub The key fingerprint is: SHA256:I60X50p2/VwZ6MHhEqx8rWNse0pC5/vewW1i4tLufQ8 name@pc The key's randomart image is: +--[ED25519 256]--+ | | | . | | o . | | .. . = o | | . S+.+ * . | | o.==.+ o +| | . +.oXo.E++| | + o*.=B.=o| | . BOo+oo| +----[SHA256]-----+ </syntaxhighlight> Do not worry about the '''randomart''' as it has no functional purpose. 5. You now have two files: * key – This is your '''private key''' (keep this secure and never share it). * key.pub – This is your '''public key''' (place this on the server). The private key should stay on the machine you will use to access the server. ==== Securing the Server with Key Authentication ==== 1. Log in to the server you want to protect with key authentication. 2. Open the SSH configuration file: <syntaxhighlight lang="bash"> sudo nano /etc/ssh/sshd_config </syntaxhighlight> 3. Modify the following lines: <syntaxhighlight lang="bash"> #PermitRootLogin prohibit-password #PasswordAuthentication yes </syntaxhighlight> to: <syntaxhighlight lang="bash"> PermitRootLogin no PasswordAuthentication no </syntaxhighlight> This prevents root login over SSH, disables password login and forces key-based authentication. 4. Save and exit the file. 5. Go to the home directory of the user you wish to secure with key authentication. Create the '''.ssh''' directory (if it doesn't exist), then create the '''authorized_keys''' file inside it: <syntaxhighlight lang="bash"> mkdir -p ~/.ssh nano ~/.ssh/authorized_keys </syntaxhighlight> Paste the entire contents of the `.pub` file into this document and save it. 6. Restart the SSH service. Use the appropriate command for your system: <syntaxhighlight lang="bash"> sudo systemctl restart sshd # For systems using systemd sudo service ssh restart # For older systems or systems using openrc </syntaxhighlight> '''DO NOT LOG OUT UNTIL YOU CONFRIM THE CONFIGURATION IS CORRECT TO AVOID BEING LOCKED OUT.''' 7. Open another [[TUI|terminal]] window on the machine you will use to SSH into the server and test the connection: <syntaxhighlight lang="bash"> ssh <user>@<address> -i /location/to/private/key/file </syntaxhighlight> If you can log in without a password, the key authentication system is correctly configured! e5e716052a5a8e620a34b889c9260e3afeae7f47 0 158 5592 3593 2026-05-29T06:09:20Z Hyperreal 388 Fix syntax highlighting error wikitext text/x-wiki [[Category:Terminology]] {{Needs Citations}}{{Cleanup|Contrary to the page title, this page does not provide in-depth information for commands}}When using [[Linux]], sooner or later, there's a good chance you'll end up finding yourself in front of a [[TUI|terminal]] and having to paste in or type in things that recommended to you by people on the internet. What you are doing when this happens is running a '''command'''. This is telling a program or utility to behave in a certain way or to perform some sort of action. Some common commands include <code>echo</code>, <code>mv</code>, [[cat|<code>cat</code>]], etc. When running commands, You may have to rely on functions reserved to privileged users. When this happens you will likely start your command with <code>sudo</code> followed with your original command. [[sudo]] tells your computer to ''do'' something as a ''super user'' which will allow you to bypass restrictions. It should be important to note that '''sudo is a separate package''' and may not be pre-installed with certain [[Linux Distributions|distributions]]. If this is the case, you will need to use something like <code>su</code> to log in as root and then run your command as root or install sudo as root. == Useful Commands == Furthermore, with commands you will likely need to include ''options'' that specify to the program how you want it to behave. One of the most common options is <code>--help</code>, which will usually tell program to list all of its options. An example would be as follows: cat --help In this case, the 'cat' utility would respond to this command with the following:<syntaxhighlight lang="bash">Usage: cat [OPTION]... [FILE]... Concatenate FILE(s) to standard output. With no FILE, or when FILE is -, read standard input.   -A, --show-all           equivalent to -vET   -b, --number-nonblank    number nonempty output lines, overrides -n   -e                       equivalent to -vE   -E, --show-ends          display $ at end of each line   -n, --number             number all output lines ...</syntaxhighlight>These options can either mildly or even wildly change the behavior of programs. Unfortunately, options are specific to each program and the options for one program will behave totally different between different programs. Thankfully, <code>--help</code> is always there and ready. If not, you can always run [[man|<code>man</code>]] before a program similarly to how you would run <code>sudo</code>, and it will tell you how these programs behave, usually in a slightly different way. Very often, Commands will also request a file to run its commands on. For example, [[nano]] requires you to choose a file for it to create or edit, and you would provide it in the same line that you run nano on like the following; nano example.txt When providing files you can either choose to provide one from the [[Working Directory|working directory]] (Like shown) or you can provide a file from anywhere in the [[filesystem]] that your user has access to. Here is an example of a command on a file that you want to edit in your documents folder. nano ~/Documents/example.txt The tilda sign <code>~</code>, in Linux and some other [[Operating System|operating systems]], expands to the full [[Directory Path|directory path]] of the current user's home folder. Here is what it would look like to type out the whole path: nano /home/user/Documents/example.txt These two locations are the exact same except one of them is much simpler to type, otherwise they are the same. __INDEX__ __NEWSECTIONLINK__ ceedbb4cb83d19da682df365832747918db9bbdc 3000 701 5593 2685 2026-05-29T06:10:25Z Hyperreal 388 Fix syntax highlighting errors wikitext text/x-wiki Ollama is a runtime for running AI models locally or on a personal server. == Installation == === Official Install Script === curl -fsSL <nowiki>https://ollama.com/install.sh</nowiki> | sh === Arch Linux === ==== No GPU ==== sudo pacman -S ollama ==== ROCm (AMD) ==== sudo pacman -S ollama-rocm ==== CUDA (Nvidia) ==== sudo pacman -S ollama-cuda == Using Models == When picking models, ensure there is enough memory to fit the model you are using. Models small enough to fit in the GPUs memory will only use the GPU while models too big to fit in the GPU will use a mix of GPU and CPU. To check GPU and CPU memory usage run: ollama ps === From Terminal === Gemma 3 will download if not already on the system and then run. ollama run gemma3 Gemma 3 by default uses the 4B version of the model but different versions can be specified. ollama run gemma3:12b Ollama uses q4_K_M quantisation by default but different quantisation level can be specified. ollama run gemma3:12b-it-q8_0 === From a Graphical User Interface === ==== Alpaca ==== Alpaca is officially distributed as a Flatpak. flatpak install flathub com.jeffser.Alpaca Alpaca can be configured to use Ollama externally including remote hosts but can also install Ollama internally as a Flatpak. flatpak install flathub com.jeffser.Alpaca.Plugins.Ollama The Flatpak Ollama plugin can support AMD GPUs using another plugin. flatpal install flathub com.jeffser.Alpaca.Plugins.AMD ==== Visual Studio Code ==== Ollama can be integrated into Visual Studio Code using [https://marketplace.visualstudio.com/items?itemName=Continue.continue Continue]. == Officially Supported GPUs == Consult this [https://github.com/ollama/ollama/blob/main/docs/gpu.md table] for official GPU support. == Use Unsupported AMD GPUs on ROCm == To use ROCm on GPUs not officially supported by Ollama we can extend the Systemd service file with the following command: sudo systemctl edit ollama.service This will open up a file in the systems text editor where you can extend the service. Below are examples of what to add to the file: === Example: Radeon RX 6000 series === <syntaxhighlight lang="ini"> [Service] Environment="HSA_OVERRIDE_GFX_VERSION=10.3.0" </syntaxhighlight> === Example: Radeon RX 5000 series === <syntaxhighlight lang="ini"> [Service] Environment="HSA_OVERRIDE_GFX_VERSION=10.1.0" </syntaxhighlight>The Ollama service will need to be restarted before the GPU can be used. sudo systemctl restart ollama.service d45e8d8f63e32259ba97aca2af8d2f344f2df16c 3000 696 5594 4162 2026-05-29T06:10:52Z Hyperreal 388 Fix syntax highlighting error wikitext text/x-wiki == Using Cinnamon == * Open Start Menu in bottom right corner * Log Out * Click on [[Cinnamon]] Logo next to log In details * Switch to desired [[Window Manager]] == Using i3 == <syntaxhighlight lang="shell"> Mod+shift+e </syntaxhighlight> * Confirm that you want to log out in pop-up * Click on [[i3]] logo next to Log In details * Switch to desired Window Manager == Using XFCE == * Open Start Menu in Top Left corner * Log Out * Click on [[XFCE]] Logo next to log In details * Switch to desired Window Manager == Using MATE == * Open Start Menu in bottom right corner * Log Out * Click on [[MATE]] Logo next to log In details * Switch to desired Window Manager 2fa018aec2e4be0d8ec2b324f8a0bc2dab89f263 2 1209 5595 5037 2026-05-29T06:18:30Z Hyperreal 388 /* Socials */ wikitext text/x-wiki FOSS geek, privacy advocate, digital archivist, gamer, autistic [https://en.wikipedia.org/wiki/Schizotypy schizotype] * GPG: E6AAEAC9BAF03ABE0B0861F6FDBEB7D214D5BBEF * [https://keyoxide.org/hyperreal%40moonshadow.dev Keyoxide] == Web == * Main website: https://moonshadow.dev * Blog: https://blog.moonshadow.dev * Gists: https://gists.moonshadow.dev * Code: https://radicle.defelo.de/nodes/seed.moonshadow.dev * Other code: https://tildegit.org/hyperreal * GitHub: https://github.com/hyperreal64 == Socials == * [https://bsky.app/profile/hyperreal.at.moonshadow.dev Bluesky] * [https://discordapp.com/users/263927928595808257 Discord] * [https://tilde.zone/@hyperreal Fediverse (Mastodon)] * IRC: <code>hyperreal</code> on Libera.chat, tilde.chat, and hackint. * [https://reddit.com/user/SchizoidArchivist Reddit] * [https://signal.me/#eu/UEc0iZQ4f_2sCKN0JPz7DkP48QpdHcU2LENa0dLmbnx4D1XENahJp7q-oaP_gsNS Signal] * [xmpp://hyperreal@tilde.team XMPP] 1804f9b86d5aeb1455f036b5948491b816b3c147 0 625 5596 5443 2026-05-29T12:28:59Z Tungnon1222 314 Cleaned up "default desktop" section wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with Xfce goodies bundle) * [[COSMIC]] (complete COSMIC stack) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options: KDE Plasma, GNOME, Xfce, and COSMIC are more complete compared to other options here while KDE Plasma is the most polished option out of these due to being the distro's default. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] Out of these options: niri and MangoWC are the most usable out of the box. niri comes preconfigured with Noctalia Shell, while MangoWC comes preconfigured with Dank Material Shell. These come with more complete "pseudo desktop experience" than the other options here. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 79487d44384b978da54caf654386fd872894538d 5597 5596 2026-05-29T12:30:10Z Tungnon1222 314 /* Bootloaders */ added explanation about systemd boot wikitext text/x-wiki {{DistributionInfobox | title = CachyOS | image = [[File:CachyOS Logo.svg]] | caption = The CachyOS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64 | website = [https://cachyos.org cachyos.org] }} '''CachyOS''' is an [[Arch Linux]]–based distribution focused on ease of use and performance.<ref name="official-docs" /> It is designed to deliver lightning-fast speeds and stability with a simple graphical installer and multiple desktop environments. The project combines Arch's rolling release model with aggressive compiler and kernel optimisations for modern CPUs. == History == CachyOS was launched in late 2022. It was founded by Peter "ptr1337" Jung and Vladislav "vnepogodin" Nepogodin. The goal is to make Arch Linux more accessible and performance-optimised. The first ISOs were released in 2022. Since then, CachyOS has grown rapidly, releasing monthly snapshots and gaining attention on [[DistroWatch]] and other Linux community sites.<ref name="distrowatch" /> == Philosophy == CachyOS aims to provide a beginner-friendly user experience without sacrificing the flexibility and power of Arch Linux. It retains compatibility with the [[Arch User Repository|AUR]] while focusing on speed, stability, and ease of use. The distribution targets both desktop users and gamers with specialised kernel features and compiled packages optimised for modern CPUs. == Key Features == === Performance-Optimised Kernel === * Multiple kernel variants (`linux-cachyos`) compiled with Clang, LTO, and Propeller optimisations. * CPU-specific builds: x86-64, x86-64-v3, x86-64-v4, and znver4. * Low-latency schedulers: BORE, EEVDF, BMQ. * Support for AMD P-State, kCFI, and other performance patches. === Optimised Package Repositories === * Architecture-specific repos for CPUs supporting advanced instruction sets. * Core packages are rebuilt using high-performance compiler flags like `-O3`, LTO, and AutoFDO. === Custom Toolchain and Build Infrastructure === * Uses Clang or GCC for builds with profile-guided optimisation (PGO). * Enables faster execution of compiled binaries on supported hardware. === Gaming and Multimedia === * Custom [[Proton]] (`proton-cachyos`) and [[Wine]] builds with NTSync and reduced 32-bit overhead. * Steam Deck and ROG Ally patches built into the kernel. * Support for DLSS updates via included “DLSS Swapper” utility. * Out-of-box configuration for gaming performance with schedulers and power profiles. === Additional Utilities === * `pacman-offline` for offline updates. * Graphical kernel manager and “CachyOS-Settings” GUI. * Support for Btrfs snapshots with Limine and GRUB bootloaders out of the box. * Optional Firejail, DNSCrypt, AppArmor hardening. == File Systems == * [[Btrfs]] (default) * [[XFS]] * [[EXT4]] * [[ZFS]] == Bootloaders == CachyOS provides several bootloaders to choose: * [[Limine]] (default + [[Btrfs]] snapshots enabled) * [[systemd-boot]] (shipped with systemd-boot-manager to generate boot entries) * [[GRUB]] ([[Btrfs]] snapshots enabled) * [[rEFInd]] Choosing [[Limine]] or [[GRUB]] alongside [[Btrfs]] as file system will have Btrfs snapshots enabled by default. == Desktop Environments == CachyOS provides several desktop environments during installation: * [[Plasma|KDE Plasma]] (default + preconfigured) * [[GNOME]] (preconfigured) * [[XFCE|Xfce]] (comes with Xfce goodies bundle) * [[COSMIC]] (complete COSMIC stack) * [[Budgie]] * [[Cinnamon]] * [[LXDE]] * [[LXQt]] * [[Mate]] Out of these options: KDE Plasma, GNOME, Xfce, and COSMIC are more complete compared to other options here while KDE Plasma is the most polished option out of these due to being the distro's default. == Window Managers == CachyOS also provides several Window Managers to choose * [[niri]] (preconfigured with [[Noctalia Shell]]) * [[Mangowc]] (preconfigured with [[Dank Materia Shell]]) * [[i3]] (preconfigured) * [[Qtile]] (preconfigured) * [[Wayfire]] (preconfigured) * [[bspwm]] * [[hyprland]] * [[Openbox]] * [[Sway]] Out of these options: niri and MangoWC are the most usable out of the box. niri comes preconfigured with Noctalia Shell, while MangoWC comes preconfigured with Dank Material Shell. These come with more complete "pseudo desktop experience" than the other options here. == Installation == The distribution includes both a graphical ([[Calamares]]) and CLI installer. Key features: * Auto-detection of CPU architecture and optimised repos. * Smooth installation experience designed for newcomers to Arch. * Manual partitioning is available for intermediate or advanced users. == Performance == According to the developers, CachyOS delivers around a 10% performance improvement over generic Arch on supported hardware. Performance benefits vary depending on workload and CPU architecture. Benchmarks show small but consistent speedups in areas like compile times, game frame rates, and load times.<ref name="betanews" /><ref name="reddit-feedback" /> == Hardware Compatibility == CachyOS is tuned for modern hardware, including: * Full support for AMD RDNA4, Intel Arc, NVIDIA RTX 4000/5000 series. * Steam Deck and handheld gaming PCs (e.g., ROG Ally). * Asus Armoury Crate support for fan and power control on gaming laptops. == Comparison to Other Arch-Based Distros == CachyOS shares traits with other Arch derivatives: * Like [[EndeavourOS]], it offers a friendly installer and maintains upstream Arch packages. However, unlike EndeavourOS, CachyOS uses mkinitcpio (much like Arch Linux) while EndeavourOS uses dracut (which is default for Fedora and some other distros). * Unlike [[Manjaro Linux]], it does not delay package updates or curate its own repos. * Similar to [[Garuda Linux]], it emphasises performance but avoids heavy theming. * Compared to pure Arch, it offers much greater ease of installation and setup. == Community and Development == * CachyOS is developed in the open with code hosted on [https://github.com/CachyOS GitHub].<ref name="github-kernel" /> * Communication channels: [https://matrix.to/#/#cachyos:matrix.org Matrix], Telegram, Discord, and forums. * Rolling release model with frequent updates and detailed changelogs. * Supported by Patreon donations ([https://www.patreon.com/CachyOS patreon.com/CachyOS]). == See Also == * [[Arch Linux]] * [[EndeavourOS]] * [[Garuda Linux]] * [[Manjaro Linux]] == References == <references><ref name="github-kernel">[https://github.com/CachyOS/linux-cachyos GitHub - CachyOS/linux-cachyos: Archlinux Kernel based on different schedulers and some other performance improvements.], CachyOS, 2025-08-09 (Accessed: 2025-08-09)</ref> <ref name="official-docs">[https://wiki.cachyos.org Welcome to the CachyOS Wiki], CachyOS Wiki, 2024-08-30 (Accessed: 2025-08-09)</ref> <ref name="distrowatch">[https://distrowatch.com/table.php?distribution=cachyos <span style="color:#fc493b">https://distrowatch.com/table.php?distribution=cachyos <sup>🍣403]</ref> <ref name="betanews">[https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <span style="color:#fc493b">https://betanews.com/2023/01/02/cachyos-linux-performance-arch/ <sup>🍣404]</ref> <ref name="reddit-feedback">[https://www.reddit.com/r/linux/comments/12trf3b/cachyos_performance_benchmark_feedback/ Reddit user feedback and benchmarks (404)]</ref></references> 853be86ff756c31c50388888b990e2eb20777b1a 0 217 5598 5379 2026-05-29T13:02:33Z Atmois 13 Remove tags and remove uncessary line wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Stable Release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022-04-21 (Accessed: 2025-09-03)</ref> |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}} [[Category:Linux Distributions]] [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is a community maintained [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref>, sponsored primarily by [[Red Hat]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> and developed by the Fedora Project. The Fedora Project was formed in 2003<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux originally began as the Fedora Project, a community maintained repository of additional software packages for Red Hat Linux (RHL).<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> The project was founded in 2002 by University of Hawaii computer science student Warren Togami.<ref>[https://fedoraproject.org/wiki/User:Wtogami Fedora Project], Warren Togami, 2009-04-14 (Accessed: 2026-05-25)</ref> Around the same time, Red Hat was shifting its focus toward the enterprise market with the introduction of Red Hat Enterprise Linux (RHEL). By 2003 demand for RHEL was increasing and Red Hat recognized growing confusion between Red Hat Linux and Red Hat Enterprise Linux due to their similar naming and overlapping purpose.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> With the growing popularity of the Fedora Project repository, Red Hat made the decision to discontinue Red Hat Linux in order to focus its internal resources on RHEL, while also becoming the primary corporate sponsor of the newly established Fedora Project.<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> As part of this transition, Fedora evolved from a repository project into its own community maintained Linux distribution with the release of Fedora Core 1 in November 2003.<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref> With this new relationship established, Fedora Linux became Red Hat’s upstream community distribution, where new software and technologies were introduced and refined before later being adopted into RHEL and eventually, CentOS Stream. Fedora continues to have a reputation for rapidly adopting new technologies and features, making it a popular choice among Linux developers and enthusiasts who want well supported and up-to-date software.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> == Release system == Fedora currently follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], '''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</ref> System upgrades are usually handled offline to prevent system breakage == The package management system == The main package manager is [[dnf]], which is usually called with the following arguments: {| class="wikitable" |+ <code>dnf</code> Usage |- ! Command !! Description |- | <code>sudo dnf up</code> || updates system packages |- | <code>sudo dnf in <pkg names> <...></code> || install new packages |- | <code>sudo dnf rm <pkg names> <...></code> || remove packages |- | <code>sudo dnf system-upgrade --relesever=<rel></code> || updates system version and packages<ref>[https://dnf.readthedocs.io/ DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</ref> |} == References == <references /> 8490b09ee6121d8253ada167e544e7d486495b16 5599 5598 2026-05-29T13:03:29Z Atmois 13 Atmois moved page [[Fedora]] to [[Fedora Linux]]: Incorrect Name wikitext text/x-wiki {{DISPLAYTITLE:Fedora Linux}}{{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Stable Release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022-04-21 (Accessed: 2025-09-03)</ref> |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}} [[Category:Linux Distributions]] [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is a community maintained [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref>, sponsored primarily by [[Red Hat]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> and developed by the Fedora Project. The Fedora Project was formed in 2003<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux originally began as the Fedora Project, a community maintained repository of additional software packages for Red Hat Linux (RHL).<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> The project was founded in 2002 by University of Hawaii computer science student Warren Togami.<ref>[https://fedoraproject.org/wiki/User:Wtogami Fedora Project], Warren Togami, 2009-04-14 (Accessed: 2026-05-25)</ref> Around the same time, Red Hat was shifting its focus toward the enterprise market with the introduction of Red Hat Enterprise Linux (RHEL). By 2003 demand for RHEL was increasing and Red Hat recognized growing confusion between Red Hat Linux and Red Hat Enterprise Linux due to their similar naming and overlapping purpose.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> With the growing popularity of the Fedora Project repository, Red Hat made the decision to discontinue Red Hat Linux in order to focus its internal resources on RHEL, while also becoming the primary corporate sponsor of the newly established Fedora Project.<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> As part of this transition, Fedora evolved from a repository project into its own community maintained Linux distribution with the release of Fedora Core 1 in November 2003.<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref> With this new relationship established, Fedora Linux became Red Hat’s upstream community distribution, where new software and technologies were introduced and refined before later being adopted into RHEL and eventually, CentOS Stream. Fedora continues to have a reputation for rapidly adopting new technologies and features, making it a popular choice among Linux developers and enthusiasts who want well supported and up-to-date software.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> == Release system == Fedora currently follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], '''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</ref> System upgrades are usually handled offline to prevent system breakage == The package management system == The main package manager is [[dnf]], which is usually called with the following arguments: {| class="wikitable" |+ <code>dnf</code> Usage |- ! Command !! Description |- | <code>sudo dnf up</code> || updates system packages |- | <code>sudo dnf in <pkg names> <...></code> || install new packages |- | <code>sudo dnf rm <pkg names> <...></code> || remove packages |- | <code>sudo dnf system-upgrade --relesever=<rel></code> || updates system version and packages<ref>[https://dnf.readthedocs.io/ DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</ref> |} == References == <references /> 8490b09ee6121d8253ada167e544e7d486495b16 5601 5599 2026-05-29T13:03:42Z Atmois 13 Remove redundant title wikitext text/x-wiki {{DistributionInfobox |title=Fedora Linux |image=[[File:Fedora logo.svg|Fedora_logo|frameless]] |caption=The Fedora Linux logo |releasestatus=Maintained |releasemodel=Stable Release<ref>[https://docs.fedoraproject.org/en-US/releases/ Fedora Linux Releases], Fedora Docs, 2022-04-21 (Accessed: 2025-09-03)</ref> |packagemanager=[[dnf]], [[rpm]] |defaultdesktops = Budgie, Cinnamon, [[i3]], Sway, GNOME, [[KDE Plasma]], LXDE, LXQt, MATE, [[Xfce]], Cosmic |usagetype=Desktop, Server, Cloud |architectures = aarch64, x86_64, ppc64le, s390x |website=[https://fedoraproject.org/ fedoraproject.org]|Current version=f42}} [[Category:Linux Distributions]] [[File:Fedora Workstation 40.png|thumb|Fedora Workstation 40 running GNOME]] '''Fedora Linux''' is a community maintained [[Linux Distributions|Linux Distribution]]<ref>[https://fedoraproject.org/wiki/FAQ#Is_the_Fedora_Project_independent_of_Red_Hat.2C_Inc..3F fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref>, sponsored primarily by [[Red Hat]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/#_relationship_between_fedora_and_rhel fedora quick docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> and developed by the Fedora Project. The Fedora Project was formed in 2003<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> after the decision of splitting Red Hat Linux into an enterprise model operating system called [[RHEL|Red Hat Enterprise Linux]] (RHEL) and a community based operating system, known as Fedora Linux. The first version of Fedora, called ''Fedora Core 1'' was released on November 6, 2003<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref>. Fedora Linux is built with the vision "where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities."<ref>[https://docs.fedoraproject.org/en-US/project/#_our_vision fedora docs], Fedora Council et al., 2025 (Accessed: August 9, 2025)</ref> === History === Fedora Linux originally began as the Fedora Project, a community maintained repository of additional software packages for Red Hat Linux (RHL).<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> The project was founded in 2002 by University of Hawaii computer science student Warren Togami.<ref>[https://fedoraproject.org/wiki/User:Wtogami Fedora Project], Warren Togami, 2009-04-14 (Accessed: 2026-05-25)</ref> Around the same time, Red Hat was shifting its focus toward the enterprise market with the introduction of Red Hat Enterprise Linux (RHEL). By 2003 demand for RHEL was increasing and Red Hat recognized growing confusion between Red Hat Linux and Red Hat Enterprise Linux due to their similar naming and overlapping purpose.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> With the growing popularity of the Fedora Project repository, Red Hat made the decision to discontinue Red Hat Linux in order to focus its internal resources on RHEL, while also becoming the primary corporate sponsor of the newly established Fedora Project.<ref>[https://web.archive.org/web/20031001204515/http://www.fedora.us/ Announcement: Red Hat Linux Merging with Fedora Linux], Fedora Project, 2003-09-22 (Accessed: 2003-10-01)</ref> As part of this transition, Fedora evolved from a repository project into its own community maintained Linux distribution with the release of Fedora Core 1 in November 2003.<ref>[https://web.archive.org/web/20201129041529/https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html Announcing Fedora Core 1], Bill Nottingham, 2003-11-06 (Accessed: 2020-01-12)</ref> With this new relationship established, Fedora Linux became Red Hat’s upstream community distribution, where new software and technologies were introduced and refined before later being adopted into RHEL and eventually, CentOS Stream. Fedora continues to have a reputation for rapidly adopting new technologies and features, making it a popular choice among Linux developers and enthusiasts who want well supported and up-to-date software.<ref>[https://fedoramagazine.org/the-fedora-project/ Fedora Magazine], Abdel El Aoami, 2025-04-21 (Accessed: 2026-05-25)</ref> == Release system == Fedora currently follows a system where a new version is released every 6 months<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], '''Fedora''' Engineering Steering Committee(fesco) & Fedora Packaging Committee(fpc), 2025 (Accessed: August 9, 2025)</ref>, which brings breaking changes, such as major library versions.<ref>[https://docs.fedoraproject.org/en-US/releases/lifecycle/ Fedora Packaging documentation], (fesco) & (fpc), 2025 (Accessed: August 9, 2025)</ref> System upgrades are usually handled offline to prevent system breakage == The package management system == The main package manager is [[dnf]], which is usually called with the following arguments: {| class="wikitable" |+ <code>dnf</code> Usage |- ! Command !! Description |- | <code>sudo dnf up</code> || updates system packages |- | <code>sudo dnf in <pkg names> <...></code> || install new packages |- | <code>sudo dnf rm <pkg names> <...></code> || remove packages |- | <code>sudo dnf system-upgrade --relesever=<rel></code> || updates system version and packages<ref>[https://dnf.readthedocs.io/ DNF documentaion], rpmsoftware, 2025 (Accessed: August 9, 2025)</ref> |} == References == <references /> 2b3ee142bcc6f2393de5938851b7c30709a3dd6b 0 1301 5600 2026-05-29T13:03:29Z Atmois 13 Atmois moved page [[Fedora]] to [[Fedora Linux]]: Incorrect Name wikitext text/x-wiki #REDIRECT [[Fedora Linux]] e15805633a8374d00cb3bb56c09b626441249ed2 0 203 5602 4647 2026-05-29T14:13:21Z Larry the cow 402 Cleaned up some sections and added recommendations to consult official Gentoo documentation for ie. install and portage usage. Not a major edit, not a minor edit, somewhere inbetween. wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [https://wiki.gentoo.org/wiki/Portage portage] | defaultdesktops = None, User Choice | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in 2000 by [[Daniel Robbins]].<ref>[https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer) Daniel Robbins (computer programmer)], Wikipedia contributors, 2024-01-10 (Accessed: 2025-08-09)</ref> Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to customize their system to a degree way beyond other distributions by providing granular control over system packages and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This approach, while more time-consuming than other distributions due to it's complexity, enables optimizations specific to the user's hardware and requirements. A common myth says that a user must compile everything in '''Gentoo''' or that the [https://wiki.gentoo.org/wiki/Project:Binhost Project:Binhost] is anti-Gentoo. The irony being that Gentoo was created to be all about user choice, and all the binhost provides is a choice to its users. Using the binhost doesn't prevent a user from compiling the packages they want to modify, as both binary and source-built packages can coexist seamlessly. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements and runs on nearly anything you throw it at although some lesser used architectures will not have binaries. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "[https://wiki.gentoo.org/wiki/SLOT slotting]". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. Users who want to install Gentoo are recommended to consult the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook] which has up-to-date information about Installation, Working with Gentoo, Working with Portage, and Gentoo network configuration for a variety of system architectures. Unlike other Linux distributions, Gentoo is made to be installable from any installation environment, although the Handbook recommends using a Gentoo live environment. Gentoo provides both a minimal .iso without only a command line, and a LiveGUI with KDE Plasma. From this live environment, the user will configure disks and network before loading in a stage file to act as a seed for the Gentoo install. Later the user has to configure and install a Gentoo base system, a Linux kernel, system tooling, base configuration files, user accounts, and a bootloader. == Package Management == === Portage === [https://wiki.gentoo.org/wiki/Portage Portage] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration. Portage consists of 15 different tools, though only 3 of which - emerge, emaint, and dispatch-conf - are typically used for day-to-day maintenance. Portage is at the core of every Gentoo installation, providing advanced dependency resolution, and flexible building and installing of software both from source and from a binary package host. Inspired by the [https://en.wikipedia.org/wiki/Ports_collection ports collections]-concepts of the BSDs, Portage is extremely flexible and can also run on other distributions and operative systems, among others [https://www.gentoo.org/news/2026/04/01/gentoo-hurd.html GNU/Hurd] and [https://wiki.gentoo.org/wiki/Gentoo_FreeBSD FreeBSD]. ==== Common Usage ==== ''For detailed and up-to-date information, please refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook] and other relevant documentation.'' {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge --ask --update --deep --newuse @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge --ask package</code> | Install a package |- | <code>emerge --deselect package</code> | Remove a package from the [https://wiki.gentoo.org/wiki/Selected_set_(Portage) selected set] |- | <code>emerge --pretend --verbose package</code> | Preview package installation |- | <code>emerge --depclean</code> | Remove unneeded packages |- |<code>emerge --unmerge / emerge -C</code> |'''Do not use unless you know what you are doing''' removes a package without checking dependencies even core system packages |- |<code>emerge --pretend --verbose --depclean package</code> |Check what depends on package |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. This is done through [https://wiki.gentoo.org/wiki/USE_flag USE flags]. USE flags work by configuring '''Portage''' to decide how each package is to be installed and updated, and are a core feature of how Gentoo users can customize their installation. USE flags can also be used to include or exclude certain features from packages by omitting them at compile time. USE flags can be set both individually per package and through <code>package.use</code>, as detailed on the Gentoo wiki. === Binary Packages === Gentoo offers binaries like any other distribution but it needs to be explicitly enabled. Refer to the [https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart Binary Host Quickstart guide] for detailed information == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === Gentoo has several community resources. The official community wiki and forums can be found at [https://wiki.gento.org https://wiki.gento.org] and [https://forums.gentoo.org/ forums.gentoo.org/] respectively. There is also a bug tracking system at [https://bugs.gentoo.org/ https://bugs.gentoo.org/] Gentoo also has several public [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] both for general use and for specific topics. For live communication there are official IRC<ref>Internet Relay Chat</ref> [https://wiki.gentoo.org/wiki/IRC channels]. === Development Model === '''Gentoo''' is developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the user base through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == Compared to other distributions, '''Gentoo''' is a considered user-centric, Do-It-Yourself distribution that allows maximum customization and optimal performance through compilation and complete control over features. Gentoo also has extensive documentation, active community support, and also ability to use binaries. This comes with the downside of a steep learning curve, requiring more knowledge about which components a system needs to function, and a much longer and more tedious install process. While this is great for some users, others might prefer a more out-of-the-box experience provided by more user-friendly distributions such as [[Linux Mint]]. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://wiki.gentoo.org/wiki/Portage Portage] * [https://planet.gentoo.org/ Gentoo Planet] 944e6f705aebd9cf1bc2c4997db08a2bddffeead 1 1302 5603 2026-05-29T14:17:31Z Larry the cow 402 /* Made some changes - unsure about all formatting rules [29.05] */ new section wikitext text/x-wiki == Made some changes - unsure about all formatting rules [29.05] == Hi, Did a few changes and some cleanup today (view commit for 29.05.2026). Unsure about all the formatting rules (ie. with when to and when not to highlight. The most important thing I did was simplify sections and add some extra reminders to refer to official documentation. I think this is very important for an advanced distribution such as Gentoo, as official docs will always(1) be better and more up-to-date than these ones :) (1) provided that people commit new information to 'upstream' instead of just writing it somewhere else, that is Best of wishes ^^ [[User:Larry the cow|Larry the cow]] ([[User talk:Larry the cow|talk]]) 14:17, 29 May 2026 (UTC) 115214d6a3b0c8f1c2f56b4f00174f1ce2560b38 0 198 5604 5338 2026-05-29T16:42:18Z BlankedBlaze 411 /* Gentoo Family */ Added Fyde OS and description. wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[https://fydeos.io/ FydeOS] |A cloud-focused OS built on open-source ChromiumOS for use on multiple systems and architectures. It adds broad device support and custom Android/Linux environments, utilizing the Gentoo build system. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 1e0df542b0f519f738cd3c83438adb6dbc6c3a68 5605 5604 2026-05-29T16:56:45Z BlankedBlaze 411 wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |openFyde |A cloud-focused OS built on open-source ChromiumOS for use on multiple systems and architectures. It adds broad device support and custom Android/Linux environments, utilizing the Gentoo build system. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 47daa4856b147efad81846ffc5ca11c598e401b5 5606 5605 2026-05-29T17:04:19Z BlankedBlaze 411 switched with original Fyde and went to openfyde (Update not finished.) wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |openFyde |A fully open-source fork of FydeOS. It strips out proprietary drivers and commercial patches to provide a completely open-source, decoupled ChromiumOS experience. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 93d357b322fc3639d1b01d7bd251c3de82b6c7b3 5609 5606 2026-05-29T19:05:31Z BlankedBlaze 411 Made a Page for openFyde wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[openFyde]] |A fully open-source fork of FydeOS. It strips out proprietary drivers and commercial patches to provide a completely open-source, decoupled ChromiumOS experience. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == e63d9a4fcf437dce5e14892c065f6cb87c23dbb7 2 1303 5607 2026-05-29T17:19:50Z BlankedBlaze 411 My user Page wikitext text/x-wiki Linage OS user, Fan of Obtanium, and Proud owner of ADHD & Autism. Mostly Uses Arch (CachyOS) and I'm forcing myself to relearn Linux Mint. Main Page: Drift.rip/BlankedBlaze 854143c8c60a6c1a46167f09d594eaeb89fcc7f6 5608 5607 2026-05-29T17:33:38Z BlankedBlaze 411 Links added wikitext text/x-wiki Linage OS user, Fan of Obtainium, and Proud owner of [https://health.clevelandclinic.org/audhd AuDHD] Mostly Uses Arch [[Linux Distributions|Distro's]] ([[CachyOS]]) and I'm forcing myself to relearn [[Linux Mint]]. Main Page: [https://Drift.rip/BlankedBlaze Drift.rip/BlankedBlaze] 8238966f6c7894d0710b76a14f16a90a67147631 0 667 5610 5465 2026-05-29T22:37:12Z Realsteel99 412 added some stuff on history wikitext text/x-wiki {{Cleanup|Incomplete page, horribly out of date}} '''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. Examples of modern UNIX-based systems include MacOS and IBM AIX. The owner of the UNIX® trademark has been The Open Group since 1994.<ref>[https://unix.org/what_is_unix.html What is UNIX ®?]{{Dead Link|2026-05-26|404}} unix.org</ref> == History == === Origins === The history of UNIX begins in the mid-1960s when MIT, General Electric, and Bell labs were developing a new experimental operating system utilizing time-sharing called Multics, designed for the GE-645 mainframe computer. <ref>https://www.redhat.com/en/blog/unix-linux-history</ref> The project had many unique and beneficial new technologies, but also had severe problems. Bell labs pulled out of the project, citing its bloat and complexity. After being frustrated by Multics but inspired by its concepts, Ken Thompson and Dennis Ritchie wanted to build a much simpler, light operating system based on the rarely used DEC PDP-7 minicomputer. In the summer of 1969, Thompson wrote the initial kernel, shell, and editor, birthing "Unics"(more commonly known today as Unix.) Originally written in assembly, it was ported to C in 1973, making it highly portable and easily moved across vastly different architectures.<ref>https://www.nokia.com/bell-labs/about/history/innovation-stories/50-years-unix/</ref> === Branching === Because AT&T, the parent company of Bell Labs, was not allowed to enter the computer business due to antitrust laws, the operating system source code was licensed to universities for a nominal fee. With AT&T unable to support Unix, early Unix adopters worked together for assistance, forming a network of groups across the globe. In the mid-1970s, Ken Thompson temporarily left Bell labs and taught a course on Unix at the University of California. Students and teachers there further modified Unix, eventually creating a separate branch known as BSD(Berkeley Software Distribution). Back at AT&T, development continued, culminating in the 1983 release of a new release of Unix, Unix System V.<ref>https://www.britannica.com/technology/UNIX</ref> == References == 841e629ee2528faf2899291f7ffbec59261aeb4b 5611 5610 2026-05-29T22:44:15Z Realsteel99 412 /* Branching */ wikitext text/x-wiki {{Cleanup|Incomplete page, horribly out of date}} '''Unix''' is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. Examples of modern UNIX-based systems include MacOS and IBM AIX. The owner of the UNIX® trademark has been The Open Group since 1994.<ref>[https://unix.org/what_is_unix.html What is UNIX ®?]{{Dead Link|2026-05-26|404}} unix.org</ref> == History == === Origins === The history of UNIX begins in the mid-1960s when MIT, General Electric, and Bell labs were developing a new experimental operating system utilizing time-sharing called Multics, designed for the GE-645 mainframe computer. <ref>https://www.redhat.com/en/blog/unix-linux-history</ref> The project had many unique and beneficial new technologies, but also had severe problems. Bell labs pulled out of the project, citing its bloat and complexity. After being frustrated by Multics but inspired by its concepts, Ken Thompson and Dennis Ritchie wanted to build a much simpler, light operating system based on the rarely used DEC PDP-7 minicomputer. In the summer of 1969, Thompson wrote the initial kernel, shell, and editor, birthing "Unics"(more commonly known today as Unix.) Originally written in assembly, it was ported to C in 1973, making it highly portable and easily moved across vastly different architectures.<ref>https://www.nokia.com/bell-labs/about/history/innovation-stories/50-years-unix/</ref> === Branching === Because AT&T, the parent company of Bell Labs, was not allowed to enter the computer business due to antitrust laws, the operating system source code was licensed to universities for a nominal fee. With AT&T unable to support Unix, early Unix adopters worked together for assistance, forming a network of groups across the globe. In the mid-1970s, Ken Thompson temporarily left Bell labs and taught a course on Unix at the University of California. Students and teachers there further modified Unix, eventually creating a separate branch known as BSD(Berkeley Software Distribution). Back at AT&T, development continued, culminating in the 1983 release of a new release of Unix, Unix System V.<ref>https://www.britannica.com/technology/UNIX</ref> Throughout the 1980s, multiple major tech companies licensed Unix to run on their proprietary hardware, fracturing the market into various incompatible flavors, such as IBM's AIX, Sun Microsystem's SunOS(later known as Solaris), and HP's HP-UX. == References == 1c8804509d41490bb5f7103974460d86220a7203 0 1232 5612 5371 2026-05-29T23:23:47Z Imnotgoodatnames 121 changed the emacs source link from the github mirror to the savannah git repo wikitext text/x-wiki Commonly-used free and open source text editing [[software]] on [[Linux]]. = Text editors = {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[Gram]] |[https://gram-editor.com/ Website], [https://codeberg.org/GramEditor/gram CodeBerg] |A code editor that started as a fork of [[Zed]] to remove AI and avoid agreeing to the Zed terms of use |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://cgit.git.savannah.gnu.org/cgit/emacs.git Source] |An extensible, customizable, free/libre text editor — and more. |- |[[Pulsar]] |[https://pulsar-edit.dev/ Website], [https://github.com/pulsar-edit/pulsar GitHub] |A community-led, hyper-hackable text editor. Pulsar is a fork of the discontinued [[Atom]] editor |- |[[Atom]] |[https://atom.io/ Website], [https://github.com/atom/atom GitHub] |The hackable text editor. A discontinued GitHub developed editor |- |[[Lite XL]] |[https://lite-xl.com/ Website], [https://github.com/lite-xl/lite-xl GitHub] |A lightweight text editor written in Lua |- |[[Pragtical]] |[https://pragtical.dev/ Website], [https://github.com/pragtical/pragtical GitHub] |The practical and pragmatic code editor. Fork of [[Lite XL]] |- |[[Lapce]] |[https://lap.dev/lapce/ Website], [https://github.com/lapce/lapce GitHub] |Lightning-fast and Powerful Code Editor written in Rust |- |} == Terminal-based text editors == These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[Nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[Vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[Vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[Neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://github.com/emacs-mirror/emacs GitHub] |An extensible, customizable, free/libre text editor — and more. |- |[[Helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |- |[[Flow Control]] |[https://flow-control.dev/ Website], [https://github.com/neurocyte/flow GitHub] |TUI editor written in Zig with multiple keybinding modes |- |[[Edit]] |[https://learn.microsoft.com/en-us/windows/edit/ Website], [https://github.com/microsoft/edit GitHub] |Simple Microsoft developed command-line text editor |- |} = Integrated development environments (IDEs) = IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} d4c0e61c119e80a27a87d49f14b853f8fb9536fc 5613 5612 2026-05-29T23:35:09Z Imnotgoodatnames 121 wikitext text/x-wiki Commonly-used free and open source text editing [[software]] on [[Linux]]. = Text editors = {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[Gram]] |[https://gram-editor.com/ Website], [https://codeberg.org/GramEditor/gram CodeBerg] |A code editor that started as a fork of [[Zed]] to remove AI and avoid agreeing to the Zed terms of use |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://cgit.git.savannah.gnu.org/cgit/emacs.git Source] |An extensible, customizable, free/libre text editor — and more. |- |[[Pulsar]] |[https://pulsar-edit.dev/ Website], [https://github.com/pulsar-edit/pulsar GitHub] |A community-led, hyper-hackable text editor. Pulsar is a fork of the discontinued [[Atom]] editor |- |[[Atom]] |[https://atom.io/ Website], [https://github.com/atom/atom GitHub] |The hackable text editor. A discontinued GitHub developed editor |- |[[Lite XL]] |[https://lite-xl.com/ Website], [https://github.com/lite-xl/lite-xl GitHub] |A lightweight text editor written in Lua |- |[[Pragtical]] |[https://pragtical.dev/ Website], [https://github.com/pragtical/pragtical GitHub] |The practical and pragmatic code editor. Fork of [[Lite XL]] |- |[[Lapce]] |[https://lap.dev/lapce/ Website], [https://github.com/lapce/lapce GitHub] |Lightning-fast and Powerful Code Editor written in Rust |- |} == Terminal-based text editors == These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[Nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[Vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[Vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[Neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://cgit.git.savannah.gnu.org/cgit/emacs.git Source] |An extensible, customizable, free/libre text editor — and more. |- |[[Helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal unlike Vi. |- |[[Flow Control]] |[https://flow-control.dev/ Website], [https://github.com/neurocyte/flow GitHub] |TUI editor written in Zig with multiple keybinding modes |- |[[Edit]] |[https://learn.microsoft.com/en-us/windows/edit/ Website], [https://github.com/microsoft/edit GitHub] |Simple Microsoft developed command-line text editor |- |} = Integrated development environments (IDEs) = IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} 8a881bb278519d9734c0690551911d758cd82620 1 1304 5614 2026-05-30T02:45:15Z Hyperreal 388 /* GenAI? */ new section wikitext text/x-wiki == GenAI? == This content looks like it was generated with AI, based on the structure. Can anyone verify if this is true or not? From a cursory inspection it looks pretty accurate, but I'd be happy to go over it with a fine-toothed comb to ensure accuracy. I can also separate the Getting Started with Systemd section and below into its own guide. [[User:Hyperreal|Hyperreal]] ([[User talk:Hyperreal|talk]]) 02:45, 30 May 2026 (UTC) 0e9c0e24fb6d73066f4aa1c5011b93167866946a 0 534 5615 5458 2026-05-30T04:07:06Z Int 401 Fix citations and dead links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Nirilogo.svg|300px|example_niri_rice]] | caption = Niri's logo | title = niri | releasestatus = Maintained | firstrelease = v0.1.0-alpha.1 (2023) | lastrelease = v26.04 | languages = [[Rust]] | developers = Ivan Molodetskikh (YaLTeR) | website = https://github.com/YaLTeR/niri }} [[File:Niri Rice.png|thumb|A desktop running Niri]] Niri is a scrollable tiling [[Wayland]] compositor heavily inspired by [[PaperWM]]<ref name=":0">{{Cite|title=Niri GitHub repository|url=https://github.com/YaLTeR/niri|accessdate=30 May 2026}}</ref>. Windows are arranged in columns on an infinite strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor<ref name=":0" />. Workspaces are dynamic and arranged vertically, and every monitor has an independent set of workspaces. There's always one empty workspace all the way down, similar to how [[GNOME]] works. When a monitor disconnects, its workspaces will move to another monitor, but upon re-connection they will move back to the original monitor.<ref name=":0" /> == Features == Notable features of Niri include:<ref name=":1">{{Cite|url=https://github.com/YaLTeR/niri/wiki/Important-Software|title=Important Software - Niri GitHub wiki|accessdate=30 May 2026}}</ref> * Dynamic workspaces similar to GNOME * [https://github.com/niri-wm/niri/wiki/Overview Overview] for managing workspaces * Built-in screenshot utility * [https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules#block-out-from Block out] sensitive windows from screencasting * [https://github.com/niri-wm/niri/wiki/Gestures Touchpad and mouse gestures] * Tiling and [https://github.com/niri-wm/niri/wiki/Floating-Windows floating] window modes * Customizable borders, animations, and overall look and feel * Configuration live-reloading * Compatibility with [[X11]] applications via [[XWayland]] == References == <references /> 5141e9a6f2d79643f7dcccef00d5753b56439fad 0 628 5617 5099 2026-05-30T11:11:04Z Wilbur 142 fix wrong link wikitext text/x-wiki {{DistributionInfobox | title = Linux Mint | image = [[File:Linuxmint-logo.png|Linux Mint logo]] | caption = The Linux Mint logo | releasestatus = Maintained | releasemodel = LTS | packagemanager = [[APT]] | defaultdesktops = Cinnamon, MATE, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://linuxmint.com linuxmint.com] |wiki=[https://mintwiki.org/ The Linux Mint Community Wiki]}} Linux Mint is a stable [[Ubuntu]]-based distribution designed to work 'out of the box' and comes with the apps most people need preinstalled. It is primarily targeted towards users coming from [[Windows]] who are looking for an OS that allows them to have more control over their computer, or provide an entry point into Linux. It uses the [[Cinnamon]] desktop environment (the Linux Mint team develop Cinnamon), with maintained options for [[XFCE|Xfce]] and [[MATE]] too.<ref>[https://linuxmint.com/ Home - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> It has had [[GNOME]] and [[Plasma|KDE]] support at points in its history. There is also a Debian-based version of Linux Mint, called [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], that only has Cinnamon support.<ref>[https://distrowatch.com/table.php?distribution=mint DistroWatch.com: Linux Mint], DistroWatch.com, 2001-08-09 (Accessed: 2025-08-09)</ref> More information and resources related to Linux Mint along with how to install it, use it and manage it can be found at [https://mintwiki.org/ The Linux Mint Community Wiki]. == Overview == * Developed/owned by: Clément Lefèbvre, Vincent Vermeulen, Oscar799, and [https://linuxmint.com/teams.php team] * OS Family: [[Linux]] * Source Model: [https://github.com/linuxmint Open-source] * Update Method: [https://endoflife.date/linuxmint Release cycle] * Package Manager: [[APT|apt]], [[flatpak]] * Architecture: [[x86_64]], [[i386]] (LMDE only) [[File:Linux-Mint-Cinnamon.png|thumb|A Linux Mint installation with the Cinnamon desktop]] == History == Linux Mint was first released in 2006 by Clément Lefèbvre. It started as a beta release called Linux Mint 1.0 "Ada", which was based on [[Kubuntu]] and used the KDE desktop environment. The second version, Linux Mint 2.0 "Barbara", was the first to use Ubuntu as its base and featured the GNOME desktop environment.<ref>[https://www.linuxmint.com/about.php About Linux Mint - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> Over the years, Linux Mint evolved, adopting Ubuntu's release cycle and refining its features. In 2010, the Linux Mint team introduced [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], which was based on Debian instead of Ubuntu. The distribution became known for its user-friendly interface, multimedia support, and stability, making it a favourite among desktop users. In 2016, the Linux Mint website and forums were hacked and the installation images were infected with malware.<ref>{{Cite|url=https://www.pcworld.com/article/419713/hackers-planted-a-backdoor-inside-a-compromised-version-of-linux-mint.html|title=Linux Mint website hacked, ISO downloads replaced with backdoored operating system|author=Nick Mediati, PCWorld|year=2016|accessdate=2025.08.31}}</ref> The latest release, Linux Mint 22.3 "Zena", was launched on the 13th of January, 2026 and is supported until 2029.<ref>https://linuxmint.com/rel_zena.php, Linux Mint, 2006-08-09 (Accessed: 2026-05-24)</ref> == Compatibility with upstream distros == Linux Mint is primarily based on Ubuntu, which itself is derived from Debian. This means Mint inherits compatibility with Ubuntu's package repositories and software ecosystem. However, Mint also maintains a separate edition called [https://mintwiki.org/wiki/Linux_Mint_Debian_Edition_(LMDE) Linux Mint Debian Edition (LMDE)], which is based directly on Debian. Mint developers have stated that they prefer using Ubuntu as a base because it's easier to remove unwanted features from Ubuntu than to add missing ones to Debian. That said, LMDE exists as a backup plan in case Ubuntu ever undergoes drastic changes that make it unsuitable for Mint.<ref>[https://www.reddit.com/r/linuxquestions/comments/1bh9u4l/why_linux_mint_still_uses_ubuntu_as_a_base_distro/ Why Linux Mint still uses Ubuntu as a base distro rather than Debian?], rnmkrmn, 2024-03-18 (Accessed: 2025-08-09)</ref> == Software installation == Mint ships with its own [http://packages.linuxmint.com/ repositories], which contain some useful software such as [[Firefox]], Thunderbird, and other software that was removed from the Ubuntu repositories as [[Canonical]] wanted these to be installed via [[snap]] instead. The Linux Mint team are against using snap, so packages this software themselves. The repositories also contain software made by the Linux Mint team such as Cinnamon and its related applications<ref>[https://repo.c48.uk/mint/pkgs/pool/ Index of /mint/pkgs/pool/] (Accessed: 2025-08-09)</ref> which can be installed from the [https://mintwiki.org/wiki/Software_Manager Software Manager]. == References == c136437d329090acaef94bff25309470d6249cb3 1 1305 5618 2026-05-30T12:41:45Z Sivecano 413 /* list compositor by tiling/floating */ new section wikitext text/x-wiki == list compositor by tiling/floating == maybe we should list compositors by whether they are tiling/floating/other like in the arch wiki with a short explanation of the differences. [[User:Sivecano|Sivecano]] ([[User talk:Sivecano|talk]]) 12:41, 30 May 2026 (UTC) aa4adc7bfb22129cf88f734f7fef9f6399a3b70a 0 769 5619 5467 2026-05-30T12:49:53Z Sivecano 413 update information about river in line with the breaking changes made in the 0.4 release on 2026-03-15: https://codeberg.org/river/river/releases/tag/v0.4.0 wikitext text/x-wiki {| class="wikitable" ! Compositor !! Desktop Environment !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || None (Reference) || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. |- | [[MangoWM]]<ref>[https://mangowc.vercel.app MangoWM Homepage]{{Dead Link|2026-05-26|404}} (Accessed: 2026-02-27)</ref> || None || [[C]] || Extremely customizable & performant Wayland compositor built on top of [[dwl]]. |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| [[C]] || Modified to support Wayland in GNOME Shell. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]]|| [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- | [[Sway]] || None || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || None (Tiling) || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[river]]<ref>[https://codeberg.org/river/river Codeberg - A non-monolithic Wayland compositor] river, (Accessed: 2026-05-30)</ref>|| None (external window manager) || [[zig]]|| A non-monolithic wayland compositor where window management is performed by an external program |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || None (3D effects) || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || None (Kiosk) || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- | [[Niri]] || None (Scrolling) || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp cosmic-comp github repo], pop-os team et al., 2025 (Accessed: 2026-05-25)</ref> |[[COSMIC]] |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |None |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || None (Tiling) || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} ==References== <references /> 40432c7c0eab49f3cb90439afd2bf407d0312030 0 1232 5620 5613 2026-05-30T12:59:27Z Sivecano 413 change kakoune description to something more descriptive. wikitext text/x-wiki Commonly-used free and open source text editing [[software]] on [[Linux]]. = Text editors = {| class="wikitable" !Name !External links !Description |- |[[Geany]] |[https://www.geany.org/ Website], [https://github.com/geany/geany GitHub] |A powerful, stable and lightweight programmer's text editor. |- |[[Kate]] |[https://apps.kde.org/en-gb/kate/ KDE Applications], [https://invent.kde.org/utilities/kate GitLab] |KDE Advanced Text Editor, a code editor that comes with [[Plasma|KDE Plasma]] |- |[[KWrite]] |[https://apps.kde.org/en-gb/kwrite/ KDE Applications] |A text editor that comes with [[Plasma|KDE Plasma]] based on Kates editor component. |- |[[Code| Code - OSS (Visual Studio Code)]] |[https://github.com/code-oss-dev/code GitHub] |An open source text editor by Microsoft that can be upgraded into an IDE through extensions. |- |[[Zed]] |[https://zed.dev/ Website], [https://github.com/zed-industries/zed GitHub] |Text editor written in Rust. |- |[[Gram]] |[https://gram-editor.com/ Website], [https://codeberg.org/GramEditor/gram CodeBerg] |A code editor that started as a fork of [[Zed]] to remove AI and avoid agreeing to the Zed terms of use |- |[[GNU Emacs|GNU Emacs (GUI)]] |[https://www.gnu.org/software/emacs/ Website], [https://cgit.git.savannah.gnu.org/cgit/emacs.git Source] |An extensible, customizable, free/libre text editor — and more. |- |[[Pulsar]] |[https://pulsar-edit.dev/ Website], [https://github.com/pulsar-edit/pulsar GitHub] |A community-led, hyper-hackable text editor. Pulsar is a fork of the discontinued [[Atom]] editor |- |[[Atom]] |[https://atom.io/ Website], [https://github.com/atom/atom GitHub] |The hackable text editor. A discontinued GitHub developed editor |- |[[Lite XL]] |[https://lite-xl.com/ Website], [https://github.com/lite-xl/lite-xl GitHub] |A lightweight text editor written in Lua |- |[[Pragtical]] |[https://pragtical.dev/ Website], [https://github.com/pragtical/pragtical GitHub] |The practical and pragmatic code editor. Fork of [[Lite XL]] |- |[[Lapce]] |[https://lap.dev/lapce/ Website], [https://github.com/lapce/lapce GitHub] |Lightning-fast and Powerful Code Editor written in Rust |- |} == Terminal-based text editors == These text editors use a [[TUI]] and are useful for editing config files. {| class="wikitable" !Name !External links !Description |- |[[Nano]] |[https://www.nano-editor.org/ Website], [https://cgit.git.savannah.gnu.org/cgit/nano.git/log/ Source] |Simple terminal text editor that comes with most distributions |- |[[Vi]] |[https://github.com/Cube9999/vi GitHub] |A keyboard based terminal text editor |- |[[Vim]] |[https://www.vim.org/ Website], [https://github.com/vim/vim GitHub] |An improved version of Vi with various changes and support for plugins |- |[[Neovim]] |[https://neovim.io/ Website], [https://github.com/neovim/neovim GitHub] |A customizable keyboard terminal text editor with themes and extensions |- |[[GNU Emacs]] |[https://www.gnu.org/software/emacs/ Website], [https://cgit.git.savannah.gnu.org/cgit/emacs.git Source] |An extensible, customizable, free/libre text editor — and more. |- |[[Helix]] |[https://helix-editor.com/ Website], [https://github.com/helix-editor/helix GitHub] |A modern terminal editor with batteries included similar to Kakoune and written in Rust |- |[[Kakoune]] |[https://kakoune.org/ Website], [https://github.com/mawww/kakoune GitHub] |A unique modal editor which unlike Vi puts selections before actions. |- |[[Flow Control]] |[https://flow-control.dev/ Website], [https://github.com/neurocyte/flow GitHub] |TUI editor written in Zig with multiple keybinding modes |- |[[Edit]] |[https://learn.microsoft.com/en-us/windows/edit/ Website], [https://github.com/microsoft/edit GitHub] |Simple Microsoft developed command-line text editor |- |} = Integrated development environments (IDEs) = IDEs typically feature compilers, debuggers with stepping, and everything needed to produce software. {| class="wikitable" !Name !External links !Description !Focus |- |[[Code::Blocks]] |[https://www.codeblocks.org/downloads/ Website], [https://www.codeblocks.org/downloads/source/ Source] |Cross-platform integrated development environment centred on native-language workflows. |C/C++ and Fortran |- |[[Eclipse IDE]] |[https://eclipseide.org/ Website], [https://github.com/eclipse GitHub] |General-purpose, plugin-based IDE with integrated build, debug, and project tooling. |Java and multi-language via plugins |- |[[KDevelop]] |[https://kdevelop.org/ Website] ,[https://invent.kde.org/kdevelop/kdevelop GitLab] |KDE’s integrated development environment with code navigation, debugging, and VCS integration. |C/C++ and Qt/KDE workflows |- |[[Lazarus]] |[https://www.lazarus-ide.org/ Website], [https://gitlab.com/freepascal.org/lazarus/lazarus GitLab] |Rapid application development IDE for Free Pascal with visual form design. |Pascal/Free Pascal |- |[[NetBeans]] |[https://netbeans.apache.org/front/main/index.html Website], [https://github.com/apache/netbeans GitHub] |Full-featured IDE with project templates, debugging, profiling, and build integration. |Java, PHP, and web development |- |[[Qt Creator]] |[https://www.qt.io/development/tools/qt-creator-ide Website], [https://github.com/qt-creator/qt-creator GitHub] |Purpose-built IDE for Qt application development with integrated UI design and debugging. |Qt/C++/QML |- |[[Spyder]] |[https://www.spyder-ide.org/ Website], [https://github.com/spyder-ide/spyder GitHub] |Scientific Python IDE with integrated console, debugger, variable explorer, and plotting tools. |Python/data science |} 7872dc2dc34a63bc73dcadc235c0b96dff2d9ab9 0 1306 5621 2026-05-30T13:02:36Z Int 401 Create stub wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = EXWM | releasestatus = Maintained | lastrelease = 0.34 (27 June 2025)<ref name=":0">{{Cite|title=EXWM ELPA package|url=https://elpa.gnu.org/packages/exwm.html|accessdate=30 May 2026}}</ref> | firstrelease = 0.1 (3 Nov 2015)<ref name=":0" /> | languages = [[Emacs Lisp]] | developers = EXWM developers | website = https://github.com/emacs-exwm/exwm | license = GPL-3.0-only | sourcecode = https://github.com/emacs-exwm/exwm }} EXWM is a [[X Window Manager#Tiling Window Managers|tiling]] [[X Window Manager|X window manager]] for [[Emacs]].<ref name=":1">{{Cite|title=EXWM User Guide|url=https://github.com/emacs-exwm/exwm/wiki|accessdate=30 May 2026}}</ref> == Features == Every window in EXWM is an Emacs buffer. This naturally allows for dynamic workspaces and seamless switching between windows and buffers.<ref name=":1" /> EXWM also supports multi-monitor setups. == History == == Installation == {{GuideWarning}} # Install [[Emacs]]. # Install EXWM within Emacs: <code>M-x package-install RET exwm RET</code> # Add this to [[X11#xinitrc|xinitrc]]: <syntaxhighlight lang="sh">exec emacs</syntaxhighlight> # Add this to your Emacs init file: <syntaxhighlight lang="emacs-lisp"> (require 'exwm) (require 'exwm-config) (exwm-config-example) </syntaxhighlight><code>(exwm-config-example)</code> will load the default settings. To use your own settings, use:<syntaxhighlight lang="emacs-lisp"> (require 'exwm) (exwm-enable) </syntaxhighlight> == Usage == == References == <references /> 9a8fb5cd52b0258e2facb206fdc7b79f579090b1 5624 5621 2026-05-31T01:10:47Z Stone574 416 use-package is best practice wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = EXWM | releasestatus = Maintained | lastrelease = 0.34 (27 June 2025)<ref name=":0">{{Cite|title=EXWM ELPA package|url=https://elpa.gnu.org/packages/exwm.html|accessdate=30 May 2026}}</ref> | firstrelease = 0.1 (3 Nov 2015)<ref name=":0" /> | languages = [[Emacs Lisp]] | developers = EXWM developers | website = https://github.com/emacs-exwm/exwm | license = GPL-3.0-only | sourcecode = https://github.com/emacs-exwm/exwm }} EXWM is a [[X Window Manager#Tiling Window Managers|tiling]] [[X Window Manager|X window manager]] for [[Emacs]].<ref name=":1">{{Cite|title=EXWM User Guide|url=https://github.com/emacs-exwm/exwm/wiki|accessdate=30 May 2026}}</ref> == Features == Every window in EXWM is an Emacs buffer. This naturally allows for dynamic workspaces and seamless switching between windows and buffers.<ref name=":1" /> EXWM also supports multi-monitor setups. == History == == Installation == {{GuideWarning}} # Install [[Emacs]]. # Install EXWM within Emacs: <code>M-x package-install RET exwm RET</code> # Add this to [[X11#xinitrc|xinitrc]]: <syntaxhighlight lang="sh">exec emacs</syntaxhighlight> # Add this to your Emacs init file: <syntaxhighlight lang="emacs-lisp"> (use-package exwm :ensure t :config (require 'exwm-config) (exwm-config-example)) </syntaxhighlight><code>(exwm-config-example)</code> will load the default settings. To use your own settings, use:<syntaxhighlight lang="emacs-lisp"> (use-package exwm :ensure t :config ;; config options here (exwm-enable)) </syntaxhighlight> == Usage == == References == <references /> b546bf79b1becefecac8b474ebd23280bf4f3255 0 1200 5622 5255 2026-05-30T13:07:56Z Sivecano 413 Add a second paragraph to the kakoune page. this gives a bit more of an overview of the features of kakoune wikitext text/x-wiki {{stub|date=may 2026}} {{SoftwareInfobox |image=[[File:Kakoune logo.svg|thumb|The logo for Kakoune]] |caption=Kakoune |title=Kakoune |releasestatus=Maintained |lastrelease=2026.05.21, May 20, 2026 |firstrelease=Unknown, Sep 2, 2011 |languages=[[C++]], [[Kakoune Script]] |developers=[https://github.com/mawww Maxime Coste] |website=[https://kakoune.org/ kakoune.org] }} [[Category:Software]] [[File:Kakoune-linux-init-main.c.png|thumb|Kakoune open to the Linux kernel source code (<code>init/main.c</code>)]] '''Kakoune''' is a modal editor, it is designed to provide an efficient, predictable, and scriptable code editing environment<ref>{{Cite|url=https://kakoune.org/why-kakoune/why-kakoune.html|title=Why Kakoune|author=Maxime Coste|year=2020-01-03|accessdate=2026-05-23}}</ref>. It is a strong divergence from [[Vi]] like editors and inspired [[Helix]]. Kakoune has code motions similar to [[Vi]] with a focus on selections instead of actions. Kakoune supports multiple cursors and a server-client architecture similar to [[GNU Emacs]] this allows Kakoune to forego having to manage windows or panes internally. It instead relies on terminal multiplexers like [[tmux]] or simply the user's window manager. Kakoune is configured in a simple Configuration Language called [[Kakoune Script]] plugins are written using [[Shell]] or any other programming language like [[C]], [[Rust]] or [[Python]]. e3f5682a040b27ae406a3ee8b68e6024579b06a5 0 1056 5623 4998 2026-05-31T00:58:13Z Strangely Human Feeling 415 Updated link for OpenSUSE tumbleweed wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Rolling release''' is a software release model where software updates are delivered continuously. Unlike [[fixed release]] which is in a discrete manner, rolling release usually implies shipping the latest software as soon as possible. A famous example would be [[Arch Linux]]. Rolling release does not imply unstable software. The software may be tested thoroughly before shipping. An example would be [[OpenSUSE#Tumbleweed|openSUSE Tumbleweed]]. The deciding factor for [[distro]]s would be usually whether updates would stop, that is, whether ''mass updates'' are provided, where there are full ''system upgrades'' in which many [[package]]s would be updated together. If so, that violates the fundamental requirements of rolling release. == Semi-rolling == '''Semi-rolling''' is a layman's term for describing distributions providing updates for non-breaking features, bug fixes, etc., while requiring full system upgrades to receive further software updates, otherwise updates will stop eventually. There is no concrete definition and the term is quite ambiguous, but usually this describes fixed-release distros like [[Fedora|Fedora Linux]]. ca6296c9963ca7a4bcb39cdb46ae448a81cd195e 5627 5623 2026-05-31T02:00:05Z Larry the cow 402 Elaborated a bit on what rolling means, added comparison to make the difference clearer wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Rolling release''' is a software release model where software updates are delivered continuously, and often frequently. Unlike [[fixed release]] where software usually is provided through versions, rolling release usually provides one single, continously updated version of the software. A famous example would be [[Arch Linux]], providing only one version in contranst to ie. Ubuntu which is versioned into 26.10, 25.10 etc. Even though rolling release distributions are often associated with being cutting edge, meaning providing the newest software as fast as possible, these two terms should not be conflated; the term rolling release is first and foremost about model of distribution, and not speed of delivery. Rolling release does not imply unstable software. The software may be tested thoroughly before shipping. Some examples would be [[OpenSUSE#Tumbleweed|openSUSE Tumbleweed]], or [[Gentoo]]. The deciding factor for [[distro]]s would be usually whether updates would stop, that is, whether ''mass updates'' are provided, where there are full ''system upgrades'' in which many [[package]]s would be updated together. If so, that violates the fundamental requirements of rolling release. == Semi-rolling == '''Semi-rolling''' is a layman's term for describing distributions providing updates for non-breaking features, bug fixes, etc., while requiring full system upgrades to receive further software updates, otherwise updates will stop eventually. There is no concrete definition and the term is quite ambiguous, but usually this describes fixed-release distros like [[Fedora|Fedora Linux]]. 1d93ad2fe695539435cc124a8ed6c4617360508a 5628 5627 2026-05-31T02:01:28Z Larry the cow 402 wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Rolling release''' is a software release model where software updates are delivered continuously, and often frequently. Unlike [[fixed release]] where software usually is provided through versions, rolling release usually provides one single, continously updated version of the software. A famous example would be [[Arch Linux]], providing only one version in contranst to ie. Ubuntu which is versioned into 26.10, 25.10 etc. Even though rolling release distributions are often associated with being cutting edge, meaning providing the newest software as fast as possible, these two terms should not be conflated; the term rolling release is first and foremost about model of distribution, and not speed of delivery. Rolling release does not imply unstable software. The software may be tested thoroughly before shipping. Some examples would be [[OpenSUSE#Tumbleweed|openSUSE Tumbleweed]], or [[Gentoo]]. The deciding factor for [[distro]]s would be usually whether updates would stop, that is, whether ''mass updates'' are provided, where there are full ''system upgrades'' in which many [[package]]s would be updated together. If so, that violates the fundamental requirements of rolling release. == Semi-rolling == '''Semi-rolling''' is a layman's term for describing distributions providing updates for non-breaking features, bug fixes, etc., while requiring full system upgrades to receive further software updates, otherwise updates will stop eventually. There is no concrete definition and the term is quite ambiguous, but usually this describes fixed-release distros like [[Fedora|Fedora Linux]]. == See also == * [[Fixed release]] 9da7645705f4ed2a021b427a1969a348bfc43d80 5644 5628 2026-05-31T12:51:55Z Strangely Human Feeling 415 Added links, general cleanup wikitext text/x-wiki [[Category:Release_model]] [[Category:Terminology]] '''Rolling release''' is a software release model where updates are delivered continuously, and often frequently.<ref>https://vanillaos.org/blog/article/2023-01-31/point-vs-rolling-release-and-the-modern-solutions</ref><ref>https://linuxiac.com/rolling-vs-point-release-linux-distributions/</ref> Unlike a [[fixed release]] model, where software is provided through versions, rolling release provides a single, continuously updated version of the software. A notable example would be [[Arch Linux]]. Though rolling release distributions can package cutting edge software and updates, many are still tested before shipping, such as [[OpenSUSE#Tumbleweed|openSUSE Tumbleweed]] or [[Gentoo]].<ref>https://wiki.gentoo.org/wiki/FAQ</ref> == Semi-rolling == '''Semi-rolling''' is a layman's term for describing distributions providing updates for non-breaking features, bug fixes, etc., while requiring full system upgrades to receive further software updates, otherwise updates will stop eventually. There is no concrete definition and the term is quite ambiguous, but usually this describes fixed-release distros like [[Fedora|Fedora Linux]]. == See also == * [[Fixed release]] 85ee7365a5d41b3105afd0be9daa80c236eb82a8 0 279 5625 5416 2026-05-31T01:46:52Z Strangely Human Feeling 415 little cleanup and refrences wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] or [[transactional-update]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[IceWM]] | usagetype = Desktop, Server | architectures = i686, x86-64, aarch64, ppc64le, s390x | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE (/ˌoʊpənˈsuːzə/) is a line of [[Linux distributions]] developed by the openSUSE Project and the SUSE S.A.<ref>[https://en.opensuse.org/openSUSE:Guiding_principles#Governance openSUSE Governance Structure], governance structure of openSUSE and SUSE, openSUSE wiki</ref> – a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == OpenSUSE stands out by having variations of the distributions: === Tumbleweed === Tumbleweed is the [[Rolling release]] distribution containing the latest [[openQA|openQA]] testet versions of all software. Tumbleweed is based on Factory, openSUSEs main development codebase, As soon as a openQA tests pass, a new Tumbleweed snapshot will be released – typically several times a week. === Slowroll === Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === Leap === Leap is the [[fixed release]] distribution of OpenSUSE. It receives minor releases every 12 months, with 24 months of free support, and upwards of 36 months for paid enterprise support.<ref>https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/16.0/html/release-notes-leap-160/</ref><ref>https://www.suse.com/products/long-term-service-pack-support/</ref> === Kalpa === Kalpa is an atomic and transactional Linux desktop offering the KDE Plasma Desktop Environment. It's goal is to be easy to use and for people who "want to be stuff done" without messing with their operating system. Kalpa is based on Tumbleweed and MicroOS. === MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed ==References== 775a848a59d45dfb873d40f7ecafa87c8736a6bc 5626 5625 2026-05-31T01:47:45Z Strangely Human Feeling 415 wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = openSUSE | image = [[File:OpenSUSE Logo.svg|frameless]] | caption = openSUSE | releasestatus = Maintained | releasemodel = Stable or Rolling | packagemanager = [[zypper]] or [[transactional-update]] | defaultdesktops = [[KDE Plasma]], [[GNOME]], [[Xfce]], [[IceWM]] | usagetype = Desktop, Server | architectures = i686, x86-64, aarch64, ppc64le, s390x | website = [https://www.opensuse.org opensuse.org] }} OpenSUSE (/ˌoʊpənˈsuːzə/) is a line of [[Linux distributions]] developed by the openSUSE Project and the SUSE S.A.<ref>[https://en.opensuse.org/openSUSE:Guiding_principles#Governance openSUSE Governance Structure], governance structure of openSUSE and SUSE, openSUSE wiki</ref> – a software company that provides [[Linux]] services to business and enterprise customers. Particular features that stand out is their in-house installer, YaST2, of the [[Operating System|operating system]] that stays installed after installation is complete. YaST2 stays installed as a configuration tool while the operating system is in use with [[GUI]] and [[TUI]] options. == Versions == OpenSUSE stands out by having variations of the distributions: === Tumbleweed === Tumbleweed is the [[rolling release]] distribution containing the latest [[openQA|openQA]] testet versions of all software. Tumbleweed is based on Factory, openSUSEs main development codebase, As soon as a openQA tests pass, a new Tumbleweed snapshot will be released – typically several times a week. === Slowroll === Slowroll is an experimental version of openSUSE Tumbleweed. It update less frequently while still being relatively up to date and aims to provide a more stable experience, it does this by taking a snapshot of Tumbleweed roughly once a month which is then tested to ensure stability. === Leap === Leap is the [[fixed release]] distribution of OpenSUSE. It receives minor releases every 12 months, with 24 months of free support, and upwards of 36 months for paid enterprise support.<ref>https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/16.0/html/release-notes-leap-160/</ref><ref>https://www.suse.com/products/long-term-service-pack-support/</ref> === Kalpa === Kalpa is an atomic and transactional Linux desktop offering the KDE Plasma Desktop Environment. It's goal is to be easy to use and for people who "want to be stuff done" without messing with their operating system. Kalpa is based on Tumbleweed and MicroOS. === MicroOS === MicroOS is an Immutable OS designed to host container workloads with automated administration and patching. It's philosophy is to be predictable, scalable and reliable. === Leap Micro === Leap Micro, similar to MicroOS is designed for host container workloads, but to increase stability with being based on Leap rather than Tumbleweed ==References== c4552c112e9f1cbf55e0ae5b66bc1dccf2e51059 0 291 5629 4372 2026-05-31T03:47:37Z Stone574 416 gnome 50 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|300px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 50, 2026-03-18 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[Category:Desktop Environments]] [[File:GNOME 43.png|thumb|A desktop running GNOME 43]] '''GNOME''' (GNU Network Object Model Environment) is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>[https://www.gnu.org/philosophy/free-sw.en.html What is Free Software?], GNU (Accessed: May 7, 2025)</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>[[wikipedia:Qt_(software)#Early_developments|Early Developments of QT]], Wikipedia (Accessed: May 7, 2025)</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>[[wikipedia:GNOME#History|History of GNOME]], Wikipedia (Accessed: May 7, 2025)</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>[https://foundation.gnome.org/ GNOME Foundation], GNOME Foundation, 2025-08-08 (Accessed: 2025-08-09)</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. == References == b131c7a904be194bad797ac4cc5d8c9de790cba8 5631 5629 2026-05-31T04:00:43Z Larry the cow 402 Corrected the common acronym and GNU stuff wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GNOME logo.svg|300px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 50, 2026-03-18 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[Category:Desktop Environments]] [[File:GNOME 43.png|thumb|A desktop running GNOME 43]] '''GNOME''' is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>[https://www.gnu.org/philosophy/free-sw.en.html What is Free Software?], GNU (Accessed: May 7, 2025)</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. GNOME used to be an acronym for "GNU Network Object Modeling Environment", but that is no longer the case; nowadays, GNOME stands for GNOME.<ref>[https://mail.gnome.org/archives/marketing-list/2010-April/msg00050.html |Re: GNOME -> Gnome], mail.gnome.org (Acessed: May 31, 2026)</ref> == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>[[wikipedia:Qt_(software)#Early_developments|Early Developments of QT]], Wikipedia (Accessed: May 7, 2025)</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>[[wikipedia:GNOME#History|History of GNOME]], Wikipedia (Accessed: May 7, 2025)</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>[https://foundation.gnome.org/ GNOME Foundation], GNOME Foundation, 2025-08-08 (Accessed: 2025-08-09)</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. == References == 228a7f0884f966cf85e6e5682480b9626aeee5a3 6 1307 5630 2026-05-31T03:58:56Z Stone574 416 wikitext text/x-wiki Logo of GTK 38457a3f5750e5460eaf9fd545126387fb0d7f77 0 1308 5632 2026-05-31T04:15:10Z Stone574 416 init GTK page wikitext text/x-wiki {{SoftwareInfobox | image = [[File:GTK logo.png|300px|GTK_logo]] | caption = GTK Logo | title = GTK | releasestatus = Maintained | lastrelease = 4.22.4, 2026-04-30 | languages = C , with bindings for C++, Python, Rust, JavaScript, Vala and more | developers = GNOME Project, The GTK Team | website = https://gtk.org/ }} '''GTK''' is a cross-platform widget toolkit used for building graphical user interfaces. It is written primarily in [[C]] and exposes a fully object-oriented widget system through its own type system, '''GObject''', and serves as the foundational UI library for the [[GNOME]] desktop environment and a large number of standalone applications across [[Linux]], [[Windows]], and [[macOS]]. GTK is licensed under the [[GNU General Public License#GNU Lesser General Public License (LGPL)|LGPL]], permitting use in both free and proprietary applications <ref>[https://www.gtk.org/docs/getting-started/ GTK Getting Started], GTK Project (Accessed: May 2026)</ref>. == History == GTK was originally written in 1996 by ''Spencer Kimball'', ''Peter Mattis'', and ''Josh MacDonald'' as part of the [[GIMP]] image editor project, as a replacement for the proprietary Motif toolkit. The name ''GIMP Toolkit'' directly reflects this origin. In 1997, when the '''GNOME Project''' was founded by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a desktop environment, GTK was adopted as its core widget library. ==== Timeline<ref>[[wikipedia:GTK#History|GTK History]], Wikipedia (Accessed: May 2026)</ref> ==== * '''GTK 1.0 (1998)''': First stable release; tightly coupled to GIMP and X11. Introduced the foundational widget set and the Glib dependency. * '''GTK 2.0 (2002)''': Major overhaul introducing Pango for internationalised text rendering, for accessibility, and improved theming support via theme engines. * '''GTK 3.0 (2011)''': Released in February 2011, shortly before [[GNOME]] 3 in April 2011. Introduced [[CSS]]-based theming that replaced the old rc-based system, Cairo based rendering, and initial [[Wayland]] support alongside [[X11]]. * '''GTK 4.0 (2020)''': Rendering was moved to the '''GSK''' (GTK Scene Graph Kit) layer, backed by '''OpenGL''', '''Vulkan''', or '''Cairo''' renderers. Input event handling was overhauled, media playback support was added natively, and the layout system was substantially revised. e891542cb95c8a02304a6a7b4004f8aed73ad993 3000 1309 5633 2026-05-31T04:53:34Z Stone574 416 Created page with "{{Guide Warning}} You will need patchelf, elfutils, and gcompat gcompat can be installed from most package managers. Enable DRM in settings so firefox downloads the widevine plugin. Navigate to the plugin in your profile (~/.mozilla/(..)/gmp-widevinecdm/(version) Run: <syntaxhighlight lang="bash"> patchelf --add-needed libgcompat.so.0 ./libwidevinecdm.so </syntaxhighlight> Now we need to update the firefox config. We need the hash: <syntaxhighlight lang="bash"> sha51..." wikitext text/x-wiki {{Guide Warning}} You will need patchelf, elfutils, and gcompat gcompat can be installed from most package managers. Enable DRM in settings so firefox downloads the widevine plugin. Navigate to the plugin in your profile (~/.mozilla/(..)/gmp-widevinecdm/(version) Run: <syntaxhighlight lang="bash"> patchelf --add-needed libgcompat.so.0 ./libwidevinecdm.so </syntaxhighlight> Now we need to update the firefox config. We need the hash: <syntaxhighlight lang="bash"> sha512sum libwidevinecdm.so </syntaxhighlight> Then open your firefox about:config and set media.gmp-widevinecdm.hashValue to whatever you just copied. Then you will need export MOZ_DISABLE_GMP_SANDBOX=1 to your ~/.profile so firefox can read libgcompat.so 64d2ed3b1c03eba357c71b3eb0d50e11d1202aca 6 1310 5634 2026-05-31T06:53:39Z Madonuko 140 Usage of kdenlive with custom floating window layout wikitext text/x-wiki == Summary == Usage of kdenlive with custom floating window layout == Licensing == {{CC-BY-SA-4.0}} 16ccb600455783776e9917dad0ec3f4bf878d34a 0 1084 5635 5153 2026-05-31T08:09:05Z Int 401 Put references into its own section wikitext text/x-wiki [[Category:Software]] [[Category:Package_Managers]] '''Alpine Package Keeper (apk)''' (not to be confused with <code>.apk</code> installation files found on android systems) is Alpine's official package manager. Coded in C, its primary goal is to manage packages on a user's systems while staying minimal. Packages on the distribution's repositories come in 3 official repository: <code>main</code>, <code>community</code>, and <code>testing</code>;<ref>[https://wiki.alpinelinux.org/wiki/Repositories#Official_repositories Repositories - Official Repositories], ''Alpine Wiki'', The Alpine Team (1) (Accessed 2/12/2026 20:39 UTC-5)</ref> however, the user is free to enable and disable them freely.<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], ''Alpine User Handbook,'' The Alpine Team (1) (Accessed 02/10/2026 18:00 UTC-5)</ref> == Overview == The <code>apk-tools</code> package provides the package manager and other features, the table below shows possible commands.<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper Alpine Package Keeper], ''Alpine Wiki'', The Alpine Team (1) (Accessed 2/12/2026 20:40 UTC-5)</ref> {| class="wikitable" |+Package Management Via <code>apk</code> !Command !Usage !Overview |- |<code>add</code> |<code>apk add <package_name></code> |Adds a package to the system and modifies WORLD file, commits changes afterwards |- |<code>del</code> |<code>apk del <package_name></code> |Deletes a package from the system and modifies WORLD file, commits changes afterwards |- |<code>fix</code> |<code>apk fix <package_name></code> |Fixes (attempts to) a package via reinstall and/or upgrading without modifying WORLD |- |<code>update</code> |<code>apk update</code> |Updates repository index, Typically ran after modifying repository file |- |<code>upgrade</code> |<code>apk upgrade <optional_package></code> |Upgrade packages on the system, optionally upgrade only one package by specifying it. |- |<code>cache</code> |<code>apk cache <option></code> |Manages the local package cache |- |<code>query</code> |<code>apk query <package_name></code> |Combines <code>info</code>, <code>list</code>, and <code>search</code> commands through your installed packages and outputs information in a human-readable format |- |<code>info</code> |<code>apk info [optional_flag] <optinal_package></code> |Lists all information about installed packages and allows you to search through it with given flags |- |More commands... | | |} == Managing Packages == Official software on the Alpine Linux repositories are named "''a-packs''" and have the extension <code>.apk</code> (Not to be confused with Android's APK installation files). You can edit which repositories you'd like to access by editing <code>/etc/apk/repositories</code>, commenting/uncommenting any repository you'd like. Upon saving the file, run <code>apk update</code> to update the repository index.<ref>[https://wiki.alpinelinux.org/wiki/Repositories#Managing_repositories Repositories - Managing Repositories], ''Alpine Wiki'', The Alpine Team (3) (Accessed 2/12/2026 20:48 UTC-5)</ref> APK will automatically echo how many packages are currently available on enabled repositories upon completing the updates.<ref>[https://wiki.alpinelinux.org/wiki/Repositories Repositories], ''Alpine Wiki'', The Alpine Team (1) (Accessed 2/12/2026 20:48 UTC-5)</ref> === World === The <code>WORLD</code> file on Alpine Linux (located at <code>/etc/apk/world</code>) describes desired system states in a plain text file and uses unique syntax to configure package installation. Should you edit the file, run <code>apk fix</code> to apply changes. The <code>world</code> file must be in order upon running <code>apk fix</code>, else the package manager refuses to apply any constraints to the adjusted file; hence why APK will never leave a system unbootable.<ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#World Alpine Package Keeper - World], ''Alpine Wiki,'' The Alpine Team (1) (Accessed 2/12/2026 20:56 UTC-5)</ref> === Configuring APK === APK allows you to configure the package manager by adjusting/editing the <code>/etc/config/apk</code> (assuming the user has made it [make the file via <code>touch /etc/config/apk</code> with proper permissions]) will override the default APK config located in <code>/lib/apk/config</code>. <ref>[https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#Configuration_file Alpine Package Keeper - Configuration File], ''Alpine Wiki'', The Alpine Team (11) (Accessed 2/12/2026 21:10 UTC-5)</ref> == References == <references /> ba671d03cd97b403f6bcbc3e81aef7ffb668a6c8 5638 5635 2026-05-31T09:16:52Z Int 401 Reword and make citations use the Cite template wikitext text/x-wiki [[Category:Software]] [[Category:Package_Managers]] Alpine Package Keeper (APK) is [[Alpine Linux]]'s [[package manager]]. (Not to be confused with [[Android]] <code>.apk</code> files) == Overview == The <code>apk-tools</code> package provides APK. The table below shows commonly used commands.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper|title=Alpine Package Keeper - Alpine Wiki|accessdate=12 February 2026}}</ref> {| class="wikitable" |+Commonly used APK commands !Command !Action |- |<code>apk add <package_name></code> |Adds a package to the system and modifies WORLD file, commits changes afterwards |- |<code>apk del <package_name></code> |Deletes a package from the system and modifies WORLD file, commits changes afterwards |- |<code>apk fix <package_name></code> |Fixes (attempts to) a package via reinstall and/or upgrading without modifying WORLD |- |<code>apk update</code> |Updates repository index, Typically ran after modifying repository file |- |<code>apk upgrade <optional_package></code> |Upgrade packages on the system, optionally upgrade only one package by specifying it. |- |<code>apk cache <option></code> |Manages the local package cache |- |<code>apk query <package_name></code> |Combines <code>info</code>, <code>list</code>, and <code>search</code> commands through your installed packages and outputs information in a human-readable format |- |<code>apk info [flags] [packages]</code> |Lists all information about installed packages and allows you to search through it with given flags |} == Repositories == Alpine has three official [[Repository|package repositories]]:<ref>{{Cite|title=Repositories - Official repositories - Alpine Wiki|url=https://wiki.alpinelinux.org/wiki/Repositories#Official_repositories|accessdate=12 February 2026}}</ref> * <code>main</code> packages are stable and officially supported by the Alpine core team. * <code>community</code> packages are generally stable but not officially supported by the Alpine core team. * <code>testing</code> packages are newer but may be unstable. <code>testing</code> is only available on the <code>edge</code> branch. === Managing repositories === {{GuideWarning}} The <code>/etc/apk/repositories</code> file is a newline-separated list of repositories that APK will use.<ref>{{Cite|url=https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html|title=Working with the Alpine Package Keeper (apk), ''Alpine User Handbook''|accessdate=10 February 2026}}</ref> The built-in <code>setup-apkrepos</code> script manages <code>/etc/apk/repositories</code> for you:<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_configuration_management_scripts#setup-apkrepos|title=Alpine configuration management scripts - setup-apkrepos - Alpine Wiki|accessdate=31 May 2026}}</ref> * <code>setup-apkrepos -c</code> will enable the <code>community</code> repository. * <code>setup-apkrepos -f</code> will make APK use the fastest mirror for all repositories. See the [https://wiki.alpinelinux.org/wiki/Alpine_configuration_management_scripts#setup-apkrepos official documentation for <code>setup-apkrepos</code>] for a complete list of options. == Packages == Official software on the Alpine Linux repositories are named "''a-packs''" and have the extension <code>.apk</code>. You can edit which repositories you'd like to access by editing <code>/etc/apk/repositories</code>, commenting/uncommenting any repository you'd like. Upon saving the file, run <code>apk update</code> to update the repository index. APK will automatically echo how many packages are currently available on enabled repositories upon completing the updates.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Repositories|title=Repositories - Alpine Wiki|accessdate=12 February 2026}}</ref> === World === The <code>/etc/apk/world</code> file describes desired system states in a plain text file and uses unique syntax to configure package installation. Should you edit the file, run <code>apk fix</code> to apply changes. The <code>world</code> file must be in order upon running <code>apk fix</code>, else the package manager refuses to apply any constraints to the adjusted file; hence why APK will never leave a system unbootable.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#World|title=Alpine Package Keeper - World - Alpine Wiki|accessdate=12 February 2026}}</ref> == Configuration == APK can be configured by editing <code>/etc/config/apk</code>. If it does not exist, create it with <code>touch /etc/config/apk</code>. This will override the default APK config located in <code>/lib/apk/config</code>.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#Configuration_file|title=Alpine Package Keeper - Configuration File - Alpine Wiki|accessdate=12 February 2026}}</ref> == References == <references /> 8e2c8be26314c4f8b615140e9f90811c0a423ee7 5639 5638 2026-05-31T09:17:36Z Int 401 Move World section from Packages to Configuration wikitext text/x-wiki [[Category:Software]] [[Category:Package_Managers]] Alpine Package Keeper (APK) is [[Alpine Linux]]'s [[package manager]]. (Not to be confused with [[Android]] <code>.apk</code> files) == Overview == The <code>apk-tools</code> package provides APK. The table below shows commonly used commands.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper|title=Alpine Package Keeper - Alpine Wiki|accessdate=12 February 2026}}</ref> {| class="wikitable" |+Commonly used APK commands !Command !Action |- |<code>apk add <package_name></code> |Adds a package to the system and modifies WORLD file, commits changes afterwards |- |<code>apk del <package_name></code> |Deletes a package from the system and modifies WORLD file, commits changes afterwards |- |<code>apk fix <package_name></code> |Fixes (attempts to) a package via reinstall and/or upgrading without modifying WORLD |- |<code>apk update</code> |Updates repository index, Typically ran after modifying repository file |- |<code>apk upgrade <optional_package></code> |Upgrade packages on the system, optionally upgrade only one package by specifying it. |- |<code>apk cache <option></code> |Manages the local package cache |- |<code>apk query <package_name></code> |Combines <code>info</code>, <code>list</code>, and <code>search</code> commands through your installed packages and outputs information in a human-readable format |- |<code>apk info [flags] [packages]</code> |Lists all information about installed packages and allows you to search through it with given flags |} == Repositories == Alpine has three official [[Repository|package repositories]]:<ref>{{Cite|title=Repositories - Official repositories - Alpine Wiki|url=https://wiki.alpinelinux.org/wiki/Repositories#Official_repositories|accessdate=12 February 2026}}</ref> * <code>main</code> packages are stable and officially supported by the Alpine core team. * <code>community</code> packages are generally stable but not officially supported by the Alpine core team. * <code>testing</code> packages are newer but may be unstable. <code>testing</code> is only available on the <code>edge</code> branch. === Managing repositories === {{GuideWarning}} The <code>/etc/apk/repositories</code> file is a newline-separated list of repositories that APK will use.<ref>{{Cite|url=https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html|title=Working with the Alpine Package Keeper (apk), ''Alpine User Handbook''|accessdate=10 February 2026}}</ref> The built-in <code>setup-apkrepos</code> script manages <code>/etc/apk/repositories</code> for you:<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_configuration_management_scripts#setup-apkrepos|title=Alpine configuration management scripts - setup-apkrepos - Alpine Wiki|accessdate=31 May 2026}}</ref> * <code>setup-apkrepos -c</code> will enable the <code>community</code> repository. * <code>setup-apkrepos -f</code> will make APK use the fastest mirror for all repositories. See the [https://wiki.alpinelinux.org/wiki/Alpine_configuration_management_scripts#setup-apkrepos official documentation for <code>setup-apkrepos</code>] for a complete list of options. == Packages == Official software on the Alpine Linux repositories are named "''a-packs''" and have the extension <code>.apk</code>. You can edit which repositories you'd like to access by editing <code>/etc/apk/repositories</code>, commenting/uncommenting any repository you'd like. Upon saving the file, run <code>apk update</code> to update the repository index. APK will automatically echo how many packages are currently available on enabled repositories upon completing the updates.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Repositories|title=Repositories - Alpine Wiki|accessdate=12 February 2026}}</ref> == Configuration == APK can be configured by editing <code>/etc/config/apk</code>. If it does not exist, create it with <code>touch /etc/config/apk</code>. This will override the default APK config located in <code>/lib/apk/config</code>.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#Configuration_file|title=Alpine Package Keeper - Configuration File - Alpine Wiki|accessdate=12 February 2026}}</ref> === World === The <code>/etc/apk/world</code> file describes desired system states in a plain text file and uses unique syntax to configure package installation. Should you edit the file, run <code>apk fix</code> to apply changes. The <code>world</code> file must be in order upon running <code>apk fix</code>, else the package manager refuses to apply any constraints to the adjusted file; hence why APK will never leave a system unbootable.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#World|title=Alpine Package Keeper - World - Alpine Wiki|accessdate=12 February 2026}}</ref> == References == <references /> 1d43d38bb161072009f96dcbed6fa65b8102ef0b 5640 5639 2026-05-31T09:24:40Z Int 401 Add infobox wikitext text/x-wiki [[Category:Software]] [[Category:Package_Managers]] {{SoftwareInfobox | title = Alpine Package Keeper | releasestatus = Maintained | lastrelease = 3.0.6 | languages = [[C]] | developers = The Alpine team | website = https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper | license = GPL-2.0-only | sourcecode = https://gitlab.alpinelinux.org/alpine/apk-tools }} Alpine Package Keeper (APK) is [[Alpine Linux]]'s [[package manager]]. (Not to be confused with [[Android]] <code>.apk</code> files) == Overview == The <code>apk-tools</code> package provides APK. The table below shows commonly used commands.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper|title=Alpine Package Keeper - Alpine Wiki|accessdate=12 February 2026}}</ref> {| class="wikitable" |+Commonly used APK commands !Command !Action |- |<code>apk add <package_name></code> |Adds a package to the system and modifies WORLD file, commits changes afterwards |- |<code>apk del <package_name></code> |Deletes a package from the system and modifies WORLD file, commits changes afterwards |- |<code>apk fix <package_name></code> |Fixes (attempts to) a package via reinstall and/or upgrading without modifying WORLD |- |<code>apk update</code> |Updates repository index, Typically ran after modifying repository file |- |<code>apk upgrade <optional_package></code> |Upgrade packages on the system, optionally upgrade only one package by specifying it. |- |<code>apk cache <option></code> |Manages the local package cache |- |<code>apk query <package_name></code> |Combines <code>info</code>, <code>list</code>, and <code>search</code> commands through your installed packages and outputs information in a human-readable format |- |<code>apk info [flags] [packages]</code> |Lists all information about installed packages and allows you to search through it with given flags |} == Repositories == Alpine has three official [[Repository|package repositories]]:<ref>{{Cite|title=Repositories - Official repositories - Alpine Wiki|url=https://wiki.alpinelinux.org/wiki/Repositories#Official_repositories|accessdate=12 February 2026}}</ref> * <code>main</code> packages are stable and officially supported by the Alpine core team. * <code>community</code> packages are generally stable but not officially supported by the Alpine core team. * <code>testing</code> packages are newer but may be unstable. <code>testing</code> is only available on the <code>edge</code> branch. === Managing repositories === {{GuideWarning}} The <code>/etc/apk/repositories</code> file is a newline-separated list of repositories that APK will use.<ref>{{Cite|url=https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html|title=Working with the Alpine Package Keeper (apk), ''Alpine User Handbook''|accessdate=10 February 2026}}</ref> The built-in <code>setup-apkrepos</code> script manages <code>/etc/apk/repositories</code> for you:<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_configuration_management_scripts#setup-apkrepos|title=Alpine configuration management scripts - setup-apkrepos - Alpine Wiki|accessdate=31 May 2026}}</ref> * <code>setup-apkrepos -c</code> will enable the <code>community</code> repository. * <code>setup-apkrepos -f</code> will make APK use the fastest mirror for all repositories. See the [https://wiki.alpinelinux.org/wiki/Alpine_configuration_management_scripts#setup-apkrepos official documentation for <code>setup-apkrepos</code>] for a complete list of options. == Packages == Official software on the Alpine Linux repositories are named "''a-packs''" and have the extension <code>.apk</code>. You can edit which repositories you'd like to access by editing <code>/etc/apk/repositories</code>, commenting/uncommenting any repository you'd like. Upon saving the file, run <code>apk update</code> to update the repository index. APK will automatically echo how many packages are currently available on enabled repositories upon completing the updates.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Repositories|title=Repositories - Alpine Wiki|accessdate=12 February 2026}}</ref> == Configuration == APK can be configured by editing <code>/etc/config/apk</code>. If it does not exist, create it with <code>touch /etc/config/apk</code>. This will override the default APK config located in <code>/lib/apk/config</code>.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#Configuration_file|title=Alpine Package Keeper - Configuration File - Alpine Wiki|accessdate=12 February 2026}}</ref> === World === The <code>/etc/apk/world</code> file describes desired system states in a plain text file and uses unique syntax to configure package installation. Should you edit the file, run <code>apk fix</code> to apply changes. The <code>world</code> file must be in order upon running <code>apk fix</code>, else the package manager refuses to apply any constraints to the adjusted file; hence why APK will never leave a system unbootable.<ref>{{Cite|url=https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#World|title=Alpine Package Keeper - World - Alpine Wiki|accessdate=12 February 2026}}</ref> == References == <references /> d52e30a5abb2e7326d195cf2ddf6b082053094b2 0 1265 5636 5616 2026-05-31T08:10:22Z Int 401 Place in Software category wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Wine | image = [[File:Wine Logo.png|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = Multilingual | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. == Installation == === [[Arch Linux]] === Stable: <syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight> Staging: <syntaxhighlight lang="sh">sudo pacman -S wine-staging</syntaxhighlight> == Usage == Wine is a [[CLI|command-line]] program. Provide a Windows executable file for Wine to run: <syntaxhighlight lang="sh">wine <path to .exe></syntaxhighlight> === Prefixes === Wine stores configuration files and installed programs inside a ''Wine prefix''. Wine prefixes contain a minimal Windows filesystem (a.k.a. ''C: drive''). The default Wine prefix is <code>~/.wine</code>. You can modify the <code>WINEPREFIX</code> environment variable to change it. For example, to use the directory <code>myprefix/</code> as the Wine prefix to run <code>application.exe</code>: <syntaxhighlight lang="sh">WINEPREFIX=myprefix wine application.exe</syntaxhighlight> == Performance == === dxvk === By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). == References == <references /> 689266e25e413c464420e2e7570bd824487874c4 6 1311 5637 2026-05-31T09:10:36Z Madonuko 140 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 1312 5641 2026-05-31T09:58:11Z Madonuko 140 init wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Kdenlive_colored_dark_logo.png|frameless]] | caption = Kdenlive logo | title = Kdenlive | releasestatus = Maintained | lastrelease = 26.04.1, 2026-05-05 | firstrelease = 0.2.0, 2003-01-21 | languages = [[C++]] | developers = [[KDE]] | website = [https://kdenlive.org kdenlive.org] | license = [[GPL-3.0-only]] | sourcecode = https://invent.kde.org/multimedia/kdenlive }} Kdenlive (or stylised as ''kdenlive'') is an [[open source]] graphical [[Video Editing|video editor]] created with [[Qt]], [[KDE Frameworks]], and the [[MLT]] multimedia framework. It is usually regarded as the most popular open source video editor on [[Linux]].<ref>[https://flixier.com/blog/video-editing-software-for-linux Best Video Editing Software for Linux in 2026: 11 Open-Source & Pro Options], Flixier, 2026 (Accessed: 2026-05-31)</ref><ref>[https://www.fosslinux.com/6506/top-10-best-video-editors-for-linux.htm 6 Best Video Editors for Linux (2026 Professional Guide)], Foss Linux, 2026 (Accessed: 2026-05-31)</ref><ref>[https://itsfoss.com/best-video-editing-software-linux/ Best Free Video Editing Software for Linux], It's FOSS, 2024 (Accessed: 2026-05-31)</ref> The name ''Kdenlive'' stands for ''KDE Non-Linear Video Editor''<ref>[https://kdenlive.org/ Kdenlive], Kdenlive, 2026 (Accessed: 2026-05-31)</ref>, where ''[[wikipedia:Non-Linear Editing|Non-Linear]]'' refers to a method of video editing that does not modify the source, unlike traditional linear editing where the physical video tapes are modified.<ref>[https://martech.zone/acronym/nle/What Is NLE? Non-Linear Editing], Martech Zone Acronyms, 2026 (Accessed: 2026-05-31)</ref> Kdenlive also comes with some basic audio editing features and effects.<ref>[https://docs.kdenlive.org/en/effects_and_filters/audio.html Audio Tools], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> == History == == Usage == [[File:Kdenlive madonuko undred-cover.jpg|right|thumb|Video editing on Kdenlive with a custom layout consisting of floating windows.]] An [https://docs.kdenlive.org/en/getting_started/quickstart.html official quick start guide] is available on their official documentation. Just like most other modern video editors, editing in Kdenlive is based around 3 core concepts: tracks/layers in timelines (seen in the bottom left window in the image), effects/compositions (seen in the top left window), and source clips (seen in the bottom right window). Users can drag and drop source clips into the timeline, and then add compositions and effects to the clips. These compositions and effects can alter how the clips are displayed in the final video output, such as resizing and blurring the clip. Some compositions can act as transitions between clips.<ref>[https://docs.kdenlive.org/en/compositing.html Transitions and Compositions], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> == See Also == * [https://docs.kdenlive.org/en/index.html Kdenlive Manual] == References == 76dca0def1ff0bf277c2596095903d87685f9179 5642 5641 2026-05-31T10:59:10Z Madonuko 140 fix wikipedia dead link wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Kdenlive_colored_dark_logo.png|frameless]] | caption = Kdenlive logo | title = Kdenlive | releasestatus = Maintained | lastrelease = 26.04.1, 2026-05-05 | firstrelease = 0.2.0, 2003-01-21 | languages = [[C++]] | developers = [[KDE]] | website = [https://kdenlive.org kdenlive.org] | license = [[GPL-3.0-only]] | sourcecode = https://invent.kde.org/multimedia/kdenlive }} Kdenlive (or stylised as ''kdenlive'') is an [[open source]] graphical [[Video Editing|video editor]] created with [[Qt]], [[KDE Frameworks]], and the [[MLT]] multimedia framework. It is usually regarded as the most popular open source video editor on [[Linux]].<ref>[https://flixier.com/blog/video-editing-software-for-linux Best Video Editing Software for Linux in 2026: 11 Open-Source & Pro Options], Flixier, 2026 (Accessed: 2026-05-31)</ref><ref>[https://www.fosslinux.com/6506/top-10-best-video-editors-for-linux.htm 6 Best Video Editors for Linux (2026 Professional Guide)], Foss Linux, 2026 (Accessed: 2026-05-31)</ref><ref>[https://itsfoss.com/best-video-editing-software-linux/ Best Free Video Editing Software for Linux], It's FOSS, 2024 (Accessed: 2026-05-31)</ref> The name ''Kdenlive'' stands for ''KDE Non-Linear Video Editor''<ref>[https://kdenlive.org/ Kdenlive], Kdenlive, 2026 (Accessed: 2026-05-31)</ref>, where ''[[wikipedia:Non-linear editing|Non-Linear]]'' refers to a method of video editing that does not modify the source, unlike traditional linear editing where the physical video tapes are modified.<ref>[https://martech.zone/acronym/nle/What Is NLE? Non-Linear Editing], Martech Zone Acronyms, 2026 (Accessed: 2026-05-31)</ref> Kdenlive also comes with some basic audio editing features and effects.<ref>[https://docs.kdenlive.org/en/effects_and_filters/audio.html Audio Tools], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> == History == == Usage == [[File:Kdenlive madonuko undred-cover.jpg|right|thumb|Video editing on Kdenlive with a custom layout consisting of floating windows.]] An [https://docs.kdenlive.org/en/getting_started/quickstart.html official quick start guide] is available on their official documentation. Just like most other modern video editors, editing in Kdenlive is based around 3 core concepts: tracks/layers in timelines (seen in the bottom left window in the image), effects/compositions (seen in the top left window), and source clips (seen in the bottom right window). Users can drag and drop source clips into the timeline, and then add compositions and effects to the clips. These compositions and effects can alter how the clips are displayed in the final video output, such as resizing and blurring the clip. Some compositions can act as transitions between clips.<ref>[https://docs.kdenlive.org/en/compositing.html Transitions and Compositions], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> == See Also == * [https://docs.kdenlive.org/en/index.html Kdenlive Manual] == References == 4548f8268ca2be4e0cc59150d21a3948ed517729 5643 5642 2026-05-31T11:00:45Z Madonuko 140 fix nle acronym ref dead link wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Kdenlive_colored_dark_logo.png|frameless]] | caption = Kdenlive logo | title = Kdenlive | releasestatus = Maintained | lastrelease = 26.04.1, 2026-05-05 | firstrelease = 0.2.0, 2003-01-21 | languages = [[C++]] | developers = [[KDE]] | website = [https://kdenlive.org kdenlive.org] | license = [[GPL-3.0-only]] | sourcecode = https://invent.kde.org/multimedia/kdenlive }} Kdenlive (or stylised as ''kdenlive'') is an [[open source]] graphical [[Video Editing|video editor]] created with [[Qt]], [[KDE Frameworks]], and the [[MLT]] multimedia framework. It is usually regarded as the most popular open source video editor on [[Linux]].<ref>[https://flixier.com/blog/video-editing-software-for-linux Best Video Editing Software for Linux in 2026: 11 Open-Source & Pro Options], Flixier, 2026 (Accessed: 2026-05-31)</ref><ref>[https://www.fosslinux.com/6506/top-10-best-video-editors-for-linux.htm 6 Best Video Editors for Linux (2026 Professional Guide)], Foss Linux, 2026 (Accessed: 2026-05-31)</ref><ref>[https://itsfoss.com/best-video-editing-software-linux/ Best Free Video Editing Software for Linux], It's FOSS, 2024 (Accessed: 2026-05-31)</ref> The name ''Kdenlive'' stands for ''KDE Non-Linear Video Editor''<ref>[https://kdenlive.org/ Kdenlive], Kdenlive, 2026 (Accessed: 2026-05-31)</ref>, where ''[[wikipedia:Non-linear editing|Non-Linear]]'' refers to a method of video editing that does not modify the source, unlike traditional linear editing where the physical video tapes are modified.<ref>[https://martech.zone/acronym/nle/ What Is NLE? Non-Linear Editing], Martech Zone Acronyms, 2026 (Accessed: 2026-05-31)</ref> Kdenlive also comes with some basic audio editing features and effects.<ref>[https://docs.kdenlive.org/en/effects_and_filters/audio.html Audio Tools], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> == History == == Usage == [[File:Kdenlive madonuko undred-cover.jpg|right|thumb|Video editing on Kdenlive with a custom layout consisting of floating windows.]] An [https://docs.kdenlive.org/en/getting_started/quickstart.html official quick start guide] is available on their official documentation. Just like most other modern video editors, editing in Kdenlive is based around 3 core concepts: tracks/layers in timelines (seen in the bottom left window in the image), effects/compositions (seen in the top left window), and source clips (seen in the bottom right window). Users can drag and drop source clips into the timeline, and then add compositions and effects to the clips. These compositions and effects can alter how the clips are displayed in the final video output, such as resizing and blurring the clip. Some compositions can act as transitions between clips.<ref>[https://docs.kdenlive.org/en/compositing.html Transitions and Compositions], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> == See Also == * [https://docs.kdenlive.org/en/index.html Kdenlive Manual] == References == a0a47aad5a83b9ba727a86f31f0aace300a05ad1 5661 5643 2026-06-01T01:42:17Z Madonuko 140 /* Customisation */ wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Kdenlive_colored_dark_logo.png|frameless]] | caption = Kdenlive logo | title = Kdenlive | releasestatus = Maintained | lastrelease = 26.04.1, 2026-05-05 | firstrelease = 0.2.0, 2003-01-21 | languages = [[C++]] | developers = [[KDE]] | website = [https://kdenlive.org kdenlive.org] | license = [[GPL-3.0-only]] | sourcecode = https://invent.kde.org/multimedia/kdenlive }} Kdenlive (or stylised as ''kdenlive'') is an [[open source]] graphical [[Video Editing|video editor]] created with [[Qt]], [[KDE Frameworks]], and the [[MLT]] multimedia framework. It is usually regarded as the most popular open source video editor on [[Linux]].<ref>[https://flixier.com/blog/video-editing-software-for-linux Best Video Editing Software for Linux in 2026: 11 Open-Source & Pro Options], Flixier, 2026 (Accessed: 2026-05-31)</ref><ref>[https://www.fosslinux.com/6506/top-10-best-video-editors-for-linux.htm 6 Best Video Editors for Linux (2026 Professional Guide)], Foss Linux, 2026 (Accessed: 2026-05-31)</ref><ref>[https://itsfoss.com/best-video-editing-software-linux/ Best Free Video Editing Software for Linux], It's FOSS, 2024 (Accessed: 2026-05-31)</ref> The name ''Kdenlive'' stands for ''KDE Non-Linear Video Editor''<ref>[https://kdenlive.org/ Kdenlive], Kdenlive, 2026 (Accessed: 2026-05-31)</ref>, where ''[[wikipedia:Non-linear editing|Non-Linear]]'' refers to a method of video editing that does not modify the source, unlike traditional linear editing where the physical video tapes are modified.<ref>[https://martech.zone/acronym/nle/ What Is NLE? Non-Linear Editing], Martech Zone Acronyms, 2026 (Accessed: 2026-05-31)</ref> Kdenlive also comes with some basic audio editing features and effects.<ref>[https://docs.kdenlive.org/en/effects_and_filters/audio.html Audio Tools], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> == History == == Usage == [[File:Kdenlive madonuko undred-cover.jpg|right|thumb|Video editing on Kdenlive with a custom layout consisting of floating windows.]] An [https://docs.kdenlive.org/en/getting_started/quickstart.html official quick start guide] is available on their official documentation. Just like most other modern video editors, editing in Kdenlive is based around 3 core concepts: tracks/layers in timelines (seen in the bottom left window in the image), effects/compositions (seen in the top left window), and source clips (seen in the bottom right window). Users can drag and drop source clips into the timeline, and then add compositions and effects to the clips. These compositions and effects can alter how the clips are displayed in the final video output, such as resizing and blurring the clip. Some compositions can act as transitions between clips.<ref>[https://docs.kdenlive.org/en/compositing.html Transitions and Compositions], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> === Customisation === Keyboard shortcuts and layouts in Kdenlive are also highly customisable. When the titlebars are enabled in the ''View'' menu, different parts of the layout can be dragged and dropped onto other parts of the window. Floating windows and autohide are also supported. Custom layouts can also be saved in the ''View'' menu. Keyboard layouts can be customised by right-clicking the corresponding entry in the context menu. == See Also == * [https://docs.kdenlive.org/en/index.html Kdenlive Manual] == References == 9082339585c16d4b364a5d29ca0c4c8c9edff07e 5662 5661 2026-06-01T09:16:09Z Madonuko 140 /* Customisation */ configuring keyboard shortcuts wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Kdenlive_colored_dark_logo.png|frameless]] | caption = Kdenlive logo | title = Kdenlive | releasestatus = Maintained | lastrelease = 26.04.1, 2026-05-05 | firstrelease = 0.2.0, 2003-01-21 | languages = [[C++]] | developers = [[KDE]] | website = [https://kdenlive.org kdenlive.org] | license = [[GPL-3.0-only]] | sourcecode = https://invent.kde.org/multimedia/kdenlive }} Kdenlive (or stylised as ''kdenlive'') is an [[open source]] graphical [[Video Editing|video editor]] created with [[Qt]], [[KDE Frameworks]], and the [[MLT]] multimedia framework. It is usually regarded as the most popular open source video editor on [[Linux]].<ref>[https://flixier.com/blog/video-editing-software-for-linux Best Video Editing Software for Linux in 2026: 11 Open-Source & Pro Options], Flixier, 2026 (Accessed: 2026-05-31)</ref><ref>[https://www.fosslinux.com/6506/top-10-best-video-editors-for-linux.htm 6 Best Video Editors for Linux (2026 Professional Guide)], Foss Linux, 2026 (Accessed: 2026-05-31)</ref><ref>[https://itsfoss.com/best-video-editing-software-linux/ Best Free Video Editing Software for Linux], It's FOSS, 2024 (Accessed: 2026-05-31)</ref> The name ''Kdenlive'' stands for ''KDE Non-Linear Video Editor''<ref>[https://kdenlive.org/ Kdenlive], Kdenlive, 2026 (Accessed: 2026-05-31)</ref>, where ''[[wikipedia:Non-linear editing|Non-Linear]]'' refers to a method of video editing that does not modify the source, unlike traditional linear editing where the physical video tapes are modified.<ref>[https://martech.zone/acronym/nle/ What Is NLE? Non-Linear Editing], Martech Zone Acronyms, 2026 (Accessed: 2026-05-31)</ref> Kdenlive also comes with some basic audio editing features and effects.<ref>[https://docs.kdenlive.org/en/effects_and_filters/audio.html Audio Tools], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> == History == == Usage == [[File:Kdenlive madonuko undred-cover.jpg|right|thumb|Video editing on Kdenlive with a custom layout consisting of floating windows.]] An [https://docs.kdenlive.org/en/getting_started/quickstart.html official quick start guide] is available on their official documentation. Just like most other modern video editors, editing in Kdenlive is based around 3 core concepts: tracks/layers in timelines (seen in the bottom left window in the image), effects/compositions (seen in the top left window), and source clips (seen in the bottom right window). Users can drag and drop source clips into the timeline, and then add compositions and effects to the clips. These compositions and effects can alter how the clips are displayed in the final video output, such as resizing and blurring the clip. Some compositions can act as transitions between clips.<ref>[https://docs.kdenlive.org/en/compositing.html Transitions and Compositions], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> === Customisation === Keyboard shortcuts and layouts in Kdenlive are also highly customisable. When the titlebars are enabled in the ''View'' menu, different parts of the layout can be dragged and dropped onto other parts of the window. Floating windows and autohide are also supported. Custom layouts can also be saved in the ''View'' menu. Keyboard layouts can be customised by right-clicking the corresponding entry in the menu, or in ''Settings'' > ''Configure Keyboard Shortcuts…'' ({{Keypress|Ctrl|Alt|,}}). == See Also == * [https://docs.kdenlive.org/en/index.html Kdenlive Manual] == References == 130ea9fc8a41d01c8770973eb1a250d9a9f5759d 5663 5662 2026-06-01T09:55:26Z Madonuko 140 /* History */ populate a bit wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | image = [[File:Kdenlive_colored_dark_logo.png|frameless]] | caption = Kdenlive logo | title = Kdenlive | releasestatus = Maintained | lastrelease = 26.04.1, 2026-05-05 | firstrelease = 0.2.0, 2003-01-21 | languages = [[C++]] | developers = [[KDE]] | website = [https://kdenlive.org kdenlive.org] | license = [[GPL-3.0-only]] | sourcecode = https://invent.kde.org/multimedia/kdenlive }} Kdenlive (or stylised as ''kdenlive'') is an [[open source]] graphical [[Video Editing|video editor]] created with [[Qt]], [[KDE Frameworks]], and the [[MLT]] multimedia framework. It is usually regarded as the most popular open source video editor on [[Linux]].<ref>[https://flixier.com/blog/video-editing-software-for-linux Best Video Editing Software for Linux in 2026: 11 Open-Source & Pro Options], Flixier, 2026 (Accessed: 2026-05-31)</ref><ref>[https://www.fosslinux.com/6506/top-10-best-video-editors-for-linux.htm 6 Best Video Editors for Linux (2026 Professional Guide)], Foss Linux, 2026 (Accessed: 2026-05-31)</ref><ref>[https://itsfoss.com/best-video-editing-software-linux/ Best Free Video Editing Software for Linux], It's FOSS, 2024 (Accessed: 2026-05-31)</ref> The name ''Kdenlive'' stands for ''KDE Non-Linear Video Editor''<ref>[https://kdenlive.org/ Kdenlive], Kdenlive, 2026 (Accessed: 2026-05-31)</ref>, where ''[[wikipedia:Non-linear editing|Non-Linear]]'' refers to a method of video editing that does not modify the source, unlike traditional linear editing where the physical video tapes are modified.<ref>[https://martech.zone/acronym/nle/ What Is NLE? Non-Linear Editing], Martech Zone Acronyms, 2026 (Accessed: 2026-05-31)</ref> Kdenlive also comes with some basic audio editing features and effects.<ref>[https://docs.kdenlive.org/en/effects_and_filters/audio.html Audio Tools], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> == History == The history of Kdenlive is documented [https://kdenlive.org/about/ on the official site]. While it was mentioned that the project was launched with version 0.2.3 in October 2003, the first tag is in fact 0.2.0, created on 2003-01-21.<ref>[https://invent.kde.org/multimedia/kdenlive/-/tags?sort=version_asc Tags · Multimedia / Kdenlive], GitLab (Accessed: 2026-06-01)</ref> == Usage == [[File:Kdenlive madonuko undred-cover.jpg|right|thumb|Video editing on Kdenlive with a custom layout consisting of floating windows.]] An [https://docs.kdenlive.org/en/getting_started/quickstart.html official quick start guide] is available on their official documentation. Just like most other modern video editors, editing in Kdenlive is based around 3 core concepts: tracks/layers in timelines (seen in the bottom left window in the image), effects/compositions (seen in the top left window), and source clips (seen in the bottom right window). Users can drag and drop source clips into the timeline, and then add compositions and effects to the clips. These compositions and effects can alter how the clips are displayed in the final video output, such as resizing and blurring the clip. Some compositions can act as transitions between clips.<ref>[https://docs.kdenlive.org/en/compositing.html Transitions and Compositions], Kdenlive 26.04 Manual 26.04 documentation, 2026 (Accessed: 2026-05-31)</ref> === Customisation === Keyboard shortcuts and layouts in Kdenlive are also highly customisable. When the titlebars are enabled in the ''View'' menu, different parts of the layout can be dragged and dropped onto other parts of the window. Floating windows and autohide are also supported. Custom layouts can also be saved in the ''View'' menu. Keyboard layouts can be customised by right-clicking the corresponding entry in the menu, or in ''Settings'' > ''Configure Keyboard Shortcuts…'' ({{Keypress|Ctrl|Alt|,}}). == See Also == * [https://docs.kdenlive.org/en/index.html Kdenlive Manual] == References == 6dd05099cc6b9c431cc3f97e038c18d8a2bd52de 0 1231 5645 5412 2026-05-31T13:15:01Z Lurxcha 418 Added the music player Strawberry to the list, due to its many features. Strawberry link does not exist yet. wikitext text/x-wiki {{Stub}} This page lists local music playing [[software]] to enjoy your local music collection of flacs, mp3s, etc. {| class="wikitable" !Name |External Link !Description |- |[[Elisa]] |[https://apps.kde.org/de/elisa/ Website] |Simple music player made by [[KDE]]. |- |DeaDBeeF |[https://deadbeef.sourceforge.io Website] |Modular audio player which supports plugins and customisation. |- |[[Strawberry]] |[https://www.strawberrymusicplayer.org/ Website] |Customizable, feature-rich music player written in C++ |} df88bcb2d71bfc9a810a8f49040f2fc35a57f236 0 677 5646 5111 2026-05-31T14:55:15Z Strangely Human Feeling 415 /* Installation */ added wiki links wikitext text/x-wiki [[File:Flatpak Logo.png|thumb|Flatpak's logo.]] Flatpak is a universal packaging system and runtime for installing packages separate from the system packages. Mainly meant for desktop applications, Flatpak allows application developers to distribute packages without needing to worry about distro compatibility because Flatpak installs its own runtime dependencies. It claims to improve security through sandboxing providing the user the ability to give or revoke permissions for a given application. Flatpak is installed by default on many distributions and it's main distribution platform is Flathub. == Installation == Flatpak comes preinstalled on many distributions such as [[Linux Mint]] and [[Fedora Linux|Fedora]] but can be installed through most distro's package repositories if not present. ==== KDE Discover ==== KDE Discover includes the ability to install Flatpak and enable Flathub through its graphical user interface. Go to the setting tab and install the Flatpak backend then restart Discover then go back to the settings and enable Flathub. ==== CLI Install on Ubuntu ==== To install Flatpak from the CLI run:<syntaxhighlight lang="bash"> sudo apt install flatpak </syntaxhighlight>To enable Flathub from the CLI run:<syntaxhighlight lang="bash"> flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo </syntaxhighlight>If you make use of GNOME Software you can install the integration plugin:<syntaxhighlight lang="bash"> sudo apt install gnome-software-plugin-flatpak </syntaxhighlight>For the KDE Discover plugin run:<syntaxhighlight lang="bash"> sudo apt install plasma-discover-backend-flatpak </syntaxhighlight>For other distros read the guides on [https://flathub.org/setup Flathub.org]. == Compatibility == Flatpak allows improved package compatibility through its use of its own runtime dependencies. Packages can run through Flatpak where it might not be possible to run on natively such as: * Applications that require a newer version of glibc than whats available on an stable release distro such as Rocky Linux 8. * Applications that depend on glibc such as Steam running on a distro using musl like Alpine Linux. * Multilib packages such as Steam or Wine on distros without multilib support such as CentOS Stream 10. == Sandboxing == Package permissions can be managed by the user through a graphical user interface with Flatseal which can be installed as a Flatpak. == Flathub Package Verification == Flathub has a package verification system that allows packages maintained by the official developers to have a verification tick.<ref>[https://docs.flathub.org/docs/for-app-authors/verification Verification | Flathub Documentation], Flathub Team, 2025 (Accessed: 2025-06-22)</ref> This has lead to some confusion where verification is mistaken for package safety. Linux Mint hides unverified Flatpaks from Software Manager by default Starting in version 22.<ref>[https://www.omgubuntu.co.uk/2024/06/linux-mint-will-hide-unverified-flatpaks Linux Mint Will Hide Unverified Flatpaks in Software Manager - OMG! Ubuntu], Joey Sneddon, 2024 (Accessed: 2025-06-22)</ref> == References == a980dc840d0a2ed1e7446fcdabcb4716ab3c2345 6 1313 5647 2026-05-31T17:09:37Z Lurxcha 418 wikitext text/x-wiki Picture of the Strawberry menu in dark mode while playing a song. In the background is the album picture of the song. 380a14b3c2e20136355ecb2d44ad683e36279e4b 0 1314 5648 2026-05-31T17:33:41Z Lurxcha 418 Started with the basic information about Strawberry music player including a screenshot of the menu wikitext text/x-wiki [[File:Image of Strawberry Player.png|alt=Picture of the Strawberry menu in dark mode while playing a song. In the background is the album picture of the song.|thumb|500x500px|Strawberry menu]] Strawberry is a [[Music Players|music player]] made for audiophiles, offering a clean, minimalistic and intuitive [[GUI|graphical user interface]] <ref>{{Cite|url=https://www.tech2geek.net/strawberry-music-player-a-powerful-open-source-organizer-for-audiophiles/|title=Strawberry Music Player: A Powerful, Open-Source Organizer for Audiophiles|author=Clara Moreau|year=2025-07-06|accessdate=2026-05-31}}</ref>. Originally it was forked from [[wikipedia:Clementine_(software)|Clementine]] in 2018. The [[Software]] is written in [[C++]] using the [[wikipedia:Qt_(software)|Qt]]<nowiki/>framework<ref>{{Cite|url=https://itsfoss.com/strawberry-music-player/|title=Strawberry Music Player: A fork of Clementine|author=John Paul Wohlscheid|year=2020-10-29|accessdate=2026-05-31}}</ref> 7bdb2a36be7bf45263f77736bf8e33183fcdbc82 5650 5648 2026-05-31T17:43:06Z Lurxcha 418 solved a minor space mistake wikitext text/x-wiki [[File:Image of Strawberry Player.png|alt=Picture of the Strawberry menu in dark mode while playing a song. In the background is the album picture of the song.|thumb|500x500px|Strawberry menu]] Strawberry is a [[Music Players|music player]] made for audiophiles, offering a clean, minimalistic and intuitive [[GUI|graphical user interface]] <ref>{{Cite|url=https://www.tech2geek.net/strawberry-music-player-a-powerful-open-source-organizer-for-audiophiles/|title=Strawberry Music Player: A Powerful, Open-Source Organizer for Audiophiles|author=Clara Moreau|year=2025-07-06|accessdate=2026-05-31}}</ref>. Originally it was forked from [[wikipedia:Clementine_(software)|Clementine]] in 2018. The [[Software]] is written in [[C++]] using the [[wikipedia:Qt_(software)|Qt]]<nowiki/> framework<ref>{{Cite|url=https://itsfoss.com/strawberry-music-player/|title=Strawberry Music Player: A fork of Clementine|author=John Paul Wohlscheid|year=2020-10-29|accessdate=2026-05-31}}</ref> 8da48293380dd2008bc6a99bdfca5015bc9787f2 5651 5650 2026-05-31T17:56:21Z Lurxcha 418 changed Qt link from wikipedia.org link to foss.wiki link wikitext text/x-wiki [[File:Image of Strawberry Player.png|alt=Picture of the Strawberry menu in dark mode while playing a song. In the background is the album picture of the song.|thumb|500x500px|Strawberry menu]] Strawberry is a [[Music Players|music player]] made for audiophiles, offering a clean, minimalistic and intuitive [[GUI|graphical user interface]] <ref>{{Cite|url=https://www.tech2geek.net/strawberry-music-player-a-powerful-open-source-organizer-for-audiophiles/|title=Strawberry Music Player: A Powerful, Open-Source Organizer for Audiophiles|author=Clara Moreau|year=2025-07-06|accessdate=2026-05-31}}</ref>. Originally it was forked from [[wikipedia:Clementine_(software)|Clementine]] in 2018. The [[Software]] is written in [[C++]] using the [[Qt]] framework<ref>{{Cite|url=https://itsfoss.com/strawberry-music-player/|title=Strawberry Music Player: A fork of Clementine|author=John Paul Wohlscheid|year=2020-10-29|accessdate=2026-05-31}}</ref> 95c9c3d6eab302a434672362a1b0016f2b6a0f9c 0 198 5649 5609 2026-05-31T17:34:13Z Lawl 419 add calculate linux to list of gentoo based distros wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- ![https://www.calculate-linux.org/ Calculate] !A user friendly Gentoo based distribution focused on ease of use and backwards compatibility with Gentoo. |- |[[openFyde]] |A fully open-source fork of FydeOS. It strips out proprietary drivers and commercial patches to provide a completely open-source, decoupled ChromiumOS experience. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 5b54ca2c8049685a984c4e9d60c703dfe8cef42e 5652 5649 2026-05-31T18:02:37Z Lawl 419 add oasis, derive, kiss, gkiss and secureblue wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Secureblue]] |A security focused desktop and server Linux distribution built on [[Fedora Atomic]]. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[https://www.calculate-linux.org/ Calculate] |A user friendly Gentoo based distribution focused on ease of use and backwards compatibility with Gentoo. |- |[[openFyde]] |A fully open-source fork of FydeOS. It strips out proprietary drivers and commercial patches to provide a completely open-source, decoupled ChromiumOS experience. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[Dérive Linux]] |Dérive is a simple and independent Linux distribution based on the Musl libc and Busybox. |- |[[GKISS Linux]] |A fork of the original KISS Linux that uses the GNU libc rather than the Musl libc to add extra compatability. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[KISS Linux]] |A Linux distribution focused on simplicity and transparency. Maintained by the KISS community rather than the original creator. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- ||[[Oasis Linux]] |Oasis is a small, fully statically linked BSD like Linux distribution. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |- == References == 85c7e1f88833ede38a798123acfa337c74d5fad4 0 394 5653 5362 2026-05-31T18:29:11Z MysteryBirb 353 Added BSD foss wiki link wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel == BSD Based == {| class="wikitable" |- ! OS !! Description |- | [[BSD|Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} == Darwin Based == {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} == Solaris Based == {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} == Other UNIX-like == {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} == L4 based == {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} == Other Operating Systems == {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An Operating System originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[RISC OS]] | An open source operating system designed in Cambridge, England by Acorn. First released in 1987, its origins can be traced back to the original team that developed the Arm microprocessor. |- |} 0308920b92363b1e6bec4abebf9ff9a913b959ac 5655 5653 2026-05-31T18:30:42Z Matthias von Schwarzwald 361 /* Other Operating Systems */ Typos wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel == BSD Based == {| class="wikitable" |- ! OS !! Description |- | [[BSD|Berkeley Software Distribution (BSD)]] | A Discontinued Unix Like Operating System designed to improve on Bell Labs' UNIX |- | [[DragonFly BSD]] | an operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- | [[FreeBSD]] | an operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- | [[GhostBSD]] | a rolling release operating system based on [[FreeBSD]] |- | [[HardenedBSD]] | a security-enhanced fork of [[FreeBSD]] |- | [[NetBSD]] | an operating system focused on code clarity, careful design, and portability across many computer architectures |- | [[OpenBSD]] | an operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- | [[TrueNAS Core]] | originally known as FreeNAS and based on [[FreeBSD]] this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} == Darwin Based == {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} == Solaris Based == {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} == Other UNIX-like == {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} == L4 based == {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} == Other Operating Systems == {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An operating system originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs|TempleOS]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[RISC OS]] | An open-source operating system designed in Cambridge, England by Acorn. First released in 1987, its origins can be traced back to the original team that developed the Arm microprocessor. |- |} 636e740b8b8c8f92f5bbeb08d270344b8ae599af 0 1315 5654 2026-05-31T18:29:23Z Uniolo 345 Create as redirect to BSD so it can be linked to directly wikitext text/x-wiki #redirect [[BSD]] 856560ad05b60ee1b9f174cb8a51f27aa30f7fdb 0 653 5656 5369 2026-05-31T18:39:51Z Strangely Human Feeling 415 made website in infobox hyperlink wikitext text/x-wiki {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox | title = Pop!_OS | image = [[File:Pop! OS Icon.svg|frameless]] | caption = The Pop!_OS logo | releasestatus = Maintained | packagemanager = [[APT]] | defaultdesktops = COSMIC | usagetype = Desktop | architectures = x86_64 | website = https://system76.com/pop | releasemodel = Stable }} Pop!_OS is a free and open-source [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]] called [[COSMIC]]. Pop!OS is developed by the American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. [[File:Poposrice.png|border|right|frameless|346x346px]] == <u>Features</u> == * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle 14beef557f368eac3f0fb6677653dece5b74d63c 0 174 5657 4208 2026-05-31T19:14:29Z Lawl 419 add to the fun fact secttion wikitext text/x-wiki {{Cleanup|Incomplete page}} [[Category:Terminology]] [[File:Btop.png|alt=Btop System Monitor|thumb|Btop, a terminal-based system monitoring tool.]] A terminal user interface (TUI) is a form of user interface where a program prints special characters that are interpreted by the terminal renderer and are completely invisible, but manipulate the way the terminal renders stuff like for example changing the color of the following text, moving the cursor to an arbitrary place in the terminal, making text bold, making text italic, changing the color palette of the Linux TTY, and so much more. The program can also read in keyboard input by reading special character sequences in sent by the terminal driver. '''<u>FUN FACT</u>''': You may have tried using your arrow keys once or twice to move your cursor in a prompt from a program such as the [[Pacman]] package manager or something else that throws prompts for the user to answer. You may have noticed that instead of moving your cursor, the arrow keys send "garbage" text ("^[[D^[[C^[[A^[[B"). Programs such as [https://www.gnu.org/software/bash/ Bash] are able to move your cursor when you hit the arrow keys by actually reading and interpreting this "garbage" text in real-time using a terminal configuration mode called "raw mode" which is when the terminal disables a bunch of buffering settings that would normally require you to press ENTER before the terminal can see your user input. This "raw mode" is used in many, many areas of software that use terminal user interfaces, from text editors to file managers. {| class="wikitable" |+Terminal Manipulation Libraries !Library !Language !Developer !Description |- |[https://gitlab.com/Oglo12/otmlib Oglo's Terminal Manipulation Library] |[[C (programming language)|C]] |Jackson Novak (OgloTheNerd) |A single-header C99 library for manipulating the terminal. |- |[https://invisible-island.net/ncurses/ NCurses] |[[C (programming language)|C]] |Thomas Dickey |A library installed on most Linux and BSD systems for creating terminal user interfaces. |- |[https://crates.io/crates/crossterm Crossterm] |[[Rust]] |Timon |A cross-platform terminal manipulation library written in Rust. |- |[https://github.com/termbox/termbox2 Termbox2] |[[C (programming language)|C]] |Adam |A suckless single-header C library for manipulating the terminal. |- |[https://hackage.haskell.org/package/vty vty] |[[Haskell]] |Jonathan Daugherty |A TUI library in the niche of NCurses for Haskell. |} 89115f743bab6271876086cd4ac625fd7393184c 0 1316 5658 2026-05-31T19:41:17Z Lawl 419 make about half of a page dedicated to helping users pick a filesystem wikitext text/x-wiki [[Category:Guides]] {{Stub}} A filesystem is a method used by operating systems to perform numerous data operations, such as retrieving and storing data. There are numerous types of filesystems, built for numerous different purposes. Thanks to the flexibility that comes with Linux, you are free to choose whichever filesystem you want depending on what you want it to do. {| class="wikitable" |- ! Filesystem !! Description |- | [[ext4]] || An incredibly stable filesystem, often seen as the standard filesystem. Used by default by many Linux distributions. |- | [[xfs]] || A high performance 64-bit filesystem, often used in servers rather than desktop use. |- | [[btrfs]] || A filesystem made to address the lack of numerous data integrity features in existing filesystems. Features snapshots natively. |- | [[zfs]] || An advanced filesystem with many features, such as [[Copy On Write]], pooled storage, snapshots, and much more. |} 571b12654ab6aa149738e290ec3f5a4a01179edc 5659 5658 2026-05-31T20:39:49Z Lawl 419 add table to help users actually pick a filesystem wikitext text/x-wiki [[Category:Guides]] {{Stub}} A filesystem is a method used by operating systems to perform numerous data operations, such as retrieving and storing data. There are numerous types of filesystems, built for numerous different purposes. Thanks to the flexibility that comes with Linux, you are free to choose whichever filesystem you want depending on what you want it to do. <!-- TODO: add more filesystems --> {| class="wikitable" |- ! Filesystem !! Description |- | [[ext4]] || An incredibly stable filesystem, often seen as the standard filesystem. Used by default by many Linux distributions. |- | [[xfs]] || A high performance 64-bit filesystem, often used in servers rather than desktop use. |- | [[btrfs]] || A filesystem made to address the lack of numerous data integrity features in existing filesystems. Features snapshots natively. |- | [[zfs]] || An advanced filesystem with many features, such as [[Copy On Write]], pooled storage, snapshots, and much more. |} ==Picking a Filesystem== {| class="wikitable" |- ! Use case !! Appropriate filesystem |- | Desktop || [[ext4]] or [[btrfs]] |- | Server || [[xfs]] or [[zfs]] |- | Speed || [[xfs]] |- | Data integrity || [[zfs]] or [[btrfs]] |} Any filesystem can fit any use case. These are just what most people recommend you use for the specific use case. Another important thing to note is that just because a filesystem isn't at the top of, say, data integrity, that doesn't mean that you have a high chance of losing your data. It just means that there is a higher chance of data loss, however the chances are still tiny. 9336b13e981cf4ed2cd2ce93a3e7de327a874bbe 5660 5659 2026-05-31T23:22:35Z Stone574 416 wikitext text/x-wiki [[Category:Guides]] {{Stub}} A filesystem is a method used by operating systems to perform numerous data operations, such as retrieving and storing data. There are numerous types of filesystems, built for numerous different purposes. Thanks to the flexibility that comes with Linux, you are free to choose whichever filesystem you want depending on what you want it to do. <!-- TODO: add more filesystems --> {| class="wikitable" |- ! Filesystem !! Description |- | [[ext4]] || An incredibly stable filesystem, often seen as the standard filesystem. Used by default by many Linux distributions. |- | [[xfs]] || A high performance 64-bit filesystem, often used in servers rather than desktop use. |- | [[btrfs]] || A filesystem made to address the lack of numerous data integrity features in existing filesystems. Features snapshots natively. |- | [[zfs]] || An advanced filesystem with many features, such as [[Copy On Write]], pooled storage, snapshots, and much more. |- | [[nilfs2]] || A continuous snapshotting log-structured filesystem. It automatically retains past states of your data |} ==Picking a Filesystem== {| class="wikitable" |- ! Use case !! Appropriate filesystem |- | Desktop || [[ext4]] or [[btrfs]] |- | Server || [[xfs]] or [[zfs]] |- | Speed || [[xfs]] |- | Data integrity || [[zfs]] or [[btrfs]] |} Any filesystem can fit any use case. These are just what most people recommend you use for the specific use case. Another important thing to note is that just because a filesystem isn't at the top of, say, data integrity, that doesn't mean that you have a high chance of losing your data. It just means that there is a higher chance of data loss, however the chances are still tiny. f24a5980ab4fcf5633756081c26616dd6ad0835e 0 1317 5664 2026-06-01T16:22:59Z Lawl 419 add libc with comparison table wikitext text/x-wiki {{Stub}} "libc" is a phrase commonly used around Linux distributions. It is a shorthand term for the C standard library. It is vital to all Linux distributions, as it provides a wide range of functions and data types essential for developing C software. A libc should contain implementations of standard input-output operations, memory management functions, string manipulation routines, and much more. In Linux, there are often options when installing certain distributions where you choose which libc you want to use, and it is important to know the differences between certain libcs as different libcs provide different advantages over others. {| class="wikitable" ! libc !! Description |- | [[glibc]] || A libc with a focus on providing a consistent interface to access system resources to make developing cross-platform software easier. Often used in generic desktops or servers. |- | [[musl]] || A minimalist C library aiming at being more lightweight and secure than [[glibc]] and [[uClibc]]. Often used in environments where security, low resource usage, and auditability is wanted or needed. |- | [[uClibc]] || A minimalist C library aiming to be suitable for embedded computing. Has been widely replaced by [[musl]]. |} e3b44748d25aa724c5c9e1ee8f335020f737e973 0 214 5665 3684 2026-06-01T16:53:50Z Lurxcha 418 /* References */ + added the revealing date of Tux wikitext text/x-wiki [[Category:Mascots]] {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Tux | image = [[File:Tux.svg|frameless|size=200px]] | caption = Tux! }} '''Tux''' is the official mascot of [[Linux]], designed by Larry Ewing and revealed on May 9, 1996 by [[Linus Torvalds]].<ref>[https://www.xda-developers.com/linuxs-tux-the-penguin-mascot-turns-30-today/ Linux's adorable Tux the Penguin mascot turns 30 today, and the OG design is still being used], Simon Batt, 2026-05-09 (Accessed: 2026-06-01)</ref> Tux was created for the Linux 2.0 logo competition.<ref>[https://web.archive.org/web/20040407092622/http://www.cs.earlham.edu/~jeremiah/linux-pix/linux-logo.html Linux Logo Competition], Jeremiah E. Jahn, 2004-08-09 (Accessed: 2004-04-07)</ref> == References == <references /> 6c52d953a089dac73d66619a1f07089d9cd74c09 0 779 5666 3623 2026-06-02T00:41:42Z Matthias von Schwarzwald 361 Typos and grammar wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Haskell-Logo.svg]] | title = Haskell | releasestatus = Maintained | lastrelease = GHC 9.12.2 - 22 July 2025 / Haskell2010 | firstrelease = GHC 0.29 - 25 July 1996 / Haskell 1.0 | languages = Haskell | developers = The Haskell Foundation | designed by = ICFP | website = [https://haskell.org haskell.org] }} {{Needs Citations}}'''Haskell''' is a general-purpose, statically typed, purely functional programming language with type inference and lazy evaluation. = History = Functional programming in the 80's already had its roots in programming - such as the [[Lisp]] language. The new idea that sparked the creation of multiple functional languages (such as Miranda, SASL, KRC) was lazy evaluation - which later became one of the core Haskell ideas. In order to centralize functional programming efforts, multiple conferences (later merged into the International Conference on Functional Programming) were held in the 1990s. They resulted in the creation of '''Haskell'''. = Philosophy = Haskell as a functional language inherits its philosophy from math-oriented subjects such as lambda calculus or category theory. Despite its reputation, Haskell doesn't require prior knowledge of those in order to write basic code. = Installation & Usage = The most common Haskell compiler is [[GHC|'''GHC''' - Glasgow Haskell Compiler]]. The installation process shouldn't be harder than installing the `ghc` package with your favorite package manager. GHC provides essential tools, such as `ghc` and `ghci` - the compiler and interpreter. The latter can be used for simple inline operations, which is extremely useful when learning the language. = Useful Links = * [https://learnyouahaskell.github.io/ Learn You A Haskell] is a popular book (with a free online copy) which aims to explain Haskell without requiring prior knowledge in functional programming. * [https://hoogle.haskell.org/ Hoogle] is a Haskell API search engine, helpful in finding libraries etc. dc0ecc99a976a236f3364731f088518290378914 0 257 5667 4298 2026-06-02T02:07:02Z Strangely Human Feeling 415 Changed version number and Hyprland uses Lua now wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Hyprland logo.png|center|frame]] | caption = Hyprland logo | title = Hyprland | releasestatus = Maintained | lastrelease = v0.55.2, 2026-5-16 | languages = [[C++]] | developers = The Hyprwm team | website = [https://hypr.land/ hypr.land] }} [[Category:Wayland compositors]] [[Category:Window managers]] [[Category:Free software]] [[File:Hyprland.png|thumb|A desktop running Hyprland, showing [[Neofetch]] and a web browser.]] '''Hyprland''' is a dynamic tiling [[window manager]] and [[Wayland]] compositor. It was originally based on [[wlroots]] but migrated away from it towards its own rendering backend library [[aquamarine]] in version 0.42.0<ref>[https://hypr.land/news/independentHyprland/ Hyprland moves off wlroots], 2025-09-02 (Accessed 2025-09-02)</ref> It is known for its smooth animations, extensive visual customisation, and focus on aesthetics without sacrificing performance. Originally created by ''Vaxry'', Hyprland has grown into a full ecosystem of companion tools maintained by the Hyprwm team.<ref name="website">[https://hypr.land/ Hyprland], 2025-08-10 (Accessed: 2025-08-10)</ref> Hyprland currently uses Lua and it's deprecate hyprlang for configuration.<ref>https://hypr.land/news/update55/</ref> The project also provides several companion utilities, including: * '''Hyprcursor''' – a modern replacement for the traditional XCursor format, enabling animated and high-resolution cursors. * '''Hypridle''' – an idle management daemon similar to ''swayidle'', but tightly integrated with Hyprland’s configuration system. * '''Hyprpaper''' – a lightweight and optimised wallpaper manager for Wayland. * '''Hyprlock''' - a highly customizable and efficient Wayland lockscreen * '''Hyprpicker''' - a small utility for picking a color on your current screen == Features == Notable features of Hyprland include: * Smooth, GPU-accelerated animations for window movement, resizing, opening, and closing. * Gradient and colour customisation for window borders, with adjustable gradient angles. * Compatibility with most Wayland applications and support for [[XWayland]] to run X11 applications. * Auto-generated default configuration with sensible settings (e.g. touchpad tap-to-click enabled by default). * Highly modular design, allowing users to enable or disable features as needed. == See also == * [[Sway]] * [[Wayfire]] * [[River (window manager)|River]] == References == <references /> 57bf40e11a41fba3d50b35c90bc3a92053ae9ecb 0 769 5668 5619 2026-06-02T23:44:55Z Sivecano 413 Group wayland compositors by type, change columns wikitext text/x-wiki The choice of Wayland compositor is most comparable with choosing a window manager under [[X11]]. The Wayland compositor is in charge of rendering everything, routing input, configuring input/output devices as well as window management policy. The last one is what users are usually most interested in. A wayland compositor alone does not constitute a full desktop environment, so further components are usually needed. ==Compositors Associated to a Desktop Environment== These Compositors are associated to a specific desktop environment. They are not meant to be used outside of their desktop environments. {| class="wikitable" ! Compositor !! Desktop Environment !! Window Managagement Paradigm !! Written In !! Notes |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| Floating Window Management || [[C]] || The compositor of the GNOME desktop environment. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]] || Floating WIndow Management || [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp cosmic-comp github repo], pop-os team et al., 2025 (Accessed: 2026-05-25)</ref> |[[COSMIC]] | Floating or Stacking Window Management |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |} ==Floating Compositors== These compositors have what is often referred to as floating or stacking window management. This is same model you see on gnome and KDE where windows move around freely and are allowed to overlap each other. {| class="wikitable" ! Compositor !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. Not suitable for daily use |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- |} ==Tiling Compositors== These compositors perform what is referred to as tiling window management. Windows usually don't overlap and are automatically positioned to take up screen space. These often favour more advanced usage of virtual desktop or tags as well as a more keyboard-driven workflow. {| class="wikitable" ! Compositor !! Written In !! Notes |- | [[MangoWM]]<ref>[https://mangowc.vercel.app MangoWM Homepage]{{Dead Link|2026-05-26|404}} (Accessed: 2026-02-27)</ref> || [[C]] || Extremely customizable & performant Wayland compositor built on top of [[dwl]]. |- | [[Sway]] || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[Niri]] || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} == Other Compsitors == These compositors don't fit neatly into any of the above paradigms. {| class="wikitable" ! Compositor !! Written In !! Notes |- | [[river]]<ref>[https://codeberg.org/river/river Codeberg - A non-monolithic Wayland compositor] river, (Accessed: 2026-05-30)</ref> || [[zig]]|| A non-monolithic wayland compositor where window management is performed by an external program. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- |} ==References== <references /> 192925f96f9799a8b2edb27fe6c0c783a4e280ed 0 827 5669 4991 2026-06-03T16:27:20Z Imnotgoodatnames 121 clarified the wayland situation on slackware a bit wikitext text/x-wiki '''Wayland''' is a communication protocol that specifies the communication between a display server and its clients, as well as a [[C (programming language)|C]] library implementation of that protocol. A display server using the Wayland protocol is called a ''[[Wayland#Wayland compositors|Wayland compositor]]'', because it additionally performs the task of a compositing window manager. Wayland is developed by a group of volunteers initially led by Kristian Høgsberg as a free and open-source community-driven project with the aim of replacing the X Window System with a secure and simpler windowing system for [[Linux]] and other [[Unix]]-like operating systems. The project's source code is published under the terms of the [[MIT License]], a permissive free software license. The Wayland project also develops an implementation of a Wayland compositor called ''[[Wayland#Weston|Weston]]''. == Overview == [[File:Wayland_display_server_protocol.svg|right|thumb]] The Wayland Display Server project was started by [[Red Hat]] developer Kristian Høgsberg in 2008. Beginning around 2010, Linux desktop graphics have moved from having "a pile of rendering interfaces... all talking to the X server, which is at the center of the universe" towards putting the Linux kernel and its components (i.e. Direct Rendering Infrastructure (DRI), Direct Rendering Manager (DRM)) "in the middle", with "window systems like X and Wayland ... off in the corner". This will be "a much-simplified graphics system offering more flexibility and better performance". Høgsberg could have added an [[Xdmx|extension to X]] as many recent projects have done, but preferred to "[push] X out of the hotpath between clients and the hardware" for reasons explained in the project's FAQ. Wayland consists of a protocol and a reference implementation named [[Wayland#Weston|Weston]]. The project is also developing versions of [[GTK]] and [[Qt (software)|Qt]] that render to Wayland instead of to X. Most applications are expected to gain support for Wayland through one of these libraries without modification to the application. Initial versions of Wayland have not provided network transparency, though Høgsberg noted in 2010 that network transparency is possible. It was attempted as a Google Summer of Code project in 2011, but was not successful. Adam Jackson has envisioned providing remote access to a Wayland application by either "pixel-scraping" (like [[Virtual Network Computing|VNC]]) or getting it to send a "rendering command stream" across the network (as in [[Remote Desktop Protocol|RDP]], [[SPICE (protocol)|SPICE]] or [[X11]]). As of early 2013, Høgsberg was experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor. In August 2017, GNOME saw the first such pixel-scraping VNC server implementation under Wayland. In modern Wayland compositors, network transparency is handled in an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] that implements the RemoteDesktop portal. Many Wayland compositors also include an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] for common tasks such as a native file picker for native applications and sandboxes such as [[Flatpak]] ([https://github.com/flatpak/xdg-desktop-portal-gtk xdg-desktop-portal-gtk] is commonly used as a fallback filepicker), screen recording, network transparency, screenshots, color picking, and other tasks that could be seen as needing user intervention and being security risks otherwise. Note that xdg-desktop-portal is not Flatpak or Wayland-specific, and can be used with alternative packaging systems and windowing systems. == Wayland compositors == [[File:Window_(windowing_system).svg|right|thumb|Typical elements of a [[Window (computing)|window]]. The Wayland protocol does not specify what software is responsible for rendering the [[window decoration]].{{r|Graesslin 2013 decorations}}]] [[File:KDE_Plasma_5.24_on_Arch_Linux_screenshot.png|thumb|Plasma 5.24.0 (February 2022) on Wayland ({{code|kwin_wayland}} compositor) under [[Arch Linux]]]] [[Display server|Display servers]] that implement the Wayland display server protocol are also called ''Wayland compositors'' because they additionally perform the task of a [[compositing window manager]]. A library called '''wlroots''' is a modular Wayland implementation that functions as a base for several compositors A list of compositors can be found [[Wayland Compositors|here]]. === Weston === [[Weston (software)|Weston]] is a Wayland compositor previously developed as the [[reference implementation]] of the protocol by the Wayland project. It is written in [[C (programming language)|C]] and released under the [[MIT License]]. Weston officially supports only [[Linux]] due to dependencies on kernel-specific features such as kernel mode-setting (KMS), the Graphics Execution Manager (GEM), and [[udev]]. On Linux, it handles input via [[evdev]] and buffer management via Generic Buffer Management (GBM). A prototype port for [[FreeBSD]] was announced in 2013. The compositor supports High-bandwidth Digital Content Protection (HDCP) and uses GEM to share buffers between applications and the compositor. It features a plug-in architecture with "shells" that provide elements like docks and panels. Applications are responsible for rendering their own window decorations. Weston supports rendering via [[OpenGL ES]] or the [[pixman]] library for software rendering. The full OpenGL stack is avoided to prevent pulling in [[GLX]] and other [[X11|X Window System]] dependencies. A remote desktop interface for Weston was proposed in 2013 by a developer from [[RealVNC]]. ==== Maynard ==== [[File:Maynard_desktop.png|thumb|Maynard (in January 2017)]] '''''Maynard''''' is a [[graphical shell]] and has been written as a plug-in for Weston, just as the [[GNOME Shell]] has been written as a plug-in to [[Mutter (software)|Mutter]]. The [[Raspberry Pi Holdings|Raspberry Pi]] in collaboration with [[Collabora]] released Maynard. === libinput === [[File:Libinput_for_Wayland_compositors.svg|thumb|libinput was created to consolidate the input stack across multiple Wayland compositors.]] The Weston code for handling input devices (keyboards, pointers, touch screens, etc.) was split into its own separate library, called ''libinput'', for which support was first merged in Weston 1.5. Libinput handles input devices for multiple Wayland compositors and also provides a generic [[X.Org Server]] input driver. It aims to provide one implementation for multiple Wayland compositors with a common way to handle input events while minimizing the amount of custom input code compositors need to include. libinput provides device detection (via [[udev]]), device handling, input device event processing and abstraction. Version 1.0 of libinput followed version 0.21, and included support for tablets, button sets and touchpad gestures. This version will maintain stable API/ABI. As GNOME/GTK and [[KDE Frameworks 5]] have mainlined the required changes, Fedora 22 will replace X.Org's evdev and Synaptics drivers with libinput. With version 1.16, the [[X.Org Server]] obtained support for the libinput library in form of a wrapper called [[Mono]]. === Wayland Security Module === Wayland Security Module is a proposition that resembles the [[Linux Security Module]] interface found in the [[Linux kernel]]. Some applications (especially the ones related to [[accessibility]]) require privileged capabilities that should work across different Wayland compositors. Currently, applications under Wayland are generally unable to perform any sensitive tasks such as taking screenshots or injecting input events without going through [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] or obtaining privileged access to the system. Wayland Security Module is a way to delegate security decisions within the compositor to a centralized security decision engine. == Adoption == The Wayland protocol is designed to be simple so that additional protocols and interfaces need to be defined and implemented to achieve a holistic windowing system. While many graphical toolkits already fully support Wayland, the developers of the [[Graphical shell|graphical shells]] are cooperating with the Wayland developers to create the necessary additional interfaces. === Desktop Linux distributions === Most major Linux distributions default to using Wayland. Some notable examples are: * [[Debian]] ships Wayland as the default session for GNOME since version [[Debian 10|10 (Buster)]], released 6 July 2019. * [[Fedora]] starting with version 25 (released 22 November 2016) uses Wayland for the default GNOME 3.22 desktop session, with [[X.Org]] as a fallback if the graphics driver cannot support Wayland. Fedora uses Wayland as the default for KDE desktop session starting with version 34 (released 27 April 2021) * [[Manjaro]] ships Wayland as default in the Gnome edition of Manjaro 20.2 (Nibia) (released 22 November 2020). * [[Raspberry Pi OS]], a port of Debian, has offered the option to use Wayland since version [[Debian 11|11 (Bullseye)]], which was released on 3 December 2021. Wayland became the default in version [[Debian 12|12 (Bookworm)]], released on 10 October 2023. * [[Red Hat Enterprise Linux]] ships Wayland as the default session in version 8, released 7 May 2019. * [[Ubuntu]] shipped with Wayland by default in Ubuntu 17.10 (Artful Aardvark). However, Ubuntu 18.04 LTS reverted to X.Org by default due to several issues. Since Ubuntu 21.04, Wayland is the default again. * [[Slackware]] included Wayland on 20 February 2020 for the development version, -current, which became version 15.0 in 2022. Slackware 15.0 (released 2022) has Wayland although the only compositor/DE available in the repos is KDE Plasma with `startkwayland`. However, Wayland is still not the default. == History == Kristian Høgsberg, a [[Linux]] graphics and [[X.Org]] developer who previously worked on [[AIGLX]] and [[Direct Rendering Infrastructure|DRI2]], started Wayland as a spare-time project in 2008 while working for [[Red Hat]]. His stated goal was a system in which "every frame is perfect, by which I mean that applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker." Høgsberg was driving through the town of Wayland, Massachusetts when the underlying concepts "crystallized", hence the name (Weston and Maynard are also nearby towns in the same area, continuing the reference). In October 2010, Wayland became a [[freedesktop.org]] project. As part of the migration, the prior Google Group was replaced by the ''wayland-devel'' mailing list as the project's central point of discussion and development. The Wayland client and server libraries were initially released under the [[MIT License]], while the reference compositor Weston and some example clients used the [[GNU General Public License]] version 2. Later, all the GPL code was relicensed under the MIT license "to make it easier to move code between the reference implementation and the actual libraries". In 2015 it was discovered that the license text used by Wayland was a slightly different and older version of the MIT license, and the license text was updated to the current version used by the [[X.Org]] project (known as [[Expat License|MIT Expat License]]). {| class="wikitable sortable collapsible text-align:center" |} 1148a633923a0351057600e9c821c0fab491c075 6 1318 5670 2026-06-04T13:28:42Z Moon 422 Official artwork of Glenda, mascot of [https://en.wikipedia.org/wiki/Plan_9_from_Bell_Labs Plan 9 from Bell Labs]. wikitext text/x-wiki == Summary == Official artwork of Glenda, mascot of [https://en.wikipedia.org/wiki/Plan_9_from_Bell_Labs Plan 9 from Bell Labs]. c146592352098c2dd887281e5b463aa397edca7f 14 390 5671 4646 2026-06-04T13:41:25Z Moon 422 wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE Mascot Konqi by Tyson Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE women mascot Katie development cropped by Tyson Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|frameless|64x64px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|64x64px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Tuz-logo.svg|alt=A drawing of a Tasmanian devil wearing a fake penguin beak,|frameless|76x76px]] |[[Taz]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|64x64px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|64x64px]] |[https://krita.org/en/about/mascot/ KiKi] |[https://krita.org Krita] |} ==== Other Projects Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:415656095680e1c6138277b0ba27e212.png|frameless|64x64px]] |[[Talia]] |[https://www.noctalia.dev Noctalia] |- |[[File:Sudo-sandwich-logo-65.png |frameless|64x64px]] |[[Sudo Sandwich]] |[https://www.sudo.ws Sudo] |- |[[File:Plan9 Bunny.png|alt=The rabbit mascot of Plan 9 from Bell Labs.|frameless|64x64px]] |[[Glenda]] |[[Plan 9 from Bell Labs]] |} 51658cd717772d8ce864af7f3dfd517c5efed19f 5692 5671 2026-06-10T02:14:24Z Strangely Human Feeling 415 /* Desktop Environment Mascots */ Added Kori and resized other desktop mascots wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE_Mascot_Konqi_by_Tyson_Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|center|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE_women_mascot_Katie_development_cropped_by_Tyson_Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|center|frameless|91x91px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Mascot KDE Kori.png|center|thumb|151x151px]] |[[Kori]] |[[KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|83x83px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Tuz-logo.svg|alt=A drawing of a Tasmanian devil wearing a fake penguin beak,|frameless|76x76px]] |[[Taz]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|64x64px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|64x64px]] |[https://krita.org/en/about/mascot/ KiKi] |[https://krita.org Krita] |} ==== Other Projects Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:415656095680e1c6138277b0ba27e212.png|frameless|64x64px]] |[[Talia]] |[https://www.noctalia.dev Noctalia] |- |[[File:Sudo-sandwich-logo-65.png |frameless|64x64px]] |[[Sudo Sandwich]] |[https://www.sudo.ws Sudo] |- |[[File:Plan9 Bunny.png|alt=The rabbit mascot of Plan 9 from Bell Labs.|frameless|64x64px]] |[[Glenda]] |[[Plan 9 from Bell Labs]] |} fa61de08870d77ef59719e3d41a99cf8bff22549 5695 5692 2026-06-10T03:19:47Z Strangely Human Feeling 415 /* Program Mascots */ Resized images for clarity sake and added alt text to Kori wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE_Mascot_Konqi_by_Tyson_Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|center|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE_women_mascot_Katie_development_cropped_by_Tyson_Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|center|frameless|90x90px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Mascot KDE Kori.png|alt=A cartoon anthropomorphic teal dragon wearing a blue scarf with the letter K|frameless|120x120px]] |[[Kori]] |[[KDE Plasma]] |- |[[File:Xfce-xue.jpg|alt=A drawing of a black rat|frameless|90x90px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Tuz-logo.svg|alt=A drawing of a Tasmanian devil wearing a fake penguin beak,|frameless|76x76px]] |[[Taz]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|90x90px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|120x120px]] |[https://krita.org/en/about/mascot/ KiKi] |[https://krita.org Krita] |} ==== Other Projects Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:415656095680e1c6138277b0ba27e212.png|frameless|64x64px]] |[[Talia]] |[https://www.noctalia.dev Noctalia] |- |[[File:Sudo-sandwich-logo-65.png |frameless|64x64px]] |[[Sudo Sandwich]] |[https://www.sudo.ws Sudo] |- |[[File:Plan9 Bunny.png|alt=The rabbit mascot of Plan 9 from Bell Labs.|frameless|64x64px]] |[[Glenda]] |[[Plan 9 from Bell Labs]] |} acc56e2042e83c3c5d67c930e931f3abf5743aff 5697 5695 2026-06-10T03:57:14Z Strangely Human Feeling 415 /* Desktop Environment Mascots */ Replaced XFCE mascot with transparent SVG wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |[https://fedoraproject.org/ Fedora] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE_Mascot_Konqi_by_Tyson_Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|center|frameless|92x92px]] |[[Konqi]] |[[Plasma|KDE Plasma]] |- |[[File:KDE_women_mascot_Katie_development_cropped_by_Tyson_Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|center|frameless|90x90px]] |[[Katie]] |[[Plasma|KDE Plasma]] |- |[[File:Mascot KDE Kori.png|alt=A cartoon anthropomorphic teal dragon wearing a blue scarf with the letter K|frameless|120x120px]] |[[Kori]] |[[KDE Plasma]] |- |[[File:Mascot XFCE Xue.svg|alt=A drawing of a black rat|frameless|120x120px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Tuz-logo.svg|alt=A drawing of a Tasmanian devil wearing a fake penguin beak,|frameless|76x76px]] |[[Taz]] |[[Linux]] |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] (unofficial) |[[Linux]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|90x90px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|120x120px]] |[https://krita.org/en/about/mascot/ KiKi] |[https://krita.org Krita] |} ==== Other Projects Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:415656095680e1c6138277b0ba27e212.png|frameless|64x64px]] |[[Talia]] |[https://www.noctalia.dev Noctalia] |- |[[File:Sudo-sandwich-logo-65.png |frameless|64x64px]] |[[Sudo Sandwich]] |[https://www.sudo.ws Sudo] |- |[[File:Plan9 Bunny.png|alt=The rabbit mascot of Plan 9 from Bell Labs.|frameless|64x64px]] |[[Glenda]] |[[Plan 9 from Bell Labs]] |} dfb719a1c9ab3008a8a16f4984ea4d5aa4942b9a 0 1319 5672 2026-06-04T14:13:09Z Moon 422 Plan 9 from Bell Labs is a distributed operating system developed as a successor to UNIX. wikitext text/x-wiki =Plan9 from Bell Labs= Plan9 from Bell Labs is a distributed [[operating system]] developed at [https://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in the late 1980s. It was designed by [https://en.wikipedia.org/wiki/Ken_Thompson Ken Thompson], [https://en.wikipedia.org/wiki/Rob_Pike Rob Pike], David Presotto, Phil Winterbottom, and others. In 2021, the system was transferred to the [https://p9f.org Plan 9 Foundation] and relicensed under the [[MIT License]]. 270b3b6f337b63a8827f10f1355d1ac96df0997d 5673 5672 2026-06-04T15:04:50Z Moon 422 wikitext text/x-wiki [https://p9f.org/about.html Plan 9 from Bell Labs] is a distributed [[operating system]] developed at [https://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in the late 1980s. It was designed by [https://en.wikipedia.org/wiki/Ken_Thompson Ken Thompson], [https://en.wikipedia.org/wiki/Rob_Pike Rob Pike], David Presotto, Phil Winterbottom, and others. In 2021, the system was transferred to the [https://p9f.org Plan 9 Foundation] and relicensed under the [[MIT License]]. 5b37f8f08db7f74612cf8c60c025c844f28ae7b4 0 1320 5674 2026-06-04T20:13:53Z Brochard 351 Redirect to "Plan 9 from Bell Labs" wikitext text/x-wiki #REDIRECT [[Plan 9 from Bell Labs]] 3eefd6b34545528cca9e7033f888f77334445885 0 480 5675 5209 2026-06-05T22:15:47Z 2elevation 115 Add Oreon 10 (Build 2606) wikitext text/x-wiki {{DistributionInfobox |title=Oreon Linux |image=[[File:OreonLogo_2026.png|thumb]] |caption=Oreon Logo |releasestatus=Maintained |releasemodel=LTS |packagemanager=[[dnf]] |defaultdesktops = GNOME, [[KDE Plasma]] |usagetype=Desktop, Server |architectures = aarch64, x86_64 |website=[https://oreonhq.com/ oreonhq.com]}} [[Category:Linux Distributions]] [[File:Oreon 10 desktop.png|thumb|Oreon 10 default desktop since Build 2504 running GNOME]] '''Oreon Linux''' is a [[Linux Distributions|Linux Distribution]] developed by Oreon HQ. Originally based on AlmaLinux, the project modifies its enterprise base to provide a practical, out-of-the-box desktop experience, importing missing system packages from [[Fedora|Fedora Linux]].<ref>[https://copr.fedorainfracloud.org/coprs/brandonlester/oreon-10/ brandonlester/oreon-10 Copr Repository], Fedora Copr (Accessed: 2026-05-23)</ref> === History === The first release, ''Oreon Lime (R1/R1.1)'', launched on January 1, 2024.<ref>[https://boostyconnect.com/oreon-lime-r1-lifecycle/ Oreon Lime R1/R1.1 Lifecycle], BoostyConnect Technologies (Accessed: 2025-08-09)</ref> It was replaced on February 18, 2024, by ''Oreon Lime (R2)'', which moved the base to AlmaLinux for long-term support capabilities.<ref>[https://wiki.oreonhq.com/docs/Support-Timelines/oreon-lime-r2-support-timeline Oreon Lime (R2) Support Timeline], Oreon Wiki (Accessed: 2026-05-23)</ref> This early release shipped with GNOME 40 and Linux kernel 5.14, receiving coverage from outlets like ''The Register''.<ref>[https://www.theregister.com/2024/08/20/oreon_lime_desktop_almalinux/ Oreon Lime is AlmaLinux with a desktop twist], Liam Proven, The Register, 2024-08-20</ref> ==== Oreon 10 Build Cycle ==== Oreon 10 officially launched on December 12, 2024, with the original release (Build 2412), introducing KDE Plasma 6 alongside Linux kernel 6.11, which updated to kernel 6.12 shortly after. Incremental system updates and maintenance fixes are pushed through a build-number system formatted as the first two digits of the year followed by the month.<ref>[https://wiki.oreonhq.com/docs/Support-Timelines/oreon-10-support-timeline Oreon 10 Support Timeline], Oreon Wiki (Accessed: 2026-05-23)</ref> Build 2501 launched on January 1, 2025, followed by Build 2502 on February 12, 2025. Build 2503 released shortly after on February 28, 2025. Build 2504 was pushed on March 13, 2025, which switched the default desktop choice back to GNOME following user criticism regarding the interface shift. Later maintenance milestones included Build 2507 on July 14, 2025, and Build 2510 on October 12, 2025. The cycle continued into the following year with Build 2602 on February 9, 2026 as well as Build 2603, which released on March 1, 2026, and replaced the older Anaconda installer with a custom installer called Centrio while changing several other default configurations.<ref>[https://distrowatch.com/?newsid=12744 Oreon 10-2603 DistroWatch Announcement], Oreon HQ (Accessed: 2026-05-23)</ref> The latest Oreon 10 build is Build 2606, which released on May 29, 2026. === Future Development === Following updates from the Oreon team and coverage by BetaNews, development focus has moved toward the next major release, Oreon 11. The upcoming release will drop its reliance on AlmaLinux entirely. Instead, the distribution is moving toward becoming an independent RPM-based Linux distribution to gain direct control over its repository infrastructure and package availability, targeting a better release cycle and separate package branches.<ref>[https://betanews.com/article/oreon-11/ Oreon 11 could be the Linux OS that helps you leave Microsoft Windows for good], BetaNews (Accessed: 2026-05-23)</ref> To back this infrastructure independence, Oreon HQ secured major hosting partnerships. The Oregon State University Open Source Lab joined as a sponsor in May 2026 to help host the new Oreon Build Service and power part of the Oreon mirror network, providing dedicated high-performance servers.<ref>[https://osuosl.org/communities/ OSU OSL Communities Ecosystem], Oregon State University Open Source Lab (Accessed: 2026-05-23)</ref> This followed a network infrastructure sponsorship formed with Cloudflare in July 2025. == References == <references /> 62e6ce4281a50dd2745e658fd4ec95887edfd9d9 0 1018 5676 4329 2026-06-06T14:27:20Z Chillygopher 423 Update the Language's Description and Last Release wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:go.png|200px]] | caption = Go Logo | title = Go | releasestatus = Maintained | lastrelease = 1.26.4 | languages = [[Go]], originally written in [[C]] | developers = The Go Team; originally by Rob Pike, Ken Thompson and Robert Griesemer | website = [https://go.dev/ go.dev] }} Go (or Golang) is a statically typed, fast and simple "C-like" language, developed at Google in 2006 by the Go Team. It provides Class-less Object Oriented Programming (OOP), First-Class Support for Concurrency using Goroutines and Channels and Support for Generics programming using the Go Generics. The language also offers a Rich Standard Library, Powerful Command Line Tools and a Powerful Language Server attributing to its widespread adoption in Cloud Native, Web and [[CLI]] Development. 7d7a9cf347fa80d7f81540142c5188453e7d0cff 5677 5676 2026-06-06T14:45:06Z Chillygopher 423 Fix inaccuracies and cite sources wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:go.png|200px]] | caption = Go Logo | title = Go | releasestatus = Maintained | lastrelease = 1.26.4 | languages = [[Go]], originally written in [[C]] | developers = The Go Team; originally by Rob Pike, Ken Thompson and Robert Griesemer | website = [https://go.dev/ go.dev] }} Go (or Golang) is a statically typed, fast and simple "C-like" language, conceived at Google in 2007 by the Go Team <ref>[https://go.dev/talks/2012/splash.article], Go at Google: Language Design in the Service of Software Engineering - The Go Programming Language, 2012-10-25, (Accessed 2026-06-06)</ref> It provides Class-less Object Oriented Programming (OOP), First-Class Support for Concurrency using Goroutines and Channels and Support for Generics programming using the Go Generics. The language also offers a Rich Standard Library, Powerful Command Line Tools and a Powerful Language Server attributing to its widespread adoption in Cloud Native, Web and [[CLI]] Development<ref>[https://go.dev/solutions/use-cases], Use-Cases - The Go Programming Language, n.d, (Accessed 2026-06-06)</ref> References 0b32e74a369d73b25cb81077993932cfb7fb16b5 5678 5677 2026-06-06T14:46:16Z Chillygopher 423 fix spacing wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:go.png|200px]] | caption = Go Logo | title = Go | releasestatus = Maintained | lastrelease = 1.26.4 | languages = [[Go]], originally written in [[C]] | developers = The Go Team; originally by Rob Pike, Ken Thompson and Robert Griesemer | website = [https://go.dev/ go.dev] }} Go (or Golang) is a statically typed, fast and simple "C-like" language, conceived at Google in 2007 by the Go Team <ref>[https://go.dev/talks/2012/splash.article], Go at Google: Language Design in the Service of Software Engineering - The Go Programming Language, 2012-10-25, (Accessed 2026-06-06)</ref> It provides Class-less Object Oriented Programming (OOP), First-Class Support for Concurrency using Goroutines and Channels and Support for Generics programming using the Go Generics. The language also offers a Rich Standard Library, Powerful Command Line Tools and a Powerful Language Server attributing to its widespread adoption in Cloud Native, Web and [[CLI]] Development<ref>[https://go.dev/solutions/use-cases], Use-Cases - The Go Programming Language, n.d, (Accessed 2026-06-06)</ref> References 107bb750870f29d841a0c5a1a802cb757ff7aee6 1 1321 5679 2026-06-06T19:30:43Z Imnotgoodatnames 121 /* Disagreement with the title change */ new section wikitext text/x-wiki == Disagreement with the title change == ''Plan 9'' is the common and the far-more widely used name. Even the developers of the system usually call it simply "Plan 9". In fact, the very first words on the main text on p9f.org/about.html are "Plan 9 is…", and the about page only calls it "Plan 9 from Bell Labs" on the title and when mentioning a paper of the same name. The p9f.org also calls the operating system simply "Plan 9". [[User:Imnotgoodatnames|Imnotgoodatnames]] ([[User talk:Imnotgoodatnames|talk]]) 19:30, 6 June 2026 (UTC) b3eb88600f2c49112e97f456b6b3acdf1a09129a 5680 5679 2026-06-06T19:31:14Z Imnotgoodatnames 121 /* Disagreement with the title change */ wikitext text/x-wiki == Title should be simply ''Plan 9'' == ''Plan 9'' is the common and the far-more widely used name. Even the developers of the system usually call it simply "Plan 9". In fact, the very first words on the main text on p9f.org/about.html are "Plan 9 is…", and the about page only calls it "Plan 9 from Bell Labs" on the title and when mentioning a paper of the same name. The p9f.org also calls the operating system simply "Plan 9". [[User:Imnotgoodatnames|Imnotgoodatnames]] ([[User talk:Imnotgoodatnames|talk]]) 19:30, 6 June 2026 (UTC) f79370244b5551900ae22c29ad1a0629e65ca158 5681 5680 2026-06-07T05:35:35Z Madonuko 140 /* Title should be simply Plan 9 */ Reply wikitext text/x-wiki == Title should be simply ''Plan 9'' == ''Plan 9'' is the common and the far-more widely used name. Even the developers of the system usually call it simply "Plan 9". In fact, the very first words on the main text on p9f.org/about.html are "Plan 9 is…", and the about page only calls it "Plan 9 from Bell Labs" on the title and when mentioning a paper of the same name. The p9f.org also calls the operating system simply "Plan 9". [[User:Imnotgoodatnames|Imnotgoodatnames]] ([[User talk:Imnotgoodatnames|talk]]) 19:30, 6 June 2026 (UTC) :The official name of the operating system should probably be used, just like [[Fedora Linux]] and [[Ultramarine Linux]]. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 05:35, 7 June 2026 (UTC) 7ed07d87d31c969e29a68d90448ae22d2c627fdf 0 203 5682 5602 2026-06-08T00:00:38Z Ok 425 Date correction, Project was founded on 2002 not 2000. Additionally, added the full date accordingly ( 31 March, YEAR ), Source: https://en.wikipedia.org/wiki/Gentoo_Linux wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = Gentoo Linux | image = [[File:Gentoo Linux logo matte.svg|300px|Gentoo Linux logo matte]] | caption = The official Gentoo Linux logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [https://wiki.gentoo.org/wiki/Portage portage] | defaultdesktops = None, User Choice | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.gentoo.org/ gentoo.org] }} [https://www.gentoo.org/ Gentoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded on 31 March 2002 by [[Daniel Robbins]].<ref>[https://en.wikipedia.org/wiki/Daniel_Robbins_(computer_programmer) Daniel Robbins (computer programmer)], Wikipedia contributors, 2024-01-10 (Accessed: 2025-08-09)</ref> Known for its emphasis on customization and performance optimization, '''Gentoo''' allows users to customize their system to a degree way beyond other distributions by providing granular control over system packages and features. == Overview == '''Gentoo''' stands out for its unique approach to [[package management]] and system configuration. Users can fine-tune their installation through compile-time options called USE flags, which determine what features and dependencies are included in each package. This approach, while more time-consuming than other distributions due to it's complexity, enables optimizations specific to the user's hardware and requirements. A common myth says that a user must compile everything in '''Gentoo''' or that the [https://wiki.gentoo.org/wiki/Project:Binhost Project:Binhost] is anti-Gentoo. The irony being that Gentoo was created to be all about user choice, and all the binhost provides is a choice to its users. Using the binhost doesn't prevent a user from compiling the packages they want to modify, as both binary and source-built packages can coexist seamlessly. === Key Features === There are multiple key features that '''Gentoo''' allows, by example '''Gentoo''' allows the user to completely configure the system as they wish. One can choose between [[OpenRC]] or [[Systemd]] as their init system, but that can also be changed as well if the user has a desire for it. The Operating System itself has extensive hardware and architecture support, the '''Gentoo''' Handbook has many officially supported architectures, but the users can opt in for other architectures as well, as '''Gentoo''' is very flexible with the software it provides, hence the name "Meta-Distribution". '''Gentoo''' follows the Rolling Release model with stable and unstable branch options, by default all unstable packages ('''~amd64)''' are masked, so the user will not accidentally get unstable packages inside their system without their knowledge or approval. '''Gentoo''' has minimal system requirements and runs on nearly anything you throw it at although some lesser used architectures will not have binaries. '''Portage''', one of the most key components of '''Gentoo''', allows the user to have super control over the system and packages within it. It allows for easy compilation settings ( USE flags ), monitoring the system packages effectively and letting the user change the system as they desire. Additionally, '''Portage''' allows storing multiple versions of the same package on the system, also called "[https://wiki.gentoo.org/wiki/SLOT slotting]". As example, the user can download both Python 2 and Python 3, and use them at the same time on different projects. == Installation == Installing '''Gentoo''' requires manual configuration and compilation of the system components. Users who want to install Gentoo are recommended to consult the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook] which has up-to-date information about Installation, Working with Gentoo, Working with Portage, and Gentoo network configuration for a variety of system architectures. Unlike other Linux distributions, Gentoo is made to be installable from any installation environment, although the Handbook recommends using a Gentoo live environment. Gentoo provides both a minimal .iso without only a command line, and a LiveGUI with KDE Plasma. From this live environment, the user will configure disks and network before loading in a stage file to act as a seed for the Gentoo install. Later the user has to configure and install a Gentoo base system, a Linux kernel, system tooling, base configuration files, user accounts, and a bootloader. == Package Management == === Portage === [https://wiki.gentoo.org/wiki/Portage Portage] is '''Gentoo'''<nowiki/>'s package management system, providing powerful features for system administration. Portage consists of 15 different tools, though only 3 of which - emerge, emaint, and dispatch-conf - are typically used for day-to-day maintenance. Portage is at the core of every Gentoo installation, providing advanced dependency resolution, and flexible building and installing of software both from source and from a binary package host. Inspired by the [https://en.wikipedia.org/wiki/Ports_collection ports collections]-concepts of the BSDs, Portage is extremely flexible and can also run on other distributions and operative systems, among others [https://www.gentoo.org/news/2026/04/01/gentoo-hurd.html GNU/Hurd] and [https://wiki.gentoo.org/wiki/Gentoo_FreeBSD FreeBSD]. ==== Common Usage ==== ''For detailed and up-to-date information, please refer to the [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo Handbook] and other relevant documentation.'' {| class="wikitable" ! Command ! Description |- | <code>emerge --sync</code> | Update package repository |- | <code>emerge --ask --update --deep --newuse @world</code> | Update system |- | <code>emerge -s package</code> | Search for packages |- | <code>emerge --ask package</code> | Install a package |- | <code>emerge --deselect package</code> | Remove a package from the [https://wiki.gentoo.org/wiki/Selected_set_(Portage) selected set] |- | <code>emerge --pretend --verbose package</code> | Preview package installation |- | <code>emerge --depclean</code> | Remove unneeded packages |- |<code>emerge --unmerge / emerge -C</code> |'''Do not use unless you know what you are doing''' removes a package without checking dependencies even core system packages |- |<code>emerge --pretend --verbose --depclean package</code> |Check what depends on package |} == System Optimization == === Compilation Flags === '''Gentoo''' users can optimize their system through CPU-specific optimizations, in order to compile packages specific to their CPU specifications and hardware. This is done through [https://wiki.gentoo.org/wiki/USE_flag USE flags]. USE flags work by configuring '''Portage''' to decide how each package is to be installed and updated, and are a core feature of how Gentoo users can customize their installation. USE flags can also be used to include or exclude certain features from packages by omitting them at compile time. USE flags can be set both individually per package and through <code>package.use</code>, as detailed on the Gentoo wiki. === Binary Packages === Gentoo offers binaries like any other distribution but it needs to be explicitly enabled. Refer to the [https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart Binary Host Quickstart guide] for detailed information == Security == '''Gentoo''' allows users to setup extensive [[SELinux]]<ref>Security Enhanced Linux. https://en.wikipedia.org/wiki/Security-Enhanced_Linux</ref> support, alongside hardened profiles. '''Gentoo''' receives regular security patches, and their bug tracker will always remain public so that everyone can see each issue '''Gentoo''' has live. The people behind '''Gentoo''' clearly mentioned they will not hide anything from it's userbase, as it destroys the trust between developers and users. '''Gentoo''' also has signed package verification to make sure each package remains unaffected by malicious individuals. Additionally, one can opt for the kernel hardening options that the developers rolled out for the community. == Community and Development == === Community Resources === Gentoo has several community resources. The official community wiki and forums can be found at [https://wiki.gento.org https://wiki.gento.org] and [https://forums.gentoo.org/ forums.gentoo.org/] respectively. There is also a bug tracking system at [https://bugs.gentoo.org/ https://bugs.gentoo.org/] Gentoo also has several public [https://www.gentoo.org/get-involved/mailing-lists/ mailing lists] both for general use and for specific topics. For live communication there are official IRC<ref>Internet Relay Chat</ref> [https://wiki.gentoo.org/wiki/IRC channels]. === Development Model === '''Gentoo''' is developed as an open source project, with contributions coming from both the official developers and community members. Today, '''Gentoo''' is one of the most documented distributions to ever exists, with a very complex wiki and a lot of contributions coming in daily. Everything in this distribution is almost fully community driven; package maintenance, bugs, issues, patches, or active ebuilds through public user overlays or the official '''Gentoo''' repository. Security updates come regularly from the official developers, to maintain best security practices for the Operating System. The system encourages keeping packages up to date through it's rolling release model, while remaining stable. The behind the scenes of the entire Operating System is coordinated by an active team of developers, with direct communications to the user base through it's IRC channels, mailing list and the Bugzilla. Gentoo's source code alongside package data are publicly hosted in Git repositories, allowing anyone to view, fork, or contribute changes. == Comparison with Other Distributions == Compared to other distributions, '''Gentoo''' is a considered user-centric, Do-It-Yourself distribution that allows maximum customization and optimal performance through compilation and complete control over features. Gentoo also has extensive documentation, active community support, and also ability to use binaries. This comes with the downside of a steep learning curve, requiring more knowledge about which components a system needs to function, and a much longer and more tedious install process. While this is great for some users, others might prefer a more out-of-the-box experience provided by more user-friendly distributions such as [[Linux Mint]]. == Trivia == * [[Larry the Cow]] is Gentoo's unofficial mascot * The name "Gentoo" (''[[wikipedia:Gentoo_penguin|Pygoscelis papua]]'') comes from the fast-swimming Gentoo penguin, a species that can reach speeds of 36km/h (22 mph), being the fastest of all species of penguins * You can view Larry the Cow by running <code>emerge --moo</code> == See Also == * [[Linux]] == External Resources == * [https://wiki.gentoo.org/ Gentoo Wiki] * [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] * [https://packages.gentoo.org/ Package Database] * [https://bugs.gentoo.org/ Bug Tracker] * [https://wiki.gentoo.org/wiki/Portage Portage] * [https://planet.gentoo.org/ Gentoo Planet] 3e65373bcebb5a213668b013adbb6d884067a5f1 0 2 5683 3877 2026-06-08T00:10:57Z Ok 425 Refined the Arch Linux logo description for tone. Additionally, added the creation date of the distribution, as that was completely absent from the page. wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Arch Linux | image = [[File:Arch Linux "Crystal" icon.svg|Arch_Linux_"Crystal"_icon]] | caption = The official Arch Linux logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = x86_64 | website = [https://archlinux.org archlinux.org] }} [[Category:Linux Distributions]] [[File:Arch_Linux_Minimal_Neofetch_Output.png|thumb|[[Neofetch]] on Arch Linux]] '''Arch Linux''' is an independent rolling release [[Linux Distributions|Linux distribution]] founded on 11 March 2002 focused on the '''KISS''' ''(Keep It Simple, Stupid)''<ref>[https://wiki.archlinux.org/title/arch_terminology#KISS Arch terminology – KISS], Arch Linux, accessed 2025-06-29</ref> principle that focuses on being lightweight and flexible<ref>[https://archlinux.org/about/ About Arch Linux], The Arch Linux Team, accessed 2025-06-29.</ref>. Arch Linux is kept up-to-date by regularly updating the packages of the system. It was originally founded by Judd Vinet due to his inspiration from [[CRUX Linux]] being "simplistic, elegant, and very quick and easy to use" <ref>[https://distrowatch.com/dwres.php?resource=interview-arch Interview with Judd Vinet], Ladislav Bodnar, accessed 2025-06-29</ref>. === Functionality === Distinguishing features of Arch Linux from other distributions are its [[Package Manager|package manager]] named ''[[pacman]]'' and the minimal installation package set ''[https://archlinux.org/packages/core/any/base/ base]'', which as of July 4 2024 comprises only 28 packages such as ''[[glibc]]'', ''[[systemd]]'', and the only optional package ''linux'', comprising the [[linux|kernel]]. Building Arch Linux packages is automated by the bash script <code>makepkg</code> which executes either a build script or a PKGBUILD.<ref>[https://pacman.archlinux.page/makepkg.8.html makepkg(8) – build packages], Arch Linux, 2025-06-29</ref><ref>[https://pacman.archlinux.page/PKGBUILD.5.html PKGBUILD(5) – package build script format], Arch Linux, accessed 2025-06-29</ref> Users of the [[Arch User Repository|AUR]] are encouraged to understand the build scripts of packages they are about to execute before installing packages.<ref>{{Cite|url=https://wiki.archlinux.org/title/Arch_User_Repository#Build_the_package|title=Arch User Repository Wiki|accessdate=2025-08-26}}</ref> <code>makepkg</code> is part of the ''pacman'' package. === Installation === The Arch Linux website provides a downloadable ISO image that can be flashed onto a bootable drive. The operating system can be installed by following the [https://wiki.archlinux.org/title/Installation_guide Installation Guide] or by using the included installation script, archinstall. ==== Arch Installation Script ==== This is generally the easier way to install Arch Linux, although it does limit the amount of possible configurations, for more advanced control the manual installation should be used. {| class="wikitable" !Mirrors |Select a mirror region that is close to you. This is where pacman is able to fetch package lists. |- !Locales |Select your language and keyboard layout. |- !Disk Configuration and Partitioning |While manual partitioning is slightly more advanced for beginners, archinstall provides a setting for a pre-configured setup that streamlines the process. |- !Full Disk Encryption |This is directed towards those interested in deeper security and/or privacy. While, security-wise, it does not necessarily guard your system while it is powered on, it will help mitigate data theft on your main drive from an adversary with access to it while it's powered off. [citation] |- !Bootloader |You are able to pick from GRUB, systemd-boot, EFIstub, and Lumine. The choice is up to you - generally, GRUB is the most popular. |- !Unified Kernel Images [citation]   |A switch to enable or disabled Unified Kernel Images, these can be booted directly from UEFI |- !Swap Memory |The memory allocated to your system when it runs out of RAM. Set to as high or as little as you feel you need. |- !Host Name |The name of your machine. |- !Root Password   |Set a password for the root account. |- !Profile and Drivers |Here, you can select multiple profiles: * minimal - a barebones installation of Arch without any Display Manager. Consider whether you will really need such a minimal system. * server - a minimal install aimed towards a headless server. * desktop - the most popular choice for archinstall. Offers not only Desktop Environments but also Window Managers. * Xorg - offers a minimal install, but with graphics drivers attached. Keep in mind your system composition and remember which Graphics Card or Processor you are using to select the correct driver. |- !Greeter/Display Manager |Offers a choice between sddm, gdm, ly, and lightdm. |- !Audio |It is generally recommended to pick the newer PipeWire, yet PulseAudio exists as an option. If this is a server, you will likely not need sound. |- ![[Kernel|Kernels]] |There are four kernel<nowiki/>s, as of now, that users may choose from: * Linux - the latest upstream (?) generic kernel release. * Linux-LTS - a staggered release of the generic kernel operating from the latest Long-Term-Support release. * Linux-Zen - a version of the kernel designed for average desktop usage. [CITATION] It optimizes the main kernel in favor of being run on a desktop, yet it arguably does not seem to offer much actual performance gain or loss [CITATION] * Linux-Hardened - a version of the Linux kernel with extra patches for more security. Consider whether you need this or not - there are potential drawbacks. [CITATION] |- !Additional Packages |Name any additional packages you may want (e.g. Firefox) |- !Network Configuration |It's advised to use NetworkManager or plain iwctl so you do not have to worry about a broken network setup post-install. However, if you know what you are doing, use ethernet, or know how to install network pacakges after installation, you can still '''use no network configuration''' post install. If you are happy with your current configuration from the ISO, select '''copy from ISO.''' |- !Timezone |Select your timezone. |- !Automatic Time Sync (NTP) |Using systemctl timers [UNSURE], periodically sync with timeservers. For the ultra privacy-concerned, you can always leave this off. |- !Optional Repositories |There are two as of writing: * '''multilib -''' From experience, it is a good idea to leave this '''ticked on.''' These generally provide compatibility libraries that you may need for other applications to run. * '''testing -''' From experience, it is a good idea to leave this '''ticked off.''' These are often packages still undergoing trial runs from developers and are extremely prone to breakages. |} Once you are done, either '''save configuration''' or plainly '''Install.''' === Trivia === * If you add "ILoveCandy" to <code>/etc/pacman.conf</code> instead of a regular progress bar you get a pacman eating dots.<ref>{{Cite|url=https://shibumi.dev/posts/my-pacman.conf-file/|title=My pacman.conf file|author=Christian Rebischke|year=2020|accessdate=2025-08-26}}</ref> * The name "Arch" came from the word "arch-nemesis".<ref>[https://web.archive.org/web/20120914175514/http://osdir.com/ml/linux.arch.general/2005-08/msg00253.html Archived post on linux.arch.general (msg00253)], OSDir.com, accessed 2025-06-29</ref> * Arch is directly inspired by another DIY distribution named CRUX.<ref>{{Cite|url=https://wiki.archlinux.org/title/Arch_compared_to_other_distributions?pubDate=20250818#CRUX|title=Arch compared to other distributions|accessdate=2025-08-26}}</ref> == References == <references /> 8ccdc96516f6806448e74eae07ec3045ae00517b 0 202 5684 3634 2026-06-08T00:22:44Z Ok 425 Small correction regarding the number of the unofficial Gentoo Linux mascots. The page has misleadingly refered to Larry the Cow as "The unofficial mascot of Gentoo", however it insinuates that Larry ( the cow ) is the only mascot of that type. In reality, there are more unofficial Gentoo Linux mascots, as told by the **Official Gentoo Linux Larry the Cow wiki page** ( Source: https://wiki.gentoo.org/wiki/Larry_the_cow ; "Larry the Cow is one of Gentoo's unofficial mascots"). wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[Category:Mascots]] [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is among the unofficial mascots<ref>https://wiki.gentoo.org/wiki/Larry_the_cow Gentoo Wiki, 2023 (Imported 4th June 2024)</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html Gentoo Forums, 2003 (imported 4th June 2024)</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727 Gentoo Bug Report, 2003 (imported 4th June 2024)</ref> * Larry can be found in [[emerge]] by running <code>emerge --moo</code> Larry can also be found in [[Dpkg|apt]] by running <code>apt moo</code> . * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow MySpace, (imported 4th June 2024)</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry, Gentoo Wiki, 2000 (imported 4th June 2024)</ref> [[File:Larry The Cow with Gentoo Logo.png|thumb|Larry after he grew his black and white patches]] == References == <references /> 5e5d22eee328fb080c378c1216a7124fd8df2e0f 5690 5684 2026-06-10T01:09:19Z Larry the cow 402 wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[Category:Mascots]] [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:aptmoo.png|frame|Larry has infected Debian]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] '''Larry the Cow''' is among the unofficial mascots<ref>https://wiki.gentoo.org/wiki/Larry_the_cow Gentoo Wiki, 2023 (Imported 4th June 2024)</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html Gentoo Forums, 2003 (imported 4th June 2024)</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727 Gentoo Bug Report, 2003 (imported 4th June 2024)</ref> * Larry can be found in [[emerge]] by running <code>emerge --moo</code> Larry can also be found in [[Dpkg|apt]] by running <code>apt moo</code> . * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow MySpace, (imported 4th June 2024)</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry, Gentoo Wiki, 2000 (imported 4th June 2024)</ref> [[File:Larry The Cow with Gentoo Logo.png|thumb|Larry after he grew his black and white patches]] * Larry the cow was a bit frustrated at the current state of Linux distributions until he tried Gentoo Linux.<ref>https://www.gentoo.org/get-started/about/ Gentoo.org (imported 9th June 2026)</ref> == References == <references /> f0f7ea4d8e67515c6b9f49e19a5d16f4956d6857 2 1322 5685 2026-06-08T00:34:25Z Ok 425 Personal wiki page wikitext text/x-wiki Previous account: [[Special:Contributions/Empester]], all contributions apply. 630849abb11f0831304c745f4f686671171474d6 8 624 5686 4607 2026-06-08T21:21:08Z Atmois 13 Fix colour on vector home page [[User:Madonuko]] css text/css /* CSS placed here will be applied to all skins */ @import url('https://fonts.googleapis.com/css2?family=Fira+Mono:wght@400;500;700&display=swap'); :root { --font-family-citizen-monospace: 'Fira Mono'; } /* Force underline on all links and improve contrast */ a, a:visited, .external, .external:visited, .mw-redirect { text-decoration: underline; color: #1E90FF; font-weight: 500; } .new { text-decoration: underline; color: #FF4D4D; font-weight: 500; } /* Main Page */ .home-button { display: inline-block; padding: 8px 16px; margin: 0.25em 0; background-color: var(--color-primary, var(--color-progressive, #0066cc)); color: var(--color-primary--contrast, var(--color-inverted, white)); text-decoration: none; border-radius: 4px; font-weight: bold; transition: background-color 0.3s; } .home-button:hover { background-color: var(--color-primary--hover, var(--color-progressive--hover, #0052a3)); } .button-container { display: flex; flex-wrap: wrap; gap: 0.5em; justify-content: center; margin: 8px 0; padding: 0; } .content-grid { display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-top: 12px; } .content-section { background: var(--background-color-dp-04,var(--color-surface-2,var(--background-color-neutral-subtle, #2d2d2d))); border: 1px solid var(--border-color-base, var(--color-base--subtle, #555)); border-radius: 8px; padding: 20px; color: var(--color-base, var(--color-emphasized, #e0e0e0)); } .content-section.full-width { grid-column: 1 / -1; } .content-section.full-width p { margin: 8px 0; } .content-section.full-width center>p { margin: 6px 0; } .content-header { font-size: 1.4em; font-weight: bold; color: var(--color-primary, var(--color-progressive, #4a9eff)); border-bottom: 2px solid var(--color-primary, var(--color-progressive, #4a9eff)); padding-bottom: 6px; margin-bottom: 10px; } .content-section h4 { color: var(--color-primary, var(--color-progressive, #4a9eff)); margin-top: 15px; margin-bottom: 8px; } .content-section ul, .content-section ol { margin-left: 20px; } .content-section li { margin-bottom: 4px; } /* Header */ .home-header { position: relative; padding-top: 20px; padding-bottom: 8px; line-height: var(--line-height-xx-small); text-align: center; } .home-header-subtitle { margin-bottom: 4px; font-size: var(--font-size-small); letter-spacing: 0.05em; } .home-header-title { margin: 0; font-size: 3rem; letter-spacing: 0.025em; line-height: 1; } html.skin-citizen-dark .home-header:before, html.skin-citizen-dark .home-header__searchIcon img { filter: invert(1); } @media (max-width: 768px) { .content-grid { grid-template-columns: 1fr; } .home-button { padding: 6px 12px; font-size: 0.9em; } } @media (hover: none) { .home-header__search .desktoponly { display: none; } } .content-section .external::after, .content-section a.external::after { display: none; } .category-grid a { text-decoration: none; } .home-button.blue { background-color: #7aa2f7; color: #1a1b26; } .home-button.blue:hover { background-color: #5a7fd8; } .home-button.green { background-color: #9ece6a; color: #1a1b26; } .home-button.green:hover { background-color: #7fb347; } .home-button.orange { background-color: #fab387; color: #1a1b26; } .home-button.orange:hover { background-color: #f9a875; } .home-button.purple { background-color: #cba6f7; color: #1a1b26; } .home-button.purple:hover { background-color: #b794f6; } .home-button.teal { background-color: #94e2d5; color: #1a1b26; } .home-button.teal:hover { background-color: #7dd3c0; } .home-button.pink { background-color: #f38ba8; color: #1a1b26; } .home-button.pink:hover { background-color: #f07aa3; } .home-button.yellow { background-color: #e0af68; color: #1a1b26; } .home-button.yellow:hover { background-color: #d99955; } .home-button.gray { background-color: #bb9af7; color: #1a1b26; } .home-button.gray:hover { background-color: #a78bfa; } .home-button.red { background-color: #f7768e; color: #1a1b26; } .home-button.red:hover { background-color: #f5647a; } .home-button.cyan { background-color: #89dceb; color: #1a1b26; } .home-button.cyan:hover { background-color: #74c7ec; } .home-button.indigo { background-color: #9d7cd8; color: #1a1b26; } .home-button.indigo:hover { background-color: #8b6bc7; } .home-button a, .home-button a:visited, .home-button a:hover, .home-button a:active { color: white; } /* Footer */ #footer-places { display: block !important; column-count: unset !important; } #footer-places ul { display: grid !important; grid-template-columns: repeat(3, max-content); gap: 0.25em 2rem; } #footer-places-about { order: 1; } #footer-places-statuspage { order: 2; } #footer-places-discord { order: 3; } #footer-places-guidelines { order: 4; } #footer-places-transparency { order: 5; } #footer-places-donate { order: 6; } #footer-places-disclaimers { order: 7; } #footer-places-privacy { order: 8; } #footer-places-github { order: 9; } #footer-places li { white-space: nowrap; } @media (max-width: 720px) { #footer-places ul { grid-template-columns: repeat(2, max-content); } } @media (max-width: 480px) { #footer-places ul { grid-template-columns: repeat(1, max-content); } } 2a84c86d9d0dd8e486a4a6266fa2f45c23e9359e 1 1323 5688 2026-06-10T00:58:55Z Larry the cow 402 /* literally me */ new section wikitext text/x-wiki == literally me == like fr [[User:Larry the cow|Larry the cow]] ([[User talk:Larry the cow|talk]]) 00:58, 10 June 2026 (UTC) 95e6fcaaabb9e1c5b24ff0014d2cbefe2daf3765 5689 5688 2026-06-10T01:00:17Z Ok 425 wikitext text/x-wiki == literally me == like fr [[User:Larry the cow|Larry the cow]] ([[User talk:Larry the cow|talk]]) 00:58, 10 June 2026 (UTC) what are we doing with our lives? d0cfb697ff70c8cd3b4626affbf55ee2e140e5a0 6 1324 5691 2026-06-10T02:06:58Z Strangely Human Feeling 415 Artist: Tyson Tan Source Artwork: : https://tysontan.com/temp/electric_20260302A_konqi_kde_30th_logo.zip wikitext text/x-wiki == Summary == Artist: Tyson Tan Source Artwork: : https://tysontan.com/temp/electric_20260302A_konqi_kde_30th_logo.zip == Licensing == {{Unknown_copyright}} 34fecd8fbf0d6311e59a86fa061a0eadbf21a273 0 1325 5693 2026-06-10T02:54:14Z Strangely Human Feeling 415 Created Kori page and added short descriptor wikitext text/x-wiki {{MascotInfobox|caption=KDE's mascot Kori|image=[[File:Mascot KDE Kori.png|Mascot_KDE_Kori|222px]]|title=Kori}}Kori, designed by Tsyon Tan, is a mascot for introduced for [[KDE|KDE's]] 30th anniversary.<ref>https://tysontan.com/</ref><ref>https://kde.org/anniversaries/30/</ref> They're described as a non-binary pet dragon intended to help celebrate pride month during 2026. 62b7e2acb4a045b656f6defb6c239dfe9d78f524 5694 5693 2026-06-10T03:06:07Z Strangely Human Feeling 415 Created Kori page and added short description wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox| caption = KDE's mascot Kori |image = [[File:Mascot KDE Kori.png|Mascot_KDE_Kori|222px]] |title = Kori }} '''Kori''', designed by [https://tysontan.com/ Tsyon Tan], is a mascot for introduced for [[KDE|KDE's]] 30th anniversary.<ref>https://kde.org/anniversaries/30/</ref> They're described as a non-binary pet dragon intended to help celebrate pride month during 2026.<ref>https://bsky.app/profile/kde.org/post/3mn7jyrgzd22l</ref> == References == <references /> a72a77f7771f3483df93b733574233ebf6d3bea3 6 1326 5696 2026-06-10T03:55:26Z Strangely Human Feeling 415 Sources: https://www.xfce.org/download https://web.archive.org/web/20120117065612/http://www.xfce.org/about/artwork https://commons.wikimedia.org/wiki/File:Xfce_logo-footprint.svg wikitext text/x-wiki == Summary == Sources: https://www.xfce.org/download https://web.archive.org/web/20120117065612/http://www.xfce.org/about/artwork https://commons.wikimedia.org/wiki/File:Xfce_logo-footprint.svg == Licensing == {{LGPL}} 83a4db453df91417f1b259c6a708c59180534779 0 568 5698 3694 2026-06-10T03:58:13Z Strangely Human Feeling 415 Replaced XFCE mascot with transparent SVG wikitext text/x-wiki [[Category:Mascots]] {{Needs_Citations}} {{MascotInfobox | title = Xue | image = [[File:Mascot XFCE Xue.svg |frameless |alt=A small black illustrated mouse]] | caption = Xue the XFCE mascot }} Xue is the mascot of [https://xfce.org/ XFCE] Xue is described as a black female mouse in [https://supertuxkart.net/Main_Page SuperTuxKart] 0e920c29f80dd2d8321fd8c21553a91bfa5c6e14 0 1327 5699 2026-06-11T02:26:48Z Wreckvall 426 Created a basic overview for pip with some basic instructions. Needs to be continued wikitext text/x-wiki Pip is a [[Package Manager|package manager]] for [[Python]], used to manage third-party installations. When installing a [[package]] with pip, the internet is used to access [[PyPI]] - an official registry for Python packages - and downloads those onto your machine. === Using Pip in the Terminal === ==== Install a package ==== Replace <code><package_name></code> with the name of the package you want to install (as written in its official PyPI project description). pip install <package_name> ==== Update a package ==== Replace <code><package_name></code> with the name of the package you want to update (as written in its official PyPI project description). pip install --update <package_name> ==== Remove a package ==== Replace <code><package_name></code> with the name of the package you want to remove (as written in its official PyPI project description). pip uninstall <package_name> 172312fa87e9bdb7048e3612123cb7a030f167ce 5700 5699 2026-06-11T04:28:15Z Wreckvall 426 added more use cases for pip and explained python -m wikitext text/x-wiki Pip is a [[Package Manager|package manager]] for [[Python]], used to manage third-party installations. When installing a [[package]] with pip, the internet is used to access [[PyPI]] - an official registry for Python packages - and downloads those onto your machine. === Using Pip in the Terminal === Note that in the commands presented below, the <code>python -m</code> is not necessary (for instance, <code>pip install <package_name></code> works by itself). However, if you have multiple Python versions and pip doesn't belong to the version you want to install the package in, you can use <code>python -m</code> to specify the version. You can check which Python version <code>pip</code> belongs to using the command <code>pip --version</code>. You can also check your default Python version with <code>python --version</code>. If you use <code>python -m</code>, it will correspond to the Python installation with that version. Otherwise, you can specify another version, for instance, <code>python3.12 -m</code> or <code>python3.11 -m.</code> ==== Package details ==== You can obtain the details about a package using: python -m pip show <package_name> Replace <code><package_name></code> with the name of the package you want to investigate (as written in its official PyPI project description). To list even more details, use the option <code>--verbose</code> python -m pip show --verbose <package_name> ==== Install a package ==== Replace <code><package_name></code> with the name of the package you want to install (as written in its official PyPI project description). python -m pip install <package_name> You can also install a specific version, replacing <version_number> with the version number. python -m pip install <package_name>==<version_number> ==== Update a package ==== Replace <code><package_name></code> with the name of the package you want to update (as written in its official PyPI project description). python -m pip install --update <package_name> ==== Remove a package ==== Replace <code><package_name></code> with the name of the package you want to remove (as written in its official PyPI project description). python -m pip uninstall <package_name> ==== Listing packages ==== List all packages installed with pip: python -m pip list You can also show all the packages that are outdated python -m pip list --outdated The option <code>--outdated</code> can also be shortened to <code>-o</code>. ==== Saving Requirements ==== You can save all your installed packages into a file, and use that file to install all those packages in a new setup, saving you from having to manually reinstall each individual package. In [[Linux]], you can save your packages into the file <code>req.txt</code> with the command: python -m pip freeze > req.txt Then, you can use the contents of <code>req.txt</code> to install the packages using: python -m pip install -r req.txt a90105f8664edcdd4635b7ab97c0be84ec09f88b 0 8 5701 5552 2026-06-11T04:57:33Z Wreckvall 426 restructured the article a lot. let me know what you think! wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. === Unix Philosophy: Key Concepts === The design of Linux is based on some core tenets, including: # '''Do One Thing and Do It Well:''' Instead of having large monolithic programs that try to do everything, Linux tends to have smaller simple tools can be combined or chained together, allowing for complex results with high customisability and user control. # '''Treat Everything as a File:''' Everything is a file, including all the commands you use, external devices, processes, etc... This allows for easy, consistent access. # '''Text-Based Configurations:''' Maybe configuration files and system settings are stored in a easy-to-read and easy-to-edit plaintext form. # '''Open Source:''' See the article about [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] Linux avoids [[bloat]] and values [[privacy]]. Other terms: * [[RTFM]] * [[Security]] === Get Started with Linux === You might have to configure these when you first install linux: [[Drivers]] [[Linux kernel]] [[Linux Distributions|Linux Distribution]] ([[Derivative]]) === The Command Line === See these articles to learn about the command line: * [[CLI|Command-Line Interface (CLI)]] * [[Command]] Many Linux distributions use [[bash]]. Learn some common bash commands, including: * '''Text Editing:''' ** [[nano]] ** [[micro]] ** [[vim]] * '''Compression:''' ** [[Tar.xz|tar.xz / Tarball]] Other important concepts to learn to use the command line include: * [[Ownership]] * [[Processes|Processes and Jobs]] === User Interfaces === Two main types of user interfaces: [[GUI|Graphical User Interface (GUI)]] and [[TUI|Text-Based User Interface (TUI)]]. Some common [[Desktop Environment‏‎|Desktop Environment‏‎s]] include: * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] Before you login: [[Display Manager]] After you login: [[Window Manager|Window Managers]] * [[DWM]] * [[Hyprland]] * [[IceWM]] * [[i3]] Have fun with [[Ricing|Theming / "Ricing"]]! === Packages === [[Repository|Repository (Repo)]] [[Package]] [[Package Manager|Package Managers]] * [[APK|apk]] * [[APT|apt]] * [[DNF|dnf]] * [[DPKG|dpkg]] * [[flatpak]] * [[NixOS|nix]] * [[pacman]] * [[portage]] * [[RPM|rpm]] * [[snap]] * [[zypper]] === General Programming === [[Script]] [[Program]] Learn some [[:Category:Programming Languages|programming languages]]. Beginner friendly ones include: * [[Python]] * [[Javascript]] These are "high-level" languages that [[abstract]] away the inner workings of the computer. Low level languages include: * [[Assembly]] == Advanced Terms == In effort to avoid stressing new users, there are some subjectively more complicated topics most new users will not ''need'' to learn about, unless they are trying to perform some specific task. * [[Building / Compiling]] * [[Compositor]] ** [[Wayland]] ** [[X11]] * [[Git]] * [[GitHub]] * [[GNU]] * [[Hacking]] ** [[Cybersecurity]] ** [[DDoS]] ** [[ARPANET]] ** [[Ransomware]] ** [[Penetration testing|Penetration Testing]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * [[Kernel]] * [[Kernel Module]] * [[Licenses]] * [[Shell]] ** [[Bash]] ** [[Zsh]] * [[TTY]] * [[X.Org]] * [[Xwayland]] __INDEX__ __NEWSECTIONLINK__ 691c0e9ab89d6ffc1b69a71b7369610ce73d25ed 5716 5701 2026-06-12T12:14:41Z Wreckvall 426 incorporated the advanced terms into the structure too wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. === Unix Philosophy: Key Concepts === It is important to note that Linux is not an operating system, it is a [[kernel]]. The actual operating system is [[GNU]], which uses the Linux kernel. Also note that not all 'Linux' systems use GNU (take Android, for example). GNU also values user freedom, and have based their [[licence]] on four principles. To cite their website:<blockquote>(0) to run the program, (1) to study and change the program in source code form, (2) to redistribute exact copies, and (3) to distribute modified versions.<ref>{{Cite|url=https://www.gnu.org/philosophy/philosophy.html|title=GNU Operating System|accessdate=2026/06/12|year=2025/05/17}}</ref></blockquote>The design of the Linux kernel is also based on some core tenets, including: # '''Do One Thing and Do It Well:''' Instead of having large monolithic programs that try to do everything, Linux tends to have smaller simple tools can be combined or chained together, allowing for complex results with high customisability and user control. # '''Treat Everything as a File:''' Everything is a file, including all the commands you use, external devices, processes, etc... This allows for easy, consistent access. # '''Text-Based Configurations:''' Maybe configuration files and system settings are stored in a easy-to-read and easy-to-edit plaintext form. # '''Open Source:''' See the article about [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] Linux avoids [[bloat]] and values [[privacy]]. Other terms: * [[RTFM]] * [[Security]] === Get Started with Linux === You might have to configure these when you first install Linux: [[Drivers]] Some helpful terms: * [[Linux kernel]] * [[Linux Distributions|Linux Distribution]] ([[Derivative]]) * [[Kernel]] and [[Kernel Module]] (advanced) === The Command Line === See these articles to learn about interacting with the terminal: * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * (a more advanced concept) [[TTY]] Many Linux distributions use [[bash]]. Learn some common bash commands, including: * '''Text Editing:''' ** [[nano]] ** [[micro]] ** [[vim]] * '''Compression:''' ** [[Tar.xz|tar.xz / Tarball]] Other important concepts to learn to use the command line include: * [[Ownership]] * [[Processes|Processes and Jobs]] There are also different kinds of [[Shell|shells]] you can use, though this is a more advanced concept. * [[Bash]] * [[Zsh]] === User Interfaces === Two main types of user interfaces: [[GUI|Graphical User Interface (GUI)]] and [[TUI|Text-Based User Interface (TUI)]]. Some common [[Desktop Environment‏‎|Desktop Environment‏‎s]] include: * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] Before you login: [[Display Manager]] After you login: [[Window Manager|Window Managers]] * [[DWM]] * [[Hyprland]] * [[IceWM]] * [[i3]] A more advanced concept is the [[Compositor]]. There are two main architectures for compositors: * [[Wayland]] * [[X11]] (protocol) ** [[X.Org]] (application) [[Xwayland]] exists to bridge these two architectures. Have fun with [[Ricing|Theming / "Ricing"]]! === Packages === [[Repository|Repository (Repo)]] [[Package]] [[Package Manager|Package Managers]] * [[APK|apk]] * [[APT|apt]] * [[DNF|dnf]] * [[DPKG|dpkg]] * [[flatpak]] * [[NixOS|nix]] * [[pacman]] * [[portage]] * [[RPM|rpm]] * [[snap]] * [[zypper]] === General Programming === [[Script]] [[Program]] Learn some [[:Category:Programming Languages|programming languages]]. Beginner friendly ones include: * [[Python]] * [[Javascript]] These are "high-level" languages that [[abstract]] away the inner workings of the computer. Low level languages include: * [[Assembly]] Other more advanced terms include: * [[Building / Compiling]] * [[Git]] and [[GitHub]] are useful for saving your coding projects === General Programming === [[Hacking]] and [[Cybersecurity]] terms: * Early internet: [[ARPANET]] * Attacks: ** [[DDoS]] ** [[Ransomware]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * Defence: ** [[Penetration testing|Penetration Testing]] __INDEX__ __NEWSECTIONLINK__ ac503a87444b008ec4455dc99cfb27ace3057a36 5717 5716 2026-06-12T12:17:28Z Wreckvall 426 /* Unix Philosophy: Key Concepts */ minor clearup wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. === Unix Philosophy: Key Concepts === It is important to note that Linux by itself is not an operating system, it is a [[kernel]]. The actual operating system is [[GNU]], which uses the Linux kernel. When people say the 'Linux operating system,' they mean the GNU/Linux operating system. Also note that not all 'Linux' systems use GNU (take Android, for example). GNU also values user freedom, and have based their [[licence]] on four principles. To cite their website:<blockquote>(0) to run the program, (1) to study and change the program in source code form, (2) to redistribute exact copies, and (3) to distribute modified versions.<ref>{{Cite|url=https://www.gnu.org/philosophy/philosophy.html|title=GNU Operating System|accessdate=2026/06/12|year=2025/05/17}}</ref></blockquote>The design of the Linux kernel is also based on some core tenets, including: # '''Do One Thing and Do It Well:''' Instead of having large monolithic programs that try to do everything, Linux tends to have smaller simple tools can be combined or chained together, allowing for complex results with high customisability and user control. # '''Treat Everything as a File:''' Everything is a file, including all the commands you use, external devices, processes, etc... This allows for easy, consistent access. # '''Text-Based Configurations:''' Maybe configuration files and system settings are stored in a easy-to-read and easy-to-edit plaintext form. # '''Open Source:''' See the article about [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] Linux avoids [[bloat]] and values [[privacy]]. Other terms: * [[RTFM]] * [[Security]] === Get Started with Linux === You might have to configure these when you first install Linux: [[Drivers]] Some helpful terms: * [[Linux kernel]] * [[Linux Distributions|Linux Distribution]] ([[Derivative]]) * [[Kernel]] and [[Kernel Module]] (advanced) === The Command Line === See these articles to learn about interacting with the terminal: * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * (a more advanced concept) [[TTY]] Many Linux distributions use [[bash]]. Learn some common bash commands, including: * '''Text Editing:''' ** [[nano]] ** [[micro]] ** [[vim]] * '''Compression:''' ** [[Tar.xz|tar.xz / Tarball]] Other important concepts to learn to use the command line include: * [[Ownership]] * [[Processes|Processes and Jobs]] There are also different kinds of [[Shell|shells]] you can use, though this is a more advanced concept. * [[Bash]] * [[Zsh]] === User Interfaces === Two main types of user interfaces: [[GUI|Graphical User Interface (GUI)]] and [[TUI|Text-Based User Interface (TUI)]]. Some common [[Desktop Environment‏‎|Desktop Environment‏‎s]] include: * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] Before you login: [[Display Manager]] After you login: [[Window Manager|Window Managers]] * [[DWM]] * [[Hyprland]] * [[IceWM]] * [[i3]] A more advanced concept is the [[Compositor]]. There are two main architectures for compositors: * [[Wayland]] * [[X11]] (protocol) ** [[X.Org]] (application) [[Xwayland]] exists to bridge these two architectures. Have fun with [[Ricing|Theming / "Ricing"]]! === Packages === [[Repository|Repository (Repo)]] [[Package]] [[Package Manager|Package Managers]] * [[APK|apk]] * [[APT|apt]] * [[DNF|dnf]] * [[DPKG|dpkg]] * [[flatpak]] * [[NixOS|nix]] * [[pacman]] * [[portage]] * [[RPM|rpm]] * [[snap]] * [[zypper]] === General Programming === [[Script]] [[Program]] Learn some [[:Category:Programming Languages|programming languages]]. Beginner friendly ones include: * [[Python]] * [[Javascript]] These are "high-level" languages that [[abstract]] away the inner workings of the computer. Low level languages include: * [[Assembly]] Other more advanced terms include: * [[Building / Compiling]] * [[Git]] and [[GitHub]] are useful for saving your coding projects === General Programming === [[Hacking]] and [[Cybersecurity]] terms: * Early internet: [[ARPANET]] * Attacks: ** [[DDoS]] ** [[Ransomware]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * Defence: ** [[Penetration testing|Penetration Testing]] __INDEX__ __NEWSECTIONLINK__ 6dbe73e8dea28f74286236c99895041611f4470e 0 1265 5702 5636 2026-06-11T06:56:00Z Madonuko 140 explain ''Wine is not emulator''; /* Installation */ add /* Fedora Linux */ wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Wine | image = [[File:Wine Logo.png|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = [[C]] | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine was originally a recursive acronym for ''Wine is not emulator''. Wine does not perform emulation of a Windows system; it provides libraries (DLLs) needed by the Windows programs, and these libraries are implemented to instead invoke Linux system calls, similar to how [[Cygwin]] functions on Windows. Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. == Installation == {{Guide Warning}} === [[Arch Linux]] === Stable: <syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight> Staging: <syntaxhighlight lang="sh">sudo pacman -S wine-staging</syntaxhighlight> === [[Fedora Linux]] === Wine stable is available via <code>sudo dnf install wine</code>. Other versions of Wine are available in [[Terra]] under the package name <code>terra-wine-stable</code>, <code>terra-wine-staging</code>, and <code>terra-wine-dev</code>. [[Winetricks]] and [[dxvk]] support (mentioned [[#dxvk|below]]) are also provided via <code>terra-winetricks</code> and <code>terra-wine-dxvk</code>. <code>[[protontricks]]</code>, <code>winetricks</code>, and <code>winetricks-git</code> are also available in Fedora. == Usage == Wine is a [[CLI|command-line]] program. Provide a Windows executable file for Wine to run: <syntaxhighlight lang="sh">wine <path to .exe></syntaxhighlight> === Prefixes === Wine stores configuration files and installed programs inside a ''Wine prefix''. Wine prefixes contain a minimal Windows filesystem (a.k.a. ''C: drive''). The default Wine prefix is <code>~/.wine</code>. You can modify the <code>WINEPREFIX</code> environment variable to change it. For example, to use the directory <code>myprefix/</code> as the Wine prefix to run <code>application.exe</code>: <syntaxhighlight lang="sh">WINEPREFIX=myprefix wine application.exe</syntaxhighlight> == Performance == === dxvk === By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). == References == <references /> 4086d638e2228df8d662995ece2582fd0ef3588d 5703 5702 2026-06-11T06:59:14Z Madonuko 140 cite better perf than emulation wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Wine | image = [[File:Wine Logo.png|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = [[C]] | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. Wine was originally a recursive acronym for ''Wine is not emulator''. Wine does not perform emulation of a Windows system; it provides libraries (DLLs) needed by the Windows programs, and these libraries are implemented to instead invoke Linux system calls, similar to how [[Cygwin]] functions on Windows. This makes its performance much better than other emulation software.<ref>[https://www.howtogeek.com/windows-apps-in-wine-vs-vms/ Running Windows Apps in Wine vs. VMs: Which Is Better?], How-To Geek, 2024 (Accessed: 11 June 2026)</ref> Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. == Installation == {{Guide Warning}} === [[Arch Linux]] === Stable: <syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight> Staging: <syntaxhighlight lang="sh">sudo pacman -S wine-staging</syntaxhighlight> === [[Fedora Linux]] === Wine stable is available via <code>sudo dnf install wine</code>. Other versions of Wine are available in [[Terra]] under the package name <code>terra-wine-stable</code>, <code>terra-wine-staging</code>, and <code>terra-wine-dev</code>. [[Winetricks]] and [[dxvk]] support (mentioned [[#dxvk|below]]) are also provided via <code>terra-winetricks</code> and <code>terra-wine-dxvk</code>. <code>[[protontricks]]</code>, <code>winetricks</code>, and <code>winetricks-git</code> are also available in Fedora. == Usage == Wine is a [[CLI|command-line]] program. Provide a Windows executable file for Wine to run: <syntaxhighlight lang="sh">wine <path to .exe></syntaxhighlight> === Prefixes === Wine stores configuration files and installed programs inside a ''Wine prefix''. Wine prefixes contain a minimal Windows filesystem (a.k.a. ''C: drive''). The default Wine prefix is <code>~/.wine</code>. You can modify the <code>WINEPREFIX</code> environment variable to change it. For example, to use the directory <code>myprefix/</code> as the Wine prefix to run <code>application.exe</code>: <syntaxhighlight lang="sh">WINEPREFIX=myprefix wine application.exe</syntaxhighlight> == Performance == === dxvk === By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). == References == <references /> 36a3186590360e24a8c6c27854462e7ffdf63f14 6 1328 5704 2026-06-11T12:01:08Z Rob Kam 380 wikitext text/x-wiki == Licensing == {{GPL}} 6b26f5cce63faf4ce1130ffc4f5c42cf3e3a00ac 0 1182 5705 5282 2026-06-11T12:09:55Z Rob Kam 380 Revert article to Werner Bregulla’s original Ytree v2; update content from official site wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Ytree screenshot.gif|frameless]] | caption = Ytree screenshot | title = Ytree | releasestatus = Active | lastrelease = 2.13 (2026-06-10) | languages = [[C]] | developers = Werner Bregulla | website = https://www.han.de/~werner/ytree.html }} '''Ytree''' (<code>ytree</code>) is a keyboard-driven [[TUI]] file manager for UNIX-like systems. It is a curses-based file manager inspired by DOS XTree, designed for browsing filesystems and archives quickly from the terminal.<ref name="ytree">[https://www.han.de/~werner/ytree.html Ytree Home Page], han.de (Accessed: 2026-06-11)</ref> == Overview == Ytree presents a multi-pane terminal interface with a directory tree, file window, and information/statistics pane. It supports browsing filesystems and archive formats, including RAR, SPM, RPM, TAR, ARC, LHA, ZIP, and ZOO.<ref name="ytree" /> The project has long emphasized keyboard-oriented navigation and file operations, following the style of the original XTree family of file managers.<ref name="ytree" /> == Features == === Archive browsing === Ytree can browse supported archives as if they were directories, allowing file navigation within compressed or packaged content.<ref name="ytree" /> === Terminal user interface === The interface is curses-based and optimized for fast keyboard interaction in a text terminal.<ref name="ytree" /> === Platform support === The project has been reported to run on a wide range of UNIX and UNIX-like systems, including classic systems as well as modern platforms such as Linux, FreeBSD, OpenBSD, NetBSD, Mac OS X, and Haiku.<ref name="ytree" /> == Release history == The original project site lists recent releases and fixes. As of 2026-06-11, the latest published release is 2.13, dated 2026-06-10. Recent updates include Haiku OS support and various bug fixes and compatibility improvements.<ref name="ytree" /> === Selected recent releases === * '''2.13''' — Haiku OS support * '''2.12''' — fix for a compile error in <code>CutFilename</code> * '''2.11''' — removal of the clock display, UnixWare 7 support, UTF-8 input fixes, and minor bug fixes * '''2.10''' — 7zip / ISO support and compile support for GCC 15 * '''2.09''' — window resize support for hex view and hex edit, display improvements == Building == The project page says that in most cases it is sufficient to enable the appropriate platform section in the <code>Makefile</code>, then run <code>make</code> and <code>make install</code>. Users may also customize Ytree through <code>$HOME/.ytree</code>.<ref name="ytree" /> == Platforms == The site lists Ytree as running on or being reported for the following platforms:<ref name="ytree" /> * SYSV R3.2/R4 * Interactive UNIX * Linux * NeXTstep 2.1 * IRIX 5.2 * AIX 3.2 * HP-UX * SunOS 4.1 / Solaris 2 * ULTRIX 4.3 * DEC-UNIX / OSF1 * FreeBSD * OpenBSD * NetBSD * QNX * Mac OS X * DJGPP * Haiku == Availability == The project page provides the source tarball directly from the website, and also links to package listings and ports for several operating systems.<ref name="ytree" /> == Related projects == The original site also links to other XTree-related resources, including the XTree Fan Page and the homepage of Jeff Johnson, the creator of the original XTree and XTreeGold.<ref name="ytree" /> == Copyright == Ytree is distributed as free software under the GNU General Public License, version 2 or later.<ref name="ytree" /> == Contact == Bug reports, comments, and patches are welcomed via the maintainer's email address listed on the project site.<ref name="ytree" /> == See also == * [[UnixTree]] * [[YtreeNova]] == References == {{reflist}} [[Category:Software]] [[Category:File managers]] 3aa39de01c15b8a5e90e4c25ac37f814c037e949 6 1329 5706 2026-06-11T13:00:18Z Rob Kam 380 wikitext text/x-wiki == Licensing == {{CC-BY-SA-4.0}} c66ccb1aacf84edb16d0f0ce6d1e5ce300a1d6ae 0 1330 5707 2026-06-11T13:00:54Z Rob Kam 380 Document YtreeNova fork and status wikitext text/x-wiki {{SoftwareInfobox | image = [[File:YtreeNova F8 split view.png|frameless]] | caption = YtreeNova in F8 split view | title = YtreeNova | releasestatus = Alpha (maintained) | lastrelease = v1.0.0-alpha | languages = [[C]] | developers = Rob Kam; forked from original Ytree by Werner Bregulla | website = https://github.com/robkam/ytreenova }} '''YtreeNova''' (<code>ytnova</code>), is a keyboard-first [[TUI]] file manager for UNIX-like systems. It is a fork of Werner Bregulla's [[Ytree]], redesigned around a "logger" model that scans directory trees into memory so users can navigate, filter, tag, and operate across large file hierarchies quickly.<ref name="ytreenova">[https://github.com/robkam/ytreenova README.md], github.com/robkam/ytreenova (Accessed: 2026-06-11)</ref><ref name="man">[https://github.com/robkam/ytreenova/blob/main/etc/ytnova.1.md etc/ytnova.1.md], github.com/robkam/ytreenova (Accessed: 2026-06-11)</ref> == Overview == YtreeNova is inspired by DOS XTree-style workflows and presents a multi-pane terminal interface with a directory tree, file window, and info/statistics pane. It supports multiple operating modes, including Directory, File, Showall, Global, Archive, Split Screen, and Preview.<ref name="man" /> The project continues the XTree-style keyboard-driven approach while expanding the original Ytree codebase with additional features and modernized behavior.<ref name="ytreenova" /> == Features == === Multi-volume logging === YtreeNova can log one or more directories or archives at startup and switch between logged volumes quickly.<ref name="man" /> === Split screen and preview === It includes split-screen panel mode and integrated file preview mode for rapid file inspection and comparison.<ref name="man" /> === Archive-as-directory workflow === Supported archives, such as ZIP, TAR, and GZ, can be browsed like virtual directories, with archive-aware operations where supported.<ref name="man" /> === Keyboard-driven workflow === The interface is designed for efficient terminal use, with navigation and file management centered on the keyboard.<ref name="ytreenova" /> == Development status == As of 2026-06-10, YtreeNova is in active alpha development. The repository describes it as a maintained fork of Ytree with ongoing work and expanding functionality.<ref name="ytreenova" /><ref name="man" /><ref>[https://github.com/robkam/ytreenova/tags Tags], github.com/robkam/ytreenova (Accessed: 2026-06-11)</ref> == History == YtreeNova began as a fork of Ytree and was renamed to distinguish the project from Werner Bregulla's original upstream, which remains active.<ref name="ytreenova" /> == References == <references /> [[Category:Software]] [[Category:File managers]] c7ae6a7686ae0ce8f8e5e16a772466be6cbfad21 5710 5707 2026-06-11T13:16:29Z Rob Kam 380 wikitext text/x-wiki {{SoftwareInfobox | image = [[File:YtreeNova F8 split view.png|frameless]] | caption = YtreeNova in F8 split view | title = YtreeNova | releasestatus = Alpha (maintained) | lastrelease = v1.0.0-alpha | languages = [[C]] | developers = Rob Kam; forked from original Ytree by Werner Bregulla | website = https://github.com/robkam/ytreenova }} '''YtreeNova''' (<code>ytnova</code>), is a keyboard-first [[TUI]] file manager for UNIX-like systems. It is a fork of Werner Bregulla's [[Ytree]], redesigned around a "logger" model that scans directory trees into memory so users can navigate, filter, tag, and operate across large file hierarchies quickly.<ref name="ytreenova">[https://github.com/robkam/ytreenova README.md], github.com/robkam/ytreenova (Accessed: 2026-06-11)</ref><ref name="man">[https://github.com/robkam/ytreenova/blob/main/etc/ytnova.1.md etc/ytnova.1.md], github.com/robkam/ytreenova (Accessed: 2026-06-11)</ref> == Overview == YtreeNova is inspired by DOS XTree-style workflows and presents a multi-pane terminal interface with a directory tree, file window, and info/statistics pane. It supports multiple operating modes, including Directory, File, Showall, Global, Archive, Split Screen, and Preview.<ref name="man" /> The project continues the XTree-style keyboard-driven approach while expanding the original Ytree codebase with additional features and modernized behavior.<ref name="ytreenova" /> == Features == === Multi-volume logging === YtreeNova can log one or more directories or archives at startup and switch between logged volumes quickly.<ref name="man" /> === Split screen and preview === It includes split-screen panel mode and integrated file preview mode for rapid file inspection and comparison.<ref name="man" /> === Archive-as-directory workflow === Supported archives, such as ZIP, TAR, and GZ, can be browsed like virtual directories, with archive-aware operations where supported.<ref name="man" /> === Keyboard-driven workflow === The interface is designed for efficient terminal use, with navigation and file management centered on the keyboard.<ref name="ytreenova" /> == Development status == As of 2026-06-10, YtreeNova is in active alpha development. The repository describes it as a maintained fork of Ytree with ongoing work and expanding functionality.<ref name="ytreenova" /><ref name="man" /><ref>[https://github.com/robkam/ytreenova/tags Tags], github.com/robkam/ytreenova (Accessed: 2026-06-11)</ref> == History == YtreeNova began as a fork of Ytree and was renamed to distinguish the project from Werner Bregulla's original upstream, which remains active.<ref name="ytreenova" /> == See also == * [[Ytree]] * [[UnixTree]] == References == <references /> == External links == * [https://github.com/robkam/ytreenova YtreeNova], GitHub repository [[Category:Software]] [[Category:File managers]] 43b712821234d8e408209bc412823790d5ac8333 6 1181 5708 4944 2026-06-11T13:04:55Z Rob Kam 380 wikitext text/x-wiki {{Cleanup|The file is an unused duplicate.}} fccf8f2e119a6799f7130eb87ccf88eaf97d56ba 0 1331 5709 2026-06-11T13:13:33Z Rob Kam 380 Created page with "'''UnixTree''' is a console-mode file manager for Unix and Linux systems, modeled after DOS XTreeGold. It provides keyboard-driven file and directory management, archive browsing, FTP logging, and an application menu for user-defined commands.<ref name="unixtree">[https://www.unixtree.org/ UnixTree.org home page], [https://www.unixtree.org/details.htm details], and [https://www.unixtree.org/history.htm history] (accessed 2026-06-11)</ref> == Overview == UnixTree describ..." wikitext text/x-wiki '''UnixTree''' is a console-mode file manager for Unix and Linux systems, modeled after DOS XTreeGold. It provides keyboard-driven file and directory management, archive browsing, FTP logging, and an application menu for user-defined commands.<ref name="unixtree">[https://www.unixtree.org/ UnixTree.org home page], [https://www.unixtree.org/details.htm details], and [https://www.unixtree.org/history.htm history] (accessed 2026-06-11)</ref> == Overview == UnixTree describes itself as a powerful and versatile terminal-based file manager for Unix-like systems. It is designed for fast filesystem navigation and for performing file operations across selected files in a directory tree.<ref name="unixtree" /> == History == The project began as '''xtree for UNIX Systems''' and was later renamed '''UnixTree'''. The history page lists releases from the original 1.00 line through later UnixTree releases, including 2.20 and 3.0.x.<ref name="unixtree" /> == Features == * keyboard-oriented navigation inspired by XTreeGold<ref name="unixtree" /> * archive support, including tar and gz<ref name="unixtree" /> * FTP logging<ref name="unixtree" /> * an application menu for user-defined commands<ref name="unixtree" /> * its own curses package rather than the system curses or ncurses libraries<ref name="unixtree" /> == Platforms == The site lists UnixTree builds or ports for a wide range of platforms, including Linux, FreeBSD, Mac OS X, AIX, HP-UX, Solaris, SCO systems, and Windows.<ref name="unixtree" /> == License == UnixTree is released as free software under the GNU General Public License.<ref name="unixtree" /> == See also == * [[Ytree]] * [[YtreeNova]] == External links == * [https://www.unixtree.org/ Official website] == References == <references /> [[Category:Software]] [[Category:File managers]] {{stub}} 4eda31645b35416c4e3d28aedcdf4af7325ca908 14 1332 5711 2026-06-11T13:21:55Z Rob Kam 380 Created page with "[[Category:Software]]" wikitext text/x-wiki [[Category:Software]] 3177c712ce9cabbfd5a2ce2820b693582d921e11 2 1186 5712 5026 2026-06-11T13:23:14Z Rob Kam 380 wikitext text/x-wiki * [https://github.com/robkam/ytreenova YtreeNova: a File Manager for Unix-like Systems] a24b2e59228898bc1db8c3e98fbb2a7c62f60adc 0 218 5713 5453 2026-06-11T19:11:52Z Lawl 419 add qualities table to aid users in finding more distros that are lightweight + add to gentoo and alpine thingy wikitext text/x-wiki [[Category:Guides]] [[Linux]] due to its generally lower system requirements than [[Windows]]<ref>[https://palmertech.medium.com/revive-old-hardware-with-linux-4091821db8c3 Revive Old Hardware with Linux], Aidan Palmer, 2023-03-05 (Accessed: 2025-08-09)</ref> or [[macOS]] and a general absence of vendor-imposed hardware restrictions is frequently chosen for reviving and reusing older devices. == Choosing a Desktop Environment == While a lot of focus is usually put on the choice of distribution, the [[Desktop Environment‏‎]] (or [[Window Manager]]) used is often far more important. If your system has a relatively large amount of RAM (8+GB), but a slow CPU, a 'heavier' desktop environment like [[KDE Plasma]] or [[GNOME]] may still be usable. {| class="wikitable" |+ !Desktop Environment !Pros !Cons !Other Notes |- |[[Xfce|XFCE]] | * Minimal background processes (lightweight) * Easy to use with a low to medium learning curve | * Panel system may be confusing to new users * May look outdated without a theme installed |This is the most common recommendation for a light desktop environment |- |[[LXQT]] | * Minimal background processes (lightweight) * Easy to use with a small learning curve due to using the Windows desktop paradigm | * May look outdated without a theme installed |LXQT is the modern version of the older LXDE, which was also known for being lightweight |- |Most Window managers (TWMs or WMs) | * Require very few system resources beyond those of the display server | * More difficult to use due to having a keyboard-centric interface * Require text-based configuration to fit the preferences of the user * May require extra tools for some functionality (i.e. keyrings, polkit, GTK, QT, etc.) |Usually require command line knowledge to troubleshoot |} == Choosing a Distribution == When choosing a distribution, it is important to bear in mind what the device will be used for, and the hardware of the system. If a computer is less than 10 years old, it is likely that no special treatment will be needed, and almost any Linux distribution, such as Linux Mint, will be fast and responsive. There are several distributions that are widely recommended by the community: ''Note: While this does mention some general pros and cons of certain distributions, such as ease of installation, that do not affect performance, it should not be used as a comprehensive guide on choosing a distribution for use cases outside of restoring older devices.'' '''Also refer to [[Choosing A Linux Distribution]] for more information not related to installation on older systems.''' {| class="wikitable" |+ !Distribution !Pros !Cons !Recommended Use Case !Other Notes |- |[[Linux Mint]]<ref>[https://www.linuxmint.com/faq.php Frequently Asked Questions - Linux Mint], Linux Mint, 2006-08-09 (Accessed: 2025-08-09)</ref> | * Easy to install * Reasonably lightweight | * May not include some packages desired by advanced users without PPAs or building from source * Is not the lightest distribution available | * 2+GB of RAM * Intel Core i-series 2nd Generation or newer |Linux Mint provides several versions with different desktop environments. The lightest of these is XFCE. This is the version, instead of the default Cinnamon version, being referred to on this page unless otherwise noted. |- |[[Debian]]<ref>[https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <span style="color:#fc493b">https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html <sup>🍣404]{{Dead Link|2026-05-26|404}}</ref> | * Automated installation * Has a minimum amount of installed packages installed by default * Has a minimum amount of running services by default | * NetInstaller is hard to use (Use the live environment's Calamares installer instead when possible) * Minimal package base means some desired packages will not be installed by default | * CPU * 512MB RAM (With minimal GUI) * Any AMD64 (AKA x64 or x86_64) CPU | * The Live environment should be used instead of the net-installer if a simple installation is desired |- |[[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Frequently_asked_questions Frequently asked questions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref><ref>[https://wiki.archlinux.org/title/Arch_compared_to_other_distributions Arch compared to other distributions], ArchWiki, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Extremely lightweight due to only using specific user-selected packages * Wide package availability from the AUR | * Difficult and time-consuming to install * Minimal package base means some desired packages will not be installed by default | * 512MB RAM (With minimal GUI) * AMD64, Aarch64, i386 or Mips CPU | * Arch Linux will not be covered in this article |- |[[Fedora]]<ref>[https://fedoraproject.org/wiki/FAQ FAQ], Fedora Project Wiki, 2025-07-24 (Accessed: 2025-08-09)</ref><ref>[https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/hardware_overview/#hardware_overview-specs Hardware Overview], Fedora Docs, 2025-08-09 (Accessed: 2025-08-09)</ref> | * Considered user-friendly | * Fedora (with the default GNOME) is very resource-taking. The [https://fedoraproject.org/spins/ XFCE spin] is a better option for older devices. * Has little documentation | * 2GB RAM (For default GNOME desktop environment) * Any AMD64 with dual core processor or faster | |- |[[Gentoo]] | * Extremely lightweight * Large variety of hardware support * Packages are compiled from source by default, allowing good optimization * Very well written wiki and great community | * Difficult installation * Long install or package install process due to source compilation being very long on older devices | * Any of these CPU architectures: amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 * '''CPU:''' 1 GHz * '''RAM:''' 512 MB or higher. * '''Disk Space:''' At least 8 GB | |- |[[Puppy Linux]] | * Considered user-friendly * Very light * Very fast on old devices * Easy installation | * [[Bloat|Bloated]] * Few and possibly outdated documentation | * Processor with a clock frequency of at least 300 MHz * RAM not less than 128 MB * 512 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 1024x768 pixels * CD/DVD drive or USB port for booting the system<ref name=":0">[https://pq.hosting/en/help/distributions/424-sistemnye-trebovanija-dlja-puppy-linux.html System requirements for Puppy Linux]{{Dead Link|2026-05-26|404}}, THE.Hosting, 2023-04-23 (Accessed: 2025-08-09)</ref> | |- |[[Tiny Core Linux]] | * Very Light * Very Fast on old devices * GUI desktop * GUI installer | | * Processor with a clock frequency of at least 50 MHz * RAM not less than 46 MB * 12 MB of free space on a hard disk or USB drive * Video card with support for a screen resolution of at least 640x480 pixels * CD/DVD drive or USB port for booting the system<ref name=":0" /> | |- |[[Alpine Linux]] | * Extremely lightweight * Fast package manager * Extremely helpful set of setup or installation utilities installed by default | | * Atleast 128MB of RAM, however more is recommended for installation process * 0-700MB of storage, however not needed on the diskless install. * Working internet connection (not needed in extended base image) |} There are many, many more Linux distributions that will most likely not end up on this list. However, there are multiple qualities of a Linux distribution that indicate it will be lightweight enough to run on older devices: {| class="wikitable" |+ !Quality !Description |- |[[Musl]] |A very lightweight libc, aiming to be smaller than [[uClibc]]. |- |[[Busybox]] |A software package that combines tiny versions of many common UNIX utilities into a single, small executable. |} == Troubleshooting == ''No troubleshooting information specific to installing Linux on older devices has been contributed'' == References == <references /> a4fbf3d2f83612c22f355325a318c9ba6879f477 2 1333 5714 2026-06-11T19:20:19Z Lawl 419 bio meow wikitext text/x-wiki hii!!! i'm lawl :3 heres a little profile that tells you how to contact me mainly, my main bio is at https://lawl.oss.zone. - email: [http://mailto:lawlcat@cock.li lawlcat@cock.li] - discord: @lawlkitty my pgp key is provided on my website!! d104ee2a99c78912d7e85e75f7a83225772becca 2 1334 5715 2026-06-11T21:10:53Z Ephemeral8997 427 custom theming css text/css :root { --background-color-base: #0d0f10 !important; --background-color-primary: #141719 !important; --background-color-secondary: #1b1e20 !important; --background-color-interactive: #222629 !important; --background-color-tabs: #181b1d !important; --color-base: #bcc4c9 !important; --color-primary: #94a3ab !important; --color-secondary: #6e7b82 !important; --color-link: #8ea1a8 !important; --color-link-visited: #66747a !important; --color-link-active: #d2dadf !important; --border-color-base: #222629 !important; --border-color-primary: #1b1e20 !important; } h1, h2, h3, h4, h5, h6, .mw-first-heading { font-family: "Times New Roman", Georgia, serif !important; font-weight: 400 !important; color: #dae2e6 !important; letter-spacing: 0.06em !important; text-transform: uppercase; border-bottom: 1px solid #1b1e20 !important; } body, html, .mw-body, #content, .oo-ui-panelLayout { background-color: #0d0f10 !important; color: #bcc4c9 !important; } .wikitable { background-color: #141719 !important; color: #bcc4c9 !important; border: 1px solid #222629 !important; } .wikitable th { background-color: #1b1e20 !important; color: #dae2e6 !important; font-family: "Times New Roman", serif !important; border: 1px solid #222629 !important; } .wikitable td { border: 1px solid #1b1e20 !important; } .mw-highlight { background-color: #141719 !important; border: 1px solid #222629 !important; border-left: 3px solid #6e7b82 !important; } .oo-ui-buttonElement-button { background-color: #1b1e20 !important; border-color: #222629 !important; color: #bcc4c9 !important; border-radius: 0px !important; } .oo-ui-buttonElement-button:hover { background-color: #222629 !important; color: #dae2e6 !important; } 878e2802d250ae3d2e8480151446e51291c847d9 0 1335 5718 2026-06-12T22:01:29Z Lawl 419 start ssh paeg wikitext text/x-wiki {{Work In Progress}} SSH, also known as the '''Secure Shell Protocol''', is a cryptographic network protocol used to operate network services securely over an unsecured network.<ref>[https://www.rfc-editor.org/rfc/rfc4251 RFC 4251 - The Secure Shell (SSH) Protocol Architecture]</ref> It provides a secure channel over an unsecured network by using a client-server architecture, encrypting all traffic between the two parties to prevent many common attacks such as eavesdropping. 2822a31c67c403ed2abab1ba40368b9b970afff5 3000 1336 5719 2026-06-13T04:38:19Z Wreckvall 426 copied the installation guide from the main sway article to the guides namespace wikitext text/x-wiki See the main article on [[Sway]]. === Notes before you install Sway: === * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] === Installation guide: === ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For [[Arch]]: ==== Using pacman: pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For [[Debian]]: ==== Using apt package manager: apt install sway ==== For [[Fedora]]: ==== Using dnf package manager dnf install sway e8aedb37380497122dc3b9f58de9c1ed6bf84eba 0 574 5720 4285 2026-06-13T04:51:13Z Wreckvall 426 added a citation, cleaned up the article (moved the installation process to guides), and added a section on how to use sway wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox |image=[[File:SwayLogo.png|thumb]] |caption=Sway Logo |title=Sway |releasestatus=Maintained |lastrelease=1.11, 2025-06-09 |firstrelease=0.1, 2016-05-24 |languages=[[C]] |developers=Sway Developers |website=[https://swaywm.org/ swaywm.org] }} Sway ('''S'''irCmpwn's '''Way'''land compositor) is a famous tiling [[Wayland]] [[compositor]]. It is meant to be the [[I3]] of Wayland. It takes inspiration from i3 in its design and configuration, and, consequently, it is very backwards-compatible with i3. Owing to its simplistic and productive nature, it is not eye-candy with enthralling visuals and effects. [[SwayFX]] is a fork of Sway that introduces many rendering effects, such as: blur, shadows, anti-aliased rounded corners, borders and titlebars, dimming of unfocused windows and much more. === Notable Features: === According to Sway's official website<ref>{{Cite|url=https://swaywm.org/|title=Sway|accessdate=2026/06/13}}</ref>: * Sway organizes windows in a structured, logical manner rather than letting users manually place them anywhere. * Windows are arranged in such a manner as to maximize the efficiency of your screen and can be easily controlled by using the keyboard only. Windows are arranged in a grid like manner. * Backward compatible with i3 configuration and supports its features, and some extra. * Extensive documentation in the form of man pages. === Use: === See [[Guides:Installing Sway|Installing Sway]] for details on how to install Sway. To configure Sway, copy the example configuration file into your user config folder: mkdir -p ~/.config/sway cp /etc/sway/config ~/.config/sway/ Then, you can start editing the <code>~/.config/sway/config</code> with the editor of your choice. The format is similar to i3 configuration files. If you are migrating from i3 to Sway, you can reuse your old configuration file. To switch to Sway, select Sway in the Display Manager as you are logging in. You can also launch a Sway session from your terminal with the command <code>sway</code>. For ideas on how to customize your config file, refer to Section 3 of the [https://wiki.archlinux.org/title/Sway Arch Wiki's guide on Sway] (it works on other distros too, not just Arch!). 1c57b0750579476b951bee2c54f6bd1bc48e2405 0 1335 5721 5718 2026-06-13T08:27:05Z Lawl 419 add a LOT more ssh stuffs wikitext text/x-wiki {{Stub}} SSH, also known as the '''Secure Shell Protocol''', is a cryptographic network protocol used to operate network services securely over an unsecured network.<ref>[https://www.rfc-editor.org/rfc/rfc4251 RFC 4251 - The Secure Shell (SSH) Protocol Architecture]</ref> It provides a secure channel over an unsecured network by using a client-server architecture, encrypting all traffic between the two parties to prevent many common attacks such as eavesdropping. SSH was introduced in 1995 to serve as a replacement for earlier, insecure remote-access protocols such as [[Telnet]] and the [[Berkeley r-commands]], which transmitted data, including authentication credentials, in unencrypted plaintext. SSH is commonly used for remote command-line login and remote command execution, but can also be used for file transfer and port forwarding. == Usage == SSH is used via a '''client''' application, which connects to an '''SSH server''' running on the remote machine you wish to connect to. The most widely used implementation of SSH is [[OpenSSH]], which is a derivative of the original free SSH 1.2.12 release from Tatu Ylönen<ref>[https://www.openssh.org/history.html OpenSSH project history]</ref>. It was developed to provide a free, open source alternative to the original SSH. It is now used in virtually any system, with the odd exception of embedded systems and routers, which instead use [[Dropbear]], a lighter alternative to [[OpenSSH]] based on the [https://en.wikipedia.org/wiki/Secure_Shell#Version_2 SSH version 2 protocol]. Dropbear was made specifically for embedded systems and other forms of computing where low memory usage is needed. Like OpenSSH, it is also free and open source software. There are many, many more SSH clients such as [[wolfSSH]] or GNU's [[lsh]]. It is recommended you just use OpenSSH or Dropbear, as other SSH clients are often less known, less documented, or have no general advantages or use case above the standard SSH clients. === Connecting to a remote host === The basic syntax for connecting with the SSH client is: - <code>ssh user@host</code> .. where <code>user</code> is the remote account to log in as, and <code>host</code> is the hostname or IP address of the server. To specify a non-default port, such as 2222: - <code>ssh -p 2222 user@host</code> On a successful connection, the user is dropped into a shell on the remote machine. There are many more command line arguments, and extra setup instructions needed to connect to a remote server. If you need help with something not listed here, see the official [https://man.openbsd.org/ssh OpenSSH man page]. === Setup === Setting up an SSH server involves installing and enabling an SSH daemon such as OpenSSH's [[sshd]], and configuring authentication. It is '''strongly recommended''' that you harden the default SSH config before exposing a server to the Internet. See [[Guides:Best SSH Security Practices]] for a full guide, as this wiki entry will not cover that. == History == SSH was designed in 1995 by '''Tatu Ylönen''' after a password-sniffing attack on his university's network. This attack exposed the weaknesses of all of the existing remote access protocols. As a response to this, Ylönen released the first SSH version, now called '''SSH-1''', as freeware in July 1995.<ref>[https://www.ssh.com/academy/ssh/original-ssh-overview Ylönen's original announcement]</ref> Adoption of this new protocol was rapid, within a few months it was estimated there were over 20,000 users across 550 countries. Later, Ylönen founded '''SSH Communications Security''' to continue development of the protocol commercially. Over time, the SSH codebase became more and more restrictive in it's licensing, which led developers behind [[OpenBSD]] to fork the last freely licensed version of SSH (SSH 1.2.12) in 1999, creating [[OpenSSH]], which is now the most common and widely deployed SSH implementation in the world. Later on, SSH-1 was found to have numerous cryptographic weaknesses, leading to the design of a successor to SSH-1, the '''SSH-2''' protocol, developed by the '''IETF SECSH''' working group. SSH-2 was published as a collection of RFCs in 2006, most notably '''RFC 4251'''. SSH-2 is purposefully incompatible with SSH-1 due to it's security problems. '''SSH-1 is now considered obsolete,''' usage of it is strongly discouraged. Because of the general superiority of SSH-2 over SSH-1, numerous implementations have come out for it, such as [[lsh]] and [[Dropbear]]. 1604d14ab24e4537a0e21fcd39ae4bd2e319868a 5722 5721 2026-06-13T08:44:31Z Madonuko 140 tidy up format wikitext text/x-wiki {{Stub}} SSH, also known as the '''Secure Shell Protocol''', is a cryptographic network protocol used to operate network services securely over an unsecured network.<ref>[https://www.rfc-editor.org/rfc/rfc4251 RFC 4251 - The Secure Shell (SSH) Protocol Architecture]</ref> It provides a secure channel over an unsecured network by using a client-server architecture, encrypting all traffic between the two parties to prevent many common attacks such as eavesdropping. SSH was introduced in 1995 to serve as a replacement for earlier, insecure remote-access protocols such as [[Telnet]] and the [[Berkeley r-commands]], which transmitted data, including authentication credentials, in unencrypted plaintext. SSH is commonly used for remote command-line login and remote command execution, but can also be used for file transfer and port forwarding. == Usage == SSH is used via a '''client''' application, which connects to an '''SSH server''' running on the remote machine you wish to connect to. The most widely used implementation of SSH is [[OpenSSH]], which is a derivative of the original free SSH 1.2.12 release from Tatu Ylönen<ref>[https://www.openssh.org/history.html OpenSSH project history]</ref>. It was developed to provide a free, open source alternative to the original SSH. It is now used in virtually any system, with the odd exception of embedded systems and routers, which instead use [[Dropbear]], a lighter alternative to [[OpenSSH]] based on the [[wikipedia:Secure_Shell#Version_2|SSH version 2 protocol]]. Dropbear was made specifically for embedded systems and other forms of computing where low memory usage is needed. Like OpenSSH, it is also free and open source software. There are many, many more SSH clients such as [[wolfSSH]] or GNU's [[lsh]]. It is recommended you just use OpenSSH or Dropbear, as other SSH clients are often less known, less documented, or have no general advantages or use case above the standard SSH clients. === Connecting to a remote host === The basic syntax for connecting with the SSH client is: ssh ''user''@'''host''' where <code>''user''</code> is the remote account to log in as, and <code>'''host'''</code> is the hostname or IP address of the server. To specify a non-default port, such as 2222: ssh -p 2222 ''user''@'''host''' On a successful connection, the user is dropped into a shell on the remote machine. There are many more command line arguments, and extra setup instructions needed to connect to a remote server. If you need help with something not listed here, see the official [https://man.openbsd.org/ssh OpenSSH man page]. === Setup === Setting up an SSH server involves installing and enabling an SSH daemon such as OpenSSH's [[sshd]], and configuring authentication. It is '''strongly recommended''' that you harden the default SSH config before exposing a server to the Internet. See [[Guides:Best SSH Security Practices]] for a full guide, as this wiki entry will not cover that. == History == SSH was designed in 1995 by '''Tatu Ylönen''' after a password-sniffing attack on his university's network. This attack exposed the weaknesses of all of the existing remote access protocols. As a response to this, Ylönen released the first SSH version, now called '''SSH-1''', as freeware in July 1995.<ref>[https://www.ssh.com/academy/ssh/original-ssh-overview Ylönen's original announcement]</ref> Adoption of this new protocol was rapid, within a few months it was estimated there were over 20,000 users across 550 countries. Later, Ylönen founded '''SSH Communications Security''' to continue development of the protocol commercially. Over time, the SSH codebase became more and more restrictive in it's licensing, which led developers behind [[OpenBSD]] to fork the last freely licensed version of SSH (SSH 1.2.12) in 1999, creating [[OpenSSH]], which is now the most common and widely deployed SSH implementation in the world. Later on, SSH-1 was found to have numerous cryptographic weaknesses, leading to the design of a successor to SSH-1, the '''SSH-2''' protocol, developed by the '''IETF SECSH''' working group. SSH-2 was published as a collection of RFCs in 2006, most notably '''RFC 4251'''. SSH-2 is purposefully incompatible with SSH-1 due to it's security problems. '''SSH-1 is now considered obsolete,''' usage of it is strongly discouraged. Because of the general superiority of SSH-2 over SSH-1, numerous implementations have come out for it, such as [[lsh]] and [[Dropbear]]. == References == 88e7bf5a04884ba0051238f1776b9114c9f0fbbc 5754 5722 2026-06-15T08:59:47Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{Stub}} SSH, also known as the '''Secure Shell Protocol''', is a cryptographic network protocol used to operate network services securely over an unsecured network.<ref>[https://www.rfc-editor.org/rfc/rfc4251 RFC 4251 - The Secure Shell (SSH) Protocol Architecture]</ref> It provides a secure channel over an unsecured network by using a client-server architecture, encrypting all traffic between the two parties to prevent many common attacks such as eavesdropping. SSH was introduced in 1995 to serve as a replacement for earlier, insecure remote-access protocols such as [[Telnet]] and the [[Berkeley r-commands]], which transmitted data, including authentication credentials, in unencrypted plaintext. SSH is commonly used for remote command-line login and remote command execution, but can also be used for file transfer and port forwarding. == Usage == SSH is used via a '''client''' application, which connects to an '''SSH server''' running on the remote machine you wish to connect to. The most widely used implementation of SSH is [[OpenSSH]], which is a derivative of the original free SSH 1.2.12 release from Tatu Ylönen<ref>[https://www.openssh.org/history.html OpenSSH project history]</ref>. It was developed to provide a free, open source alternative to the original SSH. It is now used in virtually any system, with the odd exception of embedded systems and routers, which instead use [[Dropbear]], a lighter alternative to [[OpenSSH]] based on the [[wikipedia:Secure_Shell#Version_2|SSH version 2 protocol]]. Dropbear was made specifically for embedded systems and other forms of computing where low memory usage is needed. Like OpenSSH, it is also free and open source software. There are many, many more SSH clients such as [[wolfSSH]] or GNU's [[lsh]]. It is recommended you just use OpenSSH or Dropbear, as other SSH clients are often less known, less documented, or have no general advantages or use case above the standard SSH clients. === Connecting to a remote host === The basic syntax for connecting with the SSH client is: ssh ''user''@'''host''' where <code>''user''</code> is the remote account to log in as, and <code>'''host'''</code> is the hostname or IP address of the server. To specify a non-default port, such as 2222: ssh -p 2222 ''user''@'''host''' On a successful connection, the user is dropped into a shell on the remote machine. There are many more command line arguments, and extra setup instructions needed to connect to a remote server. If you need help with something not listed here, see the official [https://man.openbsd.org/ssh OpenSSH man page]. === Setup === Setting up an SSH server involves installing and enabling an SSH daemon such as OpenSSH's [[sshd]], and configuring authentication. It is '''strongly recommended''' that you harden the default SSH config before exposing a server to the Internet. See [[Guides:Best SSH Security Practices]] for a full guide, as this wiki entry will not cover that. == History == SSH was designed in 1995 by '''Tatu Ylönen''' after a password-sniffing attack on his university's network. This attack exposed the weaknesses of all of the existing remote access protocols. As a response to this, Ylönen released the first SSH version, now called '''SSH-1''', as freeware in July 1995.<ref>[https://www.ssh.com/academy/ssh/original-ssh-overview Ylönen's original announcement]{{Dead Link|2026-06-15|404}}</ref> Adoption of this new protocol was rapid, within a few months it was estimated there were over 20,000 users across 550 countries. Later, Ylönen founded '''SSH Communications Security''' to continue development of the protocol commercially. Over time, the SSH codebase became more and more restrictive in it's licensing, which led developers behind [[OpenBSD]] to fork the last freely licensed version of SSH (SSH 1.2.12) in 1999, creating [[OpenSSH]], which is now the most common and widely deployed SSH implementation in the world. Later on, SSH-1 was found to have numerous cryptographic weaknesses, leading to the design of a successor to SSH-1, the '''SSH-2''' protocol, developed by the '''IETF SECSH''' working group. SSH-2 was published as a collection of RFCs in 2006, most notably '''RFC 4251'''. SSH-2 is purposefully incompatible with SSH-1 due to it's security problems. '''SSH-1 is now considered obsolete,''' usage of it is strongly discouraged. Because of the general superiority of SSH-2 over SSH-1, numerous implementations have come out for it, such as [[lsh]] and [[Dropbear]]. == References == a2dbde4709230e0f198e5553042b9edd97cef4a2 6 1337 5723 2026-06-13T09:47:11Z Lawl 419 wikitext text/x-wiki An orange flag, with the word "NetBSD" de8fe750aa8489af4eb58ff7f7432d5c40b4d0fd 0 1338 5724 2026-06-13T15:49:44Z Lawl 419 made pretty much all of netbsd page, sum edits may be needed but probably not much wikitext text/x-wiki [[Category:Misc Operating Systems]] [[Category:BSD]] {{DistributionInfobox | architectures = amd64, evbarm, evbmips, evbppc, hpmarm, i386, sparc64, xen | caption = The NetBSD logo | defaultdesktops = [[CTWM]] | image = [[File:NetBSD Icon.png|200px|The NetBSD icon]] | packagemanager = [[pkgsrc]] | releasemodel = Stable | releasestatus = Maintained | title = NetBSD | usagetype = Servers, desktops, handheld devices, embedded computing | website = https://netbsd.org/ }} '''NetBSD''' is a free and open source Unix-like operating system based on the [[Berkeley Software Distribution]] <ref>[https://en.wikipedia.org/wiki/NetBSD Wikipedia entry for NetBSD] </ref>. It was the first ever open source BSD descendant officially released after [[386BSD]] was forked. NetBSD still continues to be actively developed and is built for an incredibly large amount of platforms. The NetBSD project itself focuses on numerous factors, such as code clarity, careful design and portability across many architectures, which is evident through it supporting '''over 59''' hardware platforms. Each architecture usable on NetBSD is broken down into "ports", and then organized into tiers based on the current importance of the port and level of community activity. NetBSD is built on a highly unique package system called [[pkgsrc]], which is an OS-agnostic package system. This means that it not only runs on NetBSD, but runs on numerous other operating systems such as many Linux distributions. 0ac2f70f720e2dfaa40f51511ae35ca8f18fdcc7 0 1339 5725 2026-06-13T16:27:33Z Lawl 419 make most of uclibc page, may need adding to wikitext text/x-wiki '''uClibc''' (pronounced yew-see-lib-see), is a small standard C library intended for Linux kernel-based operating systems (a.k.a distributions) that require low resource usage, such as embedded devices and routers. It is much smaller than other options such as the GNU standard C library ([[glibc]]). uClibc's development started around 1999 by Erik Anderson. Although being mostly developed from complete scratch, uClibc does incorporate code from other software such as [[glibc]]. uClibc is fully free and open source, and is licensed under the [[GNU Lesser General Public License]]. While other libc alternatives may be made to support as many features as possible, uClibc focuses on the bare minimum, with most of the features you can enable or disable at your will. This allows it to be suitable for embedded computing and low-memory environments. After a long lack of communication from the uClibc project maintainer, [[uClibc-ng]] was built. It is an actively maintained fork of the original uClibc after the original project went over 2 years without a single update. uClibc seems to have no updates anymore, but the original project author often refers to [[uClibc-ng]] for current releases. uClibc, aswell as it's maintained fork [[uClibc-ng]], have been effectively replaced by newer and smaller C standard libraries, such as [[musl]] and [[dietlibc]]. uClibc still stands as a lighter alternative to [[glibc]], but usage of the original project is not recommended, and instead it is recommended to use [[uClibc-ng]]. If you want a full list of comparisons of each libc, see https://www.etalabs.net/compare_libcs.html. 6451200ffabe0ac4561c44cab4843952ad6a46f2 0 1092 5726 5279 2026-06-13T16:32:51Z Lawl 419 add security notice, correct some stuff wikitext text/x-wiki {{DistributionInfobox | title = Tinfoil Hat Linux | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | releasestatus = Discontinued | releasemodel = None | packagemanager = None | defaultdesktops = Terminal only | usagetype = Security | architectures = i386 | website = tinfoilhat.shmoo.com }} '''Tinfoil Hat Linux''' ('''THL''') is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defend itself from surveillance including TEMPEST and keyloggers. Most of the security features in TFHL are now obsolete, as they are unmaintained and may hold numerous vulnerabilities. == List of Tinfoil Hat Linux methods against surveillance== * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanism were intended to enhance operational security limiting data persistence and mitigating common surveillance techniques. 5a7f7fdc92fadcef26d93c483cd4c31d16168c6e 0 396 5727 5509 2026-06-13T16:39:12Z Lawl 419 add irc to messaging wikitext text/x-wiki Software includes command line applications, Linux core utilities (terminal commands), and applications with graphical user interfaces (GUI), background processes (daemons), etc. that run on a computer operating system. This page is dedicated to listing common and widely recommended free and open source software used on [[Linux]] distributions. To install software on Linux, use your distribution's software manager or [[Package Manager|package manager]]. = System = Programs for managing your hardware, operating system, and installed software. == App Stores and Software Managers == Install, remove, and update apps! {| class="wikitable" !Name !External links !Description !DE |- |[[Discover]] |[https://apps.kde.org/discover/ KDE Applications], [https://invent.kde.org/plasma/discover GitLab] |The software center for KDE Plasma; distributes [[Flatpak]]s. |[[Plasma|KDE Plasma]] |} == Package Managers == '''See the main page: [[Package Managers]]''' Package managers are command line programs for your distribution that handle installing, removing, and updating software. These are the most common package managers: {| class="wikitable" !Name !External links !Description !Distribution |- |[[pacman]] |[https://pacman.archlinux.page/ Website], [https://gitlab.archlinux.org/pacman/pacman GitLab] |The package manager for Arch-based operating systems. |[[Arch Linux]], [[EndeavourOS]], etc. |- |[[apt]] |[https://www.debian.org/doc/manuals/apt-guide/index.en.html Website], [https://salsa.debian.org/apt-team/apt GitLab] |The package manager for Debian-based operating systems. |[[Debian]], [[Ubuntu]], etc. |- |[[dnf]] |[https://docs.fedoraproject.org/en-US/quick-docs/dnf/ Website], [https://github.com/rpm-software-management/dnf GitHub] |The package manager for Fedora and RHEL-based operating systems. |[[Fedora]] |} == File Managers == '''See the main page: [[File Managers]]''' File managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. These are the most common file managers: {| class="wikitable" !Name !External links !Description !DE |- |Dolphin |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |[[Plasma|KDE Plasma]] |- |Thunar |[https://docs.xfce.org/xfce/thunar/start Xfce] |Thunar is [[Xfce]]'s modern file manager, desgined from the group up for speed and friendliness. |[[Xfce]] |- |} == System Resource Monitors (task managers) == '''See the main page: [[System Resource Monitors]]''' GUI and terminal programs for monitoring hardware utilization and listing all currently-running applications, services, and processes. == System Information Viewers == '''See the main page: [[System Information Viewers]]''' These include GUI and fetch scripts. == Hardware Maintenance == '''See the main page: [[Hardware Maintenance]]''' These are GUI and TUI programs that check the current health and utilization of hardware components such as your SSD/HDDs and battery. = Productivity = Get common office work done. == Office Suites == <!-- TODO: comparison of FOSS office suites article - deviaze --> {| class="wikitable" !Name !External links !Description |- |[[LibreOffice]] |[https://www.libreoffice.org/ Website], [https://github.com/LibreOffice GitHub] |Free and open source office suite. Somewhat outdated GUI but best option on Linux. |} = Social and Messaging = <!-- TODO: decide how we can organize this category --> {| class="wikitable" !Name !External links !Description |- |[[Fluxer]] |[https://fluxer.app/ Website], [https://github.com/FluxerApp GitHub] |Instant messaging and VoIP platform built for friends, groups, and communities. |- |[[Cinny]] |[https://cinny.in/ Website], [https://github.com/cinnyapp/cinny GitHub] |Matrix client focused on providing a simple, elegant and secure interface. |- |[[Matrix]] |[https://matrix.org/ Website], [https://github.com/matrix-org GitHub] |Matrix is an open source decentralised protocol with independant clients. |- |[[XMPP]] |[https://xmpp.org Website] |An extensible federated messaging protocol. |- |[[IRC]] |None |A text-based chat system for instant messaging, designed for group communication. |} = Media = '''See the main page: [[Media]]''' == Image == Includes software primarily meant for drawing, photo & image editing and vector image editing '''See the main page [[Image Editing]]''' == 3D == Includes software primarily for 3d modeling, texturing, and animation '''See the main page [[3D Editing]]''' == Video == '''See the main page [[Video Editing]]''' For video players, see [[Video Players]] == Music and Audio == '''See the main page: [[Music and Audio]]''' For music players, see [[Music Players]] = Text Editing and Software Development = '''See the main page: [[Text Editors]]''' This includes text editors for editing config files, writing software, and integrated development environments (IDEs). = Gaming = '''See the main page: [[Gaming]]''' = Security and Privacy = '''See the main article: [[Security and Privacy]]''' This includes password managers, VPN software, encryption and decryption software, and similar. = Accessibility = This includes screen readers, colorblind accessibility software, and similar. = Miscellaneous = Software that does not fit in any other category. 8e507309b192b0aa27a9af535b78127e7e689ae5 0 169 5728 5181 2026-06-13T18:02:06Z Lawl 419 add eweos na dchimera to "used by" category with their respective packagte managers wikitext text/x-wiki [[Category:Terminology]] [[File:Apt-get install mediawiki.png|thumb|Installing MediaWiki with apt-get]] A package manager is a utility designed to handle [[package]]s, [[software]] delivered in specific formats. Regular functions include [[install]]ing, removing, updating, and searching packages, usually from a package [[repository]]. === List of Package Managers === Note: The ''Used By'' field also implies [[derivative]]s, which are listed in the [[Linux Distributions]] page. There are exceptions to this rule, specifically cross-distribution package managers such as [[snap]], [[nix]] and [[flatpak]]. For a list of package formats, see the [[package]] page. {| class="wikitable" ! Package Manager !! Written In !! Used By !! Maintained By |- ! colspan="4" |'''Distribution-specific package managers''' |- | [[apk]] || [[C]]<ref name="alpine git">[https://gitlab.alpinelinux.org/alpine/apk-tools alpine / apk-tools · GitLab], Alpine Linux community (Accessed: 2025-10-18)</ref> || [[Alpine Linux]]<ref>[https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html Working with the Alpine Package Keeper (apk)], Alpine Linux Documentation, 2025-08-25 (Accessed: 2025-10-18)</ref>, [[Chimera Linux]] || Alpine Linux Community<ref name="alpine git" /> |- | [[apt]] || [[C++]]<ref name="deb-apt">[https://salsa.debian.org/apt-team/apt apt], APT Developers, 2017-12-25 (Accessed: 2025-10-18)</ref> || [[Debian]]<ref>[https://wiki.debian.org/Apt Apt], Debian Wiki, 2025-08-23 (Accessed: 2025-10-18)</ref> & [[Ubuntu]]<ref>[https://en.wikipedia.org/wiki/Ubuntu Ubuntu], Wikipedia contributors, 2004-09-16 (Accessed: 2025-10-18)</ref> || Debian Community<ref name="deb-apt"/> |- | [[cpt]] || [[Shell]]<ref name="carbs git">[https://github.com/CarbsLinux/cpt GitHub - CarbsLinux/cpt], Carbs Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Carbs Linux]]<ref>[https://carbslinux.org Home | Carbs Linux], Carbs Linux Dev Team, 2024-03-06 (Accessed: 2025-10-18)</ref> || Carbs Linux Dev Team<ref name="carbs git" /> |- | [[dnf]] || DNF5 [[C++]]<ref>[https://github.com/rpm-software-management/dnf5 GitHub - rpm-software-management/dnf5], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref> | DNF4 & Older [[Python]]<ref>[https://github.com/rpm-software-management/dnf GitHub - rpm-software-management/dnf], DNF team, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Fedora]]<ref>[https://docs.fedoraproject.org/en-US/quick-docs/package-management/ Package management system], Fedora Docs, 2025-10-18 (Accessed: 2025-10-18)</ref>, [[RHEL| Red Hat Enterprise Linux]]<ref>[https://www.redhat.com/en/blog/how-manage-packages Linux package management with YUM and RPM], Red Hat, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr">[https://wiki.openmandriva.org/en/distribution/guides/software-management Software management], OpenMandriva wiki, 2025-07-18 (Accessed: 2025-10-18)</ref> || [[Red Hat]]<ref>[https://en.wikipedia.org/wiki/DNF_(software) DNF (software)], Wikipedia contributors, 2015-01-23 (Accessed: 2025-10-18)</ref> |- | [[eopkg]] || [[Python]]<ref name="solus git">[https://github.com/getsolus/eopkg GitHub - getsolus/eopkg], Solus community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Solus]]<ref>[https://help.getsol.us/docs/user/package-management/basics/ Basics to Package Management], Solus Help Center, 2025-10-08 (Accessed: 2025-10-18)</ref> || Solus Community<ref name="solus git" /> |- | [[pacman]] || [[C]]<ref name="arch-pacman">[https://gitlab.archlinux.org/pacman/pacman Pacman], Arch Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Arch Linux]]<ref>[https://wiki.archlinux.org/title/Pacman pacman], ArchWiki, 2025-09-28 (Accessed: 2025-10-18)</ref>, [[eweOS]] || Arch Linux Community<ref name="arch-pacman" /> |- | [[paldius]] || [[C++]]<ref name="exherbo git">[https://gitlab.exherbo.org/paludis/paludis Paludis / paludis · GitLab], Exherbo community (Accessed: 2025-10-18)</ref> || [[Exherbo]]<ref name="exherbo git" /> || Exherbo Community<ref name="exherbo git" /> |- | [[pkg]] || [[C]]<ref name="freebsd git">[https://github.com/freebsd/pkg GitHub - freebsd/pkg], FreeBSD community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[FreeBSD]]<ref>[https://en.wikipedia.org/wiki/FreeBSD FreeBSD], Wikipedia contributors, 2001-07-27 (Accessed: 2025-10-18)</ref> || FreeBSD Community<ref name="freebsd git" /> |- | [[pkgutils]] || [[C++]]<ref name="crux git">[https://git.crux.nu/tools/pkgutils tools/pkgutils], CRUX Dev Team, 2000-10-18 (Accessed: 2025-10-18)</ref> || [[CRUX]]<ref>[https://crux.nu/Wiki/FaqPkgUtils pkgutils], CRUX Wiki (Accessed: 2025-10-18)</ref> || CRUX Dev Team<ref name="crux git" /> |- | [[pmm]] || [[Shell]]|| [[Bedrock Linux]]<ref>[https://bedrocklinux.org/0.7/pmm-beta.html Bedrock Linux 0.7 Package Manager Manager Beta], Bedrock Linux Dev Team, 2025-09-29 (Accessed: 2025-10-18)</ref> || Bedrock Linux Dev Team<ref>[https://github.com/bedrocklinux/bedrocklinux-userland/tree/master/src/slash-bedrock/share/pmm bedrocklinux-userland/src/slash-bedrock/share/pmm at master · bedrocklinux/bedrocklinux-userland · GitHub], Bedrock Linux Dev Team, 2025-10-18 (Accessed: 2025-10-18)</ref> |- | [[portage]] || [[Python]]<ref name="gentoo git">[https://github.com/gentoo/portage GitHub - gentoo/portage], Gentoo community, 2025-10-18 (Accessed: 2025-10-18)</ref>|| [[Gentoo]]<ref>[https://wiki.gentoo.org/wiki/Portage Portage], Gentoo wiki, 2025-10-18 (Accessed: 2025-10-18)</ref> || Gentoo Community<ref name="gentoo git" /> |- | [[scratch]] || [[Shell]]<ref name="venom git">[https://codeberg.org/venomlinux/scratchpkg venomlinux/scratchpkg], Venom Linux Dev Team (Accessed: 2025-10-18)</ref> || [[Venom Linux]]<ref>https://venomlinux.org/wiki#package-manager.scratch{{Dead Link|2025-10-18|404}}</ref> || Venom Linux Dev Team<ref name="venom git" /> |- | [[XBPS|xbps]] || [[C]]<ref name="void git">[https://github.com/void-linux/xbps GitHub - void-linux/xbps], Void Linux Community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Void Linux]]<ref>[https://docs.voidlinux.org/xbps/index.html XBPS Package Manager], Void Linux Handbook, 2025-10-18 (Accessed: 2025-10-18)</ref> || Void Linux Community<ref name="void git" /> |- | [[zypper]] || [[C++]]<ref name="opensuse contrib">[https://github.com/openSUSE/zypper GitHub - openSUSE/zypper], SUSE LINUX Products GmbH, 2011-10-18 (Accessed: 2025-10-18)</ref> || [[openSUSE]]<ref>[https://doc.opensuse.org/documentation/tumbleweed/zypper/ Zypper], openSUSE User Documentation Project, 2024-02-28 (Accessed: 2025-10-18)</ref>, [[SUSE Linux Enterprise]]<ref>[https://documentation.suse.com/smart/systems-management/html/concept-zypper/index.html Zypper package manager], SUSE Software Solutions Germany GmbH, 2025-10-18 (Accessed: 2025-10-18)</ref> & [[OpenMandriva]]<ref name="om pkg mgr" />|| openSUSE Community<ref name="opensuse contrib" /> |- ! colspan="4" |'''Cross-distribution package managers''' |- | [[Homebrew|brew]] || [[Ruby]]<ref name="brew git">[https://github.com/Homebrew/brew GitHub - Homebrew/brew], Homebrew community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[macOS]]<ref name="brew site">[https://brew.sh Homebrew], Homebrew community, 2025-10-17 (Accessed: 2025-10-18)</ref> & [[Linux]]<ref name="brew site" /> || Homebrew Community<ref name="brew git" /> |- | [[flatpak]] || [[C]]<ref name="flatpak git">[https://github.com/flatpak/flatpak GitHub - flatpak/flatpak], Flatpak contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref name="flatpak install">[https://flatpak.org/setup/ Flatpak—the future of application distribution], Flatpak contributors, 2025-07-21 (Accessed: 2025-10-18)</ref> & [[ChromeOS]]<ref name="flatpak install" /> || Flatpak Contributors<ref name="flatpak git /> |- | [[guix]] || [[Scheme]]<ref name="guix git">[https://codeberg.org/guix/guix guix/guix], GUIX Dev Team, 2019-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://guix.gnu.org/en/ GNU Guix transactional package manager and distribution], GUIX Dev Team, 2020-10-18 (Accessed: 2025-10-18)</ref> || GUIX Dev Team<ref name="guix git" /> |- | [[nix]] || [[C++]]<ref name="nix-git">[https://github.com/NixOS/nix GitHub - NixOS/nix], NixOS community, 2025-10-18 (Accessed: 2025-10-18)</ref> || [[NixOS]]<ref>[https://nixos.org/guides/how-nix-works/ How Nix Works], NixOS contributors, 2025-10-18 (Accessed: 2025-10-18)</ref> || NixOS Community<ref name="nix-git" /> |- |[[pkgsrc]] |[[C]], [https://www.crufty.net/help/sjg/bmake.html BSD Makefiles] |[[NetBSD]], SmartOS/[[illumos]], [[macOS]]/[[Darwin]], [[Linux]], [[Oracle Solaris|Solaris]], MINIX 3<ref name=":0">{{Cite|url=https://pkgsrc.org/|title=pkgsrc|author=The NetBSD Foundation|year=2025|accessdate=2026-05-22}}</ref> |The NetBSD Foundation<ref name=":0" /> |- | [[snap]] || [[Go]]<ref name="snap git">[https://github.com/canonical/snapd GitHub - canonical/snapd], Canonical Ltd., 2025-10-18 (Accessed: 2025-10-18)</ref> || [[Linux]]<ref>[https://en.wikipedia.org/wiki/Snap_(software) Snap (software)], Wikipedia contributors, 2015-11-07 (Accessed: 2025-10-18)</ref> || [[Canonical]]<ref name="snap git" /> |} == References == <references /> ed2253a80e15b84e86d1c226ef864394592f5227 6 1340 5729 2026-06-13T18:13:20Z Lawl 419 A cartoonish white ram with yellow horns and a pinkish-red bowtie. wikitext text/x-wiki == Summary == A cartoonish white ram with yellow horns and a pinkish-red bowtie. d448dcb94ebdfeaa77588f8a08a00aaf7c8bc09e 0 1341 5730 2026-06-13T18:20:22Z Lawl 419 make eweos page wikitext text/x-wiki {{DistributionInfobox | architectures = x86_64, aarch64, riscv64, loongarch64 | caption = The eweOS logo | defaultdesktops = Any | image = [[File:EweOS_logo.png|200px|alt=A cartoonish white ram with yellow horns and a reddish-pink bowtie on one of the horns.|The eweOS logo]] | packagemanager = [[pacman]] | releasemodel = Rolling | releasestatus = Maintained | title = eweOS | usagetype = Desktop, Server | website = [https://ewe.moe ewe.moe] }} eweOS is an musl-based, lightweight, general-purpose Linux distribution, which adopts the [[musl]] libc and [[busybox]] to the latest versions of software with a rolling-release model.<ref>[https://os.ewe.moe/about eweOS' official about page]</ref> It uses [[pacman]] for package management, [[Limine]] as it's bootloader and [[dinit]] as the init system. eweOS swaps out many larger system components with much smaller, leaner alternatives. eweOS also has a very simple installation procedure, which is similar to that of [[Arch Linux]]. Currently, however, installing eweOS on real hardware is not recommended, due to eweOS being in '''very''' early stages of it's development. Due to both using very similar low-level system components, eweOS and [[Chimera Linux]] share many, many similarities, including the standard C library, init system, and more, despite them having different focuses, with eweOS focusing on being lightweight, with Chimera focusing on being modern. This means they do have some differences which leads to eweOS being more lightweight, such as eweOS using [[busybox]], and Chimera not. c5ae1159761cc7ceab3d31481cde2e995fc5c7bd 5751 5730 2026-06-14T20:41:47Z Strangely Human Feeling 415 fixed slightly inaccurate url for the website wikitext text/x-wiki {{DistributionInfobox | architectures = x86_64, aarch64, riscv64, loongarch64 | caption = The eweOS logo | defaultdesktops = Any | image = [[File:EweOS_logo.png|200px|alt=A cartoonish white ram with yellow horns and a reddish-pink bowtie on one of the horns.|The eweOS logo]] | packagemanager = [[pacman]] | releasemodel = Rolling | releasestatus = Maintained | title = eweOS | usagetype = Desktop, Server | website = [https://os.ewe.moe os.ewe.moe] }} eweOS is an musl-based, lightweight, general-purpose Linux distribution, which adopts the [[musl]] libc and [[busybox]] to the latest versions of software with a rolling-release model.<ref>[https://os.ewe.moe/about eweOS' official about page]</ref> It uses [[pacman]] for package management, [[Limine]] as it's bootloader and [[dinit]] as the init system. eweOS swaps out many larger system components with much smaller, leaner alternatives. eweOS also has a very simple installation procedure, which is similar to that of [[Arch Linux]]. Currently, however, installing eweOS on real hardware is not recommended, due to eweOS being in '''very''' early stages of it's development. Due to both using very similar low-level system components, eweOS and [[Chimera Linux]] share many, many similarities, including the standard C library, init system, and more, despite them having different focuses, with eweOS focusing on being lightweight, with Chimera focusing on being modern. This means they do have some differences which leads to eweOS being more lightweight, such as eweOS using [[busybox]], and Chimera not. 1b3599808f50a99ce1a49ef9899328f549c2f985 5752 5751 2026-06-15T08:49:27Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DistributionInfobox | architectures = x86_64, aarch64, riscv64, loongarch64 | caption = The eweOS logo | defaultdesktops = Any | image = [[File:EweOS_logo.png|200px|alt=A cartoonish white ram with yellow horns and a reddish-pink bowtie on one of the horns.|The eweOS logo]] | packagemanager = [[pacman]] | releasemodel = Rolling | releasestatus = Maintained | title = eweOS | usagetype = Desktop, Server | website = [https://os.ewe.moe os.ewe.moe] }} eweOS is an musl-based, lightweight, general-purpose Linux distribution, which adopts the [[musl]] libc and [[busybox]] to the latest versions of software with a rolling-release model.<ref>[https://os.ewe.moe/about eweOS' official about page]</ref> It uses [[pacman]] for package management, [[Limine]] as it's bootloader and [[dinit]] as the init system. eweOS swaps out many larger system components with much smaller, leaner alternatives. eweOS also has a very simple installation procedure, which is similar to that of [[Arch Linux]]. Currently, however, installing eweOS on real hardware is not recommended, due to eweOS being in '''very''' early stages of it's development. Due to both using very similar low-level system components, eweOS and [[Chimera Linux]] share many, many similarities, including the standard C library, init system, and more, despite them having different focuses, with eweOS focusing on being lightweight, with Chimera focusing on being modern. This means they do have some differences which leads to eweOS being more lightweight, such as eweOS using [[busybox]], and Chimera not. 7322d392c6ea1c427e6a3b6f795c02453d8caa17 0 998 5731 4055 2026-06-13T18:27:01Z Lawl 419 change distros with dinit a bit and add somewhat reasonable artix dinit ref wikitext text/x-wiki {{Stub}} Dinit is a cross-platform service manager / supervision system.<ref>{{Cite|url=https://davmac.org/projects/dinit/|title=Dinit's official website.|accessdate=2025-09-01}}</ref> It was created by Davin McCall to fit in the middle ground between simple supervision suites and service managers. Dinit can be used as either a service manager or, on Linux, as a system manager / init system. == Distributions with Dinit == * [[Chimera Linux]] (as default)<ref>{{Cite|url=https://chimera-linux.org/about/|title=Chimera Linux - About|accessdate=2025-09-01}}</ref> * [[eweOS]] (as default)<ref>{{Cite|url=https://os.ewe.moe/about|title=EweOS {{!}} About|accessdate=2025-09-01}}</ref> * [[Artix Linux]] <ref>[https://wiki.artixlinux.org/Main/Dinit The Dinit Artix Linux wiki entry] </ref>(as an official alternative) <!-- seems to be a pretty good source but if anyone can find a better one pls change!! --> 95675ee85d0211776aa009109678a99a536e97bb 5734 5731 2026-06-13T18:41:05Z Lawl 419 add softwareinfobox wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |caption=The Dinit logo |developers=Dinit developers |firstrelease=v0.01 |languages=[[C++]], [[C]], [[Zig]], [[Go]] |lastrelease=V0.22.0 |title=dinit |website=https://github.com/davmac314/dinit |releasestatus=Maintained |image=[[File:Dinit_logo.png|200px]] }} Dinit is a cross-platform service manager / supervision system.<ref>{{Cite|url=https://davmac.org/projects/dinit/|title=Dinit's official website.|accessdate=2025-09-01}}</ref> It was created by Davin McCall to fit in the middle ground between simple supervision suites and service managers. Dinit can be used as either a service manager or, on Linux, as a system manager / init system. == Distributions with Dinit == * [[Chimera Linux]] (as default)<ref>{{Cite|url=https://chimera-linux.org/about/|title=Chimera Linux - About|accessdate=2025-09-01}}</ref> * [[eweOS]] (as default)<ref>{{Cite|url=https://os.ewe.moe/about|title=EweOS {{!}} About|accessdate=2025-09-01}}</ref> * [[Artix Linux]] <ref>[https://wiki.artixlinux.org/Main/Dinit The Dinit Artix Linux wiki entry] </ref>(as an official alternative) <!-- seems to be a pretty good source but if anyone can find a better one pls change!! --> 44fc74baf11223b34c53cfee3b03faee5c5e6830 0 1091 5732 5567 2026-06-13T18:35:07Z Atmois 13 Move GuideWarning down wikitext text/x-wiki {{Work In Progress}} {{Needs Citations}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.13.1, 2026-05-18 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io] | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation == {{Guide Warning}} ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref>. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> e64c2b9f7c5a3cd8066396a665d07bd2ac7ab4be 5753 5732 2026-06-15T08:59:23Z Hamachitan 222 🍣 Dead external links wikitext text/x-wiki {{Work In Progress}} {{Needs Citations}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.13.1, 2026-05-18 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io]{{Dead Link|2026-06-15|404}} | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation == {{Guide Warning}} ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref>. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 638aa0e342b5fc5adc6df1104d851bd05eda3606 6 1342 5733 2026-06-13T18:36:23Z Lawl 419 A black rectangle with the word "dinit" next to it. wikitext text/x-wiki == Summary == A black rectangle with the word "dinit" next to it. f2f020f8719bfa11ccdfa769d795884f4e075c67 0 1343 5735 2026-06-13T23:58:52Z Uniolo 345 Redirect to Arch Linux (but with proper capitalization) wikitext text/x-wiki #redirect [[Arch Linux]] 5943b130b6f76b1afd02c3441edb84103b80bb6f 0 1344 5736 2026-06-14T00:01:05Z Uniolo 345 Redirect to Arch User Repository (proper capitalization) wikitext text/x-wiki #redirect [[Arch User Repository]] c91f3712acbd1e470f36ddd8564cf58fea67f9c2 0 8 5737 5717 2026-06-14T01:56:21Z Wreckvall 426 /* The Command Line */ added some more bash commands wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}}{{Cleanup|i think it would be a good idea to move all of the bash commands listed to the separate page on bash.}} New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. === Unix Philosophy: Key Concepts === It is important to note that Linux by itself is not an operating system, it is a [[kernel]]. The actual operating system is [[GNU]], which uses the Linux kernel. When people say the 'Linux operating system,' they mean the GNU/Linux operating system. Also note that not all 'Linux' systems use GNU (take Android, for example). GNU also values user freedom, and have based their [[licence]] on four principles. To cite their website:<blockquote>(0) to run the program, (1) to study and change the program in source code form, (2) to redistribute exact copies, and (3) to distribute modified versions.<ref>{{Cite|url=https://www.gnu.org/philosophy/philosophy.html|title=GNU Operating System|accessdate=2026/06/12|year=2025/05/17}}</ref></blockquote>The design of the Linux kernel is also based on some core tenets, including: # '''Do One Thing and Do It Well:''' Instead of having large monolithic programs that try to do everything, Linux tends to have smaller simple tools can be combined or chained together, allowing for complex results with high customisability and user control. # '''Treat Everything as a File:''' Everything is a file, including all the commands you use, external devices, processes, etc... This allows for easy, consistent access. # '''Text-Based Configurations:''' Maybe configuration files and system settings are stored in a easy-to-read and easy-to-edit plaintext form. # '''Open Source:''' See the article about [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] Linux avoids [[bloat]] and values [[privacy]]. Other terms: * [[RTFM]] * [[Security]] === Get Started with Linux === You might have to configure these when you first install Linux: [[Drivers]] Some helpful terms: * [[Linux kernel]] * [[Linux Distributions|Linux Distribution]] ([[Derivative]]) * [[Kernel]] and [[Kernel Module]] (advanced) === The Command Line === See these articles to learn about interacting with the terminal: * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * (a more advanced concept) [[TTY]] Many Linux distributions use [[bash]]. Learn some common bash commands, including: * '''Text Editing:''' ** [[nano]] ** [[micro]] ** [[vim]] * '''Installing [[Package|Packages]] (see more in the Packages section on this article):''' ** [[APT|apt]] ** [[DNF|dnf]] ** [[pacman]] * '''Managing directories and files:''' ** touch: create a file ** mkdir: create a directory ** mv: move a file or directory (this is how you rename files BTW) ** rm: delete a file or directory ** cp: copy a file or directory * '''Compression:''' ** [[Tar.xz|tar.xz / Tarball]] Other important concepts to learn to use the command line include: * [[Ownership]] * [[Processes|Processes and Jobs]] There are also different kinds of [[Shell|shells]] you can use, though this is a more advanced concept. * [[Bash]] * [[Zsh]] === User Interfaces === Two main types of user interfaces: [[GUI|Graphical User Interface (GUI)]] and [[TUI|Text-Based User Interface (TUI)]]. Some common [[Desktop Environment‏‎|Desktop Environment‏‎s]] include: * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] Before you login: [[Display Manager]] After you login: [[Window Manager|Window Managers]] * [[DWM]] * [[Hyprland]] * [[IceWM]] * [[i3]] A more advanced concept is the [[Compositor]]. There are two main architectures for compositors: * [[Wayland]] * [[X11]] (protocol) ** [[X.Org]] (application) [[Xwayland]] exists to bridge these two architectures. Have fun with [[Ricing|Theming / "Ricing"]]! === Packages === [[Repository|Repository (Repo)]] [[Package]] [[Package Manager|Package Managers]] * [[APK|apk]] * [[APT|apt]] * [[DNF|dnf]] * [[DPKG|dpkg]] * [[flatpak]] * [[NixOS|nix]] * [[pacman]] * [[portage]] * [[RPM|rpm]] * [[snap]] * [[zypper]] === General Programming === [[Script]] [[Program]] Learn some [[:Category:Programming Languages|programming languages]]. Beginner friendly ones include: * [[Python]] * [[Javascript]] These are "high-level" languages that [[abstract]] away the inner workings of the computer. Low level languages include: * [[Assembly]] Other more advanced terms include: * [[Building / Compiling]] * [[Git]] and [[GitHub]] are useful for saving your coding projects === General Programming === [[Hacking]] and [[Cybersecurity]] terms: * Early internet: [[ARPANET]] * Attacks: ** [[DDoS]] ** [[Ransomware]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * Defence: ** [[Penetration testing|Penetration Testing]] __INDEX__ __NEWSECTIONLINK__ 302ad470f0635b6636cee939aedd32a31a97228d 5739 5737 2026-06-14T08:25:49Z Wreckvall 426 cleaned up wikitext text/x-wiki [[Category:Terminology]] {{Work In Progress}}New users engaging with the [[Linux]] and the open-source ecosystem for the first time will likely encounter a significant amount of new terminology. This is a list of subjects that new users may wish to become familiar with upon delving into more advanced Linux usage. === Unix Philosophy: Key Concepts === It is important to note that Linux by itself is not an operating system, it is a [[kernel]]. The actual operating system is [[GNU]], which uses the Linux kernel. When people say the 'Linux operating system,' they mean the GNU/Linux operating system. Also note that not all 'Linux' systems use GNU (take Android, for example). GNU also values user freedom, and have based their [[licence]] on four principles. To cite their website:<blockquote>(0) to run the program, (1) to study and change the program in source code form, (2) to redistribute exact copies, and (3) to distribute modified versions.<ref>{{Cite|url=https://www.gnu.org/philosophy/philosophy.html|title=GNU Operating System|accessdate=2026/06/12|year=2025/05/17}}</ref></blockquote>The design of the Linux kernel is also based on some core tenets, including: # '''Do One Thing and Do It Well:''' Instead of having large monolithic programs that try to do everything, Linux tends to have smaller simple tools can be combined or chained together, allowing for complex results with high customisability and user control. # '''Treat Everything as a File:''' Everything is a file, including all the commands you use, external devices, processes, etc... This allows for easy, consistent access. # '''Text-Based Configurations:''' Maybe configuration files and system settings are stored in a easy-to-read and easy-to-edit plaintext form. # '''Open Source:''' See the article about [[FLOSS|Free Open Source Software / Free, Libre Open Source Software (FOSS/FLOSS)]] Linux avoids [[bloat]] and values [[privacy]]. Other terms: * [[RTFM]] * [[Security]] === Get Started with Linux === You might have to configure these when you first install Linux: [[Drivers]] Some helpful terms: * [[Linux kernel]] * [[Linux Distributions|Linux Distribution]] ([[Derivative]]) * [[Kernel]] and [[Kernel Module]] (advanced) === The Command Line === See these articles to learn about interacting with the terminal: * [[CLI|Command-Line Interface (CLI)]] * [[Command]] * (a more advanced concept) [[TTY]] Many Linux distributions use [[bash]]. Other important concepts to learn to use the command line include: * [[Ownership]] * [[Permissions]] * [[Processes|Processes and Jobs]] There are also different kinds of [[Shell|shells]] you can use, though this is a more advanced concept. * [[Bash]] * [[Zsh]] === User Interfaces === Two main types of user interfaces: [[GUI|Graphical User Interface (GUI)]] and [[TUI|Text-Based User Interface (TUI)]]. Some common [[Desktop Environment‏‎|Desktop Environment‏‎s]] include: * [[GNOME]] * [[KDE Plasma]] * [[Xfce]] Before you login: [[Display Manager]] After you login: [[Window Manager|Window Managers]] * [[DWM]] * [[Hyprland]] * [[IceWM]] * [[i3]] A more advanced concept is the [[Compositor]]. There are two main architectures for compositors: * [[Wayland]] * [[X11]] (protocol) ** [[X.Org]] (application) [[Xwayland]] exists to bridge these two architectures. Have fun with [[Ricing|Theming / "Ricing"]]! === Packages === [[Repository|Repository (Repo)]] [[Package]] [[Package Manager|Package Managers]] * [[APK|apk]] * [[APT|apt]] * [[DNF|dnf]] * [[DPKG|dpkg]] * [[flatpak]] * [[NixOS|nix]] * [[pacman]] * [[portage]] * [[RPM|rpm]] * [[snap]] * [[zypper]] === General Programming === [[Script]] [[Program]] Learn some [[:Category:Programming Languages|programming languages]]. Beginner friendly ones include: * [[Python]] * [[Javascript]] These are "high-level" languages that [[abstract]] away the inner workings of the computer. Low level languages include: * [[Assembly]] Other more advanced terms include: * [[Building / Compiling]] * [[Git]] and [[GitHub]] are useful for saving your coding projects === General Programming === [[Hacking]] and [[Cybersecurity]] terms: * Early internet: [[ARPANET]] * Attacks: ** [[DDoS]] ** [[Ransomware]] ** [[Malware]] ** [[Trojan]] ** [[Virus]] * Defence: ** [[Penetration testing|Penetration Testing]] __INDEX__ __NEWSECTIONLINK__ 4ed3fb67b7cc59e6151d8175b7835b25723580a0 0 1345 5738 2026-06-14T08:24:52Z Wreckvall 426 created an article with the basics of bash wikitext text/x-wiki Bash is short for Bourne Again Shell, a [[Free and Open Source Software|free open-source]] interactive [[shell]] that allows you to type [[Command|commands]] and write [[Script|scripts]]. It is made for [[Unix]]-like operating systems, such as [[Linux]] and [[BSD]]. === Bash Command Line === Bash's interactive shell displays a prompt (usually a $) and waits for users to type in a command. After executing it, it displays the output of the command to the user. Bash follows a simple structure: [COMMAND] [OPTIONS] [ARGUMENTS] The command is a short word that corresponds to an executable file in the /usr/bin or /bin folder. The options are single letters or words preceded by a dash or two dashes (for instance, <code>-r</code> or <code>-name</code>). The arguments are the items you input to the command, which can include things like file names, directories, strings, numbers, etc... ==== Common Commands ==== ===== Managing [[Directory|directories]] and files: ===== ====== <code>touch</code> ====== <code>touch</code> creates a file. If the file already exists, <code>touch</code> will update the metadata. Examples of <code>touch</code> include: <code>touch new_file</code> ''creates a file called new_file'' <code>touch new_file1 new_file2 new_file3</code> ''creates three new files named new_file1, new_file2, and new_file3'' <code>touch old_file</code> ''update old_file's metadata'' <code>touch -c file</code> ''updates file's metadata but does not create file if file doesn't exist yet'' <code>touch -d "custom date" old_file</code> ''sets old_file's timestamp to a custom string'' ====== <code>mkdir</code> ====== <code>mkdir</code> creates a new directory. Examples of <code>mkdir</code> include: <code>mkdir new_dir</code> ''creates a'' ''directory called new_dir'' <code>mkdir new_dir1 new_dir2 new_dir3</code> ''creates three new'' ''directories named new_dir1, new_dir2, and new_dir3'' ====== <code>mv</code> ====== <code>mv</code> is short for 'move.' This is also how you rename files. Examples of <code>mv</code> include: <code>mv file new/location/</code> ''moves file to the new/location/ directory'' <code>mv file new_file_name</code> ''renames file to new_file_name'' <code>mv file new/location/new_file_name</code> ''moves file to the new/location/ directory and renames it to new_file_name simultaneously'' <code>mv file1 file2 file3 new/location/</code> ''moves file1, file2, and file3 to the new/location/ directory'' ====== <code>rm</code> ====== <code>mv</code> is short for 'remove.' This is also how you delete directories and files. Examples of <code>rm</code> include: <code>rm file</code> ''deletes file'' <code>rm file1 file2 file3</code> ''deletes file1, file2, and file3'' <code>rm *.txt</code> ''delete every file that ends with .txt'' <code>rm -i *.txt</code> ''same as above, but the shell will prompt you for a confirmation for each file before deleting it'' <code>rm -r directory</code> ''deletes a directory and all the files inside of it (-r option means recursive, so everything inside the directory will be deleted)'' '''<u>DANGER: DO NOT EVER EXECUTE THE COMMAND <code>rm -rf /</code>. THIS WILL WIPE YOUR WHOLE OS AND YOU WILL REGRET IT. THE <code>f</code> IN THE <code>-rf</code> OPTION STANDS FOR FORCE AND IT WILL IGNORE EVERYTHING AND YOUR WHOLE COMPUTER WILL BE GONE IN THE BLNK OF AN EYE.</u>''' ====== <code>cp</code> ====== <code>cp</code> is short for 'copy.' This allows you to duplicate directories and files. Examples of <code>cp</code> include: <code>cp file duplicate</code> ''create a copy of file called duplicate'' <code>cp file new/location/</code> ''copy file into the directory new/location/'' <code>cp file1 file2 file3 new/location/</code> ''copy file1, file2, and file3 into the directory new/location/'' <code>cp -r directory/ new/</code> ''use the -r option (recursive) to copy a whole directory into another directory'' ====== <code>find</code> ====== <code>find</code> allows you to filter through files. Examples of <code>find</code> include: <code>find directory -name "file"</code> ''outputs all files within directory with 'file' in their name'' <code>find directory -type f -name "file"</code> ''outputs all regular files within directory with 'file' in their name'' <code>find directory -type d -name "dir"</code> ''finds all directories with 'dir' in their name'' ====== <code>grep</code> ====== <code>grep</code> is similar to find but also incorporates [[Regular Expression|regular expressions]]. Examples of <code>grep</code> include: <code>grep "searchterm" file</code> ''outputs all instances of "searchterm" inside file'' <code>grep -i "searchterm" file</code> ''same thing but case insensitive, so SEARCHTERM and SeArChTeRm also match'' <code>grep -r "searchterm" directory</code> ''outputs all instances of "searchterm" inside the files within the directory'' ====== <code>cat</code> ====== <code>cat</code> shows you what's inside a file. Examples of <code>cat</code> include: <code>cat file</code> ''outputs contents of file'' <code>cat file1 file2 file3</code> ''outputs contents of file1, file2, and file3 concatenated with each other'' ===== Text Editing: ===== A few text editors are out there for you to choose. These include: * [[nano]] * [[micro]] * [[vim]] Simply type the name of your editor and the location of your file to start editing. For instance, <code>nano config.conf</code>. ===== Installing [[Package|Packages]]: ===== See the articles on some common package managers to learn how to use them in the shell. * [[APT|apt]] * [[DNF|dnf]] * [[pacman]] ===== Compression: ===== [[Tar.xz|tar.xz / Tarball]] ==== Pipes and Redirection ==== ===== Pipes ===== Pipes connect the output of one command into the input of another, replacing one of the arguments. For instance, say we have a file called <code>file.txt</code> which contains the name of a file we want to delete. Then, we can run: cat file.txt | rm Essentially, the output of <code>cat file.txt</code> acts as the argument of the <code>rm</code> command. ===== Redirection ===== Redirection takes the output of one command and changes the contents of a file. For instance, let's say we have a file called <code>file.txt</code>, which has been corrupted. Luckily, we have a backup called <code>backup.txt</code>. One way we would restore <code>file.txt</code> is to replace its contents with the backup using redirection: cat backup.txt > file.txt A common way to clear out all the contents of a file is <code>cat > file</code>, since <code>cat</code> itself returns an empty string. You can also append to the end of a file using <code>>></code>: echo "another line" >> file.txt d62a1c23696817dc740a70fe1cb4f6f8ac06c9f8 0 1095 5740 5463 2026-06-14T12:31:27Z Madonuko 140 fix hmct dead link template wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Eliza.png]] | caption = Tempest For eliza in use | title = Tempest for eliza | releasestatus = discontinued | lastrelease = 1.0.5, 2002 | firstrelease = 1.0.0, unknown | languages = Unknown | developers = Erikyyy | website = [https://erikyyy.de/tempest/]{{Dead Link|2026-05-26|<nowiki>Cannot connect to host erikyyy.de:443 ssl:default [[SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1081)]</nowiki>}} }} '''Tempest for Eliza''' is an experimental open-source program written by Erik Thiele that turns a computer monitor into a rudimentary AM radio transmitter by exploiting unintended electromagnetic emissions from display hardware. It is part of a class of software and research projects inspired by “TEMPEST” side-channel techniques. == overview == Tempest for Eliza generates carefully designed pixel patterns on a computer screen. These patterns cause the monitor’s electronic components to emit electromagnetic signals at specific frequencies. When these emissions are picked up by an AM radio tuned to the right frequency, they can be interpreted as sound often musical tones == background == The project is based on research into compromising electromagnetic emanations, a field sometimes referred to as TEMPEST. The term originally comes from a U.S. government codename related to standards for limiting electronic eavesdropping risks. A key academic foundation is the concept of van Eck phreaking, introduced by Wim van Eck in 1985, which showed that video displays can be reconstructed from their electromagnetic radiation. Tempest for Eliza builds on this idea in a creative direction: instead of reconstructing images from emissions Tempest for Eliza interfers the TEMPEST signals, also deliberately encodes audio signals into them. f4fae2a43b7b2414e6abeed42674f19392fa9b48 0 1243 5741 5417 2026-06-14T12:36:03Z Lawl 419 add more shelkls with general cleanup wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[Command-line interface]] (CLI) based shells and [[Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Capabilities == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Routes text data using redirection (<code>></code>, <code><</code>), pipelines (<code><nowiki>|</nowiki></code>), and built-ins like <code>read</code> or <code>mapfile</code> to capture input into variables/arrays. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns, limits, and controls process states using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exec</code>, and resource constraints via <code>ulimit</code>. |Spawns and kills processes when apps are opened and closed via graphical app launchers or task managers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. |Navigates and manages files and directories visually through a file manager (e.g., File Explorer, Finder). |- !Environment Management |Defines and propagates environment variables (like <code>PATH</code>) using <code>export</code> or startup scripts (<code>.profile</code>, <code>.bashrc</code>). |Modifies system configuration, system path, and user profile. through graphical apps such as settings panels. |- !Device Interaction |Reads from and writes directly to hardware devices using standard I/O redirection and device files. |Handles plug-and-play devices (e.g., mounting/ejecting flash drives) and manages peripherals via system settings. |} == Command Line Shells == // TODO: Explain command line, terminal emulators, command line interpreters, shell interpreters, and shell scripts {| class="wikitable" |- ! Shell !! Links !POSIX Compliance ! Description |- |[[Csh]] |[[wikipedia:C_shell|Wikipedia]] |No |The C Shell. Developed with an interactive command history and a syntax modeled closely after the C programming language. |- |[[Sh]] |[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html POSIX Standard Ch 02] |Yes |The original Bourne Shell. Established the foundational grammar for UNIX command interpreters and serves as the baseline reference for standard shell compliance. |- |[[Ksh]] |[http://kornshell.com Website] |Yes (compatible)<ref name=":0">These shells are capable of reading and running standard, universal POSIX scripts. However, they also include non-standard extensions (like Bash's arrays or double-bracket tests). If you write scripts using these extra features, they will work perfectly within that shell but will fail if you try to run them in a strict, pure POSIX environment.</ref> |The Korn Shell. Developed as an extension of the Bourne shell syntax, integrating interactive features from <code>csh</code> while establishing the scripting extensions that formed the basis of POSIX. |- |[[Bash]] || [https://www.gnu.org/software/bash/ Website] |Yes (compatible)<ref name=":0" />|| The "Bourne-Again Shell." An open-source, backwards-compatible replacement for <code>sh</code> created for the GNU project. Incorporates functional features from <code>ksh</code> and <code>csh</code>. |- |[[Zsh]] || [https://www.zsh.org/ Website] |Yes (compatible)<ref name=":0" />|| A highly customizable shell primarily based on the Korn shell (<code>ksh</code>) and the Bourne-syntax family. The default shell for macOS since 2019, it introduces massively upgraded interactive features like advanced menu-based auto-completion, spellcheck, and native recursive searching. |- |[[Fish]] |[https://fishshell.com/ Website] |No |Friendly Interactive Shell. Implements a custom, non-POSIX scripting syntax designed around automatic syntax highlighting and menu-driven command completion. |- |[[Elvish]] |[https://elv.sh/ Website] |No |A modern shell featuring an expressive, programming-language-like syntax, structured data support, and a built-in interactive file manager. |- |[[Xonsh]] || [https://xon.sh/ Website] |No | A Python based shell that features shared history across terminals and doubles as a superset of Python. |- |[[OSH]] |[https://oils.pub/osh.html Website] |Yes (compatible)<ref name=":0" /> |A Bash-compatible shell from the Oil project featuring precise error printouts and safer script execution. |- |[[Nushell]] |[https://www.nushell.sh/ Website] |No |A modern type of shell heavily inspired by PowerShell and functional programming. Rather than treating pipeline data as raw text, it passes structured data tables (objects with types) natively across commands. |- |[[YSH]] |[https://oils.pub/ysh.html Website] |No |A modern shell from the Oil project that acts as a bridge between traditional shell scripting, Python, YAML, and JSON. |- |[[OKsh]] |[https://github.com/ibara/oksh Github repository] |Yes |An unofficial port of OpenBSD's [[PDKsh]]. |- |[[PDKsh]] |None |Yes |OpenBSD's clone of [[Ksh]]. |- |[[Yash]] |[https://magicant.github.io/yash/ Website] |Yes |A shell focusing on being the most [[POSIX]] compliant shell in the world while focusing on usability. |} == Graphical Shells == // TODO: Explain Graphical shells, create a comparison table for Graphical shells like the shell table above == References == <references /> 56b7a64fb8fd2aebbad2eda738c896911c6933c7 0 394 5742 5655 2026-06-14T12:54:05Z Lawl 419 add more bsd based operating systems and general cleanup wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel == BSD Based == {| class="wikitable" |- ! OS !! Description |- |[[BSD|Berkeley Software Distribution (BSD)]] |A discontinued [[Unix]]-like operating system designed to improve on Bell Labs' UNIX |- |[[DragonFly BSD]] |An operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- |[[FreeBSD]] |An operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- |[[GhostBSD]] |A fork of [[FreeBSD]] focused on user friendliness and desktop usability |- |[[HardenedBSD]] |A security-enhanced fork of [[FreeBSD]].<ref>[https://hardenedbsd.org/content/about HardenedBSD's about page]</ref> |- |[[NetBSD]] |An operating system focused on code clarity, careful design, and portability across many computer architectures |- |[[OpenBSD]] |An operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- |[[pfSense]] |A [[FreeBSD]]-based firewall tailored for use as a firewall and router.<ref>>[https://en.wikipedia.org/wiki/List_of_BSD_operating_systems Wikipedia's list of BSD operating systems]</ref> |- |[[TrueNAS Core]] |Originally known as FreeNAS and based on [[FreeBSD]], this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |} == Darwin Based == {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} == Solaris Based == {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} == Other UNIX-like == {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} == L4 based == {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} == Other Operating Systems == {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An operating system originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs|TempleOS]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[RISC OS]] | An open-source operating system designed in Cambridge, England by Acorn. First released in 1987, its origins can be traced back to the original team that developed the Arm microprocessor. |- |} c5d8079993a06ca4268c4af9dc0b0e2ded0b91c6 5743 5742 2026-06-14T15:02:23Z Lawl 419 add way more to BSD table, needs moving to own page wikitext text/x-wiki These are Operating Systems that are not using the Linux Kernel == BSD Based == <!-- TODO: BSD-based should be ported to it's own page as it's way too large for here. Upon being moved it should also divide all the BSD operating systems into the table into the respective operating system they fork. --> {| class="wikitable" |- ! OS !! Description |- |[[BSD|Berkeley Software Distribution (BSD)]] |A discontinued [[Unix]]-like operating system designed to improve on Bell Labs' UNIX |- |[[DragonFly BSD]] |An operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- |[[FreeBSD]] |An operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- |[[GhostBSD]] |A fork of [[FreeBSD]] focused on user friendliness and desktop usability |- |[[HardenedBSD]] |A security-enhanced fork of [[FreeBSD]].<ref>[https://hardenedbsd.org/content/about HardenedBSD's about page]</ref> |- |[[NetBSD]] |An operating system focused on code clarity, careful design, and portability across many computer architectures |- |[[OpenBSD]] |An operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- |[[pfSense]] |A [[FreeBSD]]-based firewall tailored for use as a firewall and router.<ref>>[https://en.wikipedia.org/wiki/List_of_BSD_operating_systems Wikipedia's list of BSD operating systems]</ref> |- |[[ClonOS]] |A [[FreeBSD]] based operating system which provides a complete web UI for controlling and managing [[FreeBSD]] [[Jails]], virtual environments and more |- |[[helloSystem]] |A desktop system that focuses on simplicity, elegance, and usability. |- |[[Junos OS]] |An operating system for Juniper routers |- |[[MidnightBSD]] |A fork of the [[FreeBSD]] 6.1 Beta. |- |[[XigmaNAS]] |An operating system for network-attached storage servers, as a continuation of [[FreeNAS]]. |- |[[NomadBSD]] |A persistent live system for USB flash drives. |- |[[OPNsense]] |A [[pfSense]] forked operating system designed to be used on routers or as a firewall. |- |[[Zrouter]] |[[FreeBSD]] based firmware for embedded devices |- |[[ULBSD]] |A [[Unix]]-like, desktop orientated operating system based on [[FreeBSD]], focusing on ease of installation and integration with the [[KDE]]6 [[desktop environment]]. |- |[[TrueNAS Core]] |Originally known as FreeNAS and based on [[FreeBSD]], this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |[[Gentoo/NetBSD]] |A discontinued subproject to port Gentoo features, like [[Portage]], to the [[NetBSD]] operating system. |- |[[Debian GNU/NetBSD]] |An abandoned project to attempt to combine the [[NetBSD]] [[kernel]] with the other [[Debian]] tools. |- |[[irBSD]] |A discontinued digital forensics kit based on [[NetBSD]]. |- |[[Jibbed]] |An operating system designed for use on live CDs, based on [[NetBSD]]. |- |[[OS108]] |A desktop-orientated operating system based on [[NetBSD]]. |- |[[PolyBSD]] |A multipurpose framework for building embedded systems based on [[NetBSD]]. |- |[[smolBSD]] |A system creation tool based on [[NetBSD]], aimed at building modern, fast and lightweight VMs. |} == Darwin Based == {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} == Solaris Based == {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} == Other UNIX-like == {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} == L4 based == {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} == Other Operating Systems == {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An operating system originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs|TempleOS]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[RISC OS]] | An open-source operating system designed in Cambridge, England by Acorn. First released in 1987, its origins can be traced back to the original team that developed the Arm microprocessor. |- |} c533b44238ce58e3fe7dfc95ab93e209325d132a 5745 5743 2026-06-14T15:44:00Z Lawl 419 move bsd list to respective page, clear up capitalizsation wikitext text/x-wiki These are some operating systems that '''do not''' use the [[Linux]] [[kernel]]. The list of [[BSD]] operating systems is on it's own respective page, as the list is much larger than any other list here. == Darwin Based == {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} == Solaris Based == {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} == Other UNIX-like == {| class="wikitable" |- ! OS !! Description |- | [[Pixo OS]] | Created by Pixo Inc and licensed to Apple for their iPod Products |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} == L4 based == {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} == Other Operating Systems == {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An operating system originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs|TempleOS]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[RISC OS]] | An open-source operating system designed in Cambridge, England by Acorn. First released in 1987, its origins can be traced back to the original team that developed the Arm microprocessor. |- |} 75b8b8e272037b26cca73b8ff4ee6603c3ea2fab 0 1014 5744 4185 2026-06-14T15:41:23Z Lawl 419 move BSD table from misc operating systems to own respective BSD page, correct some information in the info card wikitext text/x-wiki {{DistributionInfobox | title = BSD | image = [[File:Daemon-phk.svg|frameless|upright=0.7]] | caption = The BSD Daemon, the mascot of BSD | releasestatus = Discontinued | releasemodel = Discontinued | packagemanager = [[Ports]] | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = Intel 80386, PDP-11, VAX | website = [https://www.bsd.org/ www.bsd.org] }} The Berkeley Software Distribution (BSD), also known as Berkeley [[UNIX|Unix]], is a discontinued Unix [[Operating System|operating system]] developed and distributed by the Computer Systems Research Group (CSRG) at the University of California, Berkeley (Hence the name). First released in 1978, it began as an improved derivative of AT&T's original Unix developed at Bell Labs, based on the source code. BSD's Mascot is a red daemon, commonly nicknamed [[Beastie]]. == Flavours == Similarly to how [[Linux]] has distributions, [[BSD]] has flavors, all based on the original [[BSD]]. They are listed below. {| class="wikitable" |- ! OS !! Description |- |[[BSD|Berkeley Software Distribution (BSD)]] |A discontinued [[Unix]]-like operating system designed to improve on Bell Labs' UNIX |- |[[DragonFly BSD]] |An operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- |[[FreeBSD]] |An operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- |[[GhostBSD]] |A fork of [[FreeBSD]] focused on user friendliness and desktop usability |- |[[HardenedBSD]] |A security-enhanced fork of [[FreeBSD]].<ref>[https://hardenedbsd.org/content/about HardenedBSD's about page]</ref> |- |[[NetBSD]] |An operating system focused on code clarity, careful design, and portability across many computer architectures |- |[[OpenBSD]] |An operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- |[[pfSense]] |A [[FreeBSD]]-based firewall tailored for use as a firewall and router.<ref>>[https://en.wikipedia.org/wiki/List_of_BSD_operating_systems Wikipedia's list of BSD operating systems]</ref> |- |[[ClonOS]] |A [[FreeBSD]] based operating system which provides a complete web UI for controlling and managing [[FreeBSD]] [[Jails]], virtual environments and more |- |[[helloSystem]] |A desktop system that focuses on simplicity, elegance, and usability. |- |[[Junos OS]] |An operating system for Juniper routers |- |[[MidnightBSD]] |A fork of the [[FreeBSD]] 6.1 Beta. |- |[[XigmaNAS]] |An operating system for network-attached storage servers, as a continuation of [[FreeNAS]]. |- |[[NomadBSD]] |A persistent live system for USB flash drives. |- |[[OPNsense]] |A [[pfSense]] forked operating system designed to be used on routers or as a firewall. |- |[[Zrouter]] |[[FreeBSD]] based firmware for embedded devices |- |[[ULBSD]] |A [[Unix]]-like, desktop orientated operating system based on [[FreeBSD]], focusing on ease of installation and integration with the [[KDE]]6 [[desktop environment]]. |- |[[TrueNAS Core]] |Originally known as FreeNAS and based on [[FreeBSD]], this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |[[Gentoo/NetBSD]] |A discontinued subproject to port Gentoo features, like [[Portage]], to the [[NetBSD]] operating system. |- |[[Debian GNU/NetBSD]] |An abandoned project to attempt to combine the [[NetBSD]] [[kernel]] with the other [[Debian]] tools. |- |[[irBSD]] |A discontinued digital forensics kit based on [[NetBSD]]. |- |[[Jibbed]] |An operating system designed for use on live CDs, based on [[NetBSD]]. |- |[[OS108]] |A desktop-orientated operating system based on [[NetBSD]]. |- |[[PolyBSD]] |A multipurpose framework for building embedded systems based on [[NetBSD]]. |- |[[smolBSD]] |A system creation tool based on [[NetBSD]], aimed at building modern, fast and lightweight VMs. |} 5506af971785721e5151403016f45d051d93688e 5746 5744 2026-06-14T15:46:16Z Lawl 419 add comment + stub wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = BSD | image = [[File:Daemon-phk.svg|frameless|upright=0.7]] | caption = The BSD Daemon, the mascot of BSD | releasestatus = Discontinued | releasemodel = Discontinued | packagemanager = [[Ports]] | defaultdesktops = Terminal User Interface | usagetype = Desktop | architectures = Intel 80386, PDP-11, VAX | website = [https://www.bsd.org/ www.bsd.org] }} The Berkeley Software Distribution (BSD), also known as Berkeley [[UNIX|Unix]], is a discontinued Unix [[Operating System|operating system]] developed and distributed by the Computer Systems Research Group (CSRG) at the University of California, Berkeley (Hence the name). First released in 1978, it began as an improved derivative of AT&T's original Unix developed at Bell Labs, based on the source code. BSD's Mascot is a red daemon, commonly nicknamed [[Beastie]]. == Flavours == <!-- TODO!!! someone pls organize these!! there should be seperate lists for bsd flavours that have a large amount of operating systems based on them like openbsd, netbsd or freebsd!! i'll probably end up doing this myself somewhat soon but if ur seeing this and have time to do it now PLEASE do!!! - lawl --> Similarly to how [[Linux]] has distributions, [[BSD]] has flavors, all based on the original [[BSD]]. They are listed below. {| class="wikitable" |- ! OS !! Description |- |[[BSD|Berkeley Software Distribution (BSD)]] |A discontinued [[Unix]]-like operating system designed to improve on Bell Labs' UNIX |- |[[DragonFly BSD]] |An operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. |- |[[FreeBSD]] |An operating system based on U.C. Berkeley's "4.4BSD-Lite" release |- |[[GhostBSD]] |A fork of [[FreeBSD]] focused on user friendliness and desktop usability |- |[[HardenedBSD]] |A security-enhanced fork of [[FreeBSD]].<ref>[https://hardenedbsd.org/content/about HardenedBSD's about page]</ref> |- |[[NetBSD]] |An operating system focused on code clarity, careful design, and portability across many computer architectures |- |[[OpenBSD]] |An operating system that emphasizes portability, standardization, correctness, proactive security and integrated cryptography |- |[[pfSense]] |A [[FreeBSD]]-based firewall tailored for use as a firewall and router.<ref>>[https://en.wikipedia.org/wiki/List_of_BSD_operating_systems Wikipedia's list of BSD operating systems]</ref> |- |[[ClonOS]] |A [[FreeBSD]] based operating system which provides a complete web UI for controlling and managing [[FreeBSD]] [[Jails]], virtual environments and more |- |[[helloSystem]] |A desktop system that focuses on simplicity, elegance, and usability. |- |[[Junos OS]] |An operating system for Juniper routers |- |[[MidnightBSD]] |A fork of the [[FreeBSD]] 6.1 Beta. |- |[[XigmaNAS]] |An operating system for network-attached storage servers, as a continuation of [[FreeNAS]]. |- |[[NomadBSD]] |A persistent live system for USB flash drives. |- |[[OPNsense]] |A [[pfSense]] forked operating system designed to be used on routers or as a firewall. |- |[[Zrouter]] |[[FreeBSD]] based firmware for embedded devices |- |[[ULBSD]] |A [[Unix]]-like, desktop orientated operating system based on [[FreeBSD]], focusing on ease of installation and integration with the [[KDE]]6 [[desktop environment]]. |- |[[TrueNAS Core]] |Originally known as FreeNAS and based on [[FreeBSD]], this original version of the popular NAS OS has since been replaced with a version based on [[Debian]] |- |[[Gentoo/NetBSD]] |A discontinued subproject to port Gentoo features, like [[Portage]], to the [[NetBSD]] operating system. |- |[[Debian GNU/NetBSD]] |An abandoned project to attempt to combine the [[NetBSD]] [[kernel]] with the other [[Debian]] tools. |- |[[irBSD]] |A discontinued digital forensics kit based on [[NetBSD]]. |- |[[Jibbed]] |An operating system designed for use on live CDs, based on [[NetBSD]]. |- |[[OS108]] |A desktop-orientated operating system based on [[NetBSD]]. |- |[[PolyBSD]] |A multipurpose framework for building embedded systems based on [[NetBSD]]. |- |[[smolBSD]] |A system creation tool based on [[NetBSD]], aimed at building modern, fast and lightweight VMs. |} 6ed57df6b7a7a0c09eccb5168d242c0298176ad8 1 1140 5747 5109 2026-06-14T16:24:34Z Lawl 419 /* remove tables, replace with links to FOSS wiki pages */ new section wikitext text/x-wiki == how to organize software == half actual discussion, half making sure some browsers aren't breaking this feature [[User:Nathan22211|Nathan22211]] ([[User talk:Nathan22211|talk]]) 01:07, 23 May 2026 (UTC) == Missing software. == This page has a header saying that, <code>This article is currently a work in progress. Please check with the editor who placed the template before making any content changes.</code> So I am going to follow the advice and list some of the missing pages. * For the <code>Terminal-based text editors</code> section, we are missing [[Neovim]] and [[Helix]]. There is also a [[Nano]] page that is included but not linked to. * For the <code>Package managers</code>, we already have a [[Package Manager|page for them]] that lists many not on this page. * [[Tor]] is not listed anywhere, so are there a bunch of pages that are not listed. * And more™ This list is fairly incomplete, and definitely needs some work, but the header does state to talk before making edits, so perhaps a different header is required. @[[User:Electron271|Electron271]] pinging you since it seems like you were the one to add the header. [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 13:45, 23 May 2026 (UTC) :I removed the template because a wiki itself is a work in progress. [[User:Rob Kam|Rob Kam]] ([[User talk:Rob Kam|talk]]) 15:38, 23 May 2026 (UTC) ::I added Vim and Helix [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 15:51, 23 May 2026 (UTC) == Link to the wiki page in the name not the "links" == I am strongly apposed to having the <code>FOSS wiki</code> links be with the other links, instead, I think they should be found by clicking on the program name. This page is linked from the front page and will likely be used by new people to find pages. I think the <code>Links</code> should be changed to <code>External links</code> and you going to the wiki page by clicking on the name, as it was previously. Currently, this page is just a list of software in general, not wiki pages about software (despite being on the front page). This change just adds to that. [[User:Uniolo|Uniolo]] ([[User talk:Uniolo|talk]]) 18:35, 24 May 2026 (UTC) == remove tables, replace with links to FOSS wiki pages == feels weird that you have a able with about 2 entries in it for some pieces of software, and none for others i think it would make sense and be better if this page was more just a contents page, where you go and find a dedicated page instead of the table, like just remove the tables as a whole it would make more sense and means that users would find more software that they were looking for originally [[User:Lawl|Lawl]] ([[User talk:Lawl|talk]]) 16:24, 14 June 2026 (UTC) b49b72be08b21a4a1904c6c2cdbcb41111017582 6 1346 5748 2026-06-14T18:11:01Z Sivecano 413 the logo of the River wayland compositor. Authored by Isaac Freund, source: https://codeberg.org/river/river/src/commit/d4fef528467974b9014b0bc9c47a9ea682cc8d4b/logo/logo.svg wikitext text/x-wiki == Summary == the logo of the River wayland compositor. Authored by Isaac Freund, source: https://codeberg.org/river/river/src/commit/d4fef528467974b9014b0bc9c47a9ea682cc8d4b/logo/logo.svg == Licensing == {{CC-BY-SA-4.0}} 9b766861c7008fd412e98adceb3aaca2dcc92d09 0 1347 5749 2026-06-14T18:22:08Z Sivecano 413 initial page for river wikitext text/x-wiki {{Work In Progress}} {{SoftwareInfobox | caption = River logo | developers = Isaac Freund | firstrelease = v0.1.0, 2021-09-03 | languages = [[Zig]] | lastrelease = v0.4.5, 2026-04-25 | title = River | website = [https://isaacfreund.com/software/river/] | releasestatus = Maintained | image = [[File:River logo.svg|thumb|center|alt=the logo of the river project]] }} River is a non-monolithic wayland compositor. Unlike most wayland compositor it does not combine compositor and window manager into one program. River achieves this by implementing a custom wayland protocol called `river-window-management-v1` which allows any client implementing it to become the window manager for river. This split allows for a lot more experimentation and window manager implementations in less performant programming languages like [[Python]]. It also makes the process a lot easier when compared to writing a full compositor. ==Window Managers== There is a an [https://codeberg.org/river/wiki/src/branch/main/pages/wm-list.md official list of window managers] in river's wiki. ==Input Config== Not all window managers configure input devices on river. Since the wayland protocols for this are entirely disjoint, there are some stand-alone tools that will work with most window managers. * [https://codeberg.org/Sivecano/channel channel] is a daemon that hot-reloads its config and has some glob-based matching rules. * [https://github.com/kewuaa/kwim kwim] a simple input config tool that simply one-shot-applies its config. 6794b0180a62920258f036e48ee150facebf8d1a 0 1348 5750 2026-06-14T19:23:19Z Lawl 419 make r-commands page wikitext text/x-wiki {{Stub}} <!-- TODO: add security section discussing security issues, add more content in general --> The '''Berkeley r-commands''' are a set of computer programs which allow a user on one [[Unix]] system to log in, run commands, and more on another remote [[Unix]] machine. The software suite was developed in 1982 by the '''Computer Systems Research Group''' at the '''University of California, Berkeley''', based on an early protocol stack of the [[Internet]]. The Computer Systems Research Group built the r-commands into their own version of [[Unix]], now known as [[BSD]], and were available after [[BSD]] v4.1. The r-commands suite quickly became the standard for [[Unix]] operating systems, and were a significant innovation.<ref>[https://en.wikipedia.org/wiki/Berkeley_r-commands Wikipedia entry on the r-commands]</ref> However, as the [[Internet]] grew, the numerous security issues in the suite became obvious, which led to the creation of the Secure Shell ([[SSH]]) protocol. [[SSH]] rapidly replaced the r-command suite along with other insecure protocols used at the time, such as [[Telnet]]. == List of commands == {| class="wikitable" |- ! Command !! Description |- | '''rcp''' || Used to remotely copy a file over the network |- | '''rlogin''' || Used to remotely login to a machine over a network. |- | '''rsh''' || Used to run a shell command on a remote computer without authenticating. |- | '''rwho''' || A command used to list those who are currently logged on to the remote machine the command was executed on. |- | '''rexec''' || A command to run a shell command on a remote computer, but requires authentication. |- | '''rstat''' || A command that returns performance statistics from the kernel. |- | '''ruptime''' || A command that returns the status report from all computers on the network. |} c1ec37b99c997820e995da7e0c6cb96351b50b99 0 1349 5755 2026-06-15T10:51:43Z Xwastyz 428 Created the documentation about bedrock linux. wikitext text/x-wiki '''<big>Bedrock Linux</big>''' is a meta Linux Distribution that allows users to mix and match components from otherwise incompatible Linux distributions (like Debian, Arch, Void, or Gentoo) into a single, cohesive operating system. Bedrock Linux lets you add new package managers/Distributions via so called "Stratas" These often only hold the Necessary dependencies/packages instead of the whole Distribution. Unlike projects like [https://distrobox.it/ Distrobox] Bedrock Linux does Not rely on containers, Installed Stratas/Distributions instead run natively on your system. Bedrock Linux also includes it´s own command line tool called "brl" [ For a list of commands visit; https://bedrocklinux.org/0.7/commands.html ] This is the primary cli-tool to install Stratas and to update the base system itself. '''<big><u>Pros</u></big>''' * '''Native''' - installed Stratas do not run inside of containers * '''Init/Kernel Customization''' - the easy installation of other Distributions allows users to use the init system from a chosen Distribution like Openrc from gentoo * '''Natively Run RHEL-Targeted Software''' - If you need to run proprietary or professional enterprise software that strictly assumes a Red Hat Enterprise Linux environment, you can easily integrate a CentOS or AlmaLinux layer by adding it as a strata. * '''Improved System Robustness''' '''-''' By keeping copies of essential filesystems across different distributions, you have redundancy. A bad kernel update from one system doesn't necessarily leave you with an unbootable system. * '''Management''' - Since every Distribution you install as a strata is kept as its own thing, you can easily remove a strata with brl, which will remove the strata and all associated Dependencies, Applications and Tools. This is very useful if one strata Miss behaves so you can easily "Reset" it. '''<big><u>Cons</u></big>''' * '''<u>High Complexity</u>''' '''<u>-</u>'''Managing multiple distributions simultaneously requires deep Linux knowledge. * '''Bootloader Risks''' '''-'''The installation process hijacks your existing system and can break bootloaders. (depending on file structure) * '''<u>No Easy Uninstallation</u>''' '''-''' You cannot simply uninstall Bedrock Linux, Fully Uninstalling it requires a full system reinstall. * '''Security Tracking Difficulties''' '''-''' Monitoring vulnerabilities across several active package managers is tedious. '''<u>Installing Bedrock Linux</u>''' Installing Bedrock Linux is usually the easiest process of Bedrock Linux. Bedrock Is not installed like any other traditional Linux Distribution, instead it relys on an "sh" script that will Hijack an your current Distribution to turn it into Bedrock Linux. <u>Heads up</u>''':''' You keep your base system and all your files nothing will be removed! It is also recommended to install Bedrock Linux on a fresh system and a system that is not using Btrfs with grub, Bedrock Linux does not allow this sort of file structure. For more information on how to Install Bedrock Linux visit; https://bedrocklinux.org/0.7/installation-instructions.html '''<big><u>Conclusion</u></big>''' Bedrock Linux '''Isn't''' For everyone. It requires at least a basic understanding of: * Init systems * Package managers * Basic commands (e.g: ls,cd,lsblk,lsusb,mv etc.) * Linux Distributions Installing it is not hard, using it however is using it as a daily driver is '''Not Recommended.''' Its Purpose is amazing but it doesnt fit everyone´s use case. If you want to learn more about bedrock Linux, visit their official website: [https://bedrocklinux.org/ BedrockLinux] 28e92b4d1c36038cdd1171d1298c4101b5ed2795 0 1350 5756 2026-06-15T11:02:46Z Xwastyz 428 Created page with "'''<big>Bedrock Linux</big>''' is a meta Linux Distribution that allows users to mix and match components from otherwise incompatible Linux distributions (like Debian, Arch, Void, or Gentoo) into a single, cohesive operating system. Bedrock Linux lets you add new package managers/Distributions via so called "Stratas" These often only hold the Necessary dependencies/packages instead of the whole Distribution. Unlike projects like [https://distrobox.it/ Distrobox] Bedrock..." wikitext text/x-wiki '''<big>Bedrock Linux</big>''' is a meta Linux Distribution that allows users to mix and match components from otherwise incompatible Linux distributions (like Debian, Arch, Void, or Gentoo) into a single, cohesive operating system. Bedrock Linux lets you add new package managers/Distributions via so called "Stratas" These often only hold the Necessary dependencies/packages instead of the whole Distribution. Unlike projects like [https://distrobox.it/ Distrobox] Bedrock Linux does Not rely on containers, Installed Stratas/Distributions instead run natively on your system. Bedrock Linux also includes it´s own command line tool called "brl" [ For a list of commands visit; https://bedrocklinux.org/0.7/commands.html ] This is the primary cli-tool to install Stratas and to update the base system itself. '''<big><u>Pros</u></big>''' * '''Native''' - installed Stratas do not run inside of containers * '''Init/Kernel Customization''' - the easy installation of other Distributions allows users to use the init system from a chosen Distribution like Openrc from gentoo * '''Natively Run RHEL-Targeted Software''' - If you need to run proprietary or professional enterprise software that strictly assumes a Red Hat Enterprise Linux environment, you can easily integrate a CentOS or AlmaLinux layer by adding it as a strata. * '''Improved System Robustness''' '''-''' By keeping copies of essential filesystems across different distributions, you have redundancy. A bad kernel update from one system doesn't necessarily leave you with an unbootable system. * '''Management''' - Since every Distribution you install as a strata is kept as its own thing, you can easily remove a strata with brl, which will remove the strata and all associated Dependencies, Applications and Tools. This is very useful if one strata Miss behaves so you can easily "Reset" it. '''<big><u>Cons</u></big>''' * '''<u>High Complexity</u>''' '''<u>-</u>'''Managing multiple distributions simultaneously requires deep Linux knowledge. * '''Bootloader Risks''' '''-'''The installation process hijacks your existing system and can break bootloaders. (depending on file structure) * '''<u>No Easy Uninstallation</u>''' '''-''' You cannot simply uninstall Bedrock Linux, Fully Uninstalling it requires a full system reinstall. * '''Security Tracking Difficulties''' '''-''' Monitoring vulnerabilities across several active package managers is tedious. '''<u>Installing Bedrock Linux</u>''' Installing Bedrock Linux is usually the easiest process of Bedrock Linux. Bedrock Is not installed like any other traditional Linux Distribution, instead it relys on an "sh" script that will Hijack an your current Distribution to turn it into Bedrock Linux. <u>Heads up</u>''':''' You keep your base system and all your files nothing will be removed! It is also recommended to install Bedrock Linux on a fresh system and a system that is not using Btrfs with grub, Bedrock Linux does not allow this sort of file structure. For more information on how to Install Bedrock Linux visit; https://bedrocklinux.org/0.7/installation-instructions.html '''<big><u>Conclusion</u></big>''' Bedrock Linux '''Isn't''' For everyone. It requires at least a basic understanding of: * Init systems * Package managers * Basic commands (e.g: ls,cd,lsblk,lsusb,mv etc.) * Linux Distributions Installing it is not hard, using it however is using it as a daily driver is '''Not Recommended.''' Its Purpose is amazing but it doesnt fit everyone´s use case. If you want to learn more about bedrock Linux, visit their official website: [https://bedrocklinux.org/ BedrockLinux] 320837f2570c82297240012af25e9f6245f0f812 5757 5756 2026-06-15T11:05:59Z Xwastyz 428 wikitext text/x-wiki '''<big>Bedrock Linux</big>''' is a meta Linux Distribution that allows users to mix and match components from otherwise incompatible Linux distributions (like Debian, Arch, Void, or Gentoo) into a single, cohesive operating system. Bedrock Linux lets you add new package managers/Distributions via so called "Stratas" These often only hold the Necessary dependencies/packages instead of the whole Distribution. Unlike projects like [https://distrobox.it/ Distrobox] Bedrock Linux does Not rely on containers, Installed Stratas/Distributions instead run natively on your system. Bedrock Linux also includes it´s own command line tool called "brl" [ For a list of commands visit; https://bedrocklinux.org/0.7/commands.html ] This is the primary cli-tool to install Stratas and to update the base system itself. '''<big><u>Pros</u></big>''' * '''Native''' - installed Stratas do not run inside of containers * '''Init/Kernel Customization''' - the easy installation of other Distributions allows users to use the init system from a chosen Distribution like Openrc from gentoo * '''Natively Run RHEL-Targeted Software''' - If you need to run proprietary or professional enterprise software that strictly assumes a Red Hat Enterprise Linux environment, you can easily integrate a CentOS or AlmaLinux layer by adding it as a strata. * '''Improved System Robustness''' '''-''' By keeping copies of essential filesystems across different distributions, you have redundancy. A bad kernel update from one system doesn't necessarily leave you with an unbootable system. * '''Management''' - Since every Distribution you install as a strata is kept as its own thing, you can easily remove a strata with brl, which will remove the strata and all associated Dependencies, Applications and Tools. This is very useful if one strata Miss behaves so you can easily "Reset" it. '''<big><u>Cons</u></big>''' * '''<u>High Complexity</u>''' '''<u>-</u>'''Managing multiple distributions simultaneously requires deep Linux knowledge. * '''Bootloader Risks''' '''-'''The installation process hijacks your existing system and can break bootloaders. (depending on file structure) * '''<u>No Easy Uninstallation</u>''' '''-''' You cannot simply uninstall Bedrock Linux, Fully Uninstalling it requires a full system reinstall. * '''Security Tracking Difficulties''' '''-''' Monitoring vulnerabilities across several active package managers is tedious. '''<u>Installing Bedrock Linux</u>''' Installing Bedrock Linux is usually the easiest process of Bedrock Linux. Bedrock Is not installed like any other traditional Linux Distribution, instead it relys on an "sh" script that will Hijack your current Distribution to turn it into Bedrock Linux. <u>Heads up</u>''':''' You keep your base system and all your files nothing will be removed! It is also recommended to install Bedrock Linux on a fresh system and a system that is not using Btrfs with grub, Bedrock Linux does not allow this sort of file structure. For more information on how to Install Bedrock Linux visit; https://bedrocklinux.org/0.7/installation-instructions.html '''<big><u>Conclusion</u></big>''' Bedrock Linux '''Isn't''' For everyone. It requires at least a basic understanding of: * Init systems * Package managers * Basic commands (e.g: ls,cd,lsblk,lsusb,mv etc.) * Linux Distributions Installing it is not hard, using it however is using it as a daily driver is '''Not Recommended.''' Its Purpose is amazing but it doesnt fit everyone´s use case. If you want to learn more about bedrock Linux, visit their official website: [https://bedrocklinux.org/ BedrockLinux] 6f9d8e316ad21634ed635d744ed807661dae0771 5758 5757 2026-06-15T11:08:11Z Xwastyz 428 Spelling mistake wikitext text/x-wiki '''<big>Bedrock Linux</big>''' is a meta Linux Distribution that allows users to mix and match components from otherwise incompatible Linux distributions (like Debian, Arch, Void, or Gentoo) into a single, cohesive operating system. Bedrock Linux lets you add new package managers/Distributions via so called "Stratas" These often only hold the Necessary dependencies/packages instead of the whole Distribution. Unlike projects like [https://distrobox.it/ Distrobox] Bedrock Linux does Not rely on containers, Installed Stratas/Distributions instead run natively on your system. Bedrock Linux also includes it´s own command line tool called "brl" [ For a list of commands visit; https://bedrocklinux.org/0.7/commands.html ] This is the primary cli-tool to install Stratas and to update the base system itself. '''<big><u>Pros</u></big>''' * '''Native''' - installed Stratas do not run inside of containers * '''Init/Kernel Customization''' - the easy installation of other Distributions allows users to use the init system from a chosen Distribution like Openrc from gentoo * '''Natively Run RHEL-Targeted Software''' - If you need to run proprietary or professional enterprise software that strictly assumes a Red Hat Enterprise Linux environment, you can easily integrate a CentOS or AlmaLinux layer by adding it as a strata. * '''Improved System Robustness''' '''-''' By keeping copies of essential filesystems across different distributions, you have redundancy. A bad kernel update from one system doesn't necessarily leave you with an unbootable system. * '''Management''' - Since every Distribution you install as a strata is kept as its own thing, you can easily remove a strata with brl, which will remove the strata and all associated Dependencies, Applications and Tools. This is very useful if one strata Miss behaves so you can easily "Reset" it. '''<big><u>Cons</u></big>''' * '''<u>High Complexity</u>''' '''<u>-</u>'''Managing multiple distributions simultaneously requires deep Linux knowledge. * '''Bootloader Risks''' '''-'''The installation process hijacks your existing system and can break bootloaders. (depending on file structure) * '''<u>No Easy Uninstallation</u>''' '''-''' You cannot simply uninstall Bedrock Linux, Fully Uninstalling it requires a full system reinstall. * '''Security Tracking Difficulties''' '''-''' Monitoring vulnerabilities across several active package managers is tedious. '''<u>Installing Bedrock Linux</u>''' Installing Bedrock Linux is usually the easiest process of Bedrock Linux. Bedrock Is not installed like any other traditional Linux Distribution, instead it relys on an "sh" script that will Hijack your current Distribution to turn it into Bedrock Linux. <u>Heads up</u>''':''' You keep your base system and all your files nothing will be removed! It is also recommended to install Bedrock Linux on a fresh system and a system that is not using Btrfs with grub, Bedrock Linux does not allow this sort of file structure. For more information on how to Install Bedrock Linux visit; https://bedrocklinux.org/0.7/installation-instructions.html '''<big><u>Conclusion</u></big>''' Bedrock Linux '''Isn't''' For everyone. It requires at least a basic understanding of: * Init systems * Package managers * Basic commands (e.g: ls,cd,lsblk,lsusb,mv etc.) * Linux Distributions Installing it is not hard, using it however as a daily driver is '''Not Recommended.''' Its Purpose is amazing but it doesnt fit everyone´s use case. If you want to learn more about bedrock Linux, visit their official website: [https://bedrocklinux.org/ BedrockLinux] c6a4a59d11ab5574e4e828c94379ebb9c033a217 2 1209 5759 5595 2026-06-15T19:59:10Z Hyperreal 388 Replaced content with "Main website: https://moonshadow.dev" wikitext text/x-wiki Main website: https://moonshadow.dev 652366af09cff298988ca205326f92fa3d36a60e 0 1351 5760 2026-06-16T09:20:23Z Wreckvall 426 talked about absolute vs relative paths and the tilde ~ wikitext text/x-wiki Directories (also known as folders) group files together, allowing for easy and clean access. Different directories can have different [[permissions]], different contents inside them, etc... === Naming === In [[Bash]], beginning a directory with a <code>/</code> would make it an '''absolute path'''. This means you start at the root directory and then go through the specified subdirectories. For instance, <code>/usr/bin/</code> starts at the root directory, goes into the <code>usr</code> directory, and then goes into the <code>bin</code> directory. Beginning a directory with <code>~/</code> would make it start at '''home directory''' of the currently logged in user. For instance, <code>~/Desktop/project/</code>. Otherwise, if a directory just starts with a word (e.g., <code>project/files/</code>), then it is implied to be within the current working directory (aka, the directory the user is in now). You can change working directories with the <code>cd</code> command. Thus, if the user is in the <code>~/Desktop/</code> directory, then <code>project/files/</code> is the same directory as the relative directory <code>files/</code> if the working directory is <code>~/Desktop/project</code>. Note that it improves clarity to end directories with a <code>/</code> and files with nothing. For instance, <code>project/files/subdirectory/</code> is a directory whereas <code>project/files/just_a_file.txt</code> is a file. This makes it more obvious whether you are talking about a file or a directory. While it's OK sometimes to write <code>project/files/subdirectory</code>, usually it can cause issues down the line. c3a9d4b140cb6af6e43cbac13debcd65a05fc754 0 602 5761 3689 2026-06-16T09:58:48Z Wreckvall 426 wrote the definitions wikitext text/x-wiki [[Category:Window Management Systems]] {{Work In Progress}} == Disambiguation Page == [[Display Manager|DISPLAY MANAGER]]: The GUI of the login screen (after booting). [[X Window Manager|WINDOWS MANAGER]]: Controls the layout, tiling, positioning, and size of the windows on your screen. Essentially, the Windows Manager is about '''where'''. [[Wayland Compositors|COMPOSITOR]]: Handles the final image rendering, controlling the visual aspects of each window (e.g., blur, transparency, shadows). Essentially, the Compositor is about '''how''' the windows are drawn. Compositors are mainly for visual aesthetics and can also prevent screen tearing. [[Desktop Environments|DESKTOP ENVIRONMENT]]: A bundle of programs all working together to create the final GUI of your operating system. This includes the Windows Manager and Compositor together. f82981a4f3179e7921c5c3d3ee30b52c54b48623 0 1352 5762 2026-06-16T12:48:16Z Wreckvall 426 defined permission numbers, permission strings, and outlined how to change permissions wikitext text/x-wiki For each file, a user has three actions available to them: * <code>r</code>: read * <code>w</code>: write * <code>x</code>: execute If a user wants to do one of these actions, they need permission to do so. Permissions are usually split into three user types: * '''owner:''' the user who [[Ownership|owns]] the file * '''group:''' the group assigned to the file * '''others:''' everybody else === Permission Strings === A permission string describes the permissions of a file - aka, which user types get what perms. A permission string might look something like <code>-rwxr-</code><code>x--x</code>. Let's break it down into four parts: # <code>-</code>: File type. - means a standard file, d means a [[directory]], and l means a [[symbolic link]]. # <code>rwx</code>: The permissions of the owner. Here, the owner can read, write and execute. # <code>r-x</code>: The permissions of the user group. Here, the user group can read and execute, but not write. # <code>--x</code>: The permissions of others. Here, everybody else can execute but nothing else. You can view the permission strings of a file by running <code>ls -l</code> === Permission Numbers === A permission number is a more condensed form of a permission string. A permission number might look like <code>751</code>. Here, each digit represents a different user type. <code>7</code> represents that the owner can read, write and execute. <code>5</code> represents that the user group can read and execute. <code>1</code> represents that everybody else can only execute. In this numerical form, the three basic actions (read, write, and execute) correspond to different numbers: * <code>4</code>: read * <code>2</code>: write * <code>1</code>: execute They are added together to create the final digit. For instance, if a user can read and execute, that would be a <code>5</code>. If a user can write and execute, that would be a <code>3</code>. The highest permission level is a <code>7</code>, where the user has all permissions. The lowest permission level is <code>0</code>, where the user can't do anything. More examples of common permission numbers: * <code>755</code> (standard for directories and executables): Owner has all permissions, others can only read or execute. * <code>644</code> (standard for files): Owner can read and write, others can only read. * <code>777</code>: Everybody has full access. * <code>700</code>: Only the owner has full access, everybody else has no access. === Setting Permissions === You can set permissions by using the permission number you want the file or directory to have. For instance, sudo chmod 755 filename You can also change ownership with chown: sudo chown new_user filename For both of the above commands, use the <code>-R</code> option if you want to use it on a directory and apply the changes recursively to all the files inside of it. For instance, <code>sudo chmod -R 755 filename</code>. Additionally, for <code>chmod</code>, if you don't know the permission number you want, you can also make quick changes with symbolic notation. For instance: sudo chmod a+x filename is a common command that makes files executable. Here, <code>a</code> means everybody, <code>+</code> means add a permission, and <code>x</code> means executable. You can replace the <code>x</code> with <code>r</code> or <code>w</code> or a combination (e.g., <code>rx</code>). If you don't want the change to apply to everybody, you can specify <code>u</code> (owner) or <code>g</code> (group) or <code>o</code> (others). For instance, <code>sudo chmod ug+x filename</code> will only make the file executable for the owner and the user group. You can also take permissions away by changing the <code>+</code> to a <code>-</code>. For instance, <code>sudo chmod go-x filename</code> will remove execution permissions for everybody but the owner. 49473942b0d7e2a3011834aea481252867d38303 0 1353 5763 2026-06-16T13:11:57Z Wreckvall 426 wrote the definition wikitext text/x-wiki {{Stub}} A symbolic link (or symlink for short) is a file that acts as a pointer to another file or directory. Any reference to the symlink would be interpreted as a reference to the target file or directory. dd6c59a97c6fb94ae6c3f95c1e0cf2cc0c91d89c 0 309 5764 3677 2026-06-16T13:19:19Z Wreckvall 426 elaborated further on the use of sudo wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png.png|thumb]] |thumb]] | caption = Sudo used on [[whoami]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.17p2 | languages = [[C]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} [[Category:Software]] [[File:Sudo_logo_(2019).png|thumb|335x335px|Sudo's logo of a sandwich]] [[File:Sudo Insults.png|thumb|335x335px|Output from sudo when <code>Defaults insults</code> is added]] The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]).<ref name=":0">[https://man7.org/linux/man-pages/man8/sudo.8.html sudo(8)], Linux Manpages</ref> Its name is shorthand for "su 'do'"<ref>[https://www.sudo.ws/ sudo.ws], Sudo Developers</ref>, however as <code>su</code> stands for "substitute user"<ref>[https://man7.org/linux/man-pages/man1/su.1.html su(1)], Linux Manpages</ref> this would stand for "substitute user, do". When running a command with sudo, a process is spawned running as root while the shell stays your shell, temporarily giving you root privileges for that ''single'' command. While using sudo for every single command would functionally be the same as logging in as root, using sudo forces you to confirm (usually with your password) that you want to run a potentially dangerous command. This lets you run single isolated commands safely rather than giving you full control over the full system, which is risky. Additionally, system administrators may configure sudo by editing the <code>/etc/sudoers</code> file<ref name=":0" /> to specify which users or groups can execute specific commands. This way, it can be configured for some users to only be permitted to use sudo for specific actions, preserving both functionality and safety. == Usage == {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |Run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser''<ref name=":0" /> == Trivia == * Sudo's logo is a sandwich in reference to [https://xkcd.com/149/ xkcd 149]<ref>[https://www.sudo.ws/about/logo/ sudo.ws/about/logo], Sudo Developers</ref> * If you add the line <code>Defaults insults</code> to the Defaults section of <code>/etc/sudoers</code>, you will be insulted whenever you type the wrong password.<ref>[https://www.geeksforgeeks.org/when-sudo-insults-you/ When sudo insults you!!], GeeksforGeeks, September 13, 2023 (February 12, 2025)</ref> == References == 0252bbf2b5b8f9729db16d00d2e88c69ca9fa650 5770 5764 2026-06-16T14:34:22Z Madonuko 140 tidy up english wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png.png|thumb]] |thumb]] | caption = Sudo used on [[whoami]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.17p2 | languages = [[C]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} [[Category:Software]] [[File:Sudo_logo_(2019).png|thumb|335x335px|Sudo's logo of a sandwich]] [[File:Sudo Insults.png|thumb|335x335px|Output from sudo when <code>Defaults insults</code> is added]] The command line tool <code>sudo</code> is used to run commands as another user (most likely [[root]]).<ref name=":0">[https://man7.org/linux/man-pages/man8/sudo.8.html sudo(8)], Linux Manpages</ref> Its name is shorthand for "su 'do'"<ref>[https://www.sudo.ws/ sudo.ws], Sudo Developers</ref>, however as <code>su</code> stands for "substitute user"<ref>[https://man7.org/linux/man-pages/man1/su.1.html su(1)], Linux Manpages</ref> this would stand for "substitute user, do". When running a command with sudo, the command is spawned running as root, temporarily allowing root privileges for that ''single'' command. While using sudo for every single command would functionally be the same as logging in as root, using sudo forces confirmation (usually with the user password). sudo can be configured to run isolated commands safely without risking full control over the system. Additionally, system administrators may configure sudo by editing the <code>/etc/sudoers</code> file<ref name=":0" />, to specify which users or groups can execute specific commands, and to permit some users to use sudo for specific actions, preserving both functionality and safety. == Usage == {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |Run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser''<ref name=":0" /> == Trivia == * Sudo's logo is a sandwich in reference to [https://xkcd.com/149/ xkcd 149]<ref>[https://www.sudo.ws/about/logo/ sudo.ws/about/logo], Sudo Developers</ref> * If you add the line <code>Defaults insults</code> to the Defaults section of <code>/etc/sudoers</code>, you will be insulted whenever you type the wrong password.<ref>[https://www.geeksforgeeks.org/when-sudo-insults-you/ When sudo insults you!!], GeeksforGeeks, September 13, 2023 (February 12, 2025)</ref> == References == c1b45fc0807f1ecb732fdf995f3c7c28199233f3 0 1354 5765 2026-06-16T13:22:47Z Wreckvall 426 wrote the definition wikitext text/x-wiki {{Stub}} Root is the default Linux user with full control over the system. The root user is identified with a [[UID]] (user ID) of <code>0</code>. Any UID of <code>0</code> is automatically treated as the root user and is given unrestricted access to the system. When using the shell as the root user, the prompt will change form <code>$</code> to <code>#</code>. This warns you that you are running as the root user, and if you do something stupid, Linux will let you be stupid and you might nuke your whole system. Please be careful when running as root. 5245881e9fe5ba9b3e8f34d6d5e9e71b9bfb3b76 0 344 5766 4735 2026-06-16T13:32:02Z Wreckvall 426 expanded on the function of the kernel wikitext text/x-wiki [[Category:Terminology]] [[File:Kernel Layout.svg|thumb|How the Kernel interacts with the software and hardware.]] The '''kernel''' is the core part of any [[Operating System|operating system]], such as the [[Linux kernel]]. It's the fundamental layer between the computer's [[hardware]], including but not limited to the CPU, RAM, and GPU, and the [[:Category:Software|software]] you interact with. Functions of the kernel include: # '''Syscalls:''' Because you can't directly interact with the computer's hardware, you need to make a [[Syscalls|syscall]] to the kernel to interact with the hardware on your behalf. This ensures that all interactions with the hardware are safe and secure. # '''Process management:''' The kernel also manages [[Process|processes]]. It switches between different tasks at very high rates, making it look like they are happening concurrently (just like when your brain 'multitasks'). This is done to optimise efficiency. # '''Memory management:''' The kernel separates memory in virtual memory blocks, ensuring that no processes clash or overwrite each other's memory. This isolation is crucial to safety and security. # '''File management:''' The kernel controls data streams and I/O (input/output). Specifically, it manages the low-level side of data access and makes sure that we can read/write files safely and securely (e.g., by checking [[permissions]], coordinating simultaneous access of files by multiple users, mediating all operations on files to prevent data corruption). The [[Linux kernel]] itself is a modular and monolithic kernel, meaning that it incorporates most of the core functions within the kernel itself. These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2 Linus Torvalds 1991 (Retrieved 16th March 2025)</ref>: This is the normal Linux kernel that most people will use. Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel Kicksecure, Madaiden, Adrelanos 2023 (Retrieved 16th March 2025)</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. == References == 02725d86333be897be87e80b5dbcc6f9c59413d2 5768 5766 2026-06-16T14:25:48Z Madonuko 140 format wikitext text/x-wiki [[Category:Terminology]] {{stub}} {{Cleanup|incorrect citation format}} [[File:Kernel Layout.svg|thumb|How the Kernel interacts with the software and hardware.]] The '''kernel''' is the core part of any [[Operating System|operating system]], such as the [[Linux kernel]]. It's the fundamental layer between the computer's [[hardware]], including but not limited to the CPU, RAM, and GPU, and the [[:Category:Software|software]] you interact with. Functions of the kernel include: # '''Syscalls:''' Because you can't directly interact with the computer's hardware, you need to make a [[Syscalls|syscall]] to the kernel to interact with the hardware on your behalf. This ensures that all interactions with the hardware are safe and secure. # '''Process management:''' The kernel also manages [[Process|processes]]. It switches between different tasks at very high rates, making it look like they are happening concurrently (just like when your brain 'multitasks'). This is done to optimise efficiency. # '''Memory management:''' The kernel separates memory in virtual memory blocks, ensuring that no processes clash or overwrite each other's memory. This isolation is crucial to safety and security. # '''File management:''' The kernel controls data streams and I/O (input/output). Specifically, it manages the low-level side of data access and makes sure that we can read/write files safely and securely (e.g., by checking [[permissions]], coordinating simultaneous access of files by multiple users, mediating all operations on files to prevent data corruption). The [[Linux kernel]] itself is a modular and monolithic kernel, meaning that it incorporates most of the core functions within the kernel itself. These functions can be modified to be loaded or unloaded dynamically and even replaced with alternative modules. This modularity allows for easier customization to the kernel while also providing extended functionality as needed. Linux has multiple versions of its kernel, for example: * Basic Linux kernel<ref>https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/?h=v6.16-rc2 Linus Torvalds 1991 (Retrieved 16th March 2025)</ref>: This is the normal Linux kernel that most people will use. * Hardened Linux kernel <ref>https://github.com/Kicksecure/hardened-kernel Kicksecure, Madaiden, Adrelanos 2023 (Retrieved 16th March 2025)</ref>: The hardened Linux kernel is a modified version of the Linux kernel that incorporates additional security measures to protect against various exploits and vulnerabilities. Most servers and secure computers will use this. == References == cf4f6f80a038ac77c129939e3751172750d9f9a3 0 1355 5767 2026-06-16T13:40:49Z Wreckvall 426 defined processes and gave two types wikitext text/x-wiki A process is a program that is actively running. The PID is a unique identifier for the process. The 'owner' of the process is the user that started the process. Processes can also spawn 'child' processes that are called by the 'parent' process. === Types of Processes === '''Foreground:''' Usually executed in your shell, they prevent you from executing anything else until they are completed. '''Background:''' You can run other commands while the background processes are running. You can make something a background process by adding an & to the end of the command. A [[daemon]] is a type of background process. Daemons are managed by [[Service|services]], controlling the lifecycle of at least one daemon. a186c545b003ae58e7b51b65647b915ef4701207 1 1356 5769 2026-06-16T14:27:09Z Madonuko 140 /* Root can also refer to other terms */ new section wikitext text/x-wiki == Root can also refer to other terms == The term root can refer to the user (as mentioned in this current version) and also <code>/</code> (filesystem root). This is ambiguous. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 14:27, 16 June 2026 (UTC) 580b85ba797973f2bd67588cdfb4c718aa8a3487 0 1091 5771 5753 2026-06-16T18:05:12Z MysteryBirb 353 Fixed Guide Warning wikitext text/x-wiki {{Work In Progress}} {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.13.1, 2026-05-18 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io]{{Dead Link|2026-06-15|404}} | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref>. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 085243232fa8dc739d84ddbe7d772fc922ef3322 0 176 5772 5502 2026-06-16T18:57:13Z Strangely Human Feeling 415 updated KDE plasma version wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.7.0, June 16, 2026 [https://kde.org/announcements/plasma/6/6.7.0/] |firstrelease=1.0, July 12, 1998 [https://kde.org/announcements/1-2-3/1.0-beta1/] | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> [[Desktop Environments|desktop environment]] for [[UNIX]]-like [[Operating System|operating systems]] such as [[Linux]] and various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === Plasma includes these apps by default: * System Settings * [https://apps.kde.org/dolphin/ Dolphin] (file manager) * [https://apps.kde.org/discover/ Discover] (app store) * [https://apps.kde.org/konsole Konsole] (terminal emulator) * [https://apps.kde.org/spectacle Spectacle] (screenshot tool) * [https://apps.kde.org/kate Kate] (text editor) * [https://apps.kde.org/ark Ark] (archive manager) * [https://apps.kde.org/gwenview Gwenview] (image viewer) * [https://apps.kde.org/okular Okular] (document viewer) Additionally, KDE offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [https://apps.kde.org/krita/ Krita] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2026-05-26|403}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [https://apps.kde.org/kdenlive/ Kdenlive] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2026-05-26|403}} to demonstrate some of its basic capabilities. * [https://apps.kde.org/ark/ Ark] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [https://apps.kde.org/kate/ Kate] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [https://apps.kde.org/filelight/ Filelight] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode." In edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects apply special visual effects to the desktop. Plasma includes effects in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' in System Settings. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] rounds window corners on Plasma for both '''[[X11]]''' and '''[[Wayland]]'''. == References == <references /> 31c1f01a1222b6fd57296d2445c01eaea7ee6f46 5773 5772 2026-06-16T19:56:32Z Madonuko 140 /* Features */ wiki links wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained |lastrelease=6.7.0, June 16, 2026 [https://kde.org/announcements/plasma/6/6.7.0/] |firstrelease=1.0, July 12, 1998 [https://kde.org/announcements/1-2-3/1.0-beta1/] | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> [[Desktop Environments|desktop environment]] for [[UNIX]]-like [[Operating System|operating systems]] such as [[Linux]] and various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === Plasma includes these apps by default: * System Settings * [[Dolphin]] (file manager) * [[Discover]] (app store) * [[Konsole]] (terminal emulator) * [[Spectacle]] (screenshot tool) * [[Kate]] (text editor) * [[Ark]] (archive manager) * [[Gwenview]] (image viewer) * [[Okular]] (document viewer) Additionally, KDE offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [[Krita]] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2026-05-26|403}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [[Kdenlive]] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2026-05-26|403}} to demonstrate some of its basic capabilities. * [[Ark]] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [[Kate]] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [[Filelight]] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode." In edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects apply special visual effects to the desktop. Plasma includes effects in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' in System Settings. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] rounds window corners on Plasma for both '''[[X11]]''' and '''[[Wayland]]'''. == References == <references /> 8eff797270c961013d97dfc2f7e6a33d6ee17713 0 1247 5774 5543 2026-06-16T20:43:31Z Uniolo 345 Updated voice chat related info wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[TypeScript]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/cinnyapp/cinny }} [[Category:Software]] [[File:Cinny-Unredacted.org.png|thumb|A photo of Cinny in the Unredacted Matrix server chat]] '''Cinny''' is a free and open source [[Matrix]] client focused on providing a simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, along with the browser<ref name=":0">{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. It currently uses the [https://github.com/matrix-org/matrix-js-sdk matrix-js-sdk] but is in the process on replacing it with a custom one, as such, it is not currently accepting contributions<ref>{{Cite|url=https://github.com/cinnyapp/cinny|title=Cinny GitHub repo|author=Cinny contributors|year=2026-05-23|accessdate=2026-05-25}}</ref>. {| class="wikitable" |+Supported features<ref name=":0" /> !Name !Supported? |- |E2EE |Yes |- |Spaces |Yes |- |Voice chat (1:1) |No |- |Voice chat ([[Jitsi]]) |No |- |Voice chat (MatrixRTC) |No |- |Threads |No |- |Legacy SSO |Yes |- |Multiple accounts |No |- |Multiple languages |No |} 03be61e1909946aa81d622ea27349b6f2c7a18e0 5775 5774 2026-06-16T20:43:49Z Uniolo 345 Set "Voice chat (MatrixRTC)" to yes wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | image = [[File:Cinny logo.svg|thumb]] | caption = Cinny | title = Cinny | releasestatus = Maintained | lastrelease = v4.12.2, May 23, 2026 | firstrelease = 1.0.0, Jul 28, 2021 | languages = [[TypeScript]] | developers = [https://github.com/ajbura Ajay Bura], [https://github.com/kfiven Krishan] | website = [https://cinny.in/ cinny.im] | license = AGPL-3.0-or-later | sourcecode = https://github.com/cinnyapp/cinny }} [[Category:Software]] [[File:Cinny-Unredacted.org.png|thumb|A photo of Cinny in the Unredacted Matrix server chat]] '''Cinny''' is a free and open source [[Matrix]] client focused on providing a simple, elegant and secure interface<ref>{{Cite|url=https://cinny.in|title=Cinny website|author=Ajay Bura|year=2021|accessdate=2026-05-25}}</ref>. It supports encryption and is available on all major desktop platforms, along with the browser<ref name=":0">{{Cite|url=https://matrix.org/ecosystem/clients/cinny/|title=Matrix client list|author=Matrix.org foundation|year=Unknown|accessdate=2026-05-25}}</ref>. It currently uses the [https://github.com/matrix-org/matrix-js-sdk matrix-js-sdk] but is in the process on replacing it with a custom one, as such, it is not currently accepting contributions<ref>{{Cite|url=https://github.com/cinnyapp/cinny|title=Cinny GitHub repo|author=Cinny contributors|year=2026-05-23|accessdate=2026-05-25}}</ref>. {| class="wikitable" |+Supported features<ref name=":0" /> !Name !Supported? |- |E2EE |Yes |- |Spaces |Yes |- |Voice chat (1:1) |No |- |Voice chat ([[Jitsi]]) |No |- |Voice chat (MatrixRTC) |Yes |- |Threads |No |- |Legacy SSO |Yes |- |Multiple accounts |No |- |Multiple languages |No |} a6078fdadb4bbe0a142df6169ee09b37e78ff97b 0 709 5776 2938 2026-06-17T13:06:17Z Wreckvall 426 /* BIOS */ cleared up some stuff and added post wikitext text/x-wiki This article describes the general boot process of most [[Linux]] distributions.<ref>https://medium.com/@gangulysutapa96/6-stages-of-linux-boot-process-5ee84265d8a0 Medium.com, 2023 (Imported 02.07.25)</ref> While most Linux distributions integrates varying components, the basic steps remain the same. === BIOS === The [[BIOS]] (Basic Input/Output System) is the firmware that activates as soon as the computer is turned on. In the 'Power-on Self Test' (or POST for short), BIOS validates and checks critical hardware components (such as RAM). Additionally, BIOS loads the kernel into memory.<ref>https://www.lenovo.com/gb/en/glossary/what-is-a-bios?srsltid=AfmBOopXGO9x6E-4ZTe5WNDbGEMlTYXBLk1ivYj5LXSQC8OTUAjEAASC Lenovo.com, 2025 (Imported 02.07.2025)</ref> It is obtained from the ROM and is responsible for loading the bootloader. Once the correct boot device is selected, the BIOS loads the boot sector, which is the first sector (512 bytes) of the boot device.<ref>https://neosmart.net/wiki/mbr-boot-process/ Neosmart.net, 2025 (Imported 02.07.2025)</ref> The boot sector contains the bootloader, which is responsible for loading the [[kernel]]. === Bootloader === The bootloader is responsible for loading the kernel into memory and starting the kernel. Common bootloaders include [[GRUB]], [[Syslinux]], [[Limine]], [[Systemd|systemd-boot]], [[rEFInd]], etc. Usually, the bootloader is stored separately from the kernel, in different [[partition]]s or even on a different device. It displays an interface, such as a text-based menu to select the kernel to boot. === Initramfs === The initramfs is a compressed filesystem that is loaded into memory during boot. It contains essential files and utilities required to mount the actual root [[filesystem]] and start the init process. The initramfs is typically created using [[mkinitcpio]] or [[dracut]]. === Kernel === The kernel is the core of the operating system and is responsible for managing hardware resources and providing a platform for user-space applications. It is responsible for initializing hardware, managing memory, and providing a virtual filesystem. It is loaded by the bootloader and starts the init process. === Init === The init process, which must be stored under <code>/sbin/init</code>, is responsible for initializing the system and starting the user-space applications. It is responsible for mounting the root filesystem, starting the necessary system services, and starting the graphical user interface. On most modern systems, this is [[systemd]]. Some older systems use [[sysvinit]] or [[upstart]]. === TTY === The [[TTY]] (Teletype) is a text-based interface that allows users to interact with the operating system. It is responsible for displaying text and accepting user input. It is typically used for logging in and running commands. It is also used for debugging and troubleshooting. The TTY is available even on modern systems and can be accessed through the {{Key press|Ctrl|Alt|F1}} to {{Key press|Ctrl|Alt|F6}} keys. === Display Manager === The [[Display Manager|display manager]] is responsible for managing the [[GUI|graphical user interface]].<ref>https://wiki.archlinux.org/title/Display_manager Arch wiki, 2025 (Imported 02.07.2025)</ref> On most modern systems, this is [[lightdm]], [[gdm]], or [[sddm]]. Once the user logs in, the display manager executes the [[Window Manager|window manager]] or [[Desktop Environments|desktop environment]] chosen by the user. == References == 5931108fbacec593dbcf020981894a1d3b2d3f68 0 905 5777 4137 2026-06-18T16:45:51Z Nathan22211 360 bedrock linux mentions the same issue with ZFS file systems as BTRFS file systems wikitext text/x-wiki {{Guide Warning}} {{DistributionInfobox | title = Bedrock Linux | image = [[File:Bedrock Linux.png|Bedrock_Linux]] | caption = Bedrock Linux Logo | releasestatus = Maintained | packagemanager = [[pmm]] | releasemodel = Meta distribution | usagetype = Desktop/Server | defaultdesktops = None | architectures = x86_64, s390x, ppc64le, ppc64, ppc, mipsel, mips64el, mips, i686, i586, i486, i386, armv7l, armv7hl, aarch64 | website = [https://bedrocklinux.org bedrocklinux.org] }} [[Category:Linux Distributions]] '''Bedrock Linux''' is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. Bedrock integrates these components into one largely cohesive system. <ref>[https://bedrocklinux.org Bedrock Linux Home Page], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> === Distro compatibility === While Bedrock works fine with most distributions, there are distributions which can cause issues with Bedrock. The best examples are:<ref>[https://bedrocklinux.org/0.7/distro-compatibility.html Bedrock Linux 0.7 Poki Distro Support], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> * Distributions that use BSD-like sysvinit * Distributions that use GRUB plus either BTRFS or ZFS file systems (due to a bug in GRUB <ref>[https://bedrocklinux.org/0.7/feature-compatibility.html#grub-btrfs-zfs Grub with BTRFS or ZFS], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref>) * Immutable distributions * Non FHS-compliant distributions like [[NixOS]] or [[GUIX]] === Installation === The Bedrock Linux website provides a hijack script which can be used to convert current Linux distribution to Bedrock Linux <ref>[https://bedrocklinux.org/0.7/installation-instructions.html Installation Instructions], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> === Going through the tutorial === Bedrock Linux provides an interactive tutorial which can be accessed with <code>brl tutorial basics</code>, but also a text version for those who prefer those <ref>[https://bedrocklinux.org/0.7/basic-usage.html Basic Usage], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> === Known issues === ==== brl update and brl fetch fail with proxy ==== With some specific URL's brl fetch and brl update might fail For brl update, possible work-arounds include: * Downloading the update with some other software and providing it as the parameter to brl update * Configuring brl update to use another Bedrock mirror. There are no obvious work-arounds for brl fetch. ==== Unmount warnings on shutdown ==== Those are harmless warnings, which are caused by Bedrock using a Linux kernel feature which propagates some mount and unmount operations, Which causes some init systems to be confused by this and show warnings about being unable to unmount directories because they were already unmounted ==== Root filesystem fsck may be skipped ==== Because of a quirk in how Bedrock works, init systems might not mount the root directory read-only in preparation for fsck, Bedrock does attempt to disable this by changing the corresponding field in <code>/etc/fstab</code> Some initrds will <code>fsck</code> the root filesystem, but not all. Bedrock should offer the option to call <code>fsck</code> on the root filesystem, but it currently does not <ref>[https://bedrocklinux.org/0.7/known-issues.html Known Issues], Bedrock Linux, 2024 (Accessed: 2025-09-12)</ref> == References == <references /> caf29bf06e27ccc4d5a885a97661b400ecdb3966 0 1279 5778 5505 2026-06-18T16:51:02Z Nathan22211 360 /* CNC/Machine Control */ full spectrum features were merged into Snapmaker Orca recently wikitext text/x-wiki = 3D modelling, texturing, and animation = == Modelling == Software for editing, manipulating, and animating 3D models. {| class="wikitable" !Name !External links !Description |- |[[Blender]] |[https://www.blender.org Website],[https://projects.blender.org/blender/blender GitHub] |Industry-standard 3D modelling and 3D animation software |} == Texturing == {| class="wikitable" !Name !External links !Description |- |[[Material Maker]] |[https://www.materialmaker.org/ Website], [https://github.com/RodZill4/material-maker Github] |Node-based procedural texture creation software. Mainly used for 3D models |} == CNC/Machine Control == Software used to control hobbyist and/or industrial machinery. {| class="wikitable" !Name !External Links !Description |- |Orca Slicer |[https://github.com/OrcaSlicer/OrcaSlicer Github] |A modern Slicer for Marlin, Klippper, and RRF 3d printers with a built in web UI viewer. Based on Bambu Studio |- |Prusa Slicer |[https://github.com/prusa3d/PrusaSlicer Github] |A sli3er fork maintained by Prusa Research for thier printers, but supports most other brands as well |- |Pre Flight |[https://github.com/oozebot/preFlight Github] |A Prusa Slicer fork with a modern stack, preproccesing support, CMYK+W painting, and a slew of other features. |- |Snapmaker Orca |[https://github.com/Snapmaker/OrcaSlicer Github] [https://www.snapmaker.com/snapmaker-orca Website] |An Orca Slicer fork meant for snapmaker's U1 toolchanger |- |LaserMagic |[https://lasermagic.ci-yow.com/ Website] |Laser Gcode generator for GBRL compatible Lasers |} dd3324b1cec96bd1c08a99437dec5da08db8e4f6 0 623 5779 4872 2026-06-18T18:50:37Z Wilbur 142 add some missing citations wikitext text/x-wiki {{Cleanup|Citations lack information required in the [[FW:Guidelines#Citations]]}} {{DistributionInfobox | title = EndeavourOS | image = [[File:EndeavourOS Logo.svg|Thumb]] | caption = The Endeavour OS logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[Cinnamon]], [[I3]], [[GNOME]], [[KDE Plasma]], [[LXDE]], [[LXQt]], [[MATE]], [[Xfce]], [[Budgie]] | usagetype = Desktop | architectures = x86_64, AArch64 | website = [https://endeavouros.com endeavouros.com] }} '''EndeavourOS''' is a user-friendly [[Linux Distributions|Linux distribution]] based on [[Arch Linux]]. It aims to provide an easy-to-install Arch-based system with a pre-configured desktop environment, a friendly community, and minimal modifications to upstream Arch.<ref name=":0">[https://endeavouros.com/ Home - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> === History === EndeavourOS was launched in July 2019 as a spiritual successor to [[Antergos]], another Arch-based distribution that was discontinued.<ref>[https://endeavouros.com/about-us/ About us - EndeavourOS], EndeavourOS, 2021-08-09 (Accessed: 2025-08-09)</ref> The project was created to provide a similar experience with a focus on simplicity, community, and learning [[Arch Linux]] fundamentals. === Installation === EndeavourOS provides an ISO with the [[Calamares]] installer, offering both offline (Plasma only) and online installation modes. The online mode allows users to select their preferred desktop environment and additional packages.<ref>{{Cite|url=https://discovery.endeavouros.com/installation/customizing-the-endeavouros-install-process/2022/03/|title=Customizing the EndeavourOS install process|author=Manuel|year=2022|accessdate=2026-06-18}}</ref> === Arch Compatibility === [[File:EndeavourOS 21.4 screenshot.png|thumb|Screenshot of EndeavourOS 21.4]] EndeavourOS is fully compatible with [[Arch Linux]], meaning it uses Arch's official repositories directly and adheres closely to Arch's philosophy of simplicity and user control. It does not repackage software or maintain separate downstream packages, unlike some Arch-based distributions. ==== Key Points of Compatibility: ==== * Shared Repositories: EndeavourOS uses the same "core", "extra", and "multilib" (32-bit) repositories as Arch Linux. * [[AUR]] Support: The Arch User Repository (AUR) is available by default, and tools like [[yay]] are pre-installed to facilitate [[AUR]] package management.<ref>{{Cite|url=https://discovery.endeavouros.com/aur/faq-what-is-the-aur/2021/03/|title=[FAQ] What is the AUR?|author=EndeavourOS|year=2021|accessdate=2026-06-18}}</ref> * Rolling Release: Follows Arch's rolling-release model, receiving updates as soon as they are pushed upstream. * [[Pacman]] Compatibility: Fully compatible with Arch's [[pacman]] package manager and its tooling ecosystem.<ref>{{Cite|url=https://discovery.endeavouros.com/pacman/pacman-basic-commands/2021/03/|title=Pacman basic commands|author=Bryanpwo|year=2021|accessdate=2026-06-18}}</ref> Because of this alignment, most documentation and guides written for [[Arch Linux]] are directly applicable to EndeavourOS, making it ideal for users who want to learn and eventually transition to vanilla [[Arch]], or simply want a more user-friendly Arch experience out of the box. ==== Respositories ==== EndeavourOS relies on Arch Linux's mirror network for most packages, supplemented by a small respository (which can be viewed [https://repo.c48.uk/endeavouros/repo/endeavouros/ here]) that houses a few packages from the [[AUR]], as well as EndeavourOS-specific themes and utilities.<ref>[https://repo.c48.uk/endeavouros/repo/endeavouros/ Index of /endeavouros/repo/endeavouros/] (Accessed: 2025-08-09)</ref> This is simply a [[pacman]] repository that can simply be added to any [[Arch Linux]] system if desired. == References == 76d282c2677669602076f8c42671bf416531db1b 0 516 5780 3679 2026-06-18T20:18:48Z Hyperreal 388 Separate intructions into Guide wikitext text/x-wiki {{Cleanup|Instructions should be seperated into its own Guide page}} {{Needs_Citations}} Systemd is an init system and service manager used by many modern [[Linux Distributions|Linux distributions]]. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here's how Systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': Systemd provides a unified system for managing services, devices, logs, and network interfaces. * '''Dependency Management''': Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': Systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in Systemd == Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit's dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''Systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''Systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''Systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential Systemd Commands == Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. a3be3dec22d172b9e3d0e8dfb0f95f7264f3f8ab 5789 5780 2026-06-18T21:01:07Z Hyperreal 388 Add website and manpages as references wikitext text/x-wiki Systemd<ref>[https://systemd.io/ systemd.io], SystemD contributors (Accessed 2026-06-18)</ref> is an init system and service manager used by many modern [[Linux Distributions|Linux distributions]]. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == Systemd was developed as a more efficient and flexible replacement for the traditional SysVinit system. Here's how Systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': Systemd provides a unified system for managing services, devices, logs, and network interfaces. * '''Dependency Management''': Systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': Systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in Systemd == Systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit's dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''Systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''Systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''Systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential Systemd Commands == Welcome to the handy world of Systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands<ref>[https://www.freedesktop.org/software/systemd/man/latest/index.html systemd manpages], FreeDesktop.org contributors (Accessed 2026-06-18)</ref>: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. 828231b1eac46cc2f06937a7a32a606bef4f6305 5800 5789 2026-06-21T11:23:47Z Madonuko 140 add softwareinfobox wikitext text/x-wiki [[Category:Software]] {{stub}}{{SoftwareInfobox | title = systemd | releasestatus = Maintained | lastrelease = v261 (2026-06-20) | languages = [[C]] | developers = systemd developers | website = [https://systemd.io systemd.io] | license = GPL-2.0-or-later AND LGPL-2.1-or-later | sourcecode = https://github.com/systemd/systemd | image = [[File:Systemd-logo.svg|frameless]] | caption = systemd logo }} systemd<ref>[https://systemd.io/ systemd.io], systemd contributors (Accessed 2026-06-18)</ref> is an init system and service manager used by many modern [[Linux Distributions|Linux distributions]]. It is designed to initialize the system, manage system services, and maintain system resources. Systemd replaces the older SysVinit system, providing more advanced features and parallelization, leading to faster boot times and better system management. At the core of systemd's operation are '''units''', which represent resources or services that systemd manages. Each unit is defined by a '''unit file''', which specifies its behavior, configuration, and how it interacts with other units. == Why Systemd? == systemd was developed as a more efficient and flexible replacement for the traditional [[SysVinit]] system. Here's how systemd differs: * '''Parallel Startup''': Unlike SysVinit, which starts services sequentially, systemd starts services in parallel, drastically improving boot times. * '''Centralized Management''': systemd provides a unified system for managing services, devices, logs, and network interfaces. * '''Dependency Management''': systemd can handle service dependencies, ensuring services are started in the correct order and restarted when necessary. * '''Logging''': systemd integrates a powerful logging system, the '''journal''', which makes it easier to manage and analyze logs. == Key Concepts in systemd == systemd is designed around several key concepts that work together to provide efficient system and service management. Understanding these components is essential to effectively manage your system. Here's a breakdown of the core elements: * '''Unit''': A unit is the fundamental resource managed by systemd. It represents anything that systemd manages, such as a service, a mount point, or a socket. Each unit is described by a '''unit file''', which defines how it should behave and interact with other components. * '''Unit File''': Unit files are the configuration files that tell systemd how to manage a specific unit. These files include information about the unit's dependencies, execution order, and resource requirements. Unit files are typically found in directories such as `/etc/systemd/system/` or `/lib/systemd/system/`. * '''Service''': A service is a specific type of unit that represents a background process or daemon. Services could be network daemons, database servers, or any other long-running processes. Service units are used to control how these processes are started, stopped, and managed by systemd. * '''Target''': Targets are special unit types used to group other units together. For instance, the `graphical.target` is a target unit that defines the state where the system is ready to launch the graphical user interface (GUI). Targets are commonly used to organize the system's startup process by defining different runlevels or system states. * '''systemd Init''': The first process launched by the Linux kernel when the system starts, systemd init is responsible for initializing the system and starting the systemd daemon, which in turn manages all system processes. * '''systemd Daemon''': The heart of systemd, the systemd daemon oversees system services and resources, ensuring everything runs smoothly and that dependencies are respected. It monitors the system continuously, acting to resolve issues or restart services when necessary. * '''systemd Journal''': A powerful logging system, the systemd journal collects logs from various system components, services, and applications. It centralizes system events, errors, and warnings, providing an easy way to troubleshoot issues. The journal simplifies log management, making it easier to track system activity and diagnose problems. == Essential systemd Commands == Welcome to the handy world of systemd commands! Whether you're just starting out or you're a seasoned user, these commands will help you effectively manage services, processes, and resources on your Linux system. Here are some of the most commonly used Systemd commands<ref>[https://www.freedesktop.org/software/systemd/man/latest/index.html systemd manpages], FreeDesktop.org contributors (Accessed 2026-06-18)</ref>: * '''systemctl''': This command is your go-to for managing services. You can start, stop, restart, enable, and disable services with ease. * '''journalctl''': Use this command to view system logs stored in the Systemd Journal. It offers a detailed overview of system events and errors, making troubleshooting simpler. * '''timedatectl''': This command helps you manage the system's date and time settings. You can easily set the time zone, date, and time as needed. * '''hostnamectl''': With this command, you can manage your system's hostname. It allows you to set the hostname, domain name, and static hostname effortlessly. * '''networkctl''': This command is useful for managing network interfaces. You can check the status and configuration of your network interfaces quickly. == References == fc1a16427816821a52c26a58b82a6d5cdb5987ce 3000 1357 5781 2026-06-18T20:32:01Z Hyperreal 388 Separate instructions into Guide wikitext text/x-wiki == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash">systemctl start service-name</syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash">systemctl stop service-name</syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash">systemctl restart service-name</syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash">systemctl enable service-name</syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash">systemctl disable service-name</syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the `/lib/systemd/system/` directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there. * Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. '''Runtime Directory''' The `/run/systemd/system/` directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.service </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.timer </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer <syntaxhighlight lang="bash"> sudo systemctl enable daily-script.timer sudo systemctl start daily-script.timer </syntaxhighlight> 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: <syntaxhighlight lang="bash"> systemctl list-timers </syntaxhighlight> This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With <code>OnCalendar</code>, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from <code>/lib/systemd/system/</code> to <code>/etc/systemd/system/</code> and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with <code>.d</code>. Example: To modify <code>dummy.service</code>, create a folder named <code>dummy.service.d</code> in <code>/etc/systemd/system/</code>. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a <code>.conf</code> file to specify your changes. Example: <code>/etc/systemd/system/dummy.service.d/custom.conf</code>. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. <code>/etc/systemd/system/</code> (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. <code>/run/systemd/system/</code> (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. <code>/lib/systemd/system/</code> (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. <code>systemctl status service-name</code> * Displays the status of a specific service, including whether it's running and any associated error messages. 2. <code>journalctl -u service-name</code> * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. <code>systemctl list-units --failed</code> * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. <code>systemctl daemon-reload</code> * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. bddeab0edd03e783d71337e369861617953b34d3 5782 5781 2026-06-18T20:32:42Z Hyperreal 388 wikitext text/x-wiki {{Guide Warning}} == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash">systemctl start service-name</syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash">systemctl stop service-name</syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash">systemctl restart service-name</syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash">systemctl enable service-name</syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash">systemctl disable service-name</syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the `/lib/systemd/system/` directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the `/etc/systemd/system/` directory and apply your modifications there. * Unit files located in this directory take precedence over those in `/lib/systemd/system`, allowing for user-specific configurations. 3. '''Runtime Directory''' The `/run/systemd/system/` directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the `systemctl snapshot` command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.service </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.timer </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer <syntaxhighlight lang="bash"> sudo systemctl enable daily-script.timer sudo systemctl start daily-script.timer </syntaxhighlight> 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: <syntaxhighlight lang="bash"> systemctl list-timers </syntaxhighlight> This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With <code>OnCalendar</code>, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from <code>/lib/systemd/system/</code> to <code>/etc/systemd/system/</code> and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with <code>.d</code>. Example: To modify <code>dummy.service</code>, create a folder named <code>dummy.service.d</code> in <code>/etc/systemd/system/</code>. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a <code>.conf</code> file to specify your changes. Example: <code>/etc/systemd/system/dummy.service.d/custom.conf</code>. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. <code>/etc/systemd/system/</code> (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. <code>/run/systemd/system/</code> (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. <code>/lib/systemd/system/</code> (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. <code>systemctl status service-name</code> * Displays the status of a specific service, including whether it's running and any associated error messages. 2. <code>journalctl -u service-name</code> * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. <code>systemctl list-units --failed</code> * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. <code>systemctl daemon-reload</code> * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. ef1ed7e556ccdb275fc8d658018e4d1aa9c63666 5783 5782 2026-06-18T20:35:45Z Hyperreal 388 Fix syntax formatting wikitext text/x-wiki {{Guide Warning}} == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash"> systemctl start service-name </syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash"> systemctl stop service-name </syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash"> systemctl restart service-name </syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash"> systemctl enable service-name </syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash"> systemctl disable service-name </syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the <code>/lib/systemd/system/</code> directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the <code>/etc/systemd/system/</code> directory and apply your modifications there. * Unit files located in this directory take precedence over those in <code>/lib/systemd/system</code>, allowing for user-specific configurations. 3. '''Runtime Directory''' The <code>/run/systemd/system/</code> directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the <code>systemctl snapshot</code> command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.service </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.timer </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer <syntaxhighlight lang="bash"> sudo systemctl enable daily-script.timer sudo systemctl start daily-script.timer </syntaxhighlight> 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: <syntaxhighlight lang="bash"> systemctl list-timers </syntaxhighlight> This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With <code>OnCalendar</code>, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from <code>/lib/systemd/system/</code> to <code>/etc/systemd/system/</code> and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with <code>.d</code>. Example: To modify <code>dummy.service</code>, create a folder named <code>dummy.service.d</code> in <code>/etc/systemd/system/</code>. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a <code>.conf</code> file to specify your changes. Example: <code>/etc/systemd/system/dummy.service.d/custom.conf</code>. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. <code>/etc/systemd/system/</code> (highest priority for customizations) * This is where you should place custom or modified unit files. They override the default system unit files. 2. <code>/run/systemd/system/</code> (temporary, session-specific changes) * This directory holds runtime unit files that are created dynamically. These changes will not persist after a reboot. 3. <code>/lib/systemd/system/</code> (default system unit files) * This directory contains the default unit files installed by packages. Changes made here should be avoided, as they may be replaced by updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: 1. <code>systemctl status service-name</code> * Displays the status of a specific service, including whether it's running and any associated error messages. 2. <code>journalctl -u service-name</code> * Displays the logs for a specific service, making it easy to track down issues that may have occurred. 3. <code>systemctl list-units --failed</code> * Lists all failed units, which is useful for identifying problems with services or other system resources. 4. <code>systemctl daemon-reload</code> * Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. * This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. 080cb630b7d5a4dabecea055381ab0a1ccb99b39 5785 5783 2026-06-18T20:45:57Z Hyperreal 388 Restructure Precedence of Directories and Troubleshooting Systemd wikitext text/x-wiki {{Guide Warning}} == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash"> systemctl start service-name </syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash"> systemctl stop service-name </syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash"> systemctl restart service-name </syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash"> systemctl enable service-name </syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash"> systemctl disable service-name </syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the <code>/lib/systemd/system/</code> directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the <code>/etc/systemd/system/</code> directory and apply your modifications there. * Unit files located in this directory take precedence over those in <code>/lib/systemd/system</code>, allowing for user-specific configurations. 3. '''Runtime Directory''' The <code>/run/systemd/system/</code> directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the <code>systemctl snapshot</code> command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.service </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.timer </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer <syntaxhighlight lang="bash"> sudo systemctl enable daily-script.timer sudo systemctl start daily-script.timer </syntaxhighlight> 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: <syntaxhighlight lang="bash"> systemctl list-timers </syntaxhighlight> This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With <code>OnCalendar</code>, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from <code>/lib/systemd/system/</code> to <code>/etc/systemd/system/</code> and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with <code>.d</code>. Example: To modify <code>dummy.service</code>, create a folder named <code>dummy.service.d</code> in <code>/etc/systemd/system/</code>. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a <code>.conf</code> file to specify your changes. Example: <code>/etc/systemd/system/dummy.service.d/custom.conf</code>. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: {| class="wikitable" |- ! Directory !! Purpose |- | <code>/etc/systemd/system/</code> || Highest priority for customizations. This is where you should place custom or modified unit files. They override the default system unit files. |- | <code>/run/systemd/system/</code> || Temporary, session-specific changes. This directory holds runtime unit files that are created dynamically. Changes made here will not persist after a reboot. |- | <code>/lib/systemd/system/</code> || Default system unit files. This directory contains the default unit files installed by packages. One should avoid making changes here, as they may be replaced by package updates. |} == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: * <code>systemctl status service-name</code>: Displays the status of a specific service, including whether it's running and any associated error messages. * <code>journalctl -u service-name</code>: Displays the logs for a specific service, making it easy to track down issues that may have occurred. * <code>systemctl list-units --failed</code>: Lists all failed units, which is useful for identifying problems with services or other system resources. * <code>systemctl daemon-reload</code>: Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. 8d73254424fe7d53497e102614cb085047825b0c 5787 5785 2026-06-18T20:47:22Z Hyperreal 388 /* Precedence of Directories */ wikitext text/x-wiki {{Guide Warning}} == Getting Started with Systemd == Systemd is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash"> systemctl start service-name </syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash"> systemctl stop service-name </syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash"> systemctl restart service-name </syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash"> systemctl enable service-name </syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash"> systemctl disable service-name </syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the <code>/lib/systemd/system/</code> directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the <code>/etc/systemd/system/</code> directory and apply your modifications there. * Unit files located in this directory take precedence over those in <code>/lib/systemd/system</code>, allowing for user-specific configurations. 3. '''Runtime Directory''' The <code>/run/systemd/system/</code> directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the <code>systemctl snapshot</code> command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.service </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.timer </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer <syntaxhighlight lang="bash"> sudo systemctl enable daily-script.timer sudo systemctl start daily-script.timer </syntaxhighlight> 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: <syntaxhighlight lang="bash"> systemctl list-timers </syntaxhighlight> This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With <code>OnCalendar</code>, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from <code>/lib/systemd/system/</code> to <code>/etc/systemd/system/</code> and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with <code>.d</code>. Example: To modify <code>dummy.service</code>, create a folder named <code>dummy.service.d</code> in <code>/etc/systemd/system/</code>. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a <code>.conf</code> file to specify your changes. Example: <code>/etc/systemd/system/dummy.service.d/custom.conf</code>. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. <code>/etc/systemd/system/</code>: Highest priority for customizations. This is where you should place custom or modified unit files. They override the default system unit files. 2. <code>/run/systemd/system/</code>: Temporary, session-specific changes. This directory holds runtime unit files that are created dynamically. Changes made here will not persist after a reboot. 3. <code>/lib/systemd/system/</code>: Default system unit files. This directory contains the default unit files installed by packages. One should avoid making changes here, as they may be replaced by package updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: * <code>systemctl status service-name</code>: Displays the status of a specific service, including whether it's running and any associated error messages. * <code>journalctl -u service-name</code>: Displays the logs for a specific service, making it easy to track down issues that may have occurred. * <code>systemctl list-units --failed</code>: Lists all failed units, which is useful for identifying problems with services or other system resources. * <code>systemctl daemon-reload</code>: Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. 455d44700ed16711c7d0a0b5bed5df5d481d63bb 5788 5787 2026-06-18T20:49:08Z Hyperreal 388 Add link to SystemD article wikitext text/x-wiki {{Guide Warning}} == Getting Started with Systemd == [[Systemd]] is the default init system for many popular Linux distributions, including Debian, Ubuntu, and Red Hat. It provides powerful tools for managing services, processes, and resources. Here are some practical examples of how to use Systemd commands effectively: === Managing Services === 1. '''Starting a Service''': To start a service, use the following command: <syntaxhighlight lang="bash"> systemctl start service-name </syntaxhighlight> 2. '''Stopping a Service''': To stop a running service, use: <syntaxhighlight lang="bash"> systemctl stop service-name </syntaxhighlight> 3. '''Restarting a Service''': To restart a service, use: <syntaxhighlight lang="bash"> systemctl restart service-name </syntaxhighlight> 4. '''Enabling a Service''': To ensure a service starts automatically at boot, use: <syntaxhighlight lang="bash"> systemctl enable service-name </syntaxhighlight> 5. '''Disabling a Service''': To prevent a service from starting at boot, use: <syntaxhighlight lang="bash"> systemctl disable service-name </syntaxhighlight> == What Are Units? == Units are standardized representations of system resources such as services, devices, or timers. These unit files dictate how systemd manages these resources. === Where Are Unit Files Stored? === 1. '''System Directory''' The primary location for system-wide unit files is the <code>/lib/systemd/system/</code> directory. * This is where unit files are automatically installed when software packages are added to the system. * '''Important''': Do not modify files in this directory, as they may be replaced during software updates. 2. '''Custom Directory''' To customize or override the behavior of a unit, copy its unit file to the <code>/etc/systemd/system/</code> directory and apply your modifications there. * Unit files located in this directory take precedence over those in <code>/lib/systemd/system</code>, allowing for user-specific configurations. 3. '''Runtime Directory''' The <code>/run/systemd/system/</code> directory is used for temporary unit file changes during system operation. * Files in this directory are created dynamically at runtime and can temporarily override other unit files for the current session. * '''Note''': Any changes made here are not saved and will be lost after a system reboot. === Types of Units === The suffix of a unit file indicates the type of service or functionality it provides. Below is a table of common unit types and their functions: {| class="wikitable" |+ Common Unit Types |- ! Suffix !! Function |- | .automount || Automatically mounts a specified file system when accessed, requiring a corresponding .mount unit. |- | .device || Manages and monitors hardware devices recognized by the system, such as those detected by udev or sysfs. |- | .mount || Defines a specific mount point for file systems, with units named according to the mount path. |- | .path || Specifies a file system path that triggers activation of other units when changes are detected. |- | .scope || Created by systemd to manage groups of processes based on information from system bus interfaces. |- | .service || Controls the execution of system services or applications, handling their lifecycle and dependencies. |- | .slice || Organizes and manages resource allocation for processes using Linux Control Groups (cgroups). |- | .socket || Defines a socket for inter-process communication (IPC) or network connections, facilitating service activation. |- | .snapshot || Represents a point-in-time capture of the system state, created when the <code>systemctl snapshot</code> command is run. |- | .swap || Describes the swap space used by the system for memory management, allowing for temporary data storage. |- | .target || Groups other units to synchronize their startup or shutdown during system boot or state transitions. |- | .timer || Manages scheduled tasks and events, allowing for periodic execution of services or actions. |} == Systemd Timers: A Replacement for Cron Jobs == Systemd timers can replace traditional cron jobs for scheduling tasks. They offer more flexibility and integration with systemd services. Example: Running a Script Daily 1. Create a Service File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.service </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily [Service] ExecStart=/path/to/your/script.sh </syntaxhighlight> 2. Create a Timer File <syntaxhighlight lang="bash"> sudo nano /etc/systemd/system/daily-script.timer </syntaxhighlight> Contents: <syntaxhighlight lang="ini"> [Unit] Description=Run script daily at midnight [Timer] OnCalendar=daily [Install] WantedBy=timers.target </syntaxhighlight> 3. Enable and Start the Timer <syntaxhighlight lang="bash"> sudo systemctl enable daily-script.timer sudo systemctl start daily-script.timer </syntaxhighlight> 4. Verify the Timer To verify that your timer is active and running as scheduled, use the following command: <syntaxhighlight lang="bash"> systemctl list-timers </syntaxhighlight> This command will display all active timers, including their next scheduled activation time and how long ago they last ran. It also provides information about the associated unit files. With <code>OnCalendar</code>, you can specify various schedules such as weekly, hourly, or custom times. For example: * '''weekly''': A timer that triggers once a week. * '''hourly''': A timer that triggers once every hour. * Custom times, such as "Mon *-* * 10:00:00" for a Monday execution at 10:00 AM. == How to Modify a Unit File? == === Full Customization === If you want to fully customize a unit, you should copy the desired unit file from <code>/lib/systemd/system/</code> to <code>/etc/systemd/system/</code> and modify it as needed. For example: <syntaxhighlight lang="bash"> sudo cp /lib/systemd/system/dummy.service /etc/systemd/system/ sudo nano /etc/systemd/system/dummy.service </syntaxhighlight> === Partial Changes === If you only need to change a specific directive in a unit file without copying the entire file, you can use the following method: 1. Create a directory named after the unit file, ending with <code>.d</code>. Example: To modify <code>dummy.service</code>, create a folder named <code>dummy.service.d</code> in <code>/etc/systemd/system/</code>. <syntaxhighlight lang="bash"> sudo mkdir /etc/systemd/system/dummy.service.d </syntaxhighlight> 2. Inside this folder, create a <code>.conf</code> file to specify your changes. Example: <code>/etc/systemd/system/dummy.service.d/custom.conf</code>. <syntaxhighlight lang="ini"> [Service] ExecStartPre=/path/to/custom/script.sh </syntaxhighlight> This method allows you to add specific configuration changes without overriding the entire unit file. == Precedence of Directories == When systemd processes unit files, it prioritizes directories in the following order: 1. <code>/etc/systemd/system/</code>: Highest priority for customizations. This is where you should place custom or modified unit files. They override the default system unit files. 2. <code>/run/systemd/system/</code>: Temporary, session-specific changes. This directory holds runtime unit files that are created dynamically. Changes made here will not persist after a reboot. 3. <code>/lib/systemd/system/</code>: Default system unit files. This directory contains the default unit files installed by packages. One should avoid making changes here, as they may be replaced by package updates. == Troubleshooting Systemd == Systemd provides several ways to troubleshoot and diagnose problems with services and units: * <code>systemctl status service-name</code>: Displays the status of a specific service, including whether it's running and any associated error messages. * <code>journalctl -u service-name</code>: Displays the logs for a specific service, making it easy to track down issues that may have occurred. * <code>systemctl list-units --failed</code>: Lists all failed units, which is useful for identifying problems with services or other system resources. * <code>systemctl daemon-reload</code>: Reloads the systemd manager configuration, which is helpful after editing or adding new unit files. This command ensures that systemd is aware of any changes made to unit files without requiring a reboot. 11b166b3231ec221d9165ee2d6c7debe81bc4405 0 319 5784 3670 2026-06-18T20:45:38Z Nathan22211 360 Added some ricing steps. This 100% needs more refinement than I can think of and maybe some things moved to other parts of the wiki. wikitext text/x-wiki [[Category:Terminology]] {{Needs Citations}}'''Ricing''' (''slang'') refers to extensively customizing a [[Desktop Environment|desktop environment]] or [[Window Manager|window manager]] to create a unique, personalized computing experience. The term originated from the automotive modification scene ("ricer" cars) and has been adopted by the Linux/Unix community. While primarily focused on aesthetic customization through themes, colors, widgets, and interface layouts, ricing can improve functionality and performance. Common ricing elements include: * Custom window borders, titlebars, decorations; * Color schemes and typography; * Specialized status bars and system monitors; * Custom application launchers and menus * Personalized desktop widgets and notifications * Modified system icons and cursors Popular tools for ricing include customization frameworks such as polybar and picom for window managers like i3, bspwm, and dwm. People frequently share configuration files, or "dotfiles," and screenshots - [https://www.reddit.com/r/unixporn/ r/unixporn] is one of the most popular. == Getting Started: Basics == For most of these tools, you'll want a compositor that uses wl-roots, Smithy, aquamarine (hyprland,) or Mir. GNOME and Cinnamon don't support the protocals needed for many of these tools, KDE supports some of them. do note, it's a general assumption that CSS is used for styling and color with everything listed below. We won't go into how each program is configured on this page specifically. Please refer to any guides put out by the developers or elsewhere in this wiki. === Compositors === Please refer to [[Wayland Compositors]] or [[X Window Managers]] for various compositors that are available. Wayland is typically recommended for compatibility with newer hardware and software. === Frameworks === these are general purpose frameworks that can be used to create anything you can imagine. It'd be best to look at existing dotfiles that use these frameworks if you don't fully understand how to use them and/or their languages, as they're comparatively more advanced than the specific purpose utilities listed later. {| class="wikitable" |+Wayland !Framework !Links !Language(s) !Description |- |Eww |[https://elkowar.github.io/eww/eww.html Website] |Yuck | |- |Ewwii |[https://ewwii-sh.github.io/ Website] |nbcl, yuck (yucky-ewwii) | |- |Fabric |[https://wiki.ffpy.org/ Website] |Python | |- |weLD |[https://github.com/fjueic/WeLD Github] |Python, web frameworks e.g. Javascript, React. | |- |ags |[https://aylur.github.io/ags/ Website] |JSX | |- |Chunks |[https://github.com/sashk4/chunks-rs Github] |Rust | |- |Quickshell |[https://quickshell.org/ Website] |QML | |} === Bars === Ideally you'll want at least one of these assuming you're not using a framework for your own bar. A bar will allow you to have a HUD on your battery; if your device has one; opened applications, and access to clickable shortcuts you; or the dotfile maker; programs in. KDE has one built in if you decided to use it. {| class="wikitable" |+Wayland !Bar !Links !Languages !Description |- |Waybar |[https://github.com/alexays/waybar Github] |JSON5 | |- |Ironbar |[https://github.com/jakestanger/ironbar Github] |JSON, YAML, TOML, Corn | |} === Set up === once you've made your choice(s) and set up your configs and scripts. You'll want to make them run at startup on your compositor. You can do that with the autostart methods for your chosen compositor/window manager. The 'how' varies between them and how they're configured. 721ea7f94ca5ddb9ae1c2e0c5b7de93de9879a64 0 1358 5786 2026-06-18T20:46:05Z Uniolo 345 Redirect to XMPP wikitext text/x-wiki #redirect [[XMPP]] 5e978e34231c5a0b7369f2487cf644867772dc82 0 1359 5790 2026-06-19T13:32:39Z Uniolo 345 Redirect to NixOS wikitext text/x-wiki #redirect [[NixOS]] 1f2516623cbe104899c67a9f07e0e5fd6b109db4 0 171 5791 5224 2026-06-19T13:34:19Z Uniolo 345 Added the year in which the "Change of Leadership" controversy took place. wikitext text/x-wiki [[Category:Linux Distributions]] {{DistributionInfobox | title = NixOS | image = [[File:Nix snowflake.svg|frameless|150px]] | caption = The NixOS logo; also a symbol of the Nix package manager | releasestatus = Actively maintained | releasemodel = New release every six months, with optional unstable branch | packagemanager = [https://nixos.org Nix package manager] | defaultdesktops = GNOME, [[KDE Plasma]] | usagetype = Desktop, Server | architectures = i686, x86_64, aarch64 | website = [https://nixos.org nixos.org] }} '''NixOS''' is a [[Linux Distributions|Linux distribution]] built around the '''Nix''' [[Package Manager|package manager]], offering features such as atomic upgrades, rollbacks, and a declarative configuration model.<ref>https://nixos.org/manual/nixos/stable/index.html#sec-intro Official NixOS manual, 2025 (Imported 4th June 2024)</ref> It was initially developed by Eelco Dolstra.<ref>https://edolstra.github.io/pubs/phd-thesis.pdf NixOS Thesis, 2025 (Imported 4th June 2024)</ref> Introducing new methods for system management, such as nixos-rebuild & [[nix-shell]]. Powered by a central configuration language and source, your configuration.nix or flake. Enabling your system to be fully reproducible and version locked. === Home Manager === Home Manager is a NixOS module for configuring user environments in <code>/home</code>, often integrated directly into NixOS to enable unified system and user-level rebuilds. It provides a broad range of options beyond standard NixOS configurations, allowing users to manage dotfiles, install and configure applications, and customize environment settings for a tailored, reproducible setup.[[File:Nixos-desktop.jpg|thumb|A NixOS desktop running GNOME 43.1 with Neofetch displayed.]] === Flakes === '''[https://wiki.nixos.org/wiki/Flakes Flakes]''' are an experimental (But mostly stable and trusted) feature of the Nix package manager aimed at simplifying dependency and configuration management, making builds more reproducible and shareable across environments. * Flakes provide a standardized format for specifying dependencies, configurations, and sources, enabling easier integration and consistency across systems. * Using Flakes, developers can define isolated and reproducible environments, ideal for both development and deployment. === Disko === [https://github.com/nix-community/disko Disko] is a NixOS module for configuring disk layouts and their partitions. It facilitates the quick and easy installation of NixOS on systems with the same disk setup. === Lix === [https://lix.systems Lix] is a community fork of Nix. It uses the Meson build system, though the Lix team also plans to gradually introduce Rust to the source code.<ref name=":0">https://lix.systems/about/#why-lix Official Lix Website, 2025 (Imported 4th June 2024)</ref> The project also aims to evolve the Nix language into the new Lix language—maintaining general syntactic compatibility with Nix but introducing refinements and new features.<ref name=":0" /> === Controversy === ==== Anduril Sponsorship ==== NixCon 2023, a community conference dedicated to the Nix project, received a sponsorship from Anduril, a U.S.-based military defense contractor. Upon learning of the sponsorship, the event venue, TU Darmstadt, requested additional information from the Nix Foundation to assess whether the sponsorship aligned with its policies. In response, the Nix Foundation ultimately decided to withdraw Anduril's sponsorship.<ref>https://discourse.nixos.org/t/nixcon-2023-sponsorship-situation-from-the-nixos-foundation/33583 NixOS statement ,2023 (Imported 4th June 2024)</ref> ==== Change of Leadership ==== In 2024, following an open letter criticizing the Nix Foundation and calling for the resignation of Eelco Dolstra, he eventually stepped down.<ref>https://save-nix-together.org{{Dead Link|2025-08-14|Cannot connect to host save-nix-together.org:443 ssl:default [Connect call failed ('35.220.189.138', 443)]}} NixOS fundraiser, 2024 (Imported 4th June 2024)</ref><ref name=":1">https://mastodon.delroth.net/@delroth/112450680035780629 Mastodon, 2024 (Imported 4th June 2024)</ref> After his resignation, a new board was established. Their first action was to lift the ban on a controversial user from the Nixpkgs contributor Zulip chat, sparking further debate.<ref name=":1" /> === Trivia === * NixOS employs a purely functional approach to package management, ensuring that package installations remain isolated from one another. * The Nix package manager supports reproducible builds, making it especially suited for consistent and reliable development environments. == References == <references /> b9c9f07b19e22f9f80513b9ebda5c1d970875189 0 700 5792 3590 2026-06-19T16:06:07Z Satnus 215 Switched out the logo to the proper one wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Calamares Logo.png|200px]] | caption = Calamares Installer | title = Calamares | releasestatus = Maintained | lastrelease = 3.3.14 (Feb 20, 2025) | languages = [[C++]], [[Python]], [[QML]] | developers = Adriaan de Groot | website = [https://calamares.io/ calamares.io], [https://calamares.codeberg.page/ calamares.codeberg.page] (temporarily) }} [[File:Calamares on Debian 10 screenshot.jpg|thumb|Calamares on Debian]] Calamares is a distribution-independent system installer, with an advanced partitioning feature for both manual and automated partitioning operations. Calamares is designed to be customizable by distribution maintainers without the need for cumbersome patching, thanks to third-party branding and external modules support.<ref>https://github.com/calamares/calamares Calamares Github, 2025 (27th June 2025)</ref> == References == <references /> 658931997d6b4224b197e0996685d8f6c1f77343 6 1360 5793 2026-06-19T21:37:27Z Lawl 419 The Limine logo wikitext text/x-wiki == Summary == The Limine logo e8e30173650db6cead1ff3a880acb411349aeff7 0 1361 5794 2026-06-19T21:38:16Z Lawl 419 write most of limine page, needs installation instructions writing wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |caption=The Limine logo |developers=Mintsuki and contributors |firstrelease=v0.01 |languages=[[C]], [[Assembly]] |lastrelease=V12.3.3 |title=Limine |website=https://limine-bootloader.org |releasestatus=Maintained |image= [[File:Limine-logo.png|200px|alt=The Limine logo, a blocky purple L.|Limine logo]] }} Limine is a modern, secure, portable, multiprotocol bootloader and boot manager, also used as the reference implementation for the Limine boot protocol.<ref>[https://github.com/limine-bootloader/limine Official Limine Github repository]</ref> It supports the [[ISO-9660]] and [[FAT]] filesystems. Limine aims to provide a solid, secure and robust alternative to larger bootloaders such as [[GNU]]'s [[GRUB]]. Limine also provides its own boot protocol as an alternative to the [[Multiboot specification]]<ref>[https://en.wikipedia.org/wiki/Limine_(bootloader) Wikipedia entry on Limine]</ref>, with the goal of reducing the amount of work needed for a kernel developer to get a workable 64-bit environment once booted.<ref>[https://limine-bootloader.org/ Limine's website]</ref> Albeit smaller and less adapted than its alternatives, Limine is used by several [[Linux]] distributions, such as [[Dérive Linux]], [[Chimera Linux]]<ref>[https://linuxiac.com/chimera-linux-introduces-key-bootloader-changes/ Linuxiac page on Chimera bootloader changing to Limine]</ref> and [[CachyOS]]<ref>[https://linuxiac.com/cachyos-march-2025-release-brings-limine-bootloader/ Linuxiac page on CachyOS bootloader changing to Limine]</ref>. 73e946888d6d1e6fa621e1b9c467bfe265a31f67 0 1176 5795 5292 2026-06-19T21:43:54Z Lawl 419 add links to other foss wiki pages wikitext text/x-wiki {{DistributionInfobox | title = Chimera Linux | image = [[File:Chimera_Linux_logo.svg|200px|Chimera Linux logo]] | caption = The Chimera Linux logo | releasestatus = Maintained | releasemodel = Rolling | packagemanager = [[Apk]] | defaultdesktops = [[GNOME]], [[Terminal User Interface]] [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64, ppc, ppc64, ppc64le, aarch64, riscv64 | website = [https://chimera-linux.org/ chimera-linux.org] }} '''Chimera Linux''' is an independent, general-purpose, rolling-release Linux distribution developed from scratch. It utilizes a FreeBSD-based userland, [[Musl]] C library and the LLVM toolchain, along with the [[Dinit]] service manager. Its primary focus is correctness, consistency and simplicity, but not at the expense of feature set; its primary desktop environment is [[GNOME]].<ref>{{Cite|url=https://chimera-linux.org/docs/|title=Chimera Linux Documentation|author=The Chimera Project|accessdate=5/25/26}}</ref> == Key elements in the architecture == Chimera Linux rejects many established patterns of traditional Linux ecosystem, replacing standard components with lighter ones, modern and strictly standardized alternatives: * '''FreeBSD Userland instead of GNU:''' Standard tools of terminal (like <code>ls</code>, <code>cp</code>, <code>mv</code> or <code>sed</code>) they come directly from the [[FreeBSD]] code tree, not from GNU <code>coreutils</code>. This means that system commands behave according to POSIX and BSD standards, not GNU-specific extensions. * '''LLVM/Clang compiler:''' While most of the mainline distributions (like [[Arch Linux|Arch]] or [[Debian]]) is compiled using GCC, Chimera is build completely from scratch using modern toolchain [[LLVM]] and [[Clang]]. * '''Musl libc:''' Chimera is using <code>musl</code> as a standard C library instead of <code>glibc</code>. This makes the base system exceptionally lightweight. * '''[[Apk]] Package Manager:''' Borrowed from [[Alpine Linux]] package manager <code>apk-tools</code> handles all software installation. Works incredibly fast and manages dependencies. == Component comparison == {| class="wikitable" ! Component ! Traditional Linux (e.g., Arch) ! Chimera Linux |- | '''Kernel''' | Linux | Linux |- | '''Userland''' | [[GNU]] | [[FreeBSD]] |- | '''C Library (libc)''' | [[glibc]] | [[musl]] |- | '''Compiler''' | [[GCC]] | [[LLVM]] / Clang |- | '''System Init''' | [[systemd]] | [[Dinit]] |- | '''Package Manager''' | [[pacman]] / [[apt]] | [[apk-tools]] |} == Target Audience == Chimera Linux '''is not intended for beginners'''. The intended audience are power users, programmers and enthusiasts looking for clean and minimal environment free from GNU and [[Systemd]] domination. It offers unique environment to experience administration in the style of [[BSD]], while maintaining the broad hardware compatibility of the [[Linux]] kernel. == External links == * [https://chimera-linux.org/about/ About Chimera Linux] — Official project overview. <references /> 6b44b1030ce315e5d33742bb414c00239a48a5d6 0 1362 5796 2026-06-19T21:59:12Z Lawl 419 made (not much) of pcmanfm page wikitext text/x-wiki {{Stub}} PCManFM (or PC Man File Manager) is an extremely fast, lightweight file manager for [[Linux]] that powers [[LXDE]] and [[LXQt]] [[desktop environments]].<ref>[https://pcmanfm.com Official PCManFM website]</ref> Rather than other file managers that also use a [[Graphical User Interface]] which mostly focus on ease-of-use and looks, PCManFM focuses on raw performance, speed, and tiny memory footprint. Due to his dissatisfaction with [[GTK3]], Hong Jen Yee, the PCManFM developer, decided to experiment with using [[Qt]] in early 2013.<ref>[http://blog.lxde.org/?p=966 LXDE blog post about the switch from GTK3 to Qt]</ref> Now, this new version adapting [[Qt]] has replaced the old [[GTK3]] version. === Features === * Full [[GVfs]] support with easy access to remote filesystems * Twin panel * Thumbnails for pictures * Desktop management * Bookmarks * Multiple languages * Tabbed browsing, similar to web browsers * Volume management * Drag and drop support * Provides many views d83e7271cc4d7b7f706ce95ebad6d1e8a365e2d7 0 1363 5797 2026-06-20T12:18:16Z Lawl 419 make a tiny amount of iso 9660 page, needs some citations aswell as more info in general wikitext text/x-wiki {{Stub}} '''ISO 9660''', or ECMA-119, is a filesystem for optical disc media. The file system is an international standard available from the International Organization for Standardization (ISO). <ref>[https://en.wikipedia.org/wiki/ISO_9660 Wikipedia entry on ISO 9660]</ref> It is the standard filesystem for CD-ROMs, however is also widely used on DVD and BD media or even USB sticks or hard disks. ISO 9660 is not a complex filesystem compared to other alternatives, however has certain features that are worth knowing about. One of these odd features is that filenames must only consist of uppercase letters A-Z, digits, dots and underscores.<ref>[http://wiki.osdev.org/ISO_9660 OSDev Wiki entry on ISO 9660]</ref> 69c0791016107638e6bd095efa812be3a34b0d01 0 1364 5798 2026-06-20T13:53:30Z Lawl 419 make most of KISS page, needs cleanup n distroinfobox wikitext text/x-wiki {{Stub}} '''KISS Linux''' is a meta-distribution for the [[x86_64]] architecture with a focus on simplicity, sustainability and user freedom.<ref>[https://kisslinux.github.io KISS Linux official Github page]</ref> It was made originally by '''Dylan Araps''', however is now maintained by the KISS community. The distribution focuses on being maintainable by a single user, who is able to choose what is on their system entirely, without any external influence. The user is provided with three things to aid them in this process: the official repositories, the package management system and the freedom to maintain their system by themselves. The distribution follows a rolling release model, with the compilation happening on the users machine, with updates only containing changes to instructions on how to build each package. === Package manager === KISS uses it's own shell-based, fully independent package manager, called <code>kiss</code>. Unlike other package managers, it uses "actions", which are easy to understand instead of complicated arguments. These actions are listed below. {| class="wikitable" |- ! Action !! Description |- |'''alternatives''' |List and swap alternatives |- |'''build''' |Build specified package |- |'''checksum''' |Generate checksums for specified package |- |'''download''' |Download sources |- |'''install''' |Install specified package(s) |- |'''list''' |List installed packages |- |'''remove''' |Remove specified package |- |'''search''' |Search for specified package |- |'''update''' |Update the system and package repositories |- |'''upgrade''' |Upgrade the system |- |'''version''' |Get the package manager version |} === Specifications === Due to KISS focusing on control and minimalism, many components that would usually be heavy are swapped out for lighter, smaller alternatives. KISS uses the [[musl]] C standard library, its own independent init framework in shell and [[Busybox]]. These allow it to be much lighter than its alternatives. === Community === The KISS community now maintains the KISS project. They provide a more modern documentation, maintained package repositories, and better support. The original KISS project by Dylan Araps is now discontinued. e1e2e913b325fec0df4dc149e0e929e0217d33cd 0 1365 5799 2026-06-20T17:00:30Z Lawl 419 make gkiss page wikitext text/x-wiki '''GKISS Linux''' is a [[Linux]] distribution forked from [[KISS Linux]], adopting the [[GNU]] [[C]] standard library ([[glibc]]) rather than the [[musl]] [[C]] standard library. This enables much better compatibility with drivers especially, specifically the [[NVIDIA]] GPU drivers, as it does not work well with [[musl]]. However, due to the nature of [[glibc]], this means your system is much larger, and uses up more memory than the original KISS. It also makes [[statically linking]] your binaries more difficult, as [[glibc]] actively discourages it, and doing the process anyway leads to breakage.<ref>[https://blog.habets.se/2023/04/Linking-statically.html habets.se blog post about issues with glibc.]</ref> For more information, refer to the [[KISS Linux]] page. The C standard library difference is the only real difference between '''GKISS''' and regular '''KISS''', so all of the '''KISS''' guides can be used as normal. b3d751de93825e67fd08f23f03f6fada347af0d3 0 1366 5801 2026-06-22T05:12:16Z Wreckvall 426 moved root article to root user wikitext text/x-wiki {{Stub}} Root is the default Linux user with full control over the system. The root user is identified with a [[UID]] (user ID) of <code>0</code>. Any UID of <code>0</code> is automatically treated as the root user and is given unrestricted access to the system. When using the shell as the root user, the prompt will change form <code>$</code> to <code>#</code>. This warns you that you are running as the root user, and if you do something stupid, Linux will let you be stupid and you might nuke your whole system. Please be careful when running as root. 5245881e9fe5ba9b3e8f34d6d5e9e71b9bfb3b76 0 309 5802 5770 2026-06-22T05:13:09Z Wreckvall 426 change link from root to root user wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Sudo.png.png|thumb]] |thumb]] | caption = Sudo used on [[whoami]] | title = Sudo | releasestatus = Maintained | lastrelease = 1.9.17p2 | languages = [[C]] | developers = sudo project | website = [https://www.sudo.ws/ www.sudo.ws/] }} [[Category:Software]] [[File:Sudo_logo_(2019).png|thumb|335x335px|Sudo's logo of a sandwich]] [[File:Sudo Insults.png|thumb|335x335px|Output from sudo when <code>Defaults insults</code> is added]] The command line tool <code>sudo</code> is used to run commands as another user (most likely [[Root User|root]]).<ref name=":0">[https://man7.org/linux/man-pages/man8/sudo.8.html sudo(8)], Linux Manpages</ref> Its name is shorthand for "su 'do'"<ref>[https://www.sudo.ws/ sudo.ws], Sudo Developers</ref>, however as <code>su</code> stands for "substitute user"<ref>[https://man7.org/linux/man-pages/man1/su.1.html su(1)], Linux Manpages</ref> this would stand for "substitute user, do". When running a command with sudo, the command is spawned running as root, temporarily allowing root privileges for that ''single'' command. While using sudo for every single command would functionally be the same as logging in as root, using sudo forces confirmation (usually with the user password). sudo can be configured to run isolated commands safely without risking full control over the system. Additionally, system administrators may configure sudo by editing the <code>/etc/sudoers</code> file<ref name=":0" />, to specify which users or groups can execute specific commands, and to permit some users to use sudo for specific actions, preserving both functionality and safety. == Usage == {| class="wikitable" |+Common Sudo Commands !Command !Description |- |<code>sudo <command></code> |Run the given command as superuser |- |<code>sudo -E <command></code> |Run the given command as superuser while keeping the current user's env vars |- |<code>sudo -s</code> |Opens a shell with superuser permissions |- |} ''note: every mentioned command is also compatible with the <code>-u <user></code> argument, which will run the command as the given user instead of superuser''<ref name=":0" /> == Trivia == * Sudo's logo is a sandwich in reference to [https://xkcd.com/149/ xkcd 149]<ref>[https://www.sudo.ws/about/logo/ sudo.ws/about/logo], Sudo Developers</ref> * If you add the line <code>Defaults insults</code> to the Defaults section of <code>/etc/sudoers</code>, you will be insulted whenever you type the wrong password.<ref>[https://www.geeksforgeeks.org/when-sudo-insults-you/ When sudo insults you!!], GeeksforGeeks, September 13, 2023 (February 12, 2025)</ref> == References == da7f0d4961e65b5f0b66a50e29d058a06486448a 0 1354 5803 5765 2026-06-22T05:14:09Z Wreckvall 426 turned it into a disambiguation page wikitext text/x-wiki Root can refer to: * The root (<code>/</code>) [[directory]] * The [[Root User|root user]] b162466b624aade25e24f2a55f85cb83421ef736 0 1367 5804 2026-06-26T20:16:17Z Lawl 419 make sequoia page wikitext text/x-wiki {{Stub}} <!-- TODO: softwareinfobox!!! --> '''Sequoia PGP''' is a complete implementation of [[OpenPGP]] as defined by the deprecated [[RFC 4880]] and the newer [[RFC 9580]], and various related standards.<ref>[https://wiki.archlinux.org/title/Sequoia_PGP ArchWiki Sequoia entry]</ref> It is written in the [[Rust]] programming language, so therefore memory safe, as well as being more modern and having a focus on safety, security, correctness and robustness, which allows it to be much more secure than other [[OpenPGP]] implementations, such as [[GPG]]. Many operating systems which prioritize security already use, or are switching to, Sequoia, like [[Qubes OS]].<ref>[https://github.com/QubesOS/qubes-builder-github/pull/19 Github pull request, requesting to add Sequoia OpenPGP.</ref><ref>[https://github.com/QubesOS/qubes-issues/issues/8241 Github issue requesting to add Sequoia.]</ref> === Projects === <!-- TODO: sq (the CLI) deserves a seperate page entirely, so if you are adding usage instructions, please add it to foss.wiki/sq rather than here and change the link from a link to the gitlab page to a link to the foss.wiki entry for it. this is information for the library. thanks!!! --> These are projects, as listed on Sequoia's project page. {| class="wikitable" |- ! Project !! Description |- | [https://gitlab.com/sequoia-pgp/sequoia sequoia-openpgp] || A low-level [[OpenPGP]] library. |- | [https://gitlab.com/sequoia-pgp/sequoia-sq sq] || The primary command-line ([[CLI]]) interface for Sequoia. |- | [https://gitlab.com/sequoia-pgp/sequoia-sqv sqv] || A [[CLI]] interface for [[OpenPGP]] signature verification. |- | [https://gitlab.com/sequoia-pgp/sequoia-sop sqop] || An implementation of SOP using Sequoia. |- | [https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg Chameleon] || A full re-implementation of [[GPG]] using Sequoia. |- | [https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp Octopus] || A Sequoia [[OpenPGP]] backend for [[Thunderbird]]. |} === References === dc17e2dacad4989a863c3bac9625659e37599f6b 0 1368 5805 2026-06-26T20:19:58Z Lawl 419 redirect wikitext text/x-wiki #redirect [[Sequoia]] 1a14670f94f8baf5f746f7f49062385a26edefc5 0 322 5806 5398 2026-06-26T20:26:28Z Lawl 419 general cleanup wikitext text/x-wiki [[Category:Software]] {{Needs Citations}} {{SoftwareInfobox | image = [[File:Musl.png|thumb]] | caption = musl ldd command output. | title = musl | releasestatus = Maintained | lastrelease = 1.2.5 (2024-02-29, commit[https://git.musl-libc.org/cgit/musl/commit/?h=v1.2.5&id=0784374d561435f7c787a555aeab8ede699ed298]) | languages = [[C]] | developers = Rich Felker (dalias) and others | website = [https://musl.libc.org/ musl.libc.org] | license = [[MIT License|MIT]] | sourcecode = https://git.musl-libc.org/cgit/musl }} '''musl''' is a C standard library intended for operating systems based on the [[Linux kernel]], released under the [[MIT License]]. It was developed by Rich Felker as a clean, efficient, and standards-conformant libc implementation. == Usage on [[Operating System|Operating Systems]] == [[Linux Distributions|Linux distributions]] that use musl as their standard C library (some use ''only'' musl) include but are not limited to: * [[Alpine Linux]] * [[Dragora 3]] * [[Gentoo|Gentoo Linux]] ([[glibc]] by default, musl can be chosen at install time) * [[OpenWrt]] * [[postmarketOS]] * [[Sabotage]] * [[Morpheus Linux]] * [[Chimera Linux]] * [[Void Linux]] * [[Dérive Linux]] * [[Oasis Linux]] The [[seL4]] microkernel ships with musl, for binaries that have been linked against [[glibc]], [[gcompat]] and glibmus-hq can be used to execute them on musl-based distros. == Notable differences from [[Glibc]] and Other C Libraries == musl is noted to have chosen certain sacrifices in functionality as design choices for security. === utmp(x) and Other Accounting Functionality === The utmp/wtmp family of Unix and POSIX<ref>{{Cite|url=https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/utmpx.h.html|title=user accounting database definitions, The Open Group Base Specifications Issue 8 (IEEE Std 1003.1-2024)|author=The IEEE and The Open Group|year=2024|accessdate=2026-05-22}}</ref><ref>{{Cite|url=https://pubs.opengroup.org/onlinepubs/9799919799/functions/endutxent.html|title=user accounting database functions, The Open Group Base Specifications Issue 8 (IEEE Std 1003.1-2024)|author=The IEEE and The Open Group|year=2024|accessdate=2026-05-22}}</ref> functions have been removed due to security concerns<ref>{{Cite|url=https://wiki.musl-libc.org/faq.html#Q:-Why-is-the-utmp/wtmp-functionality-only-implemented-as-stubs?|title=musl libc FAQ|author=Kylie McClain|year=2016|accessdate=2026-05-22}}</ref><!-- NOTE: I got the author info for this citation from the git blame of the musl libc wiki: https://github.com/somasis/musl-wiki/blame/e8e065dd5aaf1a189bc659f347638f4b155fc3f4/faq.md#L90 -->. This decision breaks several programs that are useful on multi-user systems, such as wall, last, and who. [https://skarnet.org/software/utmps/ Skarnet implements a daemon which can provide such functionality on musl systems], however it is not included by default on most of these distributions. === Name Service Switch (nsswitch) === [[glibc]] and most other ctandard C libraries on UNIX and Unix-like systems implement something known as the Name Service Switch, or, nsswitch<ref>{{Cite|url=https://skarnet.org/software/nsss/nsswitch.html|title=The problem with nsswitch|author=Skarnet|accessdate=2025-05-22}}</ref>. Musl does not implement these functions either, so [https://skarnet.org/software/nsss/ Skarnet has also provided another daemon for this]. == References == <references /> == See also == * [[Bionic libc]] * [[dietlibc]] * [[glibc]] * [[klibc]] * [[Newlib]] * [[uClibc]] * [[uClibc-ng]] f6dbb1861cf0123b7d616a2120bdbae91a8f9149 0 317 5807 5466 2026-06-26T20:30:21Z Lawl 419 add links to other wiki pages, cleanup wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, [[rolling-release]] [[Linux]] distribution built from scratch. It was created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm Void Linux: Distribution mit XBPS-Paketverwaltung]{{Dead Link|2026-05-26|Cannot connect to host www.pro-linux.de:443 ssl:default [Connection reset by peer]}}, Pro-Linux, 2015-06-12 (Accessed: 2025-08-09)</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and [[musl]] <code>libc</code> support. == Architecture Support == Void Linux provides installation images for: * [[x86_64]] (amd64) - Both [[glibc]] and [[musl]] variants * [[i686]] (32-bit x86) - [[glibc]] only * [[aarch64]] (64-bit ARM) * [[armv6l]] and [[armv7l]] (32-bit ARM) == System Management == === Init System === Void uses [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for runit. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | sv up service || Start a service |- | sv down service || Stop a service |- | sv status service || Check service status |- | ls /var/service || List enabled services |} === System Variants === Void Linux offers two C library implementations, which provide many of the functions used by programs written in the [[C]] programming language: [[glibc]] and [[musl]] <code>libc</code>. ====glibc==== [[glibc]] is the original C library implementation used by Void Linux. While it provides compatibility with most proprietary software, it produces larger executables and uses more memory than musl libc. ====musl==== musl libc was added to the Void Linux repositories in 2013.<ref>[https://github.com/void-linux/void-packages/commit/8420d238cb1338fef2a7392bca6dc65c6fa80001 New package: musl-0.9.9.], Juan RP, 2013 (Accessed: October 18, 2025)</ref> It has a smaller footprint and full static linking support, though not all programs are compatible with it. == Installation == Void Linux is installed using a terminal-based installer called <code>void-installer</code> which is included in the live ISO images provided by the project. It guides users in configuring the network, setting the system's locale and time zone, adding user accounts, partitioning the disks, and installing the system itself.<ref>[https://www.debugpoint.com/install-void-linux/ How to Install Void Linux [Step by Step&#93;], Arindam, 2024 (Accessed: October 18, 2025)</ref> Detailed instructions for installation are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == Void uses a script called <code>xbps-src</code> for building packages, using template files that specify the package metadata, dependencies, and build instructions. It builds packages in a container with only the declared dependencies installed.<ref>[https://www.ordinatechnic.com/distribution-specific-guides/Void/void-linux-creating-binary-packages-using-xbps-src Void Linux: Creating Binary Packages Using xbps-src], Ordinatechnic, 2018 (Accessed: October 18, 2025)</ref> It also supports cross-compilation. == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://voidlinux.org/news/ Official blog] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == ed8ccb32797cc792dab6d750566a2a096ef3feac 5808 5807 2026-06-26T20:32:16Z Lawl 419 wrap each sv command in code blocjks wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = Void | image = [[File:Void Linux logo.svg|Void_linux_logo]] | caption = The official Void logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[XBPS]] | defaultdesktops = [[Xfce]] (live image only) | usagetype = Desktop, Server | architectures = amd64, aarch64, armv6l, armv7l, i686 | website = [https://voidlinux.org/ voidlinux.org] }} '''Void Linux''' is an independent, [[rolling-release]] [[Linux]] distribution built from scratch. It was created in 2008 by Juan Romero Pardines, a former [https://www.netbsd.org/ NetBSD]<ref>[https://www.pro-linux.de/news/1/22419/void-linux-distribution-mit-xbps-paketverwaltung.htm Void Linux: Distribution mit XBPS-Paketverwaltung]{{Dead Link|2026-05-26|Cannot connect to host www.pro-linux.de:443 ssl:default [Connection reset by peer]}}, Pro-Linux, 2015-06-12 (Accessed: 2025-08-09)</ref> developer. Void distinguishes itself through minimal design philosophy, use of the <code>runit</code> init system instead of the widely adopted <code>systemd</code>, home-grown [[XBPS]] package manager, and [[musl]] <code>libc</code> support. == Architecture Support == Void Linux provides installation images for: * [[x86_64]] (amd64) - Both [[glibc]] and [[musl]] variants * [[i686]] (32-bit x86) - [[glibc]] only * [[aarch64]] (64-bit ARM) * [[armv6l]] and [[armv7l]] (32-bit ARM) == System Management == === Init System === Void uses [[runit]] as its init system, offering clean process states for all new services<ref>{{Cite|url=https://docs.voidlinux.org/config/services/index.html|title=Void Linux Handbook}}</ref>, musl support, and an overall small codebase that does one thing well. Below is a short cheat sheet for <code>sv</code>, the service manager for runit. {| class="wikitable" style="margin:auto" ! Command !! Purpose |- | <code>sv up service</code> || Start a service |- | <code>sv down service</code> || Stop a service |- | <code>sv status service</code> || Check service status |- | <code>ls /var/service</code> || List enabled services |} === System Variants === Void Linux offers two C library implementations, which provide many of the functions used by programs written in the [[C]] programming language: [[glibc]] and [[musl]] <code>libc</code>. ====glibc==== [[glibc]] is the original C library implementation used by Void Linux. While it provides compatibility with most proprietary software, it produces larger executables and uses more memory than musl libc. ====musl==== musl libc was added to the Void Linux repositories in 2013.<ref>[https://github.com/void-linux/void-packages/commit/8420d238cb1338fef2a7392bca6dc65c6fa80001 New package: musl-0.9.9.], Juan RP, 2013 (Accessed: October 18, 2025)</ref> It has a smaller footprint and full static linking support, though not all programs are compatible with it. == Installation == Void Linux is installed using a terminal-based installer called <code>void-installer</code> which is included in the live ISO images provided by the project. It guides users in configuring the network, setting the system's locale and time zone, adding user accounts, partitioning the disks, and installing the system itself.<ref>[https://www.debugpoint.com/install-void-linux/ How to Install Void Linux [Step by Step&#93;], Arindam, 2024 (Accessed: October 18, 2025)</ref> Detailed instructions for installation are available in the [https://docs.voidlinux.org/installation/index.html official handbook]. == Package Development == Void uses a script called <code>xbps-src</code> for building packages, using template files that specify the package metadata, dependencies, and build instructions. It builds packages in a container with only the declared dependencies installed.<ref>[https://www.ordinatechnic.com/distribution-specific-guides/Void/void-linux-creating-binary-packages-using-xbps-src Void Linux: Creating Binary Packages Using xbps-src], Ordinatechnic, 2018 (Accessed: October 18, 2025)</ref> It also supports cross-compilation. == See Also == * [[Linux]] == External Links == * [https://voidlinux.org/ Official website] * [https://voidlinux.org/news/ Official blog] * [https://docs.voidlinux.org/ Documentation] * [https://github.com/void-linux GitHub organization] == References == 26ac0d9c0d1b35f88361269d806bf6262942863b 0 1369 5809 2026-06-26T21:56:20Z Lawl 419 redirect wikitext text/x-wiki #REDIRECT [[GnuPG]] 7cd206327c357b049d70ba44713c606469a39fb4 5810 5809 2026-06-26T21:57:28Z Lawl 419 wrong redirect oopsie wikitext text/x-wiki #REDIRECT [[Gnupg]] ac4b6314f82928a0a3061203e538450b71c7dc94 0 1190 5811 5332 2026-06-26T22:03:12Z Lawl 419 add security related things, cleanup wikitext text/x-wiki {{Stub}} {{SoftwareInfobox |image=[[File:GnuPG-Logo.svg|thumb]] |caption=GnuPG |releasestatus=Maintained |lastrelease=2.5.19, Apr 24, 2026 |firstrelease=1.0.0, Sep 7, 1999 |languages=[[C]] |developers=[https://en.wikipedia.org/wiki/Werner_Koch Werner Koch] |website=[https://gnupg.org/ gnupg.org] |license=GPL-3.0-or-later }} [[Category:Software]] [[File:GPG keys generation.png|thumb|Example of PGP key generation with GPG]] '''GnuPG''' (also known as <code>GPG</code>) is a Free and Open Source implementation of the [https://www.ietf.org/rfc/rfc4880.txt OpenPGP standard] that is included in many [[Linux Distributions|Linux distributions]] and is a dependency of many package managers, including [[Pacman]]<ref>{{Cite|url=https://archlinux.org/packages/core/x86_64/pacman/|title=Archlinux "Pacman" package|author=Christian Hesse|year=2026-05-06|accessdate=2026-05-23}}</ref>. GnuPG is primarily used to asymmetrically encrypt files and messages but can also be used to symmetrically encrypt files or messages. Asymmetric encryption allows a sender to encrypt a file using a public key that only the receiver with the shard key can decrypt. Symmetric encryption on the other hand allows files or messages to be encrypted and decrypted with the same password password. Likewise, GnuPG can also sign messages using Asymmetric encryption allowing a receiver to verify, using a sender's public key, the legitimacy of a message. GnuPG and [[SSH]] is used by [[Git]] to sign commits and tags<ref>{{Cite|url=https://git-scm.com/docs/signature-format|title=Git documentation|year=Unknown publication date|accessdate=2026-05-23}}</ref>. GnuPG can be integrated into apps with the [https://www.gnupg.org/software/gpgme/index.html GnuPG Made Easy library]. === Security Issues === Due to GnuPG supporting many old and deprecated algorithms and many UX mistakes, many users advise moving towards the more modern [[Age]] for encryption<ref>{{Cite|url=https://sumguy.com/age-vs-gpg-modern-encryption/|title=age vs GPG: Modern File Encryption That Doesn't Make You Cry|author=SumGuy|year=May 26, 2026|accessdate=2026-05-23}}</ref>. It should be noted that [[Age]] does not support signing, another tool like [[Minisign]] is needed. GnuPG also has a very large codebase. This makes it prone to [[CVE]]s. If you still wish to use [[OpenPGP]], but not through GnuPG, it is recommended you use [[Sequoia]], which is a more modern [[OpenPGP]] implementation. === References === <references /> bf4620d31dc9d9658c47897ad349128e3290d583 0 1370 5812 2026-06-26T22:17:56Z Lawl 419 oasis linux page wikitext text/x-wiki {{Stub}} <!-- todo: distroinfobox --> '''Oasis''' is a small, fast and reproducible [[Linux]] distribution developed by Michael Forney. Unlike other distributions, Oasis is fully statically linked; simpler than dynamically linking, which is a much more complex procedure, aswell as creating speedy and portable self contained binaries. It uses a [[BSD]] ports-like package system, which uses [[Samurai]], a [[Ninja]]-like build tool, along with build manifests generated by [[Lua]] scripts. <ref>[https://github.com/oasislinux/oasis Oasis Linux README]</ref> Like with other distributions that aim to be lightweight, Oasis swaps out many larger tools with smaller, leaner tools. These include but are not limited to: * [[BearSSL]] as the system [[TLS]] and crypto library. * [[musl]] as the C standard library. * [[oksh]] instead of [[Bash]] * [[samurai]] instead of [[Ninja]] .. and many more. The full list is available in [https://github.com/oasislinux/oasis the official Oasis Linux Github repository]. === Extra packages === Due to Oasis' limited package system, the full package tree may not include packages you want or need. To fix this, you can use [[Nix]] or [[pkgsrc]] to install packages not available in the official package tree, such as [[Firefox]]. 341a7efbc972c4c0213ba4936345d8df8eb6ba8e 0 1371 5813 2026-06-26T22:22:45Z Lawl 419 lua paeg wikitext text/x-wiki {{Stub}} <!-- TODO: DESPERATELY needs more content --> '''Lua''' is a powerful, efficient, lightweight, embeddable scripting language. It supports several programming styles: procedural, object-oriented, functional, data-driven, and data description. <ref>[https://www.lua.org/about.html Lua's official website]</ref> Lua is corss-platform software, since the interpreter of compiled bytecode is written in '''ANSI [[C]]''', aswell as Lua having a relatively simple C API to embed it into applications.<ref>[https://en.wikipedia.org/wiki/Lua Lua's Wikipedia artice]</ref> ad9020869ae1619db5be85bd0f83685fe246e10a 0 769 5814 5668 2026-06-26T22:25:23Z Lawl 419 small cleanup + tiny bit more of info wikitext text/x-wiki The choice of Wayland compositor is most comparable with choosing a window manager under [[X11]]. The Wayland compositor is in charge of rendering everything, routing input, configuring input/output devices as well as window management policy. The last one is what users are usually most interested in. A Wayland compositor alone does not constitute a full desktop environment, so further components are usually needed. For example, if you want any form of status bar, [[Waybar]] (or alternatives) are needed. ==Compositors Associated to a Desktop Environment== These Compositors are associated to a specific desktop environment. They are not meant to be used outside of their desktop environments. {| class="wikitable" ! Compositor !! Desktop Environment !! Window Managagement Paradigm !! Written In !! Notes |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| Floating Window Management || [[C]] || The compositor of the GNOME desktop environment. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]] || Floating WIndow Management || [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp cosmic-comp github repo], pop-os team et al., 2025 (Accessed: 2026-05-25)</ref> |[[COSMIC]] | Floating or Stacking Window Management |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |} ==Floating Compositors== These compositors have what is often referred to as floating or stacking window management. This is same model you see on gnome and KDE where windows move around freely and are allowed to overlap each other. {| class="wikitable" ! Compositor !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. Not suitable for daily use |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- |} ==Tiling Compositors== These compositors perform what is referred to as tiling window management. Windows usually don't overlap and are automatically positioned to take up screen space. These often favour more advanced usage of virtual desktop or tags as well as a more keyboard-driven workflow. {| class="wikitable" ! Compositor !! Written In !! Notes |- | [[MangoWM]]<ref>[https://mangowc.vercel.app MangoWM Homepage]{{Dead Link|2026-05-26|404}} (Accessed: 2026-02-27)</ref> || [[C]] || Extremely customizable & performant Wayland compositor built on top of [[dwl]]. |- | [[Sway]] || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[Niri]] || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} == Other Compsitors == These compositors don't fit neatly into any of the above paradigms. {| class="wikitable" ! Compositor !! Written In !! Notes |- | [[river]]<ref>[https://codeberg.org/river/river Codeberg - A non-monolithic Wayland compositor] river, (Accessed: 2026-05-30)</ref> || [[zig]]|| A non-monolithic wayland compositor where window management is performed by an external program. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- |} ==References== <references /> b293fba73ab64ec7a68354122988047e2f978a9d 0 1372 5815 2026-06-28T14:38:26Z Satnus 215 Started work on writing the article. wikitext text/x-wiki [[Category:Programming Languages]] {{SoftwareInfobox | image = [[File:Js-logo-unofficial.svg|frameless]] | caption = Unofficial JavaScript Logo | title = JavaScript | releasestatus = Maintained | lastrelease = ES2025, June 2025<ref>ECMA International, "ECMAScript® 2025 Language Specification", ECMA-262, June 2025, [https://262.ecma-international.org/ https://262.ecma-international.org/], June 28, 2026</ref> | languages = [[C]], [[C++]] | developers = ECMA International | website = [https://ecma-international.org/publications-and-standards/standards/ecma-262/ ECMA-262] }} a01d786a330f99d2c007e3fc9604178681a25d51 0 1373 5816 2026-06-29T21:06:55Z Lawl 419 make gnu/hurd page wikitext text/x-wiki {{Stub}} <!-- distroinfobox, more info --> '''GNU Hurd''' (also referred to as "The Hurd" on [[GNU]]'s website) is the [[GNU]] project's replacement for the [[UNIX]] operating system kernel.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's official Hurd documentation]</ref> It is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's description of Hurd]</ref> Essentially, The Hurd consists of a set of protocols and server processes (also known as daemons) that run on the [[GNU]] [[Mach]] microkernel. This means it differentiates from the [[Linux]] kernel, which is [[monolithic]].<ref>[https://itsfoss.com/news/gnu-hurd-progress-report/ ItsFOSS news report on GNU/Hurd]</ref> It has been in development since 1990, by the [[GNU]] project.<ref>[https://en.wikipedia.org/wiki/GNU_Hurd The Wikipedia entry for GNU Hurd]</ref> === History === '''Richard Stallman''' founded the [[GNU]] project in September 1983 with a goal to create a free [[GNU]] operating system.<ref>[https://cs.stanford.edu/people/eroberts/courses/cs181/projects/2000-01/open-source/gnu.htm#:~:text=In%201983,%20the%20GNU%20Project,up%20by%20proprietary%20software%20vendors. The history of the GNU project]</ref> Initially, all the necessary components needed for kernel development were made. By 1989, the [[GPL]] came into being, and the only major missing component was the [[kernel]], hence why they added the GNU operating system to [[Linux]] until they had their own kernel.<ref>[https://www.gnu.org/gnu/linux-and-gnu.html "Linux and GNU" entry on GNU's website]</ref> After this, development on the Hurd started after an abandoned kernel attempt, based on the [[TRIX]] operating system.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd History: How it started]</ref> According to the initial architect and founder of Hurd, '''Thomas Bushnell''', one of their early plans was to adopt and build on the [[4.4BSD]]-Lite kernel.<ref>[https://web.archive.org/web/20230710085615/http://www.groklaw.net/article.php?story=20050727225542530 "The Daemon, the GNU and the Penguin"]</ref> Later on from this, Richard Stallman proposed the use of the [[Mach]] microkernel, however this was delayed due to concern on whether the [[Mach]] code would be released under a suitable license.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd's history]</ref> Up until now, the development of Hurd had been relatively fast. However, with the release of the free [[Linux]] kernel in 1991, development slowed heavily, but did not stop. GNU's [[userland]] components were quickly put together with the [[Linux]] kernel to create operating systems based on the [[Linux]] kernel ([[Linux distributions]]). === References === 6a208277167ea5de5d8c4ed2b21f60917a229095 5817 5816 2026-06-30T17:54:23Z Lawl 419 distroinfobox!! (no image yet) wikitext text/x-wiki {{Stub}} <!-- distroinfobox, more info --> [[Category:Misc Operating Systems]] {{DistributionInfobox | architectures = i386, x86_64 | caption = The GNU Hurd logo | defaultdesktops = [[GNOME]], [[Xfce]], [[Window Maker]], [[Fluxbox]], [[IceWM]], [[Openbox]] | image = | packagemanager = [[dpkg]]/[[apt]] ([[Debian GNU/Hurd]]), [[Guix]] | releasemodel = Rolling | releasestatus = Experimental | title = GNU/Hurd | usagetype = Research, Development | website = [https://www.gnu.org/software/hurd/ gnu.org/software/hurd] }} '''GNU Hurd''' (also referred to as "The Hurd" on [[GNU]]'s website) is the [[GNU]] project's replacement for the [[UNIX]] operating system kernel.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's official Hurd documentation]</ref> It is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's description of Hurd]</ref> Essentially, The Hurd consists of a set of protocols and server processes (also known as daemons) that run on the [[GNU]] [[Mach]] microkernel. This means it differentiates from the [[Linux]] kernel, which is [[monolithic]].<ref>[https://itsfoss.com/news/gnu-hurd-progress-report/ ItsFOSS news report on GNU/Hurd]</ref> It has been in development since 1990, by the [[GNU]] project.<ref>[https://en.wikipedia.org/wiki/GNU_Hurd The Wikipedia entry for GNU Hurd]</ref> === History === '''Richard Stallman''' founded the [[GNU]] project in September 1983 with a goal to create a free [[GNU]] operating system.<ref>[https://cs.stanford.edu/people/eroberts/courses/cs181/projects/2000-01/open-source/gnu.htm#:~:text=In%201983,%20the%20GNU%20Project,up%20by%20proprietary%20software%20vendors. The history of the GNU project]</ref> Initially, all the necessary components needed for kernel development were made. By 1989, the [[GPL]] came into being, and the only major missing component was the [[kernel]], hence why they added the GNU operating system to [[Linux]] until they had their own kernel.<ref>[https://www.gnu.org/gnu/linux-and-gnu.html "Linux and GNU" entry on GNU's website]</ref> After this, development on the Hurd started after an abandoned kernel attempt, based on the [[TRIX]] operating system.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd History: How it started]</ref> According to the initial architect and founder of Hurd, '''Thomas Bushnell''', one of their early plans was to adopt and build on the [[4.4BSD]]-Lite kernel.<ref>[https://web.archive.org/web/20230710085615/http://www.groklaw.net/article.php?story=20050727225542530 "The Daemon, the GNU and the Penguin"]</ref> Later on from this, Richard Stallman proposed the use of the [[Mach]] microkernel, however this was delayed due to concern on whether the [[Mach]] code would be released under a suitable license.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd's history]</ref> Up until now, the development of Hurd had been relatively fast. However, with the release of the free [[Linux]] kernel in 1991, development slowed heavily, but did not stop. GNU's [[userland]] components were quickly put together with the [[Linux]] kernel to create operating systems based on the [[Linux]] kernel ([[Linux distributions]]). === References === b6728f4eda4609dd52966cf0910a059d746deaed 3000 1336 5818 5719 2026-07-02T21:35:24Z OliMoli 371 Add NixOS Sway installation instructions wikitext text/x-wiki See the main article on [[Sway]]. === Notes before you install Sway: === * All proprietary graphic drivers are not officially supported, including Nvidia's. Albeit, the open source Nouveau driver can be used instead. * Not all login managers support Wayland. If you have any issues regarding login managers refer to <code>man 1 sway.</code> * If you are planning to migrate from i3, you may want to look at [https://github.com/swaywm/sway/wiki/i3-Migration-Guide] === Installation guide: === ==== Compiling from source: ==== Following dependencies are needed, make sure you have them: git, gcc or clang, meson, wlroots, ninja, wayland, wayland-protocols, pcre2, json-c, pango, cairo, gdk-pixbuf2 (optional: additional image formats for system tray), swaybg (optional: for wallpaper), scdoc (optional: man pages), git (optional: version info). As per official guide: ====== First make sure wlroots is installed: ====== * Clone the [https://gitlab.freedesktop.org/wlroots/wlroots/ wlroots] repository using git to your desired location. * Run <code>meson build</code> to create the <u>build</u> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that either <code>/usr/local/lib</code> or <code>/usr/local/lib64</code> include<code>libwlroots.so</code> ===== Now to build sway: ===== * Clone the [https://github.com/swaywm/sway sway] repository with git * Run <code>meson build</code> to create the <code>build</code> directory * Now run the following command: <code>ninja -C build</code> to build * Finally: <code>sudo ninja -C build install</code> to install * To verify check that <code>/usr/local/bin</code> contains the <code>sway</code>, <code>swaybar</code>, <code>swaylock</code>, etc. binaries. ==== For [[Arch]]: ==== Using pacman: pacman -S sway Using paru: paru -S sway Using yay: yay -S sway ==== For [[Debian]]: ==== Using apt package manager: apt install sway ==== For [[Fedora]]: ==== Using dnf package manager: dnf install sway ==== For [[NixOS]]: ==== Setting the following value in the system configuration: programs.sway.enable = true; fac7e41e5262b3edfc06cd96baa721989dfdc0de 0 1374 5819 2026-07-04T18:04:04Z Uniolo 345 Created Internet Relay Chat (with next to nothing, but including a work in progress banner) wikitext text/x-wiki {{Work In Progress}} '''Internet Relay Chat''' or '''IRC''' for short is a protocol for users to chat with other users. 30c395dfd34d530898c9eae6a65c252d217242d1 0 1375 5820 2026-07-04T18:04:19Z Uniolo 345 Redirect to Internet Relay Chat wikitext text/x-wiki #redirect [[Internet Relay Chat]] 5be4e34c4f27057f289a0ba6e00c9de34698796e 0 1376 5821 2026-07-04T18:04:35Z Uniolo 345 Redirect to Internet Relay Chat (as mediawiki is case sensitive for page names) wikitext text/x-wiki #redirect [[Internet Relay Chat]] 5be4e34c4f27057f289a0ba6e00c9de34698796e 0 1374 5822 5819 2026-07-04T18:18:29Z Uniolo 345 Added some information, gave Arch IRC channels as an example, and defined "IRC Network", also listed some clients. wikitext text/x-wiki {{Work In Progress}} '''Internet Relay Chat''' or '''IRC''' for short, is a protocol for users to chat with other users on an IRC network. There are many such IRC networks, for instance, users seeking help on [[Arch Linux]] might use one of the the [https://wiki.archlinux.org/title/Arch_IRC_channels Arch IRC channels] to do so. An IRC Network is a collection of servers, and users who are connected to a server on an IRC network can talk to users connected to any such server on the same IRC network<ref>{{Cite|url=https://www.rfc-editor.org/info/rfc1459/#section-1.1|title=RFC 1459|author=J. Oikarinen, D. Reed|year=1993|accessdate=2026-07-04}}</ref>. There are a variety of IRC clients to choose from, such as [[Konversation]], [[WeeChat]], [[Irssi]], [[Halloy]], and many others. 41a6937e0b1c3bce8053906c1494d5e3c5c8e7ff 5823 5822 2026-07-04T18:21:41Z Uniolo 345 Added information about channels wikitext text/x-wiki {{Work In Progress}} '''Internet Relay Chat''' or '''IRC''' for short, is a protocol for users to chat with other users on an IRC network. Each network is composed of a number of channels<ref name=":0" />, with each channel having different chat messages sent within it. There are many such IRC networks, for instance, users seeking help on [[Arch Linux]] might use one of the the [https://wiki.archlinux.org/title/Arch_IRC_channels Arch IRC channels] to do so. An IRC Network is a collection of servers, and users who are connected to a server on an IRC network can talk to users connected to any such server on the same IRC network<ref name=":0">{{Cite|url=https://www.rfc-editor.org/info/rfc1459/#section-1.1|title=RFC 1459|author=J. Oikarinen, D. Reed|year=1993|accessdate=2026-07-04}}</ref>. There are a variety of IRC clients to choose from, such as [[Konversation]], [[WeeChat]], [[Irssi]], [[Halloy]], and many others. 4c24deb535a631f48a36423f78ed564f6fad5249 5825 5823 2026-07-06T14:45:53Z Uniolo 345 Added information about bouncers and alternatives wikitext text/x-wiki {{Work In Progress}} '''Internet Relay Chat''' or '''IRC''' for short, is a protocol for users to chat with other users on an IRC network. Each network is composed of a number of channels<ref name=":0" />, with each channel having different chat messages sent within it. There are many such IRC networks, for instance, users seeking help on [[Arch Linux]] might use one of the the [https://wiki.archlinux.org/title/Arch_IRC_channels Arch IRC channels] to do so. As IRC was created in 1988, it lacks many features such as message history, although bouncers, such as [[ZNC]], can allow users to work around this. Many alternatives to IRC exist, such as [[Matrix]], [[XMPP]], and [[Fluxer]]. Many IRC channels, such as the [https://userbase.kde.org/IRC_Channels KDE IRC Channels], bridge some of their IRC channels to Matrix, allowing Matrix users to chat with IRC users<ref>{{Cite|url=https://community.kde.org/Matrix|title=KDE Community Wiki, Matrix|year=2026|accessdate=2026-07-06}}</ref>. An IRC Network is a collection of servers, and users who are connected to a server on an IRC network can talk to users connected to any such server on the same IRC network<ref name=":0">{{Cite|url=https://www.rfc-editor.org/info/rfc1459/#section-1.1|title=RFC 1459|author=J. Oikarinen, D. Reed|year=1993|accessdate=2026-07-04}}</ref>. There are a variety of IRC clients to choose from, such as [[Konversation]], [[WeeChat]], [[Irssi]], [[Halloy]], and many others. 969f2436c603f15b9b96e618b2edf3ecf62c08e3 5826 5825 2026-07-06T14:47:23Z Uniolo 345 Replaced work in progress template with stub wikitext text/x-wiki {{Stub}} '''Internet Relay Chat''' or '''IRC''' for short, is a protocol for users to chat with other users on an IRC network. Each network is composed of a number of channels<ref name=":0" />, with each channel having different chat messages sent within it. There are many such IRC networks, for instance, users seeking help on [[Arch Linux]] might use one of the the [https://wiki.archlinux.org/title/Arch_IRC_channels Arch IRC channels] to do so. As IRC was created in 1988, it lacks many features such as message history, although bouncers, such as [[ZNC]], can allow users to work around this. Many alternatives to IRC exist, such as [[Matrix]], [[XMPP]], and [[Fluxer]]. Many IRC channels, such as the [https://userbase.kde.org/IRC_Channels KDE IRC Channels], bridge some of their IRC channels to Matrix, allowing Matrix users to chat with IRC users<ref>{{Cite|url=https://community.kde.org/Matrix|title=KDE Community Wiki, Matrix|year=2026|accessdate=2026-07-06}}</ref>. An IRC Network is a collection of servers, and users who are connected to a server on an IRC network can talk to users connected to any such server on the same IRC network<ref name=":0">{{Cite|url=https://www.rfc-editor.org/info/rfc1459/#section-1.1|title=RFC 1459|author=J. Oikarinen, D. Reed|year=1993|accessdate=2026-07-04}}</ref>. There are a variety of IRC clients to choose from, such as [[Konversation]], [[WeeChat]], [[Irssi]], [[Halloy]], and many others. 7a41c3cf523d194dead359bbd1ecf4c8de7a93f9 0 1040 5824 5271 2026-07-06T04:15:46Z YDTA 389 minor language changes, clarified package managers wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Qubes OS | image = [[File:QubesOSlogo.png|thumb]] | caption = The Qubes OS logo | releasestatus = Maintained | releasemodel = Stable | basedon = [[Fedora]], [[Debian]] | packagemanager = [[DNF]] (dom0), template-dependent | defaultdesktops = [[XFCE]] | virtualization = [[Xen]] | usagetype = Desktop | architectures = x86_64 | init = [[systemd]] | license = Free and open-source software | website = [https://www.qubes-os.org/ qubes-os.org] }} [[Category:Linux Distributions]] [[Category:Security]] [[Category:Virtualization]] [[Category:Privacy]] '''Qubes OS''' is a free and open-source, security-oriented operating system focused on desktop security through strong isolation and compartmentalization. Qubes OS separates applications and workflows into isolated compartments known as '''qubes'''<ref>also known as a '''domU,''' '''security domain,''' or simply '''domain'''</ref> by leveraging [[Xen]]-based virtualization<ref name=":0">{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/intro.html|title=Introduction to Qubes OS|accessdate=2026-05-24}}</ref>. It should also be noted that Qubes, rather than being considered a Linux distribution, may be considered as either a ''meta-distribution'' (in a similar regard as [[Bedrock Linux]]), or a Xen distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#is-qubes-just-another-linux-distribution|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Technically, any [[X86-64|x86_64]] operating system may be used as a qube, but the extent to which it is supported varies. == Installation == The Qubes OS project provides a [https://doc.qubes-os.org/en/latest/user/downloading-installing-upgrading/installation-guide.html comprehensive installation guide] in its documentation. Users may consider reading the documentation on [https://doc.qubes-os.org/en/latest/user/downloading-installing-upgrading/install-security.html installation security] as well. === System Requirements === The following features are <u>required</u> (but may not be sufficient) for Qubes OS<ref name=":2">{{Cite|url=https://doc.qubes-os.org/en/latest/user/hardware/system-requirements.html|title=System Requirements|author=Qubes OS Project|accessdate=2026-05-25}}</ref>: * [[X86-64|64-bit Intel or AMD processor]] ** Intel VT-x with EPT or AMD-V with RVI ** Intel VT-d or AMD-Vi (also known as AMD IOMMU) * 6 GB RAM * 32 GB free space on disk The following are <u>recommended</u> for running Qubes OS<ref name=":2" />: * [[X86-64|64-bit Intel processor]] ** Intel VT-x with EPT ** Intel VT-d ** AMD processors are not recommended due to inconsistent security support on client platforms (see Important Notes for details). * 16 GB RAM * 128 GB free space ** A fast solid-state drive is strongly recommended by the project * An Intel integrated graphics processor is strongly recommended by the project ** Nvidia GPUs may require significant troubleshooting. ** AMD GPUs have not been formally tested, but Radeons (especially RX580 and earlier) generally work well. * A non-USB keyboard, or multiple USB controllers * A Trusted Platform Module (TPM) with proper BIOS support == Supported [[Qubes OS#Templates|Templates]] == The Qubes OS project officially provides the following templates: * [[Fedora]]-based ** [[XFCE]] ** [[GNOME]] ** Minimal (CLI only) * [[Debian]]-based ** XFCE ** GNOME ** Minimal (CLI only) Community-supported templates are also available, [https://doc.qubes-os.org/en/latest/user/templates/templates.html#community with additional considerations]: * [[Kicksecure]] * [[Whonix]] **Whonix Gateway **Whonix Workstation * Arch (in <code>qubes-templates-community-testing</code>) Users will also be able to create their own Templates from scratch == Architecture == Each qube is implemented as a separate [[Xen|Xen virtual machine]], which the user may utilize for activities such as composing documents or browsing the web<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/getting-started.html|title=Qubes OS Basics|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Each qube is distinguished by its name, which identifies its purpose, and a color which identifies its level of trust<ref name=":0" />. Qubes are copy-on-write, meaning that a [https://doc.qubes-os.org/en/latest/user/advanced-topics/volume-backup-revert.html full revert mechanism is available should it be needed]. === Templates === Templates provide root filesystems for app qubes. When an app qube is started, a copy of the root filesystem will be made and used by the app qube, then discarded on shutdown<ref name=":3">{{Cite|url=https://doc.qubes-os.org/en/latest/user/reference/glossary.html|title=Glossary|author=Qubes OS Project|accessdate=2026-05-25}}</ref>. Software meant to be run in app qubes must be installed in the corresponding template. See https://doc.qubes-os.org/en/latest/user/templates/templates.html === App qubes === App qubes are qubes where the user is meant to conduct everyday activities. An app qube will use a copy of the root filesystem taken from a chosen [[Qubes OS#Template|template]], and will only keep things in <code>/home/</code>and <code>/usr/local/</code>after being restarted<ref name=":3" />. App qubes can also be disposable templates and provide the base for disposable qubes. === Disposables === Disposable qubes obtain a fresh filesystem from its disposable template (distinct from a template) upon startup and fully discard it after shutting down<ref name=":3" />. === Standalones === A traditional virtual machine, both root and user directories are kept between starts<ref name=":3" />. == Security == === Qubes Master Signing Key === The QMSK is an [[Gnupg|OpenPGP]] key used as the root of trust for the Qubes OS Project to verify developer keys, release signatures, and communications<ref name=":1">{{Cite|url=https://doc.qubes-os.org/en/latest/project-security/verifying-signatures.html#how-to-import-and-authenticate-the-qubes-master-signing-key|title=Verifying signatures|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. The QMSK is available from the Qubes Project at https://keys.qubes-os.org/keys/qubes-master-signing-key.asc, or in any Qubes OS provided qube at <code>/usr/share/qubes/qubes-master-key.asc</code>. Users are encouraged by the Qubes Project to "distrust the infrastructure"<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/introduction/faq.html#what-does-it-mean-to-distrust-the-infrastructure|title=Qubes FAQ|author=Qubes OS Project|accessdate=2026-05-25}}</ref> and to compare multiple channels to verify the QMSK's fingerprint<ref name=":1" /> Any single source (including this website) should not be trusted. One copy is provided here as: <code>0x427F11FD0FAA4B080123F01CDDFA1A3E36879494</code> Other potential channels to obtain the fingerprint from include: * The Qubes OS Project wiki * Video recordings of presentations about Qubes * Asking a friend(s) * Asking a stranger(s) === Limitations === It is important to note that while Qubes OS is designed to to limit the damage caused by the compromise of one or multiple qubes, <u>it does ''not'' attempt at additional hardening for the VM operating system itself</u> above that of the base distribution<ref>{{Cite|url=https://doc.qubes-os.org/en/latest/developer/system/security-design-goals.html#security-design-goals|title=Security Design Goals|author=Qubes OS Project|accessdate=2026-05-24}}</ref>. Users may consider using other security-oriented distributions in conjunction with Qubes OS for additional security. == External Links == * [https://www.qubes-os.org/ Official website] * [https://www.qubes-os.org/doc/ Official documentation] * [https://github.com/QubesOS Qubes OS GitHub] e1e1f0f22092fbbaaded8a1d83d7be4577e0cb63 6 1377 5827 2026-07-08T19:54:51Z PhantasNick 291 wikitext text/x-wiki Logo for openSUSE Based Distro, Aeon 57d435273a3f481527b04a0c36825b2520c3cf1a 0 1378 5828 2026-07-08T19:56:59Z PhantasNick 291 Initial Creation of Aeon Page wikitext text/x-wiki {{DistributionInfobox | title = Aeon | image = [[File:Aeon-Logo.svg|frameless]] | caption = Aeon | releasestatus = Maintained | releasemodel = Rolling | packagemanager = [[transactional-update]] | defaultdesktops = [[GNOME]] | usagetype = Desktop | architectures = x86-64 | website = [https://aeondesktop.github.io/# aeondesktop.github.io] }} Aeon is an immutable desktop Linux distribution based on [[openSUSE]]. It is a relatively small, low-maintenance system with automated daily updates, thus recommended for Linux beginners or "lazy developers". Some of the distribution's other features include a custom system installer called Transactional Installation Kit (TIK), a pre-configured [[GNOME]] desktop, out-of-the-box support for [[Flatpak]] packages, [[Distrobox]] configured to launch Tumbleweed containers, and automatic rollbacks to its last working state. 89eefea8bab760222c285b85c9b6ef137bb4daa1 5861 5828 2026-07-17T04:29:18Z PhantasNick 291 added Stub and Citation Templates wikitext text/x-wiki {{stub}} {{Needs Citations}} {{DistributionInfobox | title = Aeon | image = [[File:Aeon-Logo.svg|frameless]] | caption = Aeon | releasestatus = Maintained | releasemodel = Rolling | packagemanager = [[transactional-update]] | defaultdesktops = [[GNOME]] | usagetype = Desktop | architectures = x86-64 | website = [https://aeondesktop.github.io/# aeondesktop.github.io] }} Aeon is an immutable desktop Linux distribution based on [[openSUSE]]. It is a relatively small, low-maintenance system with automated daily updates, thus recommended for Linux beginners or "lazy developers". Some of the distribution's other features include a custom system installer called Transactional Installation Kit (TIK), a pre-configured [[GNOME]] desktop, out-of-the-box support for [[Flatpak]] packages, [[Distrobox]] configured to launch Tumbleweed containers, and automatic rollbacks to its last working state. d8ea91ef1a0c1ca26f31b6bae156f9b7e6ca2366 0 394 5829 5745 2026-07-08T20:11:28Z Lenni 429 Move Pixo OS out of list of UNIX-like OSes wikitext text/x-wiki These are some operating systems that '''do not''' use the [[Linux]] [[kernel]]. The list of [[BSD]] operating systems is on it's own respective page, as the list is much larger than any other list here. == Darwin Based == {| class="wikitable" |- ! OS !! Description |- | [[audioOS]] | an OS developed by Apple for their HomePod Products, forked from [[tvOS]] |- | [[iOS]] | an OS developed by Apple for their iPhone, iPod Touch and Early iPad and Apple TV Products |- | [[iPadOS]] | an OS developed by Apple made for their iPad products, forked from [[iOS]] |- | [[macOS]] | an OS developed by Apple, orignally called Mac OS X, it has been developed by Apple since 2001 |- | [[tvOS]] | an OS developed by Apple for their Apple TV products, forked from [[iOS]] |- | [[visionOS]] | an OS developed by Apple for their Apple Vision products, forked from [[iPadOS]] |- | [[watchOS]] | an OS developed by Apple for their Apple Watch Products, forked from [[iOS]] |- |} == Solaris Based == {| class="wikitable" |- ! OS !! Description |- | [[OpenIndiana]] | a continuation of the [[OpenSolaris]] operating system. It was conceived during the period of uncertainty following the [[Oracle]] takeover of [[Sun Microsystems]] |- | [[OpenSolaris]] | a discontinued open-source computer operating system for SPARC and x86 based systems, created by [[Sun Microsystems]] |- | [[Oracle Solaris]] | a proprietary Unix operating system developed by [[Sun Microsystems]], now owned by [[Oracle]] |- | [[Illumos]] | a partly free and open-source Unix operating system based on [[OpenSolaris]] |- |} == Other UNIX-like == {| class="wikitable" |- ! OS !! Description |- | [[Redox OS]] | A Unix-like microkernel-based operating system written in [[Rust]] |- | [[SerenityOS]] | a modern Unix-like operating system, with a look and feel that emulates 1990s operating systems |- | [[UnixWare]] | A proprietary [[UNIX|UNIX®]] operating system developed by Xinuos (previously SCO) |- | [[z/OS]] | IBM's flagship operating system for System z mainframes |- | [[GNU/Hurd]] | A fully [[POSIX]] compliant [[FLOSS|free]] operating system based on the [[GNU Mach microkernel]] |- |} == L4 based == {| class="wikitable" |- ! OS !! Description ! |- | [[SculptOS]] | A graphical dynamic OS based on the [[Genode]] OS framework that supports a variety of [[L4 microkernels]] and [[Linux]] | |- | [[LionsOS]] | A static OS based on the high assurance [[SeL4 microkernel]] developed by the [[Trustworthy Systems group]] | |- | [[L4Re]] | An OS that is maintained by Kernkonzept, it uses the [[Fiasco.OC]] microkernel which is developed by TU Dresden |- |} == Other Operating Systems == {| class="wikitable" |- ! OS !! Description ! |- | [[MS-DOS]] | A command-line operating system developed by Microsoft for early IBM-compatible personal computers | |- | [[FreeDOS]] | A set of [[FLOSS|free]] MS-DOS compatible software including a kernel and command interpreter | |- | [[OS/2]] | An operating system originally created as a joint venture between [[IBM]] and [[Microsoft]] designed to replace DOS | |- | [[ReactOS]] | An open source operating system compatible with [[Windows]] NT programs and [[drivers]] | |- | [[TempleOs|TempleOS]] | An independently developed operating system by [[Terry A. Davis]]. | |- | [[Windows]] | A proprietary graphical operating system developed and marketed by [[Microsoft]] |- | [[RISC OS]] | An open-source operating system designed in Cambridge, England by Acorn. First released in 1987, its origins can be traced back to the original team that developed the Arm microprocessor. |- |[[Pixo OS]] |Created by Pixo Inc and licensed to Apple for their iPod Products |} e38d4a5ded477901dee7ea47ab45799a0a28b89b 0 1379 5830 2026-07-09T17:38:21Z Asyncwashere 430 Created page with "[[Category:Software]] [[Category:Package_Managers]] {{SoftwareInfobox | title = Pkg Package Manager | releasestatus = Maintained | lastrelease = 2.7.5 | languages = [[C]], [[Sh]] | developers = The FreeBSD Project | website = https://www.freebsd.org/ | license = BSD 2-Clause License | sourcecode = https://github.com/freebsd/pkg }} '''Pkg''' (not to be confused with Termux's pkg) is the default [[Package Manager|package manager]] of [[FreeBSD]]. It is used to download..." wikitext text/x-wiki [[Category:Software]] [[Category:Package_Managers]] {{SoftwareInfobox | title = Pkg Package Manager | releasestatus = Maintained | lastrelease = 2.7.5 | languages = [[C]], [[Sh]] | developers = The FreeBSD Project | website = https://www.freebsd.org/ | license = BSD 2-Clause License | sourcecode = https://github.com/freebsd/pkg }} '''Pkg''' (not to be confused with Termux's pkg) is the default [[Package Manager|package manager]] of [[FreeBSD]]. It is used to download and install '''binary''' applications. Pkg does not come bundled with FreeBSD, instead each system has a placeholder (<code>/usr/sbin/pkg</code>) which will initiate the process of bootstrapping the actual package manager. == Overview == The table below will show a list of useful commands. Parameters will be encapsulated in braces (<code>[]</code>), required parameters will be prefixed by an asterisk (<code>*</code>).<ref> {{Cite|url=https://docs.freebsd.org/en/books/handbook/ports/|title=Installing Applications: Packages and Ports - FreeBSD wiki|accessdate=9. July 2026}}</ref> {| class="wikitable" |+Commonly used PKG commands !Command !Action |- |<code>pkg</code> | Required upon system installation to bootstrap <code> pkg </code> (internet connection required). |- |<code>pkg install *[package]</code> | Used to install packages. |- |<code>pkg update</code> | Updates the package repository. |- |<code>pkg search *[query]</code> | Used to search the repositories for installed packages. |- |<code>pkg info [package]</code> | Used to display information about installed packages. |- |<code> pkg fetch *[package]</code> | Used to fetch a package '''before''' installing it. |- | <code>pkg upgrade</code> | Used to update all installed packages to their latest versions. |- |<code>pkg audit</code> | Used to determine whether there are any vulnerabilities in installed packages. |- | <code>pkg delete *[package]</code> | Used to delete packages. |- | <code>pkg autoremove</code> | Used to remove dependencies which are no longer required by any other package on the system. |- | <code>pkg prime-list</code> | Used to list packages which were explicitly installed by the user, and not pulled in as a dependency. |- | <code>pkg clean</code> | Used to remove old packages that were stored in a cache directory. |- | <code>pkg lock *[package]</code> | Using this command, a user can "lock" a package and prevent it from being modified, deleted or reinstalled. |} == Ports == {{GuideWarning}} The Ports Collection is a repository of application sources, which can be compiled into packages (called Ports) on the system. [https://vuxml.freebsd.org/ Installation of third party software blindly can be dangerous, please check this link before doing so.] It is not advised to mix and match both regular <code>pkg</code> packages and Ports, as <code>pkg</code> uses earlier versions of software that either conflict with the installed Ports or can generally make the system unstable in conjunction with Ports. Ports cannot be installed with <code>pkg</code>, they must be compiled from the directory they were downloaded to (default: <code>/usr/ports</code>). == Configuration == '''Pkg''' can be configured by editing <code>/usr/local/etc/pkg.conf</code>. Lines prefixed by <code>#</code> are commented and will be ignored. == References == <references /> cc60c24839624821924eb25a3b43dd12b350ac6e 5831 5830 2026-07-09T17:46:09Z Asyncwashere 430 Switched the name of the package manager to use correct casing wikitext text/x-wiki {{DISPLAYTITLE:pkg}} [[Category:Software]] [[Category:Package_Managers]] {{SoftwareInfobox | title = pkg Package Manager | releasestatus = Maintained | lastrelease = 2.7.5 | languages = [[C]], [[Sh]] | developers = The FreeBSD Project | website = https://www.freebsd.org/ | license = BSD 2-Clause License | sourcecode = https://github.com/freebsd/pkg }} '''pkg''' (not to be confused with Termux's pkg) is the default [[Package Manager|package manager]] of [[FreeBSD]]. It is used to download and install '''binary''' applications. pkg does not come bundled with FreeBSD, instead each system has a placeholder (<code>/usr/sbin/pkg</code>) which will initiate the process of bootstrapping the actual package manager. == Overview == The table below will show a list of useful commands. Parameters will be encapsulated in braces (<code>[]</code>), required parameters will be prefixed by an asterisk (<code>*</code>).<ref> {{Cite|url=https://docs.freebsd.org/en/books/handbook/ports/|title=Installing Applications: Packages and Ports - FreeBSD wiki|accessdate=9. July 2026}}</ref> {| class="wikitable" |+Commonly used pkg commands !Command !Action |- |<code>pkg</code> | Required upon system installation to bootstrap <code> pkg </code> (internet connection required). |- |<code>pkg install *[package]</code> | Used to install packages. |- |<code>pkg update</code> | Updates the package repository. |- |<code>pkg search *[query]</code> | Used to search the repositories for installed packages. |- |<code>pkg info [package]</code> | Used to display information about installed packages. |- |<code> pkg fetch *[package]</code> | Used to fetch a package '''before''' installing it. |- | <code>pkg upgrade</code> | Used to update all installed packages to their latest versions. |- |<code>pkg audit</code> | Used to determine whether there are any vulnerabilities in installed packages. |- | <code>pkg delete *[package]</code> | Used to delete packages. |- | <code>pkg autoremove</code> | Used to remove dependencies which are no longer required by any other package on the system. |- | <code>pkg prime-list</code> | Used to list packages which were explicitly installed by the user, and not pulled in as a dependency. |- | <code>pkg clean</code> | Used to remove old packages that were stored in a cache directory. |- | <code>pkg lock *[package]</code> | Using this command, a user can "lock" a package and prevent it from being modified, deleted or reinstalled. |} == Ports == {{GuideWarning}} The Ports Collection is a repository of application sources, which can be compiled into packages (called Ports) on the system. [https://vuxml.freebsd.org/ Installation of third party software blindly can be dangerous, please check this link before doing so.] It is not advised to mix and match both regular <code>pkg</code> packages and Ports, as <code>pkg</code> uses earlier versions of software that either conflict with the installed Ports or can generally make the system unstable in conjunction with Ports. Ports cannot be installed with <code>pkg</code>, they must be compiled from the directory they were downloaded to (default: <code>/usr/ports</code>). == Configuration == '''pkg''' can be configured by editing <code>/usr/local/etc/pkg.conf</code>. Lines prefixed by <code>#</code> are commented and will be ignored. == References == <references /> f24eb557d56f1e6d9f7f0a3aeabb073c7241a743 5832 5831 2026-07-09T17:49:32Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DISPLAYTITLE:pkg}} [[Category:Software]] [[Category:Package_Managers]] {{SoftwareInfobox | title = pkg Package Manager | releasestatus = Maintained | lastrelease = 2.7.5 | languages = [[C]], [[Sh]] | developers = The FreeBSD Project | website = https://www.freebsd.org/ | license = BSD 2-Clause License | sourcecode = https://github.com/freebsd/pkg }} '''pkg''' (not to be confused with Termux's pkg) is the default [[Package Manager|package manager]] of [[FreeBSD]]. It is used to download and install '''binary''' applications. pkg does not come bundled with FreeBSD, instead each system has a placeholder (<code>/usr/sbin/pkg</code>) which will initiate the process of bootstrapping the actual package manager. == Overview == The table below will show a list of useful commands. Parameters will be encapsulated in braces (<code>[]</code>), required parameters will be prefixed by an asterisk (<code>*</code>).<ref> {{Cite|url=https://docs.freebsd.org/en/books/handbook/ports/|title=Installing Applications: Packages and Ports - FreeBSD wiki|accessdate=9. July 2026}}</ref> {| class="wikitable" |+Commonly used pkg commands !Command !Action |- |<code>pkg</code> | Required upon system installation to bootstrap <code> pkg </code> (internet connection required). |- |<code>pkg install *[package]</code> | Used to install packages. |- |<code>pkg update</code> | Updates the package repository. |- |<code>pkg search *[query]</code> | Used to search the repositories for installed packages. |- |<code>pkg info [package]</code> | Used to display information about installed packages. |- |<code> pkg fetch *[package]</code> | Used to fetch a package '''before''' installing it. |- | <code>pkg upgrade</code> | Used to update all installed packages to their latest versions. |- |<code>pkg audit</code> | Used to determine whether there are any vulnerabilities in installed packages. |- | <code>pkg delete *[package]</code> | Used to delete packages. |- | <code>pkg autoremove</code> | Used to remove dependencies which are no longer required by any other package on the system. |- | <code>pkg prime-list</code> | Used to list packages which were explicitly installed by the user, and not pulled in as a dependency. |- | <code>pkg clean</code> | Used to remove old packages that were stored in a cache directory. |- | <code>pkg lock *[package]</code> | Using this command, a user can "lock" a package and prevent it from being modified, deleted or reinstalled. |} == Ports == {{GuideWarning}} The Ports Collection is a repository of application sources, which can be compiled into packages (called Ports) on the system. [https://vuxml.freebsd.org/ Installation of third party software blindly can be dangerous, please check this link before doing so.] It is not advised to mix and match both regular <code>pkg</code> packages and Ports, as <code>pkg</code> uses earlier versions of software that either conflict with the installed Ports or can generally make the system unstable in conjunction with Ports. Ports cannot be installed with <code>pkg</code>, they must be compiled from the directory they were downloaded to (default: <code>/usr/ports</code>). == Configuration == '''pkg''' can be configured by editing <code>/usr/local/etc/pkg.conf</code>. Lines prefixed by <code>#</code> are commented and will be ignored. == References == <references /> 9dc2144bd32e1d9b796d6640bc7b5410cf12eab7 0 575 5833 5087 2026-07-11T10:28:13Z Imnotgoodatnames 121 emacs is primarily a text editor, and that's what it should be introduced as wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.2, Aug 14, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] GNU Emacs is a free/libre text editor and interpreter for the Emacs Lisp language, with extensions to assist with various other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, make sure to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. ''Also see [[Vim]].'' == References == c345b334f8405800c46fdd8b8f6b4b08113c6339 5836 5833 2026-07-11T11:24:47Z Imnotgoodatnames 121 optional actions shouldn't be worded as if they're required, even if they are recommended wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.2, Aug 14, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] GNU Emacs is a free/libre text editor and interpreter for the Emacs Lisp language, with extensions to assist with various other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, it's strongly recommended to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. ''Also see [[Vim]].'' == References == 69849a3dd78a5c7de0ced51191661b68e0cc4828 3000 577 5834 4067 2026-07-11T11:14:49Z Imnotgoodatnames 121 Added quick compilation guide, added download info for macOS, MS Windows and MS-DOS wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is recommended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight lang="text"># Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland</syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight lang="text"># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then install Emacs with the following command:<syntaxhighlight lang="text"> # emerge app-editors/emacs </syntaxhighlight> === NixOS === You can install Emacs in a variety of ways in NixOS. A common way to install Emacs is to append the following code to your NixOS configuration:<syntaxhighlight lang="nix" line="1">{ services.emacs = { enable = true; /* There are more options you can set, please read https://search.nixos.org/options?channel=unstable&query=services.emacs for more information. */ }; }</syntaxhighlight>You can then rebuild the system using your desired method—most commonly with <code>nixos-rebuild switch</code>—to use a system configuration which has Emacs installed. === FreeBSD === Emacs be installed on FreeBSD by using either pkg or ports. If you want a binary package at the absence of deeper customization, then you can use either of the following commands:<syntaxhighlight lang="text"> ## Installing Emacs (X11) # pkg install emacs ## Installing Emacs (Wayland) # pkg install emacs-wayland ## More flavours can be found here: https://www.freshports.org/editors/emacs/ </syntaxhighlight>If you are willing to compile Emacs for deeper customization, then you can use the editors/emacs port. This part is expected for people to have used ports in the past; read [https://docs.freebsd.org/en/books/handbook/ports/#ports-using Chapter 4 of the FreeBSD Handbook] for information on how to use ports if desired. And with that, you can use the following commands to build the Emacs port:<syntaxhighlight lang="text"> $ cd /usr/ports/editors/emacs # make config # make install clean </syntaxhighlight> === macOS === macOS doesn't have an official package manager or an official GNU Emacs package. However, GNU Emacs can be installed from homebrew using either of the following <code>% brew install emacs</code> <code>% brew install emacs-app</code> Alternatively, GNU Emacs can be compiled for the macOS desktop using the <code>--with-ns</code> configuration option. === Microsoft Windows === GNU Emacs can be downloaded for Microsoft Windows from a [https://ftpmirror.gnu.org/emacs/windows GNU ftp mirror] (recommended) or the primary GNU ftp server. === MS-DOS === GNU Emacs for Microsoft DOS and compatible operating systems can be downloaded from [https://www.delorie.com/djgpp/getting.html a DJGPP ftp mirror] at current/v2gnu/em3002b.zip == Installing from Source == GNU Emacs can be built from source using the standard Autotools + Make procedure. First, make sure the host system has all the dependencies required for Emacs itself and for the desired Emacs features (such as [[X11]] support). The source code for GNU Emacs releases can be downloaded from a [https://ftpmirror.gnu.org/emacs GNU ftp mirror] (recommended) or from the primary gnu ftp server. Alternatively, the current GNU Emacs development source can be cloned using git with <code>$ git clone git://git.git.savannah.gnu.org/emacs.git</code> To build GNU Emacs from source, run the following commands in the source tree: <syntaxhighlight lang="text"> $./autogen.sh #unnecessary if building from release tarball $ ./configure [configuration options] $ make $ make install #optional; run make clean after make install to free some storage space </syntaxhighlight> running <code>$ ./configure --help</code> will print all available configuration options. <code>$ make install</code> will install Emacs to /usr/local/bin by default on UNIX-like systems. A different installation prefix can be specified with the <code>--prefix=/path/to/prefix/dir</code> configuration option. A more detailed explanation is available at [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] in its Savannah repository. == References == 14e659b44660dd66b82d2a4ac6cc6992a80b393a 5835 5834 2026-07-11T11:19:21Z Imnotgoodatnames 121 wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is recommended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight lang="text"># Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland</syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight lang="text"># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then install Emacs with the following command:<syntaxhighlight lang="text"> # emerge app-editors/emacs </syntaxhighlight> === NixOS === You can install Emacs in a variety of ways in NixOS. A common way to install Emacs is to append the following code to your NixOS configuration:<syntaxhighlight lang="nix" line="1">{ services.emacs = { enable = true; /* There are more options you can set, please read https://search.nixos.org/options?channel=unstable&query=services.emacs for more information. */ }; }</syntaxhighlight>You can then rebuild the system using your desired method—most commonly with <code>nixos-rebuild switch</code>—to use a system configuration which has Emacs installed. === FreeBSD === Emacs be installed on FreeBSD by using either pkg or ports. If you want a binary package at the absence of deeper customization, then you can use either of the following commands:<syntaxhighlight lang="text"> ## Installing Emacs (X11) # pkg install emacs ## Installing Emacs (Wayland) # pkg install emacs-wayland ## More flavours can be found here: https://www.freshports.org/editors/emacs/ </syntaxhighlight>If you are willing to compile Emacs for deeper customization, then you can use the editors/emacs port. This part is expected for people to have used ports in the past; read [https://docs.freebsd.org/en/books/handbook/ports/#ports-using Chapter 4 of the FreeBSD Handbook] for information on how to use ports if desired. And with that, you can use the following commands to build the Emacs port:<syntaxhighlight lang="text"> $ cd /usr/ports/editors/emacs # make config # make install clean </syntaxhighlight> === macOS === macOS doesn't have an official package manager or an official GNU Emacs package. However, GNU Emacs can be installed from homebrew using either of the following <code>% brew install emacs</code> <code>% brew install emacs-app</code> Alternatively, GNU Emacs can be compiled for the macOS desktop using the <code>--with-ns</code> configuration option. === Microsoft Windows === GNU Emacs can be downloaded for Microsoft Windows from a [https://ftpmirror.gnu.org/emacs/windows GNU ftp mirror] (recommended) or the primary GNU ftp server. === MS-DOS === GNU Emacs for Microsoft DOS and compatible operating systems can be downloaded from [https://www.delorie.com/djgpp/getting.html a DJGPP ftp mirror] at current/v2gnu/em3002b.zip == Installing from Source == GNU Emacs can be built from source using the standard Autotools + Make procedure. First, make sure the host system has all the dependencies required for Emacs itself and for the desired Emacs features (such as [[X11]] support). The source code for GNU Emacs releases can be downloaded from a [https://ftpmirror.gnu.org/emacs GNU ftp mirror] (recommended) or from the primary gnu ftp server. Alternatively, the current GNU Emacs development source can be cloned using git with <code>$ git clone git://git.git.savannah.gnu.org/emacs.git</code> To build GNU Emacs from source, run the following commands in the source tree: <syntaxhighlight lang="text"> $./autogen.sh #unnecessary if building from release tarball $ ./configure [configuration options] $ make $ make install #optional; run make clean after make install to free some storage space </syntaxhighlight> running <code>$ ./configure --help</code> will print all available configuration options. <code>$ make install</code> will install Emacs to /usr/local/bin by default on UNIX-like systems. A different installation prefix can be specified with the <code>--prefix=/path/to/prefix/dir</code> configuration option. A more detailed explanation is available at [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] in its Savannah repository. == References == f340ed6959b793647819afa9fe70324cfb6da6a6 5840 5835 2026-07-11T17:44:49Z Asyncwashere 430 Added a section on GnuTLS. wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is recommended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight lang="text"># Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland</syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight lang="text"># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then install Emacs with the following command:<syntaxhighlight lang="text"> # emerge app-editors/emacs </syntaxhighlight> === NixOS === You can install Emacs in a variety of ways in NixOS. A common way to install Emacs is to append the following code to your NixOS configuration:<syntaxhighlight lang="nix" line="1">{ services.emacs = { enable = true; /* There are more options you can set, please read https://search.nixos.org/options?channel=unstable&query=services.emacs for more information. */ }; }</syntaxhighlight>You can then rebuild the system using your desired method—most commonly with <code>nixos-rebuild switch</code>—to use a system configuration which has Emacs installed. === FreeBSD === Emacs be installed on FreeBSD by using either pkg or ports. If you want a binary package at the absence of deeper customization, then you can use either of the following commands:<syntaxhighlight lang="text"> ## Installing Emacs (X11) # pkg install emacs ## Installing Emacs (Wayland) # pkg install emacs-wayland ## More flavours can be found here: https://www.freshports.org/editors/emacs/ </syntaxhighlight>If you are willing to compile Emacs for deeper customization, then you can use the editors/emacs port. This part is expected for people to have used ports in the past; read [https://docs.freebsd.org/en/books/handbook/ports/#ports-using Chapter 4 of the FreeBSD Handbook] for information on how to use ports if desired. And with that, you can use the following commands to build the Emacs port:<syntaxhighlight lang="text"> $ cd /usr/ports/editors/emacs # make config # make install clean </syntaxhighlight> === macOS === macOS doesn't have an official package manager or an official GNU Emacs package. However, GNU Emacs can be installed from homebrew using either of the following <code>% brew install emacs</code> <code>% brew install emacs-app</code> Alternatively, GNU Emacs can be compiled for the macOS desktop using the <code>--with-ns</code> configuration option. === Microsoft Windows === GNU Emacs can be downloaded for Microsoft Windows from a [https://ftpmirror.gnu.org/emacs/windows GNU ftp mirror] (recommended) or the primary GNU ftp server. === MS-DOS === GNU Emacs for Microsoft DOS and compatible operating systems can be downloaded from [https://www.delorie.com/djgpp/getting.html a DJGPP ftp mirror] at current/v2gnu/em3002b.zip == Installing from Source == GNU Emacs can be built from source using the standard Autotools + Make procedure. First, make sure the host system has all the dependencies required for Emacs itself and for the desired Emacs features (such as [[X11]] support). The source code for GNU Emacs releases can be downloaded from a [https://ftpmirror.gnu.org/emacs GNU ftp mirror] (recommended) or from the primary gnu ftp server. Alternatively, the current GNU Emacs development source can be cloned using git with <code>$ git clone git://git.git.savannah.gnu.org/emacs.git</code> For access to internet resources over <code>https</code>, GNU Emacs must be compiled with [https://ftp.gnu.org/gnu/gnutls/ GnuTLS]. It can still be compiled without, but external package repositories which rely on a secure connection such as [https://melpa.org/ melpa] will not function. To build GNU Emacs from source, run the following commands in the source tree: <syntaxhighlight lang="text"> $./autogen.sh #unnecessary if building from release tarball $ ./configure [configuration options] $ make $ make install #optional; run make clean after make install to free some storage space </syntaxhighlight> running <code>$ ./configure --help</code> will print all available configuration options. <code>$ make install</code> will install Emacs to /usr/local/bin by default on UNIX-like systems. A different installation prefix can be specified with the <code>--prefix=/path/to/prefix/dir</code> configuration option. A more detailed explanation is available at [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] in its Savannah repository. == References == 995139dfa2111fadf115dbfa8c01e2c8c540386f 5841 5840 2026-07-12T09:35:02Z Imnotgoodatnames 121 added more compilation information wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is recommended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight lang="text"># Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland</syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight lang="text"># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then install Emacs with the following command:<syntaxhighlight lang="text"> # emerge app-editors/emacs </syntaxhighlight> === NixOS === You can install Emacs in a variety of ways in NixOS. A common way to install Emacs is to append the following code to your NixOS configuration:<syntaxhighlight lang="nix" line="1">{ services.emacs = { enable = true; /* There are more options you can set, please read https://search.nixos.org/options?channel=unstable&query=services.emacs for more information. */ }; }</syntaxhighlight>You can then rebuild the system using your desired method—most commonly with <code>nixos-rebuild switch</code>—to use a system configuration which has Emacs installed. === FreeBSD === Emacs be installed on FreeBSD by using either pkg or ports. If you want a binary package at the absence of deeper customization, then you can use either of the following commands:<syntaxhighlight lang="text"> ## Installing Emacs (X11) # pkg install emacs ## Installing Emacs (Wayland) # pkg install emacs-wayland ## More flavours can be found here: https://www.freshports.org/editors/emacs/ </syntaxhighlight>If you are willing to compile Emacs for deeper customization, then you can use the editors/emacs port. This part is expected for people to have used ports in the past; read [https://docs.freebsd.org/en/books/handbook/ports/#ports-using Chapter 4 of the FreeBSD Handbook] for information on how to use ports if desired. And with that, you can use the following commands to build the Emacs port:<syntaxhighlight lang="text"> $ cd /usr/ports/editors/emacs # make config # make install clean </syntaxhighlight> === macOS === macOS doesn't have an official package manager or an official GNU Emacs package. However, GNU Emacs can be installed from homebrew using either of the following <code>% brew install emacs</code> <code>% brew install emacs-app</code> Alternatively, GNU Emacs can be compiled for the macOS desktop using the <code>--with-ns</code> configuration option. === Microsoft Windows === GNU Emacs can be downloaded for Microsoft Windows from a [https://ftpmirror.gnu.org/emacs/windows GNU ftp mirror] (recommended) or the primary GNU ftp server. === MS-DOS === GNU Emacs for Microsoft DOS and compatible operating systems can be downloaded from [https://www.delorie.com/djgpp/getting.html a DJGPP ftp mirror] at current/v2gnu/em3002b.zip Alternatively, instructions for building GNU Emacs for DOS on DOS or Windows 9x are located in the GNU Emacs source tree at msdos/INSTALL. == Installing from Source == There are multiple uses and advantages to installing GNU Emacs from source. The most obvious one is the ability to install it on systems that either do not package it themselves at all, or have an older version than the desired one. Building Emacs from source also enables a far deeper level of customization using the various configure options that can be enabled or disabled in the build process. For example, it enables building Emacs to use various graphical toolkits such as [[GTK]], [[Motif]], pure GTK (for Wayland), pure [[X11]] or to not use a GUI at all and remain an exclusively [[TUI]] program. GNU Emacs can be built from source using the standard Autotools + Make procedure. First, make sure the host system has all the dependencies required for Emacs itself and for the desired Emacs features (such as X11 support). The source code for GNU Emacs releases can be downloaded from a [https://ftpmirror.gnu.org/emacs GNU ftp mirror] (recommended) or from the primary gnu ftp server. Alternatively, the current GNU Emacs development source can be cloned using git with <code>$ git clone git://git.git.savannah.gnu.org/emacs.git</code> For access to internet resources over <code>https</code>, GNU Emacs must be compiled with [https://ftp.gnu.org/gnu/gnutls/ GnuTLS]. It can still be compiled without, but external package repositories which rely on a secure connection such as [https://melpa.org/ melpa] will not function. To build GNU Emacs from source, run the following commands in the source tree: <syntaxhighlight lang="text"> $./autogen.sh #unnecessary if building from release tarball $ ./configure [configuration options] $ make $ make install #optional; run make clean after make install to free some storage space </syntaxhighlight> running <code>$ ./configure --help</code> will print all available configuration options. <code>$ make install</code> will install Emacs to /usr/local/bin by default on UNIX-like systems. A different installation prefix can be specified with the <code>--prefix=/path/to/prefix/dir</code> configuration option. A more detailed overview is available at [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] in the GNU Emacs Savannah git repository. == References == 829f8c860a4aab3431c5ccdd9c494eb86043acb5 5842 5841 2026-07-12T15:16:47Z Imnotgoodatnames 121 Added table of notable configuration flags wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is recommended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight lang="text"># Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland</syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight lang="text"># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then install Emacs with the following command:<syntaxhighlight lang="text"> # emerge app-editors/emacs </syntaxhighlight> === NixOS === You can install Emacs in a variety of ways in NixOS. A common way to install Emacs is to append the following code to your NixOS configuration:<syntaxhighlight lang="nix" line="1">{ services.emacs = { enable = true; /* There are more options you can set, please read https://search.nixos.org/options?channel=unstable&query=services.emacs for more information. */ }; }</syntaxhighlight>You can then rebuild the system using your desired method—most commonly with <code>nixos-rebuild switch</code>—to use a system configuration which has Emacs installed. === FreeBSD === Emacs be installed on FreeBSD by using either pkg or ports. If you want a binary package at the absence of deeper customization, then you can use either of the following commands:<syntaxhighlight lang="text"> ## Installing Emacs (X11) # pkg install emacs ## Installing Emacs (Wayland) # pkg install emacs-wayland ## More flavours can be found here: https://www.freshports.org/editors/emacs/ </syntaxhighlight>If you are willing to compile Emacs for deeper customization, then you can use the editors/emacs port. This part is expected for people to have used ports in the past; read [https://docs.freebsd.org/en/books/handbook/ports/#ports-using Chapter 4 of the FreeBSD Handbook] for information on how to use ports if desired. And with that, you can use the following commands to build the Emacs port:<syntaxhighlight lang="text"> $ cd /usr/ports/editors/emacs # make config # make install clean </syntaxhighlight> === macOS === macOS doesn't have an official package manager or an official GNU Emacs package. However, GNU Emacs can be installed from homebrew using either of the following <code>% brew install emacs</code> <code>% brew install emacs-app</code> Alternatively, GNU Emacs can be compiled for the macOS desktop using the <code>--with-ns</code> configuration option. === Microsoft Windows === GNU Emacs can be downloaded for Microsoft Windows from a [https://ftpmirror.gnu.org/emacs/windows GNU ftp mirror] (recommended) or the primary GNU ftp server. === MS-DOS === GNU Emacs for Microsoft DOS and compatible operating systems can be downloaded from [https://www.delorie.com/djgpp/getting.html a DJGPP ftp mirror] at current/v2gnu/em3002b.zip Alternatively, instructions for building GNU Emacs for DOS on DOS or Windows 9x are located in the GNU Emacs source tree at msdos/INSTALL. == Installing from Source == There are multiple uses and advantages to installing GNU Emacs from source. The most obvious one is the ability to install it on systems that either do not package it themselves at all, or have an older version than the desired one. Building Emacs from source also enables a far deeper level of customization using the various configure options that can be enabled or disabled in the build process. For example, it enables building Emacs to use various graphical toolkits such as [[GTK]], [[Motif]], pure GTK (for Wayland), pure [[X11]] or to not use a GUI at all and remain an exclusively [[TUI]] program. GNU Emacs can be built from source using the standard Autotools + Make procedure. First, make sure the host system has all the dependencies required for Emacs itself and for the desired Emacs features (such as X11 support). The source code for GNU Emacs releases can be downloaded from a [https://ftpmirror.gnu.org/emacs GNU ftp mirror] (recommended) or from the primary gnu ftp server. Alternatively, the current GNU Emacs development source can be cloned using git with <code>$ git clone git://git.git.savannah.gnu.org/emacs.git</code> For access to internet resources over <code>https</code>, GNU Emacs must be compiled with [https://ftp.gnu.org/gnu/gnutls/ GnuTLS]. It can still be compiled without, but external package repositories which rely on a secure connection such as [https://melpa.org/ melpa] will not function. To build GNU Emacs from source, run the following commands in the source tree: <syntaxhighlight lang="text"> $./autogen.sh #unnecessary if building from release tarball $ ./configure [configuration options] $ make $ make install #optional; run make clean after make install to free some storage space </syntaxhighlight> running <code>$ ./configure --help</code> will print all available configuration options. ===Notable configuration options=== This is a list of notable configuration options for GNU Emacs and their uses. Keep in mind that --with-feature=no disables the 'feature' feature and that --without-feature is the same as --with-feature=no. {| class="wikitable" !Configure flag !effect |- |<code>--prefix=PREFIX |Installs Emacs to the directory PREFIX during <code>make install</code> (eg. <code>--prefix=/home/username</code> will install files into /home/username/bin, /home/username/lib etc. |- |<code>--with-x |Compiles GNU Emacs with X Windowing System support. Necessary for a graphical interface on X11. |- |<code>--with-x-toolkit=TOOLKIT |Builds Emacs with the TOOLKIT X graphical toolkit. TOOLKIT can be 'yes', 'gtk', 'gtk2', 'gtk3', 'lucid', 'athena', or 'motif'. Disabling this feature (setting it to 'no') will build Emacs against pure Xlib. |- |<code>--with-pgtk |Builds the "Pure GTK" toolkit version of Emacs, enabling native Wayland support but potentially making X support unstable. |- |<code>--with-gpm |Enables support for gpm, enabling support for the mouse in the Linux virtual terminal. |- |<code>--with-ns |If on macOS, builds Emacs for Cocoa; otherwise builds Emacs for [[GNUstep]]. |- |<code>--with-android |Builds Emacs for Android and packages it in an Android .apk file. |} A more detailed overview is available at [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] in the GNU Emacs Savannah git repository. == References == 5d2b9482a175bea356aff2c5cc6d6247dfd01a8d 0 1373 5837 5817 2026-07-11T11:37:40Z Imnotgoodatnames 121 GNU Hurd is the kernel of the GNU/Hurd operating system. Also removed duplicate links to the same article. wikitext text/x-wiki {{Stub}} <!-- distroinfobox, more info --> [[Category:Misc Operating Systems]] {{DistributionInfobox | architectures = i386, x86_64 | caption = The GNU Hurd logo | defaultdesktops = [[GNOME]], [[Xfce]], [[Window Maker]], [[Fluxbox]], [[IceWM]], [[Openbox]] | image = | packagemanager = [[dpkg]]/[[apt]] ([[Debian GNU/Hurd]]), [[Guix]] | releasemodel = Rolling | releasestatus = Experimental | title = GNU/Hurd | usagetype = Research, Development | website = [https://www.gnu.org/software/hurd/ gnu.org/software/hurd] }} '''GNU/Hurd''' is an unofficial name for the [[GNU]] operating system running on the '''GNU Hurd''' kernel. GNU Hurd (also referred to as "The Hurd" on GNU's website) is the GNU project's replacement for the [[UNIX]] operating system kernel.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's official Hurd documentation]</ref> It is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's description of Hurd]</ref> Essentially, The Hurd consists of a set of protocols and server processes (also known as daemons) that run on the GNU [[Mach]] microkernel. This means it differentiates from the [[Linux]] kernel, which is [[monolithic]].<ref>[https://itsfoss.com/news/gnu-hurd-progress-report/ ItsFOSS news report on GNU/Hurd]</ref> It has been in development since 1990, by the [[GNU]] project.<ref>[https://en.wikipedia.org/wiki/GNU_Hurd The Wikipedia entry for GNU Hurd]</ref> === History === '''Richard Stallman''' founded the GNU project in September 1983 with a goal to create a free GNU operating system.<ref>[https://cs.stanford.edu/people/eroberts/courses/cs181/projects/2000-01/open-source/gnu.htm#:~:text=In%201983,%20the%20GNU%20Project,up%20by%20proprietary%20software%20vendors. The history of the GNU project]</ref> Initially, all the necessary components needed for kernel development were made. By 1989, the [[GPL]] came into being, and the only major missing component was the [[kernel]], hence why they added the GNU operating system to [[Linux]] until they had their own kernel.<ref>[https://www.gnu.org/gnu/linux-and-gnu.html "Linux and GNU" entry on GNU's website]</ref> After this, development on the Hurd started after an abandoned kernel attempt, based on the [[TRIX]] operating system.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd History: How it started]</ref> According to the initial architect and founder of Hurd, '''Thomas Bushnell''', one of their early plans was to adopt and build on the [[4.4BSD]]-Lite kernel.<ref>[https://web.archive.org/web/20230710085615/http://www.groklaw.net/article.php?story=20050727225542530 "The Daemon, the GNU and the Penguin"]</ref> Later on from this, Richard Stallman proposed the use of the [[Mach]] microkernel, however this was delayed due to concern on whether the [[Mach]] code would be released under a suitable license.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd's history]</ref> Up until now, the development of Hurd had been relatively fast. However, with the release of the free [[Linux]] kernel in 1991, development slowed heavily, but did not stop. GNU's [[userland]] components were quickly put together with the [[Linux]] kernel to create operating systems based on the [[Linux]] kernel ([[Linux distributions]]). === References === b1c3d542750f177fb9d84154181e46202fe9ccdb 0 1005 5838 4272 2026-07-11T12:13:09Z Imnotgoodatnames 121 All Things Linux is no more wikitext text/x-wiki {{Needs Citations}} A variety of ways for installing [[software]] are available on most [[Unix]]-like systems, which will be explained below. == Software Repositories == :''Main Article: [[Repository]]'' Software programs may be downloaded from a centralised software [[repository]], possibly in the format of [[package]]s or [[binary|binaries]]. This process could be manual or automatic — users may choose to download these software manually instead of using automation tools. In many cases however, the word ''repository'' refers to the latter, where a ''package manager'' is required to extract, decode, and install the contents of a package, as explained in the next section. [[File:KDE Discover home page.png|right|thumb|The home page of the [[KDE]] [[Discover]] program, showing popular and recommended software.]] === Package Managers === :''Main Article: [[Package manager]]'' Software distributed in the form of '''software packages''' may be installed via various ''package managers''. Some package managers are specific to a [[Linux Distributions|distribution]] (or a branch of distributions), while others may be used across different distributions or even different [[Operating System|operating system]]s. On this wiki, the start of a distribution page contains an info box indicating its main supported package managers. Consult the corresponding pages on how to use them. In many cases this is the preferred way of installing software, as it's convenient to update all installed packages at once. For distribution-specific package managers, the packages are usually provided by the same distributions maintainers, making package breakages very unlikely. For package managers that ship packages directly provided by upstream (i.e. the maintainers of the software), the packages are usually more up-to-date with minimal security concerns, and upstream support is usually better. ==== Distribution Package Managers ==== Some package formats are specific to distributions. For [[Debian]]-based distributions, [[dpkg]] is used, and for [[Red Hat]] based distributions, [[rpm]] is used. In most cases, the matching package format must be used, otherwise installation is not possible. [[File:Flathub main website dark.png|right|thumb|The Flathub home featuring different flatpak packages]] ==== Cross-platform Package Managers ==== Some package managers like [[flatpak]] and [[snap]] provide software support for different distributions, in the format of [[sandbox]]ing. While other repositories are available, the mainstream repo for Flatpak is [[Flathub]], which contains both [[open source]] and [[proprietary]] software. For snap, [[Canonical]] [[Snapcraft]] is the default snap repository. Common package managers that do not involve sandboxing include [[brew]], [[nix]]. Some [[Programming languages]] provide their own package manager such as [[pip]] and [[cargo]]. [[File:AppImageHub home page.jpg|left|thumb|Home page of AppImageHub showing different software categories]] == AppImages == :''Main Article: [[AppImage]]'' When a software is not available as a package or in a repository, usually the second option is to use an '''AppImage''' provided by upstream. The same AppImage may be run on most [[Linux]] distributions as long as the [[architecture]] is correct. '''AppImages do not support updates'''. In many cases, users are required to download a newer version from upstream in order to update their AppImages. Software in AppImage formats are also significantly less optimised compared to ones provided by corresponding distributions. Some third-party services like [[AppImageHub]] provide centralised repositories of software for users to download manually. <div style="clear: both"></div> == Binaries == :''Main Article: [[Executable]]'' Sometimes upstream provides pre-compiled binaries (possibly in a [[tar]]ball) for users to download directly. These binaries are usually optimised to some degree, but may not run on obscure setups (e.g. older systems). == Manual Compilation == If the source code is available, users may manually [[compile]] the program. This produces an executable most optimised for the system, and possibly has the highest chance of working correctly. The major downside however is that this requires technical knowledge and takes time. == Tips, Tricks & Troubleshooting == === When NOT to use Flatpak === Refrain from installing the following types of software via flatpak and/or other sandboxing package managers. {| class="wikitable" ! Software !! Reason |- | [[Terminal]] emulators | These often only work properly when run directly on the host system. |- | [[CLI]]/[[TUI]] applications | The UX of flatpak isn't optimized for these types of applications. |- | Modded/Multi-instance game launchers (e.g. Minecraft launchers) | May require access to system libraries, and can be better managed by the user when not sandboxed. For example Minecraft launchers can easily access multiple [[JRE]] installations when not sandboxed. |- | Other appliactions that require manual modification of data files | Requires user to modify its data files regularly, applies in the same above case. |- | Applications that suffer major performance or technical issues due to sandboxing ([[IDE]]s, [[text editor]]s, [[file manager]]s, [[DAW]]s and other applications that rely on native [[plugin]] support like [[VST]]s or [[LV2]], etc.) | Usually require systems libraries to be present to work properly. |- | System components | Part of the [[OS]] |- | System [[library|libraries]] | Required to build or use the aforementioned packages |} === Finding Packages === The '''third-party''' websites listed in this section are '''unaffiliated''' with FOSS Wiki, and provide instructions that may be '''potentially dangerous''', which readers should understand clearly before proceeding with caution. [[File:Command-not-found-com_vim_page.png|left|thumb|The vim page on [https://command-not-found.com/vim command-not-found.com]<nowiki/>]] [https://command-not-found.com/ command-not-found.com] may be used to search for common command-line utilities. While it provides command-line specific instructions for mainstream distributions, other distributions are not supported, and only a small set of packages are registered. [[File:Pkgs.org_search_zed.png|right|thumb|Searching ''Zed'' in package summaries on pkgs.org]] [[pkgs.org]] [https://pkgs.org] provides command-line instructions for installing packages, alongside package information, with better UX for searching packages. Try searching for <code>/usr/bin/''binname''</code> when in doubt. Alternatively, [[Repology]] [https://repology.org] provides better coverage since it includes more third party repositories (notably the [[AUR]]), but comes with worse UX for searching packages (i.e. ''projects'' in Repology terms). Note that the former does not include Canonical Snapcraft [https://snapcraft.io], while the latter supports neither Flathub [https://flathub.org] nor Snapcraft. Some distributions such as [[OpenSUSE]] [https://search.opensuse.org/packages/] also provide dedicated websites for finding packages provided by the distributions. === Missing or Broken Distribution Packages === When a package does not exist or breaks, bug reports or requests should be given to repository maintainers. Avoid reporting directly to upstream maintainers unless they directly maintain the packages in question (which applies to many Flathub packages). In the meantime, '''advanced''' users could try to mitigate the issue: ; Missing runtime dynamic libraries : In case of [[wikipedia:Dynamic linker|dynamically link]]ed programming languages, you may see the following errors:<syntaxhighlight lang="shell-session"> /usr/bin/my_program: error while loading shared libraries: libexample.so.0: cannot open shared object file: No such file or directory /usr/bin/my_program: symbol lookup error: /usr/lib64/libexample.so.0: undefined symbol: some_example_symbol_123</syntaxhighlight> : The former error indicates that the library required is not installed, so you can find the package that provides the dynamic library and install it, e.g. with pkgs.org or your package manager: ([[dnf]] example)<syntaxhighlight lang="shell-session"> # dnf install 'libexample.so.0()(64bit)' </syntaxhighlight> : For other package formats that do not support ''provides'': :# search the RPM provides on pkgs.org :# click into any RPM packages :# go to the files section and copy the full [[soname]] [[path]] (e.g. <code>/usr/lib64/libexample.so.0</code>) :# paste the file path into the search bar to search again : If the library could not be found, the compiled executable is probably out of date. : The latter error is a result of [[wikipedia:Application binary interface|ABI]] mismatch, and can only be solved by obtaining the correct library version. Make sure your system is up to date, then contact the package maintainer of <code>my_program</code>. Usually this indicates the program (<code>my_program</code> in this case) needs to be recompiled. ; Missing modules for scripting languages : For software written in scripting languages, you may see the following errors:<syntaxhighlight lang="shell-session"> $ example_python_program Traceback (most recent call last): ... ImportError: No module named my_module $ example_nodejs_program Error: Cannot find module 'my_module' ... </syntaxhighlight> : These modules may be installed manually in the meantime: ([[apt]]/[[pacman]] example)<syntaxhighlight lang="shell-session"> # apt install python3-my-module # pacman -Syu node-my-module </syntaxhighlight> e2ab63bf31ae8940f04509e1f7e15cd1eb7130c0 0 1380 5839 2026-07-11T16:45:40Z Lawl 419 secureblue page wikitext text/x-wiki '''Secureblue''' is a security-focused desktop and server [[Linux]] [[operating system]], developed as an open-source project.<ref>[https://secureblue.dev/ Secureblue's official website]</ref> It is built from [[Fedora Linux]], as it ships with certain security beneficial tools such as [[SELinux]], which are enabled by default. Secureblue is designed for users whose main priority is using Linux, and second priority is security. Secureblue does not strive to be the most secure operating system out there, and is rather aimed at being a usable, secure Linux desktop. === Features === Secureblue ships with many tools and features to allow users to achieve a secure Linux desktop. These features include: * [[Trivalent]] browser shipped by default * Global [[hardened_malloc]], including for [[Flatpak]] * Kernel hardening via [[sysctl]] and kernel arguments * Automatic blacklisting of numerous unused kernel modules, reducing attack surface * ujust tooling being shipped by default, allowing for easy hardening * And many, many more. When putting all this, along with other features, together, you end up with an incredibly secure Linux distribution, suitable for both desktop and server use. 21a99caf9b71e76d59fe79cb3ef8812e4c56001f 5869 5839 2026-07-18T02:51:26Z PhantasNick 291 Stub wikitext text/x-wiki {{Stub}} '''Secureblue''' is a security-focused desktop and server [[Linux]] [[operating system]], developed as an open-source project.<ref>[https://secureblue.dev/ Secureblue's official website]</ref> It is built from [[Fedora Linux]], as it ships with certain security beneficial tools such as [[SELinux]], which are enabled by default. Secureblue is designed for users whose main priority is using Linux, and second priority is security. Secureblue does not strive to be the most secure operating system out there, and is rather aimed at being a usable, secure Linux desktop. === Features === Secureblue ships with many tools and features to allow users to achieve a secure Linux desktop. These features include: * [[Trivalent]] browser shipped by default * Global [[hardened_malloc]], including for [[Flatpak]] * Kernel hardening via [[sysctl]] and kernel arguments * Automatic blacklisting of numerous unused kernel modules, reducing attack surface * ujust tooling being shipped by default, allowing for easy hardening * And many, many more. When putting all this, along with other features, together, you end up with an incredibly secure Linux distribution, suitable for both desktop and server use. 463f39b98d7c451f90ef73d445d00d20524d180c 0 198 5843 5652 2026-07-13T17:34:29Z Ow0cast 249 closed wikitable wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Secureblue]] |A security focused desktop and server Linux distribution built on [[Fedora Atomic]]. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[https://www.calculate-linux.org/ Calculate] |A user friendly Gentoo based distribution focused on ease of use and backwards compatibility with Gentoo. |- |[[openFyde]] |A fully open-source fork of FydeOS. It strips out proprietary drivers and commercial patches to provide a completely open-source, decoupled ChromiumOS experience. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[Dérive Linux]] |Dérive is a simple and independent Linux distribution based on the Musl libc and Busybox. |- |[[GKISS Linux]] |A fork of the original KISS Linux that uses the GNU libc rather than the Musl libc to add extra compatability. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[KISS Linux]] |A Linux distribution focused on simplicity and transparency. Maintained by the KISS community rather than the original creator. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- ||[[Oasis Linux]] |Oasis is a small, fully statically linked BSD like Linux distribution. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == 2cced74b1baa34e75dbe910944e4bdf09ac690eb 0 1381 5844 2026-07-15T08:49:35Z Imnotgoodatnames 121 Page created; MS-DOS, PC DOS, FreeDOS parts wikitext text/x-wiki '''DOS''' is a family of MS-DOS compatible disk operating systems for the IBM PC and compatibles. The most popular operating systems in the category are Microsoft's '''IBM PC DOS''' and '''MS-DOS'''. All other DOS-es were designed to be compatible with MS-DOS but usually introduced new features as well. =PC DOS= {{SoftwareInfobox | title = '''IBM PC DOS''' | image = [[File:IBM_PC_DOS_7.0_logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | caption = IBM PC DOS logo | releasestatus = Discontinued | lastrelease = PC DOS 2000 | languages = [[x86 Assembly]], [[C]] | developers = Microsoft, IBM | license = Proprietary | website = [https://web.archive.org/web/19990508201612/www.software.ibm.com/os/dos/dos2000/oem.html PC DOS 2000 for OEMs (archived 1999)] }} '''IBM PC DOS''' is the original DOS developed in 1981 by Microsoft for the IBM Personal Computer alongside Microsoft's MS-DOS, which was sold to the open market. It shared development with MS-DOS and the two systems were nearly identical until 1993, when Microsoft stopped developing it and IBM started introducing new features. =MS-DOS= {{SoftwareInfobox | title = '''MS-DOS''' | image = [[File:Msdos-icon.svg|frameless|upright=0.8]] | caption = MS-DOS icon in [[Windows]] | releasestatus = Discontinued | lastrelease = 6.22; 8.0 (As part of [[Windows]] ME) | languages = [[x86 Assembly]], [[C]] | developers = Microsoft | license = Proprietary; 1.25, 2.11, 4.00: [[MIT_License|MIT]] | website = [https://web.archive.org/web/19990508201612/www.software.ibm.com/os/dos/dos2000/oem.html PC DOS 2000 for OEMs (archived 1999)] }} '''MS-DOS''' (Microsoft DOS) is the version of Microsoft's DOS sold to OEMs other than IBM. It quickly became the most popular DOS system due to its use by most IBM compatible personal computers. From 1994 it ceased development as an independent operating system and from 1995 to 2000 was instead developed as the core part of the [[Windows]] 9x series. =FreeDOS= {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG | defaultdesktops = [[CLI|Command line interface]] | usagetype = Desktop | architectures = IA-16, i386 | website = [http://freedos.org freedos.org] }} FreeDOS is a [[FOSS|free]] DOS operating system developed since 1994, when Microsoft announced Windows would replace MS-DOS. It includes various advantages over MS-DOS such as kernel-level FAT-32 support, a network package manager and a CD release. d48078085c3fae3141fdec8f7e98549099039d3c 5845 5844 2026-07-15T08:55:41Z Imnotgoodatnames 121 oops wikitext text/x-wiki '''DOS''' is a family of MS-DOS compatible disk operating systems for the IBM PC and compatibles. The most popular operating systems in the category are Microsoft's '''IBM PC DOS''' and '''MS-DOS'''. All other DOS-es were designed to be compatible with MS-DOS but usually introduced new features as well. =PC DOS= {{SoftwareInfobox | title = '''IBM PC DOS''' | image = [[File:IBM_PC_DOS_7.0_logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | caption = IBM PC DOS logo | releasestatus = Discontinued | lastrelease = PC DOS 2000 | languages = [[x86 Assembly]], [[C]] | developers = Microsoft, IBM | license = Proprietary | website = [https://web.archive.org/web/19990508201612/www.software.ibm.com/os/dos/dos2000/oem.html PC DOS 2000 for OEMs (archived 1999)] }} '''IBM PC DOS''' is the original DOS developed in 1981 by Microsoft for the IBM Personal Computer alongside Microsoft's MS-DOS, which was sold to the open market. It shared development with MS-DOS and the two systems were nearly identical until 1993, when Microsoft stopped developing it and IBM started introducing new features. =MS-DOS= {{SoftwareInfobox | title = '''MS-DOS''' | image = [[File:Msdos-icon.svg|frameless|upright=0.8]] | caption = MS-DOS icon in [[Windows]] | releasestatus = Discontinued | lastrelease = 6.22; 8.0 (As part of [[Windows]] ME) | languages = [[x86 Assembly]], [[C]] | developers = Microsoft | license = Proprietary; 1.25, 2.11, 4.00: [[MIT_License|MIT]] | website = [https://web.archive.org/web/20170709153940/https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/windows_dos_overview.mspx MS-DOS overview (archived 2017)] }} '''MS-DOS''' (Microsoft DOS) is the version of Microsoft's DOS sold to OEMs other than IBM. It quickly became the most popular DOS system due to its use by most IBM compatible personal computers. From 1994 it ceased development as an independent operating system and from 1995 to 2000 was instead developed as the core part of the [[Windows]] 9x series. =FreeDOS= {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG | defaultdesktops = [[CLI|Command line interface]] | usagetype = Desktop | architectures = IA-16, i386 | website = [http://freedos.org freedos.org] }} FreeDOS is a [[FOSS|free]] DOS operating system developed since 1994, when Microsoft announced Windows would replace MS-DOS. It includes various advantages over MS-DOS such as kernel-level FAT-32 support, a network package manager and a CD release. 78ef362f8d5f7fbe2581836baf3d99af9b8a93a6 5848 5845 2026-07-15T09:03:33Z Imnotgoodatnames 121 Added screenshot wikitext text/x-wiki [[File:Command_com.png|thumb|MS-DOS command prompt]] '''DOS''' is a family of MS-DOS compatible disk operating systems for the IBM PC and compatibles. The most popular operating systems in the category are Microsoft's '''IBM PC DOS''' and '''MS-DOS'''. All other DOS-es were designed to be compatible with MS-DOS but usually introduced new features as well. =PC DOS= {{SoftwareInfobox | title = '''IBM PC DOS''' | image = [[File:IBM_PC_DOS_7.0_logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | caption = IBM PC DOS logo | releasestatus = Discontinued | lastrelease = PC DOS 2000 | languages = [[x86 Assembly]], [[C]] | developers = Microsoft, IBM | license = Proprietary | website = [https://web.archive.org/web/19990508201612/www.software.ibm.com/os/dos/dos2000/oem.html PC DOS 2000 for OEMs (archived 1999)] }} '''IBM PC DOS''' is the original DOS developed in 1981 by Microsoft for the IBM Personal Computer alongside Microsoft's MS-DOS, which was sold to the open market. It shared development with MS-DOS and the two systems were nearly identical until 1993, when Microsoft stopped developing it and IBM started introducing new features. =MS-DOS= {{SoftwareInfobox | title = '''MS-DOS''' | image = [[File:Msdos-icon.svg|frameless|upright=0.8]] | caption = MS-DOS icon in [[Windows]] | releasestatus = Discontinued | lastrelease = 6.22; 8.0 (As part of [[Windows]] ME) | languages = [[x86 Assembly]], [[C]] | developers = Microsoft | license = Proprietary; 1.25, 2.11, 4.00: [[MIT_License|MIT]] | website = [https://web.archive.org/web/20170709153940/https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/windows_dos_overview.mspx MS-DOS overview (archived 2017)] }} '''MS-DOS''' (Microsoft DOS) is the version of Microsoft's DOS sold to OEMs other than IBM. It quickly became the most popular DOS system due to its use by most IBM compatible personal computers. From 1994 it ceased development as an independent operating system and from 1995 to 2000 was instead developed as the core part of the [[Windows]] 9x series. =FreeDOS= {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG | defaultdesktops = [[CLI|Command line interface]] | usagetype = Desktop | architectures = IA-16, i386 | website = [http://freedos.org freedos.org] }} FreeDOS is a [[FOSS|free]] DOS operating system developed since 1994, when Microsoft announced Windows would replace MS-DOS. It includes various advantages over MS-DOS such as kernel-level FAT-32 support, a network package manager and a CD release. 73709e62e9429bf905a71153e0abcb89d8587046 0 1382 5846 2026-07-15T08:58:24Z Imnotgoodatnames 121 Created link wikitext text/x-wiki #REDIRECT [[DOS_(x86_operating_system)#FreeDOS]] 57044aae0c3d5ad76b5f2669d2e3325cf0c22c12 0 1383 5847 2026-07-15T08:59:24Z Imnotgoodatnames 121 Created link wikitext text/x-wiki #REDIRECT [[DOS_(x86_operating_system)#MS-DOS]] bc3f9a337e50a30e5e21fad7aa9aa40400781080 3000 1384 5849 2026-07-16T00:58:03Z Hyperreal 388 Add Blocking AI bots and webcrawlers with Fail2Ban wikitext text/x-wiki {{GuideWarning}} == Requirements == * A configured public-facing webserver, such as Caddy, Apache, or Nginx. This guide will cover those three. * A firewall solution, such as firewalld, UFW, nftables, PF, or iptables. * The webserver is hosted on a Linux distribution or *BSD. * fail2ban from the host distribution's package repositories. == Configuring Fail2Ban == Ensure the above requirements are met. In this guide, we'll assume the fail2ban configuration files are located under <code>/etc/fail2ban</code>. We'll be creating three files: * <code>/etc/fail2ban/filter.d/badbots.conf</code> * <code>/etc/fail2ban/filter.d/suspaths.conf</code> * <code>/etc/fail2ban/jail.local</code> === AI bots === The AI bot names are taken from the ai-robots-txt GitHub repository<ref>[https://raw.githubusercontent.com/ai-robots-txt/ai.robots.txt/refs/heads/main/robots.json robots.json], GitHub, accessed 2026-07-15</ref>. We can add or remove whichever ones we like. The names will be filtered by matching regex for the User-Agent from our webserver access logs. The regex used will depend on the logging format of our webserver. First, we'll create the file <code>/etc/fail2ban/filter.d/badbots.conf</code>. Add the following contents. <syntaxhighlight lang="bash"> [Definition] badbots = AddSearchBot|AgentTimes|AI2Bot|AI2Bot-DeepResearchEval|Ai2Bot-Dolma|aiHitBot|AIWebIndex|amazon-kendra|amazon-QBusiness|Amazonbot|AmazonBuyForMe|Amzn-SearchBot|Amzn-User|Andibot|Anomura|anthropic-ai|ApifyBot|ApifyWebsiteContentCrawler|Applebot|Applebot-Extended|Aranet-SearchBot|atlassian-bot|Awario|AzureAI-SearchBot|bedrockbot|bigsur\.ai|Bravebot|Brightbot|Brightbot 1\.0|BuddyBot|Bytespider|CCBot|Channel3Bot|ChatGLM-Spider|ChatGPT Agent|ChatGPT-User|Claude-Code|Claude-SearchBot|Claude-User|Claude-Web|ClaudeBot|Cloudflare-AutoRAG|CloudVertexBot|Code|cohere-ai|cohere-training-data-crawler|Cotoyogi|CragCrawler|Crawl4AI|Crawlspace|Cursor|Datenbank Crawler|DeepSeekBot|Devin|Diffbot|DuckAssistBot|Echobot Bot|EchoboxBot|ExaBot|FacebookBot|facebookexternalhit|Factset_spyderbot|FirecrawlAgent|FriendlyCrawler|GeistHaus-PageFetcher|Gemini-Deep-Research|Google-Agent|Google-CloudVertexBot|Google-Extended|Google-Firebase|Google-Gemini-CLI|Google-NotebookLM|GoogleAgent-Mariner|GoogleAgent-URLContext|GoogleOther|GoogleOther-Image|GoogleOther-Video|GPTBot|HenkBot|iAskBot|iaskspider|iaskspider/2\.0|IbouBot|ICC-Crawler|ImagesiftBot|imageSpider|img2dataset|ISSCyberRiskCrawler|kagi-fetcher|Kangaroo Bot|Kimi-User|KlaviyoAIBot|KunatoCrawler|laion-huggingface-processor|LAIONDownloader|LCC|LinerBot|Linguee Bot|LinkupBot|Manus-User|meta-externalagent|Meta-ExternalAgent|meta-externalfetcher|Meta-ExternalFetcher|meta-webindexer|MistralAI-User|MistralAI-User/1\.0|Mozilla-Tabstack|MyCentralAIScraperBot|NagetBot|netEstate Imprint Crawler|newsai|NotebookLM|NovaAct|OAI-SearchBot|omgili|omgilibot|OpenAI|opencode|operator|PanguBot|Panscient|panscient\.com|Perplexity-User|PerplexityBot|PetalBot|PhindBot|Poggio-Citations|Poseidon Research Crawler|QualifiedBot|Querit-SearchBot|QueritBot|QuillBot|quillbot\.com|SBIntuitionsBot|Scrapy|SemrushBot-OCOB|SemrushBot-SWA|Shap-User|ShapBot|Sidetrade indexer bot|Spider|TavilyBot|Terra Cotta|TerraCotta|Thinkbot|TikTokSpider|Timpibot|TongyiBot|Trae|TwinAgent|UseAI|VelenPublicWebCrawler|WARDBot|Webzio-Extended|webzio-extended|wpbot|WRTNBot|YaK|YandexAdditional|YandexAdditionalBot|YiyanBot|YouBot|ZanistaBot|Tuwunel|Synapse </syntaxhighlight> The <code>badbots</code> variable contains a string that is meant to be substituted into regex. The <code>BotName|OtherBotName</code> is a regular expression syntax that matches any of the listed bot names. The <code>|</code> is like a [https://en.wikipedia.org/wiki/Logical_disjunction logical OR operator]. In the <code>badbots</code> variable above, any one of the listed bots will be matched by our regex filter. The next step is to add a <code>failregex</code> variable to <code>/etc/fail2ban/filter.d/badbots.conf</code>. Refer to the webserver subsections below for which regex to use. Each filter must have the <code>ignoreregex =</code> variable declared in the file, even if the value is empty. We won't need it for our use-case. ==== Caddy ==== In <code>/etc/fail2ban/filter.d/badbots.conf</code>, add the following <code>failregex</code> variable. This is compatible with Caddy's JSON Structured log format. <syntaxhighlight lang="bash"> failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*".*(?:%(badbots)s).*".* ignoreregex = </syntaxhighlight> The <code>failregex</code> variable is used by fail2ban to filter our webserver access logs by matching the regex string. The <code>%(badbots)s</code> part is used to substitute the contents of the <code>badbots</code> variable we declared earlier. ==== Apache ==== In <code>/etc/fail2ban/filter.d/badbots.conf</code>, add the following <code>failregex</code> variable, which is compatible with the Apache webserver's log file format. <syntaxhighlight lang="bash"> failregex = ^<HOST> -.*"(GET|POST|HEAD).*HTTP.*"(?:%(badbots)s)"$ ignoreregex = </syntaxhighlight> ==== Nginx ==== In <code>/etc/fail2ban/filter.d/badbots.conf</code>, add the folllowing <code>failregex</code> variable to match the User-Agents in Nginx access logs. <syntaxhighlight lang="bash"> failregex = ^<HOST> \- \S+.*\"(GET|POST|HEAD).*\S+\".*(?:%(badbots)s).*"$ ignoreregex = </syntaxhighlight> === Web crawlers === We need to create the file <code>/etc/fail2ban/filter.d/suspaths.conf</code>. Our regex filter will match filesystem paths that are deemed suspicious in our webserver access logs. ==== Caddy ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*"uri":(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*"status":4\d{2}.* ignoreregex = </syntaxhighlight> ==== Apache ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*" ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*\"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).* ignoreregex = </syntaxhighlight> === jail.local === First copy the jail configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Now edit <code>/etc/fail2ban/jail.local</code>. Add the following contents under HTTP servers in the JAILS section. Uncomment one of the lines for the <code>action</code> variable, depending our firewall software. <syntaxhighlight lang="bash"> # # JAILS # # # HTTP servers # [badbots] enabled = true filter = badbots #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto [suspaths] enabled = true filter = suspaths #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto </syntaxhighlight> The variables above can be tweaked to user preference. For more information on fail2ban configuration, consult <code>man fail2ban</code><ref>[https://manpages.debian.org/testing/fail2ban/jail.conf.5.en.html fail2ban(8)], Debian man pages, accessed 2026-07-15</ref> and <code>man jail.conf</code><ref>[https://manpages.debian.org/trixie/fail2ban/jail.conf.5.en.html jail.conf(5)], Debian man pages, accessed 2026-07-15</ref>. == Starting the services == Now that we have our configuration files in place, it's time to enable and start the fail2ban service. <syntaxhighlight lang="bash"> # systemd sudo systemctl enable --now fail2ban.service # SysV init, OpenRC, BSD init sudo service fail2ban start </syntaxhighlight> We can check information on our fail2ban jails with the following commands. <syntaxhighlight lang="bash"> # Check the status of our jails sudo fail2ban-client status # See which hosts have been banned by fail2ban sudo fail2ban-client banned # Check stats of our jails sudo fail2ban-client stats </syntaxhighlight> == References == <references /> 835bd8e6701782e81f45ebf22b987411d56eee45 5850 5849 2026-07-16T04:47:13Z Hyperreal 388 /* AI bots */ wikitext text/x-wiki {{GuideWarning}} == Requirements == * A configured public-facing webserver, such as Caddy, Apache, or Nginx. This guide will cover those three. * A firewall solution, such as firewalld, UFW, nftables, PF, or iptables. * The webserver is hosted on a Linux distribution or *BSD. * fail2ban from the host distribution's package repositories. == Configuring Fail2Ban == Ensure the above requirements are met. In this guide, we'll assume the fail2ban configuration files are located under <code>/etc/fail2ban</code>. We'll be creating three files: * <code>/etc/fail2ban/filter.d/badbots.conf</code> * <code>/etc/fail2ban/filter.d/suspaths.conf</code> * <code>/etc/fail2ban/jail.local</code> === AI bots === The AI bot names are taken from the ai-robots-txt GitHub repository<ref>[https://raw.githubusercontent.com/ai-robots-txt/ai.robots.txt/refs/heads/main/robots.json robots.json], GitHub, accessed 2026-07-15</ref>. We can add or remove whichever ones we like. The names will be filtered by matching regex for the User-Agent from our webserver access logs. The regex used will depend on the logging format of our webserver. First, we'll create the file <code>/etc/fail2ban/filter.d/badbots.conf</code>. We should add the following contents. <syntaxhighlight lang="bash"> [Definition] badbots = AddSearchBot|AgentTimes|AI2Bot|AI2Bot-DeepResearchEval|Ai2Bot-Dolma|aiHitBot|AIWebIndex|amazon-kendra|amazon-QBusiness|Amazonbot|AmazonBuyForMe|Amzn-SearchBot|Amzn-User|Andibot|Anomura|anthropic-ai|ApifyBot|ApifyWebsiteContentCrawler|Applebot|Applebot-Extended|Aranet-SearchBot|atlassian-bot|Awario|AzureAI-SearchBot|bedrockbot|bigsur\.ai|Bravebot|Brightbot|Brightbot 1\.0|BuddyBot|Bytespider|CCBot|Channel3Bot|ChatGLM-Spider|ChatGPT Agent|ChatGPT-User|Claude-Code|Claude-SearchBot|Claude-User|Claude-Web|ClaudeBot|Cloudflare-AutoRAG|CloudVertexBot|Code|cohere-ai|cohere-training-data-crawler|Cotoyogi|CragCrawler|Crawl4AI|Crawlspace|Cursor|Datenbank Crawler|DeepSeekBot|Devin|Diffbot|DuckAssistBot|Echobot Bot|EchoboxBot|ExaBot|FacebookBot|facebookexternalhit|Factset_spyderbot|FirecrawlAgent|FriendlyCrawler|GeistHaus-PageFetcher|Gemini-Deep-Research|Google-Agent|Google-CloudVertexBot|Google-Extended|Google-Firebase|Google-Gemini-CLI|Google-NotebookLM|GoogleAgent-Mariner|GoogleAgent-URLContext|GoogleOther|GoogleOther-Image|GoogleOther-Video|GPTBot|HenkBot|iAskBot|iaskspider|iaskspider/2\.0|IbouBot|ICC-Crawler|ImagesiftBot|imageSpider|img2dataset|ISSCyberRiskCrawler|kagi-fetcher|Kangaroo Bot|Kimi-User|KlaviyoAIBot|KunatoCrawler|laion-huggingface-processor|LAIONDownloader|LCC|LinerBot|Linguee Bot|LinkupBot|Manus-User|meta-externalagent|Meta-ExternalAgent|meta-externalfetcher|Meta-ExternalFetcher|meta-webindexer|MistralAI-User|MistralAI-User/1\.0|Mozilla-Tabstack|MyCentralAIScraperBot|NagetBot|netEstate Imprint Crawler|newsai|NotebookLM|NovaAct|OAI-SearchBot|omgili|omgilibot|OpenAI|opencode|operator|PanguBot|Panscient|panscient\.com|Perplexity-User|PerplexityBot|PetalBot|PhindBot|Poggio-Citations|Poseidon Research Crawler|QualifiedBot|Querit-SearchBot|QueritBot|QuillBot|quillbot\.com|SBIntuitionsBot|Scrapy|SemrushBot-OCOB|SemrushBot-SWA|Shap-User|ShapBot|Sidetrade indexer bot|Spider|TavilyBot|Terra Cotta|TerraCotta|Thinkbot|TikTokSpider|Timpibot|TongyiBot|Trae|TwinAgent|UseAI|VelenPublicWebCrawler|WARDBot|Webzio-Extended|webzio-extended|wpbot|WRTNBot|YaK|YandexAdditional|YandexAdditionalBot|YiyanBot|YouBot|ZanistaBot|Tuwunel|Synapse </syntaxhighlight> The <code>badbots</code> variable contains a string that is meant to be substituted into a regex filter. The <code>BotName|OtherBotName</code> is regular expression syntax that matches any of the listed bot names. The <code>|</code> is like a [https://en.wikipedia.org/wiki/Logical_disjunction logical OR operator]. In the <code>badbots</code> variable above, any one of the listed bots will be matched by our regex filter. If any of the bots are present in the User-Agent field of our webserver logs, fail2ban will take the IP associated with that request and add it to the jail, thereby blocking any future requests from that IP for certain amount of time that we define later. The next step is to add a <code>failregex</code> variable to <code>/etc/fail2ban/filter.d/badbots.conf</code>. We can refer to the webserver subsections below for which regex to use. Each filter must have the <code>ignoreregex =</code> variable declared in the file, even if the value is empty. We won't need to define it for our use-case, but it still needs to be in the file. In the following sections, the <code>failregex</code> variable is different for each webserver that uses a different log format. Caddy uses a JSON structured format, while Apache and Nginx use the [https://en.wikipedia.org/wiki/Common_Log_Format Common Log Format]. ==== Caddy ==== <syntaxhighlight lang="bash"> failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*".*(?:%(badbots)s).*".* ignoreregex = </syntaxhighlight> The <code>failregex</code> variable is used by fail2ban to filter our webserver access logs by matching the regex string. The <code>%(badbots)s</code> part is used to substitute the contents of the <code>badbots</code> variable we declared earlier. ==== Apache ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> -.*"(GET|POST|HEAD).*HTTP.*"(?:%(badbots)s)"$ ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> \- \S+.*\"(GET|POST|HEAD).*\S+\".*(?:%(badbots)s).*"$ ignoreregex = </syntaxhighlight> === Web crawlers === We need to create the file <code>/etc/fail2ban/filter.d/suspaths.conf</code>. Our regex filter will match filesystem paths that are deemed suspicious in our webserver access logs. ==== Caddy ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*"uri":(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*"status":4\d{2}.* ignoreregex = </syntaxhighlight> ==== Apache ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*" ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*\"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).* ignoreregex = </syntaxhighlight> === jail.local === First copy the jail configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Now edit <code>/etc/fail2ban/jail.local</code>. Add the following contents under HTTP servers in the JAILS section. Uncomment one of the lines for the <code>action</code> variable, depending our firewall software. <syntaxhighlight lang="bash"> # # JAILS # # # HTTP servers # [badbots] enabled = true filter = badbots #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto [suspaths] enabled = true filter = suspaths #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto </syntaxhighlight> The variables above can be tweaked to user preference. For more information on fail2ban configuration, consult <code>man fail2ban</code><ref>[https://manpages.debian.org/testing/fail2ban/jail.conf.5.en.html fail2ban(8)], Debian man pages, accessed 2026-07-15</ref> and <code>man jail.conf</code><ref>[https://manpages.debian.org/trixie/fail2ban/jail.conf.5.en.html jail.conf(5)], Debian man pages, accessed 2026-07-15</ref>. == Starting the services == Now that we have our configuration files in place, it's time to enable and start the fail2ban service. <syntaxhighlight lang="bash"> # systemd sudo systemctl enable --now fail2ban.service # SysV init, OpenRC, BSD init sudo service fail2ban start </syntaxhighlight> We can check information on our fail2ban jails with the following commands. <syntaxhighlight lang="bash"> # Check the status of our jails sudo fail2ban-client status # See which hosts have been banned by fail2ban sudo fail2ban-client banned # Check stats of our jails sudo fail2ban-client stats </syntaxhighlight> == References == <references /> 4f705d4cdbdae9323ba46d9cb71177b2a4a9df8d 5851 5850 2026-07-16T04:48:12Z Hyperreal 388 /* AI bots */ wikitext text/x-wiki {{GuideWarning}} == Requirements == * A configured public-facing webserver, such as Caddy, Apache, or Nginx. This guide will cover those three. * A firewall solution, such as firewalld, UFW, nftables, PF, or iptables. * The webserver is hosted on a Linux distribution or *BSD. * fail2ban from the host distribution's package repositories. == Configuring Fail2Ban == Ensure the above requirements are met. In this guide, we'll assume the fail2ban configuration files are located under <code>/etc/fail2ban</code>. We'll be creating three files: * <code>/etc/fail2ban/filter.d/badbots.conf</code> * <code>/etc/fail2ban/filter.d/suspaths.conf</code> * <code>/etc/fail2ban/jail.local</code> === AI bots === The AI bot names are taken from the ai-robots-txt GitHub repository<ref>[https://raw.githubusercontent.com/ai-robots-txt/ai.robots.txt/refs/heads/main/robots.json robots.json], GitHub, accessed 2026-07-15</ref>. We can add or remove whichever ones we like. The names will be filtered by matching regex for the User-Agent from our webserver access logs. The regex used will depend on the logging format of our webserver. First, we'll create the file <code>/etc/fail2ban/filter.d/badbots.conf</code>. We should add the following contents. <syntaxhighlight lang="bash"> [Definition] badbots = AddSearchBot|AgentTimes|AI2Bot|AI2Bot-DeepResearchEval|Ai2Bot-Dolma|aiHitBot|AIWebIndex|amazon-kendra|amazon-QBusiness|Amazonbot|AmazonBuyForMe|Amzn-SearchBot|Amzn-User|Andibot|Anomura|anthropic-ai|ApifyBot|ApifyWebsiteContentCrawler|Applebot|Applebot-Extended|Aranet-SearchBot|atlassian-bot|Awario|AzureAI-SearchBot|bedrockbot|bigsur\.ai|Bravebot|Brightbot|Brightbot 1\.0|BuddyBot|Bytespider|CCBot|Channel3Bot|ChatGLM-Spider|ChatGPT Agent|ChatGPT-User|Claude-Code|Claude-SearchBot|Claude-User|Claude-Web|ClaudeBot|Cloudflare-AutoRAG|CloudVertexBot|Code|cohere-ai|cohere-training-data-crawler|Cotoyogi|CragCrawler|Crawl4AI|Crawlspace|Cursor|Datenbank Crawler|DeepSeekBot|Devin|Diffbot|DuckAssistBot|Echobot Bot|EchoboxBot|ExaBot|FacebookBot|facebookexternalhit|Factset_spyderbot|FirecrawlAgent|FriendlyCrawler|GeistHaus-PageFetcher|Gemini-Deep-Research|Google-Agent|Google-CloudVertexBot|Google-Extended|Google-Firebase|Google-Gemini-CLI|Google-NotebookLM|GoogleAgent-Mariner|GoogleAgent-URLContext|GoogleOther|GoogleOther-Image|GoogleOther-Video|GPTBot|HenkBot|iAskBot|iaskspider|iaskspider/2\.0|IbouBot|ICC-Crawler|ImagesiftBot|imageSpider|img2dataset|ISSCyberRiskCrawler|kagi-fetcher|Kangaroo Bot|Kimi-User|KlaviyoAIBot|KunatoCrawler|laion-huggingface-processor|LAIONDownloader|LCC|LinerBot|Linguee Bot|LinkupBot|Manus-User|meta-externalagent|Meta-ExternalAgent|meta-externalfetcher|Meta-ExternalFetcher|meta-webindexer|MistralAI-User|MistralAI-User/1\.0|Mozilla-Tabstack|MyCentralAIScraperBot|NagetBot|netEstate Imprint Crawler|newsai|NotebookLM|NovaAct|OAI-SearchBot|omgili|omgilibot|OpenAI|opencode|operator|PanguBot|Panscient|panscient\.com|Perplexity-User|PerplexityBot|PetalBot|PhindBot|Poggio-Citations|Poseidon Research Crawler|QualifiedBot|Querit-SearchBot|QueritBot|QuillBot|quillbot\.com|SBIntuitionsBot|Scrapy|SemrushBot-OCOB|SemrushBot-SWA|Shap-User|ShapBot|Sidetrade indexer bot|Spider|TavilyBot|Terra Cotta|TerraCotta|Thinkbot|TikTokSpider|Timpibot|TongyiBot|Trae|TwinAgent|UseAI|VelenPublicWebCrawler|WARDBot|Webzio-Extended|webzio-extended|wpbot|WRTNBot|YaK|YandexAdditional|YandexAdditionalBot|YiyanBot|YouBot|ZanistaBot|Tuwunel|Synapse </syntaxhighlight> The <code>badbots</code> variable contains a string that is meant to be substituted into a regex filter. The <code>BotName|OtherBotName</code> is regular expression syntax that matches any of the listed bot names. The <code>|</code> is like a [https://en.wikipedia.org/wiki/Logical_disjunction logical OR operator]. In the <code>badbots</code> variable above, any one of the listed bots will be matched by our regex filter. If any of the bots are present in the User-Agent field of our webserver logs, fail2ban will take the IP associated with that request and add it to the jail, thereby blocking any future requests from that IP for a certain amount of time that we define later. The next step is to add a <code>failregex</code> variable to <code>/etc/fail2ban/filter.d/badbots.conf</code>. We can refer to the webserver subsections below for which regex to use. Each filter must have the <code>ignoreregex =</code> variable declared in the file, even if the value is empty. We won't need to define it for our use-case, but it still needs to be in the file. In the following sections, the <code>failregex</code> variable is different for each webserver that uses a different log format. Caddy uses a JSON structured format, while Apache and Nginx use the [https://en.wikipedia.org/wiki/Common_Log_Format Common Log Format]. ==== Caddy ==== <syntaxhighlight lang="bash"> failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*".*(?:%(badbots)s).*".* ignoreregex = </syntaxhighlight> The <code>failregex</code> variable is used by fail2ban to filter our webserver access logs by matching the regex string. The <code>%(badbots)s</code> part is used to substitute the contents of the <code>badbots</code> variable we declared earlier. ==== Apache ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> -.*"(GET|POST|HEAD).*HTTP.*"(?:%(badbots)s)"$ ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> \- \S+.*\"(GET|POST|HEAD).*\S+\".*(?:%(badbots)s).*"$ ignoreregex = </syntaxhighlight> === Web crawlers === We need to create the file <code>/etc/fail2ban/filter.d/suspaths.conf</code>. Our regex filter will match filesystem paths that are deemed suspicious in our webserver access logs. ==== Caddy ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*"uri":(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*"status":4\d{2}.* ignoreregex = </syntaxhighlight> ==== Apache ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*" ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*\"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).* ignoreregex = </syntaxhighlight> === jail.local === First copy the jail configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Now edit <code>/etc/fail2ban/jail.local</code>. Add the following contents under HTTP servers in the JAILS section. Uncomment one of the lines for the <code>action</code> variable, depending our firewall software. <syntaxhighlight lang="bash"> # # JAILS # # # HTTP servers # [badbots] enabled = true filter = badbots #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto [suspaths] enabled = true filter = suspaths #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto </syntaxhighlight> The variables above can be tweaked to user preference. For more information on fail2ban configuration, consult <code>man fail2ban</code><ref>[https://manpages.debian.org/testing/fail2ban/jail.conf.5.en.html fail2ban(8)], Debian man pages, accessed 2026-07-15</ref> and <code>man jail.conf</code><ref>[https://manpages.debian.org/trixie/fail2ban/jail.conf.5.en.html jail.conf(5)], Debian man pages, accessed 2026-07-15</ref>. == Starting the services == Now that we have our configuration files in place, it's time to enable and start the fail2ban service. <syntaxhighlight lang="bash"> # systemd sudo systemctl enable --now fail2ban.service # SysV init, OpenRC, BSD init sudo service fail2ban start </syntaxhighlight> We can check information on our fail2ban jails with the following commands. <syntaxhighlight lang="bash"> # Check the status of our jails sudo fail2ban-client status # See which hosts have been banned by fail2ban sudo fail2ban-client banned # Check stats of our jails sudo fail2ban-client stats </syntaxhighlight> == References == <references /> 01b1f6e6300aaf0c3e37fb13c7372d8392e91274 5852 5851 2026-07-16T04:50:13Z Hyperreal 388 /* Caddy */ wikitext text/x-wiki {{GuideWarning}} == Requirements == * A configured public-facing webserver, such as Caddy, Apache, or Nginx. This guide will cover those three. * A firewall solution, such as firewalld, UFW, nftables, PF, or iptables. * The webserver is hosted on a Linux distribution or *BSD. * fail2ban from the host distribution's package repositories. == Configuring Fail2Ban == Ensure the above requirements are met. In this guide, we'll assume the fail2ban configuration files are located under <code>/etc/fail2ban</code>. We'll be creating three files: * <code>/etc/fail2ban/filter.d/badbots.conf</code> * <code>/etc/fail2ban/filter.d/suspaths.conf</code> * <code>/etc/fail2ban/jail.local</code> === AI bots === The AI bot names are taken from the ai-robots-txt GitHub repository<ref>[https://raw.githubusercontent.com/ai-robots-txt/ai.robots.txt/refs/heads/main/robots.json robots.json], GitHub, accessed 2026-07-15</ref>. We can add or remove whichever ones we like. The names will be filtered by matching regex for the User-Agent from our webserver access logs. The regex used will depend on the logging format of our webserver. First, we'll create the file <code>/etc/fail2ban/filter.d/badbots.conf</code>. We should add the following contents. <syntaxhighlight lang="bash"> [Definition] badbots = AddSearchBot|AgentTimes|AI2Bot|AI2Bot-DeepResearchEval|Ai2Bot-Dolma|aiHitBot|AIWebIndex|amazon-kendra|amazon-QBusiness|Amazonbot|AmazonBuyForMe|Amzn-SearchBot|Amzn-User|Andibot|Anomura|anthropic-ai|ApifyBot|ApifyWebsiteContentCrawler|Applebot|Applebot-Extended|Aranet-SearchBot|atlassian-bot|Awario|AzureAI-SearchBot|bedrockbot|bigsur\.ai|Bravebot|Brightbot|Brightbot 1\.0|BuddyBot|Bytespider|CCBot|Channel3Bot|ChatGLM-Spider|ChatGPT Agent|ChatGPT-User|Claude-Code|Claude-SearchBot|Claude-User|Claude-Web|ClaudeBot|Cloudflare-AutoRAG|CloudVertexBot|Code|cohere-ai|cohere-training-data-crawler|Cotoyogi|CragCrawler|Crawl4AI|Crawlspace|Cursor|Datenbank Crawler|DeepSeekBot|Devin|Diffbot|DuckAssistBot|Echobot Bot|EchoboxBot|ExaBot|FacebookBot|facebookexternalhit|Factset_spyderbot|FirecrawlAgent|FriendlyCrawler|GeistHaus-PageFetcher|Gemini-Deep-Research|Google-Agent|Google-CloudVertexBot|Google-Extended|Google-Firebase|Google-Gemini-CLI|Google-NotebookLM|GoogleAgent-Mariner|GoogleAgent-URLContext|GoogleOther|GoogleOther-Image|GoogleOther-Video|GPTBot|HenkBot|iAskBot|iaskspider|iaskspider/2\.0|IbouBot|ICC-Crawler|ImagesiftBot|imageSpider|img2dataset|ISSCyberRiskCrawler|kagi-fetcher|Kangaroo Bot|Kimi-User|KlaviyoAIBot|KunatoCrawler|laion-huggingface-processor|LAIONDownloader|LCC|LinerBot|Linguee Bot|LinkupBot|Manus-User|meta-externalagent|Meta-ExternalAgent|meta-externalfetcher|Meta-ExternalFetcher|meta-webindexer|MistralAI-User|MistralAI-User/1\.0|Mozilla-Tabstack|MyCentralAIScraperBot|NagetBot|netEstate Imprint Crawler|newsai|NotebookLM|NovaAct|OAI-SearchBot|omgili|omgilibot|OpenAI|opencode|operator|PanguBot|Panscient|panscient\.com|Perplexity-User|PerplexityBot|PetalBot|PhindBot|Poggio-Citations|Poseidon Research Crawler|QualifiedBot|Querit-SearchBot|QueritBot|QuillBot|quillbot\.com|SBIntuitionsBot|Scrapy|SemrushBot-OCOB|SemrushBot-SWA|Shap-User|ShapBot|Sidetrade indexer bot|Spider|TavilyBot|Terra Cotta|TerraCotta|Thinkbot|TikTokSpider|Timpibot|TongyiBot|Trae|TwinAgent|UseAI|VelenPublicWebCrawler|WARDBot|Webzio-Extended|webzio-extended|wpbot|WRTNBot|YaK|YandexAdditional|YandexAdditionalBot|YiyanBot|YouBot|ZanistaBot|Tuwunel|Synapse </syntaxhighlight> The <code>badbots</code> variable contains a string that is meant to be substituted into a regex filter. The <code>BotName|OtherBotName</code> is regular expression syntax that matches any of the listed bot names. The <code>|</code> is like a [https://en.wikipedia.org/wiki/Logical_disjunction logical OR operator]. In the <code>badbots</code> variable above, any one of the listed bots will be matched by our regex filter. If any of the bots are present in the User-Agent field of our webserver logs, fail2ban will take the IP associated with that request and add it to the jail, thereby blocking any future requests from that IP for a certain amount of time that we define later. The next step is to add a <code>failregex</code> variable to <code>/etc/fail2ban/filter.d/badbots.conf</code>. We can refer to the webserver subsections below for which regex to use. Each filter must have the <code>ignoreregex =</code> variable declared in the file, even if the value is empty. We won't need to define it for our use-case, but it still needs to be in the file. In the following sections, the <code>failregex</code> variable is different for each webserver that uses a different log format. Caddy uses a JSON structured format, while Apache and Nginx use the [https://en.wikipedia.org/wiki/Common_Log_Format Common Log Format]. ==== Caddy ==== <syntaxhighlight lang="bash"> failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*".*(?:%(badbots)s).*".* ignoreregex = </syntaxhighlight> * The <code>failregex</code> variable is used by fail2ban to filter our webserver access logs by matching the regex string. * The <code><HOST></code> variable is replaced by the IP address making the request to the webserver. * The <code>%(badbots)s</code> part is used to substitute the contents of the <code>badbots</code> variable we declared earlier. ==== Apache ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> -.*"(GET|POST|HEAD).*HTTP.*"(?:%(badbots)s)"$ ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> \- \S+.*\"(GET|POST|HEAD).*\S+\".*(?:%(badbots)s).*"$ ignoreregex = </syntaxhighlight> === Web crawlers === We need to create the file <code>/etc/fail2ban/filter.d/suspaths.conf</code>. Our regex filter will match filesystem paths that are deemed suspicious in our webserver access logs. ==== Caddy ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*"uri":(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*"status":4\d{2}.* ignoreregex = </syntaxhighlight> ==== Apache ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*" ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*\"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).* ignoreregex = </syntaxhighlight> === jail.local === First copy the jail configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Now edit <code>/etc/fail2ban/jail.local</code>. Add the following contents under HTTP servers in the JAILS section. Uncomment one of the lines for the <code>action</code> variable, depending our firewall software. <syntaxhighlight lang="bash"> # # JAILS # # # HTTP servers # [badbots] enabled = true filter = badbots #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto [suspaths] enabled = true filter = suspaths #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto </syntaxhighlight> The variables above can be tweaked to user preference. For more information on fail2ban configuration, consult <code>man fail2ban</code><ref>[https://manpages.debian.org/testing/fail2ban/jail.conf.5.en.html fail2ban(8)], Debian man pages, accessed 2026-07-15</ref> and <code>man jail.conf</code><ref>[https://manpages.debian.org/trixie/fail2ban/jail.conf.5.en.html jail.conf(5)], Debian man pages, accessed 2026-07-15</ref>. == Starting the services == Now that we have our configuration files in place, it's time to enable and start the fail2ban service. <syntaxhighlight lang="bash"> # systemd sudo systemctl enable --now fail2ban.service # SysV init, OpenRC, BSD init sudo service fail2ban start </syntaxhighlight> We can check information on our fail2ban jails with the following commands. <syntaxhighlight lang="bash"> # Check the status of our jails sudo fail2ban-client status # See which hosts have been banned by fail2ban sudo fail2ban-client banned # Check stats of our jails sudo fail2ban-client stats </syntaxhighlight> == References == <references /> ce4fa0a67a597d481bac1a6532c65c4cef510919 5853 5852 2026-07-16T04:51:37Z Hyperreal 388 /* Starting the services */ wikitext text/x-wiki {{GuideWarning}} == Requirements == * A configured public-facing webserver, such as Caddy, Apache, or Nginx. This guide will cover those three. * A firewall solution, such as firewalld, UFW, nftables, PF, or iptables. * The webserver is hosted on a Linux distribution or *BSD. * fail2ban from the host distribution's package repositories. == Configuring Fail2Ban == Ensure the above requirements are met. In this guide, we'll assume the fail2ban configuration files are located under <code>/etc/fail2ban</code>. We'll be creating three files: * <code>/etc/fail2ban/filter.d/badbots.conf</code> * <code>/etc/fail2ban/filter.d/suspaths.conf</code> * <code>/etc/fail2ban/jail.local</code> === AI bots === The AI bot names are taken from the ai-robots-txt GitHub repository<ref>[https://raw.githubusercontent.com/ai-robots-txt/ai.robots.txt/refs/heads/main/robots.json robots.json], GitHub, accessed 2026-07-15</ref>. We can add or remove whichever ones we like. The names will be filtered by matching regex for the User-Agent from our webserver access logs. The regex used will depend on the logging format of our webserver. First, we'll create the file <code>/etc/fail2ban/filter.d/badbots.conf</code>. We should add the following contents. <syntaxhighlight lang="bash"> [Definition] badbots = AddSearchBot|AgentTimes|AI2Bot|AI2Bot-DeepResearchEval|Ai2Bot-Dolma|aiHitBot|AIWebIndex|amazon-kendra|amazon-QBusiness|Amazonbot|AmazonBuyForMe|Amzn-SearchBot|Amzn-User|Andibot|Anomura|anthropic-ai|ApifyBot|ApifyWebsiteContentCrawler|Applebot|Applebot-Extended|Aranet-SearchBot|atlassian-bot|Awario|AzureAI-SearchBot|bedrockbot|bigsur\.ai|Bravebot|Brightbot|Brightbot 1\.0|BuddyBot|Bytespider|CCBot|Channel3Bot|ChatGLM-Spider|ChatGPT Agent|ChatGPT-User|Claude-Code|Claude-SearchBot|Claude-User|Claude-Web|ClaudeBot|Cloudflare-AutoRAG|CloudVertexBot|Code|cohere-ai|cohere-training-data-crawler|Cotoyogi|CragCrawler|Crawl4AI|Crawlspace|Cursor|Datenbank Crawler|DeepSeekBot|Devin|Diffbot|DuckAssistBot|Echobot Bot|EchoboxBot|ExaBot|FacebookBot|facebookexternalhit|Factset_spyderbot|FirecrawlAgent|FriendlyCrawler|GeistHaus-PageFetcher|Gemini-Deep-Research|Google-Agent|Google-CloudVertexBot|Google-Extended|Google-Firebase|Google-Gemini-CLI|Google-NotebookLM|GoogleAgent-Mariner|GoogleAgent-URLContext|GoogleOther|GoogleOther-Image|GoogleOther-Video|GPTBot|HenkBot|iAskBot|iaskspider|iaskspider/2\.0|IbouBot|ICC-Crawler|ImagesiftBot|imageSpider|img2dataset|ISSCyberRiskCrawler|kagi-fetcher|Kangaroo Bot|Kimi-User|KlaviyoAIBot|KunatoCrawler|laion-huggingface-processor|LAIONDownloader|LCC|LinerBot|Linguee Bot|LinkupBot|Manus-User|meta-externalagent|Meta-ExternalAgent|meta-externalfetcher|Meta-ExternalFetcher|meta-webindexer|MistralAI-User|MistralAI-User/1\.0|Mozilla-Tabstack|MyCentralAIScraperBot|NagetBot|netEstate Imprint Crawler|newsai|NotebookLM|NovaAct|OAI-SearchBot|omgili|omgilibot|OpenAI|opencode|operator|PanguBot|Panscient|panscient\.com|Perplexity-User|PerplexityBot|PetalBot|PhindBot|Poggio-Citations|Poseidon Research Crawler|QualifiedBot|Querit-SearchBot|QueritBot|QuillBot|quillbot\.com|SBIntuitionsBot|Scrapy|SemrushBot-OCOB|SemrushBot-SWA|Shap-User|ShapBot|Sidetrade indexer bot|Spider|TavilyBot|Terra Cotta|TerraCotta|Thinkbot|TikTokSpider|Timpibot|TongyiBot|Trae|TwinAgent|UseAI|VelenPublicWebCrawler|WARDBot|Webzio-Extended|webzio-extended|wpbot|WRTNBot|YaK|YandexAdditional|YandexAdditionalBot|YiyanBot|YouBot|ZanistaBot|Tuwunel|Synapse </syntaxhighlight> The <code>badbots</code> variable contains a string that is meant to be substituted into a regex filter. The <code>BotName|OtherBotName</code> is regular expression syntax that matches any of the listed bot names. The <code>|</code> is like a [https://en.wikipedia.org/wiki/Logical_disjunction logical OR operator]. In the <code>badbots</code> variable above, any one of the listed bots will be matched by our regex filter. If any of the bots are present in the User-Agent field of our webserver logs, fail2ban will take the IP associated with that request and add it to the jail, thereby blocking any future requests from that IP for a certain amount of time that we define later. The next step is to add a <code>failregex</code> variable to <code>/etc/fail2ban/filter.d/badbots.conf</code>. We can refer to the webserver subsections below for which regex to use. Each filter must have the <code>ignoreregex =</code> variable declared in the file, even if the value is empty. We won't need to define it for our use-case, but it still needs to be in the file. In the following sections, the <code>failregex</code> variable is different for each webserver that uses a different log format. Caddy uses a JSON structured format, while Apache and Nginx use the [https://en.wikipedia.org/wiki/Common_Log_Format Common Log Format]. ==== Caddy ==== <syntaxhighlight lang="bash"> failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*".*(?:%(badbots)s).*".* ignoreregex = </syntaxhighlight> * The <code>failregex</code> variable is used by fail2ban to filter our webserver access logs by matching the regex string. * The <code><HOST></code> variable is replaced by the IP address making the request to the webserver. * The <code>%(badbots)s</code> part is used to substitute the contents of the <code>badbots</code> variable we declared earlier. ==== Apache ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> -.*"(GET|POST|HEAD).*HTTP.*"(?:%(badbots)s)"$ ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> \- \S+.*\"(GET|POST|HEAD).*\S+\".*(?:%(badbots)s).*"$ ignoreregex = </syntaxhighlight> === Web crawlers === We need to create the file <code>/etc/fail2ban/filter.d/suspaths.conf</code>. Our regex filter will match filesystem paths that are deemed suspicious in our webserver access logs. ==== Caddy ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*"uri":(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*"status":4\d{2}.* ignoreregex = </syntaxhighlight> ==== Apache ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*" ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*\"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).* ignoreregex = </syntaxhighlight> === jail.local === First copy the jail configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Now edit <code>/etc/fail2ban/jail.local</code>. Add the following contents under HTTP servers in the JAILS section. Uncomment one of the lines for the <code>action</code> variable, depending our firewall software. <syntaxhighlight lang="bash"> # # JAILS # # # HTTP servers # [badbots] enabled = true filter = badbots #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto [suspaths] enabled = true filter = suspaths #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto </syntaxhighlight> The variables above can be tweaked to user preference. For more information on fail2ban configuration, consult <code>man fail2ban</code><ref>[https://manpages.debian.org/testing/fail2ban/jail.conf.5.en.html fail2ban(8)], Debian man pages, accessed 2026-07-15</ref> and <code>man jail.conf</code><ref>[https://manpages.debian.org/trixie/fail2ban/jail.conf.5.en.html jail.conf(5)], Debian man pages, accessed 2026-07-15</ref>. == Starting the service == Now that we have our configuration files in place, it's time to enable and start the fail2ban service. <syntaxhighlight lang="bash"> # systemd sudo systemctl enable --now fail2ban.service # SysV init, OpenRC, BSD init sudo service fail2ban start </syntaxhighlight> We can check information on our fail2ban jails with the following commands. <syntaxhighlight lang="bash"> # Check the status of our jails sudo fail2ban-client status # See which hosts have been banned by fail2ban sudo fail2ban-client banned # Check stats of our jails sudo fail2ban-client stats </syntaxhighlight> == References == <references /> 8ddfe090641c55af64472dbfba8939e7c9e8de82 5859 5853 2026-07-17T00:36:14Z Hyperreal 388 /* Apache */ wikitext text/x-wiki {{GuideWarning}} == Requirements == * A configured public-facing webserver, such as Caddy, Apache, or Nginx. This guide will cover those three. * A firewall solution, such as firewalld, UFW, nftables, PF, or iptables. * The webserver is hosted on a Linux distribution or *BSD. * fail2ban from the host distribution's package repositories. == Configuring Fail2Ban == Ensure the above requirements are met. In this guide, we'll assume the fail2ban configuration files are located under <code>/etc/fail2ban</code>. We'll be creating three files: * <code>/etc/fail2ban/filter.d/badbots.conf</code> * <code>/etc/fail2ban/filter.d/suspaths.conf</code> * <code>/etc/fail2ban/jail.local</code> === AI bots === The AI bot names are taken from the ai-robots-txt GitHub repository<ref>[https://raw.githubusercontent.com/ai-robots-txt/ai.robots.txt/refs/heads/main/robots.json robots.json], GitHub, accessed 2026-07-15</ref>. We can add or remove whichever ones we like. The names will be filtered by matching regex for the User-Agent from our webserver access logs. The regex used will depend on the logging format of our webserver. First, we'll create the file <code>/etc/fail2ban/filter.d/badbots.conf</code>. We should add the following contents. <syntaxhighlight lang="bash"> [Definition] badbots = AddSearchBot|AgentTimes|AI2Bot|AI2Bot-DeepResearchEval|Ai2Bot-Dolma|aiHitBot|AIWebIndex|amazon-kendra|amazon-QBusiness|Amazonbot|AmazonBuyForMe|Amzn-SearchBot|Amzn-User|Andibot|Anomura|anthropic-ai|ApifyBot|ApifyWebsiteContentCrawler|Applebot|Applebot-Extended|Aranet-SearchBot|atlassian-bot|Awario|AzureAI-SearchBot|bedrockbot|bigsur\.ai|Bravebot|Brightbot|Brightbot 1\.0|BuddyBot|Bytespider|CCBot|Channel3Bot|ChatGLM-Spider|ChatGPT Agent|ChatGPT-User|Claude-Code|Claude-SearchBot|Claude-User|Claude-Web|ClaudeBot|Cloudflare-AutoRAG|CloudVertexBot|Code|cohere-ai|cohere-training-data-crawler|Cotoyogi|CragCrawler|Crawl4AI|Crawlspace|Cursor|Datenbank Crawler|DeepSeekBot|Devin|Diffbot|DuckAssistBot|Echobot Bot|EchoboxBot|ExaBot|FacebookBot|facebookexternalhit|Factset_spyderbot|FirecrawlAgent|FriendlyCrawler|GeistHaus-PageFetcher|Gemini-Deep-Research|Google-Agent|Google-CloudVertexBot|Google-Extended|Google-Firebase|Google-Gemini-CLI|Google-NotebookLM|GoogleAgent-Mariner|GoogleAgent-URLContext|GoogleOther|GoogleOther-Image|GoogleOther-Video|GPTBot|HenkBot|iAskBot|iaskspider|iaskspider/2\.0|IbouBot|ICC-Crawler|ImagesiftBot|imageSpider|img2dataset|ISSCyberRiskCrawler|kagi-fetcher|Kangaroo Bot|Kimi-User|KlaviyoAIBot|KunatoCrawler|laion-huggingface-processor|LAIONDownloader|LCC|LinerBot|Linguee Bot|LinkupBot|Manus-User|meta-externalagent|Meta-ExternalAgent|meta-externalfetcher|Meta-ExternalFetcher|meta-webindexer|MistralAI-User|MistralAI-User/1\.0|Mozilla-Tabstack|MyCentralAIScraperBot|NagetBot|netEstate Imprint Crawler|newsai|NotebookLM|NovaAct|OAI-SearchBot|omgili|omgilibot|OpenAI|opencode|operator|PanguBot|Panscient|panscient\.com|Perplexity-User|PerplexityBot|PetalBot|PhindBot|Poggio-Citations|Poseidon Research Crawler|QualifiedBot|Querit-SearchBot|QueritBot|QuillBot|quillbot\.com|SBIntuitionsBot|Scrapy|SemrushBot-OCOB|SemrushBot-SWA|Shap-User|ShapBot|Sidetrade indexer bot|Spider|TavilyBot|Terra Cotta|TerraCotta|Thinkbot|TikTokSpider|Timpibot|TongyiBot|Trae|TwinAgent|UseAI|VelenPublicWebCrawler|WARDBot|Webzio-Extended|webzio-extended|wpbot|WRTNBot|YaK|YandexAdditional|YandexAdditionalBot|YiyanBot|YouBot|ZanistaBot|Tuwunel|Synapse </syntaxhighlight> The <code>badbots</code> variable contains a string that is meant to be substituted into a regex filter. The <code>BotName|OtherBotName</code> is regular expression syntax that matches any of the listed bot names. The <code>|</code> is like a [https://en.wikipedia.org/wiki/Logical_disjunction logical OR operator]. In the <code>badbots</code> variable above, any one of the listed bots will be matched by our regex filter. If any of the bots are present in the User-Agent field of our webserver logs, fail2ban will take the IP associated with that request and add it to the jail, thereby blocking any future requests from that IP for a certain amount of time that we define later. The next step is to add a <code>failregex</code> variable to <code>/etc/fail2ban/filter.d/badbots.conf</code>. We can refer to the webserver subsections below for which regex to use. Each filter must have the <code>ignoreregex =</code> variable declared in the file, even if the value is empty. We won't need to define it for our use-case, but it still needs to be in the file. In the following sections, the <code>failregex</code> variable is different for each webserver that uses a different log format. Caddy uses a JSON structured format, while Apache and Nginx use the [https://en.wikipedia.org/wiki/Common_Log_Format Common Log Format]. ==== Caddy ==== <syntaxhighlight lang="bash"> failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*".*(?:%(badbots)s).*".* ignoreregex = </syntaxhighlight> * The <code>failregex</code> variable is used by fail2ban to filter our webserver access logs by matching the regex string. * The <code><HOST></code> variable is replaced by the IP address making the request to the webserver. * The <code>%(badbots)s</code> part is used to substitute the contents of the <code>badbots</code> variable we declared earlier. ==== Apache ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> -.*"(GET|POST|HEAD).*HTTP.*"(?:%(badbots)s)$ ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> \- \S+.*\"(GET|POST|HEAD).*\S+\".*(?:%(badbots)s).*"$ ignoreregex = </syntaxhighlight> === Web crawlers === We need to create the file <code>/etc/fail2ban/filter.d/suspaths.conf</code>. Our regex filter will match filesystem paths that are deemed suspicious in our webserver access logs. ==== Caddy ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*"uri":(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*"status":4\d{2}.* ignoreregex = </syntaxhighlight> ==== Apache ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*" ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*\"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).* ignoreregex = </syntaxhighlight> === jail.local === First copy the jail configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Now edit <code>/etc/fail2ban/jail.local</code>. Add the following contents under HTTP servers in the JAILS section. Uncomment one of the lines for the <code>action</code> variable, depending our firewall software. <syntaxhighlight lang="bash"> # # JAILS # # # HTTP servers # [badbots] enabled = true filter = badbots #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto [suspaths] enabled = true filter = suspaths #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto </syntaxhighlight> The variables above can be tweaked to user preference. For more information on fail2ban configuration, consult <code>man fail2ban</code><ref>[https://manpages.debian.org/testing/fail2ban/jail.conf.5.en.html fail2ban(8)], Debian man pages, accessed 2026-07-15</ref> and <code>man jail.conf</code><ref>[https://manpages.debian.org/trixie/fail2ban/jail.conf.5.en.html jail.conf(5)], Debian man pages, accessed 2026-07-15</ref>. == Starting the service == Now that we have our configuration files in place, it's time to enable and start the fail2ban service. <syntaxhighlight lang="bash"> # systemd sudo systemctl enable --now fail2ban.service # SysV init, OpenRC, BSD init sudo service fail2ban start </syntaxhighlight> We can check information on our fail2ban jails with the following commands. <syntaxhighlight lang="bash"> # Check the status of our jails sudo fail2ban-client status # See which hosts have been banned by fail2ban sudo fail2ban-client banned # Check stats of our jails sudo fail2ban-client stats </syntaxhighlight> == References == <references /> 1dcbc83efdc48f5d9e3a12f2c7b0859214d9d2f6 5860 5859 2026-07-17T00:36:27Z Hyperreal 388 /* Nginx */ wikitext text/x-wiki {{GuideWarning}} == Requirements == * A configured public-facing webserver, such as Caddy, Apache, or Nginx. This guide will cover those three. * A firewall solution, such as firewalld, UFW, nftables, PF, or iptables. * The webserver is hosted on a Linux distribution or *BSD. * fail2ban from the host distribution's package repositories. == Configuring Fail2Ban == Ensure the above requirements are met. In this guide, we'll assume the fail2ban configuration files are located under <code>/etc/fail2ban</code>. We'll be creating three files: * <code>/etc/fail2ban/filter.d/badbots.conf</code> * <code>/etc/fail2ban/filter.d/suspaths.conf</code> * <code>/etc/fail2ban/jail.local</code> === AI bots === The AI bot names are taken from the ai-robots-txt GitHub repository<ref>[https://raw.githubusercontent.com/ai-robots-txt/ai.robots.txt/refs/heads/main/robots.json robots.json], GitHub, accessed 2026-07-15</ref>. We can add or remove whichever ones we like. The names will be filtered by matching regex for the User-Agent from our webserver access logs. The regex used will depend on the logging format of our webserver. First, we'll create the file <code>/etc/fail2ban/filter.d/badbots.conf</code>. We should add the following contents. <syntaxhighlight lang="bash"> [Definition] badbots = AddSearchBot|AgentTimes|AI2Bot|AI2Bot-DeepResearchEval|Ai2Bot-Dolma|aiHitBot|AIWebIndex|amazon-kendra|amazon-QBusiness|Amazonbot|AmazonBuyForMe|Amzn-SearchBot|Amzn-User|Andibot|Anomura|anthropic-ai|ApifyBot|ApifyWebsiteContentCrawler|Applebot|Applebot-Extended|Aranet-SearchBot|atlassian-bot|Awario|AzureAI-SearchBot|bedrockbot|bigsur\.ai|Bravebot|Brightbot|Brightbot 1\.0|BuddyBot|Bytespider|CCBot|Channel3Bot|ChatGLM-Spider|ChatGPT Agent|ChatGPT-User|Claude-Code|Claude-SearchBot|Claude-User|Claude-Web|ClaudeBot|Cloudflare-AutoRAG|CloudVertexBot|Code|cohere-ai|cohere-training-data-crawler|Cotoyogi|CragCrawler|Crawl4AI|Crawlspace|Cursor|Datenbank Crawler|DeepSeekBot|Devin|Diffbot|DuckAssistBot|Echobot Bot|EchoboxBot|ExaBot|FacebookBot|facebookexternalhit|Factset_spyderbot|FirecrawlAgent|FriendlyCrawler|GeistHaus-PageFetcher|Gemini-Deep-Research|Google-Agent|Google-CloudVertexBot|Google-Extended|Google-Firebase|Google-Gemini-CLI|Google-NotebookLM|GoogleAgent-Mariner|GoogleAgent-URLContext|GoogleOther|GoogleOther-Image|GoogleOther-Video|GPTBot|HenkBot|iAskBot|iaskspider|iaskspider/2\.0|IbouBot|ICC-Crawler|ImagesiftBot|imageSpider|img2dataset|ISSCyberRiskCrawler|kagi-fetcher|Kangaroo Bot|Kimi-User|KlaviyoAIBot|KunatoCrawler|laion-huggingface-processor|LAIONDownloader|LCC|LinerBot|Linguee Bot|LinkupBot|Manus-User|meta-externalagent|Meta-ExternalAgent|meta-externalfetcher|Meta-ExternalFetcher|meta-webindexer|MistralAI-User|MistralAI-User/1\.0|Mozilla-Tabstack|MyCentralAIScraperBot|NagetBot|netEstate Imprint Crawler|newsai|NotebookLM|NovaAct|OAI-SearchBot|omgili|omgilibot|OpenAI|opencode|operator|PanguBot|Panscient|panscient\.com|Perplexity-User|PerplexityBot|PetalBot|PhindBot|Poggio-Citations|Poseidon Research Crawler|QualifiedBot|Querit-SearchBot|QueritBot|QuillBot|quillbot\.com|SBIntuitionsBot|Scrapy|SemrushBot-OCOB|SemrushBot-SWA|Shap-User|ShapBot|Sidetrade indexer bot|Spider|TavilyBot|Terra Cotta|TerraCotta|Thinkbot|TikTokSpider|Timpibot|TongyiBot|Trae|TwinAgent|UseAI|VelenPublicWebCrawler|WARDBot|Webzio-Extended|webzio-extended|wpbot|WRTNBot|YaK|YandexAdditional|YandexAdditionalBot|YiyanBot|YouBot|ZanistaBot|Tuwunel|Synapse </syntaxhighlight> The <code>badbots</code> variable contains a string that is meant to be substituted into a regex filter. The <code>BotName|OtherBotName</code> is regular expression syntax that matches any of the listed bot names. The <code>|</code> is like a [https://en.wikipedia.org/wiki/Logical_disjunction logical OR operator]. In the <code>badbots</code> variable above, any one of the listed bots will be matched by our regex filter. If any of the bots are present in the User-Agent field of our webserver logs, fail2ban will take the IP associated with that request and add it to the jail, thereby blocking any future requests from that IP for a certain amount of time that we define later. The next step is to add a <code>failregex</code> variable to <code>/etc/fail2ban/filter.d/badbots.conf</code>. We can refer to the webserver subsections below for which regex to use. Each filter must have the <code>ignoreregex =</code> variable declared in the file, even if the value is empty. We won't need to define it for our use-case, but it still needs to be in the file. In the following sections, the <code>failregex</code> variable is different for each webserver that uses a different log format. Caddy uses a JSON structured format, while Apache and Nginx use the [https://en.wikipedia.org/wiki/Common_Log_Format Common Log Format]. ==== Caddy ==== <syntaxhighlight lang="bash"> failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*".*(?:%(badbots)s).*".* ignoreregex = </syntaxhighlight> * The <code>failregex</code> variable is used by fail2ban to filter our webserver access logs by matching the regex string. * The <code><HOST></code> variable is replaced by the IP address making the request to the webserver. * The <code>%(badbots)s</code> part is used to substitute the contents of the <code>badbots</code> variable we declared earlier. ==== Apache ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> -.*"(GET|POST|HEAD).*HTTP.*"(?:%(badbots)s)$ ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> failregex = ^<HOST> \- \S+.*\"(GET|POST|HEAD).*\S+\".*(?:%(badbots)s).*$ ignoreregex = </syntaxhighlight> === Web crawlers === We need to create the file <code>/etc/fail2ban/filter.d/suspaths.conf</code>. Our regex filter will match filesystem paths that are deemed suspicious in our webserver access logs. ==== Caddy ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^\{"level":"info","ts":\d+\.\d+,"logger":"http\.log\.access\.log\d*","msg":"handled request".*"remote_ip":"<HOST>".*"uri":(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*"status":4\d{2}.* ignoreregex = </syntaxhighlight> ==== Apache ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).*" ignoreregex = </syntaxhighlight> ==== Nginx ==== <syntaxhighlight lang="bash"> [Definition] failregex = ^<HOST>.*\"(GET|POST|HEAD).*(password\.txt|passwords\.txt|config\.json|wp-login|wp-include|wp-admin|wordpress|\.env|info\.php|phpinfo|Dockerrun\.aws\.json|sftp\.json|sftp-config\.json|security\.txt|\.DS_Store|login\.aspx|filemanager\.php|blog|temp|old|backup|debug\/pprof|jsquery\.php|updates\.php|plugins\.php|post\.php|manager\.php|xmlrpc\.php|\.git|\.svn|secrets\.yaml|secrets\.json|credentials|\.yarnrc).* ignoreregex = </syntaxhighlight> === jail.local === First copy the jail configuration. <syntaxhighlight lang="bash"> sudo cp -v /etc/fail2ban/jail.conf /etc/fail2ban/jail.local </syntaxhighlight> Now edit <code>/etc/fail2ban/jail.local</code>. Add the following contents under HTTP servers in the JAILS section. Uncomment one of the lines for the <code>action</code> variable, depending our firewall software. <syntaxhighlight lang="bash"> # # JAILS # # # HTTP servers # [badbots] enabled = true filter = badbots #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto [suspaths] enabled = true filter = suspaths #action = firewallcmd-allports #action = iptables-allports #action = nftables-allports #action = ipfw #action = pf #action = ufw logpath = /path/to/webserver/access/log port = http,https maxretry = 5 findtime = 600 bantime = 90d backend = auto </syntaxhighlight> The variables above can be tweaked to user preference. For more information on fail2ban configuration, consult <code>man fail2ban</code><ref>[https://manpages.debian.org/testing/fail2ban/jail.conf.5.en.html fail2ban(8)], Debian man pages, accessed 2026-07-15</ref> and <code>man jail.conf</code><ref>[https://manpages.debian.org/trixie/fail2ban/jail.conf.5.en.html jail.conf(5)], Debian man pages, accessed 2026-07-15</ref>. == Starting the service == Now that we have our configuration files in place, it's time to enable and start the fail2ban service. <syntaxhighlight lang="bash"> # systemd sudo systemctl enable --now fail2ban.service # SysV init, OpenRC, BSD init sudo service fail2ban start </syntaxhighlight> We can check information on our fail2ban jails with the following commands. <syntaxhighlight lang="bash"> # Check the status of our jails sudo fail2ban-client status # See which hosts have been banned by fail2ban sudo fail2ban-client banned # Check stats of our jails sudo fail2ban-client stats </syntaxhighlight> == References == <references /> a613e6ae5654cf16dc091611ba0c2194659726b7 0 1292 5854 5577 2026-07-16T13:32:42Z Xuruh 407 This project has been retired. This page is pending administrator review for deletion. wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 5855 5854 2026-07-16T13:42:08Z Xuruh 407 Request deletion: project retired and page no longer relevant wikitext text/x-wiki {{Delete|Project has rebranded. Please delete this page.}} 430f0ae827ab8b82bab6fb6d6a07eab3058ee8c1 5857 5855 2026-07-16T14:18:58Z Atmois 13 Reverted edits by [[Special:Contributions/Xuruh|Xuruh]] ([[User talk:Xuruh|talk]]) to last revision by [[User:Ow0cast|Ow0cast]] wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxerlogo.png|150px]] | caption = The Fluxer World logo | title = Fluxer World | releasestatus = Beta | lastrelease = 1.0.86 | languages = TypeScript, Erlang, React Native | developers = Xuruh and Contributors | website = https://fluxer.world | sourcecode = https://github.com/fluxerworld/fluxerworld | license = AGPLv3 }} '''Fluxer World''' is a free, open-source, and cross-platform instant messaging and VoIP platform with end-to-end encryption for direct messages and group conversations. It is a fork of [[Fluxer]], with divergent features focused on encryption, mobile support, and self-hostable infrastructure. ==Overview== Fluxer World is available on Linux (AppImage, tar.gz, [[RPM]], .deb, [[flatpak|Flatpak]], AUR), Windows (NSIS installer), macOS (dmg), Android (APK via [https://f-droid.org F-Droid] and direct download), and iOS. A Progressive Web App is available at https://fluxer.world. ==Privacy and encryption== Fluxer World is designed to be privacy-conscious. Direct messages and group conversations are end-to-end encrypted using the Olm and Megolm cryptographic ratchets from the Matrix protocol. Because chats are end-to-end encrypted, administrators are not able to read their contents. Fluxerworld also does not monitor user logs. ==Features== Notable features of Fluxer World include: * End-to-end encryption for 1:1 direct messages and Group DMs using the [https://gitlab.matrix.org/matrix-org/olm Olm and Megolm] cryptographic ratchets (Matrix-compatible). * Native React Native mobile applications for Android with feature parity to the desktop client, including voice/video calls and screen sharing. * Communities, with organized channels, categories, roles and moderation tools. * Voice and video calls with screen sharing, backed by [https://livekit.io LiveKit]. * Custom emotes and stickers. * Media attachments like images, videos, audio or text. Note that attachments have an expiration date depending on their size. * Message search, with ability to filter by users, channels, dates, and more. * A bot and webhook API. ==Downloads== Fluxer World provides clients for multiple platforms, available via the Snap Store, AUR, Fedora Copr, F-Droid, GitHub Releases, and more. ===Install via terminal=== * '''Snap:''' <code>sudo snap install fluxer-world</code> * '''Arch (AUR):''' <code>yay -S fluxer-world-bin</code> * '''Fedora (Copr):''' <code>sudo dnf copr enable xuruh/fluxer-world && sudo dnf install fluxer-world</code> * '''F-Droid:''' add the repo <code>https://fluxer.world/fdroid/repo</code> in F-Droid settings ===Windows=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (x64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Installer (ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Portable (x64)] ===macOS=== * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Apple Silicon)] * [https://github.com/fluxerworld/fluxerworld/releases/latest DMG (Intel)] ===Linux=== * [https://snapcraft.io/fluxer-world Snap Store] * [https://aur.archlinux.org/packages/fluxer-world-bin AUR] * [https://copr.fedorainfracloud.org/coprs/xuruh/fluxer-world/ Fedora Copr] * [https://github.com/fluxerworld/fluxerworld/releases/latest .deb (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest .rpm (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest AppImage (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest tar.gz (x64 / ARM64)] * [https://github.com/fluxerworld/fluxerworld/releases/latest Flatpak] ===Mobile=== * [https://github.com/fluxerworld/fluxerworld/releases/latest Android APK] * [https://fluxer.world/fdroid/repo F-Droid] * [https://github.com/fluxerworld/fluxerworld/releases/latest iOS IPA] ==History== Fluxer World was forked from [[Fluxer]] to focus on end-to-end encryption and first-class mobile support. End-to-end encrypted direct messages shipped in May 2026, followed by Group DM encryption in late May 2026. ==Relationship to Fluxer== Fluxer World shares its core server architecture with upstream [[Fluxer]] (Erlang/OTP gateway, TypeScript API), but diverges in client implementation, encryption layer, and packaging targets. Both projects are AGPLv3. ==See also== * [[Fluxer]] — upstream project ==External links== * [https://fluxer.world Official website] * [https://github.com/fluxerworld/fluxerworld Source code on GitHub] * [https://github.com/fluxerworld/fluxerworld/releases Releases] [[Category:Instant messaging]] [[Category:VoIP]] [[Category:Free software]] df895a581cfcb286334b2d33406da6d9a25d3dab 1 1385 5856 2026-07-16T13:42:34Z Xuruh 407 /* Deletion request */ new section wikitext text/x-wiki == Deletion request == == Deletion request == Requesting deletion of this page. Project has been rebranded and I no longer wish to maintain this page. Thank you. [[User:Xuruh|Xuruh]] ([[User talk:Xuruh|talk]]) 13:42, 16 July 2026 (UTC) a2aa4dda2c3a1f9478d0931d4d3a62f63f6de391 5858 5856 2026-07-16T14:20:11Z Atmois 13 /* Deletion request 2 */ Reply wikitext text/x-wiki == Deletion request == == Deletion request == Requesting deletion of this page. Project has been rebranded and I no longer wish to maintain this page. Thank you. [[User:Xuruh|Xuruh]] ([[User talk:Xuruh|talk]]) 13:42, 16 July 2026 (UTC) :Pages will not be deleted due to rebranding and/or software becoming unmaintained. You are welcome to not work on the page further, we will just update the information on the page accordingly. [[User:Atmois|Atmois]] ([[User talk:Atmois|talk]]) 14:20, 16 July 2026 (UTC) fb4548d5db0d05027b29e6ccb205ec0ceb709230 0 1160 5862 4788 2026-07-17T04:34:22Z PhantasNick 291 Standard Page about KDE Linux, everything was sourced from the KDE Linux website just dont have time to add the citations wikitext text/x-wiki [[Category:Linux Distributions]] {{stub}} {{Needs Citations}} {{DistributionInfobox | title = KDE Linux | image = [[File:Kde-linux-logo.png|frameless]] | caption = KDE Linux Logo | releasestatus = Maintained | releasemodel = Rolling | packagemanager = [[flatpak]], [[AppImage]] and [[snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = x86-64 | website = [https://www.linux.kde.org kde.org/linux] }} KDE Linux is a free, open-source, user-focused operating system being built by KDE to include the best implementation of everything KDE has to offer, using the most advanced technologies. KDE Linux is the 2nd distribution project from the KDE Team, the first being [[KDE Neon]]. KDE Linux vastly differs from [[KDE Neon | Neon]] as its designed to be more stable with its immutable filesystem, transactional image based updates, OS rollback, Btrfs snapshots for user files, and a built-in backup system. With its immutable nature also means there is no traditional package manager instead supporting [[flatpak]], [[AppImage]] and [[snap]]. 94b70ee37535a14f092bc2479f37ec4d96c8b240 0 1206 5863 5450 2026-07-17T09:38:17Z Imnotgoodatnames 121 uppercase wikitext text/x-wiki '''KDE Neon''' is a [[Linux Distributions|Linux distribution]] based on [[Ubuntu|Ubuntu LTS]] developed by the [[KDE]] team, wich provides users with the latest features of the [[Plasma|KDE Plasma]] desktop environment<ref>{{Cite|url=https://neon.kde.org/faq#what-is-neon|title=KDE Neon's FAQ, What is KDE Neon question.|accessdate=2026/05/24}}</ref>. It is essentially the testing ground where new KDE Plasma updates are tested and used before being introduced to other distros using KDE Plasma (Much like how [[Fedora]] is [[Red Hat Enterprise Linux|RHEL]]'s testing ground). However, apart from the KDE Plasma desktop, the distro itself follows the stable release schedule of [[Ubuntu|Ubuntu LTS]], making it a half stable half rolling distro<ref>{{Cite|url=https://neon.kde.org/faq#is-it-rolling|title=Official statement in the KDE Neon FAQ on this.|accessdate=2026/05/26}}</ref>. because it is developed by the KDE developers, it can be seen as a "pure" KDE Plasma experience. {{DistributionInfobox|title=KDE Neon|image=[[File:KDE-Neon-logo.png]]|caption=The KDE Neon logo|releasestatus=Maintained|releasemodel=Stable Release|packagemanager=[[APT]], PackageKit|defaultdesktops=KDE Plasma|usagetype=Desktop|architectures=x86_64|website=[https://neon.kde.org/index&#124; KDE Neon]{{Dead Link|2026-05-26|404}}|Written in=C, C++, QT 6}} == History == KDE neon first started taking shape in late 2015 as a way to provide a rolling release of fresh KDE software on top of [[Ubuntu]]'s stable OS base. The first daily installation images began being built in January 2016. The first general release of KDE Neon was on 8 June 2016, it was based on an [[Ubuntu]] 16.04 base, using [[Plasma|KDE Plasma]] 5.6. The Latest version of KDE Neon, 6.6, was released on 16 February 2026. [[File:KDE-Neon-6.6-big.png|thumb|A fresh installation of KDE Neon 6.6.]] == Features == KDE Neon == Installation == KDE Neon uses the [[Calamares]] installer. Specifications for installation are: {| class="wikitable" |+ ! !Minimum !Recommended ! |- |Proccesor |1 GHz X86-64 CPU |2 GHz Dual-Core X86-64 CPU Or higher | |- |RAM |2GB |4GB and higher | |- |Storage |20 GB |40 GB and higher | |} Note that these minimum specs will just get you to run it at the bare minimum == References == 3a03e2a38f236cb3556d312922c1323ee1f475f2 0 1386 5864 2026-07-17T16:41:43Z Lawl 419 write some of zola page wikitext text/x-wiki {{Stub}} '''Zola''' is a small, fast and relatively simple [[static site generator]] (SSG) similar to [[Jekyll]] and [[Hugo]]. It is written in the [[Rust]] programming language, and uses the [[Tera]] template engine.<ref>[https://www.getzola.org/documentation/getting-started/overview/ Zola's "Getting Started" page]</ref> The content for Zola is written in [[CommonMark]], a derivative of [[Markdown]]. It contains some extra features on top of this, such as parsing footnotes, Github flavored tables, Github flavored task lists and strikethrough. == Getting Started == Zola provides the user with a simple [[Command Line Interface]] to generate, initialize and even temporarily serve Zola built content. 07b740f1fb8ac82cf78c9261fdde12651438a52b 0 1025 5865 4184 2026-07-18T02:44:32Z PhantasNick 291 Added Stub Prompt wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Omarchy | image = [[File:omarchy-logo.svg | thumb]] | caption = The Omarchy Logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[Hyprland]] | usagetype = Desktop | architectures = x86_64 | website = [https://omarchy.org omarchy.org] }} ed06ad72b87eeece7ceff7617ee81ee160e83704 0 1096 5866 5268 2026-07-18T02:47:21Z PhantasNick 291 Needs Citations wikitext text/x-wiki [[Category:Linux Distributions]] {{Stub}} {{Needs Citations}} {{DistributionInfobox | title = Pear OS | image = [[File:pearos.png|pearos.png]] | caption = Logo of Pear OS | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = [[Pacman]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = x86_64 | website = https://pearos.xyz/ }} '''Pear OS''' is an operating system based on [[Arch Linux]] with default [[Linux kernel]] (version 6.17) and [[systemd|SystemD]]. It is developed by one person. Its main purpose is to give Linux users the feeling of [[MacOS]]. == Information == Pear OS was originally developed as a web OS in 2010. The OS got later in 2014 sold to an unknown company, however in ~2022 Alexandru Bălan started developing the software again now it's available and free. d931687b4fa2738d2f47a8b4ba4c4ea8db6d1138 0 891 5867 4335 2026-07-18T02:48:08Z PhantasNick 291 Stub and Needs Citations wikitext text/x-wiki {{Stub}} {{Needs Citations}} {{DistributionInfobox | title = SteamOS | image = [[File:SteamOS wordmark.svg|Thumb]] | caption = The SteamOS wordmark | releasestatus = Maintained | packagemanager = [[Pacman]] | releasemodel = Stable | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop, Handheld | architectures = x86_64, Arm64 (in development) | website = [https://store.steampowered.com/steamos store.steampowered.com/steamos] }} SteamOS is an Immutable [[Arch Linux|Arch]]-based Linux Distribution produced by [[wikipedia:Valve_Corporation|Valve]] for it's use on proprietary hardware such as the [[wikipedia:Steam_Deck|Steam Deck.]] SteamOS focuses mainly on the user gaming experience by offering easy-access to Steam services such as the game library, Steam store and more. f686727dee54d932b7948bd5f0ceedbe9ef4660c 0 1175 5868 5276 2026-07-18T02:50:16Z PhantasNick 291 Needs Citations wikitext text/x-wiki {{Stub}} {{Needs Citations}} {{DistributionInfobox | title = TailsOS | image = [[File:Tails-logo.png]] | caption = TailsOS's logo | releasestatus = Maintained | releasemodel = Stable Release | packagemanager = [[APT]] | defaultdesktops = [[GNOME]] | usagetype = Desktop | architectures = x86_64 | website = [https://tails.net/index.en.html] }} [[Category:Linux Distributions]] [[File:TAILS 4.14 ENG 05 01 2021 15 39 25.png|thumb|TailsOS open to the "About Tails" screen]] '''TailsOS''' ''(or TAILS)'', short for '''"The Amnesic Incognito Live System"''', is a [[Debian]]-based privacy-focused [[Linux Distributions|Linux distribution]] intent on preserving anonymity against surveillance. Digital footprint is avoided through exclusively connecting to the internet via [[Tor]] and never writing to secondary storage unless explicitly told to do so. 3368d2b647ca9a34740e3e71f60493141e4fc7a9 0 659 5870 5218 2026-07-18T02:52:28Z PhantasNick 291 Needs Citations wikitext text/x-wiki {{stub}} {{Needs Citations}} {{DistributionInfobox |title=ChromeOS |image=[[File:ChromeOS Logo.svg]] |caption=ChromeOS Logo |releasestatus=Maintained |releasemodel=Stable |packagemanager=None |defaultdesktops=Chromium, Aura Shell |usagetype=Desktop |architectures=x86_64, IA-32, ARM, ARM64 |website = [http://chromeos.google chromeos.google] }} ChromeOS is a Linux distribution based on [[ChromiumOS]] designed and developed by Google in 2009. ChromeOS is composed mostly of proprietary software but includes open source software, such as the kernel itself.<ref>[http://source.chromium.org/chromiumos ChromiumOS], ChromiumOS Code Search, 2026-05-25 (Accessed: 2026-05-25)</ref> == References == 8e9ec1fd0ba5f5b12a32369b2714cb390b8010e9 0 659 5871 5870 2026-07-18T02:53:03Z PhantasNick 291 Undo revision [[Special:Diff/5870|5870]] by [[Special:Contributions/PhantasNick|PhantasNick]] ([[User talk:PhantasNick|talk]]) Whoops, turns out i can't see wikitext text/x-wiki {{stub}} {{DistributionInfobox |title=ChromeOS |image=[[File:ChromeOS Logo.svg]] |caption=ChromeOS Logo |releasestatus=Maintained |releasemodel=Stable |packagemanager=None |defaultdesktops=Chromium, Aura Shell |usagetype=Desktop |architectures=x86_64, IA-32, ARM, ARM64 |website = [http://chromeos.google chromeos.google] }} ChromeOS is a Linux distribution based on [[ChromiumOS]] designed and developed by Google in 2009. ChromeOS is composed mostly of proprietary software but includes open source software, such as the kernel itself.<ref>[http://source.chromium.org/chromiumos ChromiumOS], ChromiumOS Code Search, 2026-05-25 (Accessed: 2026-05-25)</ref> == References == 18a64892f7edbc4f6bfc412d7412580e30d2139a 0 809 5872 3613 2026-07-18T02:53:47Z PhantasNick 291 Stub wikitext text/x-wiki {{Stub}} [[Category:Linux Distributions]] {{DistributionInfobox | title = Funtoo Linux | image = [[File:funtoo.png|300px|Gentoo Linux logo matte]] | caption = The official Funtoo Linux logo | releasestatus = Discontinued | releasemodel = Rolling Release / Stable | packagemanager = [[portage]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = amd64, alpha, arm, arm64, hppa, ia64, loong, mips, m68k, ppc, riscv, s390, sparc, x86 | website = [https://www.funtoo.org/Welcome funtoo.org] }} [https://www.funtoo.org/Welcome Funtoo Linux] is a highly flexible, source-based [[Linux Distributions|Linux distribution]] founded in early 2008 by Daniel Robbins. Known for its emphasis on customization and performance optimization, '''Funtoo''' allows users to compile their entire system from source code, providing granular control over system components and features. 2e24ecb2973337a1522a377ec03f7e30aca4529f 0 198 5873 5843 2026-07-18T02:56:49Z PhantasNick 291 Modified Calculate hyperlink, unsure why instead of a wiki page it sent you to distro website wikitext text/x-wiki [[Category:Linux Distributions]] <!-- TODO: this sentence needs to be a banner - deviaze (@Deviaze) -->If you're new or interested in installing Linux on your device, see [[Guide:Switching to Linux|the guide]] and these [[Key Terms|common terms]] to get started on your journey. '''Linux''', also infrequently referred to as '''GNU/Linux''', is a collection of many operating systems, called '''distributions''', that use the [[Linux kernel]]. A Linux distribution (often referred to as a "distro") comes with some form of the Linux kernel, an [[Init System]], core utilities and libraries (such as the ones provided by [[GNU]]), a [[Package Manager]], and several other types of software. Distributions meant for general purpose desktop use often but not always provide a visual interface, called a [[Desktop Environments|Desktop Environment]] (such as [[Plasma|KDE Plasma]] or [[GNOME]]) or a [[Window Manager]] (such as [[i3]] or [[Hyprland]]). Linux is often used on server hardware and has recently been increasingly used on desktops as well. == List of Linux Distributions == This is in no way an all inclusive list of distributions and mainly covers the most popular ones. For a more comprehensive list of distributions, see [https://distrowatch.com Distrowatch] or this [[wikipedia:List_of_Linux_distributions|Wikipedia Article]]. Distributions are grouped by which distribution they are based on, and those in ''italics'' are abandoned. ==== Arch Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Arch Linux|'''Arch Linux''']] |'''An independent distribution focused on the KISS ''(Keep It Simple, Stupid)'' principle that focuses on being lightweight and flexible. Inspired by CRUX.<ref>[https://en.wikipedia.org/wiki/Arch_Linux Arch Linux], Wikipedia contributors, 2025-08-01 (Accessed: 2025-08-09)</ref>''' |- |[[Arco Linux|''Arco Linux'']] |''Arco Linux is a discontinued fork of Arch Linux designed to be friendly to new users.'' |- |[[Artix]] |A fork of Arch Linux, which avoids the usage of systemd. In its stead, it offers four alternative init systems in the pursuit of simplicity: OpenRC, [[runit]], [[dinit]], and [[s6]]. Each of them has its distinct differences, but the general goal stays the same: an init system should serve the purpose of an init system, complying with [[POSIX|POSIX standards]]. |- |[[AxOS]] |An Arch-based distribution with its own custom package manager [[Epsilon]]. It looks clean while remaining light. |- |[[CachyOS]] |CachyOS is an Arch-based distribution aimed at beginners and long-time Linux users; it is focused on optimization and stability, ships with its own Cachy Kernel, and uses a [[Calamares]] installer. |- |''[[CyberOS]] (CutefishOS)'' |''A discontinued Arch-based distribution with a custom CyberDE that looked similar to Mac OS X.'' |- |[[EndeavourOS]] |An Arch-based distribution that aims to be as user-friendly as Manjaro, but is closer in nature to Arch Linux overall. It aims to offer a decent amount of common applications used on Arch as well as including the Calamares installer. |- |[[Manjaro]] |An Arch-based rolling release distribution with a focus on user-friendliness and accessibility. Its aim is to be easy to set up and use.<ref>[https://wiki.manjaro.org/index.php/About_Manjaro#Overview]{{Dead Link|2026-05-25|404}}</ref> |- |[[Omarchy]] |An opinionated distribution specifically built for developers.<ref>[https://learn.omacom.io/2/the-omarchy-manual/91/welcome-to-omarchy Welcome to Omarchy], The Omarchy Manual (Accessed: 2026-05-25)</ref> |- |[[Pear os|Pear OS]] |An Arch-based distribution focused on giving Linux users the feeling of MacOs.<ref>[https://pearos.xyz/ pearOS], pearOS, 2026-05-25 (Accessed: 2026-05-25)</ref> |- |[[SteamOS]] |An immutable, proprietary, gaming-centric OS by Valve that is used to power the Steam Deck.<ref>[https://store.steampowered.com/steamos SteamOS], Valve, 2025 (Accessed: 2025-08-10)</ref> |} ==== Debian Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Astra Linux]] |A corporate Linux distribution used by the Russian government. |- |'''[[Debian]]''' |'''An independent distribution developed by the community-supported Debian Project which is developed openly and distributed freely.''' |- |[[Devuan]] |A fork of Debian, which avoids the usage of systemd. |- |[[GRML]] |A live CD distribution with a collection of tools for system administrators and text users. It has 2 GB of content that is decompressed on-the-fly. |- |[[Kali Linux]] |A Debian-based distribution made for security auditing and penetration testing. Has multiple versions, all of which serve different discrete purposes - they offer a "full" [[ISO]] with all of their security tools available. |- |[[ParrotOS]] |A Debian-based distribution comparable to Kali Linux, Parrot is designed for security, privacy, and development - one of its distinguishing features is that it is geared more towards daily use than Kali. ParrotOS has all the tools that are available in Kali Linux while also adding its own. |- |[[PikaOS]] |A gaming-focused distribution based on Debian Unstable. It's designed to work out-of-the-box, including up-to-date drivers and optimizations. |- |[[PureOS]] |PureOS is a FOSS-only Linux distribution and one of the only operating systems endorsed by the Free Software Foundation. |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[TailsOS]] |A distribution focused towards maximizing privacy through anonymity using [[Tor]]. It is meant to be used - albeit responsibly! - to circumvent censorship in oppressive governments or even individual situations, allowing the user to regain control of their right to possess digital freedom. |- |[[UOS]] |UOS is a corporate distribution developed by the Chinese company UnionTech Software. UOS uses [[Deepin]] as the default desktop environment. |- |[[Vanilla OS]] |An immutable and atomic Linux operating system with user experience as the main focus. |} ==== Fedora Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aurora]] |A rock-solid atomic variant of Fedora with KDE Plasma provided by [[Universal Blue]]. |- |[[Bazzite]] |A community-driven gaming distribution by Universal Blue. |- |[[Bluefin]] |A next generation [[bootc]] atomic distribution by Universal Blue. |- |[[Fedora|'''Fedora Linux''']] |'''A community-supported distribution sponsored by Red Hat. It aims to provide the latest software while maintaining a completely Free Software system. It serves as an upstream for RHEL.''' |- |[[Fedora Silverblue]] |A atomic variant of the [[Fedora]] Project designed with Security and Reliability in mind for Desktops, Servers and Containers |- |[[Nobara]] |A Fedora based distribution that comes pre installed with additional packages and configurations to make gaming and content creation easier for new Linux users. |- |[[Secureblue]] |A security focused desktop and server Linux distribution built on [[Fedora Atomic]]. |- |[[Ultramarine Linux]] |A distribution based on Fedora Linux with preapplied tweaks and sane defaults. |} ==== Gentoo Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[ChromeOS]] |A locked-up operating system developed by Google. It was initially designed to be used on Chromebooks. Can also be used on any computer via ChromeOS Flex. |- |''[[Funtoo]]'' |''A Gentoo fork, meant to make the usage of Gentoo simpler. Discontinued since 2024.'' |- |[[Gentoo]] |A highly flexible source-based distribution designed to have highly optimized and frequently updated software. |- |[[Calculate]] |A user friendly Gentoo based distribution focused on ease of use and backwards compatibility with Gentoo. |- |[[openFyde]] |A fully open-source fork of FydeOS. It strips out proprietary drivers and commercial patches to provide a completely open-source, decoupled ChromiumOS experience. |} ==== openSUSE Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Aeon]] |An immutable distribution designed to be easy to use and maintain; it exclusively uses the GNOME Desktop Environment |- |[[openSUSE]] |A group of community-developed distributions primarily sponsored by SUSE Designed for Desktop, Servers, Containers, and much more |- |[[Regata OS]] |A gaming-focused distribution with custom software made for ease of use |- |[[SUSE Linux Enterprise|SUSE Linux Enterprise (SLE)]] |An group of enterprise distributions created and maintained by SUSE, designed for Desktop, Servers, Containers, and much more |} ==== RHEL Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Alma Linux]] |A community-grounded distribution for production use. It aims to be stable while offering easy server setup for those who need to get a system running as fast and easily as possible. |- |''[[CentOS]]'' |''A discontinued Linux distribution that provided a free and open-source community-supported computing platform.'' |- |[[CentOS Stream]] |A rolling release distribution sponsored by Red Hat which is positioned as a midstream between Fedora Linux and RHEL. |- |[[Oreon|Oreon Linux]] |An Alma Linux-based distribution, developed by The Oreon Foundation. The project's goal is to provide more packages than Alma Linux by porting missing packages over from Fedora. |- |[[RHEL|'''Red Hat Enterprise Linux (RHEL)''']] |'''A commercial - once open to the public and now source-available<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> - distribution developed by Red Hat for the enterprise market.''' |- |[[Red Star OS|Red Star OS]] |A Red Hat-based OS made for the Democratic People's Republic of Korea (North Korea). |- |[[Rocky Linux]] |A community-managed distribution designed to be 100% compatible with RHEL. It aims to provide a production-grade enterprise operating system for users. |} ==== Slackware Family ==== {| class="wikitable" |- ! Distribution !! Description |- |'''[[Slackware]]''' |'''A highly customizable distribution that stresses ease of maintenance and reliability over cutting-edge software and automated tools.''' |- |[[Slax]] |A portable persistent distribution based off Slackware or Debian meant to be run on CDs/DVDs or USBs. |- |[[Zenwalk]] |A minimally modified version of Slackware. It aims to be a modern, multi-purpose Linux distribution.<ref>[https://en.wikipedia.org/wiki/Zenwalk Zenwalk], Wikipedia contributors, 2024-12-21 (Accessed: 2025-08-09)</ref> |} ==== Ubuntu Family ==== {| class="wikitable" |- ! Distribution !! Description |- |[[Linux Lite]] |An Ubuntu-based distribution targeted towards Windows users coming to Linux. It comes with [[XFCE]] as the default desktop environment. |- |[[Linux Mint]] |An Ubuntu-based Linux distribution that is targeted towards new Linux users, it also has a Debian-based version. |- |[[Pop!_OS]] |Pop!_OS is an Ubuntu-based Linux distribution developed by computer retailer System76 designed to have minimal amounts of [[bloat]]. |- |[[Trisquel]] |An Ubuntu-based Linux distribution that uses the Linux-libre kernel and avoids proprietary firmware. |- |'''[[Ubuntu]]''' |'''A distribution based on Debian developed by Canonical who provides commercial support for releases on desktops, servers and IoT devices.''' |- |[[ZorinOS]] |An Ubuntu-based Linux distribution designed especially for newcomers to Linux. |- |[[Kubuntu]] |An Ubuntu-based linux distribution that combines the power of Ubuntu together with the [[Plasma|KDE Plasma]] desktop. |- |[[KDE Neon]] |An Ubuntu-based linux distribution created by the KDE Plasma team to provide the newest versions of [[Plasma|KDE plasma]]. |} ==== Other Independent Distributions ==== {| class="wikitable" |- ! Distribution !! Description |- |[[AerynOS]] |A forward-looking, independant, atomic distribution built with bespoke [[Rust]] tooling |- |[[Alpine Linux]] |An independent distribution centered around security through minimalism. Not only is it used for [[Docker]] containers, but it is entirely free of GNU utilities. |- |[[Batocera]] |Batocera.linux is an open-source and completely free retro-gaming distribution. |- |[[Bedrock Linux]] |Bedrock Linux is an independent Linux meta-distribution which allows users to mix-and-match components from other, typically incompatible distributions. |- |[[Chimera Linux]] |Chimera Linux is a modern, general-purpose Linux distribution using a novel combination of core tools from FreeBSD, the LLVM toolchain, and the Musl C library. |- |[[CRUX Linux]] |CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is to keep it simple. The secondary focus is utilization of new Linux features and recent tools and libraries.<ref>[https://crux.nu/ CRUX | Main / HomePage], CRUX, 2025-04-21 (Accessed: 2025-08-09)</ref> |- |[[Dérive Linux]] |Dérive is a simple and independent Linux distribution based on the Musl libc and Busybox. |- |[[GKISS Linux]] |A fork of the original KISS Linux that uses the GNU libc rather than the Musl libc to add extra compatability. |- |[[GNU Guix System]] |A rolling release distribution created by GNU built around the Guix package manager and based on the Linux-libre kernel. |- |[[KDE Linux]] |A user-focused, general-purpose Linux distribution. It is built by KDE and it is meant to showcase the best implementation of everything KDE has to offer. |- |[[KISS Linux]] |A Linux distribution focused on simplicity and transparency. Maintained by the KISS community rather than the original creator. |- |[[NixOS]] |A distribution built around the Nix package manager, which provides atomic upgrades, rollbacks, and a declarative configuration model. |- ||[[Oasis Linux]] |Oasis is a small, fully statically linked BSD like Linux distribution. |- |[[postmarketOS]] |A distribution built mainly for mobile devices to bring full control and extend the life of consumer electronics. |- |[[Puppy Linux]] |A group of distributions designed to be small and full-featured. |- |[[SliTtaz GNU/Linux]] |SliTaz is a secure and high performance operating system using the Linux Kernel and GNU software.<ref>[https://slitaz.org/en/ SliTaz GNU/Linux], SliTaz, 2025-08-09 (Accessed: 2025-08-09)</ref> |- |[[Solus Linux]] |A semi-rolling release distribution. |- |[[Tinfoil Hat Linux|''Tinfoil Hat Linux'']] |''A compact, security-focused Linux distribution developed by the Shmoo Group, designed to run from removable media and provide a secure environment for handling sensitive data. The project is no longer maintained.'' |- |[[Void Linux]] |An independent distribution which supports both Musl and GLIBC system C libraries, uses the Runit service manager and their own package management system (XBPS). |- |[[Qubes OS]] |A security operating system that is built on the Xen Hypervisor and can make etc VMs like Windows or Fedora. |} == References == b80eabdf9c0ad5d52fd08753b2b0084c6b2a1789 0 225 5874 3667 2026-07-18T03:01:23Z PhantasNick 291 Added Stub wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|thumb]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64 | website = [https://redhat.com/rhel/ redhat.com] }} [[Category:Linux Distributions]] [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business customers.<ref>[https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux Red Hat Enterprise Linux], Red Hat, 2025-08-09 (Accessed: 2025-08-09)</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. == References == <references /> 15ed27c98a07d4b488b081a06de119060180f673 0 790 5875 4971 2026-07-18T03:02:17Z PhantasNick 291 Stub wikitext text/x-wiki {{Needs_Citations}} {{Stub}} {{DistributionInfobox | title = Red Star OS | image = [[File:Red Star OS Logo 2020.svg|190px]] | caption = Red Star OS logo | releasestatus = Maintained | releasemodel = Unknown | packagemanager = [[rpm]] | defaultdesktops = [[KDE Plasma]], [[GNOME]] | usagetype = Desktop | architectures = [[IA-32]], [[x86-64]], [[ARM]] | website = None }} '''Red Star OS ('''Korean: 붉은별''')''' is a [[Red Hat Enterprise Linux|Red Hat Linux]]-based [[Linux Distributions|distribution]] developed in the Democratic People's Republic of Korea (DPRK), made as a replacement for Windows in North Korea. It was first developed in 1998 by the Korea Computer Center. == Browser == '''Red Star OS''' relies on a heavily modified version of [[Firefox]] called ''[[Naenara]]'', which means "Our Country" in Korean. 310d1c971fe53f55577d1fc519d20e42af084ce7 0 277 5876 4153 2026-07-18T03:02:39Z PhantasNick 291 Stub wikitext text/x-wiki {{Needs_Citations}} {{Stub}} {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_Logo.png|thumb]] | caption = Rocky Linux | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[Category:Linux Distributions]] [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] Rocky Linux is a Linux distribution developed by RESF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit".<ref>{{Cite|url=https://www.resf.org/faq/is-resf-nonprofit|title=Is the RESF a non-profit? - RESF FAQ|author=RESF|accessdate=14 September 2025}}</ref> It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. edd92eb0fa1c3c718a815eb80938fd154d6277d5 0 233 5877 4974 2026-07-18T03:03:09Z PhantasNick 291 Stub wikitext text/x-wiki {{Stub}} {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{DistributionInfobox | title = Slackware Linux | image = [[File:Slackware_logo_from_the_official_Slackware_site.svg{{!}}class=skin-invert|frameless|upright=0.8|Slackware_logo]] | caption = Slackware Linux logo | releasestatus = Maintained | releasemodel = Stable, Rolling Release (Slackware -Current) | packagemanager = [[pkgtool]], slackpkg | defaultdesktops = [[KDE Plasma]], [[Xfce]] | usagetype = Desktop, Server | architectures = arm, i586, s390, x86_64 | website = [http://www.slackware.com slackware.com] }} [[Category:Linux Distributions]] [[File:Slackware 15.0 screenshot.png|thumb|Screenshot of Slackware 15.0 running [[KDE Plasma]]]] Slackware Linux is an independent [[Linux Distributions|Linux distribution]] and the oldest active distribution. The project was founded on July 17, 1993 by Patrick Volkerding. === History === Slackware first released as a fork of SoftLandingSystems (SLS) on July 16, 1993. By popular demand, to move away from SLS, the installer for Slackware was rewritten, using a tool called "Dialog". Version 1.1.0 released with the Dialog installer.<ref>[http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf A history of Slackware development], Eric Hameleers, 2009-10-09 (Accessed: 2025-08-09)</ref> Other notable releases of Slackware Linux include: * 1.2.0.1 - With Linux kernel 1.0 * 4.0.0 - First release to ship with KDE * 7.1 - First release to ship with [[GNOME]] The most recent release was on February 3, 2022 with the release of Slackware 15.0. == References == bf1b9ece423289e4efc950febdeba9684ff0bbca 0 653 5878 5656 2026-07-18T03:03:48Z PhantasNick 291 Stub wikitext text/x-wiki {{Stub}} {{DISPLAYTITLE:Pop!_OS}} {{Needs Citations}} {{DistributionInfobox | title = Pop!_OS | image = [[File:Pop! OS Icon.svg|frameless]] | caption = The Pop!_OS logo | releasestatus = Maintained | packagemanager = [[APT]] | defaultdesktops = COSMIC | usagetype = Desktop | architectures = x86_64 | website = https://system76.com/pop | releasemodel = Stable }} Pop!_OS is a free and open-source [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]] called [[COSMIC]]. Pop!OS is developed by the American Linux computer manufacturer System76. Pop!_OS is primarily built to be bundled with the computers built by System76, but can also be downloaded and installed on most computers. [[File:Poposrice.png|border|right|frameless|346x346px]] == <u>Features</u> == * Full support for [[Nvidia]] and [[AMD]] GPUs * Disk Encryption * Window and Workspace management * Recover Partition tool * GUI toggle 9d1f5e13299ea268f75160c1ce87b3c2ae3caeb5 0 248 5879 3686 2026-07-18T03:04:12Z PhantasNick 291 Stub wikitext text/x-wiki {{Stub}} [[Category:Linux Distributions]] {{Needs_Citations}} {{DistributionInfobox | title = Ubuntu | image = [[File:Logo-ubuntu cof-orange-hex.svg|100px]] | caption = Ubuntu Logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[GNOME]], [[Unity]] | usagetype = Desktop, Server | architectures = amd64, arm64, ppc64el, riscv, s390x | website = [https://ubuntu.com ubuntu.com] }} Ubuntu is a highly popular [[Linux Distributions|Linux distribution]] derived from [[Debian]] and developed by Canonical for the commercial market. The first version of Ubuntu was released on the October 20, 2004. Canonical profits from this distribution by providing 24/7 technical support to business costumers and extended long-term support for Ubuntu.<ref>https://ubuntu.com/pro Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> An interim release of Ubuntu is published every six months, with long-term support releases every two years. Canonical provides security updates and support for each release until the release reaches its end-of-life date. The LTS version receives 5 years of free updates or up to 10 years with Ubuntu Pro. The interim releases of Ubuntu receive 9 months of support.<ref>https://ubuntu.com/about/release-cycle Official Ubuntu Website, 2025 (Imported 7th June 2024)</ref> Ubuntu can be run locally, on a cloud, or in a [[Virtual Machine|VM]]. Ubuntu comes packaged with basic GNOME utilities as default and additionally from Ubuntu Software (formally Ubuntu Software Centre) and from APT, Ubuntu's default package manager. == References == <references /> b8f3b8c08a986afed2794c4f2c9f6640df30dd87 0 1246 5880 5517 2026-07-18T03:04:41Z PhantasNick 291 Added Stub wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Kubuntu | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[APT]], [[DPKG]], [[Snap]] | defaultdesktops = [[KDE Plasma]] | usagetype = Desktop | architectures = amd64 | website = [https://kubuntu.org/ kubuntu.com] | image = [[File:Kubuntu_logo.svg.png|100px]] | caption = Kubuntu Logo }} Kubuntu is an '''official''' [[flavor]] of [[Ubuntu]], where instead of using [[GNOME]] as its primary [[Desktop Environments|Desktop Environment]], it uses [[Plasma|KDE Plasma]], which aims to be '''user-friendly''', '''fast''', and '''customizable''', targeted at both '''newcomers''' and '''experienced''' Linux users.<ref>{{Cite|url=https://kubuntu.org/discover/|title=Discover - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref> This distribution is otherwise the '''same''' as the central Ubuntu [[Linux Distributions|Linux distribution]], with exception that it is '''community-run''' by contributors<ref>{{Cite|url=https://kubuntu.org/community/|title=Community - Kubuntu|author=Kubuntu|accessdate=25-05-2026}}</ref>. It also follows the same release schedule as Ubuntu, having a new release every '''6 months'''. 2acc789f79801b0bf3e83e8225a05814b000819f 0 656 5881 4977 2026-07-18T03:05:35Z PhantasNick 291 Added Stub wikitext text/x-wiki {{Stub}} {{DistributionInfobox |title=Batocera |image=[[file:Batocera-logo-art.png|frameless]] |caption=Batocera Logo |releasestatus=Maintained |releasemodel=Rolling Release |packagemanager=[[pacman]] |defaultdesktops=No Desktop |usagetype=placeholder |architectures=x86_64, Rpi4, Rpi5 |website=[https://batocera.org/ batocera.org] }} Batocera is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Batocera does not require any modification on your computer. Note that you must own the games you play in order to comply with the law. <ref>https://batocera.org/ Batocera website (Retrieved 18th June 2025)</ref> Batocera specialises in support for Raspberry Pis and other micro computers. Batocera offers emulation cores for retro consoles and retro home computers. == References == a8039027e8e8a759e1f46b043c84a75354f497f9 0 1365 5882 5799 2026-07-18T03:06:49Z PhantasNick 291 added Stub and Citation Templates wikitext text/x-wiki {{Stub}} {{Needs Citations}} '''GKISS Linux''' is a [[Linux]] distribution forked from [[KISS Linux]], adopting the [[GNU]] [[C]] standard library ([[glibc]]) rather than the [[musl]] [[C]] standard library. This enables much better compatibility with drivers especially, specifically the [[NVIDIA]] GPU drivers, as it does not work well with [[musl]]. However, due to the nature of [[glibc]], this means your system is much larger, and uses up more memory than the original KISS. It also makes [[statically linking]] your binaries more difficult, as [[glibc]] actively discourages it, and doing the process anyway leads to breakage.<ref>[https://blog.habets.se/2023/04/Linking-statically.html habets.se blog post about issues with glibc.]</ref> For more information, refer to the [[KISS Linux]] page. The C standard library difference is the only real difference between '''GKISS''' and regular '''KISS''', so all of the '''KISS''' guides can be used as normal. ea9632e4340a1bbc768c8ba93c42be455c23ca59 0 1051 5883 4282 2026-07-18T03:08:16Z PhantasNick 291 Stub wikitext text/x-wiki {{Stub}} [[Category:Linux Distributions]] {{DistributionInfobox | title = Solus | image = [[File:Solus.svg|Solus|300px]] | caption = The Solus logo | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = eopkg | defaultdesktops = Budgie, GNOME, KDE Plasma, Xfce | usagetype = Desktop | architectures = x86_64 | website = [https://getsol.us getsol.us] }} '''Solus''' is an independent rolling release [[Linux Distributions|Linux distribution]] that is designed for home computing. It uses the eopkg [[package manager]], which was forked from [[Pardus Linux]]'s PiSi package manager.<ref name="thelinuxrain">[https://www.thelinuxrain.org/articles/solus-impressive-most-impressive Solus - Impressive, Most Impressive], Andrew Powell, 2017 (Accessed: November 1, 2025).</ref> Solus is available in four desktop environments: its flagship [[Budgie]] desktop, as well as [[GNOME]], [[KDE Plasma]], and [[Xfce]] (formerly, [[MATE]] was available).<ref name="cyberpanel">[https://cyberpanel.net/blog/solus-linux Solus Linux: A Beginner-Friendly and Independent Linux Distribution], Marium Fahim, 2025 (Accessed: November 1, 2025).</ref> ==History== Solus was created by Ikey Doherty in 2015. Until then, it was known as Evolve OS during development.<ref>[https://www.slwoods.co.uk/?p=5880 Evolve OS changes name to Solus], Steve Woods, 2015 (Accessed: November 1, 2025).</ref> Prior to Solus, he created a [[Debian]]-based distribution called SolusOS.<ref name="thelinuxrain" /> In October 2025, Solus deprecated its "Shannon" software [[repository]] and replaced it with "Polaris", which allowed the Solus developers to remove [[Python]] version 2 and the deprecated Software Center application.<ref>[https://linuxiac.com/solus-begins-a-new-epoch-with-polaris-repository-and-python-2-removal/ Solus Begins a New Epoch with Polaris Repository and Python 2 Removal], Bobby Borisov, 2025 (Accessed: November 1, 2025).</ref> ==Software Management== There are two ways to manage software on Solus. The first is by using a graphical software manager such as [[Discover]] or [[GNOME Software]], and the second is by running <code>eopkg</code> in a terminal. Below is a list of commonly-used <code>eopkg</code> commands:<ref name="cyberpanel" /> {| class="wikitable" ! Command ! Purpose |- |<code>eopkg install <name></code> |Installs a package |- |<code>eopkg remove <name></code> |Removes a package |- |<code>eopkg search <keyword></code> |Searches for packages using the specified keyword |- |<code>eopkg upgrade</code> |Updates all of the packages in the system |} ==References== 59b038a6f2dc186cb86dd93f13c0c9594f20221b 0 1092 5884 5726 2026-07-18T03:09:09Z PhantasNick 291 added Stub and Citation Templates wikitext text/x-wiki {{Stub}} {{Needs Citations}} {{DistributionInfobox | title = Tinfoil Hat Linux | image = [[File:Tinfoillinux.jpg]] | caption = Tinfoil Hat Linux logo | releasestatus = Discontinued | releasemodel = None | packagemanager = None | defaultdesktops = Terminal only | usagetype = Security | architectures = i386 | website = tinfoilhat.shmoo.com }} '''Tinfoil Hat Linux''' ('''THL''') is a discontinued security-focused Linux distribution developed by the Shmoo Group. It was designed as a minimal, high-assurance operating system intended for cryptographic operations and protection against surveillance. == Overview == Tinfoil Hat Linux was released in 2002 as a compact, bootable operating system capable of running from a single floppy disk. It required minimal hardware resources, including an i386-compatible processor and as little as 8 MB of RAM. The system was designed to operate without a hard drive, allowing users to avoid persistent storage and reduce the risk of sensitive data leakage. Its minimal design also made it easier to audit for security purposes. == Security Features == Tinfoil Hat Linux used multiple security features to defend itself from surveillance including TEMPEST and keyloggers. Most of the security features in TFHL are now obsolete, as they are unmaintained and may hold numerous vulnerabilities. == List of Tinfoil Hat Linux methods against surveillance== * Encryption - GNU Privacy Guard (GPG) public key cryptography software is included in THL. * Data retrieval - all files are created on an encrypted RAM disk, all created files are destroyed after shutting down the computer. * Keystroke monitoring - THL has GPG Grid, a wrapper for GPG that lets you use a video game-style character entry system instead of typing in your passphrase. * Jamming TEMPEST signals - THL uses [[TEMPEST for eliza]] as TEMPEST jammer Together, these mechanism were intended to enhance operational security limiting data persistence and mitigating common surveillance techniques. 72605928731648a88d0939e7135af4ddc1216ba7 0 667 5885 5611 2026-07-18T12:03:59Z Imnotgoodatnames 121 added some links to some articles wikitext text/x-wiki {{Cleanup|Incomplete page, horribly out of date}} '''Unix''' is a family of multitasking, multi-user computer [[Operating_System|operating systems]] that derive from the original AT&T Unix, whose development started in 1969. Unix is recognised as the first portable operating system. Today UNIX isn't an operating system but rather a family of UNIX certified operating systems all following the Single UNIX Specification. Examples of modern UNIX-based systems include [[macOS]] and IBM AIX. The owner of the UNIX® trademark has been The Open Group since 1994.<ref>[https://unix.org/what_is_unix.html What is UNIX ®?]{{Dead Link|2026-05-26|404}} unix.org</ref> == History == === Origins === The history of UNIX begins in the mid-1960s when MIT, General Electric, and Bell labs were developing a new experimental operating system utilizing time-sharing called Multics, designed for the GE-645 mainframe computer. <ref>https://www.redhat.com/en/blog/unix-linux-history</ref> The project had many unique and beneficial new technologies, but also had severe problems. Bell labs pulled out of the project, citing its bloat and complexity. After being frustrated by Multics but inspired by its concepts, Ken Thompson and Dennis Ritchie wanted to build a much simpler, light operating system based on the rarely used DEC PDP-7 minicomputer. In the summer of 1969, Thompson wrote the initial kernel, shell, and editor, birthing "Unics" (more commonly known today as Unix.) Originally written in assembly, it was ported to [[C]] in 1973, making it highly portable and easily moved across vastly different architectures.<ref>https://www.nokia.com/bell-labs/about/history/innovation-stories/50-years-unix/</ref> === Branching === Because AT&T, the parent company of Bell Labs, was not allowed to enter the computer business due to antitrust laws, the operating system source code was licensed to universities for a nominal fee. With AT&T unable to support Unix, early Unix adopters worked together for assistance, forming a network of groups across the globe. In the mid-1970s, Ken Thompson temporarily left Bell labs and taught a course on Unix at the University of California. Students and teachers there further modified Unix, eventually creating a separate branch known as [[BSD]] (Berkeley Software Distribution). Back at AT&T, development continued, culminating in the 1983 release of a new release of Unix, Unix System V.<ref>https://www.britannica.com/technology/UNIX</ref> Throughout the 1980s, multiple major tech companies licensed Unix to run on their proprietary hardware, fracturing the market into various incompatible flavors, such as IBM's AIX, Sun Microsystem's SunOS (later known as Solaris), and HP's HP-UX. == References == 292ea1b2120af31dbcadf0e21d61d20a8a4ec55b 0 1381 5886 5848 2026-07-18T12:18:52Z Imnotgoodatnames 121 Added some references wikitext text/x-wiki [[File:Command_com.png|thumb|MS-DOS command prompt]] '''DOS''' is a family of MS-DOS compatible disk operating systems for the IBM PC and compatibles. The most popular operating systems in the category are Microsoft's '''IBM PC DOS''' and '''MS-DOS'''. All other DOS-es were designed to be compatible with MS-DOS but usually introduced new features as well. =PC DOS= {{SoftwareInfobox | title = '''IBM PC DOS''' | image = [[File:IBM_PC_DOS_7.0_logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | caption = IBM PC DOS logo | releasestatus = Discontinued | lastrelease = PC DOS 2000<ref>https://winworldpc.com/product/pc-dos/2000</ref> | languages = [[x86 Assembly]], [[C]] | developers = Microsoft, IBM | license = Proprietary | website = [https://web.archive.org/web/19990508201612/www.software.ibm.com/os/dos/dos2000/oem.html PC DOS 2000 for OEMs (archived 1999)] }} '''IBM PC DOS''' is the original DOS developed in 1981 by Microsoft for the IBM Personal Computer alongside Microsoft's MS-DOS, which was sold to the open market. It shared development with MS-DOS and the two systems were nearly identical until 1993, when Microsoft stopped developing it and IBM started introducing new features. =MS-DOS= {{SoftwareInfobox | title = '''MS-DOS''' | image = [[File:Msdos-icon.svg|frameless|upright=0.8]] | caption = MS-DOS icon in [[Windows]] | releasestatus = Discontinued | lastrelease = 6.22; 8.0 (As part of [[Windows]] ME)<ref>https://winworldpc.com/product/ms-dos/622</ref><ref>https://web.archive.org/web/20120109133113/http://www.microsoft.com/Presspass/press/2000/sept00/availabilitypr.mspx</ref> | languages = [[x86 Assembly]], [[C]]<ref>https://github.com/microsoft/MS-DOS</ref> | developers = Microsoft | license = Proprietary; 1.25, 2.11, 4.00: [[MIT_License|MIT]] | website = [https://web.archive.org/web/20170709153940/https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/windows_dos_overview.mspx MS-DOS overview (archived 2017)] }} '''MS-DOS''' (Microsoft DOS) is the version of Microsoft's DOS sold to OEMs other than IBM. It quickly became the most popular DOS system due to its use by most IBM compatible personal computers. From 1994 it ceased development as an independent operating system and from 1995 to 2000 was instead developed as the core part of the [[Windows]] 9x series. =FreeDOS= {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG<ref>https://opensource.com/article/21/6/freedos-package-manager</ref><ref>https://fdnpkg.sourceforge.net/</ref> | defaultdesktops = [[CLI|Command line interface]] | usagetype = Desktop | architectures = IA-16, i386<ref>https://github.com/FDOS/kernel/blob/d6791add2043c9d7b584d840a8ffaf8829fd2bdc/config.m#L57</ref> | website = [http://freedos.org freedos.org] }} FreeDOS is a [[FOSS|free]] DOS operating system developed since 1994, when Microsoft announced Windows would replace MS-DOS. It includes various advantages over MS-DOS such as kernel-level FAT-32 support, a network package manager and a CD release. == References == 12a472937c5605814ffad979f533718788c74c6a 3000 1387 5887 2026-07-19T11:08:19Z Lawl 419 make SSH signing page wikitext text/x-wiki You can use various cryptographic tools to sign Git commits and tags. This can help users of your projects confirm that ''you'' made that specific commit. This guide will walk you through setting up Git to sign your commits with SSH specifically. Prerequisites: * You must have an account on a Git service. * You must have an email added to said Git service, with the email in the SSH key matching that of the account's email. * You must have an SSH key, which is added to your Git account. If some of these are not met, Git may mark your commits or tags as "Unverified". == Configure Git to sign commits and tags with your SSH key == After you have created an SSH key, a Git account with a matching email, and added the SSH key to your Git account, you can now configure Git to use the key. Prerequisites: * Git 2.34.0 or later. * OpenSSH 8.1 or later. OpenSSH 8.7 will not work, if you are on 8.7 you must upgrade. * An SSH key with the Usage Type <code>Authentication & Signing</code> or just <code>Signing</code>. The following key types are widely supported: ** ED25519 ** ED25519_SK ** RSA ** ECDSA ** ECDSA_SK Now, we can configure Git to use your key: First. we must tell Git to use SSH to sign commits: <code>git config --global gpg.format ssh</code> Next, we need to specify which public SSH key to use as the signing key. This filename will differ depending on your setup. You can find the name of your public key by running: <code>ls ~/.ssh/</code> and then looking for file that ends with <code>.pub</code>. Now, to specify which key to use: <code>git config --global user.signingkey ~/.ssh/yourkey.pub</code> Your SSH key is now ready to sign your commits. To sign a commit, run: <code>git commit -S -m "Commit message"</code> If you don't want to include the <code>-S</code> every time, you can tell Git to sign commits automatically by running: <code>git config --global commit.gpgsign true</code> If your SSH key is protected by a passphrase, Git will prompt you to enter said passphrase. === Signing and verifying tags === Likewise with commits, you can also sign Git tags by adding the <code>-s</code> argument to your command. Example: <code>git tag -s v1.1.1 -m "Tag message"</code> Again, if you don't want to include the <code>-s</code> argument every time you push a tag, you can run: <code>git config --global tag.gpgsign true</code> And to verify tags, run: <code>git tag --verify v1.1.1</code> You can now sign and verify tags and commits securely. Congratulations! c9424175668571efff3ee13baf41bfd56f6e4d79 0 1388 5888 2026-07-20T04:33:49Z Hjrg 431 Added basic information wikitext text/x-wiki '''BIOS''' (Basic Input Ouput System) is a type of legacy firmware that performs hardware initialization during the booting process and the first software to run during boot. The BIOS is responsible for the POST (Power On Self Test). Typically the BIOS is placed in a chip that comes with the computer that is known as the ROM (Read-only memory). [[UEFI]] (Unified Extensible Firmware Interface) is the successor to the BIOS. === Accessing === The BIOS is typically accessed by pressing a certain key during boot, the key differs between manufacturers but the most common one is the '''DEL''' key or the '''F2''' key, but some manufacturers also use '''F1''', '''F10''' and other function keys Another way to reboot into BIOS is using [[Systemd]] via systemctl by doing: <syntaxhighlight lang="bash"> sudo systemctl reboot --firmware-setup </syntaxhighlight> 7b0cd01005f7318bc538bb86eb3d543c42b333f9 5889 5888 2026-07-20T04:35:20Z Hjrg 431 marked as stub wikitext text/x-wiki '''BIOS''' (Basic Input Ouput System) is a type of legacy firmware that performs hardware initialization during the booting process and the first software to run during boot. The BIOS is responsible for the POST (Power On Self Test). Typically the BIOS is placed in a chip that comes with the computer that is known as the ROM (Read-only memory). [[UEFI]] (Unified Extensible Firmware Interface) is the successor to the BIOS. === Accessing === The BIOS is typically accessed by pressing a certain key during boot, the key differs between manufacturers but the most common one is the '''DEL''' key or the '''F2''' key, but some manufacturers also use '''F1''', '''F10''' and other function keys Another way to reboot into BIOS is using [[Systemd]] via systemctl by doing: <syntaxhighlight lang="bash"> sudo systemctl reboot --firmware-setup </syntaxhighlight> [[Category:Stubs]] b60cd16246b108127d049c8ca20be387503ec4d5 5890 5889 2026-07-20T04:42:52Z Hjrg 431 Added stub template wikitext text/x-wiki {{Stub}} '''BIOS''' (Basic Input Ouput System) is a type of legacy firmware that performs hardware initialization during the booting process and the first software to run during boot. The BIOS is responsible for the POST (Power On Self Test). Typically the BIOS is placed in a chip that comes with the computer that is known as the ROM (Read-only memory). [[UEFI]] (Unified Extensible Firmware Interface) is the successor to the BIOS. === Accessing === The BIOS is typically accessed by pressing a certain key during boot, the key differs between manufacturers but the most common one is the '''DEL''' key or the '''F2''' key, but some manufacturers also use '''F1''', '''F10''' and other function keys Another way to reboot into BIOS is using [[Systemd]] via systemctl by doing: <syntaxhighlight lang="bash"> sudo systemctl reboot --firmware-setup </syntaxhighlight> [[Category:Stubs]] 171b3da4b0390f13ce248fdb54b21746918d00ce 6 1389 5891 2026-07-20T19:03:07Z Netcat 432 Snapcraft logo wikitext text/x-wiki == Summary == Snapcraft logo 7e25c3277c86555255404427ccbf1b15875c0884 0 1034 5892 5274 2026-07-20T19:08:37Z Netcat 432 Add snapcraft logo and update page info wikitext text/x-wiki [[Category:Software]] [[Category:Package_Managers]] {{SoftwareInfobox | title = Snap | releasestatus = Maintained | lastrelease = v2.76, 2026-06-19 | languages = Go, C | developers = Canonical Ltd. | website = [https://canonical.com/ canonical.com] | image = [[File:Snapcraft-logo.png]] | caption = The Snap logo }} '''Snap''' is a package management system aimed for desktops, cloud and IoT devices. The respective packages are termed as '''snaps''', which consist of an app bundled with its dependencies which works across [[Linux Distributions|Linux distributions]]<ref>[https://snapcraft.io/about About Snaps], Snapcraft, 2026-05-25 (Accessed: 2026-05-25)</ref>, similar to [[Flatpak|Flatpaks]]. Snapd is the background service that manages and maintains the installed snaps.<ref name=":0">[https://snapcraft.io/docs/installing-snapd Install the daemon], Snapcraft, 2026-01-13 (Accessed: 2026-05-25)</ref> The various snaps can be downloaded using the [https://snapcraft.io/store Snap Store]. One can build and publish snaps using [https://documentation.ubuntu.com/snapcraft/stable/ Snapcraft]. == Installation == Snapd needs to be running before a snap can be installed. It comes pre-installed with a few distributions by default such as [https://neon.kde.org/ KDE Neon], [[Manjaro]], [https://getsol.us/ Solus], [[Ubuntu]], Most [https://wiki.ubuntu.com/DerivativeTeam/Derivatives#Official_Ubuntu_Flavors Ubuntu Flavours] and [[ZorinOS]]. For distributions without Snapd pre-installed, one can refer to [https://snapcraft.io/docs/tutorials/install-the-daemon/#without-snap this section] of the official documentation and choose their respective documentation to install Snapd.<ref name=":0" /> After installing Snapd, one can head over to [https://snapcraft.io/store Snap Store] for searching and installing the software they want.<ref>[https://www.geeksforgeeks.org/linux-unix/snap-package-manager-on-ubuntu/ Snap Package Manager on Ubuntu], GeeksforGeeks, 2020-01-27 (Accessed: 2026-05-25)</ref> == References == <references /> e02f60fed129d14b804b60db6ae62e011fb6ced3 0 1335 5893 5754 2026-07-21T21:24:23Z Lawl 419 remove stub as this page is practically finished wikitext text/x-wiki SSH, also known as the '''Secure Shell Protocol''', is a cryptographic network protocol used to operate network services securely over an unsecured network.<ref>[https://www.rfc-editor.org/rfc/rfc4251 RFC 4251 - The Secure Shell (SSH) Protocol Architecture]</ref> It provides a secure channel over an unsecured network by using a client-server architecture, encrypting all traffic between the two parties to prevent many common attacks such as eavesdropping. SSH was introduced in 1995 to serve as a replacement for earlier, insecure remote-access protocols such as [[Telnet]] and the [[Berkeley r-commands]], which transmitted data, including authentication credentials, in unencrypted plaintext. SSH is commonly used for remote command-line login and remote command execution, but can also be used for file transfer and port forwarding. == Usage == SSH is used via a '''client''' application, which connects to an '''SSH server''' running on the remote machine you wish to connect to. The most widely used implementation of SSH is [[OpenSSH]], which is a derivative of the original free SSH 1.2.12 release from Tatu Ylönen<ref>[https://www.openssh.org/history.html OpenSSH project history]</ref>. It was developed to provide a free, open source alternative to the original SSH. It is now used in virtually any system, with the odd exception of embedded systems and routers, which instead use [[Dropbear]], a lighter alternative to [[OpenSSH]] based on the [[wikipedia:Secure_Shell#Version_2|SSH version 2 protocol]]. Dropbear was made specifically for embedded systems and other forms of computing where low memory usage is needed. Like OpenSSH, it is also free and open source software. There are many, many more SSH clients such as [[wolfSSH]] or GNU's [[lsh]]. It is recommended you just use OpenSSH or Dropbear, as other SSH clients are often less known, less documented, or have no general advantages or use case above the standard SSH clients. === Connecting to a remote host === The basic syntax for connecting with the SSH client is: ssh ''user''@'''host''' where <code>''user''</code> is the remote account to log in as, and <code>'''host'''</code> is the hostname or IP address of the server. To specify a non-default port, such as 2222: ssh -p 2222 ''user''@'''host''' On a successful connection, the user is dropped into a shell on the remote machine. There are many more command line arguments, and extra setup instructions needed to connect to a remote server. If you need help with something not listed here, see the official [https://man.openbsd.org/ssh OpenSSH man page]. === Setup === Setting up an SSH server involves installing and enabling an SSH daemon such as OpenSSH's [[sshd]], and configuring authentication. It is '''strongly recommended''' that you harden the default SSH config before exposing a server to the Internet. See [[Guides:Best SSH Security Practices]] for a full guide, as this wiki entry will not cover that. == History == SSH was designed in 1995 by '''Tatu Ylönen''' after a password-sniffing attack on his university's network. This attack exposed the weaknesses of all of the existing remote access protocols. As a response to this, Ylönen released the first SSH version, now called '''SSH-1''', as freeware in July 1995.<ref>[https://www.ssh.com/academy/ssh/original-ssh-overview Ylönen's original announcement]{{Dead Link|2026-06-15|404}}</ref> Adoption of this new protocol was rapid, within a few months it was estimated there were over 20,000 users across 550 countries. Later, Ylönen founded '''SSH Communications Security''' to continue development of the protocol commercially. Over time, the SSH codebase became more and more restrictive in it's licensing, which led developers behind [[OpenBSD]] to fork the last freely licensed version of SSH (SSH 1.2.12) in 1999, creating [[OpenSSH]], which is now the most common and widely deployed SSH implementation in the world. Later on, SSH-1 was found to have numerous cryptographic weaknesses, leading to the design of a successor to SSH-1, the '''SSH-2''' protocol, developed by the '''IETF SECSH''' working group. SSH-2 was published as a collection of RFCs in 2006, most notably '''RFC 4251'''. SSH-2 is purposefully incompatible with SSH-1 due to it's security problems. '''SSH-1 is now considered obsolete,''' usage of it is strongly discouraged. Because of the general superiority of SSH-2 over SSH-1, numerous implementations have come out for it, such as [[lsh]] and [[Dropbear]]. == References == fc2779312a12f01c9eded719f47a91deb1b38f89 3 1390 5894 2026-07-22T02:23:07Z Technio 366 /* test */ new section wikitext text/x-wiki == test == test [[User:Technio|Technio]] ([[User talk:Technio|talk]]) 02:23, 22 July 2026 (UTC) a8573d90e67ed6e99fbcb528272a233382eb2000 6 1391 5895 2026-07-24T14:37:00Z Lawl 419 wikitext text/x-wiki A black box with four blue pains, each containing one letter from the word: "xplr". 4c67a548b29028aa0b00a17412853b241a6e5f7c 0 1392 5896 2026-07-24T14:38:02Z Lawl 419 make xplr page wikitext text/x-wiki [[Category:Software]] [[Category:File managers]] {{SoftwareInfobox | title = xplr | releasestatus = Maintained | lastrelease = 1.1.0 | languages = [[Rust]] | developers = Arijit Basu | website = https://xplr.dev | license = MIT | sourcecode = https://github.com/sayanarijit/xplr | image = [[File:Xplr.png|64px|thumb|center]] }} '''xplr''' is a minimal, fast, and hackable terminal-based ([[TUI]]) file manager. Its primary purpose is to provide the user with a flexible and interactive controller for the ever-growing list of command line utilities for file management. This essentially makes it an interactive frontend to the command line utilities for managing files you already know, such as <code>ls</code>, <code>mv</code>, <code>cp</code>, etc. '''xplr'''s primary selling point is configuration. It uses [[Lua]] as a scripting language, which are used to make plugins, hacks, and other configurations. There are many, many more features too, such as: * Embedded LuaJIT * A simple modal system based on mesage passing * Typesafe message passing * Customizable layouts * Virtual root keybindings aswell as many more. === Writing a basic plugin === Plugins use [[Lua]], meaning, if you can write code in [[Lua]], you can make '''xplr''' plugins. Any plugin should follow a basic structure similar to this: <console> . ├── README.md └── init.lua </console> The <code>init.lua</code> is obviously required for a plugin. The README is not, however is recommended, as that way users can know what your plugin actually does. In this <code>init.lua</code> file, we need to expose a <code>setup()</code> function, to allow users to setup the plugin. To keep this file sanitary, it is recommended to have this file initialize and pull in other [[Lua]] files, which contain the source code to your plugin. This keeps the <code>init.lua</code> file as small as possible. An example <code>init.lua</code> looks like this: <syntaxhighlight lang="lua"> local function setup(args) local xplr = xplr -- your code here end return { setup = setup } </syntaxhighlight> Alternatively, you could use the official '''xplr''' plugin template, which sets up most the directories for you. Now, you can write code in other <code>.lua</code> files, and have the <code>init.lua</code> initialize them. e147e000b0d1f13d89a0be1a324b3a1e09a46a83 0 1393 5897 2026-07-24T14:39:33Z Lawl 419 redirect wikitext text/x-wiki #redirect [[xplr]] cfe22bb309b6e1b0148960ff1cd048abab3a5090 0 1394 5898 2026-07-24T15:34:21Z Imnotgoodatnames 121 Created page, added Cygwin/X entry and references as well as a stub thing. wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Cygwin | image = [[File:Cygwin_logo.svg|frameless|upright=0.6]] | releasestatus = Maintained | lastrelease = Stable: 3.6.6-1<ref>{{Cite|url=https://cygwin.com/pipermail/cygwin-announce/2026-January/012771.html|title=cygwin 3.6.6-1|accessdate=24 July 2026|year=2026}}</ref> | languages = [[C]], [[C++]] | developers = Cygnus Solutions, Red Hat<ref>{{Cite|url=https://access.redhat.com/solutions/78783|title= Is Cygwin supported?|year=2024|accessdate=24 July 2026}}</ref> | website = https://cygwin.com | license = [[GPL|GPLv3]], [[GPL#GNU_Lesser_General_Public_License_(LGPL)|LGPLv3]] | sourcecode = https://cygwin.com/git/newlib-cygwin.git | firstrelease = 18 October 1995 }} '''Cygwin''' is a Unix-compatible environment for [[Windows|Microsoft Windows]]. It consists of a library that translates POSIX system calls to Windows ones, as well as a distribution of free software built on it. ==Cygwin/X== '''Cygwin/X''' is an implementation of the [[X11|X windowing system]] for Microsoft Windows, and a part of the Cygwin project. It allows X-based Cygwin or Cygwin-based software to run graphically on Windows == References == 3d60025a05d1ca7c6c48b9f1322d6d3121515fe6 5901 5898 2026-07-24T16:14:21Z Imnotgoodatnames 121 Changed X Window System link wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Cygwin | image = [[File:Cygwin_logo.svg|frameless|upright=0.6]] | releasestatus = Maintained | lastrelease = Stable: 3.6.6-1<ref>{{Cite|url=https://cygwin.com/pipermail/cygwin-announce/2026-January/012771.html|title=cygwin 3.6.6-1|accessdate=24 July 2026|year=2026}}</ref> | languages = [[C]], [[C++]] | developers = Cygnus Solutions, Red Hat<ref>{{Cite|url=https://access.redhat.com/solutions/78783|title= Is Cygwin supported?|year=2024|accessdate=24 July 2026}}</ref> | website = https://cygwin.com | license = [[GPL|GPLv3]], [[GPL#GNU_Lesser_General_Public_License_(LGPL)|LGPLv3]] | sourcecode = https://cygwin.com/git/newlib-cygwin.git | firstrelease = 18 October 1995 }} '''Cygwin''' is a Unix-compatible environment for [[Windows|Microsoft Windows]]. It consists of a library that translates POSIX system calls to Windows ones, as well as a distribution of free software built on it. ==Cygwin/X== '''Cygwin/X''' is an implementation of the [[X_Window_System|X windowing system]] for Microsoft Windows, and a part of the Cygwin project. It allows X-based Cygwin or Cygwin-based software to run graphically on Windows. == References == b583ff3b93b458e80a6cfdf210cf0b1cecfe69a0 0 1395 5899 2026-07-24T16:10:07Z Imnotgoodatnames 121 Created page, added stub thing, images, infobox wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = X Window System | image = [[File:X11.svg{{!}}class=skin-invert|frameless|upright=0.6]] | releasestatus = Maintained | firstrelease = 19 June 1984; 42 years ago | lastrelease = Stable: X11R7.7<ref>{{Cite|url=https://www.x.org/Releases/7.7/|title=7.7|year=2012|accessdate=24 July 2026}}</ref> | languages = [[C]] | developers = Project Athena, X.Org Foundation | website = https://x.org | license = [[MIT_License|MIT]] (X.Org; historical implementations varied) | sourcecode = https://gitlab.freedesktop.org/xorg }} [[File:Twm.png|thumb|An X11 desktop running the [[twm]] window manager]] The '''X Window System''' is a windowing system common on [[Unix-like]] operating systems. It provides a [[GUI|graphical user interface]], and functions as a server-client system where the server is the machine with the display, and the client is the program accessing the display, which may or may not be connected remotely. '''X''' reads and sets various characteristics of the display and manages drawing windows as requested by clients. X is usually paired with an [[X Window Manager]], which manages the size, position and decorations of windows. X has been on version 11 since 1987, which is why it's commonly referred to as "[[X11]]" The [[Xorg|X.Org]] Foundation has been the de facto leader of X since 2004. == References == 15588d8f8184b90d24074ccaa4a63415b510c350 0 765 5900 3088 2026-07-24T16:12:35Z Imnotgoodatnames 121 reworded, added link to X page wikitext text/x-wiki X11 is the final major release version of the [[X_Window_System|X display server]] released in 1987 for [[UNIX|Unix]] operating systems. X11 is currently maintained by the X.Org foundation with the free and open-source implementation, X.Org Server. b43138a5634e3e462a2fe68cb1a35bf7e866758e 0 306 5902 3853 2026-07-24T16:15:43Z Imnotgoodatnames 121 Change X link wikitext text/x-wiki [[Category:Terminology]] [[Category:Window Management Systems]] {{Work_In_Progress}} A window manager is a piece of system software for [[X_Window_System|X]] that controls the placement of windows within a [[GUI|Graphical User Interface (GUI)]]. It controls several features of the GUI, such as the borders, title bar, size, and the ability to resize the windows. It can be provided as a part of the [[Desktop Environments|desktop environment]], such as [[KWin|Kwin]] in [[KDE Plasma]], with features such as icons and toolbars and the ability to provide a more consistent GUI. Alternatively, it can be stand-alone (such as [[i3]]) to give the user the ability to create a more lightweight and customisable environment. There are 3 main types of window managers: [[Window Manager#Stacking (Floating) Window Managers|stacking/floating]] provide the traditional desktop experience such as [[XFWM]] in [[XFCE]], [[Window Manager#Tiling Window Managers|tiling]] where the apps 'tile' so none overlap often with minimal or no reliance on the mouse such as [[qtile]] and [[Window Manager#Dynamic Window Managers|dynamic]] which can switch between stacking and tiling window layouts such as dwm.  == Types of Window Manager == === Stacking/Floating Window Managers === Floating window managers are recognizable to most computer users. They feature windows that are "floating," being able to move them freely and overlap each other. Some popular examples are listed below. * Enlightenment * KWin * Muffin * Mutter * Xfwm === Tiling Window Managers === Tiling window managers automatically align and snap windows to take up as much screen-space as possible, unless configured otherwise. Some examples include: * [[BSPWM|bspwm]] * [[i3]] * [[herbstluftwm]] * [[Notion]] * [[Ratpoison]] * [[StumpWM]] * [[Cagebreak]] === Dynamic Window Managers === Dynamic window managers combine both tiling and floating functionalities, automatically adapting window layouts based on user interactions. Providing flexibility for different workflows. Popular examples include: * [[awesomeWM]] * [[dwm]] * qtile * [[river]] * [[xmonad]] * [[FrankenWM]] * [[LeftWM]] * [[spectrwm]] === Scrollable Window Managers === Scrollable window managers tile windows as if they are sheets of paper on an endless strip going to the right, allowing you to scroll through them. Opening a new window never causes existing ones to resize. Some examples include: * [[karousel]] 63b31f143141afbe9881f11d0baa2486ac65e341 0 736 5903 3801 2026-07-24T16:25:51Z Imnotgoodatnames 121 bolded first instance of 'ed' wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[category:software]] [[File:Ed1.png|thumb|Text editor ed]] '''ed''' is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html ed], The IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> ed was part of the original Unix operating system from 1969.<ref>[https://man.cat-v.org/unix-1st/1/ed ed(1)], Unix First Edition Manual Page, 1971-11-03 (Accessed: 2025-08-09)</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>[https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html Shell & Utilities: Detailed Toc], IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s <code>s/regexp/replacement/</code> command was inherited from ed.<ref>[https://www.gnu.org/software/ed/manual/ed_manual.html GNU 'ed' Manual], GNU, 1993-08-09 (Accessed: 2025-08-09)</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor vi, whose variants remain some of the most popular TUI text editors.<ref>[https://ex-vi.sourceforge.net/ex.html ex.1], 2005-03-24 (Accessed: 2025-08-09)</ref><ref>[https://ex-vi.sourceforge.net/vi.html vi.1], 2005-03-24 (Accessed: 2025-08-09)</ref> == References == e384da4a0dcbd5106dad6f1c075409b5ba263e90 0 1396 5904 2026-07-24T16:41:20Z Imnotgoodatnames 121 Created page, added images, stub thing, no citations yet sorry wikitext text/x-wiki {{Stub}} [[File:Edwind.png|thumb|[[XTerm]], a common example of a terminal emulator on Unix-like systems, running the CLI text editor [[ed]].]] A '''terminal emulator''' is a [[GUI|graphical]] program that emulates a terminal. It allows the user to interact with [[CLI|command line interface]] or [[TUI|text user interface]] software in a graphical environment. Due to their large quantity of command-line utilities, terminal emulators are most common on [[UNIX|UNIX-like]] operating systems, but can also be found on various other systems, such as [[Microsoft Windows]]. Even though a terminal emulator's primary purpose is to emulate a physical terminal, they usually have extra quality of life features such as tabs, mouse scrollback, [[multiplexing]] and mouse and clipboard integration with the graphical shell. [[File:Windows_Terminal_v1.0_1138x624.png|thumb|Windows Terminal with multiple tabs active, split into panes.]] 25b5a460fac344bc34a9c505bab1e24e8769207e 5906 5904 2026-07-25T13:13:20Z Imnotgoodatnames 121 Added table of some terminal emulators with refs. wikitext text/x-wiki {{Stub}} [[File:Edwind.png|thumb|[[XTerm]], a common example of a terminal emulator on Unix-like systems, running the CLI text editor [[ed]].]] A '''terminal emulator''' is a [[GUI|graphical]] program that emulates a terminal. It allows the user to interact with [[CLI|command line interface]] or [[TUI|text user interface]] software in a graphical environment. Due to their large quantity of command-line utilities, terminal emulators are most common on [[UNIX|UNIX-like]] operating systems, but can also be found on various other systems, such as [[Microsoft Windows]]. Even though a terminal emulator's primary purpose is to emulate a physical terminal, they usually have extra quality of life features such as tabs, mouse scrollback, [[multiplexing]] and mouse and clipboard integration with the graphical shell. [[File:Windows_Terminal_v1.0_1138x624.png|thumb|Windows Terminal with multiple tabs active, split into panes.]] == List of terminal emulators == {| class="wikitable" |+ !Terminal emulator !Description |- |[[XTerm]] |The standard [[X_Window_System|X]] terminal emulator.<ref>[https://invisible-island.net/xterm/ XTerm] (Accessed: 2026-07-25)</ref> |- |[[Konsole]] |The terminal emulator of the [[KDE]] project.<ref>[https://apps.kde.org/en-gb/konsole/ Konsole] (Accessed: 2026-07-25)</ref> |- |[[LXTerminal]] |Terminal emulator of the [[LXDE]] desktop environment.<ref>[https://www.linuxlinks.com/lxterminal/ LXTerminal – terminal emulator of LXDE] (Accessed: 2026-07-25)</ref> |- |[[QTerminal]] |Terminal emulator developed by [[LXQt]].<ref>[https://github.com/lxqt/qterminal QTerminal] (Accessed: 2026-07-25)</ref> |- |[[st]] |Simple X terminal emulator developed by Suckless.<ref>[https://st.suckless.org st] (Accessed: 2026-07-25)</ref> |- |[[GNOME Terminal]] |The terminal emulator of the [[GNOME]] desktop environment.<ref>[https://help.gnome.org/gnome-terminal/introduction.html Terminal - introduction] (Accessed: 2026-07-25)</ref> |- |[[Terminal.app]] |Apple's proprietary terminal emulator for [[macOS]].<ref>[https://support.apple.com/en-gb/guide/terminal/trmld4c92d55/mac What is Terminal on Mac?] (Accessed: 2026-07-25)</ref> |- |[[Windows Terminal]] |Feature-rich terminal emulator developed by Microsoft for [[Windows]].<ref>[https://aka.ms/terminal Windows Terminal] (Accessed: 2026-07-25)</ref> |- |[[Termux]] |Terminal emulator app for [[Android]] that comes bundled with a software distribution of the same name.<ref>[https://termux.dev Terminal] (Accessed: 2026-07-25)</ref> |- |[[kitty]] |GPU-accelerated terminal emulator with a graphics protocol for displaying images.<ref>[https://https://sw.kovidgoyal.net/kitty/ kitty] (Accessed: 2026-07-25)</ref> |- |[[Ghostty]] |GPU-accelerated cross-platform terminal emulator.<ref>[https://https://https://ghostty.org/ Ghostty] (Accessed: 2026-07-25)</ref> |} eda7f7c0fe1ff462f651321bbbbcdf50c8d710a4 5908 5906 2026-07-25T13:20:55Z Imnotgoodatnames 121 add references thing wikitext text/x-wiki {{Stub}} [[File:Edwind.png|thumb|[[XTerm]], a common example of a terminal emulator on Unix-like systems, running the CLI text editor [[ed]].]] A '''terminal emulator''' is a [[GUI|graphical]] program that emulates a terminal. It allows the user to interact with [[CLI|command line interface]] or [[TUI|text user interface]] software in a graphical environment. Due to their large quantity of command-line utilities, terminal emulators are most common on [[UNIX|UNIX-like]] operating systems, but can also be found on various other systems, such as [[Microsoft Windows]]. Even though a terminal emulator's primary purpose is to emulate a physical terminal, they usually have extra quality of life features such as tabs, mouse scrollback, [[multiplexing]] and mouse and clipboard integration with the graphical shell. [[File:Windows_Terminal_v1.0_1138x624.png|thumb|Windows Terminal with multiple tabs active, split into panes.]] == List of terminal emulators == {| class="wikitable" |+ !Terminal emulator !Description |- |[[XTerm]] |The standard [[X_Window_System|X]] terminal emulator.<ref>[https://invisible-island.net/xterm/ XTerm] (Accessed: 2026-07-25)</ref> |- |[[Konsole]] |The terminal emulator of the [[KDE]] project.<ref>[https://apps.kde.org/en-gb/konsole/ Konsole] (Accessed: 2026-07-25)</ref> |- |[[LXTerminal]] |Terminal emulator of the [[LXDE]] desktop environment.<ref>[https://www.linuxlinks.com/lxterminal/ LXTerminal – terminal emulator of LXDE] (Accessed: 2026-07-25)</ref> |- |[[QTerminal]] |Terminal emulator developed by [[LXQt]].<ref>[https://github.com/lxqt/qterminal QTerminal] (Accessed: 2026-07-25)</ref> |- |[[st]] |Simple X terminal emulator developed by Suckless.<ref>[https://st.suckless.org st] (Accessed: 2026-07-25)</ref> |- |[[GNOME Terminal]] |The terminal emulator of the [[GNOME]] desktop environment.<ref>[https://help.gnome.org/gnome-terminal/introduction.html Terminal - introduction] (Accessed: 2026-07-25)</ref> |- |[[Terminal.app]] |Apple's proprietary terminal emulator for [[macOS]].<ref>[https://support.apple.com/en-gb/guide/terminal/trmld4c92d55/mac What is Terminal on Mac?] (Accessed: 2026-07-25)</ref> |- |[[Windows Terminal]] |Feature-rich terminal emulator developed by Microsoft for [[Windows]].<ref>[https://aka.ms/terminal Windows Terminal] (Accessed: 2026-07-25)</ref> |- |[[Termux]] |Terminal emulator app for [[Android]] that comes bundled with a software distribution of the same name.<ref>[https://termux.dev Terminal] (Accessed: 2026-07-25)</ref> |- |[[kitty]] |GPU-accelerated terminal emulator with a graphics protocol for displaying images.<ref>[https://https://sw.kovidgoyal.net/kitty/ kitty] (Accessed: 2026-07-25)</ref> |- |[[Ghostty]] |GPU-accelerated cross-platform terminal emulator.<ref>[https://https://https://ghostty.org/ Ghostty] (Accessed: 2026-07-25)</ref> |} == References == 0ae98f5fb00abde7f2a544b5d24d981ad3a4d735 0 1243 5905 5741 2026-07-24T16:43:50Z Imnotgoodatnames 121 fix links to CLI and GUI wikitext text/x-wiki {{Work In Progress|Author Name=Yoshikage Kira}} A shell is a software layer that acts as a wrapper around the core of the operating system ([[Kernel]]). It provides access to kernel features by translating human-readable commands or graphical inputs into system calls that the kernel can execute, then returning the output to the user. There are two main types of shells: [[CLI|Command-line interface]] (CLI) based shells and [[GUI|Graphical user interface]] (GUI) based shells. [[File:COSMIC Epoch 1.0.0 alpha with apps.png|alt=A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.|thumb|444x444px|A graphical desktop environment featuring a file manager, terminal emulator, system setting, and text editor. All these software allow user to interact and use kernel features in an intuitive and easy to use manner.]] [[File:Xterm.png|alt=A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.|thumb|444x444px|A terminal emulator displaying a command-line interface (CLI), where users interact with the operating system using text-based commands.]] One of the ways to interact with a CLI shell is via a [[Terminal emulator]], where a user enters commands one at a time. The shell then interprets and processes each command, returning any output or errors directly to the terminal. Conversely, the most common way people interact with a GUI shell is using a [[Desktop Environments|Desktop Environment]]. == Shell Capabilities == Below is a non-exhaustive overview of operating system features that a typical shell allows the user to access through its functionality. Some of these can only be accessed via CLI based shell but most these can be done both via CLI and GUI based shells. {| class="wikitable" !Core OS Feature !CLI Shell Functionality !GUI Shell Functionality |- !I/O Handling |Routes text data using redirection (<code>></code>, <code><</code>), pipelines (<code><nowiki>|</nowiki></code>), and built-ins like <code>read</code> or <code>mapfile</code> to capture input into variables/arrays. |Continuously captures mouse input and keyboard keystrokes to drive visual interfaces and active windows. |- !Process Management |Spawns, limits, and controls process states using <code>&</code>, <code>jobs</code>, <code>fg</code>, <code>bg</code>, <code>exec</code>, and resource constraints via <code>ulimit</code>. |Spawns and kills processes when apps are opened and closed via graphical app launchers or task managers. |- !Signal Handling |Transmits interrupt or termination signals directly via shortcuts (<code>Ctrl+C</code>) or commands (<code>kill</code>). |Triggers termination signals visually, like clicking the "X" close button or accepting a "Force Quit" prompt. |- !File System Navigation |Navigates directories using <code>cd</code>, <code>pwd</code>, <code>pushd</code>, and <code>popd</code>, with <code>*</code> (globbing) for path expansion. |Navigates and manages files and directories visually through a file manager (e.g., File Explorer, Finder). |- !Environment Management |Defines and propagates environment variables (like <code>PATH</code>) using <code>export</code> or startup scripts (<code>.profile</code>, <code>.bashrc</code>). |Modifies system configuration, system path, and user profile. through graphical apps such as settings panels. |- !Device Interaction |Reads from and writes directly to hardware devices using standard I/O redirection and device files. |Handles plug-and-play devices (e.g., mounting/ejecting flash drives) and manages peripherals via system settings. |} == Command Line Shells == // TODO: Explain command line, terminal emulators, command line interpreters, shell interpreters, and shell scripts {| class="wikitable" |- ! Shell !! Links !POSIX Compliance ! Description |- |[[Csh]] |[[wikipedia:C_shell|Wikipedia]] |No |The C Shell. Developed with an interactive command history and a syntax modeled closely after the C programming language. |- |[[Sh]] |[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html POSIX Standard Ch 02] |Yes |The original Bourne Shell. Established the foundational grammar for UNIX command interpreters and serves as the baseline reference for standard shell compliance. |- |[[Ksh]] |[http://kornshell.com Website] |Yes (compatible)<ref name=":0">These shells are capable of reading and running standard, universal POSIX scripts. However, they also include non-standard extensions (like Bash's arrays or double-bracket tests). If you write scripts using these extra features, they will work perfectly within that shell but will fail if you try to run them in a strict, pure POSIX environment.</ref> |The Korn Shell. Developed as an extension of the Bourne shell syntax, integrating interactive features from <code>csh</code> while establishing the scripting extensions that formed the basis of POSIX. |- |[[Bash]] || [https://www.gnu.org/software/bash/ Website] |Yes (compatible)<ref name=":0" />|| The "Bourne-Again Shell." An open-source, backwards-compatible replacement for <code>sh</code> created for the GNU project. Incorporates functional features from <code>ksh</code> and <code>csh</code>. |- |[[Zsh]] || [https://www.zsh.org/ Website] |Yes (compatible)<ref name=":0" />|| A highly customizable shell primarily based on the Korn shell (<code>ksh</code>) and the Bourne-syntax family. The default shell for macOS since 2019, it introduces massively upgraded interactive features like advanced menu-based auto-completion, spellcheck, and native recursive searching. |- |[[Fish]] |[https://fishshell.com/ Website] |No |Friendly Interactive Shell. Implements a custom, non-POSIX scripting syntax designed around automatic syntax highlighting and menu-driven command completion. |- |[[Elvish]] |[https://elv.sh/ Website] |No |A modern shell featuring an expressive, programming-language-like syntax, structured data support, and a built-in interactive file manager. |- |[[Xonsh]] || [https://xon.sh/ Website] |No | A Python based shell that features shared history across terminals and doubles as a superset of Python. |- |[[OSH]] |[https://oils.pub/osh.html Website] |Yes (compatible)<ref name=":0" /> |A Bash-compatible shell from the Oil project featuring precise error printouts and safer script execution. |- |[[Nushell]] |[https://www.nushell.sh/ Website] |No |A modern type of shell heavily inspired by PowerShell and functional programming. Rather than treating pipeline data as raw text, it passes structured data tables (objects with types) natively across commands. |- |[[YSH]] |[https://oils.pub/ysh.html Website] |No |A modern shell from the Oil project that acts as a bridge between traditional shell scripting, Python, YAML, and JSON. |- |[[OKsh]] |[https://github.com/ibara/oksh Github repository] |Yes |An unofficial port of OpenBSD's [[PDKsh]]. |- |[[PDKsh]] |None |Yes |OpenBSD's clone of [[Ksh]]. |- |[[Yash]] |[https://magicant.github.io/yash/ Website] |Yes |A shell focusing on being the most [[POSIX]] compliant shell in the world while focusing on usability. |} == Graphical Shells == // TODO: Explain Graphical shells, create a comparison table for Graphical shells like the shell table above == References == <references /> 7d9547e19c1d9b9abf624605d3a86c74d89a3053 0 291 5907 5631 2026-07-25T13:18:49Z Imnotgoodatnames 121 Fixed logo to look right on both light and dark theme wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Gnomelogo.svg{{!}}class=skin-invert|200px|GNOME_logo]] | caption = GNOME Logo | title = GNOME | releasestatus = Maintained | lastrelease = 50, 2026-03-18 | languages = C, C++, C#, Python, JavaScript, HTML among others | developers = GNOME Project | website = https://gnome.org/ }} [[Category:Desktop Environments]] [[File:GNOME 43.png|thumb|A desktop running GNOME 43]] '''GNOME''' is a modern, user-focused desktop environment known for its clean design, simplicity, and strong adherence to ''free software''<ref>[https://www.gnu.org/philosophy/free-sw.en.html What is Free Software?], GNU (Accessed: May 7, 2025)</ref> principles. It is the default [[Desktop Environments|desktop environment]] for prominent [[Linux Distributions|Linux distributions]] such as '''[[Fedora]]''', '''[[Ubuntu]]''', and '''[[Debian]]''', and remains a popular choice across the broader [[Linux]] and BSD ecosystems. GNOME used to be an acronym for "GNU Network Object Modeling Environment", but that is no longer the case; nowadays, GNOME stands for GNOME.<ref>[https://mail.gnome.org/archives/marketing-list/2010-April/msg00050.html |Re: GNOME -> Gnome], mail.gnome.org (Acessed: May 31, 2026)</ref> == History == GNOME was launched in 1997 by ''Miguel de Icaza'' and ''Federico Mena Quintero'' as a ''free software'' alternative to [[Plasma|KDE]], which at the time relied on the [[Qt]] toolkit, which at the time was not fully licensed under free software terms<ref>[[wikipedia:Qt_(software)#Early_developments|Early Developments of QT]], Wikipedia (Accessed: May 7, 2025)</ref>. GNOME aimed to provide a fully open-source desktop environment built using the [[GTK]] toolkit, originally developed for [[GIMP]]. ==== Timeline<ref>[[wikipedia:GNOME#History|History of GNOME]], Wikipedia (Accessed: May 7, 2025)</ref> ==== * '''GNOME 1.0''' was released in 1999. * '''GNOME 2 (2002–2011)''': Adopted a traditional desktop metaphor and panel-based interface. * '''GNOME 3 (2011)''': Introduced GNOME Shell, shifting to a more modern and streamlined user interface focused on productivity and simplicity. * '''GNOME 40+ (2021 onward)''': Marked a shift to a new versioning system and introduced horizontal workspace navigation, gesture support, and further visual and usability improvements. '''GNOME''' is developed by the '''GNOME Project''', a community-led initiative supported by the '''GNOME Foundation'''<ref>[https://foundation.gnome.org/ GNOME Foundation], GNOME Foundation, 2025-08-08 (Accessed: 2025-08-09)</ref>, a [https://wikipedia.org/wiki/Nonprofit_organization nonprofit] promoting software freedom and a user-focused design. == References == 090d5c50c27cf2303723780c3e40397fe3db9b22 0 1319 5909 5673 2026-07-25T13:34:27Z Imnotgoodatnames 121 This is a stub. wikitext text/x-wiki {{Needs_Citations}} {{Stub}} [https://p9f.org/about.html Plan 9 from Bell Labs] is a distributed [[operating system]] developed at [https://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in the late 1980s. It was designed by [https://en.wikipedia.org/wiki/Ken_Thompson Ken Thompson], [https://en.wikipedia.org/wiki/Rob_Pike Rob Pike], David Presotto, Phil Winterbottom, and others. In 2021, the system was transferred to the [https://p9f.org Plan 9 Foundation] and relicensed under the [[MIT License]]. b51ed3e82dcfdeb86126a0f151f996a9c1d234e1 0 1397 5910 2026-07-25T17:08:28Z Lawl 419 make nix page wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | title = Nix | releasestatus = Maintained | lastrelease = 2.35.1 | languages = [[C++]], [[Nix]] | developers = The Nix developers | website = https://nixos.org | license = GNU Lesser General Public License | sourcecode = https://github.com/NixOS/nix }} '''Nix''' is a cross-platform package manager for Unix-like systems and a functional language to configure said systems, invented in 2003<ref>[https://web.archive.org/web/20190421081837/https://nixos.org/~eelco/pubs/iscsd-scm11-final.pdf "Integrating Software Construction and Software Deployment - Eelco Dolstra"]</ref> by Eelco Dolstra.<ref>[https://en.wikipedia.org/wiki/Nix_(package_manager) Wikipedia entry on the Nix package manager]</ref> It powers the widely used [[NixOS]] operating system. == Philosophy == The Nix package manager uses a model in which it keeps every single package on the system separate, in a separate directory for each package. Each of these directories have a specific name which correspond to cryptographic hashes that take into account all dependencies of a package, including other packages managed by Nix. This results in isolated, reproducible packages, which, if they work on one system, they are guaranteed to work on another. This helps developers, by making errors easier to spot, and helps out users by providing them with a package that will 100% work on their computer. == Language == The Nix language is designed for conveniently creating and composing ''derivations'' - precise descriptions of how contents of existing files are used to derive new files. It is a domain-specific, purely functional, lazily evaluated, dynamically typed programming language.<ref>[https://nix.dev/tutorials/nix-language The Nix language basics]</ref> There are multiple projects that use said programming language, with the largest two being [[NixOS]] and the '''Nixpkgs''' package repository. == Nixpkgs == Nixpkgs is the package repository which is built on the Nix package manager. It contains over 122,000 packages<ref>[https://web.archive.org/web/20250115123328/https://repology.org/repository/nix_unstable nix_unstable repository info - Repology]</ref>, and is noted to have more up to date packages than any other package repository. It supports numerous operating systems, primarily [[Linux]] and [[Darwin]], with limited support for some [[BSD]] variants, and even some packages supporting [[Windows]]. == References == e7c64d1bd6ca06fcf73b050513f1de25ae91cf42 0 1226 5911 5203 2026-07-26T08:49:24Z Imnotgoodatnames 121 Add PCManFM, Prime, UnixTree, links to articles of graphical ones wikitext text/x-wiki [[Software]] file managers help browse, copy, move, and delete files, folders (directories), and more on your filesystem. == GUI file managers == {| class="wikitable" !Name !External links !Description |- |[[Dolphin]] |[https://apps.kde.org/dolphin/ KDE Applications] |Dolphin is [[KDE Plasma]]'s feature-rich file manager |- |[[Thunar]] |[https://docs.xfce.org/xfce/thunar/start Xfce] |Thunar is [[Xfce]]'s modern file manager, desgined from the group up for speed and friendliness. |- |[[PCManFM]] |[https://github.com/lxde/pcmanfm Github], [https://github.com/lxqt/pcmanfm-qt Github (PCManFM-Qt)] |File manager of [[LXDE]] and [[LXQt]] (PCManFM-Qt). |} == Terminal-based file managers == These file managers use a [[TUI]] and are useful for browsing, copying, moving, and deleting files from a terminal. {| class="wikitable" !Name !External links !Description |- |[[Midnight Commander]] |[https://midnight-commander.org/ Website], [https://github.com/MidnightCommander/mc GitHub] |Two-panel terminal-based file manager. |- |[[nnn]] |[https://github.com/jarun/nnn GitHub] |Fast and lightweight terminal-based file manager. |- |[[ranger]] |[https://ranger.fm/ Website], [https://github.com/ranger/ranger GitHub] |Terminal-based file manager with vi-style keybindings. |- |[[yazi]] |[https://yazi-rs.github.io/docs/installation/ Website], [https://github.com/sxyazi/yazi GitHub] |Terminal-based file manager written in Rust, based on asynchronous I/O. |- |[[ytree]] |[https://www.han.de/~werner/ytree.html Website], [https://github.com/robkam/ytree GitHub] |Terminal-based file manager in the XTree&trade; style. |- |[[GnuDOS#Prime|Prime]] |[https://www.gnu.org/software/gnudos/prime/index.html Manual], [https://github.com/dokakod/unixtree Github] |Terminal-based file manager with DOS-style keybinds, part of the [[GnuDOS]] project. |- |[[UnixTree]] |[https://www.unixtree.org Website] |Terminal-based file manager inspired by Xtree. |} f9cb101324ef01c8079243adce993377c79504c6 0 1398 5912 2026-07-26T12:41:24Z Imnotgoodatnames 121 Created page, added stub thing. citations and more stuff WiP. wikitext text/x-wiki {{Template:Needs Citations}} {{Stub}} {{SoftwareInfobox | title = GNUstep | caption = GNUstep logo | releasestatus = Maintained | developers = GNUstep developers, GNU Project | image = [[File:GNUstep logo.png|200px|GNUstep_logo]] | languages = [[Objective-C]] | lastrelease = Varied (GNUstep components often have independent releases) | website = [https://www.gnustep.org/ gnustep.org] }} '''GNUstep''' is a [[Free_and_Open_Source_Software|free]] implementation of Apple's [[Cocoa]] API and a collection of software based on that API. It is a part of the [[GNU]] project. Both GNUstep and Cocoa share the same NeXTSTEP roots. GNUstep supports many unique features such as special menu bar behaviour, which can be configured to act like NeXTSTEP's, [[Microsoft Windows]]' or even [[macOS]]' (with the menu bar of supported applications displayed as a small seperate window, as part of the application window or on top of the display, respectively). It can also manage windows and window decorations of any supported app, therefore technically bypassing the need for a seperate [[X_Window_Manager|window manager]], though non-GNUstep windows will remain unmanaged. GNUstep is cross platform and supports [[UNIX]] and Unix-like systems and Microsoft Windows. On Unix and Unix-like systems it runs primarily on [[X_Window_System|X]] with limited support for [[Wayland]]. [[Window Maker]] is the most common window manager used with GNUstep due to its limited integration with it and their shared default NeXTSTEP-inspired aesthetics. 5816d22791b663c9d432847d0052e800d43c2b4a 0 1399 5913 2026-07-26T12:43:11Z Hjrg 431 Created AppImage page wikitext text/x-wiki AppImage is an open source self-contained rootless distribution independent format for distributing software meant for portability and ease of use. ==== Using AppImage ==== An AppImage can be run by just downloading a .AppImage file and typing:<syntaxhighlight lang="bash"> chmod a+x example.AppImage </syntaxhighlight>in the terminal in order to make it runnable, after that it can be ran with:<syntaxhighlight lang="bash"> ./example.AppImage </syntaxhighlight> ==== Adding .desktop entries ==== In order to run an AppImage from a launcher menu such as [[Rofi]] a .desktop entry can be added, for example:<syntaxhighlight lang="desktop"> #!/usr/bin/env xdg-open [Desktop Entry] Type=Application Name=Helium Exec=/home/hjrg/Documents/Appimg/helium-0.11.3.2-x86_64.AppImage Icon=firefox Categories=Internet; Keywords=browser;helium; NoDisplay=false MimeType=x-scheme-handler/mailto;x-scheme-handler/unknown;x-scheme-handler/about;x-scheme-handler/https;x-scheme-handler/http;text/html; </syntaxhighlight>This code block shows an example of a .desktop file, in this case a .AppImage of the helium browser the required fields are type, name and exec. Exec - path where the file to be ran is located, Type=Application, Link or Directory and Name is self-explanatory. eb84eb4178205962ba890228c88c61833ce93a24 5915 5913 2026-07-26T12:50:21Z Hjrg 431 added logo wikitext text/x-wiki [[File:Logo3.svg|thumb|The AppImage logo]] AppImage is an open source self-contained rootless distribution independent format for distributing software meant for portability and ease of use. ==== Using AppImage ==== An AppImage can be run by just downloading a .AppImage file and typing:<syntaxhighlight lang="bash"> chmod a+x example.AppImage </syntaxhighlight>in the terminal in order to make it runnable, after that it can be ran with:<syntaxhighlight lang="bash"> ./example.AppImage </syntaxhighlight> ==== Adding .desktop entries ==== In order to run an AppImage from a launcher menu such as [[Rofi]] a .desktop entry can be added, for example:<syntaxhighlight lang="desktop"> #!/usr/bin/env xdg-open [Desktop Entry] Type=Application Name=Helium Exec=/home/hjrg/Documents/Appimg/helium-0.11.3.2-x86_64.AppImage Icon=firefox Categories=Internet; Keywords=browser;helium; NoDisplay=false MimeType=x-scheme-handler/mailto;x-scheme-handler/unknown;x-scheme-handler/about;x-scheme-handler/https;x-scheme-handler/http;text/html; </syntaxhighlight>This code block shows an example of a .desktop file, in this case a .AppImage of the helium browser the required fields are type, name and exec. Exec - path where the file to be ran is located, Type=Application, Link or Directory and Name is self-explanatory. 622ca7bf85b72be1e5c4a526f71f3e767244f8b4 5916 5915 2026-07-26T12:51:22Z Hjrg 431 Resize logo wikitext text/x-wiki [[File:Logo3.svg|thumb|The AppImage logo|450x450px]] AppImage is an open source self-contained rootless distribution independent format for distributing software meant for portability and ease of use. ==== Using AppImage ==== An AppImage can be run by just downloading a .AppImage file and typing:<syntaxhighlight lang="bash"> chmod a+x example.AppImage </syntaxhighlight>in the terminal in order to make it runnable, after that it can be ran with:<syntaxhighlight lang="bash"> ./example.AppImage </syntaxhighlight> ==== Adding .desktop entries ==== In order to run an AppImage from a launcher menu such as [[Rofi]] a .desktop entry can be added, for example:<syntaxhighlight lang="desktop"> #!/usr/bin/env xdg-open [Desktop Entry] Type=Application Name=Helium Exec=/home/hjrg/Documents/Appimg/helium-0.11.3.2-x86_64.AppImage Icon=firefox Categories=Internet; Keywords=browser;helium; NoDisplay=false MimeType=x-scheme-handler/mailto;x-scheme-handler/unknown;x-scheme-handler/about;x-scheme-handler/https;x-scheme-handler/http;text/html; </syntaxhighlight>This code block shows an example of a .desktop file, in this case a .AppImage of the helium browser the required fields are type, name and exec. Exec - path where the file to be ran is located, Type=Application, Link or Directory and Name is self-explanatory. b5eb611332ee4c203f8f4b82602ba532060838e7 5918 5916 2026-07-26T12:53:26Z Hjrg 431 logo fixed wikitext text/x-wiki [[File:App-image-logo.svg.png|thumb|550x550px|The AppImage logo]] AppImage is an open source self-contained rootless distribution independent format for distributing software meant for portability and ease of use. ==== Using AppImage ==== An AppImage can be run by just downloading a .AppImage file and typing:<syntaxhighlight lang="bash"> chmod a+x example.AppImage </syntaxhighlight>in the terminal in order to make it runnable, after that it can be ran with:<syntaxhighlight lang="bash"> ./example.AppImage </syntaxhighlight> ==== Adding .desktop entries ==== In order to run an AppImage from a launcher menu such as [[Rofi]] a .desktop entry can be added, for example:<syntaxhighlight lang="desktop"> #!/usr/bin/env xdg-open [Desktop Entry] Type=Application Name=Helium Exec=/home/hjrg/Documents/Appimg/helium-0.11.3.2-x86_64.AppImage Icon=firefox Categories=Internet; Keywords=browser;helium; NoDisplay=false MimeType=x-scheme-handler/mailto;x-scheme-handler/unknown;x-scheme-handler/about;x-scheme-handler/https;x-scheme-handler/http;text/html; </syntaxhighlight>This code block shows an example of a .desktop file, in this case a .AppImage of the helium browser the required fields are type, name and exec. Exec - path where the file to be ran is located, Type=Application, Link or Directory and Name is self-explanatory. 0575647fdf88854a7377cabcb5218b4eac934866 5919 5918 2026-07-26T12:53:46Z Hjrg 431 Logo fixed yet again wikitext text/x-wiki [[File:App-image-logo.svg.png|thumb|350x350px|The AppImage logo]] AppImage is an open source self-contained rootless distribution independent format for distributing software meant for portability and ease of use. ==== Using AppImage ==== An AppImage can be run by just downloading a .AppImage file and typing:<syntaxhighlight lang="bash"> chmod a+x example.AppImage </syntaxhighlight>in the terminal in order to make it runnable, after that it can be ran with:<syntaxhighlight lang="bash"> ./example.AppImage </syntaxhighlight> ==== Adding .desktop entries ==== In order to run an AppImage from a launcher menu such as [[Rofi]] a .desktop entry can be added, for example:<syntaxhighlight lang="desktop"> #!/usr/bin/env xdg-open [Desktop Entry] Type=Application Name=Helium Exec=/home/hjrg/Documents/Appimg/helium-0.11.3.2-x86_64.AppImage Icon=firefox Categories=Internet; Keywords=browser;helium; NoDisplay=false MimeType=x-scheme-handler/mailto;x-scheme-handler/unknown;x-scheme-handler/about;x-scheme-handler/https;x-scheme-handler/http;text/html; </syntaxhighlight>This code block shows an example of a .desktop file, in this case a .AppImage of the helium browser the required fields are type, name and exec. Exec - path where the file to be ran is located, Type=Application, Link or Directory and Name is self-explanatory. bf87a6c6a463339011db74d7582c173a71829b98 6 1400 5914 2026-07-26T12:48:35Z Hjrg 431 wikitext text/x-wiki The AppImage logo 7a21632c57faf4eab2cefbc2508c35c331636e4a 6 1401 5917 2026-07-26T12:52:51Z Hjrg 431 wikitext text/x-wiki AppImage Logo that depics a cog and download arrow 705c6faa2ed4bf5600b70adb5ff5cca124cdbd1b 0 1402 5920 2026-07-26T22:17:34Z Lawl 419 session page wikitext text/x-wiki {{Stub}} '''Session''' is a private, decentralized, and end-to-end encrypted ([[E2EE]]) messenger. It is fully open source, and is actively owned and developed by the Australian company, '''The Session Technology Foundation'''. It is best known for its high prioritization of user confidentiality and anonymity. == Features == Session employs numerous features which aid in securing and anonymizing the user's conversations and calls. It notably ''does not'' require a telephone number, and uses randomly generated, alphanumeric numbers for user identification. All communication is end to end encrypted, done so thanks to the independent Session protocol. This protocol is strong security wise, featuring '''Perfect Forward Secrecy''' and '''Post Quantum Cryptography'''. == Development == Session originally began as a fork of another private messenger, [[Signal]], aiming to build upon it. This continued for a while, until concerns arose regarding the potential metadata collection of the Signal Protocol and centralization. This led to them making a fully independent protocol for their messenger, The Session Protocol. However, this came with downsides, such as certain features which once came with the Signal protocol being abandoned. This includes perfect forward secrecy and deniability, which once was thought to be insignificant. However, as of 2026, the Session team has said they are working on building their own perfect forward secrecy, and deniability. 009d26f7562f68e88179b996d355f26ae2cf2fdd 0 1403 5921 2026-07-26T22:38:33Z Lawl 419 make some of webkit page wikitext text/x-wiki {{Stub}} '''WebKit''' is a browser engine, most notably adopted by Apple's [[Safari]] web browser. Aswell as [[Safari]], WebKit is also adopted in the Amazon kindle e-book reader, Nintendo consoles, [[GNOME Web]], and numerous other browsers.<ref>[https://en.wikipedia.org/wiki/WebKit Wikipedia's entry on WebKit]</ref> It began as a fork of the existing [[KHTML]] and [[KJS]] web libraries developed by the [[KDE]] foundation, and since then has been developed further by external foundations, notably Apple, Google, and others. It supports numerous operating systems, such as *nix based operating systems like [[Linux]], [[macOS]], [[Windows]], and others. == References == 09b898789c4a397d7eef2f244610403cc85aa3fc 0 1398 5922 5912 2026-07-27T15:27:48Z Imnotgoodatnames 121 Added screenshot, citations wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = GNUstep | caption = GNUstep logo | releasestatus = Maintained | developers = GNUstep developers, GNU Project | image = [[File:GNUstep logo.png{{!}}class=skin-invert|200px|GNUstep_logo]] | languages = [[Objective-C]] | lastrelease = Varied (GNUstep components often have independent releases)<ref>[https://github.com/gnustep GNUstep Github]</ref> | website = [https://www.gnustep.org/ gnustep.org] }} [[File:GNUstep_desktop.png|thumb|GNUstep desktop]] '''GNUstep''' is a [[Free_and_Open_Source_Software|free]] implementation of Apple's [[Cocoa]] API and a collection of software based on that API. It is a part of the [[GNU]] project. Both GNUstep and Cocoa share the same NeXTSTEP roots.<ref name="website">[https://gnustep.org GNUstep homepage]</ref> GNUstep supports many unique features such as special menu bar behaviour, which can be configured to act like NeXTSTEP's, [[Microsoft Windows]]' or even [[macOS]]' (with the menu bar of supported applications displayed as a small seperate window, as part of the application window or on top of the display, respectively). It can also manage windows and window decorations of any supported app, therefore technically bypassing the need for a seperate [[X_Window_Manager|window manager]], though non-GNUstep windows will remain unmanaged.<ref>[https://www.gnustep.org/resources/documentation/User/Gui/DefaultsSummary.html User Defaults Summary for GNUstep Libraries]</ref> GNUstep is cross platform and supports [[UNIX]] and Unix-like systems and Microsoft Windows. On Unix and Unix-like systems it runs primarily on [[X_Window_System|X]] with limited support for [[Wayland]].<ref>[https://home.gnustep.org/windows/installer.html Windows Installer]</ref><ref>[https://www.phoronix.com/news/GNUstep-0.29-With-Wayland GNUstep Releases Early Wayland Support, Many Other Improvements Too]</ref> [[Window Maker]] is the most common window manager used with GNUstep due to its limited integration with it and their shared default NeXTSTEP-inspired aesthetics.<ref>[https://mediawiki.gnustep.org/index.php/Window_Maker Window Maker]</ref> == References == 0f249158ecdc648d67f8f00e76f02cab4f5d3093 5923 5922 2026-07-27T15:30:03Z Imnotgoodatnames 121 Added more info to screenshot description wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = GNUstep | caption = GNUstep logo | releasestatus = Maintained | developers = GNUstep developers, GNU Project | image = [[File:GNUstep logo.png{{!}}class=skin-invert|200px|GNUstep_logo]] | languages = [[Objective-C]] | lastrelease = Varied (GNUstep components often have independent releases)<ref>[https://github.com/gnustep GNUstep Github]</ref> | website = [https://www.gnustep.org/ gnustep.org] }} [[File:GNUstep_desktop.png|thumb|GNUstep managing its own windows, with the Macintosh menu interface style.]] '''GNUstep''' is a [[Free_and_Open_Source_Software|free]] implementation of Apple's [[Cocoa]] API and a collection of software based on that API. It is a part of the [[GNU]] project. Both GNUstep and Cocoa share the same NeXTSTEP roots.<ref name="website">[https://gnustep.org GNUstep homepage]</ref> GNUstep supports many unique features such as special menu bar behaviour, which can be configured to act like NeXTSTEP's, [[Microsoft Windows]]' or even [[macOS]]' (with the menu bar of supported applications displayed as a small seperate window, as part of the application window or on top of the display, respectively). It can also manage windows and window decorations of any supported app, therefore technically bypassing the need for a seperate [[X_Window_Manager|window manager]], though non-GNUstep windows will remain unmanaged.<ref>[https://www.gnustep.org/resources/documentation/User/Gui/DefaultsSummary.html User Defaults Summary for GNUstep Libraries]</ref> GNUstep is cross platform and supports [[UNIX]] and Unix-like systems and Microsoft Windows. On Unix and Unix-like systems it runs primarily on [[X_Window_System|X]] with limited support for [[Wayland]].<ref>[https://home.gnustep.org/windows/installer.html Windows Installer]</ref><ref>[https://www.phoronix.com/news/GNUstep-0.29-With-Wayland GNUstep Releases Early Wayland Support, Many Other Improvements Too]</ref> [[Window Maker]] is the most common window manager used with GNUstep due to its limited integration with it and their shared default NeXTSTEP-inspired aesthetics.<ref>[https://mediawiki.gnustep.org/index.php/Window_Maker Window Maker]</ref> == References == 1c5c7ac0dfd245c27244e29359f72bb1f158b02b 5967 5923 2026-08-06T17:02:28Z Imnotgoodatnames 121 Added info about GNUstep applications wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = GNUstep | caption = GNUstep logo | releasestatus = Maintained | developers = GNUstep developers, GNU Project | image = [[File:GNUstep logo.png{{!}}class=skin-invert|200px|GNUstep_logo]] | languages = [[Objective-C]] | lastrelease = Varied (GNUstep components often have independent releases)<ref>[https://github.com/gnustep GNUstep Github]</ref> | website = [https://www.gnustep.org/ gnustep.org] }} [[File:GNUstep_desktop.png|thumb|GNUstep managing its own windows, with the Macintosh menu interface style.]] '''GNUstep''' is a [[Free_and_Open_Source_Software|free]] implementation of Apple's [[Cocoa]] API and a collection of software based on that API. It is a part of the [[GNU]] project. Both GNUstep and Cocoa share the same OpenStep roots.<ref name="website">[https://gnustep.org GNUstep homepage]</ref> GNUstep supports many unique features such as special menu bar behaviour, which can be configured to act like NeXTSTEP's, [[Microsoft Windows]]' or even [[macOS]]' (with the menu bar of supported applications displayed as a small seperate window, as part of the application window or on top of the display, respectively). It can also manage windows and window decorations of any supported app, therefore technically bypassing the need for a seperate [[X_Window_Manager|window manager]], though non-GNUstep windows will remain unmanaged.<ref>[https://www.gnustep.org/resources/documentation/User/Gui/DefaultsSummary.html User Defaults Summary for GNUstep Libraries]</ref> GNUstep is cross platform and supports [[UNIX]] and Unix-like systems and Microsoft Windows. On Unix and Unix-like systems it runs primarily on [[X_Window_System|X]] with limited support for [[Wayland]].<ref>[https://home.gnustep.org/windows/installer.html Windows Installer]</ref><ref>[https://www.phoronix.com/news/GNUstep-0.29-With-Wayland GNUstep Releases Early Wayland Support, Many Other Improvements Too]</ref> [[Window Maker]] is the most common window manager used with GNUstep due to its limited integration with it and their shared default NeXTSTEP-inspired aesthetics.<ref>[https://mediawiki.gnustep.org/index.php/Window_Maker Window Maker]</ref> == Applications == GNUstep '''applications''' are distributed in the form of portable application bundles. Like on macOS, they are regular directories with the '.app' suffix that contain the [[executable]] itself, the application icon and various metadata, such as the application version.<ref>[https://www.gnustep.org/resources/documentation/Developer/Base/Reference/NSBundle.html NSBundle class reference]</ref> == References == 616eae59369ed25d9f9ffeb89cf847d874f32254 0 827 5924 5669 2026-07-28T11:31:13Z Imnotgoodatnames 121 Slackware current has labwc wikitext text/x-wiki '''Wayland''' is a communication protocol that specifies the communication between a display server and its clients, as well as a [[C (programming language)|C]] library implementation of that protocol. A display server using the Wayland protocol is called a ''[[Wayland#Wayland compositors|Wayland compositor]]'', because it additionally performs the task of a compositing window manager. Wayland is developed by a group of volunteers initially led by Kristian Høgsberg as a free and open-source community-driven project with the aim of replacing the X Window System with a secure and simpler windowing system for [[Linux]] and other [[Unix]]-like operating systems. The project's source code is published under the terms of the [[MIT License]], a permissive free software license. The Wayland project also develops an implementation of a Wayland compositor called ''[[Wayland#Weston|Weston]]''. == Overview == [[File:Wayland_display_server_protocol.svg|right|thumb]] The Wayland Display Server project was started by [[Red Hat]] developer Kristian Høgsberg in 2008. Beginning around 2010, Linux desktop graphics have moved from having "a pile of rendering interfaces... all talking to the X server, which is at the center of the universe" towards putting the Linux kernel and its components (i.e. Direct Rendering Infrastructure (DRI), Direct Rendering Manager (DRM)) "in the middle", with "window systems like X and Wayland ... off in the corner". This will be "a much-simplified graphics system offering more flexibility and better performance". Høgsberg could have added an [[Xdmx|extension to X]] as many recent projects have done, but preferred to "[push] X out of the hotpath between clients and the hardware" for reasons explained in the project's FAQ. Wayland consists of a protocol and a reference implementation named [[Wayland#Weston|Weston]]. The project is also developing versions of [[GTK]] and [[Qt (software)|Qt]] that render to Wayland instead of to X. Most applications are expected to gain support for Wayland through one of these libraries without modification to the application. Initial versions of Wayland have not provided network transparency, though Høgsberg noted in 2010 that network transparency is possible. It was attempted as a Google Summer of Code project in 2011, but was not successful. Adam Jackson has envisioned providing remote access to a Wayland application by either "pixel-scraping" (like [[Virtual Network Computing|VNC]]) or getting it to send a "rendering command stream" across the network (as in [[Remote Desktop Protocol|RDP]], [[SPICE (protocol)|SPICE]] or [[X11]]). As of early 2013, Høgsberg was experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor. In August 2017, GNOME saw the first such pixel-scraping VNC server implementation under Wayland. In modern Wayland compositors, network transparency is handled in an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] that implements the RemoteDesktop portal. Many Wayland compositors also include an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] for common tasks such as a native file picker for native applications and sandboxes such as [[Flatpak]] ([https://github.com/flatpak/xdg-desktop-portal-gtk xdg-desktop-portal-gtk] is commonly used as a fallback filepicker), screen recording, network transparency, screenshots, color picking, and other tasks that could be seen as needing user intervention and being security risks otherwise. Note that xdg-desktop-portal is not Flatpak or Wayland-specific, and can be used with alternative packaging systems and windowing systems. == Wayland compositors == [[File:Window_(windowing_system).svg|right|thumb|Typical elements of a [[Window (computing)|window]]. The Wayland protocol does not specify what software is responsible for rendering the [[window decoration]].{{r|Graesslin 2013 decorations}}]] [[File:KDE_Plasma_5.24_on_Arch_Linux_screenshot.png|thumb|Plasma 5.24.0 (February 2022) on Wayland ({{code|kwin_wayland}} compositor) under [[Arch Linux]]]] [[Display server|Display servers]] that implement the Wayland display server protocol are also called ''Wayland compositors'' because they additionally perform the task of a [[compositing window manager]]. A library called '''wlroots''' is a modular Wayland implementation that functions as a base for several compositors A list of compositors can be found [[Wayland Compositors|here]]. === Weston === [[Weston (software)|Weston]] is a Wayland compositor previously developed as the [[reference implementation]] of the protocol by the Wayland project. It is written in [[C (programming language)|C]] and released under the [[MIT License]]. Weston officially supports only [[Linux]] due to dependencies on kernel-specific features such as kernel mode-setting (KMS), the Graphics Execution Manager (GEM), and [[udev]]. On Linux, it handles input via [[evdev]] and buffer management via Generic Buffer Management (GBM). A prototype port for [[FreeBSD]] was announced in 2013. The compositor supports High-bandwidth Digital Content Protection (HDCP) and uses GEM to share buffers between applications and the compositor. It features a plug-in architecture with "shells" that provide elements like docks and panels. Applications are responsible for rendering their own window decorations. Weston supports rendering via [[OpenGL ES]] or the [[pixman]] library for software rendering. The full OpenGL stack is avoided to prevent pulling in [[GLX]] and other [[X11|X Window System]] dependencies. A remote desktop interface for Weston was proposed in 2013 by a developer from [[RealVNC]]. ==== Maynard ==== [[File:Maynard_desktop.png|thumb|Maynard (in January 2017)]] '''''Maynard''''' is a [[graphical shell]] and has been written as a plug-in for Weston, just as the [[GNOME Shell]] has been written as a plug-in to [[Mutter (software)|Mutter]]. The [[Raspberry Pi Holdings|Raspberry Pi]] in collaboration with [[Collabora]] released Maynard. === libinput === [[File:Libinput_for_Wayland_compositors.svg|thumb|libinput was created to consolidate the input stack across multiple Wayland compositors.]] The Weston code for handling input devices (keyboards, pointers, touch screens, etc.) was split into its own separate library, called ''libinput'', for which support was first merged in Weston 1.5. Libinput handles input devices for multiple Wayland compositors and also provides a generic [[X.Org Server]] input driver. It aims to provide one implementation for multiple Wayland compositors with a common way to handle input events while minimizing the amount of custom input code compositors need to include. libinput provides device detection (via [[udev]]), device handling, input device event processing and abstraction. Version 1.0 of libinput followed version 0.21, and included support for tablets, button sets and touchpad gestures. This version will maintain stable API/ABI. As GNOME/GTK and [[KDE Frameworks 5]] have mainlined the required changes, Fedora 22 will replace X.Org's evdev and Synaptics drivers with libinput. With version 1.16, the [[X.Org Server]] obtained support for the libinput library in form of a wrapper called [[Mono]]. === Wayland Security Module === Wayland Security Module is a proposition that resembles the [[Linux Security Module]] interface found in the [[Linux kernel]]. Some applications (especially the ones related to [[accessibility]]) require privileged capabilities that should work across different Wayland compositors. Currently, applications under Wayland are generally unable to perform any sensitive tasks such as taking screenshots or injecting input events without going through [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] or obtaining privileged access to the system. Wayland Security Module is a way to delegate security decisions within the compositor to a centralized security decision engine. == Adoption == The Wayland protocol is designed to be simple so that additional protocols and interfaces need to be defined and implemented to achieve a holistic windowing system. While many graphical toolkits already fully support Wayland, the developers of the [[Graphical shell|graphical shells]] are cooperating with the Wayland developers to create the necessary additional interfaces. === Desktop Linux distributions === Most major Linux distributions default to using Wayland. Some notable examples are: * [[Debian]] ships Wayland as the default session for GNOME since version [[Debian 10|10 (Buster)]], released 6 July 2019. * [[Fedora]] starting with version 25 (released 22 November 2016) uses Wayland for the default GNOME 3.22 desktop session, with [[X.Org]] as a fallback if the graphics driver cannot support Wayland. Fedora uses Wayland as the default for KDE desktop session starting with version 34 (released 27 April 2021) * [[Manjaro]] ships Wayland as default in the Gnome edition of Manjaro 20.2 (Nibia) (released 22 November 2020). * [[Raspberry Pi OS]], a port of Debian, has offered the option to use Wayland since version [[Debian 11|11 (Bullseye)]], which was released on 3 December 2021. Wayland became the default in version [[Debian 12|12 (Bookworm)]], released on 10 October 2023. * [[Red Hat Enterprise Linux]] ships Wayland as the default session in version 8, released 7 May 2019. * [[Ubuntu]] shipped with Wayland by default in Ubuntu 17.10 (Artful Aardvark). However, Ubuntu 18.04 LTS reverted to X.Org by default due to several issues. Since Ubuntu 21.04, Wayland is the default again. * [[Slackware]] included Wayland on 20 February 2020 for the development version, -current, which became version 15.0 in 2022. Slackware 15.0 (released 2022) has Wayland although the only compositor/DE available in the repos is KDE Plasma with `startkwayland`. However, Wayland is still not the default. As of July 2026 Slackware -current also includes the [[Labwc]] compositor. == History == Kristian Høgsberg, a [[Linux]] graphics and [[X.Org]] developer who previously worked on [[AIGLX]] and [[Direct Rendering Infrastructure|DRI2]], started Wayland as a spare-time project in 2008 while working for [[Red Hat]]. His stated goal was a system in which "every frame is perfect, by which I mean that applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker." Høgsberg was driving through the town of Wayland, Massachusetts when the underlying concepts "crystallized", hence the name (Weston and Maynard are also nearby towns in the same area, continuing the reference). In October 2010, Wayland became a [[freedesktop.org]] project. As part of the migration, the prior Google Group was replaced by the ''wayland-devel'' mailing list as the project's central point of discussion and development. The Wayland client and server libraries were initially released under the [[MIT License]], while the reference compositor Weston and some example clients used the [[GNU General Public License]] version 2. Later, all the GPL code was relicensed under the MIT license "to make it easier to move code between the reference implementation and the actual libraries". In 2015 it was discovered that the license text used by Wayland was a slightly different and older version of the MIT license, and the license text was updated to the current version used by the [[X.Org]] project (known as [[Expat License|MIT Expat License]]). {| class="wikitable sortable collapsible text-align:center" |} 50016f8442dbdab5c7993e789af39e1849991a61 0 1404 5925 2026-07-28T15:18:15Z Imnotgoodatnames 121 Create redirect wikitext text/x-wiki #REDIRECT [[X_Window_System]] 19ef91a9570dd2d81cbf3cfb1cdf4cd0525c7944 0 1091 5926 5771 2026-07-28T18:04:36Z MysteryBirb 353 Moved Citation wikitext text/x-wiki {{Work In Progress}} {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.13.1, 2026-05-18 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io]{{Dead Link|2026-06-15|404}} | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref> == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> aafb87373bd1bcfd4f0938459dce8248708106cf 5927 5926 2026-07-28T18:05:01Z MysteryBirb 353 Removed WIP wikitext text/x-wiki {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.13.1, 2026-05-18 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io]{{Dead Link|2026-06-15|404}} | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref> == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 138d35ad049395dfcb49b9a1ebf469b0255d4564 5928 5927 2026-07-28T19:27:35Z Hjrg 431 added void linux install wikitext text/x-wiki {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.13.1, 2026-05-18 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io]{{Dead Link|2026-06-15|404}} | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWC. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref> == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> ==== [[Void Linux]] ==== <syntaxhighlight lang="bash"> sudo xbps-install mangowc </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 6e553a0e70e9a26b334aaf1c19971e4d097cf720 5929 5928 2026-07-28T19:56:01Z Uniolo 345 Fix the "Stability" section of "Features" referring to MangoWM as MangoWC (name was changed). wikitext text/x-wiki {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.13.1, 2026-05-18 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io]{{Dead Link|2026-06-15|404}} | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWM. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-05-23}}</ref> == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> ==== [[Void Linux]] ==== <syntaxhighlight lang="bash"> sudo xbps-install mangowc </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 002be10ea1df2e86817c4e06a9c93695d44c5525 5937 5929 2026-07-30T19:58:29Z MysteryBirb 353 Removed non existent deadlink, checked references wikitext text/x-wiki {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.13.1, 2026-05-18 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io] | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWM. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-07-30}}</ref> == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> ==== [[Void Linux]] ==== <syntaxhighlight lang="bash"> sudo xbps-install mangowc </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 8ae768ad3ed763ea3ad43b2b85c2d75c485dc372 5942 5937 2026-07-31T16:01:01Z MysteryBirb 353 Change Mango release version wikitext text/x-wiki {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.15.5, 2026-07-24 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io] | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} MangoWM (formerly known as MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWM. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-07-30}}</ref> == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> ==== [[Void Linux]] ==== <syntaxhighlight lang="bash"> sudo xbps-install mangowc </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> e8d097195def315f6f6d16e57618d06676b0b2f5 5943 5942 2026-07-31T17:32:59Z Netcat 432 Bold-ify article name wikitext text/x-wiki {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.15.5, 2026-07-24 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io] | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] }} '''MangoWM''' (formerly MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWM. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-07-30}}</ref> == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> ==== [[Void Linux]] ==== <syntaxhighlight lang="bash"> sudo xbps-install mangowc </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> cdc60d51145e87ae7ed9cfa660a227ca0ac65ed9 5944 5943 2026-07-31T17:38:07Z Netcat 432 Add license and source code link wikitext text/x-wiki {{Needs Citations}} {{Guide Warning}} {{SoftwareInfobox | caption = MangoWM logo | developers = MangoWM developers | firstrelease = 0.1.1, 2025-02-17 | languages = [[C]] | lastrelease = V0.15.5, 2026-07-24 | title = MangoWM | website = [https://mangowm.github.io/ mangowm.github.io] | releasestatus = Maintained | image = [[File:Mango-transparency-256.png|thumb|center]] | license = GNU GPLv3 | sourcecode = [https://github.com/mangowm/mango/ github.com/mangowm/mango] }} '''MangoWM''' (formerly MangoWC) is a [[Wayland]] compositor based on [[dwl]]. MangoWM extends [[dwl]] by adding support for multi-monitor setups, complex window layouts, and more [[Wayland]] protocols. == Features == * '''Stability''' - one of the core principles of MangoWM. After months of testing and development, the compositor is reliable enough for daily use, with only a few lingering GPU compatibility issues remaining. Breaking changes will be kept to a minimum. * '''No Feature Creep model''' - not all feature requests will be immediately implemented. For more niche requests they wait and see if It gains enough traction from the community. * '''Layouts''' - MangoWM isn't just a tiling Wayland compositor, it also supports scroller, master-stack, monocle, grid, deck, and more, with per-tag layouts. * '''Animations and Visual Effects''' - built-in blur, shadows, corner radius, and opacity effects due to the help of scenefx with the addition of smooth and customizable animations for opening, closing, moving windows and tag switching. * '''IPC Control''' - MangoWM allows for external control of the compositor with extra support for custom scripts and widgets. * '''XWayland Support''' - amazing compatibility for legacy X11 applications. * '''Tag System''' - MangoWM uses tags instead of workspaces which adds extra customization for each tag == Installation<ref>{{Cite|url=https://mangowm.github.io/docs/installation|title=Installation guide MangoWM|accessdate=2026-07-30}}</ref> == ==== [[AerynOS]] ==== <syntaxhighlight lang="bash"> sudo moss install mangowm </syntaxhighlight> ==== [[Arch Linux]] ==== MangoWM is on the [[Arch User Repository]]. Install it with an AUR helper: <syntaxhighlight lang="bash"> # Using yay yay -S mangowm # Stable yay -S mangowm-git # Latest git version # Using paru paru -S mangowm # Stable paru -S mangowm-git # Latest git version </syntaxhighlight> ==== [[Fedora]] ==== Add the terra repository: <syntaxhighlight lang="bash"> sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release </syntaxhighlight> Then install MangoWM with [[dnf]]: <syntaxhighlight lang="bash"> sudo dnf install mangowm </syntaxhighlight> ==== [[Gentoo]] ==== Add the GURU repository: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose eselect-repository eselect repository enable guru sudo emerge --sync guru </syntaxhighlight> Unmask these packages in package.accept_keywords: * gui-libs/scenefx * gui-wm/mangowm Lastly installing it: <syntaxhighlight lang="bash"> sudo emerge --ask --verbose gui-wm/mangowm </syntaxhighlight> ==== [[Guix System]] ==== Add mango channel to $HOME/.config/guix/channels.scm: <syntaxhighlight lang="bash">(cons (channel (name 'mangowm) (url "https://github.com/mangowm/mango.git") (branch "main")) %default-channels)</syntaxhighlight> Then install mango after running '''guix pull''' with: <syntaxhighlight lang="bash"> guix install mango </syntaxhighlight> Or alternatively add it to your system configuration using the mango module <syntaxhighlight lang="bash"> (use-modules (mangowm)) (packages (cons* mangowm-git ... ;; Other packages %base-packages)) </syntaxhighlight> ==== [[NixOS]] ==== MangoWM provides a Flake with a NixOS module. Add flake input: <syntaxhighlight lang="nixos"> # flake.nix { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; mangowm = { url = "github:mangowm/mango"; inputs.nixpkgs.follows = "nixpkgs"; }; # other inputs ... }; } </syntaxhighlight> Import the NixOS module: Firts option, import in configuration.nix: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) {inputs, ...}: { imports = [ inputs.mangowm.nixosModules.mango # .. other imports ... ]; # ... } </syntaxhighlight> Second option import it directly in flake: <syntaxhighlight lang="nixos"> # flake.nix { # ... outputs = { self, nixpkgs, mangowm, ...}@inputs: let inherit (nixpkgs) lib; # ... in { nixosConfigurations.YourHostName = lib.nixosSystem { modules = [ mangowm.nixosModules.mango # or inputs.mangowm.nixosModules.mango # other imports ... ]; }; } } </syntaxhighlight> Then enable the module: <syntaxhighlight lang="nixos"> # configuration.nix (or any other file that you import) { programs.mango.enable = true; } </syntaxhighlight> All available options for NixOS are stated in the official MangoWM guide. ==== [[PikaOS]] ==== <syntaxhighlight lang="bash"> pikman install mangowm </syntaxhighlight> ==== [[Void Linux]] ==== <syntaxhighlight lang="bash"> sudo xbps-install mangowc </syntaxhighlight> == Building from source == Steps to follow from the official guide: # Installing dependencies listed below # Building wlroots and scenefx from source # Building MangoWM from source ==== Dependencies ==== * wayland * wayland-protocols * libinput * libdrm * ibxkbcommon * pixman * libdisplay-info * libliftoff * hwdata * seatd * pcre2 * xorg-xwayland * libxcb ==== Building [[wlroots]] from source ==== Clone and install the specific version required (check wlroots README for latest version). <syntaxhighlight lang="bash"> git clone -b 0.19.3 https://gitlab.freedesktop.org/wlroots/wlroots.git cd wlroots meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> ==== Building scenefx from source ==== Clone and install the specific version required same as wlroots. <syntaxhighlight lang="bash"> git clone -b 0.4.1 https://github.com/wlrfx/scenefx.git cd scenefx meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> === Building MangoWM from source: === At last compile MangoWM from source with the same rules as mentioned above. <syntaxhighlight lang="bash"> git clone https://github.com/mangowm/mango.git cd mango meson build -Dprefix=/usr sudo ninja -C build install </syntaxhighlight> 0410832ea7f1fed3ba92ffa10f7a72b0ea902a71 0 1373 5930 5837 2026-07-29T09:28:28Z Imnotgoodatnames 121 Added Hurd logo wikitext text/x-wiki {{Stub}} <!-- distroinfobox, more info --> [[Category:Misc Operating Systems]] {{DistributionInfobox | architectures = i386, x86_64 | caption = The GNU Hurd logo | defaultdesktops = [[GNOME]], [[Xfce]], [[Window Maker]], [[Fluxbox]], [[IceWM]], [[Openbox]] | image = [[File:Hurd-logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | packagemanager = [[dpkg]]/[[apt]] ([[Debian GNU/Hurd]]), [[Guix]] | releasemodel = Rolling | releasestatus = Experimental | title = GNU/Hurd | usagetype = Research, Development | website = [https://www.gnu.org/software/hurd/ gnu.org/software/hurd] }} '''GNU/Hurd''' is an unofficial name for the [[GNU]] operating system running on the '''GNU Hurd''' kernel. GNU Hurd (also referred to as "The Hurd" on GNU's website) is the GNU project's replacement for the [[UNIX]] operating system kernel.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's official Hurd documentation]</ref> It is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's description of Hurd]</ref> Essentially, The Hurd consists of a set of protocols and server processes (also known as daemons) that run on the GNU [[Mach]] microkernel. This means it differentiates from the [[Linux]] kernel, which is [[monolithic]].<ref>[https://itsfoss.com/news/gnu-hurd-progress-report/ ItsFOSS news report on GNU/Hurd]</ref> It has been in development since 1990, by the [[GNU]] project.<ref>[https://en.wikipedia.org/wiki/GNU_Hurd The Wikipedia entry for GNU Hurd]</ref> === History === '''Richard Stallman''' founded the GNU project in September 1983 with a goal to create a free GNU operating system.<ref>[https://cs.stanford.edu/people/eroberts/courses/cs181/projects/2000-01/open-source/gnu.htm#:~:text=In%201983,%20the%20GNU%20Project,up%20by%20proprietary%20software%20vendors. The history of the GNU project]</ref> Initially, all the necessary components needed for kernel development were made. By 1989, the [[GPL]] came into being, and the only major missing component was the [[kernel]], hence why they added the GNU operating system to [[Linux]] until they had their own kernel.<ref>[https://www.gnu.org/gnu/linux-and-gnu.html "Linux and GNU" entry on GNU's website]</ref> After this, development on the Hurd started after an abandoned kernel attempt, based on the [[TRIX]] operating system.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd History: How it started]</ref> According to the initial architect and founder of Hurd, '''Thomas Bushnell''', one of their early plans was to adopt and build on the [[4.4BSD]]-Lite kernel.<ref>[https://web.archive.org/web/20230710085615/http://www.groklaw.net/article.php?story=20050727225542530 "The Daemon, the GNU and the Penguin"]</ref> Later on from this, Richard Stallman proposed the use of the [[Mach]] microkernel, however this was delayed due to concern on whether the [[Mach]] code would be released under a suitable license.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd's history]</ref> Up until now, the development of Hurd had been relatively fast. However, with the release of the free [[Linux]] kernel in 1991, development slowed heavily, but did not stop. GNU's [[userland]] components were quickly put together with the [[Linux]] kernel to create operating systems based on the [[Linux]] kernel ([[Linux distributions]]). === References === fe2f130e02dc8a4c2f25af28cf6da3f8068655b0 5941 5930 2026-07-31T11:05:48Z Imnotgoodatnames 121 Added aarch64 to platforms wikitext text/x-wiki {{Stub}} <!-- distroinfobox, more info --> [[Category:Misc Operating Systems]] {{DistributionInfobox | architectures = i386, x86_64, aarch64<ref>[https://www.osnews.com/story/139255/gnu-hurd-ported-to-aarch64-and-more-hurd-news/ GNU Hurd ported to aarch64 and more hurd news]</ref> | caption = The GNU Hurd logo | defaultdesktops = [[GNOME]], [[Xfce]], [[Window Maker]], [[Fluxbox]], [[IceWM]], [[Openbox]] | image = [[File:Hurd-logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | packagemanager = [[dpkg]]/[[apt]] ([[Debian GNU/Hurd]]), [[Guix]] | releasemodel = Rolling | releasestatus = Experimental | title = GNU/Hurd | usagetype = Research, Development | website = [https://www.gnu.org/software/hurd/ gnu.org/software/hurd] }} '''GNU/Hurd''' is an unofficial name for the [[GNU]] operating system running on the '''GNU Hurd''' kernel. GNU Hurd (also referred to as "The Hurd" on GNU's website) is the GNU project's replacement for the [[UNIX]] operating system kernel.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's official Hurd documentation]</ref> It is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's description of Hurd]</ref> Essentially, The Hurd consists of a set of protocols and server processes (also known as daemons) that run on the GNU [[Mach]] microkernel. This means it differentiates from the [[Linux]] kernel, which is [[monolithic]].<ref>[https://itsfoss.com/news/gnu-hurd-progress-report/ ItsFOSS news report on GNU/Hurd]</ref> It has been in development since 1990, by the [[GNU]] project.<ref>[https://en.wikipedia.org/wiki/GNU_Hurd The Wikipedia entry for GNU Hurd]</ref> === History === '''Richard Stallman''' founded the GNU project in September 1983 with a goal to create a free GNU operating system.<ref>[https://cs.stanford.edu/people/eroberts/courses/cs181/projects/2000-01/open-source/gnu.htm#:~:text=In%201983,%20the%20GNU%20Project,up%20by%20proprietary%20software%20vendors. The history of the GNU project]</ref> Initially, all the necessary components needed for kernel development were made. By 1989, the [[GPL]] came into being, and the only major missing component was the [[kernel]], hence why they added the GNU operating system to [[Linux]] until they had their own kernel.<ref>[https://www.gnu.org/gnu/linux-and-gnu.html "Linux and GNU" entry on GNU's website]</ref> After this, development on the Hurd started after an abandoned kernel attempt, based on the [[TRIX]] operating system.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd History: How it started]</ref> According to the initial architect and founder of Hurd, '''Thomas Bushnell''', one of their early plans was to adopt and build on the [[4.4BSD]]-Lite kernel.<ref>[https://web.archive.org/web/20230710085615/http://www.groklaw.net/article.php?story=20050727225542530 "The Daemon, the GNU and the Penguin"]</ref> Later on from this, Richard Stallman proposed the use of the [[Mach]] microkernel, however this was delayed due to concern on whether the [[Mach]] code would be released under a suitable license.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd's history]</ref> Up until now, the development of Hurd had been relatively fast. However, with the release of the free [[Linux]] kernel in 1991, development slowed heavily, but did not stop. GNU's [[userland]] components were quickly put together with the [[Linux]] kernel to create operating systems based on the [[Linux]] kernel ([[Linux distributions]]). === References === 4bedc8ac95dce88d99fa6f891305a294767aa3c1 0 239 5931 3704 2026-07-29T12:19:44Z Imnotgoodatnames 121 bump latest release wikitext text/x-wiki {{Needs_Citations}} {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 4.0.0, 2026-01-01 | languages = [[C++]], [[C]] | developers = Marko Maček, community contributors | website = [https://ice-wm.org/ ice-wm.org] }} [[Category:X_Window_Managers]] [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]] IceWM is a fast, simple and light X11 [[Window Management System|window manager]]. It has been developed from scratch since 1997 by Marko Maček in C++. By default, IceWM provides you with a taskbar and several tools, which allow your desktop to be as fast as possible. <references /> 6ae4409c562b59dc7674eb669f990c3b4d39e031 5932 5931 2026-07-29T17:10:54Z Imnotgoodatnames 121 Added more info, added citations, stub wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | image = [[File:IceWM Logo.png|IceWM_Logo]] | caption = IceWM logo | title = IceWM | releasestatus = Maintained | lastrelease = 4.0.0, 2026-01-01 | languages = [[C++]], [[C]] | developers = Marko Maček, community contributors | website = [https://ice-wm.org/ ice-wm.org] }} [[Category:X_Window_Managers]] [[File:Icewm-desktop.png|thumb|A screenshot of a configured IceWM desktop]] IceWM is a fast, simple and light [[X Window Manager|X11 window manager]]. It has been developed from scratch since 1997 by Marko Maček in C++.<ref name=website>[https://ice-wm.org IceWM website]</ref> IceWM includes many features uncommon for a standard window manager which are usually provided by external programs. By default, it provides a taskbar, menu bar, toolbar and several other tools, which allows the desktop to feel as fast as possible.<ref name=website></ref> IceWM places a large emphasis on customization and theming. Configuration files follow simple syntax, with plenty of preconfigured examples. It's configured by copying any file or directory the user wishes to modify from the /usr/share to $HOME/.icewm and modifying the new copy.<ref>[https://ice-wm.org/man/icewm icewm(1) | man]</ref> == References == d09507fa510944310634b6549f36a9bb8bf0dc72 0 1366 5933 5801 2026-07-29T19:01:03Z Imnotgoodatnames 121 Small touch-ups, changed wording, refs... wikitext text/x-wiki {{Stub}} '''Root''' is the default [[UNIX]] user with full control over the system. The root user is identified with a [[UID]] (user ID) of <code>0</code>. Any UID of <code>0</code> is automatically treated as the root user and is given unrestricted access to the system.<ref>[https://www.linfo.org/root.html What is root?], The Linux Information Project, May 29, 2005 (Accessed: 2026-29-07)</ref> When using most POSIX-compliant shells as the root user, the prompt will change form <code>$</code> to <code>#</code>.<ref>[https://www.man7.org/linux/man-pages/man1/bash.1.html#PROMPTING bash(1)], 2025 April 7 (accessed 2026-29-07)</ref> This warns you that you are running as the root user, and if you do something stupid, the system will let you be stupid and you might damage system-critical components. Please be careful when running with root privileges. == References == 2ce5d22dd465bdb4b12cdba40eb6c64b79cb292f 6 411 5934 1418 2026-07-29T20:10:01Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:CowsayOutput.png]] wikitext text/x-wiki minimum's terminal, cowsay program, "i love ATL!" 2630b76895d5b2573db89e1a6798fc2689e7a1e4 0 1394 5935 5901 2026-07-29T20:23:58Z Imnotgoodatnames 121 added some more refs wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Cygwin | image = [[File:Cygwin_logo.svg|frameless|upright=0.6]] | releasestatus = Maintained | lastrelease = Stable: 3.6.6-1<ref>{{Cite|url=https://cygwin.com/pipermail/cygwin-announce/2026-January/012771.html|title=cygwin 3.6.6-1|accessdate=24 July 2026|year=2026}}</ref> | languages = [[C]], [[C++]] | developers = Cygnus Solutions, Red Hat<ref>{{Cite|url=https://access.redhat.com/solutions/78783|title= Is Cygwin supported?|year=2024|accessdate=24 July 2026}}</ref> | website = https://cygwin.com | license = [[GPL|GPLv3]], [[GPL#GNU_Lesser_General_Public_License_(LGPL)|LGPLv3]] | sourcecode = https://cygwin.com/git/newlib-cygwin.git | firstrelease = 18 October 1995 }} '''Cygwin''' is a Unix-compatible environment for [[Windows|Microsoft Windows]]. It consists of a library that translates [[POSIX]] system calls to Windows ones, as well as a distribution of free software built on it.<ref>[https://cygwin.com/ Cygwin] (accessed 2026-07-29)</ref> ==Cygwin/X== '''Cygwin/X''' is an implementation of the [[X_Window_System|X windowing system]] for Microsoft Windows, and a part of the Cygwin project. It allows X-based Cygwin and Cygwin-based software to run graphically on Windows.<ref>[https://x.cygwin.com/ Cygwin/X] (accessed 2026-07-29)</ref> == References == 505db344df4735ae91e0b1c0a351857f44f7feaf 0 769 5936 5814 2026-07-30T19:55:29Z MysteryBirb 353 Removed deadlink from MangoWM wikitext text/x-wiki The choice of Wayland compositor is most comparable with choosing a window manager under [[X11]]. The Wayland compositor is in charge of rendering everything, routing input, configuring input/output devices as well as window management policy. The last one is what users are usually most interested in. A Wayland compositor alone does not constitute a full desktop environment, so further components are usually needed. For example, if you want any form of status bar, [[Waybar]] (or alternatives) are needed. ==Compositors Associated to a Desktop Environment== These Compositors are associated to a specific desktop environment. They are not meant to be used outside of their desktop environments. {| class="wikitable" ! Compositor !! Desktop Environment !! Window Managagement Paradigm !! Written In !! Notes |- | [[Mutter]]<ref>[https://gitlab.gnome.org/GNOME/mutter GNOME / mutter · GitLab], GNOME Foundation (Accessed: 2025-08-09)</ref> || [[GNOME]]|| Floating Window Management || [[C]] || The compositor of the GNOME desktop environment. Uses the Mutter library and Clutter toolkit. |- | [[KWin]]<ref>[https://github.com/KDE/kwin GitHub - KDE/kwin: Easy to use, but flexible, Wayland Compositor], KDE, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[KDE Plasma]] || Floating WIndow Management || [[C++]]|| KDE's compositor and window manager, with full Wayland support since Plasma 5. |- |[[Cosmic-comp]]<ref>[https://github.com/pop-os/cosmic-comp cosmic-comp github repo], pop-os team et al., 2025 (Accessed: 2026-05-25)</ref> |[[COSMIC]] | Floating or Stacking Window Management |[[Rust]] |A Wayland-only compositor that relies on the Iced rust Toolkit for its apps |- |} ==Floating Compositors== These compositors have what is often referred to as floating or stacking window management. This is same model you see on gnome and KDE where windows move around freely and are allowed to overlap each other. {| class="wikitable" ! Compositor !! Written In !! Notes |- | [[Weston]]<ref>[https://gitlab.freedesktop.org/wayland/weston wayland / weston · GitLab] (Accessed: 2025-08-09)</ref> || [[C]]|| Reference compositor developed by the Wayland project. Lightweight and primarily used for development and testing. Not suitable for daily use |- | [[wayfire]]<ref>[https://github.com/WayfireWM/wayfire GitHub - WayfireWM/wayfire: A modular and extensible wayland compositor], WayfireWM, 2025-08-09 (Accessed: 2025-08-09)</ref> || [[C++]] || Plugin-based compositor with Compiz-like 3D desktop effects. |- |[[labwc]]<ref>[https://labwc.github.io/ labwc], labwc, 2025-08-09 (Accessed: 2025-08-10)</ref> |[[C]] |A Stacking/Floating Wayland compositor inspired by Openbox. |- |} ==Tiling Compositors== These compositors perform what is referred to as tiling window management. Windows usually don't overlap and are automatically positioned to take up screen space. These often favour more advanced usage of virtual desktop or tags as well as a more keyboard-driven workflow. {| class="wikitable" ! Compositor !! Written In !! Notes |- | [[MangoWM]]<ref>[https://mangowm.github.io/ MangoWM Homepage] (Accessed: 2026-07-30)</ref>|| [[C]] || Extremely customizable & performant Wayland compositor built on top of [[dwl]]. |- | [[Sway]] || [[C]] || i3-compatible tiling Wayland compositor. Popular among users who prefer minimal setups. |- | [[Hyprland]] || [[C++]] || A modern and actively developed compositor featuring dynamic tiling, animations, and Wayland-exclusive features. |- | [[Niri]] || [[Rust]]|| A scrollable-tiling Wayland compositor inspired by PaperWM, a GNOME extension. |- | [[dwl]]<ref>[https://codeberg.org/dwl/dwl Codeberg - dwm for Wayland], dwl, 2025-04-12 (Accessed: 2025-08-10)</ref> || [[C]] || dwl - [[DWM|dwm]] for Wayland |- |} == Other Compsitors == These compositors don't fit neatly into any of the above paradigms. {| class="wikitable" ! Compositor !! Written In !! Notes |- | [[river]]<ref>[https://codeberg.org/river/river Codeberg - A non-monolithic Wayland compositor] river, (Accessed: 2026-05-30)</ref> || [[zig]]|| A non-monolithic wayland compositor where window management is performed by an external program. |- | [[Cage]]<ref>[https://github.com/cage-kiosk/cage GitHub - cage-kiosk/cage: A Wayland kiosk], cage-kiosk, 2018-08-09 (Accessed: 2025-08-09)</ref> || [[C]] || A simple Wayland compositor for single-application or kiosk environments. |- |} ==References== <references /> cf3de23801ac9f1cd9cf371743c8ce4fac44ad68 6 1405 5938 2026-07-31T01:16:31Z Maulie5 406 Logo of the Nushell project wikitext text/x-wiki == Summary == Logo of the Nushell project == Licensing == {{Unknown_copyright}} ac767976e3371a2b80623277a8e7fad64fe60b39 1 1323 5939 5689 2026-07-31T07:48:55Z Imnotgoodatnames 121 /* apt cow probably isn't Larry */ new section wikitext text/x-wiki == literally me == like fr [[User:Larry the cow|Larry the cow]] ([[User talk:Larry the cow|talk]]) 00:58, 10 June 2026 (UTC) what are we doing with our lives? == apt cow probably isn't Larry == I couldn't find any info anywhere that the apt cow is Larry. It also doesn't look like larry at all. I don't think it's Larry. [[User:Imnotgoodatnames|Imnotgoodatnames]] ([[User talk:Imnotgoodatnames|talk]]) 07:48, 31 July 2026 (UTC) 92f6869da2c58541971abd7e88cac83e5a3dfb77 5940 5939 2026-07-31T07:53:11Z Imnotgoodatnames 121 /* apt cow probably isn't Larry */ Reply wikitext text/x-wiki == literally me == like fr [[User:Larry the cow|Larry the cow]] ([[User talk:Larry the cow|talk]]) 00:58, 10 June 2026 (UTC) what are we doing with our lives? == apt cow probably isn't Larry == I couldn't find any info anywhere that the apt cow is Larry. It also doesn't look like larry at all. I don't think it's Larry. [[User:Imnotgoodatnames|Imnotgoodatnames]] ([[User talk:Imnotgoodatnames|talk]]) 07:48, 31 July 2026 (UTC) :Actually, do we even know if it's really a cow? It could be a bison or an ox or something. [[User:Imnotgoodatnames|Imnotgoodatnames]] ([[User talk:Imnotgoodatnames|talk]]) 07:53, 31 July 2026 (UTC) 1969f45ef062c8e30c8733d4c37a5bffdb16e1ba 0 1406 5945 2026-07-31T18:20:59Z Imnotgoodatnames 121 Created page, added stub thing. citations, misc OS category &c. wikitext text/x-wiki {{Stub}} {{Category:Misc_Operating_Systems}} {{DistributionInfobox | title = UnixWare | image = [[File:UnixWare_7_logo.svg|250px|center]] | caption = UnixWare 7 logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[RPM]]<ref name=skunkware>[https://skunkware.dev/ Skunkware]</ref> | defaultdesktops = [[CDE]] | usagetype = Desktop, Server | architectures = x86 | website = [https://www.xinuos.com/products/unixware-7/ xinuos.com/products/unixware-7] }} '''UnixWare''' is a [[proprietary software|proprietary]] [[UNIX]] system for x86 machines based on [[UNIX System V]]. Originally developed by Univel in 1992, it then passed to Novell, Santa Cruz Operation, Caldera, The SCO Group before being sold to Xinuos. Is is only available as a 32-bit x86 operating system.<ref>[http://www.faqs.org/faqs/unix-faq/unixware/general/ UnixWare Frequently Asked Questions (General)]</ref> As of july 2026, UnixWare 7 2018 is the latest release of UnixWare.<ref>[https://www.xinuos.com/wp-content/uploads/UnixWare7D2M1b-ReleaseNotesSupplement-220305.pdf SCO UnixWare 7 Definitive 2018 - Release Notes Supplement]</ref> == Skunkware == '''SCO Skunkware''' is a collection of [[Free_and_Open_Source_Software|open source software]] packages ported and built for SCO operating systems. Examples of open source software used on UnixWare include [[OpenSSH]], the RPM package manager, [[vim]] and various Mozilla software.<ref name=skunkware></ref> == References == a45c0a09d40dfcf986323157b4ff4c1fe03067d6 5946 5945 2026-07-31T18:21:58Z Imnotgoodatnames 121 Fixed category wikitext text/x-wiki {{Stub}} [[Category:Misc_Operating_Systems]] {{DistributionInfobox | title = UnixWare | image = [[File:UnixWare_7_logo.svg|250px|center]] | caption = UnixWare 7 logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[RPM]]<ref name=skunkware>[https://skunkware.dev/ Skunkware]</ref> | defaultdesktops = [[CDE]] | usagetype = Desktop, Server | architectures = x86 | website = [https://www.xinuos.com/products/unixware-7/ xinuos.com/products/unixware-7] }} '''UnixWare''' is a [[proprietary software|proprietary]] [[UNIX]] system for x86 machines based on [[UNIX System V]]. Originally developed by Univel in 1992, it then passed to Novell, Santa Cruz Operation, Caldera, The SCO Group before being sold to Xinuos. Is is only available as a 32-bit x86 operating system.<ref>[http://www.faqs.org/faqs/unix-faq/unixware/general/ UnixWare Frequently Asked Questions (General)]</ref> As of july 2026, UnixWare 7 2018 is the latest release of UnixWare.<ref>[https://www.xinuos.com/wp-content/uploads/UnixWare7D2M1b-ReleaseNotesSupplement-220305.pdf SCO UnixWare 7 Definitive 2018 - Release Notes Supplement]</ref> == Skunkware == '''SCO Skunkware''' is a collection of [[Free_and_Open_Source_Software|open source software]] packages ported and built for SCO operating systems. Examples of open source software used on UnixWare include [[OpenSSH]], the RPM package manager, [[vim]] and various Mozilla software.<ref name=skunkware></ref> == References == 4dc78b8254b70931da328037b0165c1afc153f37 5948 5946 2026-07-31T19:12:28Z Netcat 432 Update grammar wikitext text/x-wiki {{Stub}} [[Category:Misc_Operating_Systems]] {{DistributionInfobox | title = UnixWare | image = [[File:UnixWare_7_logo.svg|250px|center]] | caption = UnixWare 7 logo | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[RPM]]<ref name=skunkware>[https://skunkware.dev/ Skunkware]</ref> | defaultdesktops = [[CDE]] | usagetype = Desktop, Server | architectures = x86 | website = [https://www.xinuos.com/products/unixware-7/ xinuos.com/products/unixware-7] }} '''UnixWare''' is a [[proprietary software|proprietary]] [[UNIX]] system for x86 machines based on [[UNIX System V]]. Originally developed by Univel in 1992, it then passed to Novell, Santa Cruz Operation, Caldera, and The SCO Group before being sold to Xinuos. It is only available as a 32-bit x86 operating system.<ref>[http://www.faqs.org/faqs/unix-faq/unixware/general/ UnixWare Frequently Asked Questions (General)]</ref> As of July 2026, UnixWare 7 2018 is the latest release of UnixWare.<ref>[https://www.xinuos.com/wp-content/uploads/UnixWare7D2M1b-ReleaseNotesSupplement-220305.pdf SCO UnixWare 7 Definitive 2018 - Release Notes Supplement]</ref> == Skunkware == '''SCO Skunkware''' is a collection of [[Free_and_Open_Source_Software|open source software]] packages ported and built for SCO operating systems. Examples of open source software used on UnixWare include [[OpenSSH]], the RPM package manager, [[vim]] and various Mozilla software.<ref name=skunkware></ref> == References == a6983ed65cd06ac1c0426c6af08f6eb89ad5a704 0 1407 5947 2026-07-31T18:57:25Z Netcat 432 Create HandBrake page wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = HandBrake | releasestatus = Maintained | lastrelease = 1.11.2 | languages = [[C]], [[C#]] | developers = The HandBrake Team | website = https://handbrake.fr | license = [[GNU GPLv2]] | sourcecode = https://github.com/HandBrake/HandBrake }} '''HandBrake''' is an open-source media transcoder used for converting video to modern, widely supported codecs.<ref>{{Cite|title=HandBrake Website|url=https://handbrake.fr|accessdate=31 July 2026}}</ref> HandBrake leverages [[FFmpeg]] and other open-source tooling as part of its backend. == Features == Notable features of HandBrake include: * Batch encoding: HandBrake supports batch encoding, meaning multiple files can be queued and transcoded without human intervention. * Audio passthru: allows for audio tracks to be copied from the source, avoiding re-encoding in the process. * Video filters: files fed to HandBrake can be altered through filters, such as greyscale and de-noising. == References == 552445133fcd99f2ab3e2599b3613f7edbf6a3a5 6 1408 5949 2026-07-31T19:24:31Z MysteryBirb 353 wikitext text/x-wiki == Licensing == {{GPL}} 6b26f5cce63faf4ce1130ffc4f5c42cf3e3a00ac 0 1409 5950 2026-07-31T21:02:53Z MysteryBirb 353 Added dwl page with most info wikitext text/x-wiki {{Work In Progress}} {{SoftwareInfobox | caption = dwl logo | developers = dwl devs and community patches | firstrelease = dwl 0.2.2, 2021-12-22 | languages = [[C]] | lastrelease = dwl 0.8, 2025-12-28 | title = dwl | website = [https://codeberg.org/dwl/dwl Codeberg repo of dwl] | releasestatus = Maintained | image = [[File:dwl-logo.png|thumb|center]] }} == dwl - [[dwm]] but for [[Wayland]] == dwl is a minimal, hackable dynamically tiling window manager based on [[Wayland]]. dwl is like [[dwm]] but made for [[Wayland]], it adapts many of its features just like: * Dynamic tiling * Simple window borders * Tags * Client rules * Good mouse integration * One simple <code>config.h</code> file responsible for its config * Extensible with patches There are many more features it supports out of the box that are listed under its own Codeberg repository<ref>{{Cite|url=https://codeberg.org/dwl/dwl#background|title=Out of the box support|accessdate=2026-07-31}}</ref>. === Patches === dwl adds the ability to add custom functionality by letting you patch its code. 0c86eba01504372ebfceeb6f4ff558fb9dce1fab 5951 5950 2026-07-31T21:11:17Z Imnotgoodatnames 121 Added DISPLAYTITLE, removed first heading from page since that's not standard practice, bolded first instance of 'dwl' and did some minor rewording. wikitext text/x-wiki {{Work In Progress}} {{DISPLAYTITLE:dwl}} {{SoftwareInfobox | caption = dwl logo | developers = dwl devs and community patches | firstrelease = dwl 0.2.2, 2021-12-22 | languages = [[C]] | lastrelease = dwl 0.8, 2025-12-28 | title = dwl | website = [https://codeberg.org/dwl/dwl Codeberg repo of dwl] | releasestatus = Maintained | image = [[File:dwl-logo.png|thumb|center]] }} '''dwl''' is a minimal, hackable dynamically tiling [[Wayland Compositors|Wayland compositor]] aiming to replicate the look and feel of[[dwm]]. It adapts many of dwm's features including: * Dynamic tiling * Simple window borders * Tags * Client rules * Good mouse integration * One simple <code>config.h</code> file responsible for its configuration * Extensible with patches There are many more features it supports out of the box that are listed under its own Codeberg repository<ref>{{Cite|url=https://codeberg.org/dwl/dwl#background|title=Out of the box support|accessdate=2026-07-31}}</ref>. === Patches === dwl adds the ability to add custom functionality by letting you patch its code. 91894affc8377de56f2cfba5ad962eca5c0142d5 5952 5951 2026-07-31T21:11:46Z Imnotgoodatnames 121 typo wikitext text/x-wiki {{Work In Progress}} {{DISPLAYTITLE:dwl}} {{SoftwareInfobox | caption = dwl logo | developers = dwl devs and community patches | firstrelease = dwl 0.2.2, 2021-12-22 | languages = [[C]] | lastrelease = dwl 0.8, 2025-12-28 | title = dwl | website = [https://codeberg.org/dwl/dwl Codeberg repo of dwl] | releasestatus = Maintained | image = [[File:dwl-logo.png|thumb|center]] }} '''dwl''' is a minimal, hackable dynamically tiling [[Wayland Compositors|Wayland compositor]] aiming to replicate the look and feel of [[dwm]]. It adapts many of dwm's features including: * Dynamic tiling * Simple window borders * Tags * Client rules * Good mouse integration * One simple <code>config.h</code> file responsible for its configuration * Extensible with patches There are many more features it supports out of the box that are listed under its own Codeberg repository<ref>{{Cite|url=https://codeberg.org/dwl/dwl#background|title=Out of the box support|accessdate=2026-07-31}}</ref>. === Patches === dwl adds the ability to add custom functionality by letting you patch its code. 2771a9d250598597f3b040b35114f57b8d780adf 5954 5952 2026-08-01T18:25:40Z MysteryBirb 353 Added headline wikitext text/x-wiki {{Work In Progress}} {{SoftwareInfobox | caption = dwl logo | developers = dwl devs and community patches | firstrelease = dwl 0.2.2, 2021-12-22 | languages = [[C]] | lastrelease = dwl 0.8, 2025-12-28 | title = dwl | website = [https://codeberg.org/dwl/dwl Codeberg repo of dwl] | releasestatus = Maintained | image = [[File:dwl-logo.png|thumb|center]] }} == dwl - [[dwm]] but for [[Wayland]] == dwl is a minimal, hackable dynamically tiling window manager based on [[Wayland]]. dwl is like [[dwm]] but made for [[Wayland]], it adapts many of its features just like: * Dynamic tiling * Simple window borders * Tags * Client rules * Good mouse integration * One simple <code>config.h</code> file responsible for its config * Extensible with patches There are many more features it supports out of the box that are listed under its own Codeberg repository<ref>{{Cite|url=https://codeberg.org/dwl/dwl#background|title=Out of the box support|accessdate=2026-07-31}}</ref>. === Patches === dwl adds the ability to add custom functionality by letting you patch its code. 0c86eba01504372ebfceeb6f4ff558fb9dce1fab 5955 5954 2026-08-01T18:32:30Z MysteryBirb 353 Revert back and removed headline wikitext text/x-wiki {{Work In Progress}} {{DISPLAYTITLE:dwl}} {{SoftwareInfobox | caption = dwl logo | developers = dwl devs and community patches | firstrelease = dwl 0.2.2, 2021-12-22 | languages = [[C]] | lastrelease = dwl 0.8, 2025-12-28 | title = dwl | website = [https://codeberg.org/dwl/dwl Codeberg repo of dwl] | releasestatus = Maintained | image = [[File:dwl-logo.png|thumb|center]] }} '''dwl''' is a minimal, hackable dynamically tiling [[Wayland Compositors|Wayland compositor]] aiming to replicate the look and feel of [[dwm]]. It adapts many of dwm's features including: * Dynamic tiling * Simple window borders * Tags * Client rules * Good mouse integration * One simple <code>config.h</code> file responsible for its configuration * Extensible with patches There are many more features it supports out of the box that are listed under its own Codeberg repository<ref>{{Cite|url=https://codeberg.org/dwl/dwl#background|title=Out of the box support|accessdate=2026-07-31}}</ref>. === Patches === dwl adds the ability to add custom functionality by letting you patch its code. 2771a9d250598597f3b040b35114f57b8d780adf 0 254 5953 4129 2026-07-31T21:22:07Z Imnotgoodatnames 121 Removed the "Needs citations" template. I believe there's plenty of refs now to justify not having it according to the guidelines ("This should only be used on a page with controversial claims or is utilising content which has not been properly cited or attributed"). I also removed the "See also" section to avoid redundancy since the only entry there was a link to the dwm website, which is already listed in the infobox. + a few other tiny improvements wikitext text/x-wiki {{DISPLAYTITLE:dwm}} {{SoftwareInfobox | image = [[File:Dwm.svg|thumb]] | caption = dwm logo | title = dwm | releasestatus = Maintained | lastrelease = 6.6, 2025-08-09 | languages = [[C]] | developers = Suckless | website = [https://dwm.suckless.org/ dwm.suckless.org] }} [[Category:X_Window_Managers]] [[Category:Window Management Systems]] [[File:Dwm-shot.png|thumb|A screenshot a desktop running DWM]] '''dwm''' ('''D'''ynamic '''W'''indow '''M'''anager) is a [[Window Manager|window manager]] developed by Suckless. dwm is designed to be small in source code, fast and light.<ref>[https://dwm.suckless.org/#Differences dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref> The first version of dwm was released on July 14th, 2006 under the MIT/X Consortium license. == Installation == dwm is meant to be built from source. You can download the latest version of dwm by running:<syntaxhighlight lang="bash"> $ git clone https://git.suckless.org/dwm </syntaxhighlight>You can first configure it by making a copy of config.def.h and naming it config.h.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> This can be done by running:<syntaxhighlight lang="bash"> $ cp config.def.h config.h </syntaxhighlight><code>config.h</code> can then be configured to your liking. Before compiling dwm, make sure you have [[X11]] libraries installed. dwm can then be compiled by running:<syntaxhighlight lang="bash"> $ sudo make clean install </syntaxhighlight>If the command executes without any errors, you can then modify the ~/.xinitrc file, put <code>exec dwm</code> in it and then start X (by running <code>startx</code>) and dwm should be running. It is also recommended that you install [[dmenu]] and [[st]] along with dwm, as they provide you with a lightweight application launcher and a [[terminal emulator]]. == Configuration == Configuration is done through editing the config.h file which is written in C and recompiling dwm.<ref>[https://dwm.suckless.org/customisation/ Suckless' official customization page for DWM], suckless.org, 2025-08-27 (Accessed 2025-08-27)</ref> == Patches == dwm has many patches provided in the suckless website to add and improve its features<ref>[https://dwm.suckless.org/patches/ dwm - dynamic window manager], suckless.org, 2025-05-29 (Accessed: 2025-08-09)</ref>. Patches can be installed by running: patch -p1 < path/to/patch.diff If patch fails, you should check the .rej file, edit manually and recompile dwm. Some patches edit config.def.h, you should then edit the Makefile to remove config.h during clean and copy config.def.h to config.h. == References == f4e8e3042c527ba24653ade3709e4cb070502aa6 0 225 5956 5874 2026-08-02T03:51:49Z PhantasNick 291 changed logo image from 'thumb' to 'frameless' to fix Infobox formating wikitext text/x-wiki {{Stub}} {{DistributionInfobox | title = Red Hat Enterprise Linux | image = [[File:Red Hat logo.svg|frameless]] | caption = Red Hat Enterprise Linux (RHEL) | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = GNOME | usagetype = Desktop, Server | architectures = aarch64, i386, ia64, IBM Z, ppc, ppc64el, s390, s390x, x86_64 | website = [https://redhat.com/rhel/ redhat.com] }} [[Category:Linux Distributions]] [[File:Red Hat Enterprise Linux 9 Workstation showing GNOME Shell 40.png|thumb|Red Hat Enterprise Linux 9.0 Workstation showing GNOME Shell 40]] '''Red Hat Enterprise Linux''', commonly abbreviated as RHEL, is a commercial [[Linux Distributions|Linux distribution]] developed by Red Hat for the enterprise market and the first version of RHEL was released on the February 22, 2000.<ref>[https://www.redhat.com/en/about/press-releases/red-hat-enterprise-edition-product-line-optimizes-solutions-top-e-business-applications Red Hat Enterprise Edition Product Line Optimizes Solutions for Top E-business Applications] Press release by Red Hat. Retrieved February 20, 2020.</ref> Red Hat profits from this distribution by providing 24/7 technical support to business customers.<ref>[https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux Red Hat Enterprise Linux], Red Hat, 2025-08-09 (Accessed: 2025-08-09)</ref> == Controversy == Red Hat originally freely provided its source code, but restricted free re-distributions of the officially supported versions of RHEL. Derivative distributions such as Rocky Linux or Oracle Linux were able to be redistributed by removing Red Hat's trademarks. In 2023, Red Hat stopped publicly providing the source code for RHEL.<ref>[https://www.theregister.com/2023/06/23/red_hat_centos_move/ Red Hat strikes a crushing blow against RHEL downstreams] The Register. Retrieved 24 June 2023.</ref> However, it is still available to customers and developers under a Non Disclosure Agreement. == References == <references /> 3bda7d35acfb90d1c8f2c6b008c37cad9dc95f4a 2 427 5957 3566 2026-08-02T20:09:52Z Ow0cast 249 wikitext text/x-wiki ==<nowiki>:</nowiki>3== see [[wikipedia:User:Ow0cast|my wikipedia userpage]] <!-- hello --> 7fa8b9228af12c48af3af98e2817da2897411c9e 0 1410 5958 2026-08-03T17:32:12Z Imnotgoodatnames 121 Created page with category, refs wikitext text/x-wiki [[Category:Desktop Environments]] {{SoftwareInfobox | image = [[File:Common_Desktop_Environment_logo.svg|200px|CDE_Logo]] | caption = CDE Logo | title = Common Desktop Environment | releasestatus = Maintained | lastrelease = 2.5.3, 2025-11-25 | license = [[Proprietary software|Proprietary]] (until 2012), [[GNU General Public License#GNU Lesser General Public License_(LGPL)|LGPL-2.0-or-later]] | languages = C, C++ | developers = The Open Group, HP, IBM, Sun, USL (historical) CDE Project (modern) | website = https://sourceforge.net/projects/cdesktopenv/ }} [[File:CDE_Application_Builder.png|thumb|Screenshot of the Common Desktop Environment]] The '''Common Desktop Environment''' is a [[desktop Environments|desktop environment]] for the [[X Window System]] built on the [[Motif]] widget toolkit. It was announced in June 1993 as part of the COSE project by IBM, HP, Sun and USL, who each contributed to different parts of the environment.<ref>[https://web.archive.org/web/20120207160207/http://bubl.ac.uk/ARCHIVE/subject/computing/misc/coseup6.htm COSE Update FYI], archived 2012-02-07 (accessed 2026-08-03)</ref> '''CDE''' is based on HP's Visual Access Model desktop environment.<ref>[https://web.archive.org/web/20140821022858/http://www.hpl.hp.com/hpjournal/96apr/apr96a4.pdf Migrating HP VUE Desktop Customizations to CDE], archived 2014-08-21 (accessed 2026-08-03)</ref> CDE was the de facto standard desktop environment for UNIX systems, and it inspired both the [[KDE Plasma|KDE]] and [[GNOME]] projects. [[Red Hat Linux]] recieved a CDE port in 1997, and it remained the only [[Linux distribution]] to have a CDE port until its [[Free and Open Source Software|open-source]] release in 2012.<ref>[https://www.osnews.com/story/26247/cde-released-as-open-source/|CDE released as open source], 2012-08-06 (accessed 2026-08-03)</ref> Since its open-source release CDE development is managed by the CDE Project. It has been successfully compiled for other Linux distributions and other operating systems using the X Window System, including [[FreeBSD]] and [[NetBSD]].<ref>[https://www.freshports.org/x11/cde/ FreshPorts -- x11/cde] (accessed 2026-08-03)</ref><ref>[https://pkgsrc.se/wm/cde Common Desktop Environment] (accessed 2026-08-03)</ref> == References == 7b635ea47c6285a82e96d6198ab3c81ef1fef553 0 1411 5959 2026-08-04T02:59:11Z Strangely Human Feeling 415 Created mpv page and added lil blurb wikitext text/x-wiki {{DISPLAYTITLE:mpv}} [[Category:Software]] {{SoftwareInfobox | image = [[File:mpv logo.svg|150px]] | caption = The mpv Logo | title = mpv | releasestatus = Maintained | lastrelease = 0.41.0 | languages = [[C]], [[Lua]], [[Swift]] | developers = | website = https://mpv.io/ | sourcecode = https://github.com/mpv-player/mpv | license = GPLv2 }} '''mpv''' is a media player accessible through the command line.<ref>https://mpv.io/</ref> It uses configurable keyboard shortcuts to control video and audio during playback, such as speed, volume, audio tracks, subtitles, etc. It supports scripting through [[Lua]] and [[JavaScript]].<ref>https://mpv.io/manual/stable/#lua-scripting</ref> mpv is often embeded as a media frontend for command line software such as [https://github.com/Benexl/yt-x yt-x]. <ref>https://mpv.io/manual/stable/#embedding-into-other-programs-libmpv</ref><ref>https://github.com/mpv-player/mpv/wiki/Applications-using-mpv</ref> 7096f3a3dc48f6eef2d73e0426e9dea591885056 5960 5959 2026-08-04T03:06:37Z Strangely Human Feeling 415 /* */ added logo. (someone already uploaded it but never used it? lol) wikitext text/x-wiki {{DISPLAYTITLE:mpv}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Unofficial Mpv logo (with gradients).svg|150px]] | caption = The mpv Logo | title = mpv | releasestatus = Maintained | lastrelease = 0.41.0 | languages = [[C]], [[Lua]], [[Swift]] | developers = | website = https://mpv.io/ | sourcecode = https://github.com/mpv-player/mpv | license = GPLv2 }} '''mpv''' is a media player accessible through the command line.<ref>https://mpv.io/</ref> It uses configurable keyboard shortcuts to control video and audio during playback, such as speed, volume, audio tracks, subtitles, etc. It supports scripting through [[Lua]] and [[JavaScript]].<ref>https://mpv.io/manual/stable/#lua-scripting</ref> mpv is often embeded as a media frontend for command line software such as [https://github.com/Benexl/yt-x yt-x]. <ref>https://mpv.io/manual/stable/#embedding-into-other-programs-libmpv</ref><ref>https://github.com/mpv-player/mpv/wiki/Applications-using-mpv</ref> 3be0e84aa1ccae03087ce54ba600a3b6c8b0fd85 0 405 5961 4092 2026-08-05T13:05:55Z Uniolo 345 Clarified that Linux (as in the kernel) does not avoid proprietary software; changed "Linux" to "Many [[Linux Distributions]]" wikitext text/x-wiki [[Category:Terminology]] {{Cleanup|Short page}}Proprietary software is a type of non-free software, usually owned by a company or an organization, which forbids the user from viewing, modifying, or redistributing it and it's source code. Many [[Linux Distributions]] and other open source operating systems will avoid or not support proprietary software when possible. This is mainly due to incompatible licensing.<ref>https://solutionshub.epam.com/blog/post/proprietary-software-definition-examples Epam, 2025 (imported 27th June 2025)</ref> However some proprietary software included with certain Linux distros include NVIDIA graphics drivers, certain Wi-Fi and Bluetooth firmware, proprietary games via platforms like Steam. Some examples of proprietary software include, but are not limited to, Microsoft Windows, macOS, Adobe Photoshop, Steam, the Epic Games Launcher and the Microsoft Office Suite. == References == b4426d5b8c07fd130d576c303078eec051e3cda5 0 1412 5962 2026-08-06T14:04:57Z Sedot 397 initial draft wikitext text/x-wiki openQA is an automated test tool developed by openSUSE and SUSE that makes it possible to test the whole installation process of an operating system. <ref>[https://open.qa openQA Homepage]</ref> <references /> 8367a2ff6efcc56a5c27f95f9d91a1e907e31502 5963 5962 2026-08-06T14:46:27Z Sedot 397 add SoftwareInfoBox wikitext text/x-wiki {{SoftwareInfobox | title = openQA | releasestatus = Maintained | firstrelease = 2013 | lastrelease = rolling release model | languages = Perl, Javascript, Shell, SCSS and other | developers = [[SUSE]], [[openSUSE]] | website = [https://open.qa openQA] }} openQA is an automated test tool developed by openSUSE and SUSE that makes it possible to test the whole installation process of an operating system. <ref>[https://open.qa openQA Homepage]</ref> <references /> 994827295eb04ac596ea6bc049526b9c626164b4 5964 5963 2026-08-06T15:24:15Z Sedot 397 change link to documentation wikitext text/x-wiki {{SoftwareInfobox | title = openQA | releasestatus = Maintained | firstrelease = 2013 | lastrelease = rolling release model | languages = Perl, Javascript, Shell, SCSS and other | developers = [[SUSE]], [[openSUSE]] | website = [https://open.qa openQA] }} openQA is an automated test tool developed by openSUSE and SUSE that makes it possible to test the whole installation process of an operating system. <ref>[https://open.qa/documentation/ openQA Documentation]</ref> <references /> 5bf9caafa2a00b713f27d24e7f67b337c3e7b01b 5965 5964 2026-08-06T15:48:53Z Sedot 397 add link/references wikitext text/x-wiki {{SoftwareInfobox | title = openQA | releasestatus = Maintained | firstrelease = 2013-05-14<ref>[https://build.opensuse.org/projects/openSUSE:Factory/packages/openQA/files/openQA.changes?expand=1 openQA], openQA.changes changelog (Accessed: 2026-08-06) </ref> | lastrelease = rolling release model | languages = Perl, Javascript, Shell, SCSS and other | developers = [[SUSE]], [[openSUSE]] | website = [https://open.qa openQA] }} openQA is an automated test tool developed by openSUSE and SUSE that makes it possible to test the whole installation process of an operating system. <ref>[https://open.qa/documentation/ openQA Documentation]</ref> == References == <references /> ce5c3418a81f9ac4371ccb2114d621dc2265a169 5966 5965 2026-08-06T15:56:08Z Sedot 397 wikitext text/x-wiki {{SoftwareInfobox | title = openQA | releasestatus = Maintained | firstrelease = 2013-05-14<ref>[https://build.opensuse.org/projects/openSUSE:Factory/packages/openQA/files/openQA.changes?expand=1 openQA], openQA.changes changelog (Accessed: 2026-08-06) </ref> | lastrelease = rolling release model | languages = Perl, Javascript, Shell, SCSS and other | developers = [[SUSE]], [[openSUSE]] | website = [https://open.qa openQA] | sourcecode = https://github.com/os-autoinst/openQA | license = GPLv2 }} openQA is an automated test tool developed by openSUSE and SUSE that makes it possible to test the whole installation process of an operating system. <ref>[https://open.qa/documentation/ openQA Documentation]</ref> == References == <references /> c52d263ed901a071e441324fe22b5437f9083008 0 277 5968 5876 2026-08-06T17:16:20Z Sedot 397 cleaned up DistributionInfobox wikitext text/x-wiki {{Needs_Citations}} {{Stub}} {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[Category:Linux Distributions]] [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] Rocky Linux is a Linux distribution developed by RESF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit".<ref>{{Cite|url=https://www.resf.org/faq/is-resf-nonprofit|title=Is the RESF a non-profit? - RESF FAQ|author=RESF|accessdate=14 September 2025}}</ref> It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. 0616eec7a57142c94104c4de9269e2967fa68b33 0 1134 5969 5544 2026-08-06T17:47:21Z Uniolo 345 Noted that E2EE and federation is planned. wikitext text/x-wiki [[Category:Software]] {{SoftwareInfobox | image = [[File:Fluxer-symbol-color.svg|150px]] | caption = The Fluxer logo | title = Fluxer | releasestatus = Maintained | lastrelease = 0.0.8 | languages = [[Electron]], [[TypeScript]], [[Rust]], [[Erlang]] | developers = Hampus Kraft and Contributors | website = https://fluxer.app | sourcecode = https://github.com/fluxerapp/fluxer | license = AGPLv3 }} Fluxer is a free, open-source, cross-platform instant messaging and VoIP platform designed as a privacy-respecting alternative to Discord. ==Overview== '''Fluxer''' is available as a [[flatpak]] on [[Flathub]], as well as other official formats including [[AppImage]], tar.gz, [[RPM]], .[[deb]], and more. Fluxer also allows for custom clients and has plans to incorporate federation and self-hosting capabilities in the future. ==Features== Notable features of Fluxer include: * Communities, with organized channels, categories, roles and moderation tools. * Text channels. * Voice channels. * Screen sharing. * Custom emotes and stickers. * Media attachments like images, videos, audio or text. Note that attachments have an expiration date depending on their size. * Discord-compatible markdown, with some additional features like [https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts alerts]. * Message search, with ability to filter by users, channels, dates, and more. * A Progressive Web App for mobile. * A Discord-compatible bot and webhook API. While not yet implemented, Hampus Kraft has confirmed that federation, and E2EE for certain features, are planned<ref>{{Cite|url=https://fluxer.app/blog/roadmap-2026|title=[Fluxer] Roadmap 2026|author=Hampus Kraft|year=January 26, 2026|accessdate=2026-08-06}}</ref>. ==Server Info== '''Vultr''' provides Fluxer's primary hosting. The main store for account data (messages, communities, profiles, and other persisted content) is in '''Piscataway, New Jersey''', and the object storage for user-uploaded files runs in the same region. Voice and real-time communication infrastructure also runs on Vultr across multiple regions worldwide, so calls can be routed near you for latency. '''Bunny.net''' operates Fluxer's content delivery network, with edge nodes worldwide, for user-generated content on the fluxerusercontent.com domain. In the future, Fluxer wants to offer the ability to partition your data entirely within the EU — for both your account and your communities. As stated in their FAQ, which you can find on https://fluxer.gg/fluxer-hq 4963328f2e8ae8372ff899f8ea66a794206228a8 0 781 5970 4993 2026-08-06T18:15:28Z Sedot 397 add References, rewrite Intro Text wikitext text/x-wiki {{stub}} {{Needs Citations}} [[Category:Package Managers]] '''RPM''' (originally Red Hat Package Manager, now a acronym for RPM Package Manager) stands for '''RPM Package Manager'''. <ref>[https://rpm.org/timeline RPM Timeline], RPM renamed (Jan 17 2000) – (Accessed: 2026-06-08)</ref> It is both a package format (<code>.rpm</code>) and the name of the [[package]] management system used in [[Linux Distributions|Linux distributions]] such as [[Red Hat Enterprise Linux]], [[Fedora Linux]], [[Rocky Linux]], [[CentOS]], [[AlmaLinux]] and [[openSUSE]]. == Overview == An RPM package is a file that contains: * Compiled software binaries * Configuration files * Metadata (name, version, dependencies, etc.) * Installation and removal scripts The standard file extension is <code>.rpm</code>. == Components of an RPM Package == * <b>Header</b>: Contains metadata (name, version, architecture, etc.) * <b>Payload</b>: The actual files to be installed * <b>Scripts</b>: Optional pre/post-install and removal scripts == Common Tools == * <code>rpm</code> — Low-level tool for querying, installing, and removing RPM packages * <code>rpmbuild</code> — Tool for building RPM packages from SPEC files * <code>rpmlint</code> — Linter to check RPM quality and packaging errors == Basic Commands == === Installing an RPM file === <syntaxhighlight lang="bash"> sudo rpm -ivh package.rpm </syntaxhighlight> === Query installed packages === <syntaxhighlight lang="bash"> rpm -q package-name </syntaxhighlight> === List all installed RPMs === <syntaxhighlight lang="bash"> rpm -qa </syntaxhighlight> === Remove a package === <syntaxhighlight lang="bash"> sudo rpm -e package-name </syntaxhighlight> === Verify a package === <syntaxhighlight lang="bash"> rpm -V package-name </syntaxhighlight> == Advantages == * Dependency tracking * Transaction-based installation/removal * Clean upgrade paths * Strong ecosystem support (DNF, YUM, repositories, etc.) == Limitations == * Requires careful dependency management * Binary format — not human-readable == External Resources == * [https://rpm.org/ Official RPM Site] * [https://fedoraproject.org/wiki/RPM Fedora RPM Guide] * [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Fedora Packaging Guidelines] == See Also == * [[yum]] * [[dnf]] * [[rpmbuild]] * [[zypper]] == References == <references /> bc2fd088875a0023dc643b46ea665a7e34fb6a47 0 781 5971 5970 2026-08-06T18:16:24Z Sedot 397 wikitext text/x-wiki {{stub}} {{Needs Citations}} [[Category:Package Managers]] '''RPM''' (originally Red Hat Package Manager) stands for '''RPM Package Manager'''. <ref>[https://rpm.org/timeline RPM Timeline], RPM renamed (Jan 17 2000) – (Accessed: 2026-06-08)</ref> It is both a package format (<code>.rpm</code>) and the name of the [[package]] management system used in [[Linux Distributions|Linux distributions]] such as [[Red Hat Enterprise Linux]], [[Fedora Linux]], [[Rocky Linux]], [[CentOS]], [[AlmaLinux]] and [[openSUSE]]. == Overview == An RPM package is a file that contains: * Compiled software binaries * Configuration files * Metadata (name, version, dependencies, etc.) * Installation and removal scripts The standard file extension is <code>.rpm</code>. == Components of an RPM Package == * <b>Header</b>: Contains metadata (name, version, architecture, etc.) * <b>Payload</b>: The actual files to be installed * <b>Scripts</b>: Optional pre/post-install and removal scripts == Common Tools == * <code>rpm</code> — Low-level tool for querying, installing, and removing RPM packages * <code>rpmbuild</code> — Tool for building RPM packages from SPEC files * <code>rpmlint</code> — Linter to check RPM quality and packaging errors == Basic Commands == === Installing an RPM file === <syntaxhighlight lang="bash"> sudo rpm -ivh package.rpm </syntaxhighlight> === Query installed packages === <syntaxhighlight lang="bash"> rpm -q package-name </syntaxhighlight> === List all installed RPMs === <syntaxhighlight lang="bash"> rpm -qa </syntaxhighlight> === Remove a package === <syntaxhighlight lang="bash"> sudo rpm -e package-name </syntaxhighlight> === Verify a package === <syntaxhighlight lang="bash"> rpm -V package-name </syntaxhighlight> == Advantages == * Dependency tracking * Transaction-based installation/removal * Clean upgrade paths * Strong ecosystem support (DNF, YUM, repositories, etc.) == Limitations == * Requires careful dependency management * Binary format — not human-readable == External Resources == * [https://rpm.org/ Official RPM Site] * [https://fedoraproject.org/wiki/RPM Fedora RPM Guide] * [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Fedora Packaging Guidelines] == See Also == * [[yum]] * [[dnf]] * [[rpmbuild]] * [[zypper]] == References == <references /> f7bee103e747407380afd68f711c84444d5860f1 0 268 5972 5530 2026-08-06T18:26:02Z Imnotgoodatnames 121 bump latest release wikitext text/x-wiki [[Category:Software]] [[Category:Command-line software]] [[Category:System information tools]] {{SoftwareInfobox | image = [[File:Fastfetch.png|thumb]] | caption = Fastfetch running on Fedora | title = Fastfetch | releasestatus = Maintained | lastrelease = 2.67.0, 2026-08-06 | languages = [[C (programming language)|C]] | developers = fastfetch-cli | website = [https://github.com/fastfetch-cli/fastfetch GitHub repository] | license = [[MIT License|MIT]] | firstrelease = 1.0.0, 2020-03-20 }} '''Fastfetch''' is a cross-platform command-line utility for displaying system information, similar in purpose to [[Neofetch]]. It is primarily written in [[C (programming language)|C]] and is designed with a strong focus on speed and low resource usage. Fastfetch can display details about the [[Operating system|operating system]], hardware components, and installed software in a highly configurable format<ref name=":0">{{Cite|url=https://github.com/fastfetch-cli/fastfetch|title=Fastfetch GitHub page}}</ref>. The tool supports a wide range of modules, allowing users to customise the output to include information such as CPU, GPU, memory, storage, display resolution, kernel version, package count, and more. It is actively maintained and available for Linux, macOS, and Windows<ref name=":0" />. == See also == * [[Neofetch]] * [[Screenfetch]] == References == <references /> 8965e97ef23c63a551d8535bb986e64ae02789d8 0 1413 5973 2026-08-06T18:43:50Z Sedot 397 first draft wikitext text/x-wiki YUM the [[package]] manager was an automatic updater and installer for rpm-based systems. It is now deprecated and the repository was archived.<ref>[https://github.com/rpm-software-management/yum YUM Github Archive], (Accessed: 2026-08-06).</ref> The succesor of YUM is [[DNF]]. == References == <references /> 8ca6b057b1b1189ae471ce8f1b18ef84f10e6754 5974 5973 2026-08-06T18:44:46Z Sedot 397 wikitext text/x-wiki YUM the [[package]] manager was an automatic updater and installer for [[rpm]]-based systems. It is now deprecated and the repository was archived.<ref>[https://github.com/rpm-software-management/yum YUM Github Archive], (Accessed: 2026-08-06).</ref> The succesor of YUM is [[DNF]]. == References == <references /> 2ce6788b46a6b446fd936c8dee40f02fc400e5e4 0 272 5975 5154 2026-08-06T18:51:02Z Sedot 397 add link yum page wikitext text/x-wiki [[Category:Software]] [[Category:Package Managers]] {{Cleanup|The article does not reflect the latest information on dnf5}}{{Cleanup|is that <code>dnf</code>'s importance is described in a pretty biased way, and some parts of this page feels somewhat AI-generated.}}{{Needs Citations}} {{SoftwareInfobox | image = [[File:DNF Command Line Interface.png|frameless]] | caption = Invoking <code>sudo dnf upgrade</code> on a terminal with <code>dnf4</code> | title = DNF | releasestatus = Maintained | lastrelease = <code>dnf5</code> 5.2.13.1 (2025-04-25) | languages = [[C++]] | developers = [[Fedora]] and Red Hat, et al. | website = [https://github.com/rpm-software-management/dnf5/ github.com/rpm-software-management/dnf5] }} '''DNF''', short for ''Dandified YUM'', is a software package manager for Linux distributions such as [[Fedora]], [[CentOS]], and [[RHEL]] (Red Hat Enterprise Linux). It was designed to be a better version of the traditional [[yum]] (Yellowdog Updater Modified) package manager, offering better performance, dependency resolution, and a more user-friendly command-line interface. == History == DNF was introduced as a replacement for YUM in Fedora 18, aiming to address some of the issues of its original predecessor. Development on DNF began in 2011, with a focus on modernizing the package management system for Fedora and other [[RPM]]-based distributions. === Development of DNF5 === The development of DNF5, the next-generation Fedora package manager, began in early 2020 as a complete rewrite of the existing DNF4 codebase to address architectural and performance limitations:<ref>[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NWSURJRGZAIIMNZJT244DHDPOG2PBQXZ/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> <blockquote> We've managed to drop a lot of redundant code across the whole DNF stack in the past years, but we have reached a point when it's nearly impossible to consolidate the code any further without breaking the API/ABI. Especially with PackageKit being dead<ref>[https://blogs.gnome.org/hughsie/2019/02/14/packagekit-is-dead-long-live-well-something-else/ PackageKit is dead, long live, well, something else], hughsie, 2019 (Accessed 2025-06-21)</ref>, we can't move with the old "libhif" API in libdnf, because making any bigger changes to PackageKit is clearly out of scope. </blockquote> The announcement of DNF5 development was made in March 2020, with a roadmap targeting major API changes and early development snapshots throughout 2020, aiming for inclusion in Fedora 34 and stable replacement of DNF4 by early 2021.<ref>[https://lwn.net/Articles/814066/ Announcing the start of DNF 5 development], Daniel Mach, 2020 (Accessed: 2025-06-21)</ref> Key motivations for DNF5's development included the need to modernize the codebase, which had become cluttered and difficult to maintain, and to move away from dependencies on Python and older APIs. The new design emphasized a fully featured package manager written primarily in C++ for improved performance, reduced resource usage, and a smaller install size compared to DNF4.<ref>[https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5#Benefit_to_Fedora Make DNF5 The Default], Jaroslav Mracek, 2022 (Accessed 2025-06-21)</ref> DNF5 also aimed to unify the software management tools in Fedora by replacing DNF and Microdnf, and providing a new daemon alternative to PackageKit.<ref name=":0">[https://ostechnix.com/dnf5-package-manager-introduction/ Introduction to DNF5: The Next-Generation Fedora Package Manager], Sk, 2025 (Accessed: 2025-06-21)</ref> DNF5 introduced a new core library (libdnf5), revamped plugin systems, enhanced modularity support, and a streamlined command-line interface with improved user experience. The development process was marked by an emphasis on openness, community involvement, and transparent upstream issue tracking to foster broader collaboration. By Fedora 38, DNF5 was available, and it became the default package manager in Fedora 41, fully replacing the older DNF.<ref name=":0" /> == Features == ==== Dependency Resolution ==== DNF utilizes advanced dependency resolution algorithms to ensure that all required dependencies for a package are installed correctly. It resolves dependencies 10x more efficiently than YUM, resulting in faster package installation and updates. ==== Transaction History ==== DNF maintains a transaction history, allowing users to review previous actions such as package installations, updates, and removals. This feature helps users track any changes to the system, and troubleshoot any issues that arise. ==== Modularity Dupport ==== DNF offers support for modular repositories, allowing users to enable or disable specific modules within a repository. This approach provides larger flexibility in managing software components and their dependencies. ==== Plugin System ==== DNF features a plugin architecture that enables developers to extend it's functionality with additional features and customization. Various plugins are available for tasks such as package cleaning, download acceleration, and repository management. ==== Parallel Downloads ==== DNF supports parallel package downloads, allowing multiple packages to be retrieved simultaneously from repositories. This feature speeds up the overall installation and update process, especially on systems with high-speed internet connections. ==== Package Groups ==== DNF allows packages to be organized into groups, making it easier to install related sets of software. Users can install entire groups of packages with a single command, streamlining the setup of development environments or specific software stacks. == Usage == DNF can be used from the command line interface (CLI) to perform various package management tasks, including: * Installing Packages: <code>dnf install <package_name></code> * Updating Packages: <code>dnf update</code> * Removing Packages: <code>dnf remove <package_name></code> * Listing Installed Packages: <code>dnf list installed</code> * Searching for Packages: <code>dnf search <keyword></code> * Managing Repositories: <code>dnf repolist</code>, <code>dnf config-manager</code> * Viewing Transaction History: <code>dnf history</code> == Compatibility == DNF is the default package manager for Fedora and is also available for CentOS/RHEL starting from version 8. While it is not directly compatible with systems using YUM, DNF can handle YUM repositories and packages seamlessly, providing a smooth transition for users upgrading from older distributions. == Community and Development == DNF is an open-source project developed and maintained by the Fedora community with contributions from Red Hat and other Linux enthusiasts. The project is hosted on GitHub, where users can report issues, contribute code, and participate in discussions about future enhancements and features. == Conclusion == DNF represents a significant evolution in package management for RPM-based Linux distributions, offering improved performance, dependency resolution, and usability compared to its original predecessor, YUM. With its robust feature set, active development community, and widespread adoption, DNF continues to be a vital component of modern Linux operating systems. == References == 9848a95515750bce9a256fa55a6ac63281834b03 0 1414 5976 2026-08-06T20:36:16Z Sedot 397 initial draft wikitext text/x-wiki '''Flathub''' is a Appstore (or public [[repository]]) for [[Flatpak]] Applications providing Users a way to get their Apps and Developers the option to reach millions of Linux Users on popular [[Linux Distributions]]. <ref>[https://flathub.org/en/about Flathub About]</ref> The Documentation for == Reference == <references /> 6dd11de2a9b653e140d49545b3c96a4550828b1f 5977 5976 2026-08-06T20:37:13Z Sedot 397 wikitext text/x-wiki '''Flathub''' is a Appstore (or public [[repository]]) for [[Flatpak]] Applications providing Users a way to get their Apps and Developers the option to reach millions of Linux Users on popular [[Linux Distributions]]. <ref>[https://flathub.org/en/about Flathub About]</ref> == Reference == <references /> 8a5e63e5376dfc7c526895a1752f785c63400c93 0 1398 5978 5967 2026-08-07T11:58:47Z Imnotgoodatnames 121 Added .app example, remove stub as i feel the page is decently whole now wikitext text/x-wiki {{SoftwareInfobox | title = GNUstep | caption = GNUstep logo | releasestatus = Maintained | developers = GNUstep developers, GNU Project | image = [[File:GNUstep logo.png{{!}}class=skin-invert|200px|GNUstep_logo]] | languages = [[Objective-C]] | lastrelease = Varied (GNUstep components often have independent releases)<ref>[https://github.com/gnustep GNUstep Github]</ref> | website = [https://www.gnustep.org/ gnustep.org] }} [[File:GNUstep_desktop.png|thumb|GNUstep managing its own windows, with the Macintosh menu interface style.]] '''GNUstep''' is a [[Free_and_Open_Source_Software|free]] implementation of Apple's [[Cocoa]] API and a collection of software based on that API. It is a part of the [[GNU]] project. Both GNUstep and Cocoa share the same OpenStep roots.<ref name="website">[https://gnustep.org GNUstep homepage]</ref> GNUstep supports many unique features such as special menu bar behaviour, which can be configured to act like NeXTSTEP's, [[Microsoft Windows]]' or even [[macOS]]' (with the menu bar of supported applications displayed as a small seperate window, as part of the application window or on top of the display, respectively). It can also manage windows and window decorations of any supported app, therefore technically bypassing the need for a seperate [[X_Window_Manager|window manager]], though non-GNUstep windows will remain unmanaged.<ref>[https://www.gnustep.org/resources/documentation/User/Gui/DefaultsSummary.html User Defaults Summary for GNUstep Libraries]</ref> GNUstep is cross platform and supports [[UNIX]] and Unix-like systems and Microsoft Windows. On Unix and Unix-like systems it runs primarily on [[X_Window_System|X]] with limited support for [[Wayland]].<ref>[https://home.gnustep.org/windows/installer.html Windows Installer]</ref><ref>[https://www.phoronix.com/news/GNUstep-0.29-With-Wayland GNUstep Releases Early Wayland Support, Many Other Improvements Too]</ref> [[Window Maker]] is the most common window manager used with GNUstep due to its limited integration with it and their shared default NeXTSTEP-inspired aesthetics.<ref>[https://mediawiki.gnustep.org/index.php/Window_Maker Window Maker]</ref> == Applications == GNUstep '''applications''' are distributed in the form of portable application bundles. Like on macOS, they are regular directories with the '.app' suffix that contain the [[executable]] itself, the application icon and various metadata, such as the application version.<ref>[https://www.gnustep.org/resources/documentation/Developer/Base/Reference/NSBundle.html NSBundle class reference]</ref> === Example GNUstep application === <syntaxhighlight lang="text"> TextEdit.app ├── Resources │ ├── ApplicationScripting.xlp │ ├── Edit.tiff │ ├── EditTitle.tiff │ ├── Encodings.txt │ ├── English.lproj │ ├── Info-gnustep.plist │ ├── ScriptingInfo.plist │ ├── TextEdit.desktop │ ├── rtf.tiff │ ├── rtfd.tiff │ └── text.tiff ├── TextEdit └── stamp.make </syntaxhighlight> == References == 3193495eaa8b0acdfd1fdde2766a499e2e5a99aa 0 1415 5979 2026-08-09T10:54:06Z Imnotgoodatnames 121 Created page with caregory, stub, refs, infobox wikitext text/x-wiki {{stub}} [[Category:Linux Distributions]] {{DistributionInfobox |title = Android |image = [[File:Android_2023_3D_logo_and_wordmark.svg{{!}}class=skin-invert|Android_logo|frameless]] |caption = Android logo |releasestatus = Maintained |releasemodel = Stable Release<ref>[https://https://developer.android.com/about/versions/ Android releases]</ref> |packagemanager = Android PKG |defaultdesktops = Launcher3 (AOSP) |usagetype = Smartphone, Desktop, Smart devices |architectures = aarch64, armeabi, x86, x86_64 |website = [https://android.com/ android.com] }} Android is a [[Linux Distributions|Linux-based]] operating system developed by google primarily for touch-screen devices. As of 2026, it is the world's most widely used operating system.<ref>[https://gs.statcounter.com/os-market-share Operating System Market Share Worldwide - statcounter] (accessed 2026-08-09)</ref> Android isn't intended to be manually installed by users, but rather preinstalled by device manufacturers, who usually include their own proprietary software. The core open-source Android operating system is known as the Android Open Source Project (AOSP).<ref>[https://source.android.com/ Android Open Source Project]</ref> Android packages (apps), which use the Android APK format, are usually installed through app stores such as the proprietary Google Play store or the open-source F-Droid. Alternatively, apk files can also be installed manually. == References == b76d10fb470dc4b6d7769a3e759b9aadd156fd98 8 538 5980 5319 2026-08-09T20:58:23Z Atmois 13 Update text wikitext text/x-wiki Check out our [https://discord.foss.wiki Discord Server] to get updates on the wiki and see what we are up to. 5ff230e6d18d55026132a4377845a610b7642ba4 0 1416 5981 2026-08-10T11:29:40Z Imnotgoodatnames 121 Create page, WIP thing, refs, blablabla wikitext text/x-wiki {{stub}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | caption = MSYS2 logo <!-- No logo here currently as the license of the MSYS2 logo is currently unclear. please don't try to add it until the license situation regarding it is cleared up. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://https://www.msys2.org// msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref>[https://msys2.org MSYS2 home page]</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?]</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 - MSYS2]</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64]</ref> MSYS2 uses the [[Pacman]] package manager for package managment.<ref name=whatis/> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. <ref>[https://www.msys2.org/docs/environments/ Environments - MSYS2]</ref> {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |UCRT64 |<code>/uscrt64</code> |gcc |UCRT |x86_64 |- |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == References == b2558380598ac62977fdbfd8c70bb737fe9c914d 5982 5981 2026-08-10T11:56:10Z Imnotgoodatnames 121 goddamn it wikitext text/x-wiki {{Work In Progress}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | caption = MSYS2 logo <!-- No logo here currently as the license of the MSYS2 logo is currently unclear. please don't try to add it until the license situation regarding it is cleared up. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://https://www.msys2.org// msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref>[https://msys2.org MSYS2 home page]</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?]</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 - MSYS2]</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64]</ref> MSYS2 uses the [[Pacman]] package manager for package managment.<ref name=whatis/> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. <ref>[https://www.msys2.org/docs/environments/ Environments - MSYS2]</ref> {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |UCRT64 |<code>/uscrt64</code> |gcc |UCRT |x86_64 |- |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == References == 30b0907b067f72f635236c4c63342b1bce21be6c 5987 5982 2026-08-10T15:45:45Z Imnotgoodatnames 121 Minor rewording, typo fixing, more ARM & package managment info. WIP template REMAINS until logo license situation is resolved. wikitext text/x-wiki {{Work In Progress}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | caption = MSYS2 logo <!-- No logo here currently as the license of the MSYS2 logo is currently unclear. please don't try to add it until the license situation regarding it is cleared up. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://https://www.msys2.org// msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2 home page]</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?]</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 - MSYS2]</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64]</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by <ref name=envs>[https://www.msys2.org/docs/environments/ Environments - MSYS2]</ref> {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |UCRT64 |<code>/ucrt64</code> |gcc |UCRT |x86_64 |- |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS. It is always active, all other environments inherit from it and add their own environment variables on top. === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure compatibility with ARM, not to install an ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11 (#96) - MSYS2 Installer - Github issues ]</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue MSYS2 Packages]</ref> {| class="wikitable" !Environment !Package name prefix |- |MSYS |None (no package name prefix) |- |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |MINGW32 |<code>mingw-w64-</code> |- |MINGW64 |<code>mingw-w64-x86_64-</code> |- |CLANG32 |None (environment fully deprecated)<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment Removal of the CLANG32 environment]</ref> |} == References == 9c44a97eaacbec637449decfa001e71679a42889 5988 5987 2026-08-10T16:22:42Z Imnotgoodatnames 121 slight package managment more info whatever wikitext text/x-wiki {{Work In Progress}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | caption = MSYS2 logo <!-- No logo here currently as the license of the MSYS2 logo is currently unclear. please don't try to add it until the license situation regarding it is cleared up. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://https://www.msys2.org// msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2 home page]</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?]</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 - MSYS2]</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64]</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by <ref name=envs>[https://www.msys2.org/docs/environments/ Environments - MSYS2]</ref> {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |UCRT64 |<code>/ucrt64</code> |gcc |UCRT |x86_64 |- |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS. It is always active, all other environments inherit from it and add their own environment variables on top. === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure compatibility with ARM, not to install an ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11 (#96) - MSYS2 Installer - Github issues ]</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue MSYS2 Packages]</ref> {| class="wikitable" !Environment !Package name prefix |- |MSYS |None (no package name prefix) |- |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |MINGW32 |<code>mingw-w64-</code> |- |MINGW64 |<code>mingw-w64-x86_64-</code> |- |CLANG32 |None (environment fully deprecated)<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment Removal of the CLANG32 environment]</ref> (historically <code>mingw-w64-clang-i686</code>)<ref>[https://www.msys2.org/docs/package-naming/ Package Naming - MSYS2]</ref> |} == References == bdf815e01134b85fff09f571ac510337dcc9f492 5990 5988 2026-08-10T18:10:05Z Imnotgoodatnames 121 Added icon, still no logo due to unclear licensing. will replace icon with logo if licensing issue gets resolved wikitext text/x-wiki {{Work In Progress}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | image = [[file:Msys2-icon.png|frameless|upright=0.5|MSYS2 icon]] | caption = MSYS2 icon <!-- Icon used instead of logo due to logo's unclear licensing. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://https://www.msys2.org// msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2 home page]</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?]</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 - MSYS2]</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64]</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by <ref name=envs>[https://www.msys2.org/docs/environments/ Environments - MSYS2]</ref> {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |UCRT64 |<code>/ucrt64</code> |gcc |UCRT |x86_64 |- |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS. It is always active, all other environments inherit from it and add their own environment variables on top. === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure compatibility with ARM, not to install an ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11 (#96) - MSYS2 Installer - Github issues ]</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue MSYS2 Packages]</ref> {| class="wikitable" !Environment !Package name prefix |- |MSYS |None (no package name prefix) |- |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |MINGW32 |<code>mingw-w64-</code> |- |MINGW64 |<code>mingw-w64-x86_64-</code> |- |CLANG32 |None (environment fully deprecated)<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment Removal of the CLANG32 environment]</ref> (historically <code>mingw-w64-clang-i686</code>)<ref>[https://www.msys2.org/docs/package-naming/ Package Naming - MSYS2]</ref> |} == References == 85c35a58d879799fed1440c7de6076b3d41b9b34 0 1417 5983 2026-08-10T12:13:01Z Lawl 419 trivalent page wikitext text/x-wiki {{Stub}} '''Trivalent''' is a security-focused, [[Chromium]]-based browser for desktop [[Linux]] inspired by [[GrapheneOS]]' [[Vanadium]] browser.<ref>[https://github.com/secureblue/Trivalent/blob/live/docs/README.md Github repository for Trivalent]</ref> Trivalent's primary focus is to achieve the security of [[Chromium]] based browsers, while removing telemetry and other tracking elements as well as including some patches to help secure the browser furthermore. It is the default browser on the [[Secureblue]] Linux distribution. == Features == * Contains numerous patches from the [[Vanadium]] browser designed to enhance security * Contains additional patches on top of the Vanadium patches and existing [[Chromium]] patches to enhance security * Automatic disabling of telemetry * Automatically opt-out of optional services included by default (e.g the password manager) * Simple and small UX changes which can be easily disabled == Privacy == Trivalent is ''not'' privacy focused. Instead, Trivalent's primary focus is security. This does mean that Trivalent may lack some features which give a benefit to privacy, but sell out on some security or do little to contribute to it. This only affects a tiny amount of changes, however, with most privacy-selling features disabled entirely. de48ece4176cb7d3fbe8cda6c64b74a6086e5906 0 1418 5984 2026-08-10T12:26:12Z Lawl 419 vanadium page wikitext text/x-wiki {{Stub}} {{Needs Citations}} '''Vanadium''' is a security and privacy enhanced [[Chromium]]-based browser for the [[GrapheneOS]] operating system, serving as the WebView implementation for rendering content within apps and also acting as the browser for the user. It features strong isolation, and utilizes numerous patches to help Vanadium achieve increased privacy and security for the user. Vanadium heavily relies on GrapheneOS' system-level patches to be able to utilize features which the browser requires features from the operating system to run, such as certain types of exploit mitigation. ## Features * Hardware memory tagging enabled for the main allocator * Type-based CFI (control flow integrity) * Hardened stack protector * Strict, hardened site isolation & sandboxing * Battery API giving deliberate incorrect information to avoid fingerprinting * Widely unused features such as WebGPU disabled to decrease attack surface * Client hints replaced with [[Chromium]]'s reduced user agent to prevent fingerprinting cd4646df3a3f790b0dbf6fcd6abcbf503a7bb158 5985 5984 2026-08-10T13:11:08Z Lawl 419 fix header wikitext text/x-wiki {{Stub}} {{Needs Citations}} '''Vanadium''' is a security and privacy enhanced [[Chromium]]-based browser for the [[GrapheneOS]] operating system, serving as the WebView implementation for rendering content within apps and also acting as the browser for the user. It features strong isolation, and utilizes numerous patches to help Vanadium achieve increased privacy and security for the user. Vanadium heavily relies on GrapheneOS' system-level patches to be able to utilize features which the browser requires features from the operating system to run, such as certain types of exploit mitigation. == Features == * Hardware memory tagging enabled for the main allocator * Type-based CFI (control flow integrity) * Hardened stack protector * Strict, hardened site isolation & sandboxing * Battery API giving deliberate incorrect information to avoid fingerprinting * Widely unused features such as WebGPU disabled to decrease attack surface * Client hints replaced with [[Chromium]]'s reduced user agent to prevent fingerprinting af8752ebe9705a012af105db800aa180cbbc55fd 0 569 5986 3583 2026-08-10T14:32:20Z Netcat 432 Fixed image dimensions, added citations and info wikitext text/x-wiki [[Category:Mascots]] {{MascotInfobox | title = Beastie | image = [[File:Daemon-phk.svg|frameless]] | caption = Beastie, the BSD daemon }} Beastie is the generic mascot of [[BSD]] operating systems, and the primary mascot of [https://freebsd.org/ FreeBSD]. Beastie is a red cartoon devil (daemon) who wears green sneakers and holds a yellow trident, which symbolises the forking of processes. He was designed by John Lasseter while working at Lucasfilm<ref name=":0">{{Cite|title=FreeBSD Day Interview with Beastie, the BSD Deamon|url=https://forums.freebsd.org/threads/freebsd-day-interview-with-beastie-the-bsd-deamon.93886/|author=FreeBSD Foundation|year=2024|accessdate=2026-08-10}}</ref>, however, the copyright is held by Marshall Kirk McKusick. == References == <references /> 844624d19beb4d28954d3d5af8d0d7591b3a5295 6 1419 5989 2026-08-10T18:05:22Z Imnotgoodatnames 121 = MIT LICENSE (can't select it from the licensing drop down menu = msys2.ico from github.com/msys2/msys2-launcher/blob/master/msys2.ico, converted to .png wikitext text/x-wiki == Summary == = MIT LICENSE (can't select it from the licensing drop down menu = msys2.ico from github.com/msys2/msys2-launcher/blob/master/msys2.ico, converted to .png d2e04b368ed59f1cd6a71002af7ab3b7f5d52758 0 622 5991 4863 2026-08-10T22:06:43Z Atmois 13 Remove template wikitext text/x-wiki A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:COSMIC Epoch 1.0.0 alpha with apps.png|[[COSMIC]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity Desktop Environment]] File:XFCE-4.18-Desktop.png|[[Xfce]] File:LXDE-Qt preview.png|[[LXDE]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment originally based on GNOME 3, developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[COSMIC]] |[[COSMIC]] is a Desktop Environment developed by [[system76]], also known as the creators of [[Pop! OS|Pop! OS.]] COSMIC is built in [[Rust]] and is notable for having automatic window tiling built into the desktop as a primary feature. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in a variety of languages, but primarily is built in [[C]]. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[Xfce]] |[[Xfce]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} e0c3bfa46f1ba8c9022f2e5ff01b1285cf607536 14 390 5992 5697 2026-08-10T22:10:03Z Atmois 13 Merge project rows wikitext text/x-wiki == FOSS Mascots == The lists below do not show every mascot for FOSS software in existence, instead the most popular mascots for the most popular software are listed. If you want an extensive list of all computer mascots, non FOSS included please refer to https://en.wikipedia.org/wiki/List_of_computing_mascots ==== Distribution Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:OpenSUSE Button.svg|alt=A vector graphic of a green lizard|frameless|64x64px]] |[[Geeko]] |[[OpenSUSE]] |- |[[File:Larry-nefarius-v2.svg|alt=A drawing of a white cow with brown feet|frameless|64x64px]] |[[Larry the Cow]] |[[Gentoo]] |- |[[File:Daemon-phk.svg|alt=A vector graphic of a cartoon red devil wearing shoes and holding a pitchfork|frameless|70x70px]] |[[Beastie|Daemon]] |[[BSD]] |- |[[File:Heckert GNU white.svg|alt=A vector graphic of a black and white drawing of a wildebeest|frameless|64x64px]] |[[Gnu]] |[[GNU]] |- |[[File:Puffy-openbsd.gif|alt=A drawing of a smug yellow puffer fish with human like lips|frameless|64x64px]] |[[Puffy]] |[[OpenBSD]] |- |[[File:FedoraGreenPanda.png|alt=a drawing of a panda with green ears and eyes and a green symbol on its belly|frameless|101x101px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_panda Panda] | rowspan="4" |[https://fedoraproject.org/ Fedora] |- |[[File:FedoraBadger.png|alt=a badger with a red sash wearing shades|frameless|65x65px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_badger Badger] |- |[[File:FedoraBeefy.png|alt=a hot dog with white gloves and a face pointing|frameless|105x105px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_beefy Beefy] |- |[[File:FedoraColur.png|alt=a rainbow bird|frameless|127x127px]] |[https://docs.fedoraproject.org/en-US/project/brand/#_col%C3%BAr Colúr] |} ==== Desktop Environment Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:KDE_Mascot_Konqi_by_Tyson_Tan.png|alt=A vector graphic of a green dragon standing on its back legs pointing its finger|center|frameless|92x92px]] |[[Konqi]] | rowspan="3" |[[Plasma|KDE Plasma]] |- |[[File:KDE_women_mascot_Katie_development_cropped_by_Tyson_Tan.png|alt=A vector graphic of a light green dragon sitting using a laptop, with if< on the screen|center|frameless|90x90px]] |[[Katie]] |- |[[File:Mascot KDE Kori.png|alt=A cartoon anthropomorphic teal dragon wearing a blue scarf with the letter K|frameless|120x120px]] |[[Kori]] |- |[[File:Mascot XFCE Xue.svg|alt=A drawing of a black rat|frameless|120x120px]] |[[Xue]] |[[XFCE]] |} ==== Linux Kernel Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Tux.svg|alt=A drawing of a penguin sitting|frameless|76x76px]] |[[Tux]] |[[Linux]] |- |[[File:Tuz-logo.svg|alt=A drawing of a Tasmanian devil wearing a fake penguin beak,|frameless|76x76px]] |[[Taz]] | rowspan="2" |[[Linux]] (Unoffical) |- |[[File:Xenia the Linux Fox.gif|alt=A drawing of a human male shaped orange fox wearing sunglasses and a black tshirt that reads "Linux"|frameless|120x120px]] |[[Xenia]] |} ==== Program Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:Wilber-big.png|frameless|90x90px]] |[[Wilber]] |[https://www.gimp.org GIMP] |- |[[File:Kiki.png|frameless|120x120px]] |[https://krita.org/en/about/mascot/ KiKi] |[https://krita.org Krita] |} ==== Other Projects Mascots ==== {| class="wikitable" !Image !Mascot !Project related to |- |[[File:415656095680e1c6138277b0ba27e212.png|frameless|64x64px]] |[[Talia]] |[https://www.noctalia.dev Noctalia] |- |[[File:Sudo-sandwich-logo-65.png |frameless|64x64px]] |[[Sudo Sandwich]] |[https://www.sudo.ws Sudo] |- |[[File:Plan9 Bunny.png|alt=The rabbit mascot of Plan 9 from Bell Labs.|frameless|64x64px]] |[[Glenda]] |[[Plan 9 from Bell Labs]] |} 9654ccafa7326aadc9905253e5cb84e71aa4fcf4 0 791 5993 3209 2026-08-10T22:22:12Z Atmois 13 Start content wikitext text/x-wiki {{Work In Progress}} Marked as WIP as defining how to categorise languages. Ideas include paradigm and primary use case, former option is a bit less debated but less accessible to a newer programmer and the latter makes the purposes clear but a lot of languages blur the lines. c08aee010d1d2e8a23742c5adeeddbba250057f0 0 1 5994 4618 2026-08-10T22:22:41Z Atmois 13 Update about wikitext text/x-wiki __NOTOC__ <div class="content-section full-width"> <center> <div class="home-header"> <div class="home-header-subtitle">Welcome to</div> <h1 class="home-header-title">FOSS Wiki</h1> <div class="home-header-subtitle">A comprehensive wiki for Free and Open Source Software and Linux related topics.</div> </div> <div class="button-container"> [[FW:Contributing|<span class="home-button">✍️ How to Contribute</span>]] [[FW:Guidelines|<span class="home-button">📋 Wiki Guidelines</span>]] [[:Category:Pages Needing Cleanup|<span class="home-button">🛠 Pages Needing Help</span>]] [[Guides:Contributing|<span class="home-button">📖 Guides Policies</span>]] <span class="home-button">[https://discord.foss.wiki 💬 Our Discord Server]</span> </div> {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! <blockquote><small>"The most valuable wealth of humanity is its knowledge, which cannot be destroyed; all other riches that we have gained are not considered to be wealth at all."</small></blockquote></center></div> <div class="content-section full-width"> <div class="content-header">Categories</div> <center> <div class="button-container"> [[Desktop Environments|<span class="home-button blue">💻 Desktop Environments</span>]] [[Linux Distributions|<span class="home-button green">🐧 Linux Distributions</span>]] [[Guides:Guides|<span class="home-button orange">📘 Guides</span>]] [[Software|<span class="home-button purple">🧩 Software</span>]] [[Package Managers|<span class="home-button teal">📦 Package Managers</span>]] [[Mascots|<span class="home-button pink">🐧 Mascots</span>]] [[Terminology|<span class="home-button yellow">🔤 Terminology</span>]] [[Misc Operating Systems|<span class="home-button gray">🌐 Misc Operating Systems</span>]] [[Programming Languages|<span class="home-button red">💻 Programming Languages</span>]] [[Wayland Compositors|<span class="home-button cyan">🌊 Wayland Compositors</span>]] [[X Window Managers|<span class="home-button indigo">🪟 X Window Managers</span>]] </div> </center> </div> <div class="content-grid"> <div class="content-section"> <div class="content-header">About</div> '''FOSS Wiki''' is a centralised, easy-to-use reference for the FOSS and Linux ecosystem that provides clear overviews and practical guides for all users! Rather than replacing pre-existing documentation and wiki's, we aim to complement them by connecting concepts across distributions and tools as well as highlighting essential references and best practices. You can see more about what content is suitable for the wiki in the [[FW:Guidelines#Notability Standards|guidelines]]. You can learn more about our wiki, its history and its staff on the [[FW:About|about page]]. We hope to see you join us in making the wiki a great resource for all users, with your help we can achieve greatness! ====== Wiki Support ====== If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on our [https://discord.foss.wiki Discord server]! To contact the administrators, you can open a ticket with <code>/ticket</code> on the Discord or email an administrator via the emails listed on the [[FW:Contact|contact page]]. You can read more about the project's goals and the history of the wiki on the [[FW:About|about]] page! </div> <div class="content-section"> <div class="content-header">How to Help</div> '''Don't be afraid to edit''' - ''anyone'' can edit almost every page. If you see something that could be improved, you can go and fix it! You can add content, upload freely licensed images, check that pages meet the guidelines, or improve the prose to make articles easier to read. ====== How to Start Editing ====== The best place to start is the [[FW:Contributing|Contributing Guide]], it's fine if you are overwhelmed or don't know where to start, but don't worry if you don't understand everything at first. * Review the [[FW:Guidelines|guidelines]] page and the [[FW:Code of Conduct|Code of Conduct]] as they contain the standards and policies of the wiki. * For users new to Mediawiki check out the [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] for how Mediawiki markup works. * Pages in need of edits can be found on [[:Category:Needs Citations]] or [[:Category:Pages Needing Cleanup]]. * Look for pages which may need improvement on the [[Special:RecentChanges|recent changes]] log. * Check out [[Special:WantedPages]] for the most linked-to pages which don't exist. If you're ever stuck for what to edit or how you can help, you can always check out our [https://discord.foss.wiki Discord Server], where there will always be someone happy to help you get editing! </div> <div class="content-section full-width"> <div class="content-header">Our Key Values</div> '''FOSS Wiki''' has 4 key values which underpins everything we do on the wiki and its guidelines, if anything remember these values when editing the wiki. # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. </div> <div class="content-section full-width"> <div class="content-header">[[Special:RecentChanges|Recent Activity]]</div>{{Special:RecentChanges|hidebots|namespace=0|limit=10}}</div> </div> 084dad2679de9b285aef84eee954ac31d26135c6 4 556 5995 5570 2026-08-10T22:23:49Z Atmois 13 Update information wikitext text/x-wiki == <u>About</u> == {{#invoke:StatsLine|stats}} Join the numbers and go contribute to make improve the wiki for everyone! '''FOSS Wiki''' is a wiki centred around providing reliable and informative resources to users of all ability levels of FOSS and Linux adjacent software through information pages, guides, indexes and more! If you need wiki support, have any queries or wish to report something, check out the <code>#wiki</code> channel on the [https://discord.foss.wiki Discord server]! To contact the administrators, check out our [[FW:Contact|contact page]]! We have 4 key values for FOSS Wiki, that summarise all of our [[guidelines]]: # '''Accuracy:''' Content should be up-to-date and high quality and should strive to follow the [[FW:Guidelines|Guidelines]]. # '''Courtesy:''' Editors should be respectful to other users and work together to make an amazing resource, and always act in good faith. # '''Impartiality:''' Content should always be unbiased to avoid misleading users and advocacy. # '''Accessibility:''' Content should be written so that any user of any ability can understand and make use of it. == <u>Important Links</u> == * [[FW:Code of Conduct|Code of Conduct]] - Outlines the expected behaviour of users and contributors alike * [[Guidelines]] - Outlines the style guidelines and values of FOSS Wiki * [[Contributing]] - Outlines how YOU can contribute to FOSS Wiki * [[FW:Privacy Policy|Privacy Policy]] - The privacy policy of FOSS Wiki * [[FW:Disclaimer|Disclaimer]] - FOSS Wiki Editing Disclaimer == <u>Wiki Staff</u> == ====== Leadership ====== * [[User:Atmois|Atmois]] - Wiki Director ====== Stewards ====== * [[User:Ow0cast|Ow0cast]] * [[User:Madonuko|Madonuko]] == '''<u>History</u>''' == === <u>Independence</u> ~ ''April 2026 - Present'' === '''May 2026''' We obtained the '''atl.wiki''' domain to act as a redirect to our new domain alongside doing some much needed improvements to the infrastructure to improve database backup resilience and improved our [[FW:Privacy Policy]] further with the new changes. We also opened up [https://donate.foss.wiki donations] via Open Collective to allow for quicker and larger improvements to the wiki utilising an independent bank and stripe accounts. Alongside this, [https://fibery.io Fibery] generously provided us an unlimited pro plan for the wiki! With this we setup a public [https://open.foss.wiki Ledger and Roadmap] which on it you can see exactly what we are planning and spending money on to keep the wiki running. On the 22nd of May we did our launch party, with the support of over half a dozen other communities we pushed the wiki into a new era. We welcomed almost 100 new editors helping to make over 500 new edits to the wiki in the week following the launch. We also grew the wiki team with [[User:Madonuko]] (with their nifty bot [[User:Hamachitan]]) join us! After the launch party thanks to donations from [[User:Scottc96]] and [[User:Wilbur]], we were able to provision a second VPS to host the wiki's database separately and to provide redundancy. Alongside this we implemented daily, immutable and encrypted backups of the database to a secure S3 bucket to ensure the data is securely backed up to protect the wiki. '''April 2026''' After the dissolution of All Things Linux, the wiki was branched off (utilising the old wiki's database) into its own project run by the director, [[User:Atmois|Atmois]] as an independent project. The wiki kept its goals and standards but just re-branded to the '''FOSS Wiki''' using the nifty domain '''''foss.wiki'''''! [[User:Ow0cast|Ow0cast]] and [[User:Scottc96|Scott96]] (promoted to co-director) remained part of the Wiki team and we redeployed the wiki within 2 weeks ready for editing. With the relaunch we setup of our status page with Phare at [https://status.foss.wiki status.foss.wiki] and launched our own [https://discord.foss.wiki Discord Server] and partnered with [https://discord.gg/nglinux Neon Genesis Linux], a server run by [[User:Scottc96|Scott96]] to provide high quality FOSS/Linux support and discussions. Our wiki deployment code is available on our new [https://github.foss.wiki GitHub] and we redeployed Umami analytics and updated our [[FW:Privacy Policy|Privacy Policy]] to clarify some unclear data retention details as well as provide Opt Out information for Umami if users with to not be included in wiki usage analytics. ''Finally, we thank everyone who stuck with us especially former ATL staff for all their support and kindness during these tough times, every edit and every bit of support is valued and I am eternally grateful for everyone's help to make this fantastic resource for FOSS/Linux users, thank you and I hope to see you editing with us in the future! ~ atmois'' === <u>ATL Ownership</u> ~ ''May 2024 - March 2026'' === ===== August 2025 ===== In the past few months went silent as we did a lot of changes to improve the wiki. Starting by restructuring our internal systems to allow for a staging wiki to be setup to avoid testing Mediawiki Configuration changes on the live wiki, migrating to NGINX for faster and simpler performance, refined our Privacy Policy to be more transparent about our systems, expanded our guidelines, redesigned our home page from scratch and so much more that make every little bit of the wiki a better experience for both editors and users. to be added: DDoS report, 1.0 release and wikibot launch ===== April 2025 ===== The month started with an enormous overhaul to the entire setup, we reinstalled Mediawiki, separated the database to its own, more secure and resilient server, planned cleaner updates and setup following the best practises for Mediawiki. We now had a more long-term ready and maintainable setup ready for 1.0, we also set up Short URL properly to have our pages on the root and properly setup SEO and finalised most of our policies to be up to scratch. We had our official launch of [[Guides:Contributing|Guides]] with already a small group of editors dedicated to writing them out of the box and wrote some new policies for it as well as finalise the goals for 1.0. Furthermore, we had some amazing support from the community in brainstorming what we could do to make the wiki an amazing resource for all users of all ability levels and established our [[FW:Guidelines|key values of the wiki]], Accuracy, Impartiality, Consistency, Courtesy and Accessibility. To end an already booming month, we had a mention on Brodie Robertson's channel<ref>[https://www.youtube.com/watch?v=jxhMA0G2_MA&t=600 Useful Resources Every New Linux User Needs], Brodie Robertson, 2025 (Retrieved 1st May 2025)</ref> bring an amazing influx of new editors from all backgrounds to the wiki to help make the content even better. ===== February 2025 ===== We entirely reworked our internal systems in order to allow easier long-term maintenance, as well as working on some issues with our skins. We also started work on templates and cleaning up loose ends on content ready for 1.0 to make the cleanest experience possible for users. Shortly after we then ran another re-licencing effort as we realised in retrospect the original decision was poorly made and rushed, however we rectified it through a formal discussion and form to comply with the licence and to allow the maximum freedom of the content on the wiki whilst protecting our editors. We now are fully licensed under [https://creativecommons.org/licenses/by-sa/4.0/deed.en CC BY-SA 4.0] and are confident in this decision as the best for both editors and readers alike. To end the month, we removed Moderation to re-add ApprovedRevs only on our, at the time planned, [[Guides:Contributing|Guides]] section of the wiki. This was done as we were confident on our ability to combat misinformation and spam effectively with our growing user base. We also resolved the issues with our skins and began work on most of our policies and essential documentation. ===== January 2025 ===== In the new year, we started planning our proper full release of the wiki, titled internally as "1.0". We started off with setting up SSO for our staff team and worked on resolving some long-standing bugs. We also changed our update policy to LTS updates only with an update to Mediawiki 1.43 and worked with editors to make the wiki a better experience for users and editors alike. ===== November 2024 ===== We migrated from ApprovedRevs to Moderation to reduce the complexity of the system for page reviews and upgraded to Mediawiki 1.42.3 as well as cleaning up our backend from a messed up install. We also added some nice extensions for logged-in users, such as [[mediawikiwiki:Extension:Favorites|favourites]] and TOTP 2FA. After some internal discussion, we decided to ask our community what they thought of our usage of the [https://creativecommons.org/licenses/by/4.0/ CC BY] licence for the wiki content. After a short vote, it was decided to re-licence the content to [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA]. We also required email confirmation for all users to combat spam on the wiki. To end up the month, [[User:Atmois|Atmois]] was assigned to lead the wiki project. Their primary assignment was to prepare the wiki for a proper release and get it up to scratch with the best practises and learn the ins and outs of Mediawiki to most effectively use it, the next month consisted of a lot of planning and internal reworks. ===== October 2024 ===== After a few quiet months of slow growth, [[User:Atmois|Atmois]] was recruited to help administrate and manage the wiki. With some amazing help from a system-administrator at [https://weirdgloop.org Weird Gloop] (The hosts of the [https://minecraft.wiki Minecraft] and [https://runescape.wiki Runescape] wiki's) we planned the next steps for the wiki. We opened registration to all users and implemented some started work on our guidelines and policies! We had a small wave of spam-bots which we quickly resolved by implementing [https://www.cloudflare.com/application-services/products/turnstile/ Cloudflare Turnstile] on signup, which entirely removed the issue. As we had low moderation capabilities, we enabled ApprovedRevs across the whole wiki and granted all existing editors approving permissions as a thank you for their work. We reworked our [[Main Page|main page]] to remove the dynamic list of all pages as we neared almost 75 pages with almost 1000 edits, we also re-implemented drafts and cleaned up our automated systems on the wiki to prepare for some large scale internal changes. ===== June 2024 ===== We obtained the domain '''atl.wiki''' and set up the server for the wiki! Accounts began as invite only for trusted members of the ATL Discord. Electron271, Green and [[User:Scottc96|Scott96]] were chosen the initial team behind running and maintaining the wiki, led by the Owner of ATL, Kaizen. We set up a dedicated section of our discord to run the wiki from and had just 10 editors starting work on the wiki, we also set up a variety of themes and choose [https://github.com/starCitizenTools/mediawiki-skins-Citizen/ Citizen] as our default theme due to its modern feel compared to the default skins. After suffering some DDoS attacks, we officially launched the wiki! We then hit 250 edits, our first significant milestone, and had almost 25 pages! We opened up registration further to most members within All Things Linux on an open request basis. ===== May 2024 ===== The initial plans were made for starting the wiki in the Discord Server, [https://mediawiki.org Mediawiki] was chosen as the software for being the most extensible and powerful of the choices available. Discussions were held on what the goals of the wiki should be and what content should be included on the wiki. == The Future == Thank you for everyone who has or will contribute to the wiki, we appreciate it more than you can think, as the wiki would not be here without you all. We hope you found the content on the wiki useful, or even yourself want to contribute, we are always happy to welcome new faces. To a prosperous future for the wiki, we hope to see you there with us. - [[User:Atmois|atmois]] 730035b335b56ecaffa335321b8c9526d5de1f18 4 595 5996 5571 2026-08-10T22:24:09Z Atmois 13 Update information wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.foss.wiki Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all staff at once please email: ''team(at)foss.wiki'' ~ To report security vulnerabilities please see our [[FW:Security|Security Policy]]. [[User:Atmois|Atmois]] - Wiki Director ''- zoe.m(at)foss.wiki'' [[User:Ow0cast|Ow0cast]] - Wiki Steward - ''nikki.k(at)foss.wiki'' [[User:Madonuko|Madonuko]] - Wiki Steward - ''mado.n(at)foss.wiki'' c4f53bb000e5280d4f2776a1b9f196d01155d24f 0 1420 5997 2026-08-11T00:55:35Z Uniolo 345 Create PhotoRec with some basic information, might expand later. wikitext text/x-wiki {{SoftwareInfobox | image = [[File:PhotoRec Logo.svg|thumb]] | caption = PhotoRec | title = PhotoRec | releasestatus = Maintained | lastrelease = 7.2, Feb 22, 2024 | languages = [[C]] | developers = Christophe GRENIER | website = [https://www.cgsecurity.org/wiki/PhotoRec cgsecurity.org/wiki/PhotoRec] | license = GPL-2.0 license | sourcecode = https://github.com/cgsecurity/testdisk }} [[Category:Software]] {{stub}} '''PhotoRec''' is a tool made by cgsecurity for recovering permanently deleted files on a variety of operating systems and file systems. It uses a [[TUI]] and supports a [https://www.cgsecurity.org/wiki/File_Formats_Recovered_By_PhotoRec wide range of different files]. It shares some of its source code and a git repo with [[TestDisk]]. 67e6405c4eb19b48806ddff454c2ddd966edf602 5999 5997 2026-08-11T01:13:19Z Uniolo 345 Added note about it going after underlying data wikitext text/x-wiki {{SoftwareInfobox | image = [[File:PhotoRec Logo.svg|thumb]] | caption = PhotoRec | title = PhotoRec | releasestatus = Maintained | lastrelease = 7.2, Feb 22, 2024 | languages = [[C]] | developers = Christophe GRENIER | website = [https://www.cgsecurity.org/wiki/PhotoRec cgsecurity.org/wiki/PhotoRec] | license = GPL-2.0 license | sourcecode = https://github.com/cgsecurity/testdisk }} [[Category:Software]] {{stub}} '''PhotoRec''' is a tool made by cgsecurity for recovering permanently deleted files on a variety of operating systems, it ignores the file system and uses the underlying data<ref>{{Cite|url=https://www.cgsecurity.org/wiki/PhotoRec|title=cgsecurity wiki, PhotoRec|year=21 May 2023|accessdate=2026-08-10}}</ref>. It uses a [[TUI]] and supports a [https://www.cgsecurity.org/wiki/File_Formats_Recovered_By_PhotoRec wide range of different files]. It shares some of its source code and a git repo with [[TestDisk]]. 8049c645b1d4c45981b0c9048187e28954645ed4 6000 5999 2026-08-11T01:17:58Z Uniolo 345 Added note about its inclusion with Kali Linux (not where I found it BTW) wikitext text/x-wiki {{SoftwareInfobox | image = [[File:PhotoRec Logo.svg|thumb]] | caption = PhotoRec | title = PhotoRec | releasestatus = Maintained | lastrelease = 7.2, Feb 22, 2024 | languages = [[C]] | developers = Christophe GRENIER | website = [https://www.cgsecurity.org/wiki/PhotoRec cgsecurity.org/wiki/PhotoRec] | license = GPL-2.0 license | sourcecode = https://github.com/cgsecurity/testdisk }} [[Category:Software]] {{stub}} '''PhotoRec''' is a tool made by cgsecurity for recovering permanently deleted files on a variety of operating systems, it ignores the file system and uses the underlying data<ref>{{Cite|url=https://www.cgsecurity.org/wiki/PhotoRec|title=cgsecurity wiki, PhotoRec|year=21 May 2023|accessdate=2026-08-10}}</ref>. It uses a [[TUI]] and supports a [https://www.cgsecurity.org/wiki/File_Formats_Recovered_By_PhotoRec wide range of different files]. It shares some of its source code and a git repo with [[TestDisk]]. It is included with [[Kali Linux]]<ref>{{Cite|url=https://www.kali.org/tools/|title=Kali Tools|author=OffSec Services|year=2026|accessdate=2026-08-10}}</ref>. 8cf73304402ea3020104106f06580439196f8d06 0 1421 5998 2026-08-11T00:55:46Z Uniolo 345 Redirect to PhotoRec since mediawiki is case sensitive wikitext text/x-wiki #redirect [[PhotoRec]] ac3264a64786521578b34511bcb6456abf6b2ca5 2 805 6001 3574 2026-08-11T22:32:22Z Ow0cast 249 wikitext text/x-wiki {{#ifeq: $2 | Tor Endpoint | <strong>To prevent abuse, Tor users cannot edit the Wiki.</strong> | <strong>Your username or IP address has been blocked.</strong> {{int:blockedtext-made-by|$1}} {{int:blockedtext-reason-comment|$2}} * {{int:blockedtext-start-time|$8}} * {{int:blockedtext-expiration-time|$6}} * {{int:blockedtext-intended-blockee|$7}} {{int:blockedtext-contact-blocker-admin|$1}} You can use the "{{int:emailuser}}" feature if a valid email address is specified in your [[Special:Preferences|preferences]] and you have not been blocked from using it. {{int:blockedtext-block-ip|$3}} {{int:blockedtext-block-id|$5}} {{int:blockedtext-include-details-queries}} }} b392b030ce8b6c1062b9a3c004c461675b4efc25 8 1422 6002 2026-08-11T23:50:04Z Atmois 13 Update info wikitext text/x-wiki {{#ifeq: $2 | Tor Endpoint | <strong>To prevent abuse, Tor users cannot edit the Wiki.</strong> | <strong>Your username or IP address has been blocked.</strong> {{int:blockedtext-made-by|$1}} {{int:blockedtext-reason-comment|$2}} * {{int:blockedtext-start-time|$8}} * {{int:blockedtext-expiration-time|$6}} * {{int:blockedtext-intended-blockee|$7}} {{int:blockedtext-contact-blocker-admin|$1}} You can use the "{{int:emailuser}}" feature if a valid email address is specified in your [[Special:Preferences|preferences]] and you have not been blocked from using it. {{int:blockedtext-block-ip|$3}} {{int:blockedtext-block-id|$5}} {{int:blockedtext-include-details-queries}} }} b392b030ce8b6c1062b9a3c004c461675b4efc25 0 1382 6003 5846 2026-08-12T13:00:04Z Imnotgoodatnames 121 Create dedicated FreeDOS page, infobox, screenshot, stub. More coming eventually. wikitext text/x-wiki {{stub}} {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG<ref>[https://opensource.com/article/21/6/freedos-package-manager Install and remove software packages on FreeDOS]</ref><ref>[https://fdnpkg.sourceforge.net/ FDNPKG - a network-enabled package manager for FreeDOS]</ref> | defaultdesktops = [[CLI|Command line interface]] | usagetype = Desktop | architectures = IA-16, i386<ref>[https://github.com/FDOS/kernel/blob/d6791add2043c9d7b584d840a8ffaf8829fd2bdc/config.m#L57 kernel/config.m - FDOS/Kernel - Github]</ref> | website = [http://freedos.org freedos.org] }} [[File:FreeDOS_1.1_screenshot.png|thumb|FreeDOS command prompt]] '''FreeDOS''' is a [[FOSS|free]] [[DOS (x86 operating system)|DOS]] operating system developed as an open-source and fully compatible alternative to [[MS-DOS]]. The project started as PD-DOS in 1994, when Microsoft announced it would no longer be developing MS-DOS as an independent operating system but rather as the core component of [[Windows|Windows 95]].<ref>[https://www.freedos.org/about/ About FreeDOS]</ref> FreeDOS is the oldest known open-source DOS as well as one of the few remaining operating systems capable of booting on the original 16-bit x86 processors such as the Intel 8086. It is the only major DOS still in active development. == References == c09b918d26e185f4fb21625de10a4672cdacf294 6005 6003 2026-08-12T13:08:29Z Imnotgoodatnames 121 Category, Blinky. wikitext text/x-wiki {{stub}} [[Category:Misc Operating Systems]] {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = Blinky, the FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG<ref>[https://opensource.com/article/21/6/freedos-package-manager Install and remove software packages on FreeDOS]</ref><ref>[https://fdnpkg.sourceforge.net/ FDNPKG - a network-enabled package manager for FreeDOS]</ref> | defaultdesktops = [[CLI|Command line interface]] | usagetype = Desktop | architectures = IA-16, i386<ref>[https://github.com/FDOS/kernel/blob/d6791add2043c9d7b584d840a8ffaf8829fd2bdc/config.m#L57 kernel/config.m - FDOS/Kernel - Github]</ref> | website = [http://freedos.org freedos.org] }} [[File:FreeDOS_1.1_screenshot.png|thumb|FreeDOS command prompt]] '''FreeDOS''' is a [[FOSS|free]] [[DOS (x86 operating system)|DOS]] operating system developed as an open-source and fully compatible alternative to [[MS-DOS]]. The project started as PD-DOS in 1994, when Microsoft announced it would no longer be developing MS-DOS as an independent operating system but rather as the core component of [[Windows|Windows 95]].<ref>[https://www.freedos.org/about/ About FreeDOS]</ref> FreeDOS is the oldest known open-source DOS as well as one of the few remaining operating systems capable of booting on the original 16-bit x86 processors such as the Intel 8086. It is the only major DOS still in active development. == References == 1bc8200baea1619638eab9fc6ed42a2225c52266 6007 6005 2026-08-12T17:41:47Z Imnotgoodatnames 121 Added more info on package managment, desktops etc., refs, screenshots.... wikitext text/x-wiki {{stub}} [[Category:Misc Operating Systems]] {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = Blinky, the FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG<ref>[https://opensource.com/article/21/6/freedos-package-manager Install and remove software packages on FreeDOS]</ref><ref>[https://fdnpkg.sourceforge.net/ FDNPKG - a network-enabled package manager for FreeDOS]</ref> | defaultdesktops = [[CLI|Command line interface]] OpenGEM (optional) | usagetype = Desktop | architectures = IA-16, i386<ref>[https://github.com/FDOS/kernel/blob/d6791add2043c9d7b584d840a8ffaf8829fd2bdc/config.m#L57 kernel/config.m - FDOS/Kernel - Github]</ref> | website = [http://freedos.org freedos.org] }} [[File:FreeDOS_1.1_screenshot.png|thumb|FreeDOS command prompt]] '''FreeDOS''' is a [[FOSS|free]] [[DOS (x86 operating system)|DOS]] operating system developed as an open-source and fully compatible alternative to [[MS-DOS]]. The project started as PD-DOS in 1994, when Microsoft announced it would no longer be developing MS-DOS as an independent operating system but rather as the core component of [[Windows|Windows 95]].<ref>[https://www.freedos.org/about/ About FreeDOS]</ref> FreeDOS is the oldest known open-source DOS as well as one of the few remaining operating systems capable of booting on the original 16-bit x86 processors such as the Intel 8086. It is the only major DOS still in active development. == Compatibility == FreeDOS is almost fully compatible with MS-DOS command syntax, software and drivers. It's able to run nearly all programs built for MS-DOS, including early, pre-95 versions of Microsoft Windows and other DOS graphical environments, such as OpenGEM. It can also utilize DPMIs and DOS Extenders to run 32-bit software, including DOS builds of [[Bash]] and other GNU and UNIX software compiled with [[DJGPP]]. == Environment == [[File:VirtualBox_FreeDOS_1.3_22_11_2023_15_49_13.png|thumb|The OpenGEM graphical shell running on FreeDOS]] The basic FreeDOS environment consists of the FreeDOS kernel, <code>KERNEL.SYS</code>, a command interpreter ([[shell]]), which is automatically ran by the kernel on startup, and any installed packages. The default FreeDOS shell, FreeCom, is installed on the system to <code>\COMMAND.COM</code> for MS-DOS compatibility. It is fully compatible with MS-DOS and PC DOS COMMAND.COM shells. Alternate shells, like <code>bash.exe</code>, can be used with the <code>SHELL</code> and <code>SHELLHIGH</code> options in the FreeDOS configuration file <code>\CONFIG.SYS</code> or <code>FDCONFIG.SYS</code>.<ref>[https://www.freedos.org/books/get-started/9-fdconfig-sys/ How to configure FreeDOS with FDCONFIG.SYS]</ref> Graphical environments, like as OpenGEM, can also be installed from the FreeDOS setup CDs. == Package Managment == [[File:Fdimples.png|thumb|The FDIMPLES package manager]] Unlike traditional DOS implementations, FreeDOS has a full-featured [[TUI]] package manager, FDIMPLES, used to install software from a FreeDOS CD to disk.<ref>[https://www.freedos.org/books/get-started/10-using-fdimples/ How to install and remove packages with FDIMPLES]</ref> The '''FDNPKG''' package manager is installed using FDIMPLES and is a [[CLI]] package manager capable of installing software remotely over the internet. == References == 3c5a770e53f67cf211dbdc2f103194662f05c17d 6008 6007 2026-08-12T17:42:15Z Imnotgoodatnames 121 Removed stub thing wikitext text/x-wiki [[Category:Misc Operating Systems]] {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = Blinky, the FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG<ref>[https://opensource.com/article/21/6/freedos-package-manager Install and remove software packages on FreeDOS]</ref><ref>[https://fdnpkg.sourceforge.net/ FDNPKG - a network-enabled package manager for FreeDOS]</ref> | defaultdesktops = [[CLI|Command line interface]] OpenGEM (optional) | usagetype = Desktop | architectures = IA-16, i386<ref>[https://github.com/FDOS/kernel/blob/d6791add2043c9d7b584d840a8ffaf8829fd2bdc/config.m#L57 kernel/config.m - FDOS/Kernel - Github]</ref> | website = [http://freedos.org freedos.org] }} [[File:FreeDOS_1.1_screenshot.png|thumb|FreeDOS command prompt]] '''FreeDOS''' is a [[FOSS|free]] [[DOS (x86 operating system)|DOS]] operating system developed as an open-source and fully compatible alternative to [[MS-DOS]]. The project started as PD-DOS in 1994, when Microsoft announced it would no longer be developing MS-DOS as an independent operating system but rather as the core component of [[Windows|Windows 95]].<ref>[https://www.freedos.org/about/ About FreeDOS]</ref> FreeDOS is the oldest known open-source DOS as well as one of the few remaining operating systems capable of booting on the original 16-bit x86 processors such as the Intel 8086. It is the only major DOS still in active development. == Compatibility == FreeDOS is almost fully compatible with MS-DOS command syntax, software and drivers. It's able to run nearly all programs built for MS-DOS, including early, pre-95 versions of Microsoft Windows and other DOS graphical environments, such as OpenGEM. It can also utilize DPMIs and DOS Extenders to run 32-bit software, including DOS builds of [[Bash]] and other GNU and UNIX software compiled with [[DJGPP]]. == Environment == [[File:VirtualBox_FreeDOS_1.3_22_11_2023_15_49_13.png|thumb|The OpenGEM graphical shell running on FreeDOS]] The basic FreeDOS environment consists of the FreeDOS kernel, <code>KERNEL.SYS</code>, a command interpreter ([[shell]]), which is automatically ran by the kernel on startup, and any installed packages. The default FreeDOS shell, FreeCom, is installed on the system to <code>\COMMAND.COM</code> for MS-DOS compatibility. It is fully compatible with MS-DOS and PC DOS COMMAND.COM shells. Alternate shells, like <code>bash.exe</code>, can be used with the <code>SHELL</code> and <code>SHELLHIGH</code> options in the FreeDOS configuration file <code>\CONFIG.SYS</code> or <code>FDCONFIG.SYS</code>.<ref>[https://www.freedos.org/books/get-started/9-fdconfig-sys/ How to configure FreeDOS with FDCONFIG.SYS]</ref> Graphical environments, like as OpenGEM, can also be installed from the FreeDOS setup CDs. == Package Managment == [[File:Fdimples.png|thumb|The FDIMPLES package manager]] Unlike traditional DOS implementations, FreeDOS has a full-featured [[TUI]] package manager, FDIMPLES, used to install software from a FreeDOS CD to disk.<ref>[https://www.freedos.org/books/get-started/10-using-fdimples/ How to install and remove packages with FDIMPLES]</ref> The '''FDNPKG''' package manager is installed using FDIMPLES and is a [[CLI]] package manager capable of installing software remotely over the internet. == References == a00a2518103bfe1ce7da6162f9fa7848cb55b6fc 6009 6008 2026-08-13T08:45:22Z Imnotgoodatnames 121 Minor adjustements wikitext text/x-wiki [[Category:Misc Operating Systems]] {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = Blinky, the FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG<ref>[https://opensource.com/article/21/6/freedos-package-manager Install and remove software packages on FreeDOS]</ref><ref>[https://fdnpkg.sourceforge.net/ FDNPKG - a network-enabled package manager for FreeDOS]</ref> | defaultdesktops = [[CLI|Command line interface]] OpenGEM (optional) | usagetype = Desktop | architectures = IA-16, i386<ref>[https://github.com/FDOS/kernel/blob/d6791add2043c9d7b584d840a8ffaf8829fd2bdc/config.m#L57 kernel/config.m - FDOS/Kernel - Github]</ref> | website = [http://freedos.org freedos.org] }} [[File:FreeDOS_1.1_screenshot.png|thumb|FreeDOS command prompt]] '''FreeDOS''' is a [[FOSS|free]] [[DOS (x86 operating system)|DOS]] operating system developed as an open-source and fully compatible alternative to [[MS-DOS]]. The project started as PD-DOS in 1994, when Microsoft announced it would no longer be developing MS-DOS as an independent operating system but rather as the core component of [[Windows|Windows 95]].<ref>[https://www.freedos.org/about/ About FreeDOS]</ref> FreeDOS is the oldest known open-source DOS as well as one of the few remaining operating systems capable of booting on the original 16-bit x86 processors such as the Intel 8086. It is the only major DOS still in active development. == Compatibility == FreeDOS is almost fully compatible with MS-DOS command syntax, software and drivers. It's able to run nearly all programs built for MS-DOS, including early, pre-95 versions of Microsoft Windows and other DOS [[desktop Environments|graphical environments]], such as OpenGEM. It can also utilize DPMIs and DOS Extenders to run 32-bit software, including DOS builds of [[Bash]] and other GNU and UNIX software compiled with [[DJGPP]]. == Environment == [[File:VirtualBox_FreeDOS_1.3_22_11_2023_15_49_13.png|thumb|The OpenGEM graphical shell running on FreeDOS]] The basic FreeDOS environment consists of the FreeDOS [[kernel]], <code>KERNEL.SYS</code>, a command interpreter ([[shell]]), which is automatically ran by the kernel on startup, and any installed packages. The default FreeDOS shell, FreeCom, is installed on the system to <code>\COMMAND.COM</code> for MS-DOS compatibility. It is fully compatible with MS-DOS and PC DOS COMMAND.COM shells. Alternate shells, like <code>bash.exe</code>, can be used with the <code>SHELL</code> and <code>SHELLHIGH</code> options in the FreeDOS configuration file <code>\CONFIG.SYS</code> or <code>\FDCONFIG.SYS</code>.<ref>[https://www.freedos.org/books/get-started/9-fdconfig-sys/ How to configure FreeDOS with FDCONFIG.SYS]</ref> Graphical environments, like as OpenGEM, can also be installed from the FreeDOS setup CDs. == Package Managment == [[File:Fdimples.png|thumb|The FDIMPLES package manager]] Unlike traditional DOS implementations, FreeDOS has a full-featured [[TUI]] [[package manager]], FDIMPLES, used to install software from a FreeDOS CD to disk.<ref>[https://www.freedos.org/books/get-started/10-using-fdimples/ How to install and remove packages with FDIMPLES]</ref> The '''FDNPKG''' package manager is installed using FDIMPLES and is a [[CLI]] package manager capable of installing software remotely over the internet. == References == 2ca938b990ff3d4c70852448ac50bf0e54d6a8cd 0 1381 6004 5886 2026-08-12T13:03:49Z Imnotgoodatnames 121 Add link to [[FreeDOS]] wikitext text/x-wiki [[File:Command_com.png|thumb|MS-DOS command prompt]] '''DOS''' is a family of MS-DOS compatible disk operating systems for the IBM PC and compatibles. The most popular operating systems in the category are Microsoft's '''IBM PC DOS''' and '''MS-DOS'''. All other DOS-es were designed to be compatible with MS-DOS but usually introduced new features as well. =PC DOS= {{SoftwareInfobox | title = '''IBM PC DOS''' | image = [[File:IBM_PC_DOS_7.0_logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | caption = IBM PC DOS logo | releasestatus = Discontinued | lastrelease = PC DOS 2000<ref>https://winworldpc.com/product/pc-dos/2000</ref> | languages = [[x86 Assembly]], [[C]] | developers = Microsoft, IBM | license = Proprietary | website = [https://web.archive.org/web/19990508201612/www.software.ibm.com/os/dos/dos2000/oem.html PC DOS 2000 for OEMs (archived 1999)] }} '''IBM PC DOS''' is the original DOS developed in 1981 by Microsoft for the IBM Personal Computer alongside Microsoft's MS-DOS, which was sold to the open market. It shared development with MS-DOS and the two systems were nearly identical until 1993, when Microsoft stopped developing it and IBM started introducing new features. =MS-DOS= {{SoftwareInfobox | title = '''MS-DOS''' | image = [[File:Msdos-icon.svg|frameless|upright=0.8]] | caption = MS-DOS icon in [[Windows]] | releasestatus = Discontinued | lastrelease = 6.22; 8.0 (As part of [[Windows]] ME)<ref>https://winworldpc.com/product/ms-dos/622</ref><ref>https://web.archive.org/web/20120109133113/http://www.microsoft.com/Presspass/press/2000/sept00/availabilitypr.mspx</ref> | languages = [[x86 Assembly]], [[C]]<ref>https://github.com/microsoft/MS-DOS</ref> | developers = Microsoft | license = Proprietary; 1.25, 2.11, 4.00: [[MIT_License|MIT]] | website = [https://web.archive.org/web/20170709153940/https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/windows_dos_overview.mspx MS-DOS overview (archived 2017)] }} '''MS-DOS''' (Microsoft DOS) is the version of Microsoft's DOS sold to OEMs other than IBM. It quickly became the most popular DOS system due to its use by most IBM compatible personal computers. From 1994 it ceased development as an independent operating system and from 1995 to 2000 was instead developed as the core part of the [[Windows]] 9x series. =FreeDOS= ''Main page: [[FreeDOS]]'' {{DistributionInfobox | title = FreeDOS | image = [[File:Blinky.svg|frameless|upright=0.8|Blinky]] | caption = FreeDOS mascot | releasestatus = Maintained | releasemodel = Stable | packagemanager = FDIMPLES, FDNPKG<ref>https://opensource.com/article/21/6/freedos-package-manager</ref><ref>https://fdnpkg.sourceforge.net/</ref> | defaultdesktops = [[CLI|Command line interface]] | usagetype = Desktop | architectures = IA-16, i386<ref>https://github.com/FDOS/kernel/blob/d6791add2043c9d7b584d840a8ffaf8829fd2bdc/config.m#L57</ref> | website = [http://freedos.org freedos.org] }} '''FreeDOS''' is a [[FOSS|free]] DOS operating system developed since 1994, when Microsoft announced Windows would replace MS-DOS. It includes various advantages over MS-DOS such as kernel-level FAT-32 support, a network package manager and a CD release. == References == b0039522da718703285fa18ea3fefee9fb19cce5 6 1423 6006 2026-08-12T17:30:45Z Imnotgoodatnames 121 Screenshot of the FreeDOS FDimples package manager wikitext text/x-wiki == Summary == Screenshot of the FreeDOS FDimples package manager == Licensing == {{CC-BY-4.0}} e7d64c94972b23a7ef2756d684a40e2853b2954a 0 1424 6010 2026-08-13T14:57:36Z Imnotgoodatnames 121 Create page, category, stub, refs, infobox, screenshot, wine relation wikitext text/x-wiki {{stub}} [[Category:Misc Operating Systems]] {{DistributionInfobox | title = ReactOS | image = [[File:ReactOS_logo.svg|frameless|ReactOS logo]] | caption = ReactOS logo | releasestatus = Maintained | releasemodel = Stable, nightly builds available<ref>[https://reactos.org/getbuilds/ Download ReactOS Builds]</ref> | packagemanager = RAPPS<ref>[https://reactos.org/wiki/RAPPS RAPPS - ReactOS Wiki]</ref> | defaultdesktops = Explorer<ref>[https://reactos.org/wiki/ReactOS_Explorer ReactOS Explorer]</ref> | usagetype = Desktop | architectures = x86, x64<ref name=site>[https://reactos.org ReactOS homepage]</ref> | website = [http://reactos.org reactos.org] }} [[File:ReactOS_0.4.14_Firefox_48_screenshot.png|thumb|ReactOS desktop]] '''ReactOS''' is a [[FOSS|free]] operating system developed as an open-source and fully compatible alternative to [[Windows|Microsoft Windows]]. The ReactOS project started in 1997 as a revival of the earlier ''FreeWin95'' project which was an effort to create a Windows 95 clone. ReactOS, however, aims for Windows NT compatibility instead. Despite being in development since 1997, it is still in alpha as of 2026. ReactOS currently targets NT version 5.2 compatibility, equivalent to Windows Server 2003.<ref>[https://reactos.org/pipermail/ros-dev/2015-March/017216.html ReactOS versioning]</ref> == Relation to Wine == Both ReactOS and [[Wine]], the Windows compatibility layer for [[UNIX|Unix-like]] systems, are attempts to implement an open-source Windows-compatible environment. As such, both projects support and cooperate with each other to some degree. Many parts of ReactOS use Wine code.<ref>[https://github.com/reactos/reactos/blob/master/README.md#more-information reactos/README.md - ReactOS Github]</ref> == References == e0f4cff3fd511e9fa5f0ac7a94cb0819b85a292c 0 1142 6011 5497 2026-08-13T15:05:47Z Imnotgoodatnames 121 Add more references to FOSS software wikitext text/x-wiki {{stub}} '''Windows''' is a [[proprietary software|proprietary]] [[Operating System|operating system]] developed by Microsoft. While originally catered towards personal computers, Windows now offers versions such as Windows Server, Windows IoT, and Windows LTSC. It was first released on November 20, 1985 as Windows 1.0 with a graphical user interface.<ref>{{Cite|url=https://en.wikipedia.org/wiki/Microsoft_Windows|title=Microsoft Windows Wikipedia Entry|accessdate=2026}}</ref> [[Cygwin]] and [[MSYS2|MSYS]] are ports of various [[GNU]] packages and other [[free and Open Source Software|free]] Unix-like software to Windows. == FOSS implementations == === Wine === ''Main page: [[Wine]]'' '''Wine''' is a Windows compatibility layer used to run Windows applications on [[UNIX]]-like operating systems such as [[macOS]] and [[Linux Distributions|Linux-based operating systems]]. === ReactOS === ''Main page: [[ReactOS]]'' '''ReactOS''' is an open-source operating system designed to be binary-compatible with Windows NT. == References == 875824cb2380077eb8378bec5f0f08563c31013b 0 1373 6012 5941 2026-08-14T14:53:28Z Imnotgoodatnames 121 Add desktop screenshot wikitext text/x-wiki {{Stub}} <!-- distroinfobox, more info --> [[Category:Misc Operating Systems]] {{DistributionInfobox | architectures = i386, x86_64, aarch64<ref>[https://www.osnews.com/story/139255/gnu-hurd-ported-to-aarch64-and-more-hurd-news/ GNU Hurd ported to aarch64 and more hurd news]</ref> | caption = The GNU Hurd logo | defaultdesktops = [[GNOME]], [[Xfce]], [[Window Maker]], [[Fluxbox]], [[IceWM]], [[Openbox]] | image = [[File:Hurd-logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | packagemanager = [[dpkg]]/[[apt]] ([[Debian GNU/Hurd]]), [[Guix]] | releasemodel = Rolling | releasestatus = Experimental | title = GNU/Hurd | usagetype = Research, Development | website = [https://www.gnu.org/software/hurd/ gnu.org/software/hurd] }} [[File:Debian GNU Hurd GNUstep desktop.png|thumb|GNU/Hurd running [[GNU Emacs]], [[Bash|GNU Bash]] and GNU plotutils on the [[GNUstep]] [[desktop Environments|desktop environment.]]]] '''GNU/Hurd''' is an unofficial name for the [[GNU]] operating system running on the '''GNU Hurd''' kernel. GNU Hurd (also referred to as "The Hurd" on GNU's website) is the GNU project's replacement for the [[UNIX]] operating system kernel.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's official Hurd documentation]</ref> It is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's description of Hurd]</ref> Essentially, The Hurd consists of a set of protocols and server processes (also known as daemons) that run on the GNU [[Mach]] microkernel. This means it differentiates from the [[Linux]] kernel, which is [[monolithic]].<ref>[https://itsfoss.com/news/gnu-hurd-progress-report/ ItsFOSS news report on GNU/Hurd]</ref> It has been in development since 1990, by the [[GNU]] project.<ref>[https://en.wikipedia.org/wiki/GNU_Hurd The Wikipedia entry for GNU Hurd]</ref> === History === '''Richard Stallman''' founded the GNU project in September 1983 with a goal to create a free GNU operating system.<ref>[https://cs.stanford.edu/people/eroberts/courses/cs181/projects/2000-01/open-source/gnu.htm#:~:text=In%201983,%20the%20GNU%20Project,up%20by%20proprietary%20software%20vendors. The history of the GNU project]</ref> Initially, all the necessary components needed for kernel development were made. By 1989, the [[GPL]] came into being, and the only major missing component was the [[kernel]], hence why they added the GNU operating system to [[Linux]] until they had their own kernel.<ref>[https://www.gnu.org/gnu/linux-and-gnu.html "Linux and GNU" entry on GNU's website]</ref> After this, development on the Hurd started after an abandoned kernel attempt, based on the [[TRIX]] operating system.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd History: How it started]</ref> According to the initial architect and founder of Hurd, '''Thomas Bushnell''', one of their early plans was to adopt and build on the [[4.4BSD]]-Lite kernel.<ref>[https://web.archive.org/web/20230710085615/http://www.groklaw.net/article.php?story=20050727225542530 "The Daemon, the GNU and the Penguin"]</ref> Later on from this, Richard Stallman proposed the use of the [[Mach]] microkernel, however this was delayed due to concern on whether the [[Mach]] code would be released under a suitable license.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd's history]</ref> Up until now, the development of Hurd had been relatively fast. However, with the release of the free [[Linux]] kernel in 1991, development slowed heavily, but did not stop. GNU's [[userland]] components were quickly put together with the [[Linux]] kernel to create operating systems based on the [[Linux]] kernel ([[Linux distributions]]). === References === 7977441c39c26b7760256caba24f442313e6b25d 0 182 6013 5289 2026-08-14T16:39:48Z Imnotgoodatnames 121 Add Debian GNU/Hurd part wikitext text/x-wiki {{DistributionInfobox | title = Debian | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | caption = The official Debian logo | releasestatus = Maintained | releasemodel = Rolling Release / Stable | packagemanager = [[dpkg]] | defaultdesktops = GNOME, [[Xfce]], [[KDE Plasma]], Cinnamon, MATE, LXDE, LXQt | usagetype = Desktop, Server | architectures = amd64, aarch64, armel, armhf, i686, mipsel, mips64el, ppc64el, s390x | website = [https://www.debian.org/ debian.org] }} [[Category:Linux Distributions]] [[File:Debian 12 Bookworm KDE Plasma Desktop English.png|thumb|Debian 12 Bookworm running [[KDE Plasma]]]] '''Debian''' (/ˈdɛbiən/),<ref>"[https://www.debian.org/intro/about Debian -- About]". Debian. [https://web.archive.org/web/19990117033720/https://www.debian.org/intro/about Archived] from the original on January 17, 1999. Retrieved May 20, 2024.</ref> also known as '''Debian GNU/Linux''', is a [[Linux Distributions|Linux distribution]] developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993.<ref>"[http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog ChangeLog]". [[wikipedia:Ibiblio|ibiblio]]. [https://web.archive.org/web/20170106042725/http://www.ibiblio.org/pub/historic-linux/distributions/debian-0.91/ChangeLog Archived] from the original on January 6, 2017.</ref> == History == Debian adheres to the principles of the GNU Project and Free Software<ref name=":0">[https://www.gnu.org/distros/common-distros.html "Explaining Why We Don't Endorse Other Systems"]. [[wikipedia:GNU|GNU]]. [https://web.archive.org/web/20231102171742/https://www.gnu.org/distros/common-distros.html Archived] from the original on November 2, 2023.</ref><ref>[https://www.debian.org/social_contract#guidelines "Debian Social Contract"]. Debian. October 1, 2022.</ref> and has been developed openly and distributed freely. The Free Software Foundation sponsored the project from November 1994 to November 1995.<ref>[https://web.archive.org/web/20231103150337/https://www.debian.org/doc/manuals/project-history/project-history.en.txt "A Brief History of Debian"]. Archived from [https://www.debian.org/doc/manuals/project-history/project-history.en.txt the original] on November 3, 2023.</ref> In 1997, the Debian Project established Software in the Public Interest as a nonprofit organization to provide ongoing financial support. However, it no longer receives endorsement from GNU and the FSF due to its long-standing practice of hosting non-free software repositories and, since 2022, including non-free firmware in its installation media by default.<ref name=":0" /><ref>[https://web.archive.org/web/20231102171923/https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html "General Resolution: non-free firmware: results"]. Archived from [https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html the original] on November 2, 2023.</ref> The first version of Debian, Debian 0.01 released on September 15, 1993. The first generaly usable Debian version to be released, Version 0.90, was released on 16 august 1993<ref>{{Cite|url=https://www.debian.org/doc/manuals/project-history/releases.en.html|title=Debian releases overview|accessdate=2026/26/05}}</ref>. It is considered one of the earliest [[Linux Distributions|linux distros]] alongside [[Slackware]] and [[MCC Interim Linux]]. == Features == === Release Cycle === Debian maintains three primary development branches: * Stable - The current official release, recommended for production systems * Testing - The next planned stable release, featuring newer software versions * Unstable (Sid) - The rolling development branch where new packages are initially introduced === Package Management System === Debian uses the [[APT]] (Advanced Package Tool) built on top of [[dpkg]], featuring: * Over 59,000 ready-to-install software packages * Multiple repository sections (main, contrib, non-free) * Secure package verification through signed repositories * Sophisticated dependency resolution === Project Management === The project is managed by a team of volunteers led by the Debian Project Leader, and it adheres to foundational documents such as: * The Debian Social Contract * The Debian Constitution * The Debian Free Software Guidelines === Hardware requirements === Debian's hardware requirements are at minimum those needed by the kernel and GNU tool set.<ref>[http://www.debian.org/releases/stable/amd64/ch02s01.en.html "2.1. Supported Hardware"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20201228203501/https://www.debian.org/releases/stable/amd64/ch02s01.en.html Archived] from the original on December 28. 2020.</ref> The recommended system requirements vary based on the extent of the installation, with more extensive installations requiring more resources.<ref name=":1">[http://www.debian.org/releases/stable/amd64/ch03s04.en.html "3.4. Meeting Minimum Hardware Requirements"]. Debian GNU/Linux Installation Guide. Debian. 2019. [https://web.archive.org/web/20210112200525/https://www.debian.org/releases/stable/amd64/ch03s04.en.html Archived] from the original on January 12, 2021.</ref> {| class="wikitable" !Install type !RAM (minimum) !RAM (recommended) !Hard Drive |- |No desktop |256 megabytes |512 megabytes |4 gigabytes |- |With desktop |1 gigabytes |2 gigabytes |10 gigabytes |} The actual minimum memory requirements depend on the architecture and can be significantly lower than the numbers listed in the table. For example, it is possible to install Debian on an x86-64 system with just 170 MB of RAM.<ref name=":1" /> Graphical user interfaces can run on older or low-end systems, but it is advisable to install [[Window Manager|Window Managers]] instead of [[Desktop Environment|Desktop Environments]], as they are less resource-intensive. The requirements for individual software vary greatly and should be considered alongside the base operating environment's requirements.<ref name=":1" /> == Installation == Debian provides multiple installation methods: * Full DVD/CD sets containing the complete repository * Network installation images for minimal downloads * Live images for testing before installation * Architecture-specific installers * Cloud images for virtual deployment == Debian GNU/Hurd == {{DistributionInfobox | title = Debian GNU/Hurd | image = [[File:Debian-OpenLogo.svg|Debian-OpenLogo]] | releasestatus = Maintained | releasemodel = Stable, Rolling release | packagemanager = [[dpkg]] | defaultdesktops = [[IceWM]] | usagetype = Development, Desktop, Server | architectures = i686, x86_64 | website = [https://www.debian.org/ports/hurd debian.org/ports/hurd] }} '''Debian GNU/Hurd''' is an experimental port of the Debian userland packages to the [[GNU/Hurd|GNU Hurd]] kernel.<ref>[https://www.debian.org/ports/hurd/ Debian GNU/Hurd]</ref> It tries to stay close to Debian GNU/Linux, with most Debian GNU/Linux packages available on Debian GNU/Hurd. However, there are some differences between the ports - only i386 and amd64 ports are currently supported, despite Hurd itself also supporting aarch64 as well as using sysvinit instead of [[Systemd]].<ref>[https://www.debian.org/ports/hurd/hurd-news.html April 25th, 2015 - Debian GNU/Hurd news]</ref> == References == <references /> 74aceeb2f6936ee6fa6666e20467eb9f3a71a0b5 0 1425 6014 2026-08-14T16:40:58Z Imnotgoodatnames 121 Create redirect wikitext text/x-wiki #REDIRECT [[Debian#Debian GNU/Hurd]] faf6cf164887cb611f4fa9920f63ee91f6d5bb21 0 202 6015 5690 2026-08-15T09:25:26Z Imnotgoodatnames 121 APT Cow isn't Larry. Actually it's older than Gentoo itself, and i couldn't find any references to them being the same cow applied retroactively wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[Category:Mascots]] [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] [[File:aptmoo.png|frame|Similar cow output on [[APT]]. Have you mooed today?]] '''Larry the Cow''' is among the unofficial mascots<ref>https://wiki.gentoo.org/wiki/Larry_the_cow Gentoo Wiki, 2023 (Imported 4th June 2024)</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html Gentoo Forums, 2003 (imported 4th June 2024)</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727 Gentoo Bug Report, 2003 (imported 4th June 2024)</ref> * Larry can be found in [[emerge]] by running <code>emerge --moo</code> Larry can also be found in [[Dpkg|apt]] by running <code>apt moo</code> . * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow MySpace, (imported 4th June 2024)</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry, Gentoo Wiki, 2000 (imported 4th June 2024)</ref> [[File:Larry The Cow with Gentoo Logo.png|thumb|Larry after he grew his black and white patches]] * Larry the cow was a bit frustrated at the current state of Linux distributions until he tried Gentoo Linux.<ref>https://www.gentoo.org/get-started/about/ Gentoo.org (imported 9th June 2026)</ref> == References == <references /> 8ac573ad200f4958dc0588e5be3de614d2b07045 0 412 6016 3595 2026-08-15T09:28:53Z Imnotgoodatnames 121 APT Cow isn't Larry. Actually it's older than Gentoo itself, and i couldn't find any references to them being the same cow applied retroactively wikitext text/x-wiki [[Category:Software]] {{Needs Citations}} {{SoftwareInfobox | image = [[File:CowsayOutput.png|thumb|left|alt=a terminal with the user as "minimum" and the hostname as "tidepod" doing the command `cowsay "i love ATL"` which outputs an ASCII art of a cow with a speech bubble that says: "i love ATL!"]] | caption = Example Cowsay output | title = Cowsay | releasestatus = Maintained | lastrelease = 3.04, 2016-06-25 | languages = [[Perl]] | developers = cowsay-org | website = [https://github.com/cowsay-org/cowsay github.com/cowsay-org/cowsay] }} '''Cowsay''' is a simple program that generates ASCII art of a cow with a speech bubble with the given parameter in it. It can also generate other characters / animals using files that end in <code>.cow</code> or the built-in premade art using the <code>-f</code> (<code>cowsay -f [name]</code>) flag. (For example: tux) Other commands like <code>fortune</code>, can be piped into Cowsay, and Cowsay can be piped into commands like <code>lolcat</code>. You can use the <code>-l</code> flag (<code>cowsay -l</code>) to list the available cow files (character / animal names) Cowsay can be used in many things, for example: [[Ricing]] showcases (screenshots, or videos), IRC channels, code comments and etc. '''Cowthink''' is cowsay's "thinking" alternative, which turns the speech bubble into a thinking bubble. == Available Parameters == {| class="wikitable" |- ! Options !! Cow mode !! Cow Eyes !! Cow Tongue |- | <code>-b</code> || Borg mode || == || None |- | <code>-d</code> || Dead mode || XX || None |- | <code>-g</code> || Greedy mode || $$ || None |- | <code>-p</code> || Paranoid mode || @@ || None |- | <code>-s</code> || "Stoned" mode || ** || U-shaped |- | <code>-t</code> || Tired mode || -- || None |- | <code>-w</code> || Wired mode || OO || None |- | <code>-y</code> || Youthful mode || .. || None |- | <code>-e</code> || Custom eye mode || [Given parameter] || Default (none unless specified) |- | <code>-T</code> || Custom tongue mode || Default (none unless specified) || [given parameter] |} == Trivia == * Cowsay was debian's package of the day back in 2007 [https://debaday.debian.net/2007/10/28/cowsay-a-configurable-talking-and-thinking-cow/ <sup><nowiki>[1]</nowiki></sup>] * [[Larry the Cow]] (<code>emerge --moo</code>) and Cowsay share the same ASCII art. [[Debian]]'s [[APT]] tool (<code>apt moo</code>) also features a similar cow. * There is a graphical version of this program called [https://www.doof.me.uk/xcowsay/ xcowsay]. 65f3ff86649fee6c2bd270c6aebbb252e1bcbd97 0 1426 6017 2026-08-17T13:47:44Z Imnotgoodatnames 121 Create page with stuff, refs, infobox etcetera wikitext text/x-wiki {{Stub}} [[Category:Software]] {{SoftwareInfobox | title = Qt | image = [[File:Qt_logo_neon_2022.svg|200px|Qt logo]] | caption = Qt Logo | releasestatus = Maintained | lastrelease = 6.11.1, 2026-05-13 | languages = [[C++]] | developers = Qt Project, Qt Group | website = [https://www.qt.io/ qt.io] | license = [[GPL]], [[GPL#GNU Lesser General Public License (LGPL)|LGPL]] [[Proprietary software|Qt Commercial License]]<ref>[https://www.qt.io/development/qt-framework/qt-licensing Qt Licensing Overview]</ref> }} '''Qt''' is an application development framework and widget toolkit for creating cross-platform [[GUI|graphical]] [[Installing software|applications]] originally developed since 1994. In addition to GUI applications, Qt also supports [[CLI|command line]] programs and web frameworks.<ref>[https://cutelyst.org/ Cutelyst]</ref> Qt primarily targets C++ but also supports other languages, such as [[Python]] using bindings. Qt is cross-platform and supports [[Unix]]-like systems using [[X_Window_System|X]] and [[Wayland]], [[Microsoft Windows]], [[macOS]] and various embedded systems such as [[QNX]].<ref>[https://doc.qt.io/qt-6/supported-platforms.html Supported Platforms -Qt]</ref> Qt is the graphical toolkit used by [[KDE]] for their [[KDE Plasma|Plasma]] [[desktop Environments|desktop environment]].<ref>[https://develop.kde.org/ KDE Developer Platform]</ref> == Qt tools == Qt offers various tools for developing Qt-based software, such as the Qt Creator [[Text Editors#Integrated development environments (IDEs)|IDE]], the automated Makefile generator ''qmake'', Qt Designer, the Qt Linguist translation tool and others.<ref>[https://www.qt.io/development/tools/qt-creator-ide Qt Creator IDE]</ref><ref>[https://doc.qt.io/qt-6/qmake-tutorial.html Getting Started with qmake]</ref> == References == a81a956c6533e8058add6143c05a37cd35648502 0 1427 6018 2026-08-18T17:01:17Z Imnotgoodatnames 121 Create sh page for both Bourne and POSIX sh wikitext text/x-wiki [[category:software]] {{DISPLAYTITLE:sh}} '''sh''' on [[UNIX]] and Unix-like systems refers to the standard name or alias of the [[shell]] on [[UNIX]] and UNIX-like systems, the [[POSIX]] specification for a shell and, more specifically, the executable name of the '''Bourne shell'''. == Bourne shell == The Bourne shell is the default of [[Research Unix|classic Unix]] since first appearing on Version 7 Unix as an upgrade to the Thompson shell.<ref>[https://www.in-ulm.de/~mascheck/bourne/ The Traditional Bourne Shell Family]</ref> The Bourne shell introduced many features now standard on Unix shells including variables, <code>for</code> loops and <code>case</code>. Though the Bourne shell isn't used on any modern UNIX or Unix-like system, it became the de facto standard for the standard shell utility on most systems. The [[Korn shell]] began as an upgraded version of the Bourne shell and the ''[[Bash|GNU Bourne Again SHell]]'' (''Bash'') was developed by the [[GNU|GNU Project]] to be a compatible and upgraded clone of the Bourne, Korn and [[csh|C]] shells.<ref>[https://www.gnu.org/software/bash/ GNU Bash]</ref> == POSIX sh == POSIX specifies the ''sh'' utility as a command language interpreter that executes commands from a command line string, a specified file or the standard output.<ref name=sh>[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/sh.html sh — shell, the standard command language interpreter]</ref> It also defines the ''Shell Command Language''.<ref>[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_19 2. Shell Command Language]</ref> POSIX does not enforce a filesystem hierarchy and, for that reason, explicitly states that applications that need to call sh (usually shell scripts) should determine its PATH using <code>command -v sh</code> rather than assuming it's installed to <code>/bin/sh</code> as is the case on nearly all UNIX and Unix-like systems.<ref name=sh/> == References== da07a263dd2f5ab335b6cbee672b137d6f8ab32a 0 1428 6019 2026-08-18T17:05:01Z Imnotgoodatnames 121 Create redirect wikitext text/x-wiki #REDIRECT [[UNIX#Origins]] 075554cc820f5ca0f4d74ffb987f46bc2a67b23c 0 436 6020 3577 2026-08-23T02:01:14Z Itscool900 435 Updated a misleading claim; see https://oldwww.adelielinux.org/about/faq.html#not_alpine wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/ adelielinux.org]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is an APK-based [[Linux Distributions|Linux distribution]]. The distribution targets old and low end machines, like desktops and servers. == Base description == One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution uses the OpenRC init system for service management, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. fe4e2a869032cab718963c971cbe59c7f716fc65 0 436 6021 6020 2026-08-23T02:01:58Z Itscool900 435 fix grammar and combine sentences wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/ adelielinux.org]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is an APK-based [[Linux Distributions|Linux distribution]] targeting old and low end machines, like desktops and servers. == Base description == One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution uses the OpenRC init system for service management, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. f248011e7ce49d815afd09f39f0984d32b95d11e 6022 6021 2026-08-23T02:05:54Z Itscool900 435 fix wording wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/ adelielinux.org]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is an APK-based [[Linux Distributions|Linux distribution]] targeting old and low end machines, including both desktops and servers. == Base description == One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution uses the OpenRC init system for service management, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. 89ca4ddbabbfab94595b56823fa3ad59eafb4d29 6023 6022 2026-08-23T03:55:34Z Itscool900 435 add hyphen wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/ adelielinux.org]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is an APK-based [[Linux Distributions|Linux distribution]] targeting old and low-end machines, including both desktops and servers. == Base description == One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution uses the OpenRC init system for service management, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. c93f5ddffad4c3fd12d54074c44a7522061d96c1 6024 6023 2026-08-23T04:05:10Z Itscool900 435 update information on service management, add the first citation(!) wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/ adelielinux.org]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is an APK-based [[Linux Distributions|Linux distribution]] targeting old and low-end machines, including both desktops and servers. == Base description == One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution offers a choice between s6 and OpenRC for service management<ref>[https://help.adelielinux.org/html/admin/introduction.html https://help.adelielinux.org/html/admin/introduction.html#]</ref>, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. 9e32ac6a2a576eb92733d2dd1b8f5160ded954df 6068 6024 2026-08-25T08:57:45Z Hamachitan 222 /* References */ 🍣 Fix [[FW:Guidelines#Citations|citations]] wikitext text/x-wiki {{Needs Citations}} {{DistributionInfobox|title=Adélie Linux|image= [[File:Adelie Linux Logo.png|thumb]] |caption=The Adélie Linux logo|releasestatus=Maintained|releasemodel=Rolling Release|packagemanager=[[apk-tools]]|defaultdesktops=[[KDE Plasma]], LXQT, MATE, [[Xfce]]|usagetype=Desktop|architectures=x86_64, PPC, ARM|website=[https://www.adelielinux.org/ adelielinux.org]}} [[File:Adelie_linux_neofetch.png|thumb|Neofetch of Adélie Linux on LiveCD environment]] '''Adélie Linux''' is an APK-based [[Linux Distributions|Linux distribution]] targeting old and low-end machines, including both desktops and servers. == Base description == One of the standout features of Adélie Linux is its focus on portability and compatibility, allowing it to run on a wide range of hardware, from older machines to modern systems. The distribution offers a choice between s6 and OpenRC for service management<ref>[https://help.adelielinux.org/html/admin/introduction.html Adélie Linux 1.0 Administrator's Handbook - Chapter 1. Introduction], Adélie Linux, 2021-06-01 (Accessed: 2026-08-25)</ref>, which contributes to its speed and efficiency. Adélie Linux also emphasizes a clean and straightforward user interface, making it accessible for both newcomers and experienced users. It comes with a selection of pre-installed software that covers essential tasks, while also allowing users to easily customize their environment by installing additional packages from its repositories. With a commitment to open-source principles, Adélie Linux encourages community involvement and contributions, fostering a collaborative environment for development and support. 9bebff003bb8b9e1fa1b7ad33647474a9a4eff43 3001 1429 6025 2026-08-23T04:12:39Z Itscool900 435 /* "There are two boot modes for computer systems" */ new section wikitext text/x-wiki == "There are two boot modes for computer systems" == I feel like this should have at least 5 asterisks if you're going to say it. CSM, EFI 1.10, libreboot... lumping every system into two categories is dubious. [[User:Itscool900|Itscool900]] ([[User talk:Itscool900|talk]]) 04:12, 23 August 2026 (UTC) 15711e8f8e9be1bff7f730ae18d5e1287422b8db 6026 6025 2026-08-23T04:14:41Z Madonuko 140 /* "There are two boot modes for computer systems" */ Reply wikitext text/x-wiki == "There are two boot modes for computer systems" == I feel like this should have at least 5 asterisks if you're going to say it. CSM, EFI 1.10, libreboot... lumping every system into two categories is dubious. [[User:Itscool900|Itscool900]] ([[User talk:Itscool900|talk]]) 04:12, 23 August 2026 (UTC) :There were consensus that this entire article should be rewritten anyway. — [[User:Madonuko|Madonuko]] ([[User talk:Madonuko|talk]]) 04:14, 23 August 2026 (UTC) 82671b2a4af4b3487f8dc913890de68dc578c747 0 274 6027 3581 2026-08-23T04:20:24Z Itscool900 435 cite a claim wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs Citations}} {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''', also known simply as '''Artix''', is a Linux distribution based on [[Arch]] that focuses on providing alternative init systems to systemd . It maintains high compatibility with Arch Linux while offering users the freedom to choose their preferred init system. == History == Artix Linux emerged from the Arch-OpenRC and Manjaro-OpenRC projects<ref>https://systemd-free.artixlinux.org/news.php#170727</ref>, officially launching in 2017 as a response to Arch Linux's adoption of systemd as its only init system. The distribution aims to provide a systemd-free experience while maintaining the principles of simplicity and user-centricity that Arch Linux is known for. == Features == === Init System Options === Artix supports multiple init systems: * OpenRC - A dependency-based init system from Gentoo * runit - A cross-platform Unix init scheme with service supervision * s6 - A suite of programs for process supervision * dinit - A service manager and init system designed to be simple and portable === Package Management === Artix uses [[Pacman]] as its package manager and maintains its own repositories alongside converted Arch Linux packages. The distribution provides several package repositories: * System repositories (specific to each init system) * Universe repository (containing converted Arch packages) * Galaxy repository (Artix-specific packages) === Installation === The distribution offers several installation methods: * Live ISOs with various desktop environments * Base ISOs for minimal installations * OpenRC, runit, dinit, and s6 variants of each ISO == Philosophy == Artix adheres to the KISS principle (Keep It Simple, Stupid) inherited from Arch Linux while emphasizing: * Init system freedom * System transparency * User control * Minimal [[bloat]] * Rolling release model == Package Compatibility == While maintaining high compatibility with Arch Linux packages, some modifications are necessary for systemd-dependent packages. The Artix team maintains: * Native packages built specifically for Artix * Converted Arch packages modified to work without systemd * Scripts and tools to help users convert systemd-dependent packages == Community == Artix Linux maintains its own: * Forums for user support and discussion * Wiki documentation * Package repositories * Development team == System Requirements == * x86_64 architecture * Minimum 512 MB RAM (2 GB recommended) * Minimum 2 GB storage (20 GB recommended) * Basic knowledge of command line operations * Understanding of Linux system administration b0e50d552064f53ca0b67f1935a50178dbe71c04 6067 6027 2026-08-25T08:56:06Z Hamachitan 222 /* References */ 🍣 Fix [[FW:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Linux Distributions]] {{Needs Citations}} {{DistributionInfobox | title = Artix | image = [[File:Artixlogo.png|100px]] | caption = Logo of Artix Linux | releasestatus = Maintained | releasemodel = Bleeding edge | packagemanager = [[Pacman]] | defaultdesktops = any | usagetype = Desktop, Server | architectures = x86_64 | website = [https://artixlinux.org/ artixlinux.org] }} '''Artix Linux''', also known simply as '''Artix''', is a Linux distribution based on [[Arch]] that focuses on providing alternative init systems to systemd . It maintains high compatibility with Arch Linux while offering users the freedom to choose their preferred init system. == History == Artix Linux emerged from the Arch-OpenRC and Manjaro-OpenRC projects<ref>[https://systemd-free.artixlinux.org/news.php#170727 Return of the Jedi], Archlinux, systemd-free, 2017-07-27 (Accessed: 2026-08-25)</ref>, officially launching in 2017 as a response to Arch Linux's adoption of systemd as its only init system. The distribution aims to provide a systemd-free experience while maintaining the principles of simplicity and user-centricity that Arch Linux is known for. == Features == === Init System Options === Artix supports multiple init systems: * OpenRC - A dependency-based init system from Gentoo * runit - A cross-platform Unix init scheme with service supervision * s6 - A suite of programs for process supervision * dinit - A service manager and init system designed to be simple and portable === Package Management === Artix uses [[Pacman]] as its package manager and maintains its own repositories alongside converted Arch Linux packages. The distribution provides several package repositories: * System repositories (specific to each init system) * Universe repository (containing converted Arch packages) * Galaxy repository (Artix-specific packages) === Installation === The distribution offers several installation methods: * Live ISOs with various desktop environments * Base ISOs for minimal installations * OpenRC, runit, dinit, and s6 variants of each ISO == Philosophy == Artix adheres to the KISS principle (Keep It Simple, Stupid) inherited from Arch Linux while emphasizing: * Init system freedom * System transparency * User control * Minimal [[bloat]] * Rolling release model == Package Compatibility == While maintaining high compatibility with Arch Linux packages, some modifications are necessary for systemd-dependent packages. The Artix team maintains: * Native packages built specifically for Artix * Converted Arch packages modified to work without systemd * Scripts and tools to help users convert systemd-dependent packages == Community == Artix Linux maintains its own: * Forums for user support and discussion * Wiki documentation * Package repositories * Development team == System Requirements == * x86_64 architecture * Minimum 512 MB RAM (2 GB recommended) * Minimum 2 GB storage (20 GB recommended) * Basic knowledge of command line operations * Understanding of Linux system administration d0d032e8733057c66239f61c68b8bb77a18a6e0a 0 1234 6028 5320 2026-08-23T16:18:08Z MysteryBirb 353 Added page support for proton-vpn wikitext text/x-wiki [[Software]] including password manages, VPN services/providers, encryption, and similar. = Virtual Private Network (VPN) = VPN software is used to anonymize who you are on the internet and prevent tracking. {| class="wikitable" !Name !External links !Description !Open source? |- |[[ProtonVPN]] |[https://protonvpn.com/ Website], [https://github.com/ProtonVPN GitHub] |A commercial VPN software with Linux support. |Partially |} = Password managers = {| class="wikitable" !Name !External links !Description |- |[[KeePassXC]] |[https://keepassxc.org/ Website] ,[https://github.com/keepassxreboot/keepassxc GitHub] |Cross-platform secure password manager, awarded a security Visa by the French National Cybersecurity Agency (ANSSI). |- |[[BitWarden]] |[https://bitwarden.com/ Website], [https://github.com/bitwarden GitHub] |Bitwarden is a open-source cross-platform password management service that is used to store sensitive information in an encrypted vault. Its one of the most popular password managers in use. |} = Encryption = {| class="wikitable" !Name !External links !Description |- |[[GnuPG]] |[https://gnupg.org/ Website]. [https://github.com/gpg/gnupg GitHub Mirror] |Open source PGP encryption implementation. |- |[[Age]] |[https://github.com/FiloSottile/age GitHub] |Simple asymmetric and symmetric file encryption protocol. |- |[[Minisign]] |[https://jedisct1.github.io/minisign/ Website], [https://github.com/jedisct1/minisign GitHub] |A dead simple utility for cryptographically signing messages and files. |- |[[Cryptsetup]] |[https://gitlab.com/cryptsetup/cryptsetup GitLab] |Utility for creating, opening, and managing LUKS encrypted drives, partitions, and volumes. |- |[[Gocryptfs]] |[https://github.com/rfjakob/gocryptfs GitHub] |Encrypted overlay FUSE filesystem made in Go. |- |[[Cryptomator]] |[https://cryptomator.org/ Website], [https://github.com/cryptomator/cryptomator GitHub] |Program for creating encrypted vaults for use with cloud providers. |} 4b4d2865af3c7e4f71917d7e7380cae4b585446e 6 1430 6029 2026-08-24T09:12:41Z Imnotgoodatnames 121 GNUstep GWorkspace Application icon wikitext text/x-wiki == Summary == GNUstep GWorkspace Application icon == Licensing == {{GPL}} abc2a71d9877aece6f05866ba41bcd7cdbd4eb3f 6 1431 6030 2026-08-24T09:25:08Z Imnotgoodatnames 121 GNUstep GWorkspace application icon - resized to 256px wikitext text/x-wiki == Summary == GNUstep GWorkspace application icon - resized to 256px == Licensing == {{GPL}} 1340a48dbb76b505ae0533d9f167be1324762bd2 0 1432 6031 2026-08-24T09:31:52Z Imnotgoodatnames 121 Create page with finder and GWorkspace, add gworkspace infobox and stub thing wikitext text/x-wiki {{stub}} [[Category:Software]] [[Category:File_managers]] '''Finder''' is the default file manager and [[shell|graphical shell]] on all versions of [[macOS]]. It is used for managing disks drives and files as well as launching applications == GWorkspace == {{SoftwareInfobox | title = GWorkspace | image = [[File:GWorkspace-resized.png|128px]] | releasestatus = Maintained | lastrelease = 1.1.0 | caption = GWorkspace application icon | languages = [[Objective-C]]<ref name=git>[https://github.com/gnustep/apps-gworkspace gnustep/apps-gworkspace - Github]</ref> | developers = GNUstep project | website = [https://www.gnustep.org/experience/GWorkspace.html GWorkspace] | license = [[GPL|GPLv2]] | sourcecode = https://github.com/gnustep/apps-gworkspace }} '''GWorkspace''' is a [[GNUstep]] reimplementation of the NeXTSTEP file manager and the GNUstep equivalent of Finder. It is a file manager application and, optionally, a desktop shell that provides a customizable desktop with desktop icons and an application dock.<ref name=site>[https://www.gnustep.org/experience/GWorkspace.html GWorkspace]</ref> baef8a8cf978fe12e0590e48a118e29b61e232c0 6047 6031 2026-08-25T07:41:40Z Imnotgoodatnames 121 Add GWorkspace screenshot, more GWorkspace info, Gershwin Workspace entry, Refrences header wikitext text/x-wiki {{stub}} [[Category:Software]] [[Category:File_managers]] '''Finder''' is the default file manager and [[shell|graphical shell]] on all versions of [[macOS]]. It is used for managing disk drives and files as well as launching applications. == GWorkspace == {{SoftwareInfobox | title = GWorkspace | image = [[File:GWorkspace-resized.png|128px]] | releasestatus = Maintained | lastrelease = 1.1.0 | caption = GWorkspace application icon | languages = [[Objective-C]]<ref name=git>[https://github.com/gnustep/apps-gworkspace gnustep/apps-gworkspace - Github]</ref> | developers = GNUstep project | website = [https://www.gnustep.org/experience/GWorkspace.html GWorkspace] | license = [[GPL|GPLv2]] | sourcecode = https://github.com/gnustep/apps-gworkspace }} [[File:GWorkspace-desktop.png|thumb|'''GWorkspace''' as a file manager and shell, recycle bin, desktop settings, desktop icons and an application dock on a GNUstep desktop.]] '''GWorkspace''' is a [[GNUstep]] reimplementation of the NeXTSTEP file manager and the GNUstep equivalent of Finder. It is a file manager application and, optionally, a desktop shell that provides a customizable desktop with desktop icons and an application dock.<ref name=site>[https://www.gnustep.org/experience/GWorkspace.html GWorkspace]</ref> It provides various features of a desktop shell including a recycle bin, a desktop preferences window and previews for images and other files.<ref>[https://mediawiki.gnustep.org/index.php/GWorkspace.app GWorkspace.app - GNUstepWiki]</ref> === Gershwin Workspace === '''Workspace''' is a fork of GWorkspace for the [[Gershwin|Gershwin desktop environment.]] Like the rest of Gershwin, it aims to bring a more macOS-like experience to the desktop and therefore includes features such as thumbnail previews for files and the ability to place the dock on the bottom of the desktop as opposed to just the right or left.<ref>[https://github.com/gershwin-desktop/gershwin-workspace gershwin-desktop/gershwin-workspace - Github]</ref> == References == d57cf054b479c34cac7d63682afb169e30228b38 6048 6047 2026-08-25T07:42:19Z Imnotgoodatnames 121 OOps wikitext text/x-wiki {{stub}} [[Category:Software]] [[Category:File_managers]] '''Finder''' is the default file manager and [[shell|graphical shell]] on all versions of [[macOS]]. It is used for managing disk drives and files as well as launching applications. == GWorkspace == {{SoftwareInfobox | title = GWorkspace | image = [[File:GWorkspace-resized.png|128px]] | releasestatus = Maintained | lastrelease = 1.1.0 | caption = GWorkspace application icon | languages = [[Objective-C]]<ref name=git>[https://github.com/gnustep/apps-gworkspace gnustep/apps-gworkspace - Github]</ref> | developers = GNUstep project | website = [https://www.gnustep.org/experience/GWorkspace.html GWorkspace] | license = [[GPL|GPLv2]] | sourcecode = https://github.com/gnustep/apps-gworkspace }} [[File:GWorkspace-desktop.png|thumb|'''GWorkspace''' as a file manager and shell, managing the recycle bin, desktop settings, desktop icons and an application dock on a GNUstep desktop.]] '''GWorkspace''' is a [[GNUstep]] reimplementation of the NeXTSTEP file manager and the GNUstep equivalent of Finder. It is a file manager application and, optionally, a desktop shell that provides a customizable desktop with desktop icons and an application dock.<ref name=site>[https://www.gnustep.org/experience/GWorkspace.html GWorkspace]</ref> It provides various features of a desktop shell including a recycle bin, a desktop preferences window and previews for images and other files.<ref>[https://mediawiki.gnustep.org/index.php/GWorkspace.app GWorkspace.app - GNUstepWiki]</ref> === Gershwin Workspace === '''Workspace''' is a fork of GWorkspace for the [[Gershwin|Gershwin desktop environment.]] Like the rest of Gershwin, it aims to bring a more macOS-like experience to the desktop and therefore includes features such as thumbnail previews for files and the ability to place the dock on the bottom of the desktop as opposed to just the right or left.<ref>[https://github.com/gershwin-desktop/gershwin-workspace gershwin-desktop/gershwin-workspace - Github]</ref> == References == df8033c0c0df9277dd30e79e583624ccd874c1c8 6066 6048 2026-08-25T08:54:49Z Hamachitan 222 /* References */ 🍣 Fix [[FW:Guidelines#Citations|citations]] wikitext text/x-wiki {{stub}} [[Category:Software]] [[Category:File_managers]] '''Finder''' is the default file manager and [[shell|graphical shell]] on all versions of [[macOS]]. It is used for managing disk drives and files as well as launching applications. == GWorkspace == {{SoftwareInfobox | title = GWorkspace | image = [[File:GWorkspace-resized.png|128px]] | releasestatus = Maintained | lastrelease = 1.1.0 | caption = GWorkspace application icon | languages = [[Objective-C]]<ref name=git>[https://github.com/gnustep/apps-gworkspace GWorkspace], GNUstep, 2026-08-25 (Accessed: 2026-08-25)</ref> | developers = GNUstep project | website = [https://www.gnustep.org/experience/GWorkspace.html GWorkspace] | license = [[GPL|GPLv2]] | sourcecode = https://github.com/gnustep/apps-gworkspace }} [[File:GWorkspace-desktop.png|thumb|'''GWorkspace''' as a file manager and shell, managing the recycle bin, desktop settings, desktop icons and an application dock on a GNUstep desktop.]] '''GWorkspace''' is a [[GNUstep]] reimplementation of the NeXTSTEP file manager and the GNUstep equivalent of Finder. It is a file manager application and, optionally, a desktop shell that provides a customizable desktop with desktop icons and an application dock.<ref name=site>[https://www.gnustep.org/experience/GWorkspace.html GNUstep Workspace Manager: GWorkspace], GNUstep, 2025-02-24 (Accessed: 2026-08-25)</ref> It provides various features of a desktop shell including a recycle bin, a desktop preferences window and previews for images and other files.<ref>[https://mediawiki.gnustep.org/index.php/GWorkspace.app GWorkspace.app], GNUstepWiki, 2025-12-25 (Accessed: 2026-08-25)</ref> === Gershwin Workspace === '''Workspace''' is a fork of GWorkspace for the [[Gershwin|Gershwin desktop environment.]] Like the rest of Gershwin, it aims to bring a more macOS-like experience to the desktop and therefore includes features such as thumbnail previews for files and the ability to place the dock on the bottom of the desktop as opposed to just the right or left.<ref>[https://github.com/gershwin-desktop/gershwin-workspace gershwin-desktop/gershwin-workspace: Fork of GWorkspace with modifications for Gerswhin], gershwin-desktop, 2026-08-25 (Accessed: 2026-08-25)</ref> == References == 7b479100569a8724c42602d931e9b6c5f5ffdc20 6070 6066 2026-08-26T14:03:21Z Imnotgoodatnames 121 Page was split and contents added to [[GNUstep]] and [[MacOS]] wikitext text/x-wiki #REDIRECT [[macOS#Finder]] [[Category:File_managers]] 4b15ec25317da1f2d2b2bff9e00cde711657bb0e 4 1433 6032 2026-08-24T12:49:12Z Atmois 13 Create sandbox redirect wikitext text/x-wiki #REDIRECT [[Special:MyPage/sandbox]] 05b0357123f98ac8a3d2d2e0d25dca49fc19d287 6033 6032 2026-08-24T12:50:21Z Atmois 13 Revert tempoarily wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6034 6033 2026-08-24T12:57:14Z Atmois 13 Add text wikitext text/x-wiki To try out editing or write a draft you can visit your personal Sandbox here: [[Special:MyPage/sandbox]]. In this page you can test anything within the [[Code of Conduct]] before you edit a page in the Mainspace. You can learn more about contributing on [[FW:Contributing]] and check out [https://www.mediawiki.org/wiki/Help:Contents Mediawiki's Editing Guide] to learn more about wikitext. 17a5b2353c2aba4c7e0fa34a561080d0e622942e 6035 6034 2026-08-24T12:58:30Z Atmois 13 Improve layout wikitext text/x-wiki == '''[[Special:MyPage/sandbox]]''' == To try out editing or write a draft you can visit your personal Sandbox here: [[Special:MyPage/sandbox]]. In this page you can test anything within the [[Code of Conduct]] before you edit a page in the Mainspace. You can learn more about contributing on [[FW:Contributing]] and check out [[mediawikiwiki:Help:Contents|Mediawiki's Editing Guide]] to learn more about wikitext. __NOTOC__ __NOINDEX__ __NONEWSECTIONLINK__ 3cf2dbcbfad3c5b0a78f30ae64277deb1b908208 0 902 6036 3842 2026-08-24T15:08:30Z Imnotgoodatnames 121 Add fileman category wikitext text/x-wiki [[Category:Software]] [[Category:File managers]] {{SoftwareInfobox | image = [[File:Mc.png|frameless]] | caption = Midnight Commander in action | title = Midnight Commander | releasestatus = Maintained | lastrelease = 4.8.33 | languages = [[C]] | developers = Miguel de Icaza, GNU Project, et al. | website = https://midnight-commander.org/ }} '''GNU Midnight Commander''' (<code>mc</code>) is a dual-pane [[TUI]] file manager. It also includes an internal file viewer (<code>mcview</code>), editor (<code>mcedit</code>), and diff viewer (<code>mcdiff</code>).<ref>[https://midnight-commander.org/ Welcome to Midnight Commander], Yury V. Zaytsev, 2025-03-02 (Accessed: 2025-08-22)</ref> == Overview == The screen of Midnight Commander is divided into four parts, with most of it being taken up by the two directory panels. On the bottom are the function key labels and above it is the shell command line. On the top is the drop down menu accessible with <code>f9</code>.<ref name="MC(1)">[https://source.midnight-commander.org/man/mc.html#Overview MC(1)] (Accessed: 2025-08-22)</ref> == Features == [[File:Mcf.png|thumb|Midnight Commander accessing a tar archive and remote ftp connection]] ==== Remote access ==== Midnight Commander can access remote machines using ftp, sftp or a shell connection. ==== Mouse support ==== Midnight Commander supports mouse input on xterm-compatible terminal emulators or on a Linux virtual console with [[gpm]]. ==== Tar archives ==== Midnight Commander enables read-only access to tar archives.<ref name="MC(1)" /> == References == 49acc806eee751c8fc4c1d8a200e9c0939277587 0 1434 6037 2026-08-24T15:11:01Z Imnotgoodatnames 121 Create redirect with category wikitext text/x-wiki [[Category:File managers]] #REDIRECT [[Finder#GWorkspace]] bb352510e101626faff622e51da31838da3e18c4 6038 6037 2026-08-24T15:11:42Z Imnotgoodatnames 121 Fix redirect hopefully wikitext text/x-wiki #REDIRECT [[Finder#GWorkspace]] [[Category:File managers]] efd7fafcf55371e6e94ccd60e456160d29b3a605 6049 6038 2026-08-25T08:39:23Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:File managers]] #REDIRECT [[Finder#GWorkspace]] bb352510e101626faff622e51da31838da3e18c4 14 1435 6039 2026-08-24T15:16:05Z Imnotgoodatnames 121 Create text editor category wikitext text/x-wiki [[Category:Software]] 3177c712ce9cabbfd5a2ce2820b693582d921e11 0 575 6040 5836 2026-08-24T15:16:56Z Imnotgoodatnames 121 add to category wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|thumb]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.2, Aug 14, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] [[Category:Text editors]] GNU Emacs is a free/libre text editor and interpreter for the Emacs Lisp language, with extensions to assist with various other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, it's strongly recommended to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. ''Also see [[Vim]].'' == References == f8884674235fe699fb25dd0b29b334fc516fb034 0 1120 6041 5351 2026-08-24T15:17:17Z Imnotgoodatnames 121 Add to category wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Vimlogo.svg|thumb]] | caption = Vim | title = Vim | releasestatus = Maintained | lastrelease = 9.2, Feb 14, 2026 | firstrelease = 1.14, Jan, 1992 | languages = [[C]], [[Vim Script]] | developers = [https://github.com/chrisbra/ Christian Brabandt] | website = [https://www.vim.org/ vim.org] | license = Vim License | sourcecode = https://github.com/vim/vim }} [[Category:Software]] [[Category:Text editors]] [[File:Vim-splash.png|thumb|The Vim Splash Screen]] [[Vim]] is a [[Vi]] like text editor that runs in the terminal and stands for "Vi IMproved"<ref name=":0">[https://man.archlinux.org/man/vim.1 Vim.1], Manpages. Published 2025-06-27, accessed 2026-05-22.</ref>. It is considered [[wikipedia:Careware|Charityware]] due to it encouraging users to help children in Uganda by donating to [https://www.kuwasha.net/ Kuwasha]<ref>{{Cite|url=https://vimhelp.org/uganda.txt.html#uganda|title=Vim Reference Manual|author=Bram Moolenaar|year=Feb 14, 2026|accessdate=2026-05-23}}</ref><ref name=":1">[https://www.hostingadvice.com/blog/vim-creator-champions-charityware/ Vim Creator Champions Charityware: Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8], Laura Bernheim, 2016-09-11 (2026-05-22).</ref>. Vim is upwards compatible with Vi<ref name=":0" /> and uses keybindings atypical to that of a standard text editor. Vim is configured using its own programming language, [[Vim Script]]. Vim was originally created by [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] because of the various limitations of [[Vi]]<ref name=":1" />. Vim originally stood for "Vi IMitation"<ref name=":1" />. [[wikipedia:Bram_Moolenaar|Bram Moolenaar]] was the fist maintainer and has since past away in August of 2023<ref>{{Cite|url=https://groups.google.com/g/vim_announce/c/tWahca9zkt4?pli=1|title=Message from the family of Bram Moolenaar, Vim mailing list|author=Bram Moolenaar|year=Aug 5, 2023|accessdate=2026-05-25}}</ref>. A list of Vim maintainers can be found [https://github.com/orgs/vim/people here]. For users wanting to learn Vim, consider using [[Neovim]] instead for a more modern editor and backwards compatible editor, or [[Helix]] if you don't care about being able to use other [[Vi]]-Like editors. ''Also see: [[GNU Emacs|Emacs]].'' ==Usage tips== Most of the same things as [[Vi]] apply to Vim. For learning vim, it is recommended to use <code>vimtutor</code>. You can achieve this by running <code>vimtutor</code> or opening Vim and typing <code>:Tutor</code>, then hitting enter. While this also applies to [[Vi]], It is often joked that Vim is hard to exit, which is not true, exiting Vim can be achieved by entering <code>:wq!</code>, you may have to press the escape key first to enter Normal mode, however. Vim, similar to [[Busybox]], behaves differently depending on the name of the executable or symlink<ref name=":0" />, a list of these different behaviors can be found on the list below. {| class="wikitable" !Name !Behavior |- |vim |Starts Vim normally. |- |view |Starts Vim in read-only mode. |- |ex |Starts vim in "Ex mode" which is an easier way of typing <code>:</code> commands, except no file is often loaded. |- |gex |Starts the GUI. May not always be available. |- |evim |Starts "Easy Vim", sets <code>insertmode</code>. |- |vimdiff |Starts in <code>diff-mode</code>. |} This list is not comprehensive, a full list can be found by running <code>:help starting</code> in Vim and going to <code>Vim arguments</code>. == References == <references /> 22403a131559022bab58e1523f13708cac5821d3 0 736 6042 5903 2026-08-24T15:17:50Z Imnotgoodatnames 121 Add to category wikitext text/x-wiki {{DISPLAYTITLE:ed}} [[category:software]] [[category:Text editors]] [[File:Ed1.png|thumb|Text editor ed]] '''ed''' is a text editor for [[Unix-Like|Unix-like]] operating systems. It is a line editor, meaning it works in a [[CLI]] environment where everything is done by typing commands, and each line is edited one by one. ed, somewhat like its successor [[vi]], works in two modes, ''command'' and ''input''. In command mode characters the user inputs are interpreted as commands, and in input mode they are interpreted as text added to the buffer.<ref>[https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html ed], The IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> ed was part of the original Unix operating system from 1969.<ref>[https://man.cat-v.org/unix-1st/1/ed ed(1)], Unix First Edition Manual Page, 1971-11-03 (Accessed: 2025-08-09)</ref> It remains part of [[POSIX]] and the Open Group standards for UNIX operating systems.<ref>[https://pubs.opengroup.org/onlinepubs/9699919799/utilities/contents.html Shell & Utilities: Detailed Toc], IEEE and The Open Group, 2001-08-09 (Accessed: 2025-08-09)</ref> == Legacy == Due to its reputation as a user-hostile environment, ed has mostly been replaced by [[TUI]] and GUI screen editors and is rarely used today, but it was influential for many popular Unix tools still used today. The command line tool [[grep|<code>grep</code>]] was directly inspired by the ed command <code>g/re/p</code> and [[sed]]'s <code>s/regexp/replacement/</code> command was inherited from ed.<ref>[https://www.gnu.org/software/ed/manual/ed_manual.html GNU 'ed' Manual], GNU, 1993-08-09 (Accessed: 2025-08-09)</ref> ed would serve as a major influence to the line editor [[ex]], from which would later come the screen editor vi, whose variants remain some of the most popular TUI text editors.<ref>[https://ex-vi.sourceforge.net/ex.html ex.1], 2005-03-24 (Accessed: 2025-08-09)</ref><ref>[https://ex-vi.sourceforge.net/vi.html vi.1], 2005-03-24 (Accessed: 2025-08-09)</ref> == References == 3f713ebc0baca44649be73451c3900c1b2fd0d8c 0 756 6043 3607 2026-08-24T15:18:17Z Imnotgoodatnames 121 Add to category wikitext text/x-wiki {{DISPLAYTITLE:ex}} [[category:software]] [[category:Text editors]] [[File:Exedit.png|thumb|nvi text editor in Ex mode]] '''Ex''' is a text editor developed for [[UNIX|Unix]] systems in 1977 as a modified version of em, which was an improved version of the original Unix text editor [[ed]].<ref>[https://man.freebsd.org/cgi/man.cgi?query=vi&manpath=FreeBSD+14.3-RELEASE vi], The FreeBSD Project, 2024-04-18 (Accessed: 2025-08-09)</ref><ref>[https://web.archive.org/web/20240621040052/https://www.groklaw.net/article.php?story=20050422235450910 Groklaw - The Daemon, the Gnu and the Penguin, Ch. 4 & 5 - by Peter H. Salus], Peter H. Salus, 2005-04-22 (Accessed: 2024-06-21)</ref> Like ed, ex is a line editor, meaning commands can only be executed on one line at a time. Ex was eventually modified into a screen editor and became [[vi]]. Modern versions of ex are rarely distributed on their own, but are rather line editor modes of vi text editors.<ref>[https://man.netbsd.org/ex.1 ex(1) - NetBSD Manual Pages], 3rd Berkeley Distribution, 2024-04-28 (Accessed: 2025-08-09)</ref> == References == ed95fb309206726e688b36591c865515f3ee5519 0 909 6044 4150 2026-08-24T15:18:54Z Imnotgoodatnames 121 Add to category wikitext text/x-wiki {{DISPLAYTITLE:nvi}} {{Work In Progress}} [[Category:Software]] [[category:Text editors]] {{SoftwareInfobox | title = '''nvi''' | image = [[File:Nvi.png|thumb]] | caption = Text editor nvi | releasestatus = Maintained | lastrelease = 1.81.6 | languages = [[C]] | developers = Keith Bostic & Sven Verdoolaege | website = [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page Berkeley Vi Editor (nvi) home page.] }} '''nvi''' is a text editor for [[Unix-Like]] operating systems. nvi was originally created as a replacement for the [[vi]] editor and first appeared in 4.4BSD.<ref name="openbsd-manpage">[https://man.openbsd.org/vi.1 Man page for nvi], nvi, April 24, 2024 (Accessed: 2025-09-09)</ref> Unlike other modern implementations of the vi editor such as [[vim]] or [[elvis]], nvi still closely resembles the look and feel of the original vi. == Overview == '''vi''', '''ex''', and '''view''' are all interfaces to the same program, nvi. It is possible to launch nvi in ex mode using the -e option and to launch nvi in view mode using the -R option.<ref name="openbsd-manpage" /> nvi supports all features of vi except open mode and lisp edit options, and it itself includes a number of additional features listed [https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page here].<ref>[https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page nvi home page], nvi, 2024 (Accessed: 2025-09-09)</ref> == References == c4235f5b9c13761771cef8a4e26141e5ab114c20 6 1436 6045 2026-08-25T06:57:24Z Imnotgoodatnames 121 screenshot of a GNUstep desktop running the GWorkspace desktop, file manager, dock and recycle bin wikitext text/x-wiki == Summary == screenshot of a GNUstep desktop running the GWorkspace desktop, file manager, dock and recycle bin == Licensing == {{GPL}} a8f9647096ab39ac2848d42fd4fda2d567a32533 6046 6045 2026-08-25T07:15:09Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:GWorkspace-desktop.png]] wikitext text/x-wiki == Summary == screenshot of a GNUstep desktop running the GWorkspace desktop, file manager, dock and recycle bin == Licensing == {{GPL}} a8f9647096ab39ac2848d42fd4fda2d567a32533 0 202 6050 6015 2026-08-25T08:39:46Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Cleanup|Citations lack information required in the [https://atl.wiki/Policies#Citations guidelines]}} {{MascotInfobox | title = Larry the Cow | image = [[File:Larry the cow.png|Larry the Cow]] | caption = The renowned Larry the Cow }} [[Category:Mascots]] [[File:Larry the cow.png|frame|Larry the Cow]] [[File:Larry-the-cow-full.svg|thumb|Larry the Cow grew black spots (how)]] [[File:emergemoo.png|frame|Need Larry's wisdom? Look no further than "emerge --moo"]] [[File:aptmoo.png|frame|Similar cow output on [[APT]]. Have you mooed today?]] '''Larry the Cow''' is among the unofficial mascots<ref>https://wiki.gentoo.org/wiki/Larry_the_cow Gentoo Wiki, 2023 (Imported 4th June 2024)</ref> of [[Gentoo]], they were originally created by a user called Nefarius.<ref>https://forums.gentoo.org/viewtopic-t-257123-postdays-0-postorder-asc-start-0.html Gentoo Forums, 2003 (imported 4th June 2024)</ref> === Trivia === * Since Larry is a male, a few people argue that they should be called Larry the Bull instead, however a bug report was filed and no action was taken.<ref>https://bugs.gentoo.org/27727 Gentoo Bug Report, 2003 (imported 4th June 2024)</ref> * Larry can be found in [[emerge]] by running <code>emerge --moo</code> Larry can also be found in [[Dpkg|apt]] by running <code>apt moo</code> . * Larry the Cow is from Round Rock, Texas.<ref>https://myspace.com/larrythecow MySpace, (imported 4th June 2024)</ref> * Larry the Cow is listed to be a member of the [https://wiki.gentoo.org/wiki/Project:Catalyst Gentoo Catalyst release building tool] on [https://wiki.gentoo.org/wiki/User:Larry their userpage], however does not have any credit listed. * Larry the Cow's computer is made by Gateway 2000.<ref>https://wiki.gentoo.org/wiki/User:Larry, Gentoo Wiki, 2000 (imported 4th June 2024)</ref> [[File:Larry The Cow with Gentoo Logo.png|thumb|Larry after he grew his black and white patches]] * Larry the cow was a bit frustrated at the current state of Linux distributions until he tried Gentoo Linux.<ref>https://www.gentoo.org/get-started/about/ Gentoo.org (imported 9th June 2026)</ref> == References == <references /> 9c335f741d94a8910cd0b6bb832cc85c512cb886 0 1373 6051 6012 2026-08-25T08:39:56Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki [[Category:Misc Operating Systems]] {{Stub}} <!-- distroinfobox, more info --> {{DistributionInfobox | architectures = i386, x86_64, aarch64<ref>[https://www.osnews.com/story/139255/gnu-hurd-ported-to-aarch64-and-more-hurd-news/ GNU Hurd ported to aarch64 and more hurd news]</ref> | caption = The GNU Hurd logo | defaultdesktops = [[GNOME]], [[Xfce]], [[Window Maker]], [[Fluxbox]], [[IceWM]], [[Openbox]] | image = [[File:Hurd-logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | packagemanager = [[dpkg]]/[[apt]] ([[Debian GNU/Hurd]]), [[Guix]] | releasemodel = Rolling | releasestatus = Experimental | title = GNU/Hurd | usagetype = Research, Development | website = [https://www.gnu.org/software/hurd/ gnu.org/software/hurd] }} [[File:Debian GNU Hurd GNUstep desktop.png|thumb|GNU/Hurd running [[GNU Emacs]], [[Bash|GNU Bash]] and GNU plotutils on the [[GNUstep]] [[desktop Environments|desktop environment.]]]] '''GNU/Hurd''' is an unofficial name for the [[GNU]] operating system running on the '''GNU Hurd''' kernel. GNU Hurd (also referred to as "The Hurd" on GNU's website) is the GNU project's replacement for the [[UNIX]] operating system kernel.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's official Hurd documentation]</ref> It is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html GNU's description of Hurd]</ref> Essentially, The Hurd consists of a set of protocols and server processes (also known as daemons) that run on the GNU [[Mach]] microkernel. This means it differentiates from the [[Linux]] kernel, which is [[monolithic]].<ref>[https://itsfoss.com/news/gnu-hurd-progress-report/ ItsFOSS news report on GNU/Hurd]</ref> It has been in development since 1990, by the [[GNU]] project.<ref>[https://en.wikipedia.org/wiki/GNU_Hurd The Wikipedia entry for GNU Hurd]</ref> == History == '''Richard Stallman''' founded the GNU project in September 1983 with a goal to create a free GNU operating system.<ref>[https://cs.stanford.edu/people/eroberts/courses/cs181/projects/2000-01/open-source/gnu.htm#:~:text=In%201983,%20the%20GNU%20Project,up%20by%20proprietary%20software%20vendors. The history of the GNU project]</ref> Initially, all the necessary components needed for kernel development were made. By 1989, the [[GPL]] came into being, and the only major missing component was the [[kernel]], hence why they added the GNU operating system to [[Linux]] until they had their own kernel.<ref>[https://www.gnu.org/gnu/linux-and-gnu.html "Linux and GNU" entry on GNU's website]</ref> After this, development on the Hurd started after an abandoned kernel attempt, based on the [[TRIX]] operating system.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd History: How it started]</ref> According to the initial architect and founder of Hurd, '''Thomas Bushnell''', one of their early plans was to adopt and build on the [[4.4BSD]]-Lite kernel.<ref>[https://web.archive.org/web/20230710085615/http://www.groklaw.net/article.php?story=20050727225542530 "The Daemon, the GNU and the Penguin"]</ref> Later on from this, Richard Stallman proposed the use of the [[Mach]] microkernel, however this was delayed due to concern on whether the [[Mach]] code would be released under a suitable license.<ref>[https://www.gnu.org/software/hurd/history.html GNU Hurd's history]</ref> Up until now, the development of Hurd had been relatively fast. However, with the release of the free [[Linux]] kernel in 1991, development slowed heavily, but did not stop. GNU's [[userland]] components were quickly put together with the [[Linux]] kernel to create operating systems based on the [[Linux]] kernel ([[Linux distributions]]). == References == 3646d91180fedaa921c9e929ee9f6eb773ecd440 6065 6051 2026-08-25T08:53:12Z Hamachitan 222 /* References */ 🍣 Fix [[FW:Guidelines#Citations|citations]] wikitext text/x-wiki [[Category:Misc Operating Systems]] {{Stub}} <!-- distroinfobox, more info --> {{DistributionInfobox | architectures = i386, x86_64, aarch64<ref>[https://www.osnews.com/story/139255/gnu-hurd-ported-to-aarch64-and-more-hurd-news/ GNU Hurd ported to AArch64, and more Hurd news], Thom Holwerda, 2024-04-11 (Accessed: 2026-08-25)</ref> | caption = The GNU Hurd logo | defaultdesktops = [[GNOME]], [[Xfce]], [[Window Maker]], [[Fluxbox]], [[IceWM]], [[Openbox]] | image = [[File:Hurd-logo.svg{{!}}class=skin-invert|frameless|upright=0.8]] | packagemanager = [[dpkg]]/[[apt]] ([[Debian GNU/Hurd]]), [[Guix]] | releasemodel = Rolling | releasestatus = Experimental | title = GNU/Hurd | usagetype = Research, Development | website = [https://www.gnu.org/software/hurd/ gnu.org/software/hurd] }} [[File:Debian GNU Hurd GNUstep desktop.png|thumb|GNU/Hurd running [[GNU Emacs]], [[Bash|GNU Bash]] and GNU plotutils on the [[GNUstep]] [[desktop Environments|desktop environment.]]]] '''GNU/Hurd''' is an unofficial name for the [[GNU]] operating system running on the '''GNU Hurd''' kernel. GNU Hurd (also referred to as "The Hurd" on GNU's website) is the GNU project's replacement for the [[UNIX]] operating system kernel.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html What Is the GNU Hurd?], GNU, 2010-12-07 (Accessed: 2026-08-25)</ref> It is firstly a collection of protocols formalizing how different components may interact. The protocols are designed to reduce the mutual trust requirements of the actors thereby permitting a more extensible system.<ref>[https://www.gnu.org/software/hurd/hurd/what_is_the_gnu_hurd.html What Is the GNU Hurd?], GNU, 2010-12-07 (Accessed: 2026-08-25)</ref> Essentially, The Hurd consists of a set of protocols and server processes (also known as daemons) that run on the GNU [[Mach]] microkernel. This means it differentiates from the [[Linux]] kernel, which is [[monolithic]].<ref>[https://itsfoss.com/news/gnu-hurd-progress-report/ 36 Years in Making, GNU's Very Own Kernel Project Hurd is Anything But Dead], Sourav Rudra, 2026-02-03 (Accessed: 2026-08-25)</ref> It has been in development since 1990, by the [[GNU]] project.<ref>[https://en.wikipedia.org/wiki/GNU_Hurd GNU Hurd], Wikipedia contributors, 2026-07-22 (Accessed: 2026-08-25)</ref> == History == '''Richard Stallman''' founded the GNU project in September 1983 with a goal to create a free GNU operating system.<ref>[https://cs.stanford.edu/people/eroberts/courses/cs181/projects/2000-01/open-source/gnu.htm#:~:text=In%201983,%20the%20GNU%20Project,up%20by%20proprietary%20software%20vendors. GNU], 2001-03-20 (Accessed: 2026-08-25)</ref> Initially, all the necessary components needed for kernel development were made. By 1989, the [[GPL]] came into being, and the only major missing component was the [[kernel]], hence why they added the GNU operating system to [[Linux]] until they had their own kernel.<ref>[https://www.gnu.org/gnu/linux-and-gnu.html Linux and GNU], GNU Project, 2001-08-25 (Accessed: 2026-08-25)</ref> After this, development on the Hurd started after an abandoned kernel attempt, based on the [[TRIX]] operating system.<ref>[https://www.gnu.org/software/hurd/history.html History], GNU Project, 1998-08-25 (Accessed: 2026-08-25)</ref> According to the initial architect and founder of Hurd, '''Thomas Bushnell''', one of their early plans was to adopt and build on the [[4.4BSD]]-Lite kernel.<ref>[https://web.archive.org/web/20230710085615/http://www.groklaw.net/article.php?story=20050727225542530 Groklaw - The Daemon, the GNU and the Penguin - Ch. 16], Dr. Peter Salus, 2003-08-25 (Accessed: 2023-07-10)</ref> Later on from this, Richard Stallman proposed the use of the [[Mach]] microkernel, however this was delayed due to concern on whether the [[Mach]] code would be released under a suitable license.<ref>[https://www.gnu.org/software/hurd/history.html History], GNU Project, 1998-08-25 (Accessed: 2026-08-25)</ref> Up until now, the development of Hurd had been relatively fast. However, with the release of the free [[Linux]] kernel in 1991, development slowed heavily, but did not stop. GNU's [[userland]] components were quickly put together with the [[Linux]] kernel to create operating systems based on the [[Linux]] kernel ([[Linux distributions]]). == References == 68765ba4e5e51909682eef63c1d7a894b24fabc8 0 791 6052 5993 2026-08-25T08:40:15Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} Marked as WIP as defining how to categorise languages. Ideas include paradigm and primary use case, former option is a bit less debated but less accessible to a newer programmer and the latter makes the purposes clear but a lot of languages blur the lines. f9e56809f3e7d82d3da9ca5b2f5b3e640bbd43c1 0 622 6053 5991 2026-08-25T08:40:25Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki A desktop environment (DE) is a group of programs that are used to display information and allow the user to interact with the computer, often using a [[GUI]] or [[TUI]]. A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets.<gallery mode="packed" widths="200" heights="200"> File:Budgie-Screenshot-Raven-RU.png|[[Budgie]] File:LinuxMint22-Wilma-English.png|[[Cinnamon]] File:COSMIC Epoch 1.0.0 alpha with apps.png|[[COSMIC]] File:Enlightenment-screenshot-2021.png|[[Enlightenment]] File:GNOME 43.png|[[GNOME]] File:Lxqt-screenshot-about.png|[[LXQt]] File:MATEDesktop.png|[[MATE]] File:KDE Plasma 5.26 screenshot.png|[[KDE Plasma]] File:Trinity R.14.1.3 screenshot.png|[[Trinity Desktop Environment]] File:XFCE-4.18-Desktop.png|[[Xfce]] File:LXDE-Qt preview.png|[[LXDE]] </gallery> {| class="wikitable" |+Desktop Environments !Name !Description |- |[[Budgie]] |The [[Budgie|Budgie Desktop]] is a modern [[Desktop Environment|desktop environment]] based on [[GNOME]] designed to keep out the way of the user. Budgie is written in [[Vala]]. |- |[[Cinnamon]] |[[Cinnamon]] is a Desktop Environment originally based on GNOME 3, developed by the [[Linux Mint]] team and written in [[JavaScript]]. |- |[[COSMIC]] |[[COSMIC]] is a Desktop Environment developed by [[system76]], also known as the creators of [[Pop! OS|Pop! OS.]] COSMIC is built in [[Rust]] and is notable for having automatic window tiling built into the desktop as a primary feature. |- |[[Enlightenment]] |[[Enlightenment]] is a desktop environment and window manager for [[Linux]] and other [[Unix-Like|Unix-Based]] [[Operating System|Operating Systems]] written in [[C]] and [[ELF]]. |- |[[GNOME]] |[[GNOME]] is a popular desktop environment and is the default desktop environment for a large number of operating systems. GNOME is written in a variety of languages, but primarily is built in [[C]]. |- |[[LXDE]] |[[LXDE]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Written in [[C]]. |- |[[LXQt]] |[[LXQt]] is a desktop environment built on [[Qt]] which derives from [[Razor-qt]] and [[LXDE]] components which were ported to [[Qt]]. |- |[[MATE]] |[[MATE]] is a lightweight desktop environment continuation of GNOME 2 and is coded in [[Python]] and [[C++]]. |- |[[Plasma]] |[[Plasma|KDE Plasma]] is a highly customizable and popular and is coded in [[C++]] and [[QML]]. |- |[[Trinity Desktop Environment]] |[[Trinity Desktop Environment]] is an desktop environment forked from [[Plasma|KDE]] 3 coded in [[C]]. |- |[[Xfce]] |[[Xfce]] is a lightweight desktop environment aiming to be fast for weaker hardware while still remaining user friendly. Coded in [[C]]. |} b3b577b60668145a0375fc9b11fb886f6507dde6 0 1416 6054 5990 2026-08-25T08:40:35Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | image = [[file:Msys2-icon.png|frameless|upright=0.5|MSYS2 icon]] | caption = MSYS2 icon <!-- Icon used instead of logo due to logo's unclear licensing. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://https://www.msys2.org// msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2 home page]</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?]</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 - MSYS2]</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64]</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by <ref name=envs>[https://www.msys2.org/docs/environments/ Environments - MSYS2]</ref> {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |UCRT64 |<code>/ucrt64</code> |gcc |UCRT |x86_64 |- |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS. It is always active, all other environments inherit from it and add their own environment variables on top. === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure compatibility with ARM, not to install an ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11 (#96) - MSYS2 Installer - Github issues ]</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue MSYS2 Packages]</ref> {| class="wikitable" !Environment !Package name prefix |- |MSYS |None (no package name prefix) |- |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |MINGW32 |<code>mingw-w64-</code> |- |MINGW64 |<code>mingw-w64-x86_64-</code> |- |CLANG32 |None (environment fully deprecated)<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment Removal of the CLANG32 environment]</ref> (historically <code>mingw-w64-clang-i686</code>)<ref>[https://www.msys2.org/docs/package-naming/ Package Naming - MSYS2]</ref> |} == References == f60eab53b96d7b20c080e126b7dd919f337e3c53 6064 6054 2026-08-25T08:48:43Z Hamachitan 222 /* References */ 🍣 Fix [[FW:Guidelines#Citations|citations]] wikitext text/x-wiki {{Work In Progress}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | image = [[file:Msys2-icon.png|frameless|upright=0.5|MSYS2 icon]] | caption = MSYS2 icon <!-- Icon used instead of logo due to logo's unclear licensing. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://https://www.msys2.org// msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 Support], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64], David Allsopp, 2018-08-25 (Accessed: 2026-08-25)</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by <ref name=envs>[https://www.msys2.org/docs/environments/ Environments], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |UCRT64 |<code>/ucrt64</code> |gcc |UCRT |x86_64 |- |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS. It is always active, all other environments inherit from it and add their own environment variables on top. === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" !Environment !Prefix !Compiler toolchain !C library !Architecture |- |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure compatibility with ARM, not to install an ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11], Blackhex, 2025-02-26 (Accessed: 2026-08-25)</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue Pending Package Updates], MSYS2 Packages, 2026-08-25 (Accessed: 2026-08-25)</ref> {| class="wikitable" !Environment !Package name prefix |- |MSYS |None (no package name prefix) |- |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |MINGW32 |<code>mingw-w64-</code> |- |MINGW64 |<code>mingw-w64-x86_64-</code> |- |CLANG32 |None (environment fully deprecated)<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment News], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> (historically <code>mingw-w64-clang-i686</code>)<ref>[https://www.msys2.org/docs/package-naming/ Package Naming], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> |} == References == b5bb9103a299bfd01811f35afb8e5786f554c3bf 0 1418 6055 5985 2026-08-25T08:40:45Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} {{Needs Citations}} '''Vanadium''' is a security and privacy enhanced [[Chromium]]-based browser for the [[GrapheneOS]] operating system, serving as the WebView implementation for rendering content within apps and also acting as the browser for the user. It features strong isolation, and utilizes numerous patches to help Vanadium achieve increased privacy and security for the user. Vanadium heavily relies on GrapheneOS' system-level patches to be able to utilize features which the browser requires features from the operating system to run, such as certain types of exploit mitigation. == Features == * Hardware memory tagging enabled for the main allocator * Type-based CFI (control flow integrity) * Hardened stack protector * Strict, hardened site isolation & sandboxing * Battery API giving deliberate incorrect information to avoid fingerprinting * Widely unused features such as WebGPU disabled to decrease attack surface * Client hints replaced with [[Chromium]]'s reduced user agent to prevent fingerprinting 703e3a63502c7e32831d36939242617acb9bf98e 0 1417 6056 5983 2026-08-25T08:40:55Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Stub}} '''Trivalent''' is a security-focused, [[Chromium]]-based browser for desktop [[Linux]] inspired by [[GrapheneOS]]' [[Vanadium]] browser.<ref>[https://github.com/secureblue/Trivalent/blob/live/docs/README.md Github repository for Trivalent]</ref> Trivalent's primary focus is to achieve the security of [[Chromium]] based browsers, while removing telemetry and other tracking elements as well as including some patches to help secure the browser furthermore. It is the default browser on the [[Secureblue]] Linux distribution. == Features == * Contains numerous patches from the [[Vanadium]] browser designed to enhance security * Contains additional patches on top of the Vanadium patches and existing [[Chromium]] patches to enhance security * Automatic disabling of telemetry * Automatically opt-out of optional services included by default (e.g the password manager) * Simple and small UX changes which can be easily disabled == Privacy == Trivalent is ''not'' privacy focused. Instead, Trivalent's primary focus is security. This does mean that Trivalent may lack some features which give a benefit to privacy, but sell out on some security or do little to contribute to it. This only affects a tiny amount of changes, however, with most privacy-selling features disabled entirely. ee08c2b018f8f02df62c41bff00ba9a7b825910e 6063 6056 2026-08-25T08:46:54Z Hamachitan 222 /* References */ 🍣 Fix [[FW:Guidelines#Citations|citations]] wikitext text/x-wiki {{Stub}} '''Trivalent''' is a security-focused, [[Chromium]]-based browser for desktop [[Linux]] inspired by [[GrapheneOS]]' [[Vanadium]] browser.<ref>[https://github.com/secureblue/Trivalent/blob/live/docs/README.md Trivalent], secureblue, 2026-08-25 (Accessed: 2026-08-25)</ref> Trivalent's primary focus is to achieve the security of [[Chromium]] based browsers, while removing telemetry and other tracking elements as well as including some patches to help secure the browser furthermore. It is the default browser on the [[Secureblue]] Linux distribution. == Features == * Contains numerous patches from the [[Vanadium]] browser designed to enhance security * Contains additional patches on top of the Vanadium patches and existing [[Chromium]] patches to enhance security * Automatic disabling of telemetry * Automatically opt-out of optional services included by default (e.g the password manager) * Simple and small UX changes which can be easily disabled == Privacy == Trivalent is ''not'' privacy focused. Instead, Trivalent's primary focus is security. This does mean that Trivalent may lack some features which give a benefit to privacy, but sell out on some security or do little to contribute to it. This only affects a tiny amount of changes, however, with most privacy-selling features disabled entirely. 63dbe1d9697b34b587518cc0abbc73f893d0d38c 0 277 6057 5968 2026-08-25T08:41:06Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Needs_Citations}} {{Stub}} {{DistributionInfobox | title = Rocky Linux | image = [[File:Rocky_Linux_wordmark.svg | thumb | Rocky Linux official logo]] | releasestatus = Maintained | releasemodel = Stable | packagemanager = [[dnf]] | defaultdesktops = [[GNOME]] | usagetype = Desktop, Server | architectures = x86-64-v2, s390x, ppc64el, ARM64 | website = [https://rockylinux.org rockylinux.org] }} [[Category:Linux Distributions]] [[File:Rocky Linux 9 Workstation showing GNOME Shell 40.png | thumb | Screenshot of Rocky Linux desktop]] Rocky Linux is a Linux distribution developed by RESF (Rocky Enterprise Software Foundation), which is a privately owned benefit corporation that describes itself as a "self-imposed not-for-profit".<ref>{{Cite|url=https://www.resf.org/faq/is-resf-nonprofit|title=Is the RESF a non-profit? - RESF FAQ|author=RESF|accessdate=14 September 2025}}</ref> It is intended to be a downstream binary-compatible release using the [[RHEL|Red Hat Enterprise Linux (RHEL)]] operating system source code. The project's aim is to provide a production-grade enterprise operating system. Rocky Linux has become popular for enterprise operating system use. = Migration = You can migrate to Rocky Linux from CentOS Stream, CentOS, AlmaLinux, RHEL, or Oracle Linux. To do this, you need a handy tool called [https://docs.rockylinux.org/guides/migrate2rocky migrate2rocky]. It is a script that, when run, will change out all of your repositories to those of Rocky Linux. Packages will install and upgrade or down-grade as necessary, and your operating system's branding will also change. === Caveats and warnings === Do check out migrate2rocky's README page, because known clashes exist. This script is most likely to work without incident on completely fresh installs. If you want to convert a production server, '''make a data backup and system snapshot''', or do it in a staging environment first. 219f2f70934ad43a0a4d5a6716298a21b1bd5b2d 0 1412 6058 5966 2026-08-25T08:41:16Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{SoftwareInfobox | title = openQA | releasestatus = Maintained | firstrelease = 2013-05-14<ref>[https://build.opensuse.org/projects/openSUSE:Factory/packages/openQA/files/openQA.changes?expand=1 openQA], openQA.changes changelog (Accessed: 2026-08-06) </ref> | lastrelease = rolling release model | languages = Perl, Javascript, Shell, SCSS and other | developers = [[SUSE]], [[openSUSE]] | website = [https://open.qa openQA] | sourcecode = https://github.com/os-autoinst/openQA | license = GPLv2 }} openQA is an automated test tool developed by openSUSE and SUSE that makes it possible to test the whole installation process of an operating system. <ref>[https://open.qa/documentation/ openQA Documentation]</ref> == References == <references /> b881db761fa23fcc316a00c42d58d14fab340601 6062 6058 2026-08-25T08:46:07Z Hamachitan 222 /* References */ 🍣 Fix [[FW:Guidelines#Citations|citations]] wikitext text/x-wiki {{SoftwareInfobox | title = openQA | releasestatus = Maintained | firstrelease = 2013-05-14<ref>[https://build.opensuse.org/projects/openSUSE:Factory/packages/openQA/files/openQA.changes?expand=1 openQA], openQA.changes changelog (Accessed: 2026-08-06)</ref> | lastrelease = rolling release model | languages = Perl, Javascript, Shell, SCSS and other | developers = [[SUSE]], [[openSUSE]] | website = [https://open.qa openQA] | sourcecode = https://github.com/os-autoinst/openQA | license = GPLv2 }} openQA is an automated test tool developed by openSUSE and SUSE that makes it possible to test the whole installation process of an operating system. <ref>[https://open.qa/documentation/ Documentation], SUSE LLC, 2026-08-21 (Accessed: 2026-08-25)</ref> == References == <references /> b17aee56fc3c91e8f46f96118d6b96f2331a1903 0 1411 6059 5960 2026-08-25T08:41:26Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{DISPLAYTITLE:mpv}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Unofficial Mpv logo (with gradients).svg|150px]] | caption = The mpv Logo | title = mpv | releasestatus = Maintained | lastrelease = 0.41.0 | languages = [[C]], [[Lua]], [[Swift]] | developers = | website = https://mpv.io/ | sourcecode = https://github.com/mpv-player/mpv | license = GPLv2 }} '''mpv''' is a media player accessible through the command line.<ref>https://mpv.io/</ref> It uses configurable keyboard shortcuts to control video and audio during playback, such as speed, volume, audio tracks, subtitles, etc. It supports scripting through [[Lua]] and [[JavaScript]].<ref>https://mpv.io/manual/stable/#lua-scripting</ref> mpv is often embeded as a media frontend for command line software such as [https://github.com/Benexl/yt-x yt-x]. <ref>https://mpv.io/manual/stable/#embedding-into-other-programs-libmpv</ref><ref>https://github.com/mpv-player/mpv/wiki/Applications-using-mpv</ref> 75ea59a6cf4cfd93b675b0d7c0bbe1ad24d56f51 6061 6059 2026-08-25T08:45:36Z Hamachitan 222 /* References */ 🍣 Fix [[FW:Guidelines#Citations|citations]] wikitext text/x-wiki {{DISPLAYTITLE:mpv}} [[Category:Software]] {{SoftwareInfobox | image = [[File:Unofficial Mpv logo (with gradients).svg|150px]] | caption = The mpv Logo | title = mpv | releasestatus = Maintained | lastrelease = 0.41.0 | languages = [[C]], [[Lua]], [[Swift]] | developers = | website = https://mpv.io/ | sourcecode = https://github.com/mpv-player/mpv | license = GPLv2 }} '''mpv''' is a media player accessible through the command line.<ref>[https://mpv.io/ mpv.io], mpv.io, 2026-06-28 (Accessed: 2026-08-25)</ref> It uses configurable keyboard shortcuts to control video and audio during playback, such as speed, volume, audio tracks, subtitles, etc. It supports scripting through [[Lua]] and [[JavaScript]].<ref>[https://mpv.io/manual/stable/#lua-scripting LUA SCRIPTING], mpv.io, 2026-06-28 (Accessed: 2026-08-25)</ref> mpv is often embeded as a media frontend for command line software such as [https://github.com/Benexl/yt-x yt-x]. <ref>[https://mpv.io/manual/stable/#embedding-into-other-programs-libmpv EMBEDDING INTO OTHER PROGRAMS (LIBMPV)], mpv.io, 2026-06-28 (Accessed: 2026-08-25)</ref><ref>[https://github.com/mpv-player/mpv/wiki/Applications-using-mpv Applications using mpv], mpv-player/mpv Wiki, 2026-08-25 (Accessed: 2026-08-25)</ref> 0ce9075f6088f96780b0521ed4f913ee0517880f 0 1409 6060 5955 2026-08-25T08:42:41Z Hamachitan 222 🍣 Format preamble wikitext text/x-wiki {{Work In Progress}} {{DISPLAYTITLE:dwl}} {{SoftwareInfobox | caption = dwl logo | developers = dwl devs and community patches | firstrelease = dwl 0.2.2, 2021-12-22 | languages = [[C]] | lastrelease = dwl 0.8, 2025-12-28 | title = dwl | website = [https://codeberg.org/dwl/dwl Codeberg repo of dwl] | releasestatus = Maintained | image = [[File:dwl-logo.png|thumb|center]] }} '''dwl''' is a minimal, hackable dynamically tiling [[Wayland Compositors|Wayland compositor]] aiming to replicate the look and feel of [[dwm]]. It adapts many of dwm's features including: * Dynamic tiling * Simple window borders * Tags * Client rules * Good mouse integration * One simple <code>config.h</code> file responsible for its configuration * Extensible with patches There are many more features it supports out of the box that are listed under its own Codeberg repository<ref>{{Cite|url=https://codeberg.org/dwl/dwl#background|title=Out of the box support|accessdate=2026-07-31}}</ref>. == Patches == dwl adds the ability to add custom functionality by letting you patch its code. 5785b7840d708fa67659754dbf08e9292256d716 0 718 6069 5454 2026-08-26T14:00:48Z Imnotgoodatnames 121 Add finder part to features wikitext text/x-wiki {{DISPLAYTITLE:macOS}} [[File:Apple-Logo-Transparent.png|thumb|right]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical [[Operating System|operating systems]] developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a [[UNIX]] (Darwin/[[BSD]]) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Finder === The default file manager and [[shell|desktop shell]] on all versions of [[macOS]]. It is used for managing disk drives, files and desktop icons as well as launching applications. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/{{Dead Link|2026-05-26|timeout (10)}}|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> cc232262df3307e828fc025be837a05afb18e044 0 1398 6071 5978 2026-08-26T14:04:07Z Imnotgoodatnames 121 Add GWorkspace thing wikitext text/x-wiki {{SoftwareInfobox | title = GNUstep | caption = GNUstep logo | releasestatus = Maintained | developers = GNUstep developers, GNU Project | image = [[File:GNUstep logo.png{{!}}class=skin-invert|200px|GNUstep_logo]] | languages = [[Objective-C]] | lastrelease = Varied (GNUstep components often have independent releases)<ref>[https://github.com/gnustep GNUstep Github]</ref> | website = [https://www.gnustep.org/ gnustep.org] }} [[File:GNUstep_desktop.png|thumb|GNUstep managing its own windows, with the Macintosh menu interface style.]] '''GNUstep''' is a [[Free_and_Open_Source_Software|free]] implementation of Apple's [[Cocoa]] API and a collection of software based on that API. It is a part of the [[GNU]] project. Both GNUstep and Cocoa share the same OpenStep roots.<ref name="website">[https://gnustep.org GNUstep homepage]</ref> GNUstep supports many unique features such as special menu bar behaviour, which can be configured to act like NeXTSTEP's, [[Microsoft Windows]]' or even [[macOS]]' (with the menu bar of supported applications displayed as a small seperate window, as part of the application window or on top of the display, respectively). It can also manage windows and window decorations of any supported app, therefore technically bypassing the need for a seperate [[X_Window_Manager|window manager]], though non-GNUstep windows will remain unmanaged.<ref>[https://www.gnustep.org/resources/documentation/User/Gui/DefaultsSummary.html User Defaults Summary for GNUstep Libraries]</ref> GNUstep is cross platform and supports [[UNIX]] and Unix-like systems and Microsoft Windows. On Unix and Unix-like systems it runs primarily on [[X_Window_System|X]] with limited support for [[Wayland]].<ref>[https://home.gnustep.org/windows/installer.html Windows Installer]</ref><ref>[https://www.phoronix.com/news/GNUstep-0.29-With-Wayland GNUstep Releases Early Wayland Support, Many Other Improvements Too]</ref> [[Window Maker]] is the most common window manager used with GNUstep due to its limited integration with it and their shared default NeXTSTEP-inspired aesthetics.<ref>[https://mediawiki.gnustep.org/index.php/Window_Maker Window Maker]</ref> == Applications == GNUstep '''applications''' are distributed in the form of portable application bundles. Like on macOS, they are regular directories with the '.app' suffix that contain the [[executable]] itself, the application icon and various metadata, such as the application version.<ref>[https://www.gnustep.org/resources/documentation/Developer/Base/Reference/NSBundle.html NSBundle class reference]</ref> === Example GNUstep application === <syntaxhighlight lang="text"> TextEdit.app ├── Resources │ ├── ApplicationScripting.xlp │ ├── Edit.tiff │ ├── EditTitle.tiff │ ├── Encodings.txt │ ├── English.lproj │ ├── Info-gnustep.plist │ ├── ScriptingInfo.plist │ ├── TextEdit.desktop │ ├── rtf.tiff │ ├── rtfd.tiff │ └── text.tiff ├── TextEdit └── stamp.make </syntaxhighlight> == GWorkspace == {{SoftwareInfobox | title = GWorkspace | image = [[File:GWorkspace-resized.png|128px]] | releasestatus = Maintained | lastrelease = 1.1.0 | caption = GWorkspace application icon | languages = [[Objective-C]]<ref name=git>[https://github.com/gnustep/apps-gworkspace GWorkspace], GNUstep, 2026-08-25 (Accessed: 2026-08-25)</ref> | developers = GNUstep project | website = [https://www.gnustep.org/experience/GWorkspace.html GWorkspace] | license = [[GPL|GPLv2]] | sourcecode = https://github.com/gnustep/apps-gworkspace }} [[File:GWorkspace-desktop.png|thumb|GWorkspace as a file manager and graphical shell, managing the recycle bin, desktop settings, desktop icons and an application dock on a GNUstep desktop.]] '''GWorkspace''' is a GNUstep reimplementation of the NeXTSTEP file manager and the GNUstep equivalent of [[Finder]]. It is a file manager application and, optionally, a desktop shell that provides a customizable desktop with desktop icons and an application dock.<ref name=site>[https://www.gnustep.org/experience/GWorkspace.html GNUstep Workspace Manager: GWorkspace], GNUstep, 2025-02-24 (Accessed: 2026-08-25)</ref> It provides various features of a desktop shell including a recycle bin, a desktop preferences window and previews for images and other files.<ref>[https://mediawiki.gnustep.org/index.php/GWorkspace.app GWorkspace.app], GNUstepWiki, 2025-12-25 (Accessed: 2026-08-25)</ref> === Gershwin Workspace === '''Workspace''' is a fork of GWorkspace for the [[Gershwin|Gershwin desktop environment.]] Like the rest of Gershwin, it aims to bring a more macOS-like experience to the desktop and therefore includes features such as thumbnail previews for files and the ability to place the dock on the bottom of the desktop as opposed to just the right or left.<ref>[https://github.com/gershwin-desktop/gershwin-workspace gershwin-desktop/gershwin-workspace: Fork of GWorkspace with modifications for Gerswhin], gershwin-desktop, 2026-08-25 (Accessed: 2026-08-25)</ref> == References == 79861bf1ec5f84382c2f1143d52daae6f348b848 0 1434 6072 6049 2026-08-26T14:04:26Z Imnotgoodatnames 121 Fix redirect wikitext text/x-wiki [[Category:File managers]] #REDIRECT [[GNUstep#GWorkspace]] be9c033c1379e2da7c6ea2c17253826aba357fe0 6073 6072 2026-08-26T14:04:45Z Imnotgoodatnames 121 Fix redirect for real wikitext text/x-wiki #REDIRECT [[GNUstep#GWorkspace]] [[Category:File managers]] b6165693f14685d748f5922cf3208bd8b3602ba9 0 718 6074 6069 2026-08-26T14:42:23Z Imnotgoodatnames 121 Add entry for FOSS alternatives to macOS apps and macOS itself (since foss is the primary focus of the wiki). Also replaced the apple logo with a black/white one since i'm not 100% sure the old one was also public domain. wikitext text/x-wiki {{DISPLAYTITLE:macOS}} [[File:Apple_logo_black.svg{{!}}class=skin-invert|thumb|upright=0.8|right|Apple logo]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical [[Operating System|operating systems]] developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a [[UNIX]] (Darwin/[[BSD]]) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Finder === The default file manager and [[shell|desktop shell]] on all versions of [[macOS]]. It is used for managing disk drives, files and desktop icons as well as launching applications. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/{{Dead Link|2026-05-26|timeout (10)}}|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == FOSS alternatives == There are many viable [[FOSS]] alternatives for Apple software. Many applications in macOS can be replaced by open-source ones, such as iTerm2 instead of the [[Terminal emulator|Terminal]] app or [[VLC]] instead of the QuickTime Player. [[Linux Distributions|Linux-based]] and [[BSD]] operating systems, among others, provide a free Unix-like core operating system. [[GNUstep]] is a free implementation of Apple's Cocoa API and includes features common on macOS, such as .app Application bundles, enabling a macOS-like environment on operating systems running [[X Window System|X]] or [[Wayland]]. It also includes [[GWorkspace]], a Finder equivalent that provides a file manager, desktop icons, a dock and various other desktop features. [[Gershwin]] is a GNUstep-based [[desktop Environments|desktop environment]] that aims to replicate the look and feel of the macOS desktop on [[X11]]. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> 798b36fb2d7762b8b5221236550fe6e3478d8e34 6076 6074 2026-08-27T11:25:24Z Imnotgoodatnames 121 Add more info on FOSS wikitext text/x-wiki {{DISPLAYTITLE:macOS}} [[File:Apple_logo_black.svg{{!}}class=skin-invert|thumb|upright=0.8|right|Apple logo]] '''macOS''' (pronounced “mack-oh-es”) is a family of proprietary graphical [[Operating System|operating systems]] developed and maintained by '''Apple Inc.''' It runs exclusively on Mac computers—including MacBook, iMac, Mac mini, and Mac Pro—and is built upon a [[UNIX]] (Darwin/[[BSD]]) foundation. macOS is renowned for its polished interface, deep ecosystem integration, and emphasis on security and privacy. == History == === Early Origins (2001–2005) === The operating system debuted as **Mac OS X** on 24 March 2001. It introduced a modern UNIX-based core derived from NeXTSTEP and BSD, featuring memory protection, preemptive multitasking, and a rich visual interface powered by Quartz<ref>{{Cite|title=Darwin (operating system)|url=https://en.wikipedia.org/wiki/Darwin_%28operating_system%29|author=Wikipedia contributors|year=2025}}</ref>. === OS X Era (2006–2015) === * In 2006, Apple shifted to Intel processors, enabling macOS to run on x86‑64 architecture<ref>{{Cite|title=MacOS architecture|url=https://en.wikipedia.org/wiki/MacOS|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.12 Sierra introduced Siri, APFS, and improvements to storage management<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref>. * macOS 10.13 High Sierra (2017) fully adopted APFS for all SSDs, improving performance and security. === Apple Silicon & Modern Era (2020–2024) === * Released in 2020, **macOS 11 Big Sur** transitioned macOS visually and as part of supporting Apple Silicon (M1) architecture. * **macOS 14 Sonoma** (2023) introduced interactive desktop widgets, Game Mode, and Safari enhancements. * **macOS 15 Sequoia** (2024) included iPhone Mirroring, Passwords app, and expanded Apple Intelligence<ref>{{Cite|title=MacOS Sequoia|url=https://en.wikipedia.org/wiki/MacOS_Sequoia|author=Wikipedia contributors|year=2025}}</ref>. === Latest Release: macOS 26 “Tahoe” (2025) === Announced at WWDC on 9 June 2025, the operating system is expected for public release in fall 2025<ref>{{Cite|title=macOS Tahoe|url=https://en.wikipedia.org/wiki/MacOS_Tahoe|author=Wikipedia contributors|year=2025}}</ref>. Major new features include: * '''Liquid Glass''' design with refined frosted transparency in menus, Control Center, Dock, and sidebars<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * AI-enhanced Spotlight featuring Quick Keys and in-app actions<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Phone app integration and Live Activities support via Continuity<ref>{{Cite|title=macOS Tahoe 26 is official: here's everything...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref>. * Metal 4 and a dedicated Games app with Game Overlay and Low Power Mode<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. * Expanded accessibility: Accessibility Reader, Vehicle Motion Cues, and Braille Access<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. * Final major release supporting Intel Macs; future versions will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Architecture == macOS combines proprietary and open-source components: * '''Darwin'''—open-source base (kernel, drivers), introduced 2000 * '''XNU'''—hybrid kernel (Mach microkernel + BSD), supporting x86-64 and ARM64<ref>{{Cite|title=XNU|url=https://en.wikipedia.org/wiki/XNU|author=Wikipedia contributors|year=2025}}</ref> * '''APFS'''—Apple File System (since High Sierra), optimized for encryption and snapshots<ref>{{Cite|title=Apple File System|url=https://en.wikipedia.org/wiki/Apple_File_System|author=Wikipedia contributors|year=2025}}</ref> == User Experience & Core Features == === Liquid Glass UI === A sleek design language using subtle translucency and refined glass-like elements across system UI, Dock, menu bar, and windows<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Finder === The default file manager and [[shell|desktop shell]] on all versions of [[macOS]]. It is used for managing disk drives, files and desktop icons as well as launching applications. === Spotlight === Now supports file/app search, clipboard history, in-app commands, Quick Keys, and Apple Intelligence-enhanced actions<ref>{{Cite|title=Apple’s updated Spotlight...|url=https://www.digitaltrends.com/computing/apples-updated-spotlight-is-the-best-upgrade-in-macos-tahoe/{{Dead Link|2026-05-26|timeout (10)}}|author=Digital Trends|year=2025}}</ref>. === Continuity & Phone Integration === Includes a native Phone app for calls, voicemails, call screening, and Live Activities synced from iPhone to Mac<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref>. === Apple Intelligence & Shortcuts === AI-powered workflows in Shortcuts app, image generation via Genmoji/Image Playground, text summarization with Apple Intelligence models<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Games & Metal 4 === Game Launcher, overlay for live chat/settings, and optimized low-power mode; new Metal 4 framework improves performance<ref>{{Cite|title=The Top New Features in MacOS Tahoe|url=https://www.wired.com/story/macos-26-tahoe-top-features/|author=WIRED|year=2025}}</ref>. === Accessibility Features === Imagery Reader, Vehicle Motion Cues, enhanced Braille Access, using AI and ordinals across system<ref>{{Cite|title=macOS Tahoe makes the Mac more capable...|url=https://www.apple.com/newsroom/2025/06/macos-tahoe-26-makes-the-mac-more-capable-productive-and-intelligent-than-ever/|author=Apple Inc.|year=2025}}</ref>. == Supported Hardware == macOS 26 Tahoe supports: * Apple Silicon (M1–M4) machines * A limited set of Intel Macs, including Intel MacBook Pro (2019–2020), select Intel iMac, Intel Mac mini, and Mac Pro models<ref>{{Cite|title=Does your Mac support macOS Tahoe 26?|url=https://www.techradar.com/computing/mac-os/does-your-mac-support-macos-tahoe-26-heres-the-full-list-of-compatible-macbooks-and-macs|author=TechRadar|year=2025}}</ref>. All future updates will require Apple Silicon<ref>{{Cite|title=We've Finally Reached the End of the Road for Intel Macs|url=https://www.wired.com/story/macos-tahoe-last-update-for-intel-macs/|author=WIRED|year=2025}}</ref>. == Release Cadence == Apple releases macOS annually following this schedule: # June: WWDC announcement & developer beta # July: Public beta via Apple Beta Software Program # September–October: General public release<ref>{{Cite|title=macOS Tahoe 26 is official...|url=https://www.techradar.com/computing/mac-os/macos-tahoe|author=TechRadar|year=2025}}</ref> == Security & Privacy == macOS emphasizes safeguarding user data: * '''System Integrity Protection''' (SIP) to prevent unauthorized system modifications * '''FileVault''' full-disk encryption * '''Passkeys''' via iCloud Keychain * '''Rapid Security Responses''' allow patching without full OS installs * On-device AI to minimize data sharing with cloud<ref>{{Cite|title=macOS now has a phone app...|url=https://economictimes.indiatimes.com/magazines/panache/macos-now-has-a-phone-app-meet-macos-tahoe-26{{Dead Link|2025-08-14|404}}|author=Economic Times|year=2025}}</ref> == Reception & Criticism == Positive feedback highlights elegant design, productivity tools, and AI integration. Concerns include: the final Intel macOS release, possible visual distraction from transparency, and a steeper learning curve for older users. == FOSS == The core operating system of macOS, Darwin, is based heavily on [[free and Open Source Software|free and open-source]] software. The kernel, XNU, is open-source. The [[userland]] is taken mostly from [[FreeBSD]] and, in lesser part, [[GNU]] as well as some miscellaneous software such as [[Vim]] and [[ncurses]].<ref>{{Cite|title=Releases|url=https://opensource.apple.com/releases/|author=Apple Inc.|year=2026}}</ref> === FOSS alternatives === There are many viable [[FOSS]] alternatives for Apple software. Many applications in macOS can be replaced by open-source ones, such as iTerm2 instead of the [[Terminal emulator|Terminal]] app or [[VLC]] instead of the QuickTime Player. [[Linux Distributions|Linux-based]] and [[BSD]] operating systems, among others, provide a free Unix-like core operating system. [[GNUstep]] is a free implementation of Apple's Cocoa API and includes features common on macOS, such as .app Application bundles, enabling a macOS-like environment on operating systems running [[X Window System|X]] or [[Wayland]]. It also includes [[GWorkspace]], a Finder equivalent that provides a file manager, desktop icons, a dock and various other desktop features. [[Gershwin]] is a GNUstep-based [[desktop Environments|desktop environment]] that aims to replicate the look and feel of the macOS desktop on [[X11]]. == See also == * [[Darwin (operating system)]] * [[XNU]] * [[APFS]] * [[macOS Sequoia]] * [[Apple Silicon]] == References == <references/> 172ce08ac5d84cbf74551affe31f7c6d6d7e14ef 0 575 6075 6040 2026-08-26T18:10:28Z Imnotgoodatnames 121 Fix logo wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|126px]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=30.2, Aug 14, 2025 |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html gnu.org] }} [[Category:Software]] [[Category:Text editors]] GNU Emacs is a free/libre text editor and interpreter for the Emacs Lisp language, with extensions to assist with various other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, it's strongly recommended to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. ''Also see [[Vim]].'' == References == 3739b58d9a93e25985f1c85c0e50385a3fb7d3d7 6 1437 6077 2026-08-31T13:45:44Z Imnotgoodatnames 121 Gershwin desktop environment screenshot wikitext text/x-wiki == Summary == Gershwin desktop environment screenshot == Licensing == {{CC-BY-4.0}} 2419eec95a0ce559b68e16247a91f99c624e8247 0 1438 6078 2026-08-31T13:50:21Z Imnotgoodatnames 121 Created page with "{{Stub}} [[Category:Desktop Environments]] [[File:Gershwin.png|thumb|Gershwin desktop screenshot]] '''Gershwin''' is a [[GNUstep]]-based [[desktop Environments|desktop environment]] for X. It implements various [[macOS]]-like features, such as a dock and a global menu bar that supports both normal GNUstep apps and [[GTK]] programs. It is composed primarily of forks of existing core GNUstep software, such as Workspace, a fork of GWorspace and a fork of SystemPreferences,..." wikitext text/x-wiki {{Stub}} [[Category:Desktop Environments]] [[File:Gershwin.png|thumb|Gershwin desktop screenshot]] '''Gershwin''' is a [[GNUstep]]-based [[desktop Environments|desktop environment]] for X. It implements various [[macOS]]-like features, such as a dock and a global menu bar that supports both normal GNUstep apps and [[GTK]] programs. It is composed primarily of forks of existing core GNUstep software, such as Workspace, a fork of GWorspace and a fork of SystemPreferences, however it includes various unique software as well, such as a terminal emulator. It also uses a custom GNUstep theme named ''Eau'', french for "Aqua", the name of the visual theme formerly used by OS X/macOS. a699ca7e9325b3c3f4f508d0c658272e411e123c 6079 6078 2026-08-31T13:55:31Z Imnotgoodatnames 121 Add refs wikitext text/x-wiki {{Stub}} [[Category:Desktop Environments]] [[File:Gershwin.png|thumb|Gershwin desktop screenshot]] '''Gershwin''' is a [[GNUstep]]-based [[desktop Environments|desktop environment]] for X.<ref>[https://github.com/gershwin-desktop/gershwin-desktop gershwin-desktop - Github]</ref> It implements various [[macOS]]-like features, such as a dock and a global menu bar that supports both normal GNUstep apps and [[GTK]] programs.<ref>[https://gershwin-desktop.github.io/docs/developer/menu.html Global Menu - Gershwin desktop documentation]</ref> It is composed primarily of forks of existing core GNUstep software, such as Workspace, a fork of GWorspace and a fork of SystemPreferences, however it includes various unique software as well, such as a terminal emulator. It also uses a custom GNUstep theme named ''Eau'', french for "Aqua", the name of the visual theme formerly used by OS X/macOS.<ref>[https://github.com/gershwin-desktop/gershwin-eau-theme gershwin-eau-theme - Github]</ref> == References == fb52ff3093f5d5bd7a9fc70b2ceeb501ce62f6eb 6080 6079 2026-08-31T13:56:28Z Imnotgoodatnames 121 beh wikitext text/x-wiki {{Stub}} [[Category:Desktop Environments]] [[File:Gershwin.png|thumb|Gershwin desktop screenshot]] '''Gershwin''' is a [[GNUstep]]-based [[desktop Environments|desktop environment]] for [[X_Window_System|X]].<ref>[https://github.com/gershwin-desktop/gershwin-desktop gershwin-desktop - Github]</ref> It implements various [[macOS]]-like features, such as a dock and a global menu bar that supports both normal GNUstep apps and [[GTK]] programs.<ref>[https://gershwin-desktop.github.io/docs/developer/menu.html Global Menu - Gershwin desktop documentation]</ref> It is composed primarily of forks of existing core GNUstep software, such as Workspace, a fork of GWorspace and a fork of SystemPreferences, however it includes various unique software as well, such as a terminal emulator. It also uses a custom GNUstep theme named ''Eau'', french for "Aqua", the name of the visual theme formerly used by OS X/macOS.<ref>[https://github.com/gershwin-desktop/gershwin-eau-theme gershwin-eau-theme - Github]</ref> == References == 31e15ba92eb6126a97e9cedd09d3d6c3d158a032 6 1439 6081 2026-08-31T16:13:15Z Imnotgoodatnames 121 == MIT == MSYS2 clang64 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 clang64 icon == Licensing == {{Unknown_copyright}} c42add2311458a5a9910b24acc9454faa526c28c 6 1440 6082 2026-08-31T16:13:36Z Imnotgoodatnames 121 == MIT == MSYS2 clang32 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 clang32 icon 13ef00c434140fc4b98f65f55fffacbf7b900ece 6 1441 6083 2026-08-31T16:14:02Z Imnotgoodatnames 121 == MIT == MSYS2 clangarm64 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 clangarm64 icon 27eeba226bfb3d7c1bd5fc0ca8be2a3812be28a8 6 1442 6084 2026-08-31T16:14:24Z Imnotgoodatnames 121 == MIT == MSYS2 mingw32 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 mingw32 icon 4483deafaf6e1231f2928bbac32f95da3ec70e23 6 1443 6085 2026-08-31T16:14:48Z Imnotgoodatnames 121 == MIT == MSYS2 mingw64 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 mingw64 icon 33ebfdfca0915129ec0392f852daac54ec281f03 6 1444 6086 2026-08-31T16:15:09Z Imnotgoodatnames 121 == MIT == MSYS2 ucrt64 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 ucrt64 icon d409edb013b70fbe235bd5a9f4bd74401b8c9abc 0 1416 6087 6064 2026-08-31T16:29:06Z Imnotgoodatnames 121 Add icons for MSYS2 environments (taken from github.com/msys2/msys2-launcher/tree/master/icons, converted to .png using imagemagick) wikitext text/x-wiki {{Work In Progress}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | image = [[file:Msys2-icon.png|frameless|upright=0.5|MSYS2 icon]] | caption = MSYS2 icon <!-- Icon used instead of logo due to logo's unclear licensing. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://https://www.msys2.org// msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 Support], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64], David Allsopp, 2018-08-25 (Accessed: 2026-08-25)</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by <ref name=envs>[https://www.msys2.org/docs/environments/ Environments], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture |- |[[File:Msys2-icon.png|32px|MSYS icon]] |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |[[File:ucrt64.ico-5.png|32px|UCRT64 icon]] |UCRT64 |<code>/ucrt64</code> |gcc |UCRT |x86_64 |- |[[File:clang64.ico-5.png|32px|CLANG64 icon]] |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |[[File:clangarm64.ico-5.png|32px|CLANGARM64 icon]] |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS. It is always active, all other environments inherit from it and add their own environment variables on top. === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture |- |[[File:mingw32.ico-5.png|32px|MINGW32 icon]] |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |[[File:mingw64.ico-5.png|32px|MINGW64 icon]] |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |[[File:clang32.ico-5.png|32px|CLANG32 icon]] |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure compatibility with ARM, not to install an ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11], Blackhex, 2025-02-26 (Accessed: 2026-08-25)</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue Pending Package Updates], MSYS2 Packages, 2026-08-25 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Package name prefix |- |[[File:Msys2-icon.png|32px|MSYS icon]] |MSYS |None (no package name prefix) |- |[[File:ucrt64.ico-5.png|32px|UCRT64 icon]] |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |[[File:clang64.ico-5.png|32px|CLANG64 icon]] |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |[[File:clangarm64.ico-5.png|32px|CLANGARM64 icon]] |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |[[File:mingw32.ico-5.png|32px|MINGW32 icon]] |MINGW32 |<code>mingw-w64-</code> |- |[[File:mingw64.ico-5.png|32px|MINGW64 icon]] |MINGW64 |<code>mingw-w64-x86_64-</code> |- |[[File:clang32.ico-5.png|32px|CLANG32 icon]] |CLANG32 |None (environment fully deprecated)<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment News], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> (historically <code>mingw-w64-clang-i686</code>)<ref>[https://www.msys2.org/docs/package-naming/ Package Naming], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> |} == References == 06db0551aa11847ffc49b444ee124b7a0c817ac7 6088 6087 2026-08-31T18:52:26Z Imnotgoodatnames 121 Fix website, minor rewording wikitext text/x-wiki {{Work In Progress}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | image = [[file:Msys2-icon.png|frameless|upright=0.5|MSYS2 icon]] | caption = MSYS2 icon <!-- Icon used instead of logo due to logo's unclear licensing. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://www.msys2.org/ msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 Support], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64], David Allsopp, 2018-08-25 (Accessed: 2026-08-25)</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS2 environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by <ref name=envs>[https://www.msys2.org/docs/environments/ Environments], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture |- |[[File:Msys2-icon.png|32px|MSYS icon]] |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |[[File:ucrt64.ico-5.png|32px|UCRT64 icon]] |UCRT64 |<code>/ucrt64</code> |gcc |UCRT |x86_64 |- |[[File:clang64.ico-5.png|32px|CLANG64 icon]] |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |[[File:clangarm64.ico-5.png|32px|CLANGARM64 icon]] |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS2. It is always active, all other environments inherit from it and add their own environment variables on top. === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture |- |[[File:mingw32.ico-5.png|32px|MINGW32 icon]] |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |[[File:mingw64.ico-5.png|32px|MINGW64 icon]] |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |[[File:clang32.ico-5.png|32px|CLANG32 icon]] |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure the MSYS2 setup works without issues, not to install a fully ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11], Blackhex, 2025-02-26 (Accessed: 2026-08-25)</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue Pending Package Updates], MSYS2 Packages, 2026-08-25 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Package name prefix |- |[[File:Msys2-icon.png|32px|MSYS icon]] |MSYS |None (no package name prefix) |- |[[File:ucrt64.ico-5.png|32px|UCRT64 icon]] |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |[[File:clang64.ico-5.png|32px|CLANG64 icon]] |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |[[File:clangarm64.ico-5.png|32px|CLANGARM64 icon]] |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |[[File:mingw32.ico-5.png|32px|MINGW32 icon]] |MINGW32 |<code>mingw-w64-</code> |- |[[File:mingw64.ico-5.png|32px|MINGW64 icon]] |MINGW64 |<code>mingw-w64-x86_64-</code> |- |[[File:clang32.ico-5.png|32px|CLANG32 icon]] |CLANG32 |None (environment fully deprecated)<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment News], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> (historically <code>mingw-w64-clang-i686</code>)<ref>[https://www.msys2.org/docs/package-naming/ Package Naming], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> |} == References == 3a942fb0975566544fa09fcfee9efeffedc3e428 6103 6088 2026-09-03T09:48:44Z Imnotgoodatnames 121 Replace icons with SVG versions, fix package naming issues wikitext text/x-wiki {{Work In Progress}} [[Category:Software]] {{DistributionInfobox | title = MSYS2 | image = [[file:Msys2.svg|frameless|upright=0.5|MSYS2 icon]] | caption = MSYS2 icon <!-- Icon used instead of logo due to logo's unclear licensing. --> | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://www.msys2.org/ msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 Support], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64], David Allsopp, 2018-08-25 (Accessed: 2026-08-25)</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS2 environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by <ref name=envs>[https://www.msys2.org/docs/environments/ Environments], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture |- |[[File:Msys2.svg|32px|MSYS icon]] |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |[[File:Ucrt64.svg|32px|UCRT64 icon]] |UCRT64 |<code>/ucrt64</code> |gcc |UCRT |x86_64 |- |[[File:Clang64.svg|32px|CLANG64 icon]] |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |[[File:Clangarm64.svg|32px|CLANGARM64 icon]] |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS2. It is always active, all other environments inherit from it and add their own environment variables on top. === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture |- |[[File:Mingw32.svg|32px|MINGW32 icon]] |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |[[File:Mingw64.svg|32px|MINGW64 icon]] |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |[[File:Clang32.svg|32px|CLANG32 icon]] |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure the MSYS2 setup works without issues, not to install a fully ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11], Blackhex, 2025-02-26 (Accessed: 2026-08-25)</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue Pending Package Updates], MSYS2 Packages, 2026-08-25 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Package name prefix |- |[[File:Msys2.svg|32px|MSYS icon]] |MSYS |None (no package name prefix) |- |[[File:Ucrt64.svg|32px|UCRT64 icon]] |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |[[File:Clang64.svg|32px|CLANG64 icon]] |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |[[File:Clangarm64.svg|32px|CLANGARM64 icon]] |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |[[File:Mingw32.svg|32px|MINGW32 icon]] |MINGW32 |<code>mingw-w64-i686-</code> |- |[[File:Mingw64.svg|32px|MINGW64 icon]] |MINGW64 |<code>mingw-w64-x86_64-</code> |- |[[File:Clang32.svg|32px|CLANG32 icon]] |CLANG32 |None (environment fully deprecated)<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment News], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> (historically <code>mingw-w64-clang-i686-</code>)<ref>[https://www.msys2.org/docs/package-naming/ Package Naming], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> |} == References == 1edf504e6ec74cc323a3eea5d10571477205652f 3000 577 6089 5842 2026-08-31T20:11:26Z Imnotgoodatnames 121 Add more Windows info wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is recommended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight lang="text"># Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland</syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight lang="text"># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then install Emacs with the following command:<syntaxhighlight lang="text"> # emerge app-editors/emacs </syntaxhighlight> === NixOS === You can install Emacs in a variety of ways in NixOS. A common way to install Emacs is to append the following code to your NixOS configuration:<syntaxhighlight lang="nix" line="1">{ services.emacs = { enable = true; /* There are more options you can set, please read https://search.nixos.org/options?channel=unstable&query=services.emacs for more information. */ }; }</syntaxhighlight>You can then rebuild the system using your desired method—most commonly with <code>nixos-rebuild switch</code>—to use a system configuration which has Emacs installed. === FreeBSD === Emacs be installed on FreeBSD by using either pkg or ports. If you want a binary package at the absence of deeper customization, then you can use either of the following commands:<syntaxhighlight lang="text"> ## Installing Emacs (X11) # pkg install emacs ## Installing Emacs (Wayland) # pkg install emacs-wayland ## More flavours can be found here: https://www.freshports.org/editors/emacs/ </syntaxhighlight>If you are willing to compile Emacs for deeper customization, then you can use the editors/emacs port. This part is expected for people to have used ports in the past; read [https://docs.freebsd.org/en/books/handbook/ports/#ports-using Chapter 4 of the FreeBSD Handbook] for information on how to use ports if desired. And with that, you can use the following commands to build the Emacs port:<syntaxhighlight lang="text"> $ cd /usr/ports/editors/emacs # make config # make install clean </syntaxhighlight> === macOS === macOS doesn't have an official package manager or an official GNU Emacs package. However, GNU Emacs can be installed from homebrew using either of the following <code>% brew install emacs</code> <code>% brew install emacs-app</code> Alternatively, GNU Emacs can be compiled for the macOS desktop using the <code>--with-ns</code> configuration option. === Microsoft Windows === GNU Emacs can be downloaded for Microsoft Windows from a [https://ftpmirror.gnu.org/emacs/windows GNU ftp mirror] (recommended) or the primary GNU ftp server. GNU Emacs can also be installed as a [[Cygwin]] program rather than a native Win32 (MinGW) one, enabling greater integration of [[UNIX]]-like required by tools like the built-in [[terminal emulator]] as well as allowing it to use any [[X Window System|X]] widget toolkit or GNUstep rather than just the Win32 UI.<ref>[https://stackoverflow.com/questions/2075504/how-to-best-integrate-emacs-and-cygwin How to best integrate Emacs and Cygwin?] (accessed 2026-08-31</ref> Currently, upstream Emacs source only supports Windows x86 and x86_64 targets. ARM64 support requires 3rd party patches such as the ones implemented by the [[MSYS2]] project for their mingw-aarch64-emacs package.<ref>[https://gist.github.com/jgbabyn/ce4bf3bc25e781b5733d7e1c25bf988e Compiling Emacs for Windows on ARM], jgbabyn (accessed 2026-08-31)</ref><ref>[https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-emacs/002-aarch64-fixes.patch 002-aarch64-fixes.patch], msys2, 2024-29-02 (accessed 2026-08-31)</ref> === MS-DOS === GNU Emacs for Microsoft DOS and compatible operating systems can be downloaded from [https://www.delorie.com/djgpp/getting.html a DJGPP ftp mirror] at current/v2gnu/em3002b.zip Alternatively, instructions for building GNU Emacs for DOS on DOS or Windows 9x are located in the GNU Emacs source tree at msdos/INSTALL. == Installing from Source == There are multiple uses and advantages to installing GNU Emacs from source. The most obvious one is the ability to install it on systems that either do not package it themselves at all, or have an older version than the desired one. Building Emacs from source also enables a far deeper level of customization using the various configure options that can be enabled or disabled in the build process. For example, it enables building Emacs to use various graphical toolkits such as [[GTK]], [[Motif]], pure GTK (for Wayland), pure [[X11]] or to not use a GUI at all and remain an exclusively [[TUI]] program. GNU Emacs can be built from source using the standard Autotools + Make procedure. First, make sure the host system has all the dependencies required for Emacs itself and for the desired Emacs features (such as X11 support). The source code for GNU Emacs releases can be downloaded from a [https://ftpmirror.gnu.org/emacs GNU ftp mirror] (recommended) or from the primary gnu ftp server. Alternatively, the current GNU Emacs development source can be cloned using git with <code>$ git clone git://git.git.savannah.gnu.org/emacs.git</code> For access to internet resources over <code>https</code>, GNU Emacs must be compiled with [https://ftp.gnu.org/gnu/gnutls/ GnuTLS]. It can still be compiled without, but external package repositories which rely on a secure connection such as [https://melpa.org/ melpa] will not function. To build GNU Emacs from source, run the following commands in the source tree: <syntaxhighlight lang="text"> $./autogen.sh #unnecessary if building from release tarball $ ./configure [configuration options] $ make $ make install #optional; run make clean after make install to free some storage space </syntaxhighlight> running <code>$ ./configure --help</code> will print all available configuration options. ===Notable configuration options=== This is a list of notable configuration options for GNU Emacs and their uses. Keep in mind that --with-feature=no disables the 'feature' feature and that --without-feature is the same as --with-feature=no. {| class="wikitable" !Configure flag !effect |- |<code>--prefix=PREFIX |Installs Emacs to the directory PREFIX during <code>make install</code> (eg. <code>--prefix=/home/username</code> will install files into /home/username/bin, /home/username/lib etc. |- |<code>--with-x |Compiles GNU Emacs with X Windowing System support. Necessary for a graphical interface on X11. |- |<code>--with-x-toolkit=TOOLKIT |Builds Emacs with the TOOLKIT X graphical toolkit. TOOLKIT can be 'yes', 'gtk', 'gtk2', 'gtk3', 'lucid', 'athena', or 'motif'. Disabling this feature (setting it to 'no') will build Emacs against pure Xlib. |- |<code>--with-pgtk |Builds the "Pure GTK" toolkit version of Emacs, enabling native Wayland support but potentially making X support unstable. |- |<code>--with-gpm |Enables support for gpm, enabling support for the mouse in the Linux virtual terminal. |- |<code>--with-ns |If on macOS, builds Emacs for Cocoa; otherwise builds Emacs for [[GNUstep]]. |- |<code>--with-android |Builds Emacs for Android and packages it in an Android .apk file. |} A more detailed overview is available at [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] in the GNU Emacs Savannah git repository. == References == 9efc09c552649ae3f1923494b85069618a9ef796 6112 6089 2026-09-03T20:11:57Z Imnotgoodatnames 121 Add more Android info wikitext text/x-wiki {{GuideWarning}} [[GNU Emacs|GNU Emacs]] is packaged in many Linux distributions<ref>[https://repology.org/project/emacs/versions emacs package versions], Repology, 2016-08-10 (Accessed: 2025-08-10)</ref> and can be installed from Canonical's Snap<ref>[https://snapcraft.io/emacs Install GNU Emacs on Linux], Snap Store, 2025-07-20 (Accessed: 2025-08-10)</ref> or built yourself if not present in your distribution. This guide will provide information on how to install Emacs in these cases. Emacs 28.1 and above is recommended for daily use. == Installing == === Debian/Ubuntu-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo apt install emacs-gtk # Installing Emacs PGTK (Wayland) $ sudo apt install emacs-pgtk </syntaxhighlight> === Fedora-based distros === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo dnf install emacs-gtk+x11 # Installing Emacs PGTK (Wayland) $ sudo dnf install emacs </syntaxhighlight> === openSUSE Tumbleweed === <syntaxhighlight lang="text"> # Installing Emacs GTK (X11) $ sudo zypper in emacs-gtk # Installing Emacs PGTK (Wayland) # openSUSE does not provide a package for Emacs PGTK. # Check the "Installing From Source" section for installation steps. </syntaxhighlight> === Arch Linux === <syntaxhighlight lang="text"># Installing Emacs GTK (X11) $ sudo pacman -S emacs # Installing Emacs PGTK (Wayland) $ sudo pacman -S emacs-wayland</syntaxhighlight> === Gentoo Linux === The installation process for Emacs is different on Gentoo Linux, as it uses USE flags instead of different package names to specify how it was built. Add the correpsonding options to <code>/etc/portage/package.use/emacs</code>:<syntaxhighlight lang="text"># Emacs GTK (X11) app-editors/emacs X gtk # Emacs PGTK (Wayland) app-editors/emacs -X gtk</syntaxhighlight>After adding this, you can then install Emacs with the following command:<syntaxhighlight lang="text"> # emerge app-editors/emacs </syntaxhighlight> === NixOS === You can install Emacs in a variety of ways in NixOS. A common way to install Emacs is to append the following code to your NixOS configuration:<syntaxhighlight lang="nix" line="1">{ services.emacs = { enable = true; /* There are more options you can set, please read https://search.nixos.org/options?channel=unstable&query=services.emacs for more information. */ }; }</syntaxhighlight>You can then rebuild the system using your desired method—most commonly with <code>nixos-rebuild switch</code>—to use a system configuration which has Emacs installed. === FreeBSD === Emacs be installed on FreeBSD by using either pkg or ports. If you want a binary package at the absence of deeper customization, then you can use either of the following commands:<syntaxhighlight lang="text"> ## Installing Emacs (X11) # pkg install emacs ## Installing Emacs (Wayland) # pkg install emacs-wayland ## More flavours can be found here: https://www.freshports.org/editors/emacs/ </syntaxhighlight>If you are willing to compile Emacs for deeper customization, then you can use the editors/emacs port. This part is expected for people to have used ports in the past; read [https://docs.freebsd.org/en/books/handbook/ports/#ports-using Chapter 4 of the FreeBSD Handbook] for information on how to use ports if desired. And with that, you can use the following commands to build the Emacs port:<syntaxhighlight lang="text"> $ cd /usr/ports/editors/emacs # make config # make install clean </syntaxhighlight> === macOS === macOS doesn't have an official package manager or an official GNU Emacs package. However, GNU Emacs can be installed from homebrew using either of the following <code>% brew install emacs</code> <code>% brew install emacs-app</code> Alternatively, GNU Emacs can be compiled for the macOS desktop using the <code>--with-ns</code> configuration option. === Microsoft Windows === GNU Emacs can be downloaded for Microsoft Windows from a [https://ftpmirror.gnu.org/emacs/windows GNU ftp mirror] (recommended) or the primary GNU ftp server. GNU Emacs can also be installed as a [[Cygwin]] program rather than a native Win32 (MinGW) one, enabling greater integration of [[UNIX]]-like required by tools like the built-in [[terminal emulator]] as well as allowing it to use any [[X Window System|X]] widget toolkit or GNUstep rather than just the Win32 UI.<ref>[https://stackoverflow.com/questions/2075504/how-to-best-integrate-emacs-and-cygwin How to best integrate Emacs and Cygwin?] (accessed 2026-08-31</ref> Currently, upstream Emacs source only supports Windows x86 and x86_64 targets. ARM64 support requires 3rd party patches such as the ones implemented by the [[MSYS2]] project for their mingw-aarch64-emacs package.<ref>[https://gist.github.com/jgbabyn/ce4bf3bc25e781b5733d7e1c25bf988e Compiling Emacs for Windows on ARM], jgbabyn (accessed 2026-08-31)</ref><ref>[https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-emacs/002-aarch64-fixes.patch 002-aarch64-fixes.patch], msys2, 2024-29-02 (accessed 2026-08-31)</ref> === Android === GNU Emacs as an [[Android]] app can be downloaded for various architectures from the [https://ftp.gnu.org/gnu/emacs/android/ GNU ftp server]. On [[Termux]], GNU Emacs can be installed using the native package manager: <syntaxhighlight lang="text"> # Installing Emacs (terminal only) $ pkg install emacs # Installing Emacs X11 $ pkg install emacs-x </syntaxhighlight> === MS-DOS === GNU Emacs for Microsoft DOS and compatible operating systems can be downloaded from [https://www.delorie.com/djgpp/getting.html a DJGPP ftp mirror] at current/v2gnu/em3002b.zip Alternatively, instructions for building GNU Emacs for DOS on DOS or Windows 9x are located in the GNU Emacs source tree at msdos/INSTALL. == Installing from Source == There are multiple uses and advantages to installing GNU Emacs from source. The most obvious one is the ability to install it on systems that either do not package it themselves at all, or have an older version than the desired one. Building Emacs from source also enables a far deeper level of customization using the various configure options that can be enabled or disabled in the build process. For example, it enables building Emacs to use various graphical toolkits such as [[GTK]], [[Motif]], pure GTK (for Wayland), pure [[X11]] or to not use a GUI at all and remain an exclusively [[TUI]] program. GNU Emacs can be built from source using the standard Autotools + Make procedure. First, make sure the host system has all the dependencies required for Emacs itself and for the desired Emacs features (such as X11 support). The source code for GNU Emacs releases can be downloaded from a [https://ftpmirror.gnu.org/emacs GNU ftp mirror] (recommended) or from the primary gnu ftp server. Alternatively, the current GNU Emacs development source can be cloned using git with <code>$ git clone git://git.git.savannah.gnu.org/emacs.git</code> For access to internet resources over <code>https</code>, GNU Emacs must be compiled with [https://ftp.gnu.org/gnu/gnutls/ GnuTLS]. It can still be compiled without, but external package repositories which rely on a secure connection such as [https://melpa.org/ melpa] will not function. To build GNU Emacs from source, run the following commands in the source tree: <syntaxhighlight lang="text"> $./autogen.sh #unnecessary if building from release tarball $ ./configure [configuration options] $ make $ make install #optional; run make clean after make install to free some storage space </syntaxhighlight> running <code>$ ./configure --help</code> will print all available configuration options. ===Notable configuration options=== This is a list of notable configuration options for GNU Emacs and their uses. Keep in mind that --with-feature=no disables the 'feature' feature and that --without-feature is the same as --with-feature=no. {| class="wikitable" !Configure flag !effect |- |<code>--prefix=PREFIX |Installs Emacs to the directory PREFIX during <code>make install</code> (eg. <code>--prefix=/home/username</code> will install files into /home/username/bin, /home/username/lib etc. |- |<code>--with-x |Compiles GNU Emacs with X Windowing System support. Necessary for a graphical interface on X11. |- |<code>--with-x-toolkit=TOOLKIT |Builds Emacs with the TOOLKIT X graphical toolkit. TOOLKIT can be 'yes', 'gtk', 'gtk2', 'gtk3', 'lucid', 'athena', or 'motif'. Disabling this feature (setting it to 'no') will build Emacs against pure Xlib. |- |<code>--with-pgtk |Builds the "Pure GTK" toolkit version of Emacs, enabling native Wayland support but potentially making X support unstable. |- |<code>--with-gpm |Enables support for gpm, enabling support for the mouse in the Linux virtual terminal. |- |<code>--with-ns |If on macOS, builds Emacs for Cocoa; otherwise builds Emacs for [[GNUstep]]. |- |<code>--with-android |Builds Emacs for Android and packages it in an Android .apk file. |} Instructions for building GNU Emacs an Android app are available at [[Guides:Building Emacs for android]]. A more detailed overview is available at [https://git.savannah.gnu.org/cgit/emacs.git/tree/INSTALL root/INSTALL] in the GNU Emacs Savannah git repository. == References == 01574d8e541ac61b61371cbb90443d80505337af 0 650 6090 3605 2026-09-01T13:11:31Z Imnotgoodatnames 121 Fix logo for light mode wikitext text/x-wiki [[Category:Desktop Environments]] {{SoftwareInfobox | image=[[File:Enlightenment-logo-new.svg{{!}}class=skin-invert|Enlightenment_logo]] | caption = Enlightenment logo | title=Enlightenment | releasestatus=Maintained | lastrelease=0.27.1, March 17, 2025 | firstrelease=0.13.2, January 18, 1998 | languages=[[C]], [[ELF]] | developers=Enlightenment Foundation | website=[https://www.enlightenment.org/, enlightenment.org/] }} [https://www.enlightenment.org/ Enlightenment] is a [[Desktop Environments|Desktop Environment]] and [[Window Manager]] for [[Linux]] and other [[Unix|Unix-like]] [[Operating System|operating systems]], such as [[BSD]] derivatives.<ref name=":0">[https://www.enlightenment.org/about Enlightenment About Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref>. Originally created by Carsten Haitzler in the late 90s with the philosophy "that users should be given as much control as possible."<ref>[https://www.enlightenment.org/about-enlightenment| About Enlightenment Page], Enlightenment foundation, 2025 (Retrieved 14th June 2025)</ref> === Features === Enlightenment has many key features as a [[graphical desktop]] including its own set of graphical and system libraries known as the "Enlightenment Foundation Libraries". Designed to be portable and efficient while also being easy to use on various devices including touch devices even being used in Samsung devices.<ref name=":0" /> * Support for both [https://www.x.org/wiki/ X11] and experimental [https://wayland.freedesktop.org/ Wayland] support. * A hand optimized software rendering compositor. * Very low memory requirements. * The ability to configure everything graphically. * Touch gestures * Window Management Features ** Virtual desktops. ** Optional window tiling. ** Customizable mouse and keyboard bindings. ** And many more modules. == References == <references /> 61912b5e8e239ad7593a4c27c40ae883edc610ed 0 1347 6091 5749 2026-09-01T13:17:49Z Imnotgoodatnames 121 Fix logo for dark mode wikitext text/x-wiki {{Work In Progress}} {{SoftwareInfobox | caption = River logo | developers = Isaac Freund | firstrelease = v0.1.0, 2021-09-03 | languages = [[Zig]] | lastrelease = v0.4.5, 2026-04-25 | title = River | website = [https://isaacfreund.com/software/river/] | releasestatus = Maintained | image = [[File:River logo.svg{{!}}class=skin-invert|thumb|center|alt=the logo of the river project]] }} River is a non-monolithic wayland compositor. Unlike most wayland compositor it does not combine compositor and window manager into one program. River achieves this by implementing a custom wayland protocol called `river-window-management-v1` which allows any client implementing it to become the window manager for river. This split allows for a lot more experimentation and window manager implementations in less performant programming languages like [[Python]]. It also makes the process a lot easier when compared to writing a full compositor. ==Window Managers== There is a an [https://codeberg.org/river/wiki/src/branch/main/pages/wm-list.md official list of window managers] in river's wiki. ==Input Config== Not all window managers configure input devices on river. Since the wayland protocols for this are entirely disjoint, there are some stand-alone tools that will work with most window managers. * [https://codeberg.org/Sivecano/channel channel] is a daemon that hot-reloads its config and has some glob-based matching rules. * [https://github.com/kewuaa/kwim kwim] a simple input config tool that simply one-shot-applies its config. 2e64aeacb20990e4f8f8e5949f1439e0088d485a 0 176 6092 5773 2026-09-01T13:24:20Z Imnotgoodatnames 121 Fix logo for dark mode, improve infobox formatting, update last release wikitext text/x-wiki {{SoftwareInfobox |image = [[File:Plasma-logo-monochrome.svg{{!}}class=skin-invert|thumb]] |caption = KDE Plasma Logo |title = KDE Plasma |releasestatus = Maintained |lastrelease = 6.7.4, June 16, 2026 [https://kde.org/announcements/plasma/6/6.7.0/] |firstrelease = 1.0, July 12, 1998 [https://kde.org/announcements/1-2-3/1.0-beta1/] |languages = [[C++]], QML |developers = KDE |website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> [[Desktop Environments|desktop environment]] for [[UNIX]]-like [[Operating System|operating systems]] such as [[Linux]] and various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === Plasma includes these apps by default: * System Settings * [[Dolphin]] (file manager) * [[Discover]] (app store) * [[Konsole]] (terminal emulator) * [[Spectacle]] (screenshot tool) * [[Kate]] (text editor) * [[Ark]] (archive manager) * [[Gwenview]] (image viewer) * [[Okular]] (document viewer) Additionally, KDE offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [[Krita]] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2026-05-26|403}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [[Kdenlive]] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2026-05-26|403}} to demonstrate some of its basic capabilities. * [[Ark]] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [[Kate]] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [[Filelight]] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode." In edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects apply special visual effects to the desktop. Plasma includes effects in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' in System Settings. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] rounds window corners on Plasma for both '''[[X11]]''' and '''[[Wayland]]'''. == References == <references /> b766a323f0cedf3583ae2f5ea7bf268586f5c1e5 6093 6092 2026-09-01T13:27:51Z Imnotgoodatnames 121 bluhh wikitext text/x-wiki {{SoftwareInfobox | image = [[File:Plasma-logo-monochrome.svg{{!}}class=skin-invert|thumb]] | caption = KDE Plasma Logo | title = KDE Plasma | releasestatus = Maintained | lastrelease = 6.7.4, June 16, 2026 [https://kde.org/announcements/plasma/6/6.7.0/] | firstrelease = 1.0, July 12, 1998 [https://kde.org/announcements/1-2-3/1.0-beta1/] | languages = [[C++]], QML | developers = KDE | website = [https://kde.org/plasma-desktop/ kde.org/plasma-desktop] }} [[Category:Desktop Environments]] [[File:KDE Plasma 5.26 screenshot.png|thumb|Screenshot of KDE Plasma 5.26]] KDE Plasma is a popular<ref>https://qa.debian.org/popcon.php?package=plasma-desktop Debian Popularity Contest</ref><ref>https://pkgstats.archlinux.de/packages?query=plasma-desktop Arch Linux Package Statistics</ref> [[Desktop Environments|desktop environment]] for [[UNIX]]-like [[Operating System|operating systems]] such as [[Linux]] and various flavors of [[BSD]].<ref>KDE Project - Distributions [https://community.kde.org/Distributions]</ref> Originally created by Matthias Ettrich in 1996, the KDE project was founded upon the premise that it should be a "complete graphical environment," implying the creation of a fully featured and richly tooled Desktop Environment which KDE has become in the modern era.<ref>Matthias Ettrich. "''New Project: Kool Desktop Environment. Programmers wanted!''"[https://groups.google.com/g/de.comp.os.linux.misc/c/SDbiV3Iat_s/m/zv_D_2ctS8sJ?pli=1]</ref> === Features === Plasma includes these apps by default: * System Settings * [[Dolphin]] (file manager) * [[Discover]] (app store) * [[Konsole]] (terminal emulator) * [[Spectacle]] (screenshot tool) * [[Kate]] (text editor) * [[Ark]] (archive manager) * [[Gwenview]] (image viewer) * [[Okular]] (document viewer) Additionally, KDE offers a multitude of software - according to their website, they have successfully created "over 200 applications" for the modern desktop.<ref>KDE Project - Applications [https://apps.kde.org/]</ref> Some of their most important projects have made a significant impact on the Linux universe: * [[Krita]] - a fully-featured suite for artistry such as painting and even animation.<ref>Invidious - "''Krita Animation Test''" [https://yewtu.be/watch?v=p_ZseR5YEiM]{{Dead Link|2026-05-26|403}}</ref> Often compared to CLIP STUDIO, Procreate, and others. * [[Kdenlive]] - a movie editor for film-making, with a few transitions and effects. While it does not currently rival the capabilities of professional video creation software, it is still user-friendly and powerful enough to satisfy the video editing needs of many users. Kdenlive, as an example, was explicitly used to create [https://yewtu.be/watch?v=N3iduKNqSTk this video]{{Dead Link|2026-05-26|403}} to demonstrate some of its basic capabilities. * [[Ark]] - a file compression and decompression tool that supports a wide range of formats commonly used throughout the internet. Despite the lack of RAR support, Ark is just as versatile and arguably even competes against applications like WinRar. * [[Kate]] - a text editor that not only supports syntax highlighting - a must for quick edits to source code - but has a plethora of features that make it a suitable choice for lightweight programming. * [[Filelight]] - a very useful tool for assessing how much storage on your machine is in use or free, which does not only scale to your installation disk but also to external media as well. === Edit Mode === [[File:Edit Mode - Widgets.png|thumb|"Add Widgets..." bar on KDE Plasma]] Part of KDE's robust configuration is its capability to enter "edit mode." In edit mode, you have full access to the layout of your system's panels and widgets. Within this menu, there are several elements: * '''Widgets -''' in and of themselves, widgets can do two possible things in the layout of your desktop; ** They can be added, often seamlessly, into one of your '''panels''' for easy management; ** They can be added directly onto your desktop - that is, the empty space you have without any windows open. *** Note that this does imply, for laptops, a small yet somewhat noticeable drop in battery life. If you want your laptop to last, make sure you minimize your plugins. * '''Get New Widgets... -''' Here, you can find some often useful widgets made by the community. Be sure to check for quality - sometimes, widgets can be very buggy. * '''Add Panel... -''' These are the bars of which that house widgets or trays, pictured below. Depending on your composition of spacers and widgets in between, panels can serve multiple purposes beyond just an Application Launcher like on Windows. * '''Configure Desktop and Wallpaper... -''' A simple user interface to change your wallpaper and adjust its appearance. ** These can be modified by plugins. ** '''NOTE: This was written before the KDE 6.1 update.''' There are not many major functional differences, most are visual. === Desktop Effects === Desktop effects apply special visual effects to the desktop. Plasma includes effects in categories such as: * '''Accessibility -''' Helps the visually impaired or other people that may struggle to use a desktop without additional aid. * '''Appearance -''' Different tweaks, animations, and additional features that can be added or removed to allow for the adjustment of the KDE desktop's visual elements. ** '''EX: Wobbly Windows''' allows for your windows to have additional elasticity when dragged and interacted with.. * '''Focus -''' Determines the behavior of stacked windows and popups. * '''Peek at Desktop Animation -''' Animation played when using Peek at Desktop. * '''Tools -''' Used primarily for debugging with the base tools. * '''Virtual Desktop Switching Animation -''' Seen when changing virtual desktops. * '''Window Management/Open and Close Animations -''' Determines the visual behavior of open windows, as well as determining the behavior of them when interacted with. There are also extra effects that can be obtained either through the [[Package Manager|package manager]] or through '''Get new effects...''' in System Settings. For example, '''kwin-effect-rounded-corners-git''' on the [[Arch User Repository]] rounds window corners on Plasma for both '''[[X11]]''' and '''[[Wayland]]'''. == References == <references /> bc74cbf1338f0d8e8075f1f9b766c0545126dfe6 0 653 6094 5878 2026-09-01T13:58:36Z Imnotgoodatnames 121 Rewording, refs, ARM support wikitext text/x-wiki {{Stub}} {{DISPLAYTITLE:Pop!_OS}} {{DistributionInfobox | title = Pop!_OS | image = [[File:Pop! OS Icon.svg|frameless]] | caption = The Pop!_OS logo | releasestatus = Maintained | packagemanager = [[APT]] | defaultdesktops = COSMIC | usagetype = Desktop | architectures = x86_64, aarch64 | website = [https://system76.com/pop system76.com/pop] | releasemodel = Stable }} '''Pop!_OS''' is a [[FOSS|free and open-source]] [[Linux Distributions|Linux distribution]] based on [[Ubuntu]]. Pop!_OS features a custom [[Desktop Environments|desktop environment]] called [[COSMIC]].<ref>[https://9to5linux.com/system76-launches-pop_os-24-04-lts-with-cosmic-alpha-desktop-environment System76 Launches Pop!_OS 24.04 LTS with COSMIC Alpha Desktop Environment], Marcus Nestor, 2024-08-08 (accessed 2026-09-01)</ref> Pop!_OS is developed by the American Linux computer manufacturer System76 for whose computers it's primarily built for, though it can also be downloaded and installed on most other personal computers.<ref>[https://system76.com/pop Pop!_OS Linux Operating System] (accessed 2026-09-01)</ref> [[File:Poposrice.png|thumb|Pop!_OS desktop screenshot|346px]] == Features == * Full support for [[Nvidia]] and [[AMD]] GPUs<ref>[https://www.forbes.com/sites/jasonevangelho/2019/03/20/pop_os-18-10-linux-gaming-nvidia-radeon-user-experience/ Pop OS 18.10 Linux Gaming Report: System76 Nails It For Nvidia And AMD Users], Jason Evangelho, 2019-03-27 (accessed 2026-09-01)</ref> * Disk Encryption * Window and Workspace management * Recovery Partition support<ref>[https://www.omgubuntu.co.uk/2019/04/system76-launch-pop-os-19-04-based-on-ubuntu-19-04 System76 Launch Pop OS 19.04, Based on Ubuntu 19.04], Joey Sneddon, 2019-04-24 (accessed 2026-09-01)</ref> * GUI toggle == References == 74bd22e168cc76e7fb803674ed12b8f6344bbbb3 3000 1300 6095 5589 2026-09-02T15:27:45Z Hyperreal 388 Fix error in btrfs set property command, use http mirrors wikitext text/x-wiki {{GuideWarning}} In this guide, we'll use a Debian Live ISO to do the following: * Create a single LUKS2 encrypted partition. * Create a single Btrfs filesystem with <code>@</code>, <code>@home</code>, <code>@swap</code> and other subvolumes. * Create an encrypted swapfile in the <code>@swap</code> subvolume. * Optional: removal of crypto keys from RAM during laptop suspend * Optional: configurations for laptops == Pre-installation setup == Boot into the live ISO, open a terminal, and become root. Install the needed packages. <syntaxhighlight lang="bash"> sudo -i apt update apt install debootstrap cryptsetup arch-install-scripts </syntaxhighlight> Create partitions. We'll assume the drive we're installing Debian onto is <code>/dev/nvme0n1</code>. <syntaxhighlight lang="bash"> cfdisk /dev/nvme0n1 </syntaxhighlight> In the <code>cfdisk</code> TUI, create the following: * GPT partition table * 512M <code>/dev/nvme0n1p1</code> EFI System Partition (EF00) * 100%+ <code>/dev/nvme0n1p2</code> Linux filesystem Now we'll format the partitions we created. The <code>cryptsetup</code> command will prompt us to enter a secure password for the LUKS2 encrypted partition. <syntaxhighlight lang="bash"> mkfs.fat -F 32 -n EFI /dev/nvme0n1p1 cryptsetup -y -v --type luks2 luksFormat --label Debian /dev/nvme0n1p2 cryptsetup luksOpen /dev/nvme0n1p2 cryptroot mkfs.btrfs /dev/mapper/cryptroot </syntaxhighlight> Now we'll create the Btrfs subvolumes. <syntaxhighlight lang="bash"> mount /dev/mapper/cryptroot /mnt btrfs subvolume create /mnt/@ btrfs subvolume create /mnt/@home btrfs subvolume create /mnt/@swap umount -lR /mnt </syntaxhighlight> Re-mount the subvolumes as partitions. <syntaxhighlight lang="bash"> mount -t btrfs -o defaults,subvol=@,compress=zstd:1 /dev/mapper/cryptroot /mnt mkdir -p /mnt/{boot,home} mkdir /mnt/boot/efi mount /dev/nvme0n1p1 /mnt/boot/efi mount -t btrfs -o defaults,subvol=@home,compress=zstd:1 /dev/mapper/cryptroot /mnt/home </syntaxhighlight> Setup the swap file. <syntaxhighlight lang="bash"> mkdir -p /mnt/swap mount -t btrfs -o subvol=@swap /dev/mapper/cryptroot /mnt/swap touch /mnt/swap/swapfile chmod 600 /mnt/swap/swapfile chattr +C /mnt/swap/swapfile btrfs property set /mnt/swap compression none dd if=/dev/zero of=/mnt/swap/swapfile bs=1M count=16384 mkswap /mnt/swap/swapfile swapon /mnt/swap/swapfile </syntaxhighlight> == Base installation == Create a nested subvolume for <code>/var/log</code> under the <code>@</code> subvolume. This will be automounted with <code>@</code> so there is no need to add it to <code>/etc/fstab</code>. Nested subvolumes are not included in snapshots of the parent subvolume. Creating a nested subvolume for <code>/var/log</code> will ensure the log files remain untouched when we restore the rootfs from a snapshot. <syntaxhighlight lang="bash"> mkdir -p /mnt/var btrfs subvolume create /mnt/var/log </syntaxhighlight> Now we'll run <code>debootstrap</code> to bootstrap the base system. We'll use the Trixie release as an example, but we can use any release codename. <syntaxhighlight lang="bash"> debootstrap --arch amd64 trixie /mnt </syntaxhighlight> Bind the pseudo-filesystems for chroot. <syntaxhighlight lang="bash"> mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys mount -t proc proc /mnt/proc </syntaxhighlight> Generate fstab. <syntaxhighlight lang="bash"> genfstab -U /mnt >> /mnt/etc/fstab </syntaxhighlight> Chroot into the new system. <syntaxhighlight lang="bash"> cp -v /etc/resolv.conf /mnt/etc/ chroot /mnt </syntaxhighlight> == Configure the new installation == Set the timezone, locales, keyboard configuration, and console. <syntaxhighlight lang="bash"> apt install locales keyboard-configuration dpkg-reconfigure tzdata locales keyboard-configuration </syntaxhighlight> Set the hostname. <syntaxhighlight lang="bash"> echo 'hostname' > /etc/hostname echo '127.0.1.1 hostname.localdomain hostname' >> /etc/hosts </syntaxhighlight> Configure APT sources in <code>/etc/apt/sources.list</code>. * Replace <code>http://deb.debian.org/debian </code> with our desired mirror. * Replace <code>trixie</code> with our desired Debian version name. E.g., <code>bookworm</code>, <code>forky</code>. * Replace <code>main non-free-firmware</code> with the repositories we want. Options include: <code>main</code>, <code>contrib</code>, <code>non-free</code>, <code>non-free-firmware</code>. * The only entry that needs to stay unchanged is the <code>debian-security</code> repository. <syntaxhighlight lang="bash"> deb http://deb.debian.org/debian trixie main non-free-firmware deb http://deb.debian.org/debian trixie-updates main non-free-firmware deb http://deb.debian.org/debian trixie-backports main non-free-firmware deb http://deb.debian.org/debian-security trixie-security main non-free-firmware </syntaxhighlight> Install essential packages. <syntaxhighlight lang="bash"> apt update apt dist-upgrade apt install linux-image-amd64 linux-headers-amd64 firmware-linux firmware-linux-nonfree sudo command-not-found systemd-timesyncd systemd-resolved cryptsetup cryptsetup-initramfs efibootmgr btrfs-progs grub-efi </syntaxhighlight> Install a desktop environment (optional). <syntaxhighlight lang="bash"> apt install task-gnome-desktop task-desktop </syntaxhighlight> If installing on a laptop: <syntaxhighlight lang="bash"> apt install task-laptop powertop </syntaxhighlight> Set the root password. <syntaxhighlight lang="bash"> passwd root </syntaxhighlight> Create users and groups. We'll pretend our user is <code>tux</code> and that they want sudo privileges. <syntaxhighlight lang="bash"> adduser tux usermod -aG systemd-journal tux usermod -aG sudo tux </syntaxhighlight> If we want our user to be able to use sudo without a password, run the following commands. <syntaxhighlight lang="bash"> echo "tux ALL=(ALL) NOPASSWD: ALL" | tee /etc/sudoers.d/tux chmod 440 /etc/sudoers.d/tux </syntaxhighlight> == Setup the bootloader == Optional package for extra protection of suspended laptops. <syntaxhighlight lang="bash"> apt install cryptsetup-suspend </syntaxhighlight> Setup encryption parameters. We'll need the encrypted partition's UUID. <syntaxhighlight lang="bash"> blkid -s UUID -o value /dev/nvme0n1p2 </syntaxhighlight> Edit <code>/etc/crypttab</code> and use the UUID from the output of the previous command. <syntaxhighlight lang="bash"> cryptroot UUID=<uuid> none luks </syntaxhighlight> Install the bootloader. <syntaxhighlight lang="bash"> grub-install --target=x86_64-efi --efi-directory=/boot/efi --recheck --bootloader-id="Debian" </syntaxhighlight> Edit <code>/etc/default/grub</code> to include support for encrypted disks. <syntaxhighlight lang="bash"> GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" GRUB_ENABLE_CRYPTODISK=y GRUB_TERMINAL=console </syntaxhighlight> Update the grub configuration. <syntaxhighlight lang="bash"> update-grub </syntaxhighlight> Exit chroot and reboot. <syntaxhighlight lang="bash"> exit umount -lR /mnt reboot </syntaxhighlight> == Emergency recovery from live ISO == In the event of an emergency recovery situation, boot into the live ISO again and run the following commands to mount the encrypted filesystem for maintenance. <syntaxhighlight lang="bash"> sudo -i cryptsetup luksOpen /dev/nvme0n1p2 cryptroot mount -t btrfs -o defaults,subvol=@,compress=zstd:1 /dev/mapper/cryptroot /mnt mount /dev/nvme0n1p1 /mnt/boot/efi mount -t btrfs -o defaults,subvol=@home,compress=zstd:1 /dev/mapper/cryptroot /mnt/home mount -t btrfs -o subvol=@swap /dev/mapper/cryptroot /mnt/swap swapon /mnt/swap/swapfile mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys mount -t proc proc /mnt/proc chroot /mnt </syntaxhighlight> 37dc1db23d0493b1734ba39ff945199fa6a618d3 6 1445 6096 2026-09-03T09:34:07Z Imnotgoodatnames 121 == MIT == MSYS2 MSYS icon wikitext text/x-wiki == Summary == == MIT == MSYS2 MSYS icon edea69beca66e9911e628280f857bfcc445e97f4 6109 6096 2026-09-03T17:19:18Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Msys2.svg]] wikitext text/x-wiki == Summary == == MIT == MSYS2 MSYS icon edea69beca66e9911e628280f857bfcc445e97f4 6 1446 6097 2026-09-03T09:34:57Z Imnotgoodatnames 121 == MIT == MSYS2 CLANG64 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 CLANG64 icon 7e7f4f2023497362e8442411628c8cb5fd96ca82 6105 6097 2026-09-03T17:17:37Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Clang64.svg]] wikitext text/x-wiki == Summary == == MIT == MSYS2 CLANG64 icon 7e7f4f2023497362e8442411628c8cb5fd96ca82 6 1447 6098 2026-09-03T09:35:30Z Imnotgoodatnames 121 == MIT == MSYS2 UCRT64 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 UCRT64 icon 27779d52cc5e7d00c30047540baeb7e95043a3f7 6110 6098 2026-09-03T17:19:36Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Ucrt64.svg]] wikitext text/x-wiki == Summary == == MIT == MSYS2 UCRT64 icon 27779d52cc5e7d00c30047540baeb7e95043a3f7 6 1448 6099 2026-09-03T09:36:05Z Imnotgoodatnames 121 == MIT == MSYS2 CLANGARM64 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 CLANGARM64 icon 2e0c4ed14e7b1e0013868ea3ba82058ad86cc8ac 6106 6099 2026-09-03T17:18:11Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Clangarm64.svg]] wikitext text/x-wiki == Summary == == MIT == MSYS2 CLANGARM64 icon 2e0c4ed14e7b1e0013868ea3ba82058ad86cc8ac 6 1449 6100 2026-09-03T09:37:11Z Imnotgoodatnames 121 == MIT == MSYS2 MINGW32 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 MINGW32 icon 07668a0f23f9ec0170ac6aa70ca74dbd866f1873 6107 6100 2026-09-03T17:18:34Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Mingw32.svg]] wikitext text/x-wiki == Summary == == MIT == MSYS2 MINGW32 icon 07668a0f23f9ec0170ac6aa70ca74dbd866f1873 6 1450 6101 2026-09-03T09:37:33Z Imnotgoodatnames 121 == MIT == MSYS2 MINGW64 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 MINGW64 icon 96b92117fcd079d4c0ca998ab6870636f68c9206 6108 6101 2026-09-03T17:18:52Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Mingw64.svg]] wikitext text/x-wiki == Summary == == MIT == MSYS2 MINGW64 icon 96b92117fcd079d4c0ca998ab6870636f68c9206 6 1451 6102 2026-09-03T09:40:34Z Imnotgoodatnames 121 == MIT == MSYS2 MINGW64 icon wikitext text/x-wiki == Summary == == MIT == MSYS2 MINGW64 icon 650634b6d51a9bcb74070813a5218e1ef0379021 6104 6102 2026-09-03T17:17:13Z Imnotgoodatnames 121 Imnotgoodatnames uploaded a new version of [[File:Clang32.svg]] wikitext text/x-wiki == Summary == == MIT == MSYS2 MINGW64 icon 650634b6d51a9bcb74070813a5218e1ef0379021 3000 1452 6111 2026-09-03T19:57:01Z Imnotgoodatnames 121 Create guide wikitext text/x-wiki {{GuideWarning}} This guide is for building and packaging [[GNU Emacs]] as an [[Android]] .apk application. For compiling GNU Emacs in Termux, see [[Guides:Emacs_Installation_Guide#Installing_from_source]]. Building GNU Emacs for Android is a slightly more involved process as it requires unique build options and dependencies. It is currently only officially supported on x86_64 GNU/Linux systems, though, in theory, it may work on [[M1|Apple silicon]]-based [[macOS]] devices as well. == Requirements == You need to have a working Java compiler from OpenJDK. You can usually install it using your operating system's package manager, eg. <code>$ sudo apt install openjdk17</code> In addition, you also need the GNU m4 macro processor. <code>$ sudo apt install m4</code> == Setup == For the purposes of this guide, the Android SDK command-line tools, NDK as well as the Emacs source will be installed to $HOME/android. You can download the Android SDK from [https://developer.android.com/studio developer.android.com/studio] and the NDK from [https://developer.android.com/ndk/ developer.android.com/ndk/]. You can get the Emacs source from the official Savannah [[Git]] repository or through a release tarball from a GNU ftp mirror. For this example, we're using the Git upstream. <code>$ git clone git://git.git.savannah.gnu.org/emacs.git $HOME/android/emacs</code> Finally, install the Android platform and build tools using the SDK command-line tools. This guide assumes your working-directory is $HOME/android past this point. As of september 2026, the minimum supported Android API version for the Emacs git upstream is 37.0, which corresponds to Android 17. You can check your source's minimum API version in the java/INSTALL text file in the Emacs source tree. <syntaxhighlight lang="text"> $ cmdline-tools/bin/sdkmanager --sdk_root=$HOME/android "platforms;android-37.0" $ cmdline-tools/bin/sdkmanager --sdk_root=$HOME/android "build-tools;37.0.0" </syntaxhighlight> This will install <code>android.jar</code> to <code>$HOME/android/platforms/android-37.0/android.jar</code> and the build tools to <code>$HOME/android/build-tools/37.0.0/</code>. == Dependencies == This step is technically optional, but skipping it means building Emacs without basic features including basic image and HTTPS support. If you want either of those images, all of these are required. This also is not a comprehensive list, but rather a general guide, so less important features that require more work to implement, such as SVG image and [[SELinux]] support are left out. If you need any of those, the process for adding them and their dependencies is the same as adding the other features. First, create a directory for the dependencies. For this guide, we will use: <code>$ mkdir emacs/andeps</code> Download the most recent versions of the following packages from [https://sourceforge.net/projects/android-ports-for-gnu-emacs/files/ sourceforge.net/projects/android-ports-for-gnu-emacs/files]: * giflib * gmp * gnutls * harfbuzz * libjpeg-turbo * libpng * libtasn1 * libxml2 * nettle * p11-kit * tiff * tree-sitter and place the tarballs in <code>$HOME/emacs/andeps/</code> and extract them, eg. <syntaxhighlight lang="text"> $ cd emacs/andeps $ tar -xf libjpeg-turbo-3.0.2-emacs.tar.gz </syntaxhighlight> You should now have a directory named something like 'libjpeg-turbo-3.0.2' in the 'andeps' directory containing <code>Android.mk</code>, among other files. Do this for all the tarballs until all are extracted to their individual directories under 'andeps'. == Build == Everything is now set-up to build GNU Emacs properly. Finally, go to the Emacs source directory and configure Emacs. The <code>--with-android</code> configuration option should point to the android.jar file in the installed Android platform directory. <code>ANDROID_CC</code> should point to the Android NDK [[C]] compiler of the target architecture, which this guide assumes is 64-bit ARM (aarch64). <code>SDK_BUILD_TOOLS</code> should point to the directory of the installed Android build tools. Finally, <code>--with-ndk-path</code> should be a '''space-seperated''' list of paths to all, if any, of the dependencies you have chosen to include. <syntaxhighlight lang="text"> $ cd $HOME/android/emacs $ ./autogen.sh $ ./configure --with-android=$HOME/android/platforms/android-37.0/android.jar \ ANDROID_CC=$HOME/android/android-ndk-r30-beta3/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android37-clang \ SDK_BUILD_TOOLS=$HOME/android/build-tools/37.0.0 \ --with-ndk-path="$HOME/android/emacs/andeps/giflib-5.2.1 $HOME/android/emacs/andeps/gmp-6.3.0 \ $HOME/android/emacs/andeps/gnutls-3.8.5 $HOME/android/emacs/andeps/harfbuzz-7.1.0 \ $HOME/android/emacs/andeps/libjpeg-turbo-3.0.2 $HOME/android/emacs/andeps/libpng-1.6.41 \ $HOME/android/emacs/andeps/libtasn1-4.19.0 $HOME/android/emacs/andeps/libxml2-2.12.4 \ $HOME/android/emacs/andeps/nettle-3.8 $HOME/android/emacs/andeps/p11-kit-0.24.1 \ $HOME/android/emacs/andeps/tiff-4.5.1 $HOME/android/emacs/andeps/tree-sitter-0.26.3 $HOME/android/emacs/andeps/webp" </syntaxhighlight> '''Make sure to change the configure flags and variables to match your setup.''' If configure finishes with no errors, you can run <code>make</code> to compile Emacs. This will build the .apk file to <code>java/emacs-<version>-<api-version>-<abi>.apk</code> in the Emacs source tree. 1872b011f1d2857c9685fba3244b5f7718bb3c99 6115 6111 2026-09-04T08:15:17Z Imnotgoodatnames 121 Minor fixes wikitext text/x-wiki {{GuideWarning}} {{DISPLAYTITLE:Guides: Building GNU Emacs for Android}} This guide is for building and packaging [[GNU Emacs]] as an [[Android]] .apk application. For compiling GNU Emacs in Termux, see [[Guides:Emacs Installation Guide#Installing from Source]]. Building GNU Emacs for Android is a slightly more involved process as it requires unique build options and dependencies. It is currently only officially supported on x86_64 GNU/Linux systems, though, in theory, it may work on [[M1|Apple silicon]]-based [[macOS]] devices as well. == Requirements == You need to have a working Java compiler from OpenJDK. You can usually install it using your operating system's package manager, eg. <code>$ sudo apt install openjdk17</code> In addition, you also need the GNU m4 macro processor. <code>$ sudo apt install m4</code> == Setup == For the purposes of this guide, the Android SDK command-line tools, NDK as well as the Emacs source will be installed to $HOME/android. You can download the Android SDK from [https://developer.android.com/studio developer.android.com/studio] and the NDK from [https://developer.android.com/ndk/ developer.android.com/ndk/]. You can get the Emacs source from the official Savannah [[Git]] repository or through a release tarball from a GNU ftp mirror. For this example, we're using the Git upstream. <code>$ git clone git://git.git.savannah.gnu.org/emacs.git $HOME/android/emacs</code> Finally, install the Android platform and build tools using the SDK command-line tools. This guide assumes your working-directory is $HOME/android past this point. As of september 2026, the minimum supported Android API version for the Emacs git upstream is 37.0, which corresponds to Android 17. You can check your source's minimum API version in the java/INSTALL text file in the Emacs source tree. <syntaxhighlight lang="text"> $ cmdline-tools/bin/sdkmanager --sdk_root=$HOME/android "platforms;android-37.0" $ cmdline-tools/bin/sdkmanager --sdk_root=$HOME/android "build-tools;37.0.0" </syntaxhighlight> This will install <code>android.jar</code> to <code>$HOME/android/platforms/android-37.0/android.jar</code> and the build tools to <code>$HOME/android/build-tools/37.0.0/</code>. == Dependencies == This step is technically optional, but skipping it means building Emacs without basic features including basic image and HTTPS support. If you want either of those images, all of these are required. This also is not a comprehensive list, but rather a general guide, so less important features that require more work to implement, such as SVG image and [[SELinux]] support are left out. If you need any of those, the process for adding them and their dependencies is the same as adding the other features. First, create a directory for the dependencies. For this guide, we will use: <code>$ mkdir emacs/andeps</code> Download the most recent versions of the following packages from [https://sourceforge.net/projects/android-ports-for-gnu-emacs/files/ sourceforge.net/projects/android-ports-for-gnu-emacs/files]: * giflib * gmp * gnutls * harfbuzz * libjpeg-turbo * libpng * libtasn1 * libxml2 * nettle * p11-kit * tiff * tree-sitter and place the tarballs in <code>$HOME/emacs/andeps/</code> and extract them, eg. <syntaxhighlight lang="text"> $ cd emacs/andeps $ tar -xf libjpeg-turbo-3.0.2-emacs.tar.gz </syntaxhighlight> You should now have a directory named something like 'libjpeg-turbo-3.0.2' in the 'andeps' directory containing <code>Android.mk</code>, among other files. Do this for all the tarballs until all are extracted to their individual directories under 'andeps'. == Build == Everything is now set-up to build GNU Emacs properly. Finally, go to the Emacs source directory and configure Emacs. The <code>--with-android</code> configuration option should point to the android.jar file in the installed Android platform directory. <code>ANDROID_CC</code> should point to the Android NDK [[C]] compiler of the target architecture, which this guide assumes is 64-bit ARM (aarch64). <code>SDK_BUILD_TOOLS</code> should point to the directory of the installed Android build tools. Finally, <code>--with-ndk-path</code> should be a '''space-seperated''' list of paths to all, if any, of the dependencies you have chosen to include. <syntaxhighlight lang="text"> $ cd $HOME/android/emacs $ ./autogen.sh $ ./configure --with-android=$HOME/android/platforms/android-37.0/android.jar \ ANDROID_CC=$HOME/android/android-ndk-r30-beta3/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android37-clang \ SDK_BUILD_TOOLS=$HOME/android/build-tools/37.0.0 \ --with-ndk-path="$HOME/android/emacs/andeps/giflib-5.2.1 $HOME/android/emacs/andeps/gmp-6.3.0 \ $HOME/android/emacs/andeps/gnutls-3.8.5 $HOME/android/emacs/andeps/harfbuzz-7.1.0 \ $HOME/android/emacs/andeps/libjpeg-turbo-3.0.2 $HOME/android/emacs/andeps/libpng-1.6.41 \ $HOME/android/emacs/andeps/libtasn1-4.19.0 $HOME/android/emacs/andeps/libxml2-2.12.4 \ $HOME/android/emacs/andeps/nettle-3.8 $HOME/android/emacs/andeps/p11-kit-0.24.1 \ $HOME/android/emacs/andeps/tiff-4.5.1 $HOME/android/emacs/andeps/tree-sitter-0.26.3 $HOME/android/emacs/andeps/webp" </syntaxhighlight> '''Make sure to change the configure flags and variables to match your setup.''' If configure finishes with no errors, you can run <code>make</code> to compile Emacs. This will build the .apk file to <code>java/emacs-<version>-<api-version>-<abi>.apk</code> in the Emacs source tree. 82957723132466ee66a797e4c6d774b0bcdb8adf 0 1265 6113 5703 2026-09-04T00:54:24Z Int 401 Clarify Wine acronym wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Wine | image = [[File:Wine Logo.png|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = [[C]] | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. "Wine" is a recursive acronym for ''Wine Is Not an Emulator''. Wine does not perform emulation of a Windows system; it provides libraries (DLLs) needed by the Windows programs, and these libraries are implemented to instead invoke Linux system calls, similar to how [[Cygwin]] functions on Windows. This makes its performance much better than other emulation software.<ref>[https://www.howtogeek.com/windows-apps-in-wine-vs-vms/ Running Windows Apps in Wine vs. VMs: Which Is Better?], How-To Geek, 2024 (Accessed: 11 June 2026)</ref> Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. == Installation == {{Guide Warning}} === [[Arch Linux]] === Stable: <syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight> Staging: <syntaxhighlight lang="sh">sudo pacman -S wine-staging</syntaxhighlight> === [[Fedora Linux]] === Wine stable is available via <code>sudo dnf install wine</code>. Other versions of Wine are available in [[Terra]] under the package name <code>terra-wine-stable</code>, <code>terra-wine-staging</code>, and <code>terra-wine-dev</code>. [[Winetricks]] and [[dxvk]] support (mentioned [[#dxvk|below]]) are also provided via <code>terra-winetricks</code> and <code>terra-wine-dxvk</code>. <code>[[protontricks]]</code>, <code>winetricks</code>, and <code>winetricks-git</code> are also available in Fedora. == Usage == Wine is a [[CLI|command-line]] program. Provide a Windows executable file for Wine to run: <syntaxhighlight lang="sh">wine <path to .exe></syntaxhighlight> === Prefixes === Wine stores configuration files and installed programs inside a ''Wine prefix''. Wine prefixes contain a minimal Windows filesystem (a.k.a. ''C: drive''). The default Wine prefix is <code>~/.wine</code>. You can modify the <code>WINEPREFIX</code> environment variable to change it. For example, to use the directory <code>myprefix/</code> as the Wine prefix to run <code>application.exe</code>: <syntaxhighlight lang="sh">WINEPREFIX=myprefix wine application.exe</syntaxhighlight> == Performance == === dxvk === By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). == References == <references /> 86ce3ea632402ac6b05e21b18305ff16ec1c0ef1 6114 6113 2026-09-04T07:53:21Z Imnotgoodatnames 121 Cygwin isn't really like Wine at all. Cygwin uses a dll to implement POSIX functions in Windows. Cygwin binaries are native Windows binaries, it can't run Linux binaries wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Wine | image = [[File:Wine Logo.png|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = [[C]] | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. "Wine" is a recursive acronym for ''Wine Is Not an Emulator''. Wine does not perform emulation of a Windows system; it provides libraries (DLLs) needed by the Windows programs, and these libraries are implemented to instead invoke Linux system calls, similar to how [[WSL]] 1 functions on Windows. This makes its performance much better than other emulation software.<ref>[https://www.howtogeek.com/windows-apps-in-wine-vs-vms/ Running Windows Apps in Wine vs. VMs: Which Is Better?], How-To Geek, 2024 (Accessed: 11 June 2026)</ref> Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. == Installation == {{Guide Warning}} === [[Arch Linux]] === Stable: <syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight> Staging: <syntaxhighlight lang="sh">sudo pacman -S wine-staging</syntaxhighlight> === [[Fedora Linux]] === Wine stable is available via <code>sudo dnf install wine</code>. Other versions of Wine are available in [[Terra]] under the package name <code>terra-wine-stable</code>, <code>terra-wine-staging</code>, and <code>terra-wine-dev</code>. [[Winetricks]] and [[dxvk]] support (mentioned [[#dxvk|below]]) are also provided via <code>terra-winetricks</code> and <code>terra-wine-dxvk</code>. <code>[[protontricks]]</code>, <code>winetricks</code>, and <code>winetricks-git</code> are also available in Fedora. == Usage == Wine is a [[CLI|command-line]] program. Provide a Windows executable file for Wine to run: <syntaxhighlight lang="sh">wine <path to .exe></syntaxhighlight> === Prefixes === Wine stores configuration files and installed programs inside a ''Wine prefix''. Wine prefixes contain a minimal Windows filesystem (a.k.a. ''C: drive''). The default Wine prefix is <code>~/.wine</code>. You can modify the <code>WINEPREFIX</code> environment variable to change it. For example, to use the directory <code>myprefix/</code> as the Wine prefix to run <code>application.exe</code>: <syntaxhighlight lang="sh">WINEPREFIX=myprefix wine application.exe</syntaxhighlight> == Performance == === dxvk === By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). == References == <references /> 15eb12f0ab70b6148540b5848b839cc2d8c97bc6 6116 6114 2026-09-04T10:15:11Z Imnotgoodatnames 121 Replace logo with SVG wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Wine | image = [[File:WINE-logo.svg|100px]] | releasestatus = Maintained | lastrelease = Stable: 11.0<ref>{{Cite|url=https://www.winehq.org/news/2026011301|title=Wine 11.0 Released|accessdate=26 May 2026|year=2026}}</ref> Preview: 11.9<ref>{{Cite|url=https://gitlab.winehq.org/wine/wine/-/releases/wine-11.9|title=Wine 11.9|accessdate=26 May 2026|year=2026}}</ref> | languages = [[C]] | developers = Wine authors | website = https://winehq.org | license = LGPL-2.1-or-later | sourcecode = https://gitlab.winehq.org/wine/wine | firstrelease = 4 July 1993; 32 years ago }} Wine is a compatibility layer allowing [[Windows]] applications to run on [[UNIX]]-like operating systems<ref>{{Cite|url=https://www.winehq.org/|title=WineHQ|accessdate=26 May 2026}}</ref>. "Wine" is a recursive acronym for ''Wine Is Not an Emulator''. Wine does not perform emulation of a Windows system; it provides libraries (DLLs) needed by the Windows programs, and these libraries are implemented to instead invoke Linux system calls, similar to how [[WSL]] 1 functions on Windows. This makes its performance much better than other emulation software.<ref>[https://www.howtogeek.com/windows-apps-in-wine-vs-vms/ Running Windows Apps in Wine vs. VMs: Which Is Better?], How-To Geek, 2024 (Accessed: 11 June 2026)</ref> Wine aims to remain stable and compatible with most Windows applications. However, newer applications may need certain patches to run correctly, in which case Wine provides a "staging" build with experimental patches that are not yet accepted upstream. == Installation == {{Guide Warning}} === [[Arch Linux]] === Stable: <syntaxhighlight lang="sh">sudo pacman -S wine</syntaxhighlight> Staging: <syntaxhighlight lang="sh">sudo pacman -S wine-staging</syntaxhighlight> === [[Fedora Linux]] === Wine stable is available via <code>sudo dnf install wine</code>. Other versions of Wine are available in [[Terra]] under the package name <code>terra-wine-stable</code>, <code>terra-wine-staging</code>, and <code>terra-wine-dev</code>. [[Winetricks]] and [[dxvk]] support (mentioned [[#dxvk|below]]) are also provided via <code>terra-winetricks</code> and <code>terra-wine-dxvk</code>. <code>[[protontricks]]</code>, <code>winetricks</code>, and <code>winetricks-git</code> are also available in Fedora. == Usage == Wine is a [[CLI|command-line]] program. Provide a Windows executable file for Wine to run: <syntaxhighlight lang="sh">wine <path to .exe></syntaxhighlight> === Prefixes === Wine stores configuration files and installed programs inside a ''Wine prefix''. Wine prefixes contain a minimal Windows filesystem (a.k.a. ''C: drive''). The default Wine prefix is <code>~/.wine</code>. You can modify the <code>WINEPREFIX</code> environment variable to change it. For example, to use the directory <code>myprefix/</code> as the Wine prefix to run <code>application.exe</code>: <syntaxhighlight lang="sh">WINEPREFIX=myprefix wine application.exe</syntaxhighlight> == Performance == === dxvk === By default, [[wikipedia:DirectX|DirectX]] 1-11 calls under Wine are translated into [[wikipedia:OpenGL|OpenGL]] using Wine's built-in DirectX implementation named WineD3D. While WineD3D may work for regular applications, it is often slow and buggy when gaming. [https://github.com/doitsujin/dxvk dxvk] is an alternative DirectX implementation that translates DirectX 8-11 calls into [https://www.vulkan.org/ Vulkan]. It beats WineD3D in terms of performance and compatibility for most games. You can install the latest version using [[Winetricks]]:<syntaxhighlight lang="sh"> winetricks dxvk </syntaxhighlight>DirectX 12 is not affected because Wine already includes a fast and compatible implementation of DirectX 12 named VKD3D (separate from WineD3D). == References == <references /> 5c66d299c408e6a5861ba39727e69008f5805ff8 6 1453 6117 2026-09-04T11:29:07Z Imnotgoodatnames 121 Bash and Mintty running on ReactOS using Cygwin 2.874 x86_64 wikitext text/x-wiki == Summary == Bash and Mintty running on ReactOS using Cygwin 2.874 x86_64 == Licensing == {{GPL}} af936f7a5ed7e55f8022254dc2f7e79681c4aadc 0 1394 6118 5935 2026-09-04T12:17:53Z Imnotgoodatnames 121 Add terminal emulator, package managment stuff with images and refs wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Cygwin | image = [[File:Cygwin_logo.svg|frameless|upright=0.6]] | releasestatus = Maintained | lastrelease = Stable: 3.6.9 | languages = [[C]], [[C++]] | developers = Cygnus Solutions, Red Hat<ref>{{Cite|url=https://access.redhat.com/solutions/78783|title= Is Cygwin supported?|year=2024|accessdate=24 July 2026}}</ref> | website = https://cygwin.com | license = [[GPL|GPLv3]], [[GPL#GNU_Lesser_General_Public_License_(LGPL)|LGPLv3]] | sourcecode = https://cygwin.com/git/newlib-cygwin.git | firstrelease = 18 October 1995 }} '''Cygwin''' is a Unix-compatible environment for [[Windows|Microsoft Windows]]. It consists of a library that translates [[POSIX]] system calls to Windows ones, as well as a distribution of free software built on it.<ref>[https://cygwin.com/ Cygwin] (accessed 2026-07-29)</ref> The core of Cygwin is the cygwin1.dll file, a library which provides core POSIX API functionality and to which all Cygwin-based software is dynamically linked to.<ref>[https://cygwin.com/faq.html#faq.programming.static-linking Cygwin FAQ] (accessed 2026-09-04)</ref> == Terminal emulator == ''Main page: [[Mintty]]'' [[File:Cygwin-ReactOS.png|Cygwin shell running in mintty on [[ReactOS]].|thumb|upright=1.5]] Since 2011, the default [[terminal emulator]] for Cygwin has been the PuTTY-based ''Mintty'', a Cygwin-based [[xterm]]-compatible terminal emulator for Windows.<ref>[https://cygwin.com/legacy-ml/cygwin-announce/2011-11/msg00040.html Updated: mintty-1.0.2-1]</ref> However, Cygwin-based programs do not depend on it and the Windows Console, Windows Terminal and other terminal emulators, such as [[Konsole]], can run a Cygwin shell as well. == Package managment == [[File:Cgywin select packages.zh.png|Cygwin package selection screen|thumb]] Cygwin does not have a traditional [[package Manager|package manager]] like the ones used by most [[linux Distributions|Linux distributions]]. Instead, Cygwin packages are installed, updated and removed during the 'Select Packages' step of the Cygwin setup. The setup must be re-run to manage packages every time after the initial installation.<ref>[https://cygwin.com/install.html Installing and Updating Cygwin Packages] (accessed 2026-09-04)</ref> ==Cygwin/X== '''Cygwin/X''' is an implementation of the [[X_Window_System|X windowing system]] for Microsoft Windows, and a part of the Cygwin project. It allows X-based Cygwin and Cygwin-based software to run graphically on Windows.<ref>[https://x.cygwin.com/ Cygwin/X] (accessed 2026-07-29)</ref> == References == cf6ced3cd2a50314d381e463cc14a7e67d5a664d 0 1454 6119 2026-09-04T15:36:45Z Imnotgoodatnames 121 Create page with screenshot, refs, infobox etcetera wikitext text/x-wiki {{DISPLAYTITLE:mintty}} {{SoftwareInfobox | image = [[File:Konsole_icon.svg|frameless]] | caption = Oxygen theme Konsole icon, used by mintty | title = mintty | developers = Andy Koppe, Thomas Wolff | releasestatus = Maintained | lastrelease = 3.8.3 | languages = [[C]] | website = [https://mintty.github.io mintty.github.io] | license = [[GNU General Public License|GPLv3]] }} [[File:Cygwin-ReactOS.png|mintty running on [[ReactOS]]|thumb|upright=1.5]] '''Mintty''' is an [[XTerm]]-compatible [[terminal emulator]] for [[Microsoft Windows]] based on [[PuTTY]].<ref name=site>[https://mintty.github.io/ Mintty] (accessed 2026-09-04)</ref><ref>[https://www.softpedia.com/get/System/System-Miscellaneous/MinTTY.shtml MinTTY - Softpedia] (accessed 2026-09-04)</ref> It relies [[Cygwin]] for its [[POSIX]]-compatible API and is its and [[MSYS2]]'s default terminal emulator.<ref>[https://cygwin.com/legacy-ml/cygwin-announce/2011-11/msg00040.html Updated: mintty-1.0.2-1] (accessed 2026-09-04)</ref><ref>[https://www.msys2.org/docs/terminals/ Terminals] (accessed 2026-09-04)</ref> It also officially supports [[WSL]] and native Windows software generally works using ''ConPTY''.<ref>[https://github.com/mintty/mintty/wiki/Tips#inputoutput-interaction-with-alien-programs Input/Output interaction with alien programs] (accessed 2026-09-04)</ref> b2b1db16c9053c21f9a1a3b18492a5a575e3bdaa 0 1455 6120 2026-09-04T16:41:36Z Imnotgoodatnames 121 Create page, stub, infobox, screenshot wikitext text/x-wiki {{Stub}} {{DISPLAYTITLE:xterm}} {{SoftwareInfobox | title = xterm | image = [[File:Icon_of_XTerm_(from_2012).svg|128px]] | caption = XTerm icon | developers = Mark Vandevoorde (original) Thomas Dickey | releasestatus = Maintained | lastrelease = 411 | languages = [[C]] | website = [https://invisible-island.net/xterm/ invisible-island.net/xterm/ ] | license = [[MIT License|MIT]]/X consortium }} [[File:Edwind.png|thumb|[[ed]] running in xterm]] '''xterm''', often stylized as '''XTerm''' is the standard [[X Window System|X]] [[terminal emulator]].<ref name=faq>[https://invisible-island.net/xterm/xterm.faq.html What is XTerm?]</ref> It emulates the VT100 and Tektronix 4014 terminals.<ref name=manpage>[https://manpage.me/?q=xterm XTERM(1)]</ref> Since its original development in 1984, xterm has gotten new features including Unicode support, TrueType font support, a menu bar and a scroll bar.<ref name=manpage/> UXterm is a thin XTerm wrapper that launches XTerm with the Unicode-compatible [[UTF-8]] character encoding if it isn't already set.<ref>[https://manpage.me/?q=uxterm UXTERM(1)]</ref> Like many X applications, xterm can be customized using X Resources. xterm uses the ''XTerm'' resource class while uxterm uses ''UXTerm''.<ref name=faq/> d4b4975bbe02903bb7e9ff22507393fc71c52a94 0 1456 6121 2026-09-04T16:42:31Z Imnotgoodatnames 121 Create redirect wikitext text/x-wiki #REDIRECT [[xterm]] 6bb293c7aa0ef1cba8d29235eeba45db67957405 4 327 6122 4495 2026-09-04T20:47:27Z Atmois 13 test edit wikitext text/x-wiki linux is cool. why? because i said so. bye test [[File:Bazzitehyfetch.png|alt=test|thumb]] =References= 9a55f50c7981a6b0fdfcf9108af66b8353c76f01 0 1394 6123 6118 2026-09-05T07:18:25Z Imnotgoodatnames 121 Add MSYS info, minor fixes wikitext text/x-wiki [[Category:Software]] {{Stub}} {{SoftwareInfobox | title = Cygwin | image = [[File:Cygwin_logo.svg|frameless|upright=0.6]] | releasestatus = Maintained | lastrelease = Stable: 3.6.9 | languages = [[C]], [[C++]] | developers = Cygnus Solutions, Red Hat<ref>{{Cite|url=https://access.redhat.com/solutions/78783|title= Is Cygwin supported?|year=2024|accessdate=24 July 2026}}</ref> | website = https://cygwin.com | license = [[GPL|GPLv3]], [[GPL#GNU_Lesser_General_Public_License_(LGPL)|LGPLv3]] | sourcecode = https://cygwin.com/git/newlib-cygwin.git | firstrelease = 18 October 1995 }} '''Cygwin''' is a Unix-compatible environment for [[Windows|Microsoft Windows]]. It consists of a library that translates [[POSIX]] system calls to Windows ones, as well as a distribution of free software built on it.<ref>[https://cygwin.com/ Cygwin] (accessed 2026-07-29)</ref> The core of Cygwin is the cygwin1.dll file, a library which provides core POSIX API functionality and to which all Cygwin-based software is dynamically linked to.<ref>[https://cygwin.com/faq.html#faq.programming.static-linking Cygwin FAQ] (accessed 2026-09-04)</ref> == Terminal emulator == ''Main page: [[mintty]]'' [[File:Cygwin-ReactOS.png|Cygwin shell running in mintty on [[ReactOS]].|thumb|upright=1.5]] Since 2011, the default [[terminal emulator]] for Cygwin has been the PuTTY-based ''mintty'', a Cygwin-based [[xterm]]-compatible terminal emulator for Windows.<ref>[https://cygwin.com/legacy-ml/cygwin-announce/2011-11/msg00040.html Updated: mintty-1.0.2-1], 2011-11-20 (accessed 2026-09-05)</ref> However, Cygwin-based programs do not depend on it and the Windows Console, Windows Terminal and other terminal emulators, such as [[Konsole]], can run a Cygwin shell as well. == Package managment == [[File:Cgywin select packages.zh.png|Cygwin package selection screen|thumb]] Cygwin does not have a traditional [[package Manager|package manager]] like the ones used by most [[linux Distributions|Linux distributions]]. Instead, Cygwin packages are installed, updated and removed during the 'Select Packages' step of the Cygwin setup. The setup must be re-run to manage packages every time after the initial installation.<ref>[https://cygwin.com/install.html Installing and Updating Cygwin Packages] (accessed 2026-09-04)</ref> == Cygwin/X == '''Cygwin/X''' is an implementation of the [[X_Window_System|X windowing system]] for Microsoft Windows, and a part of the Cygwin project. It allows X-based Cygwin and Cygwin-based software to run graphically on Windows.<ref>[https://x.cygwin.com/ Cygwin/X] (accessed 2026-07-29)</ref> == MSYS == '''MSYS''' is a minimal Cygwin fork designed to provide a UNIX-like environment for the [[MinGW]] compiler toolchain.<ref>[https://web.archive.org/web/20190710133445/mingw.org/wiki/MSYS MSYS], 2008-01-18 (archived 2019-07-10)</ref> It used msys-1.0.dll, a modified version of the cygwin DLL. MSYS was installed alongside MinGW and uses its package manager ''mingw-get''.<ref>[https://web.archive.org/web/20190710134913/http://www.mingw.org/wiki/Getting_Started Getting Started], 2007-05-22 (archived 2019-07-10)</ref> MSYS was abandoned around 2010 and superseded by the [[MSYS2]] project, whose base Unix-like environment is also based on Cygwin.<ref>[https://cygwin.com/pipermail/cygwin/2013-June/209001.html Adding MSYS functionality to Cygwin], 2013-06-19 (accessed 2026-09-05)</ref><ref>[https://www.msys2.org/wiki/History/ History] (accessed 2026-09-05)</ref> == References == bf078692ee62cd6e81f22f139a1343b3c0a841c7 0 1454 6124 6119 2026-09-05T07:38:47Z Imnotgoodatnames 121 Minor rewording, add to category wikitext text/x-wiki [[Category:Software]] {{DISPLAYTITLE:mintty}} {{SoftwareInfobox | image = [[File:Konsole_icon.svg|frameless]] | caption = Oxygen theme Konsole icon, used by mintty | title = mintty | developers = Andy Koppe, Thomas Wolff | releasestatus = Maintained | lastrelease = 3.8.3 | languages = [[C]] | website = [https://mintty.github.io mintty.github.io] | license = [[GNU General Public License#GNU General Public License (GPL)|GPLv3]] }} [[File:Cygwin-ReactOS.png|mintty running on [[ReactOS]]|thumb|upright=1.5]] '''Mintty''' is an [[XTerm]]-compatible [[terminal emulator]] for [[Microsoft Windows]] based on [[PuTTY]].<ref name=site>[https://mintty.github.io/ Mintty] (accessed 2026-09-04)</ref><ref>[https://www.softpedia.com/get/System/System-Miscellaneous/MinTTY.shtml MinTTY - Softpedia] (accessed 2026-09-04)</ref> It relies [[Cygwin]] for its [[POSIX]]-compatible API and is its and [[MSYS2]]'s default terminal emulator.<ref>[https://cygwin.com/legacy-ml/cygwin-announce/2011-11/msg00040.html Updated: mintty-1.0.2-1] (accessed 2026-09-04)</ref><ref>[https://www.msys2.org/docs/terminals/ Terminals] (accessed 2026-09-04)</ref> Mintty also supports [[WSL]] and native Windows Console (ConHost) software generally works using ''ConPTY'', a compatibility layer providing seamless interaction between ConHost signals and Unix-style PTY ones.<ref>[https://github.com/mintty/mintty/wiki/Tips#inputoutput-interaction-with-alien-programs Input/Output interaction with alien programs] (accessed 2026-09-04)</ref><ref>[https://devblogs.microsoft.com/commandline/windows-command-line-introducing-the-windows-pseudo-console-conpty/ Windows Command-Line: Introducing the Windows Pseudo Console (ConPTY)], Rich Turner, 2018-08-02 (accessed 2026-09-05)</ref> ebc4d625f9f33ece4a0fb92d5d69f2d06c29b9cc 0 1455 6125 6120 2026-09-05T09:14:35Z Imnotgoodatnames 121 Minor rewording, add access date to references (oops), add Tek mode screenshot, bit more info on sixel wikitext text/x-wiki {{Stub}} {{DISPLAYTITLE:xterm}} {{SoftwareInfobox | title = xterm | image = [[File:Icon_of_XTerm_(from_2012).svg|128px]] | caption = XTerm icon | developers = Mark Vandevoorde (original) Thomas Dickey | releasestatus = Maintained | lastrelease = 411 | languages = [[C]] | website = [https://invisible-island.net/xterm/ invisible-island.net/xterm] | license = [[MIT License|MIT]]/X consortium | sourcecode = [https://invisible-mirror.net/archives/xterm/ invisible-mirror.net/archives/xterm] }} [[File:Edwind.png|thumb|[[ed]] running in xterm]] [[File:XTerm_tek_mode.png|thumb|XTerm in Tek mode with the Toolbar enabled displaying a graph.]] '''xterm''', often stylized as '''XTerm''' is the standard [[terminal emulator]] of the [[X Window System]].<ref name=faq>[https://invisible-island.net/xterm/xterm.faq.html What is XTerm?] (accessed 2026-09-04)</ref> It emulates the VT100 family of terminals as well as the Tektronix 4014 vector terminal.<ref name=manpage>[https://manpage.me/?q=xterm XTERM(1)] (accessed 2026-09-05)</ref> Since its original development in 1984, xterm has gotten new features including Unicode support, mouse support, TrueType font support, a menu bar and a scroll bar, many of which inspired and were implemented by later terminal emulators such as [[rxvt]] and [[Konsole]].<ref name=manpage/><ref>[https://tldp.org/HOWTO/Xterm-Title-6.html 6. Appendix: escapes for other terminal types] (accessed 2026-09-05)</ref> '''UXterm''' is a thin XTerm wrapper that launches XTerm with the Unicode-compatible [[UTF-8]] character encoding if it isn't already set.<ref>[https://manpage.me/?q=uxterm UXTERM(1)] (accessed 2026-09-05)</ref> Like many X applications, xterm can be customized using X Resources. xterm uses the ''XTerm'' resource class. uxterm uses its own resource class, ''UXTerm'', allowing it to set default X resources independently of the main XTerm program.<ref name=faq/> XTerm supports the [[sixel]] graphics format, allowing bitmap images to be rendered directly in the terminal window.<ref>[https://invisible-island.net/xterm/xterm.log.html#xterm_359 Patch #359], 2020-08-17 (accessed 2026-09-05)</ref> 191d2d325b1bc36fe30b459e0ea4e5330947792b 6146 6125 2026-09-06T16:31:13Z Imnotgoodatnames 121 Add platforms, references header wikitext text/x-wiki {{Stub}} {{DISPLAYTITLE:xterm}} {{SoftwareInfobox | title = xterm | image = [[File:Icon_of_XTerm_(from_2012).svg|128px]] | caption = XTerm icon | developers = Mark Vandevoorde (original) Thomas Dickey | releasestatus = Maintained | lastrelease = 411 | languages = [[C]] | website = [https://invisible-island.net/xterm/ invisible-island.net/xterm] | license = [[MIT License|MIT]]/X consortium | sourcecode = [https://invisible-mirror.net/archives/xterm/ invisible-mirror.net/archives/xterm] | platforms = [[Linux]], [[BSD]], [[GNU/Hurd|GNU (Hurd)]], [[Cygwin]], [[macOS]] }} [[File:Edwind.png|thumb|[[ed]] running in xterm]] [[File:XTerm_tek_mode.png|thumb|XTerm in Tek mode with the Toolbar enabled displaying a graph.]] '''xterm''', often stylized as '''XTerm''' is the standard [[terminal emulator]] of the [[X Window System]].<ref name=faq>[https://invisible-island.net/xterm/xterm.faq.html What is XTerm?] (accessed 2026-09-04)</ref> It emulates the VT100 family of terminals as well as the Tektronix 4014 vector terminal.<ref name=manpage>[https://manpage.me/?q=xterm XTERM(1)] (accessed 2026-09-05)</ref> Since its original development in 1984, xterm has gotten new features including Unicode support, mouse support, TrueType font support, a menu bar and a scroll bar, many of which inspired and were implemented by later terminal emulators such as [[rxvt]] and [[Konsole]].<ref name=manpage/><ref>[https://tldp.org/HOWTO/Xterm-Title-6.html 6. Appendix: escapes for other terminal types] (accessed 2026-09-05)</ref> '''UXterm''' is a thin XTerm wrapper that launches XTerm with the Unicode-compatible [[UTF-8]] character encoding if it isn't already set.<ref>[https://manpage.me/?q=uxterm UXTERM(1)] (accessed 2026-09-05)</ref> Like many X applications, xterm can be customized using X Resources. xterm uses the ''XTerm'' resource class. uxterm uses its own resource class, ''UXTerm'', allowing it to set default X resources independently of the main XTerm program.<ref name=faq/> XTerm supports the [[sixel]] graphics format, allowing bitmap images to be rendered directly in the terminal window.<ref>[https://invisible-island.net/xterm/xterm.log.html#xterm_359 Patch #359], 2020-08-17 (accessed 2026-09-05)</ref> == References == 012002a3c803f5cf252a642f6bd27754d0505ee8 0 1127 6126 4834 2026-09-05T14:45:15Z Imnotgoodatnames 121 Add infobox. removed License and 'Source code location' parts since they're now in the infobox, added no citations template wikitext text/x-wiki {{Needs Citations}} [[Category:Software]] [[Category:Browsers]] {{DISPLAYTITLE:LibreWolf}} {{SoftwareInfobox |image = [[File:LibreWolf Icon.png|256px]] |caption = LibreWolf logo |title = LibreWolf |releasestatus = Maintained |lastrelease = 155.0-1 |languages = [[C++]], [[C]], [[JavaScript]] |developers = LibreWolf Community |website = [https://librewolf.net librewolf.net] | license = [[MPL|MPL 2.0]] [[GNU General Public License#GNU Affero General Public License (AGPL)|AGPLv3]] (website) | sourcecode = [https://codeberg.org/librewolf codeberg.org/librewolf] [https://gitlab.com/librewolf-community gitlab.com/librewolf.community] }} LibreWolf is an open-source fork of the browser Mozilla [[Firefox]] focused on privacy and security. Their website is https://librewolf.net. It was originally released for Linux in March 2020 with a community-maintained version being released for Microsoft Windows in February 2021 and a Mac port following a few months later in April 2021. == Features == LibreWolf's main purpose is privacy, therefore the features it adds are all mainly privacy-based. Some features LibreWolf adds include uBlock Origin by default, disabled telemetry, DuckDuckGo as the default search engine, cookies and history being wiped on closing of browser by default, and Firefox Sync being disabled by default. == Current Linux distro support == [[Gentoo]], [[Arch Linux|Arch]], Debian-based, [[Fedora]], [[openSUSE]] and available to any other distro via a [[Flatpak]] and an AppImage. == Windows support == You can get LibreWolf on Windows via the Microsoft Store, a portable release as just a .exe or with [[Package Manager|Package Managers]] like Scoop, Chocolatey and Winget. f47fe478a63b23c94884ee394dcdf675a60ca030 0 1395 6127 5899 2026-09-05T17:56:22Z Imnotgoodatnames 121 Minor rewording; added XWayland, remote connection, root window info, Cygwin/X, XQuartz all with refs; removed stub thing wikitext text/x-wiki {{SoftwareInfobox | title = X Window System | image = [[File:X11.svg{{!}}class=skin-invert|frameless|upright=0.6]] | caption = X logo | releasestatus = Maintained | firstrelease = 19 June 1984; 42 years ago | lastrelease = Stable: X11R7.7<ref>{{Cite|url=https://www.x.org/Releases/7.7/|title=7.7|year=2012|accessdate=24 July 2026}}</ref> | languages = [[C]] | developers = Project Athena, X.Org Foundation | website = [https://x.org x.org] | license = [[MIT_License|MIT]] (X.Org; historical implementations varied) | sourcecode = [https://gitlab.freedesktop.org/xorg gitlab.freedesktop.org/xorg] }} [[File:Twm.png|thumb|An X11 desktop running the [[twm]] window manager]] The '''X Window System''' is a windowing system common on [[Unix-like]] operating systems. It provides a [[GUI|graphical user interface]], and functions as a server-client system where the server is the machine with the display, and the client is the program accessing the display, which may or may not be connected remotely. '''X''' reads and sets various characteristics of the display and manages drawing windows as requested by clients. X is usually paired with an [[X Window Manager]], which manages the size, position and decorations of windows. X has been on version 11 since 1987, which is why it's commonly referred to as ''[[X11]]''. The '''root window''' is the static, background window that covers the entire display. All other X windows are drawn on top of the root window.<ref>[https://www.x.org/guide/concepts/ X Window System Concepts] (accessed 2026-09-05)</ref> The [[X.Org]] Foundation's X server has been the de facto standard X server implementation since its creation in 2004. == Remote connections == X allows remote connections between clients and servers either directly over TCP or, more commonly, using the [[SSH|OpenSSH]] <code>-X</code> and <code>-Y</code> flags, which enable regular and trusted X11 forwarding, respectively. == XWayland == '''XWayland''' is an X server developed by the X.Org foundation intended to run X clients on a [[Wayland]] desktop.<ref>[https://wayland.freedesktop.org/docs/book/Xwayland.html X11 Application Support] (accessed 2026-09-05)</ref> XWayland generally runs in rootless - i.e. without a visible root window - mode, where individual X windows are displayed inside Wayland windows, though it can also run "rootful" - with the entire X server in one window.<ref>[https://bennett.dev/rootful-xwayland/ Run buggy X11 apps with Xwayland rootful mode], Bennett Hardwick (accessed 2026-09-05)</ref> == Cygwin/X == ''Main page: [[Cygwin#Cygwin/X|Cygwin/X]]'' '''Cygwin/X''' is the [[Cygwin]] project's X server based on X.Org server.<ref>[https://x.cygwin.com Cygwin/X] (accessed 2026-09-05)</ref> It allows running X clients on [[Microsoft Windows]] in both rooted and rootless modes.<ref>[https://x.cygwin.com/docs/man1/XWin.1.html XWin(1)], 2021-12-12 (accessed 2026-09-05)</ref> == XQuartz == ''Main page: [[XQuartz]]'' '''XQuartz''' is an implementation of the X.Org server for [[macOS]] originally developed by Apple. It includes the ''quartz-wm'' X window manager, a stacking window manager with OS X-like aesthetics.<ref>[https://www.xquartz.org/index.html XQuartz] (accessed 2026-09-05)</ref> XQuartz can run in rootless and rootful modes, although it relies on the X Window Manager for window decorations in either mode; thus, XQuartz must be used with a window manager such as ''quartz-wm'' even in rootless mode.<ref>[https://www.xquartz.org/index.html Remote X11 Window Manager on XQuartz], 2024-04-06 (accessed 2026-09-05)</ref><ref>[https://gitlab.freedesktop.org/xorg/app/quartz-wm xorg/app/quartz-wm] (accessed 2026-09-05)</ref> == References == ef16040d73f74be79d264a97b1ec95e830cb2a41 6150 6127 2026-09-26T09:04:41Z Imnotgoodatnames 121 Add WM & DE part, refs wikitext text/x-wiki {{SoftwareInfobox | title = X Window System | image = [[File:X11.svg{{!}}class=skin-invert|frameless|upright=0.6]] | caption = X logo | releasestatus = Maintained | firstrelease = 19 June 1984; 42 years ago | lastrelease = Stable: X11R7.7<ref>{{Cite|url=https://www.x.org/Releases/7.7/|title=7.7|year=2012|accessdate=24 July 2026}}</ref> | languages = [[C]] | developers = Project Athena, X.Org Foundation | website = [https://x.org x.org] | license = [[MIT_License|MIT]] (X.Org; historical implementations varied) | sourcecode = [https://gitlab.freedesktop.org/xorg gitlab.freedesktop.org/xorg] }} [[File:Twm.png|thumb|An X11 desktop running the [[twm]] window manager]] The '''X Window System''' is a windowing system common on [[Unix-like]] operating systems. It provides a [[GUI|graphical user interface]], and functions as a server-client system where the server is the machine with the display, and the client is the program accessing the display, which may or may not be connected remotely. '''X''' reads and sets various characteristics of the display and manages drawing windows as requested by clients. X is usually paired with an [[X Window Manager]], which manages the size, position and decorations of windows. X has been on version 11 since 1987, which is why it's commonly referred to as ''[[X11]]''. The '''root window''' is the static, background window that covers the entire display. All other X windows are drawn on top of the root window.<ref>[https://www.x.org/guide/concepts/ X Window System Concepts] (accessed 2026-09-05)</ref> The [[X.Org]] Foundation's X server has been the de facto standard X server implementation since its creation in 2004. == Desktop environments and window managers == ''Main pages: [[X_Window_Manager|X window manager]], [[Desktop Environments|Desktop environments]]'' [[File:LinuxMint22-Wilma-English.png|thumb|[[Cinnamon]], the default desktop environment of [[Linux Mint]], runs on X11 by default.]] A '''window manager''' is a program that manages the size, position, decorations and window borders of X client windows. A window manager allows the user to move, resize, close and otherwise manage windows using keyboard shortcuts and/or GUI elements such as buttons and menus.<ref>[https://dev.to/heiytor/writing-a-window-manager-from-scratch-part-i-2fb8 Writing a Window Manager From Scratch Part I ], Heitor Danilo, 2024-01-23 (accessed 2026-09-26)</ref> A '''desktop environment''' is a bundle of software including a window manager that together provide a unified look and feel to the desktop. Desktop environments provide common desktop tools such as a [[shell|GUI shell]], file manager, image viewer, options manager and a [[X compositor|compositor]], among others.<ref>[https://www.computerhope.com/jargon/d/desktop-environment.htm Desktop environment], Computer Hope, 2024-07-18 (accessed 2026-09-26)</ref> == Remote connections == X allows remote connections between clients and servers either directly over TCP or, more commonly, using the [[SSH|OpenSSH]] <code>-X</code> and <code>-Y</code> flags, which enable regular and trusted X11 forwarding, respectively.<ref>[https://man.openbsd.org/ssh.1 ssh(1)], 2026-09-05 (accessed 2026-09-26)</ref> == XWayland == '''XWayland''' is an X server developed by the X.Org foundation intended to run X clients on a [[Wayland]] desktop.<ref>[https://wayland.freedesktop.org/docs/book/Xwayland.html X11 Application Support] (accessed 2026-09-05)</ref> XWayland generally runs in rootless - i.e. without a visible root window - mode, where individual X windows are displayed inside Wayland windows, though it can also run "rootful" - with the entire X server in one window.<ref>[https://bennett.dev/rootful-xwayland/ Run buggy X11 apps with Xwayland rootful mode], Bennett Hardwick (accessed 2026-09-05)</ref> == Cygwin/X == ''Main page: [[Cygwin#Cygwin/X|Cygwin/X]]'' '''Cygwin/X''' is the [[Cygwin]] project's X server based on X.Org server.<ref>[https://x.cygwin.com Cygwin/X] (accessed 2026-09-05)</ref> It allows running X clients on [[Microsoft Windows]] in both rooted and rootless modes.<ref>[https://x.cygwin.com/docs/man1/XWin.1.html XWin(1)], 2021-12-12 (accessed 2026-09-05)</ref> == XQuartz == ''Main page: [[XQuartz]]'' '''XQuartz''' is an implementation of the X.Org server for [[macOS]] originally developed by Apple. It includes the ''quartz-wm'' X window manager, a stacking window manager with OS X-like aesthetics.<ref>[https://www.xquartz.org/index.html XQuartz] (accessed 2026-09-05)</ref> XQuartz can run in rootless and rootful modes, although it relies on the X Window Manager for window decorations in either mode; thus, XQuartz must be used with a window manager such as ''quartz-wm'' even in rootless mode.<ref>[https://www.xquartz.org/index.html Remote X11 Window Manager on XQuartz], 2024-04-06 (accessed 2026-09-05)</ref><ref>[https://gitlab.freedesktop.org/xorg/app/quartz-wm xorg/app/quartz-wm] (accessed 2026-09-05)</ref> == References == abbcf4f121b88a21af953ff96defdb5a2007c9c5 6 1457 6128 2026-09-05T19:02:37Z Uniolo 345 wikitext text/x-wiki A photo of the program 'countryfetch' displaying information about Antartica a760814c82e2ddd9a41145c2d963e9dd53551c21 0 1458 6129 2026-09-05T19:07:15Z Uniolo 345 Created countryfetch with various information, Antartica was chosen for the screenshot due to it not being a country (and hence being less likely to cause drama) wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = countryfetch | releasestatus = Maintained | lastrelease = 0.2.0, 4 June 2025 | languages = [[Rust]] | developers = [https://github.com/nik-rev Nik Rev] | website = [https://github.com/nik-rev/countryfetch github.com/nik-rev/countryfetch] | license = Apache 2.0 License | sourcecode = [https://github.com/nik-rev/countryfetch github.com/nik-rev/countryfetch] }} [[Category:Software]] [[File:Countryfetch antartica.png|alt=countryfetch displaying information about Antartica|thumb|countryfetch displaying information about Antartica]] '''Countryfetch''' is a program written by Nik Rev in rust, it is capable of displaying various information about various countries and [[wikipedia:Antarctica|Antartica]]. == References == <references /> b933daff0e99f1ee0fa096d6503ec1815f0971d8 6131 6129 2026-09-05T19:10:00Z Uniolo 345 Removed refrences section, none yet. wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = countryfetch | releasestatus = Maintained | lastrelease = 0.2.0, 4 June 2025 | languages = [[Rust]] | developers = [https://github.com/nik-rev Nik Rev] | website = [https://github.com/nik-rev/countryfetch github.com/nik-rev/countryfetch] | license = Apache 2.0 License | sourcecode = [https://github.com/nik-rev/countryfetch github.com/nik-rev/countryfetch] }} [[Category:Software]] [[File:Countryfetch antartica.png|alt=countryfetch displaying information about Antartica|thumb|countryfetch displaying information about Antartica]] '''Countryfetch''' is a program written by Nik Rev in rust, it is capable of displaying various information about various countries along with [[wikipedia:Antarctica|Antartica]]. eb3f75ec9ca6067ddea8170aece0b956aa9d1b21 6144 6131 2026-09-06T13:15:22Z Uniolo 345 Added usage basic information wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = countryfetch | releasestatus = Maintained | lastrelease = 0.2.0, 4 June 2025 | languages = [[Rust]] | developers = [https://github.com/nik-rev Nik Rev] | website = [https://github.com/nik-rev/countryfetch github.com/nik-rev/countryfetch] | license = Apache 2.0 License | sourcecode = [https://github.com/nik-rev/countryfetch github.com/nik-rev/countryfetch] }} [[Category:Software]] [[File:Countryfetch antartica.png|alt=countryfetch displaying information about Antartica|thumb|countryfetch displaying information about Antartica]] '''Countryfetch''' is a program written by Nik Rev in rust, it is capable of displaying various information about various countries along with [[wikipedia:Antarctica|Antartica]]. A full list of countries can be found by using <code>countryfetch --list-countries</code>, you can display information about a country by using <code>countryfetch [COUNTRY]</code> or <code>countryfetch [COUNTRY CODE]</code>. If no arguments are provided, it will display information about your country. bb8f06a4168577a4a751dce1ecf32cfce4e7358d 6145 6144 2026-09-06T13:15:48Z Uniolo 345 Changed "your country" to "your current country" wikitext text/x-wiki {{Stub}}{{SoftwareInfobox | title = countryfetch | releasestatus = Maintained | lastrelease = 0.2.0, 4 June 2025 | languages = [[Rust]] | developers = [https://github.com/nik-rev Nik Rev] | website = [https://github.com/nik-rev/countryfetch github.com/nik-rev/countryfetch] | license = Apache 2.0 License | sourcecode = [https://github.com/nik-rev/countryfetch github.com/nik-rev/countryfetch] }} [[Category:Software]] [[File:Countryfetch antartica.png|alt=countryfetch displaying information about Antartica|thumb|countryfetch displaying information about Antartica]] '''Countryfetch''' is a program written by Nik Rev in rust, it is capable of displaying various information about various countries along with [[wikipedia:Antarctica|Antartica]]. A full list of countries can be found by using <code>countryfetch --list-countries</code>, you can display information about a country by using <code>countryfetch [COUNTRY]</code> or <code>countryfetch [COUNTRY CODE]</code>. If no arguments are provided, it will display information about your current country. 3bafc0babefc27de4b28487742219156a3f7eb79 6 1459 6130 2026-09-05T19:08:01Z Imnotgoodatnames 121 IceWM running on XQuartz wikitext text/x-wiki == Summary == IceWM running on XQuartz == Licensing == {{GPL}} e773d8fe327aa0b41b8eff13aeca9ea45838de66 6 1460 6132 2026-09-05T19:14:25Z Imnotgoodatnames 121 XTerm running in quartz-wm on XQuartz wikitext text/x-wiki == Summary == XTerm running in quartz-wm on XQuartz == Licensing == {{GPL}} 2363916d2749ecb08d0517eaedc680752621a011 0 1461 6133 2026-09-05T19:19:17Z Imnotgoodatnames 121 Create page with stub, screenshots, infobox, refs wikitext text/x-wiki {{Stub}} {{SoftwareInfobox | title = XQuartz | image = [[File:X.Org_Logo.svg{{!}}class=skin-invert|frameless|upright=0.6]] | caption = X.Org logo, used by XQuartz | releasestatus = Maintained | lastrelease = 2.8.6 | languages = [[C]] | developers = XQuartz project Apple (historical) | website = [https://www.xquartz.org/ www.xquartz.org] | license = [[MIT_License|MIT]] Apple Public Source License 2.0 (quartz-wm) | sourcecode = [https://github.com/XQuartz github.com/XQuartz] }} [[File:Xterm quartz.png|thumb|XTerm client in a quartz-wm window]] [[File:IceWM XQuartz.png|thumb|[[IceWM]] running in rooted mode on XQuartz]] '''XQuartz''' is an implementation of the [[X.Org]] [[X Window System|server]] for [[macOS]] originally developed by Apple.<ref name=site>[https://www.xquartz.org/ XQuartz] (accessed 2026-09-05)</ref> XQuartz can run in both rootless and rootful modes, although it relies on the X Window Manager for window managment in both modes, which is why it ships with a custom [[X Window Manager|X window manager]], ''quartz-wm'', preinstalled, though other window managers can be used instead.<ref>[https://www.xquartz.org/index.html Remote X11 Window Manager on XQuartz], 2024-04-06 (accessed 2026-09-05)</ref><ref name=wm-git>[https://gitlab.freedesktop.org/xorg/app/quartz-wm xorg/app/quartz-wm] (accessed 2026-09-05)</ref> XQuartz is usually launched using the provided XQuartz.app bundle, which starts the X server in, by default, rootless mode and starts quartz-wm as well as [[xterm]]. == quartz-wm == '''quartz-wm''' is an X window manager for XQuartz originally developed by Apple and currently maintained by the X.Org Foundation. quartz-wm is designed to emulate the look of the macOS UI. It uses the AppleWM X11 protocol extension to have XQuartz render its window borders and handles basic window managment.<ref name=wm-git/> == References == 90269270c81d00bd6c8f96440fdfe1d186919bf1 828 163 6134 5097 2026-09-06T06:39:09Z Madonuko 140 make website optional Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage( args.image, args.caption ) end retval:addRow( 'Release Status', args.releasestatus ) :addRow( 'Release Model', args.releasemodel ) :addRow( 'Package Manager', args.packagemanager ) :addRow( 'Default Desktops', args.defaultdesktops ) :addRow( 'Usage Type', args.usagetype ) :addRow( 'Architectures', args.architectures ) if args.website then retval:addRow( 'Website', args.website ) end if args.wiki then retval:addRow('Wiki', args.wiki) end return retval end return p 0c834a74624186dc30d4b723fed3b27fb6f32eb4 10 162 6135 5102 2026-09-06T06:39:39Z Madonuko 140 document website as optional wikitext text/x-wiki <includeonly>{{#invoke:DistributionInfobox|main}}</includeonly> <noinclude>{{/doc}}<templatedata> { "params": { "title": { "type": "string", "required": true }, "image": { "type": "wiki-file-name" }, "caption": {}, "releasestatus": { "required": true }, "releasemodel": { "required": true }, "packagemanager": { "required": true }, "defaultdesktops": { "required": true }, "usagetype": { "required": true }, "architectures": { "required": true }, "website": { "type": "url" }, "wiki": { "type": "url" } }, "format": "block" } </templatedata></noinclude> 31f8e10fd650ff0d964a3de969ae9d65eb627d59 828 204 6136 5323 2026-09-06T06:40:33Z Madonuko 140 make website optional, add platforms field Scribunto text/plain local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) if args.image then retval:addImage(args.image, args.caption) end retval:addRow('Release Status', args.releasestatus) retval:addRow('Last Release', args.lastrelease) if args.firstrelease and args.firstrelease ~= '' then retval:addRow('First Release', args.firstrelease) end retval:addRow('Language(s)', args.languages) retval:addRow('Developer(s)', args.developers) if args.website then retval:addRow('Website', args.website) end if args.license then retval:addRow('License', args.license) end if args.sourcecode then retval:addRow('Source Code', args.sourcecode) end if args.platforms then retval:addRow('Platforms', args.platforms) end return retval end return p af654a7a1628ff596ea9def20a13043c466e78f5 10 205 6137 5286 2026-09-06T06:42:13Z Madonuko 140 document platforms field, make website field optional wikitext text/x-wiki <includeonly>{{#invoke:SoftwareInfobox|main}}</includeonly> <noinclude>{{/doc}}<templatedata> { "params": { "title": { "required": true }, "image": { "type": "wiki-file-name" }, "caption": { "type": "string" }, "releasestatus": { "required": true }, "lastrelease": { "required": true }, "firstrelease": {}, "languages": { "required": true }, "developers": { "required": true }, "website": { "label": "Website", "type": "url" }, "license": { "label": "License", "description": "[[SPDX]] license identifier", "example": "MIT OR Apache-2.0", "type": "string" }, "sourcecode": { "label": "Source code repository", "type": "url" }, "platforms": { "description": "Systems that the software runs on", "example": "[[Linux]], [[FreeBSD]], [[DOS]]", "type": "content" } }, "format": "block" } </templatedata></noinclude> 61156e1b43ebc41ea956660884622757ea80222b 0 575 6138 6075 2026-09-06T08:06:18Z Imnotgoodatnames 121 Add platforms, update website. bump latest release, add development release wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|126px]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=31.1, Aug 24, 2026 32.0.50 (development) |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/software/emacs/ gnu.org/software/emacs] |platforms = [[Linux]], [[macOS]], [[BSD]], [[Microsoft Windows]], [[Cygwin]], [[Android]], [[Haiku]], [[DOS (x86 operating system)|DOS (DJGPP)]] }} [[Category:Software]] [[Category:Text editors]] GNU Emacs is a free/libre text editor and interpreter for the Emacs Lisp language, with extensions to assist with various other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, it's strongly recommended to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. ''Also see [[Vim]].'' == References == 9878d947d9bb56c6d20605f09ecf84a65650f083 6139 6138 2026-09-06T08:10:32Z Imnotgoodatnames 121 Clarify Windows on ARM is not officially supported wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|126px]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=31.1, Aug 24, 2026 32.0.50 (development) |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/software/emacs/ gnu.org/software/emacs] |platforms = [[Linux]], [[macOS]], [[BSD]], [[Microsoft Windows]] (x86_64 only), [[Cygwin]], [[Android]], [[Haiku]], [[DOS (x86 operating system)|DOS (DJGPP)]] }} [[Category:Software]] [[Category:Text editors]] GNU Emacs is a free/libre text editor and interpreter for the Emacs Lisp language, with extensions to assist with various other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, it's strongly recommended to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. ''Also see [[Vim]].'' == References == 88f3cf76a22d8893e9733d2409897e8f724e1761 6140 6139 2026-09-06T08:16:59Z Imnotgoodatnames 121 forgot the Hurd oops wikitext text/x-wiki {{SoftwareInfobox |image=[[File:EmacsIcon.svg|126px]] |caption=GNU Emacs logo |title=GNU Emacs |releasestatus=Maintained |lastrelease=31.1, Aug 24, 2026 32.0.50 (development) |firstrelease=13, Mar 20, 1985 |languages=[[C]], [[Emacs Lisp]] |developers=[[GNU]] |website=[https://www.gnu.org/software/emacs/ gnu.org/software/emacs] |platforms = [[Linux]], [[macOS]], [[BSD]], [[Microsoft Windows]] (x86-64 only), [[Cygwin]], [[Android]], [[Haiku]], [[GNU/Hurd|GNU (Hurd)]], [[DOS (x86 operating system)|DOS (DJGPP)]] }} [[Category:Software]] [[Category:Text editors]] GNU Emacs is a free/libre text editor and interpreter for the Emacs Lisp language, with extensions to assist with various other features.<ref name=":0">[https://www.gnu.org/software/emacs/emacs.html GNU Emacs - GNU Project], GNU Project, 2015-08-10 (Accessed: 2025-08-10)</ref> It began development in 1984 by Richard Stallman of the GNU project as a part of the Emacs family of editors.<ref>[https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/HISTORY HISTORY « etc - emacs.git - Emacs source repository], 2025-08-09 (Accessed: 2025-08-09)</ref> The latest version of Emacs is 30.2 released on the 14th of August, 2025.<ref><span style="color:#fc493b">https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30</span></ref> == History == The history of GNU Emacs starts with TECO, a command-based text editor written by Dan Murphy in 1962, originally made for MIT's PDP-1 machines. TECO was continually iterated on and ported to newer machines, such as the PDP-6, PDP-8, PDP-10 (AKA DecSystems 10), and PDP-11.<ref>Murphy, Dan. “The Beginnings of TECO.” IEEE Annals of the History of Computing 31, no. 4 (October 2009): 110–15. https://doi.org/10.1109/MAHC.2009.127.</ref> Richard Stallman, inspired by E, an early visual text editor written at Stanford AI Lab, enhanced TECO for the PDP-10 by adding visual editing capabilities in 1974. Stallman also included a "macro" system, allowing users to bind TECO functions to custom commands. This very quickly lead to the spread of user made macro collections like TECMAC and TMACS.<ref>Stallman, Richard M. “EMACS the Extensible, Customizable Self-Documenting Display Editor.” ACM SIGOA Newsletter 2, no. 1–2 (April 1, 1981): 147–56. https://doi.org/10.1145/1159890.806466.</ref> Two years later, Guy Steele made efforts to create a more unified set of macros, and with Stallman's help, EMACS was created in late 1976.<ref name=":1">Williams, Sam. Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution. 2nd ed. Boston, MA: Free Software Foundation, 2010.</ref> EMACS inspired many clones for other operating systems and machines, including EINE and ZWEI written in Lisp Machine Lisp, Multics Emacs in MacLisp, and James Gosling's Emacs (AKA Gosmacs) for Unix in C.<ref>Monnier, Stefan, and Michael Sperber. “Evolution of Emacs Lisp.” Proceedings of the ACM on Programming Languages 4, no. HOPL (June 12, 2020): 74:1-74:55. https://doi.org/10.1145/3386324.</ref> Seeking to write a fully free/libre version of Emacs, Stallman made modifications to Gosling's Emacs in 1984, under the impression that he was free to do so.<ref name=":1" /> However, UniPress, who had purchased the rights to Gosling's Emacs the year prior,<ref>UniPress Software, Inc. Advertisement, Byte Magazine, December 1983, 334.</ref> claimed that Stallman did not have the right to redistribute his own version of Gosmacs. Stallman complied with their request by replacing all of Gosling's code with new original code.<ref name=":1" /> On March 20, 1985, Stallman shared the first public release of GNU Emacs.<ref name=":0" /> == Keybindings == Emacs recognizes several modifier keys, notated as following: {| class="wikitable" |+Emacs Key Modifiers !Prefix !Key !Notes |- |<code>C-</code> |{{Keypress|Ctrl}} | |- |<code>M-</code> |{{Keypress|Meta}} |This is the {{Keypress|Alt}} or {{Keypress|Option}} key |- |<code>S-</code> |{{Keypress|Shift}} | |- |<code>s-</code> |{{Keypress|Super}} |This is the {{Keypress|Win}} or {{Keypress|Command}} key |- |<code>RET</code> | {{Keypress|Return}} | {{Keypress|Enter}} key |- |<code>H-</code> |{{Keypress|Hyper}} |This key is supported, but no default bindings use it |- |<code>A-</code> |{{Keypress|Alt*}} |*This is most certainly NOT the same key as Alt. This is a holdover back when keyboards had separate Meta and Alt keys |} Multiple modifiers can be held together, represented by putting them one after the other. For example, <code>C-S-a</code> represents {{Keypress|Ctrl|Shift|a}}. Note that <code>C-</code> keybindings are case insensitive in the terminal,<ref>[https://www.gnu.org/software/emacs/manual/html_node/emacs/Modifier-Keys.html Modifier Keys (GNU Emacs Manual)], GNU Project (Accessed: 2025-08-10)</ref> so there is no distinction between <code>C-a</code> and <code>C-A</code>. This isn't an issue for the default keybindings, but custom bindings may rely on this. Consider using graphical Emacs if you wish to take advantage of this. Most keybindings consist of a "prefix" followed by one or more keys. For example, to execute <code>C-x C-s</code>, you need to press the prefix <code>C-x</code> first, and then press <code>C-s</code>. In this case, you can hold down the {{Keypress|Ctrl}} key and press {{Keypress|x|s|chain=}} in quick succession. This can help reduce strain on the pinky from frequently pressing the {{Keypress|Ctrl}} key. == Installing == See [[Guides:Emacs Installation Guide|the installation guide here.]] == Documentation == Emacs has an extensive library of documentation which covers its functions, variables and keys. It can be found by opening Metahelp with <code>C-h ?</code> and then pressing the key corresponding to the section you are looking for. You may also use the keys from Metahelp after the <code>C-h</code> prefix. For example: <code>C-h k</code> to access <code>describe-key</code>. == Setting up MELPA == MELPA is a commonly used Emacs package repository which provides more packages you may want to use such as Flycheck for syntax checking. MELPA provides its own "Getting started" page<ref>[https://melpa.org/#/getting-started Getting started], MELPA, 2024-11-20 (Accessed: 2025-08-09)</ref> which we suggest reading. We will provide information on setting it up here however. Before we begin, it's strongly recommended to move '''~/.emacs''' to '''~/.emacs.d/init.el''' (create the directory if it is missing) to avoid any future confusion. In this '''init.el''', add either of the options in the following code block.<syntaxhighlight lang="emacs-lisp">;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package package :config (add-to-list 'package-archives '("melpa". "https://melpa.org/packages") t) (package-initialize)) ;; Option 2 (require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages") t) (package-initialize)</syntaxhighlight>After reloading the configuration, you will now be able to have MELPA packages installable with <code>M-x package-install</code>. == Setting up LSP support == Since 29.1, Emacs has provided Eglot as a way to manage LSPs. If you want to autoload Eglot at startup, then you could use one of the options from the codeblock.<syntaxhighlight lang="emacs-lisp"> ;; Option 1 (Recommended if using Emacs 29.1 or later) (use-package eglot :hook prog-mode :bind (("C-c l" . eglot-code-actions) ("C-c l f b" . eglot-format-buffer) ("C-c l f r" . eglot-format))) ;; Option 2 (require 'eglot) (add-hook #'prog-mode-hook #'eglot-ensure) (local-set-key "C-c l c a" 'eglot-code-actions) (local-set-key "C-c l f b" 'eglot-format-buffer) (local-set-key "C-c l f r" 'eglot-format) </syntaxhighlight>This will allow Eglot to start when <code>prog-mode</code> (<code>c-mode</code>, <code>python-mode</code> and <code>js-mode</code> among other programming modes) are enabled and an LSP is found. Eglot commands can be mapped as seen fit. == Evil == Evil (Extensible VI Layer) is a package which provides Emacs with Vi emulation.<ref>[https://github.com/emacs-evil/evil GitHub - emacs-evil/evil: The extensible vi layer for Emacs.], emacs-evil, 2025-08-09 (Accessed: 2025-08-09)</ref> It is prevalent in Emacs distributions including but not limited to Doom Emacs<ref>[https://github.com/doomemacs/doomemacs?tab=readme-ov-file#features GitHub - doomemacs/doomemacs: An Emacs framework for the stubborn martian hacker], doomemacs, 2025-08-09 (Accessed: 2025-08-09)</ref> and Spacemacs<ref>[https://www.spacemacs.org/ Spacemacs: Emacs advanced Kit focused on Evil], Sylvain Benner and Contributors, 2025-07-21 (Accessed: 2025-08-09)</ref>, though it can be installed in Vanilla Emacs through MELPA. To install Evil, open <code>package-install</code> to install <code>evil</code>. You will then have Evil installed in Emacs. To enable Evil, add this to your <code>init.el</code>:<syntaxhighlight lang="emacs-lisp"> ;; Option 1, reccomended if using Emacs 29.1 or over. (use-package evil :hook after-init) ;; Option 2 (require 'evil) (evil-mode 1) </syntaxhighlight>You should now have Evil set up to start as soon as Emacs is opened. You can choose to customise it more to your liking. ''Also see [[Vim]].'' == References == adf371a801ccc8b91656bf5a5abc54e4e3b658ba 0 1398 6141 6071 2026-09-06T08:17:31Z Imnotgoodatnames 121 Add platforms wikitext text/x-wiki {{SoftwareInfobox | title = GNUstep | caption = GNUstep logo | releasestatus = Maintained | developers = GNUstep developers, GNU Project | image = [[File:GNUstep logo.png{{!}}class=skin-invert|200px|GNUstep_logo]] | languages = [[Objective-C]] | lastrelease = Varied (GNUstep components often have independent releases)<ref>[https://github.com/gnustep GNUstep Github]</ref> | website = [https://www.gnustep.org/ gnustep.org] | platforms = [[Linux]], [[BSD]], [[Microsoft Windows]], [[GNU/Hurd|GNU (Hurd)]] }} [[File:GNUstep_desktop.png|thumb|GNUstep managing its own windows, with the Macintosh menu interface style.]] '''GNUstep''' is a [[Free_and_Open_Source_Software|free]] implementation of Apple's [[Cocoa]] API and a collection of software based on that API. It is a part of the [[GNU]] project. Both GNUstep and Cocoa share the same OpenStep roots.<ref name="website">[https://gnustep.org GNUstep homepage]</ref> GNUstep supports many unique features such as special menu bar behaviour, which can be configured to act like NeXTSTEP's, [[Microsoft Windows]]' or even [[macOS]]' (with the menu bar of supported applications displayed as a small seperate window, as part of the application window or on top of the display, respectively). It can also manage windows and window decorations of any supported app, therefore technically bypassing the need for a seperate [[X_Window_Manager|window manager]], though non-GNUstep windows will remain unmanaged.<ref>[https://www.gnustep.org/resources/documentation/User/Gui/DefaultsSummary.html User Defaults Summary for GNUstep Libraries]</ref> GNUstep is cross platform and supports [[UNIX]] and Unix-like systems and Microsoft Windows. On Unix and Unix-like systems it runs primarily on [[X_Window_System|X]] with limited support for [[Wayland]].<ref>[https://home.gnustep.org/windows/installer.html Windows Installer]</ref><ref>[https://www.phoronix.com/news/GNUstep-0.29-With-Wayland GNUstep Releases Early Wayland Support, Many Other Improvements Too]</ref> [[Window Maker]] is the most common window manager used with GNUstep due to its limited integration with it and their shared default NeXTSTEP-inspired aesthetics.<ref>[https://mediawiki.gnustep.org/index.php/Window_Maker Window Maker]</ref> == Applications == GNUstep '''applications''' are distributed in the form of portable application bundles. Like on macOS, they are regular directories with the '.app' suffix that contain the [[executable]] itself, the application icon and various metadata, such as the application version.<ref>[https://www.gnustep.org/resources/documentation/Developer/Base/Reference/NSBundle.html NSBundle class reference]</ref> === Example GNUstep application === <syntaxhighlight lang="text"> TextEdit.app ├── Resources │ ├── ApplicationScripting.xlp │ ├── Edit.tiff │ ├── EditTitle.tiff │ ├── Encodings.txt │ ├── English.lproj │ ├── Info-gnustep.plist │ ├── ScriptingInfo.plist │ ├── TextEdit.desktop │ ├── rtf.tiff │ ├── rtfd.tiff │ └── text.tiff ├── TextEdit └── stamp.make </syntaxhighlight> == GWorkspace == {{SoftwareInfobox | title = GWorkspace | image = [[File:GWorkspace-resized.png|128px]] | releasestatus = Maintained | lastrelease = 1.1.0 | caption = GWorkspace application icon | languages = [[Objective-C]]<ref name=git>[https://github.com/gnustep/apps-gworkspace GWorkspace], GNUstep, 2026-08-25 (Accessed: 2026-08-25)</ref> | developers = GNUstep project | website = [https://www.gnustep.org/experience/GWorkspace.html GWorkspace] | license = [[GPL|GPLv2]] | sourcecode = https://github.com/gnustep/apps-gworkspace }} [[File:GWorkspace-desktop.png|thumb|GWorkspace as a file manager and graphical shell, managing the recycle bin, desktop settings, desktop icons and an application dock on a GNUstep desktop.]] '''GWorkspace''' is a GNUstep reimplementation of the NeXTSTEP file manager and the GNUstep equivalent of [[Finder]]. It is a file manager application and, optionally, a desktop shell that provides a customizable desktop with desktop icons and an application dock.<ref name=site>[https://www.gnustep.org/experience/GWorkspace.html GNUstep Workspace Manager: GWorkspace], GNUstep, 2025-02-24 (Accessed: 2026-08-25)</ref> It provides various features of a desktop shell including a recycle bin, a desktop preferences window and previews for images and other files.<ref>[https://mediawiki.gnustep.org/index.php/GWorkspace.app GWorkspace.app], GNUstepWiki, 2025-12-25 (Accessed: 2026-08-25)</ref> === Gershwin Workspace === '''Workspace''' is a fork of GWorkspace for the [[Gershwin|Gershwin desktop environment.]] Like the rest of Gershwin, it aims to bring a more macOS-like experience to the desktop and therefore includes features such as thumbnail previews for files and the ability to place the dock on the bottom of the desktop as opposed to just the right or left.<ref>[https://github.com/gershwin-desktop/gershwin-workspace gershwin-desktop/gershwin-workspace: Fork of GWorkspace with modifications for Gerswhin], gershwin-desktop, 2026-08-25 (Accessed: 2026-08-25)</ref> == References == e07b8e7f7523087572dd7ef50ed5d9bc44fceaaf 3000 1462 6142 2026-09-06T11:40:53Z Imnotgoodatnames 121 Create guide for starting X session wikitext text/x-wiki To run an [[X Window Manager|X window manager]] you first need to start an [[X Window System|X]] server either automatically or manually using the following methods. == Using a display manager == [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|SDDM display manager screenshot]] A [[display Manager|display manager]], also known as a '''login manager''', is a [[GUI|graphical]] program displayed after the boot process which has you enter a username and password to log in to the system. Most display managers also let you choose the [[desktop Environments|desktop environment]] or window manager to log in to. Display managers usually replace the default [[tty]] login screen. Examples of display managers for X11 include [[XDM]], [[LightDM]] and [[SDDM]]. == Using xinit == '''xinit''' is a tool that automatically starts a configured X server. '''startx''' is a wrapper around xinit that provides some sane defaults and is generally used instead of running xinit directly. xinit starts the X server and runs a shell script, usually <code>$HOME/.xinitrc</code>, containing a series of commands that are ran after X starts. When the last command in the script quits, xinit kills the X server, so the last command is generally the window manager. === Example xinitrc === All processes, except the final one, that run continuously - i.e. that lock the shell until they finish - should have an ampersand <code>&</code> placed after their command to prevent xinit from getting stuck. If unsure, place the ampersand. This example xinitrc sets the keyboard layout to Russian, starts xscreensaver, launches a terminal emulator and starts the window manager. When the window manager quits the X server will automatically close as well. <syntaxhighlight lang="shell"> #!/bin/sh exec setxkbmap ru exec xscreensaver -no-splash & exec xterm & exec twm </syntaxhighlight> == Starting X manually == You can start an X server manually using the <code>X</code> or <code>Xorg</code> commands. Keep in mind that X will not read any xinit files using this method. To start xterm in this state you can switch to a tty shell using ctrl+alt+fn and run <code>DISPLAY=:<x> xterm</code> where <code><x></code> is the number of the display, usually <code>0</code>. 43fc0fbf971b93b11fbb72706762fb050525ca57 6143 6142 2026-09-06T11:44:33Z Imnotgoodatnames 121 Minor fixes wikitext text/x-wiki To run an [[X Window Manager|X window manager]] you first need to start an [[X Window System|X]] server either automatically or manually using the following methods. == Using a display manager == [[File:Simple-desktop-display-manager-kde.png|alt=SDDM screenshot|thumb|SDDM display manager screenshot]] A [[display Manager|display manager]], also known as a '''login manager''', is a [[GUI|graphical]] program displayed after the boot process which has you enter a username and password to log in to the system. Most display managers also let you choose the [[desktop Environments|desktop environment]] or window manager to log in to. Display managers usually replace the default [[tty]] login screen. Examples of display managers for X11 include [[XDM]], [[LightDM]] and [[SDDM]]. == Using xinit == '''xinit''' is a tool that automatically starts a configured X server. '''startx''' is a wrapper around xinit that provides some sane defaults and is generally used instead of running xinit directly. xinit starts the X server and runs a shell script, usually <code>$HOME/.xinitrc</code>, containing a series of commands that are ran after X starts. When the last command in the script quits, xinit kills the X server, so the last command is generally the window manager. === Example xinitrc === All processes, except the final one, should have an ampersand <code>&</code> placed after their command to prevent xinit from getting stuck. This example xinitrc sets the keyboard layout to Russian, starts xscreensaver, launches a terminal emulator and starts the [[twm]] window manager. When the window manager quits the X server will automatically close as well. <syntaxhighlight lang="shell"> #!/bin/sh exec setxkbmap ru & exec xscreensaver -no-splash & exec xterm & exec twm </syntaxhighlight> == Starting X manually == You can start an X server manually using the <code>X</code> or <code>Xorg</code> commands. Keep in mind that X will not read any xinit files using this method. To start xterm in this state you can switch to a tty shell using ctrl+alt+fn and run <code>DISPLAY=:<x> xterm</code> where <code><x></code> is the number of the display, usually <code>0</code>. 779c7f46b929ea0e00ef74447cec3a0053e5e1d8 0 177 6147 4696 2026-09-08T01:03:58Z Fleetoise 190 Fixing grammatical errors and increasing readability wikitext text/x-wiki [[Category:Terminology]] '''Free and Open Source Software''' ('''FOSS'''), or Free/Libre (from the French word libre, meaning "free") and Open Source Software (FLOSS), is [[:Category:Software|software]] that is available under a license that grants the right to use, modify, distribute and sell the software, modified or not, to everyone. The public availability of the source code is, therefore, a necessary but not sufficient condition. FOSS is an inclusive umbrella term for free software and open-source software. The most accepted definition of Open Source is maintained by The Open Source Initiative, and is called "Open Source Definition"(OSD). The OSD was originally derived from the Debian Free Software Guidelines (DFSG)<ref>[https://opensource.org/osd The Open Source Definition], Open Source Initiative, 2007-03-22 (Accessed: 2026-01-18)</ref>. The Free Software Foundation maintains the accepted definition of Free Software<ref>[https://www.gnu.org/philosophy/free-sw.html What is Free Software?], GNU Project, 2025-12-28 (Accessed: 2026-01-18)</ref>. Proprietary or non-free software is under restrictive licensing that goes against the user rights outlined in FOSS definitions. Such restrictions include but are not limited to disallowing redistribution, sale, modification, or usage of the [[Source Code|source]] or [[Binary|binaries]] by a specific group, or requiring payment to exercise the mentioned user rights. An example of proprietary source-available software is Unreal Engine, which requires payment of royalties for the distribution of certain binaries if the source includes Unreal Engine code<ref><nowiki>https://www.unrealengine.com/en-US/eula/unreal</nowiki></ref>. === Notes === ----FOSS (Free and Open Source Software) is an inclusive term encompassing both free software and open-source software. Although these terms describe similar development models, they stem from different cultures and philosophical backgrounds. "Free" in this context refers to the users' freedom to copy and reuse the software. The Free Software Foundation, which promotes the free software model, emphasizes this by suggesting one should "think of free as in free speech, not as in free beer" (see [https://www.gnu.org/philosophy/free-sw.html "The Free Software Definition"], GNU, retrieved February 4, 2010). Free software focuses on the essential freedoms it grants to users, while open-source software highlights the strengths of its collaborative development model.<ref>[[wikipedia:Free_and_open-source_software#CITEREFFeller2005|Feller 2005]], pp. 101-106, 110-111. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> FOSS and FLOSS<ref>https://www.gnu.org/philosophy/floss-and-foss.html Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> are neutral terms that can be used without favoring either political approach.<ref>[[wikipedia:Free_and_open-source_software|"Free and open-source software"]]. Wikipedia. Wikimedia Foundation. Accessed June 4, 2024.</ref> == References == 8163561f8cea9a6b8660084e07ce2b6284dd4ad5 4 595 6148 5996 2026-09-09T20:03:34Z Atmois 13 Update emails wikitext text/x-wiki == Discord == The best way to get help from the community or administrators is by joining our [https://discord.foss.wiki Discord Server] and asking for help in the <code>#wiki</code> channel! If the issue is of a more sensitive nature, you can open a ticket with <code>/ticket</code> and ask for an Admin. You may also direct message <code>@atmois</code> (Wiki Director) for topics of a more sensitive nature. == Email == To email all staff at once please email: ''team(at)foss.wiki'' ~ To report security vulnerabilities please see our [[FW:Security|Security Policy]]. [[User:Atmois|Atmois]] - Wiki Director ''- atmois(at)foss.wiki'' [[User:Ow0cast|Ow0cast]] - Wiki Steward - ''owuh(at)foss.wiki'' [[User:Madonuko|Madonuko]] - Wiki Steward - ''mado.n(at)foss.wiki'' 2cbc672512c521ca57e1bc825529678b7fdd8266 2 192 6149 4990 2026-09-11T18:17:54Z Atmois 13 Add contact info wikitext text/x-wiki Local tech nerd, who listens to ''a lot'' of music. '''foss.wiki'''<nowiki/>'s director, come join us and [[FW:Contributing|contribute]]! https://atmois.com Email me at atmois(at)foss(dot)wiki or DM me on Discord @atmois for wiki issues! 6b9e8c80caba2b25b3ae42dc9f7b249d7c6d8acb 0 1416 6151 6103 2026-09-26T09:16:21Z Imnotgoodatnames 121 Remove WiP wikitext text/x-wiki [[Category:Software]] {{DistributionInfobox | title = MSYS2 | image = [[file:Msys2.svg|frameless|upright=0.5|MSYS2 icon]] | caption = MSYS2 icon | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://www.msys2.org/ msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 Support], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64], David Allsopp, 2018-08-25 (Accessed: 2026-08-25)</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS2 environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by <ref name=envs>[https://www.msys2.org/docs/environments/ Environments], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture |- |[[File:Msys2.svg|32px|MSYS icon]] |MSYS |<code>/usr</code> |gcc |Cygwin |x86_64 |- |[[File:Ucrt64.svg|32px|UCRT64 icon]] |UCRT64 |<code>/ucrt64</code> |gcc |UCRT |x86_64 |- |[[File:Clang64.svg|32px|CLANG64 icon]] |CLANG64 |<code>/clang64</code> |llvm |UCRT |x86_64 |- |[[File:Clangarm64.svg|32px|CLANGARM64 icon]] |CLANGARM64 |<code>/clangarm64</code> |llvm |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS2. It is always active, all other environments inherit from it and add their own environment variables on top. === Legacy environments === These environments are considered legacy and are not installed by default. {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture |- |[[File:Mingw32.svg|32px|MINGW32 icon]] |MINGW32 |<code>/mingw32</code> |gcc |MSVCRT |i686 |- |[[File:Mingw64.svg|32px|MINGW64 icon]] |MINGW64 |<code>/mingw64</code> |gcc |MSVCRT |x86_64 |- |[[File:Clang32.svg|32px|CLANG32 icon]] |CLANG32 |<code>/clang32</code> |llvm |UCRT |i686 |} '''Note''': The root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory (eg. C:\msys2), '''not''' the root of any Windows drive. == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure the MSYS2 setup works without issues, not to install a fully ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11], Blackhex, 2025-02-26 (Accessed: 2026-08-25)</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue Pending Package Updates], MSYS2 Packages, 2026-08-25 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Package name prefix |- |[[File:Msys2.svg|32px|MSYS icon]] |MSYS |None (no package name prefix) |- |[[File:Ucrt64.svg|32px|UCRT64 icon]] |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |[[File:Clang64.svg|32px|CLANG64 icon]] |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |[[File:Clangarm64.svg|32px|CLANGARM64 icon]] |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |[[File:Mingw32.svg|32px|MINGW32 icon]] |MINGW32 |<code>mingw-w64-i686-</code> |- |[[File:Mingw64.svg|32px|MINGW64 icon]] |MINGW64 |<code>mingw-w64-x86_64-</code> |- |[[File:Clang32.svg|32px|CLANG32 icon]] |CLANG32 |None (environment fully deprecated)<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment News], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> (historically <code>mingw-w64-clang-i686-</code>)<ref>[https://www.msys2.org/docs/package-naming/ Package Naming], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> |} == References == 42607bd9957ad6c9cec05745e39014b9ebd2338d 6152 6151 2026-09-26T09:47:59Z Imnotgoodatnames 121 Minor fixes, status column in legacy environments table, more legacy env info, compiler names are now properly cased wikitext text/x-wiki [[Category:Software]] {{DistributionInfobox | title = MSYS2 | image = [[file:Msys2.svg|frameless|upright=0.5|MSYS2 icon]] | caption = MSYS2 icon | releasestatus = Maintained | releasemodel = Rolling Release | packagemanager = Pacman | defaultdesktops = Windows desktop | usagetype = Desktop, Server | architectures = x86_64 aarch64 (limited support) | website = [https://www.msys2.org/ msys2.org] }} '''MSYS2''' is a collection of [[open source|open-source]] software that provides a native [[UNIX]]-like shell and development environment for [[Windows|Microsoft Windows]].<ref name=website>[https://msys2.org MSYS2], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> MSYS2 consists of Windows-native software built either for [[Cygwin]] or the native Windows API directly.<ref name=whatis>[https://www.msys2.org/docs/what-is-msys2/ What is MSYS2?], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> The core bash and coreutils tools are based on Cygwin because they don't support native Windows. Because of this, MSYS2 on ARM64 relies on the ARM Windows x86 compatibility layer since Cygwin doesn't run on ARM.<ref>[https://www.msys2.org/docs/arm64/ ARM64 Support], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref><ref>[https://www.mail-archive.com/cygwin@cygwin.com/msg157588.html Cygwin x86 on Windows 10 ARM64], David Allsopp, 2018-08-25 (Accessed: 2026-08-25)</ref> == Environments == MSYS2 uses different environments to separate the various compiler toolchains available for it. MSYS2 environments control environments variables, such as adding their respective prefix to PATH. The current active environment is defined by the <code>$MSYSTEM</code> environment variable.<ref name=envs>[https://www.msys2.org/docs/environments/ Environments], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture |- |[[File:Msys2.svg|32px|MSYS icon]] |MSYS |<code>/usr</code> |GCC |Cygwin |x86_64 |- |[[File:Ucrt64.svg|32px|UCRT64 icon]] |UCRT64 |<code>/ucrt64</code> |GCC |UCRT |x86_64 |- |[[File:Clang64.svg|32px|CLANG64 icon]] |CLANG64 |<code>/clang64</code> |LLVM |UCRT |x86_64 |- |[[File:Clangarm64.svg|32px|CLANGARM64 icon]] |CLANGARM64 |<code>/clangarm64</code> |LLVM |UCRT |aarch64 |} The MSYS environment is the Cygwin-based environment containing the base Unix-like tools of MSYS2. It is always active, all other environments inherit from it and add their own environment variables on top. Note that the root directory <code>/</code> in the MSYS2 environment corresponds to the MSYS2 installation directory, eg. <code>C:\MSYS2</code>, rather than the root of any Windows drive. === Legacy environments === These environments are considered legacy and are not installed by default. They may be receiving updates to existing packages but they will not get any new packages and any broken packages will be removed. {| class="wikitable" ! !Environment !Prefix !Compiler toolchain !C library !Architecture !Status |- |[[File:Mingw32.svg|32px|MINGW32 icon]] |MINGW32 |<code>/mingw32</code> |GCC |MSVCRT |i686 |No new packages, broken packages removed |- |[[File:Mingw64.svg|32px|MINGW64 icon]] |MINGW64 |<code>/mingw64</code> |GCC |MSVCRT |x86_64 |No new packages, broken packages removed |- |[[File:Clang32.svg|32px|CLANG32 icon]] |CLANG32 |<code>/clang32</code> |LLVM |UCRT |i686 |Removed<ref>[https://www.msys2.org/news/#2024-12-18-removal-of-the-clang32-environment Removal of the CLANG32 Environment], MSYS2, 2024-12-18 (Accessed: 2026-09-26)</ref> |} == ARM support == As of august 2026 every MSYS2 environment, including the base MSYS one, uses x86 binaries except CLANGARM64, which uses native ARM ones.<ref name=envs/> This means that MSYS2 on ARM, despite having a dedicated ARM installer, relies on the Windows x86 compatibility layer for ARM.<ref name=website/> The ARM installer exists primarily to ensure the MSYS2 setup works without issues, not to install a fully ARM-native version of MSYS2.<ref>[https://github.com/msys2/msys2-installer/issues/96 Installer hangs on Arm64 Windows 11], Blackhex, 2025-02-26 (Accessed: 2026-08-25)</ref> == Package managment == MSYS2 uses the [[Pacman]] package manager of [[Arch Linux]] for package managment.<ref name=whatis/> MSYS2 packages are divided by separate repositories, one for each environment. Most packages have different versions for each environment, which are distinguished by a prefix of the package name. For example, the UCRT64 clang package is named <code>mingw-w64-ucrt-x86_64-clang</code> while the CLANGARM64 one is named <code>mingw-w64-clang-aarch64-clang</code>. However, base MSYS (Cygwin) packages generally use just the base package name, so the clang package is named simply <code>clang</code>.<ref>[https://packages.msys2.org/queue Pending Package Updates], MSYS2 Packages, 2026-08-25 (Accessed: 2026-08-25)</ref> {| class="wikitable" ! !Environment !Package name prefix |- |[[File:Msys2.svg|32px|MSYS icon]] |MSYS |None (no package name prefix) |- |[[File:Ucrt64.svg|32px|UCRT64 icon]] |UCRT64 |<code>mingw-w64-ucrt-x86_64-</code> |- |[[File:Clang64.svg|32px|CLANG64 icon]] |CLANG64 |<code>mingw-w64-clang-x86_64-</code> |- |[[File:Clangarm64.svg|32px|CLANGARM64 icon]] |CLANGARM64 |<code>mingw-w64-clang-aarch64-</code> |- |[[File:Mingw32.svg|32px|MINGW32 icon]] |MINGW32 |<code>mingw-w64-i686-</code> |- |[[File:Mingw64.svg|32px|MINGW64 icon]] |MINGW64 |<code>mingw-w64-x86_64-</code> |- |[[File:Clang32.svg|32px|CLANG32 icon]] |CLANG32 |None (environment fully deprecated) (historically <code>mingw-w64-clang-i686-</code>)<ref>[https://www.msys2.org/docs/package-naming/ Package Naming], MSYS2, 2026-08-18 (Accessed: 2026-08-25)</ref> |} == References == 0af3af4e75818f0735cd28034ee16f4fe84ecf64